01 · Fixed contribution
December Trip
12 people × ₦50,000Known members, a clear expectation per person, partial-payment support and a deadline everyone can understand.
Zuka Groups · In development
Set what you’re collecting for, agree how it should work, invite the people involved, and let Zuka keep track of the money and what happens next.
Talk to the Zuka teamGroups is in development and is not generally available yet. The examples on this page show the planned product model and do not represent live pooled custody or a native WhatsApp group-chat bot.
Shared money gets messy quickly
Someone pays ₦20,000 first.
Someone says they paid from another account.
The deadline moves and not everyone sees it.
People keep asking who is still outstanding.
Someone asks where the money is meant to go.
The plan changes and the group needs a clear next step.
Zuka Groups is designed around one shared financial state that stays understandable as the real world changes around it.
Rules before money
Discussion can happen naturally, but the agreed money rules should not disappear into chat history. Zuka keeps the reviewed Group agreement clear enough for everyone to understand what they are contributing toward and what is meant to happen next.
The agreement doesn’t disappear into chat history.
The example describes Group state, not a custody promise. Exact destination, release and refund behaviour follows the approved production and provider design.
One Group, changing state
The same Group Purpose moves forward as people join, contribute and handle what still needs attention. Zuka keeps the agreed state understandable instead of turning the journey into five disconnected features.
Set it up
Purpose, people, contribution expectations and the important rules are clear before money starts moving.
Bring people in
An invitation takes each person to the actual Group entry experience, not back through the marketing page.
Keep progress clear
Full and partial contributions can be reflected according to the Group rules without losing sight of what is still expected.
Keep attention visible
Outstanding, failed, changed or time-sensitive states get the right next action instead of disappearing into chat history.
Reach the outcome
What happens next follows the reviewed Group rules and the approved production journey for that purpose.
Ways to use Groups
Groups is not one mechanic. The beta model is broad enough for fixed contributions, flexible targets and an agreed group purchase without turning any one use case into the whole product.
01 · Fixed contribution
Known members, a clear expectation per person, partial-payment support and a deadline everyone can understand.
02 · Flexible target
People can contribute different amounts while permitted Group progress and the intended beneficiary stay clear.
03 · Group purchase
Everyone can see when enough people have joined, what has been paid, and whether the agreed purchase is ready to proceed.
Visibility & trust
Shared money needs enough visibility to build confidence without turning participation into public financial exposure. What each person sees should follow identity, role and the Group rules.
Members should be able to understand what the Group is for, what they are expected to do, and the shared state the Rules allow them to see.
A Group does not make every payment detail, identity attribute or account detail visible to everyone involved.
Organiser actions remain bounded by the accepted Group rules and the approved production journey rather than an implied right to move pooled money freely.
Zuka Groups · In development
Agree what everyone needs to do, keep progress visible, and let unresolved money states stay visible until the Group reaches its intended outcome.
Talk to the Zuka team