Setup Apple Pay with Checkout.com
Learn how to set up Apple Pay together with Checkout.com to accept frictionless credit card payments from the customers via Touch ID and Face ID.
Last updated
Learn how to set up Apple Pay together with Checkout.com to accept frictionless credit card payments from the customers via Touch ID and Face ID.
Last updated
Customers with Apple Pay-compatible devices can utilize this payment method to ease the process of credit card payment. Apple Pay eliminates the need to type the card information and shipping details manually. Customers only need to authorize the payment using biometric authentication such as Touch ID.
In order to configure and use Apple Pay with CloudWaitress, you need to prepare some business accounts and tools as follows:
A Checkout.com business account. You can send an inquiry to create a new account to Checkout.com here - https://www.checkout.com/contact-sales
An Apple developer account; make sure you have a proper role to create identifiers and certificates.
A working domain with a valid SSL certificate.
Access to openssl command-line tool. You can learn more about OpenSSL here - openssl.org
Log in to your Apple Developer account.
Create your merchant by going to Certificates, IDs & Profiles > Identifiers, click the plus button, select the Merchant IDs section, then click Continue. You can quickly access this section by access this URL - https://developer.apple.com/account/resources/identifiers/merchant/add
Choose a useful description for the merchant.
For merchant ID, you should use a descriptive name to indicate both your business and the environment you will use it in, for example, merchant.com.mystore.production.
Log in to your Checkout.com Hub Account - https://hub.checkout.com
Go to Settings > Apple Pay and click New certificate
Click Download your certificate signing request. You'll receive a .csr file. You should store this file in a convenient location as you'll need that file for your Apple Developer account.
Click Continue until step 3 and leave this page open.
Go back to your Apple Developer account, go to the Merchant IDs list section - https://developer.apple.com/account/resources/identifiers/list/merchant, and click on the merchant you created previously.
Scroll to Apple Pay Merchant Identity Certificate section and click Create Certificate.
Select No to the question about processing payments in China and click Continue.
Upload the.csr file and click Continue.
Click Download, and store the .cer file that you received.
Go back to your Checkout.com Hub Account, and update this .cer file.
Go back to your Apple Developer Account and access the merchant page as previous steps.
Under the Merchant Domains section, click Add Domain.
Enter the domain for your business and click Save.
Click Download to get the .txt file.
You should store this file in an accessible place. The domain verification step is not completed yet. We're going to get back to this as we configure Apple Pay on the CloudWaitress.
Access your terminal and create a .csr and .key file using this command:
Inside the terminal prompt, enter your details. Make sure you leave the password blank. You'll get a .csr and .key file.
Go back to your merchant page in Apple Developer Account.
Under the Apple Pay Merchant Identity Certificate section, click Create Certificate.
Upload the.csr file you created from the above command. It should be called uploadMe.csr if you just copy the command above.
Click Continue then click Download to get your .cer file. The file name should probably be called merchant_id.cer.
Convert the .cer file into a .pem file using the following command:
After going through all the above steps, you should have the following at your hand:
An Apple Merchant ID
A configured Checkout.com account that linked to your Apple Merchant.
A domain that linked to your Apple Merchant, and it should be in the Pending state for now.
A apple-developer-merchantid-domain-association.txt file that is provided by Apple when you add the domain.
A .key and .pem certificate files.
After configuring Apple Developer Account and Checkout.com, we need to do some steps on the CloudWaitress dashboard to make Apple Pay fully functional.
Head over your restaurant settings in your CloudWaitress dashboard.
Click on the Payments tab and click Add Payment Method.
Select Apple Pay (Checkout.com) in the payment method list, and click Add Method.
Head over to your Checkout.com Hub Account and go to Settings > Channels.
Create a new channel if necessary.
Access your channel, under the API Keys section, you can copy the Secret key and Public key.
Next, you need to update Apple Pay (Checkout.com) payment method details. Specifically, we need the following fields:
Setting Option | Description |
Checkout Secret Key | The secret key from Checkout.com |
Checkout Public Key | The public key from Checkout.com |
Apple Pay Merchant ID | The identifier of your Apple Merchant, merchant.com.mystore.production, for example. |
Apple Pay Merchant Name | The description of your Apple Merchant, you can get it inside the merchant page |
Apple Pay Merchant Domain | The domain name that you registered with Apple Merchant. You should drop the |
Apple Pay Merchant Domain Association | Copy the content of |
Apple Pay Merchant Identity Certificate | Copy the content of the |
Apple Pay Merchant Identity Private Key | Copy the content of the |
Click Save to update the settings.
Go back to your merchant page in your Apple Developer account. Under the Merchant Domains sections, you should see your domain is currently in Pending status. Click Verify, the status of your domain should be Verified now.
If you receive the warning about the Apple Pay Platform Web Merchant Terms and Conditions like the above image. You should ask your Apple Developer account holder to visit the merchant page, click on the link inside the warning, and accept the terms. Otherwise, you'll not be able to make changes to the merchant like adding domains or generate certificates.
If you receive errors when processing the payments, please check the Apple Pay certificate again. You can try to generate new certificates and update your payment settings accordingly. If the problem still happens after changing the certificates, please contact us for more supports.
