help1
shopify payment customizationshopifycheckoutshopify functionsshopify plus

Shopify Payment Customization: Four Paths, One Winner

Scripts died June 30. Functions has undocumented Plus gates. Apps have real limits. Shopify payment customization has four paths, ranked by plan tier.

help1 Team
Shopify Payment Customization: Four Paths, One Winner

Quick Answer: For most non-Plus merchants who need Shopify payment customization at checkout, install PayRules or BeSure Checkout Rules and stop. For Plus merchants with an in-house developer, migrate to Functions with a Payment Customization extension. Neither path fixes draft-order checkouts or the Shopify Payments block, and both fail silently if you skip the admin activation step.

If you got here, you have probably already ruled out the obvious things. Settings > Payments has no "hide this method when" toggle. Your old Shopify Script stopped firing on June 30, 2026 and you found out the ugly way. Someone told you Functions "works on all plans" so you paid a developer to build one, and now Shopify is telling you the app you own will only activate on Plus. Or you tried a Liquid + JavaScript hack that used to work and it silently broke the day Shop Pay took over your checkout button.

If any of that sounds familiar, welcome. This post is about the four paths merchants actually use for Shopify payment customization at checkout: what each one costs, what silently breaks on each one, and which one I would pick for you depending on your plan and what you are trying to do.

I have written and torn apart these implementations for about two years. The one thing I got wrong for most of that time was believing the "Functions is on all plans" framing on the developer blog. It is technically true. It is also so heavily qualified that for a non-Plus merchant who needs custom logic, the answer is closer to "no."

The four paths, at a glance

Here is the shortlist, in order of how often I see them in the wild.

PathWho it works forCostWhat it can doWhat it cannot do
Public app (PayRules, BeSure, Bony, Vista, RulePilot)All plans~$5-15/moHide by shipping method, product tag, country, order total, customer tagCustom real-time lookups, hide Shopify Payments on non-Plus, anything on draft orders
Functions via custom appShopify Plus only, in practiceDeveloper time + PlusAny logic Functions supports, including bespoke conditionsNetwork calls, draft orders, Sofort/iDeal hiding, hiding Shopify Payments outside Plus
Functions via published appAll plansApp Store review cycle + your own dev timeSame as above, but distributed as an appSame limits; plus the whole App Store review process for one merchant
Liquid + JavaScript hack in the themeAll plans, technicallyFree-ishBasic show/hide on classic checkoutExtensibility checkout, Shop Pay, Apple Pay, anything after August 2026

The columns are the criteria I actually use when a merchant asks. The sections below unpack each one.

Setup and who can use it

Public apps. Install PayRules or BeSure from the Shopify App Store, open the app, click through a no-code rule builder, save. Total time is 15 to 45 minutes for a first rule if you already know what condition you want. This is the path 80% of merchants should take, and the path most of them do take without even hearing about the alternatives. All plans. No developer required.

Functions via a custom app. A developer scaffolds a Shopify Payment Customization extension using the Shopify CLI, writes the logic in Rust or JavaScript, deploys to your store's private app, and then activates it in Settings > Payments > Payment customizations. This is the officially documented path in Shopify's Functions docs. It has one undocumented condition: your store must be on Shopify Plus for the "activate" step to succeed on a custom (non-public) app. The exact error is "Shop must be on a Shopify Plus plan to activate functions." I have seen merchants on Advanced plans pay four-figure fees to a developer, get the extension deployed, then discover this at go-live. HugoRangel documented exactly this on the Shopify Community forum in August 2024, and the limitation has not changed in the two years since.

Functions via a published app. Same code, but the developer packages it as a public Shopify App Store app and puts it through App Review. Once it is listed, the app installs on any plan. This is the workaround Shopify staff suggest when the Plus gate comes up. It is technically true and practically ridiculous for a one-store rule. App Review takes weeks, requires a public privacy policy, and the resulting app has one user (you). If you were going to publish it as a business anyway, fine. Otherwise this is not really a path, it is a shape of one.

Liquid + JavaScript hack. In the classic Shopify checkout, you could hide a payment method with a bit of Liquid in checkout.liquid plus some inline JavaScript that manipulated the DOM. josephraphael documented a stable variant of this in a 2020 Shopify Community thread and it kept working for years. In 2026 it fails against Shop Pay, Apple Pay, and any accelerated checkout button that skips the payment page. Non-Plus stores also cannot edit checkout.liquid. The August 2026 checkout extensibility migration will end this path entirely for the merchants who still have it.

If you want a second pair of eyes on which of these paths fits your specific store before you spend money on a developer, help1's expert chat has a saved diagnostic for exactly this question and the first 15 minutes are free.

What each path silently fails at

This is where the comparison gets uncomfortable, because every path on this list has a failure mode that produces zero error, zero admin alert, and zero customer-facing warning. The order below is the order in which I have watched merchants discover them.

Public apps fail on draft orders. If your store uses Shopify B2B, Draft Orders for wholesale, or any app that generates a draft order server-side, your payment rules do not enforce on that checkout. All payment methods appear, including the ones you deliberately restricted. This is not a bug in the app. It is a platform limitation of the Payment Customization API. Shopify Developer Support confirmed it in a 2023 community thread ("draft orders are processed slightly differently than online checkouts, scripts aren't activated on checkout for these types of invoice payment URLs") and a 2024 follow-up thread got the same answer. Every app I know of that claims to hide payment methods on draft orders is misleading you.

Custom Functions fail silently if you skip the admin activation. The developer post-mortem by flarecanary on dev.to catalogued this trap in June 2026: a deployed Function does nothing until you create an active Shopify Payment Customization record in Settings > Payments and link the Function to it. If your developer handed off the code, said "it's live," and you never went to that settings page, your Function has been sitting dormant. The app shows no errors. The extension appears in the admin. The Function never runs. I have seen this bite three merchants in the last six weeks. Two of them were still paying the developer's ongoing retainer.

Functions cannot hide Sofort or iDeal. This is a specific API bug that has "persisted for months," per multiple community threads. HideOperation does not remove Sofort or iDeal from checkout even when configured identically to methods that do hide correctly. One Dutch merchant, afbs2023, had to fully disable Sofort in Settings > Payments as a workaround, which meant it was also unavailable in the contexts where they wanted it. Shopify has not published a fix as of July 2026.

Functions cannot hide Shopify Payments on non-Plus. In May 2025 a developer named David_Arbias tried to use HideOperation to remove nine payment methods, including Shopify Payments itself, using both the ACCELERATED_CHECKOUT and PAYMENT_METHOD placements. Every other method disappeared. Shopify Payments stayed. On June 17, 2025, Shopify staff (Liam-Shopify) replied on the developer forum: "I think this would only be possible for merchants on a Plus plan." This limitation is not in the Payment Customization API reference. If you are a non-Plus merchant who wants a checkout that shows only bank transfer or PO options, no path on this list works for you. You need Plus.

Old Scripts fail silently and forever, as of June 30. willzhong, a Plus merchant with a two-year-old trade-in / upgrade program, wrote about this on r/shopify the morning Scripts died. Their Script had been applying store credit at checkout to trade-in customers. On June 30 it stopped. "As of this morning: nothing. Customers are checking out without their credit being applied. No error, no warning. Just... gone." Any Plus merchant whose checkout depended on Scripts for payment logic is now in this state until they either install a public app or write a Function. If you have not tested each restricted payment method manually since June 30, do it today. The shipping side of this sunset had the same silent-failure profile - I wrote about that pattern in the Shopify shipping scripts postmortem last week.

Liquid + JavaScript hacks bypass accelerated checkout. Shop Pay, Apple Pay, Google Pay, and PayPal Express all skip the payment method selection page entirely. A JavaScript hack that hid a checkbox on that page does nothing when the customer taps the accelerated button on the cart. Every one of these paths silently ignores your rule. If your store enables any accelerated payment method and you have a Liquid/JS hack in play, your rule already has holes in it.

The Plus gates that aren't in the docs

Two of the failure modes above are worth calling out separately because they are the ones merchants get most surprised by, and both of them come down to Shopify Plus in ways the marketing does not warn you about.

Gate one: the custom-app activation gate. The Shopify Payment Customization API is documented as available on all plans. This is true for Functions installed through public App Store apps. It is not true for a custom (private) app that a developer writes for your store. If you pay a developer to build bespoke payment logic for you, and your store is on Basic, Grow, or Advanced, the Function will not activate. Your only options are (a) upgrade to Plus, (b) have the developer publish the code as a public App Store app that you then install, or (c) settle for what a pre-existing public app can already do. There is no path to bespoke logic on non-Plus without going through App Review.

Gate two: the Shopify Payments hide gate. Even on a public app, HideOperation cannot remove Shopify Payments from checkout for non-Plus stores. The staff response on the developer forum ("I think this would only be possible for merchants on a Plus plan") is the closest thing to documentation this limitation has. If you were planning to run a store that offered only bank transfer, PO, or a specific third-party gateway - and you assumed you could just uninstall Shopify Payments as a payment method - you cannot. Removing it from your admin removes it as a processor, but as long as it is your default gateway the Payment Customization API cannot hide it at checkout below Plus.

There is a third gate that I want to flag because it burns a specific cohort: credit card customization in the US and Canada is Plus-only regardless of Function. If your goal is to hide "Credit card" as an option (as opposed to hiding one specific alternative method), you need Plus. The Solution post on the "Challenges in Payment Customization API Implementation" community thread from October 2024 spells this out.

What I'd actually pick

For 80% of the merchants I work with, the answer is a public app. PayRules or BeSure Checkout Rules cover the common cases (hide COD by shipping method, block BNPL for pre-orders, restrict methods by country, hide options by order total) with no code, on any plan, for $5-15 a month. The failure modes I care about most (draft orders, Sofort/iDeal, Shopify Payments hiding, silent activation) do not go away with a custom Function either. You are paying app rent to escape a developer bill that would not have bought you materially more.

For merchants who need a custom rule the apps cannot express - a real-time credit check, a customer's order history, a metafield synced from an external CRM - the calculation depends on your plan. If you are on Plus, hire a Functions developer and budget for the activation setup step (not just the code). If you are on Advanced or lower and you genuinely need custom logic, my honest recommendation is to move the logic upstream instead of downstream: tag the customer in your CRM or via Shopify Flow, then use a public app's customer-tag condition to enforce the rule. Two systems for one rule is annoying, but it is still cheaper and faster than App Store review for a one-store app.

For any merchant with a Shopify Script still in Settings > Checkout > Script Editor: assume it is dead. Open the Script Editor app to read what it was doing (the code is still viewable), then rebuild the same rule in a public app. Do this before you spend a day debugging a "conversion dip" that turns out to be a Script that stopped firing five weeks ago.

For anyone using a Liquid + JavaScript payment-hide hack: pull it out. It is not enforcing on your accelerated checkout buttons anyway, and the August 2026 checkout extensibility migration will finish it off for the merchants still on classic checkout. Move to a public app now, not the week before the deadline.

Do this today: open Settings > Payments > Payment customizations and confirm there is a record listed with status Active. If there is not, either your rules are not running or you never had a Function to begin with. Either way, that page is the first place to check before anything else on this list.

Still stuck? Talk to an expert.

Our vetted Shopify experts can fix this issue for you in a live session. $39 per session. Your first 15 minutes are free.