renaissance_mandate-update | Stripe Developers | Page 1

twin folioBOT May 7, 2026, 5:55 PM

#

👋 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/1502005889471746178

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

north geyser May 7, 2026, 5:55 PM

#

renaissance_mandate-update

gloomy girder May 7, 2026, 5:56 PM

#

hey @north geyser , sorry to trouble. i just open this thread to understand why the mandate.update event is happend

north geyser May 7, 2026, 5:56 PM

#

The Mandate you created is single use, so after being created and used for a payment it was marked inactive

gloomy girder May 7, 2026, 5:58 PM

#

so that mean every mandate created for single use, after it is used, Stripe will send a mandate.updated event to update us the status? (as currently we try to consume the mandate.update status with status inactive to delete corresponding record in our system.

#

to prevent this from happening, we need to create the mandate for non-single use?

north geyser May 7, 2026, 6:04 PM

#

yes

#

I mean having the Event is helpful if you for example collect bank details today but charge them in 2 months, you might not remember the Mandate was single use

#

but if you want to re-use that bank account more than once you should do a multi-use Mandate

gloomy girder May 7, 2026, 6:38 PM

#

thanks for the reply!

#

any suggestion when to have single use v.s. multiple use?

north geyser May 7, 2026, 6:46 PM

#

single use: you plan to only charge once, future payments would be on session where the customer is buying again and signing another agreement to be debited
multi use: all the other cases

twin folioBOT May 7, 2026, 6:48 PM

#

gloomy girder May 7, 2026, 6:48 PM

#

sure. sorry for a small question. i checked the code base and AI, the params we pass to stripe (on test sandbox mode) has no ON_SESSION param explicit setup. thus the mandate should be multiple use. can you help me check why the mandate is created with single use?

#

same event id evt_1TUVdtFXfYQzZWMaD78KnVPB

cursive geyser May 7, 2026, 6:50 PM

#

Hello 👋

I'm taking over as my colleague has to go

#

The mandate you referenced was created as a result of this API request: https://dashboard.stripe.com/test/logs/req_OOV1yoUCTiahCd

You are passing mandate_data explicitly here. This is for a single Payment Intent. So it created a single-use mandate.

What I find strange is that you already had a multi-use mandate for this Payment Method when you created it in this request: https://dashboard.stripe.com/test/logs/req_zvDB0b7hdBveqW

gloomy girder May 7, 2026, 6:55 PM

#

👀

cursive geyser May 7, 2026, 6:58 PM

#

The difference is the Intent being used.

The Payment Intent is used to create a one-time charge to the Customer so when you provide the mandate data is creates a single use mandate

Setup Intents are used to save Payment Methods for future use so that creates a multi-use mandate

gloomy girder May 7, 2026, 7:02 PM

#

thanks for the investigation! while not fully understand but i think i may catch up a bit. would like to see whether we can have payment intent that although just tries to charge the customer once, but do not create single-use mandate? (as we don't wanna receive an udpate from Stripe that the mandate is inactive)

cursive geyser May 7, 2026, 7:04 PM

#

In that case, if you've already saved the Payment Method with a multi-use mandate, you would not provide mandate_data in your Payment Intent.

gloomy girder May 7, 2026, 7:05 PM

#

let me have a check.

cursive geyser May 7, 2026, 7:05 PM

#

You can find the mandate on the Payment Method object and you can retrieve the Mandate object via our API: https://docs.stripe.com/api/mandates/retrieve

#

So you can check the status and type properties

gloomy girder May 7, 2026, 7:09 PM

#

so generally, the suggestion from above (1) check the mandate info via above retrieve endpoint (2) decide whether to provide mandate params from 1. before calling stripe payment_intents endpoint?

#

while from our codebase i saw we setup intent with default mandate params (which should create the multi-use mandate), so i think it should be safe we skip the mandate_data when calling payment_intents endpoint?

cursive geyser May 7, 2026, 7:11 PM

#

Okay so, for these us_bank_account payment methods, you would only need to provide the mandate_data if you did not already have an existing multi-use mandate.

So, to determine if you need to provide mandate data

Get mandate ID from Payment Method
Retreive Mandate object to determine if it is active and multi-use
If true, omit mandate_data from Payment Intent params; if false, include mandate data (this will create a single use mandate but at least the payment will go through)

#

If your codebase is creating multi-use mandates as part of saving the payment method (which is what it looks like), you will likely wind up omitting the mandate_data most of the time

#

You should receive the mandate.updated event when a mandate changes (e.g. becomes inactive) so you will know if/when you need to create a new one.

gloomy girder May 7, 2026, 7:16 PM

#

gotcha! thanks for clear clarification. may chat with my team for above information

cursive geyser May 7, 2026, 7:17 PM

#

Sure thing! Happy to shed what 💡 I can 🙂

If you have more questions later, we do close threads after a period of inactivity but you can always start a new one and we will be happy to help.

#

Even when closed, you can still access this thread for reference purposes too

#renaissance_mandate-update