#perqin
1 messages · Page 1 of 1 (latest)
👋 happy to help
hi! this is because we only simulate those flows in the "native 3DSv2" implementation(where our SDK can present native components in the app). But we are actually experimenting with turning that off and falling back to web-based authentication, since in production we find that bank's implementations of the native flows have problems that lead to lower successful payments
so we fall back to the web page, and that doesn't support those other options, it just shows the generic button
Some information:
I'm integrating Stripe's RN SDK, and after receiving "status: requires_action" from the POST/payment_intents API, the client calls the "handleNextAction" SDK API to launch the 3DS auth flow.
So currently, on the "Out of band" test card is working as expected now, right? Then we're considering only testing that scenario.
right now all the cards do the same thing, which is they open the web-based 3D Secure flow, and in our test mode implementation we only have a "success/cancel" button in that flow
the 3DSv2 specific test cards unfortunately don't work today and you can't test with them since in many cases we've disabled the native 3DSv2 implementation they're connected to