Explain It in 30 Seconds
A merchant wants to accept a customer whose account is held at another institution.
The merchant's acquiring provider and the customer's issuer need a shared way to communicate.
VisaNet provides that processing connection.
The simplified sequence is:
1. A payment request enters through the merchant's acquiring arrangement. 2. The request reaches the issuing side. 3. An approval or decline travels back. 4. Approved transactions proceed through the applicable financial-processing steps. 5. Participants receive the information needed to reconcile and settle obligations.
The account stays with the issuer. The merchant's acquiring relationship also remains separate.
Small businesses normally reach VisaNet through banks or other Visa partners, rather than opening their own direct VisaNet account. [S80]
Where It Sits in Visa
VisaNet is core processing infrastructure within Visa.
A gateway serves the merchant's payment workflow; an issuer processor operates card-program functions; a token service manages credentials.
Those services can connect to VisaNet without becoming the network or requiring Visa to own every account and application. [S29][S35][S49]
The Problem It Solved
Issuers want their customers' credentials accepted beyond their own banking relationships. Acquirers want merchants to serve customers from many issuers.
Separate systems need common messages and responsibilities: who makes the account decision, what an approval means and how obligations are reconciled.
VisaNet supplies the processing connection, while participation rules establish the surrounding framework. [S79][S80]
How It Works — Simple Version
Start with an eligible payment request
The request can originate through an in-store, online or in-app experience.
Its credential can be a supported card number or token. The interface does not determine who owns the underlying account. [S81]
Route the information
The acquiring side sends the request through its processing arrangements.
In the VisaNet Connect - Acceptance interface, Visa validates the client, translates the request and routes it toward the issuer.
The issuer's response returns through that connection. [S64]
Establish the financial transaction
An approval answers the authorization question.
The later processing must still establish the transaction's financial details and resulting obligations.
That is why a payment system needs clearing and settlement functions as well as a fast request-and-response path.
Reconcile the outcome
Participants need records they can match to their own accounts and merchant activity.
The operational job is not complete merely because a checkout displayed an approval. The institutions must understand which transactions occurred and what they owe.
Authorization, Clearing and Settlement
Authorization: may the payment proceed?
Authorization concerns the proposed transaction.
The issuer normally makes the account decision, subject to applicable network arrangements and services.
An authorization can be useful before the final financial processing occurs. It should not be described as every participant already receiving its final funds.
Clearing: what transaction must be accounted for?
Clearing communicates the financial details needed for the parties' obligations.
In VisaNet Connect's documented workflow, a capture follows a previously approved authorization to initiate clearing and settlement. [S64]
That is one supported interface's workflow, not a claim that every payment system or every transaction uses an identical sequence.
Settlement: how are the obligations discharged?
Settlement concerns the obligations between participants through the relevant arrangements.
The merchant then depends on its own acquiring and funding terms.
An issuer approval, inter-institution settlement and the merchant seeing money in its business account are connected events, but not interchangeable timestamps.
A Purchase Does Not Always End at Approval
Consider an illustrative online order authorized before shipment.
Cancellation or return requires an appropriate void, reversal or refund. The original approval does not disappear from the record.
VisaNet Connect exposes distinct authorization, capture, sale, refund and void actions. [S64][S81]
That lets participants connect payment records with what actually happened to the order; the merchant's contract determines its timing.
Why Timeouts and Retries Matter
A missing response leaves the sender unsure whether the first operation occurred. Repeating it as a new instruction can create a duplicate.
VisaNet Connect documents idempotent retries: a matching request can return the original result rather than create another operation. [S81]
Exception handling therefore answers a business question—“Did that payment already happen?”—not just a technical performance measure.
Who Uses VisaNet?
Issuers
Issuers need processing connections that support their customers' payment activity.
They retain responsibility for their own account products and customer relationships.
Acquirers and processors
The acquiring side needs to submit requests, receive responses and reconcile financial information.
Some connect through their own infrastructure; others use approved providers or sponsored arrangements.
Technology partners
Approved partners can provide interfaces between business systems and the network.
Visa's documented direct interface has onboarding and approval requirements. Access to a sandbox is not permission to process live payments. [S64]
Merchants and cardholders
They benefit from the resulting acceptance and payment experience.
Most do not directly operate the institutional network connection. Their immediate relationship remains with their bank or payment provider. [S80]
How VisaNet Fits the Money Flow
Purchase value, network fees, interchange and merchant acceptance charges are different flows.
Visa describes interchange as an interbank transfer; the merchant negotiates acceptance charges with its financial institution. [S54]
VisaNet's processing role does not make the full sale price or the merchant's entire acceptance bill Visa revenue.
Scale
Visa reported 257.545 billion processed transactions for fiscal 2025, ended September 30. [S1]
That is a transaction count.
It is not a card count, a dollar value, the number of merchants or separately disclosed VisaNet product revenue.
Scale can make an established connection useful to many counterparties. It also makes the consequences of a common interruption more extensive.
What It Depends On
Participant systems
Issuers and acquirers must connect their own account and operating systems to the processing framework.
The network cannot make an unavailable customer account function merely by routing the message correctly.
Rules and operational responsibilities
Participants need a common understanding of permitted activity, message meaning and obligations.
Regional rules and actual agreements determine the applicable details. [S79]
Reliability and incident handling
A shared network needs resilient technology and workable recovery procedures.
Visa Europe's June 2018 partial authorization outage disrupted users across the system.
In March 2019, the Bank of England directed implementation of independent-review recommendations and required an independent progress assessment. It explicitly said this was supervisory action, not enforcement or an implied regulatory breach. [S55]
Settlement performance
Visa's specified guarantees create exposure if participants fail to meet their obligations.
That risk is distinct from lending to cardholders. It is one reason collateral, monitoring and participant performance matter to a processing network. [S3]
What Depends on VisaNet
Participating issuers need the contracted processing behind their payment products. Acquirers use it to connect their merchants with other institutions.
Credential, checkout and risk services can interact with that activity while remaining separate capabilities. [S29][S35][S80]
Why It Matters to Visa
A recognizable payment credential needs an operating path to the institution making the account decision, followed by reconcilable financial processing.
VisaNet supplies that path. Its shared infrastructure supports other services and makes reliability commercially essential: one interruption can affect many participants.
Before / After
Without a common processing connection
Institutions must arrange coordination between separate account, merchant and processing systems.
With VisaNet
Participants use shared processing conventions while retaining their own accounts and customer relationships.
The comparison concerns operating arrangements, not a claim that every pre-network bank negotiated individually with every other bank.
What Most People Misunderstand
“VisaNet is a bank.”
It is processing infrastructure connecting institutions. The issuer provides the underlying customer account.
“Approval means all money has finally arrived.”
Authorization and settlement have different purposes. Merchant funding also depends on the acquiring arrangement.
“Every merchant opens a direct VisaNet account.”
Small businesses generally connect through banks or other Visa partners. [S80]
“A mobile wallet replaces the network.”
A wallet can change the customer interface while its supported transactions still use underlying processing infrastructure.
“AI removes the need for issuer decisions and risk controls.”
VisaNet +AI describes network services, including stand-in processing and settlement forecasting.
The published stand-in accuracy claim comes from a specified internal simulation. It is not a guarantee that every outage, issuer or transaction will produce the same result. [S65]
Key Milestones
1973 — Electronic processing
Visa's historical account credits Dee Hock and his team with launching VisaNet.
That was a team and organizational achievement, not the invention of every later payment technology by one person. [S23]
2018–2019 — Resilience under scrutiny
The European partial outage and subsequent supervisory response demonstrated the importance of recovery and incident management. [S55]
Current interfaces and network services
Evidence
- [S1] FY2025 Form 10-K: processed-transaction count and business context.
- [S3] Q3 FY2026 Form 10-Q: participant settlement exposure.
- [S23] Dee Hock memorial: the 1973 processing milestone.
- [S29], [S35], [S49] Adjacent credential, acceptance and issuer-processing roles.
- [S54] Visa fee explanation: interchange and merchant discount.
- [S55] Bank of England: the actual outage and supervisory response.
- [S64] VisaNet Connect getting started: access requirements and processing actions.
- [S65] VisaNet +AI: defined network services and simulation qualification.
- [S79] Participation rules and geographic scope.
- [S80] VisaNet overview: institutional and intermediary access.
- [S81] VisaNet Connect how-to: supported workflows and idempotent retries.