#alex-muresan_docs
zealous parcelBOT
đ 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/1468626303757455468
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
molten fjord
The docs suggest payment_intent.processing:
The Advanced notice email must be sent 2 days before you charge your customer. Send this email when you receive a payment_intent.processing event with a payment method of type bacs_debit
Why do you need a charge?
lapis trout
I can't find the mandate id or reference on payment_intent.processing event, it seems to only be available on a charge
lapis trout
evt_3Sx1SeKj9LkWX2rh1X4viS4u
I can see the mandate id in the charge but it looks like the charge is created after payment_intent.processing is triggered
molten fjord
Hm yeah I think you'll have to use mandate.updated actually
It has amount details on it
No need to have a payment intent id i don't think
If you are collecting a mandate and payment at the same time, and have opted not to send the combined Confirmation of sign-up incorporating an Advanced notice email, then you must wait until the mandate is accepted to send the Advanced notice email. A mandate is accepted when you receive a mandate.updated event with a payment_method_details.type set to bacs_debit and payment_method_details.bacs_debit.network_status updated from pending to accepted.
lapis trout
there's another issue due to our setup in stripe, we have one main account and multiple connected accounts for all our customers so in order to figure out which payment is for which customer (as all payments go initially to main account), we add some metadata to payment_intent which needs to be used for direct debit as well so we can decide what logo, email, phone number and so on to use in each email, that's why I said in the first place that I might need a charge id or payment intent id
due to this setup is why we can't use custom stripe emails as if I remember correctly customisation is not possible on connected account level
molten fjord
The mandate has a on_behalf_of with the connect account id on it so couldn't you decide based on that? https://docs.stripe.com/api/mandates/object#mandate_object-on_behalf_of
lapis trout
it might work
So what should I do for future payments? I still need to send Advanced Notice emails and I need to rely on payment_intent.processing, right? Will future events contain previous charges?
Or how do I get the mandate id/reference for future payments starting from payment_intent.processing event?
My understanding is that mandate.updated only gets triggered once, when mandate is collected, not for every recurrent payment.
molten fjord
The reference doesn't change
So you can store it and just re-use it
But yes you'd use payment_intent.processing
lapis trout
Alright, thank you for your time, really appreciate it!