Customer onboarding and KYC
Establish individual or business relationships with jurisdiction-specific evidence and explicit approvals.
A customer relationship starts with the institution’s eligibility, identity, privacy and risk policies. Country requirements come from its qualified jurisdiction profile. A Nigerian BVN, NIN or CAC field is relevant only to the selected arrangement.
Prepare the application
Customer operations uses an authorised local or sandbox institution and permitted office. Capture the party, related people, beneficial ownership, signatories, consent, required evidence and the intended product. The institution’s policy determines the acceptable office and responsible team.
Current source entry points
| Work | Source operation | Boundary |
|---|---|---|
| Create a customer | POST /clients | Use the versioned request and actual permission/office checks |
| Read customer details | GET /clients/{clientId} | Verify association and data scope |
| Corporate identifiers | GET/PUT /clients/{clientId}/corporatekyc | Existing source reads/writes TIN and SCUML for an existing customer |
| Account mandates | /savingsaccounts/{savingsId}/mandates | Confirm the selected mandate and signatory operation’s parent and permission checks |
| Existing-customer online enrolment | /self/registration | Enrolment uses an existing customer/account relationship |
Paths are relative to the core API base. Inspect the reference for exact schemas. A source route establishes no full online onboarding or provider verification by itself.
Business online onboarding target
Corporate Internet Banking captures the company registry record, verifies directors and owners, records the signing and approval rules, obtains a version-bound board resolution, collects digital references and documents and shows one application status. Every required director signs the exact resolution. Material changes require renewed decisions or signatures.
Institution review creates the resulting customer, account and mandates only after the required evidence and approvals. Track pending signatures, returned evidence, rejection and expiry with a named owner. The full orchestration needs its actual channel contract and acceptance.
Acceptance and recovery
Retain party and application identity, evidence hashes, consent purpose, policy versions, decisions and created records. A duplicate submission should resolve its original identity under the operation’s actual idempotency contract. Lost verification responses require status enquiry. A changed owner or signatory must invalidate affected approvals before activation.
Test cross-institution access, incomplete ownership, duplicate identifiers, rejected evidence, stale signatures, interrupted enrolment and legitimate customer correction using synthetic data.