I recently needed to send money to someone I had already paid a few days earlier.
The first time was straightforward. Add recipient. Enter account number and bank code. Input amount. Add reference. Confirm with safeguards in place.
All expected. But a few days later, I wanted to send the exact same amount to the exact same recipient. This is where the system failed the principle that “time is money.”
Instead of recognising context, I had to:
– Search through a long list of saved recipients.
– Select the same person again.
– Re-enter the amount.
– Re-enter the reference.
When I tapped into the recent transaction, I could see all the details of the previous transfer — the amount, the beneficiary, and the reference.
The system had the information. But it made me repeat it. This is pure redundancy.
In financial infrastructure, small inefficiencies compound. Three unnecessary steps, multiplied across thousands of daily transactions, amount to hours of lost human time.
When designing KiiBank, we saw this as an opportunity.
Inside the transaction details, we added a deliberate “Repeat Transfer” feature.
One button. Context preserved. Recipient pre-filled. Amount is editable if needed. Reference adjustable.
What used to take several redundant steps becomes a single, intentional action.
This is not about adding features for the sake of innovation. It is about removing the friction that users have quietly accepted for years.
Every feature we design is intentional. If it does not solve a real pain point, it does not make it into the product.
Because in digital banking, efficiency is not a luxury. It is a respect for the user’s time.
Where in financial services have we normalised repetition that technology could eliminate? I’m interested in hearing what others have experienced.
hashtag#DigitalBanking hashtag#ProductDesign hashtag#FinTech hashtag#UserExperience hashtag#KiiBank
