Case Study

How an online grocery delivery service prevented credit card fraud with FingerprintJS Pro

A grocery delivery service needed to prevent stolen credit cards from being used by new accounts without impacting legitimate users. FingerprintJS Pro’s accurate browser identifier increased fraud identification accuracy compared to their existing anti-fraud technology, reducing stolen credit card purchases and saving time on manual checks.

Download the PDF

Results

Credit Card

Prevented stolen credit card purchases from fraudsters

The company was able to identify suspicious purchases before they happened by flagging visitors with multiple accounts or a history of fraudulent transactions.

Anonymous Identification

Saved fraud analyst time spent on manual payment review

FingerprintJS Pro reduced false positives that would otherwise have to be reviewed by the company’s internal fraud team

Gears

Simplified rule management from previous solutions

FingerprintJS Pro’s API and webhooks integrated easily into the company’s existing anti-fraud system, with the increased accuracy allowing them to simplify previously complicated rulesets for flagging suspicious transactions.

Customer Overview

FingerprintJS began working with a fast-growing online grocery delivery service looking to prevent multiple forms of fraud. This multi-national company has both a web portal and a native app where customers can order items from local businesses to be delivered same-day to their door.

Sector:On-Demand Delivery
Use Case:Credit Card Fraud
Employees:1,000

FingerprintJS Features

  • 99.5% Accurate Identification
  • Browser Fingerprinting
  • GDPR and CCPA Compliant
  • Incognito Mode Detection
  • Geolocation

The problem

Stopping credit card fraud

The company wanted to reduce fraudulent purchases from stolen credit cards. Typically, stolen credit cards were being used by new accounts created via the browser. The new user would make 1-3 fraudulent purchases and abandon the account. From analysing IP data and other browser signals, the company determined that much of the fraud was being done by users who already had multiple accounts with their service, and often had made fraudulent purchases in the past.

The company had built a sophisticated anti-fraud system that took into account a visitor’s device, IP address, and browser fingerprint to flag suspicious purchases, however some fraudulent purchases were still falling through the cracks. The company found that the accuracy of their current fingerprinting solution was too low to catch all fraudulent activity, resulting in chargebacks, lost revenue, and a threat to their seller reputation.

Their anti-fraud system was also causing a number of false positives - transactions that were flagged as suspicious but were later found to be legitimate. Flagged transactions were blocked automatically within the web application only in extreme circumstances - typically flagged purchases were sent to an internal fraud analysis team to review. These additional false positives were taking up valuable time for the fraud department to review and dismiss.

The company wanted to add another high accuracy browser identifier to their anti-fraud technology stack that would reduce fraud by improving the overall accuracy of identification, and save their fraud department time.

Cleaning up anti-fraud rulesets from legacy products

From using multiple anti-fraud vendors, the logic to determine which purchases were suspicious and required review had become very complicated. The level of complexity made it difficult for the risk team to troubleshoot their own system and make changes.

The company started an internal rule management project to map out all of their individual rule triggers, and simplify the logic based on historical fraud data. If they were going to add an additional service to their anti-fraud tech stack, it needed to be easily integrated and unopinionated, allowing them to use their own rules logic and avoid introducing additional complexity.

Why FingerprintJS?

As the company had already been working with several vendors for device identification, FingerprintJS had come up in their research into an additional accurate identifier that could be incorporated into their existing solution.

Successful pilot that improved accuracy of existing solution, improved confidence in credit

After comparing FingerprintJS Pro with their existing browser identifiers, the company found that FingerprintJS Pro’s visitorIDs were more accurate and made fewer false positives, which allowed them to improve their credit card anti-fraud workflows significantly.

Ease of incorporation into existing workflows

As the company was cleaning up their existing anti-fraud rule logic, they found FingerprintJS Pro’s API and webhooks made it easy to incorporate high accuracy identification without having to adopt another opinionated anti-fraud service.

FingerprintJS Pro’s Javascript snippet also had minimal impact to browser performance, keeping the customer experience speedy and unhindered by new anti-fraud measures.

Get in Touch

Learn how FingerprintJS Pro can help your business build a custom solution to prevent online fraud.

Talk to usContact Sales
Get Started TodayStart Free Trial