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

Question

Hunt_Welch OP

Created Nov ’21

Replies 1

Boosts 0

Views 2.6k

Participants 2

I've encountered an issue where we need multiple domain associations with separate Apple Pay implementations.

Briefly, we have a /.well-known/apple-developer-merchantid-domain-association already setup with Stripe, and now we need another, different version of the file to get setup with FreedomPay. FreedomPay insists this file represents a three-way relationship between all parties and I have no reason to disbelieve them.

I'm wondering if anyone has encountered this or if there is a standard procedure. I'm currently trying to find documentation on the exact way Apple Pay verification interacts with this file to see if we can produce it dynamically.

Boost

Answer 1

RB3207 OP

Jul ’22

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.

0