Short on Time Summary
Make user identity checks more efficient by making them accessible directly from your Power Pages sites. In this article, we use ThirdFort – a client and document verification tool – as an example integration.
This article was written by one of our experts and will include a high-level description of what the integration is meant to do and explain why it was created.
Purpose of the Integration
Integrating ThirdFort in Power Pages sites will protect organisations operating in a regulated industry when they provide services to a user. ThirdFort is an automated ID and document verification platform that safeguards client and employee personal information, while providing an efficient user experience.
By using ThirdFort, we can send off requests to verify that the user is a real person. We can also check the validity of bank statements and other documents to further prove their identity and seamlessly meet security and compliance requirements.
The integration streamlines the verification process, allowing users to navigate from the Power Pages site to the ThirdFort app, where they can complete the necessary checks. This means you can spend more time focused on the tasks that matter most to your business.
For users buying services from an organisation, this integration is also a far more efficient method. They are taken through the process step-by-step – moving directly from the Power Pages site to the ThirdFort app.
Result of the Integration
With this integration, users can now login to their Power Pages account and view organisational policies that have been populated from a Dataverse table. Users can verify their identity by initiating the Know Your Customer (KYC) check by clicking the button labelled ‘KYC Check’. This triggers the check process.
This action triggers a flow powered by Power Automate and Azure Functions. Once a user has clicked ‘KYC Check’, the record will be updated to the ‘Awaiting KYC Check’ status. A request is then automatically generated and sent to the user to continue with the verification process.
An Azure Function is used to receive and verify requests from ThirdFort. When the verification is successful, it will be forwarded to a Power Automate flow that is responsible for handling ThirdFort notifications.
It will then receive the PolicyID, ensuring consistent updates within Dataverse. The API will be used to create the ThirdFort report which verifies that the user has passed the ThirdFort KYC check. The associated KYC documents are saved as a PDF file type, conveniently named using the PolicyNumber in Dataverse. This enables users to easily differentiate between policy documents.
The notification handler will also locate any additional documents that have been provided by a user and will save these documents as a ZIP file. The PolicyNumber will be included within the file name.
In both scenarios, the documents are visible to the users via the Power Pages site to improve findability and ease of access. The ThirdFort integration with Power Pages streamlines user identity checks and ensures organisations can protect sensitive information and meet compliance requirements.
This article was written primarily for people who will be implementing these digital solutions. If you have any questions about the Power Platform or the integration mentioned in this article, contact us to learn how it can benefit your organisation. You can stay up to date with the latest Microsoft updates on LinkedIn or subscribe to our monthly newsletter to get these insights delivered directly to your inbox.
