Financial-related information management apparatus, control method thereof, and control program therefor

Abstract

To provide a finance-related information management device and the like that ensure transaction security without requiring users to perform complicated procedures when withdrawing from a deposit account of a financial institution to charge electronic currency such as electronic money.SOLUTION: A finance-related information management device 40 is capable of communicating with a user terminal device 10, a business management device 20, which is a management device of a business entity, and a financial institution side management device 30, which is a management device of the financial institution. If a predetermined condition is reached, automatic account withdrawal is executed that automatically withdrawals a predetermined amount from a deposit account of the financial institution and increases the electronic currency of the terminal device. The execution of automatic account withdrawal does not require to input user financial institution password information. The execution of automatic account withdrawal is permitted based on the past automatic account withdrawal execution information, which is automatic account withdrawal execution record information in the past.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a financial-related information management device for managing financial-related information between a business operator and a financial institution, a control method for the financial-related information management device, and a control program for the financial-related information management device.

Background Art

[0002] Conventionally, there is "electronic money automatic recharge" that automatically recharges from a user's bank account or the like when the balance of electronic money or the like is low. However, in this "electronic money automatic recharge", in order to ensure the security of the transaction, input of a "password" or the like is required. (Patent Document 1, etc.)

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, for users of electronic money, there has been a problem that it is cumbersome to be required to input a password or the like every time they recharge. In addition, when a financial institution or the like that manages devices such as ATMs for recharging electronic money or the like is different from the financial institution or the like used by the user, there has also been a problem that the financial institution has to let other financial institutions or the like manage the "password" or the like.

[0005] Therefore, an object of the present invention is to provide a financial-related information management device, a control method for the financial-related information management device, a control program for the financial-related information management device, etc. that can ensure the safety of transactions without requiring complicated procedures for users when withdrawing money from a deposit account of a financial institution when charging (depositing) electronic currency such as electronic money.

[0006] In the present invention, the above object is achieved by a financial-related information management device that manages financial-related information capable of communicating with a user's terminal device, a carrier management device for carriers that communicates with the terminal device, and a financial institution side management device that is a management device of a financial institution. When the electronic money of the terminal device reaches a predetermined condition, an automatic account withdrawal is executed in which money is automatically withdrawn from a deposit account of a financial institution and a predetermined amount is increased. For the execution of the automatic account withdrawal, the input of the password information of the user's financial institution is not required as a condition, and the execution of the automatic account withdrawal is permitted based on past automatic account withdrawal execution performance information, which is past automatic account withdrawal execution information. The user Received from the terminal device Registration-related information Store it as administrator-side user information, and when the administrator-side user information matches the registration-related information which is the information received from the business operator management device, the administrator-side user information Based on this, financial institution-destined transmission information that can be received by the financial institution is generated, and based on the information received from the financial institution, carrier management device-destined transmission information that can be received by the carrier management device na is generated. This is achieved by a financial-related information management device characterized by this.

[0007] According to the above configuration, since automatic account withdrawal is possible without inputting password information such as a password, the user is not forced to input a password. Also, when executing an automatic account withdrawal (for example, auto-charge, etc.), since the execution of the automatic account withdrawal is permitted based on past automatic account withdrawal execution performance information (for example, the number of withdrawal executions per day for each carrier), inappropriate automatic account withdrawals can be prevented in advance. Also, according to the above configuration, financial institution-targeted transmission information that can be received by a financial institution is generated based on registration-related information (for example, kana name, date of birth, bank name, etc.), and business operator-targeted transmission information that can be received by a business operator is generated based on the information received from the financial institution. In this way, when a business operator transmits information to a financial institution, the financial-related information management device creates and transmits information such as a telegram that can be received by the financial institution-side management device. Also, when a financial institution transmits information to a business operator, the financial-related information management device creates and transmits information such as a telegram that can be received by the business operator management device.

[0008] In this way, since the financial-related information management device transmits information in the form of a telegram or the like that can be received by the financial institution-side management device and the business operator management device respectively, the business operator management device and the financial institution-side management device can exchange information with each other as they are without changing the conventional network system or the like at all. For example, since each financial institution-side management device adopts a separate API (Application Programming Interface), in order for the business operator management device to communicate with each financial institution-side management device, it was necessary to construct a network adapted to different APIs. On the other hand, in the present invention, since the financial-related information management device generates a telegram or the like adapted to the API of each financial institution-side management device, there is no need for the business operator management device to construct a network adapted to different APIs in order to communicate with each financial institution-side management device, and the conventional network or the like can be used as it is, and the cost can be significantly reduced.

[0013] In the present invention, the above object is achieved by a financial-related information management apparatus that can communicate with a user's terminal device, a management apparatus for a business operator that communicates with the terminal device, and a management apparatus for a financial institution that is a management apparatus of the financial institution, and that manages financial-related information Implemented in the control unit The control method is such that when the electronic money of the terminal device reaches a predetermined condition, the financial-related information management apparatus executes an automatic account withdrawal in which a withdrawal is automatically made from a deposit account of a financial institution and a predetermined amount is increased. The execution of the automatic account withdrawal by the financial-related information management apparatus is permitted based on past automatic account withdrawal execution performance information, which is past automatic account withdrawal execution information, without the input of the user's financial institution password information being a condition. The financial-related information management apparatus stores registration-related information received from the user's terminal device as administrator-side user information, and when the administrator-side user information matches the registration-related information, which is the information received from the business operator management apparatus, the financial-related information management apparatus generates transmission information to the financial institution that can be received by the financial institution and generates transmission information to the business operator that can be received by the business operator management apparatus based on the information received from the financial institution. A control method of a financial-related information management apparatus is characterized by Implemented in the control unit being achieved.

[0014] In the present invention, the above object is achieved by providing a financial-related information management apparatus that can communicate with a user's terminal device, a management apparatus for a business operator that communicates with the terminal device, and a management apparatus for a financial institution that is a management apparatus of the financial institution, and that manages financial-related information. When the electronic money of the terminal device reaches a predetermined condition, the financial-related information management apparatus has a function of executing an automatic account withdrawal in which a withdrawal is automatically made from a deposit account of a financial institution and a predetermined amount is increased. The execution of the automatic account withdrawal does not require the input of the user's financial institution password information, and the execution of the automatic account withdrawal is permitted based on past automatic account withdrawal execution performance information, which is past automatic account withdrawal execution information. Based on the Received from the terminal device registration-related information The function of storing it as administrator-side user information, and when the administrator-side user information matches the registration-related information which is the information received from the business operator management device, the administrator-side user information the financial-related information management apparatus generates transmission information to the financial institution that can be received by the financial institution and, based on the information received from the financial institution, the business operator management apparatus can receive naIt is achieved by a control program for a financial-related information management device, which is configured to execute a function of generating information to be transmitted to a business operator.

Advantages of the Invention

[0015] As described above, the present invention can provide a financial-related information management device, a control method for the financial-related information management device, and a control program for the financial-related information management device, which can ensure the safety of transactions without requiring complicated procedures from users when withdrawing money from a deposit account of a financial institution when charging (depositing) electronic money such as electronic money.

Brief Description of the Drawings

[0016]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Mode for Carrying Out the Invention

[0017] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings and the like. Note that the embodiments described below are preferred specific examples of the present invention, and thus are technically preferably subject to various limitations. However, the scope of the present invention is not limited to these aspects unless otherwise specified in the following description to limit the present invention.

[0018] FIG. 1 is a schematic explanatory diagram showing, for example, an "electronic money information management system 1" having a management server 40, which is a "financial-related information management device" according to an embodiment of the present invention. As shown in FIG. 1, this system 1 includes, for example, a terminal device 10 held by a user who uses or wishes to use an electronic money such as X Pay, and a merchant who handles an electronic money such as X PayUsage For example, it has a management device such as the operator server 20 and a management device on the financial institution side such as a bank, for example, the bank server 30.

[0019] Also, the system 1 has a financial-related information management device such as a management server 40 that manages financial-related information such as the account information of users among these terminal devices 10, an operator management device such as the operator server 20, and the bank server 30. Also, as shown in FIG. 1, these terminal devices 10, operator servers 20, management servers 40, etc. are connected to be mutually communicable via the Internet network 2, base stations 3, etc. Furthermore, as shown in FIG. 1, the management server 40 is configured to be communicable with the bank server 30.

[0020] As shown in FIG. 1, the terminal device 10 has, for example, an input device and a display unit, such as a "touch panel 11". Here, the "touch panel 11" is an electronic component that combines, for example, a display, which is a display unit, and a position input device, and is an input device that can input various information when the user touches the display on the display. Also, the terminal device 10 shown in FIG. 1 has a terminal device side communication device (not shown).

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

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

[0023] FIG. 3 and FIG. 4 are schematic block diagrams showing the main configurations of the "first various information storage unit 200 on the operator server side" and the "second various information storage unit 210 on the operator server side", respectively. These details will be described later.

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

[0025] FIGS. 6 to 10 are schematic block diagrams showing the main configurations of the "first various information storage unit 400 on the management server side" to the "fifth various information storage unit 440 on the management server side", respectively. These details will be described later.

[0026] (Regarding the bank server 30) FIG. 11 is a schematic block diagram showing the main configuration of the bank server 30 in FIG. 1. As shown in FIG. 11, the bank server 30 has a "bank-side control unit 31", and the control unit 31 controls a "bank-side communication device 32", a "bank-side display 33", a "bank-side various information input device 34", a "first various information storage unit 300 on the bank server side", and a "second various information storage unit 310 on the bank server side".

[0027] FIGS. 12 and 13 are schematic block diagrams showing the main configurations of the "first various information storage unit 300 on the bank server side" and the "second various information storage unit 310 on the bank server side". This content will be described later.

[0028] (Regarding the operation example of the electronic money management system 1) Hereinafter, an operation example and the like of the "electronic money management system 1" according to the present embodiment will be described. In the present embodiment, first, a user who wishes to use X electronic money operates the terminal device 10 shown in FIG. 1, accesses the merchant server 20 of the merchant handling X electronic money via the Internet network 2 or the like, and performs a "registration procedure" to make it available. The "user registration process" will be described.

[0029] FIGS. 14 to 16 are main schematic flowcharts showing the user registration process, and FIGS. 17 to 19 are main schematic flowcharts showing the user's charging process (at any time). Also, FIG. 20 is a main schematic flowchart showing the user's automatic account withdrawal (auto-charge, etc.) registration process, and FIGS. 21 to 23 are schematic flowcharts showing the execution process of automatic account withdrawal (auto-charge, etc.).

[0030] First, the user registration process will be described. Next, the "charging process at each time" in which a registered user operates the terminal device 10 in FIG. 1 and charges X electronic money from his / her own bank account via the Internet network 2 or the like will be described. Thereafter, the automatic account withdrawal registration process and its execution process will be described.

[0031] Here, the per-time charging process refers to a process for the user to change the cash in their own bank account into X electronic currency that can be used by the terminal device 10 at any timing as needed by the user, and is a process different from the automatic account withdrawal process, such as the auto-charging process, which automatically changes the cash in the user's bank account into X electronic currency that can be used by the terminal device 10 under predetermined conditions described later.

[0032] (User registration process) First, in step (hereinafter referred to as "ST") 1 of FIG. 14, a user who wishes to use X electronic currency (such as X Pay) operates their own terminal device 10 in FIG. 1 and accesses the business operator server 20 of the X electronic currency (such as X Pay) in FIG. 1 via the Internet network 2 or the like.

[0033] Next, it proceeds to ST2. In ST2, the "business operator side registration reception processing unit (program) 201" in FIG. 3 of the business operator server 20 in FIG. 1 operates and refers to the "registration reception information storage unit 202" in FIG. 3. In the same storage unit 202, matters to be displayed as registration information on the touch panel 11 of the terminal device 10, for example, basic reception information (such as "Kana name, date of birth, bank name, branch name, item name, account number, etc.") are stored. Therefore, the same processing unit 201 displays a screen on the touch panel 11 of the terminal device 10 requesting the input of "basic reception information (such as "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.

[0034] Next, it proceeds to ST3. In ST3, when the input to the terminal device 10 by the user is completed, the connection with the terminal device 10 is automatically changed from the business operator server 20 to the management server 40, and the "management side registration reception processing unit (program) 401" in FIG. 6 of the management server 40 operates, and the management server 40 requests the input of "current balance" and "password" on the touch panel 11 of the terminal device 10. In addition, the input of "Kana name", "Date of birth", "Occupation", "Purpose of use", "Phone number", "Account (deposit account) information (branch name, (deposit) type, account number)" is also required. These "current balance" and "PIN number", etc. are examples of registration-related information and financial institution identification information.

[0035] Next, proceed to ST4. In ST4, when the input of "current balance (for example, 1,000,000 yen)", "PIN number (for example, 5678)", "Kana name", "Date of birth", "Occupation", "Purpose of use", "Account information (branch name, type, account number)", etc. by the user is completed, the same processing unit 401 of the management server 40 operates, and stores these information in the "management-side user information" of the "management-side user information storage unit 402" in FIG. 6.

[0036] FIG. 24 is a schematic explanatory diagram showing the "management-side user information (part 1)" stored in ST4. As shown in FIG. 24, at this stage, "user ID", "Kana name", "bank name", "branch name", "type name", "account number", "current balance", "PIN number", "date of birth", "purpose of use", "occupation", "phone number", etc. are stored as management-side user information.

[0037] In this way, in the present embodiment, the user's "current balance" and "PIN number" are not input to the operator server 20. Therefore, the PIN number, account number, etc. do not leak to the electronic money operator, and the spread of these can be prevented in advance.

[0038] Next, proceed to ST5. In ST5, the management server 40 receives the data of "Kana name" and "date of birth" from the operator server 20, and determines whether they match the "Kana name" and "date of birth" input to the operator server 20 and the "Kana name" and "date of birth" input to the management server 40.

[0039] 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. In this "MS information storage unit 404", the magnetic stripe (MS) information of the cash cards of each bank is stored. Here, the MS information is the information stored in the cash card of each bank, and the account number etc. are stored in an encrypted manner.

[0040] Also, the acquisition unit 403 refers to the "bank name (for example, ABC Bank)" of the user ID in the management-side user information (part 1) in FIGS. 6 and 24, acquires the magnetic stripe (MS) information of the cash card of the bank (for example, ABC Bank), and stores it in the "management-side user information storage unit 402" in FIG. 6.

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

[0042] Next, proceed to ST7. In ST7, the "first bank-directed transmission message (for example, ATM message) creation unit (program) 405" in FIG. 6 of the management server 40 operates, and acquires "bank name (ABC Bank)", "branch name (Osaki Branch)", "item name (ordinary)", "account number (1234567)", "MS information (····)", "PIN (5678)" from the management-side user information (part 2) in the management-side user information storage unit 402 in FIGS. 6 and 25, creates the "first bank-directed transmission message", and stores it in the "first bank-directed transmission message storage unit 406" in FIG. 6.

[0043] Here, the "first bank-directed transmission message" is an example of the information transmitted to a financial institution, and is a message that can be received by a financial institution such as a bank. In this embodiment, for example, it is a message conforming to an API (Application Programming Interface) that can be received by ABC Bank. Note that although bank-oriented messages use different APIs for each bank, the management server 40 of the present embodiment has acquired information on the APIs of each bank, and thus can create a message that conforms to the relevant bank (e.g., ABC Bank).

[0044] Therefore, even if an operator acquires user information, by transmitting that information to the management server 40, it can be transmitted to the bank server 30. The operator does not need to construct a network in accordance with the different APIs for each bank, and can communicate with the bank at extremely low cost. In addition, since the bank can also communicate with the management server 40 using the API network it has been using conventionally, there is no need to newly construct a network, and communication can be carried out at extremely low cost.

[0045] Next, proceed to ST8. In ST8, the management server 40 transmits the message in the "First Bank-Directed Transmission Message Storage Unit 406" of FIG. 6 to the "bank server 30". After transmission, the management server 40 deletes the "password" in the management-side user information (Part 2) of FIG. 25 and the "password" in the "First Bank-Directed Transmission Message" in the "First Bank-Directed Transmission Message Storage Unit 406" of FIG. 6 from storage.

[0046] In this way, in the present embodiment, the "password", which is extremely important to the user, is not left not only in the operator server 20 but also in the "management server 40", resulting in an extremely secure system.

[0047] Next, proceed to ST9. In ST9, the "Password Verification Processing Unit (Program) 301" in FIG. 12 of the bank server 30 operates to acquire the "password" information of the relevant account of the bank server 30 from the "account number" etc. of the received "First Bank-Directed Transmission Message". Then, the password in the first bank-directed transmission message is verified against the password of the bank server 30.

[0048] Next, proceed to ST10. In ST10, when the bank server 30 verifies the PIN of the user's account and the PINs match exactly, the "Current Balance-Included Bank-Destination Transmission Message Creation Unit (Program) 302" in FIG. 12 of the bank server 30 operates. Then, a "Current Balance-Included Bank-Destination Transmission Message" including the "current balance" of the account in the bank server 30 for the relevant account is created and stored in the "Current Balance-Included Bank-Destination Transmission Message Storage Unit 303" in FIG. 12. This "Current Balance-Included Bank-Destination Transmission Message" also includes the "Kana name", "date of birth", "flag for identifying whether the identity has been verified at the bank (identity verification flag)", and "flag for identifying whether it is an individual or a corporation (individual / corporation identification flag)" of the account holder as grasped by the bank. Note that this PIN is an example of authentication information.

[0049] This Current Balance-Included Bank-Destination Transmission Message is created as a message conforming to the API of the relevant bank. As shown in FIG. 12, it includes information such as the bank name (ABC_bank), branch name (Osaki_Branch), item name (ordinary), account number (1234567), MS number (abvdefg), PIN (efgh), and the current balance on the bank side (1,000,000 yen).

[0050] In this step, the bank server 30 determines whether the "PIN" input by the user on the terminal device 10 is accurate.

[0051] Next, proceed to ST11. In ST11, the bank server 30 transmits the "Current Balance-Included Bank-Destination Transmission Message" in the "Current Balance-Included Bank-Destination Transmission Message Storage Unit 303" in FIG. 12 to the management server 40.

[0052] Next, proceed to ST12. In ST12, the "Current Balance-Included Business-Operator-Destination Transmission Message Creation Unit (Program) 407" in FIG. 6 of the management server 40 operates to convert the received "Current Balance-Included Bank-Destination Transmission Message" into a "Current Balance-Included Business-Operator-Destination Transmission Message". And it is stored in the "Current Balance-Included Business-Operator-Destination Transmission Message Storage Unit 411" in FIG. 7.

[0053] Here, the "message for sending to operators with current balance" in the message for sending to operators is an example of the transmission information for operators that the operator server 20 can receive. In this way, in the present embodiment, since the management server 40 converts a special message for banks into a message for operators, the operator does not need to construct a new network conforming to the API adopted by the bank for communication with the bank in particular, and the communication cost can be kept low.

[0054] As described above, in the present embodiment, since the management server 40 and the operator server 20 each transmit information in a message that can be received, the bank server 30 and the operator server 20 can exchange information as they are without changing the conventional network system or the like at all. For example, since each bank server 30 of each bank adopts a different API, the operator server 20 needs to construct a network conforming to the different APIs in order to communicate with each bank server 30. On the contrary, in the present embodiment, since the management server 40 generates a message conforming to the API of each bank server 30, the operator server 20 does not need to construct a network conforming to the different APIs in order to communicate with the bank server 30, and the conventional network or the like can be used as it is, and the cost can be greatly reduced.

[0055] Next, proceed to ST13. In ST13, the "information comparison unit (matching) (program) 412" of the management server 40 operates, and compares the "Kana name", "date of birth", and "bank-side current balance (1,000,000 yen)" in the "message for sending to operators with current balance" in the "message storage unit for sending to operators with current balance 411" in FIG. 7 with the "Kana name", "date of birth", and "current balance (1,000,000 yen)" in the "management-side user information (part 2)" in the "management-side user information storage unit 402" in FIGS. 6 and 25 to determine whether the data matches. If it matches and 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, the confirmation of the identity of the person and the confirmation that the account holder is an individual, etc. are executed based on the "Telegram for Sending to Business Operators with Current Balance" in FIG. 7.

[0056] FIG. 26 is a schematic explanatory diagram showing management-side user information indicating a state where the "Use Permission Flag" is set in ST13. As shown in FIG. 26, the "Use Permission Flag" is set in the management-side user information (No. 3). Here, the current balance is an example of balance information.

[0057] As described above, in this embodiment, the bank server 30 confirms the match between the password entered by the user and the registered password of the user's cash card. Further, 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. When these match, and furthermore, when the identity of the person has been confirmed at the bank and it has been confirmed that the account holder is an individual, etc., the "Use Permission Flag" is set only in such cases. Therefore, the user's identity authentication can be reliably performed.

[0058] In particular, in this embodiment, the verification of the password is performed by a different institution from the management server 40 for the verification of the bank server 30, the current balance, etc., so that a more reliable identity authentication is possible.

[0059] Next, proceed to ST14. In ST14, the "Use Period Information (Token) Generation Unit (Program) 413" in FIG. 7 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 (No. 4)" in which the "Token Information" is stored in ST14. As shown in FIG. 27, by adding information that limits the validity period of the user flag, the certainty of identity authentication is ensured.

[0060] Next, proceed to ST15. In ST15, the "User Information Generation Unit (Program) 414 for Sending to Merchant Server" 414 in FIG. 7 of the management server 40 operates to generate "Information for Sending to Merchant Server" and stores it in the "Information Storage Unit 415 for Sending to Merchant Server" in FIG. 7. This information for sending to the merchant server is generated as a message for sending to the merchant that can be received by the merchant server 20, and is limited to the information necessary for the merchant, and does not include the PIN of the user's cash card or the current balance information of the bank account.

[0061] Specifically, as the "Information for Sending to Merchant Server" in FIG. 7, it includes merchant ID (for example, 2001), user ID (for example, 10001), kana name, bank name (for example, ABC Bank), branch name (for example, Oosaki Branch), item name (for example, regular), account number (for example, 1234567), token (for example, 20200130) information, etc.

[0062] Thus, in this embodiment, the merchant can communicate with the bank server 30 via the management server 40 without changing the conventional system, and the configuration is such that confidential information of the user cannot be obtained. Therefore, it is easy to use for the merchant and can automatically obtain the necessary information, while for the user, it is a highly secure system.

[0063] Next, proceed to ST16. In ST16, the management server 40 transmits the "Information for Sending to Merchant Server" in the "Information Storage Unit 415 for Sending to Merchant Server" to the merchant server 20.

[0064] Next, proceed to ST17. In ST17, the merchant server 20 stores the "User Information on the Merchant Side" in the "User Information Storage Unit 203 on the Merchant Side" in FIG. 3 of the merchant server 20 based on the received "Information for Sending to Merchant Server". Specifically, as shown in the "Business Operator Side User Information Storage Unit 203" of FIG. 3, the business operator ID (for example, 2001), user ID (for example, 10001), kana name, bank name (for example, ABC Bank), branch name (for example, Oosaki Branch), item name (for example, regular), account number (for example, 1234567), token (for example, 20200130) information, etc. are stored.

[0065] Thereby, the business operator server 20 can automatically acquire the necessary information of the users who use the X electronic currency.

[0066] Next, proceed to ST18. In ST18, the management server 40 displays a registration completion screen on the touch panel 11 with the terminal device 10, and the "user registration" is completed.

[0067] (Per-charge process) For the users who have completed the registration for using the X electronic currency, the process of "charging each time", that is, changing the cash in their own bank account to the X electronic currency available on the terminal device 10 for using the X electronic currency will be described below. First, in ST21 of FIG. 17, the user who wishes to charge the electronic currency accesses the business operator server 20 of the electronic currency with their own terminal device 10.

[0068] Next, proceed to ST22. In ST22, the "Charge Each Time Reception Processing Unit (Program) 204" of FIG. 3 of the business operator server 20 operates, and an input screen for, for example, the charge amount each time, which is the charge each time information, is displayed on the touch panel 11 of the terminal device 10.

[0069] Next, proceed to ST23. In ST23, when the input is completed, the same processing unit 204 operates and stores the charge amount each time in the "Business Operator Side Charge Each Time Reception Information Storage Unit 205" of FIG. 3. In the business operator side charge each time reception information storage unit 205 of FIG. 3, the "bank name (for example, ABC Bank)", "branch name (for example, Oosaki Branch)", "item name (for example, regular)", "account number (for example, 124567)", "charge amount each time (for example, 1,000 yen)" are stored.

[0070] Next, proceed to ST24. At ST24, the connection with the terminal device 10 is automatically changed from the operator server 20 to the management server 40, and the operator server 20 transmits the "operator-side charge reception information" in the "operator-side per-time charge reception information storage unit 205" of FIG. 3 to the management server 40.

[0071] Next, proceed to ST25. At ST25, the management server 40 stores the received "operator-side charge reception information" as "management-side charge reception information" in the "management-side per-time charge reception information storage unit 421" of FIG. 8. FIG. 28 is a schematic explanatory diagram showing the content of the "management-side charge reception information (Part 1)" stored in the "management-side per-time charge reception information storage unit 421" at ST25. As shown in FIG. 28, the "management-side charge reception information (Part 1)" is as follows. "Bank name (e.g., ABC Bank)", "Branch name (e.g., Osaki Branch)", "Item name (e.g., Regular)", "Account number (e.g., 1234567)", "Per-time charge amount (e.g., 1,000 yen)"

[0072] Next, proceed to ST26. At ST26, the "password request unit (program) 422" in FIG. 8 of the management server 40 operates, and a password input screen is displayed on the touch panel 11 of the terminal device 10.

[0073] Next, proceed to ST27. At ST27, when there is an input, the same request unit 422 of the management server 40 stores the input "password (e.g., 5678)" in the "management-side per-time charge reception information storage unit 421" of FIG. 8.

[0074] FIG. 29 is a schematic explanatory diagram showing the content of the "management-side charge reception information (Part 2)" stored in the "management-side per-time charge reception information storage unit 421" at ST27. As shown in FIG. 29, the "management-side charge reception information (Part 2)" is as follows. "Bank name (e.g., ABC Bank)", "Branch name (e.g., Oosaki Branch)", "Item name (e.g., Regular)", "Account number (e.g., 1234567)", "Charge amount per time (e.g., 1,000 yen)", "PIN (e.g., 5678)"

[0075] Thus, in this embodiment, the PIN input by the user is directly input to the management server 40 instead of the operator server 20. Therefore, the operator can obtain no unnecessary information, and the user can ensure the confidentiality of the PIN.

[0076] Next, proceed to ST28. In ST28, the "User determination unit (program) 423" in FIG. 8 of the management server 40 operates, and compares the "Per-time charge reception information" in the "Management-side per-time charge reception information storage unit 421" in FIG. 8 with the "Management-side user information" in the "Management-side user information storage unit 402" of FIG. 6 of the management server 40. Specifically, compare the "Management-side per-time charge reception information (Part 2)" in FIG. 29 with the "Management-side user information (Part 4)" in FIG. 27 to determine whether the information matches. If it matches, store the information of "Per-time charge amount", "Transaction ID", and "Transaction date and time" in the "Management-side user information storage unit 402" of FIG. 6.

[0077] FIG. 30 is a schematic explanatory diagram showing the management-side user information (Part 5) with the information of "Per-time charge amount", "Transaction ID", and "Transaction date and time" added in ST28. As shown in FIG. 30, the information of "Per-time charge amount (e.g., 1,000 yen)", "Transaction ID (····)", and "Transaction date and time (····)" is stored in the management-side user information (Part 5).

[0078] Thus, in this embodiment, even for a user who has gone through the registration process, when charging, the management server 40 authenticates the user again, resulting in a more secure system.

[0079] Next, proceed to ST29. In ST29, the "Second Bank Transmission Message Creation Unit (Program) 424" in FIG. 8 of the management server 40 operates, and 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 Per-Transaction Charge Reception Information (Part 2)" in FIG. 29 of the "Management-Side Per-Transaction Charge Reception Information Storage Unit 421" in FIG. 8, a "Second Bank Transmission Message", for example, an ATM message, is created and stored in the "Second Bank Transmission Message Storage Unit 425" in FIG. 8.

[0080] Specifically, as shown in FIG. 8, the content of the "Second Bank Transmission Message" is as follows. "Bank Name (e.g., ABC_bank)", "Branch Name (e.g., Osaki_branch)", "Item Name (Ordinary)", "Account Number (e.g., 1234567)", "MS Information (e.g., Abcdefg)", "Password (e.g., efgh)", "Charge Method Classification (0)", "Password Check Classification (0)", "Per-Transaction Charge Amount (e.g., 1,000 yen)"

[0081] Here, the charge method classification indicates the classification of per-transaction charge or auto-charge (automatic account withdrawal), and "0" means per-transaction charge. Also, the "Password Check Classification" indicates the necessity of password check, and "0" means check is required. Since password check is not required for auto-charge but is required for per-transaction charge, here it is "Check Required (0)".

[0082] Next, proceed to ST30. In ST30, the management server 40 transmits the "Second Bank Transmission Message" in the "Second Bank Transmission Message Storage Unit 425" in FIG. 8 to the "Bank Server (ABC Bank) 30". And then, the information of the "Password" in the "Second Bank Transmission Message" is deleted.

[0083] Therefore, since the management server 40 does not hold the password of the user's highly confidential cash card, it has a configuration that enhances security.

[0084] Next, proceed to ST31. In ST31, the "Withdrawal Judgment Processing Unit (Program) 304" in FIG. 12 of the bank server 30 operates to determine whether the "Charge Amount Each Time" is withdrawable. If it is possible, a withdrawal (1,000 yen) process (accounting process) is performed. Then, a "Withdrawal Completed Bank Transmission Message" is generated and stored in the "Withdrawal Completed Bank Transmission Message Storage Unit 305" in FIG. 12.

[0085] Next, proceed to ST32. In ST32, the bank server 30 transmits the "Withdrawal Completed Bank Transmission Message" in the "Withdrawal Completed Bank Transmission Message Storage Unit 305" in FIG. 12 to the management server 40.

[0086] Next, proceed to ST33. In ST33, the management server 40 stores the received "Withdrawal Completed Bank Transmission Message" in the "Management-Side Withdrawal Completed Bank Transmission Message Storage Unit 426" in FIG. 8.

[0087] Next, proceed to ST34. In ST34, the "Business Operator Transmission Message Conversion Processing Unit (Program) 427" in FIG. 8 of the management server 40 operates to convert the "Management-Side Withdrawal Completed Bank Transmission Message" in the "Management-Side Withdrawal Completed Bank Transmission Message Storage Unit 426" in FIG. 8 into a "Management-Side Withdrawal Completed Business Operator Transmission Message" and stores it in the "Management-Side Withdrawal Completed Business Operator Transmission Message Storage Unit 431" in FIG. 9.

[0088] Therefore, similar to the above-described user registration process, the management server 40 generates and transmits a transmission message for the bank server 30 and a transmission message for the business operator server 20. Thus, the business operator and the bank can use the system as it is without changing the conventional system, and the present system 1 can be used at low cost.

[0089] Next, proceed to ST35. In ST35, the management server 40 stores the "Transaction Result (Withdrawal) (for example, 1,000 yen)" in the "Management-Side Withdrawal Completed Business Operator Transmission Message" in the "Management-Side Withdrawal Completed Business Operator Transmission Message Storage Unit 431" in FIG. 9 in the "Management-Side User Information Storage Unit 402" in FIG. 6.

[0090] FIG. 31 is a schematic explanatory diagram showing "Administrator-side User Information (No. 6)" with "Transaction Result (Withdrawal)" added in ST35. As shown in FIG. 31, the management server 40 is configured to manage user information excluding the password.

[0091] Next, proceed to ST36. In ST36, the management server 40 displays on the touch panel 11 of the terminal device 10 that 1000 yen has been deposited as electronic money in the charge.

[0092] Next, proceed to ST37. In ST37, when an approval input is made with the terminal device 10, a transaction end signal is transmitted to the merchant server 20.

[0093] Next, proceed to ST38. In ST38, the merchant server 20 acquires a "Transmission Message for Merchant after Withdrawal on the Management Side" from the management server 40, and adds and stores "Transaction Result (Withdrawal)" information and the like to the "Merchant-side User Information" in the "Merchant-side User Information Storage Unit 203" of FIG. 3.

[0094] In the charge process of the present embodiment, since the communication with the terminal device 10 is automatically changed to the management server 40 instead of the merchant server 20 from ST24, for example, transaction result (withdrawal) information, which is charge-related information, cannot be obtained by the merchant server 20. Therefore, when the transaction ends in ST37, the signal is transmitted from the terminal device 10 to the merchant server 20, and the merchant server 20 is configured to be able to acquire information such as the transaction result (withdrawal) from the management server 40. That is, confidential information such as the password is not input to the merchant server 20, and necessary information such as the transaction result (withdrawal) does not leak quickly and can be acquired by the merchant server 20.

[0095] In addition, according to the present embodiment, even if the communication between the merchant server 20, the bank server 30, and the management server 40 is interrupted, the merchant side can confirm the consistency of the transaction results between the merchant server 20 and the management server 40 and the bank server 30 and perform correction in case of inconsistency.

[0096] (Automatic account withdrawal (auto-charge, etc.) registration process) Next, a registration process will be described in which a user who has completed registration for using X electronic money "automatically withdraws from an account", that is, when the X electronic money available on the terminal device 10 reaches a predetermined amount (for example, 1,000 yen or less), automatically withdraws cash (10,000 yen) from his or her own bank account and changes it to the X electronic money on the terminal device 10.

[0097] FIG. 20 is a schematic flowchart showing the automatic account withdrawal registration process. First, in ST41 of FIG. 20, a user who wishes to auto-recharge X electronic money accesses the electronic money merchant server 20 with his or her own terminal device 10.

[0098] Next, the process proceeds to ST42. In ST42, the "automatic account withdrawal (for example, auto-recharge) reception processing unit (program) 211" in FIG. 4 of the merchant server 20 operates, and on the touch panel 11 of the terminal device 10, an input screen for the automatic account withdrawal amount (for example, 10,000 yen), which is the automatic account withdrawal information (for example, auto-recharge withdrawal), and the execution amount of the automatic account withdrawal (for example, the auto-recharge execution amount, 1,000 yen) is displayed.

[0099] Next, when the input is completed, the process proceeds to ST43. In ST43, the same processing unit 211 operates to store the auto-recharge withdrawal amount (10,000 yen) and the auto-recharge execution amount (1,000 yen) in the "merchant-side automatic account withdrawal reception information storage unit 212" in FIG. 4. In the "Merchant-Side Automatic Account Withdrawal Reception Information Storage Unit 212", information such as "Bank Name (e.g., ABC Bank)", "Branch Name (e.g., Oosaki Branch)", "Account Type Name (e.g., Regular)", "Account Number (e.g., 124567)", "Auto-Charge Withdrawal Amount (e.g., 10,000 yen)", "Executed Amount of Auto-Charge (e.g., 1,000 yen)" is stored. With the above, the registration process of the automatic account withdrawal (auto-charge) of X electronic currency is completed.

[0100] (Execution process of automatic account withdrawal (auto-charge)) Figure 21 is a schematic flowchart showing the execution process of automatic account withdrawal. Following Figure 21, the same process will be described below. First, in ST51 of Figure 21, the "Automatic Account Withdrawal Reception Processing Unit (Program) 211" in Figure 4 of the merchant server 20 operates, referring to the balance information of X electronic currency of the terminal device 10 in the "Per-Terminal Device Electronic Currency Balance Information Storage Unit 213" in Figure 4 of the business office server 20 and the "Automatic Account Withdrawal Execution Amount (1,000 yen)" in the "Merchant-Side Automatic Account Withdrawal Reception Information Storage Unit 212" in Figure 4, and determines whether the balance information corresponds to the automatic account withdrawal execution amount. If it corresponds, this "Merchant-Side Automatic Account Withdrawal Reception Information" is transmitted to the management server 40.

[0101] Next, it proceeds to ST52. In ST52, the "Merchant-Side Automatic Account Withdrawal Reception Information" received from the merchant server 20 is stored in the "Management-Side Automatic Account Withdrawal Reception Information Storage Unit 432" in Figure 9.

[0102] Next, it proceeds to ST53. In ST53, when the "Tentative Total Withdrawal Execution Times Generation Unit (Program) 433" in Figure 9 operates and receives the "Merchant-Side Automatic Account Withdrawal Reception Information" from the merchant server 20, tentatively, that is, assuming that the withdrawal has been executed, it adds it to the "Withdrawal Execution Times" for the day regarding the merchant, and stores the total number of times as the tentative total withdrawal execution times for the execution day in the "Tentative Total Withdrawal Execution Times Storage Unit 434" in Figure 9.

[0103] Next, proceed to ST54. In ST54, the "Withdrawal Limit and Other Standard Information Generation Unit (Program) 436" in FIG. 9 operates and refers to the "Automatic Account Withdrawal History Information Storage Unit 435" in FIG. 9. Here, the "Automatic Account Withdrawal History Information Storage Unit 435" is configured to store the total number of withdrawal execution times per day for each electronic money operator for each terminal device 10 and the like. This number of withdrawal executions is calculated based on the number of times of withdrawal execution by the bank server 30.

[0104] Also, this number of withdrawal executions is configured to preferentially store the maximum value (number of times) in a single day in the past. In the case of a number of times exceeding the maximum value of a single day that is preferentially stored, the previous maximum value is updated.

[0105] Then, the generation unit 436 determines the "withdrawal limit standard number of times" and the "withdrawal stop standard number of times" calculated by multiplying a certain ratio based on the maximum value of the number of withdrawal executions in a single day in the past of the "Automatic Account Withdrawal History Information Storage Unit 435", and stores them in the "Withdrawal Limit and Other Standard Information Storage Unit 437" in FIG. 9.

[0106] At this time, when the maximum value of the number of executions in a single day in the past is less than the arbitrarily set lower limit number of withdrawal executions, the "withdrawal limit standard number of times" and the like are determined based on this lower limit number of withdrawal executions value instead of the maximum value in the past, and are stored respectively. Therefore, for example, even when the number of automatic account withdrawals (such as auto - recharge) in the past is small, like immediately after the start of automatic account withdrawals, it is possible to avoid in advance the situation of not permitting automatic account withdrawals.

[0107] Next, proceed to ST55. In ST55, the "Automatic Account Withdrawal Monitoring Section (Program) 442" in FIG. 10 operates, and it determines whether the provisional total number of executed account withdrawals in the "Provisional Total Number of Executed Account Withdrawals Storage Section 434" in FIG. 9 has reached the "Withdrawal Limit Standard Number" or the "Withdrawal Stop Standard Number" in the "Withdrawal Limit and Other Standard Information Storage Section 437" in FIG. 9. When the provisional total number of executed account withdrawals reaches the "Withdrawal Limit Standard Number" but has not reached the "Withdrawal Stop Standard Number", "Warning Information" is generated, the "Warning Information" is sent to the operator of the management server 40, and the "Warning Information" is stored in the "Monitoring Result Information Storage Section 441" in FIG. 10, and then proceed to the "Withdrawal Limit Information Related Process" described later.

[0108] Also, when the provisional total number of executed account withdrawals has reached the "Withdrawal Stop Standard Number", "Stop Information" is generated, the "Stop Information" is sent to the administrator of the management server 40, and the "Stop Information" is stored in the "Monitoring Result Information Storage Section 441" in FIG. 10, and then proceed to the "Withdrawal Stop Information Related Process" described later. Furthermore, when the provisional total number of executed account withdrawals has not reached the "Withdrawal Limit Standard Number", proceed to the "Normal Process" described later.

[0109] As described above, in this embodiment, when executing an automatic account withdrawal (for example, auto-charge, etc.), based on the execution performance information of the automatic account withdrawal in the past (for example, the number of executed withdrawals per day for each operator, etc.), the automatic account withdrawal is classified into any one of "Normal", "Warning (Withdrawal Limit)", or "Stop (Withdrawal Stop)", and different processes are performed, thereby preventing inappropriate automatic account withdrawals in advance.

[0110] 。 Hereinafter, each of the "Normal Process", the "Withdrawal Limit Information Process", and the "Withdrawal Stop Information Process" will be described in detail.

[0111] (Normal process) FIG. 22 and FIG. 23 are schematic flowcharts showing the main processes of the "Normal Process". Hereinafter, the "Normal Process" in this embodiment will be described along with the schematic flowchart. First, in ST70 of FIG. 22, when the management server 40 refers to the "monitoring result information storage unit 441" in FIG. 10 and determines that no "warning information" or "stop information" is stored in the storage unit 441, it determines that it is "normal", generates a "transmission telegram for automatic account withdrawal to the bank", and stores it in the "transmission telegram storage unit for automatic account withdrawal to the bank 443" in FIG. 10.

[0112] Specifically, as shown in FIG. 10, the content of the "transmission telegram for automatic account withdrawal to the bank" is as follows. "Bank name (e.g., ABC Bank)", "branch name (e.g., Oosaki Branch)", "category name (e.g., ordinary)", "account number (e.g., 1234567)", "amount of automatic account withdrawal (e.g., 10,000 yen)", "MS information (e.g., Abcdefg)". In the case of automatic account withdrawal, add that the "charge method classification" of the MS information is "automatic account withdrawal (1)" and the "PIN check classification" is "check not required (1)".

[0113] Next, proceed to ST71. In ST71, the management server 40 transmits the "transmission telegram for automatic account withdrawal to the bank" to the bank server 30. In ST72, the bank server 30 operates the "withdrawal determination processing unit (program) 311" in FIG. 13 to determine whether the "amount of automatic account withdrawal" is withdrawable. If it is possible, perform a withdrawal (10,000 yen) process (accounting process). Then, proceed to ST73, and the bank server 30 generates a "telegram for bank transmission after withdrawal" and stores it in the "telegram storage unit for bank transmission after withdrawal 312" in FIG. 13.

[0114] Here, since the bank server 30 does not confirm the "PIN", the management server 40 does not need to transmit the "PIN" information to the bank server 30 either. Therefore, since the user of the terminal device 10 is not forced to input the "PIN", it is an easy-to-use system. Also, instead of forcing the user to input the PIN, for example, it is configured to prevent inappropriate execution of automatic account withdrawal based on, for example, the "maximum total number of withdrawal executions in a day" for automatic account withdrawal.

[0115] Next, proceed to ST74. At ST74, the bank server 30 transmits the "Transmitted Bank Credit Transfer Message for Withdrawal" in the "Transmitted Bank Credit Transfer Message Storage Unit 312" of FIG. 13 to the management server 40. Next, at ST75, the management server 40 stores the received "Transmitted Bank Credit Transfer Message for Withdrawal" in the "Management-Side Transmitted Bank Credit Transfer Message Storage Unit 444" of FIG. 10.

[0116] Next, proceed to ST76. At ST76, the "Message Conversion Processing Unit (Program) 445 for Sending to Business Operators" of the management server 40 in FIG. 10 operates, converts the "Management-Side Transmitted Bank Credit Transfer Message" in the "Management-Side Transmitted Bank Credit Transfer Message Storage Unit 444" of FIG. 10 into a "Management-Side Transmitted Message for Business Operators after Withdrawal", and stores it in the "Management-Side Transmitted Message Storage Unit 446 for Business Operators after Withdrawal" of FIG. 10. In this way, since the management server 40 generates and transmits the "Transmission Message for Bank Server" and the "Transmission Message for Business Operator Server", the business operator and the bank can be used as they are without changing the conventional system, and the present system 1 can be used at low cost.

[0117] Next, proceed to ST77. At ST77, the management server 40 stores the "Automatic Withdrawal of Transaction Result (for example, 10,000 yen)" in the "Management-Side User Information Storage Unit 402" of FIG. 6 from the "Management-Side Transmitted Message for Business Operators after Withdrawal" in the "Management-Side Transmitted Message Storage Unit 446 for Business Operators after Withdrawal" of FIG. 10.

[0118] FIG. 32 is a schematic explanatory diagram showing the "Management-Side User Information (No. 7)" with the "Transaction Result (Automatic Account Withdrawal)" added. As shown in FIG. 32, the management server 40 is configured to be able to manage user information excluding the password.

[0119] Next, proceed to ST78. At ST78, it is displayed on the touch panel 11 of the terminal device 10 that 10,000 yen has been automatically deposited as electronic money by automatic account withdrawal. Next, at ST79, when the terminal device 10 performs an approval input, a transaction completion signal is transmitted from the terminal device 10 to the management server 40.

[0120] Next, it proceeds to ST80. At ST80, a "Management-side Withdrawal Completed Transmission Message for Merchant" is transmitted from the management server 40 to the merchant server 20, and "Transaction Result (Automatic Account Withdrawal Transaction)" information and the like are added to and stored in the "Merchant-side User Information" in the "Merchant-side User Information Storage Unit 203" of FIG. 3.

[0121] However, if the transmission of "Transaction Result (Automatic Account Withdrawal Transaction)" information and the like from the management server 40 to the merchant server 20 is not completed normally within a predetermined time, the merchant server 20 is configured to be able to acquire information such as the transaction result (automatic account withdrawal) from the management server 40. With the above, the execution process of automatic account withdrawal in the case of being determined as "normal" ends.

[0122] (Process related to withdrawal limit information) In the "Withdrawal Limit Information Related Process", the management server 40 refers to the "Monitoring Result Information Storage Unit 441" in FIG. 10. If "Warning Information" is stored in the storage unit 441, the management server 40 provides the operator of the management server 40 with the details by email. Other processes are the same as in the case of being determined as "normal" above.

[0123] However, if "Stop Information" arbitrarily set by the operator of the management server 40 who has received the email of "Warning Information" is also stored, information indicating that automatic account withdrawal (such as auto-charge) is not possible is transmitted to the "merchant server 20" and the "terminal device 10" without transmitting the "Bank Transmission Message for Automatic Account Withdrawal" to the bank server 30. Therefore, inappropriate automatic account withdrawal is not executed, and its execution is prevented in advance.

[0124] (Regarding the "process related to withdrawal stop information") In the "Withdrawal Stop Information Related Process", when the management server 40 refers to the "Monitoring Result Information Storage Unit 441" in FIG. 10 and the "Stop Information" is stored in the storage unit 441, instead of transmitting the "Bank-Facing Automatic Account Withdrawal Transmission Telegram" to the bank server 30, information indicating that automatic account withdrawal is not possible is transmitted to the "Business Operator Server 20" and the "Terminal Device 10". Therefore, inappropriate automatic account withdrawals are not executed, and their execution is prevented beforehand.

[0125] As described above, in this embodiment, when executing an automatic account withdrawal (for example, auto-charge, etc.), based on the execution result information of past automatic account withdrawals (for example, the number of withdrawal executions per day for each business operator, etc.), the execution of the automatic account withdrawal is permitted. Therefore, inappropriate automatic account withdrawals can be prevented beforehand.

[0126] In the embodiment described above, the case of being realized as a device has been taken as an example for explanation. However, the present invention is not limited to this, and as a program that can be executed by a computer, it may be stored and distributed in a storage medium such as a magnetic disk (floppy (registered trademark) disk, hard disk, etc.), an optical disk (CD-ROM, DVD, etc.), a magneto-optical disk (MO), or a semiconductor memory.

[0127] Further, the storage medium only needs to be a storage medium that can store a program and is readable by a computer. The storage format of the storage medium is not particularly limited.

[0128] Also, based on the instructions of the program installed in the computer from the storage medium, an OS (operating system) operating on the computer, MW (middleware) such as database management software and network software, etc. may execute a part of each process for realizing this embodiment.

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

[0130] Also, the computer in the present invention may execute each process in the present embodiment based on the program stored in the storage medium, and may be a device composed of a single personal computer or the like, or may be a system in which a plurality of devices are network-connected.

[0131] Also, the computer in the present invention is not limited to a personal computer, and includes an arithmetic processing unit, a microcomputer, etc. included in an information processing device, and generally refers to devices and apparatuses capable of realizing the functions of the present invention by a program.

[0132] The embodiments of the present invention have been described above. However, the present invention is not limited to the above embodiments, and various changes can be made without departing from the scope of the claims. The configurations of the above embodiments can be partially omitted or arbitrarily combined differently from the above.

Explanation of Reference Numerals

[0133] 1 ··· Electronic money information management system, 2 ··· Internet network, 3 ··· Base station, 10 ··· Terminal device, 20 ··· Merchant server, 30 ··· Bank server, 40 ··· Management server, 200 ··· First various information storage units on the merchant server side, 210 ··· Second various information storage units on the merchant server side, 300 ··· First various information storage units on the bank server side, 310 ··· Second various information storage units on the bank server side, 400 ··· First various information storage units on the management server side, 410 ··· Second various information storage units on the management server side, 420 ··· Third various information storage units on the management server side, 430 ··· Fourth various information storage units on the management server side, 440 ··· Fifth various information storage units on the management server side

Claims

1. A financial-related information management device that manages financial-related information capable of communicating with a user's terminal device, a business operator management device that communicates with the terminal device, and a financial institution side management device that is a management device of a financial institution, when the electronic money of the terminal device reaches a predetermined condition, an automatic account withdrawal is executed in which money is automatically withdrawn from a deposit account of a financial institution and a predetermined amount is increased, input of the user's financial institution password information is not required as a condition for the execution of the automatic account withdrawal, the execution of the automatic account withdrawal is configured to be permitted based on past automatic account withdrawal execution performance information which is past automatic account withdrawal execution information, stores the registration-related information received from the user's terminal device as administrator-side user information, and when the administrator-side user information matches the registration-related information which is the information received from the business operator management device, based on the administrator-side user information, generates financial institution-destined transmission information that can be received by the financial institution, and based on the information received from the financial institution, generates business operator-destined transmission information that can be received by the business operator management device. A financial-related information management device characterized by this.

2. A control method implemented in a control unit of a financial-related information management device that manages financial-related information capable of communicating with a user's terminal device, a business operator management device that communicates with the terminal device, and a financial institution side management device that is a management device of a financial institution, when the electronic money of the financial-related information management device reaches a predetermined condition, the financial-related information management device executes an automatic account withdrawal in which money is automatically withdrawn from a deposit account of a financial institution and a predetermined amount is increased, the execution of the automatic account withdrawal of the financial-related information management device is permitted based on past automatic account withdrawal execution performance information which is past automatic account withdrawal execution information without the input of the user's financial institution password information being required as a condition, the financial-related information management device stores the registration-related information received from the user's terminal device as administrator-side user information, When the administrator-side user information matches the registration-related information received from the business operator management device, based on the administrator-side user information, the financial institution generates transmission information to the financial institution that can be received, and based on the information received from the financial institution, the business operator management device generates transmission information to the business operator that can be received. A control method implemented in a control unit of a financial-related information management device characterized by this.

3. In a financial-related information management device that manages financial-related information that can communicate with a user's terminal device, a business operator management device that is a management device of the business operator that communicates with the terminal device, and a financial institution-side management device that is a management device of the financial institution The electronic money of the terminal device has a function of automatically executing an automatic account withdrawal in which when a predetermined condition is met, money is withdrawn from a deposit account of a financial institution and a predetermined amount is increased. For the execution of the automatic account withdrawal, the input of the password information of the user's financial institution is not a condition, and the execution of the automatic account withdrawal is permitted based on the past automatic account withdrawal performance information, which is the past automatic account withdrawal performance information. A function of storing the registration-related information received from the user's terminal device as administrator-side user information. When the administrator-side user information matches the registration-related information received from the business operator management device, based on the administrator-side user information, the financial institution generates transmission information to the financial institution that can be received, and based on the information received from the financial institution, the business operator management device generates transmission information to the business operator that can be received. A control program for a financial-related information management device characterized by having a configuration that causes this function to be executed.

Images