Identities overview
Identities represent the customers who use the financial services you offer within your application. A corporate identity represents a business entity, while a consumer identity represents an individual person.
Due diligence
You need to onboard your customers onto Weavr before they can use any financial services.
You can embed an identity verification process. For consumer identities, it is called Know Your Customer (KYCKYC Know Your Customer - the identity verification process for consumer identities. This process allows you to seamlessly and securely verify your user's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers.) and for corporate identities – Know Your Business (KYBKYB Know Your Business - the identity verification process for corporate identities. This process allows you to seamlessly and securely verify your business customer's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers.). This process lets you seamlessly and securely verify your user’s identity and all you need on your end is just a few lines of code. Weavr asks your users to submit the necessary information and documentation so that they can get approved by our financial providers.
Supported Countries
We support onboarding corporates and consumers residing in the following countries:
| Austria | Belgium | Bulgaria | Croatia |
|---|---|---|---|
| Cyprus | Czech Republic | Denmark | Estonia |
| Finland | France | Germany | Greece |
| Hungary | Iceland | Ireland | Italy |
| Latvia | Liechtenstein | Lithuania | Luxembourg |
| Malta | Netherlands | Norway | Poland |
| Portugal | Romania | Slovakia | Slovenia |
| Spain | Sweden | United Kingdom |
Users
We support 2 types of users:
- Root userRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user. is the individual who is creating the identity. In case of corporate identities the root userRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user. needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company while for consumer identities, the root userRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user. is the owner of the identity.
- Authorised user is an individual that has been invited by the root userRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user. to manage the identity's instruments and transactions.
Every identity must always have one root userRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user., and optionally can have an unlimited number of authorised users.
Application-specific permissions to limit what each user can view and do need to be implemented in your application.