JP4834455B2 - Card management system, card management server, card management method, program - Google Patents

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 having a terminal that communicates with a card management server and updates card information, a card management server, a card management method, and a program.

  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.

  Cards that can be handled by such companies are determined by the handling company, and the handling companies are usually limited by stores. For this reason, the user has a plurality of types of cards and uses them according to the store. In addition, when a card that can be used in the same store as the card already possessed is obtained by presenting or the like, it is necessary to carry a plurality of cards as they are. Further, since the handling companies are limited depending on the store, a card given in a store that is not normally used by a person who received the card cannot achieve the purpose as a gift.

  In order to eliminate such inconvenience, a system has been proposed in which 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, since this type of conventional card manages one balance per card, the handling company that received the prepaid amount of the card and the handling company that has jurisdiction over the store where the card was used In the meantime, complicated settlement processing is required.

  In addition, a system in which different types of cards can be used with each other within a predetermined service range is to use multiple types of cards mutually, and once you have multiple types of cards, those cards Could not be combined into one.

  Furthermore, in a system using an IC card, the card and peripheral devices are expensive, and since the balance and personal information are stored in the card, it is generally difficult to spread.

  SUMMARY OF THE INVENTION The present invention has been made in view of the above points, and a card management system and a card management server that allow a plurality of cards to be collected and used as a single card without complicating settlement processing between card handling companies. An object is to provide a card management method and program. Another object of the present invention is to provide a card management system, a card management server, and a card that enable a person who obtains a card by gifting or the like to select a store that uses the card by himself / herself, thereby easily achieving the purpose as a gift. It is to provide a management method and a program.

  The present invention includes a card in which an ID is recorded, a card management server that manages card information of the card, a terminal that reads the ID from the card, communicates with the card management server via a network, and updates the card information. A card management system having a card management server that can manage card information of a predetermined card and card information of another card in association with each other, and is associated with the predetermined card by the predetermined card The card information can be updated.

  At this time, the card information of the predetermined card includes the ID of the other card, and the card management server searches the card information of the other card based on the ID of the other card included in the card information of the predetermined card. Thus, the card information of a predetermined card is associated with the card information of another card. Furthermore, the predetermined card and other cards are different card types that cannot be handled under the same usage conditions.

  The present invention is a card management server that is communicable with a terminal via a network and manages a card based on an ID read from a card in which an ID is recorded by the terminal. A database managed based on the ID, and a processing means for searching the database based on the card ID and updating the card information based on a request from the terminal. There is association information for associating with card information of the card, and the processing means updates card information of another card associated with the predetermined card from the ID of the predetermined card based on the association information.

  The present invention is a card management method for reading a card in which an ID is recorded by a terminal, communicating via a network with a card management server that manages the card information of the card, and updating the card information based on the ID, The card information of a predetermined card and the card information of another card are managed in association with each other, and the card information of another card can be updated by the predetermined card.

  The present invention is a computer-readable program that searches a database that manages card information of a card based on an ID assigned to a predetermined card and obtains card information of the predetermined card And a second search procedure for searching the database based on association information for associating a predetermined card with another card and acquiring the card information of the other card, and the other card information. And an update procedure for updating the computer.

  According to the present invention, the card management server can manage the card information of a predetermined card in association with the card information of another card, and the card of another card associated with the predetermined card by the predetermined card. By making the 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, Can be combined into 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 includes a card 111, a card reader / writer 112, a store terminal 113, a network 114, a management server 115, and a user 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 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. The processing device 121 includes a computer system and the like, processes data based on a management program, searches the database 122 based on a request from the store terminal 113, reads desired card information, and performs processing. At the same time, the database 122 is updated with the processing result.

  The database 122 includes a card management table 131, a card issuing company table 132, a card handling company table 133, a ticket type table 134, and an affiliation table 135.

  FIG. 2 shows a data configuration diagram of the card management table 131.

  The card management table 131 includes a card ID 141, an issuing company ID 142, a ticket type 143, an authentication number 144, a balance 145, an enrollment date 146, an expiration date 147, a valid / invalid flag 148, a consolidated card ID 149, a first handling company limited flag 150, The information includes the handling company ID 151 and the like.

  The card ID 141 is information for identifying individual cards. The issuing company ID 142 is information for identifying the company that issued the card.

  The ticket type 143 is information for identifying different types of cards. Different types of cards are, for example, cards with different handling companies and cards with different product groups to be handled, and are cards that cannot be handled under the same usage conditions. For example, a card that can be handled by one handling company but cannot be handled by another handling company, or a card that can be purchased even if the handling company is the same. The authentication number 144 is information for confirming the identity of the user.

  The balance 145 is information indicating the balance currently deposited. The membership date 146 is information indicating the date and time when the card was first deposited.

  The expiration date 147 is information indicating the expiration date of the card. The valid / invalid flag 148 is a flag for identifying whether the card is valid or invalid.

  The grouped card ID 149 corresponds to the association information and is an ID for identifying another grouped card. In the present embodiment, the card information of other cards can be acquired by the collected card ID 149, and a plurality of cards are set by sequentially setting the IDs of the cards to be collected in the collected card ID 149 of the card information of the plurality of cards to be collected. Card information can be obtained.

  The first handling company limitation flag 150 is a flag for identifying whether a card handling company is determined in advance or whether card usage is limited to a handling company at the time of initial use without being determined in advance. The handling company ID 151 is an ID for identifying the handling company to be used, and the handling company ID to be used is set.

  FIG. 3 shows a data configuration diagram of the card issuing company table 132.

  The card issuing company table 132 is a table for specifying a card issuing company and includes information such as a card issuing company ID 161, a name 162, and a location 163.

  The card issuing company ID 161 is identification information of a company that issues a card. The name 162 is information indicating the name of the card issuing company. The location 163 is information indicating the location of the card issuing company.

  FIG. 4 shows a data configuration diagram of the card handling company table 133.

  The card handling company table 133 is configured to include information such as a card handling company ID 171, a name 172, and a location 173.

  The card handling company ID 171 is an ID for identifying the card handling company. The name 172 is information indicating the name of the card handling company. The location 173 is information indicating the location of the cart handling company.

  FIG. 5 is a data configuration diagram of the ticket type table 134.

  The ticket type table 134 includes information such as a card issuing company ID 181, a ticket type 182, a ticket type name 183, and a card authentication method 184.

  The card issuing company ID 181 is an ID for identifying the card issuing company. The ticket type 182 is identification information for identifying the type of card. The ticket type name 183 is information indicating the name given to the card. The card authentication method 184 is information indicating card authentication, encryption method, or the presence or absence thereof.

  FIG. 6 shows a data configuration diagram of the tie-up table 135.

  The alliance table 135 includes information such as a card issuing company ID 191, a ticket type 192, and a card handling company ID 193.

  The card issuing company ID 191 is an ID for identifying a card issuing company. The ticket type 192 is information indicating the type of card. The card handling company ID 193 is an ID for identifying a card handling company that is affiliated with the card issuing company.

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

  FIG. 7 is a diagram for explaining processing when collecting cards.

  When performing card management, the user issues a card management request to the card management server 115 by operating the user terminal 116 in step S1-1.

  Upon receiving the card management request from the user terminal 116, the card management server 115 requests the user terminal 116 for the management card information in step S1-2.

  In response to the summary card information request from the card management server 115, the user inputs the summary card information, the summary card information, and the like by operating the user terminal 116. In the user terminal 116, when summary card information is input by the user and a transmission instruction operation is performed, the summary card information is transmitted to the card management server 115 in step S1-3.

  When the card management server 115 receives the collecting card information from the user terminal 116 in step S1-4, the card management server 115 executes a card collecting process in step S1-5. When the card collecting process is executed, the ID of the collecting card is given as the association information to the card information of the predetermined card, and the card information of the collecting card can be searched from the predetermined card. This makes it possible to use the original card.

  Next, an operation for collecting cards possessed by the user when purchasing a new card will be described.

  FIG. 8 is a diagram for explaining the operation when the new card and the card possessed by the user are collected.

  When an operation for issuing a new card is performed by a store clerk operation, the store terminal 113 transmits a card issue request to the card management server 115 in step S2-1.

  When the card management server 115 receives a card issuance request from the store terminal 113, the card management server 115 executes a card issuance process in step S2-2 and notifies the store terminal 113 of it. By the card issuing process, the valid / invalid flag 148 of the card information registered in advance corresponding to the new card in the card management table 131 is set to valid.

  When the store terminal 113 receives a notification that a card has been issued from the card management server 115, a new card is issued in step S2-3.

  At this time, when the store clerk asks the store clerk to collect other cards possessed by the user on the newly issued card, the store clerk uses the store terminal 113 to obtain information such as the new card ID and the ID of the other card to be managed. Acquire and perform card collection request operation. The store terminal 113 transmits a card management request to the card management server 115 in response to the card management request operation in step S2-4.

  The card management server 115 collects the cards based on the card collection request from the store terminal 113 and notifies the store terminal 113 of the cards. In the store terminal 113, the new card is issued in a state where the cards possessed by the user are collected in step S2-6 by the card collection notification.

  FIG. 9 shows the relationship of card information when collecting cards.

  FIG. 9 shows the relationship between the corresponding card information when the card B and the card C are collected in the card A. Note that the manner of associating card information is not limited to this embodiment.

  The card A ID is “1001”, the card B ID is “1002”, and the card C ID is “1003”. At this time, the ID “1002” of the card B is set as the consolidated card ID 149 in the card information of the card A, and the ID “1003” of the card C is set as the integrated card ID of the card information of the card B.

  When payment is made from the balance of the card B using the card A, the card B ID is acquired from the collected card ID included in the card information of the card A, the card information of the card B is searched, and the card information of the card B And the payment is made using the balance included in the card information of the card B.

  Further, when payment is made from the balance of the card C using the card A, the ID of the card B is acquired from the collected card ID included in the card information of the card A, and the card information of the card B is acquired from the ID of the card B. Furthermore, the ID of the card C is acquired from the collected card ID included in the card information of the card B, the card information of the card C is acquired from the ID of the card C, and the balance included in the card information of the card C is used. Settlement.

  As described above, the card information can be referred to in a formula that is set by sequentially setting the IDs of the cards B and C as the integrated card IDs set in the card information. Settlement. Further, as is clear from the above description, since the settlement is made to the handling company corresponding to each of the cards A, B, and C, the settlement process between the handling companies does not become complicated.

  Next, the card management processing operation of the card management server 115 will be described.

  FIG. 10 shows a card management process flowchart of the card management server 115.

  When the card management server 115 receives a card management request from the user terminal 116 in step S3-1, the card management server 115 acquires the card ID of the management destination from the card management request in step S3-2, and collects the card management request from the card management request in step S3-3. Get the original card ID.

  Next, the card management server 115 searches the card management table 131 in step S3-4, and acquires the card information of the collection destination card ID.

  In step S3-5, the card management server 115 determines whether or not the card ID 149 already stored is stored in the card information. If the card ID already stored is not stored in step S3-5, the card management server 115 sets the card ID as a card ID in step S3-6. When the management original card ID is set in the card information, the card information table 122 is updated in step S3-7.

  In addition, when the card information summarized card ID 149 has already been stored in step S3-5, the card management server 115 searches for the card information of the summarized card ID in step S3-8 and acquires the card information. Then, returning to step S3-5, the processing is continued until the grouping card ID is set as the card ID of the card information.

  As described above, the grouping destination card and the grouping source card are associated with each other, and the card information of the grouping source card can be acquired from the grouping destination card.

  Next, processing at the time of settlement using a summary card will be described.

  FIG. 11 shows a process flowchart of the settlement process.

  When the card management server 115 receives a settlement request from the store terminal 113 in step S4-1, the card management server 115 acquires store information included in the settlement request in step S4-2.

  Card management server 115 determines a handling company from store information at Step S4-3.

  Next, in step S4-4, the card management server 115 searches the card management table 131 using the card ID included in the settlement request as a key. The card management server 115 determines whether or not the card information corresponding to the card ID exists in the card management database 131 in step S4-5.

  If there is no card information in the card management database 131 in step S4-5, the card management server 115 determines that the card that has received the settlement request is an unregistered card, and sends an NG notification to the store terminal 113 in step S4-6. I do.

  If card information exists in the card management database 131 in step S4-5, the card management server 115 determines whether or not a handling company ID is set in the handling company ID 151 included in the card information in step S4-7. . If an ID is set in the handling company ID 151 in step S4-7, the card management server 115 obtains the handling company ID 151 included in the card information in step S4-8 and the handling company ID determined in step S4-3. It is determined whether or not they match.

  If the handling company IDs match in step S4-8, the card management server 115 performs a settlement process in step S4-9. For example, a process of reducing the usage fee from the balance is executed, and a process of notifying the processing result to the store terminal 113 is executed.

  If no ID is set in the handling company ID 151 in step S4-7, the card management server 115 determines in step S4-10 whether the initial handling company limited flag 150 included in the card information is valid or invalid. To do. When the initial handling company limited flag 150 is valid in step S4-10, the card management server 115 sets the handling company ID determined in step S4-3 to the handling company ID 151 in step S4-11, and the handling company. Set to a card that can only be used. In this case, if it is determined whether or not the handling company IDs match in step S4-8, the handling company IDs always match, so the process always proceeds to step S4-9 to perform settlement processing.

  FIG. 12 is a diagram for explaining the initial handling company setting operation.

  As shown in FIG. 12A, when the initial handling company limited flag of the card information is valid, the card issuing company ID “H01” and the ticket type “02” included in the card information are used as keys. If the card handling company ID “T02” at the first use exists as a card handling company capable of handling the card with the card issuing company ID “H01” and the card type “02”, with reference to the ticket type table 134 shown in FIG. As shown in FIG. 12C, “T02” is set as the handling company ID of the card information. By setting the card information handling company ID, the card information can be used only by the handling company thereafter. Further, following this process, a process of transferring the advance payment amount from the handling company that received the advance payment of the card to the handling company at the first use may be executed. The handling company that has received the advance payment for the card can be identified from the issuing company ID 142 and the ticket type 143 of the card information 131.

  Further, the card management server 115 treats the card as a normal card when the initial handling company limited flag 150 included in the card information is invalid in step S4-10, and the issuing company ID 142 included in the card information in step S4-12. The issuing company information and the ticket type information are acquired from the ticket type 143, respectively, and the ticket type table 134 of the database 122 is searched using the ticket type information and the issuing company information as a key in step S4-13, and the handling company ID is acquired. To do.

  When acquiring the handling company ID in step S4-13, the card management server 115 determines in step S4-8 whether the acquired handling company ID matches the handling company ID acquired in step S4-3. If the handling company IDs match, settlement processing is performed in step S4-9.

  If the handling company does not match in step S4-8, the card management server 115 obtains the ID from the collected card ID 149 in step S4-14, and searches the card information table 131 in step S4-4. Steps S4-5 to S4-14 are repeated. As described above, the payment can be made using the card information of the card that matches the handling company of the store where the payment is requested.

  As described above, according to the present embodiment, a plurality of cards can be combined into one card without complicating the checkout process between the card handling companies. It is possible to use other cards that have been collected.

  In addition, according to the present embodiment, the card information can be associated with the formula to be determined by sequentially setting the IDs of the plurality of cards in the collected card ID 149 of the card information of the plurality of cards to be collected. Thus, a plurality of cards can be collected without increasing the storage capacity of the card information.

  Furthermore, according to the present embodiment, a card that allows the user to select a desired store when the card is used for the first time can be provided, which is suitable as a gift.

  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 the present embodiment, the magnetic card is described as an example of the card. However, the applicable card is not limited to the magnetic card, and may be a card of another reading method.

  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 card management table 131. It is a data block diagram of the card issue company table. It is a data block diagram of the card handling company table 133. It is a data block diagram of the ticket type table. It is a data block diagram of the alliance table 135. FIG. It is a figure for demonstrating the operation | movement at the time of card collection. It is a figure for demonstrating the operation | movement at the time of a management card addition. It is operation | movement explanatory drawing at the time of card collection. 5 is a processing flowchart of the card management server 115. It is a processing flowchart of a payment process. It is a figure for demonstrating first time handling company setting operation | movement.

Explanation of symbols

100 card management system 111 card, 112 card reader / writer, 113 store terminal 114 network, 115 card management server, 116 user terminal 121 processing device, 122 database 131 card information table, 132 card issuing company table 133 card handling company table, 134 tickets Seed table, 135 alliance table

Claims (6)

A card on which an ID is recorded and which can be settled within the range of the balance, a card management server for managing card information of the card, reading the ID from the card, and communicating with the card management server via a network; A card management system having a terminal for updating information,
The card management server
The card ID of the card, the card issuing company ID of the card, the handling company ID of the card, and the collected card ID indicating the card ID of another card associated with the card ID are recorded in association with each other. Store card management table,
The handling company ID of the first card corresponding to the card ID of the first card included in the settlement request is acquired from the card management table, and the determination is made from the handling company ID of the first card and the store information included in the settlement request. If the handling company ID of the selected store matches, the settlement processing by the first card is executed for the settlement request,
When the handling company ID of the first card and the handling company ID of the store do not match, the grouped card ID corresponding to the card ID of the first card is acquired from the card management table, and is the grouped card ID. If the handling company ID of the second card corresponding to the card ID of the second card is acquired and the handling company ID of the second card matches the handling company ID of the store, the second request is received in response to the settlement request. Execute payment processing by card,
A card management system characterized by The card management server
The card management table further records a first handling company limited flag indicating validity or invalidity in association with each other,
When the handling company ID of the first card corresponding to the card ID of the first card included in the payment request cannot be obtained from the card management table, the first handling company limited flag is obtained from the card management table, and the first handling company is obtained. If the limited flag indicates valid, the handling company ID of the store is recorded as the handling company ID of the first card corresponding to the card ID of the first card in the card management table;
Executing a settlement process by a first card for the settlement request;
The card management system according to claim 1. The card management server
If the handling company ID of the second card does not match the handling company ID of the store, the collected card ID corresponding to the card ID of the second card is obtained from the card management table, and is the collected card ID. If the handling company ID of the third card corresponding to the card ID of the third card is acquired and the handling company ID of the third card matches the handling company ID of the store, the third card is accepted in response to the settlement request. Execute payment processing by card,
Card management system according to claim 1 or 2 wherein. A card on which an ID is recorded and which can be settled within the range of the balance, a card management server for managing card information of the card, reading the ID from the card, and communicating with the card management server via a network; A card management server in a card management system having a terminal for updating information,
The card ID of the card, the card issuing company ID of the card, the handling company ID of the card, and the collected card ID indicating the card ID of another card associated with the card ID are recorded in association with each other. Store card management table,
The handling company ID of the first card corresponding to the card ID of the first card included in the settlement request is acquired from the card management table, and the determination is made from the handling company ID of the first card and the store information included in the settlement request. If the handling company ID of the selected store matches, the settlement processing by the first card is executed for the settlement request,
When the handling company ID of the first card and the handling company ID of the store do not match, the grouped card ID corresponding to the card ID of the first card is acquired from the card management table, and is the grouped card ID. If the handling company ID of the second card corresponding to the card ID of the second card is acquired and the handling company ID of the second card matches the handling company ID of the store, the second request is received in response to the settlement request. Execute payment processing by card,
A card management server. A card on which an ID is recorded and which can be settled within the range of the balance, a card management server for managing card information of the card, reading the ID from the card, and communicating with the card management server via a network; A card management method in a card management system having a terminal for updating information,
The card management server
From the card management table, a card ID of the card, a card issuing company ID of the card, a handling company ID of the card, and a collected card ID indicating a card ID of another card associated with the card ID Read out the card management table recorded in association,
The handling company ID of the first card corresponding to the card ID of the first card included in the settlement request is acquired from the card management table, and the determination is made from the handling company ID of the first card and the store information included in the settlement request. If the handling company ID of the selected store matches, the settlement processing by the first card is executed for the settlement request,
When the handling company ID of the first card and the handling company ID of the store do not match, the grouped card ID corresponding to the card ID of the first card is acquired from the card management table, and is the grouped card ID. If the handling company ID of the second card corresponding to the card ID of the second card is acquired and the handling company ID of the second card matches the handling company ID of the store, the second request is received in response to the settlement request. Execute payment processing by card,
Card management method characterized by the above. A card on which an ID is recorded and which can be settled within the range of the balance, a card management server for managing card information of the card, reading the ID from the card, and communicating with the card management server via a network; In a card management system having a terminal for updating information, the card management server, which is a computer,
From the card management table, a card ID of the card, a card issuing company ID of the card, a handling company ID of the card, and a collected card ID indicating a card ID of another card associated with the card ID Read the card management table recorded in association,
The handling company ID of the first card corresponding to the card ID of the first card included in the settlement request is acquired from the card management table, and the determination is made from the handling company ID of the first card and the store information included in the settlement request. If the handling company ID of the selected store matches, the settlement request by the first card is executed for the settlement request,
When the handling company ID of the first card and the handling company ID of the store do not match, the grouped card ID corresponding to the card ID of the first card is acquired from the card management table, and is the grouped card ID. If the handling company ID of the second card corresponding to the card ID of the second card is acquired and the handling company ID of the second card matches the handling company ID of the store, the second request is received in response to the settlement request. A program for executing payment processing by card .

Images