Deadline for migrating to android 35 was Aug 31, failing which play store would stop accepting any updates to our app. Migrating to android 35 presented several challenges solving which Saravanan spent, on and off, a few months. Here are some notes.
We went live with the updated app this Wednesday. Rollout is currently 1% (or may be by now it is larger). We will monitor any problems in the field and increase rollout as we get confident. This update also paves way for upgrading digio SDK next.
The intake of NU is now beyond the critical mass that is needed for growth. On the flipside - delinquencies are higher too. Is payback higher than what we can afford, that needs to be seen.
Look at the following, "collection view" of D35 repeat delinquency. A number of xx% for month M means that of the
monies whose collection was supposed to start sometime in month M, within 35 days, xx% of the money stood uncollected.
We provide a 2/3 leeway to Pi3 since first installment has 0 delinquency (and we still get MDR there). Despite that,
in later months, Pi3 collection is poorer than PL collection, dragging RU delinquency up. We need to look at it
closely.
Some progress in cryptolinking last week.
The mobile app server released an endpoint, which will be available for the linking screen. As soon as a notification is received, the linking screen makes an API call to this endpoint and pass the verification ID. The mobile app server endpoint will return the device make and model along with the verification ID as a response. The linking screen will then pass this data as metadata to the approval API.
Status:
Mobile App
Endpoint has been released
Transaction frontend
Changes are done.
@Raksha A is doing the testing for this before release, We have decided we will release this before the Sveltekit Migration(Transaction-frontend). So we can test initial result.
Revoking select from CRM was not present earlier, now it is live
Prakash gave a tech talk on Pi3 revamp. Here are the slides and the video.
Akhil Pandey shared with me a bunch of videos he has made to help clients do integration. Find them here.
SELECT SUBSTR(bucket_id, 6) AS date, COUNT(*) AS num_approval_calls
FROM public.user_approval_events
WHERE event_name IN (
'ZeroClickTransactionEligibilityFailedEvent',
'UserApprovedEvent',
'UserApprovalFailedEvent',
'ZeroClickTransactionEligibilitySuccessEvent')
AND bucket_id >= 'date_2025_06_01'
GROUP BY 1
ORDER BY 1
Rising number of approval calls have caused instability in some of our systems. We need to find the reason of increased number of approval calls. There are rumours that juspay is calling us needlessly.
AARR is live in a limited way currently (till we fix remaining work from TS side). With this limited rollout - some AARR removal is happening via user payment on merchant app. This is very encouraging.
Thanks Manish for the dashboard and the data - of some 157 completed AARRs, 10 are via merchant page - that is 10 "blocked" users unblocking themselves by paying on merchant app.