Withdrawal Checklist: 10 Steps to Reduce Operational Risk
Most payout issues are caused by skipped basics. This is a short operational checklist before every withdrawal.
Quick Checklist
- Check rail, address, and withdrawal threshold
- Confirm fee and net payout amount
- Store tx hash immediately after send
- For delays, verify chain status before support request
Checks before pressing withdraw
Start with rail, destination address, and minimum withdrawal threshold. These three checks prevent most operational errors.
For new addresses, a test transaction should be mandatory.
- Match rail and destination
- Check minimum withdrawal
- Run test on new address
Fee and net amount control
Before approval, check net amount after fee deductions.
For small withdrawals, fee impact can be significant.
- Check fee level
- Compare final net payout
- Consider batching withdrawals when reasonable
What to do if payout is delayed
If payout is delayed, verify on-chain status by tx hash first.
Then send one structured support request with full operation details.
- Verify tx hash in explorer
- Collect time/amount/rail/address
- Submit one complete support request
Support message template
A concise message speeds up resolution: account id, amount, rail, tx hash, and send time.
Avoid fragmented multi-message threads; they slow triage.
- One complete request
- Clear operation timeline
- Attach status screenshot
Related Guides
FAQ
Do I need test withdrawals every time?
Not always, but always for new addresses or new rails.
When should support be contacted for delay?
After checking on-chain status, so support receives accurate reference data.
What data helps support resolve issues faster?
Account id, amount, rail, destination, tx hash, and exact send timestamp.
Ready to continue to the platform?
Verify live operator terms and continue through the primary route.