First top-up: cash, DuitNow, and the app that never returns

Registration metrics look kind. First-funded metrics do not. In Malaysian e-wallets and digital bank pots, the missing ringgit often left the building at the moment the applicant was handed to another app.

DuitNow as a corridor, not a button

A “Top up with DuitNow” control that deep-links into a bank app is only half a path. If the bank app opens, the transfer succeeds, and your wallet does not refresh until a manual pull-to-refresh, many applicants believe the money vanished. They screenshot, they message a friend, they do not retry. The funnel count at “top-up initiated” looks healthy. The count at “balance updated” does not.

In a walkthrough we time the interval between leaving your app and seeing the new balance, on two originating banks, not one. A delay that is fine for a salary credit is not fine for a first RM 20 test top-up.

FPX and the back button

FPX sessions that die when the applicant hits the Android back control — a habit, not a decision — should recover. We still find pages that show a generic merchant error and no receipt number. The applicant will not start again from screen one of registration. They will assume the wallet is unsafe.

Cash-in is a journey with a bus

Over-the-counter cash-in remains rational for people who do not want their bank app involved. The finance app’s job is to state which agent accepts the cash, what the nightly cut-off is, and how long the wallet takes to show the amount. “Visit a partner outlet” with no hours is how a Sunday applicant becomes a never-funded account.

When Logic Pulse Core maps a first-funded path, we treat each rail as a separate story. Averaging them into one “funding conversion” hides the rail that is actually broken.