#lukasz_docs

1 messages ¡ Page 1 of 1 (latest)

jaunty karmaBOT
#

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

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

cedar marsh
#

Looking for the right docs that describe this in more detail, but the overall answer is that generally 3DS isn't required for subsequent charges, but it's up to the bank, and they can sometimes require 3DS for such charges. This won't happen for every recurring charge, but your integration must be designed to handle this case

summer dew
#

ok so in case of subscription charges I see that in case it fails I can grab latest payment intent and client_secret from there to trigger 3dsecure prompt again (so trigger for customer stripe.confirmCardPayment(client_secret) which upon successful challenge completion of user next rebill attempt on stripe should pass)
but if user does not have a subscriptoin and just purchases a one time product then they will be asked for 3dsecure - that is expected
but if user tries to purchase another one time product again using same payment method then, will they be asked again? I understand it is up to the card issuing bank to determine that, right?

#

I would like to avoid situation when customer is prompted every time they purchase one time products if possible

cedar marsh
#

Yes, that's correct. For the last case, there can be additional friction that is reduced if the customer is using a saved payment method

#

But as you summarized, your integration always has to account for the possibility of the bank requesting 3DS, and Stripe will optimize as much as possible to avoid it happening unnecessarily

summer dew
#

ok, is there a stripe test credit card that can mimic "real frequency of 3dsecure prompts" for one time purchases (I could not find such in docs unfortunately) or do I have to test with real credit card to confirm how often I am asked for 3dsecure?

cedar marsh
#

I don't believe there is a test card for this, but I'll double check

#

No test card for this use case, you can see the available cards here:
https://docs.stripe.com/testing#authentication-and-setup

I would say the best approach is to test your integration to make sure it handles 3DS as we discussed, then monitor the live authentication analytics as described here
https://docs.stripe.com/payments/analytics/authentication

If you see unusually high numbers then you can reach out to support and we can determine if it's something unusual, bank related, integration related, etc

summer dew
#

Thats good, I will have a look also at those, thank you very much!