Apply for Payment Processing Certificate
The payment processor uses this certificate and its private key to decrypt Apple Pay payment data.
Important
This certificate requires an ECC 256-bit key, not the RSA 2048-bit key used for the Merchant Identity Certificate. Create a separate CSR and private key.
Create a certificate signing request.
Choose one method.
Method A: Keychain Access on Mac
Follow the Keychain Access procedure in step 2 in Apply for Merchant Identity Certificate, using these settings:
Field
Setting
Common Name
A distinctive name, for example Company Payment Processing
Let me specify key pair information
Select this option
Algorithm
ECC
Key Size
256 bits
CSR filename
apple_pay.certSigningRequest
Confirm that the new private key appears under login > Keys.
Retain this key.
Method B: OpenSSL
Run the following commands, replacing the example email address and Common Name:
openssl ecparam -name prime256v1 -genkey -noout -out apple_pay.key.pem openssl req -new -sha256 -key apple_pay.key.pem -out apple_pay.certSigningRequest -subj "/emailAddress=admin@example.com/CN=Company Payment Processing"This creates the CSR and its matching private key.
Download the certificate.
In Apple Developer, open the Merchant ID registered in step 1 in Apply for Merchant Identity Certificate.
Under Apple Pay Payment Processing Certificate, click Create Certificate.
Upload apple_pay.certSigningRequest.
Download the certificate as apple_pay.cer.
The downloaded certificate does not contain the private key. Combine both into a .p12 file.
Produce the P12 file.
Method A: Keychain Access on Mac
Import apple_pay.cer into the login keychain on the Mac used to create its CSR.
Under My Certificates, locate the Payment Processing Certificate and expand it. Confirm that its private key appears beneath it.
Select the certificate and matching private key, then select File > Export Items.
Export as Personal Information Exchange (.p12), using the filename apple_pay.p12.
Set an export password and retain it securely.
Method B: OpenSSL
Run these commands in the folder containing the certificate and private key:
openssl x509 -inform DER -in apple_pay.cer -out apple_pay.crt.pem openssl pkcs12 -export -legacy -inkey apple_pay.key.pem -in apple_pay.crt.pem -out apple_pay.p12Set an export password when prompted. If -legacy is not supported, omit that option.
Check the P12 file.
Run the following commands and enter the export password when prompted:
openssl pkcs12 -legacy -in apple_pay.p12 -nocerts -nodes | openssl pkey -pubout -outform DER | openssl dgst -sha256 openssl pkcs12 -legacy -in apple_pay.p12 -clcerts -nokeys | openssl x509 -pubkey -noout | openssl pkey -pubin -outform DER | openssl dgst -sha256 openssl x509 -inform DER -in apple_pay.cer -pubkey -noout | openssl pkey -pubin -outform DER | openssl dgst -sha256All three commands must finish without errors and return identical hash values. This confirms that the .p12 contains the matching private key and downloaded Apple certificate.
Check the certificate details:
openssl x509 -inform DER -in apple_pay.cer -noout -subject -enddate -textConfirm that:
The subject contains the correct Merchant ID.
The public key algorithm is id-ecPublicKey, with a 256-bit key.
The expiry date (notAfter) is in the future.
Record the expiry date for renewal.
Deliver the certificate.
Upload apple_pay.p12 in the MerchantWare Payments Portal.
From the username drop-down menu, select Payment Processing Certificates.
On the side menu, click Add Certificates.
Click Browse.
Select apple_pay.p12.
Enter the export password set in step 3.
Search for or select the merchant location to associate with the certificate.
Confirm that Type is Apple Pay and that Valid To matches the expiry date recorded in step 4.
Note
Do not upload the Payment Processing Certificate in the SuiteSpot. Upload it only in the MerchantWare Payments Portal.