https://shop.example.com/.well-known/apple-developer-merchantid-domain-association
Apple Pay enables your customers to make secure, contactless purchases using Visa and Mastercard credit and debit cards that they add to Wallet.
Apple Pay uses security features built-in to the hardware and software of Apple devices to help protect the transactions. In addition, to use Apple Pay, customers must have a passcode set on their devices and, optionally, Face ID or Touch ID.
Apple Pay is also designed to protect customers personal information. Apple doesn’t store or have access to the original credit, debit, or prepaid card numbers used with Apple Pay. And when your customers use Apple Pay with credit, debit, or prepaid cards, Apple doesn’t retain any transaction information that can be tied back to them. Transactions stay between customer, you as a merchant and customer’s bank or card issuer.
To allow your customers to pay via Apple Pay, you need to meet some requirements:
You need to configure a processor that supports Apple Pay and enable the connectors of the credit card brands that should be available.
Navigate to Space > Payment > Configuration > Processors to configure the processor that should be used to process Apple Pay payments. Supported processors are Worldline and Concardis. Make sure to enable the connectors of the credit card brands that should be available for the processor. Supported brands are Visa and Mastercard.
Apple Pay is enabled by default, but you can disable it in your space: go to Space > Settings > Wallets and open Apple Pay.
Express Checkout shows an Apple Pay button directly on your own product and cart pages, so that customers can pay without going through a checkout form. Apple validates every such payment against the domain of the page that shows the button. Each of those domains therefore has to be registered with Apple and has to serve a verification file. Apple Pay in the standard checkout runs on a payment page and needs none of this.
Creating the session, rendering the widget and processing the payment work the same way for every wallet and are described in the Express Checkout integration guide. The steps below cover what Apple Pay additionally requires.
An enabled connector that supports both Apple Pay and Express Checkout.
Apple Pay enabled in your space.
Every shop domain that shows the Apple Pay button registered with Apple and serving the domain verification file.
Go to Space > Settings > Wallets, open Apple Pay and set Express Checkout to Enabled.
Apple verifies a domain by fetching a file from it, so every shop domain has to serve that file before you can register it. The same content is used for all of your domains.
On the Apple Pay configuration page (Space > Settings > Wallets, then open Apple Pay), click Download Verification File in the Domain Verification section.
Serve exactly that content from every shop domain, at exactly this address:
https://shop.example.com/.well-known/apple-developer-merchantid-domain-association
Open that address in a browser and check that you see the verification content, over HTTPS, without a redirect and without a login.
|
Important
|
Your own browser reaching this endpoint does not prove that Apple can. Apple fetches the file from its own servers, so a firewall, bot filter, geo-block or proxy that answers you but not them leaves the domain unverified, with nothing to see in a browser. Apple cannot follow a redirect or reach an address behind a proxy, and it publishes the address ranges it verifies from in Allow Apple IP Addresses for Domain Verification; allow them if your shop restricts access. |
Publishing the downloaded file at that path is the simplest way to do it, and not the only one: a route in your own shop that returns the same content works just as well. Apple only looks at the response at that address, not at how it is produced.
|
Note
|
If you do publish it as a file, keep the name exactly as downloaded, in lower case and without a file extension. A file published as apple-developer-merchantid-domain-association.txt is not found at the address Apple requests, and the domain cannot be verified. If your browser or editor appended an extension while saving, remove it.
|
Apple documents the same file and location in Configure Apple Pay on the web. You do not need your own Apple Developer account for this: your domains are registered for you through Apple’s Apple Pay Web Merchant Registration API, so serving it at that address is the only part that happens on your server.
On the same Apple Pay configuration page (Space > Settings > Wallets, then open Apple Pay), under Registered Shop Domains, click Manage Domains, add every domain that will show the Apple Pay button, and save.
Add the exact host name, for example shop.example.com. Subdomains are separate domains: if your shop is reachable as both example.com and www.example.com, add both.
What you save is the complete list. A domain you remove is withdrawn from Apple as well, and the Apple Pay button stops working on it.
Saving registers the domains with Apple right away. Apple refuses a domain that does not serve the content at that address yet, and the error is shown on the page.
After saving, click the Refresh button to ask Apple for the current list of registered shop domains and check that your change took effect.
Under Registered Shop Domains on the Apple Pay configuration page (Space > Settings > Wallets, then open Apple Pay), next to Manage Domains, there is a Refresh button. It asks Apple which domains are registered for your space and updates the list on the page.
Use it when the Apple Pay button stops appearing on a shop page. If a domain is missing from the list, Apple has dropped it, usually because the verification address stopped working. To get it back:
In a browser, open /.well-known/apple-developer-merchantid-domain-association on the missing domain.
If you do not see the verification content, publish it again, or fix what stopped serving it in your shop.
Add the domain again under Manage Domains and save.