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

Abstract

To improve the usability of services related to digital salary payments.SOLUTION: An information processing device according to the present application executes processing related to funds deposited through a virtual account that is previously associated with a service user who uses an electronic settlement service, the information processing device having an execution unit. When electronic money equivalent to an amount received by the service user through the virtual account is charged as a service user's money balance, and the amount exceeds a first upper limit set in advance by the service user as an upper limit of cumulative charge amount for a specified period, the execution unit executes processing for charging the electronic money equivalent to an amount of the received amount that does not exceed the first upper limit to an electronic wallet that stores the service user's money balance, and transferring cash equivalent to the amount of the received amount that exceeds the first upper limit to a refund bank account previously designated by the service user.SELECTED DRAWING: Figure 3

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 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 techniques leave room for improving the usability of services related to digital salary payment.

[0005] 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 can improve the usability of services related to digital payment of wages. [Means for solving the problem]

[0006] The information processing device according to the present application is an information processing device that executes processing related to funds deposited through a virtual account that is previously associated with a service user who uses an electronic payment service, and includes an execution unit. When electronic money equivalent to the amount received by the service user through the virtual account is charged to the service user's money balance, and the amount exceeds a first upper limit that is previously set by the service user as an upper limit of the cumulative charge amount for a predetermined period, the execution unit executes processing to charge electronic money equivalent to an amount of the amount received that does not exceed the first upper limit to an electronic wallet that stores the service user's money balance, and transfer cash equivalent to the amount of the amount received that exceeds the first upper limit to a refund bank account previously designated by the service user. Effect of the Invention

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

[0008] [Figure 1] FIG. 1 is a diagram for explaining an overview of information processing according to the embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of providing refund information according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of the configuration of the payment server according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of user information stored in a user information storage unit according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of balance information stored in a balance information storage unit according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of refund information stored in a refund information storage unit according to the embodiment. [Figure 7] FIG. 7 is a flowchart illustrating an example of a processing procedure of the information processing executed by the payment server according to the embodiment. [Figure 8]FIG. 8 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server and the credit card server constituting the information processing system according to the embodiment or the modification. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] 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 descriptions are omitted.

[0010] 1. Embodiment (1-1. System Configuration) Hereinafter, the information processing according to the embodiment will be specifically described. First, before describing the information processing according to the embodiment, an example of the configuration of the information processing system SYS will be described with reference to FIG.

[0011] As shown in FIG. 1, the information processing system SYS according to the embodiment includes a user terminal 10, a financial institution server 20, and a payment server 100. The user terminal 10, the financial institution server 20, and the payment server 100 are connected to a network N (see, for example, FIG. 3) by wire or wirelessly. The user terminal 10, the financial institution server 20, and the payment server 100 can communicate with other devices via the network N. The network N is, for example, a WAN (Wide Area Network) such as the Internet.

[0012] The financial institution server 20 shown in Fig. 1 is an information processing device operated and managed by a financial institution (e.g., a bank) that cooperates with a service provider that provides an electronic payment service. The financial institution server 20 may be realized by a mainframe, a workstation, or the like. Furthermore, when the financial institution server 20 is configured with a server device, it may be realized by a single server device, or may be realized by a cloud system in which multiple server devices and multiple storage devices operate in cooperation with each other. In response to a request from a service provider that provides an electronic payment service, the financial institution server 20 lends out to the service provider multiple virtual accounts linked to real accounts that the service provider holds at the financial institution.

[0013] The payment server 100 shown in Fig. 1 is an information processing device operated and managed by a business that provides an electronic payment service. For example, the electronic payment service is a service that provides a service user with a usage environment for code payment, which allows the user to instantly pay for the price of a transaction object with a money balance, which is the balance of electronic money held by the user, using predetermined code information as described below (it can also be said to be a service that provides a predetermined transaction means that controls the exchange of electronic money by code payment).

[0014] The payment server 100 may be realized by a mainframe, a workstation, etc. When the payment server 100 is configured by a server device, it may be realized by a single server device, or may be realized by a cloud system in which a plurality of server devices and a plurality of storage devices operate in cooperation with each other.

[0015] In addition, the payment server 100, in conjunction with a payment application running on the user terminal 10, executes various processes related to the electronic payment service provided, for example, through a dedicated online system. For example, the payment server 100 distributes the payment application to those who wish to use the electronic payment service, and provides the electronic payment service on the condition that a predetermined procedure in the payment application is completed. In addition, when the payment server 100 accepts a transaction request from the payment application via an interface dedicated to the payment application (for example, various operation screens displayed on the user terminal 10 by the function of the payment supplement), it executes information processing including a remittance 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 the transaction and date and time information (i.e., a timestamp) for identifying the date and time when the transaction was performed.

[0016] The payment server 100 also provides a service (hereinafter referred to as a "salary receiving service") that allows a service user (for example, service user UA) to receive at least a part of a salary in electronic money as one of the services incidental to the electronic payment service. For example, when the service user UA requests to use the salary receiving service, the payment server 100 arbitrarily selects an unused virtual account from among a plurality of virtual accounts borrowed in advance from a financial institution associated with the payment server 100, and registers a virtual account number for identifying the selected virtual account in association with identification information unique to the service user UA. The payment server 100 can use, for example, a user ID that the payment server 100 assigns to each service user when registering for use of the electronic payment service, as identification information unique to the service user (for example, service user UA) who uses the salary receiving service. The salary receiving service may be configured as a mini-app launched in a payment app equipped with various functions related to code payment, or may be configured as a unique application program prepared independently of the payment app.

[0017] The user terminal 10 shown in Fig. 1 is an information processing terminal used by a service user UA who is a user of an electronic payment service. The electronic payment service is provided by a business operator who operates and manages a 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 also displays information distributed by the payment server 100 by a web browser or an application.

[0018] In addition, the user terminal 10 is installed with an application program for a user (hereinafter, appropriately referred to as a "payment app") for using code payment (also referred to as "smartphone payment") provided to the service user UA as a cashless payment means by an electronic payment service. When the user terminal 10 receives control information for realizing a predetermined information processing through the payment app from the payment server 100, the user terminal 10 realizes the information processing 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). Note that the predetermined application itself delivered from the payment server 100 may be regarded as the control information.

[0019] Furthermore, the service user UA can use the above-mentioned salary receiving service as one of the services incidental to the electronic payment service being used. When using the salary receiving service, the service user UA can receive at least a part of the salary in electronic money through the virtual account by notifying the employer, etc., who is the payee, of the virtual account number provided by the service provider. The service user UA can receive at least a part of various funds in electronic money by notifying the payee of the virtual account number to the payee of various funds, not limited to salary.

[0020] (1-2. Payment Using User Terminal 10) Here, an example of code payment using the user terminal 10 will be described. In the following description, for example, a two-dimensional code (QR code (registered trademark)) placed in a specific store, which indicates store identification information that identifies the specific store, is used to perform a payment using the user terminal 10 by a service user UA who receives a transaction object from a specific store. 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.

[0021] For example, when a service user UA makes a payment for the purchase or use of a transaction object such as various products or services at a specific store, the service user UA launches a payment application pre-installed in the user terminal 10. Then, the service user UA photographs a two-dimensional code placed at the specific store 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 UA or a clerk at the specific store. Then, the user terminal 10 transmits transaction information including user identification information that identifies the service user UA, store identification information (or information indicated by the store identification information, i.e., information indicating the specific store (e.g., store ID)), and the payment amount to the payment server 100.

[0022] When the payment server 100 accepts the transaction information from the user terminal 10, it transfers electronic money equivalent to the payment amount from the account of the service user UA indicated by the user identification information to the account of the specified store indicated by the store identification information. At this time, the payment server 100 may transfer the electronic money to the account of the specified store after subtracting a predetermined fee to be charged to the specified store 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 UA 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 UA indicated by the user identification information, manage it as sales information of the specified store, and transfer cash equivalent to the sales to a bank account held by the specified store at a predetermined timing. In this case, the payment server 100 may notify the service user UA 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 UA.

[0023] 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 a "store terminal") installed in a specific store. Specifically, the user terminal 10 first displays code information indicating user identification information for identifying the service user UA 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 UA (e.g., user ID)), the payment amount, and information identifying the specific store to the payment server 100.

[0024] 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 UA indicated by the user identification information to the account of the specified store. 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 UA that the transaction using electronic money has been completed by outputting a screen or a specified 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 UA indicated by the user identification information, manage the electronic money as sales information of the specified store, and transfer cash equivalent to the sales amount to a bank account held by the specified store at a specified timing. In this case, the payment server 100 may notify the store clerk or the service user UA 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 UA.

[0025] 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 UA has previously charged electronic money to an account of a specific store, but may also be, for example, a payment using a credit card registered in advance by the service user UA. 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 specific store, and may also bill the operating company of the service user UA's credit card for the amount indicated by the payment amount.

[0026] 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 UA to the account of a specific store, but may also be, for example, a settlement of transferring electronic money from the account of the service user UA to the account of another user (i.e., a transfer between users). For example, the user terminal 10 used by the service user UA 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 UA, and transmits information indicating the read identification information, the remittance amount, and the user identification information that identifies the service user UA 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 UA to the account of the user of the remittance destination, and notify the user of the completion of the remittance by outputting a screen or a predetermined sound to the user terminal 10 or the terminal device used by the user of the remittance destination.

[0027] 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. As 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 UA, and transmits the input telephone number or user ID, the remittance amount, and user identification information for identifying the service user UA to the payment server 100. Then, the payment server 100 transfers electronic money in an amount indicated by the remittance amount from the account of the service user UA to the account of the user linked to the transmitted telephone number or user ID.

[0028] 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 app. In this case, the user terminal 10 accepts, from the service user UA, the designation of the user (remittance destination) registered in the payment app 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 UA.

[0029] 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 UA, 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 UA to the account of the remittance user.

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

[0031] (1-3. Information Processing According to the Embodiment) (1-3-1. Overview of information processing) Hereinafter, an overview of the information processing according to the embodiment will be described with reference to FIG. 1. FIG. 1 is a diagram showing an overview of the information processing according to the embodiment. For example, if an employer allows only one account as a payee for a salary, it is inconvenient for an employee receiving a salary to receive an amount more than the amount he or she wishes to receive (for example, the entire amount of salary) in electronic money, and this may hinder the use of the salary receiving service. In view of this situation, the following embodiment aims to improve the usability of the service user UA in the electronic payment service by leaving room for the employee receiving a salary to select the salary receiving service as a means of receiving salary.

[0032] In the following embodiment, information processing will be described for the case where the service user UA receives at least a portion of the funds deposited in the virtual account as salary in the form of electronic money, but similar information processing can be applied to the case where the funds deposited in the virtual account are funds other than salary. In the following description, the service user UA and the user terminal 10 may be regarded as the same thing. In other words, the service user UA can be read as the user terminal 10.

[0033] As a premise for the information processing shown in Fig. 1, the payment server 100 provides the service user UA with a function for setting a monthly cumulative charge upper limit when receiving at least a portion of funds deposited in a virtual account as electronic money through a payment application installed in the user terminal 10 (step S01). The monthly cumulative charge upper limit setting function is a function for setting an upper limit, in units of 1 yen, on the monthly cumulative amount of electronic money that the service user UA, who uses a salary receiving service, charges (also called "adding to balance") to his / her own user account (e.g., electronic wallet) held in the electronic payment service through the virtual account.

[0034] For example, when registering for a salary receiving service, the service user UA sets the monthly cumulative charge limit using the monthly cumulative charge limit setting function. The service user UA can also change the monthly cumulative charge limit at any time using the monthly cumulative charge limit setting function. This allows the service user UA to reflect the changed value (i.e., amount) as the monthly cumulative charge limit in the user account in real time.

[0035] In addition, when the money balance linked to the service user UA exceeds a predetermined upper limit of the balance among the deposit amount through the virtual account, the service user UA sets up a refund bank account for receiving the refund of the excess amount exceeding the upper limit of the balance. The upper limit of the balance corresponds to the balance of electronic money secured in the electronic wallet held by the service user UA. This refund bank account is also used as a refund destination when refunding the excess amount exceeding the monthly cumulative charge upper limit to the service user UA. Note that the refund destination when refunding the excess amount exceeding the monthly cumulative charge upper limit to the service user UA may be set separately from the refund bank account. In addition, the service user UA may set multiple monthly cumulative charge upper limits and set up a bank account for receiving the refund of the excess amount for each monthly cumulative charge upper limit. For example, the service user UA may set the monthly cumulative charge limit 1 to 500,000 yen and the monthly cumulative charge limit 2 to 800,000 yen, and may set the A-1 account of Bank A as the receiving account for the excess amount that exceeds the monthly cumulative charge limit 1 and is less than the monthly cumulative charge limit 2, and the B-1 account of Bank B as the receiving account for the excess amount that exceeds the monthly cumulative charge limit 2. The service user UA may also set multiple bank accounts as receiving accounts for splitting and receiving the excess amount that exceeds the monthly cumulative charge limit. For example, the service user UA may set the C-1 account of Bank C as the receiving account for the excess amount that is less than X yen, and the D-1 account of Bank D as the receiving account for the excess amount that is X yen or more. The service user UA may also set multiple bank accounts for splitting and receiving the excess amount of the balance limit, as in the case of the monthly cumulative charge limit.

[0036] The user terminal 10 transmits information on the monthly cumulative charge upper limit to the payment server 100 in accordance with an operation by the service user UA (step S02). The payment server 100 registers the information on the monthly cumulative charge upper limit in association with the user account of the service user UA.

[0037] When financial institution server 20 detects a deposit to a virtual account from a financial institution that is the transfer source (step S11), it notifies settlement server 100 that a deposit has been made to the virtual account. For example, financial institution server 20 uses an API (Application Programming Interface) provided by the service provider to access an intermediate wallet managed by settlement server 100 and registers information on the virtual account number to which the deposit has been made and the amount of the deposit, thereby notifying that a deposit has been made to the virtual account. Note that financial institution server 20 may notify the deposit to the virtual account on a transaction basis (transaction unit) for the deposit to the virtual account.

[0038] When the payment server 100 receives a notification from the financial institution server 20 that a deposit has been made to the virtual account (step S12), it refers to the money balance linked to the service user UA corresponding to the virtual account, and determines whether the reflected balance after reflecting the amount deposited through the virtual account exceeds a pre-defined balance upper limit (step S13).

[0039] If the reflected balance after reflecting the deposit amount through the virtual account exceeds the upper balance limit, the payment server 100 calculates and determines the excess amount exceeding the upper balance limit from the difference between the upper balance limit and the reflected balance (step S14-1). The payment server 100 also calculates the amount of the deposit that does not exceed the excess amount as the amount received by the service user UA, and passes it to subsequent processing (step S14-2). If the reflected balance after reflecting the deposit amount through the virtual account is equal to or less than the upper balance limit, the payment server 100 treats the deposit amount through the virtual account as the amount received by the service user UA.

[0040] The payment server 100 determines whether the monthly cumulative charge amount of the service user UA exceeds the monthly cumulative charge upper limit set in advance by the service user UA as the upper limit of the monthly cumulative charge amount by charging the electronic money equivalent to the amount received by the service user UA through the virtual account to the service user UA's money balance (step S15).

[0041] When the monthly cumulative charge amount of the service user UA exceeds the monthly cumulative charge upper limit, the payment server 100 calculates and confirms the excess amount of the received amount that exceeds the monthly cumulative charge upper limit (step S16-1). The payment server 100 also calculates the electronic money equivalent to the amount received by the service user UA that does not exceed the monthly cumulative charge upper limit as the charge allowable amount that can be charged to the money balance of the service user UA. The payment server 100 then charges the electronic money equivalent to the calculated charge allowable amount to the electronic wallet that stores the money balance of the service user UA. The payment server 100 updates and manages the monthly cumulative charge amount based on the charge allowable amount charged to the electronic wallet of the service user UA. The payment server 100 also resets the monthly cumulative charge amount to "0" yen at the beginning of each month. This allows the service user UA to repeatedly receive at least a portion of the funds received through the virtual account over the course of a month as electronic money, up to an amount not exceeding the monthly cumulative charge limit set by the service user UA, and use this to pay for the item of a transaction through code payment using a payment app.

[0042] In addition, the payment server 100 calculates the amount to be refunded by adding up the amount deposited through the virtual account that exceeds the balance upper limit and the amount received by the service user UA that exceeds the monthly cumulative charge upper limit (step S17).

[0043] The payment server 100 also refunds the calculated refund amount to the service user UA by executing a bank transfer process to automatically transfer the amount to a refund bank account linked to the service user UA as the transfer destination (step S18). The payment server 100 may also execute the bank transfer process so that the service user UA can know whether the refund is for the amount in excess of the balance upper limit or the amount in excess of the monthly cumulative charge upper limit. In this way, the payment server 100 refunds the sum of the amount in excess of the balance upper limit and the amount in excess of the monthly cumulative charge upper limit to the bank account in the service user's name designated by the service user through automatic transfer to the service user UA, so that the service user UA can receive the refund through the bank account designated by the service user.

[0044] In addition, in the above-mentioned information processing, the payment server 100 may perform a determination on the above-mentioned balance upper limit after performing a determination on the above-mentioned monthly cumulative charge upper limit for deposits to the virtual account. For example, the payment server 100 assumes that a new deposit of 400,000 yen has been made to the virtual account associated with the service user UA in a state in which the monthly cumulative charge upper limit is 500,000 yen, the balance upper limit is 1 million yen, the money balance is 900,000 yen, and the monthly cumulative charge amount is 300,000 yen. In this case, the payment server 100 first performs a determination based on the monthly cumulative charge upper limit, and charges 200,000 yen, which does not exceed the monthly cumulative charge upper limit of 500,000 yen, of the deposit amount of 400,000 yen, to the money balance of the electronic wallet of the service user UA. Next, the payment server 100 performs a determination based on the balance upper limit, and of the money balance, 100,000 yen that exceeds the balance upper limit is subject to refund. In other words, the payment server 100 charges 100,000 yen as the money balance of the service user UA.

[0045] As described above, according to the information processing of the embodiment, when the amount of electronic money equivalent to the amount received by the service user UA through the virtual account is charged to the money balance of the service user UA, and the amount exceeds the monthly cumulative charge upper limit set by the service user as the upper limit of the cumulative charge amount in a month, the payment server 100 charges the electronic money equivalent to the amount of the amount received that does not exceed the monthly cumulative charge upper limit to the electronic wallet that stores the money balance of the service user UA corresponding to the virtual account. Therefore, even if an amount (for example, the entire salary) that is more than the amount that the service user UA wishes to receive in electronic money is deposited in the virtual account corresponding to the service user UA, the payment server 100 can charge the money balance to the extent not exceeding the monthly cumulative charge upper limit, and can refund the amount exceeding the monthly cumulative charge upper limit to a refund bank account designated by the service user UA. As a result, even if the employer allows only one account to which salary can be paid, the payment server 100 can eliminate a situation in which convenience is lost when the service user UA, who is the employee receiving the salary, selects the salary receipt service as a means of receiving salary, thereby improving the usability of electronic payment services.

[0046] (1-3-2. Example of refund information) Hereinafter, an example of providing refund information according to the embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of providing refund information according to the embodiment.

[0047] As shown in FIG. 2, the user terminal 10 transmits a request for obtaining refund information to be displayed on the screen of the payment application to the payment server 100 in accordance with an operation of the payment application by the service user UA (step S21).

[0048] When the payment server 100 receives the request to acquire the refund information from the user terminal 10, the payment server 100 acquires the refund information associated with the service user UA, and responds with the acquired refund information to the user terminal 10 (step S22).

[0049] For example, the payment server 100 can provide the service user UA with refund information indicating the details of the remittance, which distinguishes between the refund amount transferred to the refund bank account as the amount exceeding the monthly cumulative charge upper limit and the refund amount transferred to the refund bank account as the amount exceeding the balance upper limit, by transmitting the information to the user terminal 10. FIG. 2 shows an example in which the payment server 100 provides refund information including the items "refund date and time", "deposit amount", and "refund amount", and the "refund amount" item is further divided into the items "excess of balance upper limit" and "monthly cumulative charge upper limit". This allows the service user UA to easily grasp the details of the refund.

[0050] The payment server 100 may also provide, as the refund information, the monthly cumulative charge amount at the time of the refund, i.e., information on the cumulative amount of electronic money charged to the electronic wallet of the service user UA in the target month. The payment server 100 may also notify the user terminal 10 of the service user UA, for example, through a payment application, at the timing of performing a bank transfer process to the refund bank account of the service user UA, regardless of a request from the service user UA. At this time, the payment server 100 may provide not only the refund information but also information indicating the amount of electronic money charged to the electronic wallet of the service user UA. At this time, the payment server 100 may provide information indicating whether the electronic money charged to the electronic wallet corresponds to electronic money corresponding to a salary or electronic money corresponding to something other than a salary. When providing the refund information, the payment server 100 may also provide proposal information proposing a change to the monthly cumulative charge upper limit. The payment server 100 may include, as conditions for proposing a change to the monthly cumulative charge upper limit, for example, when the money balance of the electronic wallet of the service user UA is equal to or less than the average balance of the service user UA for a predetermined period, when the money balance in the electronic wallet corresponding to the salary is equal to or less than a predetermined amount, when there are more deposits than withdrawals based on the deposit and withdrawal history of electronic money (for example, salary and / or non-salary) for the target month, and when the number of times that normal electronic money is charged without going through a virtual account in the current month is greater than a predetermined number. In addition, the payment server 100 may propose a change to the monthly cumulative charge upper limit of the current month to the service user UA if the day on which the monthly cumulative charge amount exceeded the monthly cumulative charge upper limit is the beginning of the month (for example, within the first week), and may propose a change to the monthly cumulative charge upper limit of the next month if it is after a predetermined date. In addition, the payment server 100 may propose a change to the monthly cumulative charge upper limit when it is estimated that charging will occur more than a predetermined number of times in the current month based on the charge history of past salary. In addition, the payment server 100 may propose the use of a linked financial service together with the proposal to change the monthly cumulative charge upper limit.For example, when proposing the purchase of securities as a financial service, the settlement server 100 may exemplify products such as securities that can be purchased for the excess amount of the monthly cumulative charge upper limit, such as proposing securities that can be purchased for 300,000 yen when the excess amount of the monthly cumulative charge upper limit is 300,000 yen. Also, when an excess amount that exceeds the balance upper limit occurs, even if the settlement server 100 proposes and changes the monthly cumulative charge upper limit (for example, increasing the upper limit), there is a high possibility that the amount will exceed the balance upper limit and a refund will be made, so even if the above-described conditions for proposing a change to the monthly cumulative charge upper limit are met, the settlement server 100 may control not to implement a proposal to change the monthly cumulative charge upper limit for the current month.

[0051] 2. Configuration of payment server 100 Hereinafter, an example of a functional configuration of the payment server 100 according to the embodiment will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of a configuration of the payment server 100 according to the embodiment. As shown in Fig. 3, the payment server 100 has a communication unit 110, a storage unit 120, and a control unit 130.

[0052] (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 other devices such as the user terminal 10 and the financial institution server 200.

[0053] (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. 3, the storage unit 120 has a user information storage unit 121, a balance information storage unit 122, and a refund information storage unit 123.

[0054] (Regarding the user information storage unit 121) The user information storage unit 121 stores user information related to a service user who is a user of an electronic payment service (for example, the service user UA shown in FIG. 1). FIG. 4 is a diagram showing an example of user information stored in the user information storage unit 121 according to the embodiment.

[0055] 4, the user information stored in the user information storage unit 121 has multiple items such as a "user ID", a "personal information", a "wallet ID", a "virtual account number", a "deposit history", a "monthly cumulative charge limit", and a "refund bank account information". These items in the user information are associated with each other.

[0056] The "user ID" field stores a user ID, which is unique identification information assigned to each service user to uniquely identify the service user who is a user of the electronic payment service.

[0057] The "Personal Information" field stores personal information that the service user registered when registering to use the electronic payment service. The personal information may include information on demographic attributes such as name, age, and address, as well as information on psychographic attributes such as interests and preferences.

[0058] The "wallet ID" field stores a wallet ID, which is unique identification information given to each electronic wallet to uniquely identify the electronic wallet associated with each service user in the electronic payment service. The electronic wallet stores the money balance, which is the balance of electronic money associated with the service user.

[0059] The "virtual account number" field stores information indicating a virtual account number unique to a virtual account assigned to a service user who uses the "salary receipt service."

[0060] The "Deposit History" field stores information indicating the deposit history of the service user. The deposit history may include information such as the deposit date, the deposit source, and the deposit amount.

[0061] The "monthly cumulative charge limit" item stores information indicating the upper limit of the monthly cumulative amount that a service user who uses the salary receiving service can charge to his / her own user account (e.g., electronic wallet) held in the electronic payment service via a virtual account. Note that, as shown in Figure 4, there is no need to be any particular limit when storing the upper limit of the monthly cumulative amount, and the upper limit of the cumulative charge amount for any period can be set.

[0062] The "Refund Bank Account Information" item stores account information on a refund bank account for accepting refunds of the amount exceeding the balance upper limit when the service user's money balance exceeds a predefined balance upper limit. The account information may include information such as the bank name, branch name, account name, and account number. The refund bank account is also used as a refund destination when refunding the amount exceeding the monthly cumulative charge upper limit to the service user UA.

[0063] In addition, the refund destination when refunding the excess amount exceeding the monthly cumulative charge limit to the service user UA may be set separately from the refund bank account. In addition, the service user UA may set multiple monthly cumulative charge limits and set a bank account to receive the refund of the excess amount for each monthly cumulative charge limit. For example, the service user UA may set the monthly cumulative charge limit 1: 500,000 yen and the monthly cumulative charge limit 2: 800,000 yen, and set the A-1 account of Bank A as the receiving account for the excess amount exceeding the monthly cumulative charge limit 1, and the B-1 account of Bank B as the receiving account for the excess amount exceeding the monthly cumulative charge limit 2. In addition, the service user UA may set multiple refund destinations to receive the excess amount exceeding the monthly cumulative charge limit in installments. For example, the service user UA may set the C1 account of Bank C as the receiving account for the excess amount less than X yen, and the D-1 account of Bank D as the receiving account for the excess amount equal to or greater than X yen. As in the case of the monthly cumulative charge upper limit, the service user UA may set up multiple bank accounts to receive any excess amount over the balance upper limit in installments.

[0064] (Regarding the balance information storage unit 122) The balance information storage unit 122 stores balance information indicating a money balance held by a service user (for example, the service user UA shown in FIG. 1, etc.). FIG. 5 is a diagram showing an example of balance information stored in the balance information storage unit 122 according to the embodiment.

[0065] 5, the balance information stored in the balance information storage unit 122 has multiple items such as a "wallet ID" item and a "money balance" item. These items in the balance information are associated with each other.

[0066] The "wallet ID" field stores a wallet ID, which is unique identification information given to each electronic wallet to uniquely identify the electronic wallet associated with each service user in the electronic payment service. For example, the wallet ID links the user information stored in the user information storage unit 121 with the balance information stored in the balance information storage unit 122.

[0067] The "money balance" field stores information indicating the money balance, which is the balance of electronic money held by the user as payment resources for code payments provided by the electronic payment service. The money balance may be managed separately into a money balance based on funds deposited into the virtual account as salary and a money balance based on funds deposited into the virtual account as funds other than salary.

[0068] (Regarding the refund information storage unit 123) The refund information storage unit 123 stores refund information regarding refunds to be made based on a predetermined standard out of funds (for example, an amount electronically transferred by an employer or the like in the name of salary) deposited through a virtual account for the purpose of charging (also referred to as "balance addition") the money balance in the electronic wallet. For example, the refund information storage unit 123 stores refund information indicating details of remittances that distinguish between a refund amount transferred to a refund bank account as an amount exceeding the monthly cumulative charge upper limit and a refund amount transferred to a refund bank account as an amount exceeding the balance upper limit. FIG. 6 is a diagram showing an example of refund information stored in the refund information storage unit 123 according to an embodiment.

[0069] As shown in Fig. 6, the refund information stored in the refund information storage unit 123 includes multiple items such as a "user ID", a "refund date and time", a "deposit amount", and a "refund amount". The "refund amount" item is further divided into an "excess balance upper limit" item and a "monthly cumulative charge upper limit". These items in the refund information are mutually associated.

[0070] The "user ID" field stores a user ID, which is unique identification information assigned to each service user to uniquely identify the service user who is a user of the electronic payment service. For example, the "user ID" field may store the same information as the user ID included in the user information stored in the user information storage unit 121.

[0071] The "Refund Date and Time" field stores information indicating the date and time when the refund was made to the service user. The "Deposit Amount" field stores information indicating the deposit amount of funds deposited through the virtual account associated with the target service user.

[0072] The "excess balance limit" item in the "refund amount" item stores information indicating the amount of the deposit amount through the virtual account that exceeds the upper limit of the balance that is predefined as the limit that can be held as a money balance. For example, the upper limit of the balance is defined for the purpose of complying with the retention regulations that are required by law for money transfer businesses.

[0073] The "Monthly cumulative charge limit" item in the "Refund amount" item stores information indicating the amount of the service user's receipt deposited through a virtual account that exceeds the monthly cumulative limit that the service user may charge to his or her own user account (e.g., electronic wallet) held in the electronic payment service.

[0074] The payment server 100 manages the refund information stored in the refund information storage unit 123 by dividing it into the items "excess balance upper limit" and "monthly cumulative charge upper limit," thereby enabling the service user to be notified of the details of the refund.

[0075] The refund information storage unit 123 may store information on the monthly cumulative charge amount at the time of refund, that is, the cumulative amount of electronic money charged to the electronic wallet of the service user UA during the target month.

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

[0077] As shown in Fig. 3, the control unit 130 has a detection unit 131 and an execution unit 132, and these units realize or execute the functions and actions of information processing described below. Note that the control unit 130 may have new functional units different from the units shown in Fig. 3 in response to the extension of various processes executed by the payment server 100.

[0078] (Regarding the detection unit 131) The detection unit 131 detects a deposit through a virtual account for each service user. For example, the detection unit 131 may detect the deposit by checking whether a new record (e.g., information on a virtual account number and a deposit amount) has been registered in an intermediate wallet, which is an electronic wallet for processing purposes for detecting a deposit through a virtual account. Furthermore, when the detection unit 131 detects a deposit through a virtual account, it passes information on the detected deposit (e.g., the virtual account number and the deposit amount, etc.) to the execution unit 132.

[0079] (Regarding the execution unit 132) When the electronic money equivalent to the amount received by the service user (for example, service user UA shown in FIG. 1) through the virtual account is charged to the service user's money balance, and the amount exceeds a monthly cumulative charge upper limit (an example of a "first upper limit") previously set by the service user as the upper limit of the cumulative charge amount for a predetermined period, the execution unit 132 executes a process of charging the electronic money equivalent to an amount of the amount received that does not exceed the monthly cumulative charge upper limit to an electronic wallet that stores the service user's money balance, and transferring the cash equivalent to the amount of the amount received that exceeds the monthly cumulative charge upper limit to a refund bank account previously designated by the service user. The execution unit 132 can execute the above-mentioned process based on information regarding the deposit obtained from the detection unit 131.

[0080] The execution unit 132 also calculates the amount to be received as the amount of the reflected balance after reflecting the deposit amount deposited through the virtual account does not exceed a predetermined balance upper limit (an example of a "second upper limit"), calculates the amount to be refunded by adding up the amount of the deposit that exceeds the balance upper limit and the amount of the receipt that exceeds the monthly cumulative charge upper limit, and transfers cash equivalent to the calculated amount to be refunded to the refund bank account. The execution unit 132 can execute the above-mentioned processing based on information regarding the deposit obtained from the detection unit 131.

[0081] In addition, the execution unit 132 provides the service user with refund information that separately describes the amount of the refund transferred to the refund bank account as the amount exceeding the monthly cumulative charge upper limit, and the amount of the refund transferred to the refund bank account as the amount exceeding the balance upper limit. The execution unit 132 can execute the above-mentioned processing based on the information regarding the deposit obtained from the detection unit 131.

[0082] The execution unit 132 may also provide, as the refund information, the monthly cumulative charge amount at the time of refund, i.e., information on the cumulative amount of electronic money charged to the electronic wallet of the service user (for example, the service user UA shown in FIG. 1) in the target month. The execution unit 132 may also notify the user terminal 10 of the service user UA, for example, through a payment application, at the timing of performing a bank transfer process to the refund bank account of the service user UA, regardless of a request from the service user. The execution unit 132 may also provide, in addition to the refund information, information indicating the amount of electronic money charged to the electronic wallet of the service user UA. At this time, the payment server 100 may provide information indicating whether the electronic money charged to the electronic wallet corresponds to electronic money corresponding to a salary or electronic money corresponding to something other than a salary.

[0083] Furthermore, when providing the refund information, the execution unit 132 may propose a change to the monthly cumulative charge upper limit. The execution unit 132 may include, as conditions for proposing a change to the monthly cumulative charge upper limit, for example, when the money balance of the service user's electronic wallet is equal to or less than the average balance of the service user for a predetermined period, when the money balance in the electronic wallet corresponding to the salary is equal to or less than a predetermined amount, when there are more deposits than withdrawals based on the deposit and withdrawal history of electronic money (for example, salary and at least one other than salary) for the target month, and when the number of times that normal electronic money is charged without using a virtual account for the month is greater than a predetermined number. Furthermore, the execution unit 132 may propose a change to the monthly cumulative charge upper limit for the month to the service user UA if the day on which the monthly cumulative charge amount exceeded the monthly cumulative charge upper limit is the beginning of the month (for example, within the first week), and may propose a change to the monthly cumulative charge upper limit for the next month if it is after a predetermined date. In addition, the execution unit 132 may propose a change to the monthly cumulative charge upper limit when it is estimated that a charge will occur a predetermined number of times or more in the current month based on the charge history of past salary. In addition, the execution unit 132 may propose the use of a linked financial service in addition to the proposal to change the monthly cumulative charge upper limit. For example, when proposing the purchase of securities as a financial service, the execution unit 132 may exemplify products such as securities that can be purchased for the excess amount of the monthly cumulative charge upper limit, such as proposing securities that can be purchased for 300,000 yen when the excess amount of the monthly cumulative charge upper limit is 300,000 yen. In addition, the settlement server 100 may control not to execute the proposal to change the monthly cumulative charge upper limit for the current month even if the above-described conditions for proposing a change to the monthly cumulative charge upper limit are met, since there is a high possibility that the amount will exceed the balance upper limit and be refunded even if the proposal to change the monthly cumulative charge upper limit for the current month is made (for example, by increasing the upper limit).

[0084] Furthermore, when multiple monthly cumulative charge upper limits are set as the monthly cumulative charge upper limit corresponding to the service user to be processed and a bank account is set for receiving a refund of the excess amount for each monthly cumulative charge upper limit, the execution unit 132 judges the excess amount for each monthly cumulative charge upper limit and executes a bank transfer process to transfer the excess amount to the corresponding bank account according to the judgment result. Furthermore, when multiple bank accounts are set for the service user to be processed as receiving accounts for receiving the excess amount exceeding the monthly cumulative charge upper limit in installments, the execution unit 132 executes a bank transfer process to divide the excess amount and transfer the excess amount to the corresponding bank account.

[0085] The control unit 130 may further include a change receiving unit that receives a change to the refund bank account or a change to the monthly cumulative charge upper limit from the service user (for example, the service user UA shown in FIG. 1).

[0086] [3. Example of processing procedure] Hereinafter, a flow of information processing executed by the payment server 100 according to the embodiment will be described with reference to Fig. 7. Fig. 7 is a flowchart showing an example of a processing procedure of information processing executed by the payment server 100 according to the embodiment. The processing procedure shown in Fig. 7 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. 7 while the payment server 100 is operating.

[0087] 7, the execution unit 132 identifies a service user who has received a deposit through a virtual account based on the virtual account number acquired from the detection unit 131 (step S101). For example, the execution unit 132 refers to the user information stored in the user information storage unit 121 and identifies the user ID associated with the virtual account number.

[0088] The execution unit 132 also acquires the money balance of the target user, who is a service user to whom a deposit has been made through the virtual account (step S102). For example, the execution unit 132 identifies a wallet ID linked to a user ID in the user information, and acquires information on the money balance of the target user from the balance information stored in the balance information storage unit 122 using the identified wallet ID as a key.

[0089] Furthermore, the execution unit 132 determines whether or not the money balance after the deposit amount deposited through the virtual account is reflected exceeds a predetermined upper balance limit (step S103).

[0090] When the execution unit 132 determines that the money balance after reflecting the deposit amount deposited through the virtual account exceeds the balance upper limit (step S103; Yes), it calculates the excess amount of the deposit amount that exceeds the balance upper limit (step S104).On the other hand, when the execution unit 132 determines that the money balance after reflecting the deposit amount deposited through the virtual account does not exceed the balance upper limit (step S103; No), it proceeds directly to the processing procedure of step S105 described later.

[0091] In addition, the execution unit 132 determines whether the monthly cumulative charge amount of the target user exceeds a monthly cumulative charge upper limit set in advance by the target user by charging electronic money equivalent to the amount received by the target user through the virtual account to the money balance of the service user UA (step S105).

[0092] If the execution unit 132 determines that the monthly cumulative charge amount exceeds the monthly cumulative charge upper limit set in advance by the target user (step S105; Yes), it calculates the excess amount of the received amount that exceeds the monthly cumulative charge upper limit (step S106).

[0093] In addition, the execution unit 132 calculates the refund amount for the target user and transfers cash equivalent to the calculated refund amount to the refund bank account of the target user (step S107). For example, the execution unit 132 calculates the refund amount by adding up the excess amount of the deposit amount through the virtual account that exceeds the balance upper limit and the excess amount of the receipt amount of the service user UA that exceeds the monthly cumulative charge upper limit.

[0094] The execution unit 132 also calculates the chargeable amount of the target user, adds it to the electronic wallet of the target user (step S108), and ends the processing procedure shown in Fig. 7. For example, the execution unit 132 calculates electronic money equivalent to an amount not exceeding the monthly cumulative charge upper limit out of the amount received by the service user UA as the chargeable amount that can be charged to the money balance of the service user UA.

[0095] In the above-mentioned step S105, if the execution unit 132 determines that the money balance after reflecting the amount received through the virtual account does not exceed the monthly cumulative charge upper limit preset by the target user (step S105; No), the processing proceeds to the above-mentioned step S108.

[0096] The process procedure shown in Fig. 7 is an example of a process procedure executed by the payment server 100 according to the embodiment, and does not need to be particularly limited to the example shown in Fig. 7. For example, either the process procedure of step S107 or the process procedure of step S108 may be executed first.

[0097] 4. Modifications In the above embodiment, an example has been described in which the information processing system SYS according to the embodiment is configured to include the payment server 100, but the information processing system SYS does not need to be particularly limited to such an example. For example, the information processing system SYS may be configured to include multiple servers in which the processing function related to code payment possessed by the payment server 100 and the processing function of the information processing according to the embodiment are functionally or physically distributed.

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

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

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

[0101] 5. Effects As described above, the payment server 100 according to the embodiment is an information processing device that executes processing related to funds deposited through a virtual account that is previously associated with a service user who uses an electronic payment service, and includes an execution unit 132. When the electronic money equivalent to the amount of receipt received by the service user through the virtual account is charged to the money balance of the service user, and the amount of the amount of receipt exceeds a first upper limit that is previously set by the service user as the upper limit of the cumulative charge amount in a predetermined period, the execution unit 132 executes processing to charge the electronic money equivalent to an amount of the amount of receipt that does not exceed the first upper limit to an electronic wallet that stores the money balance of the service user, and transfer cash equivalent to an amount of the amount of receipt that exceeds the first upper limit to a refund bank account previously designated by the service user.

[0102] In this way, the payment server 100 according to the embodiment charges the electronic money equivalent to the amount received by the service user UA through the virtual account as the money balance of the service user UA, and when the amount exceeds the monthly cumulative charge amount preset by the service user as the upper limit of the monthly cumulative charge amount, charges the electronic money equivalent to the amount received that does not exceed the monthly cumulative charge upper limit to the electronic wallet that stores the money balance of the service user UA corresponding to the virtual account. Therefore, even if an amount (for example, the entire salary) greater than the amount the service user UA wishes to receive in electronic money is deposited in the virtual account corresponding to the service user UA, the payment server 100 can charge the money balance within the range not exceeding the monthly cumulative charge upper limit, and can refund the amount exceeding the monthly cumulative charge upper limit to a refund bank account designated by the service user UA. As a result, even if the employer allows only one account to which salary can be paid, the payment server 100 can eliminate a situation in which convenience is lost when the service user UA, who is the employee receiving the salary, selects the salary receipt service as a means of receiving salary, thereby improving the usability of electronic payment services.

[0103] The execution unit 132 may also calculate the amount to be received as the amount of the reflected balance after reflecting the deposit amount deposited through the virtual account does not exceed a predetermined balance upper limit (an example of a "second upper limit"), calculate the amount to be refunded by adding up the amount of the deposit amount that exceeds the balance upper limit and the amount of the receipt amount that exceeds the monthly cumulative charge upper limit, and transfer cash equivalent to the calculated amount to be refunded to the refund bank account. In this way, the payment server 100 according to the embodiment can improve the usability of the electronic payment service while complying with the retention regulations required by law for money transfer businesses.

[0104] In addition, the execution unit 132 may provide the service user with refund information that describes the refund amount transferred to the refund bank account as the amount exceeding the monthly cumulative charge upper limit, and the refund amount transferred to the refund bank account as the amount exceeding the balance upper limit separately. This allows the settlement server 100 according to the embodiment to notify each service user of the details of the refund, thereby improving usability.

[0105] In addition, when executing a bank transfer process to transfer cash equivalent to the refund amount to a refund bank account, the execution unit 132 may provide money balance information indicating the balance of electronic money charged to the service user's electronic wallet together with the refund information.

[0106] Furthermore, when providing the refund information, the execution unit 132 may provide the service user with proposal information that proposes changing the monthly cumulative charge upper limit (an example of the "first upper limit").

[0107] Furthermore, the execution unit 132 may provide the service user with suggested information if the service user's money balance is equal to or less than the average balance for a predetermined period.

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

[0109] The computer 1000 is connected to an output device 1010 and an input device 1020, and has a configuration in which an arithmetic unit 1030, a primary storage device 1040, a secondary storage device 1050, an output IF (Interface) 1060, an input IF 1070, and a network IF 1080 are connected via a bus 1090.

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

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

[0112] The input device 1020 may be a device that reads information from an optical recording medium such as a CD (Compact Disc), a DVD (Digital Versatile Disc), or a PD (Phase change rewritable Disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. The input device 1020 may also be an external storage medium such as a USB memory.

[0113] The network IF 1080 receives data from other devices via the network N and sends it to the arithmetic device 1030, and also transmits data generated by the arithmetic device 1030 to other devices via the network N.

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

[0115] For example, when the computer 1000 functions as the information processing device 100 according to the embodiment or the modification, the arithmetic device 1030 of the computer 1000 executes a program (e.g., an information processing program) loaded onto the primary storage device 1040, thereby realizing a function similar to that of the control unit 130. That is, the arithmetic device 1030 cooperates with the program (e.g., an information processing program) loaded onto the primary storage device 1040 to realize the processing by the information processing device 100 according to the embodiment or the modification.

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

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

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

[0119] SYS Information Processing System 10 User terminal 100 Payment Server 110 Communications Department 120 Storage section 121 User information storage unit 122 Balance information storage unit 123 Refund information storage unit 130 Control section 131 Detection unit 132 Executive Department

Claims

1. An information processing device that executes a process related to funds deposited through a virtual account that is associated in advance with a service user who uses an electronic payment service, an execution unit that executes a process of charging electronic money equivalent to the amount of receipt received by the service user through the virtual account to the money balance of the service user, when the amount of receipt exceeds a first upper limit set by the service user as an upper limit of the cumulative charge amount for a predetermined period, charging electronic money equivalent to an amount of the amount of receipt not exceeding the first upper limit to an electronic wallet that stores the money balance of the service user, and transferring cash equivalent to an amount of the amount of receipt that exceeds the first upper limit to a refund bank account previously designated by the service user.

13. An information processing device comprising:

2. The execution unit is The amount of the receipt is calculated as the amount of the reflected balance after reflecting the deposit amount deposited through the virtual account, which does not exceed a second upper limit amount that is predefined, and a refundable amount is calculated by adding up the amount of the deposit amount that exceeds the second upper limit amount and the amount of the receipt amount that exceeds the first upper limit amount, and cash equivalent to the calculated refundable amount is transferred to the refund bank account.

2. The information processing apparatus according to claim 1,

3. The execution unit is Provide the service user with refund information that separately describes the refund amount transferred to the refund bank account as the amount in excess of the first upper limit amount and the refund amount transferred to the refund bank account as the amount in excess of the second upper limit amount. The information processing device according to claim 2 .

4. The execution unit is When executing a bank transfer process to transfer cash equivalent to the refund amount to the refund bank account, provide money balance information indicating the balance of electronic money charged to the electronic wallet of the service user together with the refund information.

4. The information processing apparatus according to claim 3.

5. The execution unit is When providing the refund information, suggestion information for suggesting a change to the first upper limit is provided to the service user.

4. The information processing apparatus according to claim 3.

6. The execution unit is If the money balance of the service user is equal to or less than the average balance for a predetermined period, the suggestion information is provided to the service user.

6. The information processing apparatus according to claim 5,

7. An information processing method executed by a computer that executes a process related to funds deposited through a virtual account that is associated in advance with a service user who uses an electronic payment service, comprising: an execution step of executing a process in which, when charging electronic money equivalent to the amount received by the service user through the virtual account to the money balance of the service user, the amount of the amount received that does not exceed the first upper limit set by the service user as the upper limit of the cumulative charge amount for a predetermined period of time, electronic money equivalent to the amount of the amount received that does not exceed the first upper limit is charged to an electronic wallet that stores the money balance of the service user, and cash equivalent to the amount of the amount received that exceeds the first upper limit is transferred to a refund bank account previously designated by the service user; 13. An information processing method comprising:

8. A computer that executes a process related to funds deposited through a virtual account that is associated in advance with a service user who uses an electronic payment service, an execution procedure for executing a process in which, when charging electronic money equivalent to the amount received by the service user through the virtual account to the money balance of the service user, exceeds a first upper limit amount previously set by the service user as an upper limit of the cumulative charge amount for a predetermined period, electronic money equivalent to an amount of the amount received that does not exceed the first upper limit amount is charged to an electronic wallet that stores the money balance of the service user, and cash equivalent to an amount of the amount received that exceeds the first upper limit amount is transferred to a refund bank account previously designated by the service user; An information processing program characterized by causing the program to execute the above steps.

Images