Our Fraud Prevention Suite is a set of tools that will help you both preventing fraud, and actually fighting eventual chargebacks or alerts. We also provide a huge set of data from multiple social, public records and databases to help you on the decision making process of wether you should block a transaction from happening or not.


To use the insurance APIs you will need an API Token, which can be requested to support or navigating on your account to Users > Details > Api Token.

With that token, you’ll be able to access our API. You should send your key in every request to our API, in order to authenticate and identify yourself. For every request, you should pass the Authorization HTTP Header containing your token, prefixed by “Bearer “ string. Example below:


List All Transactions

This endpoint retrives all transactions that went through the fraud portal with the filters listed below.

HTTP Request


URL Parameters

Parameter Required Description Type
start_date No start date on MM/DD/YYYY format string
end_date No end date on MM/DD/YYYY format string
status No Comma separated statuses. Can be unconfirmed, confirmed, cannot_confirm or not_applicable. string
gateways No Comma separated gateways. Can be paycertify, authnet, nmi, stripe, paypal or any of the supported gateways. string

Sample request

curl --include \
     --request GET \
     --header "Content-Type: application/json" \
     --data-binary "
       \"start_date\": \"07/01/2017\",
       \"end_date\": \"07/15/2017\"
     }" \

The above command returns JSON structured like this:

            "full_name":"John Doe"
            "full_name":"José Silva"

Create a Transaction

Whenever you’re creating a transaction under the Fraud Portal, that means we will be fetching data from your customer from different social sources, public records and databases and Kount™ and generating a Fraud Propensity Score, which will help you on the decision making process of wether or not you should allow that transaction from happening. You can also opt into sending a confirmation to your customer which will help us gathering Geolocation and Network data for an eventual chargeback dispute. For more information, schedule a meeting with our team through email

HTTP Request


Query Parameters

Parameter Required? Description Type
transaction_id Yes Transaction unique identifier. Usually the transaction ID on your system. string
cc_last_four_digits Yes Last four digits of credit card string
name Yes Consumer full name string
amount Yes Total amount for the transaction. Decimals should be separated by ., not , string
currency Yes ISO 4217 currency code string
payment_gateway_cd Yes Payment gateway identifier. Can be paycertify, authnet, nmi, stripe, paypal or any of the supported gateways. string
email Depends Consumer email. Required when no phone. string
phone Depends Consumer mobile phone number. Required when no email. string
transaction_date No Transaction date in UTC time. Format: YYYY-MM-DD HH:ii:ss. If not provided, we’ll use the current timestamp. datetime
order_description No Description of the product being bought. string
card_type No Credit card brand string
name_on_card No Cardholder name string
cc_first_six_digits No Credit card bin number (first six digits) string
card_expiration_date No Credit card expiration date formatted as MMYY string
address No Consumer billing address string
city No Consumer billing city string
zip No Consumer billing zip code string
state No Consumer billing state string
country No Consumer billing country string
confirmation_type No Type of transaction confirmation. Can be ecommerce or default. Ecommerce is one click confirmation, default sends a confirmation page (MOTO) string
thank_you_page_url No The URL which user will be redirected after the confirmation. string
metadata No Any additional metadata you’d like to send and show on the receipts. json
curl --include \
     --request POST \
     --header "Content-Type: application/json" \
     --data-binary "
       \"transaction_id\": \"MY_TRANSACTION_ID\",
       \"cc_last_four_digits\": \"1234\",
       \"name\": \"John Doe\",
       \"phone\": \"+1-202-555-0143\",
       \"amount\": \"1.23\",
       \"currency\": \"USD\",
       \"payment_gateway_cd\": \"paycertify\",
       \"confirmation_type\": \"default\"
     }" \

The above command returns JSON structured like this:

  "success": true,
  "created_at": "2017-07-16T21:18:11.314Z",
  "transaction_id": "MyTransactionId123",
  "updated_at": "2017-07-16T21:18:11.314Z",
  "id": "1c20c8eea3ac11e7abc4cec278b6b50a",
  "amount": "1.23",
  "cc_last_four_digits": "1234",
  "consumer_id": "ff715f48a56844b4be9e9897f4d8cc99",
  "currency": "USD",
  "email": "",
  "name": "John Doe",
  "order_description": "Professional Services (Not Elsewhere Defined)",
  "payment_gateway_cd": "PayCertify",
  "phone": "+1-202-555-0143",
  "sent_for_manual_review_at": null,
  "status_cd": "Unconfirmed",
  "transaction_date": "2017-07-16T21:18:11.270Z",
  "verification_token": "c58d2057919748e4b4122d933169ab73"

Fraud Data Postback

Under your Fraud Portal account settings, you can define a postback URL to receive fraud data as a POST to perform any sort of automated rules that your business logic requires. These postbacks happen whenever a new transaction is created through the API.

Postback Response Format

Coming soon.