JP7112864B2 - Savings support device, savings support method, and savings support program - Google Patents

Description

The present invention relates to a savings support device, a savings support method, and a savings support program that support a saver who saves money.

Traditionally, savers have set up savings accounts with financial institutions for various purposes, such as saving money for their children's school fees, saving money to buy a house, or saving money for travel expenses. is used. Conventionally, a saver may save for a certain saving purpose using a plurality of accounts. For example, when a husband and wife, who are the parents of a child, save school expenses for their children, the husband may save using the husband's account and the wife may save using the wife's account. Moreover, even if there is only one saver, the saver may save for a certain saving purpose using, for example, a plurality of accounts opened at different financial institutions.

As a prior art, a plurality of child accounts such as a savings account, a life account, and a play account are provided subordinately to a parent account, and a control unit controls deposits and withdrawals of each account based on predetermined account management rules. , funds transfer according to purpose such as savings in each account (for example, refer to Patent Document 1 below).

Japanese Patent Application Laid-Open No. 2010-003111

However, in the prior art, there is a problem that when saving for a certain purpose is made using a plurality of accounts, it takes time and effort for the saver to grasp the total amount of savings for that purpose. For example, in the conventional technology, when a plurality of savers save for a certain purpose using their respective accounts, in order to grasp the total amount of savings for that purpose, it is necessary to I have to listen to each one, and it takes time. In addition, for example, in the conventional technology, even if there is only one saver, if the saver is saving for a certain saving purpose using multiple accounts, the total amount of savings for that saving purpose can be grasped. In order to do so, it is necessary to access each account and obtain the total savings amount for the purpose of saving from the obtained savings amount for each account, which is also time-consuming.

INDUSTRIAL APPLICABILITY The present invention provides a savings support device and a savings support method that enable a saver to easily grasp the total amount of savings for the purpose of saving when a plurality of accounts are used for saving for the purpose of saving. and to provide savings assistance programs.

In order to solve the above-described problems and achieve the object, the savings support device according to the present invention includes a storage unit that associates and stores the purpose of saving and the savings amount of each account used for the purpose of saving. a calculation unit for calculating the total amount of savings corresponding to the purpose; and an output unit for outputting to a terminal of a user who saves .

Further, the savings support device according to the present invention is characterized in that, in the above invention, each of the accounts is a virtual account corresponding to the purpose.

Further, in the savings support device according to the present invention, in the above invention, the storage unit further stores information specifying an account of the user, and includes information about the user and the purpose, When a purpose-specific savings creation request indicating that the user intends to save for a purpose is received, the storage unit is referred to, the user's account is specified, and the user's account is sent to the financial institution where the user's account is opened. and a virtual account creation unit that instructs to create a virtual account in the account of the user that corresponds to the purpose of It is characterized by storing in association with the amount of savings in the virtual account.

In the savings support device according to the present invention, in the above invention, the storage unit further stores a target savings amount in association with the purpose, and the output unit further includes information on the target savings amount. It is characterized by outputting purpose-based savings amount information.

In the above invention, the savings support device according to the present invention further includes a determination unit that determines whether or not the total amount of savings has reached the target savings amount. when it is determined that the total amount has reached the target savings amount, information is further output to the terminal of the user to guide that the total savings amount has reached the target savings amount. and

Further, in the savings support device according to the present invention, in the above invention, when the determination unit determines that the total amount of savings has reached the target amount of savings, the amount of money saved in each account used for the target savings is reduced. to a preset account.

Further, in the savings support device according to the present invention, in the above invention, the storage unit further stores an account-specific target savings amount for each account used for the target savings, Based on the savings amount of each account used and the target savings amount by account for each account used for the above-mentioned purpose of savings, for each account used for the above-mentioned purpose of savings, the savings amount of the account It further determines whether or not the target savings amount for each account has been reached, and the output unit determines whether the savings amount in any one of the accounts used for the target savings has reached the target savings amount for each account. When it is determined that the savings amount has reached the target savings amount for each account, information is further output to the terminal of the user to guide the account.

Further, in the savings support device according to the present invention, in the above invention, when receiving a change request to decrease the target savings amount for each account of the first account used for the purpose of saving by a predetermined amount, The change unit further comprises a change unit that decreases the target savings amount by the predetermined amount and increases the target savings amount for each account of a second account that is different from the first account and is used for the target savings by the predetermined amount. , characterized in that

Further, in the savings support method according to the present invention, the computer refers to the storage unit that stores the purpose of savings and the amount of savings in each account used for the purpose of savings in association with each other, and outputting purpose-specific savings amount information including information on the purpose and the calculated total savings amount to the terminal of the user who carries out savings for the purpose. characterized by executing

Further, the savings support program according to the present invention refers to a storage unit that stores, in a computer, a purpose of savings and a savings amount of each account used for savings for the purpose, in association with each other, so as to correspond to the purpose. and outputting purpose-specific savings amount information including information on the purpose and the calculated total savings amount to the terminal of the user who carries out savings for the purpose. It is characterized by executing

According to the present invention, when saving for a certain purpose is made using a plurality of accounts, it is possible for the saver to easily grasp the total amount of savings for the purpose of saving. play.

FIG. 1 is a diagram illustrating an example of a system configuration of a savings support system according to an embodiment; FIG. 2 is a block diagram of an example of a hardware configuration of a computer that implements the savings support server and the bank server according to the embodiment; FIG. 3 is a block diagram of an example of a hardware configuration of a computer that implements the user terminal according to the embodiment; FIG. 4 is a diagram illustrating an example of a savings support method by the savings support server according to the embodiment; 5 is a diagram depicting an example of contents stored in a user information DB according to the embodiment; FIG. FIG. 6 is a diagram depicting an example of contents stored in a purpose-specific savings information DB according to the embodiment; FIG. 7 is a diagram of an example of storage contents of a virtual account information DB according to the embodiment; FIG. 8 is a block diagram of an example of a functional configuration of a savings support server according to the embodiment; FIG. 9 is a sequence diagram (part 1) illustrating an example of processing performed by each device of the savings support system according to the embodiment; FIG. 10 is a diagram illustrating an example of a usage registration screen according to the embodiment; FIG. 11 is a diagram showing an example of a purpose-specific savings creation screen according to the embodiment. FIG. 12 is a diagram showing an example of a purpose-specific savings creation notification screen according to the embodiment. FIG. 13 is a diagram illustrating an example of a purpose-specific savings participation screen according to the embodiment; FIG. 14 is a diagram illustrating an example of a purpose-specific savings participation notification screen according to the embodiment. 15 is a sequence diagram (part 2) illustrating an example of processing performed by each device of the savings support system according to the embodiment; FIG. FIG. 16 is a diagram illustrating an example of a display screen at the time of payment according to the embodiment; 17 is a sequence diagram (part 3) illustrating an example of processing performed by each device of the savings support system according to the embodiment; FIG. 18 is a diagram illustrating an example of a display screen at the time of transfer according to the embodiment; FIG. 19 is a sequence diagram (part 4) illustrating an example of processing performed by each device of the savings support system according to the embodiment; FIG. 20 is a diagram illustrating an example of a reimbursement application screen according to the embodiment; FIG. FIG. 21 is a diagram illustrating an example of a payment permission/refusal screen according to the embodiment; FIG. 22 is a diagram showing an example of an account-by-account target savings screen according to the embodiment. 23 is a flowchart illustrating an example of savings support processing performed by the savings support server according to the embodiment; FIG. FIG. 24 is a flowchart illustrating an example of a target savings amount change process for each account performed by the savings support server according to the embodiment;

Exemplary embodiments of a savings support device, a savings support method, and a savings support program according to the present invention will be described below in detail with reference to the drawings.

(Example of system configuration of savings support system)
FIG. 1 is a diagram illustrating an example of a system configuration of a savings support system according to an embodiment; In FIG. 1 , the savings support system 100 includes a savings support server 110 , a user terminal 120 and a bank server 130 .

In savings support system 100 , savings support server 110 , user terminal 120 and bank server 130 are communicably connected via network 150 . Network 150 is, for example, the Internet. The network 150 is not limited to the Internet, but may be a WAN (Wide Area Network), a LAN (Local Area Network), Wi-Fi (registered trademark), a mobile communication network, or the like.

Savings support server 110 is an example of a savings support device according to the present invention, and is, for example, a server (computer) managed by an SNS operating company that provides SNS (Social Networking Service) to users. SNS operating companies, for example, distribute applications (hereinafter referred to as "SNS applications") that allow users to exchange messages, images, and the like.

For example, the user can communicate with the savings support server 110 using the SNS application by installing the SNS application on his or her own user terminal 120 and performing a predetermined SNS usage registration procedure. Specifically, for example, when the savings support server 110 receives a message using the SNS application from the user terminal 120 of a certain user, the message is transmitted to the user terminal 120 of another user to which the message is addressed. do. After receiving the message, the user terminal 120 displays the received message using the SNS application installed on the terminal. This allows the user to use the SNS application to send messages and the like to other users, receive messages and the like sent from other users, and use the SNS. A saver supported by the savings support server 110 is, for example, an SNS user.

Savings support server 110 also has storage unit 111, for example. The storage unit 111 stores, for example, user information of each user, information related to savings of users who receive savings support from the savings support server 110 and make savings, and the like. The user information is, for example, user identification information (eg, user ID), information specifying the user's account (eg, account number), and the like. The information about savings is information including a savings purpose, which is the purpose of savings, and the savings amount of each account used for saving for the savings purpose. Specifically, the storage unit 111 stores, for example, a user information DB 500, which will be described later with reference to FIG. 5, and a purpose-specific savings information DB 600, which will be described later with reference to FIG.

Savings support server 110 can be realized by, for example, a server computer, a workstation, a personal computer, or the like. Also, in this embodiment, an example in which storage unit 111 is provided in savings support server 110 will be described, but storage unit 111 may be provided outside of savings support server 110 . In this case, savings support server 110 may refer to storage unit 111 by accessing storage unit 111 provided outside of savings support server 110 via network 150, for example.

The user terminal 120 is a terminal (computer) used by a user. User terminal 120 includes an input device (for example, a touch panel) for accepting user operations, and an output device (for example, liquid crystal display) for displaying various information. User terminal 120 also includes a memory. For example, an SNS application is installed in the user terminal 120 as described above. User terminal 120 can be realized by, for example, a smart phone, a tablet terminal, a personal computer, or the like.

The bank server 130 is a server (computer) managed by a financial institution (for example, a bank) that manages accounts that allow transactions such as deposits and withdrawals, transfers, and transfers. The bank server 130 has an account information DB 131 that stores account information of each account opened in the financial institution that manages the bank server 130 . The account information is, for example, information indicating the name of the account holder, the account number of the account, the password used for authentication for using the account (account password), the amount of savings (balance) of the account, and the like.

In addition, the financial institution allows, for example, a user who is the holder of an account opened at the financial institution to use various services related to the account (for example, inquiry of savings amount, deposit and withdrawal) through the savings support server 110. API (Application Programming Interface) for The savings support server 110 communicates with the bank server 130 using this API, and for example, sends information to the bank server 130 for using a service according to the user's operation received via the SNS application. It receives it from the bank server 130 .

In addition, financial institutions can, for example, establish virtual accounts (hereinafter referred to as "virtual accounts") within each account (actual account) opened at the financial institution, and manage savings for each virtual account. It may offer virtual account services. Techniques for realizing such a virtual account are well known, and detailed description thereof will be omitted here. Bank server 130 may be implemented by a server computer, workstation, personal computer, or the like.

(Example of Hardware Configuration of Computer Realizing Savings Support Server 110 and Bank Server 130)
FIG. 2 is a block diagram of an example of a hardware configuration of a computer that implements the savings support server and the bank server according to the embodiment; In FIG. 2 , a computer that implements savings support server 110 and bank server 130 includes a CPU (Central Processing Unit) 201 , memory 202 , and communication IF (Interface) 203 . The CPU 201 , memory 202 and communication IF 203 are connected by a bus 210 .

The CPU 201 controls the entire computer that implements the savings support server 110 and the bank server 130 . A memory 202 is used as a work area for the CPU 201 . The memory 202 also stores various programs such as a boot program and various data used when these programs are executed. For example, the memory 202 of the computer that implements the savings support server 110 stores a user information DB 500 and purpose-specific savings information DB 600, which will be described later. Also, for example, the memory 202 of the computer that implements the bank server 130 stores an account information DB 131 including a virtual account information DB 700, which will be described later.

The memory 202 can be realized by various memory devices (circuits) such as ROM (Read-Only Memory), RAM (Random Access Memory), HDD (Hard Disc Drive) and HD (Hard Disc).

Communication IF 203 is connected to network 150 and controls the interface between the inside of the computer realizing savings support server 110 and bank server 130 and the outside of the computer. Specifically, communication IF 203 controls input/output of data between a computer that implements savings support server 110 and bank server 130 and other computers.

(Example of hardware configuration of computer realizing user terminal 120)
FIG. 3 is a block diagram of an example of a hardware configuration of a computer that implements the user terminal according to the embodiment; In FIG. 3, the computer that implements the user terminal 120 includes a CPU 301, a memory 302, an output device 303, an input device 304, and a communication IF305. CPU 301 , memory 302 , output device 303 , input device 304 and communication IF 305 are connected by bus 310 .

The CPU 301 controls the entire computer that implements the user terminal 120 . A memory 302 is used as a work area for the CPU 301 . The memory 302 also stores various programs such as the boot program and the above-described SNS application, and various data used when these programs are executed. The memory 302 can be realized by various memory devices (circuits) such as ROM, RAM, HDD and HD.

The output device 303 is, for example, a liquid crystal display or an organic EL (Electro-Luminescence) display that displays characters, images, and the like. The input device 304 also has keys for inputting characters, numerical values, various instructions, etc., and performs data input. Input device 304 is, for example, a touch panel. Also, if the computer that implements the user terminal 120 is implemented by a personal computer, the input device 304 may be a keyboard, mouse, or the like. An input device 304 realized by a touch panel or the like outputs a signal to the CPU 301 according to an input operation on the input device 304 .

The communication IF 305 is connected to the network 150 and controls the interface between the inside of the computer realizing the user terminal 120 and the outside of the computer. Specifically, the communication IF 305 controls input/output of data between the computer that implements the user terminal 120 and other computers. Communication IF 305 may also be connected to a telephone network and used for voice communication.

(Example of savings support method by savings support server 110)
Next, an example of a savings support method by the savings support server 110 will be described. FIG. 4 is a diagram illustrating an example of a savings support method by the savings support server according to the embodiment; FIG. 4 shows a savings support method by the savings support server 110 in the case of supporting savings for the savings purpose "mother's birthday" jointly performed by user U1 (for example, father) and user U2 (for example, user U1's child). An example is shown. User U1 and user U2 are, for example, SNS users.

In the example of FIG. 4, it is assumed that user U1 uses an account 410 opened at Bank A to save for the purpose of saving "mother's birthday". Here, the account 410 is, for example, an account whose name is user U1, and is an account for savings for user U1's savings purpose "mother's birthday". In addition, it is assumed that saving by user U1 using account 410 for the saving purpose of "mother's birthday" is registered in saving support server 110 prior to the saving.

In the example of FIG. 4, user U2 uses an account 420 opened at Bank B to save for the same saving purpose as user U1, ie, "mother's birthday". Here, the account 420 is, for example, an account whose name is user U2, and is an account for savings for user U2's savings purpose "mother's birthday". In addition, it is assumed that user U2 uses account 420 to save for the same saving purpose as user U1, "mother's birthday", in savings support server 110 prior to the saving.

In the example of FIG. 4, user U1 deposits only money intended for savings for "mother's birthday" into account 410 (see (1-1) in FIG. 4). Payment to account 410 can be made, for example, by transfer or transfer from an account other than account 410, or by depositing cash using an ATM (Automated Teller Machine). As a result, in account 410, only the money intended by user U1 for the saving purpose of "mother's birthday" is saved. In the example explained here, it is assumed that 10000 yen is saved in the account 410 .

The bank server 130 of Bank A transmits savings amount information indicating the savings amount of the account 410 (that is, the balance of the account 410) to the savings support server 110 (see (2-1) in FIG. 4). The bank server 130 of Bank A transmits savings amount information indicating the savings amount of the account 410 to the savings support server 110 when the savings amount of the account 410 changes due to, for example, a deposit to the account 410 . Further, the bank server 130 of Bank A may transmit savings amount information indicating the savings amount of the account 410 to the savings support server 110 when the savings support server 110 makes a request to inquire about the savings amount of the account 410. . In the example described here, since the savings amount in the account 410 is 10,000 yen, the bank server 130 of Bank A transmits savings amount information indicating that the savings amount in the account 410 is 10,000 yen to the savings support server 110. is doing.

The savings support server 110 associates the savings amount in the account 410 with the savings purpose "mother's birthday" based on the savings amount information indicating the savings amount in the account 410 received from the bank server 130 of Bank A, and stores it in the storage unit 111. (see (3-1) in FIG. 4). In the example described here, since the savings support server 110 has received the savings amount information indicating that the savings amount of the account 410 is 10,000 yen, the savings amount of the account 410 "10,000 yen" is changed to the savings purpose "mother's birth." day" is stored in the storage unit 111.

Similarly, in the example of FIG. 4, user U2 deposits only money intended for savings for "mother's birthday" into account 420 (see (1-2) in FIG. 4). Deposits into the account 420 can also be made, for example, by transfer or transfer from another account, or by depositing cash using an ATM. As a result, only the money intended by user U2 for the purpose of saving “mother's birthday” is saved in account 420 . In the example explained here, it is assumed that 5000 yen is saved in the account 420 .

In addition, the bank server 130 of Bank B saves savings amount information indicating the savings amount of the account 420 (that is, the balance of the account 420) when the savings amount of the account 420 fluctuates due to, for example, a deposit to the account 420. It is transmitted to the support server 110 (see (2-2) in FIG. 4). In the example described here, since the savings amount in the account 420 is 5,000 yen, the bank server 130 of Bank B transmits savings amount information indicating that the savings amount in the account 420 is 5,000 yen to the savings support server 110. is doing.

The savings support server 110 associates the savings amount of the account 420 with the savings purpose "mother's birthday" based on the savings amount information indicating the savings amount of the account 420 received from the bank server 130 of Bank B, and stores it in the storage unit 111. (see (3-2) in FIG. 4). In the example described here, since the savings support server 110 has received the savings amount information indicating that the savings amount of the account 420 is 5000 yen, the savings amount of the account 420 of "5000 yen" is changed to the savings purpose of "birth of mother". day" is stored in the storage unit 111.

According to the above (1-1) to (3-2), as shown in FIG. 4, the storage unit 111 associates the savings amount of the account 410 and the savings amount of the account 420 with the savings purpose "mother's birthday". stored.

The savings support server 110 refers to the storage unit 111 and sets the total savings amount of each account used for savings for a certain savings purpose as the total savings amount for that savings purpose (hereinafter referred to as "total savings amount"). calculate. In the example of FIG. 4, the savings amount of the account 410 is 10,000 yen and the savings amount of the account 420 is 5,000 yen. to calculate. In this case, savings support server 110 sends purpose-specific savings amount information including the savings purpose “mother’s birthday” and the total savings amount “15000 yen” for the savings purpose to the user terminals of user U1 and user U2. 120 (see (4) in FIG. 4).

When the user terminal 120 of the user U1 receives the above-mentioned savings amount information by purpose from the savings support server 110, the user terminal 120, for example, via the SNS application installed in the own terminal, the savings purpose indicated by the savings amount information by purpose is "mother". birthday” and the total amount of savings “15000 yen” to the user U1. Similarly, when the user terminal 120 of the user U2 receives the purpose-specific savings amount information from the savings support server 110, the user terminal 120, for example, via the SNS application installed in the user terminal 120, receives the savings indicated by the purpose-specific savings amount information. User U2 is informed of the purpose "mother's birthday" and the total savings amount "15000 yen".

As a result, the savings support server 110 can easily let the user U1 and the user U2 who save for the savings purpose "mother's birthday" save the total savings amount. Therefore, since users U1 and U2 can grasp the progress of the entire savings for the savings purpose "mother's birthday", for example, they can save the target amount by the scheduled date for completing the savings for the said savings purpose. It becomes possible to achieve the savings target for the savings purpose.

In the example of FIG. 4, for example, if user U1 wants to use account 410 for purposes other than saving for the purpose of saving "mother's birthday" or does not want user U2 to know the balance of account 410 itself, I have something to think about. For this reason, as shown in FIG. 4, for example, a virtual account 411 corresponding to the savings purpose “mother's birthday” may be provided within account 410 . In this case, bank server 130 of Bank A stores information on virtual account 411 in association with account 410, for example, as will be described later with reference to FIG. The bank server 130 of Bank A individually manages (stores) the balance of the account 410 and the amount of savings of the virtual account 411 .

In this case, it is registered in the savings support server 110 that the user U1 uses the virtual account 411 to save for the savings purpose “mother's birthday”. Then, user U1 deposits only the money intended for the savings purpose “mother's birthday” into virtual account 411 . Deposits into the virtual account 411 are performed, like the deposits into the account 410, for example, by transfer or transfer from an account other than the virtual account 411 (for example, transfer from the account 410), or by depositing cash using an ATM. be able to. As a result, in the virtual account 411, only the money intended by the user U1 for the saving purpose of "mother's birthday" is saved. Then, when the amount of savings in the virtual account 411 fluctuates due to, for example, a deposit in the virtual account 411, the bank server 130 of Bank A sends the savings amount information indicating the amount of savings in the virtual account 411 to the savings support server 110. Send.

Similarly, within the account 420, a virtual account 421 corresponding to the savings purpose "mother's birthday" may be provided. In this case, it is registered in the savings support server 110 that the user U2 uses the virtual account 421 to save for the savings purpose “mother's birthday”.

In this case, user U2 deposits into virtual account 421 only the money intended for the savings purpose “mother's birthday”. Deposits into the virtual account 421 are performed, like the deposits into the account 420, for example, by transfer or transfer from an account other than the virtual account 421 (for example, transfer from the account 420), or by depositing cash using an ATM. be able to. As a result, in the virtual account 421, only the money intended by the user U2 for the savings purpose of "mother's birthday" is saved. Then, when the amount of savings in the virtual account 421 fluctuates due to, for example, a deposit in the virtual account 421, the bank server 130 of Bank B sends savings amount information indicating the amount of savings in the virtual account 421 to the savings support server 110. Send. In this case, savings support server 110 associates the savings amount of virtual account 411 and virtual account 421 with the savings purpose “mother's birthday” and stores it in storage unit 111, for example. The total savings amount for the savings purpose "mother's birthday" is calculated from the savings amounts of the virtual accounts 411 and 421 stored in .

By providing the virtual account 411 and the virtual account 421 in this way, the user U1 and the user U2 can use the accounts 410 and 420 for purposes other than saving for the purpose of saving "mother's birthday", while also using the savings support server. It becomes possible to receive savings support by 110. In addition, by providing the virtual account 411 and the virtual account 421 in this way, the user U1 can receive savings support from the savings support server 110 without the personal information of the user U1, ie, the balance of the account 410 itself, being known to the user U2. possible to receive. Similarly, the user U2 can receive savings support from the savings support server 110 without the personal information of the user U2, ie, the balance of the account 420 itself, being known to the user U1.

In the example described above, the account 420 is the account of the user U2, and the user U1 and the user U2 jointly save for the purpose of saving "mother's birthday", but the present invention is not limited to this. For example, account 420 may also be user U1's account. In this case, for example, savings support server 110 registers that user U1 uses account 410 and account 420 to save for the savings purpose “mother's birthday”. Then, similarly to the example described above, savings support server 110 calculates the total savings amount for the savings purpose "mother's birthday" from the savings amounts of accounts 410 and 420, and the total savings amount information for each purpose is transmitted to the user terminal 120 of the user U1.

In this way, even when user U1 saves for the purpose of saving "mother's birthday" using a plurality of accounts 410 and 420, savings support server 110 can calculate the total amount of savings. can be easily grasped by the user U1. Also in this case, for example, the virtual account 411 is used instead of the account 410, and the virtual account 421 is used instead of the account 420, so that the saving for the saving purpose "mother's birthday" is performed. good.

In addition, from the viewpoint of facilitating understanding of the overall progress of savings for a certain savings purpose, as shown in FIG. Information may be transmitted to the user terminal 120 . In this case, the storage unit 111 stores in advance the target savings amount for the savings purpose, for example, in association with the savings purpose "mother's birthday". The target savings amount in this case can be arbitrarily determined by the user U1 or the user U2, for example, and is set to 50000 yen in the example of FIG. Then, when the savings support server 110 calculates the total savings amount for the savings purpose "mother's birthday", the purpose-specific savings amount information further includes information on the target savings amount corresponding to the savings purpose "mother's birthday". to the user terminals 120 of the users U1 and U2. As a result, savings support server 110 can make it easier for user U1 and user U2 to grasp the overall progress of savings for the savings purpose of "mother's birthday".

In addition, when the information of the target savings amount corresponding to the savings purpose is stored in the storage unit 111, the savings support server 110 stores the total savings amount for a certain savings purpose and the target savings amount corresponding to the savings purpose. Based on this, it may be determined whether or not the total amount of savings has reached the target amount of savings. Then, when it is determined by this determination that the total savings amount has reached the target savings amount, the savings support server 110 displays target achievement information that guides that the total savings amount has reached the target savings amount. You may make it transmit to the user terminal 120 of the user who makes savings for the purpose of savings who reached the savings amount.

For example, when the savings support server 110 calculates the total savings amount for the savings purpose "mother's birthday", it determines whether the total savings amount has reached the target savings amount "50000 yen" for the savings purpose "mother's birthday". determine whether Then, when the savings support server 110 determines that the total savings amount for the savings purpose "mother's birthday" has reached the target savings amount "50000 yen", the total savings amount for the savings purpose "mother's birthday" reaches the target savings amount. Goal achievement information that guides that the savings amount has been reached is transmitted to the user terminals 120 of the users U1 and U2. Thus, savings support server 110 can inform user U1 and user U2 that the savings goal of the savings purpose "mother's birthday" has been achieved.

In addition, when the savings support server 110 determines that the total savings amount for a certain savings purpose has reached the target savings amount for that savings purpose, the money saved by the savings for that savings purpose is transferred to a preset account. You may perform the process to move. For example, when determining that the total savings amount for the savings purpose "mother's birthday" has reached the target savings amount "50000 yen", the savings support server 110 removes the money saved in the account 410 (or the virtual account 411). The bank server 130 of Bank A is instructed to transfer to a preset account. Similarly, in this case, savings support server 110 instructs bank server 130 of Bank B to transfer money saved in account 420 (or virtual account 421) to a preset account.

The destination account in this case is, for example, an account determined by the user U1 or the user U2, which is agreed upon by both the user U1 and the user U2 as the destination account. Then, if the transfer destination account is an account of someone other than the users U1 and U2, the money saved by the users U1 and U2 through the savings for the savings purpose is transferred to You can prevent it from being used for other purposes. Further, if the transfer destination account is, for example, the account of user U1 (for example, account 410), at least user U2 will receive the money saved by user U2 through the savings for the purpose of saving after achieving the savings for the purpose of saving. It is possible to prevent the money from being used for purposes other than the saving purpose.

Also, if the savings support server 110 does not perform the process of transferring the saved money to a preset account as described above, for example, when the total savings amount for a certain savings purpose reaches the target savings amount In this case, each user who has made savings for the purpose of saving may withdraw the money saved from each account, and deliver the money to the user who is the organizer of the savings for the purpose of saving.

In addition, in order to promote saving for a certain saving purpose more efficiently, a certain limit may be placed on withdrawals from each account used for saving for that saving purpose. For example, in the example of FIG. 4, when the user U1 withdraws money from the virtual account 411 used for the savings purpose "mother's birthday", the consent of the user U2 is required, and the user U2 does not have the savings purpose "mother's birthday". Consent of the user U1 may be required when withdrawing money from the virtual account 421 used for .

In this case, for example, when there is a withdrawal request from the virtual account 411 by the user U1, the bank server 130 of Bank A reserves the withdrawal, and the user U1 attempts to withdraw from the virtual account 411. notifies the savings support server 110 that the Upon receiving this notification, savings support server 110 notifies user U2 that user U1 is about to withdraw money from virtual account 411, and receives from user U2 whether or not to permit the withdrawal. Then, when the withdrawal is permitted by the user U2, the savings support server 110 notifies the bank server 130 of Bank A that the withdrawal from the virtual account 411 is permitted. The bank server 130 of Bank A makes a withdrawal from the virtual account 411 based on the withdrawal request on the condition that the notice of permission to withdraw from the virtual account 411 is received from the savings support server 110. You should do it like this.

(Specific example of contents stored in storage unit 111)
Next, a specific example of the contents stored in the storage unit 111 will be described. 5 is a diagram depicting an example of contents stored in a user information DB according to the embodiment; FIG. Storage unit 111 stores, for example, user information DB 500 shown in FIG.

In FIG. 5, the user information DB 500 stores user information (for example, user information 501) in which user ID, user password, bank name, branch name, account number, and account password are associated with each other. Remember.

The user ID is user identification information. The user ID can be arbitrarily designated by the user who registers for use of the SNS, for example. However, if the user can specify the user ID in this way, for example, the savings support server 110 checks whether the user ID specified by the user has already been registered in the user information DB 500, and confirms that the user ID has been registered. The user ID is registered in the user information DB 500 only when it has not been completed.

Thereby, even if the user can specify the user ID, the savings support server 110 can prevent duplication of user IDs in the user information DB 500 . Also, the user ID may be the telephone number or email address of the user terminal 120 of the user who has registered for use of the SNS. In this way, duplication of user IDs in the user information DB 500 can be prevented, and the user terminal 120 can be identified by the user ID.

A user password is a password used for authentication for using SNS (for example, logging in to an SNS application). The user password can be arbitrarily determined by the user who registers for use of the SNS, for example. The bank name is the name of the financial institution where the user's account is opened. The bank name is, for example, the name of the financial institution declared by the user who performs the usage registration at the time of usage registration of the SNS. The branch name is the name of the branch where the user's account is opened. The branch name is, for example, the name of the branch declared by the user who performs the usage registration at the time of usage registration of the SNS.

The account number is the account number of the user's account. The account number is, for example, the account number declared by the user who registers for use of the SNS. The combination of bank name, branch name and account number uniquely identifies each user's account. The account password is a password used for authentication (personal identification) for using the user's account. The account password is, for example, a password declared as an account password by a user who registers for use of the SNS.

The savings support server 110 can identify and access each user's account by using the bank name, branch name, account number, and account password of each user information stored in the user information DB 500. . Also, instead of the bank name described above, a financial institution code that identifies the financial institution may be used. Similarly, instead of the branch name described above, a branch number that identifies the branch may be used.

FIG. 6 is a diagram depicting an example of contents stored in a purpose-specific savings information DB according to the embodiment; Storage unit 111 further stores purpose-specific savings information DB 600 shown in FIG. 6, for example. 6, the purpose-specific savings information DB 600 includes, for example, purpose-specific IDs, purpose-specific passwords, purpose names, user IDs, virtual account IDs, account-specific savings amounts, total savings amounts, and account-specific targets. It stores purpose-specific savings information (for example, purpose-specific savings information 601) in which information on a savings amount, a target savings amount, a savings period, and a transfer destination account are associated with each other.

The purpose-specific ID is identification information that identifies the purpose of saving. For example, when saving for a certain saving purpose is started, the savings support server 110 designates the purpose-specific ID for the saving for the saving purpose. Specifically, for example, when the savings support server 110 receives from the user terminal 120 a savings-by-purpose creation request to start savings for a certain savings purpose, the savings-by-purpose ID registered in the savings-by-purpose information DB 600 and the An arbitrary character string that is not duplicated is designated as the savings-purpose ID of the savings-purpose of the savings-purpose creation request (see step S906 in FIG. 9).

Also, the purpose-specific ID may be, for example, a character string specified by the user who makes the savings. However, if the purpose-specific ID can be specified by the user, for example, savings support server 110 checks whether the purpose-specific ID specified by the user has already been registered in purpose-specific savings information DB 600, and determines if the purpose-specific ID is registered. is not already registered, the purpose-specific ID is registered in the purpose-specific savings information DB 600 . As a result, even if the purpose-specific ID can be specified by the user, the savings support server 110 can prevent duplication of purpose-specific IDs in the purpose-specific savings information DB 600 .

The purpose-specific password is a password used for authentication for participating in saving for each saving purpose. The purpose-specific password is, for example, a character string specified by savings support server 110 . For example, when the savings support server 110 receives the above-mentioned savings creation request, the savings support server 110 designates an arbitrary character string as the purpose-specific password for participating in the savings for the purpose of the savings creation request ( See step S906 in FIG. 9).

The purpose name is a name (title) attached to the savings for each savings purpose. The purpose name is specified, for example, by the user who registered savings for a certain savings purpose in the savings support server 110 (for example, the user of the user terminal 120 who sent the above purpose-specific savings creation request). The user ID is, for example, information similar to the user ID of the user information in the user information DB 500, and is information that identifies the user who makes savings for each savings purpose.

The virtual account ID is identification information that identifies the virtual account used for saving for each saving purpose. The virtual account ID is set, for example, when bank server 130 creates a virtual account corresponding to savings for each savings purpose, and is notified to savings support server 110 . The savings amount by account is the savings amount for each virtual account used for savings for each savings purpose. The total savings amount is the total savings amount for each savings objective, eg, the sum of the savings amounts for each of the virtual accounts used for saving for each savings objective. The target savings amount by account is the target savings amount for each virtual account used for savings for each savings purpose.

The savings period indicates the period during which savings for each purpose of savings is made, for example, the period from the start date of savings for each purpose to the date (scheduled end date) for completing the savings for that purpose. The payee account indicates the account to which the money saved by the savings for the savings purpose is transferred when the savings for each savings purpose is completed. The target savings amount for each account, the target savings amount, the savings period, and the payee account can be arbitrarily set by, for example, the user who makes savings for the corresponding savings purpose.

In addition, if an API key is required for use of the above-described API published by a financial institution, the savings support server 110 registers purpose-specific savings information including API key information in the purpose-specific savings information DB 600, for example. may Specifically, for example, in this case, when saving-by-purpose savings information is registered in savings-by-purpose information DB 600, savings support server 110 registers a user (for example, a savings creation request by purpose described later) corresponding to the savings-by-purpose information. An API key is issued from the bank server 130 of the financial institution where the account of the original user terminal 120 (user of the user terminal 120) was opened, and the purpose-specific savings information including the API key information is registered in the purpose-specific savings information DB 600. When the purpose-specific savings information including the API key information is registered in this way, the savings support server 110 subsequently sends the information to the bank server 130 of the financial institution where the user's account corresponding to the purpose-specific savings information is opened. When accessing, the API key information of the purpose-specific savings information is also transmitted to the bank server 130 .

(Example of storage contents of account information DB 131)
Next, an example of the contents stored in the account information DB 131 will be described. FIG. 7 is a diagram of an example of storage contents of a virtual account information DB according to the embodiment; The account information DB 131 includes, for example, a virtual account information DB 700 shown in FIG. In FIG. 7, the virtual account information DB 700 stores virtual account information in which information such as an account number, an account password, a virtual account ID, a purpose-specific ID, a savings amount, and a savings achievement flag are associated with each other. do.

Here, the account number is the account number of each account opened in (a branch of) the financial institution that manages the bank server 130, and is the same information as the account number in the user information DB 500, for example. The account password is a password used for authentication for using each account opened in the financial institution that manages the bank server 130, and is information similar to the account password in the user information DB 500, for example.

A virtual account ID is identification information of a virtual account provided for each account opened in a financial institution that manages bank server 130, and is, for example, information similar to the virtual account ID in purpose-specific savings information DB 600. The purpose-specific ID indicates the purpose of saving for which each virtual account opened in the financial institution managing the bank server 130 is used, and is, for example, the same information as the purpose-specific savings information DB 600 . The savings amount is the current savings amount of each virtual account opened in the financial institution that manages the bank server 130, and is, for example, the same information as the savings amount by account in the savings information DB 600 by purpose. The savings achievement flag is a flag that indicates whether or not the savings amount of each virtual account opened in the bank that manages bank server 130 has reached the target savings amount for each account of the virtual account. , indicates that the target savings amount for each account has not been reached, and "1" indicates that the target savings amount for each account has been reached.

(Functional configuration of savings support server 110)
Next, an example of the functional configuration of the savings support server 110 will be described. FIG. 8 is a block diagram of an example of a functional configuration of a savings support server according to the embodiment; In FIG. 8 , savings support server 110 has, for example, storage unit 111 , calculation unit 801 , and output unit 802 .

The storage unit 111 associates and stores a savings purpose and a savings amount of each account used for savings for the savings purpose. Storage unit 111 stores purpose-specific savings information DB 600 shown in FIG. 6, for example. In the case of the purpose-specific savings information DB 600 shown in FIG. and the savings amount "5000 yen" of the virtual account identified by the virtual account ID "□□" are stored in association with each other.

In this way, the storage unit 111 stores the savings amount of the virtual account corresponding to the savings purpose in association with the savings purpose, so that the savings support server 110 can store the balance of the user's account (real account) itself. It is possible to support the saving of the user without leaking the personal information of the user to other users. In addition, since the user can use the account for purposes other than saving, the user's convenience can be enhanced.

In addition, the storage unit 111 further stores user information of each user. The storage unit 111 stores, for example, the user information DB 500 shown in FIG. Further, the storage unit 111 is provided so that each functional unit of the savings support server 110 can refer to it, and is appropriately referred to during the processing of each functional unit of the savings support server 110 . Further, the storage unit 111 may store the processing results of each functional unit of the savings support server 110 . The storage unit 111 can realize its function by the memory 202 shown in FIG. 2, for example.

The calculation unit 801 refers to the storage unit 111 and calculates the total savings amount for each savings purpose. The calculation unit 801 calculates the total savings amount of each account used for saving for a certain savings purpose as the total savings amount for that savings purpose.

Specifically, for example, when storage unit 111 stores purpose-specific savings information DB 600 shown in FIG. The savings amount is calculated as follows: the savings amount of the virtual account identified by the virtual account ID "○○" is "10000 yen" + the savings amount of the virtual account identified by the virtual account ID "□□" is "5000 yen" = "15000 yen" to calculate. Calculation unit 801 can realize its function, for example, when CPU 201 executes a program stored in memory 202 shown in FIG.

The output unit 802 outputs information based on the processing result of the savings support server 110 to the user terminal 120 and bank server 130 . For example, the output unit 802 outputs the savings amount information by purpose including the information of the total savings amount calculated by the calculation unit 801 and the savings purpose for which the total savings amount is calculated, to the user who saves for the savings purpose. Output to the user terminal 120 .

Specifically, for example, as described above, when the calculation unit 801 calculates the total savings amount for the savings purpose “mother’s birthday” identified by the purpose-specific ID “ID01”, the output unit 802 111, the users with the user IDs "U1" and "U2" who are saving for the savings purpose are specified, and the savings amounts by purpose are sent to the user terminals 120 of the users with the user IDs "U1" and "U2". Output information. Output unit 802 can realize its function by CPU 201 executing a program stored in memory 202 shown in FIG. 2 or by communication IF 203, for example.

As a result, the savings support server 110 can allow the user who makes savings for each savings purpose to easily grasp the total savings amount for each savings purpose. Therefore, the savings support server 110 can allow the user to efficiently grasp the progress of the savings for the savings purpose, and can, for example, assist the user in achieving the savings target for the savings purpose.

Savings support server 110 further has, for example, reception unit 803 and update unit 804 . The receiving unit 803 receives various information necessary for the processing of the savings support server 110 from the user terminal 120, the bank server 130, and the like. The reception unit 803 receives, for example, user information of a user who registers for use of the SNS from the user terminal 120 of the user. Upon receiving user information, the receiving unit 803 passes the received user information to the updating unit 804 . Receiving unit 803 can realize its function by CPU 201 executing a program stored in memory 202 shown in FIG. 2 or by communication IF 203, for example.

The updating unit 804 updates the contents stored in the storage unit 111 . For example, when receiving user information from the receiving unit 803 , the updating unit 804 registers the received user information in the user information DB 500 of the storage unit 111 . As a result, the user information DB 500 stores the user information of the user who has registered for use of the SNS. Updating unit 804 can realize its function when CPU 201 executes a program stored in memory 202 shown in FIG. 2, for example.

The receiving unit 803 also receives, for example, savings amount information indicating the savings amount of the account from the bank server 130 of the financial institution where the account used for saving for each savings purpose is opened. For example, as described above, bank server 130 transmits savings amount information indicating the savings amount of each account to savings support server 110 each time the savings amount of each account used for savings for each savings purpose changes. The receiving unit 803 receives the savings amount information transmitted from the bank server 130 in this way.

When receiving the savings amount information from the bank server 130 , the receiving unit 803 passes the received savings amount information to the updating unit 804 . In this case, the update unit 804 updates the purpose-specific savings information DB 600 of the storage unit 111 based on the savings amount information received from the reception unit 803 . For example, suppose that the savings amount information accepted by the accepting unit 803 is information indicating that the savings amount of the virtual account identified by the virtual account ID "○○" is "10000 yen". In this case, the updating unit 804 updates the purpose-specific savings information DB 600 so that the savings amount of the virtual account identified by the virtual account ID "○○" is "10000 yen". As a result, the purpose-specific savings information DB 600 stores the most recent savings amount of each account used for savings for each savings purpose, and the total savings amount calculated by the savings support server 110 is the actual total savings amount at that time. It is possible to increase the accuracy of matching.

Savings support server 110 may further include a virtual account creation unit 805a and a virtual account information acquisition unit 805b. In this case, the receiving unit 803 receives, from the user terminal 120 of the user, a purpose-specific savings creation request indicating that a certain user will start saving for a certain saving purpose, for example. That is, the purpose-specific savings creation request includes, for example, information about the user who starts saving for a certain savings purpose and the savings purpose.

Specifically, it is assumed that the user with the user ID "U1" starts saving for the saving purpose "mother's birthday". In this case, a purpose-specific savings creation request containing information on the user ID “U1” and the purpose name “mother’s birthday” is transmitted from the user terminal 120 of the user with the user ID “U1” to the savings support server 110. be. In this case, the receiving unit 803 receives a purpose-specific savings creation request including information on the user ID "U1" and the purpose name "mother's birthday".

When the reception unit 803 receives a savings creation request for each purpose, the virtual account creation unit 805a refers to the storage unit 111 and, based on the received savings creation request for each purpose, creates the account of the user indicated by the savings creation request for each purpose. and instruct the financial institution where the user's account was opened to create a virtual account in the user's account corresponding to the purpose of savings indicated by the user's purpose-specific savings creation request process. The virtual account creating unit 805a, for example, creates a virtual account corresponding to the savings purpose indicated by the purpose-based savings creation request of the user indicated by the purpose-based savings creation request. generates a virtual account creation instruction to instruct the bank server 130 of The function of the virtual account creating unit 805a can be realized by, for example, the CPU 201 executing a program stored in the memory 202 shown in FIG.

The virtual account creation instruction generated by the virtual account creation unit 805a is output, for example, by the output unit 802 to the bank server 130 that is the target of the instruction. When bank server 130 receives a virtual account creation instruction, bank server 130 creates a virtual account in accordance with the virtual account creation instruction. , to the savings support server 110 . Information indicating a virtual account is, for example, information indicating a virtual account ID. The information indicating the saving purpose is, for example, information indicating the purpose name and purpose-specific ID.

The information indicating the virtual account and the purpose of savings transmitted from bank server 130 is input to virtual account information acquisition section 805b via reception section 803, for example. Then, the virtual account information acquisition unit 805b acquires information indicating the virtual account created by the bank server 130 and the savings purpose corresponding to the virtual account. Then, the virtual account information acquiring unit 805b passes the virtual account created by the bank server 130 and the information indicating the savings purpose corresponding to the virtual account to the updating unit 804 . The function of the virtual account information acquisition unit 805b can be realized, for example, by the CPU 201 executing a program stored in the memory 202 shown in FIG. In this case, the update unit 804 associates the virtual account created by the bank server 130 with the savings purpose corresponding to the virtual account, and registers them in the purpose-specific savings information DB 600 of the storage unit 111 . For example, when a virtual account with a virtual account ID of “○○” is created by a purpose-specific savings creation request containing a purpose name “mother’s birthday”, the update unit 804 receives the purpose-specific savings creation request. The issued purpose-specific ID “ID01”, purpose name “mother’s birthday”, and virtual account ID “○○” are associated with each other and registered in the purpose-specific savings information DB 600 .

As a result, when the user starts saving for a certain savings purpose, the user does not need to individually create a virtual account for use in saving for that savings purpose. It is possible to reduce the user's effort for performing

In addition, the storage unit 111 may further store a target savings amount for savings for the savings purpose in association with the savings purpose. In this case, the storage unit 111 stores, for example, an amount specified by the user who saves for a certain saving purpose as the target savings amount corresponding to the saving purpose. In the case of the purpose-specific savings information DB 600 shown in FIG. I remember.

When the storage unit 111 stores the target savings amount in association with the savings purpose, the output unit 802 stores, for example, a purpose-specific savings amount further including information on the target savings amount corresponding to the savings purpose used to calculate the savings amount. Output information. Specifically, for example, when the calculation unit 801 calculates the total savings amount for the savings purpose “mother’s birthday” identified by the purpose-specific ID “ID01” as described above, the output unit 802 Purpose-specific savings amount information that further includes information on the target savings amount "50,000 yen" corresponding to the purpose is output. As a result, the savings support server 110 can combine the total savings amount for a certain savings purpose with the target savings amount, and guide the user who is saving for that savings purpose. It is possible to make it easier for the user to grasp the progress of saving for the saving purpose.

Similarly, from the viewpoint of making it easier for the user to grasp the progress of savings for each savings purpose, the storage unit 111 stores a savings account including a due date for completing the savings for the savings purpose in association with the savings purpose. A time period may also be stored. In this case, the storage unit 111 stores, for example, a period designated by the user for saving for a certain saving purpose as a saving period corresponding to the saving purpose. In the case of the purpose-specific savings information DB 600 shown in FIG. "February 1, 2012" is associated and stored. In this case, the due date for completing the savings for the savings purpose is "February 1, 2018".

When the storage unit 111 stores the savings period in association with the savings purpose, the output unit 802 outputs, for example, purpose-specific savings amount information further including information on the savings period corresponding to the savings purpose for which the total savings amount is calculated. You may Specifically, for example, when the calculation unit 801 calculates the total savings amount for the savings purpose “mother’s birthday” identified by the purpose-specific ID “ID01” as described above, the output unit 802 Purpose-specific savings that further includes information on the savings period corresponding to the purpose "December 1, 2017 to February 1, 2018 (or only February 1, 2018, which is the scheduled completion date of the savings)" Output amount information. As a result, the savings support server 110 can match the total savings amount for a certain savings purpose with the savings period, and guide the user who is saving for that savings purpose. It can make it easier for people to grasp the progress of their savings.

Moreover, when the storage unit 111 stores the target savings amount in association with the savings purpose, the savings support server 110 may further include a determination unit 806 . The determination unit 806 determines whether the total savings amount calculated by the calculation unit 801 has reached the target savings amount corresponding to the savings purpose for which the total savings amount was calculated. Specifically, for example, when the calculation unit 801 calculates the total savings amount for the savings purpose “mother's birthday” identified by the purpose-specific ID “ID01” as described above, the determination unit 806 It is determined whether or not the savings amount has reached the target savings amount "50000 yen" corresponding to the savings purpose.

In this case, for example, determination unit 806 determines that the total savings amount for the savings purpose “mother's birthday” identified by purpose-specific ID “ID01” is calculated as “15,000 yen” by calculation unit 801, as described above. If so, it is determined that the target savings amount "50000 yen" corresponding to the savings purpose has not been reached. On the other hand, for example, if the calculation unit 801 calculates that the total savings amount for the savings purpose “mother's birthday” identified by the purpose-specific ID “ID01” is “55000 yen”, the determination unit 806 determines that the savings purpose It is determined that the target savings amount "50000 yen" corresponding to is reached. Determining unit 806 can realize its function, for example, when CPU 201 executes a program stored in memory 202 shown in FIG.

If the determination unit 806 is included, for example, when the determination unit 806 determines that the total savings amount has reached the target savings amount, the output unit 802 outputs information ( goal achievement information) is further output to the user terminal 120 of the user who makes savings for the savings purpose. As a result, the savings support server 110 can guide the user who is saving for the purpose of saving that the saving for the purpose of saving has been completed, that is, the goal of the saving for the purpose of saving has been achieved.

Furthermore, the storage unit 111 may store a target savings amount for each account (for example, a virtual account) used for savings for a certain savings purpose. In this case, for example, the sum of the target savings amount for each account used for savings for a certain savings purpose is set to be the target savings amount for the savings for that savings purpose. In the case of the purpose-specific savings information DB 600 shown in FIG. stores the target savings amount "35,000 yen" for each account in association with it. Similarly, the storage unit 111 associates and stores the target savings amount for each account of “15000 yen” with the virtual account with the virtual account ID “□□”.

When the storage unit 111 stores the target savings amount for each account, the determination unit 806 refers to the storage unit 111 to determine the savings amount of each account used for saving for a certain saving purpose and the target savings amount for each account of the account. and , it may be determined whether or not the savings amount of each account used for savings for a certain savings purpose has reached the target savings amount for each account of the account.

The determination unit 806 determines, for example, the target savings amount for each account of the virtual account with the virtual account ID of "○○" used for the savings purpose of "mother's birthday" identified by the purpose-specific ID of "ID01", which is "35000 yen". Then, it is determined whether or not the amount of savings in the virtual account with the virtual account ID "○○" has reached "35000 yen". Similarly, the determination unit 806 determines, for example, the target savings amount for each account of the virtual account with the virtual account ID “□□” used for the savings purpose “mother's birthday” identified by the purpose-specific ID “ID01”. , it is determined whether or not the savings amount of the virtual account with the virtual account ID "□□" has reached "15000 yen".

In this case, for example, when the determination unit 806 determines that the savings amount of an account has reached the target savings amount for each account, the output unit 802 determines that the savings amount for the account has reached the target savings amount for each account. Information (account-specific goal achievement information) that guides the achievement of the goal may be further output to the user terminal 120 of the user who makes savings for the purpose of saving using the account. As a result, the savings support server 110 guides the account used for savings for a certain savings purpose to the account whose savings amount has reached the target savings amount for each account to the user who uses the account for savings for the purpose of savings. becomes possible.

Further, when the savings support server 110 has the determination unit 806 , the savings support server 110 may further have a transfer instruction unit 807 . When the determination unit 806 determines that the total amount of savings has reached the target savings amount, the transfer instruction unit 807 transfers the money saved in each account used for savings for the purpose of saving to a preset account. Execute the process to move. For example, if the determination unit 806 determines that the total savings amount for the purpose-specific ID “ID01” has reached the target savings amount “50000 yen”, the transfer instruction unit 807 , the money saved in the virtual account with the virtual account ID "○○" and the virtual account with the virtual account ID "□□" is transferred to the transfer destination account "●●".

Specifically, the transfer instruction unit 807, for example, through the output unit 802, sends the bank server 130 of the financial institution in which the virtual accounts with the virtual account IDs “○○” and “□□” are provided. , to transfer the money saved in the virtual account to the transfer destination account "●●" for the target savings amount for each account corresponding to the virtual account. As a result, the savings support server 110 can prevent the money from the savings from being used for other purposes after the savings for the savings purpose is achieved.

In addition, as described above, when the storage unit 111 stores the target savings amount for each account, the reception unit 803, for example, changes the target savings amount for each account of the first account used for saving for a certain savings purpose by a predetermined amount. May accept requests. In this case, upon receiving a change request, the receiving unit 803 passes the received change request to the updating unit 804 . Upon receiving the change request from the receiving unit 803, the updating unit 804 reduces the target savings amount for each account of the first account stored in the storage unit 111 by a predetermined amount in accordance with the request for change, The target savings amount for each account of the above-mentioned second account will be increased by the amount reduced.

In the case of the purpose-specific savings information DB 600 shown in FIG. Assume that a change request to reduce the amount from "35,000 yen" to "30,000 yen" is accepted. In this case, the updating unit 804 changes the target savings amount for each account of the virtual account with the virtual account ID “○○” to “30000 yen”, and also changes the target savings amount for each account to “30000 yen”, The target savings amount for each account of the virtual account with the ID "□□" is changed from "15000 yen" to "20000 yen". Thus, the savings support server 110 can maintain the target savings amount of savings for a certain savings purpose even if the target savings amount for each account used for savings for a certain savings purpose is changed. The update section 804 is an example of a change section according to the present invention.

Also, in this case, the updating unit 804 may perform the above change on the condition that the user of the account for which the target savings amount for each account is to be increased has been approved. For example, when receiving a change request from the receiving unit 803, the updating unit 804 sends, via the output unit 802, the user terminal 120 of the user whose target savings amount for each account is to be increased if the change is made in accordance with the change request. information for accepting whether or not to permit the change according to the change request. Then, when the update unit 804 receives, via the reception unit 803, information to the effect that the change is permitted from the user terminal 120 of the user of the account whose target savings amount for each account is to be increased, according to the information. , making the above changes. In this way, it is possible to prevent the target savings amount for each account corresponding to the user's account from being changed against the will of the user who saves for a certain savings purpose.

For example, when the target savings amount for each account of a certain account is reduced by “5000 yen”, if there are two other accounts used for savings for the same savings purpose as the account, the update unit 804 , the target savings amount for each account may be increased by "2500 yen". Further, for example, when the target savings amount for each account of a certain account is reduced by “5000 yen”, if there are two other accounts used for savings for the same savings purpose as the account, the update unit 804 The target savings amount by account of one account may be increased by "3000 yen", and the target savings amount by account of the other account may be increased by "2000 yen". How the update unit 804 changes the savings amount for each account to maintain the target savings amount depends, for example, on the user of the user terminal 120 who transmits the change request, the manufacturer of the savings support server 110, or the like. It may be set arbitrarily.

(Example of processing performed by each device of savings support system 100 - part 1)
Next, an example of processing performed by each device of the savings support system 100 will be described. FIG. 9 is a sequence diagram (part 1) illustrating an example of processing performed by each device of the savings support system according to the embodiment; FIG. 9 shows that the user U1 shown in FIG. 4 has registered in the savings support server 110 that the user U1 shown in FIG. has shown an example of the processing performed by each device of the savings support system 100 when participates in the savings for the savings purpose.

Also, in the description of FIG. 9, the user terminal 120 used by user U1 is referred to as "user terminal 120-1", and the user terminal 120 used by user U2 is referred to as "user terminal 120-2". 9, the bank server 130 of Bank A in which the account 410 (that is, the account of user U1) shown in FIG. Namely, the bank server 130 of Bank B where user U2's account) is opened is referred to as "bank server 130-2".

In FIG. 9, user terminal 120-1 transmits a registration request requesting registration of user information of user U1 to savings support server 110 (step S901). User terminal 120-1 displays a usage registration screen (see FIG. 10) for performing SNS usage registration, for example, when the SNS application installed in the user terminal 120-1 is activated for the first time. Then, user terminal 120-1 receives input of user information of user U1 from user U1 on the use registration screen. In step S901, the user terminal 120-1 transmits a registration request requesting registration of the user information including the user information of the user U1 accepted on the use registration screen, for example. Upon receiving the registration request from user terminal 120-1, savings support server 110 registers the user information of user U1 in user information DB 500 in accordance with the registration request (step S902).

Similarly, the user terminal 120-2 transmits a registration request requesting registration of the user information of the user U2 to the savings support server 110 (step S903). Upon receiving the registration request from user terminal 120-2, savings support server 110 registers the user information of user U2 in user information DB 500 in accordance with the registration request (step S904). Through the processing of steps S901 to S904, user U1 and user U2 are registered for use of the SNS.

After that, when user terminal 120-1 receives an operation from user U1 to start saving for a certain saving purpose (for example, saving for the saving purpose "mother's birthday"), user U1 starts saving for that saving purpose. A purpose-specific savings creation request indicating that the savings is to be made is transmitted to the savings support server 110 (step S905). User terminal 120-1 can, for example, display a purpose-specific savings creation screen (see FIG. 11) for accepting inputs such as a user ID and a purpose name when there is a predetermined operation from user U1. Then, user terminal 120-1 accepts input such as the user ID of user U1 and the name of the purpose of savings to be started by user U1 from user U1 on the purpose-based savings creation screen.

In step S905, the user terminal 120-1, for example, stores information such as the user ID and the purpose name accepted on the savings-by-purpose creation screen, and displays the savings by purpose indicating that the user U1 will start saving for that purpose name. Submit a create request. User terminal 120-1 also accepts inputs such as the target savings amount, savings period, payee account, etc. of savings to be started by user U1 on the purpose-specific savings creation screen. may be sent.

Savings support server 110, upon receiving the purpose-based savings creation request from user terminal 120-1, assigns a purpose-based ID (for example, purpose-based ID “ID01” shown in FIG. 6) that identifies the above-described savings initiated by user U1. ) and a purpose-specific password (for example, the purpose-specific password “pass5” shown in FIG. 6) used for authentication for participating in the saving are issued (step S906).

Then, savings support server 110 transmits to bank server 130-1 a virtual account creation instruction to create a virtual account corresponding to the purpose-specific ID issued in step S906 in user U1's account 410 ( step S907). In step S907, savings support server 110 transmits a virtual account creation instruction including, for example, the account number and account password of account 410 (that is, corresponding to user U1) and the purpose-specific ID issued in step S906. do.

When the bank server 130-1 receives the virtual account creation instruction from the savings support server 110, the virtual account corresponding to the purpose-specific ID indicated by the virtual account creation instruction is created in the account 410 in accordance with the virtual account creation instruction. The virtual account information of the created virtual account is registered in the virtual account information DB 700 (step S908). In step S908, bank server 130-1, for example, stores the account number, account password, and purpose-specific ID of the virtual account creation instruction received from savings support server 110, and the virtual account created according to the virtual account creation instruction. Register the virtual account information in which the virtual account ID and the information are associated with each other.

By the processing of step S908, for example, the virtual account 411 shown in FIG. 4 is created, and the virtual account information of the virtual account ID "○○" shown in FIG. 7 is registered in the virtual account information DB700. Here, the virtual account ID “○○” is the virtual account ID of the virtual account 411 . Bank server 130-1 initially sets the savings achievement flag in the virtual account information to "0". The bank server 130-1 then transmits a virtual account notification that notifies the virtual account ID of the virtual account created in step S908 to the savings support server 110 (step S909).

Upon receiving the virtual account notification from bank server 130-1, savings support server 110 registers the purpose-specific savings information related to the above-described savings initiated by user U1 in purpose-specific savings information DB 600 (step S910). In step S910, savings support server 110 generates, for example, the user ID and purpose name indicated by the purpose-specific savings creation request in step S905, the purpose-specific ID and purpose-specific password in step S906, and the virtual account indicated by the virtual account notification in step S909. Register purpose-specific savings information associated with an account ID.

If the purpose-specific savings creation request in step S905 also includes information such as the target savings amount, savings period, and transfer destination account, the savings support server 110 registers the purpose-specific savings information further associated with these information. do. In addition, since the savings amount of the virtual account is "0 yen" immediately after the virtual account is created by user U1, the savings support server 110 initially sets the savings amount for each account of the savings information for each purpose to be registered here. It is set to "0 yen", and since there is no savings amount by account other than the savings amount by account in the savings information by purpose at present, the savings amount by purpose is also set to "0 yen".

Then, the savings support server 110 transmits to the user terminal 120-1 a purpose-specific savings creation notification indicating that the purpose-specific savings information has been registered (step S911). The purpose-specific savings creation notification includes information such as purpose-specific ID and purpose-specific password of the purpose-specific savings information registered in step S910.

When the user terminal 120-1 receives the purpose-specific savings creation notification from the savings support server 110, the user terminal 120-1 displays a purpose-specific savings creation notification screen (FIG. 12) that guides the purpose-specific ID and purpose-specific password indicated in the purpose-specific savings creation notification. ) is displayed (step S912). The user U1 informs the user U2 of the purpose-specific ID and the purpose-specific password displayed on the purpose-specific savings creation notification screen, so that the user U2 also participates in the above-mentioned savings initiated by the user U1, as described below. becomes possible.

When user terminal 120-2 accepts from user U2 an operation to participate in the above-mentioned savings (in this case, savings for the savings purpose "mother's birthday") started by user U1, user terminal 120-2 starts saving for the savings purpose. to the savings support server 110 (step S913). User terminal 120-2 displays, for example, a purpose-specific savings participation screen (see FIG. 13) for accepting input of a user ID, purpose-specific ID, purpose-specific password, etc., when user U2 performs a predetermined operation. be able to. Then, user terminal 120-2 accepts input from user U2, such as the user ID of user U2, the purpose-specific ID and the purpose-specific password of the savings initiated by user U1, on the purpose-specific savings participation screen.

In step S913, the user terminal 120-2 includes information such as the user ID, the purpose-specific ID, and the purpose-specific password received from the purpose-specific savings participation screen, and the user U2 participates in the saving of the purpose-specific ID. Send a purpose-specific savings participation request indicating that

Savings support server 110, upon receiving the purpose-based savings participation request from user terminal 120-2, creates a virtual account corresponding to the purpose-specific ID of the purpose-based savings participation request in account 420 of user U2. The instructed virtual account creation instruction is transmitted to the bank server 130-2 (step S914). In step S914, savings support server 110 creates a virtual account including information such as the account number and password of account 420 (that is, corresponding to user U2) and the purpose-specific ID of the purpose-specific savings participation request in step S913. Send creation instructions.

When bank server 130-2 receives the above virtual account creation instruction from savings support server 110, bank server 130-2 follows the virtual account creation instruction and assigns the purpose-specific ID indicated by the virtual account creation instruction in the same manner as bank server 130-1. A corresponding virtual account is created in the account 420, and the virtual account information of the created virtual account is registered in the virtual account information DB 700 (step S915). By the processing of step S915, for example, the virtual account 421 shown in FIG. 4 is created, and the virtual account information about the virtual account 421 is registered in the virtual account information DB700. The bank server 130-2 then transmits a virtual account notification that notifies the virtual account ID of the virtual account created in step S915 to the savings support server 110 (step S916).

Upon receiving the virtual account notification from bank server 130-2, savings support server 110 updates the purpose-specific savings information related to the savings initiated by user U1 and participated by user U2 (step S917). In step S917, for example, if the purpose-specific ID of the purpose-specific savings participation request in step S913 is "ID01", savings support server 110 stores the purpose-specific savings information of purpose-specific ID "ID01" in purpose-specific savings information DB 600. 6), and the virtual account ID of the virtual account notification in step S916 (for example, the virtual account ID "□ □”) are further associated with each other. As a result, the user U1's virtual account used for savings for the savings purpose "mother's birthday" with the purpose-specific ID "ID01" is associated with the user U2's virtual account.

In addition, since the savings amount of the virtual account is "0 yen" immediately after the creation of the virtual account of user U2, the savings support server 110 does not store the account-specific savings amount of the virtual account of user U2 to be additionally registered here. is initially “0 yen”. Further, at this time, if the purpose-specific savings information to be updated includes information on the target savings amount, the savings support server 110, for example, updates the target savings amount of the purpose-specific savings information to the virtual account corresponding to the purpose-specific savings information. (ie, "2" if there are virtual accounts 411 and 421) may be used as the target savings amount for each virtual account.

In addition, when user U2 participates in the above-mentioned savings initiated by user U1, savings support server 110 sends a purpose-specific savings participation notification indicating that user U2 has participated in the savings to user terminals 120-1 and 120- 2 may be sent. In this case, when user terminals 120-1 and 120-2 receive a notification of participation in savings by purpose from savings support server 110, for example, a screen for participation in savings by purpose (see FIG. 13) is displayed, The users U1 and U2 are notified that the user U2 has participated in the savings initiated by the user U1.

(Example of user registration screen)
Next, an example of the use registration screen described above will be described. FIG. 10 is a diagram illustrating an example of a usage registration screen according to the embodiment; 10, a user registration screen 1000 includes a user ID input box 1001, a user password input box 1002, a bank name input box 1003, a branch name input box 1004, an account number input box 1005, and an account password input box. 1006 and a registration button 1007 are provided.

For example, after tapping the user ID input box 1001, the user can input the desired user ID in the user ID input box 1001 by inputting characters or numbers representing the user ID desired by the user. . Similarly, the user can enter letters and numbers in each of the input boxes 1002-1006.

Further, for example, when the bank name input box 1003 is tapped, a list of bank names registered in advance is displayed, and the bank name selected by the user from the list is input to the bank name input box 1003. may be made. Similarly, when the branch name input box 1004 is tapped, a list of pre-registered branch names is displayed, and the branch name selected by the user from the list is input to the branch name input box 1004. You may do so.

By tapping a registration button 1007, the user can cause a registration request including the user information entered in each of the input boxes 1001 to 1006 to be transmitted from his/her own user terminal 120 to the savings support server 110. In the example of FIG. 10, when the registration button 1007 is tapped, user ID "U1", user password "pass1", bank name "A bank", branch name "a branch", account number "0123456", account password A registration request including the user information of “pass2” is transmitted to savings support server 110 .

(An example of the purpose-specific savings creation screen)
Next, an example of the purpose-specific savings creation screen described above will be described. FIG. 11 is a diagram showing an example of a purpose-specific savings creation screen according to the embodiment. In FIG. 11, a purpose-specific savings creation screen 1100 includes a user ID input box 1101, a purpose name input box 1102, a target savings amount input box 1103, a savings period input box 1104, a transfer account input box 1105, Savings creation button 1106 by purpose is provided.

The user can input his or her own user ID in the user ID input box 1101 by, for example, tapping the user ID input box 1101 and then inputting characters or numbers representing his or her user ID. Similarly, the user can enter letters and numbers into each of the input boxes 1102-1105, for example.

Further, by tapping the creation of purpose-specific savings creation button 1106, the user can cause a purpose-specific savings creation request including the information entered in each of the input boxes 1101 to 1105 to be transmitted to the savings support server 110. FIG. In the example of FIG. 11, when the purpose-specific savings creation button 1106 is tapped, user ID "U1", purpose name "mother's birthday", target savings amount "50000 yen", savings period "December 1, 2017" date to February 1, 2018” and a purpose-specific savings creation request including information on the transfer account “●●” is sent to the savings support server 110 .

Further, when the savings support server 110 registers the purpose-specific savings information based on the received purpose-specific savings creation request, the savings support server 110 may further generate an electronic bulletin board corresponding to the purpose-specific savings information. Access restrictions are set on this electronic bulletin board using, for example, purpose-specific IDs and purpose-specific passwords of the corresponding purpose-specific savings information. As a result, a user who does not know the purpose-specific ID and purpose-specific password cannot access the electronic bulletin board. On the other hand, users who know the purpose-specific ID and the purpose-specific password (users who save for the same purpose) can have a conversation by exchanging messages on the electronic bulletin board. A talk screen, which will be described later, can be realized, for example, by displaying this electronic bulletin board.

(Example of purpose-specific savings creation notification screen)
Next, an example of the purpose-specific savings creation notification screen described above will be described. FIG. 12 is a diagram showing an example of a purpose-specific savings creation notification screen according to the embodiment. The purpose-specific savings creation notification screen 1200 shown in FIG. 12 displays the purpose-specific savings creation request of the example of FIG. FIG. 10 is a purpose-specific savings creation notification screen displayed by the user terminal 120 that has received the creation notification from the savings support server 110. FIG.

On the goal-based savings creation notification screen 1200, a message such as "The following goal-based savings has been created" is displayed. In addition, purpose-specific savings guidance information 1201 is displayed on the purpose-specific savings creation notification screen 1200 . As the purpose-specific savings guidance information 1201, information such as purpose-specific ID, purpose-specific password, purpose name, target savings amount, savings period, payee account, etc. of the purpose-specific savings creation notice received from the savings support server 110 is displayed. .

In the example of FIG. 12, as the purpose-specific savings guidance information 1201, purpose-specific ID "ID01", purpose-specific password "pass5", purpose name "mother's birthday", target savings amount "50000 yen", saving period "2017 December 1st to February 1st, 2018” and the transfer destination account “●●” are displayed. As a result, the user of the user terminal 120 on which the purpose-specific savings guidance information 1201 is displayed can learn various information about the purpose-specific savings creation notification (that is, the user's savings for the purpose of saving) received by the user terminal 120. can be done. Then, if the user wants other users to participate in this saving, the user may notify the user of the purpose-specific ID and purpose-specific password displayed by the purpose-specific savings guidance information 1201 .

In addition, as shown in FIG. 12, an invitation button 1202 may be provided on the purpose-specific savings creation notification screen 1200 . In this case, when the user taps the invite button 1202, a list of users registered as so-called "acquaintances" of the user on the SNS is displayed, and the user selected by the user from the list is provided with purpose-specific savings guidance information. 1201 is sent. In this way, the user can easily inform other users registered as "acquaintances" of the purpose-specific ID and the purpose-specific password.

(An example of the purpose-specific savings participation screen)
Next, an example of the purpose-specific savings participation screen described above will be described. FIG. 13 is a diagram illustrating an example of a purpose-specific savings participation screen according to the embodiment; In FIG. 13, a purpose-specific savings participation screen 1300 is provided with a user ID entry box 1301 , a purpose-specific ID entry box 1302 , a purpose-specific password entry box 1303 , and a purpose-specific savings participation button 1304 .

The user can input his or her own user ID in the user ID input box 1301 by, for example, tapping the user ID input box 1301 and then inputting characters or numbers representing his or her user ID. Similarly, the user can enter letters and numbers in each of the input boxes 1302 and 1303 respectively.

Further, the user taps a purpose-specific savings participation button 1304 to transmit a purpose-specific savings participation request including various information entered in each of the input boxes 1301 to 1303 from his/her own user terminal 120 to the savings support server 110. be able to. In the example of FIG. 13, when the purpose-specific savings participation button 1304 is tapped, a purpose-specific savings participation request including the information of the user ID "U2", the purpose-specific ID "ID01", and the purpose-specific password "pass5" is sent as a savings support request. It is sent to the server 110 .

Further, when the user terminal 120 displaying the purpose-specific savings participation screen receives the purpose-specific savings guidance information 1201 as described above, the purpose-specific ID input box 1302 and the purpose-specific password input box 1303 are: The purpose-specific ID and the purpose-specific password of the received purpose-specific savings guidance information 1201 may be automatically input. In this way, it is possible to reduce the trouble of inputting the purpose-specific ID and the purpose-specific password of the user, and the user can easily participate in saving, so that the user's willingness to participate in saving can be enhanced. .

(An example of the purpose-specific savings participation notification screen)
Next, an example of the purpose-based savings participation notification screen described above will be described. FIG. 14 is a diagram illustrating an example of a purpose-specific savings participation notification screen according to the embodiment. FIG. 14 shows an example of a purpose-specific savings participation notification screen displayed when the purpose-specific savings participation button 1304 in the example of FIG. 13 is tapped.

In FIG. 14, purpose-specific savings participation notification screen 1400 is implemented by, for example, a talk screen for exchanging messages between users. Further, the purpose-specific savings participation notification screen 1400 shown in FIG. 14 is a talk screen provided corresponding to the savings for the purpose of saving "mother's birthday".

A participating user column 1401 and a participating bank column 1402 are provided on the purpose-based savings participation notification screen 1400 . A participating user column 1401 displays information indicating a user who saves for a certain saving purpose. In the case of the example of FIG. 14, since the users who save for the savings purpose of "mother's birthday" are user U1 and user U2, "user U1" and "user U2" are displayed in the participating user column 1401. ing.

The participating bank column 1402 displays information indicating the financial institution where the account of the user who makes savings for a certain savings purpose is opened. In the example of FIG. 14, the account of user U1 who saves for the purpose of saving "mother's birthday" is opened at "Bank A", and the account of user U2 who saves for the purpose of saving is opened at "Bank B". , "Bank A" and "Bank B" are displayed in the participating bank column 1402 .

In addition, the purpose-specific savings participation notification screen 1400 is provided with a talk column 1403 . Participation information 1403 a is displayed in the talk column 1403 of the purpose-specific savings participation notification screen 1400 . Participation information 1403a is information for guiding that a new user has participated in savings. In the example of FIG. 14, since the user U2 has newly participated in saving for the saving purpose of "mother's birthday", "user U2 participated" is displayed as the participation information 1403a. This allows user U1 to know that user U2 has participated in the savings.

In addition, a message input box 1404 and a message transmission button 1405 are provided on the purpose-specific savings participation notification screen 1400 . When the user enters a desired message in message input box 1404 and taps message send button 1405, the message entered in message input box 1404 is displayed in participating user column 1401 via savings support server 110. can be transmitted to the user terminal 120 of each user.

For example, in the example of FIG. 14, when the message transmission button 1405 is tapped, the message entered in the message input box 1404, the savings for the savings purpose "mother's birthday" (for example, purpose-specific ID "ID01"), is transmitted to the savings support server 110 . Then, the savings support server 110 transmits the received information to the user terminal 120 of the user (the user displayed in the participating user column 1401) who makes savings for the savings purpose. When receiving the above information from the savings support server 110, the user terminal 120 displays a message indicated by the information using the SNS application installed in the user terminal 120. FIG. As a result, users who are saving for the same saving purpose can exchange messages with each other.

Specifically, in the case of the example of FIG. 14, user U2 inputs "I will participate" in message input box 1404 and then taps message send button 1405, so that user U2 says "I will participate". A simulated message 1403 b is displayed in the talk column 1403 . Similarly, in the case of the example of FIG. 14, the user U1 tapped the message send button 1405 after inputting "Good luck" in the message input box 1404, so a message imitating the user U1 saying "Good luck" is displayed. 1403 c is displayed in the talk column 1403 .

(Example of processing performed by each device of savings support system 100 - Part 2)
Next, an example of the processing performed by each device of the savings support system 100—part 2 will be described. 15 is a sequence diagram (part 2) illustrating an example of processing performed by each device of the savings support system according to the embodiment; FIG. FIG. 15 shows that the user U1 shown in FIG. 4 is saving for a certain saving purpose (for example, the saving purpose "mother's birthday"), and the desired amount is transferred from the account 410 of the user U1 shown in FIG. An example of the processing performed by each device of the savings support system 100 when making a transfer to a virtual account (for example, the virtual account 411 shown in FIG. 4) of the user U1 (for example, the virtual account 411 shown in FIG. 4) corresponding to the savings purpose (that is, depositing money into the virtual account) is shown. .

15, similarly to the description of FIG. 9, the user terminal 120 used by the user U1 is referred to as the "user terminal 120-1", and the user terminal 120 used by the user U2 is referred to as the "user terminal 120-2". and In the description of FIG. 15, the bank server 130 of Bank A in which the account 410 (that is, the account of user U1) shown in FIG. 4 is opened is referred to as "bank server 130-1".

In FIG. 15, the user terminal 120-1, based on the operation from the user U1, sends a deposit request to the savings support server to deposit the amount specified by the user U1 into the virtual account of the user U1 corresponding to the savings purpose. 110 (step S1501). Upon receiving the deposit request from user terminal 120-1, savings support server 110 transmits a deposit instruction to bank server 130-1 to deposit the amount specified by user U1 from account 410 to virtual account 411. (step S1502).

When bank server 130-1 receives the deposit instruction from savings support server 110, bank server 130-1 transfers the amount specified by user U1 from user U1's account 410 to the virtual account corresponding to the savings purpose according to the deposit instruction. (step S1503), and sends savings amount information indicating the amount of savings after the payment to the virtual account to the savings support server 110 (step S1504). In addition, bank server 130-1, for example, when the amount of savings in the virtual account corresponding to the above-mentioned savings purpose fluctuates due to the receipt of money, the bank server 130-1 performs The virtual account information in the virtual account information DB 700 is also updated.

Upon receiving the savings amount information from bank server 130-1, savings support server 110 sets the savings amount by purpose so that the savings amount by account of user U1's virtual account corresponding to the savings purpose is the savings amount after deposit. The purpose-specific savings information in the savings information DB 600 is updated (step S1505). Then, savings support server 110 refers to the updated savings information by purpose, and the savings amount by account of the virtual account of user U1 corresponding to the savings purpose reaches the target savings amount by account corresponding to the virtual account. determine whether or not Only when this determination determines that the account-specific savings amount of the virtual account has reached the account-specific target savings amount, the savings support server 110 determines that the account-specific savings amount of the virtual account has reached the account-specific target savings amount. to the bank server 130-1 (step S1506). When bank server 130-1 receives the above savings achievement notification from savings support server 110, bank server 130-1 updates the savings achievement flag of the virtual account of user U1 corresponding to the above savings purpose to "1" (step S1507).

Further, after updating the purpose-specific savings information in step S1505, the savings support server 110 refers to the updated purpose-specific savings information and calculates the total savings for the savings purpose from the savings amount of each virtual account corresponding to the savings purpose. The amount is calculated (step S1508). Then, savings support server 110 transmits to user terminals 120-1 and 120-2 purpose-specific savings amount information including information on the savings purpose and the total savings amount calculated for that savings purpose in step S1508. (step S1509).

Further, for example, when savings support server 110 has determined that the account-specific savings amount of the virtual account of user U1 corresponding to the savings purpose has reached the account-specific target savings amount of the virtual account, as described above. At this time, purpose-specific savings amount information indicating that the account-specific savings amount of the virtual account has reached the account-specific target savings amount may be transmitted to the user terminals 120-1 and 120-2.

When user terminals 120-1 and 120-2 receive the above-mentioned savings amount information by purpose from savings support server 110, user terminals 120-1 and 120-2 display a savings amount notification screen for each purpose (see FIG. 16) (step S1510) to indicate the savings purpose. , the total savings amount for the savings purpose, etc. are guided to the user U1 and the user U2.

(Example of display screen when depositing)
Next, an example of the display screen at the time of payment will be described. FIG. 16 is a diagram illustrating an example of a display screen at the time of payment according to the embodiment; In FIG. 16, the same reference numerals are assigned to the same configurations as in FIG. 14, and the description thereof is omitted. A display screen 1600 at the time of deposit shown in FIG. 16 is, for example, a talk screen provided corresponding to savings for the savings purpose "mother's birthday", similar to the purpose-specific savings participation notification screen 1400 .

For example, when user U1 enters "deposit 1000 yen" in message input box 1404 and then taps message send button 1405, user U1's account 410 corresponding to the savings purpose "mother's birthday" A deposit request for depositing "1000 yen" into a virtual account (for example, virtual account 411 shown in FIG. 4) is transmitted to savings support server 110 . Then, as shown in FIG. 16, in the talk column 1403, a message 1601 imitating the user U1 saying "deposit 1000 yen" is displayed.

Then, when 1000 yen is deposited from account 410 to user U1's virtual account based on the above deposit request, bank A says "1000 yen has been deposited. User U1's savings amount" is displayed in talk column 1403. is 11,000 yen.The total savings amount is 16,000 yen." is displayed.

(Example of processing performed by each device of savings support system 100 - Part 3)
Next, an example of the processing performed by each device of the savings support system 100—Part 3 will be described. 17 is a sequence diagram (part 3) illustrating an example of processing performed by each device of the savings support system according to the embodiment; FIG. In FIG. 17, in addition to the savings for a certain savings purpose (for example, saving for the savings purpose "mother's birthday") shown in FIG. ) is also performed, and when a predetermined amount of money is transferred from a virtual account corresponding to a certain savings purpose to a virtual account corresponding to another savings purpose, the processing performed by each device of the savings support system 100 An example is shown.

17, similarly to the description of FIG. 9, the user terminal 120 used by the user U1 is assumed to be the "user terminal 120-1", and the account 410 shown in FIG. 4 (that is, the account of the user U1) is opened. The bank server 130 of Bank A that has been sent is called "bank server 130-1". Further, each virtual account of user U1 is assumed to be a virtual account provided in account 410, for example.

In FIG. 17, user terminal 120-1 transfers the amount specified by user U1 from the virtual account of user U1 corresponding to a certain saving purpose to the virtual account of user U1 corresponding to another saving purpose. to the savings support server 110 (step S1701).

Upon receiving the transfer request from user terminal 120-1, savings support server 110 specifies a transferable virtual account (transferable account) of user U1 (step S1702). Here, the transferable account is, for example, a virtual account different from the transfer source virtual account (for example, the virtual account 411) among the virtual accounts of the user U1 (that is, the virtual account associated with the user ID “U1”). are all virtual accounts of user U1 corresponding to other savings purposes. The savings support server 110 then transmits a transferable account notification indicating the specified transferable account to the user terminal 120-1 (step S1703).

Upon receiving the transferable account notification, user terminal 120-1 displays the transferable account specified by savings support server 110 (step S1704), and guides user U1 to the transferable account. When user U1 selects one of the transferable accounts, user terminal 120-1 transmits a selected account notification indicating the selected transferable account to savings support server 110 (step S1705).

Savings support server 110, upon receiving the selected account notification, transmits to bank server 130-1 a transfer instruction to transfer the amount specified by the user in step S1701 to the transferable account selected in step S1705 ( step S1706). Bank server 130-1 transfers the amount designated by user U1 to the selected transferable account according to the transfer instruction received from savings support server 110 (step S1707). Then, bank server 130-1 transmits to savings support server 110 savings amount information indicating the savings amount after transfer of each of the transfer source virtual account and the transfer destination virtual account (step S1708). After the process of step S1708, the savings support server 110 may perform the processes after step S1505 in FIG. 15 (excluding the process of step S1507).

(Example of display screen at the time of transfer)
Next, an example of the display screen at the time of transfer will be described. 18 is a diagram illustrating an example of a display screen at the time of transfer according to the embodiment; FIG. In FIG. 18, the same components as in FIG. 14 are denoted by the same reference numerals, and descriptions thereof are omitted. A display screen 1800 at the time of transfer shown in FIG. 18 is, for example, a talk screen provided corresponding to savings for the savings purpose "mother's birthday", similar to the purpose-specific savings participation notification screen 1400 .

For example, when user U1 enters "1000 yen transfer" in message input box 1404 and taps message send button 1405, user U1's virtual account (for example, A transfer request is sent to the savings support server 110 to transfer "1000 yen" from the indicated virtual account 411) to the virtual account of the user U1 corresponding to another savings purpose. Then, as shown in FIG. 18, in the talk column 1403, a message 1801 imitating user U1 saying "1000 yen transfer" is displayed.

Then, when a transferable account is specified based on the transfer request and a transferable account notification is received from the savings support server 110, transferable account information 1802 indicating the specified transferable account is displayed. In the example of FIG. 18, the user U1's virtual account corresponding to the savings purpose "family trip" (for example, the virtual account with the virtual account ID "ΔΔ" shown in FIG. 6) is specified as the transferable account.

Therefore, in the example of FIG. 18, check boxes corresponding to “family trip” and “family trip” and a transfer execution button 1803 are displayed in the transferable account information 1802 . In this case, for example, the user U1 can select the virtual account of the user U1 corresponding to the saving purpose "family trip" as the transfer destination by tapping the check box corresponding to "family trip".

In this case, for example, user U1 can tap transfer execution button 1803 to transmit a transfer execution request to the selected transfer destination to savings support server 110 . As a result, for example, when user U1's high-priority savings purpose "family trip" is not progressing as expected, user U1 can make a low-priority savings purpose for himself/herself. Funds can be transferred from "mother's birthday" savings.

(Example of processing performed by each device of savings support system 100 - Part 4)
Next, an example of the processing performed by each device of the savings support system 100—No. 4 will be described. 19 is a sequence diagram (part 4) illustrating an example of processing performed by each device of the savings support system according to the embodiment; FIG. FIG. 19 shows that the user U1 and the user U2 shown in FIG. 4 are jointly saving for a certain saving purpose (for example, saving for the saving purpose "mother's birthday"), and each virtual account used for the saving is shown. An example of processing performed by each device of the savings support system 100 when changing the target savings amount for each account corresponding to .

19, similarly to the description of FIG. 9, the user terminal 120 used by the user U1 is referred to as the "user terminal 120-1", and the user terminal 120 used by the user U2 is referred to as the "user terminal 120-2". and 19, the bank server 130 of Bank A in which the account 410 (that is, the account of user U1) shown in FIG. Namely, the bank server 130 of Bank B where user U2's account) is opened is referred to as "bank server 130-2".

In FIG. 19, the user terminal 120-1, based on the operation from the user U1, sends a reimbursement request to the savings support server to change the target savings amount for each account of the virtual account of the user U1 corresponding to the savings purpose. 110 (step S1901).

Savings support server 110, upon receiving the above-described reimbursement request from user terminal 120-1, specifies other users who can reimburse (reimbursable users) (step S1902). Here, a transferable account is, for example, a user who makes savings for the purpose of savings, and is all users other than user U1 (here, user U2). Then, the savings support server 110 transmits to the user terminal 120-1 a user notification indicating the identified user who can make the payment to the user terminal 120-1 (step S1903).

When the user terminal 120-1 accepts the payment available user notification, the user terminal 120-1 displays a payment application screen (see FIG. 20) that accepts input of the payment available user indicated by the payment available user notification and the payment amount desired by the user U1. (Step S1904). Then, user terminal 120-1 selects one of the reimbursable users by user U1 on the reimbursement application screen, and when user U1 inputs the reimbursement amount, user terminal 120-1 selects the user selected by user U1 and A payment implementation request indicating the input payment amount is transmitted to the savings support server 110 (step S1905).

In the example of FIG. 19, the user U1 selects the user U2, and the amount of payment input by the user U1 is 5,000 yen. assumed to have been sent. In this case, the savings support server 110 transmits to the user terminal 120-2 a reimbursement request notification notifying that user U1 has requested reimbursement of the reimbursement amount input (step S1906).

When the user terminal 120-2 receives the request for reimbursement, the user terminal 120-2 displays a reimbursement permission/refusal screen for accepting whether or not reimbursement of the reimbursement amount input by the user U1 is permitted (step S1907). Then, the user terminal 120-2 transmits a payment permission notice to the savings support server 110 when the payment permission is accepted, and transmits a payment refusal notice to the savings support server 110 when the payment refusal is accepted (step S1908). .

Savings support server 110 reduces the target savings amount for each account of the virtual account of user U1 corresponding to the savings purpose by the amount to be paid on behalf of user U1 corresponding to the savings purpose only when receiving the notice of permission to pay for the savings. The purpose-specific savings information is updated so that the account-specific target savings amount of the virtual account of user U2 is increased by the advance amount input by user U1 (step S1909).

Further, in this case, when the target savings amount for each account is updated, savings support server 110 sends, for example, notification of the target savings amount for each account indicating the updated target savings amount for each account to the user terminals 120-1 and 120-2. can be sent to In this case, for example, when the user terminals 120-1 and 120-2 receive the notification of the target savings amount for each account, the target savings amount screen for each account showing the updated target savings amount for each account (see FIG. 22). ) is displayed to guide the users U1 and U2 about the updated target savings amount for each account.

(Example of display screen at the time of reimbursement)
Next, an example of the display screen at the time of reimbursement will be described. 20 is a diagram illustrating an example of a reimbursement application screen according to the embodiment; FIG. In FIG. 20, the same reference numerals are assigned to the same configurations as in FIG. 14, and the description thereof is omitted. The reimbursement application screen 2000 shown in FIG. 20 is, for example, a talk screen provided corresponding to the savings for the savings purpose "mother's birthday", similar to the purpose-specific savings participation notification screen 1400 .

The reimbursement application screen 2000 shows a reimbursable user identified by the savings support server 110 and has a check box 2001 for selecting the reimbursable user, a reimbursement amount input box 2002 for receiving input of the reimbursement amount, and a reimbursement application button. 2003 and are provided.

For example, on the reimbursement application screen 2000, the user U1 checks the check box 2001, enters "5000 yen" in the reimbursement amount input box 2002, and taps the reimbursement application button 2003. A payment execution request indicating that the user is user U2 and that the payment amount input by user U1 is 5000 yen is transmitted to savings support server 110 . In this case, the user terminal 120 of the user U2 (for example, the user terminal 120-2 shown in FIG. 18) displays a payment permission/refusal screen 2100 shown in FIG.

FIG. 21 is a diagram illustrating an example of a payment permission/refusal screen according to the embodiment; In FIG. 21, the same reference numerals are assigned to the same configurations as in FIG. 14, and the description thereof is omitted. The payment permission/refusal screen 2100 shown in FIG. 21 is, for example, similar to the purpose-specific savings participation notification screen 1400, a talk screen provided corresponding to savings for the savings purpose "mother's birthday".

In FIG. 21, the reimbursement permission/refusal screen 2100 displays "A request for reimbursement of 5,000 yen has been received from user U1." In addition, an allowance button 2101 and a refusal button 2102 are provided on the payment allowance/denial screen 2100 . The user U2 may tap the permission button 2101 to permit the payment. In this case, the user terminal 120 of the user U2 transmits a notice of allowance for advance payment to the savings support server 110 . Also, the user U2 may tap the rejection button 2102 to reject the payment. In this case, the user terminal 120 of the user U2 transmits a notice of rejection of advance payment to the savings support server 110 . In the example of FIG. 21, when the permission button 2101 is tapped by the user U2, the target savings amount screen 2200 for each account shown in FIG. 22 is subsequently displayed.

FIG. 22 is a diagram showing an example of an account-by-account target savings screen according to the embodiment. In FIG. 22, the same components as in FIG. 14 are denoted by the same reference numerals, and descriptions thereof are omitted. The account-by-account target savings amount screen 2200 shown in FIG. 22 is, for example, a talk screen provided corresponding to savings for the savings purpose "mother's birthday", like the purpose-by-purpose savings participation notification screen 1400 .

In FIG. 22, the target savings amount by account screen 2200 displays "User U1's target savings amount by account has increased from 35,000 yen to 30,000 yen. User U2's target savings amount by account has increased from 15,000 yen to 20,000 yen." Now." is displayed. As a result, user U1 and user U2 can know the target savings amount for each account after the change.

(Another example of processing performed by savings support server 110)
Next, another example of processing performed by the savings support server 110 will be described. 23 is a flowchart illustrating an example of savings support processing performed by the savings support server according to the embodiment; FIG. In FIG. 23, the savings support server 110 determines whether or not a purpose-specific savings creation request has been received from the user terminal 120 (step S2301).

If it is determined that the purpose-specific savings creation request has not been received (step S2301: No), the savings support server 110 proceeds to the process of step S2305. When it is determined that the purpose-specific savings creation request has been received (step S2301: Yes), the savings support server 110 identifies the account of the user of the user terminal 120 who requested the purpose-specific savings creation (step S2302). In step S2302, savings support server 110 refers to user information DB 500, for example, and acquires the bank name, branch name, account number, etc. corresponding to the user ID of the received savings creation request by purpose. It is possible to identify the account of the user of the user terminal 120 who requested the savings creation.

Next, savings support server 110 creates a virtual account in bank server 130 of the financial institution where the account of the user of user terminal 120 who requested to create savings by purpose has been opened, based on the identification result of step S2302. instruct (step S2303). In step S2303, the savings support server 110 stores, for example, the bank server 130 to be instructed, in the account of the user of the user terminal 120 requesting the creation of the savings by purpose corresponding to the savings purpose of the savings creation request by purpose. send a virtual account creation instruction to create a virtual account to Then, savings support server 110 stores the virtual account created by the instruction in step S2303 in association with the savings purpose of the purpose-specific savings creation request (step S2304).

The savings support server 110 then determines whether or not a participation request has been received from the user terminal 120 (step S2305). If it is determined that the participation request has not been received (step S2305: No), the savings support server 110 proceeds to the process of step S2309. When it is determined that the participation request has been received (step S2305: Yes), the savings support server 110 identifies the account of the user of the user terminal 120 who requested the participation (step S2306). In step S2306, savings support server 110 refers to user information DB 500, for example, and acquires the bank name, branch name, account number, etc., corresponding to the user ID of the participation request. of users can be identified.

Next, based on the identification result of step S2306, savings support server 110 instructs bank server 130 of the financial institution where the account of the user of user terminal 120 requesting participation has been opened to create a virtual account ( step S2307). In step S2307, savings support server 110 creates, for example, a virtual account corresponding to the savings purpose of the participation request in the account of the user of user terminal 120 that is the source of the participation request, for bank server 130 to be instructed. Send a virtual account creation instruction instructing you to do so. Then, savings support server 110 stores the virtual account created by the instruction in step S2307 in association with the savings purpose of the participation request (step S2308).

Savings support server 110 then determines whether or not savings amount information has been received from bank server 130 (step S2309). If it is determined that the savings amount information has not been received (step S2309: No), the savings support server 110 ends the processing shown in FIG. If it is determined that the savings amount information has been received (step S2309: Yes), the savings support server 110 identifies the virtual account whose savings amount has changed based on the received savings amount information (step S2310), and returns the savings information by purpose. The savings amount for each account of the virtual account whose savings amount has changed in the DB 600 is updated (step S2311).

Then, savings support server 110 calculates the total savings amount for the savings purpose from the savings amount of each virtual account used for savings for the same savings purpose as the virtual account whose savings amount has changed (step S2312). Purpose-specific savings amount information including information on the purpose and the total savings amount calculated for the savings purpose is transmitted to the user terminal 120 (step S2313). In step S2313, the user terminal 120 to which the savings support server 110 transmits the purpose-specific savings amount information is the user terminal of the user corresponding to each virtual account used for savings for the same savings purpose as the virtual account whose savings amount has changed. 120.

Next, the savings support server 110 determines whether or not the savings amount of the virtual account whose savings amount has changed has reached the target savings amount for each account of the virtual account (step S2314). If it is determined that the savings amount of the virtual account has not reached the target savings amount for each account of the virtual account (step S2314: No), the savings support server 110 ends the processing of FIG.

When determining that the savings amount of the virtual account has reached the target savings amount for each account of the virtual account (step S2314: Yes), the savings support server 110 determines that the savings amount of the virtual account has reached the target savings amount for each account. Information (account-specific goal achievement information) is transmitted to the user terminal 120 (step S2315). In step S2315, the user terminal 120 to which the savings support server 110 transmits the account-specific goal achievement information is the user terminal of the user corresponding to each virtual account used for saving for the same savings purpose as the virtual account whose savings amount has changed. 120.

Next, the savings support server 110 determines whether or not the target savings amount corresponding to the savings purpose used to calculate the total savings amount has been reached (step S2316). When determining that the total savings amount has not reached the target savings amount (step S2316: No), the savings support server 110 terminates the processing of FIG.

If it is determined that the total savings amount has reached the target savings amount (step S2316: Yes), the savings support server 110 sends information (target achievement information) to the user terminal to guide that the total savings amount has reached the target savings amount. 120 (step S2317). In step S2317, the user terminal 120 to which the savings support server 110 transmits the goal achievement information is the user terminal 120 of the user corresponding to each virtual account used for saving for the same savings purpose as the virtual account whose savings amount has changed. be.

Next, the savings support server 110 determines whether or not there is a transfer destination account setting corresponding to the savings purpose used to calculate the total savings amount (step S2318). If it is determined that the transfer destination account is not set (step S2318: No), the savings support server 110 terminates the processing shown in FIG. If it is determined that the transfer account is set (step S2318: Yes), the savings support server 110 transfers the savings amount of each virtual account corresponding to the purpose of saving used for calculating the total savings amount to the transfer account. is instructed to the bank server 130 provided with each virtual account (step S2319), and the process of FIG. 23 ends.

In addition, when the total savings amount reaches the target savings amount and the transfer to the transfer account is executed, the savings support server 110 transmits a predetermined message to the bank server 130 of the bank where the transfer account is opened. You may make it This message is set in advance in the savings support server 110 by the user who makes the savings, in the same way as the transfer account. In this case, the bank server 130 that has received the message transmits the received message to the terminal of the holder of the transfer account, for example. To give a specific example, a user who makes savings for the savings purpose of "mother's birthday" sets the mother's account as the transfer account to the savings support server 110, and sends a message "Thank you mom. I love you." Decided Children: Representative Keisuke”. In this case, the savings support server 110 sends the message "Thank you, Mom." Children loved by you: Representative Keisuke" is sent to the bank server 130 of the bank where the mother's account is opened.

In addition, when the total savings amount reaches the target savings amount, the savings support server 110 may invite other users preset by the user who makes the savings to save for the savings purpose. For example, the savings support server 110 invites another user by transmitting the purpose-specific savings guidance information 1201 described with reference to FIG. 12 to the preset user terminal 120 of another user. As a specific example, a user who saves for the purpose of saving "mother's birthday" sets the mother as a user to be invited to the savings support server 110 when the total savings amount reaches the target savings amount. .

In this case, when the total savings amount for the savings purpose "mother's birthday" reaches the target savings amount, the savings support server 110 displays the savings guidance information for each purpose for the savings purpose "mother's birthday". to the mother's user terminal 120 to invite the mother. Then, when the mother accepts this invitation, the talk screen 1400 described using FIG. 14 and the like is displayed on the mother's user terminal 120 as well. As a result, the mother and the user (for example, the child) who made savings for the savings purpose of "mother's birthday" can exchange messages and the like via the talk screen 1400 .

In addition, in this case, the savings support server 110 adds an account to the SNS when the total savings amount reaches the target savings amount in order to improve the convenience of the invited user (mother in the above example). Stores registered with are also invited. In this case, for example, the invited user can place an order with the store via the talk screen 1400 . Also, in this case, if the account of the store to which the saved money is to be transferred is set to the account of the store, the payment to the store can be easily made. Note that, in this case, the savings support server 110 may cause the transfer to be made to the transfer destination account in response to receiving a transfer execution instruction from the user. Then, for example, the user may issue a transfer execution instruction after placing the above order.

In addition, when the total amount of savings for a certain savings purpose reaches the target savings amount and the savings are completed, for example, the savings support server 110 can The user who has made savings for the savings purpose may be withdrawn from the savings for the savings purpose by, for example, canceling the association with the separate savings information.

FIG. 24 is a flowchart illustrating an example of a target savings amount change process for each account performed by the savings support server according to the embodiment; In FIG. 24, the savings support server 110 determines whether or not a payment request has been received from the user terminal 120 (step S2401). If no reimbursement request has been received (step S2401: No), the savings support server 110 ends the processing shown in FIG. If a reimbursement request has been received (step S2401: Yes), the savings support server 110 identifies a reimbursement possible user (step S2402), and sends a reimbursement possible user notification indicating the identified reimbursement possible user to the user terminal 120 of the reimbursement request source. It transmits (step S2403).

Next, the savings support server 110 determines whether or not a payment execution request has been received from the user terminal 120 (step S2404). If it is determined that the payment implementation request has not been received (step S2404: No), the savings support server 110 ends the processing shown in FIG.

If it is determined that the payment implementation request has been received (step S2404: Yes), the savings support server 110 sends the payment permission/refusal information to the user terminal 120 of the user who can be paid on payment selected by the user of the user terminal 120 who requested the payment. It transmits (step S2405). Then, the savings support server 110 determines whether or not the user of the user terminal 120 to which the payment permission/refusal information is transmitted has permitted the payment (step S2406). If it is determined that the payment has been rejected (step S2406: No), the savings support server 110 ends the processing shown in FIG.

If it is determined that reimbursement is permitted (step S2406: YES), savings support server 110 sets the account-specific target savings amount corresponding to the virtual account of the user of user terminal 120 who requested reimbursement to the specified amount specified by the user. In addition to decreasing the target savings amount by account corresponding to the virtual account of the user of the user terminal 120 to which the payment permission/refusal information is transmitted, the savings information by purpose is updated so as to increase the specified amount (step S2407). end the processing shown in .

As described above, the savings support server 110 calculates the total savings amount of the entire savings for the savings purpose from the savings amount of each account used for savings for the same savings purpose, and compares the savings purpose and the calculated total savings The purpose-specific savings information including the amount and information can be transmitted to the user terminal 120 of the user who makes the savings for the savings purpose. As a result, the savings support server 110 can allow the user who makes the savings for the savings purpose to easily grasp the total savings amount of the entire savings for the savings purpose.

In the example described in the present embodiment, an example in which savings support server 110 is provided separately from bank server 130 has been described, but the present invention is not limited to this. For example, the savings support server 110 may be integrated with any bank server 130 . In this case, for example, the CPU 201 of the bank server 130 executes a program stored in the memory 202, or the memory 202 or the communication IF 203 of the bank server 130 executes each function of the savings support server 110 described above. It can realize the function of the part.

Moreover, the savings support method described in the present embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. This savings support program is a computer-readable recording medium such as hard disk, flexible disk, CD (Compact Disc)-ROM, MO (Magneto-Optical disk), DVD (Digital Versatile Disk), USB (Universal Serial Bus) memory, etc. is recorded in a computer and executed by being read out from the recording medium by a computer. Also, the savings support program may be distributed via a network such as the Internet.

As explained above, according to the present invention, it is possible for a saver to easily grasp the total amount of savings for the purpose of saving when a plurality of accounts are used for saving for a certain purpose. can be

As described above, the savings support device, the savings support method, and the savings support program according to the present invention are useful as a savings support device, a savings support method, and a savings support program that support savers who save money. It is suitable for a savings support device, a savings support method, and a savings support program that support a saver who saves for a certain savings purpose using a plurality of accounts.

100 savings support system 110 savings support server 111 storage unit 120 user terminal 130 bank server 131 account information DB
150 network 410,420 accounts 411,421 virtual accounts 500 user information DB
600 Savings information DB by purpose
700 Virtual account information DB

Claims (7)

a calculation unit that refers to a storage unit that associates and stores a purpose of saving and a savings amount of each account used for saving for the purpose, and calculates the total amount of savings corresponding to the purpose;
a determination unit that determines whether or not the total amount of savings has reached the target amount of savings stored in the storage unit in association with the purpose;
Purpose-specific savings amount information including information on the purpose, the total savings amount calculated by the calculation unit, and the target savings amount ; an output unit for outputting, when determined, information guiding that the total amount of savings has reached the target amount of savings to a terminal of the user who makes the desired savings;
with
The storage unit further stores an account-specific target savings amount for each account used for the target savings,
Based on the savings amount of each account used for the target savings and the target savings amount for each account used for the target savings, , further determine whether the savings amount of the account has reached the target savings amount for each account of the account;
When it is determined that the savings amount of any one of the accounts used for the target savings has reached the target savings amount for each account, the output unit determines that the savings amount has reached the target savings amount for each account. further outputting to the terminal of the user information guiding the account
A savings support device characterized by: each said account is a virtual account corresponding to said purpose;
The savings support device according to claim 1, characterized by: The storage unit further stores information identifying the account of the user,
When receiving a purpose-specific savings creation request that includes information on the user and the purpose and indicates that the user will make savings for the purpose, the storage unit is referred to and the account of the user is specified. , further comprising a virtual account creation unit that instructs the financial institution where the account of the user is opened to create a virtual account corresponding to the purpose of the user in the account of the user;
The storage unit associates and stores the purpose and the savings amount of the virtual account created based on the instruction of the virtual account creation unit.
3. The savings support device according to claim 1 or 2, characterized by: Transfer for executing a process of transferring money saved in each account used for the purpose of saving to a preset account when the determination unit determines that the total amount of savings has reached the target savings amount 4. The savings support device according to any one of claims 1 to 3 , further comprising an instruction unit. When a change request to reduce the target savings amount by account of the first account used for the purpose of savings by a predetermined amount is received, the target savings amount by account of the first account is decreased by the predetermined amount, and further comprises a change unit that changes the target savings amount for each account of the second account, which is a different account and is used for the target savings, to increase the predetermined amount;
The savings support device according to any one of claims 1 to 4 , characterized by: the computer
calculating the total amount of savings corresponding to the purpose by referring to a storage unit that associates and stores the purpose of savings and the savings amount of each account used for the purpose of savings;
Determining whether the total amount of savings has reached the target amount of savings stored in the storage unit in association with the purpose,
further storing in the storage unit an account-specific target savings amount for each account used for the target savings;
Based on the savings amount of each account used for the purpose of savings and the target savings amount by account for each account used for the purpose of savings, the savings of each account used for the purpose of savings further determine whether the amount has reached the target savings amount by account for the account;
If it is determined that the sum of the purpose-specific savings amount information including information on the purpose, the calculated total savings amount, and the target savings amount and the calculated savings amount has reached the target savings amount, Information that guides that the total savings amount has reached the target savings amount, and information that the savings amount in one of the accounts used for the purpose of saving has reached the target savings amount for each account If determined, output information guiding the account whose savings amount has reached the target savings amount for each account to the terminal of the user who makes the desired savings;
A savings support method characterized by executing a process. to the computer,
calculating the total amount of savings corresponding to the purpose by referring to a storage unit that associates and stores the purpose of savings and the savings amount of each account used for the purpose of savings;
Determining whether the total amount of savings has reached the target amount of savings stored in the storage unit in association with the purpose,
further storing in the storage unit an account-specific target savings amount for each account used for the target savings;
Based on the savings amount of each account used for the purpose of savings and the target savings amount by account for each account used for the purpose of savings, the savings of each account used for the purpose of savings further determine whether the amount has reached the target savings amount by account for the account;
If it is determined that the sum of the purpose-specific savings amount information including information on the purpose, the calculated total savings amount, and the target savings amount and the calculated savings amount has reached the target savings amount, Information that guides that the total savings amount has reached the target savings amount, and information that the savings amount in one of the accounts used for the purpose of saving has reached the target savings amount for each account If determined, output information guiding the account whose savings amount has reached the target savings amount for each account to the terminal of the user who makes the desired savings;
A savings support program characterized by causing a process to be executed.

Images