How Do Virtual Card Payments Work for B2B?

A B2B virtual card payment is a single-use or vendor-specific card number generated on demand by an AP system, used to pay a supplier on the credit card rails (Visa, Mastercard, Amex) with built-in controls, set credit limit, set expiration date, locked to a specific vendor or invoice. The supplier processes it like any other card payment on their merchant terminal or virtual terminal. The buyer gets the payment data back in structured form for reconciliation, plus a rebate from the card network on the spend. B2B virtual cards now account for the majority of virtual card transaction volume, per Grand View Research data showing the segment at 70.3% of the market in 2024.

The mechanic isn't complicated, but the operational implications are different from consumer cards in ways that matter for finance teams.

Key Takeaways

• A B2B virtual card payment generates a card number tied to a specific vendor, invoice, or spend category, with limits and expiration set at issuance. The supplier processes it as a card transaction; the buyer reconciles via structured data and earns network rebates.

• B2B virtual cards now make up 70.3% of the virtual card market (Grand View Research, 2024), with Juniper Research projecting $14.6 trillion in B2B virtual card volume by 2029.

• The fundamental advantage over physical cards in B2B is the per-payment control — limits, expiration, vendor lock, and instant kill — which removes most of the misuse risk in traditional corporate card programs.

• The fundamental difference from ACH is that virtual cards skip the banking exchange. The supplier doesn't need to share account information, and the buyer doesn't need to maintain it. That changes the vendor adoption math meaningfully.

• The constraint isn't technology — it's supplier acceptance and processing fees. Managed enrollment and the right rebate-share economics decide whether a virtual card program pays off or sits idle.

How does a B2B virtual card payment actually work?

A B2B virtual card payment follows a four-step flow from buyer to supplier. The whole sequence takes seconds at the network level, though the AP workflow around it typically spans the approval, issuance, and reconciliation steps over a few days.

1. Issuance — the AP system or card platform generates a card number, expiration date, and CVV for a specific payment. The card carries metadata: credit limit (often set to the invoice amount), validity window, supplier name, GL coding, project or cost-center tag.

2. Presentment — the buyer transmits the card details to the supplier. Common methods: secure email with a one-time link, virtual card portal where suppliers retrieve their payment, or system-to-system file delivery for high-volume relationships.

3. Processing — the supplier processes the card on their existing merchant terminal or virtual terminal, exactly like any other card payment. Funds settle on the supplier's normal card-processing schedule (typically 1-3 business days).

4. Reconciliation — the buyer's AP system receives a structured payment file showing transaction status, amount, supplier, and metadata. The data posts back to the ERP for invoice matching and GL posting. The card network pays a rebate to the issuer that flows back to the buyer based on the program's economics.

The mechanic looks similar to a physical card transaction because it is one at the network level. The difference is upstream: the card number is generated for the specific purpose and disposed of when the payment closes, instead of being a static number that sits in someone's wallet and gets used across hundreds of transactions over years. The Corpay piece on virtual cards explained covers the technology fundamentals at the broader-pillar level.

What's different about B2B virtual cards versus consumer cards?

The core mechanic is the same, both are card numbers running on the Visa, Mastercard, or Amex networks. Three operational differences matter for finance teams.

The structured data return is the part finance teams usually underestimate. With consumer or physical commercial cards, reconciliation requires matching statement lines back to receipts or invoices, a labor-intensive month-end activity. With B2B virtual cards, the payment file ties each transaction back to the originating invoice and PO with full metadata, so reconciliation is largely automatic. That changes the unit economics of running an AP team at scale.

How do AP teams issue and control B2B virtual card payments?

AP teams issue B2B virtual cards through their AP automation platform or a dedicated virtual card platform that integrates with the ERP. The control model has three layers, program-level rules, vendor-level rules, and per-payment rules, that finance teams configure to match their policy.

• Program-level controls set the overall scope of the virtual card program: total credit line, allowed merchant categories (MCCs), country restrictions, and dual-approval thresholds. These rarely change once the program is set up.

• Vendor-level controls apply per-supplier rules: max single payment, frequency limits, category restrictions, and whether a lodge card is used (a vendor-specific recurring number) versus a single-use number per payment.

• Per-payment controls are set at issuance: exact dollar amount (often the invoice total to the cent), expiration date (typically 7-30 days from issuance), and metadata tags for GL coding and project tracking.

The combined effect is that misuse becomes nearly impossible. A fraudulent transaction outside the parameters set at issuance gets declined at the network level. A stolen number is useless after the expiration date or after the first use, depending on the configuration. The fraud profile of a well-run B2B virtual card program is dramatically lower than either physical cards or ACH. Corpay's analysis of how virtual cards and automation work together to mitigate fraud covers the controls in more depth.

The other operational benefit is GL coding accuracy. Because the metadata is set at issuance, with the invoice number, GL account, project code, and approver, the transaction posts back to the ERP with the coding already attached. AP doesn't recode at month-end. The work moves upstream into the issuance step where it's already happening anyway.

What does the supplier side look like?

From the supplier's perspective, a B2B virtual card payment looks like a normal card payment with a slightly different presentation. They receive the card details, typically via secure email, supplier portal, or a system integration, and run the card on their existing merchant terminal or payment gateway. Funds settle on their normal card-processing schedule.

The trade-off for suppliers is processing fees. Card payments cost the supplier roughly 1.5-3.5% in interchange fees, depending on the card brand, transaction size, and the supplier's merchant agreement. Compare that to ACH where the cost is essentially zero on the receiving side, or a paper check where the supplier absorbs the deposit time and the float risk. For many suppliers, the math is straightforward, they'd rather get paid in two days via card than wait two weeks for a check, even at a 2% cost. For others, particularly suppliers running on thin margins, the card fee is a real friction point.

The supplier benefits that finance teams sometimes undersell:

• Faster settlement versus ACH and especially versus check. Card payments clear in 1-3 days versus 5-10 for a mailed check.

• No banking exchange required — suppliers don't need to share their bank account information with the buyer. For smaller suppliers worried about security or fraud, this is a real concern (the Ghost in the Cloud piece on Corpay's blog covers this dynamic from the supplier's side).

• Predictable timing — virtual cards land on a specific date, unlike ACH which can drift across settlement windows.

The acceptance question is the real operational lever. Supplier acceptance rates for B2B virtual cards typically run 40-70% depending on the supplier mix and the buyer's enrollment effort. Programs with high acceptance look good on paper; programs stuck below 40% often don't pay back their setup cost.

How do you handle vendor acceptance and enrollment?

Vendor acceptance and enrollment is where most B2B virtual card programs succeed or fail. The platforms that handle enrollment as a managed service consistently outperform the platforms that hand you a portal and expect your team to recruit suppliers, because the work of converting a paper-check or ACH supplier to a virtual card payee involves real outbound effort, call, explain the program, address the fee concern, set up the receiving process, validate the first payment.

The three patterns that work:

• Managed enrollment with a dedicated team doing outbound contact, explaining the program, and converting suppliers one at a time. This is slow but produces durable adoption.

• Existing-network leverage — if the platform's broader vendor network already has your supplier enrolled, the conversion happens at signup with minimal AP effort. The bigger the platform's accepting vendor base, the faster this scales.

• Hybrid rebate-share — sharing some of the rebate economics with the supplier (often 30-50 basis points) to offset the card processing fee. This converts suppliers who'd otherwise refuse on cost grounds.

This is a deep topic and a full discussion of why vendor enrollment determines virtual card program success sits in a companion piece on the blog. For this guide, the practical point is: don't evaluate a virtual card platform on features. Evaluate it on the enrollment model and the realized acceptance rate from comparable customers.

When are B2B virtual card payments the right rail?

B2B virtual cards are the right rail in specific scenarios where their unique attributes, single-use control, rebate economics, no banking exchange, actually pay off versus the alternatives. They're not the right answer for everything.

The teams that get the most out of virtual cards run them as the default for one-off and ad-hoc spend, while keeping ACH as the default for recurring supplier relationships. A multi-rail AP platform makes this routing decision per-vendor and per-payment so AP isn't picking rails manually. The broader pattern is covered in Corpay's piece on the four most critical AP automation workflows.

Run B2B virtual card payments with Corpay

Corpay is built for the multi-rail B2B payment environment where virtual cards are one instrument among several, all orchestrated from a single AP approval. We complement your ERP rather than replacing it, so the chart of accounts, dimensions, and project structure you've already built stay in place and the AP workflow just gets cleaner.

Corpay's payments automation platform executes ACH, virtual card, check, and wire from one approval, picks the right rail per vendor based on policy, and absorbs the supplier enrollment work that usually limits virtual card adoption. Our managed service contacts suppliers, explains the program, addresses the fee question, and validates banking, so your AP team isn't making cold calls.

The economics matter. As Mastercard's #1 commercial B2B issuer with 4 million-plus accepting vendors in the network, we deliver virtual card rebate economics at a scale most platforms can't match. That changes the unit cost math on the spend that moves to cards, and it changes the conversion rate on supplier enrollment because many of your vendors are already in the network.

See B2B virtual card economics in your environment. Talk to our team about a working session built around your vendor spend mix, current rebate capture, and AP automation footprint. We'll show you where virtual cards realistically fit in your payment stack and what the math looks like with your data.

B2B virtual card payments FAQ

How is a B2B virtual card different from a corporate credit card?

A corporate credit card is a single static number issued to a person, used across hundreds of transactions over years. A B2B virtual card is a per-payment or per-vendor number generated on demand by the AP system with built-in controls, credit limit, expiration, vendor lock. Both run on the same card networks; the difference is in how they're issued and controlled.

Do suppliers actually want to accept virtual card payments?

It depends on the supplier. Larger suppliers with established card-processing systems usually accept virtual cards readily because the faster settlement compensates for the processing fee. Smaller suppliers running on thin margins may resist the fee, particularly for low-margin services or commodity materials. A rebate-share program that gives the supplier some of the network economics is the typical resolution.

What's the difference between a single-use virtual card and a lodge card?

A single-use virtual card has a new number for every transaction, you generate one, pay one invoice, and the number expires. A lodge card has a vendor-specific number that stays active for recurring payments to that supplier. Single-use cards offer maximum fraud protection but require generating numbers per payment. Lodge cards offer ease of use for recurring relationships at the cost of slightly broader exposure if the number is compromised.

How fast do B2B virtual card payments settle?

The card payment authorizes within seconds at the network level. Funds settle to the supplier on their normal card-processing schedule, typically 1-3 business days. That's faster than ACH (1-2 business days plus banking holds) and dramatically faster than a paper check (5-10 days plus float).

What kind of rebates do B2B virtual cards earn?

Rebate economics depend on the card brand, the volume tier, and the program structure. Typical net rebates run 1-2% of card spend flowing back to the buyer after the issuer's economics. On meaningful B2B spend volume that's a real number, for an AP function pushing $20 million annually through virtual cards, a 1.5% net rebate is $300,000 a year.

Can I issue B2B virtual cards from my existing ERP?

Most major ERPs don't issue virtual cards natively. An AP automation platform or dedicated virtual card platform handles the issuance and integrates with the ERP for posting and reconciliation. Look for platforms that post structured payment data back to your ERP, including the invoice match, GL coding, and project tags, so reconciliation stays automated.

Are B2B virtual cards safer than ACH?

Different risk profile. B2B virtual cards eliminate the BEC pattern that targets ACH (fraudster impersonates a vendor and requests banking changes) because there's no banking information to change, the card is generated per payment. They introduce a small risk if a virtual card number is intercepted before use, but single-use and short-expiration controls minimize that window. For most AP fraud profiles, virtual cards reduce overall exposure.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

Commercial Cards

Virtual Card

Payments Automation