
Reading the SSP Key approval screen before you approve a send
When you send from SSP Wallet, the browser extension signs first and then hands the transaction to SSP Key on your phone. Nothing reaches the blockchain until your phone approves it too. That second approval is only worth something if you actually read what the phone shows you. Here is what each part of SSP Key's approval screen for a send means, and what to compare.
Why the second screen matters
SSP is a 2-of-2 multisig: SSP Wallet in your browser and SSP Key on your phone each hold one key, and both must sign. If your computer were compromised, malware could change what the extension builds or displays. SSP Key, on a separate device, reads the transaction itself instead of trusting a description sent with it.
That only helps if you look. What actually stops a transaction covers where this check sits among the other safeguards.
"Reading this transaction…"
When a request arrives, SSP Key doesn't show any amounts or addresses straight away. It shows a spinner with the line "Reading this transaction…", and underneath it a short status of what it's doing, such as "Looking up the coins being spent…", "Verifying SSP Wallet signatures…" or "Checking the network fee…".
During this step, the phone decodes the raw transaction using its own copy of your wallet's public key data. The sender, the destinations, the amounts and the fee all come from that decode, not from text supplied with the request. The slider stays disabled until decoding finishes, so you can't approve something the screen hasn't shown you yet.
If SSP Key can't decode the transaction, it doesn't guess. It shows "Can't verify this transaction", removes the slider and leaves only Reject. Reject it and try again from SSP Wallet.
What the screen shows
Once decoding finishes, a send has a few parts, top to bottom:
- Header. "Transaction Request", your sending address (shortened, with a small generated pattern image called an identicon), and a pill showing the chain's coin symbol, for example BTC or ETH. Check the chain first.
- The action. A plain line such as "Send 0.05 BTC", marked "Decoded on this device". For native coins it also shows an approximate USD value. For tokens, SSP Key doesn't show a USD estimate on purpose, so compare the token amount itself.
- To. The recipient address, with its own identicon.
- Network fee. The fee in the chain's native coin, with an approximate USD value when a price is available. Token transfers still pay the fee in the native coin.
- Advanced. Collapsed by default. It holds the full sending address and, for token or contract transactions, the token contract and raw transaction data.
On Bitcoin-style chains, SSP returns change to the sending address, so change isn't listed as a recipient. Only the destinations that actually leave your wallet are shown.
Comparing the address properly
The recipient card shows the first six and last six characters of the address in bold, with "…" in between. Tap the card and it expands to the full address. Lookalike addresses rarely match six characters at both ends, but the middle still matters, so expand it for meaningful amounts.
Compare the address with the original source (the invoice, the exchange's deposit page, the message from the person you're paying), not only with the browser. If something on your computer swapped the address before you pasted it, the browser and the phone will agree with each other, and both will be wrong. Clipboard hijackers explains how that happens. The phone guards against the browser changing the transaction after you entered it. It can't know which address you meant to pay.
Warnings you might see
SSP Key adds a banner or a red note when a transaction isn't a simple payment. The common ones:
- Multiple destinations. "This transaction pays N destinations", with each one listed. Only approve if you expected all of them.
- Unverified token. The token isn't in SSP Key's list, so the amount is shown in raw units. Check the token address.
- Unreadable contract call. The transaction calls a contract SSP Key can't fully read. The raw data is under Advanced.
- Contract call that also sends coins. It isn't a plain transfer: contract code runs with your funds attached.
- Approvals. Unlimited token approvals and collection-wide approvals get high-severity banners, because they grant spending rights rather than moving funds.
If you see any of these on what you thought was an ordinary send, stop. Blind signing explains why "I can't read this" should be treated as a reason to stop, not as a formality.
When something doesn't match: reject
If the chain, amount, recipient or fee differs from what you intended, or a warning surprises you, tap Reject below the slider. SSP Wallet will show "Transaction rejected by SSP Key", and the transaction won't be broadcast. Your funds stay where they were. Before retrying, re-copy the address from its source and check the browser for unfamiliar extensions.
When everything matches, drag the slider. A tap does nothing, and letting go before about 85% of the track springs it back. After a full slide, SSP Key asks for your biometrics or password before it signs and sends.
The honest summary
The SSP Key approval screen shows what your phone decoded from the actual transaction: the chain, the action and amount, the recipient, the fee, and warnings for anything that isn't a plain payment. Its job is to catch a transaction changed between your typing and your signing.
It has limits. It can't tell whether you copied the right address in the first place, token amounts come without a USD value, and some contract calls can only be shown as raw data. Read the screen every time, compare the address with its original source, and reject anything you don't understand. Rejecting costs nothing; approving the wrong thing can't be undone.


