Shopify payment customization metafield blank — prove the owner, value, access, and checkout context.

This page is for a field used by a Payment Customization Function that is missing or invisible in Admin, the Function input, logs, an app, or checkout. A gateway that is visible when it should be hidden or reordered is a different path; use the payment customization not hiding playbook. A payment authorization or capture failure is also different; use the payment capture playbook.

Do not create a second field or install another app yet. First identify the definition owner, exact resource, key, value, input path, active Function version, and checkout surface where the value should matter.

Open Settings → Custom data or the app-owned definition surface and confirm what owns the field. A product metafield, cart attribute, payment method property, shop metafield, and Function configuration value are not interchangeable. Copy the exact namespace.key, type, validations, access setting, and app or Function that writes it.

Then open one active payment customization configuration and confirm the value is filled and saved on its documented owner, not only on a draft, duplicate, or inactive app record. If the owner is app-controlled, note the app and write path before changing the definition.

For an Admin API or app read, verify the intended scope and resource. For the Function, inspect the generated input: confirm the metafield is selected in the input query, the namespace and key match exactly, and the returned value is omitted, null, empty, or populated. Those are different clues.

Check serialization too: plain text, number, reference, list, and JSON-like values do not render alike. Test one short value through the same input path, then restore the intended type only after the path is proven. Never paste a product or cart accessor into a payment customization input without verifying the schema.

A field can be valid but blank because the active version queries a different key, the Function is still Draft, the checkout is using another payment method handle, or the app reads a different configuration than the one you tested. Capture one checkout ID, payment method handle, payment customization ID, Function version, and exact checkout path.

Compare the deployed Function input and logs with the checkout surface, not only the editor preview. If the gateway is present when it should be hidden, leave for payment customization not hiding; if the authorization or capture fails, leave for payment capture.

Use one checkout with one active payment customization and a short unmistakable test value in the configured metafield. Save it, publish the intended Function version, wait for the relevant sync or cache window, then inspect the exact Function input, log, Admin, app, or checkout surface where it should appear. Test logged out when the destination is customer-facing.

Record the checkout and payment method IDs, Function version, namespace.key, type, API version, input response shape, app version, and timestamp. If the value appears, stop. If it remains blank, the evidence should identify definition, write, access, input query, version, resource context, or empty-value handling—not a guessed fix.

Stay DIY if the work is confirming the payment customization owner, saving one value, fixing namespace.key or access, and wiring the current Function input path. This page is the checklist.

Pay for the Latch AI Ops install when you want Nico to connect the stack you already use so lead capture, ops alerts, and a checkout-ready workflow are handled together. $997 USD one-time buys that install for one live Shopify store, with a 72-hour delivery window after collaborator access. It does not buy more orders, recovered revenue, a conversion guarantee, or a theme rebuild. Checkout is on Whop; owner passwords are not requested.