---
title: "Reversal"
url: "https://mahouse.world/glossary/reversal"
type: "glossary term"
topic: "Transaction lifecycle"
author: "Ihor Vlasov"
reviewed: "2026-09-20"
published: "2026-08-10"
---

# Reversal

A reversal is the message a merchant or acquirer sends to cancel an authorisation, in full or in part, so the issuer releases the hold on the cardholder's balance — because the sale did not go through, the terminal timed out, the customer cancelled, or the final amount was less than the estimate. It is the mechanism behind a void and a partial release; the word is also used loosely for refunds and chargebacks, which differ.

**Also known as:** Authorisation reversal, Partial reversal, Payment reversal

## Key facts

- **Used at:** timeouts and errors (the terminal or gateway got no response and must cancel what may have been approved), cancellations before capture, partial reversals when the capture is less than the authorisation, and the schemes' misuse rules, which require merchants to reverse authorisations they will not capture
- **Binding:** the schemes' message specifications for full and partial reversals; scheme rules requiring reversal of unused authorisations within set times; the issuer's obligation to release the hold on receipt — its speed varies
- **Typical forms:** automatic reversal by the terminal or gateway on timeout ("we asked, we heard nothing, cancel it"); merchant-initiated void before capture; partial reversal at capture for the unused amount; incremental authorisation is the opposite operation, raising the hold
- **Typical distinction:** a reversal cancels an authorisation (no money moved); a refund returns money after capture (a credit through clearing); a chargeback is the issuer's forced return; "payment reversal" in a bank-transfer context means recalling a transfer, a different thing again
- **Parties:** the merchant and its gateway or terminal (which send), the acquirer and network (which carry), the issuer (which releases), and the cardholder whose available balance recovers

## How a reversal works in practice

A terminal sends an authorisation and the response does not arrive within its timeout. The terminal cannot know whether the issuer approved and placed a hold, so it sends a reversal for the same transaction: if the authorisation was approved, the issuer releases the hold; if it never arrived, the reversal has nothing to do. The customer is asked to tap again, and the second authorisation stands alone. Without the automatic reversal, a slow network produces two holds for one purchase and a cardholder who thinks she was charged twice.

Partial reversals do the same at the end of an estimate. A hotel that authorised €500 and captures €380 sends a partial reversal for €120 alongside the capture; the issuer converts €380 to a charge and releases €120 at once, rather than letting it expire. Fuel dispensers, once notorious for €150 holds against €40 fills, now send the completion amount within minutes under scheme mandates, and the issuer adjusts the hold. Merchants that do not send reversals leave holds to expire and pay the schemes' misuse fees for authorisations never captured.

For payments engineers, reversal handling is the error path that decides whether the integration is robust; for cardholders, it is the difference between a hold that vanishes in an hour and one that lasts a week.

## Example

A quick-service restaurant chain's terminals have no timeout reversal configured. On a day of network instability, 6% of taps time out; customers tap again; 4,200 duplicate holds are placed for one meal each — €38,000 of customers' money frozen, and 300 calls to the chain's support line and its customers' banks. The terminal vendor enables automatic reversals on timeout; the next unstable day produces 5,000 timeouts, 5,000 reversals within seconds, and no duplicate holds. The chain's acquirer also notes that the chain's scheme misuse fees — for authorisations it had never captured or reversed — fall to zero.

## Common mistakes

- No reversal on timeout, so every network blip is a double hold.
- Capturing less than the authorisation without a partial reversal.
- Using "reversal" for a refund in an integration, and sending a credit where a cancellation was meant.
- Reversing after capture, which the schemes reject; a refund is the operation then.
- Assuming the issuer releases the hold the moment the reversal is sent; some take days, and the support script should say so.

## Related terms

- [Void](https://mahouse.world/glossary/void.md)
- [Authorisation Hold](https://mahouse.world/glossary/authorisation-hold.md)
- [Authorisation and Capture](https://mahouse.world/glossary/authorisation-and-capture.md)
- [Refund](https://mahouse.world/glossary/refund.md)
- [Chargeback](https://mahouse.world/glossary/chargeback.md)
- [Transaction Lifecycle](https://mahouse.world/glossary/transaction-lifecycle.md)

— Ihor Vlasov, M&A FinTech Expert. Last reviewed 2026-09-20. https://mahouse.world/authors/ihor-vlasov