Braintree's Basic Fraud Tools and Kount Standard have been designed to help the majority of our merchants deter credit card 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
- Blacklisting or whitelisting customers (e.g. by IP or email address)
You can either establish and use your own fraud rules with Kount Custom or Braintree's rules through Kount Standard, but not both. Compared to using Braintree's fraud rules, 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 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 Accounts 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.
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.
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|
|Approved||Always sends to the processor|
|Declined||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.
**You can force Not Evaluated transactions to be gateway rejected, if you prefer – contact our Support team to configure these settings.
While Braintree's action for each decision cannot 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.
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.
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:
- Create a UDF in your Kount Agent Web Console
- Create a custom field via the Braintree Control Panel with the exact same name as the UDF, but include one of the following fraud prefixes:
- For text fields, prefix the field name with
- For numeric fields, prefix the field name with
- 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.
Emailage is a Kount fraud prevention tool that assesses risk based on the email address your customer provides with a new transaction. When you submit an Emailage request for a transaction, Kount will evaluate the provided email address to determine the validity of your potential customer. For more information about Emailage pricing or procedures, contact our Accounts team.
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
Still have questions?
If you can’t find an answer, contact our Support team.