Why This Exists
The payment system works. It just doesn't work for you.¶
Sending money is still surprisingly hard¶
If you have ever received payment from another country, sent an international transfer, or integrated a payment gateway into an online store, you have probably encountered at least one of these:
- Settlement delays of one to three business days — your money is sitting somewhere, but it hasn't arrived yet, and no one is entirely sure why.
- Fees paid to invisible parties — card networks, issuing banks, acquiring banks, correspondent banks. Each takes a small cut, and not all of them are listed on the invoice.
- Chargebacks and disputes — the payment can be reversed, weeks after the transaction, by a third party you have never spoken to.
- Geographic restrictions — certain payment methods simply don't work in certain countries, without clear explanation.
- Identity requirements — accepting or sending certain payment types requires account verification, KYC, and regulatory onboarding that can take weeks.
These aren't edge cases. They are structural features of the dominant payment architecture — one that was designed decades ago and has been incrementally patched, not fundamentally rethought.
The structural problem¶
The dominant model of payment authorisation today is one of delegated trust. A user instructs a financial institution, which in turn authorises a payment on their behalf. At no point in this flow does the payment itself carry a verifiable proof of the payer's consent. The proof lives in the intermediary's records.
This architecture works. Billions of transactions happen daily. But "works" is different from "optimal."
When the authorisation record lives in an intermediary's database rather than in the payment itself, some predictable consequences follow:
⏳
Settlement takes time because of intermediaries¶
The card issuer, processor, and acquiring bank all need to reconcile before funds move. Settlement in minutes is technically possible. Most networks choose days because that's how the economics work.
🔀
Reversals are possible because authorisation is centralised¶
Chargebacks exist because the payment network, not the payer, is the final authority on whether a transaction happened. This creates a dispute industry estimated to cost merchants billions annually.
💸
Fees accumulate because each layer extracts value¶
Every intermediary in the settlement chain earns a margin. Most merchants accept this as an unavoidable cost of doing business. It is avoidable.
🌐
Cross-border transfers are hard because banking relationships are local¶
Correspondent banking networks were built for bank-to-bank relationships, not person-to-merchant or person-to-person global transfers. They are expensive to maintain and slow to use.
What merchants experience¶
A customer pays. The merchant doesn't see the funds until the following business day — or later if the transaction crosses a weekend or holiday. Cash flow planning becomes an exercise in guesswork.
For international merchants, delays can extend to three to five business days and involve currency conversion at rates set by the processor, not the market.
A chargeback can be filed weeks after a sale. The merchant must respond with evidence. The card network reviews it. Often, the merchant loses — and pays a dispute fee on top.
In digital goods and subscription businesses, fraudulent chargebacks are a significant operating cost that is baked into pricing and passed on to honest customers.
A typical card transaction costs between 1.5% and 3.5% of the transaction value, plus a fixed per-transaction fee. For international cards, add a cross-border fee. For currency conversion, add a spread.
Merchants accept these fees because there is no alternative that reaches the same customer base. Until now.
Payment gateways don't work in every country. Some payment methods are restricted by geography, currency, or regulatory status. Merchants who want to serve global customers must integrate multiple providers and maintain complex routing logic.
What payment processors experience¶
Payment processing is a competitive, margin-compressed business. The dominant revenue model — a percentage of each transaction, shared with card networks and issuing banks — leaves less room every year.
New entrants face high barriers: card network certifications, banking partnerships, capital requirements, and regulatory frameworks that differ in every jurisdiction.
And yet, the payment infrastructure itself — the ability to move money reliably — is increasingly a commodity. The real opportunity is in the value built on top of that infrastructure: merchant relationships, analytics, embedded finance, treasury services.
The Stablecoin Stack changes the infrastructure economics so that processors can focus on where the real value is.
What the alternative looks like¶
The Stablecoin Stack is not a patch on the existing system. It is a different approach: payment authorisation that lives in the payment itself, not in an intermediary's database.
When the payer's cryptographic signature is the authorisation — and the settlement is executed by an open, auditable contract on a distributed network — the structural inefficiencies listed above become optional, not mandatory.
The key insight
A cryptographically signed payment commitment is a piece of data that carries its own proof of authenticity. It does not require a third party to vouch for it. The payer's intent is encoded in the data itself, bound to the specific parameters of the specific payment, and unforgeable without the payer's key.