Method and server for providing information related to virtual accounts

Abstract

A method, a server performing the method, and a recording medium are disclosed, comprising: a step of obtaining virtual account information including a virtual account number of a virtual account from a financial institution server; a step of determining a candidate user account corresponding to the virtual account; a step of performing user account authentication for the candidate user account based on authentication information received from a user terminal in which the candidate user account is activated; a step of obtaining designated deposit information from the user terminal including at least one of deposit bank information, deposit account number information, depositor name information, and management branch information for a deposit account to be deposited into the virtual account; a step of determining the candidate user account as a confirmed user account for the virtual account based on the result of performing the user account authentication and the designated deposit information; a step of obtaining actual deposit information from the financial institution server as a virtual account deposit is performed from the confirmed user account to the virtual account; and a step of providing a message indicating whether the virtual account deposit was performed normally based on a comparison result between the designated deposit information and the actual deposit information.

Description

Technology Field

[0001] The technical field of the present disclosure relates to a method and server for providing information related to a virtual account, and relates to a technical field that enables virtual account deposits to be performed through user account authentication. Background Technology

[0002] With the rapid increase in the use of network communication, its importance is growing day by day across all industrial sectors. In particular, various businesses utilizing wired and wireless internet are also on the rise. These businesses encompass diverse fields such as search services, advertising services, game services, portal services, e-commerce, and financial services, and the number of businesses utilizing these communication networks is increasing rapidly. Due to the recent development of information and communication technologies, various financial transaction systems using the internet are being introduced and actively developed, and are evolving day by day. Consequently, many internet financial business models are emerging, and systems utilizing virtual accounts are also on the rise. While firm banking is becoming more active as virtual account systems increase, there is a problem regarding the potential for misuse. Since information regarding the depositor or the purpose of the deposit is unclear when using virtual accounts, the same virtual account number may be used for other purposes. Therefore, measures are needed to prevent such misuse. Prior art literature

[0003] Korean Registered Patent 10-0410970 (December 1, 2003) Method and apparatus for settling betting game usage fees based on a virtual account corresponding to a real account The problem to be solved

[0004] The problem to be solved in the present disclosure is to provide an automatic transfer service through a virtual account by communicating with a user terminal, a financial institution server, and a user institution server in a system that provides information related to a virtual account.

[0005] The problems to be solved in this disclosure are not limited to those mentioned above, and other unmentioned problems will be clearly understood by a person skilled in the art from the description below. means of solving the problem

[0006] As a technical means for achieving the technical problem described above, a method for a relay server to provide information related to a virtual account according to the first aspect of the present disclosure may include: obtaining virtual account information including a virtual account number of the virtual account from a financial institution server; determining a candidate user account corresponding to the virtual account; performing user account authentication for the candidate user account based on authentication information received from a user terminal in which the candidate user account is activated; obtaining designated deposit information from the user terminal including at least one of deposit bank information, deposit account number information, depositor name information, and management branch information for a deposit account to be deposited into the virtual account; determining the candidate user account as a confirmed user account for the virtual account based on the result of performing the user account authentication and the designated deposit information; obtaining actual deposit information from the financial institution server as a virtual account deposit is performed from the confirmed user account to the virtual account; and providing a message indicating whether the virtual account deposit was performed normally based on the result of comparing the designated deposit information and the actual deposit information.

[0007] In addition, the step of determining the candidate user account as the confirmed user account for the virtual account may provide a message indicating that the candidate user account has been determined as the confirmed user account to the user institution server associated with the confirmed user account, as the candidate user account is determined as the confirmed user account.

[0008] In addition, the step of performing the above user account authentication may be performed according to an authentication method based on at least one of mobile phone identity verification, account holder real name verification, account possession verification, and non-repudiation verification.

[0009] Additionally, the step of obtaining the designated deposit information may determine the type of information included in the designated deposit information based on at least one of the user account trust level for the candidate user account, the type of information included in the actual deposit information, and the user institution trust level for the user institution server.

[0010] In addition, if the actual deposit information includes the deposit account number information, the designated deposit information may include the deposit account number information and omit the management branch information.

[0011] In addition, the step of performing the above user account authentication can determine the type of authentication method based on the number of matching instances between the designated deposit information and the actual deposit information for the above candidate user account, based on the virtual account transaction history of the above candidate user account.

[0012] In addition, the step of obtaining the designated deposit information may determine the type of information included in the designated deposit information based on weights assigned to gradually decrease in the order of the type of information included in the actual deposit information, the reliability of the user institution, and the reliability of the user account.

[0013] In addition, if the above actual deposit information includes the above deposit account number information, the above candidate determines the number of account number digits to be entered and the order of entry of the account number digits to be entered based on the user account trust level for the user account, and can receive the above input account number information according to the number of account number digits to be entered and the order of entry of the account number digits to be entered.

[0014] A relay server providing information related to a virtual account according to a second aspect of the present disclosure comprises: a receiving unit that obtains virtual account information including a virtual account number of a virtual account from a financial institution server and obtains designated deposit information including at least one of deposit bank information, deposit account number information, depositor name information, and management branch information for a deposit account to be deposited into the virtual account from a user terminal; and a processor that determines a candidate user account corresponding to the virtual account, performs user account authentication for the candidate user account based on authentication information received from the user terminal in which the candidate user account is activated, and determines the candidate user account as a confirmed user account for the virtual account based on the result of performing the user account authentication and the designated deposit information. The receiving unit obtains actual deposit information from the financial institution server as a virtual account deposit is performed from the confirmed user account to the virtual account, and the processor may provide a message indicating whether the virtual account deposit was performed normally based on the result of comparing the designated deposit information and the actual deposit information.

[0015] According to a third aspect of the present disclosure, a computer-readable non-transient recording medium may be provided on which a program for implementing the method of the first aspect is recorded. Effects of the invention

[0016] According to one embodiment of the present disclosure, security can be ensured by preventing situations in which a virtual account is abused.

[0017] In addition, security can be ensured by performing multiple user authentication procedures when mediating automatic transfer services through virtual accounts, which can improve user satisfaction.

[0018] In addition, since automatic transfer services can be performed through a relay server, it has the effect of ensuring convenience for users and participating institutions.

[0019] In addition, satisfaction can be improved in that it is possible to verify whether the virtual account deposit was successfully executed even if deposit account number information cannot be obtained from the financial institution server during a virtual account transfer.

[0020] The effects of the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art from the description below. Brief explanation of the drawing

[0021] FIG. 1 is a block diagram schematically illustrating the configuration of a relay server according to one embodiment. FIG. 2 is a flowchart illustrating each step of operation of a relay server according to one embodiment. FIG. 3 is a flowchart illustrating an example in which a relay server according to one embodiment provides a confirmed user account determination notification. FIG. 4 is a flowchart illustrating an example in which a relay server according to one embodiment determines the type of authentication method and performs user account authentication. FIG. 5 is a flowchart illustrating an example of a relay server according to one embodiment determining the type of information included in designated deposit information. FIG. 6 is a flowchart illustrating an example in which a relay server according to one embodiment determines a confirmed user account based on the type of designated deposit information determined. FIG. 7 is a flowchart illustrating an example in which a relay server according to one embodiment requests a user terminal to input deposit account number information based on whether the actual deposit information includes deposit account number information. FIG. 8 is a flowchart illustrating an example in which a relay server according to one embodiment changes the type of information included in designated deposit information depending on whether the actual deposit information includes deposit account number information. FIG. 9 is a diagram illustrating a platform schematically showing an example in which a relay server according to one embodiment supports a transfer service through a virtual account. Specific details for implementing the invention

[0022] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but can be implemented in various different forms, and the embodiments provided are merely to make the disclosure complete and to fully inform those skilled in the art of the scope of the present disclosure.

[0023] The terms used in this specification are for describing embodiments and are not intended to limit the disclosure. In this specification, the singular form includes the plural form unless specifically stated otherwise in the text. The terms “comprises” and / or “comprising” as used in this specification do not exclude the presence or addition of one or more other components in addition to the components mentioned. Throughout the specification, the same reference numerals refer to the same components, and “and / or” includes each of the mentioned components and all combinations of one or more. Although terms such as “first,” “second,” etc., are used to describe various components, these components are not limited by these terms. These terms are used merely to distinguish one component from another. Accordingly, the first component mentioned below may be the second component within the technical scope of this disclosure.

[0024] Unless otherwise defined, all terms used herein (including technical and scientific terms) may be used in a meaning commonly understood by a person skilled in the art. Additionally, terms defined in commonly used dictionaries are not to be interpreted ideally or excessively unless explicitly and specifically defined otherwise.

[0025] Spatially relative terms such as "below," "beneath," "lower," "above," and "upper" may be used to facilitate the description of the relationship between one component and other components as illustrated in the drawings. Spatially relative terms should be understood as encompassing different orientations of components during use or operation, in addition to the orientations depicted in the drawings. For example, if a component depicted in a drawing is inverted, a component described as "below" or "beneath" of another component may be placed "above" of that component. Therefore, the exemplary term "below" may encompass both the lower and upper directions. Components may also be oriented in other directions, and accordingly, spatially relative terms may be interpreted according to the orientation.

[0026] Embodiments are described in detail below with reference to the drawings.

[0027] A relay server according to an embodiment described in the embodiments may be used to provide or perform a process or platform that supports automatic transfer services through a virtual account by communicating with a plurality of user terminals and a financial institution server.

[0028] In one embodiment, the relay server may provide a signal to one or more electronic devices (not shown) or receive a signal from one or more electronic devices. To this end, the relay server may be able to communicate with one or more electronic devices or may be connected via wired or wireless connection. For example, the signal may include at least one of information, data, requests, and commands for controlling one or more electronic devices. Additionally or alternatively, the signal may include at least one of information, data, requests, and commands used by the relay server to perform any operation.

[0029] A relay server according to one embodiment may be implemented in various forms. For example, the relay server may include a web server, a network server, a cloud server, etc. As another example, the relay server may include a device such as a user terminal, a mobile device, a small computer, or a tablet. When the relay server operates as a device, it may perform operations in an on-device manner. In this case, the relay server may implement the embodiments disclosed in this specification without being restricted by the state of communication with the outside.

[0031] FIG. 1 is a block diagram schematically illustrating the configuration of a relay server (100) according to one embodiment.

[0032] Referring to the drawing, the relay server (100) may include a receiving unit (110) and a processor (120).

[0033] A receiving unit (110) according to one embodiment may obtain virtual account information including a virtual account number of a virtual account from a financial institution server. Additionally, the receiving unit (110) may obtain designated deposit information from a user terminal that includes at least one of deposit bank information, deposit account number information, depositor name information, and management branch information regarding a deposit account to be deposited into the virtual account.

[0034] A processor (120) according to one embodiment can determine a candidate user account corresponding to a virtual account. Additionally, the processor (120) can perform user account authentication for the candidate user account based on authentication information received from a user terminal in which the candidate user account is activated. Additionally, the processor (120) can determine the candidate user account as the confirmed user account for the virtual account based on the result of performing user account authentication and designated deposit information.

[0035] Additionally, the receiving unit (110) according to one embodiment can obtain actual deposit information from the financial institution server as a virtual account deposit is performed from a confirmed user account to a virtual account. Additionally, the processor (120) can provide a message indicating whether the virtual account deposit was successfully performed based on the result of comparing the designated deposit information with the actual deposit information.

[0036] It should be noted that the relay server (100) may be combined with various conventional network combinations, such as the Internet network or mobile communication network, in the process of obtaining virtual account information and designated deposit information from the receiving unit (110), performing user account authentication at the processor (120), and providing a message indicating whether the virtual account deposit was successfully performed, and there are no special restrictions on this.

[0037] In addition, it will be understood by those skilled in the art that other general-purpose components may be included in the relay server (100) in addition to the components illustrated in FIG. 1. For example, the relay server (100) may further include a memory (not shown) for storing virtual account information, designated deposit information, actual deposit information, etc. Additionally, it may further include a transmitter (not shown) for providing various messages to a user terminal, a user institution server, or a financial institution server. Alternatively, it will be understood by those skilled in the art that, according to other embodiments, some of the components illustrated in FIG. 1 may be omitted.

[0038] A relay server (100) according to one embodiment can be used by a user and can be linked with all kinds of handheld-based wireless communication devices equipped with a touch screen panel, such as mobile phones, smartphones, PDAs (Personal Digital Assistants), PMPs (Portable Multimedia Players), tablet PCs, etc. In addition, it can be included in or linked with devices that have a foundation for installing and running applications, such as desktop PCs, tablet PCs, laptop PCs, and IPTVs including set-top boxes.

[0039] The relay server (100) may be implemented as a terminal such as a computer that operates through a computer program to realize the functions described in this specification.

[0040] A relay server (100) according to one embodiment may include, but is not limited to, a system (not shown) and a related server (not shown) that support a transfer service through a virtual account. A relay server (100) according to one embodiment may support a transfer support application through a virtual account.

[0041] In the following description, the relay server (100) according to one embodiment will be described primarily in the form of an embodiment in which it independently supports a transfer service through a virtual account, but as previously mentioned, it may also be performed through integration with a device. That is, the relay server (100) and the device according to one embodiment may be implemented as an integrated unit in terms of their functions, the device may be omitted, and it can be seen that it is not limited to any one embodiment.

[0043] FIG. 2 is a flowchart illustrating each step of operation of a relay server (100) according to one embodiment.

[0045] Referring to step S210, a relay server (100) according to one embodiment may obtain virtual account information including a virtual account number of a virtual account from a financial institution server. In one embodiment, the relay server (100) may represent a server that supports firm banking. Firm banking may represent an example of a banking system used by a company, where a dedicated line connected to a bank is connected to the company's host server to perform transfers or inquiry tasks. The financial institution server may be a server corresponding to a bank that manages multiple accounts. The virtual account number may be determined from the financial institution server. The relay server (100) may obtain virtual account information including a virtual account number to be matched to multiple users determined from the financial institution server.

[0046] Referring to step S220, a relay server (100) according to one embodiment can determine a candidate user account corresponding to a virtual account. In one embodiment, the relay server (100) can obtain multiple virtual account information determined from a financial institution server for multiple user accounts. The candidate user accounts may represent multiple user accounts that wish to receive transfer services through virtual accounts using the relay server (100). The relay server (100) can correspond each virtual account number included in each of the obtained multiple virtual account information to each of the multiple candidate user accounts. That is, one virtual account number can be matched to correspond to one candidate user account.

[0047] Referring to step S230, a relay server (100) according to one embodiment may perform user account authentication for a candidate user account based on authentication information received from a user terminal in which the candidate user account is activated. In one embodiment, the user terminal in which the candidate user account is activated may correspond to a user terminal to which a virtual account number is matched. In one embodiment, user account authentication may be performed according to an authentication method based on at least one of mobile phone identity authentication, depositor real name verification, account possession authentication, and non-repudiation authentication. Mobile phone identity authentication may be authentication through a message transmitted to a mobile phone number, etc., and depositor real name verification may be authentication regarding whether the name of the candidate user account corresponding to the user terminal is the same as the depositor's name, or whether the name corresponding to the account number held by the candidate user account corresponding to the user terminal is the same as the depositor's name, etc. Additionally, account possession authentication may be authentication regarding an amount or deposit name, etc., deposited into an account number held by the candidate user account corresponding to the user terminal, such as 1 won account possession authentication. Additionally, the non-repudiation certificate may include an example of providing a message indicating proof that user account authentication has been performed. For example, the non-repudiation certificate may include an example of a digital signature for user account authentication.

[0048] Referring to step S240, a relay server (100) according to one embodiment may obtain designated deposit information including at least one of deposit bank information, deposit account number information, depositor name information, and management branch information for a deposit account to be deposited into a virtual account from a user terminal. In one embodiment, the designated deposit information may be an element that enables further user account authentication to be performed in order to transfer a certain amount from the deposit account of a user account to a virtual account. The deposit bank information may include the bank name corresponding to the deposit account corresponding to the user account, and the depositor name information may include the name corresponding to the user account or the name of the depositor corresponding to the deposit account. Additionally, the management branch information may include information regarding the location of the bank where the deposit account was opened, the branch of the bank, etc. The relay server (100) may obtain the deposit bank information, deposit account number information, depositor name information, and management branch information of the deposit account corresponding to the user account from the user terminal and store them as matching information corresponding to a candidate user account corresponding to the user terminal.

[0049] Referring to step S250, a relay server (100) according to one embodiment may determine a candidate user account as a confirmed user account for a virtual account based on the result of performing user account authentication and designated deposit information. The relay server (100) may determine a candidate user account for which matching information storage is completed as a confirmed user account for one virtual account included in the virtual account information obtained from the financial institution server in steps S210 and S220 by using matching information stored to correspond to the candidate user account through user account authentication that performs identity authentication for the candidate user account and designated deposit information obtained from the user terminal. In one embodiment, as the candidate user account is determined as a confirmed user account, the relay server (100) may provide a message indicating that the candidate user account has been determined as a confirmed user account to a user institution server associated with the confirmed user account. In this regard, this will be explained with reference to FIG. 3.

[0050] FIG. 3 is a flowchart illustrating an example in which a relay server (100) according to one embodiment provides a confirmed user account determination notification.

[0051] Referring to FIG. 3, a relay server (100) according to one embodiment may perform user account authentication (S230) by communicating with a user terminal and obtain designated deposit information from the user terminal (S240). When the relay server (100) completes the storage of matching information through user account authentication and the acquisition of designated deposit information, it may determine the candidate user account as the confirmed user account (S250). As the candidate user account is determined as the confirmed user account, the relay server (100) may provide a message (S301) to the user institution server indicating that the candidate user account has been determined as the confirmed user account. In one embodiment, the user institution server may represent a server that receives a certain amount of money deposited into a virtual account from multiple user terminals through the relay server (100). That is, the relay server (100) may support the transfer of a certain amount of money from the deposit account of the user account corresponding to the user terminal to the user institution server through the virtual account. Accordingly, the user institution server can be linked with the confirmed user account through the relay server (100), and the relay server (100) can provide a message to the user institution server indicating that the candidate user account has been determined as the confirmed user account.

[0052] Referring to step S260, a relay server (100) according to one embodiment may obtain actual deposit information from a financial institution server as a virtual account deposit is performed from a confirmed user account to a virtual account. In one embodiment, when a confirmed user account performs an account deposit to a virtual account provided by the relay server (100), the relay server (100) may obtain actual deposit information from the confirmed user account from the financial institution server. The actual deposit information may include at least one of the information included in the designated deposit information described through step S240. That is, the relay server (100) may obtain at least one of the deposit bank information, deposit account number information, depositor name information, and management branch information regarding the deposit account actually deposited into the virtual account assigned in step S220 from the financial institution server as actual deposit information.

[0053] Referring to step S270, a relay server (100) according to one embodiment may provide a message indicating whether a virtual account deposit has been successfully performed based on a comparison result between designated deposit information and actual deposit information. For example, the relay server (100) may provide a message indicating that a virtual account deposit has been successfully performed to a user terminal or a user institution server if the designated deposit information obtained from a user terminal and stored as matching information is identical to the actual deposit information obtained from a financial institution server.

[0054] Various embodiments supporting a transfer service through the virtual account described above will be explained with reference to FIGS. 4 to 9.

[0055] FIG. 4 is a flowchart illustrating an example in which a relay server (100) according to one embodiment determines the type of authentication method and performs user account authentication.

[0056] Referring to step S221 of FIG. 4, a relay server (100) according to one embodiment may determine the type of authentication method based on the number of matchings between designated deposit information and actual deposit information for a candidate user account, based on the virtual account transaction history of the candidate user account. Additionally, referring to step S222, the relay server (100) may perform an authentication method based on at least one of mobile phone number authentication, depositor real name verification, account ownership authentication, and non-repudiation authentication, depending on the type of authentication method determined. For example, the relay server (100) may obtain the virtual account transaction history of the candidate user account. The virtual account transaction history may include the number of times the relay server (100) has matched designated deposit information and actual deposit information for the candidate user account. Based on the virtual account transaction history, the relay server (100) may simplify the authentication method corresponding to user account authentication as the number of matchings increases. For example, the relay server (100) may determine the user account reliability of a candidate user account to be high when the number of matchings between designated deposit information and actual deposit information based on the virtual account transaction history exceeds the first time, thereby allowing user account authentication to be performed solely by mobile phone number authentication. Additionally, the relay server (100) may allow user account authentication to be performed for a candidate user account in the order of mobile phone number authentication → depositor real name verification → account ownership authentication when the number of matchings between designated deposit information and actual deposit information exceeds the second time and is less than the first time. In one embodiment, the first time may correspond to a number greater than the second time and may be determined as a value pre-set by an administrator.Additionally, the relay server (100) can perform user account authentication in the order of mobile phone number verification -> depositor real name verification -> account ownership verification -> non-repudiation verification when the number of matches between designated deposit information and actual deposit information corresponds to 0, that is, when there is no virtual account transaction history. Thus, depending on the user account trustworthiness, user account authentication can be simplified or performed in detail to ensure both convenience and safety.

[0057] FIG. 5 is a flowchart illustrating an example in which a relay server (100) according to one embodiment determines the type of information included in designated deposit information.

[0058] Referring to FIG. 5, a relay server (100) according to one embodiment may determine the information included in the designated deposit information differently. For example, the relay server (100) may determine the user account reliability for a candidate user account (S501). Additionally, the relay server (100) may determine the user institution reliability for a user institution server (S502). The relay server (100) may obtain the type of information included in the actual deposit information obtained from the financial institution server (S503). Accordingly, the relay server (100) may determine the type of information included in the designated deposit information differently based on at least one of the user account reliability, the user institution reliability, and the type of information included in the actual deposit information. For example, the relay server (100) may assign different weights to the type of information included in the actual deposit information, the user institution reliability, and the user account reliability, respectively (S504). For example, the relay server (100) can determine the type of information included in the designated deposit information (S505) based on weights that are gradually lowered in the order of the type of information included in the actual deposit information, the reliability of the institution using the deposit, and the reliability of the user account.

[0059] For example, in one embodiment, the type of information included in the actual deposit information may be the most important information when providing a transfer service through a virtual account. The actual deposit information may be the deposit information actually deposited into the virtual account provided by the financial institution server when a deposit into a virtual account is performed from a user terminal to a financial institution server. That is, the actual deposit information may include at least one type of information among deposit bank information, deposit account number information, depositor name information, and management branch information. The type of information included in the actual deposit information may be the most important information in that it is information that can be objectively compared with the type of information included in the designated deposit information obtained from the user terminal. Therefore, the highest weight may be assigned to the type of information included in the actual deposit information. In addition, the user institution server may be a server where a certain amount is automatically deposited when a transfer is performed from the user terminal through the virtual account. The reliability of the user institution may be determined as a percentage based on the publicity and activity of the user institution. For example, if the user organization is a highly trusted entity, such as a large corporation or a public institution, the risk associated with the process of depositing a certain amount into the user organization's server via a virtual account transfer may be reduced. If the user organization is a public institution, its trustworthiness may be determined to be 1 percent (e.g., 100 percent), and if the user organization is a large corporation, its trustworthiness may be determined to be 2 percent (e.g., 80 percent). Furthermore, if the user organization is a less trusted entity, such as a startup, the risk associated with the process of depositing a certain amount into the user organization's server via a virtual account transfer may be increased. If the user organization is a startup, its trustworthiness may be determined to be 3 percent (e.g., 50 percent). In other words, the user organization's trustworthiness can be an important factor in that it influences the risk associated with the process of depositing a certain amount into the user organization's server.Therefore, a high weight of second rank may be assigned to the trustworthiness of the user institution. Additionally, the trustworthiness of the user account for the candidate user account may also be an important factor alongside the trustworthiness of the user institution. While user account trustworthiness may be important because a certain amount is deposited into the virtual account from the user terminal corresponding to the candidate user account, the trustworthiness of the recipient may be more important, given that the user institution server is the recipient of the deposit while the user account is the depositor. Therefore, a high weight of third rank, lower than the trustworthiness of the user institution, may be assigned to user account trustworthiness. User account trustworthiness can be determined based on the virtual account transaction history of the candidate user account. For example, as described in FIG. 4, if the number of matching times between designated deposit information and actual deposit information based on the virtual account transaction history exceeds the first time, the user account reliability can be determined to be the first percent; if the number of matching times between designated deposit information and actual deposit information exceeds the second time and is less than the first time, the user account reliability can be determined to be the second percent; and if the number of matching times between designated deposit information and actual deposit information corresponds to zero times, the user account reliability can be determined to be the third percent. The relay server (100) can determine the type of information included in the designated deposit information based on the type of information included in the actual deposit information to which weights are assigned in the order described above, the user account reliability, and the user institution reliability.

[0060] For example, if the type of information included in the actual deposit information includes only deposit account number information, the relay server (100) can determine the type of information included in the designated deposit information as deposit account number information regardless of user account reliability and user institution reliability. Accordingly, a comparison can be performed on the deposit account number information included in each of the actual deposit information and the designated deposit information. Additionally, if the type of information included in the actual deposit information includes at least one type of information among deposit bank information, depositor name information, and management branch information along with deposit account number information, the type of information to be included in the designated deposit information can be determined according to the user institution reliability and user account reliability. For example, since it can be determined that the user institution reliability is more important than the user account reliability, if the user institution reliability corresponds to a third percent or more and less than a second percent (for example, if it is not a startup but a small and medium-sized enterprise), the deposit account number information and management branch information can be determined as the type of information included in the designated deposit information. Given that deposit bank information and depositor name information may have a high probability of overlap with depositor names or deposit bank information corresponding to other virtual accounts to some extent, it may be desirable to check the management branch information first. Additionally, if the user institution trust level corresponds to the 3rd percent, one of the deposit bank information and depositor name information, along with the deposit account number information and management branch information, can be randomly determined based on the user account trust level to determine the type of information included in the designated deposit information. For example, if the user account trust level corresponds to the 1st percent, the type of information can be determined based on one of the deposit bank information and depositor name information selected from the user account. If the user account trust level does not correspond to the 1st percent, the type of information to be included in the designated deposit information can be automatically and randomly determined.In addition, if the reliability of the user institution and the reliability of the user account both correspond to the third percent, the deposit account number information, deposit bank information, depositor name information, and management branch information can all be determined as types of information included in the designated deposit information.

[0061] In another embodiment, if the deposit account number information is not included in the types of information included in the actual deposit information, the relay server (100) can determine the types of information included in the designated deposit information based on weights that are assigned to gradually decrease in the order of management branch information, depositor name information, and deposit bank information. Therefore, when performing a comparison between the actual deposit information and the designated deposit information, the comparison can be performed in the order of management branch information, depositor name information, and deposit bank information. For example, the management branch information may be a factor that ensures safety in that it may include information about the location of the bank where the deposit account was opened and the branch of the bank. Therefore, the management branch information may be compared first to determine whether they are identical, as it may have the lowest probability of duplication with other virtual accounts. If the management branch information is not identical, the relay server (100) can immediately determine that the virtual account deposit was not performed normally. Additionally, if the management branch information is identical, the relay server (100) can compare the depositor name information. Since the number of banks is limited, the probability of the depositor name being duplicated may be lower than the probability of the deposit bank information being duplicated. Therefore, if the management branch information is identical, the depositor name information is compared to determine if they are identical; and if both the management branch information and the depositor name information are identical, the deposit bank information is compared to determine if they are identical. Consequently, if the comparison results of the management branch information, depositor name information, and deposit bank information are all identical, it can be determined that the virtual account deposit was successfully executed. Thus, since the determination of whether the virtual account deposit was successfully executed is made according to the method described above, the accuracy of the comparison result between the actual deposit information and the designated deposit information can be improved, and security can be ensured.

[0062] FIG. 6 is a flowchart illustrating an example in which a relay server (100) according to one embodiment determines a confirmed user account based on the type of designated deposit information determined.

[0063] A relay server (100) according to one embodiment may request information input (S241) corresponding to the type of information included in the designated deposit information determined in step S505 of FIG. 5. For example, the relay server (100) may request information corresponding to the type of information included in the designated deposit information determined from the user terminal, and the relay server (100) may determine the candidate user account as the confirmed user account for the virtual account (S250) by obtaining the designated deposit information input requested from the user terminal (S242). Steps S501 to S505 in FIG. 5 may be steps included in step S240, and steps S241 and S242 may be steps included between step S240 and step S250.

[0064] FIG. 7 is a flowchart illustrating an example in which a relay server (100) according to one embodiment requests a user terminal to input deposit account number information based on whether the actual deposit information includes deposit account number information.

[0065] Referring to FIG. 7, a relay server (100) according to one embodiment may obtain actual deposit information from a financial institution server (S260), and the relay server (100) may determine whether to include deposit account number information in the actual deposit information (S701). If the actual deposit information includes deposit account number information, the relay server (100) may determine the number of account number digits to be entered and the order of the account number digits to be entered (S702). For example, the relay server (100) may determine the number of account number digits to be entered and the order of the account number digits to be entered among the deposit account numbers based on the user account trust level for the candidate user account. The relay server (100) may request the input of deposit account number information to the user terminal according to the determined number of account number digits and the determined order of the account number digits (S703). Accordingly, the relay server (100) can receive input account number information according to the number of account number digits to be entered and the order of input of the account number digits to be entered.

[0066] In one embodiment, the relay server (100) may determine the number of digits of the account number to be entered as a first number or a second number when the user account reliability corresponds to a first percent or a second percent, and may determine the order of input of the account number digits to be entered as a continuous order from the front digit of the account number or a continuous order from the back digit of the account number. For example, when the user account reliability corresponds to a first percent, the relay server (100) may receive input account number information from the user terminal as an account number with a first number of consecutive digits starting from the front digit of the account number. Additionally, when the user account reliability corresponds to a second percent or higher but less than a first percent, the relay server (100) may determine the number of digits of the account number to be entered as a second number greater than the first number, and may receive input account number information from the user terminal as an account number with a second number of consecutive digits starting from the back digit of the account number. Additionally, when the user account reliability corresponds to a third percent or higher and less than a second percent, the relay server (100) may determine the number of digits of the account number to be entered as half the number of digits of the deposit account number and determine the order of input of the digits of the account number to be entered as an odd-numbered input or an even-numbered input. For example, the relay server (100) may receive input account number information from the user terminal as an account number located in consecutive odd-numbered digits or an account number located in consecutive even-numbered digits. Additionally, when the user account reliability corresponds to a third percent, the relay server (100) may determine the number of digits of the account number to be entered as the total number of digits and receive input account number information as the entire account number. Therefore, when the user account reliability is high, the input account number information can be entered briefly, thereby improving convenience. One embodiment is one example among various embodiments and is not limited thereto.

[0067] FIG. 8 is a flowchart illustrating an example in which a relay server (100) according to one embodiment changes the type of information included in designated deposit information depending on whether the actual deposit information includes deposit account number information.

[0068] Referring to FIG. 8, a relay server (100) according to one embodiment determines whether to include deposit account number information in the actual deposit information (S701), and if the actual deposit information includes deposit account number information, determines the number of account number digits to be entered and the order of entry of the account number digits to be entered (S702). Additionally, if the actual deposit information includes deposit account number information, the relay server (100) may include deposit account number information in the designated deposit information and omit management branch information (S711). For example, the importance of deposit account number information may be the highest in determining whether the designated deposit information and the actual deposit information are identical. The case where the deposit account number included in the actual deposit information and the deposit account number included in the designated deposit information are the same may be the case with the highest level of security. Therefore, if the deposit account number included in the actual deposit information and the deposit account number included in the designated deposit information are the same, it is not necessary to determine whether other information is identical. That is, if the relay server (100) can compare the deposit account number information with the actual deposit information by including the deposit account number information, the management branch information included in the designated deposit information can be omitted, thereby omitting the comparison process for the management branch information. In FIG. 7, steps S701 to S703 are shown as steps performed after step S260, but are not limited thereto. For example, referring to FIG. 8, the relay server (100) may perform step S240 after performing steps S701 to S703. That is, as the process illustrated in FIG. 7 and FIG. 8 is performed repeatedly, if there is a history in which the deposit account number information is included among at least one piece of information included in the actual deposit information provided by the same financial institution server, the type of information to be included in the designated deposit information to be obtained from the user terminal may be determined in step S240 of the next process.That is, steps S701 through S703 may influence the determination of the type of information to be included in the designated deposit information of step S240 in the next process that is performed repeatedly. Accordingly, steps S701 through S703 may be performed after step S260 within the same process, or may be performed to influence step S240 within the next process.

[0070] FIG. 9 is a diagram illustrating a platform schematically showing an example in which a relay server (100) according to one embodiment supports a transfer service through a virtual account.

[0071] Referring to FIG. 9, the relay server (100) can communicate with a user terminal, a service provider server, and a financial institution server. The relay server (100) can obtain virtual account information (S210) for the user terminal connected to the financial institution server and the service provider server. FIG. 9 illustrates a flow in which the relay server (100) performs steps S210 to S240 with the user terminal via the service provider server, but is not limited thereto. Specifically, the service provider server is shown merely as an example of a server connected between the user terminal and the relay server (100), but in reality, steps S210 to S240 may be performed through direct mobile communication between the relay server (100) and the user terminal. That is, each step in which the relay server (100) determines a candidate user account corresponding to a virtual account based on virtual account information obtained from a financial institution server (S220), performs user account authentication for the user account (S230), and obtains designated deposit information from a user terminal (S240) may be performed via the service provider server, but may also be performed through direct mobile communication with the user terminal by omitting the service provider server. Additionally, the relay server (100) can determine a confirmed user account (S250) for the user account corresponding to the user terminal by determining a candidate user account (S220) and performing user account authentication (S230) through mobile communication with the user terminal. Furthermore, as a deposit (S260) is performed into the virtual account from the user terminal determined as the confirmed user account, the relay server (100) can obtain actual deposit information (S260) from the financial institution server. Accordingly, the relay server (100) can provide a message (S270) to the user terminal or the institution server indicating whether the virtual account deposit was successfully performed by comparing the designated deposit information with the actual deposit information.For example, if the designated deposit information and the actual deposit information are the same, the relay server (100) can provide a message indicating that the virtual account deposit was successfully executed to the user terminal or the institution server (S270), and if the designated deposit information and the actual deposit information are different from each other, it can provide a message indicating that the virtual account deposit was not successfully executed to the user terminal or the institution server (S270).

[0072] According to one embodiment, security can be ensured by preventing the misuse of virtual accounts because it is impossible for others to deposit into the virtual account. Additionally, user satisfaction can be enhanced by ensuring security through the performance of multiple user authentication procedures when relaying automatic transfer services via virtual accounts. Furthermore, convenience for users and participating institutions can be guaranteed as the automatic transfer service can be performed through a relay server. Satisfaction can also be improved by the ability to verify whether the virtual account deposit was successfully executed even if deposit account number information cannot be obtained from the financial institution server during the virtual account transfer.

[0074] Various embodiments of the present disclosure may be implemented as software comprising one or more instructions stored in a storage medium (e.g., memory) readable by a machine (e.g., a display device or a computer). For example, a processor (120) of the machine (e.g., processor (120)) may call at least one of the one or more instructions stored from the storage medium and execute it. This enables the machine to be operated to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' merely means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

[0075] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0076] Although the present invention has been described with reference to the illustrated drawings, it is not limited by the disclosed embodiments and drawings, and those skilled in the art will understand that it may be implemented in modified forms without departing from the essential characteristics of the above description. Therefore, the disclosed methods should be considered in an illustrative rather than a restrictive sense. Even if the effects of the configuration according to the present invention are not explicitly described in the description of the embodiments, effects predictable by said configuration may also be recognized. The scope of the present invention is defined by the claims, not by the foregoing description, and all variations within the equivalent scope thereof should be interpreted as being included in the present invention. Explanation of the symbols

[0077] 100: Relay server 110: Receiver 120: Processor

Claims

Claim 1 A method for a relay server to provide information related to a virtual account, comprising: obtaining virtual account information including a virtual account number of a virtual account from a financial institution server; determining a candidate user account corresponding to the virtual account; performing user account authentication for the candidate user account based on authentication information received from a user terminal in which the candidate user account is activated; obtaining designated deposit information from the user terminal including at least one of deposit bank information, deposit account number information, depositor name information, and management branch information for a deposit account to be deposited into the virtual account; determining the candidate user account as a confirmed user account for the virtual account based on the result of performing the user account authentication and the designated deposit information; obtaining actual deposit information from the financial institution server as a virtual account deposit is performed from the confirmed user account to the virtual account; and providing a message indicating whether the virtual account deposit was performed normally based on a comparison result between the designated deposit information and the actual deposit information. Claim 2 In claim 1, the step of determining the candidate user account as the confirmed user account for the virtual account comprises providing a message to a user institution server associated with the confirmed user account indicating that the candidate user account has been determined as the confirmed user account, as the candidate user account is determined as the confirmed user account. Claim 3 In claim 2, the step of performing the user account authentication is performed according to an authentication method based on at least one of mobile phone identity verification, depositor real name verification, account possession authentication, and non-repudiation authentication. Claim 4 In claim 2, the step of obtaining the designated deposit information is a method of determining the type of information included in the designated deposit information based on at least one of the user account trust level for the candidate user account, the type of information included in the actual deposit information, and the user institution trust level for the user institution server. Claim 5 A method according to claim 2 in which, if the actual deposit information includes the deposit account number information, the designated deposit information includes the deposit account number information and the management branch information is omitted. Claim 6 In claim 3, the step of performing the user account authentication determines the type of authentication method based on the number of matching instances between the designated deposit information and the actual deposit information for the candidate user account, based on the virtual account transaction history of the candidate user account. Claim 7 In claim 4, the step of obtaining the designated deposit information is a method of determining the type of information included in the designated deposit information based on weights assigned to gradually decrease in the order of the type of information included in the actual deposit information, the reliability of the user institution, and the reliability of the user account. Claim 8 A method according to claim 5, wherein, when the actual deposit information includes the deposit account number information, the candidate determines the number of account number digits to be entered and the order of entry of the account number digits to be entered based on the user account trust level for the user account, and receives the input account number information according to the number of account number digits to be entered and the order of entry of the account number digits to be entered. Claim 9 A relay server providing information related to a virtual account comprises: a receiving unit that obtains virtual account information including a virtual account number of a virtual account from a financial institution server, and obtains designated deposit information including at least one of deposit bank information, deposit account number information, depositor name information, and management branch information for a deposit account to be deposited into the virtual account from a user terminal; and a processor that determines a candidate user account corresponding to the virtual account, performs user account authentication for the candidate user account based on authentication information received from the user terminal in which the candidate user account is activated, and determines the candidate user account as a confirmed user account for the virtual account based on the result of performing the user account authentication and the designated deposit information; wherein the receiving unit obtains actual deposit information from the financial institution server as a virtual account deposit is performed from the confirmed user account to the virtual account, and the processor provides a message indicating whether the virtual account deposit was performed normally based on the result of comparing the designated deposit information and the actual deposit information. Claim 10 A computer-readable recording medium having a program stored on it for executing the method of any one of claims 1 to 8 on a computer.

Images