← Selected work · 02 — Fintech · BNPL · UAE + KSA
Postpay: making instalments legible at the moment of purchase
I led UX at Postpay for the moments that make or lose revenue. Here they are reimagined as two prototypes you can use.
- Role
- Senior product designer
- Years
- Apr 2022 – Aug 2024
- Markets
- UAE and Saudi Arabia
- This page
- Reimagined 2026, not shipped UI
The problem
In buy-now-pay-later, revenue and trust are decided at a few moments: approval, repayment clarity and coming back. Polished screens elsewhere don’t move them.
My role
Senior product designer at Postpay (Apr 2022 – Aug 2024): UX and product for the transaction journey, dashboard and lifecycle, with research and usability testing.
The result
Reimagined as two working prototypes: a checkout with exact instalment maths in English and Arabic, and one lifecycle shown across app, email and merchant dashboard.
01 — The problem
Revenue is made at three moments.
Postpay lets shoppers split a purchase into three interest-free instalments, while the merchant is paid upfront and charged per transaction.Public Sources: Forbes Middle East, MENAbytes.
That model puts the business at three points: whether a shopper completes the checkout, whether they understand and repay on time, and whether they come back. Polishing screens elsewhere does not move those. I treated them as the product.Judgement
For scale on the first moment: across all published studies, the average documented cart abandonment rate is 70.22%, and fixable checkout problems alone could lift conversion on an average large site by about 35% (Baymard Institute). A benchmark for context, not a result of mine.Public
02 — My role
Lead on the transaction journey and lifecycle.
I led UX and product transformation: the transaction journey, dashboard and lifecycle clarity, and the research and usability testing behind them, working with product, engineering and growth.Public
03 — Design decisions
Four design calls.
Show the whole commitment on one screen
A short checkout with terms behind a link is the common pattern. This version shows the amount, schedule, total and late-payment terms together before “Confirm”, because a regulated credit product earns trust by not making people hunt for what they are agreeing to.Judgement
Make the arithmetic exact
Instalments are computed in whole fils and the first instalment absorbs any remainder, so three payments always sum to the order total to the last fils. No “approximately”.Design-level
One vocabulary for the whole lifecycle
Upcoming, due, paid, late: the same four states, names and glyphs in the app, the email and the merchant dashboard, so a customer and a merchant describing the same order are describing the same thing.Judgement
Bilingual by structure
Two markets means Arabic and English. The layout uses logical properties so it mirrors for right-to-left from one component, instead of a second design that drifts.Design-level
04 — Prototype: checkout
Choose a plan, see exactly what you owe.
Pick an order total, switch plan, switch language. Everything a person needs to decide is on this one screen. Illustrative amounts; nothing is charged.
Try another order total
Language
- Fair rounding. Try AED 1,000.00: the first instalment takes the extra fils, so the three always add up exactly.
- Bilingual by structure. Switch to Arabic: the layout mirrors using logical properties, not a second design.
- Illustrative amounts and Arabic text. Nothing is charged.
Order total
AED 1,000.00
- TodayInstalment 1 of 3 · Due todayAED 333.34
- In 1 monthInstalment 2 of 3AED 333.33
- In 2 monthsInstalment 3 of 3AED 333.33
If a payment is late
In a live product, late terms appear here in plain language, with the exact amount and date, before you confirm. Illustrative in this prototype.
05 — Prototype: lifecycle
One state, three surfaces.
Change the instalment state and watch the app, the email and the merchant dashboard update together. Each state has a glyph as well as a colour, so meaning never depends on colour alone.
Set the instalment state
Customer app
Instalment 2 of 3
AED 333.33 · 12 Dec
Instalment 2 is due today
AED 333.33 is due today. Pay now to stay on plan.
Merchant dashboard
Order #4821
Paid outInstalment 2 of 3 due today
The merchant is paid upfront whatever the state, so the dashboard says so first and the customer state second.
06 — Outcome
What I can stand behind.
- Plan, schedule, total and late terms on one screen before confirmation.Design-level
- 4 lifecycle states × 3 surfaces rendered from one definition: 12 views, one source.Design-level
- 2 locales (English, Arabic) with full right-to-left mirroring from one component.Design-level
- Instalments that always sum to the order total, to the last fils.Design-level
How I would validate it: a five-person unmoderated test on “choose a plan, then say what you will pay and when”, measuring completion, time on task and wrong answers. I don’t quote Postpay’s shipped metrics here because I can’t evidence them.
07 — What I’d instrument
Measure the three moments from day one.
I’d put analytics on checkout completion, approval rate and on-time repayment rate before shipping, so every later design decision has a number behind it rather than a story.Judgement