Financial experience design: trust before beauty
Users do not pay for a site that is just beautiful but unclear, and this is the order of priorities you need to understand before starting the design.
In finance and services, the top priority is trust and transparency. You need to disclose all fees, conditions, and privacy policies early before asking customers to commit to anything. Next is accessibility according to WCAG 2.2 standards, as users are diverse and many financial operations must be usable by everyone. Aesthetics and advanced features come after these two foundations.
- the product involves money and sensitive data; trust and transparency in fees are the top priority
- Services for a broad audience, accessibility according to WCAG 2.2 should be considered a baseline requirement.
- any flow requiring client agreement on terms needs to be clarified before commitment
- Hide fees and conditions until the final step.
- overlooked the compliance department, resulting in a redo due to legal issues
The finance and services sector has a particularity that many business owners overlook when starting to build a digital brand: users do not make decisions based on how beautiful the page is. They make decisions based on trust. And trust in this field is built through specific actions, not through colors or fonts.
Why trust is foundational, not just a bonus
The Nielsen Norman Group describes a concept called the "trust pyramid." According to this, customers must see that the page meets their trust needs at the base level before they are willing to provide sensitive information or make financial commitments. This means that flashy design lacking basic trust signals not only fails to help but also raises suspicion.
Four basic trust signals to check first in any finance 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 since October 2023) is organized around four principles. These four principles are: perceivable, operable, understandable, and robust. In finance and services, this should be considered a foundational requirement for two reasons.
The first reason is legal: many markets have either implemented or are in the process of implementing accessibility standards into regulations for financial organizations, and you should consult your compliance department or lawyer about the requirements applicable to you. The second reason is commercial. Older users, users with poor eyesight, and users with only basic mobile phones make up a significant proportion of financial customers in Vietnam. If your registration or payment flow cannot be operated by keyboard or lacks color contrast, you are excluding a portion of customers right from the start.
Three minimum points to check:
- 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.
The principle for financial content is to write for first-time readers, not for those who already understand. Each technical term that appears for the first time must be accompanied by a brief explanation. Each important condition must be separated into a standalone sentence. Buttons must clearly state what happens when clicked, avoiding vague labels like "Next" or "Confirm."
Products involving money and sensitive data (loans, investments, insurance, payments): trust and transparency of fees are the top priority, while accessibility is the second priority. Design and aesthetics come after these two foundations.
Role boundaries: what designers do and who must do the rest
A design studio builds content strategy, user experience flow, and interface. However, in financial projects, there are parts that must be handled by others, and you need to be clear about 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 agency): this is decided by your compliance department. Design only references, it does not commit to replacing it.
Stating this boundary is not to deny responsibility. Overlooking it is the most common reason financial projects need to be completely redone after launch when the compliance department discovers flows that do not meet regulations.
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.
According to Nielsen Norman Group, Trustworthy Design
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.
Decision checklist
Topic: Digital experience for finance and services. Sinh Vũ guide, sinhvu.com
Tick each item that applies or that you can already answer, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
This article provides general information according to the documents in effect as of October 6, 2026. This is not legal advice and does not substitute for a lawyer's opinion for your specific case. Rights and obligations between Sinh Vũ and clients arise only according to the signed contract.
References
W3C, Web Content Accessibility Guidelines (WCAG) 2.2, October 2023. Nielsen Norman Group, Trustworthy Design: 4 Credibility Factors. Practical experience from Sinh Vũ.
Frequently asked questions
Does the consulting service introduction page (accounting, legal) need to comply with WCAG 2.2, or is it only banking apps that require this?
Any page serving a broad audience should comply with WCAG 2.2, not just banking apps. For advisory pages, the minimum requirements are sufficient color contrast, keyboard navigability, and a scheduling form that works on screen reader devices. Besides any applicable legal requirements (you should consult your compliance department), this also directly impacts conversion rates.
Where should fees and conditions be disclosed in the workflow, and is it mandatory to display them immediately on the homepage?
It is not mandatory to display everything on the homepage. However, it should be sufficient before the customer commits, meaning before they click agree, fill in personal information, or confirm a transaction. The principle is: customers must understand what they are agreeing to before they actually agree. Hiding fees and conditions until the last step is the most common mistake and breaks trust the fastest. With many financial products, consumer protection regulations and industry regulations also require providing information before concluding, so your compliance department is the one to confirm specific requirements.
Can a design studio handle the entire transaction flow of a financial app?
The design studio can develop content strategy, user experience flow, and interface. The core transaction part, user verification, fraud prevention, and system security must be handled by the technical team or a financial industry software house. Additionally, all experience decisions in this field need to be aligned with your compliance department, as no studio can meet a specific legal framework on behalf of the business.
This article is for reference. The scope, pricing, and specific commitments of Sinh Vũ are detailed in the proposal and signed contract.