Overview
A Konfir verification starts when you create a request for an applicant. The applicant then completes the Konfir journey to connect evidence sources. As evidence is connected, Konfir’s verification engine processes it into a structured result you can review in Konsole and API
Verification lifecycle
Stage | What happens | Learn more |
1) Verification created | You create the verification request | |
2) Applicant journey | The applicant completes the verification journey | |
3) Verification engine | Konfir processes connected data | |
4) Result | Konfir delivers the verification result via Konsole & API. |
1) Verification created
A verification request is created either via the Konsole or the API, depending on the method used. In your request, you define:
Who the applicant is
What you want Konfir to verify.
What data sources can be used
2) Applicant journey
Once created, the verification moves into the applicant’s hands. The applicant enters the Konfir journey from an invite link (Konsole or CSV) or from an embedded flow (API), then connects the evidence sources they can access.
As each connection succeeds, evidence can begin to arrive and be processed. If you view a verification while the applicant is still in progress, you may see partial or evolving information. The verification becomes ready to review only when the applicant submits the journey.
3) Verification engine
After evidence is connected, Konfir’s Verification Engine turns raw source data into a structured verification result. At a high level, the engine:
standardises evidence across sources
links related evidence into a timeline
applies statuses, alerts & insights