POST /transfers

Default value: "application/json"

A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).

Header for authenticating through SCA

The ultimate sender of the funds of the transfer (ultimate debtor).

The last name of the individual.

Supported characters: [a-z] [A-Z] - . / — and space.

This parameter is:

• Allowed only when type is individual.
• Required when category is card.

The type of entity that owns the bank account or card.

Possible values: individual, organization, or unknown.

Required when category is card. In this case, the value must be individual.

Possible values:

• "organization"
• "individual"
• "unknown"

Default value: "unknown"

The first name of the individual.

Supported characters: [a-z] [A-Z] - . / — and space.

This parameter is:

• Allowed only when type is individual.
• Required when category is card.

A unique reference to identify the party or counterparty involved in the transfer. For example, your client's unique wallet or payee ID.

Required when you include cardIdentification.storedPaymentMethodId.

The full name of the entity that owns the bank account or card.

Supported characters: [a-z] [A-Z] [0-9] , . ; : - — / \ + & ! ? @ ( ) " ' and space.

Required when category is bank.

The address of the bank account or card owner.

The second line of the street address.

Supported characters: [a-z] [A-Z] [0-9] . - — / # , ’ ° ( ) : ; [ ] & \ | and Space.

Required when the category is card.

The first line of the street address.

Supported characters: [a-z] [A-Z] [0-9] . - — / # , ’ ° ( ) : ; [ ] & \ | and Space.

Required when the category is card.

The postal code. Maximum length:

• 5 digits for an address in the US.
• 10 characters for an address in all other countries.

Supported characters: [a-z] [A-Z] [0-9] and Space.

Required for addresses in the US.

The two-letter ISO 3166-2 state or province code. For example, CA in the US or ON in Canada.

Required for the US and Canada.

The two-character ISO 3166-1 alpha-2 country code. For example, US, NL, or GB.

The name of the city.

Supported characters: [a-z] [A-Z] [0-9] . - — / # , ’ ° ( ) : ; [ ] & \ | and Space.

Required when the category is card.

The date of birth of the individual in ISO-8601 format. For example, YYYY-MM-DD.

Allowed only when type is individual.

Contains information required for triggering transfer reviews.

Specifies whether you will initiate Strong Customer Authentication (SCA) in thePOST /transfers/approve request.

Only applies to transfers made with an Adyen business account.

Specifies the number of approvals required to process the transfer.

Your description for the transfer. It is used by most banks as the transfer description. We recommend sending a maximum of 140 characters, otherwise the description may be truncated.

Supported characters: [a-z] [A-Z] [0-9] / - ? : ( ) . , ' + Space

Supported characters for regular and fast transfers to a US counterparty: [a-z] [A-Z] [0-9] & $ % # @ ~ = + - _ ' " ! ?

The list of priorities for the bank transfer. This sets the speed at which the transfer is sent and the fees that you have to pay. You can provide multiple priorities. Adyen will try to pay out using the priority you list first. If that's not possible, it moves on to the next option in the order of your provided priorities.

Possible values:

• regular: for normal, low-value transactions.

• fast: a faster way to transfer funds, but the fees are higher. Recommended for high-priority, low-value transactions.

• wire: the fastest way to transfer funds, but this has the highest fees. Recommended for high-priority, high-value transactions.

• instant: for instant funds transfers within the United States and in SEPA locations.

• crossBorder: for high-value transfers to a recipient in a different country.

• internal: for transfers to an Adyen-issued business bank account (by bank account number/IBAN).

Required for transfers with category bank. For more details, see fallback priorities.

A reference that is sent to the recipient. This reference is also sent in all webhooks related to the transfer, so you can use it to track statuses for both parties involved in the funds movement.

Supported characters: a-z, A-Z, 0-9. The maximum length depends on the category.

• internal: 80 characters

• bank: 35 characters when transferring to an IBAN, 15 characters for others.

The other party involved in the funds transfer. A bank account, a balance account, a card, or a transfer instrument is required.

The unique identifier of the counterparty transfer instrument.

Contains information about the counterparty bank account.

Information about the owner of the bank account.

The last name of the individual.

Supported characters: [a-z] [A-Z] - . / — and space.

This parameter is:

• Allowed only when type is individual.
• Required when category is card.

The type of entity that owns the bank account or card.

Possible values: individual, organization, or unknown.

Required when category is card. In this case, the value must be individual.

Possible values:

• "organization"
• "individual"
• "unknown"

Default value: "unknown"

The first name of the individual.

Supported characters: [a-z] [A-Z] - . / — and space.

This parameter is:

• Allowed only when type is individual.
• Required when category is card.

A unique reference to identify the party or counterparty involved in the transfer. For example, your client's unique wallet or payee ID.

Required when you include cardIdentification.storedPaymentMethodId.

The full name of the entity that owns the bank account or card.

Supported characters: [a-z] [A-Z] [0-9] , . ; : - — / \ + & ! ? @ ( ) " ' and space.

Required when category is bank.

The address of the bank account or card owner.

The second line of the street address.

Supported characters: [a-z] [A-Z] [0-9] . - — / # , ’ ° ( ) : ; [ ] & \ | and Space.

Required when the category is card.

The first line of the street address.

Supported characters: [a-z] [A-Z] [0-9] . - — / # , ’ ° ( ) : ; [ ] & \ | and Space.

Required when the category is card.

The postal code. Maximum length:

• 5 digits for an address in the US.
• 10 characters for an address in all other countries.

Supported characters: [a-z] [A-Z] [0-9] and Space.

Required for addresses in the US.

The two-letter ISO 3166-2 state or province code. For example, CA in the US or ON in Canada.

Required for the US and Canada.

The two-character ISO 3166-1 alpha-2 country code. For example, US, NL, or GB.

The name of the city.

Supported characters: [a-z] [A-Z] [0-9] . - — / # , ’ ° ( ) : ; [ ] & \ | and Space.

Required when the category is card.

The date of birth of the individual in ISO-8601 format. For example, YYYY-MM-DD.

Allowed only when type is individual.

Contains the bank account details. The fields required in this object depend on the country of the bank account and the currency of the transfer.

Contains information about the counterparty card.

Contains information about the cardholder.

The last name of the individual.

Supported characters: [a-z] [A-Z] - . / — and space.

This parameter is:

• Allowed only when type is individual.
• Required when category is card.

The type of entity that owns the bank account or card.

Possible values: individual, organization, or unknown.

Required when category is card. In this case, the value must be individual.

Possible values:

• "organization"
• "individual"
• "unknown"

Default value: "unknown"

The first name of the individual.

Supported characters: [a-z] [A-Z] - . / — and space.

This parameter is:

• Allowed only when type is individual.
• Required when category is card.

A unique reference to identify the party or counterparty involved in the transfer. For example, your client's unique wallet or payee ID.

Required when you include cardIdentification.storedPaymentMethodId.

The full name of the entity that owns the bank account or card.

Supported characters: [a-z] [A-Z] [0-9] , . ; : - — / \ + & ! ? @ ( ) " ' and space.

Required when category is bank.

The address of the bank account or card owner.

The second line of the street address.

Supported characters: [a-z] [A-Z] [0-9] . - — / # , ’ ° ( ) : ; [ ] & \ | and Space.

Required when the category is card.

The first line of the street address.

Supported characters: [a-z] [A-Z] [0-9] . - — / # , ’ ° ( ) : ; [ ] & \ | and Space.

Required when the category is card.

The postal code. Maximum length:

• 5 digits for an address in the US.
• 10 characters for an address in all other countries.

Supported characters: [a-z] [A-Z] [0-9] and Space.

Required for addresses in the US.

The two-letter ISO 3166-2 state or province code. For example, CA in the US or ON in Canada.

Required for the US and Canada.

The two-character ISO 3166-1 alpha-2 country code. For example, US, NL, or GB.

The name of the city.

Supported characters: [a-z] [A-Z] [0-9] . - — / # , ’ ° ( ) : ; [ ] & \ | and Space.

Required when the category is card.

The date of birth of the individual in ISO-8601 format. For example, YYYY-MM-DD.

Allowed only when type is individual.

Contains the identification details of the card.

The issue number of the card. Applies only to some UK debit cards.

The year when the card was issued. Applies only to some UK debit cards.

Format: four digits. For example: 2020

The card number without any separators.

For security, the response only includes the last four digits of the card number.

The expiry month of the card.

Format: two digits. Add a leading zero for single-digit months. For example:

• 03 = March
• 11 = November

The month when the card was issued. Applies only to some UK debit cards.

Format: two digits. Add a leading zero for single-digit months. For example:

• 03 = March
• 11 = November

The unique token created to identify the counterparty.

The expiry year of the card.

Format: four digits. For example: 2020

The unique identifier of the counterparty balance account.

The category of the transfer.

Possible values:

• bank: a transfer involving a transfer instrument or a bank account.

• card: a transfer involving a third-party card.

• internal: a transfer between balance accounts within your platform.

• issuedCard: a transfer initiated by a Adyen-issued card.

• platformPayment: funds movements related to payments that are acquired for your users.

• topUp: an incoming transfer initiated by your user to top up their balance account.

Possible values:

• "topUp"
• "bank"
• "card"
• "platformPayment"
• "issuedCard"
• "internal"

The priority for the bank transfer. This sets the speed at which the transfer is sent and the fees that you have to pay. Required for transfers with category bank.

Possible values:

• regular: for normal, low-value transactions.

• fast: a faster way to transfer funds, but the fees are higher. Recommended for high-priority, low-value transactions.

• wire: the fastest way to transfer funds, but this has the highest fees. Recommended for high-priority, high-value transactions.

• instant: for instant funds transfers within the United States and in SEPA locations.

• crossBorder: for high-value transfers to a recipient in a different country.

• internal: for transfers to an Adyen-issued business bank account (by bank account number/IBAN).

Possible values:

• "regular"
• "crossBorder"
• "wire"
• "internal"
• "fast"
• "instant"

The date when the transfer will be processed. This date must be within 30 days of the current date.

Until the executionDate:

• The status of the transfer remains as received.
• The reason of the transfer remains as pending.

The timezone that applies to the execution date. Use a timezone identifier from the tz database.

Example: America/Los_Angeles. Default value: Europe/Amsterdam.

The date when the transfer will be processed. This date must be:

• Within 30 days of the current date.
• In the ISO 8601 format YYYY-MM-DD. For example: 2025-01-31

The amount of the transfer.

The amount of the transaction, in minor units.

The three-character ISO currency code.

The type of transfer.

Possible values:

• bankTransfer: for push transfers to a transfer instrument or a bank account. The category must be bank.
• internalTransfer: for push transfers between balance accounts. The category must be internal.
• internalDirectDebit: for pull transfers (direct debits) between balance accounts. The category must be internal.

Possible values:

• "internalDirectDebit"
• "bankTransfer"
• "internalTransfer"

Your reference for the transfer, used internally within your platform. If you don't provide this in the request, Adyen generates a unique reference.

The unique identifier of the source balance account.

If you want to make a transfer using a virtual bankAccount assigned to the balance account, you must specify the payment instrument ID of the virtual bankAccount. If you only specify a balance account ID, Adyen uses the default physical bankAccount payment instrument assigned to the balance account.

The unique identifier of the source payment instrument.

If you want to make a transfer using a virtual bankAccount, you must specify the payment instrument ID of the virtual bankAccount. If you only specify a balance account ID, Adyen uses the default physical bankAccount payment instrument assigned to the balance account.