JP7728652B2 - Data processing device and data processing method - Google Patents

Description

The present invention relates to a data processing device and data processing method that is connected to bank and payment service systems, and allows the results of identity verification processing to be shared with the connected system, thereby easily and safely completing identity verification processing in the connected system, centrally managing accounts and account information in the connected system, and enabling value exchange between systems.

In recent years, cashless transactions have become more common, and many payment services are being used as alternative means of payment to cash. Widely known examples of such payment services include electronic money and code payments (including barcode payments, two-dimensional code payments, and similar).

In December 2018, the government's National Strategic Special Zone Advisory Council announced a policy to lift the ban on paying salaries using electronic money, which is not permitted under current law. While there have been proposals for paying salaries using electronic money (Patent Documents 1 and 2) in the past, they have not been realized. In response to this policy, a scheme is being considered in which payer companies can designate individual electronic money accounts to make salary payments, allowing payees to receive their salaries directly as electronic money.

Japanese Patent Application Laid-Open No. 2003-157344 Patent No. 5141158 Japanese Patent Application Laid-Open No. 2003-187075

When a user applies for a new account with a bank or payment service, they are required to go through identity verification procedures for each bank or payment service. Since the results of identity verification procedures are limited to one account, even if a user has already gone through identity verification procedures with another bank or payment service, they must go through identity verification procedures again when applying to open a new bank account or use a new payment service. The information required for identity verification procedures is the same for all banks and payment services, so users must go through the same procedures multiple times, creating a burden for these cumbersome procedures. However, insufficient identity verification procedures increase the risk of crime.

Regarding identity verification procedures, there is a need for a scheme in which users can provide their identity verification information to a trusted institution and then open or register an account through simple and secure authentication via that institution.

In the world of bank accounts and payment services, balances and statements are managed on an account-by-account basis for each user, and when transferring funds, money is transferred from one account to another. When a user has multiple bank accounts and payment service accounts, it is important for the user to manage this information centrally and transfer funds to other users more efficiently.

Patent Document 3 discloses a function for aggregating and displaying information on multiple accounts, but this is not a mechanism that can handle the diverse payment services available today, nor does it allow for efficient transfer of funds to other users.

When transferring funds between individuals, the recipient's account number and account information are obtained and the funds are transferred based on that information. However, if the account number or account information is incorrect, the funds cannot be transferred, resulting in unnecessary hassle and fees. Furthermore, individuals often lack knowledge of the fees associated with remittances and do not know what payment services the recipient uses, making it difficult to know whether the selected funds transfer route is optimal.

The present invention has been made to solve these problems, and aims to provide a data processing device and data processing method that is connected to bank and payment service systems, and that allows the results of the identity verification process held by the device to be linked to the connected system, thereby easily and safely completing the identity verification process in the connected system, centrally managing accounts and account information in the connected system, and enabling value exchange between systems.

One aspect of the present invention is a data processing device that communicates information with a first system, and is characterized by comprising: means for receiving an authentication request from the first system, the authentication request including a first user identifier that identifies the same user in the data processing device and the first system and first authentication information associated with the first user identifier; means for acquiring identity verification information based on the first user identifier and the first authentication information and transmitting the identity verification information to the first system, the identity verification information indicating that identity verification processing has been successfully completed by the data processing device; means for receiving a registration information acquisition request from the first system in response to the identity verification information and transmitting user information associated with the first user identifier to the first system; and means for receiving user information associated with the first user identifier from the first system in response to the user information.

According to the present invention, the data processing device stores the results of identity verification and official personal authentication, and these results can be linked to the destination system. Therefore, when a user opens a desired bank account or applies for a payment service, the destination system can perform identity verification processing in a simple and secure manner using the results of previous identity verification procedures, without the user having to submit new identity verification documents, thereby improving user convenience.

According to the present invention, by storing authentication information and account information for various banks and payment services linked to the data processing device on the data processing device side, it becomes possible to centrally manage accounts and account balances associated with users in connected systems. Because the data processing device of the present invention acts as a hub between multiple bank systems and payment service provider systems, it becomes possible to realize value exchange (fund transfer) between these systems without the user having to be aware of the fund transfer route selection.

A more detailed understanding of the embodiments disclosed herein can be had from the following description, taken in conjunction with the accompanying drawings, in which:
1 is a configuration diagram of an entire system according to an embodiment of the present invention. 1 is a system configuration diagram of a data processing device 10 according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a data structure of an account management DB 106 according to the embodiment of the present invention. FIG. 2 is a diagram showing an example of the data structure of a deposit/withdrawal management DB 107 according to an embodiment of the present invention. FIG. 4 is a flowchart illustrating a process related to account management according to the present invention. An example of data for the account 106-1 and the virtual account number 106-2 is shown below. FIG. 1 is a flow chart illustrating a transfer receiving process according to the present invention. An example of data contents of the deposit/withdrawal management DB 107 is shown below. FIG. 10 is a flow diagram illustrating a charging process for a payment service. 10 is a flow diagram illustrating an example of processing performed in cooperation between the data processing device 10 and the payment service provider system 14. FIG. FIG. 10 is a flow diagram illustrating a process for acquiring account and account usage information. FIG. 2 is a flow diagram illustrating a fund transfer process executed by the data processing device 10 according to the present invention. FIG. 13 is a diagram showing an example of a display screen 1300 according to the present invention.

In this specification, the term "bank" is used to mean a financial institution (e.g., bank, credit union, credit association, labor bank, agricultural cooperative, Japan Post Bank, etc.) that has a four-digit financial institution code assigned by the Japanese Bankers Association (hereinafter referred to as "Zenginkyo").

In this specification, "electronic money" means a system in which monetary value is recorded as digital data on an IC card or a server connected to the Internet, and monetary value is exchanged electronically (Kojien, 7th edition). The concept of electronic money includes rechargeable electronic payment methods, but is not limited to any specific service.

In this specification, "payment services" are explained as including electronic money and code payment services (including barcode payment, two-dimensional code payment, and similar services). The electronic value information (information equivalent to monetary value) handled by the data processing device 10 and payment service provider system 14 according to the present invention is also referred to as digital money, value, etc.

The following schemes are described herein:
・A data processing device scheme that enables payees to receive their pay in electronic money without requiring payer companies to change their previous payroll procedures and payroll payment systems. ・A data processing device scheme that enables payees to transfer money to a desired bank account using deposit data such as the salary they have received, and charge a payment service. ・A data processing device scheme that allows a connected system to perform identity verification processing in a simple and secure manner using the results of previous identity verification procedures, without the user having to submit new identity verification documents when opening a desired bank account or applying to use a payment service. ・A data processing device scheme that centrally manages accounts and account balances in connected systems associated with users. ・A data processing device scheme that acts as a hub between multiple bank systems and payment service provider systems, and enables value exchange (fund transfer) between these systems without the user having to be aware of the selection of the fund transfer route.

(Overall structure)
1 is a configuration diagram of an entire system including a data processing device 10 according to an embodiment of the present invention, a bank system 11, a company system 12, a user terminal 13, and a payment service provider system 14. Although only one of each element is shown in FIG. 1, there may be multiple of these elements.

As shown in FIG. 1, the data processing device 10 is communicatively connected to the bank system 11, the user terminal 13, and the payment service provider system 14. The bank system 11 is communicatively connected to the data processing device 10, the enterprise system 12, and the payment service provider system 14. The enterprise system 12 may be communicatively connected to the bank system 11 and the user terminal 13. The payment service provider system 14 is communicatively connected to the data processing device 10, the bank system 11, and the user terminal 13.

When a new user applies to start using the data processing device 10, the data processing device 10 performs identity verification/authentication of the user via a public personal authentication mechanism using a My Number card, resident registration card, driver's license, etc., stores the identity verification/authentication results in the account management DB 106, and assigns a general-purpose ID to the user. The general-purpose ID can be used as a user ID for logging in to the data processing device 10, bank system 11, and payment service provider system 14. This application to start using the data processing device 10 may be made together with a request to generate a virtual account number, which will be described later.

In response to a virtual account number generation request from the user terminal 13, the data processing device 10 assigns a virtual account number associated with the banking system 11 to the user and transmits it to the user terminal 13. In this specification, a "virtual account number" corresponds to a financial institution's account identifier (i.e., financial institution code, branch number, deposit type, and account number). The branch number included in the virtual account number indicates the branch number of a virtual branch at the financial institution.

The data processing device 10 receives various requests and instructions from the user terminal 13, executes processing related to those requests and instructions, and sends the related requests and instructions to the corresponding systems.

The data processing device 10 receives transfer data (referred to herein as "first transfer data") for a virtual account number associated with the bank system 11 from the bank system 11, and updates the account management DB 106 and deposit/withdrawal management DB 107 based on the first transfer data. The first transfer data indicates the content of transfer information that will not be transferred to the user's deposit account (a real account opened at a financial institution).

The data processing device 10 communicates with the bank system 11 that has the bank account associated with the user and the payment service provider system 14 that has the account associated with the user to obtain the user's balance information and statement information. The data processing device 10 can collectively manage the obtained balance information and statement information, and can, for example, display this information on the user terminal 13 and use this information to determine the fund transfer route.

When a user opens a new account in the bank system 11 and when a user opens a new account in the payment service provider system 14, the data processing device 10 can link the results of the user's identity verification/authentication process and information about the user to the bank system 11 and the payment service provider system 14.

The banking system 11 has an accounting system. The accounting system has corporate and individual accounts, the payment service provider's own management account, and a pool account as described in this specification. The pool account is an account that stores (pools) all transfer amounts to virtual stores. The banking system 11 controls the transfer to the corresponding account and the deposit process to the pool account based on the received transfer data. The banking system 11 transmits the transfer data of the transfer deposited into the pool account to the data processing device 10 as first transfer data. In response to a real-time transfer instruction from the payment service provider system 14, the banking system 11 transfers the amount in the pool account to the payment service provider's own management account, and transmits the processing result to the payment service provider system 14.

The enterprise system 12 manages employee attendance and calculates payroll, generates transfer data for employees, and transmits it to the bank system 11. The enterprise system 12 may also be configured to receive the user's transfer destination information (virtual account number) from the user terminal 13.

The user terminal 13 is any type of device capable of operating in a wired or wireless environment. The user terminal 13 sends a withdrawal request for a generic ID or virtual account number to the data processing device 10 and receives a generic ID or a virtual account number associated with the banking system 11 from the data processing device 10. The user terminal 13 logs in to the data processing device 10 and sends various requests and instructions to the data processing device 10, such as a charge request or a remittance request.

The user terminal 13 sends an account registration request to the payment service provider system 14, and receives the created account after the payment service provider system 14 and the data processing device 10 complete the specified processing.

The payment service provider system 14 has a personal account associated with the user and a bank account associated with the bank system 11. The payment service provider system 14 receives requests from the data processing device 10 to charge digital money to the bank account and requests to charge digital money from the bank account to the user's personal account, sends real-time transfer instructions to the bank system 11 in response to the requests, charges the bank account and transfers money from the bank account to the user's personal account according to the results, and sends the processing results to the data processing device 10.

(System configuration)
Fig. 2 is a system configuration diagram of a data processing device 10 according to an embodiment of the present invention. As shown in Fig. 2, like a general computer, the data processing device 10 comprises a control unit 101, a main memory unit 102, an auxiliary memory unit 103, an interface (IF) unit 104, and an output unit 105, which are interconnected by a bus 120 or the like. The data processing device 10 also comprises an account management DB 106 and a deposit/withdrawal management DB 107 in the form of a file/database or the like.

The control unit 101, also known as the central processing unit (CPU), controls the various components of the data processing device 10 and performs data calculations. It also reads various programs stored in the auxiliary storage unit 103 into the main storage unit 102 and executes them. The main storage unit 102, also known as the main memory, stores various received data, computer-executable instructions, and data after calculations based on those instructions. The auxiliary storage unit 103 is a storage device such as a hard disk drive (HDD) that stores data and programs for the long term.

The embodiment in Figure 2 describes an embodiment in which the control unit 101, main memory unit 102, and auxiliary memory unit 103 are provided inside the same computer, but in other embodiments, the data processing device 10 can be configured to use multiple control units 101, main memory units 102, and auxiliary memory units 103 to achieve parallel distributed processing using multiple computers. Also, in other embodiments, multiple servers for the data processing device 10 can be installed, and multiple servers can share a single auxiliary memory unit 103.

The IF unit 104 acts as an interface when sending and receiving data with other systems and devices, and also provides an interface for accepting various commands and input data (various masters, tables, etc.) from the system operator. The output unit 105 provides a display screen for displaying processed data and printing means for printing that data.

The account management DB 106 includes an account 106-1, a virtual account number 106-2, a bank account 106-3, and a payment service account 106-4 for storing user accounts and account-related information. Figure 3 is a diagram showing an example of the data structure of the account management DB 106 according to an embodiment of the present invention.

Account 106-1 stores user information, including identity verification information, as well as account and account balance information associated with the user. Account 106-1 may include, but is not limited to, a generic ID 301, a PW 302, an authentication status 303, an authentication medium 304, an authentication date and time 305, user information 306, a face balance 307, an acquisition date and time 308, and a system balance 309. Account 106-1 may also include other data items.

General ID 301 is a user identifier assigned to the user by the data processing device 10. PW 302 indicates the user's password. General ID 301 and PW 302 can be used as a user ID and password to identify the same user in the data processing device 10, bank system 11, and payment service provider system 14.

Authentication status 303, authentication medium 304, and authentication date and time 305 are data items related to the implementation status of official personal authentication. Authentication status 303 indicates the status of whether official personal authentication using a My Number card, resident registration card, driver's license, etc. has been completed. Authentication medium 304 indicates the medium (e.g., My Number card) used for official personal authentication. Authentication date and time 305 indicates the date and time when official personal authentication was performed (YYYY/MM/DD HH:MM:SS). User information 306 indicates user-related information such as the user's name, kana name, gender, date of birth, address, and contact information (e.g., email address).

The nominal balance 307 indicates the total amount of the system balance 309, bank account, and payment service provider account balances associated with the user. The acquisition date and time 308 indicates the oldest date and time when the bank account balance information and payment service account balance information were acquired from the bank system 11 and the payment service provider system 14. The system balance 309 indicates the balance managed on a per-user basis in the data processing device 10. The balance of the system balance 309 may be referred to as "value" in this specification.

The virtual account number 106-2 stores information about the virtual account number associated with the bank system 11. The virtual account number 106-2 may include, but is not limited to, the general ID 301, financial institution code 311, branch number 312, deposit type 313, and account number 314, and may also include other data items.

Financial institution code 311 is an identifier for the financial institution and corresponds to the unified financial institution code assigned to each financial institution by the Japanese Bankers Association. Branch number 312 is an identifier that indicates a virtual branch that is predetermined for that financial institution. In other words, branch number 312 indicates a number other than the number assigned to the financial institution's actual branch, i.e., a number assigned to the virtual branch. Deposit type 313 indicates the account deposit type (for example, "savings," "current," etc.). Account number 314 is the virtual branch account number assigned to the user.

Bank account 106-3 stores information about the bank account associated with the user. Bank account 106-3 may include, but is not limited to, a general ID 301, a financial institution code 321, a branch number 322, a deposit type 323, an account number 324, a CD PIN 325, a balance 326, and a balance update date and time 327. The bank account 106-3 may also include other data items.

Financial institution code 321 is an identifier for the financial institution and corresponds to the unified financial institution code assigned to each financial institution by the Japanese Bankers Association. Branch number 322 is an identifier that indicates the actual branch of the financial institution. Deposit type 323 indicates the deposit type of the account (for example, "savings" or "current"). Account number 324 is the account number assigned to the user. CD PIN 325 is the PIN number used when using an ATM or CD (cash dispenser). Balance 326 indicates the account balance. Balance update date/time 327 indicates the date and time the account balance was updated.

The payment service account 106-4 stores information about the payment service for which the user has registered an account. The payment service account 106-4 may include a general ID 301, a service name 331, a payment service provider code 332, a user ID 333, a password 334, a balance 335, and a balance update date and time 336, but is not limited to these data items and may also include other data items.

Service name 331 indicates the name of the payment service (for example, XXPay, etc.). Payment service provider code 332 is an identifier for the provider providing the payment service and is associated with the payment service provider system 14. User ID 333 is a user identifier assigned by the payment service provider system 14. PW 334 is the user's password assigned by the payment service provider system 14. Balance 335 indicates the user's balance information for the payment service. Balance update date and time 336 indicates the date and time when the user's balance information for the payment service was updated.

Returning to Figure 2, the deposit and withdrawal management DB 107 stores deposit and withdrawal details information for value (information equivalent to monetary value) associated with the user's system account (general ID).

Figure 4 is a diagram showing an example of the data structure of the deposit/withdrawal management DB 107 according to an embodiment of the present invention. The deposit/withdrawal management DB 107 may include a general ID 301, transaction date 401, deposit amount 402, withdrawal amount 403, balance 404, and summary 405, but is not limited to these data items and may also include other data items.

Transaction date 401 indicates the date and time when deposit/withdrawal data related to value was generated. Deposit amount 402 indicates the deposit amount when deposit data was generated. Withdrawal amount 403 indicates the withdrawal amount when withdrawal data was generated. Balance 404 indicates the balance information after deposit/withdrawal data was generated. The latest value of balance 404 is equal to the value of system balance 309. Summary 405 indicates summary information of the deposit/withdrawal data. The summary information may indicate the type of deposit (e.g., "salary"), the financial institution code 311 of the bank associated with the deposit process, and the financial institution code and payment service provider code of the bank to which the funds are being transferred.

(Process flow: Account management)
Figure 5 is a flow diagram illustrating the process for account management according to the present invention. The process flow in Figure 5 explains the process for issuing a general-purpose ID to a new user and the process for issuing a virtual account number to a user who wishes to receive a transfer via a financial institution designated by the transfer requester. If a user who has already been assigned a general-purpose ID requests the issuance of a new virtual account number, the process for issuing the general-purpose ID is omitted.

At S501, the data processing device 10 receives a new usage application from the user terminal 13. The new usage application includes user information (e.g., name, kana name, gender, date of birth, address, contact information (e.g., email address), etc.), login password (PW), and information for official personal authentication.

At S502, in response to receiving the new user application, the data processing device 10 performs electronic identity verification processing using public personal authentication information (e.g., My Number card, driver's license, etc.) in cooperation with the public personal authentication service provided by the Ministry of Internal Affairs and Communications.

In S503, after the electronic identity verification process is successfully completed, the data processing device 10 issues a general-purpose ID and sends it to the user terminal 13, and stores the general-purpose ID, PW, data related to public personal authentication, and user information in account 106-1. Figure 6(a) shows an example of data in account 106-1 that stores information about a new user whose identity verification process has been successfully completed.

At S504, the data processing device 10 receives a virtual account number generation request from the user terminal 13. The virtual account number generation request includes a general ID, password, and financial institution code.

At S505, in response to the user's request to generate a virtual account number, the data processing device 10 generates a virtual account number associated with the financial institution code and sends it to the user terminal 13. The virtual account number includes the financial institution code, branch number, deposit type, and account number. Figure 6(b) is an example of data for virtual account number 106-2. The user (general ID) in the example of Figure 6(b) has six virtual account numbers. Branch number 312 is the branch number of a virtual branch at the financial institution. Account number 314 is the account number of the virtual branch of the financial institution assigned to the user, and the data processing device 10 assigns account number 314 to the user so that it does not overlap. The data processing device 10 may be configured to have a table that manages information about account number 314 for each virtual branch of the financial institution. In one embodiment of the present invention, the data processing device 10 may be configured to request the bank system 11 to generate a virtual account number.

Once the issuance of the general-purpose ID and virtual account number is complete, the user can use the general-purpose ID as a user ID to access the various functions provided by the data processing device 10, and can open an account at a bank and register an account for payment services. In response to a request from the user terminal 13, the data processing device 10 can update and delete the account 106-1 and virtual account number 106-2.

Users can provide the virtual account number to payee companies as information about their payroll account. Because the virtual account number conforms to the account system established by the Japan Bankers Association, the company system 12 can register the virtual account number as a payroll account number without any problems, and the payroll company does not need to modify the company system 12. The virtual account number can be registered as a payroll account number by an operator of the company system 12, or from a user terminal 13 connected to the company system 12.

(Processing flow: Transfer receipt processing)
Figure 7 is a flow diagram illustrating the transfer receipt process according to the present invention. The process flow in Figure 7 uses an example of a salary transfer within a bank, but the technical concept of the present invention can also be applied to transfers other than salary transfers to a user, as well as transfers from other banks. In other words, a user can use the scheme described in this specification simply by specifying the deposit account number as the virtual account number. This process flow will be described assuming that the user's virtual account number is registered in the corporate system 12 as the account number for salary transfers.

At S701, the corporate system 12 calculates the payroll of employees, including the user, and sends transfer data to the corresponding bank system 11 based on the financial institution code of the transfer destination account. The bank system 11 receives the transfer data. The transfer data is in the same format as before, following the JBA format. For transfer data of users who wish to ultimately receive their salary using any payment service, the virtual account number described above is used as the transfer account information.

At S702, the bank system 11 determines whether the branch number included in the received transfer data indicates a virtual branch. The bank system 11 may have a table that stores the branch numbers of virtual branches. If the read branch number indicates a virtual branch, processing proceeds to S703; if not, processing proceeds to S704.

At S703, the bank system 11 performs a deposit process from the transfer source company account to the pool account based on the transfer data. The pool account is an account that stores (pools) all transfer amounts to the virtual store. In other embodiments of the present invention, it is also possible to configure the pool account to be managed separately by account number, i.e., by virtual account number.

At S704, the bank system 11 processes the transfer from the transfer source company account to the user's real account based on the transfer data, and transmits the transfer processing results to the company system 12. If the transfer is not possible for a specified reason, subsequent processing such as a reversal process or a transfer deposit by reassignment is carried out in accordance with normal procedures.

At S705, the bank system 11 generates first transfer data based on the transfer data for which a deposit has been processed into the pool account (i.e., the deposit detail data for the pool account) and transmits the first transfer data to the data processing device 10. The data processing device 10 receives the first transfer data from the bank system 11.

At S706, the data processing device 10 uses the financial institution code, branch number, deposit type, and account number (i.e., virtual account number) included in the received first transfer data as search keys to identify the virtual account number data corresponding to virtual account number 106-2, and obtains the general ID 301 associated with the virtual account number. The data processing device 10 generates deposit data based on the first transfer data and adds it to the deposit/withdrawal management DB 107. Figure 8 shows an example of data in the deposit/withdrawal management DB 107. This example shows that a salary of 300,000 yen has been deposited into a general ID whose previous balance was zero, and the summary 405 shows the financial institution code of the bank holding the pool account that received the deposit and that the deposit was a salary transfer ("0138 KYUYO"). If the virtual account number data cannot be identified, the data processing device 10 notifies the bank system 11 and requests that follow-up processing, such as a reversal process or a transfer deposit by allocation, be performed.

The value of the latest balance 404 shown in Figure 8 is equal to the value of the system balance 309. The system balance 309 is similar to electronic money, but rather than being a means of payment, it can function as a measure of value for converting the value held by an individual user into any digital money. Digital money is premised on funds being preserved in a pool account by the banking system 11, and an amount equal to the system balance 309 managed by the data processing device 10 can be transferred to a bank account in one or more connected banking systems 11, and value can be transferred to a personal account of a payment service provider.

In one embodiment of the present invention, in response to a request from the user terminal 13, the data processing device 10 can transmit data from the deposit/withdrawal management DB 107 associated with the user's system account (i.e., general ID) to the user terminal 13, thereby enabling the user to inquire about details of amounts transferred to the user and their balance.

In one embodiment of the present invention, a portion of a transfer amount, such as a salary, can be added to the system balance 309, and the remainder can be deposited into the user's savings account, etc. In such a case, the data processing device 10 receives from the user terminal 13 an instruction specifying the amount to deposit into the value, and transmits the deposit amount to the banking system 11. The banking system 11 can perform processing to deposit an amount equivalent to the deposit amount, out of the transfer amount to the user's virtual account number, into a pool account, and deposit the remaining amount into the user's real account. As described with reference to Figure 7, the amount deposited into the pool account is transmitted to the data processing device 10 as first transfer data and added to the system balance 309. Information on the user's real account is transmitted from the user terminal 13 to the data processing device 10, and then transmitted from the data processing device 10 to the banking system 11.

(Processing flow: Payment service charge processing)
9 is a flow diagram illustrating the recharge process of the payment service. Note that the terms "recharge" and "transfer" can be used interchangeably.

At S901, in response to access from the user terminal 13, the data processing device 10 sends one or more payment service providers associated with the user that are candidates for the charge destination to the user terminal 13. The user inputs the payment service provider to be charged, the personal account to be charged (personal account of the payment service provider), and the charge amount while referring to the balance information of their own system account (general ID) on the screen of the user terminal 13. The user terminal 13 sends a charge request to the data processing device 10 that includes the payment service provider to be charged, the personal account to be charged, and the charge amount. The data processing device 10 receives the charge request from the user terminal 13. The amount that can be specified as the charge amount is equal to or less than the amount of the system balance 309 associated with the system account (general ID) of the sender.

At S902, the data processing device 10 identifies the bank account of the payment service provider to be charged that is included in the received charge request, and logs in to the corresponding payment service provider system 14 using the ID and PW of the identified bank account. The bank account of the payment service provider to be charged may be determined based on the contents of the summary 405 (e.g., information such as which bank the deposit was made from). The data processing device 10 transmits to the payment service provider system 14 a first charge instruction to charge the bank account with the charge amount included in the charge request, and a second charge instruction to transfer the charge amount from the bank account to the user's personal account. The first charge instruction and the second charge instruction may be transmitted together, and both may be collectively referred to as a "charge instruction." The data processing device 10 may be configured to have information on the bank account and PW of the payment service provider to be charged.

At S903, in response to the charge instruction, the payment service provider system 14 sends a real-time transfer request for the amount included in the charge instruction to the bank system 11 associated with the bank account. The bank account is an account of each bank at the payment service provider, and the bank system 11 to which the real-time transfer request is to be sent is identified by the logged-in bank account.

In response to the real-time transfer request, the bank system 11 deducts the relevant amount from the pool account, transfers the amount to the account held by the payment service provider in the bank system 11, and transmits the processing result (normal or abnormal) to the payment service provider system 14.

At S904, if the processing result received from bank system 11 indicates normal, payment service provider system 14 adds the corresponding amount to the balance of the bank account. This processing results in a transfer of money from the pool account of bank system 11 to the bank account of payment service provider system 14. Next, in accordance with the charge instruction, payment service provider system 14 adds the corresponding amount to the user's personal account and subtracts the corresponding amount from the balance of the bank account. This processing results in a transfer of money from the bank account in payment service provider system 14 to the user's personal account.

At S905, the payment service provider system 14 transmits the processing result of the charge instruction to the data processing device 10, and the data processing device 10 receives the processing result of the charge instruction. If the processing result of the charge instruction indicates that the processing has been completed successfully, the data processing device 10 deducts the system balance 309 of the system account (general ID) of the user's remitter and adds the withdrawal data to the deposit/withdrawal management DB 107.

At S906, the data processing device 10 transmits the processing results for the charge request to the user terminal 13.

In the above, the data processing device 10 was configured to charge a specified payment service in response to a request from the user terminal 13, but in other embodiments of the present invention, it may be configured to automatically perform the charge process based on predetermined setting conditions.

In one embodiment, the data processing device 10 may be configured to execute the above-mentioned charge process at a specified date and time by receiving information on the specified charge date and time from the user terminal 13. In another embodiment, the data processing device 10 may be configured to execute the charge process when triggered by a transfer of salary or the like. In either case, by having the user terminal 13 specify the specified date and time or trigger in advance along with the above-mentioned charge request data, the data processing device 10 can automatically execute the charge process without having to receive a charge request from the user each time.

In other embodiments of the present invention, a user can also transfer money to another person's personal account. In such cases, the charge request described in S901 can be modified to include the payment service provider used by the other person and the other person's personal account to be charged. In other words, whether to charge one's own payment service or transfer money to another person's payment service can be controlled depending on whether the personal account is the user's own or someone else's personal account.

In other embodiments of the present invention, the payment service provider to which the charge is made may be a local currency or any point service. In such cases, the exchange rate between the system account balance and the local currency or points may be determined arbitrarily by a local government, financial institution, etc.

(Process flow: New registration with payment service provider, information sharing)
When a user opens a bank account or registers an account with a payment service, identity verification is required. Figure 10 is a flow diagram illustrating an example of processing performed by data processing device 10 and payment service provider system 14 in cooperation with each other in response to a user's application to register an account with any payment service. In another embodiment of the present invention, the processing shown in Figure 10 may be performed by data processing device 10 and bank system 11 in cooperation with each other. This processing flow allows a user whose identity verification processing has been completed in data processing device 10 to open a bank account or register an account with a payment service without having to submit additional identity verification documents.

At S1001, the user terminal 13 sends an account registration application to the payment service provider system 14 of a given payment service. The account registration application includes at least a general ID 301 and a password 302 associated with the user. The data processing device 10 receives the account registration application from the user terminal 13.

At S1002, the payment service provider system 14 sends an authentication request including the general ID 301 and PW 302 to the data processing device 10. The data processing device 10 queries the account 106-1 based on the received general ID 301 and PW 302, and obtains information on the authentication status 303, authentication medium 304, and authentication date and time 305 associated with the general ID 301. If the information on the authentication date and time 305 is within a predetermined period (e.g., within x years), the data processing device 10 sends information on the authentication status 303, authentication medium 304, and authentication date and time 305 to the payment service provider system 14.

On the other hand, if the information in the authentication date and time 305 is not within the specified period, the data processing device 10 sends a message to the payment service provider system 14 indicating that new identity verification is required, and the payment service provider system 14 sends this message to the user terminal 13 that applied for account registration in S1001, and this processing flow ends.

In S1003, in response to receiving the authentication status 303, authentication medium 304, and authentication date and time 305 information from the data processing device 10, the payment service provider system 14 determines that the identity verification process for the user who applied for account registration in S1001 has been completed. After making this determination, the payment service provider system 14 sends a registration information acquisition request to the data processing device 10. The registration information acquisition request includes the general ID 301. The data processing device 10 acquires the user information 306 associated with the received general ID 301 from the account 106-1 and sends it to the payment service provider system 14.

At S1004, in response to receiving the user information, the payment service provider system 14 generates a user ID 333 and PW 334 for the payment service for the user, and stores the general ID 301, the generated user ID 333, PW 334, and the received user information in the storage of the payment service provider system 14. The payment service provider system 14 transmits the user ID 333 and PW 334 to the user terminal 13 that applied for account registration at S1001.

At S1005, the payment service provider system 14 transmits user information (e.g., general ID 301, service name 331 (e.g., XX Pay), payment provider code 332, user ID 333, PW 334) to the data processing device 10. The data processing device 10 stores the user information in the payment service account 106-4. This process enables the linking of user information and personal identification information between the data processing device 10 and the payment service provider system 14. Note that in another embodiment of the present invention, when the data processing device 10 and the bank system 11 share information, the information stored in the bank account 106-3 is exchanged as user information.

In this way, if identity verification is required when opening an account in the bank system 11 connected to the data processing device 10 or when registering an account in the payment service provider system 14, the bank system 11 and the payment service provider system 14 can use the general-purpose ID 301 and PW 302 to obtain authenticated information from the data processing device 10 and use this as a substitute for identity verification.

The generic ID 301 can be used to identify the same user in the data processing device 10, bank system 11, and payment service provider system 14, enabling single sign-on functionality for these devices and systems. For example, when a user logs in to the payment service provider system 14 using the generic ID 301 and PW 302, the payment service provider system 14 may be configured to send the generic ID 301 and PW 302 to the data processing device 10, have the data processing device 10 perform authentication processing, and receive the user ID 333 and PW 334 for the payment service provider system 14 from the data processing device 10. As a result, the payment service provider system 14 has performed authentication using the generic ID 301 and PW 302.

(Process flow: Account and account usage information acquisition process)
FIG. 11 is a flow diagram illustrating the process of acquiring account and account usage information.

At S1101, the data processing device 10 receives an information acquisition request from the user terminal 13, or receives an information acquisition request generated at a predetermined interval. The information acquisition request includes at least the general ID 301.

At S1102, the data processing device 10 queries the bank account 106-3 and the payment service account 106-4 based on the general ID 301 included in the information acquisition request, and acquires authentication information in the bank system 11 and the payment service provider system 14 for the bank account and payment service account associated with the general ID 301.

At S1103, the data processing device 10 identifies the bank system 11 to connect to based on the financial institution code 321 read from the bank account 106-3, and transmits the read information of the financial institution code 321, branch number 322, deposit type 323, account number 324, and CD PIN 325 to the bank system 11 to inquire about usage. The bank system 11 reads the balance and deposit/withdrawal details of the corresponding account and transmits them to the data processing device 10.

The data processing device 10 identifies the payment service provider system 14 to connect to based on the payment provider code 332 read from the payment service account 106-4, sends the user ID 333 and PW 334 information to the payment service provider system 14, and queries the usage status. The payment service provider system 14 reads the account balance and deposit/withdrawal details associated with the user ID 333 and PW 334, and sends them to the data processing device 10.

At S1104, the data processing device 10 sums the balance received from the bank system 11 and the balance received from the payment service provider system 14. The summed balance indicates the total amount associated with the user (general ID) stored in the bank system 11 and the payment service provider system 14. The data processing device 10 further sums the summed balance with the value of the system balance 309 and stores the result in the nominal balance 307 of account 106-1.

The processing of Figure 11 enables the data processing device 10 to grasp the balance and usage status of the value, bank account, and payment service account associated with the user.

In another embodiment of the present invention, the information acquisition request includes a general ID 301 and a PW 302. The data processing device 10 may be configured to acquire the balance and deposit/withdrawal details associated with the user by transmitting the general ID 301 and PW 302 to the connected bank system 11 and payment service provider system 14.

(Processing flow: Transfer of funds between users)
12 is a flow diagram illustrating a fund transfer process executed by the data processing device 10 according to the present invention. In the present invention, an example of a fund transfer process for a user whose general ID of the remittance destination is known will be described.

At S1201, the data processing device 10 receives a funds transfer instruction from the user terminal 13. The funds transfer instruction includes at least the general ID of the sender user, the general ID of the recipient user, and the amount to be transferred.

In S1202, the data processing device 10 queries account 106-1 based on the recipient user's general ID included in the funds transfer instruction, and determines whether the recipient user's general ID exists in account 106-1. If it does, processing proceeds to S1203; if it does not, processing proceeds to S1207.

At S1203, the data processing device 10 obtains the system balance 309 associated with the remittance source user's general ID, as well as the balance and usage status of the bank account and payment service account, using the method described with reference to FIG. 11. The obtained information is referred to as the first usage status.

At S1204, the data processing device 10 obtains the system balance 309 associated with the recipient user's general ID, as well as the balance and usage status of the bank account and payment service account, using the method described with reference to FIG. 11. The obtained information is referred to as the second usage status.

At S1205, the data processing device 10 compares the first usage status with the second usage status and determines the fund transfer path in accordance with predetermined criteria. The predetermined criteria for determining the fund transfer path may be the following criteria:

The first criterion is minimizing fees. Fees will be lower if the sender and recipient users use the same bank, the same bank and the same branch, or the same payment service. Therefore, the data processing device 10 can select the route that minimizes fees based on remittance fee information (not shown).

The second criterion is the frequency of use by the remittance recipient user. The data processing device 10 determines the most frequently used bank account or payment service account based on the second usage status. This allows the data processing device 10 to select as the remittance destination the bank account or payment service account that the remittance recipient user frequently uses.

The third criterion is the number of days required for the funds to arrive. Based on the date and time the funds transfer instruction is received, the data processing device 10 calculates the number of days required for the funds to arrive at each bank account and payment service account associated with the recipient user's general ID. For example, if the funds transfer instruction is received on a bank holiday or outside of business hours, the number of days required for the funds to arrive will differ for each bank and payment service. This allows the data processing device 10 to select as the recipient the bank account or payment service account that will require the fewest number of days for the funds to arrive.

The present invention is not limited to the first to third criteria, and remittances can be made based on other criteria. It is also possible to make remittances based on a combination of multiple criteria.

At S1206, the data processing device 10 executes the remittance process according to the fund transfer route determined at S1205. In connection with the remittance process, the data processing device 10 reduces the remittance source account or remittance account of the remitting user and increases the remittance destination account or remittance destination account of the remittance recipient user. In one embodiment of the present invention, the system balance 309 may be used as the remittance source and/or remittance destination. In another embodiment of the present invention, the data processing device 10 may request the connected system to perform the remittance process by sending a remittance instruction to the bank system 11 or payment service provider system 14 corresponding to the remittance source account or remittance account.

At S1207, the data processing device 10 notifies the user terminal 13 that the remittance recipient's general ID does not exist and remittance is not possible.

(Example of a screen)
13 is a diagram showing an example of a display screen 1300 according to the present invention. The user's balance displayed on the display screen 1300 is the amount of the nominal balance 307. That is, in this example, the total balance of all the value, bank accounts, and payment service accounts associated with the user "Gaitame Shiro" is displayed.

Display screen 1300 provides various menus. "Detailed Balance" provides the balance of each value, bank account, and payment service account associated with the user. "Receiving-Only (Virtual) Account Information" provides information on virtual account numbers. "Bank/Payment Service Account Information" provides information on bank accounts and payment service accounts. "Add Account" provides the ability to obtain a new virtual account number and enter information on bank accounts and payment service accounts.

(Other processing)
The data processing device 10 can perform a process of transferring a virtual account number to a bank account upon receiving a request from the bank system 11. For example, consider a case where a user has two virtual account numbers and one bank account. The bank system 11 sends a request to the data processing device 10 to transfer one of the virtual account numbers to a bank account. The transfer request includes the general ID 301, information about the virtual account number to be transferred, and information about the transferred bank account (e.g., a newly set CD PIN 325, etc.). In response to the transfer request, the data processing device 10 adds new data to the bank account 106-3 and deletes or disables the corresponding data from the virtual account number 106-2. Similarly, the data processing device 10 can perform a process of transferring a bank account to a virtual account number upon receiving a request from the bank system 11.

The principles of the present invention have been described above with reference to exemplary embodiments, but those skilled in the art will understand that various embodiments that vary in configuration and detail can be realized without departing from the spirit of the present invention. In other words, the present invention can be embodied as, for example, a system, device, method, program, or storage medium.

REFERENCE SIGNS LIST 10 Data processing device 11 Bank system 12 Corporate system 13 User terminal 14 Payment service provider system 101 Control unit 102 Main memory unit 103 Auxiliary memory unit 104 Interface (IF) unit 105 Output unit 106 Account management DB
106-1 Account 106-2 Virtual account number 106-3 Bank account 106-4 Payment service account 107 Deposit/withdrawal management DB

Claims (8)

a data processing device for communicating information with a user terminal and a first system, the data processing device comprising:
means for executing an identity verification process using the public personal authentication information in response to receiving a usage application including user information and public personal authentication information from the user terminal, and when the identity verification process is successfully completed, issuing a general-purpose ID for identifying the same user in the data processing device and the first system, transmitting the ID to the user terminal, and storing identity verification information based on the general-purpose ID, the user information, and the public personal authentication information in a storage unit;
means for receiving an authentication request from the first system, the authentication request including the generic ID;
means for obtaining the identity-verified information by making an inquiry to the storage unit based on the received general-purpose ID, and transmitting the identity-verified information to the first system;
a means for receiving a user information acquisition request including the general ID from the first system as a response to the identity verification information, reading the user information associated with the general ID from the storage unit, and transmitting the user information to the first system;
a means for receiving user information associated with the general-purpose ID from the first system in response to the user information and storing the user information in the storage unit;
A data processing device comprising: A data processing device according to claim 1, wherein receipt of the user information acquisition request indicates completion of identity verification processing by the first system using the identity verification information. The data processing device of claim 1 further comprises means for not sending the identity verification information to the first system and sending a message to the first system indicating that the authentication request is not accepted if the authentication date and time information included in the identity verification information does not indicate that the information is within the expiration date and time. The storage unit further stores a bank account DB that stores information on a bank account associated with a user, and a payment service account DB that stores information on a payment service account associated with the user,
The data processing device includes:
a means for querying the bank account DB and the payment service account DB based on the general-purpose ID included in the received information acquisition request, and acquiring the account balance of the bank account and the account balance of the payment service account associated with the general-purpose ID;
means for acquiring a system balance associated with the general-purpose ID stored in the storage unit;
a means for calculating the user's nominal balance by adding up the account balance of the bank account, the account balance of the payment service account, and the balance in the system;
The data processing apparatus of claim 1 further comprising: means for receiving a funds transfer instruction including information on the remittance source user's general ID, the remittance destination user's general ID, and the remittance amount;
A means for acquiring a first usage status based on the general ID of the remittance source user, the first usage status including the remittance source user's usage status and balance in the first system and a system balance associated with the remittance source user;
A means for acquiring second usage status based on the general ID of the remittance destination user, the second usage status including the remittance destination user's usage status and balance in the first system and a system balance associated with the remittance destination user;
A means for determining a fund transfer route according to a predetermined criterion, wherein the determining of the fund transfer route includes:
If the predetermined criterion is minimizing fees, comparing the account information and/or account information associated with the acquired first usage status with the account information and/or account information associated with the acquired second usage status, and selecting a funds transfer path that minimizes fees;
If the predetermined criterion is the frequency of use of the remittance destination user, selecting the most frequently used account or accounts based on the information on account deposit and withdrawal details and/or the information on account deposit and withdrawal details associated with the acquired second usage status;
If the predetermined criterion is the number of days required for the funds to arrive, calculate the number of days required for the funds to arrive if the funds are transferred to each of the accounts associated with the general-purpose ID of the recipient user based on the date and time of receiving the funds transfer instruction, and select the account or accounts that will require the shortest number of days for the funds to arrive;
and
The data processing apparatus of claim 1 further comprising: 1. A data processing method performed by a data processing device that communicates information with a user terminal and a first system, the method comprising:
In response to receiving a usage application including user information and public personal authentication information from the user terminal, execute an identity verification process using the public personal authentication information, and when the identity verification process is successfully completed, issue a general-purpose ID for identifying the same user in the data processing device and the first system, send it to the user terminal, and store identity verification information based on the general-purpose ID, the user information, and the public personal authentication information in a storage unit;
receiving an authentication request from the first system, the authentication request including the generic ID;
making an inquiry to the storage unit based on the received general-purpose ID to acquire the identity-verified information, and transmitting the identity-verified information to the first system;
receiving a user information acquisition request including the general ID from the first system as a response to the identity verification information, reading the user information associated with the general ID from the storage unit, and transmitting the user information to the first system;
receiving user information associated with the general-purpose ID from the first system in response to the user information and storing the user information in the storage unit;
A data processing method comprising: A data processing device that communicates with a user terminal, a bank system, and a payment service provider system,
means for executing an identity verification process using the public personal authentication information in response to receiving a usage application including user information and public personal authentication information from the user terminal, and when the identity verification process is successfully completed, issuing a user identifier for identifying the same user in the data processing device, the bank system, and the payment service provider system, transmitting the user identifier to the user terminal, and storing identity verification information based on the user identifier, the user information, and the public personal authentication information in a storage unit;
means for completing user authentication by the bank system and the payment service provider system by providing the identity-verified information associated with the user identifier to the bank system and the payment service provider system in response to receiving an authentication request including the user identifier from the bank system and the payment service provider system;
means for acquiring the account balance of a bank account and the account balance of a payment service account associated with the user identifier from the bank system and the payment service provider system, respectively;
means for acquiring a system balance associated with the user identifier, and calculating a nominal balance associated with the user identifier based on the acquired system balance, the account balance of the bank account, and the account balance of the payment service account;
A data processing device comprising: means for receiving a user identifier of a remitter and a user identifier of a remitter from the user terminal;
means for acquiring a first usage status associated with the user identifier of the remitter from the data processing device, the bank system, and the payment service provider system;
means for acquiring a second usage status associated with the user identifier of the remittance recipient from the data processing device, the bank system, and the payment service provider system;
A means for determining a fund transfer route and executing a remittance in accordance with a predetermined standard, wherein determining the fund transfer route includes:
If the predetermined criterion is minimizing fees, comparing the bank account information and/or payment service account information associated with the acquired first usage status with the bank account information and/or payment service account information associated with the acquired second usage status, and selecting a funds transfer path that minimizes fees;
If the predetermined criterion is the frequency of use of the remittance destination user, selecting the most frequently used bank account or payment service account based on the information on the bank account details and/or the information on the payment service account details associated with the acquired second usage status;
If the predetermined criterion is the number of days required for the funds to arrive, calculate the number of days required for the funds to arrive if the funds are transferred to each of the bank account and the payment service account associated with the recipient user's general-purpose ID based on the date and time the funds transfer instruction was received, and select the bank account or the payment service account that will require the shortest number of days for the funds to arrive;
a means for
The data processing apparatus of claim 7 further comprising: