#daniele-de-benedetto_webhooks
nimble sableBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1439890471869743136
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
honest oracle
👋
The event mandate.updated is triggered when there is an update on the mandate and not when it's created
The event checkout.session.async_payment_succeeded is the good indication that you need to monitor in order to get notified about the Sepa success
narrow tide
ok so i can always say thee looking at checkout.session.async_payment_succeeded i can get the latest_charge and from the charge the mandate id 'succeded'
if it was denied at first attempt i can look to the payment_intent failed
after that i can look to the mandate updated right ?
p.s i suggest to create some hook on first succeded/refused it can be usefull in order to separate the logics on payment intent/charge in case of sepa
honest oracle
If you get that event, it mean that the payment was succeeded
You can check the Charge, and check its payment_method_details
you should see the mandate under the sepa_debit object
In you case, here is the mandate Id mandate_1STQJFG0HkO3ZPnpnoX61t9z
narrow tide
ok thank you