Card payments now dominate everyday spending: credit and debit cards together made up more than 60% of monthly payments in 2023, according to the Federal Reserve’s Diary of Consumer Payment Choice. Cash, by contrast, has been losing ground for years, falling to 40% of small-value payments in 2021, down from 47% in 2019, per the same Federal Reserve research. These numbers describe the broad shift toward card-based spending in general, not virtual cards specifically, but they help explain why single-use and disposable card numbers have become a normal part of that card-heavy landscape. As more people adopt them, a basic question keeps coming up: if the card number you paid with no longer exists, where does the refund actually go?

How a refund tries to find its way back

A virtual card is a token: a 16-digit number generated by your bank or card provider and linked behind the scenes to your real account. When you pay a merchant, the token authorizes the charge, and the issuer settles the real money movement internally. A refund works the same way in reverse — the merchant sends the refund instruction to the same token number they charged, not to your underlying account directly. That works fine if the token is still active. Problems start when the virtual card was single-use, has expired, or was deliberately deleted after the purchase, because the merchant’s payment processor may try to credit a number that the network now treats as dead or frozen. Depending on the issuer, that refund either bounces back to the merchant as a failed transaction, gets held in a suspense queue until someone manually reroutes it, or — in better-designed systems — is automatically recognized by the card network and credited to the parent account anyway, since the token and the account share a backend identifier even after the token itself is retired. That backend identifier is the part most cardholders never see: card networks route transactions using a combination of the card number, an issuer identification range, and an internal account reference, and it’s that last piece that survives when a token is closed. Whether a given issuer actually checks that reference before giving up on a stalled refund is a design choice, not a universal rule, which is exactly why two people using virtual cards from two different providers can have completely different experiences with the same kind of return.

A returned order that took three weeks to resolve

The following situation is a composite example built to illustrate a common pattern, not an account of a specific person or real case.

The following situation is a composite example built to illustrate a common pattern, not an account of a specific person or real case. A shopper — call her Maya — generated a single-use virtual card to buy a winter jacket online, a routine habit she’d picked up to limit how many merchants ever saw a reusable number. The jacket didn’t fit, so she requested a return through the retailer’s portal and, out of habit, deleted the virtual card the same afternoon, assuming the transaction was fully closed. The retailer processed the return five days later and issued a refund to the card number on file — the one Maya had just deleted. Her card provider’s app showed nothing: no pending credit, no failed transaction notice, nothing to indicate the refund had even been attempted. For almost two weeks, the money existed only in the merchant’s system as a completed refund and in Maya’s provider’s system as an attempt against a closed token sitting in a queue nobody had flagged for her. It only moved when she contacted support with the original order confirmation and the closed card’s last four digits; an agent manually matched the refund to her account and released it three weeks after the return was approved. Nothing about the situation involved fraud or an error on the merchant’s side — it was simply a routing gap between a closed token and a live account that needed a human to bridge it.

How to keep a refund from getting stuck

The fix isn’t to avoid virtual cards — it’s to manage their lifecycle deliberately, so a refund always has somewhere to land. A little bit of discipline around when you retire a card number removes almost all the ambiguity merchants and processors run into, and it costs you almost nothing in terms of security, since a merchant-locked or time-limited card still contains the exposure a reusable card would create.

Leave the card open until the return window closes

Don’t delete or freeze a virtual card the moment a purchase goes through. Most merchants allow returns for 14 to 30 days, and some categories, like travel or furniture, run longer. Check the seller’s stated return policy and keep the card number active at least that long, plus a short buffer for processing delays on the merchant’s side. If the listed policy is vague or you can’t find it, a safe default is 45 days, which covers the large majority of retail and marketplace return windows without leaving the card open indefinitely.

Use merchant-locked cards instead of single-use ones for anything returnable

Many virtual card tools let you lock a number to one merchant rather than one transaction. That setting still limits exposure if the merchant’s systems are breached, but it leaves the card alive for exchanges, partial refunds, or a follow-up order, which is exactly the situation where a single-use card creates the most friction. This matters even more for purchases that generate multiple separate transactions over time, like a split shipment or a backordered item, where a single-use card would already be closed before the second charge or refund ever arrives.

Check your provider’s stated refund-after-closure policy before relying on it

Issuers differ in how they treat refunds sent to a closed token. Some route the money to the parent account automatically for a fixed window after closure, often 60 to 120 days; others don’t. Read this in your provider’s terms once, rather than discovering it during a dispute, and keep a note of the window so you know how long to wait before escalating. If the terms don’t mention refund handling after closure at all, treat that silence as a signal to keep cards open longer than you otherwise would, since you have no documented guarantee that a late refund will find its way back on its own.

Keep the transaction record even after the card is gone

Save the merchant confirmation, the card’s last four digits, and the date it was issued or closed. If a refund stalls, this is what both the merchant’s support team and your issuer will ask for to trace the original authorization and manually push the credit through. A screenshot of the order confirmation plus the closed card’s details, stored in one place, usually cuts a support conversation from several back-and-forth emails down to a single message with everything the agent needs.

Why a dedicated virtual card manager solves this better than deleting cards by instinct

The core issue isn’t virtual cards themselves — it’s losing visibility into which numbers are still live, which are tied to a pending return, and which can safely be closed. A dedicated virtual card manager keeps every generated number, its merchant lock, its spending limit, and its status in one place, so you’re not guessing whether a card is safe to retire. Good tools also show refund and transaction history per card rather than burying it in a single combined statement, which makes it far easier to spot a refund that landed somewhere unexpected. Because the underlying account stays constant even as individual card numbers rotate, a well-built system is also what makes automatic rerouting of late refunds possible in the first place — the backend link between token and account has to exist and be queryable for that rerouting to work. Choosing a provider that documents its refund-handling policy clearly, rather than one that treats it as a support-ticket edge case, is the practical difference between a refund that resolves itself in days and one that requires several emails to untangle. When comparing tools, it’s worth looking specifically for a visible card-status history, a stated grace period for refunds after closure, and an in-app way to flag a card as pending a return rather than simply active or closed — those three features together cover most of the scenarios that otherwise end with a support ticket.ont the work needed for the scenario above.aff.ont.affiliateLabel.aff.affLabel.affLabel.aff.aff.aff.aff.aff.aff.aff.aff.aff.aff.aff.aff.

Veritasaffiliate link

Virtual cards for online payments — the main card stays out of checkouts

Payments