humanIdentityRequirement

A Skyfire user can subscribe as an Individual or Organization. When creating a seller service, you may specify which identity fields are required to access the service by configuring humanIdentityRequirement.


Identity Types

You may configure requirements for:

  • "individual"
  • "organization"

Each accepts an array of required field names.


Individual

Level 1 Fields (Basic Identity)

Field NameType
birthdatestring
given_namestring
middle_namestring
family_namestring
phone_numberstring
phone_country_codestring

Level 2 Fields (Extended Identity)

Includes all Level 1 fields, plus:

Field NameType
id_document.issued_onstring
id_document.expires_onstring
id_document.issued_bystring
address-fullstring
address-citystring
address-regionstring
address-countrystring
no-addressstring

Organization

The following fields are allowed for "organization":

Field NameType
organization_namestring
organization_tax_idstring
organization_physical_address-fullstring
organization_physical_address-citystring
organization_physical_address-regionstring
organization_physical_address-countrystring
no-organization_physical_addressstring
organization_registered_address-fullstring
organization_registered_address-citystring
organization_registered_address-regionstring
organization_registered_address-countrystring
no-organization_registered_addressstring
birthdatestring
given_namestring
middle_namestring
family_namestring
phone_numberstring
phone_country_codestring

Empty Requirements

Both "individual" and "organization" may be set to empty arrays:

{
  "individual": [],
  "organization": []
}

This means:

  • Only a verified email is required, or
  • No additional identity verification is enforced