#jcrags - checkout async payment failure
burnt juniper
Hello! Just starting a thread for you -- I'll review and respond as soon as I can 🙂
dull turtle
Hi, thank you, take your time I am not in a hurry 🙂
burnt juniper
I don't think another event is expected, but checking on that
I think you need to choose how to handle that based on the payment failure
dull turtle
You mean when stripe returns the checkout.session.async_payment_failed event I must check what the error was?
burnt juniper
Based on what I see here, the completed event would happen when they "approve" the SEPA payment, then the async event would come later
dull turtle
Yes that's correct. What I was really looking for is for instance a user submits a very very long form. Now let's say they made the payment but for some reason it failed, the status was not set to "paid" and thus we must send the user an Email so they can retry the payment. Their data of the form submission is still in the database. But what if they never retry the payment, basically we will want to clean up this data from our database in this case. Maybe I should just implement some sort of "expiry" within our system so they are given X amount of days to retry the payment. That's fine, but I thought that Stripe maybe had some sort of way of doing this maybe. But it makes sense that you'd handle this outside of Stripe I guess.
Thanks for helping, I will just go for the expiry method 🙂
burnt juniper
Well these events are about the checkout flow only -- anything collected on your own site before sending to Checkout would of course be yours to handle appropriately
Likely you'd want to track this failure and give the user some time to retry, but that "expiry" would be on your system only
dull turtle
Yes, agree, makes sense 🙂 thanks and have a good day/evening 🙂
burnt juniper
you too!