A cross-border payment is not one transfer. It is a sequence of transfers between institutions, each of which has to know who it is dealing with and be permitted to deal with them. Stablecoins shorten the sequence. They do not remove the institutions at either end.
Banks do not have accounts everywhere. To send money to a country where it has no presence, a bank uses another bank that does, and sometimes that bank uses a third. Each hop is a real transfer between two institutions that hold accounts with each other, and each one applies its own checks before passing the value on.
The cost and the delay are the checks, not the arithmetic. Every intermediary re-screens the parties, re-applies its own sanctions and risk policy, and may hold the payment while it asks a question. A chain of three or four such hops explains most of what people mean when they say international payments take days.
It also explains the quiet failure mode: correspondents withdraw. When a bank decides a whole country or customer type is not worth the risk, the route disappears, and the economies on the far end lose access rather than merely paying more.
The middle collapses. The ends do not
This is what a stablecoin-settled cross-border payment actually consists of, written out. Steps 03 to 05 are the part people picture. The rest is where the work is.
It is tempting to read the collapse of the middle as a reduction in compliance. It is the opposite: the same obligations are now concentrated on fewer parties, and those parties are the ones holding a licence at each end.
The institution has to know its customer, and increasingly something about its customer’s counterparty. Passing information about originator and beneficiary along with a transfer is a requirement in most major regimes, not a courtesy.
Funds held for customers are not the firm’s funds. They are safeguarded, usually at a separate institution, and must survive the firm failing. This is the single most consequential rule in payments and the one most often discovered late.
Holding one pot of money on behalf of many end users, in a structure that does not give each of them their own recognised account, is the arrangement that turns a software company into an unlicensed deposit-taker. Each end user typically needs their own verified relationship.
Two regimes are worth reading directly rather than in summary: the European Union’s markets-in-crypto-assets regulation, which sets out what a crypto-asset service provider may do and what a stablecoin issuer must hold in reserve; and the United States’ federal stablecoin legislation, which defines who may issue a payment stablecoin and on what backing. Both are about the issuer and the service provider — neither makes the end user’s own obligations disappear.
Steps 02 through 07 can be presented through one interface, with one record, and without the customer assembling four vendors. What cannot be collapsed is who is permitted to hold the money at each end — that remains a licensed institution, and the technology layer is its distributor rather than its replacement.
Business verification, accounts that receive local currency, the conversions in both directions, per-customer attribution, foreign exchange and payouts are implemented at skerry.xyz. Skerry provides the interface and the record; the accounts, conversions and payouts themselves are performed by its regulated partners, and the verification a business completes is verification with those partners. Skerry is not a bank and does not hold a licence of its own. The obligations in section 03 sit with the partners and with the customer’s own business, not with the software.