Computop AI Protect

About Computop AI Protect (Powered by Nethone)

Computop AI Protect is an AI based fraud detection solution with Profiling and machine learning models to help lowering charge back rates and risk of fraud. The system works towards profiling the traffic on the site, detecting fraudulent behavior and providing business intelligence insight. It processes the data provided and it needs to be inquired in the right moment to assess the risk level of fraud or to provide insight in the moment of the inquiry.

AI Protect solution

The solution work as two step process

• Profiling solution – to collect user data

• Inquiry – to provide recommendation on the transaction

This Fraud Screening/Check on transaction can be used for several payment methods, we focused on Credit Card, SEPA and Paypal transactions but it can be extended.

Recommendation result of the Fraud Screening from AI Protect is:

• Accept – Transaction is considered non-fraudulent

• Reject – Transaction considered fraudulent

• Review – Transaction Rejected. Merchant has possibility to review the Inquiry in the Panel and make necessary changes to the rules if needed.

Implementation

Computop has implemented the AI Protect on our Hosted Payment Pages paymentpage.aspx, payssl.aspx and paysdd.aspx.

AI Protect (Profiling + Inquiry) HPP

The profiler module is implemented as the option to use a pre-authorization feature using our hosted payment page (payssl.aspx) or Payment forms paymentpage.aspx and paysdd.aspx.

The practical way is that before doing an authorization, we can use the data sent by the merchant in the request and do a fraud check before the authorization takes place.

The logic that can be used is:

• if the fraud check status is accepted = Computop triggers the authorization

• if the fraud check status is reject, the authorization never takes place, customer can use a different payment method

AI Protect (Profiling + Inquiry) server to server and Paypal

The profiler was implemented in order to be able to do fraud checks via server to server for Credit card, PayPal and EDD payment methods.

However the merchant need to implement profiling solution on their website.

Profiling Implementation

The following are the three steps of Profiling

1. Load the java script

2. Initiate Profiling

3. Complete Profiling

JavaScript file

This JavaScript file contains profiling logic. The static JavaScript file should be included on the website with URL of the form https://domain_name/s/merchant_id/script_name.js

Note*: Profiling script is provided by Nethone during on-boarding.

Script Inclusion

The following code snippet needs to be included in the page where merchant wishes to have the profiling. Usually this is Payment Page.

1
<!-- javascript inserted at the bottom of body; merchant_id may be hardcoded or inserted by backend, crossorigin="use-credentials" property is mandatory-->
2
<script type="text/javascript" id="SCRIPT_TAG_ID" crossorigin="use-credentials" src="https://provided_name.nethone.io/s/{merchant_id}/dNfsXe.js" async></script>

Script initializing function

Script initializing function (dftp.init) must be executed to gather user’s browser data. It should be called when the form has loaded. Function requires one argument, called options which is a JavaScript object with multiple properties.

Possible properties are:

attemptReference parameter

attemptReference is used to match the inquiry performed to the data gathered about a user by the profiling script. It must be a unique value generated upon every form view. You should never reuse attemptReference. In case of Single Page Applications do not reinitialize the profiling solution.

Behavioral data parameters

Handling of behavioral data gathered by the profiling script is controlled by sensitiveFields, allowedFields and secretFields parameters. Passing sensitiveFields and allowedFields controls how behavioral data from fields that are not otherwise specified will be treated. The possible modes of handling not specified fields are standard and alternative.

Standard mode:

This is the recommended mode. In this mode fields not otherwise specified will have full behavioral data gathered. Passing only sensitiveFields enables this mode, secretFields can be additionally passed.

Sample usage:

1
dftp.init({
2
  attemptReference: '8b7115e0-49d2-438b-b88f-b265e44b156f',
3
  sensitiveFields: ['number', 'cvc'],
4
});
5
// or
6
dftp.init({
7
  attemptReference: '8b7115e0-49d2-438b-b88f-b265e44b156f',
8
  sensitiveFields: ['number', 'cvc'],
9
  secretFields: ['password'],
10
});

Profiling completion

In order to ensure that all necessary profiling data was collected, it’s recommended to use dftp.profileCompleted function. It returns a Promise object that is resolved when we have completed processing and it’s safe to do an inquiry.

1
Sample usage with modern JavaScript:
2
 
3
try {
4
    await dftp.profileCompleted();
5
} catch (err) {
6
    console.error("Profiling failed with err: " + err);
7
}
8
doWorkAfterProfiling();
9
 
10
 
11
Sample usage with Promises:
12
 
13
dftp.profileCompleted().catch(err => console.error("Profiling failed with err: " + err)).finally(doWorkAfterProfiling);
14
 
15
 
16
doWorkAfterProfiling can be a function used to submit form data and perform the inquiry

Profiling script & page lifecycle

The profiling script must be loaded and initialized only once per page lifecycle. You can check for presence of the dftp object to avoid loading the script again. If the user makes repeated transactions without reloading the page you should keep using the same attemptReference when making an inquiry.

Sample payment page template and profiling script implementation

1
<html>
2
<head>
3
</head>
4
 
5
<body>
6
    <!-- payment form -->
7
    <form id="payment-form">
8
        <label>
9
            Name:<br>
10
            <input type="text" name="name" id="name" class="form-element">
11
        </label>
12
        <br>
13
        <label>
14
            Credit card number:<br>
15
            <input type="text" name="ccn" id="ccn" class="form-element">
16
        </label>
17
        <br>
18
        <label>
19
            Expiration date:<br>
20
            <input type="text" name="expiration" id="expiration" class="form-element">
21
        </label>
22
        <br>
23
        <label>
24
            CVV:<br>
25
            <input type="text" name="cvv" id="cvv" class="form-element">
26
        </label>
27
    </form>
28
    <!-- payment form end-->
29
 
30
    <!-- button which is used for sending data, calls dftp.profileCompleted inside sendForm wrapper-->
31
    <button id="send" onclick="sendForm()">Pay</button>
32
 
33
    <script>
34
        function validateFormAndSend(){
35
            // isValid is the merchants function used for card data validation
36
            if (isValid()) {
37
                // merchant function used for sending data to server
38
                sentPaymentData();
39
            } else {
40
                // merchant function used for displaying card data errors on the form
41
                displayValidationErrors();
42
            }
43
        }
44
 
45
        // function for handling case when script from profiler URL cannot be loaded and dftp object does not exist
46
        function sendForm() {
47
            if (window.dftp){
48
                dftp.profileCompleted().catch(err => console.error("Profiling failed with err: " + err)).finally(validateFormAndSend);
49
            }
50
            else {
51
                validateFormAndSend();
52
            }
53
        }
54
    </script>
55
 
56
    <!-- javascript inserted at the bottom of body; merchant_id may be hardcoded or inserted by backend, crossorigin="use-credentials" property is mandatory-->
57
    <script type="text/javascript" id="SCRIPT_TAG_ID" crossorigin="use-credentials" src="https://provided_name.nethone.io/s/{merchant_id}/dNfsXe.js" async></script>
58
 
59
    <!-- javascript initializing profiling -->
60
    <script>
61
      var scriptID = "SCRIPT_TAG_ID";       // ID of <script> tag where our script is being loaded
62
      var options = {
63
          attemptReference: "{attempt_reference}",   // inserted by the backend
64
          sensitiveFields: ["ccn", "cvv"];            // list of sensitive fields
65
      };
66
 
67
      if (window.dftp) {
68
          dftp.init(options);
69
      } else {
70
          var el = document.getElementById(scriptID);
71
          el.addEventListener("load", function () {
72
              dftp.init(options);
73
          });
74
      }
75
    </script>
76
 
77
</body>
78
</html>

Support

This is fully depending on the type of payment used, at the moment we have this available for:

• Credit Card

• SEPA Direct Debit

• PayPal

Sequence diagram

Pre-Auth using HPP

Paygate interface

Definitions

Data formats

Abbreviations

Calling the interface

Authorization Request

To carry out an AI Protect check via a Server-to-Server connection, please refer respective payment method Payments by Credit Card, Payments by Direct Debit, PayPal V2

The parameter attempt_reference need to be included in addition to the respective parameters of each payment type.