Fintech payments app

The client runs a financial product where people move and manage money, so the bar was never just "make it look nice." They needed someone who could own real product work over time — not a one-off landing page, but a payments app that handles sensitive flows, holds up under daily use, and keeps evolving as the business adds features. That kind of work needs a developer who can be trusted with a live product and paying users, not a template assembled overnight.

I work on this as an ongoing engagement, building and maintaining both the mobile and web sides of the app. The work covers the screens and flows users actually touch — payment actions, account state, the parts of the interface where mistakes are expensive — along with the steady stream of changes a real product needs: new features, fixes, and refinements shipped on a continuing basis. Because it's a financial product, correctness and clarity matter more than flash, so I build for flows that have to behave predictably every time.

The product is shipped and live in production, serving real users, with development still ongoing rather than finished and handed off. That continuity is the point: the client kept me on to keep delivering, which is the clearest signal that the software does its job and that the working relationship holds up over the long run.

This case is here for a simple reason — it's proof that I deliver real software, not just templates and quick fixes. Building and maintaining a live payments app for a paying client, in production, over time, is a different category of work, and it's the standard I bring to the rest of what I do.