Hi, I wanted to let you know that I made changes related to TLS so it matches the cipher suite Apple uses. I configured the access rules so nothing is being blocked, and I ran tests using PowerShell and OpenSSL—every result returns HTTP/1.1 200 OK. I also verified that the URL Apple says it will use to validate the file under /.well-known works correctly and it does display the contents of the file. However, when I try to verify the domain in Apple’s portal, I still get the same error: “Domain verification failed.” Could you please help us with an alternative solution or any additional verification steps we should perform? Thank you.

I’m trying to integrate Apple Pay on the web into a demo I’m building. In order to charge with Apple Pay, I need a Merchant ID, which must have the following set up: the Apple Pay Payment Processing Certificate, the Apple Pay Merchant Identity Certificate, and Merchant Domains. The one that’s giving me the error is Merchant Domains. The web environment/server is already configured and has no restrictions, and for Merchant Domain validation it requires a URL like this: https://domain/.well-known/apple-developer-merchantid-domain-association.txt. This URL is already configured with my demo domain, and when I access it I can see the contents of the apple-developer-merchantid-domain-association.txt file, which is what Apple uses to verify the domain. However, on Apple’s page, when I try to verify it, I get the error “Domain verification failed.” That seems strange to me because when I access the URL Apple uses, it does show the file contents. Could you help me with this? Also, just to mention it, I’m hosting the page on Azure App Service. Thanks.