Authorize.Net · Decline codes
What does Authorize.Net 65 “This transaction has been declined (card code filter)” mean?
Checked
Authorize.Net response reason code 65 means the transaction was declined because you configured your account, in the Merchant Interface, to reject certain card code (CVV) mismatch results, and this payment hit that rule. It is your filter, not the bank, saying no. The shopper can re-enter the security code; if many real customers are caught, review which card code results you reject.
- Type
- Hard decline for these details (merchant filter)
- Who declined
- Your Authorize.Net card code filter
- Retry
- Only with a correct security code, or after you change the filter.
- Shopper action
- Re-type the security code or use another card.
- Merchant action
- Check which CVV results your filter rejects.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 65 as never-retry on the same details and does not reroute it to a backup processor; the shopper fixes the security code and pays again on your Authorize.Net account. 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 bank returns a card code result with every authorization. Your card code filter decides which results are rejected; code 65 is that rule firing.
What the shopper can do
Enter the security code again carefully, or pay with another card.
What the store can do
In the Merchant Interface, open the Card Code Verification filter and confirm exactly which results it rejects, so only real mismatches are blocked.
For developers
errors[0].errorCode "65"; see transactionResponse.cvvResultCode for the value that triggered your rule. Code 165 is the variant where the automatic void failed.
Frequently asked questions
- Is Authorize.Net code 65 a bank decline?
- No. It is your own card code filter rejecting the security code result the bank returned.
- How is code 65 different from code 44?
- Code 44 is the processor declining on a CVV mismatch whatever your settings; code 65 is your filter rule.
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
- 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.
- 45 — Both the address check and the security code check hit the rejection rules you set.
- 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.