My payment method shows as enabled in Shopify admin but customers can't use it at checkout — why?
If a gateway looks live in Settings > Payments but vanishes or fails at checkout for real customers, the cause is almost always a mismatch in Markets, currency, device, or account status — not a broken toggle.
What's going on
A merchant opens Settings > Payments, sees the gateway (or Shopify Payments itself) listed as active, everything looks green — and yet customers report the option missing at checkout, or worse, attempting to pay and having it fail. It's a confusing gap: the admin panel is the merchant's only window into "is this on," but it doesn't tell the whole story of whether a given shopper, in a given country, on a given device, will actually see that method as a choice.
This shows up especially often on stores using Shopify Markets to sell into multiple countries or currencies. A payment method can be perfectly configured for the store's primary market and still be unavailable in a secondary market because of currency support, country restrictions set on the method itself, or because the market simply isn't included in that method's rollout. Digital wallets add another layer: Apple Pay and Google Pay have their own device and browser eligibility rules that have nothing to do with the admin toggle.
The result is a support headache — a customer abandons checkout because their preferred method isn't there, or a payment attempt fails with a generic error, and the merchant can't reproduce it because their own test (often on a different browser, device, or shipping address) doesn't hit the same conditions.
Why it happens
The admin toggle for a payment method only confirms it's activated at the account level — it doesn't guarantee visibility for every shopper. Visibility at actual checkout is layered: the method must also be permitted for the customer's country/market, supported for the currency that market is transacting in, compatible with the customer's device and browser (for wallet-based methods), and not suppressed by any active payment customization (a Shopify Function that reorders or conditionally hides methods based on cart, address, or customer attributes).
On top of that, the gateway account itself can be in a state that isn't obvious from the simple on/off toggle — pending verification, a risk review, or missing payout details can cause a method to behave inconsistently (sometimes present, sometimes not, or present but declining) without Shopify surfacing a hard "disabled" state in the list view. Merchants scanning that list for a green checkmark can easily miss a smaller "action needed" banner sitting one click deeper.
5 ways to fix it
Check the gateway's account status first — not just the toggle
In Settings > Payments, click into the specific provider (Shopify Payments or the third-party gateway) rather than just confirming it's "on." Look for banners like "Action required," "Under review," or missing bank/business details — these don't always turn the method fully off, but they can cause intermittent declines or hide it for certain order types until resolved. For Shopify Payments specifically, an incomplete payout setup or a risk review flag is one of the most common reasons a method looks live in admin but silently fails or disappears for shoppers.
Confirm the customer's country and currency are actually covered by that method in Markets
A payment method can be fully enabled at the account level and still be invisible in a specific market if that market's country isn't included in the method's availability rules, or if the market's currency isn't one the gateway supports. Under Settings > Markets, open the relevant market and check both its included countries/regions and its currency, then cross-check that against the payment method's own country-restriction settings in Settings > Payments (most manual and third-party methods have a "restrict to specific countries" option that's easy to leave misconfigured).
Test wallets (Apple Pay, Google Pay, Shop Pay) on the actual matching device and browser
Digital wallets aren't shown just because they're enabled — Apple Pay requires Safari on a verified domain with a supported device/card set up in the customer's wallet, and Google Pay requires Chrome or an Android device with a saved card. If a merchant tests in the "wrong" browser/device combo, the option correctly won't appear, which often gets misread as a bug rather than expected platform behavior. Reproduce the report using the same browser, device type, and country the customer used before assuming something is broken.
Look for a payment customization (Shopify Function) quietly hiding the method
If any app or custom Shopify Function is installed to reorder, rename, or conditionally hide payment methods (common for B2B pricing, COD restrictions, or shipping-based rules), it can suppress a method for specific carts, addresses, or customer tags even though the method shows as globally enabled. Check Settings > Checkout for any active payment customizations and temporarily disable them one at a time to isolate whether one is the cause.
If everything above checks out, escalate to Shopify Support or the gateway provider
When the account status is clean, Markets/currency coverage is correct, the device/browser matches, and no customization is interfering, the remaining cases are usually backend issues on Shopify's or the payment provider's side — for example a processor-level outage or an account-level restriction not visible in the merchant's own admin. Shopify Support can check gateway logs on their end that aren't exposed in the dashboard.
Bottom line
This is almost always a configuration gap between Markets, currency coverage, device requirements, and gateway account status rather than a genuine Shopify bug — working through the layers above resolves the large majority of these reports without installing anything new. If a store runs many markets and payment customizations at once, a periodic manual click-through of checkout in each market/device combination is the most reliable safeguard, since Shopify doesn't currently surface a single dashboard that flags "this method is enabled but invisible in market X."
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.