Refund vs Void vs Chargeback: Timing, Fees and Ratio Impact

Last updated: November 11, 2026

A customer calls at 4:40 p.m. and says she was charged twice for a $1,280 sofa. Your rep has three buttons in front of them: void, refund, or “wait and see.” Pick the right one and the money is back on her card tonight with no fee. Pick the wrong one and you could be paying a dispute fee in six weeks for a sale you already gave back.

That’s why the refund vs void vs chargeback question matters more than it looks. All three put money back in the cardholder’s pocket. But they happen at different points, cost different amounts, and only one of them counts against you with Visa and Mastercard.

This guide walks through each one the way a payments ops team sees them: what triggers it, what it costs, and how it shows up in your ratios. Then it gives you a workflow for refunding before a customer calls their bank, and shows where a payment CRM like Midcove fits.

A void cancels a card transaction before it settles, so no money moves and fees are usually minimal. A refund returns money after settlement and is initiated by the merchant. A chargeback is a reversal forced by the cardholder’s bank, carries a dispute fee, and counts toward card network monitoring ratios.

Refund vs Void vs Chargeback: The Short Definitions

What is a void?

A void cancels a transaction that has been authorized but not yet settled. The charge never completes, so the funds are released back to the cardholder’s available balance. Think of it as tearing up a check before it’s cashed.

Voids only work until your daily batch settles. On NMI and Authorize.Net that’s a set cutoff time. On Stripe, the closest equivalent is canceling an uncaptured payment.

What is a refund?

A refund sends money back to the cardholder after the original sale has settled. The merchant starts it, usually because of a return, a cancellation, or a billing mistake. It shows up as a separate credit on the customer’s statement, typically a few business days later.

Refunds can be full or partial, and they go back to the original card through the merchant account that took the payment.

What is a chargeback?

A chargeback happens when the cardholder asks their bank to reverse a charge, and the bank pulls the funds back from the merchant. You don’t choose it. It’s done to you, along with a dispute fee and a deadline to respond.

Common claims are fraud, non-delivery, or “not as described.” For the full lifecycle, see our guide on how chargebacks work step by step.

Where Each One Sits in the Transaction Lifecycle

Picture a card payment as a timeline. Each reversal type belongs to a different part of it.

1. Authorization. The issuer approves the charge and places a hold on the customer’s funds.
2. Capture. You confirm you want the money. Many card-not-present merchants authorize and capture in one step.
3. Batch settlement. At the end of the day, captured transactions are sent for clearing. This is the line that ends your void window.
4. Funding. The acquirer deposits the net amount into your bank account, usually one to two business days later.
5. Post-settlement period. Refunds live here. So do chargebacks, which cardholders can typically file within about 120 days of the transaction or the expected delivery date, depending on the card network and reason.

So the void belongs to steps 1 to 3. Refunds and chargebacks both belong to step 5. The difference between those two is simply who pulls the trigger: you or the cardholder’s bank.

A quick example from a furniture store

Take a mid-size furniture retailer that takes phone orders on a virtual terminal for card-not-present payments. A rep keys in a $1,280 order twice by mistake at 2 p.m. The batch settles at 11 p.m.

If the rep catches it the same afternoon, a void kills the duplicate. The customer sees a pending hold drop off, and no refund line ever appears. If nobody notices until the next morning, the duplicate has settled. Now it needs a refund, and the customer waits several business days for the credit.

If the customer spots it on their statement three weeks later, they may call the bank instead. That’s how a $0 problem becomes a chargeback.

Side-by-Side Comparison Table

Here’s the whole picture in one place for your support team.

What Each One Costs You

Voids: usually the cheapest fix

A voided transaction never settles, so there’s no interchange on it, though some contracts include a small authorization fee. Stripe states that you can cancel a payment before it completes at no cost.

The catch is timing. Once the batch closes, the void option disappears.

Refunds: you lose the processing fee

Refunds return the sale amount, but in most setups you don’t get your original processing fee back. Stripe’s refund documentation says this directly: processing fees from the original transaction aren’t returned. Other processors vary, so check your statement.

On a $90 order at roughly 3% all-in, that’s about $2.70 in unrecovered fees.

Chargebacks: the expensive path

A chargeback costs you the sale, the goods (if shipped), a dispute fee, and the hours someone spends building an evidence packet. Dispute fees vary by processor and risk profile. Many merchants pay somewhere between $15 and $100 per case, and high-risk accounts often sit at the upper end.

Some processors also charge a second fee if you choose to fight. According to Stripe’s guide to how disputes work, there is a separate “dispute countered” fee in addition to the dispute received fee, and the received fee is generally not returned even if you win.

And every chargeback nudges your dispute ratio up, which can lead to monitoring programs, fines, or reserves.

How Voids, Refunds and Chargebacks Affect Your Ratios

Chargebacks count against you

Card networks track how many disputes a merchant gets compared with its transaction count. Mastercard runs its Excessive Chargeback Merchant program. Visa now uses the Visa Acquirer Monitoring Program (VAMP), which counts both reported fraud and disputes on card-not-present sales. Visa’s own overview of VAMP explains how the program combines fraud and dispute monitoring into one ratio.

Thresholds change over time and by region, so ask your acquirer for the numbers that apply to your MID. Our post on chargeback ratio monitoring breaks down how each network calculates it.

Refunds and voids don’t count as chargebacks

A refund is a normal credit, not a dispute. It doesn’t add to your chargeback count. A void never settles, so it doesn’t add to anything except perhaps your authorization count.

That’s why a refund-first culture works. A $90 refund costs $90 plus a few dollars. A $90 chargeback costs the same $90, plus a fee, plus ratio damage.

The fraud report trap

There’s one exception to know about. When a cardholder reports a charge as fraud, the issuer often files a fraud report (a TC40 at Visa, a SAFE report at Mastercard). Refunding the charge afterward stops the chargeback, but it may not erase the fraud report.

Under VAMP, those fraud reports feed the ratio too. Stripe’s dispute docs note that a refund generally only prevents a fraud report when it’s processed as a reversal shortly after capture. So for true stolen-card cases, speed matters even more.

One caution: a very high refund rate can still worry your acquirer, so watch it per MID alongside dispute rate.

A Refund-First Workflow That Prevents Disputes

A refund-first policy doesn’t mean refunding everyone. It means making the refund path faster than the chargeback path.

1. Check the open batch before cutoff. Have someone scan the day’s transactions for duplicates, test charges, and cancelled orders an hour before settlement. Void anything that shouldn’t settle.
2. Give support a clear refund authority matrix. For example: frontline staff can refund up to $150 without approval; team leads up to $1,000; anything above goes to finance.
3. Reply to billing complaints within one business day. Silence sends customers to their bank.
4. Refund to the original card through the original MID. If you run multiple merchant accounts, a refund pushed through the wrong one creates reconciliation headaches and may not be allowed.
5. Send a confirmation with a reference number. Say how long the credit usually takes. This one email prevents many “I never got my money” disputes.
6. Use pre-dispute alerts where you have them. Alert services such as Ethoca and Verifi’s Rapid Dispute Resolution let you refund before a dispute becomes a formal chargeback. Your processor can tell you what’s available.
7. Log a reason for every refund. The patterns tell you what to fix upstream.

Where a payment CRM helps

This workflow breaks down when refunds, voids, and disputes live in four gateway portals. Support can’t see that a disputed order was already refunded.

Midcove sits on top of the merchant accounts you already have with NMI, Authorize.Net, Stripe, or PayPal. Its refund management tools handle full and partial refunds and send each one back through the original MID. Voids, refunds, and sales show in one transaction dashboard across gateways, and disputes land in a single chargeback queue with deadline tracking.

Common Mistakes Ops Teams Make

• Refunding after a chargeback is already open. Once a dispute is filed, a separate refund can mean the customer gets paid twice. Handle it inside the dispute process instead. Stripe, for one, blocks refunds outside the dispute while a dispute is open.
• Missing the void window. Staff see the error but wait until tomorrow to “deal with it.” Now it’s a refund with fees.
• Partial refunds without explanation. A customer who expected $200 back and got $140 may dispute the whole charge. Always state what was refunded and why.
• Letting dispute deadlines slip. Response windows are often 7 to 21 days depending on the network and processor. Miss one and you lose by default.

For a broader prevention playbook beyond refunds, see our guide on practical ways to reduce chargebacks.

Key Takeaways

• A void cancels a transaction before batch settlement; a refund returns money after settlement; a chargeback is forced by the cardholder’s bank.
• Voids are usually the cheapest fix, so review the open batch before cutoff every day.
• Refunds typically cost you the original processing fee, but they don’t count toward chargeback ratios.
• Chargebacks bring a dispute fee, lost goods, staff time, and ratio damage under programs like Visa VAMP and Mastercard’s ECM.
• Refunding after a fraud report may stop a chargeback but not the fraud report itself, so act fast on suspected fraud.
• A refund-first workflow with clear authority limits and quick replies keeps customers away from their bank.
• Track refunds, voids, and disputes per MID in one view so problems in one brand don’t hide in the averages.

Frequently Asked Questions

Is a void better than a refund?

When it’s available, yes. A void stops the transaction before it settles, so the customer never sees a completed charge and you usually avoid processing fees. The limit is timing: once the daily batch settles, you must issue a refund instead.

How long do I have to void a transaction?

Usually until your gateway’s batch settles, which is often once a day at a set time. On NMI and Authorize.Net, you’ll see the cutoff in your settlement settings. On Stripe, you can cancel a payment that hasn’t been captured yet. Ask your gateway exactly when your batch closes, since it differs by account setup.

Does a refund count as a chargeback?

No. A refund is a merchant-initiated credit and doesn’t count toward your chargeback ratio. That’s why refunding a genuine complaint quickly is almost always cheaper than letting it become a dispute. Keep an eye on overall refund rate, though, because acquirers can still flag unusually high refund levels as a risk signal.

Can a customer file a chargeback after getting a refund?

Yes, it happens. A customer may not notice the credit, or may dispute before the refund posts. If that occurs, respond to the dispute with proof of the refund, including the date, amount, and reference number. That evidence usually wins the case, but you’ll still have paid the dispute fee in most setups.

Should I refund a transaction that already has a chargeback?

Generally, no. Once a chargeback is open, the funds have already been pulled back to the cardholder, so a separate refund can pay them twice. Either accept the dispute or fight it with evidence. Some processors block refunds while a dispute is active.

Do I get my processing fees back on a refund?

Often not. Many processors keep the original processing fee when you refund. Stripe states this in its documentation. Some interchange-plus setups pass back part of the interchange, and reversals done very soon after the sale may cost less. Check your monthly statement to see how your processor handles it.

How much does a chargeback cost a merchant?

More than the sale itself. You lose the transaction amount, any goods shipped, a dispute fee that commonly ranges from about $15 to $100, and staff time. Some processors add a fee if you contest, and a rising ratio risks monitoring program fines.

How long does a customer have to file a chargeback?

For Visa and Mastercard, cardholders typically have around 120 days from the transaction or expected delivery date, though some reason codes and services allow longer. For prepaid travel or events, the clock often starts on the service date. That’s why a booking taken in January can be disputed well into summer.

Choosing the Right Reversal Every Time

The refund vs void vs chargeback decision comes down to timing and control. If the batch hasn’t settled, void it. If it has, refund it quickly and tell the customer exactly what you did. Chargebacks are the outcome you get when neither of those happens fast enough.

Teams that do this well check the open batch daily, give support clear refund limits, and watch refunds and disputes per merchant account. That’s the kind of daily routine Midcove is built to support, with voids, refunds, and chargeback cases from every gateway in one place, sent back through the MID that took the payment.

Start this week: find your batch cutoff time, write down your refund limits, and check last month’s refund and dispute counts per MID.