We’re trying to add Apple Pay support to our mobile app (via the Developer Portal) but keep getting the error “the uploaded certificate could not be validated.” We’ve tried several times with both sandbox and production selected but keep getting the same error. We even tried adding Apple Pay to a different Application to see if that was the problem, but still same error.
I’m pretty sure we are following the instructions given on Square’s and Apple’s sites for the process. Am I missing something or is there a problem on Square’s end with processing Apple certificates?
I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:
Additional Documentation
In-App Payment Solutions
Build on iOS
Payment API: Process Online and In-Person Payments
If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.
Thanks for reaching out! Are you able to verify that your Apple Pay merchant identity certificate is publicly accessible and not restricted to internal/private distribution? Square needs to be able to validate the certificate during upload, so if it’s locked down, validation will fail.
I assume everything is public. There is no option anywhere when creating an identity or adding a certificate to indicate public or private.
@ChadDev Can you let me know what your application ID is (with the sq0idp-… prefix), as well as the approximate timestamp (date/time/timezone) of when you last got this error? Happy to dig through the logs and see what I can find here!
We’ve tried probably about 6 different times to get it to work with different apps but the one we need to get it working for has the ID: sq0idp-tVNdDmIaXmrObKCUPP-LbQ.
The approximate time of one of our tests is: 10:55 AM (PST) Mar. 30, 2026.
@ChadDev Would it be possible for you to do another test and let me know the timestamp of that? It looks like your earliest test at the end of March may have expired from our logs.
Ok, just tried it a couple seconds ago. Still same error.
