You are in a WhatsApp family group with relatives in the UK, Nigeria, Canada, the UAE, and Australia. Daily chat — birthdays, new babies, medical updates, who is travelling, what the weather is like. The conversation is constant; the relationships are strong; the geographic spread is the kind of thing that defines modern families.
What does not happen in the group: actual money movement. When your aunt in Lagos needs help with something, the conversation about what she needs happens in WhatsApp. The actual sending of money happens elsewhere — through Wise, through Western Union, through whatever international transfer app whoever is sending happens to use. The conversation thread and the payment thread are separate. The friction of switching apps, copying account numbers, navigating unfamiliar interfaces, and waiting for transfers to settle is enough that some of these conversations never become payments at all.
The same pattern repeats across millions of WhatsApp groups, Telegram channels, Signal threads, and other messaging conversations. The conversation is in the messenger; the payment is somewhere else; the mismatch is a quiet but constant tax on cross-border family life.
Why messenger payments are still mostly absent
The major messaging platforms have all attempted to build native payment infrastructure. None has succeeded at scale globally:
WhatsApp Pay. Launched in India (2020), Brazil (2021), and the US (2024). Limited to specific countries. The US version uses Novi/Meta Pay infrastructure. International payments between WhatsApp Pay markets are not supported even where the feature exists in both ends. A WhatsApp family group spanning India, the UK, and Nigeria has no native WhatsApp payment path between members.
Telegram payments. Telegram supports payments through bot integrations and the Telegram Wallet (TON-blockchain-based). Adoption is uneven; the experience is fragmented; cross-border use is technically possible but practically rare for non-crypto-fluent users.
Signal. Built MobileCoin-based payments in 2021 with limited geographic availability. Has not become a meaningful payment surface for most users.
Facebook Messenger. Had a P2P payment feature; Meta Pay rolled it back in many markets. Currently US-only and underused.
iMessage / Apple Messages with Apple Cash. US-only.
Google Messages. No native payment integration.
The pattern: every major messaging platform has tried to add payments natively. None has managed to build a globally available, cross-border-capable payment layer. The constraint is not the messaging side — the constraint is the payment infrastructure underneath, which is built around national rails and country-specific compliance regimes.
How an S-handle works as an in-chat payment surface
An Shandle is a single payment identifier — short, shareable, permanent, global. The handle is not a messaging-platform feature; it is independent of any messenger and works inside any of them as plain text.
The mechanic is simple: paste the handle into the conversation. Anyone with a Spondula wallet who sees the handle can send to it from their wallet app. No messaging-platform integration required. No country-availability issue tied to the messenger. The handle is text; pasting text into a chat works in every messenger that exists.
Use cases that emerge:
"Send me X for the thing" in a group chat. Someone organising a group activity (gift, dinner, holiday, contribution) drops their handle in the chat with the request. Each member sends from their wallet. The conversation about what is needed and the action of paying for it happen in the same place.
Family help requests. An aunt in Lagos mentions in the family WhatsApp group that she needs help with a specific cost. A nephew in London sees the message, copies the handle from her chat profile, sends. The conversation thread becomes the payment thread — without leaving WhatsApp.
Telegram channel tipping. A Telegram channel admin pins their handle to the channel's about section. Channel members who appreciate the content tip directly. The handle works inside Telegram even though Telegram's native payment infrastructure is fragmented.
Bot- and command-based payments inside chats. Communities can build simple bots that respond to handle-based commands ("/send @handle 5") to make in-chat payments more conversational. The underlying payment is still handled by Spondula; the bot is just a UI sugar layer.
What it costs: nothing on same-currency transfers. A small transparent exchange spread on cross-currency conversions, shown before confirmation. There is no per-transaction fee, no flat-rate floor, no messenger-platform cut.
Messaging apps have over 5 billion users worldwide combined. Native cross-border payment infrastructure inside those apps reaches a fraction of that user base. WhatsApp Pay is limited to three countries; Telegram payments are fragmented; Signal payments are geographically restricted. The conversation surface is global; the payment surface is not.
— Industry analysis of WhatsApp Pay, Telegram Wallet, Signal MobilCoin geographic availability, 2025
What changes when the chat and the payment are the same surface
The friction between messenger and payment app has economic and social consequences that compound across millions of conversations daily. Every conversation that should have ended in a payment but did not — because the friction of switching apps was higher than the social cost of the implicit IOU — is value not moved.
A handle in a chat profile, paste-able into any conversation, makes the conversation-to-payment path one step instead of three. The economic effect is that more "I owe you" conversations become "settled" conversations. The social effect is that the conversation no longer needs to carry the awkward weight of unresolved money.
Cross-border family groups specifically benefit. The geographic spread of modern families means that the same family group may include members across countries where every messenger's native payment feature works for some pairs and not others. A handle works for every pair. The family WhatsApp group becomes capable of supporting whatever financial flows the family already has — with the same simplicity as the photos and updates that already flow through it.
Messengers connect 5 billion people. The payment infrastructure that should sit alongside those connections has been built one country at a time, with most pairs of members unable to send to each other natively. The S-handle is what makes the chat thread and the payment thread the same thread — for any pair, in any messenger, anywhere.
Spondula is pre-launch. If you have a group chat that frequently turns into a "send me X" conversation that then exits the chat to settle elsewhere, the waitlist is where the chat and the payment finally converge.
Frequently asked questions
Does Spondula have a messenger app or integration?
The Shandle works as plain text inside any messenger — WhatsApp, Telegram, Signal, iMessage, Facebook Messenger, Discord, Slack. There is no messenger integration required; the handle is a string that can be pasted, copied, or shared anywhere text works. The actual payment happens in the Spondula wallet app when the recipient or sender opens it.
Can I send to someone's S-handle directly from inside WhatsApp / Telegram?
The send action happens in the Spondula wallet app. From a chat, you copy the handle, switch to your wallet, paste, send. Some communities build bots or shortcuts that streamline this further (a Telegram bot that takes /send commands, for example), but the base case is copy-paste — which works in every messenger.
Will my recipient be notified of the payment in our chat?
The recipient receives a notification from the Spondula wallet when the payment arrives. Whether they see it in the chat itself depends on whether the chat has an integrated bot or notification mechanism. The base case is that the chat carries the conversation and the request; the wallet carries the payment notification.
What about privacy — is my S-handle visible to anyone in the group chat who sees it?
An Shandle is similar to a username in terms of privacy. Sharing it in a group chat is comparable to sharing your phone number or your Venmo username — it identifies you to anyone who has it but does not expose your wallet balance, transaction history, or personal banking details. The handle is what someone needs to send to you, not what they need to access your wallet.
Can I have a different handle for different groups (family vs work vs friends)?
Most users have one handle they use across contexts (similar to using one phone number across contexts). Some users may set up multiple wallets with different handles for different purposes. Specific multi-handle support depends on the wallet implementation and use case.
Spondula is a global payments network. It is not a bank, exchange, investment platform, or broker. Availability, pricing, and Operator coverage vary by country. Bitcoin rewards depend on real network activity and are not guaranteed. See our terms and conditions for full details.
