Adding bitcoin to a custodial app looks like a one-step operation — copy an address, send, wait — but almost everything that can go wrong is decided before the first satoshi moves. The choices that matter are which route to use, which network that route runs on, and whether the receiving account is actually ready to accept a deposit. These matter more than the fee, because a bitcoin transaction cannot be reversed and a custodial provider may be unable to recover a send that lands on the wrong network.
Cash App exposes three routes for getting bitcoin in. An on-chain address accepts bitcoin on the Bitcoin network and settles only after miners confirm the transaction, which takes minutes to hours because blocks arrive roughly every ten minutes on average. A Lightning invoice settles near-instantly and carries no fee on Cash App, but both sides must support Lightning and the feature is not available to New York residents. A $cashtag is not a bitcoin address at all: it lets another Cash App customer pay dollars that are converted into bitcoin only if the recipient has switched that conversion on.
The first two routes differ in a way that is easy to misread. The on-chain address is a public key — the string you share so someone can pay you — while the private key stays with Cash App, which holds the coins in custody. Sharing an address is safe; sharing a PIN or a sign-in code is not. Keeping those two apart is the difference between telling someone where to send money and handing them access to the account.
The largest source of permanent loss is asset and network mismatch. A bitcoin address takes only bitcoin on the Bitcoin network. Bitcoin Cash, Ether, or any other asset sent there is unsupported, and bitcoin wrapped onto another blockchain is not the same as bitcoin on the Bitcoin network. Cash App’s disclosures state that sending an unsupported asset, or sending to an incompatible network, results in permanent and irreversible loss, and that Cash App cannot recover funds sent to incorrect, incompatible, or unsupported addresses or networks. The same trap runs in reverse: stablecoin deposits use a separate flow on their own networks, and crossing the two is the same class of mistake.
Fees are less frightening than the cautionary framing suggests. Cash App’s fee page lists no fee for receiving bitcoin, advertises no Lightning Network fees, and charges no fee for standard-speed withdrawals. The cost a depositor actually pays comes from the sending side — the exchange’s withdrawal fee or the network fee the sending wallet sets. What Cash App does not publish is a deposit minimum: the disclosures say it may require one, so when the receive screen shows a minimum, send more than that instead of testing the boundary.
Two habits make an ordinary deposit routine. Verify identity before anyone sends coins, so a deposit never sits in an account that cannot yet be used. And copy the address from the app today rather than reusing one saved from a screenshot: bitcoin.org’s privacy guidance is to use a new address for each payment, and a saved address may no longer be the one the app is showing. For a large first deposit, sending a small test amount and waiting for it to appear before moving the rest is cheap insurance against a wrong address or network, because the one thing that cannot be done afterward is taking the transaction back.
Source: BTCUSA.