KR102607325B1 - Method of simple payment using customer information of mobile communication company, user terminal and mobile communication company server performing method, and simple payment system including same - Google Patents

Abstract

According to an embodiment of the present invention, a method of providing simple payment to a user performed by a user terminal includes, when accessing a predetermined page provided by a product sales server, the user terminal makes the simple payment to a mobile carrier server. sending a line authentication request to verify availability; If the user terminal can use the simple payment, receiving a line authentication response including line identification information of the user terminal from the mobile communication company server in response to the line authentication request; And when a predetermined payment is made using the simple payment, it may include providing the simple payment to the user using the line identification information.

Description

A simple payment method using customer information of a mobile carrier, a user terminal and a mobile carrier server that perform the method, and a simple payment system including these {METHOD OF SIMPLE PAYMENT USING CUSTOMER INFORMATION OF MOBILE COMMUNICATION COMPANY, USER TERMINAL AND MOBILE COMMUNICATION COMPANY SERVER PERFORMING METHOD, AND SIMPLE PAYMENT SYSTEM INCLUDING SAME}

The present invention relates to a simple payment method using customer information of a mobile carrier, a user terminal and a mobile carrier server that perform the method, and a simple payment system including these.

In the case of online shopping malls, transaction volume has been increasing every year recently due to the spread of simple payment methods and the untact trend. Recently, online shopping malls are linked to social media platforms or personal broadcasting platforms, allowing customers to immediately purchase products from the online shopping mall that they saw on social media or personal broadcasting.

However, small and medium-sized online shopping malls are not fully utilizing the linkage with other platforms. This is because in the case of small and medium-sized online shopping malls, consumers search for products on large portal sites, and use links generated from large portal sites or large portal sites. This is because product purchases occur through the address of the online shopping mall searched on the site.

In other words, when entering an external link (online shopping mall) from a portal site, consumers must register as a member at the relevant online shopping mall to purchase products. Customers who do not trust membership or find it inconvenient can purchase products at the online shopping mall. Chances are you won't buy it.

Additionally, even if a customer signs up for membership, if the online shopping mall's payment interface is not convenient for the user, there is a possibility that the customer will not purchase the product due to the payment interface.

Meanwhile, in order to reduce the possibility of purchase interruption as mentioned above, small and medium-sized online shopping malls can use the simple payment function provided by large portal sites. However, the simple payment function provided by large portal sites has a high usage fee, which is burdensome for small and medium-sized online shopping malls. This can be.

Therefore, online shopping malls need a convenient payment interface that does not require customers to register as members without worrying about fees.

The problem to be solved by the present invention is to provide a method of providing simple payment to the purchaser by using the purchaser's customer information managed by the mobile communication company in order to solve the above-mentioned problem.

However, the problems to be solved by the present invention are not limited to those mentioned above, and other problems to be solved that are not mentioned can be clearly understood by those skilled in the art to which the present invention pertains from the description below. will be.

According to an embodiment of the present invention, a method of providing simple payment to a user performed by a user terminal includes, when accessing a predetermined page provided by a product sales server, the user terminal makes the simple payment to a mobile carrier server. sending a line authentication request to verify availability; If the user terminal can use the simple payment, receiving a line authentication response including line identification information of the user terminal from the mobile communication company server in response to the line authentication request; And when a predetermined payment is made using the simple payment, it may include providing the simple payment to the user using the line identification information.

The line identification information may be included in the line authentication response as a result of the mobile carrier server performing a header enrichment authentication procedure for the line authentication request.

The line identification information may be obtained from the mobile carrier server as the mobile carrier server adds the IP address of the user terminal to the header of the line authentication request.

The step of providing the simple payment to the user includes, when making a predetermined payment using the simple payment, identity verification to confirm that the user is a legitimate user of the user terminal using the line identification information. Steps to perform; And when the user is confirmed to be a legitimate user of the user terminal according to the identity verification authentication, it may include providing the simple payment.

The step of performing the identity verification authentication may include, when the user has pre-set a password used for the identity verification authentication, providing the user with an interface that allows the user to input the pre-set password; And when the password is not previously set, it may include providing the user with an interface that allows the user to input information verifying that the user is a legitimate user of the user terminal.

A method in which a mobile communication company server provides simple payment to a user of a user terminal according to another embodiment of the present invention includes, when the user accesses a predetermined page provided by a product sales server using the user terminal, the user Receiving, from a terminal, a line authentication request to authenticate whether the user terminal can use the simple payment; Based on the line authentication request, determining whether the user terminal is a terminal capable of using the simple payment provided by the mobile communication company server; As a result of the determination, if the user terminal can use the simple payment, transmitting a line authentication response including line identification information used to provide the simple payment to the user terminal; And when there is a simple payment request from the user terminal, it may include providing the simple payment to the user terminal using the line identification information.

The determining step includes performing a header enrichment authentication procedure on the line authentication request; And according to the results of the header enhanced authentication procedure, it may include determining whether the user terminal is a terminal that can use the simple payment provided by the mobile communication service provider server.

The determining step may include obtaining identification information of the user terminal assigned to the IP address using the IP address of the user terminal added to the header of the line authentication request; And it may include using the identification information to determine whether the user terminal is a terminal that can use the simple payment provided by the mobile communication company server.

When there is a simple payment request from the user terminal, the step of providing the simple payment to the user terminal using the line identification information includes: When there is a simple payment request, whether the user is a legitimate user of the user terminal A step of performing identity verification to verify whether the identity is verified; And when it is confirmed that the user is a legitimate user of the user terminal according to the identity verification authentication, it may include providing the simple payment.

The step of performing the identity verification authentication includes, when the password used for the identity verification authentication is preset, providing an interface to allow the user terminal to input the preset password; And when the password is not previously set, it may include providing an interface that allows the user to input information confirming that he or she is a legitimate user of the user terminal.

A user terminal that provides simple payment to users according to another embodiment of the present invention includes a transceiver that transmits and receives data with a product sales server and a mobile carrier server; and a processor that controls the transceiver, wherein the processor controls the transceiver to enable the user terminal to make the simple payment to the mobile carrier server when accessing a predetermined page provided by the product sales server. A line authentication request is transmitted to verify whether the service can be used, and the transceiver is controlled. When the user terminal can use the simple payment, in response to the line authentication request, from the mobile carrier server, When a line authentication response containing line identification information of the user terminal is received and a predetermined payment is made using the simple payment, the simple payment can be provided to the user using the line identification information.

A mobile carrier server that provides simple payment to users of user terminals according to another embodiment of the present invention includes a transceiver that transmits and receives data to and from the user terminal and a product sales server; and a processor that controls the transceiver, wherein the processor controls the transceiver to, when the user accesses a predetermined page provided by the product sales server using the user terminal, from the user terminal, Receiving a line authentication request for authenticating whether the user terminal can use the simple payment, and based on the line authentication request, whether the user terminal is a terminal that can use the simple payment provided by the mobile carrier server determines and controls the transceiver, and as a result of the determination, if the user terminal can use the simple payment, send a line authentication response containing line identification information used to provide the simple payment to the user terminal. When transmitting and there is a simple payment request from the user terminal, the simple payment can be provided to the user terminal using the line identification information.

A computer-readable recording medium storing a computer program according to another embodiment of the present invention allows the user terminal to use the simple payment to a mobile carrier server when accessing a predetermined page provided by a product sales server. transmitting a line authentication request to authenticate whether or not there is a line authentication request; If the user terminal can use the simple payment, receiving a line authentication response including line identification information of the user terminal from the mobile communication company server in response to the line authentication request; And when a predetermined payment is made using the simple payment, providing the simple payment to the user using the line identification information, providing the simple payment to the user performed by the user terminal. It may include instructions for causing the processor to perform the method.

A computer-readable recording medium storing a computer program according to another embodiment of the present invention provides, when the user accesses a predetermined page provided by a product sales server using the user terminal, from the user terminal, Receiving a line authentication request to authenticate whether the user terminal can use the simple payment; Based on the line authentication request, determining whether the user terminal is a terminal capable of using the simple payment provided by the mobile communication company server; As a result of the determination, if the user terminal can use the simple payment, transmitting a line authentication response including line identification information used to provide the simple payment to the user terminal; And when there is a simple payment request from the user terminal, providing the simple payment to the user terminal using the line identification information, and providing the simple payment to the user of the user terminal performed by the mobile communication company server. It may include instructions for causing the processor to perform the provided method.

According to an embodiment of the present invention, the shopping mall server can provide a simple payment service to the buyer by using the buyer's customer information managed by the mobile communication company server, thereby providing the buyer with a simple payment service without the need for membership registration.

In addition, according to an embodiment of the present invention, the shopping mall server can provide a safer and more convenient payment function to the buyer by making a simple payment using the identity verification function provided by the mobile communication company server.

Additionally, according to an embodiment of the present invention, the shopping mall server can provide simple payments to buyers with lower or no fees compared to simple payments provided by large portal sites.

1 is a block diagram showing a simple payment system according to an embodiment of the present invention.
Figure 2 is a flowchart showing a simple payment method that performs line authentication when accessing a predetermined page according to an embodiment of the present invention.
Figure 3 is a flowchart showing a simple payment method that performs line authentication during the payment process according to another embodiment of the present invention.
Figure 4 is a flowchart showing a simple payment method of a simple payment system when a payment agency server does not exist according to another embodiment of the present invention.
Figure 5 is a flowchart showing a method of performing line authentication for a user terminal in a user authentication server when the user terminal connects to a shopping mall server using a cellular network according to an embodiment of the present invention.
Figure 6 shows an example of a simple payment button determined depending on whether the user terminal has line authentication.
Figure 7 shows an example of a screen displayed on the user terminal when the user sets a password for identity verification.
Figure 8 shows an example of a screen displayed on a user terminal when the user does not set a password for identity verification.
Figure 9 shows an example of a simple payment performed on a user terminal when the line of the user terminal is authenticated according to an embodiment of the present invention.
Figure 10 shows an example of simple payment performed on a user terminal when the line of the user terminal is not authenticated according to another embodiment of the present invention.
Figure 11 is a block diagram showing the configuration of devices according to an embodiment of the present invention.

The advantages and features of the present invention and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms. The present embodiments are merely provided to ensure that the disclosure of the present invention is complete and to provide common knowledge in the technical field to which the present invention pertains. It is provided to fully inform those who have the scope of the invention, and the present invention is only defined by the scope of the claims.

In describing embodiments of the present invention, if it is determined that a detailed description of a known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description will be omitted. The terms described below are terms defined in consideration of functions in embodiments of the present invention, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

1 is a block diagram showing a simple payment system according to an embodiment of the present invention.

Referring to FIG. 1 , the simple payment system 10 may include a user terminal 100, a shopping mall server 200, a user authentication server 300, and a payment server 400.

The user terminal 100 can purchase products or use services at the online shopping mall by viewing products or services at the online shopping mall and paying for the product purchase or service use using a simple payment provided by the mobile communication company.

In this specification, 'simple payment' refers to a separate membership registration for a shopping mall by verifying identity and making payment through a mobile carrier that is used by the user of the user terminal 100 or can be authenticated by the user of the user terminal 100. This may refer to a payment method that allows the user terminal 100 to make payments for purchasing products or using services at a shopping mall without this need.

The user terminal 100 may be a device such as a smartphone, tablet, laptop computer, or PC that communicates using a mobile network such as a cellular network or Wi-Fi, or communicates through a wired network.

The user terminal 100 accesses a predetermined page (e.g., a page for determining a purchase intention for a product, such as a product purchase details page) or thereafter (e.g., when simple payment is selected as the payment method for the product). ), the mobile carrier's line in which the user terminal 100 manages the user authentication server 300 through header enrichment or a direct user authentication method (e.g., a method in which the user enters personal information and authentication information) You can verify that you are.

In addition, when the user terminal 100 wants to pay for the purchase of a product, according to the identity verification authentication request received from the user authentication server 300, the user using the user terminal 100 is the legitimate party of the user terminal 100. You can authenticate your identity as a user.

The shopping mall server 200 can sell products online to customers (users of the user terminal 100) and provide a simple payment service to the user terminal 100 using customer information managed by the mobile communication company.

More specifically, when the user terminal 100 accesses a predetermined page, the shopping mall server 200 may provide the user terminal 200 with a simple payment button to check whether the simple payment service is used. Thereafter, when the user terminal 100 decides to use simple payment, the shopping mall server 200 uses the user authentication server 300 to send the payment server 400 to the user terminal 100 for which line authentication and user authentication have been completed. ) can provide a simple payment service.

Depending on the embodiment, the shopping mall server 200 authenticates the line according to whether the user terminal 100 is a user terminal whose line has been identified by the user authentication server 300 (e.g., through header enrichment authentication). (depending on whether the terminal is a certified terminal), different types of simple payment buttons can be provided. This means that, in the case of the user terminal 100 whose line has been identified through header enhanced authentication by the user authentication server 300, the shopping mall server 200 can proceed with payment for the product using customer information managed by the corresponding mobile carrier. This is because, when entering the simple payment button, it is necessary to notify the user terminal 100 that payment will be made through the corresponding line.

Or, according to another embodiment, depending on the selection of the shopping mall server 200, the shopping mall server 200, regardless of whether the user terminal 100 has been identified by the user authentication server 300, The same simple payment button can also be provided to (100).

For example, referring to FIG. 6, (a) of FIG. 6 shows a case where the user terminal 100 accesses a predetermined page of a shopping mall using a cellular network and the line is identified by the user authentication server 300 (i.e. , when the line information of the user terminal 100 is obtained through header enhancement), it is an example of a method in which the shopping mall server 200 displays at least part of the phone number of the user terminal 100 and provides a simple payment button. , (b) of FIG. 5 shows an example of a method in which the shopping mall server 200 provides a simple payment button without displaying the phone number of the user terminal 100.

As shown in (a) of FIG. 6, when the user terminal 100 accesses the predetermined page using a cellular network and the line of the user terminal 100 is identified, the user terminal 100 enters its phone number. In order to recognize that payment is in progress, the shopping mall server 200 includes “010-1***-*234”, which is at least part of the phone number of the user terminal 100, in the first simple payment button (BTN_1). It can be provided to the user terminal 100.

On the other hand, as shown in (b) of FIG. 6, when the user terminal 100 accesses a predetermined page, line authentication for the user terminal 100 is not performed, or the user terminal 100 cannot access the predetermined page. Even if line authentication is performed for the user terminal 100, if the shopping mall server 200 decides not to provide the phone number of the user terminal 100, the shopping mall server 200 includes the phone number of the user terminal 100. A second simple payment button (BTN_2) that is not used may be provided to the user terminal 100.

Here, the user terminal 100 connects to the shopping mall server 200 using WiFi or a wired network, or the user terminal 100 uses a mobile carrier other than the mobile carrier that manages the user authentication server 300. In this case, line authentication for the user terminal 100 may not be performed.

At this time, if the user terminal 100 is connected to the shopping mall server 200 using WiFi or a wired network, as will be described later using FIG. 10, the user terminal 100 can conveniently use a direct user authentication method. Payment service is available.

In addition, when the user terminal 100 is a terminal using another mobile communication service provider, the user terminal 100 transfers the IP address of the user terminal 100 to the other mobile communication service provider by the user authentication server 300. You can use the simple payment service through your telecommunication company or by entering your mobile phone payment information through a payment agency server.

The simple payment method provided by the shopping mall server 200 may vary depending on whether the user terminal 100 is a terminal whose line has been identified by the user authentication server 300. This is because, if the line of the user terminal 200 is not identified, an additional process must be performed to determine the mobile carrier used by the user terminal 100 and whether the user terminal 100 is a terminal capable of making mobile phone payments. Simple payment procedures that differ depending on whether the line is identified will be explained in more detail with reference to FIGS. 9 and 10.

Meanwhile, in this specification, a simple payment button includes not only a simple payment selection interface implemented in at least a portion of the predetermined page, but also an interface implemented in a separate page derived from the predetermined page, such as a pop-up window. It can include not only an interface that allows you to select the 'simple payment service' itself, which is distinct from other payment methods, but also an interface that allows you to select 'yes' or 'no' to use the simple payment service.

In addition, in this specification, for convenience of explanation, the object that the user terminal 100 connects to and purchases products is referred to as the shopping mall server 200, but the simple payment method according to the embodiment of the present specification is not limited to the shopping mall. . That is, depending on the embodiment, the shopping mall server 200 is not only applicable to shopping malls that sell not only tangible products but also intangible products (e.g., music, videos, online books, etc.), as well as to users of the user terminal 100. This may also apply to servers that provide services rather than products and receive a service fee. Therefore, if service provision is considered to be included in an intangible product in a broad sense, the shopping mall server 200 may mean a product sales server or a product provision server.

The user authentication server 300 may perform line authentication of the user terminal 100 according to a request from the user terminal 100 and transmit the result to the user terminal 100.

More specifically, the user authentication server 300 determines whether the user terminal 100 that accesses a predetermined page or selects simple payment as the payment method is a line that can use the simple payment service. When receiving an inquiring line authentication request, a header strengthening authentication procedure is performed on the IP address of the user terminal 100, and as a response to the line authentication request, a line through which the user terminal 100 can use the simple payment service In this case, a line authentication response containing line identification information of the user terminal 100 may be transmitted. In addition, the user authentication server 300 allows a user who wishes to pay for the purchase of a product (service) using simple payment. For the terminal 100, user authentication may be performed by the mobile telecommunication company.

More specifically, when the user terminal 100 purchases a product or uses a service using simple payment, the user authentication server 300 provides user authentication from the shopping mall server 200 to the mobile carrier for the user terminal 100. You can receive a user authentication request requesting .

Accordingly, the user authentication server 300 transmits an identity verification request to the user terminal 100, and upon receiving an identity verification response including a password from the user terminal 100, based on this, the shopping mall server 200 A user authentication response may be transmitted to verify that the user of the user terminal 100 is a legitimate user of a line capable of simple payment.

As the user terminal 100 purchases a product or uses a service at the shopping mall server 200, when a simple payment is made on the shopping mall server 200 for the user terminal 100 to purchase a product or use a service, the payment server (400) allows for simple payment.

Depending on the embodiment, when the payment agency server performs simple payment on your behalf, the payment server 400 may transmit a payment response instructing to proceed with payment in response to the payment request from the payment agency server, and the payment agent server If the payment server 400 does not provide simple payment on your behalf, the payment server 400 may receive a payment request from the shopping mall server 200 and proceed with the payment based on the risk management of the payment server 400 itself.

In this specification, for convenience of explanation, the user authentication server 300 and the payment server 400 are described as separate servers, but they are not limited to this. That is, depending on the embodiment, the user authentication server 300 and the payment server 400 may be implemented as a user authentication function and payment function within one server managed by a mobile communication company.

Figure 2 is a flowchart showing a simple payment method that performs line authentication when accessing a predetermined page according to an embodiment of the present invention.

Referring to Figures 1 and 2, when the user terminal 100 accesses the product page (or purchase history confirmation page, etc.) to purchase a product (or use a service) at the shopping mall server 200 (S200) , the shopping mall server 200 may transmit product page information to the user terminal 100 (S202). The product page information may include a script requesting the user terminal 100 to perform a line authentication request.

Therefore, upon receiving the product page information, the user terminal 100 sends a line authentication request to the user authentication server 300 to authenticate that the line (phone number) of the user terminal 100 is a line that can use simple payment. It can be transmitted to (S204).

The user authentication server 300, which has received the line authentication request, may perform user authentication to verify whether the user terminal 100 that sent the line authentication request is a user terminal using the mobile carrier that manages the user authentication server 300. (S206). Depending on the embodiment, the user authentication server 300 may perform user authentication for the user terminal 100 using header enrichment, and the user authentication method using header enrichment is described in more detail in FIG. 5. Let me explain.

Through the user authentication process, the identification number (e.g., phone number) of the user terminal 100 corresponds to the identification number provided by the mobile communication company, and the user terminal 100 is a user terminal that can use simple payment. If confirmed, the user authentication server 300 sends a line authentication response to the user terminal 100 as a response to the line authentication request of the user terminal 100, authenticating that the user terminal 100 is a line capable of using simple payment. It can be transmitted to (S208).

Depending on the embodiment, the line authentication response may include line identification information corresponding to the identification number of the user terminal 100. The line identification information can be used to display at least part of the phone number of the user terminal 100 in the simple payment button displayed on the product page, and then, when purchasing a product (or using a service) of the user terminal 100. It can be used for user authentication and/or simple payment.

Accordingly, when the line authentication of the user terminal 100 is completed, the user terminal 100 selects at least some of the phone numbers of the user terminal 100 obtained in response to the line authentication through a method such as displaying a simple payment button. can be displayed on the product page.

Afterwards, when the user terminal 100 purchases a product (or uses a service) and selects simple payment as the payment method for purchasing a product (or using a service) (i.e., the user terminal 100 enters the simple payment button) In one case) (S210), the shopping mall server 200 sends a user authentication request to the user authentication server 300 requesting to proceed with identity verification to verify whether the user of the user terminal 100 is a legitimate user who can use simple payment. ) can be transmitted to (S212).

The user authentication request may include line identification information for identifying the user terminal 100, payment information (eg, payment amount), and product information.

The user authentication server 300, which has received the user authentication request, in response to the user authentication request, checks whether the user terminal 100 is occupied by a legitimate user of the user terminal 100 along with the personal information of the user terminal 100. An identity verification request including an identity verification question may be transmitted to the user terminal 100 (S214).

Depending on the embodiment, the identity verification request may include payment information for a product (or service) (e.g., transaction identification information for a product (or service used) purchased by the user terminal 100), delivery information (e.g., user terminal 100 (buyer information and/or delivery address information corresponding to the delivery information of 100), identity verification information to confirm whether the user occupies the user terminal 100, and at least one of the contact information and address of the user of the user terminal 100 It may further include.

In response to the identity verification request, the user terminal 100 may transmit an identity verification response corresponding to the answer to the identity verification question to the user authentication server 300 (S216).

For example, further referring to FIGS. 7 and 8, FIG. 7 is an example of an identity verification request transmitted to the user terminal 100, when the legitimate user of the user terminal 100 sets a password for identity verification. An example of a screen displayed on the user terminal is shown, and Figure 8 is another example of an identity verification request transmitted to the user terminal 100, when the legitimate user of the user terminal 100 has not set a password for identity verification. shows an example of a screen displayed on a user terminal.

That is, when the legitimate user of the user terminal 100 has previously set a password for the identity verification question, as shown in FIG. 7, the user terminal 100 sets the password according to the identity verification question received from the user authentication server 300. An interface that allows input can be displayed.

On the other hand, if the legitimate user of the user terminal 100 does not set a password for the identity verification question, the user terminal 100 receives the identity verification request from the user authentication server 300 before receiving the identity verification request. You may receive confirmation questions.

At this time, as shown in FIG. 8, the user terminal 100 displays an interface that allows the user to input an answer to the identity verification question for setting a password, and the user of the user terminal 100 enters the correct answer to the identity verification question. In this case, the user terminal 100 may display an interface for (re)setting the password for the identity verification question. Unlike FIG. 8, the identity verification question for setting the password may include not only the automatic payment bank, but also any one of the automatic payment card (card company), date of birth, and SMS authentication.

When the user of the user terminal 100 (re)sets the password, the user terminal 100 displays the interface shown in FIG. 7 to allow the user to enter the password according to the identity verification question.

When it is confirmed that the user of the user terminal 100 is a legitimate user through the identity verification response received from the user terminal 100, the user authentication server 300 responds to the user authentication request from the shopping mall server 200. , a user authentication response indicating that identity verification for the user terminal 100 has been completed may be transmitted to the shopping mall server 200 (S218).

The user authentication response includes duplication information (DI) corresponding to the identification number for the payment service for product purchase (or service use), the phone number of the user terminal 100, transaction identification information, and line identification information. can do.

When receiving a user authentication response from the user authentication server 300, the shopping mall server 200 may request payment for product purchase (or service use) of the user terminal 100 (S220).

At this time, depending on the embodiment, if there is a payment agency server 500 that performs payment, the shopping mall server 200 may transmit a payment request to the payment agency server 500), and the payment request may include replication information, It may include the phone number of the user terminal 100, payment amount, product information, transaction identification information, and line identification information.

The payment agency server 500 can apply its own risk management (S222) and proceed with the payment. Depending on the progress of the payment, the payment agency server 500 may transmit a payment request to the payment server 400 ( S224), the payment server 400 that has received the payment request may transmit a payment response to the payment agency server 500 in response (S226).

Here, the payment request transmitted from the payment agent server 500 to the payment server 400 may include line identification information, transaction identification information, payment amount, and product information, and the payment server 400 may send the payment agent server 500 ) The payment response sent to is connection information ( Connecting Information (CI) may be included.

The payment agency server 500, which has received a payment response from the payment server 400, transmits a payment response indicating that the payment request has proceeded normally in response to the payment request to the shopping mall server 200 (S228), and the shopping mall server (200) 200) may transmit product purchase completion (service availability) to the user terminal 100 (S230).

At this time, the payment response sent by the payment server 400 to the payment agency server 500 and the payment response transmitted by the payment agency server 500 to the shopping mall server 200 are the user of the user terminal 100 (i.e., the purchaser). ) may include at least one of name, delivery address, contact information, and order number, and the information included in the payment response may be used by the shopping mall server 200 to manage payment history and proceed with product delivery.

Figure 3 is a flowchart showing a simple payment method that performs line authentication during the payment process according to another embodiment of the present invention.

Referring to Figures 1 and 3, when the user terminal 100 accesses the product page (or purchase history confirmation page, etc.) to purchase a product (or use a service) on the shopping mall server 200 (S300) , the shopping mall server 200 may transmit product page information to the user terminal 100 (S302).

When the user terminal 100 purchases a product (or uses a service) on the relevant product page or a product page accessed thereafter (S304) and selects simple payment as the payment method for purchasing the product (or using the service), The shopping mall server 200 may transmit a payment progress request to the user authentication server 300. Here, the payment progress request may be a message simply requesting payment (i.e., requesting transmission of a payment window), or it may be a message requesting line authentication and identity verification along with payment progress.

Upon receiving a payment proceeding request, the user authentication server 300 may transmit a payment window to the user terminal 100 (S308).

Upon receiving the payment window, the user terminal 100 may transmit a line authentication request to the user authentication server 300 to authenticate that the line (phone number) of the user terminal 100 is a line that can use simple payment. There is (S310).

When receiving a line authentication request from the user terminal 100, the user authentication server 300 determines whether the user terminal 100 that transmitted the line authentication request is a user terminal using the mobile carrier that manages the user authentication server 300. Line authentication to authenticate can be performed (S312). Depending on the embodiment, the user authentication server 300 may perform user authentication for the user terminal 100 using header enhancement.

Through the user authentication process, the identification number (e.g., phone number) of the user terminal 100 corresponds to the identification number provided by the mobile communication company, and the user terminal 100 is a user terminal that can use simple payment. If confirmed, the user authentication server 300 sends a line authentication response to the user terminal 100 as a response to the line authentication request of the user terminal 100, authenticating that the user terminal 100 is a line that can use simple payment. It can be transmitted to (S314).

When line authentication is completed, the user authentication server 300 checks whether a legitimate user of the user terminal 100 occupies the user terminal 100 (i.e., whether the user of the user terminal 100 is a legitimate user). To do so, an identity verification request including an identity verification question may be transmitted to the user terminal 100 (S316).

In this specification, the identity verification request is distinct from the line authentication response, and the user authentication server 300 transmits the identity verification request after transmitting the line authentication response. However, the identity verification request is not limited to this. That is, depending on the embodiment, the user authentication server may transmit an identity verification request along with a line authentication response.

Depending on the embodiment, the identity verification request may include payment information for a product (or service) (e.g., transaction identification information for a product (or service used) purchased by the user terminal 100), delivery information (e.g., user terminal 100 (buyer information and/or delivery address information corresponding to the delivery information of 100), identity verification information to confirm whether the user occupies the user terminal 100, and at least one of the contact information and address of the user of the user terminal 100 It may further include.

In response to the identity verification request, the user terminal 100 may transmit an identity verification response corresponding to the answer to the identity verification question to the user authentication server 300 (S318).

When it is confirmed that the user of the user terminal 100 is a legitimate user through the identity verification response received from the user terminal 100, the user authentication server 300 provides an identity indicating that identity verification for the user terminal 100 has been completed. The verification result may be transmitted to the user terminal 100 (S320), and a payment progress response indicating that line authentication and identity verification have been completed may be transmitted to the shopping mall server 200 (S322).

When a payment progress response is received from the user authentication server 300, the shopping mall server 200 may request payment for product purchase (or service use) of the user terminal 100.

At this time, depending on the embodiment, if there is a payment agency server 500 that acts as an agent for payment, the shopping mall server 200 may transmit a payment request to the payment agency server 500 (S324), and the payment request is duplicated. It may include information, phone number of the user terminal 100, payment amount, product information, transaction identification information, and line identification information.

The payment agency server 500 can apply its own risk management (S326) and proceed with the payment. As the payment progresses, the payment agency server 500 transmits a payment request to the payment server 400 (S328). ), the payment server 400, which has received the payment request, may transmit a payment response indicating that it will proceed with the payment requested by the shopping mall server 200 to the payment agency server 500 in response (S330).

Here, the payment request transmitted from the payment agent server 500 to the payment server 400 may include line identification information, transaction identification information, payment amount, and product information, and the payment server 400 may send the payment agent server 500 ) The payment response sent to is connection information ( Connecting Information (CI) may be included.

The payment agency server 500, which has received a payment response from the payment server 400, transmits a payment response indicating that the payment request has proceeded normally in response to the payment request to the shopping mall server 200 (S332), and the shopping mall server ( 200) may transmit a product purchase completion (service available) indicating that the product purchase has been completed upon completion of payment to the user terminal 100 (S334).

At this time, the payment response sent by the payment server 400 to the payment agency server 500 and the payment response transmitted by the payment agency server 500 to the shopping mall server 200 are the user of the user terminal 100 (i.e., the purchaser). ) may include at least one of name, delivery address, contact information, and order number, and the information included in the payment response may be used by the shopping mall server 200 to manage payment history and proceed with product delivery.

That is, unlike the embodiment of FIG. 2 in which line authentication is performed when the user terminal 100 accesses the product page, in the embodiment of FIG. 3, the user terminal 100 uses simple payment to purchase the product after accessing the product page. Line authentication may be performed when a decision is made to pay the fee (or service fee). Through this, it can be differentiated from the embodiment of FIG. 2 in that line authentication is not performed on user terminals that do not use simple payment (that is, line authentication is performed only on user terminals that select simple payment as the payment method). .

Figure 4 is a flowchart showing a simple payment method of a simple payment system when a payment agency server does not exist according to another embodiment of the present invention.

Referring to FIGS. 1 to 4 , the user authentication response step (S400) of FIG. 4 may be substantially the same as the user authentication response step (S218) of FIG. 2 and the payment progress response step (S322) of FIG. 3.

Accordingly, in the description of FIG. 4, the description of steps performed before the user authentication response step (S400) will be applied mutatis mutandis to FIG. 2 or FIG. 3.

When receiving a user authentication response from the user authentication server 300, the shopping mall server 200 may transmit a payment request to the payment server 400 (S402).

Since there is no payment server that handles payment, the payment request may only include payment amount, product information, transaction identification information, and line identification information.

The payment server 400 can apply its own risk management (S404) to proceed with the payment, and as the payment progresses, the payment server 400 sends a payment response including connection information in response to the payment request to the shopping mall. It can be transmitted to the server 200 (S406).

The shopping mall server 200, which has received a payment response from the payment server 400, may transmit product purchase completion (service available) to the user terminal 100 (S408).

Figure 5 is a flowchart showing a method of performing user authentication for a user terminal in a user authentication server when the user terminal connects to a shopping mall server using a cellular network according to an embodiment of the present invention.

Referring to FIGS. 1, 2, 3, and 5, the line authentication request step (S500) and the line authentication request response step (S512) of FIG. 5 are the same as the line authentication request step (S204) of FIG. 2 and the line authentication request response step (S512). It may be substantially the same as (S208) and the line authentication request step (S310) and line authentication request response (S314) of FIG. 3.

Accordingly, the remaining steps (S502 to S510) of FIG. 5 may correspond to specification of the line authentication step (S206) of FIG. 2 or the line authentication step (S312) of FIG. 3.

More specifically, when receiving a line authentication request (e.g., Http call) from the user terminal 100, the user authentication server 300 or a separate mobile carrier server (e.g., X-forward server) sends the header of the line authentication request. The IP address of the user terminal 100 may be added (S502), and a line authentication request with the IP address added to the header may be transmitted to the payment server 400 (S504). Depending on the embodiment, the IP address of the user terminal 100 may be included in the line authentication request generated by the user terminal 100 and transmitted to the user authentication server 300 or a separate mobile carrier server.

The payment server 400 extracts the IP address of the user terminal 100 from the header of the line authentication request. When the user terminal 100 connects to the shopping mall server 200 using a cellular network, the IP address is used for payment. Since it corresponds to the IP address of the mobile communication company that manages the server 400, the payment server 400 can obtain the subscriber identification number (eg, MSISDN) assigned to the IP address (S506).

To this end, the payment server 400 queries the network equipment (e.g., NAG) for subscriber identification information to which the extracted IP address is assigned, and receives the subscriber identification information to which the extracted IP address is assigned as a result of the query, thereby providing a subscriber identification number. can be obtained.

The payment server 400 transmits the acquired subscriber identification number to the user authentication server 300 (S508), and the user authentication server 300 uses the subscriber identification number to connect the user terminal 100 to the user authentication server 300. ), it can be confirmed that the mobile communication service is provided from the mobile communication company that manages (S510), and it can be confirmed that the user terminal 100 is a terminal that can use the mobile phone payment service.

Therefore, based on this, the user authentication server 300 may transmit a line authentication response to the shopping mall server 200 to authenticate that the user terminal 100 is provided with a mobile communication service from the corresponding mobile communication company (S512).

Figure 9 shows an example in which simple payment is performed when the line of the user terminal is authenticated according to an embodiment of the present invention.

1 to 9, when the user terminal 100 succeeds in line authentication by accessing the product page of the shopping mall server 200 through a cellular network, the user authentication server 300 connects the line of the user terminal 100. Identification information can be obtained, and the user terminal 100 can create a simple payment button using the line identification information included in the reply authentication response received from the user authentication server 300. Accordingly, the user terminal 100 displays the first screen 101 including a simple payment button provided by the shopping mall server 200 and displaying “010-1***-*234”, which is a part of the user’s phone number. You can.

Afterwards, when the user of the user terminal 100 enters the simple payment button to pay for the product purchase using simple payment, and the user of the user terminal 100 has previously set a password for the identity verification question, the user The terminal 100 may display a second screen 103 including an interface for entering a preset password as an answer to an identity verification question to prove occupation of the user terminal 100 by a legitimate user. there is. At this time, depending on the embodiment, the user terminal 100 may display "Hong*dong", which is part of the buyer's name previously stored on the authenticated line, and "Seoul **-gu ** Gil **", which is part of the pre-stored delivery address. You can.

On the other hand, although not shown in FIG. 9, if the user of the user terminal 100 does not set a password for the identity verification question, the user terminal 100 provides the user with a password to enter the answer to the identity verification question. If the password for the identity verification question is (re)set by displaying the interface and the user of the user terminal 100 entering the correct answer to the identity verification question, the user terminal 100 can input the (re)set password. A second screen 103 including an interface may be displayed.

Meanwhile, in the second screen 103, the user of the user terminal 100 enters 'Use a different phone number' in order to pay with a phone number other than the user's own authenticated phone number. In this case, even though it is identified whether the user terminal 100 can use the simple payment through the line identification information of the user terminal 100, the user terminal 100 can proceed with the simple payment using a different phone number. Then, in order to verify whether the user of the user terminal 100 is a legitimate user of the other phone number, the user terminal 100 provides information about the legitimate user of the other phone number ( (e.g. name, date of birth, phone number, etc.) and authentication information indicating whether the legitimate user of the other phone number occupies the terminal of the other phone number (e.g., authentication number sent to the entered phone number) The third screen 105 may be provided from the user authentication server 300 and displayed.

When it is proven that the user of the user terminal 100 is a legitimate user of the other phone number, the user terminal 100 displays information (purchaser name, phone number, delivery address, etc.) previously entered on the other phone number, The fourth screen 107 for simple payment using the other phone number may be provided from the user authentication server 300 and displayed.

When the user terminal 100 inputs the final payment button on the fourth screen 107 (e.g., 'Pay with mobile phone (*234)' on the second screen 103 and 'Pay with mobile phone (*234)' on the fourth screen 107 'Pay with mobile phone (*678)'), simple payment can be made through the payment server 400.

Figure 10 shows an example of a user terminal performing a simple payment when the line of the user terminal is not authenticated according to another embodiment of the present invention.

1 to 8 and 10, when the user terminal 100 connects to the shopping mall server 200 through a network other than a cellular network, such as WiFi or wired Internet, the user terminal 100 performs line authentication. Since it cannot be performed, the user terminal 100 cannot make a simple payment using the line identification information according to line authentication. Accordingly, the user terminal 100 may display the fifth screen 111 including a simple payment button for which the line is not authenticated.

Since the user terminal 100 has not been authenticated as to whether it is a terminal that can use the simple payment service, if the user of the user terminal 100 inputs the simple payment button on the fifth screen 111, the user terminal 100 ) is information about the legitimate user of the phone number for which the user wishes to make a simple payment (e.g., name, date of birth, phone number, etc.) and authentication information indicating whether the legitimate user of the phone number occupies the terminal of the phone number. The sixth screen 113 for allowing users to input (for example, an authentication number sent to the entered phone number) may be provided from the user authentication server 300 and displayed.

If it is proven that the user is the legitimate user of a phone number that allows simple payment, the user terminal displays the information (buyer name, phone number, delivery address, etc.) already entered on the phone number entered by the user and uses the phone number. Thus, the seventh screen 115 for simple payment can be provided from the user authentication server 300 and displayed.

When the user terminal 100 inputs the final payment button on the seventh screen 115 (e.g., ‘Pay with mobile phone (*234)’ on the seventh screen 115), the payment server 400 Payments can be made via mobile phone.

Figure 11 is a block diagram showing the configuration of devices according to an embodiment of the present invention.

Referring to FIGS. 1 and 11 , device 1000 may include a processor 1100, a transceiver 1200, and a memory 1300. Here, the device 1000 may be a user terminal 100, a shopping mall server 200, a user authentication server 300, or a payment server 400.

The processor 1100 can generally control the functions of the device 1000.

The processor 1100 can transmit and receive data from another device using the transceiver 1200.

The memory 1300 may store the program 1400 and information necessary for execution of the program 1400. Here, the program 1400 may refer to software that includes instructions for performing the functions of the device 1000 according to an embodiment of the present specification.

The processor 1100 may load the program 1400 and information necessary for execution of the program 1400 from the memory 1300 in order to execute the program 1400.

The processor 110 may execute the program 1400 to perform the functions of the device 1000 according to an embodiment of the present specification.

According to an embodiment of the present invention, the shopping mall server can provide a simple payment service to the buyer by using the buyer's customer information managed by the mobile communication company server, thereby providing the buyer with a simple payment service without the need for membership registration.

In addition, according to an embodiment of the present invention, the shopping mall server can provide a safer and more user-friendly payment function to the buyer by making a simple payment using the identity verification function provided by the mobile communication company server.

Additionally, according to an embodiment of the present invention, the shopping mall server can provide simple payments to buyers with lower or no fees compared to simple payments provided by large portal sites.

Combinations of each block of the block diagram and each step of the flow diagram attached to the present invention may be performed by computer program instructions. Since these computer program instructions can be mounted on the encoding processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, the instructions performed through the encoding processor of the computer or other programmable data processing equipment are included in each block or block of the block diagram. Each step of the flowchart creates a means to perform the functions described. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular way, so that the computer-usable or computer-readable memory The instructions stored in can also produce manufactured items containing instruction means that perform the functions described in each block of the block diagram or each step of the flow diagram. Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer and can be processed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing functions described in each block of the block diagram and each step of the flow diagram.

Additionally, each block or each step may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative embodiments it is possible for the functions mentioned in blocks or steps to occur out of order. For example, two blocks or steps shown in succession may in fact be performed substantially simultaneously, or the blocks or steps may sometimes be performed in reverse order depending on the corresponding function.

The above description is merely an illustrative explanation of the technical idea of the present invention, and those skilled in the art will be able to make various modifications and variations without departing from the essential quality of the present invention. Accordingly, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention, but rather to explain it, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention shall be interpreted in accordance with the claims below, and all technical ideas within the scope equivalent thereto shall be construed as being included in the scope of rights of the present invention.

10: Simple payment system
100: user terminal
200: Shopping mall server
300: User authentication server
400: Payment server
500: Payment agency server
1000: device
1100: processor
1200: Transceiver
1300: Memory
1400: Program

Claims (13)

In a method of providing simple payment to a user performed by a user terminal,
When accessing a predetermined page provided by a product sales server, transmitting a line authentication request to the mobile carrier server to inquire whether the line of the user terminal is a line that can use a simple payment service;
In response to the line authentication request, receiving a line authentication response including line identification information of the user terminal from the mobile communication service provider server; and
Comprising the step of providing the simple payment to the user using the line identification information.
How to provide easy payments to your users. According to claim 1,
The line identification information is,
Included in the line authentication response as a result of the mobile carrier server performing a header enrichment authentication procedure for the line authentication request.
How to provide easy payments to your users. According to claim 1,
The line identification information is,
As the mobile communication service provider server adds the IP address of the user terminal to the header of the line authentication request, it is obtained from the mobile service provider server.
How to provide easy payments to your users. According to claim 1,
The step of providing the simple payment to the user is,
Using the line identification information, performing identity verification to confirm that the user is a legitimate user of the user terminal; and
Including the step of providing the simple payment according to the identity verification authentication.
How to provide easy payments to your users. According to clause 4,
The step of performing the identity verification authentication is,
When the user has preset a password used for identity verification authentication, providing the user with an interface to allow the user to input the preset password; and
If the password is not preset, providing the user with an interface that allows the user to input information verifying that the user is a legitimate user of the user terminal.
How to provide easy payments to your users. In a method of providing simple payment to a user of a user terminal by a mobile carrier server,
When the user accesses a certain page provided by the product sales server using the user terminal, a line authentication request is made from the user terminal to inquire whether the line of the user terminal is a line that can use the simple payment service. receiving;
Based on the line authentication request, determining whether the user terminal is a terminal capable of using the simple payment provided by the mobile communication company server;
As a result of the determination, transmitting to the user terminal a line authentication response including line identification information used to provide the simple payment; and
When there is a simple payment request from the user terminal, providing the simple payment to the user terminal using the line identification information.
A method of providing simple payments to users of user terminals. According to clause 6,
The above judgment step is,
performing a header enrichment authentication procedure on the line authentication request; and
According to the results of the header enhanced authentication procedure, determining whether the user terminal is a terminal that can use the simple payment provided by the mobile carrier server.
A method of providing simple payments to users of user terminals. According to clause 6,
The above judgment step is,
Using the IP address of the user terminal added to the header of the line authentication request, obtaining identification information of the user terminal assigned to the IP address; and
Using the identification information, determining whether the user terminal is a terminal that can use the simple payment provided by the mobile carrier server.
A method of providing simple payments to users of user terminals. According to clause 6,
The step of providing the simple payment to the user terminal is,
When the simple payment request is made, performing identity verification to verify whether the user is a legitimate user of the user terminal; and
Including the step of providing the simple payment according to the identity verification authentication.
A method of providing simple payments to users of user terminals. According to clause 9,
The step of performing the identity verification authentication is,
When the password used for identity verification authentication is preset, providing an interface to allow the user terminal to input the preset password; and
If the password is not preset, providing an interface that allows the user to input information confirming that he or she is a legitimate user of the user terminal.
How to provide easy payment to your buyers. In the user terminal that provides simple payment to the user,
A transceiver that transmits and receives data to and from the product sales server and mobile carrier server; and
Including a processor that controls the transceiver,
The processor,
By controlling the transceiver, when accessing a predetermined page provided by the product sales server, a line authentication request is made to the mobile carrier server to inquire whether the line of the user terminal is a line that can use the simple payment service. send,
Controlling the transceiver to receive, in response to the line authentication request, a line authentication response including line identification information of the user terminal from the mobile communication service provider server,
Using the line identification information, providing the simple payment to the user
User terminal. In the mobile carrier server that provides simple payment to the user of the user terminal,
A transceiver that transmits and receives data between the user terminal and the product sales server; and
Including a processor that controls the transceiver,
The processor,
By controlling the transceiver, when the user accesses a predetermined page provided by the product sales server using the user terminal, the user terminal determines whether the line of the user terminal is a line that can use the simple payment service. Receive a line authentication request inquiring whether
Based on the line authentication request, determine whether the user terminal is a terminal that can use the simple payment provided by the mobile carrier server,
Controlling the transceiver to transmit, as a result of the determination, a line authentication response containing line identification information used to provide the simple payment to the user terminal,
When there is a simple payment request from the user terminal, the simple payment is provided to the user terminal using the line identification information.
Mobile carrier server. A computer program stored on a computer-readable recording medium,
The computer program is,
Comprising instructions for causing a processor to perform the method according to any one of claims 1 to 10.
computer program.

Images