openapi: 3.0.3 info: title: Mastercard Confirmed Fraud description: >- The Fraud and Loss Database (FLD) is the Mastercard_repository for fraud transactions, and it serves as the source of truth for fraud information within the enterprise. As mentioned below, this platform currently provides multiple channels for submission and management of fraud records. contact: name: API Support email: apisupport@mastercard.com url: https://developer.mastercard.com/support version: 1.3.06 servers: - url: https://api.mastercard.com/fld/confirmed-frauds description: Global Production server (uses live data) - url: https://api.mastercard.co.in/fld/confirmed-frauds description: India Production server (uses live data) - url: https://sandbox.api.mastercard.com/fld/confirmed-frauds description: Global Sandbox server (testing environment) - url: https://sandbox.api.mastercard.co.in/fld/confirmed-frauds description: India Sandbox server (testing environment) tags: - name: Confirmed Fraud Management - name: Confirmed Fraud Submission - name: Fraud - name: Ica - name: Issuer - name: Mastercard - name: States - name: Statuses paths: /mastercard-frauds: post: tags: - Confirmed Fraud Submission - Mastercard operationId: submitMastercardFraud description: >- This endpoint allows the initiator to add a new fraud record using minimal input parameters for Mastercard built transactions. To submit a transaction as fraud, a match has to be found in the Mastercard transaction data repository(Data Warehouse). summary: >- Add a New Fraud Record Using Minimal Input Parameters for Mastercard Built Transactions. x-mastercard-api-encrypted: true requestBody: $ref: '#/components/requestBodies/FraudMastercardRequest' responses: '200': $ref: '#/components/responses/FraudAdditionException' '201': $ref: '#/components/responses/FraudAddition' '202': $ref: '#/components/responses/FraudAddAccepted' '400': $ref: '#/components/responses/BadRequestError' '401': $ref: '#/components/responses/UnauthorizedError' '403': $ref: '#/components/responses/ForbiddenError' '429': $ref: '#/components/responses/RateLimitExceededError' x-microcks-operation: delay: 0 dispatcher: FALLBACK put: tags: - Confirmed Fraud Management - Mastercard operationId: updateMastercardFraud description: >- This endpoint allows the initiator to change an existing fraud record using minimal input parameters for Mastercard built transactions. The initiator can modify both successful and rejected fraud transactions and also modify transactions which are submitted via other channels such as GFT, file upload, and online. summary: >- Change an Existing Fraud Record Using Minimal Input Parameters for Mastercard Built Transactions. x-mastercard-api-encrypted: true requestBody: $ref: '#/components/requestBodies/FraudRequestChange' responses: '200': $ref: '#/components/responses/FraudDataChanged' '400': $ref: '#/components/responses/BadRequestError' '401': $ref: '#/components/responses/UnauthorizedError' '403': $ref: '#/components/responses/ForbiddenError' '429': $ref: '#/components/responses/RateLimitExceededError' x-microcks-operation: delay: 0 dispatcher: FALLBACK /issuer-frauds: post: tags: - Confirmed Fraud Submission - Issuer operationId: submitIssuerFraud description: >- This endpoint allows the initiator to add a new fraud record using complete input parameters for both Mastercard and Issuer built transactions. The transaction will be looked up in the Mastercard transaction data repository (Data Warehouse) and if a match is found, it is submitted as a Mastercard built fraud record. If no match is found, the transaction will be submitted as an Issuer built fraud record. summary: >- Add a New Fraud Record Using Complete Input Parameters for Both Mastercard and Issuer Built Transactions. x-mastercard-api-encrypted: true requestBody: $ref: '#/components/requestBodies/FraudIssuerRequest' responses: '200': $ref: '#/components/responses/FraudIssuerAdditionException' '201': $ref: '#/components/responses/FraudIssuerAddition' '400': $ref: '#/components/responses/BadRequestError' '401': $ref: '#/components/responses/UnauthorizedError' '403': $ref: '#/components/responses/ForbiddenError' '429': $ref: '#/components/responses/RateLimitExceededError' x-microcks-operation: delay: 0 dispatcher: FALLBACK put: tags: - Confirmed Fraud Management - Issuer operationId: updateIssuerFraud description: >- This endpoint allows the initiator to change an existing fraud record using complete input parameters for both Mastercard and Issuer built transactions. The initiator can modify both successful and rejected fraud transactions and also modify transactions which are submitted via other channels such as GFT, file upload, and online. summary: >- Change an Existing Fraud Record Using Complete Input Parameters for Both Mastercard and Issuer Built Transactions. x-mastercard-api-encrypted: true requestBody: $ref: '#/components/requestBodies/FraudIssuerRequestChange' responses: '200': $ref: '#/components/responses/FraudIssuerDataChanged' '400': $ref: '#/components/responses/BadRequestError' '401': $ref: '#/components/responses/UnauthorizedError' '403': $ref: '#/components/responses/ForbiddenError' '429': $ref: '#/components/responses/RateLimitExceededError' x-microcks-operation: delay: 0 dispatcher: FALLBACK /fraud-states: put: tags: - Fraud - States operationId: fraudState description: >- This endpoint allows the initiator to delete an existing fraud record or confirm a suspended fraud record for both Mastercard and Issuer built transactions. Operation type FDD will delete existing fraud records from FLD, irrespective of the fraud state i.e., success / rejected / suspended. And operation type FDE will confirm an existing fraud record which was suspended due to reasons such as potential duplicates, billing variance, suspicious amounts, etc. summary: >- Delete an Existing Fraud Record or Confirm a Suspended Fraud Record for Both Mastercard and Issuer Built Transactions. requestBody: $ref: '#/components/requestBodies/FraudStateRequest' responses: '200': $ref: '#/components/responses/FraudStateChanged' '400': $ref: '#/components/responses/BadRequestError' '401': $ref: '#/components/responses/UnauthorizedError' '403': $ref: '#/components/responses/ForbiddenError' '429': $ref: '#/components/responses/RateLimitExceededError' x-microcks-operation: delay: 0 dispatcher: FALLBACK /fraud-statuses/icas/{ica}: get: tags: - Fraud - Ica - Statuses operationId: fraudRequestStatus description: >- This endpoint allows the initiator to get the status of an existing fraud record using combination of ICA, Ref ID & ACN, for both Mastercard and Issuer built transactions. The initiator can get status of fraud transaction submitted via any channel GFT, File upload, Online & API. summary: >- Get Status of an Existing Fraud Record for Both Mastercard and Issuer Built Transactions. parameters: - $ref: '#/components/parameters/ICA' - $ref: '#/components/parameters/Ref_Id' - $ref: '#/components/parameters/ACN' responses: '200': $ref: '#/components/responses/FraudStatusResponse' '400': $ref: '#/components/responses/FraudStatusBadRequestError' '429': $ref: '#/components/responses/RateLimitExceededError' x-microcks-operation: delay: 0 dispatcher: FALLBACK components: parameters: ICA: name: ica in: path required: true schema: type: string minLength: 3 maxLength: 7 example: '1076' description: >- Refers to the ICA of the fraud record which needs to be searched for its status. It is mandatory parameter along with Ref ID or ACN.. Ref_Id: name: ref_id in: query schema: type: string minLength: 36 maxLength: 36 example: ecb2d942-eabd-42b6-87fd-69c19692bdc6 description: >- Refers to the reference ID of the API call which was used to submit fraud record. This is optional parameter if ACN is present in the request. ACN: name: acn in: query schema: type: string minLength: 15 maxLength: 15 example: '418142102142002' description: >- Refers to the ACN of the fraud record whose status is to be fetched. This is optional parameter for record submitted through APIs. schemas: APIDataElement: required: - refId - timestamp - icaNumber type: object properties: refId: description: >- Unique identification generated by the transaction originator using UUID logic to unambiguously link a request and response message. type: string minLength: 36 maxLength: 36 example: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: type: string description: >- Timestamp of the request initiation by the originator in the format 'YYYY-MM-DDThh:mm:ss:mmm+hh:mm'. The value of '+hh:mm' portion should always be '-05:00' or '-06:00' reflecting CST time. minLength: 25 maxLength: 25 example: '2021-02-02T02:34:37-06:00' icaNumber: description: >- ICA number of the Issuer or Acquirer initiating the fraud submission request. type: string minLength: 3 maxLength: 7 example: '1076' issuerSCAExemption: description: >- Issuer SCA (Strong Customer Authentication) Exemption value. Please refer to [Table 16](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-16-issuer-sca-strong-customer-authentication-exemption) for possible values. type: string minLength: 1 maxLength: 2 example: '09' MastercardFraud: allOf: - $ref: '#/components/schemas/APIDataElement' - type: object required: - providerId - transactionIdentifiers - cardNumber - transactionAmount - transactionDate - fraudTypeCode - accountDeviceType - cardInPossession properties: providerId: $ref: '#/components/schemas/SafeFraudProvider' transactionIdentifiers: type: array items: $ref: '#/components/schemas/TransactionIdentifier' cardNumber: description: >- Cardholder account number used in the fraudulent transaction. Card number to be verified through Luhn's algorithm. type: string minLength: 12 maxLength: 19 example: '5505135664572870000' transactionAmount: description: >- Transaction amount at the merchant location (without any decimals). type: string minLength: 1 maxLength: 12 example: '10350' transactionDate: description: >- Local date at the merchant location when the transaction occurred. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210115' fraudPostedDate: description: >- Date on which the fraud is posted in FLD by the originator. Format is 'YYYYMMDD'.It is optional field, if not provided FLD System will save it as System date. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210120' fraudTypeCode: description: >- Code identifying the reason the originator submitted the transaction as fraud in FLD. Please refer to [Table 1](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-1-fraud-type-codes) for possible values. type: string minLength: 2 maxLength: 2 example: '04' fraudSubTypeCode: description: >- Code to further identify the reason that the originator submitted the transaction as a fraud in FLD. This attribute is mandatory for the Issuer but optional for the Acquirer. Please refer to [Table 2](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-2-fraud-sub-type-codes) for possible values. type: string minLength: 1 maxLength: 1 example: U accountDeviceType: description: >- Indicates if the account uses a magnetic stripe, chip, pin, contactless or any combination thereof. Please refer to [Table 3](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-3-account-device-type-codes) for possible values. type: string minLength: 1 maxLength: 1 example: '1' cardholderReportedDate: description: >- Date on which the cardholder had reported the fraud. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210118' cardInPossession: description: >- 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' (for Unknown). type: string minLength: 1 maxLength: 1 example: 'N' avsResponseCode: description: >- The Address Verification Service response code in the Authorization Request Response. Please refer to [Table 4](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-4-avs-response-codes) for possible values. type: string minLength: 1 maxLength: 1 example: U authResponseCode: description: >- Indicates the result of the authorization request. Please refer to [Table 5](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-5-authorization-response-codes) for possible values. type: string minLength: 2 maxLength: 2 example: '01' memo: description: >- Brief description by the originator providing some comment supporting the action. type: string minLength: 1 maxLength: 1000 example: This is a sample FDA minimal request. IssuerFraud: allOf: - $ref: '#/components/schemas/APIDataElement' - type: object required: - acquirerId - transactionIdentifiers - cardNumber - fraudTypeCode - fraudSubTypeCode - cardProductCode - transactionDate - settlementDate - transactionAmount - transactionCurrencyCode - billingAmount - billingCurrencyCode - merchantId - merchantName - merchantCity - merchantCountryCode - merchantPostalCode - merchantCategoryCode - terminalAttendanceIndicator - terminalId - terminalOperatingEnvironment - cardholderPresenceIndicator - cardPresenceIndicator - cardInPossession - catLevelIndicator - terminalCapabilityIndicator - posEntryMode - cvcInvalidIndicator - avsResponseCode - authResponseCode - accountDeviceType properties: acquirerId: description: Acquirer identification number (ICA number) for the transaction. type: string minLength: 3 maxLength: 7 example: '5450' transactionIdentifiers: type: array items: $ref: '#/components/schemas/TransactionIdentifier' cardNumber: description: >- Cardholder account number used in the fraudulent transaction. Card number to be verified through Luhn's algorithm. type: string minLength: 12 maxLength: 19 example: '5505135664572870000' fraudTypeCode: description: >- Code identifying the reason the originator submitted the transaction as fraud in FLD. Please refer to [Table 1](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-1-fraud-type-codes) for possible values. type: string minLength: 2 maxLength: 2 example: '04' fraudSubTypeCode: description: >- Code to further identify the reason that the originator submitted the transaction as fraud in FLD. Please refer to [Table 2](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-2-fraud-sub-type-codes) for possible values. type: string minLength: 1 maxLength: 1 example: U cardProductCode: description: >- Value identifying the type of card used in the transaction. Please refer to [Card Type Codes table](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-2/) for possible values. type: string minLength: 3 maxLength: 3 example: MSI transactionDate: description: >- Local date at the merchant location when the transaction occurred. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210115' settlementDate: description: Settlement date of transaction reported. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210116' fraudPostedDate: description: >- Date on which the fraud is posted in FLD by the originator. Format is 'YYYYMMDD'. It is optional field, if not provided FLD System will save it as System date. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210120' cardholderReportedDate: description: >- Date on which the cardholder had reported the fraud. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210118' transactionAmount: description: >- Transaction amount at the merchant location (without any decimals). type: string minLength: 1 maxLength: 12 example: '10350' transactionCurrencyCode: description: >- Code defining the currency used for the transaction amount. The code should be part of the numeric ISO Standard Currency Codes list. type: string minLength: 3 maxLength: 3 example: '826' billingAmount: description: >- Amount appearing on the cardholder statement in the cardholder's billing currency (without any decimals). type: string minLength: 1 maxLength: 12 example: '10350' billingCurrencyCode: description: >- Code defining the currency used for the billing amount. The code should be part of the numeric ISO Standard Currency Codes list. type: string minLength: 3 maxLength: 3 example: '826' merchantId: description: >- Card acceptor / merchant's unique identification number, assigned by the Acquirer. type: string minLength: 1 maxLength: 15 example: A42E51982100100 merchantName: description: Name of the card acceptor. type: string minLength: 1 maxLength: 22 example: BANKNEWPORT merchantCity: description: City in which the merchant is located. type: string minLength: 1 maxLength: 13 example: PHOENIX merchantStateProvinceCode: description: >- If the card acceptor/merchant is in the US, the state in which it is located. type: string minLength: 2 maxLength: 3 example: AZ merchantCountryCode: description: Indicates the country in which the merchant is located. type: string minLength: 3 maxLength: 3 example: USA merchantPostalCode: description: Postal code at the merchant location. type: string minLength: 1 maxLength: 10 example: '85001' merchantCategoryCode: description: Card acceptor business code / merchant category code. type: string minLength: 4 maxLength: 4 example: '6011' terminalAttendanceIndicator: description: >- Indicates if the card acceptor was attending the terminal at the time of transaction. Please refer to [Table 12](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-12-terminal-attendance-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: '1' terminalId: description: >- Unique code identifying a terminal at the card acceptor (merchant) location. type: string minLength: 1 maxLength: 8 example: 5055D305 terminalOperatingEnvironment: description: >- Indicates whether the card acceptor is attending the terminal and the location of the terminal. Please refer to [Table 13](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-13-terminal-operating-environment) for possible values. type: string minLength: 1 maxLength: 1 example: '4' cardholderPresenceIndicator: description: >- Indicates whether the cardholder is present at the point of service and explains the condition if the cardholder is not present. Please refer to [Table 6](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-6-cardholder-presence-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: '5' cardPresenceIndicator: description: >- Indicates whether the card was present at the point of service. Please refer to [Table 7](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-7-card-present-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: '1' cardInPossession: description: >- 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' (for Unknown). type: string minLength: 1 maxLength: 1 example: 'N' catLevelIndicator: description: >- Indicates whether the cardholder activated the terminal with the use of the card and the CAT security level. Please refer to [Table 9](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-9-cardholder-activated-terminal-level-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: '1' terminalCapabilityIndicator: description: >- Indicates the terminal capability for transferring the data on the card into the terminal. Please refer to [Table 14](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-14-terminal-input-capability-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: '5' electronicCommerceIndicator: description: >- Indicates the security protocol and authentication of the transaction. Mandatory if CAT Level = 6. Please refer to [Table 10](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-10-electronic-commerce-security-level-indicator) for possible values. type: string minLength: 1 maxLength: 2 example: '24' posEntryMode: description: >- Indicates how the PAN was entered at the terminal. Please refer to [Table 8](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-8-pos-entry-mode) for possible values. type: string minLength: 2 maxLength: 2 example: '05' cvcInvalidIndicator: description: >- Indicates whether the CVC was valid when authorization was attempted. Please refer to [Table 15](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-15-card-validation-code-cvc-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: M avsResponseCode: description: >- The Address Verification Service response code in the Authorization Request Response. Please refer to [Table 4](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-4-avs-response-codes) for possible values. type: string minLength: 1 maxLength: 1 example: U authResponseCode: description: >- Indicates the result of the authorization request. Please refer to [Table 5](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-5-authorization-response-codes) for possible values. type: string minLength: 2 maxLength: 2 example: '01' secureCode: description: >- Indicates the type of security processing used for the PIN data. Mandatory if ecommerce indicator = 21 or 22. Please refer to [Table 11](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-11-secure-code) for possible values. type: string minLength: 1 maxLength: 1 example: '9' accountDeviceType: description: >- Indicates if the account uses a magnetic stripe, chip, pin, contactless or any combination thereof. Please refer to [Table 3](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-3-account-device-type-codes) for possible values. type: string minLength: 1 maxLength: 1 example: '1' acquirerRoutingTransitNumber: description: >- The identification number of the merchant's acquirer. Applicable for a single message transaction. Mandatory if an acquirer ICA value is '9999999'. type: string minLength: 10 maxLength: 10 example: '1790018674' issuerRoutingTransitNumber: description: >- The identification number of the issuing institution. Applicable for a single message transaction. Mandatory if an issuer ICA value is '9999999'. type: string minLength: 10 maxLength: 10 example: '1231380159' transactionIndicator: description: >- Indicates whether the transaction was initiated by the cardholder or the merchant as well as providing more detail as to the type of stored credentials being used for the transaction. Please refer to [Table 17](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-17-cardholder-merchant-initiated-transaction-indicator) for possible values. type: string minLength: 4 maxLength: 4 example: M101 memo: description: >- Brief description by the originator providing some comment supporting the action. type: string minLength: 1 maxLength: 1000 example: This is a sample FDA complete request. UpdatedMastercardFraud: allOf: - $ref: '#/components/schemas/APIDataElement' - type: object required: - providerId - auditControlNumber properties: providerId: $ref: '#/components/schemas/SafeFraudProvider' auditControlNumber: description: >- 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. type: string minLength: 15 maxLength: 15 example: '418142102142002' fraudPostedDate: description: >- Date on which the fraud is posted in FLD by the originator. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210120' fraudTypeCode: description: >- Code identifying the reason the originator submitted the transaction as fraud in FLD. Please refer to [Table 1](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-1-fraud-type-codes) for possible values. type: string minLength: 2 maxLength: 2 example: '04' fraudSubTypeCode: description: >- 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. Please refer to [Table 2](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-2-fraud-sub-type-codes) for possible values. type: string minLength: 1 maxLength: 1 example: U accountDeviceType: description: >- Indicates if the account uses a magnetic stripe, chip, pin, contactless or any combination thereof. Please refer to [Table 3](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-3-account-device-type-codes) for possible values. type: string minLength: 1 maxLength: 1 example: '1' cardholderReportedDate: description: >- Date on which the cardholder had reported the fraud. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210118' cardInPossession: description: >- 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' (for Unknown). type: string minLength: 1 maxLength: 1 example: 'N' memo: description: >- Brief description by the originator providing some comment supporting the action. type: string minLength: 1 maxLength: 1000 example: This is a sample FDC minimal request. UpdatedIssuerFraud: allOf: - $ref: '#/components/schemas/APIDataElement' - type: object required: - auditControlNumber properties: acquirerId: description: Acquirer identification number (ICA number) for the transaction. type: string minLength: 3 maxLength: 7 example: '5450' auditControlNumber: description: >- 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. type: string minLength: 15 maxLength: 15 example: '418142102142002' cardNumber: description: >- Cardholder account number used in the fraudulent transaction. Card number to be verified through Luhn's algorithm. type: string minLength: 12 maxLength: 19 example: '5505135664572870000' fraudTypeCode: description: >- Code identifying the reason the originator submitted the transaction as fraud in FLD. Please refer to [Table 1](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-1-fraud-type-codes) for possible values. type: string minLength: 2 maxLength: 2 example: '04' fraudSubTypeCode: description: >- Code to further identify the reason that the originator submitted the transaction as fraud in FLD. Please refer to [Table 2](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-2-fraud-sub-type-codes) for possible values. type: string minLength: 1 maxLength: 1 example: U cardProductCode: description: >- Value identifying the type of card used in the transaction. Please refer to [Card Type Codes table](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-2/) for possible values. type: string minLength: 3 maxLength: 3 example: MSI transactionDate: description: >- Local date at the merchant location when the transaction occurred. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210115' settlementDate: description: Settlement date of transaction reported. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210116' fraudPostedDate: description: >- Date on which the fraud is posted in FLD by the originator. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210120' cardholderReportedDate: description: >- Date on which the cardholder had reported the fraud. Format is 'YYYYMMDD'. type: string minLength: 8 maxLength: 8 pattern: ^\d{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$ example: '20210118' transactionAmount: description: >- Transaction amount at the merchant location (without any decimals). type: string minLength: 1 maxLength: 12 example: '10350' transactionCurrencyCode: description: >- Code defining the currency used for the transaction amount. The code should be part of the numeric ISO Standard Currency Codes list. type: string minLength: 3 maxLength: 3 example: '826' billingAmount: description: >- Amount appearing on the cardholder statement in the cardholder's billing currency (without any decimals). type: string minLength: 1 maxLength: 12 example: '10350' billingCurrencyCode: description: >- Code defining the currency used for the billing amount. The code should be part of the numeric ISO Standard Currency Codes list. type: string minLength: 3 maxLength: 3 example: '826' merchantId: description: >- Card acceptor / merchant's unique identification number, assigned by the Acquirer. type: string minLength: 1 maxLength: 15 example: A42E51982100100 merchantName: description: Name of the card acceptor. type: string minLength: 1 maxLength: 22 example: BANKNEWPORT merchantCity: description: City in which the merchant is located. type: string minLength: 1 maxLength: 13 example: PHOENIX merchantStateProvinceCode: description: >- If the card acceptor / merchant is in the US, the state in which it is located. type: string minLength: 2 maxLength: 3 example: AZ merchantCountryCode: description: Indicates the country in which the merchant is located. type: string minLength: 3 maxLength: 3 example: USA merchantPostalCode: description: Postal code at the merchant location. type: string minLength: 1 maxLength: 10 example: '85001' merchantCategoryCode: description: Card acceptor business code / merchant category code. type: string minLength: 4 maxLength: 4 example: '6011' terminalAttendanceIndicator: description: >- Indicates if the card acceptor was attending the terminal at the time of transaction. Please refer to [Table 12](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-12-terminal-attendance-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: '1' terminalId: description: >- Unique code identifying a terminal at the card acceptor (merchant) location. type: string minLength: 1 maxLength: 8 example: 5055D305 terminalOperatingEnvironment: description: >- Indicates whether the card acceptor is attending the terminal and the location of the terminal. Please refer to [Table 13](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-13-terminal-operating-environment) for possible values. type: string minLength: 1 maxLength: 1 example: '4' cardholderPresenceIndicator: description: >- Indicates whether the cardholder is present at the point of service and explains the condition if the cardholder is not present. Please refer to [Table 6](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-6-cardholder-presence-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: '5' cardPresenceIndicator: description: >- Indicates whether the card was present at the point of service. Please refer to [Table 7](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-7-card-present-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: '1' cardInPossession: description: >- 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' (for Unknown). type: string minLength: 1 maxLength: 1 example: 'N' catLevelIndicator: description: >- Indicates whether the cardholder activated the terminal with the use of the card and the CAT security level. Please refer to [Table 9](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-9-cardholder-activated-terminal-level-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: '1' terminalCapabilityIndicator: description: >- Indicates the terminal capability for transferring the data on the card into the terminal. Please refer to [Table 14](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-14-terminal-input-capability-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: '5' electronicCommerceIndicator: description: >- Indicates the security protocol and authentication of the transaction. Mandatory if CAT Level = 6. Please refer to [Table 10](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-10-electronic-commerce-security-level-indicator) for possible values. type: string minLength: 1 maxLength: 2 example: '24' posEntryMode: description: >- Indicates how the PAN was entered at the terminal. Please refer to [Table 8](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-8-pos-entry-mode) for possible values. type: string minLength: 2 maxLength: 2 example: '05' cvcInvalidIndicator: description: >- Indicates whether the CVC was valid when authorization was attempted. Please refer to [Table 15](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-15-card-validation-code-cvc-indicator) for possible values. type: string minLength: 1 maxLength: 1 example: M avsResponseCode: description: >- The Address Verification Service response code in the Authorization Request Response. Please refer to [Table 4](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-4-avs-response-codes) for possible values. type: string minLength: 1 maxLength: 1 example: U authResponseCode: description: >- Indicates the result of the authorization request. Please refer to [Table 5](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-5-authorization-response-codes) for possible values. type: string minLength: 2 maxLength: 2 example: '01' secureCode: description: >- Indicates the type of security processing used for the PIN data. Mandatory if ecommerce indicator = 21 or 22. Please refer to [Table 11](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-11-secure-code) for possible values. type: string minLength: 1 maxLength: 1 example: '9' accountDeviceType: description: >- Indicates if the account uses a magnetic stripe, chip, pin, contactless or any combination thereof. Please refer to [Table 3](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-3-account-device-type-codes) for possible values. type: string minLength: 1 maxLength: 1 example: '1' transactionIndicator: description: >- Indicates whether the transaction was initiated by the cardholder or the merchant as well as providing more detail as to the type of stored credentials being used for the transaction. Please refer to [Table 17](https://developer.mastercard.com/fld-fraud-submission/documentation/parameters/annexure-1/#table-17-cardholder-merchant-initiated-transaction-indicator) for possible values. type: string minLength: 4 maxLength: 4 example: M101 memo: description: >- Brief description by the originator providing some comment supporting the action. type: string minLength: 1 maxLength: 1000 example: This is a sample FDC complete request. FraudDeleteAndConfirm: allOf: - $ref: '#/components/schemas/APIDataElement' - type: object required: - providerId - auditControlNumber - operationType properties: providerId: $ref: '#/components/schemas/SafeFraudProvider' operationType: $ref: '#/components/schemas/FraudState' auditControlNumber: description: >- 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. type: string minLength: 15 maxLength: 15 example: '418142102142002' memo: description: >- Brief description by the originator providing some comment supporting the action. type: string minLength: 1 maxLength: 1000 example: This is a sample FDD / FDE request. FraudBase: type: object properties: refId: description: >- Unique identification generated by the transaction originator using UUID logic to unambiguously link a request and response message. example: ecb2d942-eabd-42b6-87fd-69c19692bdc6 maxLength: 36 minLength: 36 type: string timestamp: description: >- Timestamp of the request initiation by the originator in the format 'YYYY-MM-DDThh:mm:ss:mmm+hh:mm'. The value of '+hh:mm' portion should always be '-05:00' or '-06:00' reflecting CST time. example: '2022-05-24T20:34:37+6:00' maxLength: 25 minLength: 25 type: string icaNumber: description: >- ICA number of the Issuer or Acquirer or Provider initiating the fraud submission request. example: '1076' maxLength: 7 minLength: 3 type: string Fraud: allOf: - $ref: '#/components/schemas/FraudBase' - type: object required: - responseCode - responseMessage properties: responseCode: description: >- 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. type: string minLength: 3 maxLength: 3 example: '000' responseMessage: description: >- Transaction response description corresponding to the response code. type: string minLength: 1 maxLength: 100 example: Success icaNumber: description: >- 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. type: string minLength: 3 maxLength: 7 example: '1076' auditControlNumber: description: >- 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. type: string minLength: 15 maxLength: 15 example: '418142102142002' duplicateAuditControlNumbers: description: >- List of existing Audit Control Number which matches the request submitted for Mastercard-built or Issuer-built. This attribute will appear in case of the records already present while trying to submit or update the existing record. type: array items: type: string minItems: 1 maxItems: 5 uniqueItems: true matchLevelIndicator: description: >- Indicates if it is a Mastercard-built or Issuer-built record. Possible values are 'M' for Mastercard built record and 'I' for Issuer built record. This attribute will be absent if the request is not processed by FLD application. type: string minLength: 1 maxLength: 1 example: M financialTransactionIndicator: description: >- 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 transactions (having a clearing record) and 'DECLINED' for declined auth transactions (without a clearing record). This attribute will be absent if the request is not processed by FLD application. type: string minLength: 1 maxLength: 20 example: DECLINED authorizationResponse: description: >- Provides the 'Auth Response Code' and 'Auth Response Code Description' combination if 'Financial Transaction Indicator' value is 'DECLINED'. This attribute will be absent for all other scenarios. type: string minLength: 1 maxLength: 200 example: 05 - Do not honor previousStatus: description: >- Previous status of the transaction in terms of an FDC, FDD and FDE event. type: string minLength: 1 maxLength: 50 example: CONFIRMED-REJECTED currentStatus: description: >- Current status of the transaction in terms of an FDA, FDC, FDD and FDE event. type: string minLength: 1 maxLength: 50 example: CONFIRMED-SUCCESS channel: description: Fraud request submission fld channel name. type: string minLength: 1 maxLength: 50 example: Online errorDetails: $ref: '#/components/schemas/ErrorWrapper' SafeFraudProvider: description: >- Indicates the originator of the request. Value 10 is for Issuer and 20 for Acquirer. type: string example: '10' pattern: ^(10|20) minLength: 2 maxLength: 2 CfcIndicator: description: >- Flag to indicate a single or dual message transaction. Possible values are - - 'ARN' for Acquirer Reference Number - 'BRN' for Banknet Reference Number - 'TRC' for Trace ID - 'SER' for Serial ID type: string enum: - ARN - BRN - TRC - SER FraudState: description: >- Indicates the type of operation to be performed for the given audit control number. The value FDD is to indicate delete operation and FDE is to indicate confirm operation. type: string minLength: 1 maxLength: 50 enum: - FDD - FDE TransactionIdentifier: description: Transaction Identifier containing CFC Indicator the key and value pair. type: object properties: cfcKey: $ref: '#/components/schemas/CfcIndicator' cfcValue: description: >- Actual value depending on the 'CFC Indicator' subject to the following validations 1. For ARN, Min Length is 23, Max Length is 23 and Data Type is N. 2. For BRN, Min Length is 6, Max Length is 9 and Data Type is AN. 3. For TRC, Min Length is 6, Max Length is 6 and Data Type is N. 4. For SER, Min Length is 9, Max Length is 9 and Data Type is N. type: string minLength: 6 maxLength: 23 example: '0111111111999999999999' Error: title: ErrorMessage required: - Description - ReasonCode type: object properties: Source: type: string description: The application or component that generated this error. minLength: 3 maxLength: 50 example: FLD ReasonCode: type: string description: >- Reason code is a unique constant identifying the error case encountered during request processing. minLength: 5 maxLength: 100 example: VALIDATION_ERROR Description: type: string description: Human-readable short description of the reasonCode minLength: 10 maxLength: 250 example: Reference Id is not provided Details: type: string description: >- Optional detailed description provides information about data received and calculated during request processing. This helps the user to diagnose errors. minLength: 0 maxLength: 1000 example: This is mandatory field while requesting for fraud submission. Recoverable: type: boolean description: >- Recoverable flag indicates whether this error is always returned for this request, or retrying could change the outcome. For example, 'true' or 'false'. example: false Errors: title: Errors required: - Error type: object properties: Error: type: array description: Errors array wrapped in an error object items: $ref: '#/components/schemas/Error' example: [] ErrorWrapper: description: >- Object containing the list of 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. title: Error Response required: - Errors type: object properties: Errors: $ref: '#/components/schemas/Errors' requestBodies: FraudMastercardRequest: description: >- Add a new fraud record using minimal input parameters for Mastercard built transactions. This endpoint uses [payload encryption](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/). Please refer to the [reference application](https://developer.mastercard.com/fld-fraud-submission/documentation/api-reference/) page for implementation details. required: true content: application/json: schema: $ref: '#/components/schemas/MastercardFraud' examples: MastercardFraudExample: $ref: '#/components/examples/MastercardFraudExample' FraudIssuerRequest: description: >- Add a new fraud record using complete input parameters for both Mastercard and Issuer built transactions. This endpoint uses [payload encryption](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/). Please refer to the [reference application](https://developer.mastercard.com/fld-fraud-submission/documentation/api-reference/) page for implementation details. required: true content: application/json: schema: $ref: '#/components/schemas/IssuerFraud' examples: IssuerFraudExample: $ref: '#/components/examples/IssuerFraudExample' FraudRequestChange: description: >- Change an existing fraud record using minimal input parameters for Mastercard built transactions. This endpoint uses [ payload encryption](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/). Please refer to the [reference application](https://developer.mastercard.com/fld-fraud-submission/documentation/api-reference/) page for implementation details. required: true content: application/json: schema: $ref: '#/components/schemas/UpdatedMastercardFraud' examples: FraudChangeExample: $ref: '#/components/examples/FraudChangeExample' FraudIssuerRequestChange: description: >- Change an existing fraud record using complete input parameters for both Mastercard and Issuer built transactions. [Mastercard payload encryption](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/). Please refer to the [reference application](https://developer.mastercard.com/fld-fraud-submission/documentation/api-reference/) page for implementation details. required: true content: application/json: schema: $ref: '#/components/schemas/UpdatedIssuerFraud' examples: FraudIssuerChangeExample: $ref: '#/components/examples/FraudIssuerChangeExample' FraudStateRequest: description: >- Delete an existing fraud record or confirm a suspended fraud record for both Mastercard and Issuer built transactions. required: true content: application/json: schema: $ref: '#/components/schemas/FraudDeleteAndConfirm' examples: FraudConfirmExample: $ref: '#/components/examples/FraudConfirmExample' FraudDeleteExample: $ref: '#/components/examples/FraudDeleteExample' responses: FraudAddition: description: Fraud submitted successfully. headers: Location: schema: type: string description: Refers to the created resource location. content: application/json: schema: $ref: '#/components/schemas/Fraud' examples: FraudAdditionExample: $ref: '#/components/examples/FraudAdditionExample' FraudAdditionException: description: Exception occurred while Fraud submission. content: application/json: schema: $ref: '#/components/schemas/Fraud' examples: FraudAdditionRejectExample: $ref: '#/components/examples/FraudAdditionRejectExample' FraudAdditionSuspendExample: $ref: '#/components/examples/FraudAdditionSuspendExample' FraudIssuerAddition: description: Fraud submitted successfully. headers: Location: schema: type: string description: Refers to the created resource location. content: application/json: schema: $ref: '#/components/schemas/Fraud' examples: FraudAdditionExample: $ref: '#/components/examples/FraudIssuerAdditionExample' FraudIssuerAdditionException: description: Exception occurred while Fraud submission. content: application/json: schema: $ref: '#/components/schemas/Fraud' examples: FraudAdditionRejectExample: $ref: '#/components/examples/FraudAdditionRejectExample' FraudAdditionSuspendExample: $ref: '#/components/examples/FraudIssuerAdditionSuspendExample' FraudAddAccepted: description: Fraud submission accepted successfully. headers: Location: schema: type: string description: Refers to the created resource location. content: application/json: schema: $ref: '#/components/schemas/Fraud' examples: FraudAddAcceptedExample: $ref: '#/components/examples/FraudAddAcceptedExample' FraudDataChanged: description: Fraud data changed successfully. content: application/json: schema: $ref: '#/components/schemas/Fraud' examples: FraudDataChanged: $ref: '#/components/examples/FraudDataChanged' FraudDataChangedError: $ref: '#/components/examples/FraudDataChangedError' FraudIssuerDataChanged: description: Fraud data changed successfully. content: application/json: schema: $ref: '#/components/schemas/Fraud' examples: FraudDataChanged: $ref: '#/components/examples/FraudIssuerDataChanged' FraudDataChangedError: $ref: '#/components/examples/FraudDataChangedError' FraudStateChanged: description: Fraud data changed successfully. content: application/json: schema: $ref: '#/components/schemas/Fraud' examples: FraudDataDeleted: $ref: '#/components/examples/FraudDataDeleted' FraudDataDeleteIcaNotAuthorize: $ref: '#/components/examples/FraudDataDeleteIcaNotAuthorize' FraudDataConfirmed: $ref: '#/components/examples/FraudDataConfirmed' FraudDataConfirmedTxnDateOlder: $ref: '#/components/examples/FraudDataConfirmedTxnDateOlder' FraudStatusResponse: description: Fraud request status in the system. content: application/json: schema: $ref: '#/components/schemas/Fraud' examples: FraudStatusConfirmed: $ref: '#/components/examples/FraudStatusConfirmed' FraudStatusSuspended: $ref: '#/components/examples/FraudStatusSuspended' FraudStatusDeleted: $ref: '#/components/examples/FraudStatusDeleted' FraudStatusRejected: $ref: '#/components/examples/FraudStatusRejected' FraudStatusNoRecordExample: $ref: '#/components/examples/FraudStatusNoRecordExample' FraudStatusNoParamRefIdAcnExample: $ref: '#/components/examples/FraudStatusNoParamRefIdAcnExample' FraudStatusBadRequestError: description: Something was wrong with the request. content: application/json: schema: $ref: '#/components/schemas/ErrorWrapper' examples: BadRequestInvalidIca: $ref: '#/components/examples/BadRequestInvalidIca' BadRequestInvalidRefId: $ref: '#/components/examples/BadRequestInvalidRefId' BadRequestInvalidACN: $ref: '#/components/examples/BadRequestInvalidACN' BadRequestError: description: Something was wrong with the request. content: application/json: schema: $ref: '#/components/schemas/ErrorWrapper' examples: BadRequestRefIdMissing: $ref: '#/components/examples/BadRequestRefIdMissing' UnauthorizedError: description: Unauthorized request. content: application/json: schema: $ref: '#/components/schemas/ErrorWrapper' examples: UnauthorizedExample: $ref: '#/components/examples/UnauthorizedExample' ForbiddenError: description: Consent not given. content: application/json: schema: $ref: '#/components/schemas/ErrorWrapper' examples: ForbiddenExample: $ref: '#/components/examples/ForbiddenExample' RateLimitExceededError: description: Too Many Requests. content: application/json: schema: $ref: '#/components/schemas/ErrorWrapper' examples: RateLimitExceededExample: $ref: '#/components/examples/RateLimitExceededExample' examples: MastercardFraudExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:37-06:00' icaNumber: '1076' providerId: '10' transactionIdentifiers: - cfcKey: ARN cfcValue: '0712141161891099999900' - cfcKey: BRN cfcValue: 999RRR cardNumber: '5505135664572870008' transactionAmount: '5505' transactionDate: '20200713' fraudPostedDate: '20210316' fraudTypeCode: '01' fraudSubTypeCode: 'N' accountDeviceType: '1' cardholderReportedDate: '20210314' cardInPossession: 'Y' avsResponseCode: U authResponseCode: '00' memo: This is a sample FDA minimal request. issuerSCAExemption: '09' IssuerFraudExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:37-06:00' icaNumber: '1076' transactionIdentifiers: - cfcKey: ARN cfcValue: '01111114320000000032087' - cfcKey: BRN cfcValue: 543REF cardNumber: '5587450000000008074' acquirerId: '2742' fraudTypeCode: '01' fraudSubTypeCode: U cardProductCode: CIR transactionDate: '20200215' settlementDate: '20200216' fraudPostedDate: '20210316' cardholderReportedDate: '20210314' transactionAmount: '56823' transactionCurrencyCode: '840' billingAmount: '56823' billingCurrencyCode: '840' merchantId: '6698696' merchantName: BANKNEWPORT merchantCity: Phoenix merchantStateProvinceCode: AZ merchantCountryCode: USA merchantPostalCode: '85001' merchantCategoryCode: '6011' terminalAttendanceIndicator: '0' terminalId: 5055D305 terminalOperatingEnvironment: '1' cardholderPresenceIndicator: '0' cardPresenceIndicator: '1' cardInPossession: 'Y' catLevelIndicator: '2' terminalCapabilityIndicator: '0' posEntryMode: '00' cvcInvalidIndicator: M avsResponseCode: U authResponseCode: '00' secureCode: '9' accountDeviceType: A transactionIndicator: M101 memo: This is a sample FDA complete request. issuerSCAExemption: '09' FraudChangeExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:37-06:00' icaNumber: '1076' providerId: '10' auditControlNumber: '123111111000025' fraudPostedDate: '20210316' fraudTypeCode: '01' fraudSubTypeCode: 'N' accountDeviceType: '1' cardholderReportedDate: '20210314' cardInPossession: 'Y' memo: This is a sample FDC minimal request. issuerSCAExemption: '09' FraudIssuerChangeExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:37-06:00' icaNumber: '1076' auditControlNumber: '123111111000025' acquirerId: '2742' cardNumber: '5587450000000008074' fraudTypeCode: '01' fraudSubTypeCode: U cardProductCode: CIR transactionDate: '20200215' settlementDate: '20200216' fraudPostedDate: '20210316' cardholderReportedDate: '20210314' transactionAmount: '56823' transactionCurrencyCode: '840' billingAmount: '56823' billingCurrencyCode: '840' merchantId: '6698696' merchantName: BANKNEWPORT merchantCity: Phoenix merchantStateProvinceCode: AZ merchantCountryCode: USA merchantPostalCode: '85001' merchantCategoryCode: '6011' terminalAttendanceIndicator: '0' terminalId: 5055D305 terminalOperatingEnvironment: '1' cardholderPresenceIndicator: '0' cardPresenceIndicator: '1' cardInPossession: 'Y' catLevelIndicator: '2' terminalCapabilityIndicator: '0' posEntryMode: '00' cvcInvalidIndicator: M avsResponseCode: U authResponseCode: '00' secureCode: '9' accountDeviceType: A transactionIndicator: M205 memo: This is a sample FDC complete request. issuerSCAExemption: '09' FraudDeleteExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:37-06:00' icaNumber: '1076' providerId: '10' auditControlNumber: '123111111000025' operationType: FDD memo: This is a sample FDD request. FraudConfirmExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:37-06:00' icaNumber: '1076' providerId: '10' auditControlNumber: '123111111000025' operationType: FDE memo: This is a sample FDE request. FraudAdditionExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '000' responseMessage: Success icaNumber: '1076' auditControlNumber: '123111111000025' currentStatus: CONFIRMED-SUCCESS matchLevelIndicator: M financialTransactionIndicator: DECLINED authorizationResponse: 05 - Do not honor FraudIssuerAdditionExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '000' responseMessage: Success icaNumber: '1076' auditControlNumber: '123111111000025' currentStatus: CONFIRMED-SUCCESS matchLevelIndicator: I financialTransactionIndicator: APPROVED FraudAdditionRejectExample: value: 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. FraudAdditionSuspendExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '201' responseMessage: Failure icaNumber: '1076' auditControlNumber: '123111111000025' matchLevelIndicator: M currentStatus: CONFIRMED-SUSPENDED duplicateAuditControlNumbers: - '000222520077829' - '000222520077830' - '000222520077831' - '000222520077832' - '000222520077833' errorDetails: Errors: Error: - ReasonCode: '30100' Description: Potential Duplicate Data Found, Record is suspended. FraudIssuerAdditionSuspendExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '201' responseMessage: Failure icaNumber: '1076' auditControlNumber: '123111111000025' matchLevelIndicator: I currentStatus: CONFIRMED-SUSPENDED duplicateAuditControlNumbers: - '000222520077829' - '000222520077830' - '000222520077831' - '000222520077832' - '000222520077833' errorDetails: Errors: Error: - ReasonCode: '30100' Description: Potential Duplicate Data Found, Record is suspended. FraudAddAcceptedExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '001' responseMessage: Pending icaNumber: '1076' auditControlNumber: '123111111000025' FraudDataChanged: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '000' responseMessage: Success icaNumber: '1076' auditControlNumber: '123111111000025' previousStatus: CONFIRMED-REJECTED currentStatus: CONFIRMED-SUCCESS matchLevelIndicator: M financialTransactionIndicator: DECLINED authorizationResponse: 05 - Do not honor FraudIssuerDataChanged: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '000' responseMessage: Success icaNumber: '1076' auditControlNumber: '123111111000025' previousStatus: CONFIRMED-REJECTED currentStatus: CONFIRMED-SUCCESS matchLevelIndicator: I financialTransactionIndicator: APPROVED FraudDataChangedError: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '100' responseMessage: Failure errorDetails: Errors: Error: - ReasonCode: '60003' Description: icaNumber incorrect datatype of attribute value. FraudDataDeleted: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '000' responseMessage: Success icaNumber: '1076' auditControlNumber: '123111111000025' previousStatus: CONFIRMED-SUCCESS currentStatus: CONFIRMED-DELETED FraudDataDeleteIcaNotAuthorize: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '200' responseMessage: Failure errorDetails: Errors: Error: - ReasonCode: '80207' Description: The user is not licensed for this particular BIN range. FraudDataConfirmed: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '000' responseMessage: Success icaNumber: '1076' auditControlNumber: '123111111000025' previousStatus: CONFIRMED-SUSPENDED currentStatus: CONFIRMED-SUCCESS FraudDataConfirmedTxnDateOlder: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '200' responseMessage: Failure errorDetails: Errors: Error: - ReasonCode: '21508' Description: Transaction date is older than 18 months. FraudStatusConfirmed: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' icaNumber: '1076' responseCode: '000' responseMessage: Success auditControlNumber: '123111111000025' channel: EXT_API currentStatus: CONFIRMED-SUCCESS matchLevelIndicator: M financialTransactionIndicator: DECLINED authorizationResponse: 05 - Do not honor FraudStatusSuspended: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' icaNumber: '1076' responseCode: '000' responseMessage: Success auditControlNumber: '123111111000025' channel: EXT_API currentStatus: CONFIRMED-SUSPENDED errorDetails: Errors: Error: - ReasonCode: '30100' Description: Potential Duplicate Data Found, Record is suspended. FraudStatusRejected: value: timestamp: '2021-03-16T20:34:40-06:00' icaNumber: '1076' responseCode: '000' responseMessage: Success auditControlNumber: '123111111000025' channel: Online currentStatus: CONFIRMED-REJECTED errorDetails: Errors: Error: - ReasonCode: '20806' Description: >- Required field [Fraud Posted Date] is missing. Record is rejected. - ReasonCode: '20828' Description: >- Required field [Fraud Type Code] is missing. Record is rejected. - ReasonCode: '20903' Description: Audit control number (ACN) is not unique. Record is rejected. - ReasonCode: '21006' Description: >- Invalid Fraud Posted Date, format should be YYYYMMDD. Record is rejected. - ReasonCode: '41200' Description: >- Unable to match transaction in data warehouse. Record is rejected. FraudStatusDeleted: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' icaNumber: '1076' responseCode: '000' responseMessage: Success auditControlNumber: '123111111000025' channel: EXT_API currentStatus: CONFIRMED-DELETED FraudStatusNoRecordExample: value: refId: ecb2d942-eabd-42b6-87fd-69c19692bdc6 timestamp: '2021-03-16T20:34:40-06:00' responseCode: '200' responseMessage: Failure auditControlNumber: '123111111000025' errorDetails: Errors: Error: - ReasonCode: '60127' Description: >- Record searched could not be found. Correct the input parameter and resubmit. FraudStatusNoParamRefIdAcnExample: value: ica: '1076' responseCode: '100' responseMessage: Failure errorDetails: Errors: Error: - ReasonCode: '60002' Description: >- ref_id or acn (Audit Control Number) attribute or attribute value is missing or incorrect. BadRequestRefIdMissing: value: Errors: Error: - Source: fld ReasonCode: VALIDATION_ERROR Description: Reference Id is not provided Recoverable: false BadRequestInvalidIca: value: Errors: Error: - Source: fld ReasonCode: VALIDATION_ERROR Description: ica incorrect datatype of attribute value. Recoverable: false BadRequestInvalidRefId: value: Errors: Error: - Source: fld ReasonCode: VALIDATION_ERROR Description: ref_id incorrect datatype of attribute value. Recoverable: false BadRequestInvalidACN: value: Errors: Error: - Source: fld ReasonCode: VALIDATION_ERROR Description: >- acn (Audit Control Number) incorrect datatype of attribute value. Recoverable: false ForbiddenExample: value: Errors: Error: - Source: fld ReasonCode: CONSENT_NOT_GIVEN Description: User Consent Not Given Recoverable: false UnauthorizedExample: value: Errors: Error: - Source: fld ReasonCode: UNAUTHORIZED_REQUEST Description: Unauthorized request Recoverable: false RateLimitExceededExample: value: Errors: Error: - Source: fld ReasonCode: RATE_LIMIT_EXCEEDED Description: >- You have exceeded the service rate limit. Maximum allowed 10 TPS. Recoverable: true details: