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

# Destinations

> Configure destinations and holder relationships for payouts

A destination defines where fiat funds land when an off-ramp completes. Each destination is tied to a customer and holds:

* Account holder details and banking information for the receiving bank.
* The relationship between the customer and the account holder (see below).

Supported rails depend on the destination's country and currency — see [Coverage](/get-started/coverage).

## Holder relationships

When you add a destination to a customer, you have to specify the relationship between the customer and the account holder.

### Self payments

If the customer is sending funds to their own destination, use:

| **Relationship** | **Use case**                                                                             |
| :--------------- | :--------------------------------------------------------------------------------------- |
| `SELF`           | Withdrawals and transfers to the customer's own destination for personal or business use |

### Third-party payments

If the customer is paying a third party (suppliers, employees, family members, etc.), use one of these relationships:

| **Relationship**     | **Use case**                                                                      |
| :------------------- | :-------------------------------------------------------------------------------- |
| `HOLDING_COMPANY`    | Parent or controlling company that owns the customer entity                       |
| `SUBSIDIARY_COMPANY` | Subsidiary or controlled entity owned by the customer                             |
| `BRANCH_OFFICE`      | Branch, regional office, or division of the customer's organization               |
| `BUSINESS_PARTNER`   | Strategic partners, joint venture collaborators, or business associates           |
| `SUPPLIER`           | Vendors, suppliers, or service providers for goods and services purchased         |
| `CUSTOMER`           | Customer's clients for refunds, rebates, or other customer obligations            |
| `CREDITOR`           | Lenders, financial institutions, or parties to whom the customer owes money       |
| `DEBTOR`             | Parties who owe money to the customer (collections or debt settlements)           |
| `FRANCHISEE`         | Franchisees operating under the customer's brand or business model                |
| `EMPLOYEE`           | Employees or contractors paid by the customer (payroll, salaries, reimbursements) |
| `RELATIVE`           | Family members of the customer (remittances, personal transfers)                  |
| `FRIEND`             | Personal acquaintances of the customer (P2P transfers, gifts)                     |

Example: a Brazilian company paying a supplier in the United States would create a destination with `SUPPLIER` as the holder relationship and provide the supplier's US bank details.

## Related resources

<CardGroup cols={2}>
  <Card title="Transactions" href="/concepts/transactions">
    Route payouts to a destination.
  </Card>

  <Card title="Customers" href="/concepts/customers">
    The legal entity that owns the destination.
  </Card>

  <Card title="Nested Payments" href="/compliance/nested-payments">
    Why holder relationships have to be disclosed and accurate.
  </Card>

  <Card title="Coverage" href="/get-started/coverage">
    Supported rails by country and currency.
  </Card>
</CardGroup>