ApplePay: merchantID not registered for domain error

While testing ApplePay we met the problem: when we try to startsession with received validationUrl to Apple Pay Web in some cases we get unusual error.

For example, while send the request to this address:

https://apple-pay-gateway-pr-pod3.apple.com/paymentservices/startSession

we got correct answer (epochTimestamp, expiresAt, merchantSessionIdentifier, nonce, merchantIdentifier, domainName, displayName,signature).

But if we send the request to one of the following addresses:

https://apple-pay-gateway-nc-pod4.apple.com/paymentservices/startSession

https://apple-pay-gateway-nc-pod1.apple.com/paymentservices/startSession

an error returns: Payment Services Exception merchantId=******* not registered for domain *********

Up vote post of trednx Down vote post of trednx
4k views
Posted by
trednx
Reply
Add a Comment

Replies

Did you get a solution? I have the exact same issue. I'm just sending the request to `validationURL` in the request as documented but get this error. Seems strange that it's successfull based on `pr-pod` URLs - I don't know what the significance of those URLs are.


I thought perhaps being logged into iCloud with a Sandbox Account might be required?

Posted by
sdlondon
Up vote reply of sdlondon Down vote reply of sdlondon
Add a Comment

Hi!


Did you fix this or now the solution? We encountered the same problem. One merchant for two domains: on first everything works fine, on the second - 50\50

Posted by
pihtaplazius
Up vote reply of pihtaplazius Down vote reply of pihtaplazius
Add a Comment

One of the possible reasons can be that your domain is not registered in ApplePay.

  1. In Certificates, Identifiers & Profiles, select Identifiers from the sidebar, then select Merchant IDs from the pop-up menu on the top right.
  2. On the right, select your merchant identifier.
  3. Under Merchant Domains, click Add Domain.
  4. Enter the fully qualified domain name, then click Save.
  5. Click Download, place the downloaded file in the specified location, then click Verify (or OK button)
  6. Click Done.


That helped me.

Posted by
noc888
Up vote reply of noc888 Down vote reply of noc888
Add a Comment
Hi there!

We encountered the same problem, for one of the domains we was getting this error consistently. It occurred that our membership payment expired.
Posted by
gsmth
Up vote reply of gsmth Down vote reply of gsmth
Add a Comment