{"id":431583,"date":"2025-07-29T22:12:57","date_gmt":"2025-07-29T15:12:57","guid":{"rendered":"https:\/\/www.swingfish.trade\/blog\/?p=431583"},"modified":"2026-06-12T09:57:26","modified_gmt":"2026-06-12T02:57:26","slug":"blueguardian-funding-simple-support-request-turned-into-fraud","status":"publish","type":"post","link":"https:\/\/www.swingfish.trade\/blog\/prop-trading-firms\/2025\/07\/blueguardian-funding-simple-support-request-turned-into-fraud\/","title":{"rendered":"BlueGuardian: Support ticket = Fraud?"},"content":{"rendered":"

… or, when kids try to run a financial institute. more stuff about BlueGuardian here<\/a><\/p>\n

The proprietary trading industry is built on one thing above all else: trust.<\/p>\n

Traders trust firms to evaluate them fairly. Firms trust traders to follow the rules. Without that mutual trust, the entire business model falls apart.<\/p>\n

Unfortunately, my recent experience with Blue Guardian demonstrated what happens when that trust is replaced by hostility, assumptions, and a customer support culture that appears to treat legitimate customers as suspects from the very beginning.<\/p>\n

How It Started<\/h3>\n

The issue itself was remarkably simple.<\/p>\n

I purchased a trading account through Blue Guardian. During the checkout process, the country field was automatically populated as Taiwan instead of Thailand.<\/p>\n

After noticing the mistake, I immediately contacted support.<\/p>\n

I did not request a refund.\u00a0I did not dispute the transaction.\u00a0I did not attempt to create multiple accounts.<\/p>\n

I simply explained that the country selection was incorrect and asked whether it could be adjusted to avoid possible KYC verification problems later.<\/p>\n

In other words, I was proactively trying to prevent future compliance issues.<\/p>\n

The Immediate Response: Fraud Accusations<\/h3>\n

Rather than assisting with the correction, support immediately began treating the situation as if it were evidence of fraud.<\/p>\n

\"\"<\/a><\/p>\n

At one point, I was informed that my purchase supposedly did not exist, despite the fact that I had an order number generated through their own system, ther system provided me with a trading account (basically shipped the product already) but for some reason there was no order?<\/p>\n

\"\"<\/a><\/p>\n

To help resolve the confusion, I provided evidence from my credit card application showing that Blue Guardian had successfully charged my card.<\/p>\n

Instead of acknowledging the possibility of an internal error, support escalated the accusations and suggested that the payment evidence had been manipulated.<\/p>\n

Think about that for a moment.<\/p>\n

A customer contacts support to fix a country field. The customer provides an order number.
\nThe customer provides payment evidence. The customer does not request a refund.<\/p>\n

Yet the response is not assistance, but repeated accusations.<\/p>\n

A Support Culture Problem<\/h3>\n

The most concerning aspect of this experience was not the technical issue itself.<\/p>\n

Mistakes happen. Websites malfunction.
\nPayment processors occasionally create confusion.<\/p>\n

What concerned me was the attitude displayed throughout the interaction.<\/p>\n

At every stage, the default assumption appeared to be that the customer was attempting something dishonest.<\/p>\n

Good customer support starts from a position of investigation and verification.<\/p>\n

Bad customer support starts from a position of accusation.<\/p>\n

In my case, it felt very much like the latter.<\/p>\n

Weeks later, the account was disabled entirely.<\/p>\n

This raises a reasonable question:<\/p>\n

I still have difficulty understanding the logic.<\/p>\n

The Bigger Pattern<\/h3>\n

After this experience, I began reading public reviews from other traders.<\/p>\n

A recurring theme appeared repeatedly:<\/p>\n