WO2020174296A1 - Système de paiement électronique et procédé associé - Google Patents

Système de paiement électronique et procédé associé Download PDF

Info

Publication number
WO2020174296A1
WO2020174296A1 PCT/IB2020/050667 IB2020050667W WO2020174296A1 WO 2020174296 A1 WO2020174296 A1 WO 2020174296A1 IB 2020050667 W IB2020050667 W IB 2020050667W WO 2020174296 A1 WO2020174296 A1 WO 2020174296A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
initiatee
psp
upi
initiator
Prior art date
Application number
PCT/IB2020/050667
Other languages
English (en)
Inventor
Dilip ASBE
Narayanan Rajendran
Sateesh PALAGIRI
Anubhav SHARMA
Original Assignee
National Payments Corporation Of India
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by National Payments Corporation Of India filed Critical National Payments Corporation Of India
Priority to SG11202109040UA priority Critical patent/SG11202109040UA/en
Priority to CA3131260A priority patent/CA3131260A1/fr
Publication of WO2020174296A1 publication Critical patent/WO2020174296A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3821—Electronic credentials
    • G06Q20/38215—Use of certificates or encrypted proofs of transaction rights
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/388—Payment protocols; Details thereof using mutual authentication without cards, e.g. challenge-response
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance

Definitions

  • THIS APPLICATION IS A PATENT OF ADDITION TO INDIAN PATENT APPLICATION NO. 201621021488 FILED ON JUNE 22 nd , 2016.
  • the present disclosure relates to electronic payment systems.
  • Registered user refers to a person having a hank account and using the electronic payment system (EPS) of the present disclosure for carrying out electronic payment transactions.
  • the registered user can be a payer i.e. a person who wants to send/pay money using the EPS, or can be a payee i.e. a person who receives/collects money using the EPS.
  • User device refers to a device, used by a registered user, wherein the user device includes but is not limited to a mobile phone, a laptop, a tablet, an iPad, a PDA, a notebook, a net book, a smart device, a smart phone, a personal computer, a handheld device and the like.
  • Payment transactions - The term‘payment transactions’ hereinafter refers to financial as well as non-financial transactions.
  • the financial transactions comprise collect/pull request and pay/push request based, person-to-person (P2P), person-to-account (P2A), and person-to- merchant (P2M) payment transactions.
  • the non-financial transactions include but are not limited to mobile banking registration, generation of one-time password (OTP), checking balance, setting or changing PIN, logging a complaint, and checking transaction status.
  • OTP one-time password
  • Banks refers to credit societies, schedule banks, cooperative banks, microfinance institutions, retail and commercial banks, savings and loan associations, insurance companies, and the like.
  • Payment Service Provider - The term‘Payment Service Provider (PSP)’ hereinafter refers to an internet bank, a payments bank, a Prepaid Payment Instrument (PPI), or any other centrally and/or government regulated entity that is allowed to acquire customers and provide payment (credit/debit) services to the customers (individuals or entities).
  • PSP provides respective application tools that can be accessed by registered users on their user devices to push or pull payments.
  • the PSP provides a tool for electronic processing of financial and non-financial transactions.
  • Payment session refers to a limited time of communication between systems or servers associated with the registered users of the present disclosure to effect payment from one registered user to another.
  • Initiator - refers to a registered user who initiates a payment session by sending a request to pay/push or collect/pull money using the user device of the present disclosure.
  • An initiator can be (i) a person acting as a payer or a payee or (ii) a merchant acting as a payee.
  • Initiatee refers to a registered user for whom the payment session is initiated by the initiator of the present disclosure.
  • An initiatee can be (i) a person acting as a payee or a payer or (ii) a merchant acting as a payee.
  • Global Identifier or Virtual Payment Address -
  • the unique Global identifier (GI) or virtual Payment address (VPA/UPI ID) is used to carry out payment transactions.
  • GI can include a mobile number, an Aadhaar number, a hank account number, or any other identifier that can uniquely and securely identify the registered user of the present disclosure.
  • VPA/UPI ID can be created by a registered user for a payment transaction(s).
  • Unified Payment Interface server refers to a central server that provides interface between a plurality of PSPs and banks for carrying out financial and non-financial transactions.
  • Payment Service Provider tool -
  • the term‘Payment Service Provider tool (PSP tool)’ hereinafter refers to an application or a tool provided by each PSP.
  • the PSP tool may be provided on a web portal or play store and/or mobile web or through other means to provide registered users an interface with the UPI through the PSP.
  • Communication means refers to a means for transmitting and receiving electronic data.
  • the communication means may include, for example, the Internet, the World Wide Web, an intranet, cable (including fiber optic cable), magnetic communications, electromagnetic communications (including RF, microwave, and infrared communications), and electronic communications.
  • Wireless communication means can support various wireless communication network protocols and technologies such as Near Field Communication (NFC), Wi-Fi, Bluetooth, 4G Long Term Evolution (LTE), Code Division Multiplexing Access (CDMA), Universal Mobile Telecommunication System (UMTS) and Global System for Mobile Telecommunication (GSM).
  • NFC Near Field Communication
  • Wi-Fi Wi-Fi
  • Bluetooth 4G Long Term Evolution
  • CDMA Code Division Multiplexing Access
  • UMTS Universal Mobile Telecommunication System
  • GSM Global System for Mobile Telecommunication
  • a payee’s mobile phone number is used to make a payment.
  • a payer it is imperative for a payer to know the payee’s bank details and/or mobile phone number as the mobile banking is based on a SIM number.
  • payment is pushed by the payer to the payee.
  • the payee is solely dependent on the payer for transactions and the payer is dependent on his/her hank web portal for the payment services.
  • Some users tend to change their mobile/ phone numbers frequently and in such cases, it is difficult for a payer to keep track of these changes. Additionally, in some cases, the payer and the payee may not want to reveal their hank details and personal details to each other. Accordingly, there is a need to limit the aforementioned drawbacks and provide an efficient, simplified and user friendly system and method for carrying out electronic payment transactions.
  • An object of the present disclosure is to provide an electronic payment system that is easy to use.
  • Another object of the present disclosure is to provide an electronic payment system that provides a central server for facilitating quick exchange of data between various entities involved in payment processing.
  • Yet another object of the present disclosure to provide an electronic payment system that enables users to pull/ collect payments from accounts of concerned persons/ entities, subsequent to the requested entity authorizing such payments.
  • Still another object of the present disclosure is to provide an electronic payment system that simplifies payment for both, the payers and the payees by reducing authorization steps and increasing security features.
  • a further object of the present disclosure is to provide an electronic payment system that enables payment transactions between a payer and a payee without mandatorily needing the hank information and hank account details of each other.
  • an object of the present disclosure is to provide an electronic payment system that enables a user to send and receive money with the help of a virtual payment address or a Global Identifier.
  • Yet another object of the present disclosure is to provide an electronic payment system that eliminates dependency of a user on his/her hank web portal or mobile application for internet or mobile banking, and allows the user to use a different hank web portal and/or mobile applications for payment transactions.
  • An electronic payment method for facilitating payment transactions between a plurality of users.
  • Each user is defined by a name, a bank account, a user device, a unique multi-character PIN, and a unique Global Identifier.
  • the method comprises the following steps:
  • UPI server Unified Payment Interface server
  • PSPs Payment Service Providers
  • PSP tool Payment Service Provider tool linked to each PSP, enabling a user from the plurality of users to select at least one PSP from the plurality of PSPs, installing, the PSP tool of the selected PSP and enabling the device of the user to communicate with the selected PSP server in a two-way communication using the PSP tool;
  • PSP tool Payment Service Provider tool
  • the registering step includes the following sub-steps:
  • VPA/UPI ID Virtual Payment Address
  • a registered user to initiate a payment session, referred to as a session request, as an initiator, to make payment to or receive payment from another registered user designated as an initiatee, by inputting either a VPA/UPI ID or a GI of the initiatee, the amount to be transacted, and the multi-character PIN of the initiator when the initiator is a payer;
  • the initiator to communicate the session request via the initiator’s PSP tool with the selected PSP server with which the initiator is registered;
  • the selected PSP server to authenticate the initiator using user device information stored in the first lookup table of the data repository of the PSP server; in the event of successful authentication of the initiator, by the initiator’s PSP server, enabling the selected initiator PSP server, to transmit the initiator’s session request to the UPI server;
  • the UPI server to extract from the initiator’s session request, the VPA/UPI ID or the global identifier of the initiatee, depending upon the initiatee information inputted in the session request;
  • initiatee is the payee - a. in the event the session request includes the VPA/UPI ID of the initiatee: i. enabling, the UPI server, to identify the PSP server of the initiatee from the VPA/UPI ID of the initiatee using the third lookup table; ii. enabling, the UPI server, to send the VPA/UPI ID along with a VPA/UPI ID translation request to the PSP server identified as the initiatee’s PSP server; and
  • the initiatee enabling, the initiatee’s PSP server, to translate the VPA/UPI ID received from the UPI server, extract the bank account information from the VPA/UPI ID, and transmit the hank account information of the initiatee to the UPI server, b. in the event the session request includes GI of the initiatee, enabling, the UPI server, to extract from the second lookup table, the bank account information of the initiatee;
  • the UPI server enabling, the UPI server, to generate a debit transaction request and a request for authenticating the initiator, with the bank of the initiator, enabling, the bank of the initiator, to authenticate the initiator using the PIN inputted by the initiator at the time of initiating the payment session, upon successful authentication, debiting the bank account of the initiator with the amount to be transacted and upon completion of the debit transaction with the initiator’s bank, transmitting a credit request to the UPI server for crediting the hank account of the initiatee with the amount to be transacted, and further enabling the UPI server to communicate with the bank of the initiatee to credit the hank account of the initiatee with the amount to be transacted by the initiator to the initiatee, and
  • the itiator is the payee - a. in the event the session request includes the VPA/UPI ID of the initiatee: i. enabling, the UPI server, to identify the PSP server of the initiatee from the VPA/UPI ID of the initiatee using the third lookup table; ii. enabling, the UPI server, to send a transaction request to the PSP server identified as the initiatee’ s PSP server;
  • the initiatee iv. on the acceptance of the transaction request by the initiatee, enabling, the initiatee’s PSP server, to send a request to the initiatee, to input his/her multi-character PIN;
  • the PSP server to receive the PIN inputted by the initatee and send an accepted transaction signal along with the PIN to the UPI server;
  • enabling, the UPI server to send the VPA/UPI ID along with a VPA/UPI ID translation request to the PSP server of the initiatee; and viii. enabling, the initiatee’s PSP server, to translate the VPA/UPI ID received from the UPI server, extract the bank account information from the VPA/UPI ID, and transmit the hank account information of the initiatee to the UPI server,
  • the UPI server i. enabling, the UPI server, to identify PSP server of the initiatee from the GI of the initiatee using the fourth lookup table;
  • the initiatee iv. on the acceptance of the transaction request by the initiatee, enabling, the initiatee’s PSP server, to send a request to the initiatee, to input his/her multi-character PIN;
  • the PSP server to receive the PIN inputted by the initatee and send an accepted transaction signal along with the PIN to the UPI server;
  • the UPI server on receiving the PIN and the accepted transaction signal from the initiatee’s PSP server, enabling, the UPI server, to generate a debit transaction request and a request for authenticating the initiatee, with the bank of the initiatee, enabling, the bank of the initiatee, to authenticate the initiatee using the PIN inputted by the initiatee, upon successful authentication, debiting the hank account of the initiatee with the amount to be transacted, and upon completion of the debit transaction with the initiatee’s bank, transmitting a credit request to the UPI server for crediting the bank account of the initiator with the amount to be transacted, and further enabling, the UPI server to communicate with the hank of the initiator to credit the bank account of the initiator with the amount to be transacted.
  • the present disclosure also envisages an Electronic Payment System (EPS) for facilitating payment transactions between a plurality of users.
  • EPS Electronic Payment System
  • Each user is defined by a name, a hank account, a user device, a unique multi-character PIN, and a unique Global Identifier.
  • the system comprises a central server, a plurality of PSP servers, a plurality of PSP tools, a user device, and a first, second, and third registering module.
  • the central server is designated as a UPI server.
  • the UPI server comprises a data repository and at least one processor.
  • the plurality of PSP servers is clustered around the UPI server.
  • the PSP servers comprise data storage and one or more processing modules.
  • Each of the PSP servers is configured to communicate with the UPI server.
  • the PSP tools are installable in user devices clustered around each of the PSP servers, wherein each user device is configured to have one or more of the PSP tools.
  • the first registering module is configured to enable a PSP server to register with the UPI server.
  • the second registering module is configured to enable a user device to be registered with a PSP server, and the third registering module is configured to enable a user to register on the PSP tool installed in its user device.
  • FIG. 1 illustrates a schematic architecture diagram of an electronic payment system (EPS);
  • EPS electronic payment system
  • Figures 2A, 2B, and 2C illustrate a flow diagram showing steps performed by the EPS of Figure 1 for effecting payer initiated transactions
  • Figures 3A, 3B, 3C, and 3D illustrate a flow diagram showing steps performed by the EPS of Figure 1 for effecting payee initiated transactions;
  • FIG 4 illustrates a block diagram of Payment Service Provider tool (PSP tool) of the EPS of Figure 1;
  • PSP tool Payment Service Provider tool
  • FIG. 5 illustrates a block diagram of Payment Service Provider server (PSP server) of the EPS of Figure 1;
  • PSP server Payment Service Provider server
  • FIG. 6 illustrates a block diagram of Unified Payment Interface server (UPI server) of the EPS of Figure 1; and Figures 7 illustrates a block diagram showing person to person transaction flow using the
  • UPI server Unified Payment Interface server
  • PGP server Payment Service Provider Server
  • Embodiments are provided so as to thoroughly and fully convey the scope of the present disclosure to the person skilled in the art. Numerous details, are set forth, relating to specific components, and methods, to provide a complete understanding of embodiments of the present disclosure. It will be apparent to the person skilled in the art that the details provided in the embodiments should not be construed to limit the scope of the present disclosure. In some embodiments, well-known processes, well-known apparatus structures, and well-known techniques are not described in detail. The terminology used, in the present disclosure, is only for the purpose of explaining a particular embodiment and such terminology shall not be considered to limit the scope of the present disclosure.
  • first, second, third, etc. should not be construed to limit the scope of the present disclosure as the aforementioned terms may be only used to distinguish one element or component from another element or component. Terms such as first, second, third etc., when used herein do not imply a specific sequence or order unless clearly suggested by the present disclosure.
  • the present disclosure addresses interoperability of banking mobile applications and/or hank web-portals for payment transactions.
  • users and/or hank customers are not restricted to use the web-portals and/or mobile-webs of the hanks in which they have their account(s). Instead, the users (both payer and payee) and/or customers can choose any bank’s web-portal or mobile-web for their payment transactions without knowing hank account details of other user/person.
  • the users (payer or payee) are required to know only a unique Global ID or virtual payment address (VPA/UPI ID) to make financial/electronic payment transactions.
  • VPN/UPI ID virtual payment address
  • Figure 1 illustrates a schematic architecture diagram of an electronic payment system (hereinafter referred to as EPS 100 or system 100) for facilitating payment transactions between a plurality of users.
  • EPS 100 electronic payment system
  • Each user is defined by a name, a bank account, a user device 106, a unique multi-character PIN, and a unique Global Identifier (GI).
  • the GI is selected from the group consisting of a mobile number, an Aadhaar number, and a hank account number of a user.
  • the payment transactions include financial as well as non-financial transactions, wherein the financial transactions comprise collect/pull requests, pay/push requests, and merchant payments, and the non- financial transactions comprise mobile banking registration, generation of one-time password (OTP), setting or changing PIN, checking transaction status, logging a complaint and the like.
  • financial transactions comprise collect/pull requests, pay/push requests, and merchant payments
  • non- financial transactions comprise mobile banking registration, generation of one-time password (OTP), setting or changing PIN, checking transaction status, logging a complaint and the like.
  • OTP one-time password
  • the EPS 100 comprises a UPI server 102, a plurality of PSP servers 104, a plurality of PSP tools, and user devices 106 associated with the plurality of users.
  • the UPI server 102 is a central server and comprises a data repository 604 and at least one processor.
  • the plurality of PSP servers 104 are clustered around the UPI server 102.
  • Each of the PSP servers 104 comprises data storage 506 and one or more processing modules.
  • the PSP server 104 is configured to communicate with the UPI server 102.
  • the PSP tools are installable in user devices 106 clustered around each of the PSP servers 104.
  • Each user device 106 is configured to have one or more of the PSP tools.
  • the system 100 includes a first registering module configured to enable a PSP server 104 to register with the UPI server 102.
  • the system 100 also includes a second registering module configured to enable a user device 106 to be registered with a PSP server 104.
  • the system 100 further includes a third registering module configured to enable a user to register on the PSP tool installed in its user device 106.
  • FIGS 2A, 2B, and 2C illustrate a flow chart depicting the steps involved in an electronic payment transaction initiated by a payer
  • Figures 3A, 3B, 3C, and 3D illustrate a flow chart depicting the steps involved in an electronic payment transaction initiated by a payee.
  • the methods of executing both payer and payee initiated transactions are implemented using the EPS 100 described above and comprises the following steps: a. providing a Unified Payment Interface server (UPI server) 102 having a data repository 604 and processing capability;
  • UPI server Unified Payment Interface server
  • PSPs Payment Service Providers
  • PSP tool Payment Service Provider tool linked to each PSP, enabling a user from said plurality of users to select at least one PSP from the plurality of PSPs, installing, the PSP tool of the selected PSP 104 and enabling the device 106 of the user to communicate with the selected PSP server 104 in a two-way communication using the PSP tool;
  • PSP tool Payment Service Provider tool
  • the UPI server 102 e. enabling, the UPI server 102 to communicate with each of the hanks of users; f. carrying out, a first authentication of a user, by verifying user information and user device information;
  • the registering step includes the sub-steps of:
  • VPA/UPI ID Virtual Payment Address
  • a registered user to initiate a payment session, referred to as a session request, as an initiator, to make payment to or receive payment from another registered user designated as an initiatee, by inputting either a VPA/UPI ID or a GI of the initiatee, the amount to be transacted, and the multi-character PIN of the initiator when the initiator is a payer;
  • the initiator j. enabling, the initiator to communicate the session request via the initiator’s PSP tool with the selected PSP server 104 with which the initiator is registered;
  • the selected PSP server 104 to authenticate the initiator using user device information stored in the first lookup table of the data repository 604 of the PSP server 104;
  • the UPI server 102 enabling, the UPI server 102, to extract from the initiator’s session request, the VPA/UPI ID or the global identifier of the initiatee, depending upon the initiatee information inputted in the session request;
  • initiatee is the payee - i. in the event the session request includes the VPA/UPI ID of the initiatee:
  • the UPI server 102 to send the VPA/UPI ID along with a VPA/UPI ID translation request to the PSP server 104 identified as the initiatee’s PSP server 104;
  • the session request includes GI of the initiatee, enabling, the UPI server 102, to extract from the second lookup table, the hank account information of the initiatee;
  • the UPI server 102 to generate a debit transaction request and a request for authenticating the initiator, with the bank of the initiator, enabling, the bank of the initiator, to authenticate the initiator using the PIN inputted by the initiator at the time of initiating the payment session, upon successful authentication, debiting the hank account of the initiator with the amount to be transacted and upon completion of the debit transaction with the initiator’s bank, transmitting a credit request to the UPI server 102 for crediting the bank account of the initiatee with the amount to be transacted, and further enabling the UPI server 102 to communicate with the hank of the initiatee to credit the hank account of the initiatee with the amount to be transacted by the initiator to the initiatee, and
  • initiator is the payee - i. in the event the session request includes the VPA/UPI ID of the initiatee:
  • the session request includes the GI of the initiatee:
  • the UPI server 102 to extract from the second lookup table, the hank account information of the initiatee, and iii. on receiving the PIN and the accepted transaction signal from the initiatee’s PSP server 104, enabling, the UPI server 102, to generate a debit transaction request and a request for authenticating the initiatee, with the bank of the initiatee, enabling, the bank of the initiatee, to authenticate the initiatee using the PIN inputted by the initiatee, upon successful authentication, debiting the bank account of the initiatee with the amount to be transacted, and upon completion of the debit transaction with the initiatee’s bank, transmitting a credit request to the UPI server 102 for crediting the hank account of the initiator with the amount to be transacted, and further enabling, the UPI server 102 to communicate with the bank of the initiator to credit the hank account of the initiator with the amount to be transacted.
  • a trusted common library is integrated with the PSP tool of the user.
  • the multi-character PIN of the user is encrypted at step (2) within the trusted common library.
  • the step (5) of creating the encrypted message includes encrypting the PIN and the hank account information using the public key of the user’s hank.
  • the sub-step (h(i)) of registering the user includes encrypting the hank account information of the user by the PSP tool, before converting the information into the VPA/UPI ID.
  • the sub-step (h(ii)) of registering the user includes encrypting the hank account information and the GI of the user, before storing it in the second lookup table.
  • the method further includes the steps of communicating with the initiator, about the failure of a payment session in the occurrence of any of the following events:
  • the method includes the step of notifying the initiator and the initiatee, upon successful completion of a payment session.
  • the method includes the step of enabling a registered user, to edit his/her hank account information, PIN, and Global Identifier (GI) and further in the event a registered user edits his/her the bank account information, PIN, and Global Identifier (GI), changes will be effected automatically in the VPA/UPI ID and the lookup tables at the PSP and UPI servers 104 and 102.
  • a registered user edits his/her hank account information, PIN, and Global Identifier (GI)
  • GI Global Identifier
  • the method includes the step of enabling a registered user, to de -register from a PSP server 104. In another embodiment, the method includes a step of enabling, the initiator, to prematurely terminate a payment session, at any time before n(iii) or at any time before o(iii) when the initiatee is the payer.
  • thee step of authenticating the initiator or the initiatee in the process when a payment session has been initiated in the steps (n(iii)) and (o(iii)) includes the following sub-steps:
  • step (i) of initiating the payment session may include the following sub-steps:
  • the data repository 604 is configured to store a set of decoding rules.
  • the step (1) of embedding the VPA/UPI ID of the initiatee may include:
  • the step of initiating a payment session may include embedding the amount to be transacted in the QR code.
  • the method further enables, an initiator or an initiatee, to create a one-time mandate, with the help of the PSP tool.
  • the mandate creation method comprises the following steps:
  • an initiator to initiate a mandate session, by inputting on his/her user device 106, either a VPA/UPI ID or a GI of the initiatee, the amount to be transacted, the start date and the end date, and the multi-character PIN of the initiator when the initiator is a payer;
  • the initiator a. enabling, the initiator, to communicate the mandate request and the PIN via the initiator’s PSP tool with a selected PSP server 104 with which the initiator is registered;
  • the UPI server 102 i. enabling, the UPI server 102, to send a mandate creation confirmation message, to the initiatee’s PSP server 104, and
  • e initiator is a payee:
  • the initiator a. enabling, the initiator, to communicate the mandate request via the initiator’s PSP tool with a selected PSP server 104 with which the initiator is registered; b. enabling, the initiator’s PSP, to send the mandate request, to the UPI server
  • the UPI server 102 to send a mandate creation confirmation message, to the initiator’s PSP server 104.
  • the method further enables, the payer, to view, modify, and revoke, the created mandate, in the PSP tool of the payer.
  • the method further enables, the initiator, to create a recurring mandate, when the initiator is the payer.
  • the method includes the step of enabling, a registered user to select his hank account, from the group consisting of a savings bank account, a current bank account, and an overdraft account.
  • the method includes, enabling, the initiator, to attach an invoice during initiation of the payment session, when the initiator is a payee.
  • the method further includes the step of establishing the credentials such as the public key of the initiator, when the initiator is a payee, before sending the transaction request to the initiatee’s PSP server 104.
  • the method includes the step of sending a warning to the initiatee on his/her user device 106 if the credential verification of the initiator has failed.
  • a signed public key/token i.e. verified public key of the payee (merchant) is stored at the payee’s PSP server 104.
  • the PSP tool may be configured to facilitate initiation of signed transaction request to the verified merchants only. This helps in reducing transaction requests from illicit sources imitating as merchant.
  • the method facilitates simultaneous initiation of multiple registrations of the users and multiple initiations of payment sessions.
  • each PSP tool of the EPS 100 comprises a first communication means 402, a session generating module 404, and a first encrypter 406.
  • the first encrypter 406 is a part of the trusted common library of the PSP tool.
  • the first communication means 402 enables communication of the PSP tool with a PSP server 104 and the UPI server 102.
  • the session generating module 404 is configured to receive either a VPA/UPI ID or a GI of the initiatee, the amount to be transacted, and the multi-character PIN of the initiator when the initiator is a payer, to generate a payment session.
  • the PSP tool includes an encoder 410 configured to receive a QR code generation request from an initiatee of a payment session, and further configured embed the VPA/UPI ID of the initiatee in a QR code.
  • the payment session is initiated when an initiator scans the generated QR code of the initiatee.
  • the QR code is a static QR code.
  • the QR code is a dynamic QR code.
  • the first encrypter 406 is configured to encrypt the PIN of the initiator or the initiatee, using the public key of the UPI, and is further configured to transmit the encrypted PIN to the UPI server 102 via the first communication means 402.
  • the PSP tool is configured to store the details of transactions carried out by it, in the user device 106 of a user, thereby enabling the user to view transaction history.
  • the transaction history comprises a chronologically time stamped list of transactions, their type, the amount transacted, and the name of the user with whom transaction was performed.
  • the PSP tool includes a mandate creating module 408 configured to receive either a VPA/UPI ID or a GI of the initiatee, the amount to be transacted, the multi character PIN of the initiator when the initiator is a payer, and a start date and an end date, to create a mandate request.
  • the mandate creating module 408 facilitates the user to authorize a future debit of his/her account by creating a mandate.
  • the mandate can be created for one time execution only and the user account is blocked for the equivalent amount immediately with the mandate creation.
  • the mandate creation facility allows the user’s account to be debited as per the agreed terms and conditions when a payee initiates request for funds. When payee initiates request for funds, the payer does not need to authenticate the transaction, since a mandate for that debit is already been given by him by authenticating while creating the mandate.
  • the PSP tool allows both payer and payee to create mandates in the form of push (Payer initiated) or pull (Payee initiated) requests. However, execution of mandate can only be initiated by the payee in a way similar to the payee initiated transaction or collect transaction.
  • the PSP tool can clearly distinguish mandates from regular transactions and keep record of mandates created & executed.
  • Mandate creation may be useful in scenarios where funds are to be blocked towards one-time future payments, such as:
  • the PSP server 104 comprises a second communication means 502, a VPA/UPI ID configurer 504, the data storage 506, a first queuing module 508, a first authenticator 510, and a translator 512.
  • the second communication means 502 is configured to enable communication with PSP tools and the UPI server 102.
  • the VPA/UPI ID configurer 504 is processable to receive user hank account information and user device information, and is further processable to merge this information to form a unique VPA/UPI ID for each user.
  • the data storage 506 comprises a first data stack, in the form of a first lookup table.
  • the first lookup table comprises the VPA/UPI ID corresponding to users whose devices are registered in the PSP server 104, wherein the VPA/UPI ID includes the user’s corresponding hank account information and user device information.
  • the data storage 506 further comprises a second data stack having processing rules and commands for controlling the storage of data into the data stacks and for controlling the operation of PSP server 104.
  • the first queuing module 508 is configured to receive and process the payment sessions in a First In First Out (FIFO) order, and is further configured to handle signals received from PSP tools and the UPI server 102 based on processing rules and commands stored in the data storage 506.
  • the first authenticator 510 is configured to provide a first level authentication of the initiator using the initiator’s user device information.
  • the translator 512 is configured to translate a VPA/UPI ID into bank account information, and is further configured to transmit the bank account information to the UPI server 102 using the second communication means 502.
  • the translator 512 comprises:
  • a data splitter configured to split the VPA/UPI ID into its elements
  • an extractor configured to extract hank account information from the elements of the VPA/UPI ID, and further configured to transmit the extracted bank account information to the UPI server 102 using the second communication means 502.
  • the PSP server 104 is further configured to store in a chronological order, a list of transactions performed by the users registered with PSP server 104 and the date on which the transaction was performed.
  • the UPI server 102 comprises a third communication means 602, a data repository 604, a second queuing module 606, an analyzer 608, a first crawler and extractor unit 610, and a second crawler and extractor unit 612.
  • the third communication means 602 is configured to enable communication with PSP servers 104 and banks.
  • the data repository 604 comprises a third, a fourth, a fifth, a sixth, a seventh, and an eighth data stack.
  • the third data stack receives and stores links to the PSP servers 104 registered with the UPI server 102.
  • the fourth data stack comprises links to a plurality of hanks associated with users registered with the PSP servers 104 which are in turn registered with the UPI server 102. Each user associated is with one or more banks.
  • the fifth data stack is in the form of a second lookup table, and comprises a plurality of items. Each item corresponds to a user whose device is registered in the PSP server 104, the user’s corresponding GI, and the user’s designated hank stored in an encrypted form.
  • the sixth data stack is in the form of a third lookup table comprising a plurality of items. Each item corresponds to a user whose device is registered in the PSP server 104, the user’s corresponding VPA/UPI ID, and the user’s corresponding PSP.
  • the seventh data stack is in the form of a fourth lookup table comprising a plurality of items.
  • the eighth data stack includes processing rules and commands for controlling the storage of data into the data stacks and for controlling the operation of UPI server 102.
  • the data repository 604 is a data mapper serving as a middle layer between in-memory objects and a database having the second, third, and fourth lookup tables.
  • the second queuing module 606 is configured to receive and process multiple payment sessions in a First In First Out (FIFO) order, and is further configured to handle signals received from PSP servers 104 and banks based on processing rules and commands stored in the seventh data stack of the data repository 604.
  • FIFO First In First Out
  • the analyzer 608 is configured to analyze the initiator session request and extract the VPA/UPI ID or GI of the initiatee from the initiator session request.
  • the analyzer 608 includes a selector switch configured to route the session request to the fifth, sixth, or seventh data stack based on the identified VPA/UPI ID or GI of the initiatee and the processing rules and commands.
  • the selector switch is an Electronic Funds Transaction (EFT) switch.
  • the first crawler and extractor unit 610 is configured to crawl through the third lookup table stored in the sixth data stack of the data repository 604, and is further configured to extract PSP of the initiatee using the VPA/UPI ID of the initiate.
  • the second crawler and extractor unit 612 is configured to crawl through the second lookup table stored in the fifth data stack of the data repository 604, and is further configured to extract bank account information of the initiatee using the GI of the initiatee.
  • the third crawler and extractor unit 614 is configured to crawl through the fourth lookup table stored in the seventh data stack of the data repository 604, and is further configured to extract PSP of the initiatee using the GI of the initiatee.
  • the UPI server 102 further includes a first decrypter 616, a second encrypter 618, and a data logger 620.
  • the first decrypter 616 is configured to receive the encrypted PIN, and is further configured decrypt the encrypted PIN using the private key of UPI server 102.
  • the second encrypter 618 is configured to cooperate with the first decrypter 616 to receive the decrypted PIN, and is further configured to encrypt the decrypted PIN using the public key of the hank.
  • the second encrypter 618 is further configured to send the encrypted PIN to the corresponding user’s hank for second level authentication.
  • the UPI server 102 may be configured to facilitate second level authentication of registered users using their biometrics such as face recognition, fingerprint recognition, iris recognition, voice recognition, and the like.
  • the data logger 620 is configured to continuously log data relating to payment sessions into the data repository 604 in encrypted form.
  • the logged data includes details of each payment session, such as initiator PSP, initiatee PSP, amount transacted, initiator and initiatee VPA/UPI ID and information, and date of transaction.
  • the logged data is retrievable for security purposes.
  • the UPI server 102 acts as a settlement agency for the participating hanks i.e. the UPI server 102 is configured to carry out net settlement between the participating hanks (sender & receiver).
  • the UPI server 102 includes an accumulator module 622 and a settlement module 624. There could be one or more settlement cycles in a day.
  • the accumulator module is configured to cooperate with the data logger 620 to consolidate transactions carried out during the previous settlement cycle.
  • the settlement module 624 is configured to settle the net debit/ credit amount related to the consolidated transactions between the sending and the receiving banks.
  • the settlement module 624 is further configured to create Multiple Net Settlement batches (MNSB) files of the participating banks.
  • MNSB Multiple Net Settlement batches
  • RTGS real-time gross settlement
  • the payable banks shall see a debit entry in their RTGS accounts, while the receiving banks shall see a corresponding credit entry in their RTGS accounts.
  • the banks may carry out their internal reconciliations post settlement.
  • the accumulator module 622 and the settlement module 624 are implemented using one or more processors.
  • the system 100 of the present disclosure is used to effect a payment transaction between a taxi driver and his passenger is shown.
  • the system 100 of the present disclosure is used by a taxi driver to collect fare for the services provided by him to his passenger/customer.
  • the taxi driver in this case the initiator and the payee
  • the taxi driver can use his user device 702 to pull or collect payment (taxi fare) from the passenger using the system 100 of the present disclosure.
  • the passenger provides his VPA/UPI ID to the taxi driver.
  • the taxi driver inputs passenger’s VPA/UPI ID and the amount to be requested in his PSP tool to initiate a payment session and generate a session request.
  • the VPA/UPI ID of the passenger could be inputted by using either a static QR code and separately inputting the amount to be requested or by a dynamic QR code which includes the fare.
  • the payment session is initiated when the passenger scans the QR code.
  • the VPA/UPI ID is provided to the UPI server 102 by the taxi driver’s PSP server (i.e. initiator’s PSP server) 704 after the PSP server 704 performs a first level authentication of the taxi driver using his device information (steps 1 and 2).
  • the UPI server 102 identifies the passenger’s PSP from his VPA/UPI ID and routes the session request to the passenger’s PSP server 710 (step 3).
  • the passenger’s PSP server 710 sends transaction request to the passenger’s PSP tool on his user device 712 (step 4).
  • the passenger accepts the transaction request and inputs his authentication credentials (i.e. PIN) on his user device 712.
  • the passenger’s PSP 710 sends the PIN to the passenger’s bank 706 via the UPI server 102 for carrying out second level authentication and debiting the passenger’s bank account (steps 5 and 6).
  • the requested amount is debited from the passenger’s hank account 706.
  • passenger’s hank Upon debiting passenger’s bank account, passenger’s hank generates a credit request and sends it to the UPI server 102 (step 7).
  • the UPI server 102 then sends the credit request to the taxi driver’s hank 708 to credit taxi driver’s hank account by the desired amount (step 8).
  • a credited amount confirmation is received from taxi driver’s hank 708 at the UPI server 102 (step 9).
  • the successful completion of payment session is communicated with the taxi driver and the passenger on their PSP tools in their user devices 702 and 712 (step 10 and 11).
  • the EPS 100 of the present disclosure can be used by a delivery guy (food delivery, apparel delivery etc.) to eliminate the cash on delivery (COD) problems. It provides a one click two factor authentication wherein a transaction is authorized by only by entering a PIN.
  • the EPS 100 envisaged in the present disclosure can be used by physical stores/merchants to make transactions including vegetable vendor payment, grocery store payments, payment for taxi 1 auto/ bus/ train/ air fares, payment in restaurants/ shops/ petrol pumps, fee payment to various educational institutes, toll plaza payment while travelling, payment to milk vendors/ newspaper vendor, trust/ temple/ relief fund/ NGO donation, payment at the mall, and the like.
  • the EPS 100 can also be used to make utility payments including payment for various bills like electricity, water, telephone, credit card etc., apartment maintenance fee bill presentment and payments, school fee bill presentment and payment, insurance premium payment, installment payment of loan, car loan EMI payment, and the like.
  • online merchants can also use the EPS 100 for E-commerce transactions including COD Payments, In-App payments, online trading, mobile recharge from newspaper advertisement using scan and pay facility, E-commerce (collect/ pull) payment through EPS 100 after checkout, and booking movie tickets. Furthermore, it can also be used in Peer to Peer transactions for remittance (both push & pull), payment to person/friends, sharing of bills with friends, salary payment to driver, and aadhaar / mobile number based inward remittance to another hank account.
  • the banks in India can have tie-ups with banks/ money transfer operators (MTOs) located overseas to facilitate overseas payment transactions using the EPS 100 of the present disclosure.
  • MTO banks/ money transfer operators
  • the customer may provide details such as beneficiary’s bank name, the VP A/ UPI ID or GI of the beneficiary, and the amount (SGD) to be transferred.
  • the customer’s bank/ MTO quotes the converted rate (INR) and receives the amount to be transferred from the customer.
  • the customer’s bank/ MTO then creates an entry in its user interface.
  • the customer’s bank/ MTO has a tie-up with an XYZ bank of India, it sends the beneficiary’s details and credits the amount to be transferred to the XYZ bank, which becomes the sender bank in India.
  • XYZ hank checks all the regulatory requirements and initiates a payment session (in INR) using beneficiary’s VP A/ UPI ID or GI. The money is debited from the XYZ hank and credited to the account of the beneficiary in ABC Bank. A confirmation is then sent back to XYZ Bank, which may pass on the same to the customer’s bank/ MTO overseas.
  • VPA/UPI ID Virtual Payment Address
  • GI Global Identifier
  • IAP In-App Payments

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

La Présente invention concerne le domaine des systèmes de paiement électronique et concerne un système de paiement électronique (EPS) 100 et un procédé. Le système de paiement électronique 100 facilite l'envoi et la réception d'argent plus simplement en utilisant des dispositifs utilisateur 106. Il fournit un serveur d'interface de paiement unifiée (UPI) 102 et permet aux utilisateurs de pousser et de tirer/recevoir des paiements à partir de comptes d'autres personnes/entités. Le système 100 de la présente invention permet d'effectuer des transactions de paiement entre des utilisateurs sans que lesdits utilisateurs aient nécessairement besoin d'avoir les informations bancaires et les coordonnées de compte bancaire les uns des autres. Il élimine le risque du stockage des coordonnées de compte de client et il peut être utilisé par des clients qui n'ont pas de cartes de crédit/débit. Il permet la confidentialité des transactions de paiement et facilite de multiples services publics, le paiement à la livraison, le partage de facture, les paiements/versements de marchand. L'EPS 100 de la présente invention fonctionne sur diverses interfaces, de sorte que des demandes de paiement peuvent être générées sur une interface Web et autorisées sur une interface mobile.
PCT/IB2020/050667 2019-02-28 2020-01-29 Système de paiement électronique et procédé associé WO2020174296A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
SG11202109040UA SG11202109040UA (en) 2019-02-28 2020-01-29 An electronic payment system and method thereof
CA3131260A CA3131260A1 (fr) 2019-02-28 2020-01-29 Systeme de paiement electronique et procede associe

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN201923007905 2019-02-28
IN201923007905 2019-02-28

Publications (1)

Publication Number Publication Date
WO2020174296A1 true WO2020174296A1 (fr) 2020-09-03

Family

ID=72239220

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/050667 WO2020174296A1 (fr) 2019-02-28 2020-01-29 Système de paiement électronique et procédé associé

Country Status (3)

Country Link
CA (1) CA3131260A1 (fr)
SG (1) SG11202109040UA (fr)
WO (1) WO2020174296A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022213150A1 (fr) * 2021-04-09 2022-10-13 DataMesh Group Pty Ltd Système et procédé pour transactions sécurisées

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017221085A1 (fr) * 2016-06-22 2017-12-28 National Payments Corporation Of India Système de paiement électronique et procédé associé

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017221085A1 (fr) * 2016-06-22 2017-12-28 National Payments Corporation Of India Système de paiement électronique et procédé associé

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"UNIFIED PAYMENTS INTERFACE", NATIONAL PAYMENTS CORPORATION OF INDIA, 31 January 2016 (2016-01-31), pages 7 - 60, Retrieved from the Internet <URL:https://www.npci.org.in/sites/default/files/UPI-PG-17_01_31_RBI_Final%20version%201.7.pdf> *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022213150A1 (fr) * 2021-04-09 2022-10-13 DataMesh Group Pty Ltd Système et procédé pour transactions sécurisées

Also Published As

Publication number Publication date
CA3131260A1 (fr) 2020-09-03
SG11202109040UA (en) 2021-09-29

Similar Documents

Publication Publication Date Title
CA3016381C (fr) Systeme de paiement electronique et procede associe
US8116734B2 (en) Party identification in a wireless network
US10453056B2 (en) Secure account creation
CN107230068B (zh) 使用可视数字货币芯片卡支付数字货币的方法和系统
KR20100123895A (ko) 모바일 전화기 지불 거래 시스템의 지불 계좌 데이터의 가공화
CN107230072B (zh) 使用数字货币芯片卡进行网上支付的方法和系统
WO2020174296A1 (fr) Système de paiement électronique et procédé associé
KR20100109992A (ko) 휴대폰 번호를 이용한 결제서비스 제공방법과 이를 위한 기록매체
US20200097968A1 (en) System and logic to convert an existing online bank transfer transaction
Fashoto et al. Development of e-wallet system for Tertiary institution in a Developing country.
Sakurada et al. SoK: Directions and Issues in Formal Verification of Payment Protocols
KR100876589B1 (ko) 펀드 가입에 따른 포인트 처리 방법 및 시스템과 이를 위한기록매체
KR20090002049A (ko) 계좌연동 쿠폰 등록 방법 및 시스템
Saravanan et al. SECURE AND CARD LESS FINGER PRINT BASED ANDROID APPLICATION FOR SHOPPING AND BILL PAYMENTS
KR20090048430A (ko) 계좌연동 쿠폰 운용방법
KR20090002058A (ko) 가치형 계좌 이용 내역 제공 및 정산처리 방법과 그 시스템
KR20090060245A (ko) 가치형 계좌 운용방법
KR20090086371A (ko) 결제승인 처리서버
KR20090002051A (ko) 결제승인 처리방법 및 시스템
KR20090085559A (ko) 복수 계좌 연동형 카드 운용방법
KR20090103852A (ko) 계좌를 이용한 복수 결제승인 처리 시스템
KR20090036479A (ko) 인트라넷 뱅킹을 이용한 무방문 대출처리 방법 및 시스템
KR20090002054A (ko) 게이트웨이를 이용한 가치 적용 결제승인 처리방법 및시스템과 그를 위한 프로그램 기록매체

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20762103

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3131260

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20762103

Country of ref document: EP

Kind code of ref document: A1