Braintree's Basic Fraud Tools and Fraud Protection have been designed to help the majority of our merchants deter fraud while still allowing legitimate transactions to process. However, some merchants may wish to have greater control over their fraud checks. Our Kount Custom integration offers a solution to that need.


While significant investment is required to manage a Kount Custom integration, there are also significant benefits, including:

  • Tailoring your rules to suit your unique business model
  • Making your rules as aggressive or lenient as you need them to be
  • Getting assistance with your rules from experts at Kount
  • Leveraging the ability to review transactions and decide what course of action to take
  • Denylisting or allowlisting customers (e.g. by IP or email address)


If you’re interested in pursuing this, contact us to discuss pricing and qualifications. Your development team can get a head start by looking over our developer docs.

Requirements and considerations

You will need to establish and use your own fraud rules with Kount Custom. Compared to using Fraud Protection, managing your own fraud detection requires a greater investment of both resources and finances. Some specific requirements to be aware of:

  • You must be processing at least 2500 transactions per month
  • There are additional fees associated with Kount Custom
  • You will still need to implement our Advanced Fraud Management Tools
  • Your team will need to conduct thorough data analysis to monitor and establish specific fraud rules for your company

Direct management of your fraud queue means that you manage it in its entirety, with assistance from Kount. Their team of experts can help you understand and identify the rules necessary to optimize your protection, as well as provide ongoing support. To get the most out of your investment, you may want to dedicate an individual or a team to monitoring your rules and ensuring they continue to work as intended.


First, you’ll work with our Customer Success team to determine whether or not it’s a good fit for your needs. If it is, we'll pass you to a Kount Account Manager who will get you set up on their end.

Be sure to check our developer docs for Kount Custom to determine if you'll need to make changes to your code, as well.

Braintree and Kount interaction

It’s important to understand how Braintree and Kount communicate – and how they don’t.

When you create a new transaction, we’ll send the information to Kount and allow a small window of time for Kount to provide their risk decision. Depending on the final decision from Kount, Braintree will either send the transaction to the processor or reject the transaction.


Once the window of communication between Kount and Braintree closes, Braintree considers the risk decision finalized and will not re-evaluate the transaction for risk. However, Kount can continue to evaluate transactions beyond that window, which can sometimes cause discrepancies in risk decisions between Braintree and Kount. See more details below.

Risk decisions

The rules you set within your Kount Custom account influence Kount’s risk decisions. These decisions ultimately determine how Braintree will handle each transaction.

Kount risk decision Braintree action
Approve Always sends to the processor
Decline Always gateway rejected
Review Always sends to the processor
Escalate* Always sends to the processor
Not Evaluated Sends to the processor by default

*The Escalate risk decision is treated the same as the Review decision in the Braintree gateway, so while you may see the Escalate decision in your Kount Agent Web Console, it will be reflected as the Review decision in the gateway.

While Braintree's action for each decision can't be changed, you can influence the decisions that Kount makes for certain transactions by using Kount rules and user defined fields. Your Kount Account Manager can help you determine what rules are best for your business – contact them for guidance.

Not Evaluated transactions

A transaction will receive a Not Evaluated risk decision when:

  • Kount takes too long to deliver a risk decision and the transaction times out
  • An error occurs during the evaluation process

You can choose to gateway reject all transactions that are Not Evaluated due to a timeout. Contact us to configure this setting.

Risk decision discrepancies

Because Kount may continue to evaluate each transaction after the window of communication with Braintree has closed, the same transaction may have a different risk decision on the Braintree side versus the Kount side.

If we don't receive a risk decision back from Kount before the window of communication closes, we will list the transaction as Not Evaluated in the Braintree gateway. Kount will continue to evaluate the transaction and will display their final decision in your Kount Agent Web Console. Because we do not re-open communication for risk decisions, the transaction will remain listed as Not Evaluated even after Kount has made a decision.

User defined fields

If you’re looking for extra security and reporting, you can create user defined fields (UDFs) in Kount and pass corresponding custom fields to Kount along with your transactions. These UDFs can be used in conjunction with your Kount rules to monitor high risk transactions.

UDFs must have a corresponding custom field in the gateway, or they will not work properly. When setting up your UDF, make sure to:

  1. Create a UDF in your Kount Agent Web Console
  2. Create a custom field via the Braintree Control Panel
    • Check the Store and Pass Back option and give the custom field the exact same name as the UDF, but with one of the following fraud prefixes:
      • For text fields, prefix the field name with fraud_
      • For numeric fields, prefix the field name with fraud_numeric_
      • For date fields, prefix the field name with fraud_date_ (note: date UDFs must be formatted MM/DD/YYYY, and dates including timestamps are not supported)

For example, if you create the UDF product_type in Kount, the corresponding custom field in the gateway must read fraud_product_type. For assistance with UDFs, contact your Kount Account Manager.


If you’ve processed a transaction and can’t find it in Kount, it’s likely that either there is a UDF that doesn’t have a corresponding custom field in your Braintree gateway, or your corresponding custom field does not have the correct fraud prefix. Make sure your UDFs always have a corresponding custom field in the gateway. If you're unable to resolve this issue, contact your Kount Account Manager for help.

Payment method UDFs

You may also notice 2 UDFs automatically passed along by Braintree for certain payment methods.

Name Description Values
PAYMENT_DISPLAY_NAME A field that represents the payment method the user transacted with. Apple Pay Card, Credit Card, Google Pay, Masterpass Card, Samsung Pay Card, Visa Checkout Card
NETWORK_TOKENIZED Indicates whether the payment method was network tokenized as a DPAN. 1 = TRUE, 0 = FALSE

Getting help

Contact your Kount Account Manager for questions on:

  • Transaction scores
  • Fraud rules
  • Reporting in Kount
  • Your Kount Agent Web Console
  • Creating UDFs

Contact Braintree for questions on:

  • Device data issues
  • Creating custom fields to map to Kount’s UDFs
  • Any integration issues