Why was my transaction declined?

Modified on Thu, Jul 2, 2020 at 1:06 PM

While Authorize.Net® may not receive specifics on a particular decline, they do include some details on declines in the transaction responses, if available.

A table of common decline reasons, with the associated Response Reason Code, is listed below:

 

2General decline by card issuing bank or by Merchant Service Provider
3Referral to card issuing bank for verbal approval
4Card reported lost or stolen; pick up card if physically available
27Address Verification Service (AVS) mismatch; declined by account settings
44Card Code decline by payment processor
45AVS and Card Code mismatch; declined by account settings
65Card Code mismatch; declined by account settings
250Fraud Detection Suite (FDS) blocked IP address
251FDS filter triggered--filter set to decline
254FDS held for review; transaction declined after manual review

For more details, please visit https://developer.authorize.net/api/reference/responseCodes.html to look up a specific Response Reason Code


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article