A shared network. Clear responsibilities.
Useful institutional collaboration begins with knowing the participants, agreeing the service and respecting the information boundaries around each relationship.
Trust is more than a technical connection.
A working interface does not, by itself, establish a financial relationship. Institutions need to understand their counterparties, the services being offered and the responsibilities that remain with each party. Those foundations determine whether a network connection can support a customer instruction.
SUPA Protocol is being developed around explicit participation and bilateral service relationships. The coordination layer helps institutions work together, but does not replace their due diligence, approvals or regulatory obligations. A useful network connects responsible participants, not anonymous capabilities.
Share information for a defined purpose.
Repeated requests for the same information can create operational friction. At the same time, an institution cannot assume that information gathered for one relationship may be freely disclosed or relied upon in another. Purpose, permission and the applicable requirements matter.
SUPA’s design direction supports appropriate coordination of information within the agreed service workflow. What can be shared, by whom and under which conditions must be established for that relationship. The aim is better continuity of relevant context without a blanket promise that one onboarding process satisfies every institution.
Keep authority close to the service.
Each participant needs control over the capabilities it offers and the instructions it accepts. Service conditions, customer eligibility and operational review remain meaningful even when a network makes the technical interaction easier.
A common coordination layer should make those boundaries easier to follow. Participants need to know which provider is responsible for the next step and what evidence supports the returned outcome. Transparency helps institutions collaborate while retaining the controls appropriate to their own role.
Build participation as an ongoing relationship.
An institutional relationship changes over time. Services can be introduced or withdrawn, operational contacts can change and an incident can require a coordinated response. Participation therefore needs a lifecycle, not merely an initial connection.
During partner discussions, we work through the proposed service scope, review responsibilities and operational processes. Detailed participation terms are agreed privately with the relevant institutions. This website describes the governing principles of the developing network, not a final rulebook or a substitute for those agreements.
A capability becomes usable through a relationship.
Two institutions identify a complementary service opportunity. Before connecting a live customer journey, they establish who provides the service, which instructions are eligible, what information is required and how exceptions will be managed. The technical integration reflects those agreed boundaries.
As the relationship develops, the participants can review the scope and consider further capabilities. SUPA’s role is to support that coordinated interaction, with responsibility remaining visible throughout. Network membership alone does not remove the need for an appropriate service relationship.
Good questions.
Clear answers.
Does network participation replace our due diligence?
No. Institutions retain their own obligations and approval processes. Any permitted use of another party’s information must be agreed and assessed appropriately.
Will all participants see our customer information?
No. Information access should follow the specific service purpose, permissions and relationship, rather than broad network visibility.
Where are the detailed participation terms?
They are discussed directly with prospective institutional participants. The public website provides an overview, not the final legal or operational agreement.
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.