Object processing method and system

Abstract

The embodiments of the present specification provide an object processing method and system, wherein the object processing method is applied to an object processing system, wherein the object processing system includes an object requester, an object provider and a resource receiver, wherein there is an association relationship between the object requester, the object provider and the resource receiver; the object provider creates a resource processing order for the target object based on an order request for the target object sent by the object requester, and sends the resource processing order to the resource receiver; the resource receiver generates a resource payment message based on the resource processing information carried in the resource processing order, returns the resource payment message to the object provider, and sends the resource payment message to the object requester based on the association relationship; the object requester processes the order request for the target object based on the resource payment message.

Description

Technical Field

[0001] The embodiments of the present specification relate to the field of computer technology, and in particular to an object processing method. Background Art

[0002] Distribution means establishing sales channels, that is, products are sold to consumers through certain channels. Distribution is the process of transferring products from the production site to the sales site. From this perspective, any sales method can be considered distribution. In the distribution process, distributors purchase goods in the traditional way and then sell them. The financial process of distributors will face challenges. At the same time, suppliers cannot perceive the orders purchased by users, the bills received, etc., and are only responsible for shipping to users. This requires suppliers to have a high degree of trust in distributors. Once a trust crisis occurs, suppliers will not be able to reconcile user orders, payment orders, and bills. Therefore, it will bring greater losses to suppliers. Summary of the invention

[0003] In view of this, the present specification provides an object processing method. One or more embodiments of the present specification also relate to an object processing system, a computing device, and a computer-readable storage medium to solve the technical defects existing in the prior art.

[0004] According to a first aspect of an embodiment of this specification, there is provided an object processing method, which is applied to an object processing system, wherein the object processing system includes an object requester, an object provider, and a resource receiver, wherein an association relationship exists between the object requester, the object provider, and the resource receiver;

[0005] The object provider creates a resource processing order for the target object based on the order request for the target object sent by the object requester, and sends the resource processing order to the resource receiver;

[0006] The resource receiver generates a resource payment message based on the resource processing information carried in the resource processing order, and returns the resource payment message to the object provider, and

[0007] Sending the resource payment message to the object requester based on the association relationship;

[0008] The object requester processes the order request for the target object based on the resource payment message.

[0009] According to a second aspect of an embodiment of this specification, there is provided an object processing system, comprising an object requester, an object provider and a resource receiver, wherein an association relationship exists between the object requester, the object provider and the resource receiver;

[0010] The object provider is configured to create a resource processing order for the target object based on the order request for the target object sent by the object requester, and send the resource processing order to the resource receiver;

[0011] The resource receiver is configured to generate a resource payment message based on the resource processing information carried in the resource processing order, and return the resource payment message to the object provider, and

[0012] Sending the resource payment message to the object requester based on the association relationship;

[0013] The object requester is configured to process the order request for the target object based on the resource payment message.

[0014] According to a third aspect of an embodiment of this specification, a computing device is provided, including:

[0015] Memory and processor;

[0016] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions, wherein the processor implements the steps of the object processing method when executing the computer-executable instructions.

[0017] According to a fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the instructions are executed by a processor, the steps of the object processing method are implemented.

[0018] In one embodiment of the present specification, the object provider creates a resource processing order for the target object based on the order request for the target object sent by the object requester, and sends the resource processing order to the resource receiver; the resource receiver generates a resource payment message based on the resource processing information carried in the resource processing order, returns the resource payment message to the object provider, and sends the resource payment message to the object requester based on the association relationship; the object requester processes the order request for the target object based on the resource payment message.

[0019] Specifically, after the object provider receives the order request for the target object sent by the object requester, it can create a resource processing order for the target object and send the resource processing order to the resource receiver, so that the resource receiver can generate a resource payment message based on the resource processing order; at the same time, the object provider can also receive the resource payment message returned by the resource receiver, and can obtain the resource bill corresponding to the order, etc., and then the object requester can also process the order request for the target object based on the resource payment message. Through the above-mentioned set of general distribution methods of the object requester to the target object, it can ensure that the object provider can perceive the entire processing process of the current target object order, so that the supplier's user order, bill and resource accounts can be easily aligned to avoid trust risks between suppliers and distributors. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 This is a system architecture diagram of an object processing method provided by an embodiment of this specification applied to an object processing system;

[0021] Figure 2 is a flow chart of an object processing method provided by an embodiment of this specification;

[0022] Figure 3 It is a flow chart of a processing process of a distribution authorization relationship of an object processing method provided by an embodiment of this specification;

[0023] Figure 4 is a flowchart of a process of applying an object processing method provided by an embodiment of the present specification to an object processing system;

[0024] Figure 5 This is a flowchart of a process of a target user in a commodity purchase application of an object processing method provided by an embodiment of this specification;

[0025] Figure 6 is a schematic diagram of the structure of an object processing system provided by an embodiment of this specification;

[0026] Figure 7 It is a structural block diagram of a computing device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0027] Many specific details are described in the following description to facilitate a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of this specification, so this specification is not limited to the specific implementation disclosed below.

[0028] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0029] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0030] First, the terms involved in one or more embodiments of this specification are explained.

[0031] Distribution: refers to the establishment of sales channels, which refers to all companies and individuals who obtain ownership of a certain commodity or service and help transfer ownership during the process of transferring the commodity or service from the producer to the consumer.

[0032] ISV (Independent Software Vendors), third-party ISV can take over the mini-program account authorized by the merchant based on the use of authorization credentials, initiate interface calls to the server of the target network platform, and thus help merchants realize the development, management, review, and release of the above-mentioned merchant mini-programs.

[0033] When selling goods, suppliers can adopt the distribution model, but the financial process of suppliers will face great challenges. If a third-party platform is used for acquiring, the supplier is only responsible for shipping according to the delivery notice, which requires the supplier to have a high degree of trust in the distributor or the third-party platform. At the same time, it is not convenient for the supplier to reconcile the orders and bills of goods. For example, the bicycle industry regards cycling cards as the core sales project, hoping to make full use of the public domain resources of the third-party platform to sell cycling cards and improve the conversion rate of card sales. However, the main body of the card belongs to the merchant. According to the traditional thinking, there are two solutions. One is that the third-party platform acts as the acquiring entity, purchases a large number of cycling cards, sells them through procurement and sales, and the finance department settles the account for the merchant. After the user successfully purchases the card, the merchant is notified to issue the card. The other is that the merchant acts as the acquiring entity, and the third-party platform acts as the merchant's acquiring ISV. The third-party platform uses the commodity order system of the third-party platform to directly collect the money into the merchant's account on the third-party platform after the card is purchased. After the merchant confirms that the money has been received, the card is issued.

[0034] The above two solutions each face their own challenges. First, when the third-party platform acts as the acquiring entity, the procurement and sales model poses a great challenge to the financial process of the third-party platform. With two lines of income and expenditure, the income cannot be directly settled to the merchant. Second, the merchant acts as the acquiring entity and the third-party platform acts as the acquiring ISV. After the user's payment is successful, the merchant receives the money in the account of the third-party platform, but there is no acquiring notification. The merchant will rely on the order system of the third-party platform to send the card issuance notification, which poses a challenge to the trust of both parties and will result in the inability to align the merchant's user orders, bills, and money.

[0035] Based on this, the object processing method provided in the embodiment of this specification does not adopt the purchasing and sales method, but can also ensure the convenience of reconciliation of merchant user orders, payment orders, and bills, and thus abstract a set of universal payment solutions for commodity distribution.

[0036] In this specification, an object processing method is provided. This specification also relates to an object processing system, a computing device, and a computer-readable storage medium, which are described in detail one by one in the following embodiments.

[0037] Figure 1 A system architecture diagram of an object processing method provided according to an embodiment of the present specification applied to an object processing system is shown.

[0038] in, Figure 1 It includes an object requester A, an object provider B and a resource receiver C. It should be noted that there is an association relationship between the object requester A, the object provider B and the resource receiver C, and the object requester A, the object provider B and the resource receiver C implement an interaction method based on the association relationship.

[0039] In actual applications, object requester A can provide users with an order interface for the target object. Users can select order items in the order interface. Object requester A creates an order based on the order item, and sends the created resource processing order to object provider B. The resource processing order is sent to resource receiver C. Resource receiver C generates a collection message based on the resource processing order, and returns the collection message to object provider B and object requester A. Object requester A calls up the cash register of resource receiver C based on the received collection message, and the user completes the resource payment through object requester A. Finally, object provider A sends the target object to the user based on the payment result to complete the processing of the target object.

[0040] The object processing method provided in the embodiment of this specification notifies the object provider to create a resource processing order after the object requester creates an order, so that the resource receiver generates a collection message according to the resource processing order, and returns the collection message to the object requester and the object provider respectively. On the one hand, it is convenient for the subsequent object requester to process the target object according to the collection message, and on the other hand, it can ensure that the user order, resource processing order, and resource accounts of the object provider are aligned, and the target object is processed after receiving the payment success message.

[0041] Figure 2 A flowchart of an object processing method provided according to an embodiment of the present specification is shown, which specifically includes the following steps.

[0042] It should be noted that the object processing method is applied to an object processing system, which includes an object requester, an object provider and a resource provider, wherein an association relationship exists among the object requester, the object provider and the resource receiver.

[0043] Step 202: The object provider creates a resource processing order for the target object based on the order request for the target object sent by the object requester, and sends the resource processing order to the resource receiver.

[0044] Among them, the object provider can be understood as the merchant or business that provides goods to users; the object requester can be understood as the party that sells the merchant's goods through its own order system; the target object can be understood as the goods purchased by the user from the object requester; the resource recipient can be understood as a third-party platform that collects resources on behalf of the object provider.

[0045] In actual applications, the object provider can receive an order request for product A sent by the object requester. The object provider creates a resource processing order based on the order request, and at the same time, sends the resource processing order to the resource receiver, so that the subsequent resource receiver can receive the resource value for product A based on the resource processing order and complete the processing of the resource processing order.

[0046] Furthermore, the association relationship among the object requester, the object provider and the resource receiver is established before the object requester sends an order request to the object provider. Prior to this, the object requester and the object provider have an agreement on processing user orders to achieve full mutual communication between the three parties and complete the processing of the target object. Specifically, before the object provider creates a resource processing order for the target object based on the order request for the target object sent by the object requester, it also includes:

[0047] The object provider establishes an authorization relationship between the object requester and the object provider, and sends the authorization relationship to the resource receiver for storage.

[0048] It should be noted that the key point of the association relationship between the object requester, the object provider and the resource receiver is that the object provider needs to establish an authorization relationship between the object requester and the object provider. The authorization relationship can be understood as the object provider agreeing that the object requester sells the goods in its own order system, and the object provider is responsible for shipping to the user. In addition, the authorization relationship may also include the commission ratio between the object requester and the object provider. This embodiment does not impose any limitation on the specific content of the authorization relationship. Based on different application scenarios, the specific content of the authorization relationship is not the same.

[0049] In actual applications, after establishing the authorization relationship between the object requester and the object provider, the object provider may send the authorization relationship to the resource receiver for storage, so that the subsequent resource receiver can determine whether to return the acquisition message to the object requester based on the authorization relationship; in addition, it should be understood that the association relationship mentioned in this embodiment can be understood as the authorization relationship between the object requester and the object provider, and the authorization relationship is stored in the resource receiver.

[0050] The object processing method provided in the embodiment of this specification stores the authorization relationship between the object provider and the object requester established by the object provider to the resource receiver, so that the resource receiver can subsequently send a collection message corresponding to the resource processing order to the object requester based on the authorization relationship.

[0051] Furthermore, when establishing the authorization relationship between the object provider and the object requester, it is also necessary to establish a commission ratio between the object provider and the object requester. Specifically, the object provider establishes the authorization relationship between the object requester and the object provider, including:

[0052] The object provider receives the authorization request from the object requester, determines the object authorization ratio based on the authorization information carried in the authorization request, and sends the object authorization ratio to the object requester;

[0053] The object requester sends an authorization application to the object provider based on the object authorization ratio;

[0054] The object provider confirms the authorization relationship with the object requester based on the authorization application.

[0055] In actual applications, after receiving the authorization request from the object requester, the object provider will determine the object authorization ratio based on the authorization information carried in the authorization request, where the object authorization ratio can be understood as the commission ratio between the distributor and the supplier for the goods; the object provider can also send the object authorization ratio to the object requester, and the object requester will submit a formal authorization application to the object provider based on the object authorization ratio. After receiving the formal authorization application, the object provider determines the authorization relationship with the object requester.

[0056] It should be noted that the process of establishing the authorization relationship between the object provider and the object requester is not limited in this embodiment, and other authorization methods may be referred to to establish the authorization relationship between the object provider and the object requester.

[0057] The object processing method provided in the embodiment of this specification is that after the object authorization ratio is determined between the object provider and the object requester, an authorization relationship is formally signed with the object requester based on the object authorization ratio. After the authorization relationship is determined, the trust between the object provider and the object requester is guaranteed, thereby realizing the distribution processing of the goods.

[0058] The following combination Figure 3 ,Taking the authorization relationship between distributors and suppliers as an example, the process of establishing the authorization relationship is further explained. Figure 3 A flow chart of the processing process of a distribution authorization relationship of an object processing method provided in an embodiment of this specification is shown.

[0059] It should be noted that the object requester is the distributor, the object provider is the supplier, and the resource recipient is the third-party platform.

[0060] Step 302: The distributor communicates with the supplier regarding the distribution intention of the target product.

[0061] Step 304: The supplier determines the distributor to distribute the target product.

[0062] Step 306: The supplier agrees on a commission ratio with the distributor.

[0063] Step 308: The supplier generates an authorization application link based on the commission ratio and sends the authorization application link to the distributor.

[0064] Step 310: The distributor formally applies to the supplier for distribution according to the authorization application link.

[0065] Step 312: The supplier also sends the authorization application link to the third-party platform, and the third-party platform can generate a distribution authorization link.

[0066] Step 314: After receiving the distributor's formal application for distribution, the supplier agrees to the distributor's application.

[0067] Step 316: The supplier will save the authorization relationship and commission ratio agreed to by the distributor on the third-party platform.

[0068] The object processing method provided in the embodiments of this specification confirms the distribution relationship between the distributor and the supplier and agrees on the commission ratio, and then determines the authorization relationship between the distributor and the supplier to ensure that the target product is processed based on a fully trusted authorization relationship between the distributor and the supplier, thereby completing the processing of the target product.

[0069] In actual applications, the distributor may also have its own order system, so that the user can select the target product on the interface of the order system provided by the distributor. Specifically, before the object provider creates the resource processing order for the target object based on the order request for the target object sent by the object requester, the process further includes:

[0070] The object requester determines the order request of the target object in response to the target user sending the order processing instruction of the target object through the object processing interface of the object requester, and

[0071] The order request is sent to the object provider.

[0072] In actual applications, the object requester can display the target user with the orderable goods through the object processing interface. After the target user sends the target object's order processing instruction through the object processing interface, the object requester can respond to the order processing instruction, determine the target object's order request, and send the order request to the object provider. For example, the target user can visit the distributor's product sales page and select product A to place an order. After receiving the order instruction for product A, the distributor can create an order request for product A and send the order request to the supplier.

[0073] In the object processing method provided in the embodiments of this specification, the user selects the corresponding target object through the object processing interface of the object requester and sends an order processing instruction for the target object. The object requester can also determine the order request based on the order processing instruction and send the order request to the object provider, which can ensure that the object provider creates a resource processing order based on the received order request for the target object.

[0074] Step 204: the resource receiver generates a resource payment message based on the resource processing information carried in the resource processing order, returns the resource payment message to the object provider, and sends the resource payment message to the object requester based on the association relationship.

[0075] The resource processing information may be understood as the price that the target object needs to pay, the product number of the target object, detailed product information, etc., which is not further limited in this embodiment.

[0076] The resource payment message can be understood as the payment information involved in the target object that the user needs to pay, such as the user ID registered by the user on the third-party platform, the payment amount of the target object, etc. This embodiment does not make too many restrictions on this.

[0077] In actual applications, after the object provider sends the determined resource processing order to the resource receiver, the resource receiver can also generate a resource payment message based on the resource processing information carried in the resource processing order, wherein the resource payment message can be regarded as a collection message of the third-party platform. The object provider can clarify the payment information involved in the order based on the collection message, such as product identification, product amount, payment account, collection account, order creation time, etc. The specific information content in the collection message is not limited in this embodiment, and the information involved in the collection message may be different based on different application scenarios or different third-party platforms of the application.

[0078] Furthermore, the resource recipient returns the resource payment message to the object provider, and synchronously returns the resource payment message to the object requester based on the association relationship, so that the object provider can obtain the resource payment message of the target object and perceive the resource payment information and other contents. At the same time, it is convenient for the subsequent object requester to complete the processing of the order based on the resource payment message.

[0079] When the resource receiver sends the resource payment message to the object provider, the resource payment message can be directly returned according to the original request link. When the resource receiver sends the resource payment message to the object requester, it needs to be sent on the basis of determining that it has a certain authorization relationship, which also ensures the transaction security between the object provider and the object requester. Specifically, sending the resource payment message to the object requester based on the association relationship includes:

[0080] The resource receiver sends the resource payment message to the object requester based on the authorization relationship between the object requester and the object provider.

[0081] In actual applications, the resource receiver will not send the resource payment message directly to the object requester. The resource receiver can also determine whether there is a real authorization relationship between the object provider and the object requester based on the pre-stored authorization relationship. Furthermore, the resource receiver can locally query the pre-signed authorization relationship between the distributor and the supplier corresponding to the acquiring message. Only after confirming that there is an authorization relationship between the distributor and the supplier can the acquiring message be sent to the distributor.

[0082] It should be noted that the specific process of the third-party platform searching for the authorization relationship locally can be based on a pre-stored relationship list or determined in other ways. This embodiment does not impose any limitation on how to determine the authorization relationship between the distributor and the supplier.

[0083] Step 206: The object requester processes the order request of the target object based on the resource payment message.

[0084] After the object requester receives the resource payment message sent by the resource receiver, the object requester can further complete the processing of the order request for the target object. The user can complete the payment for the order of the target object in the order system of the object requester and then collect the target object.

[0085] In the case where the third-party platform serves as an acquiring institution, the user can directly pay the resource to the third-party platform in the order system of the object requester, thereby realizing that the user pays the object provider the amount corresponding to the target object; specifically, the object requester processes the order request of the target object based on the resource payment message, including:

[0086] The object requester sends a payment call request to the resource receiver based on the resource payment message;

[0087] The resource receiver processes the resources of the target object based on the payment call request, obtains the payment result of the target object, and returns the payment result to the object requester.

[0088] The payment call request can be understood as a cashier interface call request initiated to the resource recipient (third-party platform) to enable the user to complete the resource payment process at the object requesting party.

[0089] In specific implementation, the object requester may initiate a payment call request to the resource recipient based on the resource payment message sent by the resource recipient, so as to prompt the user to complete the resource payment on the object requester; the resource recipient processes the resources for the target object based on the payment call request, and obtains the payment result of the target object, wherein the payment result may be a successful payment of the user's order for the target object, or a failed payment of the order. Different payment results may affect the subsequent processing process, which will not be elaborated in detail in this embodiment; finally, the payment result also needs to be returned to the object requester to complete the processing of the order.

[0090] In actual applications, after the user confirms the order request in the distributor's order system, the distributor can call the cashier of the third-party platform to process the payment. After the user sends an instruction to confirm the payment, the third-party platform can complete the resource transfer process from the user account to the supplier account. The user can see the payment success interface in the distributor's order system, which means that the entire transaction process is completed.

[0091] The object processing method provided in the embodiment of this specification sends a payment call request to the resource receiver through the object requester, so that the processing of the target object resource can be completed in the order system of the object requester, which reflects the convenience of transactions.

[0092] Further, after receiving the payment result sent by the resource receiver, the object provider performs subsequent processing on the target object; specifically, after the object requester processes the order request of the target object based on the resource payment message, it also includes:

[0093] The object provider receives the payment result of the target object sent by the resource receiver, and processes the target object based on the payment result.

[0094] In specific implementation, the object provider can process the target object according to the payment result of the target object sent by the resource receiver, such as marking the target object, forming a subsequent delivery order, and delivering the goods, etc. In actual applications, the entire commodity purchase process is completed when the user receives the corresponding commodity. Before the supplier delivers the goods, it is necessary to determine whether the order has been paid, that is, whether the supplier's account has received the corresponding account. In this embodiment, it is shown whether the supplier account in the resource receiver has received the resource transfer amount from the user account. After determining that the entire resource transfer is successful, the supplier can proceed with the delivery process.

[0095] In the object processing method provided in the embodiment of this specification, the resource provider processes the target object after confirming that the payment result for the target object has been received, thereby ensuring that the user order, bill, and money accounts of the object provider are easily aligned.

[0096] In order to enable the user to purchase goods through the object provider, after the object provider receives the payment result of the user, if it is determined that the payment result is successful, the object provider may send the target object to the target user; specifically, processing the target object based on the payment result includes:

[0097] The object provider sends the target object to the target user based on the payment result.

[0098] In actual applications, in order to ensure the transaction security of delivery, the object provider can send the target object to the target user after confirming that the payment result sent by the resource recipient is a successful payment. The object provider can then align the user order, the acquiring order, and the money, so that the object provider can ensure transaction security and avoid financial risks without relying on the trust of other parties.

[0099] In summary, the object processing method provided in the embodiments of this specification, through the above-mentioned general payment solution for commodity distribution, users can place orders at distributors through the distributor's order system, notify suppliers to fulfill their contracts, and deposit resources directly into the supplier's resource account on the third-party platform without any trust risk issues.

[0100] The following combination Figure 4 , taking the application of the object processing method provided in this specification in commodity purchase as an example, the object processing method is further explained. Figure 4 A flowchart of a process of applying an object processing method provided by an embodiment of the present specification to an object processing system is shown, which specifically includes the following steps.

[0101] Step 402: The distributor creates product A in the product order system.

[0102] Step 404: The supplier also creates product A during synchronization.

[0103] Step 406: The distributor generates a sales page and displays it to the user through the product order system.

[0104] Step 408: The distributor creates order A for product A based on the product order instruction sent by the user through the sales page, and notifies the supplier to place the order.

[0105] Step 410: The supplier creates a product order A1 based on the distributor's order notification.

[0106] Step 412: The supplier creates a third-party platform acquiring order A2 based on the commodity order A1.

[0107] Step 414: The third-party platform receives the acquiring order A2 sent by the supplier and generates an acquiring message.

[0108] Step 416: The supplier receives the payment message sent by the third-party platform.

[0109] Step 418: The third-party platform queries the authorization relationship between the distributor and the supplier, and synchronously sends the acquiring message to the distributor based on the authorization relationship.

[0110] Step 420: The distributor calls up the third-party platform cashier according to the received acquiring message.

[0111] Step 422: The third-party platform deducts the user's account on the third-party platform based on the user's operation on the distributor's order system, and transfers the corresponding funds to the supplier's account.

[0112] Step 424: The distributor displays the order completion in the order system according to the payment result sent by the third-party platform.

[0113] The payment result may be a successful payment or a failed payment, and the order completion status displayed in the order system may also be different, which is not limited in this embodiment.

[0114] Step 426: The supplier prepares to ship product A to the user based on the payment result sent by the third-party platform.

[0115] Among them, the prerequisite for the supplier to ship product A to the user is that the third-party platform has completed the transfer of funds from the user account to the supplier account.

[0116] The object processing method provided in the embodiments of this specification is to create a collection order for the goods ordered by the supplier for the user at the distributor to the third-party platform, and the third-party platform will collect the order based on the authorization relationship. After the supplier determines that the third-party platform has successfully collected the order, it will process the goods, thereby ensuring that the three accounts of the supplier, namely the order, bill, and money, are quickly aligned, so that the supplier has no trust risk during the delivery process.

[0117] In addition, the following combination Figure 5 Describing the specific steps of the object processing method on the target user side; Figure 5 A flowchart of the processing process of a target user in a commodity purchase application of an object processing method provided in an embodiment of this specification is shown, which specifically includes the following steps.

[0118] Step 502: The target user visits the product sales page of the distributor.

[0119] Step 504: The target user selects product A on the product sales page and places an order.

[0120] Step 506: The target user confirms the order based on the acquiring order returned by the third-party platform.

[0121] Step 508: The target user confirms payment for the order of commodity A.

[0122] Step 510: The target user successfully pays in the distributor's order system.

[0123] Step 512: The target user receives commodity A.

[0124] It should be noted that the method provided in this embodiment is a commodity purchasing process performed by a target user in a distributor's order system, which is associated with the interaction between the distributor, supplier and third-party platform in the above embodiment and is not further limited here.

[0125] The object processing method provided in the embodiments of this specification enables users to complete the commodity purchase process through the distributor's order system. At the same time, it also ensures that after the user confirms the order and pays the order, the supplier can process the shipment based on the user's payment result.

[0126] Corresponding to the above method embodiment, this specification also provides an object processing system embodiment. Figure 6 FIG. 1 shows a schematic diagram of the structure of an object processing system provided by an embodiment of the present specification. Figure 6 As shown, the system includes: an object requester 602, an object provider 604, and a resource receiver 606, wherein there is an association relationship between the object requester 602, the object provider 604, and the resource receiver 606;

[0127] The object provider 604 is configured to create a resource processing order for the target object based on the order request for the target object sent by the object requester, and send the resource processing order to the resource receiver;

[0128] The resource receiver 606 is configured to generate a resource payment message based on the resource processing information carried in the resource processing order, and return the resource payment message to the object provider, and

[0129] Sending the resource payment message to the object requester based on the association relationship;

[0130] The object requester 602 is configured to process the order request for the target object based on the resource payment message.

[0131] The object provider 604 is further configured to establish an authorization relationship between the object requester and the object provider, and send the authorization relationship to the resource receiver for storage.

[0132] The object provider 604 is further configured to receive the authorization request from the object requester, determine the object authorization ratio based on the authorization information carried in the authorization request, and send the object authorization ratio to the object requester;

[0133] The object requester 602 is further configured to send an authorization application to the object provider based on the object authorization ratio;

[0134] The object provider 604 is further configured to confirm the authorization relationship with the object requester based on the authorization application.

[0135] The resource receiver 606 is further configured to send the resource payment message to the object requester based on the authorization relationship between the object requester and the object provider.

[0136] The object requester 602 is further configured to send a payment call request to the resource receiver based on the resource payment message;

[0137] The resource receiver 606 is further configured to process the resources of the target object based on the payment call request, obtain the payment result of the target object, and return the payment result to the object requester.

[0138] The object provider 604 is further configured to receive the payment result of the target object sent by the resource receiver, and process the target object based on the payment result.

[0139] The object requester 602 is further configured to respond to the target user sending an order processing instruction for the target object through the object processing interface of the object requester, determine the order request for the target object, and

[0140] The order request is sent to the object provider.

[0141] The object provider 604 is further configured to send the target object to the target user based on the payment result.

[0142] The object processing system provided in this specification can create a resource processing order for the target object after the object provider receives the order request for the target object sent by the object requester, and send the resource processing order to the resource receiver, so that the resource receiver can generate a resource payment message based on the resource processing order; at the same time, the object provider can also receive the resource payment message returned by the resource receiver, and can obtain the resource bill corresponding to the order, etc., and then the object requester can also process the order request for the target object based on the resource payment message. Through the above-mentioned set of general distribution methods of the object requester to the target object, it can be ensured that the object provider can perceive the entire processing process of the current target object order, so that the supplier's user order, bill and resource accounts are easy to align, so as to avoid trust risks between suppliers and distributors.

[0143] The above is a schematic scheme of an object processing system of this embodiment. It should be noted that the technical scheme of the object processing system and the technical scheme of the object processing method described above are of the same concept, and the details not described in detail in the technical scheme of the object processing system can be referred to the description of the technical scheme of the object processing method described above.

[0144] Figure 7 The block diagram of a computing device 700 according to an embodiment of the present specification is shown. The components of the computing device 700 include but are not limited to a memory 710 and a processor 720. The processor 720 is connected to the memory 710 via a bus 730, and the database 750 is used to store data.

[0145] The computing device 700 also includes an access device 740 that enables the computing device 700 to communicate via one or more networks 760. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 740 may include one or more of any type of network interface (e.g., a network interface card (NIC)) whether wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a World Wide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.

[0146] In one embodiment of the present specification, the above components of the computing device 700 and Figure 7 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 7 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0147] The computing device 700 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or PC. The computing device 700 may also be a mobile or stationary server.

[0148] The processor 720 is used to execute the following computer executable instructions, which implement the steps of the above-mentioned object processing method when executed by the processor.

[0149] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the object processing method described above are of the same concept, and the details not described in detail in the technical scheme of the computing device can be referred to the description of the technical scheme of the object processing method described above.

[0150] An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which can implement the steps of the above-mentioned object processing method when executed by a processor.

[0151] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the object processing method described above are of the same concept, and the details not described in detail in the technical scheme of the storage medium can be referred to the description of the technical scheme of the object processing method described above.

[0152] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0153] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0154] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0155] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0156] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to only the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can well understand and use this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. An object processing method, applied to an object processing system, wherein the object processing system includes an object requester, an object provider, and a resource receiver, wherein: There is an association relationship between the object requester, the object provider and the resource receiver; The object provider creates a resource processing order for the target object based on the order request for the target object sent by the object requester, and sends the resource processing order to the resource receiver; The resource receiver generates a resource payment message based on the resource processing information carried in the resource processing order, and returns the resource payment message to the object provider, wherein the resource payment message is a collection message, and the collection message is used by the object provider to determine the payment information involved in the resource processing order, and Sending the resource payment message to the object requester based on the association relationship; The object requester processes the order request for the target object based on the resource payment message.

2. The object processing method according to claim 1, before the object provider creates a resource processing order for the target object based on the order request for the target object sent by the object requester, the method further comprises: The object provider establishes an authorization relationship between the object requester and the object provider, and sends the authorization relationship to the resource receiver for storage.

3. The object processing method according to claim 2, wherein the object provider establishes an authorization relationship between the object requester and the object provider, comprising: The object provider receives the authorization request from the object requester, determines the object authorization ratio based on the authorization information carried in the authorization request, and sends the object authorization ratio to the object requester; The object requester sends an authorization application to the object provider based on the object authorization ratio; The object provider confirms the authorization relationship with the object requester based on the authorization application.

4. The object processing method according to claim 2 or 3, wherein sending the resource payment message to the object requester based on the association relationship comprises: The resource receiver sends the resource payment message to the object requester based on the authorization relationship between the object requester and the object provider.

5. The object processing method according to claim 4, wherein the object requester processes the order request of the target object based on the resource payment message, comprising: The object requester sends a payment call request to the resource receiver based on the resource payment message; The resource receiver processes the resources of the target object based on the payment call request, obtains the payment result of the target object, and returns the payment result to the object requester.

6. The object processing method according to claim 4, after the object requester processes the order request of the target object based on the resource payment message, further comprising: The object provider receives the payment result of the target object sent by the resource receiver, and processes the target object based on the payment result.

7. The object processing method according to claim 6, before the object provider creates a resource processing order for the target object based on the order request for the target object sent by the object requester, the method further comprises: The object requester determines the order request of the target object in response to the target user sending the order processing instruction of the target object through the object processing interface of the object requester, and The order request is sent to the object provider.

8. The object processing method according to claim 7, wherein processing the target object based on the payment result comprises: The object provider sends the target object to the target user based on the payment result.

9. An object processing system, comprising an object requester, an object provider and a resource receiver, wherein: There is an association relationship between the object requester, the object provider and the resource receiver; The object provider is configured to create a resource processing order for the target object based on the order request for the target object sent by the object requester, and send the resource processing order to the resource receiver; The resource receiver is configured to generate a resource payment message based on the resource processing information carried in the resource processing order, and return the resource payment message to the object provider, wherein the resource payment message is a collection message, and the collection message is used by the object provider to determine the payment information involved in the resource processing order, and Sending the resource payment message to the object requester based on the association relationship; The object requester is configured to process the order request for the target object based on the resource payment message.

10. A computing device comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the object processing method according to any one of claims 1 to 8 are implemented.

11. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the steps of the object processing method according to any one of claims 1 to 8.

Images