Pain-confirm-payment

[hollow snow]

What product are you using to handle the payment lifecycle? (e.g. Payment Element? Card Element? Checkout? eetc.)

You shouldn't need to worry about getting the link for things like 3DS auth

[stable rapids]

So I already collected the payment method from previous checkout using payment elements. Now I am attempting to charge them and trying to deal with the authentication_required status

I used this https://stripe.com/docs/payments/save-during-payment

[hollow snow]

Ah, okay. You'll have to bring the customer back to a page where you'll call stripe.confirmCardPayment() with the Payment Method ID and the client secret of the Payment Intent: https://stripe.com/docs/js/payment_intents/confirm_card_payment

From the docs linked above: If you are using Dynamic 3D Secure(https://stripe.com/docs/payments/3d-secure#three-ds-radar), stripe.confirmCardPayment will trigger your Radar rules to execute and may open a dialog for your customer to authenticate their payment.

[stable rapids]

Ah alright, so I have to send them back to my site and use stripe.confirmCardPayment with the payment method ID & client secret

Then a 3D auth frame will be opened and handled by Stripe?

Will this create another charge or will it update the initial charge created?

[dusk escarp]

👋 Stepping in here

Then a 3D auth frame will be opened and handled by Stripe?
That's correct

It won't be another

[stable rapids]

Got it, I will go ahead and test this out shouldn't have any issues, thank you.

[dusk escarp]

NP! 🙂

Good luck

[stable rapids]

Quick question

Why is the paymentintent retrieved again in the docs?

the (err) already returns all the data alongside the intent, is this necessary?

[dusk escarp]

I'm not sure but the next section might be using it for something

if you have it already then don't think you need to fetch it again

[stable rapids]

Alright, just making sure; thanks again.