Accept Payments

Apple Pay

Apple Pay requires additional setup before it can be shown to customers in checkout.

To enable Apple Pay on the web, your platform or merchant must:

  • host a domain verification file on the website
  • register the domain with Paypercut using the API

Until both steps are complete, Apple Pay may not be available in checkout.

Apple Pay setup depends on your integration type:

  • Hosted checkout: No additional setup is required. Apple Pay is handled by Paypercut.
  • Embedded checkout (payment elements): You must complete domain verification and registration.

If you are using hosted checkout, you can skip the setup steps below.

Why Apple Pay requires setup

Apple Pay on the web requires each website domain to be verified before it can be used for payment presentation.

You must complete domain verification for every domain that displays Apple Pay.

Step 1: Download the verification file

Download the Apple Pay domain verification file:

https://cdn.paypercut.io/.well-known/apple-developer-merchantid-domain-association

Download the Apple Pay verification file

Step 2: Host the verification file

Host the file at the following path on the exact domain that will display Apple Pay:

https://your-domain/.well-known/apple-developer-merchantid-domain-association

The file must be accessible over HTTPS.

The file must be served from the /.well-known/ path on the same domain that will display Apple Pay.

Step 3: Register the domain

After the file is hosted, register the domain with Paypercut.

POST /v1/payment_method_domains

Payment Method Domains API

Domain registration is currently available through the API only.

When to register a domain

Register a domain when:

  • you are enabling Apple Pay for a hosted checkout integration
  • you are showing checkout on your own website
  • you are adding a new production or staging domain that will display Apple Pay

You should register each relevant domain separately.

Subdomains and iframe integrations

If Apple Pay is shown on more than one domain or subdomain, each one may need to be registered separately.

Examples:

For embedded or iframe-based integrations, the top-level domain and the iframe source domain may both need to be registered, depending on how checkout is rendered.

Merchant and platform responsibilities

Depending on your integration model, the verification file may be hosted by:

  • the platform
  • the merchant
  • a plugin or storefront integration

Your integration is responsible for ensuring that:

  • the file is hosted correctly
  • the domain is registered through the API
  • Apple Pay is not expected to work before verification completes

Paypercut does not place the verification file on the merchant’s website automatically.

Plugins and storefront integrations

If you are using a plugin or storefront integration, Apple Pay may still require domain verification.

Today, this setup may need to be completed manually.

Automatic domain registration for plugins may be supported in the future. Until then, plugin-based integrations should review this guide before enabling Apple Pay.

Troubleshooting

If Apple Pay does not appear in checkout:

  • confirm that the verification file is hosted on the correct domain
  • confirm that the domain has been registered through the API
  • confirm that checkout is rendered on the registered domain
  • confirm that Apple Pay is supported in the customer’s browser and device environment

Related references

Previous
Checkout Experience
Next
Payment Links