#Aquitaine=connect
1 messages · Page 1 of 1 (latest)
So if you had Radar disabled entirely, Stripe would just reject all cards requiring 3DS?
Actually, let's back up for a second - what does your integration look like right now? Are you using Charges? Payment Intents?
PaymentIntents
We create them when the customer is in the checkout stage and then confirm them once they submit payment
How do you confirm them? client-side? server-side?
We've been doing this since 2020 and have never seen this come up before though
Server side
The only client interaction we do is to get paymentMethods
Gotha - and when you make the confirm request do you also set 'off_session: true' (https://stripe.com/docs/api/payment_intents/confirm#confirm_payment_intent-off_session)?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
We set it to true, since the customer is in the payment flow
err, false
sorry. we set it to false
I believe if you set 'off_session: true' when you confirm, it'll fail if authentication is needed
which is the behavior I think you want
Are there any other implications of setting it to true that we should be concerned with?
I'm not 100% sure of the other implications (usually this is asked from the perspective of users who care about 3ds exemptions and such, and you're using it for something very different).
You could also just slightly change your integration to handle if the server-side confirmation resulted in a status of 'requires_action' and surface that as an error to your customers
Hmm, okay. Thank you!