Bridge.xyz is a stablecoin payment API that lets businesses accept, hold, convert, and pay out stablecoins through a single integration. Founded in 2022 by Sean Yu (ex-Square Cash App) and Zach Abrams (ex-Coinbase), Bridge was acquired by Stripe in October 2024 for $1.1 billion — the largest acquisition in Stripe's history at the time. The company sits between traditional banking rails and onchain settlement, and most teams describe it as "Stripe for stablecoins" because that is now literally what it is.
​

This guide covers what Bridge does, the four APIs it exposes, supported stablecoins and chains, pricing, and how it differs from Circle's CCTP and Coinbase Commerce. If you are evaluating stablecoin infrastructure for cross-border payroll, marketplace payouts, or a neo-bank product, this is the orientation.
​

Bridge is API-first stablecoin infrastructure for B2B. It handles fiat-to-stablecoin onramps, stablecoin custody, conversion between stablecoins, and payouts back to fiat through ACH, SEPA, and SWIFT — all behind REST endpoints, with KYC, KYB, and Travel Rule compliance baked in.
​

The pitch is that a developer team should not have to integrate a custodian, a market maker, a banking partner, an onramp, an offramp, and a compliance vendor separately. Bridge bundles those into one contract and one API surface. The customer base reflects that positioning: fintechs building remittance products, payroll companies paying contractors in 40 countries, marketplaces with international sellers, and neo-banks adding stablecoin balances to consumer accounts.
​

Stripe announced the $1.1 billion acquisition on October 20, 2024. Patrick Collison called stablecoins "room-temperature superconductors for financial services" in the announcement post. The deal closed in early 2025.
​

For Bridge customers, the practical change has been distribution. Bridge APIs now sit alongside Stripe's payment stack, and Stripe's existing card-issuing and treasury customers can layer stablecoin rails on top without picking a new vendor. Stripe rolled out USDC payouts in 70+ countries in 2025 using Bridge as the underlying layer. For competitors, the change is harder to read: Bridge went from a focused startup to the stablecoin arm of the most distribution-rich fintech in the world overnight.
​

Bridge ships its product as four named APIs that can be used independently or together.
​

Wallets API. Programmatically create custodied stablecoin wallets for end users. Wallets support deposits and withdrawals across multiple chains and stablecoins. Bridge holds keys; the developer holds an account abstraction.
​

Orchestration API. Move value across chains and stablecoins automatically. Define a destination (e.g., "deliver 10,000 USDC on Base") and Bridge handles the conversion, bridging, and settlement under the hood. This is the API most teams care about — it abstracts the routing problem.
​

Payout API. Send funds out to traditional bank accounts globally. US ACH, SEPA in Europe, SWIFT wire for everything else, plus local rails in select corridors. Recipient KYC is handled inside the flow.
​

Convert API. Swap between supported stablecoins (USDC ↔ USDT ↔ EURc ↔ PYUSD) at quoted rates. Useful when payer holds one stablecoin and payee wants another.
​

Bridge supports the four stablecoins that dominate B2B payment volume today: USDC (Circle), USDT (Tether), EURc (Circle's euro stablecoin), and PYUSD (PayPal USD, issued by Paxos).
​

Supported chains include Ethereum, Solana, Polygon, Arbitrum, Base, Tron, and Stellar. Tron and Stellar matter for cross-border payments — Tron holds the bulk of USDT remittance volume globally, and Stellar is the dominant rail for MoneyGram and several African corridors. Base is included as Coinbase's L2 because so much fintech volume has migrated there since Coinbase's USDC fee waiver.
​

Public pricing on bridge.xyz/pricing lists roughly 10 basis points (0.10%) plus the network fee as the standard fee for stablecoin movement. Fiat payouts add the underlying rail cost (ACH is near-zero, SWIFT is typically $15–$30 per wire). Volume customers negotiate custom pricing.
​

For context, Coinbase Commerce charges 1% on stablecoin checkout. Stripe's card processing is 2.9% + $0.30. The KC Fed estimates traditional B2B card interchange runs $0.50–$0.80 per transaction on large-ticket commercial cards. Ten bps on a $50,000 supplier payment is $50 — versus several hundred dollars on a card, or a flat $25 SWIFT wire that takes two business days.
​

Circle's Cross-Chain Transfer Protocol (CCTP) is a burn-and-mint primitive for moving USDC between chains natively. It is free at the protocol level — you pay only gas — and it is permissionless. Anyone can integrate CCTP directly.
​

Bridge is a managed orchestration layer that sits above primitives like CCTP. Bridge will use CCTP, LayerZero, or its own settlement paths under the hood to deliver a destination state; the developer never sees the routing decision. CCTP solves the "move USDC from chain A to chain B" problem. Bridge solves the "I have USD in a bank account and I need to pay someone in EURc on Polygon next Tuesday" problem.
​

The two are complements more than competitors. CCTP is rails; Bridge is the booking system.
​

Coinbase Commerce is a merchant checkout product. A Shopify or WooCommerce store drops in a Commerce button, customers pay in crypto at the till, and Coinbase settles to the merchant. It is consumer-facing at the moment of payment.
​

Bridge has no checkout widget. It is a developer API for programmatic flows: payroll runs, marketplace seller payouts, treasury rebalancing, contractor invoices. The end user often never touches a crypto UI — they see a deposit in their local bank account, and Bridge handled the stablecoin path invisibly.
​

For an e-commerce site selling DTC, Coinbase Commerce or a gateway like BitPay is the right tool. For a payroll fintech moving $50M/month to contractors in 40 countries, Bridge is the right tool. For a marketplace doing both, increasingly the answer is "use both — they do not overlap."
​

Cross-border payroll. A US-based company pays 200 contractors across Argentina, Nigeria, the Philippines, and Vietnam. Funding originates in USD via ACH, Bridge converts to USDC, routes through Tron or Stellar based on corridor economics, and settles to local bank accounts or stablecoin wallets at the recipient's choice.
​

Marketplace payouts. A global freelance platform holds funds in stablecoins, lets sellers choose payout currency and rail, and pays out daily instead of weekly without bleeding margin to wire fees.
​

Neo-bank stablecoin accounts. A consumer fintech offers a USD-denominated stablecoin savings balance to users in emerging markets. Bridge handles custody, conversion, and the bank-rail bridge on both ends.
​

Treasury and B2B AR/AP. A SaaS company invoices international customers in USDC and settles supplier payments in EURc or local fiat, depending on which side wants to bear the conversion cost.
​

Eco and Bridge sit at different layers. Bridge is a custodial B2B API focused on the fiat ↔ stablecoin boundary and bank-rail payouts. Eco is non-custodial stablecoin infrastructure for moving USDC across chains in seconds via intent-based routing. A fintech could use both: Bridge for fiat onramp/offramp and KYC, Eco Routes for the onchain cross-chain leg when the destination is another L2 instead of a bank account. For purely onchain, in-app stablecoin movement (e.g., a wallet that needs USDC on Base to settle to USDC on Arbitrum), Eco is faster and non-custodial. For fiat payouts to a bank in Lagos, Bridge is the right tool.
​

Product detail and supported assets cross-checked against bridge.xyz/docs (May 2026). Acquisition figures from Stripe's October 20, 2024 announcement and Forbes coverage. Founder background from Bridge's "About" page and Bloomberg's October 2024 reporting on the deal. CCTP detail from Circle's developer documentation. KC Fed reference for commercial card interchange. Pricing from bridge.xyz/pricing as of May 2026; enterprise pricing varies.
​