WO2010132505A2 - Purchase unit managing system - Google Patents

Abstract

The present invention discloses a purchase unit managing system for activation and loading of a prepaid card which enables purchasing of a purchase unit and transfer of the whole or some purchase unit via a network. The purchase unit managing system of the present invention includes: a purchaser terminal that communicates with a management server via a network, and transmits a purchase intention for a purchasable prepaid card and receiver information to the management server; the management server that transmits information of the purchasable prepaid cards to the purchaser terminal, receives the purchase intention, generates and stores a purchasing result including the settled purchase intention and at least some of the receiver information after a purchaser performs a settlement process of the purchase intention, and transmits a granting message.

Description

[DESCRIPTION]

[Invention Title]

PURCHASE UNIT MANAGING SYSTEM

[Related Applications]

This application claims the benefit of U.S. Provisional Patent Application No. 61/177,528, filed May 12, 2009, the contents of which are incorporated herein by reference in their entirety.

[Technical Field]

The present invention relates to a purchase unit managing system for activation and loading of a prepaid card, and more particularly to, a purchase unit managing system for activation and loading of a prepaid card which enables purchasing of a purchase unit and transfer of the whole or some purchase unit via a network.

[Background Art]

Many people admit that a current payment card can occupy a certain position in a payment technology market. Presently, a prepaid card solution has acquired a large share in the payment technology market, and distribution of various payment cards has been expanded.

To use a prepaid card, a customer pays a certain amount of money in advance and gets a card recorded with that amount of money, or deposits a certain amount of money and gets a card indicating the deposit like a debit card, so that the customer can freely purchase goods or services at any time within a card balance range or deposit. Exemplary prepaid cards include a gift card, Visa or Mastercard debit card, telephone card, transit system farecard, etc.

When purchasing the prepaid card, a purchaser selects a desirable prepaid card, and settles an activated and loaded or reloaded prepaid card by cash or card in a sole agency.

Particularly, when intending to present or transfer the purchased prepaid card to another person, the purchaser should meet the person to give the prepaid card, or should send the prepaid card to the person via a delivery service. That is, in order to give the prepaid card to another person, the purchaser should always physically give or send the prepaid card to the person.

[Disclosure]

[Technical Problem]

Therefore, an object of the present invention is to provide a purchase unit managing system and managing method which transmit a message via a network, and allow a receiver or purchaser to pick up a prepaid card in a place convenient to purchase goods or services, instead of physically giving the prepaid card.

Another object of the present invention is to provide a purchase unit managing system and managing method which allow a receiver or purchaser to select and pick up a prepaid card or cards to be activated and loaded in a desirable time and place.

A further object of the present invention is to provide a purchase unit managing system and managing method which can prevent loss and damage of a prepaid card until a receiver or purchaser picks up the prepaid card.

A still further object of the present invention is to provide a purchase unit managing system and managing method which enable selection of a kind of a prepaid card, selection of a purchase unit, and easy settlement on a network.

A still further object of the present invention is to provide a purchase unit managing system and managing method which enable selection and settlement of a purchase unit activated and loaded on a prepaid card, without designating the prepaid card on a network.

A still further object of the present invention is to provide a purchase unit managing system and managing method which cause a receiver to visit a provider to select and pick up a prepaid card, so that the provider can attract more customers.

A still further object of the present invention is to provide a purchase unit managing system and managing method which can improve reliability of transfer of a high purchase unit through confirmation and authentication of a receiver.

A still further object of the present invention is to provide a purchase unit managing system and managing method which allow purchasers or receivers owning purchase units of different kinds of prepaid cards to exchange or change the purchase units into purchase units corresponding to desirable kind of prepaid cards on a network by grouping of a management server.

A still further object of the present invention is to provide a purchase unit managing system and managing method which do not affect a redemption process of a prepaid card available by conventional activation and loading.

A still further object of the present invention is to provide a purchase unit managing system and managing method which allow a receiver granted a purchase unit by a purchaser to easily grant the purchase unit to another receiver.

A still further object of the present invention is to provide a purchase unit managing system and managing method which allow a purchaser or receiver to select, activate and load (or reload) one or more prepaid cards, since the purchaser sets a total purchase amount which is an overall size of a purchase unit.

A still further object of the present invention is to provide a purchase unit managing system and managing method which allow a purchaser or receiver to pick up a prepaid card after selecting a kind of a prepaid card and an activated and loaded money amount.

[Technical Solution]

According to an aspect of the present invention, there is provided a purchase unit managing system, comprising: a purchaser terminal including a communication unit that communicates with a management server via a network, a display unit that displays information of purchasable prepaid cards received through the communication unit, an input unit that receives, from a purchaser, input of a purchase intention for one or more of the displayed purchasable prepaid cards, and receiver information including communication access information for communication access to a receiver, and a processor that controls the communication unit, the display unit and the input unit to transmit the purchase intention for the purchasable prepaid card and the receiver information to the management server; the management server including a communication unit that communicates with the purchaser terminal, a receiver terminal and a provider terminal via the network, a storage unit that stores the information of the purchasable prepaid cards, and the purchase intention and the receiver information received from the purchaser terminal, and a processor that controls the communication unit and the storage unit to transmit the information of the purchasable prepaid cards to the purchaser terminal, receive the purchase intention, generate and store a purchasing result including the settled purchase intention and at least some of the receiver information after the purchaser performs a settlement process of the purchase intention, transmit a granting message notifying that loading of the prepaid card is possible or a loadable kind and a loadable money amount to the receiver terminal according to the receiver information, search for a purchasing result corresponding to receiver confirmation information received from the provider terminal, and transmit purchasing result confirmation for the searched purchasing result to the provider terminal, or perform a settlement process of the searched purchasing result for a provider; the receiver terminal including a communication unit that communicates with the management server, and a display unit that receives the granting message from the management server and displays the granting message; and the provider terminal including a communication unit that communicates with the management server, an input unit that receives input of the receiver confirmation information including at least communication access information of the receiver, a display unit that displays an input screen received from the management server for the use in inputting the receiver confirmation information, and a processor that controls the communication unit, the input unit and the display unit to access the management server through the communication unit, display the input screen, receive input of the receiver confirmation information, transmit the receiver confirmation information to the management server, and activate and load the prepaid card or display that activation and loading of the prepaid card are possible on the display unit according to reception of the purchasing result confirmation from the management server or a result of the settlement performed by the management server.

Also, when the information of the purchasable prepaid cards includes plural kinds of prepaid cards, the purchaser terminal acquires a purchase intention including one or more kinds of prepaid cards selected by the purchaser, and a purchase unit for each kind of prepaid card or a purchase number of each kind of prepaid card, and transmits the purchase intention to the management server.

In addition, the receiver terminal can access the management server and select changing of the selected prepaid card into another kind of prepaid card, and the management server updates the purchasing result, reflecting the kind of the prepaid card selected for change.

Moreover, a money amount loaded by the provider terminal or displayed as being loadable is equal to or smaller than a money amount settled by the purchaser.

Further, a loaded money amount of the prepaid card is some or the whole of a loadable money amount.

Furthermore, the provider terminal includes a terminal that activates and loads the prepaid card selected by the purchaser or selected by the receiver for change.

Still furthermore, the purchase unit managing system includes a terminal that is electrically disconnected from the provider terminal to activate and load the prepaid card selected by the purchaser or selected by the receiver for change.

Still furthermore, the provider terminal acquires the communication access information of the receiver terminal from the receiver and transmits the communication access information to the management server, the receiver terminal transmits an approval message to the management server, and the management server compares the communication access information received from the provider terminal with the communication access information of the receiver terminal corresponding to the approval message, and authenticates the receiver terminal if the communication access information is the same.

According to another aspect of the present invention, there is provided a purchase unit managing system, comprising: a purchaser terminal including a communication unit that communicates with a management server via a network, an input unit that receives, from a purchaser, input of a purchase intention including a purchase unit of a prepaid card, and receiver information including communication access information for communication access to a receiver, and a processor that controls the communication unit and the input unit to transmit the purchase intention and the receiver information to the management server; the management server including a communication unit that communicates with the purchaser terminal, a receiver terminal and a provider terminal via the network, a storage unit that stores the purchase intention and the receiver information received from the purchaser terminal, and a processor that controls the communication unit and the storage unit to transmit information of a purchasable purchase unit to the purchaser terminal, receive the purchase intention, generate and store a purchasing result including the settled purchase intention and at least some of the receiver information after the purchaser performs a settlement process of the purchase intention, transmit a granting message notifying that loading of the prepaid card is possible or a loadable kind and a loadable money amount to the receiver terminal according to the receiver information, search for a purchasing result corresponding to receiver confirmation information received from the provider terminal, and transmit purchasing result confirmation for the searched purchasing result to the provider terminal, or perform a settlement process of the searched purchasing result for a provider; the receiver terminal including a communication unit that communicates with the management server, and a display unit that receives the granting message from the management server and displays the granting message; and the provider terminal including a communication unit that communicates with the management server, an input unit that receives input of the receiver confirmation information including at least communication access information of the receiver, a display unit that displays an input screen received from the management server for the use in inputting the receiver confirmation information, and a processor that controls the communication unit, the input unit and the display unit to access the management server through the communication unit, display the input screen, receive input of the receiver confirmation information, transmit the receiver confirmation information to the management server, and activate and load one or more prepaid cards selected by the receiver or display that activation and loading are possible on the display unit according to reception of the purchasing result confirmation from the management server or a result of the settlement performed by the management server. According to a further aspect of the present invention, there is provided a purchase unit exchanging method, comprising: receiving, at a management server, a change request for changing a current kind of a prepaid card included in a purchasing result corresponding to each user into a target kind from two or more first to Nth user terminals; storing, at the management server, the change requests including the current kinds and the target kinds of the respective first to Nth users; confirming the current kinds and the target kinds in the change requests, and setting a change user group who can change the kinds of the prepaid cards with each other; and changing the current kinds of the respective users into the target kinds in the change user group, and updating purchasing results corresponding to the users in the change user group. According to a still further aspect of the present invention, there is provided a purchase unit managing method of a purchase unit managing system including a management server that can communicate with at least a first receiver terminal and stores purchasing results of one or more receivers, the method comprising: accessing, at the management server, the first receiver terminal; searching, at the management server, for a prestored first purchasing result corresponding to first receiver confirmation information from the first receiver terminal; if the first purchasing result exists, receiving, at the management server, granting information of at least some of prepaid cards included in the searched first purchasing result and second receiver information from the first receiver terminal; generating a second purchasing result corresponding to the granting information and the second receiver information according to the received second receiver information, and updating the first purchasing result.

[Advantageous Effects]

An embodiment of the present invention transmits a message via a network, and allows a receiver or purchaser to pick up a prepaid card in a place convenient to purchase goods or services, without physically moving the prepaid card, so that it is easy to pay for and grant the prepaid card.

Another embodiment of the present invention allows a receiver or purchaser to select and pick up an activated and loaded prepaid card in a desirable time and place, which improves convenience of the receiver or purchaser.

A further embodiment of the present invention can prevent loss and damage of a prepaid card until a receiver or purchaser picks up the prepaid card.

A still further embodiment of the present invention enables selection of a kind of a prepaid card, selection of a purchase unit, and easy settlement on a network.

A still further embodiment of the present invention enables selection and settlement of a purchase unit activated and loaded on a prepaid card, without designating the prepaid card on a network, so that a purchaser or receiver can pick up an intended prepaid card afterward.

A still further embodiment of the present invention causes a receiver to visit a provider to select and pick up a prepaid card, so that a provider can attract more customers. It is thus possible to provide an economical advantage in addition to activation and loading of the prepaid card.

A still further embodiment of the present invention can improve reliability of transfer of a high purchase unit through confirmation and authentication of a receiver.

A still further embodiment of the present invention allows a purchaser or receiver to select, activate and load (or reload) one or more prepaid cards, since the purchaser sets the total purchase amount which is an overall size of a purchase unit.

A still further embodiment of the present invention allows purchasers or receivers owning purchase units of different kinds of prepaid cards to exchange or change the purchase units into purchase units corresponding to desirable prepaid cards on a network by grouping of a management server.

A still further embodiment of the present invention does not affect a redemption process of a prepaid card available by conventional activation and loading, and thus can be implemented maintaining a conventional system. A still further embodiment of the present invention allows a receiver granted a purchase unit from a purchaser to easily grant the purchase unit to another receiver.

A still further embodiment of the present invention allows a purchaser or receiver to pick up a prepaid card after selecting a kind of a prepaid card and an activated and loaded money amount.

[Description of Drawings]

The above and other objects, features and advantages of the present invention will become apparent from the following description of a preferred embodiment given in conjunction with the accompanying drawings, in which:

FIG. 1 is a schematic configuration diagram illustrating a purchase unit managing system according to the present invention;

FIG. 2 is a schematic configuration diagram illustrating a purchaser terminal of FIG. 1 ;

FIG. 3 is a schematic configuration diagram illustrating a management server of FIG. 1 ;

FIG. 4 is a schematic configuration diagram illustrating a receiver terminal of FIG. 1 ;

FIG. 5 is a schematic configuration diagram illustrating a first embodiment of the provider terminal of FIG. 1 ;

FIG. 6 is a schematic configuration diagram illustrating a second embodiment of the provider terminal of FIG. 1 ;

FIG. 7 is a flowchart showing a purchase unit purchasing process by the purchaser terminal;

FIG. 8 is a flowchart showing a purchase unit granting process by a purchaser;

FIG. 9 is a flowchart showing a purchase unit granting process at the management server;

FIG. 10 is a flowchart showing a granting process from one receiver to another receiver;

FIG. 1 1 is a diagram illustrating an embodiment of information of purchasable prepaid cards provided by the management server;

FIG. 12 is a diagram illustrating an embodiment of a screen to which the purchaser or receiver can input receiver information in the purchase unit granting process;

FIG. 13 is a flowchart showing a prepaid card activating and loading process by a provider;

FIG. 14 is a flowchart showing a first embodiment for authenticating the purchaser or receiver, which is performed in the activating and loading process of FIG. 13;

FIG. 15 is a flowchart showing a second embodiment for authenticating the purchaser or receiver, which is performed in the activating and loading process of FIG. 13;

FIG. 16 is a flowchart showing a third embodiment for authenticating the purchaser or receiver, which is performed in the activating and loading process of FIG. 13;

FIG. 17 is a table showing an embodiment of a change request table stored by the management server;

FIG. 18 is a flowchart showing a process of the management server to change or exchange kinds of prepaid cards corresponding to purchase units;

FIG. 19 is a diagram illustrating an example of a grouping step in FIGS. 17 and 18;

FIG. 20 is a flowchart showing another purchase unit purchasing process by the purchaser terminal;

FIG. 21 is a flowchart showing another purchase unit granting process by the purchaser;

FIG. 22 is a flowchart showing another purchase unit granting process at the management server;

FIG. 23 is a flowchart showing another granting process from one receiver to another receiver;

FIG. 24 is a diagram illustrating another embodiment of the information of the purchasable prepaid cards provided by the management server;

FIG. 25 is a diagram illustrating another embodiment of the screen to which the purchaser or receiver can input receiver information in the purchase unit granting process; and FIG. 26 is a flowchart showing another prepaid card activating and loading process by the provider. [Mode for Invention]

Hereinafter, the present invention will be described in detail in connection with embodiments and drawings.

FIG. 1 is a schematic configuration diagram illustrating a purchase unit managing system according to the present invention. The purchase unit managing system of FIG. 1 includes a purchaser terminal 10 that is used by a purchaser purchasing or granting a purchase unit, a management server 20 that manages a purchase unit purchased by the purchaser, a purchase unit granted to a receiver by the purchaser, a purchase unit granted to another receiver by the receiver, information of purchasable prepaid cards that can be selected by the purchaser or receiver, purchaser information, receiver information, etc., a network 30 that enables a plurality of devices to communicate with each other via Web or WAP communication, a payment system 40 that provides various payment methods, an authentication system 50 that can authenticate the purchaser and the receiver or the purchaser information and the receiver information, a receiver terminal 60 that is used by the receiver granted the purchase unit by the purchaser or another receiver, a provider terminal 70 that activates and loads a prepaid card corresponding to the purchase unit owned by the purchaser or granted to the receiver, or displays the purchase unit, a prepaid card administration server 80 that manages using of the prepaid card when it is activated, loaded and used in various stores, and an activation device 90 that activates and loads the prepaid card. The purchase unit managing system of the present invention may be basically implemented to be independent from the prepaid card administration server 80, and the management server 20 may perform the function of the prepaid card administration server 80. In addition, the management server 20 does not basically perform the function of the authentication system 50 or the payment system 40, but may perform the function of the authentication system 50 or the payment system 40, as needed.

The purchaser terminal 10 is a device which can perform communication via the network 30, input and display necessary information, and process the purchaser's selection of the purchasable prepaid card provided in the management server 20, selection of the purchase unit, settlement and authentication, e.g. a personal computer, cellular phone, PDA. etc. It will be described below in detail with reference to FIG. 2. The management server 20 is a system which causes the purchaser to access data including information of the purchasable prepaid cards via a login procedure and select a kind of the prepaid card and the purchase unit, when the purchaser terminal 10 accesses via the network 30, causes the receiver to receive an additionally purchased purchase unit, authenticates the purchaser and the receiver, causes the purchaser to settle the payment to purchase the purchase unit, transmits a granting message to the receiver, and accesses the provider terminal 70 to authenticate activation and loading of the prepaid card selected by the purchaser or receiver and perform a payment settlement process for a provider. The management server 20 will be described below in detail with reference to FIG. 3.

The network 30 performs Web or WAP communication or other communication to enable the purchaser terminal 10 and the management server 20 to communicate with each other, may include a device or system that enables the management server 20 to transmit a necessary message (text, voice, image message, etc.), and performs Web or WAP communication or other communication to enable the provider terminal 70 and the management server 20 to communicate with each other. In addition, the network 30 provides a communication line so that the purchaser can access the payment system 40 and settle the payment of the purchase unit and that the management server 20 can perform the payment settlement for the provider. Moreover, the network 30 provides a communication line so that the purchaser and the receiver can be authenticated via communication between the authentication system 50 and the management server 20. Further, the network 30 may provide a communication line between the activation device 90 and the provider terminal 70 or the prepaid card administration server 80.

The payment system 40, which is a system for enabling a variety of payment settlements, may include a credit card system, a bank fund transfer system, etc.

The authentication system 50, which is to verify validity of the purchaser or receiver according to the purchaser information or receiver information, can verify whether the purchaser or receiver is a valid purchaser or receiver through e.g. an input name, cellular phone number, social security number, driver's license number, etc., or whether the cellular phone number is rightfully granted. The authentication system 50 may include a wire/wireless communication provider system, a government authentication system and a credit information system which store high reliable purchaser or receiver information. Alternatively, for example, the authentication system 50 can authenticate whether an owner of a cellular phone number is the purchaser or receiver.

Also, the authentication system 50 generates an authentication code, and transmits the authentication code to the management server 20 or the receiver terminal 60 to authenticate the receiver.

The receiver terminal 60 is a device which can perform communication via the network 30 and input and display necessary information, e.g. a personal computer, cellular phone and PDA. In addition, the receiver terminal 60 may receive a granting message from the management server 20 via the network 30, and access the management server 20 via the network 30 to change a kind of a prepaid card corresponding to a granted purchase unit or grant the purchase unit to another receiver. The receiver terminal 60 will be described below in detail with reference to FIG. 4.

The provider terminal 70 is a device which directly activates and loads the prepaid card selected by the purchaser or receiver, or performs display for activation and loading of the prepaid card. The provider terminal 70 is installed in a general store where the prepaid card can be activated and loaded or adjacent to the store. For example, the provider terminal 70 may include a computer, or a POS system or kiosk system installed in a customer service of various stores. The provider terminal 70 is a device which accesses the management server 20 via the network 30 so that the purchaser or receiver can confirm the owned or granted purchase unit and conduct loading corresponding to the purchase unit. The provider terminal 70 will be described below in detail with reference to FIGS. 5 and 6.

The prepaid card administration server 80 is a system which stores a serial number of an activated prepaid card or a kind of a prepaid card, and account information corresponding to a loaded money amount, and subtracts a paid money amount from the account information to perform the payment settlement when the purchaser or receiver pays for goods or services by the activated and loaded prepaid card. A conventional system can be used as the prepaid card administration server 80 as it is.

The activation device 90 reads information such as the serial number of the prepaid card selected by the purchaser or receiver and activates the prepaid card, such that an account equivalent to the loaded money amount is generated and stored in the prepaid card administration server 80, corresponding to the activated prepaid card or the serial number of the prepaid card. In a case where the provider terminal 70 is not provided with the activating and loading function of the prepaid card, the activation device 90 is e.g. a POS system or kiosk system manipulated by an operator to activate and load the prepaid card according to the purchase unit displayed by the provider terminal 70 or the money amount corresponding to the purchase unit. The activation device 90 may correspond to a conventional device that performs activation, loading and redemption of a prepaid card. The activation device 90 is electrically disconnected from the provider terminal 70, and manipulated by the operator or provider to be independent from the manipulation of the provider terminal 70.

The functions of the payment system 40, the authentication system 50, the prepaid card administration server 80 and the activation device 90 are identical to those performed in the conventional systems or devices, and thus detailed explanations thereof are omitted.

FIG. 2 is a schematic configuration diagram illustrating the purchaser terminal of FIG. 1. As illustrated in FIG. 2, the purchaser terminal 10 includes a communication unit 1 1 that can access the management server 20 via the network 30, an input unit 13 that receives input of information from a user or purchaser, a display unit 15 that displays information transmitted from the management server 20 and information input from the input unit 13, a storage unit 17 that stores various necessary information, and a processor 19 that controls the communication unit 1 1 , the input unit 13, the display unit 15 and the storage unit 17 to enable the purchaser to select a kind of a purchasable prepaid card transmitted from the management server 20, input and purchase a purchase unit, and settle the payment of the purchase unit. The purchaser terminal 10 includes a power supply unit (not shown) for applying power to the respective components. As the construction of the power supply unit is obvious to those skilled in the art, description thereof is omitted.

The communication unit 1 1 may be implemented into a wire communication module, a wireless communication module, a power line communication module, etc. which enable communication using the network 30. The input unit 13 may be implemented into an input device, e.g. a touch pad, a touch screen, a keyboard, etc.

The display unit 15 may be implemented into various display devices such as an LCD display, an LED display, etc. Moreover, the display unit 15 should be recognized as performing audible display (e.g. speaker, etc.) as well as visible display.

The storage unit 17 stores information input from the input unit 13 and information received from the management server 20 through the communication unit 1 1.

The processor 19 performs the aforementioned function, and examples for carrying out this function will be described below in detail.

FIG. 3 is a schematic configuration diagram illustrating the management server of FIG. 1. As illustrated in FIG. 3, the management server 20 includes a communication unit 21 that communicates with the purchaser terminal 10, the receiver terminal 60, the provider terminal 70 and the authentication system 50 via the network 30, an input unit 23 that receives input of information from a manager, a display unit 25 that displays information transmitted from other devices and information input from the input unit 23, a storage unit 27 that stores various necessary information, and a processor 29 that controls the storage unit 27, the communication unit 21 , the input unit 23, the display unit 25 and the storage unit 27 to enable the purchaser to select a kind of a purchasable prepaid card, input and purchase a purchase unit and settle the payment of the purchase unit, transmit a granting message to the receiver when the purchaser grants the purchased purchase unit, enable the receiver to change the kind of the prepaid card corresponding to the purchase unit, enable the receiver to grant the prepaid card to another receiver, and perform grouping according to exchange requests on kinds of prepaid cards from a plurality of purchasers or receivers. The management server 20 includes a power supply unit (not shown) for applying power to the respective components. As the construction of the power supply unit is obvious to those skilled in the art, description thereof is omitted.

The communication unit 21 may be implemented into a wire communication module, a wireless communication module, a power line communication module, etc. which enable communication using the network 30.

The input unit 23 may be implemented into an input device, e.g. a touch pad, a touch screen, a keyboard, etc.

The display unit 25 may be implemented into various display devices such as an LCD display, an LED display, etc. Moreover, the display unit 25 should be recognized as performing audible display (e.g. speaker, etc.) as well as visible display.

The storage unit 27 stores information input from the input unit 23 and information received from the management server 20 through the communication unit 21.

The processor 29 performs the aforementioned function, and examples for carrying out this function will be described below in detail.

Data stored in the storage unit 27 and managed by the processor 29 may include purchaser information acquired from the purchaser terminal 10, receiver information, information of purchasable, i.e. salable prepaid cards input by the manager or from an external server, provider information, authentication information, purchasing result, settlement information, etc.

The purchaser information includes identification information (e.g. a name, social security number, alias, driver's license number, etc.) and communication access information (a telephone number, E-mail address, fax number, etc.) of the purchaser. The purchaser information may further include a residence address, major locality address, age, gender, date of birth, memorial day, etc. of the purchaser.

The receiver information includes identification information (e.g. a name, social security number, alias, driver's license number, etc.) and communication access information (a telephone number, E-mail address, fax number, etc.) of the receiver. The receiver information may further include a residence address, major locality address, age, gender, date of birth, memorial day, etc. of the receiver.

The information of the purchasable prepaid cards includes a kind of a prepaid card, a purchase unit, and an image or text for the use in selecting the kind of the prepaid card. For convenience, the prepaid cards may be divided into first prepaid cards available according to merchant brands (e.g. Starbucks prepaid card, Baskinrobbins prepaid card, online game prepaid card, TGI prepaid card, etc.), second prepaid cards available in provider or retailer brand stores (e.g. Best buy prepaid card, Sears prepaid card, convenience store prepaid card, etc.), and third prepaid cards available in all stores or merchants accepting the prepaid card without restrictions of the merchant brands or brand stores (e.g. a prepaid card of a credit card company or bank such as a credit card). However, for example, if the merchant brands of the prepaid cards belonging to the first prepaid cards are different, they should be recognized as different kinds of prepaid cards, and the prepaid card belonging to the first prepaid cards and the prepaid card belonging to the second prepaid cards should be recognized as different kinds of prepaid cards.

In addition, the purchase unit can be selected by the purchaser, and is equivalent to a money amount loaded on an account of a prepaid card at the time of activation and loading of the prepaid card. For example, the purchase unit may be equivalent to $20 or 20,000 points. The purchase unit may be equal to or larger than the money amount loaded on the account. That is, it is because the purchaser may have to pay a service fee to an administrator or administration company of the management server 20. On the same reason, a money amount settled by the purchaser should be equal to or larger than the purchase unit.

The purchasing result includes a kind of a prepaid card (one or more kinds), a purchase unit (or a purchase unit value) of each purchased or granted prepaid card, and a total value of the purchase unit in the case of the third prepaid card. Moreover, in a case where the prepaid card is granted or presented to the receiver, the purchasing result may include information on a time or period to transmit a granting message. The purchaser or receiver may input the granting message, or the management server 20 may store appropriate contents, e.g. 'Prepaid card of $30 is presented to John. Happy Birthday! Get the prepaid card in the nearest Best Buy.'. The purchasing result becomes a purchasing result of the purchaser when the purchaser purchases the prepaid card, a purchasing result of the receiver when the purchaser grants the prepaid card to the receiver, and a purchasing result of another receiver when the receiver grants the prepaid card to another receiver.

However, the purchasing result may essentially include first purchaser information, and may include receiver information when the purchaser grants the prepaid card to the receiver afterward. Therefore, the management server 20 can continuously store the purchasing result, and provide the purchasing result to the purchaser or receiver so that the purchaser or receiver can confirm whether the final receiver activates and loads the prepaid card corresponding to the purchase unit. The provider information includes communication information for communication access (e.g. security access) to the provider terminal 70, and settlement method information for the settlement for the provider.

The authentication information includes validity examination data regarding validity of the identification information and the communication access information included in the purchaser information or receiver information, and receiver authentication data based on receiver confirmation information (e.g. the communication access information or identification information of the receiver, etc.) received from the provider terminal 70.

The settlement information includes settlement data for the purchase unit purchased by the purchaser, and settlement data for the provider. In addition, the settlement information may include fee information when the purchaser purchases the purchase unit, and fee information when the receiver re-grants the granted purchase unit.

Moreover, the storage unit 27 includes a user interface screen transmitted to the respective devices when the management server 20 communicates with the purchaser terminal 10, the receiver terminal 60 and the provider terminal 70. The user interface screen includes an input screen for the use in inputting information.

FIG. 4 is a schematic configuration diagram illustrating the receiver terminal of FIG. 1. As illustrated in FIG. 4, the receiver terminal 60 includes a communication unit 61 that can receive a message from the management server 20 and perform communication access via the network 30, an input unit 63 that receives input of information from the receiver, a display unit 65 that displays information transmitted from the management server 20 and information input from the input unit 63, a storage unit 67 that stores various necessary information, and a processor 69 that controls the communication unit 61 , the input unit 63, the display unit 65 and the storage unit 67 to display a purchase unit granting message to the receiver, or enable the receiver to select a kind of a purchasable prepaid card transmitted from the management server 20 or re-grant the granted purchase unit. The receiver terminal 60 includes a power supply unit (not shown) for applying power to the respective components. As the construction of the power supply unit is obvious to those skilled in the art, description thereof is omitted. The communication unit 61 may be implemented into a wire communication module, a wireless communication module, a power line communication module, etc. which enable communication using the network 30.

The input unit 63 may be implemented into an input device, e.g. a touch pad, a touch screen, a keyboard, etc.

The display unit 65 may be implemented into various display devices such as an LCD display, an LED display, etc. Moreover, the display unit 65 should be recognized as performing audible display (e.g. speaker, etc.) as well as visible display.

The storage unit 67 stores the information input from the input unit 63 and the information received from the management server 20 through the communication unit 61.

The processor 69 performs the aforementioned function, and examples for carrying out this function will be described below in detail.

FIG. 5 is a schematic configuration diagram illustrating a first embodiment of the provider terminal of FIG. 1. As illustrated in FIG. 5, the provider terminal 70 includes a communication unit 71 that can receive a message from the management server 20 and perform communication access via the network 30, an input unit 73 that receives input of information from the provider, a display unit 75 that displays information transmitted from the management server 20 and information input from the input unit 73, a storage unit 77 that stores various necessary information, and a processor 79 that controls the communication unit 71 , the input unit 73, the display unit 75 and the storage unit 77 to receive input of receiver confirmation information (or purchaser confirmation information), transmit the same to the management server 20, receive and display confirmation of the receiver (or purchaser) and a purchasing result corresponding to the receiver (or purchaser), and display that activation and loading of the prepaid card are possible according to the purchasing result. The provider terminal 70 includes a power supply unit (not shown) for applying power to the respective components. As the construction of the power supply unit is obvious to those skilled in the art, description thereof is omitted.

The communication unit 71 may be implemented into a wire communication module, a wireless communication module, a power line communication module, etc. which enable communication using the network 30. The input unit 73 may be implemented into an input device, e.g. a touch pad, a touch screen, a keyboard, etc. The receiver confirmation information is to confirm the receiver who confirms whether the prepaid card can be activated and loaded through the provider terminal 70. Similarly, the purchaser confirmation information is to conform the purchaser, when the purchaser does not grant the purchase unit to the receiver but directly activates, loads and uses the prepaid card.

The display unit 75 may be implemented into various display devices such as an LCD display, an LED display, etc. Moreover, the display unit 75 should be recognized as performing audible display (e.g. speaker, etc.) as well as visible display.

The storage unit 77 stores information input from the input unit 73 and information received from the management server 20 through the communication unit 71.

The processor 79 performs the aforementioned function, and examples for carrying out this function will be described below in detail.

Since the provider terminal 70 of FIG. 5 does not have a function for activating and loading (or reloading) the prepaid card, this configuration requires the activation device 90.

FIG. 6 is a schematic configuration diagram illustrating a second embodiment of the provider terminal of FIG. 1. The provider terminal 70a of FIG. 6 is similar to the provider terminal 70 of FIG. 5 except an activation unit 78.

The activation unit 78 can perform the activating and loading function of the activation device 90 under the control of the processor 79. That is, the processor 79 enables the activation unit 78 to activate and load the prepaid card selected by the receiver (or purchaser) confirmed by the management server 20.

FIG. 7 is a flowchart showing a purchase unit purchasing process by the purchaser terminal.

At step S1 1 , the purchaser terminal 10 accesses the management server 20 via the network 30. For example, the purchaser terminal 10 accesses a web page of TCP/IP communication standard interworking with the management server 20.

At step S13, the management server 20 transmits a user interface screen stored in the storage unit 27 to the purchaser terminal 10. Here, the management server 20 also transmits information of purchasable prepaid cards to the purchaser. At step S15, the purchaser terminal 10 displays the information of the purchasable prepaid cards through the display unit 15.

At step S17, if the purchasable prepaid card is one kind, the routine goes to step S19, and if not, the routine goes to step S21.

At step S19, since the purchaser does not need to select the kind of the prepaid card, the purchaser inputs a purchase unit of the displayed prepaid card, and the purchaser terminal 10 receives input of the purchase unit through the input unit 13. The purchase unit includes at least a purchase money amount (e.g. $20, $50, etc.), and the purchaser can select and input a purchase number (e.g. 2, 4, etc.) of the prepaid cards. In addition, a different money amount can be selected as the purchase unit for each selected number (e.g. one is $20 and the other is $50).

At step S21 , the purchaser terminal 10 receives input of the kind of the prepaid card selected by the purchaser, the purchase unit of each kind, and the purchase number of each kind through the input unit 13.

At step S23, the purchaser terminal 10 transmits a purchase intention including the input purchase unit (purchase unit amount), and the number of the prepaid cards, or the kind of the selected prepaid card, the purchase unit for each kind and the number for each kind to the management server 20 through the communication unit 11.

At step S25, the management server 20 performs a settlement process corresponding to the purchase intention received from the purchaser terminal 10. Here, the management server 20 causes the purchaser terminal 10 to settle the payment through the payment system 40.

At step S27, the management server 20 stores a purchasing result including the settled purchase intention of the purchaser in the storage unit 27. That is, the purchasing result includes the purchaser information, the purchase unit, the kind of the purchased prepaid card, the purchase number, etc.

In a case where the management server 20 stores the purchaser information of the purchaser manipulating the purchaser terminal 10, a general login process is performed between the above steps S11 to S15. Conversely, in a case where the management server 20 does not store the purchaser information of the purchaser, a registration procedure such as member joining to the management server 20 is taken, so that the management server 20 acquires the purchaser information of the purchaser. In addition, when registering the purchaser information, the management server 20 can examine validity of identification information and communication access information of the purchaser through the communication with the authentication system 50. That is, the management server 20 may limitedly store only the validity-confirmed purchaser information, and the purchaser may access the management server 20 through the purchaser terminal 10 and purchase the purchase unit of the prepaid card.

FIG. 8 is a flowchart showing a purchase unit granting process by the purchaser. In FIG. 8, when the purchaser intends to grant the purchased purchasing result, the purchaser terminal 10 accesses the management server 20, the management server 20 transmits the purchasing result corresponding to the purchaser, and the purchaser terminal 10 displays the current purchasing result.

At step S31 , the purchaser terminal 10 causes the purchaser to select or input the kind of the prepaid card, the purchase unit or the purchase number to be granted in the current purchasing result. The input information is granting information which may include the whole or some of the kind of the prepaid card, the purchase unit or the purchase number in the purchasing result of the purchaser. That is, the purchaser may grant the whole or some of the purchasing result.

At step S33, the purchaser terminal 10 causes the purchaser to input receiver information for granting. The receiver information to be input includes identification information and communication access information of the receiver. Hereupon, the purchaser terminal 10 transmits the granting information and the receiver information to the management server 20.

At step S35, the management server 20 causes the authentication system 50 to authenticate the input receiver information. This authentication is to confirm whether the identification information and the communication access information of the receiver information are valid for communication, or whether the receiver who the purchaser intends to grant is the same person as the receiver recognized by the identification information or the communication access information of the receiver information. That is, since the receiver based on the communication access information input by the user may be different from the receiver who the purchaser actually intends to grant (e.g. since the user may input wrong communication access information), the identification information of the receiver judged as the communication access information or the like is transmitted to the purchaser terminal 10, so that it can be judged by the purchaser. If the communication access information is valid or if the purchaser determines that the receiver to be granted is the same person as the judged receiver, it is judged that the receiver information has been authenticated, and the routine goes to step S37. If not, the routine goes to step S39.

At step S37, the management server 20 updates the corresponding purchasing result according to the granting information and the receiver information. Such a purchasing result includes the granting information and the receiver information. When the receiver accesses the management server 20 afterward, the receiver can confirm the purchasing result as his/her own.

At step S39, the management server 20 transmits a notice message notifying that the receiver information has not been authenticated to the purchaser terminal 10, and the purchaser terminal 10 displays the notice message. The routine goes to step S33 to newly input the receiver information.

The above steps S35 and S39 may be selectively performed by the management server 20.

As described earlier, the granting process of FIG. 8 may be performed after the process of FIG. 7, but may be performed simultaneously with the process of FIG. 7. That is, when steps S31 to S33 are performed after or at the same time with step S19 or S21 , before the purchaser transmits the purchase intention, the purchaser may grant the whole selected purchase unit, purchase number or kinds to the receiver, or may grant some to the receiver and own the other. The grant intention may be included in the purchase intention, or transmitted at the same time or in a close time with transmission of the purchase intention.

Moreover, some of the purchase unit, the purchase number or the kinds may be granted to a first receiver, and the other may be granted to a second receiver. That is, it is possible to grant the purchase unit and the like to the plurality of receivers. The purchase intention of the purchaser may be transmitted to the management server 20 and stored as the purchasing result.

FIG. 9 is a flowchart showing a purchase unit granting process at the management server. The management server 20 stores the purchasing result whose owner is the receiver in the storage unit 27 by the process of FIG. 8. At step S41 , the management server 20 transmits a granting message notifying that the purchase unit has been granted to the receiver to the receiver terminal 60 according to the communication access information of the receiver information included in the purchasing result. The granting message may be transmitted directly after the granting process of FIG. 8 by the purchaser. Alternatively, the management server 20 may allow the purchaser to set a time (e.g. date, hour, etc.) to transmit the granting message during or after the granting process of FIG. 8, add the set transmission time to the purchasing result, and store the purchasing result. As the transmission time is set like this, the granting message can be transmitted at a desirable time of the purchaser (e.g. a birthday of the receiver, a memorial day, etc.).

As described above, the granting message may include granting of the purchase unit or information on a place to pick up the prepaid card. The granting message may further include information (e.g. URL, etc.) for communication access to the management server 20.

At step S43, the receiver terminal 60 displays the received granting message on the display unit 65, so that the receiver can recognize granting of the purchase unit.

At step S45, it is judged whether the receiver communication-accesses the management server 20 through the receiver terminal 60. If the communication access occurs, the routine goes to step S47, and if not, the routine is ended.

At step S47, when it is possible to purchase plural kinds of prepaid cards, the receiver can change the kind of the prepaid card corresponding to the granted purchase unit. Accordingly, if it is possible to purchase or select the plural kinds of prepaid cards, the routine goes to step S49, and if not, the routine is ended.

At step S49, it should be judged whether it is possible to change the kind of the prepaid card corresponding to the purchase unit in the purchasing result of the receiver. Some kinds of prepaid cards may be set to be non-changeable at the time of purchasing. In this case, the receiver cannot change the kind of the prepaid card. If the kind of the prepaid card is changeable, the routine goes to step S53, and if not, the routine goes to step S51.

At step S51 , the management server 20 transmits a notice message notifying that the kind of the prepaid card corresponding to the purchase unit of the receiver is not changeable to the receiver terminal 60 to display the same. At step S53, if the receiver terminal 60 generates a change request for changing the kind of the prepaid card corresponding to the current purchase unit into the kind of the prepaid card selected by the receiver and transmits the change request to the management server 20, the routine goes to step S55, and if not, the routine is ended.

At step S55, the management server 20 updates the purchasing result of the receiver by the received change request.

In the above steps S53 and S55, when the receiver changes the kind of the prepaid card, the receiver may have to pay an additional fee. It is preferable to update the purchasing result of the receiver after the receiver settles the fee.

Also, in the above steps, when the purchaser owns his/her purchasing result, the purchaser may select the kind of the prepaid card through the purchaser terminal 10 in the similar manner.

FIG. 10 is a flowchart showing a granting process from one receiver to another receiver.

At step S61 , the receiver accesses the management server 20 using the receiver terminal 60. Here, in a state where receiver information of the receiver has not been stored or the receiver has not been registered, the management server 20 causes the receiver to take a login procedure or registration procedure.

At step S63, the management server 20 searches for a purchasing result where the receiver is set as an owner or receiver among the purchasing results stored in the storage unit 27.

At step S65, if there is the purchasing result corresponding to the receiver, the routine goes to step S67, and if not, the routine is ended.

At step S67, the management server 20 displays the corresponding purchasing result on the receiver terminal 60. If the receiver wants to grant the whole or some of the purchase unit included in the searched purchasing result, the routine goes to step S69, and if not, the routine is ended.

At step S69, the receiver can select or input a grant unit to be granted (the purchase unit, or the kind or purchase number of the prepaid card, etc.) in the searched purchasing result through the receiver terminal 60.

At step S71 , the receiver inputs receiver information of a second receiver to be granted the selected or input grant unit through the receiver terminal 60.

At step S73, the receiver transmits a grant intention including the grant unit and the receiver information of the second receiver to the management server 20 through the receiver terminal 60.

At step S75, the management server 20 updates the whole or some of the purchasing result of the receiver or generates a new purchasing result according to the grant intention, and stores a purchasing result corresponding to the second receiver.

In the granting process of FIG. 10, the aforementioned authenticating process can be carried out on the receiver information of the second receiver.

FIG. 1 1 shows an embodiment of information of purchasable prepaid cards provided by the management server.

The kinds of the purchasable prepaid cards provided by the management server 20 are A, B and C. It is possible to input the purchase number and the purchase unit for each kind. It is also possible to select a different purchase unit for each purchase number.

FIG. 12 shows an embodiment of a screen to which the purchaser or receiver can input receiver information in the purchase unit granting process.

This screen is to grant the whole or some of the purchasing result corresponding to the purchaser or receiver. The purchaser or receiver can select the kind of the prepaid card included in the purchasing result, and select or input the whole or some of the purchase unit as a grant unit. In addition, the purchaser or receiver can input receiver information or receiver information of the second receiver (e.g. identification information, communication access information, transmission time and message).

FIG. 13 is a flowchart showing a prepaid card activating and loading process by the provider. In order to activate and load a prepaid card selected during or after the purchasing or granting, the purchaser or receiver visits an installation position or place of the provider terminal 70. Thereafter, the purchaser or receiver asks for activation and loading of the selected prepaid card such that the following process of the flowchart is performed.

At step S81 , the provider (or operator) causes the provider terminal 70 to access the management server 20 via the network 30. In this communication access, the provider may take a login procedure for security, so that the management server 20 can identify the provider terminal 70 and the provider.

At step S83, the management server 20 transmits an input screen for the use in inputting purchaser confirmation information or receiver confirmation information to the provider terminal 70 to display the same, and the provider terminal 70 receives input of the purchaser confirmation information or the receiver confirmation information acquired from the purchaser or receiver through the input unit 73, and transmits the same to the management server 20 through the communication unit 71. Here, the confirmation information may include only communication access information, and may further include other information (e.g. identification information) besides the communication access information.

At step S85, the management server 20 receives the purchaser confirmation information or the receiver confirmation information, and judges whether a purchasing result corresponding to the purchaser confirmation information or the receiver confirmation information has been stored. If there is the corresponding purchasing result, the routine goes to step S89, and if not, the routine goes to step S87.

At step S87, the management server 20 generates a notice message notifying that there is no purchasing result corresponding to the purchaser confirmation information or the receiver confirmation information, and transmits the notice message to the provider terminal 70, and the provider terminal 70 displays the notice message. Here, the routine may be ended, or may return to step S83 to input new purchaser confirmation information or receiver confirmation information.

At step S89, the management server 20 transmits purchasing result confirmation including the corresponding purchasing result to the provider terminal 70, and the provider terminal 70 displays the purchasing result confirmation on the display unit 75 so that the provider (or operator) can see the contents. Therefore, the provider terminal 70 displays the purchasing result confirmation, notifying that the prepaid card can be activated and loaded.

At step S91 , the provider (or operator) manipulates the activation device 90 or the activation unit 78 provided in the provider terminal 70a to activate and load the prepaid card selected by the purchaser or receiver according to the confirmed purchasing result. Here, the loading includes initial loading and reloading. In this step, the provider (or operator) confirms whether the kind of the prepaid card in the contents of the purchasing result is identical to the kind of the prepaid card of which the purchaser or receiver asks for activation and loading on the scene.

At step S93, the provider terminal 70 transmits an activating and loading result obtained in step S91 by the provider (or operator) to the management server 20.

At step S95, since the activation and loading for the purchaser or receiver have been finished, the management server 20 updates the corresponding purchasing result to subtract the activated and loaded purchase unit, or completely erases the purchasing result. The purchasing result is updated when only some of the purchasing result has been loaded. Alternatively, the management server 20 may set the purchasing result where the purchase unit has been completely spent to be unavailable so as to prevent future use.

At the above step S91 , before the provider (or operator) performs activation and loading, if the management server 20 plans to perform or performs the payment settlement corresponding to the purchase unit to be loaded for the provider, the management server 20 enables the provider to confirm the plan or completion of the payment settlement. The management server 20 processes the plan or completion of the payment settlement, and displays the result on the provider terminal 70, so that the provider (or operator) can see the result with the naked eye.

In addition, at the above step S91 , before the provider (or operator) performs activation and loading, the provider terminal 70 asks for the payment settlement in order for the provider (or operator) to load the purchasing result, and the management server 20 performs the payment settlement and transmits the result to the provider terminal 70, so that the provider (or operator) can see the result with the naked eye.

Moreover, at the above step S95, after the receiver activates and loads the purchase unit of the prepaid card, when or after the management server 20 updates the purchasing result, the management server 20 transmits a notice message notifying that the receiver has activated and loaded the purchase unit to the purchaser terminal 10 to display the same, so that the purchaser can confirm it. Further, the purchaser terminal 10 may access the management server 20, so that the purchaser can confirm whether the purchasing result purchased by the purchaser and granted to the receiver has been updated, i.e. whether the receiver has activated and loaded the prepaid card. FIG. 14 is a flowchart showing a first embodiment for authenticating the purchaser or receiver, which is performed in the activating and loading process of FIG. 13. The first embodiment may be performed prior to the prepaid card activating and loading step of step S91 , and may be performed at the same time or in a close time with step S83 to authenticate the purchaser or receiver.

At step S101 , the provider terminal 70 asks for identification information of the purchaser or receiver to the management server 20 according to a request of the provider. Hereupon, the management server 20 transmits the identification information included in the purchasing result searched for in step S85 to the provider terminal 70, and the provider terminal 70 receives and displays the identification information.

At step S103, the provider confirms the identification information displayed on the provider terminal 70, asks for an appropriate identification medium (e.g. driver's license, etc.) to the purchaser or receiver, and compares the confirmed identification information with the information written in the identification medium. If the identification information is identical to the written information, the routine goes to step S105, and if not, the routine goes to step S107.

At step S105, since the purchaser or receiver has been authenticated, the routine may go to step S91.

At step S107, since the purchaser or receiver has not been authenticated, the routine is ended without going to step S91.

As another embodiment of FIG. 14, at step S83, the confirmation information is transmitted, including the communication access information and the identification information, and the management server 20 searches for a purchasing result corresponding to both the communication access information and the identification information. If the purchasing result is found, it can be judged that the identification information of the purchaser or receiver has been authenticated. If the purchasing result is not found, it can be judged that the identification information of the purchaser or receiver has not been authenticated.

As a further embodiment of FIG. 14, at step S89, the management server 20 may add the identification information of the purchaser or receiver to the purchasing result confirmation, and transmit the purchasing result confirmation. Accordingly, when displaying the purchasing result confirmation, the provider terminal 70 displays the identification information. The provider asks for an appropriate identification medium (e.g. driver's license, etc.) corresponding to the identification information, and compares the displayed identification information with the information written in the identification medium. If the displayed identification information is identical to the information written in the identification medium, since the purchaser or receiver has been authenticated, the steps following the step S91 may be carried out. If not, since the purchaser or receiver has not been authenticated, the steps following the step S91 may not be carried out.

FIG. 15 is a flowchart showing a second embodiment for authenticating the purchaser or receiver, which is performed in the activating and loading process of FIG. 13.

At step S11 1 , the management server 20 generates and stores an authentication code for itself and transmits the authentication code to the receiver terminal 60 (or the purchaser terminal 10), or asks for an authentication code to the authentication system 50, receives and stores the authentication code, and transmits the authentication code to the receiver terminal 60 (or the purchaser terminal 10). Here, when receiving the confirmation information at step S83, the management server 20 may perform step S1 1 1 at the same time or in a close time. Also, the management server 20 may access the receiver terminal 60 (or the purchaser terminal 10), receive an authentication code request from the purchaser or receiver through the receiver terminal 60 (or the purchaser terminal 10), and perform step S1 1 1. Hereupon, the receiver terminal 60 (or the purchaser terminal 10) receives the authentication code, and allows the receiver or purchaser to visually or audibly confirm the authentication code. That is, the authentication code may be transmitted via text or voice such as ARS.

At step S1 13, the provider terminal 70 receives input of the authentication code displayed on the receiver terminal 60 (or the purchaser terminal 10) through the input unit 73, and transmits the input authentication code to the management server 20.

At step S1 15, the management server 20 compares the prestored authentication code with the authentication code received from the provider terminal 70. If the authentication codes are the same, the routine goes to step S1 17, and if not, the routine goes to step S1 19. At step S1 17, the management server 20 judges that the received authentication code has been authenticated, and transmits the authentication result to the provider terminal 70. Hereupon, the provider terminal 70 displays the authentication result so that the steps following the step S91 can be carried out.

At step S1 19, the management server 20 judges that the received authentication code has not been authenticated, and transmits the authentication result to the provider terminal 70. Hereupon, the provider prevents the steps following the step S91.

As another embodiment of FIG. 15, in a case where a One Time Password (OTP) generation means (or generation program) is provided in the receiver terminal 60 (or the purchaser terminal 10) and an OTP generation means or data is stored in the management server 20, the purchaser or receiver can be authenticated using a OTP. The receiver terminal 60 (or purchaser terminal 10) generates and displays a OTP according to a OTP generation command. Hereupon, the provider terminal 70 transmits the generated OTP to the management server 20, and the management server 20 compares the received OTP with a OTP generated by the OTP generation means provided therein or a OTP in the OTP data, to thereby authenticate the received OTP. If the OTPs are the same, the routine is performed like step S1 17, and if not, the routine is performed like step S1 19.

FIG. 16 is a flowchart showing a third embodiment for authenticating the purchaser or receiver, which is performed in the activating and loading process of FIG. 13. The provider terminal 70 accesses the management server 20 via the network 30 to communicate therewith.

At step S141 , the management server 20 displays a screen for the use in inputting communication access information on the provider terminal 70. Hereupon, the provider (or operator) manipulating the provider terminal 70 acquires communication access information of the user terminal (the purchaser terminal 10 or the receiver terminal 60) from the user (the purchaser or receiver), and inputs the communication access information. The provider terminal 70 transmits the communication access information of the user to the management server 20, and the management server 20 stores the communication access information of the user.

At step S143, the provider (or operator) asks the user to transmit an approval message (text, voice, image, etc.) to the management server 20 using the user terminal. This approval message simply includes 'yes' or the like, so that the management server 20 can recognize the approval for activation and loading of the prepaid card from the user terminal. This approval message is transmitted by the user terminal, and its receiver is the management server 20. For example, the approval message is transmitted to the management server 20 by a text transmission system using a short code. However, as far as the message does not include disapproval contents, even if the message does not have any contents, it can be deemed as an approval message.

At step S145, the management server 20 receives the approval message via the short code.

At step S147, the management server 20 compares the communication access information of the user terminal which is a sender of the approval message with the prestored communication access information of the user terminal transmitted from the provider terminal 70. If the communication access information is the same, the routine goes to step S149, and if not, the routine goes to step S151.

At the above step S147, the comparison is performed for a certain time because the approval message transmitted from the user terminal may be delayed for some reason. Further, if the same communication access information is not received for the certain time, the routine goes to step S151.

In addition, at step S147, when the message includes a disapproval intention, even if the communication access information is the same, it is judged as non- authentication, and the routine may go to step S151. Moreover, when the message includes an approval intention, if the communication access information is the same, it is judged as authentication, and the routine may go to step S149.

At step S149, the management server 20 authenticates the communication access information of the user terminal, and transmits the authentication result to the provider terminal 70. The provider terminal 70 displays the authentication result so that the provider (or operator) can see the authentication result. The routine goes to S91 to activate and load the prepaid card.

At step S151 , the management server 20 does not authenticate the communication access information of the user terminal received from the provider terminal 70, and transmits the non-authentication result to the provider terminal 70. The provider terminal 70 displays the non-authentication result so that the provider (or operator) can see the non-authentication result. Accordingly, the provider may end the routine without activating and loading the prepaid card, or may go to step S141 to request and input the communication access information of the user terminal again.

Next, when the purchaser or receiver intends to change a kind of a prepaid card corresponding to an owned or granted purchase unit, for the change, a process for the management server 20 exchanging the purchase units will be described.

The management server 20 receives a request (change request or exchange request) for changing a purchase unit of a current kind into a purchase unit of a target kind from the purchaser terminal 10 or the receiver terminal 60 (or the user terminal), and stores the request like FIG. 17. As illustrated in FIG. 17, in the management server 20, kinds of purchasable prepaid cards are A to E (five kinds), and users are H1 to H8 (eight persons). An operation of the management server 20 corresponding to the change request will be explained with reference to FIG. 18. The change request includes at least user information (identification information, communication access information), a current kind and a target kind. The change request may further include a purchase unit.

FIG. 18 is a flowchart showing a process of the management server 20 to change or exchange kinds of prepaid cards corresponding to purchase units.

At step S121 , the management server 20 receives a change request (or exchange request) including a current kind and a target kind from the user terminal (the purchaser terminal 10 or the receiver terminal 60) via the network 30.

At step S123, the management server 20 generates and stores a change request table including the received change requests like FIG. 17.

At step S125, the management server 20 confirms the current kinds and the target kinds in the change requests, and sets a change user group who can exchange the kinds of the prepaid cards with each other. When there are a change request having a current kind identical to a target kind of another change request and a change request having a target kind identical to a current kind of another change request, the step for setting the change user group selects the change requests of such relation. That is, the change requests which can change or exchange the kinds of the prepaid cards with each other exist in the change user group. The group may be set in the order of reception of the change requests.

At step S127, it is judged whether there is the change user group formed in the group setting step S125. If there is no change user group, the routine goes to step S121. If not, the routine goes to step S129.

At step S129, the management server 20 asks for confirmation of the change to the user terminal of the user in the change user group. As the management server 20 receives such confirmation from the user before changing the kind, it can perform high reliable change or exchange.

At step S131 , the management server 20 judges whether it has received confirmation from all the user terminals in the change user group. If so, the routine goes to step S133. If not, the management server 20 repeatedly performs step S131. After a certain time elapses, the management server 20 judges that the receiver rejects the change or exchange, erases the generated user change group, and ends the procedure.

At step S133, the management server 20 updates the purchasing results of the users in the change user group, i.e. adds the contents of the target kind to the current kind with respect to each change request of the change user group. That is, the purchasing results of the users in the change user group are updated, including the purchase unit of the target kind. As a result, the kinds are changed or exchanged.

At step S135, the management server 20 notifies the updating results to the respective users corresponding to the updated purchasing results, thereby informing the users of owning the purchase unit of the updated kind.

In FIG. 18, the management server 20 may include a step for charging the user with the purchasing result updated. That is, the management server 20 may gratuitously or onerously change or exchange the kinds of the prepaid cards.

FIG. 19 shows an example of the grouping step in FIGS. 17 and 18. Referring to FIG. 19, at step S125, the change user group may be composed of two or more independent change user subgroups.

As illustrated in FIG. 9, a change user subgroup Sub1 includes change requests of users H1 , H2 and H5, and a change user subgroup Sub2 includes change requests of users H6 and H8. Current kinds or target kinds of the respective change requests of one independent change user subgroup are different from current kinds or target kinds of the respective change requests of another independent change user subgroup.

When there are such change user subgroups, at steps S129 to S135, the management server 20 asks for confirmation to every change user subgroup. If the management server 20 receives confirmation from all the user terminals of the users in the same change user subgroup, it can perform updating of step S133.

In addition, when the change request includes the purchase unit, for the change or exchange, it should be further judged whether the change user group has same purchase units or purchase units with an equivalent value. For example, when the purchase unit of the user H6 is $30, if the purchase unit of the user H8 is $30, they can be changed or exchanged.

Moreover, there are change requests of users H3, H4 and H7 who do not belong to the change user group.

Meanwhile, another embodiment of the present invention will be described.

Another embodiment of the present invention is also implemented with the system of FIGS. 1 to 6, and the devices including the purchaser terminal 10, the management server 20, the network 30, the payment system 40, the authentication system 50, the receiver terminal 60, the provider terminal 70, the prepaid card administration server 80 and the activation device 90. However, a characteristic of a purchase unit processed in the purchase unit managing system of FIGS. 1 to 6 is more or less different. This embodiment relates to purchasing, granting, activation and loading of a purchase unit which is not limited to a kind of a prepaid card, so that a purchaser or receiver can ask for activation and loading of one or more desirable prepaid cards.

The purchaser terminal 10 is a device which displays purchasable prepaid cards provided by the management server 20, or enables the purchaser to select, settle and authenticate a purchase unit (or an overall size of a purchase unit). That is, the purchase unit may not correspond to a specific kind of prepaid card.

The management server 20 is a system which enables the purchaser to select a purchase unit without selecting a kind of a prepaid card, causes the receiver to receive an additionally purchased purchase unit, authenticates the purchaser and the receiver, causes the purchaser to settle the payment to purchase the purchase unit, transmits a granting message to the receiver, and accesses the provider terminal 70 to authenticate activation and loading of the prepaid card selected by the purchaser or receiver and perform a payment settlement process for a provider.

The receiver terminal 60 may access the management server 20 via the network 30, and select a kind of a prepaid card corresponding to a granted purchase unit or grant the purchase unit to another receiver.

The provider terminal 70 is a device which directly activates and loads the prepaid card selected by the purchaser or receiver, or performs display for activation and loading of the prepaid card.

In detail, the processor 19 of the purchaser terminal 10 causes the purchaser to input, purchase and settle a purchase unit (or a total purchase amount of the purchase unit). Also, the purchaser terminal 10 can receive kinds of prepaid cards (or purchasable prepaid cards) which can be activated and loaded with the purchase unit from the management server 20, and display the kinds of the prepaid cards. The processor 19 performs the aforementioned function, and examples for carrying out such a function will be described below in detail.

In addition, the management server 20 includes the processor 29 which enables the purchaser to input, purchase and settle the purchase unit, transmits a granting message to the receiver when the purchaser grants the purchased purchase unit, and performs a re-granting process from the receiver to another receiver. Moreover, when the kinds of the prepaid cards which can be activated and loaded with the purchase unit whose owner is the purchaser or receiver are limitative, the management server 20 stores kind information of the prepaid cards (or the purchasable prepaid cards), and transmits the kind information to the purchaser terminal 10 or the receiver terminal 60 to display the same.

Data stored in the storage unit 27 and managed by the processor 29 may include purchaser information acquired from the purchaser terminal 10, receiver information, purchasable, i.e. salable purchase unit information input by a manager or from an external server, provider information, authentication information, purchasing result, settlement information, etc. The purchaser information, the authentication information, the provider information, the authentication information and the settlement information are identical to those explained with reference to FIG. 3, but the other are more or less different in the following respects. The purchasable purchase unit information includes a purchase unit which can be input by the purchaser, and an image or text for the use in selecting or inputting the purchase unit. The purchase unit may be equal to or larger than a money amount activated and loaded on one or more prepaid cards in the provider terminal 70. For example, when the kinds of the prepaid cards which can be activated and loaded with the purchase unit are limitative, the purchase unit information can provide the purchaser or receiver with the kinds of the prepaid cards which can be activated and loaded.

In addition, the purchase unit can be selected by the purchaser, and is equivalent to a money amount loaded on an account of the prepaid card at the time of activation and loading of the prepaid card. For example, the purchase unit may be equivalent to $20 or 20,000 points. The purchase unit may be equal to or larger than the money amount loaded on the account. That is, it is because the purchaser may have to pay a service fee to an administrator or administration company of the management server 20. On the same reason, a money amount settled by the purchaser should be equal to or larger than the purchase unit.

The purchasing result includes a purchased or granted purchase unit (or a purchase unit value), and purchaser information or receiver information.

Moreover, after purchasing the purchase unit, when the purchaser or receiver selects a kind of a prepaid card (one or more kinds), the purchasing result may further include information of the kind of the selected prepaid card.

Further, the processor 69 of the receiver terminal 60 displays a granting message for the purchase unit to the receiver, or enables the receiver to select the kind of the purchasable prepaid card transmitted from the management server 20 and re- grant the granted purchase unit. The processor 69 performs the aforementioned function, and examples for carrying out such a function will be described below in detail.

Furthermore, the processor 79 of the provider terminal 70 receives input of receiver confirmation information (or purchaser confirmation information), transmits the same to the management server 20, receives and displays confirmation of the receiver (or purchaser) and a purchasing result corresponding to the receiver (or purchaser), and displays that a prepaid card corresponding to a purchase unit included in the purchasing result can be activated and loaded as shown in FIG. 5. The processor 79 performs the aforementioned function, and examples for carrying out such a function will be described below in detail.

Alternatively, like FIG. 6, the processor 79 of the provider terminal 70 enables the activation unit 78 to activate and load the prepaid card selected by the receiver (or purchaser) confirmed by the management server 20.

FIG. 20 is a flowchart showing another purchase unit purchasing process by the purchaser terminal.

Step S21 1 is identical to step S1 1 of FIG. 7.

At step S213, the management server 20 transmits a user interface screen stored in the storage unit 27 to the purchaser terminal 10. Here, when kinds of prepaid cards which the purchaser (or user) can activate and load are limitative, the management server 20 also transmits information of purchasable prepaid cards to the purchaser (or user) for reference.

At step S215, the purchaser terminal 10 displays the information of the prepaid cards through the display unit 15.

At step S217, since the purchaser does not need to select the kind of the prepaid card, the purchaser inputs a purchase unit, and the purchaser terminal 10 receives input of the purchase unit through the input unit 13. The purchase unit includes at least a purchase money amount (e.g. $20, $50, etc.), and the purchaser can select or input a purchase number (e.g. 2, 4, etc.). In addition, a different money amount can be selected as the purchase unit for each selected number (e.g. one is $20 and the other is $50).

At step S219, the purchaser terminal 10 transmits a purchase intention including the input purchase unit (purchase unit amount) or the purchase number of the purchase unit to the management server 20 through the communication unit 11.

At step S221 , the management server 20 performs a settlement process corresponding to the purchase intention received from the purchaser terminal 10. Here, the management server 20 causes the purchaser terminal 10 to perform the settlement through the payment system 40.

At step S223, the management server 20 stores a purchasing result including the settled purchase intention of the purchaser in the storage unit 27. That is, the purchasing result includes the purchaser information, the purchase unit, the purchase number, etc. In a case where the management server 20 stores the purchaser information of the purchaser manipulating the purchaser terminal 10, a general login process is performed between the above steps S211 to S215. Conversely, in a case where the management server 20 does not store the purchaser information of the purchaser, a registration procedure such as member joining to the management server 20 is taken, so that the management server 20 acquires the purchaser information of the purchaser.

In addition, when registering the purchaser information, the management server 20 can examine validity of identification information and communication access information of the purchaser through the communication with the authentication system 50. That is, the management server 20 may limitedly store only the validity-confirmed purchaser information, and the purchaser may access the management server 20 through the purchaser terminal 10 and purchase the purchase unit of the prepaid card.

FIG. 21 is a flowchart showing another purchase unit granting process by the purchaser. In FIG. 21 , when the purchaser intends to grant the purchased purchasing result, the purchaser terminal 10 accesses the management server 20, the management server 20 transmits the purchasing result corresponding to the purchaser, and the purchaser terminal 10 displays the current purchasing result.

At step S231 , the purchaser terminal 10 causes the purchaser to select or input the purchase unit or the purchase number to be granted in the current purchasing result. The input information is granting information which may include the whole or some of the purchase unit or the purchase number in the purchasing result of the purchaser. That is, the purchaser may grant the whole or some of the purchasing result.

Step S233 is similar to step S33 of FIG. 8. The purchaser terminal 10 transmits the granting information and receiver information to the management server 20.

Step S235 is similar to step S35 of FIG. 8. The management server 20 causes the authentication system 50 to authenticate the input receiver information. If the communication access information is valid or if the purchaser determines that the receiver to be granted is the same person as the judged receiver, it is judged that the receiver information has been authenticated, and the routine goes to step S237. If not, the routine goes to step S239.

Step S237 is similar to step S37. The management server 20 updates the corresponding purchasing result according to the granting information and the receiver information.

Step S239 is similar to step S39 of FIG. 8.

The above steps S235 and S239 may be selectively performed by the management server 20.

As described earlier, the granting process of FIG. 21 may be performed after the process of FIG. 20, but may be performed simultaneously with the process of FIG. 20. That is, when steps S231 to S233 are performed after or at the same time with step S219 or S221 , before the purchaser transmits the purchase intention, the purchaser may grant the selected purchase unit or purchase number to the receiver, or may grant some to the receiver and own the other. The grant intention may be included in the purchase intention, or transmitted at the same time or in a close time with transmission of the purchase intention.

Moreover, some of the purchase unit, the purchase number or the kinds may be granted to a first receiver, and the other may be granted to a second receiver. That is, it is possible to grant the purchase unit and the like to the plurality of receivers. The purchase intention of the purchaser may be transmitted to the management server 20 and stored as the purchasing result.

FIG. 22 is a flowchart showing another purchase unit granting process at the management server. The management server 20 stores a purchasing result whose owner is the receiver in the storage unit 27 like FIG. 9.

Step S241 is similar to step S41 of FIG. 9.

Step S243 is similar to step S43 of FIG. 9.

Step S245 is similar to step S45 of FIG. 9. If the communication access occurs, the routine goes to step S247, and if not, the routine is ended.

At step S247, the management server 20 acquires receiver information of the receiver terminal 60, or confirms the receiver via a login procedure of the receiver, and displays the purchasing result of the receiver. If there is no purchasing result, it will not be displayed.

At step S249, it should be judged whether it is possible to select a kind of a prepaid card with respect to the purchase unit in the purchasing result of the receiver. For example, when there are one or more kinds of selectable prepaid cards, the routine goes to step S251. Alternatively, if the receiver cannot select a kind of a prepaid card with respect to the granted purchase unit, or if the management server 20 does not provide a service for selecting a kind of a prepaid card, the routine is ended.

At step S251 , the management server 20 transmits information of prepaid cards which can be selected by the receiver to the receiver terminal 60, and the receiver terminal 60 displays the prepaid card information, so that the receiver can see the kinds of the selectable prepaid cards. The receiver arbitrarily selects the kind of the prepaid card among the kinds of the selectable prepaid cards. Here, the whole purchase unit or purchase number may be selected corresponding to the kind of the specific prepaid card, or some purchase unit or purchase number may be selected corresponding to the kind of the specific prepaid card. The receiver terminal 60 generates selection information including the kind of the prepaid card, the purchase unit (or purchase unit size) or the purchase number, and transmits the selection information to the management server 20.

At step S253, the management server 20 updates the purchasing result of the receiver by the received selection information.

In the above steps S251 and S253, when selecting the kind of the prepaid card, the receiver may have to pay an additional fee. It is preferable to update the purchasing result of the receiver after the receiver settles the fee.

Also, in the above steps, when the purchaser owns his/her purchasing result, the purchaser may select the kind of the prepaid card through the purchaser terminal 10 in the similar manner.

FIG. 23 is a flowchart showing another granting process from one receiver to another receiver. The process of FIG. 23 is similar to the process of FIG. 10 described above.

Steps S261 to S267 are performed identically to steps S61 to S67 of FIG. 10, respectively.

At step S269, the receiver can select or input a grant unit to be granted (a purchase unit, or a kind or purchase number of a prepaid card, etc.) in the searched purchasing result through the receiver terminal 60. The receiver terminal 60 stores granting information including the grant unit.

Steps S271 and S273 are performed similarly to steps S71 and S73 of FIG. 10, respectively.

The aforementioned authenticating process may be performed on receiver information of a second receiver in the granting process of FIG. 23.

FIG. 24 shows another embodiment of the information of the purchasable prepaid cards provided by the management server.

The kinds of the prepaid cards provided by the management server 20 are A, B and C, and the purchaser can input the purchase number or purchase unit. It is recognized that the purchase unit can be used to activate and load one or more kinds A, B and C of the prepaid cards.

FIG. 25 shows another embodiment of a screen to which the purchaser or receiver can input receiver information in the purchase unit granting process.

This screen is to grant the whole or some of the purchasing result corresponding to the purchaser or receiver. The purchaser or receiver can select or input the whole or some of the purchase unit (or purchase number) included in the purchasing result as a grant unit. In addition, the purchaser or receiver can input receiver information or receiver information of the second receiver (e.g. identification information, communication access information, transmission time and message).

FIG. 26 is a flowchart showing another prepaid card activating and loading process by the provider. The purchaser or receiver may select a desirable kind of prepaid card in a store where the provider terminal 70 has been installed, or select a kind of a prepaid card in advance by the prepaid card selecting process of FIG. 22. In order to activate and load the selected prepaid card, the purchaser or receiver visits an installation position or place of the provider terminal 70. Thereafter, the purchaser or receiver asks for activation and loading of the selected prepaid card such that the following process of the flowchart is performed.

Steps S281 to S287 are performed identically to steps S81 to S87 of FIG. 13, respectively.

At step S289, the management server 20 transmits purchasing result confirmation including the corresponding purchasing result to the provider terminal 70, and the provider terminal 70 displays the purchasing result confirmation on the display unit 75 so that the provider (or operator) can see the contents. Therefore, the provider terminal 70 displays the purchasing result confirmation, notifying that the prepaid card can be activated and loaded.

At step S291 , the provider (or operator) manipulates the activation device 90 or the activation unit 78 provided in the provider terminal 70a to activate and load the prepaid card selected by the purchaser or receiver according to the confirmed purchasing result. Here, the loading includes initial loading and reloading. In this step, when the kind of the prepaid card has been selected in advance like FIG. 9, the provider (or operator) confirms whether the kind of the prepaid card in the contents of the purchasing result is identical to the kind of the prepaid card of which the purchaser or receiver asks for activation and loading on the scene.

At step S293, the provider terminal 70 transmits an activating and loading result obtained in step S291 by the provider (or operator) to the management server 20.

At step S295, since the activation and loading for the purchaser or receiver have been finished, the management server 20 updates the corresponding purchasing result to subtract the activated and loaded purchase unit, or completely erases the purchasing result. The purchasing result is updated when only some of the purchasing result has been loaded. Alternatively, the management server 20 may set the purchasing result where the purchase unit has been completely spent to be unavailable so as to prevent future use.

At the above step S291 , before the provider (or operator) performs activation and loading, if the management server 20 plans to perform or performs the payment settlement corresponding to the purchase unit to be loaded for the provider, the management server 20 enables the provider to confirm the plan or completion of the payment settlement. The management server 20 processes the plan or completion of the payment settlement, and displays the result on the provider terminal 70, so that the provider (or operator) can see the result with the naked eye.

In addition, at the above step S91 , before the provider (or operator) performs activation and loading, the provider terminal 70 asks for the payment settlement in order for the provider (or operator) to load the purchasing result, and the management server 20 performs the payment settlement and transmits the result to the provider terminal 70, so that the provider (or operator) can see the result with the naked eye.

Moreover, at the above step S295, after the receiver activates and loads the purchase unit of the prepaid card, when or after the management server 20 updates the purchasing result, the management server 20 transmits a notice message notifying that the receiver has activated and loaded the purchase unit to the purchaser terminal 10 to display the same, so that the purchaser can confirm it. Further, the purchaser terminal 10 may access the management server 20, so that the purchaser can confirm whether the purchasing result purchased by the purchaser and granted to the receiver has been updated, i.e. whether the receiver has activated and loaded the prepaid card.

The purchaser manipulating the purchaser terminal 10 may correspond to a purchase unit buyer, purchaser, gift giver, gift sender, etc. In addition, the receiver manipulating the receiver terminal 60 may correspond to a receiver, recipient, redeemer, re-gifter, etc. Moreover, the provider manipulating or owning the provider terminal 70 may include a seller and an issuer. Here, the seller may correspond to a reseller or retailer, e.g. a supermarket, retailer store, convenience store, etc, and the issuer may correspond to a merchant or issuer, e.g., Starbucks, Bed bath & beyond, McDonald's, etc. The provider terminal manipulated by the seller may include e.g. a credit card reader, a credit card reader mounted in a POS, etc.

Although the present invention has been illustrated and described in connection with the accompanying drawings and the preferred embodiments, the present invention is not limited thereto and is defined by the appended claims. Therefore, it will be understood by those skilled in the art that various modifications and changes can be made thereto without departing from the spirit and scope of the invention defined by the appended claims.

Claims

[CLAIMS]

1. A purchase unit managing system, comprising: a purchaser terminal including a communication unit that communicates with a management server via a network, a display unit that displays information of purchasable prepaid cards received through the communication unit, an input unit that receives, from a purchaser, input of a purchase intention for one or more of the displayed purchasable prepaid cards, and receiver information including communication access information for communication access to a receiver, and a processor that controls the communication unit, the display unit and the input unit to transmit the purchase intention for the purchasable prepaid card and the receiver information to the management server; the management server including a communication unit that communicates with the purchaser terminal, a receiver terminal and a provider terminal via the network, a storage unit that stores the information of the purchasable prepaid cards, and the purchase intention and the receiver information received from the purchaser terminal, and a processor that controls the communication unit and the storage unit to transmit the information of the purchasable prepaid cards to the purchaser terminal, receive the purchase intention, generate and store a purchasing result including the settled purchase intention and at least some of the receiver information after the purchaser performs a settlement process of the purchase intention, transmit a granting message notifying that loading of the prepaid card is possible or a loadable kind and a loadable money amount to the receiver terminal according to the receiver information, search for a purchasing result corresponding to receiver confirmation information received from the provider terminal, and transmit purchasing result confirmation for the searched purchasing result to the provider terminal, or perform a settlement process of the searched purchasing result for a provider; the receiver terminal including a communication unit that communicates with the management server, and a display unit that receives the granting message from the management server and displays the granting message; and the provider terminal including a communication unit that communicates with the management server, an input unit that receives input of the receiver confirmation information including at least communication access information of the receiver, a display unit that displays an input screen received from the management server for the use in inputting the receiver confirmation information, and a processor that controls the communication unit, the input unit and the display unit to access the management server through the communication unit, display the input screen, receive input of the receiver confirmation information, transmit the receiver confirmation information to the management server, and activate and load the prepaid card or display that activation and loading of the prepaid card are possible on the display unit according to reception of the purchasing result confirmation from the management server or a result of the settlement performed by the management server.

2. The purchase unit managing system of claim 1 , wherein, when the information of the purchasable prepaid cards comprises plural kinds of prepaid cards, the purchaser terminal acquires a purchase intention including one or more kinds of prepaid cards selected by the purchaser, and a purchase unit for each kind of prepaid card or a purchase number of each kind of prepaid card, and transmits the purchase intention to the management server.

3. The purchase unit managing system of claim 2, wherein the receiver terminal can access the management server and select changing of the selected prepaid card into another kind of prepaid card, and the management server updates the purchasing result, reflecting the kind of the prepaid card selected for change.

4. The purchase unit managing system of claim 1 , wherein a money amount loaded by the provider terminal or displayed as being loadable is equal to or smaller than a money amount settled by the purchaser.

5. A purchase unit managing system, comprising: a purchaser terminal including a communication unit that communicates with a management server via a network, an input unit that receives, from a purchaser, input of a purchase intention including a purchase unit of a prepaid card, and receiver information including communication access information for communication access to a receiver, and a processor that controls the communication unit and the input unit to transmit the purchase intention and the receiver information to the management server; the management server including a communication unit that communicates with the purchaser terminal, a receiver terminal and a provider terminal via the network, a storage unit that stores the purchase intention and the receiver information received from the purchaser terminal, and a processor that controls the communication unit and the storage unit to transmit information of a purchasable purchase unit to the purchaser terminal, receive the purchase intention, generate and store a purchasing result including the settled purchase intention and at least some of the receiver information after the purchaser performs a settlement process of the purchase intention, transmit a granting message notifying that loading of the prepaid card is possible or a loadable kind and a loadable money amount to the receiver terminal according to the receiver information, search for a purchasing result corresponding to receiver confirmation information received from the provider terminal, and transmit purchasing result confirmation for the searched purchasing result to the provider terminal, or perform a settlement process of the searched purchasing result for a provider; the receiver terminal including a communication unit that communicates with the management server, and a display unit that receives the granting message from the management server and displays the granting message; and the provider terminal including a communication unit that communicates with the management server, an input unit that receives input of the receiver confirmation information including at least communication access information of the receiver, a display unit that displays an input screen received from the management server for the use in inputting the receiver confirmation information, and a processor that controls the communication unit, the input unit and the display unit to access the management server through the communication unit, display the input screen, receive input of the receiver confirmation information, transmit the receiver confirmation information to the management server, and activate and load one or more prepaid cards selected by the receiver or display that activation and loading of the prepaid card selected by the receiver are possible on the display unit according to reception of the purchasing result confirmation from the management server or a result of the settlement performed by the management server.

6. The purchase unit managing system of claim 5, wherein a money amount activated and loaded on the prepaid card in the provider terminal or displayed as being activatable and loadable is equal to or smaller than a money amount settled by the purchaser.

7. The purchase unit managing system of claim 5, wherein the management server stores information of purchasable prepaid cards which can be activated and loaded with the purchase unit, and transmits the stored information of the purchasable prepaid cards to the purchaser terminal, and the purchaser terminal displays the received information of the purchasable prepaid cards.

8. The purchase unit managing system of claim 5, wherein the management server stores information of purchasable prepaid cards which can be activated and loaded with the purchase unit, the receiver terminal accesses the management server, receives and displays information of selectable prepaid cards according to a purchasing result corresponding to the receiver, and transmits, to the management server, selection information including one or more kinds of prepaid cards selected by the receiver through the input unit or a purchase unit size corresponding to the kind, and the management server updates and stores the purchasing result of the receiver according to the selection information of the receiver.

9. The purchase unit managing system of claim 8, wherein the provider terminal activates and loads each selected kind of prepaid card with the corresponding purchase unit size according to the updated purchasing result, or displays that activation and loading are possible.

10. The purchase unit managing system of claim 9, wherein a money amount activated and loaded by the updated purchasing result or displayed as being activatable and loadable is equal to or smaller than the purchase unit or the total purchase unit of the selected prepaid cards.

1 1. The purchase unit managing system of either claim 1 or 5, wherein a loaded money amount of the prepaid card is some or the whole of a loadable money amount.

12. The purchase unit managing system of any one of claims 1 to 10, wherein the provider terminal comprises a terminal that activates and loads the prepaid card selected by the purchaser or selected by the receiver for change.

13. The purchase unit managing system of any one of claims 1 to 10, comprising a terminal that is electrically disconnected from the provider terminal to activate and load the prepaid card selected by the purchaser or selected by the receiver for change.

14. The purchase unit managing system of either claim 1 or 5, wherein the communication access information comprises one or more of a telephone number, e- mail address and fax number of the receiver.

15. The purchase unit managing system of claim 14, wherein the receiver information stored in the management server comprises identification information for identifying the receiver.

16. The purchase unit managing system of claim 15, wherein, when or after confirming the purchasing result, the management server further receives the identification information of the receiver from the provider terminal, and compares the received identification information of the receiver with the prestored identification information of the receiver, to thereby authenticate the receiver terminal.

17. The purchase unit managing system of claim 15, wherein, when transmitting purchasing result confirmation, the management server transmits the prestored identification information of the receiver to the provider terminal at the same time or in a close time, and the provider terminal displays the identification information of the receiver to be confirmed by the provider.

18. The purchase unit managing system of either claim 1 or 5, wherein, when or after confirming the purchasing result, the management server generates an authentication code corresponding to the purchasing result, stores the authentication code in the storage unit, visibly or audibly transmits the authentication code to the receiver terminal, receives an authentication code input to the provider terminal from the provider terminal afterward, and compares the received authentication code with the stored authentication code, to thereby authenticate the receiver terminal.

19. The purchase unit managing system of either claim 1 or 5, wherein, when or after confirming the purchasing result, the management server receives an authentication code request from the receiver terminal, generates an authentication code corresponding to the purchasing result in response to the request, stores the authentication code in the storage unit, visibly or audibly transmits the authentication code to the receiver terminal, receives an authentication code input to the provider terminal from the provider terminal afterward, and compares the received authentication code with the stored authentication code, to thereby authenticate the receiver terminal.

20. The purchase unit managing system of claim 18, wherein the management server transmits an authentication result to the provider terminal, and performs settlement for the provider according to a settlement request received from the provider terminal afterward.

21. The purchase unit managing system of claim 20, wherein the management server performs settlement in response to the settlement request, and transmits a settlement result to the provider terminal.

22. The purchase unit managing system of claim 20, wherein the provider terminal transmits an activating and loading result to the management server after activating and loading the prepaid card, and the management server updates or erases the purchasing result or sets the purchasing result to be non-available according to the activating and loading result.

23. The purchase unit managing system of either claim 1 or 5, wherein the purchaser terminal and the receiver terminal are identical.

24. The purchase unit managing system of either claim 1 or 5, wherein the receiver terminal comprises an OTP generation means, generates an OTP according to the receiver's command, and displays the OTP on the display unit, the provider terminal transmits the input OTP to the management server, and the management server directly verifies the received OTP or causes an external system to verify the received OTP, to thereby authenticate the receiver.

25. The purchase unit managing system of either claim 1 or 5, wherein the provider terminal acquires the communication access information of the receiver terminal from the receiver and transmits the communication access information to the management server, the receiver terminal transmits an approval message to the management server, and the management server compares the communication access information received from the provider terminal with the communication access information of the receiver terminal corresponding to the approval message, and authenticates the receiver terminal if the communication access information is the same.

26. The purchase unit managing system of claim 25, wherein the receiver terminal transmits the approval message to the management server using a short code.

27. The purchase unit managing system of claim 15, wherein the management server confirms validity of the receiver according to the communication access information of the receiver, or causes an external system to confirm validity of the receiver, and stores the result in the storage unit.

28. The purchase unit managing system of claim 27, wherein the management server transmits a granting message, confirms a purchasing result or performs settlement only for the validity-confirmed receiver information of the receiver.

29. A purchase unit exchanging method, comprising: receiving, at a management server, a change request for changing a current kind of a prepaid card included in a purchasing result corresponding to each user into a target kind from two or more first to Nth user terminals; storing, at the management server, the change requests including the current kinds and the target kinds of the respective first to Nth users; confirming the current kinds and the target kinds in the change requests, and setting a change user group who can change the kinds of the prepaid cards with each other; and changing the current kinds of the respective users into the target kinds in the change user group, and updating purchasing results corresponding to the users in the change user group.

30. The purchase unit exchanging method of claim 29, wherein, when there are a change request having a current kind identical to a target kind of another change request and a change request having a target kind identical to a current kind of another change request, the step for setting the change user group selects the change requests of such relation.

31. The purchase unit exchanging method of claim 30, wherein independent user subgroups can be formed in the change user group, and current kinds or target kinds of respective change requests of one independent change user subgroup are different from current kinds or target kinds of respective change requests of another independent change user subgroup.

32. The purchase unit exchanging method of claim 29, comprising charging, at the management server, the user with the purchasing result updated.

33. The purchase unit exchanging method of any one of claims 29 to 31 , comprising receiving, at the management server, conformation for the change from the respective user terminals between the setting step and the updating step, wherein, when the management server receives confirmation from all the users in the change user group or from all the users in each independent change user subgroup, the management server performs the updating step.

34. A purchase unit managing method of a purchase unit managing system including a management server that can communicate with at least a first receiver terminal and stores purchasing results of one or more receivers, the method comprising: accessing, at the management server, the first receiver terminal; searching, at the management server, for a prestored first purchasing result corresponding to first receiver confirmation information from the first receiver terminal; if the first purchasing result exists, receiving, at the management server, granting information of at least some of a purchase unit included in the searched first purchasing result and second receiver information from the first receiver terminal; generating a second purchasing result corresponding to the granting information and the second receiver information according to the received second receiver information, and updating the first purchasing result.

35. The purchase unit managing method of claim 34, wherein the granting information comprises one or more kinds of prepaid cards and a purchase unit included in the first purchasing result.

36. The purchase unit managing method of claim 34, comprising transmitting, at the management server, a notice message notifying that the purchase unit is granted to the receiver to the receiver terminal according to the receiver information.