Skip to content
Card Networks ← All terms

Void

Definition

A void cancels an authorized transaction before capture, releasing the hold without any funds movement — the correct alternative to a refund pre-settlement.

A void is the cancellation of an authorized card transaction before it is captured and settled. When a transaction is voided, the authorization hold is released and no funds move — making a void fundamentally different from a refund, which reverses a completed transaction after funds have settled. Voids are typically processed same-day; the cardholder's available balance is restored quickly. Most payment gateways and PSPs support void via API for any authorized-but-uncaptured transaction within the authorization window.

Void is the cleanest way to cancel a transaction that hasn’t settled yet. Because no funds have moved, a void avoids the interchange cost, refund processing fees, and cardholder wait time associated with a full refund. Operators who understand the void window and build it into their returns and cancellation flows reduce operational overhead and improve the customer experience on cancelled orders.

Void vs. Refund

The distinction matters operationally:

VoidRefund
TimingBefore capture / settlementAfter settlement
Funds movementNone — hold releasedReversal transaction processed
Interchange costNoneTypically none on the refund itself, but the original transaction interchange was already paid
Processing timeImmediate (hold releases within hours to same-day)3–10 business days for cardholder credit
PSP feeUsually noneSometimes a refund processing fee

The window to void varies by acquirer and PSP implementation. Most support same-day voids up to the point of settlement batch processing. Some PSPs allow voids up to 24 hours after authorization; others only within the same business day.

Pre-Authorization and Void

Pre-authorization (pre-auth) flows generate the most void volume in practice. Hotels, car rental companies, and fuel merchants authorize an estimated amount at the start of a transaction and void or adjust at the end.

Hotel example: A hotel authorizes $500 at check-in. At check-out, the actual bill is $380. The hotel either:

  1. Captures $380 (partial capture) and releases the $120 hold via the capture adjustment, or
  2. Voids the $500 authorization entirely and runs a new $380 authorization and capture

The cardholder’s experience improves when the pre-auth hold is released promptly — especially for debit cards where the hold directly reduces available funds.

How to Void via API

Most PSPs expose a void endpoint:

  • Stripe: Cancel a PaymentIntent before capture with cancel action
  • Adyen: Send a /cancel request referencing the PSP reference
  • Checkout.com: POST to /payments/{id}/cancellations
  • Braintree: Transaction.void(transactionId)

The operation is idempotent — voiding an already-voided transaction returns a success response, not an error, on most platforms.

When Void Is Not Available

Void is not available if:

  • The transaction has already been captured and included in a settlement batch
  • The authorization has expired (scheme window elapsed)
  • The PSP does not support void for that payment method (some wallets and local payment methods do not support pre-auth / void flows)

In these cases, a refund is the only option. Monitoring authorization-to-capture timing in your operations prevents expired auths from forcing unnecessary refund flows.

Related terms