# Loan Application Screening

<figure><img src="/files/OD62nIfhRraziFT6WAKZ" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
It should be explicitly noted here that all constituent elements of BCA Bank and BCA Finance in this use case, such as car loan eligibility criteria, customer profiles within the bank, and any other related artifacts, are ***purely hypothetical and fictitious*** and therefore designed exclusively for illustration purposes only.
{% endhint %}

## <mark style="color:blue;">Overview</mark>

BCA Finance, a prominent player in car loan solutions, manages a high-volume stream of applications on a daily basis. The application processing pipeline is segmented into two pivotal phases: Preliminary Screening and Comprehensive Evaluation. This use case is confined to defining the architecture and implementation methodologies for the Preliminary Screening phase, with a particular emphasis on privacy preservation and execution transparency using the zkPass architecture. The Comprehensive Evaluation phase, although crucial, falls beyond the scope of this use case.

## <mark style="color:blue;">Minimum Eligibility Criteria for Preliminary Screening</mark>

To be eligible for car loan coverage through BCA Finance, applicants must meet the following hypothetical criteria as part of the initial screening phase:

* Hold an active BCA Bank account with a minimum balance of Rp 55,000,000.
* Have a credit score of 650 or above.

Fulfilling these prerequisites is imperative for advancing to the comprehensive evaluation stage of the application process.

## <mark style="color:blue;">Objectives of the Screening Process</mark>

BCA Bank and BCA Finance intend to develop a screening process that meets the following objectives:

* <mark style="color:orange;">**Cost-Efficient Application Filtering**</mark>\
  The objective is to expedite the initial sorting of incoming applications, consequently lowering operational overhead. Utilizing an automated, secure, real-time processing system allows BCA Finance to substantially reduce the financial burden associated with manual intervention.
* <mark style="color:orange;">**Privacy Protection for BCA Bank Customers**</mark>\
  In order to safeguard customer data privacy, BCA Bank will not directly transfer any sensitive information to BCA Finance. Rather,  a proof-of-eligibility token, which confirms that the applicant satisfies the predefined criteria, should be sent to BCA Finance. This approach mitigates the risk of data exposure while maintaining the integrity of the application process.
* <mark style="color:orange;">**Verifiable Loan Evaluation**</mark>\
  Ensuring transparency in the car loan application workflow is crucial. The evaluation result must be solely based on a quantitative analysis of the applicant's credentials. Specifically, the decision-making must be controlled by the business rules defined in a query, which lays out the particular criteria for car loan eligibility. BCA Finance requires that its query runs unmodified, retaining its original logic. Additionally, the query must be performed on the customer profile data and should correspond to the applicant under assessment.

The objective of this use case study is to provide a comprehensive blueprint for zkPass integration to implement a loan application screening mechanism that maintains a good balance between operational efficiency, user data privacy, and verifiable execution. Subsequent sections will delve into the intricate details of the technical architecture, data flow dynamics, and the integration strategies for each stakeholder.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gl-docs.gitbook.io/zkpass/use-cases/loan-application-screening.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.