TW201835824A - Mobile payment sublicensing method and payment system implemented through same - Google Patents

Abstract

The invention relates to a mobile payment authorization method and system. The method comprises the following steps: enabling a main user terminal to be bound with a payment account; enabling the main user terminal and a slave user terminal to respectively log in a server, and enabling the main user terminal to send a sublicensing request to the server; enabling the server to check the sublicensing request, and issuing Token and a transaction secret key to the slave user terminal after the sublicensing request passes the checking; and enabling the slave user terminal to achieve the payment according to the Token and the transaction secret key. According to the invention, the method can achieve the mobile payment sublicensing between family members and friends based on trust, and can guarantee the transaction safety through the Token and the transaction secret key. Meanwhile, when a user is carrying out the payment, the user does not need to input a password, so the method enables the payment to be quick and convenient, and enables the user experience to be better. Moreover, a cellphone of the user can achieve the payment transaction without connecting the Internet.

Description

Mobile payment transfer authorization method and payment system realized by the same

[0001] The present invention relates to computer communication technologies, and in particular, to a mobile payment transfer authorization method based on a payment token (Token) implementation, a payment system implemented by using the mobile payment transfer authorization method, a mobile terminal, and a server.

[0002] Existing mainstream payment methods require a password to verify the identity of the user to implement payment. This has the following disadvantages: First, the user needs to input a password to pay, the payment process is troublesome, and the user experience is poor. [0003] Second, mobile payment needs to be bound to its own bank card, and it is impossible to realize shared bank card payment between family or friends. [0004] Third, the user account password may be stolen, posing a security risk.

In view of the above problems, an object of the present invention is to provide a trust-based mobile payment transfer authorization method between family members or friends and a mobile payment transfer realized by the method under the premise of ensuring payment security. Authorization system. [0006] The mobile payment authorization method of the present invention is implemented by a primary user terminal, a user terminal, a server, and a merchant terminal, and the method includes the following steps: a binding step, the primary user terminal binding a payment account; The authorization request request step, the main user terminal and the user terminal respectively log in to the server, and the main user terminal sends a transfer authorization request to the server; the authorization request verification step, the server verifies the transfer authorization request, and passes the verification Thereafter, the token is issued to the slave user terminal; and the authorization payment step is performed, and the payment is implemented from the user terminal according to the token and the transaction key. [0007] Preferably, in the transfer authorization request, the primary user terminal presets one or more of an authorization limited amount, an authorization limited time, an authorized limited place, an authorized limited merchant, and whether a transaction confirmation is required. [0008] Preferably, the transfer authorization request verification step comprises the following sub-steps: the server checks the transfer authorization request; after the verification, the token and the transaction key are issued to the slave user terminal at one time; The terminal stores the Token and transaction key in a secure element or in the cloud. [0009] Preferably, the step of transferring the authorization payment comprises the following sub-steps: when the payment transaction is performed from the user terminal, a Token is generated in the cloud or the local security element instead of the PAN, and the Token is used, and one transaction is used for each transaction. The transaction key encrypts the transaction elements (including Token, transaction amount, merchant number, terminal number, etc.) to form a transaction ciphertext, and conducts a consumer transaction at the transaction terminal; the merchant terminal will include the current consumption location, the merchant number, and the transaction amount. And the transaction information of the transaction Token and the transaction ciphertext is sent to the server; the server verifies the transaction token, decrypts the transaction ciphertext information, and verifies the legality of the transaction identity; in the case of successful verification, the server returns the verification success to the merchant terminal. And complete the payment. [0010] Preferably, in the sub-step of the server verifying the transaction token, the server verifies the transaction token and determines whether one or more of the transaction amount, the transaction time, the transaction location, and the transaction merchant are in the transfer as needed. Pre-set in the authorization request. [0011] Preferably, in the sub-step of the server verifying the transaction token, the method further includes: the server sends the transaction information to the main user terminal for transaction confirmation, and the server is in the case that the main user terminal confirms that the transaction is executable. The merchant terminal returned the verification successfully. [0012] The mobile payment transfer authorization system of the present invention is characterized in that the system is provided with: a main user terminal for binding with a payment account and for submitting a transfer authorization request to the server described below; The terminal is configured to receive the Token and the transaction key sent by the following server, store it in the security unit or store it in the cloud, and use the Token to combine the transaction key to perform the transaction; the server is used to access the host The transfer authorization request of the user terminal is checked and the Token and the transaction key are generated and sent to the slave user terminal by the check, and are used for verifying from the slave user terminal when the transaction payment is made. Transmitting the transaction token and the transaction ciphertext and completing the transaction if the verification passes; and the merchant terminal, when the slave user terminal is consuming at the merchant terminal, for including the transaction token, the merchant from the user terminal The transaction information of the number, transaction amount, and transaction ciphertext is submitted to the server. [0013] Preferably, the primary user terminal sets one or more of an authorized limited amount, an authorized limited time, an authorized limited place, an authorized limited merchant, and the like in the transfer authorization request. [0014] Preferably, the merchant terminal has: an LBS module for acquiring a transaction place for generating a transaction; and a communication module for uploading a transaction place and transaction information generated by the transaction to the server. [0015] Preferably, the server is provided with: a Token authorization module, configured to generate a Token and a transaction key, and send the Token and the transaction key to the slave user terminal; and a location calculation module, It is used to calculate the distance between the transaction place and the authorized restriction place, and whether the comparison meets the conditions for the authorized limited place set in the transfer authorization request. [0016] Preferably, the Token authorization module is further configured to set a certain life cycle of the Token. [0017] Preferably, the primary user terminal sets whether a transaction confirmation is required in the transfer authorization request, and if the transaction confirmation is required, the server forwards the information about the transaction to the primary user terminal. It is confirmed by the main user terminal, and the transaction is allowed only after being confirmed by the main user terminal. [0018] The mobile terminal of the present invention is characterized in that: the mobile terminal is configured to receive a Token and a transaction key sent by a server, store the Token and the transaction key in a security unit or store in a cloud, and use the Token combines the transaction key to trade. [0019] The server of the present invention is configured to implement a transfer authorization for the primary user terminal to the user terminal, and is characterized in that it is used for checking the transfer authorization request from the primary user terminal and generating the verification result. The Token and the transaction key are issued to the slave user terminal for verifying the transaction token and the transaction ciphertext sent from the slave user terminal when the transaction payment is made and completing the transaction payment if the verification is passed. [0020] Preferably, the server of the present invention is provided with: a Token authorization module for generating a Token and a transaction key, and the token and the transaction key are sent to the slave user terminal; and the location calculation module is used. In calculating the distance between the transaction location and the authorized restriction location, the comparison is in accordance with the conditions of the authorization-qualified location set in the transfer authorization request. [0021] According to the present invention, it is possible to perform mobile payment transfer authorization from the primary user terminal to the secondary user terminal, thereby enabling trust-based mobile payment transfer authorization between family members and friends. Among them, the transaction can be realized by using the token and the transaction key, thereby ensuring the security of the transaction. Moreover, the user does not need to input a password when paying, which is quick and convenient, and the user experience is good. On the other hand, since a plurality of Tokens and a plurality of transaction keys can be received and stored in advance from the user terminal, the payment transaction can be performed from the user terminal without networking.

[0025] The following are some of the various embodiments of the invention, which are intended to provide a basic understanding of the invention. It is not intended to identify key or critical elements of the invention or the scope of the invention. First, some terms that will appear in the present invention will be described. [0027] The card analog technology is a technique in which an NFC terminal is collectively compared to a card and is accessed by a card reader. [0028] Token technology means that the Token SP generates a Token according to the PAN (Primary Account) provided by the Token Requestor, and then transfers the Token as a substitute value of the PAN to each part of the payment, so that in the payment process, the unique PAN is only in the Token SP. Transfer between the transfer party and the issuer, because the three private lines are connected and trust each other, and when the Token is detected to be risky or expires, a new Token replacement will be generated again, thereby greatly reducing the possibility of PAN leakage during the payment process. Greatly improved the security of PAN. [0029] The LBS location service is also called a Location Based Service (LBS), which acquires location information (latitude and longitude coordinates) of a mobile terminal user through a telecommunication mobile operator's network (eg, GSM network, CDMA network). . [0030] PAN refers to a bank card master account issued by a bank, which is generally composed of a card issuer identifier, a personal account identifier, and a check digit. [0031] HCE (host-based card emulation) refers to a host-based card analogy, which implements card analogy on a mobile terminal equipped with an NFC function. [0032] First, the mobile payment transfer authorization method of the present invention will be described. 1 is a flow chart showing a mobile payment transfer authorization method of the present invention. As shown in FIG. 1, the mobile payment authorization method of the present invention is implemented by a primary user terminal, a user terminal, a server, and a merchant terminal, and the method includes the following steps: binding step S100: primary user The terminal binds the payment account; the transfer authorization request is raised to step S200: the primary user terminal and the user terminal separately log in to the server, and the primary user terminal sends a transfer authorization request to the server, wherein, in the transfer authorization request, the primary user The terminal may set the authorization limited amount, the authorization limited time, the authorized limited location, the authorized limited merchant, etc. according to the need, and may also set whether the transaction confirmation is needed according to the need; the authorization request verification step S300: the server verifies the transfer authorization request, After verification, the Token and the transaction key are issued to the slave user terminal in one time; and the authorization payment step S400 is performed: the payment is realized from the user terminal by using the Token and the transaction key, wherein the Token and the transaction are performed from the user terminal. The key is stored in its secure element (SE) or stored in the cloud When the payment transaction is performed from the user terminal, the cloud or the local security element (SE) generates a Token, and the Token is used to support the cloud flash payment transaction terminal on the merchant side for the consumer transaction, and the merchant terminal will include the current consumption location, the merchant number, and the transaction. The relevant consumption information including the amount and transaction token, transaction ciphertext, etc. is transmitted to the server, and the server verifies the transaction token and the transaction ciphertext, and completes the payment if the verification is successful. [0035] Next, an embodiment of a specific application of the mobile payment transfer authorization method of the present invention will be described. 2 is a flow chart showing an embodiment of a mobile payment transfer authorization method of the present invention. [0037] The mobile payment transfer authorization method of this embodiment is implemented by the main user terminal 100, the user terminal 200, the server 300, and the merchant terminal 400. As shown in FIG. 2, the mobile payment transfer authorization method according to an embodiment of the present invention includes the following specific steps: 1 The primary user terminal 100 binds a payment account (for example, a bank card, a payment) by, for example, a mobile payment application or the like. Card, consumer card, etc.). [0039] 2 The main user terminal 100 and the user terminal 200 respectively log in to the server 300. [0040] 3 The main user terminal 100 issues a transfer authorization request to the server 300 to allow the payment function from the user terminal 200 to be able to use the main user terminal 100, wherein in the transfer authorization request, the main user terminal 100 You can set the authorization limit amount, authorization time limit, authorization limit location, authorized qualified merchant, etc. according to your needs. You can also set whether you need transaction confirmation as needed. [0041] 4 The server 300 checks the related information of the transfer authorization request, and after passing the verification, issues the Token and the transaction key to the slave user terminal 200 (the temporary Token is bound to the main user terminal 100). The payment account) stores the Token and the transaction key from the user terminal 200 in its secure element (SE) or in the cloud, at which time the user terminal 200 has a payment function. According to the setting of the main user terminal 100, the payment transaction from the user terminal 100 having the Token has various types of restrictions such as an authorized limited amount, an authorized limited time, an authorized limited place, an authorized limited merchant, and the like, and if the limit is exceeded, the use is performed. The terminal 200 will lose the payment function. [0042] 5 When the user terminal 200 performs a payment transaction, the cloud or the local security element (SE) generates a Token, and supports the cloud flash payment transaction on the merchant side through HCE (host-based cardemulation) or SE (Secure Element). The terminal 400 performs a consumer transaction. In addition, usually the cloud will generate more than one Token in advance so that the user can still use HCE payment when the device is not connected to the Internet. [0043] The merchant terminal 400 transmits relevant consumption information including the current consumption location, the merchant number, the transaction amount, and the transaction token, the transaction ciphertext, and the like to the server 300. [0044] The server 300 verifies the transaction token and the transaction ciphertext, and determines the transaction amount, the transaction time, the transaction location, whether the transaction merchant meets the authorized limit amount, the authorization limited time, the authorized limited location, the authorized limited merchant, and the like according to the need. [0045] 8 Optionally, the transaction confirmation is performed, and the server 300 transmits the transaction information to the main user terminal 100 for transaction confirmation. [0046] 9 In the case where the verification is successful (optionally including the case where the transaction confirmation is successful), the server 300 returns the verification success to the merchant terminal 400 and completes the payment. [0047] In the present invention, Token solves the problem of card number information leakage, and replaces the card number with a virtual digit string of 13 to 19 bits. The server 300 issues a Token and a transaction key to the slave user terminal 200, and through the transaction key, calculates a transaction ciphertext for each credit card transaction for the validity verification of the transaction identity. Transaction security is achieved through the combination of Token and transaction key. 3 is a block diagram showing the configuration of an embodiment of a mobile payment transfer authorization system of the present invention. As shown in FIG. 3, the mobile payment transfer authorization system of the present invention includes a primary user terminal 100, a secondary user terminal 200, a server 300, and a merchant terminal 400. [0050] The primary user terminal 100 refers to a mobile payment device of the primary user, and may be, for example, a smart phone, a tablet or a wearable device, etc., which may include a payment APP, and a binding payment account (eg, a bank card, a payment card). Etc.), the payment APP can be used to implement user login and subsequent payment transfer authorization. The primary user terminal 100 is configured to bind a payment account for submitting a transfer authorization request to the server 300. The main user terminal 100 can set one or more of the authorized limited amount, the authorized limited time, the authorized limited place, the authorized limited merchant, and the like in the transfer authorization request according to the need, or can set whether the transaction confirmation is needed according to the need. . [0051] The user terminal 200 refers to a user's mobile device, which is installed with a payment APP, such as a smart phone, a tablet or a wearable device, etc., and receives a Token certificate transmitted from the server 300 (or is stored in Cloud), complete the payment. The Token and the transaction key sent by the server 300 are received from the user terminal 200, the Token and the transaction key are stored in the security unit or stored in the cloud, and the Token and the transaction key are used for the transaction. [0052] The server 300 is configured to check the transfer authorization request from the main user terminal 100 and generate a Token and a transaction key in the case of verification and send it to the slave user terminal 200, and use the transaction payment. The transaction Token and the transaction ciphertext sent from the user terminal 200 are verified and the transaction payment is completed in the case of verification. [0053] The server 300 is provided with a Token authorization module 310 and a location calculation module 320. The location calculation module 320 is an optional module. [0054] The Token authorization module 310 is configured to generate a Token and a transaction key, and bind the Token to the card number corresponding to the main transaction terminal, and authorize the Token to the user terminal 200. Further, the Token authorization module 310 can also set a certain life cycle for the Token. [0055] The location calculation module 320 is configured to calculate a distance between the transaction location and the authorized restriction location, and whether the comparison meets the condition of the authorization-defined location set in the transfer authorization request. [0056] The merchant terminal 400 may be, for example, a terminal device such as a POS machine of a merchant. The merchant terminal 400 includes a communication module 410 and an LBS function module 420. The LBS function module 420 is an optional module. The communication module 410 is configured to upload the transaction location (optional) and transaction information generated by the transaction to the server 300. The LBS module 420 is used to detect where the transaction occurred. [0057] According to the present invention, it is possible to perform mobile payment transfer authorization from the primary user terminal to the secondary user terminal, thereby enabling trust-based mobile payment transfer authorization between family members and friends. Among them, the transaction can be realized by using the token and the transaction key, thereby ensuring the security of the transaction. Moreover, the user does not need to input a password when paying, which is quick and convenient, and the user experience is good. On the other hand, since a plurality of Tokens and transaction keys can be received and stored in advance from the user terminal, the payment transaction can be performed from the user terminal without networking. [0058] The above examples mainly illustrate the mobile payment transfer authorization method of the present invention, the payment system implemented by the mobile payment transfer authorization method, the mobile terminal, and the server. Although only a few of the specific embodiments of the present invention have been described, it is understood that the invention may be embodied in many other forms without departing from the spirit and scope of the invention. The present examples and embodiments are to be considered as illustrative and not restricting Modifications and replacements.

[0059]

100‧‧‧ primary user terminal

200‧‧‧From the user terminal

300‧‧‧Server

310‧‧‧Token Authorization Module

320‧‧‧Location Computing Module

400‧‧‧Business terminal

410‧‧‧Communication Module

420‧‧‧LBS module

1 is a flow chart showing a mobile payment transfer authorization method of the present invention. 2 is a flow chart showing an embodiment of a mobile payment transfer authorization method of the present invention. 3 is a block diagram showing the construction of an embodiment of a mobile payment transfer authorization system of the present invention.

Claims (15)

A mobile payment authorization method is implemented by a primary user terminal, a user terminal, a server, and a merchant terminal, and the method includes the following steps: a binding step, the primary user terminal is bound to the payment account; The main user terminal and the user terminal respectively log in to the server, and the main user terminal sends a transfer authorization request to the server; the authorization request verification step, the server verifies the transfer authorization request, and after the verification, the token is issued and The transaction key is given to the slave user terminal; and the authorization payment step is performed, and the user terminal uses the token and the transaction key to implement the payment. The mobile payment authorization method according to claim 1, wherein in the transfer authorization request, the primary user terminal presets an authorized limited amount, an authorized limited time, an authorized limited place, an authorized limited merchant, and whether a transaction confirmation is required. One or more of them. The mobile payment authorization method of claim 2, wherein the transfer authorization request verification step comprises the following sub-steps: the server reconciles the transfer authorization request; after the verification, the Token and the plurality are issued at one time The transaction key is given to the slave user terminal; and the Token and transaction key are stored in the secure element or stored in the cloud from the user terminal. The mobile payment authorization method of claim 3, wherein the transfer authorization payment step comprises the following sub-steps: when the user terminal performs a payment transaction at the transaction terminal, using a Token in the cloud or a local security element instead PAN, using a transaction key for each transaction, encrypting the Token, transaction amount, merchant number, and terminal number as transaction elements to form a transaction ciphertext, and transmitting the merchant terminal for consumption transactions; the merchant terminal will include the current consumption location, the merchant The transaction information of the transaction amount and the transaction token and the transaction ciphertext is sent to the server; the server verifies the transaction token, decrypts the transaction ciphertext information, verifies the validity of the transaction identity; and in the case of successful verification, the server The merchant terminal returns to the verification success and completes the payment. The mobile payment authorization method according to claim 4, wherein in the sub-step of the server verifying the transaction token, the server verifies the transaction token and determines the transaction amount, the transaction time, the transaction place, and the transaction merchant according to the need. Whether one or more of the items are pre-set in the transfer authorization request. The mobile payment authorization method according to claim 5, wherein, in the sub-step of the server verifying the transaction token, the method further comprises: the server sending the transaction information to the main user terminal for confirming the transaction, at the main user terminal When the confirmation transaction is executable, the server returns the verification to the merchant terminal successfully. A mobile payment transfer authorization system, characterized in that the system is provided with: a main user terminal for binding with a payment account and for submitting a transfer authorization request to a server to be received; The Token and transaction key sent by the following server are stored in the security unit or stored in the cloud, and the Token and the transaction key are used for the transaction; the server is used for the authorization request from the primary user terminal. Performing a check and generating a Token and a transaction key in the case of verification and delivering to the slave user terminal, for verifying the transaction token and the transaction ciphertext sent from the slave user terminal when the transaction payment is made and The transaction is completed by the verification; and the merchant terminal submits the transaction information from the user terminal including the transaction token, the merchant number, the transaction amount, and the transaction ciphertext when the user terminal consumes at the merchant terminal. server. The mobile payment transfer authorization system according to claim 7, wherein the primary user terminal sets one of an authorized limit amount, an authorized limited time, an authorized limited place, an authorized limited merchant, or the like in the transfer authorization request or Multiple. The mobile payment transfer authorization system according to claim 8, wherein the merchant terminal has: an LBS module for acquiring a transaction place where the transaction is generated; and a communication module for using the transaction place generated by the transaction and Transaction information is uploaded to the server. The mobile payment transfer authorization system according to claim 9, wherein the server has: a Token authorization module, configured to generate a Token and a transaction key, and issue the Token and the transaction key to the slave use. And a location calculation module, configured to calculate a distance between the transaction location and the authorized restriction location, and whether the comparison meets the condition for the authorized limited location set in the transfer authorization request. The mobile payment transfer authorization system of claim 9, wherein the Token authorization module is further configured to set a certain life cycle of the Token. The mobile payment transfer authorization system according to claim 9, wherein the primary user terminal sets whether a transaction confirmation is required in the transfer authorization request, and if the transaction confirmation is required, the server will be related. The transaction information is forwarded to the primary user terminal and confirmed by the primary user terminal, and the transaction is allowed only after confirmation by the primary user terminal. A mobile terminal is characterized in that the mobile terminal is configured to receive a Token and a transaction key sent by a server in a security unit or store in a cloud, and use the Token and a transaction key to perform a transaction. A server for realizing a transfer authorization to a user terminal by a main user terminal, which is characterized in that it is used for checking a transfer authorization request from a main user terminal and generating a Token and a transaction gold in the case of verification The key is sent to the slave user terminal for verifying the transaction token and the transaction ciphertext sent from the slave user terminal when the transaction payment is made and completing the transaction payment if the verification is passed. The server of claim 14, wherein the server has: a Token authorization module, configured to generate a Token and a transaction key, and the token and the transaction key are sent to the slave user terminal; The location calculation module is configured to calculate a distance between the transaction location and the authorized restriction location, and whether the comparison meets the conditions for the authorized limited location set in the transfer authorization request.