Do Not Merge Several Winshark Cashouts Into One Complaint
Google surfaces a complaint involving multiple pending withdrawals. Each request can be held at a different point, so create one row per cashout and one shared chronology only for account-wide decisions.
Review Winshark withdrawalsBuild one row per request
Record ID, value, rail, destination suffix, creation time and current status. Never replace three IDs with one total amount.
Attach shared account events
Place verification requests or support decisions on the central chronology, then link them to every affected row. Keep request-specific cancellations and dispatches separate.
Close rows independently
Add a trace and receipt, reversal, or written rejection to the relevant row. The case is complete only when every original request has a final outcome.
Frequently asked questions
Can several requests share one support case?
Yes, but each withdrawal still needs its own evidence row.
Should the amounts be combined?
No. Combining them can hide a missing or duplicated payment.
What closes a pending row?
Usable receipt, documented return, cancellation or a reasoned final decision.
Last reviewed: 8 August 2026