Receipt token processing program, computer, and receipt token processing method

Abstract

To make electronic receipts, which serve as proof of purchase of goods or services, easy and secure to handle. [Solution] A receipt token processing program enables a computer having a processor and memory to realize a payment information acquisition function that acquires payment information indicating the contents of the payment process, and a receipt token issuance function that issues an instruction to a smart contract to generate a receipt token that proves the contents of the payment based on the payment information.

Description

[Technical Field]

[0001] At least one embodiment of the present invention relates to a receipt token processing program, a computer, and a receipt token processing method. [Background technology]

[0002] Patent Document 1 describes an electronic receipt management server. The electronic receipt management server includes a management means for storing and managing electronic receipt information related to receipt information indicating transaction details of merchandise to be paid for in a first storage area. The electronic receipt management server includes a receiving means for receiving information including identification information of any of the electronic receipt information stored in the first storage area and a type of specific processing executed for the transaction indicated by the electronic receipt information of the identification information. The electronic receipt management server includes a stamp information management means for, when the receiving means receives the information, associating the identification information of the electronic receipt information with stamp information indicating the type of specific processing, and storing and managing the associated information in a second storage area provided separate from the first storage area. The electronic receipt management server includes an electronic receipt viewing enabling means for enabling an information processing device associated with a recipient code to view the electronic receipt information associated with the recipient code, and, if the stamp information is associated with the electronic receipt information to be viewed, outputting the stamp information together with the electronic receipt information to enable viewing. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2024-097960 Summary of the Invention [Problem to be solved by the invention]

[0004] When providing the user with in-app content purchased by the user by means of display or the like, conventional techniques have used an electronic receipt as proof of purchase.

[0005] Examples of conventional techniques that use electronic receipts as proof of purchase include the following.

[0006] A user logs in to an account on a user terminal and purchases a product. The payment system processes the payment for the product purchase and sends an electronic receipt indicating the payment result to the user terminal. The user terminal stores the received electronic receipt as local data.

[0007] When receiving a service related to a purchased product, the user launches an app on the user device. The app on the user device sends the electronic receipt stored as local data to the payment system and requests verification. The payment system verifies the electronic receipt and sends the verification result to the app on the user device. Based on the verification result, the app on the user device provides the user with the service by, for example, displaying appropriate content on the user device. If a refund or cancellation is made for the product purchase, the content of the electronic receipt will be changed, and the payment system will send the revised electronic receipt again to the app on the user device for re-verification.

[0008] The prior art of using electronic receipts as proof of purchase has the following problems.

[0009] Since electronic receipts are stored locally on the user's device, there is a risk of the receipts being tampered with.

[0010] When the payment system implementer and the app implementer are different, multiple steps are required to exchange electronic receipts, making the process complicated and difficult to implement. Also, if the verified electronic receipt is saved on the app's server and subsequent receipt verification is skipped in order to omit multiple steps, updates to the electronic receipt due to refunds or cancellations cannot be properly detected.

[0011] In the case of subscription-based auto-renewal payments, there is a mechanism for detecting renewals, and it is possible to handle this by calling a dedicated API to obtain the current subscription status, but because the API to be called differs depending on the purchase format, the app's processing flow becomes even more complicated, making it even more difficult to implement.

[0012] When a user uses an app on a different device or OS, purchase information cannot be transferred. To transfer purchase information, the app must prepare a server and implement a careful transfer process for electronic receipts.

[0013] Since a server must be prepared on the app side before the app is released and a system for centrally managing purchase information on the server side must be designed for each app, implementation is difficult unless the app developer has ample development resources and a development schedule.

[0014] An object of at least one embodiment of the present invention is to solve the above problem and provide a receipt token processing program, a computer, and a receipt token processing method for easily and safely handling electronic receipts that prove the purchase of goods or services. [Means for solving the problem]

[0015] From a non-limiting perspective, a receipt token processing program according to one embodiment of the present invention enables a computer having a processor and memory to realize a payment information acquisition function that acquires payment information indicating the content of the payment process, and a receipt token issuance function that issues an instruction to a smart contract to generate a receipt token that proves the content of the payment based on the payment information.

[0016] In a non-limiting aspect, a computer according to one embodiment of the present invention has a processor and memory, and the processor executes a payment information acquisition process in which payment information indicating the content of a payment process is acquired, and a receipt token issuance process in which, based on the payment information, an instruction is issued to a smart contract to generate a receipt token that proves the content of the payment.

[0017] From a non-limiting perspective, a receipt token processing method according to one embodiment of the present invention is a computer-based receipt token processing method, which includes a payment information acquisition process that acquires payment information indicating the content of the payment process, and a receipt token issuance process that issues an instruction to a smart contract to generate a receipt token that proves the content of the payment based on the payment information. [Effects of the Invention]

[0018] Each embodiment of the present application addresses one or more of the deficiencies. [Brief explanation of the drawings]

[0019] [Figure 1] FIG. 1 is a block diagram illustrating an example of the configuration of a receipt token processing system corresponding to at least one embodiment of the present invention. [Figure 2] FIG. 1 is a block diagram showing a configuration of a computer according to at least one embodiment of the present invention. [Figure 3] FIG. 10 is a sequence diagram showing an example of processing of a receipt token processing system corresponding to at least one of the embodiments of the present invention. [Figure 4] FIG. 10 is a sequence diagram showing an example of processing of a receipt token processing system corresponding to at least one of the embodiments of the present invention. [Figure 5] FIG. 10 is a sequence diagram showing an example of processing of a receipt token processing system corresponding to at least one of the embodiments of the present invention. [Figure 6] FIG. 10 is a sequence diagram showing an example of processing of a receipt token processing system corresponding to at least one of the embodiments of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0020] Hereinafter, examples of embodiments of the present invention will be described with reference to the drawings. Note that the various components in the examples of the embodiments described below can be combined as appropriate to the extent that no inconsistencies or the like arise. Furthermore, content described as an example of one embodiment may be omitted in other embodiments. Furthermore, the content of operations and processes unrelated to the characteristic parts of each embodiment may be omitted. Furthermore, the order of various processes constituting the various flows and sequences described below may be in any order to the extent that no inconsistencies or the like arise in the processing content.

[0021] FIG. 1 is a block diagram showing an example of the configuration of a receipt token processing system 100 corresponding to at least one embodiment of the present invention. The receipt token processing system 100 comprises a server 10 and a user terminal 20 used by a user of the receipt token processing system 100. User terminals 20A, 20B, and 20C are each an example of a user terminal 20. The configuration of the receipt token processing system 100 is not limited to this. For example, the receipt token processing system 100 may be configured so that multiple users use a single user terminal. The receipt token processing system 100 may also comprise multiple servers. The user terminal 20 may perform the functions of the server 10.

[0022] The server 10 and the user terminal 20 are examples of computers. The server 10 and the user terminal 20 are each communicatively connected to a communication network 30 such as the Internet. The connection between the communication network 30 and the server 10 and the connection between the communication network 30 and the user terminal 20 may be a wired connection or a wireless connection. For example, the user terminal 20 may be connected to the communication network 30 by performing data communication with a base station managed by a telecommunications carrier via a wireless communication line.

[0023] The receipt token processing system 100 includes a server 10 and a user terminal 20, thereby realizing various functions for executing various processes in response to user operations.

[0024] The server 10 may incorporate a part or all of a payment system (described below). Alternatively, a part or all of the payment system may be implemented externally to the server 10, and the server 10 may be communicatively connected to a part or all of the externally implemented payment system. Hereinafter, the explanation will be given assuming that the server 10 implements a payment system. The server 10 includes a processor 11, a memory 12, and a storage device 13. The processor 11 is, for example, a central processing unit such as a CPU (Central Processing Unit) that performs various calculations and control. Furthermore, if the server 10 includes a GPU (Graphics Processing Unit), some of the various calculations and control may be performed by the GPU. The server 10 uses the data read into the memory 12 to execute various information processing operations using the processor 11, and stores the obtained processing results in the storage device 13 as necessary.

[0025] The storage device 13 functions as a storage medium for storing various types of information. The configuration of the storage device 13 is not particularly limited. Examples of hardware resources that make up the storage device 13 include, but are not limited to, HDDs and SSDs. However, the storage device that stores various types of information only needs to have a storage area accessible by the server 10, and may be configured to have, for example, a dedicated storage area outside the server 10.

[0026] The user terminal 20 is managed by a user. Examples of the user terminal 20 include a mobile phone terminal, a smartphone, a PDA (Personal Digital Assistant), a personal computer, a tablet, a stationary game device, a portable game device, etc. The user terminal 20 may be VR goggles, AR glasses, smart glasses, AR contacts, or other wearable devices that can be operated by the user.

[0027] The user terminal 20 is equipped with hardware and software for connecting to the communication network 30 and performing various processes by communicating with the server 10. Each of the multiple user terminals 20 may be configured to be able to communicate directly with each other (peer-to-peer communication) without going through the server 10.

[0028] The user terminal 20 may have a built-in display device. The display device may also be connected to the user terminal 20 wirelessly or via a wire. Note that the display device is an extremely common configuration and is therefore not shown here. The display device is an example of an output device. When a user performs various information processing using the user terminal 20, a screen required for the information processing (information processing screen) is displayed as an image by the display device, and the user recognizes this image. The information processing screen is displayed, for example, on a display which is an example of a display device provided in the user terminal, or on a display which is an example of a display device connected to the user terminal.

[0029] The user terminal 20 includes a processor 21, a memory 22, and a storage device 23. The processor 21 is, for example, a central processing unit such as a CPU (Central Processing Unit) that performs various calculations and control. Furthermore, if the user terminal 20 includes a GPU (Graphics Processing Unit), some of the various calculations and control may be performed by the GPU. The user terminal 20 uses the data read into the memory 22 to execute various information processing in the processor 21, and stores the obtained processing results in the storage device 23 as necessary. The storage device 23 functions as a storage medium that stores various information.

[0030] The user terminal 20 may have a built-in input device. The input device may also be connected to the user terminal 20 wirelessly or via a wire. The input device accepts operational inputs from the user. In response to the operational inputs from the user, a processor provided in the server 10 or a processor provided in the user terminal 20 executes various control processes. Examples of input devices include touch panel screens provided on smartphones, tablets, etc., keyboards, mice, game pads, joysticks, and other controllers.

[0031] Additionally, the user terminal 20 may be equipped with other output devices such as a speaker, etc. The other output devices output sounds, vibrations, and various other types of information to the user.

[0032] In this embodiment, the communication network 30 includes a blockchain network 60. The blockchain network 60 is constructed by a plurality of nodes such as computers. As examples of the plurality of nodes, FIG. 1 shows nodes 6a, 6b, 6c, and 6d, each of which is a computer. These are merely examples, and the number of nodes does not have to be four. Note that the blockchain network 60 may be constructed as a network separate from the illustrated communication network 30.

[0033] A plurality of nodes 6a to 6d are typically interconnected in a peer-to-peer manner to form a blockchain network 60. A distributed ledger is stored in a storage device provided in each node. The server 10 or the user terminal 20 may be communicatively connected to the blockchain network 60. The server 10 or the user terminal 20 may function as a node included in the blockchain network 60.

[0034] FIG. 2 is a block diagram showing the configuration of a computer according to at least one embodiment of the present invention.

[0035] In this example, the computer 50 will be described as the user terminal 20 in Fig. 1. However, the computer 50 may be the server 10 in Fig. 1 or another computer.

[0036] The computer 50 comprises a payment information acquisition unit 501, a receipt token issuance unit 502, a receipt token update unit 503, a receipt token fixation unit 504, and a receipt token verification unit 505. The processor of the computer 50 references a receipt token processing program stored in the storage device and executes the program to functionally realize the payment information acquisition unit 501, the receipt token issuance unit 502, the receipt token update unit 503, the receipt token fixation unit 504, and the receipt token verification unit 505.

[0037] The payment information acquisition unit 501 has a function to acquire payment information indicating the details of the payment process. The payment information acquisition unit 501 has a function to acquire cancellation information indicating the cancellation of the payment. The receipt token issuance unit 502 has a function to issue an instruction to the smart contract to generate a receipt token that proves the details of the payment based on the payment information. The receipt token update unit 503 has a function to issue an instruction to the smart contract to update an issued receipt token based on the cancellation information. The receipt token fixation unit 504 has a function to issue an instruction to the smart contract to fix the receipt token. The receipt token verification unit 505 has a function to issue an instruction to verify the receipt token to the smart contract.

[0038] The payment process refers to, for example, the payment process when a user purchases a product or service. Payment methods in the payment process include credit card payment and payment methods using points, but other payment methods are also possible.

[0039] The payment information is information that indicates the details of the payment process. For example, the payment information includes the purchase date and time, the purchaser's identifier, the identifier of the purchased product or service, the payment amount, the payment method, etc. The payment information may also include other information.

[0040] The payment details may be details identified from the payment information described above. Examples of payment details include an identifier that identifies the user, the purchase date and time, the payment amount, and the payment method. A receipt token that proves the payment details typically refers to a non-fungible token (NFT). However, a receipt token may also be another type of token that can be linked to an object. The token includes information that can identify the payment details or information that can access the payment details. For example, the payment information may be embedded in the token by encryption, or location information such as a URL for accessing the payment information may be embedded in the token.

[0041] The smart contract implements a token generation method that generates a receipt token on the blockchain when the smart contract is called by specifying parameters. The receipt token issuing unit 502 specifies parameters based on payment information and calls the token generation method.

[0042] A payment cancellation occurs, for example, when a user who has purchased a product or service cancels the purchase. The payment system receives a purchase cancellation request from the user terminal 20 and performs payment cancellation processing. The payment cancellation processing is similar to that of conventional payment systems, so a detailed explanation will be omitted. Cancellation information is information that indicates the content of the payment cancellation. Cancellation information includes the date and time of cancellation, the identifier of the person who canceled (the purchaser), the identifier of the product or service to be canceled, the payment amount, the payment method, etc. If an identifier that can uniquely identify the transaction, such as a transaction number, is assigned when the payment processing is performed, the cancellation information may also include that identifier.

[0043] If a transaction is canceled, the receipt token, which is proof of purchase, also needs to be updated. Therefore, the receipt token update unit 503 issues an instruction to the smart contract to update the issued receipt token based on the cancellation information. The smart contract implements a method that, when called, updates the contents of the receipt token based on specified parameters.

[0044] Token locking is also known as SBT. Since SBT itself is a conventional technology in the field of token handling, a detailed explanation is omitted. The smart contract implements a method that, when called, locks the receipt token based on the specified parameters.

[0045] The predetermined process requiring receipt token verification may be, for example, a process of outputting content related to a product purchased by a user, or a process of providing a service purchased by a user via a user terminal. Outputting content means, for example, displaying content such as an image or video on a display device, or outputting audio. Other processes that provide some value to a user on the condition that payment has been made correctly fall under the predetermined process. A method is implemented in the smart contract that, when called, verifies the receipt token based on specified parameters.

[0046] (Issuing receipt token) Next, a program execution process according to an embodiment of the present invention will be described. Fig. 3 is a sequence diagram showing an example of a process performed by a receipt token processing system according to at least one embodiment of the present invention.

[0047] In the processing examples shown in FIGS. 3 to 6, a first application is installed in the user terminal 20. The first application is a web application that enables the user to purchase products. An API for executing payment processing is implemented in the first application. The first application may or may not communicate with a payment system. The first application may or may not communicate with the server 10. The server 10 may or may not communicate with the payment system. In addition, a database (hereinafter referred to as DB) for saving account receipts, which will be described later, is stored in the storage device 23 of the user terminal 20. The DB may be stored in a storage device accessible from the user terminal 20 via a communication line.

[0048] In the processing examples shown in FIGS. 3 to 6, the product is in-app content that can be used in the second app. For example, still images, videos, and audio correspond to in-app content. The second app is a partner app that is affiliated with the first app. The second app may be the same as the first app. The second app may be installed on the user terminal 20. The second app may be installed on a computer other than the user terminal 20.

[0049] In the processing example shown in FIGS. 3 to 6, a payment system is implemented in the server 10.

[0050] The user purchases in-app content via the user terminal 20 (St101).

[0051] The user terminal 20 creates a payment order and transmits it to the server 10 (St102). A payment system is implemented in the server 10. The server 10 executes payment processing (St103).

[0052] After the payment process is completed, the server 10 issues a new account receipt and sends it to the user terminal 20 (St104). The account receipt refers to the payment information described above. The payment information acquisition unit 501 acquires the account receipt, which is the payment information, and saves the record of the account receipt in the DB (St105).

[0053] The receipt token issuing unit 502 issues an instruction to the smart contract 2 to generate a receipt token that certifies the details of the payment, specifying generation parameters based on the account receipt (St106). In other words, the receipt token issuing unit 502 calls the token generation method of the smart contract 2.

[0054] The smart contract 2 executes the token generation method (St107). As a result, a receipt token is generated and stored in the blockchain 3 (St108).

[0055] (Refresh receipt token) FIG. 4 is a sequence diagram showing an example of processing of a receipt token processing system corresponding to at least one embodiment of the present invention.

[0056] The user requests a refund and cancellation of the purchased content via the user terminal 20 (St201).

[0057] The user terminal 20 searches the DB for and acquires the account receipt corresponding to the request for refund and cancellation (St202).

[0058] The user terminal 20 transmits a request to amend the settlement order to the server 10 (St203). The server 10 executes the refund / cancellation process (St204). Note that the refund / cancellation process is a general process, so a detailed explanation will be omitted.

[0059] The server 10 updates the content of the issued account receipt to reflect the details of the payment cancellation, and transmits an updated account receipt to the user terminal 20. The payment information acquisition unit 501 acquires the updated account receipt (Step 205). The updated account receipt corresponds to cancellation information indicating the details of the payment cancellation.

[0060] The user terminal 20 updates the account receipt stored in the DB based on the cancellation information included in the acquired updated account receipt (St206).

[0061] The receipt token update unit 503 issues an instruction to the smart contract 2 to update the issued receipt token based on the cancellation information included in the acquired update account receipt (Step 207). That is, the receipt token update unit 503 specifies the update parameters identified based on the cancellation information and calls the token update method of the smart contract 2.

[0062] Smart contract 2 executes the token update method (Step St208). As a result, the receipt token is updated in the blockchain and the updated information is saved (Step St209).

[0063] (Receipt token fixation) FIG. 5 is a sequence diagram showing an example of processing of a receipt token processing system corresponding to at least one embodiment of the present invention.

[0064] In this example, a case will be described in which the fixing process is performed by the user terminal 20. However, the fixing process may be performed by the server 10 instead of the user terminal 20.

[0065] A program for executing jobs that are executed periodically, such as weekly processing or monthly processing, is installed in the user terminal 20. The program for executing the jobs that are executed periodically may be installed in the user terminal 20 separately from the first application, or may be incorporated into the first application.

[0066] The user terminal 20 extracts and acquires account receipts that satisfy a predetermined condition from the DB (Step St301). The predetermined condition may be, for example, an account receipt that has passed a predetermined renewal deadline. The predetermined condition may also be that the user has issued a fixation instruction to the user terminal 20. The predetermined condition may also be a condition other than these. In this example, the explanation will be given assuming that the predetermined condition is an account receipt that has passed a predetermined renewal deadline.

[0067] The receipt token fixation unit 504 issues an instruction to fix the receipt token to the smart contract 2 (St302). That is, the receipt token fixation unit 504 specifies fixation parameters required for fixation and calls the fixation method of the smart contract 2. The fixation parameters include, for example, identification information that identifies the receipt token.

[0068] The smart contract 2 executes the token fixation method (St303). The blockchain 3 approves and stores the fixation result (St304) and sends information indicating the fixation result to the smart contract 2 (St305). The smart contract 2 sends information indicating the fixation execution result to the user terminal 20 (St306).

[0069] The user terminal 20 stores the information of the account receipt corresponding to the fixed receipt token in the DB (Step St307).

[0070] (Utilizing receipt tokens) FIG. 6 is a sequence diagram showing an example of processing of a receipt token processing system corresponding to at least one embodiment of the present invention.

[0071] In this example, the second app is installed on the user terminal 20 together with the first app. The second app is a partner app with billable content. The second app may or may not be equipped with an API for communicating with the payment system. Furthermore, at the stage of utilizing the receipt token, the storage device 23 of the user terminal 20 does not need to store a DB for saving account receipts. This is because, in this embodiment, the receipt token is stored in the blockchain 3 and can be used as proof of purchase in place of a conventional electronic receipt.

[0072] The user requests the user terminal 20 to use in-app content (Step St401). Use here may refer to displaying the in-app content. Use of in-app content may refer to any action related to the content, such as acquiring, displaying, using, consuming, saving, lending, borrowing, transferring, exchanging, sharing, or making the content private. Requesting use may be an explicit action from the user's perspective to use the content, such as tapping a button to acquire or display the content. Requesting use may also be an implicit action from the user's perspective to use the content, such as launching the app or logging in to a user account.

[0073] The user terminal 20 checks the access rights of the user account (St402). The process of a user logging in to a user account and the process of checking the access rights of a user account are conventional techniques, so a detailed description thereof will be omitted.

[0074] If the access rights of the user account are successfully confirmed, the receipt token is directly verified as follows: The receipt token verification unit 505 specifies search parameters and searches for receipt tokens stored in the blockchain (St403). The receipt token verification unit 505 obtains the search results for the receipt token from the blockchain 3 (St404). The receipt token verification unit 505 verifies the receipt token locally (St405). Note that a verification algorithm from the prior art may be used as the local verification algorithm.

[0075] If the appropriate receipt token cannot be obtained in step St404, or if the local verification in step St405 fails, the user terminal 20 determines that the verification has failed. In this case, the requested in-app content is not provided to the user.

[0076] If the direct verification of the receipt token is successful, verification is performed via the smart contract. The receipt token verification unit 505 issues a verification instruction for the receipt token to smart contract 2 (Step 406). That is, the receipt token verification unit 505 specifies the necessary account parameters and calls the token verification method of smart contract 2. The necessary account parameters include, for example, the identification information of the receipt token to be verified and an identifier that identifies the user.

[0077] The smart contract 2 executes the receipt token verification method on the blockchain 3 (St407). The blockchain 3 approves and stores the verification result (St408). The blockchain 3 sends information indicating the verification result to the smart contract 2 (St409). The smart contract 2 sends information indicating the verification execution result to the receipt token verification unit 505 (St410). The information indicating the verification result may be numerical information, for example, where 0 indicates successful verification and 1 indicates unsuccessful verification. The information indicating the verification result may also be other types of information, such as Boolean information that takes the value TRUE or FALSE.

[0078] Based on the information indicating the result of the verification, the user terminal 20 notifies the second application of information indicating the confirmed access right (St411).

[0079] If the information indicating the confirmed access right includes information indicating that the access right is granted due to successful verification, the second application on the user terminal 20 provides the in-application content to the user (St412). Note that if the information indicating the confirmed access right includes information indicating that the access right is not granted due to unsuccessful verification, the second application does not provide the in-application content to the user.

[0080] In the above, the user terminal 20 performs the process of calling the method in the smart contract 2. However, the server 10 may perform the process of calling the method in the smart contract 2. The server 10 simply acquires the necessary information from the user terminal 20 and specifies parameters to be passed to the smart contract 2 based on the acquired information.

[0081] (What to do when automatic subscription renewal fails) With subscriptions, the service contract period is automatically renewed, and payments are made automatically on a regular basis, such as once a month. This regular payment, or automatic renewal, can sometimes fail for some reason. For example, if credit card payment is specified as the payment method, the credit card's available credit for the current month may be insufficient, or the credit card may have expired. Below is an example of what to do when automatic renewal fails.

[0082] If the automatic renewal payment process fails in the payment system, the payment system may or may not issue an account receipt, and may or may not store the account receipt in a database or blockchain.

[0083] If the user executes a re-payment process or modifies the payment information via the user terminal 20, the payment system executes a re-payment process. If this re-payment process is successful, the payment system issues a new account record with an automatic update. The process after issuing the new account record is the same as the process from step St105 onwards in Figure 3, so a detailed description will be omitted.

[0084] As described above, in an embodiment of the present disclosure, payment information is tokenized on a blockchain. Then, proof of purchase is based on the token. Therefore, there is no need to issue a traditional electronic receipt for proof of purchase. This provides the following advantages:

[0085] (Simplifying proof of purchase) Proof of purchase can be achieved without the direct transmission and reception of an electronic receipt and / or a verification process by a payment processor.

[0086] After purchasing a product or service, the electronic receipt is tokenized on the blockchain, eliminating the need to send the electronic receipt to a user device or the app vendor's program. The token is used as proof of purchase, and the app vendor's program (e.g., the second app) simply verifies the token on the blockchain.

[0087] Even if there are changes to the contents of the electronic receipt due to refunds or cancellations, the changes will be reflected on the blockchain.

[0088] (Improved data security) Because proof of purchase is tokenized on the blockchain, measures against the loss or tampering of electronic receipt data are strengthened.

[0089] (Multi-device and multi-platform compatible) Account purchase information is centrally managed on the blockchain, and is not restricted by devices or platforms.

[0090] (Possibility of secondary use) Using a public chain as a storage destination for receipt tokens would provide permanence and openness, allowing for secondary use of receipts. For example, it would be possible for purchasers of content from a discontinued app to receive preferential treatment in reissues or related apps.

[0091] As described above, each embodiment of the present application solves one or more deficiencies. Note that the effects of each embodiment are non-limiting effects or examples of effects.

[0092] In each of the above-described embodiments, the user terminal 20 and the server 10 execute the above-described various processes in accordance with various control programs (e.g., receipt token processing program) stored in their own storage devices. Also, other computers, not limited to the user terminal 20 and the server 10, may execute the above-described various processes in accordance with various control programs (e.g., receipt token processing program) stored in their own storage devices.

[0093] Furthermore, the configuration of the receipt token processing system 100 is not limited to the configuration described as an example of the embodiment above. For example, the server may execute some or all of the processes described as processes executed by the user terminal, or the user terminal may execute some or all of the processes described as processes executed by the server. Also, the user terminal may be configured to have some or all of the memory unit (memory device) that the server has. In other words, the receipt token processing system 100 may be configured so that some or all of the functions of either the user terminal or the server are provided in the other.

[0094] Furthermore, the program may be configured to cause a part or all of the functions described as examples of each of the above-mentioned embodiments to be realized by a single device that does not include a communication network.

[0095] [Note] The above-described embodiments have been described so that at least the following invention can be implemented by a person having ordinary skill in the art to which the invention pertains.

[0096] [1] A computer having a processor and a memory, a payment information acquisition function that acquires payment information indicating the content of the payment process; A receipt token processing program that realizes a receipt token issuance function that issues an instruction to a smart contract to generate a receipt token that proves the content of the payment based on the payment information.

[0097] According to the receipt token processing program described above, electronic receipts proving the purchase of goods or services can be handled easily and securely.

[0098] [2] The payment information acquisition function acquires cancellation information indicating the details of the payment cancellation, Further realizing a receipt token update function, which issues an instruction to a smart contract to update the issued receipt token based on the cancellation information; The receipt token processing program described in [1]. This ensures that the receipt token content is correctly updated even if the user cancels their purchase.

[0099] [3] the processor, Further implementation of the receipt token fixing function by issuing an instruction to the smart contract to fix the aforementioned receipt token. The receipt token processing program described in [1]. This allows receipt tokens to be fixed when certain conditions are met, such as a certain period of time having passed since the purchase.

[0100] [4] Verification of the receipt token is required to perform the prescribed process. Further implementation of verification functionality, which involves issuing verification instructions for the aforementioned receipt token to a smart contract. The receipt token processing program described in [1]. This allows the receipt token, which serves as proof of purchase, to be verified, and only if the verification result is satisfactory, a predetermined process can be carried out to provide the product or service to the user.

[0101] [5] a processor and a memory, the processor: a payment information acquisition process for acquiring payment information indicating the content of the payment process; A receipt token issuing process that issues an instruction to a smart contract to generate a receipt token that certifies the content of the payment based on the payment information. Run, computer.

[0102] The above computer allows for easy and safe handling of electronic receipts that prove the purchase of goods or services.

[0103] [6] A computer-implemented method for processing receipt tokens, comprising: a payment information acquisition process for acquiring payment information indicating the content of the payment process; and a receipt token issuing process for issuing an instruction to a smart contract to generate a receipt token that certifies the content of the payment based on the payment information. Receipt token processing method.

[0104] The receipt token processing method described above allows for easy and secure handling of electronic receipts that prove the purchase of goods or services. [Industrial Applicability]

[0105] According to one embodiment of the present invention, a receipt token processing program, a computer, and a receipt token processing method are useful for easily and safely handling electronic receipts that prove the purchase of goods or services. [Explanation of symbols]

[0106] 2. Smart Contracts 3. Blockchain 60 Blockchain Networks Nodes 6a to 6d 10 Servers 11 processors 12 Memory 13 Storage device 20, 20A, 20B User terminal 21 processors 22 Memory 23 Storage device 30 Communication Network 100 Receipt Token Processing System 501 Payment Information Acquisition Department 502 Receipt Token Issuance Department 503 Receipt Token Updater 504 Receipt Token Fixation Unit 505 Receipt Token Validation Unit

Claims

1. A computer having a processor and a memory, a payment information acquisition function that acquires payment information indicating the content of the payment process; A receipt token issuing function that issues an instruction to a smart contract to generate a receipt token that certifies the content of the payment based on the payment information, A receipt token processing program that makes this possible.

2. The payment information acquisition function acquires cancellation information indicating the cancellation details of the payment, Further realizing a receipt token update function, which issues an instruction to a smart contract to update the issued receipt token based on the cancellation information; The receipt token processing program according to claim 1 .

3. the processor, issuing an instruction to a smart contract to freeze the receipt token, further realizing a receipt token freeze function; The receipt token processing program according to claim 1 .

4. The receipt token needs to be verified in order to execute a predetermined process; issuing a verification instruction for the receipt token to a smart contract, further realizing a verification function; The receipt token processing program according to claim 1 .

5. a processor and a memory, the processor: a payment information acquisition process for acquiring payment information indicating the content of the payment process; A receipt token issuing process that issues an instruction to a smart contract to generate a receipt token that certifies the content of the payment based on the payment information. Run, computer.

6. A computer-implemented method for processing receipt tokens, comprising: a payment information acquisition process for acquiring payment information indicating the content of the payment process; and a receipt token issuing process for issuing an instruction to a smart contract to generate a receipt token that certifies the content of the payment based on the payment information. Receipt token processing method.

Images