Bridge OUSD integration
Bridge builds stablecoin APIs for moving funds, creating custodial wallets and issuing tokens. Stripe acquired Bridge in February 2025. Bridge Building Inc. currently issues OUSD; the separate Bridge National Trust Bank remains in organization and is not the issuer. [1] [2]
Holding OUSD
Bridge custodial wallets explicitly support OUSD on Base, Ethereum, Solana and Tempo. [3]
Create the beneficiary’s wallet, then fund it using an approved orchestration route or a supported direct deposit. Read balances and wallet history, and process bridge_wallet.activity events for deposits and withdrawals. Keep a company treasury under the company’s own customer ID. [4] [3]
Wallet accounting uses whole US cents. Production fund flows need Legal & Compliance approval; wallet geography restrictions and the EEA restriction described under Creating OUSD wallets apply before funding. [3] [5]
Sending payouts from OUSD
Bridge Transfers can deliver OUSD or another supported destination asset; check each route direction. [6] [5]
Create a transfer with the amount, customer, source, destination and idempotency key. [6]
For external funding, follow source_deposit_instructions, including the deposit reference. For a Bridge-wallet source, retrieve the wallet and supply initiation context when initiation_required is true; Bridge pulls the wallet balance. [6]
Track the transfer to payment_processed and retain the final transaction hash. Reconcile refunds and exception states separately. [7]
Handle transaction compliance reviews through Bridge’s RFI API (beta). Retrieve GET /v0/rfis/{id}, inspect requested_items and their response_types, then submit answers to POST /v0/rfis/{id}/responses with customer:write scope. This API covers transaction RFIs, not customer RFIs; Dashboard Support and email responses remain available. An RFI response is not confirmation that a paused transfer completed. [8] [9]
The guide’s Tempo/OUSD request conflicts with Polygon and Stellar in other examples; those examples do not prove OUSD support on those chains. [6] [7]
The reviewed routes list OUSD destinations on Base, Ethereum, Solana and Tempo, and OUSD sources on Base, Ethereum, Solana and Bridge Wallet; the reviewed route-explorer matrix did not establish a Tempo-source route. USD ACH-to-OUSD has a USD 1 minimum; listed Base/Ethereum/Solana OUSD-to-USD ACH or wire routes have a 1 OUSD minimum, after developer fees. Recheck the current route and minimum before submission. EEA users are limited to USDC and EURC. [5] [10]
Issuing OUSD-funded cards
Bridge wallet-funded cards use Stripe Issuing; current OUSD card funding still needs confirmation. [11]
Complete coordinated Bridge and Stripe program onboarding and connect the accounts using Bridge’s installation link. [11]
Request the cards endorsement for the Bridge customer. Consumer onboarding returns a Stripe cardholder ID for creating the Issuing card; create it within 24 hours before the endorsement expires, or renew the KYC confirmation. [11] [12]
Configure the approved funding wallet with the current Stripe integration. Noncustodial wallets need the required onchain spending approval; Bridge wallets need sufficient funds. [13] [11]
Confirm OUSD, the chain and the program’s geographic eligibility. The legacy Bridge card-account provisioning endpoint is deprecated; use the current Stripe Issuing integration. [13] [14]
Minting and redeeming OUSD
Open Standard network partners can arrange direct OUSD access through Bridge. [2]
Complete the applicable onboarding and agree the funding and destination route. Bridge handles minting and reserve allocation, or burning and release of funds, within the approved issuance flow. The public issuance overview does not provide a universally available OUSD mint endpoint. [2] [15]
Follow the transfer’s actual deposit instructions and reconcile the destination credit. For bank redemption, the wallet off-ramp requires a verified customer, funded wallet and external bank-account reference; its USDB example must not be copied as an OUSD request. [6] [16]
Access and cost: partner onboarding and approval apply to each route; the issuance overview does not establish one global API release stage. Bridge announces no Bridge minting or redemption fee. Developer charges, network costs, funding/payout rail charges and conversion costs still need a quote for the chosen operation. [2] [15] [17]
Route checks: the current matrix lists USD ACH into OUSD on Base, Ethereum, Solana and Tempo, and OUSD from Base, Ethereum or Solana into USD ACH or Wire. Each listed minimum is 1 in the source currency, after developer fees. No OUSD@Tempo source entry was established; EEA users are limited to USDC and EURC. [5] [10]
Creating OUSD wallets
Bridge provides a direct custodial-wallet API with explicit OUSD support on four networks. [3]
After onboarding and production fund-flow approval, create the beneficiary customer with country and, where applicable, US state. Create a wallet through POST /v0/customers/{customerId}/wallets with the selected chain; save its wallet ID and receiving address. [4] [3]
The OUSD wallet matrix lists Base, Ethereum, Solana and Tempo. Wallets exclude New York, Texas, Kenya, Australia, Japan, Singapore, Malaysia, Vietnam and Indonesia. Broader eligibility rules also apply; EEA users are limited to USDC and EURC. Check both the business and beneficiary before provisioning and funding. [3] [5]
Converting OUSD
Bridge documents conversion into and out of OUSD using approved transfer routes. [18]
Access and route: confirm the source asset, destination asset and both chains in the Route Explorer, plus account and beneficiary eligibility. USDC sources on Base, Ethereum, Solana, Tempo or in Bridge Wallet are listed into OUSD on its four native networks. Do not infer reverse routes, all-pairs support or a Tempo OUSD source route. EEA routes do not support OUSD. [5]
Inventory wallets, liquidation addresses, reusable transfer templates and virtual accounts. In the migration guide, USDx includes USDC; it is a placeholder for the existing asset, not a token identifier. Upgrade legacy Prefunded Account integrations to Wallet APIs first. [18]
Schedule downtime, pause deposits and withdrawals, and let in-flight transfers finish. Change destination currency on liquidation addresses, reusable templates and virtual accounts. Only close eligible awaiting-funds transfers; later-stage transfers must settle. [18]
Convert each wallet balance with a unique idempotency key for that operation. Wait for payment_processed, reconcile OUSD balances and late USDC deposits, then resume. Cross-chain migration needs new destination wallets/accounts and routes. Prepare rollback only after verifying its reverse route. [18]
Cost and limits: inspect the route quote, developer fees and post-fee minimums before migrating. A no-mint/redemption-fee announcement does not establish zero total conversion or network cost. Generic migration examples must not expand OUSD beyond Base, Ethereum, Solana and Tempo. [17] [10] [2] [19]
Managing OUSD custody
Bridge offers custodial OUSD wallets, subject to approved production fund flows and geographic restrictions. [3]
Identify the beneficiary and obtain Bridge Legal & Compliance approval for the fund flow before accepting deposits. Use Bridge Orchestration APIs for transfers; direct deposits require a supported token and chain. Apply the same customer and geographic checks described under Creating OUSD wallets. [3]
Reconcile wallet balances and history in whole US cents, rather than treating that accounting precision as the token’s onchain decimals. Retain the wallet and customer references for each movement. [3] [4]
Testing integrations
Bridge Sandbox supports simulated payment activity and associated webhooks. It does not submit transactions to live banks or blockchains, so simulated completion is not evidence of OUSD settlement. [20]
Obtain sandbox access, create a sandbox customer and simulate its compliance state. Configure and activate a sandbox webhook endpoint for the event categories you need. [20]
Run a supported simulation: liquidation deposits produce liquidation_address.drain; virtual-account deposits produce virtual_account.activity and applicable transfer events; wallet deposits produce bridge_wallet.activity. [20]
Retrieve the resulting resource or wallet history and compare it with received events. Exercise duplicates, delays and failures in your application separately. Event coverage and timing may differ from production; do not assume blockchain-testnet or every OUSD route support. [20]
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-26. This profile summarizes provider documentation. No live integration independently tested.
- Stripe: Bridge acquisition completed ↗
Published 2025-02-04 · Reviewed 2026-10-11 - Bridge: Open USD is live, issued by Bridge ↗
Published 2026-09-30 · Reviewed 2026-10-12 - Bridge: Custodial wallets ↗
Published date not provided · Reviewed 2026-10-12 - Bridge: Create, fund and reconcile wallets ↗
Published date not provided · Reviewed 2026-10-11 - Bridge: Supported blockchains and fiat rails ↗
Published date not provided · Reviewed 2026-10-12 - Bridge: Transfers ↗
Published date not provided · Reviewed 2026-10-11 - Bridge: Transfer states ↗
Published date not provided · Reviewed 2026-10-11 - Bridge: transaction RFI API and responses ↗
Published date not provided · Reviewed 2026-10-26 - Bridge: Developer changelog ↗
Published date not provided · Reviewed 2026-10-26 - Bridge: Transaction minimums ↗
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 - Bridge: Card customer eligibility ↗
Published date not provided · Reviewed 2026-10-11 - Bridge: Card funding strategies ↗
Published date not provided · Reviewed 2026-10-11 - Bridge: Deprecated card-account provisioning ↗
Published date not provided · Reviewed 2026-10-11 - Bridge: Minting and burning ↗
Published date not provided · Reviewed 2026-10-12 - Bridge: Wallet off-ramp ↗
Published date not provided · Reviewed 2026-10-11 - Bridge: Developer fees ↗
Published date not provided · Reviewed 2026-10-12 - Bridge: Migrating to OUSD ↗
Published date not provided · Reviewed 2026-10-12 - Bridge: OUSD overview ↗
Published date not provided · Reviewed 2026-10-12 - Bridge: Set up a sandbox environment ↗
Published date not provided · Reviewed 2026-10-12
Claim-level sources, product review dates and evidence status are retained in the downloadable dataset.