#Kasuni
copper pond
lilac girder
pi_3Mc4llGBcm8kohcp1I64xuCk
candid zenith
Thanks. Well this is expected. You used a test card that always requires authentification, so you need to confirm the PaymentIntent on the frontend now (and not the backend) to go through the 3DS flow.
lilac girder
Hi Can you bit explain how to confirm payment in front end while i am using the stored card?
candid zenith
I recommend reading this guide that covers this: https://stripe.com/docs/payments/save-and-reuse?platform=web#charge-saved-payment-method
lilac girder
Is this type of card can be stored in live environment?
candid zenith
Yes you can store a card in a live environement. And when you try to charge it it will either work right away or it will require 3DS. This is completely up to the bank.
lilac girder
Can we check whether what is the card type when they are storing it to the system? ( that mean is the card is always authenticate or not)
candid zenith
You can't know that in advance no.
But once you create the PaymentIntent, if status is require_action, then you know that 3DS is requested.
lilac girder
is require_action comes when setup intent is created ?
candid zenith
It can happen for both SetupIntent and PaymentIntent. And it completely up to the bank to decide when they will require 3DS or not.
lilac girder
Hi, i am bit confusing here.what would be the cardElement when i confirm the payment using stored card in front end
candid zenith
You use this, which only needs the client secret of the PaymentIntent: https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-attached
visual badger
👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!