Last updated
Last updated
You do not need your own Apple Developer account for this process!
The Apple Merchant ID used with your gateway will be created by and maintained by CheckoutChamp.
Not all gateways support Apple Pay. Apple Pay is supported on Acquired3DS, AdyenV2, Airwallex, Authorize.netV2, Bambora, cardstream, Celerispay, CheckoutV2, EasyPay Direct, eMerchantPay, Fluid Pay, Gala Technology, Merchant Warrior, MerchantConnect, MerchantConnectV2, NMI, NomuPay, PaysafeV2, Priority, SquareV2, SquareV2, Stripe, Surgeify, Swipen, TotalApps, Truevo, Trust Payments, Vantiv, VantivV2, Verifi, Whitelabel Payments, WorldlineV2, Worldnet, and Worldpay.
Fluid Pay and Trust Payments offer a special onboarding workflow. See the appropriate tab in Step 1 to begin.
Apple Pay is generally one-time use. Rebills and 1-click upsells are supported on AdyenV2, eMerchantPay, Merchant Warrior, Stripe, CheckoutV2, and Trust Payments.
Payments cannot be processed without a valid Payment Processing Certificate from your payment processor.
The Payment Processing Certificate is a file obtained from your gateway that usually ends with a .certSigningRequest or .csr file extension.
You will need to follow this guide to obtain the file from your gateway (see ) and upload this file to CheckoutChamp using the Upload Certificate button under the Apple Pay section on the gateway edit page in the CRM (see ).
CheckoutChamp will upload this file to Apple, and Apple will use the public key from the certificate to encrypt Apple Pay tokens during checkout. Your gateway will then use the private key from the certificate to decrypt the Apple Pay token in order to process the payment.
That is why certificates are gateway specific, and the same certificate cannot be used across gateways.
Some gateways require that a .cer file be uploaded back to them.
This is a file that is generated by Apple that can be downloaded via the Download Apple File button on the gateway edit page in the CRM after CheckoutChamp has completed on-boarding of the certificate and enabled the gateway for Apple Pay (see ).
Please Note: Your Gateway’s Payment Processing Certificate EXPIRES every 25 months. You will need to generate and upload a NEW certificate to your CheckoutChamp gateway prior to the expiration date.
Obtain an Apple Pay Payment Processing Certificate (.certSigningRequest file) from your gateway.
If your gateway requires that you provide an Apple Pay Merchant ID to obtain a certificate, copy the Pending Apple Pay Merchant ID from the gateway edit page in the CRM.
Inside of Airwallex:
Go to Payments > Settings.
Click Manage next to the Apple Pay row.
Click the Upload Certificate in the iOS certificates section.
Click Download CSR file.
A .certificateSigningRequest file will download.
Keep that page open and in a new tab go to the gateway edit page in the CRM of your Airwallex gateway. From there:
Click the Upload Certificate button in the Apple Pay section and upload the .certificateSigningRequest file downloaded from Airwallex.
Wait for CheckoutChamp to board this certificate onto Apple Pay. This may take some time. You will be notified by email when it is complete.
Once on-boarding has been completed in CheckoutChamp, return to the gateway edit page and click Download Apple File.
A .cer file will download.
Return to the iOS certificates page in Airwallex. From there:
Click Select file under the Upload your certificate file step.
Select the .cer file downloaded from the gateway edit page in the CRM.
Click Upload.
Note: Not all gateways support Apple Pay. See the list at the top of this article.
Click the green Certificate button on the right side and upload the certSigningRequest file.
Be sure the file matches the gateway (e.g., a Stripe file is valid only on a Stripe gateway).
After the file is uploaded the file name appears. There is a button to remove the file and a button to upload a new certificate. Use these buttons if a file was uploaded in error.
Now wait. CheckoutChamp will take some time to board this certificate onto Apple Pay. You will be notified by email when it is complete. When it is complete then begin Step 3.
Step 2 is complete when Apple Pay is enabled on the CheckoutChamp gateway. Your payment gateway may require an Apple Pay Certificate File (.cer) be uploaded for their verification. Use the Apple Pay File button to download the file.
Go to the hamburger menu in the top right and select Settings. Scroll down to the Apple Pay - Domain Setup section. Click Register Domain. Choose the domain and the gateway on which to process Apple Pay (the gateways to select should be those that have successfully completed step 2). Save. Repeat this for each domain on which Apple Pay will be transacted.
Gateway and Partner Merchant Identifier should be filled in. Do not edit. Optionally set Merchant Name, Country, and the Require Address option. Save.
Merchant Name: Customizable merchant name to display to customers while authorizing payment.
Ex: "Touch ID to Pay My Store (displayName) $118.00"
Country: Country to use for each Apple Pay Session
Option 1:
Your gateway supports a 1-click upsell on Apple Pay using a payment token returned from the gateway at checkout
Place one or more standard buttons on each upsell page. Follow standard instructions for those buttons to submit the upsell. Add class cc-one-click-btn to each button. There is no need to have an Apple Pay button on each page. The buttons will submit using the original payment token.
Option 2:
Your gateway does not support Option 1. You prefer to have a generic button on upsell pages instead of an Apple button.
Place one or more standard buttons on each upsell page. Follow standard instructions for those buttons to submit the upsell. The buttons will automatically support Apple Pay or non-Apple Pay based on the checkout. Apple Pay will redirect the consumer to Apple to complete the upsell. No additional work is needed.
Option 3:
Your gateway does not support Option 1. You prefer to have an Apple button on upsell pages.
Place one or more standard buttons AND one or more Apple Pay buttons on each upsell page. Choose all the buttons on the arrow(s) leaving the page. When the live page loads the standard buttons are removed if the checkout was with Apple Pay. Pressing the Apple Pay buttons will redirect the consumer to Apple to complete the upsell. When the live page loads the Apple Pay buttons are removed if the checkout was not Apple Pay. The standard buttons will submit the upsell.
Log in to the Authorize.net portal -
Login to . Go to Gateways > Gateway List > edit the Fluid Pay gateway on which to transact Apple Pay. Press the Generate Apple Pay Certificate button.
Login to . Go to Gateways > Gateway List > edit the Trust Payments gateway on which to transact Apple Pay. Press the Generate Apple Pay Certificate button.
Login to . Go to Gateways > Gateway List > edit the gateway on which to transact Apple Pay.
Login to
Apply Pay checkout is available only on Apple devices. Apple Pay buttons on a live page will only display on Apple devices.
Use these instructions for Apple Pay processing on CheckoutChamp hosted pages
