Update Application Information

Card product applications with identity mismatches may require manual review. In some cases, an account holder can attempt to resolve the issue by updating an application that is in progress. This page explains how.

Once an application is updated, Highnote re-runs verification. If the updated information matches, identity verification is approved. If the updated information still results in a mismatch, identity documents may be requested from the account holder.

The workflow for updating application information is as follows:

1. Subscriber receives the notification, CARD_PRODUCT_APPLICATION_IDENTITY_UPDATE_REQUESTED .

2. Subscriber queries the following: businessProfile, primaryAuthorizedPerson, ultimateBeneficialOwners

3. Subscriber initiates identity updates and supplies the fields requested in changesRequested (as many times as needed).

4. Once the changes are applied, the subscriber enables the customer to CONFIRM or CANCEL.

   • If customer confirms: Confirm the Initiated Update
   • If customer cancels or does not follow through: Cancel the Initiated Update.
   • If no changes are needed, Cancel the Initiated Update.

Once confirmed or canceled, additional changes are no longer allowed.

The following Business Account Holder fields can be updated while an application is in progress.

You cannot update a Business Profile if any of the following tags are present on the application: OFAC_MATCH or DENIED_FRAUD.

In these scenarios, Highnote performs additional validation and verification to determine the final KYB status of the Business Profile.

You cannot update a Primary Authorized Person if any of the following tags are present on the application: HIGH_ABUSE_SCORE, HIGH_THEFT_SCORE, DENIED_FRAUD, or WATCHLIST_HIT.

In these scenarios, Highnote performs additional validation and verification to determine the final KYC status of the Primary Authorized Person.

You cannot update an Ultimate Beneficial Owner (UBO) if any of the following tags are present on the application: HIGH_ABUSE_SCORE, HIGH_THEFT_SCORE, DENIED_FRAUD, or WATCHLIST_HIT.

In these scenarios, Highnote performs additional validation and verification to determine the final KYC status of the Ultimate Beneficial Owner.

Use the following query to find requested identity updates on an application, indicated by the current verification reason of IDENTITY_UPDATE_REQUESTED. The changesRequested field within the requestedUpdates array indicates which fields can be updated to resolve identity verification.

Use the following mutations to initiate identity updates.

Use the requestedIdentityUpdateId from the query above to initiate an update for the Business identity.

Use the following mutation to stage an update to an identity for the Business Account Holder’s Primary Authorized Person.

Use the following mutation to stage an update to an identity for the Business Account Holder’s Ultimate Beneficial Owner.

After staging the update, use the following mutation with the requestedIdentityUpdateId to confirm and submit the applied updates. Once confirmed, KYC and/or KYB will automatically re-run with the updated identity information. If identity verification can still not be resolved with the updated information, documentation may be requested for the identity.

You can cancel the initiated identity update to the Business, the Primary Authorized Person, or the Ultimate Beneficial Owner. If the Account Holder has no changes to the identity, cancel the update. If the update is cancelled, documentation may be requested for the identity.

Use the following mutation to cancel an update to an identity, prior to confirming.

Use the following query to review the appliedUpdates on the Account Holder’s application.