Can I hide Apple Pay in some countries but not others in WooCommerce?

Not natively. Gateways generally surface express methods globally or not at all. Asteris Cart adds a per-method, per-zone matrix so you can hide Apple Pay in one region and PayPal in another.

Why would I disable an express method by region?

Reasons include regional payment preferences, compliance, fraud patterns, or a gateway that settles poorly in a given market. The control lets you match express methods to where they actually help.

Per-zone control of express checkout in WooCommerce

By default, express checkout methods like Apple Pay, Google Pay and PayPal show everywhere or nowhere — gateways do not offer per-region toggles natively. Asteris Cart adds a per-method, per-zone kill switch: a matrix where you can hide Apple Pay in one region, PayPal in another, and leave the rest as they are. It uses WooCommerce geolocation to detect the customer's zone and applies your rules, so express buttons appear only where you want them.

All-or-nothing express buttons

Express checkout buttons — Apple Pay, Google Pay, PayPal, Amazon Pay — are a strong conversion tool when they fit the market. The catch is control. Gateways generally let you turn an express method on or off for the whole store. They do not give you a clean way to say “show Apple Pay in Australia and the US, hide it in this region, and show PayPal there instead” [VERIFY: gateway docs/community].

For a store selling across regions, that is a real gap. Payment preferences differ by country, some methods settle poorly in some markets, and compliance or fraud patterns can make a method more trouble than it is worth in a specific region.

The matrix Asteris Cart adds

Asteris Cart ships a per-method, per-zone kill switch — an admin matrix of express methods against shipping zones:

Toggle any express method on or off per zone. Hide Apple Pay in one region, PayPal in another, keep Google Pay everywhere.
Zone detection via WooCommerce geolocation. The customer’s zone is detected, then your rules decide which express buttons render.
No gateway lock-in. The control sits in the checkout layer, so it works across the express methods your gateway already surfaces.

Code receipt: src/Checkout/Express_Checkout.php::killed_methods_for_current_zone() [CODE SNIPPET — CC to insert the current killed_methods_for_current_zone() body from src/ at build; must match shipping v1.0.]

Why it sits in a checkout plugin

This is the kind of control store owners ask payment providers for and rarely get, because a gateway reasons about payments, not about your shipping zones or storefront logic. The checkout layer is where the zone and the express buttons meet, so that is where the switch belongs. Asteris Cart puts the most-requested missing control where it can actually be applied.

How this fits

The per-zone kill switch is part of the Express Checkout module and one of the six Asteris Cart wedges. See the Express Checkout module → · Compare Asteris Cart with the alternatives → · See pricing →

FAQ

Can I hide Apple Pay in some countries but not others? Not natively in most gateways. Asteris Cart adds a per-method, per-zone matrix so you can.

Why disable an express method by region? Regional payment preferences, compliance, fraud patterns, or a method that settles poorly in a market.

How does Asteris Cart decide the zone? It uses WooCommerce geolocation to detect the customer’s zone, then applies your per-zone rules.

Sources

Asteris Cart code receipt: src/Checkout/Express_Checkout.php::killed_methods_for_current_zone()
Gateway per-region limitation: [attach Stripe community / gateway docs cite at publish]