• Resolved jfstyle

    (@jfstyle)


    Good afternoon! The store has a Direct bank transfer payment set up. When selecting this payment, an error pops up: 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. The client remains on the checkout page, the order is generated in the admin panel, but the email to the client with the payment details does not go away.

    • This topic was modified 5 months ago by jfstyle.
Viewing 15 replies - 1 through 15 (of 44 total)
  • Hi @jfstyle,

    I see how this checkout error appearing with Direct Bank Transfer can be confusing, especially when the order is still being created in the admin but the customer remains stuck on the checkout page and does not receive the payment instructions email. I will be glad to help look into this and narrow down what might be causing the behavior you are seeing.

    To better understand the situation, could you please clarify when you first started noticing this error? Was it after a recent change such as a WooCommerce update, a theme or plugin update, or a settings change, or was everything working as expected before? Also, is this a brand new store setup or an existing store where this flow previously worked without issues?

    It would also really help to see exactly what is happening on the checkout page. If possible, please share a short screen recording using https://loom.com, or a screenshot of the error message using https://snipboard.io so we can see the full context.

    Finally, could you share a copy of your WooCommerce System Status Report so we can review your environment and configuration details? You can copy the report from WooCommerce, Status, System status, and paste it into one of these services, then share the link here: https://pastebin.com.

    Once we have those details, we can take a closer look and guide you on the next best steps.

    Thread Starter jfstyle

    (@jfstyle)

    This store has not previously used a direct bank transfer. I am testing this payment method for the first time. I am attaching a video of the process. thank you!

    [video src="https://skrinshoter.ru/v/090126/mU0NcCkH.mp4?view=1&name=Видео-09-01-2026%2010:31:55.mp4" /]

    Hi @jfstyle,

    Thank you for sharing the screen recording of the issue on your end. It really helps to see the full checkout flow and confirms exactly where things are breaking, so we can focus on the right areas and move this forward efficiently.

    To take a closer look at your store environment and configuration, could you please share your WooCommerce System Status Report. You can find it under WooCommerce, Status, System status. Once copied, please paste it into https://pastebin.com or https://gist.github.com and share the link here.

    With that information, we can review your setup in detail and advise on the next steps to resolve the Direct Bank Transfer checkout behavior you are seeing.

    Thread Starter jfstyle

    (@jfstyle)

    Plugin Support Frank Remmy (woo-hc)

    (@frankremmy)

    Hi @jfstyle,

    Thanks for sharing your system report.

    This type of issue is often related to email delivery problems or conflicts with plugins/themes. Let’s start by checking a few things:

    1. Go to WooCommerce → Status → Logs and look for any error messages related to emails or the bank transfer payment method.
    2. Try sending a test email from WordPress (like a password reset) to see if emails are working at all from your site.
    3. Since you have several plugins active, try temporarily deactivating non-essential plugins to see if one is causing the conflict.

    Also, have you noticed when this issue started, or has it been happening since you set up the bank transfer payment method?

    Looking forward to your response.

    Thread Starter jfstyle

    (@jfstyle)

    Thanks! the problem was with the smtp settings. Hosting support has solved everything!

    Hi @jfstyle,

    Glad to hear that everything is now working smoothly and that the issue was traced back to the SMTP settings. It is great that your hosting support was able to step in and get this resolved, and I appreciate you coming back to share the update, it will certainly help others who may run into a similar situation.

    If you have a moment, we would really value your experience being shared with others. You can leave a review for WooCommerce here, https://ww.wp.xz.cn/support/plugin/woocommerce/reviews/#new-post. Your feedback helps the team continue improving the plugin and the support experience.

    Feel free to reach out anytime if you need help with anything else, and I wish you all the best with your store going forward.

    Thread Starter jfstyle

    (@jfstyle)

    Goodnight! I have to reopen this topic. The error appears again with all payment options and only if I enable mandatory registration when placing an order. If guest purchase is enabled, then there is no error.

    Hi @jfstyle,

    I understand how frustrating this is, especially after things appeared resolved and the error now returns only when mandatory account registration is enabled. I am keen to help narrow this down and get you back to a stable checkout experience.

    When checkout requires account creation, WooCommerce relies on user registration, password generation, and email sending all in one flow. Issues like this are commonly linked to email delivery, user creation hooks, or a plugin or theme conflict that only triggers during registration.

    To move this forward, could you please confirm whether you have already tried the plugin conflict test that was suggested earlier, with all non essential plugins disabled and a default theme temporarily active, then testing checkout again with mandatory registration enabled. This helps confirm whether a specific plugin or theme is interfering with user creation.

    Also, when you have a moment, it would be really helpful to see a short screen recording of this latest behavior with mandatory registration turned on. Please feel free to use https://loom.com video and share the link here so we can clearly see what happens at the point the error appears.

    Once we confirm those two points, we can guide you on the next best steps with confidence.

    Thread Starter jfstyle

    (@jfstyle)

    I changed the theme to the standard one, turned off the plugins – the result is the same. The error has not gone away((

    [video src="https://skrinshoter.ru/v/090126/JrwFC8Yc.mp4?view=1&name=Видео-09-01-2026%2019:53:46.mp4" /]

    Hi @jfstyle,

    Thanks for testing with a default theme and all plugins disabled, that helps a lot.

    Since the error only happens when mandatory account registration is enabled, and:

    • the order is still created in the admin,
    • the error occurs with all payment methods,
    • guest checkout works fine,

    this indicates the issue is not payment-related, but is happening during customer account creation at checkout.

    This is commonly caused by a failure in:

    • user registration, or
    • account-related email sending (even if SMTP appears mostly working).

    Please check the following:

    1. WooCommerce → Settings → Accounts & Privacy
      • Make sure “Allow customers to create an account during checkout” is enabled.
      • Try disabling automatic password generation and allow customers to set their own password.
    2. WordPress → Settings → General
      • Ensure “Anyone can register” is enabled.
      • Confirm the default role is set to Customer.
    3. WooCommerce → Status → Logs
      • Check for any errors related to user creation or emails at the time of checkout.

    As a temporary workaround, keeping guest checkout enabled will avoid this issue, since account creation is skipped.

    If you find any relevant log errors, feel free to share them here (you can redact sensitive info), and we’ll help interpret them.

    Thread Starter jfstyle

    (@jfstyle)

    I checked the first items – all the jackdaws are standing.

    But I think you’re right, the problem is with sending emails. That is, first the user must register, and then the order is created, right?

    The order is not created in the admin area! I looked at the logs and found this:

    2026-01-10T07:38:52+00:00 Отладка [Shortcode #1] Place Order flow initiated Дополнительный контекст{ “order_uid”: “8b5de5fa-5157-470c-8f87-dab2bc32355f”, “store_url”: “https://bilingvionline.com”, “last_error”: { “type”: 2, “message”: “include_once(): Failed opening ‘/var/www/vhosts/bilingvionline.com/httpdocs/wp-content/mu-plugins/litespeed-cache/litespeed-cache.php’ for inclusion (include_path=’.:/opt/alt/php82/usr/share/pear:/opt/alt/php82/usr/share/php:/usr/share/pear:/usr/share/php’)”, “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-content/mu-plugins/nmwp-mu-loader.php”, “line”: 10 }, “backtrace”: [ { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-content/plugins/woocommerce/includes/class-wc-checkout.php”, “line”: 1301, “function”: “wc_log_order_step” }, { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-content/plugins/woocommerce/includes/class-wc-ajax.php”, “line”: 544, “function”: “process_checkout”, “class”: “WC_Checkout”, “type”: “->” }, { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-includes/class-wp-hook.php”, “line”: 341, “function”: “checkout”, “class”: “WC_AJAX”, “type”: “::” } ], “remote-logging”: false }

    • This reply was modified 4 months, 4 weeks ago by jfstyle.

    Hi @jfstyle,

    Thanks for sticking with the troubleshooting and for sharing the log details, they clearly point to what is happening and help narrow this down quickly.

    This is not a payment or email issue. When mandatory registration is enabled, WooCommerce first creates the customer account and only then creates the order. The log shows a fatal error caused by a missing LiteSpeed Cache must use plugin file being loaded by nmwp-mu-loader.php. Because mu plugins always load, this stops the checkout flow entirely, which is why no order is created and all payment methods fail when registration is required.

    The next step is to contact your hosting provider and ask them to fix the LiteSpeed Cache mu plugin setup. They may need to reinstall LiteSpeed Cache correctly or remove the broken mu plugin loader that is pointing to a missing file. Once that is resolved, mandatory account creation at checkout should work normally.

    For reference on how checkout and account creation work together, https://woocommerce.com/document/configuring-woocommerce-settings/accounts-and-privacy/#guest-checkout-and-accounts.

    Please let me know once the host has reviewed this and we can confirm everything is working as expected.

    Thread Starter jfstyle

    (@jfstyle)

    Hosting support has made changes to the caching plugin. But the error remains, I am attaching information from the log.

    2026-01-10T14:32:21+00:00 Отладка [Shortcode #1] Place Order flow initiated Дополнительный контекст{ “order_uid”: “9cd9ebf5-4999-477c-b091-e7c98c87f10f”, “store_url”: “https://bilingvionline.com”, “backtrace”: [ { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-content/plugins/woocommerce/includes/class-wc-checkout.php”, “line”: 1301, “function”: “wc_log_order_step” }, { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-content/plugins/woocommerce/includes/class-wc-ajax.php”, “line”: 544, “function”: “process_checkout”, “class”: “WC_Checkout”, “type”: “->” }, { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-includes/class-wp-hook.php”, “line”: 341, “function”: “checkout”, “class”: “WC_AJAX”, “type”: “::” } ], “remote-logging”: false } 2026-01-10T14:32:21+00:00 Отладка [Shortcode #2] Session updated with checkout data and totals calculated Дополнительный контекст{ “order_uid”: “9cd9ebf5-4999-477c-b091-e7c98c87f10f”, “store_url”: “https://bilingvionline.com”, “backtrace”: [ { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-content/plugins/woocommerce/includes/class-wc-checkout.php”, “line”: 1318, “function”: “wc_log_order_step” }, { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-content/plugins/woocommerce/includes/class-wc-ajax.php”, “line”: 544, “function”: “process_checkout”, “class”: “WC_Checkout”, “type”: “->” }, { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-includes/class-wp-hook.php”, “line”: 341, “function”: “checkout”, “class”: “WC_AJAX”, “type”: “::” } ], “remote-logging”: false } 2026-01-10T14:32:21+00:00 Отладка [Shortcode #3] Checkout posted data validated Дополнительный контекст{ “payment_method”: “bacs”, “order_uid”: “9cd9ebf5-4999-477c-b091-e7c98c87f10f”, “store_url”: “https://bilingvionline.com”, “backtrace”: [ { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-content/plugins/woocommerce/includes/class-wc-checkout.php”, “line”: 1324, “function”: “wc_log_order_step” }, { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-content/plugins/woocommerce/includes/class-wc-ajax.php”, “line”: 544, “function”: “process_checkout”, “class”: “WC_Checkout”, “type”: “->” }, { “file”: “/var/www/vhosts/bilingvionline.com/httpdocs/wp-includes/class-wp-hook.php”, “line”: 341, “function”: “checkout”, “class”: “WC_AJAX”, “type”: “::” } ], “remote-logging”: false }

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Thank you for the update. Based on the logs you’ve shared, everything appears to be working as expected and no errors are currently visible.

    To assist you further, we’ll need to be able to replicate the issue on our end. I’ve checked your site and can see that the thirdparty payment method Pay with Iyzico payment.

    Could you please create a staging site and do the following for testing purposes:

    • Deactivate all plugins except WooCommerce
    • Enable a default theme
    • Enable the defualt Direct Bank Transfer (BACS) payment method

    This will allow us to place a test order and verify the checkout flow in a clean environment.

    You can use the following plugin to create a staging site:
    https://ww.wp.xz.cn/plugins/wp-staging/

    Once the staging site is ready, please share the access details so we can proceed with testing.

Viewing 15 replies - 1 through 15 (of 44 total)

You must be logged in to reply to this topic.