jasoomine_unexpected

[tribal bane]

👋 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/1215410858641858622

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[pure sundial]

we are also not using the Stripe SDK in the Android and iOS apps

[placid hemlock]

It sounds like this is an issue with the deeplink back to your app

[pure sundial]

Our API team handles generating the stripe url, and they generate the Payment Intent on their side

I checked with our API team and they said they didn't see issues with the deeplinks that are generate to reroute back to our apps. and when testing using the Test SCA cards in a test environment, we are successfully deeplinked back into our app. I think the edge case here is that if we leave the stripe webview to go to the background or another banking app, that deeplinking action gets lost somehow

[pure sundial]

I was wondering if you have heard of cases where 3DS/SCA works fine in test environments using test cards, but will run into issues in production when SCA flows are more complex and interact with more external banking apps

[placid hemlock]

It is possible, yes, since bank 3ds flows don't always behave nicely

One option to explore is redirecting first to you own server endpoint

Then subsequently redirecting to your app deeplink