Information processing method, program, and information processing device
The system allows users to make donations or tips using electronic money through compatible payment terminals, enhancing convenience and ensuring efficient donation management with incentives and emergency flexibility, addressing the lack of such functionality in existing systems.
Patent Information
- Application Number
- PCT/JP2025/002628
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-01-30
- Filing Date
- 2025-01-28
- Publication Date
- 2025-08-07
AI Technical Summary
Existing systems lack an efficient method for users to make donations or tips using electronic money through payment terminals, limiting the convenience and accessibility of charitable contributions.
A system and method that utilizes a payment terminal compatible with electronic money to accept donation or tip requests, transferring the funds to specified recipients, integrated with a server that manages user, host, and donation destination databases, allowing for easy donation management and incentives.
Enables convenient and efficient charitable contributions using electronic money, providing incentives to hosts and ensuring appropriate donation distribution, including emergency redirection if needed, while facilitating tax deductions for users.
Smart Images

Figure JP2025002628_07082025_PF_FP_ABST
Abstract
Description
Information processing method, program, and information processing device
[0001] The present invention relates to an information processing method, a program, and an information processing device.
[0002] There are systems that support users in making donations. For example, Patent Document 1 discloses a fee calculation device that calculates the amount billed to a user by adding a donation to the usage fee for a mobile phone or the like.
[0003] Japanese Patent Application Laid-Open No. 2009-75905
[0004] In one aspect, an object of the present invention is to provide an information processing method and the like that allows donations or tips to be made using a payment terminal that supports electronic money.
[0005] In one aspect, the information processing method involves a computer executing a process to accept a request for payment of a donation using electronic money via a payment terminal compatible with electronic money, and to transfer the donation to a specified donation destination.
[0006] In one aspect, the information processing method involves a computer performing a process to accept a payment request for a donation or tip using electronic money via a payment terminal compatible with electronic money, and to transfer the donation or tip to a specified donation recipient or tip recipient.
[0007] In one aspect, donations or tips can be made using a payment terminal that accepts electronic money.
[0008] 1 is an explanatory diagram showing an example of the configuration of a donation system. FIG. 1 is a block diagram showing an example of the configuration of a server. FIG. 2 is a diagram showing an example of the record layout of a user DB, a host DB, a payment terminal DB, and a donation destination DB. FIG. 3 is a diagram showing an example of the record layout of a donation program DB and a donation history DB. FIG. 4 is a diagram showing the flow of donations. FIG. 5 is a diagram showing an example of a payment terminal. FIG. 6 is a diagram showing another example of a payment terminal. FIG. 7 is a diagram showing another example of a display screen of a payment terminal. FIG. 8 is a diagram showing an example of a user screen. FIG. 9 is a diagram showing an example of a user screen. FIG. 10 is a diagram showing an example of a user screen. FIG. 11 is a diagram showing an example of a user screen. FIG. 12 is a diagram showing an example of a donation destination screen. FIG. 13 is a diagram showing an example of a donation destination screen. FIG. 14 is a diagram showing an example of a donation destination screen. FIG. 15 is a diagram showing an example of a host screen. FIG. 16 is a diagram showing an example of a host screen. FIG. 17 is a flowchart showing an example of a processing procedure executed by a server. FIG. 18 is an example of a screen displayed by the payment terminal after a donation has been settled. FIG. 19 is an example of a screen displayed by the payment terminal after a donation has been settled.
[0009] The present invention will be described in detail below with reference to the drawings showing embodiments thereof. (Embodiment) Fig. 1 is an explanatory diagram showing an example of the configuration of a donation system. In this embodiment, a donation system will be described that accepts donations in electronic money when payment for the purchase of a product or service is made in electronic money using a payment terminal 3 that supports electronic money. The donation system includes an information processing device 1, a user terminal 2, a payment terminal 3, a host terminal 4, and a donation recipient terminal 5. Each device is communicatively connected via a network N such as the Internet.
[0010] In this specification, "electronic money" may include not only prepaid store-value types, but also postpaid types, prepaid cards that allow you to pay a certain amount in advance and then enter a code number issued in exchange for that amount to make a payment, as well as payment methods such as credit cards. In other words, "electronic money" can be any electronic payment method, and the specific payment method is not particularly important.
[0011] The information processing device 1 is an information processing device capable of various information processing and sending and receiving information, such as a server computer or a personal computer. In this embodiment, the information processing device 1 is assumed to be a server computer, and for simplicity, will be referred to as server 1 below. The server 1 accepts a donation payment request using electronic money via a payment terminal 3 that supports electronic money. When the donation payment request is accepted, the server 1 executes a process to remit the donation to a specified donation destination.
[0012] The user terminal 2 is a terminal device carried by a user making a donation, and is, for example, a mobile terminal such as a smartphone, a tablet terminal, etc. For example, the user performs a screen display or payment process using electronic money, which will be described later, via the user terminal 2.
[0013] It should be noted that payment by electronic money is not limited to payment by the user terminal 2 (mobile terminal), but may be made using other media such as an IC card or credit card.
[0014] The payment terminal 3 is a terminal that accepts payments using electronic money. There is no particular limitation on the location where the payment terminal 3 is installed, but for example, the payment terminal 3 is installed in a store, a commercial facility, a taxi, etc.
[0015] In the following explanation, the installer of the store or the like that has installed the payment terminal 3 will be referred to as the "host." Note that in the following explanation, the "host" will be described as being different from the donation recipient, but the "host" that installs the payment terminal 3 may be the same as the donation recipient.
[0016] The host terminal 4 is a terminal device used by the host who installs the payment terminal 3, and is, for example, a personal computer, smartphone, tablet terminal, etc. As will be described later, the host registers the payment terminal 3 in the system in advance, enabling donations via the payment terminal 3.
[0017] The donation recipient terminal 5 is a terminal device used by the charity organization that is the donation recipient, and is, for example, a personal computer, smartphone, tablet terminal, etc. As will be described later, the charity organization registers the donation program that it implements in this system and accepts donations from users.
[0018] In this embodiment, the donation recipient is assumed to be an organization (corporation), but the donation recipient may also be an individual.
[0019] 2 is a block diagram showing an example configuration of the server 1. The server 1 includes a control unit 11, a main memory unit 12, a communication unit 13, and an auxiliary memory unit 14. The control unit 11 has one or more arithmetic processing devices such as a central processing unit (CPU), a micro-processing unit (MPU), or a graphics processing unit (GPU), and performs various information processing, control processing, and the like by reading and executing a program P stored in the auxiliary memory unit 14. The main memory unit 12 is a temporary storage area such as a static random access memory (SRAM) or a dynamic random access memory (DRAM), and temporarily stores data necessary for the control unit 11 to execute arithmetic processing. The communication unit 13 is a communication module for performing communication-related processing and transmits and receives information to and from the outside.
[0020] The auxiliary memory unit 14 is a non-volatile storage area such as a large-capacity memory or a hard disk, and stores a program P (program product) and other data necessary for the control unit 11 to execute processing. The auxiliary memory unit 14 also stores a user DB 141, a host DB 142, a payment terminal DB 143, a donation destination DB 144, a donation program DB 145, and a donation history DB 146. The user DB 141 is a database that stores information about each user. The host DB 142 is a database that stores information about each host. The payment terminal DB 143 is a database that stores information about each payment terminal 3. The donation destination DB 144 is a database that stores information about each charity organization that is a donation destination. The donation program DB 145 is a database that stores information about each donation program implemented by the charity organization. The donation history DB 146 is a database that stores donation histories by users.
[0021] The auxiliary storage unit 14 may be an external storage device connected to the server 1. The server 1 may be a multi-computer consisting of multiple computers, or may be a virtual machine virtually constructed by software.
[0022] Furthermore, in this embodiment, the server 1 is not limited to the above configuration, and may include, for example, an input unit that accepts operation input, a display unit that displays images, etc. Furthermore, the server 1 may be provided with a reading unit that reads a portable storage medium 1a such as a CD (Compact Disk)-ROM or a DVD (Digital Versatile Disc)-ROM, and may read and execute the program P from the portable storage medium 1a.
[0023] FIG. 3 is a diagram showing an example of the record layout of user DB 141, host DB 142, payment terminal DB 143, and donation destination DB 144.
[0024] The user DB 141 includes a user ID column, a name column, an address column, an email column, a phone number column, and a link key column. The user ID column stores a user ID, which is an identifier for each user. The name column, address column, email column, phone number column, and link key column each store, in association with the user ID, the user's name, address, email address, phone number, and key information for linking electronic money to the system.
[0025] The host DB 142 includes a host ID column, a host name column, an industry column, a type column, a corporation number column, and a host information column. The host ID column stores a host ID, which is an identifier for each host. The host name column, industry column, type column, corporation number column, and host information column each store, in association with the host ID, the host name, the host's industry, the type indicating a corporation or individual, the corporation number, and other host information (for example, the host's representative name, the name of the person in charge, and an email address).
[0026] The payment terminal DB 143 includes a terminal ID column, a host ID column, a terminal name column, and a terminal information column. The terminal ID column stores a terminal ID, which is an identifier for each payment terminal 3. The host ID column, terminal name column, and terminal information column each store, in association with the terminal ID, the host ID of the host on which the payment terminal 3 is installed, the name of the payment terminal 3, and other terminal information (e.g., the model number of the payment terminal 3, the start date of use, the last date of use, etc.).
[0027] Donation recipient DB144 includes an organization ID column, an organization name column, a corporate number column, and a donation recipient information column. The organization ID column stores an organization ID, which is an identifier for each charity that is a donation recipient. The organization name column, corporate number column, and donation recipient information column each store the name of the charity, its corporate number, and other donation recipient information (e.g., the name of the charity's representative, the name of the person in charge, email address, etc.) in association with the organization ID.
[0028] FIG. 4 is a diagram showing an example of the record layout of the donation program DB 145 and the donation history DB 146. As shown in FIG.
[0029] The donation program DB 145 includes a program ID column, an organization ID column, a category column, a program name column, a program information column, a deduction column, a donation amount column, an expiration date column, and an emergency column. The program ID column stores a program ID column that is an identifier for each donation program. The organization ID column, category column, program name column, program information column, deduction column, donation amount column, expiration date column, and emergency column each store, in association with the program ID column, the organization ID of the charitable organization implementing the donation program, the donation program category, the program name, other program information (e.g., description, image, audio, etc. to be output as donation recipient information), whether the donation program is eligible for donation deductions, the donation amount accepted from the user (e.g., initial display amount, minimum amount, maximum amount, etc.), the expiration date of the donation program, and whether a change to the donation recipient is permitted when a specific emergency occurs.
[0030] The donation history DB 146 includes a donation ID column, a program ID column, a terminal ID column, a user ID column, a donation amount column, a payment provider ID column, a host incentive column, a donation date and time column, a cancellation date and time column, a receipt column, and a status column. The donation ID column stores a donation ID, which is an identifier for each donation made by a user. The program ID column, terminal ID column, user ID column, donation amount column, payment provider ID column, host incentive column, donation date and time column, cancellation date and time column, receipt column, and status column store, in association with the donation ID, the program ID of the donation program to which the user donated, the terminal ID of the payment terminal 3 that accepted the donation, the user ID of the user who made the donation, the donation amount, a payment provider ID that is an identifier for the payment provider that handles the payment of the electronic money used by the user, the amount of the incentive paid to the host with the donation, the donation date and time, the cancellation date and time if the donation was canceled, the issuance date and number of receipts if issued, and whether the remittance was completed.
[0031] 5 is a diagram showing the flow of donations. The donation program implemented in this embodiment will be described with reference to FIG.
[0032] As described above, in this embodiment, a user can make a donation using electronic money at the payment terminal 3 installed in the host store, etc. For example, a user can make a donation when paying for a product or service using electronic money.
[0033] Donations are paid to the operator (platform) of this system. The operator keeps a portion of the donations as sales, and the remaining donations are paid to the charity. In this way, the charity pays the donations to the final beneficiary.
[0034] The reason for placing a charity between the operator (platform) of this system and the final beneficiary is that the charity can review the appropriateness of the donation to the final beneficiary, allowing for the optimal selection of the final recipient of the donation. Also, because whether a donation is eligible for tax deductions is determined by the charity, not the final beneficiary, having a charity eligible for tax deductions intervene has the advantage of making it easier for users to receive tax deductions.
[0035] It is not necessary to have a charity organization intervene between the operator of this system and the ultimate beneficiary.
[0036] The operator pays a portion of the sales as a payment fee to a payment provider (payment agent) that offers electronic money as a payment method, and also pays a portion of the sales to the host as an incentive for cooperating with the donation program.
[0037] In this way, users can make donations using the highly convenient payment method of electronic money, while hosts can earn income as an incentive, thereby encouraging donations to charitable organizations.
[0038] The present embodiment will be outlined below with reference to FIGS.
[0039] Fig. 6 is a diagram showing an example of a payment terminal 3. Fig. 6 illustrates the appearance of a general-purpose mobile terminal (smartphone, tablet terminal, etc.) used as the payment terminal 3. As shown in Fig. 6, a reader device 31 that accepts payments is connected to the payment terminal 3, and payments using electronic money are accepted via the reader device 31.
[0040] Note that, since many mobile terminals (smartphones, etc.) have a function for accepting touch payments, etc., payments may be accepted using an internal reader function without providing an external reader device 31. In other words, the reader device 31 may be integrated with the payment terminal 3.
[0041] When accepting a donation from a user, the payment terminal 3 displays the screen shown in Fig. 6. This screen displays donation recipient information and the donation amount. The user terminal 2 displays an image, logo, description, etc. of the donation recipient (charity organization) as donation recipient information. In addition, the user terminal 2 displays as donation recipient information whether the donation is eligible for a tax deduction.
[0042] The screen also includes a donation amount display field 61 and multiplier change buttons 62, 62, 62. The donation amount display field 61 is a display field that displays the donation amount. Initially, the donation amount display field 61 displays the donation amount (hereinafter referred to as the "displayed amount") set by the host or the charity organization, as will be described later. The multiplier change button 62 is a button for changing the multiplier of the donation amount. When an operation input to the multiplier change button 62 is received, the donation amount is set to the amount obtained by multiplying the displayed amount by the selected multiplier.
[0043] In the above example, the donation amount is set by changing the donation amount multiplier, but it is also possible to change the donation amount by providing, for example, plus and minus buttons, or to set the donation amount by directly entering a number.
[0044] In addition, in this embodiment, donation recipient information and a magnification change button 62, etc. are displayed on the payment terminal 3, allowing the user to check the donation recipient information and change the donation amount, but the payment terminal 3 only needs to display the donation amount at a minimum, and does not need to display anything else.
[0045] At the time of payment, the user checks the displayed amount, changes the multiplier, and then performs payment processing using the user terminal 2 (or using other media such as an IC card) with the payment terminal 3. When payment is completed, the payment terminal 3 outputs a predetermined voice (thank you voice) that is set for each donation program.
[0046] It is preferable that the payment terminal 3 outputs different sounds depending on the number of times that it has accepted donations (donation payment requests) from users. For example, when the server 1 accepts a payment request from a user via the payment terminal 3, it refers to the donation history DB 146 and counts the number of donations made by the user. The server 1 then selects and outputs a sound corresponding to the number of donations from a plurality of pre-prepared sounds. It is also possible, for example, for the server 1 to randomly select and output a sound from the plurality of sounds. By changing the sound each time a donation is accepted, it is possible to provide users with an incentive to cooperate with the donation program.
[0047] In this embodiment, audio is output after payment, but instead of or in addition to audio, an image (still image or video), text, etc. may be displayed (see also Variant Example 1 described below).
[0048] Fig. 7 is a diagram showing another example of the payment terminal 3. Fig. 7 shows the appearance of a terminal dedicated to payment as the payment terminal 3.
[0049] 6 except that it does not display an image or description of the charity organization, but displays the donation amount (displayed amount) and whether the donation is tax deductible. Payment terminal 3 also has multiplier change buttons 71, 71, 71, and when operation input is received on multiplier change button 71, the payment terminal 3 receives a donation amount equal to the displayed amount multiplied by the changed multiplier.
[0050] The payment terminal 3 may be configured to only display the donation amount and not include the rate change button 71.
[0051] Figure 8 is a diagram showing another example of the display screen of the payment terminal 3. The payment terminal 3 is not limited to a payment terminal dedicated to electronic money as exemplified in Figure 7, but may also be a POS (Point of Sale) register or the like. Figure 8 shows an example of the display screen when the payment terminal 3 is a POS register.
[0052] The display screen shown in Figure 8 includes total amount selection buttons 81, 81, 81. The total amount selection button 81 is a button for selecting the total amount of the purchase price of the product or service and the donation. When an operation input to the total amount selection button 81 is accepted, the payment terminal 3 accepts payment of the selected total amount.
[0053] Specifically, by changing the donation amount, the payment terminal 3 displays multiple total amounts, rounded up to a predetermined digit (ones, tens, and hundreds), on the total amount selection buttons 81, 81, and accepts the selection of the total amount. For example, if the purchase price of a product is "183 yen," by changing the donation amount to "7 yen," "17 yen," and "817 yen," respectively, the total amounts will be rounded up to "190 yen," "200 yen," and "1,000 yen," and displayed on the total amount selection button 81. This allows donations to be made in the same way as donating change.
[0054] The above donation amount setting is an example, and it is also possible to donate a fixed amount, such as "10 yen" or "100 yen."
[0055] 9A to 10B are diagrams showing examples of user screens, which the user can view and operate.
[0056] As shown in FIG. 9A, the user terminal 2 accepts input to set (select) electronic money to be linked with this system. As already mentioned, the electronic money is not limited to that provided by the user terminal 2, and IC cards, credit cards, etc. may also be linked. When electronic money linking is set up, the user terminal 2 can display a list of donations made by the user (donation history). For example, as shown in FIG. 9B, the user terminal 2 displays the date and time of the donation, the name of the charity organization to which the donation was made, the name of the donation program, etc. in a table format.
[0057] For example, the user terminal 2 may be configured to allow the user to download, as a bonus, the donation program to which the user has donated, or digital content (images, audio, etc.) or coupons corresponding to the donation itself, via a donation list screen such as that shown in Fig. 9B. When a donation (a donation settlement request) is received from a user, a bonus may be granted to the user, thereby providing the user with an incentive to cooperate with the donation program.
[0058] In the above description, some kind of electronic item (image, sound, coupon, etc.) is given to the user as a benefit, but the benefit is not limited to an electronic item, and a physical item may also be given to the user.
[0059] 10A and 10B, the user terminal 2 can change account settings. Specifically, as shown in Fig. 10A, the user terminal 2 displays a screen for changing (editing) the receipt delivery address (described later) and accepts the setting change. As shown in Fig. 10B, the user terminal 2 displays a screen for changing the linked electronic money and accepts the setting change.
[0060] 11A to 12B are diagrams showing examples of donation recipient screens, which can be viewed and operated by charitable organizations that are donation recipients.
[0061] As shown in Fig. 11A, the donation recipient terminal 5 displays a list of donations received from each user (donation history). The donation recipient terminal 5 displays the date and time the donation was received, the donation amount, the name of the donation program, etc. in a table format. Also, as shown in Fig. 11B, the donation recipient terminal 5 displays a screen for changing account settings and accepts changes to account settings (such as name, address, and email address).
[0062] 12A, the donation recipient terminal 5 displays a list of donation programs that accept donations. The donation recipient terminal 5 displays the donation program name, whether the donation is tax deductible, category, etc. in a table format.
[0063] When an operation input for "New Addition" is received on the screen of Fig. 12A, the donation recipient terminal 5 transitions to the screen shown in Fig. 12B and accepts the new registration (new addition) of a donation program. Specifically, as shown in Fig. 12B, the donation recipient terminal 5 accepts setting inputs such as the donation program name, category, description, image, whether or not it is tax deductible, donation amount (displayed amount, multiplier, etc.). Note that this screen may also allow settings such as the sound to be output after the donation is settled.
[0064] The donation recipient terminal 5 also accepts a setting input for "emergency overwrite" to determine whether or not to allow a change in the donation recipient in the event of a specific emergency. A specific emergency is, for example, a natural disaster. In this system, in the event of an emergency such as a natural disaster, the donation is made by changing the donation recipient from the original one to another.
[0065] It is preferable to charge a fee if "emergency overwriting" is not permitted. This allows donations to be made in an appropriate manner when an emergency occurs.
[0066] 13A to 14 are diagrams showing examples of host screens, which the host can view and operate.
[0067] As shown in Fig. 13A, the host terminal 4 accepts input for setting up an account (host name, business type, type of business, corporate or individual, etc.). Also, as shown in Fig. 13B, the host terminal 4 displays a list of payment terminals 3 installed by the host.
[0068] When an operation input for "New Addition" is received on the screen of Fig. 13B, the host terminal 4 transitions to the screen shown in Fig. 14 and receives new registration (new addition) of the payment terminal 3. Specifically, as shown in Fig. 14, the host terminal 4 receives setting inputs such as the terminal ID, name, and model number of the payment terminal 3, the donation program for receiving donations at the payment terminal 3, and the donation amount. In addition, the host terminal 4 receives setting inputs for "Emergency Overwrite" as to whether or not to allow a change in the donation destination when a specific emergency occurs.
[0069] As described above, the host terminal 4 accepts registration of the payment terminal 3. Information on the registered payment terminal 3 is stored in the payment terminal DB 143.
[0070] When a user pays for the purchase of a product or service using the payment terminal 3, the server 1 accepts a payment request for a donation using electronic money via the payment terminal 3. Specifically, the server 1 accepts a payment request to pay the total amount of the purchase price of the product or service and the donation using electronic money.
[0071] As shown in Figures 6 and 7, the server 1 accepts a payment to donate a displayed amount preset by the host or charity organization. Alternatively, if an input to change the donation multiplier is received, the server 1 accepts a payment to donate an amount obtained by multiplying the displayed amount by the changed multiplier. Alternatively, as shown in Figure 8, the server 1 may display on the payment terminal 3 multiple total amounts rounded up to a predetermined digit (units, tens, and hundreds), and accept a payment to pay a total amount selected by the user from among the displayed total amounts.
[0072] When a donation settlement request is received, the server 1 waits (pools) for the donation to be transferred until a predetermined transfer timing (e.g., once a month, once a day, etc.) arrives. When the transfer timing arrives, the server 1 executes a process to transfer part or all of the donation to the donation recipient associated with the settlement terminal 3. Specifically, the server 1 executes a process to transfer part of the donation to the donation recipient and also transfer part of the donation to the host as an incentive.
[0073] When a donation settlement request is received, the server 1 determines whether a specific emergency has occurred, according to settings made by the operator. If it is determined that a specific emergency has occurred and settings have been made to allow a change in the donation destination when an emergency occurs, the server 1 executes a process to transfer the donation to a different donation destination instead of the donation destination associated with the payment terminal 3.
[0074] Through the above process, the donation is sent to the charity organization to which it was donated.
[0075] In this embodiment, donations are pooled until a predetermined remittance timing arrives, but remittance may be made each time a donation payment request is received at the payment terminal 3.
[0076] In this system, a donation can be canceled at the user's request up until the time the donation transfer is completed. When a donation cancellation request is received from the user terminal 2, the server 1 cancels the donation transfer. The donation whose transfer is canceled is refunded to the user.
[0077] In this embodiment, donations can be cancelled, but donations may not be cancelled. Also, the host or the donation recipient may be able to set whether or not to allow donation cancellation.
[0078] In addition, in response to a request from a user, the operator of this system issues (outputs) a receipt for the donation. When a request is received from the user terminal 2, for example, the server 1 sends electronic data of the receipt to the user's email address. This allows the user to obtain the receipt necessary to receive a donation deduction.
[0079] In this embodiment, a receipt is issued in response to a request from the user, but it may also be automatically issued when a donation is made. In addition, in this embodiment, a receipt is sent by means of e-mail or the like, but as in Variation 1 described below, a QR code (registered trademark) may be displayed on the payment terminal 3 after the donation payment has been made, so that the receipt can be obtained.
[0080] As described above, according to this embodiment, when shopping for merchandise at a host store or the like, donations can be easily made using electronic money.
[0081] 15 is a flowchart showing an example of a processing procedure executed by the server 1. The processing executed by the server 1 when a user makes a donation will be described with reference to FIG. 15. When the user terminal 2 makes a payment via the payment terminal 3, the control unit 11 of the server 1 outputs donation destination information regarding the donation destination associated with the payment terminal 3 to the user terminal 2 and displays it on the app screen (step S11). The donation destination information includes an image, description, etc. of the donation program, as well as whether the donation is eligible for tax deduction.
[0082] The control unit 11 accepts a payment request via the payment terminal 3 to pay the total amount of the purchase price of the product or service and the donation using electronic money (step S12). For example, as shown in Figures 6 and 7, the control unit 11 accepts payments to pay a preset displayed amount as a donation, as well as payments to pay an amount obtained by multiplying the displayed amount by the changed multiplier when an input to change the donation multiplier is received. Alternatively, as shown in Figure 8, the control unit 11 displays multiple total amounts on the payment terminal 3 with fractions rounded up to a predetermined digit (units, tens, and hundreds), and accepts payments to pay a total amount selected by the user from among the displayed total amounts.
[0083] The control unit 11 executes a process to transfer part or all of the donation to a predetermined donation destination (step S13). Specifically, the control unit 11 executes a process to transfer part of the donation to the donation destination associated with the payment terminal 3, and also to transfer part of the donation to the host (installer) who installed the payment terminal 3. In this case, the control unit 11 determines whether a specific emergency has occurred. If it is determined that a specific emergency has occurred and the host has set up a system to allow the donation destination to be changed in the event of an emergency, the control unit 11 executes a process to transfer the donation to a donation destination other than the donation destination associated with the payment terminal 3.
[0084] The control unit 11 accepts a donation cancellation request between the time when the payment request is accepted and the time when the donation remittance is completed (step S14). If a cancellation request is accepted, the control unit 11 stops the remittance process.
[0085] The control unit 11 determines whether the remittance of the donation has been completed (step S15). If it determines that the remittance has not been completed (S15: NO), the control unit 11 returns the process to step S14.
[0086] If it is determined that the remittance is complete (S15: YES), the control unit 11 outputs (issues) a receipt for the donation in response to a request from the user terminal 2 (step S16). For example, the control unit 11 sends electronic data of the receipt to the user's email address by email, and outputs the receipt data to a printer (not shown) to print it. The control unit 11 then ends the series of processes.
[0087] Although the above description has been given assuming that donations are made at the same time as purchasing goods or services, the payment terminal 3 may be configured to solely accept donations and not to accept payments for purchasing goods or services. In other words, the payment terminal 3 may be a terminal dedicated to donations.
[0088] Furthermore, an application program dedicated to this system may be installed on the user terminal 2, and the donations may be settled through this application. By providing a dedicated application, it is possible to set, for example, the type of electronic money to be used for donations as a default, or to set, by default, the type of donation program to which the user gives priority (for example, "environmental protection," "animal protection," etc.).
[0089] As described above, according to this embodiment, donations can be made using electronic money by utilizing the payment terminal 3 that supports electronic money.
[0090] (Modification 1) In this modification, an example of a screen displayed by the payment terminal 3 after a donation has been paid will be disclosed.
[0091] 16A and 16B are example screens displayed by the payment terminal 3 after a donation has been made. For example, as shown in FIG. 16A, the payment terminal 3 displays current donation information (donation recipient, donation amount) and donation history (total donation amount, number of donations). The payment terminal 3 also displays a two-dimensional code such as a QR code for downloading a receipt. The receipt can be received by scanning the two-dimensional code with the user terminal 2. As shown in FIG. 16B, the payment terminal 3 displays a predetermined image (thanks image) and outputs a predetermined sound (thanks voice).
[0092] (Modification 2) In the above embodiment, the case where donations are made by electronic money has been described, but this system can also be applied to cases where tips are paid in addition to donations.
[0093] That is, the server 1 accepts a tip payment request in electronic money via the payment terminal 3 that supports electronic money, and executes a process of sending the tip to a predetermined tip recipient (for example, the host that has installed the payment terminal 3). Supporting electronic money makes it easy to pay tips, improving user convenience, etc.
[0094] The embodiments disclosed herein are illustrative in all respects and should not be considered limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims.
[0095] The matters described in each embodiment can be combined with each other. Furthermore, the independent claims and dependent claims described in the claims can be combined with each other in any combination, regardless of the reference format. Furthermore, the claims use a format in which a claim references two or more other claims (multiple claim format), but this is not limited to this. A multiple claim (multi-multi claim) that references at least one other multiple claim may also be used.
[0096] DESCRIPTION OF SYMBOLS 1 Server (information processing device) 11 Control unit 12 Main memory unit 13 Communication unit 14 Auxiliary memory unit P Program 141 User DB 142 Host DB 143 Payment terminal DB 144 Donation destination DB 145 Donation program DB 146 Donation history DB 2 User terminal 3 Payment terminal 4 Host terminal 5 Donation destination terminal
Claims
1. An information processing method in which a computer executes the process of accepting a request to make a donation by electronic money via a payment terminal that supports electronic money, and executing the process of transferring the donation to a specified donation destination.
2. The information processing method according to claim 1, wherein the payment request is accepted via the payment terminal to settle the total amount of the purchase price of the product or service and the donation amount using electronic money, and a process is executed to transfer part or all of the donation amount to the donation recipient.
3. The information processing method according to claim 2, further comprising the steps of: changing the amount of the donation, rounding up the total amount to a predetermined digit, and accepting the payment request for the total amount.
4. The information processing method according to claim 1, further comprising the step of transferring a portion of the donation to the donation recipient and transferring a portion of the donation to an installer of the payment terminal.
5. The information processing method according to claim 1, further comprising: accepting a setting input for setting the donation destination in association with the payment terminal; and executing a process for transferring the donation to the donation destination associated with the payment terminal.
6. The information processing method according to claim 5, wherein, when the payment request is received, it is determined whether a specific emergency has occurred, and if it is determined that a specific emergency has occurred, money is sent to a donation destination other than the donation destination associated with the payment terminal.
7. The information processing method according to claim 1, further comprising the step of displaying donation recipient information, including whether or not the donation is eligible for tax deduction, when the payment request is accepted.
8. The information processing method according to claim 1, further comprising outputting a receipt for the donation.
9. The information processing method according to claim 1, wherein a request to cancel the donation is accepted between the acceptance of the payment request and the completion of the donation transfer, and when the cancellation request is accepted, the donation transfer process is stopped.
10. The information processing method of claim 1, wherein when accepting the payment request, an input to change the donation multiplier is accepted, and when an input to change the donation multiplier is accepted, the payment request is accepted to pay the donation amount equal to the amount obtained by multiplying a predetermined amount by the changed multiplier.
11. The information processing method according to claim 1, wherein, when the payment request is accepted, a sound, image or text set according to the donation destination is output via the payment terminal.
12. The information processing method according to claim 11, wherein different sounds, images or text are output depending on the number of times the payment request for the donation is received from the user.
13. A program that causes a computer to execute the following process: accept a request for payment of donations using electronic money via a payment terminal that supports electronic money; and execute a process to transfer the donation to a specified donation destination.
14. An information processing device having a control unit, wherein the control unit accepts a request to settle a donation using electronic money via a payment terminal compatible with electronic money, and executes a process to transfer the donation to a specified donation destination.
15. An information processing method in which a computer executes the process of accepting a request for payment of a donation or tip using electronic money via a payment terminal compatible with electronic money, and executing the process of transferring said donation or tip to a designated donation recipient or tip recipient.
Citation Information
Patent Citations
Contribution collecting system and method
JP2007041685A
A system and method for managing the generation, collection, and distribution of donations through the use of payment cards.
JP2011520196A
Provision device, provision method and provision program
JP2022015261A
Sports team donation reward provision system, sports team donation reward provision method, and program
JP2022155539A
Settlement device, settlement method, program and settlement system
JP2023097337A