Card Refunds, Reversals and Voids Explained

When money needs to go back to a cardholder, the right mechanism depends on how far the original transaction has progressed. A void or reversal cancels a transaction before it settles, so the customer's reserved funds are simply released. A refund is a new transaction that pushes money back to the card after settlement has already happened.

Choosing the right one matters for the customer experience: a released hold restores the customer's available balance without money ever having moved, while a refund has to travel back through the card networks and can take several business days to reflect.

Refund vs Reversal vs Void

Terminology varies between providers: "void" and "reversal" are often used interchangeably, and some platforms expose only a single "cancel" action that voids or reverses depending on the transaction state.

When Should You Void or Reverse Instead of Refund?

Whenever the transaction has not yet settled. Typical situations:

• The customer cancels an order minutes after placing it.
• A duplicate transaction is spotted on the same day.
• A pre-authorisation hold is no longer needed, for example a rental deposit after the vehicle is returned. See Authorisation, Capture and Pre-Authorisation.

Voiding is better for everyone: no money moves, so there is nothing to reconcile, and the customer's funds are released rather than being debited and later re-credited. Note that the release of the pending amount is controlled by the issuing bank, so customers of different South African banks may see the hold disappear at different speeds.

How Do Card Refunds Work?

A refund is a payment in the opposite direction. The merchant instructs the refund through their payment provider, the amount flows back through the acquirer and card network, and the issuing bank credits the cardholder's account.

Key points:

• Refund to the original card only. Scheme rules require refunds to go back to the card that paid. This protects against money-laundering and keeps the audit trail intact. If the card has been closed, the issuing bank still receives the refund and routes it to the customer.
• Partial refunds are allowed. You can refund any amount up to the original transaction value, and in most cases split it across multiple partial refunds.
• Timing depends on the banks. Refunds commonly take a few business days to show on the customer's statement, and timing differs between issuers. Tell customers this upfront to avoid "where is my refund?" queries.
• Fees are not always returned. Depending on your pricing agreement, the processing fees on the original transaction may not be reimbursed when you refund. Check your provider's terms rather than assuming.
• Refunds are not disputes. A refund is voluntary. If the cardholder instead disputes the transaction through their bank, that is a chargeback, a formal process with evidence requirements and additional cost. Refunding quickly when a customer has a valid claim is almost always cheaper than losing a chargeback. See Card Chargebacks.

Practical Tips for Merchants

• Prefer a void or reversal over a refund whenever the transaction has not settled.
• Publish a clear refund policy and set expectations about how long refunds take to reflect.
• Use idempotency controls so a refund cannot accidentally be submitted twice. See Idempotency and Duplicate Payments.
• Track refund events via webhooks so your order system and your payment records stay in sync. See Webhooks and Callbacks.
• Watch your refund rate; an unusually high one can indicate product, fulfilment or fraud problems.

Related Topics

• Card payments hub
• Authorisation, Capture and Pre-Authorisation
• How Do Card Payments Work?
• Card Chargebacks