Admin payout ops
Payout operations for reserve release, transfer control, and audit trace
Treat payout work like controlled platform finance: initialize rows from bound orders, re-check release readiness, release reserve intentionally, submit transfers, and mark paid only with a visible ledger trail.
Priority queue
Start with what is safe to move next
Admin payout work should surface risk and readiness immediately: which rows are still pending, which are blocked, and where reserve can safely move.
Ready to release
0 payout rows ready or near-ready
Release-ready work should feel like the obvious next action, not a hidden state inside a generic operations table.
0 actionable rowsReserve-aware
Blocked or pending
0 pending / 0 blocked
Operators need to separate “wait” from “intervene” at a glance, especially when disputes or quiet-period rules are involved.
Dispute-awareQueue health
Ledger trace
0 recent ledger events
Payout control becomes trustworthy when every movement is legible in the accounting trail, not only in the status label.
Audit visible
Initialization
Create payout rows only from orders that are genuinely ready
Initialization is the handoff from order fulfillment to money movement. It should stay explicit, not happen invisibly in the background.
Initialize seller payouts
Payout lifecycle pressure
No payout rows exist yetInitialize a payout from a confirmed order to start the queue.
Payout actions
Operate the selected payout without losing queue context
Re-check readiness, release reserve, submit transfer, and mark paid from one compact control area that still keeps the backlog visible nearby.
Operate selected payout
No seller payouts have been initialized yet.
Ledger trace
Keep the accounting trail visible from the same desk
Reserve release and payout completion only feel safe when the operator can still read the ledger events that explain what just happened.
No ledger transactions have been recorded yet.