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

Abstract

To promote use of services related to digital money.SOLUTION: An information processing device includes a reception part and an allocation part. The reception part receives charge instructions of digital money from a service user. The allocation part after the charge instructions are received, allocates a scheduled charge amount specified in the charge instructions, on the condition that deposit of the capital to be applied to a charge instruction transaction in accordance with the charge instructions is confirmed.SELECTED DRAWING: Figure 3

Description

Technical Field

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

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 increasingly penetrating 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.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, the conventional technology has room for improvement in promoting the use of services related to digital money.

[0006] The present application has been made in view of the above, and an object thereof is to provide an information processing apparatus, an information processing method , love information processing program , and information processing systems that can promote the use of services related to digital money.

Means for Solving the Problems

[0007] The information processing device according to the present application comprises a reception unit and an allocation unit. The reception unit receives digital money charge instructions from service users. After receiving a charge instruction, the allocation unit, on the condition that the deposit of funds to be used for the charge instruction transaction corresponding to the charge instruction is confirmed, executes the allocation of the planned charge amount specified in the charge instruction. [Effects of the Invention]

[0008] According to one embodiment, the effect is to promote the use of services related to digital money. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 is a diagram illustrating the overview of the information processing according to this embodiment. [Figure 2] Figure 2 is a diagram illustrating the overview of the information processing according to this embodiment. [Figure 3] Figure 3 is a block diagram showing an example configuration of the business operator Y system according to this embodiment. [Figure 4] Figure 4 shows an overview of the account information according to this embodiment. [Figure 5] Figure 5 shows an overview of the charge instruction information according to this 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 this embodiment. [Figure 8] Figure 8 is a sequence diagram showing the overall processing flow in the information processing system according to this embodiment. [Figure 9] Figure 9 is a flowchart showing an example of the processing procedure of the service provision device according to this embodiment. [Figure 10] Figure 10 shows an example of the configuration of a service provision device according to a modified example. [Figure 11]FIG. 11 is a hardware configuration diagram showing an example of a computer that realizes the functions of the service providing apparatus according to the present embodiment or a modified example.

Embodiments for Carrying Out the Invention

[0010] Hereinafter, an information processing apparatus, an information processing method , love information processing program , and information processing systems according to the present application will be described in detail with reference to the drawings in the form for carrying them out (hereinafter referred to as "the present embodiment"). Note that the information processing apparatus, the information processing method , love information processing program , and information processing systems according to the present application are not limited thereto. Further, in the following embodiments, the same parts are denoted by the same reference numerals, and redundant descriptions are omitted.

[0011] 〔1. An Example of Information Processing According to the Present Embodiment〕 Hereinafter, an example of information processing according to the present embodiment will be described with reference to FIGS. 1 and 2. FIGS. 1 and 2 are diagrams showing the outline of the information processing according to the present embodiment.

[0012] As shown in FIG. 1, the information processing system SYS according to the present 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 present embodiment, and it may include business management systems operated and managed by other business operators not shown in FIG. 1.

[0013] 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.

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

[0015] The system of Business Operator X, SYS-1 is, for example, a business management system operated and managed by Business Operator X engaged in a predetermined business. The system of Business Operator X, SYS-1 is realized, for example, by a single server device or workstation, a cloud system in which a plurality of server devices and a plurality of storage devices cooperate to operate, etc. Note that Business Operator X may use, instead of the system of Business Operator X, SYS-1, an information processing device such as a smartphone, a tablet-type terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), a wearable terminal, etc.

[0016] Also, when the system of Business Operator X, SYS-1 receives control information for realizing predetermined information processing from the system of Business Operator Y, SYS-4, it realizes the information processing according to the control information. Here, the control information is described, for example, by a script language such as JavaScript (registered trademark), a style sheet language such as CSS (Cascading Style Sheets), a programming language such as Java (registered trademark), a markup language such as HTML (HyperText Markup Language), etc. Note that in the present embodiment, a predetermined application itself distributed from the system of Business Operator Y, SYS-4 may be regarded as the control information.

[0017] 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.

[0018] 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.

[0019] 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.

[0020] 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 this 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.

[0021] 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.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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 digital money, such as service users or stores. That is, the various services according to this 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 other various 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.

[0026] 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.

[0027] 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.

[0028] 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.

[0029] 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.

[0030] 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).

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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).

[0038] 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).

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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."

[0047] 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.

[0048] 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".

[0049] 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.

[0050] 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.

[0051] 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 this 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.

[0052] 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.

[0053] 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.

[0054] 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).

[0055] 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.

[0056] 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.

[0057] 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.

[0058] 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.

[0059] 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.

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

[0061] 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.

[0062] 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.

[0063] 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.

[0064] (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 this embodiment.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] 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.

[0069] 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.

[0070] 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.

[0071] 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.

[0072] (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 illustrating an overview of the charge instruction information according to this embodiment.

[0073] 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.

[0074] 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.

[0075] 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.

[0076] 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.

[0077] 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)."

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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".

[0082] (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.

[0083] (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).

[0084] (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.

[0085] (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 this embodiment. Note that Figure 6 shows an example of account information according to this embodiment, and may be configured in a different form than the example shown in Figure 6.

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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.

[0090] 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.

[0091] 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.

[0092] 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".

[0093] (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 this embodiment. Note that Figure 7 shows an example of the charge history according to this embodiment, and the system may be configured in a different form than the example shown in Figure 7.

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

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

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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.

[0104] 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.

[0105] 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.

[0106] (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).

[0107] 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.

[0108] (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.

[0109] (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.

[0110] 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.

[0111] 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.

[0112] 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.

[0113] (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.

[0114] 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".

[0115] (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.

[0116] 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.

[0117] 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.

[0118] 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.

[0119] [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.

[0120] 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).

[0121] 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).

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

[0123] 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).

[0124] 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).

[0125] 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).

[0126] 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).

[0127] 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).

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

[0129] 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.

[0130] (3-2. Processing of service provision equipment) Next, the processing procedure by the service provision device 300 according to this 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 this embodiment. The processing procedure shown below is repeatedly executed by the control unit 330 of the service provision device 300.

[0131] 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).

[0132] 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).

[0133] 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).

[0134] 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).

[0135] 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.

[0136] 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.

[0137] 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.

[0138] 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).

[0139] 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.

[0140] 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.

[0141] [4. Variations] The embodiment described above is merely an example of information processing according to this embodiment, 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 the 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 modified service provision device.

[0142] 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.

[0143] 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.

[0144] 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.

[0145] 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.

[0146] 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).

[0147] 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).

[0148] 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.

[0149] 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.

[0150] 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.

[0151] 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.

[0152] 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.

[0153] 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.

[0154] 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.

[0155] 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.

[0156] 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.

[0157] 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.

[0158] 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.

[0159] In this way, by consolidating the various parts 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, enabling efficient processing. Furthermore, the deployment of a network N-2 that connects the various parts of the operator Y system SYS-4 according to the above embodiment in a communicative manner becomes unnecessary, eliminating the impact of communication failures on network N-2 on service provision.

[0160] [5. Hardware Configuration] Furthermore, the service provision device 300 according to this embodiment, or the modified service provision device 400, described above, is implemented by a computer 1000 having the configuration shown in Figure 11, for example. Figure 11 is a hardware configuration diagram showing an example of a computer that implements the functions of the service provision device according to this embodiment or a modified version.

[0161] 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.

[0162] 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.

[0163] 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.

[0164] 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.

[0165] 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.

[0166] 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.

[0167] For example, when the computer 1000 functions as a service provider 300, which is an example of an information processing device according to this 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 this embodiment in cooperation with the program (for example, an information processing program) loaded on the primary storage device 1040.

[0168] 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.

[0169] [6. Effects] As described above, the service provision device 300, which is an example of an information processing device according to this embodiment, has a reception unit 331 and an allocation unit 332. The reception unit 331 receives a digital money charge instruction from a service user. After the charge instruction is received, the allocation unit 332 executes the allocation of the planned charge amount specified in the charge instruction transaction, on the condition that the deposit of funds to be used for the charge instruction transaction corresponding to the charge instruction is confirmed.

[0170] As a result, the service provider 300 can handle the balance after a charge instruction has been received, thereby ensuring clarity regarding the use of the money allocated to the sub-wallet, and providing various digital money-related services to service users, thereby promoting the use of digital money-related services.

[0171] Furthermore, the allocation unit 332 allocates the planned charge amount to the main wallet linked to the account into which the principal is deposited, on the condition that a predetermined balance equivalent to the principal is added.

[0172] Furthermore, the allocation unit 332 allocates the planned charge amount from a predetermined balance to the sub-wallet corresponding to the name of the charge specified in the charge instruction.

[0173] As a result, the service provider 300 can electronically manage information related to the charging of digital money through the main wallet and sub-wallet linked to the service user.

[0174] Furthermore, the service provider 300 has a payout unit 333 that pays out the balance of the main wallet that was not used for charge instruction transactions to the service user according to a predetermined payout cycle. As a result, the service provider 300 can provide various digital money services to service users while complying with retention regulations, and can promote the use of digital money services.

[0175] Furthermore, the service provider 300 has a provision unit 334 that provides detailed information regarding the charging of digital money performed in response to a charge instruction, upon request from the service user. This allows the service provider 300 to allow the service user to understand the flow of deposits and withdrawals related to the charge instruction in detail, thereby promoting the use of digital money services.

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

[0177] Furthermore, the service provision device 300 or service provision device 400 described above can be flexibly configured to implement functions by calling external platforms via APIs (Application Programming Interfaces) or network computing.

[0178] 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."

[0179] 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]

[0180] 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 Provision Department

Claims

1. A reception desk that receives digital money top-up instructions from service users, When the service user receives a deposit notification indicating that funds have been deposited into a virtual account linked to the main wallet used for depositing and withdrawing the digital money, the allocation unit executes the allocation of the planned charge amount specified in the charge instruction, A charge unit executes a process to charge the digital money corresponding to the planned charge amount allocated by the allocation unit to the money account linked to the account specified in the charge instruction. It has, The aforementioned allocation unit is The amount of the planned charge will be allocated from a predetermined balance equivalent to the source of funds to the sub-wallet corresponding to the charge name specified in the charge instruction. An information processing device characterized by the following:

2. The payout unit pays out the balance of the main wallet that was not used for the charge instruction transaction, from the predetermined balance, to the service user according to a predetermined payout cycle. The information processing apparatus according to claim 1, further comprising the above.

3. A service provider that, in response to a request from the service user, provides detailed information regarding the charging of digital money performed in accordance with the charge instruction. The information processing apparatus according to claim 1 or 2, further comprising the above.

4. A method of information processing performed by a computer, The process of receiving instructions from service users to charge digital money, When the service user receives a deposit notification indicating that funds have been deposited into a virtual account linked to the main wallet used for depositing and withdrawing the digital money in response to the charge instruction, the allocation process executes the allocation of the planned charge amount specified in the charge instruction. A charge step which executes the process of charging the digital money corresponding to the planned charge amount allocated in the allocation step to the money account linked to the account to be charged as specified in the charge instruction. Includes, The aforementioned allocation process is, The amount of the planned charge will be allocated from a predetermined balance equivalent to the source of funds to the sub-wallet corresponding to the charge name specified in the charge instruction. An information processing method characterized by the following:

5. The procedure for receiving digital money top-up instructions from service users, When the service user receives a deposit notification indicating that funds have been deposited into a virtual account linked to the main wallet used for depositing and withdrawing the digital money in response to the charge instruction, an allocation procedure is performed to allocate the planned charge amount specified in the charge instruction. A charge procedure that executes the process of charging the digital money corresponding to the planned charge amount allocated by the allocation procedure to the money account linked to the account to which the charge is to be placed, as specified in the charge instruction. Have the computer run it, The aforementioned assignment procedure is: The amount of the planned charge will be allocated from a predetermined balance equivalent to the source of funds to the sub-wallet corresponding to the charge name specified in the charge instruction. An information processing program characterized by the following features.

6. An information processing system including a charging system and a service provision device, The service provision device, The service accepts requests from users to top up their digital money. When the service user receives a deposit notification indicating that funds have been deposited into a virtual account linked to the main wallet used for depositing and withdrawing the digital money in response to the charge instruction, the service user shall allocate the planned charge amount from a predetermined balance equivalent to the funds to the sub-wallet corresponding to the name of the charge specified in the charge instruction. The aforementioned charging system The service provider executes a process to charge the digital money corresponding to the scheduled charge amount allocated by the service provider to the money account linked to the account specified in the charge instruction. An information processing system characterized by the following:

Images