AVS and CVV Verification: Filter Settings That Work
Payment Processing Fundamentals

AVS and CVV Checks: Filter Settings That Balance Fraud and Lost Sales

AVS and CVV verification explained: what each response code means and gateway filter settings that reduce fraud while limiting declines of good customers.

Hand holding a blank card in front of an open laptop on a sunlit table, suggesting an online card payment

Photo: Pixabay

On this page 6 sections
  1. What AVS and CVV Verification Actually Compares
  2. Reading AVS and CVV Response Codes
  3. The Default Setting That Quietly Blocks International Buyers
  4. A Clean Match Doesn't Make an Order Safe
  5. Gateway Filter Settings by Risk Level
  6. Does AVS Still Affect Your Interchange Rate?

Key takeaways

  • Authorize.Net's default AVS filter rejects B, E, G, N, R, S and U. That can block good international cards until you change it.
  • A wrong security code is a stronger fraud signal than a partial address match, so decline CVV mismatches and review partial AVS matches.
  • In the illustrative example, declining every partial match only pays off when roughly 18% or more of those orders are fraud.
  • Wells Fargo's April 2026 Visa matrix lists AVS as optional for CPS/Card Not Present. Collect the billing ZIP for fraud screening, and don't count on it to qualify for interchange.

AVS and CVV verification checks whether the person paying knows two things a casual thief may not: the numbers in the cardholder's billing address and the security code printed on the card. The issuing bank compares what was entered against its records and returns a one-letter result for each check. A mismatch doesn't automatically kill the sale. The issuer may still approve the authorization, and in most cases your gateway's filter settings decide what happens next.

That makes the filter settings a business decision, and no setting removes risk on both sides. Set them too loosely and more stolen cards get through. Set them too tightly and you turn away the customer who moved last month or typed an old ZIP from memory. Where you draw the line depends on what you sell and how quickly it leaves your hands.

What AVS and CVV Verification Actually Compares

The address verification service (AVS) compares the billing address entered at checkout with the address the issuer has on file. It checks less than most merchants assume. Authorize.Net's API documentation says the bank returns only whether the house number and the postal code match, and the merchant can't retrieve the address itself. So "Main Street" versus "Main St." doesn't matter. A transposed house number does.

AVS checks the billing address only. A billing address that differs from the shipping address is a separate fraud signal, and you have to set up that rule yourself.

The card verification value (CVV) is the three- or four-digit code printed on the front or back of the card, as described in the PCI DSS v4.0 self-assessment questionnaire. On American Express cards it's on the front. Under PCI DSS Requirement 3.3.1.2, you may collect the code to authorize a sale, but the PCI Security Standards Council prohibits storing it after authorization, even if it's encrypted.

A customer's permission doesn't change that, according to the Council's FAQ 1574. If you write the code down while taking a phone order, the questionnaire expects you to shred the paper or black out the code once the sale is complete. PCI DSS is an industry security standard, not federal law. Your processing agreement is what binds you to it.

Because merchants can't store the code, a thief who breaches your order history won't find it there. A thief who captures card details as they are typed, through a phishing page or a compromised checkout, gets the code along with everything else.

Reading AVS and CVV Response Codes

Every card-not-present authorization that includes address data comes back with an AVS letter. The codes below are the ones Authorize.Net documents. The "Typical Handling" column is our suggested starting point. It isn't a network rule.

CodeWhat It MeansTypical Handling
YStreet address and 5-digit ZIP matchAccept
XExact matchAccept
AStreet matches, ZIP doesn'tReview
Z5-digit ZIP matches, street doesn'tReview, or accept on low-risk orders
W9-digit ZIP matches, street doesn'tReview, or accept on low-risk orders
NNeither street nor ZIP matchesDecline or step up to 3-D Secure
UAddress information unavailableJudge on other signals
SIssuer doesn't support AVSJudge on other signals
GNon-U.S. issuing bankJudge on other signals; consider 3-D Secure
RSystem unavailable or timed outRetry once, then judge on other signals
EAVS errorReview
BNo address information was providedFix your checkout form
PAVS not applicable to this transactionJudge on other signals

The same letters don't always mean the same thing. Cybersource's AVS reference explains that these single letters are Visa's standard codes and that other brands' results, including American Express, are mapped onto them. The Bancorp's developer reference gives a different meaning for the same letter Y depending on the card brand. Visa has also pared down its list. Elavon's documentation says that since April 2023 Visa has discontinued redundant AVS values, and it marks several letters, including G and P, as no longer used by Visa, with R or Z returned instead. Check your own gateway's code list before you change any rule.

CVV results are simpler. M is a match and N is a mismatch. P means the code wasn't processed. U means the issuer isn't certified for the check, and S means the issuer says the card has a code but the merchant indicated it doesn't, per Inovio's response-code reference. A processor support guide on CVV2 codes adds a point merchants often miss: the CVV result is separate from the approval, so a sale can be approved even when the code doesn't match. Your settings decide whether that sale goes through.

Be less forgiving of a CVV mismatch than of an address mismatch. A real customer who mistypes a three-digit code can fix it in seconds. A script that cycles through codes until one works is a card-testing attack, and our guide to spotting and stopping card testing attacks covers the velocity limits to pair with a strict CVV rule.

The Default Setting That Quietly Blocks International Buyers

This problem is easy to miss on Authorize.Net. According to Authorize.Net's AVS article, the gateway rejects codes B, E, G, N, R, S and U by default unless you change the settings in the Merchant Interface. G means a non-U.S. issuer, and U and S mean the check couldn't be done. Many foreign cards return exactly those codes, so a store using the defaults can decline good international orders without anyone noticing.

Authorize.Net's support article says accepting G, U and S lets you take international cards. The Authorize.Net merchant guide adds two caveats. First, not every bank outside the U.S. returns G, U or S. Second, if you accept N, rejecting B, E, R, G, U and S makes little sense, because those codes mean the address couldn't be verified at all. That's weaker evidence of fraud than an outright mismatch. Visa's code changes matter here too: if a non-U.S. Visa card now comes back as R instead of G, a rule that rejects R will still turn that buyer away.

If you sell abroad, accept the unavailable codes, watch how R behaves on foreign cards, and rely on the CVV result and 3-D Secure authentication instead. MannyPay's international payment processing page covers currency and settlement options for cross-border sales.

A Clean Match Doesn't Make an Order Safe

A Y result proves only that the buyer knows the cardholder's billing address. Stolen card data can be sold with the address and security code included, because fraudsters know merchants check those fields. A full match is good evidence to include when you respond to a dispute. It doesn't shift liability for an unauthorized-use chargeback. 3-D Secure is the tool built for that, because it asks the issuer to authenticate the cardholder directly.

Treat AVS and CVV as a first screen. For a store shipping physical goods, they can filter out unsophisticated fraud, but they won't stop a buyer who holds complete card details. Digital goods and items that resell easily need more layers, and our comparison of fraud prevention tools for online stores covers what to add first.

Gateway Filter Settings by Risk Level

Most gateways let you assign an action to each response code: accept, decline or hold for review. Stores on WooCommerce or Shopify that connect through an outside gateway such as Authorize.Net or NMI usually set these rules in the gateway, not in the store platform. Treat the table below as a starting point, and adjust it after a month of real results.

SettingPhysical Goods, Standard RiskInstant Digital or High-Resale GoodsKeyed Phone or Mail Orders
AVS N (no match)DeclineDeclineDecline
AVS A/Z/W (partial)ReviewReview or 3-D SecureReview
AVS U/S/G (unavailable)Accept, watch other signalsReview or 3-D SecureReview
AVS R/E (error)ReviewReviewRetry, then review
CVV N (mismatch)DeclineDeclineDecline
CVV P/U (not processed)AcceptReviewReview

The middle column is stricter because there's no shipping delay that gives you time to cancel. A buyer who receives a gift card code or a software download has the goods immediately. A furniture store can usually stop a suspicious order before it leaves the warehouse.

Keyed orders get extra scrutiny because a caller can read the numbers off a stolen card while you type. Collect the billing ZIP and security code in your virtual terminal on every phone order, including calls from people who sound like regulars.

Worked Example: When Declining Partial Matches Pays

Partial matches are where good sales get lost, so it helps to put numbers on the choice. Every figure here is illustrative. Replace them with your own.

Assumptions: in one month, 60 orders come back with a partial AVS match. Four are fraud and 56 are legitimate. The average order is $85 at a 40% gross margin, so each sale earns $34 in gross profit and the goods cost $51. If you decline partial matches, half of the legitimate buyers retry successfully and the other half give up. A fraud order that ships costs you the goods plus a $25 chargeback fee, or $76.

  • Declining every partial match loses 28 good orders: 28 × $34 = $952 in gross profit.
  • Accepting every partial match lets 4 fraud orders through: 4 × $76 = $304.

Under these assumptions, a blanket decline costs about three times what it prevents. The break-even point is more useful than either total. Each legitimate partial-match order you decline costs $17 on average (half of them walk away, at $34 each), while each fraud order you let through costs $76. Declining pays only when 76F is greater than 17 × (60 − F), where F is the number of fraud orders. That works out to about 11 of the 60, or roughly 18%. Below that rate, reviewing or accepting partial matches is the better choice. Above it, decline them or send them through 3-D Secure.

Reviewing 60 orders is a manageable monthly workload, and a reviewer comparing the shipping address with the customer's order history can catch much of the fraud. Chargebacks also count against your dispute ratio, so lean toward review even when the dollar math is close.

What a Filter Decline Looks Like to the Customer

The AVS result arrives with the issuer's response, so by the time your filter rejects the sale, the issuer may already have approved it. Depending on the bank, the customer may see a pending charge for a while. If they then retry with corrected details, they can see what looks like a double charge. A clear decline message heads off much of that confusion: say the billing address didn't match and that any pending amount will drop off. Our article on declined payment messages that save the sale has wording you can adapt. Filtered attempts may also carry a per-authorization charge, as explained in whether declined card transactions cost you money.

Does AVS Still Affect Your Interchange Rate?

Less than it used to, at least for Visa. Interchange is the fee the networks set and the issuing bank collects. Older processor guides listed AVS as a requirement for Visa's lower-cost card-not-present categories, but Wells Fargo's Visa qualification matrix effective April 2026 lists AVS (ZIP code) as optional for CPS/Card Not Present. Requirements still vary by network and category, and they change, so confirm the current criteria with your processor before assuming a missing ZIP is harmless. Any processor's matrix reflects how that processor applies the network rules. It doesn't replace Visa's own tables.

Keep the billing fields either way. They feed your fraud filters and your dispute responses. If you want a shorter form, our guide to which checkout form fields to cut and which to keep shows where trimming is safe.

Start with your last statement and look for any lines marked downgrade, non-qualified or EIRF on keyed and online sales. Then open your gateway's AVS settings and compare them with the table above, beginning with whether G, R, U and S are set to reject. If either check raises questions, request a free quote and bring the statement. A MannyPay specialist will respond within one business day.

Sources

  1. Authorize.net Support: Understanding and Configuring the Address Verification Service (AVS)
  2. Authorize.net Merchant Integration Guide
  3. Authorize.net API Documentation: Payment Transactions
  4. Authorize.net/Cybersource Developer: AVS Codes for Other Processors
  5. Elavon Developer: Hosted Payment Page Response Codes
  6. The Bancorp Developer Portal: AVS Response Codes
  7. My Payments Insider: CVV2 Response Codes
  8. Inovio Help Desk: AVS and CVV Responses
  9. PCI Security Standards Council FAQ: Are Merchants Allowed to Request Card-Verification Codes/Values?
  10. PCI Security Standards Council FAQ 1574
  11. PCI DSS v4.0 Self-Assessment Questionnaire B
  12. Wells Fargo Merchant Services: Payment Network Qualification Matrix, Effective April 2026

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