Account transaction management system

Abstract

To provide an account transaction management system capable of securing safety of account transfer.SOLUTION: An account transaction management system 1 which is configured to set a user account of a user of a financial institution as a debit account for account transfer includes: a virtual account DB 12 which stores a virtual account of the user in association with the user account; a setting request receiving unit which receives a setting request to set the virtual account as a debit account, from a business operator which receives an account transfer request using the virtual account from the user; a validity receiving unit which receives validity information indicating whether the setting request is valid or not, from the user; a debit account setting unit which sets the virtual account as a debit account when the setting request is determined to be valid based on the validity information; and a debit execution unit which debits, after setting the debit account, the amount to be paid from the user to the business operator from the user account associated with the virtual account.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an account transaction management system that enables automatic withdrawals from a financial institution's account. [Background technology]

[0002] Account transfers, in which payments are automatically debited from a specific account at a financial institution, have become commonplace, and various technologies for ensuring the safety of account transfers have been proposed. For example, Patent Document 1 discloses an account transfer acceptance system that includes a database that stores customer information, including account information, and personal identification information in association with each customer, and that, when a request for account transfer is made, collates the customer information and personal identification information, and sets the customer's account as the withdrawal account only if the collation is successful. With this account transfer acceptance system, the account transfer will not be registered unless the person requesting the account transfer knows the customer information and personal identification information, thereby preventing fraudulent transactions from occurring. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-159849 Summary of the Invention [Problem to be solved by the invention]

[0004] When a user wishes to make an account transfer, they typically fill out an account transfer request form with necessary information such as account information and submit it to a business operator. In the case of the above-mentioned conventional account transfer acceptance system, it is assumed that the user will fill out the account transfer request form with not only account information but also personal identification information and submit it to a business operator. In this case, there is a risk that the account information and personal identification information will be leaked, which could result in fraudulent transactions.

[0005] The present invention has been made in view of the above circumstances, and its main object is to provide an account transaction management system and an account transaction management method that can ensure the safety of account transfers. [Means for solving the problem]

[0006] In order to solve the above problems, one aspect of the present invention provides an account transaction management system that is capable of setting a user account of a user at a financial institution as a debit account for an account transfer, and includes: a memory unit that stores a virtual account of the user in association with the user account; a setting request receiving unit that receives a setting request from a business operator that has received a request from the user for an account transfer using the virtual account to set the virtual account as the debit account; a validity receiving unit that receives validity information from the user indicating whether the setting request is valid or not; a debit account setting unit that sets the virtual account as the debit account if it is determined that the setting request is valid based on the validity information; and a debit execution unit that, after setting the debit account, debits the amount to be paid by the user to the business operator from the user account that is associated with the virtual account.

[0007] In the above aspect, the device may further include a prompting unit that prompts the user to provide the correct / incorrect information when the setting request is received from the business operator.

[0008] In the above aspect, the correct / incorrect acceptance unit may accept the correct / incorrect information from the user before the setting request acceptance unit accepts the setting request from the business operator.

[0009] In addition, in the above aspect, the system may further include an account holder setting unit that sets an account holder designated by the user as the account holder of the virtual account.

[0010] In addition, in the above aspect, the system may further include an account holder setting unit that automatically sets the account holder of the virtual account.

[0011] In addition, in the above aspect, the system may further include a branch setting unit that sets a branch designated by the user as a branch of the virtual account.

[0012] In addition, in the above aspect, the system may further include a branch office setting unit that automatically sets a branch office for the virtual account.

[0013] In addition, the above aspect may further include an account number setting unit that sets a numeric string with the same number of digits as the account number of the user account as the account number of the virtual account. [Effects of the Invention]

[0014] According to the present invention, it is possible to ensure the safety of account transfers. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram showing the configuration of an account transaction management system and its communication destination. [Figure 2] FIG. 10 is a diagram showing an example of the layout of a virtual account database. [Figure 3] FIG. 10 is a diagram showing an example of a virtual account application form. [Figure 4] 10 is a flowchart showing an example of a procedure for a virtual account start process. [Figure 5] FIG. 10 is a diagram showing an example of a start-of-use request screen. [Figure 6] FIG. 10 is a diagram showing an example of a reception completion screen. [Figure 7] FIG. 10 is a diagram showing an example of an account transfer request form. [Figure 8] 10 is a flowchart showing an example of a procedure for determining whether or not the result is correct; [Figure 9] FIG. 10 is a diagram showing an example of a correct / incorrect information reception screen. [Figure 10] 10 is a flowchart showing an example of a procedure for a withdrawal execution process. DETAILED DESCRIPTION OF THE INVENTION

[0016] When a user of a financial institution wishes to make an account transfer using their own account (hereinafter referred to as "user account") as the debit account, they must provide the payee business with information to identify the user account. In this case, while it is common to provide the account number of the user account, in this embodiment, the account number of a virtual account linked to the user account is provided. This makes it possible to prevent information about the user account, such as the account number of the user account, from being leaked.

[0017] Preferred embodiments of the present invention will be described below with reference to the drawings. Note that the following embodiments are merely examples of methods and devices for embodying the technical concept of the present invention, and the technical concept of the present invention is not limited to the following. Various modifications can be made to the technical concept of the present invention within the technical scope described in the claims.

[0018] (System configuration) Figure 1 is a block diagram showing the configuration of an account transaction management system and its communication partners according to this embodiment. The account transaction management system (hereinafter simply referred to as the "management system") 1 according to this embodiment is a financial institution system operated by a financial institution such as a bank, and is a computer system that manages various transactions in each account. The management system 1 communicates with a user terminal 2 and a business operator terminal 3 via the Internet 101.

[0019] The user terminal 2 is an information terminal used by each user who has an account at a financial institution, and examples of such terminals include a personal computer, a smartphone, a tablet terminal, a smart watch, etc. The user terminal 2 uses an internet browser or a dedicated application to acquire information provided by the management system 1 and display it on a display unit.

[0020] The business operator terminal 3 is an information terminal used by each business operator requesting the setting of account transfer. As in the case of the user terminal 2, the business operator terminal 3 is composed of a personal computer, a smartphone, or the like, and transmits and receives data to and from the management system 1 using an internet browser or a dedicated application, or the like.

[0021] The following describes the detailed configuration of the management system 1. The management system 1 is composed of one or more computers equipped with a control unit including a CPU, RAM, and ROM, and a storage unit, and this control unit executes each of the processes described below. The storage unit of the management system 1 is provided with the following databases: a user account database (DB) 11, a virtual account database (DB) 12, and an account transfer request database (DB) 13. The following describes the details of these databases.

[0022] (A) User Account DB11 The user account DB11 is a database that stores information about the user accounts of each user of the financial institution. For example, information such as the account holder's name, branch number, account title (savings, current, etc.), and account number is stored in the user account DB11. In addition, information for personal authentication is linked to the user account DB11. For example, the impression of a personal seal (registered seal), a driver's license, and a My Number (personal identification number) are linked to each user account.

[0023] (B) Virtual Account DB12 The virtual account DB12 is a database that stores information about virtual accounts set up for each user. Here, a virtual account is a virtual account used for automatic deductions via account transfer, and is associated with a real user account. As will be described later, when a request for deduction is made to a virtual account, the deduction is made from the user account associated with that virtual account.

[0024] In addition to the same information as in the user account DB 11, the virtual account DB 12 stores identifiers of user accounts associated with the virtual accounts. Figure 2 is a diagram showing an example of the layout of the virtual account DB 12. As shown in Figure 2, the virtual account DB 12 stores information such as the account number, account subject, account holder, branch number, and storage location (path) of information for personal authentication of the virtual account, in association with the account number, which is the identifier of the user account.

[0025] As will be described later, a virtual account is set up in response to a request from a user. When the account is set up, various pieces of information are stored in the virtual account DB 12. In this embodiment, a seal impression is used as information for personal authentication. However, other information, such as a driver's license or My Number, may also be used as information for personal authentication.

[0026] As described above, virtual accounts are associated with user accounts, and when a request for debiting a virtual account is made, the debit is made from the user account associated with that virtual account. Therefore, the virtual account does not need to have an account number or account title, as long as it is associated with a user account. However, in this embodiment, the account number and account title are set for the virtual account, just as for a regular user account. This has the advantage that when an account transfer request is made, the business operator can respond without feeling uncomfortable. This point will be described in detail later.

[0027] (C) Direct debit request DB13 The account transfer request DB13 is a database that stores information related to account transfer requests from business operators. For example, in addition to the identifier of the business operator, various information related to the account used for automatic account transfer withdrawal (such as the account number and account holder) is stored in the account transfer request DB13. The management system 1 obtains information from the user indicating whether the account transfer request from the business operator is legitimate, and then verifies the legitimacy of the request based on that information, and stores information indicating the result in the account transfer request DB13. Details of this will be described later.

[0028] (System Operation) A user who wishes to use a virtual account first informs the financial institution where the user already has an account that he or she wishes to open a virtual account. In this case, the user fills out the necessary information on a virtual account application form, such as the one shown in Figure 3, and submits it to the financial institution.

[0029] As shown in Figure 3, the branch number, account title, account number, and name are entered in the virtual account application form. These are the branch number, account title, account number, and name of the user's account. In other words, the user enters the branch number, account title, account number, and name of the user's account held at the financial institution to which the form is submitted in the virtual account application form. Meanwhile, the seal for the virtual account (registered seal for the virtual account) is affixed in the seal section of the virtual account application form. However, if the user agrees, this seal may be the same as the seal for the user's account.

[0030] In the example shown in Figure 3, numbers are used as information to identify the branch and account title of an account, but this is not limited to this. For example, the branch name may be used as information to identify the branch, or both the branch number and branch name may be used. Furthermore, characters such as "regular" and "current" may be used as information to identify the account title. These points also apply to other parts of this specification that refer to branches and account titles.

[0031] The virtual account application form may be provided by the user to the financial institution by mail or other means, or may be provided electronically by the user entering the necessary information on a website or by writing the necessary information in an email.

[0032] When a financial institution receives a virtual account application form from a user, the management system 1 confirms that the user account described in the application form actually exists by referring to the user account DB 11. The management system 1 then stores the seal impression for the virtual account and registers information including the storage location and the account number of the user account in the virtual account DB 12. This completes preparations for using the virtual account.

[0033] (Virtual account activation process) After preparations for use of the virtual account have been made as described above, the user accesses the management system 1 using the user terminal 2 and executes the virtual account start-up process shown in Figure 4. Details of the virtual account start-up process will be explained below with reference to the flowchart in Figure 4.

[0034] As described above, a start-of-use request screen for inputting the information necessary to start using the virtual account is displayed on the display unit of the user terminal 2 that has accessed the management system 1. Here, it is assumed that the user terminal 2 is a tablet terminal, and each screen is displayed on the display unit (display) of the tablet terminal.

[0035] Fig. 5 is a diagram showing an example of the above-mentioned start-of-use request screen. As shown in Fig. 5, the start-of-use request screen displayed on the display unit 21 of the user terminal 2 has input fields for inputting the branch number, account title, account number, and account holder of the virtual account. After inputting each piece of information in each input field, the user presses the send button 211. As a result, each piece of information is transmitted to the management system 1.

[0036] The user inputs only the branch number, account title, account number, and account holder of the virtual account that the user wishes to set. For example, if the user wishes to set everything except the account number, the user inputs only the branch number, account title, and account holder, as shown in Figure 5, and leaves the account number blank. In this case, as will be described later, the account number will be automatically set by the management system 1. Alternatively, for example, if the user leaves all input fields blank, the branch number, account title, account number, and account holder will all be automatically set by the management system 1.

[0037] In addition, if the user sets at least one of the branch number, account title, account number, and account holder name, they can be any number they like. For example, the branch number and account number can be a number that the user can easily remember, and the account holder name can be the name of another person or a fictitious person.

[0038] As described above, input of the start-of-use request by the user is completed by pressing the send button 211 on the start-of-use request screen. As shown in Fig. 4, when the user terminal 2 receives the input of this start-of-use request (S101), it transmits it to the management system 1 (S102).

[0039] When the management system 1 receives a usage start request from the user terminal 2 (S201), it sets the account holder of the virtual account (S202). Here, if the usage start request includes a name, the management system 1 sets that name as the account holder of the virtual account. On the other hand, if the usage start request does not include a name, the management system 1 automatically sets the account holder of the virtual account. For example, the management system 1 may set the account holder using part of the user's name, such as making only the last name or first name of the user's given name the same, or may set a random name as the account holder. Furthermore, if the usage start request includes only part of the name (such as the last name or first name), the management system 1 may use that part to complete the name and set it as the account holder.

[0040] Next, the management system 1 sets the account number of the virtual account (S203). Here, if the request to start use includes an account number, the management system 1 sets that account number as the account number of the virtual account. On the other hand, if the request to start use does not include an account number, the management system 1 automatically sets the account number of the virtual account. For example, the management system 1 generates a random numeric string with the same number of digits as the account number of the user account (e.g., seven digits) and sets it as the account number of the virtual account. Also, if the request to start use includes part of the account number (a numeric string with less than a predetermined number of digits), the management system 1 may randomly generate a numeric string of the remaining digits to generate a numeric string of a predetermined number of digits and set it as the account number.

[0041] Next, the management system 1 sets a branch number for the virtual account (S204). If a branch number is included in the request to start use, the management system 1 sets that branch number as the branch number for the virtual account. On the other hand, if a branch number is not included in the request to start use, the management system 1 automatically sets a branch number for the virtual account. For example, the management system 1 randomly selects one branch number from the branch numbers of existing branches and sets it as the branch number for the virtual account.

[0042] Next, the management system 1 sets the account subject of the virtual account (S205). Here, if the request to start use includes an account subject, the management system 1 sets that account subject as the account subject of the virtual account. On the other hand, if the request to start use does not include an account subject, the management system 1 automatically sets the account subject of the virtual account. For example, the management system 1 extracts an arbitrary account subject from among multiple account subjects and sets it as the account subject of the virtual account.

[0043] After the account holder, account number, branch number, and account title of the virtual account have been set as described above, the management system 1 registers this information in the virtual account DB 12 (S206). This makes the virtual account available for use. The management system 1 then transmits acceptance completion information to the user terminal 2 indicating that acceptance of the user's request to start use has been completed (S207).

[0044] When the user terminal 2 receives the acceptance completion information from the management system 1 (S103), it uses the information included in the acceptance completion information to display an acceptance completion screen on the display unit 21 (S104). FIG. 6 is a diagram showing an example of the acceptance completion screen. As shown in FIG. 6, the acceptance completion screen displays the branch number, account title, account number, and account holder information set for the virtual account. By referring to this acceptance completion screen, the user can understand the various pieces of information related to the virtual account.

[0045] After executing the virtual account activation process described above, the user submits an account transfer request to the payee business to realize an account transfer using the virtual account. Figure 7 shows an example of such an account transfer request. As shown in Figure 7, information about the account for automatic withdrawal is entered on the account transfer request. Specifically, the name of the financial institution, branch number, account title, account number, and account holder of the account are entered, and then a registered seal is affixed.

[0046] The user fills in the fields of the account transfer request form with the name of the financial institution for the user's account, as well as the branch number, account title, account number, and account holder of the virtual account set up in association with that user's account, and then stamps it with the seal used on the virtual account application form. In this case, all information entered on the account transfer request form other than the name of the financial institution belongs to the virtual account, not the user's account. In this way, information about the user's account does not need to be disclosed on the account transfer request form, preventing the leakage of information about the user's account.

[0047] When transferring funds using a special account such as a virtual account, it is expected that a dedicated account transfer request form different from a conventional account transfer request form will be prepared, or even if a conventional account transfer request form is used, special information will need to be entered. However, in this embodiment, the branch number, account title, account number, and account holder are set for the virtual account, just like a user account, and each of these pieces of information is entered on the account transfer request form. Therefore, it is possible to use a conventional account transfer request form, and there is no need to enter special information. Therefore, the business operator who receives the account transfer request form can proceed with the procedure without feeling any discomfort.

[0048] The business operator submits the account transfer request form received from the user to the financial institution. This submission can be made in a variety of ways, for example, by mail or electronically. The financial institution that receives this submission inputs the details of the account transfer request form into the management system 1. This means that the management system 1 has received a setting request from the business operator to set the virtual account as a withdrawal account. Note that this setting request may also be sent electronically from the business operator terminal 3 to the management system 1, which then receives it.

[0049] (correct / incorrect determination process) When the management system 1 receives the setting request, it determines whether the setting request is valid. At this time, a validity determination process is executed. Figure 8 is a flowchart showing an example of the procedure of the validity determination process.

[0050] 8, the management system 1 first provides a request for correct / incorrect information to the user terminal 2 to prompt the user to provide correct / incorrect information indicating whether the setting request is correct or not (S301). This request may be provided by e-mail or the like, or may be provided to the user terminal 2 that has accessed the management system 1 via an internet browser or the like.

[0051] When the user terminal 2 receives a request for correct / incorrect information from the management system 1 (S401), it displays a correct / incorrect information reception screen on the display unit 21 for receiving correct / incorrect information (S402). FIG. 9 is a diagram showing an example of the correct / incorrect information reception screen. As shown in FIG. 9, the correct / incorrect information reception screen displays the name of the business that has requested the account transfer setup and information about the user's virtual account. After checking this information, the user determines whether it matches the contents of the account transfer request form that the user submitted to the business. If the user determines that it matches, the user presses the "Yes" button 212, and if the user determines that it does not match, the user presses the "No" button 213. This completes the input of the correct / incorrect information.

[0052] 8, when the user terminal 2 receives input of correct / incorrect information from the user as described above (S403), it transmits the correct / incorrect information to the management system 1 (S404). When the management system 1 receives the correct / incorrect information (S302), it determines whether the setting request from the business operator is correct or not based on the correct / incorrect information (S303).

[0053] If the management system 1 determines that the setting request from the business operator is not valid (NO in S303), it terminates the process. On the other hand, if the management system 1 determines that the setting request is valid (YES in S303), it compares the seal stamped on the account transfer request form with the seal managed in the virtual account DB12 (S304). If this comparison fails, the process terminates. Here, we will continue the explanation assuming that the comparison is successful.

[0054] After successfully verifying the seal, the management system 1 registers information indicating that the request to set up the virtual account has been confirmed to be valid (hereinafter referred to as "confirmed information") in the account transfer request DB 13 (S305). This confirmed information is used during the debit execution process, which will be described later.

[0055] (Withdrawal execution process) In the case of automatic transfer, payment from the user to the business is completed by automatically withdrawing the specified payment amount from the withdrawal account at the specified date and time. The process for executing this withdrawal is the following withdrawal execution process.

[0056] Figure 10 is a flowchart showing an example of the procedure for a debit execution process executed by the management system 1. As shown in Figure 10, the management system 1 first determines whether the debit account in this process is a virtual account (S501). If it is determined that the debit account is not a virtual account (NO in S501), that is, if it is determined that the debit account is a regular user account, the management system 1 executes a process to debit the specified payment amount from that user account (S502).

[0057] On the other hand, if it is determined in step S501 that the withdrawal account is a virtual account (YES in S501), the management system 1 refers to the account transfer request DB12 and determines whether or not the user has approved the withdrawal of the amount to be paid to the business from that virtual account, that is, whether or not confirmation information has been obtained for that virtual account (S503). If it is determined that confirmation information has not been obtained (NO in S503), the management system 1 transmits to the business terminal 3 withdrawal failure information indicating that the current withdrawal cannot be executed (S504). In this case, the business that has obtained the withdrawal failure information will inform the user that the withdrawal could not be made and will take measures such as collecting the payment amount separately.

[0058] Furthermore, if it is determined in step S503 that confirmed information has been obtained (YES in S503), the management system 1 refers to the virtual account DB12 to identify the user account associated with the virtual account set as the withdrawal account, and executes processing to withdraw the payment amount from that user account (S505).

[0059] After the above step S502 or S505 is executed, the management system 1 transmits debit completion information indicating that the current debit has been completed to the business operator terminal 3 (S506). This allows the business operator to understand that the payment amount has been collected from the user. Note that when step S502 is executed, information about the user's account, such as the account number of the user's account, is included in the debit completion information, whereas when step S505 is executed, information about the virtual account, not the user's account, is included in the debit completion information.

[0060] As described above, in this embodiment, when a setting request to set a virtual account as a withdrawal account is received from a business operator, and the setting request is confirmed to be legitimate by the user, the withdrawal is executed from the user account associated with the virtual account. This makes it possible to avoid situations where withdrawals are made against the user's intention, and ensures the safety of account transfers.

[0061] (Other embodiments) In the above embodiment, the management system 1 receives a setup request from a business operator to set a virtual account as a debit account, and then receives the provision of correct / incorrect information from the user. However, this is not limited to this. For example, the management system 1 may receive the setup request from a business operator after receiving the provision of correct / incorrect information from the user. In this case, the management system 1 is assumed to receive correct / incorrect information from the user indicating that a setup request from a specific business operator will be made soon (a notice of the setup request) and that the setup request is legitimate, and then receive the setup request from the business operator. In this case, since the setup request has already been confirmed to be legitimate, the management system 1 sets the virtual account as a debit account in the same manner as in the above embodiment, and after the setup, executes a debit from the user account associated with the virtual account. In this way, the reception of correct / incorrect information from the user may occur before or after the reception of the setup request from the business operator.

[0062] In the above embodiment, when a user desires to transfer funds using a virtual account, the user submits a transfer request to the service provider. However, this is not limited to this. In recent years, a service (cash card-based transfer acceptance service) has been implemented in which a user reads a cash card into a dedicated terminal installed on the service provider's side and then inputs a personal identification number (PIN) to request a transfer from a financial institution. The present invention can also be applied to this service. In this case, the dedicated terminal transmits the information and personal identification number read from the cash card to the management system 1. The management system 1, upon receiving this information, references the virtual account DB 12 to determine whether a virtual account is linked to the user's account. If a virtual account is linked, the management system 1 transmits a message to the dedicated terminal asking whether the virtual account should be set as a withdrawal account (for example, "A virtual account has been registered to your user account. Would you like to transfer funds using the virtual account?"). The dedicated terminal then displays the message and accepts a response from the user regarding whether or not the setting is necessary. This response corresponds to the validity information in the above embodiment, i.e., information indicating whether the setting request received from the business operator (in this example, received from a terminal installed on the business operator's side) to set the virtual account as a debit account is valid. Here, if the user responds that they wish to set the virtual account as a debit account, the management system 1 sets the virtual account as a debit account, as in the above embodiment.

[0063] The dedicated terminal may be the business operator terminal 3, or may be a terminal separate from the business operator terminal 3. The management system 1 may also send the message to the user terminal 2 rather than to the dedicated terminal. In this case, the user terminal 2 displays the message (for example, "You are about to sign up for account transfer from the business operator's terminal. A virtual account has been registered to your user account. Would you like to transfer your account using the virtual account?") using a dedicated application or the like, and receives a response from the user as to whether or not the setting is necessary. From this point on, the management system 1 processes in the same manner as above, and the virtual account is set as the debit account. [Explanation of symbols]

[0064] 1 Account transaction management system 2. User terminal 21 Display section 3. Operator terminal 11 User Account Database 12 Virtual Account Database 13 Direct Debit Request Database 101 Internet

Claims

1. In an account transaction management system that can set a user account of a financial institution user as a withdrawal account for direct debit, a storage unit that stores the virtual account of the user in association with the user account; a setting request receiving unit that receives, from a business operator that has received an account transfer request using the virtual account from the user, a setting request to set the virtual account as the withdrawal account; a validity receiving unit that receives validity information indicating whether the setting request is valid from the user; a debit account setting unit that sets the virtual account as the debit account when it is determined that the setting request is valid based on the validity information; a debit execution unit that debits the amount to be paid by the user to the business operator from the user account associated with the virtual account after the debit account is set; An account transaction management system comprising:

2. a prompting unit that prompts the user to provide the correct / incorrect information when the setting request is received from the business operator; The account transaction management system of claim 1 further comprising:

3. the correct / incorrect acceptance unit accepts the correct / incorrect information from the user before the setting request acceptance unit accepts the setting request from the business operator. The account transaction management system according to claim 1 .

4. an account holder setting unit that sets the account holder designated by the user as the account holder of the virtual account; Further provided with 4. An account transaction management system according to claim 1.

5. an account holder setting unit that automatically sets the account holder of the virtual account; Further provided with 4. An account transaction management system according to claim 1.

6. a branch setting unit that sets the branch designated by the user as the branch of the virtual account; Further provided with 4. An account transaction management system according to claim 1.

7. a branch setting unit that automatically sets a branch for the virtual account; Further provided with 4. An account transaction management system according to claim 1.

8. an account number setting unit that sets a numeric string having the same number of digits as the account number of the user account as the account number of the virtual account; Further provided with 4. An account transaction management system according to claim 1.

Images