#axelvaindal-webhooks
1 messages ยท Page 1 of 1 (latest)
๐ happy to help
I assume it's impossible to guarantee webhook event order as long as we subscribe to multiple events right
true https://stripe.com/docs/webhooks/best-practices#event-ordering
it appears the subsequent customer.subscription.updated is still considered active (even though the user has not technically paid yet). Is there any reason for this?
because SEPA is an async payment method
Alright, so is there any mean to actually verify that the SEPA payment was successfully processed when the customer.subscription.updated event is sent?
Right now, we assumed that if the subscription was considered active, it was alright, but as it will always be the case for SEPA, we need a way to actually confirm the payment I suppose.
Or is there any cleaner way to handle this directly in the webhook event without fetching anything more ?
sorry I've missed your message
you should listen to this event https://stripe.com/docs/api/events/types#event_types-checkout.session.async_payment_succeeded
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
or this https://stripe.com/docs/api/events/types#event_types-checkout.session.async_payment_failed (in the case of a payment failure)
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Yes, indeed, actually I've refused the checkout.session.completed process in case payment_status is unpaid and just wait for the async one.
In such case, the customer won't exist in our system anyway and the customer.subscription.update will keep failing until we have receive the async event
Thanks for your help ๐
let me know if you need any more help
Hey, taking over here. Let me know if there's any follow-up Qs I can answer!