Bill Processing Method and Device

Abstract

The embodiments of this specification provide a bill processing method and apparatus. Among them, a bill processing method includes: obtaining a payment bill obtained after payment processing based on a user payment identifier; querying whether the storage unit of the cash register device stores bill association data containing the user payment identifier; the bill association data is constructed by the user payment identifier and bill application information pre-entered by the user; if so, generating a bill application request carrying the bill application information and the payment bill and sending it to a service platform for bill application; receiving the bill application result sent by the service platform.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a method and apparatus for processing invoices. Background Technology

[0002] With the development of internet technology, electronic invoices have been widely used. Like ordinary paper invoices, electronic invoices have a unified code issued by the tax authorities, and therefore have the same evidentiary effect. However, electronic invoices are more convenient than ordinary paper invoices in all aspects such as invoicing and reimbursement. In the process of using invoices for expense reimbursement, you first need to fill out electronic forms such as reimbursement application forms, and then submit the completed reimbursement application forms to the reviewers for review. After the review is approved, the invoices will be reimbursed. Summary of the Invention

[0003] This specification provides one or more embodiments of a ticket processing method. The ticket processing method, applied to a cash register device, includes: obtaining a payment bill obtained after payment processing based on a user payment identifier; querying whether the storage unit of the cash register device stores ticket-related data containing the user payment identifier; the ticket-related data is constructed from the user payment identifier and pre-entered ticket application information by the user; if so, generating a ticket application request carrying the ticket application information and the payment bill and sending it to a service platform to apply for a ticket; and receiving the ticket application result sent by the service platform.

[0004] This specification provides one or more embodiments of another ticket processing method applied to a service platform, comprising: receiving a ticket application request sent by a POS device; the ticket application request is generated after the POS device's storage unit stores ticket-related data including the user's payment identifier carried on the payment bill; encapsulating the ticket application request to obtain ticket issuance information, and sending the ticket issuance information to a ticket platform configured for the POS device; and sending a ticket application result to the POS device based on the ticket information returned by the ticket platform.

[0005] This specification provides one or more embodiments of a ticket processing device, operating on a POS device, including: a payment bill acquisition module configured to acquire a payment bill obtained after payment processing based on a user payment identifier; a data query module configured to query whether the storage unit of the POS device stores ticket-related data containing the user payment identifier; the ticket-related data is constructed from the user payment identifier and ticket application information pre-entered by the user; if so, a request generation module is run, the request generation module being configured to generate a ticket application request carrying the ticket application information and the payment bill and send it to a service platform to apply for a ticket; and a result receiving module configured to receive the ticket application result sent by the service platform.

[0006] This specification provides one or more embodiments of another ticket processing apparatus, operating on a service platform, comprising: a request receiving module configured to receive a ticket application request sent by a POS device; the ticket application request is generated after the POS device's storage unit stores ticket-related data including a user payment identifier carried on a payment bill; an encapsulation processing module configured to encapsulate the ticket application request to obtain ticket issuance information, and send the ticket issuance information to a ticket platform configured for the POS device; and a result sending module configured to send a ticket application result to the POS device based on the ticket information returned by the ticket platform.

[0007] This specification provides one or more embodiments of a ticket processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: obtain a payment bill obtained after payment processing based on a user payment identifier; query whether the storage unit of the cash register device stores ticket-related data containing the user payment identifier; the ticket-related data is constructed from the user payment identifier and pre-entered ticket application information by the user; if so, generate a ticket application request carrying the ticket application information and the payment bill and send it to a service platform to apply for a ticket; and receive the ticket application result sent by the service platform.

[0008] This specification provides one or more embodiments of another ticket processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: receive a ticket application request sent by a cash register device; the ticket application request is generated after the cash register device's storage unit stores ticket-related data including a user payment identifier carried on a payment bill; encapsulate and process the ticket application request to obtain ticket issuance information, and send the ticket issuance information to a ticket platform configured for the cash register device; and send a ticket application result to the cash register device based on the ticket information returned by the ticket platform.

[0009] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions that, when executed by a processor, implement the following process: Obtaining a payment bill obtained after payment processing based on a user payment identifier; querying whether the storage unit of the POS device stores ticket association data containing the user payment identifier; the ticket association data is constructed from the user payment identifier and pre-entered ticket application information by the user; if so, generating a ticket application request carrying the ticket application information and the payment bill and sending it to a service platform to apply for a ticket; receiving the ticket application result sent by the service platform.

[0010] This specification provides one or more embodiments of another storage medium for storing computer-executable instructions that, when executed by a processor, implement the following process: receiving a ticket application request from a cash register device; the ticket application request is generated after the cash register device's storage unit stores ticket-related data including the user's payment identifier carried on the payment bill; encapsulating the ticket application request to obtain ticket issuance information, and sending the ticket issuance information to a ticket platform configured for the cash register device; and sending the ticket application result to the cash register device based on the ticket information returned by the ticket platform. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 A flowchart illustrating a bill processing method provided in one or more embodiments of this specification;

[0013] Figure 2This specification provides a schematic diagram of a bill processing method according to one or more embodiments.

[0014] Figure 3 A flowchart illustrating a bill processing method for a first-time invoicing scenario, provided for one or more embodiments of this specification;

[0015] Figure 4 A flowchart illustrating a bill processing method applied to a bill issuance scenario, provided for one or more embodiments of this specification;

[0016] Figure 5 A flowchart illustrating another bill processing method provided in one or more embodiments of this specification;

[0017] Figure 6 A schematic diagram of a ticket processing device provided for one or more embodiments of this specification;

[0018] Figure 7 A schematic diagram of another ticket processing device provided in one or more embodiments of this specification;

[0019] Figure 8 This specification provides a schematic diagram of the structure of a ticket processing device according to one or more embodiments.

[0020] Figure 9 This is a schematic diagram of the structure of a ticket processing device provided for one or more embodiments of this specification. Detailed Implementation

[0021] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0022] This specification provides an example of a bill processing method:

[0023] The ticket processing method provided in this embodiment stores the header information of the user who applies for the ticket in a storage unit configured in the POS device. This allows the user to apply for tickets based on the stored header information during subsequent applications through the POS device, eliminating the need for the user to manually enter the header information each time. Specifically, based on the payment bill obtained after payment processing using the user's payment identifier, the method reads the ticket association data of the user's payment identifier from the storage unit of the POS device; generates a ticket application request containing the ticket application information from the ticket association data and the payment bill; and sends it to the service platform; then receives the ticket application result from the service platform. Thus, the method automatically applies for tickets based on the stored header information, eliminating the need for the user to manually enter the header information after each payment.

[0024] Reference Figure 1 The ticket processing method provided in this embodiment is applied to a cash register device and specifically includes steps S102 to S108.

[0025] Step S102: Obtain the payment bill obtained after processing the payment based on the user's payment identifier.

[0026] In this embodiment, the user payment identifier includes an identifier that can characterize the user's identity during the payment process; optionally, it includes at least one of the following: a user identity identifier, or a channel identifier of the payment channel used for payment processing. For example, if a user makes a payment based on a bank card, the bank card identifier is the user payment identifier; or, information associated with the bank card that characterizes the user's identity can also be used as the user payment identifier. Furthermore, the user payment identifier can also be replaced by a user identifier; wherein the user identifier includes the user's name; for example, the user name bound to the payment channel read from the user's payment information; or, the user identifier can also be the user's communication channel identifier; the communication channel identifier can be read based on the user's payment information or obtained from the user terminal used for payment processing.

[0027] It should be noted that user payment identifiers or user identifiers are, to some extent, considered user privacy information. In order to ensure user privacy and security, user authorization is required before obtaining user payment identifiers or user identifiers.

[0028] In specific implementation, after processing the payment for the order to be paid, a payment bill is generated; optionally, the payment bill is generated after processing the payment based on the order to be paid and the user payment characteristics collected by the POS device; in one optional implementation provided in this embodiment, the following operations are performed during the process of obtaining the payment bill obtained after processing the payment based on the user payment identifier:

[0029] The user's payment characteristics are collected based on the data acquisition components configured in the POS device;

[0030] Generate a payment request carrying the user's payment characteristics and the order to be paid, and send it to the payment platform for payment processing;

[0031] Receive the payment bill sent by the payment platform after successful payment processing.

[0032] Optionally, the user payment features include at least one of the following: the user's payment identifier, a biometric image; the user payment identifier includes a payment channel identifier or a user identity identifier obtained after identifying the user payment features.

[0033] Specifically, users pay by displaying a payment icon or by using biometrics. The POS device collects the payment icon or biometric image displayed by the user's terminal and sends the collected payment icon or biometric image and the generated order to be paid to the payment platform for payment processing.

[0034] During the payment processing, the payment platform can obtain the user's payment account by recognizing the payment identifier or by recognizing the associated user's payment account through biometric image recognition. Based on the obtained user payment account, the platform can transfer resources for the pending payment order and generate a payment bill after the resource transfer.

[0035] Biometric images include, for example, facial feature images of users collected during the process of making facial recognition payments.

[0036] In addition, in this embodiment, the process of obtaining the payment bill after payment processing based on the user payment identifier can also be carried out in the following manner: collecting user payment features based on the collection component configured in the cash register; identifying the user payment features to obtain the user payment identifier associated with the user payment features; generating a payment request carrying the user payment identifier and the order to be paid and sending it to the payment platform for payment processing; and receiving the payment bill sent by the payment platform after successful payment processing.

[0037] In the specific execution process, after receiving the payment bill sent by the payment platform after successful payment processing, the POS device can render and display a payment success page to make the payment result more intuitive for the user and the cashier. In this embodiment, in order to automate the invoice application after payment processing, the invoice issuance process is performed asynchronously after obtaining the payment bill. To further improve the user and cashier's perception of the invoice issuance process, in an optional implementation of this embodiment, after obtaining the payment bill, a payment success page is rendered and displayed based on the acquisition of the payment bill; optionally, the payment success page displays an invoice application reminder layer.

[0038] For example, after the POS device receives the payment bill, it renders a payment success page and displays a pop-up window on the payment success page saying "Initiating invoice issuance asynchronously, the invoice will be sent to the user's email address later".

[0039] Step S104: Query whether the storage unit of the cash register device stores ticket-related data containing the user's payment identifier.

[0040] The storage unit includes a storage area configured in the POS device for data storage; for example, a cache module of the POS device. The ticket association data includes relevant data for issuing tickets to users, constructed from user payment identifiers and ticket application information. For example, the association between user payment identifiers and ticket application information.

[0041] Optionally, the storage unit stores a preset number of invoice-related data; the invoice-related data stored in the storage unit is constructed based on the user's payment identifier and the invoice application information pre-entered by the user.

[0042] In practical applications, due to the limited storage space of the storage unit, in order to avoid storing unused ticket-related data in the storage unit, resulting in a large storage volume in the storage unit and affecting the operation of the cash register, the preset number of ticket-related data stored in the storage unit may be determined based on the usage frequency of the ticket application information contained in the ticket-related data.

[0043] To ensure the operational efficiency of the POS equipment, in one optional implementation of this embodiment, the associated data of the receipts (the relationship between user payment identifiers and receipt application information) stored in the storage space is managed in the following way:

[0044] Calculate the amount of invoice-related data stored in the storage unit;

[0045] If the amount of data exceeds a preset number, the bill association data stored in the storage unit is sorted in descending order according to the frequency of use of bill application information in the stored bill association data to obtain a storage queue; bill association data in the queue that is after the position corresponding to the preset number is deleted.

[0046] If the amount of data is less than or equal to the preset amount, no processing is required.

[0047] Specifically, a low-frequency usage elimination system is adopted for the ticket-related data stored in the storage unit; optionally, the above management process can be executed according to a preset cycle.

[0048] For example, to ensure the operating efficiency of the POS equipment, the number of associations between user identifiers and ticket header information stored in the storage unit should not exceed M. The storage unit is deleted according to a preset period. When the preset period is detected, the number of associations stored in the storage unit is calculated to be m. If m ≤ M, no processing is required; if m > M, the associations are sorted in descending order according to the frequency of use of ticket header information in the associations to obtain a storage queue, and the associations after the Mth position in the storage queue are deleted.

[0049] Alternatively, the document association data stored in the storage unit can be managed each time document association data is stored in the storage unit. Specifically, since new document association data needs to be added to the storage queue, the number of document association data in the storage queue must be less than a preset threshold. During the management of the storage unit, the following operations are performed:

[0050] Calculate the amount of document-related data stored in the unit;

[0051] If the number of data is greater than or equal to a preset number, the bill association data stored in the storage unit is sorted in descending order according to the frequency of use of bill application information in the stored bill association data to obtain a storage queue; the bill association data in the sorted queue that is after the position corresponding to the preset number is deleted.

[0052] If the amount of data is less than or equal to the preset amount, no processing is required.

[0053] In addition, the number of storage units can be unlimited, and the decision to delete the invoice-related data from the storage unit can be based solely on the frequency of use of the invoice-related data stored in the storage unit; specifically, the frequency of data use of the invoice-related data stored in the storage unit can be detected; and invoice-related data in the storage unit whose data use frequency is less than the frequency threshold (x times / month) can be deleted.

[0054] In the specific execution process, based on the payment bill obtained after payment processing based on the user payment identifier, the storage unit of the cash register is queried to see if it stores the ticket application information containing the user payment identifier; if so, the following step S106 is executed to generate a ticket application request carrying the ticket application information and the payment bill and send it to the service platform to apply for a ticket.

[0055] In this embodiment, if the execution result after querying whether the storage unit of the POS device stores ticket-related data containing the user's payment identifier is negative, since the service platform has a large storage space, all ticket-related data stored in the storage unit of the POS device will be stored on the service platform. Therefore, as long as the user has entered the data, it will be stored in the storage space of the service platform. Thus, after querying that the storage unit of the POS device does not contain ticket-related data containing the user's payment identifier, a further query is performed on the service platform to retrieve ticket-related data containing the user's payment identifier. This improves the efficiency of ticket application and further ensures that the user only needs to enter the data to apply for multiple tickets.

[0056] This embodiment provides two optional implementation methods. The following describes in detail the processing methods when the storage unit of the cash register does not find the ticket-related data containing the user's payment identifier.

[0057] (1) In one optional implementation of this embodiment, if no ticket-related data containing the user's payment identifier is found in the storage unit of the cash register, the following operation is performed:

[0058] Send an information query request carrying the user's payment identifier to the service platform to perform a query on the service platform for invoice-related data containing the user's payment identifier;

[0059] If the service platform receives the bill application information contained in the queried bill association data, then the following step S106 is executed;

[0060] If the query result sent by the service platform is empty, a reminder to enter the invoice application information is displayed; the invoice application information entered and submitted by the user is obtained, an invoice application request carrying the payment bill and the invoice application information submitted by the user is generated and sent to the service platform to apply for the invoice.

[0061] Specifically, the system checks whether the storage unit of the POS device stores ticket-related data containing the user's payment identifier. If not, it queries the service platform for ticket-related data containing the user's payment identifier. If the service platform finds ticket-related information containing the user's payment identifier, it generates a ticket application request carrying the ticket application information and payment bill from the ticket-related information and sends it to the service platform to apply for a ticket. The system then receives the ticket application result from the service platform.

[0062] If the query result from the service platform is empty, the user needs to enter the invoice application information; that is, if the query result from the service platform is empty, the system interacts with the user to obtain the invoice application information, generates an invoice application request based on the payment bill and the obtained invoice application information, and sends it to the service platform to apply for the invoice; and receives the invoice application result sent by the service platform.

[0063] The POS device sends an information query request carrying the user's payment identifier to the service platform. The service platform checks whether there is any ticket-related data containing the user's payment identifier. If so, it sends the ticket application information contained in the queried ticket-related data to the POS device. If not, it sends an empty query result to the POS device.

[0064] After receiving the ticket application information from the service platform, in order to update the storage unit, in an optional implementation of this embodiment, the POS device updates the ticket-related data stored in the storage unit in the following manner:

[0065] Based on the user's payment identifier and the invoice application information sent by the service platform, invoice association data is constructed;

[0066] The constructed invoice association data is written to the storage unit.

[0067] Specifically, after receiving the ticket application information sent by the service platform, the ticket association data containing the user payment identifier and the ticket application information sent by the service platform is stored in the storage unit of the POS device, so that a ticket application can be made based on the ticket application information after the user to whom the user payment identifier belongs makes a payment.

[0068] When the POS device receives an empty query result from the service platform, in order to issue a receipt for the user's payment, it interacts with the user to obtain the receipt application information entered by the user. To enable subsequent payments by the same user to be processed without requiring further receipt application information from the user, in an optional implementation of this embodiment, after obtaining the receipt application information entered and submitted by the user, the following operations are also performed:

[0069] Based on the user's payment identifier and the invoice application information submitted by the user, invoice association data is constructed;

[0070] The constructed invoice association data is written into the storage unit and sent to the service platform for storage.

[0071] Specifically, the POS device displays a reminder to enter receipt application information. Users can enter receipt application information using the POS device, or they can obtain the user's receipt application information by displaying an information identifier associated with the receipt application information. The POS device can collect and identify the information identifier to obtain the user's receipt application information. The information identifier can be a QR code, barcode, etc.

[0072] Furthermore, after obtaining the user's input ticket application information, to ensure that the user can apply for a ticket without having to input the application information again during subsequent payments via the POS device, the ticket association data, including the user's payment identifier and the submitted ticket application information, is stored in the POS device's storage unit. Since the storage unit will evict key ticket data to ensure the POS device's operational efficiency, to further guarantee the effective storage of the user's ticket application information, after constructing the ticket association data, it is sent to the service platform for storage. In other words, after obtaining the user's input ticket application information, the ticket association data based on the user's payment identifier and submitted ticket application information is stored in the storage unit and on the service platform. This ensures that even if the ticket association data is deleted from the storage unit, it can still be retrieved on the service platform, improving the effectiveness of storage.

[0073] (2) The above method provides a process of querying the service platform for the invoice association data containing the user payment identifier after failing to find the invoice association data containing the user payment identifier in the storage unit; in another optional implementation of this embodiment, after failing to find the invoice association data containing the user payment identifier in the storage unit, a request for issuing an invoice carrying the payment bill is generated and sent to the service platform to issue the invoice; and the invoice issuance result sent by the service platform after issuing the invoice is received.

[0074] The service platform issues the invoice based on the invoice issuance request. To ensure the authenticity of the invoice, it needs to be issued by a platform with invoice issuance qualifications. Therefore, in one optional implementation of this embodiment, the invoice issuance by the service platform includes the following operations:

[0075] Check whether invoice-related data containing the user's payment identifier carried on the payment bill is stored;

[0076] If so, read the invoice application information from the queried invoice association data and generate invoice issuance information carrying the queried invoice application information and the payment bill; send the invoice issuance information to the invoice platform configured on the cash register, and send the invoice issuance result to the cash register according to the invoice information sent by the invoice platform;

[0077] If not, a receipt issuance result with empty receipt application information is sent to the POS device so that the POS device can collect receipt application information and send a receipt application request.

[0078] Specifically, the POS device checks whether the storage unit stores invoice-related data containing the user's payment identifier. If not, it sends a invoice issuance request carrying the payment bill to the service platform to issue the invoice. The service platform issues the invoice based on the invoice issuance request and sends the invoice issuance result. The POS device receives the invoice issuance result sent by the service platform.

[0079] In practice, the process of issuing invoices requires the use of the user's invoice application information, the payment bill information, and / or the merchant's relevant information. Therefore, the service platform needs to encapsulate the information required for the invoice issuance process and send the encapsulated invoice issuance information to the invoice platform configured for the POS device for invoice issuance.

[0080] In this embodiment, after receiving a ticket issuance request, the service platform encapsulates the request to obtain ticket issuance information and sends the information to the ticket platform configured for the POS device. The process by which the service platform encapsulates the ticket application request to obtain ticket issuance information can be implemented as follows:

[0081] The configuration information of the cash register is read based on the device identifier carried in the ticket issuance request.

[0082] Extract the ticket auxiliary information contained in the configuration information;

[0083] The auxiliary information of the invoice, the queried invoice application information, and the payment bill carried in the invoice issuance request are identified as the invoice issuance information.

[0084] Optionally, the device identifier is the identifier of the POS device; the configuration information is entered and submitted by the merchant to which the POS device belongs.

[0085] Specifically, the service platform queries whether it stores invoice-related data containing the user's payment identifier carried on the payment bill based on the invoice issuance request; if so, it reads the invoice application information contained in the queried invoice-related data, and reads the invoice auxiliary information of the POS device based on the device identifier carried on the invoice issuance request; and sends the invoice application information, invoice auxiliary information, and payment bill as invoice issuance information to the invoice platform configured for the POS device.

[0086] If not, send a receipt application result with empty receipt application information to the POS device to allow for the entry of receipt application information.

[0087] Furthermore, after obtaining the invoice issuance information, the service platform sends the invoice issuance information to the invoice platform configured for the POS device; in this embodiment, the merchant can configure the invoice platform to issue invoices for the merchant's payment bills.

[0088] Based on this, in this embodiment, during the process of sending the invoice issuance information to the invoice platform configured for the POS device, the platform identifier contained in the configuration information of the POS device is first read; then the invoice issuance information is passed to the interface corresponding to the platform identifier.

[0089] Specifically, during the process of the service platform sending invoice issuance information to the invoice platform, the invoice issuance information is passed to the interface corresponding to the platform identifier contained in the configuration information of the POS device.

[0090] It should be noted that merchants can input configuration information through the POS device, which then sends the configuration information to the service platform for storage. In one optional implementation of this embodiment, the POS device performs the following operations:

[0091] Obtain the configuration information for the POS device entered by the merchant;

[0092] The configuration information and the device identifier of the POS device are sent to the service platform for configuration information storage.

[0093] Optionally, the configuration information includes the platform identifier of the ticketing platform configured for the POS device; specifically, the service platform stores the configuration information of the POS device.

[0094] Step S106: Generate a bill application request carrying the bill application information and the payment bill and send it to the service platform to apply for a bill.

[0095] The invoice application request includes a request to the service platform to apply for an invoice, carrying invoice application information and a payment bill. An invoice issuance request is also provided, the difference being that the invoice issuance request does not carry invoice application information. Optionally, the invoice application request is generated after the storage unit of the POS device stores invoice-related data containing the user payment identifier carried on the payment bill.

[0096] In specific implementation, after the above query is performed to see if the storage unit of the POS device stores the ticket-related data containing the user's payment identifier, if the storage unit stores the ticket-related data containing the user's payment identifier, a ticket application request carrying the payment bill and the ticket application information contained in the ticket-related data is generated and sent to the service platform to apply for the ticket.

[0097] Alternatively, after executing the above query to see if the storage unit of the POS device stores ticket-related data containing the user's payment identifier, if the storage unit does not store ticket-related data containing the user's payment identifier, then query the service platform to see if it stores ticket-related data containing the user's payment identifier; if the service platform sends the ticket application information contained in the queried ticket-related data, then a ticket application request carrying the payment bill and the ticket application information is generated and sent to the service platform.

[0098] The service platform receives a ticket application request from the POS device, encapsulates the ticket application request to obtain ticket issuance information, and sends the ticket issuance information to the ticket platform configured for the POS device.

[0099] In one optional implementation method provided in this embodiment, the service platform performs information encapsulation processing in the following manner:

[0100] The configuration information of the POS device is read based on the device identifier carried in the ticket application request.

[0101] Extract the ticket auxiliary information contained in the configuration information;

[0102] The auxiliary information of the invoice and the payment bill and invoice application information carried in the invoice application request are identified as the invoice issuance information.

[0103] Specifically, the service platform reads the receipt auxiliary information of the POS device based on the receipt application request sent by the POS device, and determines the receipt auxiliary information and the payment bill and receipt application information carried in the receipt application request as the receipt issuance information.

[0104] Furthermore, in one optional implementation of this embodiment, the service platform performs the following operations when sending invoice issuance information to the invoice platform configured for the POS device:

[0105] Read the platform identifier contained in the configuration information of the POS device;

[0106] The invoice issuance information is passed to the interface corresponding to the platform identifier.

[0107] Specifically, after determining the invoice issuance information, the service platform transmits the invoice issuance information to the interface corresponding to the platform identifier contained in the configuration information of the POS device.

[0108] Step S108: Receive the ticket application result sent by the service platform.

[0109] The bill application result includes a successful bill application result; in addition, it may also include a failed bill application result; in order to improve the POS terminal's perception of bill information, the bill application result may optionally include bill information.

[0110] In the above steps, the service platform sends invoice issuance information to the invoice platform; the invoice platform issues invoices based on the invoice issuance information and obtains the invoice information corresponding to the payment bill; in order to improve the service platform's management of invoice information, the invoice platform sends the invoice information to the service platform after generating the invoice information; after receiving the invoice information, the service platform sends the invoice issuance result to the cash register.

[0111] Among them, bill information refers to the vouchers obtained after the issuance of a bill; such as a bill or a bill voucher.

[0112] For example, after determining the invoice issuance information, the service platform sends it to the invoice platform. The invoice platform generates an invoice based on the invoice application information, payment bill, and invoice auxiliary information contained in the invoice issuance information, and sends the invoice to the service platform. After receiving the invoice, the service platform sends the successful invoice application result to the cash register.

[0113] The POS device receives the receipt application result from the service platform. To improve the user's awareness of the receipt application result, the POS device can display the receipt application result after receiving it.

[0114] It should be noted that the bill application information includes the user's communication identifier, such as an email address. After the bill platform issues the bill, it sends the bill to the user based on the communication channel corresponding to the user's communication identifier included in the bill application information.

[0115] In summary, the bill processing method provided in this embodiment involves the following steps: After the POS device receives the payment bill obtained after payment processing based on the user's payment identifier, it checks the storage unit to see if there is any bill application information associated with the user's payment identifier. If so, it generates a bill application request carrying the bill application information and the payment bill and sends it to the service platform to apply for a bill. Based on the bill application request, the service platform sends the POS device's bill auxiliary information, bill application information, and payment bill to the bill platform corresponding to the POS device. The bill platform issues a bill based on the bill auxiliary information, bill application information, and payment bill, and sends the obtained bill to the service platform. The service platform adds the bill to the bill list and sends the bill application result to the POS device.

[0116] If the POS device does not find the receipt application information associated with the user's payment identifier in the storage unit, it sends an information query request to the service platform. The service platform checks whether the receipt application information associated with the user's payment identifier is stored. If so, it sends the queried receipt application information to the POS device. The POS device generates receipt application information based on the payment bill and the receipt application information sent to the service platform and sends it to the service platform. Based on the receipt application request, the service platform sends the receipt application information, the payment bill, and the POS device's receipt auxiliary information to the corresponding receipt platform. The receipt platform issues a receipt based on the receipt auxiliary information, the receipt application information, and the payment bill, and sends the obtained receipt to the service platform. The service platform adds the receipt to the receipt list and sends the receipt application result to the POS device.

[0117] If the service platform does not find the invoice application information associated with the user's payment identifier, it sends an empty query result to the POS device. The POS device interacts with the user based on the empty query result to obtain the invoice application information entered by the user, and generates invoice application information based on the payment bill and the user's entered information, then sends it to the service platform. Based on the invoice application request, the service platform sends the invoice application information, the payment bill, and the POS device's invoice auxiliary information to the corresponding invoice platform. The invoice platform issues the invoice based on the invoice auxiliary information, the invoice application information, and the payment bill, and sends the obtained invoice to the service platform. The service platform adds the invoice to its invoice list and sends the invoice application result to the POS device.

[0118] Therefore, users only need to enter bill application information during the initial payment and bill issuance process. The bill application information entered by the user is associated with and stored with the user's payment identifier. The user can then use the bill application information in subsequent payment and bill issuance processes. This eliminates the need for users to enter bill application information multiple times, which would otherwise lead to low efficiency in bill issuance. This improves the efficiency of user payment and bill issuance, and in turn, enhances the user's perception of the payment and bill issuance process.

[0119] The following example uses a bill processing method provided in this embodiment in the scenario of initial bill issuance as an illustration. Figure 2 and Figure 3 For further explanation of the invoice processing method provided in this embodiment, please refer to [link / reference]. Figure 3 The invoice processing method applied to the first invoice issuance scenario includes the following steps.

[0120] like Figure 2 As shown, merchants enter configuration information, including the platform identifier for issuing receipts, through the POS device interface. The POS device uploads the configuration information to the service platform (the platform corresponding to the POS device), and the service platform stores the configuration information of the POS device.

[0121] After a user makes a purchase at a merchant, the POS device collects the user's facial image or payment identifier code. The POS device then initiates payment to the payment platform based on the collected facial image or payment identifier code. After processing the payment, the payment platform obtains a payment bill and sends it to the POS device. Upon receiving the payment bill processed based on the user's payment identifier, the POS device first checks its storage unit for any invoice application information associated with the user's payment identifier. If invoice application information is found, it sends an invoice application request to the service platform based on the invoice application information and the payment bill.

[0122] If the POS device does not find any receipt application information associated with the user's payment identifier stored in the storage unit, the POS device will query the service platform for the receipt application information associated with the user's payment identifier. If the query is empty, the user is determined to be a first-time payment user. The user enters the receipt application information through the POS device interface, and the POS device sends the association relationship between the user's payment identifier and the receipt application information entered by the user to the service platform for storage.

[0123] Based on the invoice application information and payment bill, an invoice application request is generated and sent to the service platform. The service platform reads the invoice auxiliary information from the configuration information of the POS device based on the invoice application request, and sends the invoice auxiliary information, invoice application information and payment bill to the invoice platform corresponding to the POS device to issue the invoice.

[0124] In addition, the data connection between the POS device and the billing platform can be configured. After obtaining the bill application information, the POS device generates a bill issuance request based on the bill application information, payment bill and the bill auxiliary information of the POS device and sends it to the billing platform corresponding to the POS device to issue the bill.

[0125] Step S302: Obtain the user's payment request, and call the payment platform to process the payment based on the payment request.

[0126] Step S304: Obtain the payment bill obtained after payment processing based on the user identifier.

[0127] Step S306: Render and display the payment success page based on the payment bill.

[0128] Step S308: If it is determined that the user is a first-time payment user, then obtain the bill header information entered by the user.

[0129] If neither the POS device nor the service platform has any ticket-related data containing the user's payment identifier, the user is identified as a first-time payment user.

[0130] Step S310: Construct bill association data based on user identifier and bill header information.

[0131] Step S312: Send the invoice association data to the service platform for storage.

[0132] Step S314: Generate a bill application request based on the bill header information and payment bill.

[0133] Step S316: Send a ticket application request to the service platform.

[0134] The service platform reads the ticket auxiliary information of the POS device based on the ticket application request; generates a ticket issuance request based on the ticket application information, payment bill, and ticket auxiliary information; sends the ticket issuance request to the ticket platform corresponding to the POS device; receives the ticket returned by the ticket platform and adds the ticket to the ticket list; and sends the successful ticket application result to the POS device.

[0135] Step S328: Receive the successful invoice application result, render the invoice application result display page, and display it.

[0136] The following description uses the application of a bill processing method provided in this embodiment in a bill issuance scenario as an example to further illustrate the bill processing method provided in this embodiment. (See also...) Figure 4 The bill processing method applied to bill issuance scenarios includes the following steps.

[0137] Step S402: Obtain the payment bill obtained by the payment platform after processing the payment based on the user's payment channel identifier.

[0138] Step S404: Render and display the payment success page based on the payment bill.

[0139] Step S406: Query the ticket application information associated with the user's payment channel identifier in the storage unit of the cash register device.

[0140] In step S408, if the query result is empty, an information query request is sent to the service platform based on the user's payment channel identifier.

[0141] The service platform checks whether there is any invoice application information associated with the user's payment channel identifier; it then sends the found invoice application information to the POS device.

[0142] Step S414: Generate a bill application request based on the bill application information sent by the payment bill and service platform.

[0143] Step S416: Send a ticket application request to the service platform.

[0144] The service platform reads the ticket auxiliary information of the POS device based on the ticket application request; generates a ticket issuance request based on the ticket application information, payment bill, and ticket auxiliary information; sends the ticket issuance request to the ticket platform corresponding to the POS device; receives the ticket returned by the ticket platform and adds the ticket to the ticket list; and sends the successful ticket application result to the POS device.

[0145] Step S428: Receive the successful invoice application result, render the invoice application result display page, and display it.

[0146] This specification provides an example of a bill processing method:

[0147] The bill processing method provided in this embodiment is applied to a service platform, while the bill processing method provided in the above embodiments is applied to a cash register. The bill processing method for the service platform provided in this embodiment and the bill processing method for the cash register provided in the above embodiments cooperate with each other during execution. Therefore, please refer to the relevant content of the above embodiments when reading this embodiment, and you can also refer to the relevant content of this embodiment when reading the above embodiments.

[0148] Reference Figure 5 The invoice processing method provided in this embodiment is applied to a service platform and specifically includes steps S502 to S508.

[0149] Step S502: Receive a ticket application request sent by the cash register device.

[0150] Optionally, the ticket application request is generated after the storage unit of the cash register stores ticket-related data containing the user payment identifier carried on the payment bill.

[0151] In this embodiment, the user payment identifier includes an identifier that can characterize the user's identity during the payment process; optionally, it includes at least one of the following: a user identity identifier, or a channel identifier of the payment channel used for payment processing. For example, if a user makes a payment based on a bank card, the bank card identifier is the user payment identifier; or, information associated with the bank card that characterizes the user's identity can also be used as the user payment identifier. Furthermore, the user payment identifier can also be replaced by a user identifier; wherein the user identifier includes the user's name; for example, the user name bound to the payment channel read from the user's payment information; or, the user identifier can also be the user's communication channel identifier; the communication channel identifier can be read based on the user's payment information or obtained from the user terminal used for payment processing.

[0152] It should be noted that user payment identifiers or user identifiers are, to some extent, considered user privacy information. In order to ensure user privacy and security, user authorization is required before obtaining user payment identifiers or user identifiers.

[0153] In specific implementation, the POS device obtains a payment bill after processing the payment based on the user's payment identifier, and generates a payment bill after processing the payment for the order to be paid; optionally, the payment bill is generated after processing the payment based on the order to be paid and the user's payment characteristics collected by the POS device; in this embodiment, the following operations are performed during the process of obtaining the payment bill obtained after processing the payment based on the user's payment identifier:

[0154] The user's payment characteristics are collected based on the data acquisition components configured in the POS device;

[0155] Generate a payment request carrying the user's payment characteristics and the order to be paid, and send it to the payment platform for payment processing;

[0156] Receive the payment bill sent by the payment platform after successful payment processing.

[0157] Optionally, the user payment features include at least one of the following: the user's payment identifier, a biometric image; the user payment identifier includes a payment channel identifier or a user identity identifier obtained after identifying the user payment features.

[0158] Specifically, users pay by displaying a payment icon or by using biometrics. The POS device collects the payment icon or biometric image displayed by the user's terminal and sends the collected payment icon or biometric image and the generated order to be paid to the payment platform for payment processing.

[0159] During the payment processing, the payment platform can obtain the user's payment account by recognizing the payment identifier or by recognizing the associated user's payment account through biometric image recognition. Based on the obtained user payment account, the platform can transfer resources for the pending payment order and generate a payment bill after the resource transfer.

[0160] Biometric images include, for example, facial feature images of users collected during the process of making facial recognition payments.

[0161] In addition, in this embodiment, the process of obtaining the payment bill after payment processing based on the user payment identifier can also be carried out in the following manner: collecting user payment features based on the collection component configured in the cash register; identifying the user payment features to obtain the user payment identifier associated with the user payment features; generating a payment request carrying the user payment identifier and the order to be paid and sending it to the payment platform for payment processing; and receiving the payment bill sent by the payment platform after successful payment processing.

[0162] In the specific execution process, after receiving the payment bill sent by the payment platform after successful payment processing, the POS device can render and display a payment success page to make the payment result more intuitive for the user and the cashier. In this embodiment, in order to automate the invoice application after payment processing, the invoice issuance process is performed asynchronously after obtaining the payment bill. To further improve the user and cashier's perception of the invoice issuance process, in an optional implementation of this embodiment, after obtaining the payment bill, a payment success page is rendered and displayed based on the acquisition of the payment bill; optionally, the payment success page displays an invoice application reminder layer.

[0163] For example, after the POS device receives the payment bill, it renders a payment success page and displays a pop-up window on the payment success page saying "Initiating invoice issuance asynchronously, the invoice will be sent to the user's email address later".

[0164] In practice, the system queries whether the storage unit of the POS device stores ticket-related data containing the user's payment identifier. The storage unit includes a storage area configured within the POS device for data storage; for example, a cache module of the POS device. The ticket-related data includes relevant data for issuing tickets to the user, constructed from the user's payment identifier and ticket application information. For example, the association between the user's payment identifier and ticket application information.

[0165] Optionally, the storage unit stores a preset number of invoice-related data; the invoice-related data stored in the storage unit is constructed based on the user's payment identifier and the invoice application information pre-entered by the user.

[0166] In practical applications, due to the limited storage space of the storage unit, in order to avoid storing unused ticket-related data in the storage unit, resulting in a large storage volume in the storage unit and affecting the operation of the cash register, the preset number of ticket-related data stored in the storage unit may be determined based on the usage frequency of the ticket application information contained in the ticket-related data.

[0167] Optionally, the storage unit stores a preset number of invoice-related data; the invoice-related data stored in the storage unit is constructed based on the user's payment identifier and the invoice application information pre-entered by the user.

[0168] In practical applications, due to the limited storage space of the storage unit, in order to avoid storing unused ticket-related data in the storage unit, resulting in a large storage volume in the storage unit and affecting the operation of the cash register, the preset number of ticket-related data stored in the storage unit may be determined based on the usage frequency of the ticket application information contained in the ticket-related data.

[0169] Alternatively, the document association data stored in the storage unit can be managed each time document association data is stored in the storage unit. Specifically, since new document association data needs to be added to the storage queue, the number of document association data in the storage queue must be less than a preset threshold. During the management of the storage unit, the following operations are performed:

[0170] Calculate the amount of document-related data stored in the unit;

[0171] If the number of data is greater than or equal to a preset number, the bill association data stored in the storage unit is sorted in descending order according to the frequency of use of bill application information in the stored bill association data to obtain a storage queue; the bill association data in the sorted queue that is after the position corresponding to the preset number is deleted.

[0172] If the amount of data is less than or equal to the preset amount, no processing is required.

[0173] In addition, the number of storage units can be unlimited, and the decision to delete the invoice-related data from the storage unit can be based solely on the frequency of use of the invoice-related data stored in the storage unit; specifically, the frequency of data use of the invoice-related data stored in the storage unit can be detected; and invoice-related data in the storage unit whose data use frequency is less than the frequency threshold (x times / month) can be deleted.

[0174] In the specific execution process, based on the payment bill obtained after payment processing based on the user's payment identifier, the system queries whether the storage unit of the POS device stores ticket application information containing the user's payment identifier; if so, it generates a ticket application request carrying the ticket application information and the payment bill and sends it to the service platform to apply for a ticket.

[0175] In this embodiment, if the execution result after querying whether the storage unit of the POS device stores ticket-related data containing the user's payment identifier is negative, since the service platform has a large storage space, all ticket-related data stored in the storage unit of the POS device will be stored on the service platform. Therefore, as long as the user has entered the data, it will be stored in the storage space of the service platform. Thus, after querying that the storage unit of the POS device does not contain ticket-related data containing the user's payment identifier, a further query is performed on the service platform to retrieve ticket-related data containing the user's payment identifier. This improves the efficiency of ticket application and further ensures that the user only needs to enter the data to apply for multiple tickets.

[0176] This embodiment provides two optional implementation methods. The following describes in detail the processing methods when the storage unit of the cash register does not find the ticket-related data containing the user's payment identifier.

[0177] (1) In this embodiment, if no ticket-related data containing the user's payment identifier is found in the storage unit of the cash register, the following operation is performed:

[0178] Send an information query request carrying the user's payment identifier to the service platform to perform a query on the service platform for invoice-related data containing the user's payment identifier;

[0179] If the service platform receives bill application information contained in the queried bill association data, a bill application request carrying the bill application information and the payment bill is generated and sent to the service platform to apply for the bill.

[0180] If the query result sent by the service platform is empty, a reminder to enter the invoice application information is displayed; the invoice application information entered and submitted by the user is obtained, an invoice application request carrying the payment bill and the invoice application information submitted by the user is generated and sent to the service platform to apply for the invoice.

[0181] Specifically, the system checks whether the storage unit of the POS device stores ticket-related data containing the user's payment identifier. If not, it queries the service platform for ticket-related data containing the user's payment identifier. If the service platform finds ticket-related information containing the user's payment identifier, it generates a ticket application request carrying the ticket application information and payment bill from the ticket-related information and sends it to the service platform to apply for a ticket. The system then receives the ticket application result from the service platform.

[0182] If the query result from the service platform is empty, the user needs to enter the invoice application information; that is, if the query result from the service platform is empty, the system interacts with the user to obtain the invoice application information, generates an invoice application request based on the payment bill and the obtained invoice application information, and sends it to the service platform to apply for the invoice; and receives the invoice application result sent by the service platform.

[0183] The POS device sends an information query request carrying the user's payment identifier to the service platform. The service platform checks whether there is any ticket-related data containing the user's payment identifier. If so, it sends the ticket application information contained in the queried ticket-related data to the POS device. If not, it sends an empty query result to the POS device.

[0184] After receiving the ticket application information from the service platform, in order to update the storage unit, in an optional implementation of this embodiment, the POS device updates the ticket-related data stored in the storage unit in the following manner:

[0185] Based on the user's payment identifier and the invoice application information sent by the service platform, invoice association data is constructed;

[0186] The constructed invoice association data is written to the storage unit.

[0187] Specifically, after receiving the ticket application information sent by the service platform, the ticket association data containing the user payment identifier and the ticket application information sent by the service platform is stored in the storage unit of the POS device, so that a ticket application can be made based on the ticket application information after the user to whom the user payment identifier belongs makes a payment.

[0188] When the POS device receives an empty query result from the service platform, in order to issue a receipt for the user's payment, it interacts with the user to obtain the receipt application information entered by the user. To ensure that subsequent payments by the same user can be processed without requiring further receipt application information from the user, in this embodiment, after obtaining the user's entered and submitted receipt application information, the following operations are also performed:

[0189] Based on the user's payment identifier and the invoice application information submitted by the user, invoice association data is constructed;

[0190] The constructed invoice association data is written into the storage unit and sent to the service platform for storage.

[0191] Specifically, the POS device displays a reminder to enter receipt application information. Users can enter receipt application information using the POS device, or they can obtain the user's receipt application information by displaying an information identifier associated with the receipt application information. The POS device can collect and identify the information identifier to obtain the user's receipt application information. The information identifier can be a QR code, barcode, etc.

[0192] Furthermore, after obtaining the user's input ticket application information, to ensure that the user can apply for a ticket without having to input the application information again during subsequent payments via the POS device, the ticket association data, including the user's payment identifier and the submitted ticket application information, is stored in the POS device's storage unit. Since the storage unit will evict key ticket data to ensure the POS device's operational efficiency, to further guarantee the effective storage of the user's ticket application information, after constructing the ticket association data, it is sent to the service platform for storage. In other words, after obtaining the user's input ticket application information, the ticket association data based on the user's payment identifier and submitted ticket application information is stored in the storage unit and on the service platform. This ensures that even if the ticket association data is deleted from the storage unit, it can still be retrieved on the service platform, improving the effectiveness of storage.

[0193] (2) The above method provides a process of querying the service platform for the bill association data containing the user payment identifier after failing to find the bill association data containing the user payment identifier in the storage unit; in this embodiment, after failing to find the bill association data containing the user payment identifier in the storage unit, a bill issuance request carrying the payment bill is generated and sent to the service platform to issue the bill; and the bill issuance result sent by the service platform after issuing the bill is received.

[0194] The service platform issues invoices based on the invoice issuance request. To ensure the authenticity of the invoices, they must be issued by a platform with invoice issuance qualifications. Therefore, in this embodiment, the invoice issuance by the service platform includes the following operations:

[0195] Check whether invoice-related data containing the user's payment identifier carried on the payment bill is stored;

[0196] If so, read the invoice application information from the queried invoice association data and generate invoice issuance information carrying the queried invoice application information and the payment bill; send the invoice issuance information to the invoice platform configured on the cash register, and send the invoice issuance result to the cash register according to the invoice information sent by the invoice platform;

[0197] If not, a receipt issuance result with empty receipt application information is sent to the POS device so that the POS device can collect receipt application information and send a receipt application request.

[0198] Specifically, the POS device checks whether the storage unit stores invoice-related data containing the user's payment identifier. If not, it sends a invoice issuance request carrying the payment bill to the service platform to issue the invoice. The service platform issues the invoice based on the invoice issuance request and sends the invoice issuance result. The POS device receives the invoice issuance result sent by the service platform.

[0199] In practice, the process of issuing invoices requires the use of the user's invoice application information, the payment bill information, and / or the merchant's relevant information. Therefore, the service platform needs to encapsulate the information required for the invoice issuance process and send the encapsulated invoice issuance information to the invoice platform configured for the POS device for invoice issuance.

[0200] In this embodiment, after receiving a ticket issuance request, the service platform encapsulates the request to obtain ticket issuance information and sends the information to the ticket platform configured for the POS device. The process by which the service platform encapsulates the ticket application request to obtain ticket issuance information can be implemented as follows:

[0201] The configuration information of the cash register is read based on the device identifier carried in the ticket issuance request.

[0202] Extract the ticket auxiliary information contained in the configuration information;

[0203] The auxiliary information of the invoice, the queried invoice application information, and the payment bill carried in the invoice issuance request are identified as the invoice issuance information.

[0204] Optionally, the device identifier is the identifier of the POS device; the configuration information is entered and submitted by the merchant to which the POS device belongs.

[0205] Specifically, the service platform queries whether it stores invoice-related data containing the user's payment identifier carried on the payment bill based on the invoice issuance request; if so, it reads the invoice application information contained in the queried invoice-related data, and reads the invoice auxiliary information of the POS device based on the device identifier carried on the invoice issuance request; and sends the invoice application information, invoice auxiliary information, and payment bill as invoice issuance information to the invoice platform configured for the POS device.

[0206] If not, send a receipt application result with empty receipt application information to the POS device to allow for the entry of receipt application information.

[0207] Furthermore, after obtaining the invoice issuance information, the service platform sends the invoice issuance information to the invoice platform configured for the POS device; in this embodiment, the merchant can configure the invoice platform to issue invoices for the merchant's payment bills.

[0208] Based on this, in this embodiment, during the process of sending the invoice issuance information to the invoice platform configured for the POS device, the platform identifier contained in the configuration information of the POS device is first read; then the invoice issuance information is passed to the interface corresponding to the platform identifier.

[0209] Specifically, during the process of the service platform sending invoice issuance information to the invoice platform, the invoice issuance information is passed to the interface corresponding to the platform identifier contained in the configuration information of the POS device.

[0210] It should be noted that merchants can input configuration information through the POS device, which then sends the configuration information to the service platform for storage. In one optional implementation of this embodiment, the POS device performs the following operations:

[0211] Obtain the configuration information for the POS device entered by the merchant;

[0212] The configuration information and the device identifier of the POS device are sent to the service platform for configuration information storage.

[0213] Optionally, the configuration information includes the platform identifier of the ticketing platform configured for the POS device; specifically, the service platform stores the configuration information of the POS device.

[0214] In practice, the POS device generates a receipt application request carrying the receipt application information and the payment bill and sends it to the service platform to apply for a receipt.

[0215] The invoice application request includes a request to the service platform to apply for an invoice, carrying invoice application information and a payment bill. An invoice issuance request is also provided, the difference being that the invoice issuance request does not carry invoice application information. Optionally, the invoice application request is generated after the storage unit of the POS device stores invoice-related data containing the user payment identifier carried on the payment bill.

[0216] In specific implementation, after the above query is performed to see if the storage unit of the POS device stores the ticket-related data containing the user's payment identifier, if the storage unit stores the ticket-related data containing the user's payment identifier, a ticket application request carrying the payment bill and the ticket application information contained in the ticket-related data is generated and sent to the service platform to apply for the ticket.

[0217] Alternatively, after executing the above query to see if the storage unit of the POS device stores ticket-related data containing the user's payment identifier, if the storage unit does not store ticket-related data containing the user's payment identifier, then query the service platform to see if it stores ticket-related data containing the user's payment identifier; if the service platform sends the ticket application information contained in the queried ticket-related data, then a ticket application request carrying the payment bill and the ticket application information is generated and sent to the service platform.

[0218] Step S504: Based on the invoice application request, encapsulate the invoice issuance information to obtain invoice issuance information, and send the invoice issuance information to the invoice platform configured for the cash register device.

[0219] The service platform receives a ticket application request from the POS device, encapsulates the ticket application request to obtain ticket issuance information, and sends the ticket issuance information to the ticket platform configured for the POS device.

[0220] In this embodiment, the service platform performs information encapsulation processing in the following manner:

[0221] The configuration information of the POS device is read based on the device identifier carried in the ticket application request.

[0222] Extract the ticket auxiliary information contained in the configuration information;

[0223] The auxiliary information of the invoice and the payment bill and invoice application information carried in the invoice application request are identified as the invoice issuance information.

[0224] Specifically, the service platform reads the receipt auxiliary information of the POS device based on the receipt application request sent by the POS device, and determines the receipt auxiliary information and the payment bill and receipt application information carried in the receipt application request as the receipt issuance information.

[0225] Furthermore, in this embodiment, the service platform performs the following operations when sending invoice issuance information to the invoice platform configured for the POS device:

[0226] Read the platform identifier contained in the configuration information of the POS device;

[0227] The invoice issuance information is passed to the interface corresponding to the platform identifier.

[0228] Specifically, after determining the invoice issuance information, the service platform transmits the invoice issuance information to the interface corresponding to the platform identifier contained in the configuration information of the POS device.

[0229] In practice, the POS device receives the receipt application result sent by the service platform. The receipt application result includes a successful receipt application result; in addition, it may also include a failed receipt application result; to improve the POS terminal's perception of receipt information, the receipt application result may optionally include receipt information.

[0230] Step S506: Based on the ticket information returned by the ticket platform, send the ticket application result to the cash register device.

[0231] In the above steps, the service platform sends invoice issuance information to the invoice platform; the invoice platform issues invoices based on the invoice issuance information and obtains the invoice information corresponding to the payment bill; in order to improve the service platform's management of invoice information, the invoice platform sends the invoice information to the service platform after generating the invoice information; after receiving the invoice information, the service platform sends the invoice issuance result to the cash register.

[0232] Among them, bill information refers to the vouchers obtained after the issuance of a bill; such as a bill or a bill voucher.

[0233] For example, after determining the invoice issuance information, the service platform sends it to the invoice platform. The invoice platform generates an invoice based on the invoice application information, payment bill, and invoice auxiliary information contained in the invoice issuance information, and sends the invoice to the service platform. After receiving the invoice, the service platform sends the successful invoice application result to the cash register.

[0234] The POS device receives the receipt application result from the service platform. To improve the user's awareness of the receipt application result, the POS device can display the receipt application result after receiving it.

[0235] It should be noted that the bill application information includes the user's communication identifier, such as an email address. After the bill platform issues the bill, it sends the bill to the user based on the communication channel corresponding to the user's communication identifier included in the bill application information.

[0236] In summary, the bill processing method provided in this embodiment involves the following steps: After the POS device receives the payment bill obtained after payment processing based on the user's payment identifier, it checks the storage unit to see if there is any bill application information associated with the user's payment identifier. If so, it generates a bill application request carrying the bill application information and the payment bill and sends it to the service platform to apply for a bill. Based on the bill application request, the service platform sends the POS device's bill auxiliary information, bill application information, and payment bill to the bill platform corresponding to the POS device. The bill platform issues a bill based on the bill auxiliary information, bill application information, and payment bill, and sends the obtained bill to the service platform. The service platform adds the bill to the bill list and sends the bill application result to the POS device.

[0237] If the POS device does not find the receipt application information associated with the user's payment identifier in the storage unit, it sends an information query request to the service platform. The service platform checks whether the receipt application information associated with the user's payment identifier is stored. If so, it sends the queried receipt application information to the POS device. The POS device generates receipt application information based on the payment bill and the receipt application information sent to the service platform and sends it to the service platform. Based on the receipt application request, the service platform sends the receipt application information, the payment bill, and the POS device's receipt auxiliary information to the corresponding receipt platform. The receipt platform issues a receipt based on the receipt auxiliary information, the receipt application information, and the payment bill, and sends the obtained receipt to the service platform. The service platform adds the receipt to the receipt list and sends the receipt application result to the POS device.

[0238] If the service platform does not find the invoice application information associated with the user's payment identifier, it sends an empty query result to the POS device. The POS device interacts with the user based on the empty query result to obtain the invoice application information entered by the user, and generates invoice application information based on the payment bill and the user's entered information, then sends it to the service platform. Based on the invoice application request, the service platform sends the invoice application information, the payment bill, and the POS device's invoice auxiliary information to the corresponding invoice platform. The invoice platform issues the invoice based on the invoice auxiliary information, the invoice application information, and the payment bill, and sends the obtained invoice to the service platform. The service platform adds the invoice to its invoice list and sends the invoice application result to the POS device.

[0239] Therefore, users only need to enter bill application information during the initial payment and bill issuance process. The bill application information entered by the user is associated with and stored with the user's payment identifier. The user can then use the bill application information in subsequent payment and bill issuance processes. This eliminates the need for users to enter bill application information multiple times, which would otherwise lead to low efficiency in bill issuance. This improves the efficiency of user payment and bill issuance, and in turn, enhances the user's perception of the payment and bill issuance process.

[0240] The following example uses a bill processing method provided in this embodiment in the scenario of initial bill issuance as an illustration. Figure 2 and Figure 3 For further explanation of the invoice processing method provided in this embodiment, please refer to [link / reference]. Figure 3 The invoice processing method applied to the first invoice issuance scenario includes the following steps.

[0241] like Figure 2 As shown, merchants enter configuration information, including the platform identifier for issuing receipts, through the POS device interface. The POS device uploads the configuration information to the service platform (the platform corresponding to the POS device), and the service platform stores the configuration information of the POS device.

[0242] After a user makes a purchase at a merchant, the POS device collects the user's facial image or payment identifier code. The POS device then initiates payment to the payment platform based on the collected facial image or payment identifier code. After processing the payment, the payment platform obtains a payment bill and sends it to the POS device. Upon receiving the payment bill processed based on the user's payment identifier, the POS device first checks its storage unit for any invoice application information associated with the user's payment identifier. If invoice application information is found, it sends an invoice application request to the service platform based on the invoice application information and the payment bill.

[0243] If the POS device does not find any receipt application information associated with the user's payment identifier stored in the storage unit, the POS device will query the service platform for the receipt application information associated with the user's payment identifier. If the query is empty, the user is determined to be a first-time payment user. The user enters the receipt application information through the POS device interface, and the POS device sends the association relationship between the user's payment identifier and the receipt application information entered by the user to the service platform for storage.

[0244] Based on the invoice application information and payment bill, an invoice application request is generated and sent to the service platform. The service platform reads the invoice auxiliary information from the configuration information of the POS device based on the invoice application request, and sends the invoice auxiliary information, invoice application information and payment bill to the invoice platform corresponding to the POS device to issue the invoice.

[0245] In addition, the data connection between the POS device and the billing platform can be configured. After obtaining the bill application information, the POS device generates a bill issuance request based on the bill application information, payment bill and the bill auxiliary information of the POS device and sends it to the billing platform corresponding to the POS device to issue the bill.

[0246] Step S318: Read the ticket auxiliary information of the cash register based on the ticket application request.

[0247] Step S320: Generate a bill issuance request based on the bill application information, payment bill, and bill auxiliary information.

[0248] Step S322: Send a bill issuance request to the bill platform corresponding to the cash register device.

[0249] Step S324: Receive the invoice returned by the invoice platform and add the invoice to the invoice list.

[0250] Step S326: Send the successful receipt application result to the POS device.

[0251] The following description uses the application of a bill processing method provided in this embodiment in a bill issuance scenario as an example to further illustrate the bill processing method provided in this embodiment. (See also...) Figure 4 The bill processing method applied to bill issuance scenarios includes the following steps.

[0252] Step S410: Check if there is any invoice application information associated with the user's payment channel identifier.

[0253] Step S412: Send the retrieved ticket application information to the POS device.

[0254] Step S418: Read the ticket auxiliary information of the cash register based on the ticket application request.

[0255] Step S420: Generate a bill issuance request based on the bill application information, payment bill, and bill auxiliary information.

[0256] Step S422: Send a bill issuance request to the bill platform corresponding to the cash register device.

[0257] Step S424: Receive the invoice returned by the invoice platform and add the invoice to the invoice list.

[0258] Step S426: Send the successful receipt application result to the POS device.

[0259] The following is an embodiment of a ticket processing device provided in this specification:

[0260] In the above embodiments, a ticket processing method for a cash register is provided, and correspondingly, a ticket processing device for a cash register is also provided, which will be described below with reference to the accompanying drawings.

[0261] Reference Figure 6 The diagram shows a schematic of a ticket processing device provided in this embodiment.

[0262] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0263] This embodiment provides a ticket processing device, including:

[0264] The payment bill retrieval module 602 is configured to retrieve the payment bill obtained after payment processing based on the user's payment identifier.

[0265] The data query module 604 is configured to query whether the storage unit of the POS device stores ticket-related data containing the user's payment identifier; the ticket-related data is constructed from the user's payment identifier and the ticket application information pre-entered by the user.

[0266] If so, the request generation module 606 is run. The request generation module 606 is configured to generate a bill application request carrying the bill application information and the payment bill and send it to the service platform to apply for a bill.

[0267] The result receiving module 608 is configured to receive the ticket application result sent by the service platform.

[0268] Another embodiment of the ticket processing device provided in this specification is as follows:

[0269] In the above embodiments, a bill processing method applied to a service platform is provided, and correspondingly, a bill processing device running on the service platform is also provided, which will be described below with reference to the accompanying drawings.

[0270] Reference Figure 7 The diagram shows a schematic of a ticket processing device provided in this embodiment.

[0271] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0272] This embodiment provides a ticket processing device, including:

[0273] The request receiving module 702 is configured to receive a ticket application request sent by the cash register device; the ticket application request is generated after the cash register device's storage unit stores ticket-related data including the user payment identifier carried on the payment bill.

[0274] The encapsulation processing module 704 is configured to encapsulate the invoice application request to obtain invoice issuance information, and send the invoice issuance information to the invoice platform configured for the cash register device;

[0275] The result sending module 706 is configured to send the ticket application result to the cash register device based on the ticket information returned by the ticket platform.

[0276] The following is an embodiment of a ticket processing device provided in this specification:

[0277] Corresponding to the above-described method for processing receipts applied to a cash register, based on the same technical concept, one or more embodiments of this specification also provide a receipt processing device for executing the above-described method for processing receipts applied to a cash register. Figure 8 This is a schematic diagram of the structure of a ticket processing device provided for one or more embodiments of this specification.

[0278] This embodiment provides a ticket processing device, including:

[0279] like Figure 8 As shown, the ticket processing device can vary considerably due to differences in configuration or performance. It may include one or more processors 801 and a memory 802, where one or more application programs or data may be stored. The memory 802 may be temporary or persistent storage. The application programs stored in the memory 802 may include one or more modules (not shown), each module including a series of computer-executable instructions from the ticket processing device. Furthermore, the processor 801 may be configured to communicate with the memory 802 and execute the series of computer-executable instructions stored in the memory 802 on the ticket processing device. The ticket processing device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.

[0280] In one specific embodiment, the ticket processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the ticket processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0281] Obtain the payment bill obtained after payment processing based on the user's payment identifier;

[0282] Check whether the storage unit of the POS device stores ticket association data containing the user's payment identifier; the ticket association data is constructed from the user's payment identifier and the ticket application information pre-entered by the user;

[0283] If so, generate a bill application request carrying the bill application information and the payment bill and send it to the service platform to apply for the bill;

[0284] Receive the ticket application result sent by the service platform.

[0285] Another embodiment of the ticket processing device provided in this specification is as follows:

[0286] Corresponding to the above-described method for processing invoices applied to a service platform, based on the same technical concept, one or more embodiments of this specification also provide an invoice processing device for executing the above-described method for processing invoices applied to a service platform. Figure 9 This is a schematic diagram of the structure of a ticket processing device provided for one or more embodiments of this specification.

[0287] This embodiment provides a ticket processing device, including:

[0288] like Figure 9 As shown, the ticket processing device can vary significantly due to differences in configuration or performance. It may include one or more processors 901 and a memory 902, where one or more application programs or data may be stored. The memory 902 may be temporary or persistent storage. The application programs stored in the memory 902 may include one or more modules (not shown), each module including a series of computer-executable instructions from the ticket processing device. Furthermore, the processor 901 may be configured to communicate with the memory 902 and execute the series of computer-executable instructions stored in the memory 902 on the ticket processing device. The ticket processing device may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input / output interfaces 905, one or more keyboards 906, etc.

[0289] In one specific embodiment, the ticket processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the ticket processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0290] Receive a receipt request sent by the POS device; the receipt request is generated after the POS device's storage unit stores receipt-related data including the user's payment identifier carried on the payment bill;

[0291] The bill application request is encapsulated to obtain bill issuance information, and the bill issuance information is sent to the bill platform configured for the POS device.

[0292] Based on the ticket information returned by the ticket platform, the ticket application result is sent to the POS device.

[0293] This specification provides an example of a storage medium as follows:

[0294] Corresponding to the above-described method for processing receipts in a cash register, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0295] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0296] Obtain the payment bill obtained after payment processing based on the user's payment identifier;

[0297] Check whether the storage unit of the POS device stores ticket association data containing the user's payment identifier; the ticket association data is constructed from the user's payment identifier and the ticket application information pre-entered by the user;

[0298] If so, generate a bill application request carrying the bill application information and the payment bill and send it to the service platform to apply for the bill;

[0299] Receive the ticket application result sent by the service platform.

[0300] It should be noted that the embodiments concerning the storage medium in this specification and the embodiments concerning the ticket processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0301] Another embodiment of the storage medium provided in this specification is as follows:

[0302] Corresponding to the above-described method for processing invoices applied to a service platform, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0303] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0304] Receive a receipt request sent by the POS device; the receipt request is generated after the POS device's storage unit stores receipt-related data including the user's payment identifier carried on the payment bill;

[0305] The bill application request is encapsulated to obtain bill issuance information, and the bill issuance information is sent to the bill platform configured for the POS device.

[0306] Based on the ticket information returned by the ticket platform, the ticket application result is sent to the POS device.

[0307] It should be noted that the embodiments concerning the storage medium in this specification and the embodiments concerning the ticket processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0308] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0309] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0310] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0311] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0312] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0313] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0314] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0315] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0316] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0317] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0318] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0319] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0320] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0321] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0322] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

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

Claims

1. A bill processing method, applied to a merchant's POS equipment, comprising: Obtain the payment bill obtained after payment processing based on the user's payment identifier; The system queries whether the storage unit of the POS device stores ticket-related data containing the user's payment identifier; the preset number of ticket-related data stored in the storage unit is constructed from the user's payment identifier and the ticket application information pre-entered by the user, and the preset number is determined based on the frequency of use of the ticket application information contained in the ticket-related data; If not, send an information query request carrying the user's payment identifier to the service platform. If the service platform sends a query of the bill association data containing the bill application information, generate a bill application request carrying the bill application information and the payment bill and send it to the service platform. The service platform reads the platform identifier of the bill platform configured for the POS device based on the device identifier of the POS device in the bill application request. Receive the bill application result sent by the service platform based on the bill information returned by the bill platform.

2. The ticket processing method according to claim 1, if the execution result after the step of querying whether the storage unit of the cash register device stores ticket-related data containing the user payment identifier is yes, the following steps are executed: Generate a bill application request carrying the bill application information and the payment bill and send it to the service platform to apply for a bill.

3. The bill processing method according to claim 1 further includes: If the query result sent by the service platform is empty, a reminder to enter the invoice application information will be displayed; The system obtains the bill application information entered and submitted by the user, generates a bill application request carrying the payment bill and the bill application information submitted by the user, and sends it to the service platform to apply for the bill.

4. The bill processing method according to claim 3, after the operation of obtaining the bill application information entered and submitted by the user is performed, it further includes: Based on the user's payment identifier and the invoice application information submitted by the user, invoice association data is constructed; The constructed invoice association data is written into the storage unit and sent to the service platform for storage.

5. The ticket processing method according to claim 1, after the step of querying whether the storage unit of the cash register device stores ticket-related data containing the user payment identifier is executed, it further includes: Generate a bill issuance request carrying the payment bill and send it to the service platform to issue the bill; Receive the invoice issuance result sent by the service platform after the invoice is issued.

6. The bill processing method according to claim 5, wherein the bill issuance includes: Check whether invoice-related data containing the user's payment identifier carried on the payment bill is stored; If so, read the invoice application information from the queried invoice association data and generate invoice issuance information carrying the queried invoice application information and the payment bill; The system sends the invoice issuance information to the invoice platform configured on the POS device, and sends the invoice issuance result to the POS device based on the invoice information sent by the invoice platform.

7. The bill processing method according to claim 1 further includes: Calculate the amount of invoice-related data stored in the storage unit; If the amount of data is greater than or equal to a preset amount, the bill association data stored in the storage unit is sorted in descending order according to the frequency of use of bill application information in the stored bill association data to obtain a storage queue. Delete the ticket-related data for the position following the preset number in the storage queue.

8. The bill processing method according to claim 1 further includes: Based on the user's payment identifier and the invoice application information sent by the service platform, invoice association data is constructed; The constructed invoice association data is written to the storage unit.

9. The bill processing method according to claim 1, wherein obtaining the payment bill obtained after payment processing based on the user payment identifier includes: The user's payment characteristics are collected based on the data acquisition components configured in the POS device; Generate a payment request carrying the user's payment characteristics and the order to be paid, and send it to the payment platform for payment processing; Receive the payment bill sent by the payment platform after successful payment processing.

10. The bill processing method according to claim 1, wherein the user payment identifier includes at least one of the following: User identification, and the channel identification for the payment channel used for payment processing.

11. The bill processing method according to claim 1, further comprising: Obtain the configuration information for the POS device entered by the merchant; The configuration information includes the platform identifier of the ticket platform configured for the POS device; The configuration information and the device identifier of the POS device are sent to the service platform for configuration information storage.

12. The bill processing method according to claim 1, after the step of obtaining the payment bill obtained after payment processing based on the user payment identifier is performed, it further includes: Render and display the payment success page based on the obtained payment bill; The payment success page displays a receipt application reminder layer.

13. A bill processing method, applied to a service platform, comprising: Receive an information query request sent by the POS device carrying the user's payment identifier, and query whether the ticket association data containing the user's payment identifier is stored; If so, send the ticket application information contained in the queried ticket association data to the POS device; The system receives a receipt request from the POS device and reads the platform identifier of the receipt platform configured for the POS device based on the device identifier of the POS device in the receipt request. The receipt request is generated after the POS device's storage unit stores receipt-related data containing the user's payment identifier carried on the payment bill. The preset number of receipt-related data stored in the storage unit is constructed from the user's payment identifier and the receipt request information pre-entered by the user. The preset number is determined based on the frequency of use of the receipt request information contained in the receipt-related data. The bill application request is encapsulated to obtain bill issuance information, and the bill issuance information is sent to the bill platform. Based on the ticket information returned by the ticket platform, the ticket application result is sent to the POS device.

14. The bill processing method according to claim 13, wherein the step of encapsulating the bill application request to obtain bill issuance information includes: The configuration information of the POS device is read based on the device identifier carried in the ticket application request. Extract the ticket auxiliary information contained in the configuration information; The auxiliary information of the invoice and the payment bill and invoice application information carried in the invoice application request are identified as the invoice issuance information.

15. The bill processing method according to claim 13, wherein sending the bill issuance information to the bill platform includes: Read the platform identifier contained in the configuration information of the POS device; The invoice issuance information is passed to the interface corresponding to the platform identifier.

16. A receipt processing device, operating on a merchant's point-of-sale (POS) equipment, comprising: The payment bill retrieval module is configured to retrieve the payment bill obtained after payment processing based on the user's payment identifier; The data query module is configured to query whether the storage unit of the POS device stores ticket-related data containing the user's payment identifier; the preset number of ticket-related data stored in the storage unit is constructed from the user's payment identifier and the ticket application information pre-entered by the user, and the preset number is determined based on the usage frequency of the ticket application information contained in the ticket-related data; if not, an information query request carrying the user's payment identifier is sent to the service platform; if the service platform sends a query request to the POS device containing the ticket application information, a ticket application request carrying the ticket application information and the payment bill is generated and sent to the service platform; the service platform reads the platform identifier of the ticket platform configured for the POS device based on the device identifier of the POS device in the ticket application request; The result receiving module is configured to receive the bill application result sent by the service platform based on the bill information returned by the bill platform.

17. A ticket processing device, operating on a service platform, comprising: The request receiving module is configured to receive an information query request carrying a user payment identifier sent by the POS device, and query whether ticket association data containing the user payment identifier is stored; if so, send the ticket application information contained in the queried ticket association data to the POS device; receive the ticket application request sent by the POS device, and read the platform identifier of the ticket platform configured for the POS device based on the device identifier of the POS device in the ticket application request; the ticket application request is generated after the POS device's storage unit stores ticket association data containing the user payment identifier carried by the payment bill; the preset number of ticket association data stored in the storage unit is constructed from the user payment identifier and the ticket application information pre-entered by the user, and the preset number is determined based on the usage frequency of the ticket application information contained in the ticket association data; The encapsulation processing module is configured to encapsulate the invoice application request to obtain invoice issuance information, and send the invoice issuance information to the invoice platform configured for the cash register device; The result sending module is configured to send the ticket application result to the cash register device based on the ticket information returned by the ticket platform.

18. A ticket processing device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Obtain the payment bill obtained after payment processing based on the user's payment identifier; Check whether the storage unit of the POS device stores ticket-related data containing the user's payment identifier; the preset number of ticket-related data stored in the storage unit is constructed from the user's payment identifier and the ticket application information pre-entered by the user, and the preset number is determined based on the frequency of use of the ticket application information contained in the ticket-related data; If not, send an information query request carrying the user's payment identifier to the service platform. If the service platform sends a query of the bill association data containing the bill application information, generate a bill application request carrying the bill application information and the payment bill and send it to the service platform. The service platform reads the platform identifier of the bill platform configured for the POS device based on the device identifier of the POS device in the bill application request. Receive the bill application result sent by the service platform based on the bill information returned by the bill platform.

19. A ticket processing device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Receive an information query request sent by the POS device carrying the user's payment identifier, and query whether the ticket association data containing the user's payment identifier is stored; If so, send the ticket application information contained in the queried ticket association data to the POS device; The system receives a receipt request from the POS device and reads the platform identifier of the receipt platform configured for the POS device based on the device identifier of the POS device in the receipt request. The receipt request is generated after the POS device's storage unit stores receipt-related data containing the user's payment identifier carried on the payment bill. The preset number of receipt-related data stored in the storage unit is constructed from the user's payment identifier and the receipt request information pre-entered by the user. The preset number is determined based on the frequency of use of the receipt request information contained in the receipt-related data. The bill application request is encapsulated to obtain bill issuance information, and the bill issuance information is sent to the bill platform configured for the POS device. Based on the ticket information returned by the ticket platform, the ticket application result is sent to the POS device.

20. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Obtain the payment bill obtained after payment processing based on the user's payment identifier; Check whether the storage unit of the POS device stores ticket-related data containing the user's payment identifier; the preset number of ticket-related data stored in the storage unit is constructed from the user's payment identifier and the ticket application information pre-entered by the user, and the preset number is determined based on the frequency of use of the ticket application information contained in the ticket-related data; If not, send an information query request carrying the user's payment identifier to the service platform. If the service platform sends a query of the bill association data containing the bill application information, generate a bill application request carrying the bill application information and the payment bill and send it to the service platform. The service platform reads the platform identifier of the bill platform configured for the POS device based on the device identifier of the POS device in the bill application request. Receive the bill application result sent by the service platform based on the bill information returned by the bill platform.

21. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Receive an information query request sent by the POS device carrying the user's payment identifier, and query whether the ticket association data containing the user's payment identifier is stored; If so, send the ticket application information contained in the queried ticket association data to the POS device; The system receives a receipt request from the POS device and reads the platform identifier of the receipt platform configured for the POS device based on the device identifier of the POS device in the receipt request. The receipt request is generated after the POS device's storage unit stores receipt-related data containing the user's payment identifier carried on the payment bill. The preset number of receipt-related data stored in the storage unit is constructed from the user's payment identifier and the receipt request information pre-entered by the user. The preset number is determined based on the frequency of use of the receipt request information contained in the receipt-related data. The bill application request is encapsulated to obtain bill issuance information, and the bill issuance information is sent to the bill platform configured for the POS device. Based on the ticket information returned by the ticket platform, the ticket application result is sent to the POS device.

Images