The KYC to first transfer gap begins when a verified account still cannot—or does not yet need to—complete its first useful transaction. Approval removes one barrier. It does not establish intent, explain the funding journey or prove that a payment succeeded.
September Series 03 · A practical activation investigation. All examples and numbers are hypothetical, not client results.
My first question is not “Which incentive should we send?” It is “Where does the approved user’s next action stop?” The answer determines whether marketing, product, support or operations should act.
Define the KYC to first transfer outcome
Start with a precise definition: the first successfully completed transfer after verification approval, counted once per user within an agreed observation window. Keep a created transfer, a funded transfer, a pending payment and a completed payment separate.
Choose a window that suits the product’s actual use case. Seven or fourteen days can be useful review windows in an experiment, but neither is a universal benchmark. A person who sends money monthly may behave differently from someone with an immediate payment need.
Record approval time, relevant next-step events and the authoritative transaction status. Define how cancellations, retries and delayed updates affect the report. Otherwise, the team may count an attempt as activation or misclassify a payment still in progress as abandonment.
Build cohorts around approval date
Compare people with the same opportunity to complete the action. Yesterday’s approvals should not be judged against a cohort that has had two weeks. Mark immature cohorts and review them again after the observation window closes.
Break the analysis down by meaningful factors such as acquisition source, supported corridor, funding method, device or product version when the available data supports it. Prioritise the largest stalled group before investigating small, noisy segments.
The broader logic appears in my KYC to first transfer guide. This series article focuses on turning the approval cohort into an intervention plan rather than repeating the whole onboarding diagnosis.
Separate five post-approval states
| State | What it establishes | Next question |
|---|---|---|
| No transfer journey opened | No observed attempt yet | Does the person have a current need and understand the next step? |
| Quote viewed, no transfer created | Some evaluation occurred | Is fit, cost or the recipient journey unclear? |
| Transfer created, not funded | An intended transaction exists | Can the user complete the available funding method? |
| Funded, pending | Progress has occurred | Is the status accurate and explained? |
| Failed or cancelled | The first attempt did not complete | What permitted recovery route exists? |
Map these example states to your own implementation. Do not infer a person’s financial circumstances from an event, and do not treat an unobserved action as proof of disinterest.
Diagnose intent before manufacturing urgency
A signup campaign may attract people planning a future transfer. Others may register to compare the service. Both can become approved without an immediate transaction need.
Ask a small, consented sample what they intended to do and when. Compare campaign promises with the available product. If an acquisition message attracts people outside the supported use case, more post-approval notifications may amplify the mismatch.
A useful response can be a clearer next step or a relevant explanation saved for later. An expiring reward is a different intervention and should not be used as a substitute for understanding the audience.
Inspect the funding journey on the actual device
Walk through a test journey using the supported methods and the same screens customers see. Check whether the person knows what to do next, where a confirmation will appear and what to expect while a payment is processing.
Use product-approved instructions. Do not invent settlement times, available payment methods or guarantees to make a message sound reassuring. When a method fails, support should explain the permitted alternative appropriate to that specific case.
Review aggregate error categories and support themes. Keep bank details, identity documents and personal transaction information out of general marketing reports.
A hypothetical diagnosis that changes the campaign
Imagine 200 users were approved in a mature cohort. Eighty opened a transfer quote, forty created a transfer, twenty funded it and eighteen completed it.
Sending the same “make your first transfer” message to all 182 non-completers ignores the distinction between no observed attempt and an in-progress payment. The largest visible loss is before quote opening, but the funding loss may also contain a fixable product problem.
The next step is evidence gathering. Ask whether the first group has an immediate need; inspect the funding journey for the second; explain accurate status to the pending group. The counts identify priorities, not causes.
Match the intervention to the obstacle
- Unclear next step: improve the post-approval screen and link to the relevant action.
- Unclear offer: explain the actual fee, recipient outcome and supported use case with approved copy.
- Funding friction: repair instructions or the failing step before adding reminders.
- Pending transaction: communicate status and a support route rather than asking for another attempt.
- No current need: use a proportionate lifecycle approach consistent with the person’s preferences.
The same principle applies before approval. My KYC drop-off diagnosis article explains why a reminder cannot repair an unusable verification step.
Test one explanation and measure completed value
Choose one eligible state, one hypothesis and one change. Where feasible, compare with a holdout and keep the observation window consistent. Track completed first transfers, time to completion and the number of users affected.
Include guardrails such as repeated failed attempts, support demand and complaints. A higher message click rate with no improvement in completed outcomes is evidence to investigate, not a successful activation claim.
After the first transfer, evaluate repeat use separately. A one-time reward-driven action does not establish sustained demand.
Make the activation review actionable
End the weekly review with the largest documented obstacle, the owner who can change it and the date when the outcome can be judged. Keep acquisition, product and lifecycle teams in the same conversation.
If your team can see approvals but cannot explain the missing first-value actions, my Marketing Audit and 1-on-1 Consulting can help connect measurement, onboarding and the next activation experiment.
Frequently asked questions
Does KYC approval mean the user is activated?
Only if approval is your explicitly defined value action. For a transfer product, a completed first transaction is usually a different milestone.
Should every approved user receive an incentive?
Diagnose the state and obstacle first. An incentive cannot make a failing funding step work.
Which metric should lead the review?
Use completed first-value actions in mature approval cohorts, supported by transition rates, completion time and customer feedback.