A design method for implementing a unique electronic receipt

Abstract

The application relates to the technical field of information processing, in particular to a design method of an electronic receipt with uniqueness, which comprises the following steps: S1, generating an electronic receipt according to an electronic receipt issuing request, wherein the electronic receipt issuing request comprises data associated with the generated electronic receipt; S2, pushing a notification of electronic receipt issuing completion, wherein the notification comprises an acquisition position of the electronic receipt; S2-1, generating electronic data and pushing the electronic data to a designated person; S3, electronic receipt uniqueness: S3-1, there is space for storing a digital signature in a file of the electronic receipt, and there are at least two digital signatures. One is a signature of initial created content, which is represented by Sign1, and this part will always not be modified. Another is a signature of newly added data content and original content after transmission, which is represented by Sign2. The application can back up a certain electronic transaction receipt before transmission, and the backup cannot be transferred again after the electronic transaction receipt is transferred once, so that the uniqueness of the electronic receipt is ensured.

Description

Technical Field

[0001] This invention relates to the field of information processing technology, and in particular to a design method for achieving unique electronic receipts. Background Technology

[0002] Receipts are original vouchers used by enterprises and institutions in economic activities, specifically divided into internal and external receipts. External receipts include those supervised by tax authorities (for non-taxable transactions), those supervised by finance departments, and military receipts, etc.; internal receipts are self-made legal vouchers created within enterprises and institutions for internal business transactions. Receipts are usually the basis for deducting relevant expenses when calculating taxable income for enterprise income tax purposes. Currently popular B2B and C2B businesses also require invoices, receipts, or internal vouchers issued by tax authorities as pre-tax deduction vouchers. For large group enterprises and major internet platforms with substantial B2B and C2B business, how to reduce the resources and costs consumed by paper receipt management and achieve standardized electronic receipt services is a problem that needs to be solved. With increasing digitalization in daily life and production, receipts are needed to record transaction information. Previously, and still today, this primarily involved printing out paper slips, which were then held by the recipients as proof of the transaction. Even domestic electronic invoices are essentially scanned versions of paper documents, relying on unique numbers on the slips for authentication and duplicate checking. This invention, however, uses digital signatures to digitize the receipt content, then signs the digitized content, adding the holder's information to the signature. Furthermore, when the holder changes, the signature also updates with the new holder's information. Therefore, it cannot be guaranteed that a particular transaction receipt has only one valid holder.

[0003] Therefore, a design method for achieving unique electronic receipts is proposed. Summary of the Invention

[0004] The purpose of this invention is to provide a design method for achieving unique electronic receipts, so as to solve the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a design method for a unique electronic receipt, comprising the following steps: S1. Generate an electronic receipt based on the electronic receipt issuance request. The electronic receipt issuance request includes data associated with the generation of the electronic receipt. S2. Push a notification that the electronic receipt has been issued, the notification including the location where the electronic receipt was obtained; S2-1. Generate electronic data and push it to the designated person; S3. Uniqueness of Electronic Receipts: S3-1. The electronic receipt file must have space to store digital signatures, with at least two digital signatures. One is the signature of the initially created content, denoted by Sign1, which will never be modified. The other is the signature of both the newly added data and the original content after transmission, denoted by Sign2, which is modified during the transmission of the electronic receipt. S3-2. Use dedicated software to extract and display the contents of the electronic receipt. Each time the electronic receipt is extracted, the file content will automatically increment the read count by 1 and generate a new digital signature Sign2. This ensures that the signature changes after each read, preventing tampering or copying and reuse. S3-3. Dedicated software generates an asymmetric key pair for each electronic receipt. Each electronic receipt will have an independent and different asymmetric key pair, where the private key is abbreviated as R_PRI_KEY and the public key is abbreviated as R_PUB_KEY. S3-4. When an electronic receipt is to be sent to another person, the other party needs to send the R_PUB_KEY to the original holder first. The original holder then encrypts the electronic receipt with the R_PUB_KEY and sends it to the other party. The other party can decrypt the received data and sign and save it with their own R_PRI_KEY. The electronic receipt is then sent to the other party. S3-5. To ensure that the content of the electronic receipt cannot be modified by subsequent holders, the initial signature Sign1 is encrypted using the private key of the digital certification authority. The corresponding public key is R_PUB_KEY0, which is publicly available from the user. This public key can then be used to decrypt the receipt and verify whether the content has been modified. Furthermore, because subsequent read counts and a new signature content Sign2 are added, even the original creator of the electronic receipt cannot modify it.

[0006] Preferably, in step S1, the electronic receipt issuance request further includes the ID of the external application that sent the electronic receipt issuance request and an encrypted string, wherein the encrypted string is obtained by encrypting the data associated with generating the electronic receipt and the ID using a key from the external application that sent the electronic receipt issuance request. The method may further include: finding the corresponding key based on the ID in the electronic receipt issuance request; decrypting the encrypted string in the electronic receipt issuance request using the found key; and if the decrypted data matches the data associated with generating the electronic receipt and the ID, then generating an electronic receipt for the electronic receipt issuance request.

[0007] Preferably, generating an electronic receipt in response to an electronic receipt issuance request includes: verifying whether the electronic receipt issuance request meets predetermined conditions; if it meets the predetermined conditions, generating an electronic receipt.

[0008] Preferably, verifying whether the electronic receipt issuance request meets the predetermined conditions may include: determining whether the data associated with generating the electronic receipt is sufficient to generate the electronic receipt; if sufficient to generate the electronic receipt, determining whether the data used to generate the electronic receipt among the data associated with generating the electronic receipt meets the formal specifications; if the formal specifications are met, determining that the electronic receipt issuance request meets the predetermined conditions.

[0009] An application system for a design method to achieve unique electronic receipts, including external applications and an electronic receipt platform; The electronic receipt platform specifically includes a platform access layer, a platform service layer, a middleware layer, and an infrastructure layer.

[0010] Preferably, the platform access layer is the API open interface layer of the electronic receipt public service platform, responsible for providing standard Web Service API interfaces. For example... Figure 2 As shown, external applications such as Web, APP, client, and third-party platforms can all access the electronic receipt public service platform through the platform access layer.

[0011] Preferably, the platform service layer provides various service calls to the electronic receipt public service platform, including: identity authentication, electronic signature, receipt issuance, receipt storage, receipt download, receipt push, receipt query, receipt collection, receipt red-inking, template engine, batch export, and permission configuration. These services can realize basic services such as issuing electronic receipts (e.g., also including electronic receipt push, storage, download, and verification). The platform service layer also includes a portal application and an operation backend.

[0012] Preferably, the middleware layer includes a container management platform, message queues, distributed databases, etc., and the middleware layer is used to provide containerization, microservices, and load balancing for the electronic receipt public service platform.

[0013] Preferably, the infrastructure layer includes physical devices such as computing devices, storage devices, network devices, and security devices, which are used to provide computing, storage, and network resources for the electronic receipt public service platform.

[0014] Preferably, the middleware layer includes a container management platform, message queues, distributed databases, etc., and the middleware layer is used to provide containerization, microservices, and load balancing services for the electronic receipt public service platform.

[0015] Compared with the prior art, the beneficial effects of the present invention are: 1. This invention can back up an electronic transaction receipt before it is transferred. Once the transfer occurs, the backup cannot be transferred again, thus ensuring the uniqueness of the electronic receipt. 2. This invention, in response to electronic receipt issuance requests, automatically generates corresponding electronic receipts and pushes them to the recipients of the electronic receipts, based on pre-configured tax calculation strategies, thus realizing electronic receipt services. Specifically, it utilizes two message queues to implement the issuance and push of electronic receipts, allowing non-essential business logic to run asynchronously, thereby improving response speed. Attached Figure Description

[0016] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0017] Figure 1 This is a flowchart illustrating the uniqueness of the electronic receipt according to the present invention. Figure 2 This is an application system block diagram of a design method for achieving unique electronic receipts according to the present invention. specific

[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] Please see Figures 1 to 2 The present invention provides a technical solution: A design method for achieving unique electronic receipts includes the following steps: S1. Generate an electronic receipt based on the electronic receipt issuance request. The electronic receipt issuance request includes data associated with the generation of the electronic receipt. S2. Push a notification that the electronic receipt has been issued, the notification including the location where the electronic receipt was obtained; S2-1. Generate electronic data and push it to the designated person; S3. Uniqueness of Electronic Receipts: S3-1. The electronic receipt file must have space to store digital signatures, with at least two digital signatures. One is the signature of the initially created content, denoted by Sign1, which will never be modified. The other is the signature of both the newly added data and the original content after transmission, denoted by Sign2, which is modified during the transmission of the electronic receipt. S3-2. Use dedicated software to extract and display the contents of the electronic receipt. Each time the electronic receipt is extracted, the file content will automatically increment the read count by 1 and generate a new digital signature Sign2. This ensures that the signature changes after each read, preventing tampering or copying and reuse. S3-3. Dedicated software generates an asymmetric key pair for each electronic receipt. Each electronic receipt will have an independent and different asymmetric key pair, where the private key is abbreviated as R_PRI_KEY and the public key is abbreviated as R_PUB_KEY. S3-4. When an electronic receipt is to be sent to another person, the other party needs to send the R_PUB_KEY to the original holder first. The original holder then encrypts the electronic receipt with the R_PUB_KEY and sends it to the other party. The other party can decrypt the received data and sign and save it with their own R_PRI_KEY. The electronic receipt is then sent to the other party. S3-5. To ensure that the content of the electronic receipt cannot be modified by subsequent holders, the initial signature Sign1 is encrypted using the private key of the digital certification authority. The corresponding public key is R_PUB_KEY0, which is publicly available from the user. This public key can then be used to decrypt the receipt and verify whether the content has been modified. Furthermore, because subsequent read counts and a new signature content Sign2 are added, even the original creator of the electronic receipt cannot modify it.

[0020] Specifically, in step S1, the electronic receipt issuance request further includes the ID of the external application that sent the electronic receipt issuance request and an encrypted string. The encrypted string is obtained by encrypting the data associated with generating the electronic receipt and the ID using a key from the external application that sent the electronic receipt issuance request. The method may further include: finding the corresponding key based on the ID in the electronic receipt issuance request; decrypting the encrypted string in the electronic receipt issuance request using the found key; and if the decrypted data matches the data associated with generating the electronic receipt and the ID, then generating an electronic receipt for the electronic receipt issuance request.

[0021] Specifically, generating an electronic receipt in response to an electronic receipt issuance request includes: verifying whether the electronic receipt issuance request meets predetermined conditions; if it meets the predetermined conditions, generating an electronic receipt.

[0022] Specifically, verifying whether the electronic receipt issuance request meets the predetermined conditions may include: determining whether the data associated with generating the electronic receipt is sufficient to generate the electronic receipt; if sufficient to generate the electronic receipt, determining whether the data used to generate the electronic receipt among the data associated with generating the electronic receipt meets the formal specifications; if the formal specifications are met, determining that the electronic receipt issuance request meets the predetermined conditions.

[0023] An application system for a design method to achieve unique electronic receipts, including external applications and an electronic receipt platform; The electronic receipt platform specifically includes a platform access layer, a platform service layer, a middleware layer, and an infrastructure layer.

[0024] Specifically, the platform access layer is the API open interface layer of the electronic receipt public service platform, responsible for providing standard Web Service API interfaces. For example... Figure 2 As shown, external applications such as Web, APP, client, and third-party platforms can all access the electronic receipt public service platform through the platform access layer.

[0025] Specifically, the platform service layer provides various service calls for the electronic receipt public service platform, including: identity authentication, electronic signature, receipt issuance, receipt storage, receipt download, receipt push, receipt query, receipt collection, receipt red-inking, template engine, batch export, and permission configuration. These services enable basic services such as issuing electronic receipts (e.g., pushing, storing, downloading, and verifying electronic receipts). The platform service layer also includes a portal application and an operations backend.

[0026] Specifically, the middleware layer includes a container management platform, message queues, distributed databases, etc., and is used to provide containerization, microservices, and load balancing for the electronic receipt public service platform.

[0027] Specifically, the infrastructure layer includes physical devices such as computing devices, storage devices, network devices, and security devices, which are used to provide computing, storage, and network resources for the electronic receipt public service platform.

[0028] Specifically, the middleware layer includes a container management platform, message queues, distributed databases, etc., and is used to provide containerization, microservices, and load balancing services for the electronic receipt public service platform.

[0029] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A design method for achieving unique electronic receipts, characterized in that: Includes the following steps: S1. Generate an electronic receipt based on the electronic receipt issuance request, which includes data associated with the generation of the electronic receipt; S2. Push a notification that the electronic receipt has been issued, the notification including the location where the electronic receipt was obtained; S2-1. Generate an electronic receipt and send it to the designated person; S3. Uniqueness of Electronic Receipts: S3-1. The electronic receipt file has space to store the digital signature, and there are at least two digital signatures. One is the digital signature of the initially created content, denoted by Sign1, which is never modified; the other is the digital signature of the newly added data content along with the original content, denoted by Sign2, which is modified during the transmission of the electronic receipt. S3-2. Use dedicated software to extract and display the contents of the electronic receipt. Each time the electronic receipt is extracted, the file content will automatically increment the read count by 1 and generate a new digital signature Sign2. This ensures that the digital signature changes after each read, preventing it from being tampered with or copied and reused. S3-3. Dedicated software generates an asymmetric key pair for each electronic receipt. Each electronic receipt has an independent and different asymmetric key pair, where the private key is abbreviated as R_PRI_KEY and the public key is abbreviated as R_PUB_KEY. S3-4. When an electronic receipt is to be sent to another person, the other party needs to send the R_PUB_KEY to the original holder first. The original holder encrypts the electronic receipt with the R_PUB_KEY and sends it to the other party. The other party decrypts the received data and signs and saves the electronic receipt with their own R_PRI_KEY. The electronic receipt is then sent to the other party. S3-5. To ensure that the content of the electronic receipt is not modified by subsequent holders, the initial digital signature Sign1 is encrypted with the private key of the digital certification authority. The corresponding public key is the R_PUB_KEY published by the user. This public key of the digital certification authority is used to decrypt the receipt and verify whether the content has been modified. Furthermore, because there are subsequent additions of read counts and a new digital signature Sign2, even the person who originally created the electronic receipt can no longer modify it.

Images