Configuring fingerprint
Implementing Cybersource analysis
To enable fraud analysis via Cybersource during a credit card transaction, you must add the following nodes to the authorization request: FraudAnalysis, Cart, MerchantDefinedFields, and Travel (this one only for airline ticket sales).
During Cybersource implementation, additional information can be stored using MDDs (Merchant Defined Data). These are numbered fields from 0 to N, used to store merchant-specific information.
Learn more at MDD Table.
Fingerprint with Cybersource
Fingerprint is the digital identification of the shopper's device. This identification consists of a set of data collected on the checkout page of the website or app.
In the analysis fraud request with Cybersource, the Fingerprint value will be the ProviderIdentifier generated by the merchant.
To configure Fingerprint with Cybersource, refer to the Antifraude manual.
Implementing ClearSale analysis
In the fraud analysis request with ClearSale, send the Payment.FraudAnalysis.Provider field as "ClearSale".
Fingerprint with ClearSale
Fingerprint is the digital identification of the shopper's device. This identification consists of a set of data collected on the checkout page of the website or app.
In the integration of the Gateway de Pagamento API with ClearSale fraud analysis, the session_id value must be sent in the Payment.FraudAnalysis.FingerPrintId parameter.
To configure Fingerprint with Cybersource, refer to the Antifraude manual.
Updated 10 days ago