A mobile screen must still communicate the legal information
Creditors delivering pre-contract information through a mobile application face the same starting question as other channels: what must be supplied under the applicable legal regime before the consumer is bound? Directive 2008/48/EC Article 5 and national implementing law remain relevant for covered agreements; CCD2 Article 10 modernises the requirements, generally applicable through national measures from 20 November 2026. Small screen dimensions do not create a general exemption. An app can be a channel for displaying information but must also meet any paper or durable-medium requirement. Product designers should map the binding acceptance moment and required documents before deciding how disclosures fit into a screen sequence.
Prioritise readability without rewriting legal fields
Large headlines, icons and compact summaries can help consumers navigate a complex application. They should not replace mandatory fields or change legally defined amounts. A card showing an estimated monthly payment needs to remain consistent with the full repayment schedule, APR, fees and contractual terms. Check font scaling, colour contrast, zoom, orientation and localisation. A disclosure that disappears behind an overlay or off-screen carousel may not be meaningfully available. The requirements concern the actual consumer-facing experience, not screenshots from a design prototype. If the app contains separate tabs for cost, rights and agreement details, ensure required items are available at the legally appropriate time.
Durable media and offline access need special attention
A scrollable app view may be editable by the provider and difficult to reproduce unchanged later. Where the applicable law requires information on a durable medium, assess whether the app creates a qualifying retained document or secure message. Consider what happens when a user changes phone, logs out, loses network coverage or closes the app. A disclosure stored exclusively in temporary device memory should not be presumed to meet the legal test. If a PDF is offered, verify the user can open and save it with standard accessibility features. Technical logging should establish the issued version while avoiding unnecessary retention of sensitive personal information.
Control gestures, timing and consent patterns
Swipe flows, progressive disclosure and one-tap acceptance can create timing issues. Do not allow an acceptance button to appear before required disclosures have been presented in the legally necessary manner. Test whether a consumer can return to cost and withdrawal information without losing entered application data. A mandatory checkbox or swipe animation is not itself proof that an adequate explanation was provided. CCD2 Article 10's rules on timely pre-contract information and the post-contract reminder in specified cases require a separate implementation review. Designers should also identify where notification permissions, electronic marketing consent and credit contract acceptance are presented, rather than combining unrelated permissions in one ambiguous control.
Synchronise the app with the actual credit offer
Credit offers may be recalculated by an API while the user moves between screens. The displayed borrowing rate, APR, fees, term and repayment amount must agree with the legal information supplied for the offer being accepted. A change to loan duration can affect several fields simultaneously. Record the offer identifier used to create the disclosure and prevent the app from presenting a stale file after terms change. Review differences across operating systems, supported devices and low-bandwidth situations. Customer-support links may supplement a disclosure, but a help article describing a generic product cannot necessarily replace personalised pre-contract information.
Test real journeys and maintain change records
A useful test plan covers new applications, returning users, language switches, enlarged text, interrupted checkout, offline transitions and version upgrades. Inspect whether required documents remain accessible after completion. Preserve approved template versions, release history, disclosure generation events and evidence of defects corrected. The exact legal recordkeeping duty must be confirmed by jurisdiction, so an internal event log should not be described as a universal CCD2-prescribed record. Reassess after app redesigns, changes in document delivery, accessibility complaints, court decisions about durable media or Member State CCD2 implementing measures. Technical testing and legal interpretation should inform each other without confusing optional interface choices with statutory requirements. Testing should also assess notifications sent when an offer changes. An app may display a new payment amount on its main screen while leaving the old legal information attached to a previous offer. Ensure that consumers see the applicable disclosure before accepting the modified terms. Device security features and privacy settings can block document previews or notifications, so the application needs a robust access route rather than assuming a push message was delivered. Maintain a clear separation between design preferences and mandatory disclosure content. Evidence should connect the version accepted to the document actually made available at that moment.
Frequently asked questions
Are mobile-app disclosures exempt from the usual rules?
No. A small screen does not create a general exemption from pre-contract information duties.
Does a scrollable app page always qualify as a durable medium?
No. The legal functional characteristics of the medium must be evaluated.
When do CCD2 national measures apply?
Generally from 20 November 2026, while existing domestic requirements continue to matter beforehand.
Primary sources
Directive 2008/48/EC ↗Directive (EU) 2023/2225 ↗Read the source in its current version. National implementing measures and product-specific applicability may require additional research.