DEC-RC-CC-110 · Design decision
Should a fraud test be held as static fraud data or as a fraud rule?
Compare the options before configuring the related setup steps.
Options
AStatic fraud data: a fixed value (phone, email, ZIP/postal code) matched against billing and delivery addresses. Simple to maintain and import, but slows submission when the list gets large.BFraud rule: variables and conditions combined with AND or OR, for example a customer group plus a specific product. More flexible, but every active rule is evaluated on the header and all lines, so complex rules slow submission.Recommendation
| Recommendation | Use static fraud data for known bad values and keep rules for combinations that a single value can't express. Test submission time for both before going live. |
|---|---|
| Depends on |
|
| Owner | Call center operations manager with the finance/credit controller |
Setup steps it affects
Source
| Source | https://learn.microsoft.com/en-us/dynamics365/commerce/set-up-fraud-alerts#define-fraud-criteria-and-rules |
|---|