#Alexandru Comanescu-dispute
1 messages · Page 1 of 1 (latest)
Hey! Yes, charge.dispute.created is what you want: https://stripe.com/docs/api/events/types#event_types-charge.dispute.created
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
@shadow oyster Thank you for the quick answer! And is there one for invoice (subscription based) failed payments on retry? Or should I keep the payment attempts in my DB and use that as a source of retry attempts? Do you have any suggestions?
You'll likely want: https://stripe.com/docs/api/events/types#event_types-invoice.payment_failed
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Alright, so I need to maintain my own logic for the payment attempts and failed retries. Thank you! Have a great day!
Not necessarily, no. We have an automatic retry functionality that's managed in your Dashboard: https://stripe.com/docs/invoicing/automatic-collection#failed-payments
Oh, nice!