Crypto.com × MEXC — Public Evidence Index (OBSI/OSC/CSA)

Quick Links

Index folder: OMBUDSMAN directory
Document 1: folder — email cover PDF + images
Document 2: folder — email cover PDF + images
Document 3: folder — images (deposit addr + support link)

OBSI complaint portal screenshots: 1 · 2 · 3
OBSI email threads (PDF): Complaint #1 · Complaint #2

On‑Chain Hashes & Addresses (verifiable)

Paste any hash into a block explorer (bscscan.com, etherscan.io) to independently verify the transaction and balances.

Network	Type	Hash / Address	From → To	Amount / Time	Source
BNB Chain (BEP‑20)	Transaction	`0xa5fece5f0b357621a8351b5d0ab60dfc19cade2edbdab1e859a66286a9d8aa50`	`0x4982085C9e2F89F2eCb8131Eca71aFAD896e89CB` (MEXC 13) → `0xE85A0D2D4511f071c831Ebf9749F75Cf63b2980d`	8.99899 BNB · 2025‑07‑18 15:27:09 UTC	BscScan PDF (screenshot)
Ethereum	Transaction	TXID in screenshot	`0x4354a020803761d...E9B756` (tagged “Crypto.com 12”) → `0x4790291673cc62be6a19fcfcd268235f75bd7bc8`	~1.883901 ETH · 2025‑07‑18 03:41:11 PM UTC	Etherscan screenshot
BNB Chain	Address	`0xE85A0D2D4511f071c831Ebf9749F75Cf63b2980d`	Funding by MEXC 13; outflow recorded in table	See recent tx list in screenshot	BscScan address screenshot
BNB Chain	Deposit Address (App)	`0x4790291673cc62be6a19fcfcd268235f75bd7bc8`	Crypto.com app → user deposit (BNB BEP‑20)	QR + address shown	App screenshot
BNB Chain	Support Link	`0xa5fece5f0b357621a8351b5d0ab60dfc19cade2edbdab1e859a66286a9d8aa50`	Crypto.com support shared BscScan link	—	Notification screenshot

If you have additional TXIDs (e.g., the full Ethereum TXID from the Etherscan screenshot), append them here for completeness.

OBSI Complaint — Overview

According to the emails and portal screenshots, the complainant alleges unauthorized movement of BNB/ETH and coordination between exchanges. OBSI requested two items: (1) the initial complaint letter/date to Crypto.com and (2) Crypto.com’s final decision letter; it also indicated it cannot access Google Drive links due to IT policy.

OBSI email thread — Complaint #1 (PDF), Complaint #2 (PDF)
OBSI portal submission — Page 1, Page 2, Success

Note: The complainant considers these intake requirements suspicious given the in‑app nature of Crypto.com support; OBSI states these are standard intake practices.

Document 1 — Contents (Summary)

Email cover PDF

Allegation: “MEXC and Crypto.com are in collusion … illegal movement of securities/crypto” (email cover).
Attached: OMBUDSMAN DOC 1.docx and a ZIP of screenshots (images directory mirrors many of these).
Key artifacts: BscScan/Etherscan screenshots, exchange UI records, and corporate registry look‑ups.

BscScan transaction PDF preview — BNB transfer (MEXC 13 → 0xE85A…2980d) — TXID listed.

Etherscan withdrawal screenshot — ETH withdrawal from address tagged “Crypto.com 12” to user deposit.

Document 2 — Contents (Summary)

Email cover PDF

Continuation of the complaint and escalation requests to OBSI personnel.
Screenshots of Crypto.com chat showing missing BNB and escalation to internal teams.

Crypto.com support chat opening — Support chat: report of missing BNB and pending withdrawal availability.

Crypto.com support escalation screenshot — Support indicates escalation; no timeframe provided.

Document 3 — Contents (Summary)

Crypto.com app shows BNB deposit address 0x4790…5bd7bc8 (BEP‑20).
Phone notification shows Crypto.com support sharing the BscScan TXID link for the BNB transfer.

Crypto.com app deposit address (BNB) — BNB deposit address exposed in‑app.

Notification with BscScan link — Support message containing the BscScan link to TXID 0xa5fece…9d8aa50.

How to Report / Escalate

OBSI — Consumer complaints intake; attach PDFs/images instead of cloud links.
OSC (Ontario) — osc.ca
CSA — Find your provincial/territorial regulator via securities-administrators.ca → “Investor Tools” → “File a Complaint”.