Strategic management has a useful idea for financial infrastructure: industry architecture. It asks how the roles in a system are divided, where the bottlenecks sit and whose rules govern the whole. Applied to correspondent banking, the lens is clarifying, because the system is under pressure precisely where its architecture is fixed.

Roles and where they sit

In a payment chain, several roles exist: who validates legitimacy, who holds the account, who executes, who owns the client relationship, who bears risk. In the correspondent system these are layered and overlapping. An institution can be a trust provider for one counterparty and a competitor to another. Roles are negotiated bilaterally rather than assigned by a shared architecture.

That ambiguity is not a design flaw so much as a historical inheritance. It became expensive when compliance and monitoring costs rose.

Bottlenecks

Every architecture has chokepoints. Here they are familiar: dense, expensive validation repeated across institutions; a shrinking number of correspondent relationships; and routing fixed by relationships rather than chosen. A bottleneck is not simply a slow step — it is a place where the whole system's economics are decided.

A hub restructures the sequence. One compliance function checks every operation once. Approved operations enter a single order book. AI routing then selects among paths. The roles become explicit: validation, netting, ledger, routing, execution.

Rules under pressure

The final element of industry architecture is the rule set. Today it is largely personal and bilateral trust, reviewed institution by institution. FATF Recommendation 17 allows a regulated institution to rely on due diligence performed by another, which makes codified multilateral rules possible. SUPA's reliance agreement turns that into a single document participants sign on joining, with selective audit, limits, suspension and exclusion as controls.

That is an architectural claim: the rules, not only the technology, determine what the system can do. Reading correspondent banking this way explains why the constraint is the connective layer and the governance around it.

In short

  • Industry architecture asks how roles, bottlenecks and rules are divided.
  • Correspondent roles are negotiated bilaterally and overlap.
  • Repeated validation and thin relationships are the bottlenecks.
  • A hub makes validation, netting, ledger and routing explicit.
  • Multilateral reliance rules, not just technology, set the limits.

Read how the six-layer architecture is organised at /about/.