WO2009069905A2

WO2009069905A2 - System for mobile payment service using phone number and method thereof

Info

Publication number: WO2009069905A2
Application number: PCT/KR2008/006667
Authority: WO
Inventors: Kyung Yang Park; Hoon Joon Jung
Original assignee: Harex Infotech Inc.
Priority date: 2007-11-28
Filing date: 2008-11-12
Publication date: 2009-06-04
Also published as: KR20090055474A; KR101039696B1; WO2009069905A3

Abstract

Provided are a mobile card payment system and a mobile payment service method. The mobile payment service method includes checking the type of a payment card by receiving a payment request comprising the type of the payment card, the telephone number of a mobile device, member store identification information and payment amount, performing a mobile prepayment in communication with a pre-paid card server using a payment VM driven by transmitting a first payment confirmation message comprising the member store identification information and the payment amount to the mobile device to allow the mobile device to check the first payment confirmation message if the type of the payment card is an client type, and performing a mobile credit payment in communication with a corresponding card issuer server using information received from the payment VM driven by transmitting a second payment confirmation message comprising the member store identification information and the payment amount to the mobile device to allow the mobile device to check the second payment confirmation message if the type of the payment card is an server type.

Description

SYSTEM FOR MOBILE PAYMENT SERVICE USING PHONE NUMBER AND METHOD THEREOF

Technical Field

[1] The present disclosure relates to a mobile payment service, and more particularly, to a mobile payment system and a mobile payment service method, which can request payment using a phone number without exposing the number of a payment card. Background Art

[2] Recently, a credit card is widely used as a payment means due to its convenience of use and portability. There are various cards such as a credit card, a check card, a debit card, a cash card, a gift card, and a point card according to a payment type.

[3] Also, due to development of electronic devices such as a mobile terminal and a smart card, a mobile integrated circuit (IC) card embedded in a mobile device has been widely used for a payment in various fields such as e-commerce, traffic, a vending machine, as well as general commercial transaction.

[4] According to a related art card payment method, if information (e.g., a card number, an available period, and an issuer) necessary for the transaction approval is provided via a terminal installed in a member store, the member store requests the transaction approval from the corresponding card company via a value added network (VAN). Then, the payment is performed on the basis of the approval result.

[5] However, according to the related art card payment method, the card information may be abused by a malicious member store because card information is exposed to the member store.

[6] Also, the customer's card information may be intentionally leaked to a third party by a counterfeit member store terminal. Accordingly, the leaked information may be easily used in duplicating the card, or an illegal payment by the third party. Disclosure of Invention Technical Problem

[7] Therefore, an object of the present invention is to provide a pre-paid or credit card payment system of requesting a payment approval and receiving the payment approval using only a telephone number without exposing a card number to a member store terminal, and a mobile payment service method using the same. Technical Solution [8] To achieve these and other advantages and in accordance with the purposes of the present invention as embodied and broadly described herein, a mobile card payment system in accordance with an aspect of the present invention includes: a mobile device having a payment Virtual Machine (VM) and information on a client type card includign at least one of a pre-paid card, a traffic card and an electronic cash card therein; a member store device requesting a payment approval including a telephone number of the mobile device, member store identification information and payment amount; a Mobile-Payment Gateway (M-PG) server transmitting a payment confirmation message including the member store identification information and the payment amount of the payment approval request, and driving the payment VM to the mobile device; and a pre-paid card server performing a mobile prepayment in communication with the payment VM in the mobile device which has received the payment confirmation message.

[9] To achieve these and other advantages and in accordance with the purposes of the present invention, a mobile card payment system in accordance with another aspect of the present invention includes: a mobile device having a payment VM and information on a server type card including at least one of a credit card, a check card, a debit card, a cash card and a point card therein; a member store device requesting a payment approval including a telephone number of the mobile device, member store identification information and payment amount; a mobile communication company server authenticating a user of the mobile device; and a M-PG server performing the user authentication with respect to the payment approval request through the mobile communication company server, receiving information of the server type card by transmitting applying a drive of the payment VM to the mobile device according to the authentication result, and receiving a transaction approval from a corresponding card issuer using the information of the server type card.

[10] To achieve these and other advantages and in accordance with the purposes of the present invention, a mobile card payment system in accordance with still another aspect of the present invention includes: a mobile device having information on at least one of payment cards and a payment VM; a member store device requesting a payment approval including the information on the payment card, a telephone number of the mobile device, member store identification information and payment amount; a M-PG server request a transaction approval by transmitting a first payment confirmation message applying a drive of the payment VM to the mobile device to allow the mobile device to perform a mobile prepayment in communication with a pre-paid card server if the payment card is a client type card, or transmitting a second payment confirmation message applying the drive of the payment VM to the mobile device to receive information on the server type card from the payment VM if the payment card is a server type card.

[11] To achieve these and other advantages and in accordance with the purposes of the present invention, a mobile payment service method in accordance with yet another aspect of the present invention includes: checking the type of a payment card by receiving a payment request including the type of the payment card, the telephone number of a mobile device, member store identification information and payment amount; performing a mobile prepayment in communication with a pre-paid card server using a payment VM driven by transmitting a first payment confirmation message including the member store identification information and the payment amount to the mobile device to allow the mobile device to check the first payment confirmation message if the type of the payment card is an client type; and performing a mobile credit payment in communication with a corresponding card issuer server using information received from the payment VM driven by transmitting a second payment confirmation message including the member store identification information and the payment amount to the mobile device to allow the mobile device to check the second payment confirmation message if the type of the payment card is an server type.

Advantageous Effects

[12] The present invention has an effect of enhancing personal information security by requesting a transaction approval without exposing card information because only a telephone number is used for the payment approval.

[13] Also, the present invention has another effect of re-confirming a payment amount, a payment means, etc. because a user receives a payment confirmation message through a mobile device upon payment request.

[14] Moreover, the present invention has still another effect of preventing an illegal use by a third party or a malicious member store because a user performs a mobile payment by driving a payment Virtual Machine (VM) after checking a payment confirmation message.

[15] Furthermore, the present invention has still another effect of increasing system security because a mobile device is authenticated by a mobile communication company server, and because the user is authenticated upon drive of payment VM. Brief Description of Drawings [16] FIG. 1 is a diagram illustrating a mobile card payment system using a telephone number of a server type card according to an embodiment of the present invention.

[17] FIG. 2 is a diagram illustrating a process of downloading a payment Virtual Machine

(VM) upon downloading credit card information in FIG. 1.

[18] FIG. 3 is a diagram illustrating a payment process of the mobile card payment system using the telephone number in FIG. 1.

[19] FIG. 4 is a diagram illustrating a mobile payment system of the client type card according to an embodiment of the present invention.

[20] FIG. 5 is a flowchart illustrating a mobile card payment system for server type and client type card payment according to an embodiment of the present invention. Mode for the Invention

[21] The present invention relates to a system and a method capable of performing a payment using a payment card provided in a mobile device such as a mobile phone and a smart phone, where the mobile payment may be performed by providing a member store with only a telephone number. The present invention may be embodied using various cards such as a credit card, a debit card, a cash card, a check card, a point card, an e-cash, and a traffic card. Hereinafter, the above cards will be collectively referred to as a payment card.

[22] The present invention may provide payment service by classifying the payment cards into a server type card and a client type card. The server type card refers to a card (e.g., a credit card, a check card, a debit card, a cash card, a point card, a network type prepaid card) capable of performing payment by storing the monetary value in a server, and communicating with the server using a unique identifier such as a card number. The client type card refers to a card (e.g., a traffic card, an e-cash such as a K-cash )including information on the monetary value.

[23] Hereinafter, preferred embodiments will be described in detail with reference to the accompanying drawings.

[24] FIG. 1 is a diagram illustrating a mobile card payment system using a telephone number of a server type card according to an embodiment of the present invention.

[25] Referring to FIG. 1, the mobile card payment system may include a mobile device 10 of a user, a member store device 20 in the member store where the user purchases products, a Mobile-Payment Gateway (M-PG) server 30, and a mobile communication company server 40.

[26] The mobile device 10 may include payment means such as a credit card (hereinafter, although focused on the credit card, it is noted that the server type card such as a check card, a debit card, a cash card, a point card, a network type pre-paid card may be used) information, and a payment Virtual Machine (VM). The credit card information and payment VM may be stored in an IC chip 11 embedded in the mobile device. For convenience of explanation, a mobile device including the IC chip 11 will be hereinafter described as an example. However, it is apparent that the payment VM may be embodied in any storage means or operation means equivalent to the IC chip 11.

[27] The member store device 20 may request a payment approval by transmitting information including the telephone number of mobile device 10, identification information and payment amount to the M-PG server 30.

[28] The mobile communication company server 40 may perform the user authentication of mobile device 10. The mobile communication company server 40 may include identification information (e.g., USIM Chip ID: UCID)) on the IC chip 11 embedded in the mobile device 10, a telephone number, a user identification number (e.g., resident registration number, driving license number), information on application (e.g., application for a credit card, or a pre-paid card) stored in the IC chip, and a database (hereinafter, referred to as UCID database) managing information on 3G phone, etc. The mobile communication company server 40 may perform the user authentication with respect to the mobile device 10 using the identification information and the telephone number received from the mobile device 10 on the basis of the UCID database 41.

[29] The M-PG server 30 may receive a payment approval request from the member store device 20, and perform the user authentication through the mobile communication company server 40 accordingly. If the user is authenticated as a legitimate user, the M- PG server 30 may transmit a payment confirmation message (e.g., Short Message Service (SMS) or Multimedia Message Service (MMS)) to the mobile device 10, and then receive credit card information from the payment VM driven by checking the payment confirmation message. Then, the M-PG server 30 performs may perform a transaction approval procedure with the corresponding card company server 60 using the received credit card information, and notify the member store device 20 and mobile device 10 of the transaction result.

[30] In this case, the transaction approval procedure between the M-PG server 30 and the corresponding card company server 60 may be performed through Value Added Network (VAN) company server 50. Alternatively, the M-PG server 30 may perform a role of the VAN company server 50.

[31] Hereinafter, the mobile payment procedure of the system as described in FIG. 1 will be described in detail with reference to FIGS. 2 and 3. [32] IC chip identification information (e.g., UCID, UICC-ID), which is unique, may be stored in the IC chip 11 of the mobile device 10 together with credit card information of the user. There may be a plurality of credit card information. Also, the IC chip of the mobile device 10 further may include information (offline transaction frequency, offline amount limit) for a batch process so that the mobile device 10 may not need to receive an approval for every transaction.

[33] A 3G mobile device may be used as the mobile device 10. In this case, a Universal

Subscriber Identity Module (USIM) chip may be used as the IC chip. The 3G mobile device may include information (telephone number list, call charge, additional service), which is stored in a USIM chip of a typical mobile device, and a USIM-based application such as traffic, membership, pass authentication, banking, and stock. Accordingly, only if the USIM chip is replaced, information individually stored in the mobile device 10 may be used as it is. That is, service according to an embodiment of the present invention may be independently applied to the mobile device 10.

[34] In order to use the mobile payment service according to the present invention, the user may download an application (hereinafter, referred to as a payment VM) for payment to the mobile device 10. The payment VM may be downloaded together with the credit card information. Selectively, the payment VM may be downloaded when a first payment is performed. Selectively, the payment may be downloaded from the M- PG server 30 by the request of the user.

[35] FIG. 2 is a diagram illustrating a process of downloading a payment VM upon downloading credit card information. In step S201, a card issuer receives a card issue request from a user, and performs a card issue examination. Then, in step S202, the card issuer requests a user information inquiry such as telephone number, Mobile Directory Number (MDN) and resident number from the mobile communication company 40 via an Over The Air (OTA) center. In step S203, the mobile communication company server 40 sends the result of the user authentication (e.g., customer ID, 3G phone, Combi UICC, UICC) to the card issuer via the OTA center. In step S204, the card issuer prepares issue data after confirming the result of the user authentication. In step S205, the card issuer requests the OTA center to notify the user of a message. In step S206, the OTA center notifies the mobile communication company server 40 of an issue target. In step S207, the OTA center sends a message to the mobile device 10 of the user. In step S208, the user check the message on the screen of the mobile device 10 and connects to the mobile communication company server 40 through a call back URL included in the message to download the card information and the credit card information to the IC chip 11 and the mobile device 10, respectively. In step S209, the user downloads the payment VM together. In step S210, the user notifies the mobile communication company server 40 of the result.

[36] FIG. 3 is a diagram illustrating a payment process of the mobile card payment system using the telephone number in FIG. 1.

[37] As described in FIG. 3, when the user makes payment for purchase of goods, the user expresses an intention to make payment using the mobile device 10 and provides the telephone number to the member store device 20 (®). That is, the user may make payment by providing only a telephone number without information on the credit card, thereby preventing an illegal use of his credit card caused by the member store.

[38] The member store device 20 requests the M-PG server 30 to process the payment by providing information on telephone number, payment amount, and member store number to the M-PG server 30(®).

[39] If the M-PG server 30, which serves as a central operating body of the service, receives the payment request from the member store device 20, the M-PG server 30 requests authentication of the mobile device 10 from the corresponding mobile communication company server 40 ((D).

[40] After processing the authentication procedure (e.g., verifying telephone number and

IC chip unique identification information) in accordance with the authentication request received from M-PG server 30, the mobile communication company server 40 notifies the M-PG server 30 of the authentication result (®). In this case, by performing the above authentication procedure, it is possible to prevent unnecessary transaction approval procedure when the user requests the payment by informing the telephone number without getting credit card information. Accordingly, the member store may induce such a user to use other payment means in order to maintain sales. Also, the M-PG server 30 may prevent a loss caused by unnecessary data management.

[41] Then, the M-PG server 30 transmits a payment confirmation message including member store name, payment amount and payment progress state to the mobile device 10 of the user (©).

[42] By confirming the payment confirmation message, the user drives the payment VM stored in mobile device 10 (©). In this case, if the payment VM was not downloaded the mobile device 10, the mobile device 10 may displays a message showing the absence and necessity of the payment VM on the screen of the mobile device 10. Then, the mobile device 10 may download the payment VM from the mobile communication company server 40 or the M-PG server 30 by the request of the user. [43] In this case, a user authentication procedure may be performed in driving the payment VM. That is, the user authentication procedure may be performed using one or any combination of password (card identification number set in the application of the card or by the user), PIN number of USIM chip, fingerprint recognition, and voice recognition (©'). For this, the mobile device 10 may have a fingerprint recognition module or a voice recognition module, and set up a password when the payment VM is first downloaded.

[44] Then, the mobile device 10 compares the authentication information inputted by the user with the preset authentication information (e.g., comparing an inputted password with a password stored in the IC chip) to authenticate the user. If the user is successfully authenticated, the mobile device 10 transmits the payment approval request to the M-PG server 30 together with the credit card information and IC chip identification information stored in the IC chip 11 of the mobile device 10 (©). For the security of the credit card information included in the payment request, the mobile device 10 may encode the payment approval request data through an encoding process(©") before transmitting the payment approval request data to the M-PG server 30.

[45] In this case, the payment approval request further may include on/off-line transaction classification information besides the credit card information and IC chip identification information. That is, this transaction classification information may include whether the transaction approval is performed for every transaction (on-line transaction) or in a batch (off-line transaction).

[46] The M-PG server 30 requests the transaction approval from the corresponding card company server 60 by using the credit card information included in the payment approval request (®'). In this case, the transaction approval may be requested via a VAN server 50 (®).

[47] In this case, if the transaction approval request further includes the transaction classification information, the M-PG server 30 checks if the transaction approval request corresponds to an off-line transaction request. If the transaction approval request corresponds to the off-line transaction request, the M-PG server 30 may receive information on off-line transaction frequency and amount stored in the IC chip of the mobile device 10 via the payment VM, and make payment by vicariously performing the transaction approval of the corresponding card company within the transaction frequency and amount. Then, the MPG server 30 may modify the information on offline transaction frequency and amount by reflecting the payment amount, and notify the payment VM of the payment result including the modified information. The payment VM may update information on off-line transaction frequency and amount stored in the IC chip by reflecting the payment result of the vicarious approval.

[48] Also, the MPGserver 30 may perform a batch approval by recording the details of the vicarious approval, and providing the transaction record of the vicarious approval to the corresponding card company server 60 on a date set by the user or a predetermined date (e.g., a specific monthly date).

[49] In this case, if the vicarious approval is performed, the vicarious approval may be configured to be deferred until the batch approval is actually made by the card company. That is, if the M-PG server 30 notifies of the payment result of the vicarious approval, the payment VM may be configured to automatically set off-line transaction permissible frequency and off-line transaction permissible amount to zero.

[50] Then, if the off-line transaction is not-applied or impossible, the M-PG server 30 receives the approval result from the card company 60 server (® and ®'), and notifies the member store device 20 and the user of the payment result (® and ®').

[51] As described above, it is assumed that the user confirms the message and requests the payment immediately after the user receives the payment confirmation message. However, it may be supposed that there is a non-approved payment when the transaction is not completed. In this case, re -payment may be performed with respect to the non-approved payment according to an embodiment of the present invention. The reason why re-payment may be performed is as follows. If, although there are several transactions, the user does not complete the corresponding transaction immediately after receiving the payment confirmation message, the payment confirmation message may be recorded as a general message in the mobile device 10. If the payment confirmation message is recorded as a general message, it is impossible to drive the corresponding payment VM.

[52] In order to perform a re-payment, the M-PG server 30 may maintain a list of non- approved payments, which are not completed although the payment confirmation message is sent. The user trying to perform re -payment may connect to the M-PG server 30 to receive the list of non-approved payments by driving the payment VM of the mobile device 10, and request re -payment by selecting one or more non-approved payments to complete from the list. In order to perform the re-payment, the payment VM may perform the user authentication as described above, and transmit the repayment request information including the credit card information to the M-PG server 30. The M-PG server 30, which received the re-payment request information, may complete the re -payment using the credit card information included in the re -payment request information, and notify of the re-payment result.

[53] In order to perform a re-payment, only the user authentication may be performed without transmitting the credit card information. This is because, when the first payment approval is requested, information such as payment amount and credit card information necessary for the payment have already been provided, and the information may be maintained as the list of non-approved payments in the M-PG server 30. For example, the payment VM may execute the re-payment by transmitting the repayment request information including only user authentication information such as card password to the M-PG server 30.

[54] As described above, it is assumed that information on one card is stored in the IC chip 11. However, information on a plurality of cards may be stored. When information on the plurality of cards is stored in the IC chip 11, the payment approval request may be performed using a card selected by the user, or a card determined in accordance with an order determined upon driving of the payment VM.

[55] FIG. 4 is a diagram illustrating a mobile payment system of the client type card according to an embodiment of the present invention. The mobile payment system according to this embodiment will be described, focused on a difference from the mobile payment system of the server type card with reference to FIG. 1.

[56] Referring to FIG. 4, the mobile card payment system according to this embodiment of the present invention may include a mobile device 10, a member store device 20, a mobile -payment gateway (M-PG) server 30, and a pre-paid card server 70.

[57] The mobile device 10 may include an IC chip where a payment VM and information on a payment means such as a pre-paid card (hereinafter, although 'pre-paid card' will be described as an example, a client type card such as traffic card and electronic money such as K-cash may be applied) are stored. The mobile device 10 may download and store the payment VM from the M-PG server 30 as described above.

[58] In the pre-paid card mobile payment system according to this embodiment of the present invention, the payment VM of the mobile device 10 directly performs a prepaid card payment with the pre-paid card server 70, differently from the payment system as described in FIG. 1 which performs the credit card payment via the M-PG server 30.

[59] The M-PG server 30 may transmit a payment confirmation message including member store identification information and payment amount included in the payment approval request received from the member store device 20 to the mobile device 10. The payment confirmation message may drive the payment VM of the mobile device 10 as described above. The M-PG server 30 may provide the payment approval request to the pre-paid card server 70.

[60] The pre-paid card server 70 may perform the pre-payment with the payment VM driven by the payment confirmation message, and notify the mobile device 10 and the M-PG server 30 of the payment result. For this, the pre-paid card server 70 may hold the payment approval request provided from the M-PG server 30, and check whether the pre-payment request received from the payment VM exists in the payment approval request. If the pre-payment request received from the payment VM exists in the payment approval request, the pre-paid card server 70 may perform the prepayment.

[61] Hereinafter, the payment service through the mobile payment system as described in

FIG. 4 will be described.

[62] A user notifies the member store that the user pays the purchase price of goods using a pre-paid card, and provides telephone number of mobile device 10 (®).

[63] The member store device 20 transmits a payment approval request including information on telephone number, member store identification number and payment amount to the M-PG server 30 (©). In this case, information verifying that the payment means is the pre-paid card may be further included in the payment approval request.

[64] The M-PG server 30 notifies a prepayment service provider 405 of payment approval request including member store number, payment amount, etc. after checking that the payment means is the pre-paid card (©). The prepayment service provider 405 records the payment approval request in a payment standby database DB.

[65] Also, the M-PG server 30 transmits the payment confirmation message including a member store name, payment amount and payment progress state to the mobile device 10 (®). In this case, the M-PG server 30 may transmit the payment confirmation message after performing the mobile device authentication through the mobile communication company server 40 as described above. Since description of the mobile communication company server 40 has already been described with reference to FIG. 1, the detail description will be omitted.

[66] The user may drive the payment VM by performing a payment progress confirmation about the payment confirmation message received in mobile device 10 (©). Before the payment VM is driven, the user authentication procedure will be performed using at least one of password, PIN number, fingerprint information and voice information or combination thereof as described above(©). [67] In this case, if, although the user received the payment confirmation message, the payment VM is not stored in the mobile device 10, the mobile device 10 may receive the payment VM by communicating with the M-PG server 30. In order to receive the payment VM, the payment confirmation message further may include information on a communication path through which the payment VM is downloaded from the M-PG server 30.

[68] The payment VM of the mobile device 10 requests a payment approval including member store identification information, pre-paid card information and payment amount from corresponding pre-paid card server 70 (©). When the payment VM communicates with the pre-paid card server 70 to request the payment approval, encoding process may be performed. For example, communication between the payment VM and the pre-paid card server 70 may be authenticated and encoded using a key included in pre-paid card information stored in the IC chip 11 of the mobile device 10.

[69] The pre-paid card server 70 checks whether the payment approval request received from the payment VM is stored in the payment standby DB (i.e., checks whether the payment approval request arrives at the M-PG server 30). If the payment approval request corresponding to the payment request of the payment VM exists in the payment standby DB, the prepayment is approved.

[70] Next, the pre-paid card server 70 notifies the mobile device 10 of the approved payment result (®). Also, the pre-paid card server 70 notifies the M-PG server 30 of the approved payment result (®). In this case, information on the balance obtained by subtracting the payment approved amount from the pre-paid amount may be further included in the notification of the payment result.

[71] The M-PG server 30 provides the payment result received from the pre-paid card server 70 to the member store device 20 (®).

[72] The member store verifies the payment confirmation information displayed on the member store device 20, and provides the purchased product to the user (D).

[73] The mobile communication company server 40 maintains identification information of the IC chip of the mobile device 10 in a database. Also, the mobile communication company server 40 may authenticate the mobile device 10 using the telephone number and the identification information received from the M-PG server 30. Furthermore, the mobile communication company server 40 may transmit a payment confirmation message according to the request of the M-PG server 30.

[74] Hereinafter, a mobile payment system for server type and client type card according to another embodiment of the present invention will be described. The mobile payment system for server type and client type card according to another embodiment of the present invention may be configured by combining the mobile payment system for the server type card in FIG. 1 and the mobile payment system for the client type card in FIG. 4.

[75] The mobile payment system according to this embodiment may include a mobile device 10, a member store device 20, an M-PG server 30, a credit card server 60, and a pre-paid card server 70.

[76] The mobile device 10 of a user may include an IC chip in which card information and a payment VM may be stored. In this case, card information may include one or both of server type card (hereinafter, referred to as a credit card) information and client type card (hereinafter, referred to as a pre-paid card) information. In this case, the payment VM may include all the functions of the credit card payment VM in FIG. 1 and the pre-paid card payment VM in FIG. 4.

[77] Also, as described above, the mobile device 10 may authenticate the user using at least one or any combination of password, PIN number, fingerprint recognition and voice recognition in driving the payment VM. Also, if information on a plurality of cards is stored in the mobile device 10, the payment may be requested using a card selected by the user or a predetermined order.

[78] The member store device 20 may request payment approval from the M-PG server

30 by transmitting the type of card, telephone number, member store identification number and payment amount. In this case, the type of card may be a credit card or a pre-paid card, which must corresponds to card information stored in the mobile device 10 of the user.

[79] When the M-PG server 30 receives the payment approval request, the M-PG server

30 determines which type of the card is used. If the card is a pre-paid card, the mobile payment is performed as described in FIG. 4. If the card is a credit card, the mobile payment is performed as described in FIGS. 1 to 3.

[80] That is, if the received payment approval request is from the pre-paid card, a prepayment confirmation message applying the drive of the payment VM to the mobile device 10 may be transmitted in order to perform the mobile prepayment with the prepaid card server 70. If the payment approval request is from the credit card, a credit payment confirmation message applying the payment VM to the mobile device 10 may be transmitted. This is to perform the transaction approval with the corresponding card company by receiving credit card information from the payment VM driven by the credit payment confirmation message. The approved payment result is transmitted to the member store device 20 and the mobile device 10 as described above.

[81] Before this message is sent, as described above, the authentication procedure of the mobile device 10 may be performed. That is, the M-PG server 30 may authenticate the mobile device 10 by providing IC chip identification information and telephone number of the mobile device 10 to the mobile communication company server maintaining a database of IC chip identification information.

[82] Also, if the payment VM is not stored in the mobile device 10, the mobile device 10 may download the payment VM through M-PG server. That is, the payment confirmation message further may include information on, e.g., a downloadable path of the payment VM of the M-PG server 30.

[83] More concretely, the M-PG server 30 provides the payment approval request received from mobile device 10 to the pre-paid card server 70. The mobile device 10 may receive and confirm a prepayment confirmation message, and drive the payment VM drive percentage. The payment VM may include information on member store and payment amount, and perform the mobile prepayment with the pre-paid card server 70 as described above. In this case, the pre-paid card server 70 checks whether the prepaid card payment request from the payment VM exists in the payment approval request provide from M-PG server 30. if the pre-paid card payment request from the payment VM exists, the prepayment is performed. Then, the pre-paid card server 70 may provide the payment result to the mobile device 10 and the M-PG server 30 according to the payment result, which may include information on the paid amount and the remaining balance after the payment. The M-PG server 30 may notify the mobile device 10 of the payment result to allow the user to confirm the payment result.

[84] FIG. 5 is a flowchart illustrating a mobile card payment system for server type and client type card payment according to an embodiment of the present invention. Hereinafter, a mobile payment service method for server type card and client type card payment will be described with reference to FIG. 5.

[85] In step S510, if the M-PG server 30 receives the payment request from the member store device 20, the M-PG server 30 checks the type of the payment card included in the payment request. The payment request may include information on the type of the payment card, telephone number of the mobile device 10, the member store identification number, and the payment amount.

[86] In step S520, the M-PG server 30 checks the type of the payment card. In step S521, if the type of the payment card is a pre-paid card, the M-PG server 30 transmits the prepayment confirmation message to the mobile device 10, and provides the received payment request to the pre-paid card server 70. In this case, the prepayment confirmation message may drive the payment VM of the mobile device 10, and include the member store identification information and the payment amount. The mobile device 10 receiving the prepayment confirmation message may drive the payment VM. In step S522, the payment VM requests the pre-paid card server 70 to approve the mobile prepayment including information on the pre-paid card, the member store identification, and the payment amount. The pre-paid card server 70 may perform the mobile payment, and notify the mobile device 10 and the M-PG server 30 of the payment result. In step S523, the M-PG server 30 notifies the member store device 20 of the payment result.

[87] In step S531, if the type of the credit card is verified in the M-PG server 30, the M-

PG server 30 transmits a credit payment confirmation message to the mobile device 10. In step S532, the mobile device 10 receives credit card information from the payment VM, and requests the credit card server 60 to approve the mobile credit payment using the credit card information, the member store identification information, the payment amount information. If the credit card server 60 approves the mobile credit payment, the M-PG server 30 may notify the mobile device 10 of the approved payment result.

[88] Also, the M-PG server 30, as described above, may authenticate the mobile device

10 by providing the IC chip identification information and telephone number of the mobile device 10 to the mobile communication company server 40.

[89] Moreover, the M-PG server 30 may receive approval information on the prepayment or credit payment from the corresponding pre-paid card server 70 or the corresponding credit card server 60, and notify the mobile device 10 of the approval information.

[90] The mobile payment method as described is characterized in that the user may verify the payment confirmation message using the mobile device 10. If, although the user received the message, the user doest not perform the payment, the payment may remain uncompleted. Accordingly, the M-PG server 30 may store and maintain the non-approved prepayment or credit payment (e.g., in a list or database).

[91] Also, because the non-approved payment is stored, it is possible to configure an embodiment in order to perform the later approval. More concretely, the M-PG server 30 may provide information on the non-approved payment to mobile device 10. If the M-PG server 30 receives the later approval request from the user, the M-PG server 30 may perform the later approval by re-performing the prepayment or credit payment process. [92] As the present invention may be embodied in several forms without departing from the spirit or essential characteristics thereof, it should also be understood that the above-described embodiments are not limited by any of the details of the foregoing description, unless otherwise specified, but rather should be construed broadly within its spirit and scope as defined in the appended claims, and therefore all changes and modifications that fall within the metes and bounds of the claims, or equivalents of such metes and bounds are therefore intended to be embraced by the appended claims.

Claims

[1] A mobile card payment system comprising: a mobile device having a payment Virtual Machine (VM) and information on a client type card comprising at least one of a pre-paid card, a traffic card and an electronic cash card therein; a member store device requesting a payment approval comprising a telephone number of the mobile device, member store identification information and payment amount; a Mobile-Payment Gateway (M-PG) server transmitting a payment confirmation message comprising the member store identification information and the payment amount of the payment approval request, and driving the payment VM to the mobile device; and a pre-paid card server performing a mobile prepayment in communication with the payment VM in the mobile device which has received the payment confirmation message.

[2] The mobile card payment system of claim 1, wherein the member store device requests the payment approval further comprising information on an IC chip storing the payment VM and information on the client type card, the system further comprising a mobile communication company server managing the information on the IC chip in a database, and authenticating the mobile device using the telephone number and the information on the IC chip provided from the M-PG server.

[3] The mobile card payment system of claim 2, wherein the M-PG server transmits the payment confirmation message through the mobile communication company server, which authenticates the mobile device before the transmission of the payment confirmation message.

[4] The mobile card payment system of claim 1, wherein the mobile device receives and stores the payment VM from the M-PG server, using information on a communication path with the M-PG server, further comprised in the payment confirmation message.

[5] The mobile card payment system of claim 4, wherein the mobile device drives the payment VM when a user checks the payment confirmation message, the system authenticating the user using one or any combination of a password, a PIN number and fingerprint information to drive the payment VM.

[6] The mobile card payment system of claim 1, wherein the pre-paid card server further comprises a payment standby database (DB) storing the payment approval request received from the M-PG server.

[7] The mobile card payment system of claim 6, wherein, when the payment approval request corresponding to the mobile prepayment request received from the payment VM exists in the payment standby DB, the pre-paid card server approves the mobile prepayment request.

[8] The mobile card payment system of claim 1, wherein the pre-paid card server notifies the member store device of the payment result through the M-PG server, and notifies the mobile device of the payment result through the payment VM.

[9] A mobile card payment system comprising: a mobile device having a payment Virtual Machine (VM) and information on a server type card comprising at least one of a credit card, a check card, a debit card, a cash card and a point card therein; a member store device requesting a payment approval comprising a telephone number of the mobile device, member store identification information and payment amount; a mobile communication company server authenticating a user of the mobile device; and a M-PG server performing the user authentication with respect to the payment approval request through the mobile communication company server, receiving information of the server type card by transmitting applying a drive of the payment VM to the mobile device according to the authentication result, and receiving a transaction approval from a corresponding card issuer using the information of the server type card.

[10] The mobile card payment system of claim 9, wherein the mobile device further comprises information on off-line transaction frequency and amount, the member store device requesting the payment approval by further comprising transaction classification information with respect to an on-line transaction or an off-line transaction, the M-PG server vicariously performing the transaction approval of the corresponding card issuer within a range of the information of the off-line transaction frequency and amount if the trans action classification information corresponds to the off-line transaction.

[11] The mobile card payment system of claim 10, wherein the mobile device updates the information on the off-line transaction frequency and amount by reflecting the payment result with respect to the vicarious approval received from the M- PG server.

[12] The mobile card payment system of claim 9, wherein, if the information on a plurality of server type cards exists, the mobile device performs the payment approval request with respect to the server type cards in an order selected by a user or a predetermined order.

[13] The mobile card payment system of claim 9, wherein the M-PG server maintains a list of non-approved payments while the payment confirmation message is transmitted.

[14] The mobile card payment system of claim 13, wherein the mobile device requests the list of the non-approved payments from the M-PG server, and requests the M-PG server to perform at least one of the non-approved payments, the M-PG server performing the transaction approval with respect to the non- approved payment in communication with the corresponding card issuer using the information of the server type card.

[15] A mobile card payment system comprising: a mobile device having information on at least one of payment cards and a payment VM; a member store device requesting a payment approval comprising the information on the payment card, a telephone number of the mobile device, member store identification information and payment amount; a M-PG server request a transaction approval by transmitting a first payment confirmation message applying a drive of the payment VM to the mobile device to allow the mobile device to perform a mobile prepayment in communication with a pre-paid card server if the payment card is a client type card, or transmitting a second payment confirmation message applying the drive of the payment VM to the mobile device to receive information on the server type card from the payment VM if the payment card is a server type card.

[16] The mobile card payment system of claim 15, wherein the M-PG server receives pre-paid amount information reflected by the prepayment to notify the mobile device of the paid amount information.

[17] The mobile card payment system of claim 15, wherein the M-PG server provides the payment VM to the mobile device if the payment VM is not embedded in the mobile which has received the first or second payment conformation message.

[18] The mobile card payment system of claim 15, wherein the mobile device authenticates a user by using one or any combination of a password, a PIN number, fingerprint recognition and voice recognition.

[19] The mobile card payment system of claim 15, wherein the mobile device requests the payment approval using a card selected from the plurality of card by a user or by a predetermined order.

[20] A mobile payment service method comprising: checking the type of a payment card by receiving a payment request comprising the type of the payment card, the telephone number of a mobile device, member store identification information and payment amount; performing a mobile prepayment in communication with a pre-paid card server using a payment VM driven by transmitting a first payment confirmation message comprising the member store identification information and the payment amount to the mobile device to allow the mobile device to check the first payment confirmation message if the type of the payment card is an client type; and performing a mobile credit payment in communication with a corresponding card issuer server using information received from the payment VM driven by transmitting a second payment confirmation message comprising the member store identification information and the payment amount to the mobile device to allow the mobile device to check the second payment confirmation message if the type of the payment card is an server type.

[21] The mobile payment service method of claim 20, further comprising authenticating the mobile device by providing identification information and telephone number of an Integrated Circuit (IC) chip of the mobile device to a mobile communication company server.

[22] The mobile payment service method of claim 20, further comprising generating a list of non-approved prepayments or credit payments if the mobile device which has received the first or second payment confirmation message does not perform the prepayment or the credit payment.

[23] The mobile payment service method of claim 22, further comprising post- approving the non-approved prepayment or credit payment according to repayment request of the mobile device by providing the information on the prepayment or credit payment comprised in the list to the mobile device.