Identity Verification
To ensure your business and Highnote are abiding by applicable laws and regulations, customers signing up for your card product are required to complete an application where the details provided are verified for accuracy and are validated. In order for an Account Holder to be onboarded and issued a Payment Card, an Application needs to be approved by Highnote. Qualifications include passing the Customer Identification Program (CIP), as well as Customer Due Diligence (CDD) to establish and confirm the identity of the Account Holder, and where applicable Enhanced Due Diligence (EDD) may need to be performed.
Identity verification is performed on an Application. You will open an Application on the Card Product for the Account Holder, at which point, identity verification will be performed.
After an Application is submitted, the Application applicationState.status returned will be:
PENDING, IN_REVIEW, DENIED, or APPROVED
| Status | Description |
|---|---|
PENDING | The Application has been received and the system is running automated verifications. |
IN_REVIEW | In some cases, an Application may be flagged for manual review because fraud is suspected or the information provided appears incorrect. An agent is reviewing the Application to determine a decision or if additional information is required from the Account Holder. |
DENIED | The Application has failed one or more policies (e.g. fraudulent application information provided). A Payment Card cannot be issued to this Account Holder. Customer notification of the denial and denial reason may be required. |
APPROVED | The Application has been approved. You may now issue a Payment Card to the Account Holder. |
After an Application is submitted, the Application returns an AccountHolderSnapshot containing detailed verification result codes:
| Response | Description |
|---|---|
ADDRESS_MATCH | The individual’s address was able to be verified |
ADDRESS_MISMATCH | Address was unable to be verified as provided |
DOB_MATCH | Date of birth was able to be verified |
DOB_MISMATCH | Date of birth does not match the known date of birth of the individual |
NAME_MATCH | The individual’s name was able to be verified |
NAME_MISMATCH | The name provided was unable to be verified |
SSN_MATCH | Social security number was able to be verified |
SSN_MISMATCH | Social security number does not match a known social security number for the individual |
PHONE_MATCH | Phone number was able to be verified |
PHONE_MISMATCH | Phone number does not match any known phone numbers for the individual |
WATCHLIST_HIT | The individual is currently on an active watchlist |
DEVICE_WARNING | The individual’s device has been previously flagged for fraudulent activity |
FOREIGN_DEVICE | The individual’s device has not been used in the past |
HIGH_ABUSE_SCORE | High probability of synthetic fraud |
HIGH_THEFT_SCORE | High probability of third party fraud |
MEDIUM_ABUSE_SCORE | Moderate probability of synthetic fraud |
MEDIUM_THEFT_SCORE | Moderate probability of third party fraud |
LOW_ABUSE_SCORE | Low probability of synthetic fraud |
LOW_THEFT_SCORE | Low probability of third party fraud |
KYC_FRAUD_PASS | This outcome tag is present when the following tags are not set: HIGH_THEFT_SCORE, HIGH_ABUSE_SCORE, MEDIUM_THEFT_SCORE, MEDIUM_ABUSE_SCORE, and KYC_WARNING |
KYC_WARNING | This outcome tag is present if any of the following tags are not set: ADDRESS_MATCH, DOB_MATCH, NAME_MATCH, SSN_MATCH or if the following tag is set: WATCHLIST_HIT |
After an Application is submitted, the Application returns an AccountHolderSnapshot containing detailed verification result codes:
| Response | Description |
|---|---|
ADDRESS_MATCH | Business address was able to be verified |
ADDRESS_MISMATCH | Business address was unable to be verified as provided |
BUSINESS_VERIFICATION_SCORE_PASSED | The business' overall identity has been verified |
BUSINESS_VERIFICATION_SCORE_FAILED | The business' overall identity has not been verified |
BUSINESS_NAME_MATCH | The business’ name was able to be verified |
BUSINESS_NAME_MISMATCH | The business' name provided was unable to be verified |
FEIN_MATCH | Business EIN/FEIN was able to be verified |
FEIN_MISMATCH | Business EIN/FEIN does not match a known EIN/FEIN for the business |
REPRESENTATIVE_MATCH | The associated person(s) or authorized primary applicant has been associated with the business entity |
REPRESENTATIVE_MISMATCH | The associated person(s) or authorized primary applicant has not been associated with the business entity |
OFAC_MATCH | The business information has been associated with a business on the OFAC list |
In some cases, applications can be flagged for review because additional account holder verification information is needed. This review process confirms the person or business's identity and ensures compliance with Know-Your-Customer (KYC) or Know-Your-Business (KYB) regulations.
The application review process typically takes place as follows:
- The application is flagged for review and inherits an
IN_REVIEWstatus. - The application is either manually reviewed by Highnote or indicates that additional documentation is needed from the account holder.
- Optional - Using the application status event notification, you can send a notification to account holders to alert them of the application review status and direct them to the document upload flow.
- Generate a document upload session so the account holder can upload their documents.
- Once the account holder documents are received, Highnote reviews them and makes one of the following application decisions:
- Approve the application: This indicates that the documents were verified and that the account holder's identity was confirmed.
- Deny the application: This indicates documents were not provided or appear to be fraudulent.
- Ask for more documents: This indicates that additional documents are needed to confirm the identity of the account holder.