...
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. |
Fraud Types
Visa
The following fraud types are supported by the Visa network. The Default Rules column describes the logic used for setting the default fraud type.
Stored Value | Display Value | Default Rules | Notes | |||||
---|---|---|---|---|---|---|---|---|
0 | Lost | ClaimReason = "CardLost" | ||||||
1 | Stolen | ClaimReason = "CardStolen" | ||||||
2 | Card not received as Issued (NRI) | ClaimReason = "CardNotReceived" | ||||||
3 | Fraudulent application | ClaimReason = "FraudApp" | ||||||
4 | Issuer reported counterfeit | ClaimReason = "CardSecure" and 1 or more disputed transactions with NULL .ECI | ||||||
5 | Miscellaneous/Account takeover | ClaimReason = "AccountTakeOver" | ||||||
6 | Fraudulent use of account number | ClaimReason = "CardSecure" and all disputed transaction .ECI NOT NULL | ||||||
A | Incorrect Processing | |||||||
B | Account or Credentials Takeover | |||||||
C | Merchant Misrepresentation |
| ||||||
D | Manipulation of Account Holder |
|
Page Properties | ||
---|---|---|
|
...