Auth Reversal vs. Void
When to use an auth reversal versus a void, and how they differ.
Both auth reversals and voids cancel an uncaptured authorization, but they apply in different situations and have different effects on the cardholder's account.
Auth reversal
An auth reversal cancels an authorization on the same business day it was created, before the authorization file settles with the network.
| Property | Value |
|---|---|
| When | Same day as authorization |
| Effect | Hold released immediately at the issuer |
| API endpoint | POST /v1/payments/{id}/void (Cresora routes automatically) |
| Use case | Customer changes order, authorization created in error |
Void
A void cancels an authorization that was created on a previous business day or has already settled in the authorization file.
| Property | Value |
|---|---|
| When | Next business day or later |
| Effect | Hold released in 1–5 business days (issuer-dependent) |
| API endpoint | POST /v1/payments/{id}/void (same endpoint) |
| Use case | Order cancelled after end of business day |
How to void or reverse
The API endpoint is the same — Cresora determines whether to issue an auth reversal or void based on timing:
POST https://api.cresoracommerce.com/v1/payments/{id}/void
Authorization: Bearer csk_test_xxxxxxxxxxxxResponse on success:
{
"id": "pay_xxxxxxxxxxxx",
"status": "voided",
"voided_at": "2026-05-29T14:00:00Z",
"reversal_type": "auth_reversal" // or "void"
}Timing matters for cardholders
The key practical difference for your customers:
- Auth reversal: the hold disappears from their account immediately or within hours
- Void: the hold may remain visible for 1–5 business days, even though the charge won't settle
For customer-initiated cancellations, setting expectations about void timing is important — especially for debit cards where the hold directly reduces available balance.
Process cancellations as early in the business day as possible to maximize the chance of an auth reversal (immediate hold release) rather than a next-day void.