> For the complete documentation index, see [llms.txt](https://docs.optty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optty.com/payouts/payouts.md).

# Overview

A payout is a transfer of funds **from** a merchant **to** a beneficiary — for example settling a marketplace seller, paying a contractor, or refunding outside the original transaction. Optty Payouts gives merchants a single, standardised way to initiate those transfers across any payout-enabled provider on their account.

## How payouts work in Optty

Payouts in Optty are automated from the merchant's existing balance held with the APM provider. Optty itself never touches the funds — exactly the same model as collections. When a payout is initiated, Optty translates the request into the provider's API call, submits it on the merchant's behalf, and tracks the lifecycle (scheduled, processing, paid, failed) using the provider's webhooks.

The benefit is consistency: a merchant integrates once with Optty and can disburse through any payout-enabled APM using the same UI, CSV format and lifecycle states, rather than learning each provider's payout API individually.

## Initiating payouts

There are two ways to send payouts today:

* **Bulk upload (CSV)** — a manual workflow in the portal. Upload a CSV of payouts in Optty's standard format and the entire batch is dispatched and tracked automatically. See [Bulk Payouts](/payouts/bulk-payouts.md).
* **Single payouts via API** — supported today; public documentation is being prepared and will be linked here when published. If you would like an early walkthrough or want to begin integrating now, email **<support@optty.com>** and we can arrange a demo.