Journal
Field notes from conversion tracking, written after the files were on the table
These pieces stay inside payment-enabled apps and the gateways they use. They are not essays about productivity. Each one comes from work we have had to explain in a Balakong session.
Authorisation is not conversion
A gateway can return an approved authorisation while the app never records a completed order. The gap usually lives in capture timing, not in the decline table.
What a 3-D Secure challenge does to a Malaysia-facing checkout
Challenge windows, issuer apps, and a shopper returning on a different network all look like abandonment if the app only listens for a success callback.
Matching gateway webhooks to in-app purchase events
If the webhook arrives after the shopper has left the receipt screen, your funnel will count a ghost. We walk through a practical join key that survives retries.
Reading a settlement file against the funnel
Settlement is the unfashionable source of truth. A morning with one acquirer file will show which ‘successful checkouts’ never became money.
When a failed payment is actually a timeout
FPX and some e-wallet hops leave the app waiting. Labelling every unanswered hop as a shopper quit hides the bank-side clock you cannot see.