# Confirmed Fraud
source: https://developer.mastercard.com/fld-fraud-submission/documentation/index.md

## Overview {#overview}

The Fraud and Loss Database (FLD) is the Mastercard repository for fraud transactions, and it serves as the source of truth for fraud information within the enterprise. As mentioned below, this platform currently provides multiple channels for submission and management of fraud records.

* Traditional Global File Transfer (GFT) mechanism for batch submissions.
* Manual online search and submission by users through Mastercard Connect™.
* File upload (Complete and Minimal record options) through Mastercard Connect™ by users preferring the bulk upload mechanism.

### Advantages of using APIs {#advantages-of-using-apis}

There is a growing need, especially among tech-savvy entities, to integrate with FLD through the Application Programming Interface (API) route. APIs offer several inherent advantages, including the following:

* **Automation**: With APIs, systems rather than people can manage the work, which helps entities update workflows to make them quicker and more productive.

* **Efficiency**: The content generated can be published automatically and is available for every channel. This allows users to share and distribute the content more easily.

* **Integration**: APIs make it easier to embed content from any site or application. This guarantees more fluid information delivery and an integrated user experience.

* **Personalization**: Using APIs, any user or company can customize the content and services that they use the most.

* **Adaptation**: Needs change over time and APIs help to anticipate changes. Data migration is better supported, and the information is reviewed more closely.

## How it Works {#how-it-works}

The flow chart provides a high-level overview of how FLD processes transactions submitted through the API channel and marks them as fraud.

![](https://static.developer.mastercard.com/content/fld-fraud-submission/uploads/fldhowitworksv3.png)

1. The user submits a transaction as fraud after identifying it.
2. The issuer (or processor) invokes the FLD API in real time to submit the transaction as fraud.
3. FLD processes the API request and notifies whether it was successful.
4. The FLD conveys the details related to the fraud submission request to the user.

## Before You Start {#before-you-start}

To use FLD APIs, you first create a project and then add the Fraud Submission API. Once created, you have access to the Sandbox. You use the Sandbox to test authentication with OAuth and validate that requests are correctly formatted and encrypted.
For more information, refer to [Create a new API project](https://developer.mastercard.com/fld-fraud-submission/tutorial/create-project/index.md).

## API Overview {#api-overview}

The table below describes each API and its purpose. Before moving to Sandbox and Production environments, your application must support all APIs listed.

|         **API Name**         |                                                    **Purpose**                                                    | **Applicability** |
|------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
| Fraud Data Add (Minimal)     | Add a new fraud record using minimal input parameters for Mastercard built transactions                           | Confirmed Fraud   |
| Fraud Data Add (Complete)    | Add a new fraud record using complete input parameters for both Mastercard and Issuer-built transactions          | Confirmed Fraud   |
| Fraud Data Change (Minimal)  | Change an existing fraud record using minimal input parameters for Mastercard built transactions                  | Confirmed Fraud   |
| Fraud Data Change (Complete) | Change an existing fraud record using complete input parameters for both Mastercard and Issuer-built transactions | Confirmed Fraud   |
| Fraud Data Delete            | Delete an existing fraud record for both Mastercard and Issuer-built transactions                                 | Confirmed Fraud   |
| Fraud Data Confirm           | Confirm a suspended fraud record for both Mastercard and Issuer-built transactions                                | Confirmed Fraud   |

## Next Steps {#next-steps}

Now that you have an understanding of what the service does, proceed to the [API Basics](https://developer.mastercard.com/fld-fraud-submission/documentation/api-basics/index.md) section for details on authentication and encryption.