#mramik
1 messages · Page 1 of 1 (latest)
Hi there!
This is expected. The bank may required 3DS at any point, event after a SetupIntent was successful. So your code needs to handle the case where 3DS is requested. You basically need to tell the user to come back to your website/app and then re-confirm the PaymentIntent on the frontend with https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-attached
Oh okay, thank you for your response. We're using a full BE php integration (payum, to be precise, within a sylius app) to handle setup -> payment intents ... isn't there a parameter to provide, like setup_future_usage => 'off_session, or other to indicate that the 3DS validation already happened ? In the payment intent creation we're putting 'confirm' => true, I guess it is different from the confirm_card_payment you're referencing to ..?
like setup_future_usage => 'off_session'
This parameters allows you to make off session payment with that payment method in the future. But still, the bank may ask for 3DS, there's no way around this.
Okay, thank you !