# Suspected Fraud Testing Tutorial
source: https://developer.mastercard.com/fld-suspected-fraud/documentation/tutorial-1/index.md

## Overview {#overview}

Insomnia is a free and open-source REST client application on Linux, Mac and Windows operating systems. This tutorial shows you how to use Insomnia with the Mastercard authentication plugin to make an API call.

This is a tutorial guide for executing the test cases within our Suspected Fraud Insomnia collection.

## Pre-requisites {#pre-requisites}

* Developer portal project created and credentials downloaded as per the process in the Quick Start Guide.
* Insomnia installed and configured as per the instructions in [Integration and Testing](https://developer.mastercard.com/fld-suspected-fraud/documentation/integration/index.md) together with our Insomnia Collection.

## You will learn how to {#you-will-learn-how-to}

* Execute each of the test cases within the Suspected Fraud Insomnia collection.

## Suspected Fraud Add (SFA) {#suspected-fraud-add-sfa}

### Steps to submit SFA {#steps-to-submit-sfa}

1. Issuer or Acquirer invokes SFA API to add a suspected fraud record in FLD.
2. Send a **POST** request (`/fld/suspected-frauds/mastercard-frauds`) in Insomnia using the SFA payload.
3. Verify that the `responseMessage` field indicates success.

Note: For Issuer `providerID` is '10' and for Acquirer `providerID` ID is '20'.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-a.png)
![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-b.png)

## Suspected Fraud Change (SFC) {#suspected-fraud-change-sfc}

### Steps to submit SFC {#steps-to-submit-sfc}

1. Issuer or Acquirer invokes SFC API to change a suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/mastercard-frauds `) in Insomnia using the SFC payload with unique Audit Control Number (ACN).
3. Verify that the `responseMessage` field indicates success.

Note: For Issuer `providerID` is '10' and for Acquirer `providerID` ID is '20'.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-c.png)
![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-d.png)

## Fraud Suspected Confirm (FSC) {#fraud-suspected-confirm-fsc}

### Steps to submit FSC {#steps-to-submit-fsc}

1. Issuer invokes FSC API to confirm a suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/fraud-states`) in Insomnia using the FSC payload with operation type as "CONFIRM_FRAUD" and unique ACN.
3. Verify that the `responseMessage` field indicates success.

Note: For Issuer `providerID` is '10'.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-e.png)

## Fraud Suspected Not Confirm (FSN) {#fraud-suspected-not-confirm-fsn}

### Steps to submit FSN {#steps-to-submit-fsn}

1. Issuer invokes FSN API not to confirm an earlier submitted suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/fraud-states`) in Insomnia using the FSN payload with operation type as "NOT_FRAUD" and unique ACN.
3. Verify that the `responseMessage` field indicates success.

Note: For Issuer `providerID` is '10'.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-f.png)

## Suspected Fraud Delete (SFD) {#suspected-fraud-delete-sfd}

### Steps to submit SFD {#steps-to-submit-sfd}

1. Acquirer invokes SFD API to delete a suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/fraud-states`) in Insomnia using the SFD payload with operation type as "DELETE" and unique ACN.
3. Verify that the `responseMessage` field indicates success.

Note: For Issuer `providerID` is '20'.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-g.png)

## Suspected Fraud Status (SFS) {#suspected-fraud-status-sfs}

### Steps to submit SFS {#steps-to-submit-sfs}

1. Issuers or Acquirers invokes SFS API to fetch the status of the fraud record.
2. Make a **GET** request (`/fld/suspected-frauds/fraud-statuses/icas/`) in Insomnia using the unique Interbank Card Association(ICA)+ACN or ICA+Ref_Id combination.
3. You can append `ref_id` and `acn` to request url in following way:
   * `/fraud-statuses/icas/{ica}?ref_id={ref_id}&acn={acn}`
4. Verify that the `responseMessage` field indicates success.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-h.png)

## Schema and Business Validations {#schema-and-business-validations}

### Steps to verify SFA Schema failure {#steps-to-verify-sfa-schema-failure}

1. Issuer or Acquirer invokes SFA API to add a suspected fraud record in FLD.
2. Send a **POST** request (`/fld/suspected-frauds/mastercard-frauds`) in Insomnia using the SFA payload with Unique ACN.
3. Verify the schema failure response message.

Note: For Issuer `providerID` is '10' and for Acquirer `providerID` ID is '20'.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-i.png)

### Steps to verify SFA business failure {#steps-to-verify-sfa-business-failure}

1. Issuer or Acquirer invokes SFA API to add a suspected fraud record in FLD.
2. Send a **POST** request (`/fld/suspected-frauds/mastercard-frauds`) in Insomnia using the SFA payload with Unique ACN.
3. Verify the business failure response message.

Note: For Issuer `providerID` is '10' and for Acquirer `providerID` ID is '20'.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-j.png)

### Steps to verify SFC Schema failure {#steps-to-verify-sfc-schema-failure}

1. Issuer or Acquirer invokes SFC API to change a suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/mastercard-frauds`) in Insomnia using the SFC payload with Unique ACN.
3. Verify the schema failure response message.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-k.png)

### Steps to verify SFC business failure {#steps-to-verify-sfc-business-failure}

1. Issuer or Acquirer invokes SFC API to change a suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/mastercard-frauds`) in Insomnia using the SFC payload with unique ACN.
3. Verify the business failure response message.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-l.png)

### Steps to verify FSC schema failure {#steps-to-verify-fsc-schema-failure}

1. Issuer invokes FSC API to confirm a suspected fraud record in FLD.
2. Send a ****PUT**** request (`/fld/suspected-frauds/fraud-states`) in Insomnia using the FSC payload with Unique ACN.
3. Verify the schema failure response message.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-m.png)

### Steps to verify FSC business failure {#steps-to-verify-fsc-business-failure}

1. Acquirer invokes FSC API to change a suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/fraud-states`) in Insomnia using the FSC payload with Unique ACN.
3. Verify the business failure response message.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-n.png)

### Steps to verify FSN schema failure {#steps-to-verify-fsn-schema-failure}

1. Issuer invokes FSN API to not confirm a suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/fraud-states`) in Insomnia using the FSN payload with Unique ACN.
3. Verify the schema failure response message.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-o.png)

### Steps to verify FSN business failure {#steps-to-verify-fsn-business-failure}

1. Acquirer invokes FSN API to change a suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/fraud-states`) in Insomnia using the FSN payload with Unique ACN.
3. Verify the business failure response message.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-p.png)

### Steps to verify SFD schema failure {#steps-to-verify-sfd-schema-failure}

1. Issuer or Acquirer invokes SFD API to delete a suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/fraud-states`) in Insomnia using the SFD payload with Unique ACN.
3. Verify the schema failure response message.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-q.png)

### Steps to verify SFD business failure {#steps-to-verify-sfd-business-failure}

1. Issuer or Acquirer invokes SFD API to delete a suspected fraud record in FLD.
2. Send a **PUT** request (`/fld/suspected-frauds/fraud-states`) in Insomnia using the SFD payload with Unique ACN.
3. Verify the business failure response message.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-r.png)

### Steps to verify SFS business failure {#steps-to-verify-sfs-business-failure}

1. Invokes SFS API to get status of a suspected fraud record in FLD.
2. Send a **GET** (`/fld/suspected-frauds/fraud-statuses/icas/{ica}`) request in Insomnia using the SFS payload.
3. Verify the business failure response message.

Note: This endpoint (for example, `/fraud-statuses/icas/1076?ref_id=ecb2d942-eabd-42b6-87fd-69c19692bdc6&acn=418142102142002`) is to get a status of the transactions using `ica`, `refId` and, `acn`.

![](https://static.developer.mastercard.com/content/fld-suspected-fraud/uploads/ins-s.png)