Refund vs. void: doing them right the first time

A void cancels a card sale before it settles, so the transaction essentially never happened. A refund returns money after the sale has gone through, as a new transaction moving the other way. That one difference decides whether your customer watches the charge vanish or waits days for their money, and sometimes whether you pay processing costs on the round trip.

What's the difference between a void and a refund?

It comes down to batching. Card transactions collect through the day in a batch, which is the bundle your terminal submits for settlement, usually each night. Until that batch closes, a sale is authorized but not final. Void it and it's gone: the customer's bank drops the hold, no money ever moves, and there's typically nothing to pay fees on.

Once the batch closes, the sale is settled and the money is in motion. Now the only road back is a refund, a second transaction that pushes funds from your account to the customer's card. That takes days to appear on their end, and depending on your processing agreement, the costs from the original sale may not come back to you.

So the rule of thumb is short: same day, void. Any later, refund.

When should you void a transaction?

The classics: you rang $73.99 instead of $7.39. The cashier charged twice when the reader froze mid-sale. The customer paid and then remembered the other card, the one with the points. Any mistake caught while the customer is still in the store, or at least before your batch closes, is void territory.

Here's the clean way to do it:

1. Find the original transaction in your point of sale (POS) system or terminal, and confirm the batch hasn't closed yet.
2. Void it, and keep both records, the original and the void.
3. Tell the customer what to expect: the pending charge in their banking app may take a day or two to disappear, and that pace belongs to their bank, not to you.
4. If they're paying again with a different card or cash, ring it as a fresh sale. Never try to "adjust" the old one.

Why do refunds take days to show up?

Because a refund travels the same rails as a sale, just in reverse, and the customer's bank decides when to post it. Weekends and holidays stretch the wait further. Say it plainly at the counter: "The refund's done on my end; your bank usually takes a few days to show it." That single sentence prevents most of the follow-up visits, and follow-up visits about money are rarely the cheerful kind.

Always refund to the same card that paid. It protects everyone: the money returns where it came from, and your records show a clean loop. Cash refunds for card purchases make disputes messy, and in the worst case they help someone with a stolen card turn merchandise into cash at your expense. If the purchase was on EBT (Electronic Benefit Transfer, the card system for SNAP benefits), the value goes back to the benefit account the same way, and the receipt trail matters just as much.

Paperwork now beats arguments later

Every void and refund should leave a trail you could hand to a stranger: the original receipt, the void or refund receipt, and a one-line note if the story was unusual. If the customer later disputes the charge anyway, that trail is your whole defense, and it takes thirty seconds to keep.

A POS with integrated payments does most of this filing for you, matching refunds to their original sales automatically. That's one of the quieter benefits of running payments through your register instead of beside it, and it's why NRS Pay integrates with the NRS POS. Questions about your own setup? The NRS Pay team takes them seven days a week.