Onboarding an individual
Accounts are classified into two distinct groups
MKYC - Medium KYC accounts
EKYC - Enhanced KYC accounts
1. MKYC accounts
MKYC accounts satisfy the minimum KYC requirements necessary to open an account
MKYC requirements
Field | Type | Description | Notes | |
|---|---|---|---|---|
1. |
| string | The customer's first name | [required] |
2. |
| string | The customer's last name | [required] |
3. |
| string | The customer’s phone number in international format (e.g., +233XXXXXXXXX) | [required] |
4. |
| string | Must be a recent, live image of the customer, used for accurate identification (see here for further details) | [required] |
5. |
| string | [required] | |
6. |
| string | Identification type. Must be one of the following | [required] |
7. |
| string | Identification number | [required] |
8. |
| string | Country ISO Alpha 2 code e.g. | [required] |
9. |
| string | Must be one of the following | [required] |
10. |
| string | Bio data page/side image | [optional] |
11. |
| string | Back cover image | [optional] |
12. |
| string | A government-issued identifier found on the customer’s residency permit, required for identity verification and regulatory compliance | [optional] for Ghanaians |
13. |
| string | Indicates the official issue date of the customer’s residency permit. Format: | [optional] for Ghanaians |
14. |
| string | Specifies the expiry date of the customer's residency permit. Format: | [optional] for Ghanaians |
15. |
| string | A unique identifier or path referencing the uploaded file of the customer's residency permit | [optional] for Ghanaians |
16. |
| string | A partner-generated unique reference used to track or reconcile individual transactions or customer actions within your system | [optional] |
MKYC API reference
Refer to MKYC onboard API for more details
Customer verification
All customers are verified using the identification information provided before they can be approved for creation. Updates will be sent via webhooks.
2. MKYC update
Update customer details when ID verification fails.
Field | Notes | |
|---|---|---|
1. |
| [required] |
2. |
| [optional] |
3. |
| [optional] |
4. |
| [optional] |
5. |
| [optional] |
MKYC Update API reference
Refer to MKYC update API for more details
3. EKYC Upgrade
EKYC accounts can only be created when the customer has an active MKYC account.
EKYC requirements
Field | Type | Description | Notes | |
|---|---|---|---|---|
1. |
| string | Can be one of the following | [required] |
2. |
| string | The customer’s active email address used for communication and account-related notifications | [optional] |
3. |
| string | The full name of the person identified as the customer’s next of kin | [required] |
4. |
| string | Next of kin's phone number in international format. Must not be the same as the customer's phone number. | [required] |
5. |
| string | Can be one of the following | [required] |
6. |
| string | Can be one of the following | [required] |
7. |
| string | Can be one of the following | [required] |
8. |
| string | See here for the list of sectors | [required] for employed |
9. |
| string | See here for the list of industries | [required] for employed |
10. |
| string | See here for the list of occupations | [required] for employed |
11. |
| string | Can be one of the following | [required] for employed |
12. |
| string | Additional source(s) of income apart from primary employment | [required] for employed |
13. |
| string | The name of the organization or company where the customer is currently employed | [required] for employed |
14. |
| string | Can be one of the following | [required] for employed |
15. |
| string | [required] for employed | |
16. |
| string | [required] for employed | |
17. |
| string | [required] for employed | |
18. |
| string | [required] for employed | |
19. |
| string | [required] for employed | |
20. |
| string | [required] for employed | |
21. |
| string | Available options are | [optional] default |
22. |
| array | Can be one or more of the following | [required] for |
EKYC API reference
Refer to EKYC onboard API for more details
4. Account funding
An account may be funded via any of our digital channels. We are connected to the Ghana Interbank Payment and Settlement Systems (GhIPSS), thus, all individual accounts created can be found on the GHIPSS Instant Pay (GIP) platform.
5. Approval process
An account created via API undergoes several processes. The chart below illustrates the lifecycle of an account, from the submission of details via the endpoint, through approval, to the eventual creation in the core banking system.
Fetch customer details
Retrieve the details and status of a customer at any stage of the onboarding process
Details API reference
Refer to fetch customer details API for more details