#DeliveryTiem
1 messages · Page 1 of 1 (latest)
If you are using a us_bank_account payment method then you do need to collect a mandate.
Ah okay, thanks for letting me know about this I hadn't seen this.
I thought that if you marked a payment method as set up for future use then it wouldn't need anymore customer interaction.
Well you can collect/confirm the mandate in the initial payment process when you are also setting it up for future usage.
So when we initially take the payment via the 1st payment intent, I have this option set to off_session: https://stripe.com/docs/api/payment_intents/create#create_payment_intent-setup_future_usage
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
But banks can also change what they wish to require
What do you mean by that, if you can answer it in another way?
The banks we communicate with are at liberty to change what information they require to process a payment. Examples include mandates and 3DS authentication.
So for example, I can get the user's bank info and add it to a payment intent and set the intent's 'setup_future_usage' to 'off_session', but the bank can still request authentication/mandates from the customer to approve a payment through that bank account when I create a new payment intent in the future?