FoodPay (YemeksepetiPay)

A secure payment and virtual POS platform designed from scratch for merchants, operating under TCMB regulations.

6 months

Product Designer

Fintech / B2B

FoodPay - Desktop and mobile payment platform interface

Design Needs & Focus

FoodPay (YemeksepetiPay) is a payment and virtual POS platform designed from scratch to enable businesses to receive online payments securely, operating under TCMB regulations. From day one, the product was shaped with a strong UX foundation, taking regulatory requirements, security considerations, and financial operations into account.

The core design needs that guided the process:

Building a secure and regulation-compliant payment infrastructure for merchants

Establishing trust at the very first point of contact in a fintech product

Making security, verification, and error scenarios clear and understandable for users

Presenting critical financial information such as payments, settlements, and reports in a simple and structured way

Creating a scalable and consistent UI structure suitable for a product developed from scratch

Based on these needs, the entire experience was handled end to end, from the landing page and merchant onboarding flow to the dashboard and reporting screens.

Approach

The product was approached not as a set of individual screens, but as a complete journey — from a merchant's first interaction with the platform to actively receiving payments.

Trust, licensing information, and value propositions were clearly communicated on the landing page

The merchant onboarding process was divided into clear, manageable steps

Regulatory requirements were structured in a way that reduced cognitive load

Critical financial data was prioritized on dashboard and reporting screens

Web and mobile web were designed together with a responsive-first mindset

Research & Mini Benchmark

Since the product was built from scratch, a mini benchmark study was conducted to understand industry standards.

Platforms Reviewed

Iyzico

Stripe

PayPal

Focus Areas

Merchant onboarding and verification flows

Document upload and approval processes

How security and regulatory messages are communicated to users

The analysis showed that long and mandatory processes can be managed effectively through clear guidance, progress visibility, and well-crafted microcopy.

Wireframes

Wireframe work covered the following key flows:

Landing page structure and navigation

Sign-up and login flows

Merchant onboarding (authorized person details, business info, document upload, agreements)

Dashboard, transaction summaries, and reporting screens

A primary goal during onboarding was to clearly communicate where the user is in the process and what comes next.

Design System

A compact design system was created to meet MVP needs.

Standardized Components

Form fields, validation states, and error messages were standardized across all flows.

Visual Hierarchy

A consistent typography and visual hierarchy were defined for financial data presentation.

Reusable Patterns

Reusable components were created for security and status messaging. The system was designed to support future growth.

Design System Overview

UI Screens

All screens were designed responsively for both web and mobile web. Below are the main screen groups designed for the product.

FoodPay Landing Pages - Homepage, individual and business user pages, pricing page

Landing Pages - Web

Landing Page - Mobile Responsive

FoodPay Onboarding - Application info, authorized person details, commercial info, document upload, and agreements

Onboarding Pages - Web

FoodPay Dashboard - Main dashboard with balance overview, daily performance chart, next payment status, transaction history, and financial transactions view

Dashboard - Web

Dashboard - Mobile Responsive

Impact & Key Learnings

Impact

An end-to-end first product experience was successfully delivered for FoodPay

A regulation-compliant, trust-focused, and scalable UI foundation was established

Complex financial processes were made manageable from a user perspective

Key Learnings

In financial products, user experience affects not only users but also operational and support teams

Poorly structured onboarding increases long-term support load and operational costs

Trust is not built on a single screen, but through consistent and coherent flows across the entire experience