Why did my checkout button stop working right after I changed my domain or bank account?
A checkout button that suddenly stops responding right after you touch your domain or bank details is rarely about those settings. Here's how to actually find the cause.
What's going on
My checkout button just stopped working. I click "Check out" on the cart page and nothing happens, no error, no redirect, the page just sits there or reloads itself. The strange part is this started right around when I updated my domain settings, or switched my payout bank account, so I assumed I'd broken something there. But now support is telling me it's more likely my theme or an app, and has nothing to do with the domain or bank change at all. Which is it, and how do I actually fix it?
This is a genuinely confusing problem because the timing is so suggestive: you touch your domain or banking details, and within a day the checkout button on your storefront goes dead. But a domain or payout change and a broken checkout button are usually two unrelated events that happened to land close together. Payout and bank details only control where your sales revenue gets deposited, they have no connection to whether a button on your storefront responds to a click. A domain change can occasionally affect checkout, but through a specific, diagnosable issue like a stuck SSL certificate, not just by existing.
Why it happens
An unresponsive checkout button is almost always a JavaScript problem on the storefront: a theme edit that broke the cart form or checkout link, or an app that injects a script into the cart or checkout flow and throws an error that stops other scripts on the page from running. Because these failures happen silently in the background, the page just looks like nothing happened, when in fact something did happen and then errored out.
The timing coincidence with account changes has a narrower, plausible explanation too. If you recently reconnected or edited your domain, its SSL certificate or connection status can be left in a pending or inconsistent state for a while, and a storefront generally won't run correctly if it isn't loading securely over that domain. Separately, if your store uses Shopify's newer customer accounts, checkout and login can depend on your domain being fully verified, so a change that leaves that half-finished could plausibly interfere.
A bank account or payout method change has no code path to a storefront button, it only affects where funds land after a sale completes, so when that's the only recent change, it's very unlikely to be the actual cause, however suspicious the timing looks.
5 ways to fix it
Pull the browser console error before you start guessing
Open your storefront in an incognito window, open the browser's developer console, and click checkout. If a script is failing, the console will usually show an error naming the file or app responsible at the moment of the click, which turns a slow trial-and-error rollback into a direct fix. If you're not comfortable reading console errors yourself, a screenshot of that error is the single most useful thing to hand to a developer or to Shopify support.
Roll back and isolate: theme first, then apps
From the Themes page, check your theme's edit history and try previewing or restoring a version from before the button stopped working. If that fixes it, the cause is a recent theme edit, often something touching the cart or checkout button's markup or JavaScript. If rolling back the theme doesn't help, go through your installed apps and disable non-essential ones one at a time, retesting checkout after each, especially anything that injects scripts into the cart or checkout flow: upsells, sticky-cart bars, tracking pixels, currency converters. Test in an incognito window each time so cached scripts don't mask the result.
Check your domain's connection and SSL status
In your domain settings, confirm your primary domain shows as properly connected with an active SSL certificate, not pending or unavailable. Shopify manages and issues these certificates automatically, but a domain change can sometimes leave one in a stuck or inconsistent state for a while, and storefront scripts generally won't behave correctly if the domain isn't loading securely. If anything about your domain changed around the time the button broke, it's worth confirming the connection is fully settled, or disconnecting and reconnecting to force a recheck.
If you use Shopify's newer customer accounts, check your checkout domain setup
Newer customer account setups can depend on a properly connected and verified domain for checkout and login to work correctly. If you changed domain settings recently, it's worth double-checking that this is still configured and verified rather than left half-updated. This is a narrower, less common cause than a theme or app conflict, but worth ruling out if the timing lines up with your domain change specifically.
Confirm the payment setup is unrelated, not the actual cause
A payout or bank account change controls where your sales revenue lands after a sale, it has no code path to whether a storefront button responds to a click, so it's very unlikely to be the cause here. Still, it's worth a quick check in your payment settings that your payment provider is showing as fully active and not sitting in a re-verification state, and that no test mode was left on by accident. This won't fix an unresponsive button, but it rules out a second, unrelated issue from muddying your diagnosis.
Bottom line
The coincidence with a domain or bank change is what makes this feel like an account-settings problem, but a checkout button that simply won't respond to a click is almost always a front-end script conflict, a theme edit or an app's injected code, rather than anything to do with payouts. Roll back methodically, check the console for the actual error, and confirm your domain and SSL status before assuming Shopify's payment system is at fault. If it turns out to be a tangle of conflicting app scripts that keeps recurring, that's the kind of cleanup worth solving once rather than repeating every time you add a new app.
Browse the rest of the problem library, run a free storefront scan to catch issues like this automatically, or email us and we'll work out a custom solution for it.