JP7395786B1 - Information processing device, information processing method, and information processing program - Google Patents

Abstract

An object of the present invention is to provide an information processing device, an information processing method, and an information processing program that can efficiently manage benefits. An information processing device according to the present application includes a storage section and a control section. The storage unit stores, for each of a plurality of facilities where the same benefit can be used, a benefit ID that identifies the benefit, a payment destination ID that identifies the payment destination when making payments to the facility, and a facility that identifies each facility. A database is stored that includes individual data that is linked to an ID, and common data that is linked to a benefit ID, a payment destination ID, and a common facility ID that is common to a plurality of facilities. The control unit determines, based on common data in the database, whether benefits are applicable to payments made using user terminals at each of the plurality of facilities. [Selection diagram] Figure 2

Description

The present invention relates to an information processing device, an information processing method, and an information processing program.

2. Description of the Related Art Conventionally, there has been known a technique for granting a predetermined benefit to a user who purchases a predetermined transaction object. As an example of such technology, a user can obtain a discount coupon (hereinafter simply referred to as a coupon) for a given product in advance, and use the coupon when paying at the register. Techniques for making payments have been proposed.

Japanese Patent Application Publication No. 2010-218483

However, with the above-described conventional technology, benefits such as coupons may not be efficiently managed in some cases.

For example, when a product manufactured by a certain manufacturer is sold at multiple stores, coupons for the product are linked to each store. Then, if the coupon acquired by the user is linked to the store where the payment is made, the coupon is applied. For this reason, if there are a large number of stores associated with a coupon, it is necessary to search for a store for payment from among such a large number of stores, and the search process takes time. Additionally, in cases where installation is easy and there is a large upper limit on the number of stores, such as vending machines, store identification information is not issued for each store, but all stores are managed as the same store identification information, and coupons linked to it are issued. However, in this case, it is not possible to link the store identification information with the location information of each store, so there is no way for the user to check where the coupon he/she has acquired can be used. As described above, conventionally, there is room for improvement in efficiently managing benefits such as coupons.

The present application has been made in view of the above, and aims to provide an information processing device, an information processing method, and an information processing program that can efficiently manage benefits.

The information processing device according to the present application includes a storage section and a control section. The storage unit stores, for each of a plurality of facilities where the same benefit can be used, a benefit ID that identifies the benefit, a payment destination ID that identifies a payment destination when making a payment to the facility, and each of the facilities. and common data that links the payment destination ID and a common facility ID common to the plurality of facilities to the benefit ID. do. The control unit determines, based on the common data in the database, whether the benefit is applicable to payment using a user terminal at each of the plurality of facilities.

According to one aspect of the embodiment, it is possible to efficiently manage coupons.

FIG. 1A is a diagram illustrating an example of information processing according to the embodiment. FIG. 1B is a diagram illustrating an example of information processing according to the embodiment. FIG. 1C is a diagram illustrating an example of information processing according to the embodiment. FIG. 2 is a diagram illustrating a configuration example of a payment server according to an embodiment. FIG. 3 is a diagram illustrating an example of a user information database according to the embodiment. FIG. 4 is a diagram illustrating an example of an account database according to the embodiment. FIG. 5 is a diagram illustrating an example of the facility information database according to the embodiment. FIG. 6 is a diagram illustrating an example of a coupon information database according to the embodiment. FIG. 7 is a flowchart illustrating an example of the procedure of coupon registration processing according to the embodiment. FIG. 8 is a flowchart illustrating an example of a payment processing procedure during a user scan according to the embodiment. FIG. 9 is a flowchart illustrating an example of a payment processing procedure during store scanning according to the embodiment. FIG. 10 is a hardware configuration diagram showing an example of a computer that implements the functions of a payment server.

DESCRIPTION OF THE PREFERRED EMBODIMENTS An information processing apparatus, an information processing method, and an information processing program according to the present application (hereinafter referred to as "embodiments") will be described in detail below with reference to the drawings. Note that the information processing apparatus, information processing method, and information processing program according to the present application are not limited to this embodiment. Further, in each of the embodiments below, the same parts are given the same reference numerals, and redundant explanations will be omitted.

[Embodiment]
Information processing realized by the information processing apparatus and the like of this embodiment will be described using FIGS. 1A to 1C. 1A to 1C are diagrams illustrating an example of information processing according to the embodiment. FIG. 1A shows a coupon (an example of a benefit) registration process, FIG. 1B shows a payment process using a user scan, and FIG. 1C shows a payment process using a store scan. Note that in FIGS. 1A to 1C, it is assumed that the information processing and the like according to the embodiment are realized by the payment server 10, which is an example of the information processing apparatus according to the present embodiment.

As shown in FIGS. 1A to 1C, the information processing system 1 according to the embodiment includes a payment server 10, a user terminal 100, a store terminal 200, and an external device 300. The payment server 10, the user terminal 100, the store terminal 200, and the external device 300 are connected to be able to communicate with each other by wire or wirelessly via a network N (for example, see FIG. 10). The network N is, for example, a WAN (Wide Area Network) such as the Internet. Note that the information processing system 1 shown in FIGS. 1A to 1C includes multiple payment servers 10, multiple user terminals 100, multiple store terminals 200, and multiple external devices 300. Good too.

The payment server 10 shown in FIGS. 1A to 1C is an information processing device that executes information processing according to the embodiment, and is realized by a server device, a cloud system, or the like. For example, the payment server 10 provides an electronic payment service regarding electronic payment using the user terminal 100. For example, the payment server 10 manages the accounts of providers (business operators) of transaction objects and users to whom transaction objects are provided, and transfers electronic money between accounts in accordance with payment requests from users. By doing so, various payments can be realized. Note that electronic money may be, for example, points or currency used independently by various companies, or may be currency provided by a country such as Japanese yen or dollars that can be electronically transacted. good.

The payment server 10 also provides coupon information (for example, identification information (transaction object) identifying the transaction object (product) to which the coupon is applied) regarding the coupon that is given to the user in the electronic payment service and that can be used in the electronic payment service. (identification information), the details of the benefits granted to the user by the coupon (such as a predetermined amount of cash back, etc.), the acquisition conditions for the user to obtain the coupon, etc.) It plans, sets, etc., receives coupon funds from the person who invests (provides) them, and manages them in its own device's storage unit. For example, the payment server 10 manages information indicated by a barcode (such as a JAN code or an in-store code) attached to a transaction object as transaction object identification information.

Further, the payment server 10 associates the user with the coupon acquired by the user, and manages the link in the storage unit of its own device.

A user terminal 100 shown in FIGS. 1A to 1C is an information processing device used by a user. The user terminal 100 is realized by, for example, a smartphone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), or the like. Further, the user terminal 100 displays information distributed by the payment server 10 using a web browser or an application. Note that the example shown in FIG. 1 shows a case where the user terminal 100 is a smartphone.

Note that when the user terminal 100 receives control information for realizing predetermined information processing from the payment server 10, the user terminal 100 realizes the information processing according to the control information. Here, the control information is, for example, a script language such as JavaScript (registered trademark), a style sheet language such as CSS (Cascading Style Sheets), a programming language such as Java (registered trademark), or a language such as HTML (Hyper Text Markup Language). It is written in markup language etc. Note that the predetermined application itself distributed from the payment server 10 may be regarded as the control information.

A store terminal 200 shown in FIGS. 1A to 1C is an information processing device built in a facility that provides transactions to users. In this disclosure, a vending machine that unmannedly dispenses foodstuffs and the like will be described as an example of a facility. Note that the facility is not limited to a vending machine, but may be a coin laundry, a lighting camera, or the like. Further, the store terminal 200 may be an information processing device used in a store that provides transactions to users. The store terminal 200 in this case is realized by, for example, a POS (Point of Sales) terminal, a smartphone, a tablet terminal, a notebook PC, a desktop PC, a mobile phone, a PDA, or the like. Further, the store terminal 200 displays information distributed by the payment server 10 using a web browser or an application.

The external device 300 shown in FIGS. 1A to 1C is an information processing device that manages information related to transaction objects provided by the facility, information related to payments made by users to the facility, etc., and includes a server device, a cloud system, etc. This is realized by For example, the external device 300 sends information such as transaction object identification information indicated by the JAN code, transaction object information (name, etc.) linked to the JAN code, transaction object price, etc. to a predetermined server as information regarding the transaction object. (JAN code integrated product information database, etc.), a business terminal used by a business operator that manages a store, etc., and stores the acquired information in the storage unit of its own device. In addition, the external device 300 uses information such as transaction object identification information indicated by an in-store code uniquely assigned by the business operator managing the store, the name of the transaction object, and the price of the transaction object as information regarding the transaction object. It is acquired from the operator terminal used by M1 and stored in the storage unit of its own device. In addition, the external device 300 transmits information such as identification information (payment number) for identifying a payment using the user terminal 100, which will be described later, and transaction object identification information of the transaction object that is the object of the payment, to the user's store. It is received from the store terminal 200 as information regarding the payment made to the store terminal 200, and is stored in the storage section of the own device.

Further, the external terminal 300 performs settings related to coupons according to operations by a setter (not shown). Note that settings related to coupons are performed via a setter terminal (not shown). The configurator terminal is an information processing device used by the configurator. The configurator terminal is realized by, for example, a smartphone, a tablet terminal, a notebook PC, a desktop PC, a mobile phone, a PDA, or the like. Further, the setter terminal displays information distributed by the payment server 10 using a web browser or an application.

Note that when the setter terminal receives control information for implementing predetermined information processing from the payment server 10, it implements the information processing in accordance with the control information. Here, the control information is written in, for example, a script language such as JavaScript (registered trademark), a style sheet language such as CSS, a programming language such as Java (registered trademark), a markup language such as HTML, or the like. Note that the predetermined application itself distributed from the payment server 10 may be regarded as the control information.

[About payment using user terminal 100]
Here, prior to information processing performed by the payment server 10, an example of payment (electronic payment) using the user terminal 100 will be described. In the following explanation, users will be able to Although an example in which payment is made using the user terminal 100 will be described, the embodiment is not limited to this. An example of a payment described below can be applied to a case where any user makes a payment at any store using any user terminal 100. Further, the store identification information may be not only a QR code but also a bar code, a predetermined mark, a number, etc.

For example, when a user makes a payment for using or purchasing a payment object (transaction object) such as various products and services at a store, the user starts a payment application installed in the user terminal 100 in advance. The user then photographs the store identification information installed (or displayed) at the store via the payment application. In such a case, the user terminal 100 displays a screen for inputting the price to be paid, and accepts input of the payment amount from the user or store clerk. The user terminal 100 then stores user identification information that identifies the user, and store identification information (or information indicated by the store identification information, that is, information indicating the store (or store operator) (for example, store ID )) and the payment amount are sent to the payment server 10.

In such a case, the payment server 10 transfers the amount of electronic money indicated by the payment amount from the user's account indicated by the user identification information to the store account indicated by the store identification information. The payment server 10 then sends a notification to the user terminal 100 that the payment has been completed. In such a case, the user terminal 100 notifies that the payment has been made using electronic money by displaying a screen or outputting a predetermined sound indicating that the payment has been completed. Here, the payment server 10 may subtract a predetermined fee (management fee, etc.) from the store's account when transferring the electronic money to the store's account or at a predetermined timing.

A more detailed example will be explained. For example, store identification information installed (or displayed) in a store is a URL set for each store, and includes group identification information that indicates the group to which the store belongs, and group store identification information that identifies the store in that group. The payment server 10 is managed so that it can be referenced. Note that the URL serving as the store identification information is the URL for accessing the payment server 10. When the user terminal 100 photographs the store identification information, it accesses the URL indicated by the photographed store identification information and transmits the user identification information. In such a case, the payment server 10 identifies the group identification information that corresponds to the accessed URL, and stores the electronic money account (which may be displayed as a "wallet") that is linked to the identified group identification information. Identify. Subsequently, the payment server 10 causes the user terminal 100 to display an amount input screen and input the amount. Then, the payment server 10 identifies group identification information from the wallet linked to the user identification information received from the user terminal 50, and inputs the input information to the wallet linked to the identified group identification information. transfer the amount of electronic money. Note that the payment server 10 may transfer the electronic money to a wallet linked to the group identification information and group store identification information.

As mentioned above, store identification information used for payments is normally issued for each store, but in the case of stores such as vending machines and laundromats where the number of stores is limited in a short period of time, each store identification information is issued for each store. Instead of managing store identification information for each store, there is also a management form in which all vending machines are given the same store identification information and managed if the same member store sells vending machines. In this case, even if a new vending machine is installed, the same store identification information can be used without issuing new store identification information, making management easier.

However, in the above case, when issuing a coupon, if one coupon associated with one store identification information is issued, the coupon can be used at all vending machines. However, in this case, when the user wants to check the locations where the acquired coupon can be used from the coupon screen, since there is only one store identification information, multiple addresses cannot be linked and the locations where the coupon can be used cannot be displayed. occurs.

In the present disclosure, the above one store identification information is used for payment, and separately, for example, when displaying a store to the user, store identification information for each store linked to the above one store identification information is used. By managing only internally (the payment server 10), the location of the store can be displayed to the user based on the store identification information for each store. Note that details of this point will be described later.

The above-mentioned payment is also called payment by user scan because the user scans the store code to make the payment. Note that details of the payment process by user scan will be described later with reference to FIG. 1B.

Note that the payment using the user terminal 100 is not limited to the payment processing using the user scan described above. For example, the payment using the user terminal 100 may be made using the store terminal 200. For example, the user terminal 100 displays user identification information for identifying the user on the screen. In such a case, the store terminal 200 reads the user identification information displayed on the user terminal 100, and reads the user identification information (or information indicated by the user identification information, that is, information indicating the user (for example, Information regarding the payment including the user ID)), the payment amount, and information identifying the store is transmitted to the payment server 10. In such a case, the payment server 10 transfers the amount of electronic money indicated by the payment amount from the user's account indicated by the user identification information to the store's account, and transfers the amount of electronic money indicated by the payment amount to the store's store terminal 200 or user terminal 100. However, it may be possible to notify that the payment has been completed by outputting a screen or a predetermined sound indicating that the payment has been completed.

More specifically, the user terminal 100 transmits a payment request to the payment server 10 along with user identification information. In such a case, the payment server 10 generates a one-time code, associates the generated one-time code with user identification information, and transmits the one-time code to the user terminal 50. Then, the user terminal 100 displays a one-time code (ie, information that identifies the user) on the screen. In such a case, upon reading the one-time code displayed on the user terminal 100, the store terminal 200 transmits the read one-time code, group identification information, group store identification information, and payment amount to the payment server 10. . Then, the payment server 10 transfers electronic money equivalent to the payment amount from the wallet linked to the user identification information linked to the one-time code to the wallet linked to the group identification information and group store identification information.

The above-mentioned payment is also called payment by store scan because the store terminal 200 scans the code of the user terminal 100 to make the payment. Note that details of the payment process using store scanning will be described later with reference to FIG. 1C.

Payment using the user terminal 100 is not limited to the process of transferring electronic money from an account to which the user has previously charged electronic money to a store account; for example, payment using the user's pre-registered credit card It may be a payment made in advance. In such a case, for example, the user terminal 100 transfers electronic money for the payment amount to the store's account, and requests the payment amount from the user's credit card management company (card company). Good too.

In addition, the payment using the user terminal 100 is not limited to the process of transferring electronic money from the user's account to the store's account. may be withdrawn, and the amount of cash obtained by subtracting a predetermined fee (management fee, etc.) from the payment amount may be deposited into the store's bank account. In such a case, for example, the payment server 10 manages the payment amount from each user to the store as store sales information, and at a predetermined timing, based on the sales information, stores the sales (sales information) in the store's bank account. Deposit the amount of cash obtained by subtracting a predetermined fee from the total payment amount indicated by .

In addition, if the funds for the coupon used at the time of payment are borne by the store, the payment server 10 will be able to transfer the funds when depositing cash to the store's bank account or transferring electronic money to the store's account. For example, the payment amount may be subtracted from the payment amount in cash and deposited into the bank account, or the payment amount may be deducted from the payment amount in electronic money and transferred to the store's account.

Note that the funds for the coupon may be borne not by the store but by the provider of the payment object (for example, the manufacturer of the product). In that case, the payment server 10 does not perform the above subtraction process.

Note that the payment means and payment services described above are not limited to those for providing consideration for purchasing products or providing services (settlement of debts). For example, as described above, the payment means or payment service may have a function related to remittance between accounts owned by multiple users. That is, the above-mentioned payment means and payment service may be any service that controls the transmission and reception of electronic money between the accounts of arbitrary owners linked to the owner of electronic money, such as users and stores. In other words, the payment means and payment services according to the embodiments include various controls for realizing electronic money exchange (not only various inter-account remittance controls via electronic money, but also control regarding exchanges between electronic money accounts and bank accounts). Transaction methods and transaction services that carry out various types of debt processing such as control, processing related to splits and bonus payments, and various other controls related to the exchange of assets, including electronic money, may be provided in any format. Good too. Further, the various controls realized by such transaction means and transaction services may include both payment-related control and remittance-related control, or only one of them may be included. That is, the term "transaction" is a concept that includes not only "settlement" related to electronic money, but also "remittance" of electronic money and various other types of processing. That is, the payment server 10 may be an information processing device that implements a transaction means that controls the exchange of electronic money between arbitrary owners.

[About the outline of the embodiment]
Here, as an example of a technology that gives a predetermined profit to a user who purchases a predetermined transaction object, a discount coupon (hereinafter sometimes simply referred to as a coupon) for an arbitrary product is given to the user in advance. A technology has been proposed in which the coupons are acquired and used to make payments when paying at the cash register. However, conventionally, coupons may not be managed efficiently.

For example, when a product manufactured by a certain manufacturer is sold at multiple stores, coupons for the product are linked to each store. Then, if the coupon acquired by the user is linked to the store where the payment is made, the coupon is applied. For this reason, if there are a large number of stores associated with a coupon, it is necessary to search for a store for payment from among such a large number of stores, and the search process (determining whether the coupon can be applied) takes time. In addition, in the case of stores such as vending machines that are easy to install and whose number of stores changes often, store identification information is not issued for each store, but all stores are managed as the same store identification information, and coupons linked to it are not issued. Although it is possible to issue coupons, in this case, it is not possible to link the store identification information to the location information of each store, so there is no way for the user to check where the coupons they have acquired can be used. As described above, conventionally, there is room for improvement in terms of efficient coupon management.

Therefore, the payment server 10 executes the information processing shown in FIGS. 1A to 1C. Specifically, the payment server 10 generates a common facility ID (common store identification information) common to multiple facilities 200 where the same coupon can be used, and stores it in its own device in association with the coupon. . Then, the payment server 10 acquires the common facility ID of the store where the payment is to be made from the external device 300, and determines whether the coupon can be applied based on the coupon linked to the common facility ID. As a result, when determining whether a coupon can be applied, there is no need to search for a store for payment from among a large number of stores linked to a coupon, so there are a large number of facilities 200 such as vending machines. Even if the coupon is applicable, it can be quickly determined whether the coupon is applicable or not. That is, according to the payment server 10 according to the embodiment, coupons can be managed efficiently.

The above information processing will be described in detail below using FIGS. 1A to 1C. First, a coupon registration process will be described using FIG. 1A, and then a payment process when coupons are applied by user scan and store scan will be described using FIGS. 1B and 1C. In the following description, an example will be given in which the store terminal 200 is a vending machine that provides foodstuffs and the like unmanned. Furthermore, in the following description, the user terminal 100 may be equated with the user. That is, in the following, the user can also be read as the user terminal 100.

As shown in FIG. 1A, the payment server 10 acquires list information of a plurality of facilities 200 that can use the same coupon from the external device 300 (step S1). Specifically, the external device 300 receives the settings of the coupon received from the setter. For example, the setter operates a screen provided by the payment server 10 via a setter terminal (not shown) to transmit the setting details. The setting contents include the facility 200 that is the target of the coupon, the contents of the coupon (discount rate, etc.), the conditions of the coupon (usable period, usable user attributes, etc.), and the like. The list information also includes the name of each facility, location information, and the like.

Based on the received setting contents, the external device 300 generates a list showing a list of facilities 200 where the coupon can be used, and list information including the contents of the coupon and the conditions of the coupon, and transmits it to the payment server 10.

Next, the payment server 10 issues a coupon ID for identifying the coupon based on the list information received from the external device 300, and generates common data linking the coupon ID, common SID, and common MID. and register it in the facility information database (step S2). The common MID is a member store ID (also called group identification information or merchant ID) that is identification information for identifying a payment destination, and is a member store ID common to a plurality of facilities. Further, the common SID is identification information common to a plurality of facilities, and is identification information that identifies an affiliated store. Note that when the payment server 10 acquires list information from an unregistered member store (common MID and common SID have not been issued), it issues a new common MID and common SID, and When list information is obtained from a member store (which has already issued a common SID), the issued common MID and common SID are linked to the coupon ID. Note that the member store ID (common member store ID) corresponds to the payment destination ID. Further, although details will be described later, the facility information database also includes facility information such as facility location information.

Next, the payment server 10 issues an MID for each facility and an SID for each facility for the plurality of facilities included in the list information in response to the issued coupon ID, and generates individual data linked to the coupon ID. and register it in the facility information database (step S3). The SID is identification information (store identification information) for each facility. MID is a merchant ID for each facility. Note that the MID may be the same identification information as the common MID, or may be different identification information for each facility. Note that the common MID and common SID are identification information used for payment, and the MID and SID of the above-mentioned individual data are managed only by the payment server 10. That is, the payment server 10 issues an SID and an MID for each facility in order to internally distinguish and manage each of the multiple facilities.

Subsequently, the payment server 10 notifies the external device 300 of the set of the common MID and the common SID, which are the registered common data (step S4). Then, the external device 300 stores the set of the common MID and the common SID in its own device. This completes the coupon registration process. Note that notification of the common MID and common SID to the external device 300 is a process that is performed only at the time of new registration, and the notification of the common MID and common SID does not need to be performed for already registered member stores.

Next, a coupon acquisition process for the user terminal 100 will be described using FIG. 1A. Specifically, the user terminal 100 starts the payment application and transmits a coupon acquisition request to the payment server 10 (step S5). A coupon acquisition request is transmitted when the user selects (designates a coupon ID) from a list of obtainable coupons presented on the coupon acquisition screen displayed on the user terminal 100. The user terminal 100 transmits a coupon acquisition request linked with a user ID that identifies the user to the payment server 10.

Subsequently, the payment server 10 associates the user ID and the coupon ID and registers them in the user information DB based on the coupon acquisition request received from the user terminal 100 (step S6).

Subsequently, the payment server 10 provides information based on the individual data linked to the coupon ID of the coupon acquired by the user (step 7). Specifically, when payment server 10 receives a request from a user to provide the location of facility 200 where the acquired coupon can be used, payment server 10 provides location information of facility 200 linked to the coupon ID to user 100. For example, the payment server 100 provides the locations of facilities 200 that exist around the location of the user terminal 100 on a map display. Thereby, the location information of the facility 200 where the coupon can be used can be provided to the user.

Note that if the common data linked to the coupon ID includes location information, the payment server 10 gives priority to the location information included in the common data over the location information for each facility included in the individual data. provide.

In addition, if the coupon is linked to the common data used for payment and individual data does not exist (if coupon settings are made for each facility), the payment server 10 also stores the location information of the facility linked to the common data. and, if individual data is linked to the coupon separately from the common data, provide the location information of the individual data.

The payment server 10 also determines whether only common data or common data and individual data are linked to the coupon ID, and if only common data is linked, the payment server 10 provides the location information included in the common data. , when common data and individual data are linked, location information for each facility included in the individual data may be provided.

Next, a payment process when coupons are applied by user scan and store scan will be described using FIGS. 1B and 1C. First, using FIG. 1B, a payment process when a coupon is applied by a user scan will be described.

Specifically, as shown in FIG. 1B, when a product is selected by a user, the vending machine that is the facility 200 transmits a payment information request to the external device 300 (step S1). The payment information request is a request to generate payment information (for example, a two-dimensional code) that includes information on the payment amount, and is a request that includes the payment amount that is the price of the selected product.

Next, the external device 300 generates a payment ID (payment number) that is identification information for identifying the payment, and stores it in its own device in association with the unique number corresponding to the facility 200 (step S2). The unique number is a number managed internally by the external device 300, and is identification information for identifying each facility.

Subsequently, the external device 300 transmits a payment information generation request to the payment server 10 (step S3). The payment information generation request is a payment information generation request that includes a payment ID, a payment amount, a common MID, and a common SID.

Subsequently, the payment server 10 generates payment information in accordance with the payment information generation request (step S4), and provides the generated payment information to the external device 300 (step S5). The payment information is, for example, a two-dimensional code including a payment ID, a payment amount, a common MID, and a common SID.

Subsequently, the external device 300 provides the received payment information to the corresponding facility 200 (step S6). Specifically, the external device 300 identifies the facility 200 corresponding to the unique number linked to the payment ID of the received payment information as the corresponding facility 200.

Next, the facility 200 displays the received payment information on a display unit (not shown) (step 7). Specifically, facility 200 displays payment information in a manner readable by user terminal 100.

Subsequently, the user terminal 100 reads the payment information displayed on the facility 200 using the reading function of the payment application (step S8), and transmits the read payment information to the payment server 10 (step S9).

Subsequently, the payment server 10 determines whether the coupon can be applied based on the payment information received from the user terminal 100 (step S10). Specifically, the payment server 10 refers to the user information database and the facility information database, and if the user has acquired a coupon with a coupon ID linked to the common MID and common SID of the received payment information, , it is determined that the coupon is applicable.

In this way, in the present disclosure, by linking the coupon ID to the common MID and common SID and including the common MID and common SID in the payment information, it is possible to easily determine whether the coupon can be applied from the payment information obtained by user scanning. can be determined.

Subsequently, when determining that the coupon can be applied, the payment server 10 performs payment processing using the price after applying the coupon as the payment amount (step S11). Note that, if it is determined that the coupon cannot be applied, the payment server 10 performs payment processing by setting the price to which the coupon is not applied as the payment amount. Note that when a user obtains a coupon from store information displayed in MID and SID, which are individual data for internal management, and the coupon is subsequently used, the payment server 10 stores the MID and SID that caused the acquisition. It may also be specified that the payment was made at the facility 200 indicated by .

Subsequently, the payment server 10 notifies the user terminal 100 of the completion of the payment (step S12), and also notifies the external device 300 of the completion of the payment (step S13). The payment completion notification includes the payment ID and the payment amount.

Next, the external device 300 identifies the facility 200 for which the payment was made based on the payment ID in the payment completion notification (step S14). Specifically, the external device 300 refers to the set of payment ID and SID stored in the external device 300 and identifies the SID linked to the payment ID in the payment completion notification.

Subsequently, the external device 300 instructs the identified facility 200 to provide the product (step S15). Subsequently, the facility 200 provides the product selected by the user in accordance with the product provision instruction (step S16).

Next, using FIG. 1C, a payment process when applying a coupon by store scanning will be described.

Specifically, as shown in FIG. 1C, after a product of the facility 200 is selected by the user, the user terminal 100 displays an information code including the user ID according to the user's operation (step S1). . The user holds the user terminal 100 over the information reading section of the facility 200 with the information code displayed.

Subsequently, the facility 200 acquires the user ID by reading the information code displayed on the user terminal 100 (step S2). Subsequently, the facility 200 transmits a payment request including the read user ID and the payment amount, which is the price of the selected product, to the external device 300.

Next, the external device 300 generates a payment ID (payment number) that is identification information for identifying the payment, and stores it in its own device in association with the common SID corresponding to the facility 200 (step S4).

Subsequently, the external device 300 transmits a payment request to the payment server 10 (step S5). The payment request includes a payment ID, a payment amount, a user ID, a common MID, and a common SID.

Subsequently, the payment server 10 determines whether the coupon can be applied based on the payment request received from the external device 300 (step S7). Specifically, the payment server 10 refers to the user information database and the facility information database, and if the user has acquired a coupon with a coupon ID linked to the common MID and common SID of the received payment request, , it is determined that the coupon is applicable.

In this way, in the present disclosure, by linking the coupon ID to the common IMD and the common SID, it is possible to easily determine whether the coupon can be applied from the payment information obtained by store scanning.

Subsequently, when determining that the coupon can be applied, the payment server 10 performs payment processing using the price after applying the coupon as the payment amount (step S7). Note that, if it is determined that the coupon cannot be applied, the payment server 10 performs payment processing by setting the price to which the coupon is not applied as the payment amount. Note that the payment server 10 determines the cause of acquisition if the coupon is used within a predetermined period after the user acquires the coupon from the store information displayed in the MID and SID, which are individual data for internal management. It may be specified that the payment was made at the facility 200 indicated by the MID and SID. For example, if a coupon is used within a certain period of time after acquisition, the MID and SID that caused the acquisition and payment information are stored in association with each other. By doing this, the payment information only includes the shared MID and common SID, so the payment server 10 cannot identify which store the payment was made at, but by referring to the linked MID and SID, It becomes possible for the payment server 10 to identify the store where the payment was made.

Subsequently, the payment server 10 notifies the external device 300 of the completion of payment (step S7). The payment completion notification includes the payment ID and the payment amount.

Next, the external device 300 identifies the facility 200 for which the payment was made based on the payment ID in the payment completion notification (step S8). Specifically, the external device 300 refers to the set of payment ID and SID stored in the external device 300 and identifies the SID linked to the payment ID in the payment completion notification.

Subsequently, the external device 300 instructs the identified facility 200 to provide the product (step S9). Subsequently, the facility 200 provides the product selected by the user in accordance with the product provision instruction (step S10).

As described above, the payment server 10 according to the embodiment acquires transaction object information regarding the user's payment object from the external device 300, and provides the user with profits based on the coupon specified based on the acquired transaction object information. Give. Thereby, the payment server 10 according to the embodiment can automatically apply coupons applicable to the user in payment using the payment application. That is, the payment server 10 according to the embodiment can improve convenience for users in payment.

[Payment server configuration]
Next, the configuration of the payment server 10 will be described using FIG. 2. FIG. 2 is a diagram illustrating a configuration example of a payment server according to an embodiment. As shown in FIG. 2, the payment server 10 includes a communication section 20, a storage section 30, and a control section 40.

(About the communication department 20)
The communication unit 20 is realized by, for example, a NIC (Network Interface Card). The communication unit 20 is connected to the network N by wire or wirelessly, and transmits and receives information between the user terminal 100, the facility 200, the external device 300, and the like.

(About the storage unit 30)
The storage unit 30 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 2, the storage unit 30 includes a user information database (DB) 31, an account database (DB) 32, a facility information database (DB) 33, and a coupon information database (DB) 34.

(About the user information database 31)
The user information database 31 stores various information regarding users of the electronic payment service provided by the payment server 10. Here, an example of information stored in the user information database 31 will be explained using FIG. 3. FIG. 3 is a diagram showing an example of the user information database 31 according to the embodiment. In the example of FIG. 3, the user information database 31 includes items such as "user ID,""paymenthistory," and "obtained coupon."

"User ID" indicates identification information for identifying a user. "Payment history" indicates the history of payments made using electronic payment services, and stores information such as payment destination and payment amount. “Acquired coupon” indicates a coupon that the user has acquired from among the coupons indicated by the coupon information stored in the coupon information database 34, and stores identification information (coupon ID) for identifying the coupon, for example. .

(About account database 32)
The account database 32 stores various information regarding accounts owned by users, stores (business operators), facilities 200, etc. in the electronic payment service. Here, an example of information stored in the account database 32 will be explained using FIG. 4. FIG. 4 is a diagram showing an example of the account database 32 according to the embodiment. In the example of FIG. 4, the account database 32 has items such as "account ID", "owner information", and "account balance".

“Account ID” indicates identification information for identifying an account. "Owner information" indicates information regarding the owner of the account, and stores, for example, identification information for identifying the owner. “Account balance” indicates the balance of the account.

(About facility information database 33)
The facility information database 33 stores various types of information regarding facilities. Here, an example of information stored in the facility information database 33 will be explained using FIG. 5. FIG. 5 is a diagram showing an example of the facility information database 33 according to the embodiment. In the example of FIG. 5, the facility information database 33 has items such as "facility ID", "affiliated store ID", "business ID", "facility information", and "applicable coupon".

“Facility ID” is identification information for identifying the facility 200, and is the above-mentioned SID. The "member store ID" is identification information for identifying a payment destination, and is the above-mentioned MID. “Business ID” is identification information for identifying a business that manages facility 200. “Facility information” is information regarding the facility 200, and includes the facility name, location information of the facility 200, and the like. The "applicable coupon" is a coupon applied to the facility 200, and the coupon ID in the coupon information database 34, which will be described later, is input.

In FIG. 5, "common SID #1" of "facility ID" is a common SID common to a plurality of facilities 200, and "SID #1" is an SID for each facility. Further, "common MID #1" of "affiliated store ID" is a common MID common to a plurality of facilities 200, and "MID #1" is an MID for each facility.

(About the coupon information database 34)
The coupon information database 34 stores various information regarding coupons applied to users. Here, an example of information stored in the coupon information database 34 will be explained using FIG. 6. FIG. 6 is a diagram showing an example of the coupon information database 34 according to the embodiment. In the example of FIG. 6, the coupon information database 34 has items such as "coupon ID,""profitdetails," and "acquisition conditions."

"Coupon ID" indicates identification information for identifying a coupon. “Benefit details” indicates the details of the benefit given to the user by the coupon. “Acquisition conditions” indicate conditions for a user to acquire a coupon (for example, demographic attributes, psychographic attributes, payment history).

(About the control unit 40)
The control unit 40 is a controller, and for example, various programs stored in the storage device inside the payment server 10 use the RAM as a work area by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), etc. This is achieved through execution. Further, the control unit 40 is a controller, and is realized by, for example, an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). The control unit 40 according to the embodiment realizes or executes information processing functions and operations described below.

(About information processing of control unit 40)
The control unit 40 performs the registration process and payment process described in FIGS. 1A to 1C.

(About registration process)
Specifically, the control unit 40 acquires list information of a plurality of facilities 200 that can use the same coupon from the external device 300. The list information includes the name of the facility 200, location information of the facility 200, coupon information (profit details, available period), and the like.

The control unit 40 issues a coupon ID based on the acquired list information. Further, if the member store that is the sender of the list information is unregistered, the control unit 40 issues a new common SID and common MID. The control unit 40 generates common data that links the issued coupon ID, common SID, and common MID, and registers it in the facility information DB 33.

Further, the control unit 40 issues MID and SID for each of the plurality of facilities included in the list information, generates individual data by linking the issued MID and SID to the coupon ID, and generates individual data for facility information. Register in DB33.

After registering the individual data and the common data in the facility information DB 33, the control unit 40 notifies the external device 300 of the set of common MID and common SID, which are common data.

(About payment processing: User scan)
Specifically, the control unit 40 receives a payment information generation request from the external device 300. The payment information generation request includes a payment ID, a payment amount, a common MID, and a common SID. Control unit 40 generates payment information and provides it to external device 300 based on the payment information generation request. The payment information is, for example, a two-dimensional code, and includes a payment ID, a payment amount, a common MID, and a common SID.

After providing the payment information to the external device 300, the control unit 40 acquires the payment information from the user terminal 100. In addition to the above information, the payment information acquired from the user terminal 100 is associated with a user ID.

The control unit 40 determines whether the coupon can be applied based on the payment information obtained from the user terminal 100. Specifically, the control unit 40 refers to the user information DB 31 and the facility information DB 33 and determines whether the user has acquired a coupon linked to the common MID and common SID in the payment information acquired from the user terminal 100. Determine whether or not.

The control unit 40 determines that the coupon can be applied if the user has acquired such a coupon, specifically, if the coupon ID is linked to the user ID in the user information DB 31 as an acquired coupon. judge. On the other hand, if the user has not acquired such a coupon, specifically, if the coupon ID is not linked as an acquired coupon to the user ID in the user information DB 31, the control unit 40 determines that the coupon cannot be applied. It is determined that

The control unit 40 performs payment processing based on the result of determining whether the coupon can be applied. Specifically, when the control unit 40 determines that the coupon can be applied, the control unit 40 performs payment processing using the price after applying the coupon (after discount) as the payment amount. On the other hand, if the control unit 40 determines that the coupon cannot be applied, the control unit 40 performs payment processing using the price to which the coupon is not applied as the payment amount.

After completing the payment process, the control unit 40 notifies the external device 300 and the user terminal 100 that the payment has been completed. The payment completion notification includes the payment ID and the payment amount.

(About payment processing: Store Scan)
Specifically, the control unit 40 receives a payment request from the external device 300. The payment request includes a payment ID, a payment amount, a user ID, a common MID, and a common SID.

The control unit 40 determines whether the coupon can be applied based on the payment request obtained from the external device 300. Specifically, the control unit 40 refers to the user information DB 31 and the facility information DB 33 to determine whether the user has acquired a coupon linked to the common MID and common SID in the payment request.

The control unit 40 determines that the coupon can be applied if the user has acquired such a coupon, specifically, if the coupon ID is linked to the user ID in the user information DB 31 as an acquired coupon. judge. On the other hand, if the user has not acquired such a coupon, specifically, if the coupon ID is not linked as an acquired coupon to the user ID in the user information DB 31, the control unit 40 determines that the coupon cannot be applied. It is determined that

The control unit 40 performs payment processing based on the result of determining whether the coupon can be applied. Specifically, when the control unit 40 determines that the coupon can be applied, the control unit 40 performs payment processing using the price after applying the coupon (after discount) as the payment amount. On the other hand, if the control unit 40 determines that the coupon cannot be applied, the control unit 40 performs payment processing using the price to which the coupon is not applied as the payment amount.

After completing the payment process, the control unit 40 notifies the external device 300 that the payment has been completed. The payment completion notification includes the payment ID and the payment amount.

[Processing flow]
The procedure of the coupon registration process of the payment server 10 according to the embodiment will be described using FIG. 7. FIG. 7 is a flowchart illustrating an example of the procedure of coupon registration processing according to the embodiment.

As shown in FIG. 7, the payment server 10 acquires list information of facilities 200 that can use coupons (step S101).

Next, the payment server 10 issues a coupon ID for identifying the coupon based on the list information received from the external device 300 (step S102). Subsequently, the payment server 10 generates common data for each facility 200 in which the coupon ID is linked with the common SID and the common MID, and stores it in the facility information database (step S103).

Next, the payment server 10 issues an MID and a SID for each facility included in the list information (step S104). Next, the payment server 10 generates individual data in which the MID and SID are linked to the issued coupon ID, stores it in the facility information database (step S105), and completes the registration process.

Next, with reference to FIG. 8, a procedure of payment processing when a user scans the payment server 10 according to the embodiment will be described. FIG. 8 is a flowchart illustrating an example of a payment processing procedure during a user scan according to the embodiment.

As shown in FIG. 8, the payment server 10 receives a payment information generation request from the external device 300 (step S201). The payment information generation request includes a payment ID, a payment amount, a common MID, and a common SID.

Next, the payment server 10 generates payment information based on the payment information generation request and provides it to the external device 300 (step S202).

Next, the payment server 10 acquires payment information from the user terminal 100 (step S203). Next, the payment server 10 determines whether the coupon can be applied based on the acquired payment information (step S204).

Next, the payment server 10 performs payment processing using the payment amount according to the result of determining whether the coupon can be applied (step S205). Next, the payment server 10 notifies the user terminal 100 and the external device 300 of payment completion notification (step S206), and ends the process.

Next, referring to FIG. 9, a procedure of payment processing when the payment server 10 according to the embodiment scans a store will be described. FIG. 9 is a flowchart illustrating an example of a payment processing procedure during store scanning according to the embodiment.

As shown in FIG. 9, the payment server 10 receives a payment request from the external device 300 (step S301). The payment request includes a payment ID, a payment amount, a user ID, a common MID, and a common SID.

Next, the payment server 10 determines whether the coupon can be applied based on the payment request (step S302).

Next, the payment server 10 performs payment processing using the payment amount according to the result of determining whether the coupon can be applied (step S303). Next, the payment server 10 notifies the external device 300 of payment completion notification (step S304), and ends the process.

[Modified example]
The embodiments described above are merely examples, and various modifications and applications are possible.

For example, in the coupon registration process shown in FIG. 1A, the payment server 10 acquires the list information via the external device 300, but it may also directly acquire the list information from a setter terminal (not shown).

In addition, as shown in FIGS. 1B and 1C, in the payment process, the payment server 10 receives a payment information generation request or a payment request from the facility 200 via the external device 300, but it does not generate payment information directly from the facility 200. It may also receive requests and payment requests. Similarly, the payment server 10 may send payment information or notification of payment completion directly to the facility 200 without going through the external device 300.

[About processing mode]
Among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, and conversely, all of the processes described as being performed manually can be performed manually. Alternatively, some of the steps can be performed automatically using known methods. In addition, the processing procedures, specific names, and information including various data and parameters shown in the above text and drawings may be changed arbitrarily, unless otherwise specified. For example, the various information shown in each figure is not limited to the illustrated information.

Further, each component of each device shown in the drawings is functionally conceptual, and does not necessarily need to be physically configured as shown in the drawings. In other words, the specific form of distributing and integrating each device is not limited to what is shown in the diagram, and all or part of the devices can be functionally or physically distributed or integrated in arbitrary units depending on various loads and usage conditions. Can be integrated and configured.

Furthermore, the embodiments described above can be combined as appropriate within a range that does not conflict with the processing contents.

[About burden bearer settings]
So far, we have described an example in which the funds for the coupon are borne by the manufacturer. On the other hand, the person who pays for the coupon funds does not have to be the manufacturer. For example, the bearer may be a store, a user, or the like.

Further, in the above description, a coupon was cited as an example of a benefit, but the benefit is not limited to a coupon, but may include issuing a stamp card, providing another product, or the like.

〔effect〕
As described above, the payment server 10 according to the embodiment includes the storage section 30 and the control section 40. The storage unit 30 stores, for each of a plurality of facilities 200 where the same benefit can be used, a benefit ID (coupon ID) that identifies the benefit, and a member store ID (coupon ID) that identifies the payment destination when making a payment to the facility 200. Payment destination ID, MID) and facility ID (SID) that identifies each facility 200 are linked to individual data and benefit ID, member store ID, and common facility ID (SID) that is common to multiple facilities 200. A database (facility information DB 33) containing common data linked with the common SID is stored. Based on the common data in the facility information DB 33, the control unit 40 determines whether benefits are applicable to payments made using the user terminals 100 at each of the plurality of facilities 200.

As a result, according to the payment server 10, when determining whether a coupon can be applied, there is no need to search for a store to perform payment from among a large number of stores linked to a coupon. Even if there are a large number of facilities 200, it is possible to quickly determine whether a coupon can be applied. That is, according to the payment server 10 according to the embodiment, coupons can be managed efficiently.

Further, the control unit 40 generates payment information including common data linked to the member store ID and the common facility ID and transmits it to the facility 200, and then the control unit 40 generates payment information that includes common data linked to the member store ID and the common facility ID and transmits the payment information linked to the user ID from the user terminal 100. Determine whether benefits are applicable based on the information.

Thereby, it is possible to efficiently determine whether or not a benefit is applicable in the payment processing based on the user scan.

Further, the control unit 40 receives a payment request in which the user ID acquired by the facility 200 from the user terminal 100 is linked to common data in which the affiliated store ID and the common facility ID are linked, and provides benefits based on the received payment request. Determine whether or not it is applicable.

As a result, it is possible to efficiently determine whether or not benefits are applicable in the payment process using store scanning.

Furthermore, the facility information database 33 includes location information for each facility 200. When the control unit 40 receives a request to acquire a benefit with a benefit ID specified by the user, the control unit 40 provides the user with the location information of the facility 200 where the benefit can be used, based on the individual data linked to the benefit ID. Provided to the terminal 100.

Thereby, information on facilities 200 where coupons can be used can be provided to the user terminal 100.

Further, the control unit 40 provides the location of the facility 200 on a map display.

Thereby, the user can easily grasp the location of the facility 200 where the coupon can be used.

Furthermore, when the common data is associated with location information regarding the facility 200, the control unit 40 provides the location information associated with the common data with priority over the location information for each facility 200.

As a result, location information linked to common data can be provided preferentially, and if location information is linked to individual data, location information for each facility can be provided.

Further, the benefit is a coupon or a stamp card related to a discount on payment.

Thereby, coupons or stamp cards can be managed efficiently.

Further, the facility 200 is a facility that provides unmanned services, and is, for example, a vending machine.

Thereby, it is possible to efficiently manage the benefits that can be used in the facility 200 where there are a large number of vending machines and the like.

[Hardware configuration]
Further, the payment server 10 according to each of the embodiments described above is realized, for example, by a computer 1000 having a configuration as shown in FIG. The payment server 10 will be described below as an example. FIG. 10 is a hardware configuration diagram showing an example of a computer that implements the functions of a payment server. Computer 1000 has CPU 1100, ROM 1200, RAM 1300, HDD 1400, communication interface (I/F) 1500, input/output interface (I/F) 1600, and media interface (I/F) 1700.

CPU 1100 operates based on a program stored in ROM 1200 or HDD 1400, and controls each part. The ROM 1200 stores a boot program executed by the CPU 1100 when the computer 1000 is started, programs depending on the hardware of the computer 1000, and the like.

The HDD 1400 stores programs executed by the CPU 1100, data used by the programs, and the like. Communication interface 1500 receives data from other devices via communication network 500 (corresponding to network N in the embodiment) and sends it to CPU 1100, and also sends data generated by CPU 1100 to other devices via communication network 500. Send to device.

The CPU 1100 controls output devices such as a display and a printer, and input devices such as a keyboard and mouse via an input/output interface 1600. CPU 1100 obtains data from an input device via input/output interface 1600. Further, CPU 1100 outputs the generated data to an output device via input/output interface 1600.

Media interface 1700 reads programs or data stored in recording medium 1800 and provides them to CPU 1100 via RAM 1300. CPU 1100 loads this program from recording medium 1800 onto RAM 1300 via media interface 1700, and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase change rewritable disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. etc.

For example, when the computer 1000 functions as the payment server 10, the CPU 1100 of the computer 1000 realizes the functions of the control unit 40 by executing a program loaded onto the RAM 1300. Further, each data in the storage device of the payment server 10 is stored in the HDD 1400. The CPU 1100 of the computer 1000 reads these programs from the recording medium 1800 and executes them, but as another example, these programs may be acquired from another device via a predetermined communication network.

[7. others〕
Some of the embodiments of the present application have been described above in detail based on the drawings, but these are merely examples, and various modifications and variations may be made based on the knowledge of those skilled in the art, including the embodiments described in the disclosure section of the invention. It is possible to carry out the invention in other forms with modifications.

Further, the configuration of the above-described payment server 10 can be changed flexibly, such as implementing some functions by calling an external platform or the like using an API (Application Programming Interface), network computing, or the like.

Further, "unit" described in the claims can be read as "means", "circuit", etc. For example, the reception unit can be read as reception means or reception circuit.

1 Information processing system 10 Payment server 20 Communication unit 30 Storage unit 31 User information database 32 Account database 33 Facility information database 34 Coupon information database 40 Control unit 100 User terminal 200 Facility 300 External device

Claims (10)

For each of multiple facilities where the same benefit can be used, a benefit ID that identifies the benefit, a payment destination ID that identifies the payment destination when making payments to the facility, and a facility ID that identifies each of the facilities. a storage unit that stores a database including individual data that links the benefit ID, and common data that links the payment destination ID and a common facility ID that is common to the plurality of facilities;
a control unit that determines, based on the common data in the database, whether or not the benefit is applicable in payment using a user terminal based on the facility ID of each of the plurality of facilities;
Equipped with
The storage unit includes:
storing user information in which the benefit ID of the benefit acquired by the user and the user ID of the user are linked;
The control unit includes:
After generating payment information including the common data linked to the payment destination ID and the common facility ID and transmitting it to the facility, the user ID and the facility ID are sent from the user terminal that read the payment information from the facility. Determine whether or not the benefit is applicable based on the payment information linked and transmitted and the user information.
Information processing device. The control unit includes:
The facility receives a payment request in which the user ID acquired from the user terminal is linked to the payment destination ID and the common data linked to the common facility ID, and applies the benefit based on the received payment request. The information processing device according to claim 1, wherein the information processing device determines whether or not the information is available. The database includes location information for each facility,
The control unit includes:
When a request to acquire the benefit of the benefit ID specified by the user is received, the user terminal acquires the location information of the facility where the benefit is available based on the individual data linked to the benefit ID. The information processing device according to claim 1 . The control unit includes:
The information processing device according to claim 3 , wherein when the common data is linked to location information regarding the facility, the location information linked to the common data is provided with priority over the location information for each facility. The control unit includes:
Determine whether only the common data or the common data and the individual data are linked to the benefit ID, and if only the common data is linked, provide position information included in the common data, The information processing device according to claim 3 , wherein when the common data and the individual data are linked, position information for each facility included in the individual data is provided. The control unit includes:
The information processing device according to claim 3 , wherein the location of the facility is provided on a map display. The above benefits are
The information processing device according to claim 1, wherein the information processing device is a coupon or a stamp card related to a discount for the payment. The said facility is
The information processing device according to claim 1, wherein the information processing device is a facility that provides unmanned services. An information processing method performed by a computer, the method comprising:
For each of multiple facilities where the same benefit can be used, a benefit ID that identifies the benefit, a payment destination ID that identifies the payment destination when making payments to the facility, and a facility ID that identifies each of the facilities. and storing in a storage unit a database including individual data that is linked to the benefit ID, and common data that is linked to the payment destination ID and a common facility ID that is common to the plurality of facilities. and,
a control step of determining whether or not the benefit is applicable in payment using a user terminal based on the facility ID of each of the plurality of facilities, based on the common data in the database;
including;
The storage unit includes:
storing user information in which the benefit ID of the benefit acquired by the user and the user ID of the user are linked;
The control step includes:
After generating payment information including the common data linked to the payment destination ID and the common facility ID and transmitting it to the facility, the user ID and the facility ID are sent from the user terminal that read the payment information from the facility. Determine whether or not the benefit is applicable based on the payment information linked and transmitted and the user information.
Information processing method. For each of multiple facilities where the same benefit can be used, a benefit ID that identifies the benefit, a payment destination ID that identifies the payment destination when making payments to the facility, and a facility ID that identifies each of the facilities. A procedure for storing in a storage unit a database including individual data that is linked to the benefit ID, and common data that is linked to the payment destination ID and a common facility ID that is common to the plurality of facilities. and,
a control procedure for determining, based on the common data in the database, whether or not the benefit is applicable in payment using a user terminal based on the facility ID of each of the plurality of facilities;
make the computer run
The storage unit is
storing user information in which the benefit ID of the benefit acquired by the user and the user ID of the user are linked;
The control procedure includes:
After generating payment information including the common data linked to the payment destination ID and the common facility ID and transmitting it to the facility, the user ID and the facility ID are sent from the user terminal that read the payment information from the facility. Determine whether or not the benefit is applicable based on the payment information linked and transmitted and the user information.
Information processing program.

Images