# Code and Formats source: https://developer.mastercard.com/fld-suspected-fraud/documentation/code-and-formats/index.md ## Errors Overview {#errors-overview} The error message returned will depend on which API generated the error and at what point the request failed. Error messages will be in one of the two formats. * [**Gateway Error Messages**](https://developer.mastercard.com/fld-suspected-fraud/documentation/code-and-formats/index.md#gateway-error-message): Returned by the API gateway and occur when OAuth authentication fails. * [**API Error Messages**](https://developer.mastercard.com/fld-suspected-fraud/documentation/code-and-formats/index.md#api-error-messages): Returned by the FLD application and occur during technical or business decline scenarios. Note: To ensure forward compatibility, client implementations must support new elements being added to the API responses in future. ## Gateway Error Messages {#gateway-error-messages} All errors returned by the gateway follow the same data format. ```json { "Errors": { "Error": [ { "Source": "Gateway", "ReasonCode": "", "Description": "", "Recoverable": "true/false", "Details": null } ] } } ``` | Field | Description | |-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Source** | The application that generated the error. The gateway will generate and return every error message with this field set to `Gateway`. If the source field shows a different value, another application generates the error. | | **ReasonCode** | A unique constant identifying the error case encountered during transaction processing. For example, use `INVALID_SIGNATURE` when the request signature does not match the expected one. | | **Description** | Description of the `ReasonCode` field with additional details. | | **Recoverable** | Indicates if the error is always returned for the current request, or if retrying might change the result. For example, if the request contains an invalid signature, retrying never results in success. However, if the error is related to some unexpected timeout with the service, retrying the call could result in a successful response. | | **Details** | Always null, present for backwards compatibility. | Note: For more information about gateway error messages including the error codes, refer to [Gateway Error Codes](https://developer.mastercard.com/platform/documentation/security-and-authentication/gateway-error-codes/). ## API Error Messages {#api-error-messages} Once the request payload hits the FLD application, it goes through multiple validations. If validation fails, FLD does not process the request and returns a failure response to the initiator. Categorize these failures as shown: * **Technical declines**: These are typically failures on account of schema-related validations like issues related to data type, format, or length of an attribute. * **Business declines**: These are on account of business validation errors such as conditionality check, list of accepted attribute values, presence of record in transaction or fraud repository. FLD returns the appropriate response code in the response payload in the event of a technical or business decline. FLD returns the response code '000' if it processes the request payload successfully after completing all related validations. The following table shows the response code and corresponding response message for different scenarios. The technical declines may range between "100" and "199" and the business declines may range between "200" and "299". | **Response Code** | **Response message** | **Type of decline** | |-------------------|----------------------|---------------------| | 000 | Success | N/A | | 001 | Pending | N/A | | 100 to 199 | Failure | Technical | | 200 to 299 | Failure | Business | While the response code provides the initiator with information about the type of decline, the error code and its corresponding error message provide the specific reason for the failure at a granular level. FLD may return one or more error codes and respective error messages (in an array list) for a particular response code. #### Sample failure response payload {#sample-failure-response-payload} { "refId":"ecb2d942-eabd-42b6-87fd-69c19692bdc6", "timestamp":"2021-03-16T20:34:40-06:00", "responseCode":"100", "responseMessage":"Failure", "errorDetails":{ "Errors":{ "Error":[ { "ReasonCode":"60004", "Description":"cardNumber attribute value length not in range. Minimum Length:12 and Maximum Length: 19." }, { "ReasonCode":"60003", "Description":"transactionAmount incorrect datatype of attribute value." } ] } } } #### Failure scenarios {#failure-scenarios} ##### Suspected Fraud Add {#suspected-fraud-add} | Sr No | Failure Scenario | Response Code | Reason Code | Description | Resolution Steps | |-------|----------------------------------------------------------------------------------------------------|---------------|-------------|----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | Banknet reference Number is missing. | 200 | 20850 | Banknet reference Number is missing | Correct the FDA request and resubmit again. | | 2 | Required Field \[Acquirer Reference Number\] is missing | 200 | 20805 | Required Field \[Acquirer Reference Number\] is missing | Correct the FDA request and resubmit again. | | 3 | FLD DB exception | 100 | 40100 | Fraud and Loss Database exception occurred. Record is showing an error. | Retry after sometime. | | 4 | No record found or more than one matched record based on the input parameters provided | 200 | 41200 | Unable to match transaction in the data warehouse. Validate transaction details and resubmit. | Correct the FDA request and resubmit again. | | 5 | Constraint violation during DB operation | 100 | 41600 | Constraint violation exception occurred. Record is showing an error. | Retry after sometime. | | 6 | Attribute is missing | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the FDA request and resubmit again. | | 7 | Attribute is incorrect | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the FDA request and resubmit again. | | 8 | Attribute value is missing | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the FDA request and resubmit again. | | 9 | Incorrect datatype of attribute value | 100 | 60003 | `` incorrect datatype of attribute value. | Correct the FDA request and resubmit again. | | 10 | Incorrect minimum length of attribute value | 100 | 60004 | `` attribute value length not in range. Minimum length: `

` and Maximum Length: ``. | Correct the FDA request and resubmit again. | | 11 | Incorrect maximum length of attribute value | 100 | 60004 | `` attribute value length not in range. Minimum length: `

` and Maximum Length: ``. | Correct the FDA request and resubmit again. | | 12 | Incorrect minimum value of attribute value | 100 | 60005 | `` attribute value not in range. Minimum value: `

` and Maximum Value: ``. | Correct the FDA request and resubmit again. | | 13 | Incorrect maximum value of attribute value | 100 | 60005 | `` attribute value not in range. Minimum value: `

` and Maximum Value: ``. | Correct the FDA request and resubmit again. | | 14 | Attribute value is not a defined ENUM value | 100 | 60006 | `` attribute value is not a defined ENUM value. | Correct the FDA request and resubmit again. | | 15 | The attribute value does not follow the defined pattern (for example, regex) | 100 | 60007 | `` attribute value does not follow the defined pattern. | Correct the FDA request and resubmit again. | | 16 | Array object is missing | 100 | 60008 | `` array object is missing or incorrect. | Correct the FDA request and resubmit again. | | 17 | Array object is incorrect | 100 | 60008 | `` array object is missing or incorrect. | Correct the FDA request and resubmit again. | | 18 | The timestamp value in request cannot be 'x' days before the current date | 200 | 60012 | Timestamp value in request should be the same as the current date. | Correct the FDA request and resubmit again. | | 19 | The timestamp value in request cannot be 'y' days after the current date | 200 | 60012 | Timestamp value in request should be the same as the current date. | Correct the FDA request and resubmit again. | | 20 | Duplicate reference ID for the initiator and service combination | 200 | 60013 | Duplicate Reference ID `` for the initiator and service combination. | Correct the FDA request and resubmit again. | | 21 | ICA number does not exist in the system | 200 | 60014 | ICA number does not exist in the system. | Correct the FDA request and resubmit again. | | 22 | ICA number is not active in the system | 200 | 60015 | ICA number is not active in the system. | Correct the FDA request and resubmit again. | | 23 | Request initiator is not authorized for this particular account range | 200 | 60018 | Request initiator is not authorized for this particular account range. | The user cannot submit a fraud record as the user is not provisioned for this particular account range. User can request provisioning for a particular account range through MCConnect. | | 24 | The transaction date in request cannot be 18 months before the current date | 200 | 60025 | The transaction date cannot be 18 months before the current date. | Correct the FDA request and resubmit again. | | 25 | The transaction date in request cannot be after the current date | 200 | 60026 | The transaction date cannot be after the current date. | Correct the FDA request and resubmit again. | | 26 | Fraud posted date in request cannot be before current date | 200 | 60027 | Fraud posted date cannot be before current date -1. | Correct the FDA request and resubmit again. | | 27 | Fraud posted date in request cannot be after current date | 200 | 60028 | Fraud posted date cannot be after current date. | Correct the FDA request and resubmit again. | | 28 | Fraud posted date in request cannot be before transaction date in request | 200 | 60029 | Fraud posted date cannot be before transaction date. | Correct the FDA request and resubmit again. | | 29 | Account Device Type does not exist in the system | 200 | 60033 | Account Device Type does not exist in the system. | Correct the FDA request and resubmit again. | | 30 | Account device Type is not active in the system | 200 | 60034 | Account Device Type is not active in system. | Correct the FDA request and resubmit again. | | 31 | Cardholder reported date in request cannot be 18 months before the current date | 200 | 60039 | Cardholder reported date cannot be 18 months before the current date. | Correct the FDA request and resubmit again. | | 32 | Cardholder reported date in request cannot be after the current date | 200 | 60040 | Cardholder reported date cannot be after current date. | Correct the FDA request and resubmit again. | | 33 | Cardholder reported date in request cannot be before transaction date in request | 200 | 60041 | Cardholder reported date cannot be before transaction date. | Correct the FDA request and resubmit again. | | 34 | Cardholder reported date in request cannot be after fraud posted date in request | 200 | 60042 | Cardholder reported date cannot be after fraud posted date. | Correct the FDA request and resubmit again. | | 35 | Cannot perform action. The record is already marked as confirmed. | 200 | 60058 | Cannot perform action. The record is already marked as confirmed. | Correct the FDA request and resubmit again. | | 36 | Cannot perform action. The record is already marked as not-confirmed | 200 | 60059 | Cannot perform action. The record is already marked as not-confirmed | Correct the FDA request and resubmit again. | | 37 | Invalid combination of transaction identifiers in the request | 200 | 60130 | Invalid list of transaction identifier combination. | Correct the FDA request and resubmit again. | | 38 | Suspect Fraud type code is mapped to the Acquirer and trying to use by the issuer | 200 | 60131 | The suspected fraud type is mapped to the acquirer entity. Request is errored out. | Correct the FDA request and resubmit again. | | 39 | The transaction is already marked as suspected by another issuer entity. Request is errored out. | 200 | 60132 | The transaction is already marked as suspected by another issuer entity. Request is errored out. | Correct the FDA request and resubmit again. | | 40 | ProviderId and Issuer/ Acquirer Product mapping does not exist in system | 200 | 60136 | ProviderId and Issuer/ Acquirer Product mapping does not exist in system | The user cannot submit a fraud record as product mapping is not present. User can request provisioning for a particular product through MCConnect. | | 41 | Suspect Fraud type code is mapped to Issuer and trying to use Non-Issuer mapped Non-issuer | 200 | 70001 | The suspected fraud type is mapped to the issuer entity. Request is errored out. | Correct the FDA request and resubmit again. | | 42 | The suspected fraud type is inactive or not a valid fraud type | 200 | 70002 | The suspected fraud type is inactive or not a valid fraud type. | Correct the FDA request and resubmit again. | | 43 | The transaction is already marked as suspected by another acquirer entity. Request is errored out. | 200 | 70006 | The transaction is already marked as suspected by another acquirer entity. Request is errored out. | Correct the FDA request and resubmit again. | | 44 | The suspected transaction cannot be confirmed by the acquirer entity. | 200 | 70010 | The suspected transaction cannot be confirmed by the acquirer entity. | Correct the FDA request and resubmit again. | | 45 | Any unexpected error while processing the request | 200 | 90004 | Unexpected error while processing a request. | Correct the FDA request and resubmit again. | ##### Suspected Fraud Change {#suspected-fraud-change} | Sr No | Failure Scenario | Response Code | Reason Code | Description | Resolution Steps | |-------|--------------------------------------------------------------------------------------------|---------------|-------------|-----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | The record to be changed could not be found. Correct ACN and resubmit. | 200 | 21803 | The record to be changed could not be found. Correct ACN and resubmit. | Correct the FDC request and resubmit again. | | 2 | FLD DB exception | 100 | 40100 | Fraud and Loss Database exception occurred. Record is errored out. | Retry after sometime. | | 3 | Constraint violation during DB operation | 100 | 41600 | Constraint violation exception occurred. Record is errored out. | Retry after sometime. | | 4 | Attribute is missing | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the FDC request and resubmit again. | | 5 | Attribute is incorrect | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the FDC request and resubmit again. | | 6 | Attribute value is missing | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the FDC request and resubmit again. | | 7 | Incorrect datatype of attribute value | 100 | 60003 | `` incorrect datatype of attribute value. | Correct the FDC request and resubmit again. | | 8 | Incorrect minimum length of attribute value | 100 | 60004 | `` attribute value length not in range. Minimum length: `

` and Maximum Length: ``. | Correct the FDC request and resubmit again. | | 9 | Incorrect maximum length of attribute value | 100 | 60004 | `` attribute value length not in range. Minimum length: `

` and Maximum Length: ``. | Correct the FDC request and resubmit again. | | 10 | Incorrect minimum value of attribute value | 100 | 60005 | `` attribute value not in range. Minimum value: `

` and Maximum Value: ``. | Correct the FDC request and resubmit again. | | 11 | Incorrect maximum value of attribute value | 100 | 60005 | `` attribute value not in range. Minimum value: `

` and Maximum Value: ``. | Correct the FDC request and resubmit again. | | 12 | Attribute value is not a defined ENUM value | 100 | 60006 | `` attribute value is not a defined ENUM value. | Correct the FDC request and resubmit again. | | 13 | Attribute value does not follow the defined pattern (for example, regex) | 100 | 60007 | `` attribute value does not follow the defined pattern. | Correct the FDC request and resubmit again. | | 14 | Array object is missing | 100 | 60008 | `` array object is missing or incorrect. | Correct the FDC request and resubmit again. | | 15 | Array object is incorrect | 100 | 60008 | `` array object is missing or incorrect. | Correct the FDC request and resubmit again. | | 16 | Timestamp value in request cannot be 'x' days before current date | 200 | 60012 | Timestamp value in request should be same as current date. | Correct the FDC request and resubmit again. | | 17 | Timestamp value in request cannot be 'y' days after current date | 200 | 60012 | Timestamp value in request should be same as current date. | Correct the FDC request and resubmit again. | | 18 | Duplicate Reference ID for the initiator and service combination | 200 | 60013 | Duplicate Reference ID `` for the initiator and service combination. | Correct the FDC request and resubmit again. | | 19 | ICA Number does not exist in system | 200 | 60014 | ICA Number does not exist in system. | Correct the FDC request and resubmit again. | | 20 | ICA Number is not active in system | 200 | 60015 | ICA Number is not active in system. | Correct the FDC request and resubmit again. | | 21 | Request initiator is not authorized for this particular account range | 200 | 60018 | Request initiator is not authorized for this particular account range. | User cannot submit a fraud record as user is not provisioned for this particular account range. User can request provisioning for a particular account range through MCConnect. | | 22 | The transaction date in request cannot be 18 months before current date | 200 | 60025 | The transaction date cannot be 18 months before current date. | Correct the FDC request and resubmit again. | | 23 | Fraud posted date in request cannot be before current date | 200 | 60027 | Fraud posted date cannot be before current date -1. | Correct the FDC request and resubmit again. | | 24 | Fraud posted date in request cannot be after current date | 200 | 60028 | Fraud posted date cannot be after current date. | Correct the FDC request and resubmit again. | | 25 | Fraud posted date in request cannot be before transaction date in request | 200 | 60029 | Fraud posted date cannot be before transaction date. | Correct the FDC request and resubmit again. | | 26 | Account Device Type does not exist in system | 200 | 60033 | Account Device Type does not exist in system. | Correct the FDC request and resubmit again. | | 27 | Account Device Type is not active in system | 200 | 60034 | Account Device Type is not active in system. | Correct the FDC request and resubmit again. | | 28 | Cardholder reported date in request cannot be 18 months before current date | 200 | 60039 | Cardholder reported date cannot be 18 months before current date. | Correct the FDC request and resubmit again. | | 29 | Cardholder reported date in request cannot be after current date | 200 | 60040 | Cardholder reported date cannot be after current date. | Correct the FDC request and resubmit again. | | 30 | Cardholder reported date in request cannot be before transaction date in request | 200 | 60041 | Cardholder reported date cannot be before transaction date. | Correct the FDC request and resubmit again. | | 31 | Cardholder reported date in request cannot be after fraud posted date in request | 200 | 60042 | Cardholder reported date cannot be after fraud posted date. | Correct the FDC request and resubmit again. | | 32 | None of the optional parameters provided in the request | 200 | 60057 | Request does not contain any parameter to be changed. | Correct the FDC request and resubmit again. | | 33 | Cannot perform action. The record is already marked as confirmed. | 200 | 60058 | Cannot perform action. The record is already marked as confirmed. | Correct the FDC request and resubmit again. | | 34 | Cannot perform action. The record is already marked as not-confirmed | 200 | 60059 | Cannot perform action. The record is already marked as not-confirmed | Correct the FDC request and resubmit again. | | 35 | Suspect Fraud type code is mapped to the Acquirer and trying to use by the issuer | 200 | 60131 | The suspected fraud type is mapped to the acquirer entity. Request is errored out. | Correct the FDC request and resubmit again. | | 36 | Transaction marked as suspected by the issuer only cannot be changed | 200 | 60133 | Transaction marked as suspected by the issuer only cannot be changed | Correct the FDC request and resubmit again. | | 37 | ProviderId and Issuer/ Acquirer Product mapping does not exist in system | 200 | 60136 | ProviderId and Issuer/ Acquirer Product mapping does not exist in system | The user cannot submit a fraud record as product mapping is not present. User can request provisioning for a particular product through MCConnect. | | 38 | Suspect Fraud type code is mapped to Issuer and trying to use Non-Issuer mapped Non-issuer | 200 | 70001 | The suspected fraud type is mapped to the issuer entity. Request is errored out. | Correct the FDC request and resubmit again. | | 39 | The suspected fraud type is inactive or not a valid fraud type | 200 | 70002 | The suspected fraud type is inactive or not a valid fraud type. | Correct the FDC request and resubmit again. | | 40 | Any unexpected error while processing the request | 200 | 90004 | Unexpected error while processing a request. | Correct the FDC request and resubmit again. | ##### Suspected to Confirm {#suspected-to-confirm} | Sr No | Failure Scenario | Response Code | Reason Code | Description | Resolution Steps | |-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------|-----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | Banknet Reference Number is missing. | 200 | 20850 | Banknet Reference Number is missing | Correct the request and resubmit again. | | 2 | Required Field \[Acquirer Reference Number\] is missing | 200 | 20805 | Required Field \[Acquirer Reference Number\] is missing | | | Correct the request and resubmit again. | | | | | | | 3 | FLD DB exception | 100 | 40100 | Fraud and Loss Database exception occurred. Record is errored out. | Retry after sometime. | | 4 | Constraint violation during DB operation | 100 | 41600 | Constraint violation exception occurred. Record is errored out. | Retry after sometime. | | 5 | Attribute is missing | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the request and resubmit again. | | 6 | Attribute is incorrect | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the request and resubmit again. | | 7 | Attribute value is missing | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the request and resubmit again. | | 8 | Incorrect datatype of attribute value | 100 | 60003 | `` incorrect datatype of attribute value. | Correct the request and resubmit again. | | 9 | Incorrect minimum length of attribute value | 100 | 60004 | `` attribute value length not in range. Minimum length: `

` and Maximum Length: ``. | Correct the request and resubmit again. | | 10 | Incorrect maximum length of attribute value | 100 | 60004 | `` attribute value length not in range. Minimum length: `

` and Maximum Length: ``. | Correct the request and resubmit again. | | 11 | Incorrect minimum value of attribute value | 100 | 60005 | `` attribute value not in range. Minimum value: `

` and Maximum Value: ``. | Correct the request and resubmit again. | | 12 | Incorrect maximum value of attribute value | 100 | 60005 | `` attribute value not in range. Minimum value: `

` and Maximum Value: ``. | Correct the request and resubmit again. | | 13 | Attribute value is not a defined ENUM value | 100 | 60006 | `` attribute value is not a defined ENUM value. | Correct the request and resubmit again. | | 14 | Attribute value does not follow the defined pattern (for example, regex) | 100 | 60007 | `` attribute value does not follow the defined pattern. | Correct the request and resubmit again. | | 15 | Array object is missing | 100 | 60008 | `` array object is missing or incorrect. | Correct the request and resubmit again. | | 16 | Array object is incorrect | 100 | 60008 | `` array object is missing or incorrect. | Correct the request and resubmit again. | | 17 | Timestamp value in request cannot be 'x' days before current date | 200 | 60012 | Timestamp value in request should be same as current date. | Correct the request and resubmit again. | | 18 | Timestamp value in request cannot be 'y' days after current date | 200 | 60012 | Timestamp value in request should be same as current date. | Correct the request and resubmit again. | | 19 | Duplicate Reference ID for the initiator and service combination | 200 | 60013 | Duplicate Reference ID `` for the initiator and service combination. | Correct the request and resubmit again. | | 20 | ICA Number does not exist in system | 200 | 60014 | ICA Number does not exist in system. | Correct the request and resubmit again. | | 21 | ICA Number is not active in system | 200 | 60015 | ICA Number is not active in system. | Correct the request and resubmit again. | | 22 | Request initiator is not authorized for this particular account range | 200 | 60018 | Request initiator is not authorized for this particular account range. | User cannot submit a fraud record as user is not provisioned for this particular account range. User can request provisioning for a particular account range through MCConnect. | | 23 | Fraud posted date in request cannot be before current date | 200 | 60027 | Fraud posted date cannot be before current date -1. | Correct the request and resubmit again. | | 24 | Fraud posted date in request cannot be after current date | 200 | 60028 | Fraud posted date cannot be after current date. | Correct the request and resubmit again. | | 25 | Fraud posted date in request cannot be before transaction date in request | 200 | 60029 | Fraud posted date cannot be before transaction date. | Correct the request and resubmit again. | | 26 | Account Device Type does not exist in system | 200 | 60033 | Account Device Type does not exist in system. | Correct the request and resubmit again. | | 27 | Account Device Type is not active in system | 200 | 60034 | Account Device Type is not active in system. | Correct the request and resubmit again. | | 28 | AVS Response Code does not exist in system | 200 | 60035 | AVS Response Code does not exist in system. | Correct the request and resubmit again. | | 29 | AVS Response Code is not active in system | 200 | 60036 | AVS Response Code is not active in system. | Correct the request and resubmit again. | | 30 | Auth Response Code does not exist in system | 200 | 60037 | Auth Response Code does not exist in system. | Correct the request and resubmit again. | | 31 | Fraud Type Code and Fraud Sub-type Code combination does not exist in system when both Fraud Type Code and Fraud Sub-type Code are provided in request | 200 | 60051 | Fraud Type Code and Fraud Sub-type Code combination does not exist in system. | Correct the request and resubmit again. | | 32 | Fraud Type Code and Fraud Sub-type Code combination is not active in system when both Fraud Type Code and Fraud Sub-type Code are provided in request | 200 | 60052 | Fraud Type Code and Fraud Sub-type Code combination is not active in system. | Correct the request and resubmit again. | | 33 | Cannot perform action. The record is already marked as confirmed. | 200 | 60058 | Cannot perform action. The record is already marked as confirmed. | Correct the request and resubmit again. | | 34 | Cannot perform action. The record is already marked as not-confirmed | 200 | 60059 | Cannot perform action. The record is already marked as not-confirmed | Correct the request and resubmit again. | | 35 | Invalid combination of transaction identifier in the request | 200 | 60130 | Invalid list of transaction identifier combination. | Correct the request and resubmit again. | | 36 | Suspected fraud cannot be changed on a transaction marked as Confirmed Fraud | 200 | 60134 | Suspected fraud cannot be changed on a transaction marked as Confirmed Fraud | Correct the request and resubmit again. | | 37 | ProviderId and Issuer/ Acquirer Product mapping does not exist in system | 200 | 60136 | ProviderId and Issuer/ Acquirer Product mapping does not exist in system | The user cannot submit a fraud record as product mapping is not present. User can request provisioning for a particular product through MCConnect. | | 38 | Transaction is not Declined in Data Warehouse, Acquirer Reference Number is mandatory | 200 | 66016 | Transaction is not Declined in Data Warehouse, Acquirer Reference Number is mandatory | Correct the request and resubmit again. | | 39 | Trying to confirm/unconfirmed the already confirmed record | 200 | 70004 | Suspected fraud cannot be submitted on a transaction marked as Confirmed Fraud | Correct the request and resubmit again. | | 40 | The suspected transaction cannot be confirmed by the acquirer entity. | 200 | 70010 | The suspected transaction cannot be confirmed by the acquirer entity. | Correct the request and resubmit again. | | 41 | Any unexpected error while processing the request | 200 | 90004 | Unexpected error while processing a request. | Correct the request and resubmit again. | ##### Suspected Fraud to Not Confirm {#suspected-fraud-to-not-confirm} | Sr No | Failure Scenario | Response Code | Reason Code | Description | Resolution Steps | |-------|---------------------------------------------------------------------------|---------------|-------------|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | FLD DB exception | 100 | 40100 | Fraud and Loss Database exception occurred. Record is errored out. | Retry after sometime. | | 2 | Constraint violation during DB operation | 100 | 41600 | Constraint violation exception occurred. Record is errored out. | Retry after sometime. | | 3 | Attribute is missing | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the request and resubmit again. | | 4 | Attribute is incorrect | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the request and resubmit again. | | 10 | Attribute value is missing | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the request and resubmit again. | | 11 | Incorrect datatype of attribute value | 100 | 60003 | `` incorrect datatype of attribute value. | Correct the request and resubmit again. | | 12 | Incorrect minimum length of attribute value | 100 | 60004 | `` attribute value length not in range. Minimum length: `

` and Maximum Length: ``. | Correct the request and resubmit again. | | 13 | Incorrect maximum length of attribute value | 100 | 60004 | `` attribute value length not in range. Minimum length: `

` and Maximum Length: ``. | Correct the request and resubmit again. | | 14 | Incorrect minimum value of attribute value | 100 | 60005 | `` attribute value not in range. Minimum value: `

` and Maximum Value: ``. | Correct the request and resubmit again. | | 15 | Incorrect maximum value of attribute value | 100 | 60005 | `` attribute value not in range. Minimum value: `

` and Maximum Value: ``. | Correct the request and resubmit again. | | 16 | Attribute value is not a defined ENUM value | 100 | 60006 | `` attribute value is not a defined ENUM value. | Correct the request and resubmit again. | | 17 | Attribute value does not follow the defined pattern (for example, regex) | 100 | 60007 | `` attribute value does not follow the defined pattern. | Correct the request and resubmit again. | | 18 | Array object is missing | 100 | 60008 | `` array object is missing or incorrect. | Correct the request and resubmit again. | | 19 | Array object is incorrect | 100 | 60008 | `` array object is missing or incorrect. | Correct the request and resubmit again. | | 20 | Timestamp value in request cannot be 'x' days before current date | 200 | 60012 | Timestamp value in request should be same as current date. | Correct the request and resubmit again. | | 21 | Timestamp value in request cannot be 'y' days after current date | 200 | 60012 | Timestamp value in request should be same as current date. | Correct the request and resubmit again. | | 22 | Duplicate Reference ID for the initiator and service combination | 200 | 60013 | Duplicate Reference ID `` for the initiator and service combination. | Correct the request and resubmit again. | | 23 | Cannot perform action. The record is already marked as confirmed. | 200 | 60058 | Cannot perform action. The record is already marked as confirmed. | Correct the request and resubmit again. | | 24 | Cannot perform action. The record is already marked as not-confirmed | 200 | 60059 | Cannot perform action. The record is already marked as not-confirmed | Correct the request and resubmit again. | | 25 | Not Fraud Type code does not exist in system | 200 | 60128 | Not Fraud Type code does not exist in system | Correct the request and resubmit again. | | 26 | Not Fraud Type code is not active in system | 200 | 60129 | Not Fraud Type code is not active in system | Correct the request and resubmit again. | | 27 | ProviderId and Issuer/ Acquirer Product mapping does not exist in system | 200 | 60136 | ProviderId and Issuer/ Acquirer Product mapping does not exist in system | The user cannot submit a fraud record as product mapping is not present. User can request provisioning for a particular product through MCConnect. | | 28 | The suspected transaction cannot be Not confirmed by the acquirer entity. | 200 | 60137 | The suspected transaction cannot be Not confirmed by the acquirer entity. | Correct the request and resubmit again. | | 29 | Trying to Unconfirm/confirm the already Unconfirmed record | 200 | 70005 | Suspected fraud cannot be submitted on a transaction marked as Confirmed Not Fraud | Correct the request and resubmit again. | | 30 | Any unexpected error while processing the request | 200 | 90004 | Unexpected error while processing a request. | Correct the request and resubmit again. | ##### Suspected Fraud to Delete {#suspected-fraud-to-delete} | Sr No | Failure Scenario | Response Code | Reason Code | Description | Resolution Steps | |-------|------------------------------------------------------------------------------------------------|---------------|-------------|------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | The record to be deleted could not be found. The record is rejected. Correct ACN and resubmit. | 200 | 21903 | The record to be deleted could not be found. The record is rejected. Correct ACN and resubmit. | Correct the request and resubmit again. | | 2 | FLD DB exception | 100 | 40100 | Fraud and Loss Database exception occurred. Record is errored out. | Retry after sometime. | | 3 | Constraint violation during DB operation | 100 | 41600 | Constraint violation exception occurred. Record is errored out. | Retry after sometime. | | 4 | Attribute is missing | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the request and resubmit again. | | 5 | Attribute is incorrect | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the request and resubmit again. | | 6 | Attribute value is missing | 100 | 60002 | `` attribute or attribute value is missing or incorrect. | Correct the request and resubmit again. | | 7 | Incorrect datatype of attribute value | 100 | 60003 | `` incorrect datatype of attribute value. | Correct the request and resubmit again. | | 8 | Incorrect minimum length of attribute value | 100 | 60004 | `` attribute value length not in range. Minimum length: `

` and Maximum Length: ``. | Correct the request and resubmit again. | | 9 | Incorrect maximum length of attribute value | 100 | 60004 | `` attribute value length not in range. Minimum length: `

` and Maximum Length: ``. | Correct the request and resubmit again. | | 10 | Incorrect minimum value of attribute value | 100 | 60005 | `` attribute value not in range. Minimum value: `

` and Maximum Value: ``. | Correct the request and resubmit again. | | 11 | Incorrect maximum value of attribute value | 100 | 60005 | `` attribute value not in range. Minimum value: `

` and Maximum Value: ``. | Correct the request and resubmit again. | | 12 | Attribute value is not a defined ENUM value | 100 | 60006 | `` attribute value is not a defined ENUM value. | Correct the request and resubmit again. | | 13 | Attribute value does not follow the defined pattern (for example, regex) | 100 | 60007 | `` attribute value does not follow the defined pattern. | Correct the request and resubmit again. | | 14 | Array object is missing | 100 | 60008 | `` array object is missing or incorrect. | Correct the request and resubmit again. | | 15 | Array object is incorrect | 100 | 60008 | `` array object is missing or incorrect. | Correct the request and resubmit again. | | 16 | Timestamp value in request cannot be 'x' days before current date | 200 | 60012 | Timestamp value in request should be same as current date. | Correct the request and resubmit again. | | 17 | Timestamp value in request cannot be 'y' days after current date | 200 | 60012 | Timestamp value in request should be same as current date. | Correct the request and resubmit again. | | 18 | Duplicate Reference ID for the initiator and service combination | 200 | 60013 | Duplicate Reference ID `` for the initiator and service combination. | Correct the request and resubmit again. | | 19 | Cannot perform action. The record is already marked as confirmed. | 200 | 60058 | Cannot perform action. The record is already marked as confirmed. | Correct the request and resubmit again. | | 20 | Cannot perform action. The record is already marked as not-confirmed | 200 | 60059 | Cannot perform action. The record is already marked as not-confirmed | Correct the request and resubmit again. | | 21 | ProviderId and Issuer/ Acquirer Product mapping does not exist in system | 200 | 60136 | ProviderId and Issuer/ Acquirer Product mapping does not exist in system | The user cannot submit a fraud record as product mapping is not present. User can request provisioning for a particular product through MCConnect. | | 22 | Issuer is not allowed to delete suspected transaction. | 200 | 60138 | Suspected transaction cannot be Deleted by the issuer entity. | Correct the request and resubmit again. | | 23 | Suspected fraud cannot be deleted on a transaction marked as Deleted. | 200 | 60139 | Suspected fraud cannot be deleted on a transaction marked as Deleted. | Correct the request and resubmit again. | | 24 | Transaction marked as suspected by the issuer only cannot be deleted | 200 | 70009 | Transaction marked as suspected by the issuer only cannot be deleted | Correct the request and resubmit again. | | 25 | Any unexpected error while processing the request | 200 | 90004 | Unexpected error while processing a request. | Correct the request and resubmit again. | ##### Suspected Fraud Status {#suspected-fraud-status} | Sr No | Failure Scenario | Response Code | Reason Code | Description | Resolution Steps | |-------|------------------------------------|---------------|-------------|------------------------------------|-----------------------------------------| | 1 | Record searched could not be found | 200 | 60127 | Record searched could not be found | Correct the request and resubmit again. |