JP7764349B2 - Information processing device, information processing method, information processing program, and information processing system - Google Patents

Description

The present invention relates to an information processing device, an information processing method , an information processing program , and an information processing system .

Traditionally, cashless payment methods have been widely recognized by consumers, primarily for commercial transactions between companies and individuals. However, due to their convenience, electronic payment services that are conducted online using personal devices such as smartphones are becoming increasingly popular among consumers.

In addition, the government has recently been considering introducing so-called "digital salary payments" to these electronic payment services, which would allow salaries to be paid using digital money such as electronic money or virtual currency, and digital money services are expected to become even more widespread.

Japanese Patent Application Laid-Open No. 2007-328549

However, existing technologies have room for improvement in promoting the use of digital money services.

The present application has been made in view of the above, and aims to provide an information processing device, an information processing method , an information processing program , and an information processing system that can promote the use of services related to digital money.

The information processing device according to the present application has a reception unit and a disbursement unit. The reception unit receives a digital money charge instruction from a service user. The disbursement unit pays out the remaining digital money that has not been applied to the charge instruction transaction in accordance with the charge instruction to the service user in accordance with a predefined disbursement cycle.

One aspect of this embodiment has the effect of promoting the use of digital money-related services.

FIG. 1 is a diagram showing an overview of information processing according to this embodiment. FIG. 2 is a diagram showing an overview of information processing according to this embodiment. FIG. 3 is a block diagram showing an example of the configuration of the provider Y system according to this embodiment. FIG. 4 is a diagram showing an outline of account information according to this embodiment. FIG. 5 is a diagram showing an outline of charge instruction information according to this embodiment. FIG. 6 is a diagram showing an outline of the account information stored in the account information storage unit according to this embodiment. FIG. 7 is a diagram showing an outline of the charge history stored in the charge history storage unit according to this embodiment. FIG. 8 is a sequence diagram showing the overall processing flow in the information processing system according to this embodiment. FIG. 9 is a flowchart showing an example of a processing procedure of the service providing device according to this embodiment. FIG. 10 is a diagram illustrating an example of the configuration of a service providing device according to a modified example. FIG. 11 is a hardware configuration diagram showing an example of a computer that realizes the functions of the service providing device according to this embodiment or the modification.

Hereinafter, an information processing device, an information processing method , an information processing program , and an information processing system according to the present application (hereinafter referred to as "the present embodiment") will be described in detail with reference to the drawings. Note that the information processing device, the information processing method , the information processing program , and the information processing system according to the present application are not limited to the present embodiment. Furthermore, the same components in the following embodiments will be denoted by the same reference numerals, and duplicated descriptions will be omitted.

1. An example of information processing according to this embodiment
An example of information processing according to this embodiment will be described below with reference to Figures 1 and 2. Figures 1 and 2 are diagrams showing an overview of information processing according to this embodiment.

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

In the following explanation, Business Operator X's system SYS-1 may be referred to as Business Operator X, Bank A's system SYS-2 may be referred to as "Bank A", and Bank B's system SYS-3 may be referred to as "Bank B".

Business operator X system SYS-1, Bank A system SYS-2, Bank B system SYS-3, and Business operator Y system SYS-4 are connected to network N-1 (see, for example, Figure 3). Business operator X system SYS-1, Bank A system SYS-2, Bank B system SYS-3, and Business operator Y system SYS-4 can communicate with each other via network N-1.

The business operator X system SYS-1 is, for example, a business management system operated and managed by business operator X, which operates a specific business. The business operator X system SYS-1 is realized, for example, by a single server device or workstation, or a cloud system in which multiple server devices and multiple storage devices operate in cooperation with each other. Instead of the business operator X system SYS-1, business operator X may also use information processing devices such as smartphones, tablet devices, notebook PCs (Personal Computers), desktop PCs, mobile phones, PDAs (Personal Digital Assistants), and wearable devices.

Furthermore, when provider X system SYS-1 receives control information for implementing specified information processing from provider Y system SYS-4, it implements the information processing in accordance with the control information. Here, the control information is written in, for example, a scripting language such as JavaScript (registered trademark), a style sheet 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). Note that in this embodiment, the specified application itself distributed from provider Y system SYS-4 may also be considered to be control information.

Bank A system SYS-2 is a bank system operated and managed by Bank A, one of Business Operator X's banks. Bank A system SYS-2 is realized, for example, by a single server device or workstation, or a cloud system in which multiple server devices and multiple storage devices operate in cooperation with each other.

Bank B System SYS-3 is a bank system operated and managed by Bank B, one of the banks that Business Y, described below, handles. Bank B System SYS-3 can be realized, for example, by a single server device or workstation, or a cloud system in which multiple server devices and multiple storage devices operate in cooperation with one another.

For example, Bank A system SYS-2 and Bank B system SYS-3 manage, as bank account usage history, information regarding withdrawals from bank accounts by each card company and various service providers (e.g., the amount withdrawn, the date and time of withdrawal, etc.), current account information (e.g., account balance), etc., in association with bank users. It should be noted that bank users may also be users of various digital money-related services provided by Business Y.

Business operator Y system SYS-4 is a business management system operated and managed by business operator Y, which operates a business that provides various services related to digital money. Business operator Y system SYS-4 includes a management system 100 that manages digital money balances, a charging system 200 that executes digital money charging processes, and a service providing device 300, which is an example of an information processing device related to this embodiment. Note that Figure 1 shows an example of business operator Y system SYS-4, and although explanation is omitted, it may also include a payment system (e.g., a server device) that executes payment processing for payment methods and payment services.

The management system 100, charging system 200, and service providing device 300 may be realized by a single server device or workstation, or a cloud system in which multiple server devices and multiple storage devices operate in cooperation with each other.

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 transaction objects, and individual users such as general consumers who receive transaction objects from businesses, etc.

The charging system 200 realizes money charging by transferring digital money between money accounts in accordance with charging instructions from service users. Note that digital money may be, for example, points or currencies used independently by various companies, or it may be electronically tradable currencies provided by countries, such as Japanese yen or dollars.

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

The various services described above are not limited to payment methods and payment services for providing compensation for the purchase of goods or the provision of services (debt settlement). For example, the various services described above may have a function related to the transfer of funds between accounts held by multiple users. That is, 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 a service user or a store. That is, the various services related to this embodiment may be provided in any form as long as they are transaction methods or transaction services that perform various controls for realizing the exchange of digital money (not only various inter-account transfer controls via electronic money, but also control related to transactions between electronic money accounts and bank accounts, various debt processing such as installment payments and bonus payments, and various controls related to the exchange of assets including electronic money). Furthermore, the various controls realized by such transaction methods and transaction services may include both control related to settlement and control related to remittance, or only one of them. That is, the concept of "transaction" includes not only "payments" related to electronic money, but also "remittances" of electronic money and various other processes. In other words, the service providing device 300 may be an information processing device such as a server device that implements a transaction means for controlling the exchange of electronic money between any owners.

Furthermore, the various digital money services provided by Business Y include a corporate account service that provides service users with a corporate account that is linked one-to-one with an account held by Business Y, and a money charge service that charges digital money to a specified account. These services are provided as an inseparable combination.

A corporate account includes a main wallet and a subwallet linked to the corporate account assigned to the service user. The main wallet accepts digital money deposits (addition to the balance) and digital money withdrawals (payment of the balance). The subwallet accepts allocations of the planned charge amount to be applied to charge instruction transactions in response to charge instructions from the service user. Allocation to charge instruction transactions is performed, for example, on a transaction basis. A charge transaction unit refers to the unit of the money charge service linked to the subwallet in the corporate account. Specifically, a charge instruction is expected to be sent to the service system to which the subwallet is connected (for example, the service system that provides the money charge service linked to the subwallet). In other words, the service system is expected to receive the charge instruction and apply the charge instruction transaction within the subwallet. Therefore, prior to this action (the action of applying the charge instruction transaction within the subwallet), the target amount (the amount specified in the charge instruction) is moved (allocated) from the main wallet to the subwallet. Accordingly, a deposit instruction for the funds to be applied to the charge instruction transaction is also performed on a charge transaction basis.

The money charge service offers a variety of services, including a service that allows service users to pay their employees' salaries in digital money, and a service that allows service users to pay their employees' expenses such as travel expenses and food and drink costs in digital money. Service users can select and use the various money charge services as appropriate. The money charge service selected by the service user is linked to the corporate account provided to the service user.

The following describes the information processing performed by operator Y's system SYS-4, using examples, assuming that operator X is a service user of a service provided by operator Y.

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).

The charge instruction sent by operator X consists of the following fields: "Charge destination ID," "Planned amount," "Planned date," and "Nominal." The "Charge destination ID" field records information indicating the account of the charge destination. The "Planned amount" field records information indicating the planned amount to be charged to the charge destination. The "Planned date" field records information indicating the planned date to charge to the charge destination. The "Nominal" field records information indicating the nominal nature of the charge.

The charge instruction illustrated in Figure 1 includes three charge instructions. For example, the first charge instruction is a charge instruction that specifies the charge destination as account "U#001," the charge name as "salary," the planned charge date as "2021 (year)/9 (Mon)/27 (Sun)," and the planned charge amount as "300,000 yen." The second charge instruction is a charge instruction that specifies the charge destination as account "U#002," the charge name as "salary," the planned charge date as "2021 (year)/9 (Mon)/27 (Sun)," and the planned charge amount as "300,000 yen." The third charge instruction is a charge instruction that specifies the charge destination as account "U#003," the charge name as "expenses," the planned charge date as "2021 (year)/9 (Mon)/30 (Sun)," and the planned charge amount as "400,000 yen." Note that while Figure 1 shows an example in which business operator X requests money charges under multiple names with a single charge instruction, business operator X may also request money charges separately for each name.

On the other hand, when the service providing device 300 receives a charge instruction from business operator X, it registers the received charge instruction in the charge system 200 (step S2). The service providing device 300 can temporarily hold this charge instruction until the charge instruction from business operator X is processed by the charge system 200.

In addition, upon receiving the charge instruction, the service providing device 300 (business operator Y) notifies business operator X, the sender of the charge instruction, of the information (account number) of the one-time account that business operator Y has borrowed from Bank B as the deposit destination for the funds to be applied to the charge instruction transaction. At this time, the service providing device 300 (business operator Y) pre-links 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 under contract in the name of business operator Y. By using this one-time account, the balance that will serve as the funds to be applied to the charge instruction transaction can be deposited by bank transfer. Furthermore, by using the one-time account, business operator Y can easily identify the deposit of the funds corresponding to the charge instruction, thereby streamlining the reconciliation process. Business operator Y may issue an electronic invoice to notify business operator X of the total planned charge amount specified in the charge instruction as the amount required for the money charge, and include information about the one-time account in the issued invoice. Furthermore, if business operator Y is able to borrow multiple one-time accounts from Bank B, it 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 to receive the funds to be used for the charge instruction transaction depending on the specific purpose included in the charge instruction (e.g., salary) and other items, and notify business operator X of different account information. Here, the service providing device 300 uses different one-time accounts and subwallets for each service. For example, if the purpose of the charge instruction is salary (when using a salary charge service), the service providing device 300 uses one-time account AC-1 and subwallet WR-1; if the purpose of the charge instruction is purpose Q other than salary, the service providing device 300 uses one-time account AC-2 and subwallet WR-2; and if the purpose of the charge instruction is purpose R other than salary, the service providing device 300 uses one-time account AC-2 and subwallet WR-3. In other words, if the purpose of the charge instruction is purpose other than salary, the same one-time account AC-2 is used.

Meanwhile, after sending the charge instruction, business operator X sends a deposit instruction to Bank A's system SYS-2 via business operator X's system SYS-1 to deposit the funds to be applied to the charge instruction transaction (step S3). The deposit instruction includes information such as the account number (e.g., "OBAC #111") for identifying the one-time account at Bank B notified by business operator Y as the deposit destination, and the deposit amount (e.g., "1,000,000 yen"). Figure 1 shows an example in which 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 in one lump sum as the funds to be applied to the charge instruction transaction (total amount of the planned charge amount). Note that when business operator X issues a charge instruction for each charge item, it may also deposit the funds to be applied to the charge instruction transaction (total amount of the planned charge amount) sequentially for each charge instruction. For example, business operator X may issue a charge instruction in the name of salary, and then send a deposit instruction to deposit funds (e.g., "600,000 yen") to be applied to the charge instruction transaction in the name of salary. Furthermore, business operator X may issue a charge instruction in the name of expenses, separate from the charge instruction in the name of salary, and after issuing the charge instruction in the name of expenses, send a deposit instruction to deposit funds (e.g., "400,000 yen") to be applied to the charge instruction transaction in the name of expenses.

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 allows the purpose of use of the digital money balance corresponding to the funds deposited by business operator X to be clarified when it is managed in business operator Y's system SYS-4, as described below.

Meanwhile, Bank A's Bank A system SYS-2, in accordance with the deposit instruction received from Business X, deposits the amount specified in the deposit instruction (e.g., "1,000,000 yen") into the one-time account specified in the deposit instruction (e.g., "OBAC#111") (step S4).

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

In addition to the one-time account lent to Business Y, Bank B also lends an account in Business Y's name to Business Y as a deposit destination for the funds to be applied to charge instruction transactions. Some of the accounts lent by Bank B to Business Y have a revolving pledge established on them. This is a measure by which Bank B compensates Business X for the deposit made on behalf of Business Y in the name of salary. When Bank B confirms a deposit into a one-time account in the name of salary (corresponding to a charge instruction transaction in the name of salary), it notifies Business Y of the deposit and then automatically transfers the balance of the one-time account to an account in Business Y's name on which a revolving pledge has been established, and manages the account. When Bank B confirms a deposit into a one-time account in the name of something other than salary (corresponding to a charge instruction transaction in the name of something other than salary), it notifies Business Y and then automatically transfers the balance of the one-time account to an account in Business Y's name on which a revolving pledge has been established, and manages the account. This allows the service providing device 300 to provide stable services while indirectly protecting deposits made by business operator X to an account in the name of business operator Y under a specified name (for example, salary). As a result, the psychological barrier to using business operator X's services can be lowered, and the use of digital money-related services can be promoted.

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 in the deposit notification to Operator X's main wallet (step S6). For example, when the management system 100 receives a deposit notification indicating that 1,000,000 yen has been deposited into a 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 notify the service provider device 300 that the addition (recording) of the balance to the main wallet has been completed.

Meanwhile, after receiving the charge instruction from business operator X, the service providing device 300 allocates the planned charge amount to the sub-wallet, on the condition that the deposit of the funds to be applied to the charge instruction transaction is confirmed (step S7). For example, the service providing device 300 allocates the planned charge amount specified in the charge instruction from a predetermined balance added to the main wallet to the sub-wallet corresponding to the charge name specified in the charge instruction, and moves it to the sub-wallet. Sub-wallets are individually provided corresponding to the money charge services used by business operator X.

Specifically, the service providing device 300 allocates the planned charge amount to the sub-wallet from a predetermined balance, on the condition that a predetermined balance equivalent to the aforementioned funds is added (recorded) to the main wallet linked to the one-time account for which the deposit notification was received. Specifically, in the example shown in FIG. 1, from the balance of 1,000,000 yen added to the main wallet, the service providing device 300 allocates the equivalent of 600,000 yen to the sub-wallet for charging salary money, and the equivalent of 400,000 yen to the sub-wallet for charging expense money. In this way, the service providing device 300 can ensure clarity regarding the use of money allocated to sub-wallets by handling the balance after the charge instruction has been accepted.

Meanwhile, the charging system 200 references the sub-wallet at a predetermined cycle T1, and if allocation to the sub-wallet is confirmed, it allocates the planned charge amount allocated to the sub-wallet to the charge instruction transaction (step S8). Specifically, the charging system 200 allocates the balance in the main wallet to the planned charge amount in order of the charge instructions, starting with those with the nearest planned charge date.

For example, in the example shown in Figure 1, the charging system 200 will first allocate the planned charge amount to a charge instruction in the name of salary with a planned charge date of "2021 (Year)/9 (Mon)/27 (Sun)." If the charging system 200 determines that the balance in the main wallet is less than the planned charge amount, it can suspend 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 charging system 200 locks the amount corresponding to the planned charge amount from the digital money balance in the money account linked to the main wallet, making it untransferable until the charge is executed.

The charging system 200 also executes the charge in accordance with the charge instruction from business operator X (step S9). Specifically, the charging system 200 identifies a money account linked to the account to be charged from among the money accounts managed by the management system 100, and transfers digital money corresponding to the planned charge amount from a money account linked to business operator X's corporate account to the identified money account.

For example, on the planned charge date, "2021 (Year)/9 (Mon)/27 (Sun)", the charging system 200 transfers digital money worth the planned charge amount of "200,000 yen" from the money account of the charging source, business operator X, to the money account linked to the charge destination account, "U#001". Also, on the planned charge date, "2021 (Year)/9 (Mon)/30 (Sun)", the charging system 200 transfers digital money worth the planned charge amount of "250,000 yen" from the money account of the charging source, business operator X, to the money account linked to the charge destination account, "U#002".

The service providing device 300 pays out to business operator X the balance in the main wallet that has not been allocated to the charge instruction transaction in accordance with a predefined payout cycle within the scope of compliance with retention regulations set forth in laws and regulations (e.g., the Payment Services Act) (step S10). For example, the service providing device 300 refunds to business operator X the remaining balance that has not been allocated to the charge instruction transaction out of the specified balance that was added to the main wallet as the source of digital money to be allocated to the charge instruction transaction.

Specifically, the service providing device 300 checks the withdrawal cycle of business operator X at a predetermined cycle T2, and if 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. Then, if there is an unallocated balance in the money account that has not been allocated to the charge instruction transaction, the service providing device 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 withdrawal destination of the balance and information on the deposit amount (information on the amount corresponding to the balance). The service providing device 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".

In accordance with the deposit instruction from Business Operator Y, Bank B deposits the amount specified in the deposit instruction (for example, the amount corresponding to the balance) to the account information (account number) specified in the deposit instruction. Bank B may also send a notification to Business Operator Y's system SYS-4 that the deposit has been completed.

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

As described above, in operator Y's system SYS-4, the service providing device 300, which is an example of an information processing device according to this embodiment, pays out to operator X the balance remaining in the main wallet that has not been applied to the charge instruction transaction. This allows the service providing device 300 to provide various digital money-related services to service users while complying with retention regulations, thereby promoting the use of digital money-related services.

In addition, upon request from the service user, operator Y's system SYS-4 can provide detailed information regarding the digital money charge carried out in accordance with the charge instruction.

For example, as shown in Figure 2, business operator X, who has used the money charge service, sends a charge detail request to business operator Y's system SYS-4 to request detailed information related to the charge (step S11). Figure 2 shows an example in which business operator X requests detail information corresponding to a charge instruction for "2021 (year)/9 (Mon)/23 (Sun)", but it is also possible to request detail information for a desired period in one go, not just for a specific date.

When the service provider device 300 of the operator Y system SYS-4 receives a charge detail request from the operator X, it acquires detail information corresponding to the charge detail request based on the user ID included in the charge detail request (step S12). The service provider device 300 then transmits the acquired detail information to the operator X system SYS-1 and provides the detail information (step S13).

As shown in Figure 2, the detailed information provided to business operator X consists of, for example, three pieces of detailed information: detailed information J1, detailed information J2, and detailed information J3. Detailed information J1 records information from the deposit of funds corresponding to the charge instruction to the withdrawal of the balance not applied to the charge instruction transaction.

For example, as shown in Figure 2, statement information J1 includes information such as the deposit date when the funds to be used for the charge instruction transaction were deposited into Bank B, the amount of the funds deposited, the withdrawal date of the balance, and the amount of the balance withdrawn. In the case shown in Figure 2, the withdrawal amount is 0 yen, so the date recorded as the withdrawal date, "2021 (year)/10 (month)/1 (day)", corresponds to the date when the process to check the balance in the main wallet was performed.

Furthermore, for example, as shown in FIG. 2, the statement information J2 includes the allocation date when the planned charge amount is allocated to the sub-wallet from the predetermined balance added to the main wallet, the allocation amount indicating the planned charge amount, and the name of the charge.

Furthermore, for example, as shown in FIG. 2, the statement information J3 includes information on the date on which the planned charge amount allocated to the sub-wallet was applied to the charge instruction transaction and the charge execution date on which the charge was executed.

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

[2. Device configuration example]
The configuration of the provider Y system SYS-4 according to this embodiment will be described below. Fig. 3 is a block diagram showing an example of the configuration of the provider Y system according to this embodiment.

As shown in Figure 3, operator Y's system SYS-4 includes a management system 100, a charging system 200, and a service providing device 300.

Provider Y system SYS-4 is connected to network N-1. Provider Y system SYS-4 can communicate with provider X system SYS-1, bank A system SYS-2, bank B system SYS-3, and others via network N-1. Network N-1 is a wide area network (WAN) such as the Internet. Network N-1 may also include communication networks such as local area networks (LANs), telephone networks (such as mobile phone networks and landline telephone networks), and regional Internet Protocol (IP) networks. Network N-1 may also include wired and/or wireless networks.

The management system 100, charging system 200, and service providing device 300 are also connected to network N-2. The management system 100, charging system 200, and service providing device 300 can communicate with each other via network N-2. Network N-2 is a communications network such as a LAN. Network N-2 may include a wired network or a wireless network.

(Regarding the 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 transaction objects, and individual users such as general consumers who receive transaction objects 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 related to this embodiment.

As shown in Figure 4, the account information managed by the management system 100 has multiple fields, such as an "account ID," a "main wallet ID," an "owner ID," and a "total balance." These fields in the account information are associated with each other.

The "Account ID" field stores an account ID (identification information) that is uniquely assigned to each account to identify the money account. The "Main Wallet ID" field stores identification information for identifying the main wallet provided to the service user in the corporate account service.

The "Owner ID" field stores an owner ID (identification information) that is individually assigned to each owner to identify the owner of the money account linked to the account ID. As an 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.

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

The "Total Balance" item may be further divided into categories depending on the digital money management method. 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 deposited as salary out of the total balance stored in the "Total Balance" item. The "Non-Salary" item stores information indicating the balance of digital money deposited under a name other than salary out of the total balance stored in the "Total Balance" item.

The "non-salary" category may also be further divided into categories such as "regular" and "profit." In this case, the "regular" category stores information indicating the balance of digital money charged by the money account owner. For example, 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. Furthermore, information stored in the "profit" category could include information indicating the balance of digital money cashed back on the payment amount when using the electronic payment service provided by business operator Y to service users.

Furthermore, when the management system 100 receives a deposit notification from Bank B's system SYS-3 that has been executed in response to a deposit instruction from a service user (for example, Business X), it adds a specified balance to the money account linked to the main wallet of the service user (for example, Business X) in accordance with the contents of the deposit notification. For example, if the management system 100 receives a deposit notification from Bank B 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.

(Regarding the charging system 200)
The charging system 200 executes money charging by transferring digital money between money accounts in accordance with a charging instruction from a service user. The charging system 200 manages charging instruction information acquired from the service user. Figure 5 is a diagram showing an overview of the charging instruction information according to this embodiment.

As shown in Figure 5, the charge instruction information managed by the charge system 200 has the following fields: "Charge Source ID," "Charge Destination ID," "Planned Amount," "Planned Date," and "Nominal." These fields in the charge instruction information are associated with each other.

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 account information indicating the sender of the charge instruction is a user ID (identification information) that is individually assigned to each service user to identify the service user who sent the charge instruction.

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

The "Planned Amount" field stores information about the planned charge amount specified in the charge instruction. The "Planned Date" field stores information about the planned charge amount specified in the charge instruction. The "Nomenclature" field stores information indicating the nomenclature (purpose, use) of the charge specified in the charge instruction.

For example, in the example shown in Figure 5, a charge instruction is shown for each of the accounts identified by "U#001," "U#002," or "U#003" from the source account identified by "U#111." Specifically, a charge instruction for "300,000 yen" of digital money is shown for the account identified by "U#001" as the charge destination, with the scheduled date being "2021 (year)/9 (Mon)/27 (Sun)," under the name of "salary." Another charge instruction for "300,000 yen" of digital money is shown for the account identified by "U#002" as the charge destination, with the scheduled date being "2021 (year)/9 (Mon)/27 (Sun)." Another charge instruction for "400,000 yen" of digital money is shown for the account identified by "U#003" as the charge destination, with the scheduled date being "2021 (year)/9 (Mon)/30 (Sun)."

The charging system 200 also allocates the planned charge amount allocated to the sub-wallet to the charge instruction transaction at a predetermined cycle (for example, cycle T1 shown in Figure 1). Specifically, the charging system 200 allocates the planned charge amount from the balance in the main wallet in order of the charge instructions with the nearest planned charge date.

For example, in the case shown in Figure 5, of two charge instructions from business operator X, the charge instruction in the name of salary with a scheduled charge date of "2021 (Year)/9 (Mon)/27 (Sun)" will first be allocated the planned charge amount by the charge system 200. If the charge system 200 determines that the balance in the main wallet is less than the planned charge amount, it can suspend 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 corresponding to the planned charge amount from the digital money balance in the money account linked to the main wallet, making it untransferable until the charge is executed.

The charging system 200 also carries out charging in accordance with the charging instructions from business operator X. Specifically, the charging system 200 identifies a money account linked to the account to be charged from among the money accounts managed by the management system 100, and transfers digital money corresponding to the planned charging amount from a money account linked to business operator X's corporate account to the identified money account.

For example, on the scheduled charge date, "2021 (Year)/9 (Mon)/27 (Sun)", the charging system 200 transfers digital money worth the planned charge amount of "300,000 yen" from the money account of the charging source, business operator X, to the money account linked to the charge destination account, "U#001". Also, for example, on the scheduled charge date, "2021 (Year)/9 (Mon)/27 (Sun)", the charging system 200 transfers digital money worth the planned charge amount of "300,000 yen" from the money account of the charging source, business operator X, to the money account linked to the charge destination account, "U#002". Furthermore, for example, on the planned charge date, "2021 (Year)/9 (Mon)/30 (Sun)", the charge system 200 transfers digital money equivalent to the planned charge amount of "400,000 yen" from the money account of business X, the charge source, to the money account linked to the charge destination account, "U#003".

(Regarding the service providing device 300)
The service providing device 300 cooperates with the management system 100 and the charging system 200 to execute processes related to various services relating to digital money that the business operator Y provides to service users. As shown in FIG. 3 , the service providing device 300 includes a communication unit 310, a storage unit 320, and a control unit 330.

(Regarding the communication unit 310)
The communication unit 310 is connected to the network N-1 or the network N-2 by wire or wirelessly. The communication unit 310 transmits and receives information to and from the operator X system SYS-1, the bank A system SYS-2, the bank B system SYS-3, and the like via the network N-1. The communication unit 310 also transmits and receives information to and from the management system 100 and the charging system 200 via the network N-2. The communication unit 310 is realized, for example, by a network interface card (NIC) or the like.

(Regarding the storage unit 320)
The storage unit 320 stores programs and data used for control and calculation by the control unit 330. The storage unit 320 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 3 , the storage unit 320 has an account information storage unit 321 and a charge history storage unit 322.

(Regarding the account information storage unit 321)
The account information storage unit 321 stores account information related to a corporate account provided to a service user who uses the corporate account service. As described below, the corporate account service provides a main wallet and a sub-wallet used for the money charging service. FIG. 6 is a diagram showing an overview of the account information stored in the account information storage unit according to this embodiment. Note that FIG. 6 shows an example of account information according to this embodiment, and the account information may be configured in a form different from the example shown in FIG. 6.

As shown in FIG. 6, the account information stored in the account information storage unit 321 has multiple items, such as a "user ID" field, a "main wallet" field, a "sub-wallet" field, a "withdrawal cycle" field, a "withdrawal destination" field, and a "one-time account" field. These items in the account information are associated with each other.

The "User ID" field stores the user ID (identification information) that is individually assigned to a corporation such as Business X as a service user when registering to use the electronic payment service provided by Business Y.

The "Main Wallet" item stores the main wallet ID, which is identification information for identifying the main wallet, and information indicating the balance of the money account linked to the main wallet.

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

The "Withdrawal Cycle" field stores information about the pre-defined withdrawal cycle for digital money balances not applied to charge instruction transactions, within the scope of compliance with retention regulations set forth in laws and regulations (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 account information (account number) of the financial institution designated by the service user as the withdrawal destination for the amount corresponding to the digital money balance.

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 receive funds to be used for charge instruction transactions. For example, the account information (account number) of the one-time account is notified by business operator Y (service providing device 300) to business operator X, the sender of the charge instruction.

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

(Regarding the charge history storage unit 322)
The charge history storage unit 322 stores information regarding charge history executed based on charge instructions from service users who use 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 charge history may be configured in a form different from the example shown in Figure 7.

As shown in FIG. 7, the charge history stored in the charge history storage unit 322 has multiple fields, such as a "User ID," a "Charge instruction acceptance date," a "Main wallet balance addition date," an "Addition amount," a "Payout date," a "Payout amount," a "Sub-wallet allocation date," an "Allocation amount (nominal)," a "Charge date," and a "Charge execution date." These fields in the charge history are mutually associated.

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

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

The "Main Wallet Balance Addition Date" field stores information indicating the date on which the management system 100 added to the balance of 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.

The "Addition Amount" field stores information indicating the balance added to the money account linked to the main wallet.

The "Withdrawal Date" field stores information indicating the date on which the balance of digital money not allocated to 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 of day.

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.

The "Sub-wallet allocation date" field stores information indicating the date on which the planned charge amount was allocated from the specified 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 of day.

The "Allocation Amount (Name)" field stores information indicating the planned charge amount (allocation amount) allocated to the sub-wallet and information indicating the name of the charge.

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

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 charge destination account. The "Charge Execution Date" field may also store date and time information, including the time of day.

The example shown in Figure 7 makes it possible to identify information such as the date and time when a specified balance was added to the main wallet (the date of deposit into Bank B), the amount of the balance added to the main wallet, the date and time when the balance from the main wallet was withdrawn, and the amount withdrawn. Furthermore, the example shown in Figure 7 makes it 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, the example shown in Figure 7 makes it possible to identify information such as the date and time when the balance in the main wallet was appropriated to the planned charge amount, and the date and time when the charge was performed.

(Regarding the control unit 330)
The control unit 330 is a controller that controls and performs calculations on the service providing device 300. Each unit of the control unit 330 is realized by, for example, a central processing unit (CPU) or a micro processing unit (MPU) executing various programs stored in a storage device inside the service providing device 300 using RAM as a work area. The control unit 330 is also realized by, for example, an integrated circuit such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a system on a chip (SoC).

As shown in FIG. 3, the control unit 330 has a reception unit 331, an allocation unit 332, a payout unit 333, and a provision unit 334. The control unit 330 realizes or executes the information processing functions and actions described below using the units shown in FIG. 3. Although not explained further, the internal configuration of the control unit 330 is not limited to the units shown in FIG. 3, and may include units that realize or execute information processing functions and actions for separately managing at least the salary balance from the total digital money balance.

(Regarding the reception unit 331)
The reception unit 131 receives a charge instruction for digital money from a service user. For example, the reception unit 131 receives a charge instruction transmitted from a service user (e.g., business operator X) via the communication unit 310. The reception unit 131 registers the charge instruction in the charge system 200.

(Regarding the allocation unit 332)
After the charge instruction is accepted by the accepting unit 331, the allocating unit 332 allocates the planned charge amount specified in the charge instruction, on the condition that the deposit of the funds to be used for the charge instruction transaction is confirmed.

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

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

In addition, if the name specified in the charge instruction corresponds to a specified name, the funds to be applied to the charge instruction transaction will be deposited into an account in which the service user (for example, business operator Y) receives a loan from Bank B, and into which a pledge (revolving pledge) has been established to use the aforementioned funds as collateral. For example, if the name of the charge is salary, the funds will be deposited into an account in the service user's name into which a pledge (revolving pledge) has been established.

(Regarding the payout unit 333)
The payout unit 333 pays out to the service user the remaining balance of the digital money that has not been allocated to the charge instruction transaction executed in response to the charge instruction, according to a predefined payout cycle. For example, the payout unit 333 pays out to the service user the remaining balance that has not been allocated to the charge instruction transaction, out of the predetermined balance that has been added to the main wallet as the source of digital money to be allocated to the charge instruction transaction.

Specifically, the payout unit 333 references the account information stored in the account information storage unit 321 and checks whether the payout cycle for the balance not applied to the charge instruction transaction has been reached for business operator X, the sender of the charge instruction. The payout cycle is predefined within a range that complies with retention regulations set forth in laws and regulations (e.g., the Payment Services Act). If the payout unit 33 confirms that the payout 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 a balance exists in business operator X's money account, the payout 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 payout destination of the balance and information on the deposit amount (information on the amount corresponding to the balance). The payout 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."

(Regarding the providing unit 334)
In response to a request from a service user, the providing unit 334 provides detailed information (see FIG. 2, for example) relating to the digital money charge executed in response to a charge instruction.

For example, the providing unit 334 obtains a charge detail request sent from a service user via the communication unit 310. Then, based on the user ID included in the charge detail request, the providing unit 334 obtains detail information corresponding to the charge detail request from the charge history stored in the charge history storage unit 322. Note that the charge detail request may specify the date or period for which the user wishes to receive the detail information.

For example, the providing unit 334 can acquire various information ranging from the deposit of funds corresponding to the charge instruction to the payout of the balance not allocated to the charge instruction transaction. Information that the providing unit 334 can acquire from the charge history includes the deposit date on which the funds to be allocated to the charge instruction transaction were deposited into Bank B, the amount of the funds deposited, the payout date of the balance, and the payout amount of the balance. Furthermore, information that the providing unit 334 can acquire from the charge history includes the allocation date on which the planned charge amount was allocated to the sub-wallet from a specified balance added to the main wallet, the allocation amount indicating the planned charge amount, and information on the name of the charge. Furthermore, information that the providing unit 334 can acquire from the charge history includes the allocation date on which the planned charge amount allocated to the sub-wallet was allocated to the charge instruction transaction, and the charge execution date on which the charge was executed.

The providing unit 334 can provide the service user with multiple pieces of detailed information that compile this information for each specified procedure. For example, the providing unit 334 can provide the service user with detailed information (e.g., detailed information J1 shown in FIG. 2) that compiles information such as the deposit date on which the funds to be applied to the charge instruction transaction were deposited into Bank B, the amount of the funds deposited, the withdrawal date of the balance, and the amount of the balance withdrawn. Furthermore, for example, the providing unit 334 can provide detailed information (e.g., detailed information J2 shown in FIG. 2) that compiles information such as the allocation date on which the planned charge amount was allocated to the sub-wallet from the specified balance added to the main wallet, the allocation amount indicating the planned charge amount, and the name of the charge. Furthermore, for example, the providing unit 334 can provide detailed information (e.g., detailed information J3 shown in FIG. 2) that compiles information such as the allocation date on which the planned charge amount allocated to the sub-wallet was applied to the charge instruction transaction and the charge execution date on which the charge was executed.

3. Processing Procedure
(3-1. Overall processing)
The overall processing flow in the information processing system SYS according to this embodiment will be described below with reference to Fig. 8. Fig. 8 is a sequence diagram showing the overall processing flow in the information processing system according to this embodiment.

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

When the service provider device 300 of operator Y system SYS-4 receives a charge instruction from operator X system SYS-1, it registers the charge instruction in the charge system 200 (step S102).

Furthermore, in accordance with the operation by business operator X, business operator X's system SYS-1 sends a deposit instruction to bank A's system SYS-2 to apply the funds to the charge instruction transaction (step S103).

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

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

When the management system 100 of business Y's system SYS-4 receives the deposit notification from Bank B's system SYS-3, it adds a specified balance equivalent to the amount notified in the deposit notification to business X's main wallet (step S106).

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

The charge system 200 of operator Y's system SYS-4 references the subwallet at a predetermined cycle (for example, cycle T1 shown in Figure 1), and if allocation to the subwallet is confirmed, it applies the planned charge amount allocated to the subwallet to the charge instruction transaction (step S108).

The charging system 200 also performs charging in accordance with the charging instructions from business operator X (step S109).

Meanwhile, the service provider device 300 of business operator Y's system SYS-4 pays out the balance in the main wallet that has not been applied to the charge instruction transaction to business operator X in a predefined payout cycle (step S110). This completes the processing shown in Figure 8.

(3-2. Processing of the service providing device)
Next, a processing procedure performed by the service providing device 300 according to this embodiment will be described with reference to Fig. 9. Fig. 9 is a flowchart showing an example of a processing procedure performed by the service providing device according to this embodiment. Note that the processing procedure shown below is repeatedly executed by the control unit 330 of the service providing device 300.

As shown in FIG. 9, the reception unit 331 registers the charge instruction received from the service user in the charge system 200 (step S201). In addition, the allocation unit 332 checks the balance in the main wallet of the service user who sent the charge instruction (step S202).

If the allocation unit 332 confirms that a specified 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 item specified in the charge instruction (step S203).

The payout unit 333 also references the account information stored in the account information storage unit 321 to check whether the payout cycle for the balance not applied to the charge instruction transaction has been reached for the service user who sent the charge instruction (step S204).

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

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

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

If it is confirmed in step S204 above that the dispensing cycle has not been reached (step S204; No), the confirmation procedure of step S204 is repeated at a predetermined interval.

In step S202 described above, if the allocation unit 332 confirms that the specified balance has not been added to the main wallet (step S202; No), it determines whether the grace period for executing the charge instruction is still in effect (e.g., seven days from the receipt of the instruction) (step S207).

If the allocation unit 332 determines that the grace period for executing the charge instruction is still in effect (step S207; Yes), the process returns to the confirmation procedure of step S202 described above.

On the other hand, if the allocation unit 332 determines that the grace period for executing the charge instruction is not yet reached (step S207; No), it discards the charge instruction received from the service user (step S208). The allocation unit 332 then notifies the service user who sent the charge instruction that the charge instruction has been discarded (step S209), and ends the processing procedure shown in FIG. 9.

4. Modifications
The present embodiment described above shows 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 charging system 200 may be aggregated in the service providing device 300, and the service providing device 300 may execute the management system 100 and the charging system 200. An example configuration of the service providing device 400 in this case will be described below. FIG. 10 is a diagram showing an example configuration of a service providing device according to a modified example.

As shown in FIG. 10, the service providing device 400 according to the modified example has a communication unit 410, a memory unit 420, and a control unit 430.

The communication unit 410 corresponds to the communication unit 310 of the service providing device 300. The communication unit 410 transmits and receives information to and from the operator X system SYS-1, the bank A system SYS-2, the bank B system SYS-3, and the like via the network N-1.

The memory unit 420 corresponds to the memory unit 320 of the service providing device 300, and stores programs and data used for control and calculation by the control unit 430. As shown in FIG. 10, the memory unit 420 has an account information memory unit 421, an account information memory unit 422, a charge instruction information memory unit 423, and a charge history memory unit 424.

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 related to corporate accounts provided to service users who use the corporate account service.

The account information storage unit 422 stores account information related to money accounts held 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).

The charge instruction information storage unit 423 stores charge instruction information obtained from the service user. The charge instruction information stored in the charge instruction information storage unit 423 corresponds to the charge instruction information managed by the above-mentioned charge system 200 (see Figure 5).

The charge history memory unit 424 corresponds to the charge history memory unit 322 of the memory unit 320 described above, and stores information regarding the charge history executed based on charge instructions from service users who use the corporate account service.

The control unit 430 corresponds to the control unit 330 of the service providing device 300, and is a controller that controls and performs calculations on the service providing device 400. As shown in FIG. 10 , the control unit 430 has a reception unit 431, a management unit 432, an allocation unit 433, a charge unit 434, a payout unit 435, and a provision unit 436.

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

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.

For example, the management unit 432 acquires, via the communication unit 410, a deposit notification from Bank B's system SYS-3 that has been executed in response to a deposit instruction from a service user (e.g., Business X). The management unit 432 then adds to the digital money balance linked to the main wallet of the service user (e.g., Business X) according to the contents of the acquired deposit notification. For example, if the management unit 432 receives a deposit notification from Bank B indicating that 450,000 yen has been deposited, it adds the digital money balance 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 main wallet of the service user who sent the charge instruction, among the account information stored in the account information storage unit 421.

The allocation unit 433 corresponds to the allocation unit 332 of the control unit 330 described above, and after the charge instruction is accepted by the acceptance unit 431, the allocation unit 433 allocates the planned charge amount specified in the charge instruction, on the condition that the deposit of the funds to be applied to the charge instruction transaction is confirmed.

The charging unit 434 is responsible for the processing functions executed by the charging system 200 described above, and performs money charging by transferring digital money between money accounts in accordance with charging instructions from the service user.

For example, the charging unit 434 allocates the planned charge amount allocated to the sub-wallet at a predetermined cycle (for example, cycle T1 shown in Figure 1) to the charge instruction transaction. Specifically, the charging unit 434 allocates the planned charge amount from the balance in the main wallet in order of the charge instructions with the nearest planned charge date.

Furthermore, for example, the charging unit 434 performs charging in accordance with a charging instruction from a service user (e.g., business operator X). Specifically, the charging unit 434 references the account information stored in the account information storage unit 422 and identifies a money account linked to the account to be charged specified in the charging instruction. The charging unit 434 then performs money charging by transferring digital money corresponding to the planned charging amount from a money account linked to the service user's corporate account to the identified money account.

The payout unit 435 corresponds to the payout unit 333 of the control unit 330 described above, and pays out the remaining digital money that has not been applied to the charge instruction transaction to the service user according to a predefined payout cycle.

The providing unit 436 corresponds to the providing unit 334 of the control unit 330 described above, and provides detailed information (see, for example, Figure 2) that is detailed information related to the digital money charge executed in response to a charge instruction in response to a request from the service user.

In this way, by aggregating the various components of the provider Y system SYS-4 according to the present embodiment described above and integrating them physically and functionally into the service provider device 400, information related to various services can be centrally managed, enabling efficient processing. Furthermore, there is no need to deploy a network N-2 that communicatively connects the various components of the provider Y system SYS-4 according to the present embodiment described above, eliminating the impact of communication failures in the network N-2 on the provision of services.

5. Hardware Configuration
The above-described service providing device 300 according to the present embodiment or the service providing device 400 according to the modified example is realized, for example, by a computer 1000 having a configuration as shown in Fig. 11. Fig. 11 is a hardware configuration diagram showing an example of a computer that realizes the functions of the service providing device according to the present embodiment or the modified example.

The 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 IF (Interface) 1060, an input IF 1070, and a network IF 1080 are connected via a bus 1090.

The arithmetic device 1030 operates based on programs stored in the primary storage device 1040 and secondary storage device 1050, and 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 device 1030 for various calculations. The secondary storage device 1050 is a storage device in which data used by the arithmetic device 1030 for various calculations and various databases are registered, and is realized by a ROM (Read Only Memory), HDD, flash memory, etc.

The output IF 1060 is an interface for transmitting information to be output to an output device 1010, such as a monitor or printer, which outputs various types of information. It is implemented, for example, by a connector conforming to a standard such as USB (Universal Serial Bus), DVI (Digital Visual Interface), or HDMI (High Definition Multimedia Interface). The input IF 1070 is an interface for receiving information from various input devices 1020, such as a mouse, keyboard, and scanner, and is implemented, for example, by USB.

The input device 1020 may be a device that reads information from optical recording media 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), a tape medium, a magnetic recording medium, or a semiconductor memory. The input device 1020 may also be an external storage medium such as a USB memory.

Network IF 1080 receives data from other devices via network N and sends it to the computing device 1030, and also transmits data generated by the computing device 1030 to other devices via network N.

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.

For example, when the computer 1000 functions as the service providing device 300, which is an example of an information processing device according to this embodiment, the arithmetic unit 1030 of the computer 1000 realizes functions similar to those of the control unit 330 by executing a program (e.g., an information processing program) loaded onto the primary storage device 1040. In other words, the arithmetic unit 1030 realizes the processing of the service providing device 300 according to this embodiment in cooperation with the program (e.g., an information processing program) loaded onto the primary storage device 1040.

Furthermore, when the computer 1000 functions as the service providing device 400, which is an example of an information processing device according to the modified example, the arithmetic unit 1030 of the computer 1000 realizes the same functions as the control unit 430 by executing a program (e.g., an information processing program) loaded onto the primary storage device 1040. In other words, the arithmetic unit 1030 realizes the processing by the service providing device 400 according to the modified example in cooperation with the program (e.g., an information processing program) loaded onto the primary storage device 1040.

6. Effects
As described above, the service providing device 300, which is an example of an information processing device according to this embodiment, has a reception unit 331 and a disbursement unit 333. The reception unit 331 receives a digital money charge instruction from a service user. The disbursement unit 333 pays out the remaining digital money that has not been applied to the charge instruction transaction in accordance with the charge instruction to the service user in accordance with a predetermined disbursement cycle.

This allows the service providing device 300 to provide various digital money-related services to service users while complying with retention regulations, thereby promoting the use of digital money-related services.

In addition, the payout unit 333 pays out to the service user the balance that has not been allocated to the charge instruction transaction, out of the specified balance added to the main wallet as the source of digital money to be allocated to the charge instruction transaction.

The service providing device 300 also has an allocation unit 332 that allocates the planned charge amount specified in the charge instruction from a predetermined balance to the sub-wallet corresponding to the charge name specified in the charge instruction.

This allows the service providing device 300 to electronically manage information related to digital money charges through the main wallet and sub-wallet linked to the service user.

The service providing device 300 also has a providing unit 334 that, in response to a request from a service user, provides detailed information regarding the digital money charge executed in accordance with a charge instruction. This allows the service providing device 300 to provide the service user with a detailed understanding of the flow of deposits and withdrawals related to the charge instruction, thereby promoting the use of digital money-related services.

[7. Other]
The present embodiment and some of its modifications have been described in detail above with reference to the drawings. However, these are merely examples, and the present invention can be implemented in other forms that incorporate various modifications and improvements based on the knowledge of those skilled in the art, including the forms described in the Disclosure of the Invention section.

Furthermore, the configuration of the above-mentioned service providing device 300 or service providing device 400 can be flexibly changed, for example, by calling external platforms using APIs (Application Programming Interfaces) or network computing, depending on the functions.

Furthermore, the term "unit" in the claims can be read as "means" or "circuit." For example, a control unit can be read as a control means or a control circuit.

Furthermore, the effects described in the embodiments of the present application are merely descriptive or exemplary and are not limiting. In other words, the embodiments of the present application may achieve other effects that would be apparent to those skilled in the art from the description of the embodiments, in addition to or in place of the above effects.

100 Management system 200 Charging system 300 Service providing device 310 Communication unit 320 Memory unit 321 Account information memory unit 322 Charging history memory unit 330 Control unit 331 Reception unit 332 Allocation unit 333 Payout unit 334 Provision unit 400 Service providing device 410 Communication unit 420 Memory unit 421 Account information memory unit 422 Account information memory unit 423 Charging instruction information memory unit 424 Charging history memory unit 430 Control unit 431 Reception unit 432 Management unit 433 Allocation unit 434 Charging unit 435 Payout unit 436 Provision unit

Claims (7)

a reception unit that receives a digital money charging instruction from a service user;
an allocation unit that, when receiving a deposit notification indicating that funds to be applied to a charge instruction transaction in accordance with the charge instruction have been deposited into a virtual account linked to a main wallet used by the service user for depositing and withdrawing the digital money, allocates the planned charge amount to a sub-wallet corresponding to the charge name specified in the charge instruction, on the condition that a predetermined balance equivalent to the funds to be applied to the charge instruction transaction is added to the main wallet;
a charging unit that executes a process of charging a money account linked to a charge destination account specified in the charge instruction with digital money corresponding to the planned charge amount allocated by the allocation unit;
and a payout unit that pays out the remaining balance of the digital money that has not been applied to the charge instruction transaction to the service user in accordance with a payout cycle that is predefined within a range that can comply with retention regulations . The dispensing unit
2. The information processing device according to claim 1, wherein the predetermined balance that has not been applied to the charge instruction transaction is paid out to the service user. The allocation unit
Allocating the planned charge amount to the sub -wallet from the predetermined balance
3. The information processing apparatus according to claim 2, wherein : The information processing device according to any one of claims 1 to 3, further comprising: a providing unit that provides detailed information regarding the digital money charge executed in response to the charge instruction in response to a request from the service user. 1. A computer-implemented information processing method, comprising:
a receiving step of receiving a digital money charging instruction from a service user;
an allocation step of allocating the planned charge amount to a sub-wallet corresponding to the charge name specified in the charge instruction, on the condition that a predetermined balance equivalent to the funds to be allocated to the charge instruction transaction is added to the main wallet when the service user receives a deposit notification indicating that funds to be allocated to the charge instruction transaction in accordance with the charge instruction have been deposited into a virtual account linked to the main wallet used by the service user for depositing and withdrawing the digital money;
a charging step of executing a process of charging a money account linked to a charge destination account specified in the charge instruction with digital money corresponding to the planned charge amount allocated in the allocation step;
and a payout step of paying out the remaining balance of the digital money that has not been applied to the charge instruction transaction to the service user in accordance with a payout cycle that is predefined within a range that can comply with retention regulations . A procedure for accepting instructions to charge digital money from a service user;
an allocation procedure for allocating the planned charge amount to a sub-wallet corresponding to the charge name specified in the charge instruction, on the condition that a predetermined balance equivalent to the funds to be allocated to the charge instruction transaction is added to the main wallet when the service user receives a deposit notification indicating that funds to be allocated to the charge instruction transaction in accordance with the charge instruction have been deposited into a virtual account linked to the main wallet used by the service user for depositing and withdrawing the digital money;
a charging step of executing a process of charging a money account linked to a charge destination account specified in the charge instruction with digital money corresponding to the planned charge amount allocated by the allocation step;
and a payout procedure for paying out the remaining balance of the digital money that has not been applied to the charge instruction transaction to the service user in accordance with a payout cycle that is predefined within a range that can comply with retention regulations . An information processing system including a charging system and a service providing device,
The service providing device
Accepts digital money charging instructions from service users,
When the service user receives a deposit notification indicating that funds to be applied to the charge instruction transaction in accordance with the charge instruction have been deposited into a virtual account linked to the main wallet used for depositing and withdrawing the digital money by the service user, the service user allocates the planned charge amount to a sub-wallet corresponding to the charge name specified in the charge instruction, on the condition that a predetermined balance equivalent to the funds to be applied to the charge instruction transaction is added to the main wallet,
The charging system
execute a process of charging a money account linked to a charge destination account specified in the charge instruction with digital money corresponding to the planned charge amount allocated by the service providing device;
The service providing device
The remaining balance of the digital money that has not been appropriated for the charge instruction transaction is paid out to the service user in accordance with a payout cycle that is predefined within the scope that allows compliance with retention regulations.
An information processing system comprising: