Express Ticket Checkout
A mobile-friendly checkout for paying a parking ticket. The interface renders from backend configuration, so one application serves clients with different requirements.
- Period
- Context
- My role
The problem
Every client wanted a different checkout — different fields, different steps, different payment methods. Shipping a build per client would have meant maintaining a fleet of near-identical applications.
How it was built
The backend describes the screen
The UI is rendered from configuration served by the backend, so a client's checkout is data rather than a branch. Onboarding a new client with different requirements is a configuration change, not a release.
Payment options as part of that configuration
Multiple payment methods are wired in and selected by the same configuration, so the checkout flexes to what each client actually offers.
Built for someone standing at a machine
This is used one-handed, on mobile data, by a person who wants to leave a car park. The whole flow is built for that moment.
Where it landed
- One application serving multiple clients with different checkout requirements
- New client configurations without a code change
Specification
- Pattern
- Payments
- Sector