Fund information recording device, fund information recording method, and fund information recording program

Abstract

[Problem] To provide a fund information recording device that makes it possible to ascertain a flow of a fund provided by a fund provider. [Solution] A fund information recording device 30 records, on a block chain 300, a token corresponding to a fund received as an electronic ticket of a providing source. When provision of an electronic ticket is requested from a user, services for which the electronic ticket can be provided to the user are extracted, and a list of available services is presented to the user. When one service is selected by the user, stores available to the user are extracted and a list of available stores is presented to the user. When one store is selected by the user, an electronic ticket usable in the store is provided. The fund information recording device 30 records, on the block chain 300, information on the user to whom the electronic ticket is provided, in association with a token corresponding to the electronic ticket.

Description

Fund Information Recording Device, Fund Information Recording Method, and Fund Information Recording Program

[0001] The present invention relates to a fund information recording device, a fund information recording method, and a fund information recording program.

[0002] A donation is an act of gratuitously providing money, goods, etc. according to one's own will, and donations are carried out in various forms. For example, a children's cafeteria is an effort to provide meals for poor families and children who eat alone operated by donations, and plays a major role in realizing a symbiotic society.

[0003] In relation to this, Patent Document 1 below discloses a technique for gratuitously providing a user with a meal at a pre-registered restaurant using the funds of a third party. In the technique of Patent Document 1, by having the user display a predetermined screen on a mobile terminal such as a smartphone, it becomes possible to have a free meal at the visited restaurant. According to this technique, it is possible to provide a free meal for children at a restaurant registered as a children's cafeteria.

[0004] Japanese Patent Application Laid-Open No. 2021-174248

[0005] As described above, by making a donation, it is possible to support the operation of a children's cafeteria and contribute to society. However, there is a problem that the fund provider who provided funds by donation cannot grasp how the funds provided by himself / herself were actually used. Therefore, for example, even if one wants to make a donation, one cannot know whether the funds donated by oneself actually reached the children who are in trouble, etc., so there is a situation where one feels不安 or hesitates about making a donation.

[0006] The present invention has been made in view of the above problems. Therefore, an object of the present invention is to provide a fund information recording device, a fund information recording method, and a fund information recording program for enabling the fund provider to grasp the flow of funds such as to whom the funds provided were distributed.

[0007] The above object of the present invention is achieved by the following means.

[0008] (1) Fund information recording device comprising: a storage unit that stores service information relating information about the provider of an electronic ticket and information about the recipients of the electronic ticket, and user information including information about the user; a fund receiving processing unit that receives deposits of funds from funders for the electronic ticket of the provider; a recording unit that records tokens corresponding to the funds received as electronic tickets by the fund receiving processing unit on a blockchain; an extraction unit that, when a request for provision of an electronic ticket by a user of a mobile terminal device is recognized, obtains information about the user of the mobile terminal device by referring to the user information, extracts the provider to which the user of the mobile terminal device corresponds to the recipient by referring to the information about the recipients of the service information; and a provision processing unit that performs the process of providing the electronic ticket of the provider extracted by the extraction unit to the user of the mobile terminal device, wherein the recording unit records information about the user of the mobile terminal device to whom the electronic ticket was provided on the blockchain in association with the token corresponding to the electronic ticket.

[0009] (2) The fund information recording device according to (1) above, wherein the recording unit records information about the fund provider who has deposited funds into the electronic ticket on the blockchain in association with the token corresponding to the electronic ticket.

[0010] (3) The financial information recording device according to (1) or (2) above, wherein the recording unit records information relating to the provider of the electronic ticket on the blockchain in association with the token corresponding to the electronic ticket.

[0011] (4) The financial information recording device according to (1) or (2) above, wherein the recording unit records information about the store where the electronic ticket was used on the blockchain in association with the token corresponding to the electronic ticket that was used.

[0012] (5) The fund information recording device according to (1) or (2) above, wherein the recording unit records on the blockchain information relating to the quantity of tokens corresponding to the amount used as an electronic ticket.

[0013] (6) The fund information recording device according to (1) or (2) above, further comprising an acquisition unit that acquires certificate information relating to a fund provision certificate proving that the fund provider has provided funds to the provider, and the recording unit records the certificate information on the blockchain by associating it with the token corresponding to the funds.

[0014] (7) The fund information recording device according to (1) or (2) above, further comprising an output unit that outputs information relating to the token recorded on the blockchain, information relating to the user of the mobile terminal device to which the electronic ticket corresponding to the token was provided, and information relating to the store where the electronic ticket was used, in an order that the information is viewable.

[0015] (8) The financial information recording device described in (1) or (2) above, wherein the service information includes information relating to the registered account of the recipient, and the user information includes information relating to the registered account of the user.

[0016] (9) The financial information recording device described in (1) or (2) above, wherein the service information includes information relating to at least one of the age and address of the recipient, and the user information includes information relating to at least one of the age and address of the user.

[0017] (10) If the extraction unit extracts multiple providers, the provision processing unit provides information about the multiple providers to the user of the mobile terminal device and prompts the user to select a provider, as described in (1) or (2) above, the fund information recording device.

[0018] (11) The financial information recording device according to (1) or (2) above, wherein the service information further associates information about stores where electronic tickets can be used with information about the provider, and the provision processing unit performs the process of providing the electronic tickets by referring to the information about the stores.

[0019] (12) The financial information recording device according to (1) or (2) above, wherein the service information further associates information regarding the usage of the electronic ticket with information regarding the provider, and the provision processing unit performs the process of providing the electronic ticket by referring to the information regarding the usage.

[0020] (13) The financial information recording device according to (1) or (2) above, wherein the service information further associates with the provider information information indicating the frequency or amount of use of the electronic ticket as information regarding the use of the electronic ticket, the information indicating the frequency or amount of use has a first value and a second value greater than the first value, the user information further includes information indicating a specific situation for the user, the provision processing unit performs a process of providing the electronic ticket by referring to the first value if the user of the mobile terminal device is not in the specific situation, and performs a process of providing the electronic ticket by referring to the second value if the user of the mobile terminal device is in the specific situation.

[0021] (14) The financial information recording device described in (1) or (2) above, wherein the user information is assigned identification information on a household basis for identifying the user.

[0022] (15) The fund information recording device according to (1) or (2) above, wherein when the electronic ticket is used, the provision processing unit presents an input screen for entering a message and prompts the user to enter a message, and when a message is entered, the recording unit records the message on the blockchain in association with the token corresponding to the electronic ticket.

[0023] (16) If the message is not entered, the fund information recording device described in (15) above performs a process to prohibit the user from using the electronic ticket again.

[0024] (17) If there are multiple providers, the fund receiving processing unit performs a process to present information about the multiple providers to the fund provider and prompt the fund provider to select a provider to whom the funds will be provided, as described in (1) or (2) above.

[0025] (18) The electronic ticket includes an electronic ticket usable at a restaurant, as described in (1) or (2) above, and is a financial information recording device.

[0026] (19) A method for recording fund information, comprising the steps of: (a) storing in a storage unit service information relating to a provider of electronic tickets and information relating to recipients of the electronic tickets, and user information including information relating to a user; (b) receiving a deposit of funds from a funder for the provider's electronic tickets; (c) recording on a blockchain a token corresponding to the funds received as electronic tickets in step (b); (d) when a request for provision of electronic tickets by a user of a mobile terminal device is recognized, obtaining information relating to the user of the mobile terminal device by referring to the user information, and extracting the provider to which the user of the mobile terminal device corresponds to the recipient by referring to the information relating to recipients of the service information; and (e) performing a process of providing the user of the mobile terminal device whose electronic ticket was extracted in step (d), wherein step (c) records on a blockchain information relating to the user of the mobile terminal device to whom the electronic ticket was provided, in association with the token corresponding to the electronic ticket.

[0027] (20) A fund information recording program comprising: (a) a procedure for storing in a storage unit service information relating to a provider of electronic tickets and a recipient of the electronic tickets, and user information including information about the user; (b) a procedure for receiving a deposit of funds from a funder for the provider's electronic tickets; (c) a procedure for recording on a blockchain a token corresponding to the funds received as electronic tickets in procedure (b); (d) a procedure for, when a request for electronic tickets from a user of a mobile terminal device is recognized, obtaining information about the user of the mobile terminal device by referring to the user information, and extracting the provider to which the user of the mobile terminal device corresponds to the recipient by referring to the recipient information of the service information; and (e) a procedure for providing the user of the mobile terminal device with the electronic tickets of the provider extracted in procedure (d), wherein procedure (c) causes a computer to execute a process for recording on a blockchain information relating to the user of the mobile terminal device to whom the electronic tickets were provided, in association with the token corresponding to the electronic tickets.

[0028] According to the fund information recording device according to an embodiment of the present invention, a token corresponding to the funds received as an electronic ticket from the provider is recorded on the blockchain. When a user requests an electronic ticket, first, services (supporting organizations) that can provide electronic tickets to the user are extracted, and a list of available services is presented to the user. If the user selects a service, stores that the user can use are extracted, and a list of available stores is presented to the user. If the user selects a store, an electronic ticket usable at that store is provided. Information about the user to whom the electronic ticket was provided is then recorded on the blockchain in association with the token corresponding to the electronic ticket. As a result, since information about the user to whom the electronic ticket was provided is recorded in association with the token corresponding to the electronic ticket, for example, a fund provider can understand who received the funds they provided and can track the flow of funds.

[0029] This is a diagram showing the schematic configuration of the fund information recording system. This is a block diagram showing the schematic configuration of a mobile terminal device. This is a block diagram showing the schematic configuration of a terminal device. This is a block diagram showing the schematic configuration of a server device. This is a diagram showing the contents of the storage unit of the server device. This is a diagram showing an example of service information. This is a diagram showing an example of store information. This is a diagram showing an example of user information. This is a sequence chart showing the procedure for providing electronic tickets. This is a diagram following Figure 9. This is a diagram showing an example of a store search screen. This is a diagram showing an example of a service list screen. This is a diagram showing an example of a store list screen. This is a diagram showing an example of a menu list screen. This is a diagram showing an example of an order confirmation screen. This is a diagram showing an example of a payment confirmation screen. This is a diagram showing an example of a message input screen. This is a diagram showing an example of a donation recipient list screen. This is a diagram showing an example of an image for accessing the donation deposit screen. This is a flowchart showing the procedure for receiving donations. This is a flowchart showing the procedure for recording. This is a flowchart showing the procedure for outputting. This is a diagram showing an example of a screen for checking the donation flow output in the output processing of Figure 22. This is a diagram showing an example of a screen for checking the donation flow output in the output processing of Figure 22. This is a diagram showing an example of a certificate output in the output processing of Figure 22. This is a diagram showing an example of a screen showing the certificate verification result. This is a conceptual diagram showing how the electronic ticket provision processing and fund information recording processing are executed.

[0030] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are merely illustrative, and various modifications are possible from such embodiments.

[0031] Figure 1 is a diagram illustrating the schematic configuration of a fund information recording system to which a fund information recording device according to one embodiment of the present invention is applied. In the following explanation, the case in which the fund information recording device records information regarding electronic tickets for meals will be used as an example, but electronic tickets are not limited to meals and can be used for various purposes. Furthermore, in the following explanation, the case in which a funder provides funds as a donation will be used as an example, but the fund information recording device is not limited to this in terms of the funders and forms of provision of funds, and can be applied to funds provided by various providers and in various forms of provision, such as taxes and political contributions.

[0032] The electronic tickets allow users 2a and 2b to receive meals free of charge at restaurants 1a and 1b by presenting them to the staff. The electronic tickets are provided independently by multiple support organizations 3a and 3b, including local governments such as prefectures and municipalities, NPOs, and volunteer groups. Support organizations 3a and 3b receive donations from donors (fund providers) 4a and 4b, which serve as the source of funds for the electronic tickets. Support organizations 3a and 3b pay the meal costs for users 2a and 2b to restaurants 1a and 1b on behalf of users 2a and 2b, based on the usage of the electronic tickets.

[0033] As shown in Figure 1, the fund information recording system comprises a plurality of mobile terminal devices 10a to 10c, a plurality of terminal devices 20a and 20b, and a server device 30. The mobile terminal devices 10a to 10c, terminal devices 20a and 20b, and the server device 30 are configured to communicate with each other via a network 40 such as the Internet.

[0034] Mobile terminal devices 10a to 10c are, for example, smartphones and are used by users 2a, 2b and donors 4a. Terminal devices 20a and 20b are, for example, PCs (Persipnal Computers) and are used by the system administrator 5 of the fund information recording system and donors 4b.

[0035] Note that the types and number of devices connected to network 40 are not limited to the example shown in Figure 1. Numerous mobile terminals and other terminal devices may be connected to network 40.

[0036] <Mobile Terminal Devices> Next, the configurations of mobile terminal devices 10a to 10c will be described with reference to Figure 2. Since mobile terminal devices 10a to 10c have similar configurations, mobile terminal device 10a will be used as a representative example in the following description.

[0037] Figure 2 is a block diagram illustrating the schematic configuration of the mobile terminal device 10a. As shown in Figure 2, the mobile terminal device 10a comprises a control unit 11, a storage unit 12, a communication unit 13, and an operation display unit 14, which are interconnected by a bus.

[0038] The control unit 11 is composed of a CPU (Central Processing Unit) and memory such as RAM (Random Access Memory) and ROM (Read Only Memory), and controls each of the above parts and performs various calculation processes according to the program.

[0039] The storage unit 12 is composed of an SSD (Solid State Drive) or HDD (Hard Disk Drive) and stores various programs and data.

[0040] The communication unit 13 is an interface for communicating with other devices, and various wired or wireless communication interfaces are used.

[0041] The operation display unit 14 is, for example, a touch panel display, which displays and inputs various types of information.

[0042] <Terminal Devices> Next, the configurations of terminal devices 20a and 20b will be described with reference to Figure 3. Since terminal devices 20a and 20b have similar configurations, terminal device 20a will be used as a representative example in the following description.

[0043] Figure 3 is a block diagram illustrating the schematic configuration of the terminal device 20a. As shown in Figure 3, the terminal device 20a comprises a control unit 21, a storage unit 22, a communication unit 23, a display unit 24, and an input unit 25, which are interconnected by a bus. Note that, to avoid repetition in the explanation, the parts of the terminal device 20a that have the same functions as those of the mobile terminal device 10a will not be described.

[0044] The display unit 24 is, for example, a liquid crystal display and displays various types of information.

[0045] The input unit 25 includes a keyboard, a numeric keypad, a mouse, etc., and accepts input of various types of information.

[0046] <Server Device> Next, referring to FIG. 4, the configuration of the server device 30 will be described. The server device 30 corresponds to the fund information recording device of the present invention.

[0047] FIG. 4 is a block diagram showing a schematic configuration of the server device 30. As shown in FIG. 4, the server device 30 includes a control unit 31, a storage unit 32, and a communication unit 33, which are interconnected by a bus. Note that since each of the above units of the server device 30 has the same functions as those of the above units of the portable terminal device 10a, redundant explanations will be omitted.

[0048] The storage unit 32 stores a blockchain 300 for recording and making the received fund flow browsable. Since the blockchain 300 can be configured by a known blockchain platform such as the XRP Ledger, detailed explanations will be omitted. Note that the blockchain 300 may be stored not in the storage unit 32 of the server device 30 but in another device that functions as a node of the blockchain 300. In this case, the server device 30 can record various types of information on the blockchain 300 or output the various types of information recorded on the blockchain 300 in a browsable manner by accessing another device. Also, devices such as the portable terminal device 10a and the terminal device 20a may acquire an account to access the blockchain 300, store the blockchain 300, or access another device that stores the blockchain 300.

[0049] Figure 5 shows the contents of the storage unit 32 of the server device 30. As shown in Figure 5, the storage unit 32 of the server device 30 stores service information 110, store information 120, and user information 130. Service information 110 is information about the rules for using electronic tickets for each support organization that provides electronic tickets. For example, the service information may include information about the registered account of the recipient. The service information may also include information about at least one of the recipient's age and address. Store information 120 is information about registered stores, and user information 130 is information about registered users. For example, the user information may include information about the user's registered account. The user information may also include information about at least one of the user's age and address. Details of service information 110, store information 120, and user information 130 will be described later.

[0050] Furthermore, the storage unit 32 of the server device 30 stores programs corresponding to the fund acceptance processing unit 210, the recording unit 220, the extraction unit 230, the provision processing unit 240, the acquisition unit 250, and the output unit 260.

[0051] The fund receiving processing unit 210 receives deposits of funds from funders into electronic tickets provided by each supporting organization (provider).

[0052] The recording unit 220 records tokens corresponding to the funds received as electronic tickets by the fund acceptance processing unit 210 onto the blockchain 300.

[0053] When the extraction unit 230 recognizes an electronic ticket provision request from users 2a and 2b, it refers to the service information 110 and extracts the support organizations (services) 3a and 3b that are providers of electronic tickets for which the users are eligible recipients of the electronic tickets.

[0054] The provision processing unit 240 performs the process of providing the electronic ticket of the provider (service) extracted by the extraction unit 230 to the user. The recording unit 220 records information about the user to whom the electronic ticket was provided, associating it with the token corresponding to the electronic ticket, on the blockchain 300.

[0055] The acquisition unit 250 acquires certificate information relating to a funding certificate that proves that a funder has provided funds to the provider (service). In this case, the recording unit 220 associates the certificate information with the token corresponding to the provided funds and records it on the blockchain 300.

[0056] The output unit 260 outputs information about tokens recorded on the blockchain 300, information about users to whom electronic tickets corresponding to those tokens were provided, and information about the stores where those electronic tickets were used, in an order that makes them viewable.

[0057] Furthermore, the recording unit 220 may record information about funders who have deposited funds into an electronic ticket on the blockchain, associating it with the token corresponding to the electronic ticket.

[0058] Furthermore, the recording unit 220 may record information regarding the provider of the electronic ticket on the blockchain 300 in association with the token corresponding to the electronic ticket.

[0059] Furthermore, the recording unit 220 may record information about the store where the electronic ticket was used on the blockchain 300, associating it with the token corresponding to the electronic ticket used.

[0060] Furthermore, the recording unit 220 may record information on the blockchain 300 regarding the quantity of tokens corresponding to the amount used as an electronic ticket.

[0061] Furthermore, if a message is entered by a user using an electronic ticket, the recording unit 220 may record the message on the blockchain 300 in association with the token corresponding to the electronic ticket.

[0062] The functions of each of the above-mentioned parts are achieved when the control unit 31 executes the corresponding program.

[0063] Furthermore, the mobile terminal devices 10a to 10c, terminal devices 20a and 20b, and server device 30 may have components other than those described above, and may not have some of the components described above. For example, the mobile terminal devices 10a to 10c may be equipped with a camera.

[0064] Next, referring to Figures 6 to 8, we will explain the service information 110, store information 120, and user information 130 in order.

[0065] Figure 6 shows an example of service information 110. Service information 110 is information regarding the rules for using electronic tickets, and is registered, for example, by the system administrator 5 through the terminal device 20a to the storage unit 32 of the server device 30.

[0066] As shown in Figure 6, the service information 110 includes service ID information 111, service name information 112, target age information 113, target address information 114, usage frequency information 115a, 115b, available amount information 116, available store information 117, ticket number information 118, and issued ticket number information 119.

[0067] Service ID information 111 is information for identifying the support organizations 3a and 3b that provide the electronic tickets, and service name information 112 is information indicating the name of the ticket provision service provided by support organizations 3a and 3b. Target age information 113 is information indicating the age of the recipients of the electronic tickets, and target address information 114 is information indicating the address (prefecture / city / town) of the recipients of the electronic tickets.

[0068] The usage frequency information 115a and 115b indicates the number of times a user can use an electronic ticket in a week, and includes first usage frequency information 115a and second usage frequency information 115b. First usage frequency information 115a indicates the number of times a user who is not receiving public assistance can use the ticket, and second usage frequency information 115b indicates the number of times a user who is receiving public assistance can use the ticket. Available amount information 116 indicates the amount of money (maximum amount) a user can spend on a single meal, and available store information 117 indicates restaurants where the electronic ticket can be used.

[0069] Ticket quantity information 118 indicates the number of electronic tickets that support organizations 3a and 3b can provide, and issued ticket quantity information 119 indicates the number of electronic tickets that have been issued. Ticket quantity information 118 is updated when donations are received, and issued ticket quantity information 119 is updated when electronic tickets are issued.

[0070] Figure 7 shows an example of store information 120. Store information 120 is information about registered stores and is registered, for example, by the system administrator 5 through the terminal device 20a to the storage unit 32 of the server device 30.

[0071] As shown in Figure 7, the store information 120 includes store ID information 121, store name information 122, location information 123, available time slot information 124, menu ID information 125, menu name information 126, menu price information 127, available number of servings information 128, and number of servings served information 129.

[0072] Store ID information 121 is information used to identify the restaurant, and store name information 122 is information indicating the name of the restaurant. Location information 123 is information indicating the location of the restaurant (prefecture and city / town). Availability time information 124 is information indicating the time period during which the restaurant can offer the menu for the electronic ticket (the time period during which users can use the electronic ticket).

[0073] Menu ID information 125 is information for identifying menus for which electronic tickets can be used, and menu name information 126 is information indicating the name of the menu. Menu price information 127 is information indicating the price of the menu.

[0074] The information on the number of meals that can be provided 128 indicates the number of meals that a restaurant can provide in a day using electronic tickets, and the information on the number of meals that have already been provided 129 indicates the number of meals that a restaurant has already provided in a day.

[0075] Figure 8 shows an example of user information 130. User information 130 is information about registered users and is registered, for example, by users 2a and 2b themselves through their mobile terminal devices 10a and 10b in the storage unit 32 of the server device 30.

[0076] As shown in Figure 8, user information 130 includes user ID information 131, name information 132, date of birth information 133, address information 134, and welfare assistance information 135.

[0077] User ID information 131 is information used to identify the user, and name information 132 is information indicating the user's name. Date of birth information 133 is information indicating the user's date of birth, and address information 134 is information indicating the user's address (prefecture and city / town). Public assistance information 135 is information indicating whether or not the user is receiving public assistance (not receiving: 0, receiving: 1). User ID information 131 is assigned on a household basis. In addition, information (not shown) indicating the electronic tickets used by the user in a week is stored in association with the user ID information 131 and the user's name information 132.

[0078] The information stored in the storage unit 32 of the server device 30 is not limited to the information described above. The storage unit 32 of the server device 30 may include, for example, information indicating the business hours and account number of a restaurant, information indicating the location and account number of a support organization providing electronic tickets, and information indicating the contact information of a user. Furthermore, the values ​​for ID information, etc., are not limited to the examples above, and any characters, numbers, or symbols may be used.

[0079] The operation of the fund information recording system will be explained below with reference to Figures 9 to 17. In the following explanation, the case where user 2a of the mobile terminal device 10a uses an electronic ticket will be used as an example.

[0080] Figures 9 and 10 are sequence charts showing the procedure for providing electronic tickets in a fund information recording system. The processing in the sequence chart is executed by the control units 11 and 31 of the mobile terminal device 10a or server device 30, according to a program stored in the storage units 12 and 32 of each device 10a and 30. The processing units in the sequence chart are divided according to the main processing content to facilitate understanding of each process, and the present invention is not limited by how the processing steps are classified.

[0081] First, the mobile terminal device 10a receives a store search instruction (step S1). More specifically, the mobile terminal device 10a displays a store search screen 310, as shown in Figure 11, on the operation display unit 14, and receives an instruction from the user 2a to search for stores where electronic tickets can be used. The store search screen 310 is provided to the mobile terminal device 10a from the server device 30 when a registered user 2a logs into the system.

[0082] Upon receiving a store search instruction, the mobile terminal device 10a transmits search instruction information to the server device 30 to instruct it to perform the store search (step S2).

[0083] Upon receiving the search instruction information, the server device 30 extracts services available to user 2a of the mobile terminal device 10a (step S3). More specifically, the server device 30 first refers to the user information 130 to recognize the age and address of user 2a of the mobile terminal device 10a. Then, the server device 30 refers to the target age information 113 and target address information 114 of the service information 110 to extract from among multiple services services for which user 2a is eligible to receive electronic tickets. At this time, the server device 30 refers to the service information 110 to exclude services for which the number of electronic tickets that can be issued is "0" and services for which the number of times user 2a has used electronic tickets exceeds the values ​​of the usage frequency information 115a and 115b from the available services.

[0084] The server device 30 then generates display information for listing the extracted services and transmits it to the mobile terminal device 10a (steps S4, S5).

[0085] Upon receiving the display information, the mobile terminal device 10a displays a service list screen 320, as shown in Figure 12, on the operation display unit 14, prompting the user 2a to select a service (support organization) to use (step S6). Figure 12 shows an example where two services are extracted as services for which user 2a is eligible to receive electronic tickets.

[0086] Then, the mobile terminal device 10a accepts the user 2a's selection of a service through the service list screen 320 (step S7). More specifically, the mobile terminal device 10a accepts the user 2a's selection of one service from among two services presented on the service list screen 320.

[0087] Upon receiving the service selection, the mobile terminal device 10a transmits information about the selected service (for example, service ID information) to the server device 30 (step S8).

[0088] Upon receiving information about the selected service, the server device 30 extracts available restaurants (step S9). More specifically, the server device 30 refers to the available restaurant information 117 in the service information 110 to extract restaurants that are available for the selected service. At this time, the server device 30 refers to the restaurant information 120 to exclude restaurants that are not open during the time period when electronic tickets can be used, or restaurants that have "0" meals available, from the list of available restaurants.

[0089] The server device 30 then generates display information for listing the extracted stores and transmits it to the mobile terminal device 10a (steps S10, S11).

[0090] Upon receiving the display information, the mobile terminal device 10a displays a store list screen 330, as shown in Figure 13, on the operation display unit 14, prompting the user 2a to select a store to use (step S12). Figure 13 shows an example where three stores are extracted as stores available to user 2a.

[0091] Then, the mobile terminal device 10a accepts the user 2a's selection of a store through the store list screen 330 (step S13). More specifically, the mobile terminal device 10a accepts the user 2a's selection of one store from among the three stores presented on the store list screen 330.

[0092] Upon receiving the store selection, the mobile terminal device 10a transmits information about the selected store (for example, store ID information) to the server device 30 (step S14). The user 2a then visits the selected store.

[0093] The server device 30, having received information about the selected store, extracts the available menus (step S15). More specifically, the server device 30 refers to the store information 120 and extracts the menus available at the restaurant selected by user 2a.

[0094] The server device 30 then generates display information for listing the extracted menus and transmits it to the mobile terminal device 10a (steps S16, S17).

[0095] Upon receiving the display information, the mobile terminal device 10a displays a menu list screen 340 on the operation display unit 14, as shown in Figure 14, prompting the user 2a to select a menu item (step S18). Figure 14 shows an example where the menu items available to user 2a are one dish menu item (children's set meal) and "specify price and use". "Specify price and use" will be explained later.

[0096] Then, the mobile terminal device 10a accepts the user 2a's selection of a menu through the menu list screen 340 (step S19). More specifically, the mobile terminal device 10a accepts the user 2a's selection of one menu from among two menus presented on the menu list screen 340. If there are two or more users corresponding to the user ID information (for example, if siblings are registered for one user ID information), user 2a selects their own name through a user selection screen (not shown) and then makes a menu selection.

[0097] Upon receiving the menu selection, the mobile terminal device 10a transmits information about the selected menu (for example, menu ID information) to the server device 30 (step S20).

[0098] The server device 30, having received information about the selected menu, generates display information for displaying the order confirmation screen and transmits it to the mobile terminal device 10a (steps S21, S22).

[0099] Upon receiving the display information, the mobile terminal device 10a displays an order confirmation screen 350 on the operation display unit 14, as shown in Figure 15 (step S23). The user 2a presents the order confirmation screen 350 as an electronic ticket to the store clerk at the store and presses (taps) the order confirmation button 351.

[0100] When the order confirmation button 351 is pressed, the mobile terminal device 10a accepts the order confirmation from the user 2a (step S24). Having accepted the order confirmation, the mobile terminal device 10a transmits information to the server device 30 indicating that the order has been confirmed (step S25).

[0101] Upon receiving information indicating that the order has been confirmed, the server device 30 generates display information for displaying the payment confirmation screen and transmits it to the mobile terminal device 10a (steps S26, S27). At this time, the server device 30 updates the service information 110, including the number of issued tickets 119, the store information 120, including the number of meals served 129, and information indicating the electronic tickets used by user 2a in the past week.

[0102] Upon receiving the display information, the mobile terminal device 10a displays a payment confirmation screen 360 on the operation display unit 14, as shown in Figure 16 (step S28). The user 2a then presents the payment confirmation screen 360 to the store clerk and presses the payment confirmation button 361.

[0103] When the payment confirmation button 361 is pressed, the mobile terminal device 10a accepts the payment confirmation by the user 2a (step S29). Having accepted the payment confirmation, the mobile terminal device 10a transmits information to the server device 30 indicating that the payment has been confirmed (step S30).

[0104] Upon receiving information indicating that payment has been confirmed, the server device 30 stores the payment information (step S31). More specifically, the server device 30 stores information about the restaurant where user 2a received the meal, the date and time the meal was received, and the name and price of the menu item received as payment information in the storage unit 32. Later, based on the payment information, the support organization that provided the electronic ticket pays the restaurant.

[0105] The server device 30 then generates display information for displaying the message input screen and transmits it to the mobile terminal device 10a (steps S32, S33).

[0106] Upon receiving the display information, the mobile terminal device 10a displays a message input screen 370, as shown in Figure 17, on the operation display unit 14, prompting the user 2a to enter a thank you message (step S34).

[0107] Then, the mobile terminal device 10a receives a message input from the user 2a through the message input screen 370 (step S35). Upon receiving the message input, the mobile terminal device 10a transmits information about the message to the server device 30 (step S36).

[0108] The server device 30, having received information about the message, publishes the message (step S37). More specifically, it publishes the message so that donors 4a and 4b, who have made donations to the support organization that provides the electronic tickets, can view the thank-you message from the user on their mobile terminal device 10c and terminal device 20b.

[0109] Furthermore, if a thank-you message is not entered, the server device 30 will prohibit user 2a from using the electronic ticket again until a thank-you message is entered. With this configuration, the thank-you message will be reliably entered by the user.

[0110] In the electronic ticket provision process described above, when an electronic ticket is used with a specified amount, the server device 30 refers to the available amount information 116 in the service information 110 and presents the user 2a with an amount input screen (not shown) with the available amount as the upper limit. Once the user 2a enters the amount to be used, the server device 30 issues an electronic ticket for that amount.

[0111] The process for receiving donations from donors 4a and 4b will be explained below with reference to Figures 18 and 19.

[0112] The server device 30 provides each support organization 3a, 3b with an input screen (not shown) for depositing donations into the support organization's account, and a URL (Uniform Resource Locator) for accessing the screen. Donors 4a, 4b can easily deposit donations into support organizations 3a, 3b by accessing the input screen from their mobile terminal device 10c or terminal device 20b.

[0113] In this case, the donor can select one support organization (service) to which they will donate their funds from among several support organizations (services) through a list of support organizations screen 400, such as the one shown in Figure 18. With this configuration, the donor can donate their funds to the support organization of their choice.

[0114] Furthermore, guidance to the above input screen may be provided, for example, by displaying a poster 500, as shown in Figure 19, inside a restaurant or other establishment. In this case, donors 4a and 4b can immediately access the input screen (URL) for depositing donations by reading a two-dimensional code image 510, such as a QR code (registered trademark), with the camera of their mobile terminal device.

[0115] The fund information recording process performed in the fund information recording system will be described below with reference to Figures 20 to 26.

[0116] Figure 20 is a flowchart showing the procedure for receiving donations. Figure 21 is a flowchart showing the procedure for recording. Figure 22 is a flowchart showing the procedure for outputting. Figures 23 and 24 are examples of screens for checking the donation flow output in the output process shown in Figure 22. Figure 25 is an example of a certificate output in the output process shown in Figure 22. Figure 26 is an example of a screen showing the certificate verification result.

[0117] First, let me explain how we process donations.

[0118] As shown in Figure 20, the server device 30 determines whether or not it has received a donation from a donor (step S101). Donations are accepted, for example, as deposits of funds into electronic tickets provided by each support organization (provider).

[0119] If the donation has not been accepted (step S101: NO), the server device 30 waits until the donation is accepted.

[0120] If a donation is accepted (Step S101: YES), the server device 30 issues a token corresponding to the funds received as an electronic ticket and records it on the blockchain 300 (Step S102). For example, if the server device receives 10,000 yen in funds, it records a token corresponding to 10,000 yen (for example, 10,000 tokens) on the blockchain 300. The server device 30 may also record information about the donor (fund provider) who deposited funds into the electronic ticket, associating it with the token corresponding to the electronic ticket on the blockchain 300. The server device 30 may also record information about the provider of the electronic ticket, associating it with the token corresponding to the electronic ticket on the blockchain 300. The server device 30 then terminates the donation acceptance process.

[0121] Next, we will explain the process of recording information regarding the use of electronic tickets.

[0122] As shown in Figure 21, the server device 30 determines whether or not the electronic ticket has been used (step S201). For example, if the electronic ticket is used by a user at a designated store, the server device 30 determines that the electronic ticket has been used. The server device 30 may also determine that the electronic ticket has been used even if the electronic ticket has not actually been used, for example, when the electronic ticket is distributed to the user.

[0123] If no electronic ticket is being used (step S201: NO), the server device 30 waits until an electronic ticket is being used.

[0124] If an electronic ticket is used (step S201: YES), the server device 30 records information regarding the use of the electronic ticket on the blockchain 300 in association with the corresponding token (step S202). For example, the server device 30 records information about the user to whom the electronic ticket corresponding to the token was provided, in association with the token, on the blockchain 300. The information about the user may be, for example, user ID information for identifying the user in the server device 30, or it may be an account (such as a wallet account) for the user to access the blockchain 300. The server device 30 may also record information about the store where the electronic ticket corresponding to the token was used, in association with the token corresponding to the used electronic ticket, on the blockchain 300. The server device 30 may also record information about the quantity of tokens corresponding to the amount used as an electronic ticket on the blockchain 300.

[0125] Next, we will explain the output processing for each method.

[0126] As shown in Figure 22, the server device 30 determines whether or not it has received a request to output various types of information (step S301). For example, a donor operates a terminal device 20a or the like to send an output request to the server device 30 in order to check various types of information about the funds they have donated. The output request includes information to identify the donor and information to identify each token corresponding to the funds provided by the donor, in order to specify the information to be output. The server device 30 receives the output request sent from the terminal device 20a.

[0127] If no output request has been received (step S301: NO), the server device 30 waits until an output request is received.

[0128] If an output request is received (step S301: YES), the server device 30 outputs various information recorded on the blockchain 300 in a viewable format (step S302). For example, the server device 30 outputs information relating to tokens corresponding to funds provided by donors, information relating to users to whom electronic tickets corresponding to those tokens were provided, and information relating to the stores where those electronic tickets were used, in a viewable format. For example, the server device 30 outputs various information recorded on the blockchain 300 in a viewable format by outputting screens as shown in Figures 23 and 24.

[0129] For example, in the screen shown in Figure 23, the input field at the top for searching accepts the donor's account address and individual transaction IDs related to the tokens. This displays a list of information about the corresponding tokens in a field labeled "Token Transaction". When the target information is selected from the list of tokens, a screen like Figure 24 is displayed. In the screen shown in Figure 24, the number of tokens is displayed along with which electronic ticket provider (supporting organization) the target token (electronic ticket) was distributed to which user and at which store it was used.

[0130] Furthermore, the server device 30 may acquire certificate information relating to a donation certificate (proof of funding) that proves a donor has made a donation to a support organization, associate the certificate information with the token corresponding to the donation, and record it on the blockchain 300. For example, the server device 30 records certificate information for outputting a donation certificate as shown in Figure 25 as a digital certificate on the blockchain 300. The server device 30 may receive and record certificate information from each support organization, or it may generate certificate information with permission from each support organization. When the server device 30 receives a request from a donor to output certificate information relating to a donation, it outputs a screen as shown in Figure 25, allowing the donor to obtain and use the certificate. The server device 30 may also verify the validity of the certificate as described above and display a screen outputting the verification result as shown in Figure 26.

[0131] Furthermore, the server device 30 may record information indicating the message (Figure 17) received from the mobile terminal device 10a and made public in steps S34 to S37 of Figure 10 on the blockchain 300, associating it with the token corresponding to the electronic ticket used.

[0132] Figure 27 is a conceptual diagram showing how the electronic ticket provision process and the fund information recording process are executed.

[0133] As shown in Figure 27, when funder A1 provides 10,000 yen to electronic ticket provider B1, tokens (for example, 10,000 tokens) corresponding to the 10,000 yen received as an electronic ticket are recorded on blockchain 300.

[0134] Furthermore, when user C1, who is eligible for the electronic ticket, uses the electronic ticket worth 700 yen at store D1, 700 of the 10,000 tokens will be recorded on blockchain 300 as having been used by user C1 at store D1. In addition, when user C1 sends a thank-you message, that message will be recorded on blockchain 300 in association with the tokens used. This allows funders to know who used the funds they provided and how. They can also see thank-you messages from users who actually used the funds.

[0135] As described above, according to the fund information recording system of this embodiment, tokens corresponding to funds received as electronic tickets from the provider are recorded on the blockchain. When a user requests an electronic ticket, first, services (supporting organizations) that can provide electronic tickets to the user are extracted, and a list of available services is presented to the user. Once a service is selected by the user, stores that the user can use are extracted, and a list of available stores is presented to the user. Once a store is selected by the user, an electronic ticket usable at that store is provided. Information about the user to whom the electronic ticket was provided is then recorded on the blockchain in association with the token corresponding to that electronic ticket. As a result, since information about the user to whom the electronic ticket was provided is recorded in association with the token corresponding to the electronic ticket, for example, a funder can understand who received the funds they provided and can track the flow of funds. Traditionally, funds such as donations, support funds, and taxes have had the characteristic of being "colorless," making it difficult to clearly understand how the donated funds were used, which has been a major challenge when making donations, etc. According to the fund information recording device of the present invention, funds provided for use as electronic tickets distributed to recipients are recorded as tokens on the blockchain, and each time an electronic ticket is distributed or used, its contents are recorded on the blockchain. Therefore, the needs of funders and others who wish to make the flow of provided funds transparent can be met.

[0136] Furthermore, the fund information recording system records information about funders who have deposited funds into electronic tickets on the blockchain, associating it with the token corresponding to the electronic ticket. As a result, information about funders who provided funds for electronic tickets is recorded on the blockchain as being associated with the token corresponding to the electronic ticket, making it possible to clearly record who provided the funds and which electronic ticket corresponds to it.

[0137] Furthermore, the fund information recording system records information about the provider of an electronic ticket on the blockchain, associating it with the token corresponding to that electronic ticket. As a result, information about the provider of an electronic ticket is recorded on the blockchain as association with the token corresponding to that electronic ticket, making it possible to clearly record which provider the electronic ticket belongs to.

[0138] Furthermore, the fund information recording system records information about the stores where electronic tickets were used on the blockchain, associating it with the token corresponding to the electronic ticket used. This means that information about the stores where the electronic ticket was used is recorded in association with the token corresponding to the electronic ticket. Therefore, funders can understand where their funds were used and gain a more detailed understanding of the flow of funds.

[0139] Furthermore, the fund information recording system records information on the blockchain regarding the quantity of tokens corresponding to the amount used as an electronic ticket. This allows funders to understand how much of their provided funds were used, providing a more detailed understanding of the flow of funds.

[0140] Furthermore, the fund information recording system acquires certificate information related to fund provision certificates that prove that a funder has provided funds to a provider, associates the certificate information with the token corresponding to the funds, and records it on the blockchain. This means that, for example, if a funder provides funds as a donation, the fact that the funder made a donation is clearly recorded on the blockchain, so the funder can obtain a highly reliable fund provision certificate that is difficult to forge or alter. The funder who has made a donation can use the acquired fund provision certificate to prove to third parties that they have made a donation for various purposes and in various situations.

[0141] Furthermore, the fund information recording system outputs information about tokens recorded on the blockchain, information about users who received electronic tickets corresponding to those tokens, and information about the stores where those electronic tickets were used, making them viewable in an associated manner. This allows funders, for example, to easily understand who used and where each electronic ticket corresponding to the funds they provided.

[0142] Furthermore, service information includes information about the registered accounts of recipients, and user information includes information about the user's registered account. This allows the provider to provide electronic tickets to users whose accounts have been pre-registered, provided that users have been pre-registered.

[0143] Furthermore, service information includes information about at least one of the recipient's age and address, and user information includes information about at least one of the user's age and address. This allows the provider to provide electronic tickets to users who meet the age or address requirements by pre-registering the age or address requirements of users who are eligible for the provider's electronic tickets.

[0144] Furthermore, if multiple providers are identified, the fund information recording system presents information about all of them to the user of the mobile device and prompts the user to select a provider. This allows the user to choose which electronic ticket to use from among the electronic tickets from multiple providers.

[0145] Furthermore, the fund information recording system refers to information about stores where electronic tickets associated with service information can be used, and processes the provision of electronic tickets. This allows, for example, each electronic ticket provider to specify the stores where the electronic tickets can be used.

[0146] Furthermore, the fund information recording system refers to information regarding the usage of electronic tickets associated with service information and processes the provision of electronic tickets. This allows, for example, each electronic ticket provider or store to specify the usage of the electronic ticket.

[0147] Furthermore, when an electronic ticket is used, the fund information recording system prompts the user to enter a message and records the entered message on the blockchain, associating it with the token corresponding to the electronic ticket. This allows, for example, funders to see messages from users of electronic tickets provided based on the funds they provided.

[0148] Furthermore, the fund information recording system will prohibit the user from using the electronic ticket again if the above message is not entered. This encourages users who use electronic tickets to enter a message. Therefore, it can encourage users of electronic tickets to directly express their gratitude to funders, giving funders a sense of having helped someone, a sense of purpose, and a positive motivation to provide further funding.

[0149] Furthermore, if there are multiple providers, the fund information recording system presents the funder with information about all of them and prompts the funder to select the provider to whom they wish to provide the funds. This allows the funder to choose the provider of the electronic ticket they wish to fund from among multiple providers.

[0150] Furthermore, according to the fund information recording system of this embodiment, the frequency of electronic ticket usage is changed according to the user's welfare benefit status. Specifically, users who do not receive welfare benefits are allowed to use the ticket once a week, while users who do receive welfare benefits are allowed to use it seven times a week. With this configuration, it is possible to provide more comprehensive support to users who receive welfare benefits.

[0151] The present invention is not limited to the embodiments described above, and can be modified in various ways within the scope of the claims.

[0152] For example, the embodiment described above used the case where a funder provides funds as a donation. However, the fund information recording device is not limited to this, as it can cover various fund providers and forms of provision. For instance, it can be applied to funds provided by various providers and in various forms, such as taxes paid by taxpayers to the national or local government, or political funds provided by companies or individuals to politicians or political parties, and used for various purposes.

[0153] Furthermore, the embodiments described above used the example of a user visiting a restaurant and using an electronic ticket. However, the electronic ticket for meals provided by the financial information recording device of the present invention is not limited to electronic tickets that can be used when visiting a restaurant, but may also be, for example, an electronic ticket that can be used with a food delivery service.

[0154] Furthermore, the embodiments described above have used the example of the financial information recording device of the present invention providing an electronic ticket for a meal. However, the electronic ticket provided by the financial information recording device of the present invention is not limited to an electronic ticket for a meal, and may be, for example, an exchange voucher redeemable for goods or services other than meals, or an electronic ticket such as a cash voucher usable at stores other than restaurants.

[0155] Furthermore, in the embodiment described above, the example given was that information regarding the rules for using electronic tickets is registered for each support organization 3a, 3b that provides the electronic tickets as service information 110. However, the providers of electronic tickets are not limited to support organizations 3a, 3b such as local governments and NPOs, but can be various funding groups. In this case, information regarding the rules for using electronic tickets is registered for each funding group.

[0156] Furthermore, in the embodiment described above, the number of times an electronic ticket can be used (frequency of use) was changed according to the user's welfare benefit status. However, the usage details that are changed according to the user's specific circumstances are not limited to the frequency of electronic ticket use; the available amount of the electronic ticket may also be changed. In this case, two values ​​for the available amount information 116 are set so that the available amount is larger when the user is receiving welfare benefits than when the user is not receiving welfare benefits.

[0157] In the embodiments described above, the functions of each device may be implemented by other devices. For example, each function of the server device 30 may be implemented by the mobile terminal devices 10a and 10b, or by other server devices. Alternatively, some of the functions of the mobile terminal devices 10a and 10b may be implemented by the server device 30.

[0158] The means and methods for performing various processing in the fund information recording device according to the above embodiment can be implemented by either a dedicated hardware circuit or a programmed computer. The program may be provided, for example, on a computer-readable recording medium such as a USB (Universal Serial Bus) memory or a DVD (Digital Versatile Disc)-ROM, or it may be provided online via a network such as the Internet. In this case, the program recorded on the computer-readable recording medium is usually transferred to and stored in a storage unit such as an HDD. Furthermore, the program may be provided as a standalone application software, or it may be incorporated into the software of the fund information recording device as a function of the device.

[0159] This application is based on Japanese Patent Application No. 2025-002268, filed on January 7, 2025, and its disclosures are referenced and incorporated as a whole.

[0160] 10a, 10b, 10c Mobile terminal device, 11, 21, 31 Control unit, 12, 22, 32 Storage unit, 13, 23, 33 Communication unit, 14 Operation display unit, 20a, 20b Terminal device, 24 Display unit, 25 Input unit, 30 Server device, 40 Network, 110 Service information, 120 Store information, 130 User information, 300 Blockchain.

Claims

1. Fund information recording device comprising: a storage unit that stores service information relating information about the provider of an electronic ticket and information about the recipients of the electronic ticket, and user information including information about the user; a fund acceptance processing unit that accepts deposits of funds from funders for the provider's electronic ticket; a recording unit that records tokens corresponding to the funds accepted as electronic tickets by the fund acceptance processing unit on a blockchain; an extraction unit that, when a request for electronic ticket provision by a user of a mobile terminal device is recognized, obtains information about the user of the mobile terminal device by referring to the user information, and extracts the provider to which the user of the mobile terminal device corresponds to the recipient by referring to the recipient information of the service information; and a provision processing unit that performs the process of providing the electronic ticket of the provider extracted by the extraction unit to the user of the mobile terminal device, wherein the recording unit records information about the user of the mobile terminal device to whom the electronic ticket was provided, relating it to the token corresponding to the electronic ticket on the blockchain.

2. The fund information recording device according to claim 1, wherein the recording unit records information about the fund provider who has deposited funds into the electronic ticket on the blockchain in association with the token corresponding to the electronic ticket.

3. The financial information recording device according to claim 1 or 2, wherein the recording unit records information relating to the provider of the electronic ticket on the blockchain in association with the token corresponding to the electronic ticket.

4. The financial information recording device according to claim 1 or 2, wherein the recording unit records information about the store where the electronic ticket was used on the blockchain in association with the token corresponding to the electronic ticket used.

5. The financial information recording device according to claim 1 or 2, wherein the recording unit records on the blockchain information relating to the quantity of tokens corresponding to the amount used as the electronic ticket.

6. The fund information recording device according to claim 1 or 2, further comprising an acquisition unit that acquires certificate information relating to a fund provision certificate proving that the fund provider has provided funds to the provider, wherein the recording unit associates the certificate information with the token corresponding to the funds and records it on the blockchain.

7. The financial information recording device according to claim 1 or 2, further comprising an output unit that outputs information relating to the token recorded on the blockchain, information relating to the user of the mobile terminal device to which the electronic ticket corresponding to the token was provided, and information relating to the store where the electronic ticket was used, in an order that the latter can be viewed in association with each other.

8. The financial information recording device according to claim 1 or 2, wherein the service information includes information relating to the registered account of the recipient, and the user information includes information relating to the user's registered account.

9. The financial information recording device according to claim 1 or 2, wherein the service information includes information relating to at least one of the age and address of the recipient, and the user information includes information relating to at least one of the age and address of the user.

10. If the extraction unit extracts multiple providers, the provision processing unit performs a process to present information about the multiple providers to the user of the mobile terminal device and prompt the user to select a provider, as described in claim 1 or 2.

11. The financial information recording device according to claim 1 or 2, wherein the service information further associates information about stores where electronic tickets can be used with information about the provider, and the provision processing unit performs the process of providing the electronic tickets by referring to the information about the stores.

12. The financial information recording device according to claim 1 or 2, wherein the service information further associates information regarding the usage of the electronic ticket with information regarding the provider, and the provision processing unit performs the process of providing the electronic ticket by referring to the information regarding the usage.

13. The service information further includes, as information relating to the usage of the electronic ticket, information indicating the frequency of use or the amount of the electronic ticket that can be used, associated with the information relating to the provider, the information indicating the frequency of use or the amount of the electronic ticket that can be used having a first value and a second value greater than the first value, the user information further includes information indicating a specific situation for the user, and the provision processing unit performs a process of providing the electronic ticket by referring to the first value if the user of the mobile terminal device is not in the specific situation, and performs a process of providing the electronic ticket by referring to the second value if the user of the mobile terminal device is in the specific situation, the fund information recording device according to claim 1 or 2.

14. The financial information recording device according to claim 1 or 2, wherein the user information is assigned identification information on a household basis for identifying the user.

15. The financial information recording device according to claim 1 or 2, wherein when the electronic ticket is used, the provision processing unit presents an input screen for entering a message and prompts the user to enter a message, and when the message is entered, the recording unit records the message on the blockchain in association with the token corresponding to the electronic ticket.

16. If the aforementioned message is not entered, the provision processing unit performs a process to prohibit the user from using the electronic ticket again, as described in claim 15.

17. If there are multiple providers, the fund receiving processing unit performs a process to present information about the multiple providers to the fund provider and prompt the fund provider to select a provider to whom the funds will be provided, according to claim 1 or 2.

18. The financial information recording device according to claim 1 or 2, wherein the electronic ticket includes an electronic ticket usable at a restaurant.

19. A method for recording financial information performed by a computer, comprising: (a) the computer storing in a storage unit service information relating to a provider of electronic tickets and information relating to recipients of the electronic tickets, and user information including information relating to a user; (b) the computer receiving a deposit of funds from a funder for the provider's electronic ticket; (c) the computer recording on a blockchain a token corresponding to the funds received as the electronic ticket in step (b); (d) the computer, when it recognizes a request for provision of electronic tickets by a user of a mobile terminal device, obtaining information relating to the user of the mobile terminal device by referring to the user information, and extracting the provider to which the user of the mobile terminal device corresponds to the recipient by referring to the recipient information of the service information; and (e) the computer performing a process to provide the user of the mobile terminal device with the electronic ticket of the provider extracted in step (d), wherein step (c) is the method for recording financial information, wherein step (c) records on a blockchain information relating to the user of the mobile terminal device to whom the electronic ticket was provided, in association with the token corresponding to the electronic ticket.

20. A fund information recording program comprising: (a) a procedure for storing in a storage unit service information that associates information about the provider of an electronic ticket with information about the recipients of the electronic ticket, and user information that includes information about the user; (b) a procedure for receiving a deposit of funds from a funder for the provider's electronic ticket; (c) a procedure for recording on a blockchain a token corresponding to the funds received as the electronic ticket in procedure (b); (d) a procedure for, when a request for electronic ticket provision by a user of a mobile terminal device is recognized, obtaining information about the user of the mobile terminal device by referring to the user information, and extracting the provider to which the user of the mobile terminal device corresponds to the recipient by referring to the recipient information of the service information; and (e) a procedure for providing the user of the mobile terminal device to the electronic ticket extracted in procedure (d), wherein procedure (c) causes a computer to execute a process to record on the blockchain information relating to the user of the mobile terminal device to whom the electronic ticket was provided, in association with the token corresponding to the electronic ticket.

Images