Authorize.Net · Decline codes
What does Authorize.Net 251 “This transaction has been declined (Fraud Detection Suite filter)” mean?
Checked
Authorize.Net response reason code 251 means the transaction was declined as a result of triggering a Fraud Detection Suite filter; Authorize.Net's note gives a blocked IP address as the example. The rules are yours, set in the Merchant Interface, so the bank never weighed in. Review which filter fired before loosening anything.
- Type
- Risk block (merchant setting)
- Who declined
- Your Authorize.Net Fraud Detection Suite filters
- Retry
- No, not unless you change the filter or approve the order.
- Shopper action
- Contact the store or try another payment method.
- Merchant action
- Find which filter fired in the Merchant Interface and adjust only if real customers are hit.
What PlatformDTC does
PlatformDTC treats Authorize.Net code 251 as a fraud stop: checkout never retries it on a backup processor, so your Fraud Detection Suite rules keep the final say. 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 Fraud Detection Suite runs the filters you configure on each transaction. Code 251 means one of them was set to decline and fired; Authorize.Net's example is a blocked IP address.
What the store can do
Open the declined transaction to see the triggering filter. Tighten nothing blindly: switch noisy filters from decline to review if they catch real customers.
For developers
errors[0].errorCode "251". Filters set to hold rather than decline return 252 or 253 instead.
Frequently asked questions
- Which filter caused Authorize.Net code 251?
- The transaction details in the Merchant Interface show which Fraud Detection Suite filter was triggered.
- Can I let a code 251 order through?
- Not after the fact; adjust the filter, or set it to hold for review so you can approve orders manually.
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
- 250 — The payment came from an IP address you blocked in Authorize.Net's fraud tools.
- 252 — The payment was accepted but is held for your review by a fraud filter set to hold.
- 41 — Your own FraudScreen.Net threshold blocked the payment because its fraud score was too high.
- 253 — The card was authorized, but a fraud filter is holding the payment for your review.
- 254 — You or your team declined the payment after reviewing a held transaction.
- 295 — The prepaid card only covered part of the amount; another payment is needed for the rest.
- 36 — The bank approved the card at checkout, but the payment failed when it was settled.
- 6 — The card number failed validation: a typo, a missing digit, or not a real card number.