We were unable to process your order, please try again.
-
Hi, I hope you’re doing well.
Recently, my clients and I have encountered an issue during checkout. When placing an order, we receive the following error message:
“We were unable to process your order, please try again.”
I’ve already taken the following steps to troubleshoot the issue:
- Excluded checkout pages from caching
- Updated WooCommerce to the latest version
- Disabled the Order Attribution feature
Despite these actions, the issue persists. Everything was working fine before, so I’m unsure what’s causing this problem.
You can find a screenshot of the error here:
https://imgur.com/a/8xnT2i3And here is the System Status Report for reference:
https://gist.github.com/ismailpro25/29f766378067b22f09527296e5f7f4e8I’d really appreciate your help in resolving this as soon as possible.
-
Hi @omarjnani18,
Welcome to the WooCommerce forum, and thanks for sharing the details of the issue you’re facing. I completely understand how frustrating this must be, especially when everything was working fine before. You’ve already taken some excellent initial troubleshooting steps, including excluding the checkout from caching, updating WooCommerce, and disabling the Order Attribution feature.
Thank you as well for sharing both the screenshot and the System Status Report, which gives us a clear picture of your setup.
To better understand what’s happening, could you let us know when this issue first started showing up? Was it immediately after updating WooCommerce? If so, could you confirm which version you updated from, and the current version you’re now on?
I did notice in your System Status Report that there are several active plugins interacting with WooCommerce, and it’s possible one of them is interfering with the checkout flow. To rule out a plugin conflict, I’d recommend doing a quick conflict test:
- Temporarily deactivate all plugins except WooCommerce.
- Switch to a default theme like Storefront.
- Attempt a test checkout.
If the checkout works after doing this, you can reactivate your plugins one by one to identify which one is causing the problem.
If you prefer not to run this test on your live site, you can create a staging site using the WP Staging plugin and test there safely without affecting customers.
Let us know what you discover, and we’ll be ready to help from there!
Thanks for the prompt support and for outlining a detailed troubleshooting process.
I’ve followed your recommendations and performed the conflict test on a staging website by switching to the Storefront theme and deactivating all plugins except WooCommerce and Elementor. Unfortunately, the issue persists even in this minimal setup.
Additionally, I tried downgrading WooCommerce to versions 9.9.3 and 9.8.5, but the issue remained — and actually got worse. For example, during checkout, the order summary section keeps loading indefinitely, or I receive the following error message:
“There was an error processing your order. Please check for any charges in your payment method and review your order history before placing the order again.”
This issue first came to my attention yesterday, based on reports from clients.
I’ve also attached screenshots here for your reference:
https://imgur.com/a/xNHoeDNHi @omarjnani18 ,
Thanks so much for reaching out—and I’m really sorry to hear you’re still running into this issue.
When you get a moment, could you please share the System Status Report from your staging site? That’ll help us take a closer look and get a better sense of what’s happening.
In the meantime, have you had a chance to test placing an order using one of the default payment methods, like Cash on Delivery or Direct Bank Transfer? I’m curious to know if the same error appears with those options too.
Also, here’s a quick set of steps that might help reset things by Navigate to WooCommerce → Status → Tools:
- Clear WooCommerce transients
- Clear expired transients
- Clear template cache
- Reset capabilities
- Clear customer sessions
Once that’s done, clear your browser cache and test again. I’d also suggest temporarily disabling your CDN—since I noticed you’re using Cloudflare—just to rule out any caching conflicts during testing.
Let us know what you find—we’re here to help!
Hi @jonayedhosen,
Thanks for your continued support.
I’ve followed all the steps you recommended, including:
- Testing with default payment methods like Cash on Delivery and Direct Bank Transfer
- Running all the suggested tools from WooCommerce → Status → Tools
- Clearing my browser cache
- Temporarily disabling Cloudflare CDN
Unfortunately, the issue still persists after all of that.
Here’s a screenshot of the issue as it currently appears:
https://imgur.com/a/sD0G9EsAnd here’s the System Status Report from the staging site:
https://gist.github.com/ismailpro25/d5aa7aae002cf81059badeeff4c6159aHi there,
Thanks for the detailed info and for sharing the screenshots and system report.
I checked your checkout page and noticed a console error related to the REST API:
{code: 'rest_not_logged_in', message: 'You are not currently logged in.', data: {status: 401}}This error suggests that something—likely a script on the checkout page—is trying to make a request that requires the user to be logged in, but it’s not detecting the session properly. This can happen if:
- A plugin or script is interfering with how sessions or authentication tokens are handled.
- The page is heavily customized using a page builder like Elementor, which I can see is active on your site.
As a next step, I recommend:
- Temporarily disabling Elementor on the checkout page to see if that resolves the issue.
- If you’re using a custom Elementor checkout template, switch back to the default WooCommerce checkout to rule out template-level conflicts.
- Check for any custom widgets or scripts added via Elementor that might be sending requests on page load.
- Make sure that cookies and session handling aren’t being blocked by any security or optimization tools.
Let us know what you find after testing that, and we’ll be happy to help further!
Hi there,
Thanks again for your insights and for pointing out the REST API issue.
Following your suggestion, I tested by disabling Elementor on the checkout page. I also switched from the custom Elementor checkout template back to the default WooCommerce checkout. After these changes, I discovered that WooCommerce only works properly when all other related plugins are deactivated, including Elementor, FunnelKit, and CartFlows.
To give you more context:
- I’ve been using FunnelKit for a long time with no issues, and everything was working fine until now.
- As part of the test, I switched to CartFlows as an alternative, but I encountered the exact same issue:
“There was an error processing your order. Please check for any charges in your payment method and review your order history before placing the order again.”
Based on these tests, it appears that WooCommerce is currently not functioning properly with essential third-party plugins like Elementor, FunnelKit, and CartFlows—even though these are widely used and previously compatible.
https://gist.github.com/ismailpro25/3f9dde43ab856ec6a87d83ee75c98c4dHi @omarjnani18,
Thanks so much for the detailed testing and follow-up!
It’s clear you’ve done a thorough job narrowing this down. Since WooCommerce works properly when all third-party plugins are disabled, the next step would be to activate one plugin at a time—Elementor, FunnelKit, or CartFlows—to identify which specific one is triggering the issue.
Once you pinpoint the plugin, I recommend reaching out directly to its developers with your findings. They’ll be in the best position to confirm compatibility with the latest WooCommerce version and help with a fix.
Thank you for understanding!
That said, we’d be grateful if you could share your feedback here: https://wordpress.org/support/plugin/woocommerce/reviews/#new-post
Thanks again for reaching out!
As I mentioned earlier, I already tested the plugins individually—Elementor, FunnelKit, and CartFlows—one by one, and WooCommerce is not working properly with any of them, even when activated separately. The issue persists in all cases, which suggests this might not be caused by a specific plugin but rather a broader compatibility issue between WooCommerce and third-party integrations that previously worked fine.
So just to clarify—are you suggesting I now need to contact each plugin developer separately (Elementor, FunnelKit, CartFlows, etc.) even though they all show the same compatibility issue with WooCommerce?
Honestly, that doesn’t seem very efficient or logical, especially since the problem only started after recent WooCommerce updates, and these plugins were all working before.
the error i got now either still loading or this meassage when i placed the order at checkout:
“There was an error processing your order. Please check for any charges in your payment method and review your order history before placing the order again.”Hi @omarjnani18,
I completely understand where you’re coming from, and you’ve made a very valid point. It can definitely feel frustrating when multiple trusted plugins that were previously working smoothly start misbehaving after a WooCommerce update.
When WooCommerce rolls out a new release, it sometimes includes changes to how key functions or APIs behave under the hood. These changes, while often necessary to improve performance, security, or compatibility with WordPress core, can inadvertently affect third-party plugins, especially ones like Elementor, FunnelKit, and CartFlows that rely deeply on WooCommerce’s checkout flow.
Because these plugins extend WooCommerce functionality, any update on our end might require corresponding updates on theirs to maintain full compatibility. While we do our best to minimize breaking changes and communicate with developers ahead of time, some edge cases (like the one you’re seeing) only surface after updates are rolled out widely.
That’s why the next best step here would be to report the issue, along with your detailed findings and testing results, to the respective plugin developers. They’ll be able to check if they need to update their codebase to work properly with WooCommerce’s latest version, and in many cases, they can provide a hotfix or specific guidance.
We’re here to support anything WooCommerce core-related, and I really appreciate your patience and proactive troubleshooting throughout this. If there’s anything else you need help testing from our side, just let us know!
Thanks for the clarification and detailed explanation — that makes sense.
I’ll go ahead and reach out to the respective plugin developers with all the testing results I’ve gathered.
Appreciate your support and guidance throughout this process!
Hi @omarjnani18,
Thanks so much for your reply, and I really appreciate your willingness to take the next step by reaching out to the plugin developers directly. You’ve done an excellent job narrowing this down and providing all the relevant details, which will no doubt be very helpful for them in diagnosing compatibility issues on their end.
Please feel free to circle back here with any updates or feedback you receive from their support teams, we’ll be glad to take another look if anything further is needed from our side.
In the meantime, I’ll leave this thread unresolved for now. If we don’t hear back after about a week, we’ll check in to see how things are going before considering it resolved.
Looking forward to hearing how things progress!
Just to follow up—I’ve now tested again with only WooCommerce active (all other plugins fully disabled) and using the default Storefront theme.
Despite this minimal setup, the checkout page is still stuck loading, as shown in the screenshot below:
Screenshot: https://imgur.com/a/MRFxVT0
Here is the updated System Status Report for your reference:
https://gist.github.com/ismailpro25/d10d52f3ef7d1778cf4f91477faa4dc0This confirms the issue is not related to any third-party plugin or theme, and seems to originate within WooCommerce itself.
Looking forward to your guidance on how to proceed from here.
Hi @omarjnani18,
Thanks so much for the detailed update, the new screenshot, and the updated System Status Report. I appreciate how thorough you’ve been in testing and documenting everything.
I tried visiting the staging URL listed in your report (https://iptvnorway.no/staging) to test the checkout flow directly, but it redirects to https://www.iptvnorway.no/best-iptv-norway/, which doesn’t allow me to replicate the checkout issue you’re seeing.
If this were a core WooCommerce issue, we would likely be seeing widespread reports from other store owners encountering the same failure on a minimal setup. Still, at the moment, this appears to be isolated to your environment. This suggests that the problem may be related to your server configuration, custom settings, or a caching/security rule at the server level that interferes with session handling or REST API calls.
Would it be possible for you to temporarily make the staging site publicly accessible and provide the correct checkout URL where the issue can be tested? Once I can access the live checkout flow, I’ll gladly test and share my findings.
Looking forward to digging deeper into this with you!
Thanks again for your time and support — I really appreciate it.
Regarding the staging site, there’s a redirection from iptvnorway.no to iptvnorway.no/best-iptv-norway/, which is why you were redirected.
To access the staging environment directly, you just need to add /staging/ after .no/ in the URL.
For example, the correct checkout URL would be:
https://iptvnorway.no/staging/checkout/Please feel free to test the checkout flow there. The issue is still present, and I hope this will help you investigate further.
Thanks again for your continued assistance!
The topic ‘We were unable to process your order, please try again.’ is closed to new replies.
