Table of Contents
Want a branded fully-backed stablecoin without standing up your own reserve bank, compliance stack, and mint/burn infra? Bridge Open Issuance is that path: you design the token experience, Bridge issues and operates the mint/burn rails, and you can share treasury rewards.
The product name in Bridge docs is a custom xUSD (your brand, your ticker). Open Issuance is not a Dashboard checkbox.
You contact sales@bridge.xyz, complete onboarding, then wire Orchestration transfers into mint and redeem flows.
This guide walks the 2026 Open Issuance stack as of September 13, 2026: design knobs (chain, ticker, logo, open vs closed loop), mint/burn via Orchestration, cash vs treasuries allocation (including the $100m AUM examples), rewards payout timing, and the control tradeoff you accept when Bridge stays the issuer/operator.
Key Takeaways
- Bridge Open Issuance launches a branded fully-backed xUSD; Bridge handles reserves, compliance, and mint/burn infra.
- Design knobs: chain, token name, ticker, 32x32 logo, reserves strategy (~20% cash to start), refundable deposits, open vs closed loop.
- Multi-chain same ticker is supported with shared reserves and separate contracts; listed chains include Tempo, Base, Solana, Ethereum, Aptos, Sui, Polygon, Stellar, Arbitrum, Optimism, Linea, Monad, HyperEVM.
- Mint/burn runs through Orchestration deposits and redemptions; allocate liquidity with POST /v0/issuance/reserves/liquidity_allocation (Api-Key + Idempotency-Key).
- Named downside: you do not self-mint; Bridge is the issuer/operator, so you trade control for speed and compliance; sales onboarding is required.
What Bridge Open Issuance is (and isn't)
Bridge documents Open Issuance as a branded, fully-backed custom stablecoin you control at the product layer. Bridge handles reserve management, compliance, and infrastructure so you don't rebuild banking, smart contracts, and licenses from scratch.
The end-to-end flow is Orchestration (fiat or crypto in) → Mint → Reserves (cash + treasuries) → Rewards share to the issuer. Instant access to Bridge rails (on/off-ramps, Cards, interoperability with other Bridge-issued coins) comes with the launch.
Open Issuance is not the same as Open USD (OUSD) from Open Standard or Bridge's own closed-loop USDB. Those are more off-the-shelf reward paths.
Open Issuance is the custom branded xUSD route. See Bridge's issuance overview and issuance options.
Prerequisites and setup (as of Sep 13, 2026)
Before the first mint, Bridge's path requires:
- An Open Issuance engagement started with sales@bridge.xyz (not a Dashboard toggle).
- Design choices locked: chain(s), token name, ticker (Token ID), 32x32 token logo, open vs closed loop, starting reserves mix.
- Bridge API credentials for Orchestration transfers and reserves allocation calls (Api-Key + Idempotency-Key).
- Wallets and Orchestration destinations ready for mint delivery and redemption exits.
- Compliance and entity paperwork Bridge requires for GENIUS-ready / licensed issuance.
Custom setup can be as little as a day when no new chain support is needed. New chain work extends that timeline.
Step 1. Design the branded xUSD
Bridge's designing your stablecoin guide lists the knobs you set before mint goes live.
| Knob | What you choose | Notes (as of Sep 2026) |
|---|---|---|
| Chain | Tempo, Base, Solana, Ethereum, Aptos, Sui, Polygon, Stellar, Arbitrum, Optimism, Linea, Monad, HyperEVM, more on demand | Multi-chain same ticker: shared reserves, separate contracts |
| Token Name | Display name for wallets and explorers | Brand-facing string |
| Token ID (ticker) | Short ticker (your xUSD symbol) | Same ticker across chains when multi-chain |
| Token Logo | 32x32 asset | Required for wallet display |
| Reserves Strategy | Cash vs treasuries mix | Typically ~20% cash to start |
| Refundable Deposits | Inventory for fast swaps | Optional liquidity buffer |
| Loop model | Open Loop vs Closed Loop | Distribution and transferability tradeoff |
Open Loop examples Bridge cites: Phantom CASH, MetaMask mUSD, Native Markets USDH. Tokens can move on public rails beyond your app.
Closed Loop example: Takenos TAKO. Transfers stay inside the permitted set, which limits distribution but reduces public transferability risk.
Step 2. Wire Orchestration into mint and burn
Bridge detects an Orchestration deposit, allocates reserves, and mints 1:1 to the destination wallet. Redeem burns the xUSD and releases fiat or crypto through the same rails.
Orchestration plugs into Bridge money movement covering 200+ countries (Virtual Accounts, Liquidation Addresses, Transfers). Swaps into xUSD use Orchestration transfers with Api-Key + Idempotency-Key, the same pattern as other Bridge transfers.
If your treasury already funds Bridge Virtual Accounts for USDC, reuse that ops muscle. See how to open a Bridge Virtual Account for USDC.
Full mint/burn lifecycle detail lives in Bridge's minting and burning and orchestration docs.
Step 3. Allocate reserves (cash vs treasuries)
You choose how reserves sit between on-demand liquid cash and treasuries. Bridge manages partners and settlement; you set the mix via API.
As of Sep 2026 Bridge documents:
- On-demand liquid: USD banking hours / on-chain stablecoins 24/7 for fast redemptions.
- Treasuries: roughly EFFR − 20 bps, about 1 business day to free.
- Off-chain USD: roughly EFFR − 200 bps.
- On-chain stables as reserves: 0% reward.
- Partners named: Lead Bank; BlackRock, Fidelity; Superstate USTB; BUIDL.
Example at $100m AUM (Bridge's illustrative cases): redemption-first 50/50 → about 2.2% effective; reward-first 10/90 → about 3.3% effective.
Bridge typically suggests starting near ~20% cash so redemptions don't stall while treasuries unwind.
Reserves allocation API
Call POST https://api.bridge.xyz/v0/issuance/reserves/liquidity_allocation. Headers: Api-Key and Idempotency-Key. Read current mix with GET on the same path.
See Bridge's reserve management docs before you ship allocation automation.
Step 4. Collect rewards (and know what doesn't earn)
Bridge shares the majority of treasury rewards with the issuer, minus issuance fees. Cash reserves generally don't earn.
On-chain stables held as reserves earn 0%.
Payout lands by the 5th business day of the following month, in tokens or fiat per Bridge's rewards docs.
Don't model rewards as if 100% of AUM sits in treasuries. Bake the cash sleeve and fee line into the forecast, then reconcile to the monthly statement.
Open Loop vs Closed Loop (and off-the-shelf alternatives)
| Path | Who issues / operates | Transferability | Fit |
|---|---|---|---|
| Open Issuance open loop | Bridge (branded xUSD) | Public (e.g. Phantom CASH, MetaMask mUSD, Native Markets USDH) | Ecosystem loyalty, wallet distribution |
| Open Issuance closed loop | Bridge (branded xUSD) | Restricted (e.g. Takenos TAKO) | App-contained balances, tighter control |
| Open USD (OUSD) | Open Standard | Open-loop off-the-shelf | Faster, less brand control |
| USDB | Bridge | Closed-loop Bridge coin | Off-the-shelf closed path |
Stablecoin payments stacks (Stripe, Bridge, BVNK) sit beside issuance, not instead of it. For accept rails after you have a coin, see how to accept stablecoin payments on Stripe and Stripe vs Bridge vs BVNK for stablecoin payments in 2026.
Stablecoin Insider's take
Related Stablecoin Insider playbooks
Platform context: Bridge review 2026.
Accept path: how to accept stablecoin payments on Stripe.
Third-party payouts: how to send a Circle stablecoin payout.
Stack compare: Stripe vs Bridge vs BVNK for stablecoin payments in 2026.
FAQ
How do I issue a branded stablecoin with Bridge Open Issuance?
Contact sales@bridge.xyz, lock design knobs (chain, ticker, logo, loop, reserves mix), then mint and redeem through Orchestration while Bridge operates reserves and compliance.
What is the difference between Open Issuance, OUSD, and USDB?
Open Issuance is your branded xUSD. OUSD is Open Standard's open-loop off-the-shelf coin. USDB is Bridge's closed-loop coin. All can share reward economics differently.
Which chains can my xUSD launch on?
Bridge lists Tempo, Base, Solana, Ethereum, Aptos, Sui, Polygon, Stellar, Arbitrum, Optimism, Linea, Monad, HyperEVM, with more on demand. Multi-chain same ticker uses shared reserves and separate contracts.
How do mint and burn work?
Bridge detects an Orchestration deposit, allocates reserves, and mints 1:1. Redeem burns xUSD and releases fiat or crypto through Bridge rails.
When do treasury rewards pay out?
Majority of treasury rewards (minus issuance fees) pay by the 5th business day of the following month, in tokens or fiat. Cash sleeves generally don't earn.
Do I self-mint the branded stablecoin?
No. Bridge is the issuer/operator of mint and burn. You design the brand and allocation policy; you trade self-mint control for speed and compliance.
Next step
Email sales@bridge.xyz with chain, ticker, open vs closed loop, and a draft ~20% cash / treasuries mix. Parallel-path Orchestration transfers and a sandbox liquidity_allocation call so mint/burn and reserves APIs are proven before marketing the branded xUSD.
Still mapping Bridge rails before Open Issuance?
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.
){kind=link}