Management device, management method, and management program

Abstract

A management device, a management method, and a management program are provided that promote the use of electronic payment services that support digital salary payments. [Solution] In a management system having a payment source server and a payment server, the payment server 10, which is a management device, has an acquisition unit that acquires user information about users who use a specified payment method, a deposit acceptance unit that accepts digital money deposits for users, and a funds transfer unit that transfers a portion of the digital money deposited as salary from the digital money deposited as salary accepted by the deposit acceptance unit to the reserved balance of the payment account into which the digital money as salary was deposited, based on the user information acquired by the acquisition unit.

Description

Technical Field

[0001] The present invention relates to a management device, a management method, and a management program.

Background Art

[0002] Conventionally, electronic payment services that use digital money such as electronic money and virtual currency have been known. For example, as a type of electronic payment service, a method of performing payment by displaying or reading a two-dimensional code or the like using a terminal device carried by a user (for example, smartphone payment) is known.

[0003] In such electronic payment services, in recent years, "digital payment of salary" that accepts payment of salary by digital money has been proposed.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In the above prior art, there is room for further improvement in promoting the use of electronic payment services corresponding to digital payment of salary.

[0006] The present application has been made in view of the above, and an object thereof is to provide a management device, a management method, and a management program that can promote the use of an electronic payment service corresponding to digital payment of salary.

Means for Solving the Problems

[0007] The management device according to this application comprises an acquisition unit and a deposit acceptance unit. The acquisition unit acquires user information relating to users who use a predetermined payment method. The deposit acceptance unit accepts digital money deposits from users. The fund transfer unit transfers a portion of the digital money received as salary from the deposit acceptance unit to the reserved balance of the settlement account into which the digital money was deposited as salary, based on the user information acquired by the acquisition unit. [Effects of the Invention]

[0008] According to one embodiment of the system, it has the effect of promoting the use of electronic payment services that support digital salary payments. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 shows an example of the management process according to the first embodiment. [Figure 2] Figure 2 shows an example of electronic payment processing according to the first embodiment. [Figure 3] Figure 3 shows an example of the configuration of a payment server according to the first embodiment. [Figure 4] Figure 4 shows an example of an account database according to the first embodiment. [Figure 5] Figure 5 shows an example of a payment request according to the first embodiment. [Figure 6] Figure 6 shows an example of a withdrawal request according to the first embodiment. [Figure 7] Figure 7 shows an example of the screen of a user terminal according to the first embodiment. [Figure 8] Figure 8 is a flowchart showing an example of the procedure for payment processing among the management processes according to the first embodiment. [Figure 9] Figure 9 is a flowchart showing an example of the withdrawal process procedure among the management processes according to the first embodiment. [Figure 10] Figure 10 shows an example of the management process according to the second embodiment. [Figure 11] FIG. 11 is a diagram showing a configuration example of a settlement server according to the second embodiment. [Figure 12] FIG. 12 is a diagram showing an example of an account database according to the second embodiment. [Figure 13] FIG. 13 is a diagram showing an example of a history database according to the second embodiment. [Figure 14] FIG. 14 is a diagram showing an example of a registration information database according to the second embodiment. [Figure 15] FIG. 15 is a diagram showing an example of a claim information database according to the second embodiment. [Figure 16] FIG. 16 is a diagram showing an example of a screen of a user terminal according to the second embodiment. [Figure 17] FIG. 17 is a flowchart showing an example of a procedure for registering sorting information in the management process according to the second embodiment. [Figure 18] FIG. 18 is a flowchart showing an example of a procedure for fund transfer processing in the management process according to the second embodiment. [Figure 19] FIG. 19 is a flowchart showing an example of a procedure for settlement processing in the management process according to the second embodiment. [Figure 20] FIG. 20 is a hardware configuration diagram showing an example of a computer that realizes the functions of the settlement server.

BEST MODE FOR CARRYING OUT THE INVENTION

[0010] Hereinafter, embodiments for implementing the management device, management method, and management program according to the present application (hereinafter referred to as "embodiments") will be described in detail with reference to the drawings. Note that the management device, management method, and management program according to the present application are not limited by this embodiment. Also, in the following embodiments, the same parts are denoted by the same reference numerals, and redundant explanations are omitted.

[0011] 〔1. First Embodiment〕 〔1-1. Regarding the management process〕 Using FIG. 1, the management process realized by the management device and the like of the first embodiment will be described. FIG. 1 is a diagram showing an example of the management process according to the first embodiment. In FIG. 1, it is assumed that the settlement server 10, which is an example of the management device according to the first embodiment, realizes the management process and the like according to the embodiment.

[0012] As shown in FIG. 1, the management system 1 according to the first embodiment includes a settlement server 10, a user terminal 100, a payer server 400, a bank server 600, and an ATM (Automatic Teller Machine) 800.

[0013] The settlement server 10, the user terminal 100, the payer server 400, and the bank server 600 are connected to each other so as to be able to communicate with each other by wire or wirelessly via a network N (for example, see FIG. 3). The network N is, for example, a WAN (Wide Area Network) such as the Internet. Note that the management system 1 shown in FIG. 1 may include a plurality of settlement servers 10, a plurality of user terminals 100, a plurality of payer servers 400, a plurality of bank servers 600, and a plurality of ATMs 800.

[0014] The settlement server 10 is an information processing device that executes the management process according to the first embodiment, and is realized by a server device, a cloud system, or the like. For example, the settlement server 10 provides an electronic payment service related to electronic payment performed by displaying or reading a predetermined code using the user terminal 100. For example, the settlement server 10 manages the settlement accounts of digital money owned by the provider of the transaction target or the user provided by the transaction target, and realizes various settlements by moving digital money between settlement accounts according to the settlement information from the user. Note that the digital money may be, for example, points or currencies independently used by various companies, or may be a currency provided by a country such as the Japanese yen or the US dollar that enables electronic transactions. The processing content of the electronic payment service performed via the settlement server 10 will be described later.

[0015] The user terminal 100 is an information processing device used by the user. The user terminal 100 can be implemented as, for example, a smartphone, a tablet device, a notebook PC (Personal Computer), a desktop PC, a mobile phone, or a PDA (Personal Digital Assistant). Figure 1 shows an example where the user terminal 100 is a smartphone.

[0016] The payment source server 400 is an information processing device used by businesses that pay salaries to users, and is implemented by server devices, cloud systems, etc. For example, the payment source server 400 is a server device belonging to the company that employs the users (hereinafter referred to as the "payer"). Note that the business that acts as the payer is not limited to companies (corporations, legal entities, etc.), but may also be the national government, prefectures, municipalities, or other local governments.

[0017] The user terminal 100 and the payment source server 400 display the information distributed by the payment server 10 using a web browser or application.

[0018] Furthermore, when the user terminal 100 and the payment source server 400 receive control information from the settlement server 10 to perform predetermined information processing, they perform the information processing according to the control information. Here, the control information is written in, for example, a scripting language such as JavaScript (registered trademark), a stylesheet language such as CSS (Cascading Style Sheets), a programming language such as Java (registered trademark), or a markup language such as HTML (HyperText Markup Language). Alternatively, the predetermined application itself distributed from the settlement server 10 may be considered as the control information.

[0019] The bank server 600 is an information processing device belonging to a bank that manages users' bank accounts, and is implemented using server equipment or a cloud system. For example, the bank server 600 manages information such as the usage history of bank accounts, including information on withdrawals from bank accounts by each card company and various service providers (such as the amount withdrawn and the date and time of withdrawal), and current account information (such as the account balance), in association with the user.

[0020] Furthermore, the bank server 600 is connected to the ATM 800 via a network such as the internet, either by wired or wireless means, enabling communication between them. The ATM 800 dispenses cash according to the user's instructions.

[0021] The payer, who is the user's employer, pays the user a salary on a regular basis (for example, once a month). The management system 1 according to the first embodiment supports so-called "digital salary payments," where the salary is paid using digital money.

[0022] First, the settlement server 10 receives a payment request from the payment source server 400 (step S1). The payment request includes the identification information of the user (payee) receiving the digital money payment (payee identification information, hereinafter referred to as "payee ID"), the payment amount, and the purpose of the payment. Figure 1 shows an example of a payment request that includes payee ID "U1", payment amount "300,000 yen", and purpose "salary".

[0023] The payee ID "U1" is the identification information of user U1 (user identification information, hereinafter referred to as "user ID"). The user ID can be any information that can identify user U1, and may include numbers, letters, symbols, or combinations thereof, as well as, for example, a telephone number and email address, or a combination of a telephone number and email address and a name. The name may be written in kanji, hiragana, katakana, or the alphabet. In addition, the payment request may include identification information that identifies the payer (payer identification information, hereinafter referred to as "payer ID").

[0024] Next, the payment server 10 determines whether the item included in the payment request is salary. If the item included in the payment request is salary, the payment server 10 processes the payment for the salary balance among the total balances associated with the user ID included in that payment request.

[0025] For example, the settlement server 10 stores account information that associates the "Owner ID" field, the "Total Balance" field, and the "Breakdown" field. The "Owner ID" field stores identification information (owner identification information, hereinafter referred to as "Owner ID") that identifies the owner who owns the digital money account (settlement account). Here, an example is shown where the "Owner ID" field stores the user ID "U1" that identifies user U1, but the "Owner ID" field may also store the payer ID, identification information that identifies the provider that provides the transaction target (provider identification information, hereinafter referred to as "provider ID"), etc. The "Total Balance" field stores information that shows the total balance of digital money owned by the owner identified by the Owner ID.

[0026] The "Breakdown" field stores information showing the breakdown of the total balance stored in the "Total Balance" field. Specifically, the "Breakdown" field includes the "Salary" field and the "Other" field. The "Salary" field stores information showing the balance of digital money received as salary from the total balance stored in the "Total Balance" field. The "Other" field stores information showing the balance of digital money received under names other than salary from the total balance stored in the "Total Balance" field.

[0027] For example, Figure 1 shows an example of account information, including user ID "U1", total balance "1,000,000 yen", salary "700,000 yen", and other income "300,000 yen". In this case, when the payment request shown in Figure 1 is received, the settlement server 10 changes the "total balance" item associated with user ID "U1" from "1,000,000 yen" to "1,300,000 yen". The settlement server 10 also changes the "salary" item associated with user ID "U1" from "700,000 yen" to "1,000,000 yen" (step S2). The "other income" item remains unchanged.

[0028] On the other hand, if the settlement server 10 receives a payment request that includes items other than salary, it changes the "total balance" item and the "other than salary" item in the corresponding account information. In this case, the "salary" item is not changed. The "other than salary" item may be subdivided into multiple items. That is, there may be multiple items other than salary, and in this case, the "other than salary" item may be subdivided to correspond to the multiple items.

[0029] Thus, in the management system 1 according to the first embodiment, at least the salary balance is managed separately from the total balance of digital money. As a result, for example, the settlement server 10 can display balance information showing the total balance (for example, total balance "1,300,000 yen") on the user terminal 100 of user U1, by separating it into salary balance information showing the salary balance (for example, total balance "1,000,000 yen") and non-salary balance information showing the balance other than salary (for example, total balance "300,000 yen") (step S3).

[0030] Therefore, according to the management system 1 of the first embodiment, when digital salary payments are made, the balance including salary can be properly managed.

[0031] Incidentally, in digital salary payments, user convenience can be ensured by making it possible to convert the digital money paid as salary into cash. Specifically, it is necessary to allow users to withdraw the digital money paid as salary from an ATM. Therefore, the management system 1 according to the first embodiment is configured to allow users to withdraw the digital money paid as salary from an ATM 800.

[0032] For example, ATM 800 sends a withdrawal request including the user ID and withdrawal amount to the bank server 600 in accordance with the operation performed by user U1 (step S4). The operation performed by user U1 on ATM 800 may be, for example, an input operation on the ATM 800's touch panel or physical buttons, or an operation in which the ATM 800 reads a QR code (registered trademark) displayed on the user terminal 100. The information entered into ATM 800 should include at least the user ID and the withdrawal amount.

[0033] Next, the bank server 600 sends the withdrawal request received from the ATM 800 to the settlement server 10 (step S5).

[0034] Next, the settlement server 10 modifies the "salary" item in the corresponding balance information based on the withdrawal request received from the bank server 600. For example, suppose the withdrawal request includes user ID "U1" and withdrawal amount "100,000 yen". In this case, the settlement server 10 changes the "total balance" item associated with user ID "U1" from "1,300,000 yen" to "1,200,000 yen", and also changes the "salary" item from "1,000,000 yen" to "900,000 yen" (step S6).

[0035] Next, the payment server 10 sends a withdrawal instruction, including the user ID and the withdrawal amount, to the bank server 600 (step S7). Upon receiving the withdrawal instruction, the bank server 600 debits the withdrawal amount from the bank account of the business operator to which the payment server 10 belongs, i.e., the company providing the electronic payment service (step S8). This process may be performed at the time the payment server 10 receives the withdrawal instruction, or it may be performed at a predetermined time, for example, once a month.

[0036] The bank server 600 also sends a withdrawal instruction, including the withdrawal amount, to the ATM 800 (step S9). The ATM 800 then dispenses cash equal to the withdrawal amount included in the withdrawal instruction (step S10).

[0037] Thus, in the management system 1 according to the first embodiment, user U1 can withdraw the portion of their total digital money balance corresponding to their salary balance as cash from the ATM 800.

[0038] The above-mentioned mechanism for cashing out digital money applies to digital money paid as salary, and does not apply to digital money paid under other names. Allowing digital money paid under other names to be cashed out could raise concerns, for example, that it could become a breeding ground for money laundering. For this reason, the payment server 10 may prohibit withdrawals of non-salary balances from ATM 800. However, if non-salary balances are subdivided into multiple categories, withdrawals of any of these subdivided categories may be permitted from ATM 800.

[0039] [1-2. Regarding payment using user terminal 100] Next, an example of payment (electronic payment) using the user terminal 100 will be explained with reference to Figure 2. Figure 2 is a diagram showing an example of electronic payment processing according to the first embodiment. In the management system 1, both the salary balance and the non-salary balance from the total balance of the digital money described above can be used for electronic payment.

[0040] As shown in Figure 2, the management system 1 may further include a provider terminal 200. The provider terminal 200 is an information processing device used by a provider that provides transaction items to a user. The provider terminal 200 can be implemented as, for example, a POS (Point of Sales) terminal, a smartphone, a tablet terminal, a notebook PC, a desktop PC, a mobile phone, a PDA, etc. The provider terminal 200 also displays information distributed by the payment server 10 using a web browser or application. Figure 2 shows an example where the provider terminal 200 is a POS terminal.

[0041] The following description describes an example in which user U1 makes a payment using user terminal 100 with a two-dimensional code (QR code®) placed in store A, which displays identification information (hereinafter referred to as "store code") C1 that identifies store A. However, the first embodiment is not limited to this. The payment example described below can also be applied when any user makes a payment at any store using any user terminal 100. Furthermore, store code C1 may be a barcode, a predetermined mark, a number, etc. (i.e., a predetermined code), not just a QR code®.

[0042] For example, when user U1 makes a payment for the use or purchase of various goods and services at store A, user U1 launches a payment application pre-installed on user terminal 100. Then, user U1 photographs and reads the store code C1 installed at store A via the payment application (step S11). In this case, user terminal 100 displays a screen for entering the price of the payment item and accepts the payment amount from user U1 or a store employee at store A. Then, user terminal 100 transmits payment information to payment server 10, including the user ID that identifies user U1, the store code C1 (or the information indicated by the store code C1, i.e., information indicating store A (for example, the provider ID)), and the payment amount.

[0043] When the payment server 10 receives payment information from the user terminal 100 (step S12), it transfers the amount of digital money indicated by the payment amount from the payment account of user U1, indicated by the user ID, to the payment account of store A, indicated by the store code C1 (step S13). The payment server 10 then sends a notification to the user terminal 100 that the payment has been completed (step S14). In this case, the user terminal 100 notifies the user that the payment has been completed by displaying a screen or outputting a predetermined sound indicating that the payment has been completed.

[0044] It should be noted that payment using the user terminal 100 is not limited to the process described above. For example, payment using the user terminal 100 may also be made using the provider terminal 200 installed at store A. For example, the user terminal 100 displays a user ID on its screen to identify user U1. In such a case, the provider terminal 200 installed at store A reads the user ID displayed on the user terminal 100 and sends payment information indicating the user ID, the payment amount, and information identifying store A to the payment server 10. In such a case, the payment server 10 moves the amount of digital money indicated by the payment amount from the payment account of user U1 indicated by the user ID to the payment account of store A, and may notify the provider terminal 200 or user terminal 100 at store A that the payment has been completed by displaying a screen or outputting a predetermined sound indicating that the payment has been completed.

[0045] Furthermore, payment using the user terminal 100 may involve not only the transfer of digital money from a payment account pre-charged by user U1 to store A's payment account, but also, for example, payment using a credit card pre-registered by user U1. In such a case, for example, the user terminal 100 may transfer the payment amount in digital money to store A's payment account and simultaneously bill the user U1's credit card company (card company) for the payment amount.

[0046] Furthermore, payments made using the user terminal 100 are not limited to payments made at physical stores; for example, payments made for transactions in e-commerce services (i.e., online payments). In such cases, for example, the user terminal 100 transmits payment information to the payment server 10, including a user ID that identifies user U1, a provider ID, and the price of the transaction (payment amount). The payment server 10 then transfers the amount of digital money indicated by the payment amount from the user U1's payment account, indicated by the user ID, to the provider's payment account, indicated by the provider ID, and notifies the user terminal 100 that the payment has been completed by displaying a screen or outputting a predetermined sound indicating that the payment has been completed.

[0047] [2. Configuration of the payment server] Next, the configuration of the payment server 10 will be described using Figure 3. Figure 3 is a diagram showing an example of the configuration of the payment server 10 according to the first embodiment. As shown in Figure 3, the payment server 10 has a communication unit 20, a storage unit 30, and a control unit 40.

[0048] (Regarding Communications Section 20) The communication unit 20 is implemented, for example, by a NIC (Network Interface Card). The communication unit 20 is connected to the network N by wire or wireless connection and transmits and receives information with the user terminal 100, the provider terminal 200, the payment source server 400, the bank server 600, etc.

[0049] (Regarding memory unit 30) The storage unit 30 is implemented by, for example, semiconductor memory elements such as RAM (Random Access Memory) and flash memory, or by storage devices such as hard disks and optical discs. As shown in Figure 4, the storage unit 30 has an account database 31.

[0050] (Regarding account database 31) The account database 31 stores various information (an example of the balance information described above) regarding accounts (settlement accounts) owned by users, payers, providers, etc., in the electronic payment service. Here, an example of the information stored in the account database 31 will be explained using Figure 4. Figure 4 is a diagram showing an example of an account database according to the first embodiment. In the example in Figure 4, the account database 31 has items such as "account ID", "owner ID", "total balance", and "breakdown".

[0051] The "Account ID" field stores identification information (account identification information, hereinafter referred to as "Account ID") to identify the settlement account. The "Owner ID" field stores identification information to identify the owner of the settlement account linked to the Account ID. For example, in the example shown in Figure 4, the "Owner ID" field stores the user ID "U1" of user U1, the payer ID "E1" of the payer who pays the salary, the provider ID "P1" of the provider that provides the transaction items, etc.

[0052] The "Total Balance" field stores information showing the total balance of the settlement account. The "Breakdown" field stores information showing the breakdown of the total balance. Specifically, the "Breakdown" field includes the "Salary" field and the "Non-Salary" field, with the "Non-Salary" field being further subdivided into, for example, the "Regular" field and the "Profit" field.

[0053] The "Salary" field stores information indicating the balance of digital money received as salary, out of the total balance stored in the "Total Balance" field. The "Other" field stores information indicating the balance of digital money received under names other than salary, out of the total balance stored in the "Total Balance" field.

[0054] Furthermore, within the "Other than Salary" category, the "Regular" item stores information indicating the balance of digital money that the settlement account holder has charged themselves. For example, the "Regular" item stores information indicating the balance of digital money deposited from a credit card or bank account linked to the settlement account. The "Profit" item stores information indicating, for example, the balance of digital money that has been cashed back on the payment amount when using the electronic payment service provided by Management System 1.

[0055] (Regarding the control unit 40) The control unit 40 is a controller, and is realized, for example, by a CPU (Central Processing Unit) or MPU (Micro Processing Unit) executing various programs stored in the storage device inside the payment server 10 using RAM as a working area. Alternatively, the control unit 40 is a controller, and is realized, for example, by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array). As shown in Figure 3, the control unit 40 according to the first embodiment has a reception unit 41, a deposit processing unit 42, a withdrawal processing unit 43, and a display control unit 44, and realizes or executes the information processing functions and operations described below.

[0056] (Regarding Reception Desk 41) The reception unit 41 receives digital money deposit requests. An example of the information included in a deposit request will be explained with reference to Figure 5. Figure 5 is a diagram showing an example of a deposit request according to the first embodiment.

[0057] As shown in Figure 5, a payment request includes information such as "Payer ID," "Recipient ID," "Amount to be paid," and "Description." The "Payer ID" is the identification information of the payer who sent the payment request, and the "Recipient ID" is the identification information of the recipient. The "Amount to be paid" is information indicating the amount of digital money to be paid, and the "Description" is information indicating the purpose of the payment. The payment request shown in Figure 5 indicates that "300,000 yen" will be paid as salary from the employer of user U1, identified by the payer ID "E1," to user U1, identified by the recipient ID "U1."

[0058] Furthermore, the reception unit 41 receives requests to withdraw digital money to the ATM 800. An example of the information included in a withdrawal request will be explained with reference to Figure 6. Figure 6 is a diagram showing an example of a withdrawal request according to the first embodiment.

[0059] As shown in Figure 6, a withdrawal request includes information such as "Bank ID," "Source ID," "Withdrawal Amount," and "Destination." The "Bank ID" is the identification information of the bank that sent the withdrawal request, and the "Source ID" is the identification information of the user making the withdrawal. The "Withdrawal Amount" is information indicating the amount to be withdrawn, and the "Destination" is information indicating the destination (where the money will be withdrawn). The withdrawal request shown in Figure 6 was sent from Bank ID "B1" and indicates that a user with Source ID "U1" (i.e., user U1) will withdraw 100,000 yen from an ATM.

[0060] The reception unit 41 may receive payment information related to the settlement of transactions in the e-commerce service. For example, the reception unit 41 receives payment information from the user terminal 100 that includes a user ID to identify the user, a provider ID to identify the provider that provides the transaction item, and the price (payment amount) of the transaction item.

[0061] Furthermore, the reception unit 41 may receive payment information from the provider terminal 200 installed in the store. For example, the reception unit 41 receives payment information that includes the user ID read by the provider terminal 200, the user ID displayed on the user terminal 100, the payment amount, and information identifying the store.

[0062] Furthermore, the reception unit 41 may receive a request from the user terminal 100 to confirm the total balance of digital money. In this case, the confirmation request only needs to include the user ID.

[0063] (Regarding deposit processing section 42) The deposit processing unit 42 performs deposit processing on the account database 31 based on the deposit request received by the reception unit 41.

[0064] Specifically, the deposit processing unit 42 transfers digital money equivalent to the deposit amount included in the deposit request from the settlement account linked to the payer ID included in the deposit request to the settlement account linked to the payee ID included in the deposit request. In other words, the deposit processing unit 42 subtracts the deposit amount from the total balance of the settlement account linked to the payer ID and adds the deposit amount to the total balance of the settlement account linked to the payee ID.

[0065] Furthermore, the deposit processing unit 42 determines whether the item included in the deposit request is "salary". If the item included in the deposit request is "salary", the deposit processing unit 42 adds the deposit amount to the "salary" item in the total balance of the settlement account linked to the payee ID.

[0066] On the other hand, if the item name included in the payment request is "other than salary," the payment processing unit 42 adds the payment amount to the "other than salary" item in the total balance of the settlement account linked to the payee ID. For example, if the item name included in the payment request is "regular," the payment processing unit 42 adds the payment amount to the "regular" item in the total balance of the settlement account linked to the payee ID. Also, if the item name included in the payment request is "profit," the payment processing unit 42 adds the payment amount to the "profit" item in the total balance of the settlement account linked to the payee ID.

[0067] (Regarding withdrawal processing unit 43) The withdrawal processing unit 43 performs withdrawal processing on the account database 31 based on the withdrawal request received by the reception unit 41.

[0068] Specifically, the withdrawal processing unit 43 deducts the digital money equivalent to the withdrawal amount included in the withdrawal request from the settlement account linked to the withdrawal source ID included in the withdrawal request. Then, the withdrawal processing unit 43 sends a withdrawal instruction to the bank server 600 of the bank ID included in the withdrawal request via the communication unit 20 and network N. The withdrawal instruction may include information such as the withdrawal source ID and the withdrawal amount.

[0069] Furthermore, the withdrawal processing unit 43 determines whether the withdrawal destination included in the withdrawal request is an "ATM". If the withdrawal destination included in the withdrawal request is an "ATM", the withdrawal processing unit 43 subtracts the withdrawal amount from the "salary" item of the total balance of the settlement account linked to the withdrawal source ID.

[0070] Furthermore, if the withdrawal destination included in the withdrawal request is other than "ATM," for example, if the withdrawal destination is a "bank account," the withdrawal processing unit 43 may subtract the withdrawal amount from the item selected by the user among the "salary" and "regular" items of the settlement account linked to the withdrawal source ID. The selection of the balance item to be used as the withdrawal source (in this case, the "salary" and "regular" items) may be made by operating the ATM 600. Alternatively, it may be set in advance by the user.

[0071] (Regarding the display control unit 44) The display control unit 44 displays content related to the electronic payment service provided by the management system 1 on the user terminal 100 used by the user.

[0072] For example, when the reception unit 41 receives a request from the user terminal 100 to confirm the total balance, the display control unit 44 transmits balance information indicating the total balance of the settlement account owned by the user identified by the user ID included in the confirmation request to the user terminal 100. At this time, the display control unit 44 obtains information for the "total balance," "salary," and "other than salary" items from the settlement account linked to the user ID, and displays the obtained information on the user terminal 100 via the settlement application.

[0073] Figure 7 shows an example of balance information displayed on the user terminal 100. Figure 7 is a diagram showing an example of the screen of the user terminal 100 according to the first embodiment. As an example, Figure 7 shows the balance information of a settlement account owned by user U1.

[0074] As shown in Figure 7, the display control unit 44 retrieves information such as "Total Balance" of "1,000,000 yen", "Salary" of "700,000 yen", and "Other than Salary" of "300,000 yen" from the settlement account linked to user ID "U1", and displays the retrieved information on the user terminal 100.

[0075] In this way, the display control unit 44 divides the total digital money balance into salary balance and non-salary balance and displays it on the user terminal 100 used by the user.

[0076] [3. Management Process Flow] Next, the procedure for the management processing of the payment server 10 according to the first embodiment will be described. First, the procedure for deposit processing will be described with reference to Figure 8. Figure 8 is a flowchart showing an example of the procedure for deposit processing among the management processing according to the first embodiment.

[0077] As shown in Figure 8, the settlement server 10 accepts the payment request (step S101). Next, the settlement server 10 determines whether the name of the payment request is "salary" (step S102). If it is determined that the name is "salary" (step S102; Yes), the settlement server 10 makes the payment to the salary balance (step S103). Specifically, the settlement server 10 transfers funds from the payment source's settlement account to the payee's salary balance.

[0078] On the other hand, if the payment request is not for "salary," that is, if it is determined to be for "non-salary" (step S102; No), the settlement server 10 makes the payment to the non-salary balance (step S104). Specifically, the settlement server 10 transfers funds from the payment source's settlement account to the payment recipient's non-salary balance. After completing the processing in step S103 or step S104, the settlement server 10 terminates the payment process.

[0079] Next, the withdrawal process procedure will be explained with reference to Figure 9. Figure 9 is a flowchart showing an example of the withdrawal process procedure among the management processes according to the first embodiment.

[0080] As shown in Figure 9, the settlement server 10 accepts the withdrawal request (step S201). Next, the settlement server 10 determines whether the withdrawal destination is an ATM or not (step S202). If it is determined that the withdrawal destination is an ATM (step S202; Yes), the settlement server 10 withdraws the funds from the salary balance (step S203).

[0081] On the other hand, if the withdrawal destination is not an ATM, that is, if it is determined that the withdrawal destination is a bank account (step S202; No), the settlement server 10 withdraws the funds from the balance item selected by the user from the salary balance and non-salary balance (step S204). After completing the processing in step S203 or step S204, the settlement server 10 sends a withdrawal instruction to the bank server 600 (step S205) and terminates the withdrawal process.

[0082] [4. Second Embodiment] Next, the management process according to the second embodiment will be described with reference to Figure 10. Figure 10 is a diagram showing an example of the management process according to the second embodiment.

[0083] As shown in Figure 10, when the settlement server 10 receives a salary deposit request from the payer server 400 (step S21), it deposits digital money as salary into the settlement account of the user to whom the salary will be paid (step S22). As described above, the salary deposit request includes, for example, the identification information of the user (payee) receiving the salary (payee ID), the deposit amount, and the name of the deposit. Also, as described above, when the name included in the deposit request is "salary", the settlement server 10 deposits the amount of digital money included in the deposit request into the "salary balance" of the settlement account linked to the payee ID.

[0084] Next, the payment server 10 performs sorting processing on a portion of the digital money deposited as salary into the payment recipient's payment account, sorting it according to its purpose based on the user information of the user who is the payment recipient (step S23).

[0085] For example, user information may include setting information related to salary classification (hereinafter referred to as "classification information"). Classification information may include, for example, identification information that identifies the transaction target (transaction target identification information, hereinafter referred to as "transaction target ID"), identification information that identifies the provider that provides the transaction target (provider identification information, hereinafter referred to as "provider ID"), the amount of the transaction target, etc.

[0086] In the example shown in Figure 10, the system is configured to allocate "10,000 yen" to Use A, "5,000 yen" to Use B, and "3,000 yen" to Use C. In this case, when digital money is deposited into the user's payment account as salary, the payment server 10 sorts the deposited digital money according to the sorting information, allocating 10,000 yen to Use A, 5,000 yen to Use B, and 3,000 yen to Use C. In this case, the payment server 10 restricts the use of 18,000 yen of the deposited digital money as salary to Uses A-C. In other words, the amount of salary that the user can use for purposes other than Uses A-C is the total salary minus 18,000 yen.

[0087] Thus, the payment server 10 according to the second embodiment limits the use of digital money deposited as salary by sorting it based on user information. This allows users to prevent overspending of their salary by setting up the system to separate expenses that occur every month, such as utility bills, communication fees, and tuition fees.

[0088] Furthermore, when digital money is deposited as salary, the payment server 10 may automatically use the digital money sorted by purpose for that purpose. For example, if purpose A is a deposit into an investment account owned by the user, the payment server 10 may automatically move 10,000 yen of the digital money deposited as salary to the investment account. Also, for example, if purpose B is the purchase of goods that the user buys regularly (for example, monthly), the payment server 10 may move 5,000 yen of the digital money deposited as salary to the payment account of the provider of those goods.

[0089] Thus, as part of the sorting process for digital money deposited as salary, the payment server 10 may either set aside a portion of the digital money deposited as salary in the payment account owned by the user, or it may move a portion of the digital money deposited as salary to an account other than the payment account owned by the user.

[0090] Furthermore, the settlement server 10 may generate sorting information based on user input operations, or based on withdrawal history information among user information. For example, the settlement server 10 may estimate the transaction items that the user regularly purchases based on the withdrawal history information, and generate sorting information that includes the transaction item ID of the estimated transaction item, the provider ID of the provider that provides the transaction item, and the amount of the transaction item. In this case, the settlement server 10 may propose to the user whether or not to use the generated sorting information, and if the proposal is approved, it may adopt the generated sorting information.

[0091] [5. Configuration of the payment server] Next, the configuration of the payment server according to the second embodiment will be described with reference to Figure 11. Figure 11 is a diagram showing an example of the configuration of the payment server according to the second embodiment.

[0092] As shown in Figure 11, the control unit 40 of the settlement server 10 according to the second embodiment includes an acquisition unit 45, a fund transfer unit 46, an estimation unit 47, a determination unit 48, a settlement processing unit 49, and a proposal unit 50. The storage unit 30 of the settlement server 10 according to the second embodiment includes a history database 32, a registration information database 33, and a billing information database 34.

[0093] (Regarding account database 31) An example of the information stored in the account database 31 according to the second embodiment will be explained with reference to Figure 12. Figure 12 is a diagram showing an example of the account database according to the second embodiment.

[0094] As shown in Figure 12, the account database 31 according to the second embodiment includes items such as "Everyday Use," "Reserve #1," and "Reserve #2" under the "Salary" item. The "Everyday Use" item stores the amount of digital money deposited as salary that is not restricted in its use, i.e., digital money that the user can use freely. The "Reserve #1" and "Reserve #2" items store the amount of digital money deposited as salary that is restricted in its use. These "Reserve" items are linked to the "Sorting Information" item in the registration information database 33, which will be described later. When a new reserve item is added to the "Sorting Information" item, the newly added reserve item is also added to the account database 31.

[0095] In the second embodiment, when a deposit processing unit 42 receives a deposit request that includes "salary" as the nominal item, it stores the digital money of the "amount" included in the deposit request in the "everyday use" item of the "salary" item in the settlement account. A portion of the digital money stored in the "everyday use" item will then be moved by the fund transfer unit 46, which will be described later, to the "reserved" item of the "salary" item or to an account other than the settlement account into which the salary was deposited. This point will be described later.

[0096] (Regarding the history database 32) The history database 32 stores information about the history of transactions the user has made in the past (an example of withdrawal history information). An example of the information stored in the history database 32 will be explained with reference to Figure 13. Figure 13 is a diagram showing an example of a history database according to the second embodiment.

[0097] In the example shown in Figure 13, the history database 32 has items such as "User ID", "Date and Time", "Provider ID", "Transaction Subject", and "Amount".

[0098] The "User ID" field stores the user ID of the user who made the transaction. The "Date and Time" field stores the date and time the transaction (payment) took place. The "Provider ID" field stores the provider ID of the provider who provided the item being traded. The "Item in Transaction" field stores information to identify the item being traded (e.g., product number, product name, etc.). The "Amount" field stores the amount the user paid for the item being traded.

[0099] (Regarding registration information database 33) The registration information database 33 stores registration information about users (an example of user information). An example of the information stored in the registration information database 33 will be explained with reference to Figure 14. Figure 14 is a diagram showing an example of a registration information database according to the second embodiment.

[0100] In the example shown in Figure 14, the registration information database 33 has items such as "User ID," "Name," "Age," "Gender," "Family Composition," "Operating Account ID," and "Classification Information."

[0101] The "User ID" field stores the user ID. The "Name" field stores the name of the user identified by the user ID. Note that the name stored in the "Name" field may be represented not only by kanji, but also by hiragana, katakana, alphabet, etc. The "Age" field stores the age of the user identified by the user ID. The "Gender" field stores the gender of the user identified by the user ID. The "Family Composition" field stores the family composition of the user identified by the user ID. For example, information such as the relationship to the user, name, age, and gender may be stored in the "Family Composition" field. The "Investment Account ID" field stores identification information (investment account identification information, hereinafter referred to as "Investment Account ID") that identifies the investment account owned by the user identified by the user ID.

[0102] The "Sorting Information" field stores the sorting information set for a user identified by their user ID. For example, the "Sorting Information" field may include items such as "Sorting ID," "Provider ID," "Transaction Target," and "Set Amount."

[0103] The "Sorting ID" field stores identification information to identify sorting information. Two types of sorting IDs are stored here: "Reserved ID" and "Transfer ID". The "Reserved ID" is identification information that identifies sorting information to be reserved in the user's settlement account, while the "Transfer ID" is identification information that identifies sorting information to be transferred to an account other than the user's settlement account.

[0104] The "Provider ID" field stores the provider ID of the provider that provides the transaction item for which the transaction is intended, as identified by the sorting ID in the sorting information. The "Transaction Item" field stores information (e.g., product number, product name, etc.) used to identify the transaction item for which the transaction is intended, as identified by the sorting ID in the sorting information. The "Set Amount" field stores the set amount of digital money to be held in the settlement account or transferred to an account other than the settlement account, as identified by the sorting ID in the sorting information.

[0105] (Regarding billing information database 34) The billing information database 34 stores billing information transmitted, for example, from a provider terminal 200 or a provider server owned by the provider. Here, an example of the information stored in the billing information database 34 will be explained using Figure 15. Figure 15 is a diagram showing an example of a billing information database according to the second embodiment. In the example in Figure 15, the billing information database 34 has items such as "Billing Information ID", "User ID", "Provider ID", "Payment Deadline", "Transaction Subject", and "Amount".

[0106] The "Billing Information ID" field stores identification information to identify the billing information. The "Provider ID" field stores the provider ID that identifies the billing provider. The "User ID" field stores the user ID that identifies the user to whom the billing is being processed. The "Payment Due Date" field stores the payment due date for the billed amount. The "Transaction Subject" field stores information indicating the transaction subject to the billing. Here, for ease of understanding, "electricity" and "water" are used, but the "Transaction Subject" field stores information that can identify the transaction subject. The "Amount" field stores the amount to be billed to the recipient.

[0107] (Regarding acquisition section 45) The acquisition unit 45 acquires user information about the user. For example, the acquisition unit 45 acquires various types of information stored in the account database 31, history database 32, registration information database 33, and billing information database 34 as user information.

[0108] (Regarding Fund Transfer Section 46) The fund transfer unit 46 moves a portion of the digital money that has been received as salary from the digital money that has been accepted for deposit by the receiving unit 41, based on the user information acquired by the acquisition unit 45.

[0109] The fund transfer unit 46 moves a portion of the digital money deposited as salary to the "reserved" item within the settlement account from which the digital money was deposited, or to an account other than the settlement account from which the digital money was deposited, according to the sorting information stored in the registration information database 33. The sorting information with a reserved ID is retrieved from the registration information database 33 by the acquisition unit 45.

[0110] First, let's explain how to move digital money to the "Reserved" item within your payment account.

[0111] As described above, digital money as salary is first deposited into the "Everyday Use" item within the "Salary" item of the settlement account. When digital money is deposited into the "Everyday Use" item, the fund transfer unit 46 moves a portion of the digital money deposited into the "Everyday Use" item to the "Reserved" item according to the sorting information with the reserved ID. For example, in the registration information database 33 shown in Figure 14, two sorting information entries, "Reserved #1" and "Reserved #2," are associated with the user with user ID "U1." When digital money as salary is deposited into the account of user U1 with user ID "U1," the fund transfer unit 46 moves the digital money from the "Everyday Use" item to the "Reserved #1" item and the "Reserved #2" item of the settlement account associated with user ID "U1."

[0112] At this time, the fund transfer unit 46 moves digital money from the "Everyday Use" item to the "Reserved" item so that the amount stored in the "Reserved" item of the settlement account matches the amount stored in the "Set Amount" item of the sorting information.

[0113] For example, suppose that before the salary is deposited, the settlement account's "Reserve #1" item contains "100 yen". In this case, the fund transfer unit 46 moves "14,900 yen" from the settlement account's "Everyday Use" item to the "Reserve #1" item so that the settlement account's "Reserve #1" item becomes "15,000 yen".

[0114] The fund transfer unit 46 may also move the amount of digital money stored in the "set amount" item of the sorting information from the "regular use" item of the settlement account to the "reserved" item, regardless of the balance of the "reserved" item.

[0115] Here, as shown in Figure 14, the "Reserve #1" sorting information is linked to multiple provider IDs and multiple service targets. For example, the "Reserve #1" sorting information is linked to "electricity," "water," etc., as service targets. Thus, the "Reserve #1" sorting information may be sorting information for reserving monthly expenses (fixed costs). The "Set Amount" item linked to such "Reserve #1" sorting information may store an amount entered by the user, or an amount estimated by the estimation unit 47, which will be described later. The contents of the estimation unit 47 will be described later. Thus, the fund transfer unit 46 may move a portion of the digital money deposited as salary to the "Reserve" item based on the monthly expenditure amount estimated by the estimation unit 47.

[0116] Furthermore, the sorting information for "Reservation #1" may be linked not only to the above-mentioned public utility charges, but also to items that the user purchases regularly (for example, monthly) (for example, supplements or disposable contact lenses). The "Set Amount" item linked to this sorting information for "Reservation #1" may store an amount entered by the user, or an amount estimated by the estimation unit 47 described later.

[0117] Next, we will explain how to transfer a portion of the digital money deposited as salary to an account other than the settlement account from which the digital money was deposited.

[0118] When digital money is deposited as salary into the "Everyday Use" item, the fund transfer unit 46 moves a portion of the digital money deposited into the "Everyday Use" item to another account according to the sorting information with the remittance ID. For example, in the registration information database 33 shown in Figure 14, two sorting pieces of information, "Remittance #1" and "Remittance #2," are associated with the user with user ID "U1." As an example, when digital money is deposited as salary into user U1 with user ID "U1," the fund transfer unit 46 moves the set amount "3,000 yen" associated with "Remittance #1" from the "Everyday Use" item of the settlement account associated with user ID "U1" to the investment account identified by the provided target "Investment #1" associated with "Remittance #1."

[0119] Here, the sorting information for "Transfer #1" may be generated based on a proposal from the proposal unit 50, which will be described later. The contents of the proposal unit 50 will be described later. In this way, the fund transfer unit 46 may automatically transfer the amount of digital money proposed by the proposal unit 50 from the digital money deposited as salary to the investment account.

[0120] (Regarding Estimation Section 47) The estimation unit 47 estimates the types of transactions that a user regularly purchases and the amounts thereof, based on the withdrawal history information stored in the history database 32, which is obtained from the user information acquired by the acquisition unit 45.

[0121] As an example, the estimation unit 47 identifies a transaction item that a user has been purchasing consecutively over several months, based on withdrawal history information. For example, the estimation unit 47 refers to the history database 32 shown in Figure 13 and identifies that user U1 with user ID "U1" has been purchasing the item "supplement" for a price of "5,000 yen" offered by provider ID "P1" for several consecutive months (for example, three months). In this case, the estimation unit 47 estimates that the item "supplement" for a price of "5,000 yen" offered by provider ID "P1" is a transaction item that the user regularly purchases.

[0122] Furthermore, the estimation unit 47 may estimate the user's monthly expenditure amount based on the withdrawal history information stored in the history database 32, which is obtained from the user information acquired by the acquisition unit 45.

[0123] As an example, the estimation unit 47 refers to the history database 32, calculates the user's monthly expenditure for multiple months (for example, the most recent three months), and estimates the average amount (average expenditure) as the monthly expenditure.

[0124] In this case, the estimation unit 47 may calculate the average expenditure by limiting the scope of transactions. For example, the estimation unit 47 may calculate the average expenditure by limiting it to public utility charges such as water, gas, and electricity. Alternatively, the estimation unit 47 may calculate the average expenditure by limiting it to fixed expenses that are incurred every month, such as tuition fees for cram schools, rent, and loan payments, in addition to public utility charges.

[0125] Furthermore, the estimation unit 47 may estimate the monthly expenditure amount based on the invoice information stored in the billing information database 34.

[0126] For example, the estimation unit 47 refers to the billing information database 34 shown in Figure 15 and identifies billing information IDs "Billing #1" and "Billing #2" as billing information associated with user ID "U1". The billing information for "Billing #1" indicates that user U1, with user ID "U1", has been billed by provider ID "P4" for a payment of "8,000 yen" for the transaction item "electricity" by the payment deadline "2021 / 3 / 27". The billing information for "Billing #2" indicates that user U1, with user ID "U1", has been billed by provider ID "P5" for a payment of "7,000 yen" for the transaction item "water" by the payment deadline "2021 / 3 / 27".

[0127] In this case, the estimation unit 47 may estimate "15,000 yen," which is the total amount of electricity and water bills, as the user U1's expenditure for March.

[0128] Furthermore, the estimation unit 47 may estimate the amount of digital money to be transferred to the investment account based on the amount of digital money deposited as salary and user information.

[0129] For example, the estimation unit 47 determines the percentage of the salary to be deposited into the investment account based on at least one of the user's age, gender, and family structure stored in the registration information database 33. For example, the settlement server 10 may have pre-stored market information (for example, "a single man in his 30s should invest 3% of his salary") that links combinations of age, gender, and family structure with the above percentage, and in this case, the estimation unit 47 may determine the above percentage based on the market information.

[0130] The estimation unit 47 then uses the salary amount and the above-mentioned percentage to estimate the amount of digital money to be transferred to the investment account.

[0131] (Regarding the determination unit 48) When the receiving unit 41 receives payment information, the determination unit 48 determines whether the payment details match the purpose set in the "reservation" item in the payment account.

[0132] For example, if the payment information includes user ID "U1", provider ID "P4", and service subject "electricity", the determination unit 48 determines that the payment content matches the purpose set in the sorting information of "reservation #1", that is, the provider ID and service subject associated with "reservation #1".

[0133] Furthermore, if the payment information includes user ID "U1", provider ID "P1", and item to be provided "supplement", the determination unit 48 determines that the payment details match the purpose set in the sorting information of "reservation #2", that is, the provider ID and item to be provided linked to "reservation #2".

[0134] (Regarding payment processing unit 49) The payment processing unit 49 executes payment processing according to the payment information received by the reception unit 41. For example, the payment processing unit 49 moves the amount of digital money indicated by the payment amount from the user's account indicated by the user ID to the provider's account indicated by the provider ID.

[0135] Here, if the determination unit 48 determines that the content of the settlement information received by the reception unit 41 matches the purpose set in the "reserved" item of the settlement account, the settlement processing unit 49 performs settlement processing using the balance of the "reserved" item whose purpose matches.

[0136] For example, if the payment information received by the reception unit 41 includes user ID "U1", provider ID "P1", product "supplement", and amount "5,000 yen", the payment processing unit 49 will transfer "5,000 yen" from the balance "5,000 yen" in the "Reservation #2" item to the payment account of provider ID "P1".

[0137] Thus, the use of digital money linked to a "reserved" item is limited to the purpose set for that "reserved" item. Therefore, users can prevent wasteful spending of digital money by reserving the digital money they need each month in advance in the "reserved" item.

[0138] (Regarding Proposal 50) The proposal unit 50 generates sorting information based on the estimation results from the estimation unit 47, and transmits the contents of the generated sorting information to the user terminal 100 via the communication unit 20 and network N, proposing to the user that they use the generated sorting information to set aside or automatically transfer their salary.

[0139] When the proposal unit 50 receives notification from the user terminal 100 via the communication unit 20 and network N that it approves the above proposal, it registers the approved sorting information in the registration information database 33.

[0140] Furthermore, when the proposal unit 50 receives sorting information created by the user operating the user terminal 100 via the communication unit 20 and the network N, it may register the received sorting information in the registration information database 33.

[0141] (Regarding the display control unit 44) In the second embodiment, the display control unit 44 displays the total balance of digital money as salary, i.e., the salary balance, on the user terminal 100 used by the user, divided into a reserved balance and a regular spending balance.

[0142] For example, when the reception unit 41 receives a request from the user terminal 100 to confirm the salary balance, the display control unit 44 transmits the salary balance of the settlement account owned by the user, i.e., the total amount of digital money linked to the "salary" item, to the user terminal 100 of the user identified by the user ID included in the confirmation request. At this time, the display control unit 44 retrieves information for the "everyday use" item and the "reserved" item from the settlement account linked to the user ID, and displays the retrieved information on the user terminal 100 via the payment application.

[0143] Figure 16 shows an example of salary balance information displayed on the user terminal 100. Figure 16 is a diagram showing an example of the screen of the user terminal 100 according to the second embodiment. As an example, Figure 16 shows the salary balance information of a settlement account owned by user U1.

[0144] As shown in Figure 16, the display control unit 44 retrieves information such as "525,000 yen" as the "salary" item, "500,000 yen" as the "everyday use" item, and "25,000 yen" as the "reserved" item from the payment account linked to user ID "U1", and displays the retrieved information on the user terminal 100.

[0145] Thus, the display control unit 44 may display the digital money salary balance on the user terminal 100 used by the user, divided into a balance for everyday use and a balance for reserved use.

[0146] [6. Management Process Flow] Next, the procedure for the management process of the payment server 10 according to the second embodiment will be described. First, the sorting information registration process will be described with reference to Figure 17. Figure 17 is a flowchart showing an example of the procedure for the sorting information registration process among the management processes according to the second embodiment.

[0147] As shown in Figure 17, the payment server 10 generates sorting information based on the estimation results from the estimation unit 47 (step S301). Subsequently, the payment server 10 transmits the generated sorting information to the user terminal 100 and proposes to the user that they register the sorting information (step S302).

[0148] Next, the settlement server 10 determines whether the proposal in step S302 has been approved (step S303). If it determines that the proposal has been approved (step S303; Yes), it registers the proposed sorting information in the registration information database 33 (step S304).

[0149] If the process in step S304 is completed, or if the proposal is not approved in step S303 (step S303, No), the settlement server 10 terminates the sorting information registration process.

[0150] Next, the fund transfer process will be explained with reference to Figure 18. Figure 18 is a flowchart showing an example of the procedure for the fund transfer process among the management processes according to the second embodiment.

[0151] As shown in Figure 18, the settlement server 10 deposits the digital money as salary into the everyday spending balance ("Everyday Spending" item) in the account database 31 (step S401). Next, the settlement server 10 determines whether or not the sorting information ("Reserved" sorting information) associated with the "Reserved ID" is registered in the registration information database 33 (step S402). If it is determined that the "Reserved" sorting information is registered (step S402; Yes), the settlement server 10 moves the digital money from the everyday spending balance to the reserved balance according to the "Reserved" sorting information (step S403).

[0152] If the process in step S403 is completed, or if the "reservation" sorting information is not registered in step S402 (step S403; No), the settlement server 10 determines whether sorting information associated with the "transfer ID" ("transfer" sorting information) is registered in the registration information database 33 (step S404). If it is determined that the "transfer" sorting information is registered (step S404; Yes), the settlement server 10 moves the digital money from the regular balance to another account according to the "transfer" sorting information (step S405).

[0153] If the process in step S405 is completed, or if the "remittance" sorting information is not registered in step S404 (step S404; No), the settlement server 10 terminates the fund transfer process.

[0154] Next, the payment processing will be explained with reference to Figure 19. Figure 19 is a flowchart showing an example of the payment processing procedure among the management processes according to the second embodiment.

[0155] As shown in Figure 19, the settlement server 10 acquires settlement information (step S501). Next, the settlement server 10 determines whether the content of the acquired settlement information matches the purpose set for the reserved balance (step S502). If it is determined that it matches the purpose set for the reserved balance (step S502; Yes), the settlement server 10 performs settlement processing using the reserved balance (step S503).

[0156] On the other hand, if the purpose set for the reserved balance does not match in step S502 (step S502; No), the settlement server 10 performs the settlement process using the regular balance (step S504). After completing the process in step S503 or step S504, the settlement server 10 terminates the settlement process.

[0157] [7. Variations] The embodiments described above are merely examples, and various modifications and applications are possible.

[0158] In the embodiment described above, an example was given of moving a portion of the digital money deposited as salary. However, similarly, a portion of digital money other than salary may be set aside or moved to a different account. For example, in the account database 31 shown in Figure 12, the "Other than salary" item may include items such as "Everyday use" and "Set aside". In this case, when a deposit request that includes a designation other than salary is received, the digital money of the "Amount" included in the deposit request is stored in the "Everyday use" item within the "Other than salary" item of the settlement account. A portion of the digital money stored in the "Everyday use" item is then moved by the fund transfer unit 46, described later, to the "Set aside" item within the "Salary" item or to an account other than the settlement account into which the salary was deposited. Thus, fund transfer processing may be performed on digital money other than salary.

[0159] The payment request sent from the payer server 400 to the settlement server 10 may include information on the "payment date." The "payment date" is information that specifies the date on which the payment processing will be performed. In this case, the settlement server 10 will perform the payment processing on the payment date specified by the "payment date" included in the payment request. In other words, the settlement server 10 will hold the payment processing until the payment date specified by the "payment date." Thus, the management system 1 may be configured to allow the digital payment of salaries to be scheduled.

[0160] The "payment date" information only needs to include at least the month. For example, if the "payment date" information includes "April," the payment server 10 should execute the payment processing on a predetermined day in April (for example, April 25th).

[0161] Of the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, and conversely, all or part of the processes described as being performed manually can be performed automatically by known methods. In addition, the processing procedures, specific names, and information including various data and parameters shown in the above documents and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in each figure is not limited to the information shown.

[0162] Furthermore, the components of each illustrated device are functionally conceptual and do not necessarily need to be physically configured as shown. In other words, the specific forms of distribution and integration of each device are not limited to those shown, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads and usage conditions.

[0163] Furthermore, the embodiments described above can be combined as appropriate, provided that the processing content is not contradictory.

[0164] [8. Effects] As described above, the payment server 10 according to the embodiment is a management device that manages the balance of digital money used for electronic payments by reading a predetermined code, and has a reception unit 41 and a deposit processing unit 42. The reception unit 41 receives a deposit request that includes the identification information of the user receiving the digital money deposit and the name of the deposit. The deposit processing unit 42, when the name included in the deposit request received by the reception unit 41 is salary, performs a deposit processing for the salary balance of the total balance linked to the identification information included in the deposit request, and when the name included in the deposit request received by the reception unit 41 is a name other than salary, it performs a deposit processing for the balance other than salary of the total balance linked to the identification information included in the deposit request.

[0165] As a result, the payment server 10 according to this embodiment can manage the balance of digital money owned by the user separately into salary balance and non-salary balance. Therefore, according to the payment server 10 according to this embodiment, when a digital payment of salary is made, the balance including salary can be properly managed.

[0166] Furthermore, in the payment server 10 according to this embodiment, the reception unit 41 receives a withdrawal request to an ATM that includes the user's identification information. The payment server 10 according to this embodiment also has a withdrawal processing unit 43 that, when a withdrawal request is received by the reception unit 41, processes the withdrawal from the salary balance among the total balances linked to the identification information included in the withdrawal request.

[0167] This allows users to cash out their salaries received in digital money directly from ATMs without going through a bank account (i.e., without first transferring the digital money to a bank account).

[0168] Furthermore, the payment server 10 according to this embodiment includes a display control unit 44 that divides the total balance into salary balance and non-salary balance and displays them on the user terminal 100 used by the user.

[0169] This allows users to easily check the balance of their salary deposited into their settlement account. Furthermore, users can easily see the balance of digital money they own that can be cashed out at an ATM.

[0170] Furthermore, the payment server 10 according to this embodiment includes an acquisition unit 45, a receiving unit 41, and a fund transfer unit 46. The acquisition unit 45 acquires user information relating to users who use a predetermined payment method. The receiving unit 41 accepts deposits of digital money to users. The fund transfer unit 46 transfers a portion of the digital money that has been accepted by the receiving unit 41 as salary, based on the user information acquired by the acquisition unit 45.

[0171] This allows users to set aside a portion of the digital money deposited as their salary for things like monthly utility bills, or to automatically transfer it to an account other than their settlement account, such as an investment account. Therefore, the settlement server 10 according to this embodiment can promote the use of electronic payment services that support digital salary payments.

[0172] Furthermore, in the payment server 10 according to this embodiment, the fund transfer unit 46 moves a portion of the digital money deposited as salary to an account other than the payment account into which the digital money was deposited. This allows users to move a portion of their deposited salary to a predetermined account without, for example, having to operate a terminal. Therefore, the payment server 10 according to this embodiment can promote the use of electronic payment services that support digital salary payments.

[0173] Furthermore, in the payment server 10 according to this embodiment, accounts other than the payment account are investment accounts. The payment server 10 according to this embodiment further includes an estimation unit 47 that estimates the amount of digital money to be transferred to the investment account based on the amount of digital money deposited as salary and user information. The fund transfer unit 46 transfers the amount of digital money estimated by the estimation unit 47 from the digital money deposited as salary to the investment account.

[0174] This allows users to transfer a portion of their deposited salary to an investment account without having to perform any terminal operations, for example. Furthermore, since the amount of digital money to be transferred to the investment account is estimated by the estimation unit 47, users do not have to worry about how much of their salary to allocate to investments. Therefore, the payment server 10 according to this embodiment can promote the use of electronic payment services that support digital salary payments.

[0175] Furthermore, in the payment server 10 according to this embodiment, the fund transfer unit 46 moves a portion of the digital money deposited as salary to the reserved balance of the payment account into which the digital money as salary was deposited.

[0176] This allows users to, for example, set aside the digital money they need each month in their settlement account, thus curbing wasteful spending of digital money.

[0177] Furthermore, the payment server 10 according to this embodiment includes a determination unit 48 and a payment processing unit 49. When payment information relating to a payment using a predetermined payment method is acquired, the determination unit 48 determines whether the content of the payment matches the purpose set in the reserved balance. If the determination unit 48 determines that the content of the payment matches the purpose, the payment processing unit 49 performs payment processing using the reserved balance.

[0178] This allows you to limit the use of digital money deposited into your reserved balance. In other words, it prevents digital money deposited into your reserved balance from being used for purposes other than those intended.

[0179] Furthermore, the payment server 10 according to this embodiment has an estimation unit 47 that estimates the monthly expenditure amount based on the withdrawal history information of the payment account owned by the user, which is obtained by the acquisition unit 45. The fund transfer unit 46 moves a portion of the digital money deposited as salary to the reserve balance based on the expenditure amount estimated by the estimation unit 47.

[0180] In this way, by setting aside the estimated monthly expenditure amount calculated by the estimation unit 47 in the reserve balance, it is possible to curb users from overspending with digital money.

[0181] Furthermore, the payment server 10 according to this embodiment has an estimation unit 47 that estimates the monthly expenditure amount based on invoice information indicating the content of the billing to the user, which is obtained from the user information acquired by the acquisition unit 45. The fund transfer unit 46 moves a portion of the digital money deposited as salary to the reserve balance based on the expenditure amount estimated by the estimation unit 47.

[0182] In this way, by setting aside the estimated monthly expenditure amount calculated by the estimation unit 47 in the reserve balance, it is possible to curb overspending of digital money by users. Furthermore, by estimating the expenditure amount based on invoice information, the monthly expenditure amount can be estimated with greater accuracy.

[0183] Furthermore, the payment server 10 according to this embodiment includes a display control unit 44 that displays the total balance of digital money as salary, divided into a reserved balance and a balance other than the reserved balance, on the user's terminal 100.

[0184] This allows users to easily track the balance of their salary deposited into their payment account, separating the balance of digital money with restricted use from the balance of digital money that can be used freely.

[0185] [9. Hardware Configuration] Furthermore, the payment server 10 according to each embodiment described above is implemented by a computer 1000 having a configuration such as that shown in Figure 20. The following explanation will use the payment server 10 as an example. Figure 20 is a hardware configuration diagram showing an example of a computer that implements the functions of a payment server. The computer 1000 has a CPU 1100, RAM 1200, ROM 1300, HDD 1400, communication interface (I / F) 1500, input / output interface (I / F) 1600, and media interface (I / F) 1700.

[0186] The CPU 1100 operates based on programs stored in the ROM 1300 or HDD 1400, and controls various parts. The ROM 1300 stores boot programs executed by the CPU 1100 when the computer 1000 starts up, as well as programs that depend on the computer 1000's hardware.

[0187] The HDD 1400 stores programs executed by the CPU 1100, as well as data used by such programs. The communication interface 1500 receives data from other devices via the communication network 500 (corresponding to network N in this embodiment) and sends it to the CPU 1100, and also transmits data generated by the CPU 1100 to other devices via the communication network 500.

[0188] The CPU 1100 controls output devices such as displays and printers, and input devices such as keyboards and mice, via the input / output interface 1600. The CPU 1100 acquires data from input devices via the input / output interface 1600. The CPU 1100 also outputs data it has generated to output devices via the input / output interface 1600.

[0189] The media interface 1700 reads a program or data stored in the recording medium 1800 and provides it to the CPU 1100 via the RAM 1200. The CPU 1100 loads the program from the recording medium 1800 onto the RAM 1200 via the media interface 1700 and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or PD (Phase Change Rewritable Disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

[0190] For example, when computer 1000 functions as a payment server 10, the CPU 1100 of computer 1000 implements the functions of the control unit 40 by executing programs loaded onto RAM 1200. The HDD 1400 stores the data from the payment server 10's storage device. The CPU 1100 of computer 1000 reads and executes these programs from the recording medium 1800, but as another example, these programs may be obtained from other devices via a predetermined communication network.

[0191] [10. Other] Although some embodiments of the present invention have been described in detail above with reference to the drawings, these are illustrative examples, and the present invention can be implemented in various other forms with modifications and improvements based on the knowledge of those skilled in the art, starting with the embodiments described in the disclosure section of the invention.

[0192] Furthermore, the aforementioned payment server 10 can be flexibly configured to implement certain functions by calling external platforms, etc., via APIs (Application Programming Interfaces) or network computing.

[0193] Furthermore, the term "part" in the claims can be replaced with "means," "circuit," etc. For example, "reception part" can be replaced with "reception means" or "reception circuit." [Explanation of symbols]

[0194] 1 Management System 10 Payment Server 20 Communications Department 30 Storage section 31 Account Database 32 History Database 33. Registration Information Database 34. Billing Information Database 40 Control Unit 41 Reception Department 42. Deposit Processing Section 43. Withdrawal Processing Unit 44 Display Control Unit 45 Acquisition Department 46 Fund Transfer Department 47 Estimation part 48 Judgment section 49 Payment Processing Unit 50 Proposal Department 100 User Terminals 200 provider terminals 400 Payment source server 600 bank servers

Claims

1. An acquisition unit that acquires user information relating to a user who uses a predetermined payment method, including sorting information relating to the sorting of digital money, A deposit receiving unit that accepts digital money deposits from the aforementioned users, An estimation unit estimates the amount billed as the monthly expenditure amount based on the invoice information, which shows the content of the billing to the user, among the user information acquired by the acquisition unit, A fund transfer unit sorts the digital money received by the deposit receiving unit into a portion of the digital money received as salary and a portion of the digital money received for purposes other than salary, based on the user information which includes the expenditure amount estimated by the estimation unit as a set amount, for regularly occurring expenditures. It has, The management device is characterized in that the sorting information includes identification information that identifies the transaction object, identification information that identifies the provider that is the source of the transaction object, and a set amount of the digital money to be sorted for expenditure to the transaction object.

2. An estimation unit estimates the monthly expenditure amount based on the withdrawal history information of the settlement account owned by the user, from the user information acquired by the acquisition unit. It has, The aforementioned fund transfer unit is, Based on the user information which includes the expenditure amount estimated by the estimation unit as the set amount, a portion of the digital money deposited as salary is allocated for the regularly occurring expenditures. The control device according to feature 1.

3. A display control unit displays the total balance of the digital money, which is considered salary, on the terminal device used by the user, separating it into the balance of periodic expenditures and the balance other than the balance of periodic expenditures. The control device according to claim 1, characterized by having the following features.

4. When payment information relating to a payment using the predetermined payment method is obtained, a determination unit determines whether the content of the payment matches the purpose set for the regularly occurring expenditure, If the determination unit determines that the content of the settlement matches the intended use, the settlement processing unit performs settlement processing using the balance of the regularly occurring expenditure. The control device according to claim 1, characterized by having the following features.

5. The aforementioned payment receiving unit receives a payment request that includes the user's identification information and the purpose of the payment. If the item name included in the payment request received by the payment receiving unit is salary, the payment processing unit will process the payment for the salary balance among the total balances linked to the identification information included in the payment request. If the item name included in the payment request received by the payment receiving unit is something other than salary, the payment processing unit will process the payment for the balance of non-salary items among the total balances linked to the identification information included in the payment request. The control device according to claim 1, further comprising the following:

6. A management method performed by a computer, An acquisition step of acquiring user information relating to a user who uses a predetermined payment method, which includes sorting information relating to the sorting of digital money, A deposit acceptance process for receiving digital money deposits from the aforementioned users, An estimation step is performed to estimate the amount billed as the monthly expenditure amount based on the invoice information, which shows the content of the billing to the user, among the user information obtained by the acquisition step, A fund transfer process is performed to allocate a portion of the digital money received as salary and a portion of the digital money received for purposes other than salary, based on the user information which includes the expenditure amount estimated by the estimation process as a set amount, for regularly occurring expenditures. Includes, The management method is characterized in that the sorting information includes identification information that identifies the transaction object, identification information that identifies the provider that is the source of the transaction object, and a set amount of the digital money that is sorted for expenditure to the transaction object.

7. A procedure for acquiring user information relating to a user who uses a prescribed payment method, which includes classification information relating to the classification of digital money, A deposit acceptance procedure for accepting digital money deposits to the aforementioned users, An estimation procedure is performed to estimate the amount billed as the monthly expenditure amount based on the invoice information, which shows the details of the billing to the user, among the user information obtained by the acquisition procedure, A fund transfer procedure which, of the digital money received through the deposit acceptance procedure, separates a portion of the digital money received as salary and a portion of the digital money received for purposes other than salary, based on user information which includes the expenditure amount estimated by the estimation procedure as a set amount, for regularly occurring expenditures. Have the computer run it, The management program is characterized by including the sorting information as identification information for identifying the transaction object, identification information for identifying the provider that is the source of the transaction object, and a set amount of the digital money to be sorted for expenditure to the transaction object.

Images