Critical Bug: XStore loses session/billing data on failed payment return (Order Pay page validation

This topic has 4 replies, 2 voices, and was last updated 1 day, 11 hours ago ago by Jack Richardson

  • Avatar: John
    John
    Participant
    May 26, 2026 at 08:27

    Hi support team,

    I am facing a critical issue on the checkout page using the XStore theme on a live client website.

    The issue happens specifically after a payment is canceled or fails at the bank’s gateway. When the gateway redirects the customer back to the website’s order-pay page (/checkout/order-pay/XXXX/?pay_for_order=true…) so they can try paying again, the XStore theme seems to clear or lose the session/billing data.

    As a result, when the user clicks “Pay” again on this page, WooCommerce triggers the checkout validation hooks and throws multiple red errors stating that billing fields (Email, Address, Country, etc.) are mandatory.

    Moreover, please note that the page does not provide any option or input fields for the user to re-enter this missing information. The user is completely trapped on a screen with error messages and no way to fill in the required data.

    It seems that the theme fails to preserve or correctly fetch the existing billing data from the created order once the user returns from a failed/canceled payment session.

    This is a critical flow issue blocking users from retrying their payments. Please provide a fix or a code snippet to ensure billing data is preserved or bypassed on the order-pay endpoint after a gateway rejection.

    Content is visible for topic creator and
    support staff only.
    Files is visible for topic creator and
    support staff only.
    3 Answers
    Avatar: Jack Richardson
    Jack Richardson
    Support staff
    May 26, 2026 at 10:07

    Hello @John,

    Thank you for the information you have provided. Could you please check whether the issue persists when testing the same procedure with a default theme such as Storefront? Our theme does not automatically clear any cookies or cache on such pages, so the same issue may occur when using the default Storefront theme, as all script verifications and other configurations are managed by the WooCommerce plugin.

    If you have a staging website, please recreate the test there using the default theme. If the issue occurs only with our XStore theme, we will investigate it in detail.

    Best regards,
    Jack Richardson
    The 8Theme’s Team

    Avatar: John
    John
    Participant
    May 26, 2026 at 10:18

    I’ve made the same procedure some months ago with another theme (Konte) and I didn’t have similar issue.

    Avatar: Jack Richardson
    Jack Richardson
    Support staff
    May 26, 2026 at 11:27

    Hello @John,

    Over the past few months, approximately 5–7 versions of the WooCommerce plugin have been released (https://developer.woocommerce.com/changelog/), along with updates to other plugins that could potentially cause this issue. Therefore, we kindly asked you to test the current setup using the default theme to ensure accurate test results.

    Thank you for your understanding and for respecting our support time.

    Best regards,
    Jack Richardson
    The 8Theme’s Team

  • Viewing 4 results - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.Log in/Sign up

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.