The chain matters more than anything else on this screen. The same stablecoin exists on several networks, and a transfer sent to an address on a network the recipient does not use is generally unrecoverable. Sending to an @handle sidesteps the problem entirely, because the handle resolves to the right address on the right chain.
Send a payment
- 1
Tap Send from the home screen or the tab bar.
- 2
Choose the asset, and the chain if the asset exists on more than one.
Where a rail choice exists — Bitcoin on-chain or Lightning, USDT on Ethereum or TRON — the app asks which one you want, with the cost difference shown.
- 3
Enter the recipient: paste an address, scan a QR, pick a contact, or type an @handle.
An @handle resolves to the recipient's address on the chain you selected, which removes the wrong-network failure mode.
- 4
Enter the amount, in crypto or in your local currency.
- 5
Read the review sheet.
It shows the exact amount, the destination, the network fee, and any service fee. What you are approving is displayed in full — the app clear-signs rather than asking you to trust an opaque blob.
- 6
Approve with Face ID or your device passcode to sign.
Signing happens on your phone. Our servers prepare the unsigned context and relay the signed result; they never hold a key that could sign for you.
- 7
Track the transaction in Activity until it confirms.
Good to know
- Send a small test amount first when paying a new address for a large sum. The cost is a few cents of gas and it catches every category of address mistake.
- If the recipient screening flags an address, the send is blocked rather than warned about. That check runs before signing, and the broadcast is bound to the screened recipient so it cannot be swapped afterwards.
- Sending costs the blockchain's network fee, which goes to the network rather than to us. Sends themselves carry no SpendTheBits service fee.
Frequently asked
Blockchain transfers are final and cannot be reversed by anyone, including us. This is why the app screens recipients, guards against address poisoning, and shows the full destination on the review sheet before you sign.
Either the recipient address matched a sanctions or risk list, or a spending guardrail you configured — a per-transaction cap, an allowlist, or quiet hours — refused it. The app names which one.
Yes. Sending to any valid address on a supported chain works normally. @handles are a convenience for people who do use it.
Get SpendTheBits
A fully non-custodial wallet for 13 chains, free on iOS and Android. Your keys never leave your phone.