Authorize.Net · Decline codes
What does Authorize.Net 165 “This transaction has been declined (CVV void failed)” mean?
Checked
Authorize.Net response reason code 165 says the system void failed after a CVV2 code mismatch, based on the card code response and your merchant settings. The sale was declined, yet the authorization the processor granted may still sit on the card until it expires or is reversed. The shopper should correct the security code; the store may need to help release the hold.
- Type
- Hard decline for these details (merchant filter)
- Who declined
- Your Authorize.Net card code settings, then the processor
- Retry
- Only with the correct security code. Check for a held authorization.
- Shopper action
- Re-enter the security code; a pending hold may appear for a while.
- Merchant action
- Release any lingering authorization if the shopper asks.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 165 as never-retry on the same details: no backup processor is offered, so the card is not authorized twice while the first hold is pending. 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
Your card code settings rejected the transaction after the processor had authorized it, and the follow-up void did not complete.
What the store can do
If the shopper sees a pending amount, contact your merchant service provider or the issuer with the transaction details to reverse the authorization.
For developers
errors[0].errorCode "165". Authorize.Net's description: "System void failed. CVV2 Code mismatch based on the CVV response and the merchant settings."
Frequently asked questions
- Was the shopper charged after Authorize.Net code 165?
- No sale was captured, but an authorization hold may remain until it expires or is reversed.
- What should the shopper do after code 165?
- Re-enter the correct security code or use another card.
Sources
- Authorize.Net Response Code Tool (response reason codes) — Authorize.Net
- Authorize.Net response codes (JSON list behind the Response Code Tool) — Authorize.Net
Related
- 65 — Your card code (CVV) filter rejected the payment based on the security code result.
- 44 — The processor declined because the card's security code (CVV) did not match the bank's records.
- 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.
- 128 — The shopper's bank does not currently allow transactions on this account.
- 250 — The payment came from an IP address you blocked in Authorize.Net's fraud tools.
- 251 — A Fraud Detection Suite filter declined the payment, including the blocked-IP filter.