What an AVS test is

An AVS test is a sandbox transaction that sends a billing address and ZIP code to the card issuer and returns an Address Verification System response code. The code tells your system how much of the address matched. In production, AVS helps you decide whether to accept, hold, or reject a card-not-present order. In a sandbox, it lets you confirm that your checkout form passes the right fields and that your rules read the result correctly.

Gateway sandboxes ship with published test card numbers. Each number triggers a fixed AVS outcome, so you can reproduce a match or a mismatch on demand without touching a real cardholder account. Never run an AVS test with a live card number.

Prerequisites

• A sandbox merchant account with a payment gateway that supports AVS
• The gateway's published test card numbers and the AVS outcome each one returns
• Access to raw API responses or the transaction detail view in the sandbox dashboard
• A test billing address, city, state, and ZIP code you can change between runs

How to run an AVS test

1. Open the gateway's test card reference page and copy the card number that maps to the AVS result you want to check.
2. Open your sandbox payment form or API client.
3. Enter the test card number, a future expiration date, and any CVV the reference page lists for that card.
4. Fill the billing address fields with the street, city, state, and ZIP the gateway associates with that test card.
5. Submit the transaction.
6. Open the transaction detail view and locate the AVS response field.
7. Record the code, then change one field at a time and resubmit to see how the code shifts.
8. Repeat the run with the ZIP removed, the street removed, and both removed to cover every branch of your decision logic.
9. Confirm that your order workflow routes each code to the action you intend, such as accept, review, or decline.
10. Log the address, ZIP, and returned code for each run so the QA record matches the result.

Reading AVS response codes

Most gateways return a single letter. The exact set varies, so confirm the list against your provider's documentation before you write rules.

• Y - Street address and five-digit ZIP both match.
• A - Street address matches, ZIP does not.
• Z - Five-digit ZIP matches, street address does not.
• N - Neither the street address nor the ZIP matches.
• U - The issuer could not check the address, often because the system is unavailable.
• R - The issuer's system is down. Retry the request.
• S - The card issuer does not support AVS. Common outside the United States.
• G - Non-US issuer. AVS has limited reach on the transaction.

What to watch for

AVS checks the numeric part of the street address and the ZIP. Apartment letters and minor spelling differences often pass. A mismatch on a full match code usually means the address fields are not reaching the gateway at all, so check the field mapping in your request payload before you change your rules.

AVS is not a standalone fraud control. Pair it with CVV checks, velocity limits, and your own risk scoring. An AVS match confirms that an address is on file with the issuer; it does not confirm that the person entering the card owns it.