As part of DBS Bank’s response to the Monetary Authority of Singapore’s pause, we were asked to examine the payment journey and provide users with more certainty during system downtime.
I was the Design Lead for the project, working across PayLah! and digibank in 2024. We had a tight timeline and limited design support, while the work required input from Design, Digital, Product Leadership and Technology.
After the feature launched:
- User's feedback
Client: DBS
Role: Design Lead
Team: Four designer
Timeline: 2024
The brief initially focused on payment messaging. To understand what was happening across the full experience, we mapped the end-to-end journey across PayLah! and digibank.
I focused on two questions:
1. What was causing the lack of clarity?
2. Where could we improve the experience?
Through stakeholder interviews, we found that the problem was more than a confusing message.
Transactions could remain in a “pending” state. During PayNow downtime or server failures, the status recorded by the central system could also differ from what the merchant had received. A customer might see a successful payment while the merchant was still waiting for the funds.
At the same time, older users had been asking for larger text on the completion page. Merchants also needed a better way to check that a successful payment was genuine.
What started as a status problem became a broader design question:

We made the merchant name and amount more prominent and increased the font size. This made the information easier for older users to read and gave merchants the key details they needed when checking a payment.
We also introduced an animated success icon. The animation made the confirmation more visible and was intended to make static screenshots harder to use as false proof of payment.

The old experience told users that it was being processed and asked them to check their transaction history. The redesigned screen gave them a direct answer: no money had been deducted, there was an issue and they could try another payment method. We kept the transaction details available in case they needed to refer to them.


