#ebellotpu6
1 messages ยท Page 1 of 1 (latest)
Hi ๐ so to confirm, you're performing the Setup Intent confirmation from your server-side code?
yes
but as I have said, after creating the paymentmethod and attaching a customer_id to it, I am getting 'Missing required param: mandate_data.' when I try to confirmSetupIntent
Gotcha, in that case you will need to provide the mandate_data hash and include the details of the mandate acceptance that you got from your customer:
https://stripe.com/docs/api/setup_intents/confirm#confirm_setup_intent-mandate_data
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
and how I can get this hash?
You need to provide it.
If you're doing server-side confirmation, then you need your own custom flow for collecting permission from your customers to run those transactions. You then provide the details of how you got that permission to us, via the mandate_data hash, when confirming the related intent.
so, for example I have to provide the ip and the browser agent?
If you're collecting mandate acceptance in an online fashion via your website.
Alternatively you could use our recommended approach for preparing SEPA payment methods for future use, which uses a Setup Intent with client-side confirmation so Stripe.js can collect the mandate details for you.
https://stripe.com/docs/payments/sepa-debit/set-up-payment
yes, but this works with stripe elements
and I can't get the iban number with them...
Why do you need direct access to the iban?
If that is a necessity for your flow, then you will need to continue down your current integration path and will need to add mandate collection to your flow.
because the clients will pay through subscriptions and If one day, the business decides to migrate out of stripe, they will need to get the iban numbers to maintain the subscription
Okay, you will need to collect mandate acceptance from your customers then, and you will need to provide details of that acceptance to us.
and with source it would be possible?
I don't understand the question
Is this a new integration you're building? If so I would not recommend this flow, as suggested by the warning at the top of the documentation about this approach being considered deprecated.
yes, it is new
Then I would not recommend using the Sources flow.