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
There are two 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 creates the identity. For 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. must 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 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. 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 always assigned the Admin role and has full access to 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. (or another user with the Access Management role) to act on the identity's behalf.
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.
Roles
Weavr provides a set of pre-configured roles that can be assigned to authorised users to control their level of access. The available roles are:
- Card AssigneeCard Assignee The person that a card is assigned to and who will use the card. For consumers, the card owner and card assignee are the same person. For corporates, the card assignee and card owner are different entities - the corporate is the card owner and the person using the card is the card assignee. Card assignees must be created as Authorised Users. -- for users who need to access and spend on their own assigned card(s) only.
- Cards Management Role -- for users responsible for managing a card programmeProgramme A programme represents your application within Weavr. Everything you create — Identities, Instruments, Transactions — sits beneath a Programme. When you register as an Embedder, you receive a Programme in the Sandbox and, once approved, one in Production..
- Funds Management Role -- for users who need to manage fund inflows or outflows.
- Access Management Role -- for users responsible for creating and managing other users.
- Admin -- full access to all operations, combining all of the preceding roles.
Multiple roles can be assigned to a single user, and 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. always has the Admin role. Read the user roles page for detailed permissions per role.
Role-based access control is an optional feature. If you prefer to manage access restrictions within your own system, users can be granted full access via the Admin role.