Every digital-asset operation needs an executor somewhere: an entity that actually moves the token and bears responsibility for doing so properly. In a well-designed network that executor is a regulated provider. Understanding what these providers contribute — and where they sit in the architecture — clarifies why a network should include them rather than work around them.
Executors, not competitors
A regulated digital-asset or stablecoin provider is one class of participant in the same network as banks, electronic money institutions, payment institutions, money services businesses, card issuers and acquirers, and local rail providers. They are not rivals to be displaced. In SUPA's design, participants are simultaneously trust providers, flow receivers, executors and users of the hub. A digital-asset provider plays the executor role for the legs that need it, while remaining a client-serving business in its own right — SUPA does not compete with participants for their clients.
What they contribute
- A licence and a supervisory relationship, providing an accountable party for the leg.
- The operational capability to convert and move digital assets, and to pay out onto local rails.
- Defined responsibilities that can be relied upon under a codified agreement.
- Records that allow an operation to be reconstructed.
How they fit the layers
Digital-asset providers appear in the rail-adapter layer, the sixth of SUPA's six layers. By the time an operation reaches them, it has already passed legitimacy validation — reliance confirmation, sanctions screening, agent mandate, client-profile fit and network anomaly signals — and been routed by cost, settlement time, reliability and regulatory fit. Over-limit operations become a human approval request rather than a rejection. The ledger then records the resulting movement in double entry, attributed to principal, agent and policy version.
In short
- Digital-asset operations need an accountable executor.
- Regulated providers supply that role, not a workaround.
- They sit alongside other participants, not in opposition to them.
- Validation happens once, before the provider executes the leg.
- Records tie the leg back to a principal and an agent.
For how participants fit together, see /institutions/