Payment networks are usually evaluated on features: currencies supported, rails connected, integrations offered. Those matter, but they are not what makes a network usable at scale. Reliability and predictability are. A feature is optional; reliability is the product. That distinction is why trust belongs in the architecture, not in the marketing.

Trust that cannot be reused

In the correspondent system, trust is personal, bilateral and non-transferable. Every relationship is established separately between two institutions and reviewed separately. It cannot be passed on, so it cannot be amortised. When a corridor is thin, the cost of maintaining that trust can exceed its value, and the relationship is withdrawn. The consequence is structural: fewer relationships, fewer routes.

Codifying trust as a rule

FATF Recommendation 17 allows a regulated institution to rely on client due diligence performed by another regulated institution. On that basis, trust can become a multilateral rule rather than a series of private arrangements. Participants sign one reliance agreement on joining, which fixes responsibility, the data accompanying each operation, access to KYC documents on request for SUPA, another participant or a regulator, a minimum KYC/KYB standard regardless of jurisdiction, and consequences — selective audit, limits, suspension and exclusion.

The nuance is stated plainly: reliance does not transfer legal responsibility, and cross-border reliance is not permitted everywhere, so local-law limits are checked per jurisdiction.

Reliability as the deliverable

Codified trust then supports predictable operation. A single legitimacy validation checks each operation once. Approved operations enter one order book where offsetting flows cancel, and the remainder is routed by AI across available paths. The ledger records every operation against principal, agent and policy version, so outcomes can be examined rather than assumed.

That traceability is what makes the system dependable: not a promise that nothing will go wrong, but evidence of what happened and under which rules. Features attract attention; reliability earns usage.

In short

  • Features are optional; reliability is the core product.
  • Bilateral, non-transferable trust cannot be reused or amortised.
  • FATF Recommendation 17 allows reliance to be codified.
  • One reliance agreement sets responsibility and consequences.
  • Traceability — not promises — makes a network dependable.

Read how trust is designed into the protocol at /about/.