TreasuryConcepts
Payout
The Payout entity in Treasury.
A payout is a money-movement instruction: a debit from one of your linked
funding accounts that arrives in a recipient's bank account over ACH, same-day
ACH, RTP, or wire. Payouts are created in two phases — initiate (which
returns a transaction in pending state and may require a 2FA code) and
confirm (which submits to the rail). Until confirmed they can be cancelled
without cost.
Lifecycle
pending—POST /treasury/sendreturned a transaction ID. Funds are not yet moving. If your security rules require it, this state also returns anapproval_requiredflag and you must collect a 6-digitsecurity_codefrom the operator.processing—POST /treasury/send/confirmaccepted the transaction and handed it to the rail. RTP completes in seconds; ACH typically settles in 1–3 business days; wires same day.completed— Rail acknowledged settlement. The associated Settlement record is created and thesettlement.createdwebhook fires.failed/returned— Rail rejected or returned the payment (insufficient funds, bad routing, bank closure). The transaction stays visible viaGET /treasury/transactions/{id}.cancelled—POST /treasury/send/cancelran before confirmation. No rail submission, no fee.
Relationships
A payout belongs to one Recipient (which owns the destination Bank Account) and debits one of your linked funding Bank Accounts. It produces exactly one Settlement on success. If the recipient is a US contractor and the year-to-date total crosses the IRS threshold, payouts also feed the Tax Document (1099) calculation.
Fields that matter
recipient_id(uuid) — destination recipient.source_account_id(string) — your linked bank account being debited.amount(integer, USD cents,> 0) — the amount to send.method("ach" | "same_day_ach" | "rtp" | "wire") — rail. Affects fee and settlement window; RTP and wire are irreversible.memo(string, ≤500 chars) — appears on the recipient's bank statement where the rail supports it.notes(string, ≤2000 chars) — internal-only, never sent to the rail.