Build or Buy a Payment Customization Function on Plus?
A payment customization function is a BUY for almost every Plus merchant: HidePay and Payfy hide, reorder and gate payment methods by country, cart total, customer tag or metafield for $3.99–$9.99/month (verified Sep 2026). Build only when the rule needs data no rule engine exposes, at $6,000–$18,000 (Deploi estimate, illustrative). The custom lane is Plus-only, since custom apps with Function APIs need Plus. Payment terms, deposits and review flags are not this function's job.
Your profile — see how the verdict shifts
- Confidence
- High — Browsed the App Store's Marketing and conversion › Checkout and Selling products › Payments categories, ran searches for payment customization and hide-payment-method apps, and cross-checked each live listing on 2026-09-05. HidePay (4.8★, 388 reviews), Payfy (4.9★, 147 reviews) and PayRules (4.9★, 97 reviews) are all Built for Shopify, all run as public payment customization functions on any plan, and Payfy's Premium tier reaches cart attributes, line properties and metafield conditions. Every one of them gates the visibility and order of existing payment methods, which is also exactly what a custom payment customization function does. Nothing in either lane sets payment terms, deposits or an order review flag; deposits are a native B2B setting available only on Shopify Plus, and a review flag is a Flow workflow. Shopify's docs state that only Plus stores can use custom apps that contain Shopify Function APIs.
- Reference scenario
- $20M–$100M GMV · Shopify Plus · rules to hide or reorder payment methods by geography, order value and customer type · agency or in-house dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Any plan · hide or reorder by country, cart total, customer tag or product | BUY | HidePay's Premium plan covers every one of those conditions for $3.99/month (verified Sep 2026), and the app itself is a payment customization function, so you get the same checkout mechanism a build would use without owning any code. |
| Plus · rules keyed to metafields, cart attributes or line properties | BUY | Payfy's Premium plan reads cart attributes, line properties and metafield conditions for $9.99/month (verified Sep 2026). Write the signal you need, such as a risk score, into a metafield and let the app read it before you write a function to read it yourself. |
| Plus · rule computed from data no rule engine exposes, or dozens of interacting rules | BUILD | PayRules tops out at 25 active rules on its $19.99/month Elite plan (verified Sep 2026), and none of the three evaluates a computation you can't express as a condition. One function with your own input query and settings costs $6,000–$18,000 (Deploi estimate, illustrative) and replaces the rule list. |
| Plus · the real requirement is payment terms, deposits or a manual review flag | WAIT | A payment customization function hides, moves or renames payment methods, and that is all it does. Net terms and deposits are native B2B settings on the company location, with deposits available only on Plus, and a review flag is a Shopify Flow workflow that tags or holds the order. Neither lane on this page is the tool. |
What Payment Customization Function Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Removing cash on delivery for the addresses and cart values where refused deliveries concentrate turns orders that would have been returned to origin into orders that are paid up front. |
| Operational efficiency | Medium | Gating a manual or invoice method to tagged B2B customers stops retail orders arriving on terms your finance team has to unwind by hand. |
| Customer experience | Medium | Reordering puts the payment method a segment actually uses first, so a wholesale buyer sees invoice terms at the top and a consumer sees Shop Pay. |
| Data & insight | Low | A rule keyed to a metafield risk score creates a reason to maintain that score, which then feeds fraud review and reporting beyond checkout. |
Spend ceiling: The ceiling for rule-based gating is $3.99–$9.99/month (verified Sep 2026). A build at $6,000–$18,000 (Deploi estimate, illustrative) only clears that bar when the rule it expresses prevents more than that in refused deliveries or fraud per year, and when no condition list can express it.
What buying enables (top apps)
- + Hide or reorder by cart total, country, discount, product, weight, customer tag or spend, and currency, live the same afternoon
- + Metafield, cart-attribute and line-property conditions on Payfy Premium for $9.99/month (verified Sep 2026)
- + Free operation on development and Shopify Plus sandbox stores, so staging costs nothing
- + Built for Shopify listings at 4.8–4.9★ with vendor-maintained API upkeep
What building additionally unlocks
- + A rule that is a computation across cart, customer, address and metafield inputs rather than a condition from a list
- + No rule-count ceiling and no per-store subscription across a Plus organization's production stores
- + Checkout data that never leaves Shopify's sandbox for a third-party app
- + Thresholds exposed through function settings your operations team controls, versioned with your own release process
Find Your Verdict in 3 Questions
Is the requirement to hide, reorder or rename payment methods, rather than to set terms, deposits or a review flag?
Yes: Go to question 2.
No: Your verdict: WAIT. Net terms and deposits are native B2B settings on the company location, with deposits available only on Plus, and a review flag is a Shopify Flow workflow; a payment customization function isn't the tool.
Can HidePay, Payfy or PayRules express the condition, using country, cart total, customer tag, product, metafield or cart attribute?
Yes: Your verdict: BUY. HidePay or Payfy at $3.99–$9.99/month (verified Sep 2026) runs the same function mechanism a build would, without the code.
No: Go to question 3.
Is the store on Shopify Plus?
Yes: Your verdict: BUILD. One payment customization function with your own input query and settings, at $6,000–$18,000 (Deploi estimate, illustrative).
No: Your verdict: BUY. Custom apps with Function APIs are Plus-only, so pick the app whose conditions come closest and precompute the missing signal into a customer tag or metafield it can read.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | HidePay or Payfy is configured in an afternoon, while a production payment customization function with settings and fixtures runs an estimated 2–5 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Paid tiers run $3.99–$19.99/month (verified Sep 2026), among the cheapest subscriptions in the App Store, while the build carries only upkeep and no subscription at all. | ||
| Maintenance & upgrades | The vendor absorbs quarterly API versions and checkout changes for every merchant at once, while your own function needs roughly 15–20% of build cost per year (Deploi estimate) to keep current. | ||
| Switching & exit | Rules are simple enough to rebuild in another app in an hour, though the configuration lives in the vendor's admin; your own function's logic and settings live in your repository and metafields. | ||
| Risk | |||
| Vendor risk | Three Built for Shopify listings with 97 to 388 reviews make this a healthy, if small, category, and a first-party function has no vendor to lose. | ||
| Security & compliance surface | A gating app reads cart, customer and address data under App Store review; a custom function runs in Shopify's sandbox with only the input query you wrote, and no third party sees checkout data. | ||
| Platform-deprecation exposure | Both lanes sit on the same Payment Customization Function API, so an API version change hits both; the vendor ships the fix for everyone, and you ship yours on your own schedule. | ||
| Value | |||
| Fit to requirement | Country, cart total, customer tag, product, metafield and cart-attribute conditions cover nearly every real gating rule, and the function only adds value for a computation those conditions can't express. | ||
| Time to market | Today versus two to five weeks, and the rule usually needs to be live before a COD-heavy campaign or a B2B launch, not after. | ||
| Performance & scale | Both lanes run inside the same 11-million-instruction budget for carts up to 200 line items with no storefront script, so checkout speed is identical either way. | ||
| Data ownership & AI-readiness | A function reading your own metafields lets the same risk or customer-tier data drive gating, reporting and personalization; an app's rule configuration stays in the vendor's admin. | ||
| Focus & opportunity cost | Spending developer weeks to replace a $3.99/month app (verified Sep 2026) is the clearest opportunity-cost loss on this hub, unless the rule genuinely can't be expressed. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| HidePay: Hide Payment Methods | Live — 4.8★, 388 reviews; Built for Shopify. Hides payment methods by cart total, country, discount, product, weight, customer tag or spend, and shipping or cart currency, with AND/OR logic on the Advanced plan and express-checkout button hiding on Ultimate. The Free Dev Store plan runs on development stores and Shopify Plus sandbox stores only, so staging is free and production bills per store. | Free Dev Store plan (development and Plus sandbox stores only, 5 rules); Premium $3.99/month; Advanced $5.99/month; Ultimate $7.99/month; 7-day free trial on paid plans (verified Sep 2026) | The default choice for hide-by-condition rules on any plan |
| Payfy: Hide Payment Rules | Live — 4.9★, 147 reviews; Built for Shopify. Up to 2 rules on Basic and 5 main rules on Advanced; the Premium plan adds cart attributes, line properties and metafield conditions, which is the closest an app gets to a custom function's inputs. Free on development and Shopify Plus sandbox stores. | Development Store plan free (dev and Plus sandbox stores only); Basic $3.99/month; Advanced $5.99/month; Premium $9.99/month; 7-day free trial on paid plans (verified Sep 2026) | Rules that key off metafields, cart attributes or line properties without writing a function |
| PayRules: Hide Payment Methods | Live — 4.9★, 97 reviews; Built for Shopify. More than 30 conditions, with 5 active rules on Essential, 10 on Professional and 25 plus OR logic on Elite. The free plan is limited to development stores. | Free Development plan (development stores only); Essential $4.99/month; Professional $9.99/month; Elite $19.99/month; 3-day free trial on paid plans (verified Sep 2026) | Stores that need many parallel rules and OR logic across conditions |
| Custom payment customization function (custom app) | Build lane — The same hide, move and rename operations the apps perform, driven by an input query you write over cart, customer, delivery address and metafields. Installable only on Shopify Plus, because custom apps containing Function APIs are Plus-only. Worth it for a computed rule no condition list expresses, and for nothing else. | $6,000–$18,000 one-time plus upkeep (Deploi estimate, illustrative) | Plus merchants with a gating rule that is a computation, not a condition |
The Build Path
- Express the rule as hide, move and rename operations: A payment customization function receives the cart, the customer and the available payment methods, and returns operations that hide, reorder or rename them. Write the rule as a decision table first: which method, under which combination of address, value, customer and metafield conditions. If the table fits a condition list, buy the app instead.
- Keep the input query small and precompute the signal: The input query is capped at 3,000 bytes and a calculated cost of 30, list arguments can't exceed 100 elements, and metafield values over 10,000 bytes aren't returned. A risk score or a customer tier belongs in a metafield written ahead of time, not computed in the function on every checkout.
- Merchant settings so ops changes thresholds without a redeploy: Expose the COD cart-total ceiling, the country list and the customer tags through the function settings component, which gives your operations team a configuration form with the native save bar. Hard-coded thresholds turn every marketing change into a deployment.
- Test with fixtures, then replay production input: The budget is 11 million instructions for carts up to 200 line items and a 256 kB compiled binary, and JavaScript reaches the instruction limit sooner than Rust, per Shopify's guidance. Run the function against fixture carts with the CLI, then replay logged production inputs before release.
- Effort band
- $6,000–$18,000 for one production payment customization function with settings and fixtures — Deploi estimate (illustrative); lands in the $10–25K contact-form band
- Typical timeline
- 2–5 weeks to a production function (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $1,000–$3,500/yr (Deploi estimate, illustrative) for quarterly API version bumps, checkout changes and the rule adjustments operations asks for.
- What you own — and what you take on
- You own: the rule, its thresholds in your metafields and settings, the fixtures and the deployment history. You take on: API version upkeep and a Plus dependency, since the custom app stops being installable if the store leaves Plus.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $200–$800 (configuration time) | $6,000–$18,000 |
| Years 1–3 (recurring) | $144–$360 (subscription across three years) | $3,000–$10,500 (upkeep and rule changes) |
| 3-year total | ≈$344–$1,160 | ≈$9,000–$28,500 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column assumes a paid HidePay or Payfy tier plus a few hours of internal configuration each year.
- † Build column covers one payment customization function with merchant settings and fixtures; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Entry tiers cap rules hard: Payfy Basic allows 2 rules and PayRules Essential 5, so a store with several markets climbs a tier quickly (verified Sep 2026)
- — The free plans on HidePay and Payfy run only on development and Plus sandbox stores, so every production store in a Plus organization bills separately
- — Hiding a method at the payment step doesn't remove its express-checkout button on the cart unless the tier covers that, which HidePay reserves for Ultimate at $7.99/month (verified Sep 2026)
- — No gating app sets payment terms, deposits or a review flag, so a purchase made for those reasons solves nothing
On the build path
- — Custom apps containing Function APIs are Plus-only, so the function is uninstallable if the store ever leaves Plus
- — Replacing a $3.99/month app with developer weeks (verified Sep 2026) is the clearest opportunity-cost loss on this hub unless the rule truly can't be expressed
- — Input queries are capped at 3,000 bytes and cost 30, so a rule that wants the whole cart plus customer history has to be redesigned around precomputed metafields
- — ~$1,000–$3,500/yr in upkeep (Deploi estimate, illustrative)
What Merchants Say
Merchants in cash-on-delivery markets describe the same arc: refused deliveries pile up in specific regions, they want COD gone for those addresses and above a cart value, and a rule-based app handles it the same day.
The low-star reviews cluster on tier limits and edge cases: two rules on the entry plan run out fast, and a method hidden at the payment step still shows as an express-checkout button until a higher tier handles that too.
If You Change Your Mind Later
If you bought and outgrow it
Screenshot or export your rule list before you cancel, because the configuration lives in the vendor's admin and the hidden methods reappear the moment the app is removed. Rebuilding a handful of conditions in another app is an hour's work, which is why exit risk here is close to zero.
If you built and want out
Nothing strands. The rule logic lives in your repository, the thresholds in your metafields and settings, and exit means uninstalling your own custom app. Retreating to HidePay or Payfy is a $3.99–$9.99/month decision (verified Sep 2026), and the metafield signals you built keep working as app conditions.
When This Answer Changes
We're watching for:
- ▸ Shopify adding condition-based payment-method rules to native checkout settings, which would move the whole buy lane to WAIT
- ▸ Payfy or HidePay adding computed or external-data conditions, which narrows the build lane further
- ▸ A change to Shopify's per-store activation limits for payment customizations, which shapes how many rules either lane can hold
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Do I need Shopify Plus to hide or reorder payment methods?
No, hiding or reordering payment methods works on any plan through an App Store app. HidePay, Payfy and PayRules are public apps that contain payment customization functions, and Shopify's docs state that stores on any plan can use public apps distributed through the App Store that contain functions. Paid tiers run $3.99–$19.99/month (verified Sep 2026). Only a custom app containing your own function requires Shopify Plus.
Can a payment customization function set net terms, deposits or a manual review flag?
No, a payment customization function only hides, reorders or renames payment methods at checkout. Net payment terms and deposit requirements are native B2B settings on the company location, and Shopify's help states deposit requirements are available only on the Shopify Plus plan. Payments aren't captured automatically when terms expire, so capture stays manual. A review flag is a Shopify Flow workflow, and Flow is free on Basic, Grow, Advanced and Plus.
What does a custom payment customization function cost to build?
A custom payment customization function costs $6,000–$18,000 one-time, plus roughly 15–20% of build cost per year in upkeep (Deploi estimate, illustrative). The scope is one function with an input query under 3,000 bytes, merchant-facing settings for thresholds and country lists, fixture tests and deployment, over 2–5 weeks. HidePay covers the common conditions for $3.99/month instead (verified Sep 2026), so the build only pays for a rule no condition list expresses.
Your Next Steps
If you're going with BUY(matches your selected profile)
- Write the gating rules as a decision table before you compare tiers, so you know how many rules and which conditions you need
- Pick HidePay for condition breadth or Payfy Premium for metafield, cart-attribute and line-property conditions (verified Sep 2026)
- Configure and test on a Plus sandbox store first, where both apps are free
- Check whether hidden methods still appear as express-checkout buttons and choose the tier that covers them
- Handle terms, deposits and review flags in native B2B settings and Flow, not in the gating app
If you're going with BUILD
- Prove the rule can't be expressed as app conditions, including by precomputing a signal into a metafield Payfy could read
- Design the input query within the 3,000-byte and cost-30 limits and decide which signals are precomputed
- Build one function with merchant settings for every threshold operations will want to change
- Test against fixture carts, replay logged production input, and release with a rollback plan
Official Docs & Sources
- Payment customizations — shopify.dev
- Shopify Functions overview and plan gate — shopify.dev
- Function limits — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Cart Transform vs. a Bundle App: Who Owns Pricing?
Overriding a bundle line's price, title and image with Cart Transform's lineUpdate works only on development stores or Shopify Plus; bundle apps cover the rest.
Should You Run a Custom Cart Transform Alongside an App's?
Shopify caps cart transform functions at one per app rather than one per store, and runs every app's function, so a custom one can sit beside a bundle app's.
Branding API vs. the Free Checkout Editor: Do You Need Code?
The free checkout and accounts editor covers most branding on every plan; Plus API overrides add precision, and the Checkout Blocks branding editor ends 2026-12-31.
Checkout Extension Network Access: What Shopify Actually Allows
Checkout UI extensions declare four capabilities in the extension TOML file, and network_access is the one Shopify makes you request before publishing.
Should You Build or Buy Your Shopify Scripts-to-Functions Migration?
A Scripts-to-Functions migration is a build for any store whose checkout logic still earns money — unported rules have already gone silent.
Ready to settle your payment-method rules for good?
Most of the time our answer is an app at under $10/month (verified Sep 2026) and an hour of configuration, and we say so. When your rule is a computation no condition list expresses, we scope one payment customization function with settings your operations team controls, and we keep the terms, deposits and review-flag work where it belongs, in native B2B settings and Flow.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Platform limits quoted from shopify.dev as of September 2026. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.