KYC verification of unregulated trusts (NZL)
Use this API call to perform KYC verification of unregulated trusts.
Parameters
Name | Type | Description |
---|---|---|
country | string | NZL |
name | string | |
unRegulatedTrustType | string | familyTrust / parallelTrust / singleTrust / nextGenTrust / businessTrust / charitableTrust |
registeredOfficeRequired | string | address |
trustDeed | string | base64 Data URI (JPG/PNG/PDF) |
stakeholders | array | beneficiaries / trustee (*) / settlors |
unRegulatedTrustType options
Option | Description |
---|---|
familyTrust | Family Trust |
parallelTrust | Parallel Trust |
singleTrust | Single Trust |
nextGenTrust | NextGen Trust |
businessTrust | Business Trust |
charitableTrust | Charitable Trust |
Stakeholder types
Name | Type | Note |
---|---|---|
beneficiaries | individual | Individuals who directly or indirectly own 25% or more of the entity, or are entitled to 25% or more of the income or assets of the entity. |
trustee | individual, private company, public company, government body | |
settlors | individual |
Note on submitting stakeholders
For each trust, the same individual can hold multiple stakeholder roles. For example, in a trust, a person can be both a trustee and a beneficiary. We strongly recommend submitting an individual in only one stakeholder role. If there is a specific role that must be included (i.e., is required), such as trustee, submit the individual in that role to avoid running multiple KYCs (identity verifications) for the same person within a single KYB, which would be redundant. This is a cost-effective approach. For instance, if John ok Citizen is both a trustee and beneficiary of MY TRUST, submit John ok Citizen as a trustee, as this role is required to be submitted, rather than as both. This will prevent duplicate charges for verification. Even if the individual is submitted under one role, bronID will map any additional relevant roles in the background and include them in the documentation.
Note on uploading documents
Base64 encoded uploads must be submitted as a Data URI (with data format prefix). Example PDF format:
data:application/pdf;base64,JVBERi0xLjUKJYCBgoMKMSAwIG9i...