From sign-up to first transaction
Fintech apps lose most users between install and the first transaction. Chumbaq nudges each person through KYC, funding and first use, and you can run it on your own servers.
TriggerAdded to cart
Wait1 hour
BranchBought since?
YES
ExitGoal reached
NO
PushYour cart is saved
Wait1 day
WhatsAppHold my pair?
Sample journey.
Where users slip away
- 01
Stuck in KYC
People start verification, hit a document step, and leave for good.
- 02
Funded, never used
The account is open but the first transaction never happens.
- 03
Data that can't leave
Your security team won't send customer data to another vendor's cloud.
Journeys you can run on day one
Each one is a journey you build once in Chumbaq. It runs for every new user who matches, and stops as soon as they reach the goal.
Finish KYC
- KYC started
- Wait 2 hours
- Push
- Wait 1 day
- KYC complete
First deposit
- KYC complete
- In-app on next open
- Wait 2 days
- Funded
First transaction
- Account funded
- Wait 1 day
- Push at best hour
- Transaction
Dormant account
- No login 30 days
- Push
- Wait 3 days
- SMS
- Login
Your customers' data stays with you
Run Chumbaq on your own servers, including your own cloud account in India. You still use the same SDKs, journeys and reports.
- Runs on your own infrastructure
- Your own SMS, email and WhatsApp provider accounts
- Export everything, anytime
Fintech apps, answered
Are you SOC 2 or ISO certified?
Not yet, and we say so. If you need your data in your own infrastructure, self-hosting keeps it there.
Can I send OTPs?
You can send transactional SMS through your Twilio account. Chumbaq is built for engagement, so most teams keep OTPs on their existing path.
Bring your users back
Free up to 2,500 monthly active users. No card, no sales call.