KR20140131838A - Method and mobile device for paying using transaction id, and payment server - Google Patents

Abstract

A payment processing method of a payment server includes the steps of: receiving a first payment request message from a content providing server; generating a transaction ID corresponding to the received first payment request message; transmitting a first payment response message including the transaction ID to the content providing server, as the transaction ID is delivered to a mobile device from the content providing server; receiving a second payment request message including the transaction ID and authentication information from the mobile device; performing a payment process on the basis of the transaction ID and the authentication information; generating a second payment response message including execution result of a payment processor; and transmitting the second payment response message to the content providing server, as the execution result is delivered to the mobile device from the content providing server.

Description

METHOD AND MOBILE DEVICE FOR PAYING USING TRANSACTION ID, AND PAYMENT SERVER USING TRANSACTION ID,

A payment method using a transaction ID, a mobile device, and a payment server.

Currently, domestic phone bill is available in mobile phone application based service that can directly access mobile phone device and USIM (Universal Subscriber Identity Module). In mobile browser, it is possible to make micro payment through PG (Payment Gateway) company. In this case, the user must input the mobile phone number and mobile phone SMS authentication number in the micro payment through PG company.

On the other hand, the credit card payment method that accounts for most of the electronic e-commerce settlement adopts an online authentication method such as an ISP, a secure click, and requires the installation of Active X (Active X). However, since there is a limitation in installing Active AX on a mobile terminal, it is difficult to apply the online authentication method used in the existing Internet electronic commerce payment to the mobile terminal as it is.

In connection with the payment system using a mobile terminal, Korean Patent Publication No. 2012-0075568 discloses a method for authenticating a user and a terminal based on an e-mail address of a purchaser, a user ID, a home telephone number, Is disclosed.

A mobile device and a payment server capable of performing an authentication process without a separate user authentication process by transferring a transaction ID issued by a payment server to a mobile device and performing settlement based on the transferred transaction ID. The present invention also provides a payment method, a mobile device, and a payment server capable of providing mobile payment with a simple process through interlocking of a mobile web browser and a payment application. Also, a payment method, a mobile device, and a payment server capable of secure payment without inputting separate user authentication information are provided. It is to be understood, however, that the technical scope of the present invention is not limited to the above-described technical problems, and other technical problems may exist.

As a technical means for achieving at least one of the above-mentioned technical problems, an embodiment of the present invention includes a step of receiving a first payment request message from a content providing server, a transaction corresponding to a received first payment request message Generating a transaction ID and a transaction ID from the mobile device; and transmitting a transaction ID and a transaction ID from the mobile device to the content providing server, wherein the transaction ID is transmitted from the content providing server to the mobile device, Receiving a second payment request message including a transaction ID and authentication information, performing a payment process based on the transaction ID and the authentication information, generating a second payment response message including a result of execution of the payment processor, To the content providing server, And a step of delivering the content from the content providing server to the mobile device.

In another embodiment of the present invention, there is provided a content providing server including a first message receiving unit for receiving a first payment request message from a content providing server, a generating unit for generating a transaction ID corresponding to the received first payment request message, 1 transmission request message to the content providing server, the transaction ID is transmitted to the mobile device by the transmitting unit and the content providing server, and the second message is received from the mobile device, And a payment execution unit for performing a payment process based on the reception unit, the transaction ID, and the authentication information, wherein the generation unit generates a second payment response message including a result of execution of the payment processor, Server, the result is that the content It can provide a billing server that delivers balls from the server to the mobile device.

According to another embodiment of the present invention, there is provided a mobile terminal including a display unit for displaying contents through an execution screen of a first application running on a mobile device, a first payment request message A first transmission unit for transmitting a transaction ID from the content providing server to the mobile terminal, and a first payment response message including a transaction ID from the content providing server, wherein the transaction ID is generated by a payment server, A second transmission unit for transmitting a second payment request message including information to the payment server, a second payment response message including a payment execution result from the content providing server, And a second receiving unit, which is a second receiving unit.

According to any one of the above-mentioned objects of the present invention, the transaction ID issued by the payment server is transferred to the mobile device, and the settlement is performed based on the transferred transaction ID, so that the authentication process can be performed without a separate user authentication process . In addition, mobile payment can be provided by a simple process through interworking of a mobile web browser and a payment application. Further, it is possible to provide a safe mobile device payment method by preventing the leakage of personal information without requiring separate user authentication information input. In addition, by automatically acquiring various authentication information of the mobile device through the payment application, it is possible to provide improved user convenience.

1 is a configuration diagram of a mobile device settlement system according to an embodiment of the present invention.
2 is a configuration diagram of a payment server 30 according to an embodiment of the present invention.
3A is a configuration diagram of a generator 32 according to an embodiment of the present invention.
FIG. 3B is a configuration diagram of the settlement unit 35 according to an embodiment of the present invention.
4 is a configuration diagram of a mobile device 10 according to an embodiment of the present invention.
5 is a configuration diagram of a transaction ID according to an embodiment of the present invention.
6 is a flowchart illustrating a payment method according to an embodiment of the present invention.
7 is a flowchart illustrating a process of authenticating the content providing server 20.
FIG. 8 is a flowchart for explaining the process of authenticating the mobile device 10. FIG.
9A to 9B are flowcharts illustrating a payment method according to an embodiment of the present invention.
10 is a flowchart illustrating a payment method according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, which will be readily apparent to those skilled in the art. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

Throughout the specification, when a part is referred to as being "connected" to another part, it includes not only "directly connected" but also "electrically connected" with another part in between . Also, when an element is referred to as "comprising ", it means that it can include other elements as well, without departing from the other elements unless specifically stated otherwise.

1 is a configuration diagram of a mobile device settlement system according to an embodiment of the present invention. Referring to FIG. 1, the mobile device payment system includes a mobile device 10, a content providing server 20, and a payment server 30. However, the configuration of the mobile device settlement system is not limited to those shown in FIG. 1, and configurations other than the configuration of FIG. 1 may be further included in the mobile device settlement system.

The components of FIG. 1 that constitute the mobile device payment system are connected through a wireless network. For example, as shown in FIG. 1, the mobile device 10 is connected to a content providing server 20 and a payment server 30 via a wireless network. Generally, a wireless network refers to a connection structure in which information can be exchanged between each node such as a terminal and a server. An example of such a wireless network includes a wireless LAN (WLAN), a Wi-Fi, broadband, Bluetooth network, LTE (Long Term Evolution) network, Wimax (World Interoperability for Microwave Access), HSDPA (High Speed Downlink Packet Access), and the like.

Referring to FIG. 1, when a payment request for purchased content is received from a user, the mobile device 10 attempts a payment request to the content providing server 20. At this time, the payment request can be made through the wireless network based on the message exchange protocol. An example of a message exchange protocol may be HTTPS (Hypertext Transfer Protocol over Secure Socket Layer)

The mobile device 10 purchases the content through the Internet shopping mall and requests payment of the content purchase amount. In addition, the mobile device 10 purchases one or more services provided from the web and requests payment of the service use fee. At this time, the mobile device 10 may be provided with a web browser for purchasing contents or services.

The mobile device 10 may include a separate billing application for performing the payment process. The payment application performs a payment process in cooperation with the payment server 30. When the payment application is downloaded to the mobile device 10, the serial number and the serial number issue date of the payment application are encrypted and stored in the mobile device 10 have.

The payment application can collect various kinds of information of the mobile device 10. [ At this time, various kinds of information may mean information necessary for the payment process. An example of such various information is at least one of a cellular telephone number (CTN) stored in the mobile device 10, an International Mobile Equipment Identity (IMEI), an International Mobile Station Identity (IMSI), and an Integrated Circuit Card Identifier (ICCID).

One example of the mobile device 10 is a Personal Communication System (PCS), a Global System for Mobile communication (GSM), a Personal Digital Cellular (PDC), a Personal Handyphone System (PHS), a Personal Digital Assistant (PDA) 2,000, Code Division Multiple Access (CDMA) -2000, W-CDMA (W-CDMA), Wibro (Wireless Broadband Internet) terminals, smartphones, smartpads, But may not be construed as limited to such an example, although it may include any type of handheld based wireless communication device.

The content providing server 20 provides the content to the mobile device 10. Such contents include goods, music, movies, services, and the like. For example, the content providing server 20 may operate the Internet shopping mall and provide the Internet shopping mall service to the mobile device 10 to purchase the content. The content providing server 20 can transmit and receive a payment request and a response message for content requested to be purchased from the mobile device 10 to and from the payment server 30. [ At this time, the payment request message may include the identification number of the mobile device 10 and purchase information.

The content providing server 20 may encrypt or decrypt a message input to the content providing server 20 or a message output from the content providing server 30. [ One example of a message is a payment request message and a payment response message.

The payment server 30 performs settlement of the content requested to be purchased by the mobile device 10. [ For this purpose, the payment server 30 can authenticate the mobile device 10, the content providing server 20, and the like. The payment server 30 may exist in the mobile device payment system, but may exist separately in the external system that provides the payment service.

The payment server 30 generates a transaction ID which is a payment authorization key corresponding to the payment request of the mobile device 10. [ In addition, the payment server 30 can provide the generated transaction ID to the mobile device 10 via the content providing server 20. This transaction ID is used for the settlement process between the mobile device 10 and the payment server 30. [ The payment server 30 authenticates whether the mobile device 10 is a legitimate user or a user device based on the transaction ID and the authentication information received from the mobile device 10 and then performs a payment process for the payment request of the mobile device 10 can do.

The transaction ID can be SSL encrypted. Here, SSL encryption is an authentication encryption for securely sending and receiving data between a web browser and a web server, and has a function of verifying the identity of each other between a web browser and a web server.

The mobile device 10, the content providing server 20 and the payment server 30 will be described in more detail with reference to the drawings.

2 is a configuration diagram of a payment server 30 according to an embodiment of the present invention. 2, the payment server 30 includes a first message receiving unit 31, a generating unit 32, a transmitting unit 33, a second message receiving unit 34, and a payment performing unit 35. However, it should be understood by those skilled in the art that various modifications may be made based on the components shown in FIG. 2, which are well known to those skilled in the art.

The first message receiving unit 31 may receive the first payment request message from the content providing server. Here, the first payment request message is generated in response to the first payment request transmitted from the first application of the mobile device 10 to the content providing server 20 by the content providing server 20, The message may include the identity of the mobile device 10 and the payment information of the mobile device 10. [ Here, the first settlement request message may include a correlation ID. CorrelationID is a unique value used in the future for cancellation of payment, confirmation of purchase, etc. The payment information may include at least one of an IP address, order number, shop identification number, user identification number, product identification number, payment amount, VAT information, terminal model name, and RS rate of the mobile device, Lt; / RTI > The ID of the mobile device 10 may be a joining ID of the web page. For example, the ID of the mobile device 10 may be "Auction ID on the auction homepage" or "Next ID on the next homepage ".

The generating unit 32 may generate a transaction ID corresponding to the received first payment request message. At this time, the first payment request message may include a request for determining the authentication method of the mobile device. The authentication method of the mobile device can be changed according to the payment amount of the user and the configuration of the purchased contents. For example, the generating unit 32 may determine an authentication method of the mobile device and generate a different type of authentication key in addition to the transaction ID according to the determined authentication method. Here, the authentication key includes AppSecurityNumber requesting confirmation of the app serial number of the payment application 50 installed in the mobile device 10, open one time password requesting input of the mobile device user in the payment application 50 of the mobile device 10 , It may be a password preset by the customer. The AppSecurityNumber is composed of a randomly selected 4-digit position number among 16 position values and can be transmitted and received between the payment application and the payment server of the mobile device. The open one time password may be an authentication key for allowing the user to view and input the open one time password exposed in the mobile payment application during the payment authentication step with the 4-digit authentication key generated at the payment server 30 at random.

As another example, the generating unit 32 can generate an authentication key whose authentication validity time is set to be different. The authentication key may be S_ProvID of the content providing server 20, S_TokenID of the content providing server 20, C_ProvID of the second application, AppSecurityNumber of the second application, C_TokenID of the second application, and CouponID of the second application. Here, the C_ProvID of the second application may be transmitted / received between the payment server and the mobile device when the C_ProvID or the C_TokenID of the second application is authenticated from the payment server 30, and otherwise may be stored in the payment application of the mobile device. The AppSecurityNumber of the second application and the C_TokenID of the second application may be used for purchase authentication of the mobile device. The AppSecurityNumber of the second application may be transmitted and received between the payment server and the mobile device when purchasing the mobile device.

5 is a configuration diagram of a transaction ID according to an embodiment of the present invention. Referring to FIG. 5, a communication company classification 51, a shop classification 52, a time stamp 53, a req ID 54, a Succ / Fail flag 55, a correlation random number 56, 57). At this time, the time stamp 53 may mean the authentication expiration time of the transaction ID. In addition, the req ID 54 may mean a settlement request identification number. The Succ / Fail flag 55 may indicate a payment success or failure flag based on the settlement result. In addition, the correlation random number 56 may be a random number. In addition, the app serial number check 57 may mean a confirmation field or AppSecurityNumber for authenticating the app serial number of the payment application.

 It will be understood by those skilled in the art that various modifications may be made based on the components shown in FIG. 5, which are well known to those skilled in the art.

3A is a configuration diagram of a generator 32 according to an embodiment of the present invention. 3A, the generating unit 32 includes an extracting unit 321, an identifying unit 322, a managing unit 323, and a time setting unit 324. However, it should be understood by those skilled in the art that various modifications may be made based on the constituent elements shown in FIG. 3A.

The extracting unit 321 may extract the transaction ID and authentication information from the ID of the mobile device 10 and the received second payment request message from the received first payment request message. Here, the authentication information may be an International Mobile Equipment Identity (IMEI) information stored in the mobile device, an International Mobile Station Identity (IMSI) information, an IP address of the mobile device, and some or all of the app serial number of the second application or AppSecurityNumber have. Such authentication information is information automatically obtained from the payment application of the mobile device.

The S_ProvID of the content providing server 20, the S_TokenID of the content providing server 20, the C_ProvID of the second application, the AppSecurityNumber of the second application, the C_TokenID of the second application, and the CouponID of the second application may be included in the second payment request message have. For example, upon receiving the encrypted first payment request message or the second payment request message, the extracting unit 321 decrypts the first payment request message or the second payment request message by applying an encryption algorithm, The ID of the mobile device, the transaction ID, and the authentication information can be extracted. In this case, the encryption algorithm may be ARIA, SEED, AES, 3DES, which are bidirectional encryption algorithms, and SHA and HAS, which are unidirectional encryption algorithms.

As another example, the extracting unit 321 may extract the C_TokenID of the second application whose authentication expiration time has elapsed from the second settlement request message.

The confirmation unit 322 can confirm the communication company of the mobile device 10 based on the extracted ID of the mobile device. Or the authentication key generated based on the authentication time is checked to see if the authentication time has expired, and then the authentication key is generated for the expired authentication key. For example, if the C_TokenID of the second application whose authentication expiration time has elapsed is confirmed, the creator 32 can request the authentication key re-issuance. At this time, the authentication key may be a C_TokenID and a CouponID of the second application.

The management unit 323 can manage the generated transaction ID in response to the received first payment request message. Further, the authentication key generated based on the authentication time can be managed. Here, the authentication key may be S_ProvID of the content providing server 20, S_TokenID of the content providing server 20, C_ProvID of the second application, AppSecurityNumber of the second application, C_TokenID of the second application, and CouponID of the second application.

The time setting unit 324 may set an authentication expiration time for the transaction ID transmitted to the content providing server 20. [ The authentication expiration time of an authentication key, such as a transaction ID, can be set using the Multi Time Length Window Sliding technique. The Multi-Time Length Window Sliding scheme helps secure settlement by setting the authentication expiration time in order of importance of the authentication key for the authentication of the content providing server 20 and the mobile device 30. For example, the Multi-Time Length Window Sliding technique may be configured such that the S_ProvID authentication expiration time of the content providing server 20 is 28 days, the S_TokenID authentication expiration time of the content providing server 20 is 14 days, the C_ProvID authentication expiration time of the second application is 7 days, the authentication expiration time of the AppSecurityNumber of the second application is 7 days, the C_TokenID authentication expiration time of the second application is 12 hours, the CouponID authentication expiration time of the second application is 12 hours, and the authentication expiration time of the transaction ID is 60 seconds The expiration time is set to a differential value.

The transmitting unit 33 may transmit a first payment response message including a transaction ID to the content providing server.

The second message receiver 34 may receive the second payment request message. At this time, the second settlement request message includes the transaction ID and the authentication information. As described above, the transaction ID may be transmitted to the web browser of the mobile device 10 through the first settlement response message.

The settlement performing unit 35 can perform the settlement process through interlocking with the external server based on the settlement information, the transaction ID, and the authentication information. Here, the external server may be a carrier billing infrastructure server that supervises the payment service of the mobile device. The settlement performing unit 35 can perform settlement when the mobile device authentication passes. Such mobile device authentication may be authentication for device authentication, user authentication, IP address authentication, and TokenID of the mobile device. The settlement performing unit 35 can perform settlement when the IP address of the mobile terminal is the 3G or LTE network. The settlement performing unit 35 may perform settlement only when it has passed the settlement limit management system.

FIG. 3B is a configuration diagram of the settlement unit 35 according to an embodiment of the present invention. 3B, the settlement execution unit 35 includes an ID determination unit 351, an authentication time determination unit 352, an execution unit 353, and a verification unit 354. [ However, it should be understood by those skilled in the art that various modifications may be made based on the constituent elements shown in FIG. 3B.

The ID determination unit 351 can determine whether the transaction ID included in the second settlement request message matches the transaction ID included in the first settlement response message.

The authentication time determination unit 352 determines whether the transaction ID included in the second settlement request message is received within the authentication expiration time. And transmits a determination result message to the transmission unit 33. For example, if the Time Stamp field 53 of the transaction ID is 60 seconds, the authentication time determination unit 352 determines whether the transaction ID included in the second settlement request message is received from the mobile device within 60 seconds. If the received time of the received transaction ID exceeds 60 seconds, the authentication time determination unit 352 informs the transfer unit 33 of the result of the failed transaction ID authentication.

The verification unit 354 can verify the app serial number of the authentication information received from the mobile device. For example, the verification unit 354 may verify the validity of the mobile device by comparing the app serial number check field 2 4 5 value of the transmitted transaction ID with the app serial number position value of the payment application.

The execution unit 353 can perform the settlement process based on the verification result of whether or not the transaction ID is matched, whether the result is received within the authentication expiration time, and the app serial number of the authentication information received from the mobile device.

The generating unit 32 may generate a second payment response message including a result of the payment processor.

The transmitting unit 33 transmits a second payment response message to the content providing server 20 and the result of the payment processor can be transmitted from the content providing server 20 to the mobile device 10. For example, 2 The payment response message may be a message including a payment request number, a transaction ID, a payment success or failure, and an order number.

4 is a configuration diagram of a mobile device 10 according to an embodiment of the present invention. 4, the mobile device 10 includes a display unit 11, a first transmitting unit 12, a first receiving unit 13, a second transmitting unit 14, and a second receiving unit 15. It should be understood, however, that various modifications may be made based on the components shown in FIG. 4, by those skilled in the art to which the embodiments of the present invention belong.

The display unit 11 may display the content on the execution screen of the first application running on the mobile device 10. [ The display unit 11 may display the goods to the mobile device user through the mobile web browser running on the mobile device 10. [ Also, the display unit 11 can receive a user's input through a user interface. For example, the display unit 11 may receive a user input for a product displayed through a touch input interface. When the user first accesses the payment application of the mobile device, the display unit 11 may receive the user's resident number, settlement agreement, and payment password.

The first transmitting unit 12 may transmit the first payment request message to the content providing server 20 when a payment request for the content is inputted through the user interface.

Here, the first payment request message may be generated by the first application. The first payment request message may be transmitted to the content providing server 20 based on the HTTP protocol.

The first receiving unit 13 receives a first payment response message including a transaction ID from the content providing server 20, and the transaction ID can be generated by the payment server. Here, the transaction ID can be transferred from the first application to the second application based on the URL SCHEME technique. The first application may be a web browser and the second application may be a payment application directly connected to a payment server.

URL SCHEME is a way to enable interoperability between mobile applications on mobile devices with Android or iOS, which can deliver values to application execution and applications. However, the transaction ID may not be transmitted to the payment application if the mobile device IP address network is captured as WiFi. In this case, the web browser of the mobile device can be moved to the mobile phone settlement unavailable web page.

The second transmission unit 14 may transmit a second payment request message including the received transaction ID and the authentication information of the mobile device 10 to the payment server 30. [

Here, the second payment request message may be generated by the second application installed in the mobile device 10. [ The authentication information of the mobile device 10 is information automatically obtained from the second application. For example, if the app serial number check field of the received transaction ID is set to a value of 2 4 5, the second transmission unit transmits the second, fourth and fifth values of the app serial number of the payment application to the second payment request message To the payment server 30.

The second receiving unit 15 receives a second payment response message including a payment execution result from the content providing server 20, and the payment execution result may be generated by the payment server 30. For example, the second payment response message may be a message including a payment success or failure message and a payment order number.

6 is a flowchart illustrating a payment method according to an embodiment of the present invention. 6, when the web browser 60 of the mobile device 10 makes a payment request (S601) to the content providing server 20, the content providing server 20 transmits a first payment authentication request message And transmits a first payment authentication request message to the payment server 30 (S602). The payment server 30 having received the first settlement authentication request message analyzes the first settlement authentication request message and determines an authentication method corresponding to the first settlement authentication request message. If the determined authentication method corresponds to the authentication 1, ID is generated (S603). The payment server 30 generates a first payment authentication response message including the generated transaction ID and transmits it to the content providing server (S604). The content providing server 20 receiving the first settlement authentication response message transmits the first settlement authentication response message to the web browser 60 of the mobile device (S605). The web browser 60 extracts the transaction ID from the received first payment authentication response message and transmits it to the payment application 50 of the mobile device 10 (S606). The payment application 50 of the mobile device 10 generates a second payment authorization request message including the received transaction ID, the token authentication ID of the mobile device, and the IP address of the mobile device, and transmits it to the payment server 30 (S607) do. Based on the received second settlement authentication request message, the payment server 30 determines whether the transaction ID included in the second settlement authentication request message has been received within the valid period of time (S608). In the case of confirmation with a valid transaction ID, the payment server 30 extracts the token authentication ID and the IP address of the mobile device from the received second payment authentication request message and generates a third payment authentication request message including the extracted information To the external server 40 (S609). The external server 40 confirms the settlement authentication based on the received third settlement authentication request message (S610), generates a third settlement authentication response message including the phone number of the mobile device 10, (Step S611). The settlement server 30 checks the mobile device settlement limit based on the received third settlement authentication response message (S612). If the limit of the settlement request amount is not exceeded, the settlement server 30 transmits the settlement limit to the external server 40 A payment request message is transmitted (S613). The external server 40 processes the settlement based on the received settlement request message (S614) and transmits a settlement response message to the settlement server (S615). The payment server 40 having received the settlement response message transmits a second settlement authentication response message including the settlement result to the content providing server 20 (S616). The content providing server 20 extracts the settlement execution result from the received second settlement authentication response message and transmits it to the web browser 60 of the mobile device 10 (S617).

In another embodiment, when the web browser 60 of the mobile device 10 makes a payment request (S601) to the content providing server 20, the content providing server 20 generates a first payment authentication request message corresponding to the payment request And transmits a first payment authentication request message to the payment server 30 (S602). The payment server 30 having received the first settlement authentication request message analyzes the first settlement authentication request message and determines an authentication method corresponding to the first settlement authentication request message. If the determined authentication method corresponds to the authentication 2, ID and the app serial number request 4-digit value (S603). The payment server 30 generates a first payment authentication response message including the generated transaction ID and the app serial number request 4-digit value and transmits it to the content providing server (S604). The content providing server 20 receiving the first settlement authentication response message transmits the first settlement authentication response message to the web browser 60 of the mobile device (S605). The web browser 60 extracts the transaction ID and the app serial number request 4-digit value from the received first payment authentication response message and transmits it to the payment application 50 of the mobile device 10 (S606). The payment application 50 of the mobile device 10 generates a second payment authorization request message including the received transaction ID, the token authentication ID of the mobile device, the IP address of the mobile device, and the number of the requested app serial number To the payment server 30 (S607). Based on the received second settlement authentication request message, the payment server 30 determines whether the transaction ID included in the second settlement authentication request message has been received within the valid period and determines whether the app serial number is authenticated (S608). In the case of confirmation with a valid transaction ID, the payment server 30 extracts the token authentication ID and the IP address of the mobile device from the received second payment authentication request message and generates a third payment authentication request message including the extracted information To the external server 40 (S609). The external server 40 confirms the settlement authentication based on the received third settlement authentication request message (S610), generates a third settlement authentication response message including the phone number of the mobile device 10, (Step S611). The settlement server 30 checks the mobile device settlement limit based on the received third settlement authentication response message (S612). If the limit of the settlement request amount is not exceeded, the settlement server 30 transmits the settlement limit to the external server 40 A payment request message is transmitted (S613). The external server 40 processes the settlement based on the received settlement request message (S614) and transmits a settlement response message to the settlement server (S615). The payment server 40 having received the settlement response message transmits a second settlement authentication response message including the settlement result to the content providing server 20 (S616). The content providing server 20 extracts the settlement execution result from the received second settlement authentication response message and transmits it to the web browser 60 of the mobile device 10 (S617).

In another embodiment, when the web browser 60 of the mobile device 10 makes a payment request (S601) to the content providing server 20, the content providing server 20 transmits a first payment authentication request message corresponding to the payment request And transmits a first payment authentication request message to the payment server 30 (S602). The payment server 30 having received the first settlement authentication request message analyzes the first settlement authentication request message and determines an authentication method corresponding to the first settlement authentication request message. If the determined authentication method corresponds to the authentication 3, ID and the open One Time Password 4 digits (S603). The payment server 30 generates a first payment authentication response message including the generated transaction ID and the open One Time Password and transmits the first payment authentication response message to the content providing server (S604). The content providing server 20 receiving the first settlement authentication response message transmits the first settlement authentication response message to the web browser 60 of the mobile device (S605). The web browser 60 extracts the transaction ID and the open One Time Password 4 digits from the received first payment authentication response message and transmits it to the payment application 50 of the mobile device 10 (S606). The payment application 50 of the mobile device 10 generates a second payment authorization request message including the received transaction ID, the token authentication ID of the mobile device, the IP address of the mobile device, and four open One Time Passwords, 30 (S607). Based on the received second settlement authentication request message, the payment server 30 determines whether the transaction ID included in the second settlement authentication request message has been received within the valid period of time and determines whether the open one time password is 4-digit matched (S608) do. In the case of confirmation with a valid transaction ID, the payment server 30 extracts the token authentication ID and the IP address of the mobile device from the received second payment authentication request message and generates a third payment authentication request message including the extracted information To the external server 40 (S609). The external server 40 confirms the settlement authentication based on the received third settlement authentication request message (S610), generates a third settlement authentication response message including the phone number of the mobile device 10, (Step S611). The settlement server 30 checks the mobile device settlement limit based on the received third settlement authentication response message (S612). If the limit of the settlement request amount is not exceeded, the settlement server 30 transmits the settlement limit to the external server 40 A payment request message is transmitted (S613). The external server 40 processes the settlement based on the received settlement request message (S614) and transmits a settlement response message to the settlement server (S615). The payment server 40 having received the settlement response message transmits a second settlement authentication response message including the settlement result to the content providing server 20 (S616). The content providing server 20 extracts the settlement execution result from the received second settlement authentication response message and transmits it to the web browser 60 of the mobile device 10 (S617).

7 is a flowchart illustrating a process of authenticating the content providing server 20. 7, when the content providing server 20 first tries to make a payment request to the payment server 30 or when the valid authentication ID period of the content providing server 20 expires, the content providing server 20 transmits a payment request (S701) the valid authentication ID request message of the content providing server to the authentication server 30 (step S701). Upon receiving the valid authentication ID request message of the content providing server, the payment server 30 transmits the valid authentication ID and effective authentication ID expiration time of the content providing server corresponding to the valid authentication ID request message of the content providing server, ID and an expiration time of the token ID, and transmits the valid authentication ID response message of the content providing server to the content providing server 20 (S702) .

In another embodiment, when the period of the token ID of the content providing server 20, which is one of information for authenticating the content providing server 20, expires, the content providing server 20 sends the content to the payment server 30 Upon receiving the token ID request message of the server, the payment server 30 receiving the token ID request message of the content providing server receives the token ID of the content providing server corresponding to the token ID request message of the content providing server, And transmits a token ID response message of the generated content providing server to the content providing server 20. The content providing server 20 transmits the token ID response message to the content providing server 20,

FIG. 8 is a flowchart for explaining the process of authenticating the mobile device 10. FIG. 8, when the mobile device 10 first tries to make a payment request, or when the USIM of the mobile device 10 is replaced, or when the effective authentication ID period of the mobile device 10 expires, The payment application 60 of the mobile device transmits the valid authentication ID request message of the mobile device to the payment server 30 (S801). Here, the valid authentication ID request message of the mobile device includes International Mobile Equipment Identity (IMEI) information, International Mobile Station Identity (IMSI) information, IP address of the mobile device, and UICC SIM information.

The payment server 30 having received the valid authentication ID request message of the mobile device determines the validity of the mobile device 10 based on the valid authentication ID request message of the mobile device 10 in operation S802, 10), the payment server 30 transmits the effective authentication ID and effective authentication ID expiration time of the mobile device corresponding to the valid authentication ID request message of the mobile device, the expiration time of the token ID and the token ID of the mobile device, Generates a valid authentication ID response message of the mobile device that includes either the device's AppSecurityNumber and the expiration time of AppSecurityNumbe and forwards the generated validation ID response message of the mobile device to the billing application 60 of the mobile device 10 (S803)

Another embodiment is that when the period of the token ID of the mobile device 10, which is one of the pieces of information authenticating the validity of the mobile device 10, expires, the mobile device 10 sends to the payment server 30 a token ID And transmits a request message.

Here, the token ID request message of the mobile device includes the valid authentication ID of the mobile device and the IP address of the mobile device.

Upon receiving the token ID request message from the mobile device, the payment server 30 determines the validity of the mobile device 10 based on the token ID request message of the mobile device 10 (S802) The payment server 30 generates a token ID response message of the mobile device that includes either the token ID of the mobile device and the expiration time of the token ID corresponding to the token ID request message of the mobile device, Token ID response message of the mobile device 10 to the mobile device 10.

9A to 9B are flowcharts illustrating a payment method according to an embodiment of the present invention. 9A and 9B, when the web browser 60 of the mobile device 10 receives the settlement request (S901) from the user interface 70, the web browser 60 of the mobile device 10 responds to the settlement request And transmits the generated first payment request message to the content providing server 20 (S902).

The content providing server 20 transmits the first payment request message received from the web browser 60 of the mobile device 10 to the payment server 30 in step S903.

When the payment server 30 receives the first payment request message from the content providing server 20, the payment server 30 extracts the ID and payment information of the mobile device 10 from the first payment request message (S904) And confirms the communication company of the mobile device with the extracted ID of the mobile device 10 (S905).

The payment server 30 generates and manages a transaction ID corresponding to the first payment request message received from the content providing server 20 (S906). The payment server 30 sets the authentication expiration time for the transaction ID before transmitting the generated transaction ID (S907).

The payment server 30 generates a first payment response message including a transaction ID, and then transmits a first result response message to the content providing server 20 (S908).

When the content providing server 20 receives the first payment response message from the payment server 30, the content providing server 20 transmits a first payment response message to the web browser 60 of the mobile device 10 (S909 )do.

The web browser 60 of the mobile device 10 extracts the transaction ID from the received first payment response message and transmits the extracted transaction ID to the payment application 50 of the mobile device 10 using the URL SCHEME technique S910).

The payment application 50 of the mobile device 10 generates a second payment request message containing the transaction ID and the authentication information of the mobile device 10 received from the web browser 60 of the mobile device 10, And transmits the second settlement request message to the payment server 30 (S911).

When the payment server 30 receives the second payment request message from the payment application 50 of the mobile device 10, the payment server 30 extracts the transaction ID and the authentication information of the mobile device 10 from the second payment request message (S912).

The payment server 30 determines whether the extracted transaction ID is identical to the transaction ID of the first settlement response message (S913). If it is determined that the transaction ID is the same transaction ID, the payment server 30 determines whether the extracted transaction ID has been received within the transaction ID authentication expiration time of the first payment response message (S914).

If the extracted transaction ID is received within the transaction ID authentication expiration time of the first payment response message, the payment server 30 performs the payment process through interoperation with the external server (S915) 2 settlement response message (S916), and transmits the generated second settlement response message to the content providing server 20 (S917).

When the content providing server 20 receives the second payment response message from the payment server 30, the content providing server 20 extracts the execution result of the payment processor from the second payment response message, (S5918) to the web browser 60 of the web browser 10 (step S5918).

10 is a flowchart illustrating a payment method according to an embodiment of the present invention. The payment method of the payment server 30 described in FIG. 10 is only an embodiment of the present invention, and therefore, there is no limitation thereto, and various embodiments may exist.

Referring to FIG. 10, in step S1001, the payment server 30 may receive a first payment request message from the content providing server 20.

In step S1002, the payment server 30 may generate a transaction ID corresponding to the received first payment request message.

In step S1003, the payment server 30 transmits a first payment response message including a transaction ID to the content providing server 20, and the transaction ID is transmitted from the content providing server 20 to the mobile device 10 .

In step S1004, the payment server 30 may receive a second payment request message including a transaction ID and authentication information from the mobile device.

In step S1005, the payment server 30 may perform the settlement process based on the transaction ID and the authentication information. .

In step S1006, the payment server 30 generates a second payment response message including the result of the payment processor.

In step S1007, the payment server 30 transmits a second payment response message to the content providing server 20, and the result is transmitted from the content providing server 20 to the mobile device 10. [

The payment method according to the embodiment described with reference to FIG. 10 may also be implemented in the form of a recording medium including instructions executable by a computer such as a program module executed by a computer. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, the computer-readable medium may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes any information delivery media, including computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transport mechanism.

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

The scope of the present invention is defined by the appended claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be interpreted as being included in the scope of the present invention .

10: Mobile device
20: Content providing server
30: Payment server

Claims (15)

In a payment method,
Receiving a first payment request message from a content providing server;
Generating a transaction ID corresponding to the received first payment request message;
Transmitting a first payment response message including the transaction ID to the content providing server, wherein the transaction ID is transmitted from the content providing server to the mobile device;
Receiving a second payment request message including the transaction ID and authentication information from the mobile device;
Performing a settlement process based on the transaction ID and the authentication information;
Generating a second settlement response message including an execution result of the settlement processor; And
And transmitting the second payment response message to the content providing server, wherein the execution result is transmitted from the content providing server to the mobile device.
The method according to claim 1,
The first payment request message is generated in response to a first payment request transmitted from the first application of the mobile device to the content providing server by the content providing server,
Wherein receiving the second payment request message comprises receiving the second payment request message from a second application of the mobile device.
3. The method of claim 2,
Wherein the first application is a web browser and the second application is a payment application directly connected to a payment server.
The method according to claim 1,
Wherein the first payment request message includes an ID of the mobile device.
3. The method of claim 2,
Wherein the authentication information includes International Mobile Equipment Identity (IMEI) information and International Mobile Station Identity (IMSI) information stored in the mobile device, an IP address of the mobile device, and an app serial number of the second application.
The method according to claim 1,
Wherein the first payment request message includes payment information of the mobile device,
Wherein the step of performing the settlement process performs the settlement process by interlocking with an external server based on the settlement information, the transaction ID, and the authentication information.
The method according to claim 1,
Wherein the transaction ID includes at least one of a country classification field, a carrier identification field, a time stamp field, a random number field, and an app serial number check field.
3. The method of claim 2,
Wherein the transaction ID is transferred from the first application to the second application based on a URL SCHEME technique.
A payment server for providing payment through a mobile device,
A first message receiver for receiving a first payment request message from a content providing server;
A generating unit for generating a transaction ID corresponding to the received first payment request message;
A transmission unit for transmitting a first payment response message including the transaction ID to the content providing server;
A second message receiver for receiving a second payment request message from the mobile device, the transaction ID being transmitted to the mobile device and including the transaction ID and authentication information, by the content providing server; And
And a settlement performing unit for performing a settlement process based on the transaction ID and the authentication information
Wherein the generating unit generates a second payment response message including a result of the payment processor,
Wherein the transmission unit transmits a second payment response message to the content providing server, wherein the result of the execution is transmitted from the content providing server to the mobile device.
10. The method of claim 9,
Wherein the generation unit comprises:
An extracting unit for extracting the ID of the mobile device from the received first payment request message;
A confirmation unit for confirming a communication company of the mobile device based on the extracted mobile device ID;
A management unit for managing a transaction ID generated in response to the received first payment request message; And
And a time setting unit for setting an authentication expiration time for the transaction ID transmitted to the content providing server.
11. The method of claim 10,
Wherein the extracting unit extracts the transaction ID and authentication information from the received second payment request message.
10. The method of claim 9,
Wherein the settlement performing unit comprises:
An ID determining unit for determining whether a transaction ID included in the second settlement request message matches a transaction ID included in the first settlement response message;
An authentication time determiner for determining whether a transaction ID included in the second settlement request message is received within an authentication expiration time; And
And an execution unit that performs a payment process based on a result of the determination as to whether or not the IDs match and a result of the determination as to whether or not the IDs have been received within the authentication expiration time.
13. The method of claim 12,
Wherein the settlement performing unit comprises:
And a verifying unit for verifying an app serial number of authentication information received from the mobile device,
Wherein the performing unit performs the settlement process based on the verification result, the determination result of whether or not the ID matches, and the determination result of whether or not the identification is received within the authentication expiration time.
In a mobile device,
A display unit for displaying contents through an execution screen of a first application running on the mobile device;
A first transmission unit for transmitting a first payment request message to a content providing server when a payment request for the content is inputted through a user interface;
A first receiving unit receiving a first payment response message including a transaction ID from the content providing server, the transaction ID being generated by a payment server;
A second transmission unit for transmitting a second payment request message including the received transaction ID and authentication information of the mobile device to the payment server; And
And a second receiving unit that receives a second payment response message including a payment execution result from the content providing server, wherein the payment execution result is generated by a payment server.
15. The method of claim 14,
Wherein the first payment request message is generated by the first application,
And the second payment request message is generated by a second application installed in the mobile device.

Images