# Data collection Collect the required customer data during your sign-up flow and pass it to Solaris to create the necessary resources. Solaris uses two primary resources for customer data: * **Person resource:** Represents a natural person (retail customer, freelancer, or business representative). [API Reference](/api-reference/onboarding/persons/#tag/Persons) * **Business resource:** Represents a legal entity. [API Reference](/api-reference/onboarding/businesses/#tag/Businesses) ![Diagram: Customer data resources](/assets/data-resources.9e4361995d91a55751d2ce64d989e6816d80af13c5735b633c420300110a90ec.865bea7f.svg) The required data points depend on your product, customer type, and country. **Mandatory Fields:** Only the fields listed below are required for Solaris. You may collect additional optional fields based on your business needs. ## Digital Banking & Cards If you're onboarding customers for Digital Banking & Cards products, the following data points are required for each customer type and country: ### Retail customers (B2C) note You must pass these data points to Solaris when you [POST Create a person](/api-reference/onboarding/persons/#tag/Persons/paths/~1v1~1persons/post) resource for the customer. Germany - `salutation` **Note:** `MR` for male, `MS` for female, `null` for gender-neutral. - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` - `line_1` - `line_2` - `postal_code` - `city` - `country` - `birth_date` Format: YYYY-MM-DD - `birth_city` - `birth_country` - `nationality` - `employment_status` Possible values for Germany below: - `EMPLOYED` - `UNEMPLOYED` - `PUBLIC_SECTOR_EMPLOYEE` - `PROFESSIONAL_SOLDIER` - `FREELANCER` - `HOUSEWORK` - `APPRENTICE` - `MANAGEMENT` - `RETIRED` - `STUDENT` - `SELF_EMPLOYED` - `MILITARY_OR_COMMUNITY_SERVICE` - `tax_information` - `marital_status` - `mobile_number` - `terms_conditions_signed_at` - `data_terms_signed_at` - `own_economic_interest_signed_at` - `fatca_relevant` - `fatca_crs_confirmed_at` France - `salutation` **Note:** `MR` for male, `MS` for female; no gender-neutral options are possible. - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` - `line_1` - `line_2` - `postal_code` - `city` - `country` **Note:** Must be `FR` - `contact_address` (Must be available but set as optional) - `line_1` - `line_2` - `postal_code` - `city` - `country` **Note:** Must be `FR` - `birth_name` - `birth_date` - `birth_city` - `birth_country` - `birth_post_code` **Note:** Only required for customers born in France. Use the two- or three-digit code corresponding with the *département de naissance* where the customer was born. - `nationality` - `employment_status` Only the following values are allowed for France: - `EMPLOYED` - `UNEMPLOYED` - `RETIRED` - `STUDENT` - `SELF_EMPLOYED` - **Note:** If the customer selects the options `EMPLOYED` or `SELF_EMPLOYED`, then the `socioprofessional_category` and `work_country` parameters should be made available. - `email` - `mobile_number` - `branch` **Note:** Must be `FR` - `work_country` - `job_title` - `socioprofessional_category` - `purpose_of_account_opening` - `main_income_source` - `annual_income_range` - `terms_conditions_signed_at` - `data_terms_signed_at` - `own_economic_interest_signed_at` - `fatca_relevant` - `fatca_crs_confirmed_at` - `self_declared_as_pep` Italy Foreign Birth Countries **Crucial:** If the customer's `birth_country` is **NOT** Italy (`IT`), you must set the `birth_province` to **`EE`**. - `salutation` `Enum` **Note:** `MR` for male, `MS` for female. - `first_name` `String` (including all middle names as printed on the ID document) - `last_name` `String` (including all middle names as printed on the ID document) - `address` (Italian: *residenza*): The customer's legal residence. Must be in Italy. - `line_1` `String` - `line_2` `String` - `postal_code` `String` **Note:** Must correspond to the selected city. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `city` `String` **Note:** Must correspond to the selected province. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `country` `String(2)` **Note:** Must be `IT`. - `state` `String(2)` 2-digit Italian province code. [Download Province List (CSV)](/downloads/italy-province-list.csv). - `contact_address` (Italian: *domicilio*): (Optional) Temporary residence or secondary address. - *Fields same as address above* - `birth_date` `ISO 8601` (YYYY-MM-DD) - `birth_city` `String` **Note:** Must correspond to selected province. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `birth_country` `String(2)` [Download Country List (CSV)](/downloads/italy-country-list.csv). - `birth_province` `String(2)` [Download Province List (CSV)](/downloads/italy-province-list.csv). - `nationality` `String(2)` - `employment_status` `Enum` Only the following values are allowed for Italy: - `EMPLOYED` - `UNEMPLOYED` - `RETIRED` - `STUDENT` - `SELF_EMPLOYED` - **Note:** If the customer selects the options `EMPLOYED` or `SELF_EMPLOYED`, then the `nace_code` and `work_country` parameters should be made available. - `email` `String` - `mobile_number` `String` - `branch` `String(2)` **Note:** Must be `IT`. - `nace_code` `String` Relevant NACE codes up to level 2. - `work_country` `String(2)` ISO 3166-2 code. - `work_province` `String(2)` (Required if work country is `IT`). [Download Province List (CSV)](/downloads/italy-province-list.csv). - `purpose_of_account_opening` `String` - `main_income_source` `String` - `annual_income_range` `Enum` - `terms_conditions_signed_at` `ISO 8601` (Timestamp) - `data_terms_signed_at` `ISO 8601` (Timestamp) - `own_economic_interest_signed_at` `ISO 8601` (Timestamp) - `fatca_relevant` `Boolean` - `fatca_crs_confirmed_at` `ISO 8601` (Timestamp) - `self_declared_as_pep` `Boolean` Spain - `salutation` **Note:** `MR` (Sr.) for male, `MS` (Sra.) for female; no gender-neutral options are possible. - `first_name` **Note:** Must include all first names, separated by spaces. - `last_name` **Note:** Must include first and second last names, separated by spaces. - `address` Please note the requirements of spanish addresses [below](#spanish-addresses-requirements). - `line_1` (Street name, Number) - `line_2` (Floor, Door) - `postal_code` - `city` - `country` **Note:** Must be `ES` - `state` 2-digit Spanish province code. [Click here for a full list of Spanish province codes.](https://www.iso.org/obp/ui/#iso:code:3166:ES) - `birth_date` (Format: DD/MM/YYYY) - `birth_city` - `birth_country` - `birth_province` 2-digit Spanish province code. [Click here for a full list of Spanish province codes.](https://www.iso.org/obp/ui/#iso:code:3166:ES) - `nationality` - `employment_status` Only the following values are allowed for Spain: - `EMPLOYED` - `UNEMPLOYED` - `RETIRED` - `STUDENT` - `SELF_EMPLOYED` - **Note:** If the customer selects the options `EMPLOYED` or `SELF_EMPLOYED`, then the `nace_code` should be made available. - `email` - `mobile_number` - `branch` **Note:** Must be `ES` - `nace_code` Relevant NACE codes up to level 2. - `purpose_of_account_opening` - `main_income_source` - `annual_income_range` - `terms_conditions_signed_at` - `data_terms_signed_at` - `own_economic_interest_signed_at` - `fatca_relevant` - `fatca_crs_confirmed_at` - `self_declared_as_pep` ### Freelancers note You must pass these data points to Solaris when you [POST Create a person](/api-reference/onboarding/persons/#tag/Persons/paths/~1v1~1persons/post) resource for the customer. Germany - `salutation` **Note:** `MR` for male, `MS` for female, `null` for gender-neutral. - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` (Home address) - `line_1` - `line_2` - `postal_code` - `city` - `country` - `birth_date` - `birth_city` - `birth_country` - `nationality` - `employment_status` Possible values below: - `FREELANCER` - `SELF_EMPLOYED` - `tax_information` - `marital_status` - `mobile_number` - `business_trading_name` - `business_address_line_1` - `business_address_line_2` - `business_postal_code` - `business_city` - `business_country` - `business_purpose` - `nace_code` Relevant NACE codes up to level 4. - `purpose_of_account_opening` - `main_income_source` - `expected_monthly_revenue_cents` - `terms_conditions_signed_at` - `data_terms_signed_at` - `own_economic_interest_signed_at` - `fatca_relevant` - `fatca_crs_confirmed_at` France - `salutation` **Note:** `MR` for male, `MS` for female; no gender-neutral options are possible. - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` (Home address) - `line_1` - `line_2` - `postal_code` - `city` - `country` **Note:** Must be `FR` - `birth_name` - `birth_date` - `birth_city` - `birth_country` - `birth_post_code` **Note:** Only required for customers born in France. Use the two- or three-digit code corresponding with the *département de naissance* where the customer was born. - `nationality` - `employment_status` Only the following values are allowed: - `SELF_EMPLOYED` - **Note:** If the customer selects `SELF_EMPLOYED`, then you must ask if they want to open a freelancer account. If not, the customer must go through the B2C flow. Additionally, freelancer-only partners should reject all "personal expenses" accounts that are not linked to any professional or business activity. - `mobile_number` - `business_trading_name` - `business_address_line_1` - `business_address_line_2` - `business_postal_code` - `business_city` - `business_country` - `business_purpose` - `branch` **Note:** Must be `FR` - `work_country` - `socioprofessional_category` - `purpose_of_account_opening` - `main_income_source` - `annual_income_range` - `international_operativity_expectation` - `registration_number` (SIREN Number) - `terms_conditions_signed_at` - `data_terms_signed_at` - `own_economic_interest_signed_at` - `fatca_relevant` - `fatca_crs_confirmed_at` - `self_declared_as_pep` Italy Foreign Birth Countries **Crucial:** If the customer's `birth_country` is **NOT** Italy (`IT`), you must set the `birth_province` to **`EE`**. - `salutation` `Enum` **Note:** `MR` for male, `MS` for female. - `first_name` `String` (including all middle names as printed on the ID document) - `last_name` `String` (including all middle names as printed on the ID document) - `address` (Italian: *residenza*): The customer's legal residence. Must be in Italy. - `line_1` `String` - `line_2` `String` - `postal_code` `String` **Note:** Must correspond to the selected city. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `city` `String` **Note:** Must correspond to the selected province. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `country` `String(2)` **Note:** Must be `IT`. - `state` `String(2)` 2-digit Italian province code. [Download Province List (CSV)](/downloads/italy-province-list.csv). - `contact_address` (Italian: *domicilio*): (Optional) Temporary residence or secondary address. - *Fields same as address above* - `birth_date` `ISO 8601` (YYYY-MM-DD) - `birth_city` `String` **Note:** Must correspond to selected province. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `birth_country` `String(2)` [Download Country List (CSV)](/downloads/italy-country-list.csv). - `birth_province` `String(2)` [Download Province List (CSV)](/downloads/italy-province-list.csv). - `nationality` `String(2)` - `employment_status` `Enum` Only `SELF_EMPLOYED` is allowed. - **Note:** If the customer selects `SELF_EMPLOYED`, then you must ask if they want to open a freelancer account. If not, the customer must go through the B2C flow. Additionally, freelancer-only partners should reject all "personal expenses" accounts that are not linked to any professional or business activity. - `mobile_number` `String` - `branch` `String(2)` **Note:** Must be `IT`. - `nace_code` `String` Relevant NACE codes up to level 4. - `work_country` `String(2)` ISO 3166-2 code. - `work_province` `String(2)` (Required if work country is `IT`). [Download Province List (CSV)](/downloads/italy-province-list.csv). - `purpose_of_account_opening` `String` - `vat_number` `String(11)` - `main_income_source` `String` - `annual_income_range` `Enum` - `international_operativity_expectation` `String` - `terms_conditions_signed_at` `ISO 8601` (Timestamp) - `data_terms_signed_at` `ISO 8601` (Timestamp) - `own_economic_interest_signed_at` `ISO 8601` (Timestamp) - `fatca_relevant` `Boolean` - `fatca_crs_confirmed_at` `ISO 8601` (Timestamp) - `self_declared_as_pep` `Boolean` Spain - `salutation` **Note:** `MR` for male, `MS` for female; no gender-neutral options are possible. - `first_name` **Note:** Must include all first names, separated by spaces. - `last_name` **Note:** Must include first and second last names, separated by spaces. - `address` Please note the requirements of spanish addresses [below](#spanish-addresses-requirements). - `line_1` (Street name, Number) - `line_2` (Floor, Door) - `postal_code` - `city` - `country` **Note:** Must be `ES` - `state` 2-digit Spanish province code. [Click here for a full list of Spanish province codes.](https://www.iso.org/obp/ui/#iso:code:3166:ES) - `birth_date` (Format: DD/MM/YYYY) - `birth_city` - `birth_country` [2-digit ISO 3166-2 code](https://unece.org/trade/uncefact/unlocode-country-subdivisions-iso-3166-2) - `birth_province` 2-digit Spanish province code. [Click here for a full list of Spanish province codes.](https://www.iso.org/obp/ui/#iso:code:3166:ES) - `nationality` - `employment_status` Only the following values are allowed: - `SELF_EMPLOYED` - **Note:** If the customer selects `SELF_EMPLOYED`, then you must ask if they want to open a freelancer account. If not, the customer must go through the B2C flow. Additionally, freelancer-only partners should reject all "personal expenses" accounts that are not linked to any professional or business activity. - `email` - `mobile_number` - `branch` **Note:** Must be `ES` - `business_address_line_1` - `business_address_line_2` - `business_postal_code` - `business_city` - `business_country` - `nace_code` Relevant NACE codes up to level 4. - `purpose_of_account_opening` - `main_income_source` - `annual_income_range` - `international_operativity_expectation` - `terms_conditions_signed_at` - `data_terms_signed_at` - `own_economic_interest_signed_at` - `fatca_relevant` - `fatca_crs_confirmed_at` - `self_declared_as_pep` ### Business customers (B2B) note You must pass these data points to Solaris when you [POST Create a business](/api-reference/onboarding/businesses/#tag/Businesses/paths/~1v1~1businesses/post) resource for the customer. Germany - `name` (Business registered name.) - `address` (Business registered address.) - `line_1` - `line_2` - `postal_code` - `city` - `country` - `sector` Note the mapping between sector, country and legal form. - `legal_form` Note the mapping between sector, country and legal form. - `nace_code` Relevant NACE codes up to level 4. - `foundation_date` - `tax_information` - `tax_country` - `tax_confirmation` - `registration_issuer` - `registration_number` - `registration_district` - `registration_type` - `crs_company_type` - `business_purpose` - `terms_conditions_signed_at` - `fatca_relevant` - `fatca_crs_confirmed_at` France - `name` (Business registered name.) - `address` (Business registered address.) - `line_1` - `line_2` - `postal_code` - `city` - `country` **Note:** Must be `FR` - `sector` Note the mapping between sector, country and legal form. - `legal_form` Note the mapping between sector, country and legal form. - `foundation_date` - `tax_information` - `tax_country` - `registration_number` **Note:** For an association, it must be the SIREN number + the RNA number. For overseas territories (Nouvelle Calédonie, Polynésie, Wallis-et-Futuna, Mayotte), it is the TAHITI or RIDE number. - `registration_type` - `crs_company_type` - `business_purpose` - `branch` **Note:** Must be `FR` - `purpose_of_account_opening` - `source_of_funds` - `company_status` - `international_operativity_expectation` - `expected_annual_revenue` - `expected_annual_incoming_funds` - `number_employees` - `terms_conditions_signed_at` - `fatca_relevant` - `fatca_crs_confirmed_at` Italy - `name` `String` (Business registered name.) - `address` (Business registered address.) - `line_1` `String` - `line_2` `String` - `postal_code` `String` **Note:** Must correspond to the selected city. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `city` `String` **Note:** Must correspond to the selected province. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `country` `String(2)` **Note:** Must be `IT`. - `state` `String(2)` 2-digit Italian province code. [Download Province List (CSV)](/downloads/italy-province-list.csv). - `sector` `Enum` Note the mapping between sector, country and legal form. - `legal_form` `Enum` Note the mapping between sector, country and legal form. - `nace_code` `String` Relevant NACE codes up to level 4. - `foundation_date` `ISO 8601` (YYYY-MM-DD) - `tax_information` - `tax_country` `String(2)` - `registration_number` `String` - `registration_type` `Enum` - `crs_company_type` `Enum` - `business_purpose` `String` - `branch` `String(2)` **Note:** Must be `IT`. - `purpose_of_account_opening` `String` - `source_of_funds` `String` - `company_status` `Enum` - `international_operativity_expectation` `String` - `expected_annual_revenue` `Integer` - `expected_annual_incoming_funds` `Integer` - `number_employees` `String` - `vat_number` `String(11)` - `terms_conditions_signed_at` `ISO 8601` (Timestamp) - `fatca_relevant` `Boolean` - `fatca_crs_confirmed_at` `ISO 8601` (Timestamp) Spain - `name` (Business registered name. No abbreviations are allowed.) - `address` (Business registered address.) Please note the requirements of spanish addresses [below](#spanish-addresses-requirements). - `line_1` - `line_2` - `postal_code` - `city` - `country` **Note:** Must be `ES` - `state` 2-digit Spanish province code. [Click here for a full list of Spanish province codes.](https://www.iso.org/obp/ui/#iso:code:3166:ES) - `sector` Note the mapping between sector, country and legal form. - `legal_form` Note the mapping between sector, country and legal form. - `nace_code` Relevant NACE codes up to level 4. - `foundation_date` - `tax_information` - `tax_country` - `registration_number` - `registration_issuer` - `registration_type` - `crs_company_type` - `business_purpose` - `branch` **Note:** Must be `ES` - `purpose_of_account_opening` - `source_of_funds` - `company_status` - `international_operativity_expectation` - `expected_annual_revenue` - `expected_annual_incoming_funds` - `number_employees` - `terms_conditions_signed_at` - `fatca_relevant` - `fatca_crs_confirmed_at` #### Legal representatives note - You must pass these data points to Solaris when you [POST Create a person](/api-reference/onboarding/persons/#tag/Persons/paths/~1v1~1persons/post) resource for the business' legal representative. - After creating a person, a legal representative must be assigned to the business by creating a legal representative resource and also collecting the `type_of_representation`. For more information, check the [API reference](/api-reference/onboarding/businesses/#tag/Business-legal-representatives). Germany - `salutation` **Note:** `MR` for male, `MS` for female, `null` for gender-neutral. - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` - `line_1` - `line_2` - `postal_code` - `city` - `country` - `birth_date` - `birth_city` - `birth_country` - `nationality` - `mobile_number` - `fatca_relevant` - `fatca_crs_confirmed_at` France - `salutation` **Note:** `MR` for male, `MS` for female; no gender-neutral options are possible. - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` - `line_1` - `line_2` - `postal_code` - `city` - `country` **Note:** Must be `FR` - `birth_name` - `birth_date` - `birth_city` - `birth_country` - `birth_post_code` **Note:** Only required for customers born in France. Use the two- or three-digit code corresponding with the *département de naissance* where the customer was born. - `nationality` - `mobile_number` - `fatca_relevant` - `fatca_crs_confirmed_at` - `self_declared_as_pep` Italy Foreign Birth Countries **Crucial:** If the person's `birth_country` is **NOT** Italy (`IT`), you must set the `birth_province` to **`EE`**. - `salutation` `Enum` **Note:** `MR` for male, `MS` for female. - `first_name` `String` (including all middle names as printed on the ID document) - `last_name` `String` (including all middle names as printed on the ID document) - `address` (Italian: *residenza*): The customer's legal residence. Must contain the street name and house number. - `line_1` `String` - `line_2` `String` - `postal_code` `String` **Note:** Must correspond to the selected city. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `city` `String` **Note:** Must correspond to the selected province. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `country` `String(2)` **Note:** Must be `IT`. - `state` `String(2)` 2-digit Italian province code. [Download Province List (CSV)](/downloads/italy-province-list.csv). - `birth_date` `ISO 8601` (YYYY-MM-DD) - `birth_city` `String` **Note:** Must correspond to selected province. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `birth_country` `String(2)` [Download Country List (CSV)](/downloads/italy-country-list.csv). - `birth_province` `String(2)` [Download Province List (CSV)](/downloads/italy-province-list.csv). - `nationality` `String(2)` - `email` `String` - `mobile_number` `String` - `fatca_relevant` `Boolean` - `fatca_crs_confirmed_at` `ISO 8601` (Timestamp) - `self_declared_as_pep` `Boolean` Spain - `first_name` **Note:** Must include all first names, separated by spaces. - `last_name` **Note:** Must include first and second last names, separated by spaces. - `address` Please note the requirements of spanish addresses [below](#spanish-addresses-requirements). - `line_1` (Street name, Number) - `line_2` (Floor, Door) - `postal_code` - `city` - `country` **Note:** Must be `ES` - `state` 2-digit Spanish province code. [Click here for a full list of Spanish province codes.](https://www.iso.org/obp/ui/#iso:code:3166:ES) - `birth_date` - `birth_city` - `birth_country` [2-digit ISO 3166-2 code.](https://unece.org/trade/uncefact/unlocode-country-subdivisions-iso-3166-2) - `birth_province` 2-digit Spanish province code. [Click here for a full list of Spanish province codes.](https://www.iso.org/obp/ui/#iso:code:3166:ES) - `nationality` - `mobile_number` - `fatca_relevant` - `fatca_crs_confirmed_at` - `self_declared_as_pep` #### Authorized persons Authorized persons on a business account are treated similar to a business' legal representative. Please collect the data points required for legal representatives above. note - You must pass these data points to Solaris when you [POST Create a person](/api-reference/onboarding/persons/#tag/Persons/paths/~1v1~1persons/post) resource for the business' authorized person. - After creating a person, an authorized person must be assigned to the business by creating an authorized person resource. For more information, check the [API reference](/api-reference/onboarding/businesses/#tag/Authorized-persons). This step can only be done after the business account is open. #### Beneficial owners note - You must pass these data points to Solaris when you [POST Create a person](/api-reference/onboarding/persons/#tag/Persons/paths/~1v1~1persons/post) resource for the business' beneficial owner. - After creating a person, a beneficial owner must be assigned to the business by creating a beneficial owner resource. For more information, check the [API reference](/api-reference/onboarding/businesses/#tag/Beneficial-Owners), and collecting the `voting_share`. Germany - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` - `line_1` - `line_2` - `postal_code` - `city` - `country` - `birth_date` - `nationality` - `fatca_relevant` - `fatca_crs_confirmed_at` France - `salutation` **Note:** `MR` for male, `MS` for female; no gender-neutral options are possible. - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` - `line_1` - `line_2` - `postal_code` - `city` - `country` - `birth_name` - `birth_date` - `birth_city` - `birth_country` - `birth_post_code` **Note:** Only required for customers born in France. Use the two- or three-digit code corresponding with the *département de naissance* where the customer was born. - `nationality` - `fatca_relevant` - `fatca_crs_confirmed_at` - `self_declared_as_pep` Italy Foreign Birth Countries **Crucial:** If the person's `birth_country` is **NOT** Italy (`IT`), you must set the `birth_province` to **`EE`**. - `salutation` `Enum` **Note:** `MR` for male, `MS` for female. - `first_name` `String` (including all middle names as printed on the ID document) - `last_name` `String` (including all middle names as printed on the ID document) - `address` (Italian: *residenza*): The customer's legal residence. Must contain the street name and house number. - `line_1` `String` - `line_2` `String` - `postal_code` `String` **Note:** Must correspond to the selected city. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `city` `String` **Note:** Must correspond to the selected province. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `country` `String(2)` **Note:** Must be `IT`. - `state` `String(2)` 2-digit Italian province code. [Download Province List (CSV)](/downloads/italy-province-list.csv). - `birth_date` `ISO 8601` (YYYY-MM-DD) - `birth_city` `String` **Note:** Must correspond to selected province. [Download Comune List (CSV)](/downloads/italy-comune-list.csv). - `birth_country` `String(2)` [Download Country List (CSV)](/downloads/italy-country-list.csv). - `birth_province` `String(2)` [Download Province List (CSV)](/downloads/italy-province-list.csv). - `nationality` `String(2)` - `fatca_relevant` `Boolean` - `fatca_crs_confirmed_at` `ISO 8601` (Timestamp) - `self_declared_as_pep` `Boolean` Spain - `first_name` **Note:** Must include all first names, separated by spaces. - `last_name` **Note:** Must include first and second last names, separated by spaces. - `address` Please note the requirements of spanish addresses [below](#spanish-addresses-requirements). - `line_1` (Street name, Number) - `line_2` (Floor, Door) - `postal_code` - `city` - `country` - `state` 2-digit Spanish province code. [Click here for a full list of Spanish province codes.](https://www.iso.org/obp/ui/#iso:code:3166:ES) - `birth_date` - `birth_city` - `birth_country` [2-digit ISO 3166-2 code](https://unece.org/trade/uncefact/unlocode-country-subdivisions-iso-3166-2) - `birth_province` 2-digit Spanish province code. [Click here for a full list of Spanish province codes](https://www.iso.org/obp/ui/#iso:code:3166:ES) - `nationality` - `fatca_relevant` - `fatca_crs_confirmed_at` - `self_declared_as_pep` ## Lending Standalone If you're onboarding customers for lending products, you need to collect two different sets of data points: - Personal data points: Stored in the person or business resource and used for onboarding and the KYC flow. - Credit risk-related data points: Stored in the specific lending product application (e.g., loan application, credit line application, etc.). It includes self-declared information about the customer's income, expenses and existing credit repayments, and used by the credit scorer to determine the customer's credit risk and eligibility. The following diagram describes the resources that you need to create to store customer data for lending products: ![Diagram: Customer data resources for lending](/assets/lending-data-resources.a9bedb2565620870b28733c5568c8263dfdad4fbb831ac51794f93ca69ede3da.865bea7f.svg) The required data points for lending vary per product, customer type, and country. In the following sections, you'll find the customer data points required for each product. ### Fronting Fronting products are offered to B2C (in Germany) and B2B customers (in Germany & France). The following data points are mandatory for onboarding and KYC. Additional credit-risk related fields are also mandatory, but stored in a product-specific resource (e.g., fronting loan application resource). Check the respective [fronting](/guides/lending/fronting/) product guide for more details. #### Retail customers (B2C) - Germany ul li code salutation b Note: code MR for male, code MS for female, code null for gender-neutral. li code first_name (including all middle names as printed on the ID document) li code last_name (including all middle names as printed on the ID document) li code address ul li code line_1 li code line_2 li code postal_code li code city li code country li code birth_date li code birth_city li code birth_country li code nationality li code employment_status li code mobile_number li code terms_conditions_signed_at li code data_terms_signed_at li code own_economic_interest_signed_at #### Business customers (B2B) Germany - `name` (Business registered name.) - `address` (Business registered address.) - `line_1` - `line_2` - `postal_code` - `city` - `country` - `sector` Note the mapping between sector, country and legal form. - `legal_form` Note the mapping between sector, country and legal form. - `nace_code` Relevant NACE codes up to level 4. - `foundation_date` - `tax_information` Possible values for Germany below: - `tax_country` - `tax_confirmation` - `registration_issuer` - `registration_number` - `registration_district` - `registration_type` - `crs_company_type` - `business_purpose` - `balance_sheet_total` - `number_employees` - `terms_conditions_signed_at` France - `name` (Business registered name.) - `address` (Business registered address.) - `line_1` - `line_2` - `postal_code` - `city` - `country` **Note:** Must be `FR` - `sector` Note the mapping between sector, country and legal form. - `legal_form` Note the mapping between sector, country and legal form. - `foundation_date` - `tax_information` Possible values for France below: - `tax_country` - `tax_confirmation` - `registration_issuer` - `registration_number` **Note:** For an association, it must be the SIREN number + the RNA number. For overseas territories (Nouvelle Calédonie, Polynésie, Wallis-et-Futuna, Mayotte), it is the TAHITI or RIDE number. - `crs_company_type` - `business_purpose` - `balance_sheet_total` - `number_employees` - `terms_conditions_signed_at` ##### Legal representatives Germany - `salutation` **Note:** `MR` for male, `MS` for female, `null` for gender-neutral. - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` - `line_1` - `line_2` - `postal_code` - `city` - `country` - `birth_date` - `birth_city` - `birth_country` - `nationality` - `mobile_number` - `terms_conditions_signed_at` - `data_terms_signed_at` France - `salutation` **Note:** `MR` for male, `MS` for female; no gender-neutral options are possible. - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` - `line_1` - `line_2` - `postal_code` - `city` - `country` **Note:** Must be `FR` - `birth_name` - `birth_date` - `birth_city` - `birth_country` - `birth_province` A 2-digit alphanumeric code that indicates the *département* where the customer was born. See the [following table](#french-birth-provinces) for a list of [INSEE codes](https://en.wikipedia.org/wiki/Departments_of_France#Current_departments) and use the mapped values in the **right column** as the values for this property. - `birth_post_code` **Note:** Only required for customers born in France. Use the two- or three-digit code corresponding with the *département de naissance* where the customer was born. - `nationality` - `mobile_number` - `terms_conditions_signed_at` - `data_terms_signed_at` ##### Beneficial owners Germany - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` - `line_1` - `line_2` - `postal_code` - `city` - `country` - `birth_date` - `nationality` France - `first_name` (including all middle names as printed on the ID document) - `last_name` (including all middle names as printed on the ID document) - `address` - `line_1` - `line_2` - `postal_code` - `city` - `country` **Note:** Must be `FR` - `birth_date` - `birth_province` A 2-digit alphanumeric code that indicates the *département* where the customer was born. See the [following table](#french-birth-provinces) for a list of [INSEE codes](https://en.wikipedia.org/wiki/Departments_of_France#Current_departments) and use the mapped values in the **right column** as the values for this property. - `nationality` ### Loans Loans are offered to B2C customers (in Germany). The following data points are mandatory for onboarding and KYC. Additional credit-risk related fields are also mandatory, but stored in a product-specific resource (e.g., loan application resource). Check the respective [loans](/guides/lending/consumer-loans/) product guide for more details. #### Retail customers (B2C) - Germany **Germany** ul li code salutation b Note: code MR for male, code MS for female, code null for gender-neutral. li code first_name (including all middle names as printed on the ID document) li code last_name (including all middle names as printed on the ID document) li code address ul li code line_1 li code line_2 li code postal_code li code city li code country li code birth_date li code birth_city li code birth_country li code nationality li code employment_status li code tax_information ul li code marital_status li code mobile_number li code terms_conditions_signed_at li code data_terms_signed_at li code own_economic_interest_signed_at ### Splitpay Splitpay or credit lines are offered to B2C and freelancer customers (in Germany). The following data points are mandatory for onboarding and KYC. Additional credit-risk related fields are also mandatory, but stored in a product-specific resource (e.g., credit line application resource). Check the respective [Splitpay](/guides/lending/splitpay/) product guide for more details. #### Retail customers (B2C) - Germany ul li code salutation b Note: code MR for male, code MS for female, code null for gender-neutral. li code first_name (including all middle names as printed on the ID document) li code last_name (including all middle names as printed on the ID document) li code address ul li code line_1 li code line_2 li code postal_code li code city li code country li code birth_date li code birth_city li code birth_country li code nationality li code employment_status li code tax_information ul li code marital_status li code mobile_number li code terms_conditions_signed_at li code data_terms_signed_at li code own_economic_interest_signed_at #### Freelancers - Germany ul li code salutation b Note: code MR for male, code MS for female, code null for gender-neutral. li code first_name (including all middle names as printed on the ID document) li code last_name (including all middle names as printed on the ID document) li code address (Home address) ul li code line_1 li code line_2 li code postal_code li code city li code country li code birth_date li code birth_city li code birth_country li code nationality li code employment_status Possible values below: ul li code FREELANCER li code SELF_EMPLOYED li code tax_information ul li code marital_status li code mobile_number li code business_trading_name li code business_address_line_1 li code business_address_line_2 li code business_postal_code li code business_city li code business_country li code business_purpose li code nace_code Relevant NACE codes up to level 4. li code terms_conditions_signed_at li code data_terms_signed_at li code own_economic_interest_signed_at ## KYC Standalone If you are integrating only KYC methods without banking products, collect the data points specified in the [KYC integration guides](/guides/kyc/). ## Important considerations for data collection **Name validation:** Sanitize `first_name` and `last_name` inputs: * Maximum 50 characters. * No leading whitespace. * No symbols or emojis. ### Address validation Your solution must implement address validation to ensure that your system rejects non-existent or wrong address entries before the customer goes through the identification flow. In addition, please note the following best practices: - Select a reliable provider to ensure the accuracy and actuality of data. - Address validation must happen in real-time when the customer enters their address during the onboarding flow. - The system can make auto-complete suggestions to the customer when entering the address. Additionally, it must reject non-existent or wrong entries. - If the address validation fails, the customer can enter a nearby address and proceed with the identification flow. However, the customer must submit a proof of address afterward to customer support, such as a rental contract, electricity bill, or certificate of residence in Germany (i.e., Meldebescheinigung). ### Spanish addresses requirements For Spanish addresses, you must collect the following parameters and store them in dedicated fields in your database: | Parameter | Database field | Notes | | --- | --- | --- | | Type of street | `TYPE_OF_STREET` | (Enumeration, 2 letter code, please refer to the [Type of street table](#type-of-street) for the full list of values). | | Street name | `NAME_OF_STREET` | | | Street number | `STREET_NUMBER` | | | Block | `BLOCK_NUMBER` | (Conditional field. It must be present if the address contains this element or left empty otherwise). | | Floor | `FLOOR_NUMBER` | (Conditional field. It must be present if the address contains this element or left empty otherwise). | | Door | `DOOR_NUMBER` | (Conditional field. It must be present if the address contains this element or left empty otherwise). | | City | `CITY` | | | Postal code | `POSTAL_CODE` | | | Province | `PROVINCE` | (Enumeration, Spanish province code — as defined by [ISO 3166-2](https://www.iso.org/obp/ui/#iso:code:3166:ES) — see the [Province table](#province) for the full list of values). | #### Type of street | Code | Description | Code | Description | | --- | --- | --- | --- | | AL | ALAMEDA,ALDEA | LG | LUGAR | | AP | APARTAMENTO | MC | MERCADO | | AV | AVENIDA | MN | MUNICIPIO | | BL | BLOQUE | MZ | MANZANA | | BO | BARRIO | PB | POBLADO | | CH | CHALET | PG | POLÍGONO | | CL | CALLE | PJ | PASAJE | | CM | CAMINO | PQ | PARQUE | | CO | COLONIA | PR | PROLONGACIÓN | | CR | CARRETERA | PS | PASEO | | CS | CASERÍO | PZ | PLAZA | | CT | CUESTA | RB | RAMBLA | | ED | EDIFICIO | RD | RONDA | | GL | GLORIETA | TR | TRAVESÍA | | GR | GRUPO | UR | URBANIZACIÓN | #### Province | # | Description | # | Description | # | Description | # | Description | | --- | --- | --- | --- | --- | --- | --- | --- | | 01 | Alava | 14 | Córdoba | 27 | Lugo | 40 | Segovia | | 02 | Albacete | 15 | Coruña | 28 | Madrid | 41 | Sevilla | | 03 | Alicante | 16 | Cuenca | 29 | Málaga | 42 | Soria | | 04 | Almería | 17 | Gerona | 30 | Murcia | 43 | Tarragona | | 05 | Avila | 18 | Granada | 31 | Navarra | 44 | Teruel | | 06 | Badajoz | 19 | Guadalajara | 32 | Orense | 45 | Toledo | | 07 | Baleares | 20 | Guipúzcoa | 33 | Oviedo/Asturias | 46 | Valencia | | 08 | Barcelona | 21 | Huelva | 34 | Palencia | 47 | Valladolid | | 09 | Burgos | 22 | Huesca | 35 | Palmas | 48 | Vizcaya | | 10 | Cáceres | 23 | Jaén | 36 | Pontevedra | 49 | Zamora | | 11 | Cádiz | 24 | León | 37 | Salamanca | 50 | Zaragoza | | 12 | Castellón | 25 | Lérida | 38 | Sta. Cruz Tenerife | 51 | Ceuta | | 13 | Ciudad Real | 26 | Rioja. La | 39 | Santander/Cantabria | 52 | Melilla | #### Weekly reporting For Spanish addresses, upload a weekly CSV file containing address data for **every customer with an ES IBAN residing in Spain**. Contact your Partner Manager for the upload method. **File requirements:** - **Format:** `UTF-8` - **Field separator:** `,` (comma) - **Header:** Required - **Filename:** `CustomerSpainAdress_:PartnerUID:_YYYY-MM-DD.csv` - Replace `:PartnerUID:` with your specific Partner UID value. | Column name | Format | Note | | --- | --- | --- | | person_UID | | | | TYPE_OF_STREET | CHAR(2) | Refer to the [Type of street table](#type-of-street) for the full list of values. | | NAME_OF_STREET | CHAR(60) | | | STREET_NUMBER | CHAR(5) | | | BLOCK_NUMBER | CHAR(5) | | | FLOOR_NUMBER | CHAR(5) | | | DOOR_NUMBER | CHAR(5) | | | CITY | CHAR(32) | | | POSTAL_CODE | CHAR(16) | | | PROVINCE | [ISO 3166-2](https://www.iso.org/obp/ui/#iso:code:3166:ES) | Refer to the [Province table](#province) for the full list of values. | #### Note about branching Solaris may restrict the **residency countries** that are allowed for customers onboarding to a specific **branch.** If you attempt to create a customer with a residency country that is not allowed for the given branch, the API will return a `400` error and provide a list of allowed residency countries. Example: ```json { "errors": [ { "id": "24b0e02a-341d-40bc-9e52-0d9f8cc8c6eb", "status": 400, "code": "invalid_model", "title": "Invalid Model", "detail": "country Residency Country is not allowed for this branch,allowed residency country values for branch \"null\" are [\"DE\", \"FR\"]", "source": { "field": "country", "message": "Residency Country is not allowed for this branch,allowed residency country values for branch \"null\" are [\"DE\", \"FR\"]" } } ] } ``` Please contact your Partner Manager for information about which residency countries are allowed for your branch(es). ### Enums #### Annual income range To set the value of `annual_income_range`, you may offer the customer a drop-down list with the following numeric values for each range: | Range | Value | | --- | --- | | `RANGE_1` | < 20000 | | `RANGE_2` | 20000 - 40000 | | `RANGE_3` | 40000 - 60000 | | `RANGE_4` | 60000 - 100000 | | `RANGE_5` | 100000 - 200000 | | `RANGE_6` | 200000 - 400000 | | `RANGE_7` | > 400000 | #### French birth provinces This table maps the INSEE code of each French province with the name to display to your customers in a drop-down menu as well as the value to assign to the `birth_province` property of the `Person`. | `code_departement` - [INSEE code](https://en.wikipedia.org/wiki/Departments_of_France#Current_departments) | `nom_departement` (Dropdown menu for customers) | `birth_province` (value to send to the Solaris API) | | --- | --- | --- | | 1 | Ain | 01 | | 2 | Aisne | 02 | | 3 | Allier | 03 | | 4 | Alpes-de-Haute-Provence | 04 | | 5 | Hautes-Alpes | 05 | | 6 | Alpes-Maritimes | 06 | | 7 | Ardèche | 07 | | 8 | Ardennes | 08 | | 9 | Ariège | 09 | | 10 | Aube | 10 | | 11 | Aude | 11 | | 12 | Aveyron | 12 | | 13 | Bouches-du-Rhône | 13 | | 14 | Calvados | 14 | | 15 | Cantal | 15 | | 16 | Charente | 16 | | 17 | Charente-Maritime | 17 | | 18 | Cher | 18 | | 19 | Corrèze | 19 | | 21 | Côte-d'Or | 21 | | 22 | Côtes-d'Armor | 22 | | 23 | Creuse | 23 | | 24 | Dordogne | 24 | | 25 | Doubs | 25 | | 26 | Drôme | 26 | | 27 | Eure | 27 | | 28 | Eure-et-Loir | 28 | | 29 | Finistère | 29 | | 2A | Corse-du-Sud | 2A | | 2B | Haute-Corse | 2B | | 30 | Gard | 30 | | 31 | Haute-Garonne | 31 | | 32 | Gers | 32 | | 33 | Gironde | 33 | | 34 | Hérault | 34 | | 35 | Ille-et-Vilaine | 35 | | 36 | Indre | 36 | | 37 | Indre-et-Loire | 37 | | 38 | Isère | 38 | | 39 | Jura | 39 | | 40 | Landes | 40 | | 41 | Loir-et-Cher | 41 | | 42 | Loire | 42 | | 43 | Haute-Loire | 43 | | 44 | Loire-Atlantique | 44 | | 45 | Loiret | 45 | | 46 | Lot | 46 | | 47 | Lot-et-Garonne | 47 | | 48 | Lozère | 48 | | 49 | Maine-et-Loire | 49 | | 50 | Manche | 50 | | 51 | Marne | 51 | | 52 | Haute-Marne | 52 | | 53 | Mayenne | 53 | | 54 | Meurthe-et-Moselle | 54 | | 55 | Meuse | 55 | | 56 | Morbihan | 56 | | 57 | Moselle | 57 | | 58 | Nièvre | 58 | | 59 | Nord | 59 | | 60 | Oise | 60 | | 61 | Orne | 61 | | 62 | Pas-de-Calais | 62 | | 63 | Puy-de-Dôme | 63 | | 64 | Pyrénées-Atlantiques | 64 | | 65 | Hautes-Pyrénées | 65 | | 66 | Pyrénées-Orientales | 66 | | 67 | Bas-Rhin | 67 | | 68 | Haut-Rhin | 68 | | 69 | Rhône | 69 | | 70 | Haute-Saône | 70 | | 71 | Saône-et-Loire | 71 | | 72 | Sarthe | 72 | | 73 | Savoie | 73 | | 74 | Haute-Savoie | 74 | | 75 | Paris | 75 | | 76 | Seine-Maritime | 76 | | 77 | Seine-et-Marne | 77 | | 78 | Yvelines | 78 | | 79 | Deux-Sèvres | 79 | | 80 | Somme | 80 | | 81 | Tarn | 81 | | 82 | Tarn-et-Garonne | 82 | | 83 | Var | 83 | | 84 | Vaucluse | 84 | | 85 | Vendée | 85 | | 86 | Vienne | 86 | | 87 | Haute-Vienne | 87 | | 88 | Vosges | 88 | | 89 | Yonne | 89 | | 90 | Territoire de Belfort | 90 | | 91 | Essonne | 91 | | 92 | Hauts-de-Seine | 92 | | 93 | Seine-Saint-Denis | 93 | | 94 | Val-de-Marne | 94 | | 95 | Val-d'Oise | 95 | | 971 | Guadeloupe | 97 | | 972 | Martinique | 97 | | 973 | Guyane | 97 | | 974 | La Réunion | 97 | | 976 | Mayotte | 97 | | 99 | Other (for customers **not** born in France or a French overseas department) | 99 | #### Legal form per country The selected value for the field `tax_country` influences the accepted values for the field `legal_form`. The following lists show the possible values for `legal_form` for each `tax_country`. **Austria (AT)** - `AT_SE` - `AT_OHG` - `AT_KG` - `AT_AG` - `AT_GESMBH` - `AT_EG` - `AT_GBR` - `AT_EV` - `AT_SOLE_PROPRIETORSHIP` - `AT_SELF_EMPLOYED` - `AT_AMT` - `AT_KOR` - `AT_STIFTUNGEN` - `AT_GMBH` - `AT_GMBH_CO_KG` **Belgium (BE)** - `BE_SNC` - `BE_SCS` - `BE_SA` - `BE_SPRL` - `BE_SE` - `BE_SCA` - `BE_SC` - `BE_SCRI` - `BE_SEP` - `BE_SF` - `BE_SPRLU` - `BE_SOLE_PROPRIETORSHIP` - `BE_SELF_EMPLOYED` **Bulgaria (BG)** - `BG_AD` - `BG_OOD` - `BG_KDA` - `BG_KD` - `BG_SD` - `BG_SELF_EMPLOYED` - `BG_SOLE_PROPRIETORSHIP` **Croatia (HR)** - `HR_DD` - `HR_DOO` - `HR_JDOO` - `HR_KD` - `HR_JTD` - `HR_SELF_EMPLOYED` - `HR_SOLE_PROPRIETORSHIP` - `HR_ORTA` **Czech Republic (CZ)** - `CZ_AS` - `CZ_SRO` - `CZ_KS` - `CZ_VOS` - `CZ_DRUZSTVO` - `CZ_FYZICKA_OSOBA` - `CZ_SOLE_PROPRIETORSHIP` - `CZ_SELF_EMPLOYED` **France (FR)** - `FR_AE` - `FR_EI` - `FR_SNC` - `FR_SCS` - `FR_SA` - `FR_SAS` - `FR_SARL` - `FR_SE` - `FR_SCA` - `FR_EURL` - `FR_SC` - `FR_SCOP` - `FR_SELARL` - `FR_SOLE_PROPRIETORSHIP` - `FR_SELF_EMPLOYED` **Germany & Others (Default)** Solaris accepts the following legal forms for companies in Germany and other countries not specified in this list: - `AG` - `EG` - `EK` - `EV` - `NEV` - `GBR` - `GMBH` - `GMBH_CO_KG` - `GMBH_I_GR` - `KG` - `KGAA` - `LTD` - `MUNICIPALITY` - `MUNICIPAL_COMPANY` - `NONE` - `OHG` - `PARTG` - `PRIVATE_PERSON` - `SAVINGS_BANK` - `SE` - `SELF_EMPLOYED` - `SOLE_PROPRIETORSHIP` - `UG` - `UG_I_GR` - `FOREIGN_CORPORATION` - `ADOR` - `AMT` - `KDOR` - `STIFTUNGEN` - `SECOKG` - `AGCOKG` **Hungary (HU)** - `HU_NYRT` - `HU_KFT` - `HU_BT` - `HU_KKT` - `HU_SOLE_PROPRIETORSHIP` - `HU_SELF_EMPLOYED` - `HU_ORTA` **Italy (IT)** - `IT_SE` - `IT_SNC` - `IT_SAS` - `IT_SPA` - `IT_SRL` - `IT_SAPA` - `IT_SCPA` - `IT_SCARL` - `IT_SCOP` - `IT_SS` - `IT_SOLE_PROPRIETORSHIP` - `IT_SELF_EMPLOYED` **Luxembourg (LU)** - `LU_SNC` - `LU_SCS` - `LU_SA` - `LU_SARL` - `LU_SE` - `LU_SCA` - `LU_SCSP` - `LU_SARLS` - `LU_SC` - `LU_SCOP` - `LU_SOLE_PROPRIETORSHIP` - `LU_SELF_EMPLOYED` - `LU_SECA` - `LU_ASBL` - `LU_FON` - `LU_SP` **Poland (PL)** - `PL_SA` - `PL_SPZOO` - `PL_SE` - `PL_SKA` - `PL_SPK` - `PL_SPJ` - `PL_SELF_EMPLOYED` - `PL_OTHER` **Portugal (PT)** - `PT_SNC` - `PT_SC` - `PT_SA` - `PT_LDA` - `PT_SE` - `PT_SUNI` - `PT_EIRL` - `PT_SCIV` - `PT_COP` - `PT_SOLE_PROPRIETORSHIP` - `PT_SELF_EMPLOYED` **Romania (RO)** - `RO_SA` - `RO_SRL` - `RO_SCA` - `RO_SCS` - `RO_SNC` - `RO_SELF_EMPLOYED` - `RO_SOLE_PROPRIETORSHIP` **Serbia (RS)** - `RS_AD` - `RS_DOO` - `RS_KD` - `RS_OD` - `RS_SELF_EMPLOYED` - `RS_SOLE_PROPRIETORSHIP` **Slovenia (SI)** - `SI_DD` - `SI_DOO` - `SI_KDD` - `SI_KD` - `SI_DNO` - `SI_SELF_EMPLOYED` - `SI_SOLE_PROPRIETORSHIP` **Spain (ES)** - `ES_SRC` - `ES_SC` - `ES_SA` - `ES_SAS` - `ES_SRL` - `ES_SE` - `ES_SCA` - `ES_SLNE` - `ES_SAU` - `ES_SLU` - `ES_SPRO` - `ES_SCOP` - `ES_SOLE_PROPRIETORSHIP` - `ES_SELF_EMPLOYED` **Switzerland (CH)** - `CH_DE_AG` - `CH_FR_SA` - `CH_IT_SA` - `CH_DE_GMBH` - `CH_FR_SARL` - `CH_IT_SAGL` - `CH_SE` - `CH_DE_KOMAG` - `CH_FR_SCA` - `CH_IT_SACA` - `CH_DE_KG` - `CH_FR_SCM` - `CH_IT_SAC` - `CH_DE_KIG` - `CH_FR_SNC` - `CH_IT_SNC` - `CH_DE_EG` - `CH_FR_SS` - `CH_IT_SS` - `CH_SELF_EMPLOYED` - `CH_SOLE_PROPRIETORSHIP` - `CH_DE_KMG` **The Netherlands (NL)** - `NL_VOF` - `NL_CV` - `NL_NV` - `NL_BV` - `NL_SE` - `NL_CVOA` - `NL_COPV` - `NL_MTS` - `NL_SOLE_PROPRIETORSHIP` - `NL_SELF_EMPLOYED` - `NL_VERENIGING` - `NL_STICHT` **Turkey (TR)** - `TR_ADI_SIR` - `TR_AS` - `TR_LS` - `TR_KOM_STI` - `TR_KOLL_STI` - `TR_SELF_EMPLOYED` - `TR_SOLE_PROPRIETORSHIP` **United Kingdom (GB)** - `GB_SE` - `GB_PARTNERSHIP` - `GB_LP` - `GB_PLC` - `GB_LTD` - `GB_COPS` - `GB_UAS` - `GB_PRCU` - `GB_PUCU` - `GB_SOLE_PROPRIETORSHIP` - `GB_SELF_EMPLOYED` #### Sector, tax country, and legal form mapping Dependencies exist between the fields `tax_country`, `sector`, and `legal_form`. The value selected for one field determines the accepted values for the next. The following sections outline these dependencies. #### Tax country and sector mapping The selected value for the field `tax_country` influences the accepted values for the field `sector`. The following table gives an overview about the mapping of values between the field `tax_country` and `sector`. | Tax country | Allowed values for sector | | --- | --- | | `DE` | * `ECONOMICALLY_SELF_EMPLOYED` * `ECONOMIC_DEPENDENT` * `GERMAN_BANKS` * `MUNICIPALITY_AND_MUNICIPALITY_ASSOCIATION` * `OTHER_COMPANIES_WORKMAN` * `OTHER_COMPANIES` * `OTHER_PRIVATE_INDIVIDUAL` | | All other countries | * `FOREIGN_COMPANIES` * `FOREIGN_ECONOMIC_DEPENDENT` * `FOREIGN_PRIVATE_INDIVIDUAL` * `FOREIGN_SELF_EMPLOYED_PRIVATE_PERSON` | #### Sector and legal form mapping The selected value for the field `sector` influences the accepted values for the field `legal_form`. The following table gives an overview about the mapping of values between the field `sector` and `legal_form`. | Sector | Allowed values for legal form | | --- | --- | | `OTHER_COMPANIES` | * `AG` * `EG` * `GBR` * `GMBH_CO_KG` * `GMBH_I_GR` * `GMBH` * `KG` * `KGAA` * `LTD` * `OHG` * `PARTG` * `SE` * `UG_I_GR` * `UG` | | `OTHER_COMPANIES_WORKMAN` | * `EK` * `GBR` * `LTD` * `SELF_EMPLOYED` * `SOLE_PROPRIETORSHIP` | | `FOREIGN_COMPANIES` | * `FOREIGN_CORPORATION` * `NONE` | | `GERMAN_BANKS` | * `SAVINGS_BANK` | | `MUNICIPALITY_AND_MUNICIPALITY_ASSOCIATION` | * `MUNICIPALITY` * `MUNICIPAL_COMPANY` | | `ECONOMICALLY_SELF_EMPLOYED` | * `EK` * `GBR` * `SELF_EMPLOYED` * `SOLE_PROPRIETORSHIP` | | `NON_PROFIT_ORGANIZATION` | * `EV` * `NEV` | #### NACE code The Statistical Classification of Economic Activities in the European Community (NACE) is the industry standard classification system used in the European Union. NACE uses four hierarchical levels: - **Level 1:** 21 sections identified by alphabetical letters A to U. - **Level 2:** 88 divisions identified by two-digit numerical codes (01 to 99). - **Level 3:** 272 groups identified by three-digit numerical codes (01.1 to 99.0). - **Level 4:** 629 classes identified by four-digit numerical codes (01.11 to 99.00). The first four digits (the first four levels) are consistent across all European countries. National implementations may introduce additional levels. The fifth digit might vary by country, and suppliers of databases sometimes add further digits. **Example** If the NACE code **A 01.11** (Growing of cereals (except rice), leguminous crops and oil seeds) applies to the business, supply the value as follows: `nace_code = "A 01.11"` **Reference List** Visit the [Eurostat Reference Data](https://showvoc.op.europa.eu/#/datasets/ESTAT_Statistical_Classification_of_Economic_Activities_in_the_European_Community_Rev._2/data) site for the full list of NACE code values required for your implementation. The list is available in multiple languages. **Requirements** - **Mandatory:** NACE codes are required for B2B and freelancer customers in **Germany**, **Italy**, and **Spain**. - **Excluded:** For **France**, NACE codes are not used. The *CODE NAF* system is used instead. Info Using NACE codes replaces the fields `industry` and `industry_key`. ## Mobile number collection The `mobile_number` field is collected and stored in the `person` resource. However, you must separately create and verify the number using the [mobile number endpoints](/api-reference/onboarding/persons/#tag/Person-mobile-numbers). This flow initiates an SMS OTP challenge which the customer uses to verify the number. **Specific use cases:** - **Digital Banking & Cards:** You can combine mobile number verification with the [device binding](/guides/authentication/device-binding/) flow to verify both with a single SMS OTP. * **Note:** This combined flow is only available if you use the **SMS** method for device binding. If you use the **Activation Code (QR)** method, you must verify the mobile number separately before initiating device binding. - **Lending:** If using IDnow for identification, the mobile number is verified during the KYC flow. You do not need to initiate a separate mobile number verification.