Onboard Authorized Users

1. A Highnote Account
2. An API Key, the API Explorer or the Dashboard
3. An Account Holder with approved Application
4. Authorized users feature enabled by the Highnote Support team. Contact support@highnote.com to have this feature enabled.

At this time, only Commercial Card Products support Authorized Users.

Authorized users provide a way for you to add cardholders who don't require the same access level as the primary account holder. On the Highnote platform, each authorized user is recognized as a separate entity. This means, for instance, that a business account holder can issue cards to various employees as authorized users. Regardless of whether these employees are associated with multiple cards under the same account or have a shared user profile in your system, each one is assigned a unique ID.

Authorized users have fewer capabilities than an account holder. The capability differences between authorized users and account holders provide structure for many use cases. For more information, see Use Cases.

The following table outlines the difference in capabilities between authorized users and account holders:

Access	Authorized Users	Account Holders
Get a card
Spend on a card
Provision a card to a digital wallet
Receive OTP for digital wallet verification
Activate or suspend a card
Use personal address for Address Verification Systems (AVS)		✖️
Use business address for Address Verification Systems (AVS)	✖️
Open financial account	✖️
Move funds	✖️

There are several benefits to enabling authorized users for your card product:

• Provides access to funds without permission to manage money movement or create new accounts.
• Authorized users can be issued cards with their name and address, ensuring seamless Name and Address Verification Service (AVS) experiences.
• Account holders can allocate funds for authorized users.
• Authorized users can have their own email address and/or phone number associated with their card, ensuring seamless digital wallet setup.

The following use cases are commonly used for authorized users:

• Business cards with employees as authorized users
• Fleet cards with drivers as authorized users
• Consumer cards with family members or spouses as authorized users

Another use case for authorized users involves commercial cards with categorized spending. Configure this use case in the following way:

1. Create individual financial accounts using a business account holder's application. Each financial account represents a different spending category. For example, you might have separate financial accounts for gas, groceries, and office supplies.
2. Onboard authorized users under the business account holder.
3. Open an application for the authorized user and pass the financialAccountId of the spend category financial account.
4. Issue cards to authorized users.

Each authorized user must be onboarded individually. If an authorized user needs access to multiple spending categories, they must apply to each financial account separately. This means that one authorized user account may have several applications, financial accounts, and cards, with each representing a different spend category.

Authorized users must be at least 18 years old, and their first names must be at least one character.

Client tokens can be used when onboarding authorized users for enhanced security. For more information, see Client Tokens.

Before adding authorized users, also known as auth users, you must onboard an account holder with an approved application. When creating a new authorized user, you will pass the accountHolderId to establish the relationship with the account holder.

For extra security, you can generate a Client Token and tokenize authorized user information on your client before passing the data to Highnote.

When using the following mutation to create an authorized user, name, email, phoneNumber, billingAddress, and dateOfBirth are required inputs:

After creating an authorized user, you must open an application and present your compliance agreements to complete onboarding. You can subscribe to Notification Events for updates on the Application status.

The following query represents an example of creating an authorized user application:

Once an authorized user has an approved application, you can issue a payment card to the authorized user.

If you choose to issue physical cards, during Card Personalization, the authorized user's first and last name are required for line 1. For more information on issuing physical cards, see the Print Physical Cards guide.

The following query represents an example of issuing a payment card for an authorized user:

Once an authorized user has been created, you can find authorized details, including associated applications and payment cards. The following query represents an example of finding authorized user details: