Record request conditions
Save amount, currency or asset, method, account and bonus state, request ID and displayed estimate.
This page is a decision worksheet built around a specific search task. It separates observable records, first-party wording and unresolved claims so the conclusion can be checked again after a material change.
Name the current stage
Distinguish reversible pending, document hold, risk or bonus review, rejected, approved, dispatched and missing.
Ask for route-specific evidence
Require a TXID for crypto or a traceable bank or wallet reference after dispatch, joined to the correct destination.
Close the timeline
Record usable receipt, fees and net amount. Keep operator and payment-rail time separate while reporting the full total.
Processed is not the same as received
Do not cancel repeatedly without understanding queue consequences. Preserve the case and request one specific status or trace. Reconcile any partial payment before opening another request.
Questions this page resolves
When is a Syndicate withdrawal complete?
When usable funds arrive in the intended account.
Can crypto still be delayed?
Yes, by KYC or operator review before broadcast.
What should support provide after dispatch?
A route-specific trace or TXID.