WO2023040416A1

WO2023040416A1 - Cloud hosting method and system for hardware payment device

Info

Publication number: WO2023040416A1
Application number: PCT/CN2022/102772
Authority: WO
Inventors: 李东声
Original assignee: 天地融科技股份有限公司
Priority date: 2021-09-15
Filing date: 2022-06-30
Publication date: 2023-03-23
Also published as: CN115828196A

Abstract

A cloud hosting method and system for a hardware payment device. The method comprises: a cloud hosting server receives an account opening request, allocates and activates a hardware payment device according to identity identification information, binds the user identity identification information with the hardware payment device, receives a transaction request, and sends, according to a binding relationship between the user identity identification information and the hardware payment device, the transaction request to the hardware payment device corresponding to the user identity identification information; the hardware payment device determines a transaction type according to transaction information, obtains a first data packet for payment if the transaction type is payment, and sends the first data packet for payment to the cloud hosting server; if the transaction type is receipt, the hardware payment device extracts a second data packet for payment from the transaction information, and stores the second data packet for payment.

Description

A cloud hosting method and system for hardware payment equipment

Cross References to Related Applications

This disclosure is based on a Chinese patent application with application number 202111079446.4 and a filing date of September 15, 2021, and claims the priority of this Chinese patent application. The entire content of this Chinese patent application is hereby incorporated by reference into this disclosure.

technical field

The present disclosure relates to the technical field of electronic payment, in particular to a cloud hosting method and system for a hardware payment device.

Background technique

In the existing electronic transactions, after the user opens an account, he usually needs to go to the counter to get a user-side hardware payment device, which can transmit the payment data package with the merchant or other user's device when receiving and paying, so as to complete the electronic transaction . However, this transaction method requires the user to go to the counter to get the device, which is not convenient enough. Therefore, there is an urgent need for a new method and system that can complete the above-mentioned electronic transactions without requiring the user to receive a hardware payment device.

public content

The present disclosure aims to solve one of the above-mentioned problems.

The main purpose of the present disclosure is to provide a cloud hosting method for a hardware payment device.

Another object of the present disclosure is to provide a cloud hosting system for hardware payment devices.

In order to achieve the above purpose, the technical solution of the present disclosure is specifically implemented as follows:

One aspect of the present disclosure provides a cloud hosting method for a hardware payment device, the method comprising: the cloud hosting server receives an account opening request, and the account opening request includes user identification information; the cloud hosting server allocates and activates a hardware payment device according to the identity information, Bind the user identity information with the hardware payment device, and save the binding relationship between the user identity information and the hardware payment device, wherein the hardware payment device is connected to the cloud hosting server or integrated in the cloud hosting server; the cloud hosting server receives the transaction Request, the transaction request includes: user identification information, transaction information and identity authentication information; the cloud hosting server performs authentication according to the user identification information and identity authentication information, and after the authentication is passed, according to the binding relationship between the user identification information and the hardware payment device , and send the transaction request to the hardware payment device corresponding to the user’s identity information; the hardware payment device judges the transaction type according to the transaction information, and if the transaction type is payment, then obtains the first data packet for payment, and uses the first data packet for payment The data packet is sent to the cloud hosting server; if the transaction type is payment, the second data packet used for payment is extracted from the transaction information, and the second data packet used for payment is stored; the cloud hosting server will receive the payment for payment The first data packet is sent out.

Optionally, the identity authentication information includes at least one of the following: finger vein information, fingerprint information or face information.

Another aspect of the present disclosure provides a cloud hosting system for a hardware payment device, the system includes: a cloud hosting server and at least one hardware payment device, the hardware payment device is connected to the cloud hosting server or integrated in the cloud hosting server; the cloud hosting server , for receiving an account opening request, the account opening request includes user identification information; allocate and activate a hardware payment device according to the user identification information, bind the user identification information with the hardware payment device, and save the user identification information and the hardware payment device Binding relationship; receive a transaction request, the transaction request includes: user identity information, transaction information and identity authentication information; authenticate according to the user identity information and identity authentication information, after the authentication is passed, according to the user identity information and hardware payment device binding relationship, and send the transaction request to the hardware payment device corresponding to the user identity information; the hardware payment device is used to judge the transaction type according to the transaction information, and if the transaction type is payment, obtain the first data packet for payment, Send the first data packet for payment to the cloud hosting server; if the transaction type is collection, extract the second data packet for payment from the transaction information, and store the second data packet for payment; the cloud hosting server , which is also used to send the received first data packet for payment.

It can be seen from the above technical solution provided by the present disclosure that the present disclosure provides a cloud hosting method and system for a hardware payment device. With this technical solution, by configuring one or more hardware payment devices connected to or integrated in the cloud hosting server, the user can be assigned to a cloud hardware payment device corresponding to the user's identity information after opening an account. The device, through the cloud hardware payment device, receives and pays or stores the data package used for payment to complete the transaction. The cloud hosting method or system using a hardware payment device does not require the user to go to the bank counter to get the hardware payment device when opening an account, and does not need to hold the hardware payment device in subsequent use, thereby simplifying user operations and optimizing user experience .

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following will briefly introduce the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present disclosure. For Those of ordinary skill in the art can also obtain other drawings based on these drawings without making creative efforts.

FIG. 1 is a flowchart of a cloud hosting method for a hardware payment device provided in Embodiment 1 of the present disclosure;

Fig. 2 is a schematic structural diagram of a cloud hosting system for a hardware payment device provided by Embodiment 2 of the present disclosure.

Detailed ways

The technical solutions in the embodiments of the present disclosure are clearly and completely described below in combination with the accompanying drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only some of the embodiments of the present disclosure, not all of them. Based on the embodiments of the present disclosure, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present disclosure.

Embodiments of the present disclosure will be further described in detail below in conjunction with the accompanying drawings.

Example 1

Fig. 1 is a flow chart of the cloud hosting method for the hardware payment device provided in this embodiment, the method includes steps S1-S7, now with reference to Fig. 1, the specific steps of the method are described:

In step S1, the cloud hosting server receives an account opening request, and the account opening request includes user identification information.

In this step, when the user opens an account, he can send an account opening request to the cloud hosting server through his own terminal device (such as a mobile phone, computer, etc.), or the user submits an account opening request to the bank server through the bank APP, and the bank server sends the cloud hosting server an account opening request. Send account opening request. In this embodiment, the account opening request includes at least user identification information, which is the unique identification information that marks the user. In practical applications, it can be the user's ID number, or the user's name and ID number. combinations etc. In addition, the account opening request may also include other information, such as account opening request time, account type, etc., which is not limited here.

Step S2, the cloud hosting server allocates and activates a hardware payment device according to the identity information, binds the user identity information to the hardware payment device, and saves the binding relationship between the user identity information and the hardware payment device.

In this embodiment, the hardware payment device has a built-in security chip, which has security functions such as encryption and decryption, signature verification, and safe storage. Each hardware payment device can be assigned to a user, and after binding with the user's identity information, The hardware payment device can only be used by the user. The hardware payment device can be an independent device connected to the cloud hosting server, or the hardware payment device can be integrated in the cloud hosting server. As an optional implementation, the cloud hosting server can establish a binding relationship mapping table according to the binding relationship between the user identity information and the hardware payment device, and the binding relationship mapping table can store the user identity information, the hardware payment device Serial number and the corresponding relationship between the two.

Step S3, the cloud hosting server receives the transaction request, and the transaction request includes: user identification information, transaction information and identity authentication information.

In this step, the transaction information may include one or more of the following: transaction amount, payee information or payer information, transaction time, transaction location, and the like. Optionally, the user can use his own terminal device (such as a mobile phone, computer, etc.) to start the bank APP carried in the terminal device, and the user enters transaction information and identity authentication information into the bank APP, and the bank APP Generate a transaction request with the entered identity authentication information, and send the transaction request to the cloud hosting server. Thus, the hardware payment device can perform a transaction operation according to the transaction information. As an optional implementation, the identity authentication information includes at least one of the following: finger vein information, fingerprint information, or face information. By performing identity authentication on the user who submits the transaction request through biometrics, the electronic Transaction security.

Step S4, the cloud hosting server performs authentication according to the user identity information and identity authentication information. After the authentication is passed, according to the binding relationship between the user identity information and the hardware payment device, the transaction request is sent to the hardware payment device corresponding to the user identity information .

In this implementation, after the cloud hosting server authenticates the user identity authentication information, it finds the hardware payment device belonging to the user according to the binding relationship between the user identification information and the hardware payment device, and sends the transaction request to the user's hardware payment device. The device is a hardware payment device with a built-in security chip that performs transaction operations, such as receiving or sending data packets for payment. As an optional implementation, the cloud hosting server can store a binding relationship mapping table, and look up the serial number of the hardware payment device corresponding to the received user identity information in the binding relationship mapping table, so that the And call the user's hardware payment device.

Step S5, the hardware payment device judges the transaction type according to the transaction information, if the transaction type is payment, then execute step S6, if the transaction type is payment, then execute step S7;

Step S6, obtaining the first data packet used for payment, and sending the first data packet used for payment to the cloud hosting server.

In this step, after the hardware payment device receives the transaction information indicating payment, it can obtain the first data package for payment corresponding to the denomination stored by itself from the built-in security chip according to the transaction amount in the transaction information, and use the The first data packet for payment is sent to the cloud hosting server. After the cloud hosting server receives the first data packet for payment, step S6-1 is executed, and the cloud hosting server sends the received first data packet for payment. Thus, the cloud hosting server can send the first data packet for payment to the payee device.

Step S7, extracting the second data packet used for payment from the transaction information, and storing the second data packet used for payment;

In this step, if the transaction type is payment, the transaction information carries the second data packet for payment sent by the payer, and the hardware payment device extracts the second data packet for payment and stores it in the built-in In the security chip, the payment collection operation is completed.

It can be seen from the method provided in this embodiment that by configuring one or more hardware payment devices connected to or integrated in the cloud hosting server, the user can be assigned a user identity payment device after opening an account. The cloud hardware payment device corresponding to the identification information, through which the cloud hardware payment device receives and pays or stores the data package used for payment, so as to complete the transaction. The cloud hosting method or system using a hardware payment device does not require the user to go to the bank counter to get the hardware payment device when opening an account, and does not need to hold the hardware payment device in subsequent use, thereby simplifying user operations and optimizing user experience .

Example 2

FIG. 2 is a schematic structural diagram of the cloud hosting method for the hardware payment device provided in this embodiment. Now in conjunction with FIG. 2, the structure of the system is described:

The cloud hosting system provided in this embodiment includes: a cloud hosting server 10 and at least one hardware payment device 20 , and the hardware payment device 20 is connected to the cloud hosting server 10 or integrated in the cloud hosting server 10 . In this embodiment, the hardware payment device 20 may be an independent device connected to the cloud hosting server 10, or the hardware payment device 20 may be integrated in the cloud hosting server 10. There may be multiple hardware payment devices. As shown in FIG. 2 , the hardware payment device 20 to the hardware payment device 2N are respectively connected to the cloud hosting server 10 or integrated in the cloud hosting server 10 .

The cloud hosting server 10 is configured to receive an account opening request, and the account opening request includes user identification information. When opening an account, the user can send an account opening request to the cloud hosting server 10 through his own terminal equipment (such as a mobile phone, a computer, etc.), or the user submits an account opening request to the bank server through the bank APP, and the bank server sends an account opening request to the cloud hosting server 10. ask. In this embodiment, the account opening request includes at least user identification information, which is the unique identification information that marks the user. In practical applications, it can be the user's ID number, or the user's name and ID number. combinations etc. In addition, the account opening request may also include other information, such as account opening request time, account type, etc., which is not limited here.

The cloud hosting server 10 is also used to allocate and activate a hardware payment device 20 according to the user identity information, bind the user identity information to the hardware payment device 20, and save the binding relationship between the user identity information and the hardware payment device 20 . The hardware payment device 20 has a built-in security chip, which has security functions such as encryption and decryption, signature verification, and safe storage. Each hardware payment device 20 can be assigned to a user, and after binding with the user's identity information, the hardware payment device The device 20 can only be used by this user. As an optional implementation, the cloud hosting server 10 may establish a binding relationship mapping table according to the binding relationship between the user identity information and the hardware payment device, and the binding relationship mapping table may store the user identity information, the hardware payment device serial number and the correspondence between the two.

The cloud hosting server 10 is also used to receive a transaction request, and the transaction request includes: user identification information, transaction information and identity authentication information. The transaction information may include one or more of the following: transaction amount, payee information or payer information, transaction time, transaction location, and the like. Optionally, the user can use his own terminal device (such as a mobile phone, computer, etc.) to start the bank APP carried in the terminal device, and the user enters transaction information and identity authentication information into the bank APP, and the bank APP Generate a transaction request with the entered identity authentication information, and send the transaction request to the cloud hosting server 10. Thus, the hardware payment device 20 can perform a transaction operation according to the transaction information. As an optional implementation, the identity authentication information includes at least one of the following: finger vein information, fingerprint information, or face information. By performing identity authentication on the user who submits the transaction request through biometrics, the electronic Transaction security.

The cloud hosting server 10 is also used to perform authentication according to the user identity information and identity authentication information. After the authentication is passed, according to the binding relationship between the user identity information and the hardware payment device, the transaction request is sent to the hardware corresponding to the user identity information. Payment device 20 . After the cloud hosting server 10 authenticates the user identity authentication information, it finds the hardware payment device 20 belonging to the user according to the binding relationship between the user identification information and the hardware payment device, and sends the transaction request to the user's hardware payment device 20 , the transaction operation is performed by the hardware payment device 20 with a built-in security chip, such as receiving or sending data packets for payment. As an optional implementation, the cloud hosting server 10 may store a binding relationship mapping table, and look up the serial number of the hardware payment device 20 corresponding to the received user identity information in the binding relationship mapping table, thereby The user's hardware payment device 20 can be looked up and invoked.

The hardware payment device 20 is used to judge the transaction type according to the transaction information, if the transaction type is payment, then obtain the first data packet for payment, and send the first data packet for payment to the cloud hosting server 10; if the transaction type For collection, then extract the second data packet used for payment from the transaction information, and store the second data packet used for payment; the cloud hosting server 10 is also used to send out the received first data packet used for payment . After the hardware payment device 20 receives the transaction information indicating payment, it can obtain the first data packet for payment corresponding to the face value stored by itself from the built-in security chip according to the transaction amount in the transaction information, and use the first data packet for payment The first data packet is sent to the cloud hosting server 10 . After receiving the first data packet for payment, the cloud hosting server 10 is configured to send the received first data packet for payment. Thus, the cloud hosting server 10 can send the first data packet for payment to the payee device. If the transaction type is collection, the transaction information carries the second data packet sent by the payer for payment, and the hardware payment device 20 extracts the second data packet for payment and stores it in the built-in security chip , thus completing the payment operation.

As can be seen from the system provided in this embodiment, the system configures one or more hardware payment devices connected to or integrated in the cloud hosting server 10, so that after the user opens an account, he can be assigned to a The cloud hardware payment device 20 corresponding to the user identity information receives and pays or stores the data package for payment through the cloud hardware payment device 20 to complete the transaction. The cloud hosting method or system using a hardware payment device does not require the user to go to the bank counter to get the hardware payment device when opening an account, and does not need to hold the hardware payment device in subsequent use, thereby simplifying user operations and optimizing user experience .

In the description of this specification, descriptions referring to the terms "one embodiment", "some embodiments", "example", "specific examples", or "some examples" mean that specific features described in connection with the embodiment or example , structure, material or characteristic is included in at least one embodiment or example of the present disclosure. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Although the embodiments of the present disclosure have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limitations on the present disclosure. Variations, modifications, substitutions, and modifications to the above-described embodiments are possible within the scope of the present disclosure. The scope of the present disclosure is defined by the appended claims and their equivalents.

Claims

A cloud hosting method for a hardware payment device, comprising:

The cloud hosting server receives an account opening request, and the account opening request includes user identification information;

The cloud hosting server allocates and activates a hardware payment device according to the identity information, binds the user identity information with the hardware payment device, and saves the user identity information and the hardware payment device A binding relationship, wherein the hardware payment device is connected to the cloud hosting server or integrated in the cloud hosting server;

The cloud hosting server receives a transaction request, and the transaction request includes: the user identification information, transaction information and identity authentication information;

The cloud hosting server performs authentication according to the user identity information and the identity authentication information. After passing the authentication, according to the binding relationship between the user identity information and the hardware payment device, the transaction request is sent to The hardware payment device corresponding to the user identity information;

The hardware payment device judges the transaction type according to the transaction information, if the transaction type is payment, then obtains the first data packet used for payment, and sends the first data packet used for payment to the cloud hosting server; if the transaction type is payment, extracting a second data packet for payment from the transaction information, and storing the second data packet for payment;

The cloud hosting server sends out the received first data packet for payment.
The method according to claim 1, wherein the identity authentication information includes at least one of the following: finger vein information, fingerprint information or face information.
A cloud hosting system for a hardware payment device, comprising: a cloud hosting server and at least one hardware payment device, the hardware payment device being connected to the cloud hosting server or integrated in the cloud hosting server;

The cloud hosting server is configured to receive an account opening request, and the account opening request includes user identity information; allocate and activate one of the hardware payment devices according to the user identity information, and combine the user identity information with the hardware Bind the payment device, and store the binding relationship between the user identity information and the hardware payment device; receive a transaction request, the transaction request includes: the user identity information, transaction information and identity authentication information; according to the The user identity information and the identity authentication information are authenticated. After the authentication is passed, according to the binding relationship between the user identity information and the hardware payment device, the transaction request is sent to the user identity information corresponding the said hardware payment device;

The hardware payment device is configured to judge the transaction type according to the transaction information, and if the transaction type is payment, obtain a first data packet for payment, and send the first data packet for payment to the The cloud hosting server; if the transaction type is payment, then extract the second data package for payment from the transaction information, and store the second data package for payment;

The cloud hosting server is further configured to send the received first data packet for payment to outside.
The method according to claim 3, wherein the identity authentication information includes at least one of the following: finger vein information, fingerprint information or face information.