Thirdfort

Identity verification app for regulated industries

comprehensively tested across iOS and Android by QAwerk
Girl Image Boy Image Clip Icon Blue Clip Icon Red
×
Where do you want us to send our Thirdfort case study?
Please enter your business email isn′t a business email

Thirdfort provides digital identity verification and compliance checks for regulated businesses across sectors such as legal, property, and finance. Their platform helps companies onboard clients securely while meeting anti-money laundering (AML) and Know Your Customer (KYC) requirements.

All Customers

Mobile Application Testing

Our QA focused on validating the stability of Thirdfort’s mobile apps across iOS and Android during their transition to a new cross-platform version. We tested identity verification, Source of Funds flows, and critical onboarding scenarios to ensure consistent behavior across devices, OS versions, and environments.

Learn more

Manual Testing

We conducted structured manual testing of identity verification workflows, AML compliance checks, and onboarding flows. This included exploratory testing of high-risk scenarios, regression coverage after frequent releases, and validation of complex financial verification logic across mobile platforms.

Learn more

Challenge

Thirdfort engaged QAwerk to perform end-to-end testing of their mobile app functionality side-by-side across existing native iOS and Android versions and the new cross-platform release. The goal was to identify potential regressions early and ensure critical identity verification and compliance workflows remained stable during the transition.

To support this transition, we focused on several key testing priorities:

  • Migration from Native V3 to Cross-Platform V4: The new cross-platform release required careful validation of core user flows to ensure consistent behavior across platforms and prevent disruptions to verification and onboarding processes.
  • Compliance-Critical Verification Workflows: Features such as Source of Funds checks, ID verification integrations, document uploads, and financial data validation involved complex user journeys needed for accuracy and stability.
  • Fast Release Cadence: Regular builds and changelog updates required continuous regression coverage, quick validation of fixes, and reliable release readiness checks.
  • Complex Multi-Step User Journeys: Editing flows, back navigation behavior, validation logic, and state consistency required close verification to prevent users from losing progress or encountering blockers.
  • Device Variability and Environment Inconsistencies: Testing across multiple real devices, OS versions, and environments was necessary to detect platform-specific issues and ensure consistent behavior between backend-driven UI updates and mobile builds.
  • Realistic Data and Document Validation Requirements: Certain verification scenarios required realistic test data, NFC document scanning, and valid document samples to reproduce real-world onboarding conditions effectively.

Solution

Our approach was to embed continuous manual QA into Thirdfort’s release cycle. We focused on functional testing, regression coverage, exploratory checks, and cross-platform validation of identity verification and compliance flows across iOS and Android.

Mobile Application Testing

We conducted mobile application testing for Thirdfort across iOS and Android during the transition to the new cross-platform version. Our work focused on validating onboarding flows, identity verification journeys, document uploads, and Source of Funds checks to ensure stable operation of these workflows in the new cross-platform mobile release.
Why it matters: Thirdfort’s users complete identity and financial verification directly on mobile devices. Stable performance and consistent behavior across platforms are essential for smooth onboarding and reliable compliance workflows.

Functional Testing

During functional testing, we validated key compliance features including Original ID verification via the Onfido SDK, Enhanced ID verification through the ReadID SDK, document upload flows, and Source of Funds functionality. Particular attention was given to complex user journeys such as Purchaser and Giftor flows, bank statement linking, and document evidence handling.
Why it matters: These features form the operational core of Thirdfort’s verification platform. Issues in identity or financial validation flows can interrupt onboarding and create friction for regulated businesses.

Regression Testing & Exploratory Testing

Given frequent releases and changelog updates, we conducted ongoing regression and exploratory testing cycles. Focus areas included editing flows, back navigation behavior, server-driven UI responses, input validations, and consistency of completed verification states.

Critical blockers included Source of Funds submission errors and Enhanced ID loading freezes. They were tracked, retested, and verified as resolved before subsequent releases.
Why it matters: Frequent releases increase regression risk, especially in compliance-driven products. Continuous regression and exploratory testing helped prevent disruptions as new features and updates were introduced.

Compatibility Testing

Compatibility testing was performed on real iOS and Android devices across multiple OS versions to detect device-specific issues involving inputs, keyboard behavior, UI rendering, and performance. We also investigated environment inconsistencies related to backend-driven UI behavior.
UI/UX validation ensured users could complete verification journeys without losing progress or encountering blockers.
Why it matters: Thirdfort’s onboarding flows involve sensitive identity and financial data. Reliable performance across devices and environments helps prevent friction during identity verification and document submission flows.

Bugs Found

Most issues we uncovered were concentrated in the Source of Funds journey, especially in multi-step editing flows, data persistence, and navigation behavior. These were high-impact problems because they could block users from completing compliance checks or correcting submitted details.

Bug

Actual result: Previously added co-purchasers (A and B) are removed and only the latest one (C) remains.

Expected result: Previously added co-purchasers (A and B) should remain, and the newly added co-purchaser (C) should be added in addition, not replacing existing ones.

Bug

Actual result: On the Gift details review screen, there are no Edit buttons available for any section. As a result, the user cannot edit Gift details once they have been entered.

Expected result: Each Gift details section/block should have an Edit option (or a clear way to enter edit mode) so the user can update previously entered information.

Bug

Actual result: While editing a Funds source (e.g., Sale of property), tapping the Back button navigates backwards through each previous step of the flow one-by-one (e.g., from Sale details back to Property details, then further back), instead of taking the user back to the relevant Review screen / sources list. This makes the user “walk back” through the whole flow rather than exiting the edit context.

Expected result: When editing a completed source, tapping Back should return the user to the appropriate parent screen (e.g., the Review your details screen for that source, and then the Gift funds sources list), rather than navigating step-by-step through all earlier form steps.

Result

Our collaboration supported Thirdfort’s transition to a new cross-platform mobile version while maintaining stable identity verification and compliance workflows. Side-by-side testing, continuous regression coverage, and focused validation of financial verification features helped ensure the platform remained reliable during this product evolution.

Key outcomes included:

  • Stable Rollout of Complex Compliance Functionality: Comprehensive testing of the Source of Funds feature, involving multiple data sources, conditional flows, document handling, and bank integrations, supported a smooth release of this compliance-critical capability.
  • Consistent Mobile Experience Across Platforms: Cross-platform testing of iOS and Android versions helped maintain predictable onboarding, identity verification, and document submission flows during the migration from native to cross-platform apps.
  • Reduced Release Risk for a Regulated Fintech Product: Focused regression, exploratory testing, and validation of SDK integrations (Onfido Original ID and ReadID Enhanced ID) helped prevent blockers in identity verification journeys and compliance workflows.

In Press

Thirdfort helps more than 1,500 regulated businesses in the legal and property sectors keep moving in a world of ever-changing regulations and rising fraud.

Global press release distribution platform covering business, technology, and corporate announcements

Thirdfort utilises iProov Dynamic Liveness within its digital identity app to offer speed and convenience to legitimate users while providing robust protection against sophisticated fraud threats, such as AI-driven deepfakes and synthetic identities.

Industry publication covering biometrics, digital identity, and security technologies

Launching a compliance-heavy app?

Let’s talk

Tools

TestFlightTestFlight
Firebase App DistributionFirebase App Distribution
Google Play testing tracksGoogle Play testing tracks
JiraJira
SlackSlack
Google SheetsGoogle Sheets
FigmaFigma
MiroMiro
NotionNotion
80+ critical bugs identified and reported
1,500+regulated businesses using Thirdfort
20+regression cycles executed
25+Source of Funds scenarios tested
15+high-risk editing and navigation flows validated

QAwerk Team Comment

Iryna

Iryna
QA Engineer

Testing this project stood out for its fintech and regtech context, where quality expectations are naturally high, and user scenarios involve real identity verification, financial data, and official documentation. The Source of Funds feature was particularly memorable. It combined multiple funding sources, complex state dependencies, bank integrations, and strict requirements for accurate PDF and portal outputs used by legal professionals.

MokupMedia
MokupMedia
MokupMedia

Related in Our Blog

Test Early, Test Smart: Software Testing Phases Explained

Test Early, Test Smart: Software Testing Phases Explained

Software testing isn’t just a box to tick before launch—it’s a strategic process that scales with your product. If you miss the right testing phase, there’s a risk of bugs in production, slipping deadli...

Read More
How DORA Regulation Requirements Are Resetting FinTech Compliance Standards

How DORA Regulation Requirements Are Resetting FinTech Compliance Standards

Everyone’s talking about DORA compliance requirements, but most folks still treat it like a riddle wrapped in red tape. Spoiler: it’s neither boring nor optional, especially if your business is anywhere nea...

Read More
Manual vs Automated Testing for AI Agents: Which Approach Works Best?

Manual vs Automated Testing for AI Agents: Which Approach Works Best?

As more businesses experiment with building AI agents, the need to ensure their quality grows daily. AI testing is unique, requiring additional knowledge and skills specific to this domain....

Read More
Top 7 Challenges in Mobile Testing and How to Solve Them

Top 7 Challenges in Mobile Testing and How to Solve Them

Quality mobile apps require constant vigilance. Developers face intense market pressure, along with an ever-increasing variety of devices and OS versions. As a mobile testing company, QAwerk has helped improve ...

Read More

Impressed?

Hire us

Other Case Studies

ChitChat

ChitChat

Zambia

We bug-proofed this fintech app and prepared it for launch across 4 African countries

Unfold

Unfold

United States

We transformed this crash-prone storymaker into a full-blown content creation platform, which now has a billion users and was acquired by SquareSpace

ICONOMI

ICONOMI

United Kingdom

Optimized the web and mobile onboarding flow for a crypto asset management platform, reducing user drop-off by 15%