JP7109717B2 - Remittance support server, remittance support system, remittance support method, and program for executing remittance support method - Google Patents

Description

The present invention relates to a remittance support server, a remittance support system, a remittance support method, and a program for executing the method, and in particular, to allow users who do not have bank accounts to conduct money transfer transactions via interbank networks. It relates to a remittance support system that enables.

2. Description of the Related Art Conventionally, exchange transactions, in which funds are transferred between remote locations via financial institutions such as banks, have been widely used for transfers and remittances of salaries, pensions, and dividends. For example, remittance processing based on exchange transactions is performed using deposit accounts opened in advance at financial institutions by a person sending funds (remittance requester) and a person receiving funds (recipient). Specifically, according to the remittance request information from the remittance requester, the remittance process is performed by decreasing the amount in the remittance requester's deposit account and increasing the amount in the recipient's deposit account.

In exchange transactions via such financial institutions, for example, when performing remittance processing for payment of salaries from a company to an employee, both the company requesting the remittance and the employee receiving the remittance are financially prepared in advance. It is necessary to open a deposit account at the institution, and it is not possible to send money to a person who does not have a deposit account at a financial institution.

In addition, since the remittance fee is borne by the remittance requester, in the case of a company with many employees, the company will bear a considerable amount of remittance fee for salary transfer. Furthermore, remittance fees to accounts at other banks are often set higher than remittance fees between accounts at the same financial institution.

JP-A-2000-82101 JP 2009-110371 A

Therefore, in order to reduce the remittance fee for salary transfer, the company may instruct the employee to open a bank account at the same financial institution where the bank account of the company is opened. However, it is inconvenient for employees to be forced to open a savings account at a financial institution that they do not want. Furthermore, the employee himself/herself needs to prepare documents and a seal for opening a savings account, and the procedural burden is heavy.

In order to improve the convenience of exchange transactions through financial institutions, there are transfer processing systems that perform transfer processing using a plurality of associated accounts associated with a payer of funds. Funds transferred to multiple related accounts are deposited into a specific account for consolidation, and the transfer information to the related accounts is added with the account-related information of the related accounts linked to the payer and output. The received transfer information is stored as transfer information for a specific account (see Patent Document 1).

However, although the transfer processing system of Patent Document 1 can reduce the burden of procedures on the side of the remittance requester, the recipient of the funds must open a bank account at a financial institution in order to collect several account numbers. The burden of procedures for opening a deposit account on the side of the recipient of the funds has not been alleviated.

Also, there is a proxy account management device that associates and manages a deposit account opened at a financial institution and an account (proxy account) for temporarily storing funds until the money is deposited into the deposit account already opened at the financial institution. There is (see Patent Document 2). However, the proxy account management device of Patent Literature 2 uses a proxy account as an account for temporarily storing funds until the funds are deposited into an account that has already been opened at a financial institution. Since the recipient of funds is required to open a deposit account at a financial institution, the burden of procedures on the recipient side of funds has not been alleviated in this case either.

SUMMARY OF THE INVENTION The object of the present invention was made in view of the above problems. To provide a remittance support server, a remittance support system, a remittance support method, and a program for executing the remittance support method.

In order to achieve the above object, a remittance support server according to the present invention provides specific transaction store identification information given to a physical account designated and opened by a financial institution, and a physical account that identifies the physical account. a specific transaction store management database storing information, a specific store number included in the specific transaction store identification information, and loan account information specifying a loan account opened in association with the specific store number; a loan account management database for storage; a loan account name changing unit that rewrites account name information of the loan account to user name information of the user according to the result of authentication processing for the user of the loan account; and a financial institution a remittance destination request data reception unit that receives remittance destination request data including a remittance destination branch number that specifies a remittance destination store and receiver name information that specifies a receiver via a financial network that connects the parties; a specific store information determination unit that determines whether or not the remittance destination store number matches the specific store number; a loan account name information determination unit that determines whether or not the user name information matches the user name information; and if the loan account name information determination unit determines that they match, the It is characterized by comprising a loan account transfer processing unit that executes transfer processing to the loan account.

Further, the remittance support server of the present invention may further include a physical account deposit processing unit that executes deposit processing to the physical account based on the remittance destination request data.

Further, the remittance support server of the present invention further includes a condition determination unit that determines whether or not a predetermined condition regarding the loan account is satisfied, and the transfer processing unit for the loan account determines whether the predetermined condition is satisfied. transfer processing from the real account to the loan account may be executed.

The predetermined condition may be receipt of payment permission confirmation information indicating permission of payment to the recipient by the account holder of the physical account.

The predetermined condition may be receipt of payment permission confirmation information indicating permission of payment to the recipient by the account holder of the physical account.

Further, the actual account deposit processing unit includes a changed remittance destination request data generation unit that generates changed remittance destination request data in which the remittance destination request data is changed in accordance with the actual account information, and a changed remittance destination request data and a physical account payment processing unit for executing payment processing to the physical account.

When the payment processing in the physical account payment processing unit is executed, the physical account payment processing unit transmits payment notification information to the physical account notifying that the payment processing has been executed to the recipient. You may further have the real account payment notification part which carries out.

Further, the remittance support system of the present invention is connected to a remittance support server and the remittance support server via an information communication network so as to be communicable with the remittance support server. and a user terminal for transmitting and receiving money information.

Further, the remittance support method according to the present invention is executed by a computer, and stores specific transaction store identification information given to a specified real account opened in a financial institution and real account information for specifying the real account. a step of preparing a specific transaction store management database to be stored; a specific store number included in the specific transaction store identification information; and loan account information specifying a loan account opened in association with the specific store number. and a loan account name change step of rewriting the account name information of the loan account to the user name information of the user according to the result of authentication processing for the user of the loan account. and remittance destination request data including a remittance destination branch number specifying a remittance destination store and the recipient name information of the user specified as a recipient via a financial communication network connecting financial institutions. a remittance destination request data reception step for receiving; a specific store information determination step for determining whether or not the remittance destination store number matches the specific store number; a lending account name information determining step of determining whether or not the recipient name information matches the user name information of the lending account when it is determined that the store number matches the specific store number; If it is determined that the recipient name information matches the account name information of the loan account as a result of determination in the name information determination step, transfer processing from the actual account to the loan account is performed based on the remittance destination request data. and a loan account transfer processing step to be executed.

Further, a remittance payment program according to the present invention is for a specific transaction that stores specific transaction store identification information given to a specified real account opened in a financial institution, and real account information that specifies the real account. A step of preparing a store management database; a loan account storing a specific shop number included in the specific transaction shop identification information and loan account information specifying a loan account opened in association with the specific shop number; a step of preparing a management database; a lending account name changing step of rewriting account name information of said lending account to user name information of said user according to a result of authentication processing for said lending account user; a remittance destination request data receiving step of receiving remittance destination request data including a remittance destination branch number specifying a remittance destination store and receiver name information specifying a receiver via a financial communication network connecting the two; a specific store information determining step of determining whether or not the remittance destination store number matches the specific store number; If it is determined that the recipient name information matches the user name information of the loan account, a loan account name information determination step for determining whether or not; a loan account transfer processing step of executing transfer processing from the actual account to the loan account based on the remittance destination request data when it is determined that the recipient name information matches the account name information of the loan account; causes a computer to execute a remittance support method comprising:

INDUSTRIAL APPLICABILITY According to the present invention, a remittance support server and a remittance support system that enable exchange transactions via a financial institution such as a bank even if the recipient of funds has not opened a deposit account at the financial institution such as a bank. , a remittance support method, and a program for executing the remittance support method.

1 is a diagram schematically showing the configuration of a bank system according to first and second embodiments of the present invention; FIG. 1 is a diagram schematically showing the hardware configuration of a remittance support server according to the first embodiment of the present invention; FIG. FIG. 4 is a diagram showing an example of a real account table, a specific transaction store management table, and a loan account management table at the time of opening a loan account according to the first embodiment of the present invention; FIG. 3 is a functional block diagram for explaining functions of the remittance support server according to the first embodiment of the present invention shown in FIG. 2; FIG. 7 is a diagram showing an example of a loan account management table after changing the account name of the loan account according to the first embodiment of the present invention; FIG. 4 is a diagram showing a format of remittance destination request data according to the first embodiment of the present invention; FIG. (a) is a diagram showing a real account table and a loan account management table in a state in which money has been deposited into a real account according to the first embodiment of the present invention; (b) is a diagram showing the first embodiment of the present invention; FIG. 10 is a diagram showing a real account table and a loan account management table after performing a transfer process from a real account to a loan account in the form of . FIG. 10 is a diagram showing a format of loan account money receipt notification information indicating that money has been received in a loan account by transfer processing from a real account to a loan account; FIG. 3 is a schematic flow chart showing processing executed by the remittance support server according to the first embodiment of the present invention shown in FIG. 2; FIG. FIG. 10 is a functional block diagram for explaining other functions of the remittance support server according to the second embodiment of the present invention; FIG. 10 is a diagram for explaining processing executed by a changed remittance destination request data generation unit according to the second embodiment of the present invention; FIG. 10 is a diagram showing the format of the actual account receipt notification information for notifying the user of the loan account that the money has been received in the actual account based on the changed remittance destination request data according to the second embodiment of the present invention. . FIG. 10 is a schematic flow chart for explaining other processing executed by the remittance support server according to the second embodiment of the present invention; FIG. FIG. 11 is a diagram showing another usage example of the store management table for specific transaction; FIG. 10 is a diagram showing yet another example of usage of the specific transaction store management table;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

<First embodiment>
FIG. 1 is a diagram schematically showing the configuration of a bank system 1 according to first and second embodiments of the present invention. The configuration of FIG. 1 shows an example thereof, and the configuration of the remittance support system according to the present invention is not limited to that of FIG. The term "banking system" is used for the sake of convenience, and is not limited to banking systems under the Banking Act. good too. Similarly, when using terms such as "own bank" and "other bank" hereinafter, they are not limited to banks under the Banking Act, and can be any financial institution that conducts exchange transactions. good too.

A bank system 1 according to the first embodiment of the present invention is communicably connected to a head office/branch system 2 via a financial network such as Zengin-net 3 that connects financial institutions. This is a center system configured to receive remittance request information, which is a remittance request instruction from a remittance destination to a remittance destination. The head office/branch system 2 is a general term for an information processing system for banking operations at a head office of a financial institution and an information processing system for banking operations at a branch office. The head/branch system 2 may be a head/branch system of one's own bank, or may be a head/branch system of another bank.

In addition, the bank system 1 is connected to the user terminals 6A and 6B via an information communication network such as the Internet 5 so as to be able to communicate by wire or wirelessly. (hereinafter also referred to as "loan account deposit/withdrawal information") can be transmitted and received.

This banking system 1 includes a Zengin server accounting system host 4 which is a host computer that controls communication with the head office/branch system 2 via Zengin-net 3, and various servers that perform various information processing related to financial institution operations. and a bank server group 10 including The bank server group 10 includes a bank server accounting system host 11 which is a host computer for managing bank accounts, a communication server 12 for controlling information communication via the Internet 5, etc., and a remittance support method executed by the computer. and a remittance support server 13 realized by

The bank server accounting system host 11 has a real account database (DB) 20A for managing real accounts designated and opened by banks, which are financial institutions. A “real account” is a conventional existing account that is opened by a financial institution such as a bank and allows deposits and withdrawals.

The remittance support server 13 has a specific transaction store management database (DB) 13A and a loan account management database (DB) 13B. A specific transaction shop management database (DB) 13A includes specific transaction shop identification information including a specific shop number assigned to a real account, and real account information identifying a real account associated with the specific transaction shop identification information. It is a database that stores

Here, the "specific branch number" means that in exchange transactions between banks, the user, who is the recipient of the remittance, conducts exchange transactions through a loan account, which will be described later, without having a savings account. A number representing a virtual specific store used for a specific transaction (hereinafter also referred to as a “specific transaction”).

Further, the "specific transaction shop identification information" is information including a specific shop number that identifies the specific transaction shop and shipment order information that specifies an arbitrary order of shipment. A “loan account” is a temporary loan account that does not allow deposits and withdrawals but does not bear interest.

A loan account management database (DB) 13B specifies a specific store number included in the specific transaction store identification information and a loan account opened in association with the specific store number and available to the user on the receiving side. It is a database that stores loan account information.

The bank server group 10 may have other servers (not shown) such as an information system host, which is a host computer that performs processing for providing services related to operations other than the accounting system in financial institution operations. . The bank server group 10 may also include a notification server (not shown) that provides various notifications to the users of the user terminals 6A and 6B. The communication server 12 in the bank server group 10 may be connected to an automated teller machine (ATM) 7 of the bank itself. The banking system 1 is not limited to a system in a bank under the Banking Law as long as it is a system that processes financial information. In the present embodiment, the Zengin-net 3 is a Zengin-net that communicates in a format established by the Japanese Bankers Association (ZENGINKYO), but may be another financial network.

FIG. 2 is a diagram schematically showing the hardware configuration of remittance support server 13 according to the first embodiment. Note that FIG. 2 shows an example of the hardware configuration, and the configuration of the remittance support server 13 according to the first embodiment is not limited to that shown in FIG.

As shown in FIG. 1, the remittance support server 13 according to the first embodiment is a computer that manages the information stored in the specific transaction store management database 13A and the loan account management database 13B shown in FIG. , a control unit 110 , a storage unit 120 , an input unit 130 , an output unit 140 , and a communication unit 150 , which are interconnected via a bus 160 .

The control unit 110 is composed of a processor such as a CPU (Central Processing Unit) or MPU (Micro Processing Unit), and controls the operations and various processes of the remittance support server 13 in an integrated manner. The control unit 110 is configured to be able to implement a remittance support method by appropriately reading out and executing a remittance support program pre-stored in the storage unit 120 . Detailed operations and various processes of the remittance support server 13 will be described later.

The storage unit 120 includes, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), and/or a hard disk drive, and is configured as a computer-readable storage medium. The storage unit 120 stores a remittance assistance program for the control unit 110 to execute a remittance assistance process. The storage unit 120 is preferably non-transitory and composed of a computer-readable storage medium. In the first embodiment, as shown in FIG. Although connected to the input unit 130, the output unit 140, and the communication unit 150, the storage unit 120 may store all or part of the specific transaction store management database 13A and the loan account management database 13B.

The remittance support server 13 is connected to a communication network such as a LAN of the bank server group 10 via the communication unit 150, and communicates with the bank server accounting system host 11 and the communication server 12 of the bank server group 10 via the communication network. configured to communicate with each other.

Here, before describing the specific transaction store management database 13A and the loan account management database 13B, first, an actual account opened in a financial institution such as a bank will be described with reference to FIGS. 1 and 3. FIG.

A financial institution such as a bank has an actual account database 20A in the bank server accounting system host 11 (FIG. 1). In the real account database 20A, as shown in FIG. A real account table T1 containing account name information AN1 of the identified real account and balance information TB1 indicating the balance (yen) 206 is stored.

Banks and other financial institutions require applicants who wish to open a physical account to fill out identity verification documents and report their seal. A real account is opened in association with an actual shop (hereinafter also referred to as a "real shop") with the account holder as the account holder. When a real account is opened in a financial institution such as a bank in this way, various information (actual account information RA1, account name information AN1, and balance information TB1) of a person who wishes to open a real account is stored in the real account table T1. is stored.

For example, if a person who wishes to open a bank account named "Kanri Taro" opens a physical account at a physical store called XY branch of a financial institution called ABC bank, the actual account table T1 contains the financial institution code 201 "1310" of ABC bank. , XY branch branch number 202 "137", real account deposit type 203 "1", real account account number 204 "1234567", account holder 205 "Management Taro", and balance (yen) 206 "0" (circle) is added (see FIG. 3A).

Here, the "financial institution code" is identification information assigned to each financial institution in order to identify ABC Bank, which is a financial institution. In the first embodiment, the Japanese Bankers Association ( It is represented by a four-digit number conforming to the so-called Zengin format established by the Japanese Bankers Association (JBA). A "branch number" is a unique number assigned to each branch of each financial institution, and in the first embodiment, it is represented by a three-digit number conforming to the Zengin format.

"Deposit type" is information given to each account to specify the deposit type, and is represented by a one-digit number conforming to the Zengin format. In the deposit type, for example, "1" indicates that it is a deposit account that allows deposits and withdrawals, and "9" indicates that it is a temporary loan account that does not allow deposits and savings and can only be used for deposits and withdrawals. indicates that there is An "account number" is a unique number that identifies an actual account opened at each store, and in the first embodiment, is represented by a 7-digit number conforming to the Zengin format. Since the last digit is a number used as a check digit, the number of digits that can be used as an account number is substantially the first six digits. "Balance (yen)" is the balance of the actual account, and the unit in this case is Japanese Yen.

Next, a case where a real account opened by a person who wishes to open is associated with a specific transaction shop will be described with reference to FIG. 3(b). As shown in FIG. 3(b), the specific transaction store management database 13A contains specific transaction store identification information SD2 given to the actual account specified and opened by ABC Bank, and the actual account. and account name information AN2 indicating the account holder of the actual account.

Here, the "specific transaction store identification information SD2" is unique information that identifies the specific transaction store. Includes a specific store number 211A represented by a number. In addition, in preparation for the case where two or more actual accounts are associated with the same specific shop number 211A, as will be described later, the specific transaction shop identification information SD2 may further include the order of delivery 211B representing the order of delivery. .

"Actual account information RA2" is the same information as the actual account information RA1 stored in the actual account table T1. 212D field.

The "account name information AN2" is the same information as the account name information AN1 stored in the actual account table T1, and includes the account name 212E field in this embodiment.

For example, when the actual account specified by the actual account information RA1 in the actual account table T1 of FIG. Stored in T2 is the specific branch number "888" assigned in advance by the bank system 1 to the specific branch number 211A. Account name information AN2 of a real account that stores institution code 212A "1310", branch number 212B "137", deposit type 212C "1", and account number 212D "1234567" and is associated with specific branch number 211A "888" , the account holder 212E "Management Taro" is stored.

Next, the case where the account holder opens a loan account in association with a specific transaction shop will be described with reference to FIG. 3(c).

As shown in FIG. 3(c), the loan account management database (DB) 13B stores a loan account management table T3 including loan account information LA3, account name information AN3, and balance information TB3.

The loan account information LA3 is unique information that identifies a loan account opened in association with a specific shop, and includes a financial institution code 232A that identifies the financial institution where the loan account is opened, and a shop number representing a specific shop number. 232B, deposit type 232C indicating the deposit type of the loan account to be opened, and account number 232D of the loan account to be opened. The account name information AN3 includes an account holder 233A field representing the name of "Taro Manager" who is a lending account opening applicant who wishes to open a lending account (in this case, the same as the account opener of the actual account), The balance information TB3 includes a balance (yen) 234A field representing the balance of the loan account.

Since a loan account is opened at the request of the account holder of the real account, it does not require identity verification documents or a seal notification that are required when opening a real account. For example, it is assumed that a request for opening a loan account is received from the account holder 205 "Taro Manager" of the account name information AN1 in the actual account table T1.

At this time, in the loan account management table T3, the financial institution code 232A is "1310", the store number 232B is "888" which is the specific store number, the deposit type 232C is "9" which means the loan account, and the account number 232D is "7788663". ”, “Management Taro” whose account holder 233A is the same account holder as the real account, and “0” (yen) in the balance (yen) 234A is the loan account information LA3, the account name information AN3, and the balance It is stored as the value of each field of information TB3.

Also, when there is a request to open a further additional lending account from the account holder 205 "Management Taro" in the actual account table T1, the financial institution code 232A "1310", branch number 232B "888", deposit type 232C " 9", the account number 232D is "3939391" which is different from the previous one, the account holder 233A is "Management Taro" which is the account holder of the real account, and the balance (yen) 234A is "0" (yen) for each field. Stored as a value. Incidentally, as shown in FIGS. 3(a) to 3(c), when the loan account is opened, the account holder 233A (FIG. 3(c)) of the loan account is registered in the actual account table T1 (FIG. 3(a) ) is the same as the account holder 205 “Management Taro”.

FIG. 4 is a functional block diagram for realizing a remittance support function by the control unit 110 of the remittance support server 13 according to the first embodiment of the present invention shown in FIG. As shown in FIG. 4, the functional units realized by the control unit 110 of the remittance support server 13 executing according to the remittance support server program are a loan account name change unit 111, a remittance destination request data reception unit 112, and a specified It has a store information determination section 113 , a loan account name information determination section 114 , a condition determination section 115 , and a loan account destination transfer processing section 116 .

That is, the remittance support server 13 is realized by installing the above-described remittance support server program (software) in the storage unit 120 of the computer (hardware). Each functional part is realized by cooperating with hardware. It is assumed that the storage unit 120 also pre-stores list data in which the names of a plurality of users who can be recipients from "Taro Manager" who opened the account are described. Here, the list data is preliminarily stored in the storage unit 120, but the names of a plurality of users who can be recipients are specified by other methods than pre-storing the list data in the storage unit 120. good too. For example, there is a method of pre-storing the names of a plurality of possible recipients in an external database other than the bank system 1 .

The lending account name change unit 111 reads from the storage unit 120 (FIG. 2) the above list data in which the name of "Jiro Yamada" who can be a user on the receiving side is specified in advance from "Taro management" who is the account opener, According to the result of the authentication process for the user "Jiro Yamada" who can be the recipient, the account holder 233A of the account name information AN3 of the loan account in the loan account management table T3 is changed from the account opener "Taro Manager" to the user. It is a functional part that rewrites to the name information of "Jiro Yamada". Here, the authentication process for "Jiro Yamada", who is to be the user of the loan account on the receiving side, may be any authentication method such as fingerprint authentication or confirmation of driver's license information.

The rewriting of the account holder name information AN3 of the loan account management table T3 to the account holder 233A by the loan account name change unit 111 is the same as when the remittance request data M (FIG. 6), which will be described later, is received by the remittance request data reception unit 112. This is done at the same time or before receiving the remitter request data M in the remittee request data receiving unit 112 .

Here, if the account holder 233A of the account name information AN3 in the loan account management table T3 is rewritten before the receiver request data M is received by the receiver request data receiver 112, the account holder "administrator The control unit 110 of the remittance support server 13 receives loan contract conclusion information (not shown) indicating that a loan contract for a loan account has been concluded between "Taro" and "Jiro Yamada" who can be a user on the receiving side. do when The loan contract conclusion information may be transmitted from the user terminals 6A and 6B to the bank system 1 via an information communication network such as the Internet 5 as shown in FIG. may be entered directly via

As a result of the authentication processing, when it is determined that the person is the user "Jiro Yamada", and the lending account name changing unit 111 receives the notification of the determination result, the lending account name changing unit 111 informs "Jiro Yamada". It is possible to determine that the loan account may be lent out.

In this case, the lending account name changing unit 111, for example, changes the account holder 233A of the lending account, which is the account number 232D "7788663" of the account name information AN3 in the lending account management table T3 of FIG. The account holder name 205 is changed from "Management Taro" to "Jiro Yamada" who is the user of the loan account on the receiving side. FIG. 5 is a diagram showing an example of the loan account management table T3 after the account holder 233A of the account name information AN3 in the loan account management table T3 is changed from "Taro Manager" to "Jiro Yamada".

In this way, the loan account name changing unit 111 rewrites the account holder name 233A of the account name information AN3 in the loan account management table T3 from the account opener "Taro Manager" to the name information of the user "Jiro Yamada" on the receiving side. As a result, the loan account can be temporarily lent to the user. In this way, for example, a given company may open a real account in advance at ABC Bank with "Kanri Taro" as the account holder, and a new employee "Jiro Yamada" who will be the recipient of the loan account associated with the real account. can be temporarily rented to

By doing this, the user "Jiro Yamada" who is a new employee can receive money such as salary addressed to himself through the loan account without having to open his own deposit account at ABC Bank. . Further, for example, when "Jiro Yamada" retires from the company, the account holder 233A of the account name information AN3 in the loan account management table T3 can simply be returned to the account holder of the actual account "Taro Management". When an employee joins the company, the loan account can be rewritten in the name of the other employee. Thus, the user on the receiving side can save the trouble of opening a real account at the financial institution, and management of the loan account becomes easy for both the financial institution and the account holder of the real account.

The remittance destination request data reception unit 112 is a functional unit that receives remittance destination request data from a remittance requester via a financial network such as Zengin-net 3 . FIG. 6 is a diagram showing an example of the format of the remittance destination request data M according to the first embodiment, which is transmitted from the head office/branch system 2 by the remittance requester and received via the Zengin Network 3, for example.

The remittance destination request data M includes remittance requestor information PN that identifies a remittance requester 301, a financial institution code 302 that identifies ABC Bank where a loan account to be a remittance destination is opened, and a store that will be a remittance destination. Remittance destination request information TR including fields of remittance destination branch number 303, order of delivery 304, deposit type 305, and remittance destination account number 306 that identifies the loan account to which the remittance is to be made, and recipient name 307 that identifies the recipient. and remittance amount information TA including a remittance amount (yen) 308 field. The destination order 304 is information used to designate which physical account to send to when there are two or more physical accounts for one specific store number. The remittance request data M may have other fields such as remittance request date and time, in addition to the remittance requestor information PN, remittance destination request information TR, remittee name information TN, and remittance amount information TA described above.

For example, when remittance of 10,000 yen is to be made from the remittance requester "Taro Kanri" to the user "Jiro Yamada" of the loan account, the remittance destination request data M is the remittance requester 301 of the remittance requester information PN. In the remittance destination request information TR, the financial institution code 302 is “1310,” the remittance destination branch number 303 is “888,” the order of delivery 304 is “1,” the deposit type is “9,” and the remittance destination account number is “9.” 7788663", the receiver's name 307 of the remittance destination name information TN is "Jiro Yamada", and the remittance amount (yen) 308 of the remittance amount information TA is "10,000" yen.

The specific shop information determining unit 113 determines that the remittance destination shop number 303 included in the remittance destination request information TR of the remittance destination request data M matches the specific shop number 211A (FIG. 3(b)) of the specific transaction shop management table T2. determine whether or not to In the example of FIG. 3(b), the specified store number 211A of the store management table T2 for specific transactions is "888", so the remittance destination store number 303 "888" of the remittance destination request data M and the specified store number 211A "888" ” is determined to match.

If the specific store information determination unit 113 determines that they match, the specific store with the specific store number 211A "888" is specified by the remittance destination request data M. This means that a loan account has already been opened by "Taro Management", who is the account opener of On the other hand, if they do not match, it means that the remittance account specified by the remittance destination request information TR of the remittance destination request data M is not a loan account but a real account.

The specific store information determination unit 113 determines that the remittance destination store number 303 "888" included in the remittance destination request information TR of the remittance destination request data M matches the specific store number 211A of the specific transaction store management table T2. In this case, the loan account name information determination unit 114 determines that the recipient name 307 of the remitter name information TN in the remitter request data M matches the account holder 233A of the account name information AN3 stored in the loan account management table T3. determine whether or not to

Specifically, the loan account name information determining unit 114 determines that the recipient name 307 “Jiro Yamada” of the remittee name information TN of the remitter request data M shown in FIG. It is determined whether or not it matches the account holder 233A of AN3. As shown in FIG. 5, in the loan account management table T3, the account holder 233A of the account name information AN3 has already been rewritten to the name information "Jiro Yamada" of the user who will be the recipient. is lent to the user "Jiro Yamada", the recipient name 307 "Jiro Yamada" in the remittance destination request data M is the account holder 233A "Yamada Jiro". In this case, the lending account name information determining unit 114 determines that the lending account to which the remittance request data M is to be sent is valid.

On the other hand, when the loan account management table T3 is in the state shown in FIG. When the loan account is not lent out, the recipient name 307 "Jiro Yamada" of the remittance destination request data M does not match the account holder name 226 "Taro Kanri" which is the account name information of the loan account. In this case, the lending account name information determination unit 114 determines that the lending account specified by the remittance destination request information TR of the remittance destination request data M is invalid. If it is determined to be invalid, the control unit 110 of the remittance support server 13 terminates the remittance process without performing the remittance process. When the remittance process is not performed, the control unit 110 may perform error processing such as returning an error message to the remittance requester.

The condition determination unit 115 is a functional unit that determines whether or not the loan account satisfies a predetermined condition determined by the account holder of the real account for the loan account. The predetermined condition stipulated for the loan account is, for example, reception of receipt intention confirmation information (not shown) indicating the receipt intention of "Jiro Yamada" who is the loan account user via the Internet 5. . Alternatively, another predetermined condition for the loan account is that payment permission confirmation information (not shown) indicating permission for payment by the remittance requester to the loan account user "Jiro Yamada" is received via the Internet 5. That is.

By providing the condition determination unit 115 in this way, and performing the processing in the loan account destination transfer processing unit 116 only when the condition determination unit 115 determines that the loan account satisfies a predetermined condition. , exchange transactions such as remittance processing to those who do not have accounts at financial institutions can be executed more safely and reliably.

The lending account destination transfer processing unit 116 selects the lending account from the real account corresponding to the store number 202 "137" and the account number 204 "1234567" specified by the real account information RA1 of the real account table T1 (Fig. 3(a)). Transfer processing is executed to transfer to the loan account corresponding to the store number 232B "888" and the account number 232D "7788663" specified by the loan account information LA3 of the account management table T3 (FIG. 5).

For example, as shown in FIG. 7A, when the balance (yen) 206 of the balance information TB1 of the actual account table T1 is "10,000", the loan account destination transfer processing unit 116 determines that the balance of the actual account is "10,000". ” to the loan account of the account number 232D “7788663” associated with the account holder 233A “Jiro Yamada” of the account name information AN3 of the loan account management table T3.

In this case, as shown in FIG. 7B, the balance of the real account corresponding to the real account (branch number 202 "137", account number 204 "1234567") specified by the real account information RA1 in the real account table T1 (Yen) 206 10,000 yen is subtracted from 10,000 yen to become 0 yen, and the account holder 233A "Jiro Yamada" of the account name information AN3 specified by the loan account information LA3 of the loan account management table T3 10,000 yen is added to the balance (yen) 234A of "0" yen of the loan account (store number 232B "888", account number 232D "7788663"), resulting in "10,000" yen. As a result, it becomes possible to remit 10,000 yen from “Kanri Taro,” who opened an account, to “Jiro Yamada,” a user who does not have an account with ABC Bank.

In addition, prior to performing the transfer process from the real account to the loan account, for example, a transaction log database (not shown) is provided in the storage unit 120 or an external storage unit (not shown), and Such transaction log may be recorded. The transaction log includes, for example, the transaction date of the remittance, the remittance requester, the remittance destination loan account, and other information.

In addition to the functional units shown in the functional block diagram of FIG. 4, the remittance support server 13 according to the present embodiment has a loan account settlement function realized by the control unit 110 of the remittance support server 13 executing according to the remittance support server program. It may also have a gold notification unit (not shown). When the transfer processing from the actual account to the loan account is executed in the loan account destination transfer processing unit 116 as described above, the loan account payment notification unit indicates that the transfer processing has been completed. Such loan account money receipt notification information N1 is transmitted to the recipient (in this case, "Jiro Yamada") who is the holder of the loan account through the Internet 5 . That is, the loan account payment notification information N1 is transmitted to the user terminals 6a and 6b via the Internet 5 as the loan account deposit/withdrawal information described above. Incidentally, it is assumed that the loan account receipt notification unit has previously recognized a contact address such as an e-mail address addressed to "Jiro Yamada" who is the holder of the loan account.

This loan account receipt notification information N1 includes, for example, remittance requester information PN including remittance requester 301 "Taro Taro", which is the same as the content of remittance destination request data M (FIG. 6), financial institution code 302 "1310", remittance Remittance destination request information TR including destination store number 303 "888", destination order 304 "1", deposit type 305 "9", remittance destination account number 306 "7788663", remittance destination name information TN including recipient name 307, and , remittance amount information TA including remittance amount (yen) 308 "10,000" yen, and a field of transaction date 401 "2017/08/31" of loan account payment date information DA1.

Here, the transaction date 401 field is, for example, information based on a transaction log read from a transaction log database (not shown) in the storage unit 120 or an external storage unit (not shown). Note that the loan account receipt notification unit (not shown) may be provided in the control unit 110 of the remittance support server 13, or may be provided in the notification server 16 separate from the remittance support server 13 as shown in FIG. may be

FIG. 9 is a schematic flow chart showing the processing executed by the remittance support server 13 of the first embodiment shown in FIG. Each process of the remittance support method is executed by the control unit 110 of the remittance support server 13, and various data stored in the storage unit 120 or the remittance support server 13 are read according to each step of this remittance support process.

Here, using the actual account table T1, the specific transaction store management table T2, and the loan account management table T3 shown in FIGS. 3(a) to (c), FIGS. A remittance support method according to the present embodiment will be described.

The control unit 110 of the remittance support server 13 uses the lending account name changing unit 111 to read list data containing the names of a plurality of possible users identified by the account opener from the storage unit 120, and uses the lending account. According to the result of the authentication processing for the user on the receiving side, if the user is a person listed in the list data, the account holder 233A of the account name information AN3 in the loan account management table T3 is "Management Taro". to "Jiro Yamada" in the list data (step S1).

Next, the control unit 110 of the remittance support server 13 causes the remittance request data reception unit 112 to send the remittance destination branch number 303 specifying the remittance destination store and the receipt specifying the recipient via the Zengin Network 3 . Remittance destination request data M including person's name 307 is accepted (step S2).

Then, the control unit 110 of the remittance support server 13 causes the specific store information determination unit 113 to determine whether the remittance destination store number 303 of the remittance destination request data M matches the specific store number 211A of the specific transaction store management table T2. is determined (step S3). In the example of FIG. 3(b), in the specific transaction shop management table T2, the specific shop number 211A is "888", so the remittance destination shop number 303 "888" of the remittance destination request data M and the specific shop number 211A " 888" (step S3: YES).

If they match, the remittance destination shop of the remittance destination request data M is the specific shop number 211A "888", which means that a loan account has already been opened in the loan account management table T3. The control unit 110 of the server 13 proceeds to step S4. On the other hand, if they do not match (step S3: NO), it means that the remittance destination shop of the remittance destination request data M is a physical shop that does not have a loan account. The remittance support method ends without performing the above processing.

In step S4, the control unit 110 of the remittance support server 13 confirms that the recipient name 307 "Jiro Yamada" of the remittee name information TN in the remittance request data M is the account holder of the account name information AN3 in the loan account management table T3. 233A.

When the loan account management table T3 is in the state shown in FIG. 5, that is, when the account holder 233A of the account name information AN3 is "Jiro Yamada", the remittee name information TN in the remitter request data M (FIG. 6) is The payee name 306 "Jiro Yamada" matches the account holder 233A "Jiro Yamada" of the account name information AN3 in the loan account management table T3 (step S4: YES), and the process proceeds to the next step S5.

On the other hand, if it is determined that they do not match (step S4: NO), the specific store information determination unit 113 determines that the remittance destination request data M requests remittance to an invalid loan account that is not lent. Therefore, the remittance support method is terminated.

Next, in step S5, the control section 110 of the remittance support server 13 uses the condition determination section 115 to determine whether or not the loan account satisfies a predetermined condition determined by the account holder of the real account. The predetermined condition for the loan account is, for example, receipt intention confirmation information indicating the receipt intention of "Jiro Yamada", who is the user of the loan account, has been received via the Internet 5, or other conditions regarding the loan account. The predetermined condition is that the remittance requester has received via the Internet 5 payment permission confirmation information indicating permission for payment to "Jiro Yamada" who is the user of the loan account.

In this way, the conditions are determined in step S5, and only when it is determined that the loan account satisfies the predetermined conditions, the transfer processing to the loan account in step S6 is executed. Exchange transactions such as remittance processing to those who do not have accounts can be executed more safely and reliably.

Next, in step S6, the control unit 110 of the remittance support server 13 causes the loan account destination transfer processing unit 116 to execute transfer processing from the actual account to the loan account based on the remittance destination request data M. End the process. Specifically, as shown in FIG. 7A, when the balance (yen) 206 of the balance information TB1 in the actual account table T1 is "10,000", the account of the account name information AN3 in the loan account management table T3 Transfer 10,000 yen to the loan account of 233A "Jiro Yamada".

In this case, as shown in FIG. 7B, 10,000 yen is subtracted from the balance (yen) 206 of the balance information TB1 in the actual account table T1, resulting in "0" yen, and the account name information AN3 in the loan account management table T3. account holder 233A "Jiro Yamada" balance (yen) 234A "10,000" yen. As a result, it will be possible to send money to “Jiro Yamada,” a person who does not have a bank account at ABC Bank, from “Taro Kanri,” who opened the account, via the loan account with account number 232D “7788663.” It becomes possible.

In this way, the control unit 110 of the remittance support server 13 performs transfer processing from the real account to the loan account, thereby making It is possible to prevent erroneous transfer processing (remittance processing) to be performed.

Note that the existing bank server accounting system host 11 may be set not to accept remittance processing for store numbers other than the actual store as a security measure for preventing unauthorized operations. Even in the bank system 1 with such security measures in place, the processing in the existing bank server accounting system host 11 can be significantly changed if the transfer processing is always performed to the loan account via the actual account. It is possible to safely remit money to a user of a loan account who does not have a real account.

Further, if the recipient name 307 of the remittance destination name information TN in the remittance destination request data M does not match the account holder name 233A of the account name information AN3 in the loan account management table T3 (step S4: NO), the remittance requester By sending an error message to , the remittance requester can be urged to correct the error in the remittance destination request data M and try the remittance process again.

<Second Embodiment>
Next, a second embodiment will be described. In this case, the remittance support server 13 is provided with other functions. The configuration of the bank system according to the second embodiment is the same as that of the bank system 1 according to the first embodiment described above with reference to FIG. 1, so the description is omitted here.

FIG. 10 is a functional block diagram for explaining other functions of remittance support server 13 according to the second embodiment of the present invention. As shown in FIG. 10, in which parts corresponding to those in FIG. In addition to the account name change unit 111 to the lending account destination transfer processing unit 116, based on the remittance destination request data M sent from the remittance requester to the user of the lending account, deposit processing is executed for the actual account associated with the lending account. It has a real account deposit processing unit 117 for processing.

The physical account deposit processing unit 117 further includes a changed remittance destination request data generation unit 117A, a physical account payment processing unit 117B, and a physical account payment notification unit 117C. With these other functions, even a person other than the person who opened the real account can safely and reliably transfer money to the user of the loan account who does not have a real account at the financial institution.

The changed remittance destination request data generation unit 117A converts the content of the remittance destination request data M from the remittance requester "Mio Furiko", who is not the account opener, into the account opening stored in the specific transaction store management table T2. It is a functional unit that changes the actual account information RA2 and the account holder name information AN2 of the person "Management Taro" and generates changed remittance destination request data MM.

Specifically, changed remittance destination request data generation unit 117A generates remittance destination branch number 303 and remittance destination store number 303 The remittance destination account number 306 and the recipient name 307 in the remittance destination name information TN are the actual account information in the specific transaction store management table T2 (Fig. 3(b)) of "Management Taro" who opened the actual account. It is changed according to the branch number 212B and the account number 212D of RA2 and the account holder 212 in the account holder information AN2, and the changed remittance destination request data MM is generated.

Based on the changed remittance destination request data MM generated by the changed remittance destination request data generation unit 117A, the physical account payment processing unit 117B generates the actual account table T1 (Fig. 3 ( a)) is a functional unit that performs the process of depositing money into the actual account. Specifically, based on the changed remittance destination request data MM, the physical account receipt processing unit 117B changes the remittance destination specified by the real account information RA1 of the real account table T1 of “Management Taro” who is the person who opened the real account. The remittance amount 308 "10,000" yen is received in the real account of the account number 306 "1234567".

When the physical account payment processing unit 117B executes the payment processing for the physical account "Management Taro" who established the physical account, the physical account payment notification unit 117C sends the payment to the physical account as shown in FIG. This is a functional unit that transmits the actual account receipt notification information N2 notifying that the money processing has been executed to the lending account holder "Jiro Yamada" who is the recipient.

Specifically, the actual account payment notifying unit 117C executes the payment processing of adding "10,000" (yen) to the actual account in the actual account table T1 based on the changed remittance destination request data MM described above. Then, based on the remittance requester information PN, remittance destination request information TR, remittee name information TN, and remittance amount information TA of the remittance destination request data M shown in FIG. 11, the actual account receipt notification information N2 shown in FIG. to generate Then, the actual account receipt notification unit 117C transmits the actual account receipt notification information N2 to "Jiro Yamada" who is the holder of the loan account via the Internet 5. FIG. That is, the actual account payment notification information N2 is transmitted to the user terminals 6A and 6B via the Internet 5 as the loan account deposit/withdrawal information described above. Incidentally, it is assumed that the actual account receipt notification unit 117C has previously recognized a contact address such as an e-mail address addressed to "Jiro Yamada" who is the holder of the loan account.

For example, a case where a remittance requester "Mio Furiko" who is not an account opener transfers money to a user "Jiro Yamada" who does not have a deposit account at a financial institution will be described in detail.

More specifically, the change remittance destination request data generation unit 117A of the physical account deposit processing unit 117 converts the contents of the remittance destination request data M from the remittance requester “Mio Furiko” shown in FIG. In order to change according to the contents of the actual account information RA2 in the specific transaction store management table T2 (Fig. 3(b)) of "Management Taro", the financial institution code 302 of the remittance request data M and the remittance destination store number 303, the deposit type 305, and the remittance destination account number 306 are replaced with the contents of the financial institution code 212A, branch number 212B, deposit type 212C, and account number 212D of the actual account information RA2. As a result, the changed remittance destination request data MM as shown in FIG. 11 is created. In the changed remittance destination request data MM, the remittance destination branch number 303 changes from "888" to "137", the deposit type 305 changes from "9" to "1", and the remittance destination account number 306 changes from "7788663" to "1234567". , and the recipient name 307 changes from "Jiro Yamada" to "Taro Kanri". The change remittance destination request data MM is transmitted to the bank server accounting system host 11 in FIG. Payment processing to the account is performed.

More specifically, the physical account deposit processing unit 117B of the physical account deposit processing unit 117 uses the remittance destination request information TR of the changed remittance destination request data MM generated by the changed remittance destination request data generation unit 117A shown in FIG. The amount specified by the remittance amount information TA of the changed remittance destination request data MM is deposited into the real account of "Taro Manager" who is the owner of the specified real account. The financial institution code 302 "1310", the remittance destination branch number 303 "137", the remittance destination account number 306 "1234567", and the recipient name 307 "Taro Taro" in the remittance request information TR of the changed remittance destination request data MM in FIG. , the actual account information RA1 of the actual account table T1 in FIG. is added to the balance (yen) 206 of the account specified by . As a result, the remittance amount 308 "10,000" yen is deposited in the real account of the remittance destination account number 306 "1234567" specified by the real account information RA1 of the real account table T1 shown in FIG. The actual account table T1 is in the state shown in FIG. 7(a). This completes the payment processing by the actual account payment processing unit 117B.

More specifically, when the payment processing in the physical account payment processing unit 117B is completed as described above, the physical account payment notification unit 117C of the physical account payment processing unit 117 sends, for example, the remittance destination request data M shown in FIG. remittance requester information PN including remittance requester 301 "Mio Furiko", financial institution code 302 "1310", remittance destination branch number 303 "888", order of destination 304 "1", deposit type 305 "9" ”, remittance destination request information TR including remittance destination account number 306 “7788663”, remittance destination name information TN including recipient name 307, and remittance amount information TA including remittance amount 308 “10,000” yen. The field of transaction date 501 “2017/08/29” of the account payment date information DA2 is added. Note that the actual account receipt notification unit 117C may be provided in the control unit 110 of the remittance support server 13, or may be provided in the notification server 16 separate from the remittance support server 13 as shown in FIG. .

Then, the actual account payment notification unit 117C transmits the created actual account payment notification information N2 to the lending account holder "Jiro Yamada" via the Internet 5. FIG. It is assumed that the actual account payment notification unit 117C has previously recognized a contact address such as an e-mail address addressed to "Jiro Yamada" who is the holder of the loan account.

In this way, by providing the actual account payment notification unit 117C and transmitting the actual account payment notification information N2 indicating that the payment processing for the physical account has been executed to the lending account holder "Jiro Yamada" , the lending account holder "Jiro Yamada" can know that money has been received from the remittance requester 301 "Mio Furiko" addressed to him ("Jiro Yamada") in the real account of "Taro Manager". Then, information on predetermined conditions for transferring the money addressed to him ("Jiro Yamada") deposited in the real account of "Taro Manager" to his own loan account is sent to the remittance support server 13 via the Internet 5. be able to.

As described in the description of the remittance support server 13 according to the first embodiment, the condition determination unit 115 of the remittance support server 13 determines whether or not the loan account satisfies a predetermined condition. The loan account destination transfer processing unit 116 performs processing only when it is determined that the conditions are satisfied.

Note that the physical account payment notification unit 117C may also transmit the physical account payment notification information N2 to "Management Taro" who is the account opener of the physical account. As a result, the money that arrived at the loan account holder (“Jiro Yamada” in this case) instead of himself (“Taro Management”), who is the account holder of the real account, can be withdrawn. It is possible to call attention not to do so.

In this way, in the actual account deposit processing unit 117, the remittance amount specified in the remittance destination request data from the remittance requester "Furuko Mio" to the loan account user "Yamada Jiro" is associated with the loan account. As shown in FIG. 7(a), the account number 204 "1234567" of the account holder 205 "Taro Management" in the actual account table T1 is changed by executing the payment processing to deposit the money into the physical account "Taro Management". When the actual account balance (yen) 206 reaches "10,000" yen, processing by the condition determination unit 115 and the loan account destination transfer processing unit 116 can be performed in the same manner as in the first embodiment described above.

Specifically, when the condition determination unit 115 determines that a predetermined condition is met, for example, receipt intention confirmation information (not shown) indicating the receipt intention of the loan account user “Jiro Yamada” is sent via the Internet. 5, transfer processing to the loan account is executed in the loan account destination transfer processing unit 116 . As a result of the transfer processing to the loan account, as shown in FIG. 7A, "10,000" is added to the balance (yen) 206 of the account number 204 "1234567" of the account holder 205 "Management Taro" in the actual account table T1. As shown in FIG. 7(b), 10,000 yen is subtracted from the balance (yen) 206 of the actual account (account number "1234567") in the actual account table T1 from the state where the yen exists, and the balance (yen) 206 becomes "0" yen. 10,000 yen is added to the balance (yen) 234A of the loan account (account number "7788663") of "Jiro Yamada" of the account holder 225 in the management table T3, resulting in "10,000" yen.

In this way, the lending account “7788663” linked to the real account “1234567” of “Taro Manager” is lent to “Jiro Yamada”, and then the remittance requester “Mio Furiko” opens a bank account at a financial institution. Remittance processing to user "Jiro Yamada" who does not have As a result, it becomes possible for the remittance requester "Mio Furiko", who is a person other than the person who opened the account, to "Jiro Yamada", a user who does not have an account at a financial institution.

In this case, the remittance request based on the remittance destination request data M from the remittance requester "Mio Furiko" is not directly transferred (remittance) to the loan account "7788663" lent to "Jiro Yamada". , the money is once deposited into the real account of "Management Taro" specified by the real account table T1. As a result, a remittance request from a remittance requester other than the person who opened the account, “Mio Furiko,” will be sent through the real account of “Mr. Since the payment is processed to the loan account of "Taro Yamada" who is recognized to have a certain level of trust due to what he has done, the risk of fraudulent remittance of funds can be reduced in advance for financial institutions.

FIG. 13 is a schematic flow chart for explaining other processing executed by the remittance support server 13 of FIG. The control unit 110 of the remittance support server 13, as described above in steps S1 to S4 in FIG. It is determined that the recipient name 307 "Jiro Yamada" of the remittee name information TN in the remitter request data M matches the account holder name 233A of the account name information AN3 in the loan account management table T3. Steps S11 to S13 in FIG. 13 may be executed after the transfer from the real account to the loan account in step S6.

In step S4 of FIG. 9, the control unit 110 of the remittance support server 13 determines that the recipient name 307 "Jiro Yamada" in the remittee name information TN in the remittance request data M is changed from the account name information AN3 in the loan account management table T3. If the controller 110 of the remittance support server 13 determines that it matches the account holder 233A (step S4: YES), the controller 110 of the remittance support server 13 transfers the contents of the remittance destination request data M from the remittance requester "Mio Furiko" to the specific transaction store management. It is changed according to the actual account information RA2 and the account holder name information AN2 of "Management Taro" who is the account opener stored in the table T2, and is generated as changed remittance destination request data MM (step S11).

Next, the control unit 110 of the remittance support server 13 creates a real account table T1 (Fig. 3(a)) for the person who established the real account, "Taro Taro", based on the changed remittance destination request data MM generated in step S11. ) is processed (step S12). As a result, the remittance amount 308 "10,000" is received in the real account of the remittance destination account number 306 "1234567" specified by the real account information RA1 of the real account table T1 of "Taro Manager" who opened the real account. 7A, 10,000 yen is added to the balance (yen) 206 of the real account 204 "1234567" stored in the real account table T1.

When the control unit 110 of the remittance support server 13 executes the payment processing for the physical account "Taro Manager", who is the owner of the physical account, in step S12, the payment processing for the physical account shown in FIG. 12 is executed. The actual account receipt notification information N2 for notifying that the payment has been received is transmitted to the lending account holder "Jiro Yamada" who is the recipient (step S13).

As a result, it becomes possible for the remittance requester "Mio Furiko", who is a person other than the person who opened the account, to "Jiro Yamada" who does not have an account at a financial institution.

<Other embodiments>
Another usage example in which a specific store number is registered in the specific transaction store management table T2 will be described. FIG. 14 is a diagram showing another usage example of the specific transaction store management table T2. In the loan account management table T3 of FIG. 3(c), the account number 232D is practically specified using six digits excluding the last check digit, so 999,999 for each specific store number. You can have one loan account. However, in a large group company, for example, a loan account is required for each of a large number of employees, and 999,999 loan accounts associated with one specific store number may not be sufficient. . In such a case, it is possible to manage loan accounts by assigning one actual account to two or more specific store numbers.

For example, "886", "887", and "888" are stored as the specific store number 211A in the specific transaction store management table T2, and the same actual account, that is, the financial institution code 212A is "1310". , the store number 212B is "137", the deposit type 212C is "1", and the account number 212D is "1234567". Corresponding to each specific store number 211A, a loan account specified by a 6-digit account number excluding the check digit is opened as described above. The first to 999,999th loan accounts are opened in association with the specific store number 211A "886", and the loan account information LA3 stored in the loan account management table T3 as shown in FIG. , financial institution code 232A, store number 232B, deposit type 232C, and account number 232D, in that order, "1310-886-9-000001X to 1310-886-0-999999X". In addition, the 1,000,000th to 1,999,998th loan accounts are associated with the specific store number 211A "887" and opened, and 999999X". Then, the specific store number 211A "888" is associated with the 1,999,999th to 2,999,997th lending accounts, and "1310-888-9-000001X to 1310-888-0- 999999X".

With such a configuration, even a large-scale group company may have only one real account, which is an account opened at a financial institution, and thus has the advantage of being easy to manage.

FIG. 15 is a diagram showing still another usage mode of the specific transaction store management table. A company with a small number of employees may not need 999,999 loan accounts. In such a case, instead of making a one-to-one correspondence between the specific shop number and the real account, one specific shop number may be associated with the real accounts of several companies or the like.

In the specific transaction shop management table T2 of FIG. 15, three real accounts are associated with the specific shop number 211A "888". That is, for the specific store number 211A "888", the financial institution code 212A is specified as "1310", the store number 212B as "137", the deposit type 212C as "1", and the account number 212D as "1234567". A real account identified by the financial institution code 212A of "1310", the branch number 212B of "137", the deposit type 212C of "1", and the account number 212D of "0987654", and the financial institution code 212A of It is associated with the real account identified by "1310", the branch number 212B of "137", the deposit type 212C of "1", and the account number 212D of "2233445".

In the case of the specific transaction store management table T2 of FIG. 15, the specific transaction store is specified by using the fact that the specific transaction store identification information SD2 includes the destination order 211B in addition to the specific store number 211A. . Therefore, each real account is assigned a different order of destination 211B. For example, in the specific transaction store management table T2 of FIG. 15, the actual account identified by the account number 212D of "1234567" is assigned the order of delivery 211B of "1" and the account number 212D of "0987654". The actual account identified by the account number 212D of "2233445" is assigned a sending order 211B of "3".

In this case, the remittance destination request data M shown in FIG. 6 or FIG. 11 stores, in the field of destination order 303, information specifying the order of delivery assigned to the real account that is the destination. As a result, since it is not necessary to assign specific branch numbers to companies with a small number of employees, the financial institution can allocate specific branch numbers without waste.

1 bank system 2 head office/branch system 3 Zengin network 4 Zengin server accounting system host 5 Internet 6A, 6B user terminal 7 ATM
10 bank server group 11 bank server accounting system host 12 communication server 13 remittance support server 13A store management database for specific transactions (DB)
13B Loan account management database (DB)
20A Actual account database (DB)
110 control unit 111 loan account name change unit 112 remittance destination request data reception unit 113 specific store information determination unit 114 loan account name information determination unit 115 condition determination unit 116 loan account destination transfer processing unit 117 actual account deposit processing unit 117A changed remittance destination Request data generation unit 117B Actual account payment processing unit 117C Actual account payment notification unit 120 Storage unit 130 Input unit 140 Output unit 150 Communication unit 160 Bus T1 Actual account table T2 Specific transaction store management table T3 Lending account management table M Remittance Destination request data MM Change remittance destination request data N1 Loan account receipt notification information N2 Actual account receipt notification information

Claims (9)

a specific transaction store management database that stores specific transaction store identification information given to a physical account designated and opened by a financial institution and actual account information that identifies the actual account;
a loan account management database storing a specific shop number included in the specific transaction shop identification information and loan account information specifying a loan account opened in association with the specific shop number;
a lending account name change unit that rewrites account name information of the lending account to user name information of the user according to the result of authentication processing for the user of the lending account;
Remittance destination request data including a remittance destination branch number that identifies a remittance destination store via a financial network that connects financial institutions, and recipient name information that identifies the recipient of the loan account that is the user. a remittance destination request data reception unit that receives
a specific store information determination unit that determines whether the remittance destination store number matches the specific store number;
a loan account name information determination unit that determines whether or not the recipient name information matches the user name information of the loan account when the specific store information determination unit determines that they match;
a loan account transfer processing unit that executes a transfer process from the actual account to the loan account based on the remittance destination request data when the loan account name information determination unit determines that there is a match ;
a physical account deposit processing unit that executes deposit processing for the physical account based on the remittance destination request data;
with
A remittance characterized in that, when the remittance requester information of the remittance request data is not the account opener of the real account, the physical account deposit processing unit executes deposit processing before executing the transfer processing. Support server. further comprising a condition determination unit that determines whether a predetermined condition for the loan account is satisfied;
2. The remittance support server according to claim 1 , wherein said loan account transfer processing unit executes transfer processing from said real account to said loan account when said predetermined condition is satisfied. 3. The remittance support server according to claim 2 , wherein said predetermined condition is acceptance of receiving intention confirmation information indicating said user's receiving intention. 3. The remittance support server according to claim 2 , wherein said predetermined condition is reception of payment permission confirmation information indicating permission of payment to said recipient by an account holder of said actual account. The physical account deposit processing unit
a changed remittance destination request data generation unit that generates changed remittance destination request data in which the remittance destination request data is changed in accordance with the actual account information;
2. The remittance support server according to claim 1 , further comprising a physical account payment processing unit for executing payment processing to said physical account based on said changed remittance destination request data. The physical account deposit processing unit
a physical account payment notification unit that, when the payment processing in the physical account payment processing unit is executed, transmits, to the recipient, physical account payment notification information notifying that the payment processing has been executed; 6. The remittance support server according to claim 5 , further comprising: a remittance support server according to any one of claims 1 to 6 ;
a user terminal communicably connected to the remittance support server via an information communication network, and transmitting/receiving loan account deposit/withdrawal information regarding deposit/withdrawal to/from the loan account with the remittance support server; , remittance support system. run by a computer,
a step of preparing a specific transaction store management database for storing specific transaction store identification information given to a specified real account opened in a financial institution and real account information specifying the actual account;
a step of preparing a loan account management database for storing a specific shop number included in the specific transaction shop identification information and loan account information specifying a loan account opened in association with the specific shop number;
a lending account name change step of rewriting account name information of the lending account to user name information of the user according to the result of authentication processing for the user of the lending account;
Via a financial communication network that connects financial institutions, the remittance destination branch number that identifies the remittance destination shop, and the recipient name information of the user that identifies the recipient of the loan account that is the user a remittance destination request data receiving step for receiving remittance destination request data including
a specific store information determination step of determining whether or not the remittance destination store number matches the specific store number;
If it is determined that the remittance destination store number matches the specific store number as a result of the determination in the specific store information determination step, whether or not the recipient name information matches the user name information of the loan account a loan account name information determination step for determining
If it is determined that the recipient name information matches the account name information of the lending account as a result of determination in the lending account name information determining step, a transfer from the actual account to the lending account is made based on the remittance destination request data. A loan account transfer processing step for executing transfer processing;
a physical account deposit processing step of executing deposit processing to the physical account based on the remittance destination request data;
with
A remittance characterized in that, in the actual account deposit processing step, the deposit processing is executed before the transfer processing is executed when the remittance requester information of the remittance request data is not the account opener of the physical account. how to help. a step of preparing a specific transaction store management database for storing specific transaction store identification information given to a specified real account opened in a financial institution and real account information specifying the actual account;
a step of preparing a loan account management database for storing a specific shop number included in the specific transaction shop identification information and loan account information specifying a loan account opened in association with the specific shop number;
a lending account name change step of rewriting account name information of the lending account to user name information of the user according to the result of authentication processing for the user of the lending account;
A remittance destination request that includes a remittance destination branch number that specifies a remittance destination store and a beneficiary name information that specifies the beneficiary of the above-mentioned loan account, which is the user, via a financial communication network that connects financial institutions. a remittance destination request data receiving step for receiving data;
a specific store information determination step of determining whether or not the remittance destination store number matches the specific store number;
If it is determined that the remittance destination store number matches the specific store number as a result of the determination in the specific store information determination step, whether or not the recipient name information matches the user name information of the loan account a loan account name information determination step for determining
If it is determined that the recipient name information matches the account name information of the lending account as a result of determination in the lending account name information determining step, a transfer from the actual account to the lending account is made based on the remittance destination request data. A loan account transfer processing step for executing transfer processing;
a physical account deposit processing step of executing deposit processing to the physical account based on the remittance destination request data;
with
In the actual account deposit processing step, when the remittance requester information of the remittance request data is not the account opener of the physical account, a remittance support method for executing deposit processing before executing the transfer processing is provided to the computer. program to run.

Images