You are an absolute legend! I was stuck at this step for over a month. Sending the object instead of the empty object fixed the issue.
Coupontools
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Hi Matt,
Thanks for your reply. The domain in the initiativeContext is correct so I don't think the issue is related to that.
I was wondering, I get a valid response from the Apple servers when validating the merchant using the validationURL retrieved from the client. The only thing I am not 100% sure of is all the different kind of certificates. As I get a valid json response from the validation URL, I assume my certificates are correct. Can I rule out the certificates being an issue?
The device itself is also not the issue. I am logged in as a Sandbox tester and was able to do a payment via https://applepaydemo.apple.com/.
The only parameters that are shared between client and server is the merchant identifier and the domain (initiativeContext) the request is send from. If I change one the merchant identifiers (client or server), I get an error from the validationURL which means the merchant identifier is not the issue. The initiativeContext is the only thing remaining which I checked numerous times and is configured correctly.