Also experiencing the same issue here! Here's my timeline: Last time it worked: 13/08/2025 First time problem noticed: 18/08/2025 so it seems something changed between those dates. We also rely on ApplePaySession.applePayCapabilities to decide whether to show the Apple Pay button. Conflicting results between merchantIds? Adding some additional context here, we use two different merchant IDs for our environments, and they return conflicting results when calling: await window.ApplePaySession.applePayCapabilities(`${merchantId_credentials}`); //env1 { "paymentCredentialStatus": "applePayUnsupported" } //env2 { "paymentCredentialStatus": "paymentCredentialStatusUnknown" } Our current implementation environment is as below, Environment: Third party browsers Apple Pay JS API version 1.latest No configuration setup in Apple dev account, we use the merchantId generated by a third-party payment integration app Since the environments are on different domains, we thought the issue might be domain-related, but so far, no luck. As mentioned by @Johnxman, canMakePayments() is returning true so we could consider using that as a workaround. However, it would be great to get a clearer understanding of what’s actually causing this.