Konfir uses two status layers:
Verification status for the overall request
Activity status for each employment or gap in the timeline.
Verification status
This status appears at the top of the verification and tells you whether the applicant has submitted their verification.
Status | What it means | What to do next |
| The applicant has not submitted yet | Follow up if the verification is still required. |
| The applicant has submitted | Review the timeline and activity outcomes. |
| The verification ended before submission | Decide whether to retry (if appropriate) or use your fallback process. |
Note: A verification can be Completed even if some (or all) activities are not verified
Cancellation reasons
Cancellation reasons
Reason | What it means |
| The verification expired before completion |
| The applicant declined to use Konfir |
| Another live verification exists for this applicant |
| Someone on your team cancelled the request |
| A system or data error prevented completion |
Activity statuses
Each row in the timeline is an activity (i.e. employment or gap). Every activity has an activity status based on the strength of evidence Konfir could retrieve.
Status | What it means | What you’ll typically do |
✅ | Konfir has strong evidence that supports the activity. | Usually accept as verified (subject to your policy) |
🔄 | Some relevant evidence exists for the activity period, but it isn’t strong/complete enough to auto-verify. | Expand the activity and review what evidence is present. |
❌ | No usable evidence was found for the activity period from any source. | Consider a retry or your fallback process (if you still require evidence). |
Connected
What it means: The applicant connected at least one data source and Konfir retrieved some data that overlaps with the activity period, but it wasn’t strong enough to verify automatically.
Source | What counts as a connection |
Open Banking (Employment) | At least one debit transaction exists within the declared employment start/end dates |
Open Banking (Gap) | At least one credit or debit transaction within the declared employment start/end dates |
Payroll | At least one employment data point is returned within the declared employment start/end dates |
HMRC | At least one PAYE record exists within the declared employment start/end dates |
Not Connected
What it means: There was no data connected from any source that overlapped with the period of the declared activity.
Reason | What it means |
| The applicant skipped or didn’t try to connect a source. |
| The applicant tried to connect but did not complete the connection (e.g., login/consent issue). |
| A source was connected, but it did not contain usable data covering the activity period. |
How to handle: If an activity is Not Connected and you still require evidence, you may need a retry or a fallback process.
