KR102451670B1 - System for performing simple payment registration based common encryption of account and name, and simple payment registration method - Google Patents

Abstract

A simple payment registration method of the system is disclosed. The simple payment registration method includes the steps of: receiving, by the user terminal, account holder information and account information; the server encrypting authentication information including the account holder information and account information input through the user terminal; Decrypting the encrypted authentication information, the financial institution server comparing the decrypted authentication information with information about the previously stored account to determine whether authentication succeeds, based on whether the authentication succeeds, the server, the user terminal and registering simple payment through the user terminal according to the password set through the .

Description

A system for performing simple payment registration by common encryption of account and name, and a method for registering simple payment

The present disclosure relates to a system for performing simple payment registration, and more particularly, to a system for simplifying a simple payment registration process by encrypting an account and a name in common.

Simple payment refers to a fast and simple online payment in which payment through a specific account or specific card is directly performed only by input of a password through a terminal device (ex. smartphone) or recognition of biometric information (ex. fingerprint) .

In order to register for easy payment, you generally go through steps such as identity verification through a user terminal (ex. smartphone), account name inquiry, ARS (Audio Response System) withdrawal agreement, and password setting (used for simple payment). .

In relation to this, FIG. 1 is a view for statistically explaining the dropout rate for each stage of the conventional simple payment registration process. Here, the departure rate is defined according to the number of times a customer who wants to perform simple payment registration leaves without performing simple payment registration until the end.

Referring to FIG. 1 , in the simple payment registration process consisting of a total of 4 steps, the probability that the customer reached the final registration was 57.7%, and the probability that the customer deviated from at least one step was 42.2%.

Referring to FIG. 1 , the dropout rates in the mobile phone identity verification step and account name inquiry step were 30.6% and 5.4%, respectively, which was very high compared to other steps.

In particular, in the case of the mobile phone identity verification stage, a high dropout rate of 30.6% was recorded. ), or if the mobile phone is not in the customer's own name, it is confirmed that the possibility of departure is very high.

Laid-Open Patent Publication No. 10-2020-0048134 (Method of registering simple payment service through non-face-to-face account opening)

The present disclosure provides a simple payment registration method of a system for simplifying the simple payment registration process and lowering the dropout rate by authenticating the account holder and the account without performing mobile phone identification.

The present disclosure is a user terminal (ex. PC, mobile phone, smart phone, etc.) that is not under the user's name and is a terminal in which the simple payment system managed, provided and operated by the simple payment service provider is normally installed and operated, and safe simple payment registration and use is possible. A simple payment registration method of the system that makes this possible is provided.

Objects of the present disclosure are not limited to the above-mentioned purposes, and other objects and advantages of the present disclosure that are not mentioned may be understood by the following description, and will be more clearly understood by examples of the present disclosure. Moreover, it will be readily apparent that the objects and advantages of the present disclosure may be realized by the means and combinations thereof indicated in the claims.

In an embodiment of the present disclosure, the simple payment registration method of a system for registering simple payment for performing payment by remittance of an amount of a specific account according to input of a password, includes the steps of: a user terminal receiving account holder information and account information , encrypting, by the server, authentication information including the account holder information and the account information input through the user terminal, the financial institution server decrypting the encrypted authentication information, the financial institution server, the Comparing the decrypted authentication information with the information on the pre-stored account to determine whether authentication succeeds, based on whether the authentication succeeds, the server through the user terminal according to the password set through the user terminal It includes the step of registering easy payment.

In the step of receiving the depositor information and account information, the name of the depositor, the date of birth of the depositor, the bank name, the account number, and the account password may be received.

In this case, the simple payment registration method of the system performs at least one of a call, a recording, an electronic signature request for an electronic document, and SMS transmission and reception through the terminal of the input phone number to confirm whether the depositor agrees with the withdrawal. The method may further include the step of registering the simple payment, regardless of whether the account holder and the user of the user terminal match, based on the success of the authentication and whether the withdrawal agreement is made through the user terminal. It is possible to register the simple payment of the account holder.

In addition, the encrypting of the authentication information may include encrypting the authentication information including the name of the account holder, the date of birth of the account holder, the account number, and the account password. In this case, in the decrypting of the authentication information, the financial institution server matching the bank name may decrypt the encrypted authentication information.

Meanwhile, the financial institution server may include information on a plurality of accounts, and the information on each of the plurality of accounts may include a name of a depositor, a date of birth of a depositor, an account number, and an account password. In this case, the step of determining whether the authentication is successful may include obtaining encrypted information by encrypting the decrypted authentication information, and obtaining encrypted information on at least one account among the plurality of accounts. Depending on whether the information is matched, it may be determined whether the authentication is successful.

On the other hand, the simple payment registration method of the system includes the steps of performing verification according to a security card password or OTP (One Time Password) based on the input account holder information and account information, or the input account holder information and account information Based on the , it may further include the step of performing verification according to a certificate that can confirm the identity. In this case, the registering of the simple payment may include registering the simple payment through the user terminal based on whether the verification succeeds and whether the determined authentication succeeds.

In addition, the simple payment registration method of the system includes the steps of, when the simple payment is registered, limiting the number of times of the simple payment that can be performed through the user terminal to a preset number of times, after the simple payment is registered , when the identity authentication of the account holder of the account corresponding to the simple payment is performed with respect to the user terminal, releasing the limit setting for the allowed number of times of the simple payment may be further included.

In addition, the simple payment registration method of the system includes the steps of: when the simple payment is registered, identifying at least one user terminal having a history of self-authentication by the account holder of the account corresponding to the simple payment; The method may further include transmitting information notifying the registration of the simple payment to the user terminal.

In one embodiment of the present disclosure, a system for registering a simple payment for performing a payment by remittance of an amount of a specific account according to an input of a password includes a user terminal receiving account holder information and account information, and a user terminal inputted through the user terminal. A server that encrypts authentication information including the account holder information and the account information, decrypts the encrypted authentication information, and compares the decrypted authentication information with information about a pre-stored account to determine whether authentication succeeds, Includes financial institution servers. And, the server, based on the determined success of the authentication, according to the password set through the user terminal to register the simple payment through the user terminal.

In one embodiment of the present disclosure, the simple payment registration method of the server for registering the simple payment for performing the payment by remitting the amount of the specific account according to the input of the password, the account holder information input through the user terminal from the user terminal and receiving account information, encrypting authentication information including the account holder information and the account information, and transmitting the encrypted authentication information to a financial institution server, from the financial institution server, whether or not authentication succeeds according to the encrypted authentication information Receiving the information, based on whether the authentication is successful, according to the password set through the user terminal, comprising the step of registering a simple payment through the user terminal.

The simple payment registration method according to the present disclosure maximizes the convenience of simple payment registration and reduces the dropout rate by reducing the user's input procedure by unifying the mobile phone identity verification and account inquiry process in the conventional simple payment into one modified process. It works.

In addition, the simple payment registration method according to the present disclosure enables high-security authentication using account information and a financial institution server even through a user terminal in the name of another person, so that simple payment registration is also possible through a user terminal in the name of another person There is a heterogeneous effect of making

1 is a view for explaining the departure rate for each stage of the conventional simple payment registration process;
2 is a block diagram for explaining the configuration of a system according to an embodiment of the present disclosure;
3 is a flowchart for explaining the operation of a system according to an embodiment of the present disclosure;
4 is a view for explaining an authentication process of a system according to an embodiment of the present disclosure;
5 is a view for explaining a simple payment registration process of the system according to an embodiment of the present disclosure, and
6 is an algorithm for explaining an operation of the system limiting the number of times of performing simple payment after registering simple payment according to an embodiment of the present disclosure.

Prior to describing the present disclosure in detail, a description will be given of the description of the present specification and drawings.

First, terms used in the present specification and claims have been selected in consideration of functions in various embodiments of the present disclosure. However, these terms may vary depending on the intention or legal or technical interpretation of a person skilled in the art, and the emergence of new technology. Also, some terms are arbitrarily selected by the applicant. These terms may be interpreted in the meaning defined in the present specification, and if there is no specific term definition, it may be interpreted based on the general content of the present specification and common technical knowledge in the art.

Also, the same reference numerals or reference numerals in each drawing attached to this specification indicate parts or components that perform substantially the same functions. For convenience of description and understanding, the same reference numerals or reference numerals are used in different embodiments. That is, even though all components having the same reference number are illustrated in a plurality of drawings, the plurality of drawings do not mean one embodiment.

In addition, in this specification and claims, terms including an ordinal number, such as "first" and "second", may be used to distinguish between elements. This ordinal number is used to distinguish the same or similar elements from each other, and the meaning of the term should not be construed as limited due to the use of the ordinal number. For example, the components combined with such an ordinal number should not be limited in the order of use or arrangement by the number. If necessary, each ordinal number may be used interchangeably.

In this specification, the singular expression includes the plural expression unless the context clearly dictates otherwise. In the present application, terms such as "comprises" or "consisting of" are intended to designate that the features, numbers, steps, operations, components, parts, or combinations thereof described in the specification exist, and are intended to indicate that one or more other It is to be understood that this does not preclude the possibility of addition or presence of features or numbers, steps, operations, components, parts, or combinations thereof.

In an embodiment of the present disclosure, terms such as “module”, “unit”, “part”, etc. are terms for designating a component that performs at least one function or operation, and such component is hardware or software. It may be implemented or implemented as a combination of hardware and software. In addition, a plurality of "modules", "units", "parts", etc. are integrated into at least one module or chip, except when each needs to be implemented as individual specific hardware, and thus at least one processor. can be implemented as

In addition, in an embodiment of the present disclosure, when a part is connected to another part, this includes not only direct connection but also indirect connection through another medium. In addition, the meaning that a certain part includes a certain component means that other components may be further included without excluding other components unless otherwise stated.

2 is a block diagram illustrating the configuration of a system according to an embodiment of the present disclosure.

Referring to FIG. 2 , the system 1000 may include a server 100 , a user terminal 200 , a financial institution server 300 , and the like.

Devices in the system 1000 may perform communication based on at least one network.

The network may be a personal area network (PAN), a local area network (LAN), a wide area network (WAN), etc. depending on the area or size, and depending on the openness of the network, an intranet, It may be an extranet or the Internet.

Devices in the system 1000 are long-term evolution (LTE), LTE Advance (LTE-A), 5th generation (5G) mobile communication, code division multiple access (CDMA), wideband CDMA (WCDMA), universal mobile telecommunications (UMTS) system), WiBro (Wireless Broadband), GSM (Global System for Mobile Communications), DMA (Time Division Multiple Access), WiFi (Wi-Fi), WiFi Direct, Bluetooth, NFC (near field communication), Zigbee, etc. methods can be connected to each other. In addition, each device may be connected to each other through a wired communication method such as Ethernet, an optical network, a Universal Serial Bus (USB), or a ThunderBolt.

The server 100 may include one or more computers connected to each other, and may be implemented as a payment relay server that relays registration/execution of simple payment.

In this case, the server 100 may be connected to at least one content providing server to perform functions (registration, execution) related to simple payment within the service provided by the content providing server.

The content providing server may correspond to a service server for providing a web page/application that performs various functions such as online shopping, online payment, offline simple payment, search, social network service (SNS), and media content provision.

As a specific example, the server 100 may be linked with at least one content providing server that provides online shopping (web page/application), and among the services (online shopping) provided by the content providing server through the user terminal 200 , The server 100 may act on behalf of functions related to simple payment (eg, simple payment registration, simple payment execution, etc.).

Meanwhile, the server 100 itself may be a content providing server. As an example, the server 100 may directly provide a function of registering/performing simple payment performed during online shopping while providing an online shopping service.

The server 100 may be linked with the user terminal 200 through at least one web page or application to provide a simple payment registration function according to various embodiments to be described later.

The user terminal 200 is a means for at least one customer to perform a simple payment and corresponds to a registration target of the simple payment.

The server 100 may be connected to a plurality of user terminals, and may provide a simple payment registration service according to various embodiments to be described later through each user terminal.

The user terminal 200 may correspond to various terminal devices, such as a smart phone, a tablet PC, a notebook PC, a desktop PC, a personal digital assistant (PDA), a wearable device, and a VR/AR device.

The financial institution server 300 may be implemented as one or more computers connected to each other, and a bank, a securities company, an insurance company, a credit card company, an electronic financial company, an electronic financial auxiliary business operator, a credit information company, a personal credit information management company, a debt collection company , it may be a server of various financial institutions that perform financial business or personal credit information processing, such as a credit information concentration institution, a credit information provider/use company, and a financial-related public institution.

The server 100 may communicate with a plurality of financial institution servers, and for example, a financial institution server for each bank may be included in the system 1000 to communicate with the server 100 .

The financial institution server 300 may include information on a plurality of accounts that may each be a means of simple payment. Here, the information about each account may include the name of the account holder, the date of birth of the account holder, account number, account password, and other security information (eg, other identification numbers, security card information, OTP (One Time Password), etc.). have.

In addition, the financial institution server 300 may include information on a plurality of cards that can be a means of simple payment. Here, the information on each card may include the card user's name, date of birth, card number, card password, and other security information.

Hereinafter, a simple payment registration method performed by the system 100 according to an embodiment of the present disclosure will be described with reference to FIG. 3 .

Referring to FIG. 3 , account holder information and account information may be input through the user terminal 200 ( S310 ).

Specifically, when a user command requesting simple payment registration is received through the user terminal 200 , the server 100 provides at least one UI (User Interface) for guiding the input of account holder information and account information to the user terminal 200 . ) can be provided through

Here, the account holder information may include the name of the account holder, date of birth, resident registration number, and the like.

And, the account information may include a bank name, an account number, an account password, and the like.

Also, the server 100 may receive at least one phone number input through the user terminal 200 .

This phone number can be used later in the withdrawal agreement process. As a specific example, if authentication according to the account holder information and account information is successful, the withdrawal agreement process (eg ARS, call/recording, SMS, electronic signature for electronic documents, etc.) may be performed through the terminal of the corresponding phone number.

And, referring to FIG. 3 , the server 100 may encrypt authentication information including account holder information and account information ( S320 ).

Specifically, the server 100 may encrypt authentication information including the name of the account holder, the date of birth of the account holder, the account number, and the account password. Here, the name of the account holder, date of birth, account number, account password, and the like are commonly encrypted to generate one piece of encrypted information.

In this case, the server 100 may encrypt the authentication information using various encryption algorithms.

The encryption algorithm used to encrypt the authentication information may be a symmetric key encryption algorithm, a public key encryption algorithm, or the like, and a combination of a symmetric key encryption algorithm and a public key encryption algorithm is also possible.

Specifically, the encryption algorithm is, Advanced Encryption Standard (AES), SEED, Rivest Cipher 4 (RC4), Rivest Shamir Adleman (RSA), digital signature Algorithm (DSS), Diffie-Hellman (DH), Elliptic Curve DSA (ECDSA). , ECDH (Elliptic Curve DH), and the like can be implemented.

In addition, the encryption algorithm may be implemented as a post quantum encryption algorithm such as Rainbow, QC-MDPC, SS-NTRU, SIDH, or the like.

In particular, the encryption algorithm used in the server 100 according to the present disclosure corresponds to an encryption algorithm that meets the security strength/standard recommended by organizations such as the Financial Security Institute or NIST (National Institute of Standards and Technology) by era. can

The server 100 may transmit authentication information encrypted according to the above-described encryption algorithm to the financial institution server 300 .

Specifically, the server 100 may transmit the encrypted authentication information to the financial institution server 300 matching the bank name input as the account information.

And, referring to FIG. 3 , the financial institution server 300 (matching the input bank name) may decrypt authentication information encrypted in the server (S330). To this end, the financial institution server 300 may include at least one module for decrypting authentication information encrypted in the server 100 .

In addition, the financial institution server 300 compares the decrypted authentication information (ex. account number, account password, name of account holder, date of birth (resident registration number)) of the account holder with information about the stored account to determine whether authentication succeeds. (S340).

As a specific example, the financial institution server 300 may obtain encrypted information by encrypting the decrypted authentication information.

In this case, the financial institution server 300 may encrypt the authentication information using various encryption algorithms.

As a specific example, the financial institution server 300 may encrypt the authentication information using a hash algorithm, but is not limited thereto. Encryption processing performed by the financial institution server 300 may be different for each financial institution (eg, each bank).

In addition, the financial institution server 300 may determine whether authentication is successful according to whether there is an account matching the encrypted authentication information among the plurality of accounts.

Specifically, the financial institution server 300 encrypts information (eg, account number, account password, name of the account holder, date of birth (resident registration number)) of at least one account among the plurality of accounts (ex. hash algorithm). , it is possible to check whether the decrypted authentication information matches information processed by encryption (ex. hash algorithm) again.

In addition, the financial institution server 300 may determine whether authentication is successful according to whether or not there is a match. Specifically, when the authentication information matches at least one account, it may be determined that authentication is successful.

And, referring to FIG. 3 , the server 100 may register simple payment through the user terminal 200 based on the success of authentication (determined by the financial institution server 300) (S350) .

Specifically, when authentication is successful, the server 100 may receive a password for simple payment through the user terminal 200 and set the password as a password for simple payment.

In addition, before or after the password for simple payment is input, the server 100 performs a call with the terminal of the phone number entered through the user terminal 200 to confirm the depositor's withdrawal agreement or to make an electronic signature. You can also receive confirmation of the depositor's withdrawal agreement through electronic documents or SMS.

And, the server 100 sets the account matching the previously input account information (ex. account number) as a target account for simple payment through the user terminal 200, and can register simple payment according to the input password. have.

Thereafter, when a (customer's) simple payment request is received through the user terminal 200 , the server 100 simply transfers a predetermined amount from the target account on the premise that a password is input through the user terminal 200 . Payment can be made.

4 is a view for explaining an authentication process of a system according to an embodiment of the present disclosure.

Referring to FIG. 4 , the server 100 may be connected to a customer's terminal to receive account holder information and account information.

Alternatively, the server 100 receives account holder information (ex. name, date of birth, resident registration number, etc.) and account information (ex. bank name, account number, account password, etc.).

In addition, the server 100 may encrypt authentication information including account holder information and account information through the common encryption module 410 .

Specifically, the common encryption module 410 may encrypt the name of the account holder, the account number, the account password, and the date of birth (or resident registration number) of the account holder in common.

Also, the server 100 may identify the server 300 - 1 matching the bank name (eg, bank A) of the account information.

Then, the server 100 may transmit the encrypted authentication information to the corresponding server 300-1.

A bank server 300 - 1 may decrypt the encrypted authentication information through the common decryption module 420 .

The encryption/decryption processing algorithm of the above-described common encryption module 410 and common decryption module 420 may use, for example, an Advanced Encryption Standard (AES_CBC) algorithm, which is a symmetric key encryption algorithm. In this case, in order to increase security, the length of the symmetric key may be 256 bits or more.

At this time, rather than constructing a separate system that exchanges symmetric keys every time a transaction occurs, the counterparty's public/private key is exchanged regularly (up to 2 years), and using this, the Rivest Shamir Adleman (RSA) algorithm, an asymmetric key encryption algorithm, is used. It can be implemented to exchange the symmetric key required for data encryption/decryption by encrypting and then exchanging the symmetric key by applying .

In addition, the bank A server 300-1 may determine whether the decrypted authentication information matches the account previously stored in the bank A server 300-1.

In detail, the bank A server 300 - 1 encrypts the decrypted authentication information again through the encryption module 430 for each bank to identify whether it matches (matches) with at least one of pre-stored accounts.

As an example, the bank A server 300-1 may identify the name and date of birth of the account holder from the decrypted authentication information.

Here, the bank A server 300-1 includes information on at least one previously stored account matching the identified name and date of birth among the information on a plurality of accounts previously stored on the bank A server 300-1 (ex. The name of the account holder, the date of birth of the account holder, account number, account password, etc.) can be identified.

And, the bank A server 300-1 compares the information of the identified account encrypted (ex. hash algorithm) with authentication information encrypted (ex. hash algorithm) through the encryption module 430 for each bank. By doing so, it is possible to identify whether they match. The bank-specific encryption module 430 may be a module built according to an independently built encryption algorithm for each server of each bank (300-1, 2, 3, ...).

As another example, the bank A server 300-1 may identify an account number from the decrypted authentication information, and may identify information on an account matching the identified account number among a plurality of pre-stored information on accounts.

In this case, similarly, the bank A server 300-1 compares the encrypted information about the identified account with the authentication information encrypted through the encryption module 430 for each bank, to identify whether the information matches. .

However, an embodiment in which the bank A server 300-1 does not use the encryption module 430 for each bank is not impossible.

In this case, the bank A server 300 - 1 may identify whether the authentication information decrypted through the common decryption module 420 is matched with information on at least one previously stored account.

According to the above-described various embodiments, when it is determined whether or not the account matches the pre-stored account, the server 300 - 1 may determine whether authentication of the account holder and the account is successful according to the match. Specifically, when it is determined that it matches the pre-stored one account, it is determined that the authentication is successful.

On the other hand, in addition to the above-described embodiment, the server 100 through the user terminal 200 information (card number, card company / bank, expiration date, CVC value, password, date of birth) about the account holder's credit card (or check card) etc.) may be additionally input.

That is, the server 100 may additionally receive information about the account holder's credit card in addition to the account information and the holder information of the account, which is a means of simple payment.

In this case, the server 100 may transmit (encryption possible) information on the credit card to a financial institution server that matches the information on the credit card (eg, the B bank server 300-2: a card company).

Here, information on the card user matching the information on the credit card may be identified through the B bank server 300 - 2 , and the server 100 is the card user identified through the B bank server 300 - 2 . You can compare the information about the account holder (: information about the account holder).

That is, the server 100 not only authenticates through the A bank server 300-1 (account information and account information), but also performs authentication through the B bank server 300-2 (compare credit card information with the account holder). You can register for simple payment on the premise.

In this case, even when the account holder information and account information are exposed, since information on a separate credit card in the name of the account holder is further required, the security of identity authentication can be improved. Even if the account holder does not have a user terminal device in his/her name, he/she can perform high-security self-authentication through at least one credit card possessed by the account holder.

5 is a view for explaining a simple payment registration process of the system according to an embodiment of the present disclosure.

Referring to FIG. 5 , the simple payment registration process (S500) provided by the server 100 may consist of three steps: account and name inquiry/authentication (S510), withdrawal agreement (S520), and password setting (S530). have.

The above-described embodiment of FIG. 4 corresponds to an example of step S510.

Meanwhile, in the authentication process of step S510, separate verification using the OTP or security card serial number for the account may be additionally performed.

Specifically, the server 100 may additionally perform verification according to a security card password or OTP (One Time Password) based on account holder information and account information input through the user terminal 200 .

Alternatively, a separate verification using a certificate that can confirm the identity may be additionally performed.

Specifically, the server 100, based on the account holder information and account information input through the user terminal 200, a real certificate or mobile driver's license verification service that can confirm identity such as a resident registration card, driver's license, passport, alien registration card Alternatively, verification may be performed according to a digital ID using an identification service.

In addition, the server 100 may provide a question (problem) to the account holder and perform verification according to a user's response input to the question.

Specifically, the server 100 collects various information about the account holder of the authenticated account (eg, name, age, birthday, mobile phone number, graduation school, hobbies, specialties, interests, recent purchase/transfer history, frequently used shopping malls, etc.) One or more questions to be inquired may be provided through the user terminal 200 .

Here, the server 100 may receive the user's response to the question through the user terminal 200 , and may perform verification according to whether the user's response matches information about the account holder.

As a specific example, when the ratio of correct answers to the provided questions (the ratio in which the user's response matches information about the account holder) is greater than or equal to a certain ratio (ex. 90%), the verification may be identified as successful.

In this case, in addition to the success of authentication according to the embodiment described with reference to FIG. 4 , the success of verification (OTP, security card, various certificates, etc.) is also considered, so that the simple payment of the user terminal 200 can be registered. .

For example, the server 100 may receive an OTP or security card serial number matching the input account information and perform verification through the financial institution server 300 or at least one separate authentication server.

In this case, the server 100 may proceed to the next step (ex. S520) on the assumption that both the verification according to the OTP or security card serial number and the authentication according to FIG. 4 are successful.

When authentication of the account and name is performed through the above-described step S510, the server 100 may check whether the withdrawal is agreed to (S520).

Specifically, the server 100 may receive an input of a phone number that can be called through the user terminal 200, and performs a call with the terminal of the corresponding phone number to record a call or an Audio Response System (ARS). Based on this, it is possible to check whether the depositor agrees to withdrawal. Alternatively, the server 100 may check whether the withdrawal is agreed to based on an electronic document signed electronically or an SMS.

To this end, the server 100 may receive a phone number together in the process of receiving the account holder information in step S510 .

On the other hand, the phone number may be a phone number of the user terminal 200, which is a target of simple payment registration, or may be a phone number of another terminal.

Here, the server 100 may receive a withdrawal consent by receiving the date of birth or resident registration number of the depositor through the user terminal 200 and confirming the identity of the depositor and the intention to consent to withdrawal.

In addition, the server 100 may record the voice of the depositor who agrees with the withdrawal, record the contents of the voice response system, or store the electronic document, so that it can be used for later verification of whether the withdrawal is consented.

Alternatively, the server 100 may leave a specific message or authentication number while depositing a predetermined amount into the account of the input account information, and may check whether the withdrawal consent is agreed as the corresponding message or authentication number is input from the account holder to which the call is connected. have.

However, in addition, the withdrawal consent confirmation process may be performed according to various methods.

When the account and name authentication (S510) and withdrawal agreement (S520) are successfully performed according to the above-described embodiments, the server 100 receives a password for simple payment through the user terminal 200, and sets the password to simple. It can be set as a password for payment (S530).

As a result, with respect to the user terminal 200, simple payment according to the set password may be registered.

As such, the mobile phone user authentication step is not separately performed, and authentication according to the account holder information and account information is performed collectively according to common encryption, so that regardless of whether the account holder and the user of the user terminal 200 match, the user terminal ( 200) can be registered for easy payment by the depositor.

According to the enactment direction of the Electronic Financial Transactions Act, Enforcement Decree, and Supervisory Regulations, it was amended to “The use of specific technologies or services should not be forced, and efforts should be made to promote fair competition between security and authentication technologies” in electronic financial transactions. Therefore, it is interpreted that the authenticated (mobile phone) identity authentication is not a mandatory process.

That is, like the simple payment registration method of the system 1000 according to the present disclosure, it is possible to replace the identity authentication procedure through a bank account and account password.

Therefore, there is an effect that the account holder using the simple payment of the system 1000 according to the present disclosure can use the simple payment service on the premise of secure authentication of the person and the account even through a user terminal in the name of another person. As a result, through the system 100 according to the present disclosure, it can be expected that a dropout rate due to a simple payment attempt through a user terminal in the name of another person is reduced.

In addition, the dropout rate of the simple payment registration process can be expected to improve in that the mobile phone identity verification step, which required complicated steps, is omitted, and the procedure is relatively simplified, such as verifying the account and the account holder in one step. have.

On the other hand, although the authentication process through the financial institution server 300 is performed, the user terminal 200 in the name of another person other than the account holder can be used. Limitations may be considered.

In one embodiment, when the simple payment of the user terminal 200 is registered, the server 100 sets the number of simple payments that can be performed through the user terminal 200 a preset number of times (ex. 2 times) and/or You can set a limit to a preset amount (ex. 500,000 won per session).

However, if the user authentication (eg, mobile phone identity authentication) of the account holder of the account corresponding to the simple payment is performed with respect to the user terminal 200, the server 100 may release the limit setting for the number of times of easy payment allowed. have.

In relation to this, FIG. 6 is an algorithm for explaining an operation in which the system limits the number of times of performing simple payment after registering for simple payment according to an embodiment of the present disclosure.

6 assumes that simple payment through the user terminal 200 is registered (S610).

Here, when a command for performing the simple payment is received through the user terminal 200 (S620 - Y), the server 100 may proceed with the simple payment through the account that is the target of the simple payment (S640).

However, if the number of times the simple payment is performed through the user terminal 200 after the simple payment registration is greater than the preset number of times (k: 2 times) (S630 - Y), the server 100 It is possible to identify whether or not the account holder's mobile phone identity authentication has been performed (S650).

If the mobile phone user authentication is performed (S650 - Y), simple payment may be performed without limiting the number of times (S640).

On the other hand, if the mobile phone identity authentication is not performed (S650 - N), the server 100 may provide a notification requesting re-registration of simple payment or mobile phone identity authentication through the user terminal 200 (S660) .

Meanwhile, according to an embodiment of the present disclosure, when simple payment is registered, the server 100 may identify at least one user terminal having a history of self-authentication by the account holder of the account corresponding to the simple payment. .

To this end, the server 100 may collect information related to the account holder's identity authentication history by requesting information related to the account holder's identity authentication to at least one telecommunication company server.

And, as an example, the server 100 may identify the user terminal for which the user authentication was most recently performed with respect to the corresponding account holder.

And, the server 100 may transmit information notifying the registration of the simple payment to the identified user terminal (eg, a phone number or an identification number).

If the simple payment of the account holder is registered through a user terminal in the name of another person, as described above, information notifying the registration of the simple payment is transmitted to the user terminal in the name of the account holder, so that safety/security can be enhanced.

Also, if a message or report against the registration of the simple payment is received from the user terminal in the name of the account holder, the server 100 may cancel the registration of the simple payment.

In addition, in one embodiment, the server 100, based on a user command input through a user terminal in the name of the account holder, can purchase (simple payment) from the user terminal 200 in which simple payment is registered (in the name of another person) can also be set.

Here, the item may be set for each product item, or may be set for each seller/seller (eg, a manufacturer, an Internet shopping mall, a store, etc.). For example, simple payment may be allowed only for a specific item (eg, home appliance) of a specific shopping mall according to the setting of the account holder.

Also, the item may be set according to the price of the product. For example, simple payment may be allowed only for purchases of products of a certain amount or less according to the setting of the account holder.

As a specific example, it is assumed that the simple payment using the account of the account holder “Gil-Dong Hong” is registered in the user terminal 200 of “Gil-Seo Hong”, not the account holder. Here, according to the command of “Hong Gil-dong” received through the user terminal of “Hong Gil-dong,” the server 100 selects the items that can be easily paid in the user terminal 200 of “Hong Gil-seo” as book items (books, e-books, e -book, magazine, etc.)

In this case, simple payment through the user terminal 200 is permitted only when purchasing book items, and simple payment may not be permitted for other items.

Meanwhile, according to an embodiment of the present disclosure, when simple payment is registered through a user terminal without mobile phone identity authentication, a limit on the number of times and/or amount of simple payment may be set according to the relationship between the account holder and the user of the user terminal. have.

As an example, in the simple payment registration process, the server 100 may perform user authentication (eg, mobile phone identity authentication) of a user of a user terminal (not the account holder).

If the user of the user terminal has a family relationship with the account holder, the server 100 limits the number of daily simple payments to a preset first number (ex. 5 times), and the user of the user terminal does not have a family relationship with the account holder. In this case, the server 100 may limit the number of daily simple payment to a second preset number (eg, 2 times) less than the preset first number.

Alternatively, the server 100 may set the limit on the number of times and/or the amount of simple payment differently according to the number of villages between the user of the user terminal and the account holder (ex. between spouses: limit of 2 million won per session, between first-degree connections: one hundred per session 10,000 won limit, 2nd degree: 500,000 won per session, etc.).

To this end, the server 100 may identify the family relationship by receiving consent to provide information on the family relationship from the account holder and/or the user of the terminal.

On the other hand, according to an embodiment of the present disclosure, the server 100 sets the number of user terminals (user terminals for which mobile phone user authentication is not performed) in the name of another person in which simple payment can be registered to a preset number (ex. one). of a terminal or two terminals).

As an example, in the state that a simple payment using account 'ABC' of account holder “Hong Gil-dong” is registered (without mobile phone identification) through the terminal of (other) “Hong Gil-seo”, account holder “Hong Gil-dong” is in the same account 'ABC' In the case of an additional attempt to register for simple payment through the terminal of “Gil-Nam Hong”, the server 100 (through the terminal of “Gil-Nam Hong”) the simple payment of the terminal in the name of another person for the same account 'ABC' has already been performed by “Gil-Seo Hong” It can inform that it is registered in the terminal of (: when the number of user terminals in the name of another person to which simple payment can be registered is one).

Here, when the server 100 informs that mobile phone user authentication is required to perform simple payment registration (via the terminal of “Hong Gil-nam”), and/or registers simple payment without mobile phone identity authentication for a specific account , may indicate that registration is possible for only one terminal.

In addition, the server 100 cancels the previously registered simple payment (via the terminal of “Hong Gil-seo”), and performs a simple payment (without mobile phone identification) through the terminal currently being used (: “Hong Gil-nam”’s terminal). You may inquire whether or not to register.

On the other hand, according to an embodiment of the present disclosure, the server 100 determines whether the account holder's simple payment can be registered with respect to the user terminal according to whether the account holder is authenticated (eg, mobile phone identity authentication) through the user terminal. number can be limited.

Specifically, the server 100 may allow registration of simple payment through the user terminal for only a certain number of accounts (eg, one account) for accounts of different account holders than the user of the user terminal.

On the other hand, in the case of accounts of the same account holder as the user of the user terminal, the number of accounts may not be limited or the restriction may be relaxed (eg, two accounts) for simple payment registration.

On the other hand, according to one embodiment, the server 100 is the same account / depositor for other user terminals, depending on whether or not the account holder's identity authentication (ex. mobile phone identity authentication) through the user terminal 200 in which the simple payment is registered. You can also block easy payment registration.

As a specific example, it is assumed that the simple payment through the account of the account holder “A” is registered on the user terminal 200 , and the identity authentication of “A” is also completed through the user terminal 200 .

In this case, the server 100 may cancel the simple payment for the account of “A” registered through another user terminal or block registration of the simple payment for the account of “A” through another user terminal in the future.

Here, the above-described cancellation/blocking may be set as the identity authentication of “A” is performed through the user terminal 200, and “A” received through the user terminal 200 It may be set on the premise of the command/request of “A”.

On the other hand, the server 100 according to an embodiment of the present disclosure may collect information about the account holder and information of the user of the user terminal from at least one external server.

Specifically, when a simple payment in the name of another person is registered (ex. no mobile phone identity authentication), the server 100 receives the account holder and (of the user terminal) from the public institution server, SNS server, search engine server, shopping/advertisement server, etc. Various data related to users can be collected.

The collected data includes the history of exchanging messages, feelings of interest, and interest between the depositor and the user through SNS, the history of the user making a call with the depositor through the user terminal, and monetary transactions between the depositor and the user (ex. transfer) history, etc. may be included.

In addition, the server 100 may provide a question (problem) related to the account holder through the user terminal, and collect the user's response to the provided question as data. Here, the question regarding the account holder is the name, age, birthday, mobile phone number, school graduated from, hobbies, specialties, interests, favorite dramas/movies/books, recently purchased items, frequently used shopping malls, etc. However, the present invention is not limited thereto.

Here, the server 100 may calculate a relationship value between the account holder and the user (of the user terminal) through the collected information.

In this case, the server 100 may input various information sources, IP addresses, time, contents, etc. into at least one artificial intelligence model to calculate a relationship value between the account holder and the user. This artificial intelligence model can be a model trained to calculate relationship figures based on data from various forms and sources, and can be trained in real time based on big data (related to users who have obtained consent).

For example, when the account holder and the user leave an SNS message to each other or a history of conversations with each other is retrieved, the relationship value may be calculated to be relatively high. Specifically, the higher the number of times the message or the indication of liking is exchanged, the more recent the time of exchanging the message or the indication of liking is, the higher the relationship value may be calculated.

Also, for example, the higher the correct rate of the user's response to the question related to the account holder, the higher the relationship value may be calculated.

Alternatively, when the name/date of birth of the user (of the user terminal) used in the web page/application matches the name/date of birth of the account holder, the relational value may be calculated relatively high. In this case, the user may be identified as corresponding to the account holder 'myself', and thus may be calculated to be higher than the relationship value in the case of mutually different people.

If the relationship value is less than the threshold (there is no relationship), the server 100 may cancel or suspend the simple payment registration.

In this case, crimes such as account theft of completely unrelated users can be prevented.

Meanwhile, the various embodiments described above may be implemented by combining two or more embodiments as long as they do not conflict with or contradict each other.

Meanwhile, the various embodiments described above may be implemented in a recording medium readable by a computer or a similar device using software, hardware, or a combination thereof.

According to the hardware implementation, the embodiments described in the present disclosure are ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays) ), processors, controllers, micro-controllers, microprocessors, and other electrical units for performing other functions may be implemented using at least one.

In some cases, the embodiments described herein may be implemented by the processor itself. According to the software implementation, embodiments such as the procedures and functions described in this specification may be implemented as separate software modules. Each of the above-described software modules may perform one or more functions and operations described herein.

Meanwhile, computer instructions or a computer program for performing a processing operation in at least one electronic device in the system 1000 according to various embodiments of the present disclosure described above are non-transitory computer readable media (non-transitory). may be stored in a computer-readable medium). Computer instructions or computer programs stored in such a non-transitory computer-readable medium are such that, when executed by a processor of a specific device, the specific device performs the processing operation in each device in the system 1000 according to various embodiments described above. do.

The non-transitory computer-readable medium refers to a medium that stores data semi-permanently, rather than a medium that stores data for a short moment, such as a register, cache, memory, etc., and can be read by a device. Specific examples of the non-transitory computer-readable medium may include a CD, DVD, hard disk, Blu-ray disk, USB, memory card, ROM, and the like.

In the above, preferred embodiments of the present disclosure have been illustrated and described, but the present disclosure is not limited to the specific embodiments described above, and is commonly used in the technical field pertaining to the present disclosure without departing from the gist of the present disclosure as claimed in the claims. Various modifications may be made by those having the knowledge of

1000: system 100: server
200: user terminal 300: financial institution server

Claims (10)

In the simple payment registration method of a system for registering simple payment in which payment is performed by remitting the amount of a specific account according to the input of a password,
receiving, by the user terminal, account holder information and account information;
encrypting, by the server, authentication information including the account holder information and the account information input through the user terminal;
decrypting, by the financial institution server, the encrypted authentication information;
determining, by the financial institution server, whether authentication succeeds by comparing the decrypted authentication information with information on a previously stored account; and
Based on the success of the authentication, the server, according to the password set through the user terminal, registering a simple payment through the user terminal;
The step of receiving the account holder information and account information includes:
Enter the name of the depositor, the date of birth of the depositor, bank name, account number, and account password;
The simple payment registration method of the system,
Further comprising; confirming whether the depositor agrees to withdrawal by performing at least one of a call, a recording, an electronic signature request for an electronic document, and SMS transmission/reception through the terminal of the input phone number;
The step of registering the simple payment is,
Irrespective of whether the account holder and the user of the user terminal match, based on whether the authentication is successful and whether the withdrawal is agreed to, the simple payment of the account holder is registered through the user terminal,
The financial institution server,
contains information about a plurality of accounts;
Information on each of the plurality of accounts,
including the name of the depositor, the date of birth of the depositor, account number, and account password;
The step of determining whether the authentication is successful,
Encrypting the decrypted authentication information to obtain encrypted information,
Determining whether or not the authentication succeeds according to whether information about at least one account among the plurality of accounts matches the obtained information,
The simple payment registration method of the system,
setting, when the simple payment is registered, limiting the number of times of the simple payment that can be performed through the user terminal to a preset number; and
After the simple payment is registered, when the user authentication of the account holder of the account corresponding to the simple payment is performed with respect to the user terminal, releasing the limit setting for the number of times of the simple payment allowed;
The simple payment registration method of the system,
identifying, by the server, at least one user terminal having a history of self-authentication by the account holder of an account corresponding to the simple payment when the simple payment is registered; and
Transmitting, by the server, information notifying the registration of the simple payment to the identified user terminal; further comprising, a simple payment registration method of the system. delete delete According to claim 1,
The step of encrypting the authentication information,
Encrypt authentication information including the name of the depositor, the date of birth of the depositor, account number, and account password;
Decrypting the authentication information comprises:
The easy payment registration method of the system, wherein the financial institution server matching the bank name decrypts the encrypted authentication information. delete According to claim 1,
The simple payment registration method of the system,
performing verification according to a security card password or OTP (One Time Password) based on the input account holder information and account information; or
Based on the input account holder information and account information, the step of performing verification according to a certificate that can confirm the identity; further comprising,
The step of registering the simple payment is,
A simple payment registration method of a system for registering simple payment through the user terminal based on whether the verification succeeds and whether the determined authentication succeeds. delete delete In the system for registering a simple payment that performs payment by remitting the amount of a specific account according to the input of a password,
a user terminal for receiving account holder information and account information;
a server for encrypting authentication information including the account holder information and the account information input through the user terminal; and
A financial institution server that decrypts the encrypted authentication information and determines whether authentication succeeds by comparing the decrypted authentication information with information on a previously stored account;
The server is
Based on the determined success of the authentication, according to the password set through the user terminal to register the simple payment through the user terminal,
The account holder information is
including the name of the depositor and the date of birth of the depositor;
The account information is
including bank name, account number, and account password;
The server is
Through the terminal of the entered phone number, at least one of a call, a recording, an electronic signature request for an electronic document, and SMS transmission/reception is performed to confirm whether the depositor agrees to withdraw,
Irrespective of whether the account holder and the user of the user terminal match, based on whether the authentication is successful and whether the withdrawal is agreed to, the simple payment of the account holder is registered through the user terminal,
The financial institution server,
contains information about a plurality of accounts;
Information on each of the plurality of accounts,
including the name of the depositor, the date of birth of the depositor, account number, and account password;
The financial institution server,
Encrypting the decrypted authentication information to obtain encrypted information,
Determining whether or not the authentication succeeds according to whether information about at least one account among the plurality of accounts matches the obtained information,
The server is
When the simple payment is registered, the number of times of the simple payment that can be performed through the user terminal is set to be limited to a preset number,
After the simple payment is registered, when the user authentication of the account holder of the account corresponding to the simple payment is performed with respect to the user terminal, the limit setting for the number of times of the simple payment allowed is released,
The server is
When the simple payment is registered, the account holder of the account corresponding to the simple payment identifies at least one user terminal having a history of performing identity authentication,
A system for transmitting information informing the registration of the simple payment to the identified user terminal. delete

Images