Stripe OUSD integration
Stripe provides payment processing and financial tools for businesses, including Treasury balances, payouts and card issuing. It completed its acquisition of stablecoin infrastructure company Bridge in February 2025. OUSD support depends on the individual Stripe product. [1] [2] [3]
Holding OUSD
Can an account hold OUSD? An eligible Treasury financial account can store OUSD, with Bridge custody. It holds one stablecoin storage currency at a time. [4] [1]
In Dashboard Settings, open Business → Bank accounts and currencies. Enable OUSD for the financial account and save. Each account holds one stablecoin storage currency at a time; it cannot store OUSD and USDC simultaneously. [4]
To fund from a wallet, open Balances → Add funds → Crypto transfer, choose the network and use its deposit instructions. This requires administrator access. The documented incoming asset is USDC, or USDC.e on Tempo, converted into the storage currency; these are not native OUSD deposit instructions. [5] [4]
US businesses have public-preview access; the other listed eligible countries require private-preview access. Bank funding first enters a supported fiat balance before conversion to OUSD. [1] [5]
Sending payouts from OUSD
What reaches the recipient? Treasury can fund payouts from OUSD, but the documented external assets are supported fiat, USDC or USDC.e. Native OUSD recipient delivery is not established by this product guide. [6]
For your own wallet, open Treasury → Transfer, select or add the external account, review the costs and destination, then select Review → Transfer. For a third party, use Treasury → Payouts → Send money, choose or onboard a recipient, enter the amount and method, select Review → Send, then track the payout. [6] [7]
Crypto delivery uses USDC on Arbitrum, Avalanche C-Chain, Base, Ethereum, Optimism, Polygon, Solana and Stellar; Tempo uses USDC.e. Bank payouts convert to the destination currency. Sender, recipient and payout-method eligibility must each be checked; US access is public preview and other listed countries use private preview. [6]
Which interface? Treasury documents Dashboard transfer and payout flows. Global Payouts also has API paths: OutboundPayments and private-preview PayoutIntents. Its generic USD examples do not independently establish an OUSD route; confirm funding asset, recipient and payout method for your account. [7] [6]
Connect is a separate, fiat-funded USDC flow. A US platform must obtain private-preview approval and complete due diligence, enable the crypto method and Express Dashboard, then use the Transfers API. Recipients must be eligible individuals or sole proprietors; companies, nonprofits, and US recipients in New York or Hawaii are excluded. This does not establish OUSD delivery. [8]
Issuing OUSD-funded cards
Stripe’s customer Issuing card programs are in private preview; confirm OUSD funding for the chosen integration. [2]
For wallet-funded consumer cards, complete Stripe and Bridge program onboarding and connect the accounts using Bridge’s installation link. Request the Bridge customer’s cards endorsement, then use the returned cardholder ID with Stripe Issuing. Create a card within 24 hours before the consumer endorsement expires. Confirm OUSD and the chain with Bridge; configure the approved funding wallet and custody type. Noncustodial funding also needs spending approval. [9]
For commercial wallet-funded programs, Bridge returns a connected-account ID after business endorsement approval. Create authorized cardholders and cards under that account. [9]
For financial-account customer cards, request preview access and configure an eligible US or European Connect platform. Onboard connected accounts in approved markets, activate storage and card capabilities, then create and fund USDC financial accounts before issuing cards. This separate recipe does not establish OUSD funding. [2] [10]
For cards spending your own business’s Treasury stablecoin balance, open Cards → Create card and follow the cardholder, card-type and activation steps. This is a separate product: US public preview, with country-specific invitation access elsewhere. [11]
Converting OUSD
Which conversion is available? Treasury converts OUSD to or from supported fiat balances in the same eligible financial account. The Dashboard flow is documented; the general currency-conversion API is private preview. [12]
Open Treasury → Convert. Select the source and destination balances, enter the amount, review the displayed terms and submit. Both currencies must be supported in that account. [12]
USD/OUSD conversion does not involve foreign exchange; other fiat pairs use the current rate. This does not imply zero fees. The account cannot directly switch between OUSD and USDC storage balances through this flow. The documented stablecoin steps use the Dashboard; the general conversion API is private preview. [12]
Managing OUSD custody
Bridge custodies OUSD held in Stripe Treasury financial accounts. [4]
Enable OUSD in the financial account, then review movements in Transactions → All activity → Financial account. Filter to OUSD and export transactions for reconciliation when an accounting integration cannot read them. This is managed financial-account custody, not a self-custody wallet-creation API. [4]
Accepting OUSD payments
Can customers pay in OUSD? Stripe’s September 30, 2026 launch announcement explicitly includes OUSD payment acceptance, and its OUSD overview links to Payments. The detailed accepted-token table still names only USDC, USDP and USDG. This conflict remained unresolved on October 12, 2026; confirm the merchant, network and integration with Stripe before implementation. [13] [14] [15]
Get OUSD-specific confirmation for your merchant, network and integration before enabling it in your product. After approval, request Stablecoins and Crypto in payment-method settings and wait until it is active. The documented Checkout flow uses USD line items; dynamic payment methods display eligible options. [15] [16]
The setup guide excludes New York; the product overview lists additional markets in private preview. Its published customer limit is USD 10,000 per transaction. Payments settle to fiat; refunds return as stablecoins to the original wallet. Confirm the exact settlement currency for your account. The documented USDC test flow cannot validate OUSD acceptance. [15] [16]
Related references
- Compare all providers
- OUSD networks and exact token addresses
- Handling payment events, retries and reconciliation
References and last updated
Reviewed 2026-10-12 · Updated 2026-10-12. This profile summarizes provider documentation. No live integration independently tested.
- Stripe Treasury: stablecoin balances ↗
Published date not provided · Reviewed 2026-10-12 - Stripe: stablecoin-backed cards ↗
Published date not provided · Reviewed 2026-10-11 - Stripe: Bridge acquisition completed ↗
Published 2025-02-04 · Reviewed 2026-10-11 - Stripe Treasury: Store funds ↗
Published date not provided · Reviewed 2026-10-12 - Stripe Treasury: Add funds ↗
Published date not provided · Reviewed 2026-10-12 - Stripe Treasury: Transfer and send funds ↗
Published date not provided · Reviewed 2026-10-12 - Stripe Global Payouts: Send money ↗
Published date not provided · Reviewed 2026-10-12 - Stripe Connect: stablecoin payouts ↗
Published date not provided · Reviewed 2026-10-12 - Stripe: Stablecoin-backed cards for Bridge, Privy or third-party wallets ↗
Published date not provided · Reviewed 2026-10-11 - Stripe: Cards for financial accounts ↗
Published date not provided · Reviewed 2026-10-11 - Stripe Treasury: Cards ↗
Published date not provided · Reviewed 2026-10-11 - Stripe Treasury: Convert funds ↗
Published date not provided · Reviewed 2026-10-12 - Stripe: OUSD is now live on Stripe ↗
Published 2026-09-30 · Reviewed 2026-10-12 - Stripe: Open USD product integration overview ↗
Published date not provided · Reviewed 2026-10-12 - Stripe: Stablecoin payments ↗
Published date not provided · Reviewed 2026-10-12 - Stripe: Accept stablecoin payments with Checkout ↗
Published date not provided · Reviewed 2026-10-11
Claim-level sources, product review dates and evidence status are retained in the downloadable dataset.