Commercial Debit

A Commercial Debit Card Product allows you to issue debit cards funded from an associated Financial Account held by a business. These Payment Cards may be Virtual Cards available on your app or website, Physical Cards mailed to your Business Account Holder, or both.

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

Once you've created your Commercial Card Product, you create a Business Account Holder. Account Holders may be issued Payment Cards from multiple Card Products.

Once you have created an Account Holder, you can open an Application to onboard them to your Card Product.

Opening an Application triggers the identity verification checks (KYC) necessary for your Card Product. These checks must pass in order to onboard the Account Holder. To create the Application you will need the cardProductId and primaryAuthorizedPersonId.

When the Application is opened, it will be in a PENDING state. This means the Application is being reviewed and the appropriate KYC checks are running against the Account Holder. You can only have one Application open at a time for a given Card Product and Account Holder.

Capturing Consent

Before an Application is submitted, the required terms and conditions and relevant disclosures for the Card Product (e.g. the Cardholder Agreement) must be presented and agreed to by the Account Holder. An Account Holder’s consent must be captured before opening an Application and include who is consenting, primaryAuthorizedPerson, what they are consenting to, cardProductID, and when they consented, consentTimestamp.

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

Financial Accounts with the DIRECT_DEPOSIT feature have an associated account and routing number to be used for funds movements originated outside of Highnote.

To display the account and routing number, you can fetch them from the API by generating a Client Token and using that token to view the restricted details.

With a Financial Account ID, you can simulate a Non-Originated ACH Transfer from an external bank account into a Highnote Financial Account.

Non-Originated Transfers do not require you to connect an external bank account.

Once you have created and funded a Financial Account, you can issue a Payment Card. All Payment Cards start as a virtual card, and can later be ordered as a physical card.

You may only submit one order for a given Payment Card. If the order is canceled or fails, you may try again for the same card. However, if an order is successful and you need another Physical Card, you will need to issue a new Payment Card.

Once you have issued a Payment Card you can create an order for a Physical Card. When ordering a Physical Card, you can ship to the Account Holder's address on file or specify a different shipping address.

Physical Card orders require:

• Card Personalization Details
• Shipping Address
• Requested Ship Date
• Shipping Method and Signature Requirements

Use the following mutation to create a Physical Card order:

Selecting the number or cvv fields requires that you are PCI compliant.

Highnote recommends using the Card Viewer SDK to securely display payment card data and and reduce PCI burden.

To display the primary account number (PAN) and CVV to users, you can fetch them from the API by adding number and cvv to the selection set

Once you've completed the basics of setting up your card product, you can expand and test your integration further:

• Simulate Transactions in the Test Environment to ensure your integration works
• Create Spend Rules to control the way your cards can be used
• Setup Notifications to automate your integration