---
title: "Set Up Apple Pay"
slug: "set-up-apple-pay"
updated: 2026-03-05T22:00:14Z
published: 2026-03-05T22:00:14Z
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://resource.payrix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up Apple Pay

Apple Pay is a fast and secure way to pay and is accepted by over 85% of retailers in the US. This payment method enables users to add bank and credit cards to their phones for secure payment at stores. Card numbers are converted to unique, secure numbers stored on the phone's chip for safer transactions. Apple Pay replaces the need for customers to carry a physical card or enter personal information during sales.

Apple Pay functionality is built into the Payrix Pro platform and requires little-to-no development work. We offer three integration options for embedded payment options like PayFrame, PayFields, and contactless payment terminals.

## Set Up Apple Pay for Testing

To test and accept Apple Pay, you must do the following:

- [Meet the minimum requirements and guidelines](https://developer.apple.com/documentation/apple_pay_on_the_web/#2110131) for using Apple Pay on websites.
- [Use devices compatible with Apple Pay](https://support.apple.com/en-us/102896), such as Apple devices, Windows devices, and other devices in third-party browsers.
- [Add at least one credit or debit card](https://support.apple.com/en-us/HT204506) to the cardholder’s Apple Wallet.
- [Complete domain registration](/v1/docs/set-up-apple-pay#complete-domain-registration) for each web domain where Apple Pay will be offered.

## Complete Domain Registration

As a partner, you can register one or multiple merchants for Apple Pay using the Payrix Pro Portal. Domain registration involves providing each merchant’s web domain to Apple for server call authorization, enabling transaction verification for Apple Pay.

An acceptable merchant domain for Apple Pay is a public URL with a valid SSL certificate that uses a secure HTTPS protocol. Host a file on your website for Apple to verify the domain, ensuring eligibility for Apple Pay integration.

The following sections describe the steps for enabling Apple Pay, including registration and domain whitelisting, for both single-merchant and multi-merchant enablement:

1. [Initiate the Apple Pay registration.](/v1/docs/set-up-apple-pay#initiate-apple-pay-registration)
2. [Configure the merchant domains.](/v1/docs/set-up-apple-pay#configure-merchant-domains)
3. [Provide each domain for registration.](/v1/docs/set-up-apple-pay#provide-domains-for-registration)
4. [Register with Apple Pay.](/v1/docs/set-up-apple-pay#register-the-domains-with-apple-pay)

### Initiate Apple Pay Registration

To initiate the Apple Pay registration for merchant domains linked to each merchant’s website:

1. Select [Settings](/v1/docs/settings-partners) under Admin in the main side bar.
2. Select [Payment Methods](/v1/docs/payment-methods-partners) in the Business Details box of the Business Settings section.
3. Click **Enable** under Apple Pay to initiate the registration process.

### Configure Merchant Domains

To register your merchant domains with the Apple Pay service, you first need to configure each domain. This is a crucial step in validating the merchant for future transactions, ensuring both merchant and cardholder security.

To configure merchant domains for the Apple Pay service:

1. Click **Download** to download the domain association file. You can also manually download the required Apple Pay domain registration file for your environment using the following links:
  - **Sandbox:** [https://test-api.payrix.com/.well-known/apple-developer-merchantid-domain-association](https://test-api.payrix.com/.well-known/apple-developer-merchantid-domain-association)
  - **Production:** [https://api.payrix.com/.well-known/apple-developer-merchantid-domain-association](https://api.payrix.com/.well-known/apple-developer-merchantid-domain-association)
2. Host the file on your domains at the following endpoint: `{baseURL}/.well-known/apple-developer-merchantid-domain-association`

> [!WARNING]
> **Important!**
> 
> You must meet the following Apple Pay domain configuration requirements:
> 
> - Your website URL must be publicly accessible and cannot be set to `localhost`.
> - Your website must begin with `https` and have a valid SSL certificate for secure communication.
3. Visit each domain being registered to test if the file automatically downloads with the contents matching the original file downloaded from step 1.
4. Click **Continue** to proceed to the **Enter Domain** section.

The Apple Pay service searches each website’s specific URL path (`/.well-known/apple-developer-merchantid-domain-association`) for the matching file after registration is initiated from the Payrix Pro portal.

### Provide the Domains for Registration

To provide the domains that you want to register for Apple Pay, upload a preconfigured CSV file containing domain and merchant ID pairings. The following sections explain how to download a CSV template, enter the domains and merchants for registration, and upload the CSV file.

#### Determine Merchant Domain Configurations

Consider how your Apple Pay setup is structured before providing the merchants’ domains. Apple requires each domain that processes Apple Pay payments is linked with the correctly registered merchant ID. The following table outlines common domain and merchant configurations to help you determine which domains to register:

| Registration Use Case | Description | Example |
| --- | --- | --- |
| One Merchant, One Domain | One merchant processes Apple Pay on one domain. This is the most straightforward setup and requires a single domain to be registered to one merchant ID. | Merchant A uses *checkout.example.com* to process Apple Pay payments. |
| One Merchant, Multiple Domains | One merchant uses Apple Pay across multiple domains. You must register the merchant ID to multiple or all domains to allow payment session verification of the domain against the Apple Pay service’s approved domain list. | Merchant A uses *shop.example.com*, *pay.example.com*, and *checkout.example.com* to process Apple Pay payments. |
| Multiple Merchants, One Domain | Merchants share a domain for payment processing. You must register each merchant ID with the same domain to prevent Apple Pay from rejecting transactions due to mismatched IDs. | Merchants A, B, and C use *checkout.example.com* to process Apple Pay payments. |

Your domain registration file can include a variety of registration scenarios. The following table provides an example of how domains and merchant IDs can be linked:

| domain | merchant_id |
| --- | --- |
| shop.example.com | p1_mer_123abc4d567890efg1h2i34 |
| pay.example.com | p1_mer_123abc4d567890efg1h2i34 |
| checkout.example.com | p1_mer_123abc4d567890efg1h2i34 |
| checkout.example.com | p1_mer_234bcd5e678901fgh2i3j45 |
| checkout.example.com | p1_mer_345cde6f789012ghi3j4k56 |

In this scenario, one merchant is using one domain, one merchant is using multiple domains, and multiple merchants are using one domain.

#### Upload the CSV File

To upload a CSV file containing your merchant domains for registration:

1. Click **Template File Download** to download a CSV file for adding each applicable domain.
2. Open the downloaded CSV file and modify the file:

See the [Determine Merchant Domain Configurations](/v1/docs/set-up-apple-pay#determine-merchant-domain-configurations) section for a detailed explanation and example of a configured CSV file.
  - In the **domain** column, enter the merchant domains where your domain configuration file is hosted.

> [!WARNING]
> **Important!**
> 
> Remove the `https://` scheme from any **domain** column values in your CSV file. Domains that include this scheme fail the registration process.
  - Enter the merchant IDs for the associated merchants that you want to enable for each domain.
3. Upload your configured CSV file.
4. Click **Continue**to proceed to the **Register with Apple Pay** section.

### Register the Domains with Apple Pay

Click **Register** to validate your domains with Apple and complete the Apple Pay registration.

The registration system compares each domain registration file uploaded to the provided domains against the domains provided to Payrix Pro. Apple Pay verifies each domain by cross-referencing files, which completes within seconds.

After completing registration, an on-screen notification is displayed based on your method of enablement:

> **Merchant registration process is complete.**
> 
> Your Merchants are now able to start accepting Apple Pay payments.
> 
> **Enabled: *#*** | **Failed: *#*** | **Pending: *#***

See [Manage Your Merchant Apple Pay Registrations](/v1/docs/payment-methods-partners#manage-your-merchant-apple-pay-registrations) for information about managing each registered merchant and their domains.

A mobile payment and digital wallet service developed by Apple that allows users to make payments through Near Field Communication (NFC) technology.

A Payrix Pro platform-hosted payment solution that includes basic customization options and requires minimal development effort to implement. PayFrame embeds a Payrix Pro platform-hosted payment form on a merchant’s checkout page.

A Payrix Pro platform-hosted payment solution for merchants to securely accept payments on their website or checkout page without directly handling sensitive cardholder data. PayFields embeds iframes on the payment page to support a custom look and feel and to provide PCI compliance through a Payrix Pro PCI Level 1 Certification.

The web portal offered by the Payrix Pro platform to accomplish tasks for their business through a web-based user interface rather than the API. The Payrix Pro portal contains general settings, payment processing options, reporting, fee settings, group assignments, user management, and much more.

An entity that can process transactions and has been onboarded through a Payrix Pro partner.

The movement of funds between a customer (cardholder or eCheck account holder) and a merchant to purchase a good or service.

A PayFac-as-a-service platform. Software companies can act as payment facilitators without taking on the associated risks, compliance burdens, and investment.