Apple Pay domain name configuration

To perform Apple Pay payment integration, you must first configure and verify your Apple Pay domain name on Antom Dashboard. This operation is used for Apple Pay merchant authentication and is a core prerequisite for activating the Apple Pay payment method. The following integration modes require domain configuration and verification:

Note:

  • The following modes do not require domain name configuration or verification:
  • The following process applies to the production environment configuration in the live mode. If you need to conduct sandbox testing for Apple Pay integration, please provide your DOMAIN_NAME used to receive payments to Antom technical specialists and contact them to obtain the Apple Pay domain verification file for deployment.

Configuration preparations

Before configuration, please ensure the following prerequisites are met:

    • HTTPS certificate deployed (mandatory for Apple Pay)
    • SSL certificate deployed (non-self-signed and not expired)
    • The domain is publicly accessible and does not require authentication
    • The domain format supports both top-level domains and subdomains (e.g., example.com or pay.example.com)

Configuration steps

After ensuring all preparation conditions are met, follow these steps to configure the Apple Pay domain:

  1. Add Apple Pay domain
  2. Obtain domain verification file and deployment path
  3. Deploy domain verification file

Step 1: Add Apple Pay domain

  1. Log in to Antom Dashboard and navigate to Payments > Payment Methods.
  2. Find Apple Pay in the list of Active payment methods and click View details to enter the payment method details page.
    image.png
  3. On the Apple Pay payment method details page, click Domain Management > Add new domain. The Domain configuration pop-up window is displayed.
  4. In the Domain configuration pop-up, enter the domain to be enabled for Apple Pay (e.g., example.com).

Note: The system automatically fills in the https:// prefix. You do not need to enter it again.

image.png

image.png

Step 2: Obtain domain verification file and deployment path

  1. In the Domain configuration pop-up, under Download domain verification file, click Download to obtain the file. The specifications of the verification file are as follows:
    • File name: apple-developer-merchantid-domain-association
    • File path: Placed in the /.well-known/ directory
    • File content: Plain text
    • Access permissions: Accessible without authentication

Note: The domain verification file contains a digital token for domain verification, which is unique and immutable. Do not modify the file contents during deployment to avoid verification failure.

  1. In the Upload domain verification file section, click the copy icon to copy the file deployment path.

image.png

image.png

Step 3: Deploy domain verification file

Deploy the obtained verification file to your domain server (it is recommended to set the Content-Type to text/plain):

  1. Paste the file deployment path:
copy
https://[DOMAIN_NAME]/.well-known/apple-developer-merchantid-domain-association
  1. Verify successful file deployment:
copy
# Use curl to verify whether the file is accessible
curl https://[DOMAIN_NAME]/.well-known/apple-developer-merchantid-domain-association

FAQs

Q: How to resolve the verification failure message indicating the domain verification file cannot be found?

A: Follow these steps to troubleshoot:

  1. Confirm the file path is correct: https://[DOMAIN_NAME]/.well-known/apple-developer-merchantid-domain-association
  2. Use a browser to directly access the URL and confirm the file is accessible.
  3. Check whether the server has URL rewrite rules configured, as this may affect file access.

Q: How to resolve HTTPS certificate issues?

A: Troubleshoot the following:

  • The certificate chain is complete
  • Test the certificate configuration using SSL Labs
  • The certificate is not expired

Q: How to resolve the domain verification file downloaded from Antom Dashboard having a .p10 suffix?

A: When downloading the verification file from the Antom Dashboard, some browsers may automatically add suffixes like .p10 to the file. Remove the browser-added suffix when saving the file.

Note: If you encounter other issues during the configuration process, please contact the Antom technical support team.