How to Choose a Virtual Card Provider for Your Business

Choosing a virtual card provider means looking past the card itself. Evaluate how well the provider integrates with your ERP, how it enables your suppliers, how transparent the rebate model is, what fraud controls come standard, and what support looks like after go-live. The best provider for your business is the one that fits your AP workflow and delivers net rebate after real-world supplier behavior, not the one with the flashiest sales deck.

That framing matters because virtual cards are no longer a niche payment method. Juniper Research estimates the B2B sector makes up 76% of the $5.2 trillion global virtual cards market in 2025, and projects transaction value will grow 235% by 2029 — making virtual cards the fastest-growing B2B payment channel over the next five years. The providers pitching you have a lot of revenue to chase, which is exactly why buyer discipline has to go up.

Key Takeaways

• The card is commodity. The program around it — enablement, integration, controls, support — decides whether you net rebate or chase angry vendors.

• Headline rebate rates are marketing. What matters is effective rate after supplier acceptance, which most sales decks don't model honestly.

• ERP integration depth belongs in your gate questions. If the provider can't explain exactly how transactions post and reconcile in your ERP, skip it.

• Supplier enablement is the single biggest predictor of program success. Managed enablement beats self-service at any real scale.

• Red flags: opaque fees, no named support contact, no references at your volume, and rebate tiers that require spend you'd never actually hit.

What Does a Virtual Card Provider Actually Do?

A virtual card provider issues single-use or multi-use card numbers that your AP team uses to pay suppliers, and it runs the program around those numbers. The card itself is the thin end of what you're buying. The thick end is everything else: how the card integrates with your ERP, how suppliers get enrolled to accept it, how fraud and spend controls work, how reporting flows back, how reconciliation closes the loop, and who picks up the phone when something breaks.

That's why comparing providers purely on card features misses the point. Card networks set most of the mechanics. What varies between providers is operational — the enablement program, the ERP connectors, the people assigned to your account, and the fine print on rebate tiers. For the underlying mechanics before you dive into provider selection, our guide to virtual cards and how they work covers the basics.

Why does provider choice matter more than the card itself?

Because the program either generates rebate and reduces risk, or it creates vendor conflict and reconciliation headaches. A controller on r/Accounting described a client whose provider forced a major vendor — more than 40% of their AP — to accept cards they didn't want. The vendor eventually cut off supply. The CFO almost lost the job. The card worked fine. The program around it did not.

This is the failure mode buyers underestimate. You're not picking a payment tool. You're picking an operating partner who will touch your supplier relationships every week. The wrong partner can make AP worse, not better.

What Should You Evaluate First: the Card or the AP Fit?

Start with AP fit. If the provider can't slot into your existing workflow cleanly, nothing else about the card matters. The ERP integration, the approval routing, the reconciliation loop — those either work on day one or they turn your AP team into integration project managers for six months.

A useful gate question: "Walk me through how a $4,000 invoice paid on virtual card shows up in my ERP and closes out." If the demo skips the ERP side or hand-waves reconciliation, that's data. Real providers at enterprise scale answer this in concrete steps. Newer providers tend to describe it aspirationally.

Where do most evaluations go wrong?

Most evaluations fixate on rebate percentage and fraud reduction — both real benefits, but both downstream of whether the program actually runs in your environment. Buyers anchor on the top-line number ("up to 200 basis points!") and skip the operational depth. Six months later they discover the rebate depends on spend tiers they'll never hit, and the ERP integration requires a middleware license nobody mentioned.

A better sequence: AP fit first, controls and security second, rebate economics third. If the first two fail, the rebate math doesn't save you.

How Does the Provider Fit Into Your Existing AP Workflow?

The provider has to support the payment stack you already run. That means native or certified connectors to your ERP, a clean path from invoice approval to card issuance, and automated reconciliation that doesn't require your AP clerks to match transactions by hand. Anything less is a project, not a product.

Ardent Partners' 2024 State of ePayables report found that leading digital payment forms — ACH, wire, commercial cards, and virtual cards — collectively make up more than 68% of payments at the average enterprise (Ardent Partners, The State of ePayables 2024). At that share, virtual cards aren't a side program anymore. They need the same integration rigor as your core payment rails.

Which ERP integrations are non-negotiable?

The integrations that match your ERP — NetSuite, Sage Intacct, Microsoft Dynamics 365 Business Central, Acumatica, or whatever else you run. Ask specifically: is the connector native, certified by the ERP vendor, or file-based? Native and certified connectors handle two-way sync and usually support automated reconciliation. File-based integrations move data, but they typically require someone to import transactions manually or write a recurring script.

If you're on NetSuite or Sage Intacct, ask whether the connector supports auto-coding by MCC, cost-center mapping, and GL-level posting back to your chart of accounts. The same rigor that applies when you evaluate AP automation software applies here. You're buying a data pipeline, not just a card.

Does the provider support automated reconciliation?

Automated reconciliation means the provider's platform pushes enriched transaction data — merchant, MCC, card used, invoice match, tax — into your ERP so your team doesn't re-key anything. The alternative is export-to-CSV, manual import, and a rolling reconciliation backlog.

Ask to see a live reconciliation report from a customer at your size, not a sandbox demo. The difference between a polished demo and a live program is where real programs break.

What Controls and Security Features Separate the Serious Providers?

Single-use card numbers, MCC and amount locks, approval workflows, and multi-factor authentication on the admin portal. Those are the baseline. Providers that can't demonstrate all four shouldn't be on your shortlist.

The AFP 2025 Payments Fraud and Control Survey found that 79% of organizations experienced attempted or actual payment fraud in 2024, with checks still accounting for 63% of fraud incidents and virtual cards sitting at just 5%. That 12-to-1 gap is the clearest argument for virtual cards, but only if the controls actually work the way the provider describes.

How do single-use numbers limit fraud exposure?

Each payment gets a unique card number tied to a specific vendor and amount. If the number leaks, it's already expired. That's why single-use virtual cards show up so rarely in fraud data — there's no static account number for an attacker to reuse. If you want to go deeper on the mechanics, single-use virtual cards walk through exactly how they mitigate the business email compromise patterns that drive most AP fraud today.

Business email compromise still accounts for most fraud attempts, and the AFP data shows BEC targeting of wire transfers jumped sharply year over year. Virtual card controls don't stop BEC by themselves — but they take the payment method most exposed to it off the table for that transaction.

What approval and spend controls should be standard?

Per-card spend caps, MCC locks (so a card issued for a software subscription can't be used at a gas station), expiration controls, and approval workflows tied to your AP system. Better providers also offer real-time alerts and the ability to deactivate a card mid-flight without calling support.

Ask how approval logic flows — does it use your ERP's existing approval chains, or does the provider impose its own? Dual approval chains are a common failure point; teams either bypass one or the other within a quarter.

How Do You Pressure-Test the Rebate Math?

Ignore the headline rate. Calculate the effective rate by running actual AP data against the provider's tier schedule and their published supplier acceptance rates. Most of the time, the number drops 30-50% from the marketing figure.

In typical corporate programs, providers rebate roughly 100-150 basis points of the 200-240 basis points of interchange back to the buyer, keeping the rest (MerchantCostConsulting, B2B Virtual Card Processing, 2025). That's a fair baseline. Programs that promise much more are either padding a tier you'll never reach, or they're using short-term introductory rates that reset.

Why do headline rebate rates mislead most buyers?

Because they assume 100% supplier acceptance and peak-tier volume. Neither is realistic. PYMNTS research shows 94% of finance teams are aware of virtual cards, yet 71% still pay their suppliers primarily by check — often because the supplier refuses to accept the card. If even half your AP volume can't move to card, the headline rate cuts in half. Tier requirements multiply the gap.

One authored moment from a controller perspective: ask the provider to run your last 12 months of AP against their tier schedule and their acceptance model for your vendor mix. If they can't produce a net rebate number at the end, they haven't done the math — they're just quoting rates.

What effective rate should you actually calculate?

Effective rate = (total rebate dollars earned) ÷ (total AP spend eligible for card)

Model it three ways: with 100% of card-eligible spend captured, with 50% captured, and with 25% captured. The real answer usually sits between the 25% and 50% cases in year one, improving if enablement is good.

Mastercard's 2022 RPMG Virtual Card Benchmark Survey found that 83% of companies said virtual cards improved their working-capital position — the float and DPO benefits are real. But working capital is separate from rebate math. Don't let the provider conflate the two in a single ROI slide.

How Strong Is the Provider's Supplier Enablement Program?

Supplier enablement is the operational work of getting your suppliers to accept card payments — outreach, negotiation, onboarding, dispute handling, and ongoing enrollment. It's unglamorous and time-consuming, and it's where virtual card programs succeed or fail. If the provider doesn't run a real managed enablement program, you're going to do that work yourself.

This is the single biggest predictor of whether rebate math plays out as modeled. A program with a named enablement team and a documented outreach process will get 40-60% of AP spend on card within 18-24 months. A program that hands you email templates and wishes you luck will get to 15-20% and stall.

What happens when enablement is left to you?

Your AP team becomes a vendor-management operation on top of its day job. They explain the card benefit, field pushback about interchange pass-through, handle exception cases, and re-enroll suppliers whose contacts change. It's real work. Most mid-market AP teams don't have the bandwidth, and the program plateaus at low-card-spend share.

The Reddit thread where the CFO nearly got fired is the extreme version of this failure. A more common version: the program launches, hits 15% card share, and sits there while the promised rebate never materializes.

What does a managed enablement program look like?

A named enablement team that owns supplier outreach end-to-end. Metrics: how many suppliers contacted per month, acceptance rate by vendor segment, time-to-first-payment for new enrollees, and re-enrollment cadence. Ask to see those numbers from two reference customers at your spend level.

Also ask how the provider handles supplier objections — especially the "we don't accept cards because of the fee" response. Strong enablement programs have pre-built economic arguments for suppliers (faster payment, reduced DSO, no lockbox fees) and will negotiate acceptance terms where it makes sense.

What Does Implementation and Ongoing Support Look Like?

Implementation means getting the ERP integration connected, initial supplier enablement running, and your team trained. Ongoing support means named contacts, documented SLAs, and someone who picks up when a payment fails on a Friday afternoon. Both should be specific and committed in writing.

If the provider won't put an implementation timeline in the contract, that's a signal. Enterprise-grade providers commit to 60-120 day implementation windows with defined milestones. Self-service providers won't commit at all — which is fine for a small pilot and a problem at scale.

How long should implementation take?

For mid-market and enterprise AP, plan for 60-120 days from signed contract to first card payment running through your ERP. Anything under 60 days is usually a pared-down scope that leaves integration work for later. Anything over 120 days means the provider is customizing heavily, which becomes a recurring risk every time they update their platform.

Implementation should include ERP connector setup and testing, initial supplier enablement wave, approval workflow configuration, and training for at least your AP lead, controller, and a power user. Missing any of these is a flag.

Who answers the phone when something breaks?

A named account contact with a documented escalation path. Not a ticketing portal. Not an offshore support line. When a batch payment fails on month-end close, you need a human who knows your account. Ask for the contact in writing and confirm it in the reference call.

This sits alongside the broader support story — for comparison, the questions in our AP automation RFP guide covers the support commitments you should also get from your AP platform. Virtual card support should be at the same level or better.

Which Red Flags Should Stop You From Signing?

Five flags that should stop a deal in evaluation:

• Opaque fees. Monthly minimums, inactivity fees, FX fees, or rebate clawbacks buried in the MSA. If you can't get a one-page net-economics summary, assume the math favors the provider.

• No named support. "You'll have access to our support team" is not a support model. Ask for a named account contact and documented SLAs.

• No customer references at your volume. Any provider can find a reference. The question is whether they have three running programs at your AP volume and ERP stack. If they don't, you'll be the pilot.

• Rebate tiers set unrealistically high. If the top tier is built around a card spend far beyond what your AP-eligible volume can support, the real rate you'll earn is tier two or three. The tier is a distraction.

• Vague supplier enablement commitments. "We'll help your team reach out" is not enablement. Demand specific metrics, named enablement staff, and reference accounts at your vendor mix.

• Any one of these can be addressed in negotiation. Two or more usually means the provider's operating model doesn't match what they're selling.

How Does Provider Scale Change What You Should Look For?

Scale matters on two axes: the provider's issuer scale and the size of their accepting-vendor network. Both affect whether your program performs.

Issuer scale matters because larger issuers have better fraud models, more data to negotiate interchange, and established ERP partnerships. Smaller issuers can be nimble and good for specific use cases — expense management, employee spend — but they tend to struggle with mid-market and enterprise AP depth. If your AP volume is above nine figures annually, weight issuer scale heavily.

Accepting-vendor network matters because suppliers already enrolled with a given provider sign up faster. A meaningful share of overlap with your existing vendor list can shorten your enablement runway by months. Ask the provider for that overlap analysis before signing.

Run a Virtual Card Program Built for AP Scale with Corpay

If your evaluation surfaces the pattern this article warns about — strong card features, weak operational depth — Corpay's virtual card program is built for the other side of that gap. As Mastercard's #1 commercial B2B issuer, Corpay runs virtual card programs at the scale where enablement, ERP integration, and support either hold up or fall apart. Roughly 800,000 businesses rely on Corpay across the full commercial card and AP automation footprint.

The specific program elements that map to this evaluation framework:

• ERP fit: 180+ ERP integrations, including native connectors for NetSuite, Sage Intacct, Microsoft Dynamics 365 Business Central, and Acumatica. Automated reconciliation and enriched transaction data post directly to your GL.

• Supplier enablement: a managed program with a 4M+ accepting-vendor network, so a significant share of your supplier base is often already enrolled. Outreach, onboarding, and dispute handling are run by Corpay, not your AP team.

• Fraud controls: single-use virtual cards with MCC locks, amount limits, MFA-protected portals, and real-time transaction monitoring — the controls that keep virtual-card fraud rates far below checks in AFP's survey data.

• Rebate transparency: tier schedules and effective-rate modeling shared before you sign, not after.

• Support: named account management with documented escalation paths, not a shared queue.

Corpay complements the ERP you already run. It doesn't replace it. Learn how Corpay virtual cards fit into an AP program that already works or book a session to model rebate economics against your actual AP data.

Frequently Asked Questions

These are the questions that come up most often in virtual card provider evaluations, especially from finance leaders who've already been through one vendor selection and want to avoid the same pitfalls the second time around. Answers assume a mid-market or enterprise AP context; smaller programs may find the thresholds lighter.

What's the most important thing to look for in a virtual card provider?

Supplier enablement depth. More programs fail on enablement than on any other factor. A provider that runs a managed enablement program with named staff, documented metrics, and reference customers at your vendor mix will outperform a provider with better card features but self-service enablement. Ask specifically: how many suppliers does your enablement team contact per month, what's the acceptance rate by vendor segment, and can I talk to a customer my size about their 18-month adoption curve?

How do I know if a virtual card program will generate real rebate?

Ask the provider to model your last 12 months of AP against their tier schedule and their realistic acceptance assumptions — not 100% acceptance. Run the math at 25%, 50%, and 75% card-eligible spend capture. The year-one answer usually sits between the 25% and 50% case. If the provider won't produce that number, they haven't done the analysis and you shouldn't sign until they do.

Do virtual card providers integrate with NetSuite, Sage Intacct, and Microsoft Dynamics?

The major providers do, but depth varies. Ask whether the integration is native, ERP-vendor certified, or file-based. Native and certified connectors usually support two-way sync, automated reconciliation, and approval-chain integration. File-based connectors move data but often require manual steps. For AP at any real volume, native or certified is the gate.

Can any business use a virtual card provider, or is there a minimum spend?

Most enterprise-grade providers have implicit or explicit minimums — often $5M-$10M in annual card-eligible AP spend to make the managed service economics work. Smaller businesses can still use virtual cards through simpler self-service programs, but the rebate rates and enablement depth will be lighter. Match provider scale to your AP volume; a provider built for $100M+ programs will over-serve a $2M buyer, and vice versa.

How long does it take to implement a virtual card program?

Plan for 60-120 days from contract signing to first card payment running through your ERP. That window includes ERP integration setup and testing, initial supplier enablement wave, approval workflow configuration, and team training. Anything faster usually means reduced scope; anything slower means heavier customization, which tends to create recurring risk.

What's the difference between a virtual card issuer and a virtual card provider?

An issuer is the financial institution that actually issues the card numbers and underwrites the program. A provider is the company you contract with — which may be the issuer, or may be a platform that sits on top of an issuer. Most mid-market and enterprise buyers work with integrated issuer-providers (like Corpay), because a single accountable party simplifies support and integration. Pure platform providers riding someone else's issuing bank can work, but you should understand the dependency before signing.

Do I need a separate virtual card provider if I already have a corporate card program?

Not necessarily. Many corporate card programs include virtual card issuance as a feature, especially if your corporate card provider runs a full commercial card program. If you already have a corporate card relationship and the same provider offers a virtual card program with proper enablement and ERP integration, consolidating usually makes sense. Running two providers adds integration overhead and splits your rebate volume. For the differences between card types and when each one fits, see virtual cards versus physical cards.

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.

Virtual Card