Device and method for relaying customer confirmation and authentication

Abstract

A device for relaying customer confirmation and authentication according to an embodiment of the present invention comprises: an authentication request reception unit for receiving customer confirmation and authentication request data relative to a customer from a first institution terminal; an authentication challenge transmission unit for transmitting customer confirmation and authentication challenge data to a second institution terminal on the basis of the customer confirmation and authentication request data; a customer confirmation relay unit for relaying a customer confirmation process relative to the customer and performed between the first institution terminal and the second institution terminal on the basis of the customer confirmation and authentication challenge data; a confirmation result reception unit for receiving customer confirmation result data relative to the customer from the second institution terminal on the basis of the result of the customer confirmation process; and a confirmation result transmission unit for transmitting the customer confirmation result data to the first institution terminal.

Description

Customer verification authentication relay device and method thereof

[0001] The embodiment relates to a customer verification authentication relay device and method thereof.

[0002] Know Your Customer (KYC) is the process by which financial institutions verify and identify customers' identities. It refers to the customer authentication process for financial institutions. KYC assesses potential illicit intent and risks in business relationships and is used to ensure compliance with banking regulations and anti-money laundering (AML) regulations. Initially, KYC-related processes were mandated only for financial institutions, but now they are applied to non-financial industries, fintech companies, virtual asset exchanges, and even non-profit organizations.

[0003] The general KYC process is as follows. First, the user, or customer, must prepare documents proving their identity (e.g., an ID card, passport, etc.), a program or device used for identity verification (e.g., a public certificate, mobile phone, etc.), and other necessary documents. The user sends these documents and information to the financial institution, which verifies the identity and verifies the adequacy of the information. During the verification process, the financial institution collaborates with administrative agencies capable of verifying and / or confirming the identity. Based on the verification results, the financial institution notifies the user of the pass / fail status (pass / fail).

[0004] However, the KYC process places a significant burden on the institutions and users who perform it.

[0005] First, as anti-money laundering obligations strengthen, the amount of information required to verify a user's identity in the KYC process is increasing. The institutions providing verification information for various pieces of information are not singled out, but rather distributed differently depending on the information. Therefore, the institution conducting the KYC process must contact each verification source to verify and determine the authenticity of each piece of information. This requires significant manpower, time, and money.

[0006] Furthermore, the KYC process is not a one-time process and must be repeated after a certain period of time. Therefore, the institution conducting the KYC process must contact the institution providing verification information for each piece of information to complete the process. Users must also prepare the necessary documents for the KYC process. Furthermore, users must complete this process for each institution they use, which means the more institutions they use, the more time and effort it takes.

[0007] Therefore, there is a need for a method to solve the above problems related to the KYC process.

[0008] The embodiment provides a customer verification authentication relay device and method capable of providing a procedure related to customer identity authentication.

[0009] The problem to be solved in the embodiment is not limited to this, and it can be said that the purpose or effect that can be understood from the solution or embodiment of the problem described below is also included.

[0010] A customer verification authentication relay device according to an embodiment of the present invention includes: an authentication request receiving unit for receiving customer verification authentication request data regarding a customer from a first institution terminal; an authentication request transmitting unit for transmitting customer verification authentication request data to a second institution terminal based on the customer verification authentication request data; a customer verification relay unit for relaying a customer verification process performed between the first institution terminal and the second institution terminal regarding the customer based on the customer verification authentication request data; a verification result receiving unit for receiving customer verification result data regarding the customer from the second institution terminal based on a result of the customer verification process; and a verification result transmitting unit for transmitting the customer verification result data to the first institution terminal.

[0011] The above authentication request receiving unit can receive the customer verification authentication request data including the institution selection information corresponding to the second institution terminal and the first customer information entered corresponding to the institution selection information.

[0012] The above authentication application transmission unit may set the second institution terminal to receive the customer verification authentication application data based on the institution selection information; and may transmit the customer verification authentication application data including the first customer information to the second institution terminal.

[0013] The customer verification relay unit may receive reception information data corresponding to the customer verification authentication application data from the second agency terminal; transmit authentication information request data regarding the customer to the first agency terminal based on the reception information data; receive authentication data corresponding to the authentication information request data from the first agency terminal; and transmit the authentication data to the second agency terminal.

[0014] The above customer verification relay unit can receive the reception information data generated based on whether the first customer information matches the second customer information stored in connection with the second institution terminal.

[0015] The above verification result receiving unit can receive the customer verification result data generated based on whether the authentication information generated by the second agency terminal matches the authentication data.

[0016] The above authentication information can be generated by the second institution terminal when the first customer information and the second customer information match.

[0017] The above customer verification result data may be characterized in that it does not include financial information stored in relation to the first institution terminal.

[0018] It may include a confirmation result update unit that transmits the customer confirmation result data updated based on the preset schedule information to the second agency terminal.

[0019] The above verification result update unit may determine whether the expiration date of the customer verification result data falls within a predetermined period range based on the preset schedule information; if it is determined that the expiration date falls within the predetermined period range, transmit update request data for the customer verification result data regarding the customer to the second agency terminal; receive updated customer verification result data from the second agency terminal; and transmit the updated customer verification result data to the first agency terminal.

[0020] A customer verification authentication relay method according to an embodiment of the present invention includes the steps of: receiving customer verification authentication request data regarding a customer from a first institution terminal; transmitting customer verification authentication application data to a second institution terminal based on the customer verification authentication request data; relaying a customer verification process performed between the first institution terminal and the second institution terminal regarding the customer based on the customer verification authentication application data; receiving customer verification result data regarding the customer from the second institution terminal based on a result of the customer verification process; and transmitting the customer verification result data to the first institution terminal.

[0021] The step of receiving the customer verification authentication request data may include receiving the customer verification authentication request data including institution selection information corresponding to the second institution terminal and first customer information entered corresponding to the institution selection information.

[0022] The step of transmitting the customer verification authentication application data may include a step of setting the second institution terminal to receive the customer verification authentication application data based on the institution selection information; and a step of transmitting the customer verification authentication application data including the first customer information to the second institution terminal.

[0023] The step of relaying the customer verification process may include: a step of receiving reception information data corresponding to the customer verification authentication application data from the second institution terminal; a step of transmitting authentication information request data regarding the customer to the first institution terminal based on the reception information data; a step of receiving authentication data corresponding to the authentication information request data from the first institution terminal; and a step of transmitting the authentication data to the second institution terminal.

[0024] The step of inputting the above reception information data may input the above reception information data generated based on whether the first customer information matches the second customer information stored in connection with the second institution terminal.

[0025] The step of receiving the customer verification result data may receive the customer verification result data generated based on whether the authentication information generated by the second institution terminal matches the authentication data.

[0026] The above authentication information can be generated by the second institution terminal when the first customer information and the second customer information match.

[0027] The above customer verification result data may be characterized in that it does not include financial information stored in relation to the first institution terminal.

[0028] It may include a step of transmitting the updated customer verification result data based on the preset schedule information to the second agency terminal.

[0029] The step of transmitting the updated customer verification result data to the second agency terminal may include: a step of determining whether an expiration date of the customer verification result data falls within a predetermined period range based on the preset schedule information; a step of transmitting, if the expiration date is determined to be within the predetermined period range, update request data for the customer verification result data regarding the customer to the second agency terminal; a step of receiving updated customer verification result data from the second agency terminal; and a step of transmitting the updated customer verification result data to the first agency terminal.

[0030] According to the embodiment, the process of customer authentication can be simplified and provided to customers and institutions, so that customers and institutions can enjoy significant savings in time, effort, and cost.

[0031] Institutions that require identity verification may not store documents related to customer identity verification, which not only saves time, effort, and costs associated with storing related documents, but also provides customers with the advantage of securing their personal information.

[0032] The various advantageous and beneficial effects of the present invention are not limited to the above-described contents, and will be more easily understood in the course of explaining specific embodiments of the present invention.

[0033] FIG. 1 is a drawing for explaining a customer verification authentication relay system according to an embodiment of the present invention.

[0034] FIG. 2a and FIG. 2b are examples showing a customer verification authentication relay method using a customer verification authentication relay system according to an embodiment of the present invention.

[0035] Figure 3 is a configuration diagram of a customer verification authentication relay device according to an embodiment of the present invention.

[0036] Figure 4 is a flowchart of a customer verification authentication relay method according to an embodiment of the present invention.

[0037] Figure 5 is an example showing step S420 of Figure 4 in detail.

[0038] Figure 6 is an example showing step S430 of Figure 4 in detail.

[0039] FIG. 7 is a flowchart illustrating another example of a customer verification authentication relay method according to an embodiment of the present invention.

[0040] The present invention is susceptible to various modifications and embodiments. Specific embodiments are illustrated and described in the drawings. However, this is not intended to limit the present invention to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the present invention.

[0041] Terms including ordinal numbers, such as "second," "first," etc., may be used to describe various components, but the components are not limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present invention, a second component may be referred to as a "first component," and similarly, a first component may also be referred to as a "second component." The term "and / or" includes a combination of multiple related items described herein or any of multiple related items described herein.

[0042] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0043] The terminology used in this application is only used to describe specific embodiments and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, it should be understood that the terms "comprise" or "have" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0044] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and will not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

[0045] Hereinafter, embodiments will be described in detail with reference to the attached drawings. Regardless of the drawing numbers, identical or corresponding components are given the same reference numbers, and redundant descriptions thereof will be omitted.

[0046] FIG. 1 is a drawing for explaining a customer verification authentication relay system according to an embodiment of the present invention.

[0047] The customer verification and authentication relay system according to an embodiment of the present invention is a technology related to a platform service for relaying processes related to KYC authentication. The customer verification and authentication relay system can be used when a customer authenticates their identity to the institution they wish to use.

[0048] Typically, customers must complete identity verification procedures related to the KYC (Know Your Customer) process to use services such as account opening at their desired institution. However, identity verification requires a variety of information, and customers must prepare all of it. Even if customers already possess the necessary information, they must prepare new information if it expires. Furthermore, the institution conducting the identity verification process must individually verify each piece of information. The institution the customer wishes to use must contact the institution holding the information needed for verification and individually verify the information, which can be time-consuming, laborious, and costly. Furthermore, the institution must store and manage all of the verified information, which can be a significant time, effort, and expense.

[0049] However, the customer verification and authentication relay system according to an embodiment of the present invention provides a function that can resolve the inconveniences of the KYC process by relaying the procedures related to the KYC process. The customer verification and authentication relay system according to an embodiment of the present invention provides a relay service that allows the customer to perform the KYC-related identity verification procedure of the institution they wish to use, using the information of the institution that performed the identity verification process for the customer. This can provide the advantage of saving both the customer and the institution using time, effort, and cost.

[0050] Furthermore, the customer verification authentication relay system according to an embodiment of the present invention only transmits the results of identity verification to the user institution through the relay process, eliminating the need to store or manage the extensive information used in the KYC process. This allows the user institution to reduce the time, effort, and cost involved in storing and preserving information.

[0051] Additionally, the customer verification authentication relay system according to an embodiment of the present invention automatically updates the KYC process, which requires periodic updates, at predetermined intervals and provides it to the user institution. This allows users and the user institution to reduce the time, effort, and cost required for identity verification updates.

[0052] Below, a customer verification authentication relay system capable of providing the above features will be examined with reference to Fig. 1.

[0053] Referring to FIG. 1, a customer verification authentication system according to an embodiment of the present invention may include a customer verification authentication relay device (100), a customer terminal (200), a first agency terminal (300), and a second agency terminal (400).

[0054] First, the customer verification authentication relay device (100) refers to a device that provides a relay service that simplifies the customer authentication process that must be performed by the user institution.

[0055] According to one embodiment, a customer authentication relay device (100) can relay a user authentication-related procedure between a first institution and a second institution. The customer authentication relay device (100) can receive a request from the first institution related to the user authentication of the customer. In addition, the customer authentication relay device (100) can apply for user authentication of the customer to the second institution on behalf of the request of the first institution. Thereafter, the customer authentication relay device (100) can receive the result of processing the application related to the user authentication application of the customer from the second institution and transmit it to the first institution. In addition, the customer authentication relay device (100) can receive response information corresponding to the result of the application processing from the first institution and transmit it to the second institution. Then, the customer authentication relay device (100) can receive the result of user authentication processed based on the response information from the second institution and transmit it to the first institution. In this process, the customer verification authentication relay device (100) does not transmit or receive various verification document data required for the customer's identity verification, and ultimately only transmits the identity verification result to the first institution. Accordingly, the first institution can reduce the time required to collect and / or verify various verification documents required for the customer's identity verification, and the customer can also reduce the time required to prepare and / or provide various verification documents required for identity verification.

[0056] According to one embodiment, the customer authentication relay device (100) can relay a procedure related to the renewal of identity authentication that must be performed periodically. The customer authentication relay device (100) can provide a service that relays a procedure related to the renewal of identity authentication for customers who have previously relayed a procedure related to identity authentication. Before the validity period of the customer's identity authentication previously performed expires, the customer authentication relay device (100) can request information related to the renewal of the customer's identity authentication from the second institution that applied for identity authentication. In this case, the request for information related to the renewal can be performed if a predetermined condition is satisfied without a request process by the first institution. In addition, the customer authentication relay device (100) can transmit the received information related to the renewal of the customer's identity authentication to the first institution. Accordingly, the first institution and the customer can reduce the time, effort, and cost required for preparing, providing, collecting, and / or verifying various verification documents required for the renewal of identity authentication.

[0057] According to one embodiment, the customer verification authentication relay device (100) may be implemented as a computing device that stores an algorithm implemented to provide a relay service related to customer identity authentication between a first institution and a second institution and provides a relay service between the first institution and the second institution using the stored algorithm. For example, the customer verification authentication relay device (100) may be implemented as a server device such as a cloud. However, the present invention is not limited thereto. The customer verification authentication relay device (100) may be implemented as various types of computing devices including a processing unit for processing data and a memory for storing data. For example, the customer verification authentication relay device (100) may include a desktop computer, etc.

[0058] Next, the customer terminal (200) refers to a terminal device used by a customer to use a service for a given institution.

[0059] According to one embodiment, the customer terminal (200) may perform a user authentication procedure for using a service provided to the first institution. For example, the customer terminal (200) may receive user authentication information from the customer and transmit it to the first institution terminal (300). Furthermore, the customer terminal (200) may receive a request for input of information related to customer authentication from the first institution terminal (300) and provide it to the customer. Furthermore, the customer terminal (200) may receive predetermined information required for customer authentication and transmit it to the first institution terminal (300).

[0060] According to one embodiment, the customer terminal (200) may include an application for communicating with the first institution terminal (300) to receive services provided by the first institution and services related to identity authentication. Here, the application may be provided by the first institution. Accordingly, the customer terminal (200) may be implemented as a computing device capable of storing and executing applications. For example, the customer terminal (200) may be implemented as a portable input / output terminal device such as a smart phone or a tablet computer. However, the present invention is not limited thereto. The customer terminal (200) may be implemented as various types of computing devices including a processing unit for processing data and a memory for storing data. For example, the customer terminal (200) may include a desktop computer, etc.

[0061] Next, the first institution terminal (300) refers to a terminal device used by the institution that the customer wishes to use.

[0062] In one embodiment, the first institution terminal (300) may be a terminal device used by a first institution that provides services requiring customer authentication. For example, the first institution may be a financial institution, such as a bank or securities firm, that requires customer authentication when providing services. Alternatively, the first institution may be an open market that requires seller authentication when providing services. Furthermore, the first institution may include various organizations that utilize identity authentication.

[0063] According to one embodiment, the first institution terminal (300) may request information related to customer authentication from the customer verification authentication relay device (100) at the customer's request. In addition, the first institution terminal (300) may receive authentication data required for customer authentication from the customer terminal (200) and transmit the same to the customer verification authentication relay device (100). Thereafter, the first institution terminal (300) may receive a verification result related to customer authentication based on the authentication data from the customer verification authentication relay device (100). Thereafter, the first institution terminal (300) may determine whether the customer has been authenticated based on the verification result, and may provide a service to the customer based on the determination result. For example, if the first institution terminal (300) is a bank, the first institution terminal (300) may perform customer authentication using the customer verification authentication relay device (100) and provide a service for opening an account based on the customer authentication result.

[0064] According to one embodiment, the first institution terminal (300) may be implemented as a computing device capable of storing an algorithm implemented to provide services and procedures related to identity authentication to customers and providing a relay service between the first institution and the second institution using the stored algorithm. For example, the first institution terminal (300) may be implemented as a server device such as a cloud. However, the present invention is not limited thereto. The first institution terminal (300) may be implemented as various types of computing devices including a processing unit for processing data and a memory for storing data. For example, the first institution terminal (300) may include a desktop computer, etc.

[0065] Next, the second agency terminal (400) refers to a terminal device used by an agency that the customer is already using.

[0066] According to one embodiment, the second institution terminal (400) may be a terminal device used by the second institution that has completed identity verification for a customer who has requested identity verification from the first institution. That is, the second institution has already completed the identity verification related procedure for the customer, and the second institution terminal (400) may store important documents related to the identity verification of the customer. For example, the second institution terminal (400) may store documents related to identity verification, such as the WLF (Watch List Filtering) execution date, WLF processing result, CDD (Customer Due Diligence) execution date, re-performance scheduled date, RA (Risk Assessments) execution date, RA grade, RA grade name, EDD (Enhanced Due Diligence) target status, EDD execution date, source and origin of funds, and transaction purpose.

[0067] In one embodiment, since the second institution terminal (400) has the completed customer authentication result, the second institution may be an institution that performs customer authentication or provides services using the authentication result. For example, the second institution may be a financial institution such as a bank or securities firm. However, this is not limited thereto. As another example, the second institution may also include an open market or an administrative agency.

[0068] According to one embodiment, the second institution terminal (400) may be implemented as a computing device capable of storing data related to the customer's identity authentication and storing and / or executing an algorithm that can provide a relay service between the first institution and the second institution. For example, the second institution terminal (400) may be implemented as a server device such as a cloud, but the present invention is not limited thereto. The second institution terminal (400) may be implemented as various types of computing devices including a processing unit for processing data and a memory for storing data. For example, the second institution terminal (400) may include a desktop computer, etc.

[0069] FIG. 2a and FIG. 2b are examples showing a customer verification authentication relay method using a customer verification authentication relay system according to an embodiment of the present invention.

[0070] The customer authentication relay method using the customer authentication system illustrated in FIGS. 2A and 2B is an example. Therefore, in addition to the customer authentication relay method illustrated in FIGS. 2A and 2B, various customer authentication relay methods using the customer authentication system illustrated in FIG. 1 described above can be implemented by those skilled in the art.

[0071] In the customer verification authentication relay method described in Figures 2a and 2b, each entity is assumed as follows. The customer is a terminal used by a user who wishes to conduct a financial transaction at a bank. The customer may be someone who wishes to open an account at the bank. The first institution terminal (300) is a terminal used by the bank with which the user wishes to conduct a financial transaction. In other words, the first institution may be the bank with which the user wishes to conduct a financial transaction. The second institution terminal (400) is a terminal used by the bank with which the user previously conducted a financial transaction. In other words, the second institution may be the bank with which the user previously conducted a financial transaction.

[0072] Referring to Figures 2a and 2b, the customer terminal (200) may first receive a financial transaction request from the customer (S201). According to one embodiment, the customer terminal (200) may be installed with an application provided by the first institution, and the customer may run the application to enter a financial transaction request. For example, the customer may select a membership registration button provided by the application installed on the customer terminal (200) and then select a button requesting customer verification. Thereafter, the customer may enter the financial transaction request on the customer terminal (200) by entering the information required for customer verification.

[0073] Then, the customer terminal (200) can transmit data related to the financial transaction application to the first institution terminal (300) (S202). The data related to the financial transaction application can be transmitted to the first institution terminal (300) via a communications network.

[0074] Next, the first institution terminal (300) can receive data related to a financial transaction application received from the customer terminal (200) (S203).

[0075] Then, the first institution terminal (300) can transmit data related to the received financial transaction application to the customer verification authentication relay device (100) (S204). According to one embodiment, the data transmitted to the customer verification authentication relay device (100) may not be identical to the data received from the customer terminal (200). The data transmitted to the customer verification authentication relay device (100) may also be modified through a predetermined processing operation by the first institution terminal (300).

[0076] Next, the customer verification authentication relay device (100) can receive data related to a financial transaction application from the first institution terminal (300) (S205).

[0077] Then, the customer verification authentication relay device (100) can transmit data related to the received financial transaction application to the second institution terminal (400) (S206). According to one embodiment, the data transmitted to the second institution terminal (400) may not be identical to the data received from the first institution terminal (300). The data transmitted to the second institution terminal (400) may be modified through a predetermined processing operation by the customer verification authentication relay device (100). According to one embodiment, the customer verification authentication relay device (100) can select the second institution terminal (400) to which to transmit the data based on the data related to the financial transaction application received from the first institution terminal (300). The data related to the financial transaction application received from the first institution terminal (300) includes information on the second institution designated by the customer, and the customer verification authentication relay device (100) can select the second institution terminal (400) based on the information.

[0078] Next, the second agency terminal (400) can receive financial transaction application data from the customer verification authentication relay device (100) (S207).

[0079] In addition, the second institution terminal (400) may process the customer's identity verification request and / or generate an authentication number based on the received financial transaction application data (S208). According to one embodiment, the received financial transaction application data may include the customer's account number under his / her name. The second institution terminal (400) may verify whether the account number included in the received financial transaction application data is an account number of the second institution. If the account number is not an account number of the second institution, the second institution terminal (400) may reject the authentication request. On the other hand, if the account number is an account number of the second institution, the second institution terminal (400) may approve the authentication request. Then, the second institution terminal (400) may generate an authentication number. The generated authentication number may be transmitted to the customer via a mobile phone or bank account registered with the second institution.

[0080] Then, the second agency terminal (400) can transmit the processing result regarding the authentication application to the customer verification authentication relay device (100) (S209).

[0081] Next, the customer verification authentication relay device (100) can receive the processing result regarding the authentication application from the second agency terminal (400) (S210).

[0082] In addition, the customer verification authentication relay device (100) can transmit the processing result regarding the received authentication application to the first institution terminal (300) (S211). According to one embodiment, the data related to the processing result transmitted to the first institution terminal (300) may not be identical to the data received from the second institution terminal (400). The data transmitted to the first institution terminal (300) may also be modified through a predetermined processing operation by the customer verification authentication relay device (100).

[0083] Next, the first agency terminal (300) can receive the processing result regarding the authentication application from the customer verification authentication relay device (100) (S212).

[0084] In addition, the first agency terminal (300) may transmit the processing result regarding the received authentication application to the customer terminal (200) (S213). According to one embodiment, the data related to the processing result transmitted to the customer terminal (200) may not be identical to the data received from the customer verification authentication relay device (100). The data transmitted to the customer terminal (200) may also be modified through a predetermined processing operation by the first agency terminal (300). For example, if the processing result is that the authentication application is not permitted, the processing result transmitted to the customer terminal (200) may include a message indicating that the authentication application is not permitted. On the other hand, if the processing result is that the authentication application is permitted, the processing result transmitted to the customer terminal (200) may include a message requesting the user to enter an authentication number related to user authentication.

[0085] Next, the customer terminal (200) can receive the processing result regarding the authentication application from the first institution terminal (300) (S214).

[0086] Furthermore, the customer terminal (200) can provide the customer with the received processing result (S215). In one embodiment, if the processing result is disapproved, the customer terminal (200) can display information indicating that the authentication request was disapproved on the display device. Conversely, if the processing result is approved, the customer terminal (200) can display a screen prompting the customer to enter an authentication number on the display device.

[0087] Additionally, the customer terminal (200) can receive information corresponding to the received processing result (S216). According to one embodiment, if the processing result is disapproved, the customer terminal (200) can receive re-application information for the customer's identity verification request. Conversely, if the processing result is approved, the customer terminal (200) can receive an authentication number.

[0088] Then, the customer terminal (200) can transmit the entered authentication number to the first institution terminal (300) (S217).

[0089] Next, the first agency terminal (300) can receive data related to the authentication number from the customer terminal (200) (S218).

[0090] Then, the first agency terminal (300) can transmit data related to the received authentication number to the customer verification authentication relay device (100) (S219). According to one embodiment, the data related to the authentication number transmitted to the customer verification authentication relay device (100) may not be identical to the data received from the customer terminal (200). The data transmitted to the customer verification authentication relay device (100) may also be modified through a predetermined processing operation by the first agency terminal (300).

[0091] Next, the customer verification authentication relay device (100) can receive data related to the authentication number from the first institution terminal (300) (S220).

[0092] Then, the customer verification authentication relay device (100) can transmit data related to the received authentication number to the second agency terminal (400) (S221). According to one embodiment, the data related to the authentication number transmitted to the second agency terminal (400) may not be identical to the data received from the first agency terminal (300). The data transmitted to the second agency terminal (400) may also be modified through a predetermined processing operation by the customer verification authentication relay device (100).

[0093] Next, the second agency terminal (400) can receive data related to the authentication number from the customer verification authentication relay device (100) (S222).

[0094] Then, the second agency terminal (400) can compare data related to the previously generated authentication number and the received authentication number (S223).

[0095] Furthermore, the second agency terminal (400) may generate a processing result regarding the authentication number comparison based on the comparison result (S224). According to one embodiment, if the authentication numbers do not match, the second agency terminal (400) may generate a processing result indicating that the customer's identity authentication is not permitted. Conversely, if the authentication numbers match, the second agency terminal (400) may generate a processing result indicating that the customer's identity authentication is permitted.

[0096] Then, the second agency terminal (400) can transmit the processing result regarding the authentication number comparison to the customer verification authentication relay device (100) (S225).

[0097] Next, the customer verification authentication relay device (100) can receive the processing result regarding authentication number comparison from the second agency terminal (400) (S226).

[0098] In addition, the customer verification authentication relay device (100) can transmit the processing result regarding the comparison of the received authentication number to the first agency terminal (300) (S227). According to one embodiment, the data related to the processing result transmitted to the first agency terminal (300) may not be identical to the data received from the second agency terminal (400). The data transmitted to the first agency terminal (300) may also be modified through a predetermined processing operation by the customer verification authentication relay device (100).

[0099] Next, the first agency terminal (300) can receive the processing result regarding authentication number comparison from the customer verification authentication relay device (100) (S228).

[0100] In addition, the first agency terminal (300) may transmit the processing result regarding the comparison of the received authentication number to the customer terminal (200) (S229). According to one embodiment, the data related to the processing result transmitted to the customer terminal (200) may not be identical to the data received from the customer verification authentication relay device (100). The data transmitted to the customer terminal (200) may also be modified through a predetermined processing operation by the first agency terminal (300).

[0101] Next, the customer terminal (200) can receive the processing result regarding the authentication number comparison from the first agency terminal (300) and then output it (S230).

[0102] Figure 3 is a configuration diagram of a customer verification authentication relay device according to an embodiment of the present invention.

[0103] Referring to FIG. 3, a customer verification authentication relay device (100) according to an embodiment of the present invention may include an authentication request receiving unit (110), an authentication application transmitting unit (120), a customer verification relay device (130), a verification result receiving unit (140), and a verification result transmitting unit (150). In addition, the customer verification authentication relay device (100) according to an embodiment of the present invention may further include a verification result updating unit (160).

[0104] First, the authentication request receiving unit (110) performs a function of receiving information related to a customer authentication request received from the first agency terminal (300).

[0105] In one embodiment, the authentication request receiving unit (110) may receive customer verification authentication request data regarding a customer from the first institution terminal (300). For example, a "customer" may refer to a person who wishes to conduct a transaction requiring identity verification at the first institution. In other words, the customer may request identity verification using their terminal device, and the identity verification request may be input to the authentication request receiving unit (110) via the first institution terminal (300).

[0106] According to one embodiment, the authentication request receiving unit (110) may receive customer verification authentication request data including institution selection information corresponding to the second institution terminal (400) and first customer information entered in response to the institution selection information. That is, the customer verification authentication request data may include institution selection information and first customer information entered by the customer. Here, the institution selection information may include the name of the institution selected by the customer. For example, the institution selection information may include an institution name such as “Bank A” or “Securities Company B.” In addition, the first customer information may include information related to a customer of the selected institution. For example, the first customer information may include an account number of “Bank A.” As another example, the first customer information may include a phone number of a customer registered with “Securities Company B.”

[0107] Next, the authentication application transmission unit (120) performs the function of receiving and processing a customer authentication request received from the first institution terminal (300).

[0108] According to one embodiment, the authentication request transmission unit (120) may transmit customer authentication request data to the second institution terminal (400) based on customer authentication request data. That is, the customer authentication request data may include information indicating that the customer is requesting authentication of the customer to the second institution based on the customer authentication request.

[0109] In one embodiment, the authentication application transmission unit (120) may configure the second institution terminal (400) to receive customer verification authentication application data based on the institution selection information. For example, if the institution selection information includes "Bank A," the authentication application transmission unit (120) may configure the terminal device used by "Bank A" as the second institution terminal (400) that receives the customer verification authentication application data.

[0110] In addition, the authentication application transmission unit (120) can transmit customer verification authentication application data including first customer information to the second institution terminal (400). For example, if the first customer information includes a customer account number of “Bank A,” the authentication application transmission unit (120) can generate customer verification authentication application data including the customer account number of “Bank A” and transmit it to the terminal used by “Bank A.”

[0111] Next, the customer verification relay unit (130) performs the function of relaying the procedure related to customer authentication between the first agency terminal (300) and the second agency terminal (400).

[0112] According to one embodiment, the customer verification relay unit (130) may relay a customer verification process performed between a first institution terminal (300) and a second institution terminal (400) regarding the customer based on customer verification authentication application data. Here, the customer verification process may refer to a process performed between the first institution terminal (300) and the second institution terminal (400) for customer identity authentication.

[0113] According to one embodiment, the customer verification relay unit (130) may receive reception information data corresponding to customer verification authentication application data from the second institution terminal (400). Specifically, the customer verification relay unit (130) may receive reception information data generated based on whether the first customer information matches the second customer information stored in association with the second institution terminal (400). For example, “Bank A” selected as the second institution by the customer may check the customer’s account number included in the customer verification authentication application data to confirm whether it is an account number of “Bank A.” If it is determined that the account number of “Bank A” is correct, the second institution terminal (400) may generate reception information data including information that the customer’s identity verification has been received and transmit the generated reception information data to the customer verification relay unit (130). At this time, the second institution terminal (400) may generate an authentication number and transmit the authentication number to the customer’s account number. For example, the second agency terminal (400) can send an authentication number by entering the authentication number in the deposit field while sending '1 won' to the customer's account.

[0114] In addition, the customer verification relay unit (130) can transmit authentication information request data regarding the customer to the first agency terminal (300) based on the reception information data. For example, if reception information data indicating that the customer's identity verification has been received is received, the customer verification relay unit (130) can request an authentication number from the first agency terminal (300).

[0115] In addition, the customer verification relay unit (130) can receive authentication data corresponding to authentication information request data from the first institution terminal (300). For example, if a customer transmits an authentication number to the first institution terminal (300) through the customer terminal (200), the first institution terminal (300) can transmit authentication data including the authentication number entered by the customer to the customer verification relay unit (130).

[0116] In addition, the customer verification relay unit (130) can transmit authentication data to the second agency terminal (400).

[0117] Next, the verification result receiving unit (140) can perform a function of receiving the final result regarding the customer's identity authentication.

[0118] According to one embodiment, the verification result receiving unit (140) may receive customer verification result data regarding the customer from the second agency terminal (400) based on the result of the customer verification process.

[0119] According to one embodiment, the verification result receiving unit (140) may receive customer verification result data generated based on whether the authentication information generated by the second institution terminal (400) matches the authentication data. Here, the authentication information may be generated by the second institution terminal (400) when the first customer information and the second customer information match. For example, if the first customer information “customer account number” entered by the customer and the second customer information “customer account number” stored in the second institution terminal (400) match, the second customer terminal (200) may generate an authentication number as authentication information. In addition, the customer verification result data may be data including whether the second institution terminal (400) has authenticated the customer’s identity. For example, if the authentication number transmitted to the second institution terminal (400) matches the authentication number generated by the second institution terminal (400), the customer verification result data may include content indicating that the customer’s identity has been authenticated. Additionally, if the authentication number transmitted to the second agency terminal (400) matches the authentication number generated by the second agency terminal (400), the customer verification result data may include the date the customer's identity verification was performed, the date the customer's identity verification must be re-performed, and the customer's risk assessment result. On the other hand, if the authentication number transmitted to the second agency terminal (400) does not match the authentication number generated by the second agency terminal (400), the customer verification result data may include a statement that the customer's identity verification is not authenticated.

[0120] Meanwhile, according to one embodiment, the customer verification result data may not include financial information stored in relation to the first institution terminal (300). For example, the customer verification result data may not include document information used for identity verification. For example, the customer verification result data may not include documents related to identity verification, such as the WLF (Watch List Filtering) performance date, WLF processing result, CDD (Customer Due Diligence) performance date, re-performance scheduled date, RA (Risk Assessments) performance date, RA grade, RA grade name, EDD (Enhanced Due Diligence) target status, EDD performance date, source and origin of funds, and transaction purpose, held by the second institution.

[0121] Next, the verification result transmission unit (150) can transmit customer verification result data to the first agency terminal (300).

[0122] Next, the verification result update unit (160) performs a function of transmitting information for renewing the identity authentication of a customer for whom identity authentication was performed using the customer authentication relay device (100) according to an embodiment of the present invention to the first institution terminal (300) after a certain period of time has elapsed.

[0123] According to one embodiment, the confirmation result update unit (160) can transmit updated customer confirmation result data to the second agency terminal (400) based on preset schedule information.

[0124] In one embodiment, the verification result update unit (160) may determine whether the expiration date of customer verification result data falls within a predetermined period based on preset schedule information. For example, the verification result update unit (160) may determine whether the expiration date of the customer verification-related validity period for which a customer previously completed identity verification between 00:00 and 6:00 AM each day falls within a period of 30 days from the current day.

[0125] In addition, if the verification result renewal unit (160) determines that the expiration date falls within a predetermined period, it may transmit renewal request data for the customer verification result data regarding the customer to the second agency terminal (400). In this process, the verification result renewal unit (160) may not request additional information or instructions related to the customer's identity verification from the customer and the first agency.

[0126] And, the confirmation result update unit (160) can receive updated customer confirmation result data from the second agency terminal (400).

[0127] And, the confirmation result update unit (160) can transmit the updated customer confirmation result data to the first agency terminal (300).

[0128] Figure 4 is a flowchart of a customer verification authentication relay method according to an embodiment of the present invention.

[0129] Figure 4 can be implemented using the customer verification authentication relay device (100) described above.

[0130] Referring to FIG. 4, first, the authentication request receiving unit (110) may receive customer verification authentication request data regarding a customer from the first institution terminal (300) (S410). Specifically, the authentication request receiving unit (110) may receive customer verification authentication request data including institution selection information corresponding to the second institution terminal (400) and first customer information entered in response to the institution selection information.

[0131] Next, the customer verification authentication request data can be transmitted to the second agency terminal (400) based on the customer verification authentication request data of the authentication application transmission unit (120) (S420).

[0132] Next, the customer verification relay unit (130) can relay the customer verification process performed between the first agency terminal (300) and the second agency terminal (400) regarding the customer based on the customer verification authentication application data (S430).

[0133] Next, the verification result receiving unit (140) may receive customer verification result data regarding the customer from the second institution terminal (400) based on the results of the customer verification process (S440). Specifically, the verification result receiving unit (140) may receive customer verification result data generated based on whether the authentication information generated by the second institution terminal (400) matches the authentication data. Here, the authentication information may be generated by the second institution terminal (400) if the first customer information matches the second customer information. Here, the customer verification result data may not include financial information stored in relation to the first institution terminal (300).

[0134] Next, the verification result transmission unit (150) can transmit customer verification result data to the first agency terminal (300) (S450).

[0135] Figure 5 is an example showing step S420 of Figure 4 in detail.

[0136] Referring to FIG. 5, first, the authentication application transmission unit (120) can set the second organization terminal (400) to receive customer verification authentication application data based on organization selection information (S510).

[0137] Next, the authentication application transmission unit (120) can transmit customer verification authentication application data including first customer information to the second agency terminal (400) (S520).

[0138] Figure 6 is an example showing step S430 of Figure 4 in detail.

[0139] Referring to FIG. 6, the customer verification relay unit (130) may receive reception information data corresponding to customer verification authentication application data from the second agency terminal (400) (S610). Specifically, the customer verification relay unit (130) may receive reception information data generated based on whether the first customer information matches the second customer information stored in connection with the second agency terminal (400).

[0140] Next, the customer verification relay unit (130) can transmit authentication information request data about the customer to the first agency terminal (300) based on the reception information data (S620).

[0141] Next, the customer verification relay unit (130) can receive authentication data corresponding to authentication information request data from the first agency terminal (300) (S630).

[0142] Next, the customer verification relay unit (130) can transmit authentication data to the second agency terminal (400) (S640).

[0143] FIG. 7 is a flowchart illustrating another example of a customer verification authentication relay method according to an embodiment of the present invention.

[0144] According to one embodiment, the step illustrated in FIG. 7 may be performed after the step of FIG. 4.

[0145] Referring to FIG. 7, the confirmation result update unit (160) can transmit updated customer confirmation result data based on preset schedule information to the second agency terminal (400) (S700).

[0146] Specifically, the confirmation result update unit (160) can determine whether the expiration date of the customer confirmation result data is within a predetermined period range based on preset schedule information (S710).

[0147] Next, if the verification result renewal unit (160) determines that the expiration date is included in a predetermined period range, it can transmit renewal request data for customer verification result data regarding the customer to the second agency terminal (400) (S720).

[0148] Next, the confirmation result update unit (160) can receive updated customer confirmation result data from the second agency terminal (400) (S730).

[0149] Next, the verification result update unit (160) can transmit the updated customer verification result data to the first agency terminal (300) (S740).

[0150] The term '~ part' used in this embodiment means a software or hardware component such as an FPGA (field-programmable gate array) or an ASIC, and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Thus, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.

[0151] Although the above description focuses on examples, these are merely examples and do not limit the present invention. Those skilled in the art will appreciate that various modifications and applications not exemplified above are possible without departing from the essential characteristics of the present invention. For example, each component specifically shown in the examples can be modified and implemented. In addition, differences related to such modifications and applications should be construed as being included within the scope of the present invention defined in the appended claims.

Claims

1. An authentication request receiving unit that receives customer verification authentication request data regarding a customer from a terminal of the first agency; An authentication request transmission unit that transmits customer authentication request data to a second agency terminal based on the above customer authentication request data; A customer verification relay unit that relays a customer verification process performed between the first agency terminal and the second agency terminal based on the customer verification authentication application data; A verification result receiving unit that receives customer verification result data about the customer from the second agency terminal based on the result of the customer verification process; and A customer verification authentication relay device including a verification result transmission unit that transmits the customer verification result data to the first institution terminal.

2. In paragraph 1, The above authentication request receiving unit, A customer verification authentication relay device that receives customer verification authentication request data including agency selection information corresponding to the second agency terminal and first customer information entered in response to the agency selection information.

3. In paragraph 2, The above authentication application transmission section is, Based on the above-mentioned institution selection information, the second institution terminal is set to receive the customer verification authentication application data; A customer verification authentication relay device that transmits customer verification authentication application data including the first customer information to the second agency terminal.

4. In paragraph 1, The above customer verification relay department is, Receive reception information data corresponding to the customer verification authentication application data from the second agency terminal; Transmitting authentication information request data regarding the customer to the first institution terminal based on the above reception information data; Receive authentication data corresponding to the authentication information request data from the first agency terminal; A customer verification authentication relay device that transmits the above authentication data to the second agency terminal.

5. In paragraph 4, The above customer verification relay department is, A customer verification authentication relay device that receives the reception information data generated based on whether the first customer information matches the second customer information stored in connection with the second agency terminal.

6. In paragraph 5, As a result of the above verification, the receiver, A customer verification authentication relay device that receives the customer verification result data generated based on whether the authentication information generated by the second agency terminal matches the authentication data.

7. In paragraph 6, The above authentication information is, A customer verification authentication relay device generated by the second institution terminal when the first customer information and the second customer information match.

8. In paragraph 1, The above customer verification result data is, A customer verification authentication relay device characterized in that it does not include financial information stored in relation to the first institution terminal.

9. In paragraph 1, A customer verification authentication relay device including a verification result update unit that transmits the updated customer verification result data based on preset schedule information to the second agency terminal.

10. In paragraph 9, As a result of the above verification, the renewal department, Based on the above preset schedule information, determine whether the expiration date of the customer verification result data falls within a specified period range; If it is determined that the above expiration date is within a specified period, a request for renewal of customer verification result data regarding the customer is transmitted to the second agency terminal; Receive updated customer verification result data from the second agency terminal; A customer verification authentication relay device that transmits the updated customer verification result data to the first institution terminal.

11. Step of receiving customer verification request data regarding the customer from the first agency terminal; A step of transmitting customer verification authentication request data to a second institution terminal based on the above customer verification authentication request data; A step of relaying a customer verification process performed between the first institution terminal and the second institution terminal regarding the customer based on the customer verification authentication application data; A step of receiving customer verification result data regarding the customer from the second agency terminal based on the result of the customer verification process; and A customer verification authentication relay method, comprising: a step of transmitting the customer verification result data to the first institution terminal.

12. In paragraph 11, The step of entering the above customer verification request data is: A customer verification authentication relay method for receiving customer verification authentication request data including agency selection information corresponding to the second agency terminal and first customer information entered corresponding to the agency selection information.

13. In paragraph 12, The step of transmitting the above customer verification authentication application data is: A step for setting the second institution terminal to receive the customer verification authentication application data based on the institution selection information; and A customer verification authentication relay method comprising the step of transmitting customer verification authentication application data including the first customer information to the second institution terminal.

14. In paragraph 11, The steps for relaying the above customer verification process are: A step of receiving reception information data corresponding to the customer verification authentication application data from the second agency terminal; A step of transmitting authentication information request data regarding the customer to the first institution terminal based on the above reception information data; A step of receiving authentication data corresponding to the authentication information request data from the first agency terminal; and A customer verification authentication relay method comprising: a step of transmitting the above authentication data to the second agency terminal; 15. In paragraph 14, The step of entering the above reception information data is: A customer verification authentication relay method for receiving the reception information data generated based on whether the first customer information matches the second customer information stored in connection with the second institution terminal.

16. In paragraph 15, The step of entering the above customer verification result data is: A customer verification authentication relay method for receiving the customer verification result data generated based on whether the authentication information generated by the second agency terminal matches the authentication data.

17. In paragraph 16, The above authentication information is, A customer verification authentication relay method generated by the second institution terminal when the first customer information and the second customer information match.

18. In paragraph 11, The above customer verification result data is, A customer verification authentication relay method characterized in that it does not include financial information stored in relation to the first institution terminal.

19. In paragraph 11, A customer verification authentication relay method comprising: a step of transmitting the updated customer verification result data based on preset schedule information to the second institution terminal.

20. In paragraph 19, The step of transmitting the updated customer verification result data to the second agency terminal is as follows: A step of determining whether the expiration date of the customer verification result data falls within a predetermined period range based on the above-described preset schedule information; If it is determined that the above expiration date is within a specified period, a step of transmitting renewal request data for customer verification result data regarding the customer to the second agency terminal; A step of receiving updated customer verification result data from the second agency terminal; and A customer verification authentication relay method comprising: a step of transmitting the updated customer verification result data to the first institution terminal;

Images