CN114897535A

CN114897535A - Payment method, device and system

Info

Publication number: CN114897535A
Application number: CN202210617791.7A
Authority: CN
Inventors: 赵红洁; 翟松涛; 童亚伟; 孔颖; 朱青杰
Original assignee: Beijing Jingdong Tuoxian Technology Co Ltd
Current assignee: Beijing Jingdong Tuoxian Technology Co Ltd
Priority date: 2022-06-01
Filing date: 2022-06-01
Publication date: 2022-08-12

Abstract

The invention discloses a payment method, a payment device and a payment system, and relates to the technical field of digital medical treatment. One embodiment of the method comprises: receiving a request for settlement by using an external system, which is sent by a client, by using a server; determining cache data matched with the client from a plurality of preset cache data; determining deduction information based on the cache data and an external system settlement strategy; and after the settlement is successful, the client sends a request carrying the deduction information of the external system to the external system for synchronous updating. The problem of abnormal settlement caused by the external settlement system due to high calling frequency of the external settlement system and low interface performance of the external settlement system is solved; the user payment experience is improved.

Description

Payment method, device and system

Technical Field

The invention relates to the technical field of digital medical treatment, in particular to a payment method, a payment device and a payment system.

Background

In some internet applications, functions are provided that require an external accounting system to account, for example, accounting on system a with the account balance of system B, which is an external accounting system with respect to system a. Based on the settlement function, the user of the internet application can complete a settlement service using an external settlement system in the application.

At present, a method for calling an external settlement system in internet application mainly directly calls an interface provided by the external settlement system, and due to the problems of high frequency of calling the external settlement system and low interface performance of the external settlement system, the problem that the external settlement system is called in the application to cause abnormal settlement is often caused; the experience of the user in making payments using the internet application is greatly affected.

Disclosure of Invention

In view of this, embodiments of the present invention provide a payment method, apparatus, and system, which can receive, by a server, a request for settlement by an external system sent by a client; determining cache data matched with the client from a plurality of preset cache data; determining deduction information based on the cache data and an external system settlement strategy; and after the settlement is successful, the client sends a request carrying the deduction information of the external system to the external system for synchronous updating. The problem of abnormal settlement caused by the external settlement system due to high calling frequency of the external settlement system and low interface performance of the external settlement system is solved; the user payment experience is improved.

To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a payment method, including: receiving a request for settlement by using a first system, which is sent by a client; the settlement request comprises payment information and target account information; determining first cache data matched with the target account information from a plurality of preset cache data; the preset plurality of cache data comprise account balances of the target account information acquired from the first system; determining withholding information corresponding to the payment information based on the first cache data, a settlement policy of the first system, and the payment information; sending the deduction information to the client; and responding to the message of successful settlement of the client, updating first cache data matched with the target account information, and sending a deduction request carrying the deduction information to the first system so that the first system updates the account balance of the target account information.

Optionally, the payment method further includes: according to the set time interval, aiming at each managed target account information, executing: sending a query request of the target account information to the first system; and receiving and caching the cache data corresponding to the target account information returned by the first system.

Optionally, after receiving a request for settlement with the first system sent by the client, the payment method further includes: determining whether the target account information has a binding relationship with the first system; and if the target account information is determined not to have the binding relationship with the first system, sending a binding message aiming at the first system to the client so that a user binds the target account information to the first system through the client.

Optionally, the payment method further includes: and under the condition that the target account information is determined not to have a binding relationship with the first system, verifying user authentication information associated with the target account information by using an authentication system, and sending a first verification result to the client, so that the client executes the step of binding the target account information to the first system under the condition that the first verification result is verified.

Optionally, the payment method further includes: sending binding information associated with the target account information to the first system under the condition that the first verification result is that the verification is passed, so that the first system verifies the target account information based on the binding information; and receiving a second verification result of the first system, and sending the second verification result to the client.

In order to achieve the above object, according to a second aspect of the embodiments of the present invention, there is provided a payment method applied to a client, including: responding to an instruction for settlement by using a first system triggered by a user, and sending a settlement request to a server; the settlement request comprises payment information and target account information; receiving deduction information corresponding to the payment information sent by a server; and settling the target account information according to the payment information and the deduction information.

Optionally, the payment method further includes: receiving a first verification request sent by a server, and displaying a user information page; and receiving user authentication information which is input by a user of the client and is associated with the target account information through the user information page.

Optionally, the payment method further includes: receiving an authentication result aiming at the user authentication information sent by the server; if the authentication result indicates that the authentication of the authentication information of the user passes, displaying a binding page of the first system; receiving binding information which is input by a user of the client and is related to the target account information of the first system through the binding first system page; sending the binding information to the server; so that the server side verifies the binding information by using the first system; and receiving a verification result of verifying the binding information sent by the server, and displaying a message indicating successful binding with the first system under the condition that the verification result is verified to pass.

To achieve the above object, according to a third aspect of an embodiment of the present invention, there is provided a payment server, including: the system comprises a receiving request module, an information determining module and a settlement request module; wherein,

the receiving request module is used for receiving a request for settlement by using a first system, which is sent by a client; the settlement request comprises payment information and target account information;

the information determining module is used for determining first cache data matched with the target account information from a plurality of preset cache data; the preset plurality of cache data comprise account balances of the target account information acquired from the first system; determining withholding information corresponding to the payment information based on the first cache data, a settlement policy of the first system, and the payment information; sending the deduction information to the client;

the settlement request module is configured to update first cache data matched with the target account information in response to a successful settlement message of the client, and send a deduction request carrying the deduction information to the first system, so that the first system updates the account balance of the target account information.

Optionally, the payment server further includes: according to the set time interval, aiming at each managed target account information, executing: sending a query request of the target account information to the first system; and receiving and caching the cache data corresponding to the target account information returned by the first system.

Optionally, after receiving a request for settlement with the first system sent by the client, the payment server further includes: determining whether the target account information and the first system have a binding relationship; and if the target account information is determined not to have the binding relationship with the first system, sending a binding message aiming at the first system to the client so that a user binds the target account information to the first system through the client.

Optionally, the payment server further includes: and under the condition that the target account information is determined not to have a binding relationship with the first system, verifying user authentication information associated with the target account information by using an authentication system, and sending a first verification result to the client, so that the client executes the step of binding the target account information to the first system under the condition that the first verification result is verified.

Optionally, the payment server further includes: sending binding information associated with the target account information to the first system under the condition that the first verification result is that the verification is passed, so that the first system verifies the target account information based on the binding information; and receiving a second verification result of the first system, and sending the second verification result to the client.

To achieve the above object, according to a fourth aspect of the embodiments of the present invention, there is provided a payment client, including: a request sending module and a payment executing module; wherein,

the sending request module is used for responding to a settlement instruction which is triggered by a user and is carried out by using a first system, and sending a settlement request to the server; the settlement request comprises payment information and target account information;

the payment execution module is used for receiving deduction information which is sent by a server and corresponds to the payment information; and settling the target account information according to the payment information and the deduction information.

Optionally, the payment client further includes: receiving a first verification request sent by a server, and displaying a user information page; and receiving user authentication information which is input by a user of the client and is associated with the target account information through the user information page.

Optionally, the payment client further includes: receiving an authentication result aiming at the user authentication information sent by the server; if the authentication result indicates that the authentication of the authentication information of the user passes, displaying a binding page of the first system; receiving binding information which is input by a user of the client and is related to the target account information of the first system through the binding first system page; sending the binding information to the server; so that the server side verifies the binding information by using the first system; and receiving a verification result of verifying the binding information sent by the server, and displaying a message indicating successful binding with the first system under the condition that the verification result is verified to pass.

To achieve the above object, according to a fifth aspect of an embodiment of the present invention, there is provided a payment system, including: a payment server as described in the third aspect and a payment client as described in the fourth aspect.

To achieve the above object, according to a sixth aspect of the embodiments of the present invention, there is provided an electronic payment device, comprising: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out a method as claimed in any one of the above payment methods.

To achieve the above object, according to a seventh aspect of embodiments of the present invention, there is provided a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method as in any one of the above payment methods.

One embodiment of the above invention has the following advantages or benefits: the method comprises the steps that a server side can be used for receiving a request for settlement by an external system, wherein the request is sent by a client side; determining cache data matched with the client from a plurality of preset cache data; determining deduction information based on the cache data and an external system settlement strategy; and after the settlement is successful, the client sends a request carrying the deduction information of the external system to the external system for synchronous updating. The problem of abnormal settlement caused by the external settlement system due to high calling frequency of the external settlement system and low interface performance of the external settlement system is solved; the user payment experience is improved.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

fig. 1 is a schematic flow chart of a payment method applied to a server according to an embodiment of the present invention;

fig. 2 is a schematic flow chart of a method applied to a client-side payment method according to an embodiment of the present invention;

FIG. 3 is a schematic flow chart illustrating interaction between a client and a server according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of a payment server according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a payment client according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of a payment system according to an embodiment of the present invention;

FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

fig. 8 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Embodiments of the present invention contemplate that the entity responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and/or privacy practices. In particular, such entities should enforce and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data is collected and/or used. Personal information from the user should be collected for legitimate and legitimate uses by the entity and not shared or sold outside of these legitimate uses. Furthermore, such acquisition/sharing should be performed after receiving user informed consent. Furthermore, such entities should consider taking any necessary steps to defend and secure access to such personal information data, and to ensure that others who have access to the personal information data comply with their privacy policies and procedures. In addition, such entities may subject themselves to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to the particular type of personal information data collected and/or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the united states, the collection or acquisition of certain health data may be governed by federal and/or state laws, such as the health insurance association and accountability act (HIPAA); while other countries may have health data subject to other regulations and policies and should be treated accordingly. Therefore, different privacy practices should be maintained for different personal data types in each country.

Regardless of the foregoing, embodiments of the present invention also contemplate embodiments in which a user may selectively prevent use or access to personal information data. That is, the present invention contemplates that hardware elements and/or software elements may be provided to prevent or block access to such personal information data. For example, in terms of accessing or storing health information, the techniques of embodiments of the present invention may be configured to allow a user to opt-in or opt-out of participating in the collection of personal information data during registration services or at any time thereafter. In another example, the user may choose not to provide certain types of health-related information. In yet another example, the user may choose to limit the length of time the health-related information is maintained or to prohibit the storage of the health-related information altogether. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to accessing or using personal information. For example, the user may be notified that their personal information data is to be accessed when the application is downloaded, and then be reminded again just before the personal information data is accessed by the application.

Furthermore, it is an object of embodiments of the present invention to manage and process personal information data with a minimum of risk of inadvertent or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting data collection and deleting data. In addition, and when applicable, including in certain health information related applications, data de-identification may be used to protect the privacy of the user. De-identification may be facilitated by removing particular identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at a city level rather than at an address level), controlling how data is stored (e.g., aggregating data among users), and/or other methods, as appropriate.

The embodiment of the invention takes a medical insurance system as an example, and the medical insurance system is taken as an external settlement system, namely a first system; it is understood that the personal information data corresponding to the medical insurance system is used in compliance with a predetermined privacy policy and/or privacy practice. Currently, each e-commerce platform generally supports online medical insurance payment, which is generally divided into multiple steps, each step requiring direct interaction with a medical insurance system. Due to the fact that the performance and the network of the medical insurance system in different areas are different, under the condition that the performance of the medical insurance system in the areas is poor, the return time of an interface of the medical insurance system is long, the requirement of a large e-commerce platform for the performance of the interface cannot be met (for example, the threshold value of the system feedback time is 50 milliseconds), and under the condition that the return time exceeds the threshold value, the e-commerce platform needs to return no information or conduct abnormal processing on the interface according to the interface, so that the corresponding function is degraded, even reported wrong, and the user cannot pay for the medical insurance online. The user experience is greatly influenced, for example, the user can see the option of paying by using the medical insurance on the item detail page, but the settlement cannot be finished due to the return of abnormal information in the settlement process, and the user may repeatedly enter the settlement page for retries for many times, so that the user experience is influenced, and the system burden is increased.

In view of this, as shown in fig. 1, an embodiment of the present invention provides a payment method applied to a server, where the method may include the following steps:

step S101: receiving a request for settlement by using a first system, which is sent by a client; the settlement request includes payment information and target account information.

Specifically, the server running the embodiment of the present invention is, for example, a server of an electronic mall, and correspondingly the client is a client of the electronic mall, and when using the client, the user may send a request for settlement by using a first system, where the first system may be an external system for settlement with respect to the application server, for example, the electronic mall system in the embodiment of the present invention is an a system, and the first system is an external system with respect to the a system, and according to an application scenario, the a system may invoke one or more external systems to implement different types of services; the first system in the embodiment of the present invention is a settlement system, for example: a medical insurance settlement system of a plurality of regional levels; according to the application scene, the medical insurance system can divide a plurality of subsystems according to administrative regions, so that services are provided for users in different regions; when a user purchases an article which can be settled by the medical insurance system by using the client, the user can select an option for settling by using the medical insurance system, and after the user selects the option, the client requests the server to settle by using the first system.

Further, the settlement request includes payment information and target account information; wherein the payment information is associated with information of the items purchased by the user, and the payment information is, for example, a payment amount calculated based on the quantity and the amount of the items; the target account information is associated with user account information for the purchased item, such as user information including a user unique identifier, a user phone number, an address, and the like.

Further, before determining that the user utilizes the first system for settlement, the binding relationship between the user and the first system needs to be authenticated.

Specifically, after receiving a request for settlement with the first system sent by the client, the method further includes: determining whether the target account information has a binding relationship with the first system; and if the target account information is determined not to have the binding relationship with the first system, sending a binding message aiming at the first system to the client so that a user binds the target account information to the first system through the client. Whether the binding relationship exists between the target account information and the first system or not can be judged by inquiring whether the associated user authentication cache information contains information of the first system or not through the server side, or an interface for determining the binding information of the first system is called, the user account information is used as a reference input interface, and whether the binding relationship exists between the target account information and the first system or not is judged according to a return value of the interface; that is, it is determined whether the account of the user is already bound to the first system.

Further, if it is determined that the target account information does not have a binding relationship with the first system (for example, the user uses the first system for settlement for the first time), sending a binding message for the first system to the client. After receiving the binding message of the first system, the client sends user authentication information to the server, and the server verifies the user authentication information (for example, real-name authentication) by using an authentication system (for example, verification is performed by an official authentication system of a third party), wherein the user authentication information comprises an identity card number of a user, biological characteristic identification information (biological characteristic information for face identification, fingerprint identification and the like) and the like; that is, when it is determined that the target account information does not have a binding relationship with the first system, the user authentication information associated with the target account information is verified by using an authentication system, and a first verification result is sent to the client, so that the client performs the step of binding the target account information to the first system when the first verification result is verified.

Further, in case the user authentication passes; receiving binding information aiming at a first system sent by a client, wherein the binding information is associated with the first system and is information which is required to be verified for the first system to use the first system, and for example, in the case that the first system is a medical insurance system, the binding information comprises a unique identifier of a medical insurance place and a medical insurance card and the like; the server calls an interface of the first system, calls a verification interface of the first system by taking the received binding information as the input of the interface, receives a verification result of the first system, determines whether the user is bound with the first system or not, and sends the verification result to the client to inform the user; that is, when the first verification result is that the verification is passed, sending binding information associated with the target account information to the first system, so that the first system verifies the target account information based on the binding information; and receiving a second verification result of the first system, and sending the second verification result to the client. Preferably, the server stores the mapping relationship between the user authentication information, the target account information, the binding information and the user information of multiple types related to the user in one or more data tables.

Step S102: determining first cache data matched with the target account information from a plurality of preset cache data; the preset plurality of cache data comprise account balances of the target account information acquired from the first system; determining withholding information corresponding to the payment information based on the first cache data, a settlement policy of the first system, and the payment information; and sending the deduction information to the client.

Specifically, the server searches first cache data matched with the target account information from preset cache data; for example: the preset cache data are medical insurance account cache data corresponding to target account information of each user of the application system A; such as the user abc's health care account information (including the health care card account balance of the user abc). That is, the preset plurality of cache data includes the account balance of the target account information acquired from the first system.

The method for the server to obtain the cache data from the first system includes two methods:

the first method comprises the following steps: according to a set time interval (such as 5 minutes, 10 minutes, 30 minutes and the like), acquiring account balance (namely cache data corresponding to the target account information) of a user associated with the first system for each user who is bound with the first system, and updating the cache data for each user; the cached data may be stored in a data storage medium such as a database, a cache, or the like. That is, at set time intervals, for each piece of target account information managed: sending a query request of the target account information to the first system; and receiving and caching the cache data corresponding to the target account information returned by the first system.

The second method comprises the following steps: when the message that the user of the client uses the first system to settle accounts is judged to be successful, responding to the message that the user of the client settles accounts successfully, and updating first cache data matched with the target account information; it can be understood that by the method, the cache data of the user can be updated instantly under the condition that the cache data (account balance) of the user is changed.

Therefore, by the method that the server side of the application system acquires the cache data from the first system for each user and determines the first cache data matched with the target account information from the preset plurality of cache data, the problem that when an interface of the first system is directly called to obtain account balance, the account balance is abnormal when the external settlement system (the first system) is called due to high frequency, low interface performance and the like of the external settlement system; the payment experience of the user is improved to a greater extent.

Further, determining deduction information corresponding to the payment information based on the first cache data, the settlement policy of the first system and the payment information; sending the deduction information to the client; for example: the balance of an account in the medical insurance system of the user abc is x; the payment amount contained in the payment information of the object to be paid is y; further determining whether a settlement policy of the first system is satisfied, for example: judging whether one or more articles can be settled by the medical insurance system (namely, the first system) according to the article information of the articles to be paid, whether the value of the first cache data (account balance x in the medical insurance system) meets the payment condition of the payment amount, determining the percentage value which needs to be paid for the articles by the medical insurance settlement system, and the like, wherein the steps comprise the following steps: determining that the user abc can calculate deduction information (such as deduction amount) z for the payment amount y based on the account balance x of the medical insurance card through a settlement strategy; namely the actual amount y-z that the user needs to really pay; and after the deduction information is determined, sending the information to the client so that the client displays the related payment information to the user.

Step S103: and responding to the message of successful settlement of the client, updating first cache data matched with the target account information, and sending a deduction request carrying the deduction information to the first system so that the first system updates the account balance of the target account information.

Specifically, the user performs settlement through a page of the client, and updates the first cache data matched with the target account information in response to a message that the settlement of the client is successful. The method for updating the first cache data matched with the target account information comprises two methods: the first method comprises the following steps: directly updating the first cache data, and updating the data before the user settlement into the data after the user settlement; the second method comprises the following steps: the cached data is updated after querying the first system at intervals for return data from the first system.

Further, after receiving a message that the settlement of the client is successful, sending a deduction request carrying the deduction information to the first system, so that the first system updates the account balance of the target account information; for example: after the user finishes order payment, the application system analyzes the settlement identification in the order and requests the medical insurance system to settle according to the corresponding deduction amount; the settlement process (e.g., pre-settlement before actual settlement) about the medical insurance system is determined by the actual scenario; further, in the case of an abnormal data transmission with the medical insurance system, for example, in the case of a failure in settlement of the medical insurance system, the server of the application system may cancel the user order and send the reason for canceling the order to the client to prompt the user.

It can be understood that the account information of the first system is cached, and the deduction request is sent to the first system after the user settles, so that the problem that the server of the application system is directly connected with the first system is solved, a settlement method which is transparent but asynchronous to the user is realized, and the payment experience of the user is improved.

As shown in fig. 2, an embodiment of the present invention provides a payment method, which is applied to a client, and the method may include the following steps:

step S201: responding to an instruction for settlement by using a first system triggered by a user, and sending a settlement request to a server; the settlement request comprises payment information and target account information;

specifically, a user purchases by using a client of the application system, and settlement is performed by using the first system, which can be triggered by selecting an option for performing payment by using the first system, on a payment page, that is, the client sends a settlement request to the server in response to a settlement instruction by using the first system, which is triggered by the user; the settlement request includes payment information and target account information.

The detailed description of the first system, the settlement request, the payment information, and the target account information is the same as that of step S101, and is not repeated herein.

Step S202: receiving deduction information corresponding to the payment information sent by a server; and settling the target account information according to the payment information and the deduction information.

Specifically, the client receives the deduction information corresponding to the payment information, and settles the account for the target account information according to the payment information and the deduction information according to a settlement instruction triggered by the user.

Further, after the server side judges whether the target account information of the user is bound with the first system, a corresponding verification request is sent to the client side; for a client, namely receiving a first verification requirement sent by a server, displaying a user information page; and receiving user authentication information which is input by a user of the client and is associated with the target account information through the user information page. The detailed description about the user authentication information and the verification of the user authentication information is consistent with the description of step S101, and is not repeated here.

Further, after the user is verified (for example, real name verification), further performing binding authentication on the first system binding, that is, after receiving an authentication result for the user authentication information sent by the server; if the authentication result indicates that the authentication of the authentication information of the user passes, displaying a binding page of the first system; receiving binding information which is input by a user of the client and is related to the target account information of the first system through the binding first system page; sending the binding information to the server; so that the server side verifies the binding information by using the first system; and receiving a verification result of verifying the binding information sent by the server, and displaying a message indicating successful binding with the first system under the condition that the verification result is verified to pass. The detailed description of the verification of the user authentication information and the binding information is consistent with the description of step S101, and is not repeated here.

As shown in fig. 3, an embodiment of the present invention provides a flow of a payment method, which may include the following steps;

step S301: the server executes the following steps aiming at each managed target account information according to a set time interval: and sending a query request of the target account information to the first system.

Step S302: and the server receives and caches cache data corresponding to the target account information returned by the first system.

Step S303: the client sends a request for settlement with the first system.

Step S304: and the server determines first cache data matched with the target account information from a plurality of preset cache data.

Step S305: the client sends a message of successful settlement to the server.

Step S306: and the server side sends a deduction request carrying the deduction information to the first system.

Here, steps 301 to 302 are executed multiple times at time intervals, so the order numbering of steps 301 to 302 is merely an example, and any other steps may be followed by these two steps. The description of step 301 to step 302 is executed for each managed target account information according to a set time interval: sending a query request of the target account information to the first system; and receiving and caching the cache data corresponding to the target account information returned by the first system.

Step S303 to step 306 are described as determining deduction information corresponding to the payment information based on the first cache data, the settlement policy of the first system, and the payment information; sending the deduction information to the client; and responding to the message of successful settlement of the client, and sending a deduction request carrying the deduction information to the first system so as to enable the first system to update the account balance of the target account information.

As shown in fig. 4, an embodiment of the present invention provides a payment server 400, including: a receiving request module 401, an information determining module 402 and a settlement request module 403; wherein,

the receiving request module 401 is configured to receive a request for settlement by using a first system, where the request is sent by a client; the settlement request comprises payment information and target account information;

the information determining module 402 is configured to determine, from a plurality of preset cache data, first cache data that matches the target account information; the preset plurality of cache data comprise account balances of the target account information acquired from the first system; determining withholding information corresponding to the payment information based on the first cache data, a settlement policy of the first system, and the payment information; sending the deduction information to the client;

the settlement request module 403 is configured to, in response to the message that the settlement of the client is successful, update first cache data matched with the target account information, and send a deduction request carrying the deduction information to the first system, so that the first system updates the account balance of the target account information.

As shown in fig. 5, an embodiment of the present invention provides a payment client 500, including: a request sending module 501 and a payment executing module 502; wherein,

the request sending module 501 is configured to send a settlement request to a server in response to a settlement instruction using a first system triggered by a user; the settlement request comprises payment information and target account information;

the payment execution module 502 is configured to receive deduction information corresponding to the payment information sent by a server; and settling the target account information according to the payment information and the deduction information.

As shown in fig. 6, an embodiment of the present invention provides a payment system 600, including: a payment server 400, and one or more payment clients 500.

An embodiment of the present invention further provides a payment electronic device, including: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are enabled to realize the method provided by any one of the above embodiments.

Embodiments of the present invention further provide a computer-readable medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method provided in any of the above embodiments.

Fig. 7 illustrates an exemplary system architecture 700 of a payment server or payment client to which the payment method or payment server of embodiments of the present invention may be applied.

As shown in fig. 7, the system architecture 700 may include

terminal devices

701, 702, 703, a network 704, and a server 705. The network 704 is the medium used to provide communications links between

terminal devices

701, 702, 703 and the server 705. Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

A user may use the

terminal devices

701, 702, 703 to interact with a server 705 over a network 704, to receive or send messages or the like. The

terminal devices

701, 702, 703 may have installed thereon various client applications, such as an e-mall client application, a web browser application, a search-type application, an instant messaging tool, and the like.

The

terminal devices

701, 702, 703 may be various electronic devices having display screens and supporting various client applications, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 705 may be a server providing various services, such as a background management server providing support for client applications used by users with the

terminal devices

701, 702, 703. The background management server may process the received request for settlement using the first system and feed back a settlement result associated with the settlement to the terminal device.

It should be noted that the payment method applied to the client provided by the embodiment of the present invention is generally executed by the

terminal devices

701, 702, and 703, and the payment method applied to the server provided by the embodiment of the present invention is generally executed by the server 705, and accordingly, the payment client is generally disposed in the

terminal devices

701, 702, and 703; the payment server is typically located in the server 705.

It should be understood that the number of terminal devices, networks, and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program executes the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 801.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules and/or units described in the embodiments of the present invention may be implemented by software, and may also be implemented by hardware. The described modules and/or units may also be provided in a processor, and may be described as: a processor includes a receive request module, a determine information module, and a settlement request module. The names of these modules do not constitute a limitation to the module itself in some cases, and for example, the module for receiving a request may also be described as a "module for receiving a request for settlement by the first system sent by the client".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include: receiving a request for settlement by using a first system, which is sent by a client; the settlement request comprises payment information and target account information; determining first cache data matched with the target account information from a plurality of preset cache data; the preset plurality of cache data comprise account balances of the target account information acquired from the first system; determining withholding information corresponding to the payment information based on the first cache data, a settlement policy of the first system, and the payment information; sending the deduction information to the client; and responding to the message of successful settlement of the client, updating first cache data matched with the target account information, and sending a deduction request carrying the deduction information to the first system so that the first system updates the account balance of the target account information. So that the device applied to the client comprises: responding to an instruction for settlement by using a first system triggered by a user, and sending a settlement request to a server; the settlement request comprises payment information and target account information; receiving deduction information corresponding to the payment information sent by a server; and settling the target account information according to the payment information and the deduction information.

According to the embodiment of the invention, a server can be used for receiving a request for settlement by using an external system, which is sent by a client; determining cache data matched with the client from a plurality of preset cache data; determining deduction information based on the cache data and an external system settlement strategy; and after the settlement is successful, the client sends a request carrying the deduction information of the external system to the external system for synchronous updating. The problem of abnormal settlement caused by the external settlement system due to high calling frequency of the external settlement system and low interface performance of the external settlement system is solved; the user payment experience is improved.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A payment method, comprising:

receiving a request for settlement by using a first system, which is sent by a client; the settlement request comprises payment information and target account information;

determining first cache data matched with the target account information from a plurality of preset cache data; the preset plurality of cache data comprise account balances of the target account information acquired from the first system;

determining withholding information corresponding to the payment information based on the first cache data, a settlement policy of the first system, and the payment information; sending the deduction information to the client;

and responding to the message of successful settlement of the client, updating first cache data matched with the target account information, and sending a deduction request carrying the deduction information to the first system so that the first system updates the account balance of the target account information.

2. The method of claim 1, further comprising:

according to the set time interval, aiming at each managed target account information, executing:

sending a query request of the target account information to the first system;

and receiving and caching the cache data corresponding to the target account information returned by the first system.

3. The method of claim 1,

after receiving a request for settlement with the first system sent by the client, the method further comprises:

determining whether the target account information has a binding relationship with the first system;

and if the target account information is determined not to have the binding relationship with the first system, sending a binding message aiming at the first system to the client so that a user binds the target account information to the first system through the client.

4. The method of claim 3, further comprising:

in the event that it is determined that the target account information does not have a binding relationship with the first system,

and verifying the user authentication information associated with the target account information by using an authentication system, and sending a first verification result to the client, so that the client executes the step of binding the target account information to the first system under the condition that the first verification result is verified.

5. The method of claim 4, further comprising: in case the first verification result is verification pass,

sending binding information associated with the target account information to the first system so that the first system verifies the target account information based on the binding information;

and receiving a second verification result of the first system, and sending the second verification result to the client.

6. A payment method, applied to a client, comprising:

responding to an instruction for settlement by using a first system triggered by a user, and sending a settlement request to a server; the settlement request comprises payment information and target account information;

receiving deduction information corresponding to the payment information sent by a server;

and settling the target account information according to the payment information and the deduction information.

7. The method of claim 6, further comprising:

receiving a first verification request sent by a server side, and displaying a user information page;

and receiving user authentication information which is input by a user of the client and is associated with the target account information through the user information page.

8. The method of claim 7, further comprising:

receiving an authentication result aiming at the user authentication information sent by the server;

if the authentication result indicates that the authentication of the authentication information of the user passes, displaying a binding page of the first system;

receiving binding information which is input by a user of the client and is related to the target account information of the first system through the binding first system page;

sending the binding information to the server; so that the server side verifies the binding information by using the first system;

and receiving a verification result of verifying the binding information sent by the server, and displaying a message indicating successful binding with the first system under the condition that the verification result is verified to pass.

9. A payment server, comprising: the system comprises a receiving request module, an information determining module and a settlement request module; wherein,

10. A payment client, comprising: a request sending module and a payment executing module; wherein,

11. A payment system, comprising: the payment server of claim 9, and the payment client of claim 10.

12. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-8.

13. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-8.