An AVS mismatch happens when the billing address a customer enters at checkout does not match the address the card issuer has on file for that card. AVS stands for Address Verification Service, a fraud-prevention check used mainly for card-not-present payments such as online and phone orders.
When a card is processed, the gateway sends the numeric parts of the billing address and the ZIP or postal code to the card issuer. The issuer compares them to its records and returns an AVS response code. A full match, a partial match (street or ZIP only) and a no match are the three broad outcomes. An AVS mismatch meaning a partial or no match is not an automatic decline: your gateway settings decide whether the transaction goes through, is flagged for review, or is rejected.
AVS checks only the numbers in the street address and the ZIP or postal code, not the full text of the address. It is supported mainly for cards issued in the United States, Canada and the United Kingdom, so many international cards return a code saying AVS is unavailable rather than a true mismatch.
Many mismatches are honest mistakes rather than fraud. Common causes include customers typing a shipping address instead of the billing address, recently moved cardholders whose issuer has not updated their address, typos, apartment or suite formatting differences, and international cards from countries that do not support AVS. Fraudsters using stolen card data also produce mismatches, which is why the check exists.
Exact code letters can vary slightly by card network and processor, so always check your gateway documentation. These are the codes merchants see most often:
A partial match (A, Z or W) is usually a typo or a recent move. A no match (N) deserves a closer look, especially on a large or unusual order. Codes such as U, S, R and G are not mismatches at all, they simply mean the check could not be completed.
If your gateway is set to reject certain AVS responses, the payment is declined before it reaches the issuer for approval or immediately after the AVS result is returned. This protects against fraud but can cost you legitimate sales if the rules are too strict.
Ask the customer to re-enter the billing address exactly as it appears on their card statement. Check ZIP or postal code first, since it is the most common error. Confirm there are no extra characters, and try the format the bank uses for apartments and suites. For repeat customers, ask them to update their address with their bank. For phone orders, read the address back to the customer before submitting.
Review your AVS settings with your processor or gateway. Many merchants approve on a ZIP match and review other partial matches manually rather than auto-declining them. Pair AVS with CVV checks, 3D Secure and velocity rules so you do not rely on a single signal. Higher-risk or high-ticket orders deserve stricter rules than low-risk repeat purchases. Track which AVS codes cause the most declines so you can tune settings over time.
AVS is one of several checks, and each one catches a different problem:
Used together they work much better than any single check, which is why most fraud-prevention setups combine all three with velocity limits and order-value rules.
Every AVS rule trades protection against lost sales. Declining every mismatch blocks more fraud, but it also turns away honest customers who mistyped a ZIP or who just moved. Approving everything raises your fraud and chargeback exposure. A practical middle path is to approve a ZIP match with a CVV match, send other partial matches for review, and decline a no match only when the order is high value or has other warning signs. Review your decline reports monthly and adjust.
A matching AVS result helps show a transaction was authorized with correct cardholder information, which can support your case if the sale is later disputed. It does not by itself prevent a chargeback. Read our guides on chargeback representment and card-not-present fraud for the full picture, and see credit card processing fees explained to understand how declines and fraud tools fit into your costs.
It means the billing address or ZIP code provided at checkout does not match the issuer's records for that card.
No. Most mismatches come from typos, outdated addresses or formatting differences, though fraud is one possible cause.
No. Your gateway or processor settings determine whether to approve, review or decline based on the AVS code.
On a keyed or phone transaction, it means the address you entered did not match the issuer's records. Re-check the ZIP code and street number with the customer.
Yes, by tuning AVS rules and combining them with other fraud tools. Talk to your payment partner about settings that fit your business. See our high-risk payment solutions.
Often yes, since AVS rules are set by your gateway or processor. Turning it off removes a fraud signal, so most merchants keep AVS on and relax how they respond to partial matches instead.
Only in part. AVS is supported mainly for cards issued in the United States, Canada and the United Kingdom. Cards from other countries usually return a code saying AVS is unavailable, which is not the same as a mismatch.
Neither, usually. It is a data difference between what the buyer entered and what the bank has on file. The merchant controls only how strictly the result is treated.
Every merchant's processing setup is different, so the right answer depends on your industry, sales channels, average ticket size and chargeback history. CARDZ3N's payments specialists review those details with you and match your business with the right sponsor bank, gateway and risk tools, whether you sell online, in store, by invoice or on a recurring subscription.
We work with merchants across the USA, Canada, the UK and the EU, including high-risk, B2B and fast-growing businesses that traditional processors often turn away. If you would like a second opinion on your current rates, contract terms or approval options, contact our team for a free, no-obligation processing review.
Joshua Benedetti is the CEO of CARDZ3N, a Las Vegas-based merchant services provider specializing in high-risk payment processing and B2B payment technology.
Joshua Benedetti on LinkedInCARDZ3N Inc is headquartered in Las Vegas, Nevada, and provides merchant services to businesses that traditional processors turn away. Backed by top-tier sponsor banks and processors, CARDZ3N combines institutional stability with the speed of a specialized team that understands high-risk industries. Services include high-risk account underwriting and placement, gateway solutions across the major gateway platforms, POS integrations, ACH and check processing, chargeback prevention through ChargebackZ3N, and business lending and working capital. Its AerospacePay division serves OEMs, MROs, FBOs, and repair stations with B2B and B2G payment processing. CARDZ3N serves merchants in the USA, Canada, the UK, and the EU.
Start protecting your revenue from chargebacks today — schedule your complimentary consultation with CARDZ3N’s dispute management specialists.
