Apple Pay on custom domains
Apple Pay on the web only works on a domain that a payment processor has registered. When you serve checkout on your own domain (for example pay.example.com), you choose which processor runs Apple Pay for that domain, and PaymentKit does the rest. It registers the domain with the processor and serves Apple’s verification file for you. You don’t download or upload anything.
Before you begin
You need two things set up first:
- A connected custom domain. Add and connect your domain under Settings > Custom domains. See Custom domain for the DNS steps.
- An active Stripe or Airwallex processor with Apple Pay turned on. The processor must be active on your account and have Apple Pay enabled in its settings. If you run more than one, you pick which one handles Apple Pay for each domain.
Apple Pay on custom domains works with Stripe and Airwallex only. Other processors can’t register a domain for Apple Pay.
Turn on Apple Pay for a domain
Open Settings > Custom domains
Go to Settings > Custom domains in your dashboard. Each domain you’ve connected shows as a row with its status.
Find the Apple Pay section
Every domain row has an Apple Pay section. A badge shows whether Apple Pay is Configured or Not configured for that domain.
Choose a processor
Open the Choose a processor menu and select the Stripe or Airwallex processor you want to run Apple Pay on this domain. Only active, Apple-Pay-capable processors appear in the list. If you run more than one of the same type, each option shows the processor’s description so you can tell them apart.
That’s the whole setup. A shopper on that domain now sees the Apple Pay button at checkout, and the charge runs through the processor you picked.
You can set Apple Pay up at any time, but it only works once the domain is live and serving checkout. Apple verifies a domain by reaching it, so a domain that isn’t serving yet won’t finish verification. Connect and verify the domain (DNS and certificate) first for the smoothest setup.
What the Apple Pay status shows
The Apple Pay section on each domain shows one of these:
Use a different processor per domain
Each domain runs Apple Pay through one processor. You can:
- Change the processor. Pick a different processor from the menu. PaymentKit re-registers the domain with the new one and swaps what it serves.
- Set different processors on different domains. For example, run
pay1.example.comthrough Stripe andpay2.example.comthrough Airwallex.
A domain can run Apple Pay through only one processor at a time. Choosing a new processor replaces the old one for that domain.
Turn Apple Pay off
To turn Apple Pay off for a domain, select Turn off in that domain’s Apple Pay section. The badge goes back to Not configured, and Apple Pay verification stops being served on that domain.
There’s no separate on/off switch. Choosing a processor turns Apple Pay on, and Turn off turns it off. To turn it back on, choose a processor again.
If no processor is available
If your account has no active Stripe or Airwallex processor, the processor menu is turned off and the section shows:
Add or activate a Stripe or Airwallex processor to enable Apple Pay on this domain.
Add a Stripe or Airwallex processor (or activate one you already have) and turn on Apple Pay in its settings, then come back to this page.
If setup fails
If PaymentKit can’t register the domain, the Apple Pay section shows a short reason and the badge stays Not configured. Common causes:
- The domain isn’t live or reachable yet. Finish connecting it, then choose the processor again.
- Apple Pay isn’t enabled on the processor. Turn on Apple Pay in the processor’s settings, then choose the processor again.
After you fix the cause, choose the processor again to retry.