TW201832151A - Mobile payment method, inquiry method for mobile payment and device biding method for mobile payment - Google Patents

Abstract

A mobile payment method, an inquiry method for mobile payment and a device biding method for mobile payment are provided. The device biding method includes a cloud server generating a registration code for authentication according to a personal data, a client device receives an input code and transmitting the input code and a hardware information of the client device to the cloud server, the cloud server determining whether the input code being equal to the registration code, the cloud server generating a biding data according to the hardware information and the personal data when the input code being equal to the registration code, and the client device receiving the biding data from the cloud server.

Description

Mobile payment method, mobile payment inquiry method and device binding method for mobile payment

The present invention relates to an action payment method, a mobile payment inquiry method, and a device binding method for mobile payment.

In the traditional payment method, the consumer often needs to use the physical card to pay after the online consumer, for example, using a credit card or a financial card to pay, which is quite inconvenient to use; and, in the process of payment, the payment institution often The consumer authenticates, for example, using a natural person's voucher to confirm the identity, and the consumer needs to insert the natural person voucher card into the card reader to complete the payment. Therefore, it is quite inconvenient for consumers to use multiple physical cards in the process of making payments.

In addition, consumers can also make payments through a third-party payment platform. Third-party payment platforms do not require physical cards, but consumers need to open a separate set of accounts and passwords on third-party payment platforms. When a variety of different payment platforms are used, consumers need to open multiple sets of accounts and passwords, and remember the accounts and passwords that are applicable to different payment platforms, causing a burden on the use, or even unwilling to use them, which is quite inconvenient.

In view of this, the present invention provides a mobile payment method, a mobile payment query method, and a device binding method for mobile payment.

In an embodiment, a mobile payment device binding method includes: the cloud server generates an authentication registration code according to the personal data, and the client device receives the input registration code and sends the input registration code and one of the client device hardware information to the The cloud server determines whether the input registration code is the same as the authentication registration code. When the input registration code is the same as the authentication registration code, the cloud server generates the preset binding data according to the hardware information and the personal data, and the client device automatically The cloud server receives the preset binding data.

In an embodiment, the step of the client device transmitting the registration code and the hardware information to the cloud server includes: the client device determining whether the device binding data corresponding to the hardware information is included; and when the client device When the device binding data is not included, the client device sends the hardware information to the cloud server.

In an embodiment, a device binding method for mobile payment includes: the client device determines whether it includes a device binding data, and the device binding data corresponds to one piece of hardware information of the client device; when the client device does not include When the device binds the data, the client device sends the hardware information to a cloud server; the cloud server determines whether it contains one authentication code corresponding to the hardware information and a preset binding data; and when the cloud server When the authentication registration code corresponding to the hardware information and the preset binding data are included, the client device receives the preset binding data from the cloud server.

In an embodiment, the foregoing device binding method further includes: when the client device includes the device binding data, the client device sends the device binding data to the cloud server; the cloud server determines the device binding data and a pre- Whether the binding data is the same; and when the device binding data is different from the preset binding data, the client device deletes the device binding data.

In an embodiment, the foregoing device binding method further includes: when the cloud server includes the authentication registration code and does not include the preset binding data, the client device receives an input registration code and sends the input registration code to the cloud server. Device.

In an embodiment, a mobile payment method includes: a store device or a client device sends a billing information to a cloud server; the client device sends a device binding data to a cloud server, and the device binds The data corresponds to an account information; when the device binding data is the same as the preset binding data of one of the cloud servers, the cloud server sends the billing information to the client device; the client device sends a payment confirmation according to the billing information. The signal is sent to the cloud server; the cloud server performs an authentication procedure according to the payment confirmation signal; and when the client device passes the authentication program, the payment is made by the account information.

In an embodiment, the step of the client device transmitting the device binding data comprises: the client device receiving an input password; the client device determining whether the input password is the same as a pre-stored password; and when the input password is the same as the pre-stored password, The client device sends the device binding data to the cloud server.

In an embodiment, the step of the client device transmitting the device binding data further includes: when the client device determines that the input password is different from the pre-stored password by a predetermined number of times, the client device deletes the device binding data. .

In an embodiment, the foregoing action payment method further includes: when the device binding data is different from the preset binding data of one of the cloud servers, the client device deletes the device binding data.

In an embodiment, the step of the cloud server sending the billing information to the client device comprises: the cloud server sending the billing information to a billing management server; the billing management server according to the billing information The store identification code determines whether the billing information is valid; and when the billing information is valid, the cloud server sends the billing information to the client device.

In an embodiment, before the cloud server sends the billing information to the client device, the foregoing action payment method further includes: the store device generates a payment information code according to the billing information; and the client device reads the payment information code to Sending a payment request signal to the cloud server; wherein the cloud server sends the billing information to the client device according to the payment request signal.

In an embodiment, before the cloud server sends the billing information to the client device, the foregoing action payment method further includes: the store device generates a payment information code according to the billing information; and the client device reads the payment information code to Sending a payment request signal to the cloud server; the cloud server sends the billing information to a bill management server; the bill management server determines whether the bill information is valid according to one of the billing information store identifiers; When the billing information is valid, the cloud server sends the billing information to the client device according to the payment request signal.

In an embodiment, the billing information includes a payment amount. In the step of the cloud server performing the authentication procedure, the cloud server selectively executes the authentication procedures of different security levels according to the payment amount.

In an embodiment, the step of the client device transmitting the device binding data includes: when the client device executes an application, determining whether it includes device binding data; when the device binding data is not included, the client device The cloud server receives the preset binding data as the device binding data; and when the device binding data is included, the client device sends the device binding data to the cloud server.

In an embodiment, the cloud server belongs to a management bank, and the account information includes the account information of the management bank and the account information of the cooperative bank connected to the management bank, and the step of sending the payment confirmation signal to the client device. The client device sends a payment confirmation signal of the designated management bank or the cooperative bank to the cloud server.

In an embodiment, a mobile payment query method includes: the client device sends a device binding data to a cloud server, and the device binding data corresponds to an account information; when the device binding data and the cloud server are pre- When the binding data is the same, the client device sends a historical billing query request including a billing payment information code to the cloud server; the cloud server determines whether the billing payment information code is used by a bill management server. Valid; when the payment information code of the bill is valid, the cloud server sends one of the payment information codes of the corresponding bill to the client device.

In summary, according to one embodiment of the action payment method, the action payment inquiry method, and the device binding method of the action payment, the user can make payment by using the existing account information by the mobile device, and the user no longer needs The physical card is used for payment, and the user does not need to additionally create and memorize other accounts and passwords for payment. The user only needs to memorize a set of passwords for launching the application, and the application can be used for payment. Moreover, an embodiment of the action payment method, the action payment inquiry method, and the device binding method of the action payment in the present case can verify the uniqueness of the payer by using a device binding data including the hardware information of the client device, Confirm the identity of the payer, which in turn increases transaction security.

Please refer to FIG. 1, which is a schematic diagram of an embodiment of an action payment system to which the mobile payment method of the present invention is applied. The mobile payment system includes a cloud server 11 and a client device 12 connected to the cloud server 11. Here, FIG. 1 is an example in which the client device 12 is a mobile phone.

The cloud server 11 is a financial service that is set up by a management bank and can provide mobile payment. Before using the financial service for mobile payment, the user needs to connect to the cloud server 11 through the client device 12 or other electronic devices, and input one or more account information to be paid in the cloud server 11 (for example, Personal information, credit card information, the Bank's and/or other bank's deposit account number, and personal data may include an identity card number, birthday, mobile phone number, or any combination of the foregoing. Then, the user can install an application 121 supporting the mobile payment function in the client device 12, and bind a device binding data to the client device 12. The device binding data corresponds to the pre-registered personal data. And account information. Thereafter, when the user consumes the online merchant or the entity merchant, the application 121 can be executed and the mobile payment function can be used to perform payment by using the account information registered in advance.

Please refer to FIG. 1 and FIG. 2 together. FIG. 2 is a flow chart of an embodiment of a device binding method for mobile payment according to the present invention. After the user logs the personal data and account information to the cloud server 11, the cloud server 11 generates an authentication registration code based on the personal data (step S01). Next, the user activates the application 121 of the client device 12 and enters the authentication registration code. The client device 12 receives the input registration code S1 input by the user (step S02), and transmits the input registration code S1 and the hardware information S2 of the client device 12 to the cloud server 11 (step S03). After receiving the registration code S1, the cloud server 11 determines whether the input registration code S1 is the same as the authentication registration code (step S04). When the registration code S1 is the same as the authentication registration code (the determination result is “Yes”), the user input is indicated. The cloud server 11 generates the preset binding data S3 according to the hardware information S2 sent by the client device 12 and the pre-registered personal data (step S05), and the cloud server 11 can provide hardware information. The S2 and the personal data perform the hash function operation and the encryption operation to generate the preset binding data S3, and the client device 12 receives the preset binding data S3 from the cloud server 11 (step S06) to complete the device binding.

In an implementation, before the step S02, the cloud server 11 can perform an authentication procedure. In detail, the cloud server 11 can request the user to input the registered personal data (such as the aforementioned identity card number, mobile phone, etc.) into the client device 12 after the user logs in the personal data 11 on the cloud server 11; Then, the client device 12 sends the personal data input by the user to the cloud server 11, and the cloud server 11 determines whether the personal data input by the user is the same as the personal data registered in advance, and when the two are the same, the cloud server 11 Then the authentication procedure, such as Active One-Time Password (AOTP) authentication, One-Time Password (OTP) authentication, push authentication or biometric authentication procedure. After the client device 12 passes the authentication process, the user can input the registration code into the client device 12 to continue the subsequent steps to generate the preset binding data S3.

In step S01, the authentication registration code generated by the cloud server 11 is time-sensitive, for example, one day, six hours or one hour, and the user must input the authentication registration code into the client device 12 within a preset time. Therefore, the client device 12 receives the input registration code S1 and sends the input registration code S1 and the hardware information S2 to the cloud server 11 within a preset time after the authentication registration code is generated.

Furthermore, after the cloud server 11 executes step S04, if the result of the determination is "NO", it means that the input registration code S1 input by the user is not the same as the authentication registration code, and the cloud server 11 can cancel the authentication registration code ( Step S11); or, when the input registration code S1 is different from the authentication registration code, the cloud server 11 may also count the number of times the input registration code S1 is incorrect, and the number of times the input registration code S1 is incorrect exceeds a preset number of times (for example, two The cloud server 11 then revokes the authentication registration code (step S11). After the authentication registration code is revoked, the cloud server 11 may further prompt the user to reconnect to the cloud server 11 to regenerate another authentication registration code.

Please refer to FIG. 1 to FIG. 3 together. FIG. 3 is a flowchart of another embodiment of a device binding method for mobile payment according to the present invention. Each time the application 121 is executed, the client device 12 determines whether the aforementioned device binding procedure is completed. As shown in FIG. 3, the client device 12 first determines whether it contains device binding data (step S07). When the device binding data exists (the determination result is "Yes"), the client device 12 binds the device data. It is sent to the cloud server 11 (step S12) for verification. In step S12, the cloud server 11 compares the device binding data sent by the client device 12 with the pre-stored preset binding data S3. When the two are the same, it indicates that the client device 12 has completed binding, and the client device 12 includes valid device binding data. At this time, the application 121 supports the mobile payment function. When the two are different, the client device 12 includes invalid device binding data, and the application 121 does not support the mobile payment. Function, the client device 12 can delete the invalid device binding data.

However, when the client device 12 does not include the device binding data (the determination result in step S07 is "NO"), the client device 12 transmits the hardware information S2 to the cloud server 11 (step S08), and the cloud server 11 It is judged whether or not it contains the authentication registration code corresponding to the hardware information S2 and the preset binding data S3 (step S09). When the cloud server 11 includes the corresponding authentication registration code and does not include the corresponding preset binding data S3 (the determination result is "No"), it indicates that the user has entered the personal data into the cloud server 11 but does not verify the authentication code. The client device 12 is input. At this time, the application 121 prompts the user to input the registration code, and the device binding program will be executed starting from step S02 in FIG.

Furthermore, in the case where the client device 12 does not include the device binding data, when the cloud server 11 does not include the authentication registration code corresponding to the hardware information S2 and the preset binding data S3 (after performing step S09) If the result of the determination is "NO", it means that the user has not entered his personal data into the cloud server 11, and the application program 121 prompts the user to open the mobile payment service to the web page of the management bank (step S10).

Further, in the case where the client device 12 does not include the device binding data, when the cloud server 11 includes the authentication registration code corresponding to the hardware information S2 and the preset binding data S3 (the determination result after performing step S09) If it is "Yes", it means that the user has entered his personal data into the cloud server 11, and the registration code entered by the user is correct. At this time, the cloud server 11 executes the step S11 in FIG. 2 to send the preset binding data S3. To the client device 12. In an implementation, in step S06, the cloud server 11 can perform an authentication procedure, such as an active one-time password authentication, a one-time password authentication, a push authentication, or a biometric authentication program, and is in the client. After the device 12 passes the authentication process, the preset binding data S3 is sent to the client device 12.

The following is a description of how the user performs payment by the application 121 with the account information registered in advance when the merchant consumes. Please refer to FIG. 2 to FIG. 4 together. FIG. 4 is a schematic diagram of another embodiment of an action payment system to which the mobile payment method of the present invention is applied. The mobile payment system further includes a store-side device 13, which may be a server, a personal computer, or a Point of Sales (POS) device. When the user consumes at the entity merchant or the online merchant, the store-side device 13 transmits the billing information S4 to the cloud server 11. To make a payment, the user launches the application 121. At this time, the client device 12 performs step S07 in FIG. 3 to determine whether the device binding information is included in the client device 12. When the client device 12 includes device binding data, the client device 12 retransmits the device binding data to the cloud server 11 (step S12) to verify whether the device binding data is valid. When the cloud server 11 determines that the client device 12 includes valid device binding data, as shown in FIG. 4, the client device 12 receives the billing information S4 sent by the cloud server 11, and the user can use the application 121. The billing information S4 is known, and the payment confirmation signal S5 is sent to the cloud server 11 by the client device 12. Then, in order to further improve the security of the action payment, the cloud server 11 performs an authentication procedure according to the payment confirmation signal S5, which may be the aforementioned AOTP authentication, OTP authentication, push authentication, biometric identification, security token ( Security Token), software card emulation (HCE), other credentials, etc., but not limited to this. When the client device 12 passes the authentication process, the payment is made by using the account information previously registered in the cloud server 11. In other embodiments, the user can also send the billing information S4 to the cloud server 11 through the client device 12, and the cloud server 11 executes an authentication program according to the billing information S4 and the payment confirmation signal S5.

In an implementation aspect, different ones of the foregoing authentication procedures have different security levels, and the cloud server 11 can perform different security level authentication procedures according to the payment amount included in the billing information S4; for example, when the payment amount is When the denomination is small, if less than a predetermined amount, the cloud server 11 can perform a one-time dynamic password (OTP) with a lower security level, such as SMS authentication or push authentication, to increase the convenience of use; When the denomination is large, if the amount is greater than or equal to the foregoing preset amount, the cloud server 11 may perform an AOTP authentication or biometric authentication procedure with a higher security level to improve the security of the action payment.

To further enhance the security of the mobile payment, the client device 12 may require the user to set a password (character password or gesture password) in the application, and then the client device 12 stores the aforementioned password and has a pre-stored password. Therefore, when the application 121 is started, the application 121 displays a password input field for the user to input a password. After the client device 12 receives the input password input by the user, the client device 12 determines whether the input password and the pre-stored password are Similarly, when the input password is the same as the pre-stored password, the user can use the application 121; when the input password is different from the pre-stored password, the client device 12 counts the number of times the input password is different from the pre-stored password, and the number of times is greater than the aforementioned number. The client device 12 device binding data is deleted after a preset number of times (for example, twice or more than twice).

FIG. 5 and FIG. 6 are respectively schematic diagrams showing an implementation of the mobile payment system of FIG. 4. In these embodiments, after the cloud server 11 receives the billing information S4 sent by the store device 13, the cloud server 11 may further verify whether the billing information S4 is valid to selectively transmit the billing information S4 to the client device 12 based on the validity of the billing information S4. In detail, as shown in FIG. 5, the mobile payment system further includes a bill management server 14 connected to the cloud server 11, the bill management server 14 stores the store identification code, and the store side device 13 transmits the account. The single information S4 includes an encoding. When the cloud server 11 receives the billing information S4, the cloud server 11 sends the billing information S4 to the billing management server 14, and the billing management server 14 compares the store identification code with the account. The encoding of the single information S4 generates a comparison signal S6 to indicate whether the two are the same; when the store identification code is the same as the encoding of the billing information S4, it indicates that the billing information S4 is valid, and the cloud server 11 will be valid at this time. The billing information S4 is sent to the client device 12, and the client device 12 sends the payment confirmation signal S5 to the cloud server 11 according to the valid billing information S4; however, when the store identification code is different from the billing information S4. , indicating that the billing information S4 is invalid, that is, the merchant that the user consumes may not be legal. At this time, the cloud server 11 may send the billing information S4 to the client device 12 to issue a prompt message to the client device 12. To improve the security of mobile payments, can also improve the accuracy of payments, reduce errors subject of payment situation.

Further, after the user consumes the merchant, as shown in FIG. 6, the store side device 13 sends a bill payment information code according to the bill information S4, in addition to the bill information S4 being sent to the cloud server 11. S8, the barcode payment information code S8 may be a one-dimensional barcode, a two-dimensional barcode (for example, a Quick Response (QR) code) or a string of characters, and the string of characters may be a number, a letter, a symbol, or a combination thereof. The user can read the barcode payment information code S8 (scan one-dimensional barcode or two-dimensional barcode or manually input the character string into the client device 12) by using the application 121 of the client device 12, and generate a bill corresponding to the bill. The information S4 is one of the payment request signals S7, and the client device 12 provides the read value of the payment request signal S7 and the payment information code S8 to the cloud server 11, and the cloud server 11 verifies that the read value of the payment information code S8 is valid. And sending the valid billing information S4 to the client device 12 according to the payment request signal S7. The client device 12 receives the valid billing information S4 from the cloud server 11, and the application 121 of the client device 12 displays S4 billing information for client identification. In an implementation, the client device 12 can read the payment information code S8 by scanning the one-dimensional barcode or the two-dimensional barcode; or the user can manually input the character string into the client device 12 to make the client The application 121 of the device 12 reads the payment information code S8, that is, the user can read the payment information code S8 by one of the application devices 121 by scanning or inputting. Moreover, since the user can log in one or more account information in the cloud server 11, when the user logs in multiple account information, the cloud server 11 receives the read value of the payment request signal S7 and the payment information code S8. A payment selection signal S9 can be further sent to the client device 12 to cause the application 121 to display each account information or to display only an alias for each account information for the user to select. After the user selects one of the account information, the client device 12 generates a payment confirmation signal S5 that specifies an account information, and the client device 12 sends a confirmation signal S5 to the cloud server 11 for deduction.

In an implementation aspect, the foregoing account information may be credit card information, a deposit account of a management bank, or a deposit account of another cooperative bank connected to the management bank. Taking the credit card information as an example, the account information may include the credit card number, the effective date of the credit card, and the last three codes. When the user chooses to pay by credit card, the cloud server 11 may connect to the issuing bank after receiving the payment confirmation signal S5. And follow-up authorization and deduction procedures with the issuing bank; when the user chooses to pay with the deposit account of the cooperative bank, the cloud server 11 can be connected to the electronic direct authorization system (eDDA). The cloud server belonging to the cooperative bank triggers the identity authentication and subsequent deduction procedures of the user by the cloud server 11 by triggering the cloud server of the cooperative bank. Based on this, after the account information selected by the user is successfully debited, the cloud server 11 sends a signal indicating that the deduction is successful to the store device 13.

In an embodiment, the user can query the historical bill payment record by the application 121. In detail, after the cloud server 11 verifies that the device binding data of the client device 12 is valid, the user can use the historical billing query function of the application 121. The user inputs a bill payment information code into the application 121, and sends a historical bill inquiry request including the bill payment information code to the cloud server 11 by the client device 12. Next, the cloud server 11 is connected to the bill management server 14 based on the historical bill inquiry request to determine whether the bill payment information code exists by the bill management server 14. When the bill payment information code exists and is valid, the bill management server 14 sends the payment result corresponding to the bill payment information code, such as billing details, payment account number, payment method, etc., to the cloud server 11, the cloud server. The payment result is then forwarded to the client device 12 for display on the application 121 for viewing by the user.

In summary, according to one embodiment of the action payment method, the action payment inquiry method, and the device binding method of the action payment, the user can make payment by using the existing account information by the mobile device, and the user no longer needs The physical card is used for payment, and the user does not need to additionally create and memorize other accounts and passwords for payment. The user only needs to memorize a set of passwords for launching the application, and the application can be used for payment. And the action payment method, the action payment inquiry method and the device binding method of the action payment in the case, when the payment is made, the cloud server verifies whether the device binding data sent by the user matches to confirm the uniqueness of the payer, such as the device binding data. Inconsistent, that is, when the paymenter's identity fails to be confirmed, the service is terminated and the relevant information in the mobile device is deleted, thereby improving transaction security.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention. Any person having ordinary knowledge in the technical field can make some changes and refinements without departing from the spirit and scope of the present case. This is subject to the definition of the scope of the patent application.

11‧‧‧Cloud Server

12‧‧‧Client device

121‧‧‧Application

13‧‧‧Store-side device

14‧‧‧Billing Management Server

S1‧‧‧Enter the registration code

S2‧‧‧ hardware information

S3‧‧‧Preset binding data

S4‧‧‧ Billing Information

S5‧‧‧ payment confirmation signal

S6‧‧‧ comparison signal

S7‧‧‧ payment request signal

S8‧‧‧ payment information code

S9‧‧‧ payment selection signal

S01-S12‧‧‧Steps

[Fig. 1] A schematic diagram of an embodiment of an action payment system to which the mobile payment method of the present invention is applied. [Fig. 2] A flow chart of an embodiment of a device binding method for mobile payment according to the present invention. [Fig. 3] A flow chart showing another embodiment of a device binding method for action payment according to the present invention. [Fig. 4] A schematic diagram of another embodiment of an action payment system to which the mobile payment method of the present invention is applied. [Fig. 5] is a schematic diagram showing one embodiment of the action payment system of Fig. 4. FIG. 6 is another schematic diagram of an embodiment of the mobile payment system of FIG. 4. FIG.

Claims (16)

A device binding method for mobile payment, comprising: a cloud server generates an authentication registration code according to a person data; a client device receives an input registration code and sends the input registration code and one of the client device hardware information To the cloud server; the cloud server determines whether the input registration code is the same as the authentication registration code; when the input registration code is the same as the authentication registration code, the cloud server generates the hardware information according to the hardware information and the personal data a preset binding data; and the client device receives the preset binding data from the cloud server. The device binding method of the action payment according to claim 1, wherein the step of the client device transmitting the input registration code and the hardware information to the cloud server comprises: determining, by the client device, whether One of the hardware information device binding data; and when the client device does not include the device binding data, the client device sends the hardware information to the cloud server. A device binding method for mobile payment, comprising: a client device determining whether it includes a device binding data, the device binding data corresponding to one of the client device hardware information; when the client device does not include the When the device binds the data, the client device sends the hardware information to a cloud server; the cloud server determines whether it includes an authentication registration code corresponding to the hardware information and a preset binding data; When the cloud server includes the authentication registration code and the preset binding data, the client device receives the preset binding data from the cloud server. The device binding method of claim 3, further comprising: when the client device includes the device binding data, the client device sends the device binding data to the cloud server; the cloud server determines the Whether the device binding data is the same as a preset binding data; and when the device binding data is different from the preset binding data, the client device deletes the device binding data. The device binding method of claim 3, further comprising: when the cloud server includes the authentication registration code and does not include the preset binding data, the client device receives an input registration code and registers the input. The code is sent to the cloud server. An action payment method includes: a store device or a client device sends a billing information to a cloud server; the client device sends a device binding data to the cloud server, where the device binding data corresponds to An account information; when the device binding data is the same as the preset binding data of the cloud server, the cloud server sends the billing information to the client device; the client device according to the billing information Sending a payment confirmation signal to the cloud server; the cloud server performs an authentication procedure according to the payment confirmation signal; and when the client device passes the authentication program, performs payment by using the account information. The mobile payment method of claim 6, wherein the step of the client device transmitting the device binding data comprises: the client device receiving an input password; the client device determining whether the input password is the same as a pre-stored password; And when the input password is the same as the pre-stored password, the client device sends the device binding data to the cloud server. The mobile payment method of claim 7, wherein the step of the client device transmitting the device binding data further comprises: when the client device determines that the input password is different from the pre-stored password by a predetermined number of times The client device deletes the device binding data. The action payment method of claim 6, further comprising: when the device binding data is different from the preset binding data of the cloud server, the client device deletes the device binding data. The action payment method of claim 6, wherein the step of sending, by the cloud server, the billing information to the client device comprises: sending, by the cloud server, the billing information to a bill management server; The bill management server determines whether the billing information is valid according to the store identification code of the billing information; and when the billing information is valid, the cloud server sends the billing information to the client device. The mobile payment method of claim 6, wherein the mobile payment method further comprises: the store-side device generating a payment according to the billing information, before the step of transmitting the billing information to the client device by the cloud server The information code; and the client device reads the payment information code to send a payment request signal to the cloud server; wherein the cloud server sends the billing information to the client device according to the payment request signal. The action payment method of claim 6, before the step of the cloud server sending the bill information to the client device, the action payment method further comprises: the store device generating a payment information according to the bill information The client device reads the payment information code to send a payment request signal to the cloud server; the cloud server sends the billing information to a bill management server; and the bill management server is based on The store identification code of the billing information determines whether the billing information is valid; wherein, when the billing information is valid, the cloud server sends the billing information to the client device according to the payment request signal. The action payment method of claim 6, wherein the billing information includes a payment amount, and in the step of the cloud server executing the authentication procedure, the cloud server selectively performs different according to the payment amount. Certification process. The mobile payment method of claim 6, wherein the step of the client device transmitting the device binding data comprises: determining, by the client device, whether the device binding data is included when executing an application; When the device binds the data, the client device receives the preset binding data from the cloud server as the device binding data; and when the device binding data is included, the client device sends the device binding data. To the cloud server. The action payment method of claim 6, wherein the cloud server belongs to a management bank, and the account information includes account information of the management bank and account information of a cooperative bank connected to the management bank by the interbank. In the step of transmitting, by the client device, the payment confirmation signal, the client device sends the payment confirmation signal specifying the management bank or the cooperative bank to the cloud server. An action payment query method includes: a client device sends a device binding data to a cloud server, and the device binding data corresponds to an account information; when the device binding data is preset with one of the cloud servers When the binding data is the same, the client device sends a historical billing query request to the cloud server, and the historical billing query request includes a bill payment information code; the cloud server is judged by a bill management server Whether the bill payment information code is valid; and when the bill payment information code is valid, the cloud server sends a payment result corresponding to one of the bill payment information codes to the client device.