JP2007304806A - Card managing system, card managing server, card managing method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a card managing system, a card managing server, a card managing method, and a program, capable of managing a plurality of cards by a single card without registering personal information etc. relating to the card managing system having the card in which an ID is recorded, the card managing server for managing card information of the card, and a terminal for reading the ID from the card, for performing communication with the card managing server via a network, and for updating the card information. <P>SOLUTION: The card managing system is provided with the card in which the ID is recorded, the card managing server for managing the card information including remaining balance of the card, and a terminal capable of updating the card information, for reading the ID from the card, and for performing communication with the card managing server via the network, wherein the card managing server is enabled to update the remaining balance of a plurality of cards all at a time by registering the card information of the plurality of cards after correlating mutually. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a card management system, a card management server, a card management method, and a program, and in particular, a card in which an ID is recorded, a card management server that manages card information of the card, an ID read from the card, and via a network. The present invention relates to a card management system, a card management server, a card management method, and a program having a terminal that communicates with a card management server and updates the card information.

  In recent years, cards that have been converted into gift cards into magnetic cards and can be used like prepaid cards are on the market.

  Since such cards do not require qualification screening and are suitable for small amounts, they can be used with ease that credit cards and bank cards do not, and can be used easily by children and students. it can. For this reason, it is convenient if the parent can deposit and manage the amount of money that can be used by the child so that it can be used by the family.

  Conventionally, a system has been proposed in which a plurality of different types of cards can be mutually used within a predetermined service range (see Patent Document 1).

In the field of bank-type IC cards, in which balances, personal information, and the like are recorded, systems have been proposed that allow payment means for different uses to be used with each other (see Patent Documents 2 and 3).
Japanese Patent Laid-Open No. 11-86098 JP 2000-29965 A JP 2004-206248 A

  However, conventionally, with this type of card, since the balance was deposited and managed for each card, the parent could not manage the balance of the child's card.

  The present invention has been made in view of the above points, and by allowing the balance of a plurality of cards to be handled as the balance of one card, the balance of a child's card can be deposited and managed by the parent card. An object of the present invention is to provide a card management system, a card management server, a card management method, and a program.

  The present invention can update the card information by recording the ID, the card management server for managing the card information including the balance of the card, and reading the ID from the card and communicating with the card management server via the network. And a card management server that can update the balance of a plurality of cards at once by registering the card information of a plurality of cards in association with each other. It is characterized by that.

  The card management server manages a plurality of cards managed in association with each other by distinguishing the main card from other cards, and controls the balance so that the balance can be managed only by the main card. . In addition, the card management server is controlled to be able to deposit only with the main card.

  The card management server provides authentication information for using a pre-registered main card to the terminal when an ID is supplied from the card, and a notification that the authentication information has been confirmed is sent by the terminal. The use of the card is permitted.

  Furthermore, the card management server provides the terminal with pre-registered identity confirmation information when an ID is supplied from the card, and permits the use of the card when a notification that the identity has been confirmed is sent by the terminal. It is characterized by doing.

  The present invention is also a card management server capable of communicating with a terminal via a network and managing card information including a card balance based on an ID read from the card by the terminal. It has a registered database and processing means that can update the balance of a plurality of cards in a batch by registering the card information of a plurality of cards in the database in association with each other. .

  Furthermore, the present invention provides a card management method in which an ID assigned to a card is supplied from a terminal to a card management server via a network, and the card information is updated based on the ID by the card management server. The card information is registered in association with each other, so that the balance of a plurality of cards can be managed collectively.

  Further, the card management program of the present invention searches a database in which card information including a balance of a card is registered in a computer based on an ID assigned to the card, and obtains card information of the card, An update procedure for updating the balances of a plurality of cards at once based on the information is executed.

  According to the present invention, the card management server can be managed by linking the card information of a predetermined card and the card information of another card, and the other card linked to the predetermined card by the predetermined card can be managed. By making the card information updatable, it is possible to refer to the card information of another card from the card information of the predetermined card, thereby making it possible to use another card by the predetermined card, and a plurality of cards Can be handled as the balance of a single card. As a result, the convenience of the card can be improved.

  FIG. 1 shows a system configuration diagram of an embodiment of the present invention.

  The card management system 100 according to the present embodiment mainly includes a card 111, a card reader / writer 112, a store terminal 113, a network 114, a management server 115, and a headquarter terminal 116.

  The card 111 is, for example, a magnetic card, and at least an ID for identifying the card 111 is magnetically recorded. The information recorded on the card 111 is not limited to only the ID, but only the ID is recorded in this embodiment. The card reader / writer 112 can read at least an ID magnetically recorded on the card 111.

  The card reader / writer 112 supplies the ID read from the card 111 to the store terminal 113. The store terminal 113 is configured by a POS terminal or the like, is installed in the store, generates a request for payment based on the ID of the card 111 received from the card reader / writer 112, and sends it to the management server 115 via the network 114. Supply.

  The management server 115 includes a processing device 121 and a database 122. In this embodiment, the management server 115 is configured by the processing device 121 and the database 122. However, the processing device 121 may be the management server, and the processing device 121 may access the database 122 via the network 114. Needless to say, it is good.

  The processing device 121 is configured by a computer system or the like, and a management program is installed. The processing device 121 processes data based on the management program, searches the database 122 based on a request from the store terminal 113, reads out desired card information, performs processing, and determines the database 122 based on the processing result. Update. The management program installed in the processing device 121 can update the balance of a plurality of cards at once by registering the card information of a plurality of cards in association with each other.

  The database 122 includes a hard disk device and the like, and mainly includes a card information database 131 and a parent / child information database 132.

  FIG. 2 shows a data structure diagram of the database 122.

  The card information database 131 includes card identification information (ID) 141, parent / child identification information 142, balance 143, card usage conditions 144, identity confirmation information 145, authentication information 146, and authentication setting information 147.

  The card ID 141 is an identification number for identifying an individual card. The parent / child identification information 142 is identification information for identifying whether the card is a parent card or a child card.

  The balance 143 is a balance that can be used with an individual card.

  The card usage condition 144 is information indicating a card usage condition, and includes, for example, information such as a parent card usage limit 151, a parent card usage limit 152, and a parent card usage 153. In the parent card usage limit 151, an upper limit of the usage amount of the parent card balance by the child card is registered in advance. In the parent card use limit number 152, an upper limit of the use number of the parent card by the child card is registered in advance. In the parent card usage count 153, the usage count of the parent card by the child card is recorded.

  The identity confirmation information 145 is information for confirming the identity of the user when using the card, and the identity confirmation information is not set when the identity confirmation is not performed. The identity verification information is information that can identify the user, such as a license number possessed by the user and the date of birth of the user.

  The authentication information 146 is authentication information for performing authentication when using the parent card, and is set in the parent card. The authentication setting information 147 is information for determining whether or not to perform authentication when using the card. When the authentication setting information 147 is valid, authentication is performed using the authentication information set in the parent card. The authentication information 146 need not be set as the card information of the parent card, and the authentication information of the parent card may be set in the authentication information 146 of the child card. At this time, the authentication information 146 is information that can identify the parent, for example, the date of birth of the parent.

  The processing device 121 is configured to be able to limit the use of a child card based on information registered in the card use condition 144.

  The parent-child information database 132 includes a card ID 161 of a card having a parent-child relationship and parent-child identification information 162.

  A card ID is registered in the card ID 161. In the parent / child identification information 162, information for identifying whether the card of the card ID is a parent card or a child card is registered.

  Next, a schematic operation of the card management system 100 will be described.

  FIG. 3 shows a process flowchart of an embodiment of the present invention.

  First, a process for registering parent-child relationship information in the parent-child information database 132 will be described.

  Registration of the parent-child relationship information is performed by the headquarters terminal 116, for example.

  First, information indicating a parent-child relationship is input to the headquarters terminal 116 by a request from a user or the like. The input information indicating the parent-child relationship is, for example, the card ID of the card that is the parent card, the card ID of the card that is the child card, and the like.

  When the information indicating the parent-child relationship is input, the headquarters terminal 116 transmits the input information to the management server 115 in step S1-1.

  When receiving the input information in step S1-2, the management server 115 creates a parent-child information database 132 based on the input information. In creating the parent-child information database 132, first, the card ID of the parent card included in the input information is registered in the parent-child information database 132, and the parent-child identification information 162 is set to “parent”. Further, the card ID of the child card included in the input information is registered in the parent-child information database 132, and the parent-child identification information 162 is set to “child”.

  When the registration in the parent-child information database 132 is completed, the management server 115 transmits a parent-child information completion notification to the headquarters terminal 116 in step S1-4. Upon receiving the parent-child information registration completion notification in step S1-5, the headquarters terminal 116 displays on the display that the parent-child information registration has been completed. When it is displayed on the display of the headquarters terminal 116 that parent-child information registration has been completed, the user is notified accordingly.

  Next, the operation when using a card for which parent-child information registration has been completed will be described.

  The card is used by the store terminal 113.

  When the usage card 111 is read by the card reader / writer 112, the card reader / writer 112 reads the card ID recorded on the usage card 111 and notifies the store terminal 113. In step S 2-1, the store terminal 113 creates a usage request from the card ID of the usage card 111 and the usage request amount, and transmits it to the management server 115.

  When the management server 115 receives the use request request in step S2-2, in step S2-3, the management server 115 searches the card information database 131 using the card ID included in the use request request as a key, and whether the personal identification information 145 is set. If the identity verification information is set, the identity verification information is notified to the store terminal 113.

  When the store terminal 113 is notified of the identity verification information from the management server 115 in step S2-4, the store terminal 113 displays the identity verification information on the display of the store terminal 113 in step S2-4.

  The store clerk inquires the user about the identity verification information, compares the user's answer with the identity verification information displayed on the display of the store terminal 113, and the user's answer matches the identity verification information displayed on the store terminal 113. If so, the store terminal 113 performs an approval operation on the assumption that the person has been confirmed.

  When an approval operation is performed by the store clerk, the store terminal 113 transmits an approval notification to the management server 115 in step S2-5. When the management server 115 receives the approval notification from the store terminal 113, the management server 115 performs a use condition check process based on the use conditions registered in the card information database 131 in step S2-6.

If the usage conditions are satisfied by the usage condition check process, the management server 115 updates the card information based on the usage amount, usage status (usage amount, number of times) of the parent card, etc. in step S2-7. When the card information is updated based on the usage status, the management server 115 transmits a usage report notification to the store terminal 113 in step S2-8. The usage report notification includes a card ID, usage amount, balance, and the like.

  When the store terminal 113 receives the use report notification from the management server 115 in step S2-9, the store terminal 113 displays the result on the display of the store terminal 113, and prints and outputs it as a receipt.

  Next, the processing of the management server 115 will be described in detail.

  FIG. 4 shows a process flowchart when the management server 115 uses the card.

  When receiving the use request request from the store terminal 113 in step S3-1, the management server 115 searches the card information database 131 by the card ID included in the use request request in step S3-2, and acquires the corresponding card information. .

  The management server 115 refers to the identity verification information 145 of the corresponding card information in step S3-3, determines whether or not the identity verification information 145 is set, and if the identity verification information 145 is set. Then, the personal identification information is notified to the store terminal 113.

  When the management server 115 receives a notification from the store terminal 113 to approve the identity confirmation, the balance included in the card information is compared with the usage request amount in step S3-4, and if the balance is larger than the usage request amount, In step S3-5, the usage request amount is subtracted from the balance, and in step S3-6, the card information database 131 is updated with the subtraction result as the balance.

  In addition, as a result of comparing the balance included in the card information with the usage request amount in step S3-4, if the balance is smaller than the usage request amount, the management server 115 determines the difference between the usage request amount and the balance in step S3-7. Is set to the shortage amount.

  Next, in step S3-8, the management server 115 determines whether the use card is a parent card or a child card based on the parent-child identification information of the card information. When the use card is a child card in step S3-8, the management server 115 executes a parent card information search process in step S3-9.

  Here, the parent card information search process will be described with reference to the drawings.

  FIG. 5 shows a process flowchart of the parent card information search process.

  In step S4-1, the management server 115 searches the parent / child information database 132 using the card ID of the child card as a key, and acquires the card ID of the corresponding parent card in step S4-2.

  In step S4-3, the management server 115 searches the card information database 131 using the acquired parent card ID as a key, and acquires the card information of the parent card in step S4-4.

  Thus, the card information of the child card and the card information of the parent card are acquired. Thus, the parent card information search process is completed.

  Returning to FIG. 4, the description will be continued.

  When the management server 115 acquires the parent card information in step S3-9, the management server 115 executes an authentication process for using the parent card in step S3-10.

  Here, the authentication process will be described with reference to the drawings.

  FIG. 6 shows a flowchart of the authentication process.

  The management server 115 reads the authentication information registered in the card information of the parent card of the usage card in step S5-2 if the authentication setting is valid for the card information of the usage card in step S5-1, and stores Transmit to terminal 113 and wait for approval notification. When the management server 115 receives the approval notification from the store terminal 113 in step S5-3, the management server 115 determines that the use of the card has been approved, and permits the use of the card in step S5-4.

  In addition, when the management server 115 receives the use stop notification from the store terminal 113 in step S5-5, the management server 115 determines that the use of the card has not been approved, and stops using the card in step S5-6.

  Note that if the authentication setting is invalid in step S5-1, the management server 115 permits the use of the card in step S5-4 without performing authentication.

  Thus, the authentication process ends.

  Returning to FIG. 4, the description will be continued.

  If the card is permitted as a result of the authentication process in step S3-10, the management server 115 executes a use condition check process in step S3-11.

  Here, the use condition check process will be described with reference to the drawings.

  FIG. 7 shows a process flowchart of the use condition check process.

  If the usage conditions are set in the card information in step S6-1, the management server 115 determines that there is a condition for using the card, and the card usage status is determined to be the card usage condition 144 in step S6-2. It is determined whether it is within the range of the condition set in. For example, it is determined whether or not the amount of card usage in January has not reached 5,000 yen, and whether or not the number of card usage in January has reached the card usage limit.

  If the use condition is satisfied in step S6-3, the management server 115 permits the use of the card in step S6-4. If the use condition is not satisfied in step S6-3, the management server 115 stops using the card in step S6-5.

  Thus, the use condition check process ends.

  Returning to FIG. 4, the description will be continued.

  If the use of the card is permitted as a result of the use condition check process in step S3-11, the management server 115 compares the balance of the card information of the parent card with the insufficient amount in step S3-12, and the balance is insufficient. If it is more than the amount, the card information database update process is executed in step S3-13.

  Here, the card information database update processing will be described with reference to the drawings.

  FIG. 8 shows a process flowchart of the card information database update process.

  The management server 115 first sets the balance included in the card information of the child card to zero in step S7-1, and updates the card information of the child card in step S7-2.

  Next, the management server 115 subtracts the balance included in the card information of the parent card by the shortage amount in step S7-3, and updates the card information of the parent card in step S7-4.

  Thus, the amount corresponding to the usage amount is subtracted from the balance of the card information of the child card and the corresponding parent card, and the card information database update process is completed.

  Returning to FIG. 4, the description will be continued.

  When the card information database 131 is updated according to the usage request amount, the management server 115 transmits a message to the store terminal 113 in step S3-14.

  Further, the management server 115 determines that the result of the identity verification process in step S3-3 is not approved for the card. If the use card is a parent card in step S3-8, the management server 115 performs the authentication process in step S3-10. As a result, if use of the card is not approved, use conditions cannot be satisfied in step S3-11, or if it is determined in step S3-12 that the parent card is also short of balance, step S3- In step 15, error notification processing is performed.

  The management server 115 transmits an error message obtained as a result of the error notification process to the store terminal 113 in step S3-14.

  Note that the content of the message to be transmitted is selected by searching the message file 133 provided in the database 122 using the message identification information created in the update result, error notification processing, or the like as a key, and the store terminal 113 Sent to.

  In the store terminal, when a message such as a shortage of balance is displayed, the store clerk or the like notifies the user and requests the user to pay in cash or review the purchased product.

  Next, a specific example of the operation when using a card by a child card will be described.

  FIG. 9 is an operation explanatory diagram of one embodiment of the present invention.

  The child of the card ID “00201”, the balance “3,000 yen”, the parent card usage limit “5,000 yen”, the parent card usage limit count “5 times”, and the parent card usage count “3 times” shown in FIG. When a request for use of “4,000 yen” is made using the card B, an insufficient amount of “1,000 yen” occurs in the balance “3,000 yen” of the child card B.

  Therefore, the management server 115 searches the parent-child information database 132 using the card ID “00201” of the child card B as a key as shown in FIG. 2 to obtain the card ID “00101” of the parent card A of the child card B. To do.

  Next, the card information database 131 is searched using the acquired card ID “00101” of the parent card A as a key, and the card information of the parent card A is acquired.

  The management server 115 first sets the balance “3,000 yen” of the child card B to “0 yen”, and further, from the balance “10,000 yen” of the card information of the parent card A, the shortage amount “1,000 yen”. Is deducted. As a result, the balance of the child card B becomes “0 yen” and the balance of the parent card A becomes “9,000 yen”. As a result, the card information database 131 updates the balance of the child card B to “0 yen” and the balance of the parent card A to “9,000 yen” as shown in FIG. The parent card use count 153 of the condition 144 is updated from “3 times” to “4 times”.

  As described above, according to the present embodiment, by setting parent-child information to a plurality of cards, the use of the child card can be managed by the parent card. As a result, uselessness of the child card holder is suppressed.

  Further, in this embodiment, the card only stores a card ID for identifying the card, and no personal information is stored. Therefore, even if the card is lost, Prevent outflow. Further, in this embodiment, the card reader / writer 112 is also inexpensive, and since the system can be realized by using a peripheral device generally mounted in POS or the like, it is easy to introduce and is expected to spread rapidly. .

  In this embodiment, a magnetic card is described as an example of a card. However, an applicable card is not limited to a magnetic card, and may be another card such as an IC card.

  In addition, this invention is not limited to the said Example, It cannot be overemphasized that a various modified example can be considered in the range which does not deviate from the summary of this invention.

It is a system configuration figure of one example of the present invention. It is a data block diagram of the database 122. It is a process flowchart of one Example of this invention. 6 is a processing flowchart when a card is used by the management server 115; It is a process flowchart of a parent card information search process. It is a process flowchart of an authentication process. It is a process flowchart of a use condition check process. It is a processing flowchart of card information DB update processing. It is operation | movement explanatory drawing of one Example of this invention.

Explanation of symbols

100 card management system 111 card, 112 card reader / writer, 113 store terminal 114 network, 115 management server, 116 head office terminal 121 processing device, 122 database 131 card information table, 132 parent-child information database 141 card ID, 142 parent-child identification information, 143 Balance, 144 Card usage conditions 145 Identity verification information, 146 Authentication information, 147 Authentication setting information 151 Parent card usage limit, 152 Parent card usage limit count 153 Parent card usage count 161 Card ID, 162 Parent-child identification information

Claims (7)

The card information can be updated based on the card ID by communicating with the card management server for managing the card information including the balance of the card, the card management server for managing the card information including the balance of the card, and the card management server via the network. A card management system having a terminal,
The card management server can handle the balance of the plurality of cards as a balance of one card by registering the card information of the plurality of cards in association with each other. Card management system. The card management server manages a plurality of cards managed in association with each other by distinguishing the main card from other cards,
2. The card management system according to claim 1, wherein the balance is controlled to be manageable only by the main card. The card management server provides the terminal with authentication information for using the primary card registered in advance when an ID is supplied from the card;
3. The card management system according to claim 2, wherein use of the card is permitted when a notification that the authentication information has been confirmed is sent by the terminal. The card management server provides the terminal with identity verification information for confirming a user of a card to be registered in advance when an ID is supplied from the card,
4. The card management system according to claim 1, wherein use of the card is permitted when a notification that the identity has been confirmed is sent by the terminal. 5. A card management server capable of communicating with a terminal via a network and managing card information including a balance of the card based on an ID given to the card supplied from the terminal;
A database in which the card information is registered;
Processing means capable of handling the balance of the plurality of cards as a balance of one card by registering the card information of the plurality of cards in the database in association with each other. A card management server. A card management method for supplying an ID assigned to a card from a terminal to a card management server via a network, and updating the card information based on the ID by the card management server,
A card management method, wherein the card information of a plurality of cards is registered in association with each other so that the balance of the plurality of cards can be handled as a balance of one card. On the computer,
A search procedure for searching a database in which card information including a balance of the card is registered based on an ID given to the card, and acquiring the card information of the card;
A computer-readable program for executing an update procedure for handling a balance of a plurality of cards as a balance of a single card based on the card information.

Images