A way to write rules without using FQL
Many fraud managers and other user roles that can write rules do not necessarily have a dev background and may find writing any amount of code very daunting, no matter how simple the coding language is deemed by engineers. There should be an easier way to write rules without need of any code. ...
Support integration between D365 Fraud Protection and Azure Sentinel
Help customers of D365 Fraud Protection and Azure Sentinel leverage strengths of both products for an improved protection of their business by allowing easy integration between these products
A quick way to calculate the cost of fraud on the business
Help fraud managers understand potential benefit from D365 Fraud Protection so they can make a Buy/Try decision. The solution should take inputs which non-technical users can provide (e.g. historical transaction data, baseline metrics etc.) and then provid...
A way to quickly surface key fraud insights and act on them
Help inform fraud analysts about interesting patterns and fraud-related insights based on their own data as well as trends based on industry/geography, empowering them to act proactively and protect their organizations against fraud without significant man...
Provide ability to simulate risky transactions
Help D365 Fraud Protection customers simulate risky transactions, allowing them to easily validate their fraud protection rules, etc.
Quick and easy way to upload data from ERP system
Help customers get most out of D365 Fraud Protection by easily providing data (such as chargeback, labels etc.) via direct integration to popular ERP systems
Support fraud insights for last mile delivery
Help customers request fraud assessment prior to the delivery of packages, enabling them to turn around packages in-transit and minimize fraud loss
Bulk rule changes
Provide D365 Fraud Protection customers with the ability to apply a rule change to a group of rules simultaneously.
Real-time alerts
Ability to get notified when a certain threshold is met. Customer should be able to configure the event (For example, change in reject rate over some time frame -or- total number of rejections per hour etc.), the threshold, and mode of notification (For example, via email or text etc.). &nbs...
Ability to use IP Geolocation in Rules, Search and Export
Provide DFP Fraud Protection customers the ability to set rules, search and export based on IP geo location data. This is helpful when device fingerprinting is not captured.