Orders shows up as draft orders - customer tried to pay, reached thank you page and was not charged for it. ( i went through the whole flow myself , “paid” and wasn’t charged for it, order appears as draft. This has been close to 1 month now and a HUGE issue.
I have feedback to support at least 10 times since the upgrade. Same promise - the dev will get back to them and they will get back to me. They never did
Even here - i have DM u guys. the reply is “I just forwarded it to dev channel with high priorities.” and NOTHING gets solved. its been WEEKS
Its frustrating really. This is a core feature. You guys are costing thousands of dollars lost.
I know someone will ask me to dm the checkout URL, and promise the dev will fix it and nothing happens and the cycle repeats again.
Hi @RYgy I’m very sorry for the impact this has taken and I completely understand the frustration.
This is far from the support experience we want to deliver to our users. I was able to find your ticket and currently looking into it personally with the backend team to provide you a proper update/response.
I heard this more 10 times now. I know i will not heard back from u guys.
The next time i tell i will get a reply “oh you are still having this issue?”
Its a joke honestly. today my payment was down again when no changes was done to the funnel. Slapped with a Error code on the payments losing thousands of dollars in a day. All orders via credit card marked as draft order.
Totally understand how frustrating this must be, especially when it’s affecting live orders. I just want to let you know that both the Airwallex and Funnelish teams are actively working on this issue.
The Airwallex team has already noticed some API errors during the payment calls, and they’re currently digging deeper into the cause. We know this is a serious issue and it’s getting top priority right now.
Apologies for the experience you’ve had in support, I was able to find your ticket where we notified you that it was currently being looked into with Airwallex’s support team who are investigating why these 400 errors are showing up while calling their APIs.
We will keep you posted in both that conversation and here as well.
Appreciate you bearing with us and if you have any other issues, please don’t hesitate in letting me know.
