#oriolbv_api
velvet wagonBOT
đ 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/1493877524927610930
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
austere spire
and we are not able to test the flow.
Do you mean that the 3DS dialog does not appear?
untold frigate
correct!
we call the dialog in the frontend when the setup intent status is required_action
austere spire
You should be using "4000002760003184"
This card requires authentication for off-session payments unless you set it up for future payments. After you set it up, off-session payments no longer require authentication. However, on-session payments with this card always require authentication.
or "4000002760003184"
This card requires authentication on all transactions, regardless of how the card is set up.
https://docs.stripe.com/testing?testing-method=card-numbers#authentication-and-setup
they are the card numbers to trigger authentication
velvet wagonBOT
austere spire
Hmm, instead of using the Payment method that you created, could you try with this instead pm_card_authenticationRequired
untold frigate
what do you mean?? you mean to put this pm_card_authenticationRequired string instead of the paymentmethodId??
versed grotto
yes you can use the magic string as a way to trigger 3DS
untold frigate
but, let me clarify, this should be just for testing purposes? in production I should put the paymentMethodId right?
versed grotto
wait, I'm looking at your setup, and it feels a bit odd
why do you need to create a setup intent when you're already creating a Checkout Session in subscription mode?
since you already know the customer's email, you can either create the customer ahead of the Checkout Session and pass the customer ID (instead of the email) to the Checkout Session or you can use. https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-customer_creation and set it to true
in both cases, the PaymentMethod will be saved on the customer and you won't need an extra SetupIntent
untold frigate
Apart from the subscription of the client, the users can add a product that will require a new subscription, but this subscription will be created asynchronously when our provider approves our customer account. We just want to preauthorize it in order not to have an SCA when this subscription is created (or updated)
versed grotto
you don't need a SetupIntent for that
the PaymentMethod is already saved to be used off session
once it's attached to a customer, unless the issuer deems necessary the customer won't be asked to go through 3DS again
untold frigate
Okay, but the thing is that this behaviour is happening with several of our customers and we need a way to auto-approve this 3D Secure check when the user is still in front of the screen (that's why we thought that setup intents was what we need). See also this payment_intent.requires_action event (evt_3TLkqKDyCiiQ0txV15gSy2WX). What could we do to avoid this behaviour??
versed grotto
because you didn't pass off_session: true
that's what indicates to Stripe that the customer is not on session when this happens, so we would send the issuer a 3DS exemption request
velvet wagonBOT