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

# Payout links

> Send payouts without collecting banking details upfront by letting recipients choose how they get paid.

**Payout links** let you pay someone without collecting their banking details up front. A payout link is a secure, branded URL you send to the recipient. They use it to:

* Enter payout details
* Choose how they want to be paid
* Claim the payment

Every payout in Acclaim can include a payout link when recipient input is needed.

## How payout links work

Payout links are tied to **payouts**. When a payout is created:

* A payout link is generated automatically.
* If information is still missing, the link is how the recipient supplies it.
* The recipient completes what is required.
* The payout moves forward once the link flow is complete.

Payout links work whether the payout came from the **API**, **file uploads**, or other supported workflows.

## Lifecycle and statuses

Payout links follow the payout lifecycle, with extra states when the recipient must provide information.

### Key statuses

| Status                 | Description                                             |
| ---------------------- | ------------------------------------------------------- |
| `RequiresPayeeInfo`    | Recipient identity or profile details are still missing |
| `RequiresPayoutMethod` | Payout method or destination details are still missing  |

When the recipient finishes the link flow:

* Required information is collected.
* The payout leaves the `Requires_` states.
* Execution continues according to the rail and method, assuming all necessary approvals have been met.

## Recipient experience

Recipients get the link through the channels your organization enables, for example **email**, **SMS**, or **WhatsApp** (depending on account configuration).

When they open the link, they can typically:

* Enter required personal or business details
* Select a payout method
* Provide banking or wallet information
* Review the payout, including FX estimates when conversion applies

Validation runs in real time so issues are caught before submission.

## Security and authentication

You can require authentication before a recipient completes a link. Common options include:

* Email one-time passcode (OTP)
* SMS one-time passcode (OTP)
* Security questions

What applies is determined by your **account configuration** in the Acclaim Console.

## Notifications

Links can be sent automatically when a payout **needs recipient input** or **missing data** blocks execution.

Delivery may use **email**, **SMS**, **WhatsApp**, or other configured channels.

## After completion

After the payout is initiated or completes, the same link often becomes a **tracking** experience. Recipients may be able to:

* Track payout status
* View payment details
* Download receipts or remittance advice where available

Exact options depend on product configuration and corridor.

## FX and currency handling

If the payout involves currency conversion, recipients usually see **estimated exchange rates** and amounts in the relevant currencies so expectations are clear before they confirm.

## When to use payout links

Payout links work well when:

* You do not have recipient banking details yet.
* Recipients should pick method or destination (for example bank vs wallet).
* You want a low-friction experience without the recipient using your API.

### Common use cases

* Insurance claim payments to policyholders
* Provider or vendor payments
* Contractor or marketplace payouts

<Tip>
  Align your support team on which **channels** (email, SMS, and so on) you use for links so recipients know what to expect.
</Tip>

## Related resources

* [Payout lifecycle](./payout-lifecycle)
* [Payees](./payees)
* [Payout methods](./payout-methods)
* [File uploads overview](./file-uploads/overview)