Getting Started

Heads Up: If you plan on using 3D Secure (3DS), it's recommended that you begin with that step here: 3D Secure (3DS). Once finished, return here and follow the steps below to get your fraud detection setup properly with 3DS.

Basic Setup

Begin by following these steps to set up fraud detection for your eCommerce store.

1. Getting Started Create a new store by clicking on the Store Menu option on the left, followed by the "New Store" Icon on the right.

1. Store Creation Fill out the following fields: Store name, Allowed Domains (you can select the + Domain below to add additional ones you want to use on this store if necessary), rulesets and 3DS configuration. Need information on 3DS? Please go here -> 3D Secure (3DS) Need information on setting up Rules and Rulesets? Please go here -> Rule Management

1. Retrieve API Keys Once your store is created, click on the 3 dots under "Actions". Inside this sub menu, click on "View API Keys". You'll see a popup that shows your "Public Key" and "Private Key". Copy these down as you'll need them later.

1. Script Placement Add the following script to your landing page or checkout page footer. Replace "PUBLICKEY" with the Public API Key from your store that you notated from the popup above.

<script src="https://cdn.tripleverify.com/radar.min.js?storekey=PUBLICKEY" defer></script>

Tip: If you setup a custom tracking domain, this tracking script could change from cdn.tripleverify.com to your custom tracking domain.

1. Required Data Attributes The following attributes are required and must be added to your checkout form elements. The below is a list of the attributes and their description.

Data Attribute	Description	Require
data-radar-first-name	Customer's first name	Required*
data-radar-last-name	Customer's last name	Required*
data-radar-email	Customer's email address	Required*
data-radar-phone	Customer's phone number	Required*
data-radar-pan	Credit card number	Required*
data-radar-expiration	Card expiration (MM/YY format)	Required*
data-radar-expiration-month	Card expiration month (MM)	Required*
data-radar-expiration-year	Card expiration year (YY)	Required*

Either use single expiration field or separate month/year fields. In other words, use data-radar-expiration OR data-radar-expiration-month WITH data-radar-expiration-year.

1. Recommended Data Attributes These attributes improve fraud detection accuracy. While they all say recommended, it is smart to at least have the billing or shipping fields at minimum..

Billing Information

Data Attribute	Description	Status
data-radar-billing-address	Billing street address	Recommended
data-radar-billing-address2	Billing address line 2 (apt, suite, etc.)	Recommended
data-radar-billing-city	Billing city	Recommended
data-radar-billing-state	Billing state/province (2-letter code)	Recommended
data-radar-billing-zip-code	Billing postal/ZIP code	Recommended
data-radar-billing-country	Billing country (2-letter ISO code)	Recommended

Shipping Information

UTM Parameters

Affiliate Data

1. Form Submission Setup Time to capture and verify information. While we automatically capture the form data, there may be instances when this doesn't work as expected. So it's a good idea to always manually capture the fields. Before your form submission, add the following block of code.

// Add this before your form submission
if (typeof radar !== 'undefined') {
    radar.setTotalAmount(TOTAL); /* This is only required if you are using 
    radar.capture();                min/max thresholds for declines in your rules */
}

If you are setting up 3DS, please add the following code block instead. Replace "TOTAL" with the total amount of the transaction (as an integer) so that 3DS can be processed properly.

if (typeof radar !== 'undefined') {
    radar.setTotalAmount(TOTAL); /* This is required for 3DS. Do not omit this. */
    radar.capture(submitOrder);  /* submitOrder is your order processing function */
                                    
}

1. Add Hidden Input Add the following hidden input somewhere inside your form.

<input type="hidden" name="radar_id">

1. Request Score On your backend setup, request the score after form submission. Please ensure the $privateKey variable is set to the private key you copied in step #3.

$radar = !empty($data['radar_id']) ? 
    @file_get_contents("https://score.tripleverify.com/request?session_id={$radar_id}&private_key={$privatekey}") : '';

1. Interpreting Score Thresholds