Fraud and Loss Database Reporting
The Fraud and Loss Database (FLD) Reporting feature ensures that all customer-reported fraudulent transactions are submitted to Mastercard’s Fraud and Loss Database in real-time. FLD acts as the enterprise-wide source of truth for fraud-related data and supports Mastercard’s fraud monitoring and resolution processes.
This feature is enabled only when the system for fraud report submission configuration is set to Fraud and Loss Database (FLD). Issuers must select FLD as the reporting system in the SDAA configuration settings to activate this integration. If FLD is not enabled, then fraud report is submitted through the Mastercom Create Fraud API. Only fraud report creation is supported through Mastercom Fraud API. Edit and Delete of fraud reports are supported in FLD only.
Key features
Real-Time Fraud Submission: Automatically triggers the FDAMinimal API to report eligible fraudulent transactions when the supplemental information screen is submitted during dispute case creation. This ensures timely and compliant fraud reporting to Mastercard without requiring manual intervention.
Customer-Driven Identification: Fraudulent transactions are flagged based on customer input during the dispute process.
API Response Handling: Upon invoking the FDAMinimal API for fraud submission, the system presents the outcome to the user, indicating whether the submission was successful or failed. The response details are captured in the Service Audit for traceability and compliance. Additionally, the fraud submission status is logged in the case history.
Exception Management: Follows the standard MCOM exception handling paradigm to ensure robust error tracking and resolution.
Other reporting alternatives
Smart Dispute Agentic Automation (SDAA) provides three local actions for FLD reporting:
Submit Fraud and Loss Database Report: SDAA provides a dedicated Submit FLD local action to handle scenarios where the fraud report API call to Mastercard’s Fraud and Loss Database (FLD) is technically successful but returns a business exception status, such as CONFIRMED-SUSPENDED. This local action enables issuers to retry fraud report submission when the initial request is accepted by the FLD API but fails to reach a confirmed status due to business-level validation or processing issues.
Edit Fraud report: SDAA provides issuers with the ability to modify or delete fraud reports submitted to Mastercard’s Fraud and Loss Database (FLD) through a dedicated local action named 'Edit fraud report'. This action is available to back-office users after a successful fraud submission and presents two options:
- Modify fraud report: Allows updating fraud details by answering follow-up questions, including:
-
Fraud Type
-
Fraud Subtype
-
Cardholder in Possession
-
-
Delete fraud report: Submits a deletion request to FLD without requiring additional input.
Fraud Report Inquiry: SDAA provides issuers with the ability to inquire the status of a submitted fraud report through a dedicated local action named 'Fraud status inquiry'. This feature enables back-office agents to retrieve real-time status updates from Mastercard’s Fraud and Loss Database (FLD) using the GetFraudStatus service. It helps validate whether a fraud report was successfully processed and provides detailed metadata for audit and operational tracking.
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?