horrorcheck-payment-element-google-pay

[dusty tusk]

Hi 👋 this happens because the payment element triggers the Google Pay flow and is still holding the information that it retrieved from the payment intent when the element was initialized.

I can't recall off the top of my head if unmounting/remounting the element is enough to refresh it's info, or if you'll need to reinitialize it in order to get it to refresh.

When the payment actually is processed it uses the underlying payment intent though, which is why the process still charges the correct amount even though it doesn't show the right value.

[hybrid grove]

Okay, thanks very helpful 🙏

I'll try out the mount/unmount thing

[dusty tusk]

Happy to help!