When DuitNow QR and card share one crowded last screen

Close view of a card held above a contactless payment reader

The app looked generous. Seven ways to pay, all visible if you scrolled. DuitNow QR sat at the top. A card form sat in the middle and asked for a billing postcode even after the shopper had already typed a delivery postcode for Kajang. Touch ’n Go opened in a sheet that covered the order total.

We completed two live purchases on Android with a modest basket of T-shirts the stores actually hold. The first attempt stopped when the card form rejected a Malaysian postcode format the delivery screen had already accepted. The second attempt went through DuitNow QR but only after the shopper — in this case Daniel — dismissed a wallet sheet that had opened by mistake from a tap on the wrong row.

Floor staff in Kajang had a phrase for this: people ‘gave up at pay’ and came in to settle at the till instead. That is not a failure of the till. It is a cart that asks the same question twice and then hides the total.

The useful change was not to add an eighth tender. It was to show three: the two the shop actually takes most often, and a ‘more’ list. The card form should inherit the postcode already given. The QR should not sit under a sheet that can be opened by an accidental thumb.

Terminal Map Hub does not build those screens. We mark where a real basket stalls so the studio you already hired can change one thing at a time. If your retail app serves Selangor shoppers, pay with a real SKU before you argue about the design file.

Ask us onto your floor if a similar stall is happening at your till or in your cart.