Open Standard OUSD Stablecoin: Architecture, Reserves, Multi-Chain Design

Systems analysis only. This article describes architecture and engineering trade-offs. It is not investment, legal or financial advice.

For years the dollar stablecoin market has been a duopoly with a very thin layer of engineering diversity: two issuers, a handful of chains, and a long tail that never reached escape velocity. On October 1, 2026, that picture changed in a way that is architectural rather than merely commercial. Open Standard launched the OUSD stablecoin, issued by Stripe’s Bridge, seeded with more than $1 billion of liquidity from five founding partners, and wired into the card networks, a major exchange and a major commerce platform from day one.

It matters now because OUSD is not a startup trying to buy distribution. Visa, Mastercard, Coinbase, Shopify and Stripe already sit on the payment flows that a stablecoin needs in order to be useful, and they have taken equity-linked incentives to route volume through it. For engineers, that turns a market-structure story into a design question: what do you change in your treasury, settlement and checkout code when the default stablecoin on a major payments platform is a consortium asset?

By the end you will understand how the issuance and redemption path works, how the reserve design and attestations fit together, why four chains were chosen, what the consortium incentive model implies, and what to monitor if you integrate it.

What this covers: the market context, the reference architecture (issuer, reserves, chains), a mint-to-settlement walk-through, an integration decision framework, failure modes, practical recommendations, and an FAQ. Facts below come from launch coverage and Stripe’s own announcement; anything not published is labelled as unknown.

Context and Background

The dollar stablecoin market is large and concentrated. Launch coverage citing August 2026 data puts total supply at roughly $308 billion, with Tether’s USDT at about 59 percent and Circle’s USDC at about 23 percent. Together they hold more than 80 percent of the market. Those are reported figures from the launch reporting, and market shares drift month to month, so treat them as a snapshot rather than a constant.

That concentration shapes the economics. An issuer earns the yield on the reserve assets backing its tokens, and the party that controls distribution captures most of the value. Exchanges, wallets and payment processors have historically moved huge volume in other people’s stablecoins while earning little from the float. Open Standard is an attempt to invert that: share the issuer economics with the distributors, in exchange for them making the token a default.

The regulatory backdrop also matters. The US GENIUS Act, signed in July 2025, created a federal framework for payment stablecoins, including one-to-one reserve backing with high-quality liquid assets, redemption rights and issuer disclosure. Rulemaking is still maturing, and our earlier analysis of the proposed GENIUS Act rules on reserves and capital walks through what reserve architecture a compliant issuer has to build. OUSD lands in that environment with a reserve design that already looks like what the framework asks for: segregated custody, regulated institutions and regular attestation. Whether the issuer’s final legal status maps onto a specific GENIUS Act category is not something the launch materials state, so we do not assume it.

Meanwhile the payments side has been preparing for this. Card networks have been building stablecoin settlement paths, banks have formed consortia, and Stripe acquired Bridge in 2024 for a reported $1.1 billion to own the orchestration layer. Our overview of stablecoin payment infrastructure in 2026 covers that stack; this post zooms into one new asset that sits on top of it. For the primary announcement of how Stripe treats the asset, see Stripe’s OUSD announcement.

What was actually announced

The facts that are reasonably well established from launch reporting and Stripe’s own post are these:

OUSD is a dollar-pegged stablecoin issued by Bridge, a Stripe company, redeemable one to one for US dollars.
It is live on four networks: Base, Ethereum, Solana and Tempo. Tempo is Stripe’s default configuration.
Reserves are reported to be held at BlackRock, Lead Bank and BNY, with monthly reserve attestations.
The founding partners are Coinbase, Mastercard, Shopify, Stripe and Visa. They committed more than $1 billion for initial liquidity and received equal initial equity stakes in Open Standard.
More than 200 partner institutions are reported, up from over 140 initial backers at the June announcement.
Minting and redemption carry no fee through the Stripe, Visa and BVNK platforms, and Coinbase access began on October 1. Revenue comes from a small transaction fee, whose exact level was not published in the sources we reviewed.
Partners earn rewards in proportion to the supply and activity they drive, with a chance to earn equity.

What was not announced, or at least not in the sources reviewed: the reserve composition by asset type, the exact fee schedule, the legal entity and regulatory charter under which Bridge issues, the contract upgrade and freeze policy, and the governance voting mechanics. Each of those matters to an integrator, and we return to them under risk.

OUSD Reference Architecture: Issuer, Reserves, Chains

Short answer: OUSD separates three planes. An economic plane (Open Standard and its partner incentives), an issuance plane (Bridge minting and burning against dollar reserves held at regulated custodians), and a settlement plane (four blockchains carrying the token). Each plane can change without rewriting the others, which is the design’s main strength.

Figure 1: OUSD stablecoin reference architecture, from partner network to issuer, reserves and four settlement chains.

Figure 1 reads top to bottom. Open Standard is the coordination layer: it owns the brand, the partner agreements and the rewards model. It does not itself hold dollars or run smart contracts in the sense a user cares about. Bridge sits below it as the issuer and orchestration provider, performing the regulated act of accepting dollars and creating tokens, and the reverse. Reserve custody sits to the side of that flow, because assets backing the token must be held by institutions that are not the issuer’s operating wallet. The four chains hang off the mint and burn function as destinations.

The economic plane: a consortium cap table

Most stablecoins are run by a single company that keeps the reserve income. Open Standard distributes economics. Partners earn rewards in proportion to supply and activity they drive, and the company’s chief executive was quoted saying the overwhelming majority of the cap table is meant to be distributed to founders and non-founders based on how they help grow the network.

This is an engineering fact as much as a business one, because it changes who is motivated to integrate. A processor that earns a share of reserve yield on balances it holds has a reason to default customers into OUSD, to keep balances on its platform and to route payouts through it. Stripe’s announcement says partners can earn rewards on OUSD activity including balances held on Stripe. Expect the integration surface to be generous: SDK defaults, dashboard toggles, and onramp flows that prefer the token.

The risk of this model is the mirror image. When every large distributor is paid to promote the asset, apparent adoption can reflect incentive routing rather than organic demand. As an integrator you should separate usage you chose from usage the platform defaulted for you.

The issuance plane: Bridge as regulated orchestrator

Bridge is the issuer of record in the launch materials, and also the orchestration API through which Stripe customers convert between OUSD, fiat and other stablecoins. That dual role is convenient: one API surface handles mint, burn, conversion and payout. It also concentrates operational risk. If the orchestration service is unavailable, the on-chain token still exists and still transfers, but the primary path to dollars is degraded.

Primary redemption is the mechanism that keeps a stablecoin at par. Authorized parties mint and redeem directly at one dollar, and arbitrage between that fixed price and the secondary market holds the peg. Because minting and redemption are fee-free through Stripe, Visa and BVNK platforms, the arbitrage band should be tight for those participants. Retail holders who cannot redeem directly rely on market makers, so their effective exit price depends on exchange depth, which is why the Coinbase, Kraken and Uniswap venues named in launch coverage matter.

The settlement plane: four chains, one asset

OUSD launched natively on Base, Ethereum, Solana and Tempo. Native here means the issuer mints directly on each chain rather than relying on a third-party bridge to create wrapped copies. That matters because bridged tokens carry the bridge’s own smart-contract risk. With native issuance, supply on each chain is created and destroyed by the issuer, and cross-chain movement is a redeem on one chain and a mint on another, or a burn and mint protocol if one is used. The sources do not specify whether a cross-chain transfer protocol is used, so we treat the mechanism as unknown.

The choice of chains is informative:

Ethereum gives the deepest DeFi liquidity and the strongest institutional comfort, at the highest fees.
Base is Coinbase’s layer two, close to the exchange and its retail wallet base.
Solana offers low fees and high throughput, and a large payments and consumer footprint.
Tempo is Stripe’s own payments-oriented chain, selected as the default for Stripe customers.

Choosing Tempo as the default means Stripe controls the default settlement experience, including fee behaviour. I do not have verified public details on Tempo’s validator set, finality time or fee model for this article, and the engineering reader should look at Tempo’s own documentation before building on it. Treat any throughput or finality claim about Tempo as unverified until you have read the primary source.

Why a fixed one-to-one redemption is the real product

The marketing language is about openness, but the load-bearing property is simpler: one token equals one dollar, redeemable at no mint or burn cost for qualifying parties. Everything else, including the rewards model and chain choice, is a distribution mechanism for that property. A stablecoin that holds par under stress is worth more than any feature list, and a stablecoin that loses par once is hard to rehabilitate. The reserve design is therefore the part of the architecture to study most closely.

Reserve Design and Attestation Mechanics

Reserve architecture is where stablecoins differ most, and where the launch details are thinnest. The reported facts are that reserves are held at BlackRock, Lead Bank and BNY, with monthly attestations. Interpreting that responsibly requires understanding what each piece plausibly does and what it does not guarantee.

Three custodians, three jobs

The three named institutions suggest a layered reserve rather than a single pool. This is an inference from their roles in the market, not something the launch materials spell out, so read it as a reasonable hypothesis.

BlackRock is the world’s largest asset manager and operates widely used money market and Treasury funds, including products used as stablecoin reserve vehicles. Its presence suggests that some reserve is held in a government money market fund or similar short-duration Treasury exposure. Lead Bank is a US chartered bank that works with fintech and payments firms, so it plausibly provides cash deposit accounts and the banking connectivity for dollar inflows and outflows. BNY, a large custodian bank, plausibly provides safekeeping and possibly Treasury or repo custody. The real allocation among these is not published in the sources we reviewed, and we label it unknown.

Why split across three? Concentration risk. A stablecoin whose reserves sit at a single bank inherits that bank’s failure risk, as the March 2023 episode, when a major stablecoin briefly lost its peg because part of its reserves were stuck at a failed bank, demonstrated. Spreading cash and securities across a bank, an asset manager and a custodian narrows the blast radius of any one institution’s trouble, at the cost of operational complexity.

What a monthly attestation does and does not tell you

An attestation is an independent accountant’s report that, on a stated date, reserves of a stated composition were at least equal to tokens outstanding. It is valuable, but it is weaker than an audit of financial statements and it is a point-in-time snapshot. Two limits matter for engineers building risk monitoring:

Frequency. Monthly means up to roughly thirty days of blind interval. A reserve problem that appears and is fixed within a month, or appears just after a snapshot date, would not show in the report.
Scope. An attestation tests a defined set of assertions. It does not prove the issuer’s operational controls are sound, that custodians will honour redemption instantly, or that assets are bankruptcy remote.

The GENIUS Act framework, as I understand it, requires monthly public disclosure of reserve composition and certification by issuer executives, so monthly attestation aligns with that baseline rather than exceeding it. I have not verified the final rule text, so check the current regulations before relying on this. For a view of what regulators are proposing for capital and reserves, our GENIUS Act rules analysis goes deeper.

Reserve liquidity under stress: a worked illustration

Here is a purely illustrative calculation, with invented numbers, to show why composition matters more than the headline one-to-one ratio. Suppose a stablecoin has $10 billion in circulation and reserves split as 30 percent cash at a bank, 50 percent in a government money market fund and 20 percent in short Treasury bills held at a custodian. The numbers are hypothetical and are not OUSD’s.

A redemption surge of 15 percent in a day means $1.5 billion of outflow. Cash covers $3 billion, so the issuer can meet it from the bank account if wires clear. If the bank cut-off passed or the bank is unavailable, the issuer must liquidate fund shares, which settle same day or next day depending on the fund, or sell bills. The point is that redemption capacity is a function of settlement mechanics, not of the reserve total.

Now suppose the surge is 40 percent, or $4 billion. Cash alone is insufficient, so the issuer depends on fund redemption and bill sales, each with operational cut-offs. Even with perfectly adequate reserves, a gap of hours can open on-chain, during which the secondary price falls below par because market makers cannot be sure of redemption timing. That price dip can itself trigger more selling. This is why the speed and the independence of reserve liquidity channels matter, and why integrators should watch secondary-market depth, not only the attestation.

Open questions an integrator should ask

Because the launch materials are light on reserve specifics, a diligence list is more useful than speculation:

What is the breakdown between cash deposits, money market funds, Treasury bills and repo?
What is the maximum weighted average maturity of the securities?
Are reserve assets held in segregated, bankruptcy-remote accounts for the benefit of token holders?
What is the contractual redemption time and the minimum redemption size for direct redeemers?
Who is the attesting accounting firm, and is there a move toward more frequent or real-time proof?
Is there a legal claim for holders in an issuer insolvency, and how does it rank?

None of these were answered in the launch coverage we reviewed. Until they are, treat OUSD as a well-connected but still new asset, and size exposure accordingly.

Walk-through: From Mint to Merchant Settlement

Architecture diagrams show structure; payments engineers need the order of events. This section traces a dollar from a business bank account into OUSD and back, then shows where the token sits in a card payment. The sequence is a simplified model built from the roles described in the launch materials. Real API names, timing and limits are not published in the sources we reviewed, so none are asserted here.

The mint and redeem lifecycle

Figure 2: Mint and redeem lifecycle for the OUSD stablecoin. Dollars must be confirmed in reserves before tokens exist.

The ordering in Figure 2 is the control that makes the whole system trustworthy. Tokens are created only after the matching dollars are confirmed received and held. On redemption the order reverses: tokens are burned first, then dollars are released. A system that mints before confirming funds, or releases dollars before burning, opens a window where supply exceeds backing. Auditors and attesters care about this ordering because it makes the one-to-one invariant checkable in the ledger.

Three practical consequences follow for integrators.

First, mint latency is dominated by the fiat leg, not the chain. Bank rails such as ACH settle in batches and wires have cut-off times, so a business that wants OUSD in the next few seconds either pre-funds an account or relies on an instant rail. Block time on Base, Solana or Tempo is rarely the bottleneck. Stripe’s statement that Bridge orchestration APIs let businesses convert between OUSD and fiat or other stablecoins suggests the platform hides much of this, but the underlying constraint remains.

Second, redemption has two doors. Qualified parties redeem directly with the issuer at par. Everyone else sells on a venue. Your code should know which door a given flow uses, because the price risk is different. A treasury system that assumes it can always redeem one to one, when it actually holds tokens in a wallet with no direct redemption relationship, has a hidden market-risk exposure.

Third, supply is observable. Because mint and burn happen on chain, anyone can reconcile circulating supply per chain against the attested reserve total. That is a free monitoring signal: if on-chain supply grows between attestations, you can estimate how much the reserve must have grown by.

Where OUSD sits in a payment

Stripe describes OUSD as usable across Treasury, Issuing, Global Payouts, Crypto Onramp and Payments. That is effectively the full lifecycle of business money: receive, hold, send and spend. Figure 3 shows a simplified payment in which settlement currency is a choice.

Figure 3: Settlement choice in a payment. The OUSD stablecoin path replaces bank settlement with an on-chain transfer into a treasury balance.

In the fiat branch, funds move through the banking system on the usual schedule, typically one to two business days for card settlement in many markets, though this varies by country and acquirer. In the token branch, settlement is a transfer to a wallet or Stripe-managed balance, available around the clock rather than on banking days. The merchant can then off-ramp to dollars via Bridge, spend through an issued card, or pay out to a supplier or contractor globally.

The value proposition is not that card networks disappear. Visa and Mastercard are founding partners precisely because they want to be the connective tissue for stablecoin settlement, not be displaced by it. Our look at stablecoin settlement across the card networks explains how issuers and acquirers can settle in stablecoin while the cardholder experience stays unchanged. OUSD adds a specific asset that both networks have an equity interest in.

The agentic angle

There is a second reason the consortium shape matters: software agents. When an AI agent pays for an API call or a purchase, it needs money that settles instantly, programmatically and without a human approving a bank transfer. A stablecoin native on several chains, backed by processors that also issue cards, is a natural fit. We covered the broader pattern in our piece on agentic payments architecture. Nothing in the OUSD launch materials we reviewed specifically targets agents, so this is our reading of the fit, not a stated product feature. It is, however, a plausible driver of the default-asset strategy: whoever is the default stablecoin inside agent payment frameworks collects a great deal of micro-volume.

Fee mechanics and who pays

The reported fee design is: no cost to mint or redeem through the Stripe, Visa and BVNK platforms, and revenue from a small transaction fee. Stripe’s post adds that fees should stay predictable as volumes increase. That is a promise about pricing behaviour, not a published number, so model it as an unknown with a ceiling you negotiate.

Compare this with traditional card interchange, which is a percentage of ticket size. A flat or small per-transaction fee on a stablecoin transfer is attractive for large tickets and for business-to-business payments, where a percentage fee is painful. For very small payments, any fixed fee, plus the cost of on-chain gas, can dominate, which is partly why chains with low fees such as Solana and a payments-optimized chain such as Tempo are in the set.

A rough break-even framing helps. If your current cost on a card payment is a percentage p of ticket T, and your stablecoin cost is a fixed fee f plus gas g plus an off-ramp cost o, then stablecoin wins when f + g + o is less than p times T. With unknown f, the only honest answer is to measure it. For a $10,000 invoice at an illustrative 2.5 percent card cost, the card cost is $250, and almost any plausible fixed stablecoin fee is lower. For a $4 purchase the same percentage is ten cents, and a fixed fee can easily exceed it. These figures are illustrative, not OUSD’s actual pricing.

Integration Decision Framework

Adopting OUSD is not a single decision but a bundle: which chain, which entry point, how much balance to hold, and what to monitor. Figure 4 organizes the decision.

Figure 4: Integration decision flow for the OUSD stablecoin. Chain choice feeds a common risk review with three monitoring tracks.

Choosing a chain

The four chains represent different compromises, and the right answer depends on the flow.

Criterion	Tempo	Base	Solana	Ethereum
Role in launch	Stripe default	Coinbase ecosystem	Consumer and low fee	Deepest liquidity
Best for	Stripe-native flows	Retail onramp, DeFi on Base	High-frequency small payments	Large treasury, institutions
Main concern	Newer, less public track record	Layer two dependence on sequencer	Different tooling and outage history	Higher fees
Verified detail in sources	Default for Stripe	Native OUSD	Native OUSD	Native OUSD

The last row is deliberate. The sources we reviewed confirm native availability and Stripe’s default, but not fee levels, finality times or throughput of each chain with OUSD, so those columns above describe general chain characteristics rather than OUSD measurements. Verify against current chain documentation before you commit.

A sound default for most businesses is to take the platform’s default for operational flows and add one second chain only when a specific counterparty demands it. Every extra chain adds wallet management, monitoring, key custody, reconciliation and incident surface. A multi-chain stablecoin is a feature for the ecosystem, not a mandate for every integrator to run four chains.

Choosing an entry point

There are several doors: the Stripe platform, the Visa and Mastercard stablecoin platform path, BVNK, and Coinbase. They differ in who is your counterparty. Via Stripe, Bridge is the counterparty for conversion. Via Coinbase, an exchange relationship governs. Via a card network program, an issuer or acquirer sits between you and the token. Pick the one whose legal terms, KYC burden, settlement cut-offs and liability allocation match your treasury policy, not merely the cheapest quote.

Holding balances versus passing through

The rewards model rewards balances held on Stripe, which creates an incentive to leave funds in token form. Resist treating that as a default. A conservative pattern keeps only the operating float in OUSD, sized to a few days of payouts, and converts the rest to bank deposits or government instruments under your own treasury policy. That keeps your exposure to any single issuer’s reserve or operational failure bounded.

What to monitor

Three monitoring tracks come out of the earlier sections.

Reserve attestation. Parse each monthly report when published. Compare reserve composition and total against on-chain supply at the attestation date. Alert on composition drift, such as a growing share of less liquid assets, or a change of custodian.
Peg and depth. Track the OUSD to dollar price on the major venues, plus order book depth within, say, 10 and 50 basis points of par. A widening spread with falling depth precedes most depegs.
Compliance mapping. Record how OUSD maps to your regulatory obligations: whether your jurisdiction treats it as a permitted payment stablecoin, how your auditors classify it, and how sanctions screening works for wallet addresses.

A simple monitoring rule set might page when the venue price drops below 0.995 for more than five minutes, when top-of-book depth falls by half versus its 30-day median, or when on-chain supply on any chain changes by more than a set percentage within an hour without a matching mint request on your side. The thresholds are examples to tune, not recommendations.

Reconciliation and accounting

Finance teams will ask a boring but crucial question: where does this appear on the books? Treatment of stablecoin holdings varies by jurisdiction and accounting framework, and I do not give accounting advice here. What engineers can do is make the data clean: store the chain, transaction hash, block height, timestamp, token amount and the corresponding fiat leg for every mint, burn and transfer. Reconcile daily per chain, and keep an immutable record so auditors can trace any balance to a mint event. The more flows you run through Bridge APIs, the more you should mirror their identifiers in your ledger, so a dispute about a missing payout can be settled by lookup rather than by forensics.

Wallet and key management

Holding OUSD directly on chain brings custody questions that fiat treasuries never had. If Stripe or Coinbase holds the keys, you inherit their custody risk and their operational limits. If you hold keys yourself, you inherit signing, backup and insider-risk problems. Many businesses will sensibly choose a custodian-managed balance for operations and reserve self-custody for a narrow set of use cases. Whichever you choose, define who can authorize transfers above what size, require multi-party approval, and test recovery. A policy that has never been exercised is a hypothesis, not a control.

Trade-offs, Gotchas, and What Goes Wrong

A consortium stablecoin has real strengths, and it has failure modes that differ from those of a single-issuer coin. Being honest about them is part of designing around them.

Incentive-driven adoption can mask demand

When five distributors share equity and rewards, headline growth in supply may reflect default settings and reward programs rather than users choosing the asset. If incentives taper, or if a partner changes its default, volume can move quickly. For planning, separate sticky demand, such as customers who hold OUSD because a counterparty demands it, from rented demand that follows incentives.

Concentration hides inside diversity

Four chains and three custodians look diversified, but the control points are few. Bridge is issuer and orchestrator; Stripe is the default chain operator through Tempo, a processor, an issuer of cards and a partner; and the networks that decide acceptance are also owners. A bug, outage or policy decision at one of these can ripple through many paths at once. Diversity of chains does not remove correlation of control.

Smart-contract powers

Regulated stablecoins generally include the ability to freeze addresses and sometimes to upgrade contracts, because law enforcement and sanctions compliance require it. The launch materials we reviewed did not describe OUSD’s freeze, blacklist or upgrade policy. Integrators should read the contract on each chain, identify admin keys, and confirm how a freeze would affect a merchant whose customer wallet is flagged. Programmable money is only as predictable as its admin permissions.

Cross-chain fragmentation

Native issuance on four chains means liquidity is split four ways. A payout that needs OUSD on Solana cannot use a balance sitting on Ethereum without a conversion or transfer step, and that step has latency, cost and failure modes. Teams that start with one chain and later add a second often discover that treasury operations, not payments, become the hard part.

Thin attestations and unknown composition

As covered above, monthly attestation is a snapshot, and composition details were not published in the sources reviewed. A new reserve program with a strong institutional roster is a good sign; it is not a track record. Stablecoin history includes several episodes where reserves that looked adequate on paper behaved badly under stress because of liquidity or custody issues.

Regulatory timing

GENIUS Act rulemaking is still maturing, and the effective-date mechanics depend on final regulations. State regimes, foreign regimes such as the EU’s MiCA, and bank regulators may impose different requirements on users of the asset. A compliant status in one jurisdiction is not automatic in another. Legal review belongs in the integration plan from day one.

Operational anti-patterns

Several mistakes are easy to make. Treating on-chain finality as legal finality for a payment. Assuming mint and redemption are instant because the token moves in seconds. Hard-coding a single chain’s RPC provider. Ignoring gas token management on chains that require it. Failing to rate-limit automated payouts so that a bug can drain a wallet. Each is cheap to prevent and expensive to learn.

Practical Recommendations

If you run payments, treasury or platform engineering, the right response to OUSD is measured. It is a credible new asset with unusually strong distribution, but it launched on October 1, 2026, and the evidence base is days old.

Start by reading primary sources: Stripe’s announcement, Bridge’s documentation, and Open Standard’s published reserve and terms pages as they appear. Then pilot, do not migrate. Route a small, non-critical flow, such as contractor payouts or an internal treasury transfer, through OUSD on the default chain and measure real fees, real latency and real support responsiveness. Keep the fiat path live as a fallback.

Design for portability. Abstract the stablecoin behind an interface in your own code so that switching between OUSD, USDC or a bank deposit is configuration rather than a rewrite. Stripe says it will continue to let customers choose their stablecoin and chain and will not force conversion of existing balances, so keep that optionality instead of letting defaults erode it.

Checklist before you go live:

Confirm the legal counterparty, jurisdiction and terms for mint and redemption on your chosen entry point.
Obtain reserve composition, custodian agreements summary and the first attestation report.
Review the token contract on each chain you use for freeze, pause and upgrade powers.
Set a maximum balance policy and an automatic sweep to bank accounts above it.
Build peg, depth and supply monitors with paging thresholds.
Document key custody, approval limits and recovery drills.
Reconcile every mint, burn and transfer to your ledger daily.
Define an exit plan: how long it takes to move all balances to dollars if you must.

If your volume is mostly small consumer payments, the economics hinge on the unpublished fee schedule, so negotiate or wait. If your volume is large business-to-business payouts across borders, the case is stronger today, since a flat small fee and round-the-clock settlement address real pain.

Frequently Asked Questions

What is the OUSD stablecoin?

OUSD is a US dollar stablecoin launched on October 1, 2026 by Open Standard, with Bridge, a Stripe company, as issuer. It is designed to redeem one to one for dollars, backed by reserves reported to be held at BlackRock, Lead Bank and BNY, and it is native on Base, Ethereum, Solana and Tempo. Coinbase, Mastercard, Shopify, Stripe and Visa are the five founding partners.

Who issues OUSD and who holds the reserves?

Bridge, which Stripe acquired in 2024, is the issuer. Launch coverage reports that reserves are held at BlackRock, Lead Bank and BNY, with monthly attestations published. The breakdown of reserves by asset type, such as cash, money market funds and Treasury bills, was not available in the sources we reviewed, so anyone relying on the token should ask for it and read the attestations.

Which blockchains support OUSD?

OUSD launched natively on four networks: Base, Ethereum, Solana and Tempo. Tempo is Stripe’s payments-oriented chain and is the default in Stripe’s configuration. Native means the issuer mints directly on each chain instead of using a third-party wrapped bridge. Details of fees, finality and any cross-chain transfer mechanism were not published in the materials reviewed, so verify them in chain documentation.

Is OUSD free to mint and redeem?

Reported terms say minting and redemption carry no fee through the Stripe, Visa and BVNK platforms, and Stripe says it charges no minting or burning fees. Open Standard earns revenue from a small transaction fee, but the amount was not published in sources we reviewed. Third-party costs such as bank wires, on-chain gas and exchange spreads can still apply, so total cost depends on your path.

How is OUSD different from USDT and USDC?

Technically it is the same product category: a fiat-backed, redeemable dollar token. The difference is structure. Launch coverage puts USDT near 59 percent and USDC near 23 percent of a roughly $308 billion market, both run by single issuers. OUSD shares economics and equity-linked rewards with distributors, and has card networks, an exchange and a commerce platform as founding partners. Its track record is only days old.

Is OUSD regulated under the GENIUS Act?

The launch materials we reviewed did not state OUSD’s regulatory classification under the GENIUS Act, and the Act’s implementing rules are still being finalized. The reserve design, with regulated custodians and regular attestation, resembles what the framework expects, but resemblance is not a legal status. Check the issuer’s published disclosures and take legal advice for your jurisdiction before relying on any particular classification.