Some third-party wallet apps may not recognize the QR codes generated by the Bitcoin.com Wallet in the “receive token” flow (eg. Receive ETH, Receive MATIC). You can fix this problem by switching to “legacy address.”
Table of contents
Why the error
If a third-party wallet app shows an error when scanning your Bitcoin.com Wallet-generated cryptocurrency address, the most likely explanation is that the third-party wallet app hasn’t implemented Ethereum Improvement Proposal-681. EIP-681 is a standardized way of representing various transactions, especially payment requests, in ETH and ERC-20 tokens as URLs (in this case, a URL embedded in a QR code). Part of the motivation for EIP-681, and the reason the Bitcoin.com Wallet has implemented it, is to ensure that users don’t accidentally send a token to the wrong chain (eg. sending USDC that lives on Ethereum to an Avalanche or Polygon address), which may result in loss of funds.
A wallet app that has properly implemented EIP-681 would, after scanning the QR code for an address or payment generated by a wallet that has implemented EIP-681, warn the user if the token they are trying to send does not match the receiving address’s blockchain.
A wallet app that has NOT implemented EIP-681 would, after scanning the QR code for an address or payment generated by a wallet that has implemented EIP-681, show an error.
How to fix it
In the receive flow, switch to legacy address by:
Tapping the hamburger button, which will open a menu.
Selecting “Use legacy address.” This will generate a new QR code for your address, which will be readable even by third-party wallets that don’t support EIP-681.
For more information, you can contact email@example.com or click the chat icon on the bottom right part for assistance.
Customer support team is available 24/7 to assist.