The short answer
An authorization reversal (sometimes called "auth void" or "reversal") is a message sent from merchant → acquirer → issuer canceling a previously-granted authorization. The issuer immediately releases the hold on the cardholder's available balance. The cardholder sees the pending charge disappear from their statement within hours (often minutes), rather than waiting 1-7 days for the auth to naturally expire. Auth reversals cost you nothing extra and are universally better UX than expiration. Running them consistently is a small ops discipline with outsized customer-experience returns.
When to send an auth reversal
- Order canceled. Customer changes their mind pre-ship. Reverse the auth, no capture.
- Out of stock. You can't fulfill the order. Reverse the auth, refund any portion captured.
- Fraud detected post-auth. Fraud team reviews, flags, reverses before capture.
- Partial capture scenarios. Authed $100, only shipped $80. Capture $80 (which is itself a partial auth capture), then reverse the remaining $20.
- Auth-only for card validation. You ran a $1 pre-auth just to validate — reverse immediately. (Better pattern: use zero-auth instead.)
- Duplicate auth cleanup. Customer's double-click generated two auths. Reverse the duplicate.
Auth reversal vs. void vs. refund — the difference
- Auth reversal: Before capture. No money ever moved. Cleanest undo. Issuer-side.
- Void: Some gateways use "void" to mean auth reversal; others use it for "cancel a transaction that's captured but not settled." Terminology varies.
- Refund: After capture/settlement. Real money moves back. Incurs refund fees. See no-charge refund for edge cases.
What operators need to know
- Reversals are free at most gateways. Refunds usually cost $0.15-$0.50 each; reversals are typically included in the auth fee. Use them.
- Latency reduces support load. A customer who sees their $200 hold released in 10 minutes doesn't call support. A customer who sees it for 5 days does. ROI on building reversal automation is high.
- Partial reversals are supported. You can reverse part of an auth without canceling the whole thing. Needed when you capture less than you authed.
- Timing matters. Reversals work only before capture. Once the capture is submitted and batch-settled, you're in refund territory.
- Some issuers honor reversals faster than others. Most release holds in minutes; a handful of smaller credit unions take hours or up to 24. Customer-facing messaging should say "up to 24 hours."
- Logging for reconciliation. Every reversal should carry the original auth's transaction ID. Accounting systems that match transactions by amount will miss reversals that don't carry the link.
- Don't confuse with chargeback reversals. A chargeback reversal (from representment) is a different mechanism entirely — network-initiated, post-dispute, different message type.