An AVS code is a one-letter result that tells you how closely the billing address a customer typed matches the address their card issuer has on file. A Y means the street and ZIP match. An N means neither matches. Letters like A, Z, U and R sit in between. The code is information for you to act on. It is not a verdict, and it is not the same thing as a decline code.
This guide covers what each common code means, why mismatches happen on good orders, how AVS differs from credit card decline codes, and a simple way to handle every result.
TL;DR
- AVS compares the billing address and ZIP from checkout with the issuer's records and returns a code with your authorization response.
- Y is a full match. A and Z are partial matches, N is no match, and U and R mean the check could not be completed.
- A mismatch is not proof of fraud. Typos, autofill and recent moves cause many of them.
- AVS codes and decline codes are different. One describes the address check. The other explains why the issuer refused the payment.
- Use AVS as one layer alongside CVV, 3D Secure and velocity checks, and set rules by risk, not by a single letter.
Table of Contents
- What AVS actually checks
- The common AVS response codes
- What an AVS mismatch really means
- AVS codes vs. credit card decline codes
- How to handle each AVS result
- Why AVS should never work alone
- Worked examples
- Is AVS required?
- Does AVS affect your fees?
- Put clearer AVS data to work with PaySec
- FAQ
- Sources
What AVS actually checks
AVS stands for Address Verification Service. It is built for card-not-present payments, such as online checkout, phone orders and keyed-in sales. According to the US Payments Forum, the merchant includes the AVS request as part of the authorization. The issuer replies with a full match, partial match or no match, and that AVS response travels inside the approval or decline message.
Two details are checked:
- The numeric part of the street address, such as the house number.
- The postal code, which in the U.S. is the ZIP code.
The issuer does not check the name, the city or the apartment label in the way a person would. It compares what it has on file for the cardholder's statement address with what your customer entered.
Mastercard describes the same flow: AVS compares the entered billing address and postal code with issuer records and returns a code for the merchant to interpret. The merchant, not the code alone, decides whether to approve or decline. That one idea shapes everything below.
If you are new to the difference between in-person and remote payments, our guide to card present vs card not present explains why AVS matters most when the card is not physically in front of you. For a refresher on the security basics around card data, this overview of PCI compliance basics is a handy companion.
The common AVS response codes
The standard domestic Visa codes, as listed in the Visa Acceptance AVS reference, are the ones you will see most often in U.S. processing. Visa Acceptance also notes that American Express AVS codes are converted to Visa AVS codes before they are returned.
| Code | What it means | Street | ZIP | Typical reading |
|---|---|---|---|---|
| Y | Street and 5-digit postal code match | Match | Match | Strongest result |
| A | Street matches, but 5- and 9-digit postal codes do not | Match | No match | Partial match |
| Z | Street does not match, but 5-digit postal code matches | No match | Match | Partial match |
| N | No match | No match | No match | Weakest result |
| U | Address information unavailable | Unknown | Unknown | Check not completed |
| R | System unavailable, retry | Unknown | Unknown | Check not completed |
Your gateway may show additional letters. Some cards return codes that say a nine-digit ZIP matched, or that mark an international card. The set of letters differs by card brand and by gateway, so keep the code list from your own processor's documentation next to your fraud rules.
Y: full match
The street number and ZIP agree with the issuer's records. This is the result you want to see. It lowers the odds that the buyer typed random details, but it does not prove the buyer is the real cardholder. More on that below.
A: street matches, ZIP does not
The number on the street lines up, but the ZIP is off. The usual causes are a mistyped ZIP, a ZIP4 or a nine-digit format the issuer reads differently, or a recent move within the same street name. This is a common result on legitimate orders.
Z: ZIP matches, street does not
The ZIP is right, but the street number is not. Typos, apartment numbers in the wrong field and abbreviations such as "Apt" versus "#" often produce Z. It also appears when a buyer uses a shipping address in the billing field.
N: no match
Neither element agrees. This is the code that deserves the most scrutiny, though even here a cardholder who just moved can produce it. Look at the rest of the order before you decide.
U and R: the check did not run
U means address information was not available. R means the system was unavailable and the request should be retried. Neither says anything about the buyer. Treat them as "no signal" and rely on your other checks. Many card-issuing banks outside the U.S. do not support AVS at all, which is why U is common on foreign cards.
What an AVS mismatch really means
An AVS mismatch means the billing address entered at checkout does not match the issuer's records. According to Secure Trust, a mismatch does not directly indicate wrongdoing. Common causes include formatting differences, outdated browser autofill and a recent move before the bank's records are updated.
From a merchant's seat, the most frequent reasons look like this:
- Autofill pulls the wrong address. A saved shipping address lands in the billing field.
- The cardholder moved. The bank still has the old address on file.
- Formatting differs. "Street" versus "St.", or a unit number in the wrong place.
- The ZIP is mistyped. One wrong digit is enough.
- A business card uses a different statement address. The shipping address is the office, but the card is billed elsewhere.
- A gift or third-party purchase. The buyer enters the recipient's address in the billing field.
This is why the code is a signal and not a decision. Blocking every non-Y order would turn away real customers. Accepting every order regardless would leave you without the layer the check was designed to provide.
AVS codes vs. credit card decline codes
Readers often search both topics together, so here is the clean difference.
| AVS response code | Decline code | |
|---|---|---|
| What it describes | How well the entered address matches the issuer's records | Why the issuer or network did not approve the payment |
| Format | Usually a single letter | Usually a two-digit or short numeric code with a text reason |
| Who decides the outcome | You, based on your rules | The issuer |
| Can an order with this result still be approved? | Yes | No, the payment was refused |
An AVS result can arrive with an approved authorization. A decline code arrives when the issuer refuses. The two can appear on the same transaction: the issuer may decline and your gateway may also show an AVS result next to it.
Hard declines and soft declines
Stanford's FinGate guide to card declines separates declines into two groups. Hard declines include an expired, lost or stolen card, insufficient funds or an invalid card number. Soft declines are temporary problems, such as a billing address or ZIP mismatch or a CVV mismatch. Per the same resource, soft declines can be resubmitted one or two days later, while hard declines should not be retried.
That gives you a practical rule for your team:
- Soft decline: ask the customer to correct the address or CVV, or to try again, or contact their bank.
- Hard decline: ask for a different payment method. Do not keep retrying the same card.
Codes such as 05 (do not honor) and 51 (insufficient funds) are familiar examples of issuer responses. The exact code set and wording differ between processors and card networks, so your processor's response-code table is the authority for your account.
Mastercard, Visa and other brands
Mastercard decline codes are not a separate language for you to learn. The issuer returns a response, the network carries it and your processor maps it into a reason you can read in your dashboard. What changes by brand is how AVS results are presented. As noted above, Amex results are converted into the Visa letter set, and your gateway may translate others. If you see a letter you do not recognize, look it up in your gateway's AVS table before you set a rule around it.
How to handle each AVS result
The right response depends on the code, the order value and the rest of the risk picture. Here is a practical starting framework.
Step 1: decide what you do with each code
| Result | Suggested handling |
|---|---|
| Y | Proceed, subject to your other checks |
| A or Z | Approve low-risk orders. Review higher-value orders, new customers and shipments to a different address |
| N | Review manually or ask the customer to re-enter details before fulfilling |
| U or R | Treat as no signal. Rely on CVV, 3D Secure and order behavior. Retry R if your gateway allows |
Step 2: add context before you decide
Look at the pieces together:
- Is the order value unusual for this customer or product?
- Does the shipping address differ from billing?
- Is it a first order with expedited shipping?
- Has the same card or device tried several times in a short window?
- Did the CVV also fail?
A single partial match on a repeat customer buying their usual item is a very different order from an N on a first-time, high-value purchase shipped to a freight forwarder.
Step 3: make it easy for good customers to fix the problem
Many mismatches are typos. Helpful checkout design reduces false alarms:
- Label the field "Billing address (as it appears on your card statement)."
- Use address autocomplete and standard formatting.
- Keep unit numbers in their own field.
- Show a clear error message that says what to check instead of a generic decline.
- Let the customer try again once before the order is lost.
Step 4: keep customers on file current
When a repeat customer's card was reissued or their address changed, stale details cause both AVS misses and declines. Tools that refresh stored credentials help. Our explainer on account updater services shows how merchants keep card-on-file data current, and our note on card-on-file consent covers how to avoid declines on stored credentials.
Why AVS should never work alone
The US Payments Forum stresses that AVS belongs inside a layered fraud solution and not as a standalone safeguard. The reason is simple. Fraudsters often have the cardholder's address along with the stolen card details, so a match alone is not enough proof that a transaction is legitimate.
A sturdy setup combines several signals:
- AVS for the address and ZIP check.
- CVV to confirm the buyer has the physical card details.
- 3D Secure for authenticating the cardholder on higher-risk orders. See our guides to 3D Secure authentication and 3D Secure 2.
- Velocity and device checks to catch repeated attempts.
- Manual review for the narrow set of orders that look unusual.
The same logic applies to voice and support channels, where payments are taken by phone. Teams that handle card data in a contact center can read about contact center security for regulated organizations to see how layered controls fit together there.
For a wider view, our comprehensive fraud protection guide walks through the full stack, and the piece on detecting fake credit card fraud shows warning signs that AVS alone will not catch.
Worked examples
Three short scenarios show how the codes read in practice.
Example 1: repeat customer, code Z. A returning customer orders a $45 item they buy every month. The ZIP matches, but the street number does not. They recently added an apartment number in the wrong field. The right move is to approve, since the history is good and the value is low.
Example 2: new customer, code N, high value. A first-time buyer places a large order with overnight shipping to an address in another state. Neither street nor ZIP matches, and the CVV also failed. Hold the order, ask the customer to confirm details and consider 3D Secure before shipping.

Example 3: code U on a foreign card. The check could not run because the issuer does not return address data. The code tells you nothing about the buyer. Use CVV, 3D Secure and your order rules instead.
Is AVS required?
AVS is a check the merchant requests as part of the authorization, as the US Payments Forum describes it. How it is applied is largely a matter of your gateway settings and your own risk rules: you decide whether to collect the billing address, whether to send it for verification and what to do with each result. Your processor can tell you which AVS options your account supports and how your gateway handles each code. Because rules and settings can differ by processor and card brand, confirm the details for your account with your provider.
Does AVS affect your fees?
AVS is not a fee line on its own, but the way you collect and verify payment data can influence how a transaction is classified. Card-not-present sales are priced differently from card-present ones, and clean data helps avoid declines and disputes that cost time and money. The payment reversal guide explains how to prevent and respond to disputes. Your merchant statement and processor can show exactly how your transactions are priced.
Our perspective on AVS
At PaySec, we treat AVS as a data point that works best inside a clear process. A letter on a screen should not decide whether a good customer gets served. We think merchants do best when they read the code, weigh the order and act with a rule they can explain.
That is why we pair address checks with fraud prevention tools, tokenization and real-time transaction reporting. When you can see every authorization, AVS result and decline reason in one place, you can tune your rules by what actually happens in your business, not by guesswork.
We also believe pricing should be as clear as the codes. Our Network Offset Pricing is designed to pass through wholesale interchange, with no hidden fees, no minimums and no long-term contracts, so you can see what each transaction costs. Our PCI DSS Level 1 and SOC 2 compliance supports the secure handling of the card data that AVS and other checks rely on.
Our approach is simple: show the data, keep the rules sensible and make payments easy for the customers you want.
PaySec Marketing Team
Put clearer AVS data to work with PaySec
If you want AVS results, decline reasons and fraud tools in one place, PaySec offers an eCommerce gateway, recurring billing, fraud prevention and detailed transaction reporting, with network offset and interchange-plus pricing, no monthly minimums and no contracts. Review the merchant services we offer, see how Network Offset Pricing works or explore pricing options. Restaurants, healthcare practices, online stores, SaaS marketplaces and CBD retailers can start from the PaySec home page.
Online stores can look at our eCommerce payment processing page for gateway and fraud prevention details.
FAQ
Why does it say AVS rejected?
It usually means the billing address or ZIP entered did not match the issuer's records, and your gateway or rules are set to refuse that result. Check for typos, a wrong ZIP or an autofilled shipping address. If the customer re-enters the details correctly, the order often goes through. If your settings are strict, review whether partial matches such as A and Z should be reviewed instead of blocked.
What does AVS check?
AVS compares the numeric part of the street address and the postal code that the customer entered with what the card issuer has on file. The issuer returns a code for a full match, partial match or no match. It does not check whether the person is the true cardholder.
What is the full form of AVS?
AVS stands for Address Verification Service. Some people also write Address Verification System. Both refer to the same check of the billing address on card-not-present payments.
What should I do with an AVS mismatch on a legitimate-looking order?
Look at the whole order first: customer history, order value, shipping address and CVV result. Many mismatches come from typos, autofill or a recent move. Ask the customer to confirm their billing address, then approve once the details line up and the rest of the order looks normal.
Are AVS codes the same as decline codes?
No. An AVS code describes how well the address matched. A decline code explains why the issuer refused the payment. A payment can be approved with a partial AVS match, while a decline code means the payment was refused.
Sources
- Address Verification Service (AVS), US Payments Forum
- AVS Codes, Visa Acceptance Developer Center
- AVS Mismatch: Why Your Customer's Card Got Declined, Secure Trust
- Credit and Debit Card Decline, Stanford FinGate
- Why Address Verification Matters for Payments, Mastercard
- PCI compliance basics
- Contact center security for regulated organizations

