#thebobdresseur_api
zinc bladeBOT
👋 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/1447938820359065670
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
sturdy lodge
👋 Do you get an error when you try to call useConfirmSetupIntent without params?
glass wadi
I did not try, I have typescript errors
I did not dig the implementation of confirmSetupIntent
But is my use case a common one ? If so is it the way multiple sepa mandates should be created ?
sturdy lodge
I believe this is the usual way, if I'm understanding your use case correctly: https://docs.stripe.com/payments/ideal/set-up-payment?payment-ui=mobile&platform=react-native#react-native-charge-sepa-pm
glass wadi
Not really, this seems to use iDEAL. I'm trying to implement Sepa Debit. I have customers on the platform account and I want to create payment intents on behalf of connected accounts. When creating a payment intent with a payment method of type sepa_debit, there must be a sepa mandate linking the payment method to the connected account. So I'd like a customer to be able, for a unique payment method, to create multiple sepa mandates in order to allow connected account to debit him. Setup intents seem to do that, but cannot be confirmed without providing the iban again.
So is there another way of creating sepa mandates without having to fill in the iban every time ?
sturdy lodge
Just checking this, bear with me..
acoustic abyss
When you say 'create payment intents on behalf of connected accounts', what exactly does that look like? Is it a destination charge, direct charge?
An example pi_xxx ID of a payment you're trying to process with a SEPA PM might be useful
glass wadi
pi_3SaFhnHMOWEObXZm1oU7ORTw
acoustic abyss
Ah, yep. With on_behalf_of the mandate needs to be generated with that parameter too. Are you doing that with the Setup Intent?
I think overall though there isn't a way to confirm a Setup Intent with an existing SEPA pm_xxx (you can with card) in the RN SDK, which is what you're trying to do here
glass wadi
Yes the Setup Intent is created with on_behalf_of.
Ok thanks, I'll try another way !
acoustic abyss
You can try server-side confirmation but you'd need to handle the mandate acknowledgment manually: https://docs.stripe.com/api/setup_intents/confirm#confirm_setup_intent-mandate_data
glass wadi
This means providing mandate data manually (ip address, user agent...) ?
acoustic abyss
Yes, obviously they're normally collected by the front-end SDKs
glass wadi
Yes that was my guess, are the frontend sdks bringing more abstraction than just filling in some metadata ? Do you know if there is any legal concerns that should be taken into account when confirmation is done server side ?
acoustic abyss
Not something we'd know anything about I'm afraid