Abstract:
The present invention provides an E-wallet service method based on a waiting screen application capable of providing payment services for various types of finance company systems through a waiting screen applications installed in various types of terminals without previous registration to finance company.

Description:
BACKGROUND 
       [0001]    1. Field of the Invention 
         [0002]    The present invention relates to payment service technique, and more particularly to, an E(electronic)-wallet service method based on a waiting screen application which performs payment and payment management through a waiting screen application. 
         [0003]    2. Background of the Invention 
         [0004]    Generally, in a payment service technique, payment is performed between a seller and a buyer by a payment system or a VAN (value added network) system. As the technique is developed, a next-generation payment system called PAYMENT 2.0 is commercialized as a user-oriented personalized payment service system which provides a payment relaying service. 
         [0005]    Among the next-generation payment systems, a payment service called “INI P2P” is provided as a blog-based service. Since there is a limitation in the eligibility, the payment service has not yet widely used in the market. In addition, since a mobile safety service which is currently provided employs SMS(Short Message Service) for reinforcement of security and personalized payment approval, the mobile safety service can be provided through only a mobile communication terminal. Therefore, there is a convenience in that a user necessarily subscribe to a finance company in advance in order to register a payment means. 
         [0006]    Accordingly, in the related art, a service technique capable of integrating a plurality of payment means without a complicated procedure and managing information of payment performed by a plurality of the payment means needs to be developed. 
       SUMMARY OF THE INVENTION 
       [0007]    The present invention provides an E-wallet service method based on a waiting screen application capable of providing payment services for various types of finance company systems through a waiting screen applications installed in various types of terminals without previous registration to finance company. 
         [0008]    The present invention also provides an E-wallet service method based on a waiting screen application capable of performing payment request and managing a payment approval result through a waiting screen application. 
         [0009]    According to an aspect of the present invention, there is provided an E-wallet service method and system based on a waiting screen application including steps of: in a push module of a push system, receiving a first payment request message including customer identification information, payment object information, and payment amount information from a payment request module and pushing the first payment request message to a customer terminal which a customer is logged in by using the customer identification information; in a waiting screen application installed in the customer terminal, outputting the first payment request message, receiving payment medium information as an input or selecting one of previously-registered payment medium information items if payment according to the first payment request message is requested, generating a second payment request message including the payment medium information, the payment object information, and the payment amount information, and transmitting the second payment request message to a payment approval module of a payment approval system; in the payment approval module, generating a third payment request message having a sales check(slip) format corresponding to the payment medium information included in the second payment request message and including the payment medium information, the payment object information, and the payment amount information, transmitting the third payment request message to a payment system to request payment approval, and transmitting a payment approval result to the customer terminal if the payment approval result according to the third payment request message is supplied from the payment system; and in the waiting screen application installed in the customer terminal, receiving and outputting the payment approval result. 
         [0010]    According to the present invention, it is possible to provide payment services for various types of finance company systems through a waiting screen applications installed in various types of terminals without previous registration to finance companies, so that it is possible to greatly improve user&#39;s convenience. 
         [0011]    In addition, according to the present invention, it is possible to perform payment request and edit a payment approval result through a waiting screen application, and it is possible to manage user-customized payment information. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0012]      FIG. 1  is a diagram illustrating a configuration of an E-wallet service system based on a waiting screen application according to the present invention. 
           [0013]      FIGS. 2 and 3  are flowcharts of an E-wallet service method based on a waiting screen application according to a first embodiment of the present invention. 
           [0014]      FIG. 4  is a diagram illustrating an E-wallet service based on a waiting screen application providing screens according to the first embodiment of the present invention. 
           [0015]      FIG. 5  is a flowchart of an E-wallet service method based on a waiting screen application according to a second embodiment of the present invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0016]    A configuration of an E-wallet service system based on a waiting screen application according to the present invention will be described in detail with reference to  FIG. 1 . 
         [0017]    The E-wallet service system based on a waiting screen application includes an electronic wallet module  100 , a payment processing module  102 , a push module  108 , billing modules  116 ,  120 , and  124 , and a payment approval module  112 . The electronic wallet module  100  and the payment processing module  102  are configured based on a waiting screen application according to the present invention. 
         [0018]    The billing modules  116 ,  120 , and  124  are installed in a payment request terminal  114 , a shopping mall service server  118 , a utility billing system  122 , and the like. 
         [0019]    According to the first to third embodiments of the present invention, the billing modules  116 ,  120 ,  124  generates first payment request messages including customer identification information, payment object information, payment amount information, and the like which are input by users of the payment request terminal  114 , the shopping mall service server  118 , and the utility billing system  122  transmits the first payment request messages to the push module  108  installed in a push system  106 . In other words, the first payment request message includes customer identification information, payment object information, and payment amount information. 
         [0020]    The push module  108  is installed in the push system  106 . 
         [0021]    According to the first embodiment of the present invention, if the first payment request message is received from the billing modules  116 ,  120 , and  124  installed in the payment request terminal  114 , the shopping mall service server  118 , the utility billing system  122 , or the like, the push module  108  checks based on the customer identification information included in the first payment request message whether or not a customer logs in through a customer terminal  104 , and the push module  108  pushes the first payment request message to an electronic wallet module  100  installed in the logged-in customer terminal  104 . 
         [0022]    In addition, according to the second embodiment of the present invention, if the first payment request message is received from the billing modules  116 ,  120 , and  124  installed in the payment request terminal  114 , the shopping mall service server  118 , the utility billing system  122 , or the like, the push module  108  transmits a notice of reception of the first payment request message to the customer terminal  104  of the customer based on the customer identification information included in the first payment request message. If the customer terminal  104  accesses the push system  106  according to the notice, the push module  108  transmits the first payment request messages formed in the web account of the customer to the customer terminal. Herein, the push module  108  may use an SMS(Short Message Service) server and a push notification server for transmission of the notice. 
         [0023]    In addition, the push system  106  stores electronic wallet modules and payment processing modules as waiting screen applications having various skins. The stored electronic wallet modules and payment processing modules are downloaded to the customer terminal  104 . The electronic wallet modules may be downloaded at a charge. 
         [0024]    In addition, the push system  106  includes an electronic coupon and gift certificate information, which is generated in an image format or various electronic formats, and allows the electronic coupon and the gift certificate information to be downloaded to the customer terminal  104 . 
         [0025]    In addition, the push system  106  manages customer account information of a customer terminal such as position information, customer identification information (ID), customer terminal identification information (phone number), customer terminal specification information, login information, first payment request messages, and payment approval results, and the customer account information is provided to a customer who accesses a web through the web account. 
         [0026]    The electronic wallet module  100  and the payment processing module  102  are waiting screen applications which are downloaded from the push system  106  to be installed in the customer terminal  104 . The electronic wallet module  100  and the payment processing module  102  are installed in the customer terminal  104  such as a personal computer, a mobile communication terminal, or a mobile terminal which can be connected to the push system  106  and the payment approval system  110  via wired or wireless network. 
         [0027]    According to the first embodiment of the present invention, the electronic wallet module  100  receives and stores the first payment request message pushed by the push module  108  of the push system  106 , receives and stores a payment approval result transmitted from the payment processing module  102 , selects one of the first payment request messages according to customer&#39;s request to request the payment processing module  102  to perform payment approval, receives and stores a payment approval result returned from the payment processing module  102 , and edits the first payment request message and the payment approval result according to user&#39;s editing request. 
         [0028]    In addition, according to the second embodiment of the present invention, if the push module  108  of the push system  106  supplies the first payment request message notice information through an SMS(Short Message Service) server or an push notification server, the electronic wallet module  100  displays the first payment request message notice information on a screen, the electronic wallet module  100  accesses the web account of the user provided by the push module  108  according to user&#39;s request, receives and stores the first payment request messages transmitted from the push module  108 , selects one of the first payment request messages according to customer&#39;s request to request the payment processing module  102  to perform payment approval. The electronic wallet module  100  receives and stores a payment approval result returned from the payment processing module  102  and edits the first payment request message and the payment approval result according to user&#39;s editing request. 
         [0029]    According to the first and second embodiments of the present invention, the payment processing module  102  generates a second payment request message by adding the payment medium information to the payment request item selected according to the customer&#39;s request through the electronic wallet module  100  and provides the second payment request message to the payment approval module  112 . If the payment approval result information is supplied through the payment approval module  112 , the payment processing module  102  supplies the payment approval result information to the electronic wallet module  100 . The payment medium information is information on a credit card or a banking account or information for addition of communication fees or the like. The payment medium information may be input by a customer every payment time. In addition, a plurality of the payment medium information items may be previously registered in a storage medium, a USIM (Universal Subscriber Identity Module), or the like of the customer terminal, and after that, one of the payment medium information items may be selected by the customer. In other words, the second payment request message includes the payment medium information, the customer identification information, the payment object information, and payment amount information, 
         [0030]    The payment approval module  112  is installed in the payment approval system  110 . 
         [0031]    According to the first and second embodiments of the present invention, if the second payment request message is received, the payment approval module  112  generates a third payment request message in a sales check(slip) format corresponding to the payment medium information included in the second payment request message and transmits the generated third payment request message to the credit card company systems  126  to  128 , the bank systems  130  and  132 , or the communication company systems  134  and  136  corresponding to the payment medium to request payment approval. If information on a payment approval result is supplied from the credit card company systems  126  to  128 , the bank systems  130  and  132 , or the communication company systems  134  and  136 , the payment approval module  112  transmits the payment approval result to the payment processing module  102  installed in the customer terminal  104 . In other words, the payment approval module  112  allows different sales check(slip) formats according to the payment medium information to be compatible. 
         [0032]    In addition, in the above examples, although the case where the credit card company systems  126  to  128 , the bank systems  130  and  132 , or the communication company systems  134  and  136  is requested to perform the payment approval through the payment approval system  110  is exemplified, the payment processing module  102  may directly generate a third payment request message in a sales check(slip) format corresponding to a payment medium to request the credit card company systems  126  to  128 , the bank systems  130  and  132 , or the communication company systems  134  and  136  to perform the payment approval. 
         [0033]    In addition, according to the embodiments of the present invention, although the case where the electronic wallet service system is configured with two different hardware components, that is, the push system  106  and the payment approval system  110  is exemplified, the electronic wallet service system may be configured with one hardware component according to the convenience of a service provider. 
         [0034]    In addition, according to the first and second embodiments of the present invention, although the case where the push system  106  is configured to download the electronic wallet module  100  is exemplified, a separate management server may be configured to download the electronic wallet module  100 . 
         [0035]    Now, first and second embodiments of the operations of the waiting screen application based electronic wallet service system configured as described above will be described in detail. 
       First Embodiment 
       [0036]    The E-wallet service method based on a waiting screen application according to a first embodiment of the present invention is described with reference to flowcharts of  FIGS. 2 and 3 . 
         [0037]    One of the billing modules  116 ,  120 , and  124  installed in the payment request terminal  114  or the shopping mall service server  118 , the utility billing system  122  or the like generates a first payment request message including customer identification information, payment object information, and payment amount information for payment request and transmits the first payment request message to the push module  108  (Step S 200 ). 
         [0038]    The push module  108  extracts the customer identification information from the first payment request message and transmits the received first payment request message to the electronic wallet module  100  of the customer terminal which is logged in by the customer identification information (Step S 202 ). Herein, in the case where the customer terminal which is logged in by the customer identification information is not present, the push module  108  transmits a notice of the reception of the first payment request message through an SMS(Short Message Service) server (not shown) or a push notification server (not shown) to the customer terminal of the customer which is registered in advance. If the customer logs in according to the notice, the push module  108  transmits the received first payment request message to the electronic wallet module  100  of the customer terminal which the customer is logged in. 
         [0039]    If the first payment request message is received, the electronic wallet module  100  stores the first payment request message and outputs a notice indicating that a new first payment request message is received to a display unit (Step S 204 ). Herein, (a) of  FIG. 4  illustrates a screen informing an icon of the electronic wallet module  100  and a notice indicating that a first payment request message is received. 
         [0040]    If the output of the payment request message is requested by the customer, the electronic wallet module  100  outputs the stored first payment request messages (Steps S 206  and S 208 ). Herein, (b) of  FIG. 4  illustrates a screen informing the received first payment request messages. 
         [0041]    In the state where the items of the first payment request messages are output, if the customer selects one of the first payment request messages and the payment is requested, the electronic wallet module  100  requests the payment processing module  102  to perform a payment process for the selected item of the first payment request message (Steps S 210  and S 212 ). Herein, (c) of  FIG. 4  illustrates a screen informing detailed information when the customer selects one of the first payment request messages. 
         [0042]    If the payment request occurs, the payment processing module  102  receives the payment medium information or allows one of the payment medium information registered in advance in a USIM (Universal Subscriber Identity Module) or an internal memory to be received and generates a second payment request message including the payment object information, the payment amount information, and the payment medium information and transmits the second payment request message to the payment approval module  112  installed in the payment approval system  110  (Steps S 214  and S 216 ). Herein, (d) of  FIG. 4  illustrates a screen informing that the customer selects a payment medium for the first payment request message and requests for payment. 
         [0043]    If the second payment request message is received, the payment approval module  112  generates a third payment request message in the a sales check(slip) format based on the payment object information, the payment amount information, and the payment medium information according to the payment medium information and transmits the third payment request message to a payment system such as credit card company systems  126  to  128 , bank systems  130  and  132 , or communication company systems  134  and  136  according to the payment medium information (Step S 218 ). 
         [0044]    The payment system such as the credit card company systems  126  to  128 , the bank systems  130  and  132 , or the communication company systems  134  and  136  performs payment approval according to the third payment request message and transmits a payment approval result as a reply to the payment approval module  112  (Step S 220 ). 
         [0045]    The payment approval module  112  transmits the payment approval result to the payment processing module  102 , and the payment processing module  102  transmits the payment approval result to the electronic wallet module  100  (Step S 222  and S 224 ). 
         [0046]    The electronic wallet module  100  stores the payment approval result and outputs the payment approval result to inform the customer (Step S 226 ). 
         [0047]    In addition, the electronic wallet module  100  receives and stores the payment medium information according to a request for payment medium information registration issued by the customer (Steps S 300  and S 302 ). A plurality of the payment medium information registered are stored in the electronic wallet module  100 , so that any one of the payment medium can be selected by the customer. 
         [0048]    In addition, the electronic wallet module  100  outputs the stored results of the payment approval according to a request for editing the payment approval result. The electronic wallet module  100  receives editing information such as removing and changing of the payment approval results and performs the editing such as removing or changing of the payment approval results. The electronic wallet module  100  stores the result of the editing (Steps S 304  to S 308 ). 
         [0049]    In addition, the electronic wallet module  100  outputs the first payment request message stored according to a request for the editing of the payment request message. The electronic wallet module  100  receives editing information such as removing or changing of the first payment request messages and performs editing such as removing or changing of the first payment request message. The electronic wallet module  100  stores the result of the editing (Steps S 310  to S 314 ). 
       Second Embodiment 
       [0050]    A waiting screen application based electronic wallet service method according to a second embodiment of the present invention is described with reference to a flowchart of  FIG. 5 . 
         [0051]    One of billing modules  116 ,  120 , and  124  installed in a payment request terminal  114 , a shopping mall service server  118 , a utility billing system  122 , or the like generates a first payment request message including customer identification information, payment object information, and payment amount information for payment request and transmits the first payment request message to a push module  108  (Step S 400 ). 
         [0052]    The push module  108  extracts customer identification information from the first payment request message and transmits a notice of reception of the first payment request message to the customer terminal registered so as to correspond to the customer identification information (Step S 402 ). The transmission of the notice is performed through an SMS(Short Message Service) server (not shown) or a push notification server (not shown). 
         [0053]    The electronic wallet module  100  which receives the notice of reception of the first payment request message displays the notice on the screen so that a customer receives a notice of the reception of the first payment request message (Step S 404 ). As illustrated in (a) of  FIG. 4 , the notice of the reception may be implemented by displaying the number of the received messages in the vicinity of the electronic wallet driving icon. 
         [0054]    If the customer who receives the notice of the reception of the first payment request message requests accessing the push module  108 , the electronic wallet module  100  accesses a web account of the customer included in the push module  108  to request a list of the first payment request messages of the customer and receives the list of the first payment request messages (Steps S 406  and S 408 ). Herein, the access to the push module  108  may be performed by user double-clicking the electronic wallet driving icon. 
         [0055]    Next, the electronic wallet module  100  receives the first payment request messages, and if the customer selects one of the first payment request messages to perform request for payment under the state where the first payment request message items are output, the electronic wallet module  100  requires the payment processing module  102  to perform the payment process with respect to the selected first payment request message item (Steps S 410  and S 412 ). 
         [0056]    If the payment request occurs, the payment processing module  102  receives the payment medium information as an input or selects one of the payment medium information which is registered in advance in the USIM (Universal Subscriber Identity Module) or the internal memory, generates the second payment request message including the payment object information, the payment amount information, and the payment medium information, and transmits the second payment request message to the payment approval module  112  (Steps S 414  and S 416 ). 
         [0057]    If the second payment request message is received, the payment approval module  112  generates a third payment request message in the sales check(slip) format according to the payment medium information based on the payment object information, the payment amount information, and the payment medium information and transmits the third payment request message the payment system such as the credit card company systems  126  to  128 , the bank systems  130  and  132 , or the communication company systems  134  and  136  according to the payment medium information (Step S 418 ). 
         [0058]    The payment system such as the credit card company systems  126  to  128 , the bank systems  130  and  132 , or the communication company systems  134  and  136  performs the payment approval according to the third payment request message and returns the result thereof to the payment approval module  112  (Step S 420 ). 
         [0059]    The payment approval module  112  transmits the payment approval result to the payment processing module  102 , and the payment processing module  102  transmits the result of the payment approval to the electronic wallet module  100  (Steps S 422  and S 424 ). 
         [0060]    The electronic wallet module  100  outputs the payment approval result to present the result to the customer (Step S 426 ).