...
| Info |
|---|
Bulk Fraud ReportingIn 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. If the disputes span multiple networks, a bulk action will be displayed for each supported network. |
| Drawio | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Tip |
|---|
Extension PointsTo configure how fraud reporting is executed, update Fraud Reporting Pre-Conditions. To enable "in-flow" fraud reporting that is only executed when chargeback, deny or write-off actions are executed, set the IsFraudReportingPostEnrichment DSS to false. 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 |
|---|
Fraud Reporting UpdatesWhen Fraud Reporting was previously performed on a claim, and the claim was later denied for any reason other than a Merchant Credit, a call is placed systematically to update the Fraud Reporting after claim resolution. This optional configuration is set on by default, where supported. |
Fraud Reporting Rejects
When a fraud report is rejected, the system should exit the flow and not attempt to delete the fraud reporting. The Completed Actions will show fraud reporting as successfully completed even if it was subsequently rejected.
...