Visa's 0.10% Embedded Payment Charge Starts Today: The B2B Virtual Card Bill Comes Due
TL;DR
Visa’s new Acquirer Embedded Payment charge is 0.10%, with no per-item fee, on qualifying embedded Visa commercial virtual card transactions.
It is billed to the acquirer, not directly to the paying business, but may reach merchants through pass-through pricing, revised rates or separate fees.
The charge prices the software-embedded payment model, not simply the use of a commercial card. Classification and transaction mix will determine exposure.
Mastercard’s new Transaction Link ID requirement also takes effect today, tightening the data trail for subsequent merchant-initiated transactions.
From 30 October, higher Visa Purchasing Large Ticket limits may benefit some very large commercial payments, provided the transactions meet programme and data requirements.
Visa’s charge prices how a virtual card is created, not just the card itself
Visa’s 0.10% Acquirer Embedded Payment charge applies to qualifying virtual card payments created through Visa embedded payment integrations in business software. That includes Visa Commercial Solutions virtual cards generated within ERP, accounting, procurement or accounts payable applications and used to pay suppliers.
The charge has no per-item component and is listed separately for domestic and international transactions. It is billed to the acquirer, the bank or processor on the merchant side, not to the paying business. Processor summaries describe the charge as applying to qualifying transactions processed by acquirers in the US and Canada, with the US effective date of 23 October 2026.
Visa and Mastercard distribute their full network bulletins to acquirers rather than publishing them publicly, so the details here reflect processor summaries of the October bulletins.
This is a category change, not merely a rate change. Commercial cards have traditionally been monetised through issuing-side economics, including interchange. This charge places a price on the embedded wrapper: the fact that the virtual card was created inside business software. As virtual card processing becomes part of routine accounts-payable workflows, that distribution model now has a cost on the acceptance side too.
The paying business does not receive the invoice, but the merchant may still pay
The charge is assessed to the acquirer, but acquirers usually pass network fees through to merchants. How it appears depends on the merchant’s pricing model and contract.
With interchange plus pricing, the charge may appear as a separate pass-through line at cost, using a new merchant statement descriptor such as “Acquirer Embedded Payment”. Flat-rate pricing may absorb the cost into the blended rate, showing up instead in a rate-change notice or revised terms. Tiered pricing may absorb it, add a separate fee or move transactions into a higher-cost tier.
The arithmetic is straightforward, but the pass-through treatment is not always visible. Hypothetically, a qualifying $20,000 virtual card payment at 0.10% adds $20 in network cost, on top of interchange, assessments and processor markup. That does not mean every merchant will see a $20 line item: the processor’s pricing model and contract determine how the cost is presented.
For acquirers and PayFacs, the exposure is twofold. Absorb the charge and it can compress margin; pass it through and merchants will ask what the new descriptor means. Existing contracts may not clearly address a new network fee tied to embedded payments. Providers should check fee-variation clauses and prepare a clear explanation before statements arrive.
B2B suppliers have the greatest exposure
Businesses accepting corporate virtual cards for invoices are most likely to be affected. B2B and wholesale suppliers sit at the high end of the exposure range; contractors and service firms billing businesses face moderate exposure. B2B SaaS and membership businesses may be affected when customers pay with company cards, while online marketplaces depend on their buyer mix. Consumer e-commerce and consumer subscriptions are less exposed because ordinary consumer cards and wallets are not embedded B2B virtual accounts.
The important operational question is not just, “Do we accept Visa?” It is, “What share of our Visa volume comes from qualifying commercial virtual cards generated inside business software?” Payment providers should help merchants answer that with transaction-level data, rather than infer exposure from industry labels alone.
The 0.10% rate is relatively small compared with the significance of classification. Merchants cannot choose how Visa classifies a transaction, and transactions must not be recoded to avoid the charge. Operators can control whether they understand their commercial and virtual card mix, how the processor applies fees, and whether the contractual terms allow a pass-through or markup.
The charge is also the demand-side counterpart to this week’s supply-side development: Visa and Fifth Third’s Newline making corporate card issuing across more than 40 countries available to eligible fintechs through an API-led model. The Newline announcement points to cards becoming more deeply distributed through software. The embedded payments fee shows that acceptance economics are responding to the same shift. It is context for the pricing change, not a separate reason to assume all corporate card transactions qualify.
Mastercard’s TLID rule tightens the data trail for merchant-initiated payments
From 23 October, Mastercard requires processors to send the Transaction Link ID (TLID) retained from the original cardholder-initiated transaction with all subsequent merchant-initiated transactions. The TLID is a 22-character alphanumeric identifier linking authorisation and clearing messages; network transaction IDs continue in parallel.
Processors have been required to retain TLIDs from cardholder-initiated transactions that set up future card use since 2 June 2026. Where the original cardholder-initiated transaction predates that date, the processor must send the TLID from the earliest authorised merchant-initiated transaction after 2 June.
This is a same-day data-plumbing change alongside Visa’s new charge. The two rules are distinct, but both point to closer identification of credential-based payments that are not physically initiated by a cardholder at the time of each transaction. For operators, it reinforces the need to preserve and transmit payment identifiers reliably across authorisation and clearing.
Large-ticket sellers may find an offset, but only with the right data
From 30 October, Visa raises the maximum transaction size for some Purchasing Large Ticket (PLT) programmes from $10 million to $50 million. A third listed programme remains capped at $10 million, and the Prepaid Large Ticket maximum is unchanged.
PLT programmes provide their own interchange rates for qualifying large commercial card purchases. For wholesale, industrial and distribution sellers, more transactions may fall within the available size range. But the higher ceiling does not guarantee a lower cost: eligibility requirements still apply, and the gateway or terminal must pass the commercial data fields needed for the right rate. For eligible transactions, a large-ticket rate could be worth more than the 0.10% embedded charge. Data quality determines whether the seller can realise that potential.
Other October changes include Visa adding US support and interchange programme rates for installment credential credit products; NYCE introducing new merchant interchange groups for POS PIN debit transactions effective 1 October; and Mastercard adding commercial credit and prepaid product codes to its Variable Interchange Programme, alongside Wholesale Travel codes. Moneris lists 24 October for the Wholesale Travel codes.
Operators should check contracts, statements and transaction data now
Acquirers, PayFacs and merchants should take a few practical steps before the change becomes a statement surprise:
Confirm whether the processor passes the charge through at cost, adds a markup or absorbs it.
Ask what share of last month’s Visa volume was commercial or virtual, and how much may qualify as embedded.
Check that the gateway or terminal sends the data fields needed for commercial and large-ticket rates.
Review flat-rate and tiered contracts for network-fee variation clauses.
Monitor October and November statements for a new “Acquirer Embedded Payment” descriptor or a rate-change notice.
For the largest invoices, assess whether ACH or account-to-account payment is a better fit when card economics no longer work.
The recent Visa Canada small-merchant interchange change offers a useful reminder: changes to network economics do not automatically translate into a clear change in a merchant’s total bill. Pass-through, card mix and the underlying contract matter.
FAQ: What should payment operators know about Visa’s embedded payment charge?
How do I tell whether my Visa transactions qualify for the embedded payment fee?
Check whether the virtual cards are generated through Visa embedded payment integrations inside business applications, such as ERP, procurement or accounts payable software. Ask your acquirer or processor how qualifying volume is identified and reported. Do not recode transactions to avoid the charge.
Will the 0.10% charge appear as a separate line on my merchant statement?
Not necessarily. Interchange-plus pricing may show it as a distinct pass-through item. Flat-rate pricing may reflect it in revised terms or a blended-rate change, while tiered pricing may absorb it or apply a separate fee. Ask your provider how it will appear under your specific agreement.
How should my PayFac estimate the margin impact?
Start with the share of Visa volume that is commercial or virtual, then determine which transactions meet the embedded-payment criteria. Model whether the charge will be absorbed or passed through, and confirm whether your contract permits a markup or fee change. The headline 0.10% alone is not enough to calculate portfolio impact.
Can I offset the charge with Visa’s higher PLT transaction limit?
Potentially, if you process very large qualifying commercial payments and meet the relevant PLT programme requirements. Some programme limits rise to $50 million on 30 October, but one remains at $10 million and Prepaid Large Ticket is unchanged. Confirm eligibility and data quality with your processor.
Key takeaway
Visa’s embedded payment charge is small in percentage terms, but it marks a meaningful shift: networks are beginning to price the software layer that distributes B2B virtual cards, not just the card transaction itself. For merchants, acquirers and PayFacs, the response is practical: measure qualifying volume, verify pass-through terms, protect data quality and explain new statement charges before they become a dispute.