Quickstart (Individual)

Individual Customers

Individual customers are the end-users holding the balance. In a corporate T&E use case, this would be the staff member receiving the T&E card. In a consumer-funded use case, this would be the retail end-customer having the account. Depending on the nature of the product/program, the KYC and onboarding flow will differ. Work with your program representative in NIUM. Where KYC is mandatory, Nium's e-KYC options (MyInfo in Singapore, greenID in Australia, Onfido in multiple markets) must be used to automate KYC and onboarding process.

Customer Onboarding Process

The customer onboarding process in the Nium platform is as follows:

  1. Customer account creation.
  2. Customer compliance checks.
  3. Compliance Score and Status Change Flow
  4. RFI Flow

1. Customer Account Creation

The customer account can be created by providing customer details through the Unified Add Customer API. These customer details include the customer’s personal details, contact details, KYC details, and tax details. Some of the above-stated items are optional depending on the region and defined KYC option. The KYC options are:

  • Manual KYC - Performed by the Nium Compliance team.
  • MyInfo - eKYC solution in Singapore.
  • GreenID - eKYC solution in Australia.
  • Onfido - eKYC solution in EU countries and UK.

Once the customer account is created, the compliance process is initiated automatically.

2. Customer Compliance Checks

The compliance process for a customer involves Screening and KYC. Depending on the program, the customer might be subjected to only screening or both screening and KYC.

StepDescription
ScreeningChecks whether the customer is part of any of the regulatory blacklists or not and if it is legally allowed to do business with this customer.
KYCVerifies whether the details provided by the customer are theirs. It includes authenticating the identity and address of the customer using Proof of Identity (PoI) and Proof of Address (PoA). The proof of identity and address can be verified two ways:
a) Manual KYC - manually by the Compliance team.
b) eKYC - digitally by third-party services.

Depending on how the KYC is performed, the compliance templates are defined for the particular client. These templates are also managed at two levels:
a) Screening
b) Screening + KYC
Depending on the program, either of these can be configured. If both are configured, then Screening + KYC will be initiated.

3. Compliance Score and Status Change Flow

These compliance templates are a group of compliance services that are meant to be run when compliance checks are initiated. Based on the template, these services are invoked whenever the customer is created on the platform.

Each of these services will have a separate Compliance status as detailed below:

Compliance StatusDescription
INITIATEDCompliance has been initiated, and there are a few more steps for the customer to take to complete the KYC, such as adding required information.
This status is applicable only for eKYC.
IN PROGRESSKYC/Compliance process is in progress, and there is some action pending response from the customer, such as uploading a document.
ACTION REQUIREDCustomer has already uploaded documents, waiting for verification from the Compliance team.
RFI REQUESTEDRFI raised by Nium's Compliance team, Customer can respond to RFI through respondToRfi API.
COMPLETEDThe compliance process is completed.
ERRORNo action - customer application failed due to an error.
Contact Nium Customer Support for further assistance.
EXPIREDThe submitted document's date has expired. Nium team may raise an RFI.
REJECTIf the KYC has been rejected by compliance team, the status changes to REJECT. Reinitiate KYC process is available in this case.
CLOSEDeKYC - Not in use.

Each action will depend upon separate kycStatus and complianceStatus as detailed below:

KYC StatusCompliance StatusYour next actionAPIs involvedRemarks
PendingINITIATEDWait for compliance status callbackcustomerDetailseKYC is initiated. Our system will update the status according to GreenID and our screening results.
FailedREJECTReinitiate eKYC by providing the same customerHashIdcustomerDetails and addCustomerUsingGreenID (AU) (reinitiate)Check the Remarks or ComplianceRemarks
PendingERROREmail Nium.customerDetailsNium's Compliance team might need to check the errors manually.
PendingACTION_REQUIREDWait for the next compliance status update.customerDetailsNium's Compliance team requires manual check on this request.
PendingRFI_REQUESTEDCheck rfiDetails array and provide the requested information via uploadRfiDocuments API.customerDetails and uploadRfiDocumentsNium's Compliance team requires additional information to verify this customer.
PendingRFI_RESPONDEDWait for the next compliance status update.customerDetailsNium's Compliance team will verify the provided information in your uploadRfiDocuments API. Usually, our system will update the compliance status to ACTION_REQUIRED.
ClearCOMPLETEDContinue your user journey – e.g., Add CardcustomerDetailseKYC successful, the customer is onboarded.

📘

Info

We will call compliance Status callback to inform you of any change in compliance status, and then you need to call customerDetails API to retrieve the detailed information.

Within the complianceStatus:

  • INITIATED is the highest status.
  • CLOSED is the lowest status.

The overall compliance score is calculated based on the statuses of the individual services. The highest status among all the invoked services for that customer will be considered as the overall compliance status.

The compliance status changes for each customer are notified to clients on the Compliance Status Callback URL which is captured during client onboarding. Whenever clients receive this notification, they are supposed to get the updated customer details using the customerDetails API.

4. RFI Flow

When the Nium Compliance team finds any of the information insufficient, then the following happen.

  1. The Request for Information (RFI) is initiated, and the compliance status of that customer becomes RFI REQUESTED.

  2. The client receives a nudge at compliance status callback URL; that is, the next time they call customerDetails API, they get the status as RFI REQUESTED with the reason.

  3. The client must call respondToRfi API and provide the requested information.

  4. The compliance status changes to RFI RESPONDED.

  5. The compliance team reviews the information and takes the necessary action.