Adyen · Schema

SaleData

Data associated to the Sale System, with a particular value during the processing of the payment by the POI, including the cards acquisition. Data related to the Sale System.

PaymentsFinancial-ServicesFintech

Properties

Name Type Description
OperatorID string
OperatorLanguage string if different from the Login.
ShiftNumber string if different from the Login and see Login .SaleData.
SaleTransactionID object
SaleReferenceID string If payment reservation.
SaleTerminalData object
TokenRequestedType object
CustomerOrderID string Additional and optional identification of a customer order.
CustomerOrderReq object
SaleToPOIData string Stored with the transaction.
SaleToAcquirerData string Send to the Acquirer if present.
SaleToIssuerData object
View JSON Schema on GitHub

JSON Schema

terminal-sale-data-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/adyen/refs/heads/main/json-schema/terminal-sale-data-schema.json",
  "title": "SaleData",
  "description": "Data associated to the Sale System, with a particular value during the processing of the payment by the POI, including the cards acquisition. Data related to the Sale System.",
  "type": "object",
  "properties": {
    "OperatorID": {
      "type": "string",
      "pattern": "^.+$"
    },
    "OperatorLanguage": {
      "type": "string",
      "pattern": "^[a-z]{2,2}$",
      "description": "if different from the Login."
    },
    "ShiftNumber": {
      "type": "string",
      "pattern": "^.+$",
      "description": "if different from the Login and  see Login .SaleData."
    },
    "SaleTransactionID": {
      "$ref": "#/components/schemas/TransactionIDType"
    },
    "SaleReferenceID": {
      "type": "string",
      "pattern": "^.+$",
      "description": "If payment reservation."
    },
    "SaleTerminalData": {
      "$ref": "#/components/schemas/SaleTerminalData"
    },
    "TokenRequestedType": {
      "$ref": "#/components/schemas/TokenRequestedType"
    },
    "CustomerOrderID": {
      "type": "string",
      "pattern": "^.+$",
      "description": "Additional and optional identification of a customer order."
    },
    "CustomerOrderReq": {
      "$ref": "#/components/schemas/CustomerOrderReq"
    },
    "SaleToPOIData": {
      "type": "string",
      "pattern": "^.+$",
      "description": "Stored with the transaction."
    },
    "SaleToAcquirerData": {
      "type": "string",
      "pattern": "^.+$",
      "description": "Send to the Acquirer if present."
    },
    "SaleToIssuerData": {
      "$ref": "#/components/schemas/SaleToIssuerData"
    }
  },
  "required": [
    "SaleTransactionID"
  ]
}

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/terminal-sale-data"
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.