JP onboarding
Overview
This page contains details about the Japan (JP) Know Your Business (KYB) flows and links to the following sub-pages for a quick reference:
| Page name | Description |
|---|---|
| JP required parameters | This page lists the required API fields of each entity type. |
| JP required documents | This page contains tables listing the required documents for verification of the business entity, stakeholders, and applicants. |
| JP position mapping | This page gives a quick glance at the required positions of each entity type. |
| JP request examples | This page contains API request examples for HK entities. |
Nium offers Manual KYB flows for customers in Japan.
Manual KYB Flow
The following steps must be performed to complete an application via Manual KYB.
A diagram showing the manual KYB flow for Hong Kong. (click to enlarge)
For Manual KYB, you need to call the Onboard Corporate Customer API directly. In this flow, the entire request body needs to be passed in the Onboard Corporate Customer API.
Applicant KYC
MANUAL_KYC are supported for applicants in JP. Uploading of documents is required for Manual KYC which needs to be sent in businessDetails.applicantDetails.documentDetails. For details, see JP required documents for applicants.
CAUTION
The API gateway has a limit of 10 MB for any API request. This makes Upload Document API the preferred way to upload documents since you can upload one document at a time.
Stakeholder KYC
Only MANUAL_KYC is offered for KYC of Individual stakeholders in Hong Kong. Uploading of documents is required for Manual KYC which needs to be sent in businessDetails.stakeholders.stakeholderDetails.documentDetails. For details, see HK required documents for stakeholders.
Bank Account Details
Applicants must submit Bank Account Details of the corporate customer in the businessDetails.bankAccountDetails object. This is required per regulations to enable auto-sweep.
After submission, the status in the response of the Onboard Corporate Customer API is IN_PROGRESS. Nium initiates manual verification and sends the response via webhook. The application can get approved at this stage. Any changes in status is again communicated via webhook. For the next steps based on the response of the webhook, see Webhooks.
Terms and Conditions
You must show customers the Nium terms and conditions configured for your client resource. You can fetch these specific terms and conditions using our Terms And Conditions API.
Customers can only submit the onboarding form once they accept the terms and conditions.
To fetch the Terms And Conditions API:
- Wait for the Onboarding API to return a
customerHashId. - Once returned, call our Accept Terms and Conditions API and include the
customerHashId. - Show the customer the returned terms and conditions and record their acceptance before allowing them to transact.
For more details, see Terms and Conditions.
Updated about 2 months ago