Donor device

Abstract

To make it possible to directly provide a return gift to hometown tax payment at site.SOLUTION: A computer executes: a step of accepting an application for donation in which a locally provided item is a return gift from a donor device 20 and storing information specific to each donation in a storage device 11; and a step of transmitting donation detail information including the information unique to each donation to the donor device 20. The computer also executes a step of acquiring, via a provider device 50 operated by a provider of the return gift, the information unique to each donation included in the donation detail information received by the donor device 20. Furthermore, the computer executes a step of determining whether the information unique to each donation acquired via the provider device 50 and the information unique to each donation stored in the storage device 11 match, as a condition for providing the locally provided item to the donor.SELECTED DRAWING: Figure 10

Description

[Technical field]

[0001] The present invention relates to a hometown tax payment support system, and more particularly to a hometown tax payment support system that supports local governments. [Background technology]

[0002] Donors who make hometown tax payments to a specific local government can usually receive a gift in return for their donation. The gift is usually sent by the gift provider (a gift company) and delivered directly to the donor.

[0003] The shipping fee is not charged to the donor, but to the local government by the donor, so the local government needs to manage the shipping fee, even though it is neither the sender nor the recipient of the return gift. However, as mentioned above, since the return gift is sent by the donor, the local government cannot know the exact shipping fee and often just pays what the donor tells them to.

[0004] In addition, with the enactment of the Act amending the Local Tax Act, etc. (Act No. 2 of 2019), a designated system for hometown tax donations was created, and local governments must ensure that the return gift ratio is 30% or less and that solicitation expenses are 50% or less (for example, Non-Patent Document 1). On the other hand, if it becomes possible to provide gifts in return for hometown tax donations directly at the local area, there will be no shipping costs for the gifts, which will also lead to a reduction in the costs of soliciting gifts. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] internet <URL:http: / / www.soumu.go.jp / main_sosiki / jichi_zeisei / czaisei / czaisei_seido / furusato / file / report20190401_05.pdf> Summary of the Invention [Problem to be solved by the invention]

[0006] Therefore, an objective of the present invention is to make it possible to provide gifts in return for hometown tax donations directly on site. [Means for solving the problem]

[0007] In order to solve the above problems, in the present invention, a computer executes the steps of accepting a donation application for a local product as a return gift from a donor device, storing information unique to each donation in a storage device, and transmitting donation detail information including the information unique to each donation to the donor device. Also, the computer executes the step of acquiring the information unique to each donation included in the donation detail information received by the donor device via a donor device operated by the donor of the return gift.

[0008] Furthermore, as a condition for providing a local item to a donor, a step is executed to determine whether the information unique to each donation acquired via the donor device matches the information unique to each donation stored in the storage device. Effect of the Invention

[0009] According to the present invention, it is possible to provide gifts in return for hometown tax donations directly on-site. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a configuration diagram of an overall system including a hometown tax payment support system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a structural diagram of a donation management record stored in the database of FIG. [Diagram 3] FIG. 3 is a structural diagram of a back-yard rate table stored in the database of FIG. [Figure 4] FIG. 4 is a structural diagram of a reception site rate table stored in the database of FIG. [Diagram 5] FIG. 5 is a structural diagram of a settlement rate table stored in the database of FIG. [Figure 6] FIG. 6 is a structural diagram of a shipping fee table stored in the database of FIG. [Figure 7] FIG. 7 is a structural diagram of a return gift price table stored in the database of FIG. [Figure 8] FIG. 8 is a structural diagram of a delivery status table stored in the database of FIG. [Figure 9] FIG. 9 is a structural diagram of a shipping rate table stored in the database of FIG. [Figure 10] FIG. 10 is a configuration diagram showing a modified example of the embodiment of the present invention. [Figure 11] FIG. 11 is a structural diagram of a personal information record stored in the database of FIG. [Figure 12] FIG. 12 is a structural diagram of an item name record stored in the database of FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In Fig. 1, a hometown tax payment support system 10 is communicably connected to external computer devices through a computer network N such as the Internet. The external computer devices include a donor device 20, a reception site system 30, a local government device 40, a return gift provider device 50, and a delivery system 60.

[0012] The donor device 20 is a computer device operated by a donor making a hometown tax donation, and is not limited to a device owned by the donor, but may be a device installed on a floor used by an unspecified number of people. The reception site system 30 is a computer system that provides a reception site for accepting hometown tax donations, and includes providing a hometown tax donation portal site and a reception site unique to the local government. The local government device 40 is a computer device operated by the local government. The provider device 50 is a computer device operated by a provider of a return gift. The deliverer system 60 is a computer system operated by a deliverer.

[0013] Each of the computers 20, 30, 40, 50, 60 comprises a processor, a storage device, an input device, an output device, and a communication device as the basic elements of a computer. The processor realizes the functions of each computer by executing a program. Information used by the processor for processing is read from the storage device. Information processed by the processor is stored in the storage device. The input device acquires information required for the processor's processing from the outside. The output device outputs the information processed by the processor in a manner that appeals to the human five senses, such as sight. The communication device sends and receives information to and from an external computer via the computer network N. In the following explanation, the basic operations of these computers may be omitted.

[0014] The hometown tax donation support system 10 is also a computer system, and is equipped with a processor, a storage device, an input device, an output device, and a communication device as the basic elements of a computer. The operation of each element is similar to that described above. In this embodiment, the hometown tax donation support system 10 is equipped with an expense management function and a shipping management function. The expense management function is a function for managing the status of hometown tax donation solicitation expenses in the local government. The shipping management function is a function for managing the shipping status of return gifts, and is also capable of disclosing the shipping status to the reception site system 30.

[0015] A database 11 of information necessary for executing each of the above functions is stored in the storage device of the hometown tax payment support system 10. In this embodiment, the database 11 stores a donation management record, a backyard rate table, a reception site rate table, a settlement rate table, a delivery charge table, a return gift price table, and a delivery status table, all of which are shown in Figures 2 to 8. The structure of the database 11 may be any structure that allows the necessary information to be linked and managed, and may be selected from hierarchical, network, relational, and other types.

[0016] The donation management record has the structure shown in Figure 2. That is, for each donation ID, the donation date, local government ID, donation amount, card company ID, payment fee, gift ID, gift value, gift delivery address, gift delivery fee, reception site ID, reception site fee (site fee), back-office fee, other expenses included in the collection expenses, total expenses, and delivery ID are linked.

[0017] A unique value that does not overlap with other donations is assigned to the donation ID for each hometown tax donation. The donation date is the date on which the payment for the hometown tax donation was completed. The local government ID is assigned a unique value that indicates the local government to which the hometown tax donation was made. The donation amount is the amount for which the payment for the hometown tax donation was completed. The card company ID is assigned a unique value that indicates the company (credit card company, etc.) to which the hometown tax donation is paid. The payment fee is the fee paid to the company to which the payment is made when the hometown tax donation is paid. The return gift ID is assigned a unique value that indicates the return gift corresponding to the hometown tax donation. The return gift delivery address is the delivery address (address or part of it) specified by the donor. The return gift value is the amount borne by the local government as the price of the return gift. The return gift shipping fee is the amount borne by the local government as the shipping fee for the return gift. The return gift shipping fee may be included in the return gift value.

[0018] The reception site ID is assigned a unique value that indicates the reception site that accepted the hometown tax donation. The site fee is the amount of commission paid by the local government to the reception site for that hometown tax donation. The backyard fee is the commission paid to the company that provides the hometown tax donation support system. Other expenses are amounts not included in the solicitation expenses other than those mentioned above. Total expenses are the amount of solicitation expenses corresponding to one donation, and are represented by the sum H of B through G in Figure 2 for each donation management record. A unique value is assigned to the delivery ID for each delivery of a return gift.

[0019] The backyard fee table associates a local government ID with a backyard fee rate as shown in Figure 3. A backyard fee rate determined for each local government is set in advance.

[0020] The reception site fee table associates reception site IDs with site rates. A site rate is preset for each reception site.

[0021] The payment fee table links the card company ID with the payment fee rate. The site fee rate determined for each card company is preset.

[0022] The shipping fee table links the reward item ID with the shipping fee. A shipping fee is preset for each reward item and delivery address.

[0023] The gift price table associates a gift ID with a gift price. The price of each gift is preset.

[0024] The delivery status table links the delivery ID with delivery status information. The delivery status information indicates the delivery status of the package, such as whether it has been shipped, and is updated according to changes in the delivery status.

[0025] In the above, each rate indicates a percentage of the donation amount.

[0026] Next, the expense management function of the operation of this embodiment will be described.

[0027] When a hometown tax payment application is made from the donor device 20 to the reception site system 30, the reception site system 30 stores in a storage device, each time a donation is received, a donation ID, a donation date, a municipality ID of the municipality to which the donation is made, a donation amount, a card company ID, a gift ID, a gift delivery address, and a reception site ID, in association with each other. The reception site system 30 transmits this association information to the hometown tax payment support system 10 at a predetermined timing. In addition, if the donor device 20 itself has a hometown tax payment application function, when a hometown tax payment application is made, the donor device 20 links the donation ID, donation date, municipality ID of the municipality to which the donation is made, donation amount, card company ID, return gift ID, return gift delivery address, and reception site ID for each donation received, and transmits this linking information to the hometown tax payment support system 10.

[0028] The hometown tax payment support system 10 receives the above-mentioned linking information and executes the following processes (1) to (8) by a processor. Hereinafter, when the term "processor" is used, it refers to the processor of the hometown tax payment support system 10.

[0029] (1) Refer to the back-yard fee rate table to find the back-yard fee rate corresponding to the local government ID, and multiply the donation amount by the back-yard fee rate to find the back-yard fee.

[0030] (2) The receiving site rate table is referenced to determine the site rate corresponding to the receiving site ID, and the site fee is calculated by multiplying the donation amount by the site rate.

[0031] (3) Refer to the payment fee table to find the payment fee rate corresponding to the card company ID, and multiply the donation amount by the payment fee rate to find the payment fee.

[0032] (4) Refer to the shipping fee table to determine the shipping fee corresponding to the reward item ID and reward item delivery address.

[0033] (5) Refer to the gift price table to determine the gift price corresponding to the gift ID.

[0034] (6) Determine the amount of other expenses that fall under recruitment expenses.

[0035] (7) Then, the total expenses are calculated by adding the donation amount, payment processing fee, value of the gift, shipping fee for the gift, site fee, back-office fee, and other expenses.

[0036] (8) A donation management record linking the following is registered in the database 11: donation ID, donation date, local government ID, donation amount, card company ID, payment fee, gift ID, gift delivery address, gift value, gift shipping fee, reception site ID, site fee, backyard fee, other expenses, and total expenses.

[0037] The processor repeats the above-mentioned processes (1) to (8) for the linking information for each donation received from the reception site system 30.

[0038] When a local government official wishes to check the status of solicitation expenses, he or she operates the local government device 40 and logs into the hometown tax payment support system 10. The hometown tax payment system 10 acquires the local government ID of the logged-in local government. Next, when a request to check the status of solicitation expenses is received from the local government device 40, the donation management record to be processed is extracted from the database 11 according to the filtering conditions as follows.

[0039] (1) When no filtering conditions are specified The processor extracts from the database 11 a plurality of donation management records that have a matching local government ID and whose donation date falls within the current fiscal year.

[0040] (2) When narrowing down the search by specifying the reception site The processor receives the designation of the reception site from the local government device 40. The processor extracts from the database 11 a plurality of donation management records whose local government ID matches, whose reception site ID matches the designated reception site, and whose donation date falls within the current fiscal year.

[0041] (3) Narrow your search by specifying a card company The processor receives the card company designation from the local government device 40. The processor extracts from the database 11 a plurality of donation management records whose local government ID matches, whose card company ID matches the designated card company, and whose donation date falls within the current fiscal year.

[0042] (4) When narrowing down your search by specifying a gift The processor receives the designation of the return gift from the local government device 40. The processor extracts from the database 11 a plurality of donation management records in which the local government ID matches, the designated return gift and the return gift ID match, and the donation date falls within the current fiscal year.

[0043] (5) Narrow your search by donation date The processor receives a designation of the donation date period to be processed from the local government device 40. The processor extracts from the database 11 a plurality of donation management records that have a matching local government ID and whose donation dates fall within the designated period.

[0044] (6) When narrowing down the search by specifying multiple elements above The processor receives multiple designations of the reception site, the card company, the return gift, or the donation date period from the local government device 40. The processor extracts from the database 11 multiple donation management records that have a matching local government ID, that have matching IDs for the multiple designated elements, and that have donation dates that fall within the current fiscal year or the designated period.

[0045] Next, the processor calculates the total donation amount and the total expense amount for the extracted donation management records, and further calculates the ratio of the total expense amount to the donation amount (expense rate) by dividing the total expense amount by the total donation amount.

[0046] Furthermore, the processor reads out a threshold value (e.g., 50%) of the overhead ratio preset in the storage device and compares it with the overhead ratio calculated above. If the overhead ratio exceeds the threshold, it transmits notification data indicating that to the requesting local government device 40. Furthermore, the processor transmits the calculated overhead ratio data to the local government device 40 regardless of whether the threshold is exceeded. The local government device 40 outputs the status of the overhead ratio to an output device based on the received overhead ratio data and notification data. For example, it is possible to display the overhead ratio in a different color depending on whether the overhead ratio exceeds the threshold. The threshold may be set in stages, and the overhead ratio may be displayed in different colors depending on which stage it is in. For example, when the overhead ratio exceeds a first threshold indicating that it is approaching 50%, notification data may be generated that indicates the overhead ratio, etc. in yellow, and when the overhead ratio exceeds a second threshold indicating that it has reached 50%, notification data may be generated that indicates the overhead ratio, etc. in red.

[0047] According to the expense management function of the present embodiment described above, a local government that is not a provider of return gifts can manage the shipping costs of return gifts. Furthermore, information on the status of return gift solicitation expenses, including return gift shipping costs, can be provided to the local government in real time. Since the status of solicitation expenses for each site and each return gift can be known, for example, it becomes easy to review sites and return gifts that incur high solicitation expenses.

[0048] Here, the return gift shipping fee may be calculated based on the shipping rate (proportion to the donation amount) for each return gift. In this case, the database 11 stores the shipping rate table shown in FIG. 9. The shipping rate table links the return gift ID with the shipping rate. A shipping rate is set in advance for each return gift. The processor refers to the shipping rate table to find the shipping rate corresponding to the return gift ID, and multiplies the donation amount by the shipping rate to find the return gift shipping fee. The configuration is as follows. That is, A database that stores a delivery rate table that links, for each gift, an identifier of a gift given according to the amount of the hometown tax donation and a delivery rate according to the amount of the gift; A hometown tax donation support system comprising a processor that receives information on the donation amount corresponding to the donation, an identifier of a return gift, and an identifier of a local government to which the donation is to be made from a reception site system that accepts the hometown tax donation, reads out the shipping rate corresponding to the return gift identifier from the shipping rate table, multiplies the donation amount by the shipping rate to determine a shipping cost for the return gift, and records the shipping cost in a database for each local government to which the donation is to be made.

[0049] Next, a shipping management function of the operation of this embodiment will be described.

[0050] Normally, the reception site accepts donations from the local government, but is not connected to the gift seller, so it is difficult to know whether the gift has actually been shipped, and it is difficult to answer inquiries from donors about the status of the gift. However, this system is able to disclose the delivery status of the gift to the portal site system that acts as the reception site system and the local government's own hometown tax donation site system.

[0051] When a reception site wishes to know the delivery status of a return gift for which the reception site has received an application, the reception site staff operates a terminal included in the reception site system 30 and logs into the hometown tax donation support system 10. The hometown tax donation support system 10 obtains the reception site ID of the logged-in reception site. Next, when a request for checking the delivery status is received from the terminal along with a designated donation ID, the system reads out from the database 11 the delivery ID of the donation management record that matches the donation ID and the reception site ID. Furthermore, the system obtains current delivery status information corresponding to the read delivery ID from the delivery status table. The processor transmits the obtained delivery status information to the terminal that originated the request. The terminal outputs the received delivery status information to a display device or the like. Furthermore, when a user of a terminal in the hometown tax payment support system 10 wishes to know the delivery status of a return gift, the user operates the terminal and logs into the hometown tax payment support system 10. After authenticating the user, the hometown tax payment support system 10 receives a request from the terminal to check the delivery status, and extracts the delivery status information stored in the database 11 and transmits it to the requesting terminal. The terminal outputs the received delivery status information on a display device or the like. Here, if the hometown tax donation support system 10 knows the reception site ID of the communication destination and a connection with the communication destination is established, the above login is not required. In addition, the hometown tax donation support system 10 may provide a list of multiple delivery status information corresponding to the reception site ID. In this case, the above donation ID does not need to be specified.

[0052] This allows the reception site to know the delivery status of the return gifts that it has handled, and can respond to inquiries from donors regarding the delivery of return gifts, for example. On the other hand, since it is not possible to view the delivery status of records that do not match the reception site ID, access to unrelated delivery status information can be restricted. In addition, users of terminals within the hometown tax payment support system 10 can also check the delivery status of the return gift on a management screen, etc.

[0053] Similar to the reception site, delivery status information may be made available to local governments, gift providers, or donors.

[0054] [Modification of the above embodiment: Return gift provision management function] Next, a modified example of the above embodiment will be described with reference to Figures 10 to 12. In Figure 10, a return gift provider device 50 is connected to a computer network N. The return gift provider device 50 is a computer system used by a person who directly provides a return gift to a donor (a return gift provider), and is equipped with a processor, a storage device, an input device, an output device, and a communication device as basic computer elements. The operation of each element is the same as in the above embodiment.

[0055] In this embodiment, the hometown tax payment support system 10 has a function for managing the provision of return gifts. The function for managing the provision of return gifts is a function that enables a store or other provider of return gifts to provide the return gifts directly to the donor on-site. A "return gift provider" refers to an entity that directly provides food, lodging, entertainment, products, etc., as return gifts to the donor on-site, such as a restaurant, accommodation facility, entertainment facility, or shop. Return gifts provided on-site are hereinafter referred to as "locally provided items."

[0056] Furthermore, in addition to the database of the above embodiment, the hometown tax payment support system 10 is configured to store the records shown in Fig. 11 and Fig. 12 in a storage device. Fig. 11 is a personal information record (information unique to each donation) linking a donation ID with personal information such as the donor's address, name, and email address. Fig. 12 is a product name record linking a return gift ID with the name of the return gift.

[0057] When an application for hometown tax donation is made in which a locally provided product is used as a return gift, the hometown tax donation support system 10 records a donation management record (information unique to each donation) as follows, based on the linking information received from the donor device 20 or the reception site system 30.

[0058] When recording the donation ID, the link between the donation ID and the personal information of the donor is recorded in the personal information record of FIG. 11. When recording the return gift ID, the link between the return gift ID and the name of the return gift is recorded in the item name record of FIG. 12. The return gift provider ID is recorded in "return gift delivery address." The return gift shipping fee is recorded as 0 yen. The other configurations are the same as the previously described embodiment.

[0059] [Issuance of donation details information] When the hometown tax payment support system 10 accepts a donation in which a locally provided product is a return gift from the donor device 20, it reads out the donation ID of the donation and part of the information of the donation management record, personal information record, or product name record linked to the donation ID as donation details information, and transmits it to the donor device 20. The donor device 20 prints out the donation details information received from the hometown tax payment support system 10 from a printer installed in advance and allows the donor to obtain it.

[0060] Alternatively, when the hometown tax payment support system 10 receives a donation from the donor device 20 or the reception site system 30 in which a locally provided product is a return gift, the system reads out the donation ID of the donation and part of the information of the donation management record, personal information record, or product name record linked to the donation ID as donation details information, and transmits it to the donor device 20. The transmission method may be on-demand or email transmission. The email address is read from the personal information record and used. The donor device 20 displays the donation details information received from the hometown tax payment support system 10 on the display device of the donor device 20. The donation details information may include a code such as a two-dimensional code that encrypts the donation details information. In addition, the donor may print out the donation details information displayed on the donor device 20 from a printing device connected to the donor device 20.

[0061] [Provider device management screen] When providing the local item to the donor, the return item provider device 50 transmits a provider ID to the hometown tax payment support system 10. The provider ID may be the login ID of the donor or a unique identifier of the provider device 50. The hometown tax payment support system 10, which receives the provider ID from the provider device 50, reads one or more records in which the same provider ID as the received provider ID is registered as the return item delivery destination from the donation management record, and further reads the personal information of the donor and the name of the return item linked to the read donation ID from the personal information record and the name record. The hometown tax payment support system 10 then forms the read registration information into a list and transmits it to the provider device 50 to display it on the management screen of the provider device 50. The displayed registration information includes the address, name, etc. of the donor who receives the local item. It may also include information corresponding to a two-dimensional code obtained by encrypting part of the registration information.

[0062] [Providing gifts: manual identity verification] The provider of the local items will provide the local items to the donors after verifying their identity using the following method. (1) The donor will confirm the personal information of the visiting donor either verbally or by checking a printed copy or screen display of the donation details information brought by the donor, and if any of the registration information matches the registration information displayed on the management screen of the donor device 50, he / she will confirm that the donor is the actual donor. (2) The donor verifies the personal information of the visiting donor using identification such as a driver’s license brought by the donor, and if the registration information matches the registration information displayed on the management screen of the donor device 50, the donor confirms that the donor is the actual donor.

[0063] [Providing gifts: identity verification by computer] In addition, the provider of the local item may provide the local item to the donor after verifying the identity of the visiting donor by the following method. (3) The donor displays a code such as a two-dimensional code on the screen by selecting a link contained in an email or the like containing donation detail information displayed on the donor device 20. The donor of the local item operates the donor device 50 to read the code presented by the donor with a scanner. A two-dimensional code or other code displayed on a printed material brought by the donor may also be read with a scanner. The donor device 50 searches for registered information matching the code read with the scanner among the information displayed on the management screen of the donor device 50, and if matching registered information is found, it is determined that the donor is the actual donor. (4) Alternatively, the donor device 50 inquires of the hometown tax payment support system 10 about registration information that matches the code read by the scanner. The hometown tax payment support system 10, upon receiving the inquiry, searches for matching registration information in the donation management record, personal information record, and item name record, and upon finding matching registration information, notifies the inquiring donor device 50 of the match. Upon receiving this notification of match from the hometown tax payment support system 10, the donor device 50 determines that the donor is the donor himself / herself.

[0064] [Providing gifts: Clearing process] The donor device 50 associates the donation ID with the "already provided" status of the local donation for the record with matching registration information, and transmits it to the hometown tax payment support system 10. The hometown tax payment support system 10, which receives this, updates the value of the return gift delivery destination of the donation management record with the matching donation ID to "already provided." This prevents the same record from being resent to the donor device 50. Alternatively, when the hometown tax donation support system 10 receives an inquiry about the above-mentioned registered information from the donor device 50, it may update the value of the return gift delivery destination in the donation management record that has been confirmed to match the registered information to "already provided."

[0065] According to the above-described modified example, it is possible to provide gifts in return for hometown tax donations directly at the local site, and it is also possible for donors to receive the gifts on the same day they made their donation. For example, it is possible to make a donation at a restaurant and then immediately eat and drink at the restaurant as a gift in return, to make a donation at a lodging facility and then immediately stay at the lodging facility as a gift in return, to make a donation at an entertainment facility and then immediately use the entertainment facility, or to receive the gift in return directly at a store. Since there is no shipping fee for the gifts, it also leads to a reduction in the costs of collecting gifts.

[0066] Here, the scope of the present invention is the scope of the invention described in the claims, and is not limited to the above-described embodiment.

[0067] For example, in the above-mentioned embodiment, the donation application screen (search screen or viewing screen for return gifts) provided by the reception site system 30 to the donor device 20 can be narrowed down to only return gifts from a specific city, ward, town, or village. On the other hand, it is also possible to jump to another page (a page where return gifts from other cities, ward, town, or villages can be viewed) from there using a link such as a banner. However, a specific city, ward, town, or village usually does not want the return gifts from other cities, ward, town, or villages to be viewed. Therefore, the content of the page on which only return gifts from a specific city, ward, town, or village can be viewed can be configured so that it is not possible to jump to a page where return gifts from other cities, ward, town, or villages can be viewed. [Explanation of symbols]

[0068] 10 Hometown Tax Payment Support System 11 Database 20 Donor Device 30 Reception site system 40 Municipal equipment 50 Gift Provider Device 60 Delivery System N Computer Network

Claims

A donor device operated by an unspecified number of donors who make hometown tax donations, comprising: a processor of the donor device, a function of receiving an application for the donation that uses local products as return gifts, and a function of causing the donor to acquire a printed matter including the name or identifier of the local products. The donor device.

Images