What the trust signals in a fintech product actually are

Why doesn’t a padlock icon earn trust any more?

Because the browser that made it familiar took it away.

Google studied 1,880 users on what the address-bar padlock actually communicated and found that 89% misunderstood it. In Chrome 117, released in September 2023, the padlock was replaced with a neutral icon that opens site settings; on iOS it disappeared altogether. The motif that a generation of landing pages borrowed as shorthand for safety was deleted by the company whose browser popularised it, on the grounds that almost nobody read it correctly.

That is the decorative-trust problem in a single artefact. What actually earns trust when money is attached is a different, much less decorative set of decisions — most of which show up nowhere near the homepage.

Which trust signals actually do the work?

Numbers that show their work. A fee stated as “2%” is not the same claim as a fee stated as “2% of the transferred amount, capped at ₹200, charged after the transfer clears.” The first reads as a marketing number. The second reads as something a real person checked before publishing it. Products that state fees, timings and limits in full, in the flow itself rather than behind a “see terms” link, are making a trust decision every time — and users who deal with money professionally notice immediately.

A product that looks like its own marketing site. The gap between a polished landing page and a rough in-app screen is one of the fastest ways to lose confidence, and it is rarely intentional — usually two teams working from two budgets. To a user that gap does not read as “the marketing team tries harder.” It reads as “what else did they cut corners on.”

Honest error and edge-case states. Almost every fintech product looks trustworthy on the happy path. The real test is a failed transaction, a rejected KYC document, or a payment sitting pending longer than expected. A vague “something went wrong” with no next step reads as a product hiding something. A specific explanation — what happened, what happens next, how long it usually takes — reads as a product that has thought about this moment, because somebody had to write that copy on purpose.

Support that is visible before it is needed. A number buried three menus deep, surfacing only once something has already gone wrong, tells a different story than one visible from the first screen. It does not need to be prominent. It needs to be findable in ten seconds by someone who is currently anxious, not someone calmly browsing a help centre.

Data handling made visible, not merely compliant. Someone who uploads a bank statement or a photo ID rarely knows what happens to it next, and most products never say — even when the handling behind the scenes is genuinely careful. Showing that a document arrived, what it is being checked for, and roughly how long that takes turns an invisible, anxiety-inducing process into something the user can watch happen. Compliance that is not visible does no work for trust at all.

What does Indian regulation already require you to show?

More than most product teams realise, and it lands squarely on the first signal above.

The Reserve Bank of India’s Key Facts Statement circular of 15 April 2024 applies to all new retail and MSME loans sanctioned from 1 October 2024. It requires lenders to give every borrower a standardised statement of the loan’s key facts in plain language — including an all-inclusive Annual Percentage Rate, a computation sheet showing how that APR was arrived at, and the amortisation schedule across the loan tenor. It also closes the obvious loophole: fees not disclosed in the Key Facts Statement cannot be charged at any stage without the borrower’s explicit consent.

Read that as a design brief rather than a compliance chore and it says something useful. The regulator has decided that a number without its working shown is not a disclosure at all. That is the same judgement a careful designer makes, arrived at independently — and for a large part of Indian fintech it is now the floor, not the aspiration.

This describes the requirement in general terms and is not legal or regulatory advice. Confirm your own position with counsel or your compliance team.

When do trust badges backfire?

A financially sophisticated audience — and most fintech users are, whether or not they would describe themselves that way — has seen the padlock-and-carousel pattern many times before. It is not neutral. A page that leans hard on generic trust badges without backing them up in the product can read as compensating for something, the way an oversized “as seen on” banner sometimes does.

The badges are not the problem. Using them as a substitute for the underlying decisions is.

What does this mean for a product team?

Trust, in a fintech product, is a design system property, not a marketing addition. It has to be specified the way spacing and colour are specified — in the error states, the empty states, the pending states and the confirmation flows, not only the homepage hero. A design system that covers only the happy path has covered maybe half the moments that decide whether someone trusts the product with their money.

That is the review we actually run: not “does the homepage look credible,” but “does every state of this product — including the ones nobody designed on purpose — say the same thing about who is behind it.” The same question, asked of a storefront rather than a wallet, is why D2C storefronts lose money at three specific moments.

FAQ

What are the trust signals in a fintech app?

Fees, timings and limits stated in full inside the flow; visual consistency between the marketing site and the product itself; error and pending states that explain what happened and what happens next; support that is findable before anything goes wrong; and visible confirmation of what happens to documents a user uploads. Badges and padlock icons are not trust signals.

Do security badges and regulator logos help?

Only where the product behind them behaves consistently with the claim. On their own they are close to neutral, and with a sophisticated audience they can read as compensating for something. A badge is a summary of trust already earned, not a way of earning it.

Where should a fintech redesign start?

With the screens nobody designed on purpose. The homepage has usually had a budget and several rounds of feedback; the failure states, the pending states and the account recovery flow usually got one message and whatever the framework’s default error component looks like. That is where the gap between how a product looks and how it feels is widest.