# Submit fraud
source: https://developer.mastercard.com/mastercom-extended/documentation/use_cases/fraud/index.md

## How submitting fraud works {#how-submitting-fraud-works}

This use case demonstrates the process of an issuer submitting a transaction as confirmed fraud to Mastercom Extended for submission to the Fraud and Loss Database. For more information, refer to the [Submit fraud](https://developer.mastercard.com/mastercom-extended/tutorial/fraud/index.md) tutorial.
Diagram fraud_over

**Step 1:** The issuer searches for transactions. The transaction search response will contain any Claim IDs in Mastercom Extended already associated with the transaction. Claim IDs from the Mastercom API v6 system will not be in this response.  

**Step 2:** The issuer creates a claim for the selected transaction. If a claim has previously been created in Mastercom v6 for a transaction, an attempted Mastercom Extended Claim Creation API call (POST /claims) will yield an error message indicating a claim has already been created for this transaction in the Mastercom v6 system.  

**Step 3-optional:** The issuer retrieves claim details to view the confirmed fraud.  

**Step 4:** The issuer submits a transaction as confirmed fraud to Mastercom Extended for submission to the Fraud and Loss Database.  

## Submit confirmed fraud {#submit-confirmed-fraud}

Issuers use this endpoint to submit a transaction as confirmed fraud to Mastercom Extended for submission to the Fraud and Loss Database.
Diagram fraud
API Reference: `POST /claims/{claim_id}/frauds`