A customer says their refund never arrived. The money is fine. It just went back by a different route than anyone expected.
A customer calls a merchant to say they were charged twice. The merchant pulls up the sale, sees it was canceled a few minutes after it ran, and has no idea what the customer means. So the merchant calls the software company.
Usually, nothing went wrong with the money. A pending hold was still sitting on the customer’s card, or a refund was still working its way back through the banks. The real problem is that “cancel,” “refund,” and “reverse” get used as if they mean the same thing. In card payments, they do not.
Here is what each one is, when each one applies, and what your software can do so that merchants and their customers know what to expect.
The short answer
- A void cancels a sale after it is authorized but before it settles. The charge never posts.
- An authorization reversal releases all or part of a hold on funds that were approved but will not be captured.
- A refund is a new transaction that sends money back to the customer after the original sale has settled.
The deciding factor is timing. Before settlement, a sale can be canceled. After settlement, it has to be paid back. If the path from approval to settlement is new to you, our walkthrough of how card payments settle covers it step by step.
Side by side
| Void | Authorization reversal | Refund |
When it can happen | Before the batch settles | Before the authorized amount is captured | After the sale has settled |
What it does | Cancels the sale | Releases all or part of a hold | Sends a new credit to the customer |
What the customer sees | A pending charge that drops off | A hold that drops off or shrinks | The original charge, then a separate credit |
How fast | Usually the quickest | Depends on the issuer releasing the hold | The slowest, on the issuer’s timeline |
Cost to the merchant | Usually the lowest | Avoids network fees tied to unused holds | Fees on the original sale are usually not returned |
Most common mistake | Missing the batch cutoff | Never sending it, so the hold lingers | Refunding a different card, or refunding after a dispute is filed |
Void: canceling before the money moves
A void works only while the sale is still sitting in the open batch. Once the batch closes and the transaction goes to settlement, the void window is gone, and the only way back is a refund.
When it works, a void is the cleanest outcome. The charge never settles, the statement never shows a completed purchase, and there is no separate credit to reconcile. It is also the option merchants use least, often because staff do not know the window exists or the software does not make it clear which sales can still be voided.
The catch is what the customer sees. Even after a void, the pending line can stay in their banking app until the issuer clears it. That is the issuer’s process, not a second charge, but it is behind a large share of “you charged me twice” calls.
Authorization reversal: letting go of a hold
Many businesses authorize an amount first and capture the final amount later. A field service company authorizes at booking, a restaurant authorizes before the tip, a rental business authorizes a deposit. When the final amount is lower, or the job is canceled, the unused part of the hold should be released with an authorization reversal.
If it is not, the customer’s available credit or balance stays reduced until the hold expires on its own, which looks exactly like money taken. The card networks care about this too. Visa, for example, charges a misuse fee on authorizations that are neither captured nor properly reversed.
- Reverse the difference. When the captured amount is lower than the authorized amount, release the rest.
- Reverse what will not be captured. A canceled booking or an abandoned order should send a reversal, not simply be left to expire.
- Do not refund what never settled. A refund against a sale that is still only authorized can leave the customer with a hold and a credit at the same time, and confuse everyone.
Refund: paying it back after settlement
Once a sale has settled, money has moved. Undoing it means sending money back as a new credit, and the customer sees two lines: the original charge and, later, the refund.
- Full or partial. A refund can return the whole sale or part of it, such as one item from an order or the unused part of a service.
- Back to the original card. Card network rules expect the refund to go to the card used for the purchase. Refunding a different card weakens the merchant’s position if the customer later disputes the original charge.
- The issuer sets the clock. A merchant can send a refund the same day and the customer may still wait several business days to see it, because the issuing bank decides when the credit posts.
- Processing fees usually stay spent. Fees on the original sale are usually not returned when it is refunded, which is one reason the pricing model matters. Our comparison of interchange plus and flat rate pricing explains how those costs are built.
- Added fees come back with the sale. If the sale carried a surcharge, the refund should return it in proportion. Our guide to surcharges, cash discounts, and convenience fees covers how those fees work.
Refund or chargeback
A refund is the merchant sending money back. A chargeback is the customer’s bank pulling it back. The money can end up in the same place, but a chargeback adds fees, paperwork, and a mark against the merchant’s dispute history.
That makes a fast, clear refund one of the best ways to prevent a dispute. A customer who can see a refund is on its way rarely calls their bank. The reverse is also true: a refund issued after the customer has already filed a dispute can mean the customer is paid twice, once by the refund and once by the chargeback. Our guide to chargebacks and disputes covers what to do once a dispute is open.
Bank payments follow their own rules. An ACH payment that fails or is disputed comes back as a return under Nacha rules, not as a card refund or chargeback, one more difference covered in our look at ACH and card payments.
Why this lands on your software
The customer never sees the processor. They see the merchant’s receipt, the merchant’s checkout, and whatever screen your software puts in front of staff. Most refund confusion can be designed out.
- Show where each sale stands. Authorized, captured, settled, and refunded sales should look different on screen, so staff know which option is open. A declined sale needs neither, and our guide to reading decline codes explains why it failed.
- Offer the right option first. If a sale can still be voided, offer void. If it has settled, offer refund. Staff should not have to guess.
- Make partial amounts routine. Partial refunds and partial reversals should be a normal action, not a workaround.
- Release unused holds automatically. When the final amount is lower than the authorization, or a booking is canceled, send the reversal without waiting for someone to remember.
- Handle recurring charges carefully. Subscriptions raise prorated refunds and the question of stopping future charges, which our recurring billing guide covers in more depth.
- Put guardrails on refunds. Refunds are a common route for internal fraud. Role permissions, approval limits, and an audit trail protect the merchant, and payments partners watch refund patterns as part of the same risk discipline that starts with merchant underwriting.
- Set expectations on the receipt. A refund receipt that says when the credit should appear saves a phone call.
- Make it reconcile. Refunds are netted out of deposits, so reporting should tie each refund to the deposit it reduced.
What to ask a payments partner
- Can our software see batch status in real time, so staff know when a void is still possible?
- Are partial captures, partial reversals, and partial refunds supported through the same integration?
- How are refunds matched to the original sale in reporting and in deposits?
- What controls exist for refund permissions and limits, and can merchants manage them inside our product?
Three ways back, one experience
Voids, reversals, and refunds are not interchangeable. Each one fits a specific moment in the life of a sale, and choosing the right one is the difference between a quiet fix and an angry phone call. Most of that choice can live in the software, where staff never have to think about it.
That is easier when payments are embedded in the platform rather than bolted on, because the software already knows where every sale stands. Constellation Payments brings PCI DSS Level 1 security, a 99.9% uptime SLA, and coverage across the US and Canada to the software companies it partners with. If you want refunds and reversals to feel like part of your product, talk to your CSIPay representative.