For fintech
every screen is a record someone will audit.
A transaction view is not a table. It is a record somebody will later reconcile against a second system, export for an auditor, and have to explain a discrepancy in. Authorised, pending, settled and reversed are four different states, and most interfaces draw them as one.
what ships — 5 rows
What ships
- Transactions
- states for authorised, pending, settled and reversed
- Reconciliation
- two sources side by side, discrepancies first
- Audit trail
- who, what, when — and no silent edits
- Exports
- what leaves matches what was on the screen
- Shipped as
- Figma variables and production components
What ships
- Transactions
- states for authorised, pending, settled and reversed
- Reconciliation
- two sources side by side, discrepancies first
- Audit trail
- who, what, when — and no silent edits
- Exports
- what leaves matches what was on the screen
- Shipped as
- Figma variables and production components
what I’m not.
I am not your compliance advisor. I build the interface that makes your policy visible and enforceable; a lawyer or a compliance officer decides what the policy is. I don't write your controls and I won't tell you what your regulator will accept.
what I can show you.
No published fintech work yet. The nearest real thing is DEVSFORFUN — the identity and billing layer seven products run on, including the checkout on this site, where the money is real and the ledger has to survive a retry.
what it costs.
every line item, priced →Launch
$5,800$5,300
you save $500
brand core + website + social kit
Product
$11,300$10,500
you save $800
brand core + website + design system, standard tier
Everything
$16,400$14,900
you save $1,500
Product + the build at the system-owner rate
start by finding out what’s wrong.
$500, five days, a recorded walkthrough and a written action plan — and it comes off the project if you book one.