If the shopper is using a Mac without Touch ID, they will be prompted to verify the payment using an iPhone or Apple Watch registered to the same iCloud account. When the shopper selects Apple Pay, they are presented with a prompt to verify the payment using Touch ID or Face ID. You can download logos for Apple Pay which you can use on your payment form. Enable Apple Pay using your own Apple Developer account and certificate.Īfter you have finished enabling Apple Pay, you can show Apple Pay as an available payment method in countries where Apple Pay is supported.Set up your server for secure communication with Apple Pay.The same receipt should have the same result. There's no difference between the call coming from Postman vs coming from your client. Can you try making the call using Postman? Me: directly sending the receipts to the production endpoint is successful, you can see my HTTP reqbin requests in my post here: īrendan: Then it should work when calling our endpoint. What happens when you take one of the receipts and try calling the Apple verification endpoints directly? And if it was failing that way for multiple titles, we'd definitely be hearing about it. Now that it's been 48hrs I'll try again and see what the success rate is.īrendan: That doesn't sound like what we've seen in the past. In your experience, have these errors been related to titles recently going live on the App Store? All of my attempts were made within 24hrs of going live and all failed, so I disabled IAPs for the time being. If you wait and re-try later, you should be fine. What you're seeing happens every now and then (thankfully, occurrences have been rare, historically) - specifically, it's due to Apple's service incorrectly returning an error on the call to their production service. Should be helpful for anyone dealing with iOS receipt validation issues. Here's a transcript of the conversation I had with Brendan on the Discord.
0 kommentar(er)
