Accepting Virtual Card Payments: A Vendor's Case for Faster Funds

A customer just sent you a payment instruction asking you to accept a virtual card. The remittance email lists a 16-digit card number, an expiration date, a CVV, and an invoice number. You're sitting on a 45-day-old receivable from that same customer, and the message says the card will fund within two business days if you run the charge. Accepting virtual card payments is a real decision with real economics, and most coverage was built for the buyer's AP team trying to enroll you, not for you trying to decide.

The honest version of the answer depends on what you'd otherwise pay to carry that receivable, what your processor actually costs you on this transaction, and how much that 45 days of float is worth to you. The headline percent line on the spreadsheet matters less than most vendors think once you put the rest of the picture next to it.

Key Takeaways

• Accepting a virtual card payment looks like any other card transaction on the vendor side. The buyer's card account funds it, your processor settles to your bank the same day or next, and you receive a clean per-invoice transaction record.

• The vendor's true cost is the processing fee minus any rebate-share, not the headline interchange rate. Some buyer programs share basis points of rebate back to the vendor to soften the fee.

• The faster-funds side of the math is what gets undersold. A check that would otherwise sit in the mail for weeks turns into hours; the buyer often pays net-10 on a card instead of net-30.

• Virtual cards remove the banking-data sharing required for ACH. You never give the buyer your routing and account number, and the card number itself is useless once the single transaction clears.

• Run your actual numbers against your real alternatives, not against "free." A short-term factor at monthly compounding is more expensive than a single B2B card transaction.

What does accepting virtual card payments actually mean for a vendor?

Accepting a virtual card payment means running a card charge through the merchant processor you already have, against a card number the buyer's card program issued to pay one specific invoice. The mechanics are identical to any card-not-present transaction you'd take from a consumer over the phone. You key the number into your processor's virtual terminal, or you push it through an API, and the funds settle to your bank on the processor's normal timeline. The card number lives inside the buyer's card program; their card account funds the payment, and they reconcile it later against their own card statement.

That's the part that confuses vendors the first time. It's not a new payment rail. The invoice doesn't go through any special "virtual card network" you have to enroll in. It's just a card payment that happens to be digital-only, single-use, and tied tightly to one invoice. Your merchant processor already supports it. Your bank already settles it. The only thing that changes from a process standpoint is where the card number came from and what your customer expects in return.

The reason buyers like the format is straightforward. The card number is generated on demand, capped at the exact invoice amount, often locked to your merchant ID, and dies after the single transaction clears. They can't accidentally double-pay, the number can't be stolen and reused, and the remittance data ties cleanly to the invoice. That data hygiene gives the buyer's AP team a clean reconciliation. It also gives you a clean record on the AR side. The buyer-side guide to vendor enrollment covers how program managers approach this conversation from their seat. This article is the vendor-side version.

How is accepting a virtual card different from accepting ACH?

The biggest difference is what you hand over to get paid. ACH requires sharing your routing number and account number with the buyer's AP system, which then originates the credit through the bank. Once that data is in the buyer's system, it stays there for the life of the relationship, and any compromise of their AP system carries it forward. A virtual card payment requires nothing of yours. The buyer initiates the card payment using their own card account, and the card number is theirs to manage and dispose of.

The cost shape is different too. ACH on the receiving side is typically very cheap, often pennies per transaction or free at most banks. Funds arrive in one to three business days, with some same-day options for credits originated early enough in the day. A virtual card payment runs at standard card-acceptance rates of 1.5% to 3.5% in most B2B contexts, and settles to your bank on the same timeline as any other card payment, which for most processors is next-day funding. ACH is cheaper per transaction; virtual card is faster and shares less of your data. The right answer depends on what you're solving for.

What does the receiving process actually look like end to end?

The end-to-end process from your seat goes like this: an invoice is sent to the customer, the customer's AP team approves it and queues it for payment, and the buyer's card program issues a single-use virtual card number against that specific invoice. You receive a remittance email with the card number, the expiration date, the CVV, and the invoice number to apply it against. You key the card into your virtual terminal or push it through an integrated payment portal, and the charge runs against the buyer's card account. The funds land in your merchant account within the processor's normal authorization-to-settlement window, typically same-day authorization and next-day settlement to your bank.

The whole thing reads to your AR team like any other card payment. The transaction line on your processor's reporting will show a Mastercard or Visa transaction depending on the network the buyer's card program runs on, not a special vendor designation. The remittance email is the only thing that looks different from a B2C charge; it includes the invoice reference, the amount, the issuing bank, and sometimes a contact email if there's a dispute later. Most vendors process the first one or two virtual card payments cautiously and then settle into a routine that takes less time per payment than running a check deposit or chasing an aging ACH credit.

What's the real cost to accept a virtual card payment?

The real cost is your processor's effective rate on the transaction minus any rebate-share the buyer's program offers back, net of the savings on the alternatives you'd otherwise carry. The headline range is what shows up on your merchant statement, and that varies by card type (corporate cards run higher), processor, and your acceptance volume. The number that actually matters is what falls to your bottom line after you net out the offsets: the receivable carry you no longer pay, the collection and reconciliation effort you no longer do, the rebate-share you may negotiate, and the fraud risk you no longer carry from holding a paper check or an ACH credential.

A worked comparison helps. The table below is from the vendor's side of the relationship, not the buyer's. The numbers are typical ranges. Your processor and your specific deal terms will move them. The goal is to show the shape of the trade-off.

Ranges from industry processor pricing and Federal Reserve, 2024, Federal Reserve Payments Study (check volume and timing). Vendor cost ranges are typical for B2B card acceptance.

The factoring row is the one that catches a lot of vendors mid-decision. The classic objection to virtual cards (the headline percent of the invoice) gets compared to the wrong baseline if you're also paying a factor to advance the same invoice at monthly compounding. A two-month factor at typical rates ends up costing several percent of the invoice all-in, paid whether the customer eventually pays in 45 days or 75. A virtual card that settles in two days at a typical B2B rate is cheaper than the factor and the same speed. The honest comparison is "virtual card vs my best alternative," not "virtual card vs free."

What's the interchange fee really paying for?

The interchange fee is what the card networks charge to move money, authorize the transaction, guarantee settlement, and underwrite the consumer-protection apparatus that comes with card payments. It pays for the network rails, the issuing bank's funding cost, the risk capital that backstops chargeback reversals, and the rewards and rebates earned on the buyer side. Most of it goes back through the network to the issuing bank, which is why interchange varies by card type. Corporate cards have higher interchange than consumer debit cards because the issuing bank takes more risk and shares more rebate with the cardholder. The processor you actually pay sits on top of interchange and adds a much smaller margin.

The reason the buyer's AP team cares about it from the other direction is that the rebate they earn is a function of the same interchange your processor charges you. A buyer running a virtual card rebate program earns a percentage of payment volume back as a quarterly rebate from their card program. They're solving for total program economics after rebate, and they have a legitimate ask of you to participate, especially if you're getting paid faster as part of the deal.

Can you negotiate or get a rebate share?

You can ask, and in B2B card programs with mature buyer-side AP teams, the answer is often yes. The rebate-share mechanism works like this: the buyer's card program receives a quarterly rebate from the card issuer based on volume processed, and the buyer can elect to pass a portion of that rebate back to participating vendors. A common structure is 30 to 50 basis points of the gross payment volume credited back to the vendor monthly or quarterly. On a $100,000 invoice, that's $300 to $500 of the processing fee returned to you, which gets your effective cost down by a meaningful chunk.

Negotiation leverage improves when you can show the buyer the alternative cost they're imposing on you. If your customer pays you on 60-day terms today and they're asking for card acceptance to enroll you in their rebate program, the math is straightforward: ask for net-10 on the card payment plus a rebate-share. You give them the rebate-earning spend; they give you faster funds and a portion of the rebate; the all-in cost to you nets out close to ACH on a 30-day term. That deal isn't theoretical. It's how most large enrollment programs end up structured for vendors who push back constructively.

How much faster do vendors actually get paid?

The honest answer is meaningful, often decisive for a working-capital-tight vendor, and rarely the headline reason any single article puts the case together. Settlement timing on a virtual card runs same-day authorization and next-day funding to your bank for most processors, roughly 36 hours from when you key the card. A check that goes through the mail clears anywhere from 5 to 45 days depending on the customer's payment cycle, the postal route, and your bank's clearing window. An ACH credit reaches your bank in one to three business days from origination, but the buyer's AP team typically doesn't originate until day 25 to 35 of a net-30 or net-45 invoice cycle. Your effective time-to-funds on ACH is closer to 30 to 45 days from invoice date.

The Federal Reserve's 2024 Business Payments Study found that 66% of businesses would use instant or near-instant payments if they were offered, and 92% prioritize improved cash flow over other treasury goals. The demand is structural. The Fed also documented that commercial check volume processed by the Federal Reserve Banks fell to roughly 3.0 billion in 2024, about half of where it stood a decade earlier, and the decline shows no sign of stopping. Vendors who are still primarily paid by check are operating in the slowest-shrinking corner of the U.S. business payments stack, where supplier payment automation benefits increasingly accrue to the AR teams that move first.

Best practices for a virtual card program

Learn the internal strategies that make a virtual card program succeed — from program design to driving the vendor acceptance that determines how much of your AP spend earns rebates.

Download the guide

What does net-10 with a virtual card really mean?

Net-10 on a virtual card means the buyer's card program issues the virtual card within 10 days of the invoice date, and you process the charge to your bank as soon as you receive the card number. The funds reach your account within 24 to 48 hours of when you run the charge. Your effective time-to-funds from invoice date is roughly 11 to 12 days. That's a dramatic compression from a net-30 invoice paid by check (call it 35 to 50 days door-to-door including mail) or a net-30 invoice paid by ACH (call it 30 to 33 days).

The reason buyers offer net-10 on cards specifically is the program structure. Buyer card programs earn rebate on spend they put through the program; the more vendors they enroll and the higher the volume they process, the better the rebate economics work. Offering shorter terms is how they convert acceptance into participation. From your side, the deal looks like: take 20 days of receivable carry off the table, accept the card fee, and (in mature programs) capture a rebate-share back. The arithmetic on a working-capital-tight business is usually obvious once it's written down.

How does that change days sales outstanding?

DSO is the single number that moves the most when virtual card acceptance shows up at scale across your customer base. A vendor with $5M of annual revenue from card-accepting customers, paid on average at 45 days under the old model, carries roughly $616K of working capital tied up in receivables at any moment. Moving that book to virtual card with a net-10 cycle drops the average receivable to roughly $150K. That's $466K of working capital released back to the business without changing a single customer relationship. It funds payroll, inventory, growth, or the line of credit you would otherwise borrow against. The math scales with your card-paying revenue base.

Not every customer will agree to shorten terms; many will keep the original net terms and simply move the payment timing to the card instead of the check. Even then, the timing advantage holds. A net-30 ACH paid on day 32 and a net-30 virtual card paid on day 28 both end up at your bank around the same calendar moment, but the card pays you in roughly half the rolling window. Across a portfolio of dozens or hundreds of invoices, the float reduction is real money.

Is accepting virtual cards safe for the vendor?

Safe in this context means safer than the alternative on the table, which is usually a check (high fraud exposure, slow, manual matching) or an ACH (lower fraud exposure than a check but requires sharing your banking data with the buyer's AP system). Virtual cards land safer than both on most relevant axes. The card number you receive is single-use, capped at the exact invoice amount, often locked to your merchant ID, and dies after the charge clears. You don't share anything of yours to get paid. The most common B2B fraud vector (business email compromise that reroutes an AP payment to a fraudulent account) has nothing to grab onto when the payment is a virtual card going to a known merchant.

The AFP's 2025 Payments Fraud and Control Survey Report found that 79% of organizations experienced attempted or actual payments fraud in 2024, with checks the most-targeted payment method at 63%. Vendors who still cash checks have far more exposure than vendors who run their AR through cards and ACH. A vendor who switches a meaningful portion of their AR to virtual cards is reducing their own check exposure, not just the buyer's check exposure. Both ends of the transaction win on that.

What's the fraud profile compared to ACH and check?

A virtual card carries near-zero post-transaction fraud exposure because the card number dies after the single approved use. Even if the card number, CVV, and expiration date were intercepted in your remittance email, a second charge attempt declines because the controls close after the first authorized transaction. ACH carries low transaction-level fraud risk but ongoing data-exposure risk because your routing and account number live in the buyer's system permanently. Any compromise of that system over the next five years still threatens your account. Checks carry both the highest transaction-level fraud exposure (alteration, counterfeit, washing) and the highest data-exposure risk because the account information is printed on the front of every check you cash.

The right frame is exposure surface. A virtual card minimizes both the transaction-level surface (single use, capped amount) and the data-exposure surface (you receive a number, you process it, it dies). ACH minimizes transaction-level fraud (the rails are tightly controlled) but maintains a permanent data-exposure surface. Checks maximize both. The order of preference on a vendor's side, judged by fraud risk alone, is virtual card first, ACH second, check last. The fee structure runs in roughly the opposite order, which is why this is a real decision and not a free lunch. The fraud math should land squarely in your decision frame, not as a footnote.

What happens if there's a chargeback?

A chargeback on a B2B virtual card payment is unusual because the buyer's AP team approved the invoice before the card was issued. The chargeback process exists primarily to protect consumer cardholders from fraudulent merchant charges, not to give corporate AP teams an after-the-fact way out of an approved invoice. If a buyer attempts to charge back an invoice the AP team approved, the dispute resolution path usually returns the funds to the vendor on documentation: a copy of the invoice, the purchase order, and proof of delivery. If high-dollar acceptance from new customers is a meaningful concern, talk to your processor about your specific liability under their merchant agreement before you accept large card payments.

When does it make sense to say yes, and when to push back?

The decision shouldn't be binary. It's per-customer, per-invoice band, and per-rebate-share offer. The cases where you should default to yes are dollar amounts large enough that speed and security benefits dominate the fee, customers whose alternative payment timing is meaningfully slow, and situations where you'd otherwise carry working capital cost or factoring fees against the same receivable. The cases where you should push back are dollar amounts small enough that the absolute fee dominates anything you save, processors that don't support B2B-level interchange, or customers asking for card acceptance without offering anything in return on terms or rebate-share.

A working framework:

1. Default yes if the invoice is over $5,000, the customer's alternative payment timing is 30+ days, and you have no special processor constraint that would inflate your effective rate.

2. Negotiate if the fee feels heavy relative to your normal margins. Ask for net-10 (or shorter) terms, ask for rebate-share, or ask the customer to absorb the processing cost as a payment-terms concession.

3. Push back politely on the headline ask if the invoice is under $1,000 (the absolute fee dominates the speed value), if your processor doesn't support B2B interchange rates (your effective fee is much higher than the published range), or if the customer is offering nothing in return. Counter with ACH plus invoice-level remittance data, which gets most of the reconciliation benefit at a lower cost.

4. Walk away rarely, and only on a card-specific ask. The customer relationship isn't on the line if you don't accept the card; you can keep getting paid by ACH or check while you work through the math.

The vendor who closes the conversation with "we don't take cards" and offers nothing instead is the vendor who loses the relationship slowly. The vendor who closes with "we'd take the card at net-10 with a 30-basis-point rebate-share, otherwise let's stay on ACH at net-30" keeps the relationship and the math both. The second framing is what most buyer-side AP teams are actually hoping to hear.

When should you ask for a rebate-share?

Ask for a rebate-share when the buyer is asking for card acceptance on a meaningful annual volume with your business. At that volume, the buyer's program is earning measurable rebate from your transactions, and they have flexibility to share a portion back. Ask for it explicitly in the format you want, with basis points of the gross transaction paid monthly or quarterly, written into the payment-terms update. The typical successful negotiation lands in the 30 to 50 basis point range against gross card volume.

Don't ask for a rebate-share on a single-transaction relationship, on a small total volume, or on a customer that's already offering you faster payment terms in exchange for the card. The rebate-share is a high-volume conversation, and overreaching on it for a small-volume customer is the kind of negotiation move that gets you taken off the preferred-vendor list. The right asks are the asks proportional to what you're giving the buyer in program participation.

Virtual cards built for AP

Pay vendors with single-use cards locked to a specific supplier, amount, and date — then earn rebates on every payment. Corpay's vendor enrollment runs 2-3x higher than competitors, so more of your spend qualifies.

Explore virtual cards

When is ACH still the better option?

ACH is still the better option when you have a stable long-term relationship with the customer, you're getting paid on terms that already work for your cash flow, and the absolute fee on a card transaction would be a real economic drag relative to the marginal benefit. A vendor invoicing a long-time customer for $2,500 a month who's getting paid in 25 days under net-30 ACH terms doesn't have an obvious problem to solve. The card-acceptance fee on those transactions costs more than the speed improvement is worth. Stay on ACH unless the customer is offering something material in return.

The other ACH-wins case is when your processor doesn't support B2B-level card interchange, which means your effective rate on card acceptance lands closer to consumer-card pricing (3.0% or higher) instead of B2B rates. Talk to your processor before you commit. If they tell you all cards run at the same rate, that's your answer for this relationship. The longer-term play is to upgrade to a processor that recognizes B2B card interchange, but that's a different decision than the one in front of you on this invoice.

What to expect when your customer pays through Corpay

When a customer pays you through Corpay's virtual card program, the transaction looks like any other Mastercard payment on your processor's reporting. The card runs on Mastercard's rails, not a separate vendor-pay rail. The remittance email arrives with the card number, the invoice number cleanly broken out, and a contact path for any dispute or reconciliation question. Settlement runs on your processor's normal timeline, so the funds reach your account on the same schedule as any other card payment you take. There's no special acceptance program to enroll in, no portal to log into, and nothing on your AR side that has to change.

The reason the Corpay version matters to a hesitant vendor is scale. Corpay handles payments for over 800,000 businesses across a network of more than 4 million accepting vendors, and the program issues card transactions on Mastercard's rails as the #1 commercial B2B Mastercard issuer. That's not a fringe payment method. The buyer-side platform asking you to accept the card is the same platform paying your peers across the country and reconciling those payments back to invoice level. The story most vendors report on B2B virtual card acceptance is that it's mainstream commerce, not an experimental rail. If your customer's AP team is on Corpay, your acceptance experience will look more or less identical to any other established AR card relationship you might already have.

Vendors with their own AP needs sometimes ask whether the same platform handles their payables. The short answer is yes: Corpay's payments automation handles outbound supplier payments on the same platform that supports virtual card acceptance and broader commercial card programs. For the question in front of you on this invoice, what matters is that the inbound payment is normal-course and the funds will be in your account on the processor's next-day schedule.

Frequently Asked Questions

Should I accept virtual card payments from my customer?

In most situations where the invoice is over $5,000 and the customer is offering meaningfully faster payment than the alternative, yes. The processing fee is real, but so is the receivable carry cost you're already paying, the reconciliation effort you're saving, and the fraud exposure you're avoiding. Run your actual numbers against the alternatives before defaulting to no.

How much does it really cost to accept a virtual card?

The headline cost is the standard B2B card-acceptance rate from your processor, which varies by card type and your specific deal. The net cost is lower when you factor in rebate-share offers (often 30 to 50 basis points in mature programs), the carry cost you no longer pay on a slow receivable, and the reconciliation and fraud overhead you avoid versus checks.

How fast does a vendor get paid on a virtual card vs ACH?

Virtual card funds reach your bank in 24 to 48 hours after you process the charge, which the buyer typically initiates at or near invoice approval. Most ACH credits arrive at your bank one to three business days after origination, but the buyer's AP team usually doesn't originate until day 25 to 35 of a net-30 cycle. End to end, a virtual card on net-10 terms beats a net-30 ACH by 20 to 25 days.

Can I negotiate the interchange fee or get a rebate share?

You can negotiate a rebate-share with most mature buyer card programs above a meaningful annual card-paid volume threshold. Ask for basis points credited back against gross card transactions, paid monthly or quarterly, written into the payment-terms update. You can't negotiate the interchange itself (that's set by the card networks), but you can negotiate how much of the rebate the buyer's program keeps versus shares back.

Is accepting a virtual card safer than accepting an ACH?

For most fraud and data-exposure axes, yes. A virtual card is single-use, capped at the invoice amount, and dies after the charge clears, so the post-transaction exposure window is near zero. ACH carries low transaction-level risk but maintains a permanent data-exposure surface because your routing and account number live in the buyer's AP system permanently.

What's net-10 on a virtual card vs net-30 on ACH worth?

For a vendor with several million dollars of annual card-eligible revenue, the float compression from net-30 ACH to net-10 virtual card releases meaningful working capital. The math scales with your card-paid revenue base. Whether to give some of that back through rebate-share negotiation is a separate question from whether the underlying float compression is worth pursuing.

Will accepting virtual cards hurt my margin?

The headline fee will show up on your merchant statement. The net margin impact depends on what the card-accepted invoice would have cost you under the alternative: receivable carry, factoring fees, reconciliation labor, fraud risk. For most B2B vendors with material receivable carry costs, the net margin impact is small or positive. For vendors who already get paid quickly under the alternatives and don't carry working capital cost, the fee is more of a real margin drag and the decision is a closer call.

What happens if there's a dispute or chargeback?

Chargebacks are rare on B2B virtual cards because the buyer's AP team approved the invoice before the card was issued. If a dispute arises, the resolution typically returns funds to the vendor on documentation (invoice, PO, proof of delivery). If high-dollar acceptance from new customers is a meaningful concern, talk to your processor about your specific liability under your merchant agreement.

Do I need a special processor to accept B2B virtual cards?

You don't need a special processor, but you do need one that recognizes B2B-level card interchange. Most modern merchant processors do; some lower-end ones charge a flat consumer-card rate on every transaction, which makes B2B acceptance expensive. Ask your processor what rate they'd apply to a corporate-card B2B transaction before you commit.

What should I tell my customer if I don't want to accept it?

"We'd be glad to take the card at net-10 with a 30-basis-point rebate-share; otherwise we'd prefer to stay on ACH at our current terms." That sentence opens the negotiation in the right place. It tells the buyer you understand the program economics they're working with, it gives them a clean counter that improves your math without killing theirs, and it preserves the relationship if they decline. A flat "we don't take cards" closes a conversation that didn't need to close.

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