# FDA (Minimal) Request and Response source: https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/fda-req-res-minimal/index.md ## FDA (Minimal) Request {#fda-minimal-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 '-'. | | | timestamp | 29 | 29 | DATE | Mandatory | | Timestamp of the request initiation by the originator in the format 'YYYY-MM-DDThh:mm:ss' or 'YYYY-MM-DDThh:mm:ss+hh:mm'. The value of '+hh:mm' portion should always be '-06:00' reflecting CST time. | 2021-02-01T20:34:37-06:00 | | icaNumber | 3 | 7 | N | Mandatory | | Issuer ICA number licensed to the transaction being processed. | 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 | | transactionIdentifiers | NA | NA | NA | Mandatory | | Array list containing the 'cfcKey' and 'cfcValue' combinations.Valid combinations are: * ARN * BRN * ARN \& BRN * TRC \& SER Dual Message (Auth Clearing Transaction) * ARN * BRN * ARN \& 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 | * Code ```code "transactionIdentifiers": [ { "cfcKey": "TRC", "cfcValue": "999998" }, { "cfcKey": "SER", "cfcValue": "682328931" } ] ``` | | cfcKey | 3 | 3 | ENUM | Mandatory | | Flag to indicate a debit / credit transaction. Possible values are: * 'ARN' for Acquirer Reference Number * 'BRN' for Banknet Reference Number * 'TRC' for Trace ID * 'SER' for Serial ID | | | cfcValue | 6 | 23 | AN | Mandatory | | Actual value of the 'cfcKey' provided subject to the following validations: * For ARN, Min Length is 23, Max Length is 23 and Data Type is N * For BRN, Min Length is 6, Max Length is 9 and Data Type is AN. BRN should be populated only from DE 63, subfield 2 (Banknet Reference Number). DE63, subfield 1(Financial Network Code) is NOT to be appended. * For TRC, Min Length is 6, Max Length is 6 and Data Type is N * For SER, Min Length is 9, Max Length is 9 and Data Type is N | | | cardNumber | 12 | 19 | N | Mandatory | | Cardholder account number used in the fraudulent transaction. Do not include leading zeros. Card number to be verified through Luhn's algorithm. | 5505135664572870008 | | transactionAmount | 1 | 12 | N | Mandatory | | This is the amount of funds the cardholder requested in the local currency of the acquirer or source location of the transaction. Value should be without decimals considering the local currency exponent value. | 10350 | | transactionDate | 8 | 8 | DATE | Mandatory | | Local date at the merchant location when the transaction occurred and accepted in CST format. Format is 'YYYYMMDD'. | 20210115 | | fraudPostedDate | 8 | 8 | DATE | Optional | | Date on which the transaction was posted as fraudulent at the customer's site. 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 1' in 'Annexure 1' tab for possible values. | 04 | | fraudSubTypeCode | 1 | 1 | A | Conditional | 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 2' 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 3' 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 | Mandatory | 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 | | avsResponseCode | 1 | 1 | A | Optional | U - Unknown | The Address Verification Service response code in the Authorization Request Response. Refer to 'Table 4' in 'Annexure 1' tab for possible values. | U | | authResponseCode | 2 | 2 | AN | Optional | 40 - Unknown | Indicates the result of the authorization request. Refer to 'Table 5' in 'Annexure 1' tab for possible values. | 01 | | memo | 1 | 1000 | ANS | Optional | | Brief description by the originator providing some comment supporting the action. Following special characters are not allowed - '\^','-','#','%','=','\*','!',';','\<',' | ','\>','+','/' and Space | | issuerSCAExemption | 1 | 2 | N | Optional | | Issuer SCA(Strong Customer Authentication) Exemption value. | | ## FDA (Minimal) Response {#fda-minimal-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+hh:mm'. 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. Possible values are : * Success -- This value indicates that the fraud submission was successful. * Failure -- This value indicates that the request failed due to technical or business error. * Pending - This value indicates that the request was partially processed. In such cases, the system automatically reprocesses the request after a specified time interval with the asynchronous response recorded in the Fraud and Loss Database. The GET Status API can be used after 24 hours to verify the final status of the submitted fraud record. | Success | | icaNumber | 3 | 7 | N | Conditional | ICA number of the originator present in the transaction is sent 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: * 'CONFIRMED - SUCCESS' * 'CONFIRMED - REJECTED' * 'CONFIRMED - SUSPENDED' This attribute will be absent if the request is not processed by FLD application. | CONFIRMED - SUCCESS | | matchLevelIndicator | 1 | 1 | ENUM | Conditional | Indicates if it is a Mastercard-built or Issuer-built record. Possible values are: * 'M' if Mastercard-built * 'I' if Issuer-built This attribute will be absent if the request is not processed by FLD application. | M | | financialTransactionIndicator | 1 | 20 | ENUM | Conditional | Indicates if the fraud record is being submitted against a financial transaction (having a clearing record) or a declined auth transaction (without a clearing record). Possible values are: * 'APPROVED' for financial transaction (having a clearing record) * 'DECLINED' for declined auth transaction (without a clearing record) This attribute will be absent in case of match not found in Data Warehouse and transaction processed as Issuer Built transaction. | DECLINED | | authorizationResponse | 1 | 200 | ANS | Conditional | Provides the 'Auth Response Code' and 'Auth Response Code Description' combination only if 'Financial Transaction Indicator' value is 'DECLINED'. This attribute will be absent for all other scenarios. | 05 - Do not honor | | errorDetails -\> Errors -\> Error | NA | NA | NA | Conditional | Array list containing the combination of error reason codes and their corresponding description. 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. | |