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

Abstract

A fund information recording device, method, and program are provided that enable a fund provider to grasp the flow of funds provided by the fund provider. [Solution] In a fund information recording system in which multiple mobile terminal devices, multiple terminal devices, and a server device can communicate with each other via a network, the server device 30, which is a fund information recording device, records a token corresponding to funds accepted as an electronic ticket from the provider on the blockchain 300, and when a user requests the provision of an electronic ticket, extracts services that can provide the electronic ticket to the user and presents a list of available services to the user, and when the user selects one service, extracts available stores and presents a list of available stores, and when the user selects one store, provides an electronic ticket that can be used at that store, and records information about the user on the blockchain in association with the token corresponding to the electronic ticket.

Description

[Technical Field]

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

[0002] Donations are the act of voluntarily giving money or goods free of charge, and come in a variety of forms. For example, children's cafeterias are donation-based initiatives that provide meals to poor families and children who eat alone, and play a major role in realizing a society of inclusive coexistence.

[0003] In this regard, Patent Document 1 below discloses a technology for providing free meals to customers at pre-registered restaurants using third-party funds. The technology in Patent Document 1 allows customers to have free meals at restaurants they visit by displaying a specific screen on a mobile device such as a smartphone. This technology allows children to have free meals at restaurants registered as children's cafeterias. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-174248 Summary of the Invention [Problem to be solved by the invention]

[0005] As mentioned above, by making donations, one can contribute to society by supporting the operation of children's cafeterias. However, there is a problem in that donors who provide funds through donations cannot know how their donations are actually used. As a result, even if people want to make donations, they cannot know whether the funds they donated have actually reached children in need, which can make them feel anxious or hesitant to donate.

[0006] The present invention has been made in view of the above-mentioned problems, and 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 that enable the flow of funds provided by a fund provider to be understood, such as to whom the funds have been distributed. [Means for solving the problem]

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

[0008] (1) A fund information recording device having a memory unit that stores service information that associates information about the provider of an electronic ticket with information about recipients of the electronic ticket, and user information that includes information about the user; a fund reception processing unit that accepts deposits of funds from funders for the electronic ticket of the provider; a recording unit that records on a blockchain a token corresponding to the funds accepted as the electronic ticket by the fund reception processing unit; an extraction unit that, when a request for electronic ticket provision from a user of a mobile terminal device is recognized, refers to the user information to obtain information about the user of the mobile terminal device, and refers to information about the recipients of the service information to extract the provider that corresponds to the recipient for the user of the mobile terminal device; and a provision processing unit that performs processing to provide the electronic ticket of the provider extracted by the extraction unit to the user of the mobile terminal device, wherein the recording unit records on the blockchain information about the user of the mobile terminal device to which the electronic ticket was provided, in association with the token corresponding to the electronic ticket.

[0009] (2) A fund information recording device as described in (1) above, in which the recording unit records information about the funder who deposited funds into the electronic ticket on the blockchain in association with the token corresponding to the electronic ticket.

[0010] (3) A fund information recording device as described in (1) or (2) above, wherein the recording unit records information regarding the provider of the electronic ticket on the blockchain in association with the token corresponding to the electronic ticket.

[0011] (4) A fund information recording device as described in (1) or (2) above, in which 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 used electronic ticket.

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

[0013] (6) A fund information recording device as described in (1) or (2) above, further comprising an acquisition unit that acquires certificate information regarding a funding certificate that proves that the fund provider has provided funds to the provider, and the recording unit associates the certificate information with the token corresponding to the funds and records it on the blockchain.

[0014] (7) A fund information recording device as described in (1) or (2) above, further having an output unit that outputs information about the token recorded on the blockchain, information about the user of the mobile terminal device to which the electronic ticket corresponding to the token was provided, and information about the store where the electronic ticket was used, in a manner that allows viewing of the information.

[0015] (8) A fund information recording device as described in (1) or (2) above, wherein the service information includes information regarding the registered account of the recipient, and the user information includes information regarding the registered account of the user.

[0016] (9) A fund information recording device as described in (1) or (2) above, wherein the service information includes information regarding at least one of the recipient's age and address, and the user information includes information regarding at least one of the user's age and address.

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

[0018] (11) The service information further includes information about stores where electronic tickets can be used, which is associated with information about the provider, and the provision processing unit performs processing to provide the electronic tickets by referring to the information about the store.A fund information recording device as described in (1) or (2) above.

[0019] (12) The service information further includes information regarding the usage content of the electronic ticket, which is associated with information regarding the provider, and the provision processing unit performs processing to provide the electronic ticket by referring to the information regarding the usage content.A fund information recording device as described in (1) or (2) above.

[0020] (13) The service information further includes information indicating the frequency of use or the available amount of the electronic ticket, which is associated with information about the provider as information regarding the use of the electronic ticket, and the information indicating the frequency of use or the available amount has a first value and a second value greater than the first value, and the user information further includes information indicating a specific situation for the user, and the provision processing unit performs processing to provide the electronic ticket by referring to the first value when the user of the mobile terminal device is not in the specific situation, and performs processing to provide the electronic ticket by referring to the second value when the user of the mobile terminal device is in the specific situation, a fund information recording device described in (1) or (2) above.

[0021] (14) A fund information recording device as described in (1) or (2) above, wherein the user information includes identification information for identifying the user on a household basis.

[0022] (15) When the electronic ticket is used, the provision processing unit presents an input screen for inputting a message and performs a process to prompt the user to input a message, and when the message is input, the recording unit associates the message with the token corresponding to the electronic ticket and records it on the blockchain. A fund information recording device as described in (1) or (2) above.

[0023] (16) The fund information recording device according to (15) above, wherein if the message is not entered, the provision processing unit performs processing to prohibit the user from using the electronic ticket next time.

[0024] (17) In the case where there are multiple providers, the funds receiving processing unit presents information about the multiple providers to the fund provider and prompts the fund provider to select the provider to whom the funds will be provided. This is a funds information recording device described in (1) or (2) above.

[0025] (18) The financial information recording device according to (1) or (2) above, wherein the electronic ticket includes an electronic ticket that can be used at a restaurant.

[0026] (19) A method for recording financial information, comprising: (a) a step of storing service information in a memory unit that associates information about the provider of an electronic ticket with information about recipients of the electronic ticket, and user information that includes information about the user; (b) a step of accepting a deposit of funds from a funder for the electronic ticket from the provider; (c) a step of recording on a blockchain a token corresponding to the funds accepted as the electronic ticket in (b); (d) a step of, when a request for electronic ticket provision 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 corresponding to the recipient by referring to information about the recipients of the service information; and (e) a step of performing a process of providing the electronic ticket of the provider extracted in (d) to the user of the mobile terminal device, wherein (c) records on the blockchain information about the user of the mobile terminal device to which the electronic ticket was provided, in association with the token corresponding to the electronic ticket.

[0027] (20) A fund information recording program including the steps of: (a) storing service information in a memory unit that associates information about the provider of an electronic ticket with information about recipients of the electronic ticket, and user information that includes information about the user; (b) accepting a deposit of funds from a funder for the electronic ticket of the provider; (c) recording a token corresponding to the funds accepted as the electronic ticket in step (b) on a blockchain; (d) when a request for electronic ticket provision from a user of a mobile terminal device is recognized, referring to the user information to obtain information about the user of the mobile terminal device, and referring to information about the recipients of the service information, for the user of the mobile terminal device to extract the provider corresponding to the recipients; and (e) performing a process to provide the electronic ticket of the provider extracted in step (d) to the user of the mobile terminal device, wherein step (c) is a fund information recording program that causes a computer to execute a process to associate information about the user of the mobile terminal device to which the electronic ticket has been provided with the token corresponding to the electronic ticket on the blockchain. [Effects of the Invention]

[0028] According to a fund information recording device according to an embodiment of the present invention, a token corresponding to funds accepted as an electronic ticket from a provider is recorded on a blockchain. When a user requests the provision of an electronic ticket, first, services (support organizations) that can provide the electronic ticket to the user are extracted, and a list of available services is presented to the user. When the user selects one service, stores available to the user are extracted, and a list of available stores is presented to the user. When the user selects one store, an electronic ticket available at that store is provided. Then, information about the user to whom the electronic ticket has been provided is recorded on the blockchain in association with the token corresponding to the electronic ticket. As a result, because information about the user to whom the electronic ticket has been provided is recorded in association with the token corresponding to the electronic ticket, for example, a fund provider can know to whom the funds they provided have been provided, and can understand the flow of funds. [Brief explanation of the drawings]

[0029] [Figure 1] FIG. 1 is a diagram showing a schematic configuration of a fund information recording system. [Figure 2] FIG. 1 is a block diagram showing a schematic configuration of a mobile terminal device. [Figure 3] FIG. 2 is a block diagram showing a schematic configuration of a terminal device. [Figure 4] FIG. 2 is a block diagram showing a schematic configuration of a server device. [Figure 5] FIG. 3 is a diagram illustrating the contents stored in a storage unit of the server device. [Figure 6] FIG. 10 is a diagram illustrating an example of service information. [Figure 7] FIG. 10 is a diagram illustrating an example of store information. [Figure 8] FIG. 10 is a diagram illustrating an example of user information. [Figure 9] 10 is a sequence chart showing the procedure of an electronic ticket provision process. [Figure 10] This is a figure following FIG. 9. [Figure 11]FIG. 10 is a diagram illustrating an example of a store search screen. [Figure 12] FIG. 10 is a diagram illustrating an example of a service list screen. [Figure 13] FIG. 10 is a diagram illustrating an example of a store list screen. [Figure 14] FIG. 10 is a diagram illustrating an example of a menu list screen. [Figure 15] FIG. 10 is a diagram illustrating an example of an order confirmation screen. [Figure 16] FIG. 10 is a diagram showing an example of a payment confirmation screen. [Figure 17] FIG. 10 is a diagram illustrating an example of a message input screen. [Figure 18] FIG. 10 is a diagram showing an example of a donation destination list screen. [Figure 19] FIG. 10 is a diagram showing an example of an image for accessing a donation deposit screen. [Figure 20] 10 is a flowchart showing the procedure for accepting donations. [Figure 21] 10 is a flowchart showing the procedure of a recording process. [Figure 22] 10 is a flowchart showing the procedure of an output process. [Figure 23] FIG. 23 is a diagram showing an example of a screen for confirming the flow of donations output in the output process of FIG. 22. [Figure 24] FIG. 23 is a diagram showing an example of a screen for confirming the flow of donations output in the output process of FIG. 22. [Figure 25] FIG. 23 is a diagram showing an example of a certificate output in the output process of FIG. 22. [Figure 26] FIG. 10 is a diagram illustrating an example of a screen showing a result of verification of a certificate. [Figure 27] FIG. 10 is a conceptual diagram showing how an electronic ticket providing process and a fund information recording process are executed. DETAILED DESCRIPTION OF THE INVENTION

[0030] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] The following description of preferred embodiments of the present invention will be given with reference to the accompanying drawings. Note that the following preferred embodiments are merely exemplary and may be modified in various ways.

[0031] Figure 1 is a diagram showing 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. The following description will use an example in which the fund information recording device records information about an electronic ticket for a meal, but electronic tickets are not limited to meals and can be used for a variety of purposes. The following description will also use an example in which a funder provides funds as a donation, but the fund provider and form of provision targeted by the fund information recording device are not limited to this and can be applied to funds provided by various providers and in various forms, such as taxes and political donations.

[0032] The electronic ticket is a ticket that allows users 2a, 2b to receive a meal free of charge by presenting it to a staff member or the like at restaurants 1a, 1b. The electronic ticket is provided independently by multiple support organizations 3a, 3b, such as local governments such as prefectures and cities, towns and villages, NPOs, and volunteer groups. Donors (funders) 4a, 4b deposit donations, which serve as the source of the electronic ticket, into the support organizations 3a, 3b. The support organizations 3a, 3b pay the meal fees of users 2a, 2b to restaurants 1a, 1b on behalf of users 2a, 2b, depending on the results of using the electronic ticket.

[0033] 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, the terminal devices 20a and 20b, and the server device 30 are configured to be able to communicate with each other via a network 40 such as the Internet.

[0034] The mobile terminal devices 10a to 10c are, for example, smartphones and are used by the users 2a and 2b and the donor 4a. The terminal devices 20a and 20b are, for example, personal computers (PCs) and are used by the system administrator 5 of the fund information recording system and the donor 4b.

[0035] The types and number of devices connected to the network 40 are not limited to the example shown in Fig. 1. A large number of mobile terminal devices and terminal devices are connected to the network 40.

[0036] <Mobile terminal device> Next, the configurations of the mobile terminal devices 10a to 10c will be described with reference to Fig. 2. Since the mobile terminal devices 10a to 10c have the same configuration, the following description will be made using the mobile terminal device 10a as a representative.

[0037] Fig. 2 is a block diagram showing a schematic configuration of the mobile terminal device 10a. As shown in Fig. 2, the mobile terminal device 10a includes 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 configured with a CPU (Central Processing Unit) and memories such as RAM (Random Access Memory) and ROM (Read Only Memory), and controls the above-mentioned units and performs various arithmetic processing according to a program.

[0039] The storage unit 12 is configured by an SSD (Solid State Drive) or an HDD (Hard Disc Drive), and stores various programs and various data.

[0040] The communication unit 13 is an interface for communicating with other devices, and uses a communication interface conforming to various wired or wireless standards.

[0041] The operation display unit 14 is, for example, a touch panel display, and is used to display and input various types of information.

[0042] <Terminal Device> Next, the configurations of the terminal devices 20a and 20b will be described with reference to Fig. 3. Since the terminal devices 20a and 20b have the same configuration, the following description will be given using the terminal device 20a as a representative.

[0043] Fig. 3 is a block diagram showing a schematic configuration of terminal device 20a. As shown in Fig. 3, terminal device 20a includes control unit 21, storage unit 22, communication unit 23, display unit 24, and input unit 25, which are interconnected by a bus. Note that, among the above-mentioned units of terminal device 20a, those having the same functions as the above-mentioned units of mobile terminal device 10a will not be described in order to avoid duplication.

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

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

[0046] <Server device> Next, the configuration of the server device 30 will be described with reference to Figure 4. 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 server device 30. As shown in Fig. 4, 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 each of the above units of server device 30 has the same function as each of the above units of mobile terminal device 10a, and therefore redundant explanations will be omitted.

[0048] The memory unit 32 stores a blockchain 300 for recording the flow of received funds and making it accessible. The blockchain 300 can be configured using a known blockchain platform such as XRP Ledger, and therefore a detailed description thereof will be omitted. The blockchain 300 may not be stored in the memory unit 32 of the server device 30, but may be stored in another device that functions as a node of the blockchain 300. In this case, the server device 30 can access the other device to record various information on the blockchain 300 or output various information recorded on the blockchain 300 in a viewable manner. Furthermore, devices such as the mobile terminal device 10a and the terminal device 20a may obtain an account to access the blockchain 300, store the blockchain 300, or access another device that stores the blockchain 300.

[0049] FIG. 5 is a diagram showing the contents stored in the storage unit 32 of the server device 30. As shown in FIG. 5, the storage unit 32 of the server device 30 stores service information 110, store information 120, and user information 130. The service information 110 is information regarding the usage rules of electronic tickets for each support organization that provides the electronic ticket. For example, the service information may include information regarding the registered account of a recipient. The service information may also include information regarding at least one of the age and address of a recipient. The store information 120 is information regarding a registered store, and the user information 130 is information regarding a registered user. For example, the user information may include information regarding the registered account of a user. The user information may also include information regarding at least one of the age and address of a user. Details of the service information 110, store information 120, and user information 130 will be described later.

[0050] The storage unit 32 of the server device 30 also stores programs corresponding to a fund receiving processing unit 210, a recording unit 220, an extracting unit 230, a providing processing unit 240, an acquiring unit 250, and an output unit 260.

[0051] The fund receiving processor 210 receives funds from funders to be deposited into electronic tickets provided by each support organization (provider).

[0052] The recording unit 220 records on the blockchain 300 a token corresponding to the funds accepted as an electronic ticket by the funds acceptance processing unit 210.

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

[0054] The provision processing unit 240 performs processing to provide a user with an electronic ticket from the provider (service) extracted by the extraction unit 230. The recording unit 220 records information about the user to whom the electronic ticket has been provided on the blockchain 300 in association with a token corresponding to the electronic ticket.

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

[0056] The output unit 260 outputs information about the token recorded on the blockchain 300, information about the user to whom the electronic ticket corresponding to the token was provided, and information about the store where the electronic ticket was used, in a manner that allows viewing.

[0057] Furthermore, the recording unit 220 may record information about the funder who deposited funds into the electronic ticket on the blockchain in association with the token corresponding to the electronic ticket.

[0058] Furthermore, the recording unit 220 may record information about 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 in association with the token corresponding to the used electronic ticket.

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

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

[0062] The functions of the above-mentioned sections are realized by the control section 31 executing the corresponding programs.

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

[0064] Next, the service information 110, the store information 120, and the user information 130 will be described in order with reference to FIGS.

[0065] 6 is a diagram showing an example of the service information 110. The service information 110 is information relating to the usage rules of an electronic ticket, and is registered in the storage unit 32 of the server device 30 by the system administrator 5 via the terminal device 20a, for example.

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

[0067] The service ID information 111 is information for identifying the support organizations 3a and 3b that are the providers of the electronic ticket, and the service name information 112 is information indicating the name of the ticket provision service provided by the support organizations 3a and 3b. The target person age information 113 is information indicating the age of the recipient of the electronic ticket, and the target person address information 114 is information indicating the address (prefecture and city / town / village) of the recipient of the electronic ticket.

[0068] The usage frequency information 115a and 115b are information indicating the number of times an electronic ticket can be used by a user in a week, and include first usage frequency information 115a and second usage frequency information 115b. The first usage frequency information 115a is information indicating the number of times an electronic ticket can be used by a user who is not receiving welfare benefits, and the second usage frequency information 115b is information indicating the number of times an electronic ticket can be used by a user who is receiving welfare benefits. The usable amount information 116 is information indicating the amount of money (maximum amount) that a user can use for a single meal, and the usable store information 117 is information indicating restaurants where the electronic ticket can be used.

[0069] The ticket number information 118 is information indicating the number of electronic tickets that the support organizations 3a and 3b can provide, and the issued ticket number information 119 is information indicating the number of issued electronic tickets. The ticket number information 118 is updated when a donation is received, and the issued ticket number information 119 is updated when an electronic ticket is issued.

[0070] 7 is a diagram showing an example of the store information 120. The store information 120 is information about registered stores, and is registered in the storage unit 32 of the server device 30 by the system administrator 5 via the terminal device 20a, for example.

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

[0072] Store ID information 121 is information for identifying a restaurant, and store name information 122 is information indicating the name of the restaurant. Location information 123 is information indicating the location (prefecture, city, town, or village) of the restaurant. Available time period information 124 is information indicating the time period during which the restaurant can provide the menu for the electronic ticket (the time period during which the user can use the electronic ticket).

[0073] The menu ID information 125 is information for identifying a menu for which an electronic ticket can be used, the menu name information 126 is information indicating the name of the menu, and the menu price information 127 is information indicating the price of the menu.

[0074] The available meal number information 128 indicates the number of meals that the restaurant can provide in one day using electronic tickets, and the already provided meal number information 129 indicates the number of meals that the restaurant has already provided in one day.

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

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

[0077] User ID information 131 is information for identifying a 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, city, town, or village). Public assistance information 135 is information indicating whether the user is receiving public assistance (not receiving: 0, receiving: 1). User ID information 131 is assigned to each household. Furthermore, 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 user name information 132.

[0078] The information stored in the storage unit 32 of the server device 30 is not limited to the above information. For example, the storage unit 32 of the server device 30 may contain information indicating the business hours and account number of a restaurant, information indicating the address and account number of a support organization that provides electronic tickets, and information indicating the user's contact information. Furthermore, the values of the ID information and the like are not limited to the above examples, and any letters, numbers, or symbols may be used.

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

[0080] 9 and 10 are sequence charts showing the steps of the electronic ticket provision process executed in the fund information recording system. The process of the sequence chart is executed by the control units 11 and 31 of the mobile terminal device 10a and the server device 30 in accordance with a program stored in the memory units 12 and 32 of the respective devices 10a and 30. Note that the process units of the sequence chart are divided according to the main process content to make each process easier to understand, and the method of classifying the process steps does not limit the present invention.

[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, such as that shown in Fig. 11, on the operation display unit 14 to receive 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 by the server device 30 when the registered user 2a logs in to the system.

[0082] The mobile terminal device 10a that has received the store search instruction transmits search instruction information instructing execution of a store search to the server device 30 (step S2).

[0083] Upon receiving the search instruction information, the server device 30 extracts services available to the user 2a of the mobile terminal device 10a (step S3). More specifically, the server device 30 first references the user information 130 to recognize the age and address of the user 2a of the mobile terminal device 10a. The server device 30 then references the target person age information 113 and target person address information 114 in the service information 110 to extract, from among multiple services, services for which the user 2a is a recipient of an electronic ticket. At this time, the server device 30 references the service information 110 to exclude from the available services services those services for which the number of issuable electronic tickets is "0" and those services for which the number of times the electronic ticket has been used by the user 2a exceeds the values in the usage frequency information 115a and 115b.

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

[0085] The mobile terminal device 10a that has received the display information displays a service list screen 320 as shown in Fig. 12 on the operation display unit 14, and prompts the user 2a to select a service (support organization) to use (step S6). Note that Fig. 12 shows an example in which two services are extracted as services to which the user 2a is eligible to receive an electronic ticket.

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

[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 the information about the selected service, the server device 30 extracts available restaurants (step S9). More specifically, the server device 30 references available restaurant information 117 in the service information 110 to extract restaurants that can use the selected service. At this time, the server device 30 references restaurant information 120 to exclude from the available restaurants any restaurants that are not open during the time period in which the electronic ticket can be used or any restaurants that can provide "0" meals.

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

[0090] The mobile terminal device 10a that has received the display information displays a store list screen 330 as shown in Fig. 13 on the operation display unit 14, and prompts the user 2a to select a store to use (step S12). Note that Fig. 13 shows an example in which three stores are extracted as stores that the user 2a can use.

[0091] Then, the mobile terminal device 10a accepts the selection of a store by the user 2a through the store list screen 330 (Step S13). More specifically, the mobile terminal device 10a accepts the selection of one store by the user 2a from, for example, 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). Thereafter, the user 2a visits the selected store.

[0093] The server device 30, which has received the information about the selected restaurant, extracts available menu items (step S15). More specifically, the server device 30 refers to the restaurant information 120 to extract available menu items at the restaurant selected by the user 2a.

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

[0095] The mobile terminal device 10a that has received the display information displays a menu list screen 340 as shown in Fig. 14 on the operation display unit 14, and prompts the user 2a to select a menu to use (step S18). Note that Fig. 14 shows an example in which one food menu (children's set meal) and the option "specify price to use" are extracted as menus available to the user 2a. The option "specify price to use" will be described later.

[0096] Then, the mobile terminal device 10a accepts the selection of a menu by the user 2a through the menu list screen 340 (step S19). More specifically, the mobile terminal device 10a accepts the selection of one menu by the user 2a from 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 piece of user ID information), the user 2a selects his or her own name through a user selection screen (not shown) and then selects a menu.

[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, which has received the information about the selected menu, generates display information for displaying an order confirmation screen and transmits it to the mobile terminal device 10a (steps S21 and S22).

[0099] The mobile terminal device 10a that has received the display information displays an order confirmation screen 350 as shown in Fig. 15 on the operation display unit 14 (step S23). The user 2a presses (tap) the order confirmation button 351 while presenting the order confirmation screen 350 as an electronic ticket to a store clerk at the store.

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

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

[0102] The mobile terminal device 10a, which has received the display information, displays a payment confirmation screen 360 as shown in Fig. 16 on the operation display unit 14 (step S28). The user 2a presses the payment confirmation button 361 while showing the payment confirmation screen 360 to the store clerk at the store.

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

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

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

[0106] The mobile terminal device 10a that has received the display information displays a message input screen 370 as shown in FIG. 17 on the operation display unit 14, and prompts the user 2a to input a thank-you message (step S34).

[0107] Then, the mobile terminal device 10a accepts an input of a message by the user 2a through the message input screen 370 (step S35). Having accepted the input of the message, the mobile terminal device 10a transmits information related to the message to the server device 30 (step S36).

[0108] The server device 30, which has received the information about the message, makes the message public (step S37). More specifically, the server device 30 makes the message public so that the donors 4a and 4b who made donations to the support organization that provided the electronic ticket can view the thank-you messages from users on the mobile terminal device 10c and the terminal device 20b.

[0109] If a thank-you message is not entered, server device 30 prohibits user 2a from using the electronic ticket again until a thank-you message is entered. This configuration ensures that a thank-you message is entered by the user.

[0110] In the above-described electronic ticket provision process, when an electronic ticket is used by specifying an amount, the server device 30 refers to the available amount information 116 in the service information 110 and performs a process of presenting an amount input screen (not shown) to the user 2a, with the available amount as the upper limit. When the user 2a inputs the amount to be used, the server device 30 issues an electronic ticket for that amount.

[0111] Hereinafter, the process of accepting input of donations from donors 4a and 4b will be described with reference to FIGS.

[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 to the support organizations 3a, 3b by accessing the input screen from their mobile terminal device 10c or terminal device 20b.

[0113] At this time, the donor can select one support organization (service) to which the donation will be sent from among a plurality of support organizations (services) via a donation recipient list screen 400 as shown in Fig. 18. With this configuration, the donor can donate to the support organization of their choice.

[0114] The guidance to the input screen may be achieved, for example, by displaying a poster 500 such as that shown in Fig. 19 in a restaurant or the like. 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 executed in the fund information recording system will be described below with reference to FIGS.

[0116] Fig. 20 is a flowchart showing the steps of the donation acceptance process. Fig. 21 is a flowchart showing the steps of the recording process. Fig. 22 is a flowchart showing the steps of the output process. Figs. 23 and 24 are diagrams showing examples of screens for confirming the donation flow output in the output process of Fig. 22. Fig. 25 is a diagram showing an example of a certificate output in the output process of Fig. 22. Fig. 26 is a diagram showing an example of a screen showing the verification results of the certificate.

[0117] First, the donation acceptance process will be described.

[0118] 20, the server device 30 determines whether or not a donation has been received from a donor (step S101). The donation is received, for example, as a deposit of funds into an electronic ticket 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 the donation is accepted (step S101: YES), the server device 30 issues a token corresponding to the funds accepted as an electronic ticket and records it on the blockchain 300 (step S102). For example, if the server device accepts funds worth 10,000 yen, 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 (funder) who deposited funds for the electronic ticket on the blockchain 300 in association with the token corresponding to the electronic ticket. The server device 30 may also record information about the provider of the electronic ticket on the blockchain 300 in association with the token corresponding to the electronic ticket. The server device 30 then terminates the donation acceptance process.

[0121] Next, the process of recording information relating to the use of an electronic ticket will be described.

[0122] 21, the server device 30 determines whether or not an electronic ticket has been used (step S201). For example, when an electronic ticket is used by a user at a designated store or the like, the server device 30 determines that the electronic ticket has been used. Note that the server device 30 may 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 the electronic ticket has not been used (step S201: NO), the server device 30 waits until the electronic ticket is used.

[0124] When an electronic ticket is used (step S201: YES), the server device 30 records information about the electronic ticket use 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 on the blockchain 300 in association with the token. The information about the user may be, for example, user ID information for identifying the user in the server device 30, or 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 on the blockchain 300 in association with the token corresponding to the used electronic ticket. The server device 30 may also record information about the number of tokens corresponding to the amount used as the electronic ticket on the blockchain 300.

[0125] Next, various methods of output processing will be described.

[0126] As shown in FIG. 22, the server device 30 determines whether an output request for various information has been received (step S301). For example, a donor operates the terminal device 20a or the like to transmit an output request to the server device 30 in order to confirm various information related to the funds donated by the donor. The output request includes information for identifying the donor and information for identifying 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 transmitted from the terminal device 20a.

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

[0128] If the output request is accepted (step S301: YES), the server device 30 outputs various pieces of information recorded on the blockchain 300 so that they can be viewed (step S302). For example, the server device 30 outputs information about tokens corresponding to funds provided by donors, information about users to whom electronic tickets corresponding to the tokens have been provided, and information about stores where the electronic tickets have been used, in association with each other, so that they can be viewed. For example, the server device 30 outputs various pieces of information recorded on the blockchain 300 so that they can be viewed by outputting screens such as those shown in FIGS. 23 and 24.

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

[0130] The server device 30 may also acquire certificate information related to a donation certificate (funding certificate) that certifies that a donor has made a donation to a support organization, associate the certificate information with a token corresponding to the donation, and record the certificate information on the blockchain 300. For example, the server device 30 records certificate information for outputting a donation certificate such as that shown in FIG. 25 as a digital certificate on the blockchain 300. The server device 30 may receive and record certificate information from each support organization, or 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 related to a donation, it outputs a screen such as that shown in FIG. 25 so that the donor can obtain and use the certificate. The server device 30 may also verify the validity of the certificate and display a screen outputting the verification result as shown in FIG. 26.

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

[0132] FIG. 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 a fund provider A1 provides 10,000 yen in funds to an electronic ticket provider B1, a token (e.g., 10,000 tokens) corresponding to the 10,000 yen in funds accepted as an electronic ticket is recorded on the blockchain 300.

[0134] Furthermore, when user C1, who is the recipient of an electronic ticket, uses an electronic ticket worth 700 yen at store D1, it is recorded on the blockchain 300 that 700 of the 10,000 tokens were used by user C1 at store D1. Furthermore, when user C1 sends a thank-you message, the message is recorded on the blockchain 300 in association with the tokens used. This allows the fund provider to know who used the funds they provided and how. Furthermore, they can also check thank-you messages from users who actually used the funds.

[0135] As described above, according to the financial information recording system of this embodiment, a token corresponding to funds accepted as an electronic ticket from a provider is recorded on a blockchain. When a user requests the provision of an electronic ticket, first, services (support organizations) that can provide the electronic ticket to the user are extracted, and a list of available services is presented to the user. When the user selects one service, stores available to the user are extracted, and a list of available stores is presented to the user. When the user selects one store, an electronic ticket available 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. This allows, for example, a financial provider to know to whom the funds they provided were provided and to understand the flow of funds. Conventionally, funds such as donations, support funds, and taxes have the so-called "colorless" characteristic, making it difficult to clearly understand what the provided funds were used for. This has been a major challenge when making donations, etc. According to the fund information recording device of the present invention, funds provided to be used as electronic tickets distributed to recipients are recorded as tokens on the blockchain, and each time an electronic ticket is distributed or used, the details of that distribution are recorded on the blockchain. This satisfies the needs of funders and others who want to make the flow of provided funds transparent.

[0136] Furthermore, the fund information recording system records information about the funder who deposited funds for the electronic ticket on the blockchain in association with the token corresponding to the electronic ticket. As a result, information about the funder who provided funds for the electronic ticket is recorded on the blockchain in association with the token corresponding to the electronic ticket, making it possible to clearly record who provided the funds for the electronic ticket.

[0137] Furthermore, the fund information recording system records information about the provider of the electronic ticket on the blockchain in association with the token corresponding to the electronic ticket. As a result, the provider of the electronic ticket can be clearly recorded, since the information about the provider of the electronic ticket is recorded on the blockchain in association with the token corresponding to the electronic ticket.

[0138] The fund information recording system also records information about the store where the electronic ticket was used on the blockchain, in association with the token corresponding to the used electronic ticket. This allows information about the store where the electronic ticket was used to be recorded in association with the token corresponding to the electronic ticket. Therefore, fund providers can know where the funds they provided were used and can understand the flow of funds in more detail.

[0139] The fund information recording system also records information on the number of tokens corresponding to the amount used as an electronic ticket on the blockchain. This allows the fund provider to know how much of the funds they provided has been used, enabling them to understand the flow of funds in more detail.

[0140] The fund information recording system also obtains certificate information related to a funding certificate that certifies that a funder has provided funds to a provider, associates the certificate information with a token corresponding to the funds, and records the information on the blockchain. As a result, for example, if a funder provides funds as a donation, the fact that the funder made the donation is clearly recorded on the blockchain, allowing the funder to obtain a highly reliable funding certificate that is difficult to forge or alter. The funder who made the donation can use the obtained funding certificate to prove to third parties that they made the donation for various purposes and in various situations.

[0141] The fund information recording system also outputs, in a viewable manner, information about tokens recorded on the blockchain, information about users to whom electronic tickets corresponding to those tokens were provided, and information about stores where those electronic tickets were used, in association with each other. This allows, for example, fund providers to easily understand who and where each electronic ticket corresponding to the funds they provided was used.

[0142] The service information includes information about the registered account of the recipient, and the user information includes information about the registered account of the user. This allows the provider to provide the electronic ticket to the user whose account has been registered in advance by registering the account of the user who will be the recipient of the provider's electronic ticket in advance.

[0143] The service information includes information on at least one of the recipient's age and address, and the user information includes information on at least one of the user's age and address. This allows a provider to provide its electronic tickets to users who meet the age or address conditions by registering in advance the age or address conditions of users who will receive the provider's electronic tickets.

[0144] Furthermore, if multiple providers are extracted, the fund information recording system performs processing to present information about the multiple providers to the user of the mobile terminal device and prompt the user to select a provider, allowing the user to select an electronic ticket to use from among the electronic tickets from the multiple providers.

[0145] The fund information recording system also performs a process of providing an electronic ticket by referencing information about stores where the electronic ticket associated with the service information can be used, which allows, for example, each electronic ticket provider to specify stores where the electronic ticket can be used.

[0146] The fund information recording system also performs the process of providing an electronic ticket by referencing information related to the usage of the electronic ticket associated with the service information, which 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 performs a process that prompts the user to input a message, associates the input message with a token corresponding to the electronic ticket, and records the message on the blockchain. This allows, for example, a funder to check messages from users of electronic tickets provided using funds that the funder provided.

[0148] Furthermore, if the above message has not been entered, the funding information recording system will prohibit the user from using the electronic ticket again. This will encourage users who have used an electronic ticket to enter a message. This will encourage electronic ticket users to directly convey feelings of gratitude to the funder, giving the funder a sense of accomplishment and meaning in knowing that they have helped someone, as well as positive feelings such as a desire to provide further funding.

[0149] Furthermore, if there are multiple providers, the fund information recording system performs processing to present information about the multiple providers to the funder and prompt the funder to select the provider to which the funds will be provided, thereby allowing the funder to select the provider to which they wish to provide funds from among the multiple electronic ticket providers.

[0150] Furthermore, according to the financial information recording system of this embodiment, the frequency of electronic ticket use is changed depending on the user's welfare status. Specifically, users who do not receive welfare are allowed to use the electronic ticket once a week, while users who receive welfare are allowed to use it seven times a week. This configuration allows users who receive welfare to receive more generous support.

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

[0152] For example, in the above-described embodiment, a case where a funder provides funds as a donation has been described as an example. However, the fund providers and forms of provision that the fund information recording device targets are not limited to this. For example, the device can be applied to funds provided by various providers and in various forms and used for various purposes, such as taxes provided by taxpayers to the state or local government, and political funds provided by companies or individuals to politicians or political parties.

[0153] In the above embodiment, the user visits a restaurant and uses an electronic ticket. However, the electronic ticket for a meal provided by the fund information recording device of the present invention is not limited to an electronic ticket that can be used at a restaurant, and may be, for example, an electronic ticket that can be used for a food delivery service.

[0154] In the above-described embodiment, the fund information recording device of the present invention provides an electronic ticket for a meal. However, the electronic ticket provided by the fund 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 that can be exchanged for goods or services other than meals, or a voucher that can be used at stores other than restaurants.

[0155] In the above-described embodiment, an example has been described in which information on the usage rules for electronic tickets is registered for each of the support organizations 3a and 3b that provide the electronic tickets as the service information 110. However, the providers of electronic tickets are not limited to support organizations 3a and 3b such as local governments and NPO corporations, but may be various funding groups. In this case, information on the usage rules for electronic tickets is registered for each funding group.

[0156] In the above-described embodiment, the number of times an electronic ticket can be used (usage frequency) is changed depending on the user's welfare status. However, the usage content that is changed depending on the user's specific status is not limited to the frequency of electronic ticket use, and the available amount of the electronic ticket may also be changed. In this case, two values of the available amount information 116 are set so that the available amount is larger when the user is receiving welfare than when the user is not receiving welfare.

[0157] In the above-described embodiment, the functions of each device may be realized by another device. For example, the functions of the server device 30 may be realized by the mobile terminal devices 10a and 10b, or may be realized by another server device. Alternatively, some of the functions of the mobile terminal devices 10a and 10b may be realized by the server device 30.

[0158] The means and methods for performing various processes in the fund information recording device according to the above-described embodiments can be realized by either dedicated hardware circuits or a programmed computer. The program may be provided by a computer-readable recording medium such as a USB (Universal Serial Bus) memory or a DVD (Digital Versatile Disc)-ROM, or may be provided online via a network such as the Internet. In this case, the program recorded on the computer-readable recording medium is typically transferred to and stored in a storage unit such as a hard disk drive. The program may also be provided as standalone application software, or may be incorporated into the software of the fund information recording device as a function of the device. [Explanation of symbols]

[0159] 10a, 10b, 10c: portable terminal devices; 11, 21, 31 control section, 12,22,32 storage section, 13, 23, 33 Communications Department, 14 Operation display section, 20a, 20b terminal devices, 24 Display section, 25 input section, 30 server devices, 40 networks, 110 Service Information, 120 store information, 130 User information, 300 Blockchain.

Claims

1. a storage unit that stores service information that associates information about an electronic ticket provider with information about recipients of the electronic ticket, and user information that includes information about users; a funds receiving processing unit that receives funds from a fund provider to deposit into the electronic ticket of the provider; a recording unit that records, on a blockchain, a token corresponding to the funds accepted as the electronic ticket by the funds acceptance processing unit; an extraction unit that, when a request for providing an electronic ticket by a user of a portable terminal device is recognized, acquires information about the user of the portable terminal device by referring to the user information, and extracts the provider corresponding to the recipient of the service information by referring to information about the recipient of the service information; a providing processing unit that performs processing to provide the electronic ticket of the provider extracted by the extraction unit to the user of the mobile terminal device, The recording unit is a fund information recording device that records information about the user of the mobile terminal device to which the electronic ticket was provided on the blockchain in association with the token corresponding to the electronic ticket.

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

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

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

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

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

7. 3. The fund information recording device according to claim 1 or 2, further comprising an output unit that outputs information about the token recorded on the blockchain, information about the user of the mobile terminal device to which the electronic ticket corresponding to the token was provided, and information about the store where the electronic ticket was used, in a manner that allows viewing of the information.

8. The service information includes information about the registered account of the distribution recipient, 3. The fund information recording device according to claim 1, wherein the user information includes information about the user's registered account.

9. the service information includes information regarding at least one of the age and address of the recipient; 3. The fund information recording device according to claim 1, wherein the user information includes at least one of the user's age and address.

10. A fund information recording device as described in claim 1 or 2, wherein when the extraction unit extracts multiple providers, the provision processing unit performs a process of presenting information about the multiple providers to the user of the mobile terminal device and prompting the user to select the provider.

11. The service information further includes information about a store where the electronic ticket can be used, and the information about the provider is associated with the information about the provider.

3. The fund information recording device according to claim 1, wherein the providing processing unit performs processing to provide the electronic ticket by referring to information about the store.

12. In the service information, information regarding the use of the electronic ticket is further associated with information regarding the provider, 3. The fund information recording device according to claim 1, wherein the providing processing unit performs processing to provide the electronic ticket by referring to information related to the content of use.

13. The service information further includes information indicating the frequency of use of the electronic ticket or the available amount of the electronic ticket, which is associated with the information about the provider, as information about the use of the electronic ticket; the information indicating the available use frequency or the available use amount has a first value and a second value greater than the first value; The user information further includes information indicating a specific situation about the user; The provision processing unit performs a process of providing the electronic ticket by referring to the first value when 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 when the user of the mobile terminal device is in the specific situation. A fund information recording device as described in claim 1 or 2.

14. 3. The fund information recording device according to claim 1, wherein the user information includes identification information for identifying users on a household basis.

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

16. 16. The fund information recording device according to claim 15, wherein if the message has not been entered, the provision processing unit performs processing to prohibit the user from using the electronic ticket next time.

17. A fund information recording device as described in claim 1 or 2, wherein when there are multiple providers, the fund reception processing unit performs a process of presenting information regarding the multiple providers to the fund provider and prompting the fund provider to select the provider to whom the funds will be provided.

18. 3. The fund information recording device according to claim 1, wherein the electronic ticket includes an electronic ticket that can be used at a restaurant.

19. A computer-implemented method for recording financial information, comprising: a step (a) of causing the computer to store in a storage unit service information that associates information about an electronic ticket provider with information about recipients of the electronic ticket, and user information that includes information about the user; (b) the computer accepting a deposit of funds from a funder into the electronic ticket of the provider; (c) the computer records on a blockchain a token corresponding to the funds accepted as the electronic ticket in (b); (d) when the computer recognizes a request for electronic ticket provision from a user of a portable terminal device, it refers to the user information to acquire information about the user of the portable terminal device, and refers to information about the recipient of the service information to extract the provider corresponding to the recipient of the service information from the user of the portable terminal device; and (e) a step by the computer of providing the electronic ticket of the provider extracted in (d) to the user of the mobile terminal device, Step (c) is a fund information recording method in which information about the user of the mobile terminal device to which the electronic ticket was provided is recorded on the blockchain in association with the token corresponding to the electronic ticket.

20. a step (a) of storing in a storage unit service information that associates information about an electronic ticket provider with information about recipients of the electronic ticket, and user information that includes information about the user; (b) a step of accepting a deposit of funds from a fund provider into the electronic ticket of the provider; a step (c) of recording on a blockchain a token corresponding to the funds accepted as the electronic ticket in the step (b); a step (d) of, when a request for provision of an electronic ticket by a user of a portable terminal device is recognized, acquiring information about the user of the portable terminal device by referring to the user information, and extracting the provider corresponding to the recipient of the service information by the user of the portable terminal device by referring to information about the recipient of the service information; and step (e) of performing a process of providing the electronic ticket of the provider extracted in step (d) to the user of the mobile terminal device, Step (c) is a fund information recording program that causes a computer to execute a process of recording information about the user of the mobile terminal device to which the electronic ticket has been provided on the blockchain in association with the token corresponding to the electronic ticket.

Images