Regions

Member-to-Member Transfers with MatchCode

A secure, dual-verification transfer experience for Regions Bank customers.

This is an independent concept project created for portfolio purposes only. I am not affiliated with Regions Bank. All trademarks belong to their respective owners.

01 — Overview

Today, Regions Bank only supports internal transfers between accounts owned by the same person. Customers have no way to send money to another Regions customer, forcing them to rely on external apps like Zelle, Venmo, or Cash App.

This case study explores a concept called Member-to-Member Transfer, powered by a dual-verification method I designed called MatchCode.

02 — Problem

This project began with a real moment: my sister needed a quick $20 transfer, and I discovered Regions customers can’t send money to each other inside the platform — only between their own accounts.

Sending money inside a banking ecosystem requires:

Accurate identification
Fraud prevention
User privacy
Zero-mistake safeguards

Current financial apps solve this by email + phone + name search, but banks face stricter security constraints.

The challenge:
How do we let customers transfer money to another Regions customer without exposing sensitive information or risking misdirected transfers?

Baseline interface used for analysis and redesign.

02.1 — Understanding the Current Experience (or “Existing System”)

The current Internal Transfer feature only supports moving money between accounts owned by the same customer. There is no option for sending funds to another Regions member. This limitation forces users to rely on third-party apps like Zelle or Cash App, introduces delays, and creates unnecessary friction — especially for customers who are not tech-savvy.

03 — My Approach

I explored multiple questions:

How can users verify a recipient without seeing sensitive data?
Would account number search feel too risky?
Should users search by phone number or email?
How do we prevent someone impersonating a recipient?
What is the simplest input method while still maintaining bank-level security?

After analyzing risks, flows, and constraints, I designed MatchCode — a two-way verification method requiring both sender and recipient to confirm the transfer using a shared, one-time 4-digit code.

04 — Why MatchCode

✔ Less risky than name or email matching
✔ Doesn’t reveal private data (PII)
✔ Prevents someone claiming to be the recipient
✔ Forces both parties to actively participate
✔ Works on desktop and mobile

MatchCode is:

Generated automatically for each transfer
Visible only to the sender
Entered by the recipient to accept funds
Expired after 10 minutes
Blocked after too many attempts

06 — UX Principles Used

✨ Error Prevention
✨ Privacy by Design
✨ Progressive Disclosure
✨ Trust-Building UI
✨ Minimal Cognitive Load
✨ Cross-Device Compatibility

07 — Final Screens

Member → Member Transfer Home

Recipient Verification Modal

MatchCode Display Modal

Recipient Code Entry Modal

MatchCode Verified

Sender Transfer Complete

08 — Reflection

This project challenged me to blend banking constraints with seamless user experience. The design reduces misdirected transfers, builds user trust, and keeps users within the Regions ecosystem.

Next steps:

Mobile-first redesign

Add animations for transfer confirmation

QR code option for in-person transfers

Extend MatchCode to bill splitting