Zero-value authorization
What is zero-value authorization?
Zero-value authorization, also known as zero-amount or zero-dollar authorization, is a card validation check that sends a $0 (or small, immediately reversed) authorization request to confirm a payment card is active and the account is open, without deducting or holding any funds.
During a zero-value authorization, no money moves from the 's account. The issuer simply confirms that the card number and expiry are valid, the account is open, and the card can accept a charge later. Merchants run this check before storing a card on file, starting a subscription, or reserving a service, so they know the payment method is legitimate before any real and charge take place.
Key facts
- Also known as: zero-amount authorization, zero-dollar authorization, $0 authorization, account verification
- Amount: $0, or a small nominal amount (such as $1) that is authorized and then immediately reversed
- Funds impact: nothing is captured; with the nominal-amount variant, any temporary hold is released right away
- Common use cases: saving a card on file, setting up recurring billing or subscriptions, validating a card at signup, card tokenization
- What it confirms: the card is active, the account is open, and the card details match the issuer's records
- Result: an approval or a from the issuer, with no charge to the cardholder
How zero-value authorization works
- Request initiated: The merchant or its payment processor sends an authorization request to the card network with the amount set to zero, or to a small nominal value where a true $0 request isn't supported.
- Issuer check: The receives the request and verifies that the card number and expiry are valid, the account is open, and the card is in good standing.
- Address and security-code checks: The request can include AVS (address) and CVV (security-code) verification to confirm the cardholder's details match the issuer's records.
- Response returned: The issuer returns an approval or a decline code, signalling whether the card can be charged later.
- No settlement: Because the amount is zero, there's nothing to capture or settle. Any nominal hold is reversed, and the validated card, often stored as a token, is kept on file for future charges.
Why it matters
Zero-value authorization lets merchants confirm a card works before they rely on it. For subscription and card-on-file businesses, it prevents a common failure: storing a card that's already expired or closed, then watching the first real charge decline.
- Cleaner card-on-file data: validating a card at signup keeps invalid cards out of the vault, so recurring charges run against cards the issuer has already confirmed are active.
- Fraud screening: pairing the check with AVS and CVV verification helps catch stolen card numbers where the attacker doesn't have the matching address or security code, blocking before any money is at stake.
- No cost to the cardholder: because no funds are captured, the cardholder isn't charged and doesn't see a pending hold tying up their balance for a check.
Common issues
- Not supported everywhere: some issuers and networks don't process a true $0 authorization, so processors fall back to a small nominal amount that's authorized and then reversed.
- Visible nominal holds: when the nominal-amount variant is used, the cardholder may briefly see a pending charge before it's released, which can prompt support questions.
- Validity now isn't funds later: a zero-value authorization confirms only that the card is valid at that moment; it doesn't guarantee funds will be available when the real charge runs.
- Declines still happen: a zero-value request can return a decline code for reasons such as an inactive card or issuer restrictions, which should be resolved before the card is stored.
