The platform currently runs against the mock provider with no live registry configured. While the automated registry integration is being set up, the day-to-day flow is manual attestation, described below. Officers can still submit an automated check, but it resolves against the mock service.
KYC status lifecycle
A member’s KYC status moves through the following states as you work through verification.KYC history is permanent. Every verification attempt creates a new record on the member’s profile showing the date, time, result, and the staff member who submitted it. This history is visible on the KYC page and cannot be edited or deleted.
Submitting a member for KYC verification
You need the members.kyc.submit capability to submit verification requests. The Credit Officer and the Administrator hold this capability, so either can run an automated check or record a manual attestation.1
Open the member's profile
Search for the member on the Members list and click their name to open their profile.
2
Open the KYC page
Click the KYC button in the profile header. This opens a dedicated page headed “KYC for ” showing the member’s current KYC status and the full verification history.
3
Confirm the identifier you are verifying
The KYC page shows two identity panels side by side: one for the member’s TRN and one for their Driver’s licence. Each panel shows whether a number is on file and lists any identity documents already uploaded for that identifier.Confirm that the relevant number is on file, shown as encrypted. If a number is missing, use the inline Add number control on the panel to set it without leaving the page. The TRN must be nine digits in the format 000-000-000, and a driver’s licence number must be 4 to 12 letters or digits.Below the two panels, the Other identification card holds every other identity document the member presents: passport, national ID, voter’s ID, and the like. Upload them there. A passport number is not added inline on this page the way TRN and driver’s licence are; set it on the member’s Edit page first.
4
Submit for verification
In the Verification type dropdown, choose TRN or Driver’s licence, then click Submit for verification. An identifier with no number on file is disabled in the dropdown. The platform sends the details to the identity verification service and sets the member’s KYC status to IN_PROGRESS.The automated check covers TRN and driver’s licence only. There is no automated passport registry, so a passport is confirmed by manual attestation instead.
5
Wait for the result
Results come back within seconds. The page reflects the new status once the check completes:
- VERIFIED: the check passed. The member is now eligible for loan applications.
- FAILED: the check was rejected. See the section below on retrying.
- MANUAL_REVIEW: the check was escalated. See the section below on manual review.
Record an in-person verification
Anyone with the members.kyc.submit capability, which the Credit Officer and the Administrator hold, can record a manual, in-person identity check instead of running the automated service. This is the default flow today while the automated registry integration is being configured. Use it when the member presents their identification at the branch and a staff member confirms it against the person. To submit a manual attestation you must provide all three of the following:- At least one identifier type you checked: TRN, Driver’s licence, or Passport. The number must already be on file. For a passport, set the passport number on the member’s Edit page first, since it cannot be added inline on the KYC page.
- At least one supporting document linked from the member’s file. Each linked document must belong to the member and be in UPLOADED or SCANNED_CLEAN status. Only those two statuses qualify, so a document that is infected, expired, or archived cannot be attested against.
- An attestation note of at least 10 characters describing what you confirmed, for example “Customer in branch, IDs match photo, DOB matches.” The field holds up to 500.
member.kyc.manually_verified audit event, recording the officer, the attested documents, and a preview of the attestation note (its first 200 characters).
Retrying a failed verification
If a member’s KYC status is FAILED, the identity details submitted did not match the records held by the verification service. Correct the underlying cause before resubmitting.1
Review the member's identity details
Go to the member’s profile and click Edit. Check the TRN and driver’s licence number carefully for typos, transposed digits, or missing characters. Only these two identifiers are sent to the verifier, so a typo elsewhere cannot cause a FAILED result.
2
Correct any errors and save
Update the relevant field and save the profile.
3
Resubmit the verification
Return to the KYC page and click Submit for verification again. Each new submission creates a fresh verification record. Your previous attempts and their results remain in the history.
Manual review
When a member’s KYC status is MANUAL_REVIEW, the automated check could not reach a conclusion, for example because the records returned an ambiguous match. The platform automatically creates a task in the KYC review queue, found in the sidebar under Review queue then KYC review. A staff member with the members.kyc.review capability, which the Credit Manager and Administrator hold, works the queued task. They first claim the task onto themselves, which moves it from the open queue into their hands, then submit one of three decisions based on the documents and information on file:- Approve: the member’s KYC status moves to VERIFIED and they become eligible for loan applications.
- Reject: the member’s KYC status moves to FAILED, and you can correct their details and resubmit.
- Escalate to senior reviewer: this closes the review as Escalated and records the chosen senior reviewer (Credit Manager or Administrator) plus a reason code in the audit log. The member’s KYC status does not change; they stay in MANUAL_REVIEW, but the review task itself is now closed.