From Disclosure to Product Control: Preparing Digital Banking for the April 2027 FDIC Sign Rule
The April 1, 2027 compliance date gives banks and their technology partners time to do more than place a logo. The revised rule calls for a controlled inventory of customer journeys, clear separation of deposit and non-deposit messages, responsive and accessible presentation, and evidence that survives frequent product releases.
Why this is a product-governance project
The 2026 final rule published in the Federal Register amends digital and ATM signage requirements for FDIC-insured depository institutions and sets April 1, 2027 as the compliance date. It narrows several display obligations and adds design flexibility, but the operational challenge remains broad: banks must know where customers encounter insured deposits, non-deposit products and transitions to third-party platforms.
A static legal review will not keep pace with modern digital estates. Websites use content-management systems, mobile apps release frequently, authenticated journeys vary by customer, and ATM software may be managed across several fleets. Wealth, insurance and investment experiences may sit inside the same navigation or open on an affiliate’s platform. A rule expressed in pages and screens therefore needs to become reusable product controls.
The useful management question is not “Where should the sign go?” It is “How will the institution continually identify a covered experience, select the right disclosure, render it clearly, test it across devices and prove that it remained present after change?” That framing brings compliance, product, design, engineering, accessibility, marketing, ATM operations and vendor management into one delivery model.
Translate Part 328 into a journey map
The current eCFR text for 12 CFR Part 328 requires the official digital sign to be displayed clearly, continuously and conspicuously on three locations in a digital deposit-taking channel: the initial page or homepage of the website or application, the login page, and the page or screen where a consumer first initiates deposit-account opening.
That list should become tagged inventory, not a one-time screenshot collection. For every web domain, app, authenticated shell, account-opening flow and branded variant, record the accountable business, technical owner, release pipeline, deposit capability, non-deposit content, external links and required sign state. Include deep links, campaign landing paths, guest access and alternate authentication routes. Customers do not always enter through the homepage.
The inventory should also distinguish a “page or screen” from reusable components. A login component may appear in a browser, native app and embedded webview. A deposit-opening flow may be supplied by a core vendor but branded and configured by the bank. Mapping the component lineage makes testing scalable: one change can affect many covered surfaces, and one assurance result can sometimes support several journeys when configurations are demonstrably identical.
Separate the official sign from non-deposit signage
The final rule focuses the official digital sign on the homepage, login and first deposit-account-opening screen. It also applies non-deposit signage to pages primarily dedicated to advertising, providing information about or giving access to non-deposit products. The required message must indicate that those products are not FDIC-insured, are not deposits and may lose value.
These are different messages with different triggers. The official digital sign tells customers they are dealing with an insured institution in a relevant deposit context. Non-deposit signage distinguishes products such as investments or insurance. A content design system should therefore define separate components, approved wording, placement logic and usage rules. Treating both as generic footer disclosure invites the wrong component to appear in the wrong context.
The “primarily dedicated” standard also needs a repeatable classification method. Teams can assess page purpose, headline, calls to action, proportion of content and the transaction or information the user is seeking. A navigation reference to wealth management on a general homepage is not the same as a page built to explain or access investments. Documenting those factors turns subjective debate into reviewable evidence.
Use design flexibility with disciplined tokens
The 2026 amendments permit the official digital sign text in navy blue or black without prescribing exact hexadecimal codes, and allow Source Sans Pro Web or a similar font. The rule’s discussion recognises constraints such as space, font availability and color options. Flexibility is valuable, but unmanaged local interpretation can produce dozens of inconsistent versions.
Banks should publish a design token rather than distribute an image alone. The token can specify approved text, colors, font fallback, size bands, wrapping behaviour, clear space, background treatment, accessibility label and prohibited transformations. Each channel can implement the token natively while preserving the intended meaning. Versioning the token also lets teams identify which releases use an outdated rule interpretation.
Responsive behaviour is critical. The sign should remain legible when a mobile keyboard opens, browser zoom increases, localization expands navigation, accessibility settings enlarge text or a small ATM screen changes layout. Hard-coded height, overflow hiding and image scaling can make a technically present disclosure unreadable. Product acceptance criteria should test the rendered experience, not only whether a code element exists.
Make accessibility part of conspicuousness
The rule requires signage to be clear and conspicuous in relation to surrounding content. Accessibility standards add a useful engineering baseline. WCAG 2.2 sets a 4.5:1 minimum contrast ratio for ordinary text, permits 3:1 for large text, requires text to resize to 200% without loss of content or functionality, and addresses non-text contrast and keyboard operation.
For narrow screens and enlarged content, the W3C’s reflow guidance explains that content should fit a 320 CSS-pixel-wide viewport without two-dimensional scrolling for ordinary reading. A bank sign or non-deposit message that clips, overlaps another control or disappears behind a sticky header undermines both accessibility and the regulatory objective, even if it looked correct in the original desktop mock-up.
The test matrix should cover supported browsers, device sizes, landscape and portrait orientation, zoom, large text, high-contrast modes, screen-reader reading order, keyboard navigation and multiple languages. The sign’s text should be exposed as meaningful text where feasible rather than an unlabeled image. Automated scans can detect some defects; visual and assistive-technology testing remains necessary for placement and comprehension.
Control the handoff to third-party non-deposit products
Part 328 also addresses a logged-in customer moving from the bank’s digital deposit-taking channel to a third-party platform offering non-deposit products. The Federal Register rule permits a one-time notification to be dismissed by customer action or to disappear automatically after at least three seconds. The rule discussion makes clear that affiliates can count as third parties for this purpose.
This handoff is a service boundary and should be managed as such. The bank needs an inventory of outbound links, destination owner, product type, session state and notification trigger. Link-management systems should not bypass the notice when URLs change. Single sign-on and embedded experiences can obscure whether the customer has technically left the bank channel, so legal classification and user-experience design must be reviewed together.
A three-second timer should not become the design objective. The customer needs a reasonable opportunity to understand the message, and manual dismissal may be clearer for high-impact journeys. Analytics can reveal whether the notification fails to render, loops repeatedly or creates abandonment, but teams should avoid optimizing it into invisibility. The goal is informed transition, supported by durable event logs.
Bring ATMs and like devices into the same control model
The rule narrows digital-sign and non-deposit-sign requirements for ATMs and like devices to the initial screen and initial non-deposit transaction screen, respectively. It also permits specified machines to use a physical official sign instead of the digital sign, subject to conditions in 12 CFR Part 328. This creates configuration choices that must be tied to the actual capability and service date of each device.
An ATM estate register should include model, owner, location, software version, deploy date, deposit capability, non-deposit capability, sign method and last validation. Acquired fleets, teller-assist machines, kiosks and shared networks deserve explicit review. A generic certification from a vendor may not establish that every institution-specific configuration presents the right initial screen.
Testing should cover idle screens, language selection, card and contactless entry, unauthenticated journeys, accessibility modes, promotional content and the first non-deposit transaction screen. Physical signs need inspection and replacement processes. Digital signs need release controls and remote evidence. Both belong in the same compliance dashboard so that channel choice does not create an assurance gap.
Build release evidence, not a screenshot archive
Screenshots are useful but fragile. They rarely prove the URL, build version, customer state, device viewport, timestamp or code path that produced the image. A stronger evidence package links a requirement identifier to the classified journey, design component, test case, build, execution result, exception and approval. Automated visual checks can confirm presence and location, while manual review assesses clarity relative to surrounding content.
The official GovInfo version of the rule states that institutions already aligned with earlier requirements are not automatically grandfathered, although many existing implementations may comply. In particular, the amended rule expressly requires the sign on the first deposit-account-opening page. Banks should therefore re-test previously completed work against the final 2026 text rather than rely on earlier programme closure.
Evidence should be refreshed by change. When a shared header, login framework, account-opening vendor, navigation model or ATM software changes, the release workflow should identify affected requirements and trigger appropriate tests. Compliance teams can then sample a living control rather than re-perform an estate-wide survey before every examination.
A 2026–2027 delivery sequence
During the first phase, appoint a single programme owner and establish the authoritative interpretation set. Build the journey and device inventories, identify third-party and affiliate handoffs, and reconcile every surface to a product owner and release mechanism. Resolve unknown ownership before design work accelerates.
Next, create the approved digital-sign, non-deposit-sign and transition-notification components. Encode responsive and accessibility behaviour, integrate them into shared design systems and define approved exceptions. Pilot across one public website, one native app, one deposit-opening flow and representative ATM configurations to expose channel differences early.
Then scale implementation through normal release trains. Use component-level tests for speed, but retain journey-level validation for context. Add monitoring for missing components, broken outbound-link notices and configuration drift. Train marketing, product managers and vendors on classification triggers so new pages do not bypass review.
Before April 2027, complete an independent readiness review using production-like customer states and supported devices. Close high-risk exceptions, document temporary controls and set post-launch monitoring. The durable outcome is a disclosure-control system that survives redesigns, acquisitions and vendor upgrades, not a collection of compliant screens frozen in time.
Frequently asked questions
When is compliance with the revised FDIC digital sign rule required?
The 2026 final rule is effective March 2, 2026 and requires compliance by April 1, 2027. Institutions should use the final rule and current eCFR text as the baseline, because the earlier January 2027 date was superseded.
Where must the official digital sign appear?
Current Part 328 specifies the initial page or homepage of the website or application, the login page, and the first page or screen where a consumer initiates deposit-account opening. The display must be clear, continuous and conspicuous.
Which digital pages need non-deposit signage?
The rule applies the message to pages primarily dedicated to advertising, providing information about or giving access to non-deposit products. The message must indicate that the products are not FDIC-insured, are not deposits and may lose value.
Can the official digital sign wrap on small screens?
The revised rule provides font and color flexibility intended to accommodate technical constraints. Banks should define approved wrapping and responsive behaviour, then test legibility, contrast, zoom, text enlargement and reflow rather than improvising per page.
What evidence should a bank retain?
Useful evidence links each requirement to the covered journey or ATM, responsible owner, approved component, build or configuration, test conditions, visual result, defects, approvals and change history. Screenshots are stronger when accompanied by reproducible context and release identifiers.
References
• FDIC Official Signs final rule, 91 FR 3801 — Federal Register
• 12 CFR Part 328 — Electronic Code of Federal Regulations
• Official PDF of the 2026 final rule — GovInfo
• Web Content Accessibility Guidelines (WCAG) 2.2 — W3C
• Understanding WCAG 2.2 Reflow — W3C Web Accessibility Initiative