Cross-Border Payments Stack

Problem solved

Treasury, ALM, and sanctions compliance teams need a defensible scoring of the cross-border payment rails available to a counterparty cohort. SWIFT remains the default but not the universal choice; CIPS, INSTEX, BRICS Pay, mBridge, and dollar-stablecoin rails each clear different transaction sets at different throughput and different sanction-risk overlays. CBPS scores six rails on a consistent matrix: throughput, sanction durability, counterparty network, settlement finality, regulatory clarity, and unit cost.

Inputs

• Bank for International Settlements CPMI Red Book and CPSS-IOSCO data on payment-system volumes
• SWIFT RMB Tracker and SWIFT Watch for currency share and traffic counts
• PBoC CIPS volume and participant disclosures
• OFAC SDN and SSI list scope of named counterparties
• EU sanctions consolidated list and UK OFSI list overlay
• INSTEX, BRICS Pay, and mBridge participant attestations and central-bank disclosures
• Fintech and stablecoin reserve attestations (Tether, Circle, PYUSD, RLUSD)

Outputs

• Six-rail score matrix per counterparty cohort with explicit weights
• Throughput ceiling per rail in transaction count and notional value
• Sanction durability flag for each rail under a named sanction-tightening scenario
• Counterparty network density score (banks, corporates, central banks accessible)
• Settlement finality rating (real-time, T+1, T+2)
• Unit cost per transaction and per notional dollar
• Replication package: every score traces to a primary BIS, central bank, or attestation source

Method

1. Step 1. Lock the counterparty cohort. Define the named jurisdictions, currencies, and sanction-list overlays.
2. Step 2. Pull throughput. SWIFT FIN traffic counts, CIPS direct and indirect participant volume, mBridge pilot volumes, BRICS Pay attestations.
3. Step 3. Score sanction durability. Apply the OFAC, EU, and UK sanction-list overlay and a forward sanction-tightening scenario.
4. Step 4. Map the counterparty network. Direct participants, indirect participants, correspondent network reachable, custodial banks accessible.
5. Step 5. Score settlement finality. RTGS rails (RTP, FedNow, TIPS, T2, CHAPS) versus deferred net settlement.
6. Step 6. Compute unit cost. Per transaction fee and per notional dollar, including FX conversion and correspondent fees.
7. Step 7. Combine into a weighted CBPS score with explicit weights (default 25/25/15/15/10/10 for throughput, sanction durability, counterparty network, finality, regulatory clarity, cost).
8. Step 8. Output replication package and stress scenarios.

Assumptions

• BIS CPMI Red Book is the canonical throughput reference for established rails.
• Stablecoin reserve attestations are accepted at face value subject to attestor scope.
• Sanction durability scoring assumes current OFAC, EU, and UK list scope plus one forward scenario.

Limitations

• INSTEX and BRICS Pay disclosures are partial; CBPS reports a wider band for these rails.
• mBridge throughput is pilot-stage; production scale carries forward-looking uncertainty.
• Settlement finality on cross-rail transactions depends on correspondent legs.

Example application

Applied to BRICS Pay messaging plus Russian payment rerouting through CIPS and Yuan-corridor banks in Hong Kong, Singapore, and Dubai post-sanctions. The framework scores SWIFT, CIPS, BRICS Pay, INSTEX, and stablecoin rails on the six axes for Russian counterparty payment in 2024 to 2026, and produces a sanction-durability stress test under a BRICS Pay scaling scenario. See BRICS Pay and the 2026 settlement architecture.