Technical Field
Embodiments of the present disclosure relate to devices and associated methods for providing authentication to a transaction, and more specifically, but not limited to, a system and method for providing such authentication to digital wallets and card associations on Point of Sale Terminal (POS).
Background
Currently, various physical cards are used to perform transactions over Point Of Sale (PoS) terminals which are placed at merchant locations. However, there is a constant thrust towards eliminating the requirement of carrying physical cards to a Merchant location in addition to the growth of new digital forms of payments. Allowing users to perform transactions without a physical card is increasing becoming popular. In addition, with the advent of digital-wallets it is becoming increasingly necessary to enable digital-wallets with the existing Point of Sale (PoS) terminals. This is because existing Point Of Sale (PoS) terminals are not capable to transact with e-wallets which are not physical cards as well as mechanism being developed by the current physical card schemes that work without physical cards. Also, existing PoS (Point Of Sale) terminals are not capable to transact with digital-wallets or payment associations that implement and use a QR CODE provided by a wallet issuer or the payment association. Thus, the present Point Of Sale (PoS) terminals suffer from at least following limitations. - Incapable to perform secure transaction in the absence of physical cards e.g. with e-wallets or other forms launched by the payment associations - Incapable to perform transactions where e-wallets or payment associations have a QR code provided by a wallet issuer
Therefore, there is a long felt need
- to provide a seamless means to authenticate owners of digital wallets (without physical cards) and like instruments at existing point of sale terminal and
- to allow existing Point Of Sale Terminals (PoS) to transact with digital wallets having a QR code provided by the provider issuing Digital wallet or the payment associations.
To achieve above mentioned and many other objectives the present invention proposes upgrading the Point Of Sale Terminals (PoS) as an embedded hardware capable of transacting with digital wallets and all new mechanism of payments being released by payment associations.
Summary
For purposes of summarizing, certain aspects, advantages, and novel features of the disclosure have been described herein. It is to be understood that not necessarily all such advantages may be achieved in accordance with any one particular embodiment of the disclosure. Thus, the present
3
disclosure may be embodied or carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other advantages as may be taught suggested herein.
It is an object of the present invention to allow a holder of a digital wallet or the latest mechanism promoted by payment associations to transact on a Point of Sale (POS) terminal.
It is an object of the present disclosure to provide a combination of a web application hosted on servers in secure Data Centre and a POS terminal application residing on one or more POS networks for acceptance of available service providers.
In an embodiment of the present invention details of multiple service providers and multiple Banks (or Transaction Processing Organizations) are abstracted centrally. This allows for mapping of authentication data from any transaction originating service providers to any of the Banks, via a seamless interface.
In an embodiment, the present invention allows for switching of the transaction data to specific service provider “Bank” based on predefined criteria defined by POS application.
All the embodiments as herein described with respect to the present invention are applicable to the method and the corresponding system.
These and other embodiments of the present disclosure will also become readily apparent to those skilled in the art from the following detailed description of the embodiments having reference to the attached figures, the disclosure not being limited to any particular embodiments disclosed.
Brief Description of the Drawings
For a better understanding of the embodiments of the systems and methods described herein, and to show more clearly how they may be carried into effect, reference will now be made, by way of example, to the accompanying drawings, wherein:
FIGURE 1 illustrates a diagrammatic representation of an architectural environment in which the present invention operates, in accordance with one or more embodiments of the present disclosure.
FIGURE 2 illustrates exemplary network environment wherein POS Terminal, Banking Acquirers and the service providers such as digital wallets operate.
FIGURE 2 (a) illustrates an exemplary Point of Sale (PoS) terminal with proprietary GUI interface of HUB application of the present invention.
FIGURE 3 illustrates a flow diagram depicting an exemplary transaction done using any Prepaid Instrument or Prepaid Wallet issuer using Mobile Number and One Time Password (OTP).
FIGURE 4 illustrates an exemplary flow diagram for depicting transactions via service provider / Prepaid Instrument or Prepaid Wallet issuer using Mobile Number and a pre-generated OTP.
4
FIGURE 5 illustrates a flow diagram depicting an exemplary transaction via service provider/ Prepaid Instrument or Prepaid Wallet issuer using a Token number pre-generated by a mobile app of a user.
FIGURE 6 illustrates a flow diagram of a Terminal Management System (TMS) of the present invention for Multi-Vendor Terminals.
FIGURE 7 illustrates a flow diagram for an exemplary transaction in line with the present invention using QR code for a Wallet issuer or a payment card.
FIGURE 7 (a) An exemplary Point of Sale (PoS) terminal printing dynamic QR code of the via proprietary HUB application of the present invention.
FIGURE 8 illustrates a flow diagram of an exemplary Transaction of the present invention wherein the UPI Interface implemented on the POS machine. This would be similar to Figure 7 as well.
Detailed Description
Exemplary embodiments now will be described with reference to the accompanying drawings. The disclosure may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey its scope to those skilled in the art. The terminology used in the detailed description of the particular exemplary embodiments illustrated in the accompanying drawings is not intended to be limiting. In the drawings, like numbers refer to like elements.
The specification may refer to “an”, “one” or “some” embodiment(s) in several locations. This does not necessarily imply that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments.
As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes”, “comprises”, “including” and/or “comprising” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Furthermore, “connected” or “coupled” as used herein may include operatively connected or coupled. As used herein, the term “and/or” includes any and all combinations and arrangements of one or more of the associated listed items.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
5
The figures depict a simplified structure only showing some elements and functional entities, all being logical units whose implementation may differ from what is shown. The connections shown are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the structure may also comprise other functions and structures. It should be appreciated that the functions, structures, elements and the protocols used in communication are irrelevant to the present disclosure. Therefore, they need not be discussed in more detail here.
Also, all logical units described and depicted in the figures include the software and/or hardware components required for the unit to function. Further, each unit may comprise within itself one or more components which are implicitly understood. These components may be operatively coupled to each other and be configured to communicate with each other to perform the function of the said unit.
The features provided by the disclosed system in the present disclosure, may be wirelessly accessed remotely, in one or more embodiments, and/or through a wireless network. Such types of wireless network service providers operate and maintain the computing systems and environment, such as server system and architectures. Typically, server architecture includes the infrastructure (e.g. hardware, software, and communication lines) that offers wireless network services. The operations in embodiment of the present invention are performed wirelessly during on-air or air interface.
The terms BPES, BHES wherever used shall be construed as being referring to HOST (server) proposed by the present invention that is implemented as combination of hardware and software.
For the most part, the operations described herein are operations performed by a handset, device, computer or a machine in conjunction with a human operator or user that interacts with the computer or the machine. The programs, modules, processes, methods, data, and the like, described herein are but an exemplary implementation and are not related, or limited, to any particular computer, apparatus, or computer language. Rather, various types of general purpose computing machines or devices may be used with programs constructed in accordance with the teachings described herein.
The present invention enables the details of multiple service providers and multiple Banks/Acquirers to be abstracted centrally – thereby allowing for mapping of the transaction details from any transaction originating service providers to any of the Acquirers by creating a seamless interface that operable via both the POS (Point Of Sale Terminal) and an Enterprise server of the present invention.
As indicated, the term “Acquirer” within the purview of the present invention shall refer to Banks or transaction authentication and processing organizations (which are couple to a Bank).
It is well known that bank places POS (Point Of Sale) terminals at Merchant Establishments enabling the Merchant to authenticate and process transactions whose acceptance is enabled on the POS terminals.
Similarly, payment service providers comprise of Instrument companies, Digital Wallet providers, payment associations and any other value added services providers.
6
Also, a Point of Sale (POS) terminal is an electronic device present at various Merchant Establishments which allow the merchant to authenticate and accept payments by various debit/credit card schemes. Such POS are deployed at Merchant Establishments by Acquirers to accept payments by Debit / Credit cards.
The present invention allows for switching of the transaction details to relevant service provider or an Acquirer based on predefined rules/criteria as well as making the new payment mechanisms of the payment associations work on the same POS terminals.
Such approach eliminates the need for having each service provider to connect directly to each Acquirer – which in itself is cumbersome and inefficient.
In line with existing technologies if there were 15 service providers and 10 Acquirers and assuming that all service providers needed to connect to all Acquirers, then there would be a need for 15 X 10 connections = 150 connections.
However, under a similar scenario, the present invention merely requires 15 + 10 connections = 25 connections.
Hence, the present invention provides the benefits of reducing and simplifying the number of connections, settlements validation, the inter-operability of services across Acquirer networks.
The reduction in the count of connections also results in lesser bandwidth consumption, reporting system integrations; reconciliation issues, data center space and network usage etc.
The POS application of present invention resides on the POS terminal and acts as a universal and thin client application that is consistent across all types of multi-vendor POS Terminals.
The POS terminal application of the present invention, further, has a unified and propriety Terminal Management System (TMS) that manages the distribution of updated and upgrades of on-demand POS applications or enhancements remotely – reducing the overall time and inefficiencies that come up in the traditional mode of terminal application enhancement management.
Such an update and management in the existing environment previous required physical visit(s) by a specialized personnel to a Merchant Establishment to update the POS Terminal.
The dynamic Terminal Management System of the present invention manages not only the terminals of the current vendor / manufacturers, but also any new vendors that the Acquirers may choose to procure POS Terminals from, in the future.
The Terminal Management System of the present invention is granular in nature, thereby ensuring that an subject to an Acquirers allowance, every Merchant Establishment would have a unique set of applications on his POS Terminal.
In the current scenario, POS Terminal manufacturers have, each, designed and developed their own proprietary system architecture for their POS Terminals.
7
Due to such approach, the plethora of technical details that encompasses such a monolithic application makes the application extremely proprietary by tightly coupling the application with the underlying Operating System.
Also, vendor specific authentication application is generic and the architecture of such application is unknown, making it technically challenging for providing a common thin-client application.
Further, presently there is no platform where-in digital currency products issued by all available service providers are accepted on all the POS Terminals of multiple Acquirers at the Merchant Establishments. In addition, the new mechanisms of payment proposed by the payment associations will also be able to be run on the POS terminals at the existing merchants – something that has not been perceived at the time of conception by the payment organisations.
The Merchant Establishment acceptance for all service provider products across all the Acquirers POS Terminals enables a universal and a unified approach for Digital authentication acceptance on a POS terminal and the same is proposed by the present invention.
The present invention synchronizes multiple POS manufacturer Terminal applications based on different underlying architecture to a common hardware agnostic thin client application that has the capability of providing financial and any other Value Added applications (allowing for the transaction of various service providers); and TMS in unified manner for various Multi-Vendor POS.
Such novel integration of various service provider transaction processing acceptances and switching allows the user authentication through any kind of digital instrument issued by any available service provider on the POS Terminal at the Merchant Establishment in a seamless manner.
Said novel arrangement is made possible by the present invention by having service providers are connected and integrated with the novel platform proposed by the present invention and having the platform integrated into multi Acquirer platforms.
FIGURE 1 illustrates a diagrammatic representation of an architectural environment in which the present invention operates, in accordance with one or more embodiments of the present disclosure.
In the exemplary architecture, Multi-vendor POS Terminals [102] for various merchants are connected using the Network layer [103].
The Credit and Debit cards transactions including authentication are passed to a Acquiring switch (105) at the Network access layer (103). The service provider (for example a Prepaid Instrument) transactions are routed by Network access Layer (103) to enterpriser server (105) of the present invention.
The TMS (Terminal Management System) related processing is also communicated to enterprise server (105) of the present invention.
The enterprise server (105) connects to the service provider or for further authorization and processing of transactions.
8
FIGURE 2 illustrates exemplary network environment wherein POS Terminal, Banking Acquirers and the service providers such as digital wallets operate.
Herein, details of enterprise server/HUB of the present invention as residing in data centers is kept in order to process transactions and for maintenance of the enterprise servers/HUB.
FIGURE 2 (a) illustrates an exemplary Point of Sale (PoS) terminal with proprietary GUI interface of HUB application of the present invention.
FIGURE 3 illustrates a flow diagram depicting an exemplary transaction done using any Prepaid Instrument or Prepaid Wallet issuer using Mobile Number and One Time Password (OTP).
In a typical embodiment, the transaction is initiated at a merchant store via a POS terminal. The Merchant selects the Prepaid Instrument or the Prepaid Wallet from an available list and inputs the amount in the POS Terminal.
Thereafter, the merchant inputs a mobile number for generation of an OTP (One Time password).
In response POS terminal sends the transaction to a host server for generation of OTP.
The host server validates the POS terminal and requests the Prepaid Wallet Issuer or any like service provider to generate the OTP for this transaction and send the OTP to user.
Once the user receives the OTP, the user is allowed to check if NFC is enabled for automated input of the OTP. Otherwise, the user manually inputs the OTP to POS Terminal.
In response to said input (manual or automated), the POS Terminal sends the original transaction along with OTP for authorization to host server.
The authorization is requested from Prepaid Wallet issuer host and the response is forwarded to the terminal for Printing of Charge Slip or Termination of transaction if the Transaction or OTP is not valid.
Figure 4 illustrates an exemplary flow diagram for depicting transactions via service provider / Prepaid Instrument or Prepaid Wallet issuer using Mobile Number and a pre-generated OTP.
Here, the transaction is initiated by a merchant store on the POS terminal.
The merchant at the store selects a prepaid wallet from the available list and inputs the amount in the POS Terminal.
Thereafter, the merchant inputs the mobile number and the user inputs the Pre-Generated OTP. Alternatively mobile may be tapped.
In response the terminal sends transaction amount, Mobile number along with OTP for Authorization to host server.
At the host server it is determined that merchant is valid. If merchant is not found to be valid an error code is sent back to Point of Sale (PoS) terminal merchant store.
9
Otherwise, authorization is in turn requested from Prepaid Wallet issuer by the Enterprise server host. The wallet issuer processes the authorization, stores and sends authorized transaction and the response is forwarded to the POS Terminal, via Host Enterprise server for Printing of Charge Slip or Termination of transaction if the Transaction or OTP is not valid.
This embodiment of the present invention provides comprising of a single step significantly improves the user Experience while simultaneously saving network bandwidth.
FIGURE 5 illustrates a flow diagram depicting an exemplary transaction via service provider/ Prepaid Instrument or Prepaid Wallet issuer using a Token number pre-generated by a mobile app of a user.
The transaction is initiated at a merchant store on the POS Terminal. The Merchant selects the Prepaid Wallet from the list indicating that user intends to process a wallet transaction and inputs the amount in the POS Terminal. The user is thereinafter requested to input the token number on the Terminal. A user may have a pre generated token or a token is generated thereon by TAP of a mobile.
The POS terminal then sends the transaction amount and token Number for authorization.
The authorization is requested from the Prepaid Wallet issuer host and the response is forwarded to the POS Terminal for Printing of Charge Slip or Termination of transaction if the Transaction is not valid.
This embodiment of the present invention is also a single step method and it enhances the user experience and security as the user is not required to reveal mobile Number during the Transaction.
It will be apparent to those having ordinary skill in this art that various modifications and variations may be made to the embodiments disclosed herein, consistent with the present disclosure, without departing from the spirit and scope of the present disclosure. Other embodiments consistent with the present disclosure will become apparent from consideration of the specification and the practice of the description disclosed herein.
FIGURE 6 illustrates a flow diagram of a Terminal Management System (TMS) of the present invention for Multi-Vendor Terminals.
Here, the merchant at a merchant store selects the option on the POS Terminal for Settlement of the batch.
In response, the POS terminal prints a Batch Report and Connects to host server for settlement.
For settlement, a connection to Host Enterprise Server (HES) is made, host validates the POS Terminal and processes the Settlement. If it is an invalid Merchant or terminal it terminates the Settlement and sends an error code to the terminal.
If merchant is found to be valid, the settlement is processed and a response is sent to the Point of Sale (PoS) terminal at merchant store.
10
Upon successful settlement the POS terminal prints the settlement charge Slip.
Thereafter, POS Terminal connects to the host again for checking if there is any update from TMS (Terminal Management System).
The host based on serial no. of POS Terminal verifies if there is a new application or parameter available for that Particular POS terminal. If there is an update available for POS Terminal, the POS Terminal sends the Request to host server for the update to be downloaded.
An update within the purview of the present invention may be a mere parameter change or an update of complete application.
The host server utilizes an independent series of steps without being dependent on Vendor TMS (Terminal Management System) to download the files to the terminal.
The host server pushes the complete binary application or parameter files to the POS terminal securely. Once the End of File is reached the host server sends a flag to POS terminal to disconnect.
The POS terminal disconnects from host server and restarts to ensure the update is applied on the application with latest changes.
FIGURE 7 illustrates a flow diagram for an exemplary transaction in line with the present invention using QR code for a Wallet issuer.
A person skilled in the art would know that mVisa is a card-to-merchant payment service provided by registering the Visa Debit Cards for mVisa payment. This enables Cardholders can make instant payment of bills or to merchants. Details of merchant are typically in QR code available at the stores and/or printed on bills.
Now, mVisa (or other providers such as MasterPass) currently operates where the Bank (Acquirer) places a QR code facility on such acquirer’s Website or at the Merchant location.
The user at merchant location captures the QR code and then approves the transaction on his mobile application.
In response, in case of a financial transaction, Money is debited from the user account and credited to the Merchant’s account.
Also a credit notification is sent via an SMS / Email etc. in order to update to the merchant bank account.
Via the present invention the QR code is allowed to be printed from the POS (Point of Sale) terminal at the merchant.
The QR code generated by the present invention is dynamic. For example the QR code proposed by the present invention also includes the value of the transaction under progress in it.
This technical approach eliminates the possibility of an error that may occur when a user is scanning the QR code and inputting a value.
11
In line with the present invention once the user scans QR code, he/she only needs to do is input the PIN to allow the transaction to proceed for completion.
Post this, a charge slip is printed on the POS (Point of Sale) terminal which gives both the Merchant and the user the ease of operability of using the QR Code while ensuring that the transaction is completed without any error as soon as the charge slip is printed.
This technological feature as implemented by the HUB server of the present invention is not provided by known service providers including mVISA / MasterPass.
Now referring to FIGURE 7 a transaction with a QR code is initiated by a merchant on a Point of Sale (POS) terminal.
The merchant selects a GUI Option of “Transaction with a QR code” and inputs the necessary credentials in the POS terminal.
The POS terminal in response is configured to print a QR code with the transaction details encoded in the QR code. The QR code is scanned by the user having the mobile application of Wallet Issuer or a proprietary Hub mobile application.
The mobile device sends the transaction request to HOST (server) for approval. The authorization is requested from a wallet issuer and the response is forwarded to the user’s mobile application.
Once the transaction is approved on mobile device the merchant validates it by requesting the charge slip of the transaction on POS. The POS terminal sends the transaction details to HOST (Server) which validates the request from Wallet Issuer. Once Wallet issuer provides the confirmation that the transaction is processed, BHES sends the charge slip details to be printed on the terminal to complete the transaction.
Particularly, a user/customer visits a merchant store and specifies whether an e-wallet transaction is intended. If an e-wallet transaction is indeed intended, then the user selects a GUI option “Transaction with QR code” generated via installed application “HUB” on the Point Of Sale (PoS) terminal of the user.
Particularly, referring to FIGURE 7, the user inputs an amount. In response the PoS terminal prints a QR code with transaction details.
Thereafter, the user scans a QR code and enters a PIN no. via the mobile application of his mobile device. In response the mobile application initiates a transaction with the HUB /HOST (server) proposed by the present invention.
The HOST in response determines whether details as received are of a valid merchant. If received details are not of a valid merchant, an error code is sent by the HOST to PoS terminal. In case a valid, merchant is tracked, the HOST server sends a request to a Wallet Issuer (WI) for approval of the transaction.
The Waller Issuer (WI) determines, whether received details are of a valid user/customer. If validity is confirmed an approval for transaction is sent by Wallet Issuer to mobile application (provided by Wallet Issuer). If validity is nor confirmed an error code is sent to Host server.
12
Also once transaction approved on mobile of a user, transaction may immediately be approved or a request for printing charge slip may be placed via HOST. The HOST requests Wallet Issuer for Transaction details. If the received request for PRINT is found to be a valid transaction by Wallet issuer, then charge slip details are sent to PoS terminal via HOST and the charge slip is printed at merchant store.
FIGURE 7 (a) An exemplary Point of Sale (PoS) terminal printing dynamic QR code of the via proprietary HUB application of the present invention.
FIGURE 8 illustrates a flow diagram of an exemplary transaction of the present invention wherein UPI Interface is implemented on ae POS terminal and on a mobile device as a Mobile application.
A person skilled in the art would know that a UPI – Unified Payment Interface is provided by NPCI – National Payments Corporation of India to simplify and provide a single interface for transaction processing and authentication across all systems.
The Unified Payment Interface intends to provide a transaction processing architecture that is to achieve the goals of universal electronic processing of transactions.
Some of the key aspects of the Unified Payment Interface include easy instant transaction processing via mobile, web, and other applications.
The transactions can be both sender (payer) and receiver (payee) initiated and are carried out in a secure, convenient, and integrated fashion.
However, the underlying architecture provided by UPI – Unified Payment Interface is bent towards providing a set of APIs (Application Program Interfaces) that is configured towards taking advantage of mobile devices i.e. smartphone.
And as of now UPI – Unified Payment Interface is not implemented for POS (Point of Sale) terminals.
The present invention advantageously maps UPI – Unified Payment Interface to terminals.
The UPI as of today allows every Bank Account holder to create a username for himself (individual / corporate) and set up a password / PIN. Thereafter an individual can send / receive payments from another simply by using the username and inputting the PIN. This is particularly being implemented currently for Mobile to Mobile transaction only.
As indicated above the present invention maps UPI – Unified Payment Interface to PoS terminals which incorporates solving complex challenges.
For Example, as a Username comprises of alpha-numeric characters, it is not possible to enter the alpha numeric name of a user via POS terminal at the merchant location.
To overcome at least this challenge, the present invention extends the mVISA / Masterpass QR technology to UPI.
13
In line with the present invention a user at a merchant location chooses to transact via UPI. It is to be noted that details of Merchant UPI are already known merchant is already coupled with the acquirer bank.
Such a merchant, when visited by a user opting to transact via UPI, allows the user to selects UPI on the GUI menu of proprietary application provided by the present invention.
In response a QR code slip is generated from PoS terminal along with UPI details of the Merchant.
Thereafter, the user executes the transaction application on his mobile, scans the QR code (generated by PoS terminal) and enters his/her PIN (Personal Identification Number).
Thereafter, bank account of transacting user is debited.
This in contrast with currently operating MVISA / MASTERPASS service providers where it is the users debit / credit card which is debited.
Now, once the user’s bank account is debited a confirmation is then given to Hub Server of the present invention via the Acquiring Bank, The Hub server in turn gets this confirmation from NPCI.
In response the Hub server confirms the transaction by printing out the slip and the transaction is completed.
The processing of transactions using a UPI virtual address of a user is done on a proprietary Hub application of the present invention. Particularly, a transaction with UPI is initiated by a merchant on the POS terminal.
Again the merchant is allowed to select a GUI (Graphical User Interface) Option of “Transaction with UPI” and inputs the credentials in the POS terminal.
The POS terminal in response is configured to print a QR code with the transaction details and with Merchant Virtual Address encoded in the QR code.
The QR code is scanned by the user having the mobile application of UPI of Bank or a proprietary Hub mobile application. The user then inputs the mobile PIN on the POS terminal and the transaction sale request is sent to a Host Enterprise server.
The mobile device sends the transaction request to HOST (server) for approval. The Virtual address translation and authorization is requested from a NPCI and the response is forwarded to the user’s mobile application and Hub server by NPCI.
The virtual address of the merchant and the user is sent to NPCI using UPI interface for address translation and approval. Once the transaction is approved by NPCI the response is sent to the merchant’s terminal for printing of the Charge slip of the transaction on POS. The charge slip details contains the virtual address of user and merchant address

We Claim:
1. A method for performing secure authentication in a network environment, comprising
- Initiating a transaction via a POS (Point Of Sale) TERMINAL by a USER;
- Selecting at least one wallet and inputting a predetermined amount and a mobile number;
- Sending the transaction to a HOST SERVER by said POS (Point Of Sale) TERMINAL;
- validating the POS (Point Of Sale) TERMINAL by the HOST SERVER by generating a ONE TIME PASSWORD (OTP);
- Receiving the ONE TIME PASSWORD (OTP) by the USER and forwarding the transaction to a WALLET ISSUER HOST
Wherein WALLET ISSUER HOST processes the authorization, and a response is forwarded to the POS TERMINAL via the HOST ENTERPRISE SERVER indicating authentication of transaction.
2. A method for performing secure authentication as claimed in claim 1 wherein when the POS (Point Of Sale) terminal is not found to be valid an error code is sent back to Point of Sale (POS) terminal.
3. A method for performing secure authentication comprising
- Initiating a transaction via a POS (Point Of Sale) TERMINAL by a USER;
- selecting at least one Wallet , entering a predetermined amount and a dynamically generated TOKEN NUMBER in the POS Terminal;
- sending the transaction amount and token Number for authorization to Wallet issuer host ;
- forwarding the response to POS (Point Of Sale) terminal.
4. A method for performing secure authentication as claimed in claim 1 or claim 3 wherein for Multi-Vendor Terminals, the method comprising
- selecting predefined option on the POS Terminal for Settlement of the batch transactions
- connecting POS Terminal to a HOST SERVER
- validating POS TERMINAL and processing said batch transactions
- reconnecting POS Terminal with HOST SERVER for verifying if a new application is available for the POS Terminal.
5. A method for performing secure authentication as claimed in claim 4, wherein for an invalid POS Terminal the batch processing is terminated and an error code is sent to the terminal.
6. A method for performing secure authentication as claimed in claim 4 wherein when an update available for POS Terminal, the POS Terminal sends the Request to host server for the update to be downloaded.
16
7. A method for performing secure authentication as claimed in claim 1 wherein a QR code is allowed to be printed from a Point Of Sale (PoS) terminal and wherein the QR code comprises of value of the transaction allowing the user input a PIN for transaction completion.
8. A method for performing secure authentication as claimed in claim 1 wherein a UPI - Unified Payment Interface to PoS terminals, said mapping comprising
- Selecting to transact using Unified Payment Interface by a user;
- Generating a QR code slip from PoS terminal along with UPI details of the terminals;
- Executing a transaction application on a mobile
- scanning the QR code generated by PoS terminal and entering PIN (Personal Identification Number)
- Receiving confirmation from a Hub server via NPCI.