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.
Join the conversation.
0 comments · Be respectful, be specific, be useful.
Be the first to comment.