Mass Payout

Overview

How it works and why it matters

A mass payout distributes value to many beneficiaries through coordinated instructions, often using a batch file, API call or internal ledger. Each recipient remains a distinct obligation with its own validity, fees, errors and settlement evidence. Speed claims should be measured through successful beneficiary credits, not just API acceptance.

Important technical and operational details

It combines batch creation and funding controls with recipient-level validation, routing, status tracking, failure handling, and reconciliation.

Practical decision points

For a large batch, prevalidate every beneficiary before locking funds: destination format, network, asset, required tags or memos, available balance and authorized payout amount. The batch should have one stable submission identifier plus a distinct payout identifier for each recipient. If a process crashes halfway through, restart logic must detect which disbursements executed and which remain pending. Rejecting the whole operation after one bad address may be safer than partial execution in some workflows; in others, partial execution with a detailed result ledger is preferable. State this policy clearly and preserve enough evidence to reissue only truly failed items.

Related concepts

Payout; Payout Request

Further reading

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