Skip to main content

Initiate a cashout

post/cashouts

Initiates a cashout request

Endpoint destination URL
https://balanceplatform-api-test.adyen.com/btl/v4/cashouts
Click to copy
amountobjectRequired

Contains the amount of the cashout, in minor units.

counterpartyobject

Contains information about the counterparty of the cashout transfer.

creationDatestring

The date and time when the event was triggered, in ISO 8601 extended format. For example, 2025-03-19T10:15:30+01:00.

descriptionstring

Allowed and returned only when you provide the counterparty.transferInstrumentId field.

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

If you do not provide a description, Adyen generates a description automatically. This generated description is not returned in the response.

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

feeobject

Contains the currency and value of the cashout fee, in minor units.

instructingBalanceAccountIdstringRequired

The unique identifier of the balance account that initiates the cashout request.

referenceForBeneficiarystring

Allowed and returned only when you provide the counterparty.transferInstrumentId field.

The reference that is sent to the recipient of a cashout transfer. This reference is also sent in all webhooks related to the cashout transfer, so you can use it to track the status of the transfer.

If you do not provide a reference for the beneficiary, Adyen generates one automatically. This generated reference for the beneficiary is not returned in the response.

Supported characters: a-z, A-Z, 0-9.

transferInstrumentIdstringDeprecated

Use counterparty.transferInstrumentId instead.

The unique identifier of the counterparty transfer instrument.

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.

  • 400 - Bad Request

    The request is malformed or is not in the expected format.

  • 401 - Unauthorized

    The API credential used in the request is invalid.

  • 403 - Forbidden

    The API credential does not have the right permissions.

  • 404 - Not Found

    The requested resource was not found.

  • 422 - Unprocessable Entity

    A request validation error.

  • 429 - Too Many Requests

    Request rate limit exceeded.

  • 500 - Internal Service Error

    An unrecoverable error occurred while trying to perform the request.