Banking that answers the question you actually have
Most account screens are built to display everything at once. Bayprime starts from a different question: what do you need to know in the four seconds you have while standing at a checkout? Everything else is arranged around that answer.
Four rules we hold ourselves to
They are not slogans. Each one shows up in specific decisions across the product.
Calm over clever
Money apps get read under stress. Generous spacing, one clear number per screen, and no decoration that competes with the balance.
Always say where you are
Every request carries a visible status and a full history. Nothing changes silently, and no state is a mystery.
Boundaries in the data layer
Access control is enforced by the database, not just the interface, so a bug in a screen can never expose someone else’s account.
Fast on a mid-range phone
Server-rendered pages, a small client bundle, skeletons instead of spinners, and layouts that work from 360px upward.
How the product is built
Nothing exotic. A conventional, well-understood stack, used carefully.
Next.js (App Router)
Server components, server actions, route protection
TypeScript
Strict mode across the whole codebase
Tailwind CSS
Token-driven design system with CSS variables
Radix UI primitives
Accessible dialogs, menus, tabs and form controls
Supabase
Auth, Postgres and row level security policies
Recharts
Income, spending and review-queue charts
Ready to look around?
Open an account and explore every screen, or read the help centre first if you want to know exactly what happens behind each button.