Commercial Charge

Your card product will define the required application fields for credit risk underwriting and identity verification. These checks must pass in order to onboard commercial charge account holders.

Commercial charge card products allow you to issue lines of credit to your customers. Commercial charge cards do not charge interest and require your customers to pay their statement balance in full by the due date of each billing cycle.

There are two types of commercial charge card products you can offer using the Highnote platform:

• Unsecured: Offer a line of credit without requiring collateral. This option requires you or a debt facility to provide sufficient capital based on the lines of credit extended to your cardholders.
• Secured: Offer a line of credit backed by cardholder-funded collateral.

In the test environment, you can create a commercial charge card product from the Highnote dashboard or with the following createCardProduct mutation using the Highnote API. When creating your card product, use COMMERCIAL_CREDIT_PAY_IN_FULL as the vertical input variable:

You can create a secured commercial charge card product using Highnote's secured deposit feature. This feature can be enabled for your card product by the Highnote team and will require cardholders to provide collateral to back their line of credit.

For more information on enabling this feature and integrating it into your card product, see Create Secured Deposit Offer.

Your product funding account allocates credit lines to your account holder's financial accounts. In the test environment, you can simulate a deposit into your product funding account. Simulating deposits does not require you to connect an external bank account.

To deposit funds, you must first find your product funding account's financial account ID using the following query:

With your product funding account's financial account ID, you can simulate a deposit via wire transfer.

The memo field displays what typically appears on a given transfer. In the live environment, you won’t be able to control the memo field as there are specific guidelines on how WIRE and ACH appear to an account holder. In the test environment, you can edit the memo field.

The SimulateDeposit mutation will set the AVAILABLE_CREDIT amount for your product funding account. Use the following mutation to simulate a deposit:

Commercial charge card products are used by US Business account holders. When creating an account holder using the Highnote API, there are optional creditRiskAttribute fields that you may want to provide as inputs to a credit application. You can use these fields to simulate credit line assignments or adverse action reasons for your card product in the test environment. For more information on these simulations, see the following guides:

• Simulate Credit Line Assignment
• Simulate Adverse Action Declines

Use the following mutation to create a business account holder:

Once you have created a business account holder, you can open an application to onboard them to your commercial charge card product.

Opening an application triggers identity verification checks and any applicable credit policies necessary for your card product. Your card product will define the required application fields for identity verification and credit risk underwriting, which must pass in order to onboard the account holder.

Use the following mutation to create an account holder application and pass the cardProductId and accountHolderId as input variables:

The test environment does not run KYB (Know Your Business) and KYC (Know Your Customer) checks on applications. When testing, you can simulate application failures under a variety of scenarios by creating account holders with specific attribute values. The simulation will produce tags associated with the application decision and provide information as to why an Application outcome was APPROVED, IN_REVIEW, or DENIED.

For more information, see Simulate Application Denial.

When simulating credit line assignment, do not use any of the failure values outlined in the Simulate Verification Status guide. Using a failure value results in a DENIED application response. An application must be simulated for approval for a credit line assignment to be provided in the response.

If the annualRevenue value provided is not a value outlined in the following table, an approved application will have a $1,000 credit limit by default.

Some credit policies allow for dynamic allocation of credit limits for approved applications. Using the test environment, you can test various credit line assignments on APPROVED application responses. To test credit line assignment, see Assign a Credit Line.

You can simulate denied responses by entering simulation values for legalBusinessName, annualRevenue, and totalAnnualIncome. For more information on simulating adverse action decline, see Simulate Credit Adverse Action Decline.

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:

Setting or updating a credit limit is an asynchronous process with the Highnote team to ensure your ledger balances and validations are in check.

For credit, charge, and fleet card products, you can create a credit limit for an account holder's financial account based on your underwriting criteria, agreements, and product guidelines. The credit limit establishes a maximum spending limit for a given period, and authorizations exceeding the credit limit will be declined.

Once you have created a credit limit, you can update it as you factor in new information, such as changes in your customers' financial situations.

As part of this feature, Highnote tracks the total credit extended to your account holders' financial accounts and ensures the extended credit does not exceed your card product’s limits.

You can use the following mutation to set and update a credit limit:

After creating and funding a financial account, you can issue a payment card to the account holder. All payment cards start as virtual cards with the option of ordering them as physical cards.

For more information on issuing cards, see the Issue Cards guide.

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

You can create individual physical card orders using the following mutation. To create a group card order, see Print Cards in Bulk.

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 an account holder's primary account number (PAN) and security code (CVV), you can use the API to fetch them using the following query:

Recurring payments (or automatic payments) and one-time payments are used for card products that require the account holder to make a payment on a regular cadence. You’ll need to provide your account holders with the ability to make payments towards their outstanding or statement balance.

To schedule a repayment, an account holder must connect a verified, external bank account. Highnote has partnered with Plaid and Finicity as secure options for your account holders to verify and link their external accounts. Once linked, account holders can seamlessly transfer funds via ACH between their Highnote financial account and the external bank account. Prior to creating a payment schedule, you learn how to test connecting an external account via Plaid or Finicity from the Connect External Accounts Guide.

A recurring payment schedule can be set on a monthly frequency so that your account holders can schedule payments on their due date each month or on a customized calendar day. Recurring payment schedules are based on a point-in-time balance, such as outstanding balance, and the ACH transfer amount will be calculated on the scheduled date.

Use the following query to create a recurring payment:

You can also offer the option for account holders to schedule one-time payments using the following query:

Highnote provides the data necessary to create a statement for a financial account, which you can leverage to populate your own statement template and provide it to your customers.

Billing statement data is created on financial accounts and becomes available at the end of a billing cycle. For charge and credit card products, the billing period end date may vary across financial accounts on your portfolio. Statement data is typically available within 48 hours of a billing period end date.

For more information on generating a billing statement, see Generate Current Billing Statement.

In the test environment, you can end a financial account’s billing period early so you can simulate a billing period’s statement without waiting for the billing period to end.

The new period must be at least 60 seconds in the future, and if the periodBoundary is not supplied, the statement endPeriod will be set to 60 seconds in the future.

For more information, see Simulate Shifting the Current Open Statement's End Period.

In the test environment, you can transition a financial account’s billing period to the next cycle. This action simulates the conclusion of one billing cycle and the commencement of another for a financial account.

For more information on this simulation, see Simulate Rolling Over to the Next Billing Cycle.

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.