Radar Chat Brings Non-Custodial Bitcoin Payments Into Encrypted Messaging

If crypto ever wanted a shot at mass payments, it had to merge money with the conversations that trigger it. Radar Chat is taking that swing: a new iOS and Android app that lets you send Bitcoin directly inside an encrypted chat, without touching a custodial middleman or hopping between apps.

Built by the team behind Cake Wallet—though structured as a separate company—Radar uses the open-source Signal Protocol for end-to-end encrypted messaging. The company stresses it’s developed independently from Signal, but says it financially supports the project. The result: familiar privacy tech paired with a self-custody wallet where users hold their own keys and move funds over Bitcoin’s Lightning Network.

What stands out is the integration tightness. Payments happen in the same thread as the conversation, with private keys controlled by the user rather than a service. Radar positions this as a natural fit: the people you message are often the ones you pay, so split bills, tips, and quick reimbursements shouldn’t require copy-pasting addresses or bouncing to a separate wallet.

Under the hood, Lightning does the heavy lifting, enabling fast, low-fee transfers. While Lightning is often associated with tiny spends, Radar says it has successfully tested transactions up to $5,000. The ceiling isn’t an app-imposed limit; it’s governed by available Lightning liquidity—practical capacity across channels rather than a hard cap. During setup, users receive a seed phrase for full recovery, with an additional encrypted backup tied to their Signal account for redundancy.

Here’s the real question: can an app deliver self-custody convenience at chat speed without reverting to the usual trade-offs of centralized wallets? That comes down to four things.

- Reliability at everyday sizes: If a $12 lunch reimbursement routes instantly and a $1,000 split settles without friction, users will stick. Liquidity-aware routing is the decisive factor, not marketing. Lightning’s UX has improved, but failed routes still drive abandonment if they surface at the wrong moment. - Security that feels native: Embedding a wallet in a messenger compresses the attack surface. Seed handling, device backup flows, and secure enclave usage need to feel invisible yet robust. The encrypted backup tied to a Signal account lowers the cognitive burden, but it cannot dilute the core promise: users, not servers, hold the purse strings. - Onboarding through your social graph: Radar leans into the familiarity of Signal’s protocol and privacy posture; many privacy-first users already trust that model. If contacts are easy to find and payments auto-contextualize within chats, that’s a powerful habit loop. If not, the app becomes “just another wallet.” - Control vs. convenience positioning: Centralized apps like PayPal, Cash App, and Venmo made peer-to-peer payments effortless—but they custody funds, can freeze accounts, and see every transaction. Radar’s pitch flips that: keep your keys, preserve privacy, and still move quickly. The bar is high, because convenience has trained users to expect zero friction.

From a business lens, the wedge—paying the same people you text—creates a clear product narrative. The risk is overpromising on “it just works” if liquidity or routing is inconsistent. From a trust standpoint, building on the Signal Protocol and supporting Signal financially sends the right signal to privacy-conscious users. Ethically, aligning incentives around user-controlled money and communications avoids surveillance economics, while placing more responsibility on individuals to manage keys and recovery.

Radar frames its sweet spot as day-to-day payments—splitting expenses, grabbing lunch, tipping, paying friends back—exactly where Lightning’s speed and fees shine. If Radar can make $5 to $5,000 feel equally reliable, keep recovery sane, and ensure payments don’t leak outside the encrypted envelope, it earns a place on the home screen. If not, users drift back to custodial convenience. The opportunity is obvious; the execution window is narrow.