# FSC Request and Response source: https://developer.mastercard.com/fld-suspected-fraud/documentation/parameters/fsc-req_resp/index.md ## FSC Request {#fsc-request} | **Attribute name** | **Min length** | **Max length** | **Data type** | **Presence** | **Default value** | **Field description** | **Example** | |------------------------|----------------|----------------|---------------|--------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| | refId | 36 | 36 | ANS | Mandatory | | Unique identification generated by the transaction originator using UUID logic to unambiguously link a request and response message.The only special character allowed will be '-'. | ecb2d942-eabd-42b6-87fd-69c19692bdc6 | | timestamp | 29 | 29 | DATE | Mandatory | | Timestamp of the request initiation by the originator in the format 'YYYY-MM-DDThh:mm:ss'. | 2021-02-01T20:34:37 | | icaNumber | 3 | 7 | N | Mandatory | | ICA number of the originator initiating the FDD request. | 1076 | | providerId | 2 | 2 | ENUM | Mandatory | | Indicates the originator of the request. Possible values are: * 10 for Issuer * 20 for Acquirer For the following scenarios, this value will be '10': * Issuer and Acquirer for a transaction is the same entity * FDD or FDE operation is performed on a Issuer-built record | 10 | | auditControlNumber | 15 | 15 | N | Mandatory | | Unique number generated by FLD application and provided in the response message for a successful fraud record submission ('FDA' event). This is used as a reference to subsequently modify, delete or convert a suspended to a confirmed fraud record. | 418142102142002 | | operationType | 1 | 50 | ENUM | Mandatory | | Indicates the type of operation to be performed for the given audit control number. Possible value is `CONFIRM_FRAUD`, `NOT_FRAUD` | `CONFIRM_FRAUD` | | transactionIdentifiers | NA | NA | NA | Conditional | | It can have below mentioned combination of parameters: * ARN * BRN * ARN and BRN * TRC and SER Dual Message (Auth Clearing Transaction) * ARN * BRN * ARN and BRN Dual Message (Authorization only) * BRN Dual Message (Clearing only) * ARN Single Message * TRC and SER ARN - Acquirer Reference Number (DE31 in Clearing Message) BRN - Banknet Reference Number (DE63, subfield 2 in Dual Message Authorization Message) TRC - Trace Id (DE 11 in Single Message Authorization Message) SER - Switch Serial Number (DE 63, subfield 3 in Single Message Authorization Message) Additional Guides or References: * Single Message System Specifications * Customer Interface Specifications * IPM Clearing Formats | | | acqRefNum | 23 | 23 | AN | | | Acquirer Reference Number | | | banknetRefNum | 6 | 9 | AN | | | Banknet reference Number | | | traceId | 6 | 6 | AN | | | Trace Id | | | serialId | 9 | 9 | AN | | | Serial Id | | | fraudPostedDate | 8 | 8 | DATE | Optional | | Date on which the fraud is posted in FLD by the originator. Format is 'YYYYMMDD'. | 20210120 | | fraudTypeCode | 2 | 2 | AN | Mandatory | | Code identifying the reason the originator submitted the transaction as fraud in FLD. Refer to 'Table 2' in 'Annexure 1' tab for possible values. | 04 | | fraudSubTypeCode | 1 | 1 | A | Mandatory | U - Unknown | Code to further identify the reason why the originator submitted the transaction as fraud in FLD. This attribute is mandatory for Issuer but optional for Acquirer.Refer to 'Table 3' in 'Annexure 1' tab for possible values. | U | | accountDeviceType | 1 | 1 | AN | Mandatory | | Indicates if the account uses a magnetic stripe, chip, pin, contactless or any combination thereof. Refer to 'Table 5' in 'Annexure 1' tab for possible values. | 1 | | avsResponseCode | 1 | 1 | A | Conditional | U - Unknown | The Address Verification Service response code in the Authorization Request Response.Refer to 'Table 6' in 'Annexure 1' tab for possible values. | U | | authResponseCode | 2 | 2 | AN | Conditional | 40 - Unknown | Indicates the result of the authorization request.Refer to 'Table 7' in 'Annexure 1' tab for possible values. | 01 | | memo | 1 | 1000 | ANS | Optional | | Brief description by the originator providing some comment supporting the action. | | ## FSC Response {#fsc-response} | **Attribute name** | **Min length** | **Max length** | **Data type** | **Presence** | **Field description** | **Example** | |-----------------------------------|----------------|----------------|---------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | refId | 36 | 36 | ANS | Mandatory | Unique identification generated by the transaction originator in the request API which is echoed back to link a request and response message. | ecb2d942-eabd-42b6-87fd-69c19692bdc6 | | timestamp | 29 | 29 | DATE | Mandatory | Timestamp of the response initiation by Mastercard in the format 'YYYY-MM-DDThh:mm:ss'. The value of '+hh:mm' portion should always be '-06:00' reflecting CST time. | 2021-02-01T20:34:40-06:00 | | responseCode | 3 | 3 | N | Mandatory | Response code indicating success or failure of the transaction at an API level. Errors at a record level will be handled through 'errorDetails' element associated with each record. | 000 | | responseMessage | 1 | 100 | ANS | Mandatory | Transaction response description corresponding to the response code. | Success | | icaNumber | 3 | 7 | N | Conditional | ICA number of the originator provided in the request API which is echoed back.This attribute will be absent if the request is not processed by FLD application. | 1076 | | confirmedAuditControlNumber | 15 | 15 | N | Conditional | Unique number generated by FLD application and provided in the response message for a successful fraud record submission ('FDA' event). This is used as a reference in the request API to subsequently modify, delete or convert a suspended to a confirmed fraud record and is echoed back.This attribute will be absent if the request is not processed by FLD application. | 418142102142002 | | previousStatus | 1 | 50 | ENUM | Conditional | Indicates the previous status of the fraud record being submitted. Possible values are: * SUSPECTED-SUCCESS This attribute will be absent if the request is not processed by FLD application. | SUSPECTED-SUCCESS | | currentStatus | 1 | 50 | ENUM | Conditional | Indicates the current status of the fraud record being submitted. Possible values are: * 'CONFIRMED-SUCCESS' This attribute will be absent if the request is not processed by FLD application. | CONFIRMED-SUCCESS | | errorDetails -\> Errors -\> Error | NA | NA | NA | Conditional | Array list containing the combination of error reason codes and their corresponding description (can provide up to 5 errors for a record). It will be absent if the request is processed by FLD application successfully. | * Code ```code "errorDetails":{ "Errors":{ "Error":[ { "ReasonCode":"60002", "Description":"timestamp attribute or attribute value is missing or incorrect." } ] } } ``` | | ReasonCode | 5 | 5 | N | Conditional | Error code indicating the reason for the failure of a particular record. | | | Description | 1 | 1000 | ANS | Conditional | Description corresponding to the error reason code. | |