#drae_unexpected
sudden baneBOT
đ 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/1437828336737976342
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
ebon yew
hi there! if this is an off session payment, then you should create the Payment Intent while setting off_session to true. this will help avoid 3DS verification https://docs.stripe.com/api/payment_intents/create?api-version=2025-10-29.preview&rds=1#create_payment_intent-off_session
it's worth noting though that banks can request 3DS even for off session payments. it's pretty rare, but it happens. when it does, your integration will need to handle bringing the user back on-session to finish the payment
timid ruin
Is there a way if you can check whether the bank caused this?
I will double check the integration in case this has been changed on our end to remove setting 'off_session' => true on the creation of the Payment Intent
ebon yew
it looks like a standard bank-initiated 3DS action to me
timid ruin
Does that mean it would have happened even if I did set off_session true on Payment Intent creation API?
ebon yew
that I can't say. it's up to the bank to determine whether to initiate 3DS, Stripe doesn't control it