Start the clock from the correct event
Record the request ID, amount, method, destination suffix, creation timestamp and account time zone. If another withdrawal was paid immediately before it, retain that receipt because the published wording can anchor the next processing window to the prior paid request.
Count business days rather than calendar days and separate operator review from provider settlement. A processed status does not establish that a bank, card, wallet or chain controls the funds.
- Request and preceding payout
- Business-day calendar
- Operator status
- Processor or transaction reference
Keep one state for every request
Classify each cashout as pending, verification required, approved, paid, rejected or returned. Do not replace a pending ID with the newest ID in the ledger, and avoid cancellation and resubmission unless support explains the effect on the queue.
If documents are requested, pause the expected-payment calculation until the complete file is acknowledged. The processing condition and the verification condition are separate gates.
Escalate only after reconciling receipt
When the published window has passed, send support the request ID, previous payout reference, completed KYC confirmation and elapsed business days. Ask for the current owner of the request and the next dated action.
Close the record only when funds reach the owned destination or a documented return appears in the balance. Keep any fee and currency conversion as separate lines.
Questions players ask
What processing window do the located SpinIt terms describe?
Three business days after the request or after the last withdrawal was paid, subject to completed checks.
Does processed mean received?
No. Match the casino reference to the receiving bank, wallet or blockchain record.
Can repeated requests affect the timeline?
The published wording references the last paid request, so record and space requests carefully.
Last reviewed: 10 August 2026