Adyen · Schema
CreateAccountRequest
CreateAccountRequest schema from Adyen API
PaymentsFinancial-ServicesFintech
Properties
| Name | Type | Description |
|---|---|---|
| accountHolderCode | string | The code of Account Holder under which to create the account. |
| bankAccountUUID | string | The bankAccountUUID of the bank account held by the account holder to couple the account with. Scheduled payouts in currencies matching the currency of this bank account will be sent to this bank acco |
| description | string | A description of the account, maximum 256 characters. You can use alphanumeric characters (A-Z, a-z, 0-9), white spaces, and underscores `_`. |
| metadata | object | A set of key and value pairs for general use by the merchant. The keys do not have specific names and may be used for storing miscellaneous data as desired. > Note that during an update of metadata, t |
| payoutMethodCode | string | The payout method code held by the account holder to couple the account with. Scheduled card payouts will be sent using this payout method code. |
| payoutSchedule | string | The payout schedule of the prospective account. >Permitted values: `DEFAULT`, `HOLD`, `DAILY`, `WEEKLY`, `MONTHLY`. |
| payoutScheduleReason | string | The reason for the payout schedule choice. >Required if the payoutSchedule is `HOLD`. |
| payoutSpeed | string | Speed with which payouts for this account are processed. Permitted values: `STANDARD`, `SAME_DAY`. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/adyen/refs/heads/main/json-schema/accounts-create-account-request-schema.json",
"title": "CreateAccountRequest",
"description": "CreateAccountRequest schema from Adyen API",
"type": "object",
"properties": {
"accountHolderCode": {
"description": "The code of Account Holder under which to create the account.",
"type": "string"
},
"bankAccountUUID": {
"x-addedInVersion": "5",
"description": "The bankAccountUUID of the bank account held by the account holder to couple the account with. Scheduled payouts in currencies matching the currency of this bank account will be sent to this bank account. Payouts in different currencies will be sent to a matching bank account of the account holder.",
"type": "string"
},
"description": {
"x-addedInVersion": "4",
"description": "A description of the account, maximum 256 characters. You can use alphanumeric characters (A-Z, a-z, 0-9), white spaces, and underscores `_`.",
"type": "string"
},
"metadata": {
"x-addedInVersion": "5",
"additionalProperties": {
"type": "string"
},
"description": "A set of key and value pairs for general use by the merchant.\nThe keys do not have specific names and may be used for storing miscellaneous data as desired.\n> Note that during an update of metadata, the omission of existing key-value pairs will result in the deletion of those key-value pairs.",
"type": "object"
},
"payoutMethodCode": {
"x-addedInVersion": "5",
"description": "The payout method code held by the account holder to couple the account with. Scheduled card payouts will be sent using this payout method code.",
"type": "string"
},
"payoutSchedule": {
"description": "The payout schedule of the prospective account.\n>Permitted values: `DEFAULT`, `HOLD`, `DAILY`, `WEEKLY`, `MONTHLY`.",
"enum": [
"BIWEEKLY_ON_1ST_AND_15TH_AT_MIDNIGHT",
"DAILY",
"DAILY_AU",
"DAILY_EU",
"DAILY_SG",
"DAILY_US",
"HOLD",
"MONTHLY",
"WEEKLY",
"WEEKLY_MON_TO_FRI_AU",
"WEEKLY_MON_TO_FRI_EU",
"WEEKLY_MON_TO_FRI_US",
"WEEKLY_ON_TUE_FRI_MIDNIGHT",
"WEEKLY_SUN_TO_THU_AU",
"WEEKLY_SUN_TO_THU_US"
],
"type": "string"
},
"payoutScheduleReason": {
"description": "The reason for the payout schedule choice.\n>Required if the payoutSchedule is `HOLD`.",
"type": "string"
},
"payoutSpeed": {
"x-addedInVersion": "5",
"default": "STANDARD",
"description": "Speed with which payouts for this account are processed. Permitted values: `STANDARD`, `SAME_DAY`.",
"enum": [
"INSTANT",
"SAME_DAY",
"STANDARD"
],
"type": "string"
}
},
"required": [
"accountHolderCode"
]
}
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/accounts-create-account-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.