Product Design

Census Pay

An open-banking payments app for SMEs: instant account-to-account transfers at half the fees.

Census Pay mobile app screens showing an account-to-account payment confirmation and transfer status
Client
Census Pay
Services
Product Design, UI/UX
Platform
Mobile app
Industry
Fintech

Census Pay is a mobile payments app for small and mid-sized businesses. Built on open banking, it lets a business pay another business account-to-account, receive its money instantly, and cut more than 50% off the transaction fees it would pay on a card or processor. I led the product design, from the first flows to the shipped app.

Census Pay app icon — a green arch mark — on an iPhone home screen, with the Census Pay label below it
The Census Pay brand mark on the home screen — a calm, confident first impression for a financial tool.

Overview

Most SMEs run on payment tools built for consumers or large enterprises. They wait days for funds to clear and lose a slice of every transaction to processor fees. Census Pay connects directly to bank accounts through open banking, so money moves between businesses without a card network in the middle, settled in seconds at a fraction of the cost. My job was to make that feel obvious and safe to a business owner who isn't a fintech native and doesn't have time to learn one.

Challenge

The bank-linking step was the first real wall. Connecting an account routes the user out to their bank's authentication and back, and any confusion there kills the flow before a single payment is made. I had to design a handoff that set expectations before the user left the app and reassured them the moment they returned.

A2A payments are also irreversible in a way card payments aren't, with no chargeback to fall back on. So the screen before a transfer had to surface the right details (who, how much, which account) clearly enough that a busy owner double-checks without feeling slowed down. And the states after it (sent, received, failed) had to be unambiguous, because "is the money there?" is the only question that matters.

I also had to make the lower fees legible without overselling them. The savings are real, so I showed them as a plain number at the point of payment, not as marketing.

Census Pay dashboard on iPhone showing the business name, today's total volume, payments count, fees saved, a weekly orders chart, and a Receive Payment button
The home dashboard leads with what an owner actually asks: how much moved today, how many payments, and how much they saved in fees.

Approach

I started by mapping the business's mental model, not the rails. Owners think in terms of "pay this supplier," "did I get paid," and "what did this cost me," so those became the spine of the app rather than the underlying open-banking mechanics.

For bank linking, I designed a guided handoff: a short, plain-language screen explaining what's about to happen and why it's safe, then a clear return state confirming the account is connected. The redirect stayed, but it stopped feeling like falling off a cliff.

For payments, I designed every state as a first-class screen: pending, instant confirmation, received, and failed with a clear reason and next step. The confirmation screen leads with the payee and amount, with the source account and the fee saving right below, so the decision and its value sit in one glance.

Two iPhones showing the Census Pay request-payment flow: entering an amount on a keypad, and a generated QR code with a shareable payment link
Requesting a payment: set the amount, then share it as a QR code or a link — the payer doesn't need the app open to send.

I kept the visual language calm and high-contrast, with generous spacing and a restrained palette, so it reads as a financial tool rather than a lifestyle app. I worked closely with engineering on what open banking could and couldn't return in real time, so the designed states matched what the system could actually deliver.

iPhone notifications showing three Census Pay 'Payment received' alerts, each with an amount in OMR, the payer's name, and an invoice number
'Payment received' notifications answer the only question that matters after an account-to-account transfer — is the money there — with who, how much, and which invoice.

Outcome

Census Pay shipped as a focused, trustworthy app that does three things well: pay another business, get paid instantly, and pay far less to do it. The bank-linking flow turned the riskiest moment into a confident one, and the explicit payment states removed the "did it work?" anxiety that follows account-to-account transfers. The fee saving, over 50% versus card and processor rails, is shown plainly at the point of payment, which is exactly where a business owner decides whether a tool is worth keeping.

Two iPhones showing Census Pay transaction screens: a single transaction's details with a refund option, and a scrollable transaction history list with amounts and statuses
Transaction history and details — every payment is traceable, with a clear status and a refund path when one is needed.

Building something in fintech? Start a project with us.