JP5306304B2 - Point management server and point management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technology for realizing new usage of points. <P>SOLUTION: An encashment shop 30D is a shop for paying cash based on common points and has a confirmation terminal 3 installed. In a point management server, a point conversion section 11 converts individual points of point cards A and B joined by a user 25 into common points based on point conversion information received from the a user terminal 5. When an encashment process reception section 12 receives encashment condition information specified encashment condition of common points of the user 25, the encashment process reception section 12 transmits, to the user terminal 5, payment instruction information which orders payment of cash and is associated with the encashment condition information. When a payment permission section 13 receives, from the confirmation terminal 3, payment confirmation information for confirming whether to permit payment of cash based on the common points, the payment permission section 13 determines whether to permit payment of cash based on the encashment condition information and the payment confirmation information. <P>COPYRIGHT: (C)2012,JPO&amp;INPIT

Description

  The present invention relates to a point management server, and more particularly to a point management server that migrates points of a plurality of point services to other points.

  Various point services are operated mainly in retail and service industries. The store issues a point card to a user who has subscribed to the point service. By presenting a point card when the user purchases a product or receives a service, the store gives the user points according to the price. The user can use the given points as part of the price when purchasing a new product.

  The user can receive an economic advantage by using the point card. A store operating a retail business or a service business can expect an increase in the frequency of user visits and an increase in sales by issuing a point card to the user.

JP 2002-99966 A

  Since the point card is issued for each company that operates the store, the user must carry a plurality of point cards. In addition, since points are given to the user for each point card, there is a problem that opportunities for the user to use the points are limited.

  Patent Document 1 discloses a point bank system that can use a plurality of point services as a common point. By using the point bank system according to Patent Document 1, the user can efficiently accumulate the points to be granted. However, even if a plurality of point services are used in common, points are used for discounts on products and services. Therefore, a user cannot use points without purchasing products or the like. As described above, there is a problem that a method of using points is limited regardless of whether the points are shared.

  An object of this invention is to provide the point management server and point management system which can implement | achieve the new usage method of a point.

In order to solve the above-mentioned problem, the invention according to claim 1 is a point management server, including store designation information that designates a store that pays cash according to a first point issued to a user. When receiving the redemption condition information specifying the redemption condition of the points, the storage unit storing the redemption condition information, and the payment instruction information notifying the cash payment according to the first point and not including the store designation information the, reception and cash procedure receiving unit to be sent to the source of the cash condition information to create, a payment confirmation information to confirm whether the payment based on the instruction information can be cash payments based on the cash condition information If you, the store information recorded in the payment confirmation information, and the based on the stored store specified information in the storage unit, determines payment authorization unit whether to permit the payment of the cash, Provided.

According to a second aspect of the invention, the point management server according to claim 1, wherein the cashing condition information includes authentication information, which has been designated by the user, the payment authorization unit, said the supplied credentials Based on the authentication information recorded in the payment confirmation information, it is determined whether or not the cash payment is permitted.

The invention according to claim 3 is the point management server according to claim 2 , wherein the cashing procedure accepting unit displays flag information indicating whether or not cash is paid based on the cashing condition information. The information is stored in the storage unit in association with the information, and the payment permission unit determines whether to permit the payment of the cash based on the flag information.

According to a fourth aspect of the present invention, in the point management server according to any one of the first to third aspects, a second point issued to the user is further transmitted from a user terminal operated by the user. A point transfer unit for transferring to the first point based on the point transfer information.

According to a fifth aspect of the invention, a point management system, and the point management server that manages the issued Lupo Into the user, and the user terminal that the user operates, it is installed in a store, before Kipo Into store specified information and the confirmation terminal to confirm cash whether or not the payment is possible to the point management server, the amount of which was, wherein the point management server, you specify the store to pay the cash in accordance with the previous SL point depending on the when receiving the cash condition information specifying the redemption condition of the point it includes from the user terminal, and instructs a storage unit for storing the cash condition information, cash payments according to the prior Kipo into, and the store the payment instruction information does not include the designation information, a cash procedure accepting unit were prepared in accordance with the realization condition information transmitted to the user terminal, the cash based on the payment instruction information If the payment confirmation information for confirming whether or not payment can received from the confirmation terminal, and store information recorded in the payment confirmation information, based on the stored store specified information in the storage unit, the cash A payment permission unit that determines whether or not to permit the payment.

The invention according to claim 6 is the point management system according to claim 5 , wherein the cashing procedure receiving unit generates a two-dimensional code in which the payment instruction information is recorded, and the two-dimensional code is stored in the user terminal. The confirmation terminal reads the two-dimensional code, reproduces the payment instruction information, and generates the payment confirmation information using the reproduced payment instruction information.

  By using the common point management server of the present invention, the points given to the user can be cashed. When cash payment according to points is requested, the point management server pays cash based on payment confirmation information requesting cash payment and cashing condition information recording cashing conditions specified by the user. Decide whether to allow. For this reason, since the payment of cash is not performed when the cashing conditions specified by the user are not satisfied, it is possible to prevent the cash corresponding to the points from being illegally paid.

It is a figure which shows the structure of the common point system which concerns on embodiment of this invention. It is a sequence diagram which shows operation | movement of the common point system in a point provision process. It is a figure which shows a common point member database. It is a figure which shows point provision information. It is a figure which shows a point management database. It is a sequence diagram which shows operation | movement of the common point system in a point transfer process. It is a figure which shows a point transfer screen. It is a sequence diagram which shows operation | movement of the common point system in a cash procedure process. It is a figure which shows a cashing procedure screen. It is a figure which shows a cash history database. It is a sequence diagram which shows operation | movement of the common point system in a payment confirmation process. It is a flowchart which shows the flow of the process which determines whether the payment of the cash according to a point is permitted.

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

{1. Configuration of common point system 100}
FIG. 1 is a diagram showing a configuration of a common point system 100 according to the present embodiment. The common point system 100 is a system that manages points of point cards A and B, which are different from each other, and points (common points) of a common point card C that can be used as the point cards A and B.

  When the point cards A and B have already been issued to the user 25, the user 25 can have the common point card C issued by the operator of the common point card C. Thereby, the user can receive each service of the point cards A and B by presenting the common point card C to the store. Since the user 25 does not have to carry the point cards A and B, the convenience of the user 25 can be improved.

  The stores 20A and 20B operate different point services. The store 20 </ b> A issues a point card A to the user 25. The store 20 </ b> B issues a point card B to the user 25. The user 25 has a common point card C that can be used as the point cards A and B. The user 25 can accumulate the points (individual points) of the point cards A and B by presenting the common point card C when purchasing the product at the stores 20A and 20B.

  As a feature of the common point card C, the user 25 can exchange the points (common points) of the common point card C. A common point is generated by transferring individual points of the user 25. The cashing shop 30 </ b> D is a store that pays common points as cash to the user 25.

  As shown in FIG. 1, the common point system 100 includes a common point management server 1, point granting terminals 2 </ b> A and 2 </ b> B, a confirmation terminal 3, individual point management servers 4 </ b> A and 4 </ b> B, and a user terminal 5.

  The common point management server 1 is a server that manages the common points of the user 25 and the individual points of the point cards A and B. The common point management server 1 executes a process for transferring an individual point to a common point, a process related to a common point redemption procedure, and a determination process for determining whether or not a payment request from a redemption shop is acceptable.

  The point grant terminals 2A and 2B are terminals that issue individual points to be given to users. The point granting terminal 2A is installed in the store 20A that issues the point card A. The point granting terminal 2B is installed in the store 20B that issues the point card B. The confirmation terminal 3 is installed in the cashing shop 30D and confirms with the common point management server 1 whether or not cash payment according to the number of points of the common points is possible.

  The individual point management server 4A is a server that manages individual points of the point card A. The individual point management server 4B is a server that manages individual points of the point card B. The individual point management servers 4A and 4B not only manage the individual points given to the user 25 who owns the common point card C, but also manage individual points of users who do not have the common point card C.

  The user terminal 5 is a personal computer possessed by the user 25. The user 25 can operate the user terminal 5 to access the common point management server 1 to perform the transfer of the individual points to the common points and the common point cashing procedure. As the user terminal 5, a mobile phone possessed by the user 25 or a smartphone may be used.

{2. Configuration of common point management server 1}
Next, the configuration of the common point management server 1 will be described. The common point management server 1 includes a point transfer unit 11, a cash procedure acceptance unit 12, a payment permission unit 13, a database management unit 14, and a storage unit 15.

  The storage unit 15 stores various databases necessary for managing common points and individual points. Specifically, the storage unit 15 includes a common point member database (DB) 151, a point management DB 152, and a cash history DB 153. The common point member DB 151 is a database in which the ID of the common point card C of each user is associated with the IDs of the point cards A and B. The point management DB 152 is a database that manages common points and individual points of the user 25. The cash history DB 153 is a database that records various types of information necessary for cashing common points.

  The point transfer unit 11 transfers the individual points of the point cards A and B to which the user 25 joins to a common point according to an instruction from the user terminal 5. The user 25 may request the store clerk of the stores 10A and 20B to shift to a common point. In this case, the point transfer unit 11 shifts to a common point in accordance with instructions from the point grant terminals 2A and 2B.

  The cashing procedure acceptance unit 12 creates payment instruction information for instructing cash payment based on the designated cashing condition and transmits the payment instruction information to the user terminal 5 when the cashing condition for the common points is designated by the user terminal 5. .

  The payment permission part 13 determines whether cash payment is permitted, when the payment confirmation information 56 (refer FIG. 11) which confirms whether cash payment is possible from the confirmation terminal 3 is received. Details of the payment confirmation information 56 will be described later.

  The database management unit 14 updates the common point member DB 151, the point management DB 152, and the cash history DB 153 stored in the storage unit 15.

{3. Operation of common point system 100}
Hereinafter, the operation of the common point system 100 will be described in the order of point grant processing, point transfer processing, cashing procedure processing, and payment confirmation processing. The point giving process is a process for giving new individual points to the point cards A and B by using the common point card C when the user 25 makes a purchase. The point transfer process is a process for transferring individual points of the point cards A and B to a common point. The cashing procedure process is a process of designating a cashing condition when the user 25 cashes his / her common points. The payment confirmation process is a process performed when the user 25 requests payment of cash at the cashing shop D.

{3.1. Point grant processing}
FIG. 2 is a sequence diagram showing the operation of the common point system 100 in the point grant processing. It is assumed that the user 25 already has point cards A and B.

  First, when a point card C is newly issued to the user 25, information related to the user 25 is registered in the common point member DB 151 (step S11). Specifically, the user 25 applies for the issuance of the common point card C to the operator of the common point card C. The user enters the IDs of the point cards A and B possessed by the user along with the name on the application form. The operator registers information related to the user 25 in the common point member DB 151 based on the entry items of the application form. Thereby, the user 25 can use the common point card C instead of the point cards A and B.

  FIG. 3 is a diagram showing the common point member DB 151 in the form of a table. The common point member ID is identification information of each user who has issued the common point card C. In the name, the name of the user described in the application form is registered. In the individual member ID, the ID of a point card corresponding to the point service that can be used with the common point card C is registered. For example, as the individual member ID of the user 25, the ID “a1b2” of the point card A and the ID “gh89” of the point card B are registered.

  The user 25 presents the common point card C and purchases a product at the store 20A. The point granting terminal 2A gives individual points of the point card A to the user 25 according to the purchase price of the product paid by the user 25 (step S12). The point grant terminal 2A transmits the point grant information 51 to the common point management server 1 (step S13).

  FIG. 4 is a diagram showing the point grant information 51. As shown in FIG. 4, “1234” corresponding to the user 25 who purchased the product is recorded as the common point member ID in the point grant information 51. The store information is information for identifying the store 20A that issued the individual points. Although details will be described later, it is possible to specify which point card the individual points given to the user 25 correspond to based on the store information. As a grant point, “20 pt” granted based on the purchase price of the product is recorded. When the user 25 uses the individual points of the point card A at the time of product purchase, a negative value is recorded in the granted points.

  Reference is again made to FIG. The database management unit 14 updates the point management DB 152 based on the received point grant information 51 (step S14). FIG. 5 is a diagram showing the point management DB 152 in the form of a table. As shown in FIG. 5, the common point member ID, name, and number of points are recorded in the point management DB 152. As the number of points, common points and individual points of point cards A and B are recorded.

  In the common point management server 1, store information of stores 20A and 20B is registered in advance. For this reason, the common point management server 1 sets the point number (1900 points) of the point card A of the user 25 recorded in the point management DB 152 to 20 based on the point grant information 51 and the store information registered in advance. Add points.

  The common point management server 1 transmits the point update information 52 to the individual management server 4A that manages the individual points of the point card A (step S15). The point update information 52 includes the ID of the point card A of the user 25 (see FIG. 3) and the number of points newly given (see FIG. 4). The point update information 52 is generated based on the common point member DB 151 and the point grant information 51.

  The individual point management server 4A updates the individual point DB 40A using the received point update information 52 (step S16). The individual point DB 40A is a database for managing individual points of all the members who are subscribed to the point card A. That is, the individual point DB 40A manages not only the user 25 who owns the common point card C but also individual points of other users who do not have the common point card C.

  The user 25 may present the point card A instead of the common point card C when purchasing the product. In this case, as illustrated in FIG. 1, the point granting terminal 2 </ b> A transmits the ID of the point card A of the user 25 and the grant points to the individual point management server 4 </ b> A via the network 6. The individual point management server 4A notifies the common point management server 1 that the individual points of the point card A given to the user 25 have been updated after updating the individual point management DB 40A based on the received information. As a result, the point management DB 152 is updated.

  In this way, the common point management server 1 and the individual point management servers 4A and 4B synchronize the contents of the point management DB 153 and the individual point management DBs 40A and 40B each time the individual points of the point cards A and B are updated. Let

{3.2. Point transfer processing}
The user 25 can transfer individual points recorded in the point management DB 152 to common points. FIG. 6 is a sequence diagram showing the operation of the common point system 100 in the point transfer process. Hereinafter, the point transfer process will be described in detail with reference to FIG.

  The user terminal 5 transmits a point transfer screen display request to the common point management server 1 in accordance with the operation of the user 25 (step S21). The point transfer unit 11 transmits the data of the point transfer screen to the user terminal 5 based on the point transfer screen display request (step S22). The user terminal 5 displays a point transfer screen on the monitor based on the received data.

  FIG. 7 is a diagram showing the point transfer screen 31. In the individual point display frame 31A, the number of individual points of the point cards A and B given to the user 25 is displayed. In FIG. 7, the number of points of the user 25 is displayed based on the point management DB 152 shown in FIG. The user 25 inputs the number of points (transfer points) to be transferred to a common point among the individual points (1900 points) of the point card A into the text box 31B. Of the individual points (1200 points) of the point card B, the number of transfer points is entered in the text box 31C.

  In the conversion result display frame 31D, conversion results when the transition points input in the text boxes 31B and 31C are converted into common points are displayed. The display content of the conversion result display frame 31D is updated each time a transition point is input to the text boxes 31B and 31C.

  In the conversion result display frame 31D, the total of the transition points input in the text boxes 31B and 31C is displayed. The transfer rate is a conversion rate for calculating common points from the total of transfer points. As the transfer rate, 90% is uniformly applied to the individual points of the point cards A and B. By multiplying the total migration points (2500 points) by the migration rate (90%), the migration points after application of the migration rate are calculated as new common points (2250 points). The difference point (250 points) between the total value of the transfer points and the new common points is used as a fee paid to the cashing shop 30D that pays the user 25 cash.

  As the transfer rate, the conversion rate (90%) common to the point cards A and B may not be applied. For example, in order to adjust the monetary value per point of each individual point of the point cards A and B, a transition rate may be provided for each individual point.

  The common point display frame 31E displays the change of the common point accompanying the point shift. The common point balance indicates the balance of the common points of the user 25 at the time of instructing the current point shift. The new common point corresponds to the transition point (conversion result display frame 31D) after the transition rate is applied. The total common point is a total value of the common point balance and the new common point. That is, the total common point indicates a common point that can be used by the user 25 after the point shift.

  Reference is again made to FIG. When the user 25 clicks the transfer confirmation button 31F, the user terminal 5 transmits the point transfer information 53 to the common point management server 1 (step S24). The point transfer information 53 includes the common point member ID of the user 25 and the transfer points of the point cards A and B.

  The point transfer unit 11 updates the point management DB 152 based on the received point transfer information 53 (step S25). The point transfer unit 11 stores a conversion rate in advance. Therefore, the point transfer unit 11 calculates a new common point (2250 points) from the conversion rate (90%) and the transfer points (1500 points, 1000 points) of the point cards A and B. The point management DB 152 is updated based on the transfer points of the point cards A and B and the new common points. For example, when the common points and the individual points are the number of points shown in FIG. 5, 1500 and 1000 points are subtracted from the individual points of the point cards A and B, respectively. 2250 points are added to the common points.

  The point transfer unit 11 transmits the point update information 52 to the individual point management server 4A along with the update of the point management DB 152 (step S26). The individual point management server 4A updates the individual point management DB 40A based on the received point update information 52 (step S27). Although not shown in FIG. 6, the point update information 52 is also transmitted to the individual point management server 4B.

  The point transfer unit 11 creates transfer history information (not shown) indicating that the individual points of the point cards A and B have been transferred to a common point, and stores them in the storage unit 15. The transfer history information is used for point settlement between the stores 20A and 20B and the operator of the common point card C.

{3.3. Cash procedure processing}
As described above, the user 25 can exchange the common points given to the user 25. When redeeming common points, the user needs to specify the cashing conditions.

  FIG. 8 is a sequence diagram showing the operation of the common point system 100 in the cashing procedure process. As shown in FIG. 8, the user terminal 5 transmits a display request for a cashing procedure screen for performing a cashing procedure for common points to the common point management server 1 in accordance with an operation of the user 25 (step S31). The display request includes the ID and password of the specified common point card C specified by the user 25 at the time of application for issuance. Based on the received display request, the cashing procedure acceptance unit 12 transmits data of the cashing procedure screen to the user terminal 5 (step S32). The user terminal 5 displays a cash procedure screen on the monitor based on the received data.

  FIG. 9 is a diagram showing a cashing procedure screen 32 displayed on the monitor of the user terminal 5. The user 25 inputs the cashing conditions for the common points to the cashing procedure screen 32 (step S33).

  The user 25 inputs his common point member ID into the text box 32F. In the cash point designation frame 32A, the common points of the user 25 recorded in the point management DB 152 are displayed as the balance of the common points. The user 25 inputs a common point (cash point) to be redeemed in the text box 32B within the range of the common point balance. The amount paid to the user 25 and the balance of the common points after the redemption are displayed in the redemption point designation frame 32A according to the redemption point input in the text box 32B.

  The user 25 designates a store that receives cash to be paid based on the cash points using the pull-down menus 32C and 32D. The pull-down menu 32C displays a list of areas where stores where the user 25 desires to receive cash are present. The pull-down menu 32D displays a list of stores where cash can be paid in the area selected by the pull-down menu 32C. The user designates a store that receives cash from the list in the pull-down menu 32D. When the user 25 receives cash corresponding to the cashing point, the user 25 inputs a password used for identity verification into the text box 32E. The password entered in the text box 32E is a one-time password used for identity verification when paying cash, and is different from the password for the point card C.

  When the user 25 clicks the determination button 32G, the user terminal 5 transmits the information input in the text boxes 32B to 32F to the common point management server 1 as the cashing condition information 54 (step S34).

  The cashing procedure acceptance unit 12 updates the cashing history DB 153 based on the received cashing condition information 54 (step S35). FIG. 10 is a diagram showing the cash history DB 153 in the form of a table. As shown in FIG. 10, the cash number history DB 153 records the reference number, the common point member ID, the cash point, the cash amount, the selected area, the selected store, the password, the cashed flag, and the cash time.

  The reference number is an identification number assigned to the received cashing condition information 54. The common point member ID, the cashing point, the cashing amount, the selected area, the selected store, and the password are recorded based on the cashing condition information 54. The cashed flag is a flag indicating whether or not the cash based on the cashing points has been paid. The cashing time indicates the time when cash based on the cashing points is paid at the selected store. Information entered by the user 25 on the cashing procedure screen 32 shown in FIG. 9 is shown in the second line of the cashing history DB 153. At the time when the user 25 performs the cashing procedure, the cash payment based on the cashing point is not performed. Therefore, the cashed flag and the cashing time are blank at this time.

  Again referring to FIG. The cashing procedure acceptance unit 12 generates payment instruction information 55 in which the reference number, the cashing amount, and the common point member ID registered in the cashing history DB 153 are recorded (step S36). The cashing procedure acceptance unit 12 generates a two-dimensional code in which the payment instruction information 55 is recorded. A QR code (registered trademark) or the like can be used as the two-dimensional code. The generated two-dimensional code is transmitted from the common point management server 1 to the user terminal 5 (step S37).

{3.4. Payment confirmation process}
The user 25 operates the user terminal 5 to print a two-dimensional code. The user 25 presents the printed two-dimensional code at the selected store (the cashing shop 30D), and requests payment of cash according to the cashing point. When the user terminal 5 is a mobile device such as a mobile phone, the user 25 displays the two-dimensional code on the monitor of the user terminal 5 and presents it to the cashing shop 30D.

  The cashing shop 30D does not immediately pay cash according to the cashing point in response to a request from the user 25. When the common point management server 1 permits payment of cash corresponding to the cashing point, the cashing shop 30D pays the user 25 cash corresponding to the cashing point.

  FIG. 11 is a sequence diagram showing the operation of the common point system 100 in the payment confirmation process. The confirmation terminal 3 installed in the cashing shop 30D has a two-dimensional code reading function. The confirmation terminal 3 reads the two-dimensional code presented by the user (step S41) and reproduces the payment instruction information 55. Based on the reproduced payment instruction information 55, the confirmation terminal 3 determines that the payment of cash corresponding to the cashing point is requested, and displays a password input screen on the monitor.

  The user 25 inputs the password designated on the cashing procedure screen 32 (see FIG. 9) to the confirmation terminal 3 (step S42). After the password is input, the confirmation terminal 3 transmits the payment confirmation information 56 to the common point management server 1 (step S43). The payment confirmation information 56 includes the reference number of the payment instruction information 55, the password input to the confirmation terminal 3, and store information of the cashing shop 30 </ b> D preset in the device itself.

  The payment permission unit 13 determines whether or not to permit payment of cash based on the payment confirmation information 56 and the cash history DB 153 (step S44). The payment permission part 13 transmits the determination result information 57 which shows a determination result to the confirmation terminal 3 (step S45).

  FIG. 12 is a flowchart showing a flow of processing (step S44) for determining whether or not to permit payment of cash according to the cashing point. The payment permission unit 13 specifies the cashing condition information 54 corresponding to the reference number of the payment confirmation information 56 from the cashing history DB 153 (step S442).

  If the redeemed flag corresponding to the identified redemption condition information 54 is “already redeemed” (Yes in step S442), the payment permission unit 13 does not permit the payment of cash according to the redeem points (step S443). Thereby, it is possible to prevent the cash corresponding to the cashing point from being paid twice.

  If the cashed flag corresponding to the specified cashing condition information 54 is blank (No in step S442), the payment permission unit 13 stores the shop information of the payment confirmation information 56 and the shop selected by the specified cashing condition information 54. It is confirmed whether or not the information matches (step S444).

  If the store information does not match (No in step S444), the payment permission unit 13 does not permit the payment of cash according to the cashing point (step 445). That is, the payment permission unit 13 determines that cash payment is requested from a store other than the store designated by the user 25. It can be prevented that the cashing shop 30D charges the cash corresponding to the cashing point to the user 25, thereby illegally charging the cash corresponding to the fee and the cashing point from the operator.

  On the other hand, when the store information matches (Yes in step S444), the payment permission unit 13 checks whether or not the password of the payment confirmation information 56 matches the password of the specified cashing condition information 54 (step S445). ). If the passwords match (Yes in step S445), the payment permission unit 13 determines that the user 25 who has exchanged cash is requesting cash payment, and permits cash payment (step S446). . If the passwords do not match (Yes in step S445), the payment permission unit 13 determines that a third party who has not redeemed the money has illegally requested payment of the cash, and paid the cash. Not permitted (step S443).

  As described above, the payment permission unit 13 determines whether or not to permit the payment of cash according to the payment confirmation information 56 based on the cashed flag, the store information, and the password. Thereby, it becomes possible to prevent the cash payment based on the common points from being performed illegally.

  When the confirmation terminal 3 receives the determination result information 57 in which a message for permitting payment is recorded, the confirmation terminal 3 displays a message indicating that cash payment is possible on the monitor. In this case, the clerk of the cash exchange shop 30D pays cash to the user 25.

  FIG. 11 will be referred to again. When the payment permitting unit 13 transmits the determination result information 57 in which a message permitting payment is recorded (step S45), the payment permitting unit 13 determines that the payment of cash corresponding to the cashing point has ended. The payment permission unit 13 updates the point management DB 152 by subtracting the cash points from the common points of the user 25. In the cash history DB 153, “Cashed” is recorded in the paid flag corresponding to the cashing condition information 54 specified in step S442 (see FIG. 12). Thereby, the payment confirmation process ends.

  As described above, the common point system 100 can transfer the individual points of the point cards A and B to the common points and pay the common points as cash. Thus, the common point system 100 can provide a new point usage method of paying points as cash.

  Whether the common point management server 1 permits the payment of cash according to the cashing point based on the cashing condition information 54 in which the cashing condition specified by the user is recorded and the payment confirmation information 56 transmitted from the confirmation terminal 3. Determine whether or not. Thereby, it is possible to prevent the cash payment according to the cashing point from being illegally performed.

  In the present embodiment, the example in which the individual points of the point cards A and B are transferred to the common points and the common points are exchanged has been described. However, the individual points of the point card A may be exchanged without shifting to the common points. For example, when the store 20A directly cashes the individual points of the point card A, the cashing procedure process and the payment confirmation process described above can be used.

DESCRIPTION OF SYMBOLS 1 Common point management server 2A, 2B Point grant terminal 3 User terminal 4A, 4B Individual point management server 5 Confirmation terminal 11 Point transfer part 12 Cash procedure part 13 Payment judgment part 15 Storage part 151 Common point member DB
152 point management DB
153 Cash history DB

Claims (6)

When receiving the cashing condition information specifying the cashing condition of the first point including the shop designating information specifying the shop that pays the cash according to the first point issued to the user, the cashing condition information is stored. A storage unit;
A cashing procedure accepting unit that instructs payment of cash according to the first point and generates payment instruction information not including the store designation information based on the cashing condition information and transmits it to a transmission source of the cashing condition information When,
When payment confirmation information for confirming whether or not cash payment is possible based on the payment instruction information is received, based on the store information recorded in the payment confirmation information and the store designation information stored in the storage unit A payment permission unit for determining whether or not to permit payment of the cash;
A point management server comprising: In the point management server according to claim 1 ,
The cash condition information is
Authentication information specified by the user;
Including
The payment management unit is a point management server that determines whether to permit the payment of the cash based on the designated authentication information and the authentication information recorded in the payment confirmation information. In the point management server according to claim 2 ,
The cashing procedure acceptance unit stores flag information indicating whether or not cash is paid based on the cashing condition information in the storage unit in association with the cashing condition information,
The said payment permission part is a point management server which determines whether the payment of the said cash is permitted based on the said flag information. In the point management server according to any one of claims 1 to 3 ,
A point transfer unit for transferring the second point issued to the user to the first point based on point transfer information transmitted from a user terminal operated by the user;
A point management server comprising: A point management server which manages Lupo Into issued to the user,
A user terminal operated by the user;
Is installed in a store, and the confirmation terminal to confirm whether or not it is possible to payment of the amount of cash in accordance with the previous Kipo Into to the point management server,
With
The point management server
If the cash condition information specifying the redemption condition of the point includes a store specification information specifying the store to pay cash in accordance with the prior SL points received from the user terminal, a storage unit for storing the cash condition information,
Before and instructs the payment of cash in accordance with the Kipo Into, and the payment instruction information that does not include the store specified information, the created on the basis of the cash condition information be transmitted to the user terminal cashing procedure receiving unit,
When payment confirmation information for confirming whether or not cash payment based on the payment instruction information is possible is received from the confirmation terminal, the store information recorded in the payment confirmation information and the store designation stored in the storage unit A payment permission unit for determining whether or not to permit payment of the cash based on the information ;
A point management system. The point management system according to claim 5 ,
The cash procedure accepting unit generates a two-dimensional code in which the payment instruction information is recorded, transmits the two-dimensional code to the user terminal,
The point management system, wherein the confirmation terminal reads the two-dimensional code, reproduces the payment instruction information, and generates the payment confirmation information using the reproduced payment instruction information.

Images