Hi all,
I’m running into a confusing issue with Apple Pay domain verification. Apple’s documentation says to host the verification file at: https://yourdomain.com/.well-known/apple-developer-merchantid-domain-association
And the portal itself seems to expect the file to be served with .txt extension during verification. My first verification passed, but subsequent checks are failing — and I’m wondering if this mismatch is the cause. Should I Keep the .txt and configure my server to serve it at both paths?
Would appreciate any insights or official clarification.
Thanks!
Hi @jr_mcd_dev,
You wrote:
Should I Keep the .txt and configure my server to serve it at both paths?
Apple's verification system expects one specific path, with no file extension:
https://yourdomain.com/.well-known/apple-developer-merchantid-domain-association
Apple's verification crawls your domain periodically (not just at initial registration). If the file is only reachable at the .txt path and not the canonical path, re-verification will fail because:
- The crawler strictly requests the extensionless URL
- Redirects from
/apple-developer-merchantid-domain-association.txtto the canonical path are not followed reliably - Some CDN/cache layers serve stale or wrong responses on re-checks
To learn more about this behavior, see the following technote:
TN3173: Troubleshooting issues with your Apple Pay merchant identifier configuration
Cheers,
Paris X Pinkney | WWDR | DTS Engineer
