Privilege application device

Abstract

To provide a privilege application device for applying a privilege to a user by taking an element of chance into account without using a lottery in an electronic settlement service.SOLUTION: A privilege application device 1A includes an acquisition unit 111 for acquiring settlement information including amount information showing a use amount about electronic settlement and identification information identifying a user of the electronic settlement, generated by each of a plurality of terminal devices, a comparison unit 113A for mutually comparing use amounts shown by settlement completion information with completed settlement in a prescribed period in the settlement information acquired by the acquisition unit 111, an extraction unit 114 for extracting a plurality of pieces of settlement completion information fulfilling a prescribed condition from the settlement completion information with the completed settlement in the prescribed period on the basis of a comparison result of the comparison unit 113A, and a notification unit 115 for notifying the plurality of terminal devices for performing one-to-one correspondence of the plurality of pieces of settlement completion information extracted by the extraction unit 114 of privilege information showing a privilege through a communication device 13.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a privilege granting device. [Background technology]

[0002] Electronic payment services using credit cards and smartphones are becoming more and more common. When a user uses an electronic payment service, a coupon that allows the user to receive a discount may be issued through a lottery.

[0003] In relation to electronic payment services, Patent Document 1 discloses a system that gives users benefits in so-called joint purchases. Joint purchases on shopping sites are electronic commerce services that display a sales price set according to the total number of purchase applications for the product and the minimum total number of applications required for a product transaction to be concluded on a web page that introduces the products to be sold, solicit applications from customers, and when the total number of applications reaches the maximum number of sales and the product is sold out or when a specified sales period has elapsed, close the applications and sell the product at an actual sales price according to the final total number of applications. Patent Document 1 discloses a system that returns a benefit according to the profit to the purchaser of the product when the same product is sold within a specified period. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2002-170021 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in conventional electronic payment services, when rewards were awarded to users through a lottery, the processing load associated with the lottery was a problem. In addition, the system disclosed in Patent Document 1 only awarded rewards when the same product was purchased, meaning that it could not be applied to general electronic payment services in which multiple users purchase different products.

[0006] The present disclosure has an object to provide a reward granting device that grants rewards to users by taking into account an element of chance while reducing the processing load in an electronic payment service. [Means for solving the problem]

[0007] The bonus granting device of the present disclosure comprises an acquisition unit that acquires payment information generated by each of a plurality of terminal devices, the payment information including amount information indicating the amount used for electronic payment and identification information identifying the user of the electronic payment; a comparison unit that compares the amounts used indicated by payment completion information for which payment was completed within a specified period among the payment information acquired by the acquisition unit; an extraction unit that extracts a plurality of payment completion information that satisfies a specified condition from the payment completion information for which payment was completed within the specified period based on the comparison result of the comparison unit; and a notification unit that notifies a plurality of terminal devices that correspond one-to-one to the plurality of payment completion information extracted by the extraction unit of bonus information indicating a bonus via a communication device. Effect of the Invention

[0008] According to the present disclosure, the processing load for providing rewards can be reduced, and the use of electronic payment that takes into account the element of chance is encouraged. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram showing an overall configuration of a privilege granting system 1A. [Diagram 2] FIG. 2 is a block diagram showing a configuration example of a payment server 10A. [Diagram 3] FIG. 13 is a diagram showing an example of the configuration of a terminal table TTB. [Figure 4]FIG. 13 is a diagram showing an example of the configuration of a user database UDB[A]. [Diagram 5] FIG. 1 shows an example of the configuration of the history database HDB[A]. [Figure 6] FIG. 11 is a diagram showing an example of payment completion information. [Figure 7] FIG. 2 is a block diagram showing an example of the configuration of a user device 20. [Figure 8] FIG. 13 is a sequence diagram of the privilege granting system 1A during payment. [Figure 9] 13 is a flowchart showing a process for granting a bonus by the payment server 10A. [Figure 10] FIG. 4 is a block diagram showing a configuration example of a payment server 10B. [Figure 11] FIG. 13 is a diagram showing an example of the configuration of a user database UDB[B]. [Figure 12] A diagram showing an example of the configuration of the history database HDB[B]. [Figure 13] FIG. 1 is a block diagram showing an overall configuration of a privilege granting system 1C. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Various embodiments according to the present disclosure will be described below with reference to the drawings. As described above, in conventional electronic payment services, when a user is awarded a reward by lottery, the processing load associated with the lottery is a problem. In addition, since the reward is awarded only when the same product is purchased, there is a problem that the reward cannot be applied to general electronic payment services in which multiple users purchase different products. The purpose of the reward awarding system of the present invention is to solve these problems.

[0011] 1: First embodiment Hereinafter, a privilege granting system 1A according to a first embodiment will be described with reference to FIGS.

[0012] 1-1: Configuration of the first embodiment 1-1-1: Overall composition Fig. 1 is a block diagram showing the overall configuration of a reward granting system 1A according to this embodiment. As shown in Fig. 1, the reward granting system 1A includes a payment server 10A, a user device 20, a store device 30, a virtual store server 40, a management server 50, a card company server 60, and a bank server 70. The payment server 10A, the user device 20, the store device 30, the virtual store server 40, the management server 50, the card company server 60, and the bank server 70 are connected to each other via a communication network NET so as to be able to communicate with each other. 1, the number of user devices 20, store devices 30, virtual store servers 40, and bank servers 70 is one, which is merely an example. The reward granting system 1A includes any number of user devices 20, store devices 30, virtual store servers 40, and bank servers 70. The numbers of user devices 20, store devices 30, virtual store servers 40, and bank servers 70 may be the same as or different from one another.

[0013] When a user U of the user device 20 purchases a product or service using a credit card or a QR code, the payment server 10A executes payment of the usage fee using a credit card or a QR code. In addition, the payment server 10A grants a benefit to the user U according to the conditions of the payment. The payment server 10A is an example of a "benefit granting device." Note that "QR code" is a registered trademark.

[0014] The user device 20 is a device used by a user U. When the user U makes a payment using a credit card or a QR code, the user device 20 acquires bonus information from the payment server 10A depending on the conditions of the payment. The bonus information is, for example, an electronic coupon or points. As an example, the user device 20 is a smartphone, a smartwatch, or a tablet terminal. The user device 20 is an example of a "terminal device."

[0015] The in-store device 30 is installed in a physical store, and when a user U makes a payment using a credit card or a QR code, it reads the information on the credit card or the QR code. Alternatively, the in-store device 30 itself may display the QR code. The in-store device 30 is connected to a credit card reader. The in-store device 30 obtains the information on the credit card read by the credit card reader. When a user U uses a credit card to purchase a product or service at a brick-and-mortar store, for example, a POS (Point Of Sales) register installed at the brick-and-mortar store is not linked to the in-store device 30 connected to the credit card reader. A store clerk at the brick-and-mortar store inputs the usage amount into the POS system independently of the in-store device 30 for sales management. The store clerk then inputs the usage amount displayed on the POS register into the in-store device 30, and transaction information including information indicating each of a user ID identifying the user U, a credit card number, a credit card expiration date, a usage amount, a usage date and time, a terminal number of the in-store device 30, a type of currency used for settlement, and an area where the in-store device 30 is installed is transmitted from the in-store device 30 to the management server 50. The information indicating the usage amount is an example of "amount information." The user ID is also an example of "identification information." The in-store device 30 may be, for example, a tablet terminal. The in-store device 30 is an example of a "terminal device."

[0016] The virtual store server 40 is a server that manages an EC (Electronic Commerce) site. A user U accesses the EC site using a user device 20. In addition, the user U operates the user device 20 to purchase a product or service sold on the EC site. When user U purchases a product or service on an EC site using a credit card number, transaction information including the credit card number, the credit card expiration date, the amount used on the above-mentioned EC site, the date and time of use, the terminal number of the virtual store server 40, the type of currency used for payment, and the area where the virtual store server 40 is located is sent from the virtual store server 40 to the management server 50 in accordance with user U's operation.

[0017] The management server 50 is a server that manages one or more store devices 30 and one or more virtual store servers 40. The management server 50 transmits transaction information received from the store devices 30 or the virtual store servers 40 to the card company server 60.

[0018] The card company server 60 is a server of a card company that issues the credit card and QR code used by the user U. The card company server 60 transmits the transaction information received from the management server 50 to the settlement server 10A. The payment server 10A checks the validity of the credit card and whether the amount used is within the credit limit of the credit card based on the transaction information received from the card company server 60. Alternatively, instead of checking whether the amount used is within the credit limit of the credit card, the payment server 10A may check with the bank server 70 whether the amount used is within the balance of the account linked to the credit card. Alternatively, the payment server 10A may check whether the amount used is within the credit limit of the credit card and also check with the bank server 70 whether the amount used is within the balance of the account linked to the credit card.

[0019] When the confirmation in the payment server 10A is completed, the payment server 10A transmits confirmation information indicating the result of the confirmation to the card company server 60. The card company server 60 transmits the confirmation information received from the payment server 10A to the management server 50. In addition, the management server 50 transmits the confirmation information received from the card company server 60 to the store device 30 or the virtual store server 40. If the confirmation information indicates that there is no problem in executing the payment, the store device 30 issues a receipt indicating the amount used. Furthermore, the payment server 10A provides a benefit to the user device 20 used by the user U according to the conditions of the payment.

[0020] The bank server 70 is a server of a bank used by the payment server 10A when the user U settles the amount of the credit card or the QR code. When the payment server 10A executes the settlement of the amount of the credit card or the QR code, the bank server 70 deducts the amount of the product or service purchased by the user U from the balance of the user U's account. The bank server 70 may deduct the amount of the product or service purchased by the user U from the balance of the user U's account for each settlement in the payment server 10A. Alternatively, the bank server 70 may deduct the total amount of the product or service purchased by the user U after the previous closing date from the balance of the user U's account for each closing date of the credit card or the credit card linked to the QR code.

[0021] In the above description, the operation of each device when the user U purchases a product or service using a credit card has been mainly described. The operation of each device when the user U purchases a product or service using a QR code is as follows.

[0022] In a physical store, the POS register is not linked to the user device 20 and the store device 30. A store clerk at the physical store inputs an amount into the POS system, independent of the store device 30, for sales management. After that, the store clerk inputs the usage amount into the store device 30, and after the usage amount is displayed on the store device 30, the user U causes the user device 20 to display a QR code. The store device 30 reads the QR code. The store device 30 reads the user U's personal identification information from the QR code. The store device 30 that reads the personal identification information transmits transaction information to the management server 50 in the same way as when the user U uses a credit card. The management server 50 and the card company server 60 then transfer the transaction information by performing the same operations as described above. The payment server 10A executes the same confirmation operation as described above. The payment server 10A transmits confirmation information to the card company server 60 and the user device 20. The confirmation information transmitted to the card company server 60 is transmitted to the store device 30 via the management server 50.

[0023] Alternatively, in the case where a board or paper on which a QR code is printed is installed in a brick-and-mortar store, the user U reads the QR code with the user device 20, then inputs the usage amount to the user device 20 and taps the payment button displayed on the user device 20. When the payment button is tapped, the above-mentioned payment information is transmitted from the user device 20 to the payment server 10A. The payment server 10A executes the same confirmation operation as described above. The payment server 10A transmits confirmation information to the card company server 60 and the user device 20. The confirmation information transmitted to the card company server 60 is transmitted to the store device 30 via the management server 50. If the user U inputs an incorrect amount into the user device 20, the user U uses the cancel function to cancel the input amount and then inputs the correct amount.

[0024] 1-1-2: Configuration of payment server 10A Fig. 2 is a block diagram showing a configuration example of the payment server 10A. As shown in Fig. 2, the payment server 10A includes a processing device 11A, a storage device 12A, a communication device 13, a display device 14, and an input device 15. The elements of the payment server 10A are connected to each other by one or more buses for communicating information. Note that the term "apparatus" in this specification may be replaced with other terms such as a circuit, a device, or a unit.

[0025] The processing device 11A is a processor that controls the entire payment server 10A. The processing device 11A is configured, for example, using one or more chips. The processing device 11A is also configured, for example, using a central processing unit (CPU) including an interface with peripheral devices, an arithmetic unit, and a register. Some or all of the functions of the processing device 11A may be realized by hardware such as a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array). The processing device 11A executes various processes in parallel or sequentially.

[0026] The storage device 12A is a recording medium that can be read and written by the processing device 11A. The storage device 12A includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory is, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (Electrically Erasable Programmable Read Only Memory). The volatile memory is, for example, a RAM (Random Access Memory). The storage device 12A also stores a control program PR1A executed by the processing device 11A, a terminal table TTB, a user database UDB[A], and a history database HDB[A]. The storage device 12A also functions as a work area for the processing device 11A.

[0027] FIG. 3 is a diagram showing an example of the configuration of the terminal table TTB. The terminal table TTB is a table that defines the correspondence between the terminal number and the store type. Here, the "terminal number" is a number that identifies the store device 30 and the virtual store server 40. The "store type" is information that indicates the type of the store in which the store device 30 and the virtual store server 40 are installed. In the terminal table TTB exemplified in FIG. 3, as an example, the actual store in which the store device 30 or the virtual store server 40 with the "terminal number" of "00001" is installed is defined as a store of a company called "A Chain". Note that the terminal table TTB exemplified in FIG. 3 stores data showing 999 pairs of correspondence. However, the number of data stored in the terminal table TTB may be any number.

[0028] FIG. 4 is a diagram showing an example of the configuration of the user database UDB[A]. The user database UDB[A] stores information about a plurality of users U of the reward-granting system 1A. The "user ID" in the user database UDB[A] is an identifier for identifying the user U who uses the reward-granting system 1A. The "device number" is a number for identifying the user device 20 used by the user U. The "card number" is the card number of the credit card used by the user U indicated by the "user ID" or the credit card linked to the QR code. The "accumulated usage amount" is the accumulated amount of usage paid by the user U to purchase goods or services from the previous closing date of the credit card to the present time. Every time the user U makes a payment using the credit card or the QR code, a new usage amount is accumulated, and the accumulated usage amount is updated. The "update date" is the date and time when the "accumulated usage amount" was last updated. In other words, the "update date and time" is the date and time when the "accumulated usage amount" became the current amount. The "credit limit" is the credit limit of the credit card having the card number indicated by the "card number". In the user database UDB[A], as an example, the "device number" of the user device 20 used by the user U with the "user ID" of "0001" is "41528", the "card number" of the credit card is "37562987", the "accumulated usage amount" at the present time is "295,000" yen, the "accumulated usage amount" was updated at "12:26:30 on August 18, 2023", and the "credit limit" of the credit card with the "card number" of "37562987" is "500,000" yen. Data is stored. The user database UDB[A] illustrated in FIG. 4 stores 999 sets of data. However, the number of data sets stored in the user database UDB[A] may be any number.

[0029] FIG. 5 is a diagram showing an example of the configuration of the history database HDB[A]. The history database HDB[A] stores information about the settlement of the usage amount paid by a plurality of users U of the reward granting system 1A to purchase a product or service using a credit card or a QR code. The information includes a part of the transaction information acquired from the card company server 60. The "user ID" in the history database HDB[A] is an identifier for identifying the user U who uses the reward granting system 1A. The "card number" is the card number of the credit card used by the user U indicated by the "user ID" or the credit card linked to the QR code. The "terminal number" is the terminal number of the store device 30 or the virtual store server 40 installed in the real store where the user U indicated by the "user ID" uses the credit card or the QR code. The "store type" is the type of the real store or the virtual store where the user U indicated by the "user ID" uses the credit card or the QR code. The "usage amount" is the amount of the price paid when the user U indicated by the "user ID" purchases a product or service using a credit card or a QR code. The "payment date and time" is the date and time when the amount indicated by the "usage amount" was paid. The "flag" is information about the payment process itself using each credit card or QR code. A "flag" of "0" indicates that the payment request has not yet been processed. A "flag" of "1" indicates that the payment was made without any problems. A "flag" of "2" indicates that the payment was attempted but was not made. In the user database UDB[A], as an example, a user U with a "user ID" of "0001" uses a credit card with a "card number" of "37562987" at a brick-and-mortar store with a "store type" of "A chain" and a store device 30 with a "terminal number" of "0346" to pay an amount of "usage amount" of "30,000" yen at a "usage date and time" of "December 26, 2023 30 seconds" at "August 18, 2023", and data indicating that the payment was made without any problems is stored. Among these items, information indicating the "user ID," "card number," "terminal number," "store type," and "amount used" included in the transaction information is referred to as "payment information." In addition, the history database HDB[A] may also include other items not shown in FIG. 5, such as the date and time of credit card usage, the type of currency used for payment, and information indicating the area in which the store device 30 or virtual store server 40 is installed.

[0030] In Fig. 2, the communication device 13 is hardware as a transmitting / receiving device for communicating with other devices. The communication device 13 is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 13 may include a connector for wired connection and an interface circuit corresponding to the connector. The communication device 13 may also include a wireless communication interface. Examples of the connector and interface circuit for wired connection include products that comply with wired LAN, IEEE1394, and USB. Examples of the wireless communication interface include products that comply with wireless LAN, Bluetooth (registered trademark), etc.

[0031] The display device 14 is a device that displays images and text information. The display device 14 displays various images under the control of the processing device 11A. For example, various display panels such as a liquid crystal display panel and an organic EL display panel are suitably used as the display device 14.

[0032] The input device 15 is a device that accepts operations from an administrator of the payment server 10A. For example, the input device 15 includes a keyboard, a touch pad, a touch panel, or a pointing device such as a mouse. Here, when the input device 15 includes a touch panel, it may also function as the display device 14.

[0033] The processing device 11A functions as an acquisition unit 111A, a settlement unit 112, a comparison unit 113A, an extraction unit 114, and a notification unit 115 by reading and executing the control program PR1A from the storage device 12A.

[0034] The acquisition unit 111A acquires transaction information from the card company server 60. The transaction information is information generated by the user device 20, the store device 30, or the virtual store server 40. As described above, the transaction information includes information indicating the amount of use related to electronic payment using a credit card or a QR code, a user ID for identifying the user U, the card number of the credit card, the expiration date of the credit card, the terminal number of the store device 30 or the virtual store server 40, the type of currency used for payment, and the area in which the store device 30 or the virtual store server 40 is installed. The acquisition unit 111A acquires information indicating the store type by collating information indicating the terminal number of the store device 30 or the virtual store server 40 among these with the terminal table TTB. Furthermore, the acquisition unit 111A stores payment information indicating at least the user ID, the card number of the credit card, the terminal number, the store type, and the amount of use in the history database HDB[A].

[0035] The settlement unit 112 settles the usage amount included in the settlement information in the history database HDB[A]. Specifically, the settlement unit 112 first derives information indicating the accumulated usage amount and the credit limit corresponding to the card number by checking the card number included in the settlement information against the user database UDB[A]. Next, the settlement unit 112 determines whether the amount obtained by adding the usage amount included in the settlement information to the accumulated usage amount does not exceed the credit limit. If the amount does not exceed the credit limit, the settlement unit 112 settles the above-mentioned usage amount. The settlement unit 112 writes information indicating the date and time of settlement in the settlement server 10A in the "settlement date and time" column associated with the above-mentioned settlement information in the history database HDB[A], and rewrites the "flag" to 1. Furthermore, the settlement unit 112 generates confirmation information indicating that the settlement has been completed without any problems.

[0036] On the other hand, if the sum of the usage amount included in the payment information and the cumulative usage amount exceeds the credit limit, the payment unit 112 generates confirmation information indicating that the payment was not successful.

[0037] Alternatively, if the amount of use does not exceed the credit limit, the settlement unit 112 further transmits information indicating the amount of use included in the settlement information to the bank server 70. The bank server 70 withdraws the amount from the bank account corresponding to the card number included in the settlement information. If the bank server 70 is able to withdraw the amount, the bank server 70 transmits information indicating that the settlement has been completed to the settlement server 10A. When the settlement server 10A receives the information, the settlement unit 112 writes information indicating the date and time of settlement at the bank server 70 in the "date and time of settlement" field associated with the above-mentioned settlement information in the history database HDB[A], and rewrites the "flag" to 1. Furthermore, the settlement unit 112 generates confirmation information indicating that the settlement has been completed without any problems.

[0038] On the other hand, if the amount used included in the payment information plus the cumulative amount used exceeds the credit limit, and if the bank server 70 is unable to debit the amount from the bank account corresponding to the card number included in the payment information, the payment unit 112 generates confirmation information indicating that the payment could not be made.

[0039] The comparison unit 113A compares the amounts of use indicated by the payment completion information, which is payment information for which payment has been completed within a predetermined period, among the payment information stored in the history database HDB[A]. In the example shown in FIG. 5, the payment completion information is information for which the flag associated with the payment information is set to "1". The above-mentioned "predetermined period" is, for example, 10 seconds. Specifically, the amounts of use indicated by the payment completion information for which payment has been completed between 12:26:00 on August 18, 2023 and 12:26:10 on August 18, 2023 are compared with each other.

[0040] Based on the comparison result in comparison unit 113A, extraction unit 114 extracts a plurality of pieces of payment completion information that satisfy a predetermined condition from the payment completion information in which payments have been completed within a predetermined period.

[0041] FIG. 6 is a diagram illustrating an example of the payment completion information. In the table illustrated in FIG. 6, payment completion information X1 indicates that a user U with a "user ID" of "0687" paid a "usage amount" of "1,000" yen using a credit card with a "card number" of "11765292" to purchase a product or service at a store device 30 with a "terminal number" of "0412" at a physical store with a "store type" of "A chain," and that the payment was completed without any problems. The payment completion information X2 indicates that a user U with a "user ID" of "0024" paid a "usage amount" of "1,000" yen using a credit card with a "card number" of "96251432" to purchase a product or service at a store device 30 with a "terminal number" of "0387" at a physical store with a "store type" of "A chain," and that the payment was completed without any problems. The payment completion information X3 indicates that a user U with a "user ID" of "0451" paid a "usage amount" of "1,005" yen using a credit card with a "card number" of "38125639" to purchase a product or service at a store device 30 with a "terminal number" of "0915" at a physical store with a "store type" of "A chain," and that the payment was completed without any problems. The payment completion information X4 indicates that a user U with a "user ID" of "0143" paid a "usage amount" of "1,100" yen using a credit card with a "card number" of "87138126" to purchase a product or service at a store device 30 with a "terminal number" of "0265" at a physical store with a "store type" of "A chain," and that the payment was completed without any problems. The payment completion information X5 indicates that a user U with a "User ID" of "0376" paid a "Used Amount" of "1,100" yen using a credit card with a "Card Number" of "76289710" to purchase a product or service at a store device 30 with a "Terminal Number" of "0198" at a physical store with a "Store Type" of "B Store", and that the payment was completed without any problems. The payment completion information X6 indicates that a user U with a "User ID" of "0431" paid a "Used Amount" of "1,105" yen using a credit card with a "Card Number" of "40917297" to purchase a product or service at a store device 30 with a "Terminal Number" of "0294" in a physical store with a "Store Type" of "B Store," and that the payment was completed without any problems. The payment completion information X7 indicates that a user U with a "User ID" of "0267" paid a "Used Amount" of "1,005" yen using a credit card with a "Card Number" of "61420834" to purchase a product or service at a store device 30 with a "Terminal Number" of "0492" at a physical store with a "Store Type" of "B Store", and that the payment was completed without any problems.

[0042] The first example of the "predetermined condition" is a condition in which the amount of use is the same, but the store type does not matter whether it is the same or not. In this case, the extraction unit 114 extracts each of the pair of payment completion information X1 and payment completion information X2, the pair of payment completion information X3 and payment completion information X7, and the pair of payment completion information X4 and payment completion information X5.

[0043] The second example of the above-mentioned "predetermined condition" is a condition in which the difference in the amount of use is within a predetermined amount, and whether or not the store type matches is not important. If the predetermined amount is 10 yen, the extraction unit 114 extracts each of the sets of payment completion information X1, payment completion information X2, payment completion information X3, and payment completion information X7, and the sets of payment completion information X4, payment completion information X5, and payment completion information X6.

[0044] A third example of the above-mentioned "predetermined condition" is a condition in which both the amount used and the store type match. In this case, the extraction unit 114 extracts a set of the payment completion information X1 and the payment completion information X2.

[0045] The fourth example of the above-mentioned "predetermined condition" is a condition that the difference in the amount of use is within a predetermined amount and the store type is the same. When the predetermined amount is 10 yen, the extraction unit 114 extracts each of a set of payment completion information X1, payment completion information X2, and payment completion information X3, and a set of payment completion information X5 and payment completion information X6.

[0046] 2, the notification unit 115 notifies the in-store device 30 of the above-mentioned confirmation information via the communication device 13, through the card company server 60 and the management server 50. The confirmation information includes payment completion information or information indicating that payment could not be made. The payment completion information is information that indicates to the store clerk using the in-store device 30 that electronic payment has been completed. When the in-store device 30 is notified of the payment completion information, it issues a receipt indicating the amount used that is included in the payment completion information.

[0047] Furthermore, the notification unit 115 notifies, via the communication device 13, the plurality of user devices 20 that correspond one-to-one to the plurality of pieces of payment completion information extracted by the extraction unit 114 of benefit information that indicates a benefit.

[0048] When the above-mentioned "specified condition" is a first example, the notification unit 115 notifies the user device 20 used by each of the user U whose "user ID" included in the payment completion information X1 is "0687", the user U whose "user ID" included in the payment completion information X2 is "0024", the user U whose "user ID" included in the payment completion information X3 is "0451", the user U whose "user ID" included in the payment completion information X4 is "0143", the user U whose "user ID" included in the payment completion information X5 is "0376", and the user U whose "user ID" included in the payment completion information X7 is "0267", of the bonus information.

[0049] When the above-mentioned "specified condition" is the second example, the notification unit 115 notifies the user device 20 used by each of the user U whose "user ID" included in the payment completion information X1 is "0687", the user U whose "user ID" included in the payment completion information X2 is "0024", the user U whose "user ID" included in the payment completion information X3 is "0451", the user U whose "user ID" included in the payment completion information X4 is "0143", the user U whose "user ID" included in the payment completion information X5 is "0376", the user U whose "user ID" included in the payment completion information X6 is "0431", and the user U whose "user ID" included in the payment completion information X7 is "0267", of the privilege information.

[0050] When the above-mentioned “specified condition” is the third example, the notification unit 115 notifies the user device 20 used by each of the user U whose “user ID” included in the payment completion information X1 is “0687” and the user U whose “user ID” included in the payment completion information X2 is “0024”, of the bonus information.

[0051] When the above-mentioned "specified condition" is the fourth example, the notification unit 115 notifies the user device 20 used by each of the user U whose "user ID" included in the payment completion information X1 is "0687", the user U whose "user ID" included in the payment completion information X2 is "0024", the user U whose "user ID" included in the payment completion information X3 is "0451", the user U whose "user ID" included in the payment completion information X5 is "0376", and the user U whose "user ID" included in the payment completion information X6 is "0431", of the bonus information.

[0052] The notification unit 115 may simultaneously notify the user device 20 of the benefit information and the payment completion information. The payment completion information is information indicating to the user U of the user device 20 that the electronic payment has been completed.

[0053] Furthermore, the notification unit 115 may notify the above-mentioned special offer information to a plurality of store devices 30 or virtual store servers 40 that correspond one-to-one to the plurality of pieces of payment completion information, instead of to a plurality of user devices 20 that correspond one-to-one to the plurality of pieces of payment completion information, by passing the special offer information via the communication device 13 through the card company server 60 and the management server 50. For the sake of simplicity, the following description will be given of a case in which the notification unit 115 notifies special offer information to a plurality of store devices 30 that correspond one-to-one to the plurality of pieces of payment completion information.

[0054] When the above-mentioned "specified condition" is a first example, the notification unit 115 notifies each of the following store devices 30 whose "terminal number" included in the payment completion information X1 is "0412", whose "terminal number" included in the payment completion information X2 is "0387", whose "terminal number" included in the payment completion information X3 is "0915", whose "terminal number" included in the payment completion information X4 is "0265", whose "terminal number" included in the payment completion information X5 is "0198", and whose "terminal number" included in the payment completion information X7 is "0492", of the bonus information.

[0055] When the above-mentioned "specified condition" is the second example, the notification unit 115 notifies the special offer information to each of the store devices 30 whose "terminal number" included in the payment completion information X1 is "0412", the store devices 30 whose "terminal number" included in the payment completion information X2 is "0387", the store devices 30 whose "terminal number" included in the payment completion information X3 is "0915", the store devices 30 whose "terminal number" included in the payment completion information X4 is "0265", the store devices 30 whose "terminal number" included in the payment completion information X5 is "0198", the store devices 30 whose "terminal number" included in the payment completion information X6 is "0294", and the store devices 30 whose "terminal number" included in the payment completion information X7 is "0492".

[0056] When the above-mentioned "specified condition" is the third example, the notification unit 115 notifies the store device 30 whose "terminal number" included in the payment completion information X1 is "0412" and the store device 30 whose "terminal number" included in the payment completion information X2 is "0387", of the bonus information.

[0057] When the above-mentioned "specified condition" is the fourth example, the notification unit 115 notifies the store device 30 whose "terminal number" included in the payment completion information X1 is "0412", whose "terminal number" included in the payment completion information X2 is "0387", whose "terminal number" included in the payment completion information X3 is "0915", whose "terminal number" included in the payment completion information X5 is "0198", and whose "terminal number" included in the payment completion information X6 is "0294", of the bonus information.

[0058] Furthermore, when the notification unit 115 notifies the multiple in-store devices 30 that correspond one-to-one to the multiple pieces of payment completion information of the special offer information, each of the multiple in-store devices 30 may issue a coupon corresponding to the special offer based on the special offer information. Specifically, each of the multiple in-store devices 30 may issue a receipt on which the coupon is printed in parallel with the notification of the special offer information, simultaneously with the notification, or after the notification.

[0059] The notification unit 115 may notify the in-store device 30 of the benefit information and the payment completion information at the same time.

[0060] Furthermore, the notification unit 115 may notify both the user device 20 and the in-store device 30 of the benefit information. Furthermore, the notification unit 115 may notify both the user device 20 and the in-store device 30 of the benefit information and the payment completion information at the same time.

[0061] 1-1-3: Configuration of user device 20 Fig. 7 is a block diagram showing a configuration example of the user equipment 20. As shown in Fig. 7, the user equipment 20 includes a processing device 21, a storage device 22, a communication device 23, a display device 24, and an input device 25. The elements of the user equipment 20 are connected to each other by one or more buses for communicating information. Note that the term "apparatus" in this specification may be replaced with other terms such as a circuit, a device, or a unit.

[0062] The processing device 21 is a processor that controls the entire user device 20. The processing device 21 is configured, for example, using one or more chips. The processing device 21 is also configured, for example, using a central processing unit (CPU) including an interface with peripheral devices, an arithmetic unit, and a register. Some or all of the functions of the processing device 21 may be realized by hardware such as a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). The processing device 21 executes various processes in parallel or sequentially.

[0063] The storage device 22 is a recording medium that can be read and written by the processing device 21. The storage device 22 includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory is, for example, a Read Only Memory (ROM), an Erasable Programmable Read Only Memory (EPROM), and an Electrically Erasable Programmable Read Only Memory (EEPROM). The volatile memory is, for example, a Random Access Memory (RAM). The storage device 22 also stores a control program PR2 executed by the processing device 21. The storage device 22 also functions as a work area for the processing device 21.

[0064] The communication device 23 is hardware as a transmitting / receiving device for communicating with other devices. The communication device 23 is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 23 may include a connector for wired connection and an interface circuit corresponding to the connector. The communication device 23 may also include a wireless communication interface. Examples of the connector and interface circuit for wired connection include products that comply with wired LAN, IEEE1394, and USB. Examples of the wireless communication interface include products that comply with wireless LAN, Bluetooth (registered trademark), etc.

[0065] The display device 24 is a device that displays images and text information. The display device 24 displays various images under the control of the processing device 21. For example, various display panels such as a liquid crystal display panel and an organic EL display panel are suitably used as the display device 24.

[0066] The input device 25 is a device that accepts operations from the user U. For example, the input device 25 includes a keyboard, a touch pad, a touch panel, or a pointing device such as a mouse. Here, when the input device 25 includes a touch panel, it may also function as the display device 24.

[0067] The processing device 21 functions as an acquisition unit 211 and a display control unit 212, for example, by reading out a control program PR2 from the storage device 22 and executing it.

[0068] The acquisition unit 211 acquires the privilege information from the payment server 10A via the communication device 23. The acquisition unit 211 may also acquire payment completion information from the payment server 10A at the same time as the privilege information.

[0069] The display control unit 212 causes the display device 24 to display the benefit indicated by the benefit information acquired by the acquisition unit 211. When the acquisition unit 211 acquires payment completion information simultaneously with the benefit information, the display control unit 212 may cause the display device 24 to display the acquired payment completion information. The payment completion information includes the above-mentioned usage amount.

[0070] 1-2: Operation of the First Embodiment 1-2-1: Operation at the time of payment FIG. 8 is a sequence diagram of the privilege granting system 1A according to the first embodiment at the time of payment.

[0071] In step S1, the in-store device 30 transmits transaction information to the management server 50. The management server 50 receives the transaction information from the in-store device 30.

[0072] In step S2, the management server 50 transmits the transaction information to the card company server 60. The card company server 60 receives the transaction information from the management server 50.

[0073] In step S3, the card company server 60 transmits transaction information to the payment server 10A. The payment server 10A receives the transaction information from the card company server 60. In the payment server 10A, the processing device 11A functions as an acquisition unit 111A. The processing device 11A stores the payment information included in the transaction information in the history database HDB[A].

[0074] In step S4, the processing device 11A included in the payment server 10A functions as the payment unit 112. The processing device 11A settles the usage amount included in the payment information in the history database HDB[A]. If the payment is completed without any problems, the processing device 11A generates confirmation information indicating that the payment has been completed without any problems. The confirmation information includes payment completion information. On the other hand, if the payment is not completed, the payment unit 112 generates confirmation information indicating that the payment has not been completed.

[0075] In step S5, the payment server 10A transmits confirmation information to the card company server 60. The card company server 60 receives the confirmation information from the payment server 10A.

[0076] In step S6, the card company server 60 transmits confirmation information to the management server 50. The management server 50 receives the confirmation information from the card company server 60.

[0077] In step S7, the management server 50 transmits confirmation information to the in-store device 30. The in-store device 30 receives the confirmation information from the management server 50.

[0078] 1-2-2: Behavior when bonus is granted FIG. 9 is a flowchart showing a process of the payment server 10A included in the privilege granting system 1A according to the first embodiment when granting a privilege.

[0079] In step S11, the processing device 11A functions as an acquisition unit 111A. The processing device 11A acquires payment information including amount information indicating the amount used for electronic payment and identification information identifying the user of the electronic payment, generated by each of the multiple user devices 20 or the store device 30. Note that step S11 corresponds to step S3 in the sequence diagram of FIG. 6.

[0080] In step S12, the processing device 11A functions as a comparison unit 113A. The processing device 11A compares the amounts of use indicated by the payment completion information of payments completed within a predetermined period among the payment information acquired by the acquisition unit 111A.

[0081] In step S13, the processing device 11A functions as the extraction unit 114. The processing device 11A extracts a plurality of pieces of payment completion information that satisfy a predetermined condition from the payment completion information in which payments have been completed within a predetermined period, based on the comparison result in step S12.

[0082] In step S14, the processing device 11A functions as the notification unit 115. The processing device 11A notifies the user devices 20 or the store devices 30, which correspond one-to-one to the payment completion information extracted in step S13, of benefit information indicating a benefit via the communication device 13.

[0083] 1-3: Advantages of the First Embodiment The payment server 10A as a privilege granting device according to this embodiment includes an acquisition unit 111A, a comparison unit 113A, an extraction unit 114, and a notification unit 115. The acquisition unit 111A acquires payment information including amount information indicating the amount of use related to electronic payment and identification information identifying the user of electronic payment, generated by each of the multiple user devices 20 or the store device 30. The comparison unit 113A compares the amounts of use indicated by the payment completion information in which the payment was completed within a predetermined period among the payment information acquired by the acquisition unit 111A. The extraction unit 114 extracts multiple payment completion information satisfying a predetermined condition from the payment completion information in which the payment was completed within a predetermined period based on the comparison result of the comparison unit 113A. The notification unit 115 notifies the multiple user devices 20 or the store devices 30 corresponding one-to-one to the multiple payment completion information extracted by the extraction unit 114 of privilege information indicating a privilege via the communication device 13.

[0084] As a result, the payment server 10A can provide a benefit to the user U in the electronic payment service by taking into account an element of chance, without using a lottery.

[0085] More specifically, the payment server 10A awards a reward just by comparing the payment amounts, and therefore the lottery process for awarding the reward can be omitted, thereby reducing the processing load related to the awarding of the reward. Furthermore, the payment server 10A can award a reward when a payment within a predetermined period satisfies a predetermined condition, so that the reward is awarded based on the actions of at least two people. Therefore, in order to award a reward, it is necessary that at least two people have made a payment within a predetermined period, and that the payment completion information satisfies the predetermined condition. A user can know the payment date and time and the payment amount of his / her own payment, but cannot know the payment date and the payment amount of another user's payment. Therefore, the above-mentioned electronic payment service encourages the use of electronic payment while taking into account the element of chance.

[0086] In addition, in the payment server 10A, the above-mentioned specified condition is that the payment completion information to be compared is payment completion information containing amount information in which the amount used is the same, or that the payment completion information to be compared is payment completion information containing amount information indicating a payment amount in which the difference in the payment amount indicated by the amount information contained in the payment completion information to be compared is less than a specified value.

[0087] As a result, a bonus is awarded when the payment amounts are the same or when the difference in the payment amounts is less than a specified value. Therefore, compared to when the specified condition is limited to the payment amounts being the same, the payment server 10A is able to expand the scope of payments for which a bonus is awarded while taking into account the element of chance.

[0088] In addition, in the payment server 10A, the above-mentioned payment completion information includes store information indicating the type of store that uses electronic payment. The comparison unit 113A compares payment completion information in which the type of store indicated by the store information included in the payment completion information is a predetermined store, among the payment completion information in which the payment has been completed within a predetermined period.

[0089] As a result, the payment server 10A can use the type of store as a condition for providing a benefit, and the benefit provided by the payment server 10A can be used for, for example, a campaign of a chain store. In addition, the payment server 10A limits the comparison target of the comparison unit 113A to payments made at a specific store, thereby reducing the processing load of the comparison unit 113A.

[0090] In addition, in the payment server 10A, the notification unit 115 simultaneously notifies the special benefit information and payment completion information indicating that the electronic payment has been completed.

[0091] As a result, the payment completion information and the benefit information are notified at the same time, so that the user device 20 or the store device 30 as a terminal device can recognize the completion of the electronic payment and the granting of the benefit without any time lag. Note that "at the same time" means a single notification. Therefore, when the benefit information and the payment completion information are included in a single notification, the benefit information and the payment completion information are notified at the same time.

[0092] The reward granting system 1A according to this embodiment includes the above-mentioned payment server 10A and a plurality of in-store devices 30 installed in a plurality of stores. The in-store device 30 issues a coupon corresponding to the reward based on the reward information.

[0093] As a result, the reward granting system 1A can grant a reward by a coupon issued by a store device 30 such as a POS register.

[0094] The reward granting system 1A according to this embodiment includes the payment server 10A and a plurality of user devices 20 owned by users of electronic payment. The user device 20 includes a display device 24 for displaying images, and displays rewards indicated by reward information on the display device 24.

[0095] As a result, the privilege granting system 1A can notify the user U that a privilege has been granted by notifying the user device 20 of the electronic coupon or point information.

[0096] 2: Second embodiment Hereinafter, a privilege granting system 1B according to the second embodiment will be described with reference to Figs. 10 to 12. For the sake of simplicity, the following mainly describes the differences between the privilege granting system 1B and the privilege granting system 1A. Furthermore, among the components of the privilege granting system 1B, the same components as those of the privilege granting system 1A are designated by the same reference numerals, and the description of their functions may be omitted.

[0097] The reward granting system 1A of the first embodiment grants a reward by checking the payment completion information of an arbitrary user U in the payment server 10A. In contrast, the reward granting system 1B of the second embodiment differs from the reward granting system 1A of the first embodiment in that the reward is granted by checking the payment completion information of a specific user U with the payment completion information of another user U. Here, the "specific user U" is, for example, a celebrity.

[0098] By setting a specific user U as a famous person such as an influencer or entertainer, a bonus is awarded to the user U who purchases the same amount as the celebrity. Therefore, the bonus awarding system 1A can not only award a bonus to the general user U, but also give the general user U the satisfaction of having made a purchase together with the celebrity.

[0099] 2-1: Configuration of the second embodiment 2-1-1: Overall structure The overall configuration of the reward granting system 1B according to the second embodiment differs from the reward granting system 1A shown in Fig. 1 in that a payment server 10B is provided instead of the payment server 10A. In other respects, the overall configuration of the reward granting system 1B is the same as the overall configuration of the reward granting system 1A shown in Fig. 1, and therefore is not illustrated.

[0100] 2-1-2: Configuration of payment server 10B Fig. 10 is a block diagram showing a configuration example of the payment server 10B. As shown in Fig. 10, the payment server 10B differs from the payment server 10A in that it includes a processing device 11B instead of the processing device 11A and a storage device 12B instead of the storage device 12A.

[0101] The memory device 12B differs from the memory device 12A provided in the payment server 10A in that it has a control program PR1B instead of the control program PR1A, a user database UDB[B] instead of the user database UDB[A], and a history database HDB[B] instead of the history database HDB[A].

[0102] FIG. 11 is a diagram showing an example of the configuration of the user database UDB[B]. Comparing the configuration of the user database UDB[B] with the user database UDB[A], the user database UDB[B] is different in that it has a "flag" as an additional item. The "flag" is a flag indicating whether or not the user U is the above-mentioned "predetermined user U." If the user U indicated by the "user ID" is the predetermined user U, the "flag" is "1." On the other hand, if the user U indicated by the "user ID" is not the predetermined user U, the "flag" is "0." In the example shown in FIG. 11, the user U with the "user ID" of "0002" is the predetermined user U, so the "flag" is "1." The other users U are not the predetermined users U, so the "flag" is "0."

[0103] FIG. 12 is a diagram showing an example of the configuration of the history database HDB[B]. Comparing the configuration of the history database HDB[B] with the history database HDB[A], the history database HDB[B] differs in that it has two items, a "first flag" and a "second flag", instead of the item "flag" of the history database HDB[A]. The "first flag", like the "flag" of the history database HDB[A], is information about the payment process itself by each credit card or QR code. A "flag" of "0" indicates that the payment request has not yet been processed. A "flag" of "1" indicates that the payment was made without any problems. A "flag" of "2" indicates that the payment was attempted but could not be made. The "second flag", like the "flag" of the user database UDB[B] shown in FIG. 11, is a flag indicating whether the user is the above-mentioned "predetermined user U". If the user U indicated by the "user ID" is the predetermined user U, the "flag" is "1". On the other hand, if the user U indicated by the "user ID" is not the predetermined user U, the "flag" is "0".

[0104] 10, the processing device 11B reads out and executes a control program PR1B from the storage device 12B, thereby functioning as an acquisition unit 111B, a settlement unit 112, a comparison unit 113B, an extraction unit 114, and a notification unit 115. Of these components, the settlement unit 112, the extraction unit 114, and the notification unit 115 have the same functions as the settlement unit 112, the extraction unit 114, and the notification unit 115 in the first embodiment, and therefore the description thereof will be omitted.

[0105] The acquiring unit 111B acquires transaction information from the card company server 60, similar to the acquiring unit 111A. The acquiring unit 111B also acquires information indicating a flag from the information included in the transaction information by checking the user ID against the user database UDB[B]. Furthermore, the acquiring unit 111B stores at least the user ID, credit card number, terminal number, store type, amount used, and payment information indicating the flag in the history database HDB[B]. The information indicating the above-mentioned flag is stored in the "second flag" item of the history database HDB[B].

[0106] Based on the "second flag" in the history database HDB[B], the comparison unit 113B identifies payment completion information in which the user U indicated by the user ID is a specific user U. Next, the comparison unit 113B compares the identified payment completion information with other payment completion information. This allows the payment completion information of the specific user U to be matched with the payment completion information of the other users U.

[0107] Here, the comparison unit 113B may treat payment completion information including store information indicating the same store type as the store type indicated by the store information included in the specified payment completion information as the above-mentioned "other payment completion information." For example, if a celebrity makes a purchase in the "A Chain," the payment completion information to be compared with the celebrity's payment completion information is limited to payment completion information for electronic payments made in the "A Chain."

[0108] Alternatively, the comparison unit 113B may further set the payment completion information including the usage amount indicating the same amount as the usage amount included in the specified payment completion information as the above-mentioned "other payment completion information." For example, if a celebrity electronically pays for a usage fee of "1,000" yen in the "A chain," the payment completion information to be compared with the celebrity's payment completion information is limited to the payment completion information in which the usage fee of "1,000" yen in the "A chain" is electronically paid.

[0109] 2-2: Operation of the second embodiment 2-2-1: Operation at the time of payment The operation of the privilege granting system 1B according to the second embodiment at the time of payment is similar to the operation of the privilege granting system 1A according to the first embodiment shown in FIG. 8 at the time of payment, and therefore illustration and description thereof will be omitted.

[0110] 2-2-2: Behavior when bonus is granted The operation of the payment server 10B included in the bonus-granting system 1B of the second embodiment when granting a bonus is similar to the operation of the payment server 10A included in the bonus-granting system 1A of the first embodiment when granting a bonus shown in Figure 9, except for the following points, so it is not shown in the figure.

[0111] In step S12, the processing device 11B functions as a comparison unit 113B. The processing device 11B identifies payment completion information in which the user U indicated by the user ID is a specific user U, and compares the usage amount of the identified payment completion information with the usage amount of other payment completion information.

[0112] 2-3: Advantages of the Second Embodiment In the payment server 10B according to this embodiment, the payment completion information includes a user ID that identifies a user U of the electronic payment. The comparison unit 113B identifies payment completion information in which the user U indicated by the user ID is a specific user U. The comparison unit 113B also compares the usage amount of the identified payment completion information with the usage amount of other payment completion information.

[0113] As a result, the payment server 10B compares the payment completion information of the specific user U with the other payment completion information, and therefore can provide a benefit to the other users U in conjunction with the payment of the specific user U.

[0114] Furthermore, in the payment server 10B, the payment completion information includes a user ID that identifies the user U of the electronic payment and store information that indicates the type of store where the electronic payment is used. The comparison unit 113B identifies payment completion information in which the user U identified by the user ID is a specific user U. Furthermore, the comparison unit 113B compares the usage amount of the payment completion information including store information indicating the same store type as the store type indicated by the store information included in the identified payment completion information with the usage amount of the identified payment completion information.

[0115] As a result, the payment server 10B can limit the granting of the benefit to cases where payment is made at the same type of store as the type of store where a specific user U, such as a celebrity, made payment, making it possible for the user U to be granted the benefit to feel as if he or she has behaved in the same way as the specific user U.

[0116] 3: Variations The present disclosure is not limited to the above-described embodiments. Specific modified embodiments are exemplified below.

[0117] 3-1: Variation 1 13 is a block diagram showing the overall configuration of a reward granting system 1C according to this modified example. Unlike the reward granting systems 1A and 1B, the reward granting system 1C does not include a management server 50 and a card company server 60. In the reward granting system 1C, the store device 30 or the virtual store server 40 directly transmits transaction information to the payment server 10A or 10B. In addition, the payment server 10A or 10B directly transmits confirmation information to the store device 30 or the virtual store server 40.

[0118] 4:Other (1) In the above-described embodiment, ROM and RAM are given as examples of storage device 12A, storage device 12B, and storage device 22, but the storage devices may be flexible disks, magneto-optical disks (e.g., compact disks, digital versatile disks, Blu-ray (registered trademark) disks), smart cards, flash memory devices (e.g., cards, sticks, key drives), CD-ROMs (Compact Disc-ROMs), registers, removable disks, hard disks, floppy (registered trademark) disks, magnetic strips, databases, servers, or other suitable storage media.

[0119] (2) In the above-described embodiments, the described information, signals, etc. may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0120] (3) In the above-described embodiment, the input / output information, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. The input / output information, etc. may be overwritten, updated, or added. The output information, etc. may be deleted. The input information, etc. may be transmitted to another device.

[0121] (4) In the above-described embodiments, the determination may be made based on a value represented using one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0122] (5) The order of the process steps, sequences, flow charts, etc. illustrated in the above-described embodiments may be changed without causing any inconsistency. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0123] (6) Each function illustrated in Fig. 1 to Fig. 13 is realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional block may be realized by combining the one device or the multiple devices with software.

[0124] (7) The programs exemplified in the above-described embodiments should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether they are called software, firmware, middleware, microcode, hardware description language, or by other names.

[0125] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired and / or wireless technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0126] (8) In each of the above embodiments, the terms “system” and “network” are used interchangeably.

[0127] (9) The information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information.

[0128] (10) In the above-described embodiment, the user device 20 and the store device 30 may be a mobile station (MS). A mobile station may be referred to by those skilled in the art as a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other appropriate term. In the present disclosure, the terms "mobile station", "user terminal", "user equipment (UE)", "terminal", etc. may be used interchangeably.

[0129] (11) In the above-mentioned embodiments, the terms "connected" and "coupled" or any variation thereof refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be a physical coupling or connection, a logical coupling or connection, or a combination thereof. For example, "connected" may be read with "access". As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and light (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0130] (12) In the above embodiments, the phrase "based on" does not mean "based only on," unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0131] (13) The terms "determining" and "determining" as used in this disclosure may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining, and the like. Also, "determining" and "determining" may include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.

[0132] (14) In the above embodiments, when "include," "including," and variations thereof are used, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, the term "or" used in this disclosure is not intended to be an exclusive or.

[0133] (15) In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural.

[0134] (16) In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

[0135] (17) Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to explicit notification, but may be implicit (e.g., not notifying the specific information).

[0136] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is for illustrative purposes only and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0137] 1A, 1B, 1C: privilege granting system, 10A, 10B: payment server, 11A, 11B: processing device, 12A, 12B: storage device, 13: communication device, 14: display device, 15: input device, 20: user device, 21: processing device, 22: storage device, 23: communication device, 24: display device, 25: input device, 30: store device, 40: virtual store server, 50: management server, 60: card company server, 70: bank Row server, 111A, 111B: acquisition unit, 112: settlement unit, 113A, 113B: comparison unit, 114: extraction unit, 115: notification unit, 211: acquisition unit, 212: display control unit, HDB: history database, NET: communication network, PR1A, PR1B, PR2: control program, TTB: terminal table, U: user, UDB: user database, X1, X2, X3, X4, X5, X6, X7: settlement completion information

Claims

1. an acquisition unit that acquires payment information generated by each of a plurality of terminal devices, the payment information including amount information indicating an amount used in relation to the electronic payment and identification information identifying a user of the electronic payment; a comparison unit that compares the amounts of use indicated by the payment completion information of the payment information acquired by the acquisition unit, the amounts of use indicated by the payment completion information of the payment information of the payment completed within a predetermined period; an extraction unit that extracts a plurality of pieces of payment completion information that satisfy a predetermined condition from the payment completion information in which the payment was completed during the predetermined period based on a comparison result of the comparison unit; a notification unit that notifies, via a communication device, a plurality of terminal devices that correspond one-to-one to the plurality of pieces of payment completion information extracted by the extraction unit of benefit information indicating a benefit; A privilege granting device comprising:

2. The predetermined condition is: The payment completion information to be compared is payment completion information containing the same amount information as the usage amount indicated by the amount information contained in the payment completion information; Alternatively, the payment completion information includes amount information indicating a payment amount in which the difference between the payment amount indicated by the amount information included in the payment completion information to be compared is equal to or less than a predetermined value. The reward granting device according to claim 1 .

3. The payment completion information includes store information indicating a type of store where the electronic payment is used, the comparison unit compares payment completion information, among the payment completion information in which the payment has been completed during the specified period, with the type of store indicated by the store information included in the payment completion information being a specified store; The bonus granting device according to claim 2 .

4. The payment completion information includes identification information for identifying a user of the electronic payment, The comparison unit is Identifying payment completion information indicating that the user indicated by the identification information is a specified user, comparing the usage amount of the identified payment completion information with the usage amount of other payment completion information; The bonus granting device according to claim 2 .

5. The payment completion information includes identification information for identifying a user of the electronic payment and store information indicating a type of store using the electronic payment, The comparison unit is Identifying payment completion information indicating that the user indicated by the identification information is a specified user, comparing the usage amount of the specified payment completion information with the usage amount of the payment completion information including store information indicating the same store type as the store type indicated by the store information included in the specified payment completion information; The bonus granting device according to claim 4.

6. The privilege granting device according to claim 1 , wherein the notification unit simultaneously notifies the privilege information and payment completion information indicating that the electronic payment has been completed.

7. A reward giving system comprising the reward giving device according to claim 1 and the plurality of terminal devices, each of the plurality of terminal devices is a store device installed in a store; The in-store device issues a coupon corresponding to the benefit based on the benefit information. Reward system.

8. A reward giving system comprising the reward giving device according to claim 1 and the plurality of terminal devices, each of the plurality of terminal devices is a user device owned by a user of electronic payment; The user device comprises: A display device for displaying an image is provided, displaying the benefit indicated by the benefit information on the display device; Reward system.

Images