Overview

When a Clover reseller or merchant acquiring bank is approved for 3DS, associated merchants can enable 3DS services from their Clover Merchant Dashboard. The 3DS service is available as follows:

• For Hosted Checkout, Clover payment products, and Clover online ordering—The 3DS authentication service is automatically available when 3DS is enabled on the Merchant Dashboard as part of fraud tools.
  Note: 3DS is enabled at the merchant identifier (mId) level. If you are a developer working with multiple mIds, then your merchant needs to enable the 3DS service for each merchant identifier.
• For on-device integrations or Clover iframe integrations—Merchants need to configure the 3DS SDK and then initiate the SDK for payments using the Ecommerce API—Create a charge and Pay for an order endpoints.
• On a merchant's custom domain—The merchant owner or admin can enable 3DS on the Clover Merchant Dashboard. They need to provide a customer-facing business website link so that issuers do not decline transactions. On the Merchant Dashboard, go to View all settings > Business Information > Customer-facing information. Clover recommends adding your merchant's custom domain in the Website field, in the format: https://www.example.com/.

Once 3DS is enabled, all merchant transactions across networks, such as American Express®, Discover®, and Visa®, go through a 3DS scan. For Mastercard®, 3DS registration is required, and merchants may need to check with their reseller for Mastercard registration status.

Enable 3DS

1. Log in to the Clover Merchant Dashboard. The Merchant Dashboard appears.

2. Go to Settings > View all settings. The Settings page appears.

3. In the Ecommerce section, click Fraud Tools. The Fraud Prevention Tools page appears.

4. In the 3D Secure 2.0 Authentication section:

• Review the terms and conditions, select the checkbox to indicate agreement, and click Enable 3DS. A pop-up appears.
• Click the Accept transactions that fail the 3DS 2.0 authentication checkbox. This lets merchants process transactions even if the 3DS 2.0 authentication fails. In this case, the merchant assumes liability for any potential fraud associated with that transaction.

5. Click Save.

Related topics

• 3D Secure (3DS) authentication overview
• 3D Secure for Ecommerce transactions—Detailed overview
• Configure 3D Secure SDK for iframe and API integration
• Test 3DS integration