EasyKash
Egypt's payment gateway, redesigned end to end: the marketing site, the checkout, and the seller panel merchants actually spend their days in.
لوحة تحكم التاجر تستاهل نفس وضوح الموقع.
EasyKash is a real Egyptian payment gateway — cards, Meeza, mobile wallets, cash collection, and installment partners like ValU and Aman, all behind one integration. It is the kind of product businesses trust with real money, which means the interface carries more weight than most.
The marketing site had already had its 2026 pass: a soft sky gradient, clear type, one accent colour doing all the work. But the seller panel — the screen a merchant actually opens every single day — was still the old admin template: a solid blue sidebar wall, clip-art icons, gradient stat tiles, red and green Yes/No blocks on every form, and empty states that read "There is no data .. try to use data filter first."
So I logged into the real panel, wrote down every one of its 41 screens field by field, and rebuilt the whole thing against one system — the same one the new homepage uses — in English and Arabic, on phone and desktop.
The product outgrew its own interface
A payment gateway earns trust in small ways — a balance that's easy to read, a form that doesn't ask the same question five different times. Once the front door looks modern, the panel behind it starts to look like the older, less trustworthy part of the same product.
One brand, two eras
The homepage says 2026. The panel — where the actual work happens, every day, for money — still says 2018. That gap is the first thing a merchant notices after they sign up.
Six forms, one shape
Invoices, tickets, reservations, subscriptions, calendar slots and physical products were six almost-identical forms, each repeating the same 15-method payment grid and fee questions. One shared template, six thin layers on top, was overdue.
Proof beats a pitch
I could have written an audit of the old panel. Instead the deliverable is the panel itself, rebuilt, in the brand's own identity — something a founder can click through in five minutes and judge immediately.
Inventory first, opinions second
Nothing here was guessed. Every field, table column, empty state and error message in this redesign was copied from the real panel before a single pixel changed, so the rebuild loses no real functionality — it just stops repeating itself.
Log in, write it down
Every one of the panel's 41 screens got logged by hand — fields, table columns, buttons, empty states — before any design decision, so the redesign is grounded in the real product, not a guess at what a payment panel should look like.
One system, every screen
The tinted-neutral palette, the pill buttons, the segmented Yes/No control that replaces those red/green blocks — all of it comes from the same token set as the new homepage, applied to tables, forms and stat cards alike.
Bilingual as structure
Arabic isn't a mirrored English layout with swapped strings.
dir="rtl" sits on the page itself, every
spacing rule uses logical properties, and Arabic text renders
in Ping AR LT — not a fallback font standing in for it.
Three screens, no seams
The homepage sells it, the checkout closes it, the panel is where the merchant actually lives. All three now share one visual language, so moving between them doesn't feel like switching products.
The prototype covers the full information architecture with working interactions — steppers, filters, toasts, a bilingual toggle — on fictional demo data, so it can be clicked through end to end without a backend.
The obvious next step is wiring it to a real API: real balances, real transaction tables, and the product-creation forms actually saving something. The information architecture and every screen are already there to build against.