KR20210068976A - Method and system for simple pament using automatic payment information for mobile phone bill - Google Patents

Abstract

A method and system for simple payment using automatic payment information for a mobile phone bill are provided. A processing server can receive the phone number of the mobile terminal of a user from the user terminal of the user. The processing server can obtain member information of the user registered in a communication company server from the communication company server of a communication company that provides a communication service to the mobile terminal by using the phone number. The processing server can perform payment for a transaction between the user terminal and an affiliated store server using the obtained member information.

Description

Simple payment method and system using automatic mobile phone bill payment information {METHOD AND SYSTEM FOR SIMPLE PAMENT USING AUTOMATIC PAYMENT INFORMATION FOR MOBILE PHONE BILL}

The following embodiments relate to a method and an apparatus for making an electronic payment, and in more detail, a simple payment method and system using payment information for automatic payment of a mobile phone bill are disclosed.

Recently, with the development of information and communication technology, electronic transactions using personal computers and mobile terminals, etc. are being actively performed.

Due to the characteristics of electronic transactions, information about the buyer's credit card or bank account must be provided to the seller in order to proceed with the payment.

The input of information for such payment may cause inconvenience to the purchaser. In particular, since the server for the electronic transaction is operated separately for each seller, the buyer may have to input information for such payment whenever he/she purchases an item from a specific seller.

For example, even when a buyer purchases an item anonymously through a specific seller's server without registering as a member, information for payment must be entered. Such input may cause inconvenience as described above, and the buyer's personal information may be exposed to the seller.

An embodiment may provide a method, apparatus, and system for performing payment in a more convenient manner for users.

An embodiment may provide a method, apparatus, and system for performing payment for a transaction with another seller using payment information of a user registered with a telecommunication company.

In one side, in a payment system, comprising: a processing server, the processing server receiving a phone number of the user's mobile terminal from the user terminal of the user, the processing server using the phone number to the mobile terminal A payment system that obtains member information of the user registered in the communication company server from a communication company server of a communication company that provides a communication service to users, and performs payment for a transaction between the user terminal and the affiliated store server using the member information is provided

On the other side, one or more processors; and a memory storing one or more programs executed by the one or more processors, wherein the one or more programs receive a phone number of the user's mobile terminal from the user's user terminal, and use the phone number to Obtaining member information of the user registered in the communication company server from a communication company server of a communication company that provides a communication service to a mobile terminal, and performing payment for a transaction between the user terminal and the affiliated store server using the member information, processing Server is provided.

In another aspect, a mobile terminal comprising: one or more processors; and a memory for storing one or more programs executed by the one or more processors, wherein the one or more programs are used for payment approval for a transaction between a user terminal and a merchant server from a processing server that has received the phone number of the mobile terminal. A mobile terminal is provided for receiving a request, performing the payment approval, and transmitting a result of the payment approval to the processing server.

In another aspect, in the payment system, a user terminal; and a mobile terminal, wherein the user terminal transmits a request for payment for a transaction between the user terminal and the affiliated store server to a processing server, and the request for payment is a phone call of the mobile device input by the user of the shopping mall user terminal number, wherein the mobile terminal receives a request for payment approval for the transaction between the user terminal and the affiliated store server from the processing server, performs the payment approval, and sends a result of the payment approval to the processing server transfer, payment system.

A method, apparatus, and system for performing a payment in a more user-friendly manner are provided.

A method, apparatus, and system for performing a payment for a transaction with another seller by using payment information of a user registered with a telecommunication company are provided.

1 illustrates a system for providing a simple payment service according to an embodiment.
2 is a flowchart of simple payment service subscription according to an embodiment.
3 is a flowchart of a simple payment request according to an embodiment.
4 is a flowchart of a simple payment app installation according to an embodiment.
5 is a flowchart of simple payment service subscription according to an embodiment.
6 is a flowchart of using a simple payment service according to an embodiment.
7 is a flowchart of a simple payment request according to an embodiment.
8 is a flowchart of simple payment information generation according to an embodiment.
9 is a flowchart of simple payment approval according to an exemplary embodiment.
10 is a flowchart of payment according to an exemplary embodiment.
11 is a flowchart of providing a simple payment result according to an exemplary embodiment.
12 illustrates a product selection screen according to an example.
13 illustrates a simple payment screen according to an example.
14 illustrates a payment waiting screen according to an example.
15 shows a user authentication screen according to an example.
16 illustrates a payment information confirmation screen according to an example.
17 illustrates a payment completion screen according to an example.
18 illustrates an order completion screen according to an example.
19 illustrates a product selection screen according to an example.
20 illustrates a simple payment screen according to an example.
21 illustrates a payment waiting screen according to an example.
22 illustrates a payment request screen according to an example.
23 shows a user authentication screen according to an example.
24 shows a payment information confirmation screen according to an example.
25 illustrates a payment completion screen according to an example.
26 shows an order completion screen according to an example.
27 shows an installation screen of a simple payment app according to an example.
28 shows an execution screen of a simple payment app according to an example.
29 shows the agreement agreement screen of the simple payment app according to an example.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0010] Reference is made to the accompanying drawings, which illustrate specific embodiments by way of example. These embodiments are described in sufficient detail to enable those skilled in the art to practice the embodiments. It should be understood that various embodiments are different but need not be mutually exclusive. For example, certain shapes, structures, and characteristics described herein with respect to one embodiment may be embodied in other embodiments without departing from the spirit and scope of the invention. In addition, it should be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the embodiment. Accordingly, the detailed description set forth below is not intended to be taken in a limiting sense, and the scope of exemplary embodiments, if properly described, is limited only by the appended claims, along with all scope equivalents to those claimed.

Like reference numerals in the drawings refer to the same or similar functions throughout the various aspects. Shapes and sizes of elements in the drawings may be exaggerated for clearer description.

Terms used in the examples are for describing the examples and are not intended to limit the present invention. In embodiments, the singular also includes the plural unless the phrase specifically dictates otherwise. As used herein, "comprises" and/or "comprising" refers to the presence of one or more other components, steps, operations and/or elements mentioned. Or addition is not excluded, and it means that an additional configuration may be included in the scope of the technical spirit of the exemplary embodiments or the implementation of the exemplary embodiments. When a component is referred to as being “connected” or “connected” to another component, the two components may be directly connected or connected to each other, but in the above 2 It should be understood that other components may exist in the middle of the components.

Terms such as first and second may be used to describe various components, but the above components should not be limited by the above terms. The above terms are used to refer to one component as distinct from another component. For example, without departing from the scope of the rights, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component.

In addition, components shown in the embodiments are shown independently to represent different characteristic functions, and it does not mean that each component is made of separate hardware or only one software component unit. That is, each component is listed as each component for convenience of description. For example, at least two of the components may be combined into one component. Also, one component may be divided into a plurality of components. Integrated embodiments and separate embodiments of each of these components are also included in the scope of rights without departing from the essence.

In addition, some of the components are not essential components to perform essential functions, but may be optional components only to improve performance. Embodiments may be implemented including only components essential for implementing the essence of the embodiments, and for example, structures in which optional components are excluded, such as components used only for performance improvement, are also included in the scope of rights.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings in order to enable those of ordinary skill in the art to easily implement the embodiments. In describing the embodiments, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present specification, the detailed description thereof will be omitted.

1 illustrates a system for providing a simple payment service according to an embodiment.

A system for providing a simple payment service includes a user terminal 110 , a mobile terminal 120 , a merchant server 130 , a processing server 140 , a communication company server 150 , an authentication server 160 , and a payment server 170 . may include

The user terminal 110 and the mobile terminal 120 may be terminals operated by a user.

For example, the user terminal 110 may be a stationary device such as a personal computer (PC), and the mobile terminal 120 may be a mobile device such as a smart phone.

In one embodiment, the user terminal 110 and the mobile terminal 120 may be physically the same device, or may be physically separate devices. For example, when a user orders a transaction object with the mobile terminal 120 , the mobile terminal 120 described in the embodiment may be understood as the user terminal 110 .

Accordingly, the description of the user terminal 110 may be understood as being replaced with that of the mobile terminal 120 , and the description of the mobile terminal 120 may be understood as being replaced with that of the user terminal 110 .

In addition, the names of the user terminal 110 and the mobile terminal 120 may be given only to help understanding of representative embodiments. The user terminal 110 may be a "transaction terminal" that the user processes an operation for a purchase of a transaction target, and the mobile terminal 120 may be a "payment terminal" that processes an operation for a simple payment for a transaction object have.

The affiliated store server 130 may be a server that sells a transaction object that the user wants to make a transaction. Here, the transaction target may mean goods, products, services and services. In addition, the transaction target may be broadly understood as payment of money, such as payment of utility bills, taxes and fines.

For example, a transaction may mean an order for a product to be traded.

The affiliate store server 130 may be a server operated by the affiliate store. The affiliated store may mean a seller who has subscribed to the simple payment service provided by the processing server 140 . In this sense, in the embodiment, "merchant store" may be understood as being replaced with "sales store", and the affiliated store server 130 may be replaced with "sales server".

The processing server 140 may be a server that provides a simple payment service. The processing server 140 provides a transaction to a user using the user terminal 110 and the mobile terminal 120 through interworking with the affiliated store server 130 , the communication company server 150 , the authentication server 160 , and the payment server 170 . A simple payment service for payment for a target may be provided. In this sense, in the embodiment, the processing server 140 may be understood as being replaced with a payment authentication server of the simple payment service, and the processing server 140 may be replaced with a “payment authentication server”.

The processing server 140 may be a server operated by a provider of a simple payment service. Operators of the affiliate store server 130 , the communication company server 150 , the authentication server 160 , and the payment server 170 may subscribe to the simple payment service.

The communication company server 150 may be a server operated by a communication company subscribed by the user. A communication company may provide a communication service such as a mobile communication service to the mobile terminal 120 . Alternatively, the communication company may provide a communication service such as the Internet to the user terminal 110 .

The authentication server 160 may be a server operated by a Certificate Authority (CA). In other words, the authentication server 160 may be a CA server. The authentication server 160 may authenticate the user and issue a user's certificate.

The payment server 170 may perform payment for a transaction between the user and the affiliated store. The payment server 170 may be operated by a financial institution such as a credit card card used by the user or a bank of a bank account used by the user. Alternatively, the payment server 170 may be a payment institution for payment for a transaction, such as the Korea Financial Telecommunications and Clearings Institute. In this sense, in the embodiment, the payment server 170 may be understood as a substitute for a financial server of a financial company or a payment institution server of a payment institution, and the payment server 170 is a "financial server" or "payment institution server" can be replaced.

Device configuration for easy payment service

As described above, the devices for the simple transaction service are the user terminal 110 , the mobile terminal 120 , the affiliated store server 130 , the processing server 140 , the communication company server 150 , the authentication server 160 , and the payment server. (170). Each of these devices may include a processing unit, a communication unit, a storage unit, and the like.

The device may include at least a portion of a processing unit, a communication unit, and a storage unit as components. The components may communicate with each other via one or more communication buses or signal lines.

Components described with respect to the device, such as a processing unit, a communication unit, and a storage unit, may be merely examples. Not all of the illustrated components may be essential to the device. The device may have more or fewer components than those described in the embodiments. Also, two or more components may be combined.

Each component may be implemented in hardware including one or more signal processing and/or application specific integrated circuits (ASICs), implemented in software, or a combination of hardware and software.

The processing unit may process a task required for the operation of the device. The processing unit may execute a code of an operation or step of the processing unit described in the embodiments.

The processing unit may generate and process a signal, data, or information input to, output from, or generated by the device, and may perform inspection, comparison, and judgment related to the signal, data or information. In other words, the generation and processing of data or information described in the embodiment and the inspection, comparison and judgment related to the data or information can be performed by the processing unit.

For example, the processing unit may be at least one processor.

The processor may be a hardware processor, or a central processing unit (CPU). There may be a plurality of processors. Alternatively, the processor may include a plurality of cores, and may provide multi-tasking for simultaneously executing a plurality of processes and/or a plurality of threads. At least some of the steps of the embodiments may be performed in parallel for a plurality of objects via a plurality of processors, a plurality of cores, a plurality of processes and/or a plurality of threads.

For example, the processing unit may execute code of an operation or step of the apparatus described in the embodiments.

For example, the processing unit may run a program. The processing unit may execute code constituting the program. The program may include an operating system (OS) of the device, a system program, an application, and an app.

In addition, the processing unit may control other components of the device for the functions of the processing unit described above.

The communication unit may receive data or information used for operation of the device, and may transmit data or information used for operation of the device.

The communication unit may transmit data or information to another device in a network to which the device is connected, and may receive data or information from the other device. In other words, the transmission or reception of data or information described in the embodiments may be performed by the communication unit.

For example, the communication unit may be a networking chip, a networking interface, or a communication port.

The storage unit may store data or information used for the operation of the device. In other words, data or information possessed by the device described in the embodiments may be stored in the storage unit.

For example, the storage unit may be a memory. The storage unit may include a built-in storage medium such as a RAM and a flash memory, and may include a removable storage medium such as a memory card.

The storage unit may store at least one program. The processing unit may execute at least one program. The processing unit may read a code of at least one program from the storage unit, and may execute the read code.

The operations, functions and features of the processing unit, communication unit and storage unit of the apparatus will be described in detail below with reference to embodiments.

The device may further include an output. The output unit may output data or information possessed by the device. In other words, data or information output in YYY (ZZZ) described in the embodiment may be output by the output unit.

A user of the device may recognize data or information output through the output unit.

Configuration of easy payment service

A method of providing a user with a payment service for an object may include a service subscription step 180 and a service use step 190 .

In step 180 , the user terminal 110 through interworking between the user terminal 110 , the mobile terminal 120 , the affiliated store server 130 , the processing server 140 , the communication company server 150 and the authentication server 160 . and the user of the mobile terminal 120 may subscribe to the simple payment service provided by the processing server 140 .

In step 190, interworking between the user terminal 110, the mobile terminal 120, the affiliated store server 130, the processing server 140, the communication company server 150, the authentication server 160, and the payment server 170 is performed. Through this, a simple payment service may be provided to users of the user terminal 110 and the mobile terminal 120 .

2 is a flowchart of simple payment service subscription according to an embodiment.

Step 180 may include steps 210 , 220 and 230 .

In step 210 , a simple payment request may be performed through interworking between the user terminal 110 , the affiliated store server 130 , and the processing server 140 .

Step 210 is exemplary and may be omitted. As step 210 is omitted, step 220 may be performed for simple payment service subscription.

In step 220 , the simple payment app for using the simple payment service may be installed through interworking between the mobile terminal 120 and the processing server 140 .

In step 230 , a simple payment service subscription may be performed through interworking between the mobile terminal 120 , the processing server 140 , the communication company server 150 , and the authentication server 160 .

3 is a flowchart of a simple payment request according to an embodiment.

Step 210 may include steps 310 , 320 , 330 , 340 , 350 and 360 .

In step 310 , the user terminal 110 may transmit a request for a payment page to the affiliate store server 130 .

The payment page may be a page that processes payment for a transaction target.

The payment page may include information on a transaction target. For example, when the transaction target is a product, the information on the transaction target may be product information.

The payment page may include information about payment. The payment information may include payment amount information.

The payment page may include options to select payment methods. The options may include easy payment. That is to say, the payment page may include an option indicating simple payment.

For example, the options may be a Graphical User Interface (GUI) object such as a list box, buttons, and options.

In step 320 , the affiliated store server 130 may transmit the payment page to the user terminal 110 as a response to the request for the payment page. The user terminal 110 may receive a payment page from the affiliate store server 130 .

In step 330 , the user terminal 110 may output a payment page.

Simple payment may be selected from among the payment methods of the payment page output to the user terminal 110 by the user. The user terminal 110 may recognize selection of simple payment by the user.

In step 340 , a phone number of the user's mobile terminal 120 for simple payment may be input to the user terminal 110 by the user. That is, the phone number may be the user's mobile phone number. The user terminal 110 may receive the user's phone number for simple payment input by the user.

In step 350 , the user terminal 110 may transmit a request for simple payment for a transaction between the user terminal 110 and the affiliated store server 130 to the processing server 140 .

Here, the transaction between the user terminal 110 and the affiliated store server 130 may mean a transaction between the user and the affiliated store.

The simple payment request may include a phone number.

The simple payment request may include purchase information for a transaction between the user terminal 110 and the affiliate store server 130 .

For example, the purchase information may include 1) affiliate store information on the affiliated store, 2) transaction target information on the transaction target of the transaction, and 3) payment amount information on the payment amount of the transaction. In other words, the purchase information may be information specifying a party of payment and a transaction target of the payment.

Here, direct communication between the user terminal 110 and the processing server 140 may not occur.

For example, the payment page may include a simple payment module. The simple payment request may be transmitted from the affiliate store server 130 to the processing server 140 through the simple payment module.

For example, when the user selects the simple payment output on the user terminal 110, the payment web page of the service server that provides the simple payment may be called, and the request of the simple payment from the called payment web page is processed by the processing server ( 140) may be transmitted.

In step 360 , the processing server 140 may identify the user of the user terminal 110 using the user's phone number and purchase information, and may determine whether the user has subscribed to the simple payment service.

For example, the processing server 140 may use 1) the user's phone number and 2) affiliate store information about the affiliated store to confirm whether the user and the affiliated store have signed up for the simple payment service.

For example, the processing server 140 may use the user's phone number to check whether the user has subscribed to the simple payment service.

For example, the processing server 140 may check whether the affiliated store has subscribed to the simple payment service by using the affiliated store information on the affiliated store.

The processing server 140 may inquire whether the user has subscribed to the simple payment service using the phone number and purchase information.

If the processing server 140 confirms that the user has not subscribed to the simple payment service, steps 220 and 230 may be performed.

4 is a flowchart of a simple payment app installation according to an embodiment.

Step 220 may include steps 410 , 420 , 430 , 440 , 450 and 460 .

In step 410 , the processing server 140 may transmit an installation guidance message for inducing installation of the simple payment app to the mobile terminal 120 .

In other words, when the simple payment request is transmitted from the user terminal 110 to the processing server 140 , the processing server 140 is sent to the mobile terminal 120 corresponding to the user's phone number received through the simple payment request. can be transmitted

The processing server 140 may use the user's phone number to specify the mobile terminal 120 to which the installation induction message is to be transmitted. The processing server 140 may transmit an installation guidance message to the smartphone corresponding to the user's phone number.

For example, the installation prompt message may be a push message.

For example, the installation induction message may be a Short Message Service (SMS) message.

For example, the installation guidance message may include a link for installing the simple payment app. The link may include a Uniform Resource Locator (URL).

In step 420 , through the user's selection, the mobile terminal 120 may install a simple payment app.

For example, the mobile terminal 120 may recognize that the user clicks on the link of the installation guidance message, and may install the simple payment app as an operation indicated by the clicked link.

In step 430 , the simple payment app of the mobile terminal 120 may output the terms of use of the simple payment service.

In step 440 , the simple payment app of the mobile terminal 120 may perform user authentication for subscribing to the simple payment service.

In step 450 , the user may input a lock setting for lock authentication for the user to use the simple payment service in the simple payment app of the mobile terminal 120 , and the simple payment app of the mobile terminal 120 is input The specified lock settings can be registered as lock authentication.

For example, the lock setting method may be at least one of a personal identification number (PIN), a password, a pattern, and biometric information of a user.

For example, the user's biometric information may be one or more of a user's fingerprint, a user's iris, and a user's face. The mobile terminal 120 may further include a sensor for recognizing the user's biometric information, such as a fingerprint sensor and a camera.

In step 460 , when the lock setting is completed, the app of the mobile terminal 120 may generate a key pair for issuing a certificate for using the simple payment service. The key pair may include a public key of the user and a private key of the user.

The mobile terminal 120 may generate an encrypted private key by performing encryption on the user's private key using information related to the user and/or the mobile terminal 120 , and use the encrypted private key to convert the encrypted private key to the mobile terminal 120 . ) can be stored in the safe area of

For example, the safe area may include a keystore, a keychain, a white box crypto (WBC), a USIM, and a cloud.

5 is a flowchart of simple payment service subscription according to an embodiment.

Step 230 may include steps 510 , 520 , 530 , 540 , 550 , 560 , 570 and 580 .

The distinction between step 220 and step 230 may be variable. For example, as in step 460 , some of the last of the steps in step 220 may be included in step 230 . Alternatively, some of the first of the steps of step 230 may be included in step 220 .

In step 510 , the simple payment app of the mobile terminal 120 may transmit a simple payment service subscription request to the processing server 140 for requesting subscription to the simple payment service.

The simple payment service subscription request may be a request for issuing a certificate for the simple payment service.

The simple payment service subscription request may include the user's public key. In other words, the simple payment app of the mobile terminal 120 may transmit a request for subscription to the simple payment service including the user's public key to the processing server 140 in order to receive a certificate for the simple payment service.

The simple payment service subscription request may include a phone number and unique identification information of the mobile terminal 120 . The simple payment app may automatically call a phone number from the SIM, and include the called phone number and unique identification information in the request for simple payment service subscription.

The processing server 140 may identify the user of the mobile terminal 120 using the phone number and unique identification information, and may associate the identified user with the mobile terminal 120 to subscribe to the simple payment service.

In step 520 , the processing server 140 may use the phone number of the mobile terminal 120 to specify a communication company server 150 of a communication company that provides a communication service to the mobile terminal 120 among a plurality of communication company servers. can The processing server 140 may transmit a request for member information for the user to the communication company server 150 corresponding to a phone number.

In operation 530 , the communication company server 150 may transmit member information to the processing server 140 as a response to the request for member information.

The processing server 140 may use the member information to perform a payment for a transaction between the user terminal 110 and the affiliate store server 130 as will be described below.

For example, the member information may include the user's name and the user's address. The user's address may be the user's residence.

The member information may include payment information of the user.

The payment information may be information about payment of automatic bill payment registered with respect to the user's phone number (or the mobile terminal 120 ). For example, the payment information may be regarded as automatic payment payment information. Alternatively, the payment information may be information for payment for automatic payment of the communication fee of the mobile terminal 120 .

For example, the payment information may include credit card information for the user's credit card or account information for the user's account. In addition, the payment information may include withdrawal consent information indicating consent to withdrawal from the user's credit card or account.

For example, the credit card information may be information about a credit card registered to automatically pay a fee for a user's phone number. For example, the credit card information may include the name of the credit card company, the number of the credit card, and the validity period of the credit card.

For example, the account information may be information on a bank account registered to automatically pay a fee for a user's phone number. For example, the account information may include a name of a bank and a number of a bank account.

In step 540, the processing server 140 may generate user information using the member information. The user information may be information specifying a user among member information, or may be information remaining from the member information excluding payment information.

For example, the user information may include the user's name and the user's address. Alternatively, the processing server 140 may use all or part of the member information as user information.

When the user information is generated, the processing server 140 may transmit a request for a certificate to the authentication server 160 .

The request for a certificate may include the user's public key and user information.

In step 550, the authentication server 160 may generate a certificate for the user.

The authentication server 160 may generate a certificate for the user using the user information and the user's public key.

The authentication server 160 may generate an encrypted certificate by performing encryption on the certificate using the user's public key.

In step 560 , the authentication server 160 may transmit the encrypted certificate to the processing server 140 as a response to the request for the certificate.

In operation 570 , the processing server 140 may transmit a subscription completion message to the mobile terminal 120 as a response to the request for subscription to the simple payment service.

The subscription completion message may include an encrypted certificate.

In step 580, the mobile terminal 120 may obtain the certificate by performing decryption on the encrypted certificate using the user's private key.

The mobile terminal 120 may store the certificate.

In step 590, the processing server 140 may subscribe the user to the simple payment service.

6 is a flowchart of using a simple payment service according to an embodiment.

Step 190 may include steps 610 , 620 , 630 , 640 and 650 .

In step 610 , a simple payment request may be performed through interworking between the user terminal 110 , the affiliate store server 130 , and the processing server 140 .

In step 620 , simple payment information generation may be performed through interworking between the affiliate store server 130 , the processing server 140 , and the communication company server 150 .

In operation 630 , simple payment approval may be performed through interworking between the mobile terminal 120 , the processing server 140 , and the authentication server 160 .

In operation 640 , payment may be performed through interworking between the processing server 140 and the payment server 170 .

In step 650 , the simple payment result may be provided through interworking between the user terminal 110 , the affiliate store server 130 , and the processing server 140 .

7 is a flowchart of a simple payment request according to an embodiment.

Step 610 may include steps 710 , 720 , 730 , 740 , 750 and 760 .

In step 710 , the user terminal 110 may transmit a request for a payment page to the affiliate store server 130 .

The payment page may be a page that processes payment for a transaction target.

The payment page may include information on a transaction target. For example, when the transaction target is a product, the information on the transaction target may be product information.

The payment page may include information about payment. The payment information may include payment amount information.

The payment page may include options to select payment methods. The options may include easy payment. That is to say, the payment page may include an option indicating simple payment.

For example, the options may be a Graphical User Interface (GUI) object such as a list box, buttons, and options.

In step 720 , the affiliate store server 130 may transmit the payment page to the user terminal 110 as a response to the request for the payment page. The user terminal 110 may receive a payment page from the affiliate store server 130 .

In step 730, the user terminal 110 may output a payment page.

Simple payment may be selected from among the payment methods of the payment page output to the user terminal 110 by the user. The user terminal 110 may recognize selection of simple payment by the user.

In step 740 , the user's phone number for simple payment may be input to the user terminal 110 by the user. The user terminal 110 may receive the user's phone number for simple payment input by the user.

In operation 750 , the user terminal 110 may transmit a request for simple payment for a transaction between the user terminal 110 and the affiliate store server 130 to the processing server 140 .

Here, the transaction between the user terminal 110 and the affiliated store server 130 may mean a transaction between the user and the affiliated store.

The simple payment request may include a phone number.

The simple payment request may include purchase information for a transaction between the user terminal 110 and the affiliate store server 130 .

For example, the purchase information may include 1) the user's phone number, 2) merchant information about the merchant, 3) transaction target information for the transaction target of the transaction, and 4) payment amount information for the payment amount of the transaction. have. In other words, the purchase information may be information specifying a party of payment and a transaction target of the payment.

In operation 760 , the processing server 140 may identify the user of the user terminal 110 using the purchase information, and may determine whether the user has subscribed to the simple payment service.

For example, the processing server 140 may use 1) the user's phone number and 2) affiliate store information about the affiliated store to confirm whether the user and the affiliated store have signed up for the simple payment service.

For example, the processing server 140 may use the user's phone number to check whether the user has subscribed to the simple payment service.

For example, the processing server 140 may check whether the affiliated store has subscribed to the simple payment service by using the affiliated store information on the affiliated store.

The processing server 140 may inquire whether the user has subscribed to the simple payment service by using the purchase information.

When the processing server 140 confirms that the user has subscribed to the simple payment service, steps 620 , 630 , 640 and 650 may be performed.

8 is a flowchart of simple payment information generation according to an embodiment.

Step 620 may include steps 810 , 820 , 830 and 840 .

In operation 810 , the processing server 140 may specify a communication company server 150 of a communication company that provides a communication service to the mobile terminal 120 using the phone number of the mobile terminal 120 . The processing server 140 may transmit a request for member information for the user to the communication company server 150 corresponding to a phone number.

In operation 820 , the communication company server 150 may transmit member information registered in the communication company server 150 to the processing server 140 as a response to the request for member information.

For example, the member information may include the user's name and the user's address. The user's address may be the user's residence.

The member information may include payment information of the user.

The payment information may be information about payment of automatic bill payment registered with respect to the user's phone number (or the mobile terminal 120 ). For example, the payment information may be regarded as automatic payment payment information. Alternatively, the payment information may be information for payment for automatic payment of the communication fee of the mobile terminal 120 .

For example, the payment information may include credit card information for the user's credit card or account information for the user's account. In addition, the payment information may include withdrawal consent information indicating consent to withdrawal from the user's credit card or account.

For example, the credit card information may be information about a credit card registered to automatically pay a fee for a user's phone number. For example, the credit card information may include the name of the credit card company, the number of the credit card, and the validity period of the credit card.

For example, the account information may be information on a bank account registered to automatically pay a fee for a user's phone number. For example, the account information may include a name of a bank and a number of a bank account.

In operation 830 , the processing server 140 may generate a payment identifier (ID) for a transaction between the user terminal 110 and the affiliate store server 130 . The payment identifier may be information identifying a transaction between the user terminal 110 and the affiliate store server 130 .

The payment identifier may be associated with the aforementioned 1) user's phone number, 2) purchase information, 3) member information, and 4) payment information. The processing server 140 may store the payment ID, the user's phone number, purchase information, member information, and payment information, for example, as one row in a table, in a database.

In one embodiment, in the storage, some of the above-mentioned information, such as the user's phone number, purchase information and member information, may be optional information.

In step 840 , the processing server 140 may transmit the payment ID and transaction information to the affiliate store server 130 .

The transaction information may be information about a transaction between the user terminal 110 and the affiliate store server 130 . In other words, the transaction information may be information specifying a transaction between the user terminal 110 and the affiliate store server 130 . The transaction information may correspond to information on a transaction target in the payment page of step 310 . In addition, the transaction information is only a part of the information on the transaction object in the payment page of step 310 , and may not include additional information other than the information on the transaction object in the payment page of step 310 .

The affiliated store server 130 may identify the payment ID for which transaction with which user terminal 110 the payment ID transmitted together using the transaction information.

For example, the transaction information of step 840 may be the same as the transaction target information described above with reference to step 750 .

For example, the transaction information of step 840 may include the above-described transaction target information and payment amount information with reference to step 750 .

For example, the transaction information of step 840 may be at least a part of the purchase information described above with reference to step 750 .

The transaction information may not include credit card information and account information. In addition, the transaction information may not include delivery information to be described later.

Through the payment ID and transaction information, the affiliated store server may recognize an ID indicating payment for a transaction between the user terminal 110 and the affiliated store server 130 .

9 is a flowchart of simple payment approval according to an exemplary embodiment.

Step 630 may include steps 910 , 915 , 920 , 925 , 930 , 935 , 940 , 945 , 950 , 955 , 960 , 965 , 970 and 975 .

In operation 910 , the processing server 140 may transmit a payment approval request for payment approval for a transaction between the user terminal 110 and the affiliate store server 130 to the mobile terminal 120 .

In other words, when the simple payment request is transmitted from the user terminal 110 to the processing server 140 , the processing server 140 is sent to the mobile terminal 120 corresponding to the user's phone number received through the simple payment request. can be transmitted

For example, the request for payment approval may be a push message to a simple payment app installed in the mobile terminal 120 .

The request for payment approval may include a payment ID. In addition, the request for payment approval may include affiliate store information and product information. The product information may include a product price.

In step 915 , as the mobile terminal 120 receives the request for payment approval, the mobile terminal 120 may execute a simple payment app installed in the mobile terminal 120 .

The executed simple payment app may be locked for lock authentication according to the lock setting registered in step 450 . The lock authentication may be for identity verification of the user. In other words, the lock authentication may be for confirming whether a person operating the mobile terminal 120 is a legitimate user.

In an embodiment, the lock screen of the lock may be a lock setting registered in the simple payment app set in step 450 when the user subscribes to the easy payment service according to the lock setting in step 450 .

In step 920 , the user of the mobile terminal 120 may unlock the simple payment app. The user may input information for releasing the registered lock setting in step 450 . For example, the information for releasing the lock setting may be one of a PIN, a password, a pattern, and biometric information of a user. As information for releasing the lock setting by the user is input into the simple payment app of the mobile terminal 120 , the lock of the simple payment app may be unlocked.

In step 925 , the simple payment app of the mobile terminal 120 may generate an encrypted payment ID by encrypting the payment ID using the user's private key.

In step 930 , the simple payment app of the mobile terminal 120 may transmit a request for signature information to the processing server 140 .

The request for signature information may include an encrypted payment ID.

When the processing server 140 receives the request for signature information, the processing server 140 may obtain the payment ID by performing decryption on the encrypted payment ID using the user's public key. The processing server 140 may identify the payment requested by the simple payment app of the mobile terminal 120 using the obtained payment ID.

In step 935 , the processing server 140 may transmit a request for the user's certificate to the authentication server 160 .

The request for a certificate may include unique identification information of the user.

When the authentication server 160 receives a request for a certificate, the authentication server 160 may identify a certificate for the user using the user's unique identification information.

Here, the certificate may be a certificate generated in step 550 of FIG. 5 and stored in the authentication server 160 .

In step 940 , the authentication server 160 may transmit the certificate to the processing server 140 .

In step 945 , the processing server 140 may perform verification of the payment ID.

In step 950 , the processing server 140 may transmit the signature information to the simple payment app of the mobile terminal 120 .

The signature information may include the original signature request text.

In an embodiment, the signature information may include at least a portion of payment information, and may include at least a portion of user information. In other words, the signature information may include information that enables the user of the mobile terminal 120 to identify a transaction that the user of the mobile terminal 120 wants to approve in addition to the original text of the signature request and to confirm the transaction details.

Alternatively, in another embodiment, at least a portion of the above-described payment information and at least a portion of the user information may be included in the request for payment approval in step 910, and to be provided to the mobile terminal 120 through the request for payment approval. may be

The processing server 140 may perform encryption on each of the payment ID, at least a portion of the payment information, and at least a portion of the user information to generate an encrypted payment ID, encrypted payment information, and encrypted user information, The encrypted payment ID, encrypted payment information, and encrypted user information may be included in the signature information of step 950 . In this case, the user's public key may be used for encryption.

When the simple payment app of the mobile terminal 120 receives a request for signature information or payment approval, it decrypts each of the encrypted payment ID, the encrypted payment information, and the encrypted user information, so that the payment ID, payment information, and user information can be generated. In this case, the user's private key may be used for decryption.

In step 955, the simple payment app of the mobile terminal 120 outputs at least a portion of the payment information and/or at least a portion of the user information in order to allow the user to check the contents of the payment subject to approval before the user approves the payment. can Also, after step 955, unlocking of step 920 may be performed once again.

In step 960 , the user may check payment information and input approval of payment. For example, the user may perform an input into a GUI object representing approval of payment, such as clicking on a button.

As the user inputs approval for payment, the simple payment app of the mobile terminal 120 may obtain approval for payment.

In step 965, the simple payment app of the mobile terminal 120 may generate a signature value by performing an electronic signature on the original signature request using the private key.

The simple payment app of the mobile terminal 120 may generate a signature value by encrypting the original signature text using the user's private key.

In step 970 , the simple payment app of the mobile terminal 120 may transmit the signature value to the processing server 140 .

The simple payment app of the mobile terminal 120 may transmit the signature value to the processing server 140 as a response to the request for payment approval.

In step 975, the processing server 140 may perform verification of the signature value.

When the processing server 140 receives the signature value, the processing server 140 may generate a signature original text by performing decryption on the signature value using the user's public key.

10 is a flowchart of payment according to an exemplary embodiment.

Step 640 may include steps 1010 , 1020 , 1030 and 1040 .

In step 1010 , the processing server 140 may verify payment information.

The processing server 140 may specify the payment server 170 to perform payment for the transaction between the user terminal 110 and the affiliated store server 130 among the plurality of payment servers by confirming the payment information.

For example, when the payment information includes credit card information, the processing server 140 may use the credit card information to select a server of a credit card company of the user's credit card as the payment server 170 .

For example, if the payment information includes account information, the processing server 140 may use the account information to select a server of a bank of the user's bank account as the payment server 170 .

For example, the processing server 140 may include the transaction between the user terminal 110 and the affiliated store server 130 in automatic bill payment for the user's phone number. In other words, the cost according to the transaction between the user terminal 110 and the affiliated store server 130 may be included in the automatic fee payment for the phone number and charged to the user. In this case, the processing server 140 may select, as the payment server 170 , an automatic bill payment server that processes automatic bill payment for the telecommunication company server 150 or a phone number using account information.

In step 1020 , the processing server 140 may transmit a payment request to the payment server 170 .

The payment request may include information required to perform payment for a transaction between the user terminal 110 and the affiliated store server 130 .

For example, the request for payment may include payment information and purchase information.

In step 1030 , the payment server 170 may perform payment for a transaction between the user terminal 110 and the affiliate store server 130 .

For example, if the payment server 170 is a server of a credit card company, the payment server 170 may process a transaction between the user terminal 110 and the affiliate store server 130 using the user's credit card. The payment server 170 may include a transaction between the user terminal 110 and the affiliated store server 130 in the use of the credit card.

For example, if the payment server 170 is a server of a bank, the payment server 170 may transfer the payment amount according to the payment amount information from the user's account to the merchant's account.

In an embodiment, if the payment server 170 is the communication company server 150 or the automatic fee payment server, the payment server 170 may include the payment amount according to the payment amount information in the fee for the phone number. In other words, the payment amount for the transaction between the user terminal 110 and the affiliate store server 130 may be included in the fee for the user's phone number, and a fee including the payment amount may be charged to the user.

As described above, in one embodiment, the processing server 140 transmits the user terminal 110 and the affiliated store server to the communication company server 150 or the automatic bill payment server through analysis of the payment information provided from the communication company server 150 . 130) may request payment for a transaction between the As the telecommunication company server 150 or the automatic bill payment server performs payment for a transaction between the user terminal 110 and the affiliated store server 130, the payment to the credit card company or bank that processes the payment of the phone number Payment for a transaction between the user terminal 110 and the affiliate store server 130 may be performed without a request.

Alternatively, in another embodiment, the communication company server 150 may provide information about a credit card or bank account for payment to the processing server 140 . For example, the payment information may include information about a credit card or bank account for payment. The processing server 140 may perform a payment for a transaction between the user terminal 110 and the affiliated store server 130 using the provided credit card or bank account information for payment. As the processing server 140 performs payment for a transaction between the user terminal 110 and the affiliate store server 130 using the credit card or bank account information for payment provided, the user's input can be simplified. . For example, for payment, the user may not input credit card information and account information into either of the user terminal 110 and the mobile terminal 120 . As the processing server 140 performs payment, payment for a transaction between the user terminal 110 and the affiliate store server 130 may be performed in real time.

In addition, as described above, as the telecommunication company server 150 or the automatic fee payment server performs a payment for a transaction between the user terminal 110 and the affiliate store server 130 , the user receives information about the transaction with the affiliate store server 130 . For payment, without registering a credit card and a bank account, the payment can be easily performed through the mobile terminal 120 by using the information about automatic bill payment registered in the payment server 170 .

At this time, in step 820 , since member information registered in the communication company server 150 is provided to the processing server 140 , the processing server 140 may store information necessary for delivery and transaction, and the delivery and information necessary for the transaction. Through such provision, after a phone number is input by the user, information necessary for delivery and transaction may not be additionally input by the user to the user terminal 110 and the mobile terminal 120 .

In operation 1040 , the payment server 170 may transmit the payment result to the processing server 140 as a response to the payment request.

11 is a flowchart of providing a simple payment result according to an exemplary embodiment.

Step 650 may include steps 1110 and 1120 .

In step 1110 , the processing server 140 may transmit a payment completion message to the user terminal 110 and the simple payment app of the mobile terminal 120 .

The payment completion message may include a payment ID. The simple payment app of the user terminal 110 and the mobile terminal 120 that has received the payment completion message confirms that the payment for the transaction between the user terminal 110 and the merchant server 130 is completed through the payment ID of the payment completion message. can

The payment completion message may be a response to the simple payment request in step 750 .

In step 1120 , the processing server 140 may transmit a payment approval message to the affiliate store server 130 .

The payment approval message may include a payment ID and shipping information.

The delivery information may be information indicating an address to which a transaction target will be delivered. For example, the processing server 140 may generate shipping information using member information or a user's address. The address indicated by the delivery information may be an address of the user among member information of the user registered in the communication company server 150 .

The delivery information may include information required to deliver a transaction target to the user, such as the user's name and the user's contact information.

The processing server 140 may perform encryption on the delivery information, and may transmit the encrypted delivery information to the affiliate store server 130 . The affiliated store server 130 may obtain the delivery information by performing decryption on the encrypted delivery information.

When the affiliated store server 130 receives the payment approval message, the affiliated store server 130 may confirm that the payment for the transaction between the user terminal 110 and the affiliated store server 130 has been completed, and the transaction target is sent to the address indicated by the delivery information. You can confirm that you need to ship .

The affiliated store server 130 may specify a transaction between the user terminal 110 and the affiliated store server 130 for which payment has been made using the payment ID.

Through the payment approval message, the transaction can be completed without the merchant server 130 acquiring information about the user for payment from the user terminal 110 and the mobile terminal 120 . In other words, the affiliated store server 130 may only obtain information required for delivery of the transaction object from the processing server 140 , and after the request for the payment page in step 310 and the transmission of the payment page in step 320 , , it may not communicate with the user terminal 110 and the mobile terminal 120 until the payment is completed.

In addition, after the user selects the simple payment service, the transaction can be completed without inputting information other than the user's phone number into the user terminal 110 .

variations of the embodiments

The above-described embodiments may be implemented with modifications and parts omitted. For example, in one embodiment, encryption and decryption of the information described above may be omitted.

Other embodiments are described below.

Installation of easy payment app

In an embodiment, in step 420 , the simple payment app may be installed in another way instead of the installation prompt message.

For example, the payment page transmitted in step 320 may include a link for installing a simple payment app, and in step 330 , the user terminal 110 outputs the link in the payment page. can

For example, the link may be a QR code.

In step 420 , the mobile terminal 120 may recognize the link through the camera of the mobile terminal 120 , and may install an app for simple payment as an operation indicated by the recognized link.

Use of additional information other than phone number to identify you

In the above-described embodiment, the phone number may be used for identification of the user and identification of the mobile terminal 120 . In one embodiment, user identification information may be used in addition to a phone number to identify the user.

User identification information may be additional information for user identification, and it may prevent an incorrect payment request due to an incorrectly entered phone number or an unfair payment request as the user enters someone else's phone number instead of his or her own phone number. It may be information to prevent. In other words, the processing server 140 can use the user identification information to confirm whether the owner of the phone number is a user of the user terminal 110 and the mobile terminal 120 , and can specify the user without error.

For example, the user identification information may include at least a part of the user's name, the user's date of birth, and the user's resident registration.

For example, the user identification information may include the unique identification information of step 510 . Alternatively, the user identification information and the unique identification information may be separate information, and the unique identification information may be information for identifying the mobile terminal 120 .

For example, the simple payment request in steps 350 and 750 may include a phone number and user identification information. In steps 360 and 760 , the processing server 140 may identify the user using the user's phone number and user identification information, and may determine whether the user has subscribed to the simple payment service.

For example, the simple payment service subscription request in step 510 may include a phone number and user identification information. The processing server 140 may identify the user using the phone number and user identification information, and may associate the identified user with the mobile terminal 120 to subscribe to the simple payment service.

User authentication

In addition to the user identification information described above, authentication of the user may be performed through other methods. Here, the authentication for the user may be to check whether the user (or the right holder) of the mobile terminal 120 indicated by the phone number is the same as the user of the user terminal 110 .

In an embodiment, the processing server 140 may measure the distance between the user terminal 110 and the mobile terminal 120 , and when the measured distance is less than or equal to a specified value, the mobile terminal 120 and the user terminal 110 . ) can be determined to be used by the same user.

For example, the simple payment request in step 350 may include user terminal location information indicating the location of the user terminal 110 . The simple payment service subscription request in step 510 may include mobile terminal location information indicated by the location of the mobile terminal 120 . The processing server 140 measures the distance between the user terminal 110 and the mobile terminal 120 using the user terminal location information transmitted from the user terminal 110 and the mobile terminal location information transmitted from the mobile terminal 120 . Also, when the measured distance is less than or equal to a specified value, it may be determined that the mobile terminal 120 and the user terminal 110 are used by the same user. When it is determined that the mobile terminal 120 and the user terminal 110 are used by the same user, the processing server 140 may associate the identified user with the mobile terminal 120 and subscribe to the simple payment service.

For example, the simple payment request in step 750 may include user terminal location information indicating the location of the user terminal 110 . The request for signature information in step 930 may include mobile terminal location information indicated by the location of the mobile terminal 120 . Alternatively, in step 970 , the mobile terminal location information may be transmitted from the mobile terminal 120 to the processing server 140 together with the encrypted signature value. In step 930 or step 975 , the processing server 140 uses the user terminal location information transmitted from the user terminal 110 and the mobile terminal location information transmitted from the mobile terminal 120 to the user terminal 110 . and a distance between the mobile terminals 120 may be measured, and when the measured distance is less than or equal to a specified value, it may be determined that the mobile terminal 120 and the user terminal 110 are used by the same user. When it is determined that the mobile terminal 120 and the user terminal 110 are used by the same user, the processing server 140 may continue the simple payment service for the user.

Verification of user using authentication information

In one embodiment, authentication information may be verified for the user. The authentication information may be information used to authenticate or verify a user.

For example, the verification of the user using the authentication information may be performed when the measured distance is not confirmed to be less than or equal to the specified distance.

For example, after step 510 , step 930 , or step 975 , the processing server 140 may transmit authentication information to the user terminal 110 .

For example, the authentication information may be a QR code, a numeric string, or a numeric string.

The user terminal 110 may output authentication information, and the simple payment app of the mobile terminal 120 may generate verification information for the authentication information by photographing the output authentication information by the user's manipulation. Alternatively, authentication information such as a numeric string and a numeric string may be input to the simple payment app of the mobile terminal 120 by the user of the user terminal 110, and the mobile terminal 120 receives the user's input after confirming the authentication information. can be used to generate verification information.

The mobile terminal 120 may transmit the verification information to the processing server 140 . The processing server 140 may determine that the mobile terminal 120 and the user terminal 110 are used by the same user if the verification information from the mobile terminal 120 is the same as the authentication information transmitted from the processing server 140 . .

Transactions using the mobile terminal 120

As described above, the user terminal 110 and the mobile terminal 120 may be physically one user terminal 110 . In other words, the user may perform a transaction with the affiliate store server 130 using the mobile terminal 120 .

In this case, the above-described interaction between the user terminal 110 , the mobile terminal 120 , and the processing server 130 may be further simplified.

For example, after step 730, the web browser of the mobile terminal 120 that outputs the payment page may transmit purchase information to the simple payment app, and the simple payment app may be performed by transmitting the purchase information. have. The purchase information may be transmitted using a URL scheme.

The simple payment app may automatically call a phone number registered in the USIM, and may transmit a simple payment request including a phone number and purchase information to the processing server 140 in step 750 .

In this case, input of a phone number by the user may also be omitted, and the transaction may be completed only by touching the touch display without input of any numeric character string.

Features related to the processing of information in the embodiment

1) As explicitly described in the above embodiment, one of the features of the present invention is to simplify the process of simple payment and reduce errors by minimizing the input from the user.

For example, input from the user to the user terminal 110 and the mobile terminal 120 to use the simple payment service is 1) an input of selection of a simple payment service, 2) an input for installation of a simple payment app 3) a phone call It may be limited to all or part of input of a number and 4) input of unlocking.

Considering that the above-mentioned 1) input of selection of simple payment service, 2) input for installation of simple payment app, and 4) input of unlocking are input through mouse click and touch display, The number string inputted to one of the user terminal 110 and the mobile terminal 120 by 2) may be only a phone number.

According to an embodiment, in addition to 2) a phone number, 4) a PIN and password for unlocking, or user identification information for user identification may be input by the user as a numeric character string. Such input may be selective, and may be replaced by actions such as touch and drag on the touch display.

The input of such information allows the user to use the simple payment service by simple manipulation without using a keyboard output on the touch display, or the like.

In addition, by using the function of the web browser of the user terminal 110 , the phone number previously cached on the payment page output in step 320 may be automatically input to the GUI object to which the phone number is to be input. In this case, input of a phone number by the user may also be omitted, and the transaction may be completed only by touching the touch display without input of any numeric character string.

2) Also, one of the features of the present invention is that information used for simple payment is provided to only a small number of possible entities of the simple payment system. Here, the objects of the simple payment system are the user terminal 110 , the mobile terminal 120 , the affiliated store server 130 , the processing server 140 , the communication company server 150 , the authentication server 160 , and the payment server 170 . can mean

According to this feature, it can be understood that the information described to be transmitted between specific entities of the simple payment system in the embodiment is not transmitted and not used by other entities of the simple payment system other than the specified specified entities above. have.

For example, the purchase information included in the simple payment request in steps 350 and 750 is originally related to the user terminal 110 , the mobile terminal 120 , the affiliate store server 130 , and is processed. It is used only in the server 140 and the payment server 170 , and may not be transmitted to the communication company server 150 and the authentication server 160 .

For example, member information provided by the communication company server 150 in steps 530 and 820 may not be transmitted to the user terminal 110 , the authentication server 160 , and the payment server 170 .

For example, among the member information provided by the communication company server 150 in steps 530 and 820 , information other than information required for delivery of a transaction target is the user terminal 110 and the affiliated store server 130 . , may not be transmitted to the communication company server 150 , the authentication server 160 , and the payment server 170 . That is, information other than information used to generate delivery information among member information may not be transmitted to the user terminal 110 , the affiliate store server 130 , the authentication server 160 , and the payment server 170 .

For example, payment information provided by the communication company server 150 in steps 530 and 820 is sent to the user terminal 110 , the mobile terminal 120 , the affiliate store server 130 and the authentication server 160 . may not be transmitted.

According to an embodiment, payment information may be transmitted to the mobile terminal 120 in order for the user to check the details of payment before payment authentication.

More specifically, information on a credit card for payment and information on a bank account for payment may not be transmitted to the user terminal 110 , the mobile terminal 120 , the merchant server 130 , and the authentication server 160 . have.

According to an embodiment, information about a credit card or information about a bank account may be transmitted to the mobile terminal 120 in order for the user to check the details of payment before payment authentication.

Due to the restrictions on the transmission and use of information as described above, leakage of personal information is prevented, and more secure transactions can be made.

In particular, the restriction of such information may be strongly imposed on the affiliated store server 130 . The transaction between the user terminal 110 and the affiliated store server 130 may be completed without the affiliated store server 130 acquiring information about the user for payment from the user terminal 110 and the mobile terminal 120 .

In step 320 , after the merchant server 130 transmits the payment page to the user terminal 110 , the information obtained by the merchant server 130 is only the payment transmitted from the processing server 140 in step 840 . ID and transaction information, and the payment ID and delivery information transmitted from the processing server 140 in step 1120 may be limited. In addition, transaction information may be omitted from transmission.

By limiting the transmission of information to the affiliate store server 130, it is possible to prevent leakage of important personal information, such as information about a user's credit card or bank account, from the simple payment system.

Also, in the embodiment, member information is extracted from the telecommunication company server 150 . Accordingly, the member information and/or information generated based on the member information is the user terminal 110 , the mobile terminal 120 , the affiliated store server 130 , the processing server 140 , the authentication server 160 , and/or the payment server Even if transmitted to 170, such member information and information generated based on member information are only used until the transaction is completed, and after the transaction is completed, the user terminal 110, the mobile terminal 120, the affiliated store server 130, and processing It may be deleted without being stored in the server 140 , the authentication server 160 , and/or the payment server 170 .

In another embodiment, since frequent transmission of member information may be a burden on the telecommunication company server 150 , member information and/or a portion of information generated based on member information may be stored in the processing server 140 even after the transaction is completed. It can be stored and reused for other transactions. For example, some of the information stored in the processing server 140 may include member information and payment information.

3) In addition, one of the features of the present invention is that in the communication of information between terminals and servers of the simple payment system, one of both ends of the communication is the processing server 140 .

That is to say, in the embodiment described above, the steps in which both ends of the communication are not the processing server 140 may be only the request of the payment page and the transmission of the payment page in the initial steps 310 and 320 .

That is, 1) in step 310, after the user terminal 320 receives the payment page, 2) after simple payment is selected in step 320, 3) a phone number is provided to the user terminal 110 by the user After input or 4) after the simple payment request including the phone number is transmitted from the user terminal 110 to the processing server 140, the processing server 140 is excluded from among the entities of the simple transaction system Direct communication may not be performed between the user terminal 110 , the mobile terminal 120 , the affiliated store server 130 , the communication company server 150 , the authentication server 160 , and the payment server 170 which are entities of . In other words, among the entities of the simple transaction system, the remaining entities excluding the processing server 140 , the user terminal 110 , the mobile terminal 120 , the affiliated store server 130 , the telecommunication company server 150 , and the authentication server 160 . and each of the payment servers 170 may only communicate with the processing server 140 .

In addition, in the entire steps of simple payment by the simple payment system, the user terminal 110 , the mobile terminal 120 , the communication company server 150 , the authentication server 160 and the payment server 170 do not communicate directly. may not be In addition, the mobile terminal 120 , the affiliated store server 130 , the communication company server 150 , the authentication server 160 , and the payment server 170 may not communicate directly.

Interface for embodiment

The interface used in the steps of the above-described embodiment is described below. The interface may be output from the user terminal 110 or the mobile terminal 120 . It can be understood that the contents described in the interface with characters, figures, and pictures are applied to the above-described embodiments.

As described above, a user may purchase a product using the mobile terminal 120 . 12 to 18 below may be interfaces output from the mobile terminal 120 when the user terminal 110 and the mobile terminal 120 are the same.

12 illustrates a product selection screen according to an example.

The product selection screen of FIG. 12 may be an interface for selecting a product, which is a target of a transaction, output from the mobile terminal 120 before the request of the payment page of step 310 .

13 illustrates a simple payment screen according to an example.

The simple payment screen of FIG. 13 may be a payment page output from the mobile terminal 120 in steps 330 and 340 , and may be an interface in which simple payment is selected and a phone number is input.

14 illustrates a payment waiting screen according to an example.

The payment waiting screen of FIG. 14 may be an interface output from the mobile terminal 120 while waiting for payment after step 350 is performed and before step 1110 is performed.

15 shows a user authentication screen according to an example.

The user authentication screen of FIG. 15 may be a lock release interface output from the mobile terminal 120 in step 920 .

16 illustrates a payment information confirmation screen according to an example.

The payment information confirmation screen of FIG. 16 may be an interface through which payment information output from the mobile terminal 120 is provided and payment approval is obtained in steps 955 and 960 .

17 illustrates a payment completion screen according to an example.

The payment completion screen of FIG. 17 may be an interface indicating completion of payment output from the mobile terminal 120 in step 1110 .

18 illustrates an order completion screen according to an example.

The order completion screen of FIG. 18 may be an interface indicating completion of payment output from the mobile terminal 120 in step 1110 .

19 to 26 below may be interfaces output from one of the user terminal 110 and the mobile terminal 120 when the user terminal 110 and the mobile terminal 120 are different from each other.

19 illustrates a product selection screen according to an example.

The product selection screen of FIG. 19 may be an interface for selecting a product, which is a target of a transaction, output from the user terminal 110 before the request of the payment page of step 310 .

20 illustrates a simple payment screen according to an example.

The simple payment screen of FIG. 20 may be a payment page output from the user terminal 110 in steps 330 and 340 , and may be an interface in which simple payment is selected and a phone number is input.

21 illustrates a payment waiting screen according to an example.

The payment waiting screen of FIG. 21 may be an interface output from the user terminal 110 while waiting for payment after step 350 is performed and before step 1110 is performed.

22 illustrates a payment request screen according to an example.

The payment request screen of FIG. 22 may be an interface notifying a request for payment approval for simple payment output from the mobile terminal 120 in step 915 .

23 shows a user authentication screen according to an example.

The user authentication screen of FIG. 23 may be a lock release interface output from the mobile terminal 120 in step 920 .

24 shows a payment information confirmation screen according to an example.

The payment information confirmation screen of FIG. 24 may be an interface through which payment information output from the mobile terminal 120 is provided and payment approval is obtained in steps 955 and 960 .

25 shows a payment completion screen according to an example.

The payment completion screen of FIG. 25 may be an interface indicating completion of payment output from the mobile terminal 120 in step 1110 .

26 shows an order completion screen according to an example.

The order completion screen of FIG. 26 may be an interface indicating completion of payment output from the user terminal 110 in step 1110 .

27 to 29 below may be an interface output from the mobile terminal 120 when a simple payment app is installed.

27 shows an installation screen of a simple payment app according to an example.

The installation screen of the simple payment app of FIG. 27 may be an interface output to install the simple payment app in the mobile terminal 120 in step 420 .

28 shows an execution screen of a simple payment app according to an example.

The execution screen of the simple payment app of FIG. 28 may be an interface output while the simple payment app is executed after the simple payment app is installed in the mobile terminal 120 in step 420 .

29 shows the agreement agreement screen of the simple payment app according to an example.

The agreement agreement screen of the simple payment app of FIG. 29 may be an interface output to obtain agreement on the terms of use from the user in the mobile terminal 120 in step 430 .

The device described above may be implemented as a hardware component, a software component, and/or a combination of the hardware component and the software component. For example, devices and components described in the embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), It may be implemented using one or more general purpose or special purpose computers, such as a programmable logic unit (PLU), microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For convenience of understanding, although one processing device is sometimes described as being used, one of ordinary skill in the art will recognize that the processing device includes a plurality of processing elements and/or a plurality of types of processing elements. It can be seen that can include For example, the processing device may include a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as parallel processors.

Software may comprise a computer program, code, instructions, or a combination of one or more thereof, which configures a processing device to operate as desired or is independently or collectively processed You can command the device. The software and/or data may be any kind of machine, component, physical device, virtual equipment, computer storage medium or device, to be interpreted by or to provide instructions or data to the processing device. , or may be permanently or temporarily embody in a transmitted signal wave. The software may be distributed over networked computer systems, and stored or executed in a distributed manner. Software and data may be stored in one or more computer-readable recording media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium.

The computer-readable recording medium may contain information used in the embodiments according to the present invention. For example, the computer-readable recording medium may include a bitstream, and the bitstream may include the information described in the embodiments according to the present invention.

The computer-readable recording medium may include a non-transitory computer-readable medium.

The computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the medium may be specially designed and configured for the embodiment, or may be known and available to those skilled in the art of computer software. Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks and magnetic tapes, optical recording media such as CD-ROMs and DVDs, and magnetic media such as floppy disks. - includes magneto-optical media, and hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

As described above, although the embodiments have been described with reference to the limited embodiments and drawings, various modifications and variations are possible from the above description by those skilled in the art. For example, the described techniques are performed in an order different from the described method, and/or the described components of the system, structure, apparatus, circuit, etc. are combined or combined in a different form than the described method, or other components Or substituted or substituted by equivalents may achieve an appropriate result.

The apparatus described in the embodiment may include one or more processors and may include a memory. The memory may store one or more programs to be executed by one or more processors. One or more programs may perform the operation of the device described in the embodiment. For example, one or more programs on the device may perform an operation described in a device-related one of the steps described above. In other words, the operation of the device described in the embodiment may be executed by one or more programs. The one or more programs may include programs, applications, and apps of the device described above in the embodiment. For example, one of the one or more programs may correspond to a program, an application, and an app of the device described above in an embodiment.

110: user terminal
120: mobile terminal
130: Merchant Server
140: processing server
150: carrier server
160: authentication server
170: payment server

Claims (18)

In the payment system,
processing server
including,
The processing server receives the phone number of the user's mobile terminal from the user's user terminal,
The processing server obtains member information of the user registered in the communication company server from a communication company server of a communication company that provides a communication service to the mobile terminal by using the phone number,
A payment system for performing a payment for a transaction between the user terminal and an affiliated store server using the member information. According to claim 1,
The processing server transmits the payment request to the payment server by using the payment information provided from the communication company server, and receives the payment result from the payment server. 3. The method of claim 2,
wherein the payment information is information about payment of automatic bill payment registered with respect to the phone number of the user. 3. The method of claim 2,
The payment information is not transmitted to the merchant server and the user terminal, payment system. According to claim 1,
After the processing server receives the phone number of the mobile terminal of the user from the user terminal of the user, direct communication is not performed between the user terminal, the mobile terminal, the affiliated store server, and the communication company server. system. According to claim 1,
After the processing server receives the phone number of the mobile terminal of the user from the user terminal of the user,
Each of the user terminal, the mobile terminal, the affiliated store server and the communication company server communicates only with the processing server. According to claim 1,
The number string input by the user to one of the user terminal and the mobile terminal for the payment is only the phone number. According to claim 1,
The information on the credit card for the payment and the information on the bank account for the payment are not transmitted to the user terminal and the mobile terminal, the payment system. According to claim 1,
The communication company server provides information about a credit card or bank account for the payment to the processing server,
and the processing server performs the payment using information about a credit card or bank account for the payment. According to claim 1,
The processing server requests the payment to the telecommunication company server or an automatic bill payment server that processes automatic bill payment for the phone number,
The payment system, wherein the payment is performed by the communication company server or the automatic bill payment server. 11. The method of claim 10,
As the payment is performed by the telecommunication company server or the automatic bill payment server, a payment system in which the payment for the transaction is performed without a request for the payment to a credit card company or a bank that handles payment of the charge to the phone number . 11. The method of claim 10,
The payment system, wherein the transaction is completed without the merchant server acquiring information about the user for the payment from the user terminal and the mobile terminal. one or more processors; and
memory storing one or more programs executed by the one or more processors
including,
the one or more programs
Receive a phone number of the user's mobile terminal from the user's user terminal,
Obtaining member information of the user registered in the communication company server from a communication company server of a communication company that provides a communication service to the mobile terminal by using the phone number,
A processing server for performing a payment for a transaction between the user terminal and the affiliated store server using the member information. In the mobile terminal,
one or more processors; and
memory storing one or more programs executed by the one or more processors
including,
the one or more programs
Receiving a request for payment approval for a transaction between the user terminal and the affiliated store server from the processing server receiving the phone number of the mobile terminal,
The mobile terminal performs the payment approval, and transmits a result of the payment approval to the processing server. 15. The method of claim 14,
wherein the payment is performed by a specific payment server using the information on the payment of automatic bill payment registered for the phone number by the processing server. 15. The method of claim 14,
The mobile terminal and the user terminal do not communicate directly. 15. The method of claim 14,
wherein the user terminal and the mobile terminal are the same device. In the payment system,
user terminal; and
mobile terminal
including,
The user terminal transmits a request for payment for a transaction between the user terminal and the affiliated store server to a processing server, and the payment request includes a phone number of the mobile device input by the user of the shopping mall user terminal,
The mobile terminal receives a request for payment approval for the transaction between the user terminal and the affiliated store server from the processing server, performs the payment approval, and transmits a result of the payment approval to the processing server. .

Images