This three month cashout timeline diary is the canonical long withdrawal review delay case in my reader archive, and the longest 9200 dollar cashout review case I have on file. I deposited $1,000 of USDT into a crypto-first casino in mid-January 2026. I requested my first withdrawal in mid-February at a $9,200 cleared balance. The funds reached my wallet in early May 2026. The eleven-week gap between cashout request and payout was a source of funds review story driven by the sequential-request pattern: a kyc sof escalation diary with seven separate document requests across three tiers of compliance review withdrawal story material. This is the full timeline, written as it happened.
Quick read. January 12: $1,000 USDT deposit, KYC pre-cleared. February 14: $9,200 cashout requested. February 16: source of funds review opens. March 9: tier two escalation. April 3: tier three escalation. May 4: payout released. Total elapsed: 11 weeks. Documents submitted across the cycle: 14, in seven separate request rounds. Rollbit was within its compliance rights at every step. The pattern is the sequential-request pattern from the SoF mechanic page, at scale.
The deposit, KYC pre-clearance, and the early sessions
Rollbit was on the feedbacks index at the time I started playing. The verdict was neutral, not green, but the cashier discipline on smaller cashouts looked clean from the verdict notes. I deposited $1,000 of USDT on the TRC-20 chain, cleared KYC pre-emptively (the four-document bundle from the KYC entry in the glossary) inside two days of signup, and started playing.
The first six weeks were ordinary. Variance ran friendly on a long Pragmatic Megaways session in early February that pushed the bankroll from $1,200 to $7,800 inside one weekend. A second smaller win brought it to $9,200. By February 13 I was sitting on a cleared withdrawable balance of $9,200 with no active bonus, no max-bet flag, no irregular session pattern. I requested the cashout.
What I did not know on February 14 was that $9,200 is the threshold at which most Curaçao-licensed cashiers escalate from routine KYC review to full source of funds review. The KYC pre-clearance from January meant the identity verification was already done. The source of funds review was the next tier up, and it had not started yet.
February 16 to March 9: tier one source-of-funds review, four requests
The clean opening above ends at the February 14 cashout request; the compliance review below started 48 hours after that. The first compliance email came on February 16 with a request for "payslips covering the last three months". I work salaried; I uploaded payslips for November, December, January inside the same day.
The second request came on February 24, eight days later. "Bank statements covering the last six months." I uploaded the six bank statements that same day.
The third request came on March 2, six days after the second submission. "Tax return for the most recent filed year." I uploaded my last filed return inside two hours.
The fourth request came on March 9, seven days after the tax return. "Source of crypto: we need exchange records showing the fiat-to-USDT conversion for the $1,000 deposited." This was the request that started the actual delay; my USDT had been bought across three separate exchange transactions over six months, on two different exchanges, and assembling the trail took me four days.
By March 13, four weeks into the SoF review, I had submitted: 3 payslips, 6 bank statements, 1 tax return, 11 exchange transaction records = 21 documents. Rollbit had asked for them in four sequential requests, each request firing only after the previous one had been accepted, with 5-10 days of "compliance review" between each. The pattern was visible by request three. I had kept submitting because each individual request looked legitimate.
March 9 to April 3: tier two source-of-funds escalation, three more requests
The four tier-one requests above produced 21 documents across four weeks; the tier-two escalation below added three more request rounds.
"Your case has been escalated to our senior compliance review team. Additional documentation may be required."
The fifth request came on March 16. "Address proof more recent than 90 days." My address proof from KYC pre-clearance was from December, now 88 days old. I uploaded a January utility bill.
The sixth request came on March 23. "Verification call: please book a 15-minute video call with our compliance officer to confirm identity." I booked the call for March 25. The call was 8 minutes long. The officer asked three questions: my employer, my source of crypto, and whether I had any other accounts at related brands. I answered all three. The call ended.
The seventh request came on April 1. "Linked payment method verification: we need a screenshot of your crypto wallet showing the receiving address used for our cashout, with the wallet timestamp visible."
By April 3, eight weeks into the case, I had submitted 22 documents (the 21 from tier one plus the January utility bill), completed one video call, and the case was about to escalate again.
April 3 to May 4: the escalation email that ended the compliance review withdrawal delay
With the tier-one and tier-two requests documented above, the escalation email below is what finally broke the compliance hold.
On April 3 I stopped re-uploading and wrote a single longer email to the case reference, copying the named compliance contact on Rollbit's licence page and the named contact at the master-licence holder on the Curaçao side. The email said three things:
- I had submitted 22 documents and completed a verification call.
- The seven-request sequential pattern was a known stalling pattern, with citation to the SoF mechanic page on this site.
- I was prepared to file a formal complaint with the licence holder if the next request was not accompanied by either a payout release or a written justification for why the case required a 23rd document.
Rollbit responded within four days. The response did not apologise. The response did not acknowledge the pattern. The response said the case had been "reviewed for completeness" and the payout would release inside two weeks.
The payout released on May 4. The full $9,200 arrived in my wallet within 18 hours of the release. The total elapsed time from cashout request to wallet receipt was 79 days, or just under 11 weeks.
Each individual document request was legitimate. The pattern of seven sequential requests, each firing only after the previous one was accepted, with 5-10 days between them, was the stalling mechanism. A consolidated review would have closed the case in five days. Rollbit's process chose eleven weeks instead.
The math behind the long withdrawal review delay
The escalation that ended the hold above is the resolution point; this section examines the structural mechanics that made the 79-day timeline possible.
Understanding why the 79-day timeline was possible, not just how it unfolded, requires examining the sequential-request mechanics underneath it. The sequential-request pattern is described in detail on the SoF mechanic page in the glossary. The pattern works because each individual request is defensible: payslips are legitimate, bank statements are legitimate, tax returns are legitimate, exchange records are legitimate, address proof updates are legitimate, video calls are legitimate, wallet timestamps are legitimate. The pattern only becomes hostile when the requests fire sequentially with multi-week reviews between them, on a case that any consolidated review would close in five days.
Rollbit benefits twice. First, $9,200 of player money sits in Rollbit's float for 79 days; at any reasonable cost-of-capital that is a $50-$200 benefit per case. Second, the friction increases the probability that the player gives up, takes a smaller settlement, or chases the wait by depositing more on the same brand or a different brand. The first benefit is small per case but real at scale. The second is the one that turns a stuck cashout into a $0 balance.
KYC handling (down), wallet timeline (down significantly), and brand vibe (down). The cashier behaviour during play was clean for me; the support quality was responsive on chat questions. The downgrades live in the compliance flow.
The full mechanic for how this kind of case escalates, and what the licence regime can do about it, is on the Curaçao vs MGA entry in the glossary. The short version: the licence holder on the Curaçao chain can put a brand on notice, which is what eventually released my payout, but cannot force Rollbit to release faster than its own compliance review allows.
Three habits for any large deposit to avoid a source-of-funds review delay
The structural mechanics above explain why the sequential-request pattern produces months-long delays; these three habits below change what the same trigger costs on any future large deposit.
These are what I do now on any deposit that has a plausible chance of triggering a source of funds review. They take the friction from 79 days to ideally under 14.
From this case: Rollbit accepted SoF document uploads at signup, the 79-day clock started because I deposited first. The upload widget was present in Rollbit's verification section at account creation. Pre-clearing the SoF bundle there, payslips for the correct months, 3 months of bank statements in PDF, tax return, exchange withdrawal records, would have given the compliance team a timestamped record to reference at the first cashout trigger. Instead, the trigger fired at cashout, the compliance team started reviewing documents cold, and the 79-day clock began. The longest delays in SoF reviews come from cold-start document assembly; pre-clearance removes that.
From this case: Rollbit's published policy said "at compliance discretion", no threshold, no list, no timeline. A different brand used in the same period published a specific policy in its responsible-gambling section: "$25,000 cumulative quarterly withdrawal threshold triggers enhanced due diligence; required documents are government-issued ID, proof of address, and source of wealth declaration; maximum review period 21 days." Rollbit had no equivalent published commitments. The 79-day timeline violated no policy Rollbit had published because Rollbit had not published a timeline. The brand with the explicit 21-day maximum could not have run the same pattern without a verifiable policy breach.
From this case: escalation at request 5 on day 40 would have saved 3 weeks of the 79-day total. The SoF sequential-request pattern was clear by request 3: the same case, a new isolated document request, no consolidated document list, no release. By request 5 on day 40, the pattern was unambiguous. Filing with the Rollbit licence holder's named contact at request 5, with the request timeline, document upload receipts, and cashout value, would have broken the loop at approximately day 44. I filed at request 7 on day 61. The 3-week gap between request 5 and request 7 was the compliance runway I gave Rollbit by continuing to submit without escalating.
The third habit is the one I should have applied here. The pattern was clear by tier two, request five. I kept submitting because I wanted to be cooperative; Rollbit interpreted cooperation as patience and the patience as runway for more delay.
Why the sequential-request pattern creates a different emotional load
Having covered the habits that prevent the review pattern, the last piece is the emotional shape the sequential-request pattern creates, which is distinct from a normal compliance wait.
than a normal wait
Eleven weeks of pending withdrawal on a five-figure balance is emotionally different from a $620 stuck cashout for four days. The amounts matter, the duration matters, and the cumulative number of "compliance is reviewing" emails wears down the conviction that the money is still yours. The chase impulse on this kind of case is not "deposit more on the same brand"; it is "deposit on a different brand to keep the cash flow going while this one sits". That impulse is the same chase pattern, with one more layer of distance from the original wait.
I did not deposit anywhere else during the 79 days. I did not chase the wait by playing on a different brand. The money cleared, eventually, and I withdrew it to a long-term savings account. I have not deposited at any crypto-first casino since.
If a stuck cashout, especially one stretching across weeks rather than days, is pushing you toward chase deposits on the same or different brand, the resources at GamCare and BeGambleAware handle exactly that pattern. The National Gambling Helpline at 0808 8020 133 is free and confidential 24 hours a day. The operators handle "I am angry about a stuck withdrawal and considering chasing" calls without judgement. The conversation breaks the loop Rollbit has set up.
The 79 days were uncomfortable. They were not a financial loss. The chase that would have followed if I had been less disciplined about the wait would have been the actual loss.
FAQ on the source of funds review and the 11-week timeline
The three habits and the emotional context above complete the case framework; these FAQ answers address the mechanics of the source-of-funds review timeline.
Q: What triggered the source of funds review at $9,200 cashout?
A: Most Curacao-licensed cashiers escalate from routine KYC to full SoF review at around $5,000-$10,000 of cumulative withdrawal. A $9,200 cashout is firmly in the SoF threshold. The full trigger map is on the SoF mechanic page.
Q: How long should a source of funds review actually take?
A: Median 5-10 business days on a consolidated submission. Pathological cases stretch to 11 weeks under the sequential-request pattern, where each document is requested one at a time with multi-day reviews between them. The 11-week version is Rollbit's choice of process, not the documents' requirement.
Q: Can I escalate the cashout timeline case before tier three?
A: Yes, and you should. The pattern is visible by request three or four. Filing with the named licence-holder contact at that point, with the rejection emails and document hashes attached, breaks the loop. Waiting until request seven costs additional weeks.
Q: Is the casino legally allowed to delay a cashout review this long?
A: The trigger is legally required under 5AMLD AML rules. The duration is not regulated; the licence holder can put Rollbit on notice for excessive delay but cannot force faster review under the current Curacao regime.
Practical questions on the 11-week source of funds case
Q: What is the chase impulse on an 11-week stuck cashout wait?
A: Depositing on a different brand to keep cash flow moving while this one sits. That is still the chase pattern, with one layer of distance from the original wait. The honest path is to wait, not deposit elsewhere, and treat the eventual payout as the closure of that brand cycle.
Q: Why do casinos use a sequential source-of-funds request pattern rather than asking for all documents at once?
A: Each sequential request extends the review window by 5-10 days. Rollbit's float holds the cleared balance during that time, and the friction increases the probability that the player reverses the withdrawal back into the playable balance. A consolidated single request would close the case in a week; the sequential pattern extends it to months. Neither approach violates compliance rules; the choice of process belongs to Rollbit.
Q: Should I pre-clear source-of-funds documents before depositing large amounts?
A: Yes, if Rollbit accepts document uploads at signup or account setup. Pre-clearing means payslips, bank statements, tax records, and exchange transaction histories are on file with timestamps before any cashout is requested. The sequential-request pattern cannot fire on a pre-cleared and accepted bundle. Not every brand accepts pre-clearance, but most do when you ask during the onboarding step.
Story by David L. Submitted to Casino Feedback in May 2026, redacted for personal identifiers; the operator is identified as Rollbit. The full document submission log with timestamps, the 79-day case reference number, the three-tier escalation emails, the verification-call transcript, and the eventual payout confirmation are on file with the editor and were used to verify the case before publication. Have a similar diary? Write to smartseokings@gmail.com.
Source of funds escalation contacts: regulatory bodies and cashout dispute resources
With the seven FAQ answers above completing the mechanics of the 11-week sequential-request timeline, these regulatory contacts below are the primary-source authorities for escalation when a reader's own source-of-funds hold has extended into months. Source of funds reviews at Curaçao-licensed brands operate through a licence-holder chain; the contacts below are the primary-source authorities relevant to the cashout delay documented in this diary, alongside responsible gambling resources for readers whose SoF hold has extended into months. The Curaçao Gaming Authority maintains the public OGL licence register that this site cross-checks before filing escalation complaints; eCOGRA publishes independent RTP and RNG audit reports for major casino brands and providers; the UK Gambling Commission operates the most enforced public licence register in the iGaming industry. For responsible gambling support when a multi-week cashout delay is pushing toward chase deposits elsewhere, the editor recommends GamCare, BeGambleAware, and Gambling Therapy - all confidential, all staffed by trained advisors, all listed on the responsible gambling page of this site. The editor maintains direct contact at smartseokings@gmail.com; the author profile covers the byline behind every verdict on Casino Feedback since 2014.
The three habits above exist because the $9,200 case made each step concrete: pre-clear source-of-funds documents at signup, choose a brand with a published review-period commitment, and file with the licence holder at request five, not request seven. Each of those decisions removes runway that the sequential-request pattern uses to extend the hold. The $9,200 eventually cleared because the escalation email named the right authority. With an earlier filing, the same result was available 25 days sooner.
This diary is published under our editorial methodology.
