#ratta-tha-vermin_webhooks
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1252330391411621959
đ Have more to share? Add details, code, screenshots, videos, etc. below.
You should see 2 retries in this case, no?
That being said, some declines are terminal, so you need to account for situations where this is the case
it says max of 2 times but i don't know if i've seen it try twice. but i'm not looking closely at this.
I guess the following would help us adjust copy on our dunning emails...
- should we be using the invoice.payment_failed webhook for dunning emails?
- can we determine if they are using ACH in the invoice.payment_failed webhook?
- can we determine if it is the final payment failed webhook sent? then we can avoid sending this email since it will be canceled anyway and we'll send the cancelation email.
Yes, you'd listen for invoice.payment_failed and inspect the next_payment_attempt attribute to see when/if Stripe will try again: https://docs.stripe.com/api/invoices/object#invoice_object-next_payment_attempt
For terminal declines, you'd look for these error codes on the associated Charge or Payment Intent: https://docs.stripe.com/billing/revenue-recovery/smart-retries#non-retryable-decline-codes
would it be enough to see if next_payment_attempt is null?
if it's null we would just not send the dunning email since it will be canceled anyway
Yep, that field being null means that we will not attempt another payment on that invoice.