The Microsoft Dynamics 365 Fraud Protection sample merchant application demonstrates how to call the Dynamics 365 Fraud Protection APIs. It happens to be in the context of an online merchant who sells clothing and other goods. This sample may be useful if you are integrating with the Dynamics 365 Fraud Protection APIs, or if you want to see how to integrate new API endpoints/features when there are new API versions.

Follow the guide to configure this sample application and run it.

• Requesting a Dynamics 365 Fraud Protection risk recommendation for purchases and using the recommendation to decide whether to charge the customer.
• Requesting a Dynamics 365 Fraud Protection risk recommendation for account sign ups and using the recommendation to decide whether to allow the customer to register for an account.
• Managing users and their associated information in the Dynamics 365 Fraud Protection system (for example, basic info, payment methods, addresses, and so on).
• Reporting chargebacks, refunds, and additional fraud signals.

The solution in the root of the repo shows how to call the APIs using .NET Core outside the context of any particular eCommerce platform. It's meant to be a reference implementation for companies with their own software.

This repo also has examples showing how to integrate Dynamics 365 Fraud Protection in common eCommerce platforms:

• Adobe Magento v1.9x

There are two main sections to the sample application:

• API documentation explaining how to authenticate with and call the APIs. Plus, API usage guidance is given for various scenarios like guest checkout.
• Sample application that you can learn from and run yourself.

Much of the code is based on the eShopOnWeb application.

In addition to this API documentation, you can read the complimentary product documentation for Dynamics 365 Fraud Protection. It covers the broad set of Dynamics 365 Fraud Protection features such as the rules engine, reporting, and customer support. It also contains release notes and highlights planned, upcoming features.

Once properly configured, this sample site uses Microsoft device fingerprinting to send device telemetry to Microsoft for the purposes of demonstrating Dynamics 365 Fraud Protection. To disable device fingerprinting, remove code related to it rather than configuring it.

For additional information, see the Microsoft Open Source Code of Conduct.