Holding a buffer in every currency and country is the treasury equivalent of buying insurance you never cancel. The balance is there for a payment that may never come, and it sits idle in the meantime. Liquidity-as-a-subscription asks a different question: instead of owning buffers everywhere, can a participant subscribe to the liquidity it needs, when it needs it?

From stock to service

Prefunding is a stock approach — hold enough everywhere to be safe. A subscription model treats liquidity as a service: access to a pool, drawn when required, sized to actual operations rather than to worst-case habit. The shift matters most for groups with many corridors. Instead of duplicating buffers across dozens of accounts, they hold access to shared capacity and pay for what the flows require.

Where this comes from

This is a later stage of the protocol, not a current product. SUPA's roadmap moves through a zone phase, where units run on licensed partners' rails; a principal phase, where it buys capacity on its own licences and builds direct correspondent relationships; and a hub phase, where institutions hold correspondent accounts and sign the multilateral reliance agreement. The final phase envisions the network becoming a shared balance sheet of participants — an intraday liquidity market, liquidity subscription and guarantees. Today, balances sit with licensed partners; SUPA is not a bank and does not take deposits.

What has to be true first

Subscription liquidity depends on netting and routing being reliable enough to trust. If offsetting flows cancel internally and the remainder is routed well, the amount a participant must hold outright falls, and shared capacity can cover the rest. Governance carries the design: limits and approval thresholds sit below the model, over-limit operations become human approval requests, and every draw stays traceable to a principal, an agent and a policy version. This is general information, not financial advice.

In short

  • Prefunding is a stock approach; subscription is a service approach.
  • Shared capacity targets duplicated buffers across corridors.
  • It is a later roadmap phase, not a live product today.
  • Netting, routing and governance are prerequisites.

Follow how the roadmap develops → /investors/