Why Is a Transaction "Successful" in Recurly but "Declined" in Authorize.net?

This discrepancy is caused by Authorize.net's built-in fraud velocity system. If this feature is enabled, a transaction may be sent back as "successful" to Recurly while it is still in a "pending/processing" status in Authorize.net.

If the transaction is ultimately declined in Authorize.net, it will still remain as "successful" in Recurly. This is because Recurly receives the initial response and does not continue communicating with the gateway to check for a final status.

You have the ability to turn this feature off in Authorize.net. We recommend contacting their support team directly if you would like to do that: https://www.authorize.net/support/.