We created the P12 key from the Merchant ID certificate using KeyChain Access when developing Apple Pay for web.
Now we are in the process of deploying Apple Pay to Prod, do we need to generate a new P12 key for Prod?
I am not sure about the process here, and need some assistance or understanding.
Do I need to create a new P12 for Production deployment or can I use the P12 created when developing?
Thanks
Post
Replies
Boosts
Views
Activity
When checking if the device supports Apple Pay and has an active card, a call is made to 'applePayCapabilities'.
The documentation indicates this method asynchronously contacts the Apple Pay servers as part of the verification process.
My understanding is that this is a client side call, from the device/OS to the Apple Server.
The application (Apple pay on the web) is behind a firewall. What domain should I whitelist for this verification to be a success?
The documentation states canMakePaymentsWithActiveCard is deprecated but will continue to work on Safari browsers.
The suggested method to use applePayCapabilities is in Beta.
This is confusing for a developer! which method should be used. I do not want to use a 'Beta' version in a Production environment. On the other hand, I also don't want to use a method which is deprecated.
Any help or guidance would be welcome.
Thank you
The documentation says that, when calling the method canMakePaymentsWithActiveCard, the method asynchronously contacts Apple pay servers.
My question is, if I want to whitelist the Apple pay servers, should I be referring to this list?
https://developer.apple.com/documentation/apple_pay_on_the_web/setting_up_your_server#3172426