Digital Onboarding For Banks

A report submitted for the course named Internship - VIII (CS423)

Submitted By

A BHISHEK K UMAR
SEMESTER - VIII
20010127
Supervised By

D R . N. K ISHORJIT S INGH

D EPARTMENT OF C OMPUTER S CIENCE AND E NGINEERING I NDIAN I NSTITUTE OF

I NFORMATION T ECHNOLOGY S ENAPATI , M ANIPUR M AY, 2024
 Declaration
In this submission, I have expressed my idea in my own words, and I have
adequately cited and referenced any ideas or words that were taken from
another source. I also declare that I adhere to all principles of academic
honesty and integrity and that I have not misrepresented or falsified any
ideas, data, facts, or sources in this submission. If any violation of the above
is made, I understand that the institute may take disciplinary action. Such a
violation may also engender disciplinary action from the sources which were
not properly cited or permission not taken when needed.

Abhishek Kumar
20010127

DATE: 06/05/2024

1
 Department of Computer Science Engineering
Indian Institute of Information Technology Senapati, Manipur

Dr. N. Kishorjit Singh Email: kishorjit@iiitmanipur.ac.in

HOD, CSE department, IIIT Manipur Contact No: +91 8974008610

To Whom It May Concern

This is to certify that the project/internship report entitled "Digital

Onboarding For Banks", submitted to the department of Computer
Science and Engineering, Indian Institute of Information Technology
Senapati, Manipur in partial fullfillment for the award of degree of
Bachelor of Technology in Computer Science and Engineering is
record bonafide work carried out by Abhishek Kumar bearing roll
number 20010127

Signature of Supervisor

Dr. N. Kishorjit Singh

Signature of the Examiner 1 ............................

Signature of the Examiner 2 ............................

Signature of the Examiner 3 ............................

Signature of the Examiner 4 ............................

 #18/2A, GRS Towers, Second Floor
Sarjapur Road, Bangalore 560 102
+91 80 4212 4272
contact@novopay.in

OFFER LETTER

8th December 2023

Dear Abhishek,

We are pleased to offer you an Internship at Novopay Solutions Private Limited (“the Company”). During
this internship you will be working from the Bangalore HQ office.

Your internship period shall be from 11th December 2023 to 11th June 2024.

We will offer you a stipend of INR 20,000 per month. Subject to your performance & business needs we will
review if your internship can be further extended and/ or full-time employment can be offered.

a. This internship is no guarantee or expectation that the activity will result in employment with the
Company. You will be provided with an internship certificate subject to the successful completion
of the internship.

b. You will maintain a regular internship schedule determined by the manager. In the event you wish
to take a planned leave, a prior intimation of a minimum of 48 hours needs to be provided.

c. During the course of this Internship, it may be necessary for the Company to share proprietary
information, including trade secrets, industry knowledge, and other confidential information, with
you in order for you to complete the duties and responsibilities. You will not share any of this
proprietary information at any time. You also will not download into your system and use any of
this proprietary information for your personal benefit at any time. This section remains in full force
and effect even after termination of the internship by its natural termination or the early termination
by either party.

d. You agree that any content provided to you by the Company in order to perform your duties and
responsibilities, including but not limited to, images, videos, and text, copyrights, or trademarks,
remains solely owned by the Company. Any work product you may create during the course of this
Internship remains the sole property of the Company.

e. The Internship can be terminated by the Company or by the intern by giving a written notice of at
least 15 (fifteen) days to the other party. Alternatively, the Company may terminate your internship
with immediate effect, upon giving you stipend in lieu of notice or pro-rated stipend for the balance
Notice Period. In case you have given a notice to terminate your internship you are expected and
required to diligently serve the entire notice period, which includes but is not limited to the
following:

3
4
 Abstract

The YesBank Digital Onboarding Service revolutionizes the customer on-

boarding experience within the framework of YesBank’s digital ecosystem.
This pioneering platform orchestrates a seamless journey for customers,agent,
and backend systems, aiming to streamline the enrollment process across a
spectrum of financial services. By harnessing advanced technology and in-
novative solutions, the platform offers a suite of features tailored to enhance
efficiency, security, and compliance.Key components include electronic docu-
ment submission, digital signatures, and real-time verification protocols, en-
suring a frictionless and expedited onboarding process. Customizable work-
flows cater to diverse product offerings and customer demographics, provid-
ing tailored experiences that align with individual preferences and regula-
tory requirements.Emphasizing user-centric design principles, the YesBank
Digital Onboarding Service prioritizes accessibility and ease of use, empower-
ing customers to interact with the platform seamlessly across multiple chan-
nels. Robust security measures safeguard sensitive data and transactions,
bolstering trust and confidence among stakeholders.With its agile and scal-
able architecture, the platform adapts to evolving industry trends and regula-
tory landscapes, positioning YesBank at the forefront of digital innovation in
banking. By facilitating swift customer acquisition, minimizing operational
overheads, and ensuring compliance with regulatory mandates, the YesBank
Digital Onboarding Service embodies the commitment to excellence and in-
novation that defines YesBank’s digital journey.
 Acknowledgement

I extend my heartfelt gratitude to Mr. Amit Kumar Agarwala, Engineer-

ing Manager at Trustt(formerly Novopay), for his exceptional guidance and
unwavering support throughout my internship at Trustt(formerly Novopay).
His profound knowledge, extensive experience, and remarkable dedication
have been invaluable assets to my learning journey. Mr. Amit’s mentorship
has not only provided me with a deeper understanding of the complexities
within the field but has also instilled in me a sense of confidence and profi-
ciency. I am deeply appreciative of his continuous encouragement and con-
structive feedback, which have enabled me to navigate through challenges
and enhance my skills effectively. Moreover, I am immensely grateful to Mr.
Amit for creating a conducive learning environment where I felt empowered
to explore new ideas, experiment with various approaches, and learn from
both successes and setbacks. His open-door policy and willingness to lend
a listening ear have fostered a sense of camaraderie and trust, making it
easier for me to seek guidance and clarification whenever needed. Further-
more, I am indebted to Mr. Amit for his exceptional problem-solving abilities
and proactive assistance in resolving any issues or hurdles that arose dur-
ing the course of my internship. His patience, encouragement, and genuine
interest in my professional development have left an indelible mark on me,
and I am immensely grateful for the opportunity to have worked under his
esteemed supervision. I would also like to express my sincere appreciation
to IIIT Manipur for providing me with the platform and resources to pur-
sue my internship at Trustt(formerly Novopay). The supportive environment
and academic infrastructure at IIIT Manipur have played a pivotal role in
facilitating my learning and growth throughout this internship journey. I am
grateful for the opportunities, guidance, and encouragement extended to me
by the faculty members and staff at IIIT Manipur, which have contributed
significantly to my overall development as a student and a professional.

Abhishek Kumar

1
Contents

List of Figures 3

1 Introduction 4
1.1 Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Literature Survey 11

3 Requirement Engineering 13

4 System Design 15

5 Implementation 20
5.1 TAT Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2 MSG file upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3 Product Admin Portal . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.4 Email triggering to psm . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.5 Adding country code . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.6 Upload Blank page letter head . . . . . . . . . . . . . . . . . . . . . 25
5.7 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6 Results 26
6.1 Project Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.1.1 Task 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.1.2 Task 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.1.3 Task 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.1.4 Task 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.1.5 Task 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.1.6 Task 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

7 Conclusion 37

Bibliography 39

2
List of Figures

4.1 MVC Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

6.1 TAT columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

6.2 msg file upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.3 Product admin role . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.4 country codes for different products . . . . . . . . . . . . . . . . . . 35
6.5 Upload Blank Letter Head . . . . . . . . . . . . . . . . . . . . . . . 36

3
Chapter 1

Introduction

Throughout my tenure at Trustt (formerly Novopay), I’ve had the privilege to

contribute to the development of a dynamic and innovative backend system
built on the foundation of Spring Boot and MySQL technologies. As a key
member of the development team, I’ve witnessed firsthand the transforma-
tive impact of these technologies on our product’s architecture, performance,
and scalability.

At Trustt, we recognize the critical role that backend systems play in en-
abling seamless interactions between applications, databases, and users. Lever-
aging the robust features and capabilities of Spring Boot and MySQL, we’ve
strived to create a backend infrastructure that not only meets the demands
of today’s digital landscape but also anticipates the needs of tomorrow.

Spring Boot, with its convention-over-configuration approach and compre-

hensive ecosystem of libraries and tools, has empowered us to rapidly de-
velop and deploy complex applications with ease. Its built-in support for de-
pendency injection, MVC architecture, and embedded servers has accelerated
our development cycles and enhanced our team’s productivity.

Complementing Spring Boot, MySQL has served as the cornerstone of our

data management strategy, providing a reliable and scalable platform for
storing, retrieving, and analyzing vast amounts of data. With features such
as ACID compliance, data replication, and advanced indexing, MySQL has
enabled us to ensure data integrity, optimize performance, and meet the
evolving needs of our users.

In this project report, I aim to share insights gleaned from my experience

working on our backend system at Trustt. From architecture design to im-
plementation details, I will explore the journey of leveraging Spring Boot and
MySQL to build a robust, efficient, and resilient backend infrastructure that

4
powers our product’s success. Through this exploration, I hope to inspire and
inform fellow developers, practitioners, and stakeholders about the transfor-
mative potential of these technologies in driving innovation and delivering
value in today’s digital economy.

1.1 Outline
The project introduces a comprehensive digital onboarding solution aimed at
revolutionizing the customer onboarding experience for Yes Bank. Recogniz-
ing the challenges and inefficiencies inherent in traditional onboarding pro-
cesses, the project aims to streamline and automate key aspects of customer
onboarding, including document submission, verification, and approval. By
leveraging cutting-edge technologies and best practices in software develop-
ment, the project seeks to enhance operational efficiency, improve customer
satisfaction, and drive business growth for Yes Bank.

The motivation behind the project stems from the need to address the short-
comings of manual onboarding processes, which are often time-consuming,
error-prone, and labor-intensive. By transitioning to a digital onboarding so-
lution, Yes Bank aims to reduce turnaround times, minimize errors, and pro-
vide a seamless and user-friendly onboarding experience for its customers.
Furthermore, the project aligns with Yes Bank’s strategic objectives of em-
bracing digital transformation and delivering innovative banking solutions
to its customers.

The purpose of the project is twofold: firstly, to streamline and automate the
customer onboarding process, and secondly, to enhance the overall customer
experience. By implementing a digital onboarding solution, Yes Bank aims
to reduce paperwork, eliminate manual data entry errors, and accelerate the
onboarding process. Additionally, the project aims to improve customer satis-
faction by providing a more convenient and efficient onboarding experience,
thereby enhancing Yes Bank’s reputation as a customer-centric bank.

Throughout the project, a thorough literature survey was conducted to iden-

tify best practices, industry standards, and emerging trends in digital on-
boarding. This survey informed the selection of technologies, methodologies,
and frameworks used in the project, ensuring alignment with industry stan-
dards and best practices. Additionally, the literature survey provided valu-
able insights into customer expectations, regulatory requirements, and com-
petitive benchmarks, guiding the design and implementation of the digital
onboarding solution.

In conclusion, the Yes Bank digital onboarding project represents a signifi-

5
cant step forward in modernizing the customer onboarding process and deliv-
ering superior banking services to customers. By leveraging the latest tech-
nologies and best practices, the project aims to transform the way customers
onboard with Yes Bank, making the process faster, more efficient, and more
user-friendly. With a strong foundation in place and a commitment to contin-
uous improvement, the project is poised to drive innovation and excellence in
customer onboarding for years to come.

6
1.2 Problem Statement
In contemporary software development landscapes, the integration and syn-
chronization of frontend and backend systems pose formidable challenges, ne-
cessitating meticulous coordination between diverse technologies and special-
ized development teams. Within the framework of Trustt’s (formerly Novo-
pay) project, this challenge assumes paramount importance, particularly in
effectively bridging the sophisticated backend infrastructure constructed upon
Spring Boot and MySQL technologies with the frontend interface developed
using Angular. Despite the robust capabilities of Spring Boot and MySQL in
offering streamlined development processes, resilient data storage, and effi-
cient data retrieval, the project’s triumph pivots on the seamless amalgama-
tion of these technologies with the frontend framework. My role as a backend
developer entails crafting and optimizing the backend infrastructure to en-
sure its compatibility and synergy with the frontend components. Crucial as-
pects encompass optimizing backend performance, implementing robust se-
curity measures, and architecting scalable database structures. Challenges
include establishing efficient communication channels between the frontend
and backend layers to facilitate seamless data exchange, ensuring the re-
liability and integrity of data storage mechanisms, and implementing strin-
gent security protocols to safeguard sensitive information. Collaboration with
frontend development teams is indispensable to align backend functionalities
with frontend requirements and ensure cohesive system functionality. More-
over, addressing scalability concerns and anticipating future growth demands
meticulous planning and strategic implementation of scalable backend archi-
tectures. Successful resolution of these challenges hinges on a comprehensive
understanding of backend technologies, meticulous attention to detail, and
effective collaboration with cross-functional teams. Ultimately, Trustt (for-
merly Novopay) endeavors to deliver a robust, scalable, and secure backend
infrastructure that underpins the seamless operation and user experience of
its digital platform.

7
1.3 Motivation
The motivation behind undertaking this project at Trustt (formerly Novopay)
stems from a commitment to delivering cutting-edge solutions that address
the evolving needs and expectations of users in today’s digital landscape. As
technology continues to advance at a rapid pace, there is a growing demand
for seamless and intuitive digital experiences that empower users and drive
engagement. By leveraging state-of-the-art technologies such as Spring Boot,
MySQL, and Angular, we aim to create a robust and user-centric platform
that revolutionizes the way users interact with our services.

Furthermore, the motivation for this project lies in the recognition of the
critical role that backend and frontend systems play in shaping the overall
user experience. A seamless integration between these systems is essential to
ensure smooth data flow, efficient communication, and cohesive functionality.
By investing in the development of a sophisticated backend infrastructure
and a responsive frontend interface, we strive to enhance user satisfaction,
improve efficiency, and drive business growth.

Moreover, the motivation for this project also stems from a desire to stay
ahead of the curve in an increasingly competitive market. By embracing
emerging technologies and best practices in software development, we posi-
tion ourselves as innovators and industry leaders, capable of delivering un-
paralleled value to our users and stakeholders. This project represents an
opportunity to push the boundaries of what is possible, to explore new av-
enues of innovation, and to create solutions that have a meaningful impact
on the lives of our users.

In essence, the motivation for this project lies in our unwavering commitment
to excellence, innovation, and user satisfaction. By harnessing the power of
technology and leveraging the expertise of our talented team, we aim to cre-
ate a digital platform that sets new standards for quality, reliability, and
usability. Through this project, we aspire to not only meet but exceed the ex-
pectations of our users, cementing our position as a trusted provider of digital
solutions in today’s dynamic and competitive market landscape.

8
1.4 Purpose
The purpose of the Digital Onboarding For Banks project at Trustt(formerly
Novopay) is multifaceted and encompasses several key objectives aimed at
addressing the evolving needs of educational institutions, administrators,
students, and job seekers.

• Enhance Financial Services: The primary purpose of the YesBank

project is to enhance financial services offered to clients through a range
of innovative digital solutions. This involves leveraging technology to
streamline banking processes, improve accessibility, and enhance the
overall customer experience.

• Optimize Transaction Processing: One of the key objectives is to op-

timize transaction processing across various services such as SmartPay,
IGTB, TallyKonnect, OBDX, eCollect, and API Banking. This includes
automating routine tasks, reducing processing times, and minimizing
errors to ensure smooth and efficient transaction management.

• Facilitate Digital Onboarding: Another important aspect of the project

is to facilitate digital onboarding for clients like Anand Rathi Pvt Lim-
ited, enabling them to easily onboard new customers and manage ac-
count openings through digital channels. This involves developing user-
friendly onboarding portals and integrating e-signature solutions for
seamless document signing.

• Improve Payment Solutions: The project aims to improve payment

solutions offered by YesBank, including SmartPay and eCollect, by en-
hancing security, expanding payment options, and providing real-time
transaction tracking capabilities. This includes integrating with third-
party payment gateways and implementing advanced fraud detection
mechanisms.

• Ensure Regulatory Compliance: Regulatory compliance is a crit-

ical aspect of the project, with the goal of ensuring that all services
provided by YesBank adhere to relevant banking regulations and stan-
dards. This includes implementing robust security measures, data en-
cryption, and compliance monitoring tools to protect customer data and
prevent fraud.

• Drive Business Growth: Ultimately, the purpose of the YesBank

project is to drive business growth by providing clients with innovative
and reliable banking solutions that meet their evolving needs. This
includes attracting new clients, retaining existing customers, and ex-
panding the range of services offered to stay competitive in the dynamic
banking industry.

9
In summary, the purpose of the Digital Onboarding For Banks project is to
revolutionize the education sector by streamlining administrative processes,
enhancing user experience, improving access to education, facilitating career
development, and promoting efficiency and innovation. Through these collec-
tive efforts,Digital Onboarding For Banks endeavors to create a more acces-
sible, equitable, and future-ready learning ecosystem that empowers individ-
uals to succeed in an increasingly competitive and dynamic world.

10
Chapter 2

Literature Survey

1. Digital Banking Trends and Innovations:

• Reviewing current trends and innovations in digital banking, including

advancements in mobile banking, online payment solutions, and digital
onboarding processes.

• Exploring case studies and industry reports highlighting successful im-

plementations of digital banking solutions by leading financial institutions.[1]

2. Technological Foundations:

• Examining the underlying technologies utilized in digital banking plat-

forms, such as Spring Boot, MySQL, Angular, and API banking frame-
works.

• Analyzing research papers and technical documentation to understand

the architectural principles, design patterns, and scalability considera-
tions relevant to backend and frontend development in digital banking.[5]

3. User Experience Design:

• Investigating user experience (UX) design principles and methodolo-

gies applied in the development of intuitive and user-friendly interfaces
for digital banking applications.

• Reviewing usability studies, UX research papers, and design guidelines

to identify best practices for enhancing user engagement and satisfac-
tion in digital banking platforms.[4]

4. Security and Compliance:

• Assessing security measures and compliance requirements applicable

to digital banking systems, including data encryption, authentication
mechanisms, and regulatory frameworks.

11
 • Surveying academic literature and industry publications on cybersecu-
rity threats, risk mitigation strategies, and regulatory compliance in
the context of financial services.[2]

5. Scalability and Performance Optimization:

• Investigating techniques for optimizing the scalability and performance

of backend systems in digital banking, such as database sharding, caching
mechanisms, and load balancing strategies.

• Reviewing performance benchmarking studies, optimization algorithms,

and architectural patterns aimed at improving system responsiveness
and throughput in high-traffic environments.[3]

6. Case Studies and Best Practices:

• Analyzing real-world case studies, success stories, and best practices

from leading financial institutions and fintech companies in the devel-
opment and deployment of digital banking solutions.

• Drawing insights from peer-reviewed research articles, industry whitepa-

pers, and conference proceedings to identify lessons learned and emerg-
ing trends in digital banking technology adoption.[6]

12
Chapter 3

Requirement Engineering

Before diving into the specifics of the development environment setup, it’s
essential to outline the hardware and software requirements necessary to
support the development of the Digital Onboarding For Banks platform. The
following requirements were identified and adhered to during the setup pro-
cess:

Hardware Requirements:

• Processor: ARM64 or x64 processor; Quad-core or better

• RAM: 8GB or higher

• Storage: 20-25GB free space; SSD recommended

• Display: 1920x1080 resolution or higher

Software Requirements:

• Operating System: Windows 11 64bit or higher

• Development Environment: Visual Studio Community Edition 2022

• Java SDK: Java SDK 8.0 or higher

• Database Management System: MySQL Workbench

The development environment for the Digital Onboarding For Banks plat-
form was meticulously set up to ensure compatibility, efficiency, and relia-
bility throughout the development lifecycle. The following steps were under-
taken to configure the development environment:

IntelliJ IDEA community edition:

13
• IntelliJ IDEA offers advanced code analysis and intelligent code com-
pletion features, including contextual suggestions, code refactoring tools,
and quick fixes, enhancing developer productivity and code quality.

• The IDE seamlessly integrates with version control systems like Git,
build tools such as Maven and Gradle, and popular frameworks like
Spring Boot and Hibernate, providing a cohesive development experi-
ence.

• IntelliJ IDEA supports a vast ecosystem of plugins, allowing developers

to customize their IDE with additional features and tools tailored to
their specific workflows and technologies.

Java SDK 8.0:

• Java SDK 8.0, also known as Java SE 8, is a major release of the Java
Platform, Standard Edition.This version of Java remains widely used in
enterprise applications and provides developers with tools for building
robust, high-performance software solutions.

MySQL Workbench:

• MySQL Workbench was selected as the database management tool for

designing, developing, and administering the MySQL database back-
end of the Trustt platform.

• The latest version of MySQL Workbench was downloaded and installed

from the official MySQL website, allowing for seamless interaction with
the database schema, tables, and stored procedures.

14
Chapter 4

System Design

The Digital Onboarding For Banks platform follows a multi-tier architecture,

comprising presentation, application, and data tiers.

Presentation Tier:
• This layer includes the user interface components accessible to clients.
It is typically implemented using web technologies such as Angular.
Application Tier:

• The application layer contains the business logic and processing com-
ponents responsible for handling user requests, executing application
workflows, and interacting with the data tier. It is implemented using
the Springboot framework, which facilitates the separation of concerns
and modular development.

Data Tier:

• The data layer consists of the database management system (DBMS)

responsible for storing and managing the application’s data. Educa-
tionERP utilizes MySQL as the relational database management sys-
tem (RDBMS) for storing student records, course information, admin-
istrative data, and other relevant data.

Architectural Patterns:
The system architecture of Digital Onboarding For Banks adheres to the fol-
lowing architectural patterns:

• Model-View-Controller (MVC): The MVC pattern separates the applica-

tion into three interconnected components: Model (data and business
logic), View (presentation layer), and Controller (user input process-
ing). This pattern promotes separation of concerns, modularity, and
testability, facilitating easier maintenance and extensibility of the sys-
tem.

15
• Client-Server Architecture: The project follows a client-server architec-
ture, where clients (web browsers) interact with a centralized server
to access application functionalities and retrieve data. This architec-
ture enables centralized data management, ensures consistency across
clients, and facilitates scalability by distributing processing tasks be-
tween clients and servers.

Designing a system for Trustt (formerly Novopay) involves creating

a robust and scalable architecture that can efficiently handle a wide
range of financial transactions while ensuring security, reliability, and
ease of use. Here’s an outline of the system design considerations for
this project:

• Modular Architecture: The system should be designed with a modular

architecture, consisting of distinct components for core banking func-
tions, digital payments, agent banking operations, and customer inter-
faces. This modular approach allows for easier maintenance, scalabil-
ity, and integration with third-party systems.

• Core Banking System: At the heart of the system is the core banking
platform, which manages customer accounts, transactions, balances,
and other essential banking functions. The core banking system should
be highly secure, scalable, and capable of handling large volumes of
transactions in real-time.

• Digital Payments Platform: Trustt’s digital payments platform enables

customers to perform a variety of financial transactions, including bill
payments, mobile recharges, money transfers, and merchant payments.
This platform should support multiple payment channels, including
web, mobile apps, USSD, and SMS, to cater to diverse customer needs
and preferences.

• Agent Banking Network: Trustt’s agent banking network serves as the

primary touchpoint for delivering financial services to customers in re-
mote and rural areas. The system should include features for agent
management, training, and monitoring, as well as tools for performing
agent transactions, managing liquidity, and reconciling accounts.

• Security and Compliance: Security is paramount in financial services,

and the system should incorporate robust security measures to protect

16
 sensitive customer data and transactions. This includes encryption pro-
tocols, access controls, authentication mechanisms, and regular secu-
rity audits to ensure compliance with regulatory standards.

• Scalability and Performance: As Trustt’s customer base grows and trans-

action volumes increase, the system should be able to scale horizontally
and vertically to accommodate higher demand. This may involve de-
ploying additional servers, optimizing database performance, and im-
plementing caching mechanisms to improve system responsiveness.

• Integration with Third-party Systems: The system should support seam-

less integration with third-party systems, including banks, payment
gateways, government databases, and other financial institutions. This
enables interoperability and data exchange between different systems,
facilitating smoother transactions and improving overall efficiency.

• Monitoring and Analytics: The system should include monitoring and

analytics tools to track system performance, detect anomalies, and gen-
erate insights into customer behavior and transaction trends. This
data-driven approach enables proactive problem-solving, performance
optimization, and informed decision-making.

• Data Management: A comprehensive data management strategy is cru-

cial for Trustt’s system design. This involves designing databases that
can efficiently store and retrieve customer account information, trans-
action records, agent details, and other relevant data. The system
should implement database normalization techniques, indexes, and par-
titioning to optimize data storage and retrieval performance. Addition-
ally, data backup and disaster recovery mechanisms should be in place
to ensure data integrity and availability.

• Transaction Processing: Trustt’s system must be capable of handling

a high volume of transactions securely and efficiently. Transaction
processing involves validating transaction requests, updating account
balances, generating transaction receipts, and ensuring transaction in-
tegrity. The system should employ transaction processing techniques
such as two-phase commit protocols, optimistic concurrency control,
and batch processing to minimize processing time and ensure data con-
sistency.

• API Integration: To facilitate integration with third-party systems and

services, Trustt’s system should expose APIs (Application Programming
Interfaces) that allow external applications to interact with the bank-
ing platform. These APIs should follow industry-standard protocols
such as RESTful APIs or SOAP APIs and provide secure access to bank-
ing functionalities such as account inquiries, fund transfers, and trans-

17
 action history retrieval. Proper authentication, authorization, and rate
limiting mechanisms should be implemented to control access and pro-
tect sensitive data.

• Compliance and Regulatory Requirements: Trustt’s system must com-

ply with regulatory requirements and industry standards governing fi-
nancial services, data privacy, and information security. This involves
implementing controls and safeguards to protect customer data, pre-
vent money laundering, and ensure adherence to Know Your Customer
(KYC) regulations. The system should maintain audit trails, conduct
regular compliance audits, and provide reporting capabilities to demon-
strate compliance with regulatory requirements.

• Scalability and High Availability: As Trustt’s customer base and trans-

action volume grow, the system must be able to scale horizontally and
vertically to handle increased demand. This requires deploying redun-
dant servers, load balancers, and caching mechanisms to distribute
workload evenly and improve system performance. High availability
features such as failover clustering, data replication, and automated
failover should be implemented to minimize downtime and ensure un-
interrupted service availability.

• Continuous Monitoring and Maintenance: Trustt’s system requires on-

going monitoring and maintenance to ensure optimal performance, se-
curity, and reliability. This involves monitoring system metrics such as
CPU usage, memory utilization, and network traffic, as well as conduct-
ing regular vulnerability scans and security audits. Automated alerts
and notifications should be set up to notify administrators of potential
issues or anomalies, allowing them to take proactive measures to ad-
dress them promptly.

• User Authentication and Authorization: Implementing strong user au-

thentication and authorization mechanisms is essential to ensure the
security of Trustt’s banking platform. This involves using techniques
such as multi-factor authentication (MFA), biometric authentication,
and token-based authentication to verify the identity of users accessing
the system. Role-based access control (RBAC) should be employed to
enforce granular access permissions, allowing users to access only the
functionalities and data relevant to their roles and responsibilities.

• Customer Support and Helpdesk Integration: Trustt’s system should

include features for customer support and helpdesk integration to pro-
vide assistance to users in case of inquiries, issues, or technical difficul-
ties. This may involve integrating with customer relationship manage-
ment (CRM) systems, ticketing platforms, and communication channels

18
 such as live chat, email, and telephone support. A centralized dash-
board for managing customer interactions and tracking support tickets
can help streamline the support process and improve customer satis-
faction.

• Regulatory Reporting and Compliance Monitoring: Trustt’s system should

include features for regulatory reporting and compliance monitoring to
ensure adherence to regulatory requirements and industry standards.
This involves capturing and aggregating data necessary for regulatory
reporting purposes, such as transaction data, customer information,
and audit logs. The system should generate regulatory reports in the
required format and frequency, facilitate regulatory audits and exam-
inations, and provide tools for monitoring compliance with regulatory
guidelines and directives.

Figure 4.1: MVC Architecture

19
Chapter 5

Implementation

Outline: This chapter presents the following:

1. A brief introduction
2. TAT Report
3. MSG file upload
4. Product Admin Portal
5. Email triggering to psm
6. Adding country code
7. Upload Blank page letter head
8. Summary

20
 A team can accomplish the project’s goals while staying within budget
and achieving pertinent deadlines by implementing a project that relies on
the strategic planning discussed earlier in the process. The phase of a project
cycle known as implementation connects the planning stage with the project
results. The success of a project ultimately depends on how successfully this
step of the process is carried out.
In this chapter, the above proposed features are briefly discussed. The
implementation steps of these features are discussed in this chapter.

5.1 TAT Report

The TAT report is a document that tracks and analyzes the turnaround time
for various processes or tasks within the project. Turnaround time refers to
the time taken to complete a specific activity from start to finish. In your
case, the TAT report likely focuses on tracking the time taken for different
stages or steps in a workflow.
• My contributions in the TAT Report include:

1. Exception Remarks: This column in the TAT report captures

any exceptions or deviations encountered during the process. These
exceptions could include errors, delays, or unusual circumstances
that affect the normal flow of the process. By documenting these
exceptions, we can identify areas for improvement and take cor-
rective actions to streamline the process.
2. COD Remarks: The COD remarks column in the TAT report
likely captures any remarks or comments from the COD role. The
COD role typically involves verifying and approving deposits or
transactions. The remarks may provide insights into the accu-
racy, completeness, or compliance of the transactions reviewed by
the COD.
3. NOC Maker and NOC Checker Remarks: NOC stands for "No
Objection Certificate" and in your project context, NOC Maker and
NOC Checker are roles involved in the issuance and verification of
NOCs. The remarks columns for NOC Maker and NOC Checker
capture any remarks or comments related to the NOC issuance
process. These remarks may include clarifications, approvals, or
rejections of NOC requests.
4. Integration with CSV File: Your task involves integrating the
exception remarks, COD remarks, NOC Maker remarks, and NOC
Checker remarks from separate tables or sources into a CSV (Comma-
Separated Values) file. This integration likely involves extracting
relevant data from the respective tables or sources and consolidat-
ing them into a structured format suitable for CSV export. The

21
 CSV file serves as a standardized format for sharing and analyz-
ing the TAT report data.

Overall, my task involved compiling and organizing information related

to exceptions, COD activities, and NOC processes into a comprehensive TAT
report in CSV format. This report enables stakeholders to track turnaround
times, identify bottlenecks, and make informed decisions to optimize the
project workflow.

5.2 MSG file upload

My task involved enabling the upload of MSG (Microsoft Outlook Message)
files across all products within a system or application, while also restricting
the upload of other file formats that are not supported or relevant.

1. Enabling MSG File Upload: MSG files are commonly used for email
messages in Microsoft Outlook. Enabling MSG file upload means al-
lowing users to upload MSG files from their local system or storage to
the application. This functionality could be useful for various purposes,
such as archiving email communications, sharing message threads, or
referencing email content within the application.

2. Across All Products: This indicates that the capability to upload MSG
files should be available across all products or modules within the sys-
tem. Regardless of the specific product or feature users are accessing,
they should have the ability to upload MSG files if needed. This ensures
consistency and uniformity in file upload functionality across different
parts of the application.

3. Restricting Other Formats: In addition to enabling MSG file upload,

the task involves implementing restrictions on other file formats that
are not supported or relevant to the system. This could include formats
such as PDF, DOCX, XLSX, or others that may not align with the ap-
plication’s requirements or use cases. By restricting these formats, you
ensure that users only upload files that are compatible and appropriate
for the system.

Overall, the task aims to enhance the file upload functionality by enabling
MSG file upload across all products while enforcing restrictions on unsup-
ported formats. This helps streamline the user experience, improve data in-
tegrity, and ensure that the application remains aligned with its intended
purpose and functionality.

22
5.3 Product Admin Portal
1. Objective: The objective of this task is to enhance the Product Admin
Portal by creating a new API that filters and displays only the products
relevant to a specific role, such as an auditor. This API aims to improve
the user experience and efficiency by presenting role-specific product
information to users.

2. New API Creation: The task involves creating a new API endpoint
within the system. This API will accept a role ID as input and re-
trieve the relevant product information based on the privileges associ-
ated with that role. The API will likely interact with the database to
fetch data from tables containing product details and role privileges.

3. Database Tables: Two new database tables are created as part of this
task: "ProductFeatureDetails" and "ProductRolePrivilege." These ta-
bles store information related to product features and role-specific priv-
ileges, respectively. The tables are designed to efficiently store and re-
trieve the necessary data for the new API.

4. Functionality: The new API is developed to provide role-based access

control to product information. When invoked with a specific role ID,
the API retrieves the products associated with that role from the database.
It then formats the data and returns it as a response to the API request.
The API ensures that only authorized users can access product infor-
mation relevant to their role.

Overall, the creation of this new API enhances the Product Admin Portal by
providing role-specific access to product information. It improves usability,
security, and efficiency by presenting users with tailored product data based
on their roles and privileges within the system.

5.4 Email triggering to psm

The task "Email triggering to PSM" involves enhancing the system’s func-
tionality to send email notifications to PSM users from various stages of the
process. Here’s an elaboration of the task:

1. Objective: The objective is to improve communication and notification

capabilities within the system by automatically sending email notifica-
tions to PSM users at critical stages of the workflow. This ensures that
PSM users are informed promptly about important events and actions
requiring their attention.

2. Integration with Email Sending Functionality: The task involves inte-

grating email sending functionality into key stages of the process. This

23
 includes stages such as client e-signature submission, COD (Checker
of Deposit) approval or rejection, and NOC (No Objection Certificate)
checker or maker actions. When these events occur, the system trig-
gers an email notification to the respective PSM user.

3. Mail Content Customization: The email content is customized to pro-

vide relevant information about the event or action that triggered the
notification. For example, the email may include details about the sub-
mitted e-signature, the status of a COD approval request, or the out-
come of a NOC checker review. This ensures that PSM users have con-
text and can take appropriate actions based on the notification.

Overall, the task enhances the system’s communication capabilities by

enabling automated email notifications to be sent to PSM users at critical
stages of the workflow. This improves transparency, efficiency, and collabo-
ration within the system by keeping PSM users informed and empowered to
take timely actions.

5.5 Adding country code

The task "Adding country code in request parameters for all products" in-
volves incorporating country codes into the request parameters for various
products within the system. Here’s an overview of the progress made for
each product:

1. IGTB: Country codes have been successfully added to the request pa-
rameters for IGTB.

2. API Banking: The addition of country codes to the request parameters

has been completed for the UserMatrixData.

3. TallyKonnect: Country codes have been integrated into the UserMatrix

for the Tally product.

4. SmartPay: The task has been accomplished for SmartPay by adding

country codes to the UserMatrixFields

5. Ecollect: Country codes have been successfully implemented in the Mis-

Reports.

Overall, significant progress has been made in adding country codes to the
request parameters for most products within the system.

24
5.6 Upload Blank page letter head
The task "Restricting the upload of blank PDF on clicking Upload blank let-
terhead involves implementing a validation mechanism to prevent users from
uploading blank PDF files. Here’s an elaboration of my task:

1. Identification of Requirement: The need to restrict the upload of blank

PDF files is recognized to maintain data integrity and usability within
the system. Blank PDF files may lead to confusion or errors in docu-
ment processing and should be avoided.

2. User Interface Modification: The user interface (UI) element for up-
loading a blank letterhead PDF is modified to include validation checks.
This may involve adding client-side scripting to the UI to verify the con-
tent of the uploaded file before submission.

3. Validation Logic: Upon clicking the "Upload blank letterhead" button,

the system performs validation checks to ensure that the uploaded PDF
file is not blank. Various criteria may be used to determine if a PDF is
blank, such as checking for the presence of text or non-white content
within the document.

4. Error Handling: If the uploaded PDF is found to be blank, appropriate

error messages are displayed to the user, indicating that blank PDF
files are not permitted for upload. This helps guide users and prevents
them from unintentionally uploading invalid files.

5. Backend Validation: Additionally, backend validation is implemented

to further enforce the restriction on uploading blank PDF files. This
ensures that even if client-side validation fails or is bypassed, the sys-
tem rejects blank PDF uploads during server-side processing.

Overall, significant progress has been made in adding country codes to the
request parameters for most products within the system.

5.7 Summary
This chapter discusses the implementation of some of the major tasks of the
project.

25
Chapter 6

Results

Outline: This chapter presents the following:

1. A brief introduction
2. Results
3. Summary

26
 The Result Analysis and Testing phase of the app involved thorough eval-
uation and validation of the implemented features to ensure functionality,
reliability, and user satisfaction. This phase encompassed various testing
methodologies and analysis techniques to identify and address any issues or
deficiencies in the application.
The following types of testing are performed on any developed system
before taking it to production (some kind of testing may not be applicable on
some system):

1. Unit Testing: Unit testing is a software testing technique in which

individual units or components of a software system are tested in isola-
tion, with the goal of verifying that each unit functions as intended. A
unit can be a function, method, or class.
The purpose of unit testing is to ensure that each unit of code performs
its intended function correctly, and that the integration of these units
works as expected. Unit tests are typically automated, and they are
designed to catch errors and defects early in the development process,
when they are easier and less expensive to fix.
Some of the benefits of unit testing include:

• Early detection of defects: Unit testing can detect errors and de-
fects early in the development process, which can save time and
money by avoiding more expensive fixes later on.
• Improved code quality: By testing each unit of code in isolation,
developers can ensure that their code is functioning as intended
and that it meets the required specifications.
• Better maintainability: Unit tests can help ensure that changes to
the codebase do not introduce new errors or regressions, making
it easier to maintain and modify the code over time.
• Faster development cycles: Unit testing can help speed up the
development process by catching errors early, reducing the time
spent on debugging and testing.

Some best practices for unit testing include:

• Writing tests that are independent of each other: Tests should be

written so that they do not depend on each other, which can help
ensure that each test is testing a specific functionality and that it
is not affected by other tests.
• Testing both positive and negative scenarios: Unit tests should
test both expected and unexpected scenarios, such as invalid in-
put, in order to ensure that the code handles these situations ap-
propriately.

27
 • Testing edge cases: Unit tests should test edge cases, such as the
minimum and maximum input values, in order to ensure that the
code handles these cases correctly.
• Automating tests: Unit tests should be automated in order to en-
sure that they are run consistently and that they can be easily
integrated into a continuous integration/continuous deployment
(CI/CD) pipeline.

2. Integration Testing: The purpose of integration testing is to ensure

that the interactions between different components of a software sys-
tem are working as expected and that the system as a whole meets the
required specifications. Integration testing can be particularly impor-
tant in complex software systems, where individual components may
work correctly in isolation but may fail when integrated with other com-
ponents.
Some of the benefits of integration testing include:

• Improved quality: Integration testing can help improve the overall

quality of a software system by detecting defects and errors that
may only appear when different components are integrated with
each other.
• Reduced risk: By identifying and addressing issues in the inte-
gration of different components early in the development process,
integration testing can help reduce the risk of problems arising
later in the development cycle or after release.
• Better communication: Integration testing can help identify com-
munication issues between different components, which can im-
prove communication and collaboration between development teams
working on different components.
• Enhanced reliability: Integration testing can help ensure that a
software system is reliable and performs as expected in different
environments and under different conditions.

Some best practices for integration testing include:

• Planning and design: Integration testing should be planned and

designed carefully, with a clear understanding of the components
that need to be tested, their dependencies, and the expected re-
sults.
• Test environment: Integration testing should be performed in an
environment that simulates the production environment as closely
as possible, in order to identify and address issues that may arise
in real-world scenarios.

28
 • Test data: Test data should be carefully selected and designed to
ensure that it covers all the possible scenarios that may occur dur-
ing integration testing.
• Automation: Integration testing should be automated whenever
possible, in order to reduce the time and effort required and to
ensure consistency in the testing process.

3. Load Testing: Load testing involves testing a software system un-

der heavy loads to evaluate its performance and behavior under high
stress conditions. The goal of load testing is to identify and eliminate
performance bottlenecks, and to ensure that the system can handle the
expected user load without degrading in performance or crashing.
Load testing is typically performed by simulating a large number of
concurrent users or requests, and by measuring the system’s response
time, throughput, and resource utilization. Load testing can be done for
different types of software systems, including web applications, APIs,
and databases.
Some of the benefits of load testing include:

• Improved system performance: Load testing can identify perfor-

mance bottlenecks in a software system, and can help developers
optimize the system for better performance under high loads.
• Enhanced reliability: Load testing can help identify issues related
to system stability and reliability, and can help ensure that the
system can handle heavy loads without crashing or losing data.
• Better scalability: Load testing can help ensure that a software
system can scale up or down as needed to handle changes in user
load or other demands.
• Improved user experience: Load testing can help ensure that a
software system provides a good user experience, even under high
loads.

Some best practices for load testing include:

• Planning and design: Load testing should be planned and de-

signed carefully, with a clear understanding of the expected user
load, the test scenarios, and the expected results.
• Test environment: Load testing should be performed in an envi-
ronment that simulates the production environment as closely as
possible, in order to identify and address issues that may arise in
real-world scenarios.
• Test data: Test data should be carefully selected and designed to
ensure that it covers all the possible scenarios that may occur dur-
ing load testing.

29
• Automation: Load testing should be automated whenever possi-
ble, in order to reduce the time and effort required and to ensure
consistency in the testing process.

30
6.1 Project Setup
1. Begin by opening your preferred code editor, such as Intellij IDEA

2. Create a folder in which the project will be stored.

3. Navigate to the folder and run Application.main file.

4. Import all necessary dependencies to initiate the project.

5. Launch the project.

6.1.1 Task 1
TAT Report

• The TAT report aims to provide insights into the Turnaround Time
(TAT) for various processes within the onboarding system. This
includes the time taken for each step in the onboarding process,
from initiation to completion.

31
 Expected Outcome

The expected outcome is a comprehensive report that displays TAT metrics

for different stages of the onboarding process. This report will allow stake-
holders to identify bottlenecks, optimize processes, and ensure efficient han-
dling of customer onboarding requests.

Figure 6.1: TAT columns

6.1.2 Task 2
MSG File Upload

• The purpose of enabling MSG file upload across all products is to en-
hance document management capabilities within the system. MSG files
are commonly used for email communications and may contain impor-
tant information relevant to the onboarding process.

Expected Outcome

By allowing users to upload MSG files, the system will facilitate the inclusion
of email communications and related documents in the onboarding process.
This will improve data completeness and streamline document management,
leading to more efficient processing of onboarding requests.

32
 Figure 6.2: msg file upload

6.1.3 Task 3
Product Admin Portal

• The Product Admin Portal is designed to centralize product manage-

ment tasks and provide administrators with a dedicated platform to
configure and manage product-related settings. This includes user ac-
cess controls, feature configurations, and other product-specific settings.

Expected Outcome

With the Product Admin Portal in place, product administrators will have
enhanced control and visibility over product configurations. They will be able
to efficiently manage user access, permissions, and other settings, leading to
better governance and administration of the onboarding system.

Figure 6.3: Product admin role

33
6.1.4 Task 4
Email Triggering to PSM

• The purpose of email triggering to PSM (Agent) users is to automate

the notification process and keep agents informed of relevant updates
and actions in the onboarding process. This includes notifications for
new tasks assigned, status updates, and requests for action.

Expected Outcome

By automating email notifications to PSM users, the system will ensure timely
communication and reduce manual intervention. Agents will receive notifica-
tions directly in their email inbox, allowing them to stay updated on onboard-
ing tasks and take necessary actions promptly, leading to improved efficiency
and responsiveness.

34
6.1.5 Task 5
Adding Country Code

• Adding country codes to request parameters aims to enhance data con-

textualization and localization within the system. This ensures that
system responses and outputs are tailored to the specific geographic
context of users, providing a more personalized user experience.

Expected Outcome

With country codes incorporated into request parameters, the system will be
able to provide localized responses and outputs based on the user’s country.
This includes displaying relevant information, applying country-specific rules
and regulations, and customizing user interfaces to meet the needs of users
from different regions.

Figure 6.4: country codes for different products

35
6.1.6 Task 6
Upload Blank Page Letterhead

• The purpose of restricting the upload of blank PDF files for letterhead
documents is to improve data integrity and usability within the system.
Uploading blank PDFs can lead to confusion and errors in document
management, so this feature aims to prevent such occurrences.

Expected Outcome

By implementing validation checks to prevent the upload of blank PDF files,

the system will ensure that users only upload valid letterhead documents
with content. This will enhance data integrity, reduce errors, and improve the
overall user experience when managing letterhead documents in the system.

Figure 6.5: Upload Blank Letter Head

36
Chapter 7

Conclusion

In conclusion, the Yes Bank Digital Onboarding Service represents a sig-

nificant milestone in the bank’s journey towards digital transformation and
customer-centric innovation. Through this project, Yes Bank has successfully
redefined the traditional account opening process, making it more accessible,
efficient, and secure for customers.

By leveraging advanced digital technologies and streamlined processes, the

Digital Onboarding Service has eliminated geographical barriers and time
constraints associated with physical branch visits, enabling customers to open
accounts remotely with ease. This has not only enhanced customer conve-
nience but has also expanded the bank’s reach to previously untapped mar-
kets and demographics.

Furthermore, the project has demonstrated Yes Bank’s commitment to regu-

latory compliance and data security by implementing robust identity verifica-
tion mechanisms and stringent security protocols. This ensures the integrity
and confidentiality of customer data, safeguarding against potential cyber
threats and fraudulent activities.

Moreover, the interoperability of the Digital Onboarding Service with ex-

isting banking systems and third-party verification services has enhanced
operational efficiency and collaboration across the banking ecosystem. This
seamless integration facilitates real-time data exchange and improves overall
process agility, enabling Yes Bank to stay ahead in a rapidly evolving digital
landscape.

Looking ahead, the success of the Yes Bank Digital Onboarding Service lays
a solid foundation for future digital initiatives and underscores the bank’s
position as a leader in digital banking innovation. As technology continues to
evolve and customer expectations evolve, Yes Bank remains committed to de-

37
livering innovative solutions that empower customers and drive sustainable
growth in the digital era.

38
Bibliography

[1] Peter-Jan Van De Venn. The evolution of digital banking. Journal of

Digital Banking, 7(4):365–377, 2023.

[2] Miren Karmele García, Eliseo Venegas, Esther Aguilera, José Manuel
Panizo, Charlotte Kelly, Diego Serrano, et al. Digital onboarding in fi-
nance: a novel model and related cybersecurity risks. Open Research
Europe, 1, 2021.

[3] Nageswararao Kanchepu. Digital transformation in banking industry:

cloud computing as a key enabler. International Numeric Journal of Ma-
chine Learning and Robots, 7(7), 2023.

[4] Renato Pinto Lopez et al. Study of user experience design of digital finan-
cial services. Master’s thesis, 2020.

[5] Deepankar Roy and Paritosh C Basu. Digital transformation of banking

institutions. India Banking and Finance Report 2021, 2021.

[6] Markus Wasserbauer. KYC onboarding in financial institutions: A best

practice criteria catalogue for selection of video identification frameworks.
PhD thesis, Technische Universität Wien, 2022.

39