Withdrawal Requests

Use this page to review, approve, and monitor withdrawal requests safely.

Interface Reference #

Purpose #

• Control payout flow quality and speed.
• Enforce risk, KYC, and policy checks before approval.
• Keep rejection rates transparent and explainable.

Processing Flow #

1. Open Operations > Withdrawal Requests.
2. Filter by pending/approved/rejected and date range.
3. Prioritize oldest pending and high-value requests.
4. Validate KYC status, account flags, and payment destination.
5. Approve/reject with reason notes.
6. Track post-action settlement confirmation.

Required Checks Before Approval #

• KYC/verification level meets payout policy.
• Account has no unresolved risk flags.
• Withdrawal amount and frequency are within thresholds.
• Destination account format and ownership checks pass.

Rejection Handling #

When rejecting, include clear reason category:

• KYC incomplete
• Policy threshold exceeded
• Risk/compliance block
• Payment destination mismatch

Troubleshooting #

• Pending queue growth: review reviewer capacity and approval bottlenecks.
• Rejection spike: verify if policy rules were updated.
• User disputes after rejection: ensure detailed reason is logged.

Best Practice #

Use dual control for high-value withdrawals: one reviewer + one final approver.