What can we help you with?


000001488


134

04/09/2025 18:12 PM

5.0

This article will guide merchants through understanding the specific response for transactions triggered by AFDS..

The Advanced Fraud Detection Suite (AFDS) specific transaction responses indicating when a transaction is affected by the AFDS filters. These filters are configured in the Merchant Interface.

Reason Response CodeResponse Reason TextNotes
250This transaction has been declined.This transaction was submitted from a blocked IP address.
251This transaction has been declined.

This transaction was submitted from a blocked IP address.

The transaction was declined as a result of triggering a Fraud Detection Suite filter.

252Your order has been received. Thank you for your business!The transaction was accepted, but is being held for merchant review. The merchant may customize the customer response in the Merchant Interface.
253Your order has been received. Thank you for your business!The transaction was accepted and was authorized, but is being held for merchant review. The merchant may customize the customer response in the Merchant Interface.
254This transaction has been declined.The transaction was declined after manual review.

For more information, please visit the Response Codes page to look up a specific error code.

For legacy integration methods, including AIM (Advanced Integration Method), SIM (Server Integration Method), and DPM (Direct Post Method), the Response Reason Code will be in either the field, x_response_reason_code, or in position 3 of the delimited response.

 



Was this article helpful?


Articles Recommended for You
Updating results