tiffbytes_code

[boreal shore]

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

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

[glacial yarrow]

What kind of 3DS result are you looking for? Could you share your use case in an example, so that I can understand your ask better?

[pastel heart]

hi River, thanks for responding. After integrating the stripe SDK using the "Complete Payment on your UI" section, I've been testing the integration and noticed that once I invoke the flowController.confirm() and when using test cards like "4242424242424242' and "4000582600000102" I get a screen similar to the once attached.

In my logs I can see that the Stripe3ds2TransactionActivity is created followed by the PaymentLauncherConfirmationActivity

however, I can't seen to find a way to retrieve the results of what I assume is an attempt to determine if 3ds is necessary. And with no callback, I can't continue my checkout flow to either have the user re-attempt or close my own UI

My aplogies for not adding this earlier, but I'm also using the Android SDK and trying to complete the client flow

[glacial yarrow]

however, I can't seen to find a way to retrieve the results of what I assume is an attempt to determine if 3ds is necessary.
Could you share the reason why you need to find out why 3DS is necessary? Payment Sheet will handle the authentication like 3DS automatically when required. There shouldn't be a need to handle any additional action when Payment Sheet is used. Or are you looking for whether a Payment Intent has gone through 3DS after a payment attempt? It'll be helpful to share your business use case / real scenario, so that I can understand what information you're looking for and suggest the solution accordingly

[pastel heart]

The main issue I'm facing is that the flowController's paymentResultCallback isn't being invoked and no payment result is being sent back anytime I use any test cards that requires 3DS.
So currently, when a user uses a card that doesn't go through a 3DS auth, I receive the PaymentSheetResult through my callback.
However, if a user uses a card that does require 3DS auth, I do not receive any PaymentSheetResult in my callback.

Is this expected?

[glacial yarrow]

The main issue I'm facing is that the flowController's paymentResultCallback isn't being invoked and no payment result is being sent back anytime I use any test cards that requires 3DS.
Did you complete the 3DS in the screenshot? If the 3DS is completed (regardless failed or successful authentication), there should be a payment result callback. Could you also share an example Payment Intent (pi_123) which has gone through 3DS, so that I can check how your integration works?