FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10, rule 13)
1. Title of the invention: Electronic BankBook
2. Applicant(s)
NAME NATIONALITY ADDRESS
TATA CONSULTANCY Indian Nirmal Building, 9th Floor, Nariman Point,
SERVICES LIMITED Mumbai 400021, Maharashtra, India
3. Preamble to the description
COMPLETE SPECIFICATION
The following specification particularly describes the invention and the manner in which it
is to be performed.

TECHNICAL FIELD
[0001] The present subject matter is related, in general to managing financial transactions and, in particular, but not exclusively to methods and systems for managing financial transactions.
BACKGROUND
[0002] On opening an account with a financial institution, such as a bank, an account holder is usually provided with a paper passbook or bank book. The passbook can be utilized by the account holder to record and maintain transaction records of his account. The passbook is generally provided in the form of a portable booklet, with a limited number of pages or leaves to record the transactions pertaining to the account of a user. In order to update the passbook with the transaction records, the user, or in this case the account holder, generally must avail printing facilities provided by a bank branch or self-service kiosks.
[0003] Banks generally provide a passbook printing facility for their account holders, where the account holder may request a bank employee or teller to update the leaves of his passbook with the transactions conducted in the account. The teller generally verifies the identity of the account holder before accommodating the passbook in a printing apparatus, such as the passbook printer, to print the transaction records of the user. In this manner, according to the convenience of the account holder, the account holder may maintain his financial transactions in his passbook. In the case where the passbook runs out of leaves, the account holder may, in a prescribed manner, request the bank to provide him with a fresh passbook.
SUMMARY
[0004] This summary is provided to introduce concepts related to financial transaction management, and the concepts are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.
[0005] In one implementation a method includes authenticating a user of an eBankBook associated with at least one bank account, receiving an update request pertaining to the financial transaction information from the eBankBook, based on the authentication, and forwarding the financial transaction information to the eBankBook, based on the update request.

BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to reference like features and components.
[0007] Fig. 1 illustrates a network environment implementing a financial transaction management system, in accordance with an implementation of the present subject matter.
[0008] Fig. 2 illustrates a method for managing financial transactions, in accordance with an implementation of the present subject matter.
DETAILED DESCRIPTION
[0009] Systems and methods for financial transaction management are described therein. The systems and methods can be implemented in a variety of computing devices, such as laptops, desktops, workstations, tablet-PCs, smart phones, notebooks or portable computers, tablet computers, mainframe computers, mobile computing devices, entertainment devices, computing platforms, internet appliances and similar systems. However, a person skilled in the art will comprehend that the embodiment of the present subject matter are not limited to any particular computing system, architecture or application device, as it may be adapted to take advantage of new computing system and platform as they become accessible.
[00010] A passbook is generally a portable paper booklet with a limited number of pages or leaves in which the account holder can record and maintain transaction data relating to the bank account. Each passbook usually relates to one bank account, therefore a user having more than one bank account in a bank can be provided with a passbook for each of the bank accounts. Furthermore, in the case where a user holds accounts in more than one bank, then the user can be provided with a passbook for each of the accounts in each of the banks.
[00011] At the convenience of the account holder, the account holder may choose to update his passbook with the latest transactions in his bank account. In order to do this, the account holder has to communicate his wish to the bank in person, to update the passbook. The account holder can go to a bank branch and request a bank employee or teller at a designated passbook desk or the account holder can avail the facilities of a self-service kiosk to update his passbook.

Generally, the teller, in response to this request, can perform a standardized authentication procedure by which the teller can verify an identity of the account holder with respect to the account. Conventional methods for authentication include photo identification using documents, such as a driving license or voter identity card, address verification using documents, such as a credit card bill or the like, and so on. Once the teller has authenticated the account holder, the teller can then proceed to procure the passbook from the account holder and accommodate said passbook in a passbook printing apparatus, such as a passbook printing machine. The teller can then obtain transaction related information, pertaining to the account of the account holder in question, for example, on a bank network computer, and execute a print command to the passbook printing machine. A similar approach sans the authentication procedure can be performed by the teller for any additional bank accounts held by the same account holder. In such a case, the teller will sequentially print the passbooks according to which account they relate to.
[00012] Generally, banks allot substantial manpower and resources towards the task of passbook updating. For example, the bank shall maintain an inventory of passbooks to be issued to customers, for which resources for warehousing and logistics need to be allotted. Moreover, the bank generally does not gain any revenue from this task, i.e., the account holder need not usually pay for the service of updating his passbook at the bank. In one example, the account holders who wish to update their passbooks generally must go to the bank and wait in queue along with other customers in order to be serviced by the teller. In another example, the account holder can be provided with the option of using a self service kiosk at the bank, where the account holder can update his passbook without the involvement of the teller. However, in both cases, the customers generally undergo a substantially high amount of waiting period before their request can be processed. Furthermore, the self service kiosks are generally substantially cost intensive for the bank to provide and maintain. In the first example, the teller may be occupied in some other job or responsibility at any given time, thus increasing the waiting period of the account holder. In the other example, there may be a limited number of self service kiosks and the account holders will have to queue to gain access to them. In other words, the dependency of the account holder on the bank teller and self service kiosks are substantially significant. The account holder must also remember to carry the required authentication documents as provided earlier, in case the self service kiosks are not available. And in some cases, if the account holder

does not provide the authentication documents, the teller can decline to update their passbooks. Furthermore, the paper passbooks are also substantially fragile and prone to damage and theft. Generally, in cases of passbook theft, there is no manner in which the passbook may be traced, and the account holder of said passbook generally has to request the bank to issue a new passbook for which the bank can charge the customer. Moreover, in case the passbook is damaged, destroyed, lost or stolen, the entire record of the transactions therein is lost. The result is that the account holder will have to request the bank for a substitute passbook along with the requisite fee, which is a substantially time and effort consuming task.
[00013] The present subject matter describes systems and methods for financial transaction management. In one implementation, the system according to the present subject matter can be implemented in a portable electronic device, such as an electronic bankbook hereinafter referred to as eBankBook. The eBankBook can be issued by a bank to a customer (hereby referred to as a user) who opens an account with the bank, and can be used by the user to securely record and maintain account transactional data. The eBankBook can be used to map the user to the one or more of his accounts with the same bank. In case the user possesses more than one account with the bank, a single eBankBook can be linked to these multiple bank accounts. In this manner, the user can be provided with a single portable device with which he may collectively record and maintain transactional data relating to his one or more bank accounts in a single bank. Furthermore, in one implementation, the eBankBook can be linked to multiple bank accounts across various banks. By providing a universal standard format in the form of guidelines and specifications with regard to maintaining financial transactions, say by a third party institution, each bank may accept the guidelines and specifications that adhere to the eBankBook and provide a customer friendly approach to utilizing a single eBankBook for multiple bank accounts across multiple banks.
[00014] In one example, the utilization of the eBankBook can assist environmental aid programs, such as the Go Green Initiative, by reducing the need for paper products and waste. Furthermore, the bank can maintain an inventory of all the eBankBooks to be issued to the users and assign each of the devices with a unique identification number, such as a Media Access Control (MAC) address, or Internet Protocol (IP) address, or the like, in order to track the eBankBook and to map each of the eBankBooks with a particular user. Moreover, while receiving the eBankBook, the user may be required to configure a password for authentication

purposes to access and use the eBankBook. The provision of a password also serves to protect the unauthorized use of the eBankBook. In one example, the user can be provided with a function to configure one password to access the eBankBook, and configure a second password in order to update the eBankBook. In a further example, the eBankBook can be provided with an integrated biometric scanner or card reader in order for the user to authenticate himself to update the eBankBook or to gain access to the information within the eBankBook. In one implementation, the eBankBook can be configured to operate in an online mode and an offline mode. In the online mode, the eBankBook is connected with the bank for authentication and updating purposes. In the offline mode, the eBankBook can perform the authentication and the update functions without being connected to the bank. In the offline mode, the eBankBook can be configured to perform an offline update process if the eBankBook is provided with mobile communication functionality. The online and offline modes are described in greater detail at a later stage. In one example, the bank may maintain a database of user authentication information so that, in the online mode, the bank can verify and authenticate the users before they update the eBankBook or gain access to the information in the eBankBook. In another example, the eBankBook can be configured to perform an authentication in the offline mode for accessing the stored information in the eBankBook, where the user authentication information can be stored within the eBankBook.
[00015] In case the user wishes to update the eBankBook with transaction data pertaining to his one or more bank accounts, the user may go to a bank branch or any designated area having connectivity to the bank, such as Automated Teller Machine (ATM) locations, where for example, a docking station can be provided. The docking station can be configured to provide connectivity to a bank branch server of a Core Banking System (CBS), and is described in detail at a later stage. Via these designated locations, the user can be provided with a secure location where the user can update the eBankBook. To this effect, the bank can provide designated eBankBook updating areas, docking stations or kiosks, where the user can then connect or dock the eBankBook to the docking station for updating purposes. In one example, if the docking station is located within a bank branch, then the docking station can be connected to the bank branch server, which in turn can be connected to a Core Banking System (CBS). In another example, depending on the architecture of the CBS, the docking station provided at locations

other than the bank branch, such as the ATM locations, can be configured to provide connectivity to a secure server, which in turn can be connected to the CBS.
[00016] In one example, in the online mode, the eBankBook can be connected to the docking station through a wired or wireless connection. Once the eBankBook is connected to the docking station, the user can be required to authenticate himself in the manner described earlier. Once the authentication is complete, the docking station can be configured to send a request to the CBS for fetching the user's account related information. The information thus received, can be presented to the user, for example, via an integrated screen in the eBankBook. Now, the user can select the accounts for which he wishes to execute an update request. For example, the user can be provided with an 'update all' button functionality, where all the accounts in the users name can be updated with transactional data. In another example, the user may specify which bank account to update, in furtherance to which, the user may also select a time period for which he wishes to update transactional data. Upon making the selection, the eBankBook can be configured to send an update request via the docking station, to the CBS. In response to the update request, the CBS can respond with the transactional data based on the selection made by the user. While receiving the data on the eBankBook, the user can be provided with a warning message, via the screen on the eBankBook, not to disconnect the eBankBook while the update is in progress.
[00017] Once the update is completed, the user can disconnect the eBankBook from the docking station. In one implementation, the bank can provide a separate printing facility, where the user can connect his eBankBook to a docking station, which is in turn connected to a printing kiosk or apparatus, and execute a print command. In one example, the printing apparatus can be provided integrated with the docking station, so that the user can issue the print command through the eBankBook to the printing apparatus while the eBankBook is connected with the docking station.
[00018] In one implementation, if the eBankBook is lost or stolen, the user can inform the bank of the same, for example, via a phone-banking helpline. The bank can then take suitable steps to trace the eBankBook or block the eBankBook as per bank policy. The bank may also issue a replacement eBankBook with a re-issue charge, after suitable verification and investigation into the matter.

[00019] In a further implementation, if an unauthorized attempt to access the eBankBook is received, either in the online mode or the offline mode, the bank may attempt to contact the user to request further information about said attempt. After a preconfigured number of unauthorized attempts, the bank may block the eBankBook for security purposes until the user contacts the bank.
[00020] These and other advantages of the present subject matter would be described in greater detail in conjunction with the following figures. While aspects of described systems and methods for management of financial transaction data can be implemented in any number of different computing systems, environments, and/or configurations, the embodiments are described in the context of the following exemplary system(s).
[00021] Fig. 1 illustrates a network environment 100 implementing a financial transaction management system 102 for managing data pertaining to bank account transactions, according to an implementation of the present subject matter. In said implementation, the financial transaction management system 102 is connected to and interacts with a plurality of user devices 104-1...104-N, collectively referred to as the user devices 104 and individually referred to as a user device 104. In one implementation, the user device 104 can be implemented as the eBankBook 104. In one example, the financial transaction management system 102 can be implemented at a financial institution, such as a bank. In another example, the financial transaction management system 102 can be implemented at the CBS. In yet another example, the financial transaction management system 102 can be a sub-system of a transaction system (CBS) deployed at the bank. The transaction system can be configured to receive a multitude of transaction update requests through the eBankBooks 104 and service the update requests. In an example, customers of the financial institution can send the transaction update requests through the eBankBooks 104. In said example, the financial transaction management system 102 can track the update requests received from the eBankBooks 104 and identify a channel used for the transaction update request. In an implementation, the financial transaction management system 102 can be implemented as the transaction system and can be configured to perform transactions based on the transaction requests received from the eBankBooks 104.
[00022] The financial transaction management system 102 may be implemented as any of a variety of conventional computing devices, including, for example, servers, a desktop PC, a

notebook or portable computer, a workstation, a mainframe computer, a mobile computing device, an entertainment device, and an internet appliance. The eBankBook 104 may be implemented as a portable hand held device with computing and communication capabilities, such as laptops, netbooks, notebooks, tablet computers, Personal Digital Assistants (PDA), mobile phones, multimedia enabled phones, or smart phones.
[00023] The financial transaction management system 102 is connected to the eBankBooks 104 over a network 106 through one or more communication links. The communication links between the financial transaction management system 102 and the eBankBooks 104 are enabled through a desired form of communication, for example, via dial-up modem connections, cable links, digital subscriber lines (DSL), wireless or satellite links, or any other suitable form of communication.
[00024] The network 106 may be a wireless network, wired network or a combination thereof. The network 106 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and such. The network 106 may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), to communicate with each other. Further, the network 106 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices.
[00025] In one implementation, the financial transaction management system 102 includes processor(s) 110 coupled to a memory 112. The financial transaction management system 102 further includes interface(s) 114, for example, to facilitate communication with the eBankBooks 104. The interface(s) 114 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, allowing the financial transaction management system 102 to interact with the eBankBooks 104. Further, the interface(s) 114 may enable the financial transaction management system 102 to communicate with other computing devices, such as web servers and external data servers (not shown in figure). The interface(s) 114 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, and wireless networks, such as WLAN,

cellular, or satellite. The interface(s) 114 may include one or more ports for connecting the financial transaction management system 102 to a number of devices to or to another server.
[00026] The processor(s) 110 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor(s) 110 is configured to fetch and execute computer-readable instructions stored in the memory 112. The memory 112 can include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
[00027] Further, the memory 112 includes module(s) 116 and data 118. In one implementation, the module(s) 116 include a transaction retrieval module 120, an authentication module 122, and other module(s) 124. The other module(s) 124 may include programs or coded instructions that supplement applications or functions performed by the financial transaction management system 102.
[00028] The data 118 includes a transaction retrieval data 126, an authentication data 128, and other data 130. The other data 130, amongst other things, may serve as a repository for storing data that is processed, received, or generated as a result of the execution of one or more modules in the module(s) 116. Although the data 118 is shown internal to the financial transaction management system 102, it may be understood that the data 118 can reside in an external repository (not shown in the figure), which is coupled to the financial transaction management system 102. The financial transaction management system 102 may communicate with the external repository through the interface(s) 114 to obtain information from the data 118.
[00029] In one implementation, the financial transaction management system 102 includes a repository of data, such as user data and standard account information etc. The user data can include but is not limited to name of the user, address of the user, photograph of the user etc. The standard account information for example, can be current interest rate, a/c opening date, limit and drawing power, and tenure of the account. In one example, the user data and the standard account information and transactions relating to the accounts can be stored in the other data 130.

For example, a user may use a device 104 to update his financial transaction data for one or more accounts in his possession. The financial transaction data can relate to credit or debit transactions associated with the bank account.
[00030] In an example, a user may possess more than one bank account at a bank where the financial transaction management system 102 can be implemented. The bank can issue a device, such as the eBankBook 104 to the user for storing and maintaining transactional records pertaining to his one or more accounts. The transactional records or information generally pertains to credit or debit transactions that occur in a bank account.
[00031] In one implementation, the eBankBook 104 includes processor(s) 111 coupled to a memory 113. The eBankBook 104 further includes interface(s) 115, for example, to facilitate communication with the financial transaction management system 102. The interface(s) 115 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, allowing the eBankBook 104 to interact with the financial transaction management system 102. The interface(s) 115 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, and wireless networks, such as WLAN, cellular, Bluetooth, Near Field Communication (NFC) technology, or satellite. The interface(s) 115 may include one or more ports for connecting the eBankBook 104 to devices such as docking stations and personal computing devices.
[00032] The processor(s) 111 of the eBankBook 104 operate similar to the processor(s) 110. The memory 113 can include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
[00033] Further, the memory 113 includes module(s) 117 and data 119. In one implementation, the module(s) 117 include a transaction module 132. The data 119 includes a transaction data 127.
[00034] In one implementation, the eBankBook 104 can be provided with an integrated biometric scanner or card reader in order to authenticate the user for using the eBankBook 104. For example, in order to access the information within the eBankBook 104, the user may be

required to authenticate himself by having to input a password, or run the biometric scanner, or the card reader.
[00035] In one implementation, the transaction module 132 can be configured to forward authentication information to the authentication module 122 in an online mode. At a server end, the authentication module 122 of the financial transaction management system 102 can be configured to receive the authentication information and verify the same by matching said information against records in the bank repository. On successful authentication, the user can be notified of the same, for example, via an integrated screen in the eBankBook 104. Therein, the user can be allowed to update the eBankBook 104 with transactional information pertaining to the one or more bank accounts of the user.
[00036] In one implementation, the eBankBook 104 can be configured to store transactional information in transaction data 127 integral to the eBankBook 104. The transaction data 127 can also be configured to store the authentication information as described earlier, so that the user can authenticate himself in an offline mode to access the information stored therein. In this implementation, the transaction module 132 can be implemented inter alia as an authentication module integral to the eBankBook 104, where the transaction module 132 can be configured to query the transaction data 127 with authentication information in order to perform the authentication of the user in the offline mode. In the offline mode, the eBankBook 104 is not connected to the financial transaction management system 102 via a docking station 103, and transactions only occur within the eBankBook 104.
[00037] In a further implementation, the eBankBook 104 can be configured with a unique Media Access Control (MAC) address, or Internet Protocol (IP) address, which for example, can be stored in the transaction data 127. The unique identification number can be used by the bank to identify and map each eBankBook 104 with one or more bank accounts of a given user or for other purposes, such as tracking. In one example, if the eBankBook 104 is lost or stolen, the bank can utilize the financial transaction management system 102 to track the movements of the eBankBook 104, and even block or disable it in certain cases. In another example, the bank may utilize an external tracking or monitoring system to track the eBankBook 104. The bank can provide a replacement eBankBook 104 in certain cases after suitable investigation has occurred. Moreover, the bank can charge a fee for the same.

[00038] In one implementation, the user may wish to update the transactional information relating to the one or more bank accounts on the eBankBook 104. In order to do so, the user may go to a bank where he holds said accounts or any secure designated area offering connectivity to the bank server, such as Automated Teller Machine (ATM) locations. In one example, the bank may provide its customers with dedicated docking stations where the user may securely connect the eBankBook 104 in order to update the eBankBook 104. In one implementation, depending on an architecture of a Core Banking System (CBS), a docking station 103 can be interfaced with a bank branch server and the CBS, for example, through the network 106. The CBS can be a centralized data center or server of a bank, where backend computations are performed and stored, for example pertaining to bank accounts of their customers.
[00039] Furthermore, the user may connect the eBankBook 104 to the docking station 103 via a secured wired (LAN, WAN, cable etc.) or wireless connection (WiFi, Bluetooth, NFC technology, etc.). Once the device 104 is successfully connected to the docking station 103, the user may initiate an update process on the eBankBook 104.
[00040] During the update process, the user can be initially required to authenticate himself in order to update the eBankBook 104. The user can input a password, or utilize the biometric scanner or card reader as described earlier in order to authenticate himself. In one implementation, the transaction module 132 of the eBankBook 104 can be configured to transmit the authentication information to the financial transaction management system 102 via the network 106 in the online mode. The authentication module 122 of the financial transaction management system 102 can be configured to receive the authentication information from the transaction module 132. Upon receiving the authentication information, the authentication module 122 can be configured to verify the received information, for example, against information stored in the authentication data 128 or the other data 130 of the financial transaction management system 102. In one example, the authentication module 122 can be interfaced with the docking station 103 at the bank.
[00041] The eBankBook 104 can also be configured to store user information such as name of the user, address of the user, photograph of the user, standard account information etc. This information can help prove the user authenticity to other institutes for Know Your Customer (KYC) purposes, which a growing number of banks are nowadays instituting. In one example,

the above mentioned information may be 'read only', i.e., the user may not be given write privileges to edit such data, but only view and print such information if required. In one implementation, the above mentioned information can be stored in the authentication data 128. In a further implementation, the transaction module 132 can be configured to store the name, address, photograph and standard account information in the transaction data 127, where such information can be queried and utilized in the offline mode. In one example, if any of the above information is changed in the financial transaction management system 102, such new information can be forwarded to the eBankBook 104 during the update process, for example, by a configuration of the authentication module 122.
[00042] Furthermore, upon successful verification of the authentication information, in the online mode, the authentication module 122 can be configured to forward a notification to the eBankBook 104 that the user has been successfully authenticated and may proceed with the update process. In an event where the user inputs incorrect authentication information, such as an incorrect password, the authentication module 122 can be configured to forward a failure notification to the eBankBook 104. In the offline mode, the transaction module 132 can be configured to notify the user that he has successfully been authenticated. During operation, the user can select specific bank accounts or all the accounts for which he would like to update the transaction information. In another example, the user device 104 can provide functionality where the user can specify a time period along with the user accounts for which he would like to update the user device 104. Upon making the selection, the transaction module 132 can be configured to forward an update request to the financial transaction management system 102.
[00043] In one example, the transaction module 132 can be configured to fetch a list of bank accounts, from the financial transaction management system 102, linked with the eBankBook 104 to the user, and based on the selection, forward the selection to the financial transaction management system 102 via the docking station 103. In one example, in case the user opens a new bank account, the transaction module 132 can be configured to fetch information pertaining to the new bank account during the update process from the financial transaction management system 102, and provide this information to the eBankBook 104. Once such information is received by the eBankBook 104, the transaction module 132 can be configured to store this information in the transaction data 127 for offline use. In one example, in case the user holds a bank account in more than one bank, the transaction module 132 can be configured to

automatically associate each bank account with the bank where the account resides. In one implementation, by the functionality of inter-bank operability of the eBankBook 104, irrespective of which bank the user goes to, the eBankBook 104 can be updated with regard to the transaction information. In this implementation, based on the account selection by the user, the transactional module 132 can be configured to forward the selection to the financial transaction management system 102, which can be implemented at the CBS of the requisite bank.
[00044] In one implementation, the transaction retrieval module 120 can be configured to receive the update request from the eBankBook 104. During the updating process, the eBankBook 104 can be configured to issue a warning to the user not to disconnect the device. Upon receiving the update request, the transaction retrieval module 120 can be further configured to scan the request and fetch transactional information, for example from the transaction retrieval data 126. Thereafter, the transaction retrieval module 120 can be further configured to forward the transactional information to the docking station 103. The docking station 103 in turn can update the eBankBook 104. In one implementation, the transactional information can be displayed to the user via an integrated screen on the eBankBook 104. In one example, the user can be provided with conveniently tabulated financial transaction information, pertaining to the one or more bank accounts of the user. The financial transaction information thus stored in the eBankBook 104 can be accessed in an offline mode by the user at his convenience after providing the required authentication.
[00045] Once the update process is complete, the user can disconnect the eBankBook 104 from the docking station 103. In one implementation, the bank can provide a printing facility for its customers who wish to obtain hard copies of the transactional information from their eBankBooks 104 for any specified time period. For example, a printing apparatus can be interfaced with the docking station 103, and a print command can be executed via the eBankBook 104, while the eBankBook 104 is connected to the docking station 103. In another example, a dedicated printing kiosk can be provided by the bank, where users can execute print commands through a wired or wireless connection to a printing apparatus. In one example, the bank can apply a fee to the users for availing the printing facilities.

[00046] In one implementation, the eBankBook 104 can be connected to a personal computing device, such as a laptop or desktop computer, to take periodic backups of the transactional information stored therein. This can be beneficial to the user in a case where the user can maintain a locally stored record of his bank account transactions. Therefore, in case the eBankBook 104 is lost, stolen, damaged or destroyed, upon the re-issue of a new eBankBook 104, the user can himself sync or update the eBankBook 104 with his bank account transactions without waiting for the bank to do the same.
[00047] In one implementation, the eBankBook 104 can also be provided with mobile communication hardware, such as in a mobile phone. For example, the bank can collaborate with a telecom operator and provide the eBankBook 104 with a Subscriber Identity Module (SIM) card. In this implementation, the eBankBook 104 can be tracked through the SIM card. Moreover, in case the user wishes to update the eBankBook 104 in an offline mode, the user may do so through Short Messaging Service (SMS) functionality.
[00048] In one implementation, the eBankBook 104 can be provided with a Graphical User Interface (GUI), via which the user can conveniently access the information stored within the eBankBook 104. In an example, the eBankBook 104 can be provided with a Thin Film Transistor (TFT) or a Liquid Crystal Display (LCD) screen in order to display information pertaining to the user accounts. The LCD or TFT screen as provided earlier can also be provided with touch technology, such as for implementation in a tablet computer or a smart phone. For example, a tabulated account statement including various details of the transactions therein can be displayed via the screen to the user. The various details can include a transaction date column, a transaction number, a short narrative on the transaction, a debit column, a credit column and an effective balance in the account. In another implementation, the GUI can also include navigational aids in order for the user to conveniently navigate through the different user accounts and their transactional information. In a further example, the eBankBook 104 can include a numeric keypad for input of numerical values and a directional keypad for directional navigation.
[00049] In a further example, the bank can provide a fund transfer facility via the eBankBook 104, where a user can transfer funds between his accounts in a bank via a functionality of the eBankBook 104. Further, the bank may associate radio frequency identification (RFID) tags with

the eBankBooks 104 owned by priority customers. Such customers may be granted certain privileges, for example, separate kiosks and no printing charges. In yet another example, the bank may carry out certain promotional or marketing campaigns through the eBankBook 104.
[00050] Fig. 2 illustrates a method 200 for managing financial transaction data, according to one implementation of the present subject matter. The method 200 may be implemented in a variety of computing systems in several different ways. For example, the method 200, described herein, may be implemented using the financial transaction management system 102, as described above.
[00051] The method 200, completely or partially, may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. A person skilled in the art will readily recognize that steps of the method can be performed by programmed computers. Herein, some embodiments are also intended to cover program storage devices, e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of the described method 200.
[00052] The order in which the method 200 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternative method. Additionally, individual blocks may be deleted from the method without departing from the spirit and scope of the subject matter described herein. Furthermore, the methods can be implemented in any suitable hardware, software, firmware, or combination thereof. It will be understood that even though the method 200 is described with reference to the financial transaction management system 102, the description may be extended to other systems as well.
[00053] At block 202, in order to authenticate a user of the eBankBook 104, authentication information for an eBankBook 104 is received. The eBankBook 104, as described earlier, can be an eBankBook issued by a bank to its customer on opening of a new account. The eBankBook 104 can be provided with a security means, such as a biometric scanner, a card reader, or password protection functionality, with which the user can authenticate himself for gaining

access to the information stored therein and subsequently to perform an update of the eBankBook 104. In one example, the user can be provided with an option to configure one password to gain offline access to the information stored in the eBankBook 104, and another password to perform an online update process regarding the financial transactions. The user can also be provided with an option to modify the existing passwords if he wishes. In one implementation, the eBankBook 104 can be connected to a docking station 103 as disclosed earlier, for example at a bank. The authentication information can be forwarded through a docking station 103, and received as described earlier, by a financial transaction management system 102 at a server side.
[00054] At block 204, the authentication information can be verified against a reference database. For example, as described earlier, the authentication information can be compared against a bank data repository containing information pertaining to user accounts and transactions thereof. As described earlier, the authentication information can be a user password, biometric scanner information, magnetic stripe card information, such as information from a debit card, or smart card information, such as information from a credit card owned by the user. Upon successful verification of the authentication information, the user can be informed, for example, via the eBankBook 104.
[00055] At a block 206, based on the verification in the block 204, an update request can be received, for example, by the financial transaction management system 102 from the eBankBook 104. For example, upon successful verification at a server end, the user can be allowed to update account information in the eBankBook 104 and further provided with an option to select for which user account he wishes to receive updated transaction details. Furthermore, the user can also be provided with an option to specify a particular time period for which he wishes to update the selected bank account(s) with the transactional information. In an example, the eBankBook 104 can have a Graphical User Interface (GUI), via which the user can conveniently access account information. In yet another example, via the graphical user interface of the eBankBook 104, the user can be provided with an 'update all' button, which executes an update request to update all the accounts in the user's possession, with transaction information from the last update executed by the user.

[00056] At a block 208, once the update request has been sent by the user, the financial transaction information can be forwarded to the user device. For example, the transaction retrieval module 120 can be configured to forward the financial transaction information to the eBankBook 104 as described earlier. In one implementation, as the user device is receiving said transactional information, the user can be warned against disconnecting the eBankBook 104 during said process. The financial transaction information may include any one a transaction date, a transaction number, a text description of the transaction, a debit information, a credit information, an effective balance in the bank account, and an account information. The account information may include, for example, current rate of interest enjoyed by the user, account opening date, and drawing power, i.e., withdraw limit.
[00057] Although implementations of managing financial transaction data have been described in language specific to structural features and/or methods, it is to be understood that the present subject matter is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as implementations for managing financial transaction data.

I/We Claim:
1. A computer implementable method to manage financial transaction information for at
least one bank account, the method comprising:
authenticating a user of an eBankBook associated with the at least one bank account;
receiving an update request from the eBankBook pertaining to the financial transaction information, based on the authentication; and
forwarding the financial transaction information to the eBankBook, based on the update request.
2. The method as claimed in claim 1, wherein the authenticating comprises:
receiving authentication information from the eBankBook comprising at least one of a user password, biometric scanner information, magnetic stripe card information, and smart card information; and
verifying the received information against a reference database.
3. The method as claimed in claim 1, wherein the authenticating further comprises forwarding one of a success notification and a failure notification to the eBankBook based on the received authentication information.
4. An eBankBook (104) for managing financial transaction data for at least one bank account, the eBankBook (104) comprising:
a processor (111); and
a memory (113) coupled to the processor (111), the memory (113) comprising:
a transaction module (132) configured to:
obtain authentication information in order to authenticate a user; and
receive financial transaction information pertaining to at least one bank account of the user from a financial transaction management system (102), based on the authentication.

5. The eBankBook (104) as claimed in claim 4, wherein the transaction module (132) is further configured to store the financial transaction information in a transaction data (127).
6. The eBankBook (104) as claimed in claim 4, wherein the transaction module (132) is further configured to store a user name, user address, user photograph, and standard account information.
7. The eBankBook (104) as claimed in claim 4, wherein the transaction module (132) is further configured to authenticate the user in an online mode by forwarding data to the financial transaction management system (102).
8. The eBankBook (104) as claimed in claim 4, wherein the transaction module (132) is further configured to authenticate the user in an offline mode by querying reference information stored in a transaction data (127).
9. The eBankBook (104) as claimed in claim 4, wherein the eBankBook (104) further comprises at least one of an integrated biometric scanner and a card reader in order to obtain the authentication information.
10. The eBankBook (104) as claimed in claim 4, wherein the eBankBook (104) is connected to a docking station (103) in order to update the eBankBook (104) with the financial transaction information from the financial transaction management system 102.
11. The eBankBook (104) as claimed in claim 4, wherein the transaction module (132) is further configured to execute a print command to a printing apparatus in a secured environment via a docking station (103).
12. The eBankBook (104) as claimed in claim 4, wherein the eBankBook (104) further comprises a screen configured to display the financial transaction information to the user.
13. The eBankBook (104) as claimed in claim 4, wherein the eBankBook (104) further comprises wired and wireless communication technology for communication with a docking station (103).
14. The eBankBook (104) as claimed in claim 4, wherein the eBankBook (104) comprises Near Field Communication (NFC) technology.

15. The eBankBook (104) as claimed in claim 4, wherein the eBankBook (104) comprises mobile communication hardware.
16. A financial transaction management system (102) for managing financial transaction information for at least one bank account, the financial transaction management system (102) comprising:
a processor (110); and
a memory (112) coupled to the processor (110), the memory (112) comprising:
an authentication module (122) configured to verify authentication information received from an eBankBook (104); and
a transaction retrieval module (120) configured to forward the financial transaction information of the at least one bank account, to the eBankBook (104), based on the verification.
17. The financial transaction management system (102) as claimed in claim 15, wherein the authentication module (122) is configured to receive at least one of a user password, biometric scanner information, magnetic stripe card information and smart card information from the eBankBook (104).
18. The financial transaction management system (102) as claimed in claim 15, wherein the financial transaction information comprises at least one of a transaction date, a transaction number, a text description of the transaction, a debit information, a credit information, an effective balance in the bank account, and an account information.
19. A computer-readable medium having embodied thereon a computer program for executing a method comprising:
authenticating a user of an eBankBook associated with the at least one financial institution account;
receiving an update request from the eBankBook pertaining to the financial transaction information, based on the authentication; and
forwarding the financial transaction information to the eBankBook, based on the update request.

20. A computer-readable medium having embodied thereon a computer program for executing a method comprising:
obtaining authentication information in order to authenticate a user; and
receiving financial transaction information pertaining to the at least one bank account of the user from the financial transaction management system, based on the authentication.