Post

Replies

Boosts

Views

Activity

Reply to Multiple Apple Pay relationships with differing apple-developer-merchantid-domain-association files
I have multiple Apple Pay Merchant IDs for different locations, each requiring its own domain association file. This forces me to verify each Merchant ID on a separate subdomain. The problem: the Apple Pay session must be initiated from the verified subdomain. It works on 10171.example.com but fails on www.example.com. I want to keep a single top-level checkout domain without redirecting users to subdomains. Is there any supported way to do this, or is top-level navigation to the verified domain always required for multi-Merchant ID setups?
1d