Financial experience design: trust before beauty

The finance and service industries have a characteristic that many business owners overlook when starting to build a digital brand: users do not make decisions based on a pretty page. They make decisions because they trust. And trust in this field is built through specific actions, not through colors or fonts.

Why trust is foundational, not just a bonus

Nielsen Norman Group describes a concept called the "trust pyramid": customers must see that the page meets their reliability needs at the base level before they are willing to provide sensitive information or financial commitments. This means that flashy designs lacking basic trust signals not only do not help but may also raise doubts.

Four basic reliability signals that Sinh Vũ checks first in every financial and service project:

• Clear and easily accessible legal entity and contact information.
• Privacy policies and terms should be written in language that is easily understood.
• All fees, profits, and conditions are disclosed before the client commits.
• Handle errors and sensitive statuses (failed transactions, incorrect information) with calm language and clear guidance.

Accessibility is not optional.

WCAG 2.2 (Web Content Accessibility Guidelines, the official W3C standard as of October 2023) is organized around four principles: perceivable, operable, understandable, and robust. For finance and services, this is almost a mandatory requirement for two reasons.

The first reason is legal: many markets have already implemented or are in the process of implementing WCAG as mandatory regulations for financial organizations. The second reason is commercial: older users, users with poor vision, and users with basic mobile phones make up a significant portion of financial customers in Vietnam. If your registration or payment flow cannot be operated by keyboard or lacks color contrast, you are excluding part of your customers right from the start.

Three minimum points that Sinh Vũ always checks:

• The color contrast between text and background meets the WCAG 2.2 threshold (no specific numbers are determined if not measured in practice).
• All forms and navigation flows are keyboard-driven, independent of mouse or touch.
• The label is form and error notification readable by screen reader software.

Clear language is design, not supplementary content.

Financial terminology is the biggest barrier preventing clients from understanding what they are agreeing to. When clients do not understand, they do not agree. Or worse, they agree without understanding and later complain.

Sinh Vũ approaches financial content with the principle: write for first-time readers, not for those who already understand. This means that each technical term must be accompanied by a brief explanation upon first appearance, each important condition must be separated into standalone sentences, and buttons must clearly state what happens when clicked, avoiding vague labels like "Next" or "Confirm."

The role boundary: what Sinh Vũ does and who must handle the rest.

Sinh Vũ builds content strategy, experience flow, and interface. This is the part Sinh Vũ ensures is solid. However, in financial projects, there are aspects that must be handled by others, and you need to be aware of this before starting.

• Core transactions, user authentication, fraud prevention, and system security: handled by the technical team or a specialized financial software house.
• Meeting specific legal frameworks (regulations from the State Bank, Ministry of Finance, or any regulatory body): decided by your compliance department. Sinh Vũ references, does not commit to replacing.

The reason Sinh Vũ states this clearly is not to evade responsibility, but because ignoring this boundary is the most common reason financial projects have to be completely redone after launch, when the compliance department discovers non-compliance issues.

Transparent disclosure from the start is one of the four core factors that create a sense of trust on the page. This is not a design option but a condition for customers to continue.

Nielsen Norman Group, Trustworthy Design: 4 Credibility Factors

Common mistakes that cause flow collapse

• Hide fees and conditions until the final step of the flow, when customers have invested time and find it hard to go back.
• Use financial terms that are not explained, leaving the customer unaware of what they are agreeing to.
• Long forms with vague error messages do not specify which fields are incorrect and how to correct them.
• A flashy design but lacking easily accessible legal entity information, contact details, and privacy policies.
• Ignoring compliance until the product is nearly launched leads to redesigning processes due to legal issues.