---
title: "Designate a beneficiary account and transfer the benefactor's current balance"
method: POST
path: "/setupBeneficiary"
tags: ["General"]
---

# Designate a beneficiary account and transfer the benefactor's current balance

`POST /setupBeneficiary`

Defines a benefactor and a beneficiary relationship between two accounts. At the time of benefactor/beneficiary setup, the funds in the benefactor account are transferred to the beneficiary account, and any further payments to the benefactor account are automatically sent to the beneficiary account. A series of benefactor/beneficiaries may not exceed four beneficiaries and may not have a cycle in it.

## Request body

- SetupBeneficiaryRequest
  - `destinationAccountCode` string, required — The destination account code.
  - `merchantReference` string — A value that can be supplied at the discretion of the executing user.
  - `sourceAccountCode` string, required — The benefactor account.

## Response `200`

OK - the request has succeeded.

- SetupBeneficiaryResponse
  - `pspReference` string — The reference of a request. Can be used to uniquely identify the request.
  - `resultCode` string — The result code.
  - `submittedAsync` boolean — Indicates whether the request is processed asynchronously. Depending on the request's platform settings, the following scenarios may be applied: * **true**: The request is queued and will be executed when the providing service is available in the order in which the requests are received. * **false**: The processing of the request is immediately attempted; it may result in an error if the providing service is unavailable.

## Other responses

- `202` — Accepted - the request has been accepted for processing, but the processing has not been completed.
- `400` — Bad Request - a problem reading or understanding the request.
- `401` — Unauthorized - authentication required.
- `403` — Forbidden - insufficient permissions to process the request.
- `422` — Unprocessable Entity - a request validation error.
- `500` — Internal Server Error - the server could not process the request.

## Changes

- **2023-03-22** (v3) `40f3741a6483` — 8 breaking
  - the request's body type/format changed from ``/`` to `object`/``
  - the response's body type/format changed from ``/`` to `object`/`` for status `200`
  - the response's body type/format changed from ``/`` to `object`/`` for status `202`
  - the response's body type/format changed from ``/`` to `object`/`` for status `400`
  - …4 more
- **2021-08-07** (v3) `f45176226426` — 1 info
  - api tag `General` added
- **2021-07-09** (v3) `e38d0becc386` — 2 info
  - the endpoint scheme security `ApiKeyAuth` was added to the API
  - the endpoint scheme security `BasicAuth` was added to the API
- **2021-04-10** (v3) `a5193c3dc852` — 5 info
  - added the optional property `status` to the response with the `400` status
  - added the optional property `status` to the response with the `401` status
  - added the optional property `status` to the response with the `403` status
  - added the optional property `status` to the response with the `422` status
  - …1 more
- **2021-03-05** (v3) `ce23a0d8c048` — 6 info
  - added the media type `application/json` for the response with the status `400`
  - added the media type `application/json` for the response with the status `401`
  - added the media type `application/json` for the response with the status `403`
  - added the media type `application/json` for the response with the status `422`
  - …2 more

[Full history](https://skmtc.dev/adyen/apis/fundservice/changes/setupBeneficiary/post.md)

---

[API](https://skmtc.dev/adyen/apis/fundservice.md) · [All operations](https://skmtc.dev/adyen/apis/fundservice/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/adyen/fundservice/revisions/9b4819139946/schema)