OUTLINE
TLDR: Acquirers and processors can expand beyond card acceptance with embedded finance, adding money movement, ledger and treasury infrastructure around the existing card relationship. This allows merchant acquiring providers to support the full merchant financial workflow, from acceptance to reconciliation, without replacing card acceptance.
Card acceptance remains one of the most important foundations of the merchant relationship. Increasingly, however, it is only one part of what merchants and the software platforms serving them expect from a payments provider.
A merchant may accept card payments through one provider, collect from bank accounts through another, use separate infrastructure for supplier payouts, reconcile through an ERP, maintain operating balances elsewhere and introduce another provider when real-time or cross-border payments are required.
For the merchant, the result is fragmentation.
For the acquirer or processor, the strategic issue is larger. Every financial workflow that moves to another provider represents another part of the merchant relationship, operating data and potential revenue moving with it.
The opportunity is not to replace card acceptance. It is to build around it.
Software is playing an increasingly important role in how merchants choose and consume financial services.
McKinsey's 2025 Merchant Acquiring Survey found that roughly 90% of U.S. merchants use an integrated software vendor solution for payments or business management, up from 48% in 2022. McKinsey also found that the U.S. ISV channel is growing significantly faster than traditional acquiring channels as software providers expand into commerce and financial management. McKinsey & Company
For merchant acquirers, that changes what a merchant payments proposition needs to support.
The financial workflow increasingly extends across five connected stages:
Accept → Fund → Manage → Pay → Reconcile
Acceptance remains core, but merchants may also need to collect funds directly from bank accounts, fund operating balances, separate money across entities or customers, initiate supplier and beneficiary payments, support real-time payouts, and reconcile every movement back to their accounting environment.
This is where embedded financial infrastructure becomes strategically relevant.
VoPay's model is designed around exactly that expansion. The acquiring relationship remains intact while VoPay provides an infrastructure layer for payment rails, wallets, ledger capabilities, automation, reporting and reconciliation.
North America is not a single rail environment.
The United States operates across ACH, Same Day ACH, RTP, FedNow, wire and card-based infrastructure, each with different operating characteristics and use cases.
ACH alone processed 35.2 billion payments worth $93 trillion in 2025. Same Day ACH reached approximately 1.45 billion transactions worth $3.92 trillion, with volume increasing 16.7% year over year. Nacha
The move toward faster bank payments is continuing. In the first quarter of 2026, Same Day ACH volume grew another 23.6% compared with the same period in 2025. Nacha
Canada presents a different infrastructure mix.
Electronic funds transfer remains a major commercial payment method, accounting for $7.2 trillion across 3.2 billion transactions in 2024. Online transfers accounted for another $568.6 billion across 1.5 billion transactions. Payments Canada
Canada is also moving toward broader real-time payment infrastructure. Payments Canada says the Real Time Rail is scheduled to begin its phased launch in Q4 2026, introducing instant, data-rich clearing and settlement with participant onboarding continuing into 2027. Payments Canada
For an acquirer supporting merchants across North America, the challenge is therefore not simply rail access.
It is managing rail complexity without passing that complexity on to the merchant.
Connecting to multiple payment rails is useful.
Orchestrating them is more valuable.
A merchant should not need detailed knowledge of every network before initiating a transaction. The infrastructure layer should be able to evaluate the business intent and determine an appropriate path based on the characteristics of the transaction.
Those considerations can include:
• Amount
• Timing and urgency
• Cost
• Beneficiary reachability
• Rail availability
• Risk controls
VoPay's orchestration model is designed around that principle. Payment intent can be evaluated against available rails, with the architecture supporting alternate payment paths while maintaining the transaction lineage required for operational visibility and reconciliation.
That distinction matters.
Adding five individual rails can create five new integrations, five operating models and five reconciliation problems.
A payment orchestration layer provides a common control plane above them.
Large acquirers and processors rarely operate in greenfield environments.
They already have merchant portals, underwriting systems, CRM platforms, settlement infrastructure, bank relationships and software partners.
New infrastructure therefore needs to work with what already exists.
VoPay supports multiple integration approaches, including APIs, host-to-host connectivity, file ingestion, SFTP, webhooks and embedded connectors. The platform layer can then connect payment rails, automation, ledgers, treasury rules, compliance processes and reporting into the wider financial ecosystem.
The objective is not a rip-and-replace strategy. It is to activate additional capabilities around the existing acquiring environment.
Payment execution is only one part of the merchant problem.
Consider a marketplace, franchise network, software platform or multi-entity enterprise.
It may need to answer questions such as:
These are ledger and treasury questions, not simply payment rail questions.
VoPay's modular infrastructure combines collection capabilities with sub-accounts and wallet structures, orchestration rules, approvals, sweeps, payouts, ERP connectivity, journals and audit trails. Compliance, onboarding, risk controls and reporting operate across those functions.
This allows the acquirer to move from facilitating individual transactions toward supporting a broader financial operating workflow.
The distinction becomes even more important when an acquirer supports an ecosystem rather than a single merchant.
A large processor may need to support direct merchants, ISVs, regional programs, marketplaces and underlying sub-merchants at the same time.
Operating that environment requires control above the individual account.
VoPay's partner model provides partner-level credentials that can sit above merchant, ISV and sub-partner structures. From that layer, partners can provision accounts, embed onboarding within their own experience, support permitted cross-account transfers and sweeps, configure billing structures and access program-level reporting.
The question changes from:
"How do we offer another payment type?"
to:
"How do we operate and monetize a broader financial services program across the merchant portfolio?"
That is a very different product conversation.
The strategic value comes down to six areas.
Adding adjacent financial capabilities allows the acquirer to solve more merchant needs within the existing relationship rather than directing the merchant toward additional financial providers.
A2A payments, payouts, treasury workflows, account structures and embedded financial services create opportunities to expand the commercial relationship beyond card processing alone.
As more merchant relationships become software-led, acquirers need infrastructure that can sit inside an ISV's application and support embedded onboarding, payments, money movement and reporting.
Building and maintaining individual connections to payment rails, banking partners, onboarding workflows, ledger infrastructure and reconciliation systems requires significant investment.
Using a common infrastructure layer allows product teams to focus on the merchant proposition instead of rebuilding underlying payment components.
The more closely a provider is connected to the merchant's funding, payouts, accounts, treasury and reconciliation workflows, the more difficult that relationship becomes to reduce to a commodity processing decision.
Payments generate financial events. Treasury infrastructure connects those events to balances, account structures, controls and systems of record.
VoPay's Beyond Card Acceptance proposition brings these capabilities together around the existing acquiring relationship.
The acquiring market is evolving from transaction processing toward broader merchant enablement.
That does not mean every acquirer needs to become every financial provider.
It means identifying the financial workflows that naturally sit beside card acceptance and determining where those capabilities can add value to the merchant, the ISV and the acquiring relationship.
Cards remain central.
But the merchant's financial workflow continues long after authorization and settlement.
Funding, balances, payouts, treasury, reporting and reconciliation are increasingly part of the same conversation.
For acquirers and processors, expanding into those workflows creates an opportunity to protect the relationship they already own while making that relationship substantially more valuable.
VoPay is a leading Fintech-as-a-Service platform built for enterprise acquirers and processors that want to embed payments and financial services directly into their core products, without the burden of building or maintaining complex infrastructure. VoPay delivers robust, compliant, fully white-labelled payment capabilities through a single API, so your acquiring relationships get stronger, not disrupted.
Explore VoPay for Acquirers and Processors
It means keeping card acceptance as the foundation while adding the financial workflows that sit beside it: collecting funds from bank accounts, funding operating balances, separating money across entities or customers, initiating supplier and beneficiary payments, supporting real-time payouts and reconciling every movement back to the accounting environment. These capabilities are made available through the relationship the acquirer already owns.
For merchant acquirers, embedded finance is an infrastructure layer for payment rails, wallets, ledger capabilities, automation, reporting and reconciliation that operates inside the existing acquiring relationship. The acquirer keeps the merchant relationship while adding these capabilities without building or maintaining the infrastructure itself.
Payment orchestration evaluates the intended outcome of a payment against available rails, based on considerations such as amount, timing and urgency, cost, beneficiary reachability, rail availability and risk controls. A payment orchestration layer provides a common control plane above multiple payment rails, instead of separate integrations, operating models and reconciliation processes for each rail.
In the United States, the key rails are ACH, Same Day ACH, RTP, FedNow and wire. In Canada, they are EFT, Interac e-Transfer® for Business and the forthcoming Real Time Rail, which will add instant account-to-account infrastructure.
Platforms, marketplaces, franchises and multi-entity merchants need to know who owns the funds, what is available, what belongs to an underlying merchant or customer, what is pending, where money should move next and how each movement reconciles back to the accounting system. Ledger and treasury capabilities answer those questions as the acquirer expands beyond acceptance.
No. The objective is to activate additional capabilities around the existing acquiring environment. VoPay supports multiple integration approaches, including APIs, host-to-host connectivity, file ingestion, SFTP, webhooks and embedded connectors.
