Give a user access to another corporate

An existing user can access more than one corporate without needing separate credentials. Link them to the second corporate instead of creating a new user or sending an invitation.

Prerequisites

• The user already has access to another corporate in the same profileProfile A template defining the configuration for one type of object - corporate identity, consumer identity, managed account, managed card, transfer, or outgoing wire transfer. When you create one of these objects you reference its Profile ID, which tells Weavr which limits, currencies, supported countries, branding, and fees to apply. Your programme ships with one or more Profile IDs per supported object type..
• You have the user's ID.
• The corporate to which you are giving access has completed 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..
• An Admin or Access Management user of that corporate has a stepped-up Access Token.

Link the user

Call the link-user API, authenticated with the stepped-up Access Token for the corporate that will receive the user:

POST/users/{user_id}/linkOpen API reference →

/users/987654321/link

The link takes effect immediately. No invitation is sent, and the user keeps their existing password and authentication factors.

Use the right flow

Use Add a user for someone who does not already have a Weavr user. If the API returns CREDENTIAL_NOT_FOUND, create and invite the user instead.

Handle the user's next login

After the user is linked to a second corporate, their next login returns an Auth Token instead of an Access Token. List the corporatesCorporates Business entities that can be onboarded as identities on Weavr. Corporate identities represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees. available to the user, let them select one, then exchange the Auth Token for an Access Token scoped to that corporate.

See Verify users for the credential-verification flow and End-user authentication for the API sequence.

Resolve common conflicts

USER_ALREADY_LINKED_TO_IDENTITY means the user already has access, so no further action is needed. PROFILE_MISMATCH, KYB_MISSING, and EMAIL_DOMAIN_NOT_ALLOWED mean the user or corporate is not eligible for linking.