Skip to content

Introduction

Preventing DCB fraud

Empello's FraudStop solution for the VAS market works to prevent fraudulent charging on DCB payment methods. FraudStop protects your payment page from the following threats:

  • In-app malware
  • Bot traffic
  • iFrame masking
  • MSISDN injection
  • Backdoor fraud

When used in conjunction with Empello FraudScan the full consumer journey can be protected.

Detection Technology

  • Spoofing detection, FraudStop detects tell tale signs of device spoofing used to make low quality traffic appear high quality.
  • Bot traffic detection, FraudStop will spot high volumes of server traffic typically used in backdoor fraud and MSISDN injection
  • Proxy detection, FraudStop catches fraudsters from outside the country often seen in backdoor fraud.
  • User behaviour monitoring, FraudStop will monitor a users interaction with the payment page to judge their authenticity.
  • App blacklist, using intelligence gathered from FraudScan as well as machine learning analysis of incoming FraudStop traffic Empello maintains an extensive blacklist used to prevent known bad apps from subscribing your users.

Increased Traffic Insight

  • See how conversion rate compares across your services
  • See which Android apps are driving to traffic to your services
  • Optimise traffic source cost and quality without revealing to Empello your suppliers

Other Benefits

  • Global coverage
  • Low consumer impact due to low latency servers and high performance javascript
  • GDPR compliant
  • Fully secure, audited regularly
  • Used by over 20 mobile operators worldwide
  • Protects in excess of 1 billion consumers

API v1 vs API v2

The API version 1 documentation is provided to support legacy users and specific use cases, if you are performing a new implementation please use API version 2.

In version 2 the javascript file is imported on your backend, using version 1 the javascript is imported browser side. Version 2 helps to improve the execution time of the FraudStop script by bundling the script with the page itself, which in turn reduces the number of false positives due to missing data points. Version 2 also removes the requirement to use a separate script for each merchant.