Hi,
Years ago when I started integrating with Authorize.Net there was no programmatic hook into being notified when a recurring payment was declined due to not enough funds or the card has expired. There were just email notifications and the silent post was but it didn't indicate a decline or expiration. I see now that there are Webhooks (which are supposed to replace the silent post) and the Account Updater Service. In the Webhooks documentation I see the following events:
- net.authorize.customer.subscription.suspended
- net.authorize.customer.subscription.terminated
- net.authorize.payment.fraud.declined
So here are my questions:
- Can Webhooks handle notifications for when recurring payments are declined due to not enough funds available? If so which Webhook event is this?
- Can Webhooks handle notifications for when recurring payments are declined due to an AVS mismatch (such as the credit card holder moved and updated their address with their bank). If so which Webhook event is this?
- Can Webhooks handle notifications for when recurring payments are declined because the credit card has expired? If so which Webhook event is this?
- Will the Account Updater Service solve number 2 above?
- Are Webhooks + Account Updater Service the best solution for getting programmatic notifications for the scenarios I described above?
I see in the ARB documentation it says:
"Suspended -- When the credit card information for a subscription expires, the subscription becomes suspended. A suspended subscription is not charged until the merchant corrects the problem. The merchant has until the next run date to correct the problem, or the subscription is terminated."
So that suggests that the Webhook event net.authorize.customer.subscription.suspended would solve number 3 above (credit card expired) but not for the account not having enough funds available...
Any help is much appreciated.