- Issue created by @SadySierralta
- 🇪🇸Spain SadySierralta
The code might lead to an order missmatch exception, checking if possible to make a solution.
- 🇪🇸Spain SadySierralta
Reloading the order again and checking in paymentSuccess if the order is complete (completed by commerce payment updater after saving payment in the onNotify) before saving seems to be working, not the best approach but i think it is ok.
- Issue was unassigned.
- Status changed to Needs review
9 months ago 10:59am 5 April 2024 - Status changed to Needs work
9 months ago 8:57am 11 April 2024 - 🇪🇸Spain SadySierralta
We should probably use checkout.session.completed instead of payment_intent.succeded to keep the context.
- Status changed to Needs review
9 months ago 11:30am 11 April 2024 - 🇬🇧United Kingdom joehuggans Harrogate, UK
I've been playing around with this and seems to work well, apart from if you have guest checkout enabled and "Create a new account for an anonymous order" also enabled, sometimes the new user is not created, and looking at the orders, the order remains stuck in cart.
I'll do some more testing and hopefully if I figure out what's causing it, report back.
- 🇬🇧United Kingdom joehuggans Harrogate, UK
After some further testing I believe this is working, I'm not sure what was causing the onNotify method to not run previous.
However, I think we need 2 Signing secret fields, for test and live mode.