Skip to content
PixelformBuy the $500 audit

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

Transactions
States for authorised, pending, settled and reversed
Reconciliation
Two sources side by side, discrepancies first
Audit trail
Who, what and when, and no silent edits
Exports
What leaves matches what was on the screen
Shipped as
Production components and a documented system

Three surfaces, and the constraint each is under

The three surfaces a fintech interface needs, and their constraintsTransaction history: Immutable record, Exportable. Reconciliation view: Two sources, one truth, Discrepancy states. Audit trail: Who, what, when, No silent edits.Transaction historyImmutable recordExportableReconciliation viewTwo sources, one truthDiscrepancy statesAudit trailWho, what, whenNo silent edits
Three surfaces, and the constraint each one is under.

What the studio is not

Not your compliance advisor. The studio builds the interface that makes your policy visible and enforceable; a lawyer or a compliance officer decides what the policy is. It doesn't write your controls, and it won't tell you what your regulator will accept.

What there is to show

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.

Start by finding out what’s wrong.

$500, five business days, a recorded walkthrough, a written action plan and a competitor table, and it comes off the project if you book one.