Fingerprint configuration in ClearSale

Where to send the Fingerprint?

In the fraud analysis request with ClearSale, send the session_id value in the Customer.BrowserFingerprint parameter.

How to configure Fingerprint on ClearSale?

Fingerprint consists of implementing a script on your checkout page (front-end), in the section where the shopper fills in payment data.

Fingerprint variables

The following table presents the variables for configuring Fingerprint with ClearSale.

VARIABLE	DESCRIPTION	TYPE	SIZE	REQUIRED
`session_id`	Identifies the user's session on the website and app. Can be created by the merchant or by ClearSale. The `session_id` value must be submitted in the `Customer.BrowserFingerprint` field.	GUID (recommended)	6 to 128 characters	Yes
`seu_appkey`	Identifies the merchant for creating the shoppers' device fingerprint. Provided by Cielo.	string	N/A	Yes

The session_id may appear in ClearSale's documentation as SessionID or SessionId.

There are three ways to include the script on your checkout page. The difference lies in how the session_id is created:

session_id created by the merchant;
session_id created by Google Tag Manager;
session_id created by ClearSale (recommended).

ℹ️
In the sandbox environment, provide the following session_id:
(seu_app fingerprint: r3j6a9f10bmssayw2thp)
This value must be sent whenever you use the sandbox environment.

Updated 19 days ago

Did this page help you?