# Business Identification Guide (BKYC)

This guide explains how to integrate Solaris' Business Know Your Customer (BKYC) as a **standalone** product, including the mandatory information you must collect from your customers and the necessary endpoints and webhooks you must integrate into your solution.

## Introduction

### Product overview

#### What is BKYC?

Solaris' BKYC solution uses RESTful APIs to perform a series of identification and compliance checks for business customers.

#### How does BKYC work?

The business identification consists of two asynchronous processes:

* **Legal identification:** The Solaris Banking Operations team verifies the completeness and accuracy of the data submitted by the business customer. They ensure that all legal representatives and ultimate beneficial owners are disclosed and linked to the business.
* **Video identification:** All of the business' legal representatives and authorized persons must undergo a video identification session with IDnow to validate their data against their identification documents.


Important
* The business must pass **both** of these checks before the business identification process is successful.
* Only legal representatives and authorized persons must undergo video identification. Ultimate beneficial owners (UBOs) are **exempt** from this requirement.


### Business identification overview

Onboarding a business requires creating multiple resources to represent the legal entity and the natural persons associated with it.

#### Business information

You must manage two distinct streams of data simultaneously:

| Information Stream | Description | Target Resource |
|  --- | --- | --- |
| **Business Information** | Details about the legal entity (e.g., name, registration number, tax info). | The company or organization (`business` resource). |
| **Person Information** | Personal details of the individuals who own, represent, or act for the business. | Legal representatives, beneficial owners, and authorized persons (`person` resource). |


#### Business identification

Verification occurs at two levels:

* **Legal identification:** Solaris verifies the legal entity.
* **Video identification:** The service provider (IDnow) identifies the natural persons. Note that only persons assigned to specific roles require video identification.


#### Business entities and roles

**The Business Resource**

In the API, a `business` represents the legal entity (the company). The `business` is the account holder and owner of the funds. A business must have at least one natural person attached to it.

**The Person Resource**

Natural persons (humans) are represented by `person` resources. They do not own the account but are authorized to act on behalf of the `business`.

**Roles**

You must assign a specific role to every person attached to a business. A single person can hold multiple roles (e.g., a Legal Representative who is also a Beneficial Owner).

The following roles are available:

* **Legal Representative:** Represents the company legally.
* **Ultimate Beneficial Owner (UBO):** Owns or controls the company.
* **Authorized Person:** Authorized to access the account (usually the Legal Representative, but can be others).
* **Signee:** Restricted role for signing documents or viewing info.


Important
You **must** assign at least one **Legal Representative** and one **Ultimate Beneficial Owner** to every business customer.

## System prerequisites

Before starting the business identification process, you must implement the following requirements:

**1. Technical setup**

Set up your environment and get your authentication keys. For instructions, see the [Technical setup guide](/guides/get-started/technical-setup).

**2. Legal and compliance screens**

Build the necessary legal and compliance screens in your sign-up flow to collect your customers' consent to the necessary legal and compliance requirements. The [Legal and compliance screens guide](/guides/get-started/onboarding-requirements/1-legal-compliance-screens) explains how to create these screens and lists their mandatory contents.

Record the customer's consent on each screen as a UTC timestamp (e.g., `2019-01-01T00:00:00Z`). Pass each timestamp in its respective field to Solaris.

* Collect the customer's consent to Solaris' Terms and Conditions and store the timestamp in the `terms_conditions_signed_at` field.
* Collect the customer's consent to data processing and store the timestamp in the `data_terms_signed_at` field.


These fields belong to the `person` resource, which stores all customer data points.

## Webhooks

Solaris recommends subscribing to the following webhook events to better automate your processes. For detailed instructions on implementing Solaris webhooks, check the [webhooks documentation](/api-reference/webhooks/).

- [BENEFICIAL_OWNER](/api-reference/onboarding/webhooks/webhook-events/paths/beneficial_owner/post)
- [BUSINESS_CHANGED](/api-reference/onboarding/webhooks/webhook-events/paths/business_changed/post)
- [BUSINESS_DELETED](/api-reference/onboarding/webhooks/webhook-events/paths/business_deleted/post)
- [BUSINESS_IDENTIFICATION](/api-reference/onboarding/webhooks/webhook-events/paths/business_identification/post)
- [IDENTIFICATION](/api-reference/onboarding/webhooks/webhook-events/paths/identification/post)
- [LEGAL_REPRESENTATIVE](/api-reference/onboarding/webhooks/webhook-events/paths/legal_representative/post)
- [PERSON_CHANGED](/api-reference/onboarding/webhooks/webhook-events/paths/person_changed/post)
- [PERSON_DELETED](/api-reference/onboarding/webhooks/webhook-events/paths/person_deleted/post)
- [PERSON_MOBILE_NUMBER_CREATED](/api-reference/onboarding/webhooks/webhook-events/paths/person_mobile_number_created/post)
- [PERSON_MOBILE_NUMBER_DELETED](/api-reference/onboarding/webhooks/webhook-events/paths/person_mobile_number_deleted/post)


## Integration flow

The following diagram gives an overview of the integration flow for BKYC stand-alone product:


```mermaid
sequenceDiagram
    autonumber
    
    participant F as Your frontend
    participant B as Your backend
    participant S as Solaris
    participant I as IDnow

    Note over F,I: Step 1: Collect business data & create business resource
    F->>B: Enter business's name and details
    B->>S: GET Search for commercial registration
    S-->>B: company's name & country, registration issuer & number
    B->>S: GET Collect business data
    S-->>B: registration issuer & number, business data
    B->>S: POST Create business
    S-->>B: 201 Created (id: business_id)
    B->>S: POST Add Annual Turnover
    S-->>B: 200 Created (value)    

    opt
        Note over F,I: Step 2: Submit business identification number (WIdNr)
        B->>S: POST Create business identification number
        Note right of B: Submit DE...-00001 OR reason_no_number
        S-->>B: 201 Created
    end

    Note over F,I: Step 3: Upload business documents
    F->>B: Upload business documents
    B->>S: POST Upload document
    S-->>B: 201 Created (id: document_id)
    B->>S: POST Upload document
    S-->>B: 201 Created (id: document_id)

    Note over F,I: Step 4: Create Legal Representative(s) (LR)
    F->>B: Enter details of legal rep
    B->>S: POST Create person(s)
    S-->>B: 201 Created (id: person_id)
    B->>S: POST Assign LR role(s)
    S-->>B: 201 Created (id: role_id)
    S-->>B: Webhook: LEGAL_REPRESENTATIVE

    Note over F,I: Step 5: Create Ultimate Beneficial Owner(s) (UBO)
    F->>B: Enter details of beneficial owner
    B->>S: POST Create person(s)
    S-->>B: 201 Created (id: person_id)
    B->>S: POST Assign UBO role(s)
    S-->>B: 201 Created (id: role_id)
    S-->>B: Webhook: BENEFICIAL_OWNER

    Note over F,I: Step 6: Create person and business tax identifications
    F->>B: Provide business tax info
    B->>S: POST Create business tax identification
    S-->>B: 201 Created (id: tax_id)
    S-->>B: Webhook: BUSINESS_TAX_IDENTIFICATION
    
    F->>B: Provide legal rep tax info
    B->>S: POST Create tax identification
    S-->>B: 201 Created (id: tax_id)
    S-->>B: Webhook: PERSON_TAX_IDENTIFICATION
    
    F->>B: Provide beneficial owner tax info
    B->>S: POST Create tax identification
    S-->>B: 201 Created (id: tax_id)

    Note over F,I: Step 7: Trigger business identification (BKYC) 
    F->>B: Redirect legal reps to complete...
    B->>S: POST Create business_identification
    S-->>B: video identification URLs (id: identification_id)
    S-->>B: Webhook: IDENTIFICATION
    F->>I: Complete video identification
    I-->>S: IDnow status updates
    
    alt IDnow Failed
        S-->>B: Webhook: BUSINESS_IDENTIFICATION (failed)
        B-->>F: Rejection notification (abort onboarding)
    else IDnow Successful
        S-->>B: Webhook: BUSINESS_IDENTIFICATION (missing_information)
        B->>S: GET Retrieve business_identification
        B-->>F: Forward questions
        F->>B: Provide answers to compliance questions
        B->>S: GET Retrieve compliance questions
        B->>S: POST Create an answer
        B-->>F: Approval notification (successful BKYC)
    end
```

### Integration steps:

Important
The required data fields you need to collect depend on different factors, such as the business' legal form, country, etc. This guide explains the standard integration process for business customers in Germany for the BKYC standalone solution.

Identify business customers by completing the following steps:

**Business registration**

1. Collect the mandatory business data in your sign-up flow, and create a business resource for your customer by completing [Step 1](#step-1-collect-business-data-and-create-business-resource).
2. Upload the required business documents by completing [Step 2](#step-2-upload-business-documents).


**Business natural person(s) registration**

1. Collect the mandatory data from each of the business' legal representatives, including the consent to the legal and regulatory requirements in your sign-up flow, and create a person resource and assign the legal representative role to this person by completing [Step 3](#step-3-create-legal-representatives).
2. Collect the mandatory data from each of the business' beneficial owner(s) in your sign-up flow, and create a person resource and assign the beneficial owner role to this person by completing [Step 4](#step-4-create-ultimate-beneficial-owners).


## Step 1: Collect business data and create business resource

In this step, you must collect the mandatory data points from the customer in your sign-up flow, including all the timestamps of the business's consent to the [legal and compliance screens](#system-prerequisites).

Afterward, you must pass all the data points to Solaris by creating a business resource to represent your customer.

### API reference

For a complete list of endpoints, properties, and examples related to the `business` resource, visit the following links:

- [Business resource API reference](/api-reference/onboarding/businesses/#tag/Businesses):
  - [POST Create business](/api-reference/onboarding/businesses/#tag/Businesses/paths/~1v1~1businesses/post)
  - [GET Retrieve business](/api-reference/onboarding/businesses/#tag/Businesses/paths/~1v1~1businesses~1%7Bid%7D/get)
  - [PATCH Update business](/api-reference/onboarding/businesses/#tag/Businesses/paths/~1v1~1businesses~1%7Bid%7D/patch)


**Related webhook events**

- [BUSINESS_CHANGED](/api-reference/onboarding/webhooks/webhook-events/paths/business_changed/post)
- [BUSINESS_DELETED](/api-reference/onboarding/webhooks/webhook-events/paths/business_deleted/post)


Important points about data collection
- Review the special considerations for data collection highlighted in the [onboarding requirements guide](/guides/get-started/onboarding-requirements/2-data-collection/#important-considerations-for-data-collection).
- You must submit the information exactly as it appears in official documents.
- When testing in the Sandbox, ensure that each business you create has unique values for `name`, `postal_code`, `legal_form`, and `registration_number` (if provided). If you create over 1000 identical business resources, the API returns a `400` error.


#### POST Create business

This endpoint creates a business resource for your customer. Add the following mandatory data points you've collected from the customer in the request body of this endpoint:

Important
You have to submit the information exactly as it appears in official documents.

**Request URL**


```shell
POST /v1/businesses
```

**Response**

The API call returns a `business` object with a unique `business_id`, which will be used to reference the created `business` in the remaining steps of the onboarding process.

[Click here to view the full API reference.](/api-reference/onboarding/businesses/#tag/Businesses/paths/~1v1~1businesses/post)

### Annual Business Turnover (Mandatory)

To successfully identify a business, annual turnover for the most recent reporting year, must be declared by the business. This is a mandatory requirement based on our regulatory reporting guidelines. Our operations may occasionally request proof of annual turnover depending on the necessity.
For new or recently established businesses, please submit an annual turnover of 0, as these businesses will not have turnover from the previous year.
Please ensure the annual turnover is submitted as a non-negative number.

[Click here to view the full API reference.](/api-reference/onboarding/businesses/#tag/Businesses/paths/~1v1~1businesses~1%7Bid%7D~1annual_turnover/post)

### Automatic data collection (Optional)

Simplify your customers' onboarding process by opting for the automatic data collection feature. With our external service provider, [Business Registry](https://www.kompany.com/search), customers can enter the country and company name, and the remaining business data fields will be automatically filled out.

Info
Automated data collection is an optional step that improves user experience. For more information on this feature and its associated cost, contact your Partner Manager.

#### GET Search for business commercial registration

The customer enters the company's name and country on your frontend and you pass this information using the following endpoint to automatically fetch the business' `registration_issuer` and `registration_number`:

Info
This endpoint might be slow in certain markets.

**Request URL:**


```shell
GET /v1/commercial_registrations/search_by_name?country={{}}&name={{}}
```

**Example response**


```json Example Response
[
    {
        "name": "EWIV für Unternehmensberatung",
        "registration_number": "HRA 201632",
        "registration_issuer": "AMTSGERICHT Lüneburg"
    }
]
```

[Click here to view the full API reference.](/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1search_by_name/get)

#### GET Automatic business data collection

Info
If the previous endpoint cannot retrieve the registration number, you must allow the user to enter it manually.

Use the following endpoint to automatically retrieve the remaining business details after obtaining the `registration_issuer` and `registration_number` from the response of the previous endpoint:

Important
- **Cost:** This endpoint has an associated cost per request. Contact your Partner Manager for more information.
- **Prefix (Germany):** For companies in Germany, you must add `AMTSGERICHT` before the value of the `registration_issuer` (e.g., `AMTSGERICHT MÜNCHEN`).
- **Registration Number:** You must enter the complete registration number, including the letters at the beginning (e.g., `HRB 12345`). Inputting `12345` alone will not work.
- **Registration Issuer:** For the `registration_issuer`, we expect one of the Business Registry offices from the list available in [Appendix V](/guides/get-started/digital-banking/onboard-business/#appendix-v-business-registry-offices). We cannot accept free input as it breaks automation.


**Request URL**:


```shell
GET /v1/commercial_registrations/find?registration_number={{}}&registration_issuer={{}}
```

**Example response**


```json Example Response
{
  "name": "FLOOR 13 GmbH",
  "address": {
    "country": "DE",
    "postal_code": "86919",
    "city": "Utting a.Ammersee",
    "line_1": "Seestraße 9",
    "line_2": ""
  },
  "legal_form": "GMBH",
  "tax_country": "DE",
  "registration_number": "HRB 198673",
  "registration_issuer": "AMTSGERICHT MÜNCHEN",
  "registration_date": "2012-05-09",
  "registry_updated_at": "2015-11-17",
  "legal_representatives": [
    {
      "first_name": "Stefan",
      "last_name": "Schneider"
    }
  ],
  "commercial_registry_industry_key": [
      "66.19.0 - Sonstige mit Finanzdienstleistungen verbundene Tätigkeiten",
      "70.10.9 - Sonstige Verwaltung und Führung von Unternehmen und Betrieben",
      "70.22.0 - Unternehmensberatung",
      "73.11.0 - Werbeagenturen"
  ]
}
```

[Click here to view the full API reference.](/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1find/get)

#### Foreign companies examples

If the company is not registered in Germany, you can still use this service for companies in other countries. The following examples describe how to find the business registration details for a French company.

Info
The field `registration_issuer` is only required for companies in Germany.

**GET Search for business commercial registration (France)**

**Request URL**


```shell
GET v1/commercial_registrations/search_by_name?name=PARISOL&country=FR
```

**Response**


```json Example Response
{
  "name": "PARISOL",
  "registration_number": "513 937359",
  "registration_issuer": null
}
```

**GET Automatic business data collection (France)**

**Request URL**


```shell
GET  /v1/commercial_registrations/find?registration_number=513937359&country=FR
```

**Response**


```json Example Response
{
  "name": "PARISOL",
  "address": {
    "country": "FR",
    "postal_code": null,
    "city": "NANTERRE",
    "line_1": "RUE D ARRAS 18",
    "line_2": ""
  },
  "legal_form": null,
  "tax_country": "FR",
  "registration_number": "513 937359",
  "registration_issuer": null,
  "registration_date": "2009-07-27",
  "registry_updated_at": null,
  "legal_representatives": [
    {
      "first_name": "Stefan",
      "last_name": "Schneider"
    }
  ]
}
```

Check the [appendix](#appendix-iii-testing-samples-for-get-search-for-business-commercial-registration) for testing data for these endpoints.

## Step 2: Submit business identification (WIdNr)

The Business Identification Number or **Wirtschaftsidentifikationsnummer (WIdNr)** is a mandatory regulatory identifier for all business entities registered in Germany, as required under § 139c AO.

Solaris uses this identifier to ensure tax compliance across our Embedded Finance platform. You must submit this data during the initial onboarding phase or update it as soon as the German tax authorities issue the number to the business.

**Technical constraints:**

* **Format validation:** The identifier must strictly follow the pattern `^DE\d{9}-\d{5}$`. For example: `DE123456789-00001`.
* **Conditional submission:** You must provide either a valid `number` OR a `reason_no_number`. Submitting a `null` value for both will result in a `400 Invalid Model` error.
* **Standardized justifications:** If a number is unavailable, use one of the following codes:
  * `NOT_ASSIGNED_YET`: The tax authority has not yet issued a WIdNr to the entity.
  * `NOT_ASSIGNED_BY_COUNTRY`: The entity's jurisdiction does not issue this specific identifier.
  * `OTHER`: Use this for unique edge cases. This selection requires a mandatory `reason_description`. For all other codes, set `reason_description` to `null`.


For implementation details, including request schemas and status codes, refer to the [Business identification number API reference](/api-reference/onboarding/businesses/business-identification-number).

## Step 3: Upload business documents

In this step, you must create document resources for all the required documents you've collected from the business in your sign-up flow and attach each one to the business. These documents are required for the business identification step.

The required documents depend on different factors, such as the business's legal form, sector, etc. Check the [appendix](#appendix-ii-bkyc-required-documents) for a list of required documents per legal form.

You have to make a separate API request for each document and specify its `document_type`. See the [appendix](#document-types) for a list of possible values for this field.

### API reference

For a complete list of endpoints, properties, and examples related to the `business document` resource, visit the following links:

- [Business Documents API Reference Documentation](/api-reference/onboarding/businesses/#tag/Business-documents):
  - [POST Create a business document](/api-reference/onboarding/businesses/#tag/Business-documents/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1documents/post)
  - [GET Retrieve a business document](/api-reference/onboarding/businesses/#tag/Business-documents/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1documents~1%7Bid%7D/get)
  - [GET Download business document](/api-reference/onboarding/businesses/#tag/Business-documents/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1documents~1%7Bid%7D~1file/get)
  - [PATCH Update a business document](/api-reference/onboarding/businesses/#tag/Business-documents/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1documents~1%7Bid%7D/patch)
  - [DELETE Delete a business document](/api-reference/onboarding/businesses/#tag/Business-documents/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1documents~1%7Bid%7D/delete)


#### POST Upload a document

This endpoint uploads a document and links it to the business with the `business_id` specified in the request URL.

Add the following properties to the request body:

- `document_type`: The document type. For a list of possible values, see the API reference.
- `file`: The file to be uploaded.


Info
The request body of this endpoint is a `multipart/form-data` content type. Parameters are transmitted as form-data, not as a raw JSON string.

**Request URL**


```shell
POST /v1/businesses/{business_id}/documents
```

[Click here to view the full API reference](/api-reference/onboarding/businesses/#tag/Business-documents/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1documents/post)

After creating a `business` resource and uploading the required documents, you must create the natural person(s) associated with the business and assign them to their respective roles. The Solaris system represents a natural person using two resources: a `person` resource that contains their data, and a natural person resource associated with the respective business resource.

Important
A business must have at least one natural person attached to it in the capacity of legal representative and/or beneficial owner.

## Step 4: Create Legal Representative(s)

In this step, collect the mandatory data points from the business' legal representative(s) and create a `person` object for each representative. Then, create a `legal_representative` resource and link it to the corresponding `person` object.

### What is a legal representative?

Legal representatives can be natural persons (individuals) or legal entities (businesses) appointed by a company to act on its behalf. The legal representative(s) of a company may be, for instance, its general manager(s) or its managing director(s). The names of a business' legal representatives are usually recorded in the company's commercial register.

Important
- A business must have at least one legal representative.
- If a business has more than one legal representative, you must create and link **all of them** to the `business` object in the Solaris system to prevent delays during the business identification process.


#### Legal representatives as legal entities

A business' legal representative can be a legal entity instead of a natural person. For example, the legal representative of a GbR company could be another GmbH or AG company.

In this case, you must do the following:

1. Collect the business data of the legal entity acting as the legal representative and create a business resource for it.
2. The natural persons who are the legal representatives of **that** legal entity are the ones who must go through the KYC flow.


### Create person resource(s) for each legal representative

For each of the business' legal representatives, you must collect the following mandatory information and call the following API endpoint:

#### POST Create person

This endpoint creates a person resource for the business' legal representative.
Add the following mandatory data points you've collected from the customer in
the request body of this endpoint:

**Mandatory properties:**

- `salutation`
- `first_name`: (including all middle names as printed on the ID document)
- `last_name`: (including all middle names as printed on the ID document)
- `birth_date`
- `birth_city`
- `birth_country` ([ISO 3166-1 alpha-2 codes](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2))
- `nationality` ([ISO 3166-1 alpha-2 codes](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2))
- `address` (Street, Number, City, Postal Code, Country, State).
- `mobile_number` The mobile number will be verified during the identification process.


Important
You have to submit the information exactly as it appears on official documents.

**Request URL**


```shell
POST /v1/persons
```

**Response**

The API returns a person object with a unique `id`. You will use this `id` in subsequent API calls as the value of `person_id` throughout the remainder of this guide.

[Click here to view the full API reference](/api-reference/onboarding/persons/#tag/Persons/paths/~1v1~1persons/post)

### Create legal representative resource(s)

For each person resource you created in the previous step, you must create a `legal_representative` resource and set the value of its `legal_representative` attribute to the `id` of the person resource.

**Optional attributes**

- `type_of_representation`: Indicates whether this legal representative can make decisions alone or jointly with other legal representatives. This attribute is optional. Possible values are `ALONE`, `JOINT`, or `OTHER`.
- `power_of_attorney_confirmed_at`: In case of `JOINT` representation, legal representatives need to confirm the power of attorney's timestamp in the `power_of_attorney_confirmed_at` attribute.


#### POST Create legal representative

This method creates a `legal_representative` resource on the business and binds a `person` to the business as a legal representative.

**Request URL**


```shell
POST /v1/businesses/{business_id}/legal_representatives
```

**Response**

The API returns an object containing the details of the new `legal_representative` resource, including its unique `id`. Note that calling this endpoint successfully will trigger the [LEGAL_REPRESENTATIVE](/api-reference/onboarding/webhooks/webhook-events/paths/legal_representative/post) webhook event.

[Click here to view the full API reference.](/api-reference/onboarding/businesses/#tag/Business-legal-representatives/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1legal_representatives/post)

## Step 5: Create Ultimate Beneficial Owner(s)

In this step:

- Collect the mandatory data points from the business' beneficial owner(s) and create a `person` object for each beneficial owner.
- Create a `beneficial_owner` resource and assign it to its corresponding `person` object.
- Display the definition of the beneficial owner in your UI.


Important
- If a business has more than one beneficial owner, you must create and link **all of them** to the corresponding `business` object to avoid delays during the business identification process.
- A beneficial owner MUST be a natural person and CANNOT be another company.


### What is a Beneficial Owner?

The Beneficial Owners (BO) are **natural** persons who, directly or indirectly, own more than 25% of a company's shares.

According to the German Money Laundering Act (Geldwäschegesetz - GwG), a Beneficial Owner is a natural person who:

- Ultimately owns or controls the business.
- On whose behalf a transaction is ultimately carried out.
- On whose behalf a business relationship is ultimately established.


Important
- The beneficial owner **must** be a **natural** person (individual) and not a legal entity (company). If your business is owned by another company (holding or corporate structure), you need to follow the trail of indirect ownership until you find an individual.
- After a thorough investigation, if no individual owns directly or indirectly more than 25% of the company's voting shares, you must add the legal representative(s) as `fictitious` beneficial owners.
- Beneficial owners don't require video identification.
- For more information about beneficial owners, check the FAQ in the appendices section.


### Beneficial owner legal definition

Ensure that the beneficial owner's full definitions and the checkbox are available to your customers in your sign-up flow.

**Full definition in English**

> The ultimate beneficial owner in the sense of the German Money Laundering Act (Geldwäschegesetz - GwG) is the natural person who ultimately owns or controls the contracting party, or on whose behalf a transaction is ultimately carried out or a business relationship is ultimately established. This particularly includes:
1. In case of legal persons, foundations without legal capacity and, in the case of other companies, any natural person who directly or indirectly holds more than a 25% share of the capital, controls more than 25% of the voting rights or exercises control in any comparable manner (+). Establishing the identity of the beneficial owner can be waived, though, for companies that are listed in an organised market in the EU with in accordance with Sec on 2 para. 5 of the Securities Trading Act or, in case of listed companies from a third country, if they are subject to EU-equivalent transparency requirements regarding voting rights or equivalent international standards;
2. In case of foundations or other legal arrangements with legal capacity (or similar) used to manage or distribute assets or property as trustee (trust management), or through which third parties are instructed with the management or distribution of assets or property, the ultimate beneficial owner is:

- any natural person who is a trustor/settlor, trustee or protector, if applicable
- any natural person who is a member of the board of the foundation,
- any natural person designated as a beneficiary,
- the group of natural persons in whose favour the assets are mainly to be administered or distributed, provided that the natural person who is to be the ultimate beneficial owner of the assets or property has not yet been determined
- any natural person who, by any other means, directly or indirectly exercises control over the asset management or property or the distribution of income.

1. In the event of acting on behalf of another party, the ultimate beneficial owner includes the party upon whose initiative the transaction is performed. If the contracting party acts as a trustee, he also acts on behalf of another party.
(+) Indirect control exists particularly if corresponding shares are held by one or more associations pursuant to Sec on 20 para. 1 GwG which are controlled by a natural person. Control exists particularly if the natural person can directly or indirectly exert a controlling influence on the association pursuant to Sec on 20 para. 1 GwG. Sec on 290 para. 2 to 4 German Commercial Code (Handelsgesetzbuch - HGB) applies mutatis mutandis to the existence of a controlling influence. If, after extensive audits have been performed and without the facts according to Sec on 43 para. 1 GwG applying, no natural person has been identified or if there is any doubt that the identified person is the ultimate beneficial owner, the ultimate beneficial owner shall be the legal representative, managing partner or partner of the contracting party.



**Full definition in German**

> Wirtschaftlich Berechtigter im Sinne des Geldwäschegesetzes, ist die natürliche Person, in deren Eigentum oder unter deren Kontrolle der Vertragspartner letztlich steht, oder auf deren Veranlassung eine Transaktion letztlich durchgeführt oder eine Geschäftsbeziehung letztlich begründet wird. Hierzu zählen insbesondere:
1. Bei juristischen Personen, außerrechtsfähigen Stiftungen und bei sonstigen Gesellschaften jede natürliche Person, welche unmittelbar oder mittelbar mehr als 25 Prozent der Kapitalanteile hält, mehr als 25 Prozent der Stimmrechte kontrolliert oder auf vergleichbare Weise Kontrolle ausübt(2). Auf die Abklärung des wirtschaftlich Berechtigten kann aber verzichtet werden bei Gesellschaften, die innerhalb der EU an einem organisierten Markt im Sinne des § 2 Abs. 5 des Wertpapierhandelsgesetzes notiert sind, oder bei börsennotierten Unternehmen aus einem Drittstaat, wenn sie dem Gemeinschaftsrecht entsprechenden Transparenzanforderungen im Hinblick auf Stimmrechtsanteile oder gleichwertigen internationalen Standards unterliegen;
2. Bei rechtsfähigen Stiftungen und Rechtsgestaltungen, mit denen treuhänderisch Vermögen verwaltet oder verteilt oder die Verwaltung oder Verteilung durch Dritte beauftragt wird, oder diesen vergleichbaren Rechtsformen zählt zu den wirtschaftlich Berechtigten:

- jede natürliche Person, die als Treugeber, Verwalter von Trusts (Trustee) oder Protektor, sofern vorhanden,
- jede natürliche Person, die Mitglied des Vorstands der Stiftung ist,
- jede natürliche Person, die als Begünstigte bestimmt worden ist,
- die Gruppe von natürlichen Personen, zu deren Gunsten das Vermögen hauptsächlich verwaltet oder verteilt werden soll, sofern die natürliche Person, die Begünstigte des verwalteten Vermögens werden soll, noch nicht bestimmt ist,
- jede natürliche Person, die auf sonstige Weise unmittelbar oder mittelbar beherrschenden Einfluss auf die Vermögensverwaltung oder Ertragsverteilung ausübt.

1. Bei Handeln auf Veranlassung zählt zu den wirtschaftlich Berechtigten derjenige, auf dessen Veranlassung die Transaktion durchgeführt wird. Soweit der Vertragspartner als Treuhänder handelt, handelt er ebenfalls auf Veranlassung.



### Create person resource for each beneficial owner

For each of the business' beneficial owners, you must collect the following mandatory information and pass it to Solaris in the request body of the following endpoint:

#### POST Create person

This endpoint creates a person resource for the business' beneficial owner. Add the following mandatory data points you've collected from the customer in the request body of this endpoint:

**Mandatory properties:**

- `salutation`
- `first_name`: (including all middle names as printed on the ID document)
- `last_name`: (including all middle names as printed on the ID document)
- `birth_date`
- `nationality` ([ISO 3166-1 alpha-2 codes](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2))
- `country`: Country of residence. ([ISO 3166-1 alpha-2 codes](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)).


Important
You have to submit the information exactly as it appears on official documents.

**Request example**:


```json
POST /v1/persons
{
    "salutation": "MR",
    "first_name": "Max",
    "last_name": "Mustermann",
    "nationality": "DE",
    "birth_date": "1982-06-20"
}
```

**Response**

The API returns a person object with a unique `id`. You will use this `id` in subsequent API calls as the value of `person_id` throughout the remainder of this guide.

[Click here to view the full API reference](/api-reference/onboarding/persons/#tag/Persons/paths/~1v1~1persons/post)

Additionally, you need to clarify whether there is an additional agreement that allows an external person or business to have a right of ownership. To collect this information, display the following question to your customers as a check box during the sign-up process:

> Are there contracts or agreements concluded outside the company register which reflect a possible ownership based on voting rights distributions?


If the customer checks this box, they must provide supplementary documentation to reflect the ownership. The required documents have the document type: `SHARE_HOLDERS_AGREEMENT`. Additionally, you need to store the response and timestamp of the customer's response and provide it when requested by Solaris.

### Create beneficial owner resource(s)

For each `person` resource you created in the previous step, you must create a `beneficial_owner` resource. You must provide values for the following properties:

- `person_id`: The `id` of the `person` resource you just created.
- `voting_share`
- `fictious`


#### POST Create beneficial owner(s)

This method creates a `beneficial_owner` resource on the business and binds a `person` to the business as a beneficial owner.

**Request example:**


```json
// POST /v1/businesses/{business_id}/beneficial_owners
{
  "person_id": "dc1a6812a14f6cc338cd084208535bcdcper",
  "voting_share": "70.50",
  "fictitious": "false",
  "relationship_to_business": "DOMINANT_INFLUENCE_OVER_SHARE_CAPITAL"
}
```

**Response**

The API call returns an object containing the details of the `beneficial_owner` resource, including its unique `id`. Note that calling this endpoint successfully will trigger the [BENEFICIAL_OWNER](/api-reference/onboarding/webhooks/webhook-events/paths/beneficial_owner/post) webhook event.

[Click here to view the full API reference.](/api-reference/onboarding/businesses/#tag/Beneficial-Owners/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1beneficial_owners/post)

## Step 6: Complete the business identification (BKYC)

In this step, you will trigger the process of verifying the identities of the business legal entity and the legal representative(s) on the business account.

**API reference**

For a complete list of endpoints, properties, and examples related to business identification (BKYC), visit the following links:

- [Business identification API reference](/api-reference/identity/identifications/#tag/Business-identifications):
  - [POST Create business identification](/api-reference/identity/identifications/#tag/Business-identifications/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1identifications/post)
  - [GET Retrieve business identification](/api-reference/identity/identifications/#tag/Business-identifications/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1identifications~1%7Bbusiness_identification_id%7D/get)


**Related webhook events**

- [BUSINESS_IDENTIFICATION](/api-reference/onboarding/webhooks/webhook-events/paths/business_identification/post)
- [IDENTIFICATION](/api-reference/onboarding/webhooks/webhook-events/paths/identification/post)


#### POST Initiate business identification

Call this endpoint to initiate the business identification process, which automatically triggers both the **legal identification** of the business and the **video identification** of applicable natural person(s). Specify the identification `method` in the request body. The default method is `idnow`.

**Request URL**


```shell
POST /v1/businesses/{business_id}/identifications
```

**Response**

Returns an identification object with a unique `id` representing the business identification resource and its overall `status`. Additionally, the payload contains individual identification objects for the video identification sessions of legal representatives, including their respective resource `id`, IDnow `status`, `reference`, and `url` for completing the process.

The payload also provides information on the legal identification process, including its dedicated `legal_identification_status`. Monitor the progress of this process by calling the API, particularly the `legal_identification_missing_information` field, where Solaris highlights compliance questions requiring answers from the business.

[Click here to view the full API reference](/api-reference/identity/identifications/#tag/Business-identifications/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1identifications/post)

### Manual video identification

While the initial business identification process automatically triggers video identification for the known legal representatives, you may need to initiate this process manually. This occurs if new legal representatives are discovered during the legal review or if an initial identification attempt fails.

Trigger video identification manually in the following cases:

1. **New legal representatives:** If the legal review uncovers new representatives, you will receive a [`LEGAL_REPRESENTATIVE`](/api-reference/onboarding/webhooks/webhook-events/paths/legal_representative/post) webhook event containing the new `legal_representative_id`. You must then initiate a video identification with IDnow and redirect the person to the provided URL.
2. **Failed attempts:** If a video identification fails, you must manually trigger a new identification session.


**API reference**

- [Customer identification (KYC) API reference](/api-reference/identity/identifications)


Prerequisites
- This guide focuses on video identification with **IDnow**.
- Ensure you have completed the [IDnow technical prerequisites](/guides/kyc/videoident/#idnow-integration) (e.g., mobile SDKs or web redirects).


**Related webhook events**

- [`IDENTIFICATION`](/api-reference/onboarding/webhooks/webhook-events/paths/identification/post)


### Create identification

Call this endpoint to initialize the identification process. You must specify the method (`idnow`) and the customer's preferred language.

**Required fields:**

- `method`: Set to `idnow`.
- `language`: `EN` or `DE`.
- `proof_of_address_type`: Required if the ID document does not show the address (e.g., Passport).
- `proof_of_address_issued_at`: Required if providing a proof of address (must be < 6 months old).


Creating the resource does **not** start the video call. You must trigger it in the next step.

**Request example**


```json
// POST /v1/persons/{person_id}/identifications
{
  "method": "idnow",
  "language": "DE",
  "proof_of_address_type": "GAS_BILL",
  "proof_of_address_issued_at": "2022-09-21"
}
```

**Response example**

Returns an identification object with status `created`.


```json
{
    "id": "6dc54352d6793a892e0702850d07b831cidt",
    "status": "created",
    "method": "idnow",
    ...
}
```

[Click here to view the full API reference](/api-reference/identity/identifications/#tag/Person-identifications/paths/~1v1~1persons~1%7Bperson_id%7D~1identifications/post).

Custom Flows
The method `idnow_custom` allows for a customized IDnow flow. If you are interested in offering this to your customers, contact your Partner Manager.

### Check supported documents

Before redirecting the customer, check which documents are supported for their country. This avoids user frustration if they attempt to use an unsupported ID.

**Request URL**


```shell
GET /v1/persons/{person_id}/identifications/{id}/supported_documents
```

[Click here to view the full API reference](/api-reference/identity/identifications/#tag/Person-identifications/paths/~1v1~1persons~1%7Bperson_id%7D~1identifications~1%7Bid%7D~1supported_documents/get)

### Trigger identification request

Call this endpoint to generate the required tokens and URLs for the IDnow session.

**Request URL**


```shell
PATCH /v1/persons/{person_id}/identifications/{id}/request
```

**Response example**

The status changes to `pending`. The response contains two critical fields depending on your integration type:

- `url`: Use this for **Web** integrations (redirect the user here). **Valid for 14 days.**
- `reference`: Use this token for **Mobile SDK** (iOS/Android) integrations.



```json
{
    "id": "6dc54352d6793a892e0702850d07b831cidt",
    "reference": "TST-KCCEY",
    "url": "[https://go.test.idnow.de/solarisbankvideoidentsandbox/identifications/](https://go.test.idnow.de/solarisbankvideoidentsandbox/identifications/)...",
    "status": "pending",
    ...
}
```

[Click here to view the full API reference](/api-reference/identity/identifications/#tag/Person-identifications/paths/~1v1~1persons~1%7Bperson_id%7D~1identifications~1%7Bid%7D~1request/patch).

### The IDnow session


```mermaid
flowchart LR
    A[Start] --> B{Integration Type?}
    B -- Web --> C[Redirect User to 'url']
    B -- Mobile SDK --> D[Init SDK with 'reference']
    C --> E[IDnow Session]
    D --> E
    E --> F{Outcome}
    F -- Success --> G[Webhook: IDENTIFICATION]
    F -- Failure --> H[Retry / Abort]
```

Once you redirect the customer (Web) or initialize the SDK (Mobile), the IDnow session begins.

1. **Consent & Setup:** The customer lands on an IDnow-branded page. They must consent to Terms & Conditions and confirm they have a valid ID document ready.
2. **Mobile Verification:** The customer provides a mobile number. The IDnow agent sends an SMS OTP to this number during the call to verify possession.
3. **Video Call:** The agent connects via video to verify the customer's face and ID document live.
4. **Data Update:** If the agent detects missing or incorrect data (e.g., name spelling), they will update the record directly. These changes are automatically reflected in the `person` resource.


### Retrieve identification status

Once the webhook `IDENTIFICATION` signals success, retrieve the final data.

Use the `?include_documents=true` query parameter to download the images of the ID document and the user's face.

**Request URL**


```shell
GET /v1/persons/{person_id}/identifications/{id}
```

[Click here to view the full API reference](/api-reference/identity/identifications/#tag/Person-identifications/paths/~1v1~1persons~1%7Bperson_id%7D~1identifications~1%7Bid%7D/get).

### Other utility endpoints

- [List IDnow attempts](/api-reference/identity/identifications/#tag/Person-identifications/paths/~1v1~1persons~1%7Bperson_id%7D~1identifications~1%7Bid%7D~1idnow_attempts/get) (Audit log of failed/aborted calls)
- [Upload additional documents](/api-reference/onboarding/persons/#tag/Person-documents/paths/~1v1~1persons~1%7Bperson_id%7D~1identifications~1%7Bid%7D~1document_upload/post)


### Compliance questions

During the legal identification process, Solaris' legal and compliance team may require additional information from your customers, including answers to certain compliance questions and/or additional documents.

#### How to identify compliance questions and documents?

1. If Solaris needs further clarification during the business identification, you will receive a notification on the [`BUSINESS_IDENTIFICATION`](/api-reference/onboarding/webhooks/webhook-events/paths/business_identification/post) webhook.
2. Call the [GET Retrieve a business identification](/api-reference/identity/identifications/#tag/Business-identifications/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1identifications~1%7Bbusiness_identification_id%7D/get) endpoint to retrieve the required details.


**Only compliance questions**

If Solaris has compliance questions for the business, the field `legal_identification_missing_information` contains only `COMPLIANCE_QUESTIONS`. In this case, collect answers from the customer on your frontend. We recommend setting **document upload as optional** to allow the customer to add supporting documents if needed.

**Example payload**


```json
{
  "legal_identification_status": "information_required",
  "legal_identification_missing_information": [
    "COMPLIANCE_QUESTIONS"
  ]
}
```

**Both compliance questions & documents**

If Solaris requires both answers to compliance questions and documents, the field `legal_identification_missing_information` contains `COMPLIANCE_QUESTIONS` and a `document_type` (e.g., `FOUNDATION_DOCUMENT`). In this case, collect the answers and the mandatory documents. You must set **document upload as mandatory** on your frontend and submit the document to Solaris using the [POST Create a Business Document endpoint](/api-reference/onboarding/businesses/#tag/Business-documents/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1documents/post).

**Example payload**


```json Example Payload
{
  "legal_identification_status": "information_required",
  "legal_identification_missing_information": [
    "COMPLIANCE_QUESTIONS",
    "FOUNDATION_DOCUMENT"
  ]
}
```

#### How to retrieve compliance questions and provide answers?

If the status indicates missing information, follow this flow to resolve it:


```mermaid
stateDiagram-v2
    direction LR
    [*] --> information_required: Legal Review Paused
    
    state "Resolution Loop" as Resolution {
        information_required --> FetchQuestions: GET /questions
        FetchQuestions --> SubmitAnswer: POST /answers
        SubmitAnswer --> SubmitAnswer: Repeat for all questions
    }

    SubmitAnswer --> pending: PATCH /mark_as_ready
    pending --> [*]: Legal Review Resumes
```

To retrieve the questions and submit answers, use the following endpoints:

#### GET Retrieve compliance questions

To get the compliance questions, call the following endpoint:

**Request URL**


```shell
GET /v1/businesses/{business_id}/identifications/{business_identification_id}/legal_identification/questions
```

**Response example**

The API call returns an object that includes the question(s) with a unique ID and the corresponding text. You must redirect these questions to your customers and retrieve their answers as part of your workflow. Provide a dedicated page for answering all questions separately.


```json Example Payload
{
  "question_id": "ebb463137becc09788dfe21fc066e670qstn",
  "question_text": "Please provide the license for security / guarding services (Bewachungsgewerbe): § 34a GewO",
  "legal_identification_id": "14eb210435e09ab7f6a06c8b9b86ce27lid",
  "business_identification_id": "4c74c804eaea5d2a2d64ef400a27a4d3bid",
  "business_id": "880bbac68a34add190786b9c74f4c82fcbiz",
  "answer_id": null,
  "answer_text": "string",
  "asked_at": "2021-07-16T13:38:06.000Z",
  "answered_at": null
}
```

[Click here to view the full API reference](/api-reference/identity/identifications/#tag/Business-identifications/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1identifications~1%7Bbusiness_identification_id%7D~1legal_identification~1questions/get).

#### Create answers for compliance questions

After receiving the compliance question answers from the customer, call the following endpoint to share them with Solaris. Make a separate API call for each answer.

**Request URL**

Provide the answer in the request body.


```shell
POST /v1/businesses/{business_id}/identifications/{business_identification_id}/legal_identification/questions/{question_id}/answers
```

[Click here to view the full API reference](/api-reference/identity/identifications/#tag/Business-identifications/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1identifications~1%7Bbusiness_identification_id%7D~1legal_identification~1questions~1%7Bquestion_id%7D~1answers/post).

#### PATCH Update business legal identification

Call this method to update the legal identification and mark it as ready to resume the identification process after adding all answers and documents. This endpoint changes the `legal_identification_status` from `information_required` to `pending`.

**Request URL**


```shell
PATCH /v1/businesses/{business_id}/identifications/{id}/legal_identification/mark_as_ready
```

[Click here to view the full API reference](/api-reference/identity/identifications/#tag/Business-identifications/paths/~1v1~1businesses~1%7Bbusiness_id%7D~1identifications~1%7Bbusiness_identification_id%7D~1legal_identification~1mark_as_ready/patch).

### Identification statuses

There are three different statuses related to the business identification process:

**1. Solarisident status**

The Solarisident process includes both legal identification and the video-identification. It's represented on the system with the property `status`, which is automatically set to `created` when creating a business identification.

Successful legal identification and video identification(s) set the status of the business identification (solarisident) to `successful`.

Check the [appendix](#solarisident-status) for more information about the different status values and descriptions.

**2. Legal identification status**

The legal identification process is represented by the `legal_identification_status` property. When a business identification is created, this value is automatically set to `created`.

Check the [appendix](#legal-identification-status) section for more information about the different status values and descriptions.

**Video identification process** The API returns a unique video identification object for each natural person undergoing video identification. This includes the `status` property, which is the IDnow status. The property has an initial value of `pending` and keeps this value as long as the corresponding legal representative has not video-identified with IDnow.

Check the [appendix](#idnow-status) for more information about the different status values and descriptions.

## What's next?

Congratulations! You've successfully completed the business identification process (BKYC).

Check the appendices below for additional information on enums and testing data.

For an overview of Solaris' Customer KYC products, check the [overview](/guides/kyc/) page.

### Useful resources

Check the following links for additional related guides and API reference documentation:

- [Business identification API reference](/api-reference/identity/identifications/#tag/Business-identifications)
- [Customer identification (KYC) API reference](/api-reference/onboarding/persons/#tag/Persons)
- [Video Identification guide](/guides/kyc/videoident)
- [Business Documents API Reference Documentation](/api-reference/onboarding/businesses/#tag/Business-documents)


## Appendix I: Enums

### CRS company type

The field `crs_company_type` is required to collect mandatory tax information and create the business `tax_identification` resource. The following table includes the possible values for this field and their descriptions:

| Enum | Description |
|  --- | --- |
| `FE_REPORTING` | Reporting Financial Institution. |
| `FE_NON_REPORTING` | Non-Reporting Financial Institution. |
| `NFE_ACTIVE_OTHER` | Active NFE (Non-Financial Entity) - A corporation whose shares are regularly traded on at least one recognized stock exchange (or an affiliate), a government entity, an international organization, a central bank, or a legal entity wholly owned by one of these. |
| `NFE_PASSIVE` | Passive NFE - A non-active Non-Financial Entity. |
| `NFE_PASSIVE_INVESTMENT` | Passive NFE (Investment) - An Investment Entity that is a Financial Institution in a jurisdiction not participating in the CRS and is managed by another Financial Institution. |


### Document types

The following table includes the possible values for the field `document_type` and their descriptions.

| Enum | Description |
|  --- | --- |
| `ANNUAL_FINANCIAL_STATEMENT` | A business or company's annual financial statement. |
| `KYC_REPORT` | The KYC report generated after successful customer identification. |
| `ID_DOCUMENT` | A person's identification document, such as a passport or ID card. |
| `SIGNATURE` | A signature sample. |
| `PICTURE` | A picture or scanned document of any other type. |
| `QES_DOCUMENT` | A document related to a Qualified Electronic Signature (QES). |
| `SIGNED_CONTRACT` | A signed contract of any kind. |
| `SIGNED_QES_DOCUMENT` | A document signed by a Qualified Electronic Signature (QES). |
| `REGISTER_APPLICATION` | A document proving the application for registration (Gründungsurkunde), used for companies "in formation". |
| `REGISTER_CHECK` | A register check. |
| `REGISTER_EXTRACT` | A commercial register excerpt or similar document. |
| `FOUNDATION_DOCUMENT` | The foundation document of a company or business. |
| `SCHUFA_COMPACT_REPORT` | A compact SCHUFA report. |
| `SCHUFA_GWG_REPORT` | A GWG (Money Laundering Act) SCHUFA report. |
| `SCHUFA_FULL_REPORT` | A full SCHUFA report about a person. |
| `SCHUFA_SHORT_REPORT` | A short SCHUFA report about a person. |
| `CREDIT_AGENCY_REPORT` | A report issued by a credit agency. |
| `SHARE_HOLDERS_AGREEMENT` | A shareholder agreement. |
| `SHAREHOLDERS_LIST` | A list of shareholders. |
| `TRADING_LICENSE` | A trading license. |
| `TRANSPARENCY_REGISTER_EXTRACT` | An extract from the transparency register. |
| `INVOICE` | An invoice of any kind. |
| `OTHER` | Any other type of document. |
| `VIDEO` | A video of any kind. |
| `VAT_CERTIFICATE` | VAT registration certificate. |


### IDnow status

The following table includes the possible values for the field `status` for the video identification process carried out by IDnow and the related description of each status.

| Status | Description |
|  --- | --- |
| `created` | The identification resource has been created for the customer. |
| `pending` | The identification process has been triggered, and the video identification URL and reference have been generated. Redirect the customer to the URL to complete the identification. |
| `pending_failed` | The identification is currently under review by the provider. You **cannot** offer banking services to the customer at this stage. |
| `successful` | The video identification was successful. The customer can be onboarded. Note that the customer's data might have been updated during the identification session. |
| `aborted` | The customer aborted the identification process. They can retry using the same URL. |
| `canceled` | The provider canceled the video identification. The customer should retry using the same URL. |
| `failed` | The identification was unsuccessful. You **cannot** onboard the customer or offer any banking services to them. |
| `expired` | The identification link has expired (validity period passed). You must create a new identification request. |


IDnow provides a reason whenever the identification has a `canceled` or `aborted` status. No reason is disclosed for the final `failed` status.

### Tax country

The following table includes the possible values for the field `tax_country`.

| Enum | Description |
|  --- | --- |
| `AT` | Austria |
| `BE` | Belgium |
| `CZ` | Czech Republic |
| `DE` | Germany |
| `ES` | Spain |
| `FR` | France |
| `GB` | United Kingdom |
| `IT` | Italy |
| `LU` | Luxembourg |
| `NL` | The Netherlands |
| `PT` | Portugal |


### Sector

The following table includes the possible values for the field `sector`.

| Enum |
|  --- |
| `ECONOMICALLY_SELF_EMPLOYED` |
| `ECONOMIC_DEPENDENT` |
| `FOREIGN_COMPANIES` |
| `FOREIGN_ECONOMIC_DEPENDENT` |
| `FOREIGN_PRIVATE_INDIVIDUAL` |
| `FOREIGN_SELF_EMPLOYED_PRIVATE_PERSON` |
| `GERMAN_BANKS` |
| `MUNICIPALITY_AND_MUNICIPALITY_ASSOCIATION` |
| `OTHER_COMPANIES` |
| `OTHER_COMPANIES_WORKMAN` |
| `OTHER_PRIVATE_INDIVIDUAL` |


### Legal form

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`

 |


### Legal identification status

The following table includes the possible values for the field `legal_identification_status`. This status tracks the progress of the legal checks performed by Solaris on the business entity.

| Status | Description |
|  --- | --- |
| `created` | The legal identification has been initiated and will be conducted shortly. |
| `information_required` | Solaris is missing one or more required documents or information. Check the `legal_identification_missing_information` array to see what is missing. |
| `pending` | The legal review is currently in progress. This status is set after you call the `mark_as_ready` endpoint. |
| `blocked_internally` | The legal identification is put on hold due to additional internal checks. |
| `successful` | The legal identification was completed successfully. |
| `failed` | The legal identification failed. Check the `legal_identification_reason` field for details. |
| `expired` | The legal identification was not completed within the required timeframe (90 days). |


### 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`.

### Solarisident status

The following table includes the possible values for the field `status`, which refers to the overall status of the business identification process (BKYC). This includes the legal identification of the business entity carried out by Solaris and the video identification of the business's natural persons.

| Status | Description |
|  --- | --- |
| `created` | The business identification resource has been created. The legal review and video identification steps will begin shortly. |
| `pending` | The business identification is currently in progress. This may mean Solaris is reviewing the legal documents or waiting for the legal representatives to complete their video identification. |
| `successful` | Both steps of the business identification process (legal review and video identifications) were completed successfully. |
| `failed` | The business identification process failed and will not continue. To understand why, check the status of the `legal_identification` or the individual video identifications. |
| `expired` | The business identification process was not completed within the allowed timeframe (usually 6 months). Either the legal identification or one of the video identifications was not finished on time. |


## Appendix II: BKYC required documents

The following table lists the required documents for identification for each legal form.

Info
For all registered legal forms, customers must input their business data (`registration_number` and `registration_issuer`).

Once the customer enters this data, Solaris automatically retrieves the required company documents, eliminating the need to request them during the onboarding flow.

Important
Inaccurate data (`registration_number` and `registration_issuer`) causes automated retrieval to fail. In this case, you must request documents manually from the customer using the request information and request document endpoints.

Solaris may request further documents during the onboarding process depending on factors such as legal entities acting as beneficial owners, complex business structures, or specific service types.

| Legal Form | Documents required | Document Type | Data can be retrieved by Solaris |
|  --- | --- | --- | --- |
| ADÖR | Register extract | REGISTER_EXTRACT | Yes - Automated |
| ADÖR | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| AG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| AG | "Aktionärsliste" for AG or AG/SE as General Partner | SHAREHOLDER_LIST | No |
| AG | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| AG_CO_KG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| AG_CO_KG | "Aktionärsliste" for AG or AG/SE as General Partner | SHAREHOLDER_LIST | No |
| AG_CO_KG | Articles of Association (Satzung) for AG/SE as General Partner | FOUNDATION_DOCUMENT | No |
| EG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| EG | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| EK | Register extract | REGISTER_EXTRACT | Yes - Automated |
| GbR | Gesellschaftsvertrag (partnership/shareholder agreement) | OTHER or SHAREHOLDER_AGREEMENT | No |
| eGbR | Register extract | REGISTER_EXTRACT | Yes - Automated |
| eGbR | Gesellschaftsvertrag (partnership/shareholder agreement) | OTHER or SHAREHOLDER_AGREEMENT | No |
| Gemeinde | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| gGmbH | Register extract | REGISTER_EXTRACT | Yes - Automated |
| gGmbH | List of Shareholders | SHAREHOLDER_LIST | Yes - Automated |
| GMBH | Register extract | REGISTER_EXTRACT | Yes - Automated |
| GMBH | List of Shareholders | SHAREHOLDER_LIST | Yes - Automated |
| GMBH_CO_KG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| GMBH_CO_KG | Shareholderlist for GmbH/UG General Partner | SHAREHOLDER_LIST | No |
| GMBH_I_GR | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| GMBH_I_GR | Gesellschaftsvertrag (partnership/shareholder agreement) | OTHER or SHAREHOLDER_AGREEMENT | No |
| GMBH_I_GR | Notariell beglaubigte Urkundenrolle/Musterprotokoll | OTHER | No |
| gUG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| gUG | List of Shareholders | SHAREHOLDER_LIST | Yes - Automated |
| KDOR | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| KG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| KGAA | Register extract | REGISTER_EXTRACT | Yes - Automated |
| KGAA | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| LTD | Register extract | REGISTER_EXTRACT | Yes - Automated |
| LTD | List of Shareholders | SHAREHOLDER_LIST | No |
| LTD | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| NEV | List of Shareholders (List of Board members) | SHAREHOLDER_LIST | No |
| NEV | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| OHG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| PARTG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| PARTG | Gesellschaftsvertrag (Partnerschaftsvertrag) | OTHER or SHAREHOLDER_AGREEMENT | No |
| SE | Register extract | REGISTER_EXTRACT | Yes - Automated |
| SE | List of Shareholders | SHAREHOLDER_LIST | No |
| SE_CO_KG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| SE_CO_KG | "Aktionärsliste" for AG or AG/SE as General Partner | SHAREHOLDER_LIST | No |
| SE_CO_KG | Articles of Association (Satzung) for AG/SE as General Partner | FOUNDATION_DOCUMENT | No |
| SE_CO_KG | Gesellschaftsvertrag (partnership/shareholder agreement) | OTHER or SHAREHOLDER_AGREEMENT | No |
| SOLE_PROPRIETORSHIP | Register extract | REGISTER_EXTRACT | No |
| Stiftungen | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| Stiftungen | Trustee Agreement / Stiftungssatzung or Statement signed by the Legal Representatives | OTHER | No |
| UG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| UG | List of Shareholders | SHAREHOLDER_LIST | Yes - Automated |
| UG_CO_KG | Register extract | REGISTER_EXTRACT | Yes - Automated |
| UG_CO_KG | Shareholderlist for GmbH/UG General Partner | SHAREHOLDER_LIST | No |
| UG_CO_KG | Gesellschaftsvertrag (partnership/shareholder agreement) | OTHER or SHAREHOLDER_AGREEMENT | No |
| UG_I_GR | Articles of Association (Satzung) | FOUNDATION_DOCUMENT | No |
| UG_I_GR | Gesellschaftsvertrag (partnership/shareholder agreement) | OTHER or SHAREHOLDER_AGREEMENT | No |
| UG_I_GR | Notariell beglaubigte Urkundenrolle/Musterprotokoll | OTHER | No |


## Appendix III: Testing samples for GET Search for business commercial registration

The following table includes testing samples for the `GET Search for business commercial registration` endpoint, including values for the fields `country`, `registration_number`, `registration_issuer`, and `name`.

| Country | Registration number | Registration issuer | Company name |
|  --- | --- | --- | --- |
| DE | HRA204605 | Oldenburg (Oldenburg) | Stiftung St. Josef-Stift |
| DE | HRB18686 | Bonn | Tekcor 1. V V UG |
| DE | HRA201632 | Lüneburg | EWIV für Unternehmensberatung |
| DE | HRA12751 | Dortmund | Industrial Mercantile International Co. |
| DE | HRB39889 | Berlin (Charlottenburg) | OKV-Ostdeutsche Kommunalversicherung auf Gegenseitigkeit |
| DE | HRA928 | Koblenz | Hans Leininger, Textilgroßhandlung |
| DE | HRA551344 | Ulm | Ravensburger Verkehrs- und Versorgungsbetriebe |
| DE | GnR729 | Landshut | BürgerEnergie Niederbayern eG |
| ES | A31239833 | ---- | BEKO ERROTA SAL |
| ES | A82234113 | ---- | HOTEL BAHIA TROPICAL SA |
| ES | D92943109 | ---- | MICHAEL SCHMIDT Y CIA ENERGIA SOLAR [...] |
| ES | B40547747 | ---- | CACTUS DIGITAL SIGNAGE SOCIEDAD LIMITADA |
| ES | V54433230 | ---- | EL SECRETO DE SUS OJOS AIE |
| ES | B93050672 | ---- | PURAENVIDIA CONSULTING SL |
| ES | G83086751 | ---- | BARCLAYS GESTION FI |
| ES | B57761249 | ---- | GRUPO SA VINYA IBIZA, SOCIEDAD LIMITADA |
| ES | A79102331 | ---- | UNIDAD EDITORIAL SA |
| FR | 304141732 | ---- | ROGER & GALLET |
| FR | 790241467 | ---- | SR SIGNALETIC |
| FR | 807956966 | ---- | MENTON PARC AUTO |
| FR | 321470072 | ---- | GROUP ETUD CONSTR HAB CONSEIL |
| FR | 642050199 | ---- | AUTOMOBILES CITROEN |
| FR | 330034968 | ---- | INNOVATION ANIMATION CULTURE TOURISME |
| FR | 388843930 | ---- | RISKAUDIT IRSN-GRS INTERNATIONAL |
| FR | 332856574 | ---- | JEAN BAPTISTE POLIZZI |
| FR | 702006230 | ---- | SOFILOGIS |
| FR | 521753418 | ---- | HOLMES AND TOOLS |
| IT | BA543920 | ---- | FONDAZIONE NICOLA E VITO ANTONIO RUGGIERI |
| IT | TP131030 | ---- | MAIORANA GIUSEPPE PICCOLO IMPRENDITORE EDILE |
| IT | BA520383 | ---- | SPECIAL CARS SRL |
| IT | BI11627 | ---- | ALLEANZA COOPERATIVA TORINESE*A.C.T. |
| IT | MI152555 | ---- | UNICREDIT SERVICES S.C.P.A |
| IT | BS505351 | ---- | FUNGHI ENERGIA & SALUTE S.R.L. |
| IT | RM1046737 | ---- | CONSORZIO G.T.I. - GRUPPO TECNOLOGIE INTEGRATE IN LIQUIDAZIONE |
| IT | ME239092 | ---- | RUACH S.C. A R.L. - CONSORZIO STABILE |


For non-`DE` companies, the `registration_issuer` field is not necessary.

## Appendix IV: License requirements

The following table lists industries connected with license requirements depending on the services provided by the business customer. Upload the license with `document_type` as `OTHER`.

| Industries that require licenses |
|  --- |
| Alcoholic Beverages (Ausschanklizenz) |
| Brokerage or Consultancy on Financial Investments |
| Waste/ Rubbish Collection, Transportation, Trade, or Brokerage |
| Insurance broker / Insurance advisor |
| Fee-based financial investment advisor |
| Realtor (Immobilienmakler) |
| Real Estate Loan Brokerage (Immobiliardarlehensvermittler) |
| Residential Property Manager (Wohnimmobilienverwalter) |
| Site supervisor (Baubetreuer) |
| Property developer (Bauträger, Bauherr) |
| Drones |
| Tour Operator (Reisevermittler) |
| Labour Leasing (Arbeitnehmerüberlassung) |
| Tax Advisor/ Tax Consultancy (Steuerberater) |
| Taxi Business (Taxenverkehr/ Taxiservice) |
| Provision of Ambulatory (Non-stationary) Care |
| Geriatric Nurses (Altenpflegerinnen und Altenpfleger) |
| Employment Agency (Arbeitsvermittlung) |
| Auctioneer/ auction houses (Auktionator) |
| Gastronomy Establishments Without Alcoholic Beverages |
| Accommodation Establishments (Beherbergungsbetriebe) |
| Loan brokerage (Darlehensvermittler) |
| Wholesale of Medicinal Products |
| Road Haulage (Güterkraftverkehr) |
| Ambulance Services (Krankentransport) |
| Trade Fairs, Exhibitions, Markets |
| Pawn Shops (Pfandleihgewerbe) |
| Podiatrist/ Medical Podiatrist |
| Showman on Funfairs (Reisegewerbe) |
| Pension Advisor (Rentenberater) |
| Pest Control (Schädlingsbekämpfung) |
| Debtor and consumer insolvency advisor |
| Covid Test Centre (Corona Schnelltestzentrum) |
| Payment service providers (Zahlungsdienstleister) |


## Appendix V: Business Registry offices

| Register Court |
|  --- |
| Aachen |
| Altenburg |
| Amberg |
| Ansbach |
| Apolda |
| Arnsberg |
| Arnstadt |
| Arnstadt Zweigstelle Ilmenau |
| Aschaffenburg |
| Augsburg |
| Aurich |
| Bad Hersfeld |
| Bad Homburg v.d.H. |
| Bad Kreuznach |
| Bad Oeynhausen |
| Bad Salzungen |
| Bamberg |
| Bayreuth |
| Berlin (Charlottenburg) |
| Bielefeld |
| Bochum |
| Bonn |
| Braunschweig |
| Bremen |
| Chemnitz |
| Coburg |
| Coesfeld |
| Cottbus |
| Darmstadt |
| Deggendorf |
| Dortmund |
| Dresden |
| Duisburg |
| Düren |
| Düsseldorf |
| Eisenach |
| Erfurt |
| Eschwege |
| Essen |
| Flensburg |
| Frankfurt am Main |
| Frankfurt/Oder |
| Freiburg |
| Friedberg |
| Fritzlar |
| Fulda |
| Fürth |
| Gelsenkirchen |
| Gera |
| Gießen |
| Gotha |
| Göttingen |
| Greiz |
| Gütersloh |
| Hagen |
| Hamburg |
| Hamm |
| Hanau |
| Hannover |
| Heilbad Heiligenstadt |
| Hildburghausen |
| Hildesheim |
| Hof |
| Homburg |
| Ingolstadt |
| Iserlohn |
| Jena |
| Kaiserslautern |
| Kassel |
| Kempten (Allgäu) |
| Kiel |
| Kleve |
| Koblenz |
| Köln |
| Königstein |
| Korbach |
| Krefeld |
| Landau |
| Landshut |
| Langenfeld |
| Lebach |
| Leipzig |
| Lemgo |
| Limburg |
| Lübeck |
| Ludwigshafen a.Rhein (Ludwigshafen) |
| Lüneburg |
| Mainz |
| Mannheim |
| Marburg |
| Meiningen |
| Memmingen |
| Merzig |
| Mönchengladbach |
| Montabaur |
| Mühlhausen |
| München |
| Münster |
| Neubrandenburg |
| Neunkirchen |
| Neuruppin |
| Neuss |
| Nordhausen |
| Nürnberg |
| Offenbach am Main |
| Oldenburg (Oldenburg) |
| Osnabrück |
| Ottweiler |
| Paderborn |
| Passau |
| Pinneberg |
| Pößneck |
| Pößneck Zweigstelle Bad Lobenstein |
| Potsdam |
| Recklinghausen |
| Regensburg |
| Rostock |
| Rudolstadt |
| Saarbrücken |
| Saarlouis |
| Schweinfurt |
| Schwerin |
| Siegburg |
| Siegen |
| Sömmerda |
| Sondershausen |
| Sonneberg |
| Stadthagen |
| Stadtroda |
| Steinfurt |
| Stendal |
| St. Ingbert (St Ingbert) |
| Stralsund |
| Straubing |
| Stuttgart |
| St. Wendel (St Wendel) |
| Suhl |
| Tostedt |
| Traunstein |
| Ulm |
| Völklingen |
| Walsrode |
| Weiden i. d. OPf. |
| Weimar |
| Wetzlar |
| Wiesbaden |
| Wittlich |
| Wuppertal |
| Würzburg |
| Zweibrücken |


## Appendix VI: FAQs

### Legal Representative FAQs

**The company I am about to register is a „Gesellschaft mit beschränkter Haftung“ (GmbH) – who is my legal representative?**

> The easiest and surest way to figure that out is to check your current register excerpt (Handelsregisterauszug). It lists all the official legal representatives you must submit. As a further indication, these people must also be listed in the Imprint of your website (Impressum).


**The Legal Representative has sole representation rights – do I need to add the other legal representatives as well?**

> Yes. Even though this legal representative could conclude the process on behalf of the company alone in the following steps, Solaris needs the complete set of information for regulatory purposes. Therefore, enter the information for all legal representatives associated with the business.


**One of our legal representatives is currently unavailable – do we need to reach them to complete the process?**

> Yes. All legal representative(s) must be identified in a video identification session to complete the business identification process (BKYC).


**Our legal representatives are about to change soon – shall I include the new ones already?**

> No; submit the information as it is currently written in the official register. If you already know that these individuals will change, inform your Onboarding Manager immediately.


**Why do I have to submit all legal representatives here?**

> As a bank, Solaris must keep a record of the companies it works with and verify the provided information. The law stipulates that Solaris must collect this information for all legal representatives.


### Beneficial Owner FAQs

**What is a “Beneficial Owner”?**

> A "Beneficial Owner" is a natural person (an individual) who directly or indirectly owns more than 25% of a legal entity's voting shares. Ultimately, it is the person who benefits from the agreement and holds decision-making power. It can never be another company; Solaris must identify the natural person behind any corporate ownership.


**The company has no beneficial owners – how should I proceed?**

> If a thorough investigation shows that no individual directly or indirectly holds more than 25% of the voting shares, Solaris is required to identify the **legal representatives** as "fictitious" beneficial owners. Enter their information accordingly.


**I don't know the ownership structure of the company – how shall I proceed?**

> The ownership structure is determined in the shareholder agreement (*Gesellschaftsvertrag*), signed when founding the entity. Any changes should be noted in amendments or updates to this contract. Consult these documents to verify ownership.


**Another company owns the company – what shall I do now?**

> Submit the information of the natural person (individual) who owns that shareholder company. If the shareholder is also a company (holding or corporate structure), follow the trail of indirect ownership until you find an individual or the ownership is diluted below 25%.


**What do you mean by direct or indirectly & how do I calculate that?**

> **Direct ownership:** A natural person owns voting shares in the business directly.
**Indirect ownership:** A person owns an entity that, in turn, owns a part of the business. You must also calculate ownership if entities are stacked (multi-level hierarchy) or if one individual holds shares via multiple entities. To determine the indirect quota, multiply the ownership percentages through each level of the hierarchy. If the total exceeds 25%, that person is a beneficial owner.


> **Example:**
**Adello GmbH** is the company being identified.
* **Shareholders of Adello GmbH:**
  * Peter: 30% (Direct BO)
  * Susi: 10%
  * Anne: 10%
  * **Toscana GmbH:** 50%
* **Shareholders of Toscana GmbH:**
  * Hugo: 75%
  * Marie: 25%

**Resulting Beneficial Owners of Adello GmbH:**
* **Peter:** Yes (Direct owner with >25%)
* **Hugo:** Yes (Indirect owner). Calculation: 50% (Toscana's share in Adello) x 75% (Hugo's share in Toscana) = **37.5%**.
* **Marie:** No. Calculation: 50% x 25% = **12.5%** (Below the 25% threshold).



**We have different kinds of shares – which shares are the decisive ones?**

> Use the shares with **voting power**, as the beneficial owner is defined by their ability to control the company's decisions.


**Does the UBO need to do something, for instance, sign something or perform a video identification?**

> No. Submit the information exactly as stated in their official documents (ID card or passport). Beneficial owners do **not** need to perform a video identification or sign documents during this process.