Hi Jody

It's possible that the gateway failed to charge because the card is no longer valid, etc. Normally, errors would be recorded into the DNN Event Viewer so the first place is to find out what is the exact cause of the error. Please post full error if possible.

Currently, I'm afraid there's no email for failed payment although you could probably create a custom task scheduler job to query orders without payment and send an email.

After further search on my end the error is not a declined/old card, it's an issue with the payment ID/profile that's being stored in the CIM interface. FYI this is only happening to us on RECURRING ORDERS only, not regular 1-off orders.

<response>
<resultCode>Error</resultCode>
<directResponse />
<messages>
<message>
<code>E00040</code>
<text>Customer Profile ID or Customer Payment Profile ID not found.</text>
</message>
</messages>
</response>

After discussion with authorize.net support on this issue, here is what they said:
E00040 – The record cannot be found. (CIM only)

This error occurs if the profileId, paymentProfileId, or shippingAddressId is not valid. There are multiple possible causes, which may include:
Confusion over the differences between profile IDs and payment profile IDs;
Issues when storing ID numbers;
Using an ID number from one account's CIM setup when submitting to another account's CIM setup.

Note that profile IDs, payment profile IDs, and shipping address IDs are not transferrable between accounts.

They said that the developer would know what to do with this info so I am passing it on to you along with a link they sent (which I am sure you guys already know about!) https://community.developer.authorize.net/

Hope this helps and can be fixed asap :)

Hi Jody,

Generally, this can happen if the customer deleted their CIM profile payment information for many reasons (e.g. change credit card by deleting and adding instead of updating, etc). However, the Storefront is not notified by A.NET when a profile payment is removed (there's no callback hook for it). Later, when the Storefront tries to contact CIM to charge that profile payment, A.NET will naturally fail. If you have a lot of recurring orders, you might have a small percentage of them will fail this way and this may be normal. Unfortunately, unless you're saying all CIM recurring payments are failing this way consistently, or if you're able to reproduce the issue with a local payment that isn't deleted, it would be quite difficult to diagnose the issue without more information.

Thank you for your understanding.