Payments bank B2B platform

A portal that opened on a menu, not on money

The home page was eleven tiles under a second navigation bar, with no money on it. One account, one balance. Exporting your own transactions meant requesting a file and waiting in a queue. One column header read "Renamed Date", an internal state leaking into the page.

Four competitors, walked screen by screen

I compared six payment platforms, and walked four of them flow by flow myself. I plotted the client in the weak quadrant and named six defects in its product.

One competitor split its views into all accounts or one. And bank staff described an access model nobody had written down, so I drew it.

Four layers, one commit

The client asked for something like that one-or-all switch. I set the two-state switch aside, because this product had four layers to resolve: eight products, merchant IDs, a three-level account tree, and roles that cut across that tree.

1

Products

Filter by biller type. Every product shows its balance before you choose, and the default is kept apart from the current one.

23

Merchant IDs and the account tree

A parent can be partly selected through two generations, shown as a checkbox state and a count. Nothing changes until you apply.

4

Role, and the context card

Company, product, accounts and balance stay on every page, with the user and their role beneath.

Designed, not built. Screens from my design files, with the client's name, logo and brand red removed.

Seven items, money first, and a new library

One rail of seven items, and a home page that opens on the user's money. A context card holds company, product, accounts and balance on every page. In the refund flow, the eligible amount is shown before you type, and an ineligible transaction shows the action disabled, not hidden.

The old library was beyond repair, and it served the bank's other products. This was the first of a new class of products, so I built a new library on Untitled UI: 20 custom components, 348 primitives and 397 colour-mode variables, each set for light and dark.

Rotated off before it was built

I rotated off in November 2025. Settlements, chargebacks, report downloads and employee management were not designed by me. Of the six defects my research named, the export problem was never reached. The account model was the bank's. I wrote it down; I did not invent it.

Also: Ekam, a design method that runs with AI, Research and design system, agentic mortgage platform. Every role, team and date.