Kount are an independent, two-step fraud and risk engine, delivering centralized fraud protection that’s separate from your Payment Processors. This gives you control across all transactions, regardless of the Payment Provider.

Kount is available through BR-DGE in the following integration methods:

BR-DGE provide different ways to utilise Kount as a Fraud & Risk engine. You can opt to integrate both of these methods to your payment flows, or use the one that best suits your needs.

BR-DGE currently provide support for:

• Kount Device Data Collector 📡
• User Defined Fields ⚙️

Kount Device Data Collector 📡

What is the Kount Device Data Collector

The Kount Device Data Collector (DDC) gathers information from a customer's device by redirecting the device browser momentarily to Kount and then back to the merchant. This passive analysis conceals the Kount interaction with the customer and does not affect the customer experience.

Using the Kount DDC

BR-DGE support the use of the Kount Device Data Collector (DDC) through our API. Allowing you to run browser fingerprinting on your customers during the checkout process, after which you can pass the Kount Session ID to Kount via BR-DGE for in-depth fraud analysis.

To get started using the Kount DDC check out the following guides from Kount with steps on how to integrate the Device Data Collector, and generate your Session ID.

• Integrating the Kount DDC to your website.
• Creating a DDC Session ID.

Once you have created your Kount DDC Session ID you can pass the resulting value to BR-DGE during your Payment creation.

To use Kount to evaluate Payment Risk via BR-DGE

1. On your customers device, generate your sessionId with the Kount Device Data Collector.
2. Send the resulting sessionId to BR-DGE in yourPOST /v1/payments request as the value in riskInstruments.kount.sessionId

...
  "riskInstruments": {
    "kount": {
      "sessionId": "your-kount-session-id"
    }
},
...

3. In the response to your payment request, you can find the resulting score from Kount by reviewing the values returned in riskAssessments object

...
 "riskAssessments": {
    "kount": {
      "score": 90.1,
      "decision": "APPROVED",
      "transactionId": "KJX50N55NGJS",
      "reasonCode": "APPROVED_3DS_STEP_UP"
    }
 },
...

📘

If Kount declines your transaction BR-DGE will stop processing it and return a response code indicating that the transaction was declined.

If there is an error communicating with Kount, the decision to halt or continue the transaction processing is configurable in your Retail Channel.

Check a Payment Risk Score

To retrieve the risk score associated with a payment you can query the payment using the BR-DGE Payment Status endpoint.

The full API reference documentation for this endpoint is available in our API reference.

1. Query the result of a BR-DGE Payment ID by using the GET /v1/payments/{paymentId}/status endpoint. Passing in your BR-DGE Payment ID as the paymentId URL path parameter.
2. In the response to your Payment Status API call check the values returned in the riskAssessments.kountobject

...
  "riskAssessments": {
    "kount": {
      "score": 90.1,
      "decision": "APPROVED",
      "transactionId": "KJX50N55NGJS"
    }
  },
...

User Defined Fields ⚙️

What are User Defined Fields?

User Defined Fields (UDFs) allow you to send additional data points to Kount as part of a payment request through BR-DGE. These additional data points can be used to enhance risk decisioning.

There are two types of additional data that can be sent to Kount:

How to use User Defined Fields

Configuring User Defined Fields and Reason Codes

Before you can use UDFs and Reason Codes with Kount you must pre-configure them in the Kount portal. For a detailed overview of adding your UDFs, and reasons codes to your Kount account check out the following guide from Kount detailing the process. How to Manage User Defined Fields.

Provide your UDFs to BR-DGE

BR-DGE will use these UDFs as part of your payment processing. We require you to advise us of your UDFs so we can update your retail channel configuration to support them.

To provide us with your UDFs please contact our support team.

📘

It is your responsibility as the merchant to advise BR-DGE of any changes you make to UDFs in the Kount interface.

Send your UDFs with a Payment Request

To utilise Kount UDFs at the point of making a payment you need to send them to BR-DGE when making a payment request to the POST /v1/payments endpoint.

Sending UDFs is achieved by utilising the customMetadata object in the BR-DGE API.

This object allows you to specify key:value pairs that will be used during the Payment process to send your UDFs to Kount. For more information on using the customMetadata object when making a payment, check out our dedicate Custom Metadata guide.

The following JSON shows an example of how you might pass some Kount UDFs to BR-DGE to be used in Payment Processing.

Send your UDFs to BR-DGE in an API call to POST /v1/payments .

...
"customMetadata": {
   "account_type": "BASIC",
   "ip_address": "153.81.4.213",
   "days_since_last_purchase": "5",
   "signup_date": "2014-11-01",
   "shipping_country": "GB"
},
...

You should then expect to receive a riskAssessments object in the response to your API call.

...
{
  ...,
  "riskAssessments": {
    "kount": {
      "score": 95.9,
      "decision": "APPROVED",
      "transactionId": "A3GV0BYTVLWX",
      "reasonCode": "3DS_STEP_UP"
    }
},
...

🚧

You will not receive a reasonCode in the response if your Kount Rule does not have a Reason Code configured

Support

To get started with Kount via BR-DGE, or if you require additional support, please contact our support team .