# SFC Request and Response source: https://developer.mastercard.com/fld-suspected-fraud/documentation/parameters/sfc-req_resp/index.md ## SFC Request {#sfc-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:mmm'. | 2021-02-01T20:34:37 | | icaNumber | 3 | 7 | N | Mandatory | | ICA number of the originator initiating the FDC 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 | | fraudPostedDate | 8 | 8 | DATE | Optional | | Date on which the suspected fraud is posted in FLD by the originator. Format is 'YYYYMMDD'. | 20210120 | | fraudTypeCode | 2 | 2 | AN | Optional | | Code identifying the reason the originator submitted the transaction as fraud in FLD. Refer to 'Table 1' in 'Annexure 1' tab for possible values. | 1 | | accountDeviceType | 1 | 1 | AN | Optional | | 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 | | cardholderReportedDate | 8 | 8 | DATE | Optional | | Date on which the cardholder had reported the fraud. Format is 'YYYYMMDD'. | 20210118 | | cardInPossession | 1 | 1 | ENUM | Optional | U - Unknown | Flag to indicate if the card holder was in possession of the card at the time the fraud occurred. Possible values are 'Y', 'N' and 'U'. | N | | memo | 1 | 1000 | ANS | Optional | | Brief description by the originator providing some comment supporting the action. | | ## SFC Response {#sfc-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 | | auditControlNumber | 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 | | currentStatus | 1 | 50 | ENUM | Conditional | Indicates the current status of the fraud record being submitted. Possible values are: * 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. | |