Integrating Thirdfort in Power Pages

You can integrate Thirdfort with Power Pages so that users start their identity and document checks directly from your portal, with the results written back to Dataverse automatically. In the integration we built, a button on the Power Pages site triggers a Power Automate flow that sends the user a Thirdfort verification request, and an Azure Function receives Thirdfort's notifications so the report and supporting documents are saved against the right record and shown back to the user on the site.

This post describes what the integration does and why we built it. It is written mainly for people implementing Power Platform solutions, so it covers the moving parts at a high level rather than step-by-step configuration.

What is Thirdfort?

Thirdfort is an automated identity and document verification platform. Users complete their checks in the Thirdfort app, which verifies that they are a real person and can also check documents such as bank statements, and the organisation receives a report showing the outcome. It is used by organisations in regulated sectors that have to carry out Know Your Customer (KYC) and anti-money laundering checks before they provide a service.

Why integrate Thirdfort with Power Pages?

Power Pages is Microsoft's platform for building external websites and portals on top of Dataverse, so customers can log in, view their own records and submit information. If you already run a customer portal in Power Pages, the identity check is one more step in the same process, and handling it in a separate system means staff copying requests, chasing users and filing reports by hand.

Bringing the two together gives you:

• a single place for the user to start their check, from the same portal account they already use
• status updates on the record in Dataverse without anyone keying them in
• the Thirdfort report and supporting documents saved against the right policy automatically
• a clear record of who was checked and when, for compliance purposes

For the user it is also a simpler process, as they are taken step by step from the Power Pages site to the Thirdfort app and back again.

How does the Thirdfort and Power Pages integration work?

The integration is built from standard Power Platform and Azure components:

• Power Pages for the customer-facing portal
• Dataverse to hold the policy records and their status
• Power Automate flows to send requests to Thirdfort and handle its notifications
• Azure Functions to receive and verify incoming requests from Thirdfort

1. The user starts the KYC check

Users log in to their Power Pages account and see their organisational policies, which are populated from a Dataverse table. To verify their identity they click the button labelled "KYC Check", which starts the process.

2. A flow sends the verification request

Clicking the button triggers a flow powered by Power Automate and Azure Functions. The record is updated to an "Awaiting KYC Check" status, and a request is generated and sent to the user automatically so they can continue the verification in the Thirdfort app.

3. Thirdfort notifications are received and verified

An Azure Function receives requests from Thirdfort and verifies them. Once a request has been verified it is passed to a Power Automate flow responsible for handling Thirdfort notifications, which receives the PolicyID so that updates are applied consistently to the right record in Dataverse.

4. The report and documents are saved

The Thirdfort API is used to create the report confirming that the user has passed the KYC check. The KYC documents are saved as a PDF named with the PolicyNumber from Dataverse, so it is easy to tell one policy's documents from another's. The notification handler also finds any additional documents the user has provided and saves them as a ZIP file, again with the PolicyNumber in the file name.

5. The user sees the results in the portal

In both cases the documents are visible to the user through the Power Pages site, so they can find them without having to ask.

What should you think about before building this?

A few points are worth agreeing early:

• which Dataverse tables and statuses the check needs to update, and who in your team acts on a failed check
• where the reports and documents are stored and how long you keep them, in line with your retention policy
• table permissions and web roles in Power Pages, so users only ever see their own records and documents
• how Azure Function keys and API credentials are stored and rotated
• who supports the flows and functions once they are live

If you do not have the skills in-house to look after integrations like this one, our Power Platform support service covers monitoring, fixes and changes.

Frequently asked questions

Can Power Pages connect to third-party verification services?

Yes. Power Pages sits on Dataverse, so Power Automate flows and Azure Functions can call external APIs such as Thirdfort and write the results back to the records the portal displays.

Why use an Azure Function as well as Power Automate?

In this integration the Azure Function receives and verifies incoming requests from Thirdfort before handing them to Power Automate, so only verified notifications update records in Dataverse.

Where are the Thirdfort reports stored?

The KYC report is saved as a PDF and any additional documents as a ZIP file, both named with the policy number from Dataverse and made available to the user on the Power Pages site.

If you have questions about Power Pages or an integration like this one, contact us.