Visa widens stablecoin payouts through Zerohash rails
Visa says eligible Visa Direct clients can prefund accounts and send payouts in stablecoins. For operators, the practical question is where stablecoin settlement fits into existing payout, treasury, and reconciliation workflows.

Visa expanded its stablecoin payout capability on 5 August 2026, with Decrypt reporting that eligible Visa Direct clients can now prefund accounts and send payouts in stablecoins. The move matters because it points to a broader shift in how payment networks think about settlement, especially for businesses that want faster cross-border value movement without rebuilding their payout stack from scratch.
The practical takeaway is not that every payout flow should move on-chain. It is that stablecoins are becoming a more normal settlement option inside existing financial infrastructure. For operators, that changes the evaluation from "can we send crypto?" to "which recipients, corridors, and treasury processes benefit from stablecoin funding or payout rails?"
What Visa is doing and why it matters
Decrypt's report says eligible Visa Direct clients can prefund accounts and send payouts in stablecoins. In a separate LinkedIn post, Adam Berg described the change as "unlocks stablecoins" for Visa. That combination suggests the focus is on payout funding and settlement, not on consumer speculation or retail wallet features.
For marketplaces, platforms, affiliate networks, and other businesses with frequent outbound payments, the appeal is operational. Stablecoin-funded payouts can reduce the number of hops between treasury, conversion, and recipient delivery, especially when the sender already holds digital assets or wants to park value in a more transferable form before distribution.
That said, the announcement should be read as a network capability, not a universal payout recipe. The real test is whether a business can match the rail to the use case, the recipient's preference, and the accounting controls around it.
Limits, exceptions, and what operators still need to monitor
The clearest limitation in the reported change is scope. Decrypt says the capability is for eligible Visa Direct clients, which means it is not a blanket feature for every sender or every corridor. Operations teams should treat eligibility, corridor coverage, prefunding requirements, and recipient delivery rules as the first checklist items before any rollout.
There is also a treasury question. Prefunding can improve payout speed, but it shifts more responsibility onto balance management, conversion timing, and reconciliation. If a business is paying contractors, creators, affiliates, or vendors across multiple currencies, the finance team still needs a clean way to track what was funded, what was converted, and what actually left the system.
For that reason, stablecoin payouts work best when they sit inside a broader payment operations layer rather than as a one-off transfer tool. Businesses need records, status tracking, and a clear owner for exceptions when a recipient cannot take the intended asset or rail.
How payout-heavy businesses should think about the next step
If you run a platform with global outbound payments, this announcement is a reminder to review your payout architecture. The useful questions are practical: where do you already hold stablecoins, where do recipients want fiat, and where does conversion happen today?
That is the same operational problem Radom is built around on its mass payouts page, where businesses can send crypto or fiat payouts from the dashboard, CSV upload, or API. The point is not to replace every existing rail, but to give finance and operations teams a controlled way to move value across crypto and fiat when the business case is there.
Visa's move will probably matter most to operators who already think in terms of treasury, settlement, and payout automation. For everyone else, it is a sign that stablecoins are moving further into mainstream payment plumbing, where the hard work is less about ideology and more about workflow design.
Sources
Exploring how this affects your operating model?