First identify the unresolved stage
An existing Winum withdrawal problem may concern the request, an account decision or receipt of a purported payment. Those are different issues. Record the stage that is actually unresolved; do not treat a support message saying “processed” as proof that money arrived.
| Stage | Useful private record | Specific question |
|---|---|---|
| Request | Timestamp, requested amount/currency and displayed status | Is the request still pending or was it rejected? |
| Account decision | Dated explanation and relevant correspondence | What reason and policy version are being relied on? |
| Claimed transfer | Verifiable payment reference | What evidence shows the transfer was initiated? |
| Receipt | Matching receiving record | Does it concern the same amount, currency and transaction? |
Keep original documents privately. Share only what is necessary with an appropriate recipient. This site has no upload service.
What the published complaint policy says
Clauses 14.3–14.4 of the brand-facing terms state a one-working-day acknowledgement and a thirty-calendar-day substantive response, with possible extra time. They specify thirty days for account-related complaints, fourteen for gameplay matters and six months for other issues. These are policy assertions, not measured response times or a conclusion about enforceability.
For an existing dispute, identify the policy version and relevant category promptly. A procedural window should not be confused with the time a payment takes or with the full extent of legal rights. Qualified advice may be needed for the actual contract and jurisdiction.
An unanswered request can become a closure dispute
The public case analysis distinguishes payment delay, account closure and a mediator’s inability to obtain evidence. If account access stops, preserve the last available status and subsequent correspondence. Do not assume that the original delay and the later decision have the same explanation.
A chronology that an appropriate reviewer can use
Write one line per event: date/time and timezone, what was observed, what was communicated, where the original record is stored and what remains unanswered. Distinguish “the screen showed pending” from an inference about intent.
List contradictions precisely. If two messages give different reasons, retain both. If a reference cannot be matched to a receiving record, state that gap rather than inventing a transfer outcome.
Choose an escalation route by the facts
A contractual disagreement, suspected impersonation and suspected cybercrime are not interchangeable. For relevant suspected cybercrime, consult the official National Cyber Crime Reporting Portal. Its remit and process must fit the circumstances; reporting does not guarantee repayment.
No new payment, circumvention of account controls or replacement account is recommended here. The editor does not act as operator support, authenticate recovery offers or negotiate repayment.
Protect credentials and identity
Do not send this project passwords, one-time codes, full card numbers or identity documents. Treat unsolicited recovery offers and requests to pay an additional amount to release a supposed refund with caution. A useful case record contains the necessary facts, not unrestricted account access.