CN116109314A - Enterprise payment method and device - Google Patents

Abstract

The embodiment of this specification provides an enterprise payment method and device. The method includes: the payment service platform receives the resource request form sent by the first business user, which includes the target order identifier, the amount of required resources and the expected arrival date; then, according to the target order identifier, determines the target from several transaction orders sent by the trading platform For transaction orders, the order information includes the amount of order resources to be paid and the agreed payment date, as well as the advance payment conditions set by the second enterprise user. days later; then, judge whether the preferential information determined based on the resource request form satisfies the above-mentioned advance payment conditions, and if it is judged to be satisfied, send an advance payment request to the second enterprise user, including the amount of resources to be paid in advance and the expected payment day. In this way, by optimizing the enterprise payment process, the service experience of the payer and the payee can be effectively improved.

Description

Enterprise payment method and device

technical field

One or more embodiments of this specification relate to the field of Internet communication technologies, and in particular, to an enterprise payment method and device.

Background technique

Enterprise payment involves communication and interaction between multiple different platforms, and the amount paid by enterprises is often high or even huge. However, the existing enterprise payment process is difficult to meet the higher requirements in practical applications.

Therefore, an optimization solution is needed, which can improve the flexibility and convenience of enterprise payment while ensuring the safety and reliability of enterprise payment, so as to fully improve the experience of all interacting parties in the enterprise payment process.

Contents of the invention

The embodiment of this specification describes an enterprise payment method and device, which can meet higher requirements in practical applications.

According to the first aspect, an enterprise payment method is provided, which is executed by the payment service platform, including: receiving several transaction orders sent by the trading platform, each order has an order identifier; receiving a resource request form sent by the first enterprise user, including the target The order identifier, the required amount of resources, and the expected arrival date for the required amount of resources; according to the target order identifier, determine the target transaction order from the plurality of transaction orders; the target transaction order is based on the first enterprise The user is the supplier, and the second enterprise user is the purchaser; the order information of the target transaction order includes the order resource amount to be paid and the agreed payment date, the order resource amount is not less than the required resource amount, and the agreed The payment date is after the expected arrival date; judging whether the preferential information determined based on the resource request form satisfies the advance payment condition, and the advance payment condition is set by the second enterprise user; if it is judged to be satisfied , sending an advance payment request to the second enterprise user, including an advance payment resource amount and the expected arrival date.

In one embodiment, the method further includes: when it is judged that it is not satisfied, sending expected discount information that meets the advance payment condition to the first enterprise user.

In one embodiment, the preferential information includes a discount rate, and the advance payment condition includes an expected rate of return; wherein, judging whether the preferential information satisfies the advance payment condition includes: and the discount rate to determine the actual rate of return; determine whether the actual rate of return has reached the expected rate of return.

In a specific embodiment, the resource request includes the preferential information.

In a specific embodiment, the discount rate is calculated based on the required resource quantity and the ordered resource quantity.

In a specific embodiment, the advance payment request further includes the actual rate of return.

In a specific embodiment, the determination of the actual rate of return is also based on the service fee collection rules set by the payment service platform.

In a more specific embodiment, after sending the advance payment request to the second enterprise user, the method further includes: receiving a service fee deducted from the payment resource amount; the payment resource amount is the second The resource amount paid by the enterprise user based on the advance payment request, and the service fee is determined based on the service fee charging rule.

In one embodiment, after sending the advance payment request to the second enterprise user, the method further includes: according to the amount of resources paid by the second enterprise user based on the advance payment request and the payment date, and the Create a payment order based on the order identifier of the above transaction order and the identifier of the resource request order.

According to the second aspect, there is provided an enterprise payment method, which is executed by a client bound to a first enterprise user, including: creating a resource request form, which includes a target order identifier, a required amount of resources, and an expectation for the required amount of resources Arrival date; send the resource request to the payment service platform, so that the payment service platform determines the target transaction order from the transaction orders sent by the transaction platform, and the target transaction order takes the first enterprise user as the supplier , with the second enterprise user as the purchaser, the order information of the target transaction order includes the order resource amount to be paid and the agreed payment date, the order resource amount is not less than the required resource amount, and the agreed payment date is within the After the expected arrival date; and, judging whether the preferential information determined based on the resource request form satisfies the advance payment condition, and the advance payment condition is set by the second enterprise user.

In one embodiment, after sending the resource request form to the payment service platform, the method further includes: receiving a payment notification from the payment service platform, the payment notification including the payment request of the second enterprise user based on the payment in advance Payment information generated by payment; the advance payment request is determined by the payment service platform when it is judged to be satisfied, including the amount of advance payment resources and the expected arrival date.

In one embodiment, after sending the resource request form to the payment service platform, the method further includes: receiving from the payment service platform expected discount information that satisfies the payment in advance condition, and the expected discount information is determined by the payment service platform. The above-mentioned payment service platform is determined when it is judged that it is not satisfied.

According to a third aspect, there is provided an enterprise payment method, executed by a client terminal bound to a second enterprise user, comprising: sending a transaction request to a transaction platform, so that the transaction platform creates a corresponding transaction order and synchronizes it to the payment service platform, the transaction order takes the first enterprise user as the supplier and the second enterprise user as the purchaser, and the order information includes the order identifier, the amount of order resources to be paid and the agreed payment date; from the payment service platform receiving an advance payment request; the payment service platform determines that the preferential information determined based on the resource request satisfies the advance payment condition after receiving the resource request form sent by the first enterprise user. determined from below; the resource request form includes the target order identifier, the required resource amount, and the expected arrival date for the required resource amount, the target order identifier is the same as the order identifier, and the expected arrival date is at Before the agreed payment date, the demanded resource amount is not greater than the ordered resource amount; the advance payment condition is set by the second enterprise user.

In an embodiment, the method further includes: based on the advance payment request, making full or partial payment for the advance payment resource amount before the expected arrival date.

According to the fourth aspect, an enterprise payment device is provided, which is integrated into the payment service platform, including: a transaction order receiving unit configured to receive a number of transaction orders sent by the transaction platform, each order having an order identifier; a request form receiving unit configured to receiving the resource request form sent by the first enterprise user, which includes the target order identifier, the required resource amount, and the expected arrival date for the required resource amount; the target order determining unit is configured to, according to the target order identifier, obtain A target transaction order is determined from several transaction orders; the target transaction order takes the first enterprise user as the supplier and the second enterprise user as the purchaser; the order information of the target transaction order includes the amount of order resources to be paid and the agreed payment date, the order resource amount is not less than the required resource amount, and the agreed payment date is after the expected arrival date; the judging unit is configured to judge whether the preferential information determined based on the resource request form satisfies Payment conditions in advance, the payment conditions in advance are set by the second enterprise user; the payment request sending unit is configured to send an advance payment request to the second enterprise user if it is judged to be satisfied, including the payment in advance Amount of resources and said expected arrival date.

According to a fifth aspect, there is provided an enterprise payment device, which is integrated into a first enterprise client, the first enterprise client is bound to a first enterprise user, and the device includes: a request creation unit configured to create a resource request A single, which includes the target order identifier, the amount of required resources, and the expected arrival date for the required amount of resources; the request sending unit is configured to send the resource request to the payment service platform, so that the payment service platform from The target transaction order is determined from several transaction orders sent by the transaction platform, the target transaction order takes the first enterprise user as the supplier, and the second enterprise user as the purchaser, and the order information of the target transaction order includes the order to be paid The resource amount and the agreed payment date, the resource amount of the order is not less than the required resource amount, and the agreed payment date is after the expected arrival date; and, judging whether the preferential information determined based on the resource request form meets the requirements Payment conditions, the advance payment conditions are set by the second enterprise user.

According to the sixth aspect, an enterprise payment device is provided, which is integrated into a second enterprise client, the second enterprise client is bound to a second enterprise user, and the device includes: a transaction request sending unit configured to send a transaction request to the transaction platform Sending a transaction request, so that the transaction platform creates a corresponding transaction order and synchronizes it to the payment service platform, the transaction order uses the first enterprise user as the supplier, and the second enterprise user as the purchaser, and the order information Including the order identifier, the amount of order resources to be paid and the agreed payment date; the payment request receiving unit is configured to receive an advance payment request from the payment service platform; the advance payment request is received by the payment service platform after receiving the first After the enterprise user sends the resource request form, it is determined that the preferential information determined based on the resource request form satisfies the conditions for payment in advance; the resource request form includes the target order identifier, the amount of required resources and the The expected arrival date of the resource amount, the target order identifier is the same as the order identifier, the expected arrival date is before the agreed payment date, and the required resource amount is not greater than the order resource amount; the advance The payment conditions are set by the second enterprise user.

According to a seventh aspect, there is provided a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed in a computer, it causes the computer to execute the method of the first aspect, the second aspect or the third aspect.

According to an eighth aspect, there is provided a computing device, including a memory and a processor, wherein executable code is stored in the memory, and when the processor executes the executable code, the first aspect, the second aspect or the third aspect are realized. aspects of the method.

By adopting the enterprise payment method and device provided by the embodiment of this specification, while ensuring the safety and reliability of enterprise payment, the flexibility and convenience of enterprise payment can be improved, thereby fully improving the experience of each enterprise user, payment service platform and other interacting parties in the enterprise payment process .

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For Those of ordinary skill in the art can also obtain other drawings based on these drawings without making creative efforts.

Figure 1 shows a schematic diagram of multi-party communication interaction in the enterprise payment process disclosed in the embodiment of this specification;

FIG. 2 shows a schematic diagram of multi-party communication interaction after instantiation based on FIG. 1;

Figure 3 shows a schematic diagram of the association of transaction orders, payment orders and resource requests;

Figure 4 shows an example implementation diagram of the payment business logic disclosed in this specification;

Fig. 5 shows another implementation example diagram of the payment business logic disclosed in this specification;

Fig. 6 shows a schematic structural diagram of an enterprise payment device integrated into a payment service platform disclosed in the embodiment of this specification;

Fig. 7 shows a schematic structural diagram of the enterprise payment device integrated in the first enterprise client disclosed in the embodiment of this specification;

Fig. 8 shows a schematic structural diagram of an enterprise payment device integrated in a second enterprise client disclosed in the embodiment of this specification.

Detailed ways

The solutions provided in this specification will be described below in conjunction with the accompanying drawings.

As mentioned above, the existing enterprise payment process is difficult to meet the higher requirements in practical applications. In a typical enterprise payment scenario, many core enterprises adopt the method of account payment when purchasing, that is, after the core enterprise places an order, the supplier will deliver the goods first, and the payment will be made after about 1-3 months. With the method of account payment, there is a long repayment period for suppliers, and there is a risk of capital loss.

Based on the observation and analysis of the above-mentioned enterprise payment scenarios, the embodiment of this manual discloses an optimization scheme for the enterprise payment process, which can simultaneously optimize the payment experience of multiple enterprise users such as suppliers and core enterprises, and improve the payment satisfaction of enterprise users .

Figure 1 shows a schematic diagram of the multi-party communication interaction in the enterprise payment process disclosed in the embodiment of this specification, wherein the multi-party interaction process shown includes: the second enterprise client submits to the payment service platform the advance payment conditions set for the transaction order; An enterprise client submits a resource demand form to the payment service platform, which includes the target transaction order number; the payment service platform determines the preferential information for the target transaction order based on the resource demand form, and then judges whether the preferential information meets the conditions for early payment, and then determines whether the preferential information meets the conditions for early payment. If satisfied, send an advance payment request to the second enterprise client, which includes the advance payment amount and the expected arrival date set by the first enterprise client.

The specific interaction steps involved in the above optimization solution are described below in conjunction with more embodiments.

FIG. 2 shows a schematic diagram of multi-party communication interaction instantiated based on FIG. 1 , where the multi-party includes a first enterprise client, a second enterprise client, a payment service platform, and a transaction platform.

The above-mentioned first enterprise client refers to the client that is bound to the first enterprise user, or in other words, the client that has logged in the account of the first enterprise user; similarly, the second enterprise client refers to the client that is bound to the second enterprise user. A specified client, or in other words, a client logged in with an account of the second enterprise user. It should be noted that the first/second enterprise client and the first/second enterprise user may be used interchangeably below; "first" in the first enterprise client and "second" in the second enterprise client, As well as similar terms elsewhere in the text, they are used to distinguish similar things, and do not have other functions such as sorting. In addition, the payment service platform and transaction platform can be independent of each other or integrated together.

As shown in Figure 2, the communication interaction process includes the following steps:

Step S210, the second enterprise client sends a transaction request to the transaction platform. In other words, the second enterprise user places an order on the trading platform.

In one embodiment, the transaction request may include: setting the first enterprise user as the supplier, setting the second enterprise user as the purchaser, the quantity of goods to be traded, the amount of transaction resources (such as the amount of resources per unit quantity of goods, or The total amount of resources for trading goods), the expected payment date (or the agreed payment date). It should be understood that the resource corresponding to the transaction resource amount is used to measure the value of the transaction goods, and the resource may be currency, or cloud storage space, or the usage time of the computing device, etc.

In another embodiment, the transaction request may also include an advance payment condition set by the second enterprise user for the transaction. In one example, the prepayment terms include an expected rate of return. In another example, the prepayment condition includes an expected purchase price for the next transaction. In yet another example, the prepayment condition includes a lead time for the next transaction.

Step S220, the trading platform creates a trading order corresponding to the trading request.

In one embodiment, the trading platform can review the transaction request first, and then create a transaction order after the review is passed. Exemplarily, the transaction platform forwards relevant information in the transaction request to the first enterprise user, and creates a transaction order after receiving a confirmation instruction from the first enterprise user.

In one embodiment, the order information of the transaction order may include the order identifier, the amount of order resources to be paid, the agreed payment date, the order creation date, transaction status (such as waiting for delivery from the supplier), etc. In another embodiment, the order information of the transaction order may also include the advance payment conditions set by the second enterprise user.

For example, see the transaction order shown in FIG. 3 , the order information includes order number, order amount, order date, expected payment date, expected rate of return and transaction status.

Step S230, the transaction platform sends several transaction orders to the payment service platform.

In one embodiment, the transaction platform can synchronize the transaction order created by it to the payment service platform in real time. In another embodiment, at the end of each time period, the transaction platform can synchronize the transaction orders created within the time period to the service platform. In a specific embodiment, the above-mentioned multiple parties may also include other enterprise clients, thus, before step S230, the trading platform may also create corresponding transaction orders based on the transaction requests sent by other enterprise clients, which is the same as that in step S220 The created transaction order is sent to the payment service platform together.

In this way, by performing this step, the transaction order in the transaction platform can be synchronized to the payment service platform.

In step S240, the first enterprise client creates a resource request form, and the resource request form includes a target order identifier, a required resource amount, and an expected arrival date for the required resource amount.

In an embodiment, the first enterprise client may determine the selected target transaction order according to the received selection instruction for the transaction order, and then determine the target order identifier of the target transaction order. It should be understood that the order quantity of the target transaction order can be one or more. For a clear and concise description, the following mainly describes the case where there is one target transaction order, and the case where there are multiple target transaction orders can be learned by simple analogy.

The above-mentioned required resource amount and expected arrival date can be set by the second enterprise user. It can be understood that the required resource amount is less than or equal to the order resource amount of the target transaction order, and the expected arrival date is before the agreed payment date of the target transaction order.

In one embodiment, the resource request form also includes preferential information. In one example, offer information may include a discounted rate. In another example, the discount information includes a discounted purchase price for the next transaction. In yet another example, the offer information may include an upper limit on lead times for the next transaction.

Exemplarily, referring to FIG. 3 , the resource request form is shown as a discount demand form, and the discount demand form includes demand order number, demand amount, discount ratio, expected due date, and demand status (such as open or closed).

Step S250, the payment service platform receives the resource request sent by the first enterprise client.

Step S260, the payment service platform determines the target transaction order from several transaction orders according to the target order identifier.

It can be understood that each of the several transaction orders has an order identifier, and the payment service platform can locate the target transaction order with the target order identifier according to the target order identifier in the resource request form.

Step S270, the payment service platform judges whether the preferential information determined based on the resource request form satisfies the condition of payment in advance.

In one embodiment, the resource request includes preferential information, at this time, the payment service platform can directly read the preferential information included in the resource request. In another embodiment, the payment service platform can determine the discount rate x according to the required resource amount a in the resource request form and the ordered resource amount b in the target transaction order. Exemplarily, x=1-a/b.

In one embodiment, the order information of the target transaction order includes payment conditions in advance, and at this time, the payment service platform can directly read it. In another embodiment, the payment service platform may inquire whether the second enterprise user has submitted the advance payment condition, and if so, obtain the submitted advance payment condition, and if not, remind the second enterprise user to set and submit.

Further, based on the obtained preferential information and advance payment conditions, it can be judged whether the former satisfies the latter. In one embodiment, the discount information includes the discount rate, and the advance payment condition includes the expected rate of return. At this time, the implementation of this step may include: first, determine the actual return based on the expected arrival date z, the agreed payment date c, and the discount rate x Rate Y. Exemplarily, the actual rate of return Y can be calculated using the following formula:

In a specific embodiment, the determination of the actual rate of return Y is also based on the service fee collection rules set by the payment service platform. In one example, the service fee charging rule includes charging a service fee of a fixed amount for the completion of the advance payment of each transaction order. In another example, the service charge collection rule includes a profit sharing rate w. Exemplarily, the actual rate of return Y can be calculated using the following formula:

From the above, the actual rate of return Y can be determined. Further, it is judged whether the actual rate of return Y reaches the expected rate of return y. It can be understood that if Y≥y, it can be determined that the preferential information satisfies the condition of payment in advance, and if Y<y, it can be determined that the preferential information does not meet the condition of payment in advance.

In another implementation situation, the preferential information includes the preferential purchase price p ₁ of the next transaction, and the advance payment condition includes the expected purchase price p ₂ of the next transaction. At this point, the implementation of this step may include: judging whether the preferential purchase price p ₁ is less than the expected purchase price p ₂ . It can be understood that if p ₁ ≤ p ₂ , it can be determined that the preferential information meets the condition of early payment, and if p ₁ >p ₂ , it can be determined that the preferential information does not meet the condition of early payment.

Based on the above, it is possible to realize the judgment on whether the preferential information satisfies the condition of payment in advance.

Further, the payment service platform can terminate the current process if it judges that it is not satisfied. In one embodiment, a request failure or request rejection notification may be sent to the first enterprise client. In an embodiment, expected discount information meeting the advance payment condition may be sent to the first enterprise client. Exemplarily, the expected discount rate x' can be calculated by the following formula as the expected preferential information.

On the other hand, when the payment service platform judges that it is satisfied, it executes step S280 to send an advance payment request to the second enterprise user, which includes the amount of resources paid in advance and the expected arrival date.

As for the resource amount paid in advance, in an embodiment, the resource amount required above may be directly determined as the resource amount paid in advance. In another embodiment, the resource amount paid in advance may be determined according to the required resource amount and the service fee collection rule. In a specific embodiment, the service fee collection rule includes charging a fixed amount of service fee for a single transaction order. At this time, the resource amount paid in advance is the sum of the required resource amount and the service fee. In another specific embodiment, the service fee collection rule includes the profit sharing rate w. At this time, the resource amount P paid in advance can be determined according to the required resource amount a, the discount rate x, and the profit sharing rate w.

In one embodiment, the actual rate of return Y is also included in the advance payment request.

According to another embodiment, after step S280 is performed, the above-mentioned communication interaction process may further include step S290, where the second enterprise user performs advance payment based on the advance payment request.

In an embodiment, the second enterprise user may make a one-off full payment for the advance payment resource amount included in the advance payment request before the expected arrival date (may include the day). In another embodiment, the second business user may make a partial payment for the resource amount paid in advance. In one example, the second enterprise user may pay in batches for the resource amount paid in advance.

In one embodiment, the amount of resources paid in advance is transferred to the account of the payment service platform, and after the service fee is deducted by the payment service platform, the remaining amount of resources is transferred to the account of the first enterprise user, and the first enterprise payment platform Send a refund notification. In another embodiment, the amount of resources paid in advance is transferred to the silent trading account created by the bank for the first enterprise user and the second enterprise user, and then the payment resource amount is divided into accounts and transferred to separate accounts of the payment service platform. and in the account of the first enterprise user.

Further, after step S290 is executed, the communication interaction process may further include: step S295, the payment service platform creates a payment order. In one embodiment, the payment order may include payment information, such as payment resource amount, payment date, service fee, payment status (such as valid or invalid), payment order number, and the like. In an embodiment, the payment order may also include a transaction order identifier and a resource demand sheet identifier. In one embodiment, the payment order may also include a payment rate of return, which is calculated according to the actual payment date.

For example, refer to Figure 3, where the payment order shown includes the payment order number, the order number of the transaction order, the demand order number of the discount demand order, the payment amount, the payment date, the payment rate of return, the fee, and the payment status .

To sum up, adopting the enterprise payment method disclosed in the embodiment of this manual can ensure the safety and reliability of enterprise payment while improving the flexibility and convenience of enterprise payment, thereby fully improving the interaction between each enterprise user and payment service platform in the enterprise payment process. experience.

The business logic involved in the enterprise payment process will be further introduced below in conjunction with Figure 4 and Figure 5 .

As shown in Figure 4, the discount demand form submitted by the supplier involves a transaction order, and the demand for payment is 180 yuan, while the transaction order is 200 yuan. The payment service platform (or service provider) can calculate the discount rate as 10. %. Therefore, the purchaser can pay part of the amount paid in advance, actually pay 95 yuan, write off the transaction 100 yuan, the service party draws 5 yuan service fee from the 95 yuan, and the remaining 90 yuan is paid back to the supplier in advance.

As shown in Figure 5, the discount demand form submitted by the supplier involves two transaction orders. It should be understood that the purchasers of these two transaction orders may be the same enterprise user or two different enterprise users. The total amount of the two transaction orders is 300 yuan, the refund demand amount of the discount demand form is 270 yuan, and the discount rate is 10%. For one of the transaction orders of 100 yuan, the purchaser actually paid 95 yuan to write off the entire transaction order. The service party took a service fee of 5 yuan from this payment, and the remaining 90 yuan was returned to the supplier in advance. For another transaction order of 200 yuan, the buyer actually paid 95 yuan, and wrote off half of the transaction order (100 yuan), and the service party also took 5 yuan service fee from this payment, and the remaining 90 Yuan is paid back to the supplier in advance. As a result, the supplier received a total of 180 yuan in advance.

Corresponding to the above enterprise payment method, the embodiment of this specification also discloses an enterprise payment device. Figure 6 shows a schematic structural diagram of an enterprise payment device integrated into a payment service platform disclosed in the embodiment of this specification, and the device 600 includes the following units:

The transaction order receiving unit 610 is configured to receive several transaction orders sent by the transaction platform, each order has an order identifier. The request receiving unit 620 is configured to receive a resource request sent by the first enterprise user, which includes a target order identifier, a required amount of resources, and an expected arrival date for the required amount of resources. The target order determining unit 630 is configured to determine a target transaction order from the plurality of transaction orders according to the target order identifier; the target transaction order uses the first enterprise user as the supplier and the second enterprise user as the supplier. Purchaser; the order information of the target transaction order includes the order resource amount to be paid and an agreed payment date, the order resource amount is not less than the required resource amount, and the agreed payment date is after the expected arrival date. The judging unit 640 is configured to judge whether the preferential information determined based on the resource request satisfies an advance payment condition, and the advance payment condition is set by the second enterprise user. The payment request sending unit 650 is configured to send an advance payment request to the second enterprise user if it is judged to be satisfied, which includes an advance payment resource amount and the expected arrival date.

In one embodiment, the apparatus 600 further includes an information sending unit 660 configured to send expected preferential information that meets the advance payment condition to the first enterprise user if it is determined that the condition is not satisfied.

In one embodiment, the preferential information includes a discount rate, and the advance payment condition includes an expected rate of return; the judging unit 640 is specifically configured to: determine the actual rate of return based on the expected arrival date, the agreed payment date, and the discount rate ; Judging whether the actual rate of return has reached the expected rate of return.

In one embodiment, the resource request form includes the preferential information.

In a specific embodiment, the discount rate is calculated based on the required resource quantity and the ordered resource quantity.

In a specific embodiment, the advance payment request further includes the actual rate of return.

In a specific embodiment, the determination of the actual rate of return is also based on the service fee collection rules set by the payment service platform.

In a more specific embodiment, the apparatus 600 further includes a service fee receiving unit 670 configured to receive the service fee deducted from the amount of payment resources; The amount of resources paid for by the payment request, and the service fee is determined based on the service fee charging rule.

In one embodiment, the apparatus 600 further includes: a payment order creation unit 680 configured to, according to the amount of resources paid by the second enterprise user based on the payment in advance request and the payment date, and the order of the transaction order ID and ID of resource request form, create payment order.

Fig. 7 shows a schematic structural diagram of an enterprise payment device integrated with a first enterprise client disclosed in the embodiment of this specification, and the first enterprise client is bound to a first enterprise user. As shown in Figure 7, the device 700 includes:

The request creation unit 710 is configured to create a resource request, which includes a target order identifier, a required amount of resources, and an expected arrival date for the required amount of resources. The request sending unit 720 is configured to send the resource request to the payment service platform, so that the payment service platform determines the target transaction order from the transaction orders sent by the transaction platform, and the target transaction order is denoted by the first enterprise The user is the supplier, and the second enterprise user is the purchaser. The order information of the target transaction order includes the order resource amount to be paid and the agreed payment date, the order resource amount is not less than the required resource amount, and the agreed The payment date is after the expected arrival date; and, judging whether the preferential information determined based on the resource request satisfies an advance payment condition set by the second enterprise user.

In one embodiment, the apparatus 700 further includes: an information receiving unit 730, configured to receive from the payment service platform expected preferential information that satisfies the advance payment condition, and the expected preferential information is provided by the payment service platform in Determined when it is judged to be unsatisfactory.

Fig. 8 shows a schematic structural diagram of an enterprise payment device integrated in a second enterprise client disclosed in the embodiment of this specification, and the second enterprise client is bound to a second enterprise user. As shown in Figure 8, the device 800 includes:

The transaction request sending unit 810 is configured to send a transaction request to the transaction platform, so that the transaction platform creates a corresponding transaction order and synchronizes it to the payment service platform. 2. The enterprise user is the purchaser, and the order information includes the order identifier, the amount of order resources to be paid, and the agreed payment date. The payment request receiving unit 820 is configured to receive an advance payment request from the payment service platform; the advance payment request is determined by the payment service platform after receiving the resource request form sent by the first enterprise user based on the resource The preferential information determined by the request form is determined when the condition of payment in advance is met; the resource request form includes the target order identifier, the amount of required resources, and the expected arrival date for the amount of required resources, and the target order identifier is related to the requested resource amount. The order identifiers are the same, the expected arrival date is before the agreed payment date, and the required resource amount is not greater than the order resource amount; the advance payment condition is set by the second enterprise user.

In one embodiment, the apparatus 800 further includes a payment unit 830 configured to, based on the advance payment request, make full or partial payment for the advance payment resource amount before the expected arrival date.

According to another embodiment, there is also provided a computer-readable storage medium on which a computer program is stored. When the computer program is executed in a computer, the computer is instructed to execute the method described in conjunction with FIG. 2 .

According to yet another embodiment, there is also provided a computing device, including a memory and a processor, wherein executable code is stored in the memory, and when the processor executes the executable code, the implementation described in conjunction with FIG. 2 is implemented. method. Those skilled in the art should be aware that, in the above one or more examples, the functions described in the present invention may be implemented by hardware, software, firmware or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.

The specific embodiments described above have further described the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above descriptions are only specific embodiments of the present invention and are not intended to limit the scope of the present invention. Protection scope, any modification, equivalent replacement, improvement, etc. made on the basis of the technical solution of the present invention shall be included in the protection scope of the present invention.

Claims (19)

1. An enterprise payment method performed by a payment service platform, comprising:

receiving a plurality of trade orders sent by a trade platform, wherein each order has an order identifier;

receiving a resource request sheet sent by a first enterprise user, wherein the resource request sheet comprises a target order mark, a required resource amount and an expected account date aiming at the required resource amount;

determining a target trade order from the plurality of trade orders according to the target order identification; the target transaction order takes the first enterprise user as a supplier and takes a second enterprise user as a purchasing party; the order information of the target transaction order comprises an order resource amount to be paid and an appointed payment day, wherein the order resource amount is not less than the required resource amount, and the appointed payment day is after the expected account date;

judging whether the preferential information determined based on the resource request sheet meets an advanced payment condition, wherein the advanced payment condition is set by the second enterprise user;

and sending an early payment request to the second enterprise user under the condition that the early payment request is judged to be met, wherein the early payment request comprises the early payment resource quantity and the expected account date.

2. The method of claim 1, further comprising:

And if the payment condition is not met, sending expected preferential information meeting the payment condition in advance to the first enterprise user.

3. The method of claim 1, wherein the offer information comprises a discount rate and the advance payment condition comprises an expected return rate; wherein, judging whether the preferential information meets the advanced payment condition comprises:

determining an actual rate of return based on the expected billing day, the contracted payment day, and the discount rate;

and judging whether the actual return rate reaches the expected return rate.

4. A method according to any of claims 1-3, wherein the resource request ticket comprises the offer information.

5. The method of claim 3, wherein the discount rate is calculated based on the amount of demand resources and the amount of order resources.

6. A method according to claim 3, wherein the actual rate of return is also included in the advance payment request.

7. A method according to claim 3, wherein the determination of the actual rate of return is further based on a service fee charging rule set by the payment service platform.

8. The method of claim 7, wherein after sending an advance payment request to the second enterprise user, the method further comprises:

Receiving a service fee deducted from the amount of the payment resource; the payment resource amount is an amount of resources paid by the second enterprise user based on the advance payment request, and the service fee is determined based on the service fee charging rule.

9. The method of claim 1, wherein after sending an advance payment request to the second enterprise user, the method further comprises:

and creating a payment order according to the resource amount and the payment date paid by the second enterprise user based on the early payment request, and the order identification of the transaction order and the identification of the resource request order.

10. A business payment method performed by a client bound to a first business user, comprising:

creating a resource request sheet, wherein the resource request sheet comprises a target order mark, a required resource amount and an expected account date aiming at the required resource amount;

the resource request list is sent to a payment service platform, so that the payment service platform determines a target transaction order from a plurality of transaction orders sent by the transaction platform, the target transaction order takes a first enterprise user as a provider and a second enterprise user as a purchasing party, order information of the target transaction order comprises an order resource amount to be paid and an appointed payment date, the order resource amount is not less than the required resource amount, and the appointed payment date is after the expected payment date; and judging whether the preferential information determined based on the resource request sheet meets an advance payment condition, wherein the advance payment condition is set by the second enterprise user.

11. The method of claim 10, wherein after sending the resource request ticket to a payment services platform, the method further comprises:

receiving a payment notification from the payment service platform, the payment notification including payment information generated by the second enterprise user making a payment based on an advanced payment request; the advance payment request is determined by the payment service platform upon determining satisfaction, including an amount of advance payment resources and the expected checkout day.

12. The method of claim 10, wherein after sending the resource request ticket to a payment services platform, the method further comprises:

expected preference information meeting the early payment condition is received from the payment service platform, the expected preference information being determined by the payment service platform if it is determined that the conditions are not met.

13. A business payment method performed by a client bound to a second business user, comprising:

sending a transaction request to a transaction platform so that the transaction platform creates a corresponding transaction order and synchronizes the transaction order to a payment service platform, wherein the transaction order takes a first enterprise user as a provider and a second enterprise user as a purchasing party, and order information comprises an order identifier, an order resource amount to be paid and an appointed payment day;

Receiving an advance payment request from a payment service platform; the payment service platform receives a resource request list sent by a first enterprise user, and then determines that preferential information determined based on the resource request list meets the condition of payment ahead of time; the resource request list comprises a target order mark, a required resource amount and an expected account-arriving day aiming at the required resource amount, wherein the target order mark is the same as the order mark, and the required resource amount is not more than the order resource amount before the appointed payment day; the advance payment condition is set by the second enterprise user.

14. The method of claim 13, further comprising:

based on the advance payment request, full or partial payment is made for the advance payment resource amount prior to the expected checkout day.

15. An enterprise payment device integrated into a payment service platform, comprising:

the transaction order receiving unit is configured to receive a plurality of transaction orders sent by the transaction platform, and each order is provided with an order identifier;

the request list receiving unit is configured to receive a resource request list sent by a first enterprise user, wherein the resource request list comprises a target order mark, a required resource amount and an expected account date aiming at the required resource amount;

The target order determining unit is configured to determine a target trade order from the plurality of trade orders according to the target order identification; the target transaction order takes the first enterprise user as a supplier and takes a second enterprise user as a purchasing party; the order information of the target transaction order comprises an order resource amount to be paid and an appointed payment day, wherein the order resource amount is not less than the required resource amount, and the appointed payment day is after the expected account date;

a judging unit configured to judge whether or not the offer information determined based on the resource request sheet satisfies an advance payment condition set by the second business user;

and a payment request sending unit configured to send an advance payment request to the second enterprise user, where the advance payment request includes an advance payment resource amount and the expected account date, if the payment request is determined to be satisfied.

16. An enterprise payment apparatus integrated with a first enterprise client, the first enterprise client being bound to a first enterprise user, the apparatus comprising:

a request creation unit configured to create a resource request including a target order identification, a required resource amount, and an expected account date for the required resource amount;

A request list sending unit configured to send the resource request list to a payment service platform, so that the payment service platform determines a target transaction order from a plurality of transaction orders sent by the transaction platform, wherein the target transaction order takes a first enterprise user as a provider and a second enterprise user as a purchasing party, order information of the target transaction order comprises an order resource amount to be paid and an appointment payment day, the order resource amount is not less than the required resource amount, and the appointment payment day is after the expected payment day; and judging whether the preferential information determined based on the resource request sheet meets an advance payment condition, wherein the advance payment condition is set by the second enterprise user.

17. An enterprise payment apparatus integrated with a second enterprise client, the second enterprise client being bound to a second enterprise user, the apparatus comprising:

the transaction request sending unit is configured to send a transaction request to the transaction platform so that the transaction platform creates a corresponding transaction order and synchronizes the corresponding transaction order to the payment service platform, wherein the transaction order takes a first enterprise user as a supplier and takes a second enterprise user as a purchasing party, and order information comprises an order identifier, an order resource amount to be paid and an appointment payment day;

A payment request receiving unit configured to receive an advance payment request from a payment service platform; the payment service platform receives a resource request list sent by a first enterprise user, and then determines that preferential information determined based on the resource request list meets the condition of payment ahead of time; the resource request list comprises a target order mark, a required resource amount and an expected account-arriving day aiming at the required resource amount, wherein the target order mark is the same as the order mark, and the required resource amount is not more than the order resource amount before the appointed payment day; the advance payment condition is set by the second enterprise user.

18. A computer readable storage medium having stored thereon a computer program, wherein the computer program, when executed in a computer, causes the computer to perform the method of any of claims 1-14.

19. A computing device comprising a memory and a processor, wherein the memory has executable code stored therein, which when executed by the processor, implements the method of any of claims 1-14.

Images