Lithic · Schema

Fraud Report Response

FintechCard IssuingPaymentsIssuer ProcessorKYCBanking as a Service

Properties

Name Type Description
transaction_token string The universally unique identifier (UUID) associated with the transaction being reported.
fraud_status string The fraud status of the transaction, string (enum) supporting the following values: - `SUSPECTED_FRAUD`: The transaction is suspected to be fraudulent, but this hasn’t been confirmed. - `FRAUDULENT`:
fraud_type string Specifies the type or category of fraud that the transaction is suspected or confirmed to involve, string (enum) supporting the following values: - `FIRST_PARTY_FRAUD`: First-party fraud occurs when a
comment string Provides additional context or details about the fraud report.
created_at string Timestamp representing when the fraud report was created.
updated_at string Timestamp representing the last update to the fraud report.
View JSON Schema on GitHub

JSON Schema

lithic-com-fraud-report-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "#/components/schemas/fraud-report-response",
  "title": "Fraud Report Response",
  "type": "object",
  "properties": {
    "transaction_token": {
      "type": "string",
      "format": "uuid",
      "description": "The universally unique identifier (UUID) associated with the transaction being reported."
    },
    "fraud_status": {
      "type": "string",
      "enum": [
        "SUSPECTED_FRAUD",
        "FRAUDULENT",
        "NOT_FRAUDULENT",
        "NO_REPORTED_FRAUD"
      ],
      "description": "The fraud status of the transaction, string (enum) supporting the following values:\n\n - `SUSPECTED_FRAUD`: The transaction is suspected to be fraudulent, but this hasn\u2019t been confirmed.\n - `FRAUDULENT`: The transaction is confirmed to be fraudulent. A transaction may immediately be moved into this state, or be graduated into this state from the `SUSPECTED_FRAUD` state.\n - `NOT_FRAUDULENT`: The transaction is (explicitly) marked as not fraudulent. A transaction may immediately be moved into this state, or be graduated into this state from the `SUSPECTED_FRAUD` state.\n - `NO_REPORTED_FRAUD`: Indicates that no fraud report exists for the transaction. It is the default state for transactions that have not been analyzed or associated with any known fraudulent activity."
    },
    "fraud_type": {
      "type": "string",
      "enum": [
        "FIRST_PARTY_FRAUD",
        "ACCOUNT_TAKEOVER",
        "CARD_COMPROMISED",
        "IDENTITY_THEFT",
        "CARDHOLDER_MANIPULATION"
      ],
      "description": "Specifies the type or category of fraud that the transaction is suspected or confirmed to involve, string (enum) supporting the following values:\n\n - `FIRST_PARTY_FRAUD`: First-party fraud occurs when a legitimate account or cardholder intentionally misuses financial services for personal gain. This includes actions such as disputing legitimate transactions to obtain a refund, abusing return policies, or defaulting on credit obligations without intent to repay.\n - `ACCOUNT_TAKEOVER`: Account takeover fraud occurs when a fraudster gains unauthorized access to an existing account, modifies account settings, and carries out fraudulent transactions.\n - `CARD_COMPROMISED`: Card compromised fraud occurs when a fraudster gains access to card details without taking over the account, such as through physical card theft, cloning, or online data breaches.\n - `IDENTITY_THEFT`: Identity theft fraud occurs when a fraudster uses stolen personal information, such as Social Security numbers or addresses, to open accounts, apply for loans, or conduct financial transactions in someone's name.\n - `CARDHOLDER_MANIPULATION`: This type of fraud occurs when a fraudster manipulates or coerces a legitimate cardholder into unauthorized transactions, often through social engineering tactics."
    },
    "comment": {
      "type": "string",
      "description": "Provides additional context or details about the fraud report."
    },
    "created_at": {
      "type": "string",
      "format": "date-time",
      "description": "Timestamp representing when the fraud report was created."
    },
    "updated_at": {
      "type": "string",
      "format": "date-time",
      "description": "Timestamp representing the last update to the fraud report."
    }
  },
  "required": [
    "transaction_token",
    "fraud_status"
  ]
}

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/lithic-com-fraud-report-response"
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.