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

Abstract

To expand the use of electronic payment services. [Solution] The information processing device according to the present invention has a management unit and a name change unit. The management unit manages the account number assigned to the service user from among the account numbers used to identify multiple virtual accounts borrowed from partner financial institutions, the user identification information that identifies the service user, and the service user's personal verification information in association with each other. When the name update unit receives a change in personal verification information from the service user, it updates the name information corresponding to the virtual account identified by the account number based on the changed personal verification information.

Description

Technical Field

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

Background Art

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

[0003] Further, as one of the above-mentioned electronic payment services, there exists a service that adopts a scheme that enables electronic payment by charging and using electronic money in association with a pre-issued user account. In relation to such services, a technology is disclosed that holds correspondence information in which virtual account numbers are associated with electronic money terminal IDs, acquires the electronic money terminal ID corresponding to the virtual account number to which a transfer was made, and transmits the acquired electronic money terminal ID and transfer amount information to an electronic money server.

[0004] Further, in recent years, the government has begun to consider the introduction of so-called "digital salary payment", which allows salary payments using digital money such as the aforementioned electronic money and virtual currency for fund transfer operators engaged in the fund transfer business. If the introduction of "digital salary payment" is initiated, the expanded use of services using digital money is expected.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, the conventional technologies described above still have challenges in expanding the use of electronic payment services.

[0007] For example, if "digital salary payments" are introduced, it is conceivable that some users of electronic payment services may wish to receive their salaries in digital money. However, depending on the policies and schemes of the companies where these service users work, unforeseen circumstances may arise where "digital salary payments" using electronic payment services are not permitted.

[0008] To give a concrete example, suppose a company J, which operates an electronic payment service, borrows a virtual account ACC from a bank and assigns it to a user U, who is a service user. When a deposit is confirmed into the virtual account ACC, the balance of the electronic money account corresponding to user U is increased according to the amount deposited. In this case, user U would designate the virtual account ACC as the account to which their salary is deposited to their employer K, but the recipient's name (user U) and the account holder's name (company J) are different. Therefore, if a company has a policy or scheme that allows salary transfers to an account designated by the employee when the recipient's name and the account holder's name match, there is a possibility that the salary will not be transferred. Thus, even if "digital salary payments" are introduced, the smooth operation of the electronic payment service scheme implemented by company J cannot be expected, and the use of electronic payment services will not be promoted.

[0009] This application was made in view of the above, and aims to provide an information processing device, an information processing method, and an information processing program that can expand the use of electronic payment services. [Means for solving the problem]

[0010] The information processing device according to this application comprises a management unit and a name change unit. The management unit manages the account number assigned to the service user from among multiple account numbers used to identify virtual accounts borrowed from partner financial institutions, user identification information that identifies the service user, and the service user's personal verification information in association with each other. When the name update unit receives a change in the personal verification information from the service user, it updates the name information corresponding to the virtual account identified by the account number based on the changed personal verification information. [Effects of the Invention]

[0011] According to one embodiment of this system, the effect is to expand the use of electronic payment services. [Brief explanation of the drawing]

[0012] [Figure 1] Figure 1 shows an example of an overview of the information processing according to the embodiment (Part 1). [Figure 2] Figure 2 shows an example of an overview of the information processing according to the embodiment (part 2). [Figure 3] Figure 3 shows an example of the overview of information processing according to the embodiment (part 3). [Figure 4] Figure 4 shows an example of a notification of a bank transfer deposit using the bank transfer deposit service according to the embodiment. [Figure 5] Figure 5 shows an overview of the name change process according to the embodiment. [Figure 6] Figure 6 is a diagram illustrating the overview of the transfer amount adjustment process according to the embodiment. [Figure 7] Figure 7 shows an example of the configuration of a payment server according to this embodiment. [Figure 8] Figure 8 shows an example of information stored in the virtual account information storage unit according to the embodiment. [Figure 9] Figure 9 shows an example of information stored in the user information storage unit according to this embodiment. [Figure 10]Figure 10 is a diagram illustrating an example of information stored in an account information storage unit according to an embodiment. [Figure 11] Figure 11 is a flowchart illustrating an example of a processing procedure of account assignment processing executed by a payment server according to an embodiment. [Figure 12] Figure 12 is a flowchart illustrating an example of a processing procedure of transfer deposit reflection processing executed by the payment server according to the embodiment. [Figure 13] Figure 13 is a flowchart illustrating an example of a processing procedure of transfer amount adjustment processing executed by the payment server according to the embodiment. [Figure 14] Figure 14 is a hardware configuration diagram illustrating an example of a computer that implements the functions of the payment server according to the embodiment. [Mode for Carrying Out the Invention]

[0013] Hereinafter, modes for carrying out the information processing apparatus, information processing method, and information processing program according to the present application (hereinafter referred to as "embodiments") will be described in detail with reference to the drawings. Note that the information processing apparatus, information processing method, and information processing program according to the present application are not limited by this embodiment. Further, in each of the following embodiments, the same reference numerals are assigned to the same parts, and duplicate descriptions are omitted.

[0014] [1. Embodiment] Information processing implemented by the information processing apparatus and the like according to the embodiment will be described using Figure 1. Figure 1 is a diagram illustrating an example of an overview (Part 1) of information processing according to the embodiment. Note that in Figure 1, the information processing and the like according to the embodiment are assumed to be implemented by a payment server 100 which is an example of the information processing apparatus according to the embodiment.

[0015] (1-1. System Configuration) As shown in Figure 1, an information processing system 1 according to an embodiment includes a user terminal 10, a bank server 20, and a payment server 100. The user terminal 10, the bank server 20, and the payment server 100 are communicatively connected to each other by wire or wirelessly via a network N (refer to, for example, Figure 5). The network N is, for example, a WAN (Wide Area Network) such as the Internet. Note that the information processing system 1 shown in Figure 1 may include a plurality of user terminals 10, a plurality of bank servers 20, and a plurality of payment servers 100.

[0016] The payment server 100 shown in Figure 1 is an information processing apparatus that executes information processing according to the embodiment, and is implemented by a server apparatus, a cloud system, or the like. For example, the payment server 100 provides service users with an electronic payment service related to electronic payment using the user terminal 10 (a service that provides a predetermined transaction means for controlling the exchange of electronic money via code payment). The payment server 100 executes information processing related to the electronic payment service. Specifically, the payment server 100 distributes an application program for user terminals for realizing code payment (hereinafter appropriately referred to as "user application") to general consumers who are service users. When receiving a transaction request from the user application via an interface dedicated to the user application, the payment server 100 executes information processing including electronic money remittance processing between accounts in accordance with the transaction request. The user application transmits transaction information including information such as a payment destination, a payment source, and a payment amount to the payment server 100. Note that the transaction information may include, in addition to the above-mentioned pieces of information, 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.

[0017] Furthermore, as one of the services mentioned above, the payment server 100 provides a service for receiving electronic money payments via bank transfer using an electronic payment service platform. For example, the payment server 100 provides a service for receiving salary payments via electronic money and various other types of bank transfers. The specific details of the information processing will be described in detail later. Note that the service for receiving salary payments and various other types of bank transfers may be configured as a mini-application launched within the user application for implementing code payments, or it may be a separate application program prepared independently of this user application.

[0018] The user terminal 10 shown in Figure 1 is a general consumer who receives transaction items from a store and is an information processing device used by the user UX of the service provided by the payment server 100. The user terminal 10 can be implemented as, for example, a smartphone, tablet, notebook PC (Personal Computer), desktop PC, mobile phone, or PDA (Personal Digital Assistant). The user terminal 10 also displays the information distributed by the payment server 100 using a web browser or application. In Figure 1, a smartphone is used as an example of the user terminal 10.

[0019] When the user terminal 10 receives control information from the payment server 100 to perform predetermined information processing, it performs the information processing according to the control information. Here, the control information is written in, for example, a scripting language such as JavaScript (registered trademark), a stylesheet language such as CSS (Cascading Style Sheets), a programming language such as Java (registered trademark), or a markup language such as HTML (HyperText Markup Language). Alternatively, the predetermined application itself distributed from the payment server 100 may be considered as the control information.

[0020] The bank server 20 shown in Figure 1 is an information processing device belonging to a bank (an example of a "financial institution") that manages bank accounts opened by interested individuals, and is implemented using server equipment or a cloud system. For example, the bank server 20 manages information related to withdrawals from bank accounts by various card companies and service providers (such as the amount withdrawn and the date and time of withdrawal), as well as current account information (such as the account balance), as a history of bank account usage, and associates it with the account holder.

[0021] (1-2. Regarding payment using user terminal 10) Here, we will describe an example of code payment (electronic payment) using the user terminal 10. In the following description, we will explain an example in which a user UX, who receives the transaction item from store X, makes a payment using the user terminal 10, using a two-dimensional code (QR code®) placed in store X that displays store identification information identifying store X. Note that the code payment example described below is also applicable when any user makes a payment at any store using any user terminal 10. Furthermore, the two-dimensional code displaying store identification information is not limited to a QR code, but may also be a barcode, a predetermined mark, a number, etc. Also, the two-dimensional code is not limited to examples that are physically constructed as printed material printed on a medium such as paper, but may also be constructed as image information displayed on any terminal.

[0022] For example, when a user UX makes a payment for purchasing or using various goods or services at store X, the user UX launches a user application pre-installed on the user terminal 10. The user UX then scans a 2D code installed at store X via the user application. In this case, the user terminal 10 displays a screen for entering the price of the transaction and accepts the payment amount from either the user UX or a store employee at store X. The user terminal 10 then sends transaction information to the payment server 100, including user identification information that identifies the user UX, store identification information (or information indicated by the store identification information, i.e., information indicating store X (for example, store ID)), and the payment amount.

[0023] When the payment server 100 receives transaction information from the user terminal 10, it transfers electronic money equivalent to the payment amount from the user UX account indicated by the user identification information to the store X account indicated by the store identification information. At this time, the payment server 100 may deduct a predetermined fee to be charged to store X from the electronic money equivalent to the payment amount before transferring it to store X's account. The payment server 100 then sends a notification to the user terminal 10 that the transaction has been completed. In this case, the user terminal 10 notifies the user UX that the electronic money transaction has been completed by displaying a screen or outputting a predetermined sound indicating that the transaction has been completed. Alternatively, the payment server 100 may withdraw electronic money equivalent to the payment amount from the user UX account indicated by the user identification information, manage it as sales information for store X, and transfer the amount of cash equivalent to the sales to the bank account held by store X at a predetermined time. In this case, the payment server 100 may notify the user UX that the electronic money transaction has been completed at the time the electronic money equivalent to the payment amount is withdrawn from the user UX's account.

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

[0025] When the payment server 100 receives transaction information from the store terminal, it transfers electronic money equivalent to the payment amount from the user UX's account, indicated by the user identification information, to the store X's account. The payment server 100 then sends a notification to the store terminal or user terminal 10 that the transaction has been completed. The store terminal or user terminal 10 notifies the user UX that the electronic money transaction has been completed by displaying a screen or outputting a predetermined sound indicating that the transaction has been completed. Alternatively, the payment server 100 may withdraw electronic money equivalent to the payment amount from the user UX's account, manage it as sales information for store X, and transfer the amount equivalent to the sales in cash to a bank account held by store X at a predetermined time. In this case, the payment server 100 may notify the store clerk or user UX that the electronic money transaction has been completed at the time the electronic money equivalent to the payment amount is withdrawn from the user UX's account.

[0026] Furthermore, payment using the user terminal 10 may involve not only transferring electronic money from an account pre-charged by the user UX to the store X's account, but also, for example, payment using a credit card pre-registered by the user UX. In such a case, for example, the user terminal 10 may transfer the amount of electronic money indicated by the payment amount to the store X's account and simultaneously bill the credit card company of the user UX for the amount indicated by the payment amount.

[0027] Furthermore, payment using the user terminal 10 may not only involve transferring electronic money from the user UX's account to the store X's account, but also, for example, transferring electronic money from the user UX's account to another user's account (i.e., a transfer between users). For example, the user terminal 10 used by the sending user UX reads user identification information that identifies the recipient user (for example, user identification information displayed on the terminal device used by the recipient user), accepts input of the transfer amount from the user UX, and sends the read identification information, the transfer amount, and information indicating the user identification information that identifies the user UX to the payment server 100. In such a case, the payment server 100 transfers the amount of electronic money indicated by the transfer amount from the user UX's account to the recipient user's account, and may notify the user terminal 10 or the recipient user's terminal device that the transfer has been completed by displaying a screen or a predetermined sound indicating that the transfer has been completed.

[0028] It should be noted that remittances using the user terminal 10 are not limited to the process described above. For example, a remittance using the user terminal 10 may be performed by inputting the recipient user's phone number or information identifying the recipient user (for example, a user ID) into the user terminal 10. To give a specific example, the user terminal 10 receives input from the user UX, including the recipient user's phone number or user ID and the remittance amount, and transmits the entered phone number or user ID, the remittance amount, and user identification information that identifies the user UX to the payment server 100. The payment server 100 then transfers the amount of electronic money indicated by the remittance amount from the user UX's account to the user's account linked to the transmitted phone number or user ID.

[0029] Here, the recipient user's phone number or user ID may be pre-registered in the user app in conjunction with information about that user. In this case, the user terminal 10 receives the user UX to specify the user (recipient) registered in the user app and input the amount to be sent to that user, and sends the phone number or user ID associated with the specified user, the amount to be sent, and user identification information that identifies the user UX to the payment server 100.

[0030] Furthermore, for example, a remittance using the user terminal 10 may be performed by providing the recipient user with link information for receiving the remittance amount. To give a specific example, the user terminal 10 receives input of the remittance amount from the user UX, generates link information for receiving the remittance amount, and provides the link information to the terminal device used by the recipient user by sending an email containing the link information or posting information containing the link information to an SNS (Social Networking Service). When the recipient user selects the link information and performs the receiving operation, the settlement server 100 transfers the amount of electronic money indicated by the remittance amount from the user UX's account to the recipient user's account.

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

[0032] (1-3. Overview of the Implementation) (1-3-1. Application for Use (Part 1)) The following describes the information processing related to the bank transfer service performed by the payment server 100. First, using Figure 1, we will explain the overview of the processing in response to an application for the bank transfer service (part 1). Figure 1 shows an overview of an application by a service user who wishes to receive bank transfer payments other than salary payments using electronic money.

[0033] In the following explanation, user terminal 10 may be treated as identical to user UX. In other words, in the following, user UX can be read as user terminal 10.

[0034] As shown in Figure 1, the settlement server 100 requests the lending of virtual accounts from the bank server 20, which belongs to a partner bank (an example of a "financial institution") (step S11). A virtual account is a set of virtual accounts linked to the same bank account owned by the business operator running the settlement server 100 at the partner bank. These virtual accounts do not function as bank accounts, but rather as unique number information for identifying the recipient of a transfer, and function as dedicated accounts for accepting various transfers. The bank server 20 lends out virtual accounts in response to the request from the settlement server 100 (step S12). The settlement server 100 can borrow a predetermined volume of virtual accounts (for example, any number such as a maximum of 9,999,999 accounts) from the bank server 20 at one time.

[0035] The user UX sends a request to the settlement server 100 to create a dedicated account for bank transfers via the top screen of the user application displayed on the user terminal 10 (for example, screen D1-1) (step S13).

[0036] When the payment server 100 receives a request from the user terminal 10 to create a dedicated account for bank transfers, it performs virtual account assignment and user information registration (step S14). For example, the payment server 100 arbitrarily selects a virtual account from among several unused virtual accounts pre-lent by a partner bank and assigns it as a dedicated account (virtual account) corresponding to the user UX that made the request. The payment server 100 then registers the account information to identify the assigned dedicated account (virtual account) in association with identification information unique to the user UX and manages it as user information. As identification information unique to the user UX, for example, the user ID that the payment server 100 individually assigns to each user when they register to use the electronic payment service can be used.

[0037] Furthermore, in order to comply with the regulations on the retention of funds in the money transfer business, which are mandated by law, the payment server 100 obtains information from the user UX at the time of application for use regarding a bank account for refunds, which is linked to the dedicated bank account for transfer deposits, in order to refund any amount exceeding a predetermined amount from the amount deposited to the dedicated bank account for transfer deposits (recipient of the remittance). The payment server 100 associates the bank account information for refunds obtained from the user UX with the unique information mentioned above and registers it as user information.

[0038] Once the assignment of the virtual account and the registration of user information are complete, the payment server 100 provides the user UX with account information by sending account information to the user terminal 10 to identify the virtual account assigned to the user UX as dedicated account information for bank transfer deposits (step S15).

[0039] The following describes an example of screen transitions displayed on the user terminal 10 in response to an application for the bank transfer deposit service. Screen D1-1 shown in Figure 1 is an example of the top screen of the user application displayed on the user terminal 10 according to the user UX operation. Screen D1-1 shown in Figure 1 has an icon OB1-1 for applying to use the bank transfer deposit service.

[0040] Furthermore, screen D1-2 shown in Figure 1 is an example of a dedicated account creation request screen displayed on the user terminal 10 according to the user UX's operation of icon OB1-1. Screen D1-2 shown in Figure 1 is provided with a button OB1-2 for sending a request to create a dedicated account for bank transfers to the settlement server 100. Button OB1-2 may be configured to accept operations from the user UX, for example, on the condition that the user enters refund account information and agrees to the terms of service and handling of personal information.

[0041] Furthermore, screen D1-3 shown in Figure 1 is an example of a response screen sent from the payment server 100 to the user terminal 10 in response to a request to create a dedicated account for bank transfers, which is sent from the user terminal 10 to the payment server 100 in accordance with the user UX's operation of button OB1-2. Screen D1-3 shown in Figure 1 displays information about the dedicated account for bank transfers created by the payment server 100. The user UX informs the recipient of the bank transfer of this information about the dedicated account for bank transfers. The recipient makes a bank transfer using the dedicated account for bank transfers notified by the user UX as the recipient (sender). When the payment server 100 detects that a bank transfer has been made to the dedicated account for bank transfers, it charges the user UX's electronic money account corresponding to the dedicated account for bank transfers with electronic money equivalent to the amount deposited into the dedicated account. In other words, the payment server 100 reflects the deposit amount in the money balance linked to the user UX's account corresponding to the dedicated account for bank transfers.

[0042] (1-3-2. Application for Use (Part 2)) The following describes the overview of the processing (part 2) in response to an application for the bank transfer service, using Figure 2. Figure 2 is a diagram showing an example of the overview of information processing (part 2) according to the embodiment. Figure 2 shows an overview of the application by a service user who wishes to receive their salary via bank transfer using electronic money. Note that the processing procedures of steps S21 to S22 shown in Figure 2 correspond to the processing procedures of steps S11 to S12 shown in Figure 1, so the explanation is omitted.

[0043] As shown in Figure 2, the user UX sends a request to the settlement server 100 to create a dedicated account for receiving salary via the top screen of the user application displayed on the user terminal 10 (for example, screen D2-1) (step S23).

[0044] When the payment server 100 receives a request from the user terminal 10 to create a dedicated account for receiving salary, it performs the assignment of a virtual account and registration of user information (step S24). For example, the payment server 100 arbitrarily selects a virtual account from among several unused virtual accounts that have been pre-loaned by a partner bank and assigns it as a dedicated account (virtual account) corresponding to the user UX that made the request. The payment server 100 then registers the account information to identify the assigned dedicated account (virtual account) in association with identification information unique to the user UX and manages it as user information. As identification information unique to the user UX, for example, the user ID that the payment server 100 individually assigns to each user when they register to use the electronic payment service can be used.

[0045] Furthermore, the payment server 100 obtains information regarding specified necessary items from the user UX when an application is made, for the purpose of ensuring compliance with the aforementioned retention regulations and detecting errors in remittances disguised as salaries. These specified necessary items are expected to include the employer or workplace, employee number, name within the company, amount to be received, and bank account for refunds. Information regarding the employer or workplace is expected to be used to verify the source of the remittance in the salary payment service. The employee number is expected to be used as a key to verify the identity of the remitter if there is an error in the remittance. The name within the company is expected to be used to verify the account holder designated as the recipient of the remittance. The amount to be received is expected to be used to adjust the amount so as not to exceed a predetermined amount. The bank account for refunds is expected to be used as the recipient for amounts exceeding the predetermined amount. The payment server 100 registers the specified information obtained from the user UX as user information, associating it with the unique information mentioned above.

[0046] Once the assignment of the virtual account and the registration of user information are complete, the payment server 100 provides the user UX with account information by sending the account information related to the virtual account assigned to the user UX to the user terminal 10 (step S25).

[0047] The following describes an example of screen transitions displayed on the user terminal 10 in response to an application for a transfer deposit service for receiving salary via electronic money. Screen D2-1 shown in Figure 2 is an example of the top screen of the user application displayed on the user terminal 10 according to the user UX operation. Screen D2-1 shown in Figure 2 has an icon OB2-1 for applying to receive salary via electronic money.

[0048] Furthermore, screen D2-2 shown in Figure 2 is an example of a dedicated account creation request screen displayed on the user terminal 10 in accordance with the user UX's operation of button OB2-2. Screen D2-2 shown in Figure 2 is provided with button OB2-2 for sending a request to the settlement server 100 to create a dedicated account for receiving salary. Button OB2-2 may be configured to accept operation from the user UX, for example, on the condition that the user enters the required information and agrees to the terms of service and the handling of personal information.

[0049] Furthermore, screen D2-3 shown in Figure 2 is an example of a response screen sent from the payment server 100 to the user terminal 10 in response to a request to create a dedicated account for receiving salaries, which is sent from the user terminal 10 to the payment server 100 in accordance with the user UX's operation of button OB2-2. Screen D2-3 shown in Figure 2 displays information about the dedicated account for receiving salaries created by the payment server 100. Here, the payment server 100 assigns a name indicating that it is for receiving salaries (for example, "Salary Branch") as the branch name for the dedicated account for receiving salaries. The user UX informs the transfer requester of this information about the dedicated account for receiving salaries. The transfer requester makes a transfer using the dedicated account for receiving salaries notified by the user UX as the transfer destination (recipient of the funds). When the payment server 100 detects a deposit from the transfer requester to the dedicated account for receiving salaries, it charges the user UX's electronic money account corresponding to the dedicated account for receiving salaries with electronic money equivalent to the deposit amount. In other words, the payment server 100 reflects the deposit amount in the money balance linked to the user UX account corresponding to the dedicated account for receiving salaries.

[0050] As described above, the settlement server 100 can assign virtual accounts to users for each purpose of use, such as transfers other than salary payments and transfers of salary payments. In the examples shown in Figures 1 and 2, the settlement server 100 explains the outline of processing when it receives applications for transfers other than salary payments and applications for transfers of salary payments separately, but it is not necessary to be limited to these examples. For example, after receiving an application for a transfer payment service, the settlement server 100 may allow the service user to select whether the purpose of use is a transfer of a non-salary payment or a transfer of salary payments.

[0051] Furthermore, the payment server 100 may assign virtual accounts to service users as dedicated accounts for transfer deposit services other than salary payments, in response to applications for such services. These virtual accounts may have a predetermined expiration date for their use. In addition, the payment server 100 may assign virtual accounts to service users in response to applications for transfer deposit services other than salary payments as one-time accounts. This promotes the renewal of virtual accounts and ensures their effective use.

[0052] Furthermore, if the payment server 100 assigns virtual accounts to service users for each purpose of use, it may manage money balances separately for each purpose of use. For example, the payment server 100 can separately manage money balances corresponding to transfer payments made through transfer payment services other than salary payments, as shown in Figure 1, and money balances corresponding to transfer payments made through transfer payment services for salary receipts, as shown in Figure 2.

[0053] (1-4. Processing of bank transfer deposits) The following will explain the overview of the processing for reflecting bank transfers made through the bank transfer service, using Figure 3 as an example. Figure 3 is a diagram showing an example of the overview of information processing (part 3) according to the embodiment. Figure 3 shows an overview of the processing in the information processing system 1 when users UX and UY, who are service users, apply to use the bank transfer service for payments other than salaries, and user UZ applies to use the bank transfer service for salaries.

[0054] As shown in Figure 3, when the user UX uses the bank transfer service, it notifies the recipient of the transfer information, including information indicating a dedicated account for bank transfers notified by the settlement server 100. For example, the user UX notifies company A, the recipient of the transfer, of the bank name: "ABC Bank", branch number: "123", branch name: "DEF", account type: "Savings", account number indicating a virtual account: "111112", and (account holder's) name: "Tokkyo Kenichi".

[0055] Furthermore, when user UY uses the bank transfer service, it notifies the recipient of the transfer information, including information indicating a dedicated account for bank transfers notified by the settlement server 100. For example, user UY notifies company B, the recipient of the transfer, of the bank name: "ABC Bank", branch number: "123", branch name: "DEF", account type: "Savings", account number indicating a virtual account: "111113", and (account holder's) name: "Ishou Sakurako".

[0056] Furthermore, when user UZ uses the transfer deposit service, it notifies the transfer requester of the transfer destination information, including information indicating a dedicated account for receiving salary, which has been notified by the settlement server 100. For example, user UZ notifies employer C, the transfer requester, of the bank name: "ABC Bank", branch number: "123", branch name: "Kyuyo Branch", account type: "Savings", account number indicating a virtual account: "111111", and (account holder's) name: "Shohyojin".

[0057] When Company A receives a bank transfer request from a user UX, it makes the transfer based on the recipient information provided by the user UX. For example, Company A sends the amount specified by the user UX from its own bank account to the bank (branch) account and account holder listed in the recipient information. Figure 3 shows an example where Company A sends cash of "¥30,000" to a dedicated account number "111112" whose account holder is "Tokkyo Kenichi".

[0058] When Company B receives a bank transfer request from User UY, it makes the transfer based on the recipient information provided by User UY. For example, Company B sends the amount specified by User UX from its own bank account to the bank (branch) account and account holder listed in the recipient information. Figure 3 shows an example where Company B sends cash of ¥50,000 to a dedicated account number "111113" whose account holder is "Ishou Sakurako".

[0059] When employer C receives a request from user UZ to receive a salary via bank transfer, C makes the transfer based on the recipient information provided by user UZ. For example, employer C sends user UZ's salary from the sending bank where C has a bank account, using the bank (branch) account and account holder name specified in the recipient information as the recipient. Figure 3 shows an example where employer C sends a salary of "¥250,000" to a dedicated account number "111111" whose account holder is "Shohyojin".

[0060] The payment server 100 performs a detection process to detect transfer deposits to dedicated accounts (virtual accounts) individually assigned to each user from among multiple virtual accounts linked to the same bank account (step S31). For example, the payment server 100 checks the balance of the bank account to which multiple dedicated accounts (virtual accounts) are linked at a predetermined time. Then, if the balance of the relevant bank account has increased, the payment server 100 individually identifies the dedicated account number that indicates the dedicated account (virtual account) designated as the recipient of the transfer.

[0061] Furthermore, when the settlement server 100 detects a deposit to the dedicated account number for bank transfers, it executes a process to confirm the details of the transfer (step S32). Then, the settlement server 100 executes a process according to the result of the confirmation of the transfer details (steps S33 to S35).

[0062] For example, the payment server 100 retrieves the balance of a dedicated account (virtual account) associated with the target user (e.g., user UX, user UY, user UZ, etc.) to whom the bank transfer deposit is to be sent. The payment server 100 then determines whether the balance of the dedicated account (virtual account) after reflecting the amount of the bank transfer deposit exceeds a predetermined amount.

[0063] If the balance of the dedicated account (virtual account) does not exceed a predetermined amount, the payment server 100 performs a charge process to reflect the amount of the transfer deposit to the electronic money balance owned by the target user (step S33). On the other hand, if the balance of the dedicated account (virtual account) exceeds a predetermined amount, the payment server 100 performs a refund process to send cash equivalent to the amount exceeding the predetermined amount to the bank account pre-linked to the target user as the recipient (step S34).

[0064] Furthermore, if the payment server 100 detects a transfer deposit that is for salary payment, it may send a confirmation request to the user to verify the details of the transfer (step S35). For example, if the source of the transfer deposit is different from the workplace or employer that the user has set in advance, the payment server 100 may send a confirmation notification to the user terminal 10 to ask whether or not it is indeed a transfer deposit for salary payment. In this case, if the payment server 100 receives confirmation from the user, it will perform processing such as charging the money balance. The payment server 100 may also trace the user's transfer deposit history and, if salary payment deposits are made at irregular intervals, send a confirmation notification to the user terminal 10 to ask the user to confirm whether or not it is indeed a transfer deposit for salary payment. This prevents the bank transfer service from being used for purposes other than those intended.

[0065] Furthermore, the payment server 100 may, at a predetermined time, acquire information for each service user indicating the balance of money managed as part of their salary, and notify the partner bank. In the event that a money transfer service provider fails, the partner bank may guarantee the electronic money paid as salary. In such cases, it is useful for the partner bank to check the balance of the electronic money paid to the user as salary, as this allows them to determine the amount that needs to be guaranteed.

[0066] Furthermore, when a user applies to use the payroll transfer service, the payment server 100 may allow the user to select the amount they wish to receive as electronic money from the total amount of the transfer. In this case, the payment server 100 can process the transfer by deducting the amount to be received as electronic money from the total amount and transferring the difference in cash to the user's bank account.

[0067] Furthermore, the operator of the payment server 100 may make prior agreements with its partner banks to refuse to accept bank transfers if the amount of a single deposit (1 shot) exceeds a predetermined amount. For example, the payment server 100 sends information to the bank server 20 at a predetermined time indicating the predetermined amount for which it will refuse to accept deposits to the virtual account. Note that the predetermined amount may be set for each purpose of use (bank transfer service).

[0068] Furthermore, the settlement server 100 may obtain from the bank server 20 information regarding transfer deposits that have been rejected by the bank server 20. For example, in the transfer deposit service for salary payments, if the amount of a single deposit (1 shot) exceeds a predetermined amount, the settlement server 100 determines that there is a high probability that the next deposit will also exceed the predetermined amount. In this case, the settlement server 100 sends a confirmation notice to the user associated with the virtual account to which the transfer deposit is sent, asking whether or not they wish to continue using the transfer deposit service for salary payments next time. This prevents the partner bank from rejecting the deposit again next time.

[0069] (1-5. Example of payment notification) The following section will explain an example of a notification of a bank transfer payment made by the bank transfer payment service, using Figure 4 as an example. Figure 4 is a diagram showing an example of a notification of a bank transfer payment made by the bank transfer payment service according to the embodiment. Figure 4 shows an example of a payment notification when a payment is made to the user UX by the bank transfer payment service.

[0070] Screen D3-1 shown in Figure 4 is an example of the top screen of a user application displayed on the user terminal 10 according to the user UX operation. Screen D3-1 shown in Figure 4 displays a general-purpose pop-up OB3-1 that notifies the user UX that a deposit has been made via the bank transfer service.

[0071] The screen D3-2 shown in Figure 4 is an example of a notification details screen displayed on the user terminal 10 in accordance with the user UX's operation of the popup OB3-1. In Figure 4, an example is shown where screen D3-2 displays detailed information corresponding to popup OB3-1, such as "A deposit of 30,000 yen has been received from Company A." This allows both companies' UX to confirm that the bank transfer deposit service has functioned correctly.

[0072] (1-6. Name Change Processing) The following explanation of the name change process in the bank transfer deposit service will be given using Figure 5. Figure 5 is a diagram illustrating the overview of the name change process according to the embodiment. The bank transfer deposit service described above has room for improvement in the following respects.

[0073] For example, in the example shown in Figure 3 above, when user UZ uses the transfer deposit service, the payment server 100 notifies the recipient of the transfer information, including information indicating a dedicated account for receiving salary payments, to the transfer requester (e.g., employer C). On the other hand, in the transfer deposit service described above, the account names of the multiple virtual accounts that the payment server 100 has borrowed from the bank server 20 are those of the business operator PP, which provides the transfer deposit service through the payment server 100. Therefore, if the transfer requester (e.g., employer C) adopts a policy or scheme that requires an exact match between the recipient's name (e.g., "Show Payer") and the name of the dedicated account to which the transfer will be made (e.g., business operator PP), the salary transfer may not be made. Such a situation can occur not only with salary transfers but also with other transfer deposits. In light of the occurrence of such a situation, the payment server 100 executes the name change process described below.

[0074] As shown in Figure 5, for example, the user UX sends a request to the settlement server 100 to create a dedicated account for bank transfers through the top screen of the user application displayed on the user terminal 10 (for example, screen D1-1 shown in Figure 1) (step S41).

[0075] When the payment server 100 receives a request from the user terminal 10 to create a dedicated account for bank transfers, it performs a status check on the user UX that made the request (step S42). Specifically, the payment server 100 refers to the status information associated with the user ID, which is included in the dedicated account creation request as unique identification information for the user UX, and determines whether or not the user UX that made the request has completed the identity verification procedure.

[0076] The identity verification procedure may be performed in advance as a compliance check when applying for a bank transfer service, for example, or it may be performed at any time upon request from the service user. The identity verification procedure is expected to be carried out by means of KYC (Know Your Customer) or eKYC (electronic Know Your Customer). The payment server 100 manages the results of the identity verification procedure and the identity verification information used in the identity verification procedure, associating them with the user ID. When the payment server 100 receives prescribed documents by mail from the service user as identity verification information, it stores and manages information about the received documents as identity verification information in its storage unit. Also, when the payment server 100 receives identity verification information uploaded online from the service user, it stores and manages the received identity verification information in its storage unit. The identity verification information can use any information that can identify the person, and examples include information such as a driver's license, passport, My Number card, or an image (selfie) showing the person's appearance taken by the service user themselves.

[0077] The payment server 100 assigns a dedicated account (virtual account) for bank transfers to the user UX that made the request, according to the status determination result (step S43). Specifically, if the status of the user UX that made the request is that the identity verification procedure has been completed, the payment server 100 arbitrarily selects a virtual account from among several unused virtual accounts that have been pre-loaned by the partner bank and assigns it as a dedicated account (virtual account) corresponding to the user UX that made the request.

[0078] Furthermore, the payment server 100 stores the account number, which identifies the dedicated account (virtual account) assigned to the user UX, in the storage unit as user information, associating it with the user ID corresponding to the user UX (step S44).

[0079] After assigning an account to the user UX, the settlement server 100 performs a name change process to change the name of the dedicated account (virtual account) assigned to the user UX to the user's name (step S45). Specifically, the settlement server 100 sends a name change request to the bank server 20, which includes the account number of the virtual account to be changed (for example, "111112") and the desired name change (for example, "Tokkyo Kenichi") (step S45). The name change process may be performed as part of a series of processes after assigning a dedicated account (virtual account) to the user UX, as described above, or it may be performed as an on-demand process in response to a request from the user UX.

[0080] Alternatively, the name change process by the settlement server 100 may be performed by accessing a management file that manages virtual accounts lent by the bank to the settlement server 100 through a predetermined interface such as an API provided by the bank, and rewriting the account name information associated with the virtual account in the management file.

[0081] After the name change process is completed, the payment server 100 notifies the user UX by sending account information, including the account number (for example, "111112") and account name (for example, "Tokkyo Kenichi"), to the user terminal 10 (step S46).

[0082] As described above, the payment server 100, in response to a request to create a dedicated account for bank transfers, executes a name change process for the dedicated account (virtual account) assigned to the service user who made the request. In this way, it is possible to support the smooth operation of the bank transfer service scheme provided through the same platform as the electronic payment service and to expand the use of the electronic payment service.

[0083] Furthermore, if the payment server 100 determines, based on the status check, that the identity verification procedure for the user UX that requested the creation has been completed, it may assign a dedicated account (virtual account) for bank transfers to the user UX that requested the creation, provided that the identity verification information used in the identity verification procedure is still valid. In addition, when the payment server 100 performs a name change process, it may change the name of the dedicated account (virtual account) to the user name of the user UX that was confirmed in the identity verification procedure.

[0084] Furthermore, the payment server 100 may set and manage an expiration date for the virtual account assigned to the user UX that requested its creation. For example, the payment server 100 stores and manages the expiration date of the virtual account assigned to the service user in a memory unit, associating it with the user ID, in accordance with the expiration date of the identity verification information. For example, in the case shown in Figure 5, the payment server 100 stores and manages the expiration date of the dedicated account (virtual account) assigned to the user UX, which is "2024 / 10 / 01", as the expiration date of the identity verification information, in a memory unit, associating it with the user ID.

[0085] Furthermore, the payment server 100 may accept requests from service users of the bank transfer service to change their personal identification information. In this case, based on the change request received from the service user, the payment server 100 associates the user ID with the user ID, updates the personal identification information before the change to the new personal identification information, and stores it in the storage unit. Note that the function for service users to request changes to their personal identification information may be included in the user application. Also, when the payment server 100 receives a change in personal identification information, if the user's name has changed (for example, if their surname has changed due to marriage), it may also change the account name accordingly.

[0086] Furthermore, when the payment server 100 changes the user name of a dedicated account (virtual account) assigned to the service user who made the creation request during the name change process, it may apply the service user's username or any string of characters that the user wishes to use as the name. The payment server 100 may also set a limit on the number of characters in the changed user name. In this case, if the user name corresponding to the change request exceeds the pre-set upper limit of characters, the payment server 100 will execute the name change process using an adjusted user name that has been adjusted so that the user name is less than or equal to the upper limit of characters. For example, the payment server 100 can adjust the number of characters in the user name from the beginning so that it is less than or equal to the upper limit of characters. In addition, if the expiration date of the identity verification information and the expiration date of the virtual account are set in association, the payment server 100 may notify the user's terminal of a request to update identity verification when the expiration date of the identity verification information is approaching, for example, one month before the expiration date, including either a notification that the identity verification deadline is approaching and a notification that the virtual account will become unusable if the deadline is exceeded, or both.

[0087] (1-7. Transfer Amount Adjustment Process) The following explanation of the transfer amount adjustment process in the transfer deposit service will be given using Figure 6. Figure 6 is a diagram illustrating the overview of the transfer amount adjustment process according to the embodiment. The transfer deposit service described above has room for improvement in the following respects.

[0088] The aforementioned bank transfer service performs processing aimed at complying with the retention regulations for money transfer businesses mandated by law. For example, the business operator of the settlement server 100 may make prior agreements with its partner banks to refuse to accept bank transfers if the amount of a single transfer exceeds a predetermined amount. As a result, the bank server 20 will refuse to accept bank transfers at the point of entry if the amount of a single transfer exceeds a predetermined amount.

[0089] Alternatively, the settlement server 100 determines whether the money balance after reflecting the deposit amount to the dedicated account (virtual account) exceeds a predetermined amount, even if the deposit amount in a single transaction (1 shot) does not exceed a predetermined amount. If the money balance associated with the service user to be processed (hereinafter referred to as "target user") exceeds a predetermined amount, the settlement server 100 executes a refund process by sending cash equivalent to the amount exceeding the predetermined amount to the bank account previously linked to the target user as the recipient.

[0090] Thus, processes to limit the deposit amount are executed on both the bank server 20 and the settlement server 100. On the other hand, let's assume that the settlement server 100 employs a scheme in which it executes a refund process on the condition that the service user has completed the identity verification procedure. Under this assumption, for example, if a deposit is accepted into a dedicated account and the money balance exceeds a predetermined amount, the refund will not be made if the target user to whom the refund is to be issued has not completed the identity verification procedure. Therefore, the settlement server 100 according to this embodiment executes the transfer amount adjustment process described below.

[0091] As shown in Figure 6, the payment server 100 refers to the account information and calculates the amount that can be charged to the service user to be processed (step S51). Specifically, the payment server 100 calculates the amount that can be charged to the service user based on the difference between the current money balance associated with the user account of the service user to be processed and the upper limit of the money balance corresponding to the service user. For example, in the case shown in Figure 6, the payment server 100 calculates the amount that can be charged as 900,000 yen, which is the difference between the current money balance of the service user to be processed, which is 100,000 yen, and the upper limit of the money balance corresponding to the service user, which is 1,000,000 yen.

[0092] The payment server 100 may calculate the amount that can be charged at a predetermined time in accordance with the increase or decrease in the money balance associated with the user account of the service user. For example, the payment server 100 may check the money balance of each service user at a predetermined time (for example, daily), identify service users whose money balance has increased or decreased as targets for processing, and calculate the amount that can be charged for the identified target service users. Alternatively, the payment server 100 may extract the target service users and then calculate the amount that can be charged at a predetermined time. Furthermore, the payment server 100 may control the timing of checking the next available charge amount for each service user and notifying them of the maximum transfer amount to the bank, based on the available charge amount of the service user, the frequency of charging the money balance, and the frequency of using the money balance. For example, the payment server 100 may adjust the cycle for calculating the available charge amount according to the available charge amount, the frequency of charging the money balance, and the frequency of using the money balance. Specifically, the payment server 100 can achieve efficient processing by, for example, shortening the calculation period for the chargeable amount for service users whose chargeable amount is less than a certain amount compared to service users whose chargeable amount is above a certain amount. Also, for example, the payment server 100 can achieve efficient processing by, for example, lengthening the calculation period for the chargeable amount for service users who charge or use their money balance relatively less frequently compared to other service users (for example, service users whose usage frequency is below a predetermined threshold) compared to service users who charge or use their money balance relatively more frequently (service users whose usage frequency is above a predetermined threshold). The period may be updated again at the time the chargeable amount is calculated, according to the size of the chargeable amount, the frequency of charging the money balance, and the frequency of using the money balance.

[0093] Next, the settlement server 100 notifies the bank server 20 of the chargeable amount calculated in step S51 as the transfer limit for the virtual account assigned to the service user to be processed (step S52). Specifically, the settlement server 100 refers to the user information and identifies the account number of the virtual account assigned to the service user based on the user ID of the service user to be processed. Then, the settlement server 100 sends a notification to the bank server 20 that includes the information of the identified virtual account number and the information of the transfer limit. For example, in the case shown in Figure 6, the settlement server 100 sends a notification to the bank server 20 that includes the transfer limit of 900,000 yen and the account number "111112".

[0094] Alternatively, instead of sending a notification of the transfer limit to the bank server 20, the settlement server 100 may access a management file managed by the bank server 20 for each virtual account, via a predetermined interface such as an API provided in advance by the bank, and change the transfer limit by rewriting the transfer limit information associated with the relevant virtual account in the management file.

[0095] Furthermore, the payment server 100 may calculate the maximum chargeable amount if the service user to be processed has not completed the identity verification procedure. This allows the bank server 20 to implement deposit restrictions at the bank server 20 level for service users who have not completed this verification procedure, even if a scheme is adopted in which refund processing is performed on the condition that the service user has completed the identity verification procedure.

[0096] Furthermore, if the service user to be processed has completed the identity verification procedure, the payment server 100 can perform a refund process for that service user. In this case, the payment server 100 compares the money balance associated with the user account owned by the service user with the pre-set balance limit associated with the user account, and if the money balance exceeds the balance limit, it may pay out the amount equivalent to the excess amount of the money balance that exceeds the balance limit. Note that if the service user to be processed has completed the identity verification procedure, the payment server 100 can perform the above refund process, so it does not need to perform the transfer adjustment process.

[0097] Furthermore, when the payment server 100 executes a refund process, if the service user to whom the refund is to be issued has not registered a refund account, it may notify the service user of a request to register a refund account through a user app, which is a dedicated application provided to the service user. The payment server 100 can notify the service user of the request to register a refund account via push notification through the user app. In addition, the payment server 100 is not limited to notifications through the user app, but may also notify the service user using any means of communication that uses the user information registered by the service user, such as email, SMS (Short Message Service), or linked SNS (Social Networking Service).

[0098] Furthermore, the settlement server 100 can receive a transfer error from the bank server 20 due to a transfer deposit to a virtual account exceeding the transfer limit. In this case, the settlement server 100 may notify the user terminal 10 of the service user associated with the account number of the virtual account corresponding to the transfer error received from the bank server 20 of information regarding the transfer error. At this time, the settlement server 100 can notify the service user of information regarding the transfer error through push notifications via a user app, which is a dedicated application provided to the service user, or through any means of communication such as email.

[0099] [2. Configuration of the payment server] Next, the configuration of the payment server 100 will be described using Figure 7. Figure 7 is a diagram showing an example of the configuration of a payment server according to the embodiment. As shown in Figure 7, the payment server 100 has a communication unit 110, a storage unit 120, and a control unit 130.

[0100] (Regarding Communications Unit 110) The communication unit 110 is implemented, for example, by a NIC (Network Interface Card). The communication unit 110 is connected to the network N by wire or wireless connection and transmits and receives information with the user terminal 10, the bank server 20, and the like.

[0101] (Regarding memory unit 120) The storage unit 120 is implemented by, for example, semiconductor memory elements such as RAM (Random Access Memory) and flash memory, or by storage devices such as hard disks and optical discs. As shown in Figure 7, the storage unit 120 includes a virtual account information storage unit 121, a user information storage unit 122, and an account information storage unit 123.

[0102] (Regarding the virtual account information storage unit 121) The virtual account information storage unit 121 stores information about virtual accounts borrowed from partner banks. Figure 8 shows an example of information stored in the virtual account information storage unit according to this embodiment. As shown in Figure 8, the virtual account information stored in the virtual account information storage unit 121 includes a "virtual account number" item and a "status" item.

[0103] The "Virtual Account Number" field stores the unique account number for each of the multiple virtual accounts linked to the same bank account owned by the business operator that operates and manages the payment server 100 at the partner bank. Note that these virtual accounts do not function as bank accounts; rather, they are unique number information used to identify the recipient of a transfer (remittance) and function as dedicated accounts for accepting various transfers. Furthermore, at the time of loan from the bank, the name of this virtual account is the name of the business operator that operates and manages the payment server 100. The "Status" field stores information indicating whether the account number representing the virtual account is currently in use (assigned to a service user).

[0104] For example, Figure 8 shows that among the virtual account numbers, "111111," "111112," and "111113" are in use, while "999999" is unused.

[0105] (Regarding the user information storage unit 122) The user information storage unit 122 stores user information relating to service users of the transfer deposit service. Figure 9 shows an example of the information stored in the user information storage unit according to the embodiment. As shown in Figure 9, the user information stored in the user information storage unit has multiple items such as "User ID", "Virtual Account (Account Number)", "User Name", "Status", "Identity Verification Information Expiration Date", "Workplace / Employer", "Employee Number", "Name within the Company", "Amount to be Received (10,000 yen)", and "Bank Account for Refund". These items of user information are linked to each other.

[0106] The "User ID" field stores unique identification information for users of the bank transfer service. The "Virtual Account (Account Number)" field stores information about the account number of the virtual account assigned to the service user. The "User Name" field stores information about the name of the service user.

[0107] The "Status" field stores status information indicating whether or not the service user has completed the identity verification process. The "Identity Verification Information Expiration Date" field stores information indicating the expiration date of the identity verification information submitted by the service user for use in the identity verification process.

[0108] The "Workplace / Employer" field stores information such as the name of the company where the service user works and the employer who employs the service user. This information about the workplace and employer is intended to be used for purposes such as verifying the source of payments in the payroll deposit service.

[0109] The "Employee Number" field stores information indicating the employee number assigned to the service user by their workplace. The employee number is intended to be used as a key to verify the identity of the sender in case of errors in bank transfers.

[0110] The "Name within the company" field stores information indicating the name of the service user at their workplace. This name is intended to be used for purposes such as verifying the account holder's name when making a remittance.

[0111] The "Amount Received (10,000 yen)" field stores information indicating the amount of salary the service user is expected to receive from their employer or workplace. This amount is intended to be used to adjust the salary so that it does not exceed a predetermined amount.

[0112] The "Bank Account for Refunds" field stores information indicating the bank account owned by the service user. The bank account stored in the "Bank Account for Refunds" field will be used as the destination for a cash refund equivalent to the amount exceeding a predetermined limit if the amount of a single deposit via the transfer service exceeds a predetermined limit, or if the money balance after reflecting the deposit amount exceeds a predetermined limit. The information corresponding to the "Employer / Workplace," "Employee Number," "Name within the Company," "Amount to Receive (in 10,000 yen)," and "Bank Account for Refunds" fields is stored when the service user applies to use the transfer service for receiving their salary.

[0113] According to Figure 9, the virtual account number for bank transfers assigned to the service user identified by user ID: "U001" is "111112", the name is "Tokkyo Kenichi", and the "refund bank account" is "D Bank △△ Branch, Ordinary Account ********". Furthermore, Figure 9 indicates that the service user identified by user ID: "U001" has completed the identity verification procedure, and the expiration date of the identity verification information used in the procedure is "October 1, 2024".

[0114] (Regarding the account information storage unit 123) The account information storage unit 123 stores various types of information (account information) related to the electronic money account (settlement account) owned by the service user in the electronic payment service. Figure 10 is a diagram showing an example of the information stored in the account information storage unit according to the embodiment. As shown in Figure 10, the account information stored in the account information storage unit 123 has multiple items such as "account ID", "owner ID", "balance", "breakdown", and "maximum balance". These items of the account information are interconnected.

[0115] The "Account ID" field stores identification information to identify the electronic money account (also called a "payment account" or "wallet") associated with the service user's user account. The "Owner ID" field stores identification information to identify the owner (service user) of the electronic money account associated with the Account ID. The "Owner ID" field may store the same information as the information stored in the User ID field.

[0116] The "Balance" field stores information indicating the total balance, which is the balance of electronic money recorded in the electronic money account. The "Breakdown" field stores information indicating the breakdown of the money balance. Specifically, the "Breakdown" field includes the "Salary" field and the "Other" field. The "Salary" field stores information indicating the balance of digital money deposited as salary through the salary deposit service. The "Other" field stores information indicating the balance of digital money deposited as something other than salary through the deposit service. The "Balance Limit" field stores information indicating the maximum balance that can be deposited into the electronic money account. For example, the balance limit is pre-set for each service user.

[0117] According to Figure 10, the owner of the electronic money account identified by "Account ID": "Account 001" is the service user identified by Owner ID: "U001," and the money balance is "100,000," with all of the contents being excluding salary. Furthermore, as shown in Figure 10, the maximum balance amount corresponding to each owner (service user) is 1 million yen.

[0118] (Regarding the control unit 130) The control unit 130 is a controller, and is implemented, for example, by a CPU (Central Processing Unit) or MPU (Micro Processing Unit) executing various programs stored in the storage device inside the settlement server 100 using RAM as the working area. Alternatively, the control unit 130 can be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array). As shown in Figure 7, the control unit 130 according to this embodiment has a detection unit 131, a reflection unit 132, a management unit 133, a name change unit 134, a calculation unit 135, a transfer adjustment unit 136, and a payout unit 137, and each of these units realizes or executes the information processing functions and operations described below.

[0119] (Regarding the detection unit 131) The detection unit 131 detects transfers to dedicated accounts (virtual accounts) individually assigned to each service user from among multiple virtual accounts linked to the same bank account owned by the service provider (the service provider that provides transfer deposit services) at a partner bank (an example of a "financial institution"). When a transfer deposit is detected, the detection unit 131 passes information such as the account number of the dedicated account (virtual account) from which the transfer deposit was detected, the account holder's name of the recipient (sender), and the deposit amount to the reflection unit 132.

[0120] Furthermore, the detection unit 131 requests the partner bank to refuse to accept a bank transfer if the amount of a single transfer exceeds a predetermined amount.

[0121] Furthermore, if the balance of the virtual account after reflecting the deposit amount exceeds a predetermined amount, the detection unit 131 sends cash equivalent to the amount exceeding the predetermined amount to the bank account pre-linked to the service user as the recipient.

[0122] Furthermore, if the detection unit 131 detects that the transfer deposit is for salary payment, it may send a confirmation request to the user to verify the details of the transfer.

[0123] (Regarding the reflection unit 132) When the detection unit 131 detects a bank transfer deposit, the reflection unit 132 reflects the amount of the transfer deposit in the money balance, which represents the balance of electronic money owned by the service user and is pre-associated with the dedicated account (virtual account).

[0124] (Regarding Management Department 133) When the management unit 133 receives a request from a service user to create a dedicated account (virtual account), it arbitrarily selects a virtual account from among several unused virtual accounts that have been pre-loaned by a partner bank and assigns it as the dedicated account (virtual account) corresponding to the service user who made the request. The management unit then manages the account information used to identify the assigned dedicated account (virtual account) by associating it with the service user's unique identification information (for example, user ID).

[0125] Furthermore, the management department 133 may assign dedicated accounts (virtual accounts) for each purpose of use (such as transfer deposits other than salary or receipt of salary).

[0126] Furthermore, if the purpose of use is not for receiving salary, the management department 133 may assign a dedicated account (virtual account) with a predetermined expiration date.

[0127] Furthermore, the management unit 133 may manage the money balance associated with each dedicated account (virtual account) according to the purpose of use of each dedicated account (virtual account).

[0128] Furthermore, the management unit 133 manages the system by associating account numbers, which are used to identify multiple virtual accounts under predetermined names borrowed from partner financial institutions (banks), with user IDs, which are user identification information used to identify users of the electronic payment service, and storing them in the user information storage unit 122.

[0129] Furthermore, the management unit 133 stores and manages status information in the user information storage unit 122, which is associated with the user ID, which is user identification information, indicating whether or not the service user has completed the identity verification procedure.

[0130] Furthermore, when the management unit 133 receives a request from a service user to create a virtual account, it performs a status determination process to determine whether the service user who made the request has completed the identity verification procedure, based on the status information associated with the user ID, which is the user identification information corresponding to the service user who made the request. If the management unit 133 determines that the identity verification procedure has been completed, it assigns a virtual account to the service user.

[0131] Furthermore, if the management unit 133 determines that the identity verification procedure has been completed, it may assign a virtual account to the service user, provided that the identity verification information used in the identity verification procedure is within its validity period.

[0132] Alternatively, the management unit 133 may set the expiration date of the identity verification information as the expiration date of the virtual account assigned to the service user, and store and manage it in the user information storage unit 122 in association with the user ID, which is the user identification information.

[0133] Furthermore, if the management unit 133 receives a request from a service user to change their personal identification information, it may update the personal identification information before the change to the new personal identification information, associate it with the user ID which is the user identification information, and store and manage it in the user information storage unit 122.

[0134] (Regarding Section 134 of the Name Change section) The name change unit 134 executes a name change process to change the designated name of a virtual account assigned to a service user to the service user's user name. For example, the name change unit 134 sends a name change request, including the account number of the virtual account to be changed (for example, "111112") and the desired name change (for example, "Tokkyo Kenichi"), to the bank server 20 via the communication unit 110. Alternatively, the name change unit 134 may change the name of a virtual account by accessing a management file that manages virtual accounts lent by the bank to the settlement server 100 through a predetermined interface such as an API provided by the bank, and rewriting the account name information associated with the virtual account in the management file. Furthermore, when executing the name change process, the name change unit 134 may change the name of the virtual account to be changed to the user name of the service user confirmed in the identity verification procedure.

[0135] Furthermore, if the name change unit 134 determines that the user name to be used as the new name for the virtual account exceeds a predetermined maximum number of characters, it may perform the name change process using an adjusted user name that is less than or equal to the maximum number of characters.

[0136] Furthermore, when the management unit 133 receives a request to change identity verification information, the name change unit 134 may, if the name of the service user associated with the changed identity verification information has also changed, execute the name change process for the virtual account using the changed name. In other words, when the name change unit 134 receives a request to change identity verification information, it may also change the account name if the user's name has changed (for example, if their surname changes due to marriage).

[0137] (Regarding calculation unit 135) The calculation unit 135 calculates the amount that the service user can charge based on the difference between the current money balance associated with the service user's user account and the balance limit, which is the upper limit of the money balance that is set in advance and associated with the service user's user account.

[0138] Furthermore, the calculation unit 135 may calculate the chargeable amount at predetermined timings in accordance with the increase or decrease in the money balance associated with the service user. Alternatively, the calculation unit 135 may calculate the chargeable amount according to a predetermined cycle based on the size of the chargeable amount, the frequency of money balance top-ups, or the frequency of money balance usage. The cycle may be updated again at the time the chargeable amount is calculated, according to the size of the chargeable amount, the frequency of money balance top-ups, or the frequency of money balance usage.

[0139] Furthermore, the calculation unit 135 may calculate the chargeable amount if the service user to be processed has not completed the identity verification procedure.

[0140] (Regarding the transfer adjustment section 136) The transfer adjustment unit 136 notifies the partner bank of the chargeable amount calculated by the calculation unit 135 as the transfer limit for the account number used to identify the virtual account. The transfer adjustment unit 136 may also change the transfer limit by accessing a management file in which the bank manages the transfer limit for each virtual account through a predetermined interface provided in advance by the bank, and rewriting the transfer limit information associated with the relevant virtual account in the management file.

[0141] Furthermore, if the transfer adjustment unit 136 receives a transfer error from a bank due to a transfer deposit to a virtual account exceeding the transfer limit, it may notify the service user associated with the virtual account (or the account number used to identify it) corresponding to the transfer error of information regarding the transfer error.

[0142] (Regarding the dispensing unit 137) If the service user to be processed has completed the identity verification procedure, the disbursement unit 137 executes a refund process to pay out the amount equivalent to the amount exceeding the balance limit from the money balance linked to the user account of the service user to be processed.

[0143] Furthermore, when the disbursement unit 137 executes a refund process, if the service user to whom the refund is to be made has not registered a disbursement account, it may notify the service user to register a disbursement account through a dedicated application provided to the service user.

[0144] [3. Example of processing procedure] (3-1. Account allocation process) The following describes an example of the processing procedure in the payment server 100 according to the embodiment. Figure 11 is a flowchart showing an example of the processing procedure for account allocation performed by the payment server 100 according to the embodiment.

[0145] As shown in Figure 11, the management unit 133 receives a request to create a dedicated account for the transfer deposit service (step S101). The management unit 133 also determines whether or not the service user who made the request has completed the identity verification procedure (step S102).

[0146] If the management unit 133 determines that the service user who requested the creation has completed the identity verification procedure (step S102; Yes), it determines whether the identity verification information used in the identity verification procedure is still valid (step S103).

[0147] If the management department 133 determines that the identity verification information used in the identity verification procedure is within its validity period (Step S103; Yes), it receives the necessary information for account creation from the service user who requested the creation (Step S104).

[0148] Furthermore, the management unit 133 arbitrarily selects a virtual account from among the multiple virtual accounts stored in the virtual account information storage unit 121 that are not currently in use, and assigns it as a dedicated account (virtual account) corresponding to the service user who requested its creation (step S105).

[0149] Furthermore, the management unit 133 associates the account information used to identify the dedicated account (virtual account) assigned in step S105 with the identification information unique to the service user (for example, user ID) and registers it in the user information storage unit 122 (step S106).

[0150] Furthermore, the name change unit 134 executes a name change process to change the predetermined name of the virtual account assigned to the service user to the service user's name (step S107).

[0151] Furthermore, the management unit 133 notifies the service user who requested the creation of information regarding the created account (step S108), and then terminates the processing procedure shown in Figure 11.

[0152] Furthermore, in step S103 described above, if the management unit 133 determines that the identity verification information used in the identity verification procedure is not within its validity period (has expired) (step S103; No), it sends a request to update the identity verification information to the user terminal 10 of the service user who requested the creation (step S109), and terminates the processing procedure shown in Figure 11. Note that if the identity verification information is updated by the service user who requested the creation, the management unit 133 may execute the processing procedures from step S104 onwards described above.

[0153] Furthermore, in step S102 described above, if the management unit 133 determines that the identity verification procedure by the service user who requested the creation has not been completed (i.e., the identity verification procedure has not been performed) (step S102; No), it sends a request to execute the identity verification procedure to the user terminal 10 of the service user who requested the creation (step S110), and terminates the processing procedure shown in Figure 11. Note that if the identity verification procedure has been completed by the service user who requested the creation, the management unit 133 may execute the processing procedures from step S103 onwards described above.

[0154] (3-2. Processing of bank transfer deposits) Figure 12 is a flowchart showing an example of the processing procedure for reflecting a bank transfer deposit, which is performed by the payment server 100 according to the embodiment.

[0155] As shown in Figure 12, the detection unit 131 detects a bank transfer deposit to the bank account linked to the virtual account (dedicated account) (step S201).

[0156] The reflection unit 132 confirms the transfer details detected in step S201 (step S202). Then, the reflection unit 132 executes processing according to the transfer details confirmed in step S202 (step S203), and the processing procedure shown in Figure 12 is completed.

[0157] (3-3. Adjustment of transfer amount) Figure 13 is a flowchart showing an example of the processing procedure for the transfer amount adjustment process executed by the settlement server 100 according to this embodiment.

[0158] As shown in Figure 13, the calculation unit 135 determines whether or not to perform an adjustment to the transfer limit (step S301). For example, the calculation unit 135 determines whether or not a timing predetermined by the administrator of the settlement server 100 has been reached as the timing for adjusting the transfer limit.

[0159] If the calculation unit 135 determines that it will perform an adjustment to the transfer conditions (step S301; Yes), it identifies the service users to be processed (hereinafter referred to as "target users") (step S302).

[0160] Furthermore, the calculation unit 135 refers to the account information and obtains the current money balance associated with the user account of the target user (step S303).

[0161] Furthermore, the calculation unit 135 refers to the account information to obtain the upper limit of the target user's money balance (upper balance amount) (step S304).

[0162] Furthermore, the calculation unit 135 calculates the amount that the target user can charge based on the difference between the target user's current money balance and the upper limit of their money balance (step S305). The calculation unit 135 then transfers the calculated amount that can be charged to the transfer adjustment unit 136.

[0163] Furthermore, the transfer adjustment unit 136 notifies the partner bank of the chargeable amount calculated by the calculation unit 135 as the transfer limit for the virtual account assigned to the target user (step S306).

[0164] The calculation unit 135 determines whether processing has been completed for all target users (step S307). If the calculation unit 135 determines that processing has been completed for all target users (step S307; Yes), it terminates the processing procedure shown in Figure 13. Conversely, if the calculation unit 135 determines that processing has not been completed for all target users (step S307; No), it returns to the processing procedure in step S303 described above and performs processing for other target users for whom the adjustment of the transfer limit has not been completed.

[0165] [4. Variations] (4-1. Regarding the recycling of virtual accounts) In the above-described embodiment, the settlement server 100 may release dedicated accounts (virtual accounts) that are in use and have not been used for the transfer deposit service for a certain period of time, thereby leaving them unused. Alternatively, the settlement server 100 may release dedicated accounts (virtual accounts) that are in use and are used only for transfer deposit services other than salary payments.

[0166] (4-2. Regarding the configuration of Information Processing System 1) In the above-described embodiment, an example was explained in which the settlement server 100 included in the information processing system 1 performs processing related to electronic payment services and processing related to bank transfer services. However, the configuration of the information processing system 1 according to the embodiment is not limited to such an example, and the server device that performs processing related to electronic payment services and the server device that performs processing related to bank transfer services may be physically separate servers, or each server device may belong to a different system. In this case, each server device is connected in a way that allows them to communicate with each other and exchange the information necessary for their respective processing.

[0167] Furthermore, among the processes described in the embodiments described above, 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 known methods. In addition, the processing procedures, specific names, and various data and parameters shown in the above document and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in each figure is not limited to the information shown.

[0168] Furthermore, the components of each illustrated device are functionally conceptual and do not necessarily need to be physically configured as shown. In other words, the specific forms of distribution and integration of each device are not limited to those shown, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads and usage conditions.

[0169] Furthermore, the embodiments described above can be combined as appropriate, provided that the processing content is not contradictory.

[0170] [5. Effects] As described above, the payment server 100 according to this embodiment has a management unit 133 and a name change unit 134. The management unit 133 manages by associating account numbers for identifying multiple virtual accounts with predetermined names borrowed from partner banks (an example of a "financial institution") with user identification information for identifying service users of the electronic payment service and storing them in the user information storage unit 122. The name change unit 134 executes a name change process to change the predetermined name of a virtual account to the user name of a service user.

[0171] Furthermore, the management unit 133 stores and manages status information in the user information storage unit 122, which is associated with the user ID (an example of "user identification information") and indicates whether or not the service user has completed the identity verification procedure. When the management unit 133 receives a request from a service user to create a virtual account, it executes a status determination process to determine whether or not the service user who made the request has completed the identity verification procedure, based on the status information associated with the user ID corresponding to the service user who made the request. If the management unit 133 determines that the identity verification procedure has been completed, it assigns a virtual account to the service user.

[0172] Furthermore, if the management unit 133 determines that the identity verification procedure has been completed, it will assign a virtual account to the service user, provided that the identity verification information used in the identity verification procedure is within its validity period.

[0173] Furthermore, the name change unit 134 changes the designated name of the virtual account to the name of the service user confirmed through the identity verification procedure.

[0174] Alternatively, the management unit 133 may set the expiration date of the identity verification information as the expiration date of the virtual account assigned to the service user, and store and manage it in the user information storage unit 122 in association with the user identification information.

[0175] Furthermore, if the management unit 133 receives a request from a service user to change their personal identification information, it may update the personal identification information before the change to the new personal identification information, associate it with the user ID, and store and manage it in the user information storage unit 122.

[0176] Furthermore, when the name change unit 134 receives a request to change the identity verification information, if the name of the service user associated with the changed identity verification information has changed, it will perform the name change of the virtual account using the changed name.

[0177] Furthermore, if the name change unit 134 exceeds the pre-set maximum number of characters for the user's name, it may perform the name change process using an adjusted user's name that is less than or equal to the maximum number of characters.

[0178] For these reasons, the payment server 100 according to this embodiment can support the smooth operation of a transfer deposit service scheme provided through the same platform as the electronic payment service, through the processing performed by each of the above-described parts, or any combination of the parts, thereby expanding the use of the electronic payment service.

[0179] [6. Hardware Configuration] Furthermore, the payment server 100 according to the above embodiment is implemented by a computer 1000 having a configuration such as that shown in Figure 14. Figure 14 is a hardware configuration diagram showing an example of a computer that implements the functions of the payment server according to the embodiment.

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

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

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

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

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

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

[0186] For example, when computer 1000 functions as a payment server 100, which is an example of an information processing device according to the embodiment, the arithmetic unit 1030 of computer 1000 realizes the same functions as the control unit 130 by executing a program (for example, an information processing program) loaded on the primary storage device 1040. That is, the arithmetic unit 1030 realizes the processing by the payment server 100 according to the embodiment in cooperation with the program (for example, an information processing program) loaded on the primary storage device 1040.

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

[0188] Furthermore, the aforementioned payment server 100 can be flexibly configured to implement certain functions by calling external platforms via APIs (Application Programming Interfaces) or network computing.

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

[0190] 1. Information Processing System 10. User terminals 20 Bank Servers 100 Payment Servers 110 Communications Department 120 Storage section 121 Virtual Account Information Storage Unit 122 User information storage unit 123 Account Information Storage Unit 130 Control Unit 131 Detection unit 132 Reflection section 133 Management Department 134 Name Change Section 135 Calculation Section 136 Transfer Adjustment Department 137 Dispensing Section

Claims

1. A management unit manages the following in association: account numbers assigned to service users from among multiple virtual account numbers borrowed from partner financial institutions, user identification information that identifies the service user, and personal verification information of the service user. When a change in the identity verification information is received from the service user, the name update unit updates the name information corresponding to the virtual account identified by the account number based on the changed identity verification information, An information processing device characterized by having the following features.

2. The aforementioned name renewal section is, The name information is updated using the name from the aforementioned identity verification information. The information processing apparatus according to feature 1.

3. The aforementioned name renewal section is, If the name on the updated identity verification information differs from the name on the previous identity verification information, update the aforementioned name information. The information processing apparatus according to feature 1.

4. The aforementioned name renewal section is, A request to update the aforementioned name information will be sent to the partner financial institution. The information processing apparatus according to feature 1.

5. The aforementioned name renewal section is, The name information associated with the virtual account is updated through an interface provided by the partner financial institution. The information processing apparatus according to feature 1.

6. The aforementioned management department, When a change in the aforementioned identity verification information is accepted, the system updates the previous identity verification information to the new identity verification information and manages it in association with the aforementioned user identification information. The information processing apparatus according to feature 1.

7. The aforementioned name renewal section is, After updating the aforementioned identity verification information, update the name information corresponding to the virtual account. The information processing apparatus according to feature 1.

8. The aforementioned virtual account is This is an account borrowed by a business providing a bank transfer service from a partner financial institution. The information processing apparatus according to feature 1.

9. The aforementioned account number is, This is an account number assigned to the service user so that it can be designated as the recipient of transfers to a third party other than the business providing the transfer deposit service. The information processing apparatus according to feature 1.

10. An information processing method performed by an information processing device, A management process that manages by associating account numbers assigned to service users from among multiple virtual account numbers borrowed from partner financial institutions, user identification information that identifies the service user, and the service user's identity verification information. When a change in the identity verification information is received from the service user, the name update process updates the name information corresponding to the virtual account identified by the account number based on the changed identity verification information. An information processing method characterized by including

11. A management procedure for managing the association between account numbers assigned to service users from among multiple virtual account numbers borrowed from partner financial institutions, user identification information that identifies the service user, and the service user's identity verification information. A name update procedure that, when a change in the identity verification information is received from the service user, updates the name information corresponding to the virtual account identified by the account number based on the changed identity verification information, An information processing program characterized by causing a computer to execute it.

Images