The following fields are specific to this gateway integration:

• API Key : The bearer API key used for Credit Card and ACH transactions. You can obtain this API key by navigating to Developers > Keys in the Checkout.com dashboard.

  Note: The API key required in this field was updated in the 2022.10.R1 release.

  • The creation of a new Checkout.com gateway instance with the old deprecated API key is not allowed.

  • For ACH transactions, if you have not provided a new bearer API key since the 2022.10.R1 release, your ACH transactions cannot be processed because the existing API key has been deprecated as requested by the Checkout.com gateway. Please obtain a new bearer API key from the Checkout.com dashboard and enter it in this field.

  • For existing gateway instances using the old deprecated API key, only credit card transactions are supported.

• API Key (SEPA): The API key used for SEPA transactions. You can obtain this API key by contacting Checkout.com support.

• SFTP Username(optional): This field is required for Gateway Reconciliation. Contact Checkout.com to get your username and enter it in this field. Your Zuora username and public key will be used to access the SFTP server. See the Gateway Reconciliation for Checkout.com for more information about Gateway Reconciliation.

• Default Soft Descriptor(optional): The default soft descriptor for payments. It is required for all Direct Debit payment methods.

• 3DS Challenge Indicator: If 3DS2 is enabled in the Payment Pages settings, the selected indicator in this field will be passed to the gateway. For more information about this indicator, see the Checkout.com documentation. Ultimately, it is the issuing bank that determines whether a card needs to be authenticated through a challenge.

• Soft Description: Soft Descriptor is used to define the merchant name or product description that will appear on the customer's statement. This field is required if you want to use Soft Descriptor. For more detailed information, seeConfigure dynamic soft descriptors

• The following fields are related to Level 2 and Level 3 data processing: If Level 2 and Level 3 data processing is enabled, additional information such as the amount of sales tax and order and line items is passed to the gateway when processing a credit card transaction. This information might result in lower interchange rates on eligible commercial, corporate, and purchasing cards. See Level 2 and Level 3 data processing on Checkout.com for more information

  • Enable L2

  • Enable L3

  • ProductCode Custom Field API Name

  • CommodityCode Custom Field API Name