# Recipients

Before creating a transfer, your application needs to allow users to choose who will receive the funds. The receiving entity is often referred to as the recipient or beneficiary.

In your application, you can have your customer select a previously created recipient or they can create a new one. The data needed to create a new recipient is dependent on multiple factors, so we recommend using our dynamic forms option to ensure you gather all the required data.

The recipient account ID is used as the `targetAccount` value when creating a transfer as well as a quote.

## List current recipients 

Each profile contains a list of active recipients that the user has previously sent funds to. To present a list of recipients to the user, your application should [retrieve the list of recipients](/api-reference/recipient/recipientlist).

If you have already created a quote, use the `currency` query parameter to filter the response by the quote currency. Then, once the user selects a recipient, your application should update the quote with the selected recipient.

## Create a new recipient 

When creating a new recipient, the required data needed is impacted by many factors, such as the currency pair, where the account is based, the amount of the transfer, and more. Additionally, regional regulatory situations can sometimes cause recipient account requirements to change over time.

To make recipient creation more manageable, Wise provides **dynamic forms** that work in a predictable and functional way, ensuring you always gather the data needed. This feature uses a single endpoint to retrieve requirements which you can then display to your users.

The [Retrieve recipient requirements dynamically endpoint reference](/api-reference/recipient/recipientaccountrequirementsget) explains how to retrieve the account requirements, display and validate the data, and collect additional data when necessary.

Once the user has provided all required details, your application can submit the [Create recipient account request](/api-reference/recipient/recipientcreate).

Dynamic forms recommended
Using dynamic forms to gather recipient requirements is highly recommended for all integrations. Dynamic forms ensure your application always has the most up-to-date set of requirements for creating recipients and that the flow will have fewer errors.

Not including dynamic forms for recipient requirements may result in your application breaking upon a requirements change, with users no longer able to create or update that type of recipient. For help implementing dynamic forms in your application, please speak with the Wise team.

## Recipient verification

Wise validates the data submitted when creating a recipient to ensure that the submitted data conforms to the required schema and regional formatting rules, such as field lengths and format checks.

For certain currencies, additional verifications occur to confirm the existence of the account or that the recipient's account number and name match the records held by the destination bank.

Review our [Recipient verification guide](/guides/product/send-money/recipient-verification) to learn about how the Wise validation and verification checks work.

## Testing recipients in the Sandbox 

Because Sandbox is a test environment, there are some differences between Sandbox and Production. Please keep these in mind as you test.

While we validate some recipient account details in Sandbox, full bank detail validation can only be tested in Production.

Speak with the Wise team if you have further questions about testing recipients in Sandbox.