Holding OUSD

Hold OUSD when your product needs a dollar-denominated balance that stays available between payments. For example, a business cash-management app could retain funds in OUSD, show the spendable balance, and use it later for supplier payouts.

The balance may live in a managed financial account or an onchain wallet. Choose that model before building the balance screen.

Understand the balance

A stablecoin balance is an amount of a particular asset. Keep the asset held, the asset deposited, and the asset paid out as separate fields: a service may convert between them.

Custody determines who safeguards the funds and authorizes movement. Use Creating OUSD wallets if each customer needs an address; use Managing OUSD custody to choose the control arrangement.

Define the requirements

• Whose money is held: the business’s own funds or a named customer’s funds
• Whether you need an account balance, an onchain wallet, or both
• Approved business and beneficiary countries, funding methods and withdrawal routes
• Fees, minimum amounts, access restrictions and the distinction between pending and spendable funds

Build the holding workflow

1. Establish the owner and account. Complete the chosen service’s onboarding and bind its account or wallet ID to the correct owner in your application.
2. Enable the asset and funding route. Confirm that the resulting balance is OUSD. For an onchain deposit, verify the exact network and token address accepted by the service.
3. Fund using the issued instructions. Keep the deposit asset, amount and reference. An OUSD storage setting does not establish that an address accepts direct OUSD deposits.
4. Confirm the credit. Record fees and any conversion separately. Update spendable funds only when the service reports the relevant credit as available.
5. Reconcile and expose the balance. Compare your records with the provider or chain and retain the original transaction references. Use the shared events and reconciliation workflow.

Example: a business cash account

An illustrative account record separates the funding deposit, the conversion into OUSD, the available OUSD balance, and any amount reserved for a pending payout. That prevents a bank debit or an unconfirmed deposit from being displayed as spendable OUSD.

When funds leave, use Sending payouts from OUSD to choose what the recipient receives.

References and review

The provider directory and activity sections below link to the official product documentation behind each route. These general workflows are application-design guidance; provider-specific steps, eligibility and asset limits are in those profiles.

Documentation reviewed October 11, 2026. Modified October 12, 2026. No live integration independently tested.

Available providers

• Bridge: Bridge custodial wallets explicitly support OUSD on Base, Ethereum, Solana and Tempo.
• Coinbase: Coinbase documents buying and managing Open USD on its US exchange; business holding arrangements need confirmation.
• Privy: Privy can expose a Bridge-custodied OUSD wallet and its balance inside an application.
• Stripe: 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.
• Visa: VSP supports OUSD balances for selected institutional clients in beta.