Information processing device, information processing method, and program

The information processing device automates and schedules tax donations to enhance user convenience in tax return systems, addressing the lack of convenience in conventional systems.

JP2025138520APending Publication Date: 2025-09-25PAYPAY CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2024037661
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-03-11
Publication Date
2025-09-25

AI Technical Summary

Technical Problem

Conventional tax return systems do not prioritize user convenience.

Method used

An information processing device and method that includes an acquisition unit to instruct users to make a donation to a local government after a predetermined period and a control unit to process the donation accordingly, enhancing user convenience through automated and scheduled tax payment services.

Benefits of technology

Provides a highly convenient tax payment service by automating and scheduling donations, improving user experience and efficiency in tax return processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025138520000001_ABST
    Figure 2025138520000001_ABST
Patent Text Reader

Abstract

To increase user's convenience.SOLUTION: An information processing device includes an acquisition unit and a control unit. The acquisition unit obtains information on the user's instruction to donate after the predetermined period when a user performs the operation for the instruction on an interface screen for inquiring whether to make a donation to the municipality after the predetermined period, the screen being displayed according to information related to operation by the user to make a donation to the municipality. The control unit performs processing for making a donation to the municipality after the predetermined period, based on the information related to the operation for the instruction.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

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

[0002] Conventionally, a device has been disclosed that assists users who have made hometown tax payments using a hometown tax payment service to create tax return data related to the hometown tax payment (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2018-67246 Summary of the Invention [Problem to be solved by the invention]

[0004] Conventional technologies have considered tax returns, but have not always considered the convenience of the service for users.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide an information processing device, an information processing method, and a program that can provide a service that is highly convenient for users. [Means for solving the problem]

[0006] One aspect of the present invention is an information processing device that includes an acquisition unit that acquires information about the operation of instructing a user to make a donation to a local government after a predetermined period of time on an interface screen that inquires whether the user will make a donation to the local government after the predetermined period of time, when the user performs an operation to instruct the user to make a donation to the local government after the predetermined period of time, and a control unit that performs processing to make a donation to the local government after the predetermined period of time based on the information about the operation of instructing the user. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide an information processing device, an information processing method, and a program that can provide a service that is highly convenient for users. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of an electronic payment system in which an electronic payment service is realized. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100 according to the first embodiment. [Figure 5] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 10 is a diagram showing another example of an interface screen. [Figure 8] FIG. 10 is a diagram showing another example of an interface screen. [Figure 9] FIG. 10 is a diagram showing an example of the contents of setting information 180. [Figure 10] 2 is a sequence diagram showing an example of the flow of processing executed by the user terminal device 10, the payment server 100, and the service server 200. FIG. [Figure 11] 10 is a flowchart showing an example of the flow of processing executed by the payment server 100. [Figure 12] 10 is a flowchart showing an example of the flow of processing executed by the payment server 100. [Figure 13] FIG. 10 is a diagram showing an example of the contents of income information 190. [Figure 14] 10 is a flowchart showing an example of the flow of processing executed by the payment server 100 using the income information 190. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, with reference to the drawings, embodiments of an information processing system, an information processing method, and a program according to the present invention will be described. The various devices and servers described below, which provide services to users and perform internal analysis, may be implemented as a distributed group of devices, and each device may be operated by a different business. Furthermore, the hardware owner (the cloud server provider) and the business that actually operates the device may also be different. An application program and a payment server work together to provide an electronic payment service. In the following description, the application program is referred to as a payment app. An electronic payment service is a service that supports payments for the purchase of goods and services at a store. A store is, for example, a physical store (real-world store) existing in real space, but may also include a virtual store for e-commerce transactions. Virtual stores may also include stores operated by entities other than the operator of the electronic payment service. In such cases, when making a payment for a purchase at a virtual store, the user is controlled to transition to an interface screen for the electronic payment service. In an electronic payment service, a store is treated as belonging to, for example, a member store (brand), and when a purchase is made at a store, processing such as payment is primarily conducted between the user and the member store. Alternatively, processing such as payment may be conducted between the user and the store.

[0010] [Electronic payment service] Figure 2 shows an example of the configuration of an electronic payment system in which an electronic payment service is realized. The electronic payment service is realized mainly by a payment server 100. The electronic payment system that realizes the electronic payment service includes, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, the payment server 100, and a service server 200. These devices communicate via, for example, a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, etc.

[0011] Some or all of the functional configuration included in the electronic payment system may be distributed across multiple devices in any form, or may be integrated into any device. For example, some or all of the functional configuration of the payment server 100 may be included in the service server 200, or some or all of the functional configuration of the service server 200 may be included in the payment server 100. The payment server 100 or the service server 200 is an example of an "information processing device." The combined functional configuration of the payment server 100 and the service server 200 may also be an "information processing device."

[0012] [User terminal device] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment app 20, which operates in cooperation with the payment server 100 to provide electronic payment services to users. The payment app 20 is installed on the user terminal device 10 from, for example, an application store, and controls the camera, communication device, touch panel, etc.

[0013] The user terminal device 10 has installed thereon, for example, a service app 30. The service app 30 is, for example, a mini app included in the payment app 20. When the payment app 20 is downloaded to the user terminal device 10, the mini app included in the payment app 20 is also downloaded to the user terminal device 10. The service app 30 cooperates with the service server 200 (an API; Application Programming Interface provided by the service server 200) to display content provided by the service server 200 on the display unit of the user terminal device 10. The service app 30 may be omitted, and the payment app 20 may have the functional configuration of the service app 30.

[0014] [Service Server] The service server 200 cooperates with the service application 30 to provide a service to a user. The service is, for example, a service related to hometown tax donations. For example, the service server 200 performs processing for making a donation to a designated local government and arranges for a return gift based on instructions from the service application 30 or the payment server 100. The processing for making a donation involves, for example, providing information about the donation to a server managed by the local government and instructing it to expedite the donation processing. For example, the service server 200 provides information about the user who made the donation to the local government, and arranges for the return gift to be delivered to an address specified by the user.

[0015] The return gift may be any item, such as agricultural produce such as vegetables, other local specialties, or industrial products, or it may be an electronic voucher (electronic gift certificate) that can be used at a designated store in the target municipality. An electronic voucher is a voucher that can be used at a designated store using the payment app 20. For example, it is preferable that the return gift be an electronic voucher. Agricultural produce has a short expiration date, and people may get tired of buying the same agricultural produce every year. In contrast, electronic vouchers can be used for a relatively long period, such as one or two years, and can be used at a variety of stores. For this reason, it is more preferable that the return gift be an electronic voucher.

[0016] [First store terminal device] The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device. The store code image 60 is placed in the store and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0017] [Second store terminal device] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, tablet terminal, personal computer, etc. An interface for affiliated stores 72 runs on the second store terminal device 70. The interface for affiliated stores 72 may be an app for affiliated stores or a browser. The interface for affiliated stores 72 accepts coupon settings and the like from the operator of the affiliated store and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image and reading the code image displayed by the user terminal device 10 by executing the app for affiliated stores.

[0018] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, this distinction will not be made and it is assumed that payment information is sent from the first store terminal device 50.

[0019] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns for electronic payment: Pattern 1 and Pattern 2.

[0020] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10, with the payment application 20 running, decodes the store code image 60 using its optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is the domain of the electronic payment service to which store identification information has been added, and is associated with an affiliated store ID, store ID, etc. in the payment server 100 (described below). The payment application 20 sends first payment information including the store URL and account ID to the payment server 100 (S2). The payment server 100 searches for store information (described below) using the affiliated store ID and store ID corresponding to the store URL, acquires the affiliated store name and store name information (S3), and sends this to the payment application 20 (S4). The user enters the payment amount into the user terminal device 10 on the screen displaying the affiliated store name and store name (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount and sends it to the payment server 100 (S6). The payment server 100 makes the electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notice (information for displaying a payment completion screen) to the payment app 20 (S8), and the payment app 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include information on the payment amount in addition to the store URL. In this case, the step of the user inputting the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0021] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, the payment app 20 sends a request to issue a one-time code to the payment server 100 when the payment app 20 is launched, when a payment operation is performed in the payment app 20, at the automatic update timing (e.g., every minute), and at other timings (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image, such as a QR code or barcode, generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first in-store terminal device 50, and the first in-store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). The first in-store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode, manually entering it, etc. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs electronic payment (S17). Then, the payment server 100 sends a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0022] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuing a one-time code may be omitted in store scanning, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0023] [Payment server] FIG. 4 is a configuration diagram of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a content providing unit 120, a payment processing unit 130, an information management unit 140, an information processing unit 150, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as a large-scale integration (LSI), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a graphics processing unit (GPU), or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD (hard disk drive) or flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device. The information management unit 140 is an example of an "acquisition unit." The information processing unit 150 is an example of a "control unit."

[0024] The storage unit 170 is a HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172 including setting information 180, content information 174, affiliated store / shop information 176, etc.

[0025] The communication unit 110 is a communication interface for connecting to the network NW, and is, for example, a network interface card.

[0026] The content providing unit 120 has, for example, a web server function, and provides information (content) for displaying various screens for electronic payment services to the user terminal device 10. The content providing unit 120 reads out necessary content from the content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs from the user while content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

[0027] The payment processing unit 130 performs payment processing based on the payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0028] FIG. 5 is a diagram showing an example of the contents of user information 172. User information 172 is an example of user registration information. User information 172 includes, for example, a user URL, account ID, telephone number, and password, as well as associated information such as email address, user ID, name, address, date of birth, registration date, charge balance, deferred payment settings, deferred payment limit, deferred payment usage amount, available deferred payment amount, payment method settings, bank account, credit card number, charge history information, payment history information, history information, voucher information, setting information 180, and eKYC information. The user URL is used for remittance processing between users. When registering for the electronic payment service, registration of a phone number and password is required. The account ID is issued to the user by the payment server 100, and the user ID can be set by the user (or does not have to be set). The email address, name, address, and date of birth are also information that can be set by the user (or do not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0029] The charge balance indicates the balance of electronic money set by the user by transferring funds to the account in advance. Transfer methods include transfers from a designated service provider (bank) ATM (Automatic Teller Machine) or from a registered bank account. The deferred payment setting indicates whether the setting for deferred payment electronic payments has been completed and is set to either "completed" or "not completed." The deferred payment limit is the monthly deferred payment limit. The deferred payment usage amount is the amount of deferred payment already used in the current month. The available deferred payment amount is the amount of deferred payment available in the current month, calculated by subtracting the deferred payment usage amount from the deferred payment limit. While the figure shows only one deferred payment limit, in reality, there may also be daily upper limits, and the lower of these may be set as the deferred payment limit. Further details on deferred payment will be discussed later. The payment method setting indicates whether the user will make electronic payments using the charge balance or by deferred payment at that time. The bank account and credit card number are information on the bank account or credit card number (account number, card number) that can be used to deposit funds into the electronic payment service. The charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. The payment history information is information that shows the breakdown of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0030] The voucher information is, for example, information about the store where the voucher held by the user can be used, the amount of the voucher, etc. When the user performs an operation to use an electronic voucher on the payment app 20, the payment server 100 performs a process to use the electronic voucher at the target store based on the store information and voucher information acquired from the first store terminal device 50 or the user terminal device 10. Then, the payment server 100 performs a process to deduct the payment amount from the amount of the used voucher in the voucher information.

[0031] eKYC information (electronic Know Your Customer information) is information obtained by identity verification performed over a network. The eKYC information includes, for example, information such as the user's name and address. The eKYC information is information obtained, for example, through an electronic payment service. A user can perform eKYC by using the payment application 20 and linking the payment application 20 with the payment server 100. The setting information 180 will be described later.

[0032] 6 is a diagram showing an example of the contents of affiliated store / store information 176. The affiliated store / store information 176 includes, for example, a first table 176A in which an affiliated store ID and a store ID are associated with a store URL, a second table 176B in which an affiliated store ID is associated with an affiliated store name and sales amount (described above), and a third table 176C in which a store ID is associated with a store name. In addition to this information, the affiliated store / store information 176 may also include information such as the category of the affiliated store or store, the store's location, and payment patterns.

[0033] The information management unit 140 manages the user information 172 and the affiliated store / store information 176 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds new records to, edits, deletes, etc. the user information 172 and the affiliated store / store information 176.

[0034] [Electronic Payment] When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 references the user information 172 to acquire the "payment method setting" of the user. For users whose "payment method setting" is set to "charge balance," the payment processing unit 130 performs electronic payment as follows: For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales proceeds. The item value of the affiliated store's sales proceeds is not itself used as electronic money, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0035] The payment processing unit 130 performs electronic payments for users whose "setting information" is set to "deferred payment" as follows. Deferred payment is set separately from "credit card payment," which is set in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service. The operator of the electronic payment service acts as the creditor, and allows electronic payments within the deferred payment limit, independent of the remaining balance. To receive the deferred payment service, a user may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used for deferred payment is settled in full on the following month's payment date, for example, by debit from a bank account. In this case, the payment processing unit 130 makes a provisional payment by adding the payment amount to the deferred payment amount and subtracting the same amount from the available deferred payment balance. On the closing date, the payment processing unit 130 performs the process described above to debit the current month's payment on the following month's payment date, or requests the credit card operator to perform this process. If the payment amount exceeds the available deferred payment balance at the time of provisional payment, an error notification is returned to the payment app 20.

[0036] [overview] When a user performs an operation to instruct a donation to a local government after a predetermined period of time on an interface screen that inquires whether or not to make a donation to the local government after a predetermined period of time, which is displayed in response to information about the user's operation to make a donation to the local government, the payment server 100 acquires information about the operation and performs processing to make a donation to the local government after a predetermined period of time based on the information about the operation. The donation is what is known as hometown tax payment. The period after the predetermined period of time is the fiscal year following the fiscal year in which the operation to instruct a donation was performed. This processing will be explained in detail below.

[0037] [Interface screen (1)] When a user operates the service app 30, for example, the service app 30 and the service server 200 (the service system) display the interface screen IF1 shown in Fig. 7 on the display unit of the user terminal device 10. The interface screen IF1 is a screen that is displayed after the user selects a local government and a donation amount in a predetermined content and performs an operation to instruct the user to make a donation. When the user operates the confirm button B1 on the interface screen IF1, the service system displays the interface screen IF2 of Fig. 7 on the display unit.

[0038] Interface screen IF2 includes buttons B2 and B3. Button B2 is a button for proceeding to the procedure. When button B2 is operated, a process is executed to make this year's hometown tax donation based on the municipality and amount confirmed on interface screen IF1. For example, a user can confirm the payment method and perform various processes on a specific interface screen to make a hometown tax donation.

[0039] [Interface screen (2)] Button B3 is a button for setting up annual donations to the same local government. When button B3 is operated, the service system displays interface screen IF3 of FIG. 8 on the display unit of the user terminal device 10. Interface screen IF3 is, for example, content that the payment server 100 displays on the display unit. Interface screen IF3 includes, for example, an area for selecting the annual donation date, an area for displaying the selected payment method, an area for changing the payment method, an email address for sending a pre-notification email, a sending date for sending the pre-notification email, and a confirmation button for confirming the content of each of the above-mentioned areas. The user can change the content of each area by performing a predetermined operation on interface screen IF3. Note that instead of annually, the donation date may be set to only the following year, every month, or every few months.

[0040] As described above, by operating the interface screen IF3, the user sets up a service (hereinafter referred to as "regular hometown tax payment service") in which the user makes a donation to the same local government every year and receives a gift in return from that local government. The information processing unit 150 of the payment server 100 generates setting information 180 based on the above operation by the user.

[0041] [Settings information] FIG. 9 is a diagram showing an example of the contents of the setting information 180. The setting information 180 is information that specifies, for example, whether or not a regular hometown tax payment service is set for each user, and the contents of that setting. For example, the information is information that associates the local government to which the user will donate, the amount, the date (day) of the donation, the payment method, the date (day) of the reminder email to be sent, and the like set by the user. The information processing unit 150 refers to the setting information 180 to send a reminder email to the user and make a donation.

[0042] [Sequence] 10 is a sequence diagram showing an example of the flow of processing executed by the user terminal device 10, the payment server 100, and the service server 200. In the following processing, the processing performed by the service server 200 may be performed by the payment server 100, and the information transmitted to the service server 200 may be transmitted via the payment server 100. Conversely, the processing performed by the payment server 100 may be performed by the service server 200, and the information transmitted to the payment server 100 may be transmitted via the service server 200.

[0043] First, when a user performs a donation operation on the service application 30 of the user terminal device 10, the service application 30 transmits information corresponding to the operation to the service server 200 (S100). Next, the service server 200 transmits content for donation based on the information corresponding to the operation (S102). The content may be provided by the payment server 100.

[0044] Next, the service application 30 of the user terminal device 10 accepts the process for donation on an interface screen corresponding to the content (S104). For example, it is assumed that an application for donation for this year and donation for next year (regular hometown tax payment service) has been made.

[0045] Next, the service app 30 transmits a request to process the current year's donation to the service server 200 (S106). Next, the service server 200 processes the current year's donation in response to the request to process the donation (S108). In the processes of S106 and S108, the request to process the current year's donation is transmitted to the payment server 100, and the payment server 100 may execute electronic payment according to the payment amount using the user's account and transmit payment instructions to the service server 200.

[0046] Next, the service app 30 transmits information about the regular hometown tax payment service to the payment server 100 (S110). Next, the payment server 100 generates setting information 180 based on the transmitted information (S112). The information transmitted in S110 is the information input in the interface IF3 described above. For example, if an operation is performed in the interface screen IF2 described above not to use the regular hometown tax payment service, for example, the processes of S110 and S112 are omitted.

[0047] Next, the payment server 100 sends a reminder email to the user terminal device 10 based on the setting information 180 (S114). Next, the payment server 100 acquires a response to the reminder email sent from the user terminal device 10 (S116). Next, the payment server 100 executes electronic payment at the timing of payment (S118). Next, the payment server 100 sends a donation instruction to the service server 200 (S120). Next, the service server 200 executes donation processing based on the donation instruction (S122).

[0048] As described above, based on the application instruction information for the regular hometown tax payment service, the payment server 100 requests the service server 200, which cooperates with the payment server 100 and executes the donation to the local government, to make a donation to the local government when the predetermined period corresponding to the regular hometown tax payment service arrives (S110, S120). More specifically, when the predetermined period arrives, the payment server 100 executes the electronic payment of the electronic payment service using the user's account of the electronic payment service to make the electronic payment of the donation (S118), and also sends a request for the donation to the local government to the service server 20 (S120). In this way, the donation process is executed by the user terminal device 10, the payment server 100, and the service server 200, thereby improving convenience for the user.

[0049] [Flowchart (donation processing)] 11 is a flowchart showing an example of the flow of processing executed by the payment server 100. First, the payment server 100 accepts an operation related to a user's donation (for example, an operation for making a hometown tax donation) (S200). Next, the payment server 100 accepts an operation related to the user's donation destination (S202). The operations of S200 and S202 are operations on the service app 30.

[0050] Next, the payment server 100 refers to the eKYC information and checks whether the donation destination is a donation-eligible local government (S204). Next, the payment server 100 determines whether the donation destination is a donation-eligible local government (S206). If the donation destination is not a donation-eligible local government, the payment server 100 transmits information indicating a change of the donation destination to the service app 30 (S208).

[0051] If the local government to which the user selects a donation destination is different from the local government that has jurisdiction over the user's address in the eKYC information, the payment server 100 determines that the donation is eligible and can accept the donation, and if the local government to which the user selects a donation destination is the same as the local government that has jurisdiction over the user's address in the eKYC information, the payment server 100 sends information to the service app 30 indicating that the donation is ineligible and that the donation destination should be changed. Note that if the user has not performed eKYC, the payment server 100 requests the user to perform eKYC via the service app 30.

[0052] If the donation destination is a donation target, the payment server 100 acquires information necessary for the hometown tax payment, such as the donation amount, from the service application 30 (S210). Next, the user inquires about applying for the regular hometown tax payment service (S212), and it is determined whether the user wishes to apply for the regular hometown tax payment service (S214).

[0053] If the user does not wish to apply for the regular hometown tax payment service, the payment server 100 executes the donation for the target year (S216). For example, the payment server 100 uses an electronic payment service to make an electronic payment for the user's payment and requests the service server 200 to process the donation for the target year.

[0054] If the person wishes to apply for the regular hometown tax payment service, the payment server 100 accepts the application for the regular hometown tax payment service (S218). Next, the payment server 100 executes the donation for the target year, sets up the regular hometown tax payment service (S220), and sets up a reminder email (generates setting information 180) (S222).

[0055] In this way, when an operation to make a donation to the local government selected by the user for this year is accepted, content (for example, interface screen IF3) inquiring about making a reservation to make a donation to the local government for next year as well is provided to the user terminal device 10. When information transmitted from the user terminal device 10 in response to an operation to make a reservation for the content to make a donation to the local government for next year as well is acquired, the payment server 100 transmits, for example, a reminder email (advance notice) to the user terminal device 10, as will be described later. This ends the processing of one routine of this flowchart.

[0056] [Flowchart (Processing related to the regular hometown tax payment service)] FIG. 12 is a flowchart showing an example of the flow of processing executed by the payment server 100. First, the payment server 100 determines whether a reminder is set in the setting information 180 (S300). If a reminder is set, the payment server 100 determines whether it is time to send a reminder (S302). If it is time to send a reminder, the payment server 100 sends the reminder to the user terminal device 10 (S304). For example, the reminder is sent to a contact such as a set email address. Alternatively, the reminder may be notified via the payment app 20 or the service app 30.

[0057] Next, the payment server 100 determines whether the user has changed the settings in the reminder content (S306). If the user has changed the settings, the payment server 100 changes the settings in the setting information 180 (S308).

[0058] If the user has not changed the settings, the payment server 100 determines whether the regular hometown tax payment service has been canceled in the reminder content (S310). If the regular hometown tax payment service has not been canceled in the reminder content, the payment server 100 determines whether this year's payment (this year's payment reserved last year) has been canceled (S312). If the determination in S310 or S312 is positive, the payment server 100 updates the setting information 180 according to the result of the determination (S314).

[0059] For example, when the payment server 100 receives an instruction to cancel a donation for next year's reservation (reserved last year but made this year) sent from the user terminal device 10 in response to a user's operation in response to a prior notification, the payment server 100 cancels the donation to the local government corresponding to the reservation and changes the content of the donation to the local government corresponding to the reservation.

[0060] If this year's payment is not canceled, the payment server 100 processes the donation at the set time (S316). For example, the payment server 100 performs electronic payment on the set date and sends payment instructions to the service server 200 in response to the payment. The payment server 100 sends a reminder email on this year's payment date for the regular hometown tax payment service, a first period before the payment date for the regular hometown tax payment service applied for last year (a prior notice is sent to the user terminal device of the user, a first period after the specified period, asking whether or not the user agrees to a request to make a donation to the local government after the specified period). If information indicating consent is sent from the user terminal device 10, the payment server 100 performs processing to make a donation to the local government on the payment date for the regular hometown tax payment service (processing to make a donation to the local government after the specified period).

[0061] Next, when the payment server 100 receives information indicating that the processing by the service server 200 has been completed, it performs a process of associating the voucher with the user's identification information managed by the electronic payment service (S318). This completes the processing of one routine of this flowchart.

[0062] As described above, the payment server 100 sends a prior notification email and makes the payment depending on the user's response to the reminder, which improves user convenience. For example, the user can decide whether to make a payment to a local government through the regular hometown tax payment service depending on their income for the current fiscal year and their use of other hometown tax payments.

[0063] For example, the payment server 100 may use a reminder email to inquire about making a payment on the payment date for the regular hometown tax payment service applied for last year. For example, when the payment server 100 acquires instructions regarding a donation for next year's reservation sent from the user terminal device 10 in response to a user's operation in response to the reminder email (advance notice) (when it acquires information indicating that payment will be made according to the reservation for the regular hometown tax payment service made last year), it executes processing to make a donation to the local government corresponding to the reservation.

[0064] [Income Information] The following describes processing using income information. The payment server 100 references the user's salary information, identifies the salary from after the specified period to before the second period (for example, when a reminder is sent), and determines whether a donation made after the specified period will be eligible for hometown tax deduction based on the identified salary and the total amount of donations for the fiscal year after the specified period before the second period, and provides information indicating the result of the determination to the user's user terminal device 10. The information indicating the result of the determination is, for example, information indicating that making a payment using the regular hometown tax payment service will reach the hometown tax payment upper limit (described below), or information indicating that the hometown tax payment upper limit will be exceeded, which helps the user determine whether they will suffer any disadvantages if they make a payment using the regular hometown tax payment service.

[0065] For example, when making a payment using the regular hometown tax payment service, different content may be provided to the user depending on, for example, (1) the case where the hometown tax payment upper limit described below is predicted to be reached, and (2) the case where the hometown tax payment upper limit is predicted not to be reached. For example, in case (1), the payment server 100 may provide the user with content recommending that the user more proactively check this year's salary and hometown tax payment amount than in case (2). As described above, the payment server 100 may send a reminder by referring to the income information 190. The memory unit 170 may store, for example, the income information 190.

[0066] FIG. 13 is a diagram showing an example of the contents of income information 190. Income information 190 is, for example, information related to the income of each user. Income information 190 is, for example, information that associates the user's income for the current fiscal year, the hometown tax donation upper limit, and the amount of hometown tax donation used. The hometown tax donation upper limit may be, for example, the upper limit at which the user can use hometown tax donations while minimizing their out-of-pocket expenses, or it may be the upper limit plus an allowance. The hometown tax donation upper limit may also be an amount set by the user. The hometown tax donation upper limit may be an amount calculated based on last year's salary, an amount calculated based on the total current salary, or an amount calculated based on the amount of salary for this fiscal year (annual income) estimated based on the trend in salary for this fiscal year.

[0067] Either or both of the income for the current year in the income information 190 and the amount of hometown tax donations used may be information entered by the user, or may be information obtained from the service app 30 or the service server 200. Also, either or both of the income for the current year in the income information 190 and the amount of hometown tax donations used may be information provided from a different app or another service server. The different app or another service server may be, for example, a bank account into which a salary is deposited, or a household accounting app that stores information on pay slips.

[0068] [flowchart] FIG. 14 is a flowchart showing an example of the flow of processing executed by the payment server 100 using the income information 190. The following mainly explains the differences from the flowchart in FIG. 12 described above. As described below, a reminder may be sent depending on the payment conditions. If it is determined in S302 that it is time to send a reminder, the payment server 100 determines whether the payment satisfies the conditions (S303-1). If the payment satisfies the conditions, the process proceeds to S304, where the payment server 100 sends a reminder to the user terminal device 10 (S304). If the payment does not satisfy the conditions, the payment server 100 sends a message to the user terminal device 10 to skip the payment (S303-2).

[0069] The conditions for payment include that even if you make payments using the regular hometown tax payment service, the amount does not reach the hometown tax payment limit, and that the total of the payment and the amount used for hometown tax payment does not reach the hometown tax payment limit.

[0070] Furthermore, the content sent to the user terminal device 10 may be different depending on whether the payment conditions are met or not. The payment server 100 may provide information that further encourages payment of the regular hometown tax payment service when the payment conditions are met, and may provide information that does not further encourage payment of the regular hometown tax payment service when the payment conditions are not met.

[0071] According to the embodiment described above, the payment server 100 performs the process for making a donation to a local government after a predetermined period of time, thereby improving convenience for users.

[0072] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0073] 10 User terminal device 20. Payment App 30 Service Apps 100 Payment Server 120 Contents Provider 130 Payment processing unit 140 Information Management Department 150 Information Processing Department 200 Service Server

Claims

1. In an interface screen for inquiring whether or not to make a donation to a local government after a predetermined period of time, which is displayed in accordance with information regarding the user's operation to make a donation to the local government, an acquisition unit that acquires, when the user performs an operation to instruct the user to make a donation to the local government after the predetermined period, information regarding the instructing operation; a control unit that performs processing to make a donation to the local government after the predetermined period based on information regarding the instructed operation; An information processing device comprising:

2. the control unit, when the predetermined period has arrived, makes a request for donation to the local government to a service server that cooperates with an information processing device and that executes donation to the local government, based on information related to the instructed operation; The information processing device according to claim 1 .

3. The information processing device is a device that provides an electronic payment service, the control unit, when the predetermined period has arrived, executes electronic payment of the electronic payment service using the user's account of the electronic payment service to make electronic payment of the donation, and sends a request for donation to the local government to the service server; The information processing device according to claim 2 .

4. After the predetermined period, the fiscal year following the fiscal year in which the operation to instruct to make the donation was performed will be the fiscal year following the fiscal year in which the operation to instruct to make the donation was performed. The information processing device according to claim 1 .

5. The donation is a hometown tax donation. The information processing device according to claim 1 .

6. The control unit sending a prior notice to the user terminal device of the user before a first period after the predetermined period, inquiring whether or not the user agrees to request a donation to the local government after the predetermined period; When information indicating consent is transmitted from the user terminal device, a process for making a donation to the local government is carried out after the predetermined period of time. The information processing device according to claim 5 .

7. After the predetermined period, the next fiscal year will be the fiscal year following the fiscal year in which the operation to make the donation was performed. The control unit When information transmitted from the user terminal device in response to an operation by the user to make a reservation to make a donation to the local government next year as well in response to content inquiring about making a reservation to make a donation to the local government next year as well, which is provided when an operation to make a donation to the selected local government this year is accepted, the advance notification is transmitted to the user terminal device. The information processing device according to claim 6 .

8. The control unit When an instruction regarding the donation for the reservation for next year transmitted from the user terminal device in response to the operation of the user in response to the advance notice is acquired, a process for making a donation to the local government corresponding to the reservation is executed; When an instruction to cancel the reservation for donation for next year, which is transmitted from the user terminal device in response to the operation of the user in response to the advance notification, is acquired, the donation to the local government corresponding to the reservation is canceled and the content of the donation to the local government corresponding to the reservation is changed. The information processing device according to claim 7 .

9. The control unit If the local government to which the user has made a donation selected by the user is different from the local government that has jurisdiction over the user's address obtained by the identity verification process stored in the storage unit, the donation is accepted; If the local government selected by the user as the donation destination is the same as the local government that has jurisdiction over the user's address obtained by the identity verification process stored in the storage unit, information indicating that the donation destination should be changed is sent to the user terminal device. The information processing device according to claim 8 .

10. The control unit Refer to the salary information of the user stored in the storage unit, Identifying the salary for a period two periods before the specified period, and determining whether the donation made after the specified period is eligible for hometown tax deduction based on the identified salary and the total amount of donations for the fiscal year after the specified period before the second period; providing information indicating the result of the determination to a user terminal device of the user; The information processing device according to claim 5 .

11. The computer In an interface screen for inquiring whether or not to make a donation to a local government after a predetermined period of time, which is displayed in accordance with information regarding the user's operation to make a donation to the local government, When the user performs an operation to instruct the user to make a donation to the local government after the predetermined period, a process of acquiring information about the instructing operation; a process for performing a process for making a donation to the local government after the predetermined period based on information about the instructed operation; An information processing method that performs the above.

12. On the computer, In an interface screen for inquiring whether or not to make a donation to a local government after a predetermined period of time, which is displayed in accordance with information regarding the user's operation to make a donation to the local government, When the user performs an operation to instruct the user to make a donation to the local government after the predetermined period, a process of acquiring information about the instructing operation; a process for performing a process for making a donation to the local government after the predetermined period based on information about the instructed operation; A program that executes the following.

Citation Information

Patent Citations

  • Donation support device, donation support method, and donation support program

    JP2014021729A

  • Final income tax return support processing device for hometown taxpayer, final income tax return support processing program, and final income tax return support processing system

    JP2018067246A