← All work Case Study

Shukran Pay · Wallet

Making restricted
money make sense.

Shukran Pay needed to lock wallet money to specific brands — and still feel effortless. I rebuilt the whole wallet so the restriction reads as clarity, not fine print.

RoleDesign Lead
SurfaceMobile app
ScopeFull wallet redesign
StatusShipping · 2026

Where this sits

The wallet behind the cashback.

Shukran Pay is the in-app wallet across Landmark's brands — where cashback, refunds, and promotional credit land and get spent. The product always existed. What changed is what the business needed from it.

For this year's big campaigns — White Wednesday and the rest — money had to be restricted to specific brands: cashback from one brand spendable only there, refunds and promos usable across a defined set. That restriction is what makes branded cashback campaigns possible in the first place. But a restriction users can't understand is just confusion with rules. So the wallet had to be rebuilt around it.

The problem

A balance you couldn't trust.

The old wallet showed one big number — then undercut it. Below the balance sat a pile of “brand credits,” each with its own amount and its own expiry, spread across a horizontal scroll and a dense list. The money was technically all there, but you couldn't tell what you could spend, or where.

If a user can't answer “how much can I actually use at this brand right now?”, no cashback campaign built on top of that wallet will land. The clarity problem was the business problem.

Old to new

Drag to see the rebuild.

Here's the old wallet home on the left, the redesign on the right. Drag the handle across to compare.

Before Old Shukran Pay home: a wallet balance with a cluttered row of brand credits, each with its own expiry.
After Redesigned Shukran Pay home: a single clear card scoped to a brand, with balance breakdown and clean recent transactions.
↔

Drag the handle — old wallet / redesign

The core idea

Two buckets, not eight footnotes.

The restriction is real and a little complex — some money is locked to one brand, some travels across a defined set. The old design exposed all of that complexity at once: every credit, every brand, every expiry, in a list. The redesign hides the machinery and shows the two answers a user actually needs — what's locked to this brand, and what travels.

Before every credit, every expiry
Old brand-restrictions sheet: a long list of per-brand credits with individual expiry dates.
After what's locked, what travels
Redesigned balance breakdown: two buckets — Centrepoint Only and Landmark Brands — each explained in a sentence.

The brand-restriction breakdown, before and after

The part I'm proudest of

One tap to the whole picture.

The card shows the balance for where you are. Tap Balance Breakdown and it opens into the full split — total, what's locked to this brand, what travels, and a plain-language line on each. The complexity is one tap away, never in your face.

Balance breakdown — tap to reveal the split

In motion

The wallet opens as you scroll.

The card stays put while the activity sheet rises over it — so the balance is always in view and the detail comes to you.

Scrolling the wallet home

What the rebuild touched

The whole flow, not a screen.

Making restricted money legible meant rethinking the wallet end to end — every place the money shows up, moves, or expires had to speak the same language.

Why it matters

The enablement layer.

This shipped for this year's campaign calendar. Now that the wallet makes restricted money legible, brands can configure cashback campaigns and credit them to users — with confidence that people will understand what they've been given and where to spend it.

It's going live as I write this, so the numbers will come later. But that's the nature of an enablement layer: the design isn't the thing users celebrate — it's the thing that lets everything on top of it work.

How I think about it

The hardest part wasn't adding the restriction. It was making a rule feel like a helpful answer instead of fine print.