Hi Matt, Hope you are doing well. I was under the impression that we had to bundle a certificate with the new build which I now understand is not needed. Thanks for clarifying. As a next step, we understand that we need to generate a new "Apple Pay Payment Processing Certificate" and share it with our payment service provider(PSP). You had mentioned in your previous statement "Next, you will need to activate the new keys/certificate within the Apple Developer Account and this triggers the new keys to be propagated to our data centers and will be used for all new transactions.". Will the old certificate no longer be active for transactions after activating the new certificate? Will PSP be able to revert to the old certificate if there are any issues during the migration to the new certificate? Thank you for your assistance.

Hi Matt, Thank you for your response. As I understood from your above response is that if we upload a new certificate for Apple Pay then the payments through the old certificate will no longer work. If we upload a new build with a new certificate then it may take at least two days for approval and may take around 1 week for the majority of the users to migrate to the new build. So many users will not be able to use Apple Pay and will receive errors. Can you suggest the best approach for updating the certificate without affecting the existing users?