...
The Fraud Reporting flow is executed on fraud card claims to facilitate the reporting process. When a service is available, this action is complete automatically by the system. When no service is configured, an assignment is generated to prompt a user to complete the necessary actions.
| Info | ||
|---|---|---|
| ||
In an environment where fraud reporting is completed manually, a bulk option is available to reduce the number of steps required to complete the fraud reporting step. This is only available when all disputes transactions are on the same acquirer network. |
| Drawio | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Tip | ||
|---|---|---|
| ||
To configure how fraud reporting is executed, update Fraud Reporting Pre-Conditions. To configure what automated methods are available and the system should determine which one to use, update DetermineAutoFraudReportingMethod. To configure the maximum number of retry attempts for the integration service, update D_ImplConfig.MaxFraudReportingServiceRetries. To enable verification mode for Mastercard, update the MCFraudReportingVerificationModeEnabled DSS. This will require a user to review all fraud values before sending the report to Mastercard. To enable verification mode for Visa, update the VisaFraudReportingVerificationModeEnabled DSS. This will require a user to review all fraud values before sending the report to Visa. | ||
| Info | ||
| ||
In an environment where fraud reporting is completed manually, a bulk option is available to reduce the number of steps required to complete the fraud reporting step. This is only available when all disputes transactions are on the same acquirer network. |
| Page Properties | ||
|---|---|---|
|
...