Multiple Apple Pay relationships with differing apple-developer-merchantid-domain-association files

Yes, we have to handle the situation of maintaining multiple Apple Pay domain verification files at my employer as well. We just swap them out as needed since you can only host a single domain verification file at a time. In practice, it looks like once the file is verified, Apple doesn't seem to check it again since your domain is already validated. As our company continues to integrate with different payment gateways / providers, we just replace the domain verification file with the new one and verify the new one.

Any news for it , it seems that check is done now each time with the verification of the domain and one account needs to have one domain . The same domain cannot be registered for multiple accounts

Did anyone figure this out? Replacing the file worked for me as well, but that feels more like a short-term solution rather than an actual fix. Has anyone seen this issue pop up again after swapping files? Can you please update here if you find a permanent solution. @magnus83 @RB3207 @Hunt_Welch

Did anyone figure this out? Replacing the file worked for me as well, but that feels more like a short-term solution rather than an actual fix. Has anyone seen this issue pop up again after swapping files? Can you please update here if you find a permanent solution. @magnus83 @RB3207 @Hunt_Welch

Hi @Hunt_Welch,

The Apple Pay Web Merchant Registration API is intended for payment platforms and e-commerce providers, to register and manage a portfolio of merchants via REST API.

Please see the following post to answer your questions about configuring multiple providers, payment gateways, and merchants with this API:

Apple Pay Web and Ecommerce site hosting Multiple Merchants on a Single Domain Site

https://developer.apple.com/forums/thread/61538?answerId=829805022#829805022

Cheers,

Paris X Pinkney |  WWDR | DTS Engineer

This doesn't answer the question unfortunately. The docs still say the merchant needs to host an apple-developer-merchantid-domain-association. Well we already have an existing file from a different apple pay implementation that we need to keep in place, but we need to add a 2nd one. Is replacing the other one with the new one a valid solution? Or will it disrupt our other apple pay implementation from our first provider?

Hi @milesg000,

You wrote:

This doesn't answer the question unfortunately. The docs still say the merchant needs to host an apple-developer-merchantid-domain-association.

For merchants, the merchant ID domain verification file is a 1:1 association with your merchant ID and merchant certificate used to secure your Apple Pay requests. See the following documentation for more details:

Configuring Your Environment

https://developer.apple.com/documentation/ApplePayontheWeb/configuring-your-environment

For payment platform integrators using the Apple Pay Web Merchant Registration API, the payment platform domain verification file is a 1:1 association with your payment platform integrator ID and payment platform ID certificate used to secure your Apple Pay requests.

Platform integrators also can download and distribute merchant domain verification files to each merchant they've registered. For more information, please see below:

Preparing merchant domains for verification

https://developer.apple.com/documentation/applepaywebmerchantregistrationapi/preparing-merchant-domains-for-verification

Then, you wrote:

Is replacing the other one with the new one a valid solution? Or will it disrupt our other apple pay implementation from our first provider?

Replacing the file will invalidate the merchant ID that was removed due to a verification failure. The expectation is to use subdomains to host each domain verification file, as needed. For instance:

• Domain: example.com
• Merchant A: merchantA.example.com
• Merchant B: merchantB.example.com

Where the Merchant subdomains can be used as the [DOMAIN_NAME] placeholder below:

https://[DOMAIN_NAME]/.well-known/apple-developer-merchantid-domain-association

Cheers,

Paris X Pinkney |  WWDR | DTS Engineer

Hi  @RB3207,

Apple Pay does automatically re-verify your merchant domain after registration based on the expiration date of your SSL certificate.

To mitigate any issues with your Apple Pay integration, you should configure your environment to use subdomains for each registered merchant ID instead of rotating merchant domain verification files manually.

To learn more about merchant domain verification, please see below:

TN3173: Troubleshooting issues with your Apple Pay merchant identifier configuration: Your domain does not automatically re-verify

https://developer.apple.com/forums/thread/695538

Cheers,

Paris X Pinkney |  WWDR | DTS Engineer