#gallopinggoose_14721
fathom hawk
mortal shell
For example, this is an old response (https://dashboard.stripe.com/test/logs/req_Cn5MLxnZHlDA2r) vs new (https://dashboard.stripe.com/test/logs/req_ZQ3I0gOx8nQPeE)
I found this older thread about a similar change and thinking it may be related? https://github.com/stripe-archive/react-stripe-elements/issues/405
cold shale
So the issue is just with how the response looks when using a test card, right? This is presumably for tests you run against your integration, which started looking different recently?
mortal shell
Yes. The request paramters didn't change and the response we are getting is different. I couldn't find any documentation on what to expect for 3DS responses or changes
cold shale
I'm not finding anything that indicates a change. Does this break your test for some reason?
mortal shell
Yes we are using the url given in next_action.use_stripe_sdk.stripe_js for our iframe testing
The new response seems to have a "three_ds_method_url" but it is empty
cold shale
Let me dig a bit more and circle back
mortal shell
Thanks
cold shale
Okay, so I figured out what's going on
Basically, this is expected. On PaymentIntent, the next_action tells you what to do next. In your example requests, they both say use_stripe_sdk which means you should use Stripe.js client-side for example to confirm the PaymentIntent and have us handle 3DS for you.
What's inside use_stripe_sdk is something purely internal to Stripe so I would not recommend using that for anything in your flow. And for 3DS2 Test cards for example the shape is different from the old 3DS1 Test cards that had a URL redirect.
Does that make sense?
void hare
What you can alternatively do in your tests is pass use_stripe_sdk: false on confirmation which changes the shape to use redirect_to_url