Mastercard · Schema

SuspectedFraud

Credit CardsDigital IdentityFinancial-ServicesFraud DetectionOpen BankingPaymentsFortune 500

Properties

Name Type Description
cardNumber string Cardholder account number used in the fraudulent transaction. Card number to be verified through Luhn's algorithm.
transactionAmount string Transaction amount at the merchant location (without any decimals).
transactionDate string Local date at the merchant location when the transaction occurred. Format is 'YYYYMMDD'.
fraudPostedDate string Date on which the fraud is posted in FLD by the originator. Format is 'YYYYMMDD'.
fraudTypeCode string Code identifying the reason the originator submitted the transaction as fraud in FLD. Please refer to [TBD - Table 1](https://developer.mastercard.com/) for possible values.
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'.
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-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "SuspectedFraud",
  "type": "object",
  "properties": {
    "cardNumber": {
      "type": "string",
      "description": "Cardholder account number used in the fraudulent transaction. Card number to be verified through Luhn's algorithm."
    },
    "transactionAmount": {
      "type": "string",
      "description": "Transaction amount at the merchant location (without any decimals)."
    },
    "transactionDate": {
      "type": "string",
      "description": "Local date at the merchant location when the transaction occurred. Format is 'YYYYMMDD'."
    },
    "fraudPostedDate": {
      "type": "string",
      "description": "Date on which the fraud is posted in FLD by the originator. Format is 'YYYYMMDD'."
    },
    "fraudTypeCode": {
      "type": "string",
      "description": "Code identifying the reason the originator submitted the transaction as fraud in FLD. Please refer to [TBD - Table 1](https://developer.mastercard.com/) for possible values."
    },
    "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."
    },
    "cardholderReportedDate": {
      "type": "string",
      "description": "Date on which the cardholder had reported the fraud. Format is 'YYYYMMDD'."
    },
    "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"
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 email required.

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