Information processing device, information processing method, and information processing program

Abstract

To provide various types of services relating to fund transfer business in compliance with relevant laws and regulations.SOLUTION: An information processing device includes a reception part 531, an appropriation processing part 532, and a transfer processing part 533. The reception part 531 receives, from a service user, an instruction to charge electronic money relating to a service used by the service user. When there is money balance associated with a corporate account for which the purpose of use is predetermined, the appropriation processing part 532 executes appropriation processing of appropriating the charge specified amount specified in the charge instruction, for charging. When the charge execution date specified in the charge instruction has arrived, the transfer processing part 533 executes transfer processing of transferring electronic money corresponding to the charge specified amount appropriated for charging to another account, the charge destination.SELECTED DRAWING: Figure 16

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing method, and an information processing program.

Background Art

[0002] Conventionally, cashless payment means in commercial transactions mainly between companies and individuals have been widely recognized by consumers. In particular, due to their convenience, electronic payment services conducted online using user terminals such as smartphones owned by individual users are spreading widely among consumers.

[0003] Moreover, recently, the government has been considering the introduction of so-called "digital payment of salaries" in such electronic payment services, where salaries are paid using digital money such as electronic money and virtual currency, and further spread of services related to digital money is expected.

[0004] By the way, conventionally, when a company transfers money to another company, a service that transfers money from an account opened by the company at a specific bank to the account of the recipient is generally used. Similar services are also desired for digital money such as the above-mentioned electronic money.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, businesses that handle electronic money must comply with relevant laws and regulations when providing their services. For example, businesses that handle electronic money are classified as money transfer businesses, which are different from banking businesses, and are subject to the regulations of laws that govern money transfer businesses. For instance, while banks can accept deposits with no stated purpose indefinitely, money transfer businesses that handle electronic money are subject to restrictions such as not being able to retain electronic money equivalent to an amount with no stated purpose for a certain period of time.

[0007] This application was made in view of the above, and aims to provide an information processing device, an information processing method, and an information processing program that can provide various services related to money transfer businesses in compliance with relevant laws and regulations. [Means for solving the problem]

[0008] The information processing device according to this application manages corporate accounts individually assigned to service users. The information processing device according to this application also comprises a reception unit, a payment processing unit, and a transfer processing unit. The reception unit receives electronic money charge instructions from service users for services used by the service user. If there is a money balance linked to the corporate account with a predetermined purpose of use, the payment processing unit executes a payment processing operation to allocate the specified charge amount specified in the charge instruction for charging. When the charge execution date specified in the charge instruction arrives, the transfer processing unit executes a transfer processing operation to transfer the electronic money corresponding to the specified charge amount allocated for charging to another account that will be used as the charge destination. [Effects of the Invention]

[0009] According to one embodiment of the system, it has the effect of being able to provide various services related to money transfer businesses in compliance with relevant laws and regulations. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a diagram illustrating an overview of the information processing according to the embodiment. [Figure 2] Figure 2 is a diagram illustrating the overview of the information processing according to the embodiment. [Figure 3] Figure 3 is a block diagram showing an example configuration of the business operator Y system according to the embodiment. [Figure 4] Figure 4 is a diagram showing an overview of account information according to the embodiment. [Figure 5] Figure 5 is a diagram showing an overview of the charge instruction information according to the embodiment. [Figure 6] Figure 6 is a diagram showing an overview of the account information stored in the account information storage unit according to this embodiment. [Figure 7] Figure 7 is a diagram showing an overview of the charge history stored in the charge history storage unit according to the embodiment. [Figure 8] Figure 8 is a sequence diagram showing the overall processing flow in the information processing system according to the embodiment. [Figure 9] Figure 9 is a flowchart showing an example of the processing procedure of a service provision device according to an embodiment. [Figure 10] Figure 10 shows an example of the configuration of a service provision device according to a modified example. [Figure 11] Figure 11 is a diagram illustrating an overview of information processing according to another embodiment. [Figure 12] Figure 12 is an explanatory diagram illustrating an example of a balance transfer operation according to another embodiment. [Figure 13] Figure 13 is an explanatory diagram illustrating an example of a balance transfer operation according to another embodiment. [Figure 14] Figure 14 shows an example of balance information according to another embodiment. [Figure 15] Figure 15 shows an example of a charge instruction list according to another embodiment. [Figure 16] Figure 16 shows an example of the configuration of a service provision device according to another embodiment. [Figure 17] Figure 17 shows an example of balance information according to another embodiment. [Figure 18]FIG. 18 is a flowchart showing an example of a processing procedure of a service providing apparatus according to another embodiment. [Figure 19] FIG. 19 is a hardware configuration diagram showing an example of a computer that realizes the functions of the service providing apparatus.

Embodiments of the Invention

[0011] Hereinafter, embodiments for implementing an information processing apparatus, an information processing method, and an information processing program according to the present application (hereinafter referred to as "embodiments") will be described in detail with reference to the drawings. Note that the information processing apparatus, the information processing method, and the information processing 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 duplicate explanations are omitted.

[0012] 〔1. An Example of Information Processing According to the Embodiment〕 Hereinafter, an example of information processing according to the embodiment will be described using FIGS. 1 and 2. FIGS. 1 and 2 are diagrams showing an overview of the information processing according to the embodiment.

[0013] As shown in FIG. 1, an information processing system SYS according to the embodiment includes a business operator X system SYS-1, an A bank system SYS-2, a B bank system SYS-3, and a business operator Y system SYS-4. Note that FIG. 1 shows an example of the information processing system SYS according to the embodiment, and it may include business management systems operated and managed by other business operators not shown in FIG. 1.

[0014] In the following description, the business operator X system SYS-1 may be described as the business operator X, the A bank system SYS-2 may be described as the "A bank", and the B bank system SYS-3 may be described as the "B bank" for explanation.

[0015] Operator X system SYS-1, Bank A system SYS-2, Bank B system SYS-3, and Operator Y system SYS-4 are connected to network N-1 (see, for example, Figure 3). Operator X system SYS-1, Bank A system SYS-2, Bank B system SYS-3, and Operator Y system SYS-4 can communicate with each other through network N-1.

[0016] The Business Operator X System SYS-1 is a business management system operated and managed by Business Operator X, which conducts a specified business. The Business Operator X System SYS-1 can be implemented by, for example, a single server device or workstation, or a cloud system in which multiple server devices and multiple storage devices work together. Alternatively, Business Operator X may use information processing devices such as smartphones, tablet terminals, notebook PCs (Personal Computers), desktop PCs, mobile phones, PDAs (Personal Digital Assistants), or wearable devices instead of the Business Operator X System SYS-1.

[0017] Furthermore, when the operator X system SYS-1 receives control information from the operator Y system SYS-4 to perform predetermined information processing, it performs 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). In this embodiment, the predetermined application itself distributed from the operator Y system SYS-4 may be considered as the control information.

[0018] The A Bank System SYS-2 is a banking system operated and managed by A Bank, one of the banks with which business operator X conducts transactions. The A Bank System SYS-2 can be implemented, for example, by a single server or workstation, or by a cloud system in which multiple server devices and multiple storage devices work together.

[0019] The B Bank System SYS-3 is a banking system operated and managed by B Bank, one of the transaction banks of business operator Y, which will be described later. The B Bank System SYS-3 can be implemented, for example, by a single server device or workstation, or by a cloud system in which multiple server devices and multiple storage devices work together.

[0020] For example, Bank A's system SYS-2 and Bank B's system SYS-3 manage information such as withdrawals from bank accounts by various card companies and service providers (e.g., the amount withdrawn and the date and time of withdrawal) and current account information (account balance, etc.) as a history of bank account usage, associating them with bank users. Note that bank users may also be users of various digital money services provided by service provider Y.

[0021] The Business Operator Y System SYS-4 is a business management system operated and managed by Business Operator Y, which provides various services related to digital money. The Business Operator Y System SYS-4 includes a management system 100 for managing digital money balances, a charging system 200 for performing digital money charging processes, and a service provision device 300, which is an example of an information processing device according to the embodiment. Figure 1 shows an example of the Business Operator Y System SYS-4, and although the explanation is omitted, it may also include a payment system (for example, a server device) that performs payment processing in payment methods and payment services.

[0022] The management system 100, the charging system 200, and the service provision device 300 are implemented by a single server device or workstation, or by a cloud system in which multiple server devices and multiple storage devices work together.

[0023] The management system 100 manages deposits and withdrawals to and from digital money accounts (hereinafter referred to as "money accounts") owned by each service user in order to use the electronic payment service provided by business operator Y. Service users may include business users such as businesses that provide the items being traded, and individual users such as general consumers who receive the items being traded from businesses.

[0024] The charge system 200 enables money charging by transferring digital money between money accounts in accordance with charge instructions from service users. Digital money may include, for example, points or currencies used independently by various companies, or it may be a form of currency provided by a country, such as Japanese yen or US dollars, that can be traded electronically.

[0025] The service provision device 300 works in conjunction with the management system 100 and the charging system 200 described above to perform processing related to various services concerning digital money (electronic money) that the business operator Y provides to service users.

[0026] The various services described above are not limited to those for the purchase of goods or provision of services (settlement of debt), such as payment methods or payment services. For example, the various services described above may have functions related to transfers between accounts held by multiple users. In other words, the various services described above may include services that control the sending and receiving of digital money between accounts of any owner linked to the owner of the digital money, such as service users or stores. That is, the various services according to the embodiment may be provided in any form as long as they are transaction means or transaction services that perform various controls to realize the exchange of digital money (not only various inter-account transfer controls via electronic money, but also controls related to exchanges between electronic money accounts and bank accounts, various debt processing such as installment payments and bonus payments, and various other controls related to the exchange of assets including electronic money). Furthermore, the various controls realized by such transaction means or transaction services may include both settlement controls and transfer controls, or only one of them. In other words, "transaction" is a concept that includes not only "settlement" of electronic money, but also "transfers" of electronic money and various other processing. In other words, the service provider 300 may be an information processing device such as a server that implements a transaction means for controlling the exchange of electronic money between any two owners.

[0027] Furthermore, the various digital money services provided by business operator Y include a corporate account service that provides service users with a corporate account linked one-to-one with business operator Y's accounts, and a money charge service that allows users to charge digital money into designated accounts. These services are provided as an inseparable combination.

[0028] A corporate account includes a main wallet and a sub-wallet linked to the corporate account granted to the service user. The main wallet accepts deposits (additions to the balance) and withdrawals (payment of the balance) of digital money. The sub-wallet accepts the allocation of the planned charge amount to be used for charge instruction transactions in response to charge instructions from the service user. The allocation for charge instruction transactions is performed, for example, on a transaction basis. A charge transaction unit refers to the unit of money charge service linked to the sub-wallet in the corporate account. Specifically, it is assumed that charge instructions are made toward the service system to which the sub-wallet is connected (for example, the service system that provides the money charge service linked to the sub-wallet). In other words, it is assumed that the service system receives the charge instruction and allocates the charge instruction transaction within the sub-wallet. Therefore, prior to this action (the action of allocating the charge instruction transaction within the sub-wallet), the target amount (the amount specified in the charge instruction) is moved (allocated) from the main wallet to the sub-wallet. Accordingly, the deposit instruction for the source of funds to be allocated to the charge instruction transaction is also performed on a charge transaction basis.

[0029] The Money Charge Service offers various options, including services that allow service users to pay employee salaries in digital money, and services that allow service users to pay employee expenses such as travel expenses and meal costs in digital money. Service users can select and use the various Money Charge Services as needed. The Money Charge Service selected by the service user is linked to the corporate account provided to the service user.

[0030] The following explanation will describe, with examples, the information processing performed by the SYS-4 system of business operator Y, using the case where business operator X is a service user of services provided by business operator Y.

[0031] As shown in Figure 1, operator X operates operator X system SYS-1 and sends a charge instruction to operator Y system SYS-4 (step S1).

[0032] The charge instruction sent by service provider X consists of the following fields: "Recipient ID", "Planned Amount", "Planned Date", and "Purpose". The "Recipient ID" field records information indicating the recipient's account. The "Planned Amount" field records information indicating the planned charge amount to be sent to the recipient. The "Planned Date" field records information indicating the planned date for the charge to be sent to the recipient. The "Purpose" field records information indicating the purpose of the charge.

[0033] The charge instructions illustrated in Figure 1 include three charge instructions. For example, the first charge instruction specifies account "U#001" as the recipient, the charge name "Salary", the scheduled charge date "2021 / 9 / 27 (Sun)", and the scheduled charge amount "300,000 yen". The second charge instruction specifies account "U#002" as the recipient, the charge name "Salary", the scheduled charge date "2021 / 9 / 27 (Sun)", and the scheduled charge amount "300,000 yen". Furthermore, the third charge instruction specifies account "U#003" as the charge destination, the charge name as "Expenses," the scheduled charge date as "2021 / 9 / 30 (Sun)," and the scheduled charge amount as "400,000 yen." Note that while Figure 1 shows an example where business operator X requests money charges for multiple purposes with a single charge instruction, business operator X may also request money charges individually for each purpose.

[0034] On the other hand, when the service provider 300 receives a charge instruction from business operator X, it registers the received charge instruction with the charge system 200 (step S2). The service provider 300 can temporarily hold the charge instruction from business operator X until it is processed by the charge system 200.

[0035] Furthermore, upon receiving a charge instruction, the service provider 300 (business operator Y) notifies business operator X, the sender of the charge instruction, of the information (account number) of a one-time account that business operator Y has borrowed from Bank B, as the destination for depositing the funds to be used for the charge instruction transaction. At this time, the service provider 300 (business operator Y) has pre-linked the account number of the one-time account with business operator X's main wallet. The one-time account is a virtual account of business operator Y that is contracted in business operator Y's name. By using this one-time account, the balance that will be used as the source of funds for the charge instruction transaction can be deposited via bank transfer. In addition, as a result of using the one-time account, business operator Y can easily identify the deposit of the source of funds corresponding to the charge instruction and streamline the reconciliation process. Business operator Y may also issue an electronic invoice to notify business operator X of the total amount of the planned charge amount specified in the charge instruction as the deposit amount required for the money charge, and may include the information of the one-time account in the issued invoice. Furthermore, if business operator Y can borrow multiple one-time accounts from bank B, business operator Y may notify business operator X of different one-time account information for each purpose included in the charge instruction. In this case, business operator Y may use different one-time accounts for depositing funds to be used for charge instruction transactions depending on the specific purpose included in the charge instruction (for example, salary) and other items, and notify business operator X of different account information for each. Here, the service provider 300 uses different one-time accounts and sub-wallets for each service. For example, if the purpose of the charge instruction is salary (when using the salary charge service), the service provider 300 uses one-time account AC-1 and sub-wallet WR-1; if the purpose of the charge instruction is a purpose other than salary Q, it uses one-time account AC-2 and sub-wallet WR-2; and if the purpose of the charge instruction is a purpose other than salary R, ​​it uses one-time account AC-2 and sub-wallet WR-3. In other words, if the purpose of the charge instruction is a purpose other than salary, the same one-time account AC-2 is used.

[0036] Meanwhile, after sending the charge instruction, business operator X sends a deposit instruction to bank A system SYS-2 via business operator X system SYS-1 for the funds to be used for the charge instruction transaction (step S3). The deposit instruction includes information such as the account number to identify the one-time account at bank B notified by business operator Y as the recipient (e.g., "OBAC#111") and the deposit amount (e.g., "1,000,000 yen"). Figure 1 shows an example where business operator X sends a deposit instruction to deposit the total amount of the planned charge amounts corresponding to multiple items included in the charge instruction as the funds to be used for the charge instruction transaction (total amount of planned charge). Note that if business operator X makes charge instructions for each charge item, it may deposit the funds to be used for the charge instruction transaction (total amount of planned charge) sequentially for each charge instruction. For example, after making a charge instruction for salary, business operator X may send a deposit instruction to deposit the funds to be used for the charge instruction transaction for salary (e.g., "600,000 yen"). Furthermore, for example, business operator X may issue a charge instruction for expenses in addition to a charge instruction for salaries, and after issuing the charge instruction for expenses, send a deposit instruction to deposit funds (for example, "400,000 yen") to be used for the charge instruction transaction for expenses.

[0037] Furthermore, business operator Y may enter into a contract with each service user, including business operator X, to ensure that they comply with the procedure of charge instruction (step S1) → deposit instruction (step S3) when using the money charge service, or may establish terms of use and obtain the consent of each service user. This makes it possible to clarify the use of the digital money balance corresponding to the funds deposited by business operator X when it is managed in business operator Y's system SYS-4, as will be described later.

[0038] Meanwhile, Bank A's Bank A system SYS-2, in accordance with the deposit instruction received from business operator X, deposits the amount specified in the deposit instruction (for example, "1,000,000 yen") into the one-time account specified in the deposit instruction (for example, "OBAC#111") (Step S4).

[0039] Meanwhile, when Bank B's Bank B system SYS-3 confirms a deposit from business X to the one-time account number it lent to business Y, it sends a deposit notification to business Y's system SYS-4 to inform business Y that a deposit has been made (step S5).

[0040] Furthermore, Bank B lends Business Y accounts in Business Y's name, in addition to the one-time accounts it lends Business Y, as a destination for depositing funds to be used for charge instruction transactions. Some of the accounts that Bank B lends to Business Y are subject to a pledge. This is a measure by Bank B to guarantee the deposits of Business X, which were deposited on behalf of Business Y under the guise of salary. When Bank B confirms a deposit into a one-time account designated as salary (corresponding to charge instruction transactions designated as salary), it notifies Business Y of the deposit and then automatically transfers the balance of this one-time account to an account in Business Y's name on which a pledge has been established for management. Also, when Bank B confirms a deposit into a one-time account designated as something other than salary (corresponding to charge instruction transactions designated as something other than salary), it notifies Business Y and then automatically transfers the balance of this one-time account to an account in Business Y's name on which no pledge has been established for management. This allows the service provider 300 to provide stable services while indirectly protecting deposits made by business operator X in an account under business operator Y's name under a predetermined name (for example, salary). As a result, the psychological barrier to business operator X using the service can be lowered, and the use of digital money-related services can be promoted.

[0041] On the other hand, when the management system 100 receives a deposit notification from Bank B, it adds a predetermined balance equivalent to the amount notified by the deposit notification to the main wallet of business operator X (step S6). For example, if the management system 100 receives a deposit notification that "1,000,000 yen" has been deposited into the one-time account with account number "OBAC#111", it identifies the main wallet linked to the one-time account and adds (records) the balance of "1,000,000 yen" to the identified main wallet. The management system 100 also adds a digital money balance equivalent to "1,000,000 yen" to the money account linked to the main wallet. The management system 100 may also notify the service provider device 300 that the addition (recording) of the balance to the main wallet has been completed.

[0042] Meanwhile, after receiving a charge instruction from business operator X, the service provider 300 allocates the planned charge amount to the sub-wallet (step S7), provided that the deposit of funds to be used for the charge instruction transaction is confirmed. For example, the service provider 300 allocates the planned charge amount specified in the charge instruction from a predetermined balance added to the main wallet and moves it to the sub-wallet corresponding to the name of the charge specified in the charge instruction. Each sub-wallet is individually established to correspond to the money charge service used by business operator X.

[0043] Specifically, the service provider 300 allocates the aforementioned planned charge amount to the sub-wallet from the predetermined balance, provided that a predetermined balance equivalent to the aforementioned source of funds is added (recorded) to the main wallet linked to the one-time account that has received a deposit notification. Specifically, in the example shown in Figure 1, the service provider 300 allocates the equivalent of "600,000 yen" to the sub-wallet for salary money charging and the equivalent of "400,000 yen" to the sub-wallet for expense money charging from the balance of "1,000,000 yen" added to the main wallet. In this way, the service provider 300 can ensure clarity regarding the use of the money allocated to the sub-wallet by handling the balance after the charge instruction has been received.

[0044] Meanwhile, the charge system 200 checks the sub-wallet at a predetermined period T1, and if the allocation to the sub-wallet is confirmed, it allocates the scheduled charge amount allocated to the sub-wallet to the charge instruction transaction (step S8). Specifically, the charge system 200 allocates the balance of the main wallet to the scheduled charge amount for charge instructions, starting with those with the closest scheduled charge dates.

[0045] For example, in the example shown in Figure 1, the charge system 200 will first allocate the planned charge amount to a charge instruction for a salary payment with a planned charge date of "2021 / 9 / 27". If the charge system 200 finds that the balance in the main wallet is insufficient to cover the planned charge amount, it can withhold the allocation to the charge instruction and notify business operator X that the balance in the main wallet is insufficient. Furthermore, after allocating the planned charge amount to the charge instruction, the charge system 200 locks the amount of digital money in the money account linked to the main wallet that corresponds to the planned charge amount, making it impossible to move until the charge is executed.

[0046] Furthermore, the charge system 200 executes the charge in accordance with the charge instructions of business operator X (step S9). Specifically, the charge system 200 identifies the money account linked to the account to be charged from among the money accounts managed in the management system 100, and transfers digital money corresponding to the planned charge amount from the money account linked to business operator X's corporate account to the identified money account.

[0047] For example, on the scheduled charge date, "2021 / 9 / 27 / Sun," the charge system 200 will transfer digital money worth "200,000 yen" from the money account of the charging source business X to the money account linked to the receiving account "U#001." Also, on the scheduled charge date, "2021 / 9 / 30 / Sun," the charge system 200 will transfer digital money worth "250,000 yen" from the money account of the charging source business X to the money account linked to the receiving account "U#002."

[0048] The service provider 300 pays out the balance of the main wallet that was not used for charge instruction transactions to business operator X in accordance with a predetermined payout cycle, within the limits that can comply with the retention regulations stipulated by law (for example, the Payment Services Act) (step S10). For example, the service provider 300 refunds to business operator X the balance that remains unused from the predetermined balance added to the main wallet as the source of digital money to be used for charge instruction transactions.

[0049] Specifically, the service provider 300 checks for the withdrawal cycle of business operator X at a predetermined period T2. Once it confirms that the withdrawal cycle has been reached, it then checks the balance of the money account linked to business operator X's main wallet. If there is an unallocated balance in the money account that has not been used for charge instruction transactions, the service provider 300 sends a deposit instruction to Bank B for an amount equivalent to the balance in business operator X's money account. The deposit instruction includes account information (account number) indicating the destination of the balance withdrawal and information on the deposit amount (information on the amount corresponding to the balance). The service provider 300 also sends an update instruction to the management system 100 to update the digital money balance in business operator X's money account to "0 yen".

[0050] Bank B, in accordance with the deposit instructions from business operator Y, deposits the amount specified in the deposit instructions (for example, an amount corresponding to the balance) to the account information (account number) specified in the deposit instructions as the recipient. Bank B may also send a notification to business operator Y's system SYS-4 that the deposit has been completed.

[0051] Furthermore, the management system 100 updates the digital money balance in business operator X's money account in accordance with the update instructions from the service provider device 300. In this way, business operator Y system SYS-4 pays out to business operator X the balance remaining in the main wallet that has not been used for charge instruction transactions.

[0052] As described above, in the business operator Y system SYS-4, the service provider 300, which is an example of an information processing device according to the embodiment, pays out to business operator X the balance remaining in the main wallet that has not been used for charge instruction transactions. As a result, the service provider 300 can provide various digital money-related services to service users while complying with retention regulations, and can promote the use of digital money-related services.

[0053] Furthermore, the service provider Y system SYS-4 can provide detailed information regarding the charging of digital money performed in response to a charge instruction, upon request from a service user.

[0054] For example, as shown in Figure 2, business operator X, which has used the money charge service, sends a charge details request to business operator Y's system SYS-4 to request detailed information about the charge (step S11). Figure 2 shows an example where business operator X requests details information corresponding to a charge instruction on "2021 / 9 / 23 (Sun)", but it is also possible to request details information for a desired period in bulk, not just by date.

[0055] When the service provider Y system SYS-4 receives a charge details request from service provider X, the service provider 300 obtains the details information corresponding to the charge details request based on the user ID included in the charge details request (step S12). The service provider 300 then transmits the obtained details information to service provider X system SYS-1 and provides the details information (step S13).

[0056] As shown in Figure 2, the detailed information provided to business operator X consists of three pieces of detailed information, for example, detail information J1, detail information J2, and detail information J3. Detail information J1 records information from the deposit of funds corresponding to the charge instruction to the withdrawal of any remaining balance not used for the charge instruction transaction.

[0057] For example, as shown in Figure 2, the details information J1 includes information such as the date the funds to be used for the charge instruction transaction were deposited into Bank B, the amount of the funds deposited, the date the balance was withdrawn, and the amount of the balance withdrawn. In the case shown in Figure 2, since the withdrawal amount is 0 yen, the date recorded as the withdrawal date, "2021 / 10 / 1 (Sun)", corresponds to the date on which the process of checking the balance of the main wallet was performed.

[0058] Furthermore, as shown in Figure 2, for example, the details information J2 includes information such as the allocation date on which the planned charge amount is allocated to the sub-wallet from a predetermined balance added to the main wallet, the allocated amount indicating the planned charge amount, and the name of the charge.

[0059] Furthermore, as shown in Figure 2, for example, the details information J3 includes information on the day the scheduled charge amount allocated to the sub-wallet was used for the charge instruction transaction, and the charge execution date on which the charge was actually executed.

[0060] In this way, business operator Y can provide service user business operator X with detailed information that allows them to understand the flow of deposits and withdrawals related to charge instructions. As a result, it is possible to promote the use of services related to digital money.

[0061] [2. Example of device configuration] The configuration of the operator Y system SYS-4 according to the embodiment will be described below. Figure 3 is a block diagram showing an example configuration of the operator Y system according to the embodiment.

[0062] As shown in Figure 3, the operator Y system SYS-4 includes a management system 100, a charging system 200, and a service provision device 300.

[0063] Operator Y's system SYS-4 is connected to network N-1. Operator Y's system SYS-4 can communicate with Operator X's system SYS-1, Bank A's system SYS-2, Bank B's system SYS-3, etc., via network N-1. Network N-1 is a WAN (Wide Area Network) such as the Internet. Network N-1 may also include communication networks such as a LAN (Local Area Network), a telephone network (e.g., a mobile phone network or a fixed telephone network), or a regional IP (Internet Protocol) network. Network N-1 may include wired networks or wireless networks.

[0064] Furthermore, the management system 100, the charging system 200, and the service provision device 300 are connected to network N-2. The management system 100, the charging system 200, and the service provision device 300 can communicate with each other via network N-2. Network N-2 is a communication network such as a LAN. Network N-2 may include a wired network or a wireless network.

[0065] (Regarding Management System 100) The management system 100 manages deposits and withdrawals to and from money accounts owned by each service user in order to use the electronic payment service provided by business operator Y. Service users may include business users such as businesses that provide the items being traded, and individual users such as general consumers that receive the items being traded from businesses. The management system 100 manages account information related to money accounts owned by business users, individual users, etc. Figure 4 is a diagram showing an overview of account information according to the embodiment.

[0066] As shown in Figure 4, the account information managed by the management system 100 has multiple fields, such as "Account ID," "Main Wallet ID," "Owner ID," and "Total Balance." These fields in the account information are interconnected.

[0067] The "Account ID" field stores the unique account ID (identification information) assigned to each account to identify the money account. The "Main Wallet ID" field stores identification information used to identify the main wallet provided to service users in the corporate account service.

[0068] The "Owner ID" field stores the Owner ID (identification information) that is individually assigned to each owner to identify the owner of the money account linked to the account ID. For example, the Owner ID may be the same as the User ID that is individually assigned to each service user when using an electronic payment service. The "Total Balance" field stores information indicating the total balance of digital money held in the money account.

[0069] For example, as shown in the example in Figure 4, the owner of the money account linked to account ID: "AC#1" is the service user assigned owner ID: "U#001," and it is shown that an amount of digital money equivalent to "50,000 yen" is held in the money account.

[0070] The "Total Balance" item may be further subdivided depending on how the digital money is managed. For example, the "Total Balance" item may be divided into a "Salary" item and a "Non-Salary" item. In this case, the "Salary" item stores information indicating the balance of digital money received as salary from the total balance stored in the "Total Balance" item. The "Non-Salary" item stores information indicating the balance of digital money received under names other than salary from the total balance stored in the "Total Balance" item.

[0071] Furthermore, the "Other than salary" category may be further subdivided into categories such as "Regular" and "Profit." In this case, the "Regular" category would store information indicating the balance of digital money that the money account holder has charged themselves. For example, the information stored in the "Regular" category could include information indicating the balance of digital money deposited from a credit card or bank account linked to the money account. Also, for example, the information stored in the "Profit" category could include information indicating the balance of digital money that has been cashed back on the payment amount when using the electronic payment service provided by business operator Y to service users.

[0072] Furthermore, when the management system 100 receives a deposit notification from the B Bank system SYS-3 in response to a deposit instruction from a service user (for example, business operator X), it adds a predetermined balance to the money account linked to the service user's (for example, business operator X's) main wallet, according to the contents of the deposit notification. For example, if the management system 100 receives a deposit notification from B Bank stating that 1,000,000 yen has been deposited, it adds a digital money balance equivalent to 1,000,000 yen to the money account linked to the main wallet. The management system 100 then updates the balance information corresponding to the main wallet of the service user who sent the charge instruction.

[0073] (Regarding the Charging System 200) The charge system 200 performs money charging by transferring digital money between money accounts in accordance with charge instructions from service users. The charge system 200 manages charge instruction information obtained from service users. Figure 5 is a diagram showing an overview of the charge instruction information according to the embodiment.

[0074] As shown in Figure 5, the charge instruction information managed by the charge system 200 includes the following items: "Charge Source ID", "Charge Destination ID", "Scheduled Amount", "Scheduled Date", and "Item". These items in the charge instruction information are interconnected.

[0075] The "Charge Source ID" field stores the account information of the service user who sent the charge instruction. In the example shown in Figure 5, for example, the user ID (identification information) that is individually assigned to each service user to identify the service user who sent the charge instruction is used as the account information indicating the source of the charge instruction.

[0076] The "Charge Destination ID" field stores the account information of the service user designated as the destination for the digital money charge via the charge instruction. In the example shown in Figure 5, for example, the user ID assigned to the service user of the charge destination is used as the account information indicating the charge destination.

[0077] The "Scheduled Amount" field stores information about the scheduled charge amount specified by the charge instruction. The "Scheduled Date" field stores information about the scheduled charge amount specified by the charge instruction. The "Description" field stores information indicating the description (purpose, use) of the charge specified by the charge instruction.

[0078] For example, as shown in the example in Figure 5, a charge instruction is indicated from the source account identified as "U#111" to the accounts identified as "U#001", "U#002", or "U#003". Specifically, the instructions indicate a charge of 300,000 yen in digital money to the account identified as "U#001" under the name of "salary," with a scheduled date of "2021 / 9 / 27 (Sun)," a charge of 300,000 yen in digital money to the account identified as "U#002" under the name of "salary," with a scheduled date of "2021 / 9 / 27 (Sun)," and a charge of 400,000 yen in digital money to the account identified as "U#003" under the name of "expenses," with a scheduled date of "2021 / 9 / 30 (Sun)."

[0079] Furthermore, the charge system 200 allocates the scheduled charge amount allocated to the sub-wallet to the charge instruction transaction at a predetermined interval (for example, the interval T1 shown in Figure 1). Specifically, the charge system 200 allocates the scheduled charge amount from the main wallet balance to the charge instructions in order of the closest scheduled charge date.

[0080] For example, as shown in Figure 5, the charge system 200 will first allocate the planned charge amount to the charge instruction from business operator X that is nominally for salary and has a planned charge date of "2021 / 9 / 27 (Sun)". If the charge system 200 finds that the balance in the main wallet is insufficient to cover the planned charge amount, it can withhold the allocation to the charge instruction and notify business operator X that the balance in the main wallet is insufficient. Furthermore, after allocating the planned charge amount to the charge instruction, the charge system 200 locks the amount of digital money in the money account linked to the main wallet that corresponds to the planned charge amount, making it impossible to move until the charge is executed.

[0081] Furthermore, the charge system 200 executes the charge in accordance with the charge instructions from business operator X. Specifically, the charge system 200 identifies the money account linked to the account to be charged from among the money accounts managed in the management system 100, and transfers digital money corresponding to the planned charge amount from the money account linked to business operator X's corporate account to the identified money account.

[0082] For example, on the scheduled charge date, "2021 / 9 / 27 / Sun", the charge system 200 will transfer the scheduled charge amount of "300,000 yen" from the money account of the charging source business X to the money account linked to the receiving account "U#001". Also, for example, on the scheduled charge date, "2021 / 9 / 27 / Sun", the charge system 200 will transfer the scheduled charge amount of "300,000 yen" from the money account of the charging source business X to the money account linked to the receiving account "U#002". For example, on the scheduled charge date, "2021 / 9 / 30 (Sun)", the charge system 200 will transfer digital money worth "400,000 yen" from the money account of the charging source business X to the money account linked to the receiving account "U#003".

[0083] (Regarding the service provision device 300) The service provision device 300 works in conjunction with the management system 100 and the charging system 200 to perform processing related to various digital money services provided by the service provider Y to service users. As shown in Figure 3, the service provision device 300 includes a communication unit 310, a storage unit 320, and a control unit 330.

[0084] (Regarding Communications Unit 310) The communication unit 310 is connected to network N-1 or network N-2 by wire or wireless connection. The communication unit 310 transmits and receives information with the operator X system SYS-1, the A bank system SYS-2, the B bank system SYS-3, etc., via network N-1. The communication unit 310 also transmits and receives information with the management system 100 and the charge system 200 via network N-2. The communication unit 310 is implemented, for example, by a NIC (Network Interface Card).

[0085] (Regarding memory unit 320) The storage unit 320 stores programs and data used for control and calculations by the control unit 330. The storage unit 320 is implemented by, for example, semiconductor memory elements such as RAM (Random Access Memory) and flash memory, or storage devices such as hard disks and optical discs. As shown in Figure 3, the storage unit 320 has an account information storage unit 321 and a charge history storage unit 322.

[0086] (Regarding the account information storage unit 321) The account information storage unit 321 stores account information relating to corporate accounts provided to service users who use the corporate account service. As described below, the corporate account service provides a main wallet and a sub-wallet used for the money charge service. Figure 6 is a diagram showing an overview of the account information stored in the account information storage unit according to the embodiment. Note that Figure 6 shows an example of account information according to the embodiment, and may be configured in a different form than the example shown in Figure 6.

[0087] As shown in Figure 6, the account information stored in the account information storage unit 321 includes multiple items such as "User ID," "Main Wallet," "Sub Wallet," "Withdrawal Cycle," "Withdrawal Destination," and "One-Time Account." These items in the account information are interconnected.

[0088] The "User ID" field stores the User ID (identification information) that was individually assigned to corporate entities such as business operator X when they registered to use the electronic payment service provided by business operator Y.

[0089] The "Main Wallet" field stores the Main Wallet ID, which is identification information used to identify the main wallet, and information indicating the balance of the money account linked to the main wallet.

[0090] The "Sub-wallet" field stores the sub-wallet ID, which is identification information for the sub-wallet, and information indicating the allocated amount from the main wallet balance to the sub-wallet. Sub-wallets are set up individually in advance for each type of charge that may be included in a charge instruction. The allocated amount is set based on the charge instruction from the service user.

[0091] The "Withdrawal Cycle" field stores information about the predetermined withdrawal cycle for digital money balances that have not been used for charge instruction transactions, within the limits of compliance with retention regulations stipulated by law (for example, the Payment Services Act). For example, the withdrawal cycle is calculated starting from the day the balance is added to the main wallet. The "Withdrawal Destination" field stores the account information (account number) of the financial institution designated by the service user as the destination for withdrawals of the amount corresponding to the digital money balance.

[0092] The "One-Time Account" field stores the account information (account number) of the One-Time Account linked to the main wallet. The One-Time Account is a transfer-only account that business operator Y borrows from bank B to use as the source of funds for charge instruction transactions. For example, the account information (account number) of the One-Time Account is notified by business operator Y (service provider device 300) to business operator X, the sender of the charge instruction.

[0093] As shown in the example in Figure 6, the main wallet balance of the service user identified by user ID: "U#111" is "0 yen", the allocated amount to the sub-wallet corresponding to the salary charge service is "600,000 yen", the allocated amount to the sub-wallet corresponding to the expense charge service is "400,000 yen", the withdrawal cycle is "7 days", the withdrawal destination is "A Bank's ordinary account (account number 123456)", and the account number of the WiTime account lent to the service user by a bank (for example, Bank B) is "OBAC#111".

[0094] (Regarding the charge history storage unit 322) The charge history storage unit 322 stores information regarding the charge history executed based on charge instructions from service users using the corporate account service. Figure 7 is a diagram showing an overview of the charge history stored in the charge history storage unit according to the embodiment. Note that Figure 7 shows an example of the charge history according to the embodiment, and the system may be configured in a different form than the example shown in Figure 7.

[0095] As shown in Figure 7, the charge history stored in the charge history storage unit 322 has multiple items, such as "User ID", "Charge Instruction Received Date", "Main Wallet Balance Addition Date", "Addition Amount", "Withdrawal Date", "Withdrawal Amount", "Sub Wallet Allocation Date", "Allocated Amount (Nominal)", "Charge Calculation Date", and "Charge Execution Date". These items in the charge history are interconnected.

[0096] The "User ID" field stores the same information as the "User ID" field in the account information described above (see, for example, Figure 6). In other words, the "User ID" field stores the User ID (identification information) that was individually assigned to a corporation such as business operator X as a service user when registering to use the electronic payment service provided by business operator Y.

[0097] The "Charge Instruction Received Date" field stores information indicating the date on which the charge instruction was received from the service user. The "Charge Instruction Received Date" field may also store date and time information, including the time of day.

[0098] The "Main Wallet Balance Addition Date" field stores information indicating the date on which the management system 100 added the balance to the money account linked to the main wallet. The "Main Wallet Balance Addition Date" field may also store date and time information, including the time of day.

[0099] The "Added Amount" field stores information indicating the balance added to the money account linked to the main wallet.

[0100] The "Withdrawal Date" field stores information indicating the date on which the remaining digital money balance that was not used for the charge instruction transaction was withdrawn from the money account linked to the main wallet to the sender of the charge instruction. The "Withdrawal Date" field may also store date and time information, including the time.

[0101] The "Withdrawal Amount" field stores information indicating the balance withdrawn from the money account linked to the main wallet to the sender of the charge instruction.

[0102] The "Sub-wallet allocation date" field stores information indicating the date on which the planned charge amount was allocated from the predetermined balance added to the main wallet to the sub-wallet corresponding to the charge name in the charge instruction. The "Sub-wallet allocation date" field may also store date and time information, including the time.

[0103] The "Allocated Amount (Nominal)" field stores information indicating the planned charge amount (allocated amount) allocated to the sub-wallet, as well as information indicating the nominal nature of the charge.

[0104] The "Charge Date" field stores information indicating the date on which the charge system 200 allocated the balance from the main wallet to the scheduled charge amount allocated to the sub-wallet. The "Charge Date" field may also store date and time information, including the time of day.

[0105] The "Charge Execution Date" field stores information indicating the date on which the planned charge amount was transferred from the money account linked to the main wallet to the money account linked to the destination account. The "Charge Execution Date" field may also store date and time information, including the time of the transfer.

[0106] As shown in the example in Figure 7, it is possible to identify information such as the date and time when a predetermined balance was added to the main wallet (B Bank deposit date), the amount added to the main wallet, the date and time when the balance from the main wallet was withdrawn, and the withdrawal amount. Furthermore, as shown in the example in Figure 7, it is possible to identify information such as the date and time when the planned charge amount was allocated to the sub-wallet, the allocated amount, and the name of the charge. Furthermore, as shown in the example in Figure 7, it is possible to identify information such as the date and time when the balance from the main wallet was used for the planned charge amount, and the date and time when the charge was executed.

[0107] (Regarding the control unit 330) The control unit 330 is a controller that performs control and calculations for the service provision device 300. Each part of the control unit 330 is implemented by, for example, a CPU (Central Processing Unit) or MPU (Micro Processing Unit) executing various programs stored in the internal memory of the service provision device 300 using RAM as the working area. The control unit 330 is also implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit), FPGA (Field Programmable Gate Array), or SoC (System on a Chip).

[0108] As shown in Figure 3, the control unit 330 includes a reception unit 331, an allocation unit 332, a disbursement unit 333, and a provision unit 334. The control unit 330 realizes or executes the information processing functions and operations described below through the parts shown in Figure 3. Although not explained here, the internal configuration of the control unit 330 is not limited to the parts shown in Figure 3, and may include parts that realize or execute information processing functions and operations for separately managing at least the salary balance from the total balance of digital money.

[0109] (Regarding reception desk 331) The reception unit 131 receives digital money charge instructions from service users. For example, the reception unit 131 receives charge instructions transmitted from service users (for example, business operator X) via the communication unit 310. The reception unit 131 registers the charge instructions with the charge system 200.

[0110] (Regarding allocation section 332) After the charge instruction is received by the reception unit 331, the allocation unit 332 executes the allocation of the planned charge amount specified in the charge instruction, provided that the deposit of funds to be used for the charge instruction transaction is confirmed.

[0111] For example, the allocation unit 332 refers to the account information stored in the account information storage unit 321 and checks whether a predetermined balance equivalent to the source of funds has been added to the main wallet linked to the account into which the source of funds for the charge instruction transaction will be deposited. If the allocation unit 332 confirms that a predetermined balance has been added to the main wallet, it allocates the planned charge amount from the balance added to the main wallet.

[0112] Specifically, the allocation unit 332 allocates the planned charge amount specified in the charge instruction to the sub-wallet corresponding to the charge name specified in the charge instruction, in response to the service user's operation. For example, if the charge name is salary, the allocation unit 332 allocates the planned charge amount from the main wallet balance to the sub-wallet corresponding to the salary charge service. The allocation unit 332 then records the information of the planned charge amount (allocated amount) allocated to the sub-wallet in the charge history storage unit 322, associating it with the service user (user ID) who sent the charge instruction.

[0113] Furthermore, the funds to be used for charge instruction transactions will be deposited into an account in which the service user (for example, business operator Y) has a loan from Bank B, and which is subject to a pledge (or revolving pledge) using the aforementioned funds as collateral, provided that the name specified in the charge instruction corresponds to a prescribed name. For example, if the name of the charge is salary, the funds will be deposited into an account in the name of the service user on which a pledge (or revolving pledge) has been established.

[0114] (Regarding the dispensing unit 333) The payout unit 333 pays out the remaining balance of digital money that was not used for the charge instruction transaction executed in response to the charge instruction to the service user according to a predetermined payout cycle. For example, the payout unit 333 pays out to the service user the balance that was not used for the charge instruction transaction from a predetermined balance that was added to the main wallet as the source of digital money to be used for the charge instruction transaction.

[0115] Specifically, the withdrawal unit 333 refers to the account information stored in the account information storage unit 321 to check whether the withdrawal cycle for the balance not used in the charge instruction transaction has been reached for business operator X, the sender of the charge instruction. The withdrawal cycle is predetermined to the extent that it is possible to comply with the retention regulations stipulated by law (for example, the Payment Services Act). If the withdrawal unit 33 confirms that the withdrawal cycle has been reached, it accesses the management system 100 to check the balance of the money account linked to business operator X's main wallet. Next, if there is a balance in business operator X's money account, the withdrawal unit 333 sends a deposit instruction to Bank B for an amount equivalent to the balance in business operator X's money account. The deposit instruction includes account information (account number) indicating the destination of the balance withdrawal and information on the deposit amount (information on the amount corresponding to the balance). The withdrawal unit 333 also sends an update instruction to the management system 100 to update the digital money balance in business operator X's money account to "0 yen".

[0116] (Regarding Section 334) The service provider 334, upon request from a service user, provides detailed information (see, for example, Figure 2) relating to the digital money charge performed in response to the charge instruction.

[0117] For example, the service provider 334 receives a charge details request sent by the service user via the communication unit 310. Then, based on the user ID included in the charge details request, the service provider 334 retrieves the details information corresponding to the charge details request from the charge history stored in the charge history storage unit 322. The charge details request may also specify the date or period for which the user wishes to receive the details information.

[0118] For example, the service provider 334 can obtain various information from the deposit of funds corresponding to the charge instruction to the withdrawal of any balance not used for the charge instruction transaction. The information that the service provider 334 can obtain from the charge history includes the deposit date on which the funds to be used for the charge instruction transaction were deposited into Bank B, the amount of the funds deposited, the date of the balance withdrawal, and the amount of the balance withdrawn. The information that the service provider 334 can obtain from the charge history also includes the allocation date on which the planned charge amount was allocated to the sub-wallet from a predetermined balance added to the main wallet, the allocation amount indicating the planned charge amount, and information on the name of the charge. Furthermore, the information that the service provider 334 can obtain from the charge history also includes the allocation date on which the planned charge amount allocated to the sub-wallet was used for the charge instruction transaction, and the charge execution date on which the charge was executed.

[0119] The provisioning unit 334 can provide the service user with multiple detailed statements of this information, compiled for each predetermined procedure. For example, the provisioning unit 334 can provide the service user with detailed statements (for example, detailed statements J1 shown in Figure 2) that compile information such as the deposit date on which the funds to be used for the charge instruction transaction were deposited into Bank B, the amount of the funds deposited, the date of the balance withdrawal, and the amount of the balance withdrawal. Also, for example, the provisioning unit 334 can provide detailed statements (for example, detailed statements J2 shown in Figure 2) that compile information such as the allocation date on which the planned charge amount was allocated to the sub-wallet from a predetermined balance added to the main wallet, the allocated amount indicating the planned charge amount, and the name of the charge. Furthermore, for example, the provisioning unit 334 can provide detailed statements (for example, detailed statements J3 shown in Figure 2) that compile information such as the allocation date on which the planned charge amount allocated to the sub-wallet was used for the charge instruction transaction, and the charge execution date on which the charge was executed.

[0120] [3. Processing Procedure] (3-1. Overall Processing) The overall processing flow in the SYS information processing system according to this embodiment will be explained below using Figure 8. Figure 8 is a sequence diagram showing the overall processing flow in the information processing system according to this embodiment.

[0121] As shown in Figure 8, the operator X system SYS-1 sends a charge instruction to the operator Y system SYS-4 in accordance with the operation performed by operator X (step S101).

[0122] When the service provider Y system SYS-4's service provision device 300 receives a charge instruction from the service provider X system SYS-1, it registers the charge instruction with the charge system 200 (step S102).

[0123] Furthermore, in accordance with the operations performed by business operator X, system SYS-1 of company X sends a deposit instruction to system SYS-2 of bank A for the funds to be used for the charge instruction transaction (step S103).

[0124] Bank A's system SYS-2 deposits the amount specified in the deposit instruction into the one-time account specified in the deposit instruction, in accordance with the deposit instruction received from business operator X (step S104).

[0125] When Bank B's system SYS-3 confirms the deposit from Bank A, it sends a deposit notification to Business Operator Y's system SYS-4 to inform Business Operator Y that the deposit has been made (step S105).

[0126] When the management system SYS-4 of business operator Y receives a deposit notification from the bank system SYS-3 of bank B, it adds a predetermined balance equivalent to the amount notified by the deposit notification to the main wallet of business operator X (step S106).

[0127] When the service provider Y system SYS-4's service provider device 300 confirms the addition of the balance to the main wallet of provider X, it allocates the planned charge amount specified in the charge instruction to the sub-wallet of provider X (step S107).

[0128] The charge system 200 of the operator Y system SYS-4 checks the sub-wallet at a predetermined interval (for example, the interval T1 shown in Figure 1), and if the allocation to the sub-wallet is confirmed, it applies the scheduled charge amount allocated to the sub-wallet to the charge instruction transaction (step S108).

[0129] Furthermore, the charging system 200 performs the charging in accordance with the charging instructions of operator X (step S109).

[0130] Meanwhile, the service provider device 300 of the operator Y system SYS-4 pays out the balance of the main wallet that was not used for the charge instruction transaction to operator X in a predetermined payout cycle (step S110). This completes the process shown in Figure 8.

[0131] (3-2. Processing of service provision equipment) Next, the processing procedure by the service provision device 300 according to the embodiment will be described using Figure 9. Figure 9 is a flowchart showing an example of the processing procedure of the service provision device according to the embodiment. The processing procedure shown below is repeatedly executed by the control unit 330 of the service provision device 300.

[0132] As shown in Figure 9, the reception unit 331 registers the charge instruction received from the service user with the charge system 200 (step S201). The allocation unit 332 also checks the balance of the main wallet of the service user who sent the charge instruction (step S202).

[0133] If the allocation unit 332 confirms that a predetermined balance has been added to the main wallet (step S202; Yes), it allocates the planned charge amount specified in the charge instruction to the sub-wallet corresponding to the charge name specified in the charge instruction (step S203).

[0134] Furthermore, the disbursement unit 333 refers to the account information stored in the account information storage unit 321 to confirm whether the service user who sent the charge instruction has reached the disbursement cycle for the balance that was not applied to the charge instruction transaction (step S204).

[0135] If the payout unit 333 confirms that the payout cycle has been reached (step S204; Yes), it accesses the management system 100 to check the balance of the money account linked to the service user's main wallet (step S205).

[0136] If there is an unallocated balance remaining in the money account linked to the service user's main wallet that has not been used for the charge instruction transaction (step S205; Yes), the payout unit 333 pays the balance of the main wallet (the balance of the money account linked to the main wallet) to the service user (step S206), and terminates the processing procedure shown in Figure 9.

[0137] On the other hand, if there is no outstanding balance remaining in the money account linked to the service user's main wallet that has not been used for the charge instruction transaction (step S204; No), the payout unit 333 terminates the processing procedure shown in Figure 9.

[0138] If it is confirmed in step S204 above that the payout cycle has not been reached (step S204; No), the confirmation procedure in step S204 is repeated at predetermined intervals.

[0139] In step S202 described above, if the allocation unit 332 confirms that a predetermined balance has not been added to the main wallet (step S202; No), it determines whether it is within the grace period for executing the charge instruction (for example, 7 days from the date of instruction receipt) (step S207).

[0140] If the allocation unit 332 determines that it is within the grace period for executing the charge instruction (step S207; Yes), it returns to the confirmation procedure in step S202 described above.

[0141] On the other hand, if the allocation unit 332 determines that it is not within the grace period for executing the charge instruction (step S207; No), it discards the charge instruction received from the service user (step S208). Then, the allocation unit 332 notifies the service user, who is the source of the charge instruction, that the charge instruction has been discarded (step S209), and terminates the processing procedure shown in Figure 9.

[0142] [4. Variations] The embodiments described above are examples of information processing according to the embodiments of the present application, and various modifications and applications are possible. The operator Y system SYS-4 may be physically or functionally distributed or integrated in any unit. For example, the processing functions of the management system 100 and the charge system 200 may be consolidated into a service provision device 300, and the service provision device 300 may execute the management system 100 and the charge system 200. The following describes an example of the configuration of the service provision device 400 in this case. Figure 10 is a diagram showing an example of the configuration of a service provision device according to a modified example.

[0143] As shown in Figure 10, the modified service provision device 400 includes a communication unit 410, a storage unit 420, and a control unit 430.

[0144] The communication unit 410 corresponds to the communication unit 310 of the service provision device 300. The communication unit 410 transmits and receives information with the carrier X system SYS-1, the A bank system SYS-2, the B bank system SYS-3, etc., via the network N-1.

[0145] The storage unit 420 corresponds to the storage unit 320 of the service provision device 300 and stores programs and data used for control and calculations by the control unit 430. As shown in Figure 10, the storage unit 420 includes an account information storage unit 421, a bank account information storage unit 422, a charge instruction information storage unit 423, and a charge history storage unit 424.

[0146] The account information storage unit 421 corresponds to the account information storage unit 321 of the storage unit 320 described above, and stores account information relating to corporate accounts provided to service users who use the corporate account service.

[0147] The account information storage unit 422 stores account information relating to money accounts owned by service users, such as business users and individual users, in order to use the electronic payment service provided by business operator Y. The account information stored in the account information storage unit 422 corresponds to the account information managed by the management system 100 described above (see Figure 4).

[0148] The charge instruction information storage unit 423 stores charge instruction information obtained from service users. The charge instruction information stored in the charge instruction information storage unit 423 corresponds to the charge instruction information managed by the charge system 200 described above (see Figure 5).

[0149] The charge history storage unit 424 corresponds to the charge history storage unit 322 of the storage unit 320 described above, and stores information regarding the charge history executed based on the charge instructions of service users using the corporate account service.

[0150] The control unit 430 corresponds to the control unit 330 of the service provision device 300 and is a controller that performs control and calculations for the service provision device 400. As shown in Figure 10, the control unit 430 has a reception unit 431, a management unit 432, an allocation unit 433, a charge unit 434, a dispensing unit 435, and a provision unit 436.

[0151] The reception unit 431 corresponds to the reception unit 331 of the control unit 330 described above, and receives digital money charge instructions from service users. The reception unit 431 registers information regarding the charge instructions received from the service in the charge instruction information storage unit 423.

[0152] The management unit 432 is responsible for the processing functions executed by the management system 100 described above, and manages deposits and withdrawals to and from the money accounts owned by each service user in order to use the electronic payment service provided by business operator Y.

[0153] For example, the management unit 432 obtains a deposit notification from the B Bank system SYS-3 via the communication unit 410, which has been executed in response to a deposit instruction from a service user (for example, business operator X). Then, the management unit 432 adds the balance of digital money linked to the service user's (for example, business operator X's) main wallet according to the contents of the obtained deposit notification. For example, if the management unit 432 receives a deposit notification from B Bank stating that 450,000 yen has been deposited, it adds the balance of digital money equivalent to 450,000 yen to the money account linked to the main wallet. The management unit 432 also updates the balance information of the service user's main wallet, which is the source of the charge instruction, from the account information stored in the account information storage unit 421.

[0154] The allocation unit 433 corresponds to the allocation unit 332 of the control unit 330 described above. After the charge instruction is received by the receiving unit 431, the allocation unit 433 executes the allocation of the planned charge amount specified in the charge instruction, provided that the deposit of funds to be used for the charge instruction transaction is confirmed.

[0155] The charge unit 434 is responsible for the processing functions performed by the charge system 200 described above, and performs money charging by moving digital money between money accounts in accordance with charge instructions from the service user.

[0156] For example, the charge unit 434 allocates the scheduled charge amount allocated to the sub-wallet to the charge instruction transaction at a predetermined period (for example, period T1 shown in Figure 1). Specifically, the charge unit 434 allocates the scheduled charge amount from the balance of the main wallet in order of the charge instructions, starting with those with the nearest scheduled charge date.

[0157] Furthermore, for example, the charge unit 434 performs a charge in accordance with the charge instruction of the service user (for example, business operator X). Specifically, the charge unit 434 refers to the account information stored in the account information storage unit 422 and identifies the money account associated with the account to which the charge is to be made, as specified in the charge instruction. The charge unit 434 then performs a money charge by transferring digital money corresponding to the planned charge amount from the money account associated with the service user's corporate account to the identified money account.

[0158] The disbursement unit 435 corresponds to the disbursement unit 333 of the control unit 330 described above, and disburses the remaining balance of digital money that was not used for charge instruction transactions to the service user according to a predetermined disbursement cycle.

[0159] The provisioning unit 436 corresponds to the provisioning unit 334 of the control unit 330 described above, and in response to a request from a service user, it provides detailed information (see, for example, Figure 2) relating to the charging of digital money performed in response to a charge instruction.

[0160] In this way, by consolidating each part of the operator Y system SYS-4 according to the above embodiment and integrating them physically and functionally into the service provision device 400, information related to various services can be centrally managed, and efficient processing can be achieved. Furthermore, the deployment of a network N-2 that connects each part of the operator Y system SYS-4 according to the above embodiment in a communicative manner becomes unnecessary, and the impact of communication failures of network N-2 on service provision can be eliminated.

[0161] [5. Other Embodiments] (5-1. Overview of information processing according to other embodiments) The following describes other embodiments for implementing the information processing device, information processing method, and information processing program according to the present application. The following describes an example of information processing when multiple main wallets are provided according to their intended use. In detail, the above-described embodiment described an example in which the planned charge amount specified in the charge instruction is automatically allocated from the main wallet to the sub-wallet by the information processing system SYS. In contrast, the information processing according to the other embodiments described below does not perform automatic allocation. Instead, the balance is transferred from the main wallet to the sub-wallet based on a transfer instruction from a service user using a corporate account, and the information processing system SYS allocates the specified amount to the charge instruction transaction based on the charge instruction.

[0162] Figure 11 is a diagram illustrating an overview of information processing according to another embodiment. As shown in Figure 11, the business operator Y system SYS-5 according to another embodiment includes a service provision device 500, which is an example of an information processing device according to another embodiment. The service provision device 500 manages corporate accounts that are individually assigned to service users (for example, business operator X) of various services provided by business operator Y.

[0163] As described below, the corporate account provided to the service user from the service provider device 500 has a first main wallet used when the charge instruction is for salary, and a second main wallet used when the charge instruction is for something other than salary.

[0164] Specifically, the corporate account shown in Figure 11 includes a main wallet for salaries and a main wallet for non-salary payments. While Figure 11 shows an example where the corporate account includes two main wallets, it may be structured in a different way than shown in Figure 11, for example, by further dividing the non-salary payment main wallet into multiple wallets.

[0165] The main salary wallet shown in Figure 11 accepts deposits, for example, from business operator X, where the charge instruction is designated as salary. This main salary wallet is linked to a bank account (for example, a one-time account) designated in advance by business operator X. This bank account is used by business operator X to deposit the source of funds for salary charges using digital money such as electronic money (hereinafter referred to as "electronic money"). The bank account linked to the main salary wallet may have a pledge on it. If the linked bank account is a one-time account, a pledge may be set on the aggregated account. This is a measure to ensure that the bank, on behalf of business operator X, guarantees the deposits received under the name of salary. In the case of salary charges, the charged electronic money is living expenses for the user, so it is necessary to take such measures to avoid situations where the user cannot use the electronic money received as salary due to business operator X going bankrupt or other reasons.

[0166] The main wallet for non-salary use shown in Figure 11 accepts deposits for purposes other than salary, such as charge instructions received by business operator X. This main wallet for non-salary use is linked to a bank account designated in advance by business operator X. This bank account is used by business operator X to deposit funds other than salary charges via electronic money. By separating the main wallet and the deposit routes to that main wallet into those for salary and those for non-salary use, it becomes possible to clearly manage salary electronic money and electronic money used for other purposes separately. This configuration is useful because it makes it easy to track the balance of salary electronic money if it becomes necessary to compensate for the salary electronic money.

[0167] Furthermore, the corporate account managed by the service provider 500 includes multiple sub-wallets, each set up for each service registered by business operator X. For example, the corporate account shown in Figure 11 includes a sub-wallet linked to the main wallet for salaries and sub-wallets linked to the main wallet for non-salary use. In the example shown in Figure 11, one sub-wallet is linked to the main wallet for salaries, and two sub-wallets are linked to the main wallet for non-salary use. Sub-wallets are set up for each service contract by the service user. For example, one service contract might be to contract for a money charge service to pay for the lease of communication equipment, and another contract for a money charge service to pay out campaign benefits to consumers. In this case, a sub-wallet is set up for each contract, linked to the corporate account of the service user who is the contracting party. In such contracts, the expenses incurred for the payment of lease fees are treated as communication expenses or rental fees in corporate accounting, and the expenses incurred for the payment of campaign benefits are allocated to selling expenses and general and administrative expenses in corporate accounting. In this way, service users can contract for services in units of their choosing, which simplifies subsequent accounting procedures.

[0168] The salary sub-wallet shown in Figure 11 allows for balance transfers between it and the salary main wallet, and accepts the application of charge instructions received in the name of salary. In the case shown in Figure 11, the salary sub-wallet will be linked to the salary charge service registered by business operator X.

[0169] The sub-wallet for non-salary use shown in Figure 11 allows for balance transfers between it and the main wallet for non-salary use, and accepts the use of charge instructions received under a name other than salary. In the case shown in Figure 11, one side of the sub-wallet for non-salary use is linked to a money charge service registered by business operator X, and the other side of the sub-wallet for non-salary use is linked to a C2B (Consumer to Business) remittance service registered by business operator X.

[0170] In this way, the service provider 500 manages corporate accounts by associating a main wallet and a sub-wallet for payroll, as well as a main wallet for non-payroll transactions with multiple sub-wallets. It should be noted that the service provider 500 is not limited to the example of hierarchically configuring corporate accounts with main and sub-wallets; corporate accounts may also be configured with a single wallet.

[0171] Furthermore, the service provider 500 receives instructions to charge electronic money related to services used by a corporation. In addition, if there is a balance in the corporation account for a predetermined purpose of use, for example, if there is a balance in the main wallet for salary, the service provider 500 executes a charge processing operation to allocate the specified charge amount specified in the charge instruction for charging. Furthermore, when the charge execution date specified in the charge instruction arrives, the service provider 500 executes a transfer processing operation to transfer the electronic money corresponding to the specified charge amount allocated for charging to another account that will be used as the charging destination.

[0172] For example, when the service provider 500 receives a deposit notification from a partner financial institution, it adds the electronic money equivalent to the deposited amount to the balance of the main wallet. Specifically, if a deposit is made to the bank account linked to the main wallet for salaries, the service provider 500 adds the balance to the main wallet for salaries. On the other hand, if a deposit is made to the bank account linked to the main wallet for non-salary payments, the service provider 500 adds the balance to the main wallet for non-salary payments.

[0173] Furthermore, the service provider 500 transfers the balance from the main wallet to the sub-wallet in accordance with the operation of the corporate account user. Below, an overview of the balance transfer operation by a corporate account user according to another embodiment will be explained using Figure 12 or Figure 13. Figures 12 and 13 are explanatory diagrams illustrating an example of a balance transfer operation according to another embodiment.

[0174] First, an example of a balance transfer operation in the main salary wallet will be explained using Figure 12. The service provider 500 provides the operation screen shown in Figure 12 in response to a request from a service user (for example, business operator X). The service provider 500 accepts a series of balance transfer operations from the service user through the operation screen shown in Figure 12. The operation screen shown in Figure 12 has a main wallet balance display area that shows the current balance of the main salary wallet, a sub-wallet balance display area that shows the current balance of the sub-wallet for salary, and a transfer money setting area for setting the electronic money to be moved from the balance of the main salary wallet to the sub-wallet for salary. The operation screen shown in Figure 12 is displayed, for example, on an information processing device used by the service user.

[0175] Service users can directly enter the amount of electronic money to be transferred into the input box provided in the money transfer settings area. In the example shown in Figure 12, the current balance of the main salary wallet is "1,000,000", and "200,000" is set as the amount of electronic money to be transferred to the sub-salary wallet.

[0176] Furthermore, after entering the amount of electronic money to be transferred, service users can move the balance from their main salary wallet to their sub-salary wallet by operating the "Transfer" button located in the money transfer settings area. Additionally, service users can reset and re-enter the amount of electronic money to be transferred by operating the "Reset" button located in the money transfer settings area.

[0177] When the service provider 500 receives an operation of the "Move" button located in the money transfer setting area from a service user, it subtracts the amount of electronic money to be moved from the balance of the main salary wallet and adds the amount of electronic money to be moved to the balance of the sub-salary wallet. The service provider 500 then redisplays the operation screen. In the example shown in Figure 12, the redisplayed operation screen shows that the current balance of the main salary wallet is "800,000" and the current balance of the sub-salary wallet is "200,000".

[0178] Next, an example of a balance transfer operation for a main wallet used for purposes other than salary will be explained using Figure 13. The service provider 500 provides the operation screen shown in Figure 13 in response to a request from a service user (for example, business operator X). The operation screen shown in Figure 13 has a main wallet balance display area that shows the current balance of the main wallet used for purposes other than salary, a sub-wallet balance display area that shows the current balance of the sub-wallet used for purposes other than salary, and a transfer money setting area for setting the electronic money to be transferred between the main wallet used for purposes other than salary and the sub-wallet used for purposes other than salary. The sub-wallet balance display area shown in Figure 13 consists of sub-wallet 1 and sub-wallet 2. For example, sub-wallet 1 is the area corresponding to the money charge service shown in Figure 11, and sub-wallet 2 is the area corresponding to the C2B remittance service shown in Figure 11. The operation screen shown in Figure 13 is displayed, for example, on an information processing device used by a service user.

[0179] Service users can directly enter the amount of electronic money to be transferred into the input box provided in the money transfer settings area. In the example shown in Figure 13, the current balance of the main wallet for non-salary use is "2,000,000", and "500,000" is set as the amount of electronic money to be transferred to the sub-wallet for non-salary use.

[0180] Furthermore, after entering the amount of electronic money to be transferred, service users can move the balance from their main wallet (for non-salary use) to their sub-wallet (for non-salary use) by operating the "Transfer" button located in the money transfer settings area. Additionally, service users can reset and re-enter the amount of electronic money to be transferred by operating the "Reset" button located in the money transfer settings area.

[0181] When the service provider 500 receives an operation of the "Move" button located in the money transfer setting area from a service user, it subtracts the amount of electronic money to be moved from the balance of the main wallet for non-salary use and adds the amount of electronic money to be moved to the balance of the sub-wallet for non-salary use. The service provider 500 then redisplays the operation screen. In the example shown in Figure 13, the redisplayed operation screen shows that the current balance of the main wallet for non-salary use is "1,500,000" and the current balance of the sub-wallet for non-salary use is "500,000". The service provider 500 is not limited to the example shown in Figure 13, and the sub-wallet balance display may show the total balance and its breakdown (paid balance and unpaid balance). The service provider 500 may also enable the transfer of balances from the sub-wallet corresponding to the money charge service to the main wallet. In this case, the service provider 500 may control the system so that only unpaid balances can be moved, and paid balances cannot be moved. The purpose is to prevent situations where already allocated balances are moved, making them unusable for further allocation. Note that allocated balances will be undone if the charge instruction is canceled. Unless the money charge service instructs a re-allocation, the balance will be treated as unallocated and returned to the main wallet.

[0182] Similarly, service users can transfer the balance of sub-wallet 2, which constitutes a sub-wallet for non-salary payments that has been deposited via the C2B remittance service, to their main wallet for non-salary payments through the operation screen shown in Figure 13.

[0183] When the service provider 500 receives a charge instruction from a service user for the purpose of salary, it executes a processing to allocate funds from the balance of the salary sub-wallet for salary charging, provided that there is a balance of money for salary charging in the salary sub-wallet. For example, the service provider 500 executes an allocation processing to allocate the balance of money in the salary sub-wallet to a charge instruction transaction related to salary charging that has not yet been allocated.

[0184] Similarly, when the service provider 500 receives a charge instruction from a service user for a charge other than salary, it executes a process to allocate funds from the sub-wallet for non-salary charges, provided that there is a balance of money in the sub-wallet for non-salary charges for charges other than salary charges. For example, the service provider 500 executes an allocation process to allocate the money balance in the sub-wallet for non-salary charges to charge instruction transactions related to non-salary charges that are currently unallocated. The service provider 500 can execute the allocation process using any processing method, such as real-time processing or batch processing. Furthermore, if the balance in the sub-wallet is insufficient to allocate funds to a charge instruction transaction, the service provider 500 may check the balance in the sub-wallet at a predetermined polling interval and, as soon as it confirms that there is a balance in the sub-wallet sufficient to allocate funds to the charge instruction transaction, allocate the planned charge amount to the charge instruction transaction. In this case, the service provider 500 may also execute a control to notify business operator X if there are unallocated charge instruction transactions a certain period before the charge execution date.

[0185] After the allocation process, when the charge execution date specified in the charge instruction arrives, the service provider 500 performs a transfer process to transfer the electronic money corresponding to the specified charge amount allocated for the charge to another account that will be used for the charge.

[0186] Furthermore, the service provider 500 may display information indicating the total balance of electronic money linked to the corporate account at the present time, the balance of money used in charge instruction transactions, and the balance of money not used in charge instruction transactions, in response to a request from a service user. Figure 14 is a diagram showing an example of balance information according to another embodiment. For example, the service provider 500 can provide the balance information shown in Figure 14 in response to a request from a service user. For example, the balance information shown in Figure 14 includes information indicating the total balance of electronic money linked to the corporate account of the service user who requested the information, and information indicating the breakdown of electronic money linked to the corporate account. Furthermore, the service provider 500 may display the breakdown of electronic money linked to the corporate account separately as the balance of the main wallet and the balance of the sub-wallet (or the balance of each sub-wallet if there are multiple sub-wallets).

[0187] Furthermore, the service provider 500 may, in response to a request from a service user, display a list of charge instructions that have not been processed due to insufficient balance, along with information indicating the specified charge amount and the charge destination. Figure 15 shows an example of a charge instruction list according to another embodiment. For example, the service provider 500 can provide the unfilled charge instruction list shown in Figure 15 in response to a request from a service user. For example, the unfilled charge instruction list shown in Figure 15 includes information indicating the date the charge instruction was received, information indicating the service to which the charge is to be placed, and information indicating the specified charge amount. The service provider 500 may also include information indicating the scheduled date of charge execution in the unfilled charge instruction list.

[0188] (5-2. Example of device configuration) The following describes an example configuration of a service provision device 500 according to another embodiment. Figure 16 is a diagram showing an example configuration of a service provision device according to another embodiment.

[0189] As shown in Figure 16, the service provision device 500 according to another embodiment includes a communication unit 510, a storage unit 520, and a control unit 530.

[0190] The communication unit 510 corresponds, for example, to the communication unit 410 of the service provision device 400 according to a modified example. The communication unit 510 transmits and receives information with the carrier X system SYS-1, the A bank system SYS-2, the B bank system SYS-3, etc., via the network N-1. The network N-1 is a WAN (Wide Area Network) such as the Internet. Note that the network N-1 may also include communication networks such as a LAN (Local Area Network), a telephone network (for example, a mobile phone network or a fixed telephone network), or a regional IP (Internet Protocol) network. The network N-1 may include a wired network or a wireless network.

[0191] The storage unit 520 corresponds to, for example, the storage unit 420 of the modified service provision device 400, and stores programs and data used for control and calculation by the control unit 530. As shown in Figure 16, the storage unit 520 includes an account information storage unit 521, a bank account information storage unit 522, a charge instruction information storage unit 523, a charge history storage unit 524, and a balance information storage unit 525.

[0192] The account information storage unit 521 corresponds, for example, to the account information storage unit 321 of the storage unit 420 described above. The account information storage unit 522 corresponds to the account information storage unit 422 of the storage unit 420 described above. The charge instruction information storage unit 523 corresponds to the charge instruction information storage unit 423 of the storage unit 420 described above. The charge history storage unit 524 corresponds to the charge history storage unit 424 of the storage unit 420 described above. In addition to the information stored by the charge history storage unit 424 of the storage unit 420 described above, the charge history storage unit 524 may also store the deposit and withdrawal history (balance history) of each sub-wallet for each sub-wallet of each service user using a corporate account. For example, the charge history storage unit 524 can further store information such as the date on which the deposit and withdrawal were made, the time on which the deposit and withdrawal were made, the type of deposit and withdrawal, the destination, the source of the deposit, the amount of the deposit and withdrawal, and the date of the charge if the deposit and withdrawal type is a charge.

[0193] The balance information storage unit 525 stores balance information including the total balance of electronic money associated with the corporate account, the amount of money that has been used, and the amount of money that remains unused. Figure 17 is a diagram showing an example of balance information according to another embodiment. Note that Figure 17 is an example of balance information according to another embodiment and is not limited to the example shown in Figure 17. For example, the balance information may be stored by dividing the electronic money associated with the corporate account into the balance of the main wallet and the balance of the sub-wallet (or the balance of each sub-wallet if there are multiple sub-wallets).

[0194] As shown in Figure 17, the balance information stored in the balance information storage unit 525 includes the fields "User ID," "Total Balance," and "Balance Breakdown." These fields in the balance information are interconnected.

[0195] The "User ID" field stores the user ID (identification information) that was individually assigned to a corporation such as business operator X as a service user when registering to use various services provided by business operator Y. The "Total Balance" field stores information showing the total balance of electronic money linked to the corporate account. The "Balance Breakdown" field has two sections: "Applied" and "Unapplied". The "Applied" section stores information showing the money balance applied to charge instruction transactions. The "Unapplied" section stores information showing the money balance that has not been applied to charge instruction transactions.

[0196] The control unit 530 corresponds to, for example, the control unit 430 of the modified service provision device 400, and is a controller that performs control and calculations for the service provision device 500. As shown in Figure 16, the control unit 530 includes a reception unit 531, an allocation processing unit 532, a transfer processing unit 533, a display control unit 534, a balance processing unit 535, a disbursement unit 536, a provision unit 537, and a management unit 538.

[0197] The reception unit 531 executes processing functions corresponding to the reception unit 431 and management unit 432 of the control unit 430 described above. For example, the reception unit 531 receives instructions from service users, such as business operator X, to charge electronic money related to services used by service users, via the communication unit 510.

[0198] Furthermore, when the reception unit 531 receives a deposit notification from a partner financial institution via the communication unit 510, which has been executed in response to a deposit instruction from a service user, it adds the electronic money equivalent to the deposited amount to the balance of the main wallet (for example, the main wallet for salaries or the main wallet for non-salary transactions shown in Figure 11) held by the corporate account corresponding to the service user who made the deposit. Note that the deposit notification is not limited to notifications from partner financial institutions, as long as it confirms that a deposit has been made by the service user.

[0199] Furthermore, the reception unit 531 can provide service users with an operation screen (see, for example, Figures 12 and 13) for accepting balance transfer operations.

[0200] The allocation processing unit 532 executes processing functions corresponding to the allocation unit 433 of the control unit 430 described above. That is, the allocation processing unit 532 performs a balance transfer from the main wallet to the sub-wallet based on a transfer instruction received from the service user through an operation screen provided to the service user by the reception unit 131 (see, for example, Figures 12 and 13), and the information processing system SYS allocates the specified amount to the charge instruction transaction based on the charge instruction. For example, if there is a money balance linked to a corporate account that has a predetermined purpose of use, the allocation processing unit 532 executes an allocation process to allocate the charge specified amount in the charge instruction for charging. The allocation process by the allocation processing unit 532 may be performed in real time, or it may be performed by periodic balance polling at a predetermined interval.

[0201] Furthermore, when the receiving unit 531 receives a charge instruction for salary, the allocation processing unit 532 executes an allocation process for salary charging from the money balance of the first wallet, provided that the first wallet, which is used when the charge instruction is for salary, has a money balance for salary charging. Specifically, the allocation processing unit 532 executes an allocation process to allocate the money balance of the sub-wallet to the charge instruction transaction for salary charging that has not yet been allocated, provided that the sub-wallet, which is capable of transferring balances with the main wallet and accepts allocation of charge instruction amounts, has a money balance for salary charging. Similarly, when the receiving unit 531 receives a charge instruction for something other than salary, the allocation processing unit 532 executes an allocation process for charges other than salary charging from the money balance of the second wallet, provided that the second wallet, which is used when the charge instruction is for something other than salary, has a money balance for charges other than salary charging. Note that the user agreement for using the salary charging service and the user agreement for using the money charging service, which are concluded by the service user, are separate and independent contracts. Therefore, if a service user has contracts for both services, for example, a charge instruction sent by the service user for the purpose of salary will include a contract identifier to prove the existence of a contract for the salary charge service. When the allocation processing unit 532 receives a charge instruction from a service user for the purpose of salary, it executes the allocation process on the condition that a formal contract for the salary charge service is confirmed based on the contract identifier included in the charge instruction. However, even if the contract identifier included in the charge instruction is a contract identifier to prove the existence of a contract for the salary charge service, if the charge instruction is for a purpose other than salary, the charge instruction will not be accepted and an error response will be given.

[0202] The transfer processing unit 533 executes processing functions corresponding to the charge unit 434 of the control unit 430 described above. For example, when the charge execution date specified in the charge instruction arrives, the transfer processing unit 533 executes a transfer process to transfer the electronic money corresponding to the specified charge amount allocated for the charge to another account that will be the charge destination.

[0203] The display control unit 534 displays balance information, including the total balance of electronic money linked to the corporate account at the current time, the balance of money used in charge instruction transactions, and the balance of money not used in charge instruction transactions, in response to a request from a service user. The display control unit 534 can also display a list of charge instructions for which the payment process has not been completed due to insufficient funds, along with information indicating the specified charge amount and the charge destination.

[0204] The balance processing unit 535 accepts transfer requests from other accounts to the corporate account and adds the electronic money corresponding to the specified amount specified in the transfer request to the balance of the corporate account's wallet. For example, the balance processing unit 535 can transfer the balance of a sub-wallet for non-salary payments (see, for example, sub-wallet 2 shown in Figure 13) that has been deposited via the C2B transfer service to the main wallet for non-salary payments (see, for example, Figure 13).

[0205] The payout unit 536 corresponds to the payout unit 435 of the control unit 430 described above, and pays out the remaining balance of digital money that was not used for the charge instruction transaction to the service user according to a predetermined payout cycle.

[0206] The provisioning unit 537 corresponds to the provisioning unit 436 of the control unit 330 described above, and in response to a request from a service user, it provides detailed information (see, for example, Figure 2) relating to the charging of digital money performed in response to a charge instruction.

[0207] The management unit 538 manages corporate accounts that have sub-wallets set up for each of the multiple services used by the service user. For example, the management unit 538 manages a first main wallet (for example, the salary main wallet shown in Figure 11) used when the charge instruction received from the service user is for salary, and associates it with sub-wallets that can receive balance transfers from the first main wallet. Also, for example, the management unit 538 manages a second main wallet (for example, the non-salary main wallet shown in Figure 11) used when the charge instruction is for something other than salary, and associates it with sub-wallets corresponding to each of the multiple services that can receive balance transfers from the second main wallet.

[0208] Furthermore, the management unit 538 may display the balance of each sub-wallet, which is provided for each of the multiple services separated by the purpose of charging, as a service usage history. For example, the management unit 538 may read and display the deposit and withdrawal history (balance history) of each sub-wallet for each service user using a corporate account from the information stored in the charge history storage unit 524 and provide it to the service user. For example, the information displayed by the management unit 538 may include information such as the date the deposit or withdrawal was made, the time the deposit or withdrawal was made, the type of deposit or withdrawal, the destination, the source of the deposit, the amount of the deposit or withdrawal, and the date of charging if the deposit or withdrawal type is a charge. This allows the administrator 538 to help service users streamline their accounting processes.

[0209] Furthermore, the management unit 538 may accept and manage the setting of at least one of the following for each service, which is divided according to the purpose of the charge: the number of times a charge instruction can be accepted and the maximum charge amount. In addition to the number of times a charge can be accepted and the maximum amount, the management unit 538 may also accept and manage the setting of the maximum balance to be transferred from the sub-wallet, the timing of the daily batch that transfers the balance remaining in the sub-wallet to the main wallet, and the maximum balance that will remain. In this case, the above-mentioned allocation processing unit 532 and transfer processing unit 533 will execute various processes according to the settings managed for each service by the management unit 538. The entity responsible for these settings may be the service user or the administrator of the information processing system SYS (service provision device 500).

[0210] (5-3. Example of processing procedure) The following describes the processing procedure of the service provision device 500 according to another embodiment, using Figure 18. Figure 18 is a flowchart showing an example of the processing procedure of the service provision device according to another embodiment. The processing procedure shown below is repeatedly executed by the control unit 530 of the service provision device 500.

[0211] As shown in Figure 18, when the reception unit 531 receives a deposit notification from a service user (step S301), it adds the electronic money corresponding to the deposited amount to the balance of the main wallet held by the corporate account corresponding to the service user who made the deposit (step S302).

[0212] Furthermore, the reception unit 531 transfers the balance from the main wallet to the sub-wallet according to the operation performed by the service user (step S303).

[0213] Furthermore, if the allocation processing unit 532 has a money balance linked to the corporate account for which a predetermined purpose of use has been determined, it executes an allocation process to allocate the charge amount specified in the charge instruction for charging (step S304).

[0214] Furthermore, when the charge execution date specified in the charge instruction arrives, the transfer processing unit 533 executes a transfer process to transfer the electronic money corresponding to the specified charge amount used for the charge to another account that will be the charge destination (step S305), and then terminates the processing procedure shown in Figure 18.

[0215] [6. Hardware Configuration] Furthermore, the service provision device 300 according to the above-described embodiment, the modified service provision device 400, or the service provision device 500 according to another embodiment are implemented by a computer 1000 having a configuration such as that shown in Figure 19. Figure 19 is a hardware configuration diagram showing an example of a computer that implements the functions of the service provision device.

[0216] Computer 1000 is connected to an output device 1010 and an input device 1020, and has a configuration in which an arithmetic unit 1030, a primary storage device 1040, a secondary storage device 1050, an output interface 1060, an input interface 1070, and a network interface 1080 are connected by a bus 1090.

[0217] The arithmetic unit 1030 operates based on programs stored in the primary storage device 1040 and the secondary storage device 1050, as well as programs read from the input device 1020, and executes various processes. The primary storage device 1040 is a memory device, such as RAM, that temporarily stores data used by the arithmetic unit 1030 for various calculations. The secondary storage device 1050 is a storage device where data used by the arithmetic unit 1030 for various calculations and various databases are registered, and is implemented using ROM (Read Only Memory), HDD, flash memory, etc.

[0218] Output IF1060 is an interface for transmitting information to be output to output devices 1010, such as monitors and printers, and is implemented using connectors of standards such as USB (Universal Serial Bus), DVI (Digital Visual Interface), and HDMI (High Definition Multimedia Interface). Input IF1070 is an interface for receiving information from various input devices 1020, such as mice, keyboards, and scanners, and is implemented using, for example, USB.

[0219] The input device 1020 may also be a device that reads information from, for example, an optical recording medium such as a CD (Compact Disc), DVD (Digital Versatile Disc), or PD (Phase Change Rewritable Disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), tape media, magnetic recording media, or semiconductor memory. Furthermore, the input device 1020 may be an external storage medium such as a USB memory stick.

[0220] Network IF1080 receives data from other devices via network N and sends it to the arithmetic unit 1030, and also transmits data generated by the arithmetic unit 1030 to other devices via network N.

[0221] The arithmetic unit 1030 controls the output device 1010 and the input device 1020 via the output IF 1060 and the input IF 1070. For example, the arithmetic unit 1030 loads a program from the input device 1020 or the secondary storage device 1050 onto the primary storage device 1040 and executes the loaded program.

[0222] For example, when the computer 1000 functions as a service provider 300, which is an example of an information processing device according to the embodiment, the arithmetic unit 1030 of the computer 1000 realizes the same functions as the control unit 330 by executing a program (for example, an information processing program) loaded on the primary storage device 1040. That is, the arithmetic unit 1030 realizes the processing by the service provider 300 according to the embodiment through cooperation with the program (for example, an information processing program) loaded on the primary storage device 1040.

[0223] Furthermore, when the computer 1000 functions as a service provider 400 according to an example of an information processing device related to a modified model, the arithmetic unit 1030 of the computer 1000 realizes the same functions as the control unit 430 by executing a program (for example, an information processing program) loaded onto the primary storage device 1040. In other words, the arithmetic unit 1030 realizes processing by the service provider 400 according to the modified model through cooperation with the program (for example, an information processing program) loaded onto the primary storage device 1040.

[0224] Furthermore, when the computer 1000 functions as a service provider 500 according to an example of an information processing device according to another embodiment, the arithmetic unit 1030 of the computer 1000 realizes the same functions as the control unit 530 by executing a program (for example, an information processing program) loaded on the primary storage device 1040. In other words, the arithmetic unit 1030 realizes the processing by the service provider 500 according to the other embodiment through cooperation with the program (for example, an information processing program) loaded on the primary storage device 1040.

[0225] [7. Effects] As described above, the service provision device 500, which is an example of an information processing device according to another embodiment, has a reception unit 531, a payment processing unit 532, and a transfer processing unit 533. The reception unit 531 receives a charge instruction for electronic money related to the service used by the service user from the service user. The payment processing unit 532, if there is a money balance linked to the corporate account for which the purpose of use has been predetermined by the charge instruction, executes a payment processing operation to allocate the specified charge amount specified in the charge instruction for charging. When the charge execution date specified in the charge instruction arrives, the transfer processing unit 533 executes a transfer processing operation to transfer the electronic money corresponding to the specified charge amount allocated for charging to another account that will be used as the charging destination.

[0226] Furthermore, the aforementioned corporate account has a first wallet used when the charge instruction is for salary, and a second wallet used when the charge instruction is for something other than salary. When the receiving unit 531 receives a charge instruction for salary, the allocation processing unit 532 executes an allocation process for salary charging from the money balance of the first wallet, provided that the first wallet has a money balance for which the purpose of use has been predetermined. Also, when the receiving unit 531 receives a charge instruction for something other than salary, the allocation processing unit 532 executes an allocation process for charging other than salary charging from the money balance of the second wallet, provided that the second wallet has a money balance for which the purpose of use has been predetermined.

[0227] Furthermore, each of the first and second wallets described above includes a main wallet linked to a bank account used for deposits and withdrawals, and a sub-wallet that allows balance transfers between the main wallet and the sub-wallet and accepts the application of charge instruction amounts. The application processing unit 532 executes an application process to apply the money balance of the sub-wallet to unapplication charge instruction transactions, provided that the sub-wallet has a money balance for which a predetermined purpose of use has been determined.

[0228] Furthermore, the reception unit 531 transfers the balance from the main wallet to the sub-wallet according to the operation performed by the service user.

[0229] Thus, the service provider 500 according to the other embodiment can, through the processing performed by each of the above-described parts, or any combination of each of the parts, transfer the money balance allocated to a charge instruction transaction to another account that is the charge destination, in accordance with the operation of the service user, and provide various services related to money transfer business in compliance with relevant laws and regulations.

[0230] Furthermore, the service provision device 500 according to another embodiment further includes a display control unit 534 that, in response to a request from a service user, displays information indicating the total balance of electronic money linked to the corporate account at the present time, the money balance used for charge instruction transactions, and the money balance not used for charge instruction transactions.

[0231] Furthermore, the display control unit 534 displays a list of charge instructions for which the top-up process has not been completed due to insufficient balance, along with information indicating the specified charge amount and the charge destination.

[0232] Furthermore, a service provision device 500 according to another embodiment further includes a balance processing unit 535 that receives a transfer request from another account to a corporate account and adds the electronic money corresponding to the specified amount specified in the transfer request to the balance of the wallet held by the corporate account.

[0233] Thus, the service provision device 500 according to other embodiments can provide various services related to money transfer services in compliance with relevant laws and regulations, while improving the usability for service users, through the processing performed by each of the above-described parts, or any combination of each of the parts.

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

[0235] Furthermore, the service provision devices 300, 400, or 500 described above can be flexibly configured to implement functions by calling external platforms via APIs (Application Programming Interfaces) or network computing. In addition, each processing function for executing information processing according to other embodiments, which is centralized in the service provision device 500, may be distributed to multiple systems as needed. For example, among the processing functions provided by the service provision device 500, functions such as managing the money balance linked to a corporate account, or functions for adding and withdrawing balances allocated to charge instruction transactions, can be distributed to other systems, allowing for the configuration of information processing systems SYS-5 according to other embodiments at any unit.

[0236] Furthermore, the term "part" in the claims can be replaced with "means," "circuit," etc. For example, "control unit" can be replaced with "control means" or "control circuit."

[0237] Furthermore, the effects described in the embodiments of this application are merely descriptive or illustrative and not limiting. In other words, the embodiments of this application may produce other effects that are obvious to those skilled in the art from the description of the embodiments, in addition to or instead of the effects described above. [Explanation of Symbols]

[0238] 100 Management Systems 200 Charge System 300 Service Provisioning Devices 310 Communications Department 320 Storage section 321 Account Information Storage Unit 322 Charge history storage unit 330 Control Unit 331 Reception Department 332 Allocation Section 333 Dispensing Section 334 Providing Department 400 Service Provisioning Devices 410 Communications Department 420 Storage section 421 Account Information Storage Unit 422 Account Information Storage Unit 423 Charge instruction information storage unit 424 Charge history storage unit 430 Control Unit 431 Reception Department 432 Management Department 433 Allocation Section 434 Charging section 435 Dispensing section 436 Providing Department 500 Service Providers 510 Communications Department 520 Storage section 521 Account Information Storage Unit 522 Account Information Storage Unit 523 Charge instruction information storage unit 524 Charge history storage unit 525 Balance Information Storage Unit 530 Control Unit 531 Reception Department 532 Allocation Processing Unit 533 Transition Processing Unit 534 Display Control Unit 535 Balance Processing Unit 536 Dispensing section 537 Providing Department 538 Management Department

Claims

1. An information processing device for managing corporate accounts individually assigned to service users, The aforementioned corporate account includes a main wallet and a sub-wallet, The main wallet allows for the transfer of electronic money between it and the sub-wallet. The aforementioned sub-wallet is linked to the services that the electronic payment service provides to the aforementioned corporate account. In response to a charge instruction from the service user, the planned charge amount to be used for the charge instruction transaction is allocated to the sub-wallet corresponding to the service used by the service user. An information processing device characterized by the following:

2. The service is This includes a charge service for transferring funds from the aforementioned corporate account to other accounts, and a C2B remittance service for accepting deposits from other accounts to the aforementioned corporate account. The information processing apparatus according to feature 1.

3. The sub-wallet is The service is provided per contract unit for the charge service by the service user. The information processing apparatus according to feature 2.

4. When a charge instruction is received from a service user under the name of the first charge service, the planned charge amount to be used for the charge instruction transaction will be allocated to the sub-wallet established for the first charge service, provided that the formal usage agreement for the first charge service is confirmed based on the contract identifier included in the charge instruction. The information processing apparatus according to feature 1.

5. Display the deposit and withdrawal history for each of the aforementioned subwallets. The information processing apparatus according to feature 1.

6. The aforementioned corporate account is The main wallet used when the charge instruction is for salary, and the main wallet used when the charge instruction is for something other than salary. The information processing apparatus according to feature 1.

7. An information processing method performed by a computer that manages corporate accounts individually assigned to service users, The aforementioned corporate account includes a main wallet and a sub-wallet, The main wallet allows for the transfer of electronic money between it and the sub-wallet. The aforementioned sub-wallet is linked to the services that the electronic payment service provides to the aforementioned corporate account. The process of allocating the planned charge amount to be used for the charge instruction transaction to the sub-wallet corresponding to the service used by the service user, in response to a charge instruction from the service user. An information processing method characterized by including

8. An information processing program that causes a computer that manages corporate accounts individually assigned to service users to execute a predetermined processing procedure, The aforementioned corporate account includes a main wallet and a sub-wallet, The main wallet allows for the transfer of electronic money between it and the sub-wallet. The aforementioned sub-wallet is linked to the services that the electronic payment service provides to the aforementioned corporate account. A procedure for allocating the planned charge amount to be used for the charge instruction transaction to the sub-wallet corresponding to the service used by the service user, in response to a charge instruction from the service user. An information processing program characterized by causing the computer to execute the following.

Images