#nicolejaneway
stark templeBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- nicolejaneway-element-events, 7 hours ago, 7 messages
rose fiber
Hello! Yeah, have a look at this guide: https://stripe.com/docs/payments/build-a-two-step-confirmation
karmic rock
I don't think this fixes the problem...
Ideally, the user could still edit their cart on the confirmation page.
So in my design, confirmation would be the final step before submitting the payment.
rose fiber
You can do that, but you would need to update the Payment Intent accordingly.
karmic rock
Ideally yes, but...
Invalid value for stripe.confirmPayment(): elements should have a mounted Payment Element or Express Checkout Element.
rose fiber
Not sure I understand?
karmic rock
The error seems to indicate I need to have a mounted Payment Element or Express Checkout Element
rose fiber
Can you share the code that's triggering that error?
karmic rock
Maybe I need to do something other than stripe.confirmPayment()
rose fiber
No, that's the right method, but I think you're passing the wrong parameters.
Can you share the code?
karmic rock
Yeah
rose fiber
Yeah, you're passing in elements there. The guide I linked you to uses stripe.confirmPayment, but it does not use the elements parameter.
You pass in the client secret from the Payment Intent instead.
I recommend you read the guide I linked to top to bottom and compare it to your current integration to spot the differences. It's a very different approach, but it uses some of the same APIs and methods and whatnot.
karmic rock
I will, thanks Rubeus!
rose fiber
Happy to help!