This page explains how Build With Me Ghana expects this control to work on the platform. It is written as operational guidance for customers, providers, and support teams.
Why KYC is required
- Build With Me handles property, construction, wallet, escrow, finance, fulfilment, and professional-service workflows. Strong identity controls help reduce fraud and protect customers, vendors, staff, and partners.
Account identity
- Each email address and Ghana Card number should create only one account.
- The expected Ghana Card format is similar to GHA-123456789-1. Test environments may allow approved UAT formats.
- Where NIA IVSP integration is active, the platform should validate the Ghana Card and live selfie through the configured verification service.
Legal name handling
- When identity is verified through the approved identity provider, the legal name returned by the provider should become the locked legal identity for the account.
- The legal name is intended for admin, compliance, and controlled operational views. Public display names can remain separate where the workflow allows.
Live selfie requirement
- The production flow is designed around a live camera selfie rather than ordinary image upload, because a live capture is a stronger control against impersonation.
Business and provider checks
- Some provider roles require business name, registration number, registration document, location, professional profile, or other role-specific evidence before approval.
- KYC approval does not automatically approve every provider role. Identity verification and service-role verification are related but separate controls.
Data protection note
- Identity and verification records should be handled with strict access control, auditability, and retention rules. Production launch should align this process with the final privacy policy and applicable law.
Need help? If your case does not match this guidance, submit a support request so the team can review the exact transaction, document, wallet event, or service record.