Home / Issuing / Onboard Accounts

Onboard Authorized Users (deprecated)

Overview

Highnote released a simplified model for Authorized Users that applies to both consumer and commercial card products. Going forward, all authorized users are Person account holder objects, even commercial products where the primary account holder is a Business account holder object.

An authorized user of a commercial card product is a cardholder with access to a card product, but with fewer permissions than the primary account holder.

On the Highnote platform, each authorized user is recognized as a separate entity. For example, a business account holder can issue cards to select employees as authorized users. Each employee is assigned a unique ID, regardless of whether they are associated with multiple cards under the same account, or have a shared user profile in your system.

The following graphic shows the relationship of a single card product with an authorized user who has multiple applications and payment cards:

Authorized Users.png

Prerequisites

  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.

Categorized spending

Categorized spending is one use case for an authorized user of a commercial card. This use case requires the API to pass specific financial account IDs. For simpler use cases in the Dashboard, see Authorized users in the Support docs.

To configure an authorized user for categorized spending of a commercial card:

  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.

In this use case, each authorized user must be onboarded individually. If authorized users need access to multiple spending categories, they must apply to each financial account separately. One authorized user account may have several applications, financial accounts, and cards; each representing a different spend category.

Onboard an authorized user

Note: Authorized users must be 18 or older and 100 or younger (to combat fraud and elder financial abuse); and their first names must be at least one character.

Client tokens can be used when onboarding authorized users for enhanced security.

Before adding authorized 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, the following inputs are required:

  • name
  • email
  • phoneNumber
  • billingAddress
  • dateOfBirth

Open application for authorized user

After creating an authorized user, you must open an authorized user application and present your cardholder agreements. You can subscribe to notification events for updates on the application status.

Use the following mutation to open an authorized user application:

Issue payment card

Note: 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.

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

Use the following query to issue a payment card to an authorized user:

Find authorized user

Once an authorized user has been created, you can find authorized details, including associated applications and payment cards. Use the following query to find authorized user details:

Provide Feedback

Was this content helpful?