RappiPay is the fintech arm of Rappi, one of Latin America's largest super-apps. I joined as the designer responsible for payments and collections - the most financially critical flows in the product, across all 5 markets simultaneously (Mexico, Colombia, Peru, Chile, and Brazil)

ROLE

Product Designer
Mar 2022- Oct 2023
Remote from Lima, Perú

SCOPE

Payments & Collections
Concept validation, User-journey mapping, Design and solution prioritization
UX strategy · Multi-market content · Dev handoff · Design Ops

TEAM

Global Design Tribe + Squad
Research, Product design, PO, Development
LATAM

Company Scale (2022 - 2023)

Monthly active users

30M+

across 9 countries

RappiCard Funding

$112M

raised Oct 2022

Revenue Growth

↑ 37%

$624M → $856M

Cards Issued

220K+

40% first-time holders

The Work: Payments & Collections

I owned the end-to-end design of the core financial UX, the flows that directly determine whether users can pay, manage debt, and stay in control of their finances across markets.

  • RappiCard payment experiences

  • End-to-end checkout systems

  • Collection flows for users in arrears

  • Payment settings and recurring payments

  • Multiple payment methods (QR codes, barcodes, direct debit)

  • Integrations with financial partners across 5 countries

Our users manage their finances in different ways, shaped by their lifestyles and needs. Our goal was to equip them with clear, comprehensive tools that make financial control simple and effective.

For 40% of RappiCard users, this was their first credit card. A confusing payment flow wasn't just a UX problem, it was a financial inclusion problem.

The multi-market complexity

Every flow had to work across Mexico, Colombia, Peru, Chile, and Brazil, with different banking infrastructure, regulatory requirements, and financial literacy levels. Content had to be managed in Spanish, English, and Portuguese, adapted for each country's specific terminology and legal language.

Design Tribe: Understanding the Team Needs

A design tribe of 25 people working across multiple squads and markets, with no shared framework for how to approach requirements, no documented ways of working, and no tools to support career growth.

Why it mattered: As Rappi's design function matured from execution to strategic partnership, the team needed infrastructure to match. The Design Ops initiative gave 25 designers a shared language, reduced process friction across squads, and created the foundation for a more autonomous, high-performing team.

Co-led a Design Ops initiative and help building tools for the team

Process

We worked within a Think → Build → Validate loop, adapted to the pace of a fast-moving fintech squad:

Think - Analyze user needs, existing research, business goals, and market-specific use cases to define the right problem before touching design tools.

Build - Start with an MVP. Move fast, make decisions, test ideas with real users before committing to full builds.

Validate - Ship, measure, iterate. Every flow was a hypothesis. We used post-launch insights to identify friction and improve continuously.

This wasn't a rigid process - it was a mindset that kept us from over-designing and under-shipping.

RappiPay taught me what it means to design at scale under real constraints - It sharpened my ability to prioritize ruthlessly, collaborate across large cross-functional teams, and build frameworks that outlast any individual feature.

RappiPay Product