Were does the Kombatix Defense API fit into your payment and fraud stack?

The most common place is in your customer support and dispute/refund management workflow. If you are using a custom CRM or a platform that isn’t supported by direct integration yet, you can use our API to gather information from the customer record and interaction, query the Defense Product, and return the raw data back into your CRM. 

Another valuable use case is in your chargeback representment strategy. Let’s say you receive a Chargeback for a digital item where the customer claimed they did not make the purchase. You can query the Defense API to gather the input validation and friendly fraud score and include it with your representment package.

One of the most intriguing use cases we’ve come across is in your transactional fraud screening process. For example, you are using Kount, or Accertify, or Forter, or another fraud provider. YOu have a set of rules defined that works, but maybe there are a number of transactions that score below your stated thresholds that you believe could be approved. Put them in manula review, run the Kobatix Defense API and determine if the information input into your checkout form ties to the individual, and if there is possible chargeback or refund history. Use that data to possibly approve more transactions. Then, if that individual ever tries to claim friendly fraud to get a refund, you have the data proving that their input was validated and tied to their profile.

Here’s an example of the input and Basic Defense output from an out of the box API call. Slide the circle left/right to see the input and output:

Kombatix can also append the input data with additional contact data to cross reference possible spouses, secondary addresses/phone numbers, and other info to help validate the individual. Ask how you can get that data added to any of our API responses.

In beta testing, when used proplery the Kombatix Standard Defense product produced these results: