Authorize.Net · Decline codes
What does Authorize.Net 41 “This transaction has been declined (FraudScreen.Net)” mean?
Checked
Authorize.Net response reason code 41 is a decline from FraudScreen.Net: only merchants set up for that service receive it, and it is returned when the transaction's fraud score is higher than the threshold the merchant set. The bank never decided anything. Check the score in your Merchant Interface, and change the threshold only if genuine customers are being blocked.
- Type
- Risk block (merchant setting)
- Who declined
- Your Authorize.Net fraud filter (FraudScreen.Net)
- Retry
- No, not on the same details. Review the order or adjust your filter.
- Shopper action
- Try another card or contact the store.
- Merchant action
- Review the score in the Merchant Interface; loosen the threshold only if real customers are hit.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 41 as a fraud stop: checkout never moves the shopper to a backup processor, because re-running a payment your own filter rejected elsewhere would simply route around that filter. 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
FraudScreen.Net scores each transaction, and Authorize.Net declines it with code 41 when the score is above the threshold you configured. Authorize.Net's note: "Only merchants set up for the FraudScreen.Net service would receive this decline."
What the store can do
Open the transaction in the Authorize.Net Merchant Interface to see why it scored high. If good customers keep getting caught, raise the threshold a little; if the orders look like card testing, leave it and add velocity limits.
For developers
errors[0].errorCode "41". The related code 141 means the system void of a FraudScreen-rejected transaction failed, which can leave an authorization on the card.
Frequently asked questions
- Did the bank decline Authorize.Net code 41?
- No. Your own FraudScreen.Net threshold declined it before the bank's answer mattered.
- How do I stop code 41 hitting real customers?
- Review the scores of the declined orders and adjust the FraudScreen.Net threshold in the Merchant Interface.
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
- 141 — FraudScreen.Net rejected the payment, but the automatic void of the authorization did not go through.
- 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.
- 44 — The processor declined because the card's security code (CVV) did not match the bank's records.
- 45 — Both the address check and the security code check hit the rejection rules you set.
- 145 — Your AVS and card code filters rejected the sale, but the automatic void of the authorization failed.
- 65 — Your card code (CVV) filter rejected the payment based on the security code result.
- 165 — A security code mismatch hit your settings and the automatic void of the authorization failed.