B2B stablecoin payments have moved from pilot to production. Visa is running a live stablecoin settlement program for card-settlement flows. DoorDash settled payouts to merchants and gig workers in 40+ countries on Tempo, with sub-second finality. Businesses running cross-border B2B payments on stablecoin rails consistently report material reductions in all-in cost versus traditional wire transfers.
The three structural advantages driving adoption are speed, cost, and programmability. This guide covers each use case, the compliance layer, and the accounting treatment that makes it workable for a finance team.
Why B2B payments have been slow to modernize
Traditional B2B cross-border payment flows route through correspondent banking chains — a sequence of banks that each hold accounts with the next link, passing the payment along with a deduction for their fee. A payment from a US company to a supplier in Brazil might touch three or four correspondent banks, each adding a delay and a charge, before arriving in the recipient's account two to five business days later.
The total cost, once FX markup is included, typically runs 2–7% of the transfer value. For high-volume or frequent payments, this is not a rounding error — it is a material line in the P&L.
Stablecoins replace the correspondent chain with a single on-chain transfer. The payer sends USDC or USDT from their wallet; the recipient receives it in under a second; no intermediary takes a cut.
Supplier payments
Supplier invoice settlement is the most common B2B stablecoin use case. The workflow:
- Supplier onboarding: Collect the supplier's wallet address alongside standard onboarding information. Run KYB verification and OFAC/sanctions screening on the wallet address before the first payment.
- Invoice approval: Standard AP approval workflow. Once approved, the payment instruction is queued with the wallet address as the destination.
- Disbursement: A single transaction per supplier (or a batch transaction covering multiple suppliers) sends the stablecoin amount. On modern payment rails, settlement is final in under a second.
- Reconciliation: The transaction hash is the payment receipt. Memo fields embedded in the transaction (ISO 20022-compatible on Tempo) carry the invoice number, allowing automated matching in the ERP.
The supplier receives the stablecoin in their wallet and can hold it, convert it to local currency through an exchange or off-ramp, or use it in subsequent payments. In markets with strong local currency, conversion is immediate and cheap. In markets with weak or controlled currencies, receiving USD-denominated stablecoins directly is often preferable.
Marketplace payouts
Two-sided marketplaces — platforms that connect buyers with sellers, drivers, or contractors — face a structural payouts problem: they owe money to many counterparties, in many countries, on irregular schedules, often in small amounts.
Card network settlement for marketplace payouts typically involves:
- Settlement delay: T+1 to T+2 for domestic funds; longer for cross-border
- Processing cost: 1.5–2.5% of the payout amount
- FX conversion: Additional 1–3% for cross-border payouts in local currency
Stablecoin payouts flip this structure. DoorDash settled payouts to merchants and Dashers in 40+ countries using Tempo. Settlement is sub-second; fees are under $0.001 per transaction; the recipient holds a dollar-denominated stablecoin that is more stable than many local currencies.
Batch transactions make the economics cleaner. Rather than one on-chain transaction per recipient, a batch pays N recipients in a single transaction. On Tempo, native batch transaction support (via the Tempo Transaction format) means an entire weekly payout cycle can be executed with one transaction submission per cohort.
AR/AP automation
The programmability of stablecoin payments creates AR/AP automation that is not possible with traditional bank rails.
Payment-on-approval: An AP smart contract holds funds in escrow; when the invoice is marked approved in the ERP (via an API call), the contract automatically releases payment to the supplier's wallet. No separate payment run, no manual wire initiation.
Delivery-triggered escrow: For physical goods, the payment contract releases when delivery is confirmed — by an oracle, an IoT signal, or a manual confirmation from both parties. This is not possible with a bank wire once it is sent.
Scheduled recurring payments: Monthly retainers, license fees, or SaaS subscriptions can be committed on-chain as scheduled transactions. The payer locks funds; the payment executes at the scheduled time without manual intervention.
Reconciliation via memo fields: Tempo's ISO 20022-compatible memo fields let businesses embed invoice numbers, PO references, and line-item codes directly in the transaction. The ERP reads the memo on the inbound transaction and auto-matches — eliminating the manual reconciliation step that currently consumes significant accounts receivable staff time.
The compliance stack
Enterprise B2B stablecoin operations require three compliance components:
| Component | What it covers | Example providers |
|---|---|---|
| KYB/KYC | Counterparty identity verification | Middesk, Persona, platform-embedded |
| Sanctions screening | OFAC, EU, UN list checks on wallet addresses | Chainalysis, Elliptic, TRM Labs |
| Transaction monitoring | Ongoing AML surveillance of payment flows | Chainalysis KYT, Elliptic Investigator |
Stripe (co-incubator of Tempo, with stablecoin settlement for millions of businesses in 100+ countries) and BVNK (enterprise stablecoin infrastructure, listed in Mastercard's Crypto Partner Program) are the two platforms that embed the full compliance stack for B2B use cases. Both handle on/off-ramp, treasury, and compliance in a single integration.
For businesses that prefer to manage stablecoin operations directly — holding stablecoins on the balance sheet and paying suppliers directly from a treasury wallet — the compliance tools are available as standalone services that integrate with existing ERP systems.
Accounting treatment
Under US GAAP (ASC 350-60, effective 2024), digital assets including stablecoins are measured at fair value with changes recognized in net income. For a dollar-pegged stablecoin at $1.00, the practical effect is identical to a bank balance: no mark-to-market volatility, no unrealized gain/loss to track. Holdings require disclosure.
Under IFRS, IAS 38 (intangible assets) has historically applied to crypto holdings, but IAS 38 does not fit a dollar-pegged financial asset well; the IASB is actively revisiting guidance. Consult auditors for jurisdiction-specific treatment.
The Stripe lineage
Tempo was incubated by Stripe and Paradigm. Stripe — which processes hundreds of billions of dollars in payments for millions of businesses — is both a validator on Tempo's network and a stablecoin settlement partner, using Tempo to settle cross-border payments for businesses in 100+ countries. Stripe's institutional involvement is not a marketing endorsement; it reflects a deliberate bet that a payments-native chain with no gas-token friction, sub-cent fees, and sub-second finality is the correct architecture for the volumes Stripe handles.
For a CFO evaluating stablecoin B2B payments, the Stripe validator relationship answers the trust question: the company that built the internet's payment infrastructure chose to co-build and validate on this chain. That is the weight of evidence worth examining before the first supplier wire.
The wire transfer cost article quantifies the cost comparison with a worked example. The Tempo field guide explains the architecture underlying the B2B use cases described here.