Release Notes
Platform guide
This page highlights changes released in May 2025.
For earlier release notes, see Recent months.
Mobile SDK
Accessibility improvements: We continuously improve the accessibility of our iOS, Android, and cross-platform plugin SDKs to comply with EAA requirements, aligning with WCAG 2.1 Level A and AA criteria.
These improvements are designed to support users with vision, dexterity, or mobility challenge, such as improved keyboard access and larger tappable areas, and include:
- We updated input fields to restrict unnecessary characters. This enhancement helps prevent user errors and improves overall usability and accessibility.
- We improved screen reader support for alerts. We made error messages, info banners, and NFC instructions accessible to screen readers. This gives users with vision impairments better context and improves overall usability.
- We added support for dynamic font sizing on iOS and Android. To meet WCAG 1.4.4 (Resize Text), we now support text scaling up to 200% without loss of content or functionality in scrollable containers.
- We improved the Document NFC scanning flow for better accessibility. The updated flow makes the experience easier to follow and gives users more control. It also supports keyboard navigation, meeting WCAG 2.2.2 (Level A/AA).

Document NFC on Android
Web SDK
Accessibility improvements: We continuously improve the accessibility of our Web SDKs to comply with EAA requirements, aligning with WCAG 2.1 Level A and AA criteria.
These improvements are designed to support users with vision, dexterity, or mobility challenge, such as improved keyboard access and larger tappable areas, and include:
- We set the accessibility language for our SDK pages. We updated our SDK to define the page language, helping browsers and assistive technologies, such as screen readers, understand and pronounce content correctly. This improves accessibility, especially for users relying on screen readers or translation tools.
- We added semantic HTML for better accessibility. We now use semantic HTML for headings, labels, and text to improve structure and meaning for assistive technologies. This enhances navigation and comprehension, in line with WCAG guidelines.
- We added support for dynamic font sizing. To meet WCAG 1.4.4 (Resize Text), we now support text scaling up to 200% without loss of content or functionality in scrollable container.
- We added support for adjustable text spacing. Users can now modify paragraph spacing to improve readability, meeting WCAG 2.1 Level AA, criterion 1.4.12.
- We improved dialog accessibility and input validation. Dialogs now use semantic HTML with proper roles, headings, and announcement order for better screen reader support. We also prevent unwanted characters in input fields to reduce typing errors. These changes support WCAG 2.1 criteria 1.3.1, 2.4.3, 4.1.2, and 3.3.1 - 3.3.4.
- We increased the tappable area for checkboxes. Checkboxes now have a minimum tappable area of 24px, making them easier to select, especially for users on touch devices or with limited dexterity.

Dynamic font size on Android
Recent months
April 2025
April 2025
Mobile SDK
Accessibility improvements: We continuously improve the accessibility of our Android and cross-platform plugin SDKs to comply with EAA requirements, aligning with WCAG 2.1 Level A and AA criteria.
These recent updates enhance usability for users with vision impairments and include:
- We updated all links to include underlines, ensuring color isn’t the only way information or actions are conveyed.
- We added underlines to link buttons to ensure they’re easily identifiable, even without color cues.
- We raised the background opacity from 50% to 90% to improve visual clarity and focus during document capture.
- We updated our default styles to increase text and UI contrast, making content easier to read and more accessible.
- We updated the default Orca color scheme to increase contrast and improve visibility.

Mobile accessibility improvements

Mobile accessibility improvements
Improved TIN extraction: We streamlined TIN extraction from Italian ID documents, improving accuracy and efficiency while reducing manual input.
Web SDK
Accessibility improvements: We continuously improve the accessibility of our Web SDKs to comply with EAA requirements, aligning with WCAG 2.1 Level A and AA criteria.
These recent updates enhance usability for users with vision impairments and include:
- We updated all links to include underlines, ensuring color isn’t the only way information or actions are conveyed.
- We raised the background opacity from 50% to 90% to improve visual clarity and focus during document capture.
- We updated our default styles to increase text and UI contrast, making content easier to read and more accessible.
- We made the shutter and close scanner buttons fully accessible via keyboard and screen readers. This update supports users who rely on assistive technologies like screen readers or have limited motor function, improving overall accessibility of our SDKs.
Improved TIN extraction: We streamlined TIN extraction from Italian ID documents, improving accuracy and efficiency while reducing manual input.
March 2025
March 2025
Web SDK
Improved document upload: We’ve enhanced the document upload experience in our Documents flows by reducing upload times.
This improvement shortens user journeys and decreases waiting times, resulting in a smoother overall onboarding experience.
Document NFC
Enhanced NFC flow: We’ve optimized the Document NFC flow for Spanish identity documents by leveraging data directly from the NFC chip when a scan is performed. As a result:
- The place of birth step is automatically skipped
- Tilted document images are automatically removed
- The overall flow is shorter and more efficient
These enhancements improve completion rates for Spanish flows.
Bank Account Verification
Migration to Tink: We’re transitioning from Klarna to Tink as our PSP to deliver improved performance, broader coverage, and a smoother payment experience.
The migration is fully handled by Fourthline — no action is required on your end.
The Fourthline Docs have been updated to reflect this change.
Mobile SDK
CameraX integration on Android (Beta): We are migrating our Android experience to the new CameraX library.
Expected benefits include:
- Higher-quality image and video capture
- Improved performance and smoother flows across our Documents and Biometrics solutions
June 2024
App Drop-in & Web SDK
Improved
Fourthline is dedicated to data-oriented decision-making, so we implemented a new analytics tracking tool: Snowplow SDK, v6.0.3.
We have also renewed our entire data pipeline.
Stay tuned!
Added
We added videos to illustrate the user experience of our solutions and modules via the App Drop-in and Web SDK.
App Drop-in
Improved
Qualified Electronic Signature
If the client leaves the signature flow, they can now re-enter the flow at the same place, instead of having to start a new flow.
Physical Proof of Address
The copy in this module now provides better guidance and improves the user experience.
Fixed
In the Android SDK, we fixed a navigation crash when initializing the drop-in, after building with AGP 8.4.x.
Web SDK
Improved
We released improvements to selfie capturing, which has increased selfie conversion by almost 7% for Android and low-end devices!!
AML Screening & Monitoring
Improved
We have improved our webhook notifications:
- You can update your configuration to be notified when a screening requires investigation: Status
manualReviewRequired
(This was already the case for AML Monitoring.) - Notifications now include hits that are still awaiting investigation: Status
pendingManualReview
- Notifications also return any relevant categories and subcategories.
Case Review Portal
Added
Quality Assurance
We're proud to introduce a new Quality Assurance functionality that lets your Compliance and QA teams flag process improvements and demonstrate evidence of compliance reviews to regulators and auditors.
Users with the QaAuditor role can create samples of completed cases for review, specifying the sample size and time period. Within cases, auditors can add comments on individual checks. Multiple auditors can collaborate on the same sample and track progress.
Selfie video depth camera data
For the App Drop-in iOS SDK, we now collect depth camera data while recording the selfie video to help confirm liveness. This functionality uses Apple TrueDepth technology on every model later than iPhone X 2017, including iPhone 11 and higher, but excluding iPhones SE 2020 and SE 5G 2022.
Improved
Physical Proof of Address
In addition to performing eligibility checks and including the Physical Proof of Address document photo in the CDD zipfile, we now extract the following data from the document:
- Document type
- Issue date
- Validity in days, based on the document type
- Client's name
- Client's home address
We return this data in the CDD PDF, XML, and JSON formats.
Tax Number
For the Tax Number module, you can now configure which TIN documents to accept. If a client provides a document that is outside your regulatory scope, we don't return the TIN to you.
For older notes, see the Release Notes Archive.
May 2024
App Components
Added
Introducing Fourthline App Components! If you build custom flows with your own UI, business logic, orchestration, reduce development time and effort with these standalone functionality modules for Android and iOS mobile apps.

App Drop-in vs App Components
Document Component
This component captures the document photos and video, with real-time feedback to the client, and extracts the data. It returns the photos, video, and data to you to upload to Fourthline via the API. We provide the UI, which you can customize in the same way as the App Drop-in. You can dynamically adjust the functionality, e.g. disable the tilted photo step.
Biometrics Component
This component captures the selfie photo and video, and functions the same way as the Document Component.
App Drop-in
Improved
You can now:
- Dynamically configure the minimum required age and related checks in the Identity Verification flow.
- Co-design Fourthline xcframeworks.
Web SDK
Added
European markets have different rules for the Tax Number module: some require evidence, such as a photo of a second document, and some have different forms of TIN, such as the Spanish NIE, NIF, and DNI. Fourthline has extensive knowledge of local regulations and our SDKs offer custom flows per market.

Market-specific Tax Number module
Previously, the Web SDK only supported the Dutch BSN flow. It now supports all Spanish TINs and the Italian codice fiscale, in parity with the App Drop-in.
Fixed
We fixed an issue where signed documents for Qualified Electronic Signature weren't available to download on some devices.
April 2024
App Drop-in
Added
As of May 1, 2024, Apple applies new third-party library requirements for all application owners on the App Store. For more information, see Apple Developer – Upcoming third-party SDK requirements.
Although Fourthline's iOS SDK itself isn't impacted, it uses 2 impacted libraries: Lottie and OpenSSL. Therefore we added a manifest file to the SDK, that explains which data points are used for what reason.
Fixed
We fixed:
- Some issues related to extending the validity of French national ID cards
- The Unknown selfie error, which was mostly occurring on iPhone 12 mini devices
Web SDK
Improved
Permissions dialog
We improved conversion in the Location section of the Identity Verification flow. To access the client's device geolocation, they need to give both operating system (OS) and browser permissions, which are under the OS's jurisdiction. If the client initially blocks permission and then decides to unblock it (especially on iOS), they need to change the permission settings on their device. At this point, there was an increase in drop-outs.
-
Before: On the Location access blocked screen, the client tapped the Learn more call-to-action (CTA) button, and an overlay containing the unblocking instructions opened. The client tapped
X
to close the overlay, changed the settings, and then tapped the Try again CTA button. -
Now: On the Location access blocked screen, the unblocking instructions are displayed in an accordion, providing a clear overview of the 2 steps involved. The client changes the settings and then taps the Try again CTA button.
UI improvements
Furthermore, the unblocking instructions for both the device's geolocation and camera are now contextual and match the client's OS and browser.
Contextual instructions for changing geolocation and camera permissions
Qualified Electronic Signature flow
We improved the 409: Incorrect passcode error message.
Fixed
We fixed some errors in the German copy.
AML Screening & Monitoring
- We released new Get hits endpoints that provide more information about false positives and confirmed hits.
- You can now configure to screen clients by PEP, sanctions, adverse media, and convictions hits separately or a custom combination, instead of all together.
- We overhauled the backend to improve search accuracy, stability, and speed.
March 2024
App Drop-in
Improved
Document NFC for Spanish documents
Document NFC is one of the most secure features of Fourthline's Document flow. For Spanish documents, we can now more easily unlock NFC chips using the card access number (CAN).

Card access number on Spanish ID document
We then re-ordered the steps in the user journey, so that clients can choose:
- NFC flow: Scan the front and back of the card with NFC (42% shorter journey).
- Document scan flow: Take more document photos (front, front tilted, back, back tilted).
Click to magnify
NFC flow vs Document scan flow
Web SDK
Added
Physical Proof of Address
Physical Proof of Address is now available on Web SDK!
In this flow, the client:
- Enters the Physical Proof of Address module
- Selects the type of proof of address document
- Chooses to upload a PDF file or photo of the document from their device, or to take a photo of the document now
- Either selects a file or image to upload
- Or, takes a photo of the document
- Confirms the document photo
Physical Proof of Address on Web SDK
Enable JS prompt
Previously, if the client had JavaScript disabled in their mobile web browser, the Web SDK couldn't load.
Now, the SDK detects this and the UI prompts the client to enable JavaScript to start the workflow.
Enable JavaScript prompt
Improved
Feature configuration
You can now configure to enable or disable the following features:
- Selfie video
- Tax Number extraction
- Tilted document photos
Lower minimum age
Previously, the minimum supported age was 18 years and is now 16 years.
Case Review Portal
You can now set up access to the Case Review Portal via Okta Federation.
Updated about 2 hours ago