Stablecoins for B2B Settlement: Where They Actually Work

Cross-border B2B payments are one of the few payment categories where the incumbent infrastructure is genuinely bad. A SWIFT wire from a US corporate to a Mexican supplier takes 1-3 business days, costs $25-45 in wire fees plus 0.5-2% FX spread, arrives without structured remittance data that the recipient’s ERP can automatically reconcile, and has a failure rate (returns, rejects, AML holds) of 3-5%. For a $50,000 invoice, the total cost of a SWIFT payment including FX spread and fees is $500-1,000. Per transaction.

Stablecoins don’t solve all of this — the FX conversion cost exists whether you pay in dollars on a blockchain or dollars through a bank — but they address the speed, cost, and reliability components in ways that SWIFT structurally cannot. The question for operators is not “will stablecoins replace SWIFT” but “in which specific corridors do stablecoins deliver enough advantage to justify the operational overhead of running a stablecoin payment stack.”

The answer is corridor-specific and more nuanced than either the crypto-enthusiast or the skeptic position allows.

The SWIFT Problem, Specifically

To understand where stablecoins compete, it’s worth being precise about what SWIFT’s problems actually are:

Correspondent banking chains. Most SWIFT wires don’t travel direct from originating bank to recipient bank. They route through one or more correspondent banks — typically 2-4 intermediaries for non-G7 corridors. Each correspondent adds settlement time (same-day if in the same time zone and currency, otherwise next-day), and each takes a fee. A payment from a US regional bank to a small Pakistani bank might route through: originating US bank → US correspondent (JPMorgan or Citi) → UAE or UK regional hub → Pakistani correspondent → recipient bank. Each hop adds cost and delay.

Cut-off times and holidays. SWIFT settlement runs in banking hours. A payment initiated at 3pm US Eastern on a Friday doesn’t start processing until Monday morning. The recipient in Manila doesn’t receive funds until Tuesday or Wednesday. The 1-3 business day estimate is an average; 3-5 business days is common for complex corridors.

Remittance information truncation. SWIFT MT messages have limited structured data fields. The invoice number, PO number, and line-item details that corporate finance needs for automated reconciliation often get truncated or stripped by intermediaries. The recipient bank receives funds with a reference that says “INVOICE 12345 OCTOBER” — not the structured XML remittance data the CFO needs to automatically close the invoice in NetSuite.

AML holds. Any transaction triggering correspondent bank AML screening can be held for manual review — 1-5 business days. There’s no notification mechanism. The sender doesn’t know why funds haven’t arrived. The recipient doesn’t know when they will.

Stablecoins on public blockchains solve the speed and correspondent-chain problems structurally. Settlement is final in minutes on Ethereum, Solana, or Stellar. There are no cut-off times. There are no correspondent intermediaries adding fees and delays. Remittance data can be attached to the transaction. AML hold risk exists at the fiat on/off-ramp, not in-chain.

Corridor Analysis

US → Mexico

The US-Mexico corridor is the highest-volume B2B payment corridor for stablecoin adoption. Several factors converge:

The SWIFT correspondent chain between US regional banks and Mexican banks (Banorte, BBVA Mexico, Santander Mexico) is reliably slow — 2-3 business days typical. FX spread on USD/MXN for corporate amounts ($50K-$500K) is 0.8-1.5% at wire rates. SPEI, Mexico’s domestic real-time rail, can receive funds from abroad — but the entry point requires a Mexican bank partner, and the correspondent relationship to get to SPEI from a US originator typically replicates the SWIFT inefficiency.

Stablecoin workflow for US→Mexico B2B: US company holds USDC, sends to Mexican supplier’s stablecoin address, Mexican supplier converts USDC to MXN via a local exchange or stablecoin-to-SPEI provider (Bitso, for example, which processes billions in cross-border value annually). The USDC transfer settles in minutes; the MXN appears in the Mexican supplier’s bank account same-day or next-business-day via SPEI.

Total cost comparison: SWIFT wire ($35 fee + 1.2% FX spread on $100,000 = $1,235) vs. stablecoin ($5-15 network fee + 0.3-0.5% FX spread on $100K via Bitso-class off-ramp = $305-515). The 2-3x cost advantage is consistent across transaction sizes above $10,000. Below that, the fixed-fee component makes comparison unfavorable for stablecoins.

The off-ramp reliability — Bitso and comparable Mexican stablecoin-to-SPEI providers — has matured significantly since 2021. Bitso processes $15B+ annually and has banking relationships that make the SPEI credit reliable. The risk is off-ramp provider concentration: there are a small number of licensed providers in Mexico, and any operational issue with Bitso affects the entire stablecoin→MXN supply chain for US operators using it.

UAE → India / Pakistan / Philippines

The UAE → South Asia corridor is the second major stablecoin B2B settlement use case. The driver is different from the Mexico corridor: it’s not SWIFT cost but SWIFT reliability.

UAE-to-Pakistan SWIFT flows have experienced repeated AML-related disruptions. US correspondent banks (which intermediate between UAE banks and Pakistani banks) have progressively de-risked Pakistani correspondent relationships — reducing services, requiring enhanced due diligence, and imposing holds. For legitimate B2B payments (IT services, business process outsourcing, textile manufacturing), this creates settlement unreliability that stablecoins avoid by not using US correspondents at all.

USDC or USDT sent from a UAE wallet to a Pakistani USDT wallet settles in minutes with no US correspondent touchpoint. The recipient converts to PKR via a Pakistani crypto exchange or OTC desk. The FX conversion is still subject to Pakistan’s complex exchange rate framework — there’s a managed official rate and a market rate — but the settlement timing risk of the SWIFT path is eliminated.

UAE → India is a different structure. India’s RBI has progressively restricted stablecoin-to-INR conversion — direct stablecoin off-ramp at Indian exchanges is limited by regulatory treatment of crypto as speculative instruments. Legitimate B2B flows to India largely still use SWIFT or purpose-built fintech corridors (Wise, Payoneer, Airwallex) rather than stablecoins, because the INR off-ramp is not reliable at scale. Stablecoin’s India advantage is minimal compared to Mexico or Pakistan.

Philippines is a positive case: Filipino OFW (overseas Filipino worker) remittance infrastructure has adapted well to stablecoin settlement. USDC → PHP via GCash’s Fuse or Coins.ph is a reliable, regulated off-ramp. B2B payments to Philippine BPO firms increasingly use USDC-to-GCash pathways rather than SWIFT.

US → Latin America (ex-Mexico)

Brazil, Colombia, Chile, and Argentina present varied stablecoin utility:

Brazil. Pix has transformed domestic payment speed, but the international payment entry is still SWIFT. USD→BRL via stablecoin requires an authorized exchange dealer (corretora de câmbio) licensed by Banco Central. Hashdex, Foxbit, and others serve this market. The regulatory clarity in Brazil (stablecoins classified, exchange dealers licensed) makes it a viable corridor. Pix itself doesn’t accept stablecoin settlement — the conversion to BRL must happen first, then Pix delivers domestically.

Argentina. The most interesting case. Argentina’s chronic USD-ARS exchange rate instability has made USDT a de facto USD substitute for businesses and individuals. Argentine businesses routinely invoice in USDT, hold treasury in USDT, and pay suppliers in USDT — avoiding ARS-denominated inflation risk. The stablecoin is not primarily a settlement efficiency tool here; it’s a currency hedge. B2B dollar flows to Argentina via stablecoin are large and well-established, though operating in a complex regulatory environment where the official/parallel rate gap creates compliance complexity for operators with US/EU accounting obligations.

Colombia, Chile. More conventional adoption: stablecoin for cross-border, converted to COP/CLP at licensed domestic exchanges, settled via local ACH equivalents. Efficiency advantage over SWIFT exists; adoption is growing but less mature than Mexico.

Where Stablecoins Don’t Work

The cases where stablecoin B2B settlement has not taken hold are as instructive as where it has:

US → EU / UK. SEPA and Faster Payments work. A USD→EUR payment from a US company to a German supplier via a global bank (Wise Business, Airwallex, or direct bank wire) settles in 1 business day with 0.3-0.5% FX spread. The SWIFT problem simply doesn’t exist in the same form for EU corridors — correspondent banking infrastructure is dense and reliable. The stablecoin efficiency gain over existing solutions is marginal and doesn’t justify the operational overhead.

B2B above $5M single transactions. Stablecoin on-chain transaction limits are rarely the issue, but the off-ramp liquidity for large single transactions is. Converting $10M USDC to MXN in a single transaction will move the market — OTC desk liquidity for stablecoin-to-fiat at large sizes requires pre-arranged quotes and has meaningful market impact. SWIFT wires at $10M are a well-understood process that treasury teams know how to execute. The stablecoin alternative introduces operational complexity without proportionate benefit.

Any corridor with unclear stablecoin regulatory treatment. China (strict), India (restricted), Nigeria (regulated but with operational complexity) — corridors where the regulatory treatment of stablecoin-to-fiat conversion is ambiguous or hostile create compliance risk that outweighs settlement efficiency gains. Operators with US public company or EU regulatory obligations need clear regulatory treatment in the recipient country before deploying stablecoin payment infrastructure.

USDC vs USDT: The Enterprise Choice

For B2B settlement, USDC (Circle) is increasingly the enterprise default. The reasons are compliance-driven:

Circle publishes monthly reserve attestations from a Big Four auditor. USDC reserves are held in short-duration US Treasury instruments and cash at regulated US financial institutions. For a corporate treasury team that needs to explain stablecoin holdings to auditors, USDC has a clear answer: it is fully reserved, independently attested, and issued by a US-regulated company.

USDT (Tether) has a larger market cap and more liquidity, particularly in emerging markets where stablecoin infrastructure was built on USDT networks. But Tether’s reserve disclosures — until recently limited and including commercial paper — have made it difficult for regulated enterprises to hold USDT in corporate treasury accounts without auditor questions. Tether has improved disclosures, but the institutional trust gap remains.

The practical outcome: USDC for enterprise B2B corridors where compliance documentation matters (US→Mexico, US→LatAm, UAE→South Asia for regulated businesses). USDT dominates OTC and less-regulated corridors where liquidity depth and merchant acceptance matter more than reserve documentation.

The Practical B2B Stack

An operator deploying stablecoin B2B payments in 2026 typically assembles:

On-ramp. The corporate account converts USD/EUR to USDC via Circle’s business API or a licensed crypto exchange with banking integration (Coinbase Prime, Anchorage Digital). This conversion is a regulated money transmission event in the US.

Settlement layer. USDC transfer on-chain. Solana has become the preferred settlement chain for high-frequency B2B payments — transaction fees of fractions of a cent, 400ms block finality, and USDC natively supported at scale. Ethereum remains relevant for large-value or DeFi-integrated use cases. Stellar is used by specific remittance corridors (primarily African and Southeast Asian).

Off-ramp. In-country conversion from USDC to local fiat. The off-ramp provider must be locally licensed, have banking relationships to credit recipient accounts in the local payment system, and provide exchange rates that are operationally competitive with SWIFT FX. This is the most fragile part of the stack — off-ramp provider health and regulatory status in each corridor is the primary operational risk.

Compliance and reporting. Transaction screening (OFAC/sanctions), counterparty KYB, and accounting treatment. FASB’s 2024 guidance clarifying that crypto assets should be measured at fair value removes a previous accounting complication for US-reporting companies.

The assembly of this stack is available through fintechs that have done the corridor integration work (Bridge, acquired by Stripe for $1.1B in February 2025; Bitso; Ripple’s payment corridors; Alchemy Pay). Using a fintech layer abstracts the on-chain complexity but reintroduces a provider concentration risk — if Bridge/Stripe has a service disruption, the operator has no backup.

The Regulatory Trajectory

The regulatory trajectory for stablecoin B2B settlement is clarifying rather than tightening in most relevant jurisdictions:

The US GENIUS Act (stablecoin legislation advanced through Senate in 2025) provides a federal licensing framework for stablecoin issuers — requiring reserve requirements and audit standards that USDC already meets and USDT is under pressure to match. For enterprises using USDC, this formalization reduces regulatory risk rather than adding it.

EU MiCA (Markets in Crypto-Assets) regulation, effective 2024-2025, creates a licensed stablecoin framework within the EU. USDC and euro-denominated stablecoins are being registered under MiCA. This provides EU operators with legal clarity on stablecoin use that was previously absent.

Singapore MAS, UAE VARA, and UK FCA are each building or have built stablecoin-specific licensing frameworks. The global direction is toward regulated stablecoin operation, not toward prohibition — which reduces the corridor risk for the enterprise use cases where compliance documentation is important.

The specific corridors where B2B stablecoin settlement is working today — US→Mexico, UAE→South Asia, US→Argentina — are working because the operational infrastructure exists, the regulatory treatment is workable, and the efficiency gain over SWIFT is large enough to justify the setup cost. The number of corridors meeting all three criteria is growing. The question for operators is not whether to have a position on stablecoin B2B settlement, but when their specific corridors will cross the threshold where the economics and operational reliability are sufficiently better than SWIFT to justify migration.