If you run a payments company, cross-border collections, a wallet, a brokerage, an e-commerce business going global — or you’re a VC listening to a founder say “we should launch our own stablecoin” — this is for you.

The most expensive sentence I hear is: “We’re already touching stablecoins, why not issue our own?” It sounds smart. It isn’t.

Issuing isn’t adding a feature. It’s adding a regulated financial business line: licensing, reserve custody, monthly attestations, BSA/AML, banking relationships, redemption obligations — every one a fixed cost that earns you nothing and can kill you if it breaks. You think you’re adding a payment option. You’re opening a bank.

And opening a bank doesn’t guarantee profit — look at Circle.

Circle’s Q1 2026 10-Q: $652.5M in reserve income. Sounds like a printer. But distribution & transaction costs were $405.4M — of which Coinbase-related distribution alone was $330.6M. GAAP net income: just $55.2M.

In other words: the money Circle pays one channel (Coinbase) is 6x its own net profit. Why? Because Coinbase owns the users and the balances. Circle does all the dirty work — issuance, reserves, compliance — and the channel sits on the entry point and collects the interest. Circle isn’t USDC’s owner. It’s USDC’s contract manufacturer.

Contrast Tether: also self-issued, but it is the default settlement currency across exchanges, OTC, and cross-border — no comparable channel-sharing cost disclosed — and it cleared $1.04B in a single quarter.

Both “issued their own.” Opposite outcomes. The difference isn’t issuance — it’s whether there’s distribution behind it.

Which leads to the 2026 update most people miss: if you have distribution, you don’t need to open a bank. White-label has matured.

Stablecoin-as-a-Service (SCaaS) is now a full supply stack: Paxos (issues PayPal’s PYUSD), Stripe / Bridge, Coinbase Stablecoin-as-a-Service (1:1 USDC-backed) — they carry the licensing, reserve custody, and multi-chain mint/redeem; you bring brand and distribution. (Note: white-label outsources the issuance stack, not your compliance — AML, KYC, and your jurisdiction’s obligations stay on you.)

The template is PYUSD: PayPal didn’t become the issuer — it handed the issuance and reserve stack to Paxos and brought the two things it actually owns: brand + hundreds of millions of users. It kept the channel tax inside its own brand.

The sharper move: distributors banding together. USDG / Global Dollar Network shares reserve income with the platforms that drive adoption, instead of the issuer keeping it all — 130+ partners (Robinhood, Kraken, and more). The subtext is a direct counter to Circle’s model: the ones who own distribution stop renting someone’s coin and form a consortium to collect the channel tax themselves.

So “should we issue?” is a decision tree:

• No distribution → Integrate (just use USDC/USDT). Put the saved cost back into your real moat: your use case. This is the right answer for 99% of teams.
• Have distribution, don’t want to run the stack → White-label / join a consortium, keep the channel tax in your brand.
• Strong distribution + can carry long-term compliance & reserve costs + the coin has strategic value → only then issue your own. Teams that check all three: count them on one hand.

Three takeaways:

1. Issuance isn’t a money printer — it’s a long-term bill you may not be able to carry.
2. What decides life or death isn’t “did you issue,” it’s “do you have distribution.”
3. If you have distribution, there are ways to reclaim the channel tax without opening a bank; if you don’t, issuing is just prepaying tuition for a war you can’t win.

(I’ve paid a version of this tuition myself: I built a public chain to first-tier performance, and it still faded — building it doesn’t mean anyone uses it.)

Integrate, white-label, or actually issue? Tell me what you’re building in the comments and I’ll break it down.

— Excerpt from The Stablecoin Operator’s Handbook: Distribution, Reserves & Compliance. Ongoing — tear it apart.

#StablecoinEconomics #ChannelTax #WhiteLabelStablecoins #CrossBorderPayments