UpPass Main Concepts

There are 3 building blocks in UpPass end-to-end verification flow.

1. No-Code Builder – This builder allows you to build a customizable webform that collect user’s inputs and their ID documents for verification.
   • Input parameters – Input parameters can be configured in the Build tab to receive the information such as a unique identifier of the application such as user_id or transaction_id that can be linked to this verification. Input parameters can also be passed for data validation such as mobile number or full name as the user performs their identity verification through UpPass.
   • Form Element – This is the element inside each step of the webform. Example form elements are such as short answer, drop down, choices, images, file uploads, e-signature etc.
   • Step – This is the step (screen) that contains multiple form elements.
   • Verification Step – These are special steps that require users to perform certain verifications such as liveness, email, ID documents, bank statements, and address verification.
   • Submission – Once the user completes the webform, the information will show up under the complete submission tab. For the incomplete form that is started by users, it will also show up under the incomplete submission tab.
2. Decision Flow – The Decision Flow allows you to connect to trusted local data, fraud services, and authoritative data sources to check and make a real-time decision based on the pre-configured rules.
   • Trigger – This defines when the decision flow is going to run. Example trigger points are such as On Form Submitted, On Form Created, On Liveness Verification Complete, On Liveness Verification Fail, etc.
   • Conditional Logic – The set of rules that are pre-configured based on the answer inputs from the users or validation against the external data sources. The data points for each service are commonly used pre-aggregated / pre-defined features for each data or fraud service.
   • Action – Various type of action carried out after the Conditional Logic such as update the Status, Trigger webhooks, passing information to external service integration.
   • Status – The customizable label that can be tagged to the submission based on the decision result. Example common status are such as risk_profile = “High”, “Medium”, “Low” or risk_action = “Auto_Pass”, “Need_Review”, “Reject”.
3. Integrations – The services or webhook endpoints that can receive the verified information (JSON format) along with the decision result.
   • Webhook – This is the webhook endpoint address used to receive the webhook triggered through the Decision Flow.
   • Integration – These are services such as e-signature, CRM, email communications, and automation platforms such as Zapier that can be added to UpPass form.