Skip to content
Last updated

B/KYC identification

Identify every customer using a KYC method approved by Solaris. The correct method depends on the product risk, branch, and customer type.

Identification types

Retail (B2C) and Freelancers: Identify the individual using a single KYC method (e.g., VideoIdent or BankIdent).

Business (B2B): The BKYC flow requires two parallel identification streams:

  1. Business identification: Solaris internal teams verify the legal entity.
  2. Person identification: You verify the natural persons associated with the business using a standard KYC method.

Contract Signing (QES): For products requiring a contract (e.g., accounts in Italy/France or loans), the customer signs the documents using a Qualified Electronic Signature (QES). This step is integrated directly into the identification flow.


KYC methods overview

This overview illustrates the standard identification methods supported for each product, customer type, and branch.

Table: KYC methods overview for DiBa & Cards

Digital Banking & Cards

Checking accounts:

  • VideoIdent (IDnow): Suitable for all customer types with supported ID documents.
  • BankIdent Plus: Suitable for B2C customers with a German IBAN.

Credit Cards:

  • Charge cards: VideoIdent (all customers) or BankIdent (customers with a German IBAN).
  • Revolving cards (B2C): BankIdent + QES.

Decoupled Cards:

  • BankIdent: B2C customers with a German IBAN.
  • VideoIdent: B2C customers with supported ID documents.

Lending

Lending products primarily use VideoIdent (IDnow) combined with QES for signing loan contracts.


Document validity (Italy & Spain)

To comply with regulatory requirements, Solaris must keep copies of valid identification documents for active customers in its Italy and Spain branches. This requirement applies to the following customer segments:

  • Retail customers
  • Freelancers & Sole proprietors
  • Businesses' legal representatives
  • Authorized persons on a business or a retail account

How will you be notified of the expiry of ID documents?

In Italy and Spain, Solaris stores the expiry date of a customer's identification document and calculates a follow-up date to notify you before it expires. You'll receive a webhook notification on the event POTENTIAL_ACCOUNT_BLOCKING 30 days before the expiry date, and then every 30 days until 90 days after the expiry.

The webhook payload includes the blocking_date, which is the date by which the account will be blocked if the customer has not identified again with a valid ID document, and the reason for the account blocking is set to IDENTIFICATION_DOCUMENT_EXPIRED.

What should you do?

After receiving a notification on the POTENTIAL_ACCOUNT_BLOCKING webhook event, you should take the following steps:

  1. Create a new identification resource for the customer and specify the identification method using the POST Create an identification.
  2. Request the identification for the customer by calling PATCH Request an identification.
  3. Notify the customer that they must complete the KYC flow with their new valid ID document.
  4. After successful KYC, Solaris will store the expiry date of the new ID document and calculates a new follow-up date.

If the customer did not identify with a valid ID document within 90 days after the expiry date, the customer's account will be blocked with the reason IDENTIFICATION_DOCUMENT_EXPIRED. If a new ID document is submitted, the account will be unblocked.

Which KYC method to use?

For the re-identification due to expired ID documents, you can choose between the following methods:

Customer Due Diligence (CDD)

Solaris performs regular risk and vetting checks on all customers.

  • Digital Banking & Cards: Mandatory for all customer types and branches. Customers must pass screening before onboarding.
  • Lending: Currently not mandatory.

See the CDD guide for details.


FATCA relevance

In compliance with the Foreign Account Tax Compliance Act (FATCA), Solaris cannot onboard customers liable for US taxes.

  • Digital Banking & Cards: Mandatory check. Verify customers are not FATCA-relevant before offering banking solutions.
  • Lending & Standalone KYC: Not mandatory.