Freeze the original request
Save the withdrawal ID, CAD amount, method, destination suffix and request time. Add every status change, support reply and KYC submission to one chronology.
Do not cancel and recreate a payout merely to refresh the screen. That can restart the queue and separate the new request from earlier evidence.
Count elapsed time in business days and note weekends separately so the timeline reflects the operator's published processing window rather than a rough calendar estimate.
- Request ID
- Status timestamps
- Verification receipts
Locate the current owner
Ask whether the request is waiting for KYC, finance review, approval, processor dispatch or the receiving provider. Each stage needs a different proof and next action.
Once the cashier says sent, request the processor or bank reference. A completed label alone does not prove the destination credited the funds.
- Review owner
- Dispatch reference
- Receiving-account result
Escalate one measurable outcome
State the amount, elapsed business time and exact missing stage. Request either the remaining verification item, approval date, dispatch reference or documented return reason.
Keep one support case. A concise timeline is more useful than several tickets with different descriptions.
Questions players ask
Should I cancel a delayed PowerUp withdrawal?
Not until support confirms why and what will happen to the processing clock.
What should support identify?
Ask which exact stage owns the request and what evidence remains.
Does completed mean received?
No. Reconcile the dispatch reference with the destination account.
Last reviewed: 9 August 2026