magnetoise_error

[livid ember]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1280417612844634166

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[sonic hare]

A Elements group should have a Payment Element mounted before calling stripe.confirmPayment(). Could you share the minimal code that reproduces the issue, so that I can look into it further?

[rugged drum]

That answers the error, which happens because the payment element (which resides in the checkout page) gets destroyed (unmounted) when I navigate to the order confirmation page.

Given that, I'm not sure if what I want is possible (separate checkout page and order confirmation page), I guess I could technically create a new payment element in the order confirmation page, pass in the details received from the checkout page, and just hide it so it's still in the DOM but the user can't see it, but that doesn't look like good practice.

[sonic hare]

Could you share the code on how stripe.confirmPayment() is called in your integration? Once the confirmation token is created, you shouldn't need elements anymore