Address Verification Service (AVS): Codes and Rules
Payments Glossary

What Is an Address Verification Service (AVS)? Codes, Fees and Fraud

How address verification service (AVS) works, what each code means, how it affects interchange, and when a mismatch deserves review instead of a decline.

Close-up of two businesspeople in dark suits shaking hands against a blurred bright office background

Photo: Pixabay

On this page 6 sections
  1. How an Address Verification Service Check Works
  2. AVS Codes: What Matched, and What Your Gateway Does by Default
  3. AVS and Interchange: Sending the Request Is What Qualifies
  4. Worked Example: When Shipping a Partial Match Pays
  5. Setting AVS Rules That Don't Turn Away Good Buyers
  6. What a Full AVS Match Doesn't Prove

Key takeaways

  • Many lower card-not-present interchange categories require you to send an AVS request, not to get a match, so blank address fields can cost more than a Z or an N.
  • Authorize.net rejects B, E, G, N, R, S and U by default, which can quietly block foreign cards on G, U and S.
  • Your break-even fraud rate is profit ÷ (profit + loss on a fraudulent order). Compare it with your own dispute history for each AVS code before you auto-decline.

An address verification service (AVS) check compares the numbers in the billing address a customer gives you, meaning the street number and the ZIP code, with the address the card issuer has on file. The issuer sends back a one-letter code that says what matched. AVS runs on card-not-present sales: online checkouts, phone orders keyed into a virtual terminal, and mail orders. It never approves or declines a sale by itself. The issuer makes the authorization decision, and your gateway settings decide what happens to the code.

That last part matters, because your gateway may already be declining sales on AVS results you've never looked at. Treat every mismatch as fraud and you turn away good customers. Ignore the code and you absorb fraud you could have caught.

How an Address Verification Service Check Works

A customer checks out on your Shopify store, or your office manager keys a client's card into a virtual terminal for phone and invoice payments. The billing address travels with the authorization request through the card network to the issuing bank. The bank returns its approval decision and the AVS result together.

Only the numbers get compared. Worldpay's merchant guide to AVS describes it as a numeric check of the street number and ZIP code, and Chargebacks911's AVS guide adds that box numbers count as numeric values too. So "St." versus "Street" doesn't cause a mismatch, but a transposed house number does. North Carolina's state merchant card program guidance notes that when a street line holds several numbers, they must appear in the correct order. Most real mismatches come from customers typing a shipping or work address, or one they left years ago. That's why Worldpay advises asking for the billing address as it appears on the customer's monthly statement.

Coverage outside the U.S. is thinner. Visa's AVS standard has separate domestic and international code sets, and the international code G means the issuer doesn't participate in AVS. If you sell abroad, expect some foreign cards to come back with no usable answer.

AVS Codes: What Matched, and What Your Gateway Does by Default

The table below uses Visa's domestic AVS codes as published by Visa Acceptance Solutions and Nuvei, plus B, which is a gateway code. The third column shows which codes Authorize.net rejects out of the box: B, E, G, N, R, S and U. Other gateways set different defaults, so check yours.

CodeWhat it meansAuthorize.net defaultReasonable handling
YStreet number and 5-digit ZIP matchAcceptApprove unless other signals look bad
XStreet number and 9-digit ZIP matchAcceptApprove unless other signals look bad
AStreet number matches, ZIP doesn'tAcceptApprove if CVV matches; review large orders
Z5-digit ZIP matches, street number doesn'tAcceptApprove if CVV matches; review large orders
W9-digit ZIP matches, street number doesn'tAcceptApprove if CVV matches; review large orders
NNeither matchesRejectReview; decline if CVV also fails
UAddress information unavailableRejectDecide on other signals
SIssuer doesn't support AVSRejectDecide on other signals
GNon-U.S. issuer that doesn't support AVSRejectDecide on other signals
RAVS system unavailable; retryRejectLet the customer retry, or decide on other signals
EAVS error, or AVS not allowed for the card typeRejectDecide on other signals
BNo address information was sentRejectFix your checkout or terminal fields

Non-U.S. Visa cards can return international codes (B, C, D, G, I, M and P), and in that set D and M signal a full match. B there means the street address matched only. It doesn't mean "no address sent," as it does in Authorize.net's list. American Express has its own letters (F, H, K, L, O, T and V) and can return Visa-style codes too. Your gateway's documentation is the final word on each letter.

Read every code next to the CVV result that comes back on the same response. A Z with a CVV match is a very different order from an N with a CVV mismatch.

AVS and Interchange: Sending the Request Is What Qualifies

AVS also changes what you pay. Interchange is the fee the card issuer collects on each sale. The networks set it in published rate tables, and the lower-cost card-not-present categories come with data requirements. For Visa consumer credit, the CPS/Card Not Present program requires AVS, according to CardFellow's breakdown of the program. Our explainer on how interchange fees are set covers the mechanics.

Here's the part merchants often get wrong: where AVS is required, the requirement is to send the request, not to get a match. The Visa and Mastercard interchange qualification matrix published by North Carolina's state controller lists the requirement as "AVS request in authorization." A Z or an N shouldn't cost you the rate, but leaving the address fields blank can. Helcim's summary of the October 2023 network changes says missing AVS is a cause of "many downgraded (higher) rates."

The requirements also differ by card type, so "AVS is required for card-not-present rates" is only mostly true. A Visa interchange fee schedule posted by Florida's Department of Financial Services says AVS isn't required for some of its debit card-not-present programs, and separately notes that business cards require it. North Carolina's guidance warns agencies on its Discover contract that Discover requires AVS on every card-not-present sale or charges an additional fee. If you send AVS on every keyed and online sale, you don't have to track which cards need it.

The cost of the check itself changed too. Helcim reports that in October 2023 Visa added a 0.0075% fee on card-not-present settled transactions and stopped charging separately for AVS and CVV2 checks. Those are network rules and fees. Anything your processor adds on top is its own pricing, so ask for current terms in writing.

Keyed sales are where AVS data most often goes missing. Someone takes a card by phone, types the number and expiration date, and skips the address. Your pricing model decides whether you see that downgrade directly. On a tiered statement the sale can land on a "non-qualified" line, and on interchange-plus it shows up as a costlier interchange category. On flat-rate pricing it's built into the processor's rate, so you won't see it on the statement. Whatever your pricing, make street number and ZIP required fields in your virtual terminal. Our guide to card-not-present transaction risks and rates explains why keyed and online sales cost more than tapped ones to begin with.

Worked Example: When Shipping a Partial Match Pays

Every figure in this example is illustrative, not a benchmark. Swap in your own.

A WooCommerce store selling outdoor gear gets a $180 order. AVS returns Z: the ZIP matched, but the street number didn't. The CVV matched, and the shipping address is in the same city as the billing address. Assumptions:

  • The product costs the store $108.
  • Shipping, paid by the store, costs $12.
  • The processor charges a $20 chargeback fee (yours may differ).
  • Processing fees are left out to keep the math simple.

A legitimate order earns $180 − $108 − $12 = $60. A fraudulent one gets disputed and the $180 is pulled back. The store loses the product, the shipping and the chargeback fee: $108 + $12 + $20 = $140.

The break-even fraud rate is profit ÷ (profit + loss): 60 ÷ (60 + 140) = 30%. Unless close to a third of orders with this profile turn out to be fraud, shipping them makes money. A good customer who gets declined may also never come back.

Now change the inputs. Take a $900 order for electronics that resell easily, with a product cost of $810, $20 shipping and the same $20 chargeback fee. Profit on a good order is $70, and the loss on a bad one is $850. Break-even falls to 70 ÷ 920, about 7.6%. The AVS code is the same, but the decision is very different. At that margin, manual review on partial matches starts to pay for itself.

Pull your dispute history for orders with the same AVS code and CVV result. Then compare the fraud rate you actually saw with your break-even line.

Setting AVS Rules That Don't Turn Away Good Buyers

Start by finding out what your gateway already does. Under Authorize.net's defaults, every G, U and S response is rejected, so many foreign cards never get a chance. Its help article notes you can unselect those codes to accept international cards. The Mastercard Gateway's AVS settings let a merchant choose, code by code, whether to process the payment, reject it, or hold it for manual review. If you use Authorize.net with MannyPay or another gateway, the setting lives in the merchant interface.

A workable starting point:

  1. Pass full matches (Y and X) unless something else about the order looks wrong.
  2. Approve partial matches (A, Z, W) when the CVV matches, and send large or easily resold orders to review.
  3. Review full mismatches (N). Decline automatically only when the CVV fails too or the order carries other red flags, such as rush shipping to a freight forwarder or several cards tried in a row.
  4. Judge the no-data codes (U, S, G, E) on everything else you know, because they say nothing about fraud either way.
  5. Treat R as a system problem, not a customer problem, and give the buyer a clear way to retry.

Strict filters have a side effect. When a gateway rejects a sale for an AVS mismatch, the issuer may already have approved the authorization. The gateway voids it, but depending on the bank, the shopper can still see a pending charge for a while. A shopper who mistyped a ZIP and retried may see several holds and decide your store is broken. Our guide to why good customers get falsely declined covers that cost in more detail.

Your checkout form causes many mismatches. Label the field "Billing address (as it appears on your card statement)," keep billing and shipping separate, and accept a 9-digit ZIP without requiring one. Legitimate customers fail AVS for ordinary reasons: a recent move the bank doesn't know about, a corporate card billed to headquarters, a prepaid or gift card with no registered address, a military or overseas address, a student on a parent's card.

What a Full AVS Match Doesn't Prove

A Y tells you the person at checkout knows the billing address. It doesn't tell you they're the cardholder. Stolen card data is often sold with the billing address attached, so a fraudster with full details passes AVS cleanly. AVS also ignores the shipping address, which is where your goods actually go. Worldpay's guide is direct about this: a full match reduces chargeback risk but doesn't eliminate it.

A match on its own won't win a fraud dispute. It is still useful evidence, alongside delivery confirmation and order history, when you fight a chargeback through representment. 3-D Secure authentication works differently: the issuer authenticates the cardholder, which can move liability for certain fraud disputes to the issuer. Whether that's worth the extra checkout step is a trade-off we cover in 3D Secure at checkout: fraud shield or conversion killer.

AVS filters also do little against card testing, where bots run many small authorizations to find live card numbers. Each attempt still reaches the issuer and still costs you an authorization fee. Rate limits and velocity rules do that job.

This week, export the last few months of AVS-rejected transactions from your gateway. Count how many were followed by a successful retry or a customer email asking what went wrong, and how many came from foreign cards rejected on G, U or S. If those numbers aren't small, your filters are costing you real buyers. If your current setup won't let you set rules by code, MannyPay can review your online payment gateways and integrations. A free quote request gets a reply from a specialist within one business day.

Sources

  1. Visa Acceptance Solutions: Understanding Address Verification Service (AVS) Result Codes
  2. Nuvei (Paya): Visa AVS Codes
  3. Authorize.net: What Is Address Verification Service (AVS) and How to Use and Configure It
  4. Mastercard Gateway: Address Verification Service
  5. Worldpay: Credit Card Address Verification Service
  6. Chargebacks911: Address Verification Service Complete Guide for Merchants
  7. North Carolina Office of the State Controller: Fraud Detection Services for Card-Not-Present Transactions
  8. North Carolina Office of the State Controller: Interchange Qualification Matrix (Visa and Mastercard)
  9. Visa Interchange Rate and Payment Network Fee Schedule (posted by Florida Department of Financial Services)
  10. CardFellow: CPS/Card Not Present, Visa Consumer Credit Interchange
  11. Helcim: Visa and Mastercard Interchange Rate and Card Brand Changes for October 2023

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading