#learner-confirm-setup-intent
faint echo
Hey @half crow Sorry, I mean if we want to setup credit card for future payments, do we need to call both setupIntents and confirmCardSetup methods or just setupIntents is sufficient?
half crow
Yes, you'll need to use confirmCardSetup with Stripe.js to handle any required auth/3DS
See this doc: https://stripe.com/docs/payments/save-and-reuse
faint echo
@half crow do we know if for US, there is any additional auth/3DS applicable?
(I know it is applicable for Europe but not US)
arctic rover
Hi there 👋 SCA/3DS isn't common in the US yet, but it might be necessary. It's up to the issuing bank whether or not they require it.
Personal anecdote: I've had one purchase in the US require a 3DS flow.
faint echo
oh ok. Are there any sample credit cards for US with auth/3DS which can be used for testing purposes?
arctic rover
Yup, we have quite a few test cards for testing various 3DS flows:
https://stripe.com/docs/testing#regulatory-cards
arctic rover
This card will always require 3DS:
4000002760003184
faint echo
Thank you. If you feel comfortable, do you mind sharing the issuing authority of your personal credit card in US which needs 3DS (only if you feel comfortable).
I want to understand which entities are mandating 3DS in US, or giving customers an option to opt-in for 3DS. In Europe and India, this is a mandate. I understand in US it is not as of now. But curious if opt-in is started
arctic rover
Sorry, it was like 6 months ago and I don't recall who the issuer was.
faint echo
Thanks Toby. That helps. If possible, please dig around more and suggest if there is any valid credit card issuer as of now, which mandates/makes optional by customer to opt-in for 3DS in US. This would be of great help.
Our current flow assumes there is no 3DS
(Our customers are US only)
We currently don't use Stripe in production, and are in the process to switch to Stripe
arctic rover
Happy to help, but we don't have an exhaustive list of issuers and their 3DS requirements.
faint echo
Is there an option to get some additional query params filled by Stripe when 3DS is complete?
If we do, we can use the same page to handle the state when 3DS is complete, else we may need to adopt a different strategy like store the state in localStorage and retrieve back when page gets reloaded
arctic rover
I'm not sure I follow
faint echo
In order for 3DS to complete, it may be required to redirect to a different URL to enter one time password. We do have a callback url which we share which Stripe will load once 3DS is complete. Since we will be moving away from the page and reloading it on 3DS success, we either need a different page for handling state suggesting 3DS is complete or need to adopt a different strategy if we try to load the same page from which initial redirection was made to complete 3DS
arctic rover
Gotcha, when redirecting back from the bank's page the redirect includes payment_intent and payment_intent_client_secret to the URL as query parameters:
https://stripe.com/docs/payments/3d-secure#when-to-use-3d-secure
faint echo
Awesome. Thank you