Authorization Header Key - Click ‘Generate key’ (this can be manually set to the same key which was generated for the Signature Key, either method is fine)
Share the Authorization Header Key
Go to the Gateway section and select the following Events:
Payment approved
Payment declined
Select the appropriate entity from ‘Entities and processing channels’.
Click 'Create webhook'
Go to Keys section and click on either of the newly created public and secret keys. Share the Processing Channel ID
On the Apaya Portal, go to ‘Connectors’ and click on the
is already listed in ‘My Connectors’, click the ‘edit’ icon. Enter the bold items from above in the Apaya Portal ‘Edit Account’ section for Checkout.com as shown below:
Note: To utilise Google Pay, provide the following:
GoogleMerchantId - Set to your Google Pay Merchant ID on Production (or set to anything on Sandbox)
GoogleMerchantName - Set to your Google Pay Merchant Name on Production (or set to anything on Sandbox)
If you don’t have these details then enter any string, e.g. ‘-’ or ‘UNAVAILABLE’.
Technical setup for Apple Pay:
If you don’t have an Apple Developer account and you want to utilize Apaya’s account, do the following:
Provide your Apaya Account Merchant with your Checkout.com ‘Public Key’ and Apaya will setup everything to do with your Checkout.com account.
Once complete, we will notify you so you can proceed to add Apple Pay to your Apaya Portal workflow in the Studio to test a transaction.
If you have your own Apple Developer account, perform the following steps:
instructions on the Checkout.com website, going through the ‘Set up Apple Pay’ from steps 1 to 7, you don’t need to do step 8. Please use the instructions below when performing the relevant steps.
Once you have created an Apple Merchant ID, send the following in its exact format to your Apaya Account Manager.
Description
Identifier
When you get to Step 5: ‘Prepare your domain for Apple Pay verification’ please use the following domain in point 5.3 so your certificate works on the Apaya platform.
