# Shopify payment customization at checkout in 2026

Payment Customization Functions hide, rename, and reorder wallets and cards, set Plus payment terms, and add B2B review rules without checkout.liquid.

- Date: 2026-11-04
- Category: Shopify

## Table of contents

- Why Shopify payment customization matters in 2026
- How Payment Customization Functions run at checkout
- Production checklist for Shopify payment customization
- What breaks when payment customization goes live
- How to measure Shopify payment customization
- Related work on this site
- FAQ
  - What is Shopify payment customization on checkout?
  - Do Shopify payment customization functions work in Shop Pay?
  - When can Shopify payment customization set payment terms?
  - How does Shopify payment customization relate to cart validation?

Shopify payment customization is how I hide cash on delivery above a threshold, demote a wallet on wholesale carts, or set net terms on high-value B2B orders without touching deprecated checkout.liquid. I am Alan Vo, a Gold Coast web developer with 18 years in production. When checkout extensibility replaced most Scripts, payment presentation moved to the [Payment Customization Function API](https://shopify.dev/docs/api/functions/latest/payment-customization) and the `cart.payment-methods.transform.run` target documented in Shopify's [Function APIs overview](https://shopify.dev/docs/api/functions/latest).

This note is for merchants and developers who already run Online Store 2.0 themes and are pairing payment rules with [Shopify checkout extensibility](https://alanvo.com/blog/shopify-checkout-extensibility/) work. It covers hide, move, and rename operations, payment terms on Plus, B2B review requirements, Shop Pay limits, and how payment customization sits after delivery customization in the checkout pipeline.

## Why Shopify payment customization matters in 2026

Shopify payment customization matters because the payment step is where trust and fraud anxiety meet. Buyers abandon when cash on delivery sits above card wallets on a $900 cart, when Shop Pay dominates a B2B company order that should invoice on net 30, or when every wallet expands before the merchant's preferred bank transfer option. Theme JavaScript cannot reorder accelerated checkout buttons reliably, and Shopify Scripts for payment sorting are not the long-term path on new builds.

Payment Customization Functions run inside Shopify's checkout backend. Your app registers a function, the merchant activates it under checkout rules, and the function returns ordered operations such as `paymentMethodHide`, `paymentMethodMove`, and `paymentMethodRename` on API version 2025-07 and later, as Shopify describes in its changelog on [standardized target and operation names](https://shopify.dev/changelog/standardized-target-and-operation-names-across-function-apis). The input is GraphQL. You request cart cost, buyer identity, company location data on B2B stores, and the list of payment methods with stable IDs.

Plan and surface rules are not optional details. Shopify's tutorial [Create the payments function](https://shopify.dev/docs/apps/build/checkout/payments/create-payments-function) states that custom apps using Functions require Shopify Plus for some placements, that payment terms only apply on Plus, and that POS does not run payment customization today. Shop Pay applies operations only to the native gift card field, not to wallet reordering. You can hide wallets from express or the payment section, but you cannot reorder them. Those constraints shape what you promise in a statement of work.

The platform caps active payment customization functions at twenty-five per store, the same family limit as [Shopify delivery customization](https://alanvo.com/blog/shopify-delivery-customization-functions/). I prefer one configurable function with JSON metafields over a stack of single-purpose apps that each consume a slot.

![Shopify payment customization on a laptop showing a Shopify storefront layout](../../images/blog/shopify-payment-customization-functions-1.jpg)

## How Payment Customization Functions run at checkout

Payment Customization Functions execute on the `cart.payment-methods.transform.run` target after delivery customization and before cart validation in the sequence Shopify documents. That ordering means your hide rule sees the cart totals discount Functions already applied, and [Shopify cart and checkout validation](https://alanvo.com/blog/shopify-cart-checkout-validation/) Functions still run last if you need a hard stop after payment presentation.

Scaffolding starts with Shopify CLI. The documented command is `shopify app generate extension --template payment_customization --name payment-customization`, then you define the input query in `cart_payment_methods_transform_run.graphql` and implement logic in Rust or JavaScript. Activation uses Admin API mutations such as `paymentCustomizationCreate` with a `functionHandle`, as shown in the create tutorial.

Operations are explicit. Hide removes a method or, on Plus, specific placements when the input exposes them. Move changes sort order with stable payment method IDs, not display names. Rename adjusts titles for methods that allow renaming. Shopify blocks renaming logo-named wallets such as Shop Pay, Apple Pay, and Google Pay, plus the native gift card field. If merchandising asks to rename Shop Pay, the answer is placement and visibility, not a custom label.

Payment terms are a separate operation family. Shopify's guide [Set payment terms](https://shopify.dev/docs/apps/build/checkout/payments/payment-terms) explains fixed, net, and event-based terms with optional deposits. Terms apply to the order being processed, not the buyer's default profile. They require Plus, do not run on accelerated checkouts, and change capture behavior for D2C versus B2B. D2C orders with terms may not offer pay-now alongside deferred options. B2B checkouts expose more deferred paths, including vaulted cards, but automatic capture rules differ from consumer checkouts.

Review requirements apply only to B2B checkouts. Shopify documents that you cannot attach review requirements to draft order invoice flows or admin draft calculations. A high cart total can force checkout into a draft order for merchant approval, which is a different support workflow than hiding COD.

When API usage is restricted by plan or region, Shopify still passes all payment methods into the function input, but operations targeting restricted methods may not take effect at checkout. Test on the merchant's actual plan rather than assuming hide works because the function returned success in logs.

## Production checklist for Shopify payment customization

The production checklist starts with payment methods as configured in admin and Shopify Payments, then function logic, then checkout configuration on a draft profile before production.

1. Export a screenshot list of every payment method and wallet the buyer sees on domestic, international, and B2B company carts today. Record stable IDs from function logs in staging, not only display names.
2. Write merchant-language rules: "Hide Cash on Delivery when cart total exceeds $150," "Move manual bank transfer above wallets for company location wholesale," "Set net 30 with 25% deposit when B2B subtotal exceeds $500."
3. Scaffold the payment customization extension and keep the input query minimal. Request cart cost, buyer context, payment method IDs, and metafield configuration on the payment customization owner object, following [Add configuration to the payments function](https://shopify.dev/docs/apps/build/checkout/payments/add-configuration).
4. Store rules in JSON metafields rather than hardcoded literals so merchandising can tune thresholds without redeploying WASM for every sale.
5. Implement hide and move with payment method IDs. Matching by substring on "Cash" breaks when a translation app renames the method.
6. Confirm rename targets are allowed. Skip rename operations on logo wallets and document that constraint for the client.
7. Deploy to a development store whose payment stack mirrors production: Shopify Payments, manual methods, gift cards, and third-party gateways if used.
8. Activate the customization under checkout rules on a draft checkout configuration. Verify the function version referenced in the app release matches what checkout rules bind.
9. Test standard checkout with carts below and above thresholds. Confirm hide and move behavior on the payment step.
10. Test Shop Pay separately. Expect that only gift card customization applies inside Shop Pay while standard checkout shows full operations.
11. Test B2B company location carts if the merchant uses Shopify B2B. Validate payment terms and review requirements only where Shopify supports them.
12. Test payment terms on Plus with fixed and net examples. Align finance on capture timing when event-based terms interact with automatic fulfillment capture settings.
13. Pair with validation Functions if hiding COD should also block progress when no card method remains eligible. An empty payment list is worse than a visible COD with a validation message.
14. Count active payment customization functions across all installed apps and stay under twenty-five.
15. Document rollback: disable the checkout rule and revert metafield JSON before peak trading if a hide rule removes every method for a segment.

![Clothing rails in a shop used as a live catalogue for Shopify payment customization](../../images/blog/shopify-payment-customization-functions-2.jpg)

## What breaks when payment customization goes live

The most common break is hiding by display name after a gateway update. Symptoms are "function succeeded in dev dashboard but checkout unchanged." Fix by logging payment method IDs in staging and updating metafield maps when apps ship changelogs.

![Theme code on a monitor during Shopify payment customization work](../../images/blog/shopify-payment-customization-functions-3.jpg)

The second break is promising wallet reordering in Shop Pay. Buyers still see default wallet ordering there. Fix copy in the brief and test standard checkout only for move operations on wallets.

The third break is payment terms on the wrong plan or surface. Terms silently fail or never appear on accelerated checkouts. Fix by confirming Plus, testing non-accelerated checkout first, and reading Shopify's payment terms limitations before launch.

The fourth break is stacking hide rules from multiple apps until no method remains. Finance sees abandoned checkouts with no payment option. Fix by consolidating rules into one function or auditing the twenty-five function cap across vendors.

The fifth break is fighting validation logic. If validation reads attributes your payment function never sets, teams argue about cart totals. Align on post-discount totals from the same input fields both functions use.

Regional restriction is subtle. When Shopify restricts Payment Customization API usage, restricted hides do not apply even though input still lists methods. Fix by verifying behavior on the live store country and plan, not only in a partner dev store defaults.

## How to measure Shopify payment customization

Measurement starts with checkout analytics and support tickets, not only function execution counts. I compare payment step completion rate and payment method mix before and after activation, segmented by cart value bands that triggered the rules.

In staging, Shopify's dev tools and function logs confirm operations returned. In production, use checkout reporting and order payment gateway names to see whether COD volume dropped above threshold or B2B orders shifted to terms. Pair with [Shopify cart and checkout validation](https://alanvo.com/blog/shopify-cart-checkout-validation/) metrics if you also block progress on risky combinations.

For B2B review requirements, measure draft orders awaiting approval and time-to-approve. A review rule that fires too often clogs operations. Tune thresholds in metafields and re-test.

Document a two-week baseline before go-live and the same two weeks after, controlling for campaigns. Payment mix shifts during sales events anyway; note merchandising calendars in the readout.

## Related work on this site

Payment presentation sits next to shipping presentation on the stores I ship. On [Their Nibs](https://alanvo.com/work/their-nibs/) checkout work, small frictions on trust and method order mattered alongside conversion fixes. [Offporter](https://alanvo.com/work/offporter/) and [retail conversion](https://alanvo.com/work/retail-conversion/) cases remind me that checkout changes need finance, support, and ads aligned before you hide a method buyers still choose on high-AOV carts.

![Phone showing a product page in Shopify payment customization testing](../../images/blog/shopify-payment-customization-functions-4.jpg)

If you are migrating Scripts, read [Shopify delivery customization at checkout](https://alanvo.com/blog/shopify-delivery-customization-functions/) next. Shipping and payment Functions deploy under the same checkout rules mindset.

## FAQ

### What is Shopify payment customization on checkout?

Shopify payment customization is a Functions API that renames, reorders, and hides payment methods at checkout, and on eligible Plus B2B flows can set payment terms or add review requirements. It replaces most legacy Script sorting for payment presentation. Merchants activate a payment customization app under checkout rules after the app deploys a `cart.payment-methods.transform.run` function.

### Do Shopify payment customization functions work in Shop Pay?

Shopify payment customization functions partially support Storefront Accelerated Checkout. In Shop Pay, operations apply only to the native gift card field according to Shopify's create tutorial. Hide and move rules you rely on in standard checkout may not mirror inside Shop Pay, so test both surfaces before promising wallet order changes.

### When can Shopify payment customization set payment terms?

Shopify payment customization can set payment terms on checkout only when the store is on Shopify Plus, as documented in Shopify's payment terms guide. Terms apply to the current order, require non-accelerated checkout for reliable testing, and support fixed, net, event-based, and deposit structures. B2B and D2C capture behavior differs, so finance should sign off before you enable event-based terms.

### How does Shopify payment customization relate to cart validation?

Shopify payment customization runs before cart and checkout validation Functions in Shopify's documented order. Payment customization shapes which methods appear; validation can still block checkout if cart contents violate rules. Use both deliberately so you do not hide every method and leave buyers with no path validation can explain.


![Card payment at a counter after a Shopify payment customization release](../../images/blog/shopify-payment-customization-functions-5.jpg)


HTML version: https://alanvo.com/blog/shopify-payment-customization-functions/