ATLAS Device Fingerprinting


ATLAS serves as a full anti fraud solution, there are two ways to integrate ATLAS into your service

ATLAS device fingerprint web integration Howto

One is via the Javascript integration code:

<script src="{device_tracker_code}/fp.js"></script> /* device tracker code is generated in your dashboard, one device tracking code per domain is allowed */
<script type="text/javascript">
if(typeof Startup !== "undefined") {
Startup.Store('userEmail', '');
Startup.Store('userName', 'customtomer_username');
Startup.Store('credit_card_bin', '4122215293138267'); /* you may send the first 6 digits of the credit card or the entire number */

result = JSON.parse(result);
console.log('do after result'+result.fraudscore); /* you can view the entire result from this lookup */
alert('Ths is a high fraud score');


ATLAS also generated a device fingerprint of the user, this is a unique identifier that will allow you to cross check users for duplicate accounts. One device fingerprint is generated for each device the user uses to visit your online property.

the result from the Javascript call will look something like this:

#### The ATLAS Device fingerprinting API will always return a fraudscore, fingerprint, proxy (Boolean), request_id, city and country.
#### Keep in mind you can later query these requests with our API at a later time. These requests won't consume credits as they do not calculate a fraud score, instead they will show what fraud score 
#### was assessed at the time of the JS Call.
fingerprint=5c533967e88ed45374a594ae17f7ffa5 <-- this is the unique identifier that was generated
browser=Firefox 67.0
operating_system=Windows 10
proxy=no <-- this validates if the user 
request_id=bd7c39f6adc061689d5532a0af90b951 <-- you can use this request_id to query the result at a later time via our API

Values that can be passed onto via Javascript to our API are the following, you may pass some or all values for analysis, these are all taken into account to assess the risk of the user.

Startup.Store('userEmail', '');
Startup.Store('userName', '');
Startup.Store('userid', '');
Startup.Store('subUserId', '');
Startup.Store('custom_1', '');
Startup.Store('custom_2', '');
Startup.Store('custom_3', '');
Startup.Store('custom_4', '');
Startup.Store('billing_first_name', '');
Startup.Store('billing_last_name', '');
Startup.Store('billing_company', '');
Startup.Store('billing_country', '');
Startup.Store('billing_address_1', '');
Startup.Store('billing_address_2', '');
Startup.Store('billing_city', '');
Startup.Store('billing_region', '');
Startup.Store('billing_postcode', '');
Startup.Store('billing_email', '');
Startup.Store('billing_phone', '');
Startup.Store('shipping_first_name', '');
Startup.Store('shipping_last_name', '');
Startup.Store('shipping_company', '');
Startup.Store('shipping_country', '');
Startup.Store('shipping_address_1', '');
Startup.Store('shipping_address_2', '');
Startup.Store('shipping_city', '');
Startup.Store('shipping_region', '');
Startup.Store('shipping_postcode', '');
Startup.Store('shipping_email', '');
Startup.Store('shipping_phone', '');
Startup.Store('credit_card_bin', '');
Startup.Store('credit_card_hash', '');
Startup.Store('credit_card_expiration_month', '');
Startup.Store('credit_card_expiration_year', '');
Startup.Store('order_amount', '');
Startup.Store('order_quantity', '');
Startup.Store('recurring', '');
Startup.Store('recurring_times', '');

ATLAS Endpoint Integration (for mobile applications, kiosks or embedded devices)

ATLAS also works by exposing an API web service where you can send an the user’s IMEI or MAC Address via the internal device API. For example in mobile devices, such as tablets or phones made by Apple Inc, the UDID serves as a unique device identifier that can be used to be passed as the ‘did’ parameter as no device fingerprinting to identify the user.

All APPLE products will return the UDID which is a unique identifier that wont be reproduced by any other Apple device. In Android based devices, generating a unique identifier for the device is tricky because of Android’s OpenSource nature, please see for more information. ATLAS requires that that the parameter ‘did’ is generated using unique hashes for a device. In some cases, we recommend hashing ANDROID_ID + MAC_ADDRES (Bluetooth or WiFi), if MAC_ADDRESS for is not available, 0’s may be used, like this: 00:00:00:00:00:00



Getting Started

IPRisk is a provider of enterprise level tools that extend from IP GeoLocation to Face Recognition. Our tools are constantly being improved to prevent and detect the latest forms of online fraud and abuse.

IPRisk helps merchants to protect their online e-commerce stores from malicious fraudsters. As a result, it helps merchant to increase their revenue and reduce chargeback or fraud losses. It also improves operation efficiency by providing merchants a simple yet intuitive merchant area for merchants to easily investigate all fraud details, which could have been a complicated process without using fraud detection tool.

If you have any questions at any time, please submit a support ticket from the customer panel or

IP Intelligence API v1

IPRisk’s IP Intelligence API¬†provides and advanced and quick way to access IPv4 address information

Interacting with the API is simple and results are returned in ‘JSON’ or ‘XML’ format. There is no limit on the daily use of your account balance however please make sure to keep your account funded to avoid any interruptions in your applications or services.

Our API is only available through secure HTTPS connection for all users. Standard HTTP(port:80) is not listening on our service. Please make sure you are connecting to or else all requests will fail.

// Replace api_key and use info and output as you see fit.
//{format json|xml|}/{ip}/{api_key}
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, '{format json|xml|}/{ip}/{api_key}');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$output = curl_exec($ch);
$info = curl_getinfo($ch);