What happens when a virtual card payment is disputed or flagged as fraud

Read summarized version with:

ChatGPT Claude Grok Perplexity Gemini

When a virtual card charge looks wrong, unauthorized, or fraudulent, report it to Zil Money support with the transaction details, freeze the card to stop further authorizations, and the claim goes to the card network and issuing bank for review. The outcome is decided case-by-case, with no fixed timeline promised in advance.

If you manage a card program, the moment that makes you nervous is not the everyday decline. It is the charge that looks like it should not be there at all: an unfamiliar merchant name, an amount that does not match what your employee said they spent, or a card number apparently used somewhere your team never went. That is a different situation from a card that gets declined at the register, where the transaction never goes through, and different from a merchant voluntarily issuing a refund. A dispute is what happens when the merchant does not hand the money back on its own.

What actually counts as a disputed charge

Not every strange-looking line on a statement is a dispute in the making, and treating every one that way wastes time and creates alarm where none is needed. Before you report anything, look at what actually happened and match it to one of a few common patterns.

The first two rows are false alarms more often than not. The last row is the one worth a formal dispute. Sorting a charge into the right row before you act saves you from freezing a card over a legitimate vendor.

The process when you dispute a virtual card charge

Once you have confirmed a charge is genuinely wrong, the process runs in five steps. None of them are automatic, and none of them guarantee a specific result. What they do is get the right information in front of the people who can actually reverse a charge: the card network and the bank that issued the card.

1. Confirm the charge is actually a problem. Pull up the transaction detail and receipt before you assume fraud. An unfamiliar merchant name is the single most common false alarm.
2. Freeze or cancel the card immediately. If the charge is genuinely unrecognized, incorrect, or fraudulent, stop new authorizations right away.
3. Report the disputed charge to support with the transaction details. Contact Zil Money support through your account or support channel and give the date, amount, and merchant name.
4. The claim is reviewed with the card network and issuing bank. Support forwards what you reported, and the network and bank review it against whatever evidence the merchant or its acquirer provides.
5. The outcome is communicated once the review completes. You are told whether the charge was reversed or upheld.

Notice what is missing: a self-service button that resolves the case on the spot. Reporting a disputed charge means talking to a person. A genuine dispute involves a second party (the merchant) and a third party (the network and issuing bank), and none of them can be settled by a toggle in a dashboard.

Why freezing the card does not undo a charge already in progress

This is the detail that trips up almost everyone the first time they go through this, so it is worth being precise about it. A card transaction happens in two stages. First, authorization: the merchant's terminal checks that the card is valid and reserves the amount. Second, settlement: the transaction actually posts and the funds move. Freezing or canceling a card blocks new authorization requests from the moment you do it. It does not reach backward and undo an authorization that already cleared before you froze the card.

In practice, that means a charge that got through the first stage minutes or hours before you noticed the problem can still complete the second stage days later, and it will still count against the card's spend cap even though the card itself is already frozen. Where the card also carries merchant, category, location, or time locks, where supported, those locks are checked at the authorization stage too, so they cannot be applied after the fact to something already in flight.

None of this makes freezing pointless. It is the single most useful thing you can do the moment you suspect a problem, since it stops every authorization that has not happened yet. It is just not a guarantee against every dollar that might still land. Speed matters because it shrinks the window, not because it closes it. Setting merchant, category, and location controls when the virtual cards for the business are first issued, rather than after a problem shows up, gives disputes like this less room to happen at all.

A real example: a false alarm and a genuine fraud case

Mistakes to avoid when a charge looks wrong

Why reporting quickly still matters, even without a promised turnaround

Once you report a disputed charge, expect an acknowledgement from support that your claim has been opened, and expect to be asked for whatever documentation you have: the transaction date, amount, merchant name, and a short description of why you believe it is wrong. From there, the claim moves to the card network and the bank that issued the card, who look at the transaction against any evidence the merchant or its payment processor supplies. As a rough anchor and nothing more, cases like this are commonly resolved within a few weeks, though every review is case-by-case and nothing is guaranteed in advance.

That review having no promised turnaround date is not the same thing as having unlimited time to report the problem in the first place. Card networks set their own filing deadline for disputes, a window measured from the transaction date that is commonly cited as around 120 days under card-network rules, though exact limits vary by network and program. Report the charge as soon as you spot it rather than waiting to see whether the amount changes or the merchant reaches out on its own; once that filing window has closed, the network may not be able to open the case at all, no matter how strong the underlying claim is.

People also ask