Desk note
Merchant-assisted applications: what the file rarely records
· Priya Menon
Malaysian BNPL volume still leans on retail and marketplace checkouts. Staff want the sale to complete. The terminal wants a decision. The file that results can look exemplary: every mandatory field present, terms accepted, OTP recorded.
What the file rarely records is the conversation. Who suggested BNPL. Whether a cheaper cash price was mentioned. Whether late fees were described as a ‘small charge’ or shown as a number. Whether the customer’s phone was used, or the staff member’s. Those facts live in CCTV, in mystery shopping, or nowhere.
We cannot reconstruct a conversation from an application record. We can look for proxies: origination in a few seconds, repeated staff identifiers, identical email patterns, cooling-off acknowledgements that sit one second after terms, and cancellation requests that arrive the same afternoon with the words ‘I did not know it was a loan.’
Those proxies do not prove mis-selling on their own. They do justify a merchant-level finding and a change in how the programme briefs shops. A file review that ignores the assisted channel because the fields are complete is reading the workflow, not the application.
If you commission this work, send us the merchant scripts and the training pack along with the files. Without them we can still grade completeness. We cannot grade explanation.