Fingerprint
About
For all transactions placed by the customer, a device fingerprint is required and is collected with the /fingerprint API request.
The information we gather with /fingerprint allows us to form a complete picture of the consumer and helps us to distinguish fraudulent behaviour from normal customer behaviour.
Unlike the rest of the Reach API Requests, /fingerprint needs to be loaded on the page in <script>
tags so that a pixel can be present on the front-end for our fraud system to hit and gather information about the customer's system.
Sample Request
<script async="" src="https://checkout.rch.how/v2.22/fingerprint?MerchantId={SANDBOX MERCHANT ID}"></script>
<script async="" src="https://checkout.rch.io/v2.22/fingerprint?MerchantId={PROD MERCHANT ID}"></script>
Websites using Content-Security-Policy may need to include the following rules to use our fingerprint mechanism:
script-src https://checkout.rch.how/;
frame-src https://checkout.rch.how/ https://tst.kaptcha.com/
script-src https://checkout.gointerpay.net/;
frame-src https://checkout.gointerpay.net/ https://ssl.kaptcha.com/
Sample Response
var gip_device_fingerprint='83a669ce-c369-4bc8-be39-ec5519528628';
var d=document;
var b=d.getElementsByTagName('body')[0];
var e=d.getElementById('gip_fingerprint');
if(e){e.parentNode.remove();}
(function(){
var div=d.createElement('div');
div.style.display="none";
div.innerHTML=`
<iframe
id="gip_fingerprint"
src="https://checkout.rch.how/pixel/e6545955-938c-4f8d-8bb6-80b239bb9711/83c669ce-c369-4bc8-be39-ec5599528628.htm">
<img src="https://checkout.rch.how/pixel/e6545955-938c-4f8d-8bd6-80b139bb9711/83c666ce-c369-4bc8-be39-ec5598518628.gif"/>
</iframe>`;
b.appendChild(div);
})();
Using the Device Fingerprint in checkout requests
The above /fingerprint response will include a gip_device_fingerprint
GUID. This value must be sent along with all customer initiated transactions in the DeviceFingerprint
parameter for /checkout and /openContract requests.
Updated 8 months ago