Adyen · JSON Structure

Notification Webhooks Payment Instrument Structure

PaymentInstrument schema from Adyen API

Type: object Properties: 10 Required: 4
PaymentsFinancial-ServicesFintech

PaymentInstrument is a JSON Structure definition published by Adyen, describing 10 properties, of which 4 are required. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.

Properties

balanceAccountId bankAccount card description id issuingCountryCode paymentInstrumentGroupId reference status type

Meta-schema: https://json-structure.org/meta/core/v0/#

JSON Structure

Raw ↑
{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/adyen/refs/heads/main/json-structure/notification-webhooks-payment-instrument-structure.json",
  "description": "PaymentInstrument schema from Adyen API",
  "properties": {
    "balanceAccountId": {
      "description": "The unique identifier of the [balance account](https://docs.adyen.com/api-explorer/#/balanceplatform/v1/post/balanceAccounts__resParam_id) associated with the payment instrument.",
      "type": "string"
    },
    "bankAccount": {
      "description": "Contains the business account details. Returned when you create a payment instrument with `type` **bankAccount**.",
      "$ref": "#/components/schemas/BankAccount"
    },
    "card": {
      "description": "Contains information about the card payment instrument. Returned when you create a payment instrument with `type` **card**.",
      "$ref": "#/components/schemas/Card"
    },
    "description": {
      "description": "Your description for the payment instrument, maximum 300 characters.",
      "maxLength": 300,
      "type": "string"
    },
    "id": {
      "description": "The unique identifier of the payment instrument.",
      "type": "string"
    },
    "issuingCountryCode": {
      "description": "The two-character [ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) country code where the payment instrument is issued. For example, **NL** or **US**.",
      "type": "string"
    },
    "paymentInstrumentGroupId": {
      "description": "The unique identifier of the [payment instrument group](https://docs.adyen.com/api-explorer/#/balanceplatform/v1/post/paymentInstrumentGroups__resParam_id) to which the payment instrument belongs.",
      "type": "string"
    },
    "reference": {
      "description": "Your reference for the payment instrument, maximum 150 characters.",
      "maxLength": 150,
      "type": "string"
    },
    "status": {
      "x-enum": [
        {
          "description": "The payment instrument has been requested. This state is applicable when creating physical cards.",
          "value": "Requested"
        },
        {
          "description": "The payment instrument is active and can be used to make payments.",
          "value": "Active"
        },
        {
          "description": "The payment instrument is inactive and cannot be used to make payments.",
          "value": "Inactive"
        },
        {
          "description": "The payment instrument is temporarily suspended and cannot be used to make payments.",
          "value": "Suspended"
        },
        {
          "description": "The payment instrument is permanently closed. This action cannot be undone.",
          "value": "Closed"
        },
        {
          "description": "The payment instrument is suspended. Either because it was stolen or lost.",
          "value": "blocked"
        },
        {
          "description": "The payment instrument is permanently closed. This action cannot be undone.",
          "value": "discarded"
        }
      ],
      "description": "The status of the payment instrument. If a status is not specified when creating a payment instrument, it is set to **Active** by default. However, there can be exceptions for cards based on the `card.formFactor` and the `issuingCountryCode`. For example, when issuing physical cards in the US, the default status is **Requested**.\n\nPossible values: \n\n * **Active**:  The payment instrument is active and can be used to make payments. \n\n * **Requested**: The payment instrument has been requested. This state is applicable for physical cards. \n\n* **Inactive**: The payment instrument is inactive and cannot be used to make payments. \n\n * **Suspended**: The payment instrument is temporarily suspended and cannot be used to make payments. \n\n * **Closed**: The payment instrument is permanently closed. This action cannot be undone. \n\n* **Stolen** \n\n * **Lost**\n\n ",
      "enum": [
        "Active",
        "Closed",
        "Inactive",
        "Lost",
        "Requested",
        "Stolen",
        "Suspended",
        "blocked",
        "discarded"
      ],
      "type": "string"
    },
    "type": {
      "description": "Type of payment instrument.\n\nPossible value: **card**, **bankAccount**. ",
      "enum": [
        "bankAccount",
        "card"
      ],
      "type": "string"
    }
  },
  "required": [
    "balanceAccountId",
    "issuingCountryCode",
    "type",
    "id"
  ],
  "type": "object",
  "name": "PaymentInstrument"
}

Work with this as data

Every JSON Structure 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 json structure

4 MCP tools reach this
  • find_json_structuresBrowse and filter every JSON Structure 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 Structure
curl "https://apis.io/api/v1/json-structures/notification-webhooks-payment-instrument-structure"
All json structure
curl "https://apis.io/api/v1/json-structures?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.