By mistake, the BTC of the BEVM Canary network was transferred to the Binance BSC recharge address. This article has a complete review of the accident process, evidence preparation and communication skills with customer service, for the reference of users who encounter similar problems.
The on-chain transaction status is ‘Confirmed’ (as shown in Figure 2), the funds have successfully reached the address generated by Binance, but the Binance account has never received the recharge.
The first complaint failed
In January 2025, I filed a complaint with Bian for the first time. The customer service replied ‘Cannot find the recharge record on the block’, it is recommended to check TXID or the network and resubmit. At that time, I could not provide valid evidence, and the complaint was rejected, mainly because I was busy at the time and had no intention of tossing (Figure 3).
The root cause: Binance uses the BSC browser to query the TXID of the BVM network, but of course it cannot be found. The ledgers of different public chains are completely independent, even if the TXID format is the same, it cannot be retrieved across the chain.
3. Turning point: It is found that the project has been upgraded
In May 2026, I reorganized the incident. At this time, I wanted to toss again and found that the BVM project has been fully upgraded and changed its name to GEB (GEB Network). View on the block browser in the Sent Records of the Little Fox Wallet that it can’t be opened (as shown in Figure 12).
If it is found that Binance’s recharge has not been self-service retrieval application, only the transaction ID can be filled in (Figure 4). But before, I was rejected because I could only fill in this field, so I finally decided to find a manual customer service.
4. Second appeal: complete communication with Binance customer service
On May 19, 2026, I contacted the human customer service again through the Binance official website, and transferred it according to the ‘Binance Wallet’ problem type. The following is a complete communication record (6 screenshots in total):
Stage 1: Connect to manual customer service
As shown in Figure 5: The customer service system transfer interface, select ‘Binance Wallet’ and successfully assign customer service CS Sylvie L, case ID 161774161
As shown in Figure 6: The customer service requires the details of the problem, I sent the UID, the transaction hash and the problem description
I told the customer service that the URL could not be opened, so I needed Binance to help me find a solution.
Stage 3: Explain the facts of the network upgrade
As shown in Figure 8: I explained to customer service that BVM has been upgraded to GEB, and provides official document channels as verification basis
Send content:
‘This transaction took place on the BVM Canary network (Chain ID: 1501). After investigation, I learned that the BVM project has been officially upgraded and renamed GEB (GEB Network). The old browser is no longer accessible, but you can go through the official GEB channel (such as documents.geb.network) Verify this information. On-chain records prove that the transaction is true and successful, and the funds are It is still in the top-up address you provided and has never been moved. I would like to ask Binance to assist in recovering the funds according to the facts of this project upgrade.’
Stage 4: Customer service internal feedback and assist in submitting a complaint
Figure 9: The customer service requires pre-stored 20 USDT in my spot account (as an asset recovery fee)
I immediately recharged 20 USDT in the Binance Spot account.
Stage 5: Successful submission of complaints
As shown in Figure 10: The customer service confirms that it has assisted in submitting the retrieval application, the application number CXF71hhq3luuJPL14O8
Official reply:
‘Thank you for your patience, the customer service has assisted you to submit the retrieval application, the application number [cxf71hhq3luaujpl 14O8] It is expected to review 2 working days and process funds in 12 weeks (the progress of the processing according to the relevant team may exist [advance])’
As shown in Figure 11: Screenshot of the ‘Application Details’ page in the Binance APP, it shows:
Processing status: under manual review, expected 30+ working days
5. Key experience and summary
5.1 Why can it be successful?
Essential factor
specific practice
Integrated chain of evidence
MetaMask “Confirmed” screenshot
Clear communication logic
Directly point out ‘the network is wrong’, rather than generally saying that ‘the account is not received’
Proactively provide verification methods
Give a link to the official GEB document, which is convenient for customer service to verify by yourself
Comply with customer service requirements
Pre-store 20 USDT fee as required, no conflict, no delay
have time to toss again
From the first appeal was rejected to the second appeal, the interval is more than one year, and the quality of Binance’s customer service is first-class
5.2 Guide to Common Misunderstandings and Pit Avoidations
❌ Misunderstanding 1: Think that TXID is common across chains → ✅ Correct understanding: TXID is only valid on the chain where it was generated.
❌ Misunderstanding 2: Relying on third-party browser screenshots as the only evidence → ✅ Correct practice: The core evidence is the internal transaction status of the wallet (metaMask shows ‘confirmed’), supplemented by browser screenshots.
❌ Misunderstanding 3: Repeatedly submit new work orders with the same content → ✅ Correct method: Continue to follow up on the basis of the original work order to avoid being merged or judged as duplicate by the system.
❌ Misunderstanding 4: Ignore the life cycle of the project side network → ✅ Correct practice: After finding that the browser cannot be opened, immediately check whether the project has been upgraded/renamed, and obtain new evidence.
5.3 Suggestions for users who encounter similar problems
The first time to take a screenshot of the wallet transaction details (including TXID, status, time, amount). This is the most unforgeable evidence.
Don’t just rely on a block browser. Try more third-party aggregation tools (such as HashHunter, etc.), and take screenshots to leave marks even if you fail.
Pay attention to the project side dynamics. Network upgrades and brand name change can often provide new verification channels.
When communicating with the Binance customer service, get straight to the point and explain ‘the network is wrong’ to avoid detours.
Prepare a handling fee of about 20 USDT (Binance usually charges for such wrong chain problems).
Be mentally prepared to wait for a long time. It may take weeks or even months from submission to funding to account.
6. Follow-up outlook
At present, my appeal has entered the manual review stage, and it is expected that the review will be completed within 2 working days, and then enter the fund processing queue (estimated 30+ working days). The Binance customer service clearly stated that ‘the relevant departments will need a long time to retrieve your funds’, which shows that the possibility of funds is very high.
I will continue to follow up and update this article after the final funds are credited. I hope my experience can provide an actionable reference for other users who are anxious about charging the wrong chain.
[…] InlastIn the process of Binance manual customer service, I have successfully submitted an application for BEVM Canary recharge recharge recharge, prepaid 20 USDT handling fee, and the work order officially entered the manual review queue. […]
1 Response
[…] InlastIn the process of Binance manual customer service, I have successfully submitted an application for BEVM Canary recharge recharge recharge, prepaid 20 USDT handling fee, and the work order officially entered the manual review queue. […]