Sending Bitcoin Cash with SSP
This guide walks you through sending Bitcoin Cash from an SSP wallet end to end: five steps, one signing prompt on the device that starts the send, and one co-signature on the second device. It takes under a minute once you know the screens — and because the flow is identical to Sending Bitcoin with SSP, anything you learned there carries straight over.
It's written for your first BCH transaction, and worth re-reading before your hundredth — the address-checking habits are what keep funds safe. New to SSP? Set up your wallet first with Setting up your first SSP wallet, and if you've done Sending Litecoin with SSP this will feel familiar.
Before you start
Three prerequisites — none of them optional.
- Both paired devices are powered on and unlocked. SSP's 2-of-2 model needs signatures from both. If one device is dead, charging, or asleep, the send won't complete.
- You have the recipient address from a trusted source. Copy it — don't type it. Manual entry invites typos, and typos go to the wrong wallet permanently. Trusted sources include the recipient's verified channel, an invoice from a service you control, or a freshly-generated address from your own second wallet.
- You've decided on a fee tier. SSP shows the current network estimate, but the priority is yours. On Bitcoin Cash fees are tiny, but the same trade-off applies: faster confirmation costs a fraction more. More on this in step 3.
Step 1: Open the send screen
On the mobile app, tap the Send button on the home screen. On the browser extension, click Send in the top action bar.
If your SSP wallet holds multiple chains, the next screen asks you to pick the asset. Select Bitcoin Cash from the list. Confirm you're on the correct sub-account — SSP supports multiple accounts per chain, and the balance at the top of the send screen is what's available for that specific account, not the wallet total.
If the balance is lower than you expect, back out and verify which account you're sending from. Funds in another account are not spendable from this screen.
Step 2: Paste the recipient address
Paste the recipient's Bitcoin Cash address into the address field. Then — before anything else — verify the first 6 characters and the last 6 characters against the trusted source you copied from. Read them aloud if you need to. If even one character is off, stop, clear the field, and re-copy from the original source.
This isn't paranoia. It's defence against a well-documented pattern called address poisoning: an attacker generates a new address whose first and last characters look almost identical to one you've used before, then sends you a dust transaction so it appears in your history. The next time you copy "the same" address from your transaction list, you copy theirs instead. Your send goes to the attacker, with no recovery. We break this pattern down in Phishing attacks targeting crypto users.
Always copy from the original trusted source, never from history. The first-and-last-6 check is the same whether the address is a modern CashAddr (bitcoincash:q…) or an older legacy 1… address.
Step 3: Enter the amount and review the fee
Enter the amount. You can type in BCH, satoshis, or local fiat — SSP converts in real time. The screen also shows your spendable balance and an estimated total including fee, so you can see at once whether you have enough.
Below the amount, SSP shows three fee tiers:
- Low — cheapest, and fine for the vast majority of Bitcoin Cash transactions.
- Normal — the default; typically confirms within the next block or two.
- High — pays a premium for inclusion in the very next block. Useful for time-sensitive transfers or exchange deposits with deadlines.
Bitcoin Cash uses the same UTXO fee mechanics as Bitcoin, so if you want to understand why a transaction costs what it does, Bitcoin fee strategy in SSP applies directly.
Step 4: Sign on both devices
This is where SSP's 2-of-2 model fires. The transaction needs an independent signature from each of your paired devices before it can be broadcast. If the model is new to you, read What is 2-of-2 multisig? first.
On the initiating device (the one you've been using so far), review the summary one last time — recipient, amount, fee — and tap Confirm. The device signs locally. It does not yet broadcast.
Switch to the second device. Within a few seconds it should display a pending signing request: the same recipient, amount, and fee, alongside an Approve / Reject choice. Verify it matches the initiating device, then tap Approve. The second device signs and the two signatures are combined.
If the second device doesn't show the prompt within ~15 seconds:
- Make sure the SSP app is in the foreground (not just running in the background).
- Check that battery saver / data saver isn't blocking background sync.
- Confirm both devices have internet — Wi-Fi or mobile data; SSP needs a connection on each side to relay the request.
You can safely retry from the initiating device if needed. Until the second signature is in, no funds have moved.
Step 5: Watch the broadcast
Once both signatures are collected, SSP submits the transaction to the Bitcoin Cash network. The send screen flips to a Pending state and shows the transaction id (txid) — tap it to open a block explorer such as Blockchair.
Bitcoin Cash blocks target roughly 10 minutes — the same cadence as Bitcoin. Depth required depends on who is receiving:
- Casual transfers, small amounts — 1 confirmation is usually enough.
- Exchange deposits — most exchanges credit after 1–3 confirmations; check the exchange's policy.
- Large transfers — many recipients wait for 6 confirmations (~60 minutes) before treating the funds as final.
You can close the app at this point. The transaction is on the network; SSP doesn't need to stay open for it to confirm.
Bitcoin Cash-specific notes
A few things are particular to Bitcoin Cash and worth knowing:
- CashAddr is the modern format. Bitcoin Cash addresses today use CashAddr, which carries a
bitcoincash:prefix and a body that starts withq— for examplebitcoincash:q…. Older legacy addresses start with1…. SSP uses CashAddr, and the step 2 check is identical for either form. - Never confuse a BCH address with a BTC one. Legacy Bitcoin Cash addresses share the exact
1…shape that Bitcoin uses, because the two chains split from a common history — so it's possible to paste a Bitcoin address into a Bitcoin Cash send, or the reverse, without noticing. Funds sent to an address on the wrong chain are effectively lost, with no recovery. Thebitcoincash:prefix exists precisely to disambiguate, which is why SSP uses CashAddr. Always confirm you selected the Bitcoin Cash asset in step 1 and that the recipient gave you a Bitcoin Cash address. - Fees are very low. Bitcoin Cash uses large blocks and rarely congests, so a typical transaction costs a tiny fraction of a cent. The step 3 tiers still exist for the rare busy moment, but for everyday sends the difference is negligible.
For the canonical reference on the protocol, see the official Bitcoin Cash project site.
Sending via a connected dApp
If the send is triggered by a browser-based dApp rather than started inside SSP, you're using <span id="[walletconnect](/academy/how-to/sending-bitcoin-with-ssp#walletconnect)"></span>WalletConnect — the open protocol that lets external dApps request signatures from your SSP wallet via QR code or deep link.
The flow is the same from step 4 onward: both devices must independently sign before the transaction broadcasts. The dApp never sees your keys — it just gets the signed result.
The difference is in steps 2 and 3: the dApp pre-fills the recipient address, amount, and sometimes the fee. Your job changes from entry to observation — verify that the recipient and amount match what you intended to authorise in the dApp. If anything looks off, reject the request and start over from the dApp side.
Related reading
- The identical flow for Bitcoin: Sending Bitcoin with SSP.
- The security model behind step 4: What is 2-of-2 multisig?.
- New to SSP? Start with Setting up your first SSP wallet.
