Skip to content

Redirect Integration

In this integration type the client hosts a redirect page (or interstitial), receives the token, queries the validation API, and enacts the blocking decision.

This integration type is suited to aggregator/operator clients who do not host the payment pages. As long as the redirect page can be placed during the payment process then the transaction can be protected. This is easier to implement than the "iFrame integration" or the "Third Party Integration".

Implementation

It is important to ensure that the FraudStop script is allowed to complete and send datapoints to Empello before redirecting the user from the page. If the script is not given enough time to run then you will see a large number of false positives, or if using API v1 a large number of users without a token. To avoid this please use the FraudStop callback function to monitor when the script is ready:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
  EmpelloInterface.onFraudStopLoaded(function (statusCode) {
    if (statusCode === 101) {
      // main JS loaded
    }
    else if (statusCode === 201) {
      // success, the redirect flow can continue
    }
    else if (statusCode === 202) {
      // there was an error after the main JS loaded
    }
    else if (statusCode === 203) {
      // main JS timed out
    }
  });

Place the redirect functionality in the !# statusCode === 201 if statement.