When you simplify a payment screen and users still feel uncertain, the design has failed. That sounds like a paradox — because in fintech, simplicity has become almost a sacred principle. ‘Less is more’, ‘remove unnecessary fields’, ‘fit it into three steps’ — these phrases appear on the opening slide of every product roadmap. But what I observe in the field tells a different story. A usability study conducted late last year at a mid-sized software company building mobile banking products in Istanbul revealed that 53% of users who successfully completed an EFT transfer were not sure whether the money had actually been sent. The screen was clean. The flow was short. There were no errors. But there was no confirmation. This captures the core tension in fintech UX: simplicity does not automatically produce trust. Trust requires its own design discipline.Treating user experience in fintech as an aesthetic exercise is the field’s most expensive misunderstanding. Design teams spend hours on color palettes, button sizes, and transition animations while the post-transaction confirmation screen gets two lines of placeholder text. Yet the user’s mental model is asking a very specific set of questions: ‘Did the money leave? Did it go to the right account? When will it arrive?’ If those three questions are not answered directly on screen, user behavior follows a predictable path: the user retries the transaction, calls customer support, or closes the app and never returns. The second outcome increases support load; the third drives churn. Both are measurable and both connect directly to business results.It helps to think about trust-generating design decisions across three axes: transaction confirmation, error communication, and ease of reversal. Transaction confirmation is about the content of the success screen. Recipient name, amount, date, and a reference number — without these four elements, a confirmation screen is nothing more than a blank page that says ‘Transaction Successful.’ A problem I saw repeatedly across Turkey-based payment applications in the 2011-2012 period was exactly this: the SMS verification code expires in 60 seconds, no countdown is shown on screen, the user panics, the form reloads, and the amount can be submitted twice. This is not a technical failure; it is the inevitable consequence of a form designed without ever asking how the user models the experience in their head.Error messaging is the most neglected area in Turkish fintech projects — and it is worth saying so plainly. ‘An error occurred’ tells the user nothing. Is the account number wrong? Is the balance insufficient? Has the system timed out? That ambiguity generates one question in the user’s mind: ‘Did my money leave?’ While working with a payment infrastructure provider based in Ankara, a focused intervention that made error messages specific and actionable led to a 64% drop in ‘transaction status’ calls to the customer support line within nine weeks. This is a direct line from a copy decision to a cost outcome. The framing matters here: design decisions of this kind should be positioned not as aesthetic improvements but as revenue protection instruments.Ease of reversal is the recommendation that meets the most resistance in design reviews. ‘Won’t an ‘Cancel’ button push users away?’ I hear this often. The answer is no — but a flow that offers no exit forces the user either into a support call after an erroneous transaction or into abandoning the product altogether. Neither outcome is acceptable. Good design gives users a clear understanding of where they are at every step, and a genuine path back if they need one. This goes beyond adding a cancel button: step indicators, a ‘here is what you are about to do’ summary, and a pre-submission review screen are the structural elements that give users a sense of control. The thesis here is direct: user control is the architectural foundation of trust, not a courtesy feature.By 2012, Turkey’s mobile channel is growing fast, and that growth adds a new constraint to fintech UX work: the screen shrinks while transaction complexity stays the same. Short-distance EFT, bill payment, credit card installment restructuring — each of these involves dozens of fields and decision points even on a desktop browser. Under pressure to fit everything onto a mobile screen, designers hide fields and collapse steps. That can be a sound decision — but every hidden field is a potential blind spot for the user. The right question to ask before removing anything is: what does the user miss when this field disappears? If what they miss is relevant to transaction accuracy, the field should not be removed. Sacrificing transactional certainty for visual elegance creates a long-term cost in fintech that is difficult to reverse.Return to that Istanbul software company and the 53% uncertainty rate from the usability study — because the team’s response is the most instructive part of the story. They made a single change: after a successful transaction, the screen now displayed the reference number, the recipient’s name, the amount, and the sentence ‘Your EFT will be processed on the same business day.’ Same flow. Same button. Same palette. In the next round of testing, the uncertainty rate fell from 53% to 16%. Six weeks later, ‘did my transaction go through?’ calls to customer support dropped by more than two-thirds. The design change carried zero development cost. It was a question of text and information hierarchy. The question that belongs on every fintech manager’s agenda is this: in your product, can the user confirm — without calling anyone — that the transaction completed correctly? If the answer is ‘no’ or ‘I’m not sure,’ allocating part of your growth budget to this problem will return faster than almost any other investment you can make.
This article was originally published in Turkish by Gökhan MERCANOĞLU on January 24, 2012. The English edition has been reviewed and edited by the author.