Enterprise account payment method, server, system, and storage medium

Abstract

The application discloses an enterprise account payment method, a server, a system and a storage medium, and belongs to the field of data processing. The method comprises the following steps: receiving an order transaction message sent by an order receiving server, wherein the order transaction message comprises order information and transaction party information; sending the order transaction message to a payment resource server, so that the payment resource server sends an order review request message to a payment terminal device; in the case that the payment resource server deducts transaction money from a payment account in response to an order review determination message, receiving a payment message sent by the payment resource server in response to the order review determination message, wherein the payment message comprises the order information and the transaction party information; and sending the payment message to a payee resource server indicated by payee information, so that the payee resource server transfers the transaction money indicated by the order information into a payee account. According to the embodiment of the application, the efficiency of enterprise payment can be improved.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of data processing, and particularly relates to an enterprise account payment method, a server, a system and a storage medium. BACKGROUND

[0002] A payment solution for ordinary users (To C) has become mature after years of development and can meet the needs of ordinary users. Since the payment solution for enterprises (To B) needs to go through more complex processes than the payment solution for To C, the payment solution for To C is difficult to apply to the To B payment field.

[0003] In the To B payment field, different functional staff in an enterprise need to complete each other's tasks and hand over, so as to complete the entire To B payment process. The entire To B payment process needs manual participation, resulting in low efficiency of enterprise payment. SUMMARY

[0004] The embodiments of the present application provide an enterprise account payment method, a server, a system and a storage medium, which can improve the efficiency of enterprise payment.

[0005] In a first aspect, the embodiments of the present application provide an enterprise account payment method, applied to a management server, and the method comprises the following steps: receiving an order transaction message sent by an order receiving server, the order transaction message comprising order information and transaction party information, the transaction party information comprising payee information and payee information; sending the order transaction message to a payee resource server indicated by the payee information, so that the payee resource server sends an order review request message to a payee terminal device indicated by the payee information, the order review request message comprising the order information and the transaction party information; in the case that the payee resource server deducts transaction money indicated by the order information from a payee account indicated by the payee information in response to an order review determination message sent by the payee terminal device, receiving a payment message sent by the payee resource server in response to the order review determination message, the payment message comprising the order information and the transaction party information, and the payee account being an enterprise account; sending the payment message to a payee resource server indicated by the payee information, so that the payee resource server transfers the transaction money indicated by the order information into a payee account indicated by the payee information.

[0006] In a second aspect, the embodiments of the present application provide an enterprise account payment method, applied to a payee resource server, the method comprising: receiving an order transaction message sent by a management server, the order transaction message being sent by an order receiving server to the management server, the order transaction message comprising order information and transaction party information, the transaction party information comprising payee information and payee information; sending an order review request message to a payee terminal device indicated by the payee information, the order review request message comprising the order information and the transaction party information; in the case of receiving an order review confirmation message sent by the payee terminal device, deducting transaction money indicated by the order information from a payee account indicated by the payee information, the payee account being an enterprise account; sending a payment message to the management server, so that the management server sends the payment message to a payee resource server indicated by the payee information, and transfers the transaction money indicated by the order information to a payee account indicated by the payee information, the payment message comprising the order information and the transaction party information.

[0007] In a third aspect, the embodiments of the present application provide a management server, comprising: a receiving module configured to receive an order transaction message sent by an order receiving server, the order transaction message comprising order information and transaction party information, the transaction party information comprising payee information and payee information; a sending module configured to send the order transaction message to a payee resource server indicated by the payee information, so that the payee resource server sends an order review request message to a payee terminal device indicated by the payee information, the order review request message comprising the order information and the transaction party information; the receiving module is further configured to, in the case of the payee resource server deducting transaction money indicated by the order information from a payee account indicated by the payee information in response to an order review determination message sent by the payee terminal device, receive a payment message sent by the payee resource server in response to the order review determination message, the payment message comprising the order information and the transaction party information, the payee account being an enterprise account; the sending module is further configured to send a payment message to a payee resource server indicated by the payee information, so that the payee resource server transfers transaction money indicated by the order information to a payee account indicated by the payee information.

[0008] In a fourth aspect, an embodiment of the present application provides a payer resource server, comprising: a receiving module configured to receive an order transaction message sent by a management server, the order transaction message being sent by an order receiving server to the management server, the order transaction message comprising order information and transaction party information, the transaction party information comprising payer information and payee information; a sending module configured to send an order review request message to a payer terminal device indicated by the payer information, the order review request message comprising the order information and the transaction party information; a processing module configured to deduct transaction money indicated by the order information from a payer account indicated by the payer information in a case where an order review confirmation message sent by the payer terminal device is received, the payer account being an enterprise account; and the sending module is further configured to send a payment message to the management server, so that the management server sends the payment message to a payee resource server indicated by the payee information, and transfers the transaction money indicated by the order information into a payee account indicated by the payee information, the payment message comprising the order information and the transaction party information.

[0009] In a fifth aspect, an embodiment of the present application provides a management server, comprising: a processor and a memory storing computer program instructions; and the processor implements the enterprise account payment method of the first aspect when executing the computer program instructions.

[0010] In a sixth aspect, an embodiment of the present application provides a payer resource server, comprising: a processor and a memory storing computer program instructions; and the processor implements the enterprise account payment method of the second aspect when executing the computer program instructions.

[0011] In a seventh aspect, an embodiment of the present application provides an enterprise account payment system, comprising the management server of the fifth aspect and the payer resource server of the sixth aspect.

[0012] In an eighth aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium storing computer program instructions, and the computer program instructions are executed by a processor to implement the enterprise account payment method of the first aspect or the enterprise account payment method of the second aspect.

[0013] The embodiment of the application provides an enterprise account payment method, a server, a system and a storage medium. The management server can forward an order transaction message sent by an order receiving server to a payer resource server, so that the payer resource server spontaneously sends an order review request message to a payer terminal device, and requests to review the order. The payer terminal device notifies the payer resource server through an order review determination message, and the payer account, i.e., the enterprise account, authorizes to continue the payment process, so that the management server can receive a payment message from the payer resource server, and forwards the payment message to a payee resource server, instructs the payee resource server to transfer the payment corresponding to the payment into the payee account, realizes the payment of the enterprise account, and basically does not need manual participation in the process, reduces the time spent in realizing the payment, and improves the efficiency of the enterprise payment. BRIEF DESCRIPTION OF DRAWINGS

[0014] In order to more clearly illustrate the technical solutions of the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiments of the application. For those of ordinary skill in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0015] Figure 1 A schematic diagram of an example of an application scenario of the enterprise account payment method provided by the embodiments of the application;

[0016] Figure 2 A schematic diagram of another example of an application scenario of the enterprise account payment method provided by the embodiments of the application;

[0017] Figure 3 A flowchart of an embodiment of the enterprise account payment method provided by the first aspect of the application;

[0018] Figure 4 A flowchart of another embodiment of the enterprise account payment method provided by the first aspect of the application;

[0019] Figure 5 A flowchart of still another embodiment of the enterprise account payment method provided by the first aspect of the application;

[0020] Figure 6 A flowchart of yet another embodiment of the enterprise account payment method provided by the first aspect of the application;

[0021] Figure 7 A flowchart of still another embodiment of the enterprise account payment method provided by the first aspect of the application;

[0022] Figure 8 A flowchart of an embodiment of the enterprise account payment method provided by the second aspect of the application;

[0023] Figure 9 Flow chart of another embodiment of the enterprise account payment method provided by the second aspect of the present application;

[0024] Figure 10 Flow chart of yet another embodiment of the enterprise account payment method provided by the second aspect of the present application;

[0025] Figure 11 Flow chart of an example of the enterprise account payment process provided by the embodiments of the present application;

[0026] Figure 12 Flow chart of another example of the enterprise account payment process provided by the embodiments of the present application;

[0027] Figure 13 Structural schematic diagram of an embodiment of the management server provided by the third aspect of the present application;

[0028] Figure 14 Structural schematic diagram of another embodiment of the management server provided by the third aspect of the present application;

[0029] Figure 15 Structural schematic diagram of yet another embodiment of the management server provided by the third aspect of the present application;

[0030] Figure 16 Structural schematic diagram of an embodiment of the payee resource server provided by the fourth aspect of the present application;

[0031] Figure 17 Structural schematic diagram of another embodiment of the payee resource server provided by the fourth aspect of the present application;

[0032] Figure 18 Structural schematic diagram of an embodiment of the management server provided by the fifth aspect of the present application;

[0033] Figure 19 Structural schematic diagram of an embodiment of the payee resource server provided by the sixth aspect of the present application. DETAILED DESCRIPTION

[0034] The features and exemplary embodiments of the various aspects of the present application will be described in detail below, in order to make the purposes, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in combination with the drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, but not to limit the present application. The present application can be implemented without some of these specific details by those skilled in the art. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

[0035] The payment scheme for general users, i.e., To C, has been matured through years of development and can meet the needs of general users. The payment scheme for enterprises, i.e., To B, needs to go through more complex processes than the payment scheme for To C, and therefore, the payment scheme for To C is difficult to apply to the To B payment field. In the To B payment field, different functional staff in an enterprise need to complete each other's tasks and hand over, so as to complete the entire To B payment process. For example, a procurement staff determines procurement items and provides details of the procurement items to a financial staff, the financial staff transfers money to a sales party of the procurement items online or offline, pays for the procurement items, and informs the procurement staff that the money has been paid, the procurement staff contacts the sales party of the procurement items, and the sales party of the procurement items confirms the receipt of the money and arranges delivery. As can be seen, the entire To B payment process needs manual participation, resulting in low payment efficiency of the enterprise.

[0036] The embodiment of the present application provides an enterprise account payment method, a server, a system and a storage medium, which can interact through part or all of the business platform server, the order receiving server, the management server, the payer server, the payee server, the payer terminal device and the payee terminal device, reduce or even completely eliminate the manual participation in the enterprise account payment process as a payer, thereby improving the payment efficiency of the enterprise.

[0037] The enterprise account payment method provided by the embodiment of the present application can involve part or all of the business platform server, the order receiving server, the management server, the payer server, the payee server, the payer terminal device and the payee terminal device, and the number of devices or equipment involved in the enterprise account payment method can be increased or decreased according to the needs, which is not limited herein.

[0038] Figure 1 An example of the application scenario of the enterprise account payment method provided by the embodiment of the present application is shown in the schematic diagram. Figure 1 As shown in the figure, the enterprise account payment method in the embodiment of the present application can involve the business platform server 11, the order receiving server 12, the management server 13, the payer resource server 14, the payee resource server 15, the payer terminal device 16 and the payee terminal device 17.

[0039] The business platform server 11 belongs to a business service platform and can provide business services, for example, the business services can include commodity services, etc. The business service platform can include one or more business platform servers 11, which is not limited herein. The business service platform can be open to the payer terminal device 16, i.e., the business platform server 11 can interact with the payer terminal device 16.

[0040] The order receiving server 12 can belong to an acquirer. The order receiving server 12 can interface with the business platform server 11 and the management server 13. The order receiving server 12 can forward messages sent by the business platform server 11 to the management server 13, and can forward messages sent by the management server 13 to the business platform server 11. The order receiving server 12 can be implemented as one server, or can be implemented as a server cluster formed by two or more servers, which is not limited herein.

[0041] The management server 13 can interface with the order receiving server 12, the payer resource server 14, and the payee resource server 15. That is, the management server 13 can interact with the order receiving server 12, the payer resource server 14, and the payee resource server 15. The management server 13 can aggregate information of orders and information of both parties of a transaction. The information of an order can include an order identifier, order content, order amount, etc., which is not limited herein. The information of both parties of a transaction can include account numbers of both parties, account status, user information, etc., which is not limited herein. The management server 13 can be implemented as one server, or can be implemented as a server cluster formed by two or more servers, which is not limited herein.

[0042] The payer resource server 14 belongs to a payer account management institution, for example, the payer resource server 14 can be a server of a bank where a payer account is located, which is not limited herein. The payer resource server 14 can manage the payer account and information of the payer, and can transfer funds in the payer account in or out according to authorization of the payer user. The payer account can be a corporate account, that is, the payer account is owned by an enterprise. The payer resource server 14 can interact with the payer terminal device 16 and the management server 13. The payer resource server 14 can be implemented as one server, or can be implemented as a server cluster formed by two or more servers, which is not limited herein.

[0043] The payee resource server 15 belongs to a payee account management institution, for example, the payee resource server 15 can be a server of a bank where a payee account is located, which is not limited herein. The payee resource server 15 can manage the payee account and information of the payee, and can transfer funds in the payee account in or out according to authorization of the payee user. The payee account can be a corporate account, or can be a personal account, which is not limited herein. The payee resource server 15 can interact with the payee terminal device 17 and the management server 13. The payee resource server 15 can be implemented as one server, or can be implemented as a server cluster formed by two or more servers, which is not limited herein.

[0044] The payer terminal device 16 is a terminal device logged in with an account of a payer. A payer user can interact with the payer resource server 14 through the payer terminal device 16, and the payer resource server 14 can inform the payer user of the fund status in the payer account through the payer terminal device 16. The payer user can also access the service platform server 11 through the payer terminal device 16 to generate an order or initiate a payment, etc. The payer terminal device 16 can include a mobile phone, a computer, a tablet computer, a wearable device, etc., which are not limited herein.

[0045] The payee terminal device 17 is a terminal device logged in with an account of a payee. A payee user can interact with the payee resource server 15 through the payee terminal device 17. The payee user can also access the service platform server 11 through the payee terminal device 17 to display a business service such as a commodity service on the business service platform. The payee terminal device 17 can include a mobile phone, a computer, a tablet computer, a wearable device, etc., which are not limited herein. The payee terminal device 17 can include a mobile phone, a computer, a tablet computer, a wearable device, etc., which are not limited herein.

[0046] Figure 2 Another example of an application scenario of the enterprise account payment method provided in the embodiments of the present application is shown in the figure. As shown in the figure, the enterprise account payment method can involve the order receiving server 12, the management server 13, the payer resource server 14, the payee resource server 15, the payer terminal device 16, and the payee terminal device 17. Figure 2

[0047] Figure 2 As shown in the figure, the difference between the application scenario and the application scenario shown in the figure is that, Figure 1 As shown in the figure, the application scenario does not include the service platform server 11. The payee user can generate an order through the payee terminal device 17, and submit the order to the order receiving server 12 for receiving through the payee terminal device 17, i.e., the payee terminal device 17 can interact with the order receiving server 12. Figure 2 The specific content of the order receiving server 12, the management server 13, the payer resource server 14, the payee server, the payer terminal device 16, and the payee terminal device 17, and the interaction relationship between the order receiving server 12, the management server 13, the payer resource server 14, the payee server, the payer terminal device 16, and the payee terminal device 17 can be referred to the related description in the application scenario example shown in the figure, which will not be described herein again.

[0048] Figure 1 The application scenario of the enterprise account payment method in the embodiments of the present application can also be changed according to specific needs, which are not limited herein.

[0049] The application scenario of the enterprise account payment method in the embodiments of the present application can also be changed according to specific needs, which are not limited herein. ​​

[0050] The enterprise account payment method, the server, the system and the storage medium of the embodiments of the present application are described one by one as follows.

[0051] The first aspect of the present application provides an enterprise account payment method, which can be applied to a management server, i.e., the enterprise account payment method can be executed by the management server. Figure 3 The flowchart of an embodiment of the enterprise account payment method provided by the first aspect of the present application is shown in FIG. 2. As shown in FIG. 2, the enterprise account payment method can include steps S201 to S204. Figure 3

[0052] In step S201, an order transaction message sent by an order receiving server is received.

[0053] The order transaction message can be generated by the order receiving server according to a received order request message. In some examples, the order request message can be sent by a business platform server, i.e., the order request can be initiated by the business platform server to the order receiving server, so that the order receiving server sends the order transaction message to the management server. In other examples, the order request message can be sent by a payee terminal device, i.e., the order request can be initiated by the payee terminal device to the order receiving server, so that the order receiving server sends the order transaction message to the management server.

[0054] The order transaction message includes order information and transaction party information. The order information includes information related to the order, for example, the order information can include one or more of order identification, order content details, order amount, etc., which are not limited herein. The transaction party information includes relevant information of both transaction parties. Specifically, the transaction party information can include payor information and payee information. The payor information can include one or more of a payor account, a payor account name, etc., which are not limited herein.

[0055] In step S202, the order transaction message is sent to a payor resource server indicated by the payor information, so that the payor resource server sends an order review request message to a payor terminal device indicated by the payor information.

[0056] The management server can interface with the order receiving server and the payor terminal device. The management server can determine the payor account according to the payor information in the order transaction message, and thus send the order review request message to the payor terminal device logged in the payor account. The order review request message includes order information and transaction party information. The order review request message is used to show the payor user the order information and the transaction party information, so that the payor user can review the order information and the transaction party information to determine whether to authorize the subsequent payment process.

[0057] ​In step S203, in the case that the payment resource server deducts the transaction amount indicated by the order information from the payment account indicated by the payment information in response to the order review determination message sent by the payment terminal device, the payment message sent by the payment resource server in response to the order review determination message is received.

[0058] If the payment user determines to authorize the subsequent payment process, the payment user can send an order review determination message to the payment resource server through the payment terminal device. The order review determination message represents the determination to authorize the subsequent payment process. In response to the order review determination message, the payment resource server can deduct the transaction amount of the order information from the payment account indicated by the payment information in the case that the payment user authorizes the subsequent payment process. The payment account in the embodiment of the present application is an enterprise account, and the enterprise account belongs to an enterprise. In the case that the payment user authorizes the subsequent payment process, the payment resource server can also send a payment message to the management server. The payment message is used to instruct the management server to conduct the subsequent payment process.

[0059] The payment message can include order information and transaction party information. The order information and the transaction party information can refer to the related description in the above-mentioned embodiments, and will not be described here again.

[0060] In step S204, the payment message is sent to the payment resource server indicated by the payment information, so that the payment resource server transfers the transaction amount indicated by the order information into the payment account indicated by the payment information.

[0061] In the case that the payment message sent by the payment resource server is received, the management server can determine the payment resource server according to the payment information, and send the payment message to the payment resource server. In the embodiment of the present application, the payment message sent by the management server to the payment resource server does not need to be triggered by the order handling server, and the process is more simple compared with the payment of a personal user.

[0062] The payment message can be used to instruct the payment resource server to perform the deposit operation of the payment account. The order information can include an order amount, and the payment resource server can determine the payment account according to the payment information, and transfer the transaction amount of the order amount into the payment account.

[0063] In the embodiments of the present application, the management server can forward the order transaction message sent by the order receiving server to the payer resource server, so that the payer resource server spontaneously sends an order review request message to the payer terminal device, requesting to review the order. The payer terminal device notifies the payer resource server through the order review determination message, and the payer account, i.e., the enterprise account, authorizes to continue the payment process, so that the management server can receive the payment message from the payer resource server and forward the payment message to the payee resource server, instructing the payee resource server to transfer the payment corresponding to this payment into the payee account, realizing the payment of the enterprise account, and basically without human intervention in the process, reducing the time spent to realize the payment and improving the efficiency of enterprise payment.

[0064] Moreover, in the payment process, the order transaction message, the order review determination message and the payment message can include order information and transaction information, combining the order information and the transaction information, avoiding the separation of the order information and the transaction information, closely associating the information, and being more convenient for management and inquiry.

[0065] In some embodiments, after receiving the order transaction message, the management server can verify the payee information to ensure that the payee account is legal and available, so as to improve the security and success rate of payment. Figure 4 The flowchart of another embodiment of the enterprise account payment method provided for the first aspect of the present application.

[0066] Figure 4 Different from Figure 3 , the enterprise account payment method shown in Figure 4 may further include steps S205 to S209, Figure 3 Step S202 in Figure 4 may be specifically refined as steps S2021 and S2022 in

[0067] In step S205, the first account data matching the payee information is searched in the preset account database.

[0068] The account database is a database configured corresponding to the management server. The account database can store legal and effective account data, for example, the account database is used to store the account data related to the payment process managed by the management server, and the account data of the account registered in the management server. Herein, the content of the account data is not limited, for example, the account data can include but is not limited to one or more of account name, account number, account status, etc. The account database can be set in the management server, or in other devices outside the management server, which is not limited herein. In some examples, the management server can call the account database through an interface. The type of the account database is not limited herein. For example, the account database can adopt a Redis database.

[0069] The first account data is account data in the account database that matches the payee information. The first account data is searched in the account database to determine whether the payee indicated by the payee information is valid. The account data that matches the payee information can be account data that is consistent with the payee information. For example, the payee information includes an account number and an account name, and the first account data is account data in the account database that has an account number and an account name consistent with the payee information. That is, the first account data can be searched in the account database if there is account data in the account database that has an account number and an account name consistent with the payee information.

[0070] In step S206, if the first account data is not found in the account database, an identity verification request message is sent to the payee resource server to cause the payee resource server to perform account identity verification on the payee information.

[0071] If the first account data is not found in the account database, it indicates that the payee may not be valid, and the payee resource server can be triggered to perform identity verification on the payee information. Specifically, the management server can send an identity verification request message to the payee resource server. The payee resource server can search for second account data that matches the payee information in the account data of the registered accounts stored in the payee resource server in response to the identity verification request message. The second account data is account data in the payee resource server that matches the payee information.

[0072] The account identity verification performed by the payee resource server on the payee information can specifically include searching for account data consistent with the payee information in the payee resource server and whether the account data consistent with the payee information is valid at the current time. If there is account data consistent with the payee information in the payee resource server and the account data is valid at the current time, the account identity verification is successful. If there is no account data consistent with the payee information in the payee resource server, the account identity verification fails. If there is account data consistent with the payee information in the payee resource server, but the account data is not valid at the current time, the account identity verification fails. In some examples, whether the account data is valid at the current time can be determined by whether the account status in the account data is an effective state; the account status is an effective state, indicating that the account data is valid at the current time; and the account status is an invalid state, indicating that the account data is not valid at the current time.

[0073] In step S207, if the account identity verification is successful, the second account data that matches the payee information sent by the payee resource server is received.

[0074] The account identity verification of the payee information by the payee resource server succeeds, that is, the payee resource server can find the second account data matching the payee information, and the payee resource server can send the second account data to the payee resource server.

[0075] The second account data can be encrypted data. For example, the payee resource server finds the account number, account name and account status matching the payee information, assembles the account number, account name and account status matching the payee information to obtain basic information, encrypts the assembled basic information to obtain the second account data. Through encryption, the security of the second account data can be enhanced, thereby improving the security of the enterprise account payment process.

[0076] In step S208, the second account data is stored in the account database, and the update time of the second account data is recorded.

[0077] The second account data is stored in the account database to supplement the account database of the management server. The update time of the second account data can be the time when the management server receives the second account. The update time of each account data in the account database can reflect the latest active time of the account data, and can also be regarded as the latest effective time of the account data.

[0078] In step S2021, the order transaction information is sent to the payee resource server indicated by the payee information in the case of successful account identity verification.

[0079] In the case that the management server receives the second account data, that is, the account identity verification succeeds, the management server sends the order transaction information to the payee resource server, that is, in the case that the payee account is determined to be legal and effective, the payment process will continue.

[0080] If the account identity verification fails, the management server will not send the order transaction information to the payee resource server, that is, the payment process is terminated, so as to ensure the security of the enterprise account payment.

[0081] In step S209, in the case that the first account data is found in the account database, it is determined whether the account status in the first account data is in the effective state.

[0082] In the case that the first account data is found in the account database, that is, the account data consistent with the payee information exists in the account database, if the account status in the first account data is in the effective state, it indicates that the payee account corresponding to the first account data is available, and the subsequent payment process can continue. If the account status in the first account data is in the invalid state, it indicates that the payee account corresponding to the first account data is unavailable, and the payment process needs to be terminated.

[0083] In order to ensure data security, the account data in the account database can be encrypted data. In the process of searching for the first account data in the account database, the account data can be decrypted, and the account number and account name in the decrypted account data are compared with the account number and account name in the payee information. If they are consistent, the account data can be determined as the first account data.

[0084] In step S2022, if the account status in the first account data is the valid state, the order transaction information is sent to the payer resource server indicated by the payer information.

[0085] If the account status in the first account data is the invalid state, the management server terminates the payment process, and can also feed back the termination reason to the order handling server, so that the order handling server feeds back the result of payment termination and the termination reason to the payer terminal device. In the case of abnormal account of the payee, the payment can be terminated in time to ensure the security of the enterprise account payment.

[0086] In some embodiments, after the management server sends the order transaction message to the payer resource server, the payer resource server can perform authority verification on the payer information and the order information, and continue the payment process if the authority verification is successful, so as to improve the security and success rate of payment. After the management server sends the payment message to the payee resource server, the result of the transfer of the money can also be obtained in real time to realize complete supervision of the payment process. Figure 5 The flowchart of another embodiment of the enterprise account payment method provided by the first aspect of the application. Figure 5 Different from Figure 3 The difference is that Figure 5 The enterprise account payment method shown in the figure can also include steps S210 to S212, and steps S213 to S215.

[0087] In step S210, the authority verification response message sent by the payer resource server is received.

[0088] The permission check response message is obtained by the payer resource server according to the order transaction message. That is, after the management server sends the order transaction message to the payer resource server, the payer resource server can perform permission check according to the order transaction message. The permission check can include checking the payer information and checking the order information. The checking of the payer information can include searching for account data matching the payer information in the payer resource server to determine whether the payer account is legal and valid. Specifically, it can be determined whether there is account data consistent with the payer information in the resource server, and if there is account data consistent with the payer information in the resource server, the checking of the payer information is successful. The checking of the order information can include determining whether the payer account has the permission to pay for the order corresponding to the order information, and if it is determined that the payer account has the permission to pay for the order corresponding to the order information, the checking of the order information is successful. If both the checking of the payer information and the checking of the order information are successful, it is determined that the permission check is successful. If at least one of the checking of the payer information and the checking of the order information fails, it is determined that the permission check fails.

[0089] The permission check response message includes permission check result information, and the permission check result information is used to represent the result of the permission check. The permission check result information can include check success information or check failure information. The management server obtains the result of the permission check from the payer resource server through the permission check response message, so as to determine whether to perform the subsequent payment process according to the result of the permission check.

[0090] In step S211, in the case where the permission check result information represents that the permission check is successful, the third account data in the preset account database matching the payer information is updated, and the update time of the third account data is recorded.

[0091] In some examples, there is no account data matching the payer information in the account database, and in the case where the permission check result information represents that the permission check is successful, the payer resource server can send the account data matching the payer information to the management server, the management server can insert the account data matching the payer information sent by the payer resource server into the account database, the account data matching the payer information inserted into the account database is the updated third account data, and the time of inserting the account data matching the payer information into the account database can be taken as the update time of the third account data.

[0092] In some examples, the account database includes the account data matching the payee information, and in the case that the permission verification result information represents that the permission verification is successful, the payee resource server sends the account data matching the payee information to the management server. The account data matching the payee information in the account database can be replaced by the account data matching the payee information sent by the payee resource server, so as to realize the updating of the third account data. The time when the account data matching the payee information in the account database is replaced by the account data matching the payee information sent by the payee resource server can be taken as the updating time of the third account data.

[0093] In yet some examples, the account database includes the account data matching the payee information, and in the case that the permission verification result information represents that the permission verification is successful, the payee resource server does not send the account data matching the payee information to the management server. When the permission verification response message is received, the management server can be considered to have updated the third account data, i.e., the account data matching the payee information in the account database. The time when the permission verification response message is received can be taken as the updating time of the third account data.

[0094] In the case that the permission verification result information represents that the permission verification fails, the payment process is terminated.

[0095] In step S212, the permission verification response message is sent to the order receiving server.

[0096] Irrespective of whether the permission verification result information represents that the permission verification succeeds or fails, the management server sends the permission verification response message to the order receiving server to inform the order receiving server of the progress of the payment, so as to facilitate the order receiving server to manage the payment progress of the order.

[0097] In step S213, the money transfer-in notification message sent by the payee resource server is received.

[0098] The money transfer-in notification message includes money transfer-in result information, which can represent that the money transfer-in to the payee account succeeds or fails. The management server can obtain the payment progress from the payee server through the money transfer-in notification message.

[0099] In step S214, in the case that the money transfer-in result information represents that the money transfer-in succeeds, the fourth account data matching the payee information in the payment message and the fifth account data matching the payee information in the payment message in the preset account database are updated, and the updating time of the fourth account data and the updating time of the fifth account data are recorded.

[0100] The fourth account data is account data in the account database that matches the payee information in the payment message. The fifth account data is account data in the account database that matches the payee information in the payment message. Due to the nature of the enterprise account payment, there can be a time gap between the ordering process and the payment process of the enterprise account. In order to ensure the timeliness of the account data in the account database, the fourth account data and the fifth account data in the account database can be updated in the case of successful transfer of the funds, and the update time of the fourth account data and the update time of the fifth account data are recorded. The update time of the fourth account data can represent the most recent active time of the fourth account data, and can also be regarded as the latest effective time of the account data. Similarly, the update time of the fifth account data can represent the most recent active time of the fifth account data, and can also be regarded as the latest effective time of the account data.

[0101] In order to improve the security of the data, the fourth account data and the fifth account data can be encrypted data, and specifically can be encrypted basic information. The basic information can include spliced account number, account name, and account status, etc. information, which is not limited here.

[0102] The first account data, the second account data, and the fifth account data can be the same or different, which is not limited here. Similarly, the third account data and the fourth account data can be the same or different, which is not limited here.

[0103] In step S215, the transfer of funds notification message is sent to the order receiving server.

[0104] Regardless of whether the transfer of funds result information represents successful transfer of funds or unsuccessful transfer of funds, the management server sends the transfer of funds notification message to the order receiving server to inform the order receiving server of the progress of the payment, so as to facilitate the order receiving server to manage the payment progress of the order, and to facilitate the order receiving server to inform the payment progress to the payer terminal device and the payee terminal device.

[0105] In some embodiments, after receiving the payment message sent by the payment resource server, the management server can also perform association verification on the payment message and the order transaction message to ensure the security of the payment. Figure 6 The flowchart of still another embodiment of the enterprise account payment method provided by the first aspect of the application. Figure 6 Different from Figure 3 The difference between the enterprise account payment method shown in Figure 6 The enterprise account payment method shown in Figure 3 The step S204 in Figure 6 The step S2041 shown in

[0106] In step S216, according to the order information and the transaction information in the payment message, the order transaction message corresponding to the payment message is searched.

[0107] When the management server receives the order transaction message in advance, the order transaction message can be stored in the management server, so as to ensure the management of the payment process by the management server and avoid data loss. In order to ensure the security of the enterprise account payment and avoid payment errors caused by the inconsistency between the payment message and the content of the order transaction message initiating the payment, the management server can search the order transaction message corresponding to the payment message according to the order information and the transaction information in the received payment message. The order transaction message corresponding to the payment message can be an order transaction message in which at least part of the information in the order information and the transaction information is consistent with at least part of the information in the order information and the transaction information in the payment message. For example, the order information includes order identifier, order details and order amount, and the transaction information includes the account numbers and account names of the payer and the payee. The order transaction message in which the order identifier is consistent with the order identifier in the payment message can be determined as the order transaction message corresponding to the payment message.

[0108] In step S217, the order information and the transaction information in the payment message and the corresponding order transaction message are associated and verified.

[0109] The association verification can include judging whether the order information in the payment message is consistent with the order information in the corresponding order transaction message, whether the transaction information in the payment message is consistent with the transaction information in the corresponding order transaction message, whether the order indicated by the order information is successfully accepted, and whether the state of the order indicated by the order information is an end state, i.e., verifying whether the payment represented by the payment message is valid. The end state can include an expired state, a canceled state, a rejected state, and a paid state. The state of the order indicated by the order information being an end state indicates that the order has been processed.

[0110] If the order information in the payment message is consistent with the order information in the corresponding order transaction message, the transaction information in the payment message is consistent with the transaction information in the corresponding order transaction message, the order indicated by the order information is successfully accepted, and the state of the order indicated by the order information is not an end state, i.e., the payment represented by the payment message is valid, the association verification is successful. If the order information in the payment message is inconsistent with the order information in the corresponding order transaction message, the transaction information in the payment message is inconsistent with the transaction information in the corresponding order transaction message, the order indicated by the order information is not successfully accepted, and / or the state of the order indicated by the order information is an end state, i.e., the payment represented by the payment message is invalid, the association verification fails.

[0111] In step S218, it is determined whether the order information and the transaction information in the payment message satisfy the payment authority condition.

[0112] The payment permission condition can be set according to scenarios, requirements, experience, etc., and is not limited herein. The payment permission condition can be related to the order information and / or the transaction party information. In some examples, the payment permission condition can include, but is not limited to, one or more of the following: the business scenario represented by the transaction party information and the order information meets the business scenario requirement, the order amount in the order information is within the single payment amount range, the payment amount of the payment party account indicated by the payment party information on the day after deducting the order amount in the order information does not exceed the single-day cumulative payment limit of the payment party account, the receiving amount of the payment party account indicated by the payment party information on the day after transferring the order amount in the order information does not exceed the single-day cumulative payment limit of the payment party account, the payment party account indicated by the payment party information is within the payment party whitelist, the payment party account indicated by the payment party information is within the payment party whitelist, the payment party account indicated by the payment party information is not within the payment party blacklist, and the payment party account indicated by the payment party information is not within the payment party blacklist.

[0113] The order information and the transaction party information in the payment message meeting the payment permission condition indicates that the payment is relatively safe, and the payment process can continue.

[0114] The order information and the transaction party information in the payment message not meeting the payment permission condition indicates that the payment is risky, and the payment process needs to be terminated.

[0115] In step S219, in the case where the association verification fails and / or the order information and the transaction party information in the payment message do not meet the payment permission condition, the payment process indicated by the payment message is terminated.

[0116] The association verification failure indicates that the payment indicated by the payment message is invalid. The order information and the transaction party information in the payment message not meeting the payment permission condition indicates that the payment is risky. In at least one of the two cases of the payment indicated by the payment message being invalid and the payment being risky, the payment may be erroneous. In order to ensure payment security, the payment process needs to be terminated.

[0117] In step S2041, in the case where the verification is successful and the order information and the transaction party information in the payment message meet the payment permission condition, the payment message is sent to the payment party resource server.

[0118] In the case where the payment indicated by the payment message is valid and the payment is relatively safe, the payment process can continue, and the payment message is sent to the payment party resource server. The payment party resource server receives the payment message, transfers the transaction amount indicated by the order information to the payment party account indicated by the payment party information, and completes the transfer of the payment amount in the payment party account.

[0119] By associating and checking the order message and the transaction party information, and checking the payment authority by using the payment authority condition, it can be determined whether the current payment is safe and effective, and the subsequent payment process is performed only when the current payment is safe and effective, thereby improving the security of the enterprise account payment.

[0120] In some embodiments, in the case of transferring the money corresponding to the current payment into the payee account, the order handling server can also send other information related to the order, such as logistics information and / or payment voucher information, to the payment resource server through the management server, so as to realize the combination of order information, transaction information, logistics information, and payment voucher information, and further improve the reliability and ease of management of the payment. Figure 7 The flowchart of another embodiment of the enterprise account payment method provided by the first aspect of the application. Figure 7 Different from Figure 3 The difference between the enterprise account payment method shown in Figure 7 The enterprise account payment method shown in the step S220 and the step S221.

[0121] In the step S220, the order processing message sent by the order handling server is received.

[0122] The order processing message includes logistics information associated with the order information and / or payment voucher information associated with the order information. The logistics information associated with the order information can include the logistics information of the order indicated by the order information. The payment voucher information associated with the order information can include the payment voucher information of the order indicated by the order information, and the payment voucher information can include invoice information, etc., which is not limited herein.

[0123] The order processing message can be received by the order handling server from the business platform server, or can be received by the order handling server from the payee terminal device, which is not limited herein.

[0124] In the step S221, the order processing message is sent to the payment resource server, so that the payment resource server sends the order processing message to the payer terminal device.

[0125] The management server receives the order processing message, and can send the order processing message to the payment resource server to send the logistics information and / or the payment voucher information to the payment resource server. The payment resource server can send the order processing message to the payer terminal device, so that the payer terminal device obtains the logistics information and / or the payment voucher information, so as to facilitate the display to the management personnel of the payer account, facilitate the tracking of the logistics of the order by the enterprise, and collect and store the payment voucher information.

[0126] Through the order processing message, the logistics and payment voucher information can be combined with the order information and transaction information, so that the information of multiple aspects is closely associated, and it is more convenient for management and inquiry.

[0127] The enterprise account payment method in the embodiments of the present application meets the online and digital requirements of the whole process of enterprise account payment, has strong timeliness in account entry, and each stage in the payment process can be supervised, thereby improving the quality of the enterprise account payment channel.

[0128] The second aspect of the present application provides an enterprise account payment method, which can be applied to a payee resource server, that is, the enterprise account payment method can be executed by the payee resource server. Figure 8 The flowchart of an embodiment of the enterprise account payment method provided by the second aspect of the present application is shown in FIG. 3. As shown in FIG. 3, the enterprise account payment method can include steps S301 to S304. Figure 8

[0129] In step S301, an order transaction message sent by a management server is received.

[0130] The order transaction message is sent by an order receiving server to the management server. The order transaction message includes order information and transaction party information. The transaction party information includes payor information and payee information.

[0131] In step S302, an order review request message is sent to a payor terminal device indicated by the payor information.

[0132] The order review request message includes order information and transaction party information.

[0133] In step S303, in the case where an order review confirmation message sent by the payor terminal device is received, the transaction amount indicated by the order information is deducted from a payor account indicated by the payor information.

[0134] The payor account is an enterprise account.

[0135] In step S304, a payment message is sent to the management server, so that the management server sends a payment message to a payee resource server indicated by the payee information, and the transaction amount indicated by the order information is transferred to a payee account indicated by the payee information.

[0136] The payment message includes order information and transaction party information.

[0137] The specific contents of steps S301 to S304 can be referred to the related descriptions in the above embodiments, which will not be repeated here.

[0138] ​In the embodiment of the present application, the payer resource server can receive the order transaction message sent by the management server, and thus spontaneously send an order review request message to the payer terminal device to request the order to be reviewed. Through the order review determination message received from the payer terminal device, the payer resource server can determine that the payer account, i.e., the enterprise account, is authorized to continue the payment process, and the payer resource server sends a payment message to the management server, so that the management server sends a payment message to the payee resource server, instructing the payee resource server to transfer the payment corresponding to this payment into the payee account, thereby realizing the payment of the enterprise account, and basically no manual intervention is required in the process, reducing the time spent to realize the payment and improving the efficiency of enterprise payment.

[0139] Moreover, in the payment process, the order transaction message, the order review determination message and the payment message can include order information and transaction information, which combines the order information and the transaction information, avoids the separation of the order information and the transaction information, and closely associates the information, which is more convenient for management and inquiry.

[0140] In some examples, after the payer resource server receives the order transaction message sent by the management server, the payer resource server can perform permission verification on the payer information and the order information, and continue the payment process if the permission verification is successful, so as to improve the security and success rate of payment. Figure 9 The flowchart of another embodiment of the enterprise account payment method provided by the second aspect of the present application. Figure 9 Different from Figure 8 The difference is that Figure 9 The enterprise account payment method shown in FIG. 5 can further include steps S305 to S307.

[0141] In step S305, permission verification is performed according to the order transaction message to obtain permission verification result information.

[0142] In step S306, the permission verification result information is used to generate a permission verification response message.

[0143] The permission verification response message includes the permission verification result information.

[0144] In step S307, the permission verification response message is sent to the management server, so that the management server updates the third account data in the preset account database that matches the payee information and records the update time of the third account data if the permission verification result information indicates that the permission verification is successful.

[0145] The specific content of steps S305 to S307 can be referred to the related description in the above embodiment, which will not be repeated here.

[0146] In some embodiments, after the payment corresponding to the current payment is transferred into the payee account, the order receiving server can also send other information related to the order, such as logistics information and / or payment voucher information, to the payment resource server through the management server, so as to realize the combination of order information, transaction information, logistics information, payment voucher information and other information, and further improve the reliability and ease of management of payment. Figure 10 A flowchart of another embodiment of the enterprise account payment method provided by the second aspect of the application. Figure 10 Different from Figure 8 , the enterprise account payment method shown in Figure 10 may further include steps S308 and S309.

[0147] In step S308, the order processing message sent by the management server is received.

[0148] The order processing message includes logistics information associated with the order information and / or payment voucher information associated with the order information.

[0149] In step S309, the order processing message is sent to the payer terminal device.

[0150] The specific content of steps S308 and S309 can be referred to the related description in the above embodiments, which will not be repeated here.

[0151] For ease of understanding, the enterprise account payment process of the embodiments of the application will be described below with reference to the application scenario shown in Figure 1 , which is different from Figure 1 . Figure 11 A flowchart of an example of the enterprise account payment process provided by the embodiments of the application. As shown in Figure 11 , the enterprise account payment process can include steps S401 to S429.

[0152] In step S401, the payer terminal device sends an order message to the business platform server.

[0153] In step S402, in response to the order message, the business platform server sends an order request message to the order receiving server.

[0154] In step S403, in response to the order request message, the order receiving server sends an order transaction message to the management server.

[0155] In step S404, the management server searches for first account data matching the payee information in the account database, and if no matching data is found, jumps to steps S405 to S408; if matching data is found, jumps to step S409.

[0156] In step S405, the management server sends an identity check request message to the payee resource server.

[0157] In step S406, the payee resource server performs account identity check in response to the identity check request message.

[0158] In step S407, the account identity check succeeds, and the payee resource server sends second account data matching the payee information to the management server.

[0159] In step S408, the management server stores the second account data into the account database, records the update time of the second account data, and jumps to step S410.

[0160] In step S409, the management server checks the first account data. If the check succeeds, the process jumps to step S410; if the check fails, the payment process is terminated.

[0161] The check includes comparing the account number and account name in the first account data with the payee information in the order transaction message, and determining whether the account state in the first account data is in an effective state. If the account number and account name in the first account data are consistent with the payee information in the order transaction message, and the account state in the first account data is in the effective state, the check succeeds. If the account number and account name in the first account data are inconsistent with the payee information in the order transaction message, and / or the account state in the first account data is in an invalid state, the check fails.

[0162] In step S410, the management server sends the order transaction message to the payer resource server.

[0163] In step S411, the payer resource server performs permission check according to the order transaction message.

[0164] In step S412, the payer resource server sends a permission check response message to the management server.

[0165] In step S413, in the case that the permission check result information in the permission check response message indicates that the permission check succeeds, the management server updates third account data matching the payer information in the account database, and records the update time of the third account data.

[0166] In step S414, the management server sends the permission check response message to the order handling server.

[0167] In step S415, the payer resource server sends an order review request message to the payer terminal device.

[0168] In step S416, the payer terminal device sends an order review determination message to the payer resource server.

[0169] In step S417, the payer resource server deducts the corresponding transaction amount from the payer account.

[0170] In step S418, the payer resource server sends a payment message to the management server.

[0171] In step S419, the management server performs association verification and payment authority verification on the payment message.

[0172] The payment authority verification is to determine whether the order information and the transaction party information in the payment message meet the payment authority conditions.

[0173] In step S420, in the case that the association verification and the payment authority verification are both successful, the management server sends a payment message to the payee resource server.

[0174] In step S421, the payee resource server transfers the transaction amount into the payee account.

[0175] In step S422, the payee resource server sends a payment transfer notification message to the management server.

[0176] In step S423, the payee resource server sends a payment transfer notification message to the payee terminal device.

[0177] In step S424, in the case that the payment transfer result information in the payment transfer notification message represents that the payment transfer is successful, the fourth account data matched with the payer information and the fifth account data matched with the payee information in the account database are updated, and the update time of the fourth account data and the fifth account data is recorded.

[0178] In step S425, the management server sends a payment transfer notification message to the order handling server.

[0179] In step S426, the business platform server sends an order processing message to the order handling server.

[0180] In step S427, the order handling server sends an order processing message to the management server.

[0181] In step S428, the management server sends an order processing message to the payer resource server.

[0182] In step S429, the payer resource server sends an order processing message to the payer terminal device.

[0183] The specific details of steps S401 to S429 can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0184] The following is an example Figure 2 The enterprise account payment process of this application embodiment will be explained using the illustrated application scenario as an example. Figure 2 correspond, Figure 12 A flowchart illustrating another example of a corporate account payment process provided in an embodiment of this application. For example... Figure 12 As shown, the corporate account payment process may include steps S501 to S528.

[0185] In step S501, the payee's terminal device sends an order request message to the order acceptance server.

[0186] In step S502, in response to the order request message, the order acceptance server sends an order transaction message to the management server.

[0187] In step S503, the management server searches the account database for the first account data that matches the payee information. If no data is found, the process proceeds to steps S504 to S507; if a data is found, the process proceeds to step S508.

[0188] In step S504, the management server sends an identity verification request message to the payee resource server.

[0189] In step S505, in response to the identity verification request message, the payee resource server performs account identity verification.

[0190] In step S506, the account identity verification is successful, and the payee resource server sends the second account data that matches the payee information to the management server.

[0191] In step S507, the management server stores the second account data into the account database, records the update time of the second account data, and then proceeds to step S509.

[0192] In step S508, the management server verifies the data of the first account. If the verification is successful, it proceeds to step S509; if the verification fails, the payment process is terminated.

[0193] Verification can be found at [link / reference]. Figure 11 The relevant explanations in the examples shown will not be repeated here.

[0194] In step S509, the management server sends an order transaction message to the payer's resource server.

[0195] In step S510, the payer's resource server performs permission verification based on the order transaction message.

[0196] In step S511, the payer resource server sends a permission check response message to the management server.

[0197] In step S512, in the case that the permission check result information in the permission check response message represents that the permission check is successful, the management server updates the third account data in the account data matching the payer information, and records the update time of the third account data.

[0198] In step S513, the management server sends a permission check response message to the order receiving server.

[0199] In step S514, the payer resource server sends an order review request message to the payer terminal device.

[0200] In step S515, the payer terminal device sends an order review determination message to the payer resource server.

[0201] In step S516, the payer resource server deducts the corresponding transaction amount from the payer account.

[0202] In step S517, the payer resource server sends a payment message to the management server.

[0203] In step S518, the management server performs association verification and payment permission verification on the payment message.

[0204] The payment permission verification is to determine whether the order information and the transaction party information in the payment message meet the payment permission condition.

[0205] In step S519, in the case that both the association verification and the payment permission verification are successful, the management server sends a payment message to the payee resource server.

[0206] In step S520, the payee resource server transfers the transaction amount into the payee account.

[0207] In step S521, the payee resource server sends a payment transfer notification message to the management server.

[0208] In step S522, the payee resource server sends a payment transfer notification message to the payee terminal device.

[0209] In step S523, in the case that the payment transfer result information in the payment transfer notification message represents that the payment transfer is successful, the fourth account data matching the payer information and the fifth account data matching the payee information in the account database are updated, and the update times of the fourth account data and the fifth account data are recorded.

[0210] In step S524, the management server sends a money transfer-in notification message to the order receiving server.

[0211] In step S525, the payee terminal device sends an order processing message to the order receiving server.

[0212] In step S526, the order receiving server sends an order processing message to the management server.

[0213] In step S527, the management server sends an order processing message to the payer resource server.

[0214] In step S528, the payer resource server sends an order processing message to the payer terminal device.

[0215] The specific content of the above steps S501 to S528 can be referred to the related description in the above embodiments, which will not be repeated here.

[0216] The third aspect of the present application provides a management server. Figure 13 An embodiment of the structure of the management server provided by the third aspect of the present application is shown in the figure. As shown in the figure, the management server 600 can include a receiving module 601 and a sending module 602. Figure 13

[0217] The receiving module 601 can be used to receive the order transaction message sent by the order receiving server.

[0218] The order transaction message includes order information and transaction party information, and the transaction party information includes payer information and payee information.

[0219] The sending module 602 can be used to send the order transaction message to the payer resource server indicated by the payer information, so that the payer resource server sends an order review request message to the payer terminal device indicated by the payer information.

[0220] The order review request message includes order information and transaction party information.

[0221] The receiving module 601 can also be used to receive a payment message sent by the payer resource server in response to the order review determination message, in the case that the payer resource server deducts the transaction money indicated by the order information from the payer account indicated by the payer information in response to the order review determination message sent by the payer terminal device.

[0222] The payment message includes order information and transaction party information. The payer account is an enterprise account.

[0223] ​The sending module 602 can also be used to send a payment message to a payee resource server indicated by payee information, so that the payee resource server transfers transaction money indicated by order information into a payee account indicated by the payee information.

[0224] In the embodiment of the application, the management server can forward the order transaction message sent by the order receiving server to the payer resource server, so that the payer resource server sends an order review request message to the payer terminal device to request the order to be audited. The payer resource server is notified by the order review determination message of the payer terminal device, and the payer account, i.e. the enterprise account, is authorized to continue the payment process, so that the management server can receive the payment message from the payer resource server and forward the payment message to the payee resource server, instructing the payee resource server to transfer the money corresponding to the payment into the payee account, realizing the payment of the enterprise account, and basically without human intervention in the process, reducing the time spent to realize the payment and improving the efficiency of enterprise payment.

[0225] Moreover, in the payment process, the order transaction message, the order review determination message and the payment message can include order information and transaction information, combining the order information and the transaction information, avoiding the separation of the order information and the transaction information, closely associating the information, and being more convenient for management and inquiry.

[0226] Figure 14 The structure schematic diagram of another embodiment of the management server provided by the third aspect of the application. Figure 14 Different from Figure 13 The difference is that Figure 14 The management server shown in the figure can also include a processing module 603.

[0227] The processing module 603 can be used to find first account data matched with the payee information in a preset account database.

[0228] The sending module 602 can also be used to send an identity verification request message to the payee resource server in the case that the first account data is not found in the account database, so that the payee resource server performs account identity verification on the payee information.

[0229] The receiving module 601 is also used to receive second account data matched with the payee information sent by the payee resource server in the case that the account identity verification is successful.

[0230] The processing module 603 is also used to store the second account data in the account database and record the update time of the second account data.

[0231] The sending module 602 can be used to send the order transaction information to the payer resource server indicated by the payer information in the case that the account identity verification is successful.

[0232] The processing module 603 is also used to determine whether the account status in the first account data is active when the first account data is found in the account database.

[0233] The sending module 602 can be used to send order transaction information to the payer resource server indicated by the payer information when the account status in the first account data is active.

[0234] In some embodiments, the receiving module 601 can also be used to receive an authorization verification response message sent by the payer's resource server.

[0235] The permission verification response message is obtained by the payer's resource server through permission verification based on the order transaction message. The permission verification response message includes permission verification result information.

[0236] The processing module 603 is also used to update the third account data that matches the payer information in the preset account database when the permission verification result indicates that the permission verification is successful, and to record the update time of the third account data.

[0237] In some examples, the sending module 602 can also be used to send an authorization verification response message to the order processing server.

[0238] In some embodiments, the receiving module 601 can also be used to receive a payment transfer notification message sent by the payee resource server, the payment transfer notification message including payment transfer result information;

[0239] The processing module 603 can also be used to update the fourth account data that matches the payer information in the payment message and the fifth account data that matches the payee information in the payment message in the preset account database when the payment transfer result information indicates that the payment transfer was successful, and record the update time of the fourth account data and the update time of the fifth account data.

[0240] In some examples, the sending module 602 can also be used to send a payment transfer notification message to the order processing server.

[0241] Figure 15 A schematic diagram of the structure of another embodiment of the management server provided in the third aspect of this application. Figure 15 and Figure 14 The difference is that, Figure 15 The management server shown may also include a verification module 604.

[0242] The processing module 603 can also be used to find the order transaction message corresponding to the payment message based on the order information and transaction party information in the payment message.

[0243] The checking module 604 can be configured to perform association checking on the order information and the transaction party information in the payment message and the order information and the transaction party information in the corresponding order transaction message, and determine whether the order information and the transaction party information in the payment message satisfy the payment permission condition.

[0244] The processing module 603 is further configured to terminate the payment process indicated by the payment message in a case where the association checking fails and / or the order information and the transaction party information in the payment message do not satisfy the payment permission condition.

[0245] The sending module 602 can be configured to send the payment message to the payee resource server in a case where the association checking succeeds and the order information and the transaction party information in the payment message satisfy the payment permission condition.

[0246] In some embodiments, the receiving module 601 can be further configured to receive an order processing message sent by the order handling server.

[0247] The order processing message includes logistics information associated with the order message and / or collection voucher information associated with the order message.

[0248] The sending module 602 can be further configured to send the order processing message to the payer resource server, so that the payer resource server sends the order processing message to the payer terminal device.

[0249] The fourth aspect of the present application provides a payer resource server. Figure 16 An embodiment of the payer resource server provided by the fourth aspect of the present application is shown in a structural schematic diagram. As shown in the structural schematic diagram, the payer resource server 700 can include a receiving module 701, a sending module 702, and a processing module 703. Figure 16

[0250] The receiving module 701 can be configured to receive an order transaction message sent by a management server.

[0251] The order transaction message is sent by an order handling server to the management server, and the order transaction message includes order information and transaction party information, and the transaction party information includes payer information and payee information.

[0252] The sending module 702 can be configured to send an order review request message to a payer terminal device indicated by the payer information.

[0253] The order review request message includes order information and transaction party information.

[0254] The processing module 703 can be configured to deduct a transaction amount indicated by the order information from a payer account indicated by the payer information in a case where an order review confirmation message sent by the payer terminal device is received.

[0255] ​The payer's account is a corporate account.

[0256] The sending module 702 can also be used to send a payment message to the management server, so that the management server sends a payment message to the payee resource server indicated by the payee information, and transfers the transaction funds indicated by the order information to the payee account indicated by the payee information.

[0257] Payment messages include order information and transaction details.

[0258] In this embodiment, the payer resource server can receive order transaction messages from the management server and then spontaneously send an order review request message to the payer terminal device, requesting the order to be reviewed. Based on the order review confirmation message received from the payer terminal device, the payer resource server can determine that the payer account (i.e., the enterprise account) is authorized to continue the payment process. The payer resource server then sends a payment message to the management server, which in turn sends a payment message to the payee resource server, instructing the payee resource server to transfer the corresponding funds to the payee account. This achieves payment through the enterprise account, and the process requires virtually no manual intervention, reducing the time spent on payment and improving the efficiency of enterprise payments.

[0259] Furthermore, during the payment process, order transaction messages, order review confirmation messages, and payment messages can include order information and transaction party information, combining order information with transaction information. This avoids the separation of order information and transaction information, ensuring that the information is closely linked and making it easier to manage and query.

[0260] Figure 17 A schematic diagram of another embodiment of the payer resource server provided in the fourth aspect of this application. Figure 17 and Figure 16 The difference is that the payer resource server 700 may also include a verification module 704.

[0261] The verification module 704 can be used to perform permission verification based on the order transaction message, obtain permission verification result information, and generate permission verification response message based on the permission verification result information.

[0262] The permission verification response message includes permission verification result information.

[0263] The sending module 702 can also be used to send an authorization verification response message to the management server, so that when the authorization verification result information indicates that the authorization verification is successful, the management server updates the third account data that matches the payee information in the preset account database and records the update time of the third account data.

[0264] In some embodiments, the receiving module 701 can also be configured to receive an order processing message sent by the management server.

[0265] The order processing message comprises logistics information associated with the order information and / or payment receipt information associated with the order information.

[0266] The sending module 702 can also be configured to send the order processing message to the payer terminal device.

[0267] The fifth aspect of the present application further provides a management server. Figure 18 An embodiment of the management server provided by the fifth aspect of the present application is shown in FIG. 8. As shown in FIG. 8, the management server 800 comprises a memory 801, a processor 802, and a computer program stored in the memory 801 and executable on the processor 802. Figure 18

[0268] In one example, the processor 802 can comprise a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement one or more embodiments of the present application.

[0269] The memory 801 can comprise a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Therefore, generally, the memory comprises one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors) it is operable to perform operations described with reference to the enterprise account payment method according to the first aspect of the present application.

[0270] The processor 802 runs a computer program corresponding to the executable program code stored in the memory 801 by reading the executable program code, for implementing the enterprise account payment method in the embodiments of the first aspect described above.

[0271] In one example, the management server 800 can further comprise a communication interface 803 and a bus 804. As shown in FIG. 8, the memory 801, the processor 802, and the communication interface 803 are connected through the bus 804 and complete communication therebetween. Figure 18

[0272] ​​The communication interface 803 is mainly configured to implement communication between the modules, devices, units and / or equipment in the embodiments of the present application. The input device and / or the output device can also be connected through the communication interface 803.

[0273] The bus 804 includes hardware, software, or both, that couples components of the management server 800 to each other in the management server 800. By way of example and not limitation, the bus 804 can include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or another suitable bus or a combination of two or more of these. Where appropriate, the bus 804 can include one or more buses. Although the present application is described and illustrated with a particular bus, it is not intended to be limited to this arrangement.

[0274] The sixth aspect of the present application further provides a payee resource server. Figure 19 An embodiment of the payee resource server provided by the sixth aspect of the present application is shown in a structural schematic diagram. As shown in the figure, the payee resource server 900 includes a memory 901, a processor 902, and a computer program stored in the memory 901 and executable on the processor 902. Figure 19

[0275] In one example, the processor 902 described above can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured to implement one or more integrated circuits of the embodiments of the present application.​

[0276] The memory 901 can include a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Thus, generally, the memory includes one or more tangible (non-transitory) computer-readable storage medium (e.g., a memory device) encoded with software including computer-executable instructions that, when executed (e.g., by one or more processors), are operable to perform the operations described with reference to the enterprise account payment method according to the second aspect of the present application.

[0277] The processor 902 runs a computer program corresponding to the executable program code stored in the memory 901 to implement the enterprise account payment method in the above-described embodiments of the second aspect, by reading the executable program code.

[0278] In one example, the payer resource server 900 can further include a communication interface 903 and a bus 904. As shown, the memory 901, the processor 902, and the communication interface 903 are connected through the bus 904 and complete communication with each other. Figure 19

[0279] The communication interface 903 is mainly used to realize the communication between the modules, devices, units, and / or equipment in the embodiments of the present application. The input device and / or the output device can also be accessed through the communication interface 903.

[0280] The bus 904 includes hardware, software, or both, which couples the components of the payer resource server 900 to each other. By way of example, and not limitation, the bus 904 can include an Accelerated Graphics Port or other graphics bus, an Advanced Graphics Port bus, a front-side bus, a HyperTransport interconnect, an industry standard architecture bus, an InfiniBand interconnect, a low pin count bus, a memory bus, a Micro Channel Architecture bus, a Peripheral Component Interconnect bus, a PCI-Express bus, a Serial Advanced Technology Attachment bus, a Video Electronics Standards Association local bus, or another suitable bus or a combination of two or more of these. Where appropriate, the bus 904 can include one or more buses. Although the present application describes and illustrates a particular bus, the present application contemplates any suitable bus or interconnect.

[0281] The seventh aspect of the present application provides an enterprise account payment system. The enterprise account payment system can include the management server and the payer resource server in the above-described embodiments, and the specific content can be referred to the related description in the above-described embodiments, which will not be described here.

[0282] ​In some examples, the enterprise account payment system described above can further include a payee resource server, details of which can be found in the relevant description of the above embodiments, which will not be repeated here.

[0283] In some examples, the enterprise account payment system described above can further include an order receiving server, details of which can be found in the relevant description of the above embodiments, which will not be repeated here.

[0284] In some examples, the enterprise account payment system described above can further include a payee terminal device and a payee terminal device, details of which can be found in the relevant description of the above embodiments, which will not be repeated here.

[0285] In some examples, the enterprise account payment system described above can further include a business platform server, details of which can be found in the relevant description of the above embodiments, which will not be repeated here.

[0286] The eighth aspect of the present application also provides a computer readable storage medium, which stores computer program instructions. When the computer program instructions are executed by a processor, the enterprise account payment method in the embodiments of the first aspect or the enterprise account payment method in the embodiments of the second aspect can be implemented, and the same technical effects can be achieved. To avoid repetition, details will not be repeated here. The computer readable storage medium can include a non-transitory computer readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which is not limited here.

[0287] It should be clear that each of the embodiments in the specification is described in a progressive manner, and the same or similar parts between each embodiment can be referred to each other. Each embodiment focuses on the differences from other embodiments. For the management server embodiment, the payee resource server embodiment, the system embodiment, and the computer readable storage medium embodiment, the relevant parts can be found in the description of the method embodiment. The present application is not limited to the specific steps and structures described above and shown in the drawings. Those skilled in the art can make various changes, modifications and additions, or change the order of the steps, after understanding the spirit of the present application. Moreover, in order to be brief, the detailed description of the known method technology is omitted.

[0288] The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other processing device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other processing device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. Alternatively, computer program implemented steps can be

[0289] Those skilled in the art will understand that the embodiments described above are merely exemplary and not limiting. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Those skilled in the art will understand and appreciate other variations of the disclosed embodiments upon studying the drawings, the specification and the claims. In the claims, the term "comprising" does not exclude other devices or steps; the term "one" does not exclude a plurality; the term "first", "second" etc. do not imply any order; the terms "first", "second" etc. are used to name the names and not to indicate any specific order. Any reference signs in the claims should not be construed as limiting the scope of the claims. The functions of a plurality of parts can be carried out by a single hardware or software module. The fact that certain technical features appear in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A corporate account payment method, characterized in that, Applied to a management server, the method includes: Receive order transaction messages sent by the order acceptance server. The order transaction messages include order information and transaction party information, and the transaction party information includes payer information and payee information. The order transaction message is sent to the payer resource server indicated by the payer information, so that the payer resource server sends an order review request message to the payer terminal device indicated by the payer information. The order review request message includes the order information and the transaction party information. The payer resource server belongs to the payer account management institution, and the payer terminal device is logged into a payer account. When the payer resource server deducts the transaction amount indicated by the order information from the payer account indicated by the payer information in response to the order review confirmation message sent by the payer terminal device, the payer resource server receives a payment message sent in response to the order review confirmation message. The payment message includes the order information and the transaction information, and the payer account is a corporate account. The payment message is sent to the payee resource server indicated by the payee information, so that the payee resource server transfers the transaction funds indicated by the order information to the payee account indicated by the payee information. The payee resource server belongs to the payee account management organization. The payment message sent by the management server to the payee resource server does not require the order acceptance server to trigger the management server to send it.

2. The method according to claim 1, characterized in that, After receiving the order transaction message sent by the order acceptance server, the following is also included: Search the preset account database for the first account data that matches the payee information; If the first account data is not found in the account database, an identity verification request message is sent to the payee resource server so that the payee resource server can verify the account identity of the payee information. If the account identity verification is successful, the system receives second account data that matches the payee information sent by the payee resource server. The second account data is stored in the account database, and the update time of the second account data is recorded; Sending the order transaction information to the payer resource server indicated by the payer information includes: If the account identity verification is successful, the order transaction information is sent to the payer resource server indicated by the payer information.

3. The method according to claim 2, characterized in that, Also includes: If the first account data is found in the account database, determine whether the account status in the first account data is active. Sending the order transaction information to the payer resource server indicated by the payer information includes: If the account status in the first account data is active, the order transaction information is sent to the payer resource server indicated by the payer information.

4. The method according to claim 1, characterized in that, After sending the order transaction message to the payer resource server indicated by the payer information, the process also includes: The system receives an authorization verification response message sent by the payment party's resource server. The authorization verification response message is obtained by the payment party's resource server through authorization verification based on the order transaction message. The authorization verification response message includes authorization verification result information. If the permission verification result indicates that the permission verification was successful, update the third account data in the preset account database that matches the payer information, and record the update time of the third account data.

5. The method according to claim 4, characterized in that, After receiving the permission verification response message sent by the payer's resource server, the method further includes: Send the permission verification response message to the order processing server.

6. The method according to claim 1, characterized in that, After receiving the payment message sent by the payer's resource server in response to the order review confirmation message, the method further includes: Based on the order information and transaction party information in the payment message, locate the order transaction message corresponding to the payment message; The order information and transaction party information in the payment message are correlated and verified with the order information and transaction party information in the corresponding order transaction message; Determine whether the order information and the transacting party information in the payment message meet the payment authorization conditions; If the association verification fails and / or the order information or the transaction party information in the payment message does not meet the payment permission conditions, the payment process indicated by the payment message shall be terminated. Sending the payment message to the payee resource server indicated by the payee information includes: If the association verification is successful and the order information and transaction party information in the payment message meet the payment permission conditions, the payment message is sent to the payee resource server.

7. The method according to claim 1, characterized in that, After sending the payment message to the payee resource server indicated by the payee information, the method further includes: Receive a payment transfer notification message sent by the payee's resource server, the payment transfer notification message including payment transfer result information; When the transfer result information indicates that the transfer was successful, update the fourth account data that matches the payer information in the payment message and the fifth account data that matches the payee information in the payment message in the preset account database, and record the update time of the fourth account data and the update time of the fifth account data.

8. The method according to claim 7, characterized in that, After receiving the payment transfer notification message sent by the payee's resource server, the method further includes: Send the payment transfer notification message to the order processing server.

9. The method according to claim 1, characterized in that, After sending the payment message to the payee resource server indicated by the payee information, the method further includes: Receive an order processing message sent by the order acceptance server, the order processing message including logistics information associated with the order message and / or payment voucher information associated with the order message; The order processing message is sent to the payer resource server, so that the payer resource server sends the order processing message to the payer terminal device.

10. A corporate account payment method, characterized in that, Applied to a payer resource server, wherein the payer resource server belongs to a payer account management organization, the method includes: The system receives an order transaction message sent by the management server. The order transaction message is sent from the order acceptance server to the management server. The order transaction message includes order information and transaction party information. The transaction party information includes payer information and payee information. Send an order review request message to the payer terminal device indicated by the payer information. The order review request message includes the order information and the transaction party information. The payer terminal device is logged into a payer account. Upon receiving an order verification confirmation message from the payer's terminal device, the transaction amount indicated by the order information will be deducted from the payer's account indicated by the payer information, where the payer's account is a corporate account. A payment message is sent to the management server, causing the management server to send the payment message to the payee resource server indicated by the payee information, transferring the transaction funds indicated by the order information to the payee account indicated by the payee information. The payment message includes the order information and the transaction party information. The payee resource server belongs to the payee account management organization. The payment message sent by the management server to the payee resource server does not require the order acceptance server to trigger the management server to send it.

11. The method according to claim 10, characterized in that, After receiving the order transaction message sent by the management server, the following is also included: Perform permission verification based on the order transaction message to obtain permission verification result information; Based on the permission verification result information, a permission verification response message is generated, wherein the permission verification response message includes the permission verification result information; The permission verification response message is sent to the management server so that, if the permission verification result indicates that the permission verification is successful, the management server updates the third account data in the preset account database that matches the payee information and records the update time of the third account data.

12. The method according to claim 10, characterized in that, After sending the payment message to the management server, the process also includes: Receive an order processing message sent by the management server, the order processing message including logistics information associated with the order information and / or payment voucher information associated with the order information; The order processing message is sent to the payment party's terminal device.

13. A management server, characterized in that, include: The receiving module is used to receive order transaction messages sent by the order acceptance server. The order transaction messages include order information and transaction party information, and the transaction party information includes payer information and payee information. The sending module is used to send the order transaction message to the payer resource server indicated by the payer information, so that the payer resource server sends an order review request message to the payer terminal device indicated by the payer information. The order review request message includes the order information and the transaction information. The payer resource server belongs to the payer account management institution, and the payer terminal device is logged into a payer account. The receiving module is further configured to receive a payment message sent by the payer resource server in response to the order verification confirmation message when the payer resource server deducts the transaction amount indicated by the order information from the payer account indicated by the payer information in response to the order verification confirmation message sent by the payer terminal device. The payment message includes the order information and the transaction information, and the payer account is a corporate account. The sending module is further configured to send the payment message to the payee resource server indicated by the payee information, so that the payee resource server transfers the transaction funds indicated by the order information to the payee account indicated by the payee information. The payee resource server belongs to the payee account management organization. The payment message sent by the management server to the payee resource server does not require the order acceptance server to trigger the management server to send it.

14. A payer resource server, characterized in that, The payer's resource server belongs to the payer's account management organization, including: The receiving module is used to receive order transaction messages sent by the management server. The order transaction messages are sent from the order acceptance server to the management server. The order transaction messages include order information and transaction party information. The transaction party information includes payer information and payee information. The sending module is used to send an order review request message to the payer terminal device indicated by the payer information. The order review request message includes the order information and the transaction party information. The payer terminal device is logged into a payer account. The processing module is used to deduct the transaction amount indicated by the order information from the payer account indicated by the payer information, where the payer account is a corporate account, upon receiving an order review confirmation message sent by the payer terminal device. The sending module is further configured to send a payment message to the management server, so that the management server sends the payment message to the payee resource server indicated by the payee information, transferring the transaction funds indicated by the order information to the payee account indicated by the payee information. The payment message includes the order information and the transaction party information. The payee resource server belongs to the payee account management institution. The payment message sent by the management server to the payee resource server does not require the order acceptance server to trigger the management server to send it.

15. A management server, characterized in that, include: Processor and memory storing computer program instructions; When the processor executes the computer program instructions, it implements the enterprise account payment method as described in any one of claims 1 to 9.

16. A payer resource server, characterized in that, include: Processor and memory storing computer program instructions; When the processor executes the computer program instructions, it implements the enterprise account payment method as described in any one of claims 10 to 12.

17. A corporate account payment system, characterized in that, This includes the management server as described in claim 15 and the payer resource server as described in claim 16.

18. The system according to claim 17, characterized in that, Also includes: The payee resource server is used to receive payment messages sent by the management server, and to transfer the transaction funds indicated by the order information in the payment message to the payee account indicated by the payee information in the payment message.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the enterprise account payment method as described in any one of claims 1 to 12.

Images