BNB Transfer Dispute – Flow Diagram

MEXC → BNB Chain TX → Crypto.com (Foris DAX CAN ULC) → Alleged Onward Wallet • Evidence & Authorities
Transfer Path Evidence Trail Regulatory/Authority Dispute/Allegation

Source Exchange: MEXC

BNB purchased after swapping ETH; then sent to a Crypto.com deposit address.
Actor

Prior Step: ETH → MEXC

ETH moved from Crypto.com to MEXC then swapped to BNB.
Etherscan: 0x5e9dd086…fa857
Chain Evidence

BNB Smart Chain Transaction

Hash: 0xa5fece5f…8aa50
Reported as arriving “pending” at Crypto.com wallet.
On-Chain

Destination: Crypto.com

Foris DAX CAN ULC (OSC registrant)
#1700, 421 7th Ave SW, Calgary, AB T2P4K9
Actor

Alleged Onward Movement

Funds allegedly moved from Crypto.com to a wallet not tied to the complainant.
Allegation

Support & Replies

Crypto.com stated the 8.9 BNB transfer “failed” and did not provide a return tx hash. Support Chat IDs: 5d54d409-5e05-49b9-902e-d281c9aba25f  |  3e6484eb-7f68-4e60-9f1f-65545ba08282
Evidence

Evidence Links (Screens/Logs)

BNB transfer & “pending” arrival screenshots
Support discussions & follow-ups
ETH → MEXC transfer evidence

OSC Registrant Details

Foris DAX CAN ULC registrant references (as cited): Ref 1Ref 2OSC listing
Individuals: Becky CantaneseJames Grabow
Context

Authorities/References

OSC Whistleblower Ref: 467-540
RCMP Case: 2025-55862
Reference
Notes & Sources: All links and identifiers (tx hashes, Drive exhibits, registrant refs) were pulled from your Ombudsman PDF. If any Drive permissions change, the buttons will still display but may require access. :contentReference[oaicite:0]{index=0}