Apple Pay (Checkout Champ)

Not all gateways support Apple Pay. Apple Pay is supported on Acquired3DS, Adyen, Authorize.netV2, Bambora, cardstream, Celerispay, CheckoutV2, ComputopV2, EasyPay Direct, Gala Technology, Merchant Warrior, MerchantConnect, MerchantConnectV2, NMI, NomuPay, PaysafeV2, Priority, SquareV2, SquareV2, StripeV2, Surgeify, Swipen, TotalApps, Truevo, Vantiv, VantivV2, Verifi, Whitelabel Payments, WorldlineV2, Worldpay.

Payments cannot be processed without a valid Payment Processing Certificate from your payment processor. You will upload your Gateway’s Payment Processing Certificate (a “csr” file with a .certSigningRequest or .csr file extension) to your CheckoutChamp gateway.

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.


Step 1: Obtain Payment Processing Certificate

Obtain an Apple Pay Payment Processing Certificate (.certSigningRequest file) from your gateway.

Step 2: Load Certificate into CheckoutChamp

Login to crm.checkoutchamp.com. Go to Gateways > Gateway List > edit the gateway on which to transact Apple Pay.

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 3: Upload Apple Pay file back to gateway

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.

Step 4: Register Apple Pay Domains

Login to app.checkoutchamp.com.

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.

 

Step 5: Navigate to each funnel on which to add Apple Pay


Step 6: Click the gear button on the top left to open the funnel settings


Step 7: Open the Payments section


Step 8: Enter Apple Pay details

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

 


Step 9: Edit Checkout page and add Apple Pay button

Step 9-1: Customize size of button by clicking on the button and dragging the highlighted corners or use Dimensions tab for advanced edits.

An Apple Pay button on a published page will be visible only on Apple devices, and its appearance will follow Apple Pay button CSS styling.

Apple Pay Buttons as shown in the Web Builder.
Apple Pay Buttons as shown on published checkout page on Apple devices.

Step 10: Save the page and exit the page builder.


Step 11: On the arrow leaving the checkout page, choose the Apple Pay button for navigation.


Step 12: Upsell pages

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.


Step 13: Publish the funnel. You’re done and ready to test!