Configuring the Clover Payment Extension

Enabled drop-down list

Indicates if the Clover Payments Extension displays as an option for customers at checkout.
Values:

• Yes
• No

Title

Title of the Clover payment that displays to customers at checkout.
Example: Payment by card (Clover)

Environment drop-down list

Environment where the Clover Payments Extension is active.
Values:

• Production
• Sandbox

Debug drop-down list

Enables the debug mode for log analysis.
Values:

• Yes
• No
  Note: Log messages are logged in var/log/payment.log.

Merchant ID

Unique merchant identifier (MID) ({mId}) created on the Clover sandbox or production environment, for every merchant business.
See Locating the merchant ID.

Public Key

Token required for the Clover Payments Extension to connect to your Clover sandbox or production developer account. This token or public key allows you to use the Clover payments extension in the selected environment. See Setting up an API token

Private Key

Token required for the Clover Payments Extension to connect to your Clover sandbox or production developer account. This token or private key allows you to use the Clover payments extension in the selected environment. See Setting up an API token

Payment action

Indicates how each payment transaction is handled based on the selected payment action.
Values:

• Authorize—Ensures that the customer’s card is in good standing and has sufficient funds to cover the purchase. An authorization transaction places a hold on the customer’s funds for the transaction amount, for settlement at a later date. You can use the the Adobe Commerce built-in process to capture an authorization.
• Authorize and Capture—Ensures that authorization and capture occur simultaneously. Capture is the process of claiming authorized funds, that is, initiating the transfer of funds from the customer’s account to your merchant bank account.

Sort Order

Sets the display order of the enabled payment methods on the checkout page.