Fintech · Design-led
Ding
A three-second promise, made easy to trust.
Ding sends mobile credit across 600+ operators, usually in under three seconds. We designed the system behind that promise: clear country selection, careful failure states, one product language across web and mobile, and a Rewards Club built around the relationships behind repeat top-ups.
- Design System
- Product Design
- Web Design
- UI/UX
- Mobile
Every state,
before it happens.
Scroll →
The work behind a three-second promise
Ding’s whole proposition is speed and certainty: money leaves you here, credit lands on a phone in Lagos or Kingston or Manila, and it happens before you have put your own phone down. That promise is easy to say and unforgiving to design. Every screen has to be legible to someone sending their first top-up, in their second language, on a bus, worrying whether it worked.
A design system that plans for the bad day
Most component libraries are a catalogue of things going well. This one is not. Alongside the buttons and the country pickers sit the states that actually decide whether someone trusts you with money again: Failed to connect. Something went wrong. Are you sure you want to delete?
Drawing the failures with the same care as the successes is the difference between a system that looks good in a presentation and one that holds up at 2am when a payment bounces. Every message got a tone, every destructive action got a second chance, and every country in the picker got its flag, its dialling code and its own row, because “search country” is the first thing most people touch.
The Rewards Club: medals, not points-farming
Loyalty in this category usually means discount mechanics. Ding’s Rewards Club is built around something better suited to the behaviour: medals for the things people already do. Sent a top-up. Sent to someone new. Sent again to the same person.
That last one is the whole insight. Repeat sending to the same number is not a transaction pattern, it is a relationship: a daughter topping up her mother every month. The system celebrates it rather than trying to upsell it.
One language, every surface
Web, app, dashboard, receipts. The same components, the same voice, the same reassurance that the money went where you sent it. The point of the system was never consistency for its own sake. It was that a person sending twenty dollars home should never have to learn the interface twice.