What Is Void? Definition, Payment Flow, and Examples
Void cancels a transaction before capture or settlement is completed and differs from refunding a posted transaction. This guide focuses on Void's real role, boundaries, and common points of confusion.
Key points
- Definition: Void cancels a transaction before capture or settlement is completed and differs from refunding a posted transaction.
- Flow position: After authorization, a merchant may capture according to order status or void before capture.
- Do not confuse: Void / Authorization Reversal
How it fits into the payment flow
For Void, the relevant process is as follows: After authorization, a merchant may capture according to order status or void before capture. Clearing exchanges transaction detail and determines positions; settlement moves funds between participants. A refund is a later credit, while pending and posted describe account-facing states.
A practical review of Void should account for this: order systems, merchant dashboards, and banking apps can update at different times. Preserve the original transaction identifiers and check the formal statement instead of treating a push notification as final accounting.
Practical example
An order is canceled before capture, so the merchant voids the original transaction instead of creating a refund. Processing closes the unfinished payment and keeps it out of clearing.
How it differs from related terms
| Term | Definition |
|---|---|
| Void | cancels a transaction before capture or settlement is completed and differs from refunding a posted transaction |
| Authorization Reversal | tells the issuer to release an authorization hold that is no longer needed because of cancellation, timeout, or amount change |
| Refund | is a merchant-initiated return of all or part of an original payment and is not the same as a cardholder chargeback |
Void focuses on the fact that it cancels a transaction before capture or settlement is completed and differs from refunding a posted transaction. Authorization Reversal, by contrast, tells the issuer to release an authorization hold that is no longer needed because of cancellation, timeout, or amount change. They can appear in one transaction while answering different questions.
Use cases and limits
A key limit of Void is the following: void and refund apply at different stages. An uncaptured transaction commonly calls for a void, while a processed transaction may require a refund. Using the wrong operation can cause duplication, delay, or reconciliation gaps.
Frequently asked questions
These answers address two common search questions about Void.
Is it the same as Authorization Reversal?
No. Void cancels a transaction before capture or settlement is completed and differs from refunding a posted transaction. Authorization Reversal tells the issuer to release an authorization hold that is no longer needed because of cancellation, timeout, or amount change. Compare the object, processing stage, and responsible party.
Are a refund and a void the same operation?
For Void, no. A void commonly applies before capture is complete, while a refund credits a transaction that has already been processed. Interfaces and timing vary by processor and network.
These primary sources support the definition and process for Void. Current product, network, and local rules still control a real transaction.