Service execution system, method and device, storage medium and electronic equipment

Abstract

The embodiment of the invention discloses a business execution system which can issue an electronic certificate used for executing UTC business to a payment account of a user directly through a non-accepting device and a server side which are used for providing payment service. In the embodiment of the invention, a retailer does not need to use an account specially used for executing the UTC service or a verification device to provide the UTC service for a user, thereby effectively improving the convenience of executing the UTC service, and reducing the cost of executing the UTC service.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a business execution system, method, apparatus, storage medium and electronic device. Background Technology

[0002] Under The Cap (UTC) is a common digital marketing campaign in the retail industry, often seen in beverages, dairy products, and snacks. After purchasing a product, users can open the bottle cap or packaging, scan the graphic code inside, and participate in winning a prize.

[0003] However, when users redeem prizes at retailers, retailers are usually required to have a dedicated account to log into the supplier's merchant system or a dedicated verification device to process the prizes. Therefore, improving the convenience of UTC transactions is an urgent issue that needs to be addressed. Summary of the Invention

[0004] This specification provides a business execution system, method, apparatus, storage medium, and electronic device to partially solve the problems existing in the prior art.

[0005] The embodiments in this specification adopt the following technical solutions: This specification provides a business execution system, which includes a user terminal, non-receiving devices deployed at retail stores, a merchant system of a target supplier, and a server; wherein: The non-receiving device is used to scan the graphic code on the target object to identify the service triggering information carried in the graphic code and send the service triggering information to the server. The server is used to determine the target supplier corresponding to the business triggering information and send the business triggering information to the merchant system of the target supplier. The merchant system of the target supplier is used to determine the target business rule hit by the business trigger information and the preset business rules based on the business trigger information and return the business execution information corresponding to the target business rule to the server. The server is also configured to generate an electronic credential for executing the target business based on the business execution information, and return the electronic credential to the non-accepting device; The non-receiving device is also used to receive and display the electronic certificate, and when conducting contactless communication with the user terminal, to obtain the user identifier of the user terminal based on the contactless communication and return the user identifier to the server. The server is also used to allocate the electronic voucher to the payment account corresponding to the user identifier.

[0006] This specification provides a business execution method applied to non-receiving devices deployed at retail stores, the method comprising: The non-receiving device scans the graphic code on the target object to identify the business trigger information carried in the graphic code, sends the business trigger information to the server, enables the server to determine the target supplier corresponding to the business trigger information, and sends the business trigger information to the merchant system of the target supplier, so that the merchant system of the target supplier can determine the target business rule hit by the business trigger information according to the business trigger information and the preset business rules, and return the business execution information corresponding to the target business rule to the server; Receive and display the electronic credentials generated by the server based on the business execution information for executing the target business; When conducting contactless communication with a user terminal, the user identifier of the user terminal is obtained based on the contactless communication, and the user identifier is returned to the server so that the server can allocate the electronic credential to the payment account corresponding to the user identifier.

[0007] This specification provides a business execution method, the method comprising: The server receives the graphic code on the target object scanned by the non-receiving device, identifies the service trigger information carried in the graphic code, and then sends the service trigger information. Identify the target supplier corresponding to the business triggering information; The business trigger information is sent to the merchant system of the target supplier, so that the merchant system of the target supplier can determine the target business rule that the business trigger information hits based on the business trigger information and the preset business rules. Receive business execution information corresponding to the target business rule returned by the merchant system of the target supplier; Based on the business execution information, generate an electronic certificate for executing the target business; The electronic credential is returned to the non-accepting device, so that the non-accepting device receives and displays the electronic credential. The non-receiving device receives the user identifier of the user terminal, which is acquired and sent by the user terminal based on contactless communication with the user terminal. The electronic credential is allocated to the payment account corresponding to the user identifier.

[0008] This specification provides a business execution apparatus for use with non-receiving devices deployed at retail stores, the apparatus comprising: The scanning module is used to scan the graphic code on the target object to identify the business trigger information carried in the graphic code, send the business trigger information to the server, enable the server to determine the target supplier corresponding to the business trigger information, and send the business trigger information to the merchant system of the target supplier, so that the merchant system of the target supplier can determine the target business rule hit by the business trigger information according to the business trigger information and the preset business rules, and return the business execution information corresponding to the target business rule to the server. The display module is used to receive and display the electronic credentials generated by the server based on the business execution information for executing the target business. The acquisition module is used to acquire the user identifier of the user terminal based on the contactless communication when conducting contactless communication with the user terminal, and return the user identifier to the server so that the server can allocate the electronic credential to the payment account corresponding to the user identifier.

[0009] This specification provides a business execution device, the device comprising: The receiving module is used to receive the graphic code on the target object scanned by the non-receiving device, identify the service trigger information carried in the graphic code, and then send the service trigger information. The determination module is used to determine the target supplier corresponding to the business triggering information; The sending module is used to send the business triggering information to the merchant system of the target supplier, so that the merchant system of the target supplier can determine the target business rule hit by the business triggering information based on the business triggering information and the preset business rules. The receiving module is further configured to receive business execution information corresponding to the target business rule returned by the merchant system of the target supplier; The generation module is used to generate electronic credentials for executing the target business based on the business execution information; The sending module is further configured to return the electronic credential to the non-accepting device, so that the non-accepting device receives and displays the electronic credential; The receiving module is further configured to receive the user identifier of the user terminal obtained and sent by the non-receiving device based on contactless communication with the user terminal; The allocation module is used to allocate the electronic voucher to the payment account corresponding to the user identifier.

[0010] This specification provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned business execution method.

[0011] This specification provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the aforementioned business execution method.

[0012] This specification provides a computer program product, which includes a computer program that, when executed by a processor, implements the aforementioned business execution method.

[0013] The above-described at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects: This specification discloses a business execution system. A non-accepting device deployed at a retailer scans a graphic code on a target object, identifies business trigger information, and sends it to a server. The server determines the target supplier corresponding to the business trigger information and sends it to the supplier's merchant system. The supplier's merchant system determines the target business rule matched by the trigger information and returns the corresponding business execution information to the server. The server generates an electronic credential for executing the target business based on the execution information and returns this credential to the non-accepting device for display. The non-accepting device obtains a user identifier through contactless communication with the user's terminal and returns it to the server. The server then allocates the electronic credential to the payment account corresponding to the user identifier. This system can directly issue electronic credentials for executing UTC (Usage-to-Consumer) transactions to users' payment accounts through the non-accepting device and the server used to provide payment services. Retailers do not need to use dedicated accounts or verification devices for UTC transactions, effectively improving the convenience and reducing the cost of UTC transactions. Attached Figure Description

[0014] The accompanying drawings, which are included to provide a further understanding of this specification and form part of this specification, illustrate exemplary embodiments and are used to explain this specification, but do not constitute an undue limitation thereof. In the drawings: Figure 1 This is a schematic diagram of the business execution system structure provided in the embodiments of this specification; Figure 2 A flowchart illustrating the business execution method provided in the embodiments of this specification; Figure 3 This is a schematic diagram illustrating the process by which a user executes a target service using electronic credentials, as provided in the embodiments of this specification. Figure 4 This is a schematic diagram of a first type of service execution device provided in the embodiments of this specification; Figure 5This is a schematic diagram of a second type of service execution device provided in the embodiments of this specification; Figure 6 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this specification. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of this specification clearer, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this specification.

[0016] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0017] Figure 1 This is a schematic diagram of the business execution system structure provided in the embodiments of this specification. The system includes: a user terminal, a non-receiving device deployed at a retailer, a merchant system of the target supplier, and a server.

[0018] User terminals, including various smart mobile terminals such as mobile phones and tablets used by users, are used for contactless communication with non-receiving devices. The contactless communication described in this specification includes, but is not limited to, contactless short-range communication, such as Near Field Communication (NFC).

[0019] A non-paying device, deployed at a retailer's premises, communicates with the retailer's merchant system to initiate payment requests to the server. When a user purchases goods at a retailer, the retailer's merchant system sends at least the total amount due for the purchased goods to the non-paying device, which can then initiate a payment request to the server based on this total amount. In the embodiments described in this specification, in addition to initiating payment requests to the server, the non-paying device can also scan the graphic code on the target object used to execute UTC services, identify the service triggering information carried in the graphic code, and trigger the execution of the UTC service.

[0020] The supplier's merchant system is used to determine whether the business trigger information identified by the non-receiving device matches a certain preset target business rule, that is, to determine whether the graphic code scanned by the non-receiving device is a winning code.

[0021] The server, located in the background, provides payment services to retailers. Upon receiving a payment request from a non-receiving device, it processes the payment using the user's payment account. In the embodiments described in this specification, in addition to providing the aforementioned payment services, the server can also be used to execute UTC transactions.

[0022] It should be noted that, according to the distribution model, in a supply chain, goods need to be manufactured and supplied by suppliers, distributed through wholesalers, and then flow to retailers, who in turn sell them to users. Therefore, the suppliers mentioned in this specification refer to merchants located at the source of the supply chain, also known as brand owners or brand owners, while the retailers are merchants in the supply chain that directly sell goods to users. The target business described in the embodiments of this specification is the UTC business. Generally speaking, the UTC business is a marketing activity provided by the suppliers; therefore, the supplier's merchant system will have pre-set rules for each target business and business execution information corresponding to each target business rule.

[0023] based on Figure 1 The system shown in this specification provides the following: Figure 2 The business execution method is shown.

[0024] Figure 2 The flowchart of the business execution method provided in the embodiments of this specification specifically includes the following steps: S200: The non-receiving device scans the graphic code on the target object to identify the service trigger information carried in the graphic code and sends the service trigger information to the server.

[0025] In the embodiments of this specification, the target object comes from goods provided by the target supplier, including the outer packaging of the goods or cards contained inside the goods, such as the inside of a beverage bottle cap or a small card contained in a bag of snacks. Any item that can carry a graphic code used to trigger the target business is acceptable. The graphic code can be a barcode, QR code, or any graphic code that can encode information.

[0026] After obtaining the target item, the user can take it to a retailer and scan the graphic code on the item using a non-receiving device. The non-receiving device then identifies the service trigger information carried in the graphic code. This service trigger information is set on the target item by the target supplier during the manufacturing of the product containing the target item, and it is used to trigger the target service offered by the supplier.

[0027] Specifically, the service triggering information can be the address used to access the target supplier's merchant system, which can be a Uniform Resource Locator (URL) address. This URL may contain a protocol field, the address field of the host where the accessed target resides (hereinafter referred to as the address field), the access path field of the accessed target on that host (hereinafter referred to as the path field), and additional parameter fields that need to be transmitted to that host (hereinafter referred to as the parameter field). The protocol field is the protocol used by the URL, such as HTTP; the address field is the address of the target supplier's merchant system; the path field is the path of the code in the target supplier's merchant system used to provide the aforementioned target service; and the parameter field can be a random number. This random number is randomly generated by the target supplier when manufacturing the product containing the target item and is used to determine the business rules of the target service matched by the graphic code on the target item.

[0028] Once a non-receiving device identifies the aforementioned service trigger information, it can send the service trigger information to the server.

[0029] S201: The server determines the target supplier corresponding to the business trigger information and sends the business trigger information to the merchant system of the target supplier.

[0030] In the embodiments described in this specification, after receiving service trigger information sent by a non-receiving device, the server can determine the target supplier corresponding to the service trigger information based on the URL address mentioned above. Specifically, the server can pre-store the correspondence between different address fields and suppliers. After receiving the URL address, the server can determine the supplier corresponding to the address field in the received URL address, which is the target supplier. After determining the target supplier, the server can send the service trigger information to the merchant system of the target supplier.

[0031] Of course, the server can also directly access the aforementioned URL address, which serves as the business trigger information. That is, it can encapsulate an access request (such as an HTTP request) based on this URL address, carrying the URL within the request, and then route the request to the target supplier's merchant system to access the URL address. Those skilled in the art should understand that regardless of the method used, as long as the aforementioned business trigger information can be sent to the target supplier's merchant system, it is acceptable.

[0032] Furthermore, the server can also preset a set of qualified merchants for the target supplier. This set includes the merchant identifiers of all retail merchants who can participate in the target service provided by the target supplier. In step S200, in addition to sending the service trigger information identified from the graphic code on the target object to the server, the non-receiving device also needs to send its own device identifier to the server. Therefore, in step S201, after receiving the service trigger information and device identifier from the non-receiving device, the server can, on the one hand, determine the target supplier corresponding to the service trigger information, and on the other hand, query the merchant identifier of the retailer corresponding to the device identifier. Then, it determines whether the merchant identifier of the retailer corresponding to the device identifier exists in the preset set of qualified merchants for the target supplier. If it does, it means that the retailer can execute the target service, and the service trigger information can be sent to the target supplier's merchant system. Otherwise, it means that the retailer is not qualified to execute the target service, and therefore the server refuses to send the service trigger information to the target supplier's merchant system.

[0033] S202: The merchant system of the target supplier determines the target business rule that the business trigger information hits based on the business trigger information and the preset business rules, and returns the business execution information corresponding to the target business rule to the server.

[0034] After receiving the aforementioned business trigger information, the target supplier's merchant system can determine the target business rule that the business trigger information hits based on the business trigger information and the preset business rules in the target supplier's merchant system.

[0035] Specifically, when the merchant system of the target supplier receives the URL address mentioned above as business trigger information, it can extract the parameter fields in the URL address to obtain the random number randomly generated by the target supplier when manufacturing the product containing the target item, and determine the target business rule that the business trigger information is triggered based on the random number.

[0036] For example, suppose the target supplier's merchant system has the following preset business rules: if the random number falls within the first value range, a discount of 2 yuan will be applied when purchasing the target product; if the random number falls within the second value range, a discount of 3 yuan will be applied. The target supplier's merchant system can determine the target business rule triggered by the business trigger information based on the value range of the random number it falls within, and then return the corresponding business execution information to the server. Continuing with the example, suppose the random number extracted from the parameter field of the received URL falls within the second value range. Then, the business execution information corresponding to the target business rule "if the random number falls within the second value range, a discount of 3 yuan will be applied when purchasing the target product" would be: a discount of 3 yuan will be applied when purchasing the target product.

[0037] That is, the business execution information includes the product information and discount rules of the target product corresponding to the target business rules.

[0038] If the target supplier's merchant system determines that the business trigger information does not match any preset business rules, it can return the judgment result that the business trigger information does not match any business rules to the server, and thus no longer execute subsequent steps.

[0039] S203: The server generates an electronic credential for executing the target business based on the business execution information, and returns the electronic credential to the non-accepting device.

[0040] After receiving the product information and discount rules of the target product, the server can generate an electronic voucher for executing the target business based on the business execution information and return it to the non-accepting device.

[0041] Specifically, after generating the electronic voucher, the server can set a corresponding validity period for it. This validity period can not exceed a preset time threshold, such as no more than 2 minutes. This is to ensure that once the target business is triggered by the business trigger information, the electronic voucher generated based on that information is used as quickly as possible. The goal is to ensure that the electronic voucher is issued to the user's payment account as soon as possible, and that the user is the one who uses the electronic voucher, thus preventing users from using the target object with the graphic code for illegal activities.

[0042] Furthermore, in the embodiments of this specification, the random numbers generated by the target supplier when manufacturing different goods containing the target item are also different. Therefore, in step S202, after the target supplier's merchant system obtains the business trigger information, it can first determine whether the electronic voucher generated based on the random number contained in the business trigger information has been cancelled. If it has been cancelled, it means that the graphic code on the target item has been used. Thus, it can return the judgment result that the business trigger information does not match any business rule to the server, so that the server will no longer execute step S203 and subsequent steps. If it has not been cancelled, it can return the business execution information corresponding to the target business rule matched by the business trigger information to the server through step S202.

[0043] S204: The non-receiving device receives and displays the electronic certificate.

[0044] In the embodiments described in this specification, the non-receiving device is an electronic device with a display device. After receiving the electronic credential sent by the server, the non-receiving device can display the electronic credential through the display device.

[0045] In step S203, the electronic voucher generated by the server may contain the product information and discount rules of the target product. After receiving the electronic voucher, the non-accepting device can display the product information and discount rules of the target product contained in the electronic voucher through the display device.

[0046] S205: When the non-receiving device communicates with the user terminal in a contactless manner, the user identifier of the user terminal is obtained based on the contactless communication, and the user identifier is returned to the server.

[0047] In the embodiments of this specification, a user can use their user terminal to establish contactless communication with the non-receiving device. The non-receiving device can then obtain the user identifier of the user terminal based on the contactless communication and return the user identifier to the server.

[0048] It should be noted that the user identifier and the user's payment account mentioned in the embodiments of this specification are not the same concept. The user identifier is only a login account used to enable the user terminal to log in to the server or the application corresponding to the server installed on the user terminal, while the payment account is the account corresponding to the user identifier used for payment, and the account stores the user's funds. To ensure payment security, the payment account itself is not transferred on the user terminal throughout the entire process of this specification.

[0049] S206: The server allocates the electronic voucher to the payment account corresponding to the user identifier.

[0050] After obtaining a user identifier sent by a non-receiving device, the server can query the payment account corresponding to that user identifier and allocate the electronic credential to the payment account corresponding to that user identifier. This allows the user to use the electronic credential in their payment account to perform the target transaction, such as... Figure 3 As shown.

[0051] Figure 3 The flowchart illustrating a user's execution of a target service using electronic credentials, as provided in the embodiments of this specification, specifically includes the following steps: S207: The retailer's merchant system obtains the product information and total amount to be paid for each product to be paid for, and sends the product information and total amount to be paid for each product to be paid for to the non-receiving device.

[0052] When users use electronic credentials to perform target transactions, the transaction execution system provided in this manual must also include the retailer's merchant system. Figure 1 (Not shown in the image), the retailer's merchant system communicates with the aforementioned non-receiving device.

[0053] pass Figure 2 The method shown allows users to bring the target item to a retailer while simultaneously purchasing other goods from that retailer; these goods are the items to be paid for.

[0054] When making payment for these items, users can first use a non-paying device at the retailer to scan the graphic code on the item to complete the payment. Figure 2 The process shown obtains electronic credentials for executing the target business. Then, when making payment for these goods, the retailer's merchant system can obtain the product information of each product through methods such as barcode scanners. Based on the amount to be paid for each product stored in the retailer's merchant system, the total amount to be paid for each product is determined. Finally, based on the communication connection between the retailer's merchant system and the non-accepting device, the product information of each product and the determined total amount to be paid are sent to the non-accepting device.

[0055] The product information of the goods to be paid for as described in this specification may include at least a product identifier used to uniquely identify the goods to be paid for.

[0056] S208: The non-receiving device sends a payment request to the server based on the user identifier of the user terminal, the product information, and the total amount to be paid.

[0057] After receiving the product information and total amount to be paid for each item from the merchant system of the retailer, the non-receiving device can obtain the user identifier of the user terminal, generate a payment request carrying the user identifier, product information of each item to be paid for, the total amount to be paid, and the retailer's payment account, and send the payment request to the server.

[0058] In step S208, when the non-receiving device obtains the user identifier of the user terminal, it can use... Figure 2 The user identifier of the user terminal obtained in step S205 can also be used to communicate with the user terminal again in a contactless manner, and the user identifier of the user terminal can be obtained based on this contactless communication. However, the user identifier obtained at this time is different from the one obtained in step S205. Figure 2 The user identifier obtained in step S205 may no longer be the same user identifier. Therefore, the user identifier obtained in step S205 can be referred to as the first user identifier, and the user identifier obtained in step S208 can be referred to as the second user identifier.

[0059] For ease of description, the following explanation will only take the example that the same user identifier is obtained in steps S205 and S208.

[0060] S209: In response to the payment request, the server queries the payment account corresponding to the user identifier based on the user identifier.

[0061] After receiving the payment request, the server can generate a payment order containing the total amount to be paid and the receiving account, based on the total amount to be paid and the receiving account contained in the payment request. At this time, the payment order has collected the total amount to be paid and the receiving account, but the payment account is still missing.

[0062] Therefore, the server can query the payment account corresponding to the user identifier based on the user identifier, and then add the queried payment account to the payment order. At this time, the payment order has collected the triple required for payment.

[0063] S210: When the electronic voucher is found in the payment account, determine whether each item to be paid contains a target item associated with the electronic voucher based on the product information. If so, redetermine the total amount to be paid for each item based on the electronic voucher, and use the payment account to pay the redetermined total amount to be paid.

[0064] When the server finds an electronic voucher in the payment account as queried in step S209, the server can determine whether each item to be paid for contains the target item associated with the electronic voucher based on the product information of each item to be paid for carried in the payment request. Specifically, the server can determine whether the product information of each item to be paid for is the same as the product information of the target item contained in the electronic voucher generated in step S203. If so, the server determines that the item to be paid for is the target item associated with the electronic voucher; otherwise, the server determines that the item to be paid for is not the target item associated with the electronic voucher.

[0065] When the server determines that a target product associated with an electronic voucher is included among the pending payment items, it can redetermine the total pending payment amount for each item based on the discount rules contained in the electronic voucher. Specifically, the payment request sent to the server by the non-receiving device may also include the pending payment amount for each pending payment item. The server can then redetermine the pending payment amount for the target product based on its pending payment amount and the discount rules contained in the electronic voucher, and redetermine the total pending payment amount based on the pending payment amounts for other pending payment items and the redetermined pending payment amount for the target product.

[0066] After determining the total amount to be paid, the server can adjust the total amount to be paid in the created payment order to the newly determined total amount to be paid. Based on the user's identifier, the server sends an authorization inquiry message to the user terminal. The user terminal displays the authorization inquiry message to the user. When the user returns an authorization confirmation message to the server through the user terminal, the server can use the queried payment account to pay for the payment order containing the newly determined total amount to be paid. That is, the amount corresponding to the newly determined total amount to be paid is transferred from the queried payment account to the retailer's collection account.

[0067] The aforementioned authorization confirmation message is used to authorize the server to allow the user's payment account to make payment for the payment order.

[0068] Generally, when a customer performs the aforementioned transaction, the cashier in a retail store needs to modify the outstanding payment amount of the customer's purchased item in the retailer's merchant system. This is extremely inconvenient, especially for chain key account (KA) retailers with inventory management, where cashiers typically lack the authority to modify the outstanding payment amount of the target item. This makes the transaction difficult to execute. However, through the aforementioned... Figure 3The method shown allows for the collection of payment for target goods initiated by non-receiving devices. The server can automatically change the amount to be paid for the target goods based on the generated electronic voucher used to execute the target transaction. Not only do retailers not need a dedicated account to log in to the target supplier's merchant system or a dedicated verification device when providing the above-mentioned target transaction to users, but cashiers also do not need to manually change the amount to be paid for the target goods, which greatly improves the convenience of executing the target transaction.

[0069] In the embodiments described in this specification, the server... Figure 3 After processing the payment order with the changed total amount due in step S210, the electronic voucher generated in step S203 can be verified, and the verification result and the merchant identifier of the retailer corresponding to the non-accepting device can be sent to the merchant system of the target supplier. In step S208, the non-accepting device can also include its own device identifier in the payment request and send it to the server, allowing the server to query the merchant identifier of the retailer corresponding to that device identifier.

[0070] After receiving the verification result and the retailer's merchant identifier, the target supplier can send the verification result to the retailer's merchant system based on the retailer's merchant identifier, allowing the retailer's merchant system to display the verification result. Upon receiving and displaying the verification result, the retailer's merchant system can send a replenishment request for the target product to the target supplier's merchant system. The target supplier's merchant system will then respond to the replenishment request by generating a replenishment order to resend the target product to the retailer. The target supplier's staff can then resend the target product to the retailer based on this replenishment order. The verification result may carry the electronic voucher and the business trigger information on which the electronic voucher was generated. After receiving the verification result, the target supplier can save it. If the same business trigger information is received again in step S202, the saved verification result can be used to determine that the electronic voucher generated based on the business trigger information has been verified, that is, the graphic code on the target item has been used. Thus, the supplier can return a judgment result to the server that the business trigger information did not match any business rules, so that the server will no longer execute step S203 and subsequent steps.

[0071] Furthermore, in Figure 3In step S210, after receiving a payment request containing the user's terminal identifier, product information of each item to be paid, the total amount to be paid, and the device identifier of the non-accepting device, the server can query the merchant identifier of the retailer corresponding to the device identifier of the non-accepting device again before re-determining the total amount to be paid. The server can then determine whether the queried merchant identifier exists in the preset set of qualified merchants for the target supplier. If so, the server can re-determine the total amount to be paid and use the user's payment account to make the payment. Otherwise, the server will refuse to re-determine the total amount to be paid and can use the user's payment account to pay the total amount to be paid carried in the original payment request sent by the non-accepting device, that is, to pay the payment order for which the total amount to be paid has not been modified.

[0072] This is because in this instruction manual Figure 2 The process of generating and distributing electronic vouchers shown is similar to... Figure 3 The process of using electronic vouchers shown are two relatively independent processes. Theoretically, a user can use electronic vouchers at a retailer... Figure 2 After obtaining the electronic voucher using the method shown, you can use it at another retailer. Figure 3 The method shown uses the electronic credential to perform the target business, therefore, in Figure 3 In this process, the server still needs to ensure that the retailer where the user uses the electronic credential to execute the target transaction is also a retailer that allows participation in the target supplier's provision of that target transaction. Of course, to minimize the possibility of this happening, in Figure 2 In step S203, it has already been described that when the server generates the electronic voucher, it can set a shorter validity period for the electronic voucher. Figure 3 In step S210 shown, before the server re-determines the total amount to be paid, in addition to determining whether the merchant identifier of the retailer exists in the preset set of qualified merchants for the target supplier, it also needs to determine whether the electronic voucher in the user's payment account is currently valid. If so, the total amount to be paid can be re-determined; otherwise, the re-determination of the total amount to be paid will be refused.

[0073] In the embodiments described in this specification, the server can pre-set a corresponding set of eligible merchants for the target supplier, and add the merchant identifiers of retailers that participate in the target business provided by the target supplier to this set of eligible merchants. Specifically, the retailer's merchant system can send the device identifier of the non-accepting device deployed at the retailer to the target supplier's merchant system. Retailer staff can directly input the device identifier of the non-accepting device into the retailer's merchant system, or they can use the retailer's merchant system to scan the graphic code carrying the device identifier on the non-accepting device to obtain the device identifier.

[0074] After receiving the device identifier from the retailer's merchant system, the target supplier's merchant system can send the device identifier to the server. The server then queries the corresponding retailer's merchant identifier based on the device identifier and returns it to the target supplier's merchant system. The target supplier's merchant system can then verify the retailer's eligibility to participate in the target business offered by the target supplier based on the retailer's merchant identifier, and return the verification result to the server. If the server receives a successful verification result, it determines that the target supplier has confirmed the retailer's eligibility to participate in the target business, and adds the retailer's merchant identifier to the pre-defined set of eligible merchants for that target supplier. If the server receives a failed verification result, it determines that the target supplier considers the retailer ineligible to participate in the target business, and therefore does not add the retailer's merchant identifier to the pre-defined set of eligible merchants for that target supplier.

[0075] In other words, in the embodiments of this specification, whether a retailer's merchant identifier can be added to the target supplier's qualified merchant set, or whether a retailer is qualified to participate in the aforementioned target business, is mainly determined by the target supplier. To further ensure business security, the server can also perform risk verification on the retailer. Specifically, after receiving the device identifier of the retailer's non-accepting device forwarded by the target supplier's merchant system, before returning the queried retailer's merchant identifier corresponding to that device identifier to the target supplier, the server can also perform risk verification on the retailer based on the device identifier of the non-accepting device and / or the queried retailer's merchant identifier. Only if the risk verification result is passed will the queried retailer's merchant identifier be returned to the target supplier. If the risk verification result is failed, there is no need to return the queried retailer's merchant identifier to the target supplier; the server can directly refuse to add the retailer's merchant identifier to the preset qualified merchant set for that target supplier.

[0076] Specifically, when the server performs risk verification on a retailer based on the device identifier of the unacceptable device, it can query the current status of the unacceptable device using the device identifier. If the current status of the unacceptable device is abnormal, the risk verification fails. When the server performs risk verification on a retailer based on the merchant identifier, it can query the risk level of the retailer using the merchant identifier. If the risk level of the retailer is higher than the set level, the risk verification fails. If the current status of the unacceptable device is normal and the risk level of the retailer is not higher than the set level, the risk verification passes.

[0077] The above describes a business execution system and method provided in the embodiments of this specification. Based on the same idea, this specification also provides corresponding devices, storage media, and electronic devices.

[0078] Figure 4 This is a schematic diagram of a first type of business execution device provided in an embodiment of this specification. The device is applied to a non-receiving device deployed at a retail store, and the device includes: The scanning module 400 is used to scan the graphic code on the target object to identify the business trigger information carried in the graphic code, send the business trigger information to the server, so that the server can determine the target supplier corresponding to the business trigger information, and send the business trigger information to the merchant system of the target supplier, so that the merchant system of the target supplier can determine the target business rule hit by the business trigger information according to the business trigger information and the preset business rules, and return the business execution information corresponding to the target business rule to the server. Display module 401 is used to receive and display the electronic credential generated by the server based on the business execution information for executing the target business; The acquisition module 402 is used to acquire the user identifier of the user terminal based on the contactless communication when conducting contactless communication with the user terminal, and return the user identifier to the server so that the server can allocate the electronic credential to the payment account corresponding to the user identifier.

[0079] Optionally, the scanning module 400 is specifically used to send the business triggering information and the device identifier of the non-accepting device to the server, so that the server queries the merchant identifier of the retailer corresponding to the device identifier, and when it is determined that the merchant identifier of the retailer exists in the preset set of qualified merchants for the target supplier, the server sends the business triggering information to the merchant system of the target supplier.

[0080] Optionally, the device further includes: The payment initiation module 403 is used to receive the product information and total amount to be paid for each product to be paid for, obtained and sent by the merchant system of the retailer; based on the user identifier of the user terminal, the product information and the total amount to be paid, it sends a payment request to the server, causing the server to respond to the payment request, query the payment account corresponding to the user identifier based on the user identifier, and when the electronic voucher is found in the queried payment account, it determines whether each product to be paid for contains the target product associated with the electronic voucher based on the product information. If so, it redetermines the total amount to be paid for each product to be paid for based on the electronic voucher, and uses the payment account to pay the redetermined total amount to be paid.

[0081] Optionally, the payment initiation module 403 is specifically used to send a payment request to the server based on the user identifier of the user terminal, the product information, the total amount to be paid, and the device identifier of the non-accepting device, so that the server determines that the merchant identifier of the retailer corresponding to the device identifier of the non-accepting device exists in the preset set of qualified merchants for the target supplier before redetermining the total amount to be paid for each product.

[0082] Figure 5 This is a schematic diagram of a second type of business execution device provided in the embodiments of this specification. The device is applied to a server and includes: The receiving module 500 is used to receive the graphic code on the target object scanned by the non-receiving device and to identify the service trigger information carried in the graphic code before sending the service trigger information; The determination module 501 is used to determine the target supplier corresponding to the service triggering information; The sending module 502 is used to send the business triggering information to the merchant system of the target supplier, so that the merchant system of the target supplier can determine the target business rule hit by the business triggering information according to the business triggering information and the preset business rules. The receiving module 500 is further configured to receive business execution information corresponding to the target business rule returned by the merchant system of the target supplier; The generation module 503 is used to generate an electronic certificate for executing the target business based on the business execution information. The sending module 502 is further configured to return the electronic certificate to the non-accepting device, so that the non-accepting device receives and displays the electronic certificate. The receiving module 500 is further configured to receive the user identifier of the user terminal obtained and sent by the non-receiving device based on contactless communication with the user terminal; The allocation module 504 is used to allocate the electronic voucher to the payment account corresponding to the user identifier.

[0083] Optionally, the sending module 502 is specifically configured to: receive the device identifier of the non-receiving device sent by the non-receiving device; query the merchant identifier of the retailer corresponding to the device identifier; and when it is determined that the merchant identifier of the retailer exists in the preset set of qualified merchants for the target supplier, send the business triggering information to the merchant system of the target supplier.

[0084] Optionally, the receiving module 500 is further configured to receive a payment request sent by the non-accepting device, wherein the payment request carries the user identifier of the user terminal, the product information of each product to be paid for, and the total amount to be paid; the payment request is sent by the retailer's merchant system after obtaining the product information of each product to be paid for and the total amount to be paid for to the non-accepting device; The device further includes: The payment module 505, in response to the payment request, queries the payment account corresponding to the user identifier based on the user identifier; when the electronic voucher is found in the payment account, it determines whether the target product associated with the electronic voucher is included in each product to be paid based on the product information; if so, it redetermines the total amount to be paid for each product to be paid based on the electronic voucher, and uses the payment account to pay the redetermined total amount to be paid.

[0085] Optionally, the payment module 505 is further configured to: after paying the re-determined total amount to be paid, verify the electronic voucher; send the verification result and the merchant identifier of the retailer corresponding to the non-accepting device to the merchant system of the target supplier, so that the merchant system of the target supplier sends the verification result to the merchant system of the retailer based on the merchant identifier of the retailer, so that the merchant system of the retailer receives and displays the verification result, and sends a replenishment request for the target product to the merchant system of the target supplier based on the verification result.

[0086] Optionally, the payment request may also include the device identifier of the non-receiving device; The payment module 505 is further configured to, before redetermining the total amount to be paid for each item to be paid, determine that the merchant identifier of the retailer corresponding to the device identifier of the non-accepting device exists in a preset set of qualified merchants for the target supplier.

[0087] Optionally, the device further includes: The configuration module 506 is configured to receive the device identifier of the non-accepting device sent by the merchant system of the target supplier, wherein the device identifier is sent by the merchant system of the retailer to the merchant system of the target supplier; query the merchant identifier of the retailer corresponding to the device identifier; return the queried merchant identifier of the retailer to the merchant system of the target supplier, so that the merchant system of the target supplier can verify the business qualifications of the retailer based on the merchant identifier of the retailer; receive the verification result returned by the merchant system of the target supplier, and when the received verification result is that the verification is passed, add the merchant identifier of the retailer to the preset set of qualified merchants for the target supplier.

[0088] Optionally, the configuration module 506 is further configured to, before returning the queried merchant identifier of the retailer to the merchant system of the target supplier, perform risk verification on the retailer based on the device identifier and / or the merchant identifier of the retailer, and determine that the verification result of the risk verification is passed.

[0089] This specification also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can be used to perform the business execution method provided above.

[0090] This specification also provides a computer program product, which includes a computer program that, when executed by a processor, implements the business execution method provided above.

[0091] based on Figure 2 and Figure 3 The business execution method shown in this specification is further provided in the embodiments. Figure 6 The diagram shows the structure of the electronic device. Figure 6 At the hardware level, the electronic device includes a processor, internal bus, network interface, memory, and non-volatile memory, and may also include other hardware required for business operations. The processor reads the corresponding computer program from the non-volatile memory into memory and then runs it to implement the aforementioned business execution method.

[0092] The above description is merely an embodiment of this specification and is not intended to limit this specification. Various modifications and variations can be made to this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of the claims of this specification.

Claims

1. A business execution system, the system comprising a user terminal, non-receiving devices deployed at retail stores, a merchant system of a target supplier, and a server; wherein: The non-receiving device is used to scan the graphic code on the target object to identify the service triggering information carried in the graphic code and send the service triggering information to the server. The server is used to determine the target supplier corresponding to the business triggering information and send the business triggering information to the merchant system of the target supplier. The merchant system of the target supplier is used to determine the target business rule hit by the business trigger information and the preset business rules based on the business trigger information and return the business execution information corresponding to the target business rule to the server. The server is also configured to generate an electronic credential for executing the target business based on the business execution information, and return the electronic credential to the non-accepting device; The non-receiving device is also used to receive and display the electronic certificate, and when conducting contactless communication with the user terminal, to obtain the user identifier of the user terminal based on the contactless communication and return the user identifier to the server. The server is also used to allocate the electronic voucher to the payment account corresponding to the user identifier.

2. The system as described in claim 1, wherein the non-receiving device is specifically used to send the service triggering information and the device identifier of the non-receiving device to the server; Specifically, the server is used to query the merchant identifier of the retailer corresponding to the device identifier, and when it is determined that the merchant identifier of the retailer exists in the preset set of qualified merchants for the target supplier, it sends the business triggering information to the merchant system of the target supplier.

3. The system of claim 1, further comprising: The retailer's merchant system; The non-receiving device is communicatively connected to the retailer's merchant system; The retailer's merchant system is used to obtain the product information and total amount to be paid for each product to be paid for, and send the product information and total amount to be paid for each product to be paid for to the non-receiving device. The non-receiving device is also used to send a payment request to the server based on the user identifier of the user terminal, the product information, and the total amount to be paid; The server is further configured to, in response to the payment request, query the payment account corresponding to the user identifier based on the user identifier, and when the electronic voucher is found in the queried payment account, determine whether each item to be paid contains a target item associated with the electronic voucher based on the product information. If so, the total amount to be paid for each item to be paid is recalculated based on the electronic voucher, and the payment account is used to pay the recalculated total amount to be paid.

4. The system as described in claim 3, wherein the server is further configured to, after making payment on the re-determined total amount to be paid, cancel the electronic voucher, and send the cancellation result and the merchant identifier of the retailer corresponding to the non-accepting device to the merchant system of the target supplier; The merchant system of the target supplier is also used to send the verification result to the merchant system of the retailer based on the merchant identifier of the retailer; The retailer's merchant system is also used to receive and display the verification results, and send a replenishment request for the target product to the target supplier's merchant system based on the verification results. The merchant system of the target supplier is also used to generate a replenishment order for reshipping the target product to the retailer in response to the replenishment request.

5. The system as described in claim 3, wherein the non-accepting device is specifically used to send a payment request to the server based on the user identifier of the user terminal, the product information, the total amount to be paid, and the device identifier of the non-accepting device; The server is also used to determine, before re-determining the total amount to be paid for each item, whether the merchant identifier of the retailer corresponding to the device identifier of the non-accepting device exists in a preset set of qualified merchants for the target supplier.

6. The system as described in claim 2 or 5, wherein the retailer's merchant system is further configured to send the device identifier of the non-accepting device to the target supplier's merchant system; The merchant system of the target supplier is also used to send the device identifier to the server; The server is also used to query the merchant identifier of the retailer corresponding to the device identifier based on the device identifier, and return the queried merchant identifier of the retailer to the merchant system of the target supplier. The merchant system of the target supplier is also used to verify the business qualifications of the retailer based on the merchant identifier of the retailer, and return the verification result to the server. The server is also used to add the retailer's merchant identifier to the preset set of qualified merchants for the target supplier when the received verification result is that the verification is passed.

7. A business execution method, the method being applied to non-receiving devices deployed at retail stores, the method comprising: The non-receiving device scans the graphic code on the target object to identify the business trigger information carried in the graphic code, sends the business trigger information to the server, enables the server to determine the target supplier corresponding to the business trigger information, and sends the business trigger information to the merchant system of the target supplier, so that the merchant system of the target supplier can determine the target business rule hit by the business trigger information according to the business trigger information and the preset business rules, and return the business execution information corresponding to the target business rule to the server; Receive and display the electronic credentials generated by the server based on the business execution information for executing the target business; When conducting contactless communication with a user terminal, the user identifier of the user terminal is obtained based on the contactless communication, and the user identifier is returned to the server so that the server can allocate the electronic credential to the payment account corresponding to the user identifier.

8. The method as described in claim 7, wherein sending the service triggering information to the server specifically includes: The service trigger information and the device identifier of the non-accepting device are sent to the server, so that the server queries the merchant identifier of the retailer corresponding to the device identifier. When it is determined that the merchant identifier of the retailer exists in the preset set of qualified merchants for the target supplier, the service trigger information is sent to the merchant system of the target supplier.

9. The method of claim 7, further comprising: Receive product information and total amount to be paid for each item from the retailer's merchant system; Based on the user identifier of the user terminal, the product information, and the total amount to be paid, a payment request is sent to the server. The server responds to the payment request by querying the payment account corresponding to the user identifier. If the electronic voucher is found in the queried payment account, it is determined whether each product to be paid for contains the target product associated with the electronic voucher. If so, the total amount to be paid for each product is recalculated based on the electronic voucher, and the payment account is used to pay the recalculated total amount to be paid.

10. The method as described in claim 9, wherein a payment request is sent to the server based on the user identifier of the user terminal, the product information, and the total amount to be paid, specifically including: Based on the user identifier of the user terminal, the product information, the total amount to be paid, and the device identifier of the non-accepting device, a payment request is sent to the server, so that the server determines that the merchant identifier of the retailer corresponding to the device identifier of the non-accepting device exists in the preset set of qualified merchants for the target supplier before re-determining the total amount to be paid for each product.

11. A business execution method, the method comprising: The server receives the graphic code on the target object scanned by the non-receiving device, identifies the service trigger information carried in the graphic code, and then sends the service trigger information. Identify the target supplier corresponding to the business triggering information; The business trigger information is sent to the merchant system of the target supplier, so that the merchant system of the target supplier can determine the target business rule that the business trigger information hits based on the business trigger information and the preset business rules. Receive business execution information corresponding to the target business rule returned by the merchant system of the target supplier; Based on the business execution information, generate an electronic certificate for executing the target business; The electronic credential is returned to the non-accepting device, so that the non-accepting device receives and displays the electronic credential. The non-receiving device receives the user identifier of the user terminal, which is acquired and sent by the user terminal based on contactless communication with the user terminal. The electronic credential is allocated to the payment account corresponding to the user identifier.

12. The method as described in claim 11, wherein sending the business triggering information to the merchant system of the target supplier specifically includes: Receive the device identifier of the non-receiving device sent by the non-receiving device; Search for the merchant's identifier that corresponds to the device identifier; When it is determined that the retailer's merchant identifier exists in the preset set of eligible merchants for the target supplier, the business triggering information is sent to the target supplier's merchant system.

13. The method of claim 11, further comprising: The system receives a payment request sent by the non-accepting device. The payment request carries the user identifier of the user terminal, the product information of each product to be paid, and the total amount to be paid. The payment request is sent by the retailer's merchant system after obtaining the product information of each product to be paid and the total amount to be paid. In response to the payment request, the payment account corresponding to the user identifier is queried based on the user identifier; When the electronic voucher is found in the payment account, the system determines whether the target product associated with the electronic voucher is included in each product to be paid for, based on the product information. If so, the total amount due for each item to be paid is recalculated based on the electronic voucher, and the payment account is used to make payment for the recalculated total amount due.

14. The method of claim 13, after making payment on the re-determined total amount to be paid, the method further includes: Cancel the aforementioned electronic voucher; The verification result and the merchant identifier of the retailer corresponding to the non-accepting device are sent to the merchant system of the target supplier. The merchant system of the target supplier sends the verification result to the merchant system of the retailer based on the merchant identifier of the retailer. The merchant system of the retailer receives and displays the verification result and sends a replenishment request for the target product to the merchant system of the target supplier based on the verification result.

15. The method of claim 13, wherein the payment request further carries the device identifier of the non-accepting device; Before redetermining the total outstanding amount for each item, the method further includes: The merchant identifier of the retailer corresponding to the device identifier of the non-accepting device is determined to exist in the preset set of qualified merchants for the target supplier.

16. The method as described in claim 12 or 15, wherein the preset set of qualified merchants for the target supplier specifically includes: Receive the device identifier of the non-receiving device sent by the merchant system of the target supplier, wherein the device identifier is sent by the merchant system of the retailer to the merchant system of the target supplier; Based on the device identifier, query the merchant identifier of the retailer corresponding to the device identifier; The merchant identifier of the retailer found in the query is returned to the merchant system of the target supplier, so that the merchant system of the target supplier can verify the business qualifications of the retailer based on the merchant identifier of the retailer; The system receives the verification result returned by the merchant system of the target supplier. When the received verification result is that the verification is passed, the merchant identifier of the retailer is added to the preset set of qualified merchants for the target supplier.

17. The method of claim 16, further comprising, before returning the queried merchant identifier of the retailer to the merchant system of the target supplier: Based on the device identifier and / or the retailer's merchant identifier, the retailer is subject to risk verification, and the verification result is determined to be passed.

18. A business execution apparatus, the apparatus being used on non-receiving devices deployed at retail stores, the apparatus comprising: The scanning module is used to scan the graphic code on the target object to identify the business trigger information carried in the graphic code, send the business trigger information to the server, enable the server to determine the target supplier corresponding to the business trigger information, and send the business trigger information to the merchant system of the target supplier, so that the merchant system of the target supplier can determine the target business rule hit by the business trigger information according to the business trigger information and the preset business rules, and return the business execution information corresponding to the target business rule to the server. The display module is used to receive and display the electronic credentials generated by the server based on the business execution information for executing the target business. The acquisition module is used to acquire the user identifier of the user terminal based on the contactless communication when conducting contactless communication with the user terminal, and return the user identifier to the server so that the server can allocate the electronic credential to the payment account corresponding to the user identifier.

19. A business execution apparatus, the apparatus comprising: The receiving module is used to receive the graphic code on the target object scanned by the non-receiving device, identify the service trigger information carried in the graphic code, and then send the service trigger information. The determination module is used to determine the target supplier corresponding to the business triggering information; The sending module is used to send the business triggering information to the merchant system of the target supplier, so that the merchant system of the target supplier can determine the target business rule hit by the business triggering information based on the business triggering information and the preset business rules. The receiving module is further configured to receive business execution information corresponding to the target business rule returned by the merchant system of the target supplier; The generation module is used to generate electronic credentials for executing the target business based on the business execution information; The sending module is further configured to return the electronic credential to the non-accepting device, so that the non-accepting device receives and displays the electronic credential; The receiving module is further configured to receive the user identifier of the user terminal obtained and sent by the non-receiving device based on contactless communication with the user terminal; The allocation module is used to allocate the electronic voucher to the payment account corresponding to the user identifier.

20. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any one of claims 7-17.

21. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the method described in any one of claims 7-17.

22. A computer program product comprising a computer program that, when executed by a processor, implements the method described in any one of claims 7-17.

Images