
Plenty of merchants check a new card the same way: run a $1 authorization, see whether it approves, then void it. It is quick, every gateway can do it, and it catches dead cards before the first real bill. Since 24 October 2026 it also breaks Visa's rules. The October 2026 edition of the Visa Core Rules and Visa Product and Service Rules prohibits an authorization for a non-zero amount when it is not a real purchase, is not meant to settle, and is there mainly to check that an account is valid or has funds.
The change lands hardest on businesses that keep cards on file: subscriptions and memberships, payment plans, account top-ups, and services billed after the work is done. Those are also the businesses most likely to be in a high-risk portfolio. This guide covers the new verification rule, what Visa requires before you store a card at all, how later charges have to be processed and labeled, and where card-on-file mistakes turn into disputes. It cites the Visa rules dated 24 October 2026. Mastercard runs a parallel framework of its own with different details, so confirm its requirements with your processor.
What changed on 24 October 2026
Visa added three connected rules in the October 2026 edition.
- No more non-zero verification. A merchant, acquirer or token requestor must not send an authorization request for a non-zero amount when all of these are true: it is not a bona fide purchase, it is not intended to proceed to clearing and settlement for that amount, and its main purpose is to verify an account's validity or status, or to assess whether funds are available. A $1 or $0.01 check that you void afterwards meets every condition.
- Zero-amount Account Verification is the tool. Visa defines an Account Verification as a message sent to the issuer for a currency unit of zero, to confirm a transaction can be completed using the card. A merchant that wants to verify an account must use one, and it cannot be used to start a purchase.
- Anticipated Amount Validation (AAV) is new. Where your acquirer supports it, a zero-amount Account Verification can carry an anticipated amount, and the issuer can say whether the account could cover it.
Visa also changed what issuers send back. An issuer may no longer answer a plain Account Verification with decline code 51, not sufficient funds, and must evaluate available funds only when an AAV request is received. If the account is valid but the anticipated amount exceeds the balance, the issuer may return a new code, Z5, valid account but amount not supported. Code 85, no reason to decline, means the account is valid but funds were not checked. Separately, Visa's rules tell issuers to decline an Account Verification for a recurring transaction on a non-reloadable prepaid card with code 57, transaction not permitted.
In practice: a $0 verification tells you a card is real and open. It no longer tells you whether there is money behind it unless you send an AAV, and a $1 authorization is no longer an allowed way to find out.
When you can use Anticipated Amount Validation
AAV is narrower than the $1 check it replaces. Visa requires a merchant that uses it to:
- Use it only for a cardholder-initiated transaction in a card-absent environment, meaning the customer is present online or on the phone, not a charge you start yourself later.
- Send a genuine estimate of a future transaction, not a probe.
- Tell cardholders that funds availability may be checked for an anticipated future amount.
- Send no more than 3 AAV requests per card number in any rolling 30-day period.
- Submit an authorization within 31 calendar days of an approved AAV.
- Not use it as a substitute for an authorization, or for repeated probing of a cardholder's balance.
Support depends on your gateway. Some processor documentation already lists an anticipated amount field on zero-amount authorizations, but do not assume yours sends it. Ask.
Before you store a card: the agreement Visa requires
Verification is the second step. The first is the customer's consent. Before a merchant stores a payment credential for future transactions, Visa requires the cardholder's express informed consent to an agreement that includes:
- A description of the goods or services and the total purchase price.
- Cancellation and refund policies.
- Where surcharging is permitted, acknowledgment of any surcharge and its disclosures.
- Your location and the address, email and phone number to contact you about the transactions.
- The last four digits of the card that will be charged, noting it may be updated over time.
- How the customer will be told about changes to the agreement.
- The transaction amount, or how it will be worked out, and the currency.
- How the stored card will be used.
- The timing and frequency of charges, or, for unscheduled charges, the event that will trigger one, such as a balance falling below a set amount.
- The expiration date of the agreement, if there is one, and the length of any trial, introductory or promotional period.
Two details catch merchants out. The terms for each transaction type must be clearly displayed when the customer consents and kept separate from your general terms and conditions, so a line buried in a terms-of-service link does not qualify. And you must keep the agreement for as long as it runs and produce it if the cardholder or the issuer asks in writing. Visa's general acceptance rules add one more: use a stored credential only as agreed with the cardholder.
The first transaction: authorize or verify, then store
Once the agreement is in place and before the first transaction, Visa requires one of two things: an authorization request for the transaction amount if you are charging now, or an Account Verification if no payment is due yet, as with a free trial or a card held against future usage. If that first authorization or verification is not approved, you must not store the card.
This is where the October change bites. A sign-up flow that saves the card after a $1 authorization and a void now does in two steps what the rules say to do in one, using a message the rules now prohibit. The compliant version is a $0 Account Verification, with an AAV attached if you need a funds check and your processor supports it.
Every later charge has to say what it is
Visa's rules sort stored-credential charges by who starts them and why. A cardholder-initiated transaction is one the customer starts, such as clicking pay with a saved card. Before processing it, you must validate the customer's identity, for example with a login and password. A merchant-initiated transaction is one you start under the agreement. For a series of charges on a stored card, Visa's rules define three kinds:
- Recurring: charges at fixed, regular intervals, no more than a year apart, such as monthly dues.
- Installment: a series of charges over a fixed period, no more than a year between them, paying for a single purchase.
- Unscheduled credential-on-file: a fixed or variable amount that does not fall on a scheduled date, such as an automatic top-up when a balance runs low.
Every stored-credential transaction must use POS entry mode 10, and recurring, installment and unscheduled charges must carry the matching indicator in the POS environment field, starting with the first authorization or verification. The authorization amount must not exceed the amount of that individual charge. Recurring and unscheduled charges must not include finance charges or interest.
The labels are not paperwork. Processor documentation ties correct coding to approval rates, and Visa Acceptance Solutions, Visa's own payment gateway business, says following the merchant-initiated framework supports higher authorization rates and is required to receive updated card details through its real-time account updater. Checkout.com told its merchants in February 2026 that Visa had introduced new assessments in November 2025 to enforce correct flagging of stored-credential transactions. Neither source gives an amount, so check your statement.
Each merchant-initiated charge also has to be linked back to the original consent through a transaction identifier that your gateway stores and resends. Gateways differ on which earlier transaction's identifier they reference, so this is a setting to confirm with your processor rather than something to build yourself.
When a stored-card charge declines
Visa's rule here is short and often missed. If an authorization for a merchant-initiated transaction on a stored credential is declined, you must notify the cardholder in writing and give them at least 7 calendar days to pay another way. Retrying on its own is not enough. How often you may retry is a separate set of limits, covered in our guide to Visa and Mastercard card retry rules.
Recurring charges carry extra duties
Recurring billing has requirements on top of everything above. You must offer a simple cancellation procedure, an online one if the customer signed up online, and state the fixed dates or intervals of the charges. At least 7 days before a recurring charge, you must notify the customer by email or another agreed method when a trial, introductory offer or promotional period is about to end, with the amount and date of the next charges and a link or other simple way to cancel online or by text message. Our guide to free trial and subscription billing rules covers those requirements alongside the FTC and state automatic-renewal laws.
How coding decides which disputes you face
Visa dispute condition 13.2, Cancelled Recurring Transaction, lets an issuer dispute a charge when the cardholder withdrew permission for a recurring transaction, or when the merchant was told before processing that the account was closed. The issuer has 120 calendar days from the processing date, and the dispute amount is limited to the unused portion of the service or merchandise.
Visa's rules list the cases where a 13.2 dispute is invalid, and they include an unscheduled credential-on-file transaction, a cardholder-initiated transaction, and outside Europe an installment transaction. That is why the indicator matters: it tells the issuer which rules apply to the charge. It is not a lever. The indicator has to match the agreement the customer actually accepted, and a monthly subscription labeled as unscheduled to dodge a cancellation dispute is a mislabeled transaction, not a defense. The agreement you kept is your evidence either way.
A card-on-file checklist for October 2026
- Find every place your systems send a non-zero authorization that is voided afterwards: sign-up, add-card, card update, trial start. Replace each with a zero-amount Account Verification.
- If you relied on the $1 check to screen for funds, ask your processor whether it supports Anticipated Amount Validation, and build within the limit of 3 per card in 30 days.
- Rewrite the save-card consent so it covers every item on Visa's list, displayed separately from general terms, and store a copy of what each customer agreed to.
- Do not save a card whose first authorization or verification declined.
- Confirm with your gateway that recurring, installment and unscheduled charges carry the correct indicators and transaction identifiers from the first transaction onward.
- Make sure a declined merchant-initiated charge triggers a written notice with at least 7 days to pay another way.
- Read your next statements for Visa integrity or stored-credential assessments. If they appear, they point to the flow that needs fixing.
Why it matters more on a high-risk account
Processors and acquiring banks watch high-risk portfolios closely, and stored-credential billing generates a steady stream of authorizations, declines and potential disputes for them to watch. A sign-up flow that still sends $1 checks, or a billing system that labels everything as recurring, is the kind of operational problem that shows up in an acquirer's reports before it shows up in yours. Getting the card-on-file setup right also helps your approval rates, which matters most for merchants who bill the same customers month after month.
PayKings places subscription, membership and payment-plan merchants with acquiring banks and gateways that support the stored-credential framework. Talk to our team if you are setting up card-on-file billing or want to check that your current setup meets Visa's October 2026 rules. Visa publishes a new edition of its rules twice a year, so confirm current requirements with your processor before you rebuild a payment flow around them.
Categories

Kyle Hall is a fintech entrepreneur, software engineer, and marketing strategist with over a decade of experience in high-risk payment processing and SaaS development. He is the CEO of PayKings, a lea...
More from Kyle Hall
Selling Ammo Online: Where a Shipping Address Isn't Enough
Ammunition is one of the few firearms products a business can sell without a federal firearms licens...
How to Sell Health Products Online: The Payments-First Guide
Most guides on how to sell health products online walk you through listing a product on a marketplac...
Remotely Created Checks Put the Loss on Your Bank, Then on You
A customer reads their routing and account numbers to you over the phone or types them into a form. ...
Online Money Making Methods: 12 Legitimate Ways to Earn in 2026
There are more legitimate ways to make money online in 2026 than ever — and more ways to lose months...