WARNING: Bitget Wallet Card has a critical backend bug swallowing Solana USDT deposits (Technical Proof inside) SCAM

Hey everyone,

I wanted to publish a detailed warning about a major engineering failure and ongoing asset-freezing loop occurring with the co-branded Bitget Wallet Card (issued by DCS Card Centre in Singapore). If you are topping up this card using USDT over the Solana network, your funds are at high risk of being swallowed by their internal bridge bots with zero automated recovery.

Here is the complete timeline, the technical breakdown of the bug I uncovered, and how their support team is using automated loops to avoid fixing a clear database discrepancy.

1. The Initial Failure (July 6)

I initiated a card top-up of 255.67 USDT via the Solana network.

On-Chain Status: Absolute SUCCESS (Tx: 2PjE8YossQ2EcpH38eL64fyij82mqo7iUGuNXiJgPxuqU9...). The funds successfully hit their custodial swap infrastructure.

The App Discrepancy: The internal Card ledger recorded the top-up as "Success," but the main payment wallet history marked it as "Failed." My available spending balance remained at exactly $0.

The UI Crash: Attempting to click the transaction logs inside the app to view details results in a permanent, broken black screen.

1. The Support Runaround & AI Gaslighting (Ticket #3243796)

I opened an urgent ticket. The automated AI assistant ("Mia") immediately generated a completely fabricated transaction history, claiming I had manually swapped the USDT for a tiny fraction of SOL, trying to blame me for the missing balance.

Once I pushed past the bot, a human agent (Beryl) officially apologized in writing for the AI providing fake information and explicitly confirmed: "We have successfully located the transaction on the blockchain."

However, instead of manually adjusting the database ledger, the support chain shifted tactics. They dropped a generic template claiming that based on their "overall risk assessment framework and compliance standards," the deposit could not be processed, and they would have to initiate a manual refund with "no confirmed timeline," passing the blame to their external card supplier (DCS).

1. The Smoking Gun: Isolating the USDT Auto-Swap Bug (July 10)

Today, I received a small reward payout and decided to isolate the variables to see if this was actually a compliance issue or just broken code. I ran two distinct control tests on the exact same card:

TEST 1 (Solana USDT): I attempted a card top-up using 12.91 USDT over Solana. The exact same glitch occurred instantly. The ledger says success, the actual spending balance stayed at $0.1, the details screen went completely black, and the tokens vanished into their system.

TEST 2 (Solana USDC): I attempted a card top-up using 3.69 USDC over Solana. Because the card natively operates on USDC infrastructure, this transaction bypassed their internal swap routing. It credited my card balance instantly without errors.

The Conclusion

This proves with 100% certainty that this is not a compliance or risk issue. Bitget's backend auto-swap router—which is supposed to automatically convert incoming Solana USDT to USDC before crediting the card ledger—is fundamentally broken. It swallows the USDT, deposits it into their system swap bots, fails to trigger the database credit to the card, and causes the front-end UI to crash into a black screen.

Right now, Bitget and DCS Card Centre are holding a total of 268.58 USDT of my perfectly clean, white, taxed money. They are sending rapid template emails every time I update the ticket with technical logs just to reset their helpdesk SLA timers.

If you own a Bitget Card, DO NOT top it up with USDT. The bridge is a black hole. If you absolutely have to use this incredibly expensive and buggy service, only use native USDC, or move your operational capital away from their ecosystem entirely until their engineering teams learn how to sync an API ledger properly.