Kount

Integrate Kount in DEUNA

Get started with Kount

Requirements

The following information must be at hand before starting configuring the different environments

• Admin:

  • Private Key
  • Account ID

• Environment:

  • test for sanbdox environment
  • live for production environment
  

Integrate Kount

Integrate Kount as an anti-fraud provider in DEUNA.

1. Set up the sandbox environment in Kount

1. Access to Kount dashboard https://app-sandbox.kount.com/login/
2. Review your API Keys

   1. Select Admin in the left panel and then Product Configuration

      

   2. Select API Keys, and then +Generate API Key

      

   3. Copy the API Key that will be used when creating the conection in Deuna

2. Configure webhooks

Configure the webhooks:

1. Under Product Configuration Webhooks and then select New Webhook

   

2. In Event Type select “Order Status Change”

3. Channel is not necessary to fill “123456”

4. In URL paste the fowllowing URLs depending on the Deuna’s environment where this Kount’ account will be used:

   • https://api.stg.deuna.io/post-transactions/kount in the textbox if the tests will be done in Deuna’s Staging Environment
   • https://api.sandbox.deuna.io/post-transactions/kount in the textbox if the tests will be done in Deuna’s Sandbox Environment
   • https://api.deuna.io/post-transactions/kount in the textbox if the tests will be done in Deuna’s Production Environment

5. Select “Enter”

   

3. Create rules

Create rules for approve, deny, and manual review:

1. Select Policy Management on the left panel

2. In the “Decisioning” tab select “Payments Fraud” in the Event dropdown

3. Select “+Create New Set” and name it as “email” , add a description and select Save

   

4. Once saved, find the Set created and in “Set Actions” select “Activate Set”

   

5. Now select “Edit”, then select the “Policies” tab and then “New Policy” to start creating email rules:

   

6. Start creating the policy to deny always the transaction, in Policy Name write “Deny Always”, in Description “Always deny by billing email”, and in outcome select “Decline” from the Dropdown

7. Now select “Add contition” from the “Policy conditions” tab, and in search conditions write “billing email”, select it from the results, and then “Confirm”

   

8. Proceed to select “equals” from the dropdown, and in the text box write “[email protected]” and select the “Save” button wich is above the “outcome” dropdown.

   

9. Now you may repeat the same steps from “New Policy” to create“Review Always” policy to send the transactions to manual review.

10. In Policy Name write “Review Always”, in Description “Always Review by billing email”, and select “Review” from the “Outcome” dropdown.

11. Then select add conditions, find billing email, and select “confirm”

12. Proceed to select “equals” from the dropdown, and in the text box write “[email protected]” and select the “Save” button wich is above the “outcome” dropdown.

    

13. You should see your policies like this

    

14. Finally, go back and ensure that the “email” set shows as activated in the “Decisioning” tab under Police Management

    

4. Setting up Sandbox Environment in Deuna

1. Access to https://admin.deuna.com/home:

2. Select Test Mode

   

3. If manual review is going to be used with Kout, go to Settings, find Merchant, and under “Payment settings” tab select “Enable Manual Review”, “Enable Automatic Operations Execution”, and “Order Follow-up”.

   

4. Configure Kount as antifraud provider using testing credentials, and setting test as Environment

5. Configure a testing payment gateway and establish a Payment Strategy. It is critical to process Medium Risk if manual review will be used for the merchant. It can be configured either Pre authorization (before the PSP) or Post Authorization (after the PSP)

   1. Pre Authorization

      

   2. Post Authorization

      

5. Configure device fingerprinting

1. To configure device fingerprinting for Kount, follow this guide

2. The parameters to configure are the following:

   1. dataCollectorUrl: fixed value tst.kaptcha.com
   2. merchantId: The merchant ID in the desired environment in Deuna (to be Provided by your Deuna Advisor)
   3. clientId: It is provided by Kount, most probably the same as the API credentials
   4. environment: ''TEST” for Sandbox, and “PROD” for Production
   5. isSinglePageApp: fixed value “false” unless Kount advises to use “True”

3. Example

   JSON

   KOUNT: {
   		"dataCollectorUrl":"tst.kaptcha.com", // fixed
   		"merchantId":"11bf255f-128a-42ae-9cea-5cc81399d97", // merchantID Deuna
   		"clientId":"781660013918393", // CREDENTIAL PROVIDED BY KOUNT
   		"environment":"TEST", // TEST OR PROD
   		"isSinglePageApp":false 
   	    } 

4. Deuna device fingerprinting SDK generates as output a base64, how to use it is as well described in the provided link in the point 1.

6. Test the integration

Make the following transactions with their respective emails:

In Manual Review you can approve or deny the transactions manually in Kount’s dashboard. When selecting the transaction in the Event Analysis section, and “Approve” or “Decline”.

The manual decision will take around one minute to be reflected in Deuna

Finally, review the transactions in the Admin, in the Fraud section should appear the following values: Approved, Denied, or Manual Review

7. Deploy Kount to Production

Set up the production environment:

1. Unselect Test Mode

   

2. Configure Kount as anti-fraud provider using testing credentials, setting live as Environment.

3. Configure the payment gateways and establish a Payment Strategy. Don’t forget that It is critical to process Medium Risk if manual review will be used for the merchant.