MessagePay was built to solve a deceptively simple problem: letting borrowers make loan payments by text message in a way that banks and credit unions could actually deploy, trust, and scale. The product lived at the intersection of borrower behavior, regulated financial systems, and institutional risk, which meant success depended less on novelty and more on alignment across disciplines.
My role was to hold that alignment. As Director of Product, I worked alongside design and engineering to shape product decisions while also managing expectations across internal leadership and external stakeholders, including banks and credit unions adopting the platform. The work required translating borrower needs into usable flows, institutional requirements into enforceable constraints, and technical realities into decisions the business could stand behind.
The challenge
“Pay your loan by text” sounds straightforward until real money enters a regulated environment. Every interaction had to be reconcilable, auditable, and supportable by financial institutions that are naturally cautious about new channels. Banks and credit unions do not adopt products because they are clever; they adopt them because they can explain them, control them, and trust them under scrutiny.
At the same time, the borrower experience could not feel heavy or procedural. The core risk was building something that worked technically but failed emotionally, or something that felt effortless to borrowers but uncomfortable for institutions. The real challenge was trust on both sides of the transaction.
What we built
We approached the product as two tightly connected experiences rather than a single interface. On the borrower side, MessagePay was designed as an SMS-first flow optimized for speed, clarity, and completion. On the institutional side, it was a governed system that made every action visible, traceable, and defensible.
The borrower experience focused on closing the gap between intention and action. Payment reminders led directly to completion, repeat payments were streamlined through one-time verification patterns, and options were designed to reflect real-world constraints rather than idealized flows. The goal was not to teach users a new system, but to let them act naturally within one they already understood: text messaging.
In parallel, we designed the institutional layer to give banks and credit unions confidence in the channel. Controls, visibility, and reporting were treated as first-class product features rather than administrative afterthoughts. This ensured the SMS channel could operate safely at scale while meeting compliance, audit, and operational requirements.
Throughout the process, my focus was on maintaining coherence between these layers—making sure borrower simplicity never came at the expense of institutional clarity, and that governance never eroded usability. The result was a system that felt conversational on the surface, while remaining rigorous underneath.