Users are experiencing a critical checkout bug where the “Pay Now” button unexpectedly changes to “Continue” and becomes unresponsive, preventing payment completion.
Key symptoms:
All breadcrumb links appear clickable prematurely, including unreached steps
JavaScript console error: “JourneyError: Fail to update journey with ‘error’: no next page”
Bug occurs inconsistently across browsing sessions and persists until checkout is restarted from the information step
Reproduction steps identified:
Add product to cart
Proceed to payment with fake/test details that fail
Return to store and modify cart quantity
Navigate back to checkout
Workaround: Restarting checkout from the contact information step or using breadcrumb navigation to earlier steps temporarily resolves the issue.
Current status: Shopify developers initially attributed the problem to test card usage causing invisible error banners, with a fix deployed to redirect users to visible error messages. However, users report experiencing the bug in production environments without test cards and when simply switching payment options. The ticket has been escalated for further investigation as the initial explanation doesn’t fully address the reported scenarios.
Summarized with AI on November 1.
AI used: claude-sonnet-4-5-20250929.
I’ve been encountering a recurring issue during the checkout process on my store. Here’s a detailed breakdown of the problem:
On the payment step of checkout, the “Pay Now” CTA button changes to “Continue” and becomes unresponsive. Clicking it does nothing.
Simultaneously, all the breadcrumb links (including “Confirmation”) appear clickable, even if that step hasn’t been reached. Clicking these links doesn’t navigate anywhere, unless it is to go to a previous step.
If I go back to the information step (where the customer puts his address and details) and proceed again through checkout, it works. However, returning to the cart using breadcrumbs and initiating checkout again reintroduces the bug.
This behavior seems random; it happens inconsistently on the same cart and customer account across standard and private browsing modes. Once the bug occurs, it persists until I restart the checkout process from the contact information step or open a fresh new private browsing.
I also noticed that, when the bug occurs, going back to the checkout from the cart page after having the payment step broken redirects directly to the payment step, whereas, when the checkout is not bugged, the CTA from the cart always redirects to the first step (information).
Additionally, I noticed the following JavaScript error in the console when the bug occurs:
JourneyError: Fail to update journey with "error": no next page.
at A1e (app.ItN7zHb5.js:42:21618)
at P1e.plan (app.ItN7zHb5.js:42:16463)
at X9.<anonymous> (app.ItN7zHb5.js:2:224899)
at set value (app.ItN7zHb5.js:2:224512)
at app.ItN7zHb5.js:42:16730
at app.ItN7zHb5.js:42:2585
at Object.current (app.ItN7zHb5.js:42:14999)
at ku.x (app.ItN7zHb5.js:2:31699)
at ku.c (app.ItN7zHb5.js:2:28857)
at bs (app.ItN7zHb5.js:2:29225)
I tried to duplicate the checkout, remove every extensions from this duplicated checkout and use the preview to test it, the bug was still there.
Could you please help me identify the root cause and provide guidance on resolving this?
From their findings the error was related to using a test card, the client would receive an error but have no way of displaying it. They have no shipped a change to redirect to where the error banner is visible and an update can be made to resolve said error. This ensures the checkout flow process makes sense in this case. Given that this was affecting test cards we don’t anticipate this further affecting customers, but please don’t hesitate to reach out if anything else pops up or if you have any other questions.
I do not know if it is helpful. I am trying to clarify with them further.
