An instruction should not disappear into a chain.
A common operational picture helps participants understand what is happening, who is responsible and what needs attention.
Connect the instruction to its history.
Financial operations often cross organisational and technical boundaries. Without a consistent record, each party may see only its own fragment of the process, leaving the customer with an incomplete explanation.
SUPA Protocol is designed to connect the originating instruction, the involved participants, the relevant approvals and the resulting execution state. For agent-led activity, that context also includes the principal and the agent’s authority.
Make exceptions visible.
An instruction may need more information, encounter an unavailable route or fail a participant’s requirements. These are operational states that need a responsible party and an understandable next step.
Shared status and clear hand-offs are intended to help institutions resolve those situations. Transparency is valuable not only when everything succeeds, but when a team must explain and repair an interrupted workflow.
Share what is needed, not everything.
A connected network is not an invitation to expose every participant’s customer data. Access must follow the purpose of the service, the authorised relationship and the applicable data requirements.
The design principle is appropriate visibility: the information needed to perform and verify the service, with responsibility and access boundaries intact. Trust comes from explicit controls as well as a clearer operational record.
See the hand-off that needs attention.
An instruction crosses an institutional boundary and pauses for review. A useful operational view should show the relevant condition and the responsible party, without suggesting that the task has already completed. The originating institution can then ask the right question and give its customer an accurate update.
The same connected record is useful after completion. Participants can associate the confirmed result with the original instruction and understand the approvals or exceptions that affected it. Access to that history should follow the purpose and permissions of each role. SUPA’s transparency principle is therefore both operational and selective: make responsibility and progress understandable, while avoiding unnecessary exposure of another institution’s customer information.
Good questions.
Clear answers.
Does transparency mean public transaction data?
No. The design concerns appropriate operational visibility for authorised participants, not a public record of customers’ financial activity.
Does each participant see the same information?
Not necessarily. Views should reflect the institution’s role, service purpose and permitted access.
Why keep intermediate states after completion?
They help explain the journey, resolve enquiries and connect the final outcome to the instruction and authority that produced it.
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.