When the Card Networks Co-Own the Stablecoin

A few days ago I wrote that SoFi and Mastercard had complicated my stablecoin argument. I had said I believe stablecoin rails will take over from the card networks, and then a card network started settling a bank’s whole card program in a stablecoin, on its own network. My conclusion was that the binary framing was wrong, and that the more likely path, at least for payments at merchants, is stablecoins moving into the settlement layer underneath the card while the network keeps the parts people see. I also said I wouldn’t read a strategy into one reported sentence about Mastercard embedding stablecoin orchestration into its stack.

This week there is a lot more than one sentence to go on. On September 30, Open Standard put its stablecoin, Open USD or OUSD, live on Base, Ethereum, Solana and Tempo. Its five founding partners are Coinbase, Mastercard, Shopify, Stripe and Visa. Two card networks, a PSP, a commerce platform and a crypto exchange are now on the same cap table for the same dollar token. That is a different situation from a card network supporting someone else’s stablecoin, and I think it pushes my view further in the direction the SoFi piece started.

What launched, and where the reporting disagrees

I’ll go through the facts carefully, because the coverage doesn’t line up on several of them, and I’d rather say so than pick the most convenient version.

According to Open Standard’s own launch post, OUSD is issued by Bridge, which the post describes as a Stripe company, with reserves held at BlackRock, Lead Bank and BNY, and monthly attestations published. Businesses can mint and redeem it one for one with the dollar at no cost through any of the integration paths. They can start building with Mastercard’s BVNK, Stripe and the Visa Stablecoin Platform now, and with Coinbase from October 1. At launch it trades on Coinbase, Kraken and Uniswap. The post says Open Standard’s partners now number over 200 financial institutions, fintechs, banks and global businesses. When the project was first announced in June, the figure was over 140.

The founding partners committed more than $1 billion to establish OUSD’s liquidity. CoinDesk and The Paypers both name five founders, with Shopify among them. American Banker’s report names four and leaves Shopify out, and gives the June partner count of 140 rather than the current one. It also dates the launch to October 1, the day Coinbase’s path opened, where Open Standard, Stripe and CoinDesk all say September 30.

Stripe’s own post says OUSD is now the default stablecoin on Stripe, on the Tempo chain, while users can still choose other stablecoins. Businesses can use it to receive, hold, send and spend funds through Stripe’s Treasury product, run card programs through Issuing, pay recipients through Global Payouts, convert fiat through its onramp, and accept it through Payments.

The part that has drawn the most comment is the economics. Open Standard’s own wording is that partners “earn rewards proportional to the supply and activity they drive on their platforms, and have the opportunity to earn equity in Open Standard.” CoinDesk reports that the five founders each received an equal initial equity stake and that, over four to five years, the overwhelming majority of the equity will be distributed based on contributions to supply and transaction activity. American Banker describes this as a model that rewards participants by transaction volume rather than assets under management, and presents that as what sets OUSD apart from Circle and Tether. That contrast is American Banker’s framing. Open Standard’s post doesn’t use the words volume or assets under management, and its own formula counts supply, which is closer to assets than the phrase suggests. The June announcement described partners receiving the earnings on the reserves, minus a management fee. My reading is that OUSD shares out what a stablecoin issuer normally keeps, to whoever distributes it, weighted by how much they distribute.

What the sources don’t give is any figure for OUSD supply or usage after launch. It went live this week. Everything below is about structure and incentives, not adoption.

From embedding to co-owning

In the SoFi piece, the observation that mattered to me was a card network behaving as if it intends to absorb the new rail rather than be bypassed by it. SoFi issued its own stablecoin and Mastercard settled in it. The network was a host.

OUSD goes a step further. Visa and Mastercard aren’t hosting a token someone else controls; they hold founding equity in the company behind it, and each offers its own platform as a way to mint and redeem it. Stripe goes further still, since the issuer is a Stripe company and Stripe has made OUSD its default. The companies that were supposed to be on the losing side of “stablecoins versus cards” are, in this arrangement, the distribution, and they are paid in proportion to how much of it they distribute.

I think that settles one part of my old framing. If the card networks believed stablecoins were a threat to be resisted, co-founding one would be an odd way to show it. The other part, the claim that stablecoin rails will carry a growing share of how money moves, it doesn’t settle, but it points my way. Open Standard’s post lists the integration paths as supporting “settlement, payment orchestration, trading, FX, wallets, cards, and more.” The networks want to be inside the stablecoin flows rather than outside them, which is a fair indication of where they expect the flows to go.

So the view I’m working with now has the same shape as last week, with more weight on it. Stablecoins move into settlement and treasury first, underneath card products and inside PSPs, and the card networks position themselves as owners and distributors of that layer rather than as the incumbent it replaces. That is still an opinion. One consortium launch, with no usage figures yet, is a strong signal about intent and a weak one about outcome.

What it changes for merchants

For a merchant accepting cards, I expect very little changes soon, and I’d be wary of anyone saying otherwise. Nothing in the launch materials says anything about card acceptance, authorisation, disputes or what merchants pay to accept cards. As I wrote about SoFi, a change in what settlement is denominated in doesn’t, as far as I can tell, touch interchange, which follows the card and is set through the networks’ schedules. The interchange fight is happening in a courtroom, not on a blockchain, and a shared stablecoin doesn’t move it.

Where I do think it changes something is for merchants who already take stablecoin payments, or who are about to. Here the question used to be which stablecoin, and the answer was mostly a market-share question. With OUSD, the answer increasingly comes from the PSP. Stripe has made OUSD its default. Partners are rewarded in proportion to the supply and activity they drive on their platforms. Put those two facts together and the stablecoin a merchant ends up holding is shaped, at least partly, by which token earns its PSP the most. I don’t think that’s sinister. Defaults are always set by someone with a reason. It’s just worth knowing, the same way it’s worth knowing why a PSP routes a card transaction to one acquirer and not another.

Let’s imagine a situation. A merchant processes through two PSPs, one for cards in Europe and one for its US traffic, and both let customers pay in stablecoins. One defaults to OUSD because it’s a partner. The other defaults to USDC. The merchant now has stablecoin balances in two tokens, held in two places, each redeemable one for one with the dollar, and its finance team has to treat them as the same money for reporting while they move through different redemption paths. Free minting and redemption through the partner paths takes most of the cost out of that. It doesn’t take out the reconciliation, the question of where each balance sits, or the decision about which one to settle supplier payments from. That is a hypothetical, and Stripe does let users choose other stablecoins, so a merchant who knows to ask can avoid most of it. My point is only that “which stablecoin” is about to become a default most merchants inherit from their PSP rather than a choice they make.

Orchestration, and how many stablecoins to expect

This is the part I find most interesting, for professional reasons. Orchestration exists because no single PSP covers everything a merchant needs, and the merchant wants one layer that decides which provider each payment goes through and then reconciles what came back. Open Standard listing payment orchestration among its integration use cases tells me the people building OUSD expect it to be one of the things that layer routes.

If Stripe, Visa and Mastercard all converge on one stablecoin, that should simplify part of the job. Routing between rails gets easier when the money arriving at the end is the same token, whichever path it took, and a merchant that would otherwise juggle several dollar stablecoins has a reason to consolidate. That’s the optimistic case and I think it’s a plausible one.

The other case is that convergence is less complete than the founder list makes it look. Visa and Mastercard both co-founded OUSD, and Mastercard’s settlement infrastructure also supports USDC, PYUSD and RLUSD, as I noted in the SoFi piece. A network that supports several stablecoins and co-owns one has every reason to keep supporting several. Coinbase, a founder here, is the same Coinbase whose x402 standard underpins Cloudflare’s agent payments tool, which settles in USDC. I wouldn’t predict which way this goes. I’d only say that a merchant routing across several providers should expect more than one stablecoin to be in the mix for a while, and should treat which token arrives where as something to track, the same as currency and settlement timing.

Where this argument stops

If you’re a merchant with one PSP, card-only, with no stablecoin acceptance or payouts on the roadmap, none of this needs your attention this quarter. Your settlement may eventually move onto a stablecoin somewhere upstream, as SoFi’s did, and if that happens the design so far suggests you wouldn’t have to notice. The same goes for anyone for whom a single acquirer and a direct integration is already the simplest setup; a shared stablecoin is not a reason to add a layer.

I’d also be careful with the agent case, which is where my original argument started. In Most Agent Payments Won’t Run on Cards I said agent-to-agent spending will mostly move wallet to wallet, without a card network involved. OUSD is on Base and Solana, the same chains that article was about, but nothing in the launch materials says anything about agents. A stablecoin co-owned by the card networks could end up being the token agents pay in, in which case the networks would be inside even the part of the market I expected them to miss. Or agent tooling could stay on USDC, where it is today. I don’t know, and the launch doesn’t tell me.

What I’d take from this week is narrower than the headlines. The card networks have now done more than tolerate stablecoins; two of them co-founded one with Stripe and pointed their own platforms at it. That makes “instead of” look even less likely than it did after SoFi, and “underneath, and owned by the same people” look more likely. For merchants, the practical consequence starts with the stablecoin they’re defaulted into, and it’s worth asking their providers why.