The instinct when building payments is to pick the rail that will win and build deeply into it. Adapter thinking inverts this. It assumes plural rails, stable interfaces and a neutral layer in the middle — so that the arrival of a new protocol is a configuration change, not a rebuild.
Plural rails, one boundary
Cards, local instant payment schemes, SWIFT, stablecoins and agent protocols such as x402, ACP, AP2/UCP and MPP each move value in a different way, for a different purpose, in a different jurisdiction. None of them is close to absorbing the others. Treating each as a plug-in behind a common boundary keeps their differences where they belong — in the adapter, not in the core.
What the core should do
If every rail is an adapter, the core stays simple: validate an operation once, net what offsets, route the remainder, and keep a ledger. SUPA's six layers follow this shape — inputs, legitimacy validation, order book, ledger, AI routing and rail adapters — with routing weighing cost, settlement time, reliability and regulatory fit across whichever paths are available.
Because the core does not assume a particular rail, it does not have to be rewritten when one changes, and a new option can be added without disturbing what already works.
Interfaces that outlast rails
For developers, the practical value is interface stability. An instruction can arrive from a human interface, from an agent through API, OpenAPI and MCP, or from an institution through ISO 20022, and the internal path does not have to be rewritten when a rail changes underneath. Ledger attribution to principal, agent and policy version persists regardless of which adapter carried the flow.
That is what neutrality buys: the ability to add the next protocol without betting the architecture on it.
In short
- Assuming plural rails is more durable than betting on one winner.
- Adapters isolate each rail's differences from the core.
- The core validates, nets, routes and records.
- Stable interfaces mean new protocols are configuration, not rebuilds.
Build on the adapters at /developers/.