KR20090055474A - System for mobile payment service using phone number and method thereof - Google Patents

Abstract

A mobile card payment system using a telephone number and a mobile payment service method using the same are provided to enhance the security by requesting the payment through the telephone number instead of card information. A mobile device(10) includes client type card information, including at least one of a prepaid card, a transportation card and an electric money card, and a payment VM(Virtual Machine). A franchise device(20) requests the payment admission including the phone number of the mobile device, franchise identification information and payment amount. A mobile-payment gateway(M-PG) server(30) sends a payment confirmation message to the mobile device.

Description

Mobile card payment system using phone number, mobile payment service method using him {SYSTEM FOR MOBILE PAYMENT SERVICE USING PHONE NUMBER AND METHOD THEREOF}

The present invention relates to a mobile payment service, and more particularly, to a mobile card payment system and a payment service method capable of requesting a payment using a phone number without exposing a payment card number in performing a payment. .

Recently, the use of credit cards and the like has been activated by the convenience of carrying and using as a payment method. These types of cards vary depending on the type of payment, such as credit cards, check cards, debit cards, cash cards, gift cards, and point cards.

In addition, due to the development of electronic devices such as mobile terminals and smart cards, there are mobile IC cards that are used in mobile devices. This is an expanding reality.

In the conventional payment method using such cards, if a terminal installed on the merchant side provides information (eg, a card number, a valid agency, a card issuer, etc.) necessary for the authorization of the transaction, the merchant stores the transaction through the VAN company. It is a method of requesting approval and processing payment based on the approved result.

However, in the current card payment method, since payment is made in a state where the card information of the customer is exposed to the merchant, there is a problem of abuse of the card information of the customer by a malicious company.

In addition, there is a problem that the card information of the customer is leaked to the third party by the modulated merchant terminal, card duplication or random payment by the third party is easy.

The present invention is to solve the above-mentioned problems, the problem to be solved by the present invention is a mobile phone using a phone number that can be requested and approved using only the phone number without exposing the number of the card for payment to the merchant device; It is to provide a card payment system, a mobile payment service method using the same.

In order to solve the above-mentioned problems, the mobile card payment system according to an aspect of the present invention, the client-type card information including at least one of a prepaid card, a transportation card and an electronic money card and mobile VM (Virtual Machine) embedded device; A merchant device requesting payment approval including a phone number of the mobile device, merchant identification information, and a payment amount; A mobile-payment gateway (M-PG) server that sends the payment confirmation message including the affiliated store identification information of the received payment approval request and the payment amount and authorizes driving the payment VM to the mobile device; And a prepaid card server for performing a mobile prepaid payment in association with the payment VM in the mobile device receiving the payment confirmation message.

According to another aspect of the present invention, a mobile card payment system includes a mobile device in which server-type card information and payment VM (Virtual Machine) including at least one of a credit card, a check card, a debit card, a cash card and a point card are embedded; A merchant device requesting payment approval including a phone number of the mobile device, merchant identification information, and a payment amount; A mobile telecommunication company server for performing user authentication of the mobile device; And performing the user authentication on the received payment approval request through the mobile telecommunication company server, and sending a payment confirmation message for driving and approving the payment VM to the mobile device according to the authentication result. Received, and the mobile server-based payment gateway (M-PG) server receives the transaction approval from the card issuer server with the received server-type card information.

According to another aspect of the present invention, a mobile card payment system includes a mobile device having at least one payment card information and a payment VM (Virtual Machine); A merchant device requesting payment approval including information on the type of the payment card making a payment request, a phone number of the mobile device, merchant identification information, and a payment amount; And if the payment card type of the received payment approval request is a client type card, sending a first payment confirmation message for driving the payment VM to the mobile device to perform mobile prepaid payment with the prepaid card server. And if the payment card type is a server-type card, sends a second payment confirmation message for driving and approving the payment VM to the mobile device, receives the server-type card information from the payment VM, and approves the transaction with the card company. Requesting Mobile-Payment Gateway (M-PG) server;

Mobile payment service method according to another aspect of the present invention, by receiving a payment request including the type of payment card, the user's mobile device phone number, merchant identification information and payment amount, and confirms the type of payment card Making; If the type of payment card is a client-type card as a result of the checking, a first payment confirmation message including the affiliated store identification information and the payment amount is sent to the mobile device, and the mobile device sends the first payment confirmation message. A prepaid payment step of performing a mobile prepaid payment with a prepaid card server using the payment VM driven by checking; And if the type of payment card is a server type card, from the payment VM driven by sending a second payment confirmation message including the affiliated store identification information and the payment amount to the mobile device and confirming the second payment confirmation message. And a credit settlement step of performing a mobile credit settlement with the corresponding card issuer server using the received server type card information.

According to the present invention, since a payment request is made at an affiliated device using a phone number without using card information, a transaction can be requested without exposing card information compared to the prior art, thereby improving security of personal information.

In addition, since the present invention receives a payment confirmation message to the user's mobile device when the payment is requested, the user can check the payment amount, payment method, and the like once more.

In addition, since the mobile payment is performed by operating the payment VM (Virtual Machine) by checking the payment confirmation message, there is an effect that can prevent random payments by malicious merchants or third parties.

In addition, the present invention can perform mobile device authentication by the mobile communication company server, user authentication when running the payment VM, there is an effect that can increase the security.

The present invention provides a system and method for performing a payment by using a payment card provided in a mobile device such as a user's mobile phone or a smart phone, and providing only a phone number to the merchant side when performing the payment. It is about. The present invention can be implemented using a variety of payment cards such as credit cards, debit cards, cash cards, check cards, point cards, electronic money, transportation cards, etc. Hereinafter, these cards are collectively referred to as 'payment card' Explain.

The present invention can classify payment cards into server-type cards and client-type cards to provide separate payment services. A server-type card is a card that stores the value of money on a server and communicates with the server using a unique identifier such as the card number of the card to make a payment (eg, credit card, check card, debit card, cash card, point card). , A network type prepaid card, etc.), and a client type card means a kind of card (for example, a transportation card or an electronic money such as K-cash) provided with information on the value of money.

Hereinafter, with reference to the accompanying drawings will be described in detail a preferred embodiment of the present invention.

1 is a block diagram of a mobile card payment system using the phone number of the server-type card according to the present invention.

The mobile card payment system shown in FIG. 1 includes a mobile device 10 provided by a user, an affiliated device device 20 provided in an affiliated store where a user purchases an item, and a mobile-payment gateway (M-PG) server ( 30) and the mobile communication company server 40.

The mobile device 10 will be described based on a payment method (hereinafter referred to as a 'credit card') such as a credit card, but a server-type card such as a check card, a debit card, a cash card, a point card, and a network type prepaid card as described above. Information), and a payment VM (Virtual Machine). Such credit card information and payment VM may be stored in the IC chip 11 mounted on the mobile device. Hereinafter, a description will be given on the assumption of a mobile device having an IC chip for convenience of description, but it is obvious that the VM can be implemented in an equivalent range of storage means and arithmetic means, rather than an IC chip.

The affiliated store device 20 may request payment approval by transmitting information including a phone number of the mobile device 10, identification information for identifying the affiliated store, and payment amount to the M-PG server 30.

The mobile telecommunication company server 40 may perform user authentication of the mobile device 10. The mobile communication company server 40 may include identification information (eg, UCID: USIM Chip ID), phone number, user identification number (eg, resident registration number, driver's license number, etc.) for the IC chip 11 mounted on the mobile device 10. ), A database (hereinafter referred to as 'UCID database') 41 for managing information such as information on applications stored on the IC chip (for example, applications for credit cards and prepaid cards) and whether or not a 3G phone is used. The mobile telecommunication company server 40 may perform user authentication on the mobile device 10 using the identification information and the phone number received from the mobile device 10 based on the database 41.

The mobile-payment gateway (M-PG) server 30 may receive the requested payment approval request from the merchant device 20 and, accordingly, perform user authentication through the mobile carrier server 40. When authenticated as a legitimate user by the mobile carrier server 40, the mobile-payment gateway (M-PG) server 30 sends a payment confirmation message (eg, Short Message Service: SMS or Multimedia Message Service) to the mobile device 10. : MMS, etc.) and receive the credit card information from the payment VM driven by the confirmation of the payment confirmation message. Thereafter, the M-PG server 30 performs a transaction approval procedure with the card company server 60 using the received credit card information, and transmits the transaction result to the affiliated device device 20 and the mobile device 10. Can be notified.

In this case, in the transaction approval procedure between the M-PG server 30 and the card company server 60, a transaction approval procedure may be performed through a value added network (VAN) company server 50, or an M-PG server ( An embodiment may be configured such that 30) serves as a VAN company server 50.

Hereinafter, the mobile payment procedure of the system shown in FIG. 1 will be described in detail with reference to FIGS. 2 and 3.

The IC chip 11 of the user's mobile device 10 may store IC chip identification information (eg, UCID, UICC-ID, etc.) uniquely added to the chip along with the user's credit card information. Such credit card information may be stored in plural numbers, and the mobile device 10 may not be required to receive approval from the card company 60 for every transaction. Information (offline transaction allowance, offline allowance, etc.) may further be stored in the IC chip 11.

As the mobile device 10, a third generation (G) mobile device may be used, and in this case, a universal subscriber identity module (USIM) chip may be used as the IC chip. The 3G mobile device can store information (telephone number list, call rates, additional services, etc.) stored in the existing mobile device on the USIM chip, and can also store USIM-based applications such as transportation, membership, access authentication, banking, and securities. Therefore, since only the USIM chip is replaced, the information stored independently in the mobile device terminal can be used as it is, so that the service according to the present invention can be independently applied to the mobile device 10.

In order to use the mobile payment service according to the present invention, a user may download and store an application for payment (hereinafter, referred to as 'payment VM') on the mobile device 10. The payment VM can be downloaded together with the download of the credit card information, or can be downloaded when the first payment is made. Alternatively, it may be downloaded from the M-PG server 30 at the request of the user.

2 is a flowchart illustrating a download of a payment VM when downloading credit card information. As shown in FIG. 2, after the card issuer receives a card issuance examination from the user (S201), an OTA (Over The Air) is issued. Request a customer information query, such as telephone number, MDN (mobile directory number), resident number to the mobile communication company server 40 through the center (S202). The mobile telecommunication company server 40 transmits the authentication result value (customer confirmation, 3G phone, combi UICC, UICC ID, etc.) to the card issuer through the OTA center through the user authentication procedure (S203). After confirming the user authentication result value, the card issuer prepares the issuance data (S204) and requests a message issuance notification to the OTA center (S205). The OTA center notifies the issue target to the mobile communication company server 40 (S206), and sends a message to the mobile device 10 of the user who applied for the card issuance (S207). After checking the message displayed on the screen of the mobile device 10, the user accesses the mobile communication company server 40 through the call back URL included in the message, downloads the card information to the IC chip 11 card, The credit card information is downloaded (S208). At this time, the user also downloads the payment VM (S209), and notifies the mobile communication company server 40 of the result (S210).

3 is a flowchart illustrating a mobile payment service method using a phone number of the system of FIG. 1.

As shown, when the user performs a payment, such as purchasing goods, the user indicates the intention to make a mobile payment to the merchant and provides the phone number of the mobile device 10 to the merchant device 20 (①). That is, the user can be provided with the service according to the present invention by providing only a telephone number without providing any information on the credit card, thereby preventing illegal use of the card and the like that may occur at the merchant side.

The merchant device 20 requests the M-PG server 30 to proceed with the payment along with information such as a user's telephone number, payment amount, and merchant number (②).

When the M-PG server 30 receives the payment request from the affiliated device device 20 as an operator of the service, the M-PG server 30 requests the user's mobile device server 40 to authenticate the mobile device 10 of the user. (③)

The mobile telecommunication company server 40 notifies the authentication result after performing an authentication procedure (for example, verifying a phone number and IC chip unique identification information) according to the authentication request received from the M-PG server 30 (④). ). In this case, by performing such an authentication process, even if the mobile device 10 does not receive the credit card information and the user calls the phone number and requests the payment, it is possible to prevent unnecessary transaction approval procedure. . Through this, the merchant 20 can secure such sales by inducing such a user to another payment means, and the M-PG server 30 can prevent the loss due to unnecessary data management.

Thereafter, the M-PG server 30 transmits a payment confirmation message in which the affiliate store name, payment due amount, payment progress confirmation message, etc. are specified to the user's mobile device 10 (⑤).

The user drives the payment VM stored in the mobile device 10 by checking the payment confirmation message (6). In this case, if the payment VM is not downloaded, the mobile device 10 may display a message indicating that the download is necessary because there is no payment VM on the screen of the mobile device 10, and the mobile communication company server 40 according to the user's download request. Alternatively, the payment VM may be downloaded by accessing the M-PG server 30.

In this case, a user authentication procedure may be performed when driving the payment VM. That is, a user authentication procedure may be performed by combining any one of a password (card password applied for card issuance or a password set by a user), a PIN number of a USIM chip, a user's fingerprint recognition, and a user's voice recognition. (⑥ ′). To this end, the mobile device 10 may include a fingerprint recognition module or a voice recognition module, and may set a password when the first payment VM is downloaded.

Thereafter, the mobile device 10 compares the authentication information input by the user with the set authentication information (for example, metabolizes the input password and the password stored in the IC chip) and authenticates the user. The payment approval request is transmitted to the M-PG server 30 including the credit card information and the IC chip identification information stored in the IC chip 11 (). In order to secure the credit card information and the like included in the payment request, the mobile device 10 may encrypt the payment approval request data through an encryption process (⑥ ″) and then transmit the encrypted data to the M-PG server 30.

In this case, the payment approval request may be configured to further include ON / OFF-LINE transaction classification information in addition to credit card information and IC chip identification information. That is, the transaction classification information may include whether to obtain approval for each transaction (online transaction) or whether to collect multiple transactions and receive approval in a batch (offline transaction).

The M-PG server 30 requests transaction approval from the card company server 60 using the credit card information included in the received payment approval request (⑧ '). In this case, the transaction approval may be requested through the VAN server 50 (⑧).

In this case, in the embodiment in which the transaction approval information is further included in the payment approval request, the M-PG server 30 checks the transaction classification information to determine whether the transaction is an offline transaction request. In the case of an offline transaction request, the M-PG server 30 may receive information on the number and amount of offline transactions stored in the IC chip of the mobile device 10 by communicating with the payment VM, and the number of transactions received. Payment can be made on behalf of the card company's transaction authorization within the range of and. The M-PG server 30 that has authorized the agent revises information about the number of offline transactions and the amount by reflecting the amount paid, and notifies the settlement VM of the settlement result including the modified information, and the settlement VM notifies. The information on the number of off-line transactions and amount stored in the IC chip can be updated by reflecting the settlement result of the authorized agency approval.

In addition, the M-PG server 30 records the agency approval history and provides the transaction record of the agency approval to the corresponding card company server 60 according to a user's request or a set date (for example, a specific date every month). Batch approval can be performed.

In this case, when the agency approval is performed, the embodiment may be configured to suspend the agency approval until the agency approval is actually approved by the card company. That is, when the M-PG server 30 notifies the payment result of the agency approval, the payment VM may configure the embodiment to automatically set the offline transaction allowance count and the offline transaction allowance amount to "zero". .

Subsequently, when the M-PG server 30 is an embodiment which does not perform an offline transaction or when an offline transaction is impossible, the M-PG server 30 is notified of the approval result from the server of the card company 60 (⑨, ⑨ ′), and the merchant device requesting the payment ( 20) and the customer are notified of the payment result (⑩, ⑩ ′) respectively.

In the above description, it is assumed that a user requests a payment by promptly confirming a payment confirmation message when the user receives the payment confirmation message. However, an unauthorized payment may exist because the user does not complete the transaction after receiving the payment confirmation message. The present invention can perform a repayment for the unauthorized payment, and the reason for such a repayment is that if there are several transaction data to be paid and the user does not immediately execute the payment confirmation message, the payment confirmation message is a general message. This is because it can be recorded and stored in the mobile device 10, and if it is recorded as a general message, the corresponding payment VM cannot be driven.

In order to perform repayment, the M-PG server 30 may maintain an unauthorized payment list in which a payment confirmation message is sent but transaction approval is not completed. The user who wants to perform the repayment may request and receive an unapproved payment list by accessing the M-PG server 30 by running the payment VM of the mobile device 10, and perform an unauthorized payment to be approved in the received list. You can select one or more to request repayment. In order to perform such a repayment, the payment VM may perform the above-described user authentication process and may transmit repayment request information including credit card information to the M-PG server 30. Receiving the repayment request information M-PG server 30 may use the credit card information included in the received repayment request information to complete the repayment and notify the payment result.

Alternatively, the embodiment may be configured to perform only user authentication without transmitting credit card information or the like in order to perform repayment. When the initial payment approval request is made, information already required for payment, such as payment amount and credit card information, has already been provided to the M-PG server 30, and the information necessary for the provided payment is provided in the M-PG server 30. This is because it may be held as the unauthorized payment list described above. For example, the payment VM may transmit the repayment request information to the M-PG server 30 including only user authentication information such as a card password to perform repayment.

Although the above description has been made on the assumption that one card information is stored in the IC chip 11, a plurality of card information may be stored. When a plurality of card information is stored in the IC chip 11, the embodiment is configured to perform the aforementioned payment approval request using a card selected by the user or a card determined according to a ranking set when the previous payment VM is driven. can do.

4 is a block diagram of a mobile payment system of a client card according to the present invention. The mobile card payment system according to the present embodiment will be described with reference to FIG. 1 based on differences from the mobile payment system of the server-type card described above.

As shown in FIG. 4, the mobile card payment system according to the present invention includes a mobile device 10, a merchant device 20, a mobile-payment gateway (M-PG) server 30, and a prepaid card server 70. It can be configured to include.

The mobile device 10 will be described as a payment means such as a prepaid card (hereinafter, 'prepaid card'), but may be implemented as a client type card such as a transit card as described above, an electronic money such as K-cash. ) And an integrated circuit (IC) chip that stores information about payment and a virtual machine (VM). As described above, the mobile device 10 may download and store the payment VM from the M-PG server 30.

In the prepaid card mobile payment system according to the present invention, the payment VM of the mobile device 10 is prepaid, unlike the payment system described above with reference to FIG. 1 performing a credit card payment via the M-PG server 30. There is a difference in the mobile payment by performing a direct prepaid card payment with the card server 70.

The M-PG server 30 sends a payment confirmation message to the mobile device including the merchant identification information and the payment amount included in the payment approval request received from the merchant device 20. As described above, the payment confirmation message may drive the payment VM of the mobile device. In addition, the M-PG server 30 may provide the received payment approval request to the prepaid card server 70.

The prepaid card server 70 may perform prepaid payment with the payment VM driven by the payment confirmation message, and may notify the mobile device 10 and the M-PG server 30 of the payment result for the prepaid payment. To this end, the prepaid card server 70 holds the payment authorization request provided from the M-PG server 30, and checks whether the request for prepaid payment received from the payment VM exists in the payment authorization request that it holds. If you do, you can make a prepayment.

Hereinafter, a payment service through the mobile payment system shown in FIG. 4 will be described.

The user notifies a merchant who wants to purchase an item, etc. to pay using a prepaid card, and informs the telephone number of the mobile device 10 that is being carried (①).

The merchant device 20 transmits a payment approval request including information on the phone number, the merchant identification number, and the payment amount to the M-PG server 30 (②). At this time, the payment means may further include information for confirming that the prepaid card may perform the payment approval request.

 After confirming that the payment method is a prepaid card, the M-PG server 30 notifies the prepaid service provider 405 of the payment approval request including information such as merchant number and amount (③), and the prepaid service provider 405 pays the payment. The authorization request is stored in the payment waiting database (DB).

In addition, the M-PG server 30 sends a payment confirmation message including the contents of the blind spot name, payment amount, payment progress confirmation, etc. to the mobile device 10 (④). In this case, the M-PG server 30 may send a payment confirmation message through the mobile communication company server 40 after performing the mobile device authentication as described above through the mobile communication company server 40. Since the description of the mobile communication company server 40 is as described above with reference to FIG. 1, a detailed description thereof will be omitted.

The user may drive the payment VM by performing a payment progress check on the payment confirmation message received by the mobile device 10 (⑤). Before the payment VM is driven, the user authentication process may be performed. The authentication process may be performed by combining at least one or a combination of a password, a PIN number, fingerprint information, and voice information as described above (6).

In this case, when the payment VM is not stored in the mobile device 10 even though the user receives the payment confirmation message, the payment VM may be received and stored by communicating with the M-PG server 30. In order to receive the payment VM, it is preferable that the payment confirmation message further includes information on a communication path for downloading the payment VM from the M-PG server.

The payment VM of the mobile device 10 requests payment approval from the corresponding prepaid card server 70 including merchant identification information, prepaid card information, and payment amount (⑦). In performing the communication for payment approval between the payment VM and the prepaid card server 70, it may be accompanied by encryption to enhance security. For example, authentication or encrypted communication with the prepaid card server 70 may be performed using a key included in the prepaid card information stored in the IC chip 11 of the mobile device.

The prepaid card server 70 checks whether the payment authorization request received from the payment VM is stored in the payment standby DB (that is, whether the payment authorization request has been reached from the M-PG server), and the payment of the payment VM. If a payment approval request corresponding to the request exists in the payment standby DB, the payment is approved by performing a prepaid payment.

The prepaid card server 70 then notifies the mobile device 10 of the approved payment result (8) and also notifies the M-PG server 30 (9). At this time, in the notification of the completion of the payment, it may be included, including information on the remaining prepaid amount subtracted from the payment approval amount.

The M-PG server 30 provides a payment result notified from the prepaid card server 70 to the affiliated store device 20 (⑩).

The merchant side confirms the payment confirmation information displayed on the merchant device 20 and provides the user with goods (iii).

The mobile communication company server 40 manages identification information of the IC chip of the mobile device 10 as a database. In addition, the mobile telecommunication company server 40 may perform authentication of the mobile device 10 using the identification information and the telephone number of the IC chip received from the M-PG server 30. In addition, the mobile communication company server 40 may send a payment confirmation message at the request of the M-PG server 30.

Hereinafter, a mobile payment system for a server-type card and a client-type card according to another embodiment of the present invention will be described. This embodiment may be configured by combining the mobile payment system of the server-type card of Figure 1 and the mobile payment system of the client-type card of FIG.

The mobile payment system according to the present embodiment may include a mobile device 10, a merchant device 20, an M-PG server 30, a credit card server 60, and a prepaid card server 70.

The mobile device 10 of the user may include an IC chip that stores card information and a payment VM. In this case, the card information may include any one or all of server-type card (hereinafter described and described as 'credit card') information and client-type card (hereinafter described and described as 'prepaid card') information. . In this case, the payment VM preferably includes both the credit card payment VM described above with reference to FIG. 1 and the prepaid card payment VM described above with reference to FIG. 4.

In addition, as described above, the mobile device 10 may perform a user authentication by combining at least one or a combination of password, PIN number, fingerprint recognition and voice recognition in driving the payment VM, and also to the mobile device 10 If there is a plurality of stored card information, payment can be requested by selecting a card according to a user's selection or a set rank.

The affiliated store device 20 may request the M-PG server 30 for payment approval, including the type of card to be paid, the user's telephone number, the merchant identification number, and the payment amount. At this time, the type of card to be paid may be a credit card or a prepaid card, which should correspond to the card information stored in the user mobile device 10.

When the M-PG server 30 receives the payment approval request, the M-PG server 30 determines which kind of card the request is, and performs the mobile payment as described above with reference to FIG. As described above with reference to FIG. 3, mobile payment may be performed.

That is, if the card type of the received payment approval request is a prepaid card, the mobile device 10 sends a prepaid payment confirmation message for driving the payment VM to the mobile device 10 to perform mobile prepaid with the prepaid card server 70. Can ship. Alternatively, if the card type is a credit card, a credit payment confirmation message for driving authorization of the payment VM may be sent to the mobile device 10. This is for receiving the credit card information from the payment VM driven by the credit check confirmation message and performing transaction approval with the card company, and notifying the merchant device 20 and the mobile device 10 of the approved payment result. As described above.

Before sending this message, as described above, a procedure for authenticating the mobile device 10 may be performed. That is, the M-PG server 30 may authenticate the mobile device by providing the IC chip identification information and the telephone number of the mobile device 10 to the mobile communication company server having the database of the IC chip identification information.

In addition, when the payment VM is not stored in the mobile device 10, the mobile device may download the payment VM through the M-PG server 30. That is, the payment confirmation message may further include information such as a path for downloading the payment VM of the M-PG server 30.

In more detail about the prepaid payment method, the M-PG server 30 provides a payment approval request received from the mobile device 10 to the prepaid card server 70. The mobile device 10 receives the prepaid payment confirmation message and checks it to drive the payment VM. The payment VM includes the prepaid card server 70 and the mobile prepaid, including information such as merchant information and payment amount, as described above. Payment can be performed. In this case, the prepaid card server 70 checks whether there is a prepaid card payment request requested from the payment VM during the payment authorization request provided from the M-PG server 30, and if so, performs the prepaid payment from the payment VM. . Thereafter, the prepaid card server 70 may provide the payment result to the mobile device 10 and the M-PG server 30 according to the result of performing the prepaid payment. It may include information such as a prepaid amount of money. The M-PG server 30 receiving the payment result may notify the mobile device 10 of the payment result again to perform the payment result check.

5 is a flowchart of a mobile card payment system for server-type card and client-type card payment according to 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.

When the M-PG server 30 receives the payment request from the affiliated device device 20, the M-PG server 30 checks the type of payment card included in the payment request (S510). The payment request may include information on the type of payment card, the phone number of the mobile device, merchant identification information, and information on the payment amount.

The M-PG server 30 checks the type of payment card (S520), if the type of payment card is a prepaid card, sends a prepaid payment confirmation message to the mobile device 10 (S521) and prepays the received payment request. The card server 70 is provided. In this case, the prepaid payment confirmation message may drive the payment VM of the mobile device 10, and may include affiliate store identification information and a payment amount. The mobile device 10 that has received the prepaid payment confirmation message may drive the payment VM by checking the prepaid payment confirmation message, and the payment VM includes the prepaid card information, the merchant identification information, and the payment amount information. Request to approve the mobile prepayment (S522). The prepaid card server 70 performs the mobile payment and notifies the mobile device 10 and the M-PG server 30 of the payment result, and the M-PG server 30 notifies the merchant device 20 of the received payment result. (S523).

If the M-PG server 30 confirms that the payment card is a credit card, the M-PG server 30 sends a credit confirmation message to the mobile device 10 (S531). Thereafter, the credit card server 60 receives the credit card information from the payment VM driven by the mobile device 10 that has acknowledged the credit payment confirmation message, and the credit card server 60 receives information on the credit card information, the merchant identification information, and the payment amount. The mobile credit settlement request is requested (S532). If the M-PG server 30 approves the payment at the credit card server 60, the M-PG server 30 may notify the mobile device 10 of the approved payment result.

In addition, as described above, the M-PG server 30 may provide identification information and phone number of the IC chip of the mobile device to the mobile communication company server 40 to perform authentication of the mobile device.

In addition, the M-PG server 30 may receive the authorization information for the prepaid payment or credit payment performed from the corresponding prepaid card server 70 or credit card server 60 to notify the mobile device 10.

The above-described mobile payment method is characterized in that the user confirms the payment confirmation message using the mobile device 10. This is when the user receives the message but does not confirm to actually make the payment, the payment is not completed, i.e., the transaction is not completed. Therefore, the M-PG server 30 preferably stores and manages information (for example, in the form of a list or a database) about such unauthorized prepaid payment or unauthorized credit settlement.

In addition, since the unapproved payment details are stored, an embodiment may be configured to perform post approval using the unauthorized payment details. In more detail, the M-PG server 30 may provide the mobile device 10 with information about the aforementioned unauthorized payment, and when receiving a message requesting post-approval from the user who has confirmed this, Post-approval can be achieved by re-running one prepayment or credit settlement process.

As mentioned above, although this invention was demonstrated in detail with reference to attached drawing, this is only an illustration, It is clear that various deformation | transformation and a change are possible within the scope of the technical idea of this invention. Therefore, the protection scope of the present invention should not be limited to the above-described embodiment, but should be determined to include the scope according to the description of the following claims and their equivalents.

1 is a block diagram of a mobile card payment system using a phone number of the server-type card according to the present invention.

2 is a flowchart illustrating downloading a payment VM when downloading the credit card information of FIG. 1.

3 is a payment flowchart of a mobile card payment system using the phone number of FIG.

4 is a block diagram of a mobile payment system of a client card according to the present invention.

Figure 5 is a flow chart of a mobile card payment system for server-type card and client card payment according to the present invention.

Claims (23)

A mobile device having client type card information and payment VM (Virtual Machine) including at least one of a prepaid card, a transportation card, and an electronic money card; A merchant device requesting payment approval including a phone number of the mobile device, merchant identification information, and a payment amount; A mobile-payment gateway (M-PG) server that sends the payment confirmation message including the affiliated store identification information of the received payment approval request and the payment amount and authorizes driving the payment VM to the mobile device; And And a prepaid card server for performing a mobile prepaid payment in association with the payment VM in the mobile device receiving the payment confirmation message. The method of claim 1, The merchant device further requests for payment approval, further including identification information of the client chip and IC chip storing the payment VM, And a mobile telecommunication company server which manages identification information of the IC chip in a database, and performs authentication of the mobile device with the identification information and the telephone number of the IC chip provided from the M-PG server. . The method of claim 2, The M-PG server sends the payment confirmation message through the mobile communication server, The mobile communication company server performs the authentication on the mobile device before sending the payment confirmation message mobile card payment system. The method of claim 1, wherein the mobile device, And receiving and storing the payment VM from the M-PG server using information on a communication path with the M-PG server further included in the payment confirmation message. The method of claim 4, wherein the mobile device, By running the payment VM by the user confirms the received payment confirmation message, Mobile card payment system to perform the authentication by combining at least one or a combination of at least one of the password, PIN number and fingerprint information to drive the payment VM. The method of claim 1, wherein the prepaid card server, The mobile card payment system further comprises a payment standby database (DB) for storing the payment approval request received from the M-PG server. The method of claim 6, wherein the prepaid card server, And if the payment approval request corresponding to the mobile prepayment request received from the payment VM exists in the payment standby DB, approving the mobile prepayment request. The method of claim 1, wherein the prepaid card server, And notifying the affiliated device device of the payment result through the M-PG server and notifying the mobile device through the payment VM. A mobile device in which server-type card information including at least one of a credit card, a check card, a debit card, a cash card and a point card and a payment VM are embedded; A merchant device requesting payment approval including a phone number of the mobile device, merchant identification information, and a payment amount; A mobile telecommunication company server for performing user authentication of the mobile device; And The user authentication is performed through the server of the mobile communication company with respect to the received payment approval request, and according to the authentication result, a payment confirmation message for driving and authorizing the payment VM is sent to the mobile device to receive the information of the server-type card. And a mobile-payment gateway (M-PG) server that receives and receives a transaction approval from the card company server with the received server-type card information. The method of claim 9, The mobile device further includes information about the number of offline transactions and amount, The affiliated device further includes a transaction classification information for an online transaction or an offline transaction to request the payment approval. The M-PG server, if the transaction classification information is an offline transaction, the mobile card payment system for billing on behalf of the transaction authorization of the card company within the range of the information on the number of offline transactions and amount. The method of claim 10, wherein the mobile device, The mobile card payment system to update the information on the number of offline transactions and the amount of money reflecting the payment result of the agency approval notified from the M-PG server. The method of claim 9, wherein the mobile device, And if the information on the embedded server-type card is plural, performing the payment authorization request for the server-type card of the selected order or the set rank. The method of claim 9, wherein the M-PG server, Mobile card payment system that has sent the payment confirmation message, but holds an unauthorized payment list that has not completed the transaction approval. The method of claim 13, The mobile device requests the M-PG server for the unauthorized payment list and requests the M-PG server to repay at least one unauthorized payment selected from the received unauthorized payment list accordingly. The M-PG server, the mobile card payment system for performing a transaction approval with the card company as the information of the server-type card for the unauthorized payment requested for re-payment. A mobile device having at least one payment card information and a payment VM installed therein; A merchant device requesting payment approval including information on the type of the payment card making a payment request, a phone number of the mobile device, merchant identification information, and a payment amount; And If the payment card type of the received payment approval request is a client type card, the mobile device sends a first payment confirmation message for driving the payment VM to the mobile device to perform mobile prepaid with the prepaid card server. If the payment card type is a server-type card, the mobile device sends a second payment confirmation message to authorize driving the payment VM, receives the server-type card information from the payment VM, and requests a transaction approval from the card company. Mobile-Payment Gateway (M-PG) server; comprising a mobile card payment system. The method of claim 15, wherein the M-PG server, And receiving the prepaid amount information reflecting the performance of the mobile prepaid payment from the prepaid card server and notifying the mobile device. The method of claim 15, wherein the M-PG server, And if the payment VM is not embedded in the mobile device that has received the first or second payment confirmation message, providing the payment VM to the mobile device. The method of claim 15, wherein the mobile device, In order to drive the payment VM, at least one of a password, PIN number, fingerprint recognition and voice recognition or a combination thereof to perform a user authentication mobile card payment system. The method of claim 15, wherein the mobile device, The mobile card payment system of the plurality of cards included in the payment card information, by the selection or by the card of the set order to perform the payment authorization request. Receiving a payment request including a type of payment card, a user's mobile device telephone number, merchant identification information, and a payment amount, and confirming the type of the payment card; If the type of payment card is a client-type card as a result of the checking, a first payment confirmation message including the affiliated store identification information and the payment amount is sent to the mobile device, and the mobile device sends the first payment confirmation message. A prepaid payment step of performing a mobile prepaid payment with a prepaid card server using the payment VM driven by checking; And If the type of payment card is a server-type card, a second payment confirmation message including the affiliated store identification information and the payment amount is sent to the mobile device and received from the payment VM driven by confirming the second payment confirmation message. The mobile payment service method comprising the; crediting step of performing a mobile credit settlement with the card issuer server using the information of the server-type card. The method of claim 20, And providing identification information and a telephone number of an integrated circuit (IC) chip of the mobile device to a mobile communication company server to perform authentication of the mobile device. The method of claim 20, If the mobile device that has received the first payment confirmation message or the second payment confirmation message does not perform the prepayment or the credit settlement, a list of the prepayment or the credit settlement for which the transaction approval is not completed is completed. Mobile payment service method further comprising; generating an unauthorized list to store. The method of claim 22, (I) providing an information about the prepaid payment or the credit payment included in the unapproved list to the mobile device and completing the unauthorized prepaid payment or credit payment according to the re-payment request of the mobile device; Mobile payment service method further comprising.

Images