Payroll

Payroll card products are prepaid cards that allow employers to deposit paychecks on employees' payment cards. Payroll cards provide a more convenient, less expensive, and safer alternative to paper checks.

Once a payroll card is issued to an employee, they can use it to make purchases anywhere a debit card is accepted, withdraw cash, and even make automatic bill payments.

This guide provides an overview of creating and setting up a payroll card product in the test environment.

In the Test Environment, you can create a Payroll Card Product from the Highnote Dashboard or with the CreateCardProduct mutation in the Highnote GraphQL API:

Account Holders (Person) must have US-based addresses and identification documents.

Payment Cards are issued to Account Holders. Once you have a Card Product, you must create Account Holders to issue Payment Cards.

For issuing Payment Cards to a Business rather than a Person, see "Create an Account Holder."

Use the following mutation to create a US Person Account Holder:

After creating an account holder, you can open an application to onboard them to your card product. Opening an application triggers identity verification processes. You can participate in the application decisioning process using Collaborative Application Decisioning.

In some cases, additional documents may be required to approve an application. For more information on collecting additional documents, see Request Documents for Application Review.

Use the following mutation to open an application for an account holder:

Financial accounts hold the balance for payment cards. To create a new financial account, pass the id of a verified application.

Financial accounts have an externalId variable field that allows you to tie the Financial account to an entity in your system. If you do not pass in an externalId, Highnote will generate one.

Use the following mutation to issue a financial account for an application:

Once you have created a financial account, you can issue a payment card. By default, all payment cards start as virtual cards. Highnote supports the following types of payment cards:

• Virtual cards
• Physical cards
• Digital wallets

Use the following mutation to issue a virtual card:

By default, all payment cards start as virtual cards. Highnote also supports issuing personalized payment cards to account holders. For more information on issuing physical cards, see Print Physical Cards.

Highnote supports issuing tokenized cards. Account holders can add tokenized cards to digital wallets like Apple and Google Pay. For more information, see Add Cards to Digital Wallets.

Warning: The Highnote test environment lets you explore the platform features and functionality. It is intended for experimenting, building integrations, and training your team.

To ensure the security of your real-world data, please do not use production data in the test environment. Production data includes sensitive information like customer details, financial data, or personally identifiable information (PII).

Use only dummy or test data explicitly created for testing purposes in the test environment.

Using a financialAccountId, you can simulate a non-originated ACH transfer from an external bank account into a Highnote financial account. Non-originated ACH transfers do not require you to connect an external bank account.

To simulate a non-originated ACH transfer in the test environment, use the following mutation:

Prepaid and payroll card have the DIRECT_DEPOSIT feature enabled by default. Financial accounts with the DIRECT_DEPOSIT feature have an associated account and routing number that can be used to transfer funds into the account from outside Highnote.

To display the account and routing number in your website or application, you can fetch them from the API by generating a Client Token and using that token to view the restricted details. The following graphic shows an example of what fetching an account and routing number looks like:

Use the following query to view direct deposit information:

Warning: Highnote recommends using the Card Viewer SDK to securely display payment card data and and reduce PCI non-compliance.

There are two methods for displaying payment card data on your website or application:

• Fetching the data from the Highnote API
• Use the Card Viewer SDK to ensure PCI compliance

To fetch payment card data from the API, use the following query:

After configuring your card product, we recommend simulating transactions. Simulating transactions is useful for testing your card program's configuration and settings.

For more information on simulating transactions, see Simulate Transactions.

After configuring your card product and simulating transactions, you can use the following features to further expand your integration:

• Create authorization controls to manage spending.
• Create a rewards program for your card product.
• Set up notifications to automate your integration.