Make local strength travel further.
Connect correspondent relationships to a shared operational layer, and bring the strengths of other institutions to your own customers.
Extend reach without rebuilding every market.
Serving an international customer often depends on capabilities outside a bank’s own footprint. The challenge is not only finding a correspondent. It is understanding what the relationship can deliver, how to route an instruction and how to follow its outcome.
SUPA is developing a common environment for those interactions. Participating banks can combine their own infrastructure with eligible account, payment, FX and liquidity services offered by other institutions.
Activate two-way correspondent relationships.
A relationship should be useful in both directions. Your institution can provide local expertise and access while drawing on another participant’s strengths when a client needs a service beyond your own reach.
Agreements, risk decisions and responsibilities remain explicit. The protocol coordinates the operational exchange; it does not remove a bank’s right or obligation to decide which counterparties and activities it supports.
Improve the route. Preserve the relationship.
Where available and appropriate, local real-time schemes can form part of a shorter path to the beneficiary. Clearing eligible obligations before settlement can also reduce unnecessary movements of liquidity.
Our focus is the complete service outcome: execution clarity, effective use of funds and competitive delivery. Your customer remains your customer, with your institution responsible for its own service and commitments.
Your client needs reach. You bring the relationship.
A business customer asks its bank to support an obligation outside the bank’s direct local footprint. Another institution has a relevant service for that destination. The practical challenge is to connect the customer instruction, the institutional agreement and the local execution into one understandable journey.
SUPA’s intended contribution is a shared operational layer for that interaction. The originating bank retains its customer relationship; the participating provider contributes its eligible capability. Both need to understand their responsibilities, the state of the instruction and the evidence required to close it. This can create a more useful correspondent relationship, including opportunities in the opposite direction. Actual service availability follows the institutions’ agreements and integration, not the mere presence of a network connection.
Good questions.
Clear answers.
Do we lose control over counterparties?
No. The bank retains its counterparty decisions, obligations and service approvals. The protocol coordinates relationships that the relevant institutions have agreed.
Must we replace existing correspondent arrangements?
The focus is on making eligible relationships work through a common operational layer. The appropriate fit with existing arrangements is assessed directly.
Are all routes real-time?
No. Local real-time capabilities are used where eligible and suitable; the complete route still depends on its funding, provider and service conditions.
A closer look.
SUPA Protocol is an institutional network under development. Participation and service availability are subject to bilateral agreements, integration, regulatory permissions and corridor coverage.
Where could we take you?
Tell us what you want to build, connect or make possible.