Home / Issuing / Manage Credit
Collaborative application decisioning is self-service in your test environment. In the live environment, the feature must be enabled for your card product by the Highnote team.
With collaborative application decisioning, you or your underwriter can make a recommended decision of APPROVED
or DENIED
for applications of your product based on your credit policy. Highnote will conduct regulatory checks on the application, including KYC, KYB, and OFAC, and use your recommended decision to arrive at a final decision. Highnote also allows for customization of the sequencing of application decisioning calls and rule execution to fit your product and credit policy.
In this guide, we will assume that you or your underwriter first provide a recommended decision after identity and fraud checks are run by Highnote before making a final decision.
The easiest way to enable collaborative application decisioning is from the Highnote dashboard in your product's settings:
You can also enable the feature from the API using the following mutation:
Receiving Events & Notifications requires you setup a Notification Target.
After the application has been submitted to Highnote, you will receive the notification event CARD_PRODUCT_APPLICATION_UNDERWRITING_DECISION_REQUESTED
. This notification event requests an underwriting decision from you or your underwriter.
The following payload is an example of the notification event you will receive:
{ "data": { "node": { "__typename": "NotificationEvent", "createdAt": "2022-12-12T16:32:49.125Z", "id": "NOTIFICATION_EVENT_ID", "name": "CARD_PRODUCT_APPLICATION_UNDERWRITING_DECISION_REQUESTED", "node": { "__typename": "AccountHolderCardProductApplication", "applicationState": { "status": "PENDING" }, "createdAt": "2022-12-12T16:32:44.499Z", "id": "APPLICATION_ID", "updatedAt": "2022-12-12T16:32:44.499Z" } } }, "extensions": { "signatureTimestamp": 1670862772620 } }
After receiving the event notification, Highnote will then await your call with your application decision.
To make an APPROVE
decision, you must specify the credit limit decision. The credit limit should be assigned to the financial account after creation.
If you are unsure about the initial credit limit during the underwriting decision, you can assign a credit limit of $0 and adjust it for the financial account later.
Use the following mutation to respond with an approval:
For a DENIED
decision, the overall application will be DENIED
and you must provide the applicable adverse action reason(s) based on your credit policy. If a decision is not received within 30 days from the application creation date, the application status will transition to DENIED
.
A complete list of adverse action reasons is available in the API Reference.
Use the following mutation to deny a credit application:
If you provide a counter offer, you still must provide the adverse action reason(s) for the denial of the card product the account holder originally applied for.
If your account holder’s creditworthiness does not qualify them for the card product they applied for, you can offer them a counter offer to an alternative product. For example, you may want to provide a counter offer to a secured credit card instead of an unsecured one. For more information on Highnote's secured deposit feature, see Create Secured Deposit Offer.
If the account holder wants to accept the counter offer, you can provide their consent of the accepted offerId
to onboard them to counter offered card product. Once an account holder accepts a counter offer, they can receive a financial account.
Use the following mutation to respond to a denied credit application with a counter offer:
After an application decision is made, the application will be marked as PENDING
while Highnote goes through the application workflow and makes a final decision. To keep track of updates to the application's status, you can use the GetAccountHolderCardProductApplication
query or subscribe to the application status events notification to get notified when the application’s status changes.
Use the following query to check the status of an application: