Stripe accepts stablecoin payments from customers in 70+ countries, settles them to USDC on Solana, Ethereum, or Polygon, and pays merchants out in either USD or stablecoin at a flat 1.5% fee. The product relaunched in October 2024 after Stripe pulled its 2014–2018 Bitcoin checkout, then expanded through the $1.1B Bridge.xyz acquisition and the 2025 Tempo L1 announcement with Paradigm.
What are Stripe stablecoin payments?
Stripe stablecoin payments let any merchant on Stripe Charges accept USDC from a customer's self-custody wallet, with Stripe handling onchain confirmation, FX, compliance, and reconciliation behind the same Dashboard and API used for card payments. Settlement clears in seconds on Solana, Ethereum, or Polygon, and payouts arrive in USD or stablecoin.
The product sits inside the standard Stripe Payments API. A merchant adds crypto as a payment method in Dashboard → Payments → Payment methods, and Stripe's Checkout and Payment Element render a QR code plus a WalletConnect handoff for the buyer. Behind the scenes, Stripe creates a one-time deposit address, watches the chain for confirmations, and posts a settled crypto Charge object when the transfer lands. From the merchant's accounting view, the row looks indistinguishable from a card payment.
The relaunch was announced in October 2024 and rolled out to US merchants first. Stripe CEO Patrick Collison framed it on the company blog as "stablecoins are room-temperature superconductors for financial services" — the bandwidth case for offchain rails finally being matched by onchain ones. USDC issuance has grown to $78.1B (DeFiLlama, May 2026), and Stripe is wiring directly into that supply rather than building its own.
How does the Stripe USDC flow actually work?
A customer scans the QR code or clicks "Pay with crypto" in Stripe Checkout, signs a USDC transfer from a wallet like Phantom, MetaMask, or Coinbase Wallet, and Stripe credits the merchant once the transaction has the required confirmations. On Solana that's typically under 5 seconds; on Ethereum, two minutes; on Polygon, roughly one minute. The merchant payout follows Stripe's normal schedule.
Three pieces of the flow matter for merchants. First, the buyer pays in USDC on any of the three supported chains — Stripe abstracts which one. The Payment Intent contains a destination address scoped to that Charge, not a shared merchant address, which removes the reconciliation problem most onchain checkout integrations create. Second, FX and settlement are deterministic: Stripe quotes the USD price at the moment of Checkout creation and locks it for a short window, so a buyer paying $99.00 sends $99.00 of USDC rather than a floating amount. Third, merchant payouts route through the existing Stripe balance — USD goes to the bank ACH/wire on the standard 2-day cycle, or USDC payouts go to a designated wallet for merchants who want to stay onchain.
The fee structure is flat at 1.5% per transaction, with no separate network fee passed through. That is materially below the 2.9% + $0.30 baseline for card payments, and the Federal Reserve Bank of Kansas City's 2023 payments research briefings place merchant interchange-plus-acquirer cost on a typical credit card at roughly $0.50–$0.80 per ticket for mid-sized retailers — Stripe is pricing the stablecoin path below that floor.
Why did Stripe acquire Bridge.xyz for $1.1B?
Bridge.xyz is a stablecoin orchestration API that handles issuance, custody, FX between fiat and USDC, and cross-border payouts to local bank accounts. Stripe announced the $1.1 billion acquisition in October 2024 — the largest in Stripe's history — to bring the offramp, treasury, and global-payout stack in-house rather than buying it as a vendor.
Before the deal, Bridge counted SpaceX, Coinbase, and several remittance corridors among customers using its APIs to move USDC into local currencies in Argentina, Mexico, the Philippines, and Nigeria. The fit with Stripe is exact. Stripe's traditional rail is card acceptance plus ACH/SEPA payouts in roughly 50 countries; Bridge's rail is USDC issuance, sweep, and onramp/offramp into roughly 40 currencies. Bolting Bridge onto Stripe Payments turned a US-merchant-first crypto-Charges product into a global stablecoin payments and payouts platform.
Operationally, Bridge now powers two pieces of the public Stripe API: the stablecoin-payment acceptance flow described above, and the Stripe Issuing + Connect rails that let platforms hold balances in USDC and pay out to bank accounts in local currency. SpaceX disclosed on a 2024 earnings call that it uses Bridge to repatriate Starlink revenue from markets where USD wires are slow or expensive — that exact use case is what the Stripe acquisition productizes.
What is Tempo, the Stripe + Paradigm blockchain?
Tempo is a payments-focused Layer 1 blockchain that Paradigm announced in September 2025 with Stripe as a founding partner. Tempo's design goal is a stablecoin-settlement chain with fixed predictable fees, regulator-friendly compliance hooks, and throughput tuned to payment workloads rather than general-purpose smart contracts. Stripe has confirmed it will support Tempo as a settlement option alongside Solana, Ethereum, and Polygon.
The "why build a chain" question is a fair one given that Stripe already settles on three. Two arguments are public. The first is fee predictability: Solana base fees are sub-cent but priority fees spike during MEV-heavy windows, and Ethereum base-layer gas can swing 20x in an afternoon. A payments chain that publishes a fee schedule the way Visa does removes that variance. The second is the compliance surface. A general-purpose L1 carries every category of traffic — DeFi, NFTs, gambling — and chain-level analytics treat that as one risk bucket. A payments-only chain narrows that surface and gives banks and acquirers a cleaner story for connecting onchain settlement to offchain compliance regimes.
Tempo is not live as of the May 2026 snapshot. Paradigm and Stripe have signaled a mainnet target inside 2026 but have not committed to a public date, and no validator set or token specifics have been disclosed. The relevant context for merchants is forward-looking: when Tempo ships, Stripe's stablecoin Charges will likely route to it by default for new merchants in the supported regions, with Solana and Ethereum remaining for buyers who already hold USDC on those chains. For broader stablecoin L1 context, see the stablecoin L1 chains guide, which covers Tempo, Plasma, Stable, and Codex.
How do merchants enable stablecoin payments on Stripe?
In Stripe Dashboard, a US-eligible merchant opens Settings → Payment methods, scrolls to the cryptocurrencies section, and toggles "USDC" on. Stripe runs a brief eligibility review — corporate KYB plus an attestation on the use of funds — and stablecoin appears as a payment method on existing Checkout sessions, Payment Links, and the Payment Element within hours of approval.
Three details trip up first-time integrators. One: stablecoin acceptance is a feature toggle, not a separate Stripe account. Existing webhooks, refunds, dispute flows, and Sigma reporting work without code changes — the payment_method.type on the Charge is crypto instead of card. Two: refunds work but with a wrinkle. A USDC refund returns USDC to the customer's originating wallet address; Stripe does not currently support refunding a stablecoin Charge to a card or bank account. Merchants integrating into existing return flows need to read the originating wallet from the Charge and route the refund accordingly. Three: payouts default to USD on the merchant's bank account. To receive stablecoin payouts instead, the merchant adds a designated payout wallet under Settings → Payouts and selects "USDC" as the payout currency.
Geographic availability has expanded in tranches. The October 2024 launch was US-only; through 2025 Stripe added the EU, UK, Canada, Australia, Singapore, and the UAE, plus pilot access for selected merchants in Brazil, Mexico, India, and Nigeria — 70+ countries as of the Q1 2026 update. The full eligibility list is published on the crypto payments docs; merchants in unsupported regions can still receive payouts from supported acquirers via Stripe Connect.
How does Stripe compare to Coinbase Commerce and other gateways?
Stripe and Coinbase Commerce target similar merchants but ship different products. Stripe folds stablecoin acceptance into the existing Payments API, charges 1.5% flat, and pays out in USD by default through the same rails the merchant already uses for cards. Coinbase Commerce is a standalone checkout product, charges 1%, and pays out in crypto unless the merchant signs up for an autoswap-to-fiat add-on.
The comparison below sorts the live US-available stablecoin checkout options by structural fit for an existing online merchant rather than crypto-native one. All four accept USDC; the divergence is in payout, reconciliation, and chain coverage.
Gateway | Fee | Payout | Chains | Integration |
Stripe | 1.5% | USD or USDC | Solana, Ethereum, Polygon (+ Tempo soon) | Same Payments API as cards |
Coinbase Commerce | 1.0% | USDC (USD via add-on) | Base, Ethereum, Polygon, Solana | Standalone checkout, hosted |
BitPay | 1.0% | USD bank or crypto | Ethereum, Polygon, Bitcoin + 10 others | Standalone, plugins for Shopify |
PayPal Crypto | ~1.5% | PYUSD or USD | Ethereum, Solana | Within PayPal merchant account |
For a merchant already running Stripe, the integration cost of toggling on crypto is roughly zero engineering hours — the dominant reason most multi-rail merchants who add stablecoins in 2026 are doing it through Stripe rather than swapping in a new processor. Coinbase Commerce wins on raw fee and on Base-native settlement, which matters for crypto-native commerce; PayPal Crypto is gated to PayPal merchants and routes mostly through PYUSD ($3.4B market cap per CoinGecko, May 2026) rather than USDC.
What changed from Stripe's 2014 Bitcoin checkout?
Stripe launched Bitcoin acceptance in March 2014 as the first major payments processor to support a cryptocurrency, then deprecated the product in April 2018 citing transaction fees, confirmation latency, and price volatility. The 2024 stablecoin relaunch fixes all three: USDC holds a dollar peg, Solana settles in seconds for fractions of a cent, and Stripe handles the FX so merchants quote and receive USD.
The 2018 shutdown post-mortem on the Stripe blog made the technical case plainly: median Bitcoin confirmation times had risen above ten minutes, fees were intermittently above $20, and the user experience of a "pay-then-wait" checkout collapsed conversion. None of those constraints apply to USDC on Solana. Sub-second finality at sub-cent fees is the baseline; Stripe quotes USD-denominated prices and absorbs the conversion at the moment the payment lands; the buyer experience is "scan, sign, done" inside the same Stripe-hosted Checkout. The 10-year gap between v1 and v2 is mostly a story of waiting for the underlying rail to catch up.
Where does Eco fit?
Stripe accepts USDC on Solana, Ethereum, and Polygon; many merchants and customers hold USDC on Base, Arbitrum, Optimism, or other L2s. Bridging between those chains before checkout is the friction Eco Routes removes — a customer paying a Stripe stablecoin invoice from a Base wallet can route USDC into one of Stripe's supported chains in a single transaction, with the destination address scoped to that specific Charge.
Eco operates as routing infrastructure across 15 supported chains; merchants and apps integrate via the Routes API, and end users see a single "pay" action that handles the cross-chain step. For a high-level view of where stablecoin payouts terminate, see the convert USDC to bank account guide.
Sources and methodology. Product details verified against Stripe's October 2024 stablecoin announcement, the crypto payments docs, the Bridge.xyz acquisition press release, and Paradigm's Tempo announcement. Stablecoin supplies pulled from DeFiLlama on May 4, 2026. Interchange comparison cites the Federal Reserve Bank of Kansas City payments research briefings (2023). Fee figures and country availability refresh quarterly.

