Stripe accepts stablecoin payments from customers worldwide, supports USDC on Tempo, Ethereum, Solana, Polygon, and Base plus USDP and USDG in the US, settles the payment into the merchant's Stripe balance in local currency, and charges 1.5% of the transaction amount in USD (Stripe's stablecoin payments docs, Stripe pricing, both read September 15, 2026). 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.
​

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. Stripe documents that completed stablecoin payments settle in the merchant's Stripe balance in the merchant's local currency, and that customer transactions are capped at 10,000 USD each.
​

The product sits inside the standard Stripe Payments API. A merchant requests the Stablecoins and Crypto payment method in the Dashboard's payment method settings, and it becomes active after Stripe reviews the request. At checkout the customer selects Crypto and Stripe redirects them to crypto.stripe.com, where they pick a currency and payment network and connect their wallet (Stripe's accept stablecoin payments guide). From the merchant's accounting view, the row looks indistinguishable from a card payment.
​

The relaunch landed in October 2024, when Paxos announced the stablecoin payments platform behind Stripe's Pay with Crypto product with Stripe as its first customer (Paxos, October 15, 2024). USDC's circulating supply was about $73.4B on September 15, 2026 (DeFiLlama), and Stripe is wiring directly into that supply rather than building its own.
​

A customer selects Crypto in Stripe Checkout, lands on crypto.stripe.com, picks a currency and network, connects a wallet such as Phantom, MetaMask, or Coinbase Wallet, and signs the transfer. Stripe credits the merchant once the transaction confirms, and payout timing varies by network per Stripe's docs. The merchant payout otherwise follows Stripe's normal schedule.
​

Three pieces of the flow matter for merchants. First, the buyer picks the network at checkout from Stripe's supported list, and the merchant does not have to care 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.
​

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.
​

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's own docs now list Tempo alongside Ethereum, Solana, Polygon, and Base as a network USDC payments can arrive on.
​

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.
​

Stripe now lists Tempo as one of the networks USDC payments can arrive on, alongside Ethereum, Solana, Polygon, and Base (Stripe's stablecoin payments docs, read September 15, 2026). 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.
​

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 follow the merchant's normal Stripe payout schedule, because the stablecoin payment has already settled into the Stripe balance in local currency.
​

Geographic availability is asymmetric. Customers can pay from anywhere outside sanctioned countries, while Stripe documents merchant eligibility for stablecoin payments as businesses in all US states except New York (Stripe's accept stablecoin payments guide, read September 15, 2026); merchants in unsupported regions can still receive payouts from supported acquirers via Stripe Connect.
​

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.

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 (about $2.8B in circulation on September 15, 2026 per DeFiLlama) rather than USDC.
​

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.
​

Stripe accepts USDC on Tempo, Ethereum, Solana, Polygon, and Base; many merchants and customers hold USDC on 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 on September 15, 2026 against Stripe's stablecoin payments docs, Stripe's accept stablecoin payments guide, Stripe's pricing page, the Paxos launch announcement of October 15, 2024, the Bridge.xyz acquisition press release, and Paradigm's Tempo announcement. Stablecoin supplies pulled from DeFiLlama on September 15, 2026. Interchange comparison cites the Federal Reserve Bank of Kansas City payments research briefings (2023). Fee figures and country availability refresh quarterly.
​

How to accept USDC payments
​Stablecoin gateways for Shopify
​Best crypto payment gateways 2026
​Bridge.xyz stablecoin API explained
​Stablecoin L1 chains pillar
​Convert USDC to bank account
​