Webhooks for failed transactions

[schammy]

Please add a webhook for failed transactions, no matter the reason (expired, processing error, general error, whatever).

I'm not sure what kind of company wouldn't want to know immediately and automatically about a failed transaction, especially if it's for a subscription (ARB).

Silent Post does this and we're trying to migrate away from it per customer support advice but glaring omissions like this are making it near impossible.

The only solution is to either constantly query the API for unsettled txns to find failures (if we want to know about them immediately, which we do), or if we didn't mind waiting up to 24 hours then we could query once per day for the entire batch for the previous day to get all transactions and find the failed ones - but this is 2018 damnit, everything should be real time.

[Anurag]

Hi @schammy

Let  me know if we can connect on developer_feedback@authorize.net  to understand the use cases you want to cover for failed transactions ?

Thanks

Anurag

[h122762561]

Hi @Anurag ,

Is there any update for this idea? It is really useful to use webooks as silent post.

[Ashwinod]

To use webhooks with your subscriptions

1. Create a webhook endpoint in your app.
2. Add logic to handle Stripe events. For subscriptions, these include payment failures and subscription state changes (like moving from trial to an active state).
3. Test your webhook endpoint to confirm that it’s working as expected.

   Here are some other useful docs about webhooks

   • For more details about , read the guide.
   • Use the for an immersive experience where you learn to build a minimal webhook endpoint.