Consumer Prepaid

Consumer Prepaid Card Products allow consumers to cover personal expenses, make in-person or online purchases, and even access cash using an ATM. A prepaid card resembles a debit card but holds a finite amount of funds and is not directly tied to a bank account.

A Consumer Prepaid Card Product allows you to issue prepaid cards funded from an underlying bank account held by an individual consumer. You can transfer funds into a Payment Card’s financial account, and the money will be ready to spend on the card when needed. These Payment Cards may be Virtual Cards available on your app or website; Physical Cards mailed to your Account Holder, or both.

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

Consumer Prepaid Card Products issue payment cards to Person Account Holders. You can create a Person Account Holder from the Highnote Dashboard and GraphQL API.

Your Account Holders may hold 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.

Once you have an approved Application, you can Issue a Funding Financial Account for an Account Holder.

Financial Accounts with the DIRECT_DEPOSIT feature have an associated account and routing number 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.

Use the following query to view direct deposit information:

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.

Use the following mutation to simulate a Non-Originated ACH transfer:

Once you've created a Funding Financial Account, you can create a Financial Account for the Payment Card and move funds between the accounts.

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.

To fund an Account Holder's Payment Card Financial Account, you can move funds from your Product Funding Account to a Financial Account. For input variables, use the following account IDs:

• toFinancialAccountId: Account Holder's Payment Card Financial Account ID
• fromFinancialAccountId: Product Funding Account ID

Use the following mutation to initiate a transfer from your Product Funding Account:

To unload funds from a Financial Account, you can transfer funds a source Financial Account to your Product Funding Account balance using the following mutation:

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