Fintech is trust, not features
Every fintech I have shipped against has a feature lead. Almost none has a trust lead.
The pattern across four years
Every fintech I have shipped against has a feature lead. Almost none has a trust lead.
In four years on financial products I have watched Revolut close the gap on every European bank by being faster on the surface and slightly less right on the backend. I have watched N26 open one back up by mishandling a wave of fraud complaints. Wise grew because they were boring on purpose. Three startups I know by name died because they shipped a beautiful card and a confused refund policy.
Where trust actually lives
Trust is built in pending states, in errors, in refunds, in the small moment when something the bank did goes wrong and the user finds out before the bank does.
Most fintech product specs cover none of this. The Figma file has 60 happy-path screens and one rejection modal that says 'Something went wrong.' The actual rejection modal is the product.
The pending state hour
At Factorial I once spent a full design hour rewriting the copy on the pending state for a card top-up. The whole screen was a spinner and one line of text.
The original copy said 'Processing your top-up.' The new copy said 'Your top-up will appear in the account within 30 seconds. If it has not, refresh the page. If it still has not, your money is safe. It is in transit at our card issuer and will land within the next two business days.'
Engineering pushed back because the copy was twice as long. Support stopped getting a category of ticket. We never measured it formally. The team knew.
The receipt that did the work
The most valuable single screen I designed on cards was the post-transaction receipt. It is 200 pixels tall. It loads less than half a second after the card is swiped. It says four things, no more: the merchant name, the euro amount, the category the spend was auto-classified into, and a tiny edit affordance for when the category is wrong.
That receipt did more for trust in the product than any feature on the roadmap that year. Every transaction was a chance for the product to be wrong about something, and the receipt was the apology mechanism the product needed before it could ever be wrong.
Feature lists vs product
Feature lists are sales decks. They live in pitch meetings and pricing pages.
Trust is what is left over after the feature has been used a hundred times in the wild. It is what the user assumes when the card goes through. It is the absence of doubt at the moment of payment. You cannot ship it directly. You can only ship the surfaces that produce it.