Authorize.Net · Decline codes
What does Authorize.Net 44 “This transaction has been declined (card code mismatch)” mean?
Checked
Authorize.Net response reason code 44 means the card code (CVV) submitted did not match the code on file at the issuing bank, and the processor declined the transaction. Authorize.Net notes the processor can do this regardless of your Card Code Verification filter settings. The shopper should re-type the security code from the back of the card, or the front on American Express, or use another card.
- Type
- Hard decline for these details
- Who declined
- The card processor, using the bank's card code check
- Retry
- Only with the correct security code. Retrying the same code will fail the same way.
- Shopper action
- Re-enter the 3- or 4-digit security code carefully, or use another card.
- Merchant action
- Let the shopper correct the code; never resubmit the same values.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 44 as never-retry on the same details: checkout shows the decline, does not reroute it to a backup processor, and the shopper can correct the security code and pay 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
The issuing bank compares the security code with its records. When it does not match, some processors decline outright even if your own card-code filter is relaxed.
What the shopper can do
Look at the card again: 3 digits on the back for Visa, Mastercard and Discover, 4 digits on the front for American Express. Type it fresh rather than relying on autofill.
What the store can do
Authorize.Net advises submitting only valid card codes, and leaving the field out entirely if you do not collect it. Do not resubmit the same code; a run of mismatches looks like someone guessing.
For developers
errors[0].errorCode "44"; check transactionResponse.cvvResultCode for the check result. Do not send an empty or made-up cardCode value.
Frequently asked questions
- Is Authorize.Net code 44 the same as my card code filter?
- No. Code 44 is the processor declining on the bank's CVV check; a decline caused by your own filter settings is code 65 (or 45 when the AVS filter is involved too).
- Can the shopper retry after code 44?
- Yes, with the correct security code. The same code will be declined again.
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
- 65 — Your card code (CVV) filter rejected the payment based on the security code result.
- 45 — Both the address check and the security code check hit the rejection rules you set.
- 165 — A security code mismatch hit your settings and the automatic void of the authorization failed.
- 78 — The security code (CVV) sent was in the wrong format, for example the wrong number of digits.
- 145 — Your AVS and card code filters rejected the sale, but the automatic void of the authorization failed.
- 27 — The billing address entered does not match the address the card's bank has on file.
- 127 — An AVS mismatch declined the sale and the automatic void failed, so a hold may stay on the card.