Kount

Our Kount™ implementation is very simple to set up and to use. We’ve created an implementation that goes through PayCertify Fraud Portal in order to add reporting features, and make the fraud checks possible to happen on the browser (our implementation is 100% JavaScript) and block fraudulent transactions from happening without even touching your system’s back end or sending data to our gateway.

Authorization

To use PayCertify’s Kount™ you will need a Fraud Portal account and your PUBLIC API KEY, which can be requested to support or by navigating on your Fraud Portal Account to Settings > Integrations > Show.

With your PUBLIC API KEY in hands, you’ll be able to start using it.

If you're having trouble finding your PUBLIC API KEY or do not have access to it yet, please reach out to support@paycertify.com.

Setting up the Rules

Kount™ has mechanisms to prevent fraud where you define statements that your business logic configures as fraud. These rules can be whenever a billing address isn’t in a specific country, or when a consumer has been doing transactions too fast, or whenever a consumer is known to be a fraudster, etc. Watch the videos below for a small overview of how Kount™ rules works.

Your browser cannot play this video.

Your browser cannot play this video.

In order to set up your Kount™ account, you mainly have two options:

Buy your own Kount MID

Operate under PayCertify’s MID

Most of our clients that want a higher level of customization / sophistication on rules set up end up with option #1, while merchants that just want to prevent common fraud pick #2. On both scenarios, you should be able to protect yourself against fraud. It’s mainly a choice of wether or not you need access to the Kount Portal to set up exclusive rules.

Setting up the Plugin

Once you have your Kount™ rules set, you should set up the plugin in your application. You should start by linking the following script into the end of the body tag on your checkout page or wherever the user is inputting credit card data:

After having the script linked into the page, you will need to add data-paycertify-kount data attribute to some inputs your checkout form so the javascript plugin will know which values to send for the fraud check:

Data Attribute

Required?

Description

Type

name

Yes

Customer’s full name

string

email

Yes

Customer’s email

string

phone

Yes

Customer’s phone on E.164 format

string

address

Yes

Customer’s full address

string

city

Yes

Billing address city

string

state

Yes

Billing address state

string

country

Yes

Billing address country

string

zip

Yes

Billing ZIP Code

string

credit_card

Yes

Credit Card number

string

amount

Yes

Transaction amount

string

Below there’s an example HTML form with all the required data attributes to be sent over to the API:

Since both success and failure functions are complex and will determine how to prevent fraud or let the transaction pass, we have two sections below, outlining how to use those and all the possibilities that you have while using them.

Success Function

The success function is triggered whenever we get a HTTP 200 status from the Fraud Portal API. That does NOT means that the success function is called whenever you’re free to allow the form to be submitted. Below we’ll explain how the success function works and outline some possibilities.

This function receives two arguments: one of them being the response itself, which contains the Kount™ response data, which will help you on the decision-making process of wether let this transaction pass to the gateway or not, and the $form variable, which is the form that contains the data-paycertify-kount attributes.

Is the device placing the order of a mobile nature (iPhone; Android; Blackberry; iPad, etc.)

MOBILE_FORWARDER

If device is mobile, is it using a forwarder to process the carrier’s service

RULES_TRIGGERED

Number of rules triggered by the RIS post

RULE_ID_X

Rule ID associated with merchant created rules. X in this case will be a number ranging from 0 to any positive integer.

RULE_DESCRIPTION_X

Rule descriptions associated with RULE_ID_X. X in this case will be a number ranging from 0 to any positive integer.

Examples

The simplest thing you can do for preventing fraud would be declining transactons that Kount recommends to decline. In order to do this, your success function could be simple as:

newPayCertify.Kount({API_KEY:'MY_PUBLIC_API_KEY',mode:'production',merchantId:'691000',success:function(response,$form){if(response.AUTO=='D'){// redirect the user to another page?// window.location.href = 'http://my.webpage.com/somewhere'// maybe display an alert to the user saying that he should try with another card?// alert('Your card was rejected. Please try with another card number.').// Or which ever logic you'd like to put in place here.}else{// let the transaction be sent to the gateway$form.submit();}},failure:function(response){console.log('failed: ',response);}});

You can also of course use which ever other variable you’d like, based on the RIS Response specified above. At this point, our Kount™ implementation is very flexible and you could create your own complex rule sets to prevent fraud based off your business constraints and internal logic.

Failure Function

The failure function is triggered whenever we get a response that isn’t successful while communicating to the Fraud Portal. You could create your own internal logic to, for example, hit a error notification system endpoint so your technical team is aware that something in regards to the communication is not working. Although, this function is used mostly for debugging purposes.

This function receives only one argument which is the response itself. Best way to inspect it is just logging it to the console and understanding what the issues are. Other than that, if you’re facing any issues while working with our Kount™ implementation, don’t hesitate to reach us at support@paycertify.com if you have any questions!