Financial-related information management device, financial-related information management system, control method for financial-related information management device, and control program for financial-related information management device

Abstract

To provide a finance-related information managing apparatus, etc. which allows a business operator to construct a network, etc. with a financial institution easily at low costs.SOLUTION: The present invention is directed to a finance-related information management apparatus 40 arranged such that registration-related information necessary for a user to have transaction with a business operator has general registration-related information and financial institution identification information that is identification information relating to a financial institution, the general registration-related information is transmitted through a business operator management apparatus to a finance-related information management apparatus, the financial institution identification information is transmitted to the finance-related information management apparatus not through the business operator management apparatus, transmission information for a financial institution that the financial institution can receive is generated based on the registration-related information and transmission information for a business operator that the business operator can receive is generated based on the information received from the financial institution.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a financial-related information management device that manages financial-related information between business operators and financial institutions, a financial-related information management system, a control method for a financial-related information management device, and a control program for a financial-related information management device. [Background technology]

[0002] In recent years, systems for purchasing goods and the like using electronic currency and the like have become widespread (for example, Patent Document 1, etc.). In many cases, such electronic currency systems are provided to users by businesses other than financial institutions such as banks. Furthermore, in order for a user to charge electronic currency or the like, it is necessary to associate the user's account at a financial institution or the like with the user's electronic currency or the like in advance. In order to make such an association, the business operator must individually establish communication between its own server and the server of the financial institution in accordance with the API (Application Programming Interface) that the financial institution itself publishes. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-51279 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, since the APIs of each financial institution are different, businesses have to build individual networks etc. to match the APIs of the different financial institutions with which their customers (users) do business, which poses the problem of huge construction costs.

[0005] Therefore, the present invention aims to provide a financial-related information management device, a financial-related information management system, a control method for a financial-related information management device, and a control program for a financial-related information management device that allow business operators to easily and at low cost to build networks with financial institutions.

[0006] The object of the present invention is to provide a service providing system that provides a service providing service to a user terminal device, a service providing service providing device that provides communication with the user terminal device, and a service providing service providing device that provides communication with the user terminal device. side A financial-related information management device that manages financial-related information between a management device and a financial institution side management device which is a management device of a financial institution, wherein registration-related information required for a user to transact with a business includes general registration-related information which is general registration-related information and financial institution identification information which is identification information related to a financial institution, the general registration-related information is transmitted to the financial-related information management device via the business side management device, and the financial institution identification information is transmitted to the financial-related information management device without passing through the business side management device, and further generates financial institution-directed transmission information which can be received by a financial institution based on the registration-related information, ,gold Generate business-oriented transmission information receivable by the business based on the information received from the financial institution. The identification information relating to the financial institution includes a password for the user's financial institution and account balance information for the user's financial institution, and when the terminal device executes a charge to increase electronic currency, the connection is automatically changed from the business-side management device to the financial-related information management device when the password is input, and when the charge is completed, a completion signal is transmitted from the terminal device to the business-side management device, and then the charge-related information is provided to the business-side management device. The object of the present invention is achieved by a financial-related information management device.

[0007] According to the above configuration, financial institution-oriented transmission information receivable by financial institutions is generated based on the registration-related information, and business-oriented transmission information receivable by businesses is generated based on the information received from the financial institution. In this way, when a business entity transmits information to a financial institution, the financial-related information management device The financial institution's management device creates and transmits information such as a message that can be received. Furthermore, when a financial institution transmits information to a business operator, the financial-related information management device creates and transmits information such as a message that can be received by the business operator's management device. In this way, the financial-related information management device transmits information in the form of telegrams or the like that can be received by both the financial institution side management device and the business operator side management device, so that the business operator side management device and the financial institution side management device can exchange information with each other as is, without any changes to the existing network system, etc. For example, since each financial institution side management device employs a different API (Application Programming Interface), the business operator side management device needs to build a network that is compatible with each different API in order to communicate with each financial institution side management device. In contrast, in the present invention, the financial-related information management device generates messages etc. that are tailored to the API of each financial institution's management device, so that the business operator's management device does not need to build networks tailored to different APIs in order to communicate with each financial institution's management device, and conventional networks etc. can be used as is, resulting in significant cost reduction.

[0008] In addition, according to the above configuration, financial institution identification information such as a user's PIN number and balance information is transmitted to the financial-related information management device without going through the business management device, so that financial institution identification information such as this PIN number and balance information will not be leaked to the business. This makes it possible to prevent the spread of financial institution identification information such as PIN numbers and balance information, and thus stabilize the level of security, making the device very safe for users. Furthermore, according to the above configuration, information such as the result of a charge transaction can be provided to the business operator without the user having to disclose the user's PIN to the business operator, making the device highly secure for users, etc.

[0009] Preferably ,gold the financial-related information management device based on matching information of the password at the financial institution, the balance information of the user received from the financial institution, and the balance information input by the user. The electricity The present invention is characterized in that it is configured to determine whether or not use of the child currency is permitted.

[0010] According to the above configuration, based on the matching information of the password information at the financial institution, the balance information of the user received from the financial institution, and the matching information of the balance information input by the user, , electric Since the system is configured to determine whether or not the child currency can be used, it is possible to reliably authenticate the identity of the user, etc.

[0013] Preferably, when withdrawal request information for withdrawing electronic currency into legal tender is input to the terminal device, the financial-related information management device causes the financial institution side management device to execute the withdrawal request information.

[0014] According to the above configuration, when withdrawal request information for withdrawing electronic currency into legal tender is input to the terminal device, the financial-related information management device executes the withdrawal request information to the financial institution side management device. Therefore, since the business management device does not need to execute the process for refunding electronic currency to legal tender, no transfer fees are incurred for the business managing the business management device, making it an easy-to-use device. Also, since the accounting process is performed instantly by the bank management device, unlike a transfer, the money can be deposited into the user's deposit account without taking much time.

[0015] The object of the present invention is to provide a service providing system that provides a service providing service to a user, the service providing system being a management device of a service providing service providing service that communicates with a user's terminal device and the service providing service providing service providing service. side A management device, a financial institution side management device which is a management device of a financial institution, the terminal device, the business side A financial institution-side management system having a management device and a financial institution-side management device for managing financial-related information between the management device and the financial institution-side management device, wherein registration-related information necessary for a user to transact with a business includes general registration-related information, which is general registration-related information, and financial institution identification information, which is identification information related to a financial institution, and the general registration-related information is transmitted to the financial-related information management device via the business-side management device, and the financial institution identification information is transmitted to the financial-related information management device without passing through the business-side management device, and the financial institution-side management device generates financial institution-directed transmission information receivable by a financial institution based on the registration-related information, and generates business-directed transmission information receivable by the business based on information received from the financial institution. The identification information relating to the financial institution includes a password for the user's financial institution and account balance information for the user's financial institution, and when the terminal device executes a charge to increase electronic currency, the connection is automatically changed from the business-side management device to the financial-related information management device when the password is input, and when the charge is completed, a completion signal is transmitted from the terminal device to the business-side management device, and then the charge-related information is provided to the business-side management device.The above object is achieved by a finance-related information management system.

[0016] The object of the present invention is to provide a service providing system that provides a service providing service to a user terminal device, a service providing service providing device that provides communication with the user terminal device, and a service providing service providing device that provides communication with the user terminal device. side A method for controlling a financial-related information management device which manages financial-related information between a management device and a financial institution side management device which is a management device of a financial institution, wherein registration-related information required for a user to transact with a business includes general registration-related information which is general registration-related information and financial institution identification information which is identification information related to a financial institution, the general registration-related information is transmitted to the financial-related information management device via the business side management device, and the financial institution identification information is transmitted to the financial-related information management device without passing through the business side management device, Also, based on the registration related information, a transmission information for financial institution that can be received by the financial institution is generated; ,gold Generate business-oriented transmission information receivable by the business based on the information received from the financial institution. The identification information relating to the financial institution includes a password for the user's financial institution and account balance information for the user's financial institution, and when the terminal device executes a charge to increase electronic currency, the connection is automatically changed from the business-side management device to the financial-related information management device when the password is input, and when the charge is completed, a completion signal is transmitted from the terminal device to the business-side management device, and then the charge-related information is provided to the business-side management device. The object of the present invention is achieved by a method for controlling a finance-related information management device, comprising the steps of:

[0017] The object of the present invention is to provide a service providing system that provides a service providing service to a user terminal device, a service providing service providing device that provides communication with the user terminal device, and a service providing service providing device that provides communication with the user terminal device. side A financial-related information management device which manages financial-related information between a management device and a financial institution side management device which is a management device of a financial institution, has a function in which registration-related information required for a user to transact with a business includes general registration-related information which is general registration-related information and financial institution identification information which is identification information related to a financial institution, the general registration-related information being transmitted to the financial-related information management device via the business side management device, and the financial institution identification information being transmitted to the financial-related information management device without passing through the business side management device, and further has a function in which financial institution-oriented transmission information which can be received by a financial institution is generated based on the registration-related information, ,gold A function of generating business-oriented transmission information receivable by the business based on information received from the financial institution; the identification information relating to the financial institution includes the user's personal identification number and the account balance information of the user's financial institution, and when the terminal device executes a charge to increase electronic currency, the connection is automatically changed from the carrier-side management device to the financial-related information management device upon input of the personal identification number; when the charge is completed, a completion signal is sent from the terminal device to the carrier-side management device, and then the charge-related information is provided to the carrier-side management device; This is achieved by a control program for a financial-related information management device configured to execute the above. Effect of the Invention

[0018] As described above, the present invention has the advantage of being able to provide a financial-related information management device, a financial-related information management system, a control method for a financial-related information management device, and a control program for a financial-related information management device that allow businesses to easily and at low cost to build networks with financial institutions. [Brief description of the drawings]

[0019] [Figure 1] FIG. 1 is a schematic explanatory diagram showing an electronic currency information management system 1, which is a "finance-related information management system" according to an embodiment of the present invention. [Diagram 2] 2 is a schematic block diagram showing the main configuration of a business server 20 of FIG. 1. [Diagram 3] 2 is a schematic block diagram showing the main configuration of a first various information storage unit 200 on the business entity's server side. FIG. [Figure 4] 2 is a schematic block diagram showing the main configuration of a second various information storage unit 210 on the business entity's server side. FIG. [Diagram 5] 2 is a schematic block diagram showing the main configuration of a management server 40 of FIG. 1. [Figure 6] 2 is a schematic block diagram showing the main configuration of a first various information storage unit 400 on the management server side. FIG. [Figure 7] 13 is a schematic block diagram showing the main configuration of a second various information storage unit 410 on the management server side. FIG. [Figure 8] 13 is a schematic block diagram showing the main configuration of a third various information storage unit 420 on the management server side. FIG. [Figure 9] FIG. 13 is a schematic block diagram showing the main configuration of a fourth various information storage unit 430 on the management server side. [Figure 10] FIG. 13 is a schematic block diagram showing the main configuration of a fifth various information storage unit 440 on the management server side. [Figure 11] FIG. 13 is a schematic block diagram showing the main configuration of a sixth various information storage unit 450 on the management server side. [Figure 12]2 is a schematic block diagram showing the main configuration of the bank server 30 of FIG. 1. [Figure 13] FIG. 2 is a schematic block diagram showing the main configuration of a first various information storage unit 300 on the bank server side. [Figure 14] FIG. 2 is a schematic block diagram showing the main configuration of a second various information storage unit 310 on the bank server side. [Figure 15] 1 is a schematic flow chart showing the main steps of a user registration process. [Figure 16] 13 is another main schematic flow chart showing the user registration process; [Figure 17] 13 is another main schematic flow chart showing the user registration process; [Figure 18] 1 is a schematic flowchart showing a main charging process performed by a user. [Figure 19] 13 is another schematic flowchart showing the main charging process of a user. [Figure 20] 13 is another schematic flowchart showing the main charging process of a user. [Figure 21] 13 is a schematic flowchart showing a refund process for a user. [Figure 22] 13 is another schematic flowchart showing a refund process for a user. [Figure 23] 13 is another schematic flowchart showing a refund process for a user. [Figure 24] FIG. 13 is a schematic explanatory diagram showing "management side user information (part 1)" stored in ST4. [Diagram 25] FIG. 13 is a schematic explanatory diagram showing management-side user information (part 2) in which MS information is stored in ST6. [Figure 26] FIG. 13 is a schematic explanatory diagram showing management-side user information indicating a state in which the "usage permission flag" is set in ST13. [Figure 27] FIG. 13 is a schematic explanatory diagram showing “management side user information (part 4)” in which “token information” is stored in ST14. [Figure 28] FIG. 13 is a schematic explanatory diagram showing the contents of "management side charge acceptance information (part 1)" stored in "management side charge acceptance information storage unit 32" in ST25. [Figure 29] FIG. 13 is a schematic explanatory diagram showing the contents of "management side charge acceptance information (part 2)" stored in "management side charge acceptance information storage unit 32" in ST27. [Diagram 30] FIG. 11 is a schematic explanatory diagram showing management-side user information (part 5) to which information on "charge amount," "transaction ID," and "transaction date and time" has been added in ST28. [Diagram 31] FIG. 13 is a schematic explanatory diagram showing “Administrator-side user information (part 6)” to which “Transaction result (withdrawal)” has been added in ST35. [Diagram 32] FIG. 11 is a schematic explanatory diagram showing the management side user information (part 7) to which the information on "refund amount," "transaction ID," and "transaction date and time" has been added in ST56. [Diagram 33] FIG. 13 is a schematic explanatory diagram showing “Administrator-side user information (part 8)” to which “transaction result (deposit)” has been added in ST64. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The embodiments described below are preferred specific examples of the present invention, and therefore various technically preferable limitations are applied. However, the scope of the present invention is not limited to these embodiments unless otherwise specified in the following description to the effect that the present invention is limited to these embodiments.

[0021] FIG. 1 is a schematic diagram showing an electronic currency information management system 1, which is a "finance-related information management system" according to an embodiment of the present invention. As shown in FIG. 1, the system 1 includes a terminal device 10 carried by a user who uses or wishes to use electronic currency such as XPay, an operator's management device of an operator that handles electronic currency such as XPay, for example an operator server 20, and a financial institution's management device such as a bank, for example a bank server 30.

[0022] In addition, the system 1 has, between the terminal device 10, the business operator server 20, and the bank server 30, a financial-related information management device, such as a management server 40, which manages financial-related information, such as user account information, etc. As shown in FIG. 1, the terminal device 10, the business server 20, the management server 40, etc. are connected to each other so as to be able to communicate with each other via an Internet network 2, a base station 3, etc. Furthermore, as shown in FIG. 1, the management server 40 is configured to be able to communicate with the bank server 30.

[0023] As shown in FIG. 1, the terminal device 10 includes an input device and a display unit, for example, a "touch panel 11." Here, the "touch panel 11" is an electronic component that combines a display, for example, as a display unit, with a position input device, and is an input device that allows a user to input various information by touching what is displayed on the display. Moreover, the terminal device 10 shown in FIG. 1 includes a terminal device-side communication device (not shown).

[0024] The terminal device 10, business operator server 20, management server 40, bank server 30, etc. of the "electronic currency management system 1" in Figure 1 are computers and have a CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), hard disk, etc., and are connected via a bus.

[0025] (Main configuration of the business operator server 20) FIG. 2 is a schematic block diagram showing the main configuration of the business server 20 of FIG. As shown in FIG. 2, the business server 20 has a business control unit 21, which controls a business communication device 22, a business display 23, and a business information input device 24. The control unit 21 also controls the "business server side first various information storage unit 200" and the "business server side second various information storage unit 210" shown in FIG.

[0026] 3 and 4 are schematic block diagrams showing the main configurations of the "business server side first various information storage unit 200" and the "business server side second various information storage unit 210," respectively. The contents of these will be described later.

[0027] (Regarding management server 40) FIG. 5 is a schematic block diagram showing the main configuration of the management server 40 in FIG. As shown in FIG. 5, the management server 40 has a "management side control unit 41", which controls a "management side communication device 42", a "management side display 43", and a "management side various information input device 44". The control unit 41 also controls the "first various information storage unit 400 on the management server side," "second various information storage unit 410 on the management server side," "third various information storage unit 420 on the management server side," "fourth various information storage unit 430 on the management server side," "fifth various information storage unit 440 on the management server side," and "sixth various information storage unit 450 on the management server side" shown in Figure 5.

[0028] 6 to 11 are schematic block diagrams showing the main configurations of the "management server side first various information storage unit 400" to "management server side sixth various information storage unit 450", respectively. The contents of these will be described later.

[0029] (About the bank server 30) FIG. 12 is a schematic block diagram showing the main components of the bank server 30 of FIG. As shown in FIG. 12, the bank server 30 has a "bank side control unit 31," which controls a "bank side communication device 32," a "bank side display 33," a "bank side various information input device 34," a "bank server side first various information storage unit 300," and a "bank server side second various information storage unit 310."

[0030] 13 and 14 are schematic block diagrams showing the main configuration of the "bank server side first various information storage unit 300" and the "bank server side second various information storage unit 310." The details will be described later.

[0031] (Example of operation of electronic currency management system 1) An example of the operation of the "electronic currency management system 1" according to this embodiment will be described below. In this embodiment, first, a "user registration process" will be described in which a user who wishes to use X-electronic currency operates the terminal device 10 shown in FIG. 1, accesses the business server 20 of a business that handles X-electronic currency via the Internet network 2 or the like, and performs a "registration procedure" to make the currency available for use.

[0032] 15 to 17 are schematic flow charts showing the main steps of a user's registration process, and FIGS. 18 to 20 are schematic flow charts showing the main steps of a user's charging process. 21 to 23 are schematic flow charts showing the refund process for the user.

[0033] Next, a "charging step" will be described in which a registered user operates the terminal device 10 of FIG. 1 to charge X electronic currency from his / her own bank account via the Internet network 2 or the like.

[0034] (User registration process) First, in step (hereinafter referred to as "ST") 1, a user who wishes to use X electronic currency (X Pay, etc.) operates his / her mobile terminal 10 of FIG. 1 and accesses the operator server 20 of X electronic currency (X Pay, etc.) of FIG. 1 via the Internet network 2 or the like.

[0035] Next, the process proceeds to ST2. In ST2, the "business-side registration reception processing unit (program) 201" in FIG. 3 of the business server 20 in FIG. 1 operates and refers to the "registration reception information storage unit 202" in FIG. The memory unit 202 stores items to be displayed as registration information on the touch panel 11 of the terminal device 10, such as basic reception information (e.g., "kana name, date of birth, bank name, branch name, item name, account number, etc."). Therefore, the processor 201 displays on the touch panel 11 of the terminal device 10 a screen requesting input of "basic reception information (for example, "kana name, date of birth, bank name, branch name, item name, account number)". Here, the basic reception information is an example of registration related information and general registration related information.

[0036] Next, the process proceeds to ST3. In ST3, when the user completes inputting information into the terminal device 10, the connection with the mobile terminal 10 is automatically changed from the business server 20 to the management server 40, and the "management side registration reception processing unit (program) 401" of the management server 40 in Fig. 6 operates, and the management server 40 requests the user to input the "current balance" and "PIN" into the touch panel 11 of the mobile terminal 10. You will also be asked to enter your name in kana, your date of birth, your occupation, your purpose of use, your telephone number, and your account information (branch name, deposit type, account number). The "current balance" and "PIN number" are examples of registration-related information and financial institution identification information.

[0037] Next, the process proceeds to ST4. In ST4, when the user has completed inputting "current balance (e.g., 1,000,000 yen)", "PIN (e.g., 5678)", "name in kana", "date of birth", "occupation", "purpose of use", "account information (branch name, type, account number)", etc., the processing unit 401 of the management server 40 operates and stores this information in "management-side user information" in the "management-side user information storage unit 402" in FIG. 6.

[0038] FIG. 24 is a schematic diagram showing the "management-side user information (part 1)" stored in ST4. As shown in Figure 24, at this stage, the following user information is stored as the managing side: "User ID," "Katakana name," "Bank name," "Branch name," "Item name," "Account number," "Current balance," "PIN," "Date of birth," "Purpose of use," "Occupation," "Telephone number," etc.

[0039] In this manner, in this embodiment, the user's “current balance” and “PIN number” are not input to the business server 20. Therefore, personal identification numbers, account numbers, etc. will not be leaked to electronic currency businesses, and the spread of these information can be prevented in advance.

[0040] Next, proceed to ST5. In ST5, the management server 40 receives the "kana name" and "date of birth" data from the business operator server 20, and determines whether the "kana name" and "date of birth" entered in the business operator server 20 match the "kana name" and "date of birth" entered in the management server 40. Next, proceed to ST6. In ST6, the "MS information acquisition unit (program) 403" in FIG. 6 of the management server 40 operates, and refers to the "MS information storage unit 404" in FIG. 6. This "MS information storage unit 404" stores magstripe (MS) information of each bank's cash card. Here, the MS information is information stored in the cash card of each bank, and account numbers and the like are stored in an encrypted form.

[0041] In addition, the acquisition unit 403 refers to the “bank name (e.g., ABC Bank)” of the user ID in the management side user information (part 1) in Figures 6 and 24, acquires the magstripe (MS) information of the cash card of the bank (e.g., ABC Bank), and stores it in the “management side user information” in Figure 6.

[0042] FIG. 25 is a schematic explanatory diagram showing management-side user information (part 2) in which MS information is stored in ST6. As shown in FIG. 25, the management side user information (part 2) stores "MS information", unlike the above-mentioned part 1.

[0043] Next, the process proceeds to ST7. In ST7, the "bank-destined message (e.g., ATM message) creation unit (program) 405" in Fig. 6 of the management server 40 operates to obtain the "bank name (ABC bank)", "branch name (Osaki branch)", "item name (regular)", "account number (1234567)", "MS information (····)", and "PIN (5678)" from the management-side user information (part 2) in the management-side user information storage unit in Figs. 6 and 25, create a "first bank-destined message", and store it in the "first bank-destined message storage unit 406" in Fig. 6.

[0044] Here, the "first telegram to be transmitted to the bank" is an example of information to be transmitted to a financial institution, and is a telegram that can be received by a financial institution such as a bank. In this embodiment, for example, the message is in accordance with an API (Application Programming Intercace) that can be received by ABC Bank. Although each bank employs a different API for bank-directed messages, the management server 40 of this embodiment acquires information on the API of each bank and is therefore able to create messages suited to the relevant bank (e.g., ABC Bank).

[0045] Therefore, even if a business operator obtains user information, the business operator can transmit the information to the bank server 30 by transmitting the information to the management server 40. This eliminates the need for the business operator to build a network in accordance with APIs that differ for each bank, and allows communication with banks at extremely low cost. . Furthermore, since banks can communicate with the management server 40 by simply using the API network that they have been using, there is no need to build a new network, and communication can be achieved at extremely low cost.

[0046] Next, the process proceeds to ST8. In ST8, the management server 40 transmits the message stored in the "first bank-destined message storage unit 406" in FIG. Then, after transmission, the management server 40 deletes from its memory the "PIN" of the management side user information (part 2) in Figure 25 and the "PIN" of the "Message to be sent to the first bank" in the "Message to be sent to the first bank memory unit 406" in Figure 6.

[0047] In this manner, this embodiment is configured so that the "PIN number," which is extremely important to the user, is not stored not only in the business server 20 but also in the "management server 40," making it an extremely secure system.

[0048] Next, the process proceeds to ST9. In ST9, the "PIN matching processing unit (program) 301" of the bank server 30 in Fig. 13 operates to obtain "PIN" information for the account in the bank server 30 from the "account number" etc. of the received "telegram to be sent to the first bank". Then, the PIN number of the first message to be sent to the bank is checked against the PIN number of the bank server.

[0049] Next, the process proceeds to ST10. In ST10, if the bank server 30 checks the PIN of the user's account and finds that the PIN is a perfect match, the "Current Balance To Bank Transmission Message Creation Unit (Program) 302" of the bank server 30 in Fig. 13 is activated. Then, a "current balance message to be sent to the bank" including the "current balance" of the account in the bank server 30 is created and stored in the "current balance message to be sent to the bank storage unit 303" in FIG. This "message to be sent to the bank with the current balance" also includes the account holder's "kana name," "date of birth," "a flag identifying whether the account holder has been identified by the bank (identity verification flag)," and "a flag identifying whether the account holder is an individual or a corporation (individual / corporation identification flag)" as known by the bank. This PIN is an example of PIN information.

[0050] This message with the current balance to be sent to the bank is created in accordance with the bank's API, and as shown in Figure 13, it contains information such as the bank name (ABC_bank), branch name (Osaki_Branch), account name (regular), account number (1234567), MS number (abvdefg), PIN number (efgh), and the current balance on the bank side (1,000,000 yen).

[0051] In this step, the bank server 30 judges whether the "personal identification number" entered by the user on the terminal device 10 is correct.

[0052] Next, the process proceeds to ST11. In ST11, the bank server 30 transmits to the management server 40 the "current balance-bearing bank-destined message to be transmitted" in the "current balance-bearing bank-destined message storage unit 303" in FIG.

[0053] Next, the process proceeds to ST12. In ST12, the "current balance-bearing business-destined telegram creation unit (program) 411" in Fig. 7 of the management server 40 operates to convert the received "current balance-bearing bank-destined telegram" into a "current balance-bearing business-destined telegram." Then, the message is stored in the "message storage unit 412 for transmission to the current balance-bearing business operator" in FIG.

[0054] Here, the “telegram to be transmitted to the business operator” of the telegram to be transmitted to the business operator with the current balance is an example of transmission information to the business operator that the business operator server 20 can receive. As described above, in this embodiment, the management server 40 converts special messages intended for banks into messages intended for businesses, so that businesses do not need to build new networks that conform to the APIs adopted by the banks specifically for communicating with the banks, thereby making it possible to keep communication costs low.

[0055] As described above, in this embodiment, the management server 40 transmits information in a message that can be received by both the bank server 30 and the business server 20, so that the bank server 30 and the business server 20 can exchange information with each other as is, without making any changes to the conventional network system, etc. For example, since the bank servers 30 of each bank employ different APIs, the business entity server 20 needs to build networks adapted to the different APIs in order to communicate with each bank server 30. In contrast, in this embodiment, the management server 40 generates messages that match the API of each bank server 30, so the business operator server 20 does not need to build a network that matches a different API to communicate with the bank server 30, and can use existing networks, etc. as is, thereby significantly reducing costs.

[0056] Next, the process proceeds to ST13. In ST13, the "information comparison unit (matching) (program) 421" of the management server 40 operates to compare the "kana name," "date of birth," and "current bank balance (1,000,000 yen)" of the "message to send to business operators with current balances" in the "message to send to business operators with current balances storage unit 412" in Fig. 7 with the "kana name," "date of birth," and "current balance (1,000,000 yen)" of the "management side user information (part 2)" in the "management side user information storage unit 402" in Fig. 6 and Fig. 25, and determines whether the data match. If they match, identity verification has been performed, and it has been confirmed that the account holder is an individual, a "use permission flag" is set in the management side user information storage unit 402 in Fig. 6. In addition, this identity verification and confirmation that the account holder is an individual are carried out based on the “Message to be sent to businesses with current balance” in Figure 7.

[0057] FIG. 26 is a schematic diagram showing the management-side user information indicating a state in which the "usage permission flag" is set in ST13. As shown in FIG. 26, the "usage permission flag" is set in the management-side user information (part 3). Here, the current balance is an example of balance information.

[0058] In this manner, in this embodiment, the bank server 30 confirms that the PIN entered by the user matches the PIN registered on the user's cash card, and the management server 40 compares the "kana name," "date of birth," and current balance entered by the user with the "kana name," "date of birth," and current balance obtained from the bank server 30, and sets the "permission to use flag" only if they match, and if the bank has confirmed that the account holder is an individual. This makes it possible to reliably authenticate the user.

[0059] In particular, in this embodiment, PIN verification is performed by the bank server 30, and current balance and other information is verified by the management server 40, so that each is performed by different institutions, enabling more reliable identity authentication.

[0060] Next, the process proceeds to ST14. In ST14, the "usage period information (token) generation unit (program) 422" in Fig. 8 of the management server 40 operates to generate token information (valid for 120 days from a specific date) and register it in the "management side user information storage unit 402" in Fig. 6. FIG. 27 is a schematic explanatory diagram showing the "management side user information (part 4)" in which the "token information" is stored in ST14. As shown in FIG. 27, the reliability of personal authentication is ensured by adding information that limits the validity period of the user flag.

[0061] Next, the process proceeds to ST15. In ST15, the "user information to be transmitted to the business server generating unit (program) 423" of the management server 40 operates to generate "information to be transmitted to the business server" and store it in the "information to be transmitted to the business server storage unit 424" in FIG. This information for transmission to the business server is generated as a business-oriented transmission message that can be received by the business server, and is limited to only the information required by the business, and does not include the user's cash card PIN or current bank account balance information.

[0062] Specifically, the "information to be sent to business server" in Figure 8 includes business ID (e.g., 2001), user ID (e.g., 10001), kana name, bank name (e.g., ABC Bank), branch name (e.g., Osaki Branch), item name (e.g., ordinary), account number (e.g., 1234567), token (e.g., 20200130), and other information.

[0063] In this manner, in this embodiment, business operators can communicate with the bank server 30 via the management server 40 without making any changes to their existing systems, and confidential information of users cannot be obtained. Therefore, it is an easy-to-use system for business operators, capable of automatically obtaining necessary information, while providing a high level of security for users.

[0064] Next, the process proceeds to ST16. In ST16, the management server 40 transmits to the agent server 20 the "information to be transmitted to the agent server" in the "information to be transmitted to the agent server storage unit 424" in FIG.

[0065] Next, the process proceeds to ST 17. In ST 17, the business server 20 stores the "business-side user information" in the "business-side user information storage unit 203" of the business server 20 in FIG. 3 based on the received "business server transmission information." Specifically, as shown in the "business-side user information storage unit 203" in FIG. 3, information such as the business ID (e.g., 2001), user ID (e.g., 10001), kana name (, bank name (e.g., ABC Bank), branch name (e.g., Osaki Branch), type name (e.g., ordinary), account number (e.g., 1234567), and token (e.g., 20200130) is stored.

[0066] This allows the business server 20 to automatically obtain necessary information about the user who uses the X electronic currency.

[0067] Next, the process proceeds to ST 18. In ST 18, the management server 20 displays a registration completion screen on the touch panel 11 of the terminal device 10, and the "user registration" is completed.

[0068] (Charge process) The steps for a user who has completed registration to use X electronic currency to "charge" the currency, i.e., change the cash in his / her bank account to X electronic currency that can be used on the terminal device 10, will be described below. First, in ST21 of FIG. 18, a user who wishes to load electronic currency accesses the electronic currency business server 20 with his / her terminal device 10.

[0069] Next, the process proceeds to ST22. In ST22, the "charge acceptance processing unit (program) 204" of the business server 20 in Fig. 3 operates, and an input screen for charging information, for example, a charging amount, is displayed on the touch panel 11 of the terminal device 10.

[0070] Next, the process proceeds to ST23. In ST23, when the input is completed, the processing unit 204 operates and stores the charge amount in the "business operator side charge acceptance information storage unit 211" in FIG. The carrier-side charge acceptance information storage unit 211 in FIG. 4 stores the bank name (e.g., ABC Bank), branch name (e.g., Osaki Branch), account name (e.g., regular), account number (e.g., 124567), and charge amount (e.g., 1,000 yen).

[0071] Next, the process proceeds to ST24. In ST24, the connection with the terminal device 10 is automatically changed from the business entity server 20 to the management server 40, and the business entity server 20 transmits to the management server 40 the "business entity side charge acceptance information" in the "business entity side charge acceptance information storage unit 211" in FIG.

[0072] Next, the process proceeds to ST25. In ST25, management server 40 stores the received "business entity side charge acceptance information" as "management side charge acceptance information" in the "management side charge acceptance information storage unit 431" in FIG. FIG. 28 is a schematic explanatory diagram showing the contents of the "management side charge acceptance information (part 1)" stored in the "management side charge acceptance information storage unit 431" in ST25. As shown in FIG. 28, the "Administrator side charge reception information (part 1)" includes the following items: "Bank name (e.g., ABC Bank)", "Branch name (e.g., Osaki Branch)", "Item name (e.g., Regular)", "Account number (e.g., 1234567)", and "Charge amount (e.g., 1,000 yen)".

[0073] Next, the process proceeds to ST26. In ST26, the "PIN request section (program) 432" of the management server 40 shown in FIG.

[0074] Next, the process proceeds to ST27. In ST27, when an input is made, the request unit 432 of the management server 40 stores the input "personal identification number (for example, 5678)" in the "management side charge acceptance information storage unit 431" in FIG.

[0075] FIG. 29 is a schematic explanatory diagram showing the contents of the "management side charge acceptance information (part 2)" stored in the "management side charge acceptance information storage unit 431" in ST27. As shown in FIG. 29, the "management side charge acceptance information (part 1)" includes the following items. "Bank name (e.g., ABC Bank)" "Branch name (e.g., Osaki Branch)" "Item name (e.g., Regular)" "Account number (e.g., 1234567)" "Charge amount (e.g., 1,000 yen)" "PIN number (e.g., 5678)"

[0076] As described above, in this embodiment, the PIN number input by the user is input directly to the management server 40, not to the business server 20. This prevents the business from obtaining unnecessary information, and allows the user to ensure the confidentiality of the PIN number.

[0077] Next, proceed to ST28. In ST28, the "first user determination unit (program) 433" in Fig. 9 of management server 40 operates to compare the "management side charge acceptance information" in the "management side charge acceptance information storage unit 431" in Fig. 9 with the "management side user information" in the "management side user information storage unit 402" in Fig. 6 of management server 40. Specifically, the "management side charge acceptance information (part 2)" in Figure 29 is compared with the "management side user information (part 4)" in Figure 27 to determine whether the information matches, and if it does match, the information on "charge amount," "transaction ID," and "transaction date and time" is stored in the "management side user information storage unit 402" in Figure 6.

[0078] FIG. 30 is a schematic diagram showing the management-side user information (part 5) to which the information on "charge amount," "transaction ID," and "transaction date and time" has been added in ST28. As shown in FIG. 30, the management side user information (part 5) stores information such as "charge amount (for example, 1,000 yen)", "transaction ID (····)", and "transaction date and time (····)".

[0079] In this manner, in this embodiment, even if a user has gone through the registration process, the management server 40 authenticates the user again when charging, making the system more secure.

[0080] Next, the process proceeds to ST29. In ST29, the "second bank-destined transmission message creation unit (program) 434" in Fig. 9 of the management server 40 operates to create a "second bank-destined transmission message", for example an ATM message, based on the "management-side user information (part 5)" in Fig. 30 of the "management-side user information storage unit 402" in Fig. 6 and the "management-side recharge acceptance information (part 2)" in Fig. 29 of the "management-side recharge acceptance information storage unit 431" in Fig. 9, and store the message in the "second bank-destined transmission message storage unit 435" in Fig. 9.

[0081] Specifically, as shown in FIG. 9, the contents of the “Second Telegram to be Sent to Bank” are as follows: "Bank name (e.g., ABC_bank)" "Branch name (e.g., Osaki_branch)" "Item name (regular)" "Account number (e.g., 1234567)" "MS information (e.g., Abcdefg)" "PIN number (e.g., efgh)" "Charge amount (e.g., 1,000 yen)"

[0082] Next, the process proceeds to ST30. In ST30, the management server 40 transmits the "telegram to be transmitted to the second bank" in the "telegram to be transmitted to the second bank storage unit 435" in Fig. 9 to the "bank server (ABC bank)". Then, the "PIN" information in the "Telegram to be sent to the second bank" is deleted.

[0083] Therefore, the management server 40 does not hold the highly confidential PIN numbers of the users' cash cards, which increases security.

[0084] Next, the process proceeds to ST31. In ST31, the "withdrawal determination processing unit (program) 304" of the bank server 30 in Fig. 13 operates to determine whether the "charge amount" can be withdrawn, and if so, performs a withdrawal process (accounting system process) of 1,000 yen. Then, a "transmission message to be sent to the withdrawn bank" is generated and stored in the "transmission message to be sent to the withdrawn bank storage unit 311" in FIG.

[0085] Next, the process proceeds to ST32. In ST32, the bank server 30 transmits to the management server 40 the "transmission message to the withdrawn bank" in the "transmission message storage unit 311 to the withdrawn bank" in FIG.

[0086] Next, the process proceeds to ST33. In ST33, the management server 40 stores the received "telegram to be transmitted to the withdrawn bank" in the "management side telegram to be transmitted to the withdrawn bank storage unit 441" in FIG.

[0087] Next, the process proceeds to ST34. In ST34, the "first telegram conversion processing unit (program) 442 for transmission to business operator" in Fig. 10 of the management server 40 operates to convert the "telegram for transmission to the withdrawn bank on the management side" in the "telegram storage unit for transmission to the withdrawn bank on the management side 441" in Fig. 10 into a "telegram for transmission to the withdrawn business operator on the management side" and store it in the "telegram storage unit for transmission to the withdrawn business operator on the management side 443" in Fig. 10.

[0088] Therefore, similar to the user registration process described above, the management server 40 generates and transmits messages to the bank server 30 and the business server 20, so that business operators and banks can use their existing systems as is without making any changes, and the present system 1 can be used at low cost.

[0089] Next, the process proceeds to ST35. In ST35, the management server 40 stores the “transaction result (withdrawal) (e.g., 1,000 yen)” of the “management side telegram to be sent to withdrawn business entity” in the “management side telegram to be sent to withdrawn business entity storage unit 443” in Fig. 10 in the “management side user information storage unit 402” in Fig. 6.

[0090] FIG. 31 is a schematic diagram showing the "administrator-side user information (part 6)" to which the "transaction result (withdrawal)" has been added in ST35. As shown in FIG. 31, the management server 40 is configured to be able to manage user information excluding personal identification numbers.

[0091] Next, the process proceeds to ST36. In ST36, the management server 40 displays on the touch panel 11 of the terminal device 10 that the charge of 1000 yen has been processed as electronic currency.

[0092] Next, the process proceeds to ST37. In ST37, when approval is inputted at the terminal device 10, a signal indicating completion of the transaction is transmitted to the business entity's server 20.

[0093] Next, the process proceeds to ST38. In ST38, the business operator server 20 acquires the "management side withdrawn business operator-directed transmission message" from the management server 40, and adds "transaction result (withdrawal)" information and the like to the "business operator-side user information" in the "business operator-side user information storage unit 203" in Fig. 3, and stores the information.

[0094] In the charging process of this embodiment, communication from ST24 with the terminal device 10 is automatically changed to the management server 40 instead of the business operator server 20, so that the business operator server 20 cannot obtain charging-related information, such as transaction result (withdrawal) information. Therefore, when the transaction is completed in ST37, a signal is transmitted from the terminal device 10 to the business operator server 20, and the business operator server 20 can obtain information such as the transaction result (withdrawal) from the management server 40. That is, confidential information such as a PIN number is not input to the business operator server 20, and necessary information such as transaction results (withdrawals) can be quickly and completely obtained by the business operator server 20. In addition, according to this embodiment, even if communication between the business server 20, the bank server 30, and the management server 40 is interrupted, the business side is able to check the consistency of the transaction results between the business server 20, the management server 40, and the bank server 30 and correct any inconsistencies.

[0095] (Refund process) The following describes the process by which a user who has completed registration to use X-electronic currency "withdraws" X-electronic currency without using it, that is, deposits X-electronic currency into his / her bank account as legal tender, such as yen. First, in ST51 of FIG. 21, a user who wishes to withdraw electronic currency accesses the electronic currency business server 20 with his / her terminal device 10.

[0096] Next, the process proceeds to ST52. In ST52, the "refund reception processing unit (program) 212" of the business server 20 in Fig. 4 operates, and an input screen for inputting refund information, for example, a refund amount, is displayed on the touch panel 11 of the terminal device 10.

[0097] Next, the process proceeds to ST53. In ST53, when the input is completed, the processing unit 212 operates to store the refund amount in the "business operator's refund acceptance information storage unit 213" in FIG. The business operator's refund acceptance information storage unit 213 in FIG. 4 stores the "bank name (e.g., ABC Bank)", "branch name (e.g., Osaki Branch)", "item name (e.g., ordinary)", "account number (e.g., 124567)", and "refund amount (e.g., 1,000 yen)".

[0098] Next, the process proceeds to ST54. In ST54, the connection with the terminal device 10 is automatically changed from the business entity server 20 to the management server 40, and the business entity server 20 transmits to the management server 40 the "business entity side refund acceptance information" in the "business entity side refund acceptance information storage unit 213" in FIG.

[0099] Next, the process proceeds to ST55. In ST55, the management server 40 stores the received "business operator's refund acceptance information" as "management side refund acceptance information" in the "management side refund acceptance information storage unit 444" in FIG. As shown in FIG. 10, the "management side refund acceptance information" includes the following items. "Bank name (e.g., ABC Bank)" "Branch name (e.g., Osaki Branch)" "Item name (e.g., Regular)" "Account number (e.g., 1234567)" "Refund amount (e.g., 1,000 yen)"

[0100] Next, the process proceeds to ST56. In ST56, the "second user determination unit (program) 451" of the management server 40 in Fig. 11 operates to compare the "management-side refund acceptance information" in the "management-side refund acceptance information storage unit 444" in Fig. 10 with the "management-side user information" in the "management-side user information storage unit 402" in Fig. 6 of the management server 40. Specifically, the "management side refund acceptance information" in Figure 10 is compared with the "management side user information (part 4)" in Figure 27 to determine whether the information matches, and if it does match, the information on "refund amount," "transaction ID," and "transaction date and time" is stored in the "management side user information storage unit 402" in Figure 6.

[0101] FIG. 32 is a schematic diagram showing the management-side user information (part 7) to which the information on "refund amount," "transaction ID," and "transaction date and time" has been added in ST56. As shown in FIG. 32, the management side user information (No. 7) stores information such as "refund amount (for example, 1,000 yen)", "transaction ID (····)", and "transaction date and time (····)".

[0102] In this manner, in this embodiment, even if a user has gone through the registration process, the management server 40 authenticates the user again at the time of a refund, making the system more secure.

[0103] Next, the process proceeds to ST57. In ST57, the "generating unit (program) 452 for transmission to the third bank" in Fig. 11 of the management server 40 operates to generate a "message to be transmitted to the third bank", for example an ATM message, based on the "management-side user information (part 4)" in Fig. 27 of the "management-side user information storage unit 402" in Fig. 6 and the "management-side refund acceptance information" in the "management-side refund acceptance information storage unit 444" in Fig. 10, and store it in the "message to be transmitted to the third bank" in Fig. 11.

[0104] Specifically, as shown in FIG. 11, the contents of the “Third Telegram to be sent to the Bank” are as follows: "Bank name (e.g., ABC_bank)" "Branch name (e.g., Osaki_branch)" "Item name (regular)" "Account number (e.g., 1234567)" "MS information (e.g., Abcdefg)" "Refund amount (e.g., 1,000 yen)"

[0105] Next, the process proceeds to ST58. In ST58, the management server 40 transmits the "transmission message to be sent to the third bank" in the "transmission message storage unit 453 to be sent to the third bank" in Fig. 11 to the "bank server (ABC bank)".

[0106] Next, the process proceeds to ST59. In ST59, the bank server 30 processes the deposit (1,000 yen) into the bank account (accounting process). Then, in ST60, a "deposited bank transmission message" is generated and stored in the "deposited bank transmission message storage unit 312" in FIG. Because the deposit (1,000 yen) to the bank account is processed instantly (accounting system processing) in this way, the money can be deposited into the user's savings account without the time it takes with a transfer.

[0107] Next, the process proceeds to ST61. In ST61, the bank server 30 transmits to the management server 40 the "deposited bank transmission message" in the "deposited bank transmission message storage unit 312" in FIG.

[0108] Next, the process proceeds to ST62. In ST62, the management server 40 stores the received "deposited bank transmission message" in the "management side deposited bank transmission message storage unit 454" in FIG.

[0109] Next, the process proceeds to ST63. In ST63, the "second telegram conversion processing unit (program) 455 for transmission to business entity" in Fig. 11 of the management server 40 operates to convert the "management side telegram for transmission to the deposited bank" in the "management side telegram for transmission to the deposited bank memory unit 454" in Fig. 11 into a "management side telegram for transmission to the deposited business entity" and store it in the "management side telegram for transmission to the deposited business entity memory unit 456" in Fig. 11.

[0110] Therefore, similarly to the user registration process described above, in the "withdrawal" process, the management server 40 generates and transmits a message to be sent to the bank server 30 and a message to be sent to the business server 20, so that business operators and banks can use their existing systems as they are without making any changes, and the present system 1 can be used at low cost.

[0111] Next, the process proceeds to ST64. In ST64, the management server 40 stores the "transaction result (deposit) (e.g., 1,000 yen)" of the "management side telegram to be sent to the paid business operator" in the "management side telegram to be sent to the paid business operator storage unit 456" in Fig. 11 in the "management side user information storage unit 402" in Fig. 6.

[0112] FIG. 33 is a schematic diagram showing the "administrator-side user information (part 8)" to which the "transaction result (deposit)" has been added in ST64.

[0113] Next, the process proceeds to ST65. In ST65, the management server 40 displays on the touch panel 11 of the terminal device 10 that 1000 yen has been refunded as legal tender (yen) and deposited into the bank account.

[0114] Next, the process proceeds to ST66. In ST66, when approval is inputted at the terminal device 10, a signal indicating completion of the transaction is transmitted to the business entity's server 20.

[0115] Next, in ST67, the management server 40 transmits to the business server 20 a “transaction result (deposit)” information and the like. Next, the process proceeds to ST68. In ST68, the business server 20 adds information such as "transaction result (deposit)" to the "business-side user information" in the "business-side user information storage unit 203" in Fig. 3 based on the "management-side paid business-to-transmission message" received from the management server 40, and stores the information.

[0116] In this manner, the above-described refund process in this embodiment is executed between the management server 40 and the bank server 30, and the business operator server 20 does not need to process the refund. Therefore, no transfer fees or the like are incurred by the business operator handling the X electronic currency that manages the business operator server 20, resulting in an easy-to-use configuration.

[0117] In addition, in ST67 of this embodiment, if the management server 40 is not normally transmitted the “transaction result (deposit)” information etc. to the business server 20 within a specified time, the business server 20 may be configured to obtain the information on the transaction result (deposit) etc. from the management server 40.

[0118] In the above-described embodiment, an example has been given of the case where the invention is realized as an apparatus, but the invention is not limited to this, and the invention may be distributed as a program that can be executed by a computer, stored on a storage medium such as a magnetic disk (e.g., a floppy (registered trademark) disk, a hard disk, etc.), an optical disk (e.g., a CD-ROM, a DVD), a magneto-optical disk (MO), or a semiconductor memory.

[0119] The storage medium may be any medium that can store a program and is computer readable. The storage format of the storage medium is not particularly limited.

[0120] In addition, the OS (operating system) that runs on the computer based on instructions from the program installed on the computer from the storage medium, database management software, etc. Alternatively, a part of each process for implementing this embodiment may be executed by a MW (middleware) such as a client or network software.

[0121] Furthermore, the storage medium in the present invention is not limited to a medium independent of a computer, but also includes a storage medium that stores or temporarily stores a program downloaded via a LAN, the Internet, or the like.

[0122] Furthermore, the computer in the present invention only needs to execute each process in this embodiment based on a program stored in a storage medium, and may be a device consisting of a single personal computer, etc., or a system in which multiple devices are connected to a network.

[0123] In addition, the computer in this invention is not limited to a personal computer, but also includes an arithmetic processing device, a microcomputer, etc. included in information processing equipment, and is a general term for equipment or devices that can realize the functions of the present invention by a program.

[0124] The above describes the embodiments of the present invention. However, the present invention is not limited to the above embodiments, and various modifications can be made without departing from the scope of the claims. The configurations of the above embodiments can be partially omitted or arbitrarily combined in a manner different from the above. [Explanation of symbols]

[0125] 1 Electronic currency information management system, 2 Internet network, 3 Base station, 10 Terminal device, 20 Business operator server, 30 Bank server, 40 Management server, 200 First various information storage unit on business operator server side, 210 Second various information storage unit on business operator server side, 300 First various information storage unit on bank server side, 310 Second various information storage unit on bank server side, 400 First various information storage unit on management server side, 410 Second various information storage unit on management server side, 420 Third various information storage unit on management server side, 430 Fourth various information storage unit on management server side, 440 Fifth various information storage unit on management server side, 450 Sixth various information storage unit on management server side

Claims

1. A financial-related information management device that manages financial-related information between a user's terminal device, a business operator's management device that is a management device of a business that communicates with the terminal device, and a financial institution's management device that is a management device of a financial institution, The registration-related information required for users to transact with businesses includes general registration-related information, which is general registration-related information, and financial institution identification information, which is identification information related to financial institutions, The general registration related information is transmitted to the financial-related information management device via the business-side management device; The financial institution identification information is transmitted to the financial-related information management device without passing through the business-side management device, Also, based on the registration-related information, a transmission information for financial institution that can be received by the financial institution is generated, and based on the information received from the financial institution, a transmission information for business entity that can be received by the business entity is generated; The identification information regarding the financial institution includes the user's password and the user's account balance information at the financial institution; This financial-related information management device is characterized in that, when the terminal device performs a charge to increase electronic currency, the connection is automatically changed from the carrier-side management device to the financial-related information management device when the PIN is entered, and when the charge is completed, an end signal is sent from the terminal device to the carrier-side management device, and then charge-related information is provided to the carrier-side management device.

2. The financial-related information management device of claim 1, characterized in that it is configured to determine permission to use electronic currency based on matching information between PIN information at the financial institution, balance information of the user received from the financial institution, and balance information entered by the user.

3. A financial-related information management device as described in claim 1 or claim 2, characterized in that when refund request information for refunding electronic currency into legal tender is input into the terminal device, the financial institution side management device executes the refund request information.

4. A user terminal device; A carrier-side management device that is a management device of a carrier that communicates with the terminal device; A financial institution side management device which is a management device of the financial institution; a financial institution-side management system including the terminal device, and a financial-related information management device that manages financial-related information between the business-side management device and the financial institution-side management device, The registration-related information required for users to transact with businesses includes general registration-related information, which is general registration-related information, and financial institution identification information, which is identification information related to financial institutions, The general registration related information is transmitted to the financial-related information management device via the business-side management device; The financial institution identification information is transmitted to the financial-related information management device without passing through the business-side management device, The financial-related information management device generates financial institution-directed transmission information receivable by the financial institution based on the registration-related information, and generates business-directed transmission information receivable by the business based on information received from the financial institution; The identification information regarding the financial institution includes the user's password and the user's account balance information at the financial institution; A financial-related information management system characterized in that, when the terminal device performs a charge to increase electronic currency, the connection is automatically changed from the carrier-side management device to the financial-related information management device when the PIN is entered, and when the charge is completed, an end signal is sent from the terminal device to the carrier-side management device, and then charge-related information is provided to the carrier-side management device.

5. A method for controlling a financial-related information management device that manages financial-related information between a user's terminal device, a business operator's management device that is a management device of a business that communicates with the terminal device, and a financial institution's management device that is a management device of a financial institution, comprising: The registration-related information required for users to transact with businesses includes general registration-related information, which is general registration-related information, and financial institution identification information, which is identification information related to financial institutions, The general registration related information is transmitted to the financial-related information management device via the business-side management device; The financial institution identification information is transmitted to the financial-related information management device without passing through the business-side management device, Also, based on the registration-related information, a transmission information for financial institution that can be received by the financial institution is generated, and based on the information received from the financial institution, a transmission information for business entity that can be received by the business entity is generated; The identification information regarding the financial institution includes the user's password and the user's account balance information at the financial institution; A control method for a financial-related information management device, characterized in that when the terminal device performs a charge to increase electronic currency, the connection is automatically changed from the business operator's management device to the financial-related information management device when the PIN is entered, and when the charge is completed, an end signal is sent from the terminal device to the business operator's management device, and then charge-related information is provided to the business operator's management device.

6. A financial-related information management device that manages financial-related information between a user's terminal device, a business operator's management device that is a management device of a business that communicates with the terminal device, and a financial institution's management device that is a management device of a financial institution, The registration-related information required for a user to transact with a business operator includes general registration-related information, which is general registration-related information, and financial institution identification information, which is identification information related to a financial institution, and the general registration-related information is transmitted to the financial-related information management device via the business operator-side management device; The financial institution identification information is transmitted to the financial-related information management device without going through the business-side management device; Also, a function of generating financial institution-oriented transmission information receivable by the financial institution based on the registration-related information, and generating business-oriented transmission information receivable by the business based on information received from the financial institution; the identification information relating to the financial institution includes the user's personal identification number and the user's account balance information at the financial institution, and when the terminal device is charged to increase electronic currency, the connection is automatically changed from the business management device to the financial-related information management device upon input of the personal identification number; A control program for a financial-related information management device that is configured to execute the function of transmitting an end signal from the terminal device to the business-side management device when charging is completed, and then providing charge-related information to the business-side management device.

Images