Skip to main content
On this page

Kount: AI-Driven Identity Trust & Fraud Prevention#

Kount, an Equifax company, is an industry leader in digital identity trust. Powered by their Identity Trust Global Network, Kount analyzes billions of data points across global interactions to determine the exact level of trust for every identity behind a transaction. It is highly trusted by global enterprises for its ability to stop fraud while simultaneously driving top-line revenue.

Capabilities:

  • Identity Trust Global Network: A massive consortium of data that links billions of interactions, devices, and identifiers to accurately assess the risk of the person behind the screen.
  • Omniscore AI: Kount’s proprietary machine learning algorithm that calculates a highly accurate transaction safety score in milliseconds.
  • Account Takeover (ATO) Protection: Monitors login behavior and device changes to stop bad actors from hijacking legitimate customer accounts.
  • Friendly Fraud Management: Provides tools and data insights specifically designed to help merchants win chargeback disputes and stop first-party fraud.

How It Works With Our Orchestration Engine: Kount’s Omniscore returns a distinct letter decision (Approve, Review, Decline) and a numerical value. Our orchestration layer ingests this response and normalizes it into our standard routing parameters. You can easily map "Approve" to Low Risk (direct Adyen routing), "Review" to Medium Risk (triggering manual review and/or 3DS authentication), and "Decline" to High Risk (blocking the transaction), allowing you to automate complex identity trust strategies with a few clicks.

Risk Tiers

The table below outline how the raw responses and risk scores from each supported provider are mapped to these standardized levels, along with the default routing actions triggered by each tier. Keep in mind that while these represent our standard configurations, you have full control to customize what triggers each risk level to perfectly align with your business's unique risk appetite.

Kount's Omniscore returns an automated decision Approve, Review, or Decline alongside a numerical score.

Provider's Raw Response (Example)Our Standardized Risk LevelDefault Routing Strategy
Decision: Approve🟢 LOW RISKProcess directly via preferred gateway (e.g., Adyen)
Decision: Review🟡 MEDIUM RISKStep-up authentication: Approve the transactions and wait for a manual review and/or Trigger 3D Secure (3DS)
Decision: Decline🔴 HIGH RISKDeny transaction OR Route to specialized high-risk gateway


Requirements

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

  • Admin:

    • Private Key
    • Account ID
  • Environment:

    • test for sandbox 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 your Kount dashboard to review your API Keys:
  2. ClickAdmin in the left panel.
  3. Click Product Configuration.
  1. Click API Keys and +Generate API Key.
  2. Copy the API Key that will be used when creating the connection in Deuna

2. Configure webhooks

Configure the webhooks:

  1. Go to Product Configuration Webhooks.

  2. Click Select New Webhook.

  1. Click Order Status Change in Event Type. In Channel, it is not necessary to fill “123456”
  2. In URL, paste the following URLs depending on the environment where your Kount account will be used:
  3. Click Enter to finish.

3. Create rules

Create rules for approve, deny, and manual review:

  1. Go to Policy Management on the left panel.

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

  3. Click +Create New Set.

  4. Name the set as “email”.

  5. Add a description.

  6. Click Save.

  1. Once saved, find the Set created and in “Set Actions” select “Activate Set”.
  1. Now select Edit, then select the “Policies” tab and then “New Policy” to start creating email rules:
  1. 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

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

  1. Proceed to select “equals” from the dropdown, and in the text box write “reject@deuna.com” and select the “Save” button switch is above the “outcome” dropdown.
  1. Now you may repeat the same steps from “New Policy” to create“Review Always” policy to send the transactions to manual review.

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

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

  4. Proceed to select “equals” from the dropdown, and in the text box write “review@deuna.com” and select the “Save” button switch is above the “outcome” dropdown.

  1. You should see your policies like this
  1. Finally, go back and ensure that the “email” set shows as activated in the “Decisioning” tab under Police Management

4. Set up the DEUNA sandbox environment

  1. Access the DEUNA Admin and enable Test mode.
  2. In Connections, configure Kount with the test credentials and the test environment.
  3. If you use manual review, ask your DEUNA Technical Account Manager to enable manual review, automatic operation execution, and order follow-up for the store.
Interactive exampleUses sample data and does not make API requests.
Production
Payments

Connections

Discover and manage payment, wallet, and anti-fraud integrations.

Acme LATAM · Production
5 sample connectionsUpdated just now
ConnectionsTypeStatusAction
AdyenPayment gatewayConnected
WorldpayPayment gatewayConnected
PayPalPayment methodConnected
Mercado PagoPayment methodNot connected
RiskifiedAnti-fraud engineNot connected
  1. Configure a test payment gateway and add Kount to a payment strategy. Kount can run before the payment provider (pre-authorization) or after it (post-authorization).
  2. Configure medium-risk handling when the merchant uses manual review, then activate the strategy.
Interactive exampleUses sample data and does not make API requests.
Production
Payments

Payment strategies

Configure default processing and rules for each payment flow.

Acme LATAM · Production

Default processing

Configure default processing and rules for each payment flow.

RuleRoutingStatusAction
Default processingAdyen → WorldpayActive

Specific rules

Configure default processing and rules for each payment flow.

1 sample rulePayment processors
PriorityRuleConditionsRoutingStatus
1High-value ordersAmount over USD 100Adyen → WorldpayActive

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”

Example

JSON
KOUNT: {
		"clientId":"781660013918393", // CREDENTIAL PROVIDED BY KOUNT
		"environment":"TEST", // TEST OR PROD
		"isSinglePageApp":false 
	    }

Deuna device fingerprinting SDK generates as output a base64.

6. Test the integration

Make the following transactions with their respective emails:

ResultFieldValueField in the Request to Deuna
Approveemailany
Denyemailreject@deuna.combilling_address.email = reject@deuna.com
Reviewemailreview@deuna.combilling_address.email = review@deuna.com

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, open the transactions in the Admin and confirm that the fraud result is Approved, Denied, or Manual review, together with the payment status and operation history.

Interactive exampleUses sample data and does not make API requests.
Production
Payments

Orders

Find a payment, then open its operational context.

Acme LATAM · Production
4 sample ordersUpdated just now
Order IDCreatedCustomerProcessorAmountStatus
Oct 1, 14:32sofia@example.comWorldpay$128.40Approved
Oct 1, 14:18diego@example.comAdyen$82.00Pending
Oct 1, 13:54ana@example.comStripe$246.90Declined
Oct 1, 13:41marco@example.comWorldpay$54.25Approved

7. Deploy Kount to Production

Set up the production environment:

  1. Kount:

    1. Get access to Production Dashboard in Production: Ask Kount for the required credentials
    2. Login into https://app.kount.com/login/ to configure the account
  2. In the DEUNA Admin configure the merchant for Production

    1. Unselect Test Mode
    2. Configure Kount as an anti-fraud provider using Production credentials, setting live as Environment
    3. Configure the payment gateways and establish a Payment Strategy.