Stablecoin Payments and the Correspondent Bank Problem

Stablecoin payments promise faster, cheaper cross-border settlement, but a November 2, 2026 essay by Richard Beverley, CEO and co-founder at Block Infrastructure, asks a sharper question: if every country issues its own stablecoin, do you get a cleaner rail or a brand-new correspondent layer? Published in Financial IT, the piece reframes the debate around fragmentation rather than transaction speed. This article tests that thesis with OneSafe’s published fee schedule, the treasury policy required when counterparties settle in different stablecoins, and the reconciliation work stablecoin settlement does not remove.

Table of Contents

• What just happened: correspondent banking is back on the table
• Why this matters now for founders and finance leads
• The background a newcomer needs in 60 seconds
• Where the consensus breaks down
• The fully loaded cost of a stablecoin payment
• What happens to correspondent banking if every country has its own stablecoin?
• Are stablecoin payments actually cheaper than wires once conversion is included?
• Do stablecoin payments remove the need for banks?
• Which stablecoin should my business accept or hold?
• How do I book and reconcile stablecoin payments in my accounts?
• What should I check before adding a stablecoin payment corridor?
• What does 'ready to launch a stablecoin strategy' actually require?
• What to do now
• What to watch next and open questions
• Key Takeaways

What just happened: correspondent banking is back on the table

The claim, attributed: cost, delay and uncertainty persist across borders

In “What Happens to Correspondent Banking If Every Country Has Its Own Stablecoin?”, Beverley argues that the foundational cross-border problem—moving money outside domestic banking hours, across time zones and between currencies—remains unchanged. Every additional institution or thinly traded currency compounds cost, delay, and uncertainty. The essay raises the prospect that a patchwork of national stablecoins could replicate the correspondent banking webs they were meant to bypass by adding conversion requirements and settlement dependencies at every border.

What the piece does not say—no new rule, no new product, no data release

The piece is an argument, not an announced regulation or product launch. It advances a thought experiment about what happens when the simplifying logic of a single globally accepted stablecoin collides with sovereign digital currencies. For finance and operations teams evaluating stablecoin payments for business, that experiment lands where vendor marketing often stops: the conversion edges.

Why this matters now for founders and finance leads

The rail you adopt this quarter becomes next year’s reconciliation problem

If you’re a global startup or DAO adding a stablecoin payment corridor today, the infrastructure choices—which stablecoin to hold, how to off-ramp, which ledger to map receipts to—will harden into operational overhead. As more jurisdictions issue their own stablecoins, counterparties may demand settlement in their local token, not yours. Treasury then has to handle multiple stablecoin balances, frequent conversions, and per-token redemption rules, even if the on-chain leg stays cheap.

Which of your payment corridors are actually exposed to the fragmentation argument

Not all corridors are equal. Paying US-based contractors in USDC from a US entity barely touches the issue. Settling with suppliers in markets that might launch a domestic stablecoin—Brazil, Japan, or Eurozone digital euro experiments—can multiply conversion decisions per payables run. Stablecoin regulation: the OCC’s 2027 deadline adds a US rulemaking timeline that could alter what “payment stablecoin” means for domestic entities.

The background a newcomer needs in 60 seconds

How a cross-border payment moves today, hop by hop

A typical international wire travels through correspondent banks. The originating bank sends a SWIFT message; intermediaries debit and credit each other, taking fees and time; the beneficiary’s local bank converts currency and deposits funds. Every hop introduces cost, delay, and compliance-review risk.

What a payment stablecoin is—and what ‘one per country’ would change

A payment stablecoin is a fiat-pegged token, typically 1:1 with a reserve currency, transferred on a blockchain. Sender sends tokens to the receiver’s wallet; settlement finality is measured in seconds. For a business-oriented primer, see Stablecoin Payments Explained: A Guide for Businesses. If one globally trusted stablecoin circulates, hops drop. If each country issues its own—backed by its own reserves and redemption rules—the on-chain transfer may still be fast, but sender and receiver face a conversion step whenever tokens differ. Hops move from correspondent banking to stablecoin-to-stablecoin or stablecoin-to-fiat conversion.

The regulatory frame most coverage uses, and why a US definition is not a global one

Much commercial content anchors “payment stablecoin” to US legislative proposals such as the Clarity for Payment Stablecoins Act. As earlier analysis of stablecoin regulation: the “Walling Off” warning explains, non-US issuers operate under different reserve, redemption, and recognition rules. For a US-specific overview, see Stablecoins explained: what US business owners need to .... Treating a stablecoin as a uniform instrument across borders is a mistake.

Where the consensus breaks down

Fewer hops vs. more edges: settling the efficiency argument

Commercial pages sell stablecoin payments as removal of intermediaries. Beverley flips the question: the on-chain leg gets simpler, but counterparties and conversion decisions do not necessarily fall—the work migrates to the edges. Both statements are correct. Cross-border stablecoin settlement collapses the correspondent chain into a blockchain transfer, but the moment you and your counterparty hold different stablecoins, you’ve recreated a conversion requirement at the border. The efficiency gain depends on whether the ecosystem converges on one or two dominant instruments.

One ‘payment stablecoin’ category or a per-jurisdiction patchwork?

Treat “payment stablecoins” as a family of instruments, not a guarantee of equivalence. For a USDC corridor, you can rely on transparent US reserves. For a foreign sovereign stablecoin, verify redemption terms before accepting it as settlement.

Rail cost vs. fully loaded cost

Marketing pages often quote only the blockchain transfer fee—cents or free. Operators absorb conversion spread, off-ramp fees, and local payout charges. Compare fully loaded cost per payment, not transfer fee per transaction.

The fully loaded cost of a stablecoin payment

What the rail costs: OneSafe’s published schedule for USDC transfers, fiat deposits and withdrawals, wires and SWIFT

Below is a like-for-like comparison of sending $10,000 from a US-based business to a European supplier using OneSafe’s publicly listed pricing, which includes ACH, wires, SWIFT, crypto-to-fiat, and FX. (OneSafe is a financial technology company; banking services are provided by its partners.)

The USDC rail itself is free on OneSafe. Savings leak out at conversion and payout. For a straight stablecoin payment from one on-chain wallet to another, cost is negligible. The moment you need fiat—and most businesses do—the bill rises.

What the edges cost: FX conversion and card FX

Foreign exchange is the silent budget killer. OneSafe’s FX fee on standard conversions is 0.25%; its corporate card FX fee is 3%. If your vendor accepts stablecoin but you pay via a card-funded crypto off-ramp, the FX mark-up can eclipse the wire fee.

Verdict: the rail is cheap; the conversion and payout are where the budget goes

Cross-border stablecoin settlement can reduce cost by 50% or more versus SWIFT in corridors with efficient off-ramps, but it does not eliminate cost. The treasurer’s job shifts from managing correspondent fees to managing conversion spreads and payout rail selection.

What happens to correspondent banking if every country has its own stablecoin?

The correspondent bank layer does not vanish; it moves to the on-ramp and off-ramp. If a Brazilian issuer creates a BRL-pegged stablecoin and your São Paulo counterparty demands settlement in that token, you must source it or convert your USDC. That conversion likely happens through a liquidity provider, exchange, or crypto-native financial institution—all de facto correspondent intermediaries. The number of institutions may shrink, but numbered accounts, credit exposures, and compliance checks persist at the edge. As the Custodia Supreme Court case for crypto banking access shows, the legal status of those intermediaries is still being defined. You don’t get a brand-new correspondent layer; you get a lighter-weight one that still requires management.

Are stablecoin payments actually cheaper than wires once conversion is included?

Yes—in the right corridor, with the right provider. A $10,000 SWIFT payment costing $85 can be brought down to $40 using USDC and a low-fee off-ramp like OneSafe’s, a savings of 53%. But if your payee’s bank triggers an additional wire, the advantage drops. If you must convert between stablecoins before off-ramping, you add a spread and possibly a liquidity-provider fee. Run the fully loaded cost on your specific corridor, not the rail-only cost.

Do stablecoin payments remove the need for banks?

Not entirely. The blockchain leg disintermediates the correspondent chain, but businesses still need a bank or fintech partner for the fiat on-ramp and off-ramp. The provider also handles compliance—KYC, transaction monitoring, sanctions screening—which a pure on-chain wallet cannot do. Stablecoin payments do not remove banks; they change which banking services you consume and how many you need. A multi-currency business account that natively supports fiat and crypto collapses these functions into one platform.

Which stablecoin should my business accept or hold?

The answer depends on counterparties and treasury tolerance for conversion. As a working policy:

• Hold USDC or another fully reserved, transparently audited stablecoin as your base treasury asset. It is widely accepted and liquid.
• Convert on receipt if a counterparty sends a different stablecoin, unless you have a near-term payable in that token. Holding multiple stablecoins fragments working capital and amplifies reconciliation.
• Pre-fund only payables corridors you run repeatedly. If suppliers demand a local sovereign stablecoin, maintain a small float, but keep core operational cash in one stablecoin.
• Verify redemption terms per issuer. A stablecoin issued under foreign law may have restrictions or FX controls that delay off-ramp.

Stablecoin treasury management becomes essential when you operate across multiple payment stablecoins.

How do I book and reconcile stablecoin payments in my accounts?

Map every stablecoin to a separate sub-ledger currency code with its own functional-currency valuation at the transaction date. When a USDC payment lands:

1. Record the receipt at the USD value at time of credit.
2. When you off-ramp to fiat, recognize realized FX gain or loss against that original value.
3. Keep a reconciliation log with transaction hash, source wallet, and on-chain timestamp—your audit trail.

For DAO treasury payments, controls are more demanding. OneSafe’s platform (which offers customizable roles and permissions for DAOs) lets you set signing authorities and transaction limits per stablecoin. Each sub-DAO or project wallet should be accounted for as a cost center, with stablecoin movements booked to inter-entity accounts if needed. The DeFi compliance after the FBI’s THORChain request illustrates why keeping an on-chain paper trail is non-negotiable.

What should I check before adding a stablecoin payment corridor?

Enterprise teams can use Stablecoin Payments for Enterprise: A Practical Guide alongside these five fiat-leg questions:

1. What fiat deposit and withdrawal fees apply to my corridor—flat, percentage, or both?
2. What FX spread or fee do you charge on conversion, and is it locked at transfer or floating until settlement?
3. Which local payout rails do you use in the destination country, and what are their cut-off times?
4. How do you handle a failed off-ramp? Will funds be returned automatically, and in what currency?
5. What is your policy on frozen or delayed transfers due to enhanced due diligence or sanctions screening?

What does 'ready to launch a stablecoin strategy' actually require?

Readiness is not “we opened a wallet.” It means you have:

• A documented treasury policy specifying which stablecoin(s) you hold, conversion intervals, and authorized signers.
• A test corridor with a known counterparty, benchmarked end-to-end on fully loaded cost.
• A reconciliation procedure mapping each transaction hash to your accounting system, with FX gain/loss rules.
• A custody model (self-custody, platform custody, or institutional custodian) with role-based permissions—especially for multi-entity and DAO structures.
• A regulatory assessment for your corridors, including local licensing requirements for receiving or holding stablecoins.

What to do now

A 30/60/90 sequence for finance teams testing a stablecoin corridor

First 30 days: Identify your top two corridors by volume where SWIFT costs are highest and counterparties accept USDC. Run a single test payment, record fully loaded cost, and document reconciliation.

Days 31–60: If fully loaded cost beats SWIFT by at least 30% and the workflow repeats, draft treasury policy and involve your accountant on bookkeeping for receipts and off-ramp conversions.

Days 61–90: Scale live payables, add a second corridor if successful, and review FX spreads monthly. If new country-level stablecoins emerge in your corridors, assess conversion cost before adopting them.

What to watch next and open questions

Signals that would confirm or kill the fragmentation thesis

• Confirming signals: multiple sovereign issuers launch stablecoins with domestic traction (digital euro, digital yen, Brazil’s Drex equivalent), and counterparties request settlement in those tokens. Cross-stablecoin spreads widen or liquidity thins.
• Killing signals: network effects drive convergence to a single or dual-token B2B standard, making sovereign tokens niche. Auto-conversion at tight spreads makes fragmentation a non-issue at the user level.

Watch the OCC’s 2027 deadline for US bank involvement with stablecoins; it will shape the US on-ramp and off-ramp landscape.

The questions this article cannot answer from the available evidence

• Will sovereign stablecoins include permissioned transfer restrictions that break composability?
• How will cross-stablecoin liquidity pools evolve in a multi-CBDC world?
• What will auditors demand as proof-of-reserves for non-US stablecoin issuers?

To track those shifts, Joyrise plans, writes and publishes illustrated SEO articles to your Webflow blog every day. Read your first article before you pay.

Key Takeaways

• Stablecoin payments do not eliminate correspondent banking; they shift conversion and settlement work to the on-ramp and off-ramp edges, where costs and compliance still live.
• Compare fully loaded cost, not rail-only fees. A template using OneSafe’s schedule shows savings up to 53% versus SWIFT in optimal corridors, but FX and payout fees can erode the advantage.
• Adopt a treasury policy now that designates a single core stablecoin (like USDC) and converts other tokens on receipt, avoiding working capital fragmentation.
• Reconciliation requires a dedicated sub-ledger, transaction-hash audit trail, and role-based permissions—especially for multi-entity and DAO treasury payments.
• Before launching a corridor, ask the five fiat-leg questions and document end-to-end cost, custody model, and bookkeeping flow.

For global businesses and DAOs testing these corridors with a platform that combines multi-currency fiat accounts and crypto capabilities, sign up at OneSafe to see if it fits your operation.