Purpose Payment came to Codeeo with a first release that had to be small enough to ship and strict enough to be trusted.
About the client
Purpose Payment is a payments product, which means the first version was not judged on how much it did but on whether it could be trusted with money at all.
What they needed
A first release that could actually ship. Payments products drown in scope: every reviewer wants one more control, one more report, one more edge case, and the product never reaches a customer.
It also had to be defensible from the first day. In a financial product, what a user can see, approve and undo is a security decision rather than a design preference.
What we built
A mobile app cut down to the one job it had to do well, with everything else written on a list for later. That single decision is what let it ship while the idea was still current.
Design and engineering ran together rather than in sequence, because the interface is the control surface. Confirmation, approval and reversal were designed with the people building the logic behind them.
The build was documented as it went, so a security review reads the same story the team tells rather than a reconstruction after the fact.
How we worked
We agreed the first release by asking what could be removed rather than what could be added.
Nothing shipped on the say so of design alone: every control that touches money was reviewed by both sides of the team.
The app, the stores and the accounts are the client's.
Services provided
- Online store
- WooCommerce
Related services
