Request a payment method
Sends a request to add a new payment method to the merchant account identified in the path.
To make this request, your API credential must have the following role:
- Management API—Payment methods read and write
The unique identifier of the merchant account.
ACCEL details.
The type of transactions processed over this payment method. Allowed values:
- pos for in-person payments.
- billpay for subscription payments, both the initial payment and the later recurring payments. These transactions have recurringProcessingModelSubscription.
- ecom for all other card not present transactions. This includes non-recurring transactions and transactions with recurringProcessingModelCardOnFile or UnscheduledCardOnFile.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Affirm details.
Merchant support email
Afterpay Touch details.
Support Email
Support Url
AlipayPlus details.
The currency used for settlement. Defaults to USD.
Amex details.
Merchant ID (MID) number. Format: 10 numeric characters.
You must provide this field when you request gatewayContract or paymentDesignatorContract service levels.
Indicates whether the Amex Merchant ID is reused from a previously setup Amex payment method.
This is only applicable for gatewayContract and paymentDesignatorContract service levels.
The default value is false.
Specifies the service level (settlement type) of this payment method. Possible values:
- noContract: Adyen holds the contract with American Express.
- gatewayContract: American Express receives the settlement and handles disputes, then pays out to you or your sub-merchant directly.
- paymentDesignatorContract: Adyen receives the settlement, and handles disputes and payouts.
Apple Pay details.
The list of merchant domains. Maximum: 99 domains per request.
For more information, see Apple Pay documentation.
The unique identifier of the business line. Required if you are a platform model.
Cartes Bancaires details.
Cartes Bancaires SIRET. Format: 14 digits.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Clearpay details.
Support Url
The list of countries where a payment method is available. By default, all countries supported by the payment method.
China Union Pay details.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
The list of currencies that a payment method supports. By default, all currencies supported by the payment method.
The list of custom routing flags to route payment to the intended acquirer.
Diners details. For merchants operating in Japan, Diners payments are processed through the JCB network. This means that you must include JCB-specific fields in this object.
MID (Merchant ID) number. Required for merchants operating in Japan. Format: 14 numeric characters.
Indicates whether the JCB Merchant ID is reused from a previously configured JCB payment method. The default value is false. For merchants operating in Japan, this field is required and must be set to true.
Specifies the service level (settlement type) of this payment method. Required for merchants operating in Japan. Possible values:
- noContract: Adyen holds the contract with JCB.
- gatewayContract: JCB receives the settlement and handles disputes, then pays out to you or your sub-merchant directly.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Discover details. For merchants operating in Japan, request Diners payment method instead. Discover is automatically requested, together with Diners.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
EFT PAD details.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Eftpos Australia details.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Girocard details.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Google Pay details.
Google Pay Merchant ID. Character length and limitations: 16 alphanumeric characters or 20 numeric characters.
Indicates whether the Google Pay Merchant ID is used for several merchant accounts. Default value: false.
iDeal details.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Interac Card details.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
JCB details.
For merchants operating in Japan, midNumber, reuseMidNumber, and serviceLevel fields are required.
For merchants operating outside of Japan, these fields are not required.
MID (Merchant ID) number. Required for merchants operating in Japan or merchants operating in Canada, Australia and New Zealand when requesting gatewayContract or paymentDesignatorContract service levels.Format: 14 numeric characters for Japan, 10 numeric characters for Canada, Australia and New Zealand.
Indicates whether the JCB Merchant ID is reused from a previously setup JCB payment method. The default value is false.For merchants operating in Japan, this field is required and must be set to true.
Specifies the service level (settlement type) of this payment method. Required for merchants operating in Japan. Possible values:
- noContract: Adyen holds the contract with JCB for merchants operating in Japan or American Express for merchants operating in Canada, Australia and New Zealand.
- gatewayContract: JCB or American Express receives the settlement and handles disputes, then pays out to you or your sub-merchant directly.
- paymentDesignatorContract: Available only for merchants operating in Canada, Australia and New Zealand. Adyen receives the settlement, and handles disputes and payouts.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Klarna details.
Indicates the status of Automatic capture. Default value: false.
The email address for disputes.
The region of operation. For example, NA, EU, CH, AU.
The email address of merchant support.
Maestro details. In the US, maestro is not supported; use maestro_usa instead.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Maestro USA details. Only for Maestro USA, for global use maestro.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
MasterCard details.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Meal Voucher FR details.
Meal Voucher conecsId. Format: digits only
Meal Voucher siret. Format: 14 digits.
The list of additional payment methods. Allowed values: mealVoucher_FR_edenred, mealVoucher_FR_groupeup, mealVoucher_FR_natixis, mealVoucher_FR_sodexo.
NYCE details.
The type of transactions processed over this payment method. Allowed values:
- pos for in-person payments.
- billpay for subscription payments, both the initial payment and the later recurring payments. These transactions have recurringProcessingModelSubscription.
- ecom for all other card not present transactions. This includes non-recurring transactions and transactions with recurringProcessingModelCardOnFile or UnscheduledCardOnFile.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
PayByBank Plaid details.
Merchant logo (max. size 150kB). Format: Base64-encoded string.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
PayMe details.
Merchant display name
Merchant logo. Format: Base64-encoded string.
The email address of merchant support.
PayPal details.
Indicates if direct (immediate) capture for PayPal is enabled. If set to true, this setting overrides the capture settings of your merchant account. Default value: true.
PayPal Merchant ID. Character length and limitations: 13 single-byte alphanumeric characters.
Your business email address.
PayTo details.
Merchant name displayed to the shopper in the Agreements
Represents the purpose of the Agreements created, it relates to the business type Allowed values: mortgage, utility, loan, gambling, retail, salary, personal, government, pension, tax, other
PULSE details.
The type of transactions processed over this payment method. Allowed values:
- pos for in-person payments.
- billpay for subscription payments, both the initial payment and the later recurring payments. These transactions have recurringProcessingModelSubscription.
- ecom for all other card not present transactions. This includes non-recurring transactions and transactions with recurringProcessingModelCardOnFile or UnscheduledCardOnFile.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
Your reference for the payment method. Supported characters a-z, A-Z, 0-9.
Sepa Direct Debit details.
Creditor id
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
The sales channel. Required if the merchant account does not have a sales channel. When you provide this field, it overrides the default sales channel set on the merchant account.
Possible values: eCommerce, pos, contAuth, and moto.
Sodexo details.
Sodexo merchantContactPhone
Sofort details.
Sofort currency code. For example, EUR.
Sofort logo. Format: Base64-encoded string.
STAR details.
The type of transactions processed over this payment method. Allowed values:
- pos for in-person payments.
- billpay for subscription payments, both the initial payment and the later recurring payments. These transactions have recurringProcessingModelSubscription.
- ecom for all other card not present transactions. This includes non-recurring transactions and transactions with recurringProcessingModelCardOnFile or UnscheduledCardOnFile.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
The ID of the store, if any.
Swish details.
- This field is required only if you have a contract with Swish. Swish handles settlement directly with you (not through Adyen).
- If not specified then it's assumed that you are using Adyen's contract with Swish.You don't have a direct relationship with Swish.
Swish number. Format: 10 digits without spaces. For example, 1231111111.
Edenred (Brazil) details.
Ticket requestorId
Twint details.
Twint logo. Format: Base64-encoded string.
Payment method variant.
Vipps details.
Vipps logo. Format: Base64-encoded string.
Vipps subscription cancel url (required in case of recurring payments)
Visa details.
Information regarding the transaction description.
You cannot configure the transaction description in the test environment.
The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /.
The type of transaction description you want to use:
- fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
WeChat Pay details.
The name of the contact person from merchant support.
The email address of merchant support.
WeChat Pay POS details.
The name of the contact person from merchant support.
The email address of merchant support.
After submitting a call, you receive a response message to inform you that your request was received and processed.
Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.
HTTP Responses
- 200 - OK- The request has succeeded. accelobject- ACCEL details. processingTypestring- The type of transactions processed over this payment method. Allowed values: - pos for in-person payments.
- billpay for subscription payments, both the initial payment and the later recurring payments. These transactions have recurringProcessingModelSubscription.
- ecom for all other card not present transactions. This includes non-recurring transactions and transactions with recurringProcessingModelCardOnFile or UnscheduledCardOnFile.
 transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 affirmobject- Affirm details. supportEmailstring- Merchant support email afterpayTouchobject- Afterpay Touch details. supportEmailstring- Support Email supportUrlstring- Support Url alipayPlusobject- AlipayPlus details. settlementCurrencyCodestring- The currency used for settlement. Defaults to USD. allowedboolean- Indicates whether receiving payments is allowed. This value is set to true by Adyen after screening your merchant account. amexobject- Amex details. midNumberstringMax length: 10- Merchant ID (MID) number. Format: 10 numeric characters. You must provide this field when you request - gatewayContractor- paymentDesignatorContractservice levels.reuseMidNumberboolean- Indicates whether the Amex Merchant ID is reused from a previously setup Amex payment method. This is only applicable for - gatewayContractand- paymentDesignatorContractservice levels. The default value is false.serviceLevelstring- Specifies the service level (settlement type) of this payment method. Possible values: - noContract: Adyen holds the contract with American Express.
- gatewayContract: American Express receives the settlement and handles disputes, then pays out to you or your sub-merchant directly.
- paymentDesignatorContract: Adyen receives the settlement, and handles disputes and payouts.
 applePayobject- Apple Pay details. domainsarray[string]- The list of merchant domains. Maximum: 99 domains per request. - For more information, see Apple Pay documentation. businessLineIdstring- The unique identifier of the business line. Required if you are a platform model. cartesBancairesobject- Cartes Bancaires details. siretstring- Cartes Bancaires SIRET. Format: 14 digits. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 clearpayobject- Clearpay details. supportUrlstring- Support Url countriesarray[string]- The list of countries where a payment method is available. By default, all countries supported by the payment method. cupobject- China Union Pay details. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 currenciesarray[string]- The list of currencies that a payment method supports. By default, all currencies supported by the payment method. customRoutingFlagsarray[string]- The list of custom routing flags to route payment to the intended acquirer. dinersobject- Diners details. For merchants operating in Japan, Diners payments are processed through the JCB network. This means that you must include JCB-specific fields in this object. midNumberstringMax length: 14- MID (Merchant ID) number. Required for merchants operating in Japan. Format: 14 numeric characters. reuseMidNumberboolean- Indicates whether the JCB Merchant ID is reused from a previously configured JCB payment method. The default value is false. For merchants operating in Japan, this field is required and must be set to true. serviceLevelstring- Specifies the service level (settlement type) of this payment method. Required for merchants operating in Japan. Possible values: - noContract: Adyen holds the contract with JCB.
- gatewayContract: JCB receives the settlement and handles disputes, then pays out to you or your sub-merchant directly.
 transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 discoverobject- Discover details. For merchants operating in Japan, request Diners payment method instead. Discover is automatically requested, together with Diners. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 eft_directdebit_CAobject- EFT PAD details. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 eftpos_australiaobject- Eftpos Australia details. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 enabledboolean- Indicates whether the payment method is enabled (true) or disabled (false). girocardobject- Girocard details. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 googlePayobject- Google Pay details. merchantIdstringMin length: 16Max length: 20- Google Pay Merchant ID. Character length and limitations: 16 alphanumeric characters or 20 numeric characters. reuseMerchantIdboolean- Indicates whether the Google Pay Merchant ID is used for several merchant accounts. Default value: false. idstring- The identifier of the resource. idealobject- iDeal details. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 interac_cardobject- Interac Card details. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 jcbobject- JCB details. For merchants operating in Japan, - midNumber,- reuseMidNumber, and- serviceLevelfields are required. For merchants operating outside of Japan, these fields are not required.midNumberstringMax length: 14- MID (Merchant ID) number. Required for merchants operating in Japan or merchants operating in Canada, Australia and New Zealand when requesting - gatewayContractor- paymentDesignatorContractservice levels.Format: 14 numeric characters for Japan, 10 numeric characters for Canada, Australia and New Zealand.reuseMidNumberboolean- Indicates whether the JCB Merchant ID is reused from a previously setup JCB payment method. The default value is false.For merchants operating in Japan, this field is required and must be set to true. serviceLevelstring- Specifies the service level (settlement type) of this payment method. Required for merchants operating in Japan. Possible values: - noContract: Adyen holds the contract with JCB for merchants operating in Japan or American Express for merchants operating in Canada, Australia and New Zealand.
- gatewayContract: JCB or American Express receives the settlement and handles disputes, then pays out to you or your sub-merchant directly.
- paymentDesignatorContract: Available only for merchants operating in Canada, Australia and New Zealand. Adyen receives the settlement, and handles disputes and payouts.
 transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 klarnaobject- Klarna details. autoCaptureboolean- Indicates the status of Automatic capture. Default value: false. disputeEmailstring- The email address for disputes. regionstringMin length: 2Max length: 2- The region of operation. For example, NA, EU, CH, AU. supportEmailstring- The email address of merchant support. maestroobject- Maestro details. In the US, - maestrois not supported; use- maestro_usainstead.transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 maestro_usaobject- Maestro USA details. Only for Maestro USA, for global use - maestro.transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 mcobject- MasterCard details. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 mealVoucher_FRobject- Meal Voucher FR details. conecsIdstring- Meal Voucher conecsId. Format: digits only siretstringMin length: 14Max length: 14- Meal Voucher siret. Format: 14 digits. subTypesarray[string]- The list of additional payment methods. Allowed values: mealVoucher_FR_edenred, mealVoucher_FR_groupeup, mealVoucher_FR_natixis, mealVoucher_FR_sodexo. nyceobject- NYCE details. processingTypestring- The type of transactions processed over this payment method. Allowed values: - pos for in-person payments.
- billpay for subscription payments, both the initial payment and the later recurring payments. These transactions have recurringProcessingModelSubscription.
- ecom for all other card not present transactions. This includes non-recurring transactions and transactions with recurringProcessingModelCardOnFile or UnscheduledCardOnFile.
 transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 paybybank_plaidobject- PayByBank Plaid details. logostring- Merchant logo (max. size 150kB). Format: Base64-encoded string. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 paymeobject- PayMe details. displayNamestring- Merchant display name logostring- Merchant logo. Format: Base64-encoded string. supportEmailstring- The email address of merchant support. paypalobject- PayPal details. directCaptureboolean- Indicates if direct (immediate) capture for PayPal is enabled. If set to true, this setting overrides the capture settings of your merchant account. Default value: true. payerIdstringMin length: 13Max length: 13- PayPal Merchant ID. Character length and limitations: 13 single-byte alphanumeric characters. subjectstring- Your business email address. paytoobject- PayTo details. merchantNamestring- Merchant name displayed to the shopper in the Agreements payToPurposestring- Represents the purpose of the Agreements created, it relates to the business type Allowed values: mortgage, utility, loan, gambling, retail, salary, personal, government, pension, tax, other pulseobject- PULSE details. processingTypestring- The type of transactions processed over this payment method. Allowed values: - pos for in-person payments.
- billpay for subscription payments, both the initial payment and the later recurring payments. These transactions have recurringProcessingModelSubscription.
- ecom for all other card not present transactions. This includes non-recurring transactions and transactions with recurringProcessingModelCardOnFile or UnscheduledCardOnFile.
 transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 referencestringMax length: 150- Your reference for the payment method. Supported characters a-z, A-Z, 0-9. sepadirectdebitobject- Sepa Direct Debit details. creditorIdstring- Creditor id transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 shopperInteractionstring- The sales channel. sodexoobject- Sodexo details. merchantContactPhonestring- Sodexo merchantContactPhone sofortobject- Sofort details. currencyCodestring- Sofort currency code. For example, EUR. logostring- Sofort logo. Format: Base64-encoded string. starobject- STAR details. processingTypestring- The type of transactions processed over this payment method. Allowed values: - pos for in-person payments.
- billpay for subscription payments, both the initial payment and the later recurring payments. These transactions have recurringProcessingModelSubscription.
- ecom for all other card not present transactions. This includes non-recurring transactions and transactions with recurringProcessingModelCardOnFile or UnscheduledCardOnFile.
 transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 storeIdstring- The ID of the store, if any. swishobject- Swish details. - This field is required only if you have a contract with Swish. Swish handles settlement directly with you (not through Adyen).
- If not specified then it's assumed that you are using Adyen's contract with Swish.You don't have a direct relationship with Swish.
 swishNumberstringMin length: 10Max length: 10- Swish number. Format: 10 digits without spaces. For example, 1231111111. ticketobject- Edenred (Brazil) details. requestorIdstring- Ticket requestorId twintobject- Twint details. logostring- Twint logo. Format: Base64-encoded string. typestring- Payment method variant. verificationStatusstring- Payment method status. Possible values: - valid
- pending
- invalid
- rejected
 vippsobject- Vipps details. logostring- Vipps logo. Format: Base64-encoded string. subscriptionCancelUrlstring- Vipps subscription cancel url (required in case of recurring payments) visaobject- Visa details. transactionDescriptionobject- Information regarding the transaction description. - You cannot configure the transaction description in the test environment. doingBusinessAsNamestringMax length: 22- The text to be shown on the shopper's bank statement. We recommend sending a maximum of 22 characters, otherwise banks might truncate the string. Allowed characters: a-z, A-Z, 0-9, spaces, and special characters . , ' _ - ? + * /. typestring- The type of transaction description you want to use: - fixed: The transaction description set in this request is used for all payments with this payment method.
- append: The transaction description set in this request is used as a base for all payments with this payment method. The transaction description set in the request to process the payment is appended to this base description. Note that if the combined length exceeds 22 characters, banks may truncate the string.
- dynamic: Only the transaction description set in the request to process the payment is used for payments with this payment method.
 wechatpayobject- WeChat Pay details. contactPersonNamestring- The name of the contact person from merchant support. emailstring- The email address of merchant support. wechatpay_posobject- WeChat Pay POS details. contactPersonNamestring- The name of the contact person from merchant support. emailstring- The email address of merchant support. 
- 204 - No Content- The request has been successfully processed, but there is no additional content. 
- 400 - Bad Request- A problem reading or understanding the request. detailstring- A human-readable explanation specific to this occurrence of the problem. errorCodestring- A code that identifies the problem type. instancestring- A unique URI that identifies the specific occurrence of the problem. invalidFieldsarray[InvalidFieldWrapper]- Detailed explanation of each validation error, when applicable. InvalidFieldobjectmessagestring- Description of the validation error. namestring- The field that has an invalid value. valuestring- The invalid value. requestIdstring- A unique reference for the request, essentially the same as - pspReference.responseobject- JSON response payload. statusinteger- The HTTP status code. titlestring- A short, human-readable summary of the problem type. typestring- A URI that identifies the problem type, pointing to human-readable documentation on this problem type. 
- 401 - Unauthorized- Authentication required. detailstring- A human-readable explanation specific to this occurrence of the problem. errorCodestring- A code that identifies the problem type. instancestring- A unique URI that identifies the specific occurrence of the problem. invalidFieldsarray[InvalidFieldWrapper]- Detailed explanation of each validation error, when applicable. InvalidFieldobjectmessagestring- Description of the validation error. namestring- The field that has an invalid value. valuestring- The invalid value. requestIdstring- A unique reference for the request, essentially the same as - pspReference.responseobject- JSON response payload. statusinteger- The HTTP status code. titlestring- A short, human-readable summary of the problem type. typestring- A URI that identifies the problem type, pointing to human-readable documentation on this problem type. 
- 403 - Forbidden- Insufficient permissions to process the request. detailstring- A human-readable explanation specific to this occurrence of the problem. errorCodestring- A code that identifies the problem type. instancestring- A unique URI that identifies the specific occurrence of the problem. invalidFieldsarray[InvalidFieldWrapper]- Detailed explanation of each validation error, when applicable. InvalidFieldobjectmessagestring- Description of the validation error. namestring- The field that has an invalid value. valuestring- The invalid value. requestIdstring- A unique reference for the request, essentially the same as - pspReference.responseobject- JSON response payload. statusinteger- The HTTP status code. titlestring- A short, human-readable summary of the problem type. typestring- A URI that identifies the problem type, pointing to human-readable documentation on this problem type. 
- 422 - Unprocessable Entity- A request validation error. detailstring- A human-readable explanation specific to this occurrence of the problem. errorCodestring- A code that identifies the problem type. instancestring- A unique URI that identifies the specific occurrence of the problem. invalidFieldsarray[InvalidFieldWrapper]- Detailed explanation of each validation error, when applicable. InvalidFieldobjectmessagestring- Description of the validation error. namestring- The field that has an invalid value. valuestring- The invalid value. requestIdstring- A unique reference for the request, essentially the same as - pspReference.responseobject- JSON response payload. statusinteger- The HTTP status code. titlestring- A short, human-readable summary of the problem type. typestring- A URI that identifies the problem type, pointing to human-readable documentation on this problem type. 
- 429detailstring- A human-readable explanation specific to this occurrence of the problem. errorCodestring- A code that identifies the problem type. instancestring- A unique URI that identifies the specific occurrence of the problem. invalidFieldsarray[InvalidFieldWrapper]- Detailed explanation of each validation error, when applicable. InvalidFieldobjectmessagestring- Description of the validation error. namestring- The field that has an invalid value. valuestring- The invalid value. requestIdstring- A unique reference for the request, essentially the same as - pspReference.responseobject- JSON response payload. statusinteger- The HTTP status code. titlestring- A short, human-readable summary of the problem type. typestring- A URI that identifies the problem type, pointing to human-readable documentation on this problem type. 
- 500 - Internal Server Error- The server could not process the request. detailstring- A human-readable explanation specific to this occurrence of the problem. errorCodestring- A code that identifies the problem type. instancestring- A unique URI that identifies the specific occurrence of the problem. invalidFieldsarray[InvalidFieldWrapper]- Detailed explanation of each validation error, when applicable. InvalidFieldobjectmessagestring- Description of the validation error. namestring- The field that has an invalid value. valuestring- The invalid value. requestIdstring- A unique reference for the request, essentially the same as - pspReference.responseobject- JSON response payload. statusinteger- The HTTP status code. titlestring- A short, human-readable summary of the problem type. typestring- A URI that identifies the problem type, pointing to human-readable documentation on this problem type.