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

Abstract

To enhance convenience of a service related to a digital payment of a salary.SOLUTION: An information processing device according to the present application performs processing related to an electronic payment service provided to a user through an on-line system, and comprises a reception unit and an apportioning processing unit. The reception unit receives from a user an apportioning setting that specifies a plurality of apportioning destinations, including an electronic wallet held by the user in the electronic payment service, as destinations among which funds transferred to a given bank account pre-linked to the user are apportioned. Upon confirmation of the transfer to the given bank account, the apportioning processing unit performs apportioning processing to apportion the funds based on the apportioning setting corresponding to the relevant user.SELECTED DRAWING: Figure 7

Description

[Technical field]

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

[0002] Recently, the government has begun to consider introducing a so-called "digital salary payment" system, which would allow money transfer businesses to pay salaries using digital money such as the above-mentioned electronic money and virtual currency. In connection with this, technologies related to the digital payment of salaries have also been proposed. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2022-151873 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above-mentioned conventional technologies have room for improvement in terms of the convenience of services related to digital payment of wages. For example, currently, there is not much demand for receiving all wages in electronic money. For this reason, if a company that pays wages allows employees to transfer wages to multiple accounts designated by the employees at their request, the employees can receive part of their wages in electronic money through their electronic money account and the rest in cash through their conventional bank account.

[0005] However, when an employee designates multiple accounts as the transfer destination of their salary, the burden of transfer fees and other expenses increases, so it is unlikely that companies will actively adopt this. For this reason, it is unlikely that an employee would be able to receive part of their salary in electronic money by designating multiple accounts as the transfer destination of their salary. On the other hand, it is expected that the amount of their salary that an employee wishes to receive in electronic money will vary depending on the employee's circumstances, the amount of their salary, etc. For this reason, if the amount to be received in electronic money is fixed, it is difficult to hope for improved usability in services related to the digital payment of wages.

[0006] The present application has been made in consideration of the above, and aims to provide an information processing device, an information processing method, and an information processing program that improve the convenience of services related to digital payment of wages. [Means for solving the problem]

[0007] The information processing device according to the present application is an information processing device that executes processing related to an electronic payment service provided to a user through an online system, and includes a reception unit and an allocation processing unit. The reception unit receives from the user an allocation setting that specifies multiple allocation destinations, including an electronic wallet held by the user in the electronic payment service, as an allocation destination of funds to be deposited into a predetermined bank account that is linked to the user in advance. When a deposit into the predetermined bank account is confirmed, the allocation processing unit executes an allocation process that allocates funds based on the allocation setting corresponding to the target user. Effect of the Invention

[0008] According to one aspect of the embodiment, it is possible to improve the convenience of services related to digital payment of wages. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an overview of information processing according to an embodiment. [Diagram 2]FIG. 2 is a diagram showing an example of a screen display when setting distribution according to the embodiment. [Diagram 3] FIG. 3 is a diagram showing an example (part 1) of information provided in the sorting service according to the embodiment. [Figure 4] FIG. 4 is a diagram showing an example (part 2) of information provided in the sorting service according to the embodiment. [Diagram 5] FIG. 5 is a diagram showing an example of the use of financial services through a sorting service according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of information management in the sorting service according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of the configuration of the payment server according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of information stored in the account information storage unit according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of information related to a distribution setting stored in the distribution setting storage unit according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a sorting history stored in a sorting history storage unit according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of user information stored in a user information storage unit according to the embodiment. [Figure 12] FIG. 12 is a flowchart illustrating an example of a process procedure of a payment schedule providing process executed by the payment server according to the embodiment. [Figure 13] FIG. 13 is a flowchart illustrating an example of a processing procedure of the allocation process executed by the payment server according to the embodiment. [Figure 14] FIG. 14 is a hardware configuration diagram illustrating an example of a computer that realizes the functions of the payment server according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, the information processing device, the information processing method, and the information processing program according to the present application will be described in detail with reference to the drawings. Note that the information processing device, the information processing method, and the information processing program according to the present application are not limited to the embodiments. In addition, the same parts in the following embodiments are given the same reference numerals, and duplicated explanations will be omitted.

[0011] 1. Embodiment The information processing performed by the information processing device according to the embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an overview of the information processing performed by the embodiment. In Fig. 1, the information processing performed by the embodiment is performed by a payment server 100, which is an example of the information processing device according to the embodiment.

[0012] (1-1. System Configuration) As shown in FIG. 1, the information processing system SYS according to the embodiment includes a user terminal 10, a bank server 20, an affiliated bank server 30, and a payment server 100. The user terminal 10, the bank server 20, the affiliated bank server 30, and the payment server 100 are connected to each other via a network N (see FIG. 7, for example) so as to be able to communicate with each other by wire or wirelessly. The network N is, for example, a wide area network (WAN) such as the Internet. Note that, for the sake of convenience of explanation, FIG. 1 illustrates a case in which the information processing system SYS includes only one user terminal 10, bank server 20, affiliated bank server 30, and payment server 100, but the information processing system SYS may include multiple user terminals 10, bank servers 20, affiliated bank servers 30, and payment servers 100.

[0013] The payment server 100 shown in Fig. 1 is an information processing device that executes information processing according to the embodiment, and is realized by a server device, a cloud system, etc. For example, the payment server 100 is operated and managed by an operator UA that provides an electronic payment service (a service that provides a predetermined transaction means that controls the exchange of electronic money by code payment) related to electronic payment using a user terminal 10 to a service user (for example, a service user UB shown in Fig. 1).

[0014] Furthermore, the payment server 100 executes various information processes related to electronic payments using the user terminal 10. Specifically, the payment server 100 distributes an application program for user terminals (hereinafter, appropriately referred to as a "payment application") for implementing code payments to general consumers who are service users. When the payment server 100 accepts a transaction request from the payment application via an interface dedicated to the payment application, it executes information processes including a transfer process of electronic money between accounts according to the transaction request. The payment application transmits transaction information including information such as the payment destination, the payment source, and the payment amount to the payment server 100. In addition to the above-mentioned information, the transaction information may include information such as a transaction code for individually identifying a transaction and date and time information (timestamp) for identifying the date and time when the transaction was performed.

[0015] Furthermore, the payment server 100 provides a transfer deposit service using electronic money as one of the linked services linked to the above-mentioned electronic payment service. For example, the payment server 100 provides a service that accepts the transfer deposit of a salary using electronic money. The specific contents of the information processing related to the transfer deposit service will be described in detail later. The service that accepts the transfer deposit of a salary may be configured as a mini-app launched in a payment app for realizing code payment, or may be a unique application program prepared independently of the payment app.

[0016] In addition, the payment server 100 provides a sorting service, which is one of the linked services linked to the above-mentioned electronic payment service, for sorting funds transferred to a virtual account linked to a service user according to the instruction of the service user. Specific information processing content of the sorting service will be described in detail later. The sorting service may be configured as a mini-app launched in a payment app for realizing code payment, or may be a unique application program prepared independently of the payment app.

[0017] The user terminal 10 shown in Fig. 1 is a general consumer who receives a transaction object from a store or the like, and is an information processing device used by a service user UB who uses a service provided by the payment server 100. The user terminal 10 is realized, for example, by a smartphone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), or the like. The user terminal 10 displays information distributed by the payment server 100 using a web browser or an application. Note that Fig. 1 illustrates a smartphone as an example of the user terminal 10.

[0018] When the user terminal 10 receives control information for implementing a predetermined information process from the payment server 100, the user terminal 10 implements the information process according to the control information. Here, the control information is described in, for example, 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), or a markup language such as HTML (HyperText Markup Language). The predetermined application itself delivered from the payment server 100 may be regarded as the control information.

[0019] The bank server 20 shown in Fig. 1 is an information processing device belonging to Bank X that manages bank accounts opened by applicants such as a company that employs a service user UB, and is realized by a server device, a cloud system, etc. For example, the bank server 20 manages information on withdrawals from the bank account by each card company or various service providers (such as the amount withdrawn and the date and time of withdrawal) and account information including the current account balance as a usage history of the bank account, in association with the account holder. The bank server 20 also executes processes such as remittance and transfer in response to instructions from each user.

[0020] The affiliated bank server 30 shown in Fig. 1 is an information processing device operated and managed by Bank Y, where the business entity UA holds an account, and is realized by a server device, a cloud system, etc. The affiliated bank server 30 manages the bank account usage history of each user, including the business entity UA, and performs processes such as remittance and transfer in response to instructions from each user.

[0021] (1-2. Payment using user terminal 10) Here, an example of code payment (electronic payment) using the user terminal 10 will be described. In the following description, for example, a two-dimensional code (QR code (registered trademark)) arranged in the store X, which indicates store identification information for identifying the store X, is used to perform a payment using the user terminal 10 by a service user UB who receives a transaction object from the store X. Note that the example of code payment described below is also applicable to a case where an arbitrary user uses an arbitrary user terminal 10 to perform a payment at an arbitrary store. In addition, the two-dimensional code indicating the store identification information may be not only a QR code, but also a barcode, a predetermined mark, a number, or the like. In addition, the two-dimensional code is not limited to an example that is physically formed by a printed matter printed on a medium such as paper, and may be formed by image information displayed on an arbitrary terminal.

[0022] For example, when a service user UB makes a payment for the purchase or use of a transaction object such as various goods or services at store X, the service user UB launches a payment application pre-installed on the user terminal 10. Then, the service user UB photographs a two-dimensional code installed at store X via the payment application. In such a case, the user terminal 10 displays a screen for inputting the price of the transaction object, and accepts input of the payment amount from the service user UB or a clerk at store X. Then, the user terminal 10 transmits transaction information to the payment server 100, the transaction information including user identification information that identifies the service user UB, store identification information (or information indicated by the store identification information, i.e., information indicating store X (for example, a store ID)), and the payment amount.

[0023] When the payment server 100 receives the transaction information from the user terminal 10, it transfers electronic money equivalent to the payment amount from the account of the service user UB indicated by the user identification information to the account of the store X indicated by the store identification information. At this time, the payment server 100 may transfer the electronic money equivalent to the payment amount to the account of the store X after subtracting a predetermined fee to be charged to the store X from the electronic money equivalent to the payment amount. Then, the payment server 100 transmits a notification that the transaction is completed to the user terminal 10. In such a case, the user terminal 10 notifies the service user UB that the transaction using electronic money is completed by outputting a screen or a predetermined sound indicating that the transaction is completed. Alternatively, the payment server 100 may withdraw electronic money equivalent to the payment amount from the account of the service user UB indicated by the user identification information, manage it as sales information of the store X, and transfer cash equivalent to the sales to a bank account held by the store X at a predetermined timing. In this case, the payment server 100 may notify the service user UB that the transaction using electronic money has been completed at the time when electronic money equivalent to the payment amount has been withdrawn from the account of the service user UB.

[0024] It should be noted that the payment using the user terminal 10 is not limited to the above-mentioned process. For example, the payment using the user terminal 10 may be made using a terminal device (hereinafter referred to as the "store terminal") installed in the store X. Specifically, the user terminal 10 first displays code information indicating user identification information for identifying the service user UB on a screen. In such a case, the store terminal reads the user identification information from the code information displayed on the user terminal 10, and transmits transaction information including the read user identification information (or information indicated by the user identification information, i.e., information indicating the service user UB (e.g., user ID)), the payment amount, and information identifying the store X to the payment server 100.

[0025] When the payment server 100 receives the transaction information from the store terminal, it transfers electronic money equivalent to the payment amount from the account of the service user UB indicated by the user identification information to the account of the store X. Then, the payment server 100 transmits a notification that the transaction has been completed to the store terminal or the user terminal 10. The store terminal or the user terminal 10 notifies the service user UB that the transaction using electronic money has been completed by outputting a screen or a predetermined sound indicating that the transaction has been completed. The payment server 100 may also withdraw electronic money equivalent to the payment amount from the account of the service user UB indicated by the user identification information, manage the amount as sales information of the store X, and transfer cash equivalent to the sales amount to a bank account held by the store X at a predetermined timing. In this case, the payment server 100 may notify the store clerk or the service user UB that the transaction using electronic money has been completed at the timing when the electronic money equivalent to the payment amount is withdrawn from the account of the service user UB.

[0026] Furthermore, the payment using the user terminal 10 may not only be a process of transferring electronic money from an account to which the service user UB has previously charged electronic money to the account of the store X, but may also be, for example, a payment using a credit card previously registered by the service user UB. In such a case, for example, the user terminal 10 may transfer electronic money in an amount indicated by the payment amount to the account of the store X, and may also bill the operating company of the credit card of the service user UB for the amount indicated by the payment amount.

[0027] Furthermore, the settlement using the user terminal 10 may not only be a process of transferring electronic money from the account of the service user UB to the account of the store X, but may also be, for example, a settlement of transferring electronic money from the account of the service user UB to the account of another user (i.e., a transfer between users). For example, the user terminal 10 used by the service user UB who is the sender of the remittance reads user identification information (for example, user identification information displayed on a terminal device used by the user of the remittance destination) that identifies the user of the remittance destination, accepts an input of the remittance amount from the service user UB, and transmits information indicating the read identification information, the remittance amount, and the user identification information that identifies the service user UB to the settlement server 100. In such a case, the settlement server 100 may transfer electronic money in an amount indicated by the remittance amount from the account of the service user UB to the account of the user of the remittance destination, and notify the fact that the remittance has been completed by outputting a screen or a predetermined sound indicating that the remittance has been completed on the user terminal 10 or the terminal device used by the user of the remittance destination.

[0028] Note that remittance using the user terminal 10 is not limited to the above-mentioned process. For example, remittance using the user terminal 10 may be performed by inputting the telephone number of the remittance destination user or information indicating the remittance destination user (e.g., user ID) into the user terminal 10. To give a specific example, the user terminal 10 accepts input of the telephone number or user ID of the remittance destination user and the remittance amount from the service user UB, and transmits the input telephone number or user ID, the remittance amount, and user identification information for identifying the service user UB to the payment server 100. The payment server 100 then transfers electronic money in an amount indicated by the remittance amount from the account of the service user UB to the account of the user linked to the transmitted telephone number or user ID.

[0029] Here, the telephone number or user ID of the remittance destination user may be linked to information about the user and registered in advance in the payment application. In this case, the user terminal 10 accepts, from the service user UB, the designation of the user (remittance destination) registered in the payment application and the input of the remittance amount to the user, and transmits to the payment server 100 the telephone number or user ID linked to the designated user, the remittance amount, and user identification information for identifying the service user UB.

[0030] Furthermore, for example, remittance using the user terminal 10 may be performed by providing the remittance user with link information for receiving the remittance amount. As a specific example, the user terminal 10 accepts an input of the remittance amount from the service user UB, generates link information for receiving the remittance amount, and provides the link information to a terminal device used by the remittance user by sending an email including the link information or posting information including the link information on a social networking service (SNS). Then, when the remittance user selects the link information and performs a receiving operation, the settlement server 100 transfers electronic money in an amount indicated by the remittance amount from the account of the service user UB to the account of the remittance user.

[0031] The above-mentioned payment means and payment services are not limited to those for providing a price (settlement of debt) for purchasing a product or providing a service. For example, as described above, the payment means and payment services may have a function related to remittance between accounts held by multiple users. That is, the above-mentioned payment means and payment services may be services that control the transmission and reception of electronic money between accounts of any owner linked to the owner of electronic money, such as a user or a store. That is, the payment means and payment services according to the embodiment may be provided in any form as long as they are transaction means and transaction services that execute various controls for realizing the exchange of electronic money (not only various inter-account remittance controls via electronic money, but also controls related to exchanges between electronic money accounts and bank accounts, various claim processes such as installments and processes associated with bonus payments, and various controls related to the exchange of assets including electronic money). In addition, the various controls realized by such transaction means and transaction services may include both control related to payment and control related to remittance, or only one of them. That is, a "transaction" is a concept that includes not only "settlement" related to electronic money, but also "remittance" of electronic money and various other processes. In other words, the payment server 100 may be an information processing device that realizes a transaction means for controlling the exchange of electronic money between any owners.

[0032] (1-3. About the remittance service) The following describes the transfer deposit service that the payment server 100 provides to the service user UB. When the payment server 100 accepts a registration request for the transfer deposit service from the service user UB through a payment app or the like, it executes allocation of a virtual account to the service user UB and registration of user information. For example, the payment server 100 arbitrarily selects an unused virtual account from among a plurality of virtual accounts borrowed in advance from a partner bank. The payment server 100 also completes allocation of the virtual account by registering account information (account number) for identifying the selected virtual account in association with identification information unique to the service user UB. Note that the payment server 100 can use, for example, a user ID that the payment server 100 assigns to each user individually when registering to use the electronic payment service, as identification information unique to the service user UB.

[0033] In addition, in registering the user information, the settlement server 100 acquires from the service user UB information on a bank account for refunding to the service user UB any amount of cash that exceeds a predetermined amount among the amount deposited in the virtual account, for the purpose of complying with the retention regulations required by law for the money transfer business. The settlement server 100 completes the initial registration of the user information by registering the information on the bank account for refund acquired from the service user UB in association with the above-mentioned unique information.

[0034] When the allocation of the virtual account and the registration of the user information are completed, the settlement server 100 transmits the account information (account number) for identifying the virtual account for the transfer deposit service to the user terminal 10, thereby providing the account information to the service user UB. The service user UB informs the transfer request destination, such as the company where the user works, of the account information provided by the settlement server 100 as the transfer destination of the salary, various expenses, etc. The transfer request destination, such as the company that receives the account information from the service user UB, transfers the predetermined amount, such as the salary, various expenses, etc., from the bank account that the transfer request destination, such as the company, receives the account information from the service user UB, and transfers the predetermined amount, such as the salary, various expenses, etc., from the bank account that the transfer request destination, such as the company, receives the account information. When the settlement server 100 detects the arrival of money in the virtual account, it charges the electronic wallet (electronic money account) of the service user UB to which the virtual account is assigned, with electronic money equivalent to the amount of the deposit to the virtual account. In this way, the service user UB can receive the receivables that he / she holds in electronic money by informing the transfer request destination of the account information.

[0035] (1-4. Information Processing According to the Embodiment) (1-4-1. Information processing for sorting services) Hereinafter, information processing related to the sorting service according to the embodiment will be described with reference to Fig. 1. In the following explanation, information processing in the case where the sorting target by the sorting service is the salary of the service user UB will be described. Note that the information processing according to the embodiment is not limited to the case where the sorting target is a salary, but can be applied to various types of funds transferred to a specified account linked in advance to the service user UB.

[0036] In the following description, the service user UB may be regarded as the same as the user terminal 10. That is, in the following description, the service user UB may be read as the user terminal 10.

[0037] As shown in Fig. 1, the service user UB executes salary allocation settings, for example, through a payment app (step S01). An example of a screen display displayed on the user terminal 10 when setting salary allocation will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of a screen display when setting allocation according to an embodiment. The payment server 100 accepts from the service user UB, through the payment app, allocation settings that specify multiple allocation destinations, including an electronic wallet held by the service user UB in an electronic payment service, as allocation destinations for the salary to be deposited into a specified bank account that is linked in advance to the service user UB.

[0038] As described below, prior to setting up salary allocation, a procedure for issuing a receiving account for receiving at least a portion of salary in electronic money is carried out. For example, as shown in Fig. 2, the top screen G1-1 of the payment application is displayed on the user terminal 10 in response to an operation by the service user UB (display example EX1-1). Also, in response to an operation by the service user UB on the top screen G1-1, the user terminal 10 displays an explanation screen (tutorial screen) G1-2 for using the salary allocation setting (display example EX1-2). The explanation screen G1-2 for the allocation setting shown in Fig. 2 is provided with a button B-1 for starting the salary allocation setting.

[0039] In response to the operation of the button B-1 on the explanation screen G1-2 by the service user UB, the user terminal 10 displays a setting screen G1-3 for setting the amount of payment to be received in electronic money from the salary and information on the current salary receiving account (display example EX1-3). The setting screen G1-3 shown in FIG. 2 has a button B1-2 for receiving a request from the service user UB to issue a receiving account for receiving the salary in both electronic money and cash. This receiving account is a virtual account, and is issued in the same manner as the above-mentioned transfer deposit service. For example, the settlement server 100 arbitrarily selects an unused virtual account number from among a plurality of virtual account numbers borrowed in advance from the affiliated bank Y, and assigns the selected virtual account number to the service user UB as a receiving account number. The virtual account is linked to a real account held by the business operator UA at Bank Y.

[0040] In addition, in response to the operation of the service user UB on the button B1-2 provided on the setting screen G1-3, the payment server 100 judges whether or not user authentication of the service user UB is necessary. If it is judged that user authentication is necessary, user authentication is performed between the payment server 100 and the service user UB. If the user authentication is successful, the payment server 100 executes a receiving account issuing process, and the user terminal 10 displays a receiving account number notification screen G1-4 (display example EX1-4). On the other hand, if it is judged that user authentication is not necessary, the payment server 100 executes a receiving account issuing process, on the condition that the service user UB agrees to the terms of use, and the user terminal 10 displays a receiving account number notification screen G1-4. The notification screen G1-4 shown in FIG. 2 displays information on the receiving account number. The payment server 100 registers the receiving account number information in the account information storage unit 121 in association with the user ID of the service user UB.

[0041] In addition, when the procedure for issuing the receiving account is completed, a salary allocation setting screen G2 (an example of a "predetermined user interface") is displayed on the user terminal 10 in response to the operation of the service user UB on the top screen G1-1 of the payment application, as shown in Fig. 2 (display example EX2). The allocation setting screen G2 shown in Fig. 2 includes a screen switching tab display area A1-1, a receiving amount setting area A1-2, and an allocation setting area A1-3.

[0042] The screen switching tab display area A1-1 includes a tab for displaying a setting screen G3 (see, for example, FIG. 5) for accepting settings related to the management of salary received as electronic money, a tab for displaying an allocation setting screen G2 for accepting settings related to salary allocation, and a tab for displaying a management screen (see, for example, FIG. 6) for managing the user information of the service user UB. For example, the user terminal 10 displays a screen corresponding to the tab operated by the service user UB. FIG. 2 shows an example in which the tab corresponding to the allocation setting screen G2 is enabled.

[0043] The receiving amount setting area A1-2 also includes a slide bar that receives an intuitive operation from the service user UB to set the receiving amount, which indicates the amount to be received in electronic money from the salary. The slide bar is configured to be movable according to the operation of the service user UB on a line segment that connects the minimum amount (for example, 0 yen) and the maximum amount (for example, 1 million yen) that can be set as the receiving amount. In FIG. 2, an example is shown in which the slide bar specifies 50,000 yen as the receiving amount. Note that the settlement server 100 may set the amount that can be received as electronic money at that time as the maximum amount, for example. For example, the amount that can be received at that time is the amount obtained by subtracting the amount of electronic money held at that time from the upper limit of 1 million yen that can be held as electronic money. The amount that can be received at that time may also be indicated numerically as a guideline, or may be displayed by changing the color of the line or the line. When the payment server 100 receives a pre-set amount to be received from the service user UB, it registers and manages information indicating the amount to be received pre-set by the service user UB in the allocation setting memory unit 122 as information regarding the allocation of funds, in association with the user ID of the service user UB.

[0044] In addition, the receipt amount setting area A1-2 shown in FIG. 2 shows an example in which the setting of the receipt amount to be received as electronic money from salary is accepted, but instead of the receipt amount, a receipt ratio indicating the ratio of the receipt amount to salary, such as 10% or 15% of salary, may be accepted. In this case, a slide bar included in the receipt amount setting area A1-2 may be configured to allow the receipt ratio to be set. Furthermore, the payment server 100 calculates the receipt amount based on the receipt ratio set for the service user UB and the deposit amount deposited into the receiving account as salary (the deposit amount included in the deposit notice).

[0045] The distribution setting area A1-3 also accepts distribution settings including at least one distribution destination account to which the salary is distributed, the amount to be remitted to the distribution destination account, and a setting of a name indicating the purpose of use of the distribution destination account or the purpose of distribution of the salary. FIG. 2 shows an example in which the account number of a regular account at M-1 Bank, the amount to be remitted of 220,000 yen, and the nominal living expenses are displayed as one of the distribution destinations. FIG. 2 also shows an example in which the account number of a regular account at M-2 Bank, the amount to be remitted of 30,000 yen, and the nominal mortgage are displayed as one of the distribution destinations. The distribution setting area A1-3 accepts new settings and changes to distribution destinations in response to operations from the service user UB. When the settlement server 100 receives the preset destination account, remittance amount, and name from the service user UB, it registers each piece of information indicating the destination account, remittance amount, and name preset by the service user UB in the remittance setting storage unit 122 as information regarding the remittance setting that specifies the destination of funds, in association with the user ID of the service user UB. The settlement server 100 can receive the setting of the name for each destination account. Note that the remittance setting area A1-3 may receive from the service user a remittance ratio setting indicating the ratio of the remittance amount to the salary instead of the remittance amount. In this case, the settlement server 100 calculates the remittance amount based on the remittance ratio set for the service user UB and the amount of the deposit deposited in the receiving account as salary (the amount of the deposit included in the arrival notice).

[0046] The payment server 100 may receive from the service user UB a setting for remittance of the money balance to another service user of the electronic payment service as a salary allocation destination. In this case, the payment server 100 registers in the allocation setting storage unit 122, as an allocation setting corresponding to the service user UB, a user ID for identifying the other service user to be the remittance destination and a remittance amount in association with each other. The payment server 100 then adds the money balance equivalent to the remittance amount to the other service user to the money balance of the electronic wallet held by the service user UB, and then transfers funds from the electronic wallet of the service user UB to the electronic wallet held by the other service user.

[0047] Returning to Fig. 1, for example, a company employing a service user UB makes a transfer reservation to the bank server 20 of Bank X for the receiving account number notified by the service user UB. When the transfer execution date in the transfer reservation arrives, the bank server 20 transfers the amount specified in the transfer reservation (for example, 300,000 yen) from the remittance bank account linked to the company to the receiving account number (step S02).

[0048] When the partner bank server 30 detects the receipt of funds from Bank X, it sends a notification of receipt to the settlement server 100, which is the borrower of the virtual account specified by the receiving account number into which the funds were received (step S03). For example, the notification of receipt includes information indicating the receiving account number and the amount of the deposit.

[0049] When the payment server 100 receives the notification of receipt of funds from the affiliated bank server 30, it identifies the distribution setting of the service user UB to be processed based on the notification of receipt of funds (step S04). For example, the payment server 100 identifies the user ID associated with the receiving account number included in the notification of receipt from the information stored in the account information storage unit 121. In addition, the payment server 100 identifies the distribution setting associated with the identified user ID from the information stored in the distribution setting storage unit 122.

[0050] The payment server 100 also transmits a remittance instruction to the affiliated bank server 30 according to the identified remittance setting (step S05-1). For example, the payment server 100 transmits a remittance instruction including a remittance source account number, which is the account number of a real account linked to the receiving account, a remittance destination account number, which is the remittance destination account included in the remittance setting, and a remittance amount included in the remittance setting. Note that the remittance source account does not necessarily need to be limited to a bank account, and may be an account to which electronic money can be remitted.

[0051] In addition, the payment server 100 adds (charges) the money balance of the electronic wallet held by the service user UB according to the identified distribution setting (step S05-2). For example, the payment server 100 adds (charges) electronic money in an amount equivalent to the amount of receipt included in the distribution setting to the electronic wallet linked to the service user UB.

[0052] The payment server 100 may also add the electronic money equivalent to the amount of the received amount to the electronic wallet held by the service user UB, on the condition that the balance after adding the electronic money equivalent to the amount of the received amount to the electronic wallet held by the service user UB does not exceed a predetermined amount that is a predetermined upper limit amount that the service user UB can secure in the electronic wallet. For example, the payment server 100 obtains the money balance of the electronic wallet held by the service user UB from the user information storage unit 124. The payment server 100 also calculates the balance after adding the electronic money equivalent to the amount of the received amount to the electronic wallet held by the service user UB (also called balance addition or charging), and compares it with a predetermined amount. Then, if the balance after the addition is equal to or less than the predetermined amount, the payment server 100 adds the electronic money equivalent to the amount of the received amount to the electronic wallet held by the service user UB. On the other hand, if the balance after the addition exceeds the predetermined amount, the payment server 100 provides the service user UB with information that the electronic wallet cannot be charged because the balance is exceeded.

[0053] The payment server 100 may also add electronic money equivalent to an amount not exceeding a predetermined amount to the electronic wallet based on the amount equivalent to the amount received, the predetermined amount, and the money balance of the service user UB at that time, and pay out the remaining amount to a bank account set up in advance by the service user UB. The payment server 100 may also add electronic money equivalent to the amount received to the electronic wallet once, and if the money balance after the addition exceeds the predetermined amount, pay out the amount equivalent to the amount exceeding the predetermined amount to a bank account set up in advance by the service user UB.

[0054] Also, the payment server 100 may execute either the transfer to the bank account or the charge to the electronic wallet first. For example, when only the amount of receipt and the bank account for receiving the salary are set by the service user UB, the payment server 100 may execute the charge to the electronic wallet (addition to the balance) first on the condition that the balance after adding the amount of electronic money equivalent to the amount of receipt to the electronic wallet held by the service user UB does not exceed a predetermined amount, and may transfer the remaining amount after subtracting the amount of receipt from the salary from the real account linked to the receiving account to the bank account for receiving the salary. Also, the payment server 100 may execute the transfer of the amount of remittance set in the allocation setting to the bank account set as the allocation destination account in the allocation setting, and then add the amount of electronic money equivalent to the remaining amount after subtracting the amount of remittance from the salary to the electronic wallet held by the service user UB.

[0055] Furthermore, the payment server 100 may provide the service user UB with suggested information regarding the setting of the next amount to be received by transmitting it to the user terminal 10 based on the service user UB's usage history of the electronic payment service. For example, the amount of usage on a monthly basis may be calculated, and an average usage amount for a certain period based on the calculated usage amount, or an amount of usage for the next month estimated from the calculated usage amount, may be proposed as the amount to be received in electronic money. The timing for the payment server 100 to provide the service user UB with suggested information regarding the setting of the next amount to be received may be any timing when the next amount to be received can be changed.

[0056] The payment server 100 may also provide the service user UB with proposal information by calculating, for example, a monthly reduction amount for the balance of the bank account that is the transfer destination account set by the service user UB as the transfer destination, and transmitting an amount equivalent to the calculated reduction amount as the remittance amount to be transferred to the transfer destination account to the user terminal 10. In this case, the payment server 100 can obtain information on the balance of the bank account that is the transfer destination account set by the service user UB as the transfer destination, using an API for accessing the affiliated bank server 30 provided by the affiliated bank Y. The timing for the payment server 100 to provide the service user UB with the proposal information on the proposed remittance amount may be any timing when the next remittance amount can be changed.

[0057] The settlement server 100 may also accept a setting of a scheduled date of deposit (arrival) in the receiving account from the service user UB in advance. In this case, the settlement server 100, for example, registers and manages information indicating the scheduled date of deposit set by the service user UB in the user information storage unit 124 in association with the user ID of the service user UB. Note that multiple settings of the information on the scheduled date of deposit may be accepted. For example, the service user UB may receive a one-time salary in addition to a regular salary from the company he / she works for. In this case, the service user UB realizes the allocation of the salary by setting a scheduled date of deposit (arrival) in the receiving account in advance. For example, the settlement server 100 checks whether the scheduled date of deposit set in advance by the service user UB matches the transfer date on which the company transferred the money to the receiving account, and then executes the allocation process. Alternatively, if there are multiple allocation settings associated with the service user UB, it checks whether there is an allocation setting with a matching transfer date, and if there is, executes the allocation process based on the relevant allocation setting. On the other hand, if the preset expected deposit date and the transfer date do not match, the payment server 100 may notify the service user UB, inquire as to whether or not to distribute the funds deposited in the receiving account, and accept an instruction from the service user UB. The payment server 100 may also accept the setting of the name information of the transfer source from the service user UB in advance. For example, if the service user UB has a side job, the salary may be transferred from multiple companies, and different distribution settings can be set for transfers from each company. For example, the payment server 100 checks whether there is a distribution setting in which the name preset by the service user UB matches the name of the transfer source for the receiving account, and if there is, executes a distribution process based on the corresponding distribution setting. On the other hand, if the name preset by the service user UB does not match the name of the transfer source, the payment server 100 may notify the service user UB, inquire as to whether or not to distribute the funds deposited in the receiving account, and if so, which distribution setting to apply, and accept an instruction from the service user UB.

[0058] Furthermore, the payment server 100 may accept, in the allocation setting, a pre-setting of a date for remittance and a setting of a date for adding to the money balance.

[0059] (1-4-2. Information provision in sorting service) Hereinafter, examples of information provision in the sorting service according to the embodiment will be described with reference to Fig. 3 and Fig. 4. Fig. 3 is a diagram showing an example (part 1) of information provision in the sorting service according to the embodiment. Fig. 4 is a diagram showing an example (part 2) of information provision in the sorting service according to the embodiment.

[0060] Fig. 3 shows an example of providing information regarding the scheduled arrival of funds in a receiving account to a service user UB. As shown in Fig. 3, when the bank server 20 accepts a transfer reservation from a company, it transmits the transfer reservation information to the affiliated bank server 30 (step S11). For example, the transfer reservation information includes information indicating the scheduled transfer date, the transfer account number, and the scheduled transfer amount.

[0061] When the affiliated bank server 30 receives the transfer reservation information from the bank server 20, it transmits it to the settlement server 100 as expected arrival information (step S12). For example, the expected arrival information includes information indicating the expected arrival date corresponding to the expected transfer date, the target account number corresponding to the transfer destination account number, and the expected arrival amount corresponding to the expected transfer amount. The transfer reservation information may also include information indicating the transfer source. In this case, the affiliated bank server 30 may transmit the expected arrival information to the settlement server 100 together with information indicating the transfer source.

[0062] When the payment server 100 receives the scheduled receipt information from the affiliated bank server 30, it refers to the information stored in the account information storage unit 121 to identify the target person corresponding to the scheduled receipt information (step S13). For example, the payment server 100 searches for a receiving account number that matches the target account number from among the receiving account numbers stored in the account information storage unit 121, and identifies the user ID associated with the searched receiving account number, thereby identifying the target person (for example, service user UB) corresponding to the scheduled receipt information.

[0063] After identifying the target person, the settlement server 100 transmits the expected money arrival information to the user terminal 10 of the identified target person, thereby providing the expected money arrival information to the target person (step S14). At this time, the settlement server 100 may transmit the expected money arrival information including the expected money arrival date and the expected money arrival amount to the user terminal 10.

[0064] When the user terminal 10 receives the scheduled payment information from the payment server 100, the user terminal 10 notifies the service user UB by displaying the scheduled payment information J-1 in a pop-up format, for example, through a payment application. Note that the display format of the scheduled payment information J-1 on the user terminal 10 is not limited to the pop-up format, and any display format can be adopted. The scheduled payment information J-1 shown in Figure 3 shows an example in which information related to the scheduled payment of salary, including the scheduled payment date and the scheduled payment amount, is displayed.

[0065] In addition, the payment server 100 may check the distribution settings corresponding to the service user UB, and display information indicating the distribution process schedule in the payment schedule information J-1.

[0066] In addition, the payment server 100 may include, in response to an operation by the service user UB, an object that transitions to a process for setting salary allocation in the payment schedule information J-1.

[0067] Furthermore, when the expected arrival information includes information indicating the transfer source, the settlement server 100 may display the expected arrival information including the information indicating the transfer source.

[0068] In addition, based on the reception history of expected remittance information including information indicating the same transfer source, if the expected remittance date contained in the expected remittance information received from the affiliated bank server 30 is different from a previous expected remittance date, the payment server 100 may include this fact in the expected remittance information J-1 and display it.

[0069] Furthermore, when the payment server 100 has received a setting of a scheduled deposit (receipt) date for the receiving account from the service user UB in advance, it may check whether the scheduled deposit (receipt) date preset by the service user UB matches the scheduled deposit date included in the scheduled deposit information, and if they match, it may display information indicating the schedule for the allocation process. Furthermore, when the payment server 100 has received a setting of a remitter's name for the receiving account from the service user UB in advance, it may check whether the remitter's name preset by the service user UB matches the remitter's name included in the scheduled deposit information, and if they match, it may display information indicating the schedule for the allocation process.

[0070] Furthermore, the payment server 100 refers to the usage history of the electronic payment service corresponding to the service user UB to be processed, and determines whether the service user UB has a debt (such as a deferred payment or a utility bill payment) that needs to be settled in the electronic payment service. If the payment server 100 determines that the service user UB has a debt, it may provide the service user UB with proposal information for proposing the settlement of the debt, together with the scheduled receipt information J-1. Furthermore, the payment server 100 may propose the settlement of the debt only when the service user UB has a debt and the debt is less than the amount included in the scheduled receipt information (when the debt can be paid).

[0071] Fig. 4 shows an example of notification when notifying the service user UB of information related to the distribution process. The processing procedure of steps S21 to S23-1, 2 shown in Fig. 4 is the same as the processing procedure of steps S03 to S05-1, 2 shown in Fig. 1. That is, the affiliated bank server 30 sends a receipt notification to the payment server 100 (step S21). Upon receiving the receipt notification from the affiliated bank server 30, the payment server 100 specifies the distribution settings (step S22), sends a remittance instruction to the affiliated bank server 30 (step S23-1), and adds the balance to the electronic wallet (step S23-2).

[0072] Then, when the payment server 100 completes the sorting process (steps S22 to S23-1, 2), it notifies the service user UB, who is a party to the sorting process, of the information on the sorting process by transmitting information J-2 to J-4 on the sorting process to the user terminal 10 (step S24). When the user terminal 10 receives the information J-2 to J-4 on the sorting process from the payment server 100, it notifies the service user UB by displaying the information J-2 to J-4 on the sorting process in a pop-up format, for example, via the payment app. Note that the display format of the information J-2 to J-4 on the sorting process in the user terminal 10 is not limited to the pop-up format, and any display format can be adopted.

[0073] For example, information J-2 on allocation processing transmitted from the payment server 100 to the user terminal 10 corresponds to information for notifying the service user UB that a remittance has been made to Bank M-1 for living expenses. Information J-3 on allocation processing transmitted from the payment server 100 to the user terminal 10 corresponds to information for notifying the service user UB that a remittance has been made to Bank M-2 for a mortgage. Information J-4 on allocation processing transmitted from the payment server 100 to the user terminal 10 corresponds to information for notifying the service user UB that the money balance of the electronic wallet held by the service user UB has been increased (charged).

[0074] (1-4-3. Use of financial services through allocation services) Hereinafter, an example of using financial services through the sorting service according to the embodiment will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of using financial services through the sorting service according to the embodiment.

[0075] As described above, the payment server 100 accepts from the service user UB a distribution setting including at least one distribution destination account to which the salary is to be distributed, the amount to be remitted to the distribution destination account, and a name indicating the purpose of use of the distribution destination account or the purpose of distribution. This allows the payment server 100 to allow the service user UB to understand at a glance how the salary is to be used.

[0076] The payment server 100 can then accept settings for a financial service linked to the electronic payment service from the service user UB as one of the destinations for distributing the salary. For example, as shown in Fig. 5, the service user UB executes settings for using the financial service through a payment application running on the user terminal 10 (step S31).

[0077] When the payment server 100 receives the usage settings for the financial service from the service user UB, it registers the usage settings for the financial service in association with the user ID of the service user UB (step S32). Then, the payment server 100 receives a notification of receipt of money from the partner bank server 30, for example, and executes a distribution process similar to that shown in FIG. 1 (step S33).

[0078] Hereinafter, an overview of the usage settings of the financial service according to the embodiment will be described with reference to Fig. 5. For example, when the tab included in the screen switching tab display area A1-1 is switched to a specific tab by the service user UB, as shown in Fig. 3, the user terminal 10 displays a setting screen G3-1 for accepting settings related to the management of salary received as electronic money (display example EX3-1).

[0079] The setting screen G3-1 is provided with an automatic allocation setting reception area A2-1 for receiving from the service user UB a selection of automatic allocation settings of salary by the settlement server 100. The automatic allocation setting reception area A2-1 shown in Fig. 5 illustrates three methods of automatic allocation setting selectable by the service user UB: "Conscientious", "Balanced", and "Aggressive". The automatic allocation setting reception area A2-1 shown in Fig. 5 also illustrates an example in which "Balanced" has been selected as the automatic allocation setting method, and displays information indicating the ratios of savings, asset management, and living expenses to salary.

[0080] In addition, the user terminal 10 displays an operation screen G3-2 when the automatic salary allocation setting is selected in response to the operation of the service user UB on the button B2-1 on the setting screen G3-1 (display example EX3-2). The operation screen G3-2 shown in FIG. 5 includes an area A3-1 in which information on the amount of salary to be allocated to savings (hereinafter referred to as "savings amount") is displayed, an area A3-2 in which information on the amount of salary to be allocated to asset management (hereinafter referred to as "asset management amount") is displayed, and an area A3-3 in which information on payment and remittance from salary is displayed. The information on the savings amount displayed in the area A3-1 and the information on the asset management amount displayed in the area A3-2 are automatically calculated, for example, by the payment server 100 according to the "balanced" allocation allocation selected by the service user UB on the setting screen G3-1, and are displayed on the user terminal 10 through the payment application. The information on payroll payments and remittances displayed in area A3-3 may be manually registered by the service user UB as information on fixed expenses that are paid at a predetermined timing, or may be automatically displayed based on prior registration by the service user UB. An editing function may be associated with area A3-3. In this case, area A3-3 is configured to allow the information on payroll payments and remittances to be arbitrarily edited according to the operation of the service user UB.

[0081] In addition, the user terminal 10 displays an operation screen G3-3 when manual setting of the salary investment amount is selected in response to the operation of the button B2-2 on the setting screen G3-1 by the service user UB (display example EX3-3). The operation screen G3-3 shown in FIG. 5 includes an area A4-1 in which information on the savings amount is displayed, an area A4-2 in which information on the asset investment amount is displayed, and an area A4-3 in which information on payment from salary and remittance is displayed. The information on the savings amount from salary displayed in the area A4-1 and the asset investment amount displayed in the area A4-2 are manually set by the service user UB on the operation screen G3-3. A setting function is associated with the areas A4-1 and A4-2, and the setting function can be activated in response to the operation of the service user UB. The setting function associated with the areas A4-1 and A4-2 may be configured to be capable of accepting the setting of the savings amount and the asset investment amount by specifying the amount, or may be configured to be capable of accepting the setting of the savings amount and the asset investment amount by specifying the ratio to the salary (total amount). 5 shows an example in which the savings amount and asset management amount are set by specifying the ratio to the (total amount of) salary. When the settlement server 100 accepts the setting of the savings amount and asset management amount by specifying the ratio to the (total amount of) salary, the settlement server 100 may accept the specification of the ratio for each type of savings and each asset management product.

[0082] Furthermore, the payment server 100 can request the service user UB to open a specified account for transferring funds to a business providing a financial service linked to the electronic payment service, as a condition for using the financial service. For example, the payment server 100 can request the service user UB to open a bank account for accepting and managing savings from salary at Bank Y, which is an affiliated bank of the business UA providing the electronic payment service. The payment server 100 can also request the service user UB to open a securities account for transferring investment assets from salary at a securities company affiliated with the business UA providing the electronic payment service.

[0083] (1-4-4. Information management in sorting services) An example of information management in the sorting service according to the embodiment will be described below with reference to Fig. 6. Fig. 6 is a diagram showing an example of information management in the sorting service according to the embodiment.

[0084] The payment server 100 can grasp the salary receipt and disbursement status of the service user UB based on the history of the allocation process executed according to the allocation setting corresponding to the service user UB and the history of use of the electronic payment service. In this way, the payment server 100 can provide the service user UB with information based on the salary receipt and disbursement status. Specifically, the payment server 100 manages each piece of information indicating the salary deposit history, the history of use of the electronic payment service, the history of remittance of the deposited salary to other bank accounts, the history of deposits and withdrawals of the deposited salary to other financial services, and the history of sending and receiving electronic money with other service users who use the electronic payment service, in association with the user ID of one payment service (for example, user identification information for identifying the service user UB). The payment server 100 can provide each service user with information based on the salary receipt and disbursement status by managing the above-mentioned various pieces of information for each service user.

[0085] For example, as shown in Fig. 6, the service user UB transmits a request for providing expenditure information through a payment application running on the user terminal 10 (step S41). When the payment server 100 receives the request for providing expenditure information from the service user UB, it acquires expenditure information corresponding to the service user UB (step S42). Then, the payment server 100 provides the acquired expenditure information to the service user UB (step S43).

[0086] Hereinafter, an example of expenditure information provided to the service user UB in the sorting service according to the embodiment will be described with reference to Fig. 6. For example, when the service user UB switches a tab included in the screen switching tab display area A1-1 to a specific tab, as shown in Fig. 6, the expenditure information display screen G4-1 displaying the expenditure information provided from the payment server 100 is displayed on the user terminal 10 (display example EX4-1).

[0087] In addition, in response to the service user UB's operation on the expenditure information display screen G4-1, the user terminal 10 displays a household accounting information display screen G4-2 (display example EX4-2), which displays household accounting information that organizes expenditures from the service user UB's salary by item based on the service user UB's allocation processing history and the service user UB's usage history of the electronic payment service.

[0088] The household accounting information displayed on the household accounting information display screen G4-2 can be displayed, for example, by month in response to a request from the service user UB. In addition, the household accounting information shown in FIG. 6 displays expenditure information corresponding to each expense item, such as "living expenses", "savings", "investment", "tuition / education", and "insurance". The expense item is identification information given to each breakdown of expenditure in order to organize expenditures in the household accounting information, and may be the same as or partially overlap with the information indicating the purpose of use or purpose of allocation in the allocation setting. The expense item may be automatically given by the payment server 100 to the expenditure information included in the distribution processing history of the service user UB and the usage history of the electronic payment service of the service user UB according to the registration information specified in advance, or a tag set to the expenditure information included in the distribution processing history of the service user UB and the usage history of the electronic payment service of the service user UB may be used. The payment server 100 generates household accounting information by organizing the expenditure information by expense item based on the history of allocation processing of the service user UB and tags indicating the expense items assigned to the expenditure information included in the usage history of the electronic payment service of the service user UB. The payment server 100 then provides the generated household accounting information to the service user UB by transmitting it to the user terminal 10. Note that the payment server 100 can also accept from the service user UB the setting of tags to be assigned to the expenditure information when allocation settings are made. In this case, the payment server 100 can automatically assign tags to the expenditure information based on the tag settings accepted from the service user UB when executing allocation processing. This eliminates the need for the payment server 100 to assign tags to the expenditure information itself, improving the convenience of the service user UB.

[0089] Furthermore, the payment server 100 may accept, for each of a plurality of receiving accounts, information indicating the name for identifying funds deposited in the receiving account as income. In this case, the payment server 100 may automatically assign a tag to information on deposits (received funds) into a receiving account with the name of salary, indicating whether the deposit (received funds) is with the name of salary or not. Furthermore, when funds that were used for fund management are returned to electronic money, the payment server 100 may automatically assign a tag indicating that the funds were used for asset management. Furthermore, the payment server 100 may also tag receipt of electronic money, such as a personal remittance of electronic money from another service user. In this way, the payment server 100 can also include the deposit (received funds) information (i.e., information on the income of the service user UB) in the household account book information.

[0090] In addition, the payment server 100 may display information indicating which history the amount is from, that is, the history from which the information is obtained, in association with the expense item as the household accounting information to be generated. For example, the payment server 100 may link the expenditure amount to the expense item and also to a withdrawal route such as a bank transfer, an electronic money remittance, the use of an electronic payment service, or a financial service deposit, and may display information for each withdrawal route such as a bank transfer of 50,000 yen and an electronic money remittance of 20,000 yen as a breakdown of the living expenses of 123,000 yen displayed on the household accounting information display screen G4-2 shown in FIG. 6.

[0091] [2. Payment Server Configuration] Next, the configuration of the payment server 100 will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of the configuration of the payment server 100 according to the embodiment. As shown in Fig. 7, the payment server 100 includes a communication unit 110, a storage unit 120, and a control unit 130.

[0092] (Regarding communication unit 110) The communication unit 110 is realized by, for example, a network interface card (NIC) etc. The communication unit 110 is connected to the network N by wire or wirelessly, and transmits and receives information to and from the user terminal 10, the affiliated bank server 30, etc.

[0093] (Regarding the storage unit 120) The storage unit 120 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. 7, the storage unit 120 has an account information storage unit 121, a distribution setting storage unit 122, a distribution history storage unit 123, and a user information storage unit 124.

[0094] (Regarding the account information storage unit 121) The account information storage unit 121 stores information indicating the correspondence between a service user (for example, service user UB) and a receiving account. Fig. 8 is a diagram showing an example of information stored in the account information storage unit 121 according to an embodiment. As shown in Fig. 8, the information indicating the correspondence stored in the account information storage unit 121 has an item for "user ID" and an item for "receiving account number".

[0095] The "User ID" field stores a user ID, which is a unique identification given to each service user in order to uniquely identify the service user in the electronic payment service. The "Receipt Account Number" field stores a receipt account number for identifying the receipt account issued to the service user. The receipt account is a virtual account for receiving salary in both electronic money and cash.

[0096] For example, FIG. 8 shows an example in which the receiving account number for identifying the receiving account assigned to the service user identified by the user ID "U#001" is "VA#001."

[0097] (Regarding the distribution setting storage unit 122) The distribution setting storage unit 122 stores information on distribution settings indicating the distribution destination of the salary for each service user. For example, the information on distribution settings includes at least one distribution destination account to which the salary is distributed, the amount to be remitted to the distribution destination account, and a setting of a name indicating the purpose of use of the distribution destination account or the purpose of distribution. The distribution setting storage unit 122 may also store information on multiple distribution settings for each service user. In this case, in addition to an identifier linked to the information on each distribution setting, information indicating the transfer source, such as the name information of the transfer source, information indicating the scheduled date of deposit, or an arbitrary name that specifies the transfer setting accepted from the user, may be linked and stored. FIG. 9 is a diagram showing an example of information on distribution settings stored in the distribution setting storage unit 122 according to the embodiment.

[0098] 9, the information on the distribution setting stored in the distribution setting storage unit 122 has an item of "user ID" and an item of "distribution setting." These items in the information on the distribution setting are associated with each other.

[0099] The "user ID" field stores a user ID, which is unique identification information given to each service user in order to uniquely identify the service user in the electronic payment service. For example, the user ID stored in the "user ID" field of the information on the distribution setting is the same as the user ID stored in the "user ID" field of the information indicating the correspondence stored in the account information storage unit 121 described above.

[0100] The "Distribution Settings" field includes the fields "Destination Account", "Remittance Amount", and "Nominal". The "Destination Account" field stores information for identifying the account to which the salary is distributed. For example, if the destination account is a bank account, information indicating the account number for identifying the bank account is stored. The "Remittance Amount" field stores information indicating the amount to be transferred to the destination account. The "Nominal" field stores information indicating the purpose of use of the "Destination Account" or the purpose of distribution.

[0101] FIG. 9 shows that a service user identified by a user ID "U#001" remits "220,000 yen" to "M-1 Bank (ordinary) 111111" under the pretext of "living expenses" as information preset as a salary allocation destination. The payment server 100 may receive the implementation date of the allocation process from the service user in advance as an allocation setting. In this case, the payment server 100 stores information indicating the implementation date of the allocation process in the allocation setting storage unit 122 in association with the user ID.

[0102] (Regarding the sorting history storage unit 123) The distribution history storage unit 123 stores, for each service user, a distribution history that is a history of distribution processing executed according to the distribution setting. FIG. 10 is a diagram showing an example of a distribution history stored in the distribution history storage unit 123 according to the embodiment. As shown in FIG. 10, the distribution history stored in the distribution history storage unit 123 has a plurality of items such as a "user ID", an "distribution date", an "amount deposited", an "allocation destination", an "amount remitted", and an "nominal". These items in the distribution history are mutually associated. Note that the distribution history storage unit 123 does not need to be particularly limited to the example described below, and may store, as the history of distribution processing, information indicating a salary deposit history, a history of use of an electronic payment service, a history of remittance of a deposited salary to a bank account, a history of deposits and withdrawals to other financial services, and a history of sending and receiving electronic money with other users who use an electronic payment service.

[0103] The "user ID" field stores a user ID, which is unique identification information given to each service user in order to uniquely identify the service user in the electronic payment service. For example, the user ID stored in the "user ID" field of the sorting history is the same information as the user ID stored in the "user ID" field of the information indicating the correspondence stored in the account information storage unit 121 described above.

[0104] The "Allocation Date" field stores information indicating the date on which the allocation process was carried out in accordance with the allocation settings. The "Deposit Amount" field stores information indicating the amount of salary deposited into the receiving account. The "Allocation Destination" field stores information (account number) indicating the allocation destination account to which the money was transferred by the allocation process, and information (wallet ID) indicating the electronic wallet to which the balance was added by the allocation process. The "Remittance Amount" field stores information indicating the remittance amount transferred by the allocation process. The "Nominal" field stores information indicating the purpose of use of the allocation destination or the purpose of the allocation.

[0105] For example, FIG. 10 shows that on December 25, 20XX, a distribution process was performed on a salary of 300,000 yen deposited in a receiving account of a service user identified by a user ID "U#001". FIG. 10 also shows that on December 25, 20XX, 220,000 yen of the 300,000 yen salary was transferred to an ordinary account of M-1 Bank identified by an account number "111111" under the name of living expenses. FIG. 10 also shows that on December 25, 20XX, 30,000 yen of the 300,000 yen salary was transferred to an ordinary account of M-2 Bank identified by an account number "222222" under the name of a mortgage. FIG. 10 also shows that on December 25, 20XX, 50,000 yen of the 300,000 yen salary was added to the money balance of an electronic wallet identified by a wallet ID "Wallet#001".

[0106] (Regarding the user information storage unit 124) The user information storage unit 124 stores user information related to a service user. FIG. 11 is a diagram showing an example of user information stored in the user information storage unit 124 according to an embodiment. As shown in FIG. 11, the user information stored in the user information storage unit 124 includes information related to the service usage history of the electronic payment service by the service user. The user information stored in the user information storage unit 124 has multiple items such as a "user ID" item, a "date of use" item, a "store used" item, a "payment amount", a "payment method" item, a "money balance" item, a "deferred payment" item, a "financial service" item, and a "payment / remittance" item. These items in the user information are mutually associated.

[0107] The "user ID" field stores a user ID, which is unique identification information given to each service user in order to uniquely identify the service user in the electronic payment service. For example, the user ID stored in the "user ID" field of the sorting history is the same information as the user ID stored in the "user ID" field of the information indicating the correspondence stored in the account information storage unit 121 described above.

[0108] The "date of use" field stores information indicating the date when the payment for a product or service was made using the electronic payment service, or when electronic money was charged (added to the balance) to the electronic wallet used in the electronic payment service. The "store used" field stores information indicating the store (affiliated store that introduces the electronic payment service) where the payment for a product or service was made using the electronic payment service, or information indicating the bank, credit card company, etc. used by the service user to charge electronic money to the electronic wallet (add to the balance), etc.

[0109] The "payment amount" field stores information indicating the amount of withdrawal or deposit made by using the electronic payment service. The "payment method" field stores information indicating whether the service user has made an immediate payment or a deferred payment through the electronic payment service. The "money balance" field stores information indicating the money balance at the time when the service user used the electronic payment service. The "money balance" field includes a normal money balance (payment balance) charged by the service user through the payment app and a money balance when a part of salary is received as electronic money, and each balance is managed separately. For example, the payment server 100 manages the funds that are deposited in the receiving account linked to the service user and are allocated as the amount to charge the electronic wallet as electronic money corresponding to the salary. The "deferred payment" field stores information indicating whether the service user has registered to use deferred payment as a payment method for the electronic payment service.

[0110] The "Financial services" item includes a "Savings" item, which is one of the financial services linked to the electronic payment service, and an "Operation" item, which is another of the financial services linked to the electronic payment service. When a service user registers to use a financial service, various information set by the service user at the time of registration to use the financial service is stored as usage registration information in the "Savings" and "Operation" items. For example, the usage registration information includes information indicating the amount of use of the financial service, such as the savings amount and the asset management amount, and information indicating a specified account to which the usage amount is allocated. The "Payment / Remittance" item stores payment and remittance information, including information on the payment of a specified amount from an electronic wallet by the service user using an electronic payment service, and information on remittance to other service users, etc.

[0111] FIG. 11 shows that a service user identified by user ID "U#001" charged 10,000 yen worth of electronic money through M-1 Bank on December 12, 20XX. FIG. 11 also shows that the service user identified by user ID "U#001" has not registered to use deferred payment as a payment method. FIG. 11 also shows that the user information corresponding to the service user identified by user ID "U#001" includes registration information for financial services related to savings and investment, and payment and remittance information related to payments and remittances.

[0112] (Regarding the control unit 130) The control unit 130 is a controller, and is realized, for example, by a central processing unit (CPU) or a micro processing unit (MPU) executing various programs stored in a storage device inside the payment server 100 using a RAM as a working area. The control unit 130 can also be realized, for example, by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0113] As shown in FIG. 5, the control unit 130 according to the embodiment has a receiving unit 131, an allocation processing unit 132, and a providing unit 133, and these units realize or execute the functions and actions of the information processing described below.

[0114] (Regarding the reception unit 131) The reception unit 131 receives from the service user a distribution setting that specifies multiple distribution destinations, including an electronic wallet held by the service user in the electronic payment service, as the distribution destination of funds (e.g., salary) to be deposited in a predetermined bank account that is linked to the service user in advance. Here, the predetermined bank account that is linked to the service user in advance is a receiving account for receiving at least a part of the funds linked to the service user in electronic money, and is arbitrarily assigned to the service user from among virtual accounts borrowed by the business operator operating the electronic payment service (e.g., business operator UA) from its partner, Bank Y. The receiving account is linked to a bank account that is a real account held by the business operator operating the electronic payment service at Bank Y, and remittances to the receiving account are deposited into the real account.

[0115] The reception unit 131 may also receive from the service user a setting of a receipt amount indicating an amount of funds to be received in electronic money. The reception unit 131 registers information indicating the receipt amount set by the service user in the allocation setting storage unit 122 in association with the user ID of the service user.

[0116] Alternatively, the reception unit 131 may receive from the service user a setting of a receiving ratio indicating the ratio of the receiving amount to the funds, instead of the receiving amount. In this case, the reception unit 131 registers information indicating the receiving ratio set by the service user in the allocation setting storage unit 122 in association with the user ID of the service user.

[0117] Furthermore, the reception unit 131 may receive the setting of the above-mentioned receiving amount or receiving ratio from the service user through a setting screen of a payment application provided to the service user (an example of a "predetermined user interface").

[0118] The reception unit 131 may also receive from the service user settings of at least one transfer destination account to which funds are to be transferred and a transfer amount corresponding to the transfer destination account. In this case, the reception unit 131 registers each piece of information indicating the transfer destination account set by the service user and the transfer amount corresponding to the transfer destination account in the transfer setting storage unit 122 in association with the user ID of the service user.

[0119] In addition, the reception unit 131 may receive information indicating the above-mentioned destination account and the remittance amount corresponding to the destination account from the service user through a setting screen of a payment application provided to the service user (an example of a "specified user interface").

[0120] Alternatively, the reception unit 131 may receive from the service user a remittance ratio setting indicating the ratio of the remittance amount to the funds instead of the remittance amount. In this case, the reception unit 131 registers information indicating the remittance ratio set by the service user in the allocation setting storage unit 122 in association with the user ID of the service user.

[0121] The reception unit 131 may also receive from the service user, as information regarding allocation settings, settings of each piece of information, such as a destination account to which funds deposited in a specified bank account previously linked to the service user are to be allocated, a remittance amount to the destination account, and a name indicating the purpose of use of the destination account or the purpose of allocation, from the service user. In this case, the reception unit 131 registers, in the allocation setting storage unit 122, each piece of information, such as the destination account set by the service user, the remittance amount corresponding to the destination account, and a name indicating the purpose of use of the destination account or the purpose of allocation, in association with the user ID of the service user.

[0122] The reception unit 131 may also receive information on the above-mentioned destination account, the remittance amount corresponding to the destination account, and the purpose of use of the destination account or the name indicating the purpose of the transfer from the service user through a setting screen of a payment application provided to the service user (an example of a "predetermined user interface"). The reception unit 131 may also receive information indicating the name for each of a plurality of predetermined bank accounts.

[0123] In addition, the receiving unit 131 may receive scheduled deposit information indicating the scheduled deposit of funds to a specified bank account that is linked in advance to the service user from Bank Y, which is an affiliate of a business operator (for example, business operator UA) that operates an electronic payment service.

[0124] The reception unit 131 may also receive information indicating a ratio to the funds from the service user as information for specifying the allocation amount to be allocated to a predetermined financial service linked to the electronic payment service. In this case, the reception unit 131 registers the information indicating the allocation amount to be allocated to the predetermined financial service (ratio to the funds) in the user information storage unit 124 in association with the user ID of the service user.

[0125] (Regarding the sorting processing unit 132) When a deposit into a specified bank account is confirmed (when a notification of receipt of funds is received from the affiliated bank server 30), the allocation processing unit 132 executes allocation processing to allocate the deposited funds to the specified bank account based on the allocation settings corresponding to the target service user.

[0126] Furthermore, when the allocation setting corresponding to the target service user includes a setting for the amount of electronic money to be received as electronic money, the allocation processing unit 132 may add an amount of electronic money equivalent to the amount of ...

[0127] In addition, if the allocation setting corresponding to the target service user includes a receipt ratio setting indicating the ratio of the receipt amount to the funds, the allocation processing unit 132 may calculate the receipt amount based on the funds and the receipt ratio, and add electronic money in an amount equivalent to the calculated receipt amount to the electronic wallet.

[0128] In addition, when the allocation settings corresponding to the target service user include settings for at least one destination account to which funds are to be allocated and a transfer amount corresponding to the destination account, the allocation processing unit 132 may execute a transfer from a specified bank account to the destination account in accordance with the settings of the destination account and the transfer amount.

[0129] In addition, if the allocation setting corresponding to the target service user includes a remittance ratio setting indicating the ratio of the remittance amount to the funds, the allocation processing unit 132 may calculate the remittance amount based on the remittance ratio, and execute a transfer from the specified bank account to the destination account based on the calculated remittance amount.

[0130] The allocation processor 132 may also calculate an allocation amount to be allocated to a predetermined financial service linked to an electronic payment service based on information indicating a ratio to funds deposited in a predetermined bank account linked to the target service user, and execute allocation processing to allocate an amount equivalent to the calculated allocation amount to a predetermined account for using the predetermined financial service. For example, the allocation processor 132 may allocate cash in an amount equivalent to the allocation amount from a predetermined bank account to a predetermined account, or allocate electronic money in an amount equivalent to the allocation amount from the balance of an electronic wallet to a predetermined account.

[0131] In addition, the allocation processing unit 132 may determine whether to directly allocate cash in an amount equivalent to the allocation amount from a specified bank account to a specified account, or to allocate electronic money in an amount equivalent to the allocation amount from the balance of the electronic wallet to a specified account, depending on the type of payment method available in the specified financial service. For example, if the payment method available in the specified financial service is "cash only", the allocation processing unit 132 directly allocates cash in an amount equivalent to the allocation amount by transferring it from the specified bank account to the specified account. In addition, for example, the allocation processing unit 132 may determine whether to directly allocate cash in an amount equivalent to the allocation amount from a specified bank account to a specified account, or to allocate electronic money in an amount equivalent to the allocation amount from the balance of the electronic wallet to a specified account, according to the settings of the service user. Note that, if both "cash" and "electronic money" are available as payment methods in the specified financial service, the allocation processing unit 132 may determine whether to directly allocate cash from a specified bank account to a specified account, or to allocate electronic money from the balance of the electronic wallet to a specified account, according to the settings of the service user.

[0132] The allocation processing unit 132 may also execute allocation processing for allocating an amount of electronic money equivalent to the allocation amount from the money balance corresponding to the salary among the money balances of the electronic wallet held by the service user to a predetermined account. For example, when a part of the salary received in electronic money is used for savings, the allocation processing unit 132 can execute allocation processing related to the savings of the service user by transferring an amount equivalent to the allocation amount from a real account held by the business entity UA in Bank Y and linked to a receiving account corresponding to the service user to a savings bank account opened by the service user in Bank Y, and subtracting an amount of electronic money equivalent to the allocation amount from the money balance corresponding to the salary of the service user. In addition, when part of the salary received in electronic money is to be used for asset management, the allocation processing unit 132 can perform allocation processing related to the service user's asset management by transferring an amount equivalent to the allocation amount from a real account held by business operator UA at Bank Y, which is linked to the receiving account corresponding to the service user, to a bank account opened by the service user at Bank Y for depositing money into a securities account, and by subtracting electronic money in an amount equivalent to the allocation amount from the money balance corresponding to the service user's salary.

[0133] Furthermore, when there are multiple transfer settings corresponding to the target service user, the distribution processing unit 132 may select a distribution setting corresponding to the funds deposited in the receiving account (i.e., indicating the distribution destination of the deposited funds) based on the contents of the setting information included in the transfer setting. For example, a distribution setting is selected based on the information on the expected deposit date and the account holder information of the transfer source set in the distribution setting, and distribution processing is performed based on the selected distribution setting.

[0134] (About the provider 133) The providing unit 133 provides the service user with suggested information regarding the setting of the next amount to be received, based on the service user's usage history of the electronic payment service.

[0135] Furthermore, the providing unit 133 can provide the service user with information on the distribution setting corresponding to the service user in response to a request from the service user, for example.

[0136] The providing unit 133 may also provide the service user with the expected money deposit information accepted by the accepting unit 131. At this time, the providing unit 133 may provide the service user with the expected money deposit information including the expected date and amount of money deposit into a specified bank account.

[0137] The providing unit 133 may also provide the service user with information indicating the schedule of the sorting process specified based on the sorting setting corresponding to the service user, together with the expected deposit information.

[0138] The providing unit 133 may also provide the service user with an object that transfers processing for setting distribution settings in response to an operation by the service user, together with the expected deposit information.

[0139] Furthermore, the providing unit 133 may provide the service user with information on the distribution process executed in accordance with the distribution setting corresponding to the service user.

[0140] In addition, the providing unit 133 may refer to the usage history of the electronic payment service corresponding to the service user to determine whether or not the service user has a debt that requires settlement in the electronic payment service (for example, whether or not there is a deferred settlement), and if it is determined that the service user has a debt, it may provide the service user with proposal information for suggesting settlement of the debt along with expected receipt information.

[0141] Furthermore, the providing unit 133, in response to a request from the service user, provides the service user with household account book information in which expenditures from the service user's funds are organized by expense item for identifying expenditures, based on the history of allocation processing and the history of use of the electronic payment service. The providing unit 133 may also provide the service user with household account book information in which funds are organized as income, based on the name corresponding to funds deposited in a specified bank account and the information of the funds deposited in the specified bank account. The providing unit 133 may also provide the service user with household account book information including information indicating the history from which the information of funds deposited in the specified bank account is obtained. The providing unit 133 may also provide the service user with household account book information in which funds deposited in a specified bank account are organized by the name indicating the purpose of use or allocation purpose.

[0142] [3. Example of processing procedure] (3-1. Payment Schedule Provisioning Process) An example of the processing procedure in the payment server 100 according to the embodiment will be described below. First, an example of the processing procedure of the remittance schedule providing process according to the embodiment will be described with reference to FIG. 12. FIG. 12 is a flowchart showing an example of the processing procedure of the remittance schedule providing process executed by the payment server 100 according to the embodiment. The processing procedure shown in FIG. 12 is executed by the control unit 130 of the payment server 100. The control unit 130 repeatedly executes the processing procedure shown in FIG. 12 while the payment server 100 is operating.

[0143] As shown in FIG. 12, the providing unit 133 determines whether or not the receipt of money schedule information has been received from the affiliated bank server 30 (Step S101).

[0144] When the providing unit 133 determines that it has received the scheduled remittance information from the partner bank server 30 (step S101; Yes), it identifies the target user who is the target service user based on the received scheduled remittance information (step S102). Then, the providing unit 133 provides the scheduled remittance information to the identified target user (step S103), and ends the processing procedure shown in FIG.

[0145] Furthermore, in the above-mentioned step S101, if the providing unit 133 determines that no remittance schedule information has been received from the affiliated bank server 30 (step S101; No), the processing procedure shown in FIG. 12 ends.

[0146] (3-2. Allocation process) Hereinafter, an example of the processing procedure of the allocation process according to the embodiment will be described with reference to Fig. 13. Fig. 13 is a flowchart showing an example of the processing procedure of the allocation process executed by the payment server 100 according to the embodiment. The processing procedure shown in Fig. 13 is executed by the control unit 130 included in the payment server 100. The control unit 130 repeatedly executes the processing procedure shown in Fig. 13 while the payment server 100 is operating.

[0147] As shown in FIG. 13, the distribution processor 132 determines whether or not a payment has been deposited in a receiving account linked to the service user (step S201).

[0148] When the distribution processing unit 132 determines that funds have been deposited in a receiving account linked to a service user (step S201; Yes), it refers to the information stored in the distribution setting memory unit 122 and identifies the distribution setting for the target user, who is the target service user (step S202).

[0149] Furthermore, the distribution processor 132 refers to the identified distribution setting and identifies information on the bank account of the target user to which the funds are to be distributed (step S203).

[0150] The remittance processor 132 also transmits a remittance instruction based on the identified remittance account and remittance amount to the affiliated bank server 30 (step S204).

[0151] Furthermore, the providing unit 133 provides the target user with information regarding the allocation process to the bank account (step S205).

[0152] The distribution processor 132 also determines whether or not the distribution destination of the target user's salary includes an electronic wallet in the distribution settings of the target user (step S206).

[0153] When the allocation processor 132 determines that the electronic wallet is the allocation destination of the target user's salary (step S206; Yes), it determines whether the money balance after allocation is equal to or less than a predetermined upper limit (step S207). That is, the allocation processor 132 determines whether the balance after adding the electronic money equivalent to the amount of receipt registered in the allocation setting to the electronic wallet is equal to or less than a predetermined amount.

[0154] When the sorting unit 132 determines that the money balance after sorting is equal to or less than the upper limit (step S207; Yes), it adds an amount equivalent to the amount of receipt corresponding to the target user according to the sorting setting to the balance (step S208). That is, the sorting unit 132 adds electronic money equivalent to the amount of receipt registered in the sorting setting to the electronic wallet.

[0155] The providing unit 133 also provides the target user with information regarding the allocation process to the electronic wallet (step S209), and ends the processing procedure shown in Fig. 13. That is, the providing unit 133 provides the target user with information that the electronic wallet has been charged with electronic money in an amount equivalent to the amount to be received.

[0156] In the above-mentioned step S207, if the allocation processor 132 determines that the money balance after allocation is not equal to or less than the predetermined upper limit (step S207; No), the process proceeds to the above-mentioned step S209. That is, the allocation processor 132 provides the target user with information that the electronic wallet cannot be charged because the balance is over the limit.

[0157] In the above-mentioned step S206, if the distribution processing unit 132 determines that there is no electronic wallet as the distribution destination of the target user's salary (step S206; No), the processing procedure shown in FIG. 13 ends.

[0158] In the above-mentioned step S201, if the distribution processing unit 132 determines that no money has been deposited in the receiving account linked to the service user (step S201; No), the processing procedure shown in FIG. 13 ends.

[0159] It is not necessary for the payment server 100 to execute the processing procedures shown in Fig. 13 in the order shown in Fig. 13. For example, the payment server 100 may execute the processing procedures shown in steps S206 to S209 before the processing procedures shown in steps S202 to S205. Moreover, the payment server 100 may simultaneously execute the information provision in step S205 and the information provision in step S209 after completing both the processing procedures in step S204 and the processing procedures in step S208.

[0160] 4. Modifications (4-1. Distribution of excess money) In the above embodiment, the payment server 100 adds (charges) the electronic wallet with an amount of electronic money equivalent to the amount of receipt, on the condition that the balance after adding the electronic money equivalent to the amount of receipt to the electronic wallet held by the service user (for example, the service user UB) does not exceed a predetermined amount that is set as the upper limit that can be secured in the electronic wallet. In addition, in the above embodiment, the payment server 100 provides the service user with information that the electronic wallet cannot be charged because the balance is over the predetermined amount when the balance after adding exceeds the predetermined amount. Here, the payment server 100 may provide the service user UB with information that the electronic wallet will be over the balance, as well as proposal information that proposes allocation of the amount in excess of the predetermined amount. Below, an overview of the information processing of the payment server 100 according to the modified example will be described. Note that, below, an example of information processing that proposes allocation of the amount in excess of the predetermined amount will be described, but the payment server 100 does not need to be limited to this example. For example, the payment server 100 may accept settings for allocation settings for excess amounts (settings for where to allocate the excess amount by specifying a percentage) in addition to the normal allocation settings, and allocate the excess amount based on the settings. Also, for example, the payment server 100 may accept in advance a selection of an allocation destination to which an excess amount is to be added from among the allocation destinations in the normal allocation settings, and automatically add the amount to the allocation amount to the corresponding allocation destination and allocate it. For example, when accepting the allocation settings, checking a checkbox for whether or not to allocate the excess amount by adding the amount to the excess amount is enabled.

[0161] 7 judges whether or not the balance after adding electronic money equivalent to the amount to be received set by the service user UB to the electronic wallet held by the service user UB exceeds a predetermined amount when the amount to be received is set by the service user U. If the allocation processing unit 132 judges that the balance after adding exceeds the predetermined amount, it notifies the provision unit 133 of the control unit 130.

[0162] When the allocation processing unit 132 determines that the post-addition balance exceeds a specified amount, the provision unit 133 provides the service user with information to the user terminal 10 via a payment app running on the user terminal 10, together with proposal information proposing the allocation of the excess amount of the post-addition balance that exceeds the specified amount, along with information that the post-addition balance will be an excess balance.

[0163] For example, the providing unit 133 may provide the service user with proposal information proposing to allocate the excess amount to a bank account specified as one of the salary allocation destinations in the allocation setting corresponding to the target service user. Furthermore, when the target service user is registered to use a financial service linked to an electronic payment service, the providing unit 133 may provide the service user with proposal information proposing to allocate the excess amount to the financial service being used. Furthermore, when the target service user is not registered to use a financial service, the providing unit 133 may suggest to register to use the financial service and provide the service user with proposal information proposing to allocate the excess amount to the financial service being used.

[0164] The providing unit 133 may also suggest an allocation destination based on the bank account registered as the allocation destination and the usage status of the financial service (for example, usage history). For example, in the case of a bank account, the providing unit 133 may determine an account that is frequently used as the allocation destination account based on a remittance history to the bank account that is accepted each time, rather than a bank account based on the remittance history or the remittance setting. In addition, for example, when the balance can be acquired using a balance API of an account registered as the bank account of the target service user, the providing unit 133 may determine, as the proposed allocation destination account, an account that has been used the most (for example, the cumulative number of times or the number of times in a specified period, etc.) based on the balance information, for example, when the speed at which the balance is reduced (for example, the reduction rate in a specified period) exceeds a threshold value or the balance is reduced to a certain amount or less. As with the case of a bank account, the providing unit 133 may also determine an allocation destination account for a financial service from among accounts linked to the financial service based on the remittance history or the balance of the user account of the service user linked to the financial service.

[0165] Furthermore, the providing unit 133 may, for example, inquire through the proposal information as to whether or not to allocate the excess amount. Then, when the providing unit 133 receives a response from the service user indicating that the allocation of the excess amount will be executed, the providing unit 133 communicates this to the allocation processing unit 132. The allocation processing unit 132 executes the allocation processing of the excess amount according to the response from the service user.

[0166] Furthermore, the reception unit 131 of the control unit 130 may receive in advance setting information specifying the distribution destination of the excess amount from the service user. In this case, the distribution processing unit 132 executes the distribution process of the excess amount based on the setting information corresponding to the target service user. Furthermore, the provision unit 133 may provide the service user with information indicating that the distribution process of the excess amount will be executed, by transmitting it to the user terminal 10 according to the preset setting information. Furthermore, when the distribution processing unit 132 executes the distribution process of the excess amount, the provision unit 133 may provide the service user with information indicating that the distribution process of the excess amount has been executed, by transmitting it to the user terminal 10.

[0167] (4-2. System configuration) In the above embodiment, an example has been described in which the payment server 100 included in the information processing system SYS performs processing related to an electronic payment service and also performs processing related to a distribution service in which the salary of a service user is distributed according to a distribution setting. However, the configuration of the information processing system SYS according to the embodiment does not need to be particularly limited to such an example, and the server device performing processing related to the electronic payment service and the server device performing processing related to the distribution service may be physically separate servers, or each server device may belong to a different system. In this case, each server device is connected to each other in a communicable manner in a state in which information required for each process can be exchanged in cooperation with each other.

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

[0169] In addition, each component of each device shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads, usage conditions, etc.

[0170] Furthermore, the above-described embodiments can be appropriately combined as long as the processing contents are not contradictory.

[0171] 5. Effects As described above, the payment server 100 according to the embodiment includes the reception unit 131 and the allocation processing unit 132. The reception unit 131 receives from the service user an allocation setting that specifies multiple allocation destinations, including an electronic wallet held by the user in the electronic payment service, as the allocation destination of funds deposited into a predetermined bank account that is linked to the service user in advance. When a deposit into the predetermined bank account is confirmed, the allocation processing unit 132 executes an allocation process that allocates funds based on the allocation setting corresponding to the target service user.

[0172] As a result, the payment server 100 according to the embodiment automatically distributes the salary of the service user according to the distribution setting of the service user in response to the deposit of the salary of the service user. As a result, the payment server 100 according to the embodiment can improve the convenience of the service related to the digital payment of salary.

[0173] The reception unit 131 also receives a setting of a receipt amount indicating an amount of funds to be received as electronic money from the service user. The allocation processing unit 132 also adds an amount of electronic money equivalent to the receipt amount to the electronic wallet held by the user on the condition that the balance after adding the amount of electronic money equivalent to the receipt amount to the electronic wallet held by the user does not exceed a predetermined amount. In this way, the payment server 100 according to the embodiment can provide the service user with a mechanism for automatically receiving, for example, a part of a salary as electronic money, thereby improving usability. In addition, when receiving a part of a salary as electronic money, the payment server 100 according to the embodiment controls the amount so that the amount does not exceed a predetermined amount within a predetermined upper limit, thereby improving usability while complying with laws and regulations in the money transfer business.

[0174] The reception unit 131 may also receive from the service user a setting of a receipt amount indicating the amount of funds to be received in electronic money. When the balance after adding electronic money of an amount equivalent to the receipt amount to the electronic wallet held by the service user exceeds a predetermined amount, the allocation processing unit 132 may pay out an amount equivalent to the excess amount exceeding the predetermined amount to a payout bank account preset by the service user.

[0175] Moreover, the reception unit 131 receives from the service user a setting of a reception ratio indicating the ratio of the reception amount to the funds, instead of the reception amount. Furthermore, the allocation processing unit 132 calculates the reception amount based on the funds and the reception ratio, and adds electronic money equivalent to the calculated reception amount to the electronic wallet. In this way, the payment server 100 according to the embodiment can increase the degree of freedom in setting the reception amount to be received as electronic money, and improve usability.

[0176] In addition, the reception unit 131 receives the setting of the amount to be received or the rate to be received from the service user through a predetermined user interface provided to the service user. As a result, the payment server 100 according to the embodiment can provide the service user with a mechanism for receiving the setting through a simple and intuitive operation, thereby improving usability.

[0177] The reception unit 131 also receives settings from the service user of at least one destination account to which funds are to be allocated and the amount to be transferred corresponding to the destination account. The allocation processing unit 132 also executes transfer from a specified bank account to the destination account according to the settings of the destination account and the amount to be transferred. In this way, the payment server 100 according to the embodiment can provide the service user with a mechanism for automatically transferring money from, for example, a salary, thereby improving usability.

[0178] In addition, the reception unit 131 receives settings of the destination account and the remittance amount from the service user through a predetermined user interface provided to the service user. As a result, the payment server 100 according to the embodiment can provide the service user with a mechanism for receiving settings through simple and intuitive operations, thereby improving usability.

[0179] Moreover, the reception unit 131 receives from the user a remittance ratio setting indicating the ratio of the remittance amount to the funds, instead of the remittance amount. The allocation processing unit 132 calculates the remittance amount based on the remittance ratio, and executes a remittance from a specified bank account to a destination account based on the calculated remittance amount. This allows the settlement server 100 according to the embodiment to increase the degree of freedom in setting the remittance amount, thereby improving usability.

[0180] Moreover, the payment server 100 according to the embodiment further includes a user information storage unit 124 and a providing unit 133. The user information storage unit 124 stores the service user's usage history of the electronic payment service in association with a user ID, which is user identification information for identifying the service user. The providing unit 133 provides the service user with suggested information regarding the setting of the next receiving amount based on the service user's usage history. As a result, the payment server 100 according to the embodiment can suggest to the service user, for example, an appropriate amount according to the usage status of the electronic payment service as the charge amount from salary, thereby improving usability.

[0181] Furthermore, when there are multiple allocation settings corresponding to the target service user, the transfer processing unit 132 selects an allocation setting corresponding to the funds based on the contents of the setting information included in the allocation setting, and executes the allocation process based on the selected allocation setting. This can further improve usability.

[0182] [6. Hardware Configuration] Moreover, the payment server 100 according to the above-mentioned embodiment and modification is realized, for example, by a computer 1000 having a configuration as shown in Fig. 14. Fig. 14 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server according to the embodiment and modification.

[0183] The computer 1000 has a CPU 1100, a RAM 1200, a ROM 1300, a HDD 1400, a communication interface (I / F) 1500, an input / output interface (I / F) 1600, and a media interface (I / F) 1700.

[0184] The CPU 1100 operates and controls each unit based on a program stored in the ROM 1300 or the HDD 1400. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 is started up, programs that depend on the hardware of the computer 1000, and the like.

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

[0186] The CPU 1100 controls output devices such as a display and a printer, and input devices such as a keyboard and a mouse, via the input / output interface 1600. The CPU 1100 acquires data from the input devices via the input / output interface 1600. The CPU 1100 also outputs data generated via the input / output interface 1600 to the output devices.

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

[0188] For example, when the computer 1000 functions as the payment server 100, the CPU 1100 of the computer 1000 executes a program loaded on the RAM 1200 to realize the function of the control unit 130. That is, the CPU 1100 realizes the processing by the payment server 100 according to the embodiment and the modified example in cooperation with the program (e.g., an information processing program) loaded on the RAM 1200. In addition, the HDD 1400 stores each data in the storage device of the payment server 100. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, these programs may be obtained from another device via a predetermined communication network.

[0189] [7. Other] Although some of the embodiments of the present application have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be embodied 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.

[0190] Further, the above-mentioned payment server 100 can be flexibly changed in configuration, for example, by calling an external platform or the like using an API (Application Programming Interface) or network computing, depending on the function.

[0191] Furthermore, the term "unit" in the claims may be read as "means" or "circuit," etc. For example, a control unit may be read as control means or a control circuit. [Explanation of symbols]

[0192] SYS Information Processing System 10 User terminal 20 Bank Server 30 Partner bank server 100 Payment Server 110 Communications Department 120 Storage section 121 Account information storage unit 122 Distribution setting memory unit 123 Distribution history memory unit 124 User information storage unit 130 Control section 131 Reception 132 Distribution processing unit 133 Provision Department

Claims

1. An information processing device that executes processing related to an electronic payment service provided to a user through an online system, When a deposit into a predetermined bank account corresponding to the electronic wallet held by the user is confirmed in the electronic payment service, a remittance processing unit executes a remittance based on a transfer setting for the bank account that has been preset. An information processing device comprising:

2. A reception unit capable of receiving, from the user, transfer settings that specify an electronic wallet held by the user in the electronic payment service as a transfer destination of funds to be deposited into a specified bank account.

2. The information processing apparatus according to claim 1, further comprising:

3. The reception unit Accepting from the user a setting of a receipt amount indicating an amount to be received in electronic money from the funds; The distribution processing unit Adding electronic money in an amount equivalent to the amount to be received to the electronic wallet held by the user, on the condition that the balance after adding the electronic money in an amount equivalent to the amount to be received does not exceed a predetermined amount.

3. The information processing apparatus according to claim 2, wherein:

4. The reception unit Accepting from the user a setting of a receiving ratio indicating a ratio of the receiving amount to the funds instead of the receiving amount; The distribution processing unit Calculating the amount to be received based on the funds and the receiving rate, and adding electronic money equivalent to the calculated amount to be received to the electronic wallet.

4. The information processing apparatus according to claim 3,

5. The specified bank account is pre-linked to the user.

5. The information processing apparatus according to claim 4,

6. The reception unit: Accepting transfer settings from the user that designate an electronic wallet held by the user in the electronic payment service as a transfer destination for funds transferred to a virtual account linked to the user; The distribution processing unit When a deposit into the virtual account is detected, electronic money equivalent to the amount deposited into the virtual account is added to the electronic wallet of the user to which the virtual account is assigned.

6. The information processing apparatus according to claim 5,

7. An information processing method carried out by a computer that executes processing related to an electronic payment service provided to a user through an online system, a remittance processing step of executing a remittance based on a transfer setting for a predetermined bank account when a deposit into a predetermined bank account corresponding to the electronic wallet held by the user is confirmed in the electronic payment service; An information processing method comprising:

8. A computer that executes processing related to electronic payment services provided to users through an online system, a remittance processing procedure for executing remittance based on a transfer setting for a predetermined bank account when a deposit into a predetermined bank account corresponding to an electronic wallet held by the user is confirmed in the electronic payment service; An information processing program characterized by causing the program to execute the above.

Images