Visa Banned the $1 Card Test: What to Use Instead
Visa now prohibits non-zero test authorizations. Here is the three-part test, plus the new funds check that replaces it and its three-per-30-days cap.
By Jeffrey Anderson

- Effective 24 October 2026, Section 7.3.10.4 (ID# 0031264) prohibits a non-zero authorization request when all three apply: it is not a bona fide purchase, it is not intended to clear for that amount, and its primary purpose is verifying the account or assessing funds. Chile follows on 2 November 2026.
- Account Verification is unchanged for validity checks: a currency unit of zero, and it must not initiate a purchase (ID# 0030934).
- Anticipated Amount Validation is the new way to ask about funds. It travels inside an Account Verification message, so it is still a zero amount request carrying an estimate (ID# 0031263).
- AAV is capped at 3 requests per card account number in any rolling 30 calendar day period, and an approved AAV must be followed by an authorization within 31 calendar days (ID# 0031262).
- AAV is card-absent and cardholder-initiated only, requires cardholder notice, and must not be used for repeated balance probing.
- New response code Z5 means valid account but amount not supported. It is a successful verification reporting an insufficient balance for the anticipated amount, not a decline.
- Issuers must not return decline code 51 on an account verification any more, and must evaluate available funds only when an AAV is received (ID# 0031047).
- An approved account verification response must represent a point-in-time assessment only and must not reserve, block or hold funds, so a funds check through AAV does not put a hold on the card.
Visa now prohibits the non-zero test authorization. Effective 24 October 2026, Section 7.3.10.4 of the Visa Core Rules and Visa Product and Service Rules (ID# 0031264) says an acquirer, merchant or token requestor "must not submit an Authorization Request for a non-zero amount" when the purpose is checking an account rather than selling something. In the LAC Region, Chile follows on 2 November 2026.
That closes the gap the $1 auth lived in. The old rule said an account verification has to be for zero. It did not say you were barred from sending a dollar instead. Now it does.
Visa also gave you something in exchange, which is the part most coverage will miss. There is a new sanctioned way to ask whether the money is there.
The Prohibition Has a Three-Part Test
All three conditions have to apply before the ban bites:
| Condition | What it means |
|---|---|
| Not a bona fide purchase of goods or services | You aren't actually selling anything with this request |
| Not intended to proceed to clearing and settlement for the submitted amount | You plan to reverse it, or let it fall off |
| The primary purpose is to verify account validity or status, or to assess funds availability | The request exists to tell you something, not to take money |
Read the conjunction carefully. A real $7.40 sale that happens to confirm the card works is untouched, because the first two conditions fail. A $1 request you intend to void, sent to find out whether a stored card still lives, meets all three.
Zero for Validity, AAV for Funds
Before this edition there was one tool. Now there are two, and they answer different questions.
| Question | Tool | Amount |
|---|---|---|
| Is this account valid? | Account Verification | Zero |
| Does this account hold at least X right now? | Anticipated Amount Validation | Zero, carrying an estimate of X |
Account Verification is unchanged and still the route for validity. Section 5.7.2.1 (ID# 0030934) requires it to be for a currency unit of zero and not to initiate a purchase, which is covered in our piece on zero dollar authorizations. The same section now adds that a merchant may use an AAV to find out whether an account is valid and holds enough for a specific future amount.
Anticipated Amount Validation is new. The glossary defines it (ID# 0031263) this way: "A message sent by an Acquirer to an Issuer, containing a genuine estimate of the amount associated with a future Transaction to assess whether a Cardholder has at least that amount of funds available at that point-in-time."
Note where it travels. An AAV rides inside an Account Verification message. It is still a zero amount request. The estimate is data in the message, not money you are asking for.
Nothing gets reserved either. Section 7.3.10.1 says an approved account verification response code must do both of the following:
- "Represent a point-in-time assessment only"
- "Not reserve, block, or hold funds on the Cardholder's account if and when available funds are checked"
So a funds check answers a question about a moment and leaves the balance alone.
AAV Comes With Hard Limits
Section 7.3.10.3 (ID# 0031262) puts seven requirements on a merchant whose acquirer supports AAV. Two of them are numeric, and those are the ones that will break a naive integration.
| Requirement | Detail |
|---|---|
| Card-absent only | Only if the transaction is cardholder-initiated in a card-absent environment |
| Genuine estimate | The amount must reflect a real estimate of a future transaction |
| Cardholder notice | You must notify cardholders that funds availability may be assessed for an anticipated future amount |
| Frequency cap | No more than 3 AAV requests per card account number in any rolling 30 calendar day period |
| Follow-through window | Submit an authorization within 31 calendar days of an approved AAV |
| Not a substitute | AAV does not replace an authorization |
| No probing | No repeated probing of a cardholder's balance, and no behaviour inconsistent with reasonable transaction needs |
Three per card per thirty days is a tight budget. If your checkout calls a funds check on every cart view, or your retry logic re-checks before each attempt, you will blow through it. The cap is per card account number, not per customer and not per order.
The 31 day follow-through is the other trap. An approved AAV that never turns into an authorization is a rule breach, not just a wasted call. If you are checking funds for something that may never be bought, you are using the wrong tool.
Issuers Got New Rules In the Same Edition
Section 7.3.10.1 (ID# 0031047) changed on the issuer side, and three parts of it affect what you see in the response.
A new response code arrived. Z5 means "valid account but amount not supported", returned when the issuer has confirmed the account is valid but the balance does not cover the anticipated amount. That is a successful verification carrying bad news about the balance, and treating it as a decline would be wrong.
Decline code 51 is now off limits here. An issuer "must not use Decline Response code 51 (Not sufficient funds) when responding to an Account Verification request". Issuers must evaluate available funds only when an AAV request is received. So a plain account verification can no longer come back as insufficient funds, which removes a long-standing ambiguity in how those responses were read. Our guide to decline codes and retry limits covers what the response codes oblige you to do.
Non-reloadable prepaid cards get their own answer. For one of those, an issuer must decline an Account Verification request for a recurring transaction with code 57, transaction not permitted. That is structural, not transient, and it lines up with what we cover on prepaid cards and partial authorization.
If You Store Cards, Check Your Gateway
The practical exposure is in code nobody has looked at for years.
Any routine that sends a small amount to test a card is now prohibited rather than merely unsanctioned. That includes a validation step before storing a credential, a periodic liveness check on cards on file, and a pre-flight check before a retry. Each one needs to become either a zero amount account verification or, if you genuinely need the funds answer, an AAV inside the caps.
If your real problem is that the final amount is unknown rather than that you doubt the card, neither tool is the answer. That is what an estimated authorization is for, which we cover in estimated and incremental authorizations.
FAQ
Does an AAV place a hold on the cardholder's funds?
No, and the rules say so directly. Section 7.3.10.1 requires an approved account verification response code to represent a point-in-time assessment only, and not to reserve, block or hold funds on the cardholder's account if and when available funds are checked. The amount is zero and the estimate is information in the message. It is also explicitly not a substitute for an authorization.
How many times can I check funds on the same card?
Three AAV requests per card account number in any rolling 30 calendar day period. The cap is on the card account number, so multiple orders or multiple customers on the same card share the same budget.
What happens if an approved AAV never becomes a sale?
The rule requires an authorization within 31 calendar days of an approved AAV. There is no carve-out for an abandoned cart, so do not use AAV speculatively.
What is response code Z5?
Valid account but amount not supported. The issuer has verified the account is valid and confirmed the balance does not have sufficient funds for the anticipated amount requested. It is specific to AAV.
Can I still get code 51 on an account verification?
No. From 24 October 2026 an issuer must not return 51 on an account verification, and must evaluate funds only on an AAV.
Does this apply in the US?
Yes. Visa lists the change as Global or Multi-Regional in its Summary of Changes, and the rules carry no regional qualifier beyond one footnote moving Chile to 2 November 2026.
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.