Refunds, Voids, and Chargebacks: Three Different Things
These three terms are often used as if they meant the same thing, but their initiators, stages, and consequences are all different:
| Refund | Void | Chargeback | |
|---|---|---|---|
| Who initiates | Merchant | Merchant | Cardholder, filed with the issuer |
| Stage | After capture | Before capture—cancels the authorization | After capture |
| Funds flow | Merchant voluntarily returns the money | The authorization is released; funds were never actually taken | Funds are pulled back from the merchant |
| Enters the dispute process | No | No | Yes |
The most practical order to think in: if it can be voided, don't capture; if it can be refunded, don't charge back.
Why this order matters: voids and refunds are merchant-side actions—they're handled quickly and usually leave no lasting record. A chargeback, by contrast, enters the card network's dispute process and counts as a recorded event for the merchant.
Reason Codes: What the Process Reads
When a chargeback is filed, it is assigned a reason code. Reason codes aren't meant for the cardholder—they're for the machinery of the process: they determine where the burden of proof lies, how long the timeline runs, and who bears the loss.
Each card network maintains its own reason code system, and the specific numbers change with each version, but the broad categories are stable over time and revolve around these four:
| Category | What it says | Where the burden of proof usually lies |
|---|---|---|
| Fraud | The cardholder claims the transaction was not made by them | Depends on verification strength (e.g., 3DS) and card type |
| Authorization issues | The authorization itself was defective: unauthorized, or captured after being declined | Merchant |
| Processing errors | Wrong amount or currency, duplicate capture, late capture | Merchant |
| Consumer disputes | Item not received, materially different from the description, charges continuing after cancellation | Merchant, which must provide proof of fulfillment |
The numbers change; the categories don't. Refer to each network's current rules for the specific codes.
What a Representment Is Arguing
If the merchant disagrees with a chargeback, it can submit evidence to rebut it within the time limit. This step is called representment, and it argues exactly one thing: whether the transaction met the conditions required by that reason code.
| Evidence type | What it proves | Which category it applies to |
|---|---|---|
| Verification records (e.g., 3DS) | The transaction was verified by the cardholder | Fraud |
| Records of card-detail validation matches | The card details came from the cardholder themselves | Fraud |
| Shipping and delivery confirmation records | The goods were delivered | Item not received |
| A history of successful transactions on the same card | Earlier transactions were normal, not stolen usage | Fraud |
| Records of the merchant's terms and cancellation process | The service was provided as agreed | Consumer disputes |
| Timing records of authorization and capture | The capture occurred within the valid window | Processing errors |
The outcome of a representment is usually decided before this step even begins: whether the evidence was kept.
Time limits are set by the card network's rules and are subject to change—refer to the current rules for the exact number of days. Missing the deadline is a default loss, and there are no exceptions.
Chargeback Rate: The Ratio Merchants Fear Most
The chargeback rate is the core metric merchants are monitored on, and the formula is straightforward: chargebacks in the month ÷ total transactions in the month.
Card network monitoring programs usually look at two conditions at the same time: a percentage threshold and an absolute transaction-count threshold, and you only enter monitoring when both are exceeded. In public materials, commonly cited thresholds hover around 1%, with tiers such as 0.9% and 1.5% applying to different networks and different programs.
What happens once a merchant is under monitoring: it may be required to remediate, fined, or asked to post a reserve, and in serious cases it can have its ability to accept card payments terminated. This also explains why merchants are so sensitive to chargebacks—and why some merchants will simply refuse to serve you after one.
Which Path Should a Cardholder Take First
First check whether the money was actually taken
If it only appears among pending items, it's an authorization—it will release on its own if never captured. Only when it genuinely appears among completed transactions do you need the next step.
With a dispute, contact the merchant first
A refund is the fastest path and doesn't enter the dispute process. Most disputes are resolved at this step, without ever needing a chargeback.
If the merchant doesn't respond, go to the issuer
Only at this point does it become a chargeback. You'll need to state which category of reason it falls under and prepare the corresponding evidence.
Keep the evidence
Orders, communication records, shipping information, cancellation process records. Evidence is your only leverage at the representment stage, and it can't be reconstructed afterwards.
There's a hard precondition here: a chargeback requires a reason, and the reason is limited to the categories above. "I changed my mind" isn't one of them.
A Chargeback Is Not a Free Undo Button
The cost of a chargeback needs to be stated clearly—there are four of them:
- For the merchant: it counts toward the monitoring metric, and reaching the threshold triggers action;
- For the cardholder: the merchant can rebut with evidence, and if the evidence is sufficient, the funds will be pulled back;
- For the relationship: abusing chargebacks can lead the merchant to simply refuse to serve you;
- For the outcome: filing a chargeback is not the same as getting your money back—the evidence and the rules decide in the end.
There's one more point that's often overlooked: a chargeback resolves this particular charge, not the underlying dispute between you and the merchant. If returns, warranty, or service issues are also involved, those still need to be handled separately.
Our boundary here needs to be explicit: the rules for refunding and freezing funds on your card are set by our platform's own policies, see Refund Policy. The dispute process described below takes place among the cardholder, the merchant, and the issuer—it is not adjudicated by us, and wedon't promise any chargeback outcome.
Chargebacks carry costs—negotiate first when there's a dispute. If it involves a balance refund on our platform, the rules are in Refund Policy, and the card issuance entry point is on the Sign-up page.
FAQ
What's the difference between a refund, a void, and a chargeback?
A refund is the merchant voluntarily returning money after capture; a void is the merchant cancelling the authorization before capture; a chargeback is filed by the cardholder with the issuer, the funds are pulled back from the merchant, and the case enters the dispute process.
Under what circumstances can I file a chargeback?
It's limited to a few categories of reasons: the transaction wasn't made by you, goods or services were never received, the item was materially different from its description, or duplicate or incorrect charges. Simply changing your mind isn't one of them.
What does a chargeback reason code mean?
It's the category each card network assigns to a chargeback, used to determine the burden of proof, the timeline, and who bears the loss. The codes differ between networks and change over time, but the broad categories stay stable across four groups: fraud, authorization issues, processing errors, and consumer disputes.
What is a merchant's representment arguing about?
Not about who's in the right, but whether the transaction met the conditions required by the reason code. The merchant must submit the corresponding evidence within the time limit; missing the deadline is a default loss.
What evidence does a representment usually need?
It depends on the reason code: verification records, card-detail validation matches, shipping and delivery confirmations, a history of successful transactions, records of the merchant's terms and cancellation process, capture timing records, and the like.
How is the chargeback rate calculated?
Chargebacks in the month divided by total transactions in the month, calculated by count rather than by amount. Network monitoring programs typically look at both a percentage threshold and an absolute transaction-count threshold.
Does a merchant being monitored affect cardholders?
Indirectly, yes. To control their chargeback rate, merchants may tighten risk control, require more verification, or simply refuse to serve cardholders with a chargeback history.
Is filing a chargeback a guaranteed way to get my money back?
Not necessarily. The merchant can submit evidence to contest it, and the final decision rests with the evidence and the card network's rules—the outcome isn't guaranteed by any party.
There's a charge on my card I don't recognize. What should I do first?
Look at three fields together first: amount, time, and billing descriptor. Confirm whether the charge really made it into your completed transactions before deciding whether to contact the merchant or the issuer—see Account Verification and Billing Descriptors.
Got the idea in a few minutes? Go open a card
Cards start at $1, no monthly fee; account top-up is $0 with a $20 minimum per deposit. See the pricing page for full details.