JP6919149B2 - Information system and information processing method - Google Patents

Description

The present invention relates to an information processing device, an information processing method, an information processing program and an information system.

The remittance fee for remittance between accounts may vary depending on conditions such as the usage status of financial products provided by financial institutions and the amount of remittance. Furthermore, if the remittance sender has accounts at multiple financial institutions, the remittance fee may vary depending on the remittance source account selected as the remittance source. Therefore, a proposal system that proposes a remittance source account with a reduced remittance fee based on pre-registered conditions is disclosed (see, for example, Patent Documents 1-4).

Japanese Unexamined Patent Publication No. 2003-303284 Japanese Unexamined Patent Publication No. 2006-114003 Japanese Unexamined Patent Publication No. 2012-018655 Japanese Unexamined Patent Publication No. 2016-148970

As mentioned above, the remittance fee may vary depending on the usage status of financial products, but the usage status of financial products is not always the same. For example, a customer who used to use an investment trust and a mortgage may no longer use an investment trust. It is difficult to update the usage status registered in the proposal system every time there is a change in the usage status of financial products. In addition, if the usage status registered in the proposal system is not updated even though the usage status of financial products is changing, the remittance fee will be charged even if the remittance source account proposed by the proposal system is used. It may not be cheap. Furthermore, the remittance fee differs depending on whether the financial institution or branch of the remittance source account and the remittance destination account are the same. Therefore, when each of the person making the remittance and the person receiving the remittance has a plurality of accounts, it is difficult to confirm from which account to which remittance the remittance fee can be reduced. Since the remittance fee differs depending on the conditions at the time of remittance described above, it was difficult to confirm the remittance source account where the remittance fee is cheaper.

Therefore, one aspect of the disclosed technology is to provide an information processing device, an information processing method, and an information processing program that can propose a remittance source account in which the remittance fee is reduced even if the remittance fee fluctuates depending on the conditions at the time of remittance. The purpose is.

One aspect of the disclosed technology is exemplified by the following information processing apparatus. This information processing device is a storage means for storing the correspondence between the account information including the information that identifies the account held by the user and the financial institution that manages the account and the user information that identifies the user. The receiving means for receiving the proposal request including the designation of the user information from the requesting device, the acquisition means for acquiring the account information associated with the user information included in the proposal request by referring to the correspondence, and the acquisition means. Inquire the management server of the financial institution specified by the account information about the transfer fee when transferring from the account specified by the account information, and obtain the inquiry result including the transfer fee when transferring from the account specified by the account information. It includes an inquiry means and a transmission means for transmitting the inquiry result acquired from the management server to the requesting device.

According to such a technique, when the information processing device receives a proposal request including the designation of user information from the requesting device, the information processing device is associated with the user information by referring to the correspondence stored in the storage unit. Get the account information. This information processing device inquires about the remittance fee from the management server of the financial institution that manages the account specified by the acquired account information. When the information processing device acquires the inquiry result, it sends it to the requesting device. According to this information processing device, the remittance fee at the time when the proposal request is received can be obtained from the management server. Therefore, even if the remittance fee fluctuates, it is possible to confirm the account where the remittance fee is cheaper.

The disclosed technique may further have the following features: The remittance fee varies depending on the remittance conditions at the time of remittance, the proposal request includes the remittance condition information indicating the remittance conditions, and the inquiry means inquires the management server about the remittance fee according to the remittance conditions. According to such technology, even if the remittance fee fluctuates depending on whether the remittance source account and the remittance destination account are the same financial institution (or the same branch) and the remittance conditions such as the remittance amount, the remittance is remitted. You can check the account where the fee will be cheaper.

The disclosed technique may further have the following features: The remittance conditions include whether the remittance source account and the remittance destination account belong to the same group, and the proposal request specifies the remittance destination account to be the remittance destination as the remittance condition information and the remittance destination account belongs to. The inquiry means inquires the management server about the remittance fee to the account belonging to the group specified by the remittance destination account information, including the remittance destination account information that identifies the group. Here, the "group" is, for example, a financial institution or a branch office of a financial institution. According to such a technique, even if the remittance fee fluctuates depending on whether the remittance source account and the remittance destination account are the same financial institution (or branch office), it is possible to confirm the account in which the remittance fee is reduced.

The disclosed technique may further have the following features: The remittance condition includes the remittance amount, the proposal request includes the remittance amount to be remitted as the remittance condition information, and the inquiry means inquires the management server about the remittance fee when remittance of the remittance amount of funds. According to such a technique, even if the remittance fee fluctuates according to the remittance amount, it is possible to confirm the account in which the remittance fee is reduced.

The disclosed technique may further have the following features: The remittance destination account information includes the user information of the holder who holds the remittance destination account, and the acquisition means refers to the correspondence and obtains the account information associated with the user information included in the remittance destination account information. get. According to such a technique, even if the account number of the remittance destination account is unknown, the remittance destination account can be specified by the user information. In addition, even if the holder of the remittance destination account does not wish to disclose the account number, it is possible to remit using the user information.

The disclosed technique may further have the following features: The correspondence relationship further includes the remittance destination permission information indicating whether or not the account information can be used as the remittance destination account, and the acquisition means refers to the correspondence relationship and includes the user information included in the remittance destination account information. Acquires account information that is associated and indicates that the remittance destination permission information may be used as the remittance destination account. According to such a technique, remittance to an account that the account holder does not want to use as a remittance destination account is suppressed.

The disclosed technique may further have the following features: The correspondence further includes the remittance source permission information indicating whether or not the account information can be used as the remittance source account, and the acquisition means is the account indicating that the remittance source permission information can be used as the remittance source account. Get information. According to such a technique, remittance from an account that the account holder does not want to use as a remittance source account is suppressed.

The disclosed technique may further have the following features: The output means replaces the account information included in the inquiry result with the user information of the holder who holds the account specified by the account information, and transmits the inquiry result. According to such a technique, the privacy of the holder of the remittance destination account can be protected by not transmitting the account number of the remittance destination account.

The disclosed technique may further have the following features: The inquiry result includes the balance of the account specified by the account information. According to such a technique, the remittance source account can be determined in consideration of the balance of the account.

The disclosed technique may further have the following features: The transmission means transmits information that identifies the remittance source account with the lowest remittance fee among the acquired inquiry results to the requesting device. With such a technology, the user can easily grasp the remittance source account with the lowest remittance fee.

The disclosed technology can also be grasped as an information processing method, an information processing program, and an information system.

This information processing device can propose a remittance source account that can confirm an account in which the remittance fee is reduced even if the remittance fee fluctuates depending on the conditions at the time of remittance.

FIG. 1 is a diagram showing an example of the configuration of the remittance assistance system according to the first embodiment. FIG. 2 is a diagram showing an example of the hardware configuration of the information processing device. FIG. 3 is a diagram showing an example of a processing block of the remittance assistance system according to the first embodiment. FIG. 4 is a first diagram showing an example of the correspondence relationship between the customer ID managed by the contract management DB and the financial product. FIG. 5 is a diagram showing an example of a correspondence relationship between the usage status of financial products managed by the condition DB and the handling of remittance fees. FIG. 6 is a first diagram showing an example of the correspondence relationship between the customer ID managed by the fee management DB and the remittance fee. FIG. 7 is a diagram showing an example of the correspondence relationship between the user and the account managed by the user management DB. FIG. 8 is a diagram showing an example of a processing sequence of the remittance assistance system according to the first embodiment. FIG. 9 is a second diagram showing an example of the correspondence relationship between the customer ID managed by the contract management DB and the financial product. FIG. 10 is a second diagram showing an example of the correspondence relationship between the customer ID managed by the fee management DB and the remittance fee. FIG. 11 is a diagram showing an example of an output screen by the requesting device.

Hereinafter, embodiments will be described with reference to the drawings. The configurations of the embodiments shown below are examples, and the disclosed technology is not limited to the configurations of the embodiments.

<First Embodiment>
In the first embodiment, a remittance assistance system that proposes a remittance source account in which a remittance fee is reduced when any one of a plurality of accounts held by a customer is transferred to a remittance destination account as a remittance source account is exemplified. FIG. 1 is a diagram showing an example of the configuration of the remittance assistance system 1 according to the first embodiment. The remittance assistance system 1 includes management servers 11a, 11b, 11c installed in each of the financial institutions 10a, 10b, and 10c, an intermediary server 21, and a request source device 31 of the user A. User A is a customer who holds an account at the financial institution 10 and is also a user of the remittance assistance system 1. Financial institutions 10a, 10b, and 10c are collectively referred to as financial institution 10. The management servers 11a, 11b, and 11c are collectively referred to as the management server 11. The management server 11 and the requesting device 31 are connected to the intermediary server 21 by a computer network. In the first embodiment, Transmission is used as a communication protocol for a computer network.
Control Protocol / Internet Protocol (TCP / IP) is adopted, but it is not limited to this. In the first embodiment, a process of remittance by designating a remittance destination account from the remittance source account of the financial institution 10 held by the user A is exemplified. Although one request source device 31 and one user A are illustrated in FIG. 1, the request source device 31 and the user A may be plural.

The management server 11 is an information processing device that manages the user A, the account held by the user A at the financial institution 10, and the usage status of the account in association with each other. The association between the user A and the account is performed, for example, based on the customer ID that identifies each customer and the account number that identifies the account at the financial institution 10. The usage status of the account includes, for example, the balance of the account. The management server 11 further manages the usage status of the financial product used by the user A at the financial institution 10 in association with the user A. Examples of the usage status of financial products include whether or not salaries and pensions are received, whether or not utility charges are automatically deducted, whether or not a credit card issued by a financial institution 10 is held, and whether or not an investment trust is used.

The mediation server 21 is an information processing device that mediates the exchange between the management server 11 and the requesting device 31. The intermediary server 21 further manages the user A and the account held by the user A at each financial institution 10 in association with each other. When the intermediary server 21 receives the request for proposal including the designation of the remittance destination account from the requesting device 31, the intermediary server 21 outputs information indicating an account that can be remitted to the remittance destination account designated by the low remittance fee from the accounts held by the user A. It is transmitted to the requesting device 31.

The request source device 31 is an information processing device used by the user A. The requesting device 31 is, for example, a desktop personal computer (PC), a notebook PC, a tablet PC, a smartphone, a personal digital assistant (PDA), or a mobile phone. The requesting device 31 can access the intermediary server 21 via the computer network.

FIG. 2 is a diagram showing an example of the hardware configuration of the information processing apparatus 500. The information processing device 500 includes a Central Processing Unit (CPU) 501, a main storage unit 502, and an auxiliary storage unit 5.
03, includes communication unit 504 and connection bus B1. The CPU 501, the main storage unit 502, the auxiliary storage unit 503, and the communication unit 504 are connected to each other by the connection bus B1. The information processing device 500 can be used as a management server 11, an intermediary server 21, and a requesting device 31.

The CPU 501 is also called a microprocessor unit (MPU) or a processor. The CPU 501 is not limited to a single processor, and may have a multiprocessor configuration. Further, a single CPU 501 connected by a single socket may have a multi-core configuration. At least a part of the processing executed by the CPU 501 is performed by a processor other than the CPU 501, for example, a dedicated processor such as a Digital Signal Processor (DSP), a Graphics Processing Unit (GPU), a numerical arithmetic processor, a vector processor, or an image processing processor. You may. Further, at least a part of the processing executed by the CPU 501 may be executed by an integrated circuit (IC) or other digital circuit. again,
An analog circuit may be included in at least a part of the CPU 501. The integrated circuits are Large Scale Integrated Circuit (LSI) and Application Specific Integrated Circuit (AS).
IC), programmable logic device (PLD) included. The PLD includes, for example, a Field-Programmable Gate Array (FPGA). The CPU 501 may be a combination of a processor and an integrated circuit. The combination is called, for example, a microcontroller unit (MCU), a system-on-a-chip (SoC), a system LSI, a chipset, or the like. In the information processing device 500, the CPU 501 expands the program stored in the auxiliary storage unit 503 into the work area of the main storage unit 502, and controls the peripheral devices through the execution of the program. As a result, the information processing apparatus 500 can execute processing that meets a predetermined purpose. The main storage unit 502 and the auxiliary storage unit 503 are recording media that can be read by the information processing device 500.

The main storage unit 502 is exemplified as a storage unit that is directly accessed from the CPU 501. The main storage unit 502 includes a Random Access Memory (RAM) and a Read Only Memory (ROM).

The auxiliary storage unit 503 stores various programs and various data in a readable and writable recording medium. The auxiliary storage unit 503 is also called an external storage device. The auxiliary storage unit 503 stores an operating system (Operating System, OS), various programs, various tables, and the like. The OS includes a communication interface program that exchanges data with an external device or the like connected via the communication unit 504. External devices and the like include, for example, other information processing devices and external storage devices connected by a computer network or the like. The auxiliary storage unit 503 may be, for example, a part of a cloud system which is a group of computers on a network.

The auxiliary storage unit 503 is, for example, an Erasable Programmable ROM (EPROM), a Solid State Drive (SSD), or a hard disk drive (Hard Disk).
Drive, HDD), etc. Further, the auxiliary storage unit 503 is, for example, a Compact Disc (CD) drive device, a Digital Versatile Disc (DVD) drive device, a Blu-ray (registered trademark) Disc (BD) drive device, or the like. Further, the auxiliary storage unit 503 may be provided by Network Attached Storage (NAS) or Storage Area Network (SAN).

The communication unit 504 is, for example, an interface with a computer network. The communication unit 504 communicates with an external device via a computer network.

The information processing device 500 may further include, for example, an input unit that receives an operation instruction or the like from a user or the like. As such an input unit, an input device such as a keyboard, a pointing device, a touch panel, an acceleration sensor, or a voice input device can be exemplified.

The information processing device 500 may include, for example, an output unit that outputs data processed by the CPU 501 or data stored in the main storage unit 502. Examples of such an output unit include an output device such as a Cathode Ray Tube (CRT) display, a Liquid Crystal Display (LCD), a Plasma Display Panel (PDP), an Electroluminescence (EL) panel, an organic EL panel, or a printer.

<Processing block>
FIG. 3 is a diagram showing an example of a processing block of the remittance assistance system 1 according to the first embodiment. FIG. 3 shows an example of processing blocks of the management server 11, the intermediary server 21, and the requesting device 31 included in the remittance assistance system 1. The information processing device 500 realizes the processing block illustrated in FIG. 3 by the CPU 501 executing a computer program executably deployed in the main storage unit 502. Hereinafter, the processing block will be described with reference to FIG.

<Processing block of management server 11>
As illustrated in FIG. 3, the management server 11 includes an authentication processing unit 101, an inquiry unit 102, a management unit 103, a contract management DB 104, a condition DB 105, and a fee management DB 106.

The contract management DB 104 is a database that manages the correspondence between the customer ID that identifies the customer of the financial institution 10 and the financial product used by the customer identified by the customer ID. FIG. 4 is a diagram showing an example of the correspondence relationship between the customer ID managed by the contract management DB 104 and the financial product. The correspondence illustrated in FIG. 4 includes columns for "customer ID," "salary," "pension," "utility," "card," and "investment trust." The contract management DB 104 also includes columns for "account number" and "balance" of the customer's account identified by the customer ID.

Information indicating the usage status of financial products is stored in each column of "salary", "pension", "utility charge", "card", and "investment trust". The information indicating the usage status is, for example, a flag. When a flag is adopted as information indicating a usage status, for example, "1" is stored in each column when a contract is made, and "0" is stored in each column when a contract is not made.

In the "customer ID" column, a customer ID that identifies a customer at the financial institution 10 is stored. In the "salary" column, for example, "1" is stored when the salary receiving account is the account of the financial institution 10, and "0" is stored when it is not. In the "pension" column, for example, "1" is stored when the receiving account of the pension is the account of the financial institution 10, and "0" is stored when it is not. In the "utility charge" column, for example, "1" is stored when the account used for automatic withdrawal of utility charge is the account of the financial institution 10, and "0" is stored when the account is not. In the "card" column, for example, "1" is stored when the credit card issued by the financial institution 10 is contracted, and "0" is stored when the credit card is not contracted. In the "Investment trust" column, for example, "1" is stored when the investment trust is made using the account of the financial institution 10, and "0" is stored when the investment trust is not made. An account number that identifies an account is stored in the "account number" column. In the "balance", the balance of the account specified by the account number stored in the "account number" column is stored. For example, in FIG. 4, it can be seen that the customer with the customer ID “CCC” uses two financial products: receiving annuity and automatically withdrawing utility charges. Further, it can be seen that the customer with the customer ID "CCC" has an account with the account number "3333" and the balance is "300,025" yen.

The condition DB 105 is a database that manages the correspondence between the usage status of financial products and the handling of remittance fees. FIG. 5 is a diagram showing an example of a correspondence relationship between the usage status of the financial product managed by the condition DB 105 and the handling of the remittance fee. The correspondence illustrated in FIG. 5 includes columns for "cumulative points," "reductions," and "number of free remittances." The "cumulative points" column stores points calculated based on the usage status of financial instruments. For example, in the contract management DB 104, 1 point is added every time one of the flags of "salary", "pension", "utility charge", "card", and "investment trust" is set to on. Also, for example, if the balance of the account exceeds 1,000,000 yen, 1 point will be added. The "Reduction Width" column stores the amount to be reduced from the remittance fee. The "Free remittance count" column stores the number of times a month can be remitted with no remittance fee.

The fee management DB 106 is a database that manages the correspondence between the customer ID and the remittance fee when the customer identified by the customer ID remits. The fee management DB 106 is updated by the management unit 103 with reference to the contract management DB 104 and the condition DB 105. Figure 6
Is a diagram showing an example of a correspondence relationship between a customer ID managed by the fee management DB 106 and a remittance fee. The correspondence relationship illustrated in FIG. 6 includes columns of "customer ID", "internal fee", "external fee", "number of free remittances", and "remaining number of times". In the "customer ID" column, as in FIG. 4, a customer ID that identifies a customer at the financial institution 10 is stored. In the "internal fee" column, the remittance fee when both the remittance destination account and the remittance source account are the same financial institution 10 is stored. In the "external fee" column, the remittance fee when the remittance destination account and the remittance source account are different financial institutions 10 is stored. Even if the remittance source account and the remittance destination account belong to the same financial institution 10, the charges may differ depending on whether the remittance destination account and the remittance source account belong to the same branch. Then, for the sake of simplicity, if the remittance destination account and the remittance source account belong to the same financial institution 10, the "internal fee" will be applied regardless of whether or not they belong to the same branch. .. Similar to the "Free remittance count" column of the condition DB 105, the "Free remittance count" column stores the maximum number of remittances that can be remitted with no remittance fee per month. The "Remaining Count" column stores the remaining number of times in the current month when remittances can be made free of charge. In FIG. 6, for example, a customer with a customer ID “AAA” has a remittance fee of 0 yen when both the remittance destination account and the remittance source account are the same financial institution 10, and the remittance destination account and the remittance source account It can be seen that the remittance fee for different financial institutions 10 is 100 yen, and the remittance fee can be sent twice more this month without any remittance fee.

Returning to FIG. 3, the authentication processing unit 101 receives the authentication request from the intermediary server 21 and performs the authentication process. There is no limitation on the authentication processing method. The authentication process is performed by, for example, password authentication, OAuth 2.0, or the like.

The inquiry unit 102 inquires about the fee management DB 106 in response to an inquiry from the intermediary server 21 authenticated by the authentication processing unit 101, and transmits the inquiry result to the intermediary server 21.

The management unit 103 determines the remittance fee based on the balance of the account held by the customer and the usage status of the financial product, and updates the fee management DB 106. For example, the management unit 103 refers to the contract management DB 104 to acquire the usage status of the customer's financial product and the balance of the account identified by each customer ID. The management unit 103 calculates the points described with reference to FIG. 5 based on, for example, the usage status of the financial product acquired from the contract management DB 104 and the balance of the account. Based on the calculated points, the management unit 103 determines the amount of reduction in the remittance fee of the customer identified by each customer ID and the number of free remittances. Referring to FIGS. 4 and 5, for example, the customer specified by the customer ID "AAA" uses the financial products of "salary", "utility charge" and "card", and the "balance" is 1, Since it is more than 1,000,000 yen, the points are 4 points. As a result, the customer identified by the customer ID "AAA" can remit the remittance fee by 100 yen, and the remittance fee can be remitted four times per month. That is, the customer identified by the customer ID "AAA" will be charged a remittance fee from the fifth remittance per month, but the remittance fee will be reduced by 100 yen. In addition, the customer identified by the customer ID "BBB" does not use any of the financial products "salary", "pension", "utility charge", "card", "investment trust", and the balance of the account is also Since it is less than 1,000,000 yen, the point is 0 point. As a result, the customer identified by the customer ID "BBB" has a reduction of 0 yen in the remittance fee and 0 times of remittance without the remittance fee. The management unit 103 updates the fee management DB 106 based on the determined reduction amount of the remittance fee and the number of free remittances. For example, the management unit 103 executes such a process at a predetermined cycle (for example, once a day), so that even if there is a change in the balance of the account or the usage status of the financial product, the management unit 103 is based on the change. The fee management DB 106 can be updated. In addition, the management unit 103 also performs a process of reducing the "remaining number of times" of the fee management DB 106 by 1 when the customer remits once with no remittance fee.

<Processing block of requesting device 31>
As illustrated in FIG. 3, the requesting device 31 includes a requesting unit 301, a receiving unit 302, and an output unit 303.

The request unit 301 makes a login request to the intermediary server 21. The login request is made, for example, by password authentication using a user ID and a password. If the login is successful, the request unit 301 sends a request for proposal. The request for proposal is an instruction to request a proposal for a remittance source account at which the remittance fee is reduced by designating the user ID and the remittance destination account. The request for proposal includes a user ID and information that identifies the remittance destination account. The information that identifies the account in the first embodiment is, for example, a set of a financial institution ID and an account number that identifies a financial institution. The financial institution ID is, for example, a unified financial institution code that uniquely identifies a financial institution. The financial institution ID may be a set of a unified financial institution code and a branch code that uniquely identifies a branch within the financial institution. The request unit 301 is an example of a “request transmission means”. The user ID is an example of "user information".

The receiving unit 302 receives the proposal result from the intermediary server 21. The proposal results include remittance fee when remittance is made from each candidate of the remittance source account where the remittance fee is cheaper and each candidate of the remittance source account. The output unit 303 sorts the received proposal results in ascending order of remittance fee and outputs them to an output means such as a display. The receiving unit 302 is an example of the “result receiving means”.

Further, the request unit 301 accepts the designation of the remittance source account from the proposal result output by the output unit 303 by an input means such as a keyboard. The requesting unit 301 transmits a remittance instruction to the intermediary server 21 so as to perform remittance from the designated remittance source account. The remittance instruction includes information that identifies the remittance source account, information that identifies the remittance destination account, and the remittance amount. The request unit 301 is an example of "instruction means".

<Processing block of intermediary server 21>
As illustrated in FIG. 3, the intermediary server 21 includes a reception unit 201, an authentication request unit 202, a proposal unit 203, a remittance processing unit 204, and a user management DB 205.

The user management DB 205 is a database that manages the correspondence between the user who uses the intermediary server 21 and the account that the user holds in the financial institution 10. FIG. 7 is a diagram showing an example of a correspondence relationship between a user and an account managed by the user management DB 205. The correspondence illustrated in FIG. 7 includes columns for "user ID", "financial institution ID", and "account number". In the "user ID" column, an ID that identifies a user who uses the intermediary server 21 is stored. An ID that identifies the financial institution 10 is stored in the column of "financial institution ID". In the first embodiment, for example, the financial institution ID of the financial institution 10a is "001", the financial institution ID of the financial institution 10b is "002", and the financial institution ID of the financial institution 10c is "003". The account number is stored in the "account number" column. In FIG. 7, for example, the user with the user ID "111" is identified by the account with the account number "1111" of the financial institution 10a identified by the financial institution ID "001" and the financial institution ID "002". It can be seen that the financial institution 10b has an account with the account number "2011". The information stored in the user management DB 205 is registered, for example, at the time of initial registration when the user ID is paid out. Further, the information stored in the user management DB 205 can be changed at any time by logging in to the intermediary server 21 from the requesting device 31, for example. The user management DB 205 is an example of a “storage means”.

The reception unit 201 receives a login request from the request source device 31 and performs a login process. If the login is successful, the requesting device 31 can request the intermediary server 21 to propose a remittance source account with a low remittance fee. The reception unit 201 receives a proposal request from the requesting device 31 that has successfully logged in. The request for proposal includes, for example, a user ID, a remittance amount, and a remittance destination account. The reception unit 201 extracts a user ID from the received proposal request, and passes the extracted user ID to the authentication request unit 202 and the proposal unit 203. The reception unit 201 is an example of "reception means".

The authentication request unit 202 makes an authentication request to the management server 11 for inquiring about the remittance fee. The authentication request unit 202 extracts the user ID from the proposal request. The authentication requesting unit 202 refers to the user management DB 205 and acquires the financial institution ID and the account number associated with the extracted user ID. The authentication request unit 202 acquires the IP address of the management server 11 based on, for example, the correspondence between the financial institution ID and the IP address of the management server 11 (not shown). The authentication request unit 202 requests the management server 11 for authentication based on the acquired IP address. Authentication is performed by, for example, password authentication or OAuth 2.0 as described above.

The proposal unit 203 inquires about the remittance fee to the management server 11. The proposal unit 203 refers to the user management DB 205 and acquires the financial institution ID and the account number associated with the user ID passed from the reception unit 201. The proposal unit 203 acquires the IP address of the management server 11 based on the correspondence between the financial institution ID and the IP address of the management server 11 (not shown). The remittance fee varies depending on, for example, whether or not the remittance source account and the remittance destination account are the same financial institution (or the same branch), and the remittance conditions such as the remittance amount. Therefore, the proposal unit 203 inquires the management server 11 about the remittance fee based on the remittance conditions such as the acquired IP address, account number, and remittance amount of the management server 11. The intermediary server 21 makes inquiries to the management server 11 of a financial institution by using, for example, scraping to acquire information from a website or an application programming interface (API) published to allow access from the outside. Can be carried out. The proposal unit 203 determines one or a plurality of remittance source account candidates for which the remittance fee is reduced based on the inquiry result received from the management server 11. The proposal unit 203 notifies the requesting device 31 of the proposal result including the information indicating the determined candidate of the remittance source account. Proposal unit 203 is an example of “acquisition means”, “inquiry means”, and “transmission means”. The account number is an example of "remittance destination account information".

The remittance processing unit 204 performs remittance processing in accordance with the remittance instruction from the requesting device 31. The remittance instructions include the designation of the remittance source account, the remittance destination account and the remittance amount. The remittance processing unit 204 is an example of the “requesting means”.

<Processing sequence>
FIG. 8 is a diagram showing an example of a processing sequence of the remittance assistance system 1 according to the first embodiment. In FIG. 8, for example, a case of remittance to the account of the financial institution 10c (financial institution ID “003”) with the account number “3333” is illustrated. Hereinafter, an example of the processing sequence of the remittance assistance system 1 according to the first embodiment will be described with reference to FIG.

In M1, the management unit 103 of the management servers 11a and 11b updates the fee management DB 106 at a predetermined cycle. That is, the information stored in the fee management DB 106 fluctuates according to the usage status of the customer's financial product and the balance of the account.

In OP1, the requesting unit 301 of the requesting device 31 transmits a user ID and a password to the intermediary server 21 to make a login request. Here, for example, it is assumed that "111" is transmitted as the user ID. The reception unit 201 of the intermediary server 21 executes the login process based on the received user ID and password.

In OP2, the requesting unit 301 of the requesting device 31 that has successfully logged in is the user ID "11.
1 ”and the account number of the remittance destination account are specified, and a request for proposal requesting a proposal for the remittance source account at which the remittance fee is reduced is transmitted to the intermediary server 21. The reception unit 201 of the intermediary server 21 that has received the proposal request extracts the user ID from the received proposal request, and passes the extracted user ID to the authentication request unit 202 and the proposal unit 203.

In OP3, the authentication request unit 202 of the intermediary server 21 refers to the user management DB 205 and specifies the financial institution ID and the account number associated with the user ID passed from the reception unit 201. Here, the user ID "111" is specified. For example, when the user management DB 205 is in the state illustrated in FIG. 7, the account number "1111" of the financial institution ID "001" and the account number "2011" of the financial institution ID "002" are specified.

In OP4, the authentication request unit 202 of the intermediary server 21 requests authentication from the management server 11 of the financial institution 10 identified by the financial institution ID specified in OP3. If the authentication is successful, the proposal unit 203 of the intermediary server 21 inquires the management server 11 about the remittance fee. The inquiry includes the account number of the remittance source account and the remittance destination account number. Here, for the management server 11a of the financial institution 10a (financial institution ID "001"), the remittance source account is the account of the financial institution 10a account number "1111", and the remittance destination account is the financial institution 10c (financial institution ID "001"). Inquiries about the remittance fee will be made when the account number "3333" ("003") is used. In OP5, for the management server 11b of the financial institution 10b (financial institution ID "002"), the remittance source account is the account of the financial institution 10b account number "2011", and the remittance destination account is the financial institution 10c (financial institution ID "002"). An inquiry is made about the remittance fee when the account number "3333" ("003") is used.

Here, it is assumed that the contract management DB 104 owned by the management server 11a of the financial institution 10a (financial institution ID "001") is in the state illustrated in FIG. Further, it is assumed that the contract management DB 104 possessed by the management server 11b of the financial institution 10b (financial institution ID "002") is in the state illustrated in FIG. Further, it is assumed that the fee management DB 106 possessed by the management server 11a of the financial institution 10a (financial institution ID "001") is in the state illustrated in FIG. Further, it is assumed that the management server 11b of the financial institution 10b (financial institution ID "002") has the fee management DB 106 in the state illustrated in FIG. Here, since the management server 11a and the management server 11b belong to different financial institutions 10, the fee management DB 106 illustrated in FIG. 10 has different contents from the condition DB 105 illustrated in FIG. 5 (that is, finance). It is determined based on the condition DB) determined by the institution 10b. In OP6, the inquiry unit 102 of the management server 11a acquires the customer ID “AAA” associated with the account number “1111” received in OP4 by referring to the contract management DB 104 exemplified in FIG. The inquiry unit 102 acquires information on the remittance fee of the customer specified by the customer ID “AAA” acquired in OP6 with reference to the fee management DB 106 illustrated in FIG. Here, since the remittance destination account is not the account of the financial institution 10a, the inquiry unit 102 can determine that the remittance fee to be applied is an external fee. Therefore, the inquiry unit 102 does not have to acquire the information on the internal fee when acquiring the information on the remittance fee. Therefore, in OP6, as information on the remittance fee, it is acquired that the external fee is 100 yen and the remaining number of free remittances is two. In OP7, the proposal unit 203 of the intermediary server 21 transmits the information of the remittance fee acquired in OP6 to the intermediary server 21.

In OP8 and OP9, the same processing as in OP6 and OP7 is performed by the management server 11b, respectively. That is, in OP8, the inquiry unit 102 of the management server 11b refers to the contract management DB 104 exemplified in FIG. 9 and acquires the customer ID “ZZZ” associated with the account number “2011” received in OP5. .. The inquiry unit 102 acquires information on the remittance fee of the customer specified by the customer ID “ZZZ” acquired in OP8 with reference to the fee management DB 106 illustrated in FIG. That is, in OP8, as information on the remittance fee, it is acquired that the external fee is 100 yen and the remaining number of free remittances is 0. In OP9, the proposal unit 203 of the intermediary server 21 transmits the information of the remittance fee acquired in OP8 to the intermediary server 21.

In OP10, the proposal unit 203 of the intermediary server 21 transmits the remittance fee for each remittance source account based on the remittance fee information received in OP7 and OP9. As mentioned above, external fees apply to remittances from any remittance source account. Therefore, when the proposal unit 203 compares the external fees of the received remittance fee information, as described above, if the account of the financial institution 10a is the remittance source account, it is 0 yen, but the account of the financial institution 10b is the remittance source account. Then it will be 100 yen. In addition, at the financial institution 10a, the remaining number of free remittances remains twice. Therefore, the proposal unit 203 includes a set of information of the financial institution ID "001", the account number "1111", the external fee "0 yen", the remaining number of free remittances "2", the financial institution ID "002", and the account number "002". The proposal result including the information set of "2011", the external fee "100 yen", and the remaining number of free remittances "0" is transmitted to the requesting device 31.

In OP11, the output unit 303 of the requesting device 31 outputs the proposal result received in OP10 to, for example, a display connected to the requesting device 31. For example, as illustrated in FIG. 11, the output unit 303 may output to the display in order from the remittance source account in which the remittance fee becomes cheaper. The user of the requesting device 31 selects the remittance source account based on the information output on the display. In OP12, the requesting device 31 transmits a remittance instruction to the intermediary server 21 so as to perform remittance from the remittance source account selected by the user of the requesting device 31. The remittance instruction includes, for example, information that identifies the remittance source account, information that identifies the remittance destination account, and the remittance amount. Here, the financial institution ID "001" and the account number "1111" are specified as the information for specifying the remittance source account, and the financial institution ID "003" and the account number "3333" are specified as the information for specifying the remittance destination account. It shall be. In addition, it is assumed that 10,000 yen is specified as the remittance amount.

In OP13, the remittance processing unit 24 of the intermediary server 21 extracts the financial institution ID “001” and the account number “1111” as the information for identifying the remittance source account from the remittance instruction received in OP12. In addition, the remittance processing unit 24 extracts the financial institution ID "003" and the account number "3333" as the information for identifying the remittance destination account from the remittance instruction received in OP12, and extracts the remittance amount of 10,000 yen. do. The remittance processing unit 24 sends the financial institution ID "001", the financial institution ID "003", and the account to the management server 11a of the financial institution 10a (financial institution ID "001") from the account specified by the financial institution ID "001" and the account number "1111". Request to send 10,000 yen to the account specified by the number "3333". In OP14, the management server 11a is specified by the financial institution ID "003" and the account number "3333" from the account specified by the financial institution ID "001" and the account number "1111" according to the request received in the OP13. Send 10,000 yen to your account.

When the authentication between the intermediary server 21 and the management server 11 in OP4 is performed by, for example, OAuth2.0, the intermediary server 21 makes an inquiry or a processing request to the management server 11. , The token obtained at the time of OAuth 2.0 authentication should also be sent.

<Effect of the first embodiment>
In the first embodiment, the management server 11 manages the usage status of the financial product by each customer by the contract management DB 104. The management server 11 has updated the fee management DB 106 based on the usage status of financial products by each customer managed by the contract management DB 104. The fee management DB 106 is updated at predetermined intervals. Therefore, the remittance fee fluctuates based on the usage status of financial products by customers. In the first embodiment, when the intermediary server 21 receives the proposal request from the request source device 31, the intermediary server 21 acquires the financial institution ID and the account number of the account held by the user who made the proposal request from the user management DB 205. The intermediary server 21 inquires about the remittance fee to the management server 11 of the financial institution 10 specified by the acquired financial institution ID. The information indicating the remittance fee obtained by the inquiry is transmitted from the intermediary server 21 to the requesting device 31, and is displayed on the display of the requesting device 31, for example. Therefore, according to the first embodiment, even if the remittance fee fluctuates due to the fluctuation in the usage status of the financial product used by the customer, the intermediary server 21 uses the remittance fee at the time when the request source device 31 requests the proposal. Information can be presented.

In the first embodiment, the requesting device 31 displays the information indicating the received remittance fee in order from the remittance source account in which the remittance fee becomes cheaper. Therefore, according to the first embodiment, it is possible to easily identify the remittance source account at which the remittance fee is reduced.

<Modification example>
In the first embodiment, the remittance destination account is specified by a set of a financial institution ID and an account number. However, the remittance destination account may be identified by another means. For example, when the holder of the remittance destination account uses the intermediary server 21, the user ID of the holder who holds the remittance destination account may be used instead of the pair of the financial institution ID and the account number. .. As described with reference to FIG. 7, the intermediary server 21 can specify the account based on the user ID. Therefore, it is possible to specify the remittance destination account by the user ID of the holder who holds the remittance destination account. In this case, the intermediary server 21 may replace the account number of the remittance destination account with the user ID of the holder of the remittance destination account in the proposal result and transmit it to the requesting device 31. Further, in this case, when the requesting device 31 displays the output screen illustrated in FIG. 11, the remittance destination account information is replaced with the set of the financial institution ID and the account number, and the remittance destination account is used. The user ID of the holder may be displayed. By not displaying the financial institution ID or account number as the remittance destination information, the privacy of the remittance destination account holder can be protected. Further, instead of the user ID, the public ID associated with the user ID may be used instead of the pair of the financial institution ID and the account number. The public ID is an ID that cannot be used for logging in to the intermediary server 21, and the intermediary server 21 can specify the account by the user ID associated with the public ID. By using the public ID, it is not necessary to tell the user ID used for login to others, so that security is improved.

Further, flag information indicating whether or not the remittance source account may be used may be added to the user management DB 205. Further, when the remittance destination account is specified by the user ID of the holder of the remittance destination account, flag information indicating whether or not the remittance destination account may be used may be added to the user management DB 205. .. In this case, the account with the flag indicating that it is not used as the remittance source account is excluded from the remittance source account, and the account with the flag indicating that it is not used as the remittance destination account is excluded from the destination account. With such a configuration, remittance from an account that does not want to be used as a remittance source account or remittance to an account that does not want to be used as a remittance destination account is suppressed. The flag information indicating whether or not it can be used as a remittance source account is an example of "remittance source permission information". The flag information indicating whether or not it can be used as a remittance destination account is an example of "remittance destination permission information".

In the first embodiment, the intermediary server 21 transmits not only the information of the remittance source account having the lowest remittance fee but also the information of other remittance source accounts to the requesting device 31. However, the intermediary server 21 may, for example, transmit only the information of the remittance source account with the lowest remittance fee to the requesting device 31.

In the first embodiment, when the requesting device 31 receives the information about the remittance source account from the intermediary server 21, it outputs not only the information of the remittance source account with the lowest remittance fee but also the information of other remittance source accounts on the display. However, the requesting device 31 may output only the information of the remittance source account that has the lowest remittance fee among the received information of the remittance source account to the display.

In the first embodiment, the intermediary server 21 acquires information indicating the remittance fee of each remittance source account from the management server 11. However, the intermediary server 21 may acquire information such as the balance of each remittance source account and conditions related to remittance, in addition to the information indicating the remittance fee of each remittance source account. The conditions for remittance are, for example, the time required for remittance and the remittance limit. The time required for remittance is, for example, real-time remittance is possible if the remittance is within the same financial institution, the next business day if the remittance is to another financial institution in Japan, or remittance to an overseas financial institution. Then it may be a few days. Also, depending on the financial institution, the maximum amount of remittance that can be sent at one time may differ. The intermediary server 21 transmits the acquired information to the requesting device 31. The requesting device 31 may also display the information acquired from the intermediary server 21 on the output screen illustrated in FIG. With such a configuration, the user can determine the remittance source account in consideration of the balance of the account and the conditions related to the remittance.

In the first embodiment, one account is designated as the remittance destination account, but a plurality of remittance destination accounts may be designated. The designation of a plurality of remittance destination accounts may be performed, for example, by designating a plurality of account numbers, designating user IDs associated with the plurality of accounts, and the like. When a plurality of remittance destination accounts are specified, the intermediary server 21 may acquire information indicating a remittance fee for each combination of the remittance source account and the remittance destination account.

In the first embodiment, as illustrated in FIG. 11, the proposal results are output in ascending order of remittance fee. However, the output of the proposal result is not limited to the method of outputting in ascending order of remittance fee. For example, the intermediary server 21 stores the number of times the remittance source account has been used as the remittance source account for each account, and when there are a plurality of remittance source accounts having the same remittance fee, the remittance source account that has been used many times is used. It may be output with priority.

In the first embodiment, the inquiry of the remittance fee made from the intermediary server 21 to the management server 11 includes the designation of the remittance destination account. However, the remittance fee inquiry does not have to include the designation of the remittance destination account. In this case, the intermediary server 21 receives both the external fee and the internal fee from the management server 11. The intermediary server 21 remits the remittance source account and the remittance based on whether or not the financial institution ID included in the account information that identifies the remittance source account and the financial institution ID included in the account information that identifies the remittance destination account match. It is determined whether or not the destination account is the same financial institution 10 account. The intermediary server 21 may transmit information conforming to the determination to the requesting device 31.

In the first embodiment, the remittance fee fluctuates depending on whether or not the remittance source account and the remittance destination account are the same financial institution. However, the remittance fee may vary even if the remittance source account and the remittance destination account are the same financial institution or if the branches are different. The remittance fee may also vary depending on, for example, the amount of remittance. The requesting device 31 may include information indicating the remittance conditions at the time of remittance in the request for proposal. The information indicating the remittance conditions may include, for example, information indicating the financial institution or branch to which the remittance destination account belongs as well as specifying the remittance destination account and the remittance amount. The intermediary server 21 can confirm the remittance fee according to the remittance condition by receiving the proposal request including the information indicating the remittance condition. The information indicating the remittance condition is an example of "remittance condition information".

In the first embodiment, as illustrated in FIG. 5, the amount of reduction in the remittance fee and the number of free remittances fluctuate according to the cumulative number of points accumulated depending on the usage status of the financial product. However, the amount of reduction in the remittance fee and the fluctuation in the number of free remittances are not limited to the cumulative number of points. For example, the amount of reduction in the remittance fee and the number of free remittances may vary depending on the stage to which the user A belongs. The stage may be promoted according to the cumulative number of points, for example, or the stage may be promoted when certain conditions (for example, a mortgage contract, use as a payroll account) are met.

In the first embodiment, in the contract management DB 104, 1 point is added for each additional use of the financial product. That is, in the first embodiment, the points to be added are set equally for all financial instruments. However, the points to be added may be set differently for each financial product. For example, 3 points may be added when contracting an investment trust, 2 points may be added when using an account to receive salary, and 1 point may be added when using an account to pay utility bills. Furthermore, for example, if an investment trust is contracted, the remittance fee may be free regardless of the current points.

In the first embodiment, the amount of reduction of the remittance fee according to the accumulated points and the number of times the remittance fee becomes free per month are managed by the condition DB 105. The information managed by the condition DB 105 is not limited to this, and the reduction range of the remittance fee according to the accumulated points may be managed without managing the number of times the remittance fee is free. As a result of the reduction of the remittance fee increasing according to the accumulated points, the remittance fee may be free.

In the first embodiment, the intermediary server 21 proposes a remittance source account in which the remittance fee is reduced, but the content of the proposal is not limited to the remittance source account. For example, the intermediary server 21 acquires the point information held by the user and the information stored in the condition DB 105 from the management server 11, and charges the remittance fee based on the acquired point information and the information stored in the condition DB 105. Conditions that can be further reduced may be detected and the detected conditions may be presented. For example, when the intermediary server 21 detects that the remittance fee is further reduced by the points added by contracting the credit card issued by the financial institution, the remittance fee is further reduced by contracting the credit card. You may suggest to the user what you can do.

The embodiments and modifications disclosed above can be combined with each other.

<< Computer-readable recording medium >>
An information processing program that enables a computer or other machine or device (hereinafter, computer or the like) to realize any of the above functions can be recorded on a recording medium that can be read by the computer or the like. Then, the function can be provided by causing a computer or the like to read and execute the program of this recording medium.

Here, a recording medium that can be read by a computer or the like is a recording medium that can store information such as data and programs by electrical, magnetic, optical, mechanical, or chemical action and can be read from the computer or the like. To say. Among such recording media, those that can be removed from a computer or the like include, for example, a flexible disc, a photomagnetic disc, a Compact Disc Read Only Memory (CD-ROM), a Compact Disc --Recordable (CD-R), and a Compact Disc --ReWriterable. (CD-RW), Digital Versatile Disc (DVD), Blu-ray Disc (BD), Digital Audio Tape (DAT), 8 mm tape, memory cards such as flash memory and the like. In addition, there are hard disks, ROMs, and the like as recording media fixed to computers and the like.

1 ... Remittance assistance system 10, 10a, 10b, 10c ... Financial institution 11, 11a, 11b, 11c ... Management server 20 ... Broker 21 ... Broker server 31 ... Request source device 101 ・ ・ ・ Authentication processing unit 102 ・ ・ ・ Inquiry department 103 ・ ・ ・ Management department 104 ・ ・ ・ Contract management DB
105 ... Condition DB
106 ・ ・ ・ Fee management DB
201 ・ ・ ・ Reception Department 202 ・ ・ ・ Authentication Request Department 203 ・ ・ ・ Proposal Department 204 ・ ・ ・ Remittance Processing Department 205 ・ ・ ・ User Management DB
301 ・ ・ ・ Request part 302 ・ ・ ・ Reception part 303 ・ ・ ・ Output part 500 ・ ・ ・ Information processing device 501 ・ ・ ・ CPU
502 ... Main storage unit 503 ... Auxiliary storage unit 504 ... Communication unit B1 ... Connection bus

Claims (4)

An information system that includes an information processing device, a management server prepared for each financial institution, and a requesting device.
The information processing device
With respect to the account held by the user, a storage means for storing the correspondence between the account information including the information for specifying the account and the financial institution that manages the account and the user information for identifying the user, and
A receiving means for receiving a proposal request including a designation of the user information from the requesting device, and
With reference to the correspondence, an acquisition means for acquiring the account information associated with the user information included in the request for proposal, and
When remittance fee for remittance from the account specified by the account information is inquired to the management server of the financial institution specified by the account information, and remittance is made from the account specified by the account information. Inquiry means to get the inquiry result including the remittance fee of
A transmission means for transmitting the inquiry result acquired from the management server to the requesting device is provided.
The management server
Upon receiving the inquiry, a management means for determining a remittance fee that varies depending on the usage status of the user for a financial product provided by the specified financial institution, and
It is provided with an inquiry means for returning the determined remittance fee to the information processing device.
The requesting device is
A request transmission means for transmitting a proposal request including the designation of the user information to the information processing device, and
The result receiving means for receiving the inquiry result and
An output means for outputting the received inquiry result is provided.
Information system. The output means outputs the account information having the lowest remittance fee among the plurality of account information included in the inquiry result according to the designation from the user.
The information system according to claim 1. The requesting device receives the designation of the account information to be used as the remittance source account among the account information output by the output means, and issues a remittance instruction including the designated account information and the designation of the remittance destination account. Further equipped with an instruction means to send to the information processing device,
The information processing device
Upon receiving the remittance instruction, the remittance is sent to the management server of the financial institution specified by the account information included in the remittance instruction, using the account specified by the account information included in the remittance instruction as the remittance source account. Further equipped with requesting means to request remittance to the destination account,
Information system according to claim 1 or 2. It is an information processing method executed by an information system including an information processing device, a management server prepared for each financial institution, and a requesting device.
The information processing device
For the account held by the user, a memory that stores in the storage unit the correspondence between the account information including the information that identifies the account and the financial institution that manages the account and the user information that identifies the user. Steps and
A reception step for receiving a proposal request including designation of the user information from the request source device, and
With reference to the correspondence, an acquisition step of acquiring the account information associated with the user information included in the request for proposal, and
When remittance fee for remittance from the account specified by the account information is inquired to the management server of the financial institution specified by the account information, and remittance is made from the account specified by the account information. Inquiry steps to get inquiry results, including remittance fees, and
A transmission step of transmitting the inquiry result acquired from the management server to the requesting device is executed.
The management server
Upon receiving the inquiry, a management step of determining a remittance fee that varies depending on the usage status of the user for the financial product provided by the specified financial institution, and
The inquiry step of returning the determined remittance fee to the information processing device is executed.
The requesting device
A request transmission step of transmitting a proposal request including the designation of the user information to the information processing device, and
The result receiving step for receiving the inquiry result and
The output step of outputting the received inquiry result and the execution of
Information processing method.

Images