CN111652604A

CN111652604A - Order payment method, order payment device and order payment system

Info

Publication number: CN111652604A
Application number: CN202010669129.7A
Authority: CN
Inventors: 查毅勇; 吴晓斌
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-07-13
Filing date: 2020-07-13
Publication date: 2020-09-11

Abstract

An order payment method is described, implemented on a cloud application server, the method comprising: the method comprises the steps of obtaining a payment interface calling request from a cloud payment client on a cloud application server, wherein the payment interface calling request is used for requesting to call a payment interface of the payment application client located on a cloud application client side so as to pay an order in the cloud payment client; and sending the payment interface calling request to the cloud application client so as to call a payment interface of the payment application client to pay the order. The cloud application client can receive the payment interface calling request; confirming whether the payment interface calling request is legal or not; and calling a payment interface of the payment application client to pay the order in response to the legality of the payment interface calling request.

Description

Order payment method, order payment device and order payment system

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to an order payment method, an order payment apparatus, and an order payment system.

Background

With the development of internet technology, Cloud technology (Cloud technology) has gained wide application. The cloud technology is a hosting technology for unifying series resources such as hardware, software, network and the like in a wide area network or a local area network to realize the calculation, storage, processing and sharing of data. Cloud technology (Cloud technology) is a generic term of network technology, information technology, integration technology, management platform technology, application technology and the like based on Cloud computing business model application, can form a resource pool, is used as required, and is flexible and convenient. Cloud computing technology will become an important support. Background services of the technical network system require a large amount of computing and storage resources, such as video websites, picture-like websites and more web portals. With the high development and application of the internet industry, each article may have its own identification mark and needs to be transmitted to a background system for logic processing, data in different levels are processed separately, and various industrial data need strong system background support and can only be realized through cloud computing.

At present, more and more application programs exist as cloud applications to save resources on the terminal side. Cloud applications are a subset of the concept of "cloud computing", which is the embodiment of cloud computing technology at the application layer. The working principle of the cloud application is to install a traditional locally-installed and locally-operated application program into a remote server cluster (namely, a cloud server) so as to become an instant-and-play service for completing business logic or operation tasks. The instance of the cloud application installed on the cloud server is the same as the corresponding application instance running locally, but the installation location is different. The main carrier of the cloud application is internet technology, and is in a presentation form of a Thin Client (Thin Client) or an intelligent Client (Smart Client). The cloud application can help a user to reduce IT cost and greatly improve working efficiency, so that the development and innovation surge of the traditional software to the cloud application is not blocked.

However, while cloud applications offer many benefits, they also present challenges to the way many applications are used, such as existing payment applications. Taking the cloud application as the cloud shopping application or the cloud game application as an example, a user may shop in the cloud shopping application or purchase a prop in the cloud game application, and at this time, the cloud application generates an order for the user to pay, and when paying for the order, a payment interface of a payment application client (e.g., a payment program of a payment treasure, a WeChat payment program, etc.) is usually required to be invoked for payment. However, the payment application client is usually installed on the local terminal, and to enable the cloud application to call the payment application client on the local terminal, the existing logic implementation of the cloud application needs to be modified to support such call, which brings a large re-development cost, and although the payment application client and the cloud application are jointly deployed on the cloud server, the overhead of modifying the logic implementation of the cloud application can be avoided, but the deployment of the payment application client on the cloud server brings a large security problem.

Disclosure of Invention

In view of the above, it is desirable to overcome some or all of the above-mentioned drawbacks and other possible drawbacks.

According to a first aspect of the present disclosure, there is provided an order payment method implemented on a cloud application server, the method comprising: the method comprises the steps of obtaining a payment interface calling request from a cloud payment client on a cloud application server, wherein the payment interface calling request is used for requesting to call a payment interface of the payment application client located on a cloud application client side so as to pay an order in the cloud payment client; and sending the payment interface calling request to the cloud application client so as to call a payment interface of the payment application client to pay the order.

According to a second aspect of the present disclosure, there is provided an order payment method implemented on a cloud application client, the method comprising: the method comprises the steps of obtaining a payment interface calling request from a cloud application server, wherein the payment interface calling request is used for requesting to call a payment interface of a payment application client side located on a cloud application client side so as to pay an order in the cloud payment client side in the cloud application server; confirming whether the payment interface calling request is legal or not; in response to the payment interface invocation request being legitimate, invoking a payment interface of the payment application client to pay for the order.

According to a third aspect of the present disclosure, there is provided an order payment apparatus implemented on a cloud application server and comprising: a request acquisition module configured to acquire a payment interface call request from a cloud payment client on a cloud application server, wherein the payment interface call request is used for requesting to call a payment interface of a payment application client located on a cloud application client side so as to pay an order in the cloud payment client; a request sending module configured to send the payment interface call request to the cloud application client in order to invoke a payment interface of the payment application client to pay for the order.

According to a fourth aspect of the present disclosure, there is provided an order payment apparatus implemented on a cloud application client and comprising: a request receiving module configured to receive a payment interface call request from a cloud application server, the payment interface call request being for requesting a call to a payment interface of a payment application client located on a cloud application client side in order to pay for an order in a cloud payment client in the cloud application server; a request validation module configured to validate whether the payment interface invocation request is legitimate; an interface invocation module configured to invoke a payment interface of a payment application client to make payment for the order in response to the payment interface invocation request being legitimate.

According to a fifth aspect of the present disclosure, there is provided an order payment system comprising a first order payment device and a second order payment device, wherein the first order payment device comprises the order payment device according to the third aspect of the present disclosure, and the second order payment device comprises the order payment device according to the fourth aspect of the present disclosure.

According to a sixth aspect of the present disclosure, there is provided a computing device comprising a processor; and a memory configured to have computer-executable instructions stored thereon that, when executed by the processor, perform any of the order payment methods described above.

According to a seventh aspect of the present disclosure, there is provided a computer-readable storage medium storing computer-executable instructions that, when executed, perform any of the order payment methods described above.

In the order payment method, the order payment device and the order payment system claimed by the disclosure, the call of the cloud payment client in the cloud application server to the payment interface of the payment application client is forwarded to the local cloud application client, so that the call of the payment interface of the payment application client is realized, the safety problem caused by the fact that the payment application client is deployed at the cloud server is avoided, the service logic and the payment logic of the existing application (namely, cloud application) installed on the cloud server do not need to be changed, and the cost of application redevelopment is saved. Moreover, since no changes are made to the cloud application business logic and the payment logic, the user can experience the same payment experience as the local application in the cloud application environment.

These and other advantages of the present disclosure will become apparent from and elucidated with reference to the embodiments described hereinafter.

Drawings

Embodiments of the present disclosure will now be described in more detail and with reference to the accompanying drawings, in which:

fig. 1 illustrates an exemplary application scenario in which a technical solution according to an embodiment of the present disclosure may be implemented;

FIG. 2 illustrates a schematic flow diagram of an order payment method according to one embodiment of the present disclosure;

FIG. 3 illustrates a schematic flow chart diagram of an order payment method according to another embodiment of the present disclosure;

FIG. 4 illustrates a schematic flow chart diagram of an order payment method according to yet another embodiment of the present disclosure;

FIG. 5 illustrates a schematic flow chart diagram of an order payment method according to yet another embodiment of the present disclosure;

FIG. 6 illustrates an exemplary block diagram of an order payment device according to one embodiment of the present disclosure;

FIG. 7 illustrates an exemplary block diagram of an order payment device according to another embodiment of the present disclosure;

FIG. 8 illustrates an exemplary block diagram of an order payment system according to one embodiment of the present disclosure;

FIG. 9 illustrates an exemplary flow diagram for order payment with an order payment system according to one embodiment of the present disclosure;

FIG. 10 illustrates an exemplary architecture diagram of an order payment system according to one embodiment of the present disclosure; and

fig. 11 illustrates an example system that includes an example computing device that represents one or more systems and/or devices that may implement the various techniques described herein.

Detailed Description

The following description provides specific details of various embodiments of the disclosure so that those skilled in the art can fully understand and practice the various embodiments of the disclosure. It is understood that aspects of the disclosure may be practiced without some of these details. In some instances, well-known structures or functions are not shown or described in detail in this disclosure to avoid obscuring the description of the embodiments of the disclosure by these unnecessary descriptions. The terminology used in the present disclosure should be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a particular embodiment of the present disclosure.

First, some terms referred to in the embodiments of the present application are explained so that those skilled in the art can understand that:

cloud application: the working principle of cloud application is a novel application that the using mode of local installation and local operation of traditional software is changed into a service of instant taking and using, and a remote server cluster is connected and controlled through the internet or a local area network to complete service logic or operation tasks. The main carrier of the cloud application is internet technology, and is shown in the form of a thin client or a smart client.

Cloud game: under the condition of cloud computing, a game is operated on a server or a server cluster at the cloud end, a picture code generated by rendering is compressed and streamed to a client through a network, and the picture code is displayed to a user at the client in a video streaming mode. And instructions and signals operated by the user at the client are transmitted to the cloud server through the network, and then the next frame of picture is calculated and rendered according to the operation feedback of the user and is pushed to the client, so that a closed loop is formed. Generally speaking, in the running environment of the cloud game, the client does not need to perform any game software installation, logic operation, rendering and the like, but only plays the video and feeds back the operation instruction of the user, and all the computations are performed at the cloud end.

The cloud application server: a cloud server on which a cloud application (e.g., cloud gaming software) is installed.

The cloud application client side: the system is generally installed on a local terminal used by a user, and is used for receiving pictures rendered by a cloud server and displaying the pictures to the user in a video stream mode; and receiving the operation of the user, and feeding back the operation to the cloud server to render the next frame of picture.

In-game purchase: refers to a consumer purchase made within the game, including but not limited to the purchase of virtual accessories, the skin of a game character, props, etc. Currently, general game software can be purchased without installing separate software and opening a third party's web page.

Payment program client: refers to software, APPs, software development kits, etc. that may pay third party merchants. Payment means, such as credit cards, or micro-letter change, online electronic money, have typically been bound inside the payment program client. Common payment program clients include pay-for-treasure, WeChat payments, and the like.

The cloud payment client side comprises: typically a payment application in a cloud application, for implementing payment logic inside the cloud application, e.g. in-game payment logic when participating in-game item purchases.

Fig. 1 illustrates an exemplary application scenario 100 in which a technical solution according to an embodiment of the present disclosure may be implemented. As shown in fig. 1, the application scenario 100 includes a terminal 110, a server 120, a server 130, and a network 140. For clarity, the following description will be described with respect to a cloud application as an example of a cloud game, but the present application is not limited to the similarity of cloud applications.

The terminal 110 may be an electronic device on which various applications are installed to provide various services, and the electronic device may be, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, and the like. As an example, a cloud application client, such as a cloud game client, is installed in the terminal 110.

The server 120 may communicate with the terminal 110 through the Network 140, and may be a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a web service, cloud communication, a middleware service, a domain name service, a security service, a CDN (Content Delivery Network), and a big data and artificial intelligence platform. In the present application, a cloud application (e.g., game instance) may be installed in the server 120, and thus the server 120 is also a cloud application server, such as a cloud game server.

Server 130 may be communicatively coupled with server 120, optionally via network 140. The server 130 may be a backend server of a cloud application (e.g., game instance), which is typically a server, device, and/or any other suitable computing device or computing system of a cloud application (e.g., game instance) provider. The server 130 may be an independent physical server, may be a server cluster or a distributed system including a plurality of physical servers, and may be a cloud server similar to the server 120.

Servers

120 and 130 may be deployed together or remotely from each other. For example, the server 130 may be operated by a cloud platform provider, while the server 120 may be operated by an independent third party, although this is not a limitation.

The network 140 may be, for example, a Wide Area Network (WAN), a Local Area Network (LAN), a wired or wireless network, a public telephone network, an intranet, or any other type of network known to those skilled in the art.

As an example, when a user operates a game instance installed on the cloud game server 120 to play a game through a cloud game client on the terminal 110, an in-game purchase behavior such as purchasing props may be initiated in the game instance, and a game payment client (which is also typically located in the game instance) supporting the in-game purchase behavior on the cloud game server 120 may interact with the game backend server 130, so as to obtain an order for this in-game purchase for performing a subsequent payment process.

In this case, a method may be first implemented at the cloud game server 120 of obtaining a payment interface call request from a cloud payment client (i.e., a game payment client) on the cloud game server, where the payment interface call request is for requesting a call to a payment interface of a payment application client (e.g., a payment program of a paypal, a WeChat payment program, etc.) located at the cloud game client side, in order to pay at the order; then, the payment interface call request is sent to the cloud game client on the terminal 110, so as to call the payment interface of the payment application client to pay for the order. Optionally, on the cloud game client side of the terminal 110, a payment interface call request from the cloud game server 120 may be obtained; and then, in the case that the payment interface calling request is confirmed to be legal, calling a payment interface of the payment application client to complete the payment of the order.

It should be noted that the scenario described above is only one example in which the embodiments of the present disclosure may be implemented, and is not limiting.

Fig. 2 illustrates a schematic flow diagram of an order payment method 200 according to one embodiment of the present disclosure. The method 200 may be implemented, for example, as a component, program module, or process on the server 120 (i.e., cloud application server) shown in fig. 1. As shown in fig. 2, the method 200 may include the following steps.

In step 201, a payment interface call request from a cloud payment client on a cloud application server is obtained, where the payment interface call request is used to request to call a payment interface of a payment application client located on a cloud application client side, so as to pay an order in the cloud payment client. As described with reference to fig. 1, a cloud application server is a server running a cloud application (e.g., an instance of a shopping application, a game instance, etc.), which is a cloud server. The cloud payment client is typically a payment application program in the cloud application, but may also exist independently of the cloud application, and is used for implementing payment logic inside the cloud application, for example, the payment logic inside the game when the in-game item is purchased. The payment interface of the payment application client, such as a common payment program for a payment instrument, a WeChat payment program, etc., may be invoked to complete the actual payment for the order.

The order is typically obtained by the following process. First, the cloud payment client sends a purchase request of a user in a cloud application to a cloud payment server corresponding to the cloud payment client, which is a payee of an order, typically a provider of the cloud application (e.g., a game provider, which obtains an income by selling items in the game). And after receiving the purchase request, the cloud payment server performs signature, encryption, order generation and the like by using the signature of the cloud payment server, and then sends the order back to the cloud payment client.

In step 202, the payment interface call request is sent to the cloud application client so as to call a payment interface of the payment application client to pay for the order. The cloud application client is typically installed on a local terminal used by the user.

In some embodiments, the address of the cloud application client, for example, a user account of the cloud application client, an IP (internet protocol) address of a terminal where the cloud application client is located, a port number, and the like, may be obtained by querying the payment status database. And then, sending the payment interface calling request to the cloud application client according to the address of the cloud application client.

In some embodiments, prior to sending the payment interface call request to the cloud application client, it may be determined whether the payment application client is available on the cloud application client side. Sending the payment interface call request to the cloud application client if the payment application client is available on the cloud application client side. The payment application client being available at the cloud application client side may include: the payment application client exists on the cloud application client side; and/or the cloud application client has the right to call the payment interface of the payment application client. The presence of the payment application client on the cloud application client side means that the payment application client is already installed on the cloud application client side, e.g. both located on the same terminal. As an example, whether the payment application client is available on the cloud application client side may also be determined by querying a payment status database.

Alternatively, the payment status database may be located on the cloud application server, and may be a stand-alone program or a data table entry, and is used to store information related to applications and payments running on the cloud application server, and to store collected addresses of cloud application clients and statuses of the payment application clients (e.g., whether the payment application clients are available on the cloud application client side). For example, each start and stop of a game on the cloud application server requires synchronization of this information to the payment status database.

In some embodiments, the payment interface call request may be preprocessed while being sent to the cloud application client, the preprocessing including at least one of encryption and encapsulation; and then sending the preprocessed payment interface calling request to the cloud application client. Encryption can ensure the security of the payment interface calling request in the transmission process and prevent the payment interface calling request from being tampered. The encapsulation may be performed as needed, for example, the Transmission mode of the payment interface invocation request may be changed by encapsulation, for example, from TCP (Transmission control Protocol) to UDP (User Datagram Protocol), so as to save Transmission resources.

By the method, the call of the cloud payment client in the cloud application server to the payment interface of the payment application client is forwarded to the cloud application client locally, so that the call of the payment interface of the payment application client is realized, the safety problem caused by the fact that the payment application client is deployed on the cloud server is avoided, the service logic and the payment logic of the existing application (namely, cloud application) installed on the cloud server do not need to be changed, and the cost of application redevelopment is saved. Moreover, since no changes are made to the cloud application business logic and the payment logic, the user can experience the same payment experience as the local application in the cloud application environment.

Fig. 3 illustrates a schematic flow diagram of an order payment method 300 according to one embodiment of the present disclosure. The method 300 may likewise be implemented, for example, as a component, program module, or process on the server 120 (i.e., cloud application server) shown in fig. 1. As shown in FIG. 3, the method 300 may include the following steps 301-304, wherein the steps 301 and 302 are similar to the steps 201-202 and will not be repeated here.

In step 303, a payment result returned after the payment interface of the payment application client is called to pay the order is obtained from the cloud application client. After the payment operation is completed, the payment application client returns a payment result to the cloud application client calling the payment interface of the payment application client regardless of the success or failure of the payment. The cloud application client further returns the payment result to the cloud application server.

In step 304, the payment result information is returned to the cloud payment client, so that the cloud payment client and the cloud payment server verify the payment result. As described above, the order is generated by the cloud payment server in response to the purchase request sent by the cloud payment client. And the cloud payment service terminal checks and analyzes the received payment result so as to confirm the payment result. And then, the cloud payment server side can return the payment result to the cloud payment client side so as to transmit the payment result to the cloud application client side to be presented to the user.

By the method 300 of the embodiment of the disclosure, the call of the cloud payment client in the cloud application server to the payment interface of the payment application client is forwarded to the cloud application client locally, so that the call of the payment interface of the payment application client is realized, the security problem caused by the payment application client being deployed on the cloud server is avoided, the service logic and the payment logic of the existing application (namely, cloud application) installed on the cloud server do not need to be changed, and the cost of application redevelopment is saved.

Fig. 4 illustrates a schematic flow diagram of an order payment method 400 according to one embodiment of the present disclosure. The method 400 may be implemented, for example, as a component, program module, or process on the terminal 110 shown in fig. 1, particularly on a cloud application client on the terminal 110. As shown in fig. 4, the method 400 may include the following steps.

In step 401, a payment interface call request from a cloud application server is obtained, where the payment interface call request is used to request to call a payment interface of a payment application client located on a cloud application client side, so as to pay an order in the cloud payment client in the cloud application server. In the case that the payment interface invocation request is encrypted or encapsulated, the payment interface invocation request also needs to be decrypted and parsed. As described with reference to fig. 1, a cloud application server is a server running a cloud application (e.g., an instance of a shopping application, a game instance, etc.), which is a cloud server. The cloud payment client is typically a payment application program in the cloud application, but may also exist independently of the cloud application, and is used for implementing payment logic inside the cloud application, for example, the payment logic inside the game when the in-game item is purchased. The payment interface of the payment application client, such as a common payment program for a payment instrument, a WeChat payment program, etc., may be invoked to complete the actual payment for the order.

At step 402, it is confirmed whether the payment interface invocation request is legitimate. In some embodiments, it may be confirmed whether the current status data about the order matches the reserved status data on the cloud application client, and if so, that the payment interface invocation request is legitimate. The status data may include, for example, one or more of the provider of the order (which is typically the provider of the cloud application), the purchaser to whom the order is directed (e.g., the purchaser of the game item), and the payment rights for the order. The payment rights for an order refer, for example, to whether the invocation of the payment interface of the payment application client for the order is allowed. As an example, the reserved status data may reflect that the invocation of the payment interface of the payment application client for an order of the game item class is not allowed, possibly because the use of the payment application client for payment is not supported for commercial competition, or the invocation of the payment interface of the payment application client is prohibited for the purpose of prohibiting an indulgent game or for the provision of certain institutions or departments.

In some embodiments, the reserved state data may be synchronized by the cloud application server to the cloud application client. As an example, the reserved state data may be stored in a call state database on the cloud application client, as described later with reference to fig. 10.

In step 403, in response to the payment interface invocation request being legitimate, the payment interface of the payment application client is invoked to make payment for the order. When the payment application client executes payment operation, the payment application client can require authentication with a user, and the authentication can be realized by using a password, a fingerprint, face recognition and other modes. And after the identity authentication is passed, the payment application client sends the payment request to a payment application server corresponding to the payment application client for verification, processing and the like. It is to be understood that, in the case that the payment application client is a payment program of a common payment treasure, a WeChat payment program, and the like, the payment application server corresponding to the payment application client may be, for example, a server of the payment program of the payment treasure, a server of the WeChat payment program, and the like. After verification and processing, the payment application server side executes operations such as the amount of the verified and cancelled order and then returns a payment result to the payment application client side.

By the method 400 of the embodiment of the disclosure, the call of the cloud payment client in the cloud application server to the payment interface of the payment application client is forwarded to the cloud application client for local processing, so that the call of the payment interface of the payment application client is realized, the security problem caused by the deployment of the payment application client on the cloud server is avoided, the service logic and the payment logic of the existing application (namely, cloud application) installed on the cloud server do not need to be changed, and the cost of application redevelopment is saved. Moreover, since no changes are made to the cloud application business logic and the payment logic, the user can experience the same payment experience as the local application in the cloud application environment.

Fig. 5 illustrates a schematic flow diagram of an order payment method 500 according to one embodiment of the present disclosure. The method 500 may be implemented, for example, as a component, program module or process on the side of the terminal 110 shown in fig. 1, in particular on a cloud application client on the terminal 110. As shown in fig. 4, the method 400 may include the following steps 501-505, wherein the steps 501-503 are similar to the steps 301-303 and will not be repeated here.

At step 504, payment results are obtained from the payment application client. As described with reference to step 403, the payment result is a response of the payment application server corresponding to the payment application client to a payment request initiated by the payment application client when its payment interface is invoked to pay for the order.

In step 505, the payment result is sent to a cloud application server, so that a cloud payment client and a cloud payment server in the cloud application server verify the payment result, wherein the order is generated by the cloud payment server in response to a purchase request of the cloud payment client. And the cloud payment server side checks and analyzes the received payment result and confirms the payment result. And then, the cloud payment server side can return the payment result to the cloud payment client side so as to transmit the payment result to the cloud application client side to be presented to the user.

By the method 500 of the embodiment of the disclosure, the call of the cloud payment client in the cloud application server to the payment interface of the payment application client is forwarded to the cloud application client for local processing, so that the call of the payment interface of the payment application client is realized, the security problem caused by the fact that the payment application client is deployed on the cloud server is avoided, the service logic and the payment logic of the existing application (namely, cloud application) installed on the cloud server do not need to be changed, and the cost of application redevelopment is saved.

FIG. 6 illustrates an exemplary block diagram of an order payment device 600 according to one embodiment of the present disclosure. The order payment apparatus 600 may be implemented on a cloud application server. As shown in fig. 6, the order payment apparatus 600 includes a request obtaining module 601 and a request sending module 602. Optionally, the order payment apparatus 600 may further include a result obtaining module 603 and a result returning module 604.

The request obtaining module 601 is configured to obtain a payment interface call request from a cloud payment client on a cloud application server, where the payment interface call request is used to request to call a payment interface of a payment application client located on a cloud application client side, so as to make payment for an order in the cloud payment client. A cloud application server is a server on which a cloud application (e.g., an instance of a shopping application, a game instance, etc.) is installed, which is a cloud server. The cloud payment client is typically a payment application program in the cloud application, but may also exist independently of the cloud application, and is used for implementing payment logic inside the cloud application, for example, the payment logic inside the game when the in-game item is purchased. The payment interface of the payment application client, such as a common payment program for a payment instrument, a WeChat payment program, etc., may be invoked to complete the actual payment for the order.

The request sending module 602 is configured to send the payment interface call request to the cloud application client in order to invoke the payment interface of the payment application client to pay for the order. The cloud application client is typically installed on a local terminal used by the user.

The result obtaining module 603 is configured to obtain, from the cloud application client, a payment result returned after the payment interface of the payment application client is invoked to pay the order. After the payment operation is completed, the payment application client returns a payment result to the cloud application client calling the payment interface of the payment application client regardless of the success or failure of the payment. The cloud application client further returns the payment result to the cloud application server.

The result returning module 604 is configured to return the payment result information to the cloud payment client so that the cloud payment client and the cloud payment server verify the payment result, wherein the order is generated by the cloud payment server in response to the purchase request of the cloud payment client. The order is generated by the cloud payment server in response to a purchase request of the cloud payment client. And the cloud payment server side checks and analyzes the received payment result and confirms the payment result. And then, the cloud payment server side can return the payment result to the cloud payment client side so as to transmit the payment result to the cloud application client side to be presented to the user.

FIG. 7 illustrates an exemplary block diagram of an order payment device 700 according to one embodiment of the present disclosure. The order payment apparatus 700 may be implemented on a cloud application client. As shown in fig. 7, the order payment apparatus 700 includes a request receiving module 701, a request confirming module 702, and an interface calling module 703. Optionally, the order payment apparatus 700 may further include a result receiving module 704 and a result sending module 705.

The request receiving module 701 is configured to receive a payment interface call request from the cloud application server, where the payment interface call request is used to request a call to a payment interface of a payment application client located on the cloud application client side, so as to pay for an order in a cloud payment client in the cloud application server. In the case that the payment interface invocation request is encrypted or encapsulated, the payment interface invocation request also needs to be decrypted and parsed.

The request validation module 702 is configured to validate whether the payment interface invocation request is legitimate. In some embodiments, the request validation module 702 is configured to validate whether the current state data for the order matches the reserved state data on the cloud application client, and if so, validate that the payment interface invocation request is legitimate.

The interface invocation module 703 is configured to invoke the payment interface of the payment application client to make payment for the order in response to the payment interface invocation request being legitimate.

The result receiving module 704 is configured to receive a payment result from a payment application client, the payment result being a response by a payment application server corresponding to the payment application client to a payment request initiated by the payment application client when its payment interface is invoked to pay for the order.

The result sending module 705 is configured to send the payment result to the cloud application server, so that the cloud payment client and the cloud payment server in the cloud application server verify the payment result, wherein the order is generated by the cloud payment server in response to a purchase request of the cloud payment client.

Fig. 8 illustrates an exemplary block diagram of an order payment system 800 including a first order payment device 801 and a second order payment device 802 according to one embodiment of the present disclosure. The first order payment apparatus 801 may be the order payment apparatus 600 described with reference to fig. 6, and the second order payment apparatus 802 may be the order payment apparatus 700 described with reference to fig. 7.

Fig. 9 illustrates an exemplary flow diagram for order payment using the order payment system 800 according to one embodiment of the present disclosure. As shown in fig. 9, at step 901, a user initiates a purchase request, for example, in a cloud application installed in a cloud application server. At step 902, the cloud payment client sends a purchase request of a user to a cloud payment server corresponding to the cloud payment client. The cloud payment server is generally deployed on a cloud server, and is different from a cloud application server. After receiving the purchase request, the cloud payment server signs the purchase request with the signature of the cloud payment server, executes operations such as order generation and encryption, and then sends the order back to the cloud payment client in step 903. And the cloud payment client sends a payment interface calling request according to the received order so as to call the payment interface of the payment application client. At step 904, a payment interface call request is sent to a first order payment device. The first order payment device is located on the cloud application server, and after receiving the payment interface call request, the first order payment device may query the payment status database to obtain an address of the cloud application client, such as a user account of the cloud application client, an IP (internet protocol) address of a terminal where the cloud application client is located, a port number, and the like, and determine whether the payment application client is available on the cloud application client side. If the request is available, the payment interface call request is sent to the cloud application client according to the address of the cloud application client after being preprocessed by packaging, encryption and the like at step 905.

After the cloud application client receives the payment interface calling request, the second order payment device on the cloud application client performs decryption and analysis processing to determine whether the payment interface calling request is legal, for example, to determine that the current state data of the order is matched with the state data reserved in the calling state database on the cloud application client. If the payment interface invocation request is validated, the payment interface of the payment application client is invoked to make payment for the order at step 906. When the payment application client performs the payment operation, the payment application client may request authentication with the user in step 907, where the authentication may be performed by using a password, a fingerprint, face recognition, and the like. After the authentication is passed, the payment application client sends the payment request to the payment application server corresponding to the payment application client for verification, processing, and the like in step 908.

At step 909, the payment application server performs the operations of checking, processing, and the like, and then returns the payment result to the payment application client. At step 910, the payment application client returns the payment result to the second order payment device on the application client. At step 911, the second order payment device processes the returned payment result, queries the call status database to obtain the cloud application server connected to the cloud payment client and information related to the cloud application, and returns the payment result to the cloud application server after encryption, encapsulation and the like. At step 912, the first order payment device on the cloud application server decrypts and parses the payment result and returns the payment result to the cloud payment client. At step 913, the cloud payment client sends the payment result to the cloud payment server for verification. And the cloud payment server side checks and analyzes the received payment result and confirms the payment result. After confirmation, the cloud payment server may return the payment result to the cloud payment client for transmission to the cloud application client for presentation to the user at step 914.

FIG. 10 illustrates an exemplary architecture diagram of an order payment system according to one embodiment of the present disclosure. As shown in fig. 10, the cloud application server includes a payment status database, a cloud application (which may include a cloud payment client), and a first order payment device. The cloud game client comprises a calling state database and a second order payment device. The invocation state database may maintain information synchronization with the payment state database. The first order payment device and the second order payment device may have a communication connection, the communication connection may use an encrypted protocol such as HTTPS, and the communication connection may also use an existing channel established between the cloud application client and the cloud application server. The information is updated synchronously, that is, the payment state information of the first order payment device and the second order payment device must be synchronized strongly and consistently. The payment state database is located in the cloud application server, can be an independent program, and can also be a data table entry, and is used for storing information related to running applications and payments on the cloud application server, and storing collected addresses of the cloud application client and states of the payment application client. For example, each start and stop of a game on the cloud application server requires synchronization of this information to the payment status database. The calling state database is located in the cloud application client, can be an independent program, and can also be a data table item, and is used for storing payment related information on the cloud application client and synchronizing the information to the payment state database. For example, if a new payment application client is installed and authorized, or an existing payment application client is deleted or de-authorized, the information needs to be synchronized to the call state database, and then the call state database synchronizes the information to the payment state database. The first order payment device can only inquire the data in the payment state database, and the second order payment device can only inquire the data in the calling state database, so that the safety of the data in the payment state database and the calling state database is ensured.

Fig. 11 illustrates an example system 1100 that includes an example computing device 1110 that represents one or more systems and/or devices that can implement the various techniques described herein. Computing device 1110 may be, for example, a server of a service provider, a device associated with a server, a system on a chip, and/or any other suitable computing device or computing system. Both of the order payment apparatuses 600 and 700 described above with reference to fig. 6 and 7 may take the form of a computing device 1110. Alternatively, both order payment devices 600 and 700 may be implemented as computer programs in the form of order payment applications 1116.

The example computing device 1110 as illustrated includes a processing system 1111, one or more computer-readable media 1112, and one or more I/O interfaces 1113 communicatively coupled to each other. Although not shown, the computing device 1110 may also include a system bus or other data and command transfer system that couples the various components to one another. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures. Various other examples are also contemplated, such as control and data lines.

Processing system 1111 represents functionality to perform one or more operations using hardware. Thus, the processing system 1111 is illustrated as including hardware elements 1114 that can be configured as processors, functional blocks, and the like. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. Hardware elements 1114 are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, a processor may be comprised of semiconductor(s) and/or transistors (e.g., electronic Integrated Circuits (ICs)). In such a context, processor-executable instructions may be electronically-executable instructions.

Computer-readable medium 1112 is illustrated as including memory/storage 1115. Memory/storage 1115 represents memory/storage capacity associated with one or more computer-readable media. The memory/storage 1115 may include volatile media (such as Random Access Memory (RAM)) and/or nonvolatile media (such as Read Only Memory (ROM), flash memory, optical disks, magnetic disks, and so forth). Memory/storage 1115 may include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., flash memory, a removable hard drive, an optical disk, and so forth). Computer-readable medium 1112 may be configured in various other ways as further described below.

The one or more I/O interfaces 1113 represent functionality that allows a user to enter commands and information to the computing device 1110 using various input devices and optionally also allows information to be presented to the user and/or other components or devices using various output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone (e.g., for voice input), a scanner, touch functionality (e.g., capacitive or other sensors configured to detect physical touch), a camera (e.g., motion that may not involve touch may be detected as gestures using visible or invisible wavelengths such as infrared frequencies), and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, a haptic response device, and so forth. Thus, the computing device 1110 may be configured in various ways as further described below to support user interaction.

Computing device 1110 also includes an order payment application 1116. The order payment application 1116 may be, for example, a software instance of the order payment apparatus 600 or 700, and in combination with other elements in the computing device 1110 implement the techniques described herein.

Various techniques may be described herein in the general context of software hardware elements or program modules. Generally, these modules include routines, programs, objects, elements, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The terms "module," "functionality," and "component" as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of computing platforms having a variety of processors.

An implementation of the described modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can include a variety of media that can be accessed by computing device 1110. By way of example, and not limitation, computer-readable media may comprise "computer-readable storage media" and "computer-readable signal media".

"computer-readable storage medium" refers to a medium and/or device, and/or a tangible storage apparatus, capable of persistently storing information, as opposed to mere signal transmission, carrier wave, or signal per se. Accordingly, computer-readable storage media refers to non-signal bearing media. Computer-readable storage media include hardware such as volatile and nonvolatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer-readable instructions, data structures, program modules, logic elements/circuits or other data. Examples of computer readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage devices, tangible media, or an article of manufacture suitable for storing the desired information and accessible by a computer.

"computer-readable signal medium" refers to a signal-bearing medium configured to transmit instructions to the hardware of computing device 1110, such as via a network. Signal media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave, data signal or other transport mechanism. Signal media also includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

As previously described, the hardware elements 1114 and the computer-readable media 1112 represent instructions, modules, programmable device logic, and/or fixed device logic implemented in hardware form that may be used in some embodiments to implement at least some aspects of the techniques described herein. The hardware elements may include integrated circuits or systems-on-chips, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), Complex Programmable Logic Devices (CPLDs), and other implementations in silicon or components of other hardware devices. In this context, a hardware element may serve as a processing device that performs program tasks defined by instructions, modules, and/or logic embodied by the hardware element, as well as a hardware device for storing instructions for execution, such as the computer-readable storage medium described previously.

Combinations of the foregoing may also be used to implement the various techniques and modules described herein. Thus, software, hardware, or program modules and other program modules may be implemented as one or more instructions and/or logic embodied on some form of computer-readable storage medium and/or by one or more hardware elements 1114. The computing device 1110 may be configured to implement particular instructions and/or functions corresponding to software and/or hardware modules. Thus, implementing modules as modules executable by the computing device 1110 as software may be implemented at least partially in hardware, for example, using the processing system's computer-readable storage media and/or hardware elements 1114. The instructions and/or functions may be executable/operable by one or more articles of manufacture (e.g., one or more computing devices 1110 and/or processing systems 1111) to implement the techniques, modules, and examples described herein.

In various embodiments, computing device 1110 may assume a variety of different configurations. For example, the computing device 1110 may be implemented as a computer-like device including a personal computer, a desktop computer, a multi-screen computer, a laptop computer, a netbook, and so forth. The computing device 1110 may also be implemented as a mobile device-like device including mobile devices such as mobile telephones, portable music players, portable gaming devices, tablet computers, multi-screen computers, and the like. Computing device 1110 may also be implemented as a television-like device that includes devices with or connected to generally larger screens in casual viewing environments. These devices include televisions, set-top boxes, game consoles, and the like.

The techniques described herein may be supported by these various configurations of computing device 1110 and are not limited to specific examples of the techniques described herein. Functionality may also be implemented in whole or in part on "cloud" 1120 using a distributed system, such as through platform 1122 described below.

Cloud 1120 includes and/or is representative of platform 1122 for resources 1124. Platform 1122 abstracts underlying functionality of hardware (e.g., servers) and software resources of cloud 1120. Resources 1124 can include applications and/or data that can be used when executing computer processes on servers remote from computing device 1110. Resources 1124 may also include services provided over the internet and/or over a subscriber network such as a cellular or Wi-Fi network.

The platform 1122 may abstract resources and functionality to connect the computing device 1110 with other computing devices. The platform 1122 may also be used to abstract a hierarchy of resources to provide a corresponding level of hierarchy of encountered demand for the resources 1124 implemented via the platform 1122. Thus, in interconnected device embodiments, implementation of functions described herein may be distributed throughout the system 1100. For example, the functionality may be implemented in part on the computing device 1110 and by the platform 1122 that abstracts the functionality of the cloud 1120.

It will be appreciated that embodiments of the disclosure have been described with reference to different functional units for clarity. However, it will be apparent that the functionality of each functional unit may be implemented in a single unit, in a plurality of units or as part of other functional units without departing from the disclosure. For example, functionality illustrated to be performed by a single unit may be performed by a plurality of different units. Thus, references to specific functional units are only to be seen as references to suitable units for providing the described functionality rather than indicative of a strict logical or physical structure or organization. Thus, the present disclosure may be implemented in a single unit or may be physically and functionally distributed between different units and circuits.

It will be understood that, although the terms first, second, third, etc. may be used herein to describe various devices, elements, components or sections, these devices, elements, components or sections should not be limited by these terms. These terms are only used to distinguish one device, element, component or section from another device, element, component or section.

Although the present disclosure has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present disclosure is limited only by the accompanying claims. Additionally, although individual features may be included in different claims, these may possibly advantageously be combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. The order of features in the claims does not imply any specific order in which the features must be worked. Furthermore, in the claims, the word "comprising" does not exclude other elements, and the words "a" or "an" do not exclude a plurality. Reference signs in the claims are provided merely as a clarifying example and shall not be construed as limiting the scope of the claims in any way.

Claims

1. An order payment method implemented on a cloud application server, the method comprising:

the method comprises the steps of obtaining a payment interface calling request from a cloud payment client on a cloud application server, wherein the payment interface calling request is used for requesting to call a payment interface of the payment application client located on a cloud application client side so as to pay an order in the cloud payment client;

and sending the payment interface calling request to the cloud application client so as to call a payment interface of the payment application client to pay the order.

2. The method of claim 1, further comprising:

obtaining a payment result returned after a payment interface of the payment application client is called to pay the order from a cloud application client;

and returning the payment result information to the cloud payment client so that the cloud payment client and the cloud payment server verify the payment result, wherein the order is generated by the cloud payment server in response to a purchase request of the cloud payment client.

3. The method of claim 1, wherein sending the payment interface invocation request to the cloud application client comprises:

determining whether the payment application client is available on the cloud application client side;

in response to the payment application client being available on the cloud application client side, sending the payment interface call request to the cloud application client.

4. The method of claim 3, wherein the payment application client is available on the cloud application client side, including one or more of:

the payment application client exists on the cloud application client side;

the cloud application client has the authority to call the payment interface of the payment application client.

5. The method of claim 1, wherein sending the payment interface invocation request to the cloud application client comprises:

invoking a request pre-processing on the payment interface, the pre-processing comprising at least one of encryption and packaging;

and sending the preprocessed payment interface calling request to the cloud application client.

6. An order payment method implemented on a cloud application client, the method comprising:

the method comprises the steps of obtaining a payment interface calling request from a cloud application server, wherein the payment interface calling request is used for requesting to call a payment interface of a payment application client side located on a cloud application client side so as to pay an order in the cloud payment client side in the cloud application server;

confirming whether the payment interface calling request is legal or not;

in response to the payment interface invocation request being legitimate, invoking a payment interface of the payment application client to pay for the order.

7. The method of claim 6, further comprising:

obtaining a payment result from a payment application client, wherein the payment result is a response of a payment application server corresponding to the payment application client to a payment request initiated by the payment application client, and the payment request is initiated by the payment application client when a payment interface of the payment application client is called to pay the order;

and sending the payment result to a cloud application server so that a cloud payment client and a cloud payment server in the cloud application server verify the payment result, wherein the order is generated by the cloud payment server in response to a purchase request of the cloud payment client.

8. The method of claim 6, wherein confirming whether the payment interface invocation request is legitimate comprises:

in response to the current state data regarding the order matching the reserved state data on the cloud application client, confirming that the payment interface invocation request is legitimate.

9. The method of claim 8, wherein the status data comprises one or more of a provider of the order, a purchaser to whom the order is directed, and payment rights for the order.

10. The method of claim 8, wherein the reserved status data is synchronized by a cloud application server to a cloud application client.

11. An order payment apparatus implemented on a cloud application server and comprising:

a request acquisition module configured to acquire a payment interface call request from a cloud payment client on a cloud application server, wherein the payment interface call request is used for requesting to call a payment interface of a payment application client located on a cloud application client side so as to pay an order in the cloud payment client;

a request sending module configured to send the payment interface call request to the cloud application client in order to invoke a payment interface of the payment application client to pay for the order.

12. An order payment apparatus implemented on a cloud application client and comprising:

a request receiving module configured to receive a payment interface call request from a cloud application server, the payment interface call request being for requesting a call to a payment interface of a payment application client located on a cloud application client side in order to pay for an order in a cloud payment client in the cloud application server;

a request validation module configured to validate whether the payment interface invocation request is legitimate;

an interface invocation module configured to invoke a payment interface of a payment application client to make payment for the order in response to the payment interface invocation request being legitimate.

13. An order payment system includes a first order payment device and a second order payment device, wherein,

the first order payment device comprising an order payment device according to claim 11, and

the second order payment device comprises an order payment device according to claim 12.

14. A computing device comprising

A memory configured to store computer-executable instructions;

a processor configured to perform the method of any one of claims 1-10 when the computer-executable instructions are executed by the processor.

15. A computer-readable storage medium storing computer-executable instructions that, when executed, perform the method of any one of claims 1-10.