Authorize.Net · Decline codes
What does Authorize.Net 45 “This transaction has been declined (AVS and card code filters)” mean?
Checked
Authorize.Net response reason code 45 is returned when the processor's answer matched the rejection criteria you set for both the Address Verification Service (AVS) filter and the Card Code filter. The bank's check results tripped your own rules, so Authorize.Net declined the sale. The shopper should re-enter the billing address and security code; you should check that your filter settings are not stricter than you intend.
- Type
- Hard decline for these details (merchant filter)
- Who declined
- Your Authorize.Net AVS and card code filters
- Retry
- Only after the shopper fixes the address and security code.
- Shopper action
- Re-enter the billing address exactly as the bank has it and the security code.
- Merchant action
- Review your AVS and card code filter rules if good customers are caught.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 45 as never-retry on the same details, so checkout does not reroute it; the shopper corrects the address and security code and submits again. On a subscription renewal the code is not retried: the subscription is held past due and the customer gets an email with a link to add a new card.
Why it happens
AVS compares the billing address with the bank's records and the card code check compares the CVV. You decide in the Merchant Interface which results to reject; code 45 means both failed your rules at once.
What the shopper can do
Use the billing address your bank has on file (the one on your card statement), including the postcode, and re-type the security code.
What the store can do
In the Merchant Interface, review the AVS and Card Code filter settings. If real customers keep landing here, your rules may be rejecting results you would accept on review.
For developers
errors[0].errorCode "45"; transactionResponse.avsResultCode and cvvResultCode carry the individual results. Code 145 means the automatic void after this rejection failed.
Frequently asked questions
- Who declined Authorize.Net code 45, the bank or me?
- Your own filter rules, acting on the bank's AVS and card code results.
- What is the difference between code 45 and code 27?
- Code 27 is an AVS mismatch decline on its own; 45 means both the AVS and card code results matched your rejection rules.
Sources
- Authorize.Net Response Code Tool (response reason codes) — Authorize.Net
- Authorize.Net response codes (JSON list behind the Response Code Tool) — Authorize.Net
- Authorize.Net API reference: createTransactionResponse fields — Authorize.Net
Related
- 27 — The billing address entered does not match the address the card's bank has on file.
- 65 — Your card code (CVV) filter rejected the payment based on the security code result.
- 145 — Your AVS and card code filters rejected the sale, but the automatic void of the authorization failed.
- 44 — The processor declined because the card's security code (CVV) did not match the bank's records.
- 165 — A security code mismatch hit your settings and the automatic void of the authorization failed.
- 127 — An AVS mismatch declined the sale and the automatic void failed, so a hold may stay on the card.
- 128 — The shopper's bank does not currently allow transactions on this account.