Secured Mobile Payments

Enhancing user experience & security of mobile transfers and payments experience

CLIENT & DURATION

Oversea-Chinese Banking Corporation (OCBC Bank)

Aug 2022 – Dec 2023

ROLE

Manager, Experience Design

OCBC Bank

UX Design, User Interface Design, User Testing

CONTEXT

OCBC Bank, a leading financial services group in Southeast Asia, faced phishing scams that required urgent security upgrades. This project aims to implement security features to prevent scams and protect customers.

IMPACT

A series of anti-fraud measures have protected customers from various scams, preventing more than $12 million SGD losses since its inception.

The Problem

The Problem

The Problem

A series of SMS phishing scams involving OCBC Bank prompted the urgent implementation of security features to protect customers and prevent further scams.

A series of SMS phishing scams involving OCBC Bank prompted the urgent implementation of security features to protect customers and prevent further scams.

A series of SMS phishing scams involving OCBC Bank prompted the urgent implementation of security features to protect customers and prevent further scams.

Surge in phishing scams involving OCBC

Affecting hundreds of customers and costing millions of dollars

Urgent need to enhance our security measures

Process

Process

Process

Define

Define

Define

Identify gaps to protect customer assets and achieve business objectives.

Alignment

Alignment

Alignment

Bring stakeholders together to align on limitations, must-haves, and necessary actions.

Ideate

Ideate

Ideate

Solution for design problems and create basic wireframes for assessment

Prototype

Prototype

Prototype

Create hi-fidelity prototypes with proposed content structure and flow

Test

Test

Test

User-testing with users and stakeholders. to understand break points. Reiterate and retest.

Remote user-testing with users and stakeholders to understand break points. Reiterate and retest.

Crisis management

Crisis management

Crisis management

A wave of phishing attacks targeting OCBC in December 2021, followed by advanced scams like malware and e-commerce fraud, prompted an urgent race to implement enhanced security features to protect customers' assets

Tackling key challenges

Tackling key challenges

As the design was being finalized, I identified key challenges that needed to be addressed to ensure the revamp's success. The solution was carefully crafted with these considerations in mind.

1

Assessing potential implications of transitioning to a new system

Assessing potential implications of transitioning to a new system

With every minute wasted, scammers could exploit vulnerable customers, so I prioritized essential features to implement immediately and phased out non-essentials for later.

2

Ensuring the ease of transition for those acquainted with old habits

Ensuring the ease of transition for those acquainted with old habits

User research showed that while customers expect seamless transfers, however, security enhancements require adding friction to ensure safety, so it was crucial to balance effective checks without overwhelming users.

Alignment

I gathered stakeholders, from business, legal, technical, and data analysts to agree on constraints, essentials, and required steps.


The intended strategy can be divided into three categories:

Detect fraud with data

System-based measures like AI and data analytics can help monitor and detect fraudulent transactions.

Verify customer identity

Verify that the consumer is the one completing the transaction.

Timely intervention

Delaying immediate transactions can allow time for intervention when necessary.

How might we effectively safeguard customer assets during the payments & transfers experience?

How might we effectively safeguard customer assets during the payments & transfers experience?

How might we effectively safeguard customer assets during the payments & transfers experience?

Conceptualization

Conceptualization

Conceptualization

I mapped out user journeys of frequently done tasks after analyzing research results to determine customer pain points and opportunity statements. From there, I came up with ideas.

Reframing the ask

👀 The ask

Detect fraud with data


💡 The opportunity

How might the bank use data to identify and deter fraud?


🙋🏻‍♀️ Possible solution

  • Inspect transaction before releasing funds

  • Filter and halt suspicious transactions

👀 The insight

Verify customer identity


💡 The opportunity

How might we ensure that the customer is the one making the transfer?


🙋🏻‍♀️ Possible solution

  • Additional customer authentication

👀 The insight

Timely intervention


💡 The opportunity

How might we bridge the gap between intervene before it's too late?


🙋🏻‍♀️ Possible solution

  • Provide quick access to seek help

  • Simplify workflows

  • Offer guidance and information

👀 The ask

👀 The ask

💡 The opportunity

💡 The opportunity

🙋🏻‍♀️ Possible solution

Detect fraud with data

Detect fraud with data

1

1

How might the bank use data to identify and deter fraud?

  • Inspect transaction before releasing funds

  • Filter and halt suspicious transactions

Verify customer identity

Verify customer identity

2

2

How might we ensure that the customer is the one making the transfer?

  • Additional customer authentication

Timely intervention

Timely intervention

3

3

How might we bridge the gap between intervene before it's too late?

  • Provide quick access to seek help

  • Simplify workflows

  • Offer guidance and information

Given the complexity of this flow, I aligned stakeholders by mapping the pre, during, and post-fraud monitoring stages to ensure logic, address gaps, and assess impacts on front and back staff.


Alongside basic wireframes, this flowchart served as the shared "source of truth" across teams, clarifying what could be implemented immediately versus deferred to phase 2.

Fig: Customer flows for pre, during, and post-fraud monitoring

I identified the need to refine customer communication—reassuring users when transactions fail without alarming them or tipping off potential fraudsters.


To address this, I mapped a "What goes on" flow to surface questions for business, legal and editorial teams, ensuring clarity, consistency, and compliance.

Fig: "What goes on" flow

The Final Solution

The Final Solution

The Final Solution

Fraud management measures were implemented at various stages of payment transactions—focusing on pre-transaction deterrence, during-transaction verification, and post-transaction detection to safeguard assets.

PRE-TRANSACTION
Personalised tools to make informed decisions

Cooling periods are implemented for adding payees or increasing transaction limits, deterring fraud by delaying immediate transactions and allowing time for intervention when necessary.

PRE-TRANSACTION
Personalised tools to make informed decisions

PRE-TRANSACTION
Personalised tools to make informed decisions

Fig: Increase of transaction limit takes effect after 12 hours

PRE-TRANSACTION
Reducing minimum transfer limits

Reduced default daily transfer limits for various types, with adjustable settings for customers. Notifications are now triggered for transfers starting from S$0.01.

PRE-TRANSACTION
Reducing minimum transfer limits

PRE-TRANSACTION
Reducing minimum transfer limits

Fig: Customers can adjust the transaction limits

DURING-TRANSACTION
Strengthening security with email authentication

With SMS compromised, email authentication was introduced, offering better security as sender verification and spam filters block most phishing attempts, ensuring only authenticated emails reach recipients.

DURING-TRANSACTION
Strengthening security with email authentication

DURING-TRANSACTION
Strengthening security with email authentication

Fig: Customers must authenticate via email to complete transaction

POST-TRANSACTION
Smart algorithms conduct backend checks before transaction approval

Algorithms and data analytics flag suspicious transactions, like those involving blacklisted accounts or duplicate transfers, for review. The bank confirms these transactions with customers via call before processing.

POST-TRANSACTION
Smart algorithms conduct backend checks before transaction approval

POST-TRANSACTION
Smart algorithms conduct backend checks before transaction approval

Fig: Suspicious transactions will be flagged for further review

Usability Testing

I tested the product at various phases, but due to the urgent implementation, testing was more limited compared to other projects.


Testing was conducted across end-to-end payment flows to ensure a realistic representation.

Low-fidelity prototypes were tested with stakeholders to gather feedback on the flow and content when a transaction is flagged as suspicious.

• High-fidelity prototypes were tested with customers for two-factor authentication and suspicious transaction scenarios to gauge sentiment, verify usability, and ensure the language is clear and appropriate.

Fig: Artefacts from customer interviews

Project Status & Impact

Project Status & Impact

Project Status & Impact

  • Launched in December 2021, continuously adding new features while gathering customer feedback through app stores or surveys.

  • Prevented more than S$12 million in losses through anti-fraud measures, safeguarding customers from various scams since inception.

Project Learnings

Project Learnings

Project Learnings

Navigating temporary unideal trade-offs

Given the surge in phishing scams involving OCBC Bank in 2022, the team promptly enacted measures, potentially compromising user experience to safeguard assets. Looking to 2024, reevaluating these trade-offs is essential given evolving customer behaviour, prompting a reconsideration of whether to enhance or relax certain measures.

Always listen to your users

Concurrently, the bank also rolled out the OCBC Digital Silvers Programme as part of an attempt to help the silver segment learn how to bank and pay digitally, and to stay safe from scams while doing so. Through which, I volunteered on weekends as a digital ambassador to teach elders digital banking skills. It was eye-opening to learn about how elders struggle with dynamic font issues, to having difficulty accessing account documents. I wasn’t just teaching them, they also taught me to be open to learning the frictions that users might face.