Mastercard · Schema

SuspectedFraudStateChange

Credit CardsDigital IdentityFinancial-ServicesFraud DetectionOpen BankingPaymentsFortune 500

Properties

Name Type Description
auditControlNumber string Unique number generated by FLD application and provided in the response message for a successful suspected fraud record submission (FDA event). This is used as a reference to subsequently modify, dele
transactionIdentifiers string Contains the a single or dual message transaction identifier values used for searching the respective transaction. Acquirer Reference Number, Banknet Reference Number, Trace Id and Serial Id values ar
fraudPostedDate string Date on which the fraud is posted in FLD by the originator. Format is 'YYYYMMDD'. This is a conditional parameter and is mandatory when operationType value is CONFIRMED_FRAUD.
fraudTypeCode string 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-
fraudSubTypeCode string 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]
accountDeviceType string 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/parame
cardholderReportedDate string Date on which the cardholder had reported the fraud. Format is 'YYYYMMDD'. This is a conditional parameter and is mandatory when operationType value is CONFIRMED_FRAUD.
notFraudTypeCode string Code to further identify the reason that the originator submitted the transaction as a not fraud transaction in FLD. This attribute is mandatory for the Issuer but optional for the Acquirer. Please re
avsResponseCode string 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-
authResponseCode string 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-c
memo string Brief description by the originator providing some comment supporting the action.
View JSON Schema on GitHub

JSON Schema

mastercard-suspected-fraud-suspected-fraud-state-change-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "SuspectedFraudStateChange",
  "type": "object",
  "properties": {
    "auditControlNumber": {
      "type": "string",
      "description": "Unique number generated by FLD application and provided in the response message for a successful suspected fraud record submission (FDA event). This is used as a reference to subsequently modify, delete or convert a suspended to a confirmed fraud record."
    },
    "transactionIdentifiers": {
      "type": "string",
      "description": "Contains the a single or dual message transaction identifier values used for searching the respective transaction. Acquirer Reference Number, Banknet Reference Number, Trace Id and Serial Id values are captured. This is a conditional parameter and is mandatory when operationType value is CONFIRMED_FRAUD."
    },
    "fraudPostedDate": {
      "type": "string",
      "description": "Date on which the fraud is posted in FLD by the originator. Format is 'YYYYMMDD'. This is a conditional parameter and is mandatory when operationType value is CONFIRMED_FRAUD."
    },
    "fraudTypeCode": {
      "type": "string",
      "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. This is a conditional parameter and is mandatory when operationType value is CONFIRMED_FRAUD."
    },
    "fraudSubTypeCode": {
      "type": "string",
      "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. This is a conditional parameter and is mandatory when operationType value is CONFIRMED_FRAUD."
    },
    "accountDeviceType": {
      "type": "string",
      "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. This field is required for Issuer and optional for Acquirer. This is a conditional parameter and is mandatory when operationType value is CONFIRMED_FRAUD."
    },
    "cardholderReportedDate": {
      "type": "string",
      "description": "Date on which the cardholder had reported the fraud. Format is 'YYYYMMDD'. This is a conditional parameter and is mandatory when operationType value is CONFIRMED_FRAUD."
    },
    "notFraudTypeCode": {
      "type": "string",
      "description": "Code to further identify the reason that the originator submitted the transaction as a not fraud transaction 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."
    },
    "avsResponseCode": {
      "type": "string",
      "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."
    },
    "authResponseCode": {
      "type": "string",
      "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."
    },
    "memo": {
      "type": "string",
      "description": "Brief description by the originator providing some comment supporting the action."
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/mastercard-suspected-fraud-suspected-fraud-state-change"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.