By Mehdi HassanWhat disclosures does a fintech website need?
A fintech website needs disclosures that explain what the company is, who holds customer money, what the product costs, what risks or terms apply, and how customer data is handled. The exact set depends on your products, licences and markets, so counsel decides the list. Design's job is to plan a home for each one before the pages are drawn.
Most fintech compliance articles stop at "add SSL and a privacy policy." Our research found that gap across ranking guides: few cover placement, legibility or how to keep disclosures right in a CMS. This checklist is the design-side companion to our fintech website design hub. It isn't legal advice; it's what to prepare so legal review is fast and complete.
Disclosure type | Typically relevant for | Who writes it |
|---|---|---|
Company and regulatory status | Every fintech | Counsel |
Partner bank or custodian | Fintechs offering accounts or cards via a bank | Counsel, with the partner |
Deposit or investor protection | Accounts, investing products | Counsel |
Fees and rates | Any priced product | Product, finance and counsel |
Lending terms and APR | Loans, credit, buy now pay later | Counsel |
Investment risk and performance | Brokerage, advisory, crypto | Counsel and compliance officer |
Privacy and data use | Every fintech | Counsel and data protection lead |
Complaints and support routes | Most regulated products | Operations and counsel |
Where should fintech disclosures appear on the page?
Fintech disclosures should appear next to the claim or action they qualify, and again in a consistent footer. A disclosure only in the footer may be technically present but practically invisible at the moment a user decides. Use this placement checklist page by page.
- Sign-up and download buttons: a one-line status statement, such as who provides banking services, directly beneath.
- Rate and yield claims: conditions, variability and effective dates directly under the number.
- Fee claims like "free" or "no fees": the exceptions in the same view.
- Protection claims: what's protected, by whom and with what limits, beside the claim.
- Loan offers and payment examples: APR and terms next to any payment amount.
- Investment returns or testimonials: the required context and risk statement with the content.
- Forms collecting personal or financial data: a short data-use note and a privacy link above the submit button.
- Footer: full legal disclosures, licences and entity details, identical on every page.
Compare how live products handle this in our annotated fintech website examples, and see the fintech landing page framework for placing conditions under a hero calculator.
How legible do fintech disclaimers need to be?
Fintech disclaimers need to be readable by the people they're meant for, at the size and device they actually use. The FTC's guidance on clear and conspicuous disclosures, available at ftc.gov, is a useful principle for design: a disclosure should be hard to miss and easy to understand, not merely present.
- Contrast: disclosure text meets WCAG contrast for body text. Pale gray on white fails users and looks evasive.
- Size: smaller than body copy is fine; unreadable on a phone is not. Test on a real device.
- Proximity: the qualifier sits in the same visual block as the claim, not a scroll away.
- Real text: never inside an image, video frame or canvas, where screen readers and search can't reach it.
- No hover-only tooltips: they don't work on touch screens and are easy to miss.
- Plain language: short sentences, defined terms, no unexplained acronyms.
- Asterisks sparingly: a symbol that sends users to the bottom of a long page breaks the link between claim and condition.
Accessibility is a compliance area of its own. Our guides to website accessibility compliance and ADA website compliance cover the wider requirements.
How should partner bank and deposit insurance language be handled?
Partner bank and deposit insurance language should be written by counsel with the partner bank, and design should present it exactly as approved, everywhere it's needed. The design risk is implying protection or a banking status that doesn't apply, through a badge, a logo or a headline that overstates what the fine print says.
If you operate in crypto, the rules and risk warnings differ again; see our guide to crypto website compliance.
How do you manage fintech website compliance in a CMS?
You manage disclosures in a CMS by storing each one once, as a locked, reusable component, and inserting it wherever it applies. When counsel changes the wording, it updates everywhere at once. This prevents the most common failure: an old rate or partner name left on a campaign page nobody remembered to check.
Create a disclosures collection
Each entry holds the approved text, its type, the products it applies to, the approver and the last review date.
Lock editing
Marketers can place disclosure components on pages but can't edit the text. Only named owners can change it.
Pair claims with qualifiers
Build rate, fee and protection claims as components that require a linked disclosure before publishing.
Add a review step
Pages containing financial claims go through a legal approval state before they can be published.
Schedule reviews
Set a reminder on each disclosure's review date and keep a change log with dates and approvers.
Archive old versions
Keep previous versions of disclosures and key pages, with dates, in case you need to show what was live.
Trust pages for security and compliance follow the same governance. Our guide to B2B website trust pages covers security, status and compliance pages in detail.
What should you hand to counsel for review?
Hand counsel a claims inventory, not just a link to staging. A spreadsheet listing every financial claim, the page it's on, a screenshot and the disclosure paired with it turns a vague review into a focused one, and makes it far less likely something slips through.
- Claims inventory: every rate, fee, protection, return or comparison claim, by page.
- Screenshots on desktop and mobile showing the claim and its qualifier together.
- The disclosures collection with current wording and where each is used.
- Forms and consents: every field collected and what the user is told about it.
- Proof sources: written permission for customer logos, reviews and testimonials.
Hypothetical example: a claims inventory for a savings app
For example, suppose a savings app's site has a homepage, a savings product page, a pricing page and a sign-up page.
The inventory lists seven claims: a headline rate on the homepage, the same rate on the product page, "no monthly fees" on pricing, a protection statement on the product page, a comparison to traditional savings accounts, a customer quote and the sign-up status line. Each row has the page, a mobile screenshot, the linked disclosure component and a column for counsel's decision. Counsel rejects the comparison claim and asks for a date on the rate. Because both live as components, the fix is two edits, not a hunt across pages.
Once compliance is planned, check that the sitemap includes every trust page using our list of must-have fintech website pages. Legal review rounds are also a real cost driver, which our fintech website cost guide covers.
