--- title: All Applications slug: generic-onboarding/all-applications docTags: createdAt: 2024-09-09T11:22:34.834Z --- # Application Cards In this section, the information for all the applications submitted to date is visible. The newly added application is marked with the 'Newly Submitted' tag. - **Search filter:** A drop-down menu of search criteria, including Name, Email ID, Application ID, and Merchant ID, can be used to find the application. These filters are configurable using the GO-Admin Backops settings. After applying the search filter, the information can be entered in the search box to find the required application. - **Filter by Flow: **To find the onboarded applications, the flow can be chosen from the dropdown menu. - **Sort by: **Applications can be sorted by the available sorting criteria from the dropdown. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/h9NbPVs-iwPAKEfUalK3W_image.png "All Applications") The onboarding time shown in the cards are only in case of submitted applications. This field is switched with 'handoff date' and 'handoff time' in case the application is currently in handoff state. Each application has status buckets into which applications are segregated into. The by default available buckets are detailed out in the subsequent pages. The key statuses are: New, Pending, Accept, Reject # View Application After clicking on the view application, you come across multiple tabs. Each tab caters to a specific use case of verification as described below. Each of these tabs have details as per that specific use case for the auditor to verify against. All images can be zoomed, rotated and cropped, allowing auditors to directly adjust customer-submitted images, resolving issues like unnecessary backgrounds or improper framing. By eliminating the need for customer revisions (draft cases), this feature reduces back-and-forth communication and speeds up the onboarding process. Let us discuss these tabs in detail: ## Summary Users are required to navigate through large amounts of data and click on individual tabs to assess the safety or validity level of documents. This process is cumbersome and lacks a summarised version of the application to make decisions faster. The summary tab provides a summarized view of the application in one place. This enables the back office user to see and analyze the application at a glance. **It helps in:** 1. **Enhanced decision making: **Enable users to quickly identify sections of the application that require thorough review based on the summarized information provided. 2. **Faster Processing: **Reduce the time and effort required for users to review applications by providing a summarized view with relevant details to expedite application processing and reduce TAT. 3. **Better Risk Management: **Improve the identification of unsafe documents by providing clear indications in the summarized view, reducing the risk of processing errors. **The Summary tab has different sections:** - **Overview:** This section gives the general details of the application, like the application ID, date and time of onboarding, application status, priority flagging, and most importantly the risk status of the application - **Personal Details:** Thissection gives the overview of the personal information provided by the applicant. - **Anomalies Summary:** This section shows the list of documents that are under the uncertain or unsafe category, along with the issues that these documents have to be put under these categories. - **Documents Summary:** Documents are one of the most important things that the back office user checks. This section shows the list of all the documents submitted by the applicant along with the percentage score of their risk profiles - **Forensics: **This shows the status of the VKYC, liveliness check and face match of the application based on the forensic analysis done by the API. :::Iframe{code="
"} ::: ## Data and Document The data and documents submitted by the onboarding customer in each step can be seen here. The result of its text match as well as the verification result sent back by the APIs is also visible here for the backops user to make an informed decision. The status, i.e., safe, uncertain, unsafe, decided by the decision engine can also be seen for each document that is submitted. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/5pJAH_JCgVU9lcOcj0bt2_data.gif "Data and Document") ## Due Diligence This is a risk and compliance check. It conducts a check/review to verify the facts and information of the onboarding customer. The aim is to ensure better valuation and risk mitigation.  - **AML Check:** This is the Anti Money Laundering Check. In this step, it checks whether the applicant has participated in any offending activities. - **Browser Data:** Provides information about the browser used by the applicant when onboarding. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/PK9CfaqK_i10UNUy9yypJ_due.gif "Due Diligence") ## Forensics The Forensics section displays the POI Image and Video recorded by the applicant (Video Verification / Photo Verification) or agent (VKYC). The back office admin can play the video and match the face from the POI image to ensure the onboarding customers themselves have performed the journey (Video Verification / Photo Verification / VCIP call). This tab renders the following information: - A PDF report containing VCIP call details. - Questions asked in the VCIP call and the corresponding agent remarks. - OTP verification details and the associated Audio Match Score (in case of video verification only). - Geolocation captured during the VCIP call (of customer and agent). - Details of the Agent who did the VCIP call. - Final Remarks of the agent. - Video Recording of the VCIP call. - Browser Details of the customer / Network details - Proof of Identity Document - Face Match Score In case any of these data is not passed, then a message will be displayed "No data has been provided". Face match score is run between the VCIP call and the proof of identity provided. If there are multiple face match scores used, then all of them will be displayed in this same tab. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/I4f5IL0X6reSeOCdBAgal_image.png "Forensics") ## Form Data When the applicant fills out the form, the whole data can be viewed under this section. The Forms section displays the data filled in by the applicant in the KYC data step which includes the applicant’s information like Gender, Place of Birth, Annual Income, Occupation, Father’s/Spouse's name, etc. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/oepwxMDUqzV6hQJlIdTDR_form.gif "Form Data") ## Additional Checks The additional checks option is the consolidated checks that may be dispersed over many tabs or sections. This can be added/configured using the Additional Checks tab present in the [Backops](docId\:KMBl7JRB5rsXyDurlkKeS) section in the GO admin portal and is used to add some additional checks to the back office portal. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/nUiQqLP-z1mTxeOLxSRUn_image.png "Additional Checks") ## Cross Verification Document verification is the process of verifying the customers' identity by performing several authenticity checks on the customer-provided ID documents. AI-based document verification solutions help us to detect and eliminate the risk of fake identities and identity thefts. It is highly capable of analyzing minor signs of forgery or modification in a single pixel of the ID document. This section will allow us to compare data from 2 different documents and match the result. It can be checked whether the different documents submitted by the applicant belong to the same person and whether both the documents have the correct and same data. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/6Jwg0K1KeJ8dqRAkvRmkE_cross.gif "Cross Verification") ## Contract The Contract section will display the digitally signed contract PDF generated from the application submitted by the applicant. Backops users can make a decision based on the data verified by them to either accept/reject/move the application to drafts.  An audit trail is a step-by-step record that allows accounting details, trade details, or other financial information to be traced. Many types of transactions can be verified and tracked with audit trails, including accounting transactions and trades in brokerage accounts. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/uxbMkj0VzSbpILG0LLk6U_screen-recording-2023-12-05-at-51814-pm.gif "Contract") ## Audit Trail Applications in GO have an audit trail that can be viewed in the Back Office Portal. The audit trail that can be viewed in the back office is detailed and comprehensive. It shows all the changes made to the application with minute details, such as the page and the field to which the change was made. It reflects the old value and the new value added. It also shows who made the last updates along with the date and time.  ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/40Xgm-e1sFDonsQP28QPT_screencast-from-2023-12-06-15-43-34.gif "Audit Trail") ## Internal Notes The notes that were written when checking the application, are shown here. In this section, the notes added by the back office user can be viewed. It will also display the rejection reasons for the rejected application and redo reason for applications moved to redo along with the name of the back office user who created the note and date of creation along with the timestamp. The 'Add New' note button is also provided to add additional notes. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/ZfMExbDn_wIgSTvYRPWj6_image.png "Internal Notes") ## Logs The logs section shows the details of how the application acceptance/rejection process progressed as well as the details of the RM to whom the application has been assigned. It shows the logs of when the application was submitted, drafted, accepted, rejected, etc., along with the date and timestamp of the event. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/qAOatj3VWVsrPJOAJ9fz-_log.gif "Logs") ## Merchant Logs This tab shows the logs of the merchant onboarding journey. It shows the details of how the onboarding journey progressed throughout. It shows the logs of all the events that occurred during the journey. Using the merchant journey logs, the actions taken by a specific merchant, the date and time when the action was taken, and the messages that were noted while performing the action can be viewed. It also shows whether the action was successful or an error occurred during the process. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/pUWNU8VzJsxZyB_UyOOlV_mer-log.gif "Merchant Logs") ## Custom Information The Custom Information tab serves as a dedicated section where information obtained through third-party integrations using the GO blender repository can be displayed. It provides a convenient and organized space for showcasing data and insights from external sources within the workflow. It can be displayed in the backops portal by following these steps: 1. Go to GO Admin Portal. 2. Click on the Backops section. 3. Go to Settings. 4. In the URL configuration tab, enter the blender URL in the 'EndPoint for Custom Information' textbox. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/w435ekxqHFd8XTye0OJ99_screen-recording-2023-05-23-at-25124-pm.gif "Custom Information Configuration") ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/LV3A6ruFRnx1bzm7j84pj_image.png "Custom Information") ## Application Report This feature is used to generate a report of the onboarding application in a PDF format. This pdf generated is not visible to the front-end onboarding user and is displayed in back office under the 'Application Report' tab for the checker to review. The platform can generate an 'application report' which is visible to the auditor dashboard. Any detail from the front-end (including file uploads) journey can be populated within the application report. The report expects an HTML format file as a template with variable mapping from the front end. The template needs to be uploaded in the 'Flow' settings in GO Admin. The output report is a pdf file in the tab "Application Report" within the application details. ![](https://api.archbee.com/api/optimize/w0YdjmC6Uxu0AJ6sPj9OT/Un9mT5k_K-RlauxhOJ7Uy_screen-recording-2023-05-23-at-70211-pm.gif "Application Report Configuraton") :::hint{type="info"} ### Getting help Please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better. You can reach out to us at [help@signzy.com](#). :::