Abstract: System and methods of conducting at Jeast one banking transaction using an electronic voucher channel are described. In one implementation, the method includes receiving a mobile number from a point of sale (POS) terminal. Further, a password is obtained from the POS terminal, corresponding to the mobile number. The method further comprises sending to a core banking solution (CBS) host system the password for validation. Based on the validation, the POS terminal is provided an access to a bank account for performing the at least or banking transaction.
FORM 2
THE PATENTS ACT, 1970 (39of 1970) & THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10, rule 13)
1. Title of the invention: ELECTRONIC VOUCHER CHANNEL
2. Applicant(s)
NAME NATIONALITY ADDRESS
("TATA CONSULTANCY Indian Nirmal Building, 9th Floor, Nariman Point,
pERVICES LIMITED | Mumbai, Maharashtra 400021, India
3. Preamble to the description
i
COMPLETE SPECIFICATION
The following specification particularly describes the invention and the manner in which it
is to be performed.
TLCHNICALFTLD
The present subject matter relates, 'in general, to systems and methods for performing
banking transactions through an electronic voucher channel.
BACKGROUND
Generally, a customer who is a holder of a bank card issued by a bank uses the bank
card for his financial transactions. The bank card includes debit cards, credit cards, prepaid cards, and charge cards. The bank card is used to perform financial or banking transactions, such as deposit funds, purchase items, withdraw funds, electronically transfer funds from one account to another, and check bank balance. Banks also provide other channels to their customers for performing banking transactions and operations. For example, branch banking and branchless banking are popular channels for providing banking services to the bank customers.
In a branch banking environment, a teller is provided within a branch of a bank. The
^pler helps the customers in conducting ! irking transections. For performing bank transactions, generally, the teller compares signature of a cu-.-iomer with the record available with the bank for authentication, before performing a requested banking transaction. Branchless banking is an alternative to the branch banking as the customer is not required to visit the branch of the bank for doing his banking transaction. For example, an automated teller machine (ATM), a point of sale (POS) terminal, and Internet banking have become a convenient mode of doing banking transactions from anywhere and at anytime without having to visit the branch. The ATM typically includes a card reader to read card details, a screen to display information, a mechanism for dispensing cash, and sometimes a writer to write to the bank card. A few ATM also includes a mechanism for accepting cash. The ATM typically includes a keypad for the customer to key in a personal identification number (PIN) for verifying the customer's credentials. Based on the validation of the credentials, the customer is allowed to perform piking transactions, such as withdraw cash, deposit cash, transfer funds, and pay bills.
SUMMARY
This summary is provided tc introduce concepts related to an electronic voucher
channel, and the concepts are further descnof .1 below h: the detailed description. This summary is neither intended to identify essential features of trie claimed subject matter nor is it intended for use in determining or limiting the scope of the clailed subject matter.
In accordance with one implementation, a method is described for performing at least
one banking transaction. The method includes receiving a mobile number of a customer from a point of sale (POS) terminal. In addition, the method includes obtaining a password, from the POS terminal, corresponding to the mobile number. The method further includes sending the password to a core banking solution (CBS) host system for validation. Based on the validation, the POS terminal is provided access to a bank account for performing the at least one banking transaction.
BRIEF DESCRIPTION OF THE FIGURES
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 thoughout foe drawings to reference like features and components:
Figure 1 illustrates a netwcik environment implementing a transaction processing
system in a banking environment, in accordance with an embodiment of the present subject matter;
Figure 2 illustrates a transaction processing system, in accordance with an embodiment
of the present subject matter;
Figure 3 illustrates a method of accessing a bank account for performing a banking
transaction by a bank customer in a POS service module, in accordance with an embodiment of the ^fcsent subject matter.
Figure 4 illustrates a method of accessing a bank account for performing a banking
transaction by a non-bank customer in a POS service module, in accordance with an embodiment of the present subject matter.
DATA.I ED DESCK.PTION
A bank is a financial institution that provides banking services and transactions, such as
accepting deposits, permitting withdrawals and bank transfers, to its customers through a unique bank account number assigned to each customer of the bank. The bank, through its branches, provides
branch-based banking services to the customers such as deposit and withdrawal of cash, transfer of funds, balance enquiry, issue of a cheque book, cheque status enquiry, issuance of account statement, and mobile and internet banking registrations.
Conventionally, in branch banking ,a customer has to visit a branch of the bank, in
person, where he is registered to perform hi: banking transaction. Nowadays, modern banks provide convenience to the customers allowing them to undertake banking transactions in providing the banking transactions without having to visit the branch. With the progress in the communication and the information technology, banking transactions can now be performed from anywhere and at anytime time. A core banking solution (CBS) has a CBS application software with a CBS bank database which is hosted on a CBS host system server. The CBS application software is based on a service-oriented-architecture (SOA) platform to improve processing time of the banking transactions. The SOA helps the bank to reduce risks that can result from manual data entry and use of out-of-date information, it further provides up-to-date operations-related information for management review.
The CBS provides easy, convenient, secure, fast, anytime and anywhere access to customers to their bank accounts and facilitates banking transactions from any of the networked methods or modes of banking, such as branch banidng with branch tellers, and branchless banking with automated teller machines (ATM), point office (POS) terminals, mobile banking, and Internet banking. To make the branch banking experience comformole, banks are making it easy for the customers to receive all types of services from one operator, popularly known as a teller. There are multiple such tellers in a branch depending upon the servicing load. In branchless banking, a bank card can be used to withdraw money from an ATM having a card reader and an interface. In some cases ATM can also be used to deposit the money. The ATM authenticates the bank card based on information provided to the ATM switch. Upon successful authentication, the ATM allows the customer to withdraw or deposit 4^h, or do other banking transactions.
The POS terminal is an electronic device that is used for verifying and processing the
bank card based banking transactions in a non-ATM environment, such as a retail shopping environment. In mobile banking, the banking transactions are performed through a mobile device, such as mobile phone, smart phone, or personal digital assistant (PDA). The Internet banking or online banking allows the customer to conduct his backing transactions through a bank's secure website using the Internet. In a branch banking environment, to facilitate CBS from any branch irrespective of whether he is registered with a branch from where he wishes to transact, each branch has a branch
server that communicates with the CBS host system server using a communication network. In branch banking ail banking services can be provided using the CBS.
The role of the branch is now becoming increasingly central to a bank's transformational
business strategies. A customer may transact from any other branch even if he is not registered therewith. Thus, by making the branch network ubiquitous, banks would like to use branch network more and more effectively.
Despite the spread of branchless banking modes, branch banking still finds favor with
many customers, such as senior citizens, low incomes groups, and less educated people. Many of the customers prefer visiting a branch for their regular banking transactions and are not yet comfortable with the use of ATM, POS, mobile phone banking, or internet banking. Branch banking is popular for many reasons, such as low penetration of the bank cards, credibility of the bank card based transactions, non-availability of the modern infrastructure in rural and remote semi-urban areas, atablished credibility of the branch based transactions, comfort in dealing with the teller with whom a customer may be dealing over years, and personalized services from bank employees. However, the bank incurs more cost in performing a banking transaction at a branch than using an electronic branchless banking medium. Electronic transactions are more cost effective. Thus, to save costs, banks can popularize branchless banking methods to reduce burden on the branch network and can also reduce transaction time of current branch backing process to accommodate more transactions using new technology. The use of branchless banking methods within a branch environment will further popularize branchless banking and will also help the bank to save in costs of the banking transactions.
Conventionally, even though technology has made the branch banking experience better,
but it is not comparable to branchless banking: the customers still have to spend a relatively considerable time and effort in making his banking transaction from the branch. In a conventional banking transaction process from the branch, the customer needs to fill-in a voucher with relevant details, sign it, and wait in a queue. The teller of the bank then needs to enter the details, which are filled-in by the customer, onto a teller screen and subsequently needs to authorize the transaction. Further, the bank performs the verification process on he next day, which involves checking of each voucher with the actual entry in the database to confirm that all the vouchers have been correctly entered in the system. This is an additional workload and consumes considerable time and efforts of the bank employees. The process also is not convenient for the customer. For example, it requires considerable time and efforts for filling-in voucher involving a number of details and then waiting in
the queue. This process therefore leads to poor use of infrastructure and wastage of paper used for printing vouchers.
The present subject matter discloses systems and methods for performing a banking
transaction through an electronic voucher channel, where credibility of branch banking and effortless features of branchless banking are combined together to give a convenient banking experience to a customer. In a POS based banking process, a bank account is accessed for performing a banking transaction using a POS terminal within a ba.ik branch for performing authentication and automatic data entry. Multiple banking systems, like a CBS host system server, a customer database, etc., communicate with each other to carry out the banking transaction. The POS based banking process provides a low cost alternative to ATM infrastructure by using the existing infrastructure of the bank branch. The POS based banking process does not require the voucher verification and voucher inventory management. Further, it also addresses issues, such as low utilization of cards and inability to
cross sell and up sell other bank products by the teller. The concerns of the customers, such as waiting the queue, voucher filling-in, manual errors in filling in account details and other information are also addressed.
The proposed system implements a POS-based banking process for performing financial
transactions in a branch banking environment. The system provides a self-service option to a customer so that the customer may utilize the time efficiently to complete a transaction through a teller within a branch environment. The banking transactions, such as balance inquiry, cheque book requests, passbook maintenance, and funds transfer. Futher, the POS based banking does not require filling-up of a voucher by the customer, entry of detail in the voucher, and subsequent voucher-verification by bank personnel. In one embodiment, a banking transaction is performed by a customer using electronic voucher channel, wherein a registered mobile phone number and a mobile personal identification Jfcmber (MPIN) are used for authorization. In another embodiment, a banking transaction is performed by a non-customer using the electronic voucher channel, wherein verification and identification of a non-bank customer are carried out through a mobile phone and a one-time password (OTP). The POS-based banking process can be enhanced further in carrying out various other banking transactions where minimum inputs are required from the customer. The process can also be used as a token system in the bank for effective queue management.
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
accessing a bank account for performing banking transactions by an electronic voucher channel 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)
Figure 1 shows a network environment 100 implementing a banking transaction
processing system 104 in a banking scenario. The transaction processing system 104 communicates, through a network A 116, with a CBS host system 102, a mobile banking server 106, and a switch 108, such as an ATM switch 108 and an electronic financial transaction (EFT) switch 108, and an SMS aggregator 110. The transaction processing s.-stem 104 further communicates, through a network B 118, with client devices 112-1, 112-2 ..., 122-V-' and POS terminals 114-1, 114-2 ..., and 114-N. The client devices can be collectively referred to as the client devices 112 and individually referred to as the client device 112. Similarly, The POS termk als can be collectively referred to as the POS terminals 114 and individually referred to as the POS terminal 114. The POS terminals 114 can be connected via ±e network B 118 to the transaction processing system 104 or to the client devices 112, using a local ^ired or wireless connection. The network environment 100 can have one or more than one transaction processing system 104. The transaction processing system 104 further includes a POS service module 122 and a front end database 120. A core banking application 124 works with a CBS database 126 on the CBS host system 102. In one implementation, the POS service module 122 may be a dedicated module to the POS terminal 114 in a branch.
With reference to Figure 1, the network environment 100 includes general purpose
computing devices in the form of the client devices 112. The network environment 100 also includes computing devices in the form of the transaction processing system 104 and the CBS host system 102 servers. The transaction processing system lOt and the CBS host system 102 may be implemented across multiple platforms, operating across a local network or across the Internet. Multiple computer systems, like the client devices 112, may communicate with one another and with the transaction processing system 104 using the network B 118. The client devices 112 include one or more entities, for example, tellers working in different operating units within a branch of a bank to meet their aspired business objectives.
In one implementation, computing devices may communicate with each other using
communication networks, such as the network A 116 and the network B 118. The communication network may be a wireless network, wired network or a combination thereof. The communication network can be implemented as one of the different t>pes 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), and Wireless Application Protocol (WAP), to communicate with each other. Further, the communication network may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices.
The computing devices like the client devices 112 may operate in a networked
environment using a communication network. It would be appreciated that the computing devices may be implemented as any of a variety of conventional computing devices, such as a server, a desktop PC, a notebook or portable computer, a workstation, a mainframe computer, a mobile computing device, an entertainment device, an internet appliance, a hand-held device, a peer device or other common network node.
The communication network delicted in Pgure 1 includes the network A 116 and the
network B 118, but may also include other networking environments. Such networking environments commonplace in offices, enterprise-wice computer networks, intranets and the Internet. The network A 116 or the network B 118 may be a wireless network, wired network or a combination thereof. The network 116 or the network B 118 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), and the internet. The network A 116 or the network B 118 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), etc., to communicate with each other. Further, the network A 116 or the network B 118 may include a variety of network devices, such as, routers, bridges, servers, computing devices, storage devices.
Each of the client devices 112 .-ollects the data related to different banking transactions
^Rhe CBS host system 102 deployed through ;he network environment 100. For handling and storing this data, the CBS host system 102 includes the CBS database 126 and the core banking application 124. The CBS database 126 of the CBS host system 102 may be used to store data temporarily or for permanent or long-term storage. For example, the transaction processing system 104 may collect data from one or more POS terminals 114 or client devices 112 and transform this data into forms that are compatible to be stored on the CBS database 126 in a standard form, combined form or other form for later retrieval.
The CBS database 126 stores data relating to the banking transactions as entered by the
teller using the client devices 112 or by the custonier using the POS terminals 114. The data entered is send to the transaction processing system 104 through the network B 118 and then to the CBS host system 102, also through the network B 118. In one implementation, the CBS host system 102 may also store data relating to errors that occurred while processing data by the teller or the customer. For example, a CBS host system may maintain error tables that store data errors that were captured while processing the data. In one implementation, the CBS database 126 of the CBS host system 102 can be stored at one or more locations locally, or remotely.
Furthermore, the transaction processing system 104 in the network environment 100
includes the POS service module 122 that receives the bank card data from'the POS terminal 114 and
transmits it to the ATM switch for authentication and, on receiving the authentication, as a response a
Primary account number is provided to the POS service module 122. The POS service module 122
communicates with the CBS host system 102 to get the customer information and transfers the data on
ascreen of the client device 112 for teller acceptance. Further to the teller acceptance, the POS service
module 122 sends acknowledgement details to the POS terminal 114 or to the SMS aggregator 110.
In one implementation, the mobile banking server 106 maintains a database of registered
mobile numbers and mobile PIN (MPIN) of the customers of the bank. These customers are registered with the bank for receiving acknowledgement of their banking transactions or for authenticating their mobile devices to do banking transactions using the mobile devices. The mobile banking server 106 uses the SMS aggregator 110 to send messages to the registered mobile numbers during banking transactions. In one implementation, when a relevant banking transaction, such as cash deposit, cash withdrawal, or account to account funds transfer, is requested by a customer using the registered mobile device, a specific message is forwarded by a POS service module 122 to a mobile banking server 106. fin receiving the authentication, as a response, a primary account number is provided to the POS service module 122. From there, a communr aticn is made with the CBS host system 102 to get the customer information. The details received frum the CBS host system 102 are then displayed on a screen of the client device 112 for teller acceptance. Further to the teller acceptance, the POS service module 122 sends acknowledgement details to the POS terminal 114 or to the SMS aggregator 110.
In another implementation, a non-bank customer could also perform the transaction like
cash deposit through the POS terminal 114. In such case, the transaction details and the non-bank customer's mobile number is entered on the POS terminal 114. The message from the POS terminal
114 is then transferred to the POS service r odule 122, from where message containing non bank customer's mobile number and a 'one time password' (OTP) is sent to the SMS aggregator 110. The message from the SMS aggregator 110 is then forwarded to the non bank customer's mobile number. On receiving the OTP, the non bank customer has to enter the OTP on the POS terminal 114 and the OTP is transferred to the POS service module 122. On successful validation of the OTP, the POS service module 122 provides the transaction related data to the client device 112. Further to the teller acceptance, the POS service module 122 sends acknowledgement details to the POS terminal 114 or to the SMS aggregator 110. In one implementation, a mobile banking server 106 is part of a CBS host system 102. The switch 108 is an electronic financial switch for intra institution banking transactions. In one implementation, switch 108 is adapted to interface with electronic financial switches of other institutions for inter institution transactions.
In one implementation, the POS terminal 114 includes a serial interface for external
vices, such as a printer, PIN keypad. In addition, the POS terminal 114 includes an Ethernet interface for connecting the POS to a local area netWv. ;-K and an inVrface using a transaction processing system 104 for connecting the POS terminal 114 to a global system for mobiles to utilize a mobile network. The POS terminal 114 is directly linked to the network B 118 and has a service provider independent IP address. The IP address provided to the POS terminal 114 is a static IP address. In one implementation, the POS terminal 114 includes a modem for providing a communication network with a transaction processing system 104, which is adapted to accept information from the POS terminals 114 and forward to a switch 108.
In one implementation, a POS terminal 114 is communicatively coupled to a client
device 112 and directly connected to a transaction processing system 104. The transaction processing
system 104, at the branch, is connected to the CBS host system 102, the switch 108, the mobile banking
diver 106, and the SMS aggregator 110 using a communication network. The POS terminal 114 can
also be enabled with a global system for mobiles (GSM) interface to utilize existing mobile networks.
The POS terminal 114 sends messages to fr.e EFT switch 108 or the ATM switch 108 in known
message formats. Various banking transacti .n's j:e possible from the POS terminal 114, such as balance
enquiry, cash withdrawal, cash deposit, funds transfer, pin change, reversals, settlement, cheque status,
passbook request, cheque book request, mob-'.e banking registration, and Internet banking registration.
The present description has been provided based on components of the network
environment 100 illustrated in Figure 1. However, the components can be present on a single
computing device wherein the computing device can be used for assessing the processes deployed in
the POS service module 122, and would still be within the scope of the present subject matter.
Figure 2 illustrates a transactior- processing system 104, in accordance with an
embodiment of the present subject matter. The -ransaction processing system 104 includes processor(s) 202, interface(s) 204, such as I/O interface(s), ar;.' memory 206 coupled to the processor(s) 202. The processor(s) 202 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) 202 are configured to fetch and execute computer-readable instructions stored in the memory 206.
The interface(s) 204 may include a variety of software and hardware interfaces, for
example, a web interface, a graphical user interface, etc., allowing the transaction processing system
104 to interact with the CBS host system 102, the mobile banking server 106, the switch 108, the SMS
^gregator 110, client device 112, and the POS terminal 114. Further, the interface(s) 204 may enable
the transaction processing system 104 to communicate with other computing devices, such as web
servers and external data servers (not shown in figure) or other communication networks (not shown in
figure). The interface(s) 204 can facilitate rr :i.;rjle communications within a wide variety of networks
and protocol types, including wired networks, f. v example LAN, cable, etc., and wireless networks
such as WLAN, cellular, or satellite. The interface(s) 204 may include one or more ports for connecting
the transaction processing system 104 to a number of devices to or to another server.
The memory 206 includes 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. The memory 206 Brcludes module(s) 208 and data 210.
The module(s) 208 further include the POS service module 122, a CBS access module
212, and other module(s) 214. The other module(s) 214 may include programs or coded instructions
that supplement applications and functions of the transaction processing system 104.
Additionally, the memory 206 further includes the data 210 that serves, amongst other
things, as a repository for storing data pr, rvssed, receded and generated by one or more of the module(s) 208 of the transaction processing system 104 and/ or by the CBS host system 102. The data 210 includes a front end database 120, access control data 216, authentication data 218, and other data
220. The other data 220 includes data generated as a result of the execution of one or more modules in the other module(s) 208.
The front end database 120, in the transaction processing system 104, may be a
relational database that stores the collected banking transaction data. The front end database 120 comprises of POS query tables that are used store the "anking transaction data entered on the POS terminal 114 for further processing. While one fruit end database 120 is shown, it will be appreciated that multiple front end databases are possible in one implementation. In one implementation, front end database 120 can be stored at one or more locations locally, or remotely.
In one implementation, transaction details for every banking transaction as received
from the POS terminal 114 are inserted in the POS query table of the front end database 120 with a pending status. The CBS application 124 keeps a check on the POS query table for entries with pending status. If there are any pending entries then the details of the entries will be pulled from the table and displayed on a display of a client device 112 corresponding to the transaction. When the entry is pulled Blm the POS query table, the status changes to request open. All the details are displayed to a teller on the display. The teller authorizes or declines the transaction. If the teller authorizes the transaction, a CBS database 126 table shall be updated and a confirmation message is sent to a transaction processing system 104. On receiving the message, the status of the entry in the POS query table changes to accepted. If the teller declines the transac'.lcr then the status of the entry in the POS query table changes to declined. On teller authorization, if the CBS application '24 sends back an error, the status of the entry in the POS query table changes tc transaction failed.
In an implementation, the POS terminal 114 receives access login credentials from the
customer. The login credentials may include, for example, user identification (user ID) using ATM card
cum debit card and a PIN, a mobile number, MPIN and biometric identification. Based on the login
credentials, the respective authentication system authenticates the user. Such authentication may be
PR-formed using an authentication technique. The POS service module 122 stores the transaction
details on successful authentication through authentication system in the authentication data 218.
In operation, an authentication sub-module (not shown in figure) authenticates the
customer based on the received login credentials as part of the authentication data 218. The modules of the authentication systems, such as the CBS access module 212 performs such authentication by sending the login credentials entered by the customer to the authentication database the CBS database 126 of the CBS host system 102, which coTipf^s the received login credentials with login credentials pre-stored in the authentication database of the C.BS database 126 If comparison indicates that the
login credentials provided by the customer are correct, an access is granted by the CBS application i 24
to the POS service module 122 and relevant access data is stored in the access control data 216. The
customer is authenticated and access to the POS terminal 114 is allowed based on the access control
data 216. On the other hand, if the comparison indicates that the login credentials provided by the
customer are incorrect, the customer authentication fails and access to the POS terminal 114 is
restricted until the correct login credentials are entered by the customer. In one implementation, an
authentication data 218 is placed in an external repository associated with a POS terminal 114.
A visual display of the corresncViding transactional data of the CBS application 124, its
processes and the associated CBS database 11:6 can be presented to the teller on the client devices 112 using the interface 204. When the customer requests verification of the customer's card details by swiping the bank card and entering the PIN at the POS terminal 114, the POS service module 122 will receive the data and will send the data using the other access module to the ATM switch 108 for verification. One or more of the computing devices can be utilized to implement the interface 204, Affile one or more of the computer server systems can be utilized to implement the CBS host system 102 and the transaction processing system 104.
Figure 3 illustrates a method 300 of conducting a banking transaction by a bank
customer in a POS service module, according to an embodiment of the present subject matter, whereas
Figure 4 illustrates a method 400 of conducting a banking transaction by a non-bank customer in a POS
service module, according to an embodiment of the present subject matter. The methods 300 and 400
may be described in the general context of coiiputer executable instructions. Generally, computer
executable instructions can include rauf.;n..s, programs, objects, components, data structures,
procedures, modules, functions, etc., that peii'jrm particular functions or implement particular abstract
data types. The methods 300 and 400 may also be practiced in a distributed computing environment
where functions are performed by remote processing devices that are linked through a communication
work. In a distributed computing environment, computer executable instructions may be located in
both local and remote computer storage media, including memory storage devices.
The order in which the methods 300 and 400 are 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 methods 300 and 400, or alternative methods. Additionally, individual blocks may be deleted from the methods 300 and 400 without departing from the spirit and scope of the subject matter described herein. Furthermore, the methods 300 and 400 can be implemented in any
suitable hardware, software, firmware, or combination thereof. The methods 300 and 400 are presently
provided for conducting a banking transaction by a customer in a POS service module.
Referring to method 300 as depicted in Figure 3, a request to perform a transaction is
received from a POS terminal operated by a bank customer, as depicted in block 302. A bank customer may be understood to be an account holder of the bank. In one implementation, the POS terminal 114 may be configured to receive the request from the bank customer. In said implementation, appropriate hardware, software or firmware or a combination thereof facilitates the bank customer to generate the request.
As illustrated in block 304, pioper authorization is provided to the bank customer to
carry out the transaction. In one implemenUii'o.:, a registered mobile number and a MPIN may be used by the POS terminal 114 to authenticate the bank customer's identity to the transaction processing system 104. In said implementation, the ban*< customer provides the registered mobile number and the MPIN to the transaction processing system 104 through the POS terminal 114.
As depicted in block 306, it is determined whether the transaction requested by the bank
customer pertains to funds transfer. Funds transfer is a common type of bank transaction in which money is transferred from the account of the bank customer to the account of a beneficiary customer using third party transfer or wire transfer. In one implementation, the bank customer selects appropriate option by pressing designated button(s) on the POS terminal 114.
If at block 306, it is determined that the transaction does not pertain to fund transfer,
then as shown in block 308, it is determined if the transaction is related to withdrawal or deposit of cash. In withdrawal of cash, for example, the ' iank customer withdraws money from the account of the bank customer, whereas in deposit of cash, mo.i.-jy is deposited in the account of the bank customer. It should be understood by those skilled in the art that deposit of cash also includes deposits made using ^wount payee cheques, pay orders, manac^r's cheque, banker's cheque, demand draft and other financial instruments.
If at block 308, it is determined, the transaction is not related to withdrawal or deposit of
cash, as shown in block 310, the bank customer is prompted to proceed with non financial transaction. Non financial transaction may be of various types, such as, request for a cheque book, request for account statement, request for change in profile information of the customer, request for activating/ availing various services provided by the bank.
If at block 306 it is determin-d that the transaction pertains to fund transfer, then as
shown in block 312, the bank customer is requested to provide the account number of the beneficiary customer. In one implementation, the POS terminal 114 facilitates the bank customer to enter the account number of the beneficiary customer using appropriate hardware, software or firmware or combination thereof.
As shown in block 314, on receiving the account number of the beneficiary customer,
various details pertaining to the beneficiary customer is received. In one implementation, the transaction processing system 104 generates and sends a request to the CBS host system 102 to retrieve various details pertaining to the beneficiary customer such as name of the beneficiary customer, type of account held by the beneficiary customer, branch associated with the beneficiary customer, and so on.
As depicted in block 316, lh^ v.rious deU"ls pertaining to the beneficiary customer is
provided to the bank customer for confirmation. Confirming the details pertaining to the beneficiary customer ensures that the transaction, i.e.the fund transfer, is being carried out in favour of the intended beneficiary customer and not in favour of anybody else. Further, this step rules out errors that may be caused due to wrong entry of account number of the beneficiary customer.
On confirming the details pertaining to the beneficiary customer at block 316 or on
determining the transaction is related to withdrawal or deposit of cash at block 308, as shown in block 318, the bank customer is prompted to enter the amount of transaction. The amount of transaction denotes the amount which is to be credited to the account of the beneficiary customer or the amount which is to be withdrawn from or deposited into the account of the bank customer.
As shown in block 320, the various details pertaining to the transaction are provided to
the bank customer for confirmation. The various details may include the amount of transaction, type of traisaction, date and time of transaction, etc. the bank 'Mtomer is prompted to confirm the details so as to rule out any typographical errors.
As depicted in block 322, a voucher, as identified by a unique voucher identification
code, henceforth referred to as voucher ID, is generated. The voucher includes details pertaining to the transaction requested by the bank customer. As illustrated in block 324, the various transaction details pertaining to the voucher is provided to a client device, such as the client device 112, operated by a teller of the bank. In one implementation, the voucher may be stored in a repository of pending transactions.
As depicted in block 326, trie teller is prompted to confirm the transaction. In one
implementation, the bank customer may request the teller to process his transaction. The teller may select the voucher from a list of pending transactions and confirm or reject the transaction based on various branch operational parameters, such as insufficient funds with Teller, incorrect amount entered by the customer. If, at block 326, the transaction is rejected by the teller, a notification is generated at block 330 so as to notify the bank customer or the beneficiary customer of the rejection of the transaction. The notification may be in form of an electronic mail, text message, printed receipt, etc.
If, at block 326, the transaction is confirmed by the teller, a request is generated at block
328 so as to update the account of the bank customer or the account of the beneficiary customer or both so that the transaction is reflected. As shown in block 330, necessary notification, in the form of an electronic mail, text message, printed receipt, etc., is provided to the bank customer or the beneficiary customer, so as to notify the bank customer or the beneficiary customer of the successful completion of the- transaction.
Referring to method 400 as depicted in Figure 4, at block 402, a request to perform a
banking transaction is received from a POS terminal, such as the POS terminal 114, operated by the non bank customer. A non bank customer is a person who does not have a bank account or other type of banking relationship with the bank and hence is not directly associated with the bank. In one implementation, the POS terminal 114 facilities the non bank customer to generate the request using appropriate hardware or software or firmware or combination thereof.
As depicted in block 404, a mobile number of the non-bank customer is received. In one
implementation, the non bank customer utilizes the POS terminal 114 to enter his mobile number. The mobile number is forwarded to the transaction processing system 104.
As shown in block 406, the non bank customer is provided with a one time password
(OTP). The OTP may be used only once, i.e. for processing one transaction. As shown in block 408, the non bank customer provides an account number of a beneficiary customer. In one implementation, the non bank customer uses the POS terminal 11"-!to-enterr the account number of the beneficiary customer.
As depicted in block 410, the various details pertaining to the beneficiary customer is
provided to the non bank customer for confirmation. In one implementation, the transaction processing system 104 transmits the account number of the beneficiary customer to the CBS host system 102. The CBS host system 102 retrieves various details pertaining to the account of the beneficiary customer and
transmits the same to the transaction processus system 104. The various details may include name of the customer, branch of the customer, etc. .coufirming the details pertaining to the beneficiary customer ensures that the transaction, i.e. the fund transfer, is being carried out in favour of the intended beneficiary customer and not in favour of anybody else. Further, this step rules out errors that may be caused due to wrong entry of account number of the beneficiary customer.
On confirming the details pertaining to the beneficiary customer at block 410, as shown
in block 412, the non bank customer is prompted to enter the amount of transaction and the OTP. The amount of transaction denotes the amount which is to be credited to the account of the beneficiary customer.
As depicted in block 414, a voucher, identified by a unique voucher identification code,
henceforth referred to as voucher ID, is generated. The voucher includes all the details pertaining to the transaction requested by the non bank customer. As illustrated in block 416, the various transaction deails pertaining to the voucher is provided \- a client device, such as the client device 112, operated by a teller of the bank. In one implementation, the voucher may be stored in a repository of pending transactions.
As depicted in block 418, the teller is prompted to confirm the transaction. In one
implementation, the non bank customer may request the teller to process his transaction. The teller may select the voucher from a list of pending transactions and confirm or reject the transaction based on various parameters such as insufficient funds, daily limit or cap imposed on the account of the bank customer, etc. If at block 418, the transaction is rejected by the teller, as shown in block 422, a notification is generated so as to notify the non bank customer or the beneficiary customer of the rejection of the transaction. The notification may be in form of an electronic mail, text message, printed receipt, etc.
If, at block 418, the transaction is confirmed by the teller, as shown in block 420, a
request is generated so as to update the accoiit of the beneficiary customer so that the transaction is reflected. As shown in block 422, necessar' notification, in the form of an electronic mail, text message, printed receipt, etc., is provided to the bank customer or the beneficiary customer, so as to notify the non bank customer or the beneficiary customer of the successful completion of the transaction.
In one implementation of methods 300 and 400, at any block, if a rule or a process or a
step fails or generates an error, proper notification may be generated so as to notify the customers as well as the teller of the error. Further various rules may be defined so as to validate the data entered by the bank customer or the non bank customer. •
Although implementations for electronic voucher channel have been described in
language specific to structural features and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as exemplary implementations for the electronic voucher channel.
I/We Claim:
1. A method for performing at least one banking transaction through an electronic voucher
channel, the method comprising:
receiving a mobile number from a point of sale (POS) terminal; obtaining a password, from the DOS terminal, based at least on the mobile number; sending, to a core banking solution (CBS) 1 usX system, the password for validation; and providing, based on the validation, POS terminal access to a bank account for performing the at least one banking transaction.
2. The method as claimed in claim 1, wherein the obtaining the password further comprises:
transmitting a request to the CBS host system for a one time password (OTP) corresponding to the mobile number through SMS aggregator; and receiving from the POS terminal, the OTP.
3. The method as claimed in claim 1, wherein the obtaining the password further comprises
«
eiving from the POS terminal, a mobile personal identification number (MPIN) as the password ■responding to the mobile number.
4. The method as claimed in claim 1, wherein the access to the bank account is provided for performing a self service by a customer.
5. The method as claimed in claim 1 further comprises sending to the POS terminal, a request for printing the at least one banking transaction completion receipt.
6. The method as claimed in claim 1 f';rih :;r comprises sending to the POS terminal, a request for printing a unique reference number on a receipt.
7. The method as claimed in claim 6 farther comprises receiving the unique reference number from an interface provided to a teller screen for receiving details of the at least one banking transaction.
8. The method as claimed in claim 7 further comprises receiving a completion authorization of the at least one banking transaction from the interface of the teller screen.
J±. A system for performing at least one banking transaction (104) through an electronic voucher channel comprising:
a processor (202); and
a memory (206) coupled to the processor, the memory (206) comprising, a point of sale (POS) service module (122) configured to,
receive a mobile number from a point of sale (POS) terminal (114); obtain a password from the POS terminal (114), wherein the password corresponds to the mobile number;
send the pass vor..i for validation to a core banking solution (CBS) host system (102); and
provide the POS terminal (114) an access to a bank account for performing the at least one banking transaction, based on the validation.
10. The system (104) as claimed in claim 9, wherein the POS service module (122) is further
configured to:
send a request to the CBS host system (102) for transmitting an one time password (OTP) to the mobile number; and
receive the OTP corresponding to the mobile number.
11. The system (104) as claimed in claim 9. wherein the POS terminal (114) is further configured to receive a mobile personal identification nui'.be-' (MPIN) as the password corresponding to the mobile number.
12. The system (104) as claimed in claim 9, wherein the POS service module (122) is further configured to send the OTP to the mobile number of a customer in the form of a text message delivered by a short message service (SMS).
13. The system (104) as claimed in claim 9, further comprising a core banking solution (CBS)
accss module (212) configured to authenticate a customer based on the login credentials.
14. The system (104) as claimed in claim 9, wherein the POS terminal (114) is further configured to receive a request for printing the at least one banking transaction completion receipt.
15. A computer-readable medium having embodied thereon a computer program for executing a method for performing at least one banking transaction through an electronic voucher channel comprising:
receiving a mobile number from a point of sale (POS) terminal; obtaining a password, from the .DOS terminal, corresponding to the mobile number; sending to a core banking solution (CBS) host system the password for validation; and providing, based on the validation, POS terminal ::n access to a bank account for performing the at least one banking transaction.
| Section | Controller | Decision Date |
|---|---|---|
| # | Name | Date |
|---|---|---|
| 1 | 2340-MUM-2011-FORM 13(19-12-2011).pdf | 2011-12-19 |
| 1 | 2340-MUM-2011-Written submissions and relevant documents (MANDATORY) [11-07-2019(online)].pdf | 2019-07-11 |
| 2 | 2340-MUM-2011-FORM 1(19-12-2011).pdf | 2011-12-19 |
| 2 | 2340-MUM-2011-Correspondence to notify the Controller (Mandatory) [07-06-2019(online)]-1.pdf | 2019-06-07 |
| 3 | 2340-MUM-2011-CORRESPONDENCE(19-12-2011).pdf | 2011-12-19 |
| 3 | 2340-MUM-2011-Correspondence to notify the Controller (Mandatory) [07-06-2019(online)].pdf | 2019-06-07 |
| 4 | 2340-MUM-2011-OTHERS [11-04-2018(online)].pdf | 2018-04-11 |
| 4 | 2340-MUM-2011-HearingNoticeLetter.pdf | 2019-05-24 |
| 5 | 2340-MUM-2011-FER_SER_REPLY [11-04-2018(online)].pdf | 2018-04-11 |
| 6 | 2340-MUM-2011-COMPLETE SPECIFICATION [11-04-2018(online)].pdf | 2018-04-11 |
| 6 | 2340-mum-2011-abstract.pdf | 2018-08-10 |
| 7 | 2340-MUM-2011-CLAIMS [11-04-2018(online)].pdf | 2018-04-11 |
| 8 | ABSTRACT1.jpg | 2018-08-10 |
| 8 | 2340-mum-2011-claims.pdf | 2018-08-10 |
| 9 | 2340-mum-2011-form 3.pdf | 2018-08-10 |
| 9 | 2340-MUM-2011-CORRESPONDENCE(2-9-2011).pdf | 2018-08-10 |
| 10 | 2340-MUM-2011-CORRESPONDENCE(21-9-2011).pdf | 2018-08-10 |
| 10 | 2340-MUM-2011-FORM 26(21-9-2011).pdf | 2018-08-10 |
| 11 | 2340-mum-2011-correspondence.pdf | 2018-08-10 |
| 11 | 2340-mum-2011-form 2.pdf | 2018-08-10 |
| 12 | 2340-mum-2011-description(complete).pdf | 2018-08-10 |
| 13 | 2340-mum-2011-drawing.pdf | 2018-08-10 |
| 13 | 2340-mum-2011-form 2(title page).pdf | 2018-08-10 |
| 14 | 2340-MUM-2011-FER.pdf | 2018-08-10 |
| 14 | 2340-MUM-2011-FORM 18(2-9-2011).pdf | 2018-08-10 |
| 15 | 2340-mum-2011-form 1.pdf | 2018-08-10 |
| 16 | 2340-MUM-2011-FER.pdf | 2018-08-10 |
| 16 | 2340-MUM-2011-FORM 18(2-9-2011).pdf | 2018-08-10 |
| 17 | 2340-mum-2011-form 2(title page).pdf | 2018-08-10 |
| 17 | 2340-mum-2011-drawing.pdf | 2018-08-10 |
| 18 | 2340-mum-2011-description(complete).pdf | 2018-08-10 |
| 19 | 2340-mum-2011-correspondence.pdf | 2018-08-10 |
| 19 | 2340-mum-2011-form 2.pdf | 2018-08-10 |
| 20 | 2340-MUM-2011-CORRESPONDENCE(21-9-2011).pdf | 2018-08-10 |
| 20 | 2340-MUM-2011-FORM 26(21-9-2011).pdf | 2018-08-10 |
| 21 | 2340-MUM-2011-CORRESPONDENCE(2-9-2011).pdf | 2018-08-10 |
| 21 | 2340-mum-2011-form 3.pdf | 2018-08-10 |
| 22 | 2340-mum-2011-claims.pdf | 2018-08-10 |
| 22 | ABSTRACT1.jpg | 2018-08-10 |
| 23 | 2340-MUM-2011-CLAIMS [11-04-2018(online)].pdf | 2018-04-11 |
| 24 | 2340-mum-2011-abstract.pdf | 2018-08-10 |
| 24 | 2340-MUM-2011-COMPLETE SPECIFICATION [11-04-2018(online)].pdf | 2018-04-11 |
| 25 | 2340-MUM-2011-FER_SER_REPLY [11-04-2018(online)].pdf | 2018-04-11 |
| 26 | 2340-MUM-2011-OTHERS [11-04-2018(online)].pdf | 2018-04-11 |
| 26 | 2340-MUM-2011-HearingNoticeLetter.pdf | 2019-05-24 |
| 27 | 2340-MUM-2011-CORRESPONDENCE(19-12-2011).pdf | 2011-12-19 |
| 27 | 2340-MUM-2011-Correspondence to notify the Controller (Mandatory) [07-06-2019(online)].pdf | 2019-06-07 |
| 28 | 2340-MUM-2011-FORM 1(19-12-2011).pdf | 2011-12-19 |
| 28 | 2340-MUM-2011-Correspondence to notify the Controller (Mandatory) [07-06-2019(online)]-1.pdf | 2019-06-07 |
| 29 | 2340-MUM-2011-Written submissions and relevant documents (MANDATORY) [11-07-2019(online)].pdf | 2019-07-11 |
| 29 | 2340-MUM-2011-FORM 13(19-12-2011).pdf | 2011-12-19 |
| 1 | 2340_MUM_2011_search_05-09-2017.pdf |