Computer system and program for securing deposits in a customer's savings account according to their purpose.

Abstract

To provide a computer system for securing deposits in a customer's savings account according to their specific needs. [Solution] The computer system of the present invention is configured to receive a restraining request relating to the restraining of at least a portion of an amount in a customer's savings account, wherein the restraining request includes information indicating the customer's purpose, and in response to the restraining request, to associate at least a portion of an amount in the customer's savings account with the customer's purpose and restrain at least a portion of that amount.

Description

[Technical Field]

[0001] This invention relates to a computer system and program for securing deposits in a regular savings account according to the customer's purpose. [Background technology]

[0002] It has long been known that accounts are opened according to the customer's purpose (see, for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] GMO Aozora Net Bank, Ltd., “Separate Accounts”, [online], [searched August 5, 2024], Internet<https: / / gmo-aozora.com / priv / service / purpose.html> [Overview of the project] [Problems that the invention aims to solve]

[0004] Opening a new account requires a considerable amount of time and effort.

[0005] The present invention aims to provide a computer system and program for securing deposits in a regular savings account according to the customer's purpose without requiring the opening of a new account. [Means for solving the problem]

[0006] In one aspect of the present invention, the computer system of the present invention is a computer system for securing a deposit in a customer's savings account according to the customer's purpose, wherein the computer system is configured to receive a restraining request relating to the restraining of at least a portion of the amount in the customer's savings account, wherein the restraining request includes information indicating the customer's purpose, and in response to the restraining request, to associate the at least a portion of the amount in the customer's savings account with the customer's purpose and restrain the at least a portion of the amount.

[0007] In one embodiment of the present invention, the amount of at least the amount of the customer's ordinary deposit account that is held in place may be configured so that it cannot be moved, either directly or indirectly.

[0008] In one embodiment of the present invention, the computer system may be configured to perform a process to notify the customer that the transfer of at least a portion of the reserved amount in the customer's savings account is to be refused, in response to receiving a transfer request from the customer.

[0009] In one embodiment of the present invention, the restraining request includes a deposit request that requires the customer to make deposits in the customer's savings account, the customer's purpose includes the customer's deposit purpose, the deposit request includes at least information indicating the customer's deposit purpose, information indicating the customer's desired deposit amount, and information indicating the customer's desired deposit period, and associating at least a portion of the amount in the customer's savings account with the customer's purpose and restraining at least a portion of the amount may include associating at least a portion of the amount in the customer's savings account with the customer's deposit purpose and restraining at least a portion of the amount during the customer's desired deposit period.

[0010] In one embodiment of the present invention, associating at least a portion of the amount in the customer's ordinary deposit account with the customer's savings purpose and restricting the at least portion of the amount during the customer's desired savings period includes, at predetermined intervals during the customer's desired savings period, associating at least a portion of the amount in the customer's ordinary deposit account with the customer's savings purpose and restricting the at least portion of the amount, wherein the predetermined interval may be shorter than the desired savings period.

[0011] In one embodiment of the present invention, the system may be configured to receive an additional restraint request that additionally request the restraint of at least another amount in the customer's savings account during the customer's desired savings period, and in response to receiving the additional restraint request, to associate the other at least amount with the customer's savings purpose and to restrain the other at least amount.

[0012] In one embodiment of the present invention, the computer system may be configured to further associate the customer's savings purpose with one of several partner companies of the bank managing the computer system.

[0013] In one embodiment of the present invention, the computer system is configured to communicate with the management system of one partner, and the computer system may further be configured to send a grant request to the management system of one partner requesting that when the customer's desired deposit period has elapsed, or when the total of at least a portion of the amounts bound in relation to the customer's deposit purpose reaches the customer's desired deposit amount, grant the customer a benefit corresponding to the customer's desired deposit amount.

[0014] In one embodiment of the present invention, the computer system may be further configured to release the restraint on at least a part of the amount restricted in relation to the savings purpose of the customer when the desired savings period of the customer has elapsed and the total of at least a part of the amount restricted in relation to the savings purpose of the customer reaches the desired savings amount of the customer.

[0015] In one aspect of the present invention, the program of the present invention is a program executed in a computer system for securing a deposit in a regular savings account according to the purpose of a customer. The computer system includes a processor unit. When the program is executed by the processor unit, it receives a restraint request related to the restraint of at least a part of the amount in the regular savings account of the customer, and the restraint request includes information indicating the purpose of the customer. And in response to the restraint request, the processor unit is configured to at least associate the at least a part of the amount in the regular savings account of the customer with the purpose of the customer and restrain the at least a part of the amount.

Advantages of the Invention

[0016] According to the present invention, it is possible to provide a computer system and a program for securing a deposit in a regular savings account according to the purpose of a customer without the need to newly open an account.

Brief Description of the Drawings

[0017] [Figure 1A] A diagram showing an example of a screen 100 displayed on a device operated by a customer [Figure 1B] A diagram showing an example of a screen 110 displayed on a device operated by a customer [Figure 2] A diagram showing an example of the configuration of a system 200 for securing a deposit in a regular savings account according to the purpose of a customer [Figure 3A] A diagram showing an example of the configuration of information stored in a customer database unit 251 [Figure 3B]A diagram showing an example of the configuration of information stored in the regular savings account database section 252 [Figure 4] A diagram showing an example of the processing executed in the computer system 210 [Figure 5] A diagram showing an example of the processing executed in the computer system 210 [Figure 6] A diagram showing another example of the processing executed in the computer system 210

Embodiments for Carrying Out the Invention

[0018] Hereinafter, the terms used in this specification are defined.

[0019] In this specification, "restraining" the amount in an account means performing processing to prevent withdrawal of that amount from the account, performing processing to prevent transfer of that amount from the account, performing processing to prevent transactions of that amount in the account, and performing processing to prevent movement of that amount within the account. That is, the restrained amount in the account cannot be withdrawn or transferred from the account, cannot be the subject of a transaction, and cannot be moved within the account.

[0020] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0021] 1. Screen transitions displayed on user devices operated by the customer. FIG. 1A shows an example of the screen 100 displayed on the device operated by the customer. The screen 100 is a screen displayed when the customer restrains and accumulates the deposits in the regular savings account according to the customer's purpose. The screen 100 can be displayed on the user device operated by the customer.

[0022] Screen 100 is a screen for requesting a customer to make a deposit in their savings account. In the embodiment shown in Figure 1A, screen 100 includes an area for displaying the customer's name, an area for displaying the branch name that manages the customer's savings account, an area for displaying the balance in the customer's savings account, a deposit purpose area 101 for entering the customer's desired deposit purpose, a target deposit period area 102 for entering the customer's desired target deposit period, a target deposit amount area 103 for entering the customer's desired target deposit amount, and a deposit start area 104 for starting the deposit with the entered conditions.

[0023] In the embodiment shown in Figure 1A, the savings purpose area 101 has a pull-down menu format that allows the customer to selectively input their desired savings purpose. This allows the customer to select a savings purpose that suits their own purpose from among several savings purposes displayed in the pull-down menu (e.g., travel, car purchase, education, etc.). However, the present invention is not limited to this. The savings purpose area 101 may be configured to allow the customer to freely input their savings purpose, insofar as it is possible to identify the customer's desired savings purpose.

[0024] In the embodiment shown in Figure 1A, the target savings period area 102 has a pull-down menu format that allows the customer to selectively input their desired target savings period. This allows the customer to select a target savings period that suits their own needs from among several target savings periods displayed in the pull-down menu (e.g., 1 week, 1 month, 6 months, 12 months, 24 months, 36 months, 48 ​​months, 60 months, 120 months, etc.). However, the present invention is not limited thereto. The target savings period area 102 may be configured to allow the customer to freely input the target savings period, for example, as long as it is possible to identify the customer's desired target savings period. The target savings period is the period that indicates the maturity of the savings.

[0025] In the embodiment shown in Figure 1A, the target savings amount area 103 has a free-form input field in which the customer can enter their desired target savings amount. This allows the customer to enter their desired target savings amount in the free-form input field. However, the present invention is not limited thereto. The target savings amount area 103 may also have a pull-down menu in which the customer can selectively enter their desired target savings amount, insofar as it is possible to identify the customer's desired target savings amount, for example, and the customer may select an amount that matches their own target savings amount from among a plurality of target savings amounts displayed in the pull-down menu (e.g., 10,000 yen, 20,000 yen, 30,000 yen, 50,000 yen, 100,000 yen, etc.).

[0026] Customers can make deposits in their ordinary savings account by entering the necessary information in the deposit purpose area 101, the target deposit period area 102, and the target deposit amount area 103, and then selecting the deposit start area 104. The deposit start area 104 may change from a non-selectable state to a selectable state once the necessary information in the deposit purpose area 101, the target deposit period area 102, and the target deposit amount area 103 has been entered, or it may change from a hidden state to a visible state so that it can be selected once the necessary information in the deposit purpose area 101, the target deposit period area 102, and the target deposit amount area 103 has been entered.

[0027] Once a customer begins accumulating deposits in their savings account, at least a portion of the amount in that account will be repeatedly held (for example, at predetermined intervals or on specific dates each month) in connection with the customer's savings objective, and will remain held until the target savings amount is reached or the target savings period has elapsed. For example, if the target savings amount is 60,000 yen and the target savings period is 1 year, 5,000 yen will be held in the first month, another 5,000 yen will be held in the second month, and so on, until the twelfth month.

[0028] In this way, customers can secure deposits in their savings accounts for the medium to long term, according to their objectives, without having to open a new account, by continuing to deposit and accumulate funds in their savings accounts according to their objectives. Furthermore, customers can receive rewards (e.g., points, coupons, or small gifts) if they continue to deposit funds until their desired target deposit period has elapsed or their desired target deposit amount has been reached. Such rewards can serve as an incentive for customers to continue depositing funds in their savings accounts according to their objectives.

[0029] The embodiment shown in Figure 1A illustrates an example in which deposits in a savings account are held and accumulated according to the customer's purpose, but the present invention is not limited to this. Insofar as deposits in a savings account are held according to the customer's purpose, non-accumulation type inventions (i.e., inventions in which deposits in a savings account are held according to the customer's purpose but are not accumulated) are also within the scope of the present invention.

[0030] Figure 1B shows an example of a screen 110 displayed on a device operated by the customer. Screen 110 is displayed when the customer wishes to hold but not deposit funds into their savings account, according to their purpose. Screen 110 may be displayed on a user device operated by the customer.

[0031] Screen 110 is a screen for requesting that a customer's savings account be locked up in a non-recurring manner. In the embodiment shown in Figure 1B, screen 110 includes an area for displaying the customer's name, an area for displaying the branch name managing the customer's savings account, an area for displaying the balance in the customer's savings account, a lock-up purpose area 111 for entering the customer's desired lock-up purpose, a lock-up period area 112 for entering the customer's desired lock-up period, a lock-up amount area 113 for entering the customer's desired lock-up amount, and a lock-up start area 114 for starting the lock-up under the entered conditions.

[0032] In the embodiment shown in Figure 1B, the constraint objective area 111 has a pull-down menu format that allows the customer to selectively input their desired constraint objective. This allows the customer to select an objective that suits their own from among several constraint objectives displayed in the pull-down menu (e.g., monthly reward, allowance, etc.). However, the present invention is not limited to this. The constraint objective area 111 may be configured, for example, to allow the customer to freely input a constraint objective, as long as it is possible to identify the customer's desired constraint objective.

[0033] In the embodiment shown in Figure 1B, the contract period area 112 has a pull-down menu format that allows the customer to selectively input their desired contract period. This allows the customer to select a contract period that suits their needs from among several contract periods displayed in the pull-down menu (e.g., 1 week, 2 weeks, 3 weeks, 1 month, 2 months, 3 months, etc.). However, the present invention is not limited to this. The contract period area 112 may be configured, for example, to allow the customer to freely input the contract period, as long as it is possible to specify the customer's desired contract period.

[0034] In the embodiment shown in Figure 1B, the amount of debt area 113 has a free-form input field in which the customer can enter their desired amount of debt. This allows the customer to enter their desired amount of debt in the free-form input field. However, the present invention is not limited thereto. The amount of debt area 113 may also have a pull-down menu in which the customer can selectively enter their desired amount of debt, insofar as it is possible to specify the customer's desired amount of debt. For example, the customer may select an amount that suits their desired amount from among several amounts displayed in the pull-down menu (e.g., 10,000 yen, 20,000 yen, 30,000 yen, 50,000 yen, 100,000 yen, etc.).

[0035] Customers can implement a non-accumulative type of deposit lock-up in their ordinary deposit account by entering the necessary information in the lock-up purpose area 111, the lock-up period area 112, and the lock-up amount area 113, and then selecting the lock-up start area 114. The lock-up start area 114 may change from an unselectable state to a selectable state once the necessary information in the lock-up purpose area 111, the lock-up period area 112, and the lock-up amount area 113 has been entered, or it may change from a hidden state to a visible state so that it becomes selectable once the necessary information in the lock-up purpose area 111, the lock-up period area 112, and the lock-up amount area 113 has been entered.

[0036] In this way, customers can choose to lock up their deposits in their savings accounts for the short term, rather than having them tied up and accumulated over the medium to long term. This allows customers to secure deposits in their savings accounts for the short term, according to their needs, without having to open a new account.

[0037] In the embodiments shown in Figures 1A and 1B, the display of the balance of deposits in the customer's ordinary deposit account may show either the total deposit balance in the customer's ordinary deposit account or the amount of deposits in the customer's ordinary deposit account excluding the amount that has been reserved.

[0038] 2. Configuration of a system for securing deposits in a regular savings account according to the customer's purpose. Figure 2 shows an example of the configuration of system 200 for securing deposits in a regular savings account according to the customer's purpose.

[0039] In the embodiment shown in Figure 2, the system 200 includes a computer system 210 for securing deposits in a regular savings account according to the customer's purpose, and user devices 2201-220 operated by the customer. N And, the partner's management system 2301~230 M The computer system 210 communicates with devices 2201-220 via the Internet 240. N Each of the management systems of its partners, 2301-230 MIt is configured to be able to communicate with each of them. Here, N and M are integers greater than or equal to 1.

[0040] The computer system 210 is an information processing device that performs processing to secure deposits in a customer's savings account according to the customer's purpose. The computer system 210 may be managed, for example, by a bank that manages the customer's savings account. In the embodiment shown in Figure 2, the computer system 210 comprises an interface unit 211, a processor unit 212 including one or more CPUs (Central Processing Units), and a memory unit 213. The hardware configuration of the computer system 210 is not particularly limited as long as its function can be realized, and may consist of a single machine or a combination of multiple machines.

[0041] The interface unit 211 is connected to devices 2201-220 N Controls communication with each of them, and the partner management systems 2301-230 M It controls communication with each of them.

[0042] The memory unit 213 stores the program required to execute the process and the data required to execute that program. The method by which the program is stored in the memory unit 213 is not specified. For example, the program may be pre-installed in the memory unit 213. Alternatively, the program may be installed in the memory unit 213 by being downloaded via a network such as the Internet 240, or it may be installed in the memory unit 213 via a storage medium such as an optical disc or USB.

[0043] The processor unit 212 controls the operation of the entire computer system 210. The processor unit 212 reads out the program stored in the memory unit 213 and executes the program. As a result, the computer system 210 can function as a device that executes desired steps, and the processor unit 212 of the computer system 210 can operate as a means for achieving the desired function.

[0044] In the embodiment shown in FIG. 2, the computer system 210 is connected to the database unit 250. The database unit 250 includes a customer database unit 251 and a savings account database unit 252.

[0045] The device 2201 is configured to be able to communicate with the computer system 210 via the Internet 240. The device 2201 may include an interface unit, a processor unit, a memory unit, a display unit, and an input unit. For example, the device 2201 may be a portable wireless terminal such as a mobile phone, a smartphone, or a tablet terminal, or may be a personal computer such as a laptop PC or a notebook PC. The same applies to the devices 2202 to 220 N The same applies.

[0046] The partner management system 2301 is configured to be able to communicate with the computer system 210 via the Internet 240. The partner management system 2301 is configured to be able to communicate with the computer system 210 managed by a bank that manages the customer's savings account. The partner may be a partner of the bank that manages the customer's savings account. The partner management system 2301 may have a configuration similar to that of the computer system 210, for example. The same applies to the partner management systems 2302 to 230 M The same applies.

[0047] Note that in the embodiment shown in FIG. 2, each of the devices 2201 to 220 N and the partner management systems 2301 to 230 MAlthough it has been explained that each of these can communicate with the computer system 210 via the Internet 240, the present invention is not limited thereto. Any type of network can be used instead of the Internet 240.

[0048] Furthermore, in the embodiment shown in Figure 2, the database unit 250 is located outside the computer system 210, but the present invention is not limited thereto. The database unit 250 can also be located inside the computer system 210. The configuration of the database unit 250 is not limited to a specific hardware configuration. For example, the database unit 250 may consist of a single hardware component or multiple hardware components. For example, the database unit 250 may be configured as a single external hard disk drive for the computer system 210, or as cloud storage connected via a network. Moreover, the configuration of each database unit included in the database unit 250 is also not limited to a specific hardware configuration. For example, each database unit included in the database unit 250 may also consist of a single hardware component or multiple hardware components.

[0049] Figure 3A shows an example of the structure of information stored in the customer database unit 251.

[0050] The customer database unit 251 stores information about customers. This customer information can be identified by customer identification information (customer ID). This customer information includes, for example, the customer's name, gender, date of birth, address, telephone number, email address, and savings account number.

[0051] Figure 3B shows an example of the structure of information stored in the ordinary deposit account database unit 252.

[0052] The ordinary deposit account database section 252 stores information about ordinary deposit accounts. This information can be identified by the ordinary deposit account number. Furthermore, this information is associated with the customer ID. This information includes, for example, the customer's held deposit balance, unheld deposit balance, total deposit balance, savings information, and information about non-savings accounts, all of which are identified by the customer ID.

[0053] Information regarding a customer's savings plan, identified by the customer ID, can also be identified by information identifying the purpose of the savings plan (savings purpose ID). The savings purpose ID is, for example, information for identifying the savings purpose entered in the savings purpose area 101 in Figure 1A, and can be generated by the computer system 210 to correspond to the savings purpose entered in the savings purpose area 101 when the savings start area 104 is selected by the customer. Information regarding savings plans includes, for example, the customer's target savings period, target savings amount, current savings period, current savings amount, information indicating the partner, and whether or not there were periods during which the customer could not be bound, and the length of those periods. The customer's target savings period may be, for example, the customer's desired target savings period entered in the target savings period area 102 in Figure 1A. The customer's target savings amount may be, for example, the customer's desired target savings amount entered in the target savings amount area 103 in Figure 1A. Furthermore, if, for example, the amount in the customer's savings account could not be locked up due to insufficient funds, the period during which the lock could not be locked up will be recorded as "Yes," and its length will be, for example, "1 consecutive month." If the amount in the customer's savings account could not be locked up in the following month as well, the period during which the lock could not be locked up will remain recorded as "Yes," and its length will be, for example, "2 consecutive months." If the amount in the customer's savings account could be locked up in the month following that, the period during which the lock could not be locked up will be recorded as "No."

[0054] Information regarding a customer's non-sustainable bondage, identified by the customer ID, can be identified by information for identifying non-sustainable purposes other than savings purposes (non-sustainable purpose ID). The non-sustainable purpose ID is, for example, information for identifying a non-sustainable bondage purpose entered in the bondage purpose area 111 in Figure 1B, and can be generated by the computer system 210 to correspond to the bondage purpose entered in the bondage purpose area 111 when the bondage start area 114 is selected by the customer. Information regarding non-sustainable bondage includes, for example, the period for which the customer should be bound in a non-sustainable bondage, the amount to which the customer should be bound in a non-sustainable bondage, etc. The period for which the customer should be bound in a non-sustainable bondage may be, for example, the customer's desired bondage period entered in the bondage period area 112 in Figure 1B. The amount to which the customer should be bound in a non-sustainable bondage may be, for example, the customer's desired bondage amount entered in the bondage amount area 113 in Figure 1B.

[0055] 3. Processes executed in a computer system Figure 4 shows an example of processing performed in the computer system 210. Each step shown in Figure 4 is performed, for example, by the processor unit 212 of the computer system 210. The steps shown in Figure 4 will be described below.

[0056] Step S401: A restraining request is received relating to the restraining of at least a portion of the amount in the customer's savings account. The restraining request includes at least information indicating the customer's purpose. The restraining request may further include information for identifying the customer. The restraining request is received, for example, from a user device 2201 operated by the customer.

[0057] A binding request may be a deposit request that requests a deposit to be made in the customer's savings account. In this case, the customer's objective is the customer's deposit objective, which is the customer's desired deposit objective entered in the deposit objective area 101, for example, as described with reference to Figure 1A.

[0058] Alternatively, the binding request may be a non-deposit binding request, which requests that the deposit in the customer's ordinary savings account be bound in a non-deposit manner. In this case, the customer's objective is the objective of non-deposit binding, which is the customer's desired binding objective entered in the binding objective area 111, for example, as described with reference to Figure 1B.

[0059] Step S402: At least a portion of the amount in the customer's savings account is associated with and reserved for the customer's purpose. The amount of the customer's savings account is associated with and reserved for the customer's purpose.

[0060] When the computer system 210 receives a transfer request requesting the removal of at least a portion of a reserved amount in the customer's savings account, it is configured to respond to the receipt of the transfer request by performing a process to notify the customer that the removal of the reserved amount will be refused. The transfer request is received, for example, from a user device 2201 operated by the customer. The process to notify the customer that the removal of the reserved amount will be refused includes, for example, sending a notice to the user device 2201 that the removal of the reserved amount will be refused.

[0061] Figure 5 shows an example of processing performed in the computer system 210. Specifically, Figure 5 shows an example of processing when the computer system 210 receives a deposit request in step S401 of Figure 4, which requests that a deposit be made in the customer's ordinary deposit account. Each step shown in Figure 5 is performed, for example, by the processor unit 212 of the computer system 210. The steps shown in Figure 5 will be described below.

[0062] Step S501: A deposit request is received requesting that a deposit be made in the customer's savings account. The deposit request includes at least information indicating the customer's purpose of deposit, information indicating the customer's desired deposit amount, and information indicating the customer's desired deposit period. The information indicating the customer's purpose of deposit may correspond to information entered in the deposit purpose area 101 of Figure 1A, the information indicating the customer's desired deposit period may correspond to information entered in the target deposit period area 102 of Figure 1A, and the information indicating the customer's desired deposit amount may correspond to information entered in the target deposit amount area 103 of Figure 1A. The deposit request may further include information for identifying the customer. The deposit request is received, for example, from a user device 2201 operated by the customer.

[0063] Step S502: At least a portion of the amount in the customer's savings account is associated with and reserved for the customer's savings purpose. This initiates savings in the customer's savings account. This process is repeated for the customer's desired savings period to carry out savings in the customer's savings account. The computer system 210 may automatically calculate, for example, the amount of at least a portion of the amount reserved in the customer's savings account based on the customer's desired target savings period and desired target savings amount. At least a portion of the amount in the customer's savings account is associated with and reserved for the customer's savings purpose, for example, at predetermined intervals (i.e., the computer system 210 is configured to repeatedly associate and reserve at least a portion of the unreserved amount in the customer's savings account with the customer's savings purpose (for example, at predetermined intervals)). For example, the amount of at least a portion of the amount reserved in the customer's savings account at predetermined intervals may be calculated by (desired target savings amount) ÷ (number of months in the desired target savings period). As described above, the reserved portion of the amount in the customer's savings account is configured so that it cannot be moved, either directly or indirectly.

[0064] Step S503: It is determined whether the desired target savings period has elapsed. This process may be performed, for example, by referring to the ordinary deposit account database unit 252. This desired target savings period is associated with the customer's savings purpose received in step S501. If the result is "Yes", the process proceeds to step S506; if the result is "No", the process proceeds to step S504.

[0065] Step S504: It is determined whether the total of at least a portion of the amounts held in relation to the customer's savings purpose has reached the desired target savings amount. This process may be performed, for example, by referring to the ordinary deposit account database unit 252. This desired target savings amount is associated with the customer's savings purpose received in step S501. If the result of the determination is "Yes", the process proceeds to step S506; if the result of the determination is "No", the process proceeds to step S505.

[0066] Step S505: It is determined whether a predetermined period has elapsed. The predetermined period may be, for example, the period from the most recent lock-up process, or the period from a predetermined date. The predetermined period is shorter than the desired deposit period. If the result of the determination is "Yes", the process returns to step S502, and at least another portion of the unlocked amount in the customer's savings account is locked up in association with the customer's deposit purpose. If the result of the determination is "No", the process returns to step S505.

[0067] Step S506: The amount that was held in the customer's savings account in connection with the customer's savings purpose, as received in Step S501, is released. This makes the released amount freely available for withdrawal, transfer, transaction, and movement.

[0068] The computer system 210 is configured to further associate the customer's deposit purpose received in step S501 with one of several affiliates of the bank managing the computer system 210. This process includes, for example, storing information indicating one of the multiple affiliates in the ordinary deposit account database section 252, associated with the deposit purpose ID. This makes it possible to identify the affiliate corresponding to the customer's deposit purpose. This process can be performed, for example, at any time after step S502 and before step S505 in Figure 5.

[0069] Step S507: A grant request is sent to one of the partner management systems associated with the customer's savings objective received in Step S501, requesting that the customer be granted a reward corresponding to the customer's desired savings amount. This process is executed in Step S503 when the customer's desired savings period has elapsed, or when it is determined in Step S504 that the total of at least a portion of the amounts bound in relation to the customer's savings objective has reached the customer's desired savings amount. The grant request may be sent, for example, to a partner management system 2301. This allows the partner management system 2301 to grant the customer a reward corresponding to the customer's desired savings amount. The reward may be, but is not limited to, points, coupons, or free gifts.

[0070] Steps S502, S504-S505 in Figure 5 are performed during the customer's desired target savings period.

[0071] Furthermore, the computer system 210 can receive an additional hold request that requests the customer to additionally hold at least a portion of the remaining amount (of the unheld amount) in their savings account for the customer's desired deposit period. In this case, the computer system 210 is configured to respond to the receipt of the additional hold request by associating the remaining amount with the customer's deposit purpose and holding the remaining amount. The additional hold request can be received, for example, at any time after step S502 and up to step S505 in Figure 5. In this case, the predetermined period in step S505 may be, for example, the period since the processing to additionally hold at least a portion of the remaining amount was performed.

[0072] Furthermore, after performing the process of additionally holding at least another portion of the amount, the computer system 210 may determine whether, as a result of additionally holding at least another portion of the amount, the total of at least another portion of the amount held in relation to the customer's savings purpose has reached the desired target savings amount. If the determination result is "Yes", the process proceeds to step S506 at this point; if the determination result is "No", the process proceeds to step S505.

[0073] Furthermore, although the embodiment shown in Figure 5 describes an example in which step S507 is performed after step S506, the present invention is not limited thereto. Step S507 may be performed before step S506.

[0074] Furthermore, the computer system 210 may transfer the amount released in step S506 to the account of the partner's management system 2301 and perform processing to grant the customer a benefit corresponding to the released amount (for example, a benefit equivalent to the released amount + α). This allows the customer to receive a benefit from the partner corresponding to the amount they have accumulated.

[0075] Figure 6 shows another example of processing performed in the computer system 210. Specifically, Figure 6 shows an example of processing when the computer system 210 receives a non-reserve hold request in step S401 of Figure 4, which requests that a deposit be reserved in a customer's ordinary savings account. Each step shown in Figure 6 is performed, for example, by the processor unit 212 of the computer system 210. The steps shown in Figure 6 will now be described.

[0076] Step S601: A non-deposit detention request is received, requesting that at least a portion of the amount in the customer's savings account be detained in a non-deposit detention manner. The non-deposit detention request includes at least information indicating the customer's purpose for non-deposit detention, information indicating the customer's desired non-deposit detention amount, and information indicating the customer's desired non-deposit detention period. The information indicating the customer's purpose for non-deposit detention may correspond to information entered in the detention purpose area 111 of Figure 1B, the information indicating the customer's desired non-deposit detention period may correspond to information entered in the detention period area 112 of Figure 1B, and the information indicating the customer's desired non-deposit detention amount may correspond to information entered in the detention amount area 113 of Figure 1B. The non-deposit detention request may further include information for identifying the customer. The non-deposit detention request is received, for example, from a user device 2201 operated by the customer.

[0077] Step S602: At least a portion of the amount in the customer's savings account is associated with and held for the customer's non-refundable holding purpose. As described above, at least a portion of the held amount in the customer's savings account is configured so that it cannot be moved, either directly or indirectly.

[0078] Step S603: It is determined whether the desired non-accumulating commitment period has elapsed. This desired non-accumulating commitment period is associated with the customer's non-accumulating commitment purpose received in step S601. If the determination result is "Yes", the process proceeds to step S604; if the determination result is "No", the process returns to step S603.

[0079] Step S604: The amount that was held in the customer's savings account in connection with the customer's non-refundable holding purpose, received in Step S601, is released. This makes the released amount freely available for withdrawal, transfer, transaction, and movement.

[0080] As described above, the present invention has been illustrated using preferred embodiments, but the present invention should not be construed as being limited to these embodiments. It should be understood that the scope of the present invention should be interpreted solely by the claims. Those skilled in the art will understand that, based on the description of the specific preferred embodiments of the present invention and common technical knowledge, an equivalent scope can be implemented. [Industrial applicability]

[0081] The present invention is useful as it provides a computer system and programs, etc., for securing deposits in a regular savings account according to the customer's purpose without requiring the opening of a new account. [Explanation of symbols]

[0082] 200 Systems 210 Computer Systems 2201~220 N User device 2301~230 M Partner's management system 240 Internet 250 Database Department

Claims

1. A computer system for securing deposits in a regular savings account according to the customer's purpose, wherein the computer system is Receiving a restraining request relating to the restraining of at least a portion of the amount in the customer's ordinary deposit account, wherein the restraining request includes information indicating the customer's purpose, In response to the aforementioned request for restraint, the customer shall associate at least a portion of the amount in the customer's ordinary deposit account with the customer's aforementioned purpose and restrain at least a portion of the amount. A computer system configured to perform at least the following:

2. The computer system according to claim 1, wherein at least a portion of the amount of money held in the customer's ordinary deposit account is configured to be unable to be moved, either directly or indirectly.

3. The computer system according to claim 2, wherein the computer system is configured to perform a process to notify the customer that the transfer of at least a portion of the reserved amount in the customer's savings account is to be refused, in response to receiving a transfer request from the customer.

4. The binding request includes a deposit request that requests the customer to deposit funds into their ordinary savings account, the customer's purpose includes the customer's deposit purpose, and the deposit request includes at least information indicating the customer's deposit purpose, information indicating the customer's desired deposit amount, and information indicating the customer's desired deposit period. The computer system according to claim 1, wherein associating at least a portion of the amount in the customer's savings account with the customer's purpose and restricting at least a portion of the amount includes associating at least a portion of the amount in the customer's savings account with the customer's savings purpose and restricting at least a portion of the amount during the customer's desired savings period.

5. Associating at least a portion of the amount in the customer's ordinary deposit account with the customer's savings purpose and restricting that at least portion of the amount during the customer's desired savings period includes, at predetermined intervals during the customer's desired savings period, associating at least a portion of the amount in the customer's ordinary deposit account with the customer's savings purpose and restricting that at least portion of the amount. The computer system according to claim 4, wherein the predetermined period is shorter than the desired accumulation period.

6. During the aforementioned customer's desired deposit period, Receiving an additional restraint request that additionally requests the restraint of at least another amount in the customer's ordinary deposit account, In response to receiving the aforementioned additional restraint request, the other at least portion of the amount shall be associated with the customer's savings purpose and restrained. The computer system according to claim 4, configured to further perform the following:

7. The computer system according to claim 1, further configured to associate the customer's savings purpose with one of several partners of the bank managing the computer system.

8. The aforementioned computer system is configured to be able to communicate with the management system of one of the partner companies. The computer system according to claim 7, further configured to transmit a grant request to the management system of one partner requesting that a benefit corresponding to the customer's desired deposit amount be granted to the customer when the customer's desired deposit period has elapsed or when the total of at least a portion of the amounts bound in relation to the customer's deposit purpose reaches the customer's desired deposit amount.

9. The computer system according to claim 1, further configured to release the restraint on at least a portion of the amount when the customer's desired savings period has elapsed and the total of at least a portion of the amount restrained in relation to the customer's savings purpose has reached the customer's desired savings amount.

10. A program executed in a computer system for securing deposits in a regular savings account according to the customer's purpose, wherein the computer system comprises a processor unit, When the aforementioned program is executed by the processor unit, Receiving a restraining request relating to the restraining of at least a portion of the amount in the customer's ordinary deposit account, wherein the restraining request includes information indicating the customer's purpose, In response to the aforementioned request for restraint, the customer shall associate at least a portion of the amount in the customer's ordinary deposit account with the customer's aforementioned purpose and restrain at least a portion of the amount. A program configured to cause the processor unit to perform at least the above.

Images