Explain It in 30 Seconds
A payment company wants to use stablecoins in a treasury or settlement workflow.
It needs more than an address.
The company needs to connect bank funding, control who can move value and reconcile what happened.
VSP brings supported parts of that work into one environment.
The initial asset is Open USD, introduced by Open Standard. Providing access to it does not turn every client balance into a Visa bank deposit. [S51]
The platform's role is operating infrastructure, not a guarantee about every asset or financial arrangement connected to it.
Where It Sits in Visa
Within Visa, VSP provides an operating environment around supported onchain activity.
It complements distinct stablecoin-settlement, linked-card and money-movement services. A merchant's card payment, program funding and institutional settlement occupy different layers; using one does not establish use of every VSP function. [S52][S53]
The Problem It Solved
An institution needs more than a stablecoin address.
Its asset, bank funding, redemption, wallet access, approvals and transaction records must work together around an actual treasury or payment obligation.
Assembling these separately creates integration and control work. VSP brings supported functions together, while the institution still decides whether the workflow meets its financial and operating needs.
How It Works — Simple Version
The launch describes a sequence of institutional tasks.
1. Onboard into the supported environment. 2. Establish the wallet arrangement and linked banking relationships. 3. Configure users, permissions and approvals. 4. Mint, hold or move the supported asset. 5. Redeem through the relevant arrangement and reconcile the result. [S51]
These are different actions.
A successful token transfer does not itself demonstrate that an institution has completed fiat redemption or discharged every related payment obligation.
The workflow must connect the technical activity with the financial event it is intended to support.
Two Wallet Arrangements
Wallet-as-a-Service
The current product guidance states that Visa provides key-management technology while the client remains its own custodian.
The supported stack includes minting, burning, managing and transferring Open USD with the relevant controls. [S92]
Visa-managed technology should therefore not be described as Visa taking custody of every client's assets.
Bring Your Own Wallet
A client can retain an existing wallet or custody provider and use VSP for supported on-ramps and off-ramps.
Ongoing mint, burn and transfer activity runs through that provider. [S92]
The two arrangements have different operating boundaries.
A buyer should not assume that every control in the full wallet-service stack automatically governs every action at an existing external provider.
Access, Movement and Redemption
Getting value onchain
The institution needs eligible funding and a supported asset relationship. A bank connection is not an unlimited credit line.
Moving the asset
The wallet arrangement determines how authorized movement is initiated and controlled.
Returning to bank funds
Redemption depends on the asset, provider and payment arrangements. It is separate from confirming an onchain transfer.
Reconciliation must connect these stages to the obligation being fulfilled; a blockchain confirmation alone does not establish fiat receipt.
Controls Have Different Jobs
User access
Permissions define who can initiate sensitive activity.
Approval
Dual control separates initiation from another authorized user's approval.
Destination controls
An allowlist restricts supported transfers to configured destinations.
Audit information
Records establish what happened and who acted.
Visa describes these capabilities within the relevant wallet arrangement. They support accountability, but their effectiveness still depends on sound permissions, destination choices and operating procedures. [S51][S92]
Portal Access Is Not API Availability
The current public FAQ describes the front-end portal and documentation as available, while API access is coming soon.
Institutional eligibility is required. Open USD access remains in beta with geographic and volume limits. [S92]
An operating portal therefore does not establish a generally available integration API or permission for any developer to execute live transfers.
Who Uses It?
Financial institutions
They can explore supported treasury, settlement or customer-product workflows.
Fintechs and payment providers
They may need an operating environment around funding and money movement.
Crypto-native businesses
They can seek connections between onchain operations and established payment infrastructure.
Treasury and operations teams
They need controls, records and a clear relationship between asset movement and financial obligations.
The client job is institutional.
The offering is not an unrestricted consumer wallet or a recommendation to hold a particular asset.
How the Economics Work
The client buys supported infrastructure and services.
Its business case compares reduced integration work, visibility or new funding access with service costs, liquidity, controls and operating effort.
Public materials do not establish one universal VSP price or standalone margin. Transfer face value and stablecoin reserves are not measures of platform revenue.
What It Depends On
Institutional eligibility
Access and capabilities are limited to the relevant clients and markets.
Asset and redemption arrangements
The institution must understand what it holds and how the supported asset can be redeemed.
A platform brand does not make every stablecoin a bank deposit.
Wallet and custody choices
The full wallet-service stack and an existing external provider have different responsibilities.
Approvals and records
The organization must keep its configuration and transaction evidence consistent with its intended use.
Funding and the surrounding obligation
Moving an asset is useful only if it serves the payment, treasury or liquidity task the client actually needs to perform.
These dependencies remain even when one interface simplifies the workflow.
What Depends on VSP
A participating client's treasury or product workflow may rely on the selected wallet, ramp and approval services.
That reliance is specific to its arrangement, not every Visa stablecoin program. VSP does not thereby become a lender, reserve auditor or guarantor for every connected counterparty.
Financing Is a Separate Relationship
Visa's September 2026 announcement describes work with Credit Coop on financing for stablecoin-linked card programs. With customer authorization, settlement information can support assessment and automated financing operations. [S53]
That addresses program liquidity, a different job from VSP's operating infrastructure. It does not mean Visa lends directly to every cardholder.
Lender, borrower, repayment and credit risk remain relevant even when the process uses onchain technology.
Flow Measures Are Not Revenue
The September announcement reported a stablecoin-settlement annualized run rate above $20 billion. [S53]
That expresses recent activity at a yearly pace. It is not a completed year's flow, VSP revenue, a reserve balance or evidence that every linked program uses VSP.
Service terms, actual adoption and operating costs are needed to explain earnings.
Why It Matters to Visa
VSP connects emerging asset workflows with institutional payment operations.
A different form of value movement still needs funding, controls and records. The opportunity is to make those functions work coherently, not to assume stablecoins automatically make every payment cheaper or instantaneous.
Before / After
Separate infrastructure pieces
The institution assembles wallets, funding, approvals and records across providers.
A supported platform arrangement
VSP brings selected functions together, with different wallet choices and explicit availability limits.
The change is integration and coordination. Custody, asset terms and the financial purpose of movement still need to be understood.
What Most People Misunderstand
“Visa supplies the wallet technology, so Visa necessarily holds the assets.”
The current wallet-service guidance says the client remains its own custodian. [S92]
“A portal means the API is generally available.”
The product FAQ distinguishes portal availability from API access still coming soon. [S92]
“Every stablecoin-linked card uses VSP.”
The platform and the wider card-program ecosystem are different scopes.
“Settlement run rate is platform revenue.”
Flow and earned revenue are different measures.
“Onchain financing removes the lender and credit risk.”
The financing relationship still has parties, obligations and repayment risk.
Key Milestones
July 16, 2026 — Platform introduction
Visa announced selected beta access, initially beginning with Open USD. [S51]
September 2026 — Related financing development
The Credit Coop example addressed a separate program-liquidity problem. [S53]
Current product guidance
The public FAQ adds explicit custody, wallet-choice and portal-versus-API boundaries.
These details qualify the operating proposition rather than establishing unrestricted general availability. [S92]
Evidence
- [S51] Original platform, supported asset and selected beta introduction.
- [S92] Current product and FAQ, including custody, wallet arrangements and interface availability.
- [S52] Separate linked-card and money-movement ecosystem context.
- [S53] Settlement flow measures and the distinct financing relationship.
The institutional workflow and economic comparisons are explanatory analysis, not asset advice, reserve certification or a live integration test.