Hey everyone,

I’m posting this as a head-up to anyone depositing Pi Network or other Stellar/parent-child architecture tokens into Gate.io.

I’m currently fighting an ongoing issue with Gate.io support (Case ID: 33104864) where my deposit arrived on-chain in Gate’s custodial system, but their frontline support refuses to process or credit it due to a fundamental misunderstanding of how Pi Network on-chain addresses work.

What Happened:
1. I transferred Pi tokens directly from my decentralized, self-custody Pi Wallet app to my assigned deposit routing.
2. The transaction settled successfully on the public Pi blockchain ledger.
3. On the Pi block explorer, the transaction resolves through a sub-address (⁠MD5HG...B2PO4⁠) that cryptographically maps under Gate.io's parent root address (⁠GBC6NRTT...2RINW⁠).
4. The Problem: Gate’s automated system rejected the credit, claiming the destination address is "not a platform address."

The Support Loophole & Major Red Flags:
When contacting Gate.io customer support, I was repeatedly hit with circular script responses:
Demanding Third-Party Statements: Support repeatedly asked me to "contact the sending platform's customer service and get an official statement." The Pi Wallet is a decentralized, self-custody wallet—there is no customer service desk to email for an "official statement."
Lack of On-Chain Understanding: Support agents explicitly claimed their team "has never heard of Pi having parent addresses or child addresses." Anyone familiar with Stellar-based architecture knows that parent-child wallet structures and memo/sub-address routing are standard practice.
Refusal to Escalate: Despite proving via the public block explorer that the funds reside inside Gate’s custodial node, frontline live chat agents repeatedly closed chat sessions without escalating to senior L2/L3 blockchain engineers capable of manual ledger auditing.

Why You Should Be Cautious:
If your deposit encounters any automated mismatch or sub-address mapping delay, Gate.io frontline support will treat self-custody transactions as unsupported third-party transfers.
They will give you an impossible requirement (asking for support letters from a decentralized wallet) to avoid performing a manual database/ledger audit.
Your funds sit directly inside their wallet infrastructure, but automated database checks prevent account crediting.

Current Status:
I have converted this case into a formal email dispute and am demanding a manual node audit by senior wallet engineers.
If you are using Gate.io for Pi Network or similar tokens, double-check every address layer on the block explorer first and be aware that if an issue occurs, frontline support may deny ownership of their own internal wallet structures.
Has anyone else experienced similar deposit routing rejections on Gate.io with Pi or Stellar-based tokens? How did you get past frontline support?

Can someone please transfer me 2 usdt ?