Payouts and payment tools

The planned payout tools focus on recurring business tasks: preparing several payments, distributing an incoming payment, and reusing details that rarely change.

Batch Pay and payroll#

Batch Pay is intended to let a team prepare payments to multiple recipients in one workflow. Possible uses include contractors, contributors, affiliates, and marketplace payouts.

The longer-term aim is to let recipients use different supported receiving preferences while the payer funds the batch using available supported assets.

Preparing payments together does not establish that they will execute as one on-chain transaction. Transaction handling, partial failures, and retry behavior need release-specific documentation.

Split Payments#

Split Payments are intended to distribute one incoming payment according to predefined settlement rules. For example, a marketplace might allocate an illustrative $100 payment as follows:

This example explains the allocation concept. It does not account for fees or define a released split-payment contract.

The focus is business settlement and payment distribution. Different destination preferences may become possible in a more advanced implementation.

Saved Payment Templates#

A template would let you keep commonly used details, such as a recipient, amount, source asset, preferred output, and description.

For example, a regular design payment could start from the same recipient and description each month. You would still review the current amount, recipient preferences, and quote before authorizing a new payment.

Before building a payout process#

These tools depend on reliable payment execution and transaction management. Launch dates, batch limits, scheduling, and retry behavior have not been specified for release.

Use the roadmap to understand the direction and payment activity for the baseline tracking model.