Add a person(holder/UBO)

During rejection remediation for business KYC, if the status is 'request', a person can be added. This action creates a new personId (without a full KYC rebuild), attaches a FACE_BIOMETRIC rejection record, and requires a biometric-url and GREEN status before review.


šŸ‘‰ Business KYC Rejection and Resubmission Guide

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string

Optional pending HOLDER_INFO / BENEFICIAL_OWNER_INFO rejection record to mark done after person is created (targetId may be empty)

string
enum
required

BENEFICIAL_OWNER = UBO; HOLDER = authorized/contact style holder (not a second signer)

Allowed:
string
required

Given name

string

Middle name

string
required

Surname

string
required

Birth date (YYYY-MM-DD)

string
enum
required

Issuing Country Code

string
enum
required

Issuing Country Code

string
enum
required

Gender

Allowed:
string
enum
required
string
required

ID number

string
enum
required

Identity document type enumeration.

  • passport: Passport
  • cn_ric: China Resident Identity Card
  • Hk_hkid: Hong Kong Identity Card (HKID)
  • driver_license: Driver's License
  • sg_nic: Singapore National Identity Card (NIC)
  • identity: Identity Card (generic)
  • other: Other ID Types
Allowed:
string
required

Role / ID start date (YYYY-MM-DD)

string

ID expiration date when required by idType

address
object
required

Address

string
required

Proof-of-address file id

number

Share percentage (required for BENEFICIAL_OWNER)

Headers
string
required

The unique identifier of the target entity. Mandatory for white-label customers to define the sub-entity context.

Response

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json