Why I Built This
WhyIBuiltThis
Across Nigeria, Kenya, Uganda and Ghana, millions save through ajo, chama, esusu and susu circles. They work because everyone knows everyone. They break in two familiar ways: one organizer disappears with the pooled money, or the paper records disagree and nobody can prove who paid.
The obvious app idea makes it worse. Open pools and stranger matching strip out the social trust the whole model runs on. The real job is removing the custody and record risk without touching the trust.
My Approach
MyApproach
I built Kora for the StacStart Borderless Bytes hackathon as a closed digital circle. Invite-only links, every join request goes to a member vote, and the organizer sets the schedule but never touches the funds. Split payments route money straight from member to that round's recipient.
Supabase does the backend work: Postgres with row-level security, realtime for the shared ledger, phone OTP auth, and Edge Functions for charges, webhooks, schedule generation and payouts. The frontend is an installable Next.js PWA, so it sits on members' phones like a native app.
Key Features
KeyFeatures
- Create invite-only circles with amount, currency, frequency and vote threshold set up front
- Join by link, admitted by vote. No single admin decides who gets in
- Money moves member to recipient through Flutterwave split payments. The organizer never holds it
- One shared ledger: every contribution and payout timestamped and visible to all members
- Payout schedule generated from the rotation order, with reminders before due dates
- Trust score per member built from on-time and late payments across cycles
How the System Works
HowtheSystemWorks
Create a circle, bring your people in by vote, and let the schedule move the money.
- Create a circle: name, contribution amount, currency, frequency, and how many votes admit a member
- Share the invite link. Requests stay pending until members approve or reject them by vote
- Generate the payout schedule from the rotation order. One cycle per member, pot pooled from contributions
- Members pay their share through Flutterwave. The webhook flips the contribution to paid and feeds the trust score
- Everyone watches the same realtime ledger. No screenshots, no notebooks, no asking who paid
- Reminders go out before due dates so one late payment doesn't cascade into everyone's payout
- Late payments settle as late, never quietly. The record shows it and the score reflects it
Engineering Challenges & Lessons Learned
EngineeringChallenges&LessonsLearned
Next.js typecheck kept choking on the Edge Functions. They run on Deno, not Node, so I excluded the functions folder from tsconfig and kept the two runtimes from stepping on each other
Payments died on preflight. The Supabase client always sends extra headers and the functions rejected them. Widening the CORS allow-list fixed it
Login kept losing invite links. The auth proxy forwarded the path but dropped the query string, so inviter attribution died at sign-in. Preserving the full URL through the redirect fixed it, and the inviter id now resolves to a real profile instead of failing the foreign key
Charge failures leaked internals to the client. I stripped error responses to a generic message and kept the cause in function logs
What I’d Improve Next
WhatI’dImproveNext
- Finish the USSD companion so members without smartphones can check status and confirm payments
- Run the live two-account pass: join by vote end to end, plus ledger updating on a second browser with no refresh
- Move Flutterwave to production keys and verify live OTP delivery across all four countries
