JP4392436B2 - Point management method, card system, and point management apparatus - Google Patents

Description

  The present invention relates to a point management method for managing points given to card members, and in particular, a point management method capable of avoiding concentration of processing that occurs in accordance with card member consumption behavior for a certain period of time, The present invention relates to a card system for carrying out the method and a point management device used in the card system.

  Whether a member who can enjoy a specific service enjoys the service, whether the beneficiary is a member, or whether the member has the necessary requirements to enjoy the service Etc. may be confirmed. For example, in the case of a credit card, when a card member pays with his / her own credit card, the credit card is authorized to check the credit card's limit of use or prevent unauthorized use. ing.

  In the case of such authorization processing, it is necessary to perform in real time when a card member uses a credit card, so that a reduction in response time is required.

  On the other hand, with regard to the purchase pattern of consumers, the use of credit cards tends to be concentrated on weekends and holidays in the middle of the New Year's holiday or evenings such as so-called Golden Week. In this way, even in a specific time zone (peak hours) where credit card usage is concentrated, credit card companies can use the equipment related to authorization processing in accordance with the peak hours so that authorization processing can be performed quickly. We are expanding.

  In addition, it is desirable to perform authorization processing for all card usage, but when authorization is used only when the usage amount exceeds a certain amount (called the floor limit) There is. In this case, during the peak time period described above, a measure may be taken such as reducing the number of authorization processes by temporarily raising the floor limit.

Further, Patent Document 1 notifies the user who has accessed the server when there is a lot of traffic on the communication network that the sales price will be discounted if it is used in another time zone. There has been disclosed a product sales method that can promote the use of a non-concentrated time zone and suppress the use of a traffic-intensive time zone.
JP 2002-318929 A

  However, in today's trend of decreasing sales per credit card use, even if the number of card usage increases, the total profit does not increase so much. It has become.

  Further, when the number of authorization processes is reduced by raising the floor limit, there is a problem that the risk of the credit card company increases.

  Therefore, it is desirable that the authorization process can be performed promptly even during peak hours without taking measures such as adding equipment as described above or raising the floor limit.

  Furthermore, in the case of the merchandise sales method disclosed in Patent Document 1, since the user is notified when the user actually accesses the server, there is a problem that traffic has already occurred at this point. There is. In order to avoid traffic concentration, it is desirable not to generate such extra traffic.

  By the way, the processing that occurs with the closing date of the credit card (for example, monthly billing processing) is naturally concentrated on the closing date, so that processing is performed by taking special measures as in the case of authorization processing. Need to avoid concentration. However, in the case of processing that accompanies such a closing date, it is possible to distribute processing by providing a plurality of closing dates (for example, the closing date of a general member and the closing date of a gold member are different dates).

  On the other hand, in the case of the authorization process, even if the time during which the process is concentrated is known in advance, the process cannot be distributed as described above. This is because the authorization process occurs in response to the card use of the card member. That is, in order to distribute the authorization processing, the card use of the card member must be distributed, but it is extremely difficult for the credit card company to control the timing of the card use.

  The present invention has been made in view of such circumstances, and its purpose is to distribute processing that occurs during card use, such as authorization processing, by avoiding card members' card use from concentrating on a specific period. It is an object of the present invention to provide a point management method that can be performed, a card system for implementing the method, and a point management device used in the card system.

  In order to solve the above-described problems, a point management method according to the present invention includes a storage unit having a predetermined storage area, a notification unit for notifying a card member of a credit card of predetermined information, and a database search. A search means for executing, and a point calculating means for calculating points given for the use of the credit card, executing an authorization process that occurs when the credit card is used by the card member, In a card system configured to construct a database for storing execution history information, a point management method for managing points that can be used by the card member with respect to card use, wherein the execution history information is: Information in which the card usage time is associated with the card member identifier that identifies the card member The storage means stores a calculation rule of points given to the use of the card when the card is used during non-peak hours, and the search means stores the card in the database. By searching the usage time of a card belonging to the peak time zone from the usage times of a plurality of cards in the accumulated execution history information, and referring to the card member identifier associated with the usage time of the searched card A step of identifying a card member who has used the card during peak hours, and a calculation stored in the storage means when the notification means uses the card during the non-peak hours in the future Notifying the specified cardholder of information indicating that the rule is applied; and the search means further includes the calculation rule. Searching for the usage time of a card belonging to a non-peak time zone from the usage times of a plurality of cards in the execution history information indicating the execution history of the authorization process that has occurred after the notification of the information indicating that is applied, The point calculation means has a step of calculating points given for the use of the card related to the searched card use time based on the calculation rule.

In the point management method according to the invention, the database stores member store information in which a member store identifier for identifying a member store of a credit card is associated with a member store type identifier for identifying a type of business of the member store. In the step of storing the calculation rule, the storage means stores the calculation rule determined according to the type of business of a credit card member store, and the execution history information includes the usage time of the card, In the step of identifying the card member, including information associated with a card member identifier and a member store identifier for identifying the member store where the card was used, the search means uses the searched card The member store information stored in the database is searched using the member store identifier associated with the time, and the member store identifier is searched. By referring to the industry merchant identified to identify the cardholder by the merchant industry, in the step of notifying to the cardholder, said notifying means, the card in the non-peak time zone in the future when performing usage it is stored in the storage means, and the information indicating the calculation rule of the industry of the identified merchant is applied, and notifies for the cardholder that the identified You may do it.

In the point management method according to the invention, in the step of storing the calculation rule, the storage means stores the calculation rule determined for each credit card member store, and the execution history information is stored in the card. In the step of specifying the card member, the search means includes the search, including information in which a usage time, the card member identifier, and a member store identifier for identifying a member store that uses the card are associated with each other. In the step of identifying a card member for each member store by referring to the member store identified by the member store identifier associated with the card usage time, and notifying the card member, the notifying means However, when the card is used in the non-peak time zone in the future, it is stored in the storage means and the specified Information indicating the calculation rule is applied according to franchisees, it may be notified for the terminal according to the cardholder that the identified.

The card system of the present invention includes a card payment system that executes an authorization process that occurs when a credit card is used by a credit card member, and a database that stores execution history information indicating an execution history of the authorization process. A card system comprising a point management device for managing points that can be used by the card member with respect to card use, wherein the execution history information includes a card use time and a card member identifier for identifying the card member. Storage means for storing a calculation rule of points given to the use of the card when the card is used in a non-peak time period. And the use of multiple cards in the execution history information stored in the database Find the utilization time of the card belonging to the peak hours from the time, by referencing the cardholder identifier associated with usage time retrieved card, sometimes using a card during peak hours specifying means for specifying a cardholder, information indicating that calculation rule stored in the storage means is applied to a case where the use of cards in the non-peak hours in the future, the identified card A non-peak time period from a plurality of card usage times in the execution history information indicating the execution history of the authorization process that occurred after the notification means for notifying the member and the information indicating that the calculation rule is applied A search means for searching for a card usage time belonging to the card, and a poi that is given for the card usage related to the card usage time searched by the search means The door, and a point calculation means for calculating, based on the calculated rule.

The point management device according to the present invention is provided in association with a card payment system that executes an authorization process that occurs when a credit card is used by a credit card member, and an execution history that indicates an execution history of the authorization process A point management device comprising a database for storing information, wherein the card member manages points that can be used for card use, wherein the execution history information includes a card use time and a card member identifier for identifying the card member Storage means for storing a calculation rule of points given for the use of the card when the card is used during non-peak hours, and the database The usage history of multiple cards in the execution history information stored in the Find the card usage time that, by referring to the cardholder identifier associated with utilization time of the retrieved card, specifying means for specifying a cardholder who have utilized card during peak hours Notification means for notifying the specified card member of information indicating that the calculation rule stored in the storage means is applied when the card is used in the non-peak time period in the future. And the usage time of the card belonging to the non-peak time zone from the usage time of the plurality of cards in the execution history information indicating the execution history of the authorization process that has occurred after the notification of the information indicating that the calculation rule is applied. Based on the calculation rule, the points given to the use of the card related to the use time of the card searched by the search means Calculating Te and a point calculation unit.

In the point management device according to the invention, the database stores member store information in which a member store identifier for identifying a member store of a credit card is associated with a member store type identifier for identifying a type of business of the member store. The storage means stores the calculation rules determined according to the type of business of the credit card member store, and the execution history information includes the usage time of the card, the card member identifier, and the usage of the card. Information that is associated with an affiliated store identifier that identifies the affiliated merchant, and the specifying means stores in the database using the affiliated store identifier that is associated with the searched card usage time. Card associations for each member store's industry by searching the member store information obtained and referring to the member store's industry identified by the member store identifier. Is configured to so as to identify, the notification means is stored in said storage means in the case of use of the card in the non-peak hours in the future, and, according to the industry of the identified merchant information indicating the calculation rule is applied, it may be configured to notify for the cardholder that the identified.

In the point management device according to the invention, the storage means stores the calculation rule determined for each credit card member store, and the execution history information includes the usage time of the card, and the card member identifier. And a member store identifier for identifying a member store where the card was used, and the specifying means is identified by the member store identifier associated with the searched card use time. By referring to the affiliated store, the card member is specified by the affiliated store, and the notification means is stored in the storage means when the card is used in the non-peak time period in the future. and has, and, configuration information indicating the calculation rule according to the identified merchant is applied, to notify for the cardholder that the identified It may be.

  The point management method of the present invention, the card system for implementing the method, and the point management device used in the card system can decentralize the processing that occurs when a member enjoys the service.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram showing the configuration of the card system of the present invention. In FIG. 1, the code | symbol 10 has shown the card system for performing the process regarding utilization of a credit card. The card system 10 includes a card payment system 3 for executing processing relating to credit card payment, and a point management device 1 for managing points available to the card member for use of the credit card.

  The card payment system 3 is installed in a member store of a credit card company, and is communicably connected to member store side terminal devices 4, 4... That generate data necessary for the payment processing of sales by using a credit card. . The member store side terminal devices 4, 4... Are configured to transmit the generated data to the card settlement system 3 at an appropriate timing.

  Further, the point management device 1 is communicably connected to the member side terminal devices 2, 2... Used by card members via a communication network 100 such as the Internet. The member-side terminal devices 2, 2... May be terminal devices that can communicate with the point management device 1 via the communication network 100. Therefore, for example, a personal computer, a PDA (Personal Digital Assistant), a mobile phone, and the like are used as the member side terminal devices 2, 2,. Here, communication between the point management device 1 and the member side terminal devices 2, 2,... Is performed using a communication protocol such as HTTP (HyperText Transfer Protocol).

  FIG. 2 is a block diagram showing a configuration of the point management device 1 provided in the card system 10 of the present invention. As shown in FIG. 2, the point management apparatus 1 includes a CPU 11, and the CPU 11 is connected to each hardware described later via a bus. Then, the CPU 11 controls the operation of the hardware and executes a computer program loaded into the memory 12. As a result, the point management device 1 can execute processing to be described later.

  The memory 12 is composed of, for example, a DRAM or an SRAM, and stores temporary data generated when the computer program is executed.

  The display unit 13 is composed of a CRT, a liquid crystal display, or the like, and displays a processing result or the like by the CPU 11. The input unit 14 includes a keyboard and a mouse, and is used when an operator gives an instruction to the point management device 1.

  The communication interface (I / F) 15 is an interface for communicating with the card settlement system 3 and the member side terminal devices 2, 2.

  The hard disk 16 is configured by a readable / writable magnetic disk or the like, and stores a computer program and an OS (operating system) necessary for the operation of the point management apparatus 1 and various data. The hard disk 16 is provided with a plurality of databases (DB). Details of these databases will be described below.

[Authorized DB]
The authorization case DB 1601 stores authorization case information related to the authorization process that occurs when a credit card is used. This authorization-specific information is generated based on data transmitted from the member store side terminal device 4.

  FIG. 3 is a conceptual diagram showing an example of the format of authorization case information stored in the authorization case DB 1601. As shown in FIG. 3, the authorization-specific information includes fields such as a date field 101, a member ID field 102, a usage amount field 103, a usage time field 104, and a usage member store code field 105. Hereinafter, information stored in each of these fields will be described.

  The date field 101 stores the credit card usage date, the member ID field 102 stores the member ID for identifying the card member, and the usage amount field 103 stores the usage amount of the credit card. The usage time field 104 stores the usage time when the credit card is used, and the usage member store code field 105 stores the member store code for identifying the member store where the credit card is used.

[Member information DB]
The member store information DB 1602 stores member store information related to credit card member stores.

  FIG. 4 is a conceptual diagram showing an example of the format of member store information stored in the member store information DB 1602. As shown in FIG. 4, the member store information includes fields such as a member store code field 111, a member store name field 112, a business type code field 113, and a region code field 114. Hereinafter, information stored in each of these fields will be described.

  The member store code field 111 identifies the member store code for identifying the member store, the member store name field 112 displays the name of the member store, and the industry code field 113 identifies the industry to which the member store belongs. The industry code and the area code field 114 each store an area code for identifying the area where the member store is located.

[Weather Information DB]
The weather information DB 1603 stores weather information related to the weather. FIG. 5 is a conceptual diagram illustrating an example of a format of weather information stored in the weather information DB 1603. As shown in FIG. 5, the weather information has fields such as a date field 121, a region code field 122, and a weather code field 123. Here, the date field 121 stores a date, the region code field 122 stores a region code for identifying the region, and the weather code field 123 stores a weather code for identifying the weather of the region on the date. Has been.

  The weather code field 123 of the weather information relating to the future date stores a weather code for identifying the weather announced in the weather forecast.

[First usage information DB]
The first usage number information DB 1604 stores first usage number information indicating the number of credit card usages by day / weather.

  FIG. 6 is a conceptual diagram illustrating an example of a format of first usage number information stored in the first usage number information DB 1604. As illustrated in FIG. 6, the first usage number information includes fields such as a date field 201, a current day weather code field 202, a previous day weather code field 203, a number field 204, and a ratio field 205. Here, the date field 201 indicates the credit card usage date, and the current day weather code field 202 indicates the current day weather code for identifying the usage day weather in the area where the member store where the credit card was used is located. Similarly, the previous day weather code field 203 stores the previous day weather code for identifying the weather the day before use. Further, the number field 204 stores the number of credit cards used, and the ratio field 205 stores the ratio of the number shown in the number field 204 to the total number of credit card uses.

[Second Usage Number Information DB]
The second usage number information DB 1605 stores second usage number information indicating the number of credit card usages by day and time zone.

  FIG. 7 is a conceptual diagram illustrating an example of a format of second usage number information stored in the second usage number information DB 1605. As shown in FIG. 7, the second usage number information includes fields such as a date field 211, a time zone (own) field 212, a time zone (to) field 213, a number field 214, and a ratio field 215. Yes. Here, the date of use of the credit card is displayed in the date field 211, the time that is the beginning of the time zone to which the credit card usage time belongs is stored in the time zone (own) field 212, and the time zone (to) field 213 is Each time that is the end of the time zone is stored. Also, the number field 214 stores the number of credit cards used, and the ratio field 215 stores the ratio of the number shown in the number field 214 to the total number of credit card uses.

[Third Usage Number Information DB]
The third usage number information DB 1606 stores third usage number information indicating the number of credit card usages by member store business type and time zone.

  FIG. 8 is a conceptual diagram illustrating an example of a format of third usage number information stored in the third usage number information DB 1606. As shown in FIG. 8, the third usage number information includes an industry code field 221, an industry field 222, a time zone (own) field 223, a time zone (to) field 224, a number field 225, a ratio field 226, and the like. Has a field. Here, the industry code field 221 stores an industry code for identifying the industry to which the member store belongs, and the industry field 222 stores the industry. Also, the time zone (own) field 223 stores the time that is the beginning of the time zone to which the credit card usage time belongs, and the time zone (to) field 224 stores the time that is the end of the time zone. . Further, the number field 225 stores the number of credit cards used, and the ratio field 226 stores the ratio of the number of credit cards used to the total number of credit cards used.

[Fourth usage information DB]
The fourth usage number information DB 1607 stores fourth usage number information indicating the number of credit card usages by member store / time zone.

  FIG. 9 is a conceptual diagram illustrating an example of a format of fourth usage number information stored in the fourth usage number information DB 1607. As shown in FIG. 9, the fourth usage number information includes a member store code field 231, a member store name field 232, a time zone (own) field 233, a time zone (to) field 234, a number field 235, and a ratio field 236. Etc. each field. Here, the member store code field 231 stores a member store code for identifying the member store, and the member store name field 232 stores the name of the member store. Also, the time zone (own) field 233 stores the time that is the beginning of the time zone to which the credit card usage time belongs, and the time zone (to) field 234 stores the time that is the end of the time zone. . Furthermore, the number field 235 stores the number of credit cards used, and the ratio field 236 stores the ratio of the number shown in the number field 235 to the total number of credit card uses.

  It should be noted that the time zone to which the credit card usage time belongs is determined in advance by the credit card company.

[First addition point rule DB]
The first addition point rule DB 1608 stores first addition point rule information indicating a calculation rule of points to be applied according to member store business types and time zones.

  FIG. 10 is a conceptual diagram showing an example of a format of first addition point rule information stored in the first addition point rule DB 1608. As shown in FIG. 10, the first addition point rule information includes the industry code field 301, the industry field 302, the date field 303, the time zone (self) field 304, the time zone (to) field 305, the addition point field 306, and the like. Each field. Here, the industry code for identifying the industry of the member store is applied to the industry code field 301, the industry identified by the industry code is applied to the industry field 302, and the first addition point rule is applied to the date field 303. Each date is stored. In addition, the time zone (own) field 304 includes a time that is the beginning of the time zone to which the first addition point rule is applied, and the time zone (to) field 305 includes a time that is the end of the time zone. 306 stores the ratio of the added points to the points given in the normal case.

[Second addition point rule DB]
The second addition point rule DB 1609 stores second addition point rule information indicating a point calculation rule applied for each member store / time zone.

  FIG. 11 is a conceptual diagram showing an example of a format of second addition point rule information stored in the second addition point rule DB 1609. As shown in FIG. 11, the second addition point rule information includes a member store code field 311, a member store name field 312, a date field 313, a time zone (own) field 314, a time zone (to) field 315, and an addition point. Each field such as a field 316 is included. Here, the member store code for identifying the member store is stored in the member store code field 311, the name of the member store identified by the member store code is stored in the member store name field 312, and the second in the date field 313. Each date to which the addition point rule is applied is stored. In addition, the time zone (self) field 314 has a time that is the beginning of the time zone to which the second addition point rule is applied, and the time zone (to) field 315 has a time that is the end of the time zone. 316 stores the ratio of the added points to the points given in the normal case.

[Third addition point rule DB]
The third addition point rule DB 1610 stores third addition point rule information indicating a calculation rule for points to be applied based on the weather of the next day.

  FIG. 12 is a conceptual diagram illustrating an example of a format of third addition point rule information stored in the third addition point rule DB 1610. As shown in FIG. 12, the third addition point rule information includes fields such as a current day field 321, a next day weather field 322, and an addition point field 323. Here, the day of the day of the credit card usage date is assigned to the current day field 321, the weather related to the weather forecast for the next day of the usage day is given to the next day weather field 322, and the addition point field 316 is given in a normal case. The ratio of the added points to the points is stored.

[Fourth addition point rule DB]
4th addition point rule DB1611 memorize | stores the 4th addition point rule information which shows the calculation rule of the point applied based on the weather of the previous day.

  FIG. 13 is a conceptual diagram showing an example of a format of fourth addition point rule information stored in the fourth addition point rule DB 1611. As shown in FIG. 13, the fourth addition point rule information includes fields such as a previous day field 331, a previous day weather field 332, a time zone (self) field 333, a time zone (to) field 334, and an addition point field 335. Have. Here, the day before the credit card usage date is stored in the previous day field 331, and the day before weather is stored in the previous day weather field 332, respectively. In addition, the time zone (own) field 333 has a time that is the beginning of the time zone to which the fourth addition point rule is applied, and the time zone (to) field 334 has a time that is the end of the time zone. 335 stores the ratio of the added points to the points given in the normal case.

[Fifth addition point rule DB]
The fifth addition point rule DB 1612 stores fifth addition point rule information indicating a point calculation rule applied for each day and time zone.

  FIG. 14 is a conceptual diagram showing an example of a format of fifth addition point rule information stored in the fifth addition point rule DB 1612. As shown in FIG. 14, the fifth addition point rule information includes fields such as a date field 341, a time zone (self) field 342, a time zone (to) field 343, and an addition point field 344. Here, the date field 341 stores the date to which the fifth addition point rule is applied. The time zone (own) field 342 includes a time that is the beginning of the time zone to which the fifth addition point rule is applied, and the time zone (to) field 343 includes a time that is the end of the time zone. 344 stores the ratio of the added points to the points given in the normal case.

[Addition point rule application result DB]
The addition point rule application result DB 1613 stores application result information regarding whether or not to apply an addition point rule.

  FIG. 15 is a conceptual diagram illustrating an example of a format of application result information stored in the addition point rule application result DB 1613. As shown in FIG. 15, the application result information includes fields such as a member ID field 401, a target month / day field 402, an addition point rule field 403, and an application field 404. Here, the member ID field 401 has a member ID for identifying a card member, the target month / day field 402 has a usage date of a credit card to which the addition point rule is applied, and the addition point rule field 403 has a usage date. The addition point rule to be applied is stored in the application field 404 as to whether or not to apply the addition point rule.

[Member / Monthly Point Total DB]
The member / monthly point total DB 1614 stores point total information regarding points obtained as a result of applying the addition point rule.

  FIG. 16 is a conceptual diagram showing an example of a format of point totaling information stored in the member / monthly point totaling DB 1614. As shown in FIG. 16, the point total information includes fields such as a member ID field 411, a target month / day field 412, a normal point field 413, and an addition point field 414. Here, a member ID for identifying a card member is stored in the member ID field 411, a use date of the credit card to which the addition point rule is applied is displayed in the target month / day field 412, and an additional point is stored in the normal point field 413. In the normal case where the rule is not applied, a normal point given to the card member is stored, and in the addition point field 414, an addition point obtained as a result of applying the addition point rule is stored.

[Utilization DB]
The use record DB 1615 stores use record information related to the use of credit cards by card members.

  FIG. 17 is a conceptual diagram illustrating an example of a format of usage record information stored in the usage record DB 1615. As shown in FIG. 17, the usage record information includes fields such as a member ID field 421, a usage date field 422, a member store code field 423, a usage amount field 424, and a usage time field 425. Here, the member ID field 421 shows a member ID for identifying a card member, the use date field 422 shows the use date of the credit card by the card member, and the member store code field 423 uses the credit card. Each member store code for identifying the store is stored. The usage amount field 424 stores the usage amount by credit card, and the usage time field 425 stores the time when the credit card is used.

[Target Member DB]
The target member DB 1616 stores target member information related to card members to which the addition point rule is applied. Here, the target member information includes at least a member ID for identifying a card member and information for identifying an addition point rule applied to the card member.

  Next, the operation of the card system 10 of the present embodiment configured as described above will be described with reference to a flowchart. The functions of the card system 10 are mainly divided into the following four.

(1) Utilization record aggregation (2) Utilization record analysis and setting of addition point rule (3) Application and notification of addition point rule (4) Point aggregation Hereinafter, each of these four functions will be described.

[(1) Total usage results]
The point management device 1 generates first usage number information, second usage number information, third usage number information, and fourth usage number information as follows.

[Generation of first usage information]
FIG. 18 is a flowchart showing an operation flow of the point management apparatus 1 of the present invention when generating the first usage number information.

  First, the point management device 1 extracts the authorization case-specific information related to the year (for example, December 2003) input by the operator using the input unit 14 from the authorization case DB 1601 (S101). Specifically, the date stored in the date field 101 is referred to, and the authority-specific information corresponding to the year and month input by the operator is extracted from the authority-specific DB 1601.

  Next, the point management device 1 searches the member store information DB 1602 using the extracted member store code of the authorization case-specific information as a key, and thereby the region of the member store where the card is used according to the authority case-specific information. A code is acquired (S102). Then, the point management device 1 searches the weather information DB 1603 using the acquired region code and date as a key, so that the current day and the previous day of the region where the member store where the card use related to the authorization case-specific information is located is located. The weather code is acquired (S103).

  Next, the point management device 1 searches the authority-specific information extracted in step S101 using the date, the current day's weather code, and the previous day's weather code as keys, and totals the number of the searched items. The number of authorization-specific information by day / weather (the weather of the current day and the previous day) is acquired (S104). Then, based on the number of cases acquired in step S104, the point management device 1 generates first usage number information indicating the number of credit card usages by day / weather (the weather on the current day and the previous day) (S105). .

  The first usage number information generated in this way is stored in the first usage number information DB 1604 by the point management apparatus 1.

[Generation of second usage number information]
FIG. 19 is a flowchart showing an operation flow of the point management apparatus 1 of the present invention when the second usage number information is generated.

  First, the point management device 1 extracts authorization-specific information related to a specific date from the authorization-specific DB 1601 in the same manner as the generation of the first usage number information (S111).

  Next, the point management device 1 searches the authorization case-specific information extracted in step S111 using a predetermined time zone as a key, and counts the number of the searched times to obtain a date / time zone-specific information. The number of authorization-specific information is acquired (S112). And based on the number acquired in step S112, the point management apparatus 1 produces | generates the 2nd usage number information which shows the usage number of the credit card according to a day and time slot | zone (S113).

  Note that the second usage number information generated in this way is stored in the second usage number information DB 1605 by the point management device 1.

[Generation of third usage number information]
FIG. 20 is a flowchart showing an operation flow of the point management apparatus 1 of the present invention when the third usage number information is generated.

  First, the point management device 1 extracts authorization-specific information related to a specific date from the authorization-specific DB 1601 in the same manner as the generation of the first usage number information (S121).

  Next, the point management apparatus 1 searches the member store information DB 1602 using the extracted member store code of the authorization case-specific information as a key, and thereby uses the type of the member store in which the card relating to the authority case-specific information is used. A code is acquired (S122). Then, the point management device 1 searches the authority-specific information extracted in step S121 using the acquired industry code and a predetermined time zone as a key, and totals the number of searches, -The number of authorization-specific information by time zone is acquired (S123). Next, based on the number of cases acquired in step S123, the point management device 1 generates third usage number information indicating the number of credit card usages for each type of business and time (S124).

  The third usage number information generated in this way is stored in the third usage number information DB 1606 by the point management device 1.

[Generation of fourth usage number information]
FIG. 21 is a flowchart showing an operation flow of the point management apparatus 1 of the present invention when the fourth usage number information is generated.

  First, the point management apparatus 1 extracts authorization-specific information relating to a specific date from the authorization-specific DB 1601 in the same manner as the generation of the first usage number information (S131).

  Next, the point management device 1 searches the member store information DB 1602 using the member store code of the extracted authorization case-specific information as a key, thereby joining the member store that has used the card related to the authority case-specific information. A store code is acquired (S132).

  Next, the point management device 1 searches the authority-specific information extracted in step S131 using the acquired member store code and a predetermined time zone as keys, and counts the number of the searches. The number of authorization-specific information by member store / time zone is acquired (S133). Then, based on the number of cases acquired in step S133, the point management device 1 generates fourth usage number information indicating the number of credit card usages by member store / time zone (S134).

  The fourth usage number information generated in this way is stored in the fourth usage number information DB 1607 by the point management device 1.

  As described above, by generating the first usage number information, the second usage number information, the third usage number information, and the fourth usage number information, the totaling of usage results is completed. Based on the total results of the usage results, the following usage results are analyzed and addition point rules are set.

[(2) Analysis of usage results and setting of additional point rules]
The person in charge of the credit card company (hereinafter simply referred to as the person in charge) performs the first addition point rule information, the second addition point rule information, the third addition point rule information, the fourth addition point rule information, and 5th addition point rule information is produced. Then, each added point rule information set in this way is input to the point management device 1 via the input unit 14.

[Creation of first addition point rule information]
As described above, the first addition point rule information indicates a rule for calculating points applied according to member store business types and time zones.

  The person in charge instructs the point management device 1 to display the content of the third usage number information stored in the third usage number information DB 1606 on the display unit 13. Then, the person in charge refers to the content of the third usage number information displayed on the display unit 13 and grasps the tendency of the usage status by member store business type and time zone. As a result, for example, “Saturday department stores have a large number of usages in the evening hours, while there are few usages in the morning hours, so set a high point grant rate for use in the morning hours.” , “In restaurants, the number of uses is concentrated during mealtimes, so set a higher point grant rate for use during other times.” “After work hours at weekday gas stations The person in charge defines a policy such as “Because of the large number of use cases, set a high point grant rate for use in the time zone before attendance”.

  Next, the person in charge creates the first addition point rule information in the format described with reference to FIG. 10 based on the policy determined as described above, and the created first addition point rule information is created. , Input to the point management device 1 using the input unit 14.

  The point management device 1 registers the input first addition point rule information in the first addition point rule DB 1608.

[Creation of second addition point rule information]
As described above, the second addition point rule information indicates a rule for calculating points applied for each member store / time zone.

  The person in charge instructs the point management device 1 to display the content of the fourth usage number information stored in the fourth usage number information DB 1607 on the display unit 13. Then, the person in charge refers to the content of the fourth usage number information displayed on the display unit 13 and grasps the tendency of the usage status by member store / time zone. As a result, for example, “Saturday XX department stores have a large number of usages in the evening hours, while there are few usages in the morning hours. "In the XX store, the number of usages during the time period before meals is large, while the number of usages during the time period after meals is small, so the point grant rate for use during the time period after meals is set high." The person in charge determines the policy.

  Next, the person in charge creates the second addition point rule information in the format described with reference to FIG. 11 based on the policy defined as described above, and the created second addition point rule information is created. , Input to the point management device 1 using the input unit 14.

  The point management device 1 registers the input second addition point rule information in the second addition point rule DB 1609.

[Creation of third addition point rule information]
The 3rd addition point rule shows the calculation rule of the point applied based on the weather of the next day as mentioned above.

  The person in charge experienced, for example, a policy such as `` If the weather forecast on the next Sunday is clear, the number of use on that Sunday will increase, so the point grant rate for Saturday use on that day will be set high ''. Determine by law.

  Next, the person in charge creates the third addition point rule information in the format described with reference to FIG. 12 based on the policy determined as described above, and sets the created third addition point rule information. , Input to the point management device 1 using the input unit 14.

  The point management device 1 registers the input third addition point rule information in the third addition point rule DB 1610.

  In the present embodiment, the person in charge generates the third addition point rule information based on an empirical rule. However, for example, the point management device 1 may calculate the number of usages according to the weather of the current day and the weather of the next day. The information to show may be produced | generated and a person in charge may make it produce 3rd addition point rule information based on the information.

[Creation of fourth addition point rule information]
As described above, the fourth addition point rule information indicates a calculation rule for points applied based on the weather of the previous day.

  The person in charge instructs the point management device 1 to display the content of the first usage number information stored in the first usage number information DB 1604 on the display unit 13. Then, the person in charge refers to the content of the first usage number information displayed on the display unit 13 and grasps the tendency of the usage status according to the weather on the previous day. As a result, for example, “If the previous day is a Saturday, and that Saturday is raining, the number of use in the afternoon of the next Sunday will increase, so the point grant rate for the use in the morning hours of that Sunday The person in charge determines a policy such as “set it high”.

  Next, the person in charge creates the fourth addition point rule information in the format described with reference to FIG. 13 based on the policy determined as described above, and the created fourth addition point rule information is created. , Input to the point management device 1 using the input unit 14.

  The point management device 1 registers the input fourth addition point rule information in the fourth addition point rule DB 1611.

[Creation of fifth addition point rule information]
As described above, the fifth addition point rule information indicates a rule for calculating points applied for each day / time zone.

  The person in charge instructs the point management device 1 to display the content of the second usage number information stored in the second usage number information DB 1605 on the display unit 13. Then, the person in charge refers to the content of the second usage number information displayed on the display unit 13 and grasps the tendency of the usage situation for each time zone. As a result, the person in charge has a policy such as, for example, “The number of usage in the evening time zone is large, while the number of usage in the morning time zone is small, so the point grant rate for morning time zone usage is set high.” Determined.

  Next, the person in charge creates the fifth addition point rule information in the format described with reference to FIG. 14 based on the policy determined as described above, and the created fifth addition point rule information is created. , Input to the point management device 1 using the input unit 14.

  The point management device 1 registers the input fifth addition point rule information in the fifth addition point rule DB 1612.

[(3) Application and notification of addition point rule]
As described below, the point management device 1 identifies a card member to which the addition point rule is applied and notifies that the addition point rule is applied.

  The following processing is set to be executed every morning by the point management apparatus 1.

[Identification of cardholders to whom the additional points rule applies]
FIG. 22 is a flowchart showing the flow of the operation of the point management apparatus 1 of the present invention in the case of specifying the card member to which the addition point rule is applied.

  First, the point management device 1 extracts authorization case-specific information related to a peak time zone (a time zone with a large number of usages) input by an operator using the input unit 14 from the authorization case DB 1601 (S201). And the point management apparatus 1 selects a specific thing among the extracted authorization classification | category information as a process target (S202).

  Next, the point management device 1 searches the member store information DB 1602 using the member store code of the authorization case-specific information selected in step S202 as a key, so that the card relating to the authorization case-specific information is used. The business type code of the store is acquired (S203). Then, the point management apparatus 1 searches the first addition point rule DB 1608 using the acquired business type code as a key (S204), and determines whether the search is successful (S205). Here, when it is determined that the search is successful because the first addition point rule information including the industry code exists (YES in S205), the point management device 1 uses the card related to the authorization case-specific information. The target member information of the card member who performed is generated, and the target member information is registered in the target member DB 1616 (S206). As described above, the target member information includes a member ID for identifying a card member and information for identifying an addition point rule applied to the card member. The point management apparatus 1 generates target member information using the member ID of the authorization case-specific information selected in step S202 and information indicating the first addition point rule.

  On the other hand, if it is determined in step S205 that the search has failed because the first addition point rule information including the industry code does not exist (NO in S205), the point management device 1 does not execute step S206. The process proceeds to the next step S207.

  Next, the point management device 1 searches the second addition point rule DB 1609 using the member store code of the authorization case-specific information selected in step S202 as a key (S207), and determines whether or not the search has succeeded (S207). S208). Here, when it is determined that the search is successful because the second addition point rule information including the member store code exists (YES in S208), the point management device 1 uses the card related to the authorization case-specific information. The target member information of the card member who performed is generated, and the target member information is registered in the target member DB 1616 (S209). In this case, the point management device 1 generates the target member information using the member ID of the authorization case-specific information selected in step S202 and information indicating the second addition point rule.

  On the other hand, if it is determined in step S208 that the search has failed because there is no second addition point rule information including the member store code (NO in S208), the point management device 1 executes step S209. Instead, the process proceeds to the next step S210.

  Next, the point management apparatus 1 determines whether all of the authorization case-specific information extracted in step S201 has been selected as a processing target (S210). Here, when it is determined that there is authorization-specific information that is not selected as a processing target (NO in S210), the point management device 1 returns to step S202 and selects new authorization-specific information as a processing target. . On the other hand, when it is determined that all the authorization case-specific information has been selected (YES in S210), the point management device 1 ends the process.

[Notification of addition point rule being applied]
FIG. 23 is a flowchart showing a flow of operations of the point management apparatus 1 of the present invention in a case where notification that the addition point rule is applied is performed.

  The point management apparatus 1 extracts all target member information from the target member DB 1616 in which the target member information is accumulated as described above (S301). Then, the point management device 1 determines the first addition point rule and the second addition according to the card member / target month (the use date of the credit card to which the addition point rule is applied) based on the extracted target member information. It is determined whether or not the point rule is applied (S302). Based on the determination result, the point management apparatus 1 generates application result information in the format described with reference to FIG. 15, and registers the generated application result information in the addition point rule application result DB 1613 (S303).

  Next, the point management apparatus 1 extracts authorization case-specific information related to the peak time zone (a time zone with a large number of usages) input by the operator using the input unit 14 from the authorization case-specific DB 1601 (S304). And the point management apparatus 1 produces | generates application result information so that a 5th addition point rule may be applied with respect to the member identified by the member ID of the extracted authorization classification | category information, The produced application result information Is registered in the addition point rule application result DB 1613 (S305).

  Next, the point management apparatus 1 acquires the weather of the previous day and the current day and the weather (weather forecast) of the next day from the weather information DB 1603 (S306). As a result, it is determined whether or not the third addition point rule and the fourth addition point rule are applied (S307). If it is determined that it is applicable here, the third addition point rule and / or the fourth addition point rule is applied to the member identified by the member ID of the authorization-specific information extracted in step S304. If the application result information is generated, and if it is determined that the application is not possible, the application result information is generated so that the third addition point rule and the fourth addition point rule are not applied to the member. Application result information is registered in the addition point rule application result DB 1613 (S308).

  And the point management apparatus 1 can receive application of which addition point rule with respect to the card member identified by the member ID shown by the application result information memorize | stored in addition point rule application result DB1613. An e-mail with content indicating whether (or not) is sent (S309). In step S309, an e-mail is transmitted to the e-mail address declared by the card member at the time of credit card member registration.

  Referring to the application result information shown in FIG. 15, it can be seen that whether or not each addition point rule is applied is shown for each member ID and target month and day. In the example shown in FIG. 15, for example, for the card member whose member ID is “4980-0000-001”, the first, second, and third are used for the card use on Saturday, December 4, 2004. The fifth addition point rule is applied, and the first, second, fourth and fifth addition point rules are applied to the card use on December 5, 2004 (Sunday). Further, for a card member whose member ID is “4980-0000-002”, since the card member has not used the card at the member store related to the second addition point rule information, December 4, 2004 The second addition point rule will not be applied to card use on Sunday (Saturday) and December 5, 2004 (Sunday). Further, for a card member with a member ID “4980-0000-003”, since the card member has not used the card at a member store of the member store industry related to the first addition point rule information, The first addition point rule will not be applied to the card use on December 4, 2012 (Sat) and December 5, 2004 (Sun). Furthermore, for the card member whose member ID is “4980-0000-004”, since the weather forecast on the next day of December 11 (Saturday) was not “sunny”, a third addition is made for the card use on that day. The point rule is not applied, and the weather on the day before December 12 (Sunday) is not “rainy”, so the fourth additional point rule is not applied to the card use on that day.

  The contents as described above indicating whether or not each addition point rule is applied are transmitted to each card member by e-mail. Each card member receives an e-mail showing such contents at the member side terminal device 2 and confirms the contents. Thereby, each card member can confirm what addition point rule is applied to him / her.

[(4) Point collection]
The point management apparatus 1 performs point aggregation as follows. The following processing is executed every night as a nighttime batch processing by the point management device 1. In addition, the point management device 1 acquires in advance data relating to the record of the use of the credit card by the card member from the card settlement system 3. Based on the data, the usage record information in the format described with reference to FIG. 17 is generated, and the generated usage record information is stored in the use record DB 1615.

  FIG. 24 is a flowchart showing an operation flow of the point management apparatus 1 of the present invention in the point counting.

  First, the point management device 1 extracts usage record information from the usage record DB 1615 (S401). And the point management apparatus 1 selects a specific thing among the extracted utilization performance information as a process target (S402).

  Next, the point management device 1 executes calculation of points given at normal time for the card usage related to the usage record information selected in step S402 (S403). Then, based on the calculation result and the usage record information, the point total information in the format described with reference to FIG. 16 is generated, and the generated point total information is registered in the member / monthly point total DB 1614 (S404). ). At this time, the addition point field 414 of the point total information is “0”.

  Next, the point management apparatus 1 searches the addition point rule application result DB 1613 using the member ID of the usage record information selected in step S402 as a key (S405), and determines whether or not the search has succeeded (S405). S406). Here, when it is determined that the search is successful because there is application result information including the member ID (YES in S406), the point management device 1 proceeds to an additional point calculation process in step S407 described later. On the other hand, when it is determined that the search has failed because there is no application result information including the member ID (NO in S406), the point management device 1 has processed all the usage record information extracted in step S401. It is determined whether or not (S409). If it is determined that all the usage record information has been processed (YES in S409), the point management device 1 ends the process. On the other hand, if it is determined that there is usage history information that has not yet been processed (NO in S409), the point management device 1 returns to step S402 and selects new usage history information as a processing target.

  As described above, when it is determined in step S406 that the search is successful (YES in S406), the point management apparatus 1 executes the following addition point calculation process (S407).

  FIG. 25 is a flowchart showing an operation flow of the point management apparatus 1 of the present invention in the addition point calculation process.

  First, the point management apparatus 1 applies the application result information searched in step S405 to determine which of the additional point rules is applied to the card usage related to the usage record information selected in step S402. (S501). Hereinafter, an addition point is calculated using the addition point rule determined to be applied in step S501. For convenience of explanation, it is assumed in the following that it is determined in step S501 that all addition point rules are applied.

  The point management device 1 acquires the business type code and the member store code from the usage record information selected in step S402 (S502). The industry code is obtained by searching the member store information DB 1602 using the member store code as a key.

  Next, the point management device 1 searches the first addition point rule DB 1608 using the usage time of the usage record information and the business type code acquired in step S501 as a key, so that the card usage related to the usage record information is prevented. The first addition point rule to be applied is acquired (S503). And the point management apparatus 1 calculates the addition point provided with respect to the card | curd use which concerns on the said usage record information using the acquired 1st addition point rule (S504).

  Next, the point management device 1 searches the second addition point rule DB 1609 using the usage time and member store code of the usage record information as keys, thereby applying the card usage related to the usage record information. A 2-addition point rule is acquired (S505). And the point management apparatus 1 calculates the addition point provided with respect to the card | curd use which concerns on the said usage record information using the acquired 2nd addition point rule (S506).

  After that, the point management device 1 acquires the third addition point rule from the third addition point rule DB 1610 (S507), and uses the acquired third addition point rule for the card usage related to the usage record information. The added points to be given are calculated (S508). Further, the point management device 1 acquires the weather code of the current day and the previous day from the weather information DB 1603 based on the usage date of the usage record information, and searches the fourth addition point rule DB 1611 based on the acquired weather code. Thus, the fourth addition point rule applied to the card usage related to the usage record information is acquired (S509). And the point management apparatus 1 calculates the addition point provided with respect to the card | curd use which concerns on the said usage record information using the acquired 4th addition point rule (S510). Further, the point management device 1 searches the fifth addition point rule DB 1612 based on the usage time of the usage record information, thereby obtaining the fifth addition point rule applied to the card usage related to the usage record information. Obtain (S511). And the point management apparatus 1 calculates the addition point provided with respect to the card | curd use which concerns on the said use performance information using the acquired 5th addition point rule (S512).

  Next, the point management device 1 adds up the respective addition points calculated as described above to execute the summation of the addition points (S513), and executes Step S408 of the flowchart shown in FIG.

  In step S408, the point management apparatus 1 updates the member / monthly point totaling DB 1614 by storing the added points totaled in step S513 in the added point field 414 of the point totaling information.

  Next, the point management apparatus 1 determines whether or not all the usage record information extracted in step S401 has been processed (S409). If it is determined that all the usage record information has been processed (YES in S409), the point management device 1 ends the process. On the other hand, when it is determined that there is usage history information that has not yet been processed (NO in S409), the point management device 1 returns to step S402, selects new usage history information as a processing target, and continues the subsequent processing. To do.

  The point management apparatus 1 transmits the point total information stored in the member / monthly point total DB 1614 to the card settlement system 3 at an appropriate timing. As a result, the card settlement system 3 accumulates this point total information, and notifies each card member of the points given to the card member as necessary. Thereby, each card member can confirm the point given to self.

  As described in “(3) Application and notification of addition point rule” above, the card member who has received the e-mail can check what addition point rule is applied to himself / herself. . For each card member who has confirmed whether or not the addition point rule is applied in this way, an incentive to use the card is applied so that the addition point rule is applied in order to obtain the addition point. It will be. Thereby, when some card members use the card in such a manner, it is possible to avoid a phenomenon in which the card is concentrated in a certain period. As a result, it is possible to avoid the authorization processing that occurs with the use of the card from being concentrated in a certain period. That is, authorization processing can be distributed. Therefore, credit card companies can shorten the response time of authorization processing without taking measures such as adding equipment even during weekends and holidays in the time of the middle-year-end year-end or so-called Golden Week evenings. Can be planned.

  In addition, the incentives described above may stimulate the card member's willingness to purchase. Therefore, this invention can also recognize the effect as sales promotion. Therefore, the present invention is desired not only for credit card companies that can decentralize authorization processing and card members that can acquire additional points, but also for credit card company member stores.

  Since the point management method, the card system, and the point management device according to the present invention can avoid the concentration of predetermined processing that occurs with the use of a card over a certain period, the authorization with the use of a credit card can be avoided. This is useful for a credit card system where processing occurs.

It is a block diagram which shows the structure of the card system of this invention. It is a block diagram which shows the structure of the point management apparatus with which the card system of this invention is provided. It is a conceptual diagram which shows an example of the format of the information classified by authorization case memorize | stored in DB according to an authorization matter. It is a conceptual diagram which shows an example of the format of the member store information memorize | stored in member store information DB. It is a conceptual diagram which shows an example of the format of the weather information stored in weather information DB. It is a conceptual diagram which shows an example of a format of the 1st usage number information memorize | stored in 1st usage number information DB. It is a conceptual diagram which shows an example of a format of the 2nd usage number information memorize | stored in 2nd usage number information DB. It is a conceptual diagram which shows an example of the format of 3rd usage number information memorize | stored in 3rd usage number information DB. It is a conceptual diagram which shows an example of the format of 4th usage number information memorize | stored in 4th usage number information DB. It is a conceptual diagram which shows an example of a format of the 1st addition point rule information memorize | stored in 1st addition point rule DB. It is a conceptual diagram which shows an example of the format of the 2nd addition point rule information memorize | stored in 2nd addition point rule DB. It is a conceptual diagram which shows an example of the format of the 3rd addition point rule information memorize | stored in 3rd addition point rule DB. It is a conceptual diagram which shows an example of the format of the 4th addition point rule information memorize | stored in 4th addition point rule DB. It is a conceptual diagram which shows an example of a format of the 5th addition point rule information memorize | stored in 5th addition point rule DB. It is a conceptual diagram which shows an example of the format of the application result information memorize | stored in addition point rule application result DB. It is a conceptual diagram which shows an example of the format of the point total information memorize | stored in member and monthly point total DB. It is a conceptual diagram which shows an example of the format of the utilization track record information memorize | stored in utilization track record DB. It is a flowchart which shows the flow of operation | movement of the point management apparatus of this invention in the case of producing | generating 1st usage number information. It is a flowchart which shows the flow of operation | movement of the point management apparatus of this invention in the case of producing | generating 2nd usage number information. It is a flowchart which shows the flow of operation | movement of the point management apparatus of this invention in the case of producing | generating 3rd usage number information. It is a flowchart which shows the flow of operation | movement of the point management apparatus of this invention in the case of producing | generating 4th usage number information. It is a flowchart which shows the flow of operation | movement of the point management apparatus of this invention in the case of specifying the card member used as the object to which an addition point rule is applied. It is a flowchart which shows the flow of operation | movement of the point management apparatus of this invention in the case of performing notification that an addition point rule is applied. It is a flowchart which shows the flow of operation | movement of the point management apparatus of this invention in point totaling. It is a flowchart which shows the flow of operation | movement of the point management apparatus of this invention in an addition point calculation process.

Explanation of symbols

1 point management device 2 member side terminal device 3 card payment system 4 member store side terminal device 10 card system 11 CPU
DESCRIPTION OF SYMBOLS 12 Memory 13 Display part 14 Input part 15 Communication interface 16 Hard disk 1601 Authorization case specific database 1602 Merchant store information database 1603 Weather information database 1604 1st use number information database 1605 2nd use number information database 1606 3rd use number information database 1607 1st 4 usage number information database 1608 1st addition point rule database 1609 2nd addition point rule database 1610 3rd addition point rule database 1611 4th addition point rule database 1612 5th addition point rule database 1613 addition point rule application result database 1614 Monthly point total database 1615 Usage result database 1616 Elephants membership database

Claims (7)

A storage means having a predetermined storage area; a notification means for notifying a card member of a credit card of predetermined information; a search means for executing a database search; and points given for use of a credit card A card that includes a point calculation means for calculating, and that is configured to execute an authorization process that occurs when a credit card is used by a card member and to build a database that stores execution history information indicating the execution history In the system, a point management method for managing the points that the card member can use with respect to the use of the card,
The execution history information includes information in which a card usage time is associated with a card member identifier for identifying a card member,
The storage means storing a calculation rule of points given for the use of the card when the card is used during a non-peak time period;
The search means searches for the usage time of a card belonging to the peak time zone from the usage times of a plurality of cards in the execution history information stored in the database, and is associated with the usage time of the searched card. Identifying card members who have used the card during peak hours by referring to the card member identifier;
When the notification means uses the card in the non-peak time period in the future, information indicating that the calculation rule stored in the storage means is applied to the specified card member. A notification step;
The search means further includes a list of cards belonging to a non-peak time zone from the usage times of a plurality of cards in the execution history information indicating the execution history of the authorization process that has occurred after notification of the information indicating that the calculation rule is applied. Searching for usage time;
A point management method comprising: the point calculating means calculating a point given for use of a card related to the searched card use time based on the calculation rule. The database stores member store information in which a member store identifier for identifying a member store of a credit card is associated with a member store type identifier for identifying the type of business of the member store,
In the step of storing the calculation rule, the storage means stores the calculation rule determined for each type of business of a credit card member store,
The execution history information includes information in which the use time of the card, the card member identifier, and a member store identifier for identifying a member store that uses the card are associated with each other,
In the step of identifying the card member, the search means searches the member store information stored in the database using the member store identifier associated with the usage time of the searched card, and the member store Identify cardholders by merchant industry by referring to the merchant industry identified by the identifier,
In the step of notifying to the cardholder, said notifying means, wherein when performing card use of the non-peak hours is stored in the storage means, and, of the identified merchant future information indicating the calculation rule of the industry is applicable, notifies for the cardholder that is the specific, point management method according to claim 1. In the step of storing the calculation rule, the storage means stores the calculation rule determined for each credit card member store,
The execution history information includes information in which the use time of the card, the card member identifier, and a member store identifier for identifying a member store that uses the card are associated with each other,
In the step of specifying the card member, the search means specifies the card member for each member store by referring to the member store identified by the member store identifier associated with the usage time of the searched card. And
In the step of notifying to the cardholder, said signaling means are stored in said storage means in the case of use of the card in the non-peak hours in the future, and, to the identified merchant information indicating the calculation rule is applied according to notify for the terminal according to the cardholder that is the specific, point management method according to claim 1. A card payment system for executing an authorization process that occurs when a credit card is used by a credit card member, and a database for storing execution history information indicating an execution history of the authorization process. A card system comprising a point management device that manages points that can be used for use,
The execution history information includes information in which a card usage time is associated with a card member identifier for identifying a card member,
The point management device
Storage means for storing a calculation rule of points given for the use of the card when the card is used during non-peak hours;
The usage time of the card belonging to the peak time zone is searched from the usage times of the plurality of cards in the execution history information stored in the database, and the card member identifier associated with the searched usage time of the card is referred to. To identify cardholders who have used the card during peak hours ,
A notification means for notifying the specified card member of information indicating that the calculation rule stored in the storage means is applied when the card is used in the non-peak time period in the future; ,
Search for searching for the usage time of a card belonging to a non-peak time zone from the usage times of a plurality of cards in the execution history information indicating the execution history of the authorization process that has occurred after notification of the information indicating that the calculation rule is applied Means,
A card system comprising: point calculation means for calculating points given for card use related to the card use time searched by the search means based on the calculation rule. Provided in association with a card payment system for executing an authorization process that occurs when a credit card is used by a credit card member, and comprising a database for storing execution history information indicating an execution history of the authorization process, It is a point management device that manages the points that card members can use for card usage,
The execution history information includes information in which a card usage time is associated with a card member identifier for identifying a card member,
When a card is used during non-peak hours, storage means for storing a calculation rule of points given for the use of the card;
The usage time of the card belonging to the peak time zone is searched from the usage times of the plurality of cards in the execution history information stored in the database, and the card member identifier associated with the searched usage time of the card is referred to. by, and identifying means for identifying the cardholder you've used the card to the peak time zone,
A notification means for notifying the specified card member of information indicating that the calculation rule stored in the storage means is applied when the card is used in the non-peak time period in the future; ,
Search for searching for the usage time of a card belonging to a non-peak time zone from the usage times of a plurality of cards in the execution history information indicating the execution history of the authorization process that has occurred after notification of the information indicating that the calculation rule is applied Means,
A point management apparatus comprising: point calculation means for calculating points given for card use related to the card use time searched by the search means based on the calculation rule. The database stores member store information in which a member store identifier for identifying a member store of a credit card is associated with a member store type identifier for identifying the type of business of the member store,
The storage means stores the calculation rule determined for each type of credit card member store,
The execution history information includes information in which the use time of the card, the card member identifier, and a member store identifier for identifying a member store that uses the card are associated with each other,
The specifying means searches for member store information stored in the database using a member store identifier associated with the usage time of the searched card, and stores the type of member store identified by the member store identifier. To configure cardholders by merchant industry,
The notification means is stored in the storage means when the card is used in the non-peak time zone in the future, and the calculation rule relating to the business type of the specified member store is applied. information indicating, configured to notify for the cardholder that is the specified point management apparatus according to claim 5. The storage means stores the calculation rule determined for each credit card member store,
The execution history information includes information in which the use time of the card, the card member identifier, and a member store identifier for identifying a member store that uses the card are associated with each other,
The specifying means is configured to specify a card member for each member store by referring to a member store identified by a member store identifier associated with the searched card usage time,
The notification means is information stored in the storage means when the card is used in the non-peak time period in the future, and information indicating that the calculation rule relating to the specified member store is applied the configured to notify for the particular cardholder, point management apparatus according to claim 5.

Images