More ways to complete the payment.
For EMIs, payment institutions and payment service providers seeking complementary reach, clearer execution and stronger institutional connections.
Close the gaps between services.
Payment institutions often have a well-developed customer experience and a strong core corridor. Expansion creates a different problem: new local partners, fragmented operational information and liquidity tied to separate arrangements.
The SUPA network is designed to make complementary capabilities easier to coordinate. An institution can seek an eligible local route or financial service from another participant without treating every connection as an entirely separate operating environment.
Bring your own advantages to the network.
Participation is not only about consuming services. A supported payment corridor, local scheme access or specialist operational capability may be valuable to other institutions serving different customers.
The services you offer, their eligibility conditions and the relationships through which they are used remain subject to your approvals. Sharing infrastructure should support your business, not compromise its controls.
Make exceptions easier to resolve.
A payment journey needs more than a submission response. Institutions need to know whether an instruction is accepted, requires further information, has been executed or has failed.
A shared operational record is intended to reduce ambiguity between participants. Clear responsibilities and status information can help your team explain the outcome to its customer and resolve issues with the right counterparty.
Give your operations team a clearer next step.
A payment institution receives a customer enquiry about an instruction that has not reached the expected outcome. If each provider only exposes its own fragment, the operations team must reconstruct the journey before it can answer. That work can be as frustrating as the original interruption.
The protocol’s design connects the relevant instruction states and responsibilities across participants. If a receiving institution needs information, the originating team should be able to identify that need and the appropriate hand-off. Once the supported service returns its result, the record should connect it back to the customer request. The aim is more understandable operations, including when the journey needs attention. Exact states and information exchange are agreed for each enabled service.
Good questions.
Clear answers.
Can we contribute a specialist payment capability?
Yes. A supported corridor, local access or another relevant service can be discussed as a contribution to the developing network.
Does participation remove funding requirements?
No. Liquidity, limits and settlement conditions remain part of the relevant service arrangement.
How are operational exceptions handled?
Participants agree the information, responsibilities and service states needed to identify and resolve exceptions during integration.
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.