I honestly thought the withdrawal delay was just some temporary issue until the platform suddenly acted like my account never existed.
I invested with this online trading company for about 3 months. Mostly crypto and forex trades. The dashboard always showed profits growing and my account manager kept encouraging me to compound instead of withdrawing early.
Everything changed the second I requested a larger withdrawal.
At first the withdrawal stayed “pending” for almost 10 days. Support kept giving excuses about liquidity providers, blockchain congestion, compliance reviews, all that stuff. Then yesterday I tried logging in again and got a message saying “account not found.”
Not suspended. Not under review. Literally account not found.
I thought maybe the site was bugged, so I tried resetting the password, but my email suddenly wasn’t recognized anymore either. What really scared me was seeing their Telegram support group disappear around the same time.
I started searching phrases like “investment platform account disappeared after withdrawal” and “broker says account does not exist after requesting payout” because the timing felt way too suspicious.
Apparently this is more common than I realized.
Some fake brokers reportedly remove or disable client accounts once victims start trying to cash out larger balances. Looking back, I noticed they were always enthusiastic when I deposited money, but the moment I mentioned withdrawing profits everything became slow and complicated.
One person in another scam discussion recommended Jim Recovery Team, so I contacted them mainly to understand whether the trading platform itself was even real or just a simulated dashboard. They helped me trace some details tied to the operation and explained how certain fraudulent investment sites recycle domains and delete user access after enough complaints or withdrawal requests happen.
If your investment account suddenly becomes “missing” right after a withdrawal attempt, take screenshots immediately and save every email/chat you still have. I almost kept waiting thinking it was a technical problem.
Top comments (0)