US Trust Required Fields

📘
NOTE
The below sections do not include all the fields from the API. They are only those that are relevant for this region. See API Reference for the full payload.

For other entity types, see:

Property	Description	Needed?
`region`	The country/region from where the end-customer (corporate customer) is located and thus getting onboarded. For the US based customers to be onboarded, use the value `US`.	Required

`businessDetails` Object

Object to accept the Business Details.

Property	Description	Needed?
`referenceId`	The unique reference ID for the Business Entity. Clients can pass a unique UUID value that Nium Platform uses as to identify the `businessDetails` entity. If not provided, Nium Platform will generate one. This unique reference Id can later be used to respond to RFI or to upload required documents for the business entity.	Optional
`businessName`	Registered Business Name	Required
`businessRegistrationNumber`	Business Registration Number. Note: For US, this field accepts the tax identification number of the business.	Required
`tradeName`	Trading Name / Doing Business As / DBA (In case the entity is doing business with a different name than the registered business name)	Optional
`businessType`	Legal entity type of the business. See Enum Values for valid set of values.	Required
`description`	This field accepts the brief overview of the business.	Required
`stockSymbol`	Stock/Ticker symbol of the business. Optional for Public Companies and n/a for all other entities.	Conditional

`legalDetails` Object

Object within the businessDetails object to accept the legal details.

Property	Description	Needed?
`registeredDate`	Date of incorporation	Required
`registeredCountry`	Country of registration/incorporation	Required
`listedExchange`	The Exchange where the business is publicly listed. See Enum Values for valid set of values. Required for Public Companies and n/a for all other entities.	Conditional

`regulatoryDetails` Object

Object within the businessDetails object to accept regulatory status of the Client.

Property	Description	Needed?
`unregulatedTrustType`	Unregulated Trust Type Detail. See Enum Values for valid set of values. This is an array, and hence can pass more than one value to this field. This is required for Trusts and n/a for all other entities.	Conditional

`RegisteredAddress` Object

Object within the businessDetails object to accept the address details where the company is registered.

Property	Description	Needed?
`registeredAddress`	Address where business was registered	Required
`addressLine1`	Address Line 1	Required
`addressLine2`	Address Line 2	Optional
`city`	City / suburb	Required
`state`	State	Required
`country`	Country	Required
`postcode`	Post Code	Required

`businessAddress` Object

Object within the businessDetails object to accept the address details where the company does business.

NOTE: These fields are used only if the principal place of business is different than the registered address.

NOTE: These fields are conditional where if isSameBusinessAddress = NO.

Property	Description	Needed?
`businessAddress`	If the principal place of Business is different than the registered address	Conditional
`addressLine1`	Address Line 1	Conditional
`addressLine2`	Address Line 2	Conditional
`city`	City /suburb	Conditional
`state`	State	Conditional
`country`	Country	Conditional
`postcode`	Post Code	Conditional

`documentDetails` Object

Object within the businessDetails object to accept the one or many documents sent via the API.

Property	Description	Needed?
`documentType`	See Enum Values for valid set of values.	Required
`document`	Document file	Required
`fileName`	File name	Required
`fileType`	File type	Required
`document`		Required

`stakeholders` Object

The array of object to accept multiple stakeholders information. For every stakeholder object sent in the API, the Nium Clients must send either 'stakeholderDetails' or 'businessPartner'.

Property	Description	Needed?
`referenceId`	Unique referenceId associated with the stakeholder. Clients can pass a unique UUID value and Nium Platform can use the given value to identify the given stakeholder object (which could be either a stakeholderDetails object or a businessPartner object), and if not provided, Nium Platform will generate one. This unique reference Id can later be used to respond to RFI or to upload required documents for the given stakeholder object.	Optional
`stakeholderDetails`	Details of individual stakeholder (at least one natural person)	Required
`kycMode`	Mode for KYC verification: `E_KYC` or `MANUAL_KYC`	Required
`firstName`	First Name	Required
`middleName`	Middle Name	Optional
`lastName`	Last Name	Required
`nationality`	Nationality	Required
`dateOfBirth`	Date of birth	Required
`professionalDetails`	Professional details of the stakeholder	Required
`position`	Position of the stakeholder. At least one of the individual stakeholder (natural person) should have a position as `CONTROL_PRONG`. See Enum Values for valid set of values.	Required
`sharePercentage`	Share percentage of the stakeholder in the company. If the stakeholder’s position is Ultimate Beneficial Owner (UBO), then the share percentage is a required input parameter, that is `if position = UBO)`	Conditional
`addressDetails`	Residential address of the stakeholder.	Required
`addressLine1`	Address Line 1 of the stakeholder.	Required
`addressLine2`	Address Line 2 of the stakeholder.	Optional
`city`	City or suburb of the stakeholder.	Required
`state`	State of the stakeholder.	Required
`country`	Country of the stakeholder.	Required
`postcode`	Post Code of the stakeholder.	Required
`contactDetails`	Contact details of the stakeholder.	Optional
`email`	Email of the stakeholder.	Optional
`contactNo`	Contact Number of the stakeholder.	Optional
`documentDetails`	Document details of stakeholder	Required
`documentType`	See Enum Values for valid set of values.	Required
`documentNumber`	Document Number	Required
`businessPartner`	Details of business partner, if applicable.	Conditional
`businessName`	Business Name	Required
`businessRegistrationNumber`	Business Registration Number	Required
`businessEntityType`	Position of the business partner in the company. See Enum Values for valid set of values.	Required
`sharePercentage`	Share percentage `(if position = UBO)`	Conditional
`registeredCountry`	Country of Incorporation	Required

`applicantDetails` Object

This object contains details about the person, ways to identify them, contact them, documents, etc.

Property	Description	Needed?
`referenceId`	Unique referenceId associated with the applicant. Clients can pass a unique UUID value and Nium Platform can use the given value to identify the given applicant object, and if not provided, Nium Platform will generate one. This unique reference Id can later be used to respond to RFI or to upload required documents for the given applicant.	Optional
`kycMode`	KYC Mode of the applicant. Applicable values: `E_KYC` / `MANUAL_KYC`	Required
`firstName`	First Name	Required
`middleName`	Middle Name	Optional
`lastName`	Last Name	Required
`nationality`	Nationality	Required
`dateOfBirth`	Date of Birth	Required
`professionalDetails`.	Professional details of the applicant	Required
`position`	Position of the applicant. See Enum Values for valid set of values.	Required
`sharePercentage`	Share percentage `(if position = UBO)`	Conditional
`address`	Residential address of the applicant	Required
`addressLine1`	Address Line 1 of the applicant	Required
`addressLine2`	Address Line 2 of the applicant	Optional
`city`	City or Suburb of the applicant	Required
`state`	State of the applicant	Required
`country`	Country of the applicant	Required
`postcode`	Post Code or zip code of the applicant	Required
`contactDetails`	Contact details of applicant	Required
`email`	Email of the applicant	Required
`countryCode`.	Country code of mobile number	Required
`contactNo`	Mobile number of the applicant	Required
`documentDetails`	Document details of applicant	Required
`documentType`	See Enum Values for valid set of values.	Required
`documentNumber`	Document Number	Required
`document`	Document Copy	Required
`fileName`	File name	Required
`fileType`	File Type	Required
`document`		Required

`additionalInfo` Object

This object contains edge-case information about the business.

Property	Description	Needed?
`isSameBusinessAddress`	Yes/No field to indicate if the principal place of business is same or different from the registered address for the business entity.	Conditional

`riskAssessmentInfo` Object

Details required for determining Risk Profile.

Property	Description	Needed?
`totalEmployees`	Size of the business (No of employees). See Enum Values for valid values.	Required
`annualTurnover`	Size of the business (Annual Turnover). See Enum Values for valid values.	Required
`industrySector`	Industry Sector. See Enum Values for valid values.	Required
`countryOfOperation`	List of countries where business operation exist apart from the registered country	Required
`transactionCountries`	Where could we expect the transaction activities of the business customer to occur i.e. send to/receive from/spend in.	Required
`intendedUseOfAccount`	Customer's intended use of account. See Enum Values for valid values.	Required

`productDetails` Object

This Object accepts the product details.

Property	Description	Needed?
`segment`	Nium Platform supports configurations of fee-templates for a list of customer-segments (i.e., Gold, Silver, Bronze, etc.,), and Nium Platform Clients can onboard a Customer with the configured Segment (as configured with the fee-template setup). This will enable the Nium Platform Client to charge differential fees to its Customers.	Optional
`productType`	One or more product types offered by the platform. Acceptable values - Cards, Send and Receive. For the US - please just pass Send and Receive. Cards is NOT supported in the US Nium One Platform (for now).	Required
`program`	The acceptable value is SME.	Required

`tags` Object

This object contains the user defined key-value pairs provided by the client.

Property	Description	Needed?
`key`	The name of the tag. Maximum key length limit is 128 characters.	Optional
`value`	The value of the tag.	Optional

KYC

With respect to onboarding the Business/Corporate Customers that are located in the US: Nium's Platform Clients can use the Nium's One Platform's APIs to onboard Business Customers (Corporate Customers). For the US based customers onboarding, Nium will perform the due diligence using a combination of automated checks and manual verification.

US-Resident	Non-Resident
If the Stakeholder or applicant is a natural person and is a resident of the US, then Nium can perform E-KYC of the person using his/her SSN. We advise the Client (i.e., Nium's Platform Client) to indicate `E_KYC` in the `kycMode` field (in the stakeholderDetails)	If the Stakeholder or applicant is a natural person and is NOT a resident of the US, then Nium can perform Manual-KYC of the person. We advise the Client (i.e., Nium's Platform Client) to indicate `Manual_KYC` in the `kycMode` field (in the stakeholderDetails)

For the documentType document, refer to Stakeholer_Applicant Doc tab for details about the right data elements to be passed for the document types.

Document Type

List of property field names used in the below Document Type table:

Property	Field Name
Business Registration Document (BRD)	`BUSINESS_REGISTRATION_DOC`
Proof of Existence (PoE)	`PROOF_OF_EXISTENCE`
Partnership Deed (PD)	`PARTNERSHIP_DEED`
Trust Deed (TD)	`TRUST_DEED`
Letter of Authorization (LoA)	`LOA`
-------------------------------------------	---------------------------------
Sole Trader	`SOLE_TRADER`
Public Company	`PUBLIC_COMPANY`
Limited Liability Partnership Firm (LLPF)	`LIMITED_LIABILITY_PARTNERSHIP`
Limited Liability Company (LLC}	`LIMITED_LIABILITY_COMPANY`
Corporations (Corp)	`CORPORATION`
Unincorporated Association (UA)	`UNINCORP_ASSOCIATION`
Limited Partnership (LP)	`LIMITED_PARTNERSHIP`
General Partnership (GP)	`GENERAL_PARTNERSHIP`
Trust	`TRUST`
Estate	`ESTATE`

Table of Document Types required for each business entity:

	Biz Reg Doc	Proof of Existence	Partnership Deed	Trust Deed	LoA
Sole Trader	Yes	-	-	-	-
Public Company	-	Yes	-	-	-
Limited Liability Partnership Firm	Yes	-	-	-	-
Limited Liability Company	Yes	-	-	-	-
Corporations	Yes	-	-	-	-
Unincorporated Association	Yes	-	-	-	-
Limited Partnership	Yes	-	Yes	-	-
General Partnership	-	-	Yes	-	-
Trust	-	-	-	Yes	-
Estate	-	-	-	-	Yes

KYC Type

NOTE: For stakeholders, documents are needed only for natural persons, not for legal entities.

Type	Remarks
`E_KYC`	If the stakeholder or applicant is a resident of the US, SSN to be passed as National ID.
`MANUAL_KYC`	If the stakeholder or applicant is NOT a resident of the US, need documents to support Proof of Address (POA) and Proof of Identity (POI), so they can send their passport details or Driver License or National ID (as issued by their residence country).

Stakeholder-Applicant Docs

Document	KYC Mode	`documentType`	`documentNumber`	`documentIssuanceCountry`	`documentExpiryDate`	`document.fileName`	`document.fileType`	`document.document`
Passport	`MANUAL_KYC` (for non-US)	`PASSPORT`	Yes (PP Number)	Yes	Yes	Yes	Yes	Yes
Drivers License	`MANUAL_KYC` (for non-US)	`DRIVER_LICENCE`	Yes (DL Number)	Yes	Yes	Yes	Yes	Yes
National ID	`E_KYC` (for US)	`NATIONAL_ID`	Yes (9-digit SSN)	-	-	-	-	-
National ID	`MANUAL_KYC` (for Non-US)	`NATIONAL_ID`	Yes	Yes	-	Yes	Yes	Yes

📘NOTE

businessDetails Object

legalDetails Object

regulatoryDetails Object

RegisteredAddress Object

businessAddress Object

documentDetails Object

stakeholders Object

applicantDetails Object

additionalInfo Object

riskAssessmentInfo Object

productDetails Object

tags Object

KYC

Document Type

KYC Type

Stakeholder-Applicant Docs

📘
NOTE

`businessDetails` Object

`legalDetails` Object

`regulatoryDetails` Object

`RegisteredAddress` Object

`businessAddress` Object

`documentDetails` Object

`stakeholders` Object

`applicantDetails` Object

`additionalInfo` Object

`riskAssessmentInfo` Object

`productDetails` Object

`tags` Object