#edgar-soloviev_3ds-just-once
twilit flameBOT
👋 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/1229780727508504617
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
boreal crestBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- edgar-soloviev_api, 6 days ago, 6 messages
fringe granite
Hi there 👋 it's not possible to build a flow that guarantees 3DS will only ever be triggered one time. It's up to the issuer of the card being used for the payment to decide whether they will require 3DS be completed or grant an exemption to that, so every payment has the possibility of having them require a 3DS challenge be completed.
You can minimze the likelihood of that though. How are you handling the second payment currently, and what test card are you using to test your flow?
twilit flameBOT
edgar-soloviev_3ds-just-once
safe saddle
I'm using this card 4000000000003220. So if I create a subscription with trial period. then after the trial expires the user will have to pass 3DS?
I also used this card 4000002500003155
fringe granite
I'm using this card 4000000000003220. So if I create a subscription with trial p...
Correct, and that test card simulates 3DS always being required so it's good for testing edge cases where issuers may request 3DS outside of when you're hoping.
3155 is the better card for testing if the setup process is working as expected.
safe saddle
Do I have the process described correctly or is there something else that can be changed to minimise the 3ds check?
fringe granite
It sounds right so far, but I don't have much context on what you're doing for the second payment. You're not using setup_future_usage for those and are creating them as off-session payments?
safe saddle
For the following payments I use only these parmters, customer, amount, currency and payment_method
fringe granite
Ah, sounds like you're missing a bit if you aren't then making another request to confirm the intent.
You'll also want to pass off_session and confirm, both set to true.
There is an example here in Step 7 that you can use as a reference:
https://docs.stripe.com/payments/save-during-payment?platform=web#charge-saved-payment-method
safe saddle
Forgot about that. There were a lot of tests. I made a request for confirmation. Am I right that if I use this card for the 3155 test, I won't always get a link to the bank page when I confirm?
fringe granite
That is correct, that card should only require 3DS if it hasn't been successfully set up as a payment method previously.
safe saddle
Thank you. You've been very helpful.