Many institutions. One connected possibility.
A clearing and coordination layer that makes bilateral correspondent relationships work in both directions — connecting the services, infrastructure and strengths of participating banks and FinTechs.
A clearing centre for a connected financial world.
Financial institutions already have valuable capabilities. The problem is how often those capabilities remain isolated: local routes, account infrastructure, financial instruments and liquidity that cannot easily be combined into one efficient service.
SUPA Protocol is our response. It is being built as a shared institutional bus: a place to coordinate financial instructions, clear eligible obligations and activate agreed relationships between participants.
Use the network’s strengths, in both directions.
A participant can bring its own infrastructure to the network and use services contributed by others. Those exchanges take place through explicit bilateral relationships, with each institution retaining control over its counterparties and supported activities.
The aim is to combine complementary advantages into a better result for the final beneficiary. The originating institution keeps its customer relationship while participants contribute the services required to complete the instruction.
Less friction between an instruction and its outcome.
Where appropriate, eligible obligations can be matched and netted before the remaining settlement is routed. Available real-time domestic payment and deposit-transfer schemes are preferred when they can complete the instruction efficiently and within the applicable rules.
Transparency runs through the process: a shared understanding of the instruction, the responsible participants and the execution state. Faster and more economical service should also be easier to understand.
The useful outcome sits beyond any single connection.
An originating institution has a customer instruction. A second participant contributes a local service, while another eligible capability may support the currency or liquidity requirement. The complete outcome depends on those contributions working together, not merely on the first institution sending a message.
SUPA Protocol is intended to coordinate that journey: establish the relevant relationships, clear eligible obligations, connect the remaining execution to a supported route and retain a readable record of the result. The sections below explore each layer in more detail. They explain the network’s direction without implying that every capability, participant or corridor is already active. The objective remains practical: a faster, more economical and more transparent financial service for the final beneficiary.
Different journeys.
A clearer way through.
Your client needs to pay a beneficiary beyond your own local reach.
- 01
Instruct
The originating institution accepts its customer’s instruction.
- 02
Coordinate
Eligible correspondent capabilities and obligations are identified.
- 03
Execute
The responsible provider uses an appropriate supported route.
- 04
Confirm
Participants receive the outcome and can reconcile the instruction.
Participating institutions need to settle eligible obligations efficiently.
- 01
Establish
Participants identify obligations under their agreed relationships.
- 02
Clear
Eligible obligations are matched or netted where supported.
- 03
Settle
The remaining amount moves through an agreed settlement arrangement.
- 04
Reconcile
The settlement outcome is connected to the original obligations.
An agent prepares an instruction on behalf of an accountable business.
- 01
Authorise
A principal gives the agent a limited, reviewable mandate.
- 02
Prepare
The agent prepares a supported instruction within its permissions.
- 03
Review
Policy and approval checks determine whether it may proceed.
- 04
Record
The enabled service returns an outcome linked to the principal and authority.
Illustrative workflows. Each service requires the relevant permissions, agreements and enabled capabilities.
Good questions.
Clear answers.
Is SUPA Protocol just another payment rail?
Its intended role is broader coordination: activate bilateral relationships, connect complementary services and clear eligible obligations before settlement through appropriate arrangements.
Does the protocol become the customer’s bank?
This overview does not claim that role. Participating institutions retain their service responsibilities and the originating institution retains its customer relationship.
What determines whether an instruction can use the network?
The relevant institutional relationships, permissions, service coverage and enabled integration must support the particular instruction.
Explore this world.
Connect the relationship. Clear the obligation.
Explore
A shorter path to the beneficiary.
Explore
An instruction should not disappear into a chain.
Explore
Connect to what another institution does best.
ExploreFollow the instruction all the way through.
Explore
A shared network. Clear responsibilities.
Explore
Connect the rails. Preserve what makes them useful.
ExploreSUPA 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.