Payout

Overview

How it works and why it matters

A payout is an outgoing disbursement to a beneficiary. It begins as an instruction but becomes financially complete only after the applicable execution and receipt policy is met. Recipient eligibility, asset/network details, approval thresholds and duplicate prevention are crucial.

Important technical and operational details

Use cases include seller proceeds, contractor earnings, customer withdrawals, rewards, refunds, and partner shares, each with distinct authorization, funding, fees, and reporting.

Practical decision points

In implementation, a payout should move through distinct states: requested, validated, authorized, submitted, executing, completed or exceptional. Each transition should have an event source and timestamp, and no automated retry should violate balance reservation or approval thresholds. Some providers return a queued instruction before any chain transaction exists. Others return a transaction ID that still needs network monitoring. Refunds, vendor payments and payroll may share the payout execution infrastructure while preserving different commercial reasons and accounting classifications. For international payouts, beneficiary eligibility and reporting duties remain independent of how quickly the receiving chain confirms the transfer.

Related concepts

Payout Request; Payout Processing

Further reading

• docs.oxapay.com documentation
• docs.oxapay.com documentation