Savings system, savings method, and program

Abstract

To improve user convenience. [Solution] The accumulation condition information acquisition unit (101) of the accumulation system (1) acquires accumulation condition information relating to the accumulation conditions of electronic money that can be used for a specified purpose, and the accumulation condition information specified by the user. The accumulation processing execution unit (102) executes accumulation processing related to accumulation based on the accumulation condition information.

Description

Technical Field

[0001] The present disclosure relates to a savings system, a savings method, and a program.

Background Art

[0002] Conventionally, electronic cash vouchers such as electronic gift certificates issued by local governments and the like are known. For example, Patent Document 1 describes a payment server that automatically applies a number of electronic cash vouchers corresponding to a payment amount in a payment service in which a user executes payment at a store using a payment application installed on a user terminal, when the setting for automatically applying electronic cash vouchers (electronic vouchers) is turned on.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, with the technique of Patent Document 1, when a user makes a high-value payment using electronic cash vouchers, it is necessary to purchase a large number of electronic cash vouchers at one time, which imposes a financial burden on the user. If the user attempts to purchase electronic cash vouchers little by little, the user has to perform the operation of purchasing electronic cash vouchers many times, which imposes an operational burden on the user. For this reason, the technique of Patent Document 1 cannot sufficiently enhance user convenience.

[0005] One of the objects of the present disclosure is to enhance user convenience.

Means for Solving the Problems

[0006] The savings system relating to this disclosure includes savings condition information relating to the savings conditions of electronic money that can be used for a specified purpose, a savings condition information acquisition unit that acquires the savings condition information specified by the user, and a savings processing execution unit that executes savings processing relating to the savings based on the savings condition information. [Effects of the Invention]

[0007] This disclosure can improve user convenience. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of the hardware configuration of a savings system. [Figure 2] This figure shows an example of a screen displayed on a user's terminal. [Figure 3] This figure shows an example of a screen displayed on a user's terminal. [Figure 4] This figure shows an example of the functions that can be realized by the savings system. [Figure 5] This is a diagram showing an example of an electronic money database. [Figure 6] This figure shows an example of a database to be searched. [Figure 7] This figure shows an example of a user database. [Figure 8] This figure shows an example of the process performed by the savings system. [Figure 9] This figure shows an example of a function that can be achieved through modification. [Figure 10] This figure shows an example of the screen displayed on the user terminal in Modification Example 1. [Figure 11] This figure shows an example of a user joining a savings plan midway through. [Figure 12] This figure shows an example of the screen displayed on a user's terminal for a user who joins the session midway. [Modes for carrying out the invention]

[0009] [1. Hardware configuration of the savings system] An example of an embodiment of the savings system, savings method, and program related to this disclosure will be described. Figure 1 is a diagram showing an example of the hardware configuration of the savings system. For example, savings system 1 includes a server 10 and a user terminal 20. Each of the server 10 and the user terminal 20 is connected to a network N such as the Internet or a LAN. At least one of the server 10 and the user terminal 20 may be present in multiple units.

[0010] Server 10 is a server computer. For example, Server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The storage unit 12 includes at least one of volatile memory such as RAM and non-volatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0011] The user terminal 20 is the user's computer. For example, the user terminal 20 is a smartphone, tablet, personal computer, or wearable device. The user terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an operation unit 24, and a display unit 25. The hardware configuration of the control unit 21, the storage unit 22, and the communication unit 23 may be the same as that of the control unit 11, the storage unit 12, and the communication unit 13, respectively. The operation unit 24 is an input device such as a touch panel or a mouse. The display unit 25 is a display such as a liquid crystal or organic EL.

[0012] It should be noted that the programs stored in the storage units 12 and 22 may be supplied to the server 10 or the user terminal 20 via the network N. Further, at least one of a reading unit (for example, a memory card slot) that reads a computer-readable information storage medium, and an input / output unit (for example, a USB port) for inputting and outputting data to and from an external device may be included in the server 10 or the user terminal 20. For example, the program stored in the information storage medium may be supplied to the server 10 or the user terminal 20 via at least one of the reading unit and the input / output unit.

[0013] Further, the computers included in the savings system 1 are not limited to the example shown in FIG. 1. The savings system 1 only needs to include at least one computer. For example, the savings system 1 may include only the server 10. In this case, the user terminal 20 exists outside the savings system 1. The savings system 1 may include the server 10 and other computers not shown in FIG. 1. The savings system 1 may include only other computers not shown in FIG. 1.

[0014] [2. Overview of Savings System] In the present embodiment, a case where the savings system 1 is applied to an electronic commerce service is taken as an example. The flow in which a user purchases a product or service through the electronic commerce service may be the same as that of a known electronic commerce service. For example, the user may register a desired product or service in a wish list and then purchase the product or service. The user can use any payment method for purchasing the product or service.

[0015] In the present embodiment, an electronic cash voucher will be described as an example of the payment method. The electronic cash voucher is an electronic cash voucher. The electronic cash voucher can also be referred to as a digital or virtual cash voucher. The electronic cash voucher may also be called an electronic voucher. The electronic cash voucher may be the same as a known electronic cash voucher. For example, the electronic cash voucher may be a gift certificate, a regional promotion ticket, a facility use ticket, a meal ticket, a gift card not classified into these, or a product exchange ticket. The electronic cash voucher may not include a free coupon. The electronic cash voucher may include a paid coupon.

[0016] For example, a user may purchase an electronic voucher via an e-commerce service, or may purchase an electronic voucher via another service different from the e-commerce service. The electronic voucher may be provided from a local government to the user as a return gift for a donation made by the user to the local government. The electronic voucher may be provided from a local government to the user as a subsidy from the local government to the user. The electronic voucher may be provided to the user by an organization such as a company as part of employee benefits. The user can use the electronic voucher for any purpose.

[0017] Figure 2 and Figure 3 are diagrams illustrating examples of screens displayed on the user terminal 20. As shown in Figure 2, the user terminal 20 causes the display unit 25 to display a purpose specification screen SC1 for the user to specify the purpose of using the electronic voucher. In the present embodiment, a case where the user uses the electronic voucher to purchase a product or service registered in a wish list is taken as an example. For example, the purpose specification screen SC1 displays various types of information (for example, title, rating, store name, price, description text, or image) related to the products or services registered in the wish list. The user can purchase the product or service registered in the wish list by selecting the button B10.

[0018] In the present embodiment, the user can accumulate electronic vouchers in order to purchase the product or service registered in the wish list. For example, when the product or service registered in the wish list is high-priced, the user accumulates electronic vouchers over a certain period of time in order to purchase the high-priced product or service. Along with the product or service registered in the wish list, a link for the user to apply for accumulation of electronic vouchers may be displayed. When the user selects the button B11, as shown in Figure 3, the user terminal 20 causes the display unit 25 to display an accumulation condition specification screen SC2 for specifying accumulation conditions that are conditions for accumulating electronic vouchers.

[0019] For example, the user enters the savings conditions in input forms F20 to F22. In the example in Figure 3, the user enters the savings amount, savings period, and bonus month as savings conditions. In the example in Figure 3, only one type of electronic voucher, such as "AAA gift certificate," is shown, but multiple types of electronic vouchers may be displayed on the savings conditions specification screen SC2. In this case, the user may specify the type of electronic voucher to be saved on the savings conditions specification screen SC2. The user may also be able to save for electronic vouchers in services (platforms) to which the savings system 1 is applied, such as e-commerce services or travel booking services.

[0020] For example, the user enters the monthly savings amount in input form F20. Input form F21 may automatically fill in the price of the product or service and the savings period corresponding to the savings amount entered by the user, or the user may be allowed to enter any savings period. The user may optionally enter a bonus month in input form F22 in which the savings amount will be higher than in other months. The user may also enter the savings amount for the bonus month in input form F22. Savings conditions, such as savings amounts corresponding to the price of the product or service, may be suggested.

[0021] For example, when a user specifies the accumulation conditions in input forms F20-F22 and selects button B23, the application for electronic gift certificate accumulation is completed. Users can use any payment method for electronic gift certificate accumulation. For example, a user may accumulate electronic gift certificates using cash, a bank account, a credit card or similar card, electronic money, a balance not classified as electronic money, cryptocurrency, or other payment methods.

[0022] As described above, the savings system 1 of this embodiment allows users to accumulate electronic vouchers to purchase goods or services registered on their wish list. The savings system 1 accumulates electronic vouchers based on the savings conditions entered by the user on the savings condition specification screen SC2. When the savings mature, the user can purchase the goods or services registered on their wish list. In this way, the savings system 1 can enhance user convenience. The details of the savings system 1 will be described below.

[0023] [3. Functions provided by the savings system] Figure 4 shows an example of the functions implemented in the accumulation system 1. The components implemented in the accumulation system 1 of this embodiment can be configured by combining them into a single device or by further distributing them among multiple devices. Figure 4 shows an example of the functions implemented in the server 10. For example, the server 10 includes a data storage unit 100, an accumulation condition information acquisition unit 101, and an accumulation processing execution unit 102. The data storage unit 100 is implemented by a storage unit 12. The accumulation condition information acquisition unit 101 and the accumulation processing execution unit 102 are each implemented by a control unit 11.

[0024] [3-1. Data Storage Unit] The data storage unit 100 stores various types of data. For example, the data storage unit 100 stores the electronic money database DB1, the search target database DB2, and the user database DB3.

[0025] Figure 5 shows an example of the electronic gift certificate database DB1. The electronic gift certificate database DB1 is a database that stores various information related to electronic gift certificates. In this embodiment, we take the example that the electronic gift certificate database DB1 stores basic information about electronic gift certificates that can be accumulated. For example, the electronic gift certificate database DB1 stores type identification information, name information, issuer information, price information, usage conditions information, premium information, validity period information, and application period information.

[0026] Type identification information is information that can identify the type of electronic gift certificate. If an e-commerce service supports multiple types of electronic gift certificates, type identification information for each of the multiple types is stored in the electronic gift certificate database DB1. For example, type identification information may be an ID uniquely assigned to each type of electronic gift certificate. If each type can be identified by the name of the electronic gift certificate, the name information may correspond to the type identification information.

[0027] In this embodiment, we describe a case where the concept of quantity does not exist for electronic vouchers, and the balance of each individual electronic voucher is managed. However, if the concept of quantity exists for electronic vouchers and the amount per voucher is defined, the type identification information may indicate the unit of currency for which the electronic voucher is. For example, even if the same usable electronic voucher has the name "AAA Gift Certificate," if there are three types of electronic vouchers with amounts of 1,000 yen, 5,000 yen, and 10,000 yen per voucher, the type identification information may be information that can identify each of these three types of electronic vouchers.

[0028] Name information is information about the name of the electronic voucher. For example, name information represents the text (string) that indicates the name of the electronic voucher. Issuer information is information about the issuer of the electronic voucher. For example, if the electronic voucher is issued by a business that operates an e-commerce service, the issuer information will indicate that business. The issuer can be any entity. For example, the issuer may be a local government or the national government, or a business that operates a service other than an e-commerce service.

[0029] Price information is information regarding the price of electronic vouchers. In this embodiment, since the concept of quantity does not exist for electronic vouchers and the balance of each electronic voucher is managed, the price information indicates the price range that the user can acquire at one time. If the concept of quantity does not exist for electronic vouchers and the balance of each electronic voucher is managed, the price information may indicate the unit of electronic voucher that the user can acquire at one time. If the concept of quantity exists for electronic vouchers and a price per voucher is set, the price information may indicate the price set for each electronic voucher. If a fee is incurred to acquire electronic vouchers, the price information may indicate the fee.

[0030] Terms of Use information is information regarding the terms and conditions for using electronic gift certificates. These terms and conditions define the conditions under which the use of an electronic gift certificate is permitted. Use of an electronic gift certificate is permitted only when these terms and conditions are met. For example, the terms and conditions may include the merchant where the user can use the electronic gift certificate (e.g., goods or services), the location of the merchant, the goods (e.g., the plans offered by the goods or services), the services (e.g., specific services provided by the goods or services), the period, age, age group, gender, place of residence, or other conditions. Electronic gift certificates do not necessarily have specific terms and conditions.

[0031] Premium information refers to information about the premium associated with electronic gift certificates. The premium is a benefit that arises with electronic gift certificates. For example, if a user who pays 10,000 yen to acquire an electronic gift certificate is granted an electronic gift certificate worth 10,500 yen, a premium of 500 yen is incurred. In the example in Figure 5, the premium information shows the percentage of the premium, but the premium information may also show the amount of the premium. Electronic gift certificates do not necessarily have a premium associated with them. If an electronic gift certificate does not have a premium associated with it, the premium information does not need to be stored in the electronic gift certificate database DB1.

[0032] Furthermore, if the premium differs depending on the investment conditions, the premium information may show the premium corresponding to the investment conditions. For example, if the premium increases with a larger investment amount per installment, the premium information may show the premium corresponding to the investment amount. If the premium increases with a longer investment period, the premium information may show the premium corresponding to the investment period.

[0033] The validity period information is information regarding the validity period of an electronic gift certificate. The validity period may be determined based on the timing of the issuance of the electronic gift certificate, or it may be predetermined regardless of the timing of the issuance of the electronic gift certificate. If there is no specific validity period, the validity period information does not need to be stored in the electronic gift certificate database DB1. The application period information is information regarding the application period for an electronic gift certificate. The application period is the period during which an application for an electronic gift certificate can be made. If there is no specific application period, the application period information does not need to be stored in the electronic gift certificate database DB1.

[0034] Note that the information stored in the electronic gift certificate database DB1 is not limited to the example in Figure 5. The electronic gift certificate database DB1 may store any information related to electronic gift certificates. For example, the electronic gift certificate database DB1 may store the acquisition conditions for acquiring electronic gift certificates (e.g., upper limit amount, or demographic information such as the user's place of residence), the number of electronic gift certificates in stock, the number of electronic gift certificates issued, information about users who have acquired electronic gift certificates, or other information.

[0035] Furthermore, if user-specifiable savings conditions are defined, user-specifiable information regarding these conditions may be stored in the electronic money database DB1. For example, the user-specifiable information may indicate the upper limit of the amount to be saved per transaction (e.g., the monthly amount), the upper limit of the total amount saved, the shortest savings period, the longest savings period, the bonus months that the user can specify, the upper limit of the amount saved during bonus months, or a combination of these. The user specifies the savings conditions within the range indicated by the user-specifiable information.

[0036] Figure 6 shows an example of the search target database DB2. The search target database DB2 is a database that stores various information about the product or service to be searched. For example, the search target database DB2 stores search target identification information, basic information about the product or service, price information, and availability information. In this embodiment, since the product or service corresponds to the search target, the example in Figure 6 shows a case where various information about the product or service is stored in the search target database DB2.

[0037] The search target identification information is information that can identify the product or service being searched. For example, the search target identification information may be an ID, name, or other information uniquely assigned to the product or service. In this embodiment, we take the example of a case where the product or service corresponds to the search target, so the search target identification information may be the ID, name, or other information of the product or service.

[0038] Basic search information is basic information about the search target. For example, basic search information may include the name of the search target, the store where it is sold, an image, a description, or other information. Available information is information about the types of electronic vouchers that a user can use when purchasing or applying for a product or service. In this embodiment, if a user can use multiple types of electronic vouchers for a product or service, price information will show the price of the product or service. Available information may also show each type of electronic voucher that can be used for the product or service. If there are any conditions (e.g., a maximum amount) on the use of the electronic voucher, available information may also show those conditions.

[0039] Note that the information stored in the search target database DB2 is not limited to the example in Figure 6. The search target database DB2 may store any information about products or services. For example, the search target database DB2 may store information about the purchase status or reservation status of products or services. If the accumulation system 1 is applied to services other than the reception service described as an example in this embodiment, the search target database DB2 may store information about products or services that are searched in those other services.

[0040] Figure 7 shows an example of the user database DB3. The user database DB3 is a database that stores various information about users. In this embodiment, when a user registers to use the reception service, a new record is created in the user database DB3 and various information about that user is stored. For example, the user database DB3 stores user identification information, basic user information, savings condition information, savings status information, and information about held electronic gift certificates.

[0041] User identification information is information that can identify a user. For example, user identification information may be a user ID, login account, email address, telephone number, or other information. User basic information is information about a user registered with the e-commerce service. For example, user basic information may be a name, place of residence, date of birth, family structure, age or age group, occupation, other demographic information, or other information. User basic information may be updated based on user actions.

[0042] Savings conditions information is information that indicates the savings conditions. Savings conditions are the conditions for saving. For example, savings conditions may include the amount saved per installment (e.g., monthly amount), savings period, savings frequency (e.g., monthly, weekly, bimonthly, or biweekly), bonus months, savings amount in bonus months, payment method used for savings, savings timing (e.g., a specific day each month), or a combination of these. Savings timing is the timing at which savings are made. Savings timing can also be said to be the timing at which payment is made. Savings timing may be a specific day each month. Savings timing may be specified by the user, or it may be predetermined and not specified by the user.

[0043] Note that the accumulation conditions are not limited to the example of this embodiment. For example, the accumulation conditions may be the type of electronic gift certificate to be accumulated. In Figure 2, the accumulation conditions specification screen SC2, which is displayed after a product button B11 is selected, may display a list of electronic gift certificates that the user can use to purchase the product. In this case, the user specifies the type of electronic gift certificate to be accumulated from among the multiple types of electronic gift certificates displayed as candidates. The accumulation conditions may also indicate the type of electronic gift certificate specified by the user.

[0044] The accumulation status information is information regarding the status of electronic money deposits. The accumulation status information may show the current accumulation status or the past accumulation status. For example, the accumulation status information may show the current total accumulation amount, the results of individual settlements, the number of deposits since the start of deposits, the elapsed time since the start of deposits, the remaining amount to be deposited until maturity, the number of deposits remaining until maturity, the remaining time until maturity, or a combination of these. The accumulation processing execution unit 102, described later, updates the accumulation status information when it executes the accumulation processing.

[0045] Furthermore, the accumulation conditions information and accumulation status information may be stored in the user database DB3 in association with purpose information related to the specified purpose. For example, the purpose information may indicate a purpose specified by the user, a purpose specified by the issuer of the electronic voucher (e.g., a store), a purpose specified by the operator or business of the platform providing the electronic voucher (e.g., an operator or business of a payment service or e-commerce service), or other purposes.

[0046] In this embodiment, the purpose information includes information that can identify the product or service specified by the user. The purpose information only needs to be able to identify the purpose specified by the user, and may be other information. The purpose information may also be a string indicating the purpose entered by the user. The server 10 may display the contents of the savings condition information, savings status information, and purpose information on the user terminal 20. If the user changes the savings conditions during the savings process, the server 10 may update the savings condition information stored in the user database DB3.

[0047] The held electronic gift certificate information is information about the electronic gift certificates held by a user. Holding electronic gift certificates can also be described as acquiring electronic gift certificates. For example, the held electronic gift certificate information may show the type identification information, balance, number of certificates, validity period, application period, or other information of the held electronic gift certificates. If a user acquires electronic gift certificates by a method other than savings, the user's held electronic gift certificate information is updated to show the electronic gift certificates acquired by that user. In this embodiment, when a user's savings plan matures, the user's held electronic gift certificate information is updated to show the electronic gift certificates that the user has saved.

[0048] Note that the information stored in the user database DB3 is not limited to the example in Figure 7. The user database DB3 may store any information about the user. For example, the user database DB3 may store the password for the user to log in to the reception service, identity verification information regarding whether the user has verified their identity, acquisition history information regarding the history of electronic money certificates acquired by the user, service usage history information regarding the user's use of e-commerce services, electronic money certificate usage history information regarding the user's use of electronic money certificates, or other information.

[0049] The data stored in the data storage unit 100 is not limited to the above example. The data storage unit 100 only needs to store the data necessary for the display control described in this embodiment. For example, the data storage unit 100 may store the data necessary for displaying the objective specification screen SC1, the accumulation condition specification screen SC2, or other screens.

[0050] [3-2. Accumulation Conditions Information Acquisition Section] The accumulation condition information acquisition unit 101 acquires accumulation condition information relating to the accumulation conditions of electronic gift certificates that can be used for a purpose specified by the user. The purpose is for the user to accumulate electronic gift certificates. In this embodiment, since the user accumulates electronic gift certificates for the purpose of purchasing goods or services, the accumulation condition information acquisition unit 101 acquires accumulation condition information relating to the goods or services specified by the user. The user may accumulate electronic gift certificates for purposes other than purchasing goods or services. The user can accumulate electronic gift certificates for any purpose. For example, the user may accumulate electronic gift certificates for the purpose of giving them as gifts to others.

[0051] In the examples in Figures 2 and 3, the products or services registered on the wish list correspond to the products or services specified by the user. The products or services specified by the user are not limited to those registered on the wish list. For example, the products or services specified by the user may be products or services added to the shopping cart, products or services registered on the favorites list, products or services displayed on the user terminal 20, or products or services selected by the user from the search results.

[0052] In this embodiment, when a user enters deposit condition information on the deposit condition specification screen SC2, the user terminal 20 transmits deposit condition information indicating the deposit condition information entered by the user to the server 10. The deposit condition information acquisition unit 101 stores the deposit condition information in the user database DB3 in association with the user's user ID. The deposit condition information acquisition unit 101 can acquire the deposit condition information from the user database DB3 at any time (for example, at the time when monthly settlements are executed).

[0053] Note that the deposit condition information may be stored in a database other than the user database DB3, a computer other than the server 10, or an information storage medium. In this case, the deposit condition information acquisition unit 101 only needs to acquire the deposit condition information from the other database, other computer, or information storage medium. The deposit condition information acquisition unit 101 only needs to acquire the deposit condition information for the deposits that are subject to the deposit processing described later.

[0054] [3-3. Accumulation Processing Execution Unit] The accumulation processing execution unit 102 executes accumulation processing based on the accumulation condition information. Accumulation processing is a series of processes in accumulating electronic gift certificates. For example, accumulation processing includes settling the accumulation amount, updating accumulation status information, notifying the user, or a combination of these. In this embodiment, since the user specifies a product or service as the purpose of accumulation, the accumulation processing execution unit 102 executes accumulation processing based on the accumulation condition information related to the product or service specified by the user.

[0055] For example, the deposit processing execution unit 102 determines whether the deposit timing indicated by the deposit condition information has arrived. If the deposit processing execution unit 102 determines that the deposit timing has arrived, it executes the settlement for the deposit based on the deposit amount and settlement method indicated by the deposit condition information. The settlement may be the same as known processing. After executing the settlement, the deposit processing execution unit 102 updates the user database DB3 so that the deposit status information indicates that the deposit has been completed. The deposit processing execution unit 102 notifies the user that the deposit was successful using a notification means such as email. The deposit processing execution unit 102 executes this series of processes as a deposit process each time the deposit timing arrives.

[0056] Note that the deposit timing may be the same for all users; in this case, the deposit timing does not need to be indicated in the deposit condition information. The deposit processing execution unit 102 executes the deposit processing for each user when the deposit timing common to all users arrives. If the bonus month and the deposit amount for that month are set in the deposit condition information, the deposit processing execution unit 102 should execute the deposit processing based on the deposit amount indicated in the deposit condition information when the bonus month indicated in the deposit condition information arrives.

[0057] Furthermore, the accumulation processing execution unit 102 may update the user's electronic gift certificate information so that the electronic gift certificates accumulated by the user are granted to the user when the accumulation matures. For example, if the electronic gift certificates are managed by balance, the accumulation processing execution unit 102 may update the user's electronic gift certificate information so that the balance indicated in the electronic gift certificate information increases by the sum of the total amount accumulated by the user and the premium of the electronic gift certificates. The timing at which the electronic gift certificates are granted to the user may be at a time other than maturity. The accumulation processing execution unit 102 may also update the user's electronic gift certificate information so that the electronic gift certificates are granted to the user before the accumulation matures.

[0058] [4. Processing executed by the accumulation system] Figure 8 shows an example of the processing performed by the accumulation system 1. Figure 8 shows the processing related to the accumulation of electronic money among the processing performed by the accumulation system 1. The control units 11 and 21 execute the programs stored in the storage units 12 and 22, respectively, thereby executing the processing shown in Figure 8. The steps in Figure 8 are an example of an accumulation method. Figure 8 shows the processing performed when the user performs an operation to display the objective specification screen SC1.

[0059] As shown in Figure 8, when the user performs an operation to display the objective specification screen SC1, the server 10 executes a process to display the objective specification screen SC1 with the user terminal 20 (S1). When the user selects button B10, the server 10 executes a process to display the savings condition specification screen SC2 with the user terminal 20 (S2). When the user specifies savings conditions on the savings condition specification screen SC2, the user terminal 20 sends savings condition information indicating the savings conditions specified by the user to the server 10 (S3).

[0060] Server 10 obtains the deposit condition information from the user terminal 20 (S4). Server 10 stores the deposit condition information in the user database DB3, associating it with the user ID of the logged-in user (S5). When the deposit timing arrives, Server 10 executes the deposit process based on the deposit condition information stored in the user database DB3 (S6), and this process ends.

[0061] [5. Summary of Embodiments] The savings system 1 of this embodiment acquires savings condition information related to the specified savings conditions. Based on the savings condition information, the savings system 1 executes the savings process. As a result, the savings system 1 can realize savings according to the specified purpose, thereby improving user convenience. For example, since savings are executed for a purpose specified by the user, rather than when the user makes savings without specifying a particular purpose, the savings system 1 is more likely to motivate the user to make savings. The savings system 1 can prevent the user from feeling financially burdened by purchasing a large amount of electronic gift certificates at once, or from feeling burdened by the hassle of purchasing electronic gift certificates repeatedly.

[0062] Furthermore, the savings system 1 acquires savings condition information for the product or service specified by the user. Based on the savings condition information for the product or service specified by the user, the savings system 1 executes the savings process. This allows the savings system 1 to realize savings tailored to a clear purpose, such as the product or service specified by the user, thereby increasing user convenience. For example, since users can save for a clear purpose such as a product or service, the savings system 1 is more likely to motivate users to save. Even if the product or service is expensive, the savings system 1 can reduce both the financial and cumbersome burden through its savings mechanism.

[0063] [6. Variant] This disclosure is not limited to the embodiments described above. This disclosure may be modified as appropriate without departing from the spirit of this disclosure.

[0064] Figure 9 shows an example of a function implemented in a modified version. For example, the server 10 includes a total amount management unit 103, a balance increase unit 104, a settlement execution unit 105, a surplus allocation unit 106, a refund execution unit 107, a premium allocation unit 108, a target determination unit 109, a purchase condition determination unit 110, a deposit cancellation unit 111, a starting price information acquisition unit 112, a multi-purpose settlement execution unit 113, and a purchase processing execution unit 114. Each of the total amount management unit 103, balance increase unit 104, settlement execution unit 105, surplus allocation unit 106, a refund execution unit 107, a premium allocation unit 108, a target determination unit 109, a purchase condition determination unit 110, a deposit cancellation unit 111, a starting price information acquisition unit 112, a multi-purpose settlement execution unit 113, and a purchase processing execution unit 114 is implemented by the control unit 11.

[0065] [6-1. Variation 1] For example, in the embodiment, the case of one user accumulating electronic gift certificates was given as an example, but multiple users may jointly accumulate electronic gift certificates. Modification 1 gives an example of multiple users accumulating electronic gift certificates for a common purpose. The common purpose may be goods or services that the multiple users purchase jointly, or it may be a purpose that is not particularly related to goods or services.

[0066] Figure 10 shows an example of a screen displayed on the user terminal 20 in Modification 1. Modification 1 takes the example of multiple users jointly accumulating electronic gift certificates for the purpose of purchasing a graduation trip tour. For example, the server 10 provides the user with a travel reservation service that handles travel products such as tours or accommodations. The user accesses the server 10 by operating the user terminal 20 and searches for the desired tour. From the search results, the user selects a tour they are considering applying for and registers it in their consideration list. The flow of searching for tours, etc., may be the same as that of a publicly known travel reservation service.

[0067] For example, when a user registers a tour to their consideration list, the user terminal 20 displays a purpose specification screen SC1 on the display unit 25, showing the contents of the consideration list, as shown in the upper part of Figure 10. In the example in the upper part of Figure 10, a tour in which four people, including the user, will participate is registered to the consideration list. In the modified example 1, it is assumed that all four people are registered with the travel booking service. The four users jointly accumulate electronic vouchers to purchase the tour. The user displaying the purpose specification screen SC1 applies for the tour on behalf of the group.

[0068] The accumulation condition information acquisition unit 101 in Modification Example 1 acquires accumulation condition information for accumulations made by multiple users, including the user described in the embodiment. In Modification Example 1, the user who specifies the purpose is the user who applies for the tour on behalf of the others. The accumulation condition information in Modification Example 1 shows the user identification information of each of the multiple users making the accumulation. The user identification information may be the user ID described in the embodiment, or it may be the user's name. The user identification information can be any information that can identify the user in some way.

[0069] The deposit conditions for each of the multiple users may be the same or different. If the deposit conditions for each of the multiple users are the same, the deposit condition information will show the deposit conditions common to all of the users. If the deposit conditions for each of the multiple users are different, the deposit condition information will show the deposit conditions for each of the multiple users. In other words, the deposit condition information may show the deposit conditions for each user.

[0070] For example, when the representative user selects button B11 on the purpose specification screen SC1, the user terminal 20 displays the savings condition specification screen SC2 on the display unit 25, as shown in the lower part of Figure 10, which accepts the specification of savings conditions for each of the multiple users. In the example in the lower part of Figure 10, the representative user specifies the participants in the savings in the input form F24. The representative user specifies the savings conditions for each of the multiple users, such as the savings amount, savings period, and bonus month. The savings conditions for each individual user may be other examples described in the embodiment. In the example in the lower part of Figure 10, the savings conditions for each of the multiple users are the same. If multiple types of electronic vouchers are available at the accommodation facility specified by the representative user, the representative user may specify the type of electronic voucher to be used for savings. In this case, the savings conditions indicate the type of electronic voucher specified by the representative user.

[0071] The representative user may specify the information of each of the multiple users participating in the savings plan on the purpose specification screen SC1. For example, the representative user may specify the number of participants in the savings plan on the purpose specification screen SC1. The savings plan conditions may indicate the number of participants specified by the representative user. The representative user does not need to specifically specify the number of participants in the savings plan on the purpose specification screen SC1. The number of tour participants may become the number of savings plan participants.

[0072] For example, when a representative user enters the savings conditions on the savings conditions specification screen SC2 and selects button B23, the user terminal 20 sends savings condition information indicating the savings conditions of each of the multiple users to the server 10. The savings condition information acquisition unit 101 acquires the savings condition information from the user terminal 20 and stores it in the user database DB3. The savings condition information acquisition unit 101 may store the savings condition information in the user database DB3 in association with the user ID of the representative user, or it may store the savings condition information in the user database DB3 in association with the user ID of each of the multiple users participating in the savings.

[0073] In Modification 1, the deposit processing execution unit 102 executes deposit processing for deposits made by multiple users based on deposit condition information. For each user participating in the deposit, the deposit processing execution unit 102 executes deposit processing based on the deposit conditions of that user as indicated by the deposit condition information. This differs from the embodiment in that the deposit processing execution unit 102 executes the deposit processing for each of the multiple users, but the details of each deposit processing are the same as in the embodiment. For example, when the timing for deposit arrives, the deposit processing execution unit 102 executes deposit processing based on the payment method of each of the multiple users.

[0074] The savings system 1 in Modification 1 acquires savings condition information for savings made by multiple users. Based on the savings condition information, the savings system 1 executes the savings process for savings made by multiple users. As a result, the savings system 1 can realize savings of electronic gift certificates made jointly by multiple users, thereby increasing convenience for multiple users. For example, even if the goods or services that multiple users jointly purchase are expensive, the savings system 1 can reduce the financial or troublesome burden through joint savings.

[0075] [6-2. Variation 2] For example, in Modification Example 1, if multiple users are making a joint investment, another user different from those multiple users may join the investment midway through. Hereafter, such other user will be referred to as the mid-term joining user. Modification Example 2 gives an example of one mid-term joining user joining the investment midway through, but multiple mid-term joining users may also join the investment midway through. Multiple mid-term joining users may join the investment at different times.

[0076] Figure 11 shows an example of a savings plan in which a user joins midway through. In the example in Figure 11, three users, A to C, start saving 10,000 yen each month for a one-year period. From the third month of saving, user D joins the savings plan. For example, user D may operate their own user terminal 20 to complete the procedure for joining the savings plan midway, or a representative from users A to C may operate their own user terminal 20 to complete the procedure for joining the savings plan midway. The savings conditions for user D are specified in the procedure for joining midway.

[0077] In Modification 2, the Savings Condition Information Acquisition Unit 101 acquires the savings conditions information of a user who joins the savings plan midway through, before the savings plan matures. The maturity date of the savings plan is the time when the savings period ends. For example, if savings are made monthly, the final month of the savings plan is the maturity date. The specific content of the savings conditions indicated by the savings conditions information of the user who joins the savings plan midway may be the same as that described in the embodiment. For example, the Savings Condition Information Acquisition Unit 101 acquires the savings conditions information of the user who joins the savings plan midway from the user terminal 20 of the user who originally participated in the savings plan, or from the user terminal 20 of the user who joins the savings plan midway.

[0078] For example, the accumulation condition information acquisition unit 101 stores the accumulation condition information in the user database DB3, associating it with at least one of the user IDs of users who were originally participating in the accumulation program and the user IDs of users who joined later. The accumulation condition information acquisition unit 101 may also acquire the accumulation condition information of users who were originally participating in the accumulation program as is, and use it as the accumulation condition information of users who joined later. In Modification Example 2, the case where the accumulation conditions of users who joined later are the same as the accumulation conditions of other users is given as an example, but as in Modification Example 3 described later, the accumulation conditions of users who joined later may be different from the accumulation conditions of other users.

[0079] In Modification 2, the accumulation processing execution unit 102 executes the accumulation processing for a user who joins the accumulation plan midway through, based on the user's accumulation condition information. For example, when the accumulation processing execution unit 102 determines that the accumulation timing has arrived, it executes the settlement for the user who joins the accumulation plan based on the user's accumulation condition information. The accumulation processing execution unit 102 updates the user's accumulation status information to indicate that the current accumulation has been made. This differs from the embodiment and Modification 1 in that it handles the accumulation processing for users who join the plan midway through, but the accumulation processing itself may be the same as in the embodiment and Modification 1.

[0080] In the example of Modification 2, a user who joins the savings plan midway through is given, but conversely, a user who is participating in the savings plan may also leave it midway. In this case, the savings conditions of other users may or may not be changed. If a user leaves the savings plan midway, the savings processing execution unit 102 will not perform the savings processing for that user thereafter. Users who leave the savings plan midway may be offered a refund.

[0081] In Modification 2, the savings system 1 obtains the savings condition information of a user who joins the savings plan midway through, before the maturity date of the savings plan. When a user joins the savings plan midway through, the savings system 1 executes the savings process for the user based on the user's savings condition information. This allows users to join the savings plan midway through, thus improving convenience for both users who were originally participating in the savings plan and users who join midway.

[0082] [6-3. Modification 3] For example, in Modification Example 2, we took the case where the savings conditions for a user who joins midway are the same as those for a user who was originally participating in the savings program. However, multiple savings methods may be available for users who join midway to choose from. The savings methods can also be considered as the specific details of the savings conditions. Data indicating the multiple savings methods available to users who join midway is stored in the data storage unit 100.

[0083] For example, the accumulation methods could be: (Accumulation Method 1) A user who joins midway pays a lump sum when joining the accumulation program and then accumulates under the same accumulation conditions as users who were originally participating; (Accumulation Method 2) A user who joins midway does not pay a lump sum when joining the accumulation program and accumulates under the same accumulation conditions as users who were originally participating; or (Accumulation Method 3) A user who joins midway does not pay a lump sum when joining the accumulation program and ultimately accumulates an amount equal to the total amount accumulated by users who were originally participating. In Modification Example 3, it is assumed that these three accumulation methods are available.

[0084] Figure 12 shows an example of a screen displayed on the user terminal 20 of a user who joins midway through the program. For example, if a user joins the program midway through, the user terminal 20 displays a program selection screen SC3 on the display unit 25, which accepts the user's selection of a program selection method. In the example in Figure 12, the program selection screen SC3 allows the user to select one of three program selection methods. The user can choose any program selection method from programs 1 to 3. Each of the program selection methods 1 to 3 has corresponding program selection conditions. The server 10 generates program selection condition information indicating the program selection conditions for each program selection method and sends it to the user terminal 20.

[0085] For example, Server 10 calculates the lump sum payment in Savings Method 1 based on the savings status information of the savings plan joined by the user who joins midway. Server 10 may calculate the lump sum payment as the total amount that the users who were originally participating in the savings plan have saved up to that point, or it may calculate a different amount as the lump sum payment. Server 10 may also calculate the savings conditions in Savings Method 3 based on the period from when the user joins midway until maturity, and the total amount saved per person in the savings plan. Based on these calculation results, Server 10 may display the Savings Method Specification Screen SC3 on the user terminal 20.

[0086] In Modification Example 3, the accumulation condition information acquisition unit 101 acquires accumulation condition information corresponding to the accumulation method selected by the user who joined midway through the program, from among multiple accumulation methods. For example, the user terminal 20 of the user who joined midway transmits accumulation condition information corresponding to the accumulation method specified on the accumulation method specification screen SC3. The accumulation condition information acquisition unit 101 acquires the accumulation condition information corresponding to the accumulation method specified by the user who joined midway through the program from the user terminal 20 and stores it in the user database DB3 as the accumulation condition information of the user who joined midway through the program. The accumulation condition information acquisition unit 101 may store the accumulation condition information of the user who joined midway through the program in association with the user ID of the user who joined midway through the program, or it may store the accumulation condition information of the user who joined midway through the program in association with the user ID of the user who was originally participating in the program.

[0087] The accumulation processing execution unit 102 in Modification 3 executes the accumulation processing for the user who joined midway, based on the accumulation condition information corresponding to the accumulation method selected by the user who joined midway. It differs from Modification 2 in that the accumulation condition information corresponding to the accumulation method selected by the user who joined midway is referenced in the accumulation processing, but otherwise it is the same as Modification 2. The details of the accumulation processing may be the same as in Modification 2.

[0088] In the modified example 3, the savings system 1 acquires savings condition information corresponding to the savings method selected by the user who joins midway through the program, from among several savings methods. Based on the savings condition information corresponding to the savings method selected by the user who joins midway through the program, the savings system 1 executes the savings process for the user who joins midway through the program. As a result, the savings system 1 can execute the savings process according to the savings method desired by the user who joins midway through the program, thereby improving convenience for the user who joins midway through the program.

[0089] [6-4. Modification 4] For example, in Modifications 1-3, while multiple users are jointly making savings, the total amount of savings by all users may be managed. The total amount of savings is the sum of the savings made by each user. In Modification 4, when the savings mature, the balance of each user's electronic voucher increases. That is, the total amount of savings is distributed to each user. In addition to the total amount of savings, the breakdown of savings made by each individual user may be managed separately.

[0090] The savings system 1 of Modified Example 4 includes a total amount management unit 103 and a balance increase unit 104. The total amount management unit 103 manages the total amount of savings made by each of the multiple users based on the savings process before the savings maturity date arrives. For example, when the savings status information of each of the multiple users is updated by the savings process, the total amount management unit 103 obtains the savings amount indicated by the savings status information of each of the multiple users and calculates the total amount of savings by summing the savings amounts made by each of the multiple users up to the present. The total amount management unit 103 manages the calculated total amount of savings by storing it in the user database DB3.

[0091] The total amount management unit 103 may manage the total amount of accumulated funds by storing the total amount in a database other than the user database DB3, a computer other than the server 10, or an information storage medium. When the total amount of accumulated funds is requested from the user terminal 20, the total amount management unit 103 may send information indicating the total amount of accumulated funds to the user terminal 20. The user terminal 20 may then display the total amount of accumulated funds on the user terminal 20 based on this information.

[0092] In Modification 4, the balance increase unit 104 increases the balance of an electronic voucher for a user based on the amount each user has contributed when the deposit matures. For example, the balance increase unit 104 calculates the increase in the balance of each user's electronic voucher by dividing the total amount of deposits managed in the user database DB3 by the number of participants who took part in the deposit. The balance increase unit 104 updates the electronic voucher information held by each user so that the balance of each user's electronic voucher increases by the calculated increase amount.

[0093] Furthermore, the increase in the balance of electronic vouchers for each user may differ from one another. For example, if the accumulated amounts indicated by the respective accumulation conditions of multiple users differ from one another, the balance increase unit 104 may update the electronic voucher information held in the user database DB3 so that the balance increases by the amount corresponding to the accumulated amount of each of the multiple users. If the total accumulated amount of each user is indicated in the accumulation status information, the balance increase unit 104 only needs to update the electronic voucher information held by that user so that the balance of that user's electronic vouchers increases by the total accumulated amount indicated in the accumulation status information of that user.

[0094] Furthermore, a user may recruit other users to make joint savings. In this case, a reward (for example, an increase similar to a premium, or an incentive different from a premium) may be granted each time an additional user joins (for example, when the total number of users reaches a predetermined number). The granting of rewards may be performed by the premium granting unit 108 or by other functions other than the premium granting unit 108. Such rewards can also generate benefits for the other users making joint savings when the savings mature.

[0095] In Modification 4, the savings system 1 manages the total amount of savings made by each of multiple users based on the savings process before the savings mature. When the savings mature, the savings system 1 increases the balance of each user's electronic voucher based on the amount of savings made by each of the multiple users. This allows users to understand the total amount of savings, thus improving user convenience. For example, users can easily understand the total amount of savings as a whole without having to calculate the total amount of savings made by each individual user.

[0096] [6-5. Variation 5] For example, in Modification 4, we took the example of a case where the accumulated amount is distributed to each of the multiple users when the savings plan matures. However, in savings plans made jointly by multiple users, the savings may be made from a single common balance. Hereafter, this balance will be referred to as the common balance. The common balance is different from the balances held by individual users. There is one common balance for multiple users participating in a savings plan. If one user participates in multiple savings plans, there is a common balance for each savings plan.

[0097] The accumulation system 1 in Modification 5 includes a total amount management unit 103 and a settlement execution unit 105. The total amount management unit 103 in Modification 5 manages the total amount of each user's accumulation amount in a common balance, which is the balance of electronic vouchers common to multiple users, before the accumulation maturity date arrives. In Modification 5, the electronic voucher information held in the common balance is stored in the user database DB3. The total amount management unit 103 updates the electronic voucher information held in the common balance each time an accumulation process is executed before the accumulation maturity date arrives, so that it increases by the total amount of the accumulation amount for the current accumulation. The electronic voucher information held in the common balance may be stored in a database other than the user database DB3, a computer other than the server 10, or an information storage medium.

[0098] In Modification 5, the settlement execution unit 105 executes a settlement for a user-specified purpose based on the common balance when the savings plan matures. The settlement for a user-specified purpose is a settlement for the purchase of goods or services specified by the user. For example, the settlement execution unit 105 updates the electronic money information held in the common balance so that the common balance decreases by the price of the goods or services specified by the user. The settlement using the electronic money itself may be the same as known processing.

[0099] In Modification 5, the savings system 1 manages the total amount of savings made by multiple users in a common balance before the savings mature. When the savings mature, the savings system 1 executes a settlement for the purpose based on the common balance. This allows users to understand the total amount of savings in the common balance, thus improving user convenience. For example, when the savings mature, users can execute a settlement for the goods or services that were the purpose of the savings using the common balance, so the savings system 1 can also improve user convenience in settlement.

[0100] [6-6. Variation 6] For example, in Modification 5, there may be a surplus in the common balance after the payment for the target goods or services has been processed. In this case, the surplus of the common balance may be given to at least one of the multiple users who participated in the savings plan. Modification 6 gives an example where the surplus is given to all of the multiple users, but the surplus may be given to only some of the multiple users. The user to whom the surplus is given may be any user, for example, the representative user.

[0101] The accumulation system 1 of Modification 6 includes a surplus allocation unit 106. When a settlement is executed, the surplus allocation unit 106 allocates the surplus amount that was not used in the settlement to at least one of the multiple users. The surplus is the common balance after the settlement is executed by the settlement execution unit 105. The surplus is the amount obtained by subtracting the settlement amount from the total amount of the accumulation. Allocating the surplus means increasing the balance of the electronic money held by the user based on the surplus. The surplus allocation unit 106 calculates the amount to be allocated to the user who is eligible for allocation based on the surplus.

[0102] For example, if the surplus is to be distributed to multiple users, the surplus distribution unit 106 may calculate the amount to be distributed to each user by dividing the surplus equally. The surplus distribution unit 106 may also calculate the amount to be distributed to each user based on a predetermined ratio. If any of the multiple users specify the amount to be distributed, the surplus distribution unit 106 may distribute electronic vouchers to each user based on the specified amount. The surplus distribution unit 106 updates the electronic voucher information of the user to which the distribution is to be distributed so that the balance of the electronic vouchers held by that user increases by the amount of the determined distribution amount.

[0103] In the modified version 6, the accumulation system 1 grants at least one of the multiple users the surplus amount of the total that was not used in the payment when a payment is executed. This allows users to receive the surplus amount that was not used in the payment after the payment for the desired goods or services has been completed, thus preventing the surplus from going to waste and improving user convenience.

[0104] [6-7. Variation 7] For example, in Modifications 1-6, benefits may be given in proportion to the number of participants in the savings plan. Benefits are advantages to the user. Modification 7 gives an example where the premium corresponds to the benefit, but benefits are not limited to premiums. For example, benefits may be discounts on savings plans, premium increases, coupons, discounts on the target product or service, points, electronic money, product vouchers, service vouchers, or other benefits. The methods for granting these benefits to the user may be the same as known methods.

[0105] In the modified example 7, the accumulation processing execution unit 102 executes the accumulation process based on the accumulation condition information and the benefits corresponding to the number of users. The benefit data showing the relationship between the number of participants in the accumulation and the benefits is stored in the data storage unit 100. The benefit data may be set so that the more participants there are, the better the benefits. Conversely, the benefit data may be set so that the fewer participants there are, the better the benefits. A good benefit means that the monetary value represented by the benefit is high. If the benefit is a premium, then a high premium corresponds to a good benefit.

[0106] For example, the accumulation processing execution unit 102 identifies a reward associated with the number of participants indicated by the accumulation condition information, based on the reward data. The accumulation processing execution unit 102 executes the accumulation process so that the reward is granted. If the reward is a premium, the accumulation processing execution unit 102 determines the amount of the premium so that the premium increases with the number of participants, and executes the accumulation process based on the amount of the premium. If the reward is a discount on the accumulation amount, the accumulation processing execution unit 102 determines the settlement amount so that the discount amount increases with the number of participants, and executes the accumulation process based on the settlement amount. Similarly for other rewards, the accumulation processing execution unit 102 executes the accumulation process so that the reward corresponding to the number of participants is granted to the user. The accumulation process in Modification Example 7 includes the process of granting the reward to the user.

[0107] The savings system 1 in Modification 7 executes the savings process based on savings condition information and benefits corresponding to the number of users. As a result, users can receive benefits according to the number of participants in the savings plan, thus enhancing user convenience. For example, if the premium increases with the number of participants in a savings plan, the savings system 1 can incentivize users to increase the number of participants in the savings plan.

[0108] [6-8. Variation 8] For example, a user may combine multiple types of electronic vouchers to accumulate funds for a purpose they specify. The accumulation condition information acquisition unit 101 in Modification Example 8 acquires accumulation condition information for a combination of multiple types of electronic vouchers that the user can use for a purpose. In Modification Example 8, the accumulation condition information shows the accumulation conditions for each of the multiple types of electronic vouchers. That is, the accumulation condition information shows the accumulation conditions for each type of electronic voucher.

[0109] For example, suppose a user can use "AAA gift certificates" and "BBB gift certificates" to purchase a product or service of their choosing. In this case, the user specifies the accumulation conditions for "AAA gift certificates" and "BBB gift certificates" on the accumulation conditions specification screen SC2. The user terminal 20 transmits accumulation condition information to the server 10, showing the accumulation conditions for each of these multiple types of electronic gift certificates. The accumulation condition information acquisition unit 101 acquires the accumulation condition information showing the accumulation conditions for each of the multiple types of electronic gift certificates from the user terminal 20 and stores it in the user database DB3.

[0110] In Modification 8, the accumulation processing execution unit 102 executes accumulation processing for a combination of multiple types of electronic vouchers based on accumulation condition information. For example, the accumulation processing execution unit 102 executes accumulation processing for each type of electronic voucher based on the accumulation conditions of each of the multiple types of electronic vouchers indicated by the accumulation condition information. That is, for each type of electronic voucher, the accumulation processing execution unit 102 executes accumulation processing for that type of electronic voucher based on the accumulation conditions of that type of electronic voucher. The accumulation processing execution unit 102 differs from the embodiment and Modifications 1 to 7 in that it executes accumulation processing for each of the multiple types of electronic vouchers for a single purpose specified by the user, but the accumulation processing for each individual type of electronic voucher may be the same as in the embodiment and Modifications 1 to 7.

[0111] The savings system 1 in Modification 8 acquires savings condition information for savings that combine multiple types of electronic gift certificates. Based on the savings condition information, the savings system 1 executes the savings process for savings that combine multiple types of electronic gift certificates. As a result, users can make savings that combine multiple types of electronic gift certificates, and the savings system 1 can improve user convenience. For example, even if the product or service specified by the user is an expensive product or service that cannot be purchased with only one type of electronic gift certificate, the user can purchase such a product or service by making savings that combine multiple types of electronic gift certificates.

[0112] [6-9. Modification 9] For example, a user may stop making contributions before the contribution period ends. Stopping contributions means the user stops contributing midway through the plan. The user can apply to stop contributions by any means. For example, the user may access the server 10 operated by the user terminal 20 and apply through a screen for requesting to stop contributions. The user may also contact a call center that accepts requests to stop contributions and apply to stop their contributions.

[0113] For example, if a user requests to cancel their savings plan, the server 10 stores cancellation request information in the user database DB3, indicating that the user has requested to cancel the savings plan. If the request is made by contacting the call center, the cancellation request information is stored in the user database DB3 by the call center operator. The server 10 may also store the cancellation request information in a database other than the user database DB3, on another computer other than the server 10, or on an information storage medium.

[0114] The savings system 1 of Modification 9 includes a refund execution unit 107. When a user cancels their savings, the refund execution unit 107 executes a refund to the balance of the user's payment method, which is a payment method other than electronic money. The payment method to which the refund is made may be any payment method that has a balance. For example, the refund execution unit 107 may execute a refund to electronic money, a balance not classified as electronic money, crypto assets, or the balance of another payment method.

[0115] Modification 9 provides an example where a refund is made to a payment method managed by the business operator managing the electronic money that is the subject of the accumulation, or to a payment method managed by an affiliated company of the said business operator. The refund in Modification 9 is a process of increasing the balance of the payment method. The process of increasing the balance of a payment method such as electronic money may be the same as known processes. For example, the refund execution unit 107 increases the balance by requesting the computer that manages the balance of the payment method such as electronic money to increase the balance.

[0116] For example, the refund execution unit 107 executes a refund based on the amount of savings accumulated by the user up to a certain point. The refund amount may be the same as the accumulated amount, or it may be less than the accumulated amount. The refund amount may include the premium, or it may be the amount excluding the premium. The refund execution unit 107 obtains the accumulated amount of the user who applied to stop accumulating savings based on the accumulation status information stored in the user database DB3. The refund execution unit 107 obtains the accumulated amount as the refund amount, or obtains the accumulated amount minus the handling fee as the refund amount. The refund execution unit 107 executes the refund by increasing the balance of the payment method by the amount of the refund.

[0117] In the modified example 9, the savings system 1 refunds the user's balance to a payment method different from the electronic gift certificate if the user stops saving. This allows the user to receive a refund in a payment method with a balance even if they stop saving, thus improving user convenience. For example, if the refund is made to a payment method managed by the business that manages the electronic gift certificate that is the subject of the savings, or to a payment method managed by an affiliate of that business, the savings system 1 can also be configured so that the funds saved by the user are used in the payment methods of these businesses.

[0118] [6-10. Variation 10] For example, in Modification 9, the process for handling refunds when a user stops making contributions was explained, but the user may also be granted a premium at that time when they stop making contributions. In Modification 10, instead of a refund being issued when a user stops making contributions, the user is given an electronic voucher corresponding to the amount of contributions at that time, but in Modification 10 as well, a refund similar to that in Modification 9 may be implemented.

[0119] The accumulation system 1 of the modified version 10 includes a premium granting unit 108. When a user stops accumulating, the premium granting unit 108 grants the user a premium corresponding to the time the user stopped accumulating. The premium corresponding to the time of cancellation is a premium whose amount varies depending on the time of cancellation. When the premium granting unit 108 grants a premium to a user, it means that the premium granting unit 108 grants the user an electronic gift certificate equivalent to the premium, or the premium granting unit 108 performs a refund equivalent to the premium.

[0120] The relationship between the cancellation point and the premium may be shown in the premium information stored in the electronic money database DB1, or in other information. The premium granting unit 108 grants the user the premium associated with the cancellation point indicated in the premium information or other information. For example, the relationship between the period from the start of the accumulation to the cancellation point and the premium granted may be defined in the premium information or other information. The premium granting unit 108 may determine the premium such that the shorter the period from the start of the accumulation to the cancellation point, the lower the premium. That is, the premium granting unit 108 may determine the premium such that the longer the period from the start of the accumulation to the cancellation point, the higher the premium.

[0121] For example, the relationship between the period from the time of discontinuation of the investment to maturity and the premium to be awarded may be defined in premium information or other information. The premium awarding unit 108 may determine the premium such that the shorter the period from the time of discontinuation of the investment to maturity, the greater the premium. That is, the premium awarding unit 108 may determine the premium such that the longer the period from the time of discontinuation of the investment to maturity, the less the premium. The premium awarding unit 108 awards the user the premium determined as described above.

[0122] In modified version 10, the savings system 1 grants the user a premium corresponding to the time the user stopped saving, if the user stops saving. This allows the user to receive a premium corresponding to the time of cancellation, even if they stop saving, thus improving the convenience of the savings system 1 for the user. For example, since the user can receive some kind of premium even if they stop saving, they can start saving with peace of mind.

[0123] [6-11. Variation 11] For example, if a user meets certain conditions, a discount on their savings amount may be offered as a benefit to the user. Alternatively, if a user meets certain conditions, their premium may be increased as a benefit to the user. Thus, Variation 11 explains a case where a benefit related to savings is offered when a user meets certain conditions.

[0124] The savings system 1 of the modified example 11 includes an eligibility determination unit 109. The eligibility determination unit 109 determines whether a user is eligible for benefits related to savings based on user information about the user. User information can be any information about the user. For example, user information may be personal information, demographic information, usage history of various services such as e-commerce services, behavioral history detected from the user terminal 20, or other information.

[0125] In Modification 11, the case where user information is stored in the user database DB3 is given as an example, but user information may also be stored in a database other than the user database DB3, a computer other than the server 10, or an information storage medium. The target determination unit 109 obtains user information of the user who applied for the savings plan from the user database DB3, the other database, the other computer, or the information storage medium. Based on the obtained user information, the target determination unit 109 determines whether or not the user is eligible for the benefit.

[0126] A benefit is an advantage that is incurred by a user who makes a regular contribution. For example, a benefit may be a discount on the contribution or an increase in the premium. To be eligible for a benefit, the user must meet the conditions for the benefit to be granted. Eligibility for a benefit can be any condition that can be determined based on user information. For example, conditions that qualify for a benefit may include the user being of a certain age or age group, the user being a student, the user working in a certain area or for a certain company, the user being a mother, the user being a father, the user living in a certain area, or other conditions.

[0127] For example, the eligibility determination unit 109 may determine whether a user is eligible for a benefit by determining whether the user's age or age group obtained from the user information is a predetermined age or age group. The eligibility determination unit 109 may also determine whether a user is eligible for a benefit by determining whether the user's occupation obtained from the user information is a student. The eligibility determination unit 109 may also determine whether a user is eligible for a benefit by determining whether the area or company where the user works, obtained from the user information, is a predetermined area or company. Similarly, for other conditions, the eligibility determination unit 109 can determine whether the user meets the conditions for eligibility for a benefit based on the user information.

[0128] In the modified example 11, the accumulation condition information acquisition unit 101 acquires accumulation condition information corresponding to the benefit when it is determined that the user is eligible for the benefit. For example, when the accumulation condition information acquisition unit 101 is determined to be eligible for the benefit, it acquires accumulation condition information in which the accumulation amount is set so that the accumulation amount is discounted compared to when the user is determined not to be eligible for the benefit. When the accumulation condition information acquisition unit 101 is determined to be eligible for the benefit, it acquires accumulation condition information in which the premium is set so that the premium is higher than when the user is determined not to be eligible for the benefit. It is assumed that information indicating the benefit that will occur when the user is eligible for the benefit is stored in the data storage unit 100. The accumulation condition information acquisition unit 101 only needs to acquire the accumulation condition information in which the benefit indicated in said information will occur.

[0129] The accumulation processing execution unit 102 executes the accumulation process based on the accumulation condition information corresponding to the benefit when it is determined that the user is eligible for the benefit. For example, the accumulation processing execution unit 102 executes the accumulation process based on the accumulation amount (accumulation amount with discount applied) indicated by the accumulation condition information. The accumulation processing execution unit 102 executes the accumulation process based on the premium (premium including the increase corresponding to the benefit) indicated by the accumulation condition information. Although it differs from the embodiment and modifications 1 to 10 in that a discount is applied or the premium increases, the accumulation process itself may be the same as in the embodiment and modifications 1 to 10.

[0130] In the modified example 11, the savings system 1 determines whether a user is eligible for a benefit based on user information. If the savings system 1 determines that a user is eligible for a benefit, it obtains savings condition information corresponding to the benefit. If the savings system 1 determines that a user is eligible for a benefit, it executes the savings process based on the savings condition information corresponding to the benefit. As a result, if a user is eligible for a benefit, they can make savings under the savings conditions corresponding to the benefit, thus improving user convenience.

[0131] [6-12. Variation 12] For example, the electronic gift certificates eligible for accumulation may have purchase conditions set for their purchase. These purchase conditions may be the same as those used for publicly known electronic gift certificates. For example, the purchase conditions may be the user's age or age group, the area in which the user resides, the area or company where the user works, the user's occupation, or other conditions. Modification 12 gives an example of a case where a user accumulates electronic gift certificates for which purchase conditions are set.

[0132] For example, when a user applies for a savings plan by specifying savings conditions from the savings conditions specification screen SC2, the server 10 determines, based on the user information, whether the user meets the purchase conditions for the electronic gift certificate to be saved. The purchase conditions are defined in the electronic gift certificate database DB1. The server 10 determines, based on the user information and the purchase conditions defined in the electronic gift certificate database DB1, whether the user meets the purchase conditions. If the server 10 determines that the user does not meet the purchase conditions, it does not accept the savings application, and if it determines that the user meets the purchase conditions, it accepts the savings application. The savings processing after the savings application is accepted may be the same as in the embodiment and modifications 1 to 11.

[0133] For example, if the user's age or age group is defined as a purchase condition, the server 10 determines whether the user's age or age group obtained from the user information is the age or age group defined as a purchase condition. If the user's residential area is defined as a purchase condition, the server 10 determines whether the area obtained from the user information is the area defined as a purchase condition. Similarly for other purchase conditions, the server 10 can determine whether the purchase condition is met based on the user information and then decide whether to accept the investment application based on the determination result. A user may no longer meet the purchase conditions before the investment matures. In this case, the investment may be stopped midway.

[0134] The savings system 1 of Modification 12 includes a purchase condition determination unit 110 and a savings cancellation unit 111. Before the maturity date of the savings, the purchase condition determination unit 110 determines, based on user information about the user, whether the user no longer meets the purchase conditions specified for the electronic gift certificate. The purchase condition determination unit 110 determines, before each savings payment is made, whether the user no longer meets the purchase conditions. For example, when the timing for each savings payment arrives, the purchase condition determination unit 110 determines, based on the latest user information, whether the user no longer meets the purchase conditions. If the user meets the purchase conditions, the savings processing execution unit 102 executes the savings processing. The method for determining the purchase conditions is as described above. In Modification 12, the purchase condition determination unit 110 determines whether the user no longer meets the purchase conditions.

[0135] The deposit cancellation unit 111 cancels deposits when it determines that the user no longer meets the purchase conditions. The deposit cancellation unit 111 cancels deposits by preventing the deposit process from being executed for users who no longer meet the purchase conditions. For example, the deposit cancellation unit 111 cancels deposits by storing deposit cancellation information, indicating that the deposit has been cancelled, in the user database DB3. The deposit processing execution unit 102 does not execute deposit processing for deposits for which deposit cancellation information has been stored. The deposit processing execution unit 102 executes deposit processing for deposits for which deposit cancellation information has not been stored. The deposit cancellation unit 111 may store the deposit cancellation information in a database other than the user database DB3, a computer other than the server 10, or an information storage medium.

[0136] The method by which the installment cancellation unit 111 cancels installments is not limited to the above example. The installment cancellation unit 111 can cancel installments for users who no longer meet the purchase conditions. For example, the installment cancellation unit 111 may cancel installments by deleting the installment condition information of users who no longer meet the purchase conditions from the user database DB3. The installment cancellation unit 111 may also cancel installments by other methods.

[0137] In modification 12, the savings system 1 determines, based on user information, whether the user no longer meets the purchase conditions specified for the electronic gift certificate before the savings maturity date. If the savings system 1 determines that the user no longer meets the purchase conditions, it stops the savings. This prevents the savings system 1 from allowing the user to accumulate electronic gift certificates in a subsequent period even if the user no longer meets the purchase conditions during the savings period.

[0138] [6-13. Variation 13] For example, if a user makes a savings plan with the intention of purchasing a product or service, the price of the product or service may increase from the time the savings plan begins. In this case, even when the savings plan matures, the price of the product or service may exceed the total amount of savings, potentially preventing the user from purchasing the product or service. Therefore, Modification 13 explains a case where the price of the product or service at the time the user started saving is guaranteed.

[0139] The savings system 1 in Modification 13 includes a settlement execution unit 105 and an initial price information acquisition unit 112. The initial price information acquisition unit 112 acquires initial price information relating to the price of the goods or services specified by the user as the purpose, at the time the savings plan begins. The initial price information indicates the price of the goods or services at the time the savings plan begins. The start of the savings plan may be at the same time as the application for the savings plan. In Modification 13, when the price of the goods or services changes, the price information in the search target database DB2 is also updated.

[0140] For example, when a user applies for a savings plan by specifying a product or service, the initial price information acquisition unit 112 acquires price information from the search target database DB2 that shows the current price of the product or service specified by the user. The initial price information acquisition unit 112 stores this price information as initial price information in the user database DB3. The initial price information acquisition unit 112 may also store the initial price information in a database other than the user database DB3, a computer other than the server 10, or an information storage medium. The initial price information acquisition unit 112 may acquire initial price information from the user database DB3, another database, another computer, or an information storage medium.

[0141] The settlement execution unit 105 executes a settlement for a product or service when the accumulation matures, based on the electronic voucher on which the accumulation was made and the initial price information. The settlement execution unit 105 executes the settlement based on the initial price information, not the current price information of the product or service specified by the user. For example, the settlement execution unit 105 executes the settlement so that the electronic voucher on which the accumulation was made is used up to the amount indicated by the initial price information. The settlement execution unit 105 may reduce the balance of the electronic voucher so that the balance of the electronic voucher decreases by the amount indicated by the initial price information. The settlement execution unit 105 may reduce the number of electronic vouchers so that the number of electronic vouchers decreases by the amount indicated by the initial price information.

[0142] The settlement execution unit 105 is not limited to the above example in which it executes settlement based on the initial price information. For example, the settlement execution unit 105 may perform settlement by discounting the price indicated by the initial price information. The discount amount may be a fixed amount, an amount corresponding to the price indicated by the initial price information, an amount corresponding to the accumulated amount, or an amount corresponding to the accumulated period. If the price indicated by the initial price information is higher than the current price, the settlement execution unit 105 may perform settlement based on the current price. The settlement execution unit 105 may perform a comparison between the price indicated by the initial price information and the current price, and based on the result of the comparison, decide which of the two prices to use for settlement.

[0143] The savings system 1 in Modification 13 acquires initial price information. When the savings plan matures, the savings system 1 executes a settlement for goods or services based on the electronic voucher used for the savings and the initial price information. This allows the user to purchase goods or services at the initial price at which the savings plan was initiated, thus enhancing user convenience.

[0144] [6-14. Variation 14] For example, even if a user uses electronic gift certificates for a purpose they specified, they may still have leftover electronic gift certificates. Example 14 describes a case where a user uses leftover electronic gift certificates for another purpose. This other purpose may be a different product or service than the one specified by the user when accumulating the electronic gift certificates, or it may be a purpose unrelated to the product or service (for example, giving the electronic gift certificates as a gift). Other purposes may include sending money to others, converting it to electronic money, or donating it to a local government or similar entity.

[0145] The accumulation system 1 of Modification 14 includes a multi-purpose settlement execution unit 113. When the accumulation matures and settlement for the purpose is executed, the multi-purpose settlement execution unit 113 executes settlements for purposes other than the original purpose based on the surplus of electronic vouchers. The surplus of electronic vouchers is the amount obtained by subtracting the settlement amount for goods or services specified by the user from the total amount of electronic vouchers accumulated by the user. The surplus of electronic vouchers can also be said to be the amount held by the user as indicated by the electronic voucher information after settlement (for example, the balance or number of electronic vouchers after settlement).

[0146] For example, the multi-purpose payment execution unit 113 uses the surplus of the electronic gift certificate to execute a payment for the purchase of other goods or services different from the goods or services specified by the user at the time of deposit. The user searches for other goods or services to purchase for other purposes using the e-commerce service and adds them to the shopping cart. The multi-purpose payment execution unit 113 uses the surplus of the electronic gift certificate to execute a payment for the other goods or services that the user has added to the shopping cart for other purposes. Similarly, if the user uses the surplus of the electronic gift certificate for purposes other than purchasing goods or services, the multi-purpose payment execution unit 113 should execute a payment for those purposes based on the surplus of the electronic gift certificate.

[0147] In the modified version 14, when the savings plan matures and a settlement for the intended purpose is executed, the savings system 1 uses the surplus electronic funds to execute a settlement for a different purpose. This allows the user to use the surplus for other purposes, thus enhancing user convenience.

[0148] [6-15. Variation 15] For example, when a user's savings plan matures, they are likely to use the electronic voucher on which the savings were made to purchase the desired product or service. Therefore, Modification 15 explains a case where the user can use the electronic voucher directly.

[0149] The savings system 1 of Modification 15 includes a purchase processing execution unit 114. When the savings period ends, the purchase processing execution unit 114 executes a purchase process for the purpose based on the electronic gift certificates on which the savings were made. The purchase process may be the settlement of the object that is the purpose of the savings (for example, goods or services), or it may be an intermediate process leading up to the settlement. The intermediate process may be the display of a screen for settlement confirmation, the display of the total amount of electronic gift certificates used for the purchase, the display of other screens for the purchase, or other processes. Since the information on the electronic gift certificates on which the savings were made is stored in the savings status information or held electronic gift certificate information of the user database DB3, the purchase processing execution unit executes the purchase process based on the savings status information or held electronic gift certificate information.

[0150] For example, if the purpose information indicates a purpose specified by the user, when the savings plan matures, the purchase processing execution unit 114 may execute a process to display a button such as "Purchase using electronic gift certificates" on the purpose specification screen SC1 in Figure 2 as a purchase process. When the user selects this button, the purchase processing execution unit 114 may execute a process to display a purchase screen for the user to purchase the product on the user terminal 20 as a purchase process. The purchase processing execution unit 114 may also execute the subsequent payment of the product as a purchase process.

[0151] For example, if the purpose information indicates a purpose specified by the issuer of the electronic voucher (e.g., a store), a button for saving may be displayed near the store on the screen where the user's favorite stores registered in the e-commerce service are displayed. The user may select this button and specify the saving conditions to make a purchase of goods from that store. The purchase processing execution unit 114 may also execute a process to display a button that allows the user to transition to the store's screen when the savings maturity date arrives, as part of the purchase process. The purchase processing execution unit 114 may also execute a process to display the store's screen on the user terminal 20 when the user selects this button, as part of the purchase process.

[0152] For example, if the purpose information indicates a purpose specified by the operator or business operator of the platform that provides electronic gift certificates, then a mini-app in the application of the service provided by the operator or business operator may allow users to accumulate electronic gift certificates that can be used at participating merchants of the service. The purchase processing execution unit 114 may execute a process as a purchase process that makes the user able to use the electronic gift certificate at participating merchants from the application when the accumulation matures. This process may also be a process that sets the electronic gift certificate as the payment source in the application.

[0153] In the modified example 15, the savings system 1 executes a purchase process based on the electronic vouchers used for the savings when the savings period matures. This allows the user to directly purchase the desired goods or services using the electronic vouchers used for the savings, thus enhancing user convenience.

[0154] [6-16. Other variations] For example, the above variations may be combined.

[0155] For example, while we have described the case where savings system 1 is applied to e-commerce services or travel booking services, savings system 1 is applicable to any service. Savings system 1 may be applied to ticket booking services, online flea market services, communication services, financial services, payment services, or other services. Savings system 1 may also be applied to services aimed at the sale of electronic money.

[0156] For example, the functions described as being implemented on server 10 may be implemented on user terminal 20 or other computers. The functions described as being implemented on server 10 may be shared among multiple computers.

[0157] [7. Addendum] For example, the savings system 1 can also be configured as follows:

[0158] (1) Accumulation condition information relating to the accumulation conditions of electronic money certificates usable for a specified purpose, comprising an accumulation condition information acquisition unit that acquires the accumulation condition information specified by the user, A savings processing execution unit that executes savings processing related to the savings based on the savings condition information, A savings system that includes this. (2) The accumulation condition information acquisition unit acquires the accumulation condition information relating to the product or service specified by the user, The aforementioned savings processing execution unit executes the savings processing based on the savings condition information relating to the product or service specified by the user. (1) The savings system described above. (3) The savings condition information acquisition unit acquires the savings condition information for savings made by multiple users, including the user, The accumulation processing execution unit executes the accumulation processing for the accumulation performed by the multiple users based on the accumulation condition information. The savings system described in (1) or (2). (4) The aforementioned savings condition information acquisition unit acquires the savings condition information of a user who joins the savings plan midway through, before the maturity date of the savings plan arrives. The accumulation processing execution unit executes the accumulation processing for the user who joins midway through the accumulation process, based on the accumulation condition information of the user who joins midway through the accumulation process. (3) The savings system described above. (5) The aforementioned savings condition information acquisition unit acquires the savings condition information corresponding to the savings method selected by the user who joined midway through, from among a plurality of savings methods. The accumulation processing execution unit executes the accumulation processing for the user who joined midway, based on the accumulation condition information corresponding to the accumulation method selected by the user who joined midway. (4) The savings system described above. (6) The aforementioned accumulation system is, Before the maturity date of the aforementioned savings, a total amount management unit manages the total amount of savings made by each of the multiple users based on the aforementioned savings process, When the aforementioned savings mature, a balance increase unit increases the balance of the electronic money certificate of each of the multiple users based on the amount of savings made by each of the users, A savings system described in any of (3) to (5), further including the above. (7) The aforementioned accumulation system is, Before the maturity date of the aforementioned savings, a total amount management unit manages the total amount of savings made by each of the aforementioned users using a common balance which is the balance of the aforementioned electronic money certificate common to the aforementioned multiple users, When the aforementioned savings reach maturity, a settlement execution unit executes settlements related to the aforementioned purpose based on the aforementioned common balance, A savings system as described in any of (3) to (6), further including the above. (8) The savings system further includes a surplus allocation unit that, when the settlement is executed, allocates to at least one of the multiple users the surplus amount of the total amount that was not used in the settlement. The savings system described in (7). (9) The savings processing execution unit executes the savings processing based on the savings condition information and the benefits corresponding to the number of users. The savings system described in any of (3) to (8). (10) The accumulation condition information acquisition unit acquires the accumulation condition information for the accumulation which combines multiple types of electronic money that the user can use for the said purpose, The accumulation processing execution unit executes the accumulation processing for the accumulation of the multiple types of electronic vouchers based on the accumulation condition information. The savings system described in any of (1) to (9). (11) The savings system further includes a refund execution unit that, if the user cancels the savings, executes a refund to the user's balance of the payment method, using a payment method different from the electronic voucher. The savings system described in any of (1) to (10). (12) The savings system further includes a premium granting unit that grants the user a premium corresponding to the time the user stopped the savings, which is the time the user stopped the savings. The savings system described in any of (1) to (11). (13) The savings system further includes an eligibility determination unit that determines whether or not the user is eligible for benefits related to the savings, based on user information relating to the user. The accumulation condition information acquisition unit acquires the accumulation condition information corresponding to the benefit when it is determined that the user is eligible for the benefit. The savings processing execution unit, when it is determined that the user is eligible for the benefit, executes the savings process based on the savings condition information corresponding to the benefit. The savings system described in any of (1) to (12). (14) The aforementioned accumulation system is, Before the maturity date of the aforementioned savings plan arrives, a purchase condition determination unit determines, based on user information relating to the user, whether or not the user no longer meets the purchase conditions specified for the electronic gift certificate. If it is determined that the user no longer meets the purchase conditions, the savings cancellation unit cancels the savings, A savings system described in any of (1) to (13), further including the above. (15) The aforementioned accumulation system is, A starting price information acquisition unit acquires starting price information relating to the price of the goods or services specified by the user as the purpose, at the start of the savings plan. When the aforementioned savings mature, a settlement execution unit executes a settlement for the aforementioned goods or services based on the aforementioned electronic gift certificate for which the savings were made and the aforementioned initial price information. A savings system described in any of (1) to (14), further including the above. (16) The savings system further includes a multi-purpose settlement execution unit that, when the savings mature and settlement for the aforementioned purpose is executed, executes settlement for a purpose other than the aforementioned purpose based on the surplus of the electronic money certificate. The savings system described in any of (1) to (15). (17) The savings system further includes a purchase processing execution unit that, when the savings reach maturity, executes a purchase process for purchasing the aforementioned purpose based on the electronic voucher on which the savings were made. The savings system described in any of (1) to (16). [Explanation of Symbols]

[0159] 1 Accumulation System, 10 Server, 11,21 Control Unit, 12,22 Storage Unit, 13,23 Communication Unit, 20 User Terminal, 24 Operation Unit, 25 Display Unit, 100 Data Storage Unit, 101 Accumulation Condition Information Acquisition Unit, 102 Accumulation Processing Execution Unit, 103 Total Amount Management Unit, 104 Balance Increase Unit, 105 Settlement Execution Unit, 106 Surplus Grant Unit, 107 Refund Execution Unit, 108 Premium Grant Unit, 109 Target Determination Unit, 110 Purchase Condition Determination Unit, 111 Accumulation Cancellation Unit, 112 Starting Price Information Acquisition Unit, 113 Other Purpose Settlement Execution Unit, 114 Purchase Processing Execution Unit, N Network, B10,B11,B23 Buttons, DB1 Electronic Voucher Database, DB2 Search Target Database, DB3 User Database, F20,F21,F22,F24 Input form, SC1 Purpose specification screen, SC2 Savings condition specification screen, SC3 Savings method specification screen.

Claims

1. Accumulation condition information relating to the accumulation conditions of electronic money certificates usable for a specified purpose, comprising an accumulation condition information acquisition unit that acquires the accumulation condition information specified by the user, A savings processing execution unit that executes savings processing related to the savings based on the savings condition information, A savings system that includes this.

2. The accumulation condition information acquisition unit acquires the accumulation condition information relating to the product or service specified by the user, The aforementioned savings processing execution unit executes the savings processing based on the savings condition information relating to the product or service specified by the user. The accumulation system according to claim 1.

3. The savings condition information acquisition unit acquires the savings condition information for savings made by multiple users, including the user, The accumulation processing execution unit executes the accumulation processing for the accumulation performed by the multiple users based on the accumulation condition information. The accumulation system according to claim 1 or 2.

4. The aforementioned savings condition information acquisition unit acquires the savings condition information of a user who joins the savings plan midway through, before the maturity date of the savings plan arrives. The accumulation processing execution unit executes the accumulation processing for the user who joins midway through the accumulation process, based on the accumulation condition information of the user who joins midway through the accumulation process. The savings system according to claim 3.

5. The aforementioned savings condition information acquisition unit acquires the savings condition information corresponding to the savings method selected by the user who joined midway through, from among a plurality of savings methods. The accumulation processing execution unit executes the accumulation processing for the user who joined midway, based on the accumulation condition information corresponding to the accumulation method selected by the user who joined midway. The savings system according to claim 4.

6. The aforementioned accumulation system is, Before the maturity date of the aforementioned savings, a total amount management unit manages the total amount of savings made by each of the multiple users based on the aforementioned savings process, When the aforementioned savings mature, a balance increase unit increases the balance of the electronic money certificate of each of the multiple users based on the amount of savings made by each of the users, The accumulation system according to claim 3, further comprising:

7. The aforementioned accumulation system is, Before the maturity date of the aforementioned savings, a total amount management unit manages the total amount of savings made by each of the aforementioned users using a common balance which is the balance of the aforementioned electronic money certificate common to the aforementioned multiple users, When the aforementioned savings reach maturity, a settlement execution unit executes settlements related to the aforementioned purpose based on the aforementioned common balance, The accumulation system according to claim 3, further comprising:

8. The savings system further includes a surplus allocation unit that, when the settlement is executed, allocates to at least one of the multiple users the surplus portion of the total amount that was not used in the settlement. The accumulation system according to claim 7.

9. The savings processing execution unit executes the savings processing based on the savings condition information and the benefits corresponding to the number of users. The savings system according to claim 3.

10. The accumulation condition information acquisition unit acquires the accumulation condition information for the accumulation which combines multiple types of electronic money that the user can use for the said purpose, The accumulation processing execution unit executes the accumulation processing for the accumulation of the multiple types of electronic vouchers based on the accumulation condition information. The accumulation system according to claim 1 or 2.

11. The savings system further includes a refund execution unit that, if the user cancels the savings, executes a refund to the user's balance of the payment method, using a payment method different from the electronic voucher. The accumulation system according to claim 1 or 2.

12. The savings system further includes a premium granting unit that grants the user a premium corresponding to the time the user stopped the savings, which is the time the user stopped the savings. The accumulation system according to claim 1 or 2.

13. The savings system further includes an eligibility determination unit that determines whether or not the user is eligible for benefits related to the savings, based on user information relating to the user. The accumulation condition information acquisition unit acquires the accumulation condition information corresponding to the benefit when it is determined that the user is eligible for the benefit. The savings processing execution unit, when it is determined that the user is eligible for the benefit, executes the savings process based on the savings condition information corresponding to the benefit. The accumulation system according to claim 1 or 2.

14. The aforementioned accumulation system is, Before the maturity date of the aforementioned savings plan arrives, a purchase condition determination unit determines, based on user information relating to the user, whether or not the user no longer meets the purchase conditions specified for the electronic gift certificate. If it is determined that the user no longer meets the purchase conditions, the savings cancellation unit cancels the savings, The accumulation system according to claim 1 or 2, further comprising:

15. The aforementioned accumulation system is, A starting price information acquisition unit acquires starting price information relating to the price of the goods or services specified by the user as the purpose, at the start of the savings plan. When the aforementioned savings mature, a settlement execution unit executes a settlement for the aforementioned goods or services based on the aforementioned electronic gift certificate for which the savings were made and the aforementioned initial price information. The accumulation system according to claim 1 or 2, further comprising:

16. The savings system further includes a multi-purpose settlement execution unit that, when the savings mature and settlement for the aforementioned purpose is executed, executes settlement for a purpose other than the aforementioned purpose based on the surplus of the electronic money certificate. The accumulation system according to claim 1 or 2.

17. The savings system further includes a purchase processing execution unit that, when the savings reach maturity, executes a purchase process for purchasing the aforementioned purpose based on the electronic voucher on which the savings were made. The accumulation system according to claim 1 or 2.

18. Accumulation condition information relating to the accumulation conditions of electronic money certificates usable for a specified purpose, comprising an accumulation condition information acquisition step of acquiring the accumulation condition information specified by the user, A savings processing execution step which executes a savings process related to the savings based on the savings condition information, Savings methods including

19. Accumulation condition information relating to the accumulation conditions of electronic money certificates usable for a specified purpose, wherein an accumulation condition information acquisition unit acquires the accumulation condition information specified by the user. A savings processing execution unit executes savings processing related to savings based on the savings condition information. A program that makes a computer function.

Images