Implement device fingerprinting
As one of its most powerful features, Microsoft Dynamics 365 Fraud Protection provides device fingerprinting that is based on artificial intelligence (AI). This feature enables the service to identifcation devices (computer, Xbox, tablet, etc.) across multiple sessions or interactions that engage with your business and others' in the fraud network. Additionally, this feature allows the service to link seemingly unreltated events to each other in the fraud network to identity patterns of fraud. Device fingerprinting runs on Microsoft Azure. It is cloud-scalable, reliable, and provides enterprise-grade security.
By tracking elements that are related to a device (computer, Xbox, tablet, and so on), you can link individual devices to events. Therefore, device fingerprinting lets you link seemingly unrelated events to each other by capturing and identifying unique device characteristics during the processes for adding a payment instrument, sign-in, and checkout.
The process of integrating device fingerprinting for Dynamics 365 Fraud Protection consists of the following tasks:
- Set up Microsoft Azure DNS.
- Integrate device fingerprinting with your website.
Set up Azure DNS
Select a subdomain under your root domain. (For example, select f.contoso.com. Any prefix can be used.)
For the selected subdomain, create a canonical name (CNAME) that points to
- Merchant website:
- DNS record:
f.contoso.com, which points to
- Merchant website:
For back-end onboarding, generate the Secure Sockets Layer (SSL) certificate for the selected subdomain.
To start the process of exchanging SSL certificates, contact DFPHelp@microsoft.com.
Integrate device fingerprinting with your website
Your web application should serve the device fingerprinting before it submits a transaction (such as a transaction for adding a payment instrument, sign-in, or checkout). Follow these steps to integrate device fingerprinting with your website.
Insert a script element on the webpages where you will profile your user's devices.
- Your_Root_Domain – The root domain of the merchant website.
- session_id – The unique session identifier of the device created by the merchant. It can be up to 128 characters long and can contain only the following characters: uppercase and lowercase Roman letters, digits, underscore characters, and hyphens (a–z, A–Z, 0–9, _, -). Although we recommend that a globally unique identifier (GUID) be used for the session ID, this approach isn't required.
- instance_id – A placeholder for the instance ID that represents you. Use the instance identifier (instance_id value) listed on the Account Information dashboard tile in the Dynamics 365 Fraud Protection Evaluate experience. You must have this value to integrate device fingerprinting with your website.
Here is an example of a response for mdt.js.
Load device fingerprinting after the page's elements are loaded.
When you submit transactions in the Dynamics 365 Fraud Protection API, complete the following actions:
- In the deviceContextId field, set a session ID.
- In the deviceContextDC field on the deviceContext object, set the window.dfp.dc variable from mdt.js response.