Bring a capability. Open a conversation.
Tell us what your institution does best and what you would like to access through the network.
Find the complementary fit.
Start with the service you want to offer or the customer problem you want to solve. It might be local payment reach, account infrastructure, foreign exchange, liquidity or another supported financial capability.
We discuss the institution behind the service, the markets it supports and the relationships required. The goal is a useful fit between participants, not a list of names with no operational connection.
Agree the responsibilities.
Institutional participation depends on appropriate due diligence, commercial and operational agreements, permissions and risk review. Each party must understand its own responsibilities and the conditions under which another participant may use its services.
We also establish the information needed to originate an instruction, the acceptance and exception process, and how the participants will reconcile the outcome.
Integrate around a real use case.
A defined service flow gives the integration a practical starting point. Technical work can then be evaluated against an expected outcome, including unsuccessful and exceptional cases.
Network expansion is staged. An introductory conversation is not confirmation of a live corridor or an activated correspondent relationship; these are established as part of the participation process.
Start with a service both sides can understand.
An introductory discussion is most useful when it connects a real capability to a real requirement. Describe the service your institution can contribute, or a customer journey that currently depends on fragmented arrangements. Include the relevant operational boundaries and the team responsible for delivery. This helps distinguish an actionable integration from a broad expression of interest.
From that starting point, we can examine the prospective relationships, service conditions and information required. Technical work follows an agreed scope, including how the institutions will recognise completion and handle exceptions. The participation process is intended to create a working relationship that can develop over time. It is not an automatic admission mechanism, and a first conversation does not commit either party to providing a financial service.
Good questions.
Clear answers.
What should we send initially?
A concise institutional introduction, the service you offer or need, its relevant markets and a proposed operational contact. Detailed diligence materials can follow through the agreed process.
Does an introductory call activate a corridor?
No. A corridor or service is enabled only after the appropriate agreements, permissions, integration and readiness checks.
Can we begin with one capability?
Yes. A focused initial scope makes responsibilities and outcomes easier to establish. Further services can be assessed as the relationship develops.
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.