Radial Device Fingerprint

Radial Device Fingerprint (RDF) is a Javascript application that captures information about a customer's device. This device information is used to create a virtual profile, which can then be compared against subsequent orders to help mitigate fraud.

Radial Device Fingerprint is used to identify new customers and customers returning to a site using the same devices. Along with other Radial proprietary software solutions, Radial Device Fingerprint helps detect good and fraudulent orders.

Radial Device Fingerprint is simple and straightforward to implement in checkout pages of the webstore. It uses remote deployment capabilities to collect device data and retrieve necessary information for evaluation purposes. After you add two HTML tags to your store's web pages, Radial Device Fingerprint will execute and automatically analyze, generate, and store virtual profiles for your site visitors as they go through the checkout experience on your site.

Please see the recommended privacy statement to be added to your website's Terms & Conditions/Privacy Statement section.

Implementation

Before you implement Radial Device Fingerprint, you must obtain the URL for the script. A Radial representative will provide a URL unique to your webstore.

To implement the Radial Device Fingerprint script, complete the following steps:

  1. Include the minified Javascript file in the checkout section of your webstore's pages. Replace the placeholder URL in src with your store's unique Radial-provided URL. 
    <script type="text/javascript" src="https://RADIAL_HOST/path/to/RDF/rdf.js" async defer></script>
  2. Add the following hidden field to your submit order form. 
    <input type="hidden" name="RDFUID" id="RDFUID" />

    Radial Device Fingerprint generates a unique ID value for the order and assigns it to this hidden field.

  3. When the order is submitted, capture the value of the RDFUID field. Send the RDFUID value to Radial in the Order Create API. See Order Create details below for both ROM and JDA.

    If you are not using Radial's Order Create API and are directly integrating with Risk Assessment API, then send the RDFUID value as a Custom Attribute in the Risk Assessment API. See Passing RDFUID in the Risk Assessment API, below.

    Please Note: If the script does not generate a value for RDFUID, or if the value is blank, do not pass the blank value in either Risk Assessment or Order Create.

Passing RDFUID in the Radial Order Management Order Create API

If you are using Radial Order Management, pass the value of RDFUID in the Order Create Request XML, as part of custom attributes in the Order section.

The below highlighted attribute RDFUID must be added in the order create XML with the value captured from the RDFUID field in the browser.

Copy this code sample. 
<Currency>USD</Currency>
<TaxHeader>
     <Error>false</Error>
</TaxHeader>
<Locale>en_US</Locale>
<CustomAttributes>
        <Attribute>
            <Key>RDFUID</Key>
            <Value>ff271086-3373-4e52-b898-9926de928347_1510073527122</Value>
        </Attribute>
</CustomAttributes>
<OrderHistoryUrl>http://www.abc.com/account/orderhistory.do</OrderHistoryUrl>

Sample ROM Order Create XML file with RDFUID: OMS_OrderCreate_DF_UID.xml

Passing RDFUID in the JDA Order Create API

If you are using JDA for Order Management, pass the value of RDFUID in the Order Create Request XML.

The below highlighted attribute RDFUID must be added in the order create XML with the value captured from the RDFUID field in the browser.

Copy this code sample. 
<CustomAttributes>
      <CustomAttribute>
        <Name>ORDTAXERR</Name>
        <Value>N</Value>
      </CustomAttribute>
      <CustomAttribute>
        <Name>TDFCALCID</Name>
        <Value>122125493</Value>
      </CustomAttribute>
      <CustomAttribute>
        <Name>ORDERCHANNEL</Name>
        <Value>WEB</Value>
      </CustomAttribute>
      <CustomAttribute>
        <Name>RDFUID</Name>
        <Value>00744669-e12b-4365-960e-108402212254_1493405974023</Value>
      </CustomAttribute>
</CustomAttributes>

Sample JDA Order Create XML file with RDFUID: QRST_OOMF_OrderCreate

Passing RDFUID in the Risk Assessment API

If you are not using Radial's Order Create API and are directly integrating with Risk Assessment API, then send the RDFUID value as a Custom Attribute in the Risk Assessment Request XML.

The below highlighted custom property DF_UID must be added in the GSI_CUSTOM group with the value captured from the RDFUID field in the browser.

Copy this code sample. 
<CustomProperties>
      <CustomPropertyGroup Name="GSI_CUSTOM">
         <CustomProperty Name="BABY_REGISTRY_IND">
            <StringValue>N</StringValue>
         </CustomProperty>
         <CustomProperty Name="PAYPAL_PAYER_COUNTRY">
            <StringValue>US</StringValue>
         </CustomProperty>
         <CustomProperty Name="GIFT_REGISTRY_IND">
            <StringValue>N</StringValue>
         </CustomProperty>
         <CustomProperty Name="ORIG_SOURCE">
            <StringValue>Web</StringValue>
         </CustomProperty>
         <CustomProperty Name="PROXY_ORDER">
            <StringValue>N</StringValue>
         </CustomProperty>
         <CustomProperty Name="PP_SLR_PRT">
            <StringValue>Eligible</StringValue>
         </CustomProperty>
         <CustomProperty Name="RDFUID">
            <StringValue>00744669-e12b-4365-960e-108402212254_1493405974023</StringValue>
         </CustomProperty>
      </CustomPropertyGroup>
</CustomProperties>

Sample Risk Assessment XML file with DF_UID custom property: RiskAssessmentWithDFUID.xml

Passing RDFUID in the Order Feed File

If you using Radial's Order Feed File for submitting the orders, then send the RDFUID value by replacing the current value being sent in DeviceID with the RDFUID value.

The element highlighted in the order XML below, DeviceID, must be updated with this new value for RDFUID. The old value does not need to be sent.

Copy this code sample. 
<DeviceID>80bb65b9-4f59-4a0c-880c-3a3c10632431_1525979597399</DeviceID>
<BrowserID>Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.1
39 Safari/537.36</BrowserID>
      <BrowserSessionID>684716325-b588434cf08f157db2320939ab4c04efc199908582c8eeb3f95b921c169bb2c4</BrowserSessionI
D>
      <BrowserConnection>TE, keep-alive</BrowserConnection>
      <BrowserAccept>text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8</Browser
Accept>
      <BrowserAcceptEncoding>gzip</BrowserAcceptEncoding>
      <BrowserAcceptCharset></BrowserAcceptCharset>
      <BrowserIdLanguageCode>en-US,en;q=0.9,sv;q=0.8</BrowserIdLanguageCode>
      <RawCookie></RawCookie>
      <BrowserCookie>SESSION=684716325-b588434cf08f157db2320939ab4c04efc199908582c8eeb3f95b921c169bb2c4</BrowserCoo
kie>
      <BrowserReferer>https://www.maccosmetics.com/checkout/index.tmpl</BrowserReferer>
      <CustomerIPAddress>104.137.133.87</CustomerIPAddress>

Verification

Place some test orders using the URL provided and share the order numbers with the Radial representative so that data can be verified for different order scenarios.

For each order placed and tested, please make sure that RDFUID is captured.

Some of the order scenarios to be tested are listed below:

  • Order with a credit card as payment method
  • Order with PayPal or PayPal Express as payment method (if applicable)
  • Order with Apple Pay as payment method (if applicable)

Production Deployment

After verification of some test orders, Radial will provide the production URL to use for live orders in your production environment.

Note: The test environment URL for Radial Device Fingerprint is different from the production URL. Do not use the test URL in production or use the production URL in a test environment.