This document describes the inner workings of Field Data selection. The Instnt Accept workflow builder allows for in-depth customization of each workflow starting with the Field Selector tool.
About Field Data
The Instnt Accept workflow builder allows in-depth customization for each workflow beginning with the Field Selector tool. Field data is the data you collect from end-users applicants in an Instnt powered sign-up page.
Instnt internally runs a decision engine and models the data you collect. We provide this using either our API or SDK. The field data submitted is the key to any 'Accept,' 'Reject,' or 'Review' decision from Instnt Accept.
We provide reason codes used to analyze the decision given by Instnt; for more information, see the Reason Code Glossary.
How-to select the Field Data?
After you signup and create an end-user in the Instnt dashboard, you can modify fields with the Field Selector tool.
Within this tool, the mandatory fields are pre-selected. You can custom and remove fields from the Add Fields section. For more information regarding the procedure to select Field Data, see the Quick Start Guide.
Types of Fields
Required Field Data
With Instnt, the establishment of your customers' identity and legitimacy increases with the number of fields you select for the verification process.
You are using Instnt with the end goal of verifying and eliminating risk when onboarding a new customer with the provided required fields.
First Name, Last Name, Address, and Phone are the mandatory fields; these are the minimum fields required to verify your customers. The Instnt decision-making models run correlations between the data provided.
The final decision varies on whether each Personal Identifiable Information (PII) independently and in correlation with each other can be verified or not.
- If an applicant's Name, Address, and Phone are verified accordingly, the decision is Accepted.
- If an applicant's Name, Phone is verified with the Address only on the City level, a Review decision is given.
- If Name, Address, and Phone fields are not verified accordingly, the decision is Rejected.
SSN, Selfie, Document Verification, and Address are optional fields; Instnt does not decide what information you should collect from your customer. Yet, we facilitate you with options with a range of possibilities.
The optional fields are beneficial when mandatory fields are not verified accordingly due to possible unavailabilities in data sources from our vendors.
When you enable the Know Your Customer (KYC) verification during workflow creation, optional fields are mandatory. The mandatory fields for Know Your Customer (KYC) include Name, DOB, Address, and Social Security Number (SSN). For more information, see the KYC article.
Email is a recommended field to have. While it does not directly affect the final decision, it reconciles data from our vendors and helps arrive at a more reliable and assured outcome.
Instnt recommends enabling the mandatory fields and adding Document Verification to your customer onboarding flow.
These checks add additional security layers for proving the identity and legitimacy of your customer with a greater chance of getting an 'Accept' decision from Instnt.
The additional data gives Instnt more room to work on different schemas and models for the final decision.
Advantages of Document Verification include verification of government-issued identification documents such as Driver's Licenses, passports, and more to simplify the verification process of addresses and DOB provided alongside their identification.
Instnt does not claim that all customers are verifiable via document verification and DOB checks, but we recommend additional assessments.The decision-making depends on the data returned to a user. Various factors regarding if a user recently obtained a Driver's License or acquired a new phone number, and other unique situations may result in verification interference.