Yuno
I was part of Yuno’s founding team. We built the platform and mobile SDK for a payment orchestrator serving LATAM; I took responsibility for the core product flows from the start.
Role
UI/UX Designer
Timeline
2 years
Team
PM, PO, stakeholders and another designer
Year
2021
the challenge
A merchant needs to understand its payments even when several providers are involved. An orchestrator brings those connections and decisions into one platform: technical complexity has to become information and controls people can use.
At Yuno, that challenge began with building the product itself. My early responsibility covered the core flows, with Payments as a central piece: the place where clients would view their payments. The scope grew to span nine areas of the platform.
my approach
I worked with PM, PO, stakeholders and another designer as we built the platform and mobile SDK. Being part of the founding team meant working on the core flows from the beginning, connecting business needs with product experiences.
The scope crossed several ways of using Yuno: reviewing payments, understanding data, configuring checkout, and working with connections and routes. Docs and the Design System were also part of my responsibility, alongside the interfaces clients used to operate.
Understand and operate payments
Payments
One of the first flows I took responsibility for. I built an operational surface that brought together payments, transactions, fraud reviews and payouts so teams could understand merchant activity without getting lost across different providers and payment methods.
I organized search, filters and the hierarchy of statuses, amounts, providers and methods to make large volumes of information easier to scan. From the list, users could move into each payment, understand its timeline and inspect its transaction data, as well as perform tasks such as exports and batch refunds.
Insights
I built the platform’s complete metrics experience, turning payment activity into information teams could interpret and use. I designed the overview and the volume and conversion-rate views as a complement to Payments: moving from individual transactions to understanding overall performance.
I also worked on chart customization so each team could configure the information it needed to analyze and adapt the view to different goals. The challenge was organizing metrics, filters and visualizations without losing clarity, making both the broader picture and specific changes in payment behavior easy to understand.
Reconciliation
I designed the reconciliation experience to connect payment records with the information needed to verify their correspondence. Unlike everyday transaction review, this flow needed to help teams examine relationships between data and clearly identify what required attention.
The work focused on organizing operational information and preserving context throughout the review, so teams could move from an overview into the necessary detail without losing track of the payment they were reconciling.
Build the payment experience
SDK Checkout
The payment experience that reaches the buyer. The work included the mobile SDK, a piece that needed to coexist with the merchant’s application. This area connects Yuno’s platform to the moment someone makes a payment.
Checkout Builder
I built the experience merchants used to configure and publish their checkout from the platform, with control over themes, orientation, typography, payment forms, additional fields and the card-enrollment experience.
The main challenge was connecting each configuration decision to its buyer-facing result. I designed a direct desktop and mobile preview that let teams validate changes in context and understand how the checkout would behave before publishing it.
Routing
I built the orchestration experience through tailored solutions, translating complex payment infrastructure into visual flows that teams could configure and understand from the platform.
I designed flows to detect drops in approval rate and trigger threshold alerts; configure rules and blocklists; define the expected max delay for each provider; and create decline groups with the conditions that determined their path. I also worked on Smart Routing, an AI-assisted feature that distributed traffic intelligently across providers, either automatically or through percentages set by the user.
Connections
The space for provider connections. My responsibility for Connections was part of building the orchestration platform: making the integration layer behind payment processing visible and understandable.
Give the product a shared foundation
Docs
Documentation was also part of my scope. It is where the product meets the people who need to understand and integrate it: information structure and readability are part of the Yuno experience.
Design System
The shared visual and component foundation of the product. I owned the Design System alongside platform flows, with the challenge of maintaining coherence across surfaces as different as payment views, configuration and checkout.
more projects
