> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slash.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Recipients and destinations

> Recipients, their destinations, supported transfer types, and information requests.

A recipient is a person or business your legal entity pays. A destination is
one set of payment instructions that belongs to a recipient. Recipients are who
you pay; customers are who pays you.

```text theme={null}
Recipient
├── Bank-account destination
├── International-wire destination
└── Information request
```

Keep the resources separate:

* Keep identity and address data on the recipient.
* Pick a payment rail through a compatible destination.
* Send an information request when the recipient should supply its own
  payment or tax details.

## Recipients

A recipient's `recipientType` is `contact` for a person (shown as "Person" in
the Slash dashboard) or `vendor` for a business. Archive one with
[`POST /v2/recipients/{recipientId}/archive`](/api-reference/recipients/archive);
archiving also hides its destinations from default list results.

A recipient id names who you pay, not where the money goes, so transfers take
a `destinationId`.

## Destinations

Each destination belongs to one recipient. Create one with
[`POST /v2/destinations`](/api-reference/create-a-destination), and filter
[`GET /v2/destinations`](/api-reference/list-destinations) by `recipientId` to
list a recipient's. There are two types:

* `bank_account` for ACH, domestic wire, or realtime payments
* `international_wire` for international wires

Use a destination's `supportedTransferTypes` rather than inferring
compatibility from `type`, and only send to it while its status allows the
rail.

Archive a destination without affecting its recipient with
[`POST /v2/destinations/{destinationId}/archive`](/api-reference/destinations/archive).
Both list endpoints omit archived resources unless `includeArchived=true`.

## Information requests

[`POST /v2/information-requests`](/api-reference/request-payment-details)
emails the recipient a secure form asking for any combination of destination,
address, and tax details. A recipient can have one `pending` request at a
time.

What the recipient submits is stored on the recipient, not on the request:

* destinations appear in [`GET /v2/destinations`](/api-reference/list-destinations)
* the address replaces the recipient's `address`
* tax details are returned by
  [`GET /v2/recipients/{recipientId}/tax-details`](/api-reference/recipients/tax-details)

`submitted` means the recipient has submitted the form at least once and can
keep editing it. Only a `pending` request can be canceled.

<Note>
  An information request can ask for `crypto_address`, but crypto destinations
  are not returned as destinations and cannot be used to create a transfer.
</Note>

A destination or information request requested under a recipient it doesn't
belong to returns `not_found`, the same as an id that doesn't exist.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.