Skip to content
Card Networks ← All terms

Void

Definition

A void requests cancellation of an uncaptured card payment; confirm the final provider state and do not assume the hold has already cleared.

A void is a provider's operation for cancelling or reversing a card payment before capture, where the payment method and current transaction state support it. The request may be asynchronous, and acceptance is not confirmation that the issuer has released the authorization hold. Once captured, use the provider's supported post-capture operation, such as a refund or reversal, according to the payment state.

Choose by payment state

“Void” is not a universal network operation name. Providers expose different endpoints and rules. For example, Adyen's online-payment cancellation guide covers payments that have not yet been captured; Adyen directs operators to use a reversal when capture status is uncertain. Stripe documents capturing an uncaptured PaymentIntent and its default cancellation window in the PaymentIntent capture API. Check the provider's current API and payment-method support before acting.

If a cancellation request times out or returns an intermediate result, retrieve or await the provider's final payment status before retrying or issuing a refund. A request being received does not prove that the hold is released. The issuing bank controls when the cardholder's available balance reflects the release.

Example: an order is cancelled while its payment is authorized but uncaptured. Submit the provider's supported cancellation, then confirm the resulting state or webhook. If the payment is already captured, follow the provider's refund or reversal process instead; do not send a second charge operation because the first request's response was delayed.

See authorization, capture, and settlement for the state/action table and confirmation signals.

Related terms