Visa Stablecoin Platform (VSP): What It Means for Banks and Fintechs in 2026

TL;DR

The Visa Stablecoin Platform (VSP) is Visa's enterprise infrastructure for minting, moving, and managing Open USD, launched in limited beta on July 16, 2026. Access requires an existing Visa Access ID and Business Identification (BID) number, so VSP is not open to any business today, only Visa's existing client base. VSP offers two paths: Wallet-as-a-Service, where Visa provides key-management technology but the client remains the custodian, or Bring Your Own Wallet, where VSP only handles on-ramp and off-ramp while an existing custody provider handles minting, burning, and transfers. It supports Ethereum, Solana, and Tempo today, and Open USD only.

Visa Stablecoin Platform: Key Facts

Who Should Use the Visa Stablecoin Platform? Who Probably Shouldn't?

You can likely evaluate VSP if:

• You already hold a Visa Access ID and Business Identification (BID) number, meaning you have an existing commercial relationship with Visa as an issuer, acquirer, or program partner.
• You specifically need Open USD, not another stablecoin, for treasury, settlement, or liquidity operations.
• Ethereum, Solana, or Tempo cover the chains your product needs.
• You can operate within Visa's current volume and geographic limits during the beta.

You probably cannot use VSP yet if:

• You have no existing Visa relationship. Access requires a Visa Account Executive to issue you a BID; there is no public sign-up.
• You need a stablecoin other than Open USD. USDC, USDT, PYUSD, RLUSD, and EURC are not supported.
• You need chains beyond Ethereum, Solana, and Tempo.
• You need an API today. Integration currently runs through the portal; programmatic access is not yet live.
• You are a pure crypto exchange, remittance operator, or stablecoin issuer without a card network relationship. Nothing in Visa's materials suggests VSP is open to this segment during the beta.

What Does VSP Replace? VSP vs. Fireblocks, BitGo, Copper, and Fystack

VSP is actually two different products wearing one name, and which one you're comparing changes the answer completely.

Path 1, Wallet-as-a-Service, is a custody product. Think of it like signing up for Fireblocks or BitGo: Visa runs the wallet technology, you log into a dashboard, and you manage Open USD through it. This path genuinely competes with custody vendors, but only for Open USD specifically. It does not touch any other asset you hold.

Path 2, Bring Your Own Wallet, is not a custody product at all. It's a payment rail. Picture it like adding a new payment gateway on top of a bank account you already have: VSP just moves fiat in and out (on-ramp and off-ramp) to fund Open USD. Your actual custody, meaning who holds the keys and signs transactions, stays exactly where it already is, whether that's Fireblocks, BitGo, Copper, or a self-hosted setup like Fystack. VSP never touches that part in this path.

So the honest one-line answer: if you pick WaaS, VSP replaces a custody vendor for Open USD. If you pick BYOW, VSP replaces nothing, it just adds a funding pipe on top of the custody you already run.

Where Fystack specifically differs from Fireblocks, BitGo, and Copper: those three are SaaS-only. You never run the infrastructure yourself, you always operate inside their hosted environment. Fystack works either way: you can self-host the MPC engine on your own servers, so no third party ever touches your keys, or use Fystack's hosted version if you want a managed option without giving up an open-source stack you can audit or move off later. That flexibility, self-hosted or hosted, on your terms, is what "self-hosted custody infrastructure" means in the rest of this article, and it's the piece VSP's Wallet-as-a-Service does not offer today: with WaaS, you're inside Visa's environment, full stop.

Where Does Custody Actually Sit in VSP?

This is the question buyers should ask before anything else, and the answer differs by path.

With Wallet-as-a-Service: per Visa's own product documentation, Visa provides the key-management technology and the client remains its own custodian, with maker/checker dual approval on sensitive operations, device-bound passkey signing instead of shared credentials, and destination-wallet allowlisting. Visa has not disclosed whether the underlying architecture is MPC, HSM-backed, or another model, so treat "you remain your own custodian" as a legal and operational framing until Visa publishes the technical architecture.

With Bring Your Own Wallet: custody stays exactly where it already is, with your existing MPC or custody provider running its own withdrawal and approval workflow. VSP never touches signing or key material in this path; it only moves fiat in and out through the on-ramp and off-ramp.

This means the practical answers to "who signs" and "who's liable" depend on which path you pick: with WaaS, your organization signs (via passkey) and Visa's terms govern what "custodian" means in the beta agreement, details not yet public. With BYOW, your existing provider's terms and architecture apply unchanged, whether that is a vendor like Fireblocks or self-hosted MPC infrastructure you operate yourself. AML and transaction monitoring responsibility, and which KYT vendor screens transactions, are not detailed in Visa's public materials for either path.

Which Stablecoins and Chains Does VSP Support?

Open USD only, on Ethereum, Solana, and Tempo, as of the beta. Visa has not published a timeline for adding USDC, USDT, PYUSD, RLUSD, EURC, or tokenized deposits to VSP, and has not confirmed additional chains beyond the three above. If your roadmap depends on multi-stablecoin or multi-chain support, that is not available in VSP today regardless of implementation path.

Does VSP Have an API for Developers?

Not yet. Visa's product page states the front-end portal and documentation are available now so teams can review specs and plan integration, but API access is "coming soon." No SDKs, language bindings, sandbox environment, or rate limits have been published. Teams evaluating VSP today are evaluating a portal-driven beta, not an API-first integration.

How Much Does VSP Cost?

Not disclosed. Visa has not published licensing fees, per-transaction fees, custody fees, minting fees, or settlement fees for VSP. Access and pricing go through a Visa Account Executive on a contract basis. Any cost comparison against Fireblocks, BitGo, Copper, or self-hosted infrastructure cannot be made responsibly until Visa publishes pricing, and any figure you see elsewhere online should be treated as speculation.

What Compliance and Security Standards Does VSP Meet?

Confirmed from Visa's materials: maker/checker dual approval on sensitive operations, device-bound passkey signing, and destination-wallet allowlisting. Not confirmed in Visa's public materials: SOC 2, ISO 27001, or PCI DSS certification specific to VSP, which KYT or transaction-screening vendor is used, Travel Rule and GENIUS Act compliance mapping specific to VSP, or GDPR-specific data handling terms. Visa as a company carries extensive compliance infrastructure, but none of that has been mapped explicitly onto VSP in public documentation. Institutions with strict vendor-compliance checklists should request this directly from their Visa representative rather than assume standard terms apply.

Is VSP Live in Production, or Still in Beta?

Still beta, with volume and geographic limits, and no public general-availability date. Visa has not named beta clients, published a case study, or disclosed transaction volume, TPS, or the number of institutions participating. For a bank evaluating whether to build a roadmap around VSP, the honest current state is: a beta program with a small number of unnamed participants, not a production-proven platform with a public track record yet.

How Do You Migrate to VSP From an Existing Custody Provider?

Visa has not published a migration guide, and no public detail exists on seed import, wallet address portability, or transition timelines. The Bring Your Own Wallet path is the lower-friction option for teams already on another provider, since it adds Open USD ramps without requiring a custody migration at all. Wallet-as-a-Service would require a genuine migration if you want to move existing custody workflows onto Visa's key-management stack, and that process is not documented publicly as of this beta.

What's the ROI of Using VSP?

Not quantifiable from public information, because pricing is not published. The general pitch behind managed platforms like VSP is fewer engineers needed to build custody and compliance tooling in-house, faster time to a working stablecoin product, and lower ongoing compliance overhead from relying on an established, regulated partner. Whether that pitch beats the cost of an existing custody vendor or a self-hosted build depends entirely on pricing Visa has not disclosed, so treat any ROI claim, including this one, as directional until you have a quote.

If You're Not Eligible for VSP Yet, What Should You Do?

Visa's Broader Stablecoin Strategy

VSP is one step in a build-out Visa started in 2021: live USDC settlement (December 2025), settlement expanded to nine blockchains reaching a $7 billion annualized run rate (April 2026), a privacy-focused settlement pilot with Brale on Canton Network (June 4, 2026), a tokenized-deposits initiative announced at Visa's Payments Forum (June 10, 2026), co-founding the 140-plus partner Open USD consortium with Stripe, Mastercard, American Express, BlackRock, Coinbase, Google, Ripple, BNY, Standard Chartered, and early adopters like DBS Bank (June 30, 2026), and now VSP itself (July 16, 2026). Read as a sequence, this is Visa building settlement, deposit, and onboarding infrastructure across every layer a bank might need, so it stays in the middle of stablecoin flows regardless of which token or chain wins.

Conclusion

VSP is real infrastructure, not vaporware, but it is early: beta only, one asset, three chains, no public API, no published pricing, and access limited to Visa's existing client base. If you already have a Visa relationship and only need Open USD, Bring Your Own Wallet is likely the lowest-friction way to try it without touching your existing custody stack. If you don't have that relationship, or need multi-chain, multi-asset custody today, that gap is exactly what self-hosted custody infrastructure like Fystack is built to close, on your own timeline, not Visa's beta list.

FAQ