In a fintech, onboarding does not fall apart where the team assumes. The usual suspect is the signup form, and that is almost never where the real problem sits: whoever made it through filling out their details already has intent. The stretch that gets lost quietly is the one that comes after, between identity verification approved and the first funded transaction.
Why that stretch stays invisible
Most product dashboards measure “registered users” and “active users” as if they were two consecutive steps. In between there are at least two events that almost never get their own name: KYC approval and the first funding load. Without that split, the report mixes someone who signed up yesterday with someone approved three weeks ago who still has not funded a dollar, both showing up as “pending” in the same column.
This matters because the already-approved user has spent the most expensive effort in the process: uploaded documents, waited for review, retried a photo that did not pass. Losing them there costs more than losing someone at the form, yet it gets less attention precisely because it is not measured as its own step.
The three events worth separating
- Signup completed. Timestamp of when the user finished entering their details.
- Verification approved. Timestamp of when KYC gave the green light, not when the user started it.
- First transaction funded. The first real money movement, whether it is a top-up, a transfer or a payment.
Those three timestamps per user are enough to calculate the time between each step and see where each weekly cohort stalls. No more infrastructure than that is needed for the initial diagnosis.
Which message works best at each point
A welcome email at 24 hours treats every user the same, regardless of the step they are on. Against that baseline, a message triggered by the “verification approved” event, pointing to the exact next step (how to fund the account, which method fits the country), converts better because it answers the user’s real moment instead of a fixed clock.
That architecture, where the stage lives as a profile attribute and only fires the message when it applies, is the same one covered in customer retention by lifecycle stage. At one cross-border payments fintech client, that approach placed 99.8% of users in a concrete stage, which made it possible to replace separate per-country campaigns with a single message engine.
Where to start
Before automating anything, split the three events in your user table and calculate how long it takes between verification approved and first transaction for the last four weeks. If that number keeps growing week over week, it is not a product problem: it means nobody is talking to the user at the exact moment they got stuck.
That diagnosis, and the flow built on top of it, is the work we do in Growth Automation, applying the same event-and-stage logic that turned Bigbox’s setup into production in 15 days, later replicated across five countries.