Digital money comes in more than one form, and the two most discussed — tokenised deposits and stablecoins — are often compared as if one must replace the other. They are better understood as instruments with different origins and different jobs. For an institution deciding how to settle cross-border value, the question is not which is superior but which is appropriate to the operation in front of it.
Two origins
A tokenised deposit represents a claim on a bank balance, represented digitally. It originates inside the banking system, and its credibility rests on the institution holding the underlying deposit. A stablecoin is issued against reserves and circulates on a network rather than inside a single bank's balance sheet. It travels further and faster across institutional boundaries, but it depends on the issuer's reserve arrangements and on the regulatory treatment of the issuer itself.
Neither is a substitute for the relationships between institutions. Money does not move between two parties because a token exists; it moves because an institution somewhere accepts the obligation to settle. That is why SUPA's design treats digital assets as one class of rail among several, rather than as the foundation of the system.
What each is good for
- Tokenised deposits suit operations where counterparties already sit inside the regulated banking perimeter and want settlement to stay there.
- Stablecoins suit operations that must cross networks or jurisdictions quickly, where a licensed digital-asset provider can execute the leg.
- Neither replaces the identity, mandate and compliance work that must accompany an operation.
Where the hub fits
In SUPA's model, both forms are reached through the same layers. Legitimacy validation checks each operation once: reliance confirmation, sanctions screening, agent mandate, client-profile fit and network anomaly signals. AI routing then weighs every path by cost, settlement time, reliability and regulatory fit, so the rail is chosen per operation rather than by preference. The ledger records every movement in double entry, attributed to principal, agent and policy version.
In short
- Tokenised deposits and stablecoins have different origins and different jobs.
- Both depend on institutions willing to settle.
- Rail choice should be made per operation, not by default.
- Licensed providers should execute digital-asset legs.
- One compliance and routing layer can serve both forms.
For how these rails sit inside institutional design, see /institutions/