Sean MarcanoSenior Product Design Manager

Moneda · 2021–2023

Mobile Secure Digital Wallet

Mobile Secure Digital Wallet

Role

Co-founder & Lead Product Designer

Timeline

2021–2023

Team

3 Co-founders + Design Team

Skills

UX Design, Product Design, User Research

55% of the Dominican Republic had no bank account. Cash was the only option — and COVID made it dangerous.

55%

Of DR's working population without access to banking

43%

Handling significant sums entirely in physical cash

3 yrs

Of iteration across three major versions

In 2021, the COVID-19 pandemic amplified a problem that had existed for decades in the Dominican Republic: 55% of the population had no access to banking. Physical cash was the only option — and carrying it had become genuinely dangerous as crime rates climbed alongside pandemic-driven job loss.

I co-founded Moneda to close that gap. Not by adapting a Western fintech product for a new market — but by going to the Dominican Republic first, learning how people actually moved money, and building something designed for that reality from the ground up.


Two Google Design Sprints. Two weeks. Before we booked a single flight.

We started with two back-to-back Google Design Sprints — five focused days each — before traveling to the Dominican Republic. The goal wasn't to design the product. It was to surface the assumptions we were carrying so we could test them against reality in the field.

Each sprint forced us to move fast: map the problem on Monday, sketch competing solutions Tuesday, commit to a direction Wednesday, prototype Thursday, test Friday. By the end of two weeks we had a clear picture of what we thought we knew — and a list of questions that only the field could answer.

What the Sprints Revealed

We discovered early that our initial assumptions about user trust, payment behavior, and digital literacy were built on a Western fintech mental model that didn't apply. The sprints didn't produce the product — they produced the right questions to take into the Dominican Republic.

Full sprint wall — wireframes, storyboards, and sticky notes from two design sprints
The sprint wall after two weeks. Every decision mapped, every assumption made visible.
HMW questions from design sprint — 'Will we be able to load people's wallets?'
HMW questions anchored each sprint day to the user's actual problem.
Competitor mapping — Ali Pay, PayPal, Venmo, M-Pesa, WeChat Pay and regional alternatives
Mapping the competitive landscape before designing anything.
Journey map from design sprint week one — user flow and decision points
Journey mapping: where does trust break, and where does it build?
Storyboard and wireframe wall from sprint week two
Storyboards from week two — translating research into interaction concepts.

We went to the Dominican Republic. We listened before we designed.

We traveled to the Dominican Republic and visited colmados — the corner stores that function as informal financial and social hubs across Dominican neighborhoods. We ran structured interviews and observations with residents across income levels, ages, and degrees of smartphone familiarity.

Three questions drove every conversation: Would users trust a digital wallet? Was going digital compelling enough to change deeply ingrained behavior? How do we get something real in front of users fast enough to learn before we overbuild?

The Central Finding

Trust was the entire product. Not features. Not speed. Not polish. If the app didn't feel safe and transparent from the very first screen, nothing else would matter. Every version of Moneda that followed was built on that single insight.

Moneda team in a colmado in the Dominican Republic — field research visits
Meeting users in the colmados — the informal financial hubs of Dominican neighborhoods.
User testing a Moneda prototype in the Dominican Republic
Putting prototypes in real hands, in real environments, before building anything.

A brand built for the Dominican Republic — not adapted for it.

Out of the sprint work and field research came a visual identity built from scratch for this context. Deep green and warm gold pulled from the landscape and culture of the Dominican Republic. Typography chosen for warmth and legibility in Spanish. A mark simple enough to work across screens, receipts, and a t-shirt worn in a colmado.

Moneda masterbrand — logo, wordmark, and secondary icon
Wordmark and secondary icon.
Moneda typography system — Noto Sans Bold and Regular
Typography: Noto Sans, warm and approachable.
Moneda color palette — deep green, gold, and community colors
Color palette: deep green, gold, and an expanded community range.
Moneda representation colors — skin tone range for community imagery
Representation colors: a brand built to reflect its community.

Representation was a core brand principle — not an afterthought. The identity system included a skin-tone range for community imagery and explicit guardrails for how the brand showed up around real people from the Dominican Republic.

The brand extended into the field: the team wore Moneda in the colmados where we were conducting research — grounding the product in the community it was built for.

Moneda branded t-shirt — deep green with gold wordmark on color block background
The brand worn in the field. Presence in the community it was building for.

Paper prototypes in colmado parking lots. Real signal before real investment.

Phase 1 had one goal: prove usability before spending a single hour on high-fidelity design. We ran crazy-eights sessions to generate directions fast, built paper prototypes, and took them back into the field — testing with real users in the same environments where the product would actually be used.

Interactions that seemed obvious to us were invisible to first-time digital wallet users. Language that felt neutral came across as cold and institutional. Those failures weren't setbacks. They were the most valuable research we ran. Every decision in Phase 2 traced back to something that broke in a colmado parking lot.

Moneda 1.0 — the initial screen set built for low-tech-literacy users
Moneda 1.0: spacious layouts, minimal visual density, and a color language drawn from the Dominican Republic flag.

Field research pointed to one clear insight: QR codes were the most trusted and intuitive payment mechanism for our users. We built the entire navigation around that.

We removed the tab bar and replaced it with large circular primary action buttons — three clear transaction paths, minimal visual footprint, maximum clarity at the moment of decision.

Moneda 1.0 navigation — QR-primary circular action buttons replacing a traditional tab bar
Navigation built around QR-first behavior.

Most iterations happened in code, not in Figma.

Between 1.0 and 2.0, the core design elements underwent extensive revision — but more importantly, the way we worked changed. Most iterations in this phase were carried out directly in code, prototyping on functional app builds rather than static mockups.

That decision made the feedback loop tighter and the signal cleaner. The gap between design decision and real-world consequence almost disappeared. What you saw in a meeting was what users were actually holding.

One of the most important — and most context-specific — challenges that emerged in 2.0: displaying an account balance in public in the Dominican Republic is a genuine safety risk. On a crowded bus, at a colmado counter, in a street market — your balance visible on screen makes you a target.

We needed a way to hide it. But the solution had to work on every device, not just Retina screens. We ran five distinct explorations: var 1 was the control, balance shown clearly. Vars 2 and 3 tested different scrambled character patterns. Var 4 returned to a clear display as a comparison anchor. Var 5 used block pixelation — chunky enough to be unreadable at a glance, but clearly intentional rather than a glitch.

Five balance display variants — from fully visible to block pixelated — exploring how to hide sensitive financial data in public
Five variants tested on real builds. Var 5 — block pixelation — won. Readable on every device, unambiguously intentional.

Moneda didn't operate on peer-to-peer transfers alone — it ran through a network of verified agents: local businesses, corner stores, and colmados registered to process transactions. The product had to work for both sides of that exchange.

Moneda agent discovery — map view showing nearby verified agents with ratings, distance, and hours
Users search for a nearby verified agent — rating, distance, and hours shown upfront.
Moneda QR ticket stub — order amount, 4-hour countdown, and agent address
The ticket stub: a QR code, the amount, a countdown, and the address. Everything needed to complete the transaction.
Moneda custom partner QR codes — branded color variants per agent partner
Each partner gets a custom-branded QR. A brand loyalty moment built into the transaction itself.
Moneda agent-side flow — incoming request, transaction details, processing, and success confirmation
The agent side: incoming request, transaction review, processing, and confirmation — a complete parallel experience.

Solving for the DR Peso — and for the ride home.

2.1 refined two things the field had surfaced: how users enter large amounts in a high-denomination currency, and the implemented solution for the balance security problem explored in 2.0.

The DR Peso is 56:1 against the USD — users regularly input four- and five-digit amounts. Before testing, I had an idea I thought would be distinctive: a ruler-style scrolling input that let users move through values like a physical dial.

It made sense on paper. In practice, users found it disorienting and slow. The interaction asked too much of people who were already navigating an unfamiliar product.

Pre-testing number input concept — ruler-style scrolling dial
The pre-testing concept. Distinctive, but it got in the way.

The answer was simpler: revert to the system keyboard. The interaction users already knew from WhatsApp and their native dialpad. Keyboard open on arrival, no custom chrome, no learning curve. We moved straight to high-fidelity and tested across iPhone SE and Android.

Moneda number input hi-fi — system keyboard across light and dark themed screens
The shipped number input — system keyboard, immediate focus.
iOS system phone keypad — the familiar interaction pattern used as the foundation
Built on what users already knew.

The pixelation approach from the 2.0 exploration was implemented and shipped. Block pixelation worked across every device — no Retina requirement, no ambiguity. Users understood instantly that the content was hidden on purpose, not broken.

Moneda balance hide feature — pixelation implemented in the shipped product
Pixelation implemented. Reliable on every screen, in every setting.

The green circle that travels with the user.

One of the most distinctive decisions in Moneda's design system was a dynamic green circle that shifts position throughout the app — appearing when a transaction completes, when an action needs confirmation, when a state changes. It's a visual cue, not a notification. A guide, not an alert.

Users begin to anticipate it, recognize it, and trust it. In an app where trust is the entire product, that kind of behavioral anchor matters more than it might anywhere else.

Moneda green circle — dynamic visual cue traveling through the user experience
A consistent anchor guiding users through every transaction state.

The broader system was built on reusable components, a consistent type scale, and Spanish-language copy written for the user rather than the product. Warm earth tones and deep green conveyed familiarity and trust — giving a growing team the foundation to ship new features without breaking the coherence that users had come to rely on.


A product that raised capital, moved legislation, and filled a gap LATAM fintech left open.

Moneda full product flow — dashboard to agent selection, confirmation, and QR order ticket
The complete transaction flow: balance → enter amount → find agent → confirm → QR ticket. End to end.

$270K

Total investment raised — starting from a $20K family & friends seed round

0.05%

Of small businesses ever raise startup venture capital (Fundera). Moneda did.

Law

Product contributed to pushing open banking legislation in the Dominican Republic

Moneda raised a $20,000 seed round from family and friends — then went on to secure $270,000 in total investment. Getting a product funded at all is rare: according to Fundera, only 0.05% of small businesses ever raise startup venture capital. Designing something worth investing in is a different kind of proof of concept.

Beyond the capital, Moneda contributed to a larger shift: the product became part of the conversation that helped push open banking legislation forward in the Dominican Republic — creating the legal framework for the kind of financial access the platform was built to provide.

At the time, LATAM was being left behind in the global fintech moment. While other markets were solving digital payments at scale, micro business owners and unbanked residents in the Dominican Republic had no viable option. Moneda was designed specifically for that gap — equitable design for MBUs navigating a cash-only lockdown economy, in a language and context that made sense for them.

What I took from this

This project taught me how to run a Google Design Sprint end to end — and what it looks like when that method is used as a research tool rather than a shortcut to answers. The field trip, the paper prototypes, the code-first iteration — none of it would have worked without the sprint structure forcing us to make our assumptions visible before we acted on them.

Next Project

Openfit · 2021

Express Checkout & Churn Prevention

33% less churn. 8% more conversions.

Express Checkout & Churn Prevention