mekhami-payment_element | Stripe Developers | Page 1

heady jewel Sep 20, 2022, 3:55 PM

#

If you're creating an entirely new Payment Intent then I don't think there's any way around doing the full re-render. The only way around this would be to update the PaymentIntent that was already created

worn iron Sep 20, 2022, 3:56 PM

#

I know you're not involved with this, but my example was https://donate.wck.org/give/417669/#!/donation/checkout

If you look at that one, they render the stripe card element and then the user can go back and change the amount without that element re-rendering. Is this an implementation detail of their application?

#

maybe they are updating the payment intent rather than creating a new one...

heady jewel Sep 20, 2022, 4:04 PM

#

This is because card element and payment element have some fundamental differences - the card element doesn't require a payment intent in order to be rendered, while the payment element does

worn iron Sep 20, 2022, 4:05 PM

#

with this configuration, if i were to update the payment intent, would i be able to pass the updated payment intent to the stripe elements api and not re-render the form?

heady jewel Sep 20, 2022, 4:09 PM

#

^^ are you still wanting to use the card element or the payment element?

worn iron Sep 20, 2022, 4:24 PM

#

the payment element

heady jewel Sep 20, 2022, 4:26 PM

#

Gotcha - so yes, if you were to update the existing element you wouldn't need to re-pass it or anything. When you go to complete/confirm the payment, Stripe already knows the PI has been updated and it'll confirm the updated payment intent. The big downside with this is that some payment method types (like google pay and apple pay) surface the amount in the UI, so if you don't re-render the Payment Element they'll show the older values

#mekhami-payment_element