A deposit support packet that protects your credentials
Send a traceable transaction record and a concise description of the discrepancy through the signed-in support channel. Evidence should let the recipient investigate without giving anyone access to your account.
Assemble the packet
| Record | Keep visible | Leave out of the shared copy |
|---|---|---|
| Withdrawal receipt | Status, destination and relevant reference | Unrelated balances and contacts |
| Chain record | Hash as selectable text, actual network and asset | Unrelated browsing or notifications |
| Receiving instructions | Intended address and memo requirement | Credentials or account recovery secrets |
| Case description | Expected result and observed result | Guesses presented as confirmed events |
Name the memo status explicitly. If you have a withdrawal reference, label it as such: an internal order identifier may not be a searchable chain hash. Preserve authentic originals privately while preparing redacted copies.
Write the cover message
Describe what you intended, what you submitted and what appeared afterward. Ask which additional ownership evidence is required. If a screenshot is missing, request an acceptable substitute rather than constructing a receipt from fragments. Clear records help investigation; they cannot create an entitlement to recovery.
For identity documents, verify the platform’s secure submission flow before uploading. A private chat account offering to collect them is insufficient evidence of an official channel.
Send it to the relevant account
Gate and Bybit profiles can orient readers using those venues. Readers whose deposit involved Binance, OKX or Bitget should likewise begin within their own official application.
Ask about review eligibility and terms before agreeing to further action. Support still needs to assess destination control and ownership.
Never attach these
Exclude a wallet seed phrase, private key, authenticator setup secret and authentication codes. Codes belong only in a genuine prompt you deliberately opened. Reject remote desktop invitations, unexpected wallet approvals and advance-payment rescue pitches. Review the authentication guidance if a request for evidence starts becoming a request for control.
Review memo and tag when comparing the receipt with receiving instructions.