Clover Connect, integrated payment channel of Fiserv (via X-Payments)
A
Written by Anna “dohtur” Verbichenko
Updated over a week ago

Stores connected to X-Payments Cloud can be configured to use payment processing via Cardpointe, aka Clover Connect, integrated payment channel of Fiserv.

Features of Clover Connect, integrated payment channel of Fiserv

Feature

Supported

Sale

Supports transactions of 'Sale' type (Authorization and capture actions are completed simultaneously at the time of payment processing)

Yes

Auth

Supports transactions of 'Auth' type (An authorization hold is placed on the amount approved by the buyer to ensure the availability of funds for capture)

Yes

Capture

Allows capturing the previously authorized amount (The authorized amount is moved from the buyer's account to the account of the merchant)

Yes

Void

Allows removing an authorization hold from the buyer's account by the merchant

Yes

Refund

Allows issuing refunds (The money is returned to the buyer's account)

Yes

Get Status

Can provide information about the status of a transaction to X-Payments Cloud

No

Get Card

Can provide new/updated information about a saved credit card. For example, if a credit card gets re-issued, it is possible to get the renewed expiration date. If any other information changes, like the credit card number or the billing address, it is possible to access this updated credit card information as well.

No

Accept

Allows accepting transactions with a higher likelihood of risk

No

Decline

Allows rejecting transactions with a higher likelihood of risk

No

Test

Can test whether the merchant account details entered in X-Payments Cloud are valid

Yes

3D-Secure via
Cardinal Commerce

Supports 3-D Secure payer authentication via Cardinal Commerce. Best for PSD 2 in the European Union.

Supports 3-D Secure payer authentication via internal gateway service or via Cardinal Commerce

Tokenization

Supports tokenization (Allows billing a customer's credit card again - without X-Payments Cloud storing cardholder data).

Yes

Account Updater

Supports Account Updater service

No

Apple Pay

Supports Apple Pay

No

Google Pay

Supports Google Pay

No

Other payment methods supported by X-Payments Cloud are listed in the section X-Payments Cloud: Supported Payment Methods.

Prerequisites for setting up Clover Connect, integrated payment channel of Fiserv

  1. You must have an active account with X-Payments Cloud.

  2. Ensure your X-Cart store is connected to your X-Payments Cloud account. This connection can be established using the X-Payments Cloud connector add-on. For detailed guidance on setting up the connection, refer here. The "Getting Started" info for X-Payments Cloud is available here.

  3. Sign up for Clover Connect and acquire a set of API access credentials.

Sign up for Clover Connect and Acquire Your API Credentials

You can sign up for Clover Connect by submitting an application using the form on the https://integrate.clover.com/partner/x-cart page.

The Clover Connect activations team will reach out to inform you of the creation of your account and will provide you with a set of credentials for API access. These credentials will need to be plugged into X-Payments, enabling the system to connect with Clover Connect for payment processing on your behalf. The Clover Connect activations team will assist you throughout the setup process and guide you in conducting a test transaction to ensure everything functions correctly.

Below is an instruction guide for configuring payment processing through Clover Connect in an X-Cart-based store.

Configure Clover Connect, integrated payment channel of Fiserv

To start payment processing via X-Payments-based Clover Connect integration, complete the steps below:

  1. In your X-Cart store's Admin area, go to the Payment Methods page (Store Setup > Payment Methods).

    The Payment Methods page looks as follows.

  2. Scroll down the page to find your store's X-Payments Cloud payment method.

  3. Proceed to configure the payment method settings.

    The X-Payments Cloud Settings page opens.

  4. If you see the locked padlock icon on the page, unlock editing before proceeding further. To do so, click either on the padlock icon itself or on the "Unlock editing" link.

    Then, confirm your authorization to edit the payment method configuration by signing in to your X-Payments account.

    Once editing has been unlocked, the padlock icon on the page should appear open.

  5. Use the Add a payment gateway drop-down selector to add Clover Connect, integrated payment channel of Fiserv payment configuration for your X-Payments Cloud payment method: select the name of the payment gateway integration from the drop-down list and click Add.

    The Add new payment configuration page for Clover Connect opens:

  6. Provide your connection details for Clover Connect and specify your payment configuration preferences.

    • Name: The text entered here serves as the identification for the payment configuration within the X-Payments Cloud admin panel and the Admin area of your X-Cart-based online store. You have the option to retain the suggested name or modify it. For instance, if you plan to set up multiple payment configurations using Clover Connect, integrated payment channel of Fiserv, such as for processing payments in various currencies, it's advisable to customize the name. This allows for easier identification without the need to access the configuration details. For instance, consider a name like "Clover Connect - USD" to denote the currency used for payments through this configuration.

    • Site ID: The host part of the Base URL that has been provided to you. For instance, if the Base URL is https://fts-uat.cardconnect.com/cardconnect/rest, the Site ID should be specified as fts-uat. Usually, the Site ID is fts for the production environment and fts-uat for the sandbox. However, it's recommended to use the value received from Clover Connect as the primary choice.

    • Merchant ID: The specific MID value provided to you.

    • Username: The REST API Username value provided to you.

    • Password: The REST API Password value provided to you.

    • Initial transaction: The mode in which you want the payment transaction to be conducted when someone buys something at your online store: Auth (authorize the payment amount but not capture the funds yet) or Auth and capture (authorize and capture the payment amount at once).

    • Test/Live mode: Whether you are using the sandbox environment or the production environment. The production environment (Live mode) should be selected for real payments, whereas the sandbox environment (Test mode) should be selected for testing.

    • Order prefix: Your trading name or any other prefix that will help you to identify a payment transaction as originating from this specific online store.

    • Accept currencies: The currencies in which you will be able to accept payments via the payment method based on this payment configuration. By default, this setting is pre-set to All supported (N), which means all the currencies supported by the payment gateway - with the number N specifying the number of currencies. To limit the range of currencies that will be accepted, click on the All supported (N) button, uncheck the Select all box - this will unselect all the selected currencies - and check the boxes for the currencies that you will accept. For the sake of example, we are creating a configuration that will support only the United States dollar; so here we need to disable all the currencies but USD.

    • Credit card types: The credit card types you wish to accept via the payment method based on this payment configuration.

    • Order total limits (Minimum / Maximum): The transaction amount range that you wish to accept via the payment method based on this payment configuration.

    • Cancel not captured: Whether authorizations obtained for payments made in the "Auth" mode should be voided automatically within 30 days of payment if the capture of the funds has not been performed.

    • For Saved cards only: This setting is intended for migration purposes, allowing you to gradually replace this payment configuration with another. Enabling this option will prevent new payment transactions via this payment configuration. However, payment transactions for any saved customer cards already associated with this payment method will still be allowed.

  7. After adjusting the payment configuration settings as you require, be sure to click Save to save your changes.

    The payment configuration will be created; a success message will be shown at the top of the screen:

    New payment configurations in X-Payments Cloud are automatically activated upon creation. Your Clover Connect configuration will now display the "Enabled" status, denoted by the green 'Status' button. If necessary, you can temporarily disable this payment configuration at a later time using this button. As you are currently configuring Clover Connect for payment processing, please ensure the status remains enabled.

  8. After the creation of your Clover Connect payment configuration has been completed, a few additional settings appear in the lower part of the page. These settings allow you to activate additional services for this payment configuration:

    • 3-D Secure (+ 3-D Secure behaviour)

    • Apple Pay (Not supported by this module)

    • Google Pay (Not supported by this module)

    Before enabling 3-D Secure, please ensure this service has been enabled for your account on the Clover Connect end.

    Instructions for configuring 3-D Secure can be found here:

  9. After adjusting the settings related to additional services as you require, be sure to save your changes by clicking the Save button at the bottom of the page again.

That is it. You have created and adjusted your Clover Connect payment configuration. It can now be found on the list of payment configurations added for X-Payments Cloud:

If you haven't yet done so, adjust the Store Settings. After this, you should be able to successfully process payments with Clover Connect.

Did this answer your question?