Words carry obligations. Calling a routing layer a bank implies deposit-taking, balance sheets and a particular set of duties and protections. SUPA is not a bank, and the difference is not semantic — it shapes what the system does, who holds the money and where responsibility sits.

What a bank does

A bank takes deposits in its own name and holds client money on its balance sheet. That capacity is licensed, supervised and closely defined. Until SUPA holds a banking licence, it does not do this: it does not take deposits and does not hold client money in its own name. Balances sit with licensed partners. Anyone assessing the system should read it with that boundary firmly in mind.

What a protocol does

A protocol layer connects participants and sets rules. It validates operations once, keeps an order book and a ledger, routes the remainder to the best path, and defines how institutions rely on one another. Its role is to make the connections work, not to stand in the middle of every balance.

SUPA operates in this way today, as a virtual special economic zone where a person or an AI agent can register an isolated business unit and get a working financial perimeter in minutes, running on licensed partners' rails. The long-term goal is to rebuild how correspondent relationships work — a hub holding correspondent accounts for institutions rather than each opening accounts everywhere — but the licence and the role are separate questions with separate timing.

Why neutrality follows

Because the layer does not compete with participants for their clients, it can sit between institutions that are also competitors. Clients stay clients of their own bank or fintech. The hub holds accounts for institutions rather than selling to their customers.

This article is general information, not legal, tax or financial advice.

In short

  • A bank takes deposits and holds client money in its own name; a protocol layer does not.
  • Before a banking licence, SUPA holds balances with licensed partners.
  • The protocol's job is to connect, validate, net and route.
  • Neutrality lets it serve institutions that compete with one another.

Read the structural argument at /about/.