#krunner-salesforce-connector
1 messages · Page 1 of 1 (latest)
Hi, it should support it. Are you seeing otherwise while testing? If so, do you mind sharing the request id with me? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Thanks! Yes this is a requestId from a production account where we first noticed the issue: req_KueMK9Irj5ETsa. The screenshots below are for the production account. (I also reproduced the error in a test mode account: req_k97Iji2v814f2D)
I'm trying to understand what happened here. It looks like it got stuck on 3D Secure.
The connector should support 3DS. We can't really help with this here unfortunately as this is not about your own code. You'll need to reach out to our support team for help: https://support.stripe.com/contact/email
krunner-salesforce-connector
Ok thanks
Just in principle, if I've created and confirmed a payment intent with setup_future_usage=off_session and the customer successfully authenticated 3DS when that happens, if I use that token to do an offline payment, how does Stripe handle 3DS? Does it require customer to reauthenticate, and if so, how would the customer be notified if it's an offline transaction?