CN106157027B

CN106157027B - Payment method, device and system

Info

Publication number: CN106157027B
Application number: CN201610602598.0A
Authority: CN
Inventors: 高毅; 王洪强; 席春艳
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2016-07-27
Filing date: 2016-07-27
Publication date: 2020-01-10
Anticipated expiration: 2036-07-27
Also published as: CN106157027A

Abstract

The disclosure relates to a payment method, a device and a system, wherein the payment method comprises the following steps: when a triggering event for payment through a bank identifier bound by a first APP is received, sending a first payment request to a first server corresponding to the first APP, wherein the first payment request carries application identifier information of a second APP; when a first response message returned by the second server according to a second payment request is received, controlling a second APP to generate a payment confirmation prompt message, wherein the second payment request is generated by the first server according to the first payment request and is sent to the second server through the first server, and the second payment request carries a serial code of the first APP for payment by using a bank identifier; when feedback information confirming payment is received, an operation of payment transaction is performed. In the technical scheme, payment confirmation needs to be carried out in the bank client when the bank identifier bound by the first APP is used for payment, so that the payment transaction is safer.

Description

Payment method, device and system

Technical Field

The present disclosure relates to the field of mobile payment technologies, and in particular, to a payment method, device, and system.

Background

Mobile payment, also known as mobile payment, is a service that allows a user to make an account payment for goods or services consumed using his mobile terminal, e.g. a mobile phone. Mobile payment is becoming a necessary payment mode in people's life. The payment through a third-party payment platform, such as WeChat, Paibao and the like, is a mobile payment mode, the third-party payment platform is used as an intermediate merchant of payment settlement service of both parties for transaction, a payment service channel needs to be provided, and the function of transaction and fund transfer settlement arrangement is realized through the third-party payment platform.

In the related art, when a user pays through a third-party payment platform, the third-party payment platform needs to provide own information such as an identity card and a bank identifier, so that the condition that the information such as the identity card and the bank identifier of the user is leaked can occur, the safety of a bank account of the user is reduced, and unnecessary loss is caused to the property of the user.

Disclosure of Invention

To overcome the problems in the related art, the present disclosure provides a payment method, apparatus and system to solve the technical defects in the related art.

According to a first aspect of the embodiments of the present disclosure, there is provided a payment method applied to an electronic payment device, which may include:

when a trigger event for payment through a bank identifier bound by a first APP (Application) is received, sending a first payment request to a first server corresponding to the first APP, wherein the first payment request carries Application identifier information of a second APP corresponding to the bank identifier bound by the first APP;

when a first response message returned by a second server corresponding to a second APP according to a second payment request is received, controlling the second APP to generate a payment confirmation prompt message, wherein the second payment request is generated by the first server according to the first payment request and is sent to the second server through the first server, and the second payment request carries a serial code for payment by using the bank identifier in the first APP;

and when receiving the feedback information for confirming the payment input according to the payment confirmation prompt message, executing the operation of the payment transaction.

In an embodiment, the performing a payment transaction when receiving feedback information confirming payment input according to the payment confirmation prompting message may include:

when feedback information for confirming payment input according to the payment confirmation prompt message is received, sending a payment confirmation message to the second server, so that the second server can forward the payment confirmation message to the first server;

receiving a second response message returned by the first server according to the payment confirmation message;

and executing the operation of payment transaction according to the second response message.

In an embodiment, the method may further comprise:

receiving a binding request for binding the bank identifier, which is triggered through an operation interface of the first APP, wherein the binding request carries application identifier information of a second APP corresponding to the bank identifier;

and executing the operation of binding the first APP and the bank identifier according to the binding request.

In an embodiment, the performing of the operation of binding the first APP with the bank identifier may include:

sending a login request to the second server, wherein the login request carries the identification information of the first APP, the bank account corresponding to the bank identification and a login password;

when a third response message returned by the second server according to the login request is received, a payment information setting interface is displayed, and a serial code of the first APP for payment by using the bank identifier is analyzed from the third response message;

when payment information input in the payment information setting interface is received, sending a binding completion request to the first server to complete the operation of binding the first APP with the bank identifier, wherein the binding completion request carries a payment password for payment by using the bound bank identifier in the first APP, the serial code and application identifier information of the second APP.

According to a second aspect of the embodiments of the present disclosure, there is provided a payment method, applied on a first server, which may include:

receiving a first payment request sent by the electronic payment device, wherein the first payment request carries application identification information and payment amount of a second APP corresponding to a bank identification bound with the first APP;

generating a second payment request according to the first payment request, wherein the second payment request carries a serial code for payment by using the bank identifier in the first APP and the payment amount;

and sending the second payment request to a second server corresponding to the second APP so that the second server can execute the money transfer operation of payment transaction according to the second payment request.

In an embodiment, the method may further comprise:

receiving a binding completion request;

analyzing a payment password, the serial code and application identification information of the second APP for payment by using the bound bank identification in the first APP from the binding completion request;

and storing the payment password for payment by using the bound bank identifier in the first APP, the serial code and the application identifier information of the second APP.

According to a third aspect of the embodiments of the present disclosure, there is provided a payment method, applied on a second server, which may include:

receiving a second payment request sent by a first server, wherein the second payment request carries a serial number and a payment amount of payment carried out by the first APP by using the bank identifier;

sending a first response message to the electronic payment device through a second APP corresponding to the second server, so that the electronic payment device controls the second APP to generate a payment confirmation prompt message according to the first response message;

and when receiving a payment confirmation message sent by the electronic payment device according to the first response message, sending the payment confirmation message to the first server.

In an embodiment, the method may comprise:

receiving the login request sent by the electronic payment device, wherein the login request carries the application identification information of the first APP, the bank account and the login password corresponding to the bank identification bound with the first APP;

when the bank account and the login password corresponding to the bank identifier bound with the first APP are determined to be correct, generating a serial code for payment in the first APP by using the bank identifier;

and sending a third response message to the electronic payment equipment, wherein the third response message carries a serial code of the first APP for payment by using the bank identifier.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a payment apparatus applied to an electronic payment device, the apparatus may include:

the payment processing method comprises a first sending module, a second sending module and a payment processing module, wherein the first sending module is configured to send a first payment request to a first server corresponding to a first APP when a trigger event of payment through a bank identifier bound by the first APP is received, and the first payment request carries application identifier information of a second APP corresponding to the bank identifier bound by the first APP;

the first generating module is configured to control a second APP to generate a payment confirmation prompt message when receiving a first response message returned by a second server corresponding to the second APP according to a second payment request, where the second payment request is generated by the first server according to the first payment request sent by the first sending module and sent to the second server through the first server, and the second payment request carries a serial code of the first APP for payment by using the bank identifier;

a payment transaction module configured to perform an operation of a payment transaction when receiving feedback information for confirming payment input according to the payment confirmation prompt message generated by the first generation module.

In an embodiment, the payment transaction module may include:

a first sending submodule configured to send a payment confirmation message to the second server when receiving feedback information of payment confirmation input according to the payment confirmation prompt message generated by the first generating module, so that the second server forwards the payment confirmation message to the first server;

a first receiving submodule configured to receive a second response message returned by the first server according to the payment confirmation message sent by the first sending submodule;

an execution submodule configured to execute an operation of a payment transaction according to the second response message received by the first receiving submodule.

In one embodiment, the apparatus further comprises:

the first receiving module is configured to receive a binding request for binding the bank identifier, which is triggered through an operation interface of the first APP, where the binding request carries application identifier information of a second APP corresponding to the bank identifier;

the binding module is configured to execute the operation of binding the first APP and the bank identifier according to the binding request received by the first receiving module.

In one embodiment, the binding module may include:

the login submodule is configured to send a login request to the second server, and the login request carries the identification information of the first APP, the bank account corresponding to the bank identifier and a login password;

the setting submodule is configured to display a payment information setting interface when receiving a third response message returned by the second server according to the login request sent by the login submodule, and analyze a serial code of the first APP for payment by using the bank identifier from the third response message;

the binding submodule is configured to send a binding completion request to the first server to complete the operation of binding the first APP with the bank identifier when receiving payment information input in the payment information setting interface displayed by the setting submodule, and the binding completion request carries a payment password for payment in the first APP by using the bound bank identifier, the serial number and application identifier information of the second APP.

According to a fifth aspect of the embodiments of the present disclosure, there is provided a payment apparatus applied on a first server, the apparatus may include:

the second receiving module is configured to receive a first payment request sent by the electronic payment device, wherein the first payment request carries application identification information and payment amount of a second APP corresponding to the bank identification bound to the first APP;

a second generating module, configured to generate a second payment request according to the first payment request received by the second receiving module, where the second payment request carries a serial number of the first APP for payment using the bank identifier and the payment amount;

the second sending module is configured to send the second payment request generated by the second generating module to a second server corresponding to the second APP, so that the second server executes an amount transfer operation of a payment transaction according to the second payment request.

In an embodiment, the apparatus may further comprise:

a third receiving module configured to receive a binding completion request;

a second parsing module configured to parse, from the binding completion request received by the third receiving module, a payment password, the serial number, and application identification information of the second APP, which are used by the first APP to pay using the bound bank identification;

the storage module is configured to store the payment password, the string code and the application identification information of the second APP, which are obtained by the second analysis module through analysis and used for payment in the first APP by using the bound bank identification.

According to a sixth aspect of the embodiments of the present disclosure, there is provided a payment apparatus applied on a second server, the apparatus may include:

a fourth receiving module, configured to receive a second payment request sent by a first server, where the second payment request carries a serial number and a payment amount of the first APP for payment using the bank identifier;

a third sending module, configured to send a first response message to the electronic payment device through a second APP corresponding to the second server, so that the electronic payment device controls the second APP to generate a payment confirmation prompt message according to the first response message;

a fourth sending module configured to send the payment confirmation message to the first server when receiving the payment confirmation message sent by the electronic payment device according to the first response message sent by the third sending module.

In one embodiment, the apparatus comprises:

a fifth receiving module, configured to receive the login request sent by the electronic payment device, where the login request carries application identification information of the first APP, a bank account corresponding to a bank identification bound to the first APP, and a login password;

a third generating module, configured to generate a serial code for payment in the first APP by using the bank identifier when it is determined that the bank account and the login password, which correspond to the bank identifier bound to the first APP, carried in the login request received by the fifth receiving module are correct;

a fifth sending module, configured to send a third response message to the electronic payment device, where the third response message carries a serial code of the first APP for payment using the bank identifier.

According to a seventh aspect of the embodiments of the present disclosure, there is provided a payment apparatus applied to an electronic payment device, the apparatus including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

when a trigger event for payment through a bank identifier bound by a first APP is received, sending a first payment request to a first server corresponding to the first APP, wherein the first payment request carries application identifier information of a second APP corresponding to the bank identifier bound by the first APP;

According to an eighth aspect of the embodiments of the present disclosure, there is provided a payment apparatus applied on a first server, the apparatus including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

According to a ninth aspect of the embodiments of the present disclosure, there is provided a payment apparatus applied on a second server, the apparatus including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

According to a tenth aspect of embodiments of the present disclosure, there is provided a payment system, which may include: the system comprises an electronic payment device, a first server and a second server;

when the electronic payment equipment receives a trigger event for payment through a bank identifier bound by a first APP application program, sending a first payment request to a first server corresponding to the first APP, wherein the first payment request carries application identifier information of a second APP corresponding to the bank identifier bound by the first APP;

after receiving the first payment request, the first server generates a second payment request according to the first payment request, wherein the second payment request carries a serial code for payment by using the bank identifier in the first APP;

the first server sends the second payment request to a second server corresponding to the second APP;

after receiving the second payment request, the second server sends a first response message to the electronic payment device through a corresponding second APP;

the electronic payment equipment controls the second APP to generate payment confirmation prompt information according to the first response message;

and when the electronic payment equipment receives the feedback information for confirming the payment input according to the payment confirmation prompt message, executing the operation of payment transaction.

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: when a user is at a first APP in an electronic payment device, for example: when the bound bank identification is used for payment in WeChat in the smart phone, a first payment request can be sent to a first server corresponding to a first APP, when the first server receives the first payment request, a serial code can be determined according to the first APP and the bound bank identification, a second payment request is generated and sent to a second server, the second server returns a first response message to a second APP corresponding to the second server according to the second payment request, a user can perform payment confirmation on an operation interface of the second APP and complete payment transaction operation, and the payment transaction operation can be completed in the first APP only by performing payment confirmation in a second APP, namely a bank client side, when the user uses the bank identification bound by the first APP for payment, so that the payment transaction is safer; in addition, because first APP and second APP can be located different terminal equipment, consequently increased the safety of user's bank sign, can further avoid causing unnecessary loss to user's property safety.

And when the electronic payment device receives a binding request of the first APP binding a bank identifier, a second APP corresponding to the bank identification may be called using the system interface, the user may log in to a second server corresponding to the second APP, and the second server generates a serial code in the first APP for payment by using the bank identifier, the second server sends the serial code to the first APP, the first APP sends the payment password, the serial code and the identifier information of the second APP to the first server to finish the operation that the first APP binds a bank identifier, therefore, when a bank card is bound in the first APP, the password of the bank card and the bank card does not need to be input, the problem that the identity card and the bank identification which are caused by information such as the identity card and the bank identification of the user are leaked in the first APP is avoided, the safety of the bank identification of the user is improved, and the experience of the user is optimized.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.

FIG. 1A is a flow diagram illustrating a payment method in accordance with an exemplary embodiment.

FIG. 1B is a first scenario diagram illustrating a payment method in accordance with an example embodiment.

FIG. 1C is a diagram illustrating a scenario of a payment method in accordance with an exemplary embodiment.

Fig. 2A is a flow chart illustrating a payment method according to an example embodiment.

Fig. 2B is a diagram illustrating selection of a bank card in a payment method according to an example embodiment.

Fig. 2C is a schematic diagram illustrating payment confirmation on the operation interface of the second APP according to an exemplary embodiment.

Fig. 3 is a flow chart illustrating a payment method according to an example embodiment two.

Fig. 4 is a flow chart illustrating a payment method according to an example embodiment.

Fig. 5 is a flow chart of a payment method according to an example embodiment.

FIG. 6 is a block diagram illustrating a payment device according to an example embodiment.

FIG. 7 is a block diagram illustrating yet another payment device according to an example embodiment.

FIG. 8 is a block diagram illustrating a payment device according to an example embodiment.

FIG. 9 is a block diagram illustrating yet another payment device according to an example embodiment.

FIG. 10 is a block diagram illustrating a payment device according to an example embodiment.

FIG. 11 is a block diagram illustrating yet another payment device according to an example embodiment.

FIG. 12 is a block diagram illustrating a suitable payment device according to an exemplary embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.

Fig. 1A is a flowchart illustrating a payment method according to an exemplary embodiment, which may be applied to an electronic payment device, such as a smart phone, a tablet computer, and a smart band, as shown in fig. 1A, and includes the following steps:

in step 101, when a trigger event for payment through a bank identifier bound by a first APP is received, a first payment request is sent to a first server corresponding to the first APP.

In an embodiment, the first payment request carries application identification information of a second APP corresponding to a bank identification bound to the first APP, and a payment amount.

In one embodiment, the bank identification may be a bank name or the like used to indicate the bank system to which the bank account used for payment belongs.

In one embodiment, the first APP may be an application program such as WeChat, Paibao, taxi-taking software, and the like; in yet another embodiment, the second APP may be a bank client application, such as a client application of an industrial and commercial bank; in another embodiment, the first server is a server corresponding to the first APP, such as a wechat server; in another embodiment, the second server is a server corresponding to the second APP, such as an industrial and commercial bank server.

In step 102, when a first response message returned by a second server corresponding to a second APP according to a second payment request is received, the second APP is controlled to generate a payment confirmation prompt message.

In an embodiment, the second payment request is generated by the first server according to the first payment request and sent to the second server through the first server, and the second payment request carries a serial code for payment using the bank identifier in the first APP.

In an embodiment, the string code may be an identification information composed of numbers and/or letters for identifying the currently executed payment transaction as the payment made in the first APP using the bound bank account number.

In one embodiment, the payment confirmation prompt message may be a text prompt message, such as "the WeChat payment platform requests to perform a payment operation, please confirm" the text prompt message.

In step 103, when feedback information for confirming payment input according to the payment confirmation prompting message is received, the operation of payment transaction is performed.

In one embodiment, the user may input the feedback information for confirming the payment according to the payment confirmation message, for example, after displaying the "WeChat payment platform requests to perform the payment operation, please confirm the" text prompt message, "the user may click the confirmation button to input the feedback information for confirming the payment, thereby completing the payment operation.

In an exemplary embodiment, as shown in fig. 1B, in the present exemplary embodiment, a first APP and a second APP are both running in the electronic payment device 110, and when the electronic payment device 110 receives a trigger event for payment by a bank card number bound by the first APP, a send first payment request may be sent to a first server 120 corresponding to the first APP, and when the first server 120 receives the first payment request, the serial code can be determined according to the first APP and the bound bank identifier, a second payment request is generated and sent to the second server 130, the second server 130 returns a first response message to the second APP corresponding to the second server 130 according to the second payment request, the user can confirm payment on the operation interface of the second APP, and after the confirmation, sending the payment confirmation result to the first APP for the first APP to complete the payment transaction operation.

In an exemplary embodiment, as shown in fig. 1C, in the present exemplary embodiment, a first APP runs in an electronic payment device 110, second APPs run in an association device 140, the first APP can access the second APP running in the association device 140 by calling a system interface, when the electronic payment device 110 receives a trigger event of payment by a bank card number bound by the first APP in the electronic payment device 110, a first payment request can be sent to a first server 120 corresponding to the first APP, when the first server 120 receives the first payment request, a string code can be determined according to the first APP and a bound bank identifier, a second payment request is generated and sent to a second server 130, the second server 130 sends a first response message to the second APP running in the association device 140 according to the second payment request, and a user can perform payment confirmation on an operation interface of the second APP, and after the confirmation, sending the payment confirmation result to the first APP for the first APP to complete the payment transaction operation.

In this embodiment, the user needs to pay in the second APP, bank client promptly and confirms when using the bank identification payment that first APP binds, just can accomplish the payment transaction operation in first APP, therefore the payment transaction is safer.

In an embodiment, when feedback information for confirming payment input according to the payment confirmation prompting message is received, the operation of performing the payment transaction may include:

when feedback information for confirming payment input according to the payment confirmation prompt message is received, sending a payment confirmation message to the second server so that the second server can forward the payment confirmation message to the first server;

In an embodiment, the method may further comprise:

receiving a binding request for binding the bank identifier triggered by an operation interface of the first APP, wherein the binding request carries application identifier information of a second APP corresponding to the bank identifier;

displaying a login interface of a second APP according to the binding request;

when login information input in a login interface is received, a login request is sent to a second server, wherein the login request carries identification information of a first APP, a bank account corresponding to a bank identification and a login password;

when a third response message returned by the second server according to the login request is received, analyzing a serial code for payment in the first APP by using the bank identifier from the third response message;

displaying a payment information setting interface;

when payment information input in the payment information setting interface is received, sending a binding completion request to the first server to complete the operation of binding the first APP with the bank identifier, wherein the binding completion request carries a payment password, a serial number and application identifier information of the second APP, which are used by the bound bank identifier in the first APP for payment.

The technical solutions provided by the embodiments of the present disclosure are described below with specific embodiments.

Fig. 2A is a flow chart illustrating a payment method according to an exemplary embodiment, fig. 2B is a schematic diagram illustrating a selection of a bank card in a payment method according to an exemplary embodiment, and fig. 2C is a schematic diagram illustrating a confirmation of payment on an operation interface of a second APP according to an exemplary embodiment; in this embodiment, by using the above method provided by the embodiment of the present disclosure, taking the electronic payment device, the first server, and the second server to perform information interaction to complete payment transaction as an example, and referring to fig. 1B and 1C, as shown in fig. 2A, the method includes the following steps:

in step 201, the electronic payment device receives a trigger event for payment through a bank card number bound by a first APP.

In an exemplary embodiment, referring to fig. 1B, a payment bank card, such as a tenderer bank savings card, may be selected in a millet payment wallet.

In step 202, the electronic payment device sends a first payment request to a first server corresponding to a first APP.

In an embodiment, the first payment request carries application identification information of a second APP corresponding to a bank identification bound to the first APP. For example, the first payment request may carry payment information in the meaning of "WeChat Payment platform chooses to pay 99 dollars to Setarian mall using a money card with a money card end number of 0956".

In step 203, after receiving the first payment request, the first server generates a second payment request according to the first payment request.

In an embodiment, the second payment request carries the first APP identification information, the serial number of the first APP for payment by using the bank identification, the bank card number, and the payment amount. For example, the second payment request may carry payment information indicating that the wechat payment platform chooses to pay 99 yuan, wxzsyh0956, using a money card with a money card end number of 0956 for a money card of a tenderer's bank.

In step 204, the first server sends a second payment request to the second server.

In step 205, the second server receives the second payment request and parses payment information from the second payment request.

In one embodiment, the payment information includes information such as the first APP id, the serial number, the bank card number, and the payment amount.

In step 206, the second server determines whether the string in the second payment request is correct, if the string in the second payment request is correct, step 207 is executed, and if the string in the second payment request is incorrect, the process ends.

In an embodiment, a string is used to identify information in the first APP that is paid using the bound bank card number, the string being generated by the second server.

In one embodiment, the second server may store the first APP identified by the generated string code and the bank card number.

In step 207, the second server sends the first response message to the electronic payment device through the second APP.

In an embodiment, referring to fig. 1B, the first APP and the second APP are both located on the electronic payment device, and the first response message may be sent directly to the electronic payment device.

In an embodiment, referring to fig. 1C, the first APP is located on the electronic payment device, and the second APP is located on the associated device, then the second APP may forward the first response message to the electronic associated device through the system interface.

In step 208, the electronic payment device controls the second APP to generate a payment confirmation prompt message according to the first response message.

In an embodiment, referring to fig. 2C, a schematic diagram of controlling payment confirmation generated by the second APP for the electronic payment device is shown.

In step 209, the electronic payment device sends a payment confirmation message to the second server when receiving the feedback information of payment confirmation input according to the payment confirmation prompt message.

In one embodiment, the user may input the payment confirmation feedback information by touching the touch screen, physically pressing a button, such as "confirm payment" in fig. 2C.

In step 210, the second server sends a confirmation payment message to the first server.

In step 211, the first server determines that the second server has completed payment according to the confirmation payment message, and sends a second response message to the first APP.

In an embodiment, the second response message carries information indicating that the payment is completed.

In step 212, a first APP in the electronic payment device displays the result of the payment completion.

In this embodiment, when the user is the first APP in the electronic payment device, for example: when the bound bank identification is used for payment in WeChat in the smart phone, a first payment request can be sent to a first server corresponding to a first APP, when the first server receives the first payment request, a serial code can be determined according to the first APP and the bound bank identification, a second payment request is generated and sent to a second server, the second server returns a first response message to a second APP corresponding to the second server according to the second payment request, a user can perform payment confirmation on an operation interface of the second APP and complete payment transaction operation, and the payment transaction operation can be completed in the first APP only by performing payment confirmation in a second APP, namely a bank client side, when the user uses the bank identification bound by the first APP for payment, so that the payment transaction is safer; in addition, because first APP and second APP can be located different terminal equipment, consequently increased the safety of user's bank sign, can further avoid causing unnecessary loss to user's property safety.

Fig. 3 is a flowchart of a payment method according to an exemplary embodiment, where this embodiment uses the method provided in this disclosure to exemplarily explain information interaction among the electronic payment device, the first server, and the second server when binding the first APP with the bank card, as shown in fig. 3, the method includes the following steps:

in step 301, the electronic payment device receives a binding request for binding a bank identifier triggered through an operation interface of the first APP.

In an embodiment, the binding request carries application identification information of the second APP corresponding to the bank identification.

In step 302, the electronic payment device displays a login interface of the second APP according to the binding request.

In one embodiment, the first APP may call a system interface, and the system will open an operation interface of the second APP by transferring the name of the second APP into the system interface. In a further embodiment, the second APP may also determine, through the system interface, identification information of the first APP requesting to open the second APP, for example, a name of the first APP.

In step 303, when the electronic payment device receives the login information input in the login interface, it sends a login request to the second server.

In an embodiment, the login request carries identification information of the first APP, a bank account corresponding to the bank identifier, and a login password.

In step 304, after receiving the login request, the second server determines whether the bank account and the login password corresponding to the bank identifier input by the user are correct; if the bank account and the login password corresponding to the bank identifier input by the user are correct, step 305 is executed, and if the bank account and the login password corresponding to the bank identifier input by the user are incorrect, step 310 is executed.

In step 305, the second server returns a third response message to the electronic payment device through the second APP according to the login request.

In an embodiment, the third response message carries a serial number of the first APP for payment by using the bank identifier.

In an embodiment, the second server returns a third response message to the electronic payment device through the second APP according to the login request, including: and the second server sends a third response message to the second APP, and the second APP sends the third response message to the first APP after receiving the third response message.

In step 306, the electronic payment device controls the first APP to display the payment information setting interface.

In step 307, when the electronic payment device receives the payment information input in the payment information setting interface, a binding completion request is sent to the first server.

In an embodiment, the binding completion request carries a payment password, a serial number, and application identification information of the second APP, which are used by the first APP to perform payment by using the bound bank identifier.

In step 308, after receiving the binding completion request, the first server analyzes the payment password, the serial number, and the application identification information of the second APP, which are used by the first APP to pay using the bound bank identifier, from the binding completion request.

In step 309, the first server stores the payment password, the string code, and the application identification information of the second APP for payment using the bound bank identification in the first APP.

In step 310, a prompt is displayed that the bank identification or login password is incorrect and the payment transaction interface is closed.

In the embodiment, when the electronic payment device receives a binding request that the first APP binds a bank identifier, a second APP corresponding to the bank identification may be called using the system interface, the user may log in to a second server corresponding to the second APP, and the second server generates a serial code for payment in the first APP by using the bank identifier, the second server sends the serial code to the first APP, the first APP sends the payment password, the serial code and the identifier information of the second APP to the first server to complete the operation of binding the first APP with the bank identifier, therefore, when a bank card is bound in the first APP, the password of the bank card and the bank card does not need to be input, the problem that the identity card and the bank identification which are caused by information such as the identity card and the bank identification of the user are leaked in the first APP is avoided, the safety of the bank identification of the user is improved, and the experience of the user is optimized.

Fig. 4 is a flowchart illustrating a payment method according to an exemplary embodiment, which may be applied to a first server, such as a WeChat server, as shown in fig. 4, and includes the following steps:

in step 401, a first payment request sent by an electronic payment device is received.

In an embodiment, the first payment request carries application identification information and payment amount of a second APP corresponding to a bank identification bound to the first APP.

In step 402, a second payment request is generated based on the first payment request.

In step 403, a second payment request is sent to a second server corresponding to the second APP, so that the second server executes an amount transfer operation of the payment transaction according to the second payment request.

In this embodiment, when the first server receives the first payment request, the first server may determine the serial number according to the first APP and the bound bank identifier, generate the second payment request, and send the second payment request to the second server, because the user needs to perform payment confirmation in the second APP, that is, the bank client, when using the bank identifier bound by the first APP to pay, the payment transaction operation can be completed in the first APP, so the payment transaction is safer.

In an embodiment, the method may further comprise:

receiving a binding completion request;

analyzing a payment password, a serial code and application identification information of a second APP for payment by using the bound bank identification in the first APP from the binding completion request;

and storing the payment password, the serial code and the application identification information of the second APP, which are paid by using the bound bank identification in the first APP.

Fig. 5 is a flowchart illustrating a payment method according to an exemplary embodiment, which may be applied to the second server, as shown in fig. 5, and includes the following steps:

in step 501, a second payment request sent by the first server is received.

In an embodiment, the second payment request carries the serial number and the payment amount of the first APP paid by using the bank identifier.

In step 502, a first response message is sent to the electronic payment device through a second APP corresponding to the second server, so that the electronic payment device controls the second APP to generate a payment confirmation prompt message according to the first response message.

In step 503, when a payment confirmation message sent by the electronic payment device according to the first response message is received, the payment confirmation message is sent to the first server.

In this embodiment, the second server returns the first response message to the second APP that the second server corresponds according to this second payment request, and the user can confirm the payment on the operation interface of second APP, accomplishes the payment transaction operation, because the user needs to confirm at the second APP when using the bank sign payment that first APP binds, just can accomplish the payment transaction operation in first APP in bank client promptly, therefore the payment transaction is safer.

In an embodiment, the method may further comprise:

receiving a login request sent by electronic payment equipment, wherein the login request carries application identification information of a first APP, a bank account and a login password, and the bank account corresponds to a bank identification bound with the first APP;

when the bank account and the login password corresponding to the bank identifier bound with the first APP are determined to be correct, generating a serial code for payment by using the bank identifier in the first APP;

and sending a third response message to the electronic payment equipment, wherein the third response message carries the serial code of the first APP for payment by using the bank identifier.

Corresponding to the embodiment of the payment method, the disclosure also provides an embodiment of a payment device.

Fig. 6 is a block diagram illustrating a payment apparatus according to an exemplary embodiment, the apparatus being applied to an electronic payment device, as shown in fig. 6, the payment apparatus including:

the first sending module 610 is configured to send a first payment request to a first server corresponding to a first APP when a trigger event for payment through a bank identifier bound to the first APP is received, where the first payment request carries application identifier information of a second APP corresponding to the bank identifier bound to the first APP;

the first generating module 620 is configured to control a second APP to generate a payment confirmation prompt message when receiving a first response message returned by a second server corresponding to the second APP according to a second payment request, where the second payment request is generated by the first server according to a first payment request sent by the first sending module 610 and sent to the second server through the first server, and the second payment request carries a serial code of the first APP for payment by using a bank identifier;

a payment transaction module 630 configured to perform an operation of a payment transaction when receiving feedback information for confirming payment inputted according to the payment confirmation prompting message generated by the first generation module 620.

Fig. 7 is a block diagram of another payment device according to an exemplary embodiment, as shown in fig. 7, and based on the embodiment shown in fig. 6, in an embodiment, the payment transaction module 630 includes:

a first sending sub-module 631 configured to send a payment confirmation message to the second server for the second server to forward the payment confirmation message to the first server when receiving feedback information of payment confirmation input according to the payment confirmation prompt message generated by the first generation module 620;

a first receiving sub-module 632 configured to receive a second response message returned by the first server according to the payment confirmation message sent by the first sending sub-module 631;

the execution submodule 633 is configured to execute the operation of the payment transaction according to the second response message received by the first receiving submodule 632.

In an embodiment, the apparatus may further comprise:

a first receiving module 640, configured to receive a binding request for binding a bank identifier triggered through an operation interface of a first APP, where the binding request carries application identifier information of a second APP corresponding to the bank identifier;

a binding module 650 configured to perform an operation of binding the first APP with the bank identity according to the binding request received by the first receiving module 640.

In one embodiment, the binding module 650 includes:

the login submodule 651 is configured to send a login request to the second server, where the login request carries identification information of the first APP, a bank account corresponding to the bank identifier, and a login password;

the setting sub-module 652 is configured to, when receiving a third response message returned by the second server according to the login request sent by the login sub-module 651, display a payment information setting interface, and analyze, from the third response message, a serial number of the first APP for payment using the bank identifier;

the binding submodule 653 is configured to, when receiving payment information input in the payment information setting interface displayed by the setting submodule 652, send a binding completion request to the first server to complete the operation of binding the first APP with the bank identifier, where the binding completion request carries a payment password for payment in the first APP using the bound bank identifier, the serial number, and application identifier information of the second APP.

With regard to the apparatus in the above embodiment, the specific manner in which each module and sub-module performs operations has been described in detail in the embodiment related to the method, and will not be elaborated here.

Fig. 8 is a block diagram illustrating a payment apparatus applied to a first server according to an exemplary embodiment, where the payment apparatus includes:

the second receiving module 810 is configured to receive a first payment request sent by the electronic payment device, where the first payment request carries application identification information of a second APP and a payment amount, where the second APP corresponds to a bank identification bound to the first APP;

a second generating module 820, configured to generate a second payment request according to the first payment request received by the second receiving module 810, where the second payment request carries the serial number and the payment amount of the first APP paid by using the bank identifier;

a second sending module 830, configured to send the second payment request generated by the second generating module 820 to a second server corresponding to the second APP, so that the second server performs an amount transfer operation of the payment transaction according to the second payment request.

Fig. 9 is a block diagram of another payment apparatus according to an exemplary embodiment, as shown in fig. 9, and based on the embodiment shown in fig. 8, in an embodiment, the apparatus further includes:

a third receiving module 840 configured to receive a binding completion request;

a second parsing module 850 configured to parse, from the binding completion request received by the third receiving module 840, the payment password, the serial number, and the application identification information of the second APP, where the payment is performed using the bound bank identifier in the first APP;

a storage module 860 configured to store the payment password, the string code, and the application identification information of the second APP, which are obtained by the second parsing module 850 by parsing and payment is performed by using the bound bank identifier.

Fig. 10 is a block diagram illustrating a payment apparatus applied to a second server according to an exemplary embodiment, and as shown in fig. 10, the payment apparatus includes:

a fourth receiving module 1010, configured to receive a second payment request sent by the first server, where the second payment request carries the serial number and the payment amount of the first APP paid by using the bank identifier;

a third sending module 1020, configured to send a first response message to the electronic payment device through a second APP corresponding to the second server, so that the electronic payment device controls the second APP to generate a payment confirmation prompt message according to the first response message;

a fourth sending module 1030 configured to send a confirmation payment message to the first server when receiving the confirmation payment message sent by the electronic payment device according to the first response message sent by the third sending module 1020.

Fig. 11 is a block diagram of another payment apparatus according to an exemplary embodiment, as shown in fig. 11, and based on the above-mentioned embodiment shown in fig. 10, in an embodiment, the apparatus may further include:

a fifth receiving module 1040, configured to receive a login request sent by the electronic payment device, where the login request carries application identification information of the first APP, a bank account corresponding to a bank identification bound to the first APP, and a login password;

the third generating module 1050 is configured to generate a serial code for performing payment by using the bank identifier in the first APP when it is determined that the bank account and the login password, which correspond to the bank identifier bound to the first APP, carried in the login request received by the fifth receiving module 1040 are correct;

the fifth sending module 1060 is configured to send a third response message to the electronic payment device, where the third response message carries the serial code of the first APP for performing payment using the bank identifier.

Corresponding to the embodiments of the payment method and the payment device, the present disclosure also provides an embodiment of a payment system, where the payment system provided in this embodiment includes an electronic payment device, a first server, and a second server; when the electronic payment equipment receives a trigger event for payment through a bank identifier bound by a first APP application program, sending a first payment request to a first server corresponding to the first APP, wherein the first payment request carries application identifier information of a second APP corresponding to the bank identifier bound by the first APP; after receiving the first payment request, the first server generates a second payment request according to the first payment request, wherein the second payment request carries a serial code for payment by using the bank identifier in the first APP; the first server sends a second payment request to a second server corresponding to the second APP; after receiving the second payment request, the second server sends a first response message to the electronic payment device through the corresponding second APP; the electronic payment equipment controls the second APP to generate payment confirmation prompt information according to the first response message; and when the electronic payment equipment receives the feedback information for confirming the payment input according to the payment confirmation prompt message, executing the operation of payment transaction. The system provided by the embodiment of the disclosure can realize that payment confirmation is required to be carried out in the bank client when the user uses the bank identifier bound by the first APP for payment, so that the payment transaction is safer.

Fig. 12 is a block diagram illustrating a registration apparatus adapted for use with a third party client according to an example embodiment. For example, the apparatus 1200 may be a smartphone, a tablet computer, or the like.

Referring to fig. 12, the apparatus 1200 may include one or more of the following components: processing component 1202, memory 1204, power component 1206, multimedia component 1208, audio component 1210, input/output (I/O) interface 1212, sensor component 1214, and communications component 1216.

The processing component 1202 generally controls overall operation of the apparatus 1200, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing element 1202 may include one or more processors 1220 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 1202 can include one or more modules that facilitate interaction between the processing component 1202 and other components. For example, the processing component 1202 can include a multimedia module to facilitate interaction between the multimedia component 1208 and the processing component 1202.

The memory 1204 is configured to store various types of data to support operation at the device 1200. Examples of such data include instructions for any application or method operating on the device 1200, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 1204 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

A power component 1206 provides power to the various components of the device 1200. Power components 1206 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for apparatus 1200.

The multimedia component 1208 includes a screen that provides an output interface between the device 1200 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1208 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 1200 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

Audio component 1210 is configured to output and/or input audio signals. For example, audio component 1210 includes a Microphone (MIC) configured to receive external audio signals when apparatus 1200 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 1204 or transmitted via the communication component 1216. In some embodiments, audio assembly 1210 further includes a speaker for outputting audio signals.

The I/O interface 1212 provides an interface between the processing component 1202 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor assembly 1214 includes one or more sensors for providing various aspects of state assessment for the apparatus 1200. For example, the sensor assembly 1214 may detect the open/closed state of the device 1200, the relative positioning of the components, such as the display and keypad of the apparatus 1200, the sensor assembly 1214 may also detect a change in the position of the apparatus 1200 or a component of the apparatus 1200, the presence or absence of user contact with the apparatus 1200, the orientation or acceleration/deceleration of the apparatus 1200, and a change in the temperature of the apparatus 1200. The sensor assembly 1214 may include a proximity sensor configured to detect the presence of a nearby object in the absence of any physical contact. The sensor assembly 1214 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1214 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communications component 1216 is configured to facilitate communications between the apparatus 1200 and other devices in a wired or wireless manner. The apparatus 1200 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 1216 receives a broadcast signal or broadcast associated information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communications component 1216 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the apparatus 1200 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.

In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as memory 1204 comprising instructions, executable by processor 1220 of apparatus 1200 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

The specific structure of the first server and the second server can be seen from the block diagram shown in fig. 12 and the corresponding description, and will not be described in detail here.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A payment method for use on an electronic payment device, the method comprising:

when a trigger event for payment through a bank identifier bound by a first APP application program is received, sending a first payment request to a first server corresponding to the first APP, wherein the first payment request carries application identifier information of a second APP corresponding to the bank identifier bound by the first APP;

when a first response message returned by a second server corresponding to a second APP according to a second payment request is received, controlling the second APP to generate a payment confirmation prompt message, wherein the second payment request is generated by the first server according to the first payment request and sent to the second server through the first server, the second payment request carries a serial code which is generated in the first APP and used for payment by using the bank identifier, and the second APP is a bank client application program, wherein the first APP calls the second APP through a system interface, and the serial code is a serial code which is generated by the second server and used for payment by using the bank identifier by the first APP;

executing the operation of payment transaction when receiving the feedback information for confirming payment input according to the payment confirmation prompt message;

when feedback information for confirming payment input according to the payment confirmation prompt message is received, executing operation of payment transaction, wherein the operation comprises the following steps:

2. The method of claim 1, further comprising:

3. The method according to claim 2, wherein said performing the operation of binding said first APP with said bank identity comprises:

when the payment information input in the payment information setting interface is received, sending a binding completion request to the first server so as to complete the operation of binding the first APP with the bank identifier, wherein the binding completion request carries a payment password for payment by using the bound bank identifier in the first APP, the serial number and the application identifier information of the second APP.

4. A payment method, applied on a first server, the method comprising:

receiving a first payment request sent by electronic payment equipment, wherein the first payment request carries application identification information and payment amount of a second APP corresponding to a bank identification bound by a first APP;

generating a second payment request according to the first payment request, wherein the second payment request carries a serial code for payment by using the bank identifier in the first APP and the payment amount, and the serial code is generated by a second server;

sending the second payment request to a second server corresponding to the second APP, so that the second server can execute an amount transfer operation of payment transaction according to the second payment request, wherein the second APP is a bank client application program;

and the first APP calls the second APP through a system interface.

5. The method of claim 4, further comprising:

receiving a binding completion request;

6. A payment method, applied on a second server, the method comprising:

receiving a second payment request sent by the first server, wherein the second payment request carries a serial number and a payment amount of payment carried out by using a bank identifier in the first APP;

sending a first response message to the electronic payment equipment through a second APP corresponding to the second server, so that the electronic payment equipment controls a second APP to generate a payment confirmation prompt message according to the first response message, wherein the second APP is a bank client application program, and the first APP calls the second APP through a system interface;

7. The method of claim 6, wherein the method comprises:

receiving a login request sent by electronic payment equipment, wherein the login request carries application identification information of the first APP, a bank account and a login password, and the bank account corresponds to a bank identification bound with the first APP;

8. A payment apparatus for use on an electronic payment device, the apparatus comprising:

a first generating module, configured to control a second APP to generate a payment confirmation prompt message when receiving a first response message returned by a second server corresponding to the second APP according to a second payment request, where the second payment request is generated by the first server according to the first payment request sent by the first sending module and sent to the second server through the first server, the second payment request carries a string code used by the first APP to pay using the bank identifier, and the second APP is a bank client application program, where the first APP calls the second APP through a system interface, and the string code is a string code generated by the second server and used by the first APP to pay using the bank identifier;

a payment transaction module configured to perform an operation of a payment transaction when receiving feedback information for confirming payment input according to the payment confirmation prompt message generated by the first generation module;

the payment transaction module comprises:

9. The apparatus of claim 8, further comprising:

10. The apparatus of claim 9, wherein the binding module comprises:

11. A payment device for application on a first server, the device comprising:

the second receiving module is configured to receive a first payment request sent by the electronic payment device, wherein the first payment request carries application identification information and payment amount of a second APP corresponding to the bank identification bound with the first APP;

a second generating module, configured to generate a second payment request according to the first payment request received by the second receiving module, where the second payment request carries a serial number and the payment amount of the first APP paid by using the bank identifier, and the serial number is generated by a second server;

a second sending module configured to send the second payment request generated by the second generating module to a second server corresponding to the second APP, so that the second server executes an amount transfer operation of a payment transaction according to the second payment request, where the second APP is a bank client application program;

and the first APP calls the second APP through a system interface.

12. The apparatus of claim 11, further comprising:

a third receiving module configured to receive a binding completion request;

13. A payment device for application on a second server, the device comprising:

the fourth receiving module is configured to receive a second payment request sent by the first server, wherein the second payment request carries the serial number and the payment amount of the first APP paid by using the bank identifier;

a third sending module, configured to send a first response message to an electronic payment device through a second APP corresponding to the second server, so that the electronic payment device controls a second APP to generate a payment confirmation prompt message according to the first response message, where the second APP is a bank client application program, and the first APP calls the second APP through a system interface;

14. The apparatus of claim 13, wherein the apparatus comprises:

a fifth receiving module, configured to receive a login request sent by an electronic payment device, where the login request carries application identification information of the first APP, a bank account corresponding to a bank identification bound to the first APP, and a login password;

15. A payment apparatus for use on an electronic payment device, the apparatus comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

16. A payment device for application on a first server, the device comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

and the first APP calls the second APP through a system interface.

17. A payment device for application on a second server, the device comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

18. A payment system, the system comprising: the system comprises an electronic payment device, a first server and a second server;

when the electronic payment equipment receives a trigger event for payment through a bank identifier bound by a first APP application program, sending a first payment request to a first server corresponding to the first APP, wherein the first payment request carries application identifier information of a second APP corresponding to the bank identifier bound by the first APP, and the second APP is a bank client application program, and the first APP calls the second APP through a system interface;

after receiving the first payment request, the first server generates a second payment request according to the first payment request, wherein the second payment request carries a serial code for payment by using the bank identifier in the first APP, and the serial code is generated by the second server;