Key takeaways
- The stablecoin sandwich is a core stablecoin payment architecture. Fiat enters through an onramp, stablecoins settle the middle leg, and local fiat exits through an offramp.
- SWIFT still works well on familiar G10 corridors, but stablecoin rails become more compelling when banking hours, FX spreads, correspondent hops, and reconciliation work are part of the cost.
- The three strongest production use cases for stablecoin payments today are cross-border payments, global payroll, and treasury operations.
- Peg stability, security, liquidity, and regulation all need planning, but most risks are controlled through issuer selection, custody design, and provider coverage.
- A single stablecoin API can reduce integration complexity because the full stack includes onramps, custody, wallets, cards, issuance, compliance, and offramps. Stitching those pieces together across vendors recreates the complexity stablecoins are supposed to remove.
On a more difficult route to send money across borders, like US-to-Mexico, a supplier payment sent through SWIFT can hop through two correspondent banks, sit in an overnight batch, and land three days later with fees and a 50 basis-point FX spread deducted along the way.
On stablecoin rails, the same payment converts to USDC, crosses a blockchain in seconds, and arrives as pesos via SPEI within minutes, often with network fees measured in cents.
That second path follows a simple architecture called the stablecoin sandwich. Fiat comes in through an onramp, stablecoins settle the middle leg, and fiat comes out through an offramp.
Stablecoin payments have moved from pilot to production. Cross-border fintechs, payroll platforms, and corporate treasury teams are settling real volume on these rails today. What matters in practice is less the hype and more the plumbing: how onramps and offramps actually work, which local rails your corridor supports on both ends, and the true all-in cost once fees, spreads, and liquidity are accounted for.
What stablecoins are, and why payment-grade stablecoins are a narrow subset
A stablecoin is a digital token built to behave like money. The most common designs track the value of a national currency, usually the US dollar, and are backed by assets such as cash or short-term Treasuries held by the issuer.
Each token equals one unit of the currency it tracks, and you can send it anywhere in the world in minutes. That structure makes stablecoins behave more like fiat than like other cryptocurrencies, whose prices can swing from one hour to the next.
Linking crypto's speed to fiat's stability solves a practical problem with digital currencies: moving money across borders without watching it fluctuate in the process.
Stablecoins make digital transactions predictable. Businesses use them to store value, settle invoices, and pay globally in something that feels as predictable as cash while moving at network speed.
How stablecoins hold their value
Stablecoins hold their peg through collateral and redemption. For every fiat-pegged token issued, the issuer keeps an equal amount of assets in reserve, usually cash, US Treasury bills, or other liquid instruments.
Those reserves are verified through audits or attestations, so users know the tokens are backed. When demand rises, new coins are minted. When holders redeem them for fiat, supply contracts. This convertibility keeps the price anchored.
While some projects use algorithms instead of reserves to manage supply, the most widely used stablecoins today rely on fiat backing because their value is easier to verify, regulate, and redeem.
The four stablecoin categories (and which ones work for payments)
Stablecoins typically fall into four categories, based on what keeps their price stable, and only one category of stablecoins is widely used for real-world payments at scale.
- Fiat-backed stablecoins, including USDC and USDT, are the most common. Each token represents a unit of government-issued currency held in liquid assets such as cash or short-term Treasuries. Because their reserves are easier to verify and redeem, they dominate real-world payment use. Bessemer reports that the global fiat-backed stablecoin supply exceeded $273 billion in March 2026, up 40x from 2020.
- Crypto-backed stablecoins are collateralized by other digital assets. These are often overcollateralized to offset volatility. DAI is a leading example.
- Commodity-backed stablecoins are tied to physical assets such as gold. They blend digital transferability with tangible value.
- Algorithmic stablecoins rely on software rules instead of collateral to balance supply and demand. They're experimental, and their history of depegging has made them less trusted for payments.
In practice, most production payment flows use fiat-backed stablecoins like USDC and USDT. A smaller set of issuer-specific tokens on public blockchains also see usage, but the center of gravity for payment volume is fiat-backed.
How a stablecoin payment actually moves
A stablecoin payment is an end-to-end settlement flow with three layers: an onramp from fiat, an onchain transfer, and an offramp back to fiat. Each layer carries work most explainers skip.
To make the mechanics concrete, let’s walk one corridor end to end: a US company that pays a Mexican supplier, sending USD-equivalent value while the supplier receives MXN in their local bank account.
1. Onramp, fiat in
The payer's USD leaves their US bank account through ACH or wire and lands at a regulated stablecoin issuer or orchestration platform, which mints or sources USDC against the deposit. The dollars are now represented as tokens on a public blockchain.
2. Blockchain rails, value in motion
That USDC travels on a network like Solana or Base, networks that confirm transactions in seconds for fractions of a cent.
Network nodes validate the transfer and include it in a block. No correspondent banks sit in between, and no business-hours window applies. Once the block confirms, settlement is final because there is no additional clearing step.
3. Offramp, fiat out
On the Mexican side, the recipient's provider receives USDC and converts it to MXN. The provider then pays the pesos into the supplier's local bank account via SPEI, Mexico's domestic instant-payment rail. The supplier sees pesos in their account, often within minutes of the sender hitting send.
The onramp and offramp are where local rails connect. In the US, that means ACH and FedWire. In the EU, SEPA. In Brazil, PIX. In Mexico, SPEI. Across Africa and Asia, local banking networks and mobile money rails play the same role.
The middle layer stays the same on every route while the local rail and chain change to match the corridor.
The open sandwich: When funds stay in stablecoins
Not every payment needs both ends of the sandwich. When the recipient is a crypto-native business, a digital-dollar account holder, or a worker in a market where local currency is losing value faster than the conversion fee costs, the payment can end on the stablecoin side.
The funds sit as USDC in the recipient's wallet. The recipient can spend through a stablecoin-backed card, hold digital dollars, or swap to local currency later. This open-sandwich variant removes the second conversion entirely, so the second set of fees disappears with it.
If you're building a neobank or digital-dollar wallet product, start by evaluating this architecture.
Programmability changes payment software
Smart contracts can embed payment conditions directly, adding logic that legacy rails cannot carry natively. For example, funds can release when a shipment is confirmed delivered. One transaction can also split a payment across a dozen suppliers, while the offramp converts to local currency on arrival. For finance teams managing complex multi-currency supplier networks, that programmability removes entire categories of manual intervention.
Programmability defines what a payment should do. Orchestration determines how it gets there.
Orchestration platforms add a routing layer that keeps transfers moving even when conditions change. If USDC on one network becomes congested or unusually expensive, the platform can route the same flow through another network with better throughput and lower fees, then finish by offramping into the recipient’s currency.
Because chain selection happens behind the scenes, the recipient simply sees the payment arrive.
Stablecoin rails vs. SWIFT: Speed, cost, and availability
SWIFT is still the default for cross-border payments at most banks and large enterprises, and on familiar corridors it works well enough that switching costs outweigh the gains. The more useful question for teams evaluating stablecoin rails is where the underlying numbers, settlement time, fees, FX spread, and operating hours, actually change the buying decision.
Federal Reserve analysis identifies the core cost problem in cross-border payments: long correspondent chains, redundant compliance checks, poor tracking, and rent extraction by intermediaries. Stablecoins can compress part of that chain, but the advantage depends on each corridor's local rails, conversion costs, and FX provider.
On a G10 route like USD to EUR, major banks already have deep liquidity, better correspondent coverage, and same-day settlement options during business hours. Stablecoin rails can still reduce network-layer costs and remove banking-hour constraints, but the per-transfer savings are often modest compared with harder corridors. Many corporate treasurers stick with SWIFT here for audit-trail familiarity, and on raw per-transfer cost alone, the case isn't overwhelming.
Stablecoins pull ahead on G10 routes when the operating model matters more than the line-item fee. Friday-night settlement, programmatic payment release when a shipment clears customs, and the removal of batch reconciliation can compound into an operational advantage that the per-transfer comparison misses.
On an emerging-market route like USD to NGN, the picture changes. Fewer direct banking relationships, wider FX spreads, and more manual compliance review make correspondent payments slower and more expensive.
Stablecoin settlement through local liquidity providers can reduce the number of intermediaries, shorten settlement windows, and give recipients a clearer status trail. The savings widen from modest on G10 routes to substantial on emerging-market routes.
Correspondent banking is the complexity stablecoin rails are designed to remove. Every additional intermediary between sender and receiver adds a fee, adds delay, and creates another point where a payment can stall in a sanctions queue or sit in an overnight batch.
Inconsistent sanctions screening across institutions can create false positives at handoffs, pushing investigation and reconciliation work onto downstream finance teams. The stablecoin sandwich replaces that chain with two regulated boundaries, the onramp and offramp, and a public blockchain in the middle.
The 24/7 advantage is easy to overlook. If a US company pays a Singapore supplier on a Friday evening, a SWIFT transfer may not start moving until Monday. On stablecoin rails, the transaction can confirm in seconds, no matter the day or time zone.
For platforms paying creators, marketplaces settling sellers, or treasury teams rebalancing across subsidiaries, rails that don't close mean settling and reconciliation in near real time, releasing payouts on weekends, and rebalancing liquidity the moment it is needed instead of waiting for the next banking window.
Where stablecoin payments win today
Stablecoin payment volume today is concentrated in three use cases, and each maps to a different buyer, flow, and proof point.
Cross-border payments, for fintechs and SMB platforms
If you're a payments lead at a fintech or neobank building remittance, supplier-payment, or virtual-account products for SMBs in markets where the traditional banking stack runs slow and expensive, this is your use case.
The flow is the closed sandwich, with fiat in on the sender's side and fiat out on the recipient's side, on rails that don't close.
Cenoa serves SMBs and solopreneurs in Turkey and Nigeria with virtual USD and EUR accounts powered by Bridge's Virtual Account API and Orchestration.
Customers can onboard in under three minutes. Deposits then convert automatically to USDC and route to user wallets. In nine months, Cenoa onboarded more than 50,000 SMBs, grew transaction volume 50x, and surpassed $10 million in monthly volume. It also reported up to 10x lower overall costs and 80% lower cross-border payment fees than PayPal, Wise, and SWIFT.
Tokens stay pegged to fiat on both sides, so SMBs in markets with currency volatility transact in stable value even when the local currency moves. Because Bridge handles the onramps, blockchain layer, and offramp into local currency, Cenoa added stablecoin rails without becoming a stablecoin company.
Global payroll, for platforms paying distributed workforces
If you lead payments at a platform that pays workers in many countries, you already know payroll is high-frequency and low-value per transaction. That combination makes it especially sensitive to FX spreads and remittance fees on traditional rails.
Remote-work marketplaces, creator-economy platforms, and contractor networks all hit this wall.
Airtm reaches 1.8 million users and offers enterprise customers global payouts to more than 100 million workers using USDC on Stellar. Airtm customers see average cost savings of 20% compared with PayPal or Wise. Bridge's support for US ACH, FedWire, and European SEPA rails let Airtm expand into the US and Europe without costly integrations or regulatory burdens. Additionally, Stellar's wide network of access points handles the last-mile conversion to local currency across Argentina, Venezuela, Colombia, Bolivia, India, Bangladesh, and Nigeria.
Low-fee networks are what make payroll economics work at this scale. When a per-transaction fee runs at fractions of a cent, weekly payments to a large contractor base stop looking like a treasury problem and start looking like a routine API call.
Treasury operations, for enterprise finance teams
If you're a head of treasury or a CFO at a mid-market or enterprise company moving capital between subsidiaries, paying suppliers in multiple currencies, or holding operating cash that earns nothing in a bank, this is the use case that changes how your operating capital sits and moves.
This flow is internal. The money is moving within the same company, or between that company’s own entities, not to a customer. The goal is to rebalance liquidity across regions on rails that can settle in minutes instead of days. In some cases, it also includes issuing a stablecoin that aligns with your product economics.
Dakota is a modern banking platform that issued its own stablecoin, DKUSD, on Bridge's Issuance API with less than a day of development time. Within the first few months, roughly 55% of Dakota's assets had moved into DKUSD. The company expects 80% within a year of launch.
DKUSD is fully backed by US Treasuries and restricted to Dakota's platform so open-market depeg risk doesn't apply, with Bridge managing the reserves. Bridge shares a portion of deposit earnings with Dakota, which changes the economics of stored balances. Every dollar held can generate yield or interchange instead of sitting in a bank account that returns nothing.
Treasury teams also use stablecoins as 24/7 working capital. Holding tokenized fiat across regions mitigates local-currency risk and allows rebalancing outside banking hours. It also replaces pre-funded nostro accounts, the foreign-currency accounts banks maintain at correspondent institutions, with a single stablecoin reserve that flows where it's needed.
Benefits and risks, side by side
Stablecoin rails can materially change settlement speed, availability, and operating cost, but they also introduce a different set of operational responsibilities. Assess the benefits to size the upside for your corridor and use case, then use the risks to pressure-test your provider, custody model, and compliance path before you move volume.
Four benefits of stablecoin payments
Speed and liquidity: Payments settle within minutes instead of days, with no banking hours, cutoffs, or clearing delays. Funds move 24/7 and give teams immediate access to working capital.
Lower transaction costs: Cost savings depend on the corridor, but Cenoa's emerging-market flows show how large the spread can get: up to 80% lower cross-border payment fees than PayPal, Wise, and SWIFT. On smaller transfers, low network fees matter because they don't scale the way correspondent-bank fees and FX spreads do.
Transparency and reconciliation: Every transaction is recorded on a public ledger with a precise timestamp, which means finance teams stop chasing confirmations across correspondent banks and start reconciling from a single on-chain record. Cenoa's SMB customers in Turkey and Nigeria get real-time visibility into every cross-border transfer rather than waiting days for status updates through a SWIFT chain.
Financial accessibility in underserved markets: Stablecoins reach markets where traditional banking is limited or where local-currency volatility makes holding cash expensive. Airtm's 1.8 million users across Argentina, Nigeria, and five other countries hold and receive USDC through a digital wallet, spend via card, or convert to local currency on their own timeline without needing a US bank account.
Four risks to consider
Regulation: Laws are tightening. Europe's MiCA framework is live; the US GENIUS Act was signed in July 2025, establishing a federal licensing and oversight framework for stablecoins, with compliance broadly required by January 2027 or sooner once final implementing rules are issued. The UK, Singapore, and Hong Kong are running their own frameworks in parallel. Pick partners, like Bridge, who comply with local rules and maintain verifiable reserves.
Peg stability: Failures in algorithmic coins and temporary wobbles in leading fiat-backed stablecoins show why issuer transparency matters. Stick with well-audited, fiat-backed options that can redeem reliably. When the use case allows, consider custom stablecoins backed by Treasuries.
Security: Handling stablecoins means safeguarding private keys and wallets. Many enterprises delegate that responsibility to regulated custodians or payment providers rather than holding keys in-house.
Liquidity and conversion: In some markets, converting between stablecoins and local currency is still limited or slow. Treasury planning must account for on- and off-ramp availability by corridor, which is why provider corridor coverage matters more than provider feature lists.
Three of the four risks are addressable through provider choice. That leaves regulation. The trend line is clear: according to the EY-Parthenon 2025 Stablecoin Survey, 15% of financial institutions already offer stablecoin services, while 57% are planning to explore new offerings.
The compliance bar has shifted from uncertainty about what's allowed to a defined set of requirements that providers handle on your behalf. In practice, that means the early question, "Can we legally do this?" is increasingly replaced by, "Which licensed partner can help us do this safely, with the right controls, disclosures, and reporting?" Teams still need internal review, but the path is clearer: select a regulated provider, validate their reserve and custody model, confirm how KYC and sanctions screening is applied at the onramp and offramp boundaries, and understand what data and audit artifacts you will receive for your own compliance program.
As stablecoin regulation becomes more explicit across major markets, adoption shifts from a policy debate to an implementation decision. The work moves toward vendor diligence, corridor-level compliance requirements, and operational readiness, not proving that the category is permissible in the abstract.
How to evaluate and adopt stablecoin payments
The build-versus-buy question is settled. Almost no one builds the full stack of onramps, custody, compliance, multi-chain orchestration, and offramps in-house anymore. The remaining question is single API versus multi-vendor stitch.
If you're a fintech building cross-border products
Start with corridor coverage. It is the fastest way to narrow your shortlist. Which sender-to-receiver routes do you need on day one, and which do you need within a year?
A provider that claims 30 supported countries, but only connects to ACH and SEPA on the fiat side, likely cannot power LATAM remittances or African payroll.
A strong corridor answer from a vendor names the specific local rail on each end, such as PIX in Brazil, SPEI in Mexico, or M-Pesa in Kenya. It also quotes a settlement time per corridor, which is what actual infrastructure looks like.
A provider that says "we support 30+ countries" without naming the rails is showing you a partnership diagram. Ask for the typical settlement time on your highest-volume corridor and whether the onramp and offramp run through the provider's own integration or a third-party aggregator.
From there, evaluate the Virtual Account or onramp API your engineering team will work with, and the compliance posture covering KYC, AML screening, and sanctions handling.
Cenoa went live in under a month because Bridge handled the licensing, screening, and rails as infrastructure that the customer integrated against rather than as a checklist the customer had to satisfy alone.
If you're a neobank building wallets and cards
Your users won't tolerate moving funds between three apps to spend a stablecoin balance. The integration that wins is the one where stablecoins behave like cash: held in a wallet and spent through a Visa or Mastercard card with the wallet drawn down automatically at point of sale.
Ask whether the provider supports both custodial and non-custodial wallets. Ask whether cards pull from the wallet just in time at authorization, with no pre-funding step. Then ask whether the card stack is global out of the box or requires per-country licensing that you have to work through.
The difference between a just-in-time authorization draw from an on-chain wallet and a pre-funded card balance is the difference between a product your users trust and a product they may abandon after the first top-up.
This is where the open-sandwich architecture comes into play. Your users hold USDC, spend via card, and avoid a second conversion unless they choose to offramp to local currency.
Whether you can launch a custom stablecoin on the same platform is the next question to ask, because once a neobank earns interchange and reserve yield from its own token, the unit economics change.
If you're an enterprise running treasury operations
Compliance and custody come before feature evaluation. A treasury team doesn't move on infrastructure that hasn't passed legal, security, and audit review. Ask for SOC 2 reports, attestation cadence on reserves, and named regulatory licenses in the jurisdictions you operate in. Ask how the provider handles GENIUS Act and MiCA reporting on your behalf.
A strong compliance answer names the specific licenses held, provides a reserve attestation schedule, and shows you the sanctions-screening workflow. A weak answer says "we handle compliance" without showing how.
Then evaluate orchestration depth. Can the provider route across multiple stablecoins and chains automatically, or do you manage chain selection yourself? Can you issue a custom stablecoin against your own reserves and earn yield on them? And if full issuance is more than you need, can you hold an off-the-shelf option like Bridge's USDB, which earns rewards on balances without a custom launch?
Dakota's DKUSD launched in under a day because Bridge runs the issuance, reserve management, and compliance underneath, so Dakota's team focused on the product layer.
Across all three personas, the evaluation comes back to the same question: how many vendors does it take to cover the full stack?
Every provider will tell you they offer a single API; what separates marketing from infrastructure is what that API actually covers. Bridge runs orchestration, wallets, cards, and issuance from one integration, with compliance and custody built in, backed by Stripe's scale and reliability standards. If you're evaluating providers for cross-border payments, payroll, or treasury operations, the sandbox is open.
Frequently asked questions
What is the stablecoin sandwich?
The stablecoin sandwich is the architecture stablecoin payments use to bridge fiat and blockchain. The sender's local currency converts to a stablecoin like USDC, the stablecoin crosses on a public blockchain in seconds, and the recipient's provider converts it to local currency on the other end.
The model lets a US dollar reach a Mexican peso account in minutes without touching a correspondent bank.
How long does a stablecoin payment take?
Once a transaction is signed, it confirms on a network like Solana or Base in seconds. End to end, including onramp and offramp, most cross-border flows land within minutes.
Compared to SWIFT's one to five business days, the difference shows up most clearly on emerging-market corridors where wire transfers can take days to clear.
How much does a stablecoin payment cost?
Network fees on low-cost stablecoin chains can be measured in cents, but the network fee is only one part of the total price. The full all-in cost, including onramp, offramp, and FX, depends on the corridor.
On G10 routes, savings may come more from 24/7 settlement and automated reconciliation than from the transfer fee itself. On emerging-market routes, the savings are more likely to show up in both fees and settlement time because the correspondent chain is longer and FX spreads are wider.
Are stablecoin payments regulated?
Yes. The US GENIUS Act, signed in July 2025, establishes a federal licensing and oversight framework for stablecoins, with compliance broadly required by January 2027 or sooner once final implementing rules are issued.
The EU's MiCA framework is already live, classifying fiat-pegged stablecoins as e-money tokens with 1:1 reserve requirements. KYC and AML obligations apply at the onramp and offramp boundaries, which is where compliant providers concentrate their controls.
Do I need to hold crypto to use stablecoin payments?
No. In the full-sandwich model, the platform runs the onramp on the sender's side, executes the blockchain transfer, and runs the offramp on the recipient's side.
Sender and recipient see fiat going in and fiat coming out without ever touching a wallet themselves. The open-sandwich variant, where funds stay in stablecoins on one or both ends, is available when the user wants direct stablecoin custody.
Bridge is not a bank. The Prepaid Debit Visa Card is issued by Lead Bank and managed by Bridge Ventures, LLC. Fees may apply. See www.bridge.xyz/legal for more details.
The content in this article is for general information and education purposes only and should not be construed as legal or tax advice. Bridge does not warrant or guarantee the accuracy, completeness, adequacy, or currency of the information in the article. You should seek the advice of a competent attorney or accountant licensed to practice in your jurisdiction for advice on your particular situation.
Request demo
