Skip to main content

Open USD for Treasury: How CFOs Should Evaluate Open Standard's Stablecoin

When Open USD fits enterprise cash versus USDC and USDG: reserve-earnings model, governance exposure, custody options, integration paths, and a decision tree by treasury profile.

Written by Eco


Open Standard's announcement of Open USD landed with 140+ partner signatures: Visa, Mastercard, Stripe, BlackRock, BNY, Standard Chartered, Google, Shopify, IBM, Coinbase, Solana, Aave. For corporate treasury teams already running pilots on USDC, USDG, or PYUSD, the immediate question is practical: does Open USD belong in the operating cash stack, and if so, where?

This piece walks through the treasury lens, reserve-earnings mechanics, governance exposure, custody options, integration paths, and offers a decision framework for matching stablecoin choice to treasury profile. It is not a recommendation. Open USD is pre-launch as of this writing, and several mechanical details are still TBD per the Open Standard announcement.

What Open USD changes for treasury teams

Open USD is positioned as shared stablecoin infrastructure rather than a single-issuer product. Partners mint and redeem at no cost with no volume caps, and reserve earnings flow back to participating partners minus an operational fee. That structure is the headline differentiator versus the incumbent issuer model, where the issuer retains float income.

For a CFO, three properties matter: who controls reserves, how earnings are distributed, and what happens if a partner exits. The next sections unpack each.

Reserve-earnings model: who captures the float?

Stablecoin economics are float economics. A dollar held as collateral against a stablecoin sits in short-duration Treasuries earning roughly the policy rate. At today's rates, $1 billion in circulation generates around $40-50 million annually in gross reserve income before fees.

The three dominant models distribute that float differently:

  • Single-issuer retention. The issuer keeps the float. USDC and USDT operate this way. Holders earn zero by default; yield comes from external lending or tokenized money market products.

  • Consortium-shared. Reserve earnings are distributed across partner companies that participate in the network. Open USD and USDG (Global Dollar Network) sit here. Open Standard's announcement specifies that partners receive "all earnings from Open USD's reserves minus a small operational management fee."

  • Pass-through to holders. Tokens like sofiUSD, USDY, or USDM rebate yield directly to holders, usually structured as a tokenized money market fund.

The treasury implication: if your company is large enough to be a partner in a consortium-shared network, the math gets interesting. If you are a holder rather than a partner, consortium-shared and single-issuer look identical from a yield perspective, both pay zero to the wallet. In that case, pass-through tokens are the only way to capture float without leaving the asset.

Governance exposure: what are you signing up for?

Open Standard is governed by a board comprised of Open USD partners. Decisions are made collectively. For a partner company, that means board representation and influence over reserve policy, redemption rules, and integration standards. For a non-partner holder, governance is something you inherit, you do not vote on it.

Compare the four governance shapes a treasury team is likely to encounter:

  • Single-issuer (USDC, USDT, PYUSD): Issuer makes all decisions. Holders accept terms or exit.

  • Consortium (Open USD, USDG): Partner board governs. Non-partner holders accept terms; partners shape them.

  • Bank-issued (FDUSD, RLUSD): Regulated bank or trust governs under banking law. Holders get the same protections as other deposit-adjacent products from that institution.

  • Protocol-issued (DAI, crvUSD): Onchain governance via token holders. Treasury teams generally avoid these for operating cash due to collateral volatility.

If governance participation has strategic value, for example, your company moves enough payment volume that being inside the standard-setting body matters, Open USD's partner structure is the point, not a side effect. If you just want a settlement asset, governance shape matters less than reserve transparency and redemption guarantees.

Custody options: where do the tokens actually sit?

Pre-launch, the supported custody stack for Open USD is not fully disclosed. Treasury teams evaluating any stablecoin should map four custody paths:

  • Qualified custodian (Coinbase Custody, BitGo, Anchorage, Fireblocks): Standard institutional path. Coinbase is a launch partner for Open USD, so first-class support is likely.

  • Bank custody (BNY, State Street): BNY is a launch partner. For treasury teams already custodied at BNY, integration through existing relationships is the cleanest path if and when BNY supports Open USD onchain.

  • Self-custody (multisig, MPC wallets): Lower counterparty risk, higher operational burden. Suitable for crypto-native treasury teams; usually not for traditional CFO orgs.

  • Settlement-only (no custody): Stablecoin enters and exits the corporate balance sheet within the same business day via an orchestration layer. The company never sits on overnight stablecoin exposure.

The last option matters more than it looks. Many corporates piloting stablecoins for cross-border payments or merchant payouts never intend to hold the asset. They want USD in, USD out, with stablecoin rails in the middle. In that case, the stablecoin choice is a function of where liquidity is deepest at the moment of settlement, which is what stablecoin orchestrators like Eco are built to handle.

Decision tree: which stablecoin fits which treasury profile?

The right answer depends on what the treasury function is actually trying to do. Four common profiles:

Profile 1, Hold for yield, no operational use. The treasury wants a USD-equivalent that earns. Open USD does not pay holders directly. USDC does not either. The fit here is a yield-bearing token (BUIDL, USDY, sofiUSD, USDM) or a tokenized money market fund, not Open USD.

Profile 2, Cross-border payments, no holding. The treasury moves money internationally and wants stablecoin rails for the settlement leg. Open USD's zero-cost mint/redeem is attractive, but at launch liquidity will be thin relative to USDC and USDT. The pragmatic path is an orchestration layer that routes across all three based on corridor depth.

Profile 3, Merchant payouts at scale. The treasury pays contractors, sellers, or affiliates globally. With Stripe, Shopify, Visa, and Mastercard all on the Open USD partner list, integration into existing payout rails is likely once the network is live. For now, USDC via Stripe Connect or Coinbase Commerce remains the established path.

Profile 4, Strategic partner participation. The company is large enough that being inside the consortium creates leverage, payment volume, board influence, reserve-earnings share. Open USD partnership is then a strategic decision, not just a treasury one, and should be evaluated alongside USDG (the other major consortium play) and direct issuer relationships.

Open USD vs USDC vs USDG: the treasury comparison

For most enterprise treasuries, the practical choice set at launch will be Open USD, USDC, and USDG. The shape of each:

Dimension

Open USD

USDC

USDG

Issuer / operator

Open Standard (partner-governed)

Circle (single issuer)

Paxos (issuer) / Global Dollar Network

Governance

Partner board, 140+ signatories

Circle

Network partners, Paxos-led

Reserve earnings

To partners (minus fee)

Retained by Circle

Distributed to network partners

Mint/redeem cost

Zero, no volume caps

Free for direct Circle accounts

Network terms

Regulatory posture

TBD at launch

State trust, MiCA-compliant in EU

NYDFS-regulated trust

Liquidity (today)

Pre-launch

Deepest of any stablecoin

Growing

Best fit

Partner companies, multi-issuer routing

Default settlement asset

Network participants seeking yield share

Integration paths: how Open USD actually shows up

Three realistic integration shapes for a treasury team:

  • Direct via payment partner. If your treasury already runs Stripe, Visa Direct, or Mastercard Move for cross-border payouts, Open USD will likely appear as a settlement option inside those rails. Lowest lift.

  • Direct via custodian. Hold Open USD at Coinbase Custody, Fireblocks, or (eventually) BNY. Suitable for treasuries that already custody other stablecoins.

  • Orchestrated. Route through a stablecoin orchestrator that handles Open USD alongside USDC, USDT, USDG, and others. The treasury team picks the policy (cheapest route, deepest liquidity, specific issuer preference); the orchestrator picks the asset at execution. This is the path that scales when no single stablecoin dominates every corridor.

Should enterprises hold Open USD?

For most treasury teams in 2026, the answer is: not yet, and possibly not as a holding decision at all. Three observations:

First, holding Open USD as idle cash captures none of the reserve-earnings upside unless your company is a partner. For yield, tokenized money market products are the more direct vehicle.

Second, for operational use, cross-border payments, payouts, supplier settlement, the question is rarely "which stablecoin do we hold" but "which stablecoin do we settle in for this transaction." Liquidity depth at the moment of execution matters more than choice of issuer.

Third, Open USD's strategic significance is the consortium model itself. If single-issuer stablecoins were the only template, treasuries had one decision: which issuer. With Open USD and USDG, consortium stablecoins now exist at scale, and the integration-layer question, how to access all of them without picking a winner, becomes the actual treasury problem.

The companies that get this right will not be the ones that choose Open USD over USDC. They will be the ones that build a settlement architecture that does not require choosing.

Related reading

Source: Open Standard, Introducing Open USD. Pre-launch details subject to change; this article reflects information disclosed in the launch announcement.

Did this answer your question?