Yes, we have to handle the situation of maintaining multiple Apple Pay domain verification files at my employer as well. We just swap them out as needed since you can only host a single domain verification file at a time. In practice, it looks like once the file is verified, Apple doesn't seem to check it again since your domain is already validated. As our company continues to integrate with different payment gateways / providers, we just replace the domain verification file with the new one and verify the new one.

See this answer: CSR algorithm/size incorrect. Expected: RSA(2048)

See this answer: CSR algorithm/size incorrect. Expected: RSA(2048)

As the error message indicates, the Certificate Signing Request for the Merchant Identity Certificate requires the RSA-2048 algorithm. As an alternative, you can use openSSL to generate the CSR via the following steps: Execute the following openSSL command to create a private key: openssl genrsa -out privateKey.key 2048 Execute the following openSSL command to generate a certificate signing request (CSR) from the private key: openssl req -new -key privateKey.key -out certificateSigningRequest.csr Login to the Apple Developer Portal and upload the CSR file. You can then download the newly generated certificate.

The Certificate Signing Request for the Merchant Identity Certificate requires the RSA-2048 algorithm. As an alternative, you can use openSSL to generate the CSR via the following steps: Execute the following openSSL command to create a private key: openssl genrsa -out privateKey.key 2048 Execute the following openSSL command to generate a certificate signing request (CSR) from the private key: openssl req -new -key privateKey.key -out certificateSigningRequest.csr Login to the Apple Developer Portal and upload the CSR file. You can then download the newly generated certificate.