Skip to content

FinTech and the office of the CFO

Subscribe

Who pays when your AP software issues the card

Explore payment liability, card issuance responsibilities, and financial risks when AP software issues business payment cards.

Who pays when your AP software issues the card

Since 23 October Visa has charged acquirers 0.10% on virtual card payments it classifies as embedded, the single-use cards that payables software creates to settle an invoice. The fee is small. What it prices, and who ends up paying it, matters more to the platforms that issue these cards and the finance teams on both ends of them.


A card network fee rarely earns an article. This one is worth reading closely because of what it is attached to. From 23 October, according to fee summaries published by several US payment processors, Visa bills acquirers a new Acquirer Embedded Payment Charge of 0.10%, with no per-item component, on qualifying transactions in the US. The summaries say it also applies in Canada, without giving a Canadian date. Visa's bulletins to acquirers are not public, so every account so far is second-hand.

What qualifies is the interesting part. The charge applies to transactions on virtual accounts provisioned through Visa's embedded payments integrations inside business applications used for B2B payments. In practice, that means the card number an accounts payable or procurement platform generates when a bill falls due, used once, and never seen by anyone in the buyer's finance team. The fee does not attach to a type of card or a type of merchant. It attaches to the route by which the card came into existence.

A price on the channel, not the card

Networks have long priced by product: consumer against commercial, card present against card not present, large ticket against small. Pricing by provisioning channel is a different idea. It tells the market that Visa can see which commercial cards were born inside a software platform, and that it regards that traffic as a distinct line of business with its own economics.

Visa has said as much in its own marketing. A June 2026 piece from Visa Commercial Solutions described embedded payments as "a revenue stream hiding in plain sight" for software platforms, and set out the model plainly: a platform issues virtual cards to smaller buyers and "operates under a revenue share agreement on interchange with a BIN-sponsor issuer." The buyer gets paid early, or rebated. The platform takes a share of interchange. The supplier, who accepts the card, pays for both.

The new charge adds a further line to that last column. Because it is billed to the acquirer, the processor sitting on the supplier's side of the transaction, it reaches the business that receives the payment, not the one that sends it. MannyPay, a merchant-services publisher, expects merchants on interchange-plus pricing to see it as its own pass-through line and those on flat-rate pricing to find it folded into a blended rate. Some processors, it says, may not pass it on until November.

Why ten basis points is not the point

Set against what a supplier already pays, 0.10% is modest. One B2B programme Visa added on 1 October, for Commercial Choice Travel, carries an interchange rate of 2.00%, according to Wind River Payments' summary of the October changes. On a $1m year of virtual card receipts, the new charge is $1,000 next to interchange that can run to twenty times that. Nobody will stop accepting cards over it.

The signal sits elsewhere. Visa's chief financial officer, Chris Suh, told analysts on 27 October that service revenue grew 14% in the fourth quarter "primarily due to pricing", and that pricing benefits in fiscal 2027 should be "similar in magnitude and timing" to 2026. Chief executive Ryan McInerney said commercial payments volume rose 12% for the year and named B2B as an area Visa expects to adopt agentic payments quickly, citing Ramp's agentic bill pay, now generally available, and BILL's payment agent, which is piloting Visa Intelligent Commerce to pay invoices. Neither executive mentioned the embedded charge. Read together, though, the call and the fee describe a network that sees software-initiated B2B payments growing and has now built a way to price them separately.

Mastercard is building the same channel. On 23 July it said its embedded virtual card programme, launched in March 2025, had "dozens of partners" across expense management, ERP, accounts payable and travel, with SAP a recent addition. None of the processor summaries this publication read lists an equivalent Mastercard charge. That could change in any network release cycle.

Figure 1

Party

What changed on 23 October

Where it shows up

The open question

Supplier receiving an embedded virtual card

A 0.10% network charge on qualifying receipts, billed to its acquirer

A separate pass-through line on interchange-plus statements; inside the blended rate on flat-rate pricing

Can it identify which receipts were tagged as embedded, and is anything above 0.10% being added in Visa's name?

Acquirer or processor

Billed directly by Visa

Network fee schedules from October onward

Pass-through at cost, marked up, or absorbed, and from which month

AP or procurement platform

Nothing billed to it under this charge, per the summaries read

Supplier enablement conversations and opt-out rates

Whether more suppliers decline cards, which shrinks the interchange it shares

Buyer's finance team

Nothing billed to it under this charge, per the summaries read

Rebate income that depends on supplier card acceptance

How much of its payables programme rests on suppliers who could switch to ACH

One fee, four ledgers. Fee mechanics from processor summaries by Wind River Payments (13 October 2026), Yan Payments (12 October 2026) and MannyPay (20 October 2026), which draw on Visa's acquirer bulletin; Visa has not published the charge. The open-question column is FinancyHub's assessment.

What it means for the platforms

For a founder or product lead running a payables product, the charge does not touch the platform's own invoice. It touches the supplier, and the supplier is the weakest link in the model already. Every virtual card programme depends on persuading vendors to accept a payment method that costs them money when a bank transfer would cost them very little. Supplier enablement teams exist because that persuasion is hard. A line on a supplier's statement that names the embedded channel gives a reluctant vendor's finance team a specific reason to ask for ACH instead.

The likelier near-term effect is on the arithmetic inside the platform, not on supplier behaviour at scale. Interchange share is often the largest revenue line in an embedded card programme. If acceptance slips by even a few points among large suppliers, the revenue share slips with it. Platforms that report card penetration of supplier spend to their boards or investors should expect the question.

What it means for the finance team

Most companies sit on both sides of this. Their AP team may run a virtual card programme for the rebate. Their AR team may receive virtual cards from customers' platforms. The charge lands on the second team, and the two rarely compare notes.

On the receiving side, the first job is visibility. A supplier cannot tell from the card number whether a payment was provisioned through an embedded integration; MannyPay notes that the classification comes from how the card was issued. The statement is where it appears, so the controller needs effective-rate reporting broken out by card type, compared before and after 23 October. Yan Payments, a processor, warns that intermediaries may add their own margin under the label of Visa's fee. Anything meaningfully above 0.10% on that category deserves a question.

On the paying side, the question is concentration. A rebate forecast built on suppliers who accept cards reluctantly is more fragile than it looks on the treasury dashboard.

Five checks for the CFO office before the November statements arrive

  1. Ask your acquirer whether the Acquirer Embedded Payment Charge is passed through at cost, and from which statement month.

  2. Break out virtual card receipts by card type and compare the effective rate for October and November with the three months before.

  3. List the customers who pay you through AP platforms and the share of receipts each represents.

  4. On the payables side, rank your rebate income by supplier and mark the suppliers most likely to ask for ACH.

  5. Ask your payables platform whether it expects any change in supplier acceptance, and what it will tell suppliers who raise the charge.

The same week the charge took effect, Visa told investors that software agents are starting to pay invoices on its network. Every one of those payments will begin as a card created inside an application, which is precisely the traffic Visa has now learned to tag. Ten basis points is the opening price on that tag, and the supplier is the one paying it.


Sources and notes. Fee mechanics, effective date and the B2B Program ID A7 rate from Wind River Payments, "October 2026 Interchange and Network Fee Updates" (Stephanie O'Connor, 13 October 2026); Yan Payments, "Visa's new 0.10% embedded payments fee on B2B virtual cards" (12 October 2026); MannyPay, "Visa Acquirer Embedded Payment Charge" (Adrian Reyes, 20 October 2026). Each relies on Visa's acquirer bulletin or on Merchant Cost Consulting's summary of it; Visa has not published the charge and FinancyHub has not seen the bulletin. Visa Commercial Solutions, "Embedded Payments as a Revenue Engine" (Prasanna Vanguri, 11 June 2026). Visa fiscal fourth-quarter 2026 earnings call, 27 October 2026, transcript via The Motley Fool. Mastercard press release, "Mastercard expands virtual card platform", 23 July 2026. FinancyHub has no commercial relationship with any firm named. Journalism, not legal, compliance or procurement advice. Corrections welcome.

The briefing

Keep reading the stack.

One email a week on financial technology and the finance stack.