Playbook
Merchant payout review workflow
Withdrawal request validation, balance reconciliation, and payout orchestration gates before execution.
01
Objective
Review withdrawal requests against merchant balance, recognition state, and payout orchestration controls before execution.
02
Prerequisites
- Payout policy separates recognized balance from in-flight payments.
- Dual-control for material outbound movement.
- Payout rail configuration documented.
03
Operational signals
- Payout request exceeds recognized merchant balance.
- Recent exception queue items unresolved for same merchant.
- Rail mismatch between settlement and payout configuration.
04
Decision points
- Approve, delay, or reject payout request.
- Partial payout versus wait for recognition.
- Manual treasury execution versus automated orchestration.
05
Escalation paths
- Treasury → finance controller for policy exceptions.
- Operations → engineering for balance computation discrepancies.
06
Failure modes
- Executing payout from detected-but-unrecognized funds.
- Skipping reconciliation check during urgent requests.
07
Recovery patterns
- Hold payout; reconcile merchant ledger state.
- Communicate delay with policy-backed reason.
- Resume orchestration after gates pass.
- Retries are normal. Webhook delivery is at-least-once. Design consumers to tolerate duplicates and out-of-order arrivals where possible.
- Asynchronous by design. Payers, chains, and your servers operate on different clocks. UI and finance should not assume synchronous finality.
- Eventual consistency. API reads, webhooks, and portal views may briefly diverge during transitions. Reconciliation jobs exist to converge truth.
Walkthroughs: /operations