Banks and financial market infrastructure
Commercial and regional banks, custodians, clearing houses and market infrastructure operators, where the integration is only finished when it can be explained to an examiner.
Leans on 02 · 03 · 05 · 09
Three rooms, one integration problem.
A supervisor, a CFO and an operations director are protecting different things. The engineering underneath is largely the same. What each of them needs to see before signing is not.
Why we separate them
The work converges. The justification does not.
Every organisation on this page has the same underlying problem: a ledger that settles continuously, and an estate that does not. Message mapping, posting models, reconciliation, exception handling and node operations look broadly alike across all three, which is why the twelve capabilities are written once and apply everywhere.
What differs is what has to be true before anyone will approve it. A bank needs evidence that survives an examiner. A payment provider needs unit economics that survive the exception rate. A corporate operations function needs to know who is on call at three in the morning for something nobody in the building has run before.
Those are not marketing distinctions. They change what gets built first, what gets instrumented, and what the handover has to contain. Pretending otherwise produces an integration that is technically correct and unapprovable.
The engineering is the easy part to agree on. The evidence is what the room is actually arguing about.
Sectors
Where the same twelve capabilities land differently
Payment providers, remittance and fintech
Payment service providers, cross-border and remittance operators, e-money institutions and fintechs, where the integration has to hold at the volumes the business plan assumes rather than the volumes the pilot ran.
Leans on 04 · 06 · 11 · 12
Corporate treasury and non-financial infrastructure
Corporate treasury functions, supply chain and logistics operators, energy and utility settlement, and public registries — where the ledger is being asked to carry obligations that currently live in an ERP and a spreadsheet.
Leans on 01 · 05 · 07 · 12
If none of the three describes you
The capabilities are the durable part and they transfer. Tell us what settles, against what, and who has to approve it — that is usually enough to say whether there is work here or not.