FraudScan Enhanced
Introduction
FraudScan Enhanced involves adding a small dynamic javascript snippet to the payment page or a redirect page before the payment page. The snippet allows Empello to collect information regarding the nature of traffic landing on that content provider. This information will allow Empello to more accurately monitor the market via a FraudScan programme by ensuring that our monitoring closely matches the traffic profiles seen in the market.
Setup
To add the javascript protection to your page your backend must request it from the Empello API each time a user requests the page. To fetch a javascript string send a request to https://antifraud.empello.net/api/v2/js/fetch/, with the following fields:
| Field | Value | Required |
|---|---|---|
| api_key | API Key given to you by your account manager | Required |
| merchant_name | Merchant name exactly as presented on the dashboard | Required |
| service_name | Service name exactly as presented in the dashboard | Required |
| country | ISO 2 letter country code (eg GB, FR, CL) | Required |
| carrier | MCC-MNC Code separated by a hyphen (see here) | Required |
| use_fraudscan_enhanced | Boolean, set to true (1) if you wish to use FraudScan Enhanced (do not mix with FraudStop) | Required if you are running FraudScan Enhanced |
| param1, param2, param3, param4 | Allows you to store up to 4 additional parameters against this transaction, for example traffic source or campaign ID | Optional |
The API will respond with:
| Field | Value | Required |
|---|---|---|
| success | Boolean value, if 0 then an error has occurred | Required |
| message | Success or error message output | Required |
| jsstring | The javascript snippet that should be added to your page | Required if success is true |
See the following example cURL request and JSON response:
1 2 3 4 5 6 7 8 | |
Example response:
1 2 3 | |