For a long time, talking about Visa was almost synonymous with talking about cards. For banks, fintechs, and payment companies, the association made sense: the company built one of the world's largest payment networks and became a central part of global financial infrastructure.
That definition no longer tells the whole story.
In fiscal Q3 2026, Visa reported US$11.6 billion in net revenue, up 14% year over year. At the same time, revenue from value-added services reached US$3.8 billion, up 33% year over year, roughly one-third of total revenue.
The numbers point to an important shift. The company’s growth increasingly extends beyond transaction processing to the broader infrastructure and services surrounding each transaction.
Issuer processing, acceptance, security, fraud prevention, data, advisory, money movement, and banking infrastructure are now part of a much broader proposition.
Visa VAS, or Visa Value-Added Services, helps explain how the company is expanding across these different layers of financial infrastructure. The expression “Visa as a Service” may also be used informally to describe this evolution, although it is not the official name of a single Visa product.
For financial institutions, this changes the central question. Connecting to a payment network remains important, but banks must also determine which infrastructure capabilities they should consume, integrate, or orchestrate.
This shift is happening as banks modernize legacy systems, support real-time payments, expand digital channels, and maintain security and operational resilience.
The evolution of financial infrastructure shows why these topics are increasingly connected, as payments, risk, processing, and banking systems depend on many of the same architectural decisions.
How Visa is evolving beyond the payment network
The payment network remains the foundation of the business. What has changed is the number of services built around it.
Today, the Visa ecosystem reaches across different parts of the financial journey. This includes capabilities related to issuing, acceptance, risk, identity, processing, advisory, data, and money movement.
Visa organizes its value-added services portfolio across areas including Issuing Solutions, Acceptance Solutions, Risk and Security Solutions, and Advisory and Other. In fiscal Q3 2026, the company reported growth across these portfolios.
The term Visa ecosystem therefore describes this landscape more accurately than the traditional perception of a company focused primarily on cards.
One clarification is important: Visa as a Service is not the name of a single standalone product. In this article, the expression is used only as an editorial description of the broader infrastructure and value-added capabilities available across the Visa ecosystem. Visa VAS is the established term for the company’s value-added services.
For banks, this matters because a relationship with payment infrastructure can now involve much more than connecting to a network.
What is changing in the business model
The transformation can be understood through the composition of the business.
The network infrastructure connecting issuers, acquirers, merchants, and other participants remains foundational. Alongside it, a growing layer of services is becoming more involved in processes closer to the day-to-day operations of financial institutions.
Some of the most important shifts include:
- A growing share of revenue associated with services beyond traditional payment-network economics;
- Deeper participation across different points of the financial technology stack;
- Monetization of capabilities related to security, data, processing, money movement, and advisory;
- Greater relevance to architecture, technology, and digital transformation teams, in addition to payment teams.
Recent numbers reinforce this direction. In fiscal Q3 2026, value-added services revenue reached US$3.8 billion, compared with US$2.8 billion in the same quarter of 2025. Growth was driven primarily by Issuing Solutions, Acceptance Solutions, and Advisory and Other Services.
In practice, this shows a company seeking to capture value across more points of financial infrastructure.
For a bank, the number of available services is only part of the analysis. The central issue is identifying which capabilities solve real problems in the existing architecture.
Visa ecosystem: the major infrastructure layers banks should understand
Thinking about the Visa ecosystem in layers helps avoid a view based solely on product names.
For a financial institution, the priority is to understand where each capability can fit into the existing architecture and what dependencies it creates.
The main layers include:
- Issuer processing;
- Merchant acceptance;
- Risk and security;
- Advisory and analytics;
- Money movement;
- Core banking;
- Value-added services;
- Integration with banking platforms and internal systems.
This view also helps distinguish modernization from replacement. Institutions can evolve their infrastructure without replacing the core, processor, or entire payment stack at once.
In many cases, modernization can happen incrementally by connecting new capabilities to what already works.
This is where concepts such as Payment Orchestration become important: when different providers, rails, and systems need to operate in coordination.
Issuer processing and card infrastructure
Issuer processing is one of the layers most directly connected to issuer operations.
In practical terms, it involves capabilities required to process card transactions and support issuing activities. For banks, this can provide an alternative to highly customized environments that are difficult to evolve.
Choosing a processor, however, is only one part of the decision.
The infrastructure needs to connect with fraud, identity, ledger, servicing, digital-channel, and other banking architecture components.
This is especially relevant for mid-market institutions. When a central platform contains extensive customization, each change can affect multiple parts of the technology environment.
A more modular architecture can help reduce that dependency, provided integration is carefully planned and responsibilities between systems are clearly defined.
Visa currently presents issuing solutions that combine issuer processing and core banking capabilities through a more modular approach.
Acceptance and merchant services
The acceptance layer expands the discussion to the merchant side of payments.
This includes capabilities related to:
- Digital acceptance;
- Payment enablement;
- Merchant connectivity;
- Different payment channels;
- Checkout experiences;
- Integration across payment methods.
This layer also matters to banks, fintechs, marketplaces, and digital platforms whose primary positioning may extend beyond payments. These organizations may need to support different methods and channels as payment behavior becomes more diverse.
When multiple paths are available to process a transaction, orchestration also becomes relevant. It can coordinate providers and routes without turning every new payment method into a separate integration.
Risk, security, and fraud capabilities
As the ecosystem expands, security becomes even more important.
Risk can relate to the transaction, identity, behavior, or the institution's own operations. That is why risk and security capabilities are central to Visa value-added services.
Visa expanded this area through its acquisition of Featurespace, a company specializing in AI technology for fraud and financial-crime prevention. The acquisition was completed in December 2024, bringing the company's capabilities into Visa's Risk and Identity Solutions business.
Detecting suspicious transactions is one part of a broader objective: expanding protection capabilities to address different risk contexts across the financial journey.
For banks, this reinforces an important trend. Security is becoming part of the processing and decision-making architecture itself, rather than operating as an isolated layer.
Advisory and data-driven services
Financial infrastructure involves more than software.
Data, benchmarking, analytics, and specialized expertise can also influence business and technology decisions.
Visa's advisory business operates in this space, supporting institutions on performance, strategy, operations, and payments. In fiscal Q3 2026, the company reported delivering 1,200 consulting projects for more than 700 clients across more than 100 countries and territories.
In practice, data-driven services can help institutions answer questions such as:
- Where is performance being lost?
- Which processes have the greatest optimization potential?
- How can portfolio performance improve?
- Which behaviors or trends deserve attention?
- Where could an infrastructure change create the greatest impact?
This type of service complements technology modernization by connecting architecture decisions to business objectives.
Money movement beyond traditional card rails
Money movement is also becoming more diverse.
Alongside traditional card payments, institutions need to consider account-to-account transfers, cross-border payments, payouts, real-time payment networks, and new forms of settlement.
The growth of Visa Direct illustrates this shift. In fiscal Q3 2026, transactions through the service grew 21% year over year.
The architectural consequence is straightforward: as more rails coexist, an infrastructure built around a single payment mechanism becomes less sustainable.
In this scenario, the institution needs to select routes, coordinate integrations, handle exceptions, and maintain visibility across the flow.
More ways to move money create more possibilities. They also create more dependencies.
Core banking and embedded infrastructure
Core banking represents one of the deepest extensions of this strategy because it touches the institution's central infrastructure directly.
Visa's acquisition of Pismo expanded its presence in this area. The company presents the platform as a cloud-native solution for core banking and payment processing, covering capabilities such as deposit accounts, cards, lending, and corporate banking.
Its strategic relevance comes from the possibility of modernizing parts of the architecture progressively, instead of approaching transformation exclusively as a complete system replacement.
For banks, this means evaluating APIs, modularity, scalability, and the ability to integrate with existing systems.
The topic also connects directly to Core Banking, especially when an institution needs to modernize its foundation without compromising operational continuity.
Visa VAS: why value-added services matter to the next phase of growth
Visa VAS describes an increasingly important part of the company's growth strategy.
The portfolio brings together different capabilities that add services around payment infrastructure, including risk, security, issuing, acceptance, advisory, and other solutions associated with Visa’s relationships with financial institutions and businesses.
Recent growth helps illustrate its importance. In fiscal Q3 2026, VAS revenue reached US$3.8 billion, up 33% year over year according to the company's quarterly report.
Beyond the revenue figure, the movement reflects a broader strategy of participating in more of the processes that support the financial system.
This can deepen integrations between Visa infrastructure and customers' technology environments. For banks, understanding VAS therefore also means identifying which services make sense within their own architecture.
Why mid-market banks should pay attention
For a mid-market bank, this discussion has a practical dimension.
Large institutions may have extensive engineering, security, data, and architecture teams. Smaller and mid-sized banks need to make more deliberate choices about what to build internally and what to consume as a service.
Common challenges include:
- Limited engineering resources;
- Pressure to modernize legacy systems;
- Increasing fraud and compliance demands;
- The need to launch products faster;
- Difficulty maintaining highly specialized infrastructure;
- The need to balance innovation, control, and operating cost.
Consuming mature capabilities can address some of these needs. The value of an external platform, however, depends on how well it fits the institution's operating and architectural model.
Before adopting any layer, the bank needs to understand integration, dependencies, governance, data ownership, resilience, and total operating cost.
Visa infrastructure: how Featurespace strengthens the risk layer
The acquisition of Featurespace shows how Visa infrastructure can expand into specialized capabilities.
The company was incorporated into Visa's Risk and Identity Solutions business, strengthening fraud prevention and risk-scoring capabilities through artificial intelligence and real-time analysis.
This evolution makes sense in an environment where payments are becoming faster and risk decisions need to keep pace.
As decision windows become shorter, integrating risk intelligence into payment flows becomes increasingly important.
The move also reinforces the value-added services strategy. Infrastructure now participates both in moving transactions and in the decisions that help protect them.
For a deeper look at how ARIC, Adaptive Behavioral Analytics, and real-time fraud decisioning fit into banking architecture, see our guide to Featurespace and ARIC.
How Pismo expands the core banking layer
Pismo represents another relevant step in the ecosystem's expansion.
Its cloud-native platform combines core banking and payment-processing capabilities with features related to accounts, cards, credit, and digital wallets.
For institutions dealing with legacy systems, the possibility of gradual modernization is especially relevant.
Visa's proposition allows banks to integrate new capabilities while preserving parts of the existing infrastructure that still serve the operation effectively.
This connects three important concepts: APIs, modularity, and speed to market for new products.
It also illustrates how the Visa ecosystem can occupy different positions within an institution's architecture, extending its role beyond the payment network.
[Insert the approved link to NTConsult's Pismo article here before publication.]
What this evolution means for bank architecture
At this point, the discussion moves from Visa’s expansion to the decisions each bank must make.
Access to more capabilities does not automatically solve financial architecture problems. Independent integrations for every service can actually create new challenges.
A bank adding new platforms needs to consider:
- Legacy core systems;
- API strategy;
- Orchestration across different providers;
- Identity and security;
- Settlement and reconciliation;
- Event-driven and real-time processes;
- Observability;
- Resilience;
- The risk of excessive vendor dependency.
A successful architecture depends on the coherence of its components and on its ability to evolve without turning every change into a high-risk project.
For institutions operating complex financial environments, this distinction matters. Modernization can preserve effective parts of the existing infrastructure while creating new integration layers for the capabilities the business needs next.
Why orchestration becomes more important as the ecosystem expands
More modularity creates more options. More options create more integrations.
That is why orchestration becomes more important as the ecosystem grows.
In an architecture with different providers and rails, an orchestration layer can help coordinate:
- Multiple payment rails;
- Routing;
- Retries and failover;
- Exception handling;
- Settlement flows;
- Observability;
- Business continuity when a dependency fails.
An orchestration layer can reduce the complexity that would otherwise arise if every system needed to communicate directly with every other component in the architecture.
In this context, Payment Orchestration can be an important part of a more flexible integration strategy.
Where workflow orchestration fits
APIs are essential to integration, but financial processes frequently require additional coordination.
These processes often involve multiple steps, decisions, systems, and exceptions. Managing them requires workflow coordination beyond simple application-to-application communication.
Examples include:
- Onboarding;
- Dispute handling;
- Fraud review;
- Payment exception management;
- Settlement reconciliation;
- Compliance workflows.
When a process crosses multiple systems, orchestration helps define what happens at each stage, which conditions must be met, and how the workflow should react when something goes wrong.
This is where solutions such as Camunda Services can support a financial-process modernization strategy.
How real-time payments change the infrastructure decision
The expansion of the financial ecosystem is happening alongside another transformation: the rise of real-time payments. Cards are now one part of a more diverse payment environment.
Institutions need to consider different rails, expectations of immediate availability, and processes that cannot depend on traditional operating cycles.
This changes the architecture.
When a transaction needs to be processed in real time, activities such as reconciliation, exception handling, monitoring, and availability must keep pace as well.
Repeatedly replacing the core as new payment methods emerge would be costly, disruptive, and unsustainable. The architecture needs to evolve without requiring a complete rebuild with every market change.
A more modular approach can help an institution support:
- Coexistence of different payment rails;
- Faster payment experiences;
- Near-real-time processing;
- New money-movement flows;
- Reconciliation and exception handling;
- Continuous evolution without recurring core replacements.
This scenario reinforces the importance of a consistent Real-Time Payments strategy.
Where stablecoins may fit next
Stablecoins add another infrastructure option for money movement and settlement alongside traditional financial systems.
Interest is particularly connected to scenarios where continuous availability, cross-border movement, liquidity, and programmable payments could create operational benefits.
Visa itself has been testing different applications. In 2025 and 2026, the company announced initiatives involving stablecoin funding, payouts, and settlement. In 2026, it also announced expanded USDC settlement capabilities for institutional partners in the United States.
For banks, deciding whether and where stablecoins create value requires a broader evaluation of:
- Regulatory requirements;
- Risk;
- Liquidity;
- Custody;
- Integration with existing systems;
- Reconciliation;
- Governance;
- Impact on treasury and settlement.
For now, the more likely scenario is coexistence between traditional infrastructure and new forms of money movement.
Stablecoins may therefore become another component of financial architecture instead of replacing every existing rail and system.
How agentic commerce could change payments infrastructure
If payments are becoming more modular, the next challenge may come from who initiates transactions.
In agentic commerce, AI systems can participate in purchasing journeys, make decisions within defined parameters, and initiate transactions on behalf of people or businesses.
This creates new questions for financial infrastructure.
Who authorized the transaction? What was the limit? Which agent made the decision? What happens when an operation falls outside expected behavior?
Key challenges include:
- Machine-initiated transactions;
- Identity and authorization;
- Transaction limits;
- Fraud controls;
- Consent;
- Auditability;
- Exception handling;
- Orchestration across agents, merchants, banks, and networks.
Visa has already been developing its approach to this scenario. In 2026, the company presented initiatives related to intelligent commerce and infrastructure for transactions initiated by AI agents.
The architectural implications deserve as much attention as the technology’s potential.
Before allowing agents to initiate financial operations, institutions will need to ensure identity, authorization, governance, security, and the ability to audit every relevant decision.
What mid-market banks should evaluate before connecting to the ecosystem
The ecosystem's expansion gives banks more capabilities to evaluate and makes selectivity even more important.
Before connecting a new layer to the architecture, the bank needs to understand which problem it is trying to solve and what the operational impact of that decision will be.
A consistent evaluation can consider:
- Strategic value: does this differentiate the bank, or is it already a commodity?
- Legacy: which limitations of the current architecture need to be addressed?
- Priority: is it more urgent to modernize processing, fraud, core banking, or money movement?
- Integration: how much effort will be required to connect the new capability?
- Dependency: does the new component create vendor lock-in?
- Control: who controls the data, rules, and processes?
- APIs: is the integration mature and flexible enough?
- Resilience: what happens when the provider becomes unavailable?
- Regulation: which requirements need to be met?
- Cost: what is the total operating cost, rather than just the solution price?
- Time to market: how much time could the change save when launching new products?
- Internal capacity: does the bank have the team needed to operate and evolve the architecture?
The goal is to find the right balance between speed and control.
In projects involving complex financial platforms, integrations, orchestration, and modernization, NTConsult works with the challenge of connecting new capabilities to legacy environments without adding unnecessary complexity.
The most useful question is therefore: “Which connections will create enough value to justify their architectural and operational implications?”
Frequently asked questions
Questions about the topic often arise because Visa, Visa VAS, and Visa as a Service may sound like similar concepts. They have different meanings within this infrastructure discussion.
What is Visa as a Service?
Visa as a Service is used here as an editorial term to describe the expansion of the Visa ecosystem beyond the payment network.
The concept includes capabilities related to processing, risk, acceptance, money movement, advisory, data, and banking infrastructure.
It is not the official name of an independent Visa product. Visa VAS is the established term for Visa Value-Added Services.
What products are part of Visa’s VAS ecosystem?
The Visa value-added services ecosystem spans different capability categories rather than a single product.
These include:
- Risk and security;
- Acceptance;
- Issuer processing;
- Advisory and data;
- Money movement;
- Selected banking infrastructure capabilities.
The portfolio can evolve over time. Institutions should therefore evaluate current offerings and their fit with their own technology environments before making architecture decisions.
How can mid-market banks connect to it?
There is no single path. Connection can happen through direct integrations, APIs, processor relationships, platforms, orchestration layers, or phased modernization projects.
The most important step is to define which capabilities need to be modernized first and how they will coexist with current systems.
In environments combining different payment rails, Real-Time Payments should also be part of the architectural evaluation.
What changes from here
Visa remains one of the world's leading payment networks. Its expanding ecosystem, however, now reaches well beyond that original role.
The growth of Visa VAS, together with the company’s expansion into issuer processing, acceptance, risk, advisory, money movement, and core banking, points to a broader strategy: participating across different layers of financial infrastructure.
For mid-market banks, this can create opportunities for selective modernization.
Institutions can evaluate which components need to evolve first and where specialized infrastructure could accelerate results, allowing transformation to proceed without replacing the entire architecture at once.
Greater modularity also increases the importance of integration, orchestration, observability, resilience, and governance.
This is one of the central lessons of Visa’s ecosystem expansion. Adding services can increase an institution’s capabilities, but sustainable modernization depends on an architecture that enables those components to work together.
The next chapter is likely to broaden this discussion further as value-added services, real-time payments, stablecoins, and agentic commerce continue to evolve.
For financial institutions, the advantage will come from knowing where each innovation can create value without compromising control, security, and stability.
It is this balance between innovation and architecture that allows financial modernization initiatives to scale.
If your institution is evaluating new payment, processing, risk, or orchestration capabilities, it is worth first discussing how these technologies can connect to the existing environment.
Talk to NTConsult about financial infrastructure modernization
