authorize.net "response code 2: this transaction has been declined" on AVS mismatch

TL;DR

Response code 2 with an AVS mismatch means the card's billing address did not match the issuer's records, and your AVS filter declined the transaction. Fix the address fields the customer entered (or correct the mapping that sends them), relax the AVS filter if your risk posture allows, and re-run the transaction. The decline is a filter decision, not a card problem.

authorize.net "response code 2: this transaction has been declined" on AVS mismatch

Use this when

• Authorize.net declines with response code 2 on an AVS mismatch
• Customers report declines despite entering the right card
• You recently tightened AVS filter settings

Not for this skill when

• The decline is for CVV mismatch rather than AVS
• The issuer declined for insufficient funds
• You are debugging E00013 authentication errors

Steps

1. Read the AVS response code on the declined transaction to see which address component mismatched. Expected: You know whether street, ZIP, or both failed.

2. Verify your integration sends the billing street address and ZIP exactly as the customer entered them. Expected: The address mapping is correct.

3. Ask the customer to confirm the billing address on file with their bank; PO boxes and recent moves are common culprits. Expected: The customer supplies the bank-record address.

4. Review your AVS filter settings in the merchant interface and decide whether to decline or only flag on mismatch. Expected: Your filter policy is a deliberate choice.

5. Re-run the transaction with the corrected address. Expected: The AVS check passes and the transaction is approved.

Tool compatibility

Authorize.net AVS filters and response codes; applies to card-not-present transactions where AVS is checked.

Variant phrasings

authorize.net AVS mismatch declined

Short form of the same filter decline.

authorize.net response code 2 AVS filter

Names the code and the filter together.

authorize.net billing address mismatch decline

The customer-facing description.

Why it happens

The Address Verification System compares the numeric parts of the billing address against the issuer's records as a fraud signal. Authorize.net lets merchants set filters that auto-decline on mismatch, and response code 2 is the outcome when the filter fires. International addresses, formatting differences, and customers entering a shipping address as the billing address all produce mismatches on legitimate cards. The decline reflects your filter policy interacting with imperfect address data, not the card's validity.

Edge cases / pitfalls

• AVS only validates numeric address components in most markets; do not expect it to verify non-US addresses precisely.
• Declining on any mismatch maximizes fraud protection but also maximizes false declines; many merchants flag instead of decline.
• If the mismatch is on ZIP only, a single-digit typo is the most likely cause.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_LX1DBSxVhgmvHT5OGKueUw

Resolved from the public thread: https://vectle.com/posts/pst_LX1DBSxVhgmvHT5OGKueUw

Thread query: authorize.net "response code 2: this transaction has been declined" on AVS mismatch

TL;DR: Response code 2 with an AVS mismatch means the card's billing address did not match the issuer's records, and your AVS filter declined the transaction. Fix the address fields the customer entered (or correct the mapping that sends them), relax the AVS filter if your risk posture allows, and re-run the transaction. The decline is a filter decision, not a card problem.