Properties
| Name | Type | Description |
|---|---|---|
| authorisationType | string | The authorisation type. For example, **defaultAuthorisation**, **preAuthorisation**, **finalAuthorisation** |
| panEntryMode | string | Indicates the method used for entering the PAN to initiate a transaction. Possible values: **manual**, **chip**, **magstripe**, **contactless**, **cof**, **ecommerce**, **token**. |
| processingType | string | Contains information about how the payment was processed. For example, **ecommerce** for online or **pos** for in-person payments. |
| relayedAuthorisationData | object | If you are using relayed authorisation, this object contains information from the relayed authorisation response from your server. |
| schemeTraceId | string | The identifier of the original payment provided by the scheme. The Id could be alphanumeric or numeric depending on the scheme. The schemeTraceID should be referring to an original schemeUniqueTransac |
| schemeUniqueTransactionId | string | The unique identifier created by the scheme. The ID could be alphanumeric or numeric depending on the scheme. |
| type | string | **issuedCard** |
| validationFacts | array | The evaluation of the validation facts. See [validation checks](https://docs.adyen.com/issuing/validation-checks) for more information. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/adyen/refs/heads/main/json-schema/transfers-issued-card-schema.json",
"title": "IssuedCard",
"description": "IssuedCard schema from Adyen API",
"type": "object",
"properties": {
"authorisationType": {
"x-addedInVersion": "4",
"description": "The authorisation type. For example, **defaultAuthorisation**, **preAuthorisation**, **finalAuthorisation**",
"type": "string"
},
"panEntryMode": {
"x-addedInVersion": "4",
"description": "Indicates the method used for entering the PAN to initiate a transaction.\n\nPossible values: **manual**, **chip**, **magstripe**, **contactless**, **cof**, **ecommerce**, **token**.",
"enum": [
"chip",
"cof",
"contactless",
"ecommerce",
"magstripe",
"manual",
"token"
],
"type": "string"
},
"processingType": {
"x-addedInVersion": "4",
"description": "Contains information about how the payment was processed. For example, **ecommerce** for online or **pos** for in-person payments.",
"enum": [
"atmWithdraw",
"balanceInquiry",
"ecommerce",
"moto",
"pos",
"purchaseWithCashback",
"recurring",
"token"
],
"type": "string"
},
"relayedAuthorisationData": {
"x-addedInVersion": "4",
"description": "If you are using relayed authorisation, this object contains information from the relayed authorisation response from your server.",
"$ref": "#/components/schemas/RelayedAuthorisationData"
},
"schemeTraceId": {
"x-addedInVersion": "4",
"description": "The identifier of the original payment provided by the scheme. The Id could be alphanumeric or numeric depending on the scheme. The schemeTraceID should be referring to an original schemeUniqueTransactionID provided in an earlier payment (not necessarily processed by Adyen). Instances of available schemeTraceId is authAdjustment or recurring payments.",
"type": "string"
},
"schemeUniqueTransactionId": {
"x-addedInVersion": "4",
"description": "The unique identifier created by the scheme. The ID could be alphanumeric or numeric depending on the scheme.",
"type": "string"
},
"type": {
"default": "issuedCard",
"description": "**issuedCard**",
"enum": [
"issuedCard"
],
"type": "string"
},
"validationFacts": {
"x-addedInVersion": "4",
"description": "The evaluation of the validation facts. See [validation checks](https://docs.adyen.com/issuing/validation-checks) for more information.",
"items": {
"$ref": "#/components/schemas/TransferNotificationValidationFact"
},
"type": "array"
}
},
"additionalProperties": false
}
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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/transfers-issued-card"
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.