Transfer funds
Versions 1 and 2 of the Transfers API are deprecated. If you are just starting your implementation, use the latest version.
Starts a request to transfer funds to:
Adyen sends the outcome of the transfer request through webhooks.
To use this endpoint:
- Your API credential must have the TransferService Webservice Initiate role.
- The account holder must have the required capabilities.
Reach out to your Adyen contact to set up these permissions.
Headers
A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).
Header for authenticating through SCA
Request body
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.
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 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.
Your reference for the transfer, used internally within your platform. If you don't provide this in the request, Adyen generates a unique reference.
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.
Response
Accepted - the request has been accepted for processing, but the processing has not been completed.
The unique identifier of the source balance account.
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 direction of the transfer.
Possible values: incoming, outgoing.
The ID of the resource.
The unique identifier of the payment instrument used in the transfer.
Additional information about the status of the transfer.
Your reference for the transfer, used internally within your platform. If you don't provide this in the request, Adyen generates a unique reference.
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 result of the transfer.
For example:
- received: an outgoing transfer request is created.
- refused: the transfer request is rejected by Adyen for one of the following reasons:
- Lack of funds in the balance account.
- Transfer limit exceeded.
- Transaction rule requirements violated.
- authorised: the transfer request is authorized and the funds are reserved.
- booked: the funds are deducted from your user's balance account.
- failed: the transfer is rejected by the counterparty's bank.
- returned: the transfer is returned by the counterparty's bank.