B2B stablecoin payments are commercial transactions between businesses settled in dollar-pegged tokens — typically USDC or USDT — on public blockchains rather than through bank wires, ACH, or SWIFT. The economic case is straightforward: settlement compresses from days to seconds, fees fall to single-digit cents on most chains, and the dollar balance becomes programmable, meaning a payment can carry conditions and chain into longer treasury workflows. As of April 29, 2026, USDC and USDT alone represent $266.8B in circulating supply per DeFiLlama, and a measurable share of that volume is settling cross-border B2B flows.
​

This article walks through the B2B status quo (the wire, ACH, and SWIFT rails businesses use today), explains why stablecoin rails win on speed and programmability, lays out the operational stack — acceptance, treasury, payouts — that production teams build, names the customer patterns where it is shipping in volume, and addresses the compliance and accounting work that any finance team needs to handle. It closes on the risks worth flagging and the orchestration layer that hides the underlying chain complexity.
​

B2B stablecoin payments are commercial settlements between two businesses — invoices, supplier payouts, payroll, intercompany transfers — executed by transferring stablecoins between blockchain addresses. The transfer is final once confirmed onchain, settles in seconds to minutes depending on the chain, and produces a permanent transaction record that finance teams can reconcile against an invoice or general-ledger entry.
​

The category covers any business-to-business payment whose primary instrument is a stablecoin. Common examples: a US software company paying a Vietnamese development team in USDC; a freight broker settling a shipping invoice with a Singapore carrier in USDT; a SaaS company collecting subscription revenue from international customers in USDC and converting to USD via a regulated offramp once a week. Circle Mint and Bridge (now part of Stripe) are the largest acceptance and offramp infrastructure providers; treasury management platforms like Utopia Labs and Fordefi handle the operational layer.
​

The volume signal is large enough to take seriously. The BIS Committee on Payments tracks cross-border payment flows; total cross-border B2B value runs in the hundreds of trillions per year. Visa Direct and global cross-border B2B exceed $150 trillion annually combined. Even single-digit-percent stablecoin penetration would represent trillions in annual stablecoin B2B volume — and the trajectory looks steeper than that. For deeper background on the underlying primitive, see programmable money and the broader piece on how stablecoin payments work.
​

Most B2B payments today move on three rails: domestic ACH for low-value high-volume flows, domestic and international wires for high-value time-sensitive payments, and SWIFT for cross-border correspondent-bank transfers. Each rail has well-understood economics and well-understood failure modes; stablecoins compete on settlement time, fee, and programmability rather than on regulatory reach.
​

The shape of each rail matters because it sets the bar that stablecoin systems clear or fall short of. ACH is cheap (often free for the originator) but settles in 1 to 3 business days and is reversible for up to 60 days under Nacha rules. Wires are fast (same-day during banking hours) but expensive ($15 to $50 per transfer for the originator, plus correspondent-bank fees) and final once sent. SWIFT messages are not money movement; they are instructions that correspondent banks act on, which is why a "SWIFT transfer" can take 2 to 5 business days and generate fee deductions at each correspondent leg.
​

The best public reference for the cost structure is the Federal Reserve Board's payment economics research. McKinsey's global payments practice publishes annual estimates of the all-in cost of cross-border B2B at 2 to 3 percent of value once FX spread, lifting fees, and intermediary deductions are included. Card-network B2B (purchasing cards, virtual cards) is a separate category — useful for low-value supplier payments but burdened by interchange that compares unfavorably to either rail. Credit-card interchange in the US runs roughly $0.50 to $0.80 per transaction in published comparisons per Federal Reserve Bank of Kansas City interchange research; debit-card interchange under Regulation II averages closer to $0.22 to $0.24 per transaction per the Fed's 2023 Reg II report.
​

Stablecoin rails do not replace this stack so much as offer a second rail with different trade-offs: faster settlement, lower fees per transfer at most volumes, programmability, and global reach without correspondent banking. They also bring new operational concerns — chain selection, custody, and accounting integration — that the legacy rails do not impose.
​

Stablecoins win three properties at once: settlement is final in seconds to minutes rather than days, per-transfer fees fall to single-digit cents on most chains rather than $15 to $50 per wire, and the payment instrument is programmable, meaning a transfer can carry conditions, route through automated logic, and integrate with onchain treasury operations directly. The combination is why volume migrates even when nominal cost differences are small.
​

Settlement time is the most visible win. A USDC transfer on Solana finalizes in roughly 400 milliseconds. On Ethereum L2s like Base, Arbitrum, and Optimism, soft confirmation arrives in about 2 seconds. Cross-chain transfers add the bridge or messaging layer's finality time — Circle's CCTP currently runs in the 13 to 20 minute range, and Hyperlane is faster on its supported routes. Compared with a SWIFT wire that may not arrive until the next business day, the operational difference is qualitative.
​

Fee economics are the second leg. Gas fees on Solana average a fraction of a cent. On Ethereum L2s, transfers usually fall between $0.001 and $0.05. On Ethereum mainnet, fees are higher and variable. A seven-figure stablecoin payment on Solana can settle for less than the postage on a printed check. A seven-figure wire often costs $30 to $50 in originator fees plus 25 to 75 basis points in FX spread on the cross-border leg. That gap shows up at every B2B volume profile, from low-four-figure contractor invoices to nine-figure intercompany transfers.
​

Programmability is the third leg and the one that compounds over time. A B2B stablecoin payment can include conditions enforced by code — funds release on delivery confirmation, on milestone completion, or on a multi-sig approval. The transfer can chain into longer flows like converting a portion to a different stablecoin, sweeping a slice into a yield position, and routing the remainder to an operating wallet, all atomically. Sweep-automation tools turn this into operational reality for treasury teams. Aave V3 holds $13.7B in TVL per DeFiLlama as of April 29, 2026, much of it from corporate treasury operations.
​

"Cross-border payments using crypto assets can be considerably cheaper and faster than incumbent rails for use cases that match the technology's strengths." — IMF Working Paper, "The Crypto Economy and Cross-Border Payments"

A production B2B stablecoin payment system has three operational layers — acceptance (how the business receives stablecoins from counterparties), treasury (how it holds and routes those balances), and payouts (how it sends stablecoins to suppliers and contractors). Each layer has well-known infrastructure choices, and the stack a team picks depends on volume, geography, and regulatory profile.
​

None of these layers requires custom development for a typical SaaS or services business. The choice is mostly about which infrastructure providers to integrate with, and at what point a treasury platform becomes more economical than direct integrations. The piece on stablecoin payment gateways compares the acceptance-layer options in detail.
​

Acceptance options range from generating an invoice that includes a wallet address (a do-it-yourself approach) to integrating a hosted checkout from a payment processor. Coinbase Commerce, BitPay, and Stripe's stablecoin acceptance handle the standard flow: customer initiates payment, processor exposes a stable address, customer pays, processor confirms onchain finality, merchant gets credited. USDC is the default acceptance asset for businesses that want a regulated US issuer; USDT is more common for counterparties in Asia and Latin America.
​

Larger merchants often run a hybrid: hosted checkout for online customers and direct-wallet acceptance for B2B counterparties who already operate stablecoin treasury. The hybrid lets the business avoid the processor's fee on internal flows while keeping a polished checkout for one-time customers.
​

Once stablecoins arrive, the treasury layer holds them, manages risk, and routes balances across operating accounts, reserve buckets, and yield positions. The custody choice is the first decision: self-custody multi-sig (typically Safe), institutional custodian (Fireblocks, BitGo, Anchorage), or a hybrid that uses both. Multi-sig with hardware-key signers and well-defined approval policies is the production default for crypto-native teams; institutional custody dominates for traditional treasury teams that want SOC 2 audits and SLAs.
​

Routing decisions sit on top of custody. A treasury holding USDC on Base may need to settle a vendor invoice on Solana or pay a contractor on Polygon. CCTP handles native USDC movement; orchestration layers handle the broader chain-selection problem. The piece on DAI for treasuries covers the crypto-collateralized alternative.
​

Payout flows look like inverted acceptance flows: the business signs a transfer out of its treasury, the recipient's wallet receives it, and the business records the entry in its accounting system. Payroll-style flows (many small payments to a list of recipients) are typically batched through specialized tools — Request Finance for invoicing-led flows, Utopia Labs for treasury-led flows, Bitwage for payroll-specific use cases.
​

Payee onboarding is the friction point that often gets underestimated. A US contractor who is happy to receive USDC may not know which chain the company is paying on, which wallet to use, or how to swap to USD on the receiving side. Production payout systems include payee-side guidance, address verification, and (often) optional fiat conversion at the receiving end via partners like Kast Card or local-currency offramps.
​

The B2B stablecoin pattern looks different across industries. Software, services, e-commerce, and physical-goods businesses each settle into different shapes — different chains, different stablecoins, different fee profiles, different reconciliation work. The patterns below are the four that show up most frequently in 2026.
​

The shapes overlap, but the dominant chain and stablecoin choice depends on where counterparties live and which custody and accounting tools the company already uses. Each pattern reflects a real trade-off between speed, fee, and operational lift.
​

A US-incorporated SaaS company with developers in Argentina, Vietnam, and Poland pays in USDC on Polygon or Base. Bi-weekly batches are signed from a Safe multi-sig and processed through Request Finance or Utopia. The contractors receive USDC and either hold, swap to local currency through a regional offramp, or spend via a stablecoin-funded card. The company avoids 2 to 5 day SWIFT delays and the 1 to 3 percent FX-spread tax on international wires.
​

An Indian agency invoicing US clients accepts USDC for the convenience of the US client and the speed of settlement. A US enterprise paying a foreign legal firm settles in USDC rather than originating an international wire that takes 2 to 5 business days and incurs intermediary deductions. The agency converts to INR through a local exchange and books the receipt as USD-denominated revenue under its accounting standard.
​

Marketplaces operating in regions with thin banking infrastructure (parts of Africa, Latin America, and Southeast Asia) settle to merchants in USDT or USDC same-block rather than batching to ACH-equivalents that may not exist. Merchant trust improves dramatically when settlement is provably instant; the operating-cash-flow effect for the merchant is real and measurable.
​

Importers paying overseas suppliers settle commercial invoices in USDC or USDT with conditions enforced by code — funds release on bill-of-lading verification, on inspection-contract approval, or on a milestone schedule. Freight brokers settle carrier invoices in stablecoins where the carrier prefers them, often through a treasury platform that handles invoice generation, payment, and accounting in one workflow. The pattern is most visible in commodity trading and fashion supply chains where international counterparties already operate dollar-denominated treasuries.
​

The matrix below summarizes the four patterns by their stablecoin, chain, and operational tooling.
​

Each pattern reflects practical constraints — the chain the counterparty already uses, the stablecoin the destination market accepts, the tools the finance team already runs. There is no single right answer, which is why orchestration matters as the patterns multiply.
​

Compliance for B2B stablecoin payments breaks into three concerns: KYC/KYB on counterparties, regulatory classification of the stablecoin and the activity, and accounting/tax treatment of stablecoin balances and flows. None of these are blockers; they are work that any finance and compliance team needs to do once, and then maintain. The reality has improved substantially since 2023.
​

The basic frame: most B2B stablecoin activity by US-incorporated counterparties is conducted under existing money-transmitter and AML frameworks layered with crypto-specific guidance. Counterparty identification is required, transaction monitoring is required, sanctions screening is required, and the work is mechanically the same as for traditional payments — different vendors, similar diligence.
​

Receiving or sending stablecoins to a counterparty's wallet requires the same identity work as paying via wire. Treasury platforms typically integrate with KYC providers like Persona or Onfido and onchain analytics from Chainalysis or TRM Labs to screen wallet addresses against sanctions lists and known illicit-activity clusters. The practical workflow is: when onboarding a new vendor, collect business documents, verify beneficial ownership, screen the receiving wallet, and store the documentation alongside the payment record.
​

The sanctions surface is the most operationally sensitive piece. OFAC's enforcement actions in recent years have specifically named wallet addresses, which makes wallet screening a standard part of any B2B stablecoin compliance program.
​

The two questions a finance team needs to answer: is the stablecoin we are using regulated as electronic money or a payment instrument in the jurisdictions where we operate, and does our use of stablecoins for B2B payments require a money-transmitter or VASP license? In the US, fiat-collateralized stablecoins issued by registered entities (Circle for USDC, Paxos for PYUSD and USDP) operate under existing state money-transmitter frameworks. The European Banking Authority's MiCA regime in the EU has specific authorization paths for stablecoin issuance and activity. The right answer depends on jurisdiction; many B2B operators run an opinion of counsel on entry.
​

Activity-side licensing is usually answered by the infrastructure provider you integrate with rather than the company doing the payments. Coinbase Commerce, Stripe, and Bridge handle the licensed processing under their own authorizations.
​

The biggest accounting change for US filers is FASB ASU 2023-08, which moved crypto assets to fair-value measurement for fiscal years starting December 2024. Stablecoins held at par show fair-value movements that match the issuer's redemption price, which simplifies the accounting story. Tax treatment for ordinary B2B payments is straightforward: a USDC payment for a service is a deductible expense at fair value on the date paid, and the recipient recognizes revenue at fair value on the date received. Specialty platforms like Cryptoworth and Bitwave handle the bookkeeping integration with NetSuite, QuickBooks, and SAP.
​

Wash-sale, capital-gain, and FBAR considerations matter for treasury holdings of yield-bearing or appreciating assets but are typically not relevant for stablecoins held at par. The Tax Foundation and the AICPA have published guidance on the open questions; the canonical references update annually.
​

The risk surface for B2B stablecoin payments has four main categories: counterparty/issuer risk, smart-contract risk, custody risk, and operational risk. Each has well-understood mitigations, and a production program implements all four explicitly. None of these risks are unique to stablecoins, but the failure modes look different than the bank-rail equivalents and need to be planned for.
​

Treating risk explicitly is the difference between a B2B stablecoin program that survives an adverse event and one that does not. The mitigations below are the production-default set, drawn from how mature programs have responded to incidents over the past two years.
​

A stablecoin can de-peg if the issuer's reserves come under stress or if the market loses confidence. USDC briefly traded below $0.90 in March 2023 during the Silicon Valley Bank failure when a portion of Circle's reserves was held there; the peg restored within days when the FDIC backstop became clear. The mitigation is portfolio composition: hold balances across multiple stablecoins (USDC and USDT, plus a smaller allocation to USDS or DAI), monitor issuer transparency reports, and have a redemption playbook for material events.
​

Counterparty risk on the receiving side is the same as in any payment channel: did the recipient deliver what was paid for. Stablecoins do not introduce new counterparty risk; they remove the bank-as-intermediary failure mode while preserving every other counterparty concern.
​

Production stablecoin programs interact with contracts — multi-sigs, swap routers, lending vaults, payment processors. Each is a smart-contract surface that could have a bug or be exploited. Mitigations include using audited contracts (OpenZeppelin, Trail of Bits, Certora are the standard auditors), running on chains with mature MEV and sequencer protections, and limiting exposure to any single contract via spending caps.
​

Lost keys mean lost funds. Multi-sig with geographically distributed signers, hardware-key requirements, and a documented recovery procedure are the production defaults. Insurance is available from specialty carriers but does not substitute for procedural rigor.
​

Sending USDC on the wrong chain, paying a wallet that turns out to be a bridged-USDC contract rather than a recipient address, or settling on a chain whose finality is reorg-prone are operational failures that show up in real programs. The mitigations are address-book discipline, integration with chain-aware tooling, and orchestration layers that abstract the chain-selection decision away from the operator.
​

Stablecoin transactions emit data — transaction hash, chain ID, block number, memo field — that does not natively map to the journal-entry shape most ERP systems expect. Without a deliberate reconciliation pipeline, a B2B stablecoin program can produce transactions the accounting team cannot trace back to invoices, vendors, or cost centers. The mitigation is to build the reconciliation step into the payment workflow rather than after it, so each onchain transaction is associated at the moment of payment with the invoice, vendor, and GL code it should hit. Vendors like Cryptoworth, Bitwave, and several treasury platforms ship the integration; teams that build their own typically need a quarter of focused engineering work to reach production parity.
​

Converting received stablecoins to fiat introduces market-hours friction at the offramp. A receiving entity that needs USD in a US bank account by Friday cutoff has to time the offramp request, since some routes settle T+1 in domestic USD. Mitigations include using offramps with intraday settlement, holding a USD float at the offramp partner, or running a hybrid program where part of the receivable is converted on receipt and part is held as USDC for next-cycle obligations. The Treasury management practice is the same principle traditional treasuries apply with FX exposure; the tools differ.
​

The chain-selection problem grows with the number of counterparties, currencies, and chains a B2B program operates across. Orchestration is the layer that hides the rail-selection and route-execution decisions behind a single interface, so a finance team can focus on counterparty relationships rather than infrastructure choices.
​

The mechanics: an orchestrator takes an intent — "pay this vendor a six-figure USDC amount, settling on the chain they specify" — and decomposes it into a route. The route may use Circle's CCTP for the USDC leg, Hyperlane for the cross-chain message, and a swap for the destination-side currency conversion. The orchestrator quotes a single price, settles atomically, and returns a single receipt. The application calling the orchestrator does not need to know which rail was used; the finance team gets one ledger view of inflows and outflows that maps cleanly to a chart of accounts.
​

Eco operates at this layer. Eco is the stablecoin orchestration network powering production cross-chain stablecoin movement across 15 chains: Ethereum, Optimism, Base, Arbitrum, HyperEVM, Plasma, Polygon, Ronin, Unichain, Ink, Celo, Solana, Sonic, BSC, and Worldchain. Routes (CLI and API) is the developer surface. The execution network handles solver selection, liquidity, and finality. Hyperlane is the live partner rail; Circle's CCTP is internal transport used inside the routing engine. Peer orchestrators including LayerZero, Wormhole, Across, and LI.FI operate alongside this layer and offer different trade-offs in finality, fee, and asset coverage. For B2B teams, the practical contrast is concrete: integrate one orchestrator and the chain-selection problem stops being an application problem.
​

What is programmable money
​

How stablecoin payments work
​

Best stablecoin payment gateways
​

How USDC works
​

What is Tether USDT
​

Circle CCTP explained
​

MakerDAO and DAI for treasuries
​

Stablecoin sweep automation tools
​

Onchain agentic payments
​

USD to USDT conversion paths
​

Kast Card USDC spending
​

Yes, in most major jurisdictions, with caveats. The activity sits under existing payment, AML, and tax frameworks layered with crypto-specific guidance. US-incorporated businesses paying suppliers in USDC operate under standard money-transmission rules; the licensed processing is typically handled by the payment provider (Circle, Stripe, Bridge) under their authorizations. Specific jurisdictions have specific rules; an opinion of counsel is standard before launching a program.
​

On Solana, roughly 400 milliseconds. On Ethereum L2s like Base or Arbitrum, around 2 seconds for soft confirmation. On Ethereum mainnet, about 12 seconds per block. Cross-chain payments add the bridge or messaging layer's finality time. CCTP currently runs in the 13 to 20 minute range; Hyperlane is faster on its supported routes. See CCTP for the canonical reference.
​

Gas fees on Solana average a fraction of a cent. On Ethereum L2s like Base, Arbitrum, and Optimism, transfers usually fall between $0.001 and $0.05. On Ethereum mainnet, fees are higher and variable. Compared with $15 to $50 per wire originator-side and 25 to 75 basis points in FX spread on cross-border legs, stablecoin transfers are an order of magnitude cheaper at most B2B volumes.
​

USDC is the default for businesses that want a regulated US issuer and tight US banking integration; per DeFiLlama, USDC supply is $77.3B as of April 29, 2026. USDT is the default for counterparties in Asia and Latin America; supply is $189.5B. PYUSD ($3.4B) and USDS ($7.8B) are growing for specific PayPal-network and yield-bearing use cases. See USD to USDT conversion paths for a deeper read on the conversion rails.
​

Agents — software that acts on behalf of a business — increasingly transact in stablecoins for machine-to-machine commerce. The pattern is documented in detail in onchain agentic payments. For B2B, the agent typically holds a small treasury balance with strict spending limits and signs paid requests against APIs and other agents, with a parent treasury contract refilling the wallet on a schedule.
​

A bridge moves a token from chain A to chain B using one specific transport mechanism. Eco is an orchestration layer that selects across multiple bridges and rails based on the user's intent and executes routes atomically. For a B2B program operating across chains and stablecoins, the practical contrast is integration count: hardcode one bridge and live with its trade-offs, or integrate one orchestrator and delegate route selection to a network that re-evaluates per transfer.
​

Sources and methodology. Stablecoin supplies and TVL pulled from DeFiLlama on April 29, 2026. Token prices from CoinGecko. Regulatory references from FASB, the Federal Reserve, the Federal Reserve Bank of Kansas City, and the European Banking Authority. Figures refresh quarterly.
​