Adyen · Schema
CreateTestCardRangesRequest
PaymentsFinancial ServicesFintechAgentic CommercePoint-of-SalePayment Processing
Properties
| Name | Type | Description |
|---|---|---|
| accountCode | string | The code of the account, for which the test card ranges should be created. |
| accountTypeCode | string | The type of the account, for which the test card ranges should be created. Permitted values: * Company * MerchantAccount > These values are case-sensitive. |
| testCardRanges | array | A list of test card ranges to create. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/adyen/main/json-schema/adyen-create-test-card-ranges-request-schema.json",
"title": "CreateTestCardRangesRequest",
"x-generated": "2026-10-12",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/adyen-createtestcardranges-api-openapi.yml#/components/schemas/CreateTestCardRangesRequest",
"properties": {
"accountCode": {
"description": "The code of the account, for which the test card ranges should be created.",
"type": "string"
},
"accountTypeCode": {
"description": "The type of the account, for which the test card ranges should be created.\n\nPermitted values:\n* Company\n* MerchantAccount\n> These values are case-sensitive.",
"type": "string"
},
"testCardRanges": {
"description": "A list of test card ranges to create.",
"items": {
"$ref": "#/$defs/TestCardRange"
},
"type": "array"
}
},
"required": [
"accountTypeCode",
"accountCode",
"testCardRanges"
],
"$defs": {
"AvsAddress": {
"properties": {
"streetAddress": {
"description": "The street and house number of the address.\n\nExample: 1 Infinite Loop, Cupertino.",
"type": "string"
},
"zip": {
"description": "The zip or post code of the address.\n\nExample: CA 95014",
"type": "string"
}
},
"required": [
"streetAddress"
]
},
"TestCardRange": {
"properties": {
"address": {
"description": "Contains the billing address of the card holder. The address details need to be AVS-compliant, which means that you need to provide at least street address.",
"$ref": "#/$defs/AvsAddress"
},
"cardHolderName": {
"description": "The name of the card holder, as it appears on the card, for the test card range.",
"type": "string"
},
"cvc": {
"description": "The test card range security code.\n\nExample: 123",
"type": "string"
},
"expiryMonth": {
"description": "Expiry month for the test card range.\n\nAllowed values:\n* JANUARY\n* FEBRUARY\n* MARCH\n* APRIL\n* MAY\n* JUNE\n* JULY\n* AUGUST\n* SEPTEMBER\n* OCTOBER\n* NOVEMBER\n* DECEMBER",
"enum": [
"APRIL",
"AUGUST",
"DECEMBER",
"FEBRUARY",
"JANUARY",
"JULY",
"JUNE",
"MARCH",
"MAY",
"NOVEMBER",
"OCTOBER",
"SEPTEMBER"
],
"type": "string"
},
"expiryYear": {
"description": "Expiry year for the test card range.\n\nExample: 2020",
"format": "int32",
"type": "integer"
},
"rangeEnd": {
"description": "The last test card number in the test card range (inclusive):\n\n* Min 6, max 19 digits\n* BIN compliant\nExample: 5432 1234 1234 4321",
"type": "string"
},
"rangeStart": {
"description": "The first test card number in the test card range (inclusive):\n\n* Min 6, max 19 digits\n* BIN compliant\nExample: 5432 1234 1234 1234",
"type": "string"
},
"threeDDirectoryServerResponse": {
"description": "3D Secure server response. It notifies whether the specified card holder is enrolled in a 3D Secure service. Possible values:\n\n* Y (Authentication available)\n* N (Card holder not enrolled/not participating)\n* U (Unable to authenticate)",
"enum": [
"N",
"U",
"Y"
],
"type": "string"
},
"threeDPassword": {
"description": "The password used for 3D Secure authentication.",
"type": "string"
},
"threeDUsername": {
"description": "The username used for 3D Secure authentication.",
"type": "string"
}
},
"required": [
"rangeStart",
"rangeEnd",
"expiryMonth",
"expiryYear",
"cardHolderName"
]
}
}
}
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/adyen-create-test-card-ranges-request"
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.