Payment authorization transfer system and payment authorization transfer method based on device connection

By implementing payment authorization transfer systems and methods between IoT devices, the problem of binding and unbinding of payment accounts between devices is solved, and the binding and use and unlocking between devices is realized, which improves the convenience of user experience and payment management.

CN113159761BActive Publication Date: 2025-04-01CHINA UNIONPAY
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202110012599.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-01-06
Publication Date
2025-04-01
Estimated Expiration
2041-01-06

AI Technical Summary

Technical Problem

The fragmentation of IoT devices and user experience problems have made it difficult for the existing technology to achieve payment account binding and unbinding between devices, especially when device cost limitations and screen-free devices.

Method used

Through a payment authorization transfer system and method based on device connection, the access request, authentication and payment steps of the slave device to the master device are realized, allowing the bound payment account of the master device to transfer authorization to the slave device for use.

Benefits of technology

The effects of "binding and using" and "unplugging and closing" are achieved. Users do not need to bind payment accounts to each device one by one. The slave device can have or lose payment capabilities as long as it connects or disconnects the main device, which improves the user experience and simplifies payment account management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113159761B_ABST
    Figure CN113159761B_ABST
Patent Text Reader

Abstract

The present invention relates to a payment authorization transfer method based on device connection and a system thereof. The method comprises: initiating an access request from a slave device to a master device, establishing a communication connection between the slave device and the master device based on the access request; initiating a payment request from the slave device to the master device, and performing legitimacy authentication on both the master device and the slave device based on the payment request; and in the authentication step, if both the master device and the slave device pass the legitimacy authentication, transferring the authorization of the payment account bound to the master device to the slave device for use, and executing the payment request based on the payment account bound to the master device. According to the present invention, "bind and use" and "unplug and close" can be achieved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to computer technology, and in particular to a payment authorization transfer system and a payment authorization transfer method based on the connection between a master device and a slave device. Background Art

[0002] In the current existing technology, the device and the payment account are generally bound through the device or with the help of a mobile phone. For example, in the case of binding through a device, if the device has a screen, it is similar to the existing mobile phone binding payment account, and the account binding is completed directly on the device side; in the case of binding with the help of a mobile phone, the device identification information is input through the mobile phone to realize the card binding, such as the existing touchless parking, touchless refueling and other scenarios, all of which realize the binding of the device identification (license plate) and the bank card through the mobile phone.

[0003] However, IoT devices are clearly fragmented, and it is difficult for some IoT devices to be associated with payment accounts. For example, due to device cost constraints, the devices cannot be equipped with more expensive communication modules such as 4G / WiFi modules, or the devices do not have screens, making it impossible to directly bind to payment accounts from the device side.

[0004] On the other hand, from the perspective of user experience, the current binding relationship between payment accounts and devices is single and fixed. That is, every time a user opens a new device payment, he needs to bind the payment account again. If he wants to close the payment, he still needs to unbind the payment account again. In the future, there will be many devices that can be used for payment, and repeated operations will bring user experience problems. Summary of the invention

[0005] In view of the above problems, the present invention aims to propose a payment authorization transfer system and a payment authorization transfer method based on device connection, which can simplify the payment account binding operation.

[0006] A payment authorization transfer method based on device connection according to one aspect of the present invention is characterized by comprising:

[0007] A connection step, initiating an access request from the slave device to the master device, and establishing a communication connection between the slave device and the master device based on the access request;

[0008] an authentication step, in which a payment request is initiated from the slave device to the master device, and the legitimacy of both the master device and the slave device is authenticated based on the payment request; and

[0009] Payment step: in the authentication step, if both the master device and the slave device pass the legitimacy authentication, the payment account bound to the master device is transferred and authorized to be used by the slave device, and the payment request is executed based on the payment account bound to the master device.

[0010] Optionally, the access request includes a payment account binding status request, and the master device returns the status of the payment account bound to the master device to the slave device according to the payment account binding status request.

[0011] Optionally, in the connecting step, the slave device initiates an access request to the master device, and in the case where multiple master devices respond to the access request, a unique master device is selected according to a filtering condition for communication connection.

[0012] Optionally, the filtering condition is any one of the following:

[0013] According to the signal strength of the main device, the distance of the main device and the user's choice of the main device.

[0014] Optionally, the authentication step includes: authenticating the master device and the slave device respectively.

[0015] Optionally, the authentication step includes:

[0016] The master device authenticates the slave device to obtain the authentication result;

[0017] The authentication result and the main device are authenticated.

[0018] Optionally, in the authentication step, authentication is performed using a symmetric encryption algorithm based on the master device ID, the slave device ID and a random number.

[0019] Optionally, in the payment step, the payment account bound to the master device is transferred and authorized to be used by the slave device based on the master device ID.

[0020] Optionally, the authentication step and the payment step are performed only under the premise that a communication connection is maintained between the slave device and the master device.

[0021] Optionally, in the connecting step, a Bluetooth communication connection or a local area network communication connection is established between the slave device and the master device.

[0022] A payment authorization transfer system based on device connection according to one aspect of the present invention is characterized in that it comprises: a slave device, a master device and a payment backend,

[0023] Wherein, the slave device includes:

[0024] A first communication module, configured to establish a communication connection with the main device; and

[0025] The first security service module is used to perform the legitimacy authentication related to the slave device authentication,

[0026] The main device comprises:

[0027] A second communication module, used to communicate with the slave device and the payment backend respectively;

[0028] a trusted payment module, configured to store the payment account information bound to the master device and return the payment account status bound to the master device to the slave device according to the access request; and

[0029] The second security service module is used to perform the legitimacy authentication of the slave device and the master device.

[0030] The payment backend includes:

[0031] An authentication platform for authenticating the legitimacy of both the master device and the slave device; and

[0032] The payment system, when both the master device and the slave device have passed the legitimacy authentication, transfers the authorization of the payment account bound to the master device to the slave device for use, and executes the payment request initiated by the slave device based on the payment account bound to the master device.

[0033] Optionally, the first communication module includes a payment account binding status request in the access request.

[0034] The trusted payment module returns the payment account status bound to the master device to the slave device according to the payment account binding status request.

[0035] Optionally, the slave device initiates an access request to the master device through the first communication module, and in the case where multiple master devices respond to the access request, a unique master device is selected according to a filtering condition for communication connection.

[0036] Optionally, the filtering condition is any one of the following:

[0037] According to the signal strength of the main device, the distance of the main device and the user's choice of the main device.

[0038] Optionally, the first security service module pre-stores a slave device ID and a slave device encryption key.

[0039] The second security service module pre-stores the master device ID and the master device encryption key.

[0040] The authentication platform pre-stores a first corresponding relationship between the slave device ID and the slave device encryption key, and a second corresponding relationship between the master device ID and the master device encryption key.

[0041] A slave device according to one aspect of the present invention is characterized by comprising:

[0042] A communication module, used to establish a communication connection with an external host device and to initiate an access request to the host device; and

[0043] Security service module, used to perform legal authentication related to slave device authentication,

[0044] The communication module includes a payment account binding status request in the access request and receives the payment account status bound to the main device returned from the main device.

[0045] Optionally, the slave device initiates an access request to the master device through the communication module, and in the case where multiple master devices respond to the access request, a unique master device is selected according to a filtering condition for communication connection.

[0046] Optionally, the filtering condition is any one of the following:

[0047] According to the signal strength of the main device, the distance of the main device and the user's choice of the main device.

[0048] A main device according to one aspect of the present invention is characterized by comprising:

[0049] The communication module is used to communicate with the external slave device and the external payment backend respectively;

[0050] A trusted payment module, used to store the payment account information bound to the master device and return the payment account status bound to the master device to the slave device according to the access request from the slave device; and

[0051] The security service module is used to pre-store the master device ID and the master device encryption key and to perform actions related to legitimacy authentication.

[0052] The payment backend of one aspect of the present invention is characterized by comprising:

[0053] An authentication platform for authenticating the legitimacy of both the master and slave devices; and

[0054] The payment system, when both the master device and the slave device have passed the legitimacy authentication, transfers the authorization of the payment account bound to the master device to the slave device for use, and executes the payment request initiated by the slave device based on the payment account bound to the master device.

[0055] Optionally, the authentication platform is used to authenticate the legitimacy of the master device and the slave device respectively, or the authentication platform authenticates the master device and the authentication result of the master device on the slave device.

[0056] Optionally, the authentication platform pre-stores a first corresponding relationship between the slave device ID and the slave device encryption key, and a second corresponding relationship between the master device ID and the master device encryption key.

[0057] A computer-readable medium according to one aspect of the present invention stores a computer program thereon, wherein when the computer program is executed by a processor, the device-connection-based payment authorization transfer method is implemented.

[0058] A computer device according to one aspect of the present invention comprises a storage module, a processor, and a computer program stored on the storage module and executable on the processor, wherein the processor implements the device connection-based payment authorization transfer method when executing the computer program.

[0059] According to the device connection-based payment authorization transfer method and the device connection-based payment authorization transfer system of the present invention, it is possible to achieve "bind and use", that is, as long as the slave device is connected to a main device that already has a payment account, it will have payment capabilities, and the user does not need to bind the payment account to each device one by one; it is possible to achieve "unplug and shut down", as long as the slave device disconnects from the main device that already has a payment account, payment unbinding can be achieved, thereby achieving the effect of quickly and dynamically acquiring payment capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 It is a schematic diagram of the general flow of the payment authorization transfer method based on device connection of the present invention.

[0061] Figure 2 It is a structural block diagram of the payment authorization transfer system based on device connection of the present invention.

[0062] Figure 3 It shows the payment process using a mobile phone as an IoT device as an example.

[0063] Figure 4 It is a flowchart of the connection process in the payment authorization transfer method based on device connection according to the first embodiment of the present invention.

[0064] Figure 5 It is a flowchart of the authentication and payment process in the payment authorization transfer method based on device connection according to the first embodiment of the present invention.

[0065] Figure 6 It is a flowchart of the connection process in the payment authorization transfer method based on device connection according to the second embodiment of the present invention.

[0066] Figure 7 It is a flowchart of the authentication and payment process in the payment authorization transfer method based on device connection according to the second embodiment of the present invention. DETAILED DESCRIPTION

[0067] The following describes some of the various embodiments of the present invention, which are intended to provide a basic understanding of the present invention, but are not intended to identify the key or decisive elements of the present invention or to limit the scope of protection.

[0068] For the purpose of brevity and illustration, the principles of the present invention are described herein mainly with reference to its exemplary embodiments. However, those skilled in the art will readily recognize that the same principles are equally applicable to all types of device-connected payment authorization transfer systems and payment authorization transfer methods, and these same principles can be implemented therein, and any such changes do not depart from the true spirit and scope of this patent application.

[0069] Moreover, in the following description, reference is made to the accompanying drawings, which illustrate specific exemplary embodiments. Electrical, mechanical, logical and structural changes may be made to these embodiments without departing from the spirit and scope of the present invention. In addition, although the features of the present invention are disclosed in conjunction with only one of several implementations / embodiments, this feature may be combined with one or more other features of other implementations / embodiments as may be desirable and / or advantageous for any given or identifiable function. Therefore, the following description should not be regarded as limiting, and the scope of the present invention is defined by the appended claims and their equivalents.

[0070] Terms such as “having” and “including” indicate that in addition to the units (modules) and steps directly and explicitly stated in the specification and claims, the technical solution of the present invention does not exclude the situation where it has other units (modules) and steps that are not directly or explicitly stated.

[0071] Figure 1 The schematic diagram is a schematic flow chart of the payment authorization transfer method based on device connection of the present invention. The payment authorization transfer method based on device connection of the present invention is implemented by a slave device, a master device and a payment backend.

[0072] like Figure 1 As shown, the payment authorization transfer method based on device connection of the present invention includes:

[0073] Connecting step S100: the slave device initiates an access request to the master device, and a communication connection is established between the slave device and the master device based on the access request;

[0074] Authentication step S200: a payment request is initiated from the master device of the device box, and the payment backend performs legitimacy authentication on the master device and the slave device. When both the master device and the slave device pass the legitimacy authentication, the payment backend transfers the payment account bound to the master device to the slave device for use; and

[0075] Payment step S300: the payment backend executes the payment request initiated by the slave device based on the payment account bound to the master device.

[0076] Among them, as a specific implementation of the connection step S100, when the slave device initiates payment, it searches for the surrounding master devices. After establishing a connection with the master device through the connection step S100, the master device forwards the device authentication information to the payment backend in the authentication step S200. Only when the payment backend authenticates both the master device and the slave device, can the payment authorization of the master device be transferred to the slave device, that is, in the payment step S300, the slave device can use the bound payment account of the master device to complete the payment through the payment backend.

[0077] As another specific implementation of the connection step S100, the slave device sends a scanning signal to the surroundings, initiates an access request from the slave device to multiple master devices, and when there are multiple master devices responding, establishes a communication connection between the slave device and one of the multiple master devices based on the access request.

[0078] In the authentication step S200, the authentication mode of the master and slave devices by the authentication platform can be a one-to-one authentication as an implementation, that is, the authentication platform authenticates the authentication information of the master device and the slave device respectively, or as another implementation, it can also be a connection authentication, that is, the master device authenticates the slave device, and the authentication platform authenticates the master device and the authentication result of the master device.

[0079] Regarding the legitimacy authentication, considering the computing power of IoT devices, a symmetric key algorithm is used here. For example, the master and slave devices have pre-burned the master and slave device encryption keys, and the correspondence between the master and slave device encryption keys and the master and slave device IDs is pre-stored in the authentication platform. During the authentication implementation process, the master device usually initiates an authentication challenge (for example, a random number) to the authentication platform on behalf of the slave device. The authentication platform compares the random number sent with the random number sent by the master and slave devices to implement legitimacy authentication.

[0080] In the present invention, the authentication step S200 and the payment step S300 are performed only under the premise of maintaining a communication connection between the slave device and the master device. Therefore, as long as the communication connection between the slave device and the master device is disconnected, the payment account transfer authorization is automatically released.

[0081] As described above, according to the payment authorization transfer method based on device connection of the present invention, firstly, the device payment authorization and the device connection status can be synchronized. For example, once the slave device is disconnected from the master device, the slave device cannot use the payment account bound to the master device to complete the payment.

[0082] Furthermore, according to the device connection-based payment authorization transfer method of the present invention, the slave device can also identify the master device with a payment account from the surrounding devices to prevent connection to useless surrounding devices.

[0083] As a specific implementation, in the connection step S100, the access request includes a payment account binding status request, and the master device returns the payment account status bound to the master device to the slave device according to the payment account binding status request.

[0084] Moreover, when there are multiple master devices, the list of payment account statuses bound to the master device is returned, and the slave device can select a unique master device for communication connection according to the filtering conditions. The filtering conditions are any of the following: by the master device signal strength, by the master device distance, and by the user's selection of the master device.

[0085] As mentioned above, when the slave device initiates the process of establishing a connection with the master device, the master device needs to transmit back its payment account binding status. The slave device can filter surrounding devices based on the payment account binding status. The filtering method can be to directly filter by account status so that the user can select the master device to be associated, or the slave device can select a unique master device for connection by combining parameters such as the signal strength and distance of surrounding devices. In this way, the master device binds the payment account once, and subsequent slave devices connected to the master device can complete payment through the payment account bound to the master device.

[0086] Figure 2 It is a structural block diagram of the payment authorization transfer system based on device connection of the present invention.

[0087] like Figure 2 As shown, the payment authorization transfer system based on device connection of the present invention includes: a slave device 100, a master device 200 and a payment backend 300.

[0088] The slave device 100 includes:

[0089] A first communication module 110, configured to establish a communication connection with the main device 200 and to initiate an access request and a payment request to the main device 200; and

[0090] The first security service module 120 is used to perform authentication actions related to the legitimacy of the slave device.

[0091] As an implementation, the first communication module 110 may have a communication module such as Bluetooth or WiFi, and may be connected to the master device 200 via Bluetooth or WiFi. Further, in order to save equipment cost, the slave device 100 itself may not have the function of connecting to the Internet but only have the Bluetooth function.

[0092] The first security service module 120 , for example, pre-stores the slave device ID, encryption / signature, and security certificate. For example, the slave device encryption key may be pre-burned therein.

[0093] The main device 200 includes:

[0094] The second communication module 210 is used to communicate with the slave device 100 and the payment backend 300 respectively;

[0095] The trusted payment module 220 is used to store the payment account information bound to the master device and return the payment account status bound to the master device to the slave device 100 according to the access request; and

[0096] The second security service module 230 is used to execute actions related to the legitimacy authentication of the slave device 100 and the master device 200 .

[0097] Among them, the second communication module 200 can be, for example, a communication module equipped with a Bluetooth module, a WiFi module, a 4G / 5G module, a dedicated line module, etc., and can communicate and connect with the slave device 100 through the Bluetooth module and the WiFi module, and can communicate and connect with the payment background 300 through the dedicated line module, the 4G / 5G module, and the WiFi module.

[0098] The trusted payment module 220 can protect sensitive payment data stored in the device, and provide an API to the device application so that the device application can read the payment account binding status (for example, "1" indicates binding and "0" indicates unbinding). As an implementation method of the trusted payment module 220, a trusted payment chip can be used.

[0099] The second security service module 230 pre-stores the master device ID, encryption / signature, and security certificate. For example, the master device encryption key may be pre-burned therein.

[0100] The payment backend 300 includes:

[0101] The authentication platform 310 is used to authenticate the legitimacy of the master device 200 and the slave device 100 to ensure that the devices used in subsequent transactions are trustworthy devices; and the payment system 320, when the authentication platform 310 passes the legitimacy authentication of the master device 200 and the slave device 100, transfers the authorization of the payment account bound to the master device to the slave device 100 for use, and executes the payment request initiated by the slave device based on the payment account bound to the master device.

[0102] Preferably, the first communication module 110 includes a payment account binding status request in the access request, and the trusted payment module 220 returns the payment account status bound to the master device 200 to the slave device 100 according to the payment account binding status request.

[0103] Optionally, the slave device 100 initiates an access request to the master device 200 through the first communication module 110, and selects a unique master device for communication connection according to a filtering condition, wherein the filtering condition is any one of the following: master device signal strength, master device distance, and user selection of the master device.

[0104] Optionally, the first security service module 120 pre-stores the slave device ID and the slave device encryption key, the second security service module 230 pre-stores the master device ID and the master device encryption key, and the authentication platform 310 pre-stores the first correspondence between the slave device ID and the slave device encryption key, and the second correspondence between the master device ID and the master device encryption key.

[0105] For ease of understanding, Figure 3 It shows the payment process using a mobile phone as an IoT device as an example. Figure 3 (a) indicates that the user selects nearby device payment when making a payment; (b) indicates that the surrounding devices (i.e., the main device) with payment accounts are displayed in a list; and (c) the payment accounts bound to the main device are displayed so that the user can select a card and complete the payment.

[0106] According to the device connection-based payment authorization transfer method and the device connection-based payment authorization transfer system of the present invention, it is possible to achieve "bind and use", that is, as long as the slave device is connected to a main device that already has a payment account, it will have payment capabilities, and the user does not need to bind the payment account to each device one by one; it is possible to achieve "unplug and shut down", as long as the slave device disconnects from the main device that already has a payment account, payment unbinding can be achieved, thereby achieving the effect of quickly and dynamically acquiring payment capabilities.

[0107] Next, a specific implementation of the payment authorization transfer method based on device connection of the present invention is described.

[0108] First embodiment

[0109] In the first embodiment, the master device is bound to the payment account by default, and the slave device discovers the surrounding devices through Bluetooth, WiFi, or local area network, etc., and Bluetooth is used as an example for explanation below. In addition, in the first embodiment, the authentication platform performs authentication by authenticating the master device and the slave device separately.

[0110] Figure 4 It is a flowchart of the connection process in the payment authorization transfer method based on device connection according to the first embodiment of the present invention.

[0111] like Figure 4 As shown, the connection process in the payment authorization transfer method based on device connection of the first embodiment of the present invention includes:

[0112] Step S1: The slave device sends a request frame while trying to access the master device. The request frame adds a request for the master device payment account binding status based on the general active scanning Bluetooth access;

[0113] Step S2: The main device obtains the device payment account binding status by calling the trusted payment module;

[0114] Step S3: The master device returns the payment account binding status and other device parameters to the slave device;

[0115] Step S4: The slave device displays the master device bound to the payment account and the user can choose it, or it defaults to the master device with the strongest signal strength or the master device closest to it. For example, if the slave device has a screen, the slave device can display the master device bound to the payment account and the user can choose it. If the slave device does not have a screen, the master device with the strongest signal can be defaulted to the access device.

[0116] Here, in order to improve the security level, as a safety guarantee, the master device can set a Bluetooth password, and the slave device can only connect after entering the Bluetooth password.

[0117] Figure 5 It is a flowchart of the authentication and payment process in the payment authorization transfer method based on device connection according to the first embodiment of the present invention.

[0118] like Figure 5 As shown, the authentication and payment process in the payment authorization transfer method based on device connection of the first embodiment of the present invention includes:

[0119] Step S11: The user initiates a payment request on the slave device;

[0120] Step S12: The slave device requests payment from the master device via the local area network;

[0121] Step S13: The master device initiates a payment request (including authentication challenge) to the device authentication platform;

[0122] Step S14: the authentication platform sends a random number to the master device;

[0123] Step S15: the master device forwards the random number to the slave device;

[0124] Step S16: The slave device encrypts the random number using the slave device encryption key to generate a slave device ciphertext;

[0125] Step S17: The slave device sends the slave device ID and ciphertext to the master device;

[0126] Step S18: The master device encrypts the random number using the master device encryption key to generate a master device ciphertext;

[0127] Step S19: The master device sends the master device ID and master device ciphertext, the slave device ID and slave device ciphertext to the device authentication platform;

[0128] Step 20: The authentication platform authenticates the master and slave devices based on the stored correspondence between the master device ID and the master device encryption key, and the correspondence between the slave device ID and the slave device encryption key;

[0129] Step S21: After both the master and slave devices have passed authentication, the authentication platform sends the master device ID to the payment system;

[0130] Step S22: the payment system finds the corresponding account bound to the main device according to the main device ID and completes the payment;

[0131] Step S23: The payment system returns the payment result to the authentication platform;

[0132] Step S24: the authentication platform returns the payment result to the main device; and

[0133] Step S25: The master device returns the payment result to the slave device.

[0134] In the first implementation, the authentication platform authenticates the master and slave devices respectively. When both parties pass the authentication, the payment account bound to the master device can be transferred and bound to the slave user for use, thereby achieving "bind and use", and the user can make payments without binding the payment account to the slave device. Moreover, as long as the slave device disconnects from the master device that already has a payment account, the payment can be untied, achieving the effect of quickly and dynamically obtaining payment capabilities.

[0135] Second embodiment

[0136] In the second embodiment, it is assumed that all master devices are bound to a payment account, the slave device has a scanning function, and can connect to multiple master devices at one time. The user can choose any payment on the master device to make payment, and in the second embodiment, the authentication platform uses a connection authentication method for authentication, that is, the master device authenticates the slave device, the authentication platform authenticates the master device and the authentication result of the master device.

[0137] Figure 6 FIG. 1 is a flow chart of the connection process in the payment authorization transfer method based on device connection according to the second embodiment of the present invention. Figure 6 In the figure, the master device 1 and the master device 2 are taken as an example, but the present invention does not impose any limitation on the number of the master devices.

[0138] like Figure 6 As shown, the connection process in the payment authorization transfer method based on device connection of the second embodiment of the present invention includes:

[0139] Step S31: The slave device scans surrounding devices (master device 1), and the connection method may be Bluetooth, WiFi, etc.;

[0140] Step S31': the slave device scans surrounding devices (master device 1), and the connection method may be Bluetooth, WiFi, etc.;

[0141] Step S32: The slave device accesses the master device 1;

[0142] Step S32': the slave device accesses the master device 2;

[0143] Step S33: the slave device sends a payment request to the master device 1;

[0144] Step S33': the slave device sends a payment request to the master device 2;

[0145] Step S34: the main device 1 requests the payment backend to display a list of bound payment accounts;

[0146] Step S34': the main device 2 requests the payment backend to display a list of bound payment accounts;

[0147] Step S35: the payment backend returns a list of bound payment accounts to the main device 1;

[0148] Step S35': the payment backend returns the bound payment account list to the main device 2;

[0149] Step S36: the master device 1 returns a list of payment accounts bound to the master device 1 to the slave device; and

[0150] Step S36': the master device 2 returns a list of payment accounts bound to the master device 2 to the slave device.

[0151] In this way, the user can select a payment account from the payment account bound to the main device 1 and the payment account bound to the main device 2 to make payment as needed.

[0152] At the same time, further device authentication can be completed on the main device side. The payment background authenticates the authentication result of the main device and uses the account bound to the main device for payment.

[0153] Figure 7 It is a flowchart of the authentication and payment process in the payment authorization transfer method based on device connection according to the second embodiment of the present invention.

[0154] like Figure 7 As shown, the authentication and payment process in the payment authorization transfer method based on device connection of the second embodiment of the present invention includes:

[0155] Step S41: The slave device initiates an authentication request to the master device;

[0156] Step S42: the master device sends an authentication challenge code (i.e., a random number) to the slave device;

[0157] Step S43: The slave device encrypts the random number using the slave device encryption key to obtain a slave device ciphertext;

[0158] Step S44: The slave device sends the slave device ciphertext to the master device;

[0159] Step S45: the master device authenticates the ciphertext of the slave device;

[0160] Step S46: After the authentication is passed, the master device uses the master device encryption key to encrypt the master device authentication result to generate the master device ciphertext (i.e., the authentication result ciphertext);

[0161] Step S47: the master device sends the master device ciphertext (i.e., the authentication result ciphertext) and the master device ID to the authentication platform;

[0162] Step S48: Authentication platform

[0163] Authenticating the master device and the master device authentication result according to the master device ID, wherein the authentication platform performs authentication based on the pre-stored correspondence between the slave device ID and the slave device encryption key, and the correspondence between the master device ID and the master device encryption key;

[0164] Step S49: If the authentication is successful, the authentication platform sends the primary device ID to the payment system;

[0165] Step S50: the payment system finds the bound payment account according to the main device ID and completes the payment;

[0166] Step S51: the payment system returns the payment result to the authentication platform;

[0167] Step S52: The authentication platform returns the payment result to the main device.

[0168] In the second embodiment, the slave device has a scanning function and can connect to multiple master devices at one time. The user can choose any payment on the master device to make a payment, thereby achieving "bind and use", and the user can make a payment without binding the payment account to the slave device. Moreover, as long as the slave device disconnects from the master device that has a payment account, the payment can be untied, achieving the effect of quickly and dynamically obtaining payment capabilities.

[0169] The present invention also provides a computer-readable medium having a computer program stored thereon, characterized in that when the computer program is executed by a processor, it is the above-mentioned payment authorization transfer method based on device connection.

[0170] The present invention also provides a computer device, comprising a storage module, a processor, and a computer program stored on the storage module and executable on the processor, wherein the processor implements the above-mentioned device connection-based payment authorization transfer method when executing the computer program.

[0171] The above examples mainly illustrate the payment authorization transfer system and payment authorization transfer method based on device connection of the present invention. Although only some of the specific embodiments of the present invention are described, it should be understood by those skilled in the art that the present invention can be implemented in many other forms without departing from its subject matter and scope. Therefore, the examples and embodiments shown are regarded as illustrative rather than restrictive, and the present invention may cover various modifications and substitutions without departing from the spirit and scope of the present invention as defined in the appended claims.

Claims

1. A payment authorization transfer method based on device connection, characterized in that: include: A connection step, initiating an access request from the slave device to the master device, and establishing a communication connection between the slave device and the master device based on the access request, wherein a Bluetooth communication connection or a local area network communication connection is established between the slave device and the master device; an authentication step, in which the slave device initiates a payment request to the master device, and based on the payment request, performs legitimacy authentication on both the master device and the slave device; and a payment step, in which, if both the master device and the slave device pass the legitimacy authentication in the authentication step, the payment account bound to the master device is transferred and authorized to be used by the slave device, and the payment request is executed based on the payment account bound to the master device, The access request includes a payment account binding status request, and the master device returns the payment account status bound to the master device to the slave device according to the payment account binding status request. The authentication step and the payment step are performed only under the premise that the communication connection between the slave device and the master device is maintained, and the payment account transfer authorization is automatically released as soon as the communication connection between the slave device and the master device is disconnected, Among them, the legitimacy authentication includes: the slave device initiates an authentication request to the master device, the master device sends an authentication challenge code to the slave device, the slave device encrypts the challenge code using the slave device encryption key to obtain the slave device ciphertext, the slave device sends the slave device ciphertext to the master device, the master device authenticates the slave device ciphertext, after the authentication is passed, the master device uses the master device encryption key to encrypt the master device authentication result to generate the master device ciphertext, the master device sends the master device ciphertext and the master device ID to the authentication platform, and the authentication platform authenticates the master device and the master device ciphertext according to the master device ID.

2. The payment authorization transfer method based on device connection as claimed in claim 1, characterized in that: In the connection step, the slave device initiates an access request to the master device, and in the case where multiple master devices respond to the access request, a unique master device is selected according to the filtering condition for communication connection.

3. The payment authorization transfer method based on device connection as claimed in claim 2, characterized in that: The filtering condition is any of the following: According to the signal strength of the main device, the distance of the main device and the user's choice of the main device.

4. The payment authorization transfer method based on device connection as claimed in claim 1, characterized in that: The authentication step includes: authenticating the master device and the slave device respectively.

5. The payment authorization transfer method based on device connection as claimed in claim 1, characterized in that: The authentication step includes: The master device authenticates the slave device to obtain an authentication result; and The authentication result and the main device are authenticated.

6. The payment authorization transfer method based on device connection as claimed in claim 1, characterized in that: In the authentication step, authentication is performed using a symmetric encryption algorithm based on the master device ID, the slave device ID and a random number.

7. The payment authorization transfer method based on device connection as claimed in claim 1, characterized in that: In the payment step, the payment account bound to the master device is transferred and authorized to be used by the slave device based on the master device ID.

8. A payment authorization transfer system based on device connection, characterized in that: include: From the device, the master device and the payment backend, Wherein, the slave device includes: A first communication module, configured to establish a communication connection with the main device; and The first security service module is used to perform the legitimacy authentication related to the slave device authentication, The main device comprises: A second communication module, used to communicate with the slave device and the payment backend respectively; a trusted payment module, configured to store the payment account information bound to the master device and return the payment account status bound to the master device to the slave device according to the access request; and The second security service module is used to perform the legitimacy authentication of the slave device and the master device. The payment backend includes: An authentication platform for authenticating the legitimacy of both the master and slave devices; and The payment system, when both the master device and the slave device have passed the legality authentication, transfers the authorization of the payment account bound to the master device to the slave device for use, and executes the payment request initiated by the slave device based on the payment account bound to the master device. The first communication module causes the access request to include a payment account binding status request, The trusted payment module returns the payment account status bound to the master device to the slave device according to the payment account binding status request, Among them, a Bluetooth communication connection or a local area network communication connection is established between the slave device and the master device. The legitimacy authentication and payment request are only performed under the premise of maintaining the communication connection between the slave device and the master device, and the payment account transfer authorization is automatically released as soon as the communication connection between the slave device and the master device is disconnected. Among them, the legitimacy authentication includes: the slave device initiates an authentication request to the master device, the master device sends an authentication challenge code to the slave device, the slave device encrypts the challenge code using the slave device encryption key to obtain the slave device ciphertext, the slave device sends the slave device ciphertext to the master device, the master device authenticates the slave device ciphertext, after the authentication is passed, the master device uses the master device encryption key to encrypt the master device authentication result to generate the master device ciphertext, the master device sends the master device ciphertext and the master device ID to the authentication platform, and the authentication platform authenticates the master device and the master device ciphertext according to the master device ID.

9. The payment authorization transfer system based on device connection as claimed in claim 8, characterized in that: The slave device initiates an access request to the master device through the first communication module, and in the case where multiple master devices respond to the access request, selects a unique master device for communication connection according to a filtering condition.

10. The payment authorization transfer system based on device connection as claimed in claim 9, characterized in that: The filtering condition is any of the following: According to the signal strength of the main device, the distance of the main device and the user's choice of the main device.

11. The payment authorization transfer system based on device connection as claimed in claim 9, characterized in that: The first security service module pre-stores the slave device ID and the slave device encryption key. The second security service module pre-stores the master device ID and the master device encryption key. The authentication platform pre-stores a first corresponding relationship between the slave device ID and the slave device encryption key, and a second corresponding relationship between the master device ID and the master device encryption key.

12. A slave device, characterized in that: include: A communication module, used to establish a communication connection with an external master device and to initiate an access request to the master device; as well as Security service module, used to perform the legality authentication related to slave device authentication, The communication module includes a payment account binding status request in the access request and receives the payment account status of the master device bound to the master device returned from the master device. When the legitimacy authentication is passed, the payment account bound to the external master device is transferred and authorized to the slave device for use. The slave device executes the payment request based on the payment account bound to the master device. A Bluetooth communication connection or a local area network communication connection is established between the slave device and the external master device. The legitimacy authentication and payment request are only performed under the premise of maintaining the communication connection between the slave device and the master device, and the payment account transfer authorization is automatically released as soon as the slave device is disconnected from the external master device. Among them, the legitimacy authentication includes: the slave device initiates an authentication request to the master device, the master device sends an authentication challenge code to the slave device, the slave device encrypts the challenge code using the slave device encryption key to obtain the slave device ciphertext, the slave device sends the slave device ciphertext to the master device, the master device authenticates the slave device ciphertext, after the authentication is passed, the master device uses the master device encryption key to encrypt the master device authentication result to generate the master device ciphertext, the master device sends the master device ciphertext and the master device ID to the authentication platform, and the authentication platform authenticates the master device and the master device ciphertext according to the master device ID.

13. The slave device according to claim 12, characterized in that: The slave device initiates an access request to the master device through the communication module, and in the case where multiple master devices respond to the access request, selects a unique master device for communication connection according to the filtering condition.

14. The slave device according to claim 13, characterized in that: The filtering condition is any of the following: According to the signal strength of the main device, the distance of the main device and the user's choice of the main device.

15. The slave device according to claim 12, characterized in that: The communication module has a scanning function.

16. A master device, characterized in that: include: The communication module is used to communicate with the external slave device and the external payment backend respectively; A trusted payment module, used to store the payment account information bound to the master device and return the payment account status bound to the master device to the slave device according to the access request from the slave device; as well as A security service module is used to pre-store the master device ID and the master device encryption key and to perform actions related to legitimacy authentication. The legitimacy authentication and payment request are only performed under the premise of maintaining communication connection between the slave device and the master device, and the payment account transfer authorization is automatically released when the slave device and the master device are disconnected from the communication connection. Establish a Bluetooth communication connection or a LAN communication connection between the slave device and the master device. Among them, the legitimacy authentication includes: the slave device initiates an authentication request to the master device, the master device sends an authentication challenge code to the slave device, the slave device encrypts the challenge code using the slave device encryption key to obtain the slave device ciphertext, the slave device sends the slave device ciphertext to the master device, the master device authenticates the slave device ciphertext, after the authentication is passed, the master device uses the master device encryption key to encrypt the master device authentication result to generate the master device ciphertext, the master device sends the master device ciphertext and the master device ID to the authentication platform, and the authentication platform authenticates the master device and the master device ciphertext according to the master device ID.

17. A computer readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the device connection-based payment authorization transfer method described in any one of claims 1 to 7 is implemented.

18. A computer device comprising a storage module, a processor, and a computer program stored in the storage module and executable on the processor, characterized in that: When the processor executes the computer program, the device connection-based payment authorization transfer method according to any one of claims 1 to 7 is implemented.

19. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the device connection-based payment authorization transfer method described in any one of claims 1 to 7 is implemented.

Citation Information

Patent Citations

  • Mobile payment sublicensing method and payment system implemented through same

    CN107256484A

  • Payment method and device based on verification terminal

    CN109155778A