CodePay Go · Merchant Operations App

/Companion page → CodePay platform work

Making merchant data trustworthy before making it intelligent.

I was asked to design a few dashboard cards. I wrote the first PRD instead — and grew it into a launched merchant operations app and the founding product role behind it.

Shipped · iOS · Android · TabletResearch-driven repositioningAI layer · vision & prototype

The merchant operations app across iOS, Android, and tablet.

Role

Design task → product owner / founding designer

Scope

Research · PRD · UX/UI · QA · GTM · AI direction

Timeline

Jul 2025 – Present

Tools

Figma · Lovable · AI prototyping

growth in 2 months

3

surfaces shipped · iOS · Android · tablet

3

partners · multiple research rounds

01

It started as dashboard cards. It became product ownership.

In payments, a dashboard card isn't a visualization — it's a trust contract.

I was brought in to design a few merchant-facing dashboard cards. But every card raised a product question — what does this metric mean, what time range does it cover, can a merchant reconcile it with the money that actually hits their bank? In payments, a dashboard card isn’t a visualization; it’s a trust contract. So I wrote the first PRD myself, and the work grew from a UI task into owning the product.

Decision · Tradeoff

Decision
Treat the cards as a product-definition problem, not a UI task.
Tradeoff
More scope and accountability — versus shipping something I didn't believe in.
Outcome
I grew into the product owner.

A metric card is a trust contract. The merchant either believes the number — or stops trusting the product behind it.

02

Merchants didn't want analytics. They wanted to know their money was right.

They don't reconcile by 'business growth.' They reconcile by what actually lands in the bank.

From November 2025 we put the app in front of partners and tested it. Across several interview rounds with our three core partners, one pattern held: merchants don’t reconcile by “business growth.” They reconcile by sales, tips, tax, fees, and what actually lands in the bank — and their real anxiety is “does what I see match my deposit?” A market signal sealed it: demographic “growth analytics” had under 1-in-10 paid retention in the field. So I repositioned the product from “See your business grow” to “Where does my money come from?”

Before

“See your business grow.”

After

“Where does my money come from?”

Decision · Tradeoff

Decision
Pause GTM when testing showed the data wasn't trustworthy enough to scale.
Tradeoff
Slower short-term adoption — versus long-term partner trust.
Outcome
The CEO aligned on a foundation sprint first.

Research synthesis — affinity clusters from the partner interview rounds.

03

In fintech, a time filter is a truth definition.

Day / Week / Month couldn't be loose UI labels — they had to be product definitions.

Before adding features, I defined the data-truth layer. The clearest example: merchants reconcile against bank settlement, which lags across days and months, so Day / Week / Month couldn’t be loose UI labels — they became product definitions, and I separated the selected range from data freshness (“last updated”). I sequenced everything else as a staged roadmap, prioritizing by what has to be true before a feature is safe rather than what’s loudest.

Decision · Tradeoff

Decision
Chose a 00:00–23:59 day boundary, and split “last updated” from the selected range.
Tradeoff
Not technically perfect — but it matches the merchant's mental model and is explainable to support.

Time picker — before vs. after, with “last updated” separated from the selected range.

04

From POC to launched on every surface merchants use.

3× growth in two months — and fewer support calls as the data explained itself.

We validated through a POC with our partner P5K, then launched the merchant app across iOS, Android, and tablet, with onboarding and growth ops driving adoption. The result: 3× growth in two months — and noticeably fewer inbound support calls as the data became self-explanatory.

growth in two months

The merchant app live on iOS, Android, and tablet.

Trust isn’t a feature you add. It’s the foundation everything else — including AI — has to stand on.

05

AI as a safer layer on top of trust — not a magic box.

The human stays the decision-maker on anything that moves money.

Designed & prototyped · not yet shipped

With the data trustworthy, AI became the next layer. I designed two workflows — Discover (surface the anomalies worth attention) and Resolve (intent-driven action, e.g. finding a transaction to refund) — under firm guardrails: no silent execution, status-aware eligibility, and a full audit trail. The human stays the decision-maker on anything that moves money. This is designed and prototyped, not yet shipped.

Discover

Merchant opens the app without a specific task and needs to know what deserves attention.

  1. 01AI surfaces the anomaly
  2. 02Tap the summary
  3. 03Breakdown chart
  4. 04Filtered transactions
  5. 05Transaction detail
  6. 06Suggested eligible action

AI is the spotlight that picks the right thread. Drill-down is what lets the merchant pull it.

Resolve

An intent-driven request under time pressure — for example, finding a transaction to refund.

  1. 01Natural-language request
  2. 02Multi-match results
  3. 03User selects transaction
  4. 04AI drafts the action
  5. 05Review
  6. 06Confirm
  7. 07Receipt + audit

AI cuts search and diagnosis time, but the human stays the decision-maker on anything that moves money.

AI summary card — concept / prototype.

Review · confirm flow — concept / prototype.

Guardrails

No silent execution

AI can suggest, draft, and explain. It can never silently move money — every payment action is human-confirmed.

Status-aware eligibility

Available actions change with transaction state. Invalid actions disable before the merchant reaches a risky step.

Audit trail

Each action records what AI suggested, what the user chose, who confirmed, when, and the final state.

06

Trust before intelligence.

In fintech, intelligence has to be built on trust you earned.

Trust before intelligence

In payments, clarity and reconciliation are the product. AI only helps once the data is believable.

Earned ownership

I turned a UI task into a product by writing the first PRD, doing the research, and making the calls.

Evidence over instinct

The reposition came from multiple partner rounds and a real market signal — not a hunch.

Sister project — same employer, different scope

Read the CodePay platform case study

Thanks for reading

View More Projects