Onboarding Requirements Overview
Copy for LLM
Copy page as Markdown for LLMs
View as Markdown
Open this page as Markdown
Open in ChatGPT
Get insights from ChatGPT
Open in Claude
Get insights from Claude
Connect to Cursor
Install MCP server on Cursor
Connect to VS Code
Install MCP server on VS Code

Introduction

Use Solaris APIs to offer banking products to retail, freelance, and business customers across supported countries.

This guide outlines the onboarding requirements based on your customer type, country, and product selection.

This guide provides a general overview. The Solaris team will provide the specific requirements for your banking use case during implementation.

Solaris offers banking products to the following customer types:

Solaris provides products to customers outside of Germany through two regulatory frameworks:

Passporting: Solaris provides services to customers in the European Economic Area (EEA) under the supervision of BaFin (German Federal Financial Supervisory Authority).
Branching: Solaris provides services via a local branch, subject to the local financial supervisory authority.

Solaris currently operates branches in:

Three key factors determine the onboarding flow and compliance checks:

Product: Higher-risk products (like Digital Banking or Lending) require stricter checks than lower-risk products.
Customer type: Requirements differ for retail customers (B2C), freelancers, and businesses (B2B).
Country: Local jurisdiction dictates specific legal and compliance obligations.

Diagram: Onboarding requirements

These factors influence:

Legal requirements: The specific agreements and consent screens required.
Data collection: The data points you must collect during sign-up.
KYC method: The identification methods available for the specific risk level and location.

The onboarding flow follows industry-standard banking procedures.

Diagram: Onboarding process

Step	Description
Legal and regulatory requirements	Collect customer consent for necessary agreements and declarations.
Data collection	Capture required customer data points in your sign-up flow.
Tax information	Collect tax residency and ID information (mandatory for specific use cases).
Document collection	Upload documents required for KYC, credit risk, or scoring processes.
Know Your Customer (KYC)	Verify the customer's identity using a supported identification method.
Product-specific requirements	Fulfill requirements specific to the product (e.g., credit checks for Lending).
Mandatory features	Integrate essential add-ons required for go-live.