Forum: PayNow alias feature removal should balance usability and protection

I refer to the report on the discontinuation of PayNow’s alias feature (No more nicknames: PayNow to end alias option for users from June, April 29). While the move is intended to curb impersonation scams, it appears to be a rather blunt approach that may reduce usability without fully addressing the root of the problem.

Removing nicknames eliminates one avenue for abuse, but it also takes away a useful feature that many rely on to identify familiar recipients easily.

Could a more balanced approach be considered? For instance, PayNow could retain nicknames but display them alongside a clearly labelled, partially masked registered name. This would let users retain familiar contacts while still verifying the legitimacy of the recipient.

In addition, banks could introduce stronger safeguards such as clearer alerts for first-time transfers, and prompts when a recipient is not found in a user’s contact list. Such measures would empower users to make more informed decisions rather than rely solely on system-imposed restrictions.

While the removal of nicknames may address a known vulnerability, it risks being a reactive measure in a landscape where scams are constantly evolving.

Increasingly, scams rely less on technical loopholes and more on social engineering tactics such as impersonation, urgency and emotional manipulation. By the time a transaction is made, victims may already have been convinced to proceed, regardless of the name displayed. 

Efforts to enhance security are certainly welcome, but they should aim to strike a better balance between protection and practicality.

Gabriel Chia