#pavlos_91429
sand axleBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- pavlos-ephemeral-key-qs, 5 hours ago, 11 messages
- pavlos_91429, 3 days ago, 14 messages
- pavlos_91429, 6 days ago, 8 messages
- pavlos_91429, 6 days ago, 33 messages
proper thistle
As a follow-up question, I'd like to ask whether follow-up payments may require authorization from the user and how I should handle something like that.
turbid otter
First of all, I recommend reading: https://stripe.com/docs/billing/subscriptions/webhooks. It would be best to handle this via webhooks. It's what we recommend. For: This means I don't, at that point, check whether the Stripe subscription is created. Should I also do that, or the fact that the first payment intent is active guarantees me that? I would just rely on getting the invoice.paid and invoice.payment_failed events
proper thistle
I will definitely use webhooks for any subsequent payments, but I thought that for this particular first one, I could rely on getting the payment status via the API retrieval to handle it in a more synchronous way
What's the different between invoice_paid and invoice.payment_intent.successful?
I mean, is checking any of those two equivalent?
turbid otter
No we always recommend invoice.paid
Oh sorry I thought you were talking about invoice.payment_succeeded (which you shouldn't use; use invoice.paid instead)
It's up to you
You can either check invoice or payment intent
Doesn't matter. Just depends on what data you need in your app
could rely on getting the payment status via the API retrieval to handle it in a more synchronous way You shouldn't rely on this
The customer's browser could crash, there could be a network error, etc
There's no guarantee your server will get that api request from the client