Zero Dollar Authorizations: How to Check a Card
Visa requires card checks to be for zero, not a dollar. And response code 85 is an approval, not a decline, which costs merchants real signups.
By Jeffrey Anderson
- Visa requires an account verification to be for a currency unit of zero and to not initiate a purchase. The common $1 test authorization is not the sanctioned mechanism.
- Response code 00 and response code 85 are both approvals. 85 means the issuer had no reason to decline but did not check the balance, and rejecting cards on 85 turns away valid customers.
- Issuers must validate the account number, confirm it is not reported lost or stolen, and may not approve or decline verification requests in a systematic or wholesale manner.
- An approved verification carries CVV, CVV2 and CAVV results back to you, with AVS and Account Name Inquiry results added from 24 October 2026.
- You must run one before storing a payment credential. If it is not approved, you are not permitted to store the card.
- From 25 July 2026 the cardholder data you send must come directly from the cardholder, and your merchant location and MCC must match the subsequent authorization.
Zero dollar authorizations are how you check a card is real without charging it. Visa calls the mechanism an Account Verification, and its rules are specific about the amount: it has to be zero.
That matters because the common workaround is a $1 authorization. Section 5.7.2.1 of the Visa Core Rules and Visa Product and Service Rules (18 April 2026) is direct about it.
The $1 Test Charge Is Not the Sanctioned Method
Here's the rule in full (ID# 0030934):
"A Merchant that chooses to verify the validity of an account must use an Account Verification. An Account Verification must both: be for a currency unit of zero, and not be used to initiate a purchase Transaction."
Two requirements, both absolute. The amount is zero, not one dollar, and the request cannot be the start of a purchase.
If your gateway runs a $1 auth to validate a card before storing it, that isn't an account verification under these rules. It's a small purchase authorization you intend to reverse, and it behaves like one: it can appear as a pending charge on the cardholder's statement, it can prompt a "what is this?" call, and in a thin-margin or prepaid situation it can fail for reasons that have nothing to do with whether the card is valid.
Ask your provider which one you're actually sending. A lot of older integrations default to the dollar.
Two Response Codes That Both Mean Yes
This is the part that trips up fraud rules built on the wrong assumption.
Visa requires issuers to respond with descriptive codes, and there are two distinct approvals (section 7.3.10.1):
- 00, Approval. Returned when the account has a balance greater than zero.
- 85, No reason to decline. Returned when the issuer has not checked the account balance.
Both are successful verifications. An 85 is not a soft decline and not a warning. It means the issuer looked at the account, found nothing wrong, and simply didn't check funds, which is what you'd expect on a zero amount request.
Treating 85 as a failure is a self-inflicted decline. If your onboarding flow rejects cards on anything other than 00, you're turning away valid customers.
For anything that isn't approved, the issuer must return a decline code indicating the primary reason.
Issuers Cannot Rubber-Stamp Them
An obligation sits on the issuer side that's worth knowing exists, because it shapes what a verification result actually tells you.
Issuers must receive and respond to zero-amount account verification requests, validate that the account number is valid and has not been reported lost or stolen, and, in the rules' own words, "not approve or decline Account Verification requests in a systematic or wholesale manner."
That last clause means the response is meant to reflect a real check on that specific account. It's a weak signal, but it isn't a meaningless one.
What Comes Back With the Verification
On an approved account verification, the issuer must provide the validation results the acquirer asked for, including the Card Verification Value, CVV2, and the Cardholder Authentication Verification Value.
Two more join that list on 24 October 2026: Address Verification Service results and Account Name Inquiry results. Until then AVS results are provided under the existing regional arrangement, which covers the US, Canada, the UK, and parts of Asia Pacific.
So a zero dollar authorization isn't only a yes or no on the card. It's a carrier for the verification data you'd otherwise have to collect at purchase time, which is why it's the right tool at signup rather than a token charge.
When You Are Required to Use One
The rules require account verification in two situations: when a merchant stores a payment credential, and when a merchant validates an account separately from a purchase.
The first is the one with teeth. Under the stored credential rules, you must run either an authorization for the transaction amount or an account verification before storing a card, and if it isn't approved you're not permitted to store the credential at all.
So the zero dollar authorization is the mechanism for a free trial, a saved card at checkout, or any arrangement where you're keeping the card but not charging it today.
Two Changes Landing on 25 July 2026
Acquirer obligations tighten this summer, and both affect what your systems send.
From 25 July 2026, when performing account name inquiry or AVS checks, acquirers must send genuine cardholder name and address data that the merchant obtained directly from the cardholder. Auto-filled or inferred data stops being acceptable.
From the same date, the merchant information in account verification requests, including merchant location and MCC, must be consistent with the subsequent authorization data. If your verification request and your later charge disagree about who or where you are, that's now a compliance problem rather than an untidy log.
One Prepaid Exception
For a non-reloadable prepaid card, the issuer must decline an account verification request for a recurring transaction with response code 57, transaction not permitted.
That's not a card problem you can retry your way out of. If you sell subscriptions and see 57 on a verification, the card is structurally ineligible for the arrangement, and the right response is to ask for a different payment method rather than to keep trying.
Frequently Asked Questions
Does response code 85 mean the card was declined?
No. 85 means "no reason to decline", returned when the issuer hasn't checked the balance. It's a successful verification. Only an actual decline code indicates a failure.
When do I have to run an account verification?
When you store a payment credential for future use, and when you want to validate an account separately from a purchase. Storing a card whose verification wasn't approved is not permitted.
Can I use one to check a card before a large charge?
You can verify validity, but it won't tell you the charge will succeed. For a purchase whose final amount you don't yet know, an estimated authorization is the correct instrument, not an account verification.
What changes in October 2026?
From 24 October 2026, issuers must also return AVS and Account Name Inquiry results on approved account verifications, which widens the data a single zero dollar request gives you.
Storing cards or running free trials and not certain your verification step is set up the way the rules expect? Apply free and we'll check it, or talk to a specialist about your recurring billing flow.
Jeffrey Anderson, Merchant Placement Specialist
Merchant placement specialist at Gray Merchants. Jeffrey works directly with acquiring-bank underwriting teams across the firm’s 70+ banking relationships to place high-risk and hard-to-place businesses, structure multi-MID accounts, and keep flagged merchants processing. His writing draws on the placement files he works every week: what underwriters ask for, why accounts get declined, and what keeps an approved account open.