Note: This article applies exclusively to merchants using the Ingrid Shopify app. Other platform integrations are not covered by this article.

When a shopper checks out with Apple Pay Express in the United Kingdom or Canada, Apple’s privacy rules limit the address data shared with merchants before the shopper approves the payment. Until the transaction is approved, Apple only provides a partial postal code — for example BT52 instead of BT52 1SA in the UK, or the first three characters (e.g. K1A) of a Canadian postal code. The full address, including the complete postal code, is only released after the shopper approves the transaction.

Carriers and the Ingrid checkout APIs require a full postal code, so during the Apple Pay Express flow the postal code is removed from the delivery address sent to Ingrid. Instead, the partial postal code is passed to Ingrid as a cart attribute:

This means that any merchant configuration relying on postal code filtering (for example, separate shipping options for Northern Ireland vs. the rest of the UK) will not match during the Apple Pay Express session — the address simply has no postal code at that point. To keep postal-code-based logic working in this flow, you need filter rules that also check the partial postal code cart attribute.

All other countries work as normal. Apple provides enough address data outside the UK and Canada, so no changes are needed for other markets.

Notes on the cart attribute behaviour:

Important: These filter rules must be configured on the delivery category or shipping option (carrier product) level — not on the region level.

Because the address contains no postal code during the Apple Pay Express session, a postal-code-only rule such as matches_any_pattern(postal_code(), 'BT*') will evaluate to false. Extend your rules with a condition on the partial_postal_code cart attribute, joined with || (OR).

Cart attributes are matched exactly — pattern matching (matches_any_pattern) does not work on cart attributes, since it only accepts a single string as input. You therefore need to list every partial postal code value that should match, using contains_any.

All Northern Ireland postcodes start with BT (districts BT1–BT99). A rule that works with both full and partial postal codes:

The list must include every possible partial value (partial_postal_code:BT1 through partial_postal_code:BT99 — 99 values in total in this example).

Negate each condition separately and join them with && (AND):

Tip: Do not wrap an entire || expression in a single not() — this causes a parsing error. Always negate each condition individually as shown above.

In the Apple Pay Express flow, the shopper cannot browse a pickup point map before approving the payment. If a pickup point option is selected, the pickup point closest to the shopper’s address is always selected automatically.

If you prefer not to offer pickup points in this flow at all, you can opt out using the suppress_pickup_points cart attribute, which is added to the session during Apple Pay Express checkouts. Add a filter rule on your pickup point delivery category:

This hides the pickup point category whenever the attribute is present, while leaving your regular checkout unaffected.