The IPQS device fingerprint API is designed to help your web or mobile app detect and prevent fraud, bots and bad actors. It uses artificial intelligence and machine learning to score users, identify fake and compromised devices and prevent chargebacks and fraud. By collecting and analyzing user behavior, the IPQS device fingerprinting API can detect fake traffic, carding attacks and even GPS spoofing. You can also use it to detect bots, emulators and other risky behavior.
Getting started with the IPQS Device Fingerprint API is easy. There is no setup or onboarding fee. IPQS provides an extensive library of unique device IDs. Once you have a API key, you can use it to access the full suite of fraud detection tools. If you already have an OAAM HTTP session, you can use it as a base to start fingerprinting your users. You can then use the IPQS Postback API to update the status of previous device fingerprinting requests.
The IPQS device fingerprinting API is available for iOS and Android. IPQS provides both standard and custom fingerprint types out of the box, but you can create your own to accommodate your application’s unique needs. Using the standard integration method, you simply send a request via HTTP POST.
After you receive the results, you can analyze the data using the IPQS data analysis tools. For example, you can find out how many times a user used the site and whether or not they made a payment. Similarly, you can see which pages generated the most clicks. This IPQS device fingerprint API information can be useful when you are analyzing high risk behaviors such as clicking on links with the word “buy” in the title. Alternatively, you can look at the list of top-performing users to gauge their overall risk level.
One of the most important elements of the device fingerprinting process is the Secure Cookie. The cookie helps to provide a one-time-use token that can be stored on a client computer. This cookie is sent to the OAAM server using an HTTP request. It is only valid for the duration of the session on the device. If the policy is not set to accept cookies, the cookie will be destroyed.
To get the most out of the device fingerprinting API, you should first append your device’s ID to a hidden form element. You can then make a GET/POST request to the URL below. However, to avoid eating into your API lookup credit, you should append the device’s ID to the form element using Ajax.
To retrieve all of the device fingerprinting information for a particular session, you can perform a search by session date. You can also choose to display the ‘Fingerprinting Details’ tab, which provides a breakdown of the fingerprints collected during the user’s session. Each of these tabs includes a variety of information, including the fingerprint type, the number of sessions created, and the alerts triggered for the device.
Lastly, you can check your device’s performance in terms of clicks. The Fingerprint Details tab provides a summary of the fingerprints that were created during the login and a list of the sessions that resulted in them.