KR20100129028A - Method for mobile payment and system thereof - Google Patents

Abstract

PURPOSE: A method for a mobile payment and a system thereof are provided to enable an MPG(Mobile Payment Gateway) to conveniently inquire the main card number of a payer based on payer identification information including a name and a mobile terminal number of the payer. CONSTITUTION: A mobile payment server receives payer identification information and transaction information from a franchise terminal(S210) and requests, from a card company server, the inquiry of the main card number of the payer matched with the payer identification number(S220). Based on the main card number inquired by the card company server, the mobile payment server generates payment request information(S250). The mobile payment server transmits the payment request information to a payer mobile server(S260).

Description

Mobile payment method and system

The present invention relates to a payment method, in particular to a mobile payment method and system.

 In recent years, the development of communication, mobile terminals and electronic commerce are rapidly developing. Thus, by transmitting and approving credit card information using a mobile terminal and a network owned by an individual, the importance of a mobile payment system that can perform e-commerce more securely is emerging.

An object of the present invention is a mobile payment gateway (MPG) to easily search the main card number of the payer using the billing party identification information including the name of the payer and the mobile terminal number, the card number It is to provide a mobile payment method and system that can be easily purchased and traded using.

In addition, an object of the present invention is to provide a mobile payment method and system in which a merchant terminal directly transmits a biller identification number to a payment card company, and the payment card company directly connects to the payer to process a payment.

The present invention for achieving the above object, in the mobile payment method of a mobile payment system comprising a merchant terminal, a mobile payment server, a card company server and a payer mobile terminal, the mobile payment server to identify the payer from the merchant terminal Receiving information and transaction information, the mobile payment server requesting the card company server to query the main card number of the payer that matches the payer identification information, and the mobile payment server is inquired from the card company server It provides a mobile payment method comprising the step of generating payment request information based on the use card number and transmitting to the payer mobile terminal.

As described above, in the mobile payment method and system according to an embodiment of the present invention, an object of the present invention is to identify a payer in which a mobile payment server (MPG) includes a payer's name and a mobile terminal number. It is possible to easily look up the payer's main use card number using the information, and more easily purchase transactions using the inquired main use card number.

In addition, in the mobile payment method and system according to an embodiment of the present invention, the merchant terminal directly transmits the biller identification number to the payment card company, and the payment card company directly connects to the payer to process payment.

Other objects, features and advantages of the present invention will become apparent from the following detailed description of embodiments taken in conjunction with the accompanying drawings.

Hereinafter, with reference to the accompanying drawings, preferred embodiments of the present invention that can specifically realize the above object will be described. At this time, the configuration and operation of the present invention shown in the drawings and described by it will be described as at least one embodiment, by which the technical spirit of the present invention and its core configuration and operation is not limited.

The terms used in the present invention have been selected as widely used general terms as possible in consideration of the functions in the present invention, but may vary according to the intention or custom of the person skilled in the art, the emergence of new technologies, and the like. In addition, in certain cases, there is also a term arbitrarily selected by the applicant, in which case the meaning will be described in detail in the description of the invention. Therefore, it is intended that the terms used in the present invention should be defined based on the meanings of the terms and the general contents of the present invention, rather than simply the names of the terms.

Throughout the specification, a mobile payment system (MPG) is a system that can conveniently perform a payment service anytime and anywhere using a mobile terminal. The mobile payment system may be made by inputting a password and confirming a message transmitted to a mobile terminal of a customer without pre-registration and inputting a card number.

Throughout the specification, a mobile terminal is a terminal capable of real-time wireless communication. The mobile terminal may include a mobile phone, a mobile phone such as a cellular phone, a smart phone, a personal digital assistant, a netbook, and the like. Can be. In particular, the netbook is a type of mobile terminal that is in the spotlight recently. The netbook aims to use simple Internet-oriented services such as browsing contents of a website based on HTML (Hyper-Text Markup Language) or a screen, e-mail, or chatting.

In the entire specification, payer identification information refers to information for authenticating and identifying individual payers. The payer identification information may include the name of the payer, the mobile phone number and payment card company information that issued the card to be paid by the payer. The payer identification information may be input from a customer through an affiliated store terminal. The payer identification information may be delivered to the customer's shoes. In addition, the payer identification information may be input to the affiliated store terminal using Near Field Communication (NFC). The short range communication may include Bluetooth, Zigbee, Infrared Data Association (IrDA), RF (Radio Frequency), and the like.

In the entire specification, the merchant terminal is a means for paying the purchase price by using the credit card information of the customer who purchased the product or service. The merchant terminal may include an electronic ordering system (EOS), a point of sales (POS) terminal, a credit authorization terminal (CAT), and a mobile phone on which merchant phone software is installed. In more detail, the EOS is an abbreviation for an online order / ordering system, and is an ordering method that issues delivery and purchase slips by directly transmitting ordering data to a computer of an ordering party through a ordering terminal using a telephone line. The POS is a system used for point of sale information management. The POS system may comprehensively manage sales affairs, market research, inventory research, and point of sale management using a POS terminal connected to an affiliated computer. The CAT is a credit card reader. The CAT can automatically read the issuing company, member number, etc. displayed on the credit card, and find out the credit rating of the credit card holder from the card issuing company through the communication line. The CAT may query online through the issuing server which issued the credit card when the payment is made using the credit card at the affiliated store to inquire the usage limit of the credit card, accident and invalidity, and sales processing.

Throughout the specification, a WAP (Wireless Application Protocol) server is a wireless Internet markup language suitable for a wireless terminal having limited resources and a narrow data transmission and reception bandwidth. The mobile WAP server may be a server operated by the mobile payment server, or may be a server operated by the card company server. On the other hand, the mobile WAP server is a server that is operated separately from the mobile payment server and the card company server, its operation may vary depending on the cooperation with other servers. The mobile WAP server may be built in the mobile payment server or the card company server to perform a payment processing function using the card of the payer.

1 is a configuration diagram schematically showing a mobile payment system according to an embodiment of the present invention, Figure 2 is a flow chart schematically showing a mobile payment method according to an embodiment of the present invention.

Hereinafter, the mobile payment method shown in FIG. 2 will be described with reference to the mobile payment system according to the present invention shown in FIG. 1.

As shown in FIG. 1, the mobile payment system according to the present invention may include a merchant terminal 110, a mobile payment server 120, a card company server 130, and a payer mobile terminal 140.

First, the mobile payment server 120 receives the payer identification information and transaction information transmitted from the affiliated store terminal 110 [S210]. The payer identification information may include a payer's name and a mobile terminal number. The transaction information may include affiliate store information, purchase details, and transaction amount. The payer identification information may be transmitted to the affiliated store terminal 110 verbally or online through a customer (not shown). In this case, the customer may be a purchase requester who requests the purchase of goods and services. The customer may be a payer who pays for the purchase price of goods and services purchased by the purchase requester. In addition, the customer may be a subject that simultaneously performs the role of the purchase requester and the payer. The payer identification information may be input to the affiliated store terminal 110 from the customer through near field communication (NFC). The short range communication may include Bluetooth, Zigbee, Infrared Data Association (IrDA), RF (Radio Frequency), and the like.

Meanwhile, the affiliated store terminal 110 may include an electronic ordering system (EOS), a point of sales (POS) terminal, a credit authorization terminal (CAT), and a mobile phone on which merchant phone software is installed. The merchant terminal 110 may store the payer identification information in the form of a database. Therefore, the payer identification information, which is built in the affiliated store terminal 110 as a database, may be searched and extracted by the command of the affiliated store terminal 110 and transmitted to the mobile payment server 120.

In addition, the mobile payment server 120 may search for the payment card company to request the main payment card number of the payer based on the purchase history of the payer [S220]. The purchaser's purchase history may include whether recent transactions of the payer-owned cards have occurred, a transaction frequency, a total transaction amount, and the like. For example, the mobile payment server 120 searches the main use card of the payer by comparing and analyzing the purchase history of various cards stored in a separate database. In addition, the card company where the main use card is issued may be selected as a payment card company. Therefore, the main payment card of the payer found based on the purchase history of the payer may be searched, and the payment card company may be requested to search the main use card of the payer only. In the same manner as described above, the mobile payment system 120 can be used simply without a separate card registration procedure, and the personal information of the payer can be protected.

Then, the mobile payment server 120 transmits the payer identification information to the card company server 130, and receives the main use card number of the payer from the card company server 130 [S230, S240]. For example, the mobile payment server 120 transmits the payer identification information to the card company server 130. Then, the card company server 130 inquires all the use card of the payer that matches the received payer identification information. Then, the card company server 13 selects the main use card mainly used by the payer with reference to the purchase history of the inquired cards. In this case, the purchase history may be received from the mobile payment server 120 together with the payer identification information. The purchase history may include whether a recent transaction of the card has occurred, a transaction frequency, a total transaction amount, and the like. Therefore, the mobile payment server 120 can easily search the payment card company to be paid by the payer based on the purchase history of the payer separately stored.

Thereafter, the mobile payment server 120 generates payment request information based on the main use card number of the payer transmitted from the card company server 130 and transmits it to the payer mobile terminal 140 [S250, S260]. , S270]. The payment request information may be generated in the form of a mobile phone message service such as a short message service (SMS) or a multimedia messaging service (MMS). The payment request information may include a URL of a mobile WAP server (not shown) that provides payment information. The payment information may include purchase details, merchant information, payment amount, installment months, main use card information, and the like.

Then, when a payment acceptance signal is input to the payer mobile terminal 140 receiving the payment request information from the payer, the payer mobile terminal 140 is automatically connected to the mobile WAP server linked to the URL to pay The process is performed [S280]. The mobile WAP server may be a server operated by the mobile payment server 120 or may be a server operated by the card company server 130. On the other hand, the mobile WAP server is a server that is operated separately from the mobile payment server 120 and the card company server 130, the operation method may vary depending on the partnership with other servers. In addition, the mobile WAP server may be built in the mobile payment server 120 or the card company server 130 to perform a payment processing function using the card of the payer.

The payment processing performed afterwards will be described below with reference to FIG. 3.

As another embodiment, the mobile payment system may be made without the configuration of the mobile payment server 120. In order to implement the mobile payment system as described above, the card company server 130 may take the role of the mobile payment server 120. That is, the merchant terminal 110 directly transmits the payer identification information of the payer to the card company server 130, and the card company server 130 directly sends a session to the payer mobile terminal 140. You can connect and perform payment processing.

In more detail, the card company server 130 receives the payer identification information and transaction information from the affiliated store terminal (110). In this case, the payer identification information may include the name of the payer and the mobile terminal number. The merchant terminal 110 may transmit the payer identification information received from the customer to the card company server 130. In addition, the affiliated store terminal 110 may search and extract the payer identification information of the corresponding payer from a database that is separately constructed and transmit the same to the card company server 130.

Thereafter, the card company server 130 inquires the main use card number of the payer matching the received payer identification information. The card company server 130 may inquire the main use card number of the payer based on the purchase history of the payer. The purchase history may include whether a recent transaction of the card has occurred, a transaction frequency, a total transaction amount, and the like.

The card company server 130 generates payment request information based on the inquired main use card number and transmits the generated payment request information to the payer mobile terminal 140. In this case, the payment request information may be generated in the form of a mobile phone message service such as SMS or MMS including the URL of the mobile WAP server providing the payment information.

Then, when a payment acceptance signal is input to the payer mobile terminal 140 receiving the payment request information, the payer mobile terminal 140 is automatically connected to the mobile WAP server linked to the URL to perform payment processing. do. The mobile WAP server may be a server operated by the card company server 130. In addition, the mobile WAP server is a server that is operated separately from the card company server 130, and its operation may be changed according to the partnership with the card company server 130. In this case, the card company server 130 may connect a session directly to the payer mobile terminal 140 to perform the payment process with the payer's mobile terminal 140.

3 is a flowchart schematically illustrating an operation flow of a payment processing process according to an embodiment of the present invention.

As shown in FIG. 3, the mobile payment server 120 transmits payment request information to the payer mobile terminal 140 [S310]. The mobile payment server 120 may generate the payment request information based on the transaction information transmitted from the affiliated store terminal 110. For example, the payment request information generated by the mobile payment server 120 may be in the form of a mobile phone message service such as SMS or MMS including a call-back URL. In this case, the callback URL may be a URL of a mobile WAP server (not shown) that provides payment information. In addition, the mobile payment server 120 may generate the payment request information based on the main use card number of the payer transmitted from the card company server 130. The main use card may be determined based on the purchase history of the payer stored in the database form in the mobile payment server 120. The purchase history may include whether a recent transaction of the card has occurred, a transaction frequency, a total transaction amount, and the like.

When the payment acceptance signal is input to the payer mobile terminal 140, the payer mobile terminal 140 is automatically connected to the mobile WAP server and receives payment information from the mobile WAP server [S320, S330, S340. ]. For example, the payer confirms payment request information in the form of the received SMS or MMS. When the payer presses the confirmation button of the payer mobile terminal 140 in the corresponding page, the payer may be automatically connected to the mobile WAP server linked to the URL. In this case, the mobile WAP server may be a server operated by the mobile payment server 120 or the card company server 130. In addition, the mobile WAP server is a server that is operated separately from the mobile payment server 120 and the card company server 130, and its operation may be changed according to the cooperation with other servers. The payment information may include purchase details, merchant information, payment price, installment months, main use card information, and the like. In addition, the mobile WAP server may be built in the mobile payment server 120 or the card company server 130 to perform a payment processing function using the card of the payer.

Subsequently, when the payer displays the intention of accepting payment processing (pressing the confirmation button) using the main use card in the payer mobile terminal 140, the mobile WAP server receives authentication information from the payer mobile terminal 140. Request and receive [S350, 360]. In this case, the payer mobile terminal 140 may provide authentication information in the form of a public certificate to the mobile WAP server.

When the payment is approved using the received authentication information, the mobile WAP server notifies the payer mobile terminal 140 of the approved payment result [S370, S380]. The mobile WAP server transmits the authentication information received from the payer mobile terminal 140 to the card company server 130 to request payment approval. Thereafter, when the payment is completed by the card company server 130, the mobile WAP server transmits the payment result to the payer mobile terminal 140 and the merchant terminal 110. The result may be transmitted in the form of SMS or MMS. In this case, payment approval may also be requested through connection with the mobile payment server 120 using software such as a virtual machine (VM) executed in the payer mobile terminal 140. And in the same manner as described above, it is possible to implement the same payment approval effect.

On the other hand, when the payment processing rejection signal using the main use card is input to the payer mobile terminal 140, the mobile WAP server provides other card information owned by the payer to the payer mobile terminal 140. [S350, S390]. For example, a payment processing reject signal using the main use card is input to the payer mobile terminal 140 by the payer. Then, the mobile payment server 120 or the card company server 130 linked to the mobile WAP server inquires all the cards owned by the payer except the main use card of the payer, and the information of the inquired cards It may be provided to the payer mobile terminal 140. In this case, the inquired payer-owned card may include cards issued by other card companies in addition to the card company server 130 that issued the main use card. The payer owned card may be searched and provided based on the purchase history of the payer. In addition, the mobile payment server 120 and the card company server 130 directly provides the card information of the inquiring payer owned card to the payer mobile terminal 140, or transmits the payment information to the mobile WAP server. It can be processed into a shape and provided.

4 is a diagram illustrating a mobile payment method when a purchase requester and a payer are the same according to an embodiment of the present invention.

As shown in FIG. 4, when the purchase requester and the payer are the same, the mobile payment system according to the present invention uses the customer 410, the merchant terminal 420, the mobile payment server 430, and the payment card company server 440. It can be configured to include. In addition, the service provider may further include a plurality of other card company servers 451, 452, and 453.

First, the customer 410 purchases goods and services at a merchant. In addition, the customer 410 inputs biller identification information through the affiliated store terminal 420 to pay for the purchase. In this case, the customer 410 is a subject that performs both the purchase requester and the payer. Accordingly, the customer 410 who purchased the goods and services may become a purchase requester and a payer. The payer identification information may be input by the customer 410 requesting the purchase. For example, the customer 410 notifies the merchant identification information verbally to the affiliated employee. Then, the affiliated store employee may input the payer identification information notified from the customer 410 to the affiliated store terminal 420. In addition, the payer identification information may be directly input from the customer 410 to the affiliated store terminal 420 through online input or near field communication (NFC).

Then, the mobile payment server 430 receives the payer identification information and transaction information transmitted from the merchant terminal 420. The payer identification information may include a payer's name and a mobile terminal number. The transaction information may include affiliate store information, purchase details, and transaction amount.

In addition, the mobile payment server 430 transmits the received payer identification information to the payment card company server 440 and requests the card company server 440 to query the main use card of the customer 410. In this case, the mobile payment server 430 may find out the main credit card payment card company of the customer 410 with reference to the purchase history of the customer 410 built in a separate database. In addition, the payer identification information may be transmitted only to the payment card company server 440 that issues the main use card.

Then, the payment card company server 440 inquires the main use card number of the payer that matches the received payer identification information and transmits to the mobile payment server 430.

Thereafter, the mobile payment server 430 generates payment request information based on the received main use card number. The payment request information is transmitted to the mobile terminal of the customer 410 to request payment from the customer 410. The payment request information may be generated in the form of a mobile phone message service such as a short message service (SMS) or a multimedia message service (MMS) including a URL of a mobile WAP server (not shown) that provides payment information. The mobile WAP server may be a server operated by the mobile payment server 430 or may be a server operated by the card company server 440. On the other hand, the mobile WAP server is a server that is operated separately from the mobile payment server 430 and the card company server 440, the operation method may vary depending on the cooperation with other servers. In addition, the mobile WAP server may be built in the mobile payment server 430 or the card company server 440 to perform a payment processing function using the card of the payer.

Then, the mobile terminal of the customer 410 that has received the payment request information receives a payment acceptance signal input from the customer 410. Then, the mobile terminal of the customer 410 is automatically connected to the mobile WAP server linked to the URL to receive payment information from the mobile WAP server. The payment information may include purchase details, merchant information, payment amount, installment months, main use card information, and the like.

Thereafter, the mobile terminal of the customer 410 receives a payment processing acceptance signal using the main use card input from the customer 410. Then, the mobile WAP server may request and receive authentication information from the mobile terminal of the customer 410. In this case, the authentication information of the mobile terminal may be implemented in the form of an authorized certificate or encrypted password.

If payment is approved using the received authentication information, the mobile WAP server may notify the mobile terminal of the customer 410 of the approved payment result. In this case, the payment approval may also be requested through the connection with the mobile payment server 430 using software such as a VM (Virtual Machine) executed in the mobile terminal of the customer 410. And in the same manner as described above, it is possible to implement the same payment approval effect. The mobile WAP server transmits the authentication information received from the mobile terminal of the customer 410 to the card company server 440 to request payment approval. Then, when the payment is completed by the card company server 440, the mobile WAP server transmits the payment result to the mobile terminal and the merchant terminal 420 of the customer 410.

On the other hand, if a payment processing rejection signal using the main use card is input to the mobile terminal of the customer 410 or there is no input for a predetermined time or more, the mobile WAP server sends the customer 410 to the mobile terminal of the customer 410. It provides information of owned other cards (451, 452, 453). For example, the customer 410 inputs a payment processing rejection signal using the main use card to the mobile terminal of the customer 410. Then, the mobile payment server 430 or the card company server 440 linked to the mobile WAP server, all the cards 451, 452, owned by the customer 410 except for the main use card of the customer 410, 453). At this time, other cards 451, 452, and 453 except the inquired main use card may include cards issued through other card companies in addition to the payment card company.

The customer 410 may request a payment by selecting a desired card among other cards 451, 452, and 453 provided from the mobile payment server 430.

5 is a diagram schematically illustrating a mobile payment method when a purchase requester and a payer are different according to an embodiment of the present invention.

As shown in FIG. 5, when the purchase requester and the payer are not the same, the mobile payment system according to the present invention includes a purchase requester 510, a merchant terminal 520, a mobile payment server 530, and a card company server 540. And a payer mobile terminal 560. In addition, the service provider may further include a plurality of other card company servers 551, 552, and 553.

First, the purchase requester 510 purchases goods and services at an affiliated store and inputs payer identification information through the affiliated store terminal 520.

Then, the mobile payment server 530 receives the payer identification information and transaction information transmitted from the affiliated store terminal 520. In this case, the payer identification information is a subject who pays for the goods and services purchased by the purchase requester 510. The payer identification information may include a payer's name and a mobile terminal number. The transaction information is information generated according to the purchase of the purchase requester 510 and may include affiliate store information, purchase history, and transaction amount. The payer identification information may be transmitted orally to the affiliated store employee by the purchase requester 510 and input to the affiliated store terminal 520 by the affiliated store employee. In addition, the purchase requester 510 may input the payer identification information to the merchant terminal 520 through online or near field communication (NFC). In this case, the short range communication may include Bluetooth, Zigbee, Infrared Data Association (IrDA), and RF (Radio Frequency).

In addition, the mobile payment server 530 transmits the payment identification information received from the merchant terminal 520 to the payment card company server 540 to request the main use card number of the payer. In this case, the mobile payment server 530 may find out the issuing card company of the main use card mainly used by the payer based on the purchase history of the payer that is built in a separate database. The payment card company server 540 issuing the main use card may be transferred to the payment card identification information to request the main use card number of the payer.

Then, the payment card company server 540 receives the payer identification information transmitted from the mobile payment server 530. In addition, the payment card company server 540 inquires the main payment card number of the payer that matches the received payment information, and transmits to the mobile payment server 530.

Thereafter, the mobile payment server 530 generates payment request information based on the received main use card number. The payment request information is transmitted to the payer mobile terminal 560 to request payment from the payer. The payment request information may be generated in the form of a mobile phone message service such as a short message service (SMS) or a multimedia message service (MMS) including a URL of a mobile WAP server (not shown) that provides payment information. The mobile WAP server may be a server operated by the mobile payment server 530 or may be a server operated by the card company server 540. On the other hand, the mobile WAP server is a server that is operated separately from the mobile payment server 530 and the card company server 540, the operation method may vary depending on the cooperation with other servers. In addition, the mobile WAP server may be built in the mobile payment server 530 or the card company server 540 to perform a payment processing function using the card of the payer.

Then, the payer mobile terminal 560 receiving the payment request information receives a payment acceptance signal input from the payer. Then, the payer mobile terminal 560 is automatically connected to the mobile WAP server linked to the URL to receive payment information from the mobile WAP server. The payment information may include purchase details, merchant information, payment amount, installment months, main use card information, and the like.

Thereafter, the payer mobile terminal 560 receives a payment processing acceptance signal using the main use card input from the payer. Then, the mobile WAP server may request and receive authentication information from the payer mobile terminal 560. In this case, the payer mobile terminal 560 may be implemented in the form of an authorized certificate or encrypted password. In this case, the payment approval may also be requested through the connection with the mobile payment server 530 using software such as a VM (Virtual Machine) executed in the payer mobile terminal 560. And in the same manner as described above, it is possible to implement the same payment approval effect.

When the payment is approved using the received authentication information, the mobile WAP server may notify the payer mobile terminal 560 of the approved payment result. The mobile WAP server transmits the authentication information received from the payer mobile terminal 560 to the card company server 540 to request payment approval. Thereafter, when the payment is completed by the card company server 540, the mobile WAP server transmits the payment result to the payer mobile terminal 560 and the merchant terminal 520.

On the other hand, if the payment processing rejection signal using the main use card is input to the payer mobile terminal 560 or there is no input for a predetermined time, the mobile WAP server owns the payer in the payer mobile terminal 560. The other cards 551, 552, and 553 provide information. For example, the payer inputs a payment processing rejection signal using the main use card to the payer mobile terminal 560. Then, the mobile payment server 530 or the card company server 540 linked to the mobile WAP server may query all the cards 551, 552, and 553 owned by the payer except the main use card of the payer. Can be. At this time, other cards 551, 552, and 553 except the inquired main use card may include cards issued through other card companies in addition to the payment card company.

The payer may request a payment by selecting a desired card among other cards 551, 552, and 553 provided from the mobile payment server 530 through the payer mobile terminal 560.

As described above, the mobile payment system according to the present invention has an advantage that a mobile terminal can be conveniently used for real-time payment without pre-registration or input of a card number.

In addition, even if a purchase requester who purchases goods and services and a payer who pays for the purchase are different, there is an advantage in that anytime, anywhere payment can be made using a mobile terminal.

Although specific embodiments of the present invention have been described with reference to the drawings, this is intended to be easily understood by those of ordinary skill in the art, and is not intended to limit the technical scope of the present invention. Therefore, the technical scope of the present invention is determined by the matters described in the claims, and the embodiments described with reference to the drawings may be modified or modified as much as possible within the technical spirit and scope of the present invention.

1 is a configuration diagram schematically showing a mobile payment system according to an embodiment of the present invention,

2 is a flowchart schematically showing a mobile payment method according to an embodiment of the present invention,

3 is a flowchart schematically illustrating an operation flow of a payment processing process according to an embodiment of the present invention;

4 is a view illustrating a mobile payment method when a purchase requester and a payer are the same according to an embodiment of the present invention.

5 is a diagram illustrating a mobile payment method when a purchase requester and a payer are different according to an embodiment of the present invention.

Claims (22)

In the mobile payment method of a mobile payment system including a merchant terminal, a mobile payment server, a card company server and a payer mobile terminal, Receiving, by the mobile payment server, payer identification information and transaction information from the merchant terminal: Requesting, by the mobile payment server, the card company server to query the main use card number of the payer matching the payer identification information; And And generating, by the mobile payment server, payment request information based on the main use card number inquired by the card company server and transmitting the generated payment request information to the payer mobile terminal. The method of claim 1, The payer identification information includes the name of the payer and the mobile terminal number. The method of claim 1, Receiving the payment request information, Sending, by the mobile payment server, at least one of an SMS and an MMS including a URL of a mobile WAP server; And If the payment acceptance signal is input from the payer mobile terminal receiving the SMS or MMS, the mobile WAP server comprising the step of providing the main use card number and payment details. The method of claim 3, wherein When the payment processing acceptance signal using the main use card number is input from the payer mobile terminal, the mobile WAP server performs the payment process using the main use card number, and the main use card number from the payer mobile terminal. When the payment processing reject signal using the input, the mobile WAP server further comprises the step of providing the other card information owned by the payer to the payer mobile terminal. The method of claim 1, The mobile payment server further comprises the step of selecting a payment card company to request the primary credit card number inquiry based on the purchase history of the payer stored in a separate database. The method of claim 1, The card company server is a mobile payment method, characterized in that for querying the main use card number of the payer based on the purchase history of the payer. The method according to claim 5 or 6, The purchase history is a mobile payment method, characterized in that it comprises at least one of whether the recent transaction occurs, the transaction frequency, the total transaction amount. The method of claim 1, The merchant terminal establishes a customer database including the payer identification information, and the mobile payment server receives the payer identification information extracted from the customer database of the merchant terminal. Merchant terminal for transmitting the payer identification information and transaction information to the mobile payment server; A card company server for storing the payer identification information and the main use card number of the payer matching the payer identification information; Receive payment information and transaction information from the merchant terminal, request the card company server to check the main card number of the payer, and generates payment request information on the basis of the card number used in accordance with the request Mobile payment server for transmitting to the payer mobile terminal; And A mobile payment system comprising a payment terminal for receiving the payment request information sent from the mobile payment server. The method of claim 9, The payer identification information includes the name of the payer and the mobile terminal number. The method of claim 9, When the mobile payment server transmits at least one of SMS and MMS including the URL of the mobile WAP server and a payment acceptance signal is input from the payer mobile terminal that receives the SMS or MMS, the mobile WAP server uses the main use. Mobile payment system, characterized in that to provide a card number and payment history. The method of claim 11, wherein When the payment processing acceptance signal using the main use card number is input from the payer mobile terminal, the mobile WAP server performs the payment process using the main use card number, and the main use card number from the payer mobile terminal. When the payment processing rejection signal using the input, the mobile WAP server further comprises providing other card information owned by the payer to the payer mobile terminal. The method of claim 9, The mobile payment server selects a payment card company to request the primary card number query on the basis of the purchase history of the payer stored in a separate database. The method of claim 9, The card company server is a mobile payment system, characterized in that for retrieving the main use card number of the payer based on the purchase history of the payer. The method according to claim 13 or 14, The purchase history is a mobile payment system, characterized in that it comprises at least one of whether the recent transaction occurs, the frequency of the transaction, the total transaction amount. The method of claim 9, The merchant terminal establishes a customer database including the payer identification information, and the mobile payment server receives the payer identification information extracted from the customer database of the merchant terminal. The method of claim 9, The payer mobile terminal is a mobile payment system, characterized in that for requesting payment approval through the connection to the mobile payment server running a virtual machine (VM) for payment approval. In the mobile payment method of the mobile payment system including a merchant terminal, a card company server and a payer mobile terminal, Receiving, by the card company server, biller identification information and transaction information from the merchant terminal; Querying, by the card company server, a main use card number of a payer matching the payer identification information; And And generating, by the card company server, payment request information based on the inquired main use card number and transmitting the generated payment request information to the payer mobile terminal. The method of claim 18, The payer identification information is a mobile payment method characterized in that it includes the name of the payer and the mobile terminal number. The method of claim 18, The merchant terminal establishes a customer database including the payer identification information, and extracts the payer identification information from the customer database of the merchant terminal and transmits it to the card company server. The method of claim 18, The card company server, after transmitting the payment request information, if the payment acceptance signal is received from the payer mobile terminal, further comprising the step of performing a payment process by connecting a direct session with the mobile terminal of the payer. Mobile payment method. Merchant terminal for transmitting the payer identification information and transaction information to the card company server; And Inquires the main use card number of the payer matching the payer identification information received from the merchant terminal, the card company server generates payment request information based on the inquired main use card number and transmits it to the payer mobile terminal. A card company server; And Mobile payment system comprising a payer mobile terminal for receiving the payment request information sent from the card company server.

Images