Converting OUSD
Convert OUSD when a product needs to exchange it for another supported asset, or turn existing funds into OUSD. For example, a treasury app could convert a supported fiat balance into OUSD before paying suppliers, then reconcile the source debit and destination credit.
Separate conversion from movement
Section titled “Separate conversion from movement”Conversion changes the asset held. A transfer changes where funds are held; a cross-chain flow may do both. Native OUSD on two networks does not prove that a provider offers a direct bridge between them.
An exchange trade is also different from minting or redemption. Use the operation that matches your account and actual source of funds.
Define the requirements
Section titled “Define the requirements”- Source asset and network, destination asset and network, and ownership on each side
- Exact supported pair and direction, eligibility, minimums, fees and any quoted rate
- Quote expiry, required funding instructions and expected settlement timing
- How pending transfers or late deposits affect a larger balance migration
Build the conversion workflow
Section titled “Build the conversion workflow”- Confirm the pair and route. Verify both sides against the provider’s current product support. Use Networks and contracts when either side is onchain.
- Prepare the destination. Establish the receiving account or wallet before initiating a conversion that moves funds there.
- Read available funds and review the quote. Store exact amounts, fees and the quote reference where the product supplies one. A dollar-equivalent display value is not an executable quote.
- Submit the approved operation once. Keep its reference and retry identity. Retrieve an uncertain result before attempting another conversion.
- Reconcile the resulting asset. Match the source debit, fees and destination credit before marking the new balance spendable.
Example: changing a product’s storage asset
Section titled “Example: changing a product’s storage asset”An illustrative migration includes more than converting the current balance: pause new activity, resolve in-flight work, change approved deposit and payout routes, verify the converted balance, then resume. Decide how late deposits in the former asset will be handled; a label change does not convert them.
Provider migration guides define which route changes are actually required. Use Holding OUSD for the resulting balance and the shared reconciliation guide for delayed or failed conversion events.
References and review
Section titled “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
Section titled “Available providers”- Bridge: Bridge documents conversion into and out of OUSD using approved transfer routes.
- Coinbase: Coinbase documents a US exchange purchase flow; institutional 1:1 conversion is a separate listed path.
- Mastercard: Open Standard lists Mastercard for buying, selling and swaps through API or portal access.
- Stripe: 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.