Stablecoin payments counterparty risk: Visa is hunting for a new settlement partner because Mastercard bought the last one

What Visa put out to tender on August 18

On August 18, 2026, CoinDesk reported — based on documents it had seen — that Visa is looking for a new stablecoin settlement partner. Follow-on coverage put the requirements plainly: Visa wants a settlement and over-the-counter provider holding cryptocurrency exchange licences in the U.S., Canada, the U.K. and Singapore, able to convert between different stablecoins, supply institutional liquidity, and settle across jurisdictions. The scope reportedly includes processing for Open USD, the dollar stablecoin project fronted by Stripe, Visa and Mastercard.

The reason the seat is empty is not a dispute or a failure. On August 3, 2026, Mastercard completed its acquisition of BVNK — signed in March, valued at up to US$1.8 billion including US$300 million of contingent consideration. BVNK is infrastructure: holding, moving and converting value across fiat and blockchains in more than 130 countries. It had been handling stablecoin settlement for Visa, and had been supplying the stablecoin plumbing behind Visa Direct payout pilots since January 2026. The moment the deal closed, Visa's settlement leg belonged to its principal competitor.

Visa declined to comment on the reported process. It has not confirmed the RFP publicly, named candidates, or disclosed a timetable. Its separate ZeroHash arrangement from August 5 — which we covered in Visa Direct's stablecoin payouts — reportedly does not span all four licensed markets the RFP asks for.

Hold the size of the entity for a second. Per Visa's own newsroom, the Visa Stablecoin Platform launched on July 16, 2026 into a network of roughly 15,000 financial institutions and more than 200 million merchant locations, on top of a company that settles on the order of US$15 trillion a year. That is the organisation currently writing an RFP because its stablecoin vendor was acquired.

The line in the reporting that should stop you: the candidate pool has shrunk

The vacancy is a story. The substitution problem is the analysis.

Per the reporting, the requirement to be licensed as a crypto exchange in the United States, Canada, the United Kingdom and Singapore at the same time — while also running institutional liquidity and multi-stablecoin conversion — leaves a very short list. Visa is not short of money, relationships or lawyers. It is short of legally interchangeable suppliers.

That is the precise definition of counterparty concentration, and it is worth stating in plain terms: a supplier you cannot easily replace is not a supplier, it is a dependency. The regulatory bar that makes a licensed settlement partner trustworthy is the same bar that makes it scarce. Both properties come from the same source, and you do not get to keep one without the other.

Now scale that observation down to your business. If four-market licensing narrows the field for a company settling trillions, how many independent firms actually sit behind the consumer-facing "stablecoin payments" brands operating in your markets? Fewer than the number of logos suggests. Payment plumbing consolidates quietly: several front ends routinely share one licensed back end. Your provider's brand is not your counterparty. Your provider's provider is.

Stablecoin settlement is not the same product as a stablecoin payment

The two get collapsed into one phrase constantly, and the difference is the whole subject of this article.

Settlement, in the sense Visa's RFP means it, is the business of moving value on behalf of other parties: taking one stablecoin and delivering another, converting into and out of local currency, holding institutional liquidity so both sides of a trade clear, and doing all of it under licence in each jurisdiction it touches. That work genuinely requires licensed intermediaries. It cannot be done any other way, and nobody sensible pretends otherwise.

A payment, in the sense a merchant means it, is much smaller. A customer has USDC. You want USDC. There is no currency to convert, no local institution to exit through, no float to warehouse. It is one on-chain transfer from one wallet to another, final in seconds. There is no settlement partner in that picture because there is nothing for a settlement partner to do.

Most of the risk merchants carry in crypto payments comes from being sold the first architecture to solve the second problem. You wanted to be paid; you were given a balance in someone else's system, plus a promise to move it later.

The hop count test

Here is a diagnostic you can run this afternoon on any payment method you accept. Count the parties that hold a balance between the moment your customer pays and the moment the funds are under your sole control:

• Card payment: acquirer, sometimes a payment facilitator, sometimes an aggregator's pooled account, then your bank. Three or four holders, plus a reversal window that stays open for months.
• Custodial crypto processor: the processor's hot wallet, an exchange or OTC desk for conversion, sometimes a partner licensed in your market, then your withdrawal. Two to four holders, each one a business that can be acquired, delicensed or wound down.
• Direct on-chain acceptance: zero. The customer's transfer credits your wallet. There is no intermediate balance because there is no intermediate.

Every entry on that list above zero is a company whose ownership, licence status and solvency you are exposed to without a contract that lets you do anything about it. Visa just demonstrated that the exposure is real even when the dependent party is the largest network in payments.

Why the substitution problem is worse for you than it is for Visa

Visa's version of this problem is an inconvenience. It will run a process, pick a firm, negotiate hard and carry on. Yours is not symmetrical, for three reasons.

You will not be told in advance. Visa knew BVNK was being acquired the day it was announced in March, and had until August to plan. A merchant typically learns that their processor has been acquired, restructured or wound down from a support email, or from a failed payout. We wrote about the sharp end of that in what happens when your crypto payment provider shuts down — acquisition is the gentler cousin of the same event, and it moves your money through new hands just the same.

Your switching cost is concentrated in one week. Visa's integration work is spread across a procurement team. Yours is your checkout, your POS terminals, your invoice templates, your webhook handlers, your reconciliation, and every subscription customer who has to re-authorise something. Migrations are where revenue leaks.

Your balance is sitting there while it happens. This is the asymmetry that matters. During any transition, whatever is in the custodial float belongs to you in the accounting sense and to somebody else in the possession sense. There is no version of that arrangement where you are the party with leverage.

Open USD, and the difference between a coin choice and a platform choice

One more detail in the RFP deserves attention: the mandate reportedly covers settlement for Open USD. OUSD was introduced by Open Standard in June 2026 with a consortium of 140-plus businesses, and it is the first asset supported on the Visa Stablecoin Platform. It is also a coin that arrived after the market had already standardised on two.

The lesson for merchants is not that OUSD is good or bad — it is far too early for anyone to say, and we are not going to pretend otherwise. The lesson is structural: when a rail is built around a specific coin, choosing the coin quietly becomes choosing the platform. Then the coin's fortunes, the consortium's politics and the platform's vendor arrangements all become your problem, in that order.

The way out is to stay issuer-agnostic at the acceptance layer. Take the dollar token your customer actually holds today — in practice USDT or USDC, which behave quite differently by region — settle it directly, and keep the freedom to add another one later without re-platforming. A merchant who accepts USDC and USDT into their own wallet has an opinion about neither consortium.

How Payzum fits: acceptance with no settlement partner to replace

Payzum is a non-custodial, crypto-only payment processor, and in the context of this story the definition does real work.

Funds go straight to wallets you control. Payzum never holds, pools or controls the money. There is no Payzum balance, so there is nothing to freeze, nothing to migrate during an ownership change, and no float that could be caught mid-transition. Settlement is the payment — the same on-chain transfer that pays you is the one that finalises.

Volatility is handled without adding a custodian. Accept what the customer holds, with optional auto-conversion to USDC or USDT so you end the day in dollars. That is a routing decision, not a deposit.

Finality replaces the reversal window. On-chain payments are not reversible by the payer's issuer. No chargebacks, no acquirer, no card-network fees — which is a different conversation from counterparty risk, but the same underlying property: the payment is over when it is over.

Multiple chains, no single point of dependence. Bitcoin, Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, BNB Chain and Avalanche, with typical confirmations of roughly 0.4s on Solana and about 2s on Base and Polygon, and network fees measured in cents rather than percentage points.

What Payzum does keep is the operational layer, which is the part you actually want a vendor for: hosted checkout, payment links and buttons, invoices with expiry and overpayment detection, subscriptions, POS with a fresh QR per sale and PIN-protected cashiers, CSV mass payouts, a REST API with signed webhooks, 2FA, encrypted secrets and a full audit log. If Payzum vanished tomorrow, your wallet, your keys and every past payment would be exactly where they are now.

How it works, step by step

1. Connect your own wallet. You provide the receiving addresses per chain. Payzum never takes custody, and there is no account balance to reconcile against.
2. Choose the instruments you need. Hosted checkout or payment links for online sales, invoices with expiry for B2B, subscriptions for recurring plans, POS QR codes for the counter, CSV batches for paying people out.
3. Set your settlement preference. Keep what the customer sends, or auto-convert to USDC or USDT so your books stay dollar-denominated. Pick the chain per flow: Solana or Base for speed and low fees at the counter, whichever your customers use for online checkout.
4. Wire it into your systems. Signed webhooks fire on confirmation so your order system, PMS, ERP or CRM reacts on its own — including at 2am on a Sunday, because on-chain settlement does not observe banking hours.

What this looks like in three real payment flows

Counterparty risk is abstract until you put it against a specific way you collect money. Three examples:

• An online store settling internationally. Today: card acquirer holds the funds, releases in a few days, and can claw back for months. With direct acceptance: the buyer pays USDC at hosted checkout, the funds land in the store's wallet in seconds, and the only party who ever held them was the buyer.
• A services firm invoicing clients abroad. Today: a wire crosses two or three correspondent banks, arrives short after deductions, and cannot be traced from either end. With direct acceptance: an invoice with expiry and a payment reference, paid on-chain, visible to both parties the moment it confirms — no intermediary to lose, and none to blame.
• An operator running weekly payouts. Today: prefunding a custodial balance and hoping the provider's banking stays intact through the weekend. With direct acceptance: CSV mass payouts and EVM stablecoin payouts sent from a wallet you fund yourself, when you choose, with no float parked at a third party in between.

Intermediated stablecoin settlement vs. direct acceptance

Both architectures are legitimate. They answer different questions. This table is about which question you are actually asking.

Three fair objections

"Visa needs licensed partners because it does something genuinely harder than I do. Isn't this comparing apples and oranges?"

Yes, deliberately. Visa's RFP is for cross-jurisdiction conversion, institutional liquidity and settlement on behalf of thousands of institutions. That is a harder job and it does require licensed counterparties. The point is not that Visa should have avoided them — it is that most merchants inherit that architecture without needing it. If your customer holds dollars-on-chain and you want dollars-on-chain, you bought a currency-conversion machine to solve a non-conversion problem. Whenever you genuinely do need fiat conversion, use a licensed provider for that leg specifically, and keep it out of the acceptance path.

"No intermediary sounds like no protection. Who do I call when something goes wrong?"

Fair, and the honest answer is that the protections are different rather than absent. You lose the ability to reverse a payment after the fact — and so does everyone else, which is why there are no chargebacks. You gain a permanent, independently verifiable on-chain record of every settlement, plus operational controls at the account level: 2FA, encrypted secrets, signed webhooks, a full audit log, and per-cashier and per-terminal analytics on POS. What you do take on is key management, which is a real responsibility and one we walk through on the call.

"We need money in a bank account eventually. Doesn't that put an intermediary back in the chain?"

For the portion you convert, yes — and that is a legitimate use of a licensed provider. The improvement is in where the intermediary sits. Today it sits in the middle of every sale, holding funds you have already earned. In the non-custodial version it sits at the end, applied only to the amount you decide to convert, at a time you choose, from a balance already in your own wallet. Payzum is crypto-only and does not settle to bank accounts; what it changes is that the intermediary stops being a mandatory checkpoint on the way to you.