Muhammad Awais

[normal nacelle]

Potentially yes. Your integration should assume 3DS/auth could be requested for all payments regardless of card country/origin

[jade bloom]

And it always have to be redirected another website?

I am integrating the stripe in SPA

[normal nacelle]

What's the actual problem you're trying to solve?

[jade bloom]

I am just trying to handle all the case for stripe elements

[normal nacelle]

Ok, but why would US cards be different? If you're using confirmPayment then the integration will handle all 3DS redirects automatically

[jade bloom]

I read somewhere that 3D secure is mostly in European countries

[jade bloom]

it can redirect to another website right?
that's why we provide the return_url

[normal nacelle]

Sure, there's regulation that around authentication for online payments in Europe: https://stripe.com/docs/strong-customer-authentication/sca-enforcement

Just not sure why that'd concern you if you're using Elements and Stripe.js – that integration will handle 3DS for all cards whenever requested, regardless of country

[jade bloom]

Because of this
Because I have SPA, if a user will be redirected to another website, user's data will be lost because I am not saving all the information until user pay

[normal nacelle]

Yes, there's details on this here: https://stripe.com/docs/payments/3d-secure#when-to-use-3d-secure
You can opt to include the 3DS UI in an iframe on your own page if you prefer

[normal nacelle]

Then I'd recommend passing state to the return_url as URL parameters

[jade bloom]

ok

I have asked the user billing details, captured the required amount,
Now I have created another off session payment intent and it throws an error

How can I update my existing stripe element for this new payment intent?

[normal nacelle]

What's the error?

[jade bloom]

Maybe insufficient funds

                elements.value = stripe.value.elements(
                    {clientSecret: paymentIntent.clientSecret}
                )

would that work?

[normal nacelle]

How can I update my existing stripe element for this new payment intent?
You'd have to create a new Elements instance with the new client_secret. Alternatively, if your amount varies before your users pay consider the deferred flow: https://stripe.com/docs/payments/accept-a-payment-deferred

[jade bloom]

so above won't work?
I think that's replacing the old elemnts with new one?

[normal nacelle]

No I don't think it will

[jade bloom]

Is there a method to unmount the existing element?

[normal nacelle]

https://stripe.com/docs/js/element/other_methods/unmount

But that won't help for what you need to do. You don't need to unmount the Payment Element, but the Elements instance

[jade bloom]

so cardElement.destroy(); ?

[normal nacelle]

As I said, if you're Payment Intent values are constantly updating (like a cart scenario where your customers update quantities, add/remove items) then you're better off using the deferred flow

[normal nacelle]

Are you using Payment Element or Card Element?

[jade bloom]

card element

With payment intent

[normal nacelle]

Then I'm not sure why you're passing the clientSecret argument to the Elements instance

[normal nacelle]

That's only needed for the Payment Element, otherwise you pass ity when you call confirmCardPayment

Ok, so you are using the Payment Element

[jade bloom]

I was thinking this is a card element, what's the diff?

[normal nacelle]

https://stripe.com/docs/payments/payment-card-element-comparison

[jade bloom]

so for payment element what do I need to do to assign another payment intent's client secret?

[normal nacelle]

You need to initialise a new Elements object via elements.create. They can't be updated