JP6987957B1 - Payment devices, programs, and information processing methods - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a payment device, a program and an information processing method capable of supporting the recording of a user's meal at a restaurant for a plurality of services for recording a meal. SOLUTION: A payment device 100 connected to a plurality of eating and drinking establishments via a network relates to a meal of a first user from among a plurality of services providing a service of recording meals to a user, based on a recording destination condition. A recording destination identification unit that identifies at least one service that is the recording destination of meal data, and a request reception unit that accepts payment requests when the first user pays for meals at a restaurant facility from the facility terminal of the restaurant facility. , A payment processing unit that performs payment processing for payment settlement based on a payment request, a meal data acquisition unit 1141 that acquires meal data related to meals at a restaurant when payment processing is performed from a facility terminal, and a meal. A meal data transmission unit 131 for transmitting data to each service providing device of at least one specified service is provided. [Selection diagram] FIG. 5

Description

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

Conventionally, there is a service that records a user's meal for health management and the like. In providing such services, meals at restaurants are also subject to recording. In the following Patent Document 1, the locations of a plurality of restaurants and the names of dishes provided by each restaurant are stored in the restaurant database, and the names of dishes are obtained from this restaurant database based on the location and date and time when the user ate. A meal history system for extracting candidates is disclosed. This meal history system presents the extracted dish name candidates to the user, accepts the selection of the dish name that the user has eaten from these candidates, and associates the selected dish name with the user in the history database. accumulate. According to such a configuration, it is possible to reduce the time and effort for the user to input the meal information when recording the meal.

Japanese Unexamined Patent Publication No. 2019-046417

By the way, in recent years, there are various services for recording meals, such as those for dieting and those for managing the health of employees in companies. However, in the above patent document, it is assumed that meals are recorded only by one service (database), and there is a problem that it cannot be dealt with when a user uses a plurality of services.

Therefore, in view of the above problems, it is an object of the present invention to provide a payment device, a program, and an information processing method capable of supporting the recording of a user's meal at a restaurant for a plurality of services for recording meals. do.

The payment device according to one aspect of the present invention is at least one of a plurality of services that provide a service for recording a meal to a user, which is a recording destination of meal data related to the meal of a first user based on a recording destination condition. Based on the record destination identification unit that specifies one service, the request reception unit that accepts the payment request when the first user pays for the meal at the restaurant from the facility terminal of the restaurant, and the payment request. , The payment processing unit that performs payment processing for payment settlement, the meal data acquisition unit that acquires meal data related to meals at restaurants when payment processing is performed from the facility terminal, and the meal data are specified. It is provided with a meal data transmission unit for transmitting to each service providing device of at least one service.

The program according to one aspect of the present invention is a recording destination of meal data related to a first user's meal based on a recording destination condition from a plurality of services that provide a user with a service of recording meals on a computer. A recording destination specifying function for specifying at least one service, and a request receiving function for accepting a settlement request for the payment when the first user pays for a meal at the eating and drinking facility from the facility terminal of the eating and drinking facility. Based on the payment request, the payment processing function for performing the payment processing for the payment and the meal data regarding the meal at the restaurant when the payment processing is performed are acquired from the facility terminal. A meal data acquisition function and a meal data transmission function of transmitting the meal data to each service providing device of the specified at least one service are realized.

The information processing method according to one aspect of the present invention is at least a destination for recording meal data related to a first user's meal, based on a recording destination condition, from among a plurality of services that provide a service for recording meals to the user. One service is specified, and when the first user pays for meals at the restaurant from the facility terminal of the restaurant, the payment request is accepted, and the payment is settled based on the settlement request. When the processing is performed and the payment processing is performed from the facility terminal, the meal data regarding the meal at the eating and drinking facility is acquired, and the meal data is transmitted to each service providing device of at least one specified service.

INDUSTRIAL APPLICABILITY According to the present invention, it is possible to provide a payment device, a program, and an information processing method capable of assisting a user's meal recording in a restaurant for a plurality of services for recording meals.

It is a figure for demonstrating the system configuration example of the integrated payment system which concerns on this Embodiment. It is a figure for demonstrating the outline of the integrated payment system which concerns on this Embodiment. It is a figure for demonstrating the outline of the integrated payment system which concerns on this Embodiment. It is a figure for demonstrating the outline of the integrated payment system which concerns on this Embodiment. It is a figure which shows an example of the functional structure of the payment apparatus which concerns on this embodiment. It is a figure which shows the screen example of the integrated payment system which concerns on this embodiment. It is a figure which shows the screen example of the integrated payment system which concerns on this embodiment. It is a figure which shows the screen example of the integrated payment system which concerns on this embodiment. It is a figure which shows the data structure example of the integrated payment system which concerns on this embodiment. It is a figure which shows the data structure example of the integrated payment system which concerns on this embodiment. It is a figure which shows the operation example of the integrated payment system which concerns on this embodiment. It is a figure which shows the operation example of the integrated payment system which concerns on this embodiment. It is a figure which shows the operation example of the integrated payment system which concerns on this embodiment. It is a figure which shows an example of the hardware composition of the payment apparatus which concerns on this embodiment. It is a figure for demonstrating the example of the cooperation method of the meal data of the integrated payment system which concerns on this embodiment.

A preferred embodiment of the present invention (hereinafter referred to as “the present embodiment”) will be described with reference to the accompanying drawings. In each figure, those with the same reference numerals have the same or similar configurations.

In the present embodiment, the "part", "device", and "system" do not simply mean physical means, but include the functions of the "part", "means", "device", and "system". Including cases where it is realized by software. Further, even if the functions of one "part", "device", or "system" are realized by two or more physical means or devices, the functions of two or more "parts", "devices", or "systems" The function may be realized by one physical means or device.

<1. Overview>
In this embodiment, an example in which a consortium composed of a plurality of businesses belonging to the healthcare industry (hereinafter, also referred to as “healthcare consortium”) provides the following functions to the customers of the businesses will be described. ..
-A function to integrate the electronic payment methods of these businesses for customers who use restaurants owned by multiple businesses (hereinafter also referred to as "integrated payment function").
-A service that provides a service that records the customer's meal data created by the restaurant when making a payment using the above electronic payment method using the restaurant (hereinafter, also referred to as "meal-related service"). ) (Hereinafter, also referred to as "meal data hub (GW) function")

The eating and drinking facility may be any facility as long as it provides a paid eating and drinking service, and may be, for example, a restaurant or an employee cafeteria of a company where a customer works.

The meal-related service may be any service as long as it includes a service for recording customer's meal data (hereinafter, also referred to as “recording service”). The meal-related service may be, for example, a service for managing a customer's meal (hereinafter, also referred to as a “meal management service”). Further, the meal-related service may be, for example, a service related to the customer's health care (hereinafter, also referred to as "health care service"), or a service for supporting the customer's diet (hereinafter, "diet support service"). Also called).

In this embodiment, an example in which the healthcare consortium uses the integrated payment system 1 according to the present embodiment in providing the integrated payment function to the customer will be described. Regarding the application of the integrated payment system 1, the plurality of businesses to be integrated with the electronic payment means may be, for example, a plurality of businesses belonging to a specific industry other than the healthcare industry, and may be in a common industry. It may be a plurality of businesses having a common purpose, policy, etc., even if they do not belong to each other.

The business operator (hereinafter, also simply referred to as “business operator”) according to the present embodiment belongs to the healthcare consortium, and for each customer, the user of the integrated payment system 1 (hereinafter, simply referred to as “user”). Owns a restaurant that provides food and beverage services. The user includes a first user and a second user different from the first user. The second user may be a user related to the first user, for example, the first user and the second user may be in the same family, or the account of the first user in SNS (Social Networking Service). It may be a friend, a follower, etc. registered for.

<1-1. System configuration>
A system configuration example of the integrated payment system 1 will be described with reference to FIG.

The integrated payment system 1 is a system for providing an integrated payment function and a meal data hub function to users, meal-related service providers, and the like. The integrated payment system 1 is also a system for providing a healthcare service to a user by itself. As shown in FIG. 1, the integrated payment system 1 includes a payment device 100, a first user device 200a used by a first user, a second user device 200b used by a second user, and a first eating and drinking facility. It includes one facility terminal 300a, a second facility terminal 300b of a second eating and drinking facility, a first business operator server 400a owned by a first business operator, and a second business operator server 400b owned by a second business operator. The first business operator owns the first eating and drinking facility, and the second business operator owns the second eating and drinking facility.

The first user device 200a and the second user device 200b are one aspect of the user device, and are collectively referred to as "user device 200" when there is no particular need to distinguish them. Further, the first facility terminal 300a and the second facility terminal 300b are one aspect of the facility terminal, and are collectively referred to as "facility terminal 300" when there is no particular need to distinguish them. Further, the first restaurant and the second restaurant are collectively referred to as "restaurant" when there is no particular need to distinguish between them. Further, the first business server 400a and the second business server 400b are one aspect of the business server, and are collectively referred to as "business server 400" when there is no particular need to distinguish them.

The payment device 100, the user device 200, and the business server 400 are connected to each other via the network N1. Further, the operator server 400 and the facility terminal 300 are connected to each other via the network N1 or the network N2 originally constructed by the operator.

At least one of the payment device 100 and the user device 200 provides the first service of the first external system 5a that provides the health care service via the network N1 in order to acquire the health care data of the user and link the meal data. It is connected to the device 500a. It is assumed that the healthcare service provided by the first external system 5a also includes a service for recording the user's meal. Further, at least one of the payment device 100 and the user device 200 is connected to the second service providing device 500b of the second external system 5b that provides the meal management service via the network N1 in order to link the user's meal data. Has been done.

The first external system 5a and the second external system 5b are collectively referred to as "external system 5" when there is no particular need to distinguish them. The first service providing device 500a and the second service providing device 500b are one aspect of the service providing device, and are collectively referred to as "service providing device 500" when there is no particular need to distinguish them.

The network N1 or N2 is composed of a wireless network or a wired network. Examples of networks include mobile phone networks, PHS (Personal Handy-phone System) networks, wireless LAN (Local Area Network), 3G (3rd Generation), LTE (Long Term Evolution), 4G (4th Generation), and 5G (4th Generation). There are networks compliant with 5th Generation), WiMax (registered trademark), infrared communication, Bluetooth (registered trademark), wired LAN, telephone line, power line network, IEEE1394, and the like.

"Health care data" is data related to the user's health care. The health care data includes, for example, at least one of physical data indicating the physical condition of the user or activity data indicating the amount of activity of the user. The physical data includes, for example, the user's "weight", "height", "body fat percentage", "body temperature", "blood pressure", "heart rate", "body age", "sleep data", or the health diagnosis received by the user. It may include health examination result information and the like showing the result of. The activity data may include, for example, the user's "steps", "calories burned", "distance traveled", etc. per predetermined period. The health care data may include, for example, the user's dietary data. The "meal data" is data related to the user's meal. Details of the meal data will be described later with reference to FIG.

The payment device 100 is an information processing device capable of integrating communication with a user device 200, a business server 400, and an external system 5 and electronic payment means of each of a plurality of businesses. By executing a predetermined program, the payment device 100 cooperates with the user device 200 to settle the payment of the price generated by the provision of the food and drink service from the restaurant facility to the user (hereinafter, simply "payment settlement" or It realizes a server function that controls processing for (also called "payment"). Further, the payment device 100 cooperates with the facility terminal 300 and the service providing device 500 to provide the service providing device 500 with the user's meal data acquired from the facility terminal 300.

The user device 200 is a terminal device such as a smartphone or a laptop, and inputs such as acceptance of a payment request from a user and communicates with the payment device 100. By executing a predetermined program, the user device 200 cooperates with the payment device 100 to send and receive information and meal data related to payment, display a screen related to payment and meal, and accept a user's request. This predetermined program may be, for example, a native application program dedicated to the integrated payment system 1 for users (hereinafter referred to as "user payment application").

The facility terminal 300 is a terminal device for payment settlement installed in a restaurant owned by a business operator. The facility terminal 300 is, for example, a POS cash register terminal having a barcode reader function, a tablet terminal, a handy terminal, or the like.

The facility terminal 300 may be provided with a POS cash register function such as acceptance of input of an ordered menu and calculation of a total amount (settlement amount) of the received menu price (food and drink charge). Further, the facility terminal 300 may realize the above-mentioned POS cash register function by installing a native application program dedicated to the integrated payment system 1 for restaurants. Further, the facility terminal 300 may be configured as a terminal connected to a POS system that manages information on sales of food and drink in order to realize the above-mentioned POS cash register function.

The first external system 5a is a system for providing a health care service, which is one of meal-related services, to a user. The first external system 5a cooperates with the payment device 100 or the user device 200 to provide the user's health care data to the payment device 100 and the like. The first external system 5a includes a first service providing device 500a. The first service providing device 500a may be, for example, a measuring device for measuring the health care data of the user. The first service providing device 500a may be, for example, a so-called wearable device that is attached to the user and measures the number of steps, heart rate, etc. of the user.

The second external system 5b is a system for providing a user with a meal management service, which is one of meal-related services. The second external system 5b cooperates with the payment device 100 to record the user's meal data provided by the payment device 100. The second external system 5b includes a second service providing device 500b. The second service providing device 500b is an information processing device capable of communicating with the payment device 100, and may be, for example, a server device.

<1-2. Overview of integrated payment function>
An example of the flow of the integrated payment function (1) to (5) according to the present embodiment will be described with reference to FIG. In this example, for the sake of simplicity, it is assumed that the user payment application is pre-installed in the user device 200. Further, in this example, in order to simplify the explanation, it is assumed that the code payment using the QR code (registered trademark) registered by the user U as the payment method is associated with the bank transfer by the user U's bank account. do. Here, "code payment" means cashless payment using a one-dimensional bar code or a two-dimensional bar code (including a QR code).

(1) First, in the integrated payment function, the integrated payment system 1 acquires the health care data of the user U from the external system 5 or the user device 200.

(2) The integrated payment system 1 grants a privilege to the user U according to the acquired health care data. Here, the "privilege" is, for example, points (in this example, "miles") that can be used at each restaurant of the business operator, an electronic coupon, or the like. Further, the "mile" referred to here may be exchangeable for an electronic coupon or the like, and in this example, the first restaurant facility S1 owned by the first business operator (in this example, "vegetable restaurant"). It is assumed that the coupon has been exchanged for an electronic coupon C (a discount coupon that discounts food and drink charges by 10%) that can be used at (in this example, "vegetable restaurant Shinjuku store"). For example, when the number of steps per day of the user U exceeds a predetermined threshold value, the integrated payment system 1 grants a preset amount of miles (in this example, described as "500 miles") to the user U.

(3-1) First, the user U uses the integrated payment function for eating and drinking at the first eating and drinking facility S1. Specifically, the user U activates the user payment application of the user device 200, and the payment means selection screen A4 including the electronic payment means of each of the plurality of businesses including the first business to which the first restaurant facility S1 belongs. (See FIG. 7 (a) described later) is displayed.

(4-1) The user U selects the electronic payment means of the vegetable restaurant from the plurality of electronic payment means displayed on the payment means selection screen A4. When the integrated payment system 1 accepts the selection, in order to make a payment by the payment method of the price registered in advance in the selected electronic payment means, the integrated payment system 1 inputs a first QR code, which is a state of the first identification code described later. Generate. Here, this "pre-registered payment method" is a code payment using a user-presented (CPM (Consumer-Presented-Mode)) first QR code. The integrated payment system 1 displays the generated first QR code on the code payment screen A5 of the user device 200 (see FIG. 7B described later).

(5-1) The user U causes the first facility terminal 300a to read the first QR code displayed on the code payment screen A2 of the user device 200 when paying the food and drink charges at the first eating and drinking facility S1. Further, the user U can present the electronic coupon C output by the user payment application when paying the food and drink charges at the first eating and drinking facility S1 to discount the food and drink charges by 10%. The first facility terminal 300a transmits a payment request for payment including the read information of the first QR code to the payment device 100. Upon receiving this payment request, the payment device 100 performs processing for payment of payment for food and drink (hereinafter, also referred to as "payment processing"). Specifically, the payment device 100 is owned by a business operator (hereinafter referred to as "payment business operator") that provides an integrated payment function to the bank server of the corresponding bank with the bank account of the user U as the transfer source. Specify the bank account as the transfer destination and instruct the transfer process.

(3-2) Next, the user U uses the integrated payment function when receiving the eating and drinking service at the second eating and drinking facility S2. Specifically, the user U activates a user payment application of the user device 200, and includes an electronic payment means of a second business operator (in this example, "health cafe") to which the second restaurant facility S2 belongs. Display the payment method selection screen A4.

(4-2) The user U selects the electronic payment means of the health cafe from the plurality of electronic payment means displayed on the payment means selection screen A1. When the integrated payment system 1 accepts the selection, it generates a second QR code, which is one aspect of the second identification code described later, in order to make a payment by the payment method of the price registered in advance in the selected electronic payment means. do. Here, this "pre-registered payment method" is a code payment using a second QR code of a restaurant presentation type (MPM (Merchant-Presented-Mode)). The integrated payment system 1 displays the generated second QR code on the screen of the second facility terminal 300b. The first identification code and the second identification code are collectively referred to as "identification code" when there is no particular need to distinguish them.

(5-2) The user U causes the user apparatus 200 to read the second QR code displayed on the screen of the second facility terminal 300b when paying the food and drink charges at the second eating and drinking facility S2. The user device 200 transmits a payment request for payment settlement including the read information of the second QR code to the payment device 100. Upon receiving this payment request, the payment device 100 performs payment processing for food and drink charges. Specifically, the settlement device 100 instructs the bank server of the corresponding bank to specify the bank account of the user U as the transfer source and the bank account held by the settlement operator as the transfer destination, and instruct the transfer process.

According to the above configuration, the integrated payment system 1 can collectively provide the user U with electronic payment means for each of the vegetable restaurant and the health cafe having the eating and drinking facility that provides the eating and drinking service. Therefore, the user U does not need to install and set each application on the user device 200 in order to use the electronic payment means of each of the vegetable restaurant and the health cafe, and only installs and sets the user payment application. good. Therefore, the integrated payment system 1 can reduce the time and effort of the user U when the user U uses the electronic payment means of each of the vegetable restaurant and the health cafe.

<1-2. Overview of meal data hub function>
An outline of the meal data hub function according to the present embodiment will be described with reference to FIG. An example will be described in which the user U uses a plurality of eating and drinking facilities and also uses a plurality of recording services for recording the meal data of the user U. In this example, as shown in FIG. 2, the user U eats and drinks at the first eating and drinking facility S1, and the food and drink charges are paid and settled.

As shown in FIG. 3, (1) the payment device 100 acquires meal data in the food and drink from the first food and drink facility S1 in which the user U eats and drinks in the plurality of food and drink facilities after payment and payment of the food and drink charges. do. (2) The payment device 100 specifies a recording destination of meal data acquired from the meal-related services used by the user U based on the recording destination condition. This specified meal-related service is also referred to as "specific service". In this example, it is assumed that the healthcare service provided by the first external system 5a and the meal management service provided by the second external system 5b are specified as recording destinations among the plurality of recording services to be used.

The "recording destination condition" is a condition for specifying the service of the recording destination of the meal data. Specifically, the recording destination condition is a condition indicating at least one meal-related service used by the first user from among a plurality of meal-related services. The recording destination condition may be set for each user, for example, or the same condition may be uniformly set for a plurality of users.

(3) The payment device 100 may convert at least a part of the meal data in order to match the specifications of the specific service and the like. (4) The payment device 100 transmits the acquired / converted meal data to the specific service.

With reference to FIG. 4, the flow of processing related to the meal data hub function in the integrated payment system 1 will be described. In this example, it is assumed that the CPM method code payment is used for payment payment.

As shown in FIG. 4, first, an example of the processing flow when the user U eats and drinks at the eating and drinking facility between day and night will be described. (1a) The user U causes the user device 200 to display the first QR code when paying the food and drink charges at the first eating and drinking facility. (2a) The first facility terminal 300a reads the first QR code displayed on the user device 200. (3a) When a payment request including the information of the first QR code read from the first facility terminal 300a is transmitted to the payment device 100, the payment device 100 performs payment processing for food and drink charges based on the payment request.

Next, an example of the flow of processing for linking meal data to the recording service will be described. (1b) At the timing of twice a day (for example, noon: 15:00, night: 21:00, etc.), the first facility terminal 300a collectively transmits the meal data to be linked to the payment device 100. (2b) The payment device 100 relays the received meal data to the meal-related service. (3b) The meal-related service records the meal data relayed from the payment device 100.

Next, an example of the flow of processing in which the user U uses the meal-related service will be described. (1c) After the meal data is recorded in the meal-related service, the user U logs in to the application or website provided by the meal-related service from the user device 200 at an arbitrary timing, and inquires about the recorded meal data. Request. (2c) Upon receiving this request, the meal-related service provides the user device 200 with the meal data of the user U as a result of the inquiry.

According to the above configuration, even if the user is using a plurality of meal-related services, the payment device 100 can link the meal data at the eating and drinking facility to the service specified as the recording destination. Therefore, according to the above configuration, the service provider of the meal-related service that records the meal has a plurality of foods and drinks used by the user in his / her own system (external system 5) in order to acquire the user's meal data. It is not necessary to implement the function of linking meal data with each facility (or its business operator) from the beginning. Therefore, according to the above configuration, the payment device 100 can support the recording of the user's meal at the eating and drinking facility for a plurality of meal-related services.

<2. Function configuration>
The functional configuration of the payment apparatus 100 according to the present embodiment will be described with reference to FIG. As shown in FIG. 5, the payment device 100 includes a control unit 110, a communication unit 130, and a storage unit 140.

The control unit 110 includes a recording destination specifying unit 111, a request receiving unit 112, a payment processing unit 113, and a health care data acquisition unit 114. Further, the control unit 110 is, for example, a condition reception unit 115, a usage information acquisition unit 116, a facility identification unit 117, a storage unit 118, a data generation unit 119, a calculation unit 120, a designated reception unit 121, a display unit 122, and a payment means reception unit. A unit 123, a code generation unit 124, or a privilege granting unit 125 may be provided.

-Recording destination identification part-
The recording destination specifying unit 111 identifies at least one service that is a recording destination of meal data related to the meal of the first user from among a plurality of meal-related services that provide the recording service to the user, based on the recording destination condition. ..

-Request reception department-
When the first user pays the price for meals at the restaurant (also referred to as “food and drink”) from the facility terminal 300 of the restaurant, the request reception unit 112 requests payment for payment (hereinafter, simply “payment request””. Also called) is accepted. The mode in which the request receiving unit 112 receives the payment request from the user device 200 or the facility terminal 300 may be any mode, for example, receiving a message indicating the payment request from the user device 200 or the like via the communication unit 130. May be good.

The payment request may include, for example, the business operator identification information of the first identification code output by the user device 200 and read by the facility terminal 300. Here, the "business identification information" is information for identifying a business, and is also hereinafter also referred to as a "business ID".

The "first identification code" is a one-dimensional bar code or a two-dimensional bar code for performing CPM code payment when a user pays for a product or the like to a restaurant. The first identification code includes a business operator ID for identifying a business operator in an electronic payment means selected by a user, and payment identification information (hereinafter, also referred to as "payment ID") for identifying payment payment.

The request receiving unit 112 may receive a payment request from, for example, the user device 200. This payment request includes the business ID of the second identification code read by the user device 200 from the facility terminal 300.

The "second identification code" is a one-dimensional bar code or a two-dimensional bar code for performing MPM-type code payment when a user pays a food and drink fee to a restaurant. The second identification code is an identification code generated by the facility terminal 300, and includes a business ID and a payment ID of the business to which the restaurant belongs.

-Payment processing unit-
The payment processing unit 113 performs payment processing for payment settlement based on the payment request received by the request reception unit 112. The payment processing unit 113 may generate payment information for the payment processing, for example, when the payment processing is performed.

The "payment information" is information indicating the content of the payment of the payment processed by the payment processing unit 113. The payment information includes, for example, a user ID indicating a user who made a payment, menu identification information indicating a menu to be settled (for example, a menu name or a menu ID), a payment date / time indicating the date and time when the corresponding payment was made, and a payment amount. , The facility ID for identifying the restaurant where the corresponding payment was made, the transaction ID for identifying the series of processes (transactions) including the processing by the payment processing unit 113, and the facility terminal where the corresponding payment was made. It may include a terminal number indicating 300.

The payment processing unit 113 may perform payment processing by, for example, an electronic payment means selected by the user. For example, when the selected electronic payment means uses payment by bank transfer, the payment processing unit 113 instructs the bank server of the destination bank to process the bank transfer. Further, for example, when the selected electronic payment means uses payment by credit card payment, the payment processing unit 113 instructs the corresponding credit card system to perform credit card payment processing.

According to the above configuration, when the user uses the electronic payment means provided by the plurality of businesses for eating and drinking at the restaurant, the user selects and requests the electronic payment means for payment of the food and drink charges. You can settle the payment for food and drink. Therefore, when using the electronic payment means provided by the plurality of businesses, the user does not need to install the application for each business, and the trouble of using the application can be reduced.

For example, the payment processing unit 113 performs payment processing by the payment method and authentication information registered by the payment method reception unit 123, which will be described later, in the electronic payment means selected by the user based on the payment request received by the request reception unit 112. You may go.

According to the above configuration, when a payment request is made, the payment processing unit 113 can smoothly settle the payment by using a pre-registered payment method or the like in the electronic payment means selected by the user. can. Therefore, according to the above configuration, the payment processing unit 113 can provide a payment service that is easy for the user to use.

In the payment processing unit 113, for example, the business operator indicated by the business operator identification information of the first identification code included in the payment request received by the request reception unit 112 matches the business operator to which the restaurant facility from which the payment request is requested belongs. If so, payment processing by code payment may be performed. Further, in such a case, the payment processing unit 113 may perform payment processing by code payment by, for example, an electronic payment means selected by the user. The settlement processing unit 113 may refer to the eating and drinking facility information when determining whether or not the business operators match.

"Food and drink facility information" is information indicating each restaurant, for example, facility identification information for identifying a restaurant (hereinafter, also referred to as "facility ID"), a facility name indicating the name of a restaurant, or The business ID of the business to which the restaurant belongs may be included.

According to the above configuration, the payment processing unit 113 selects the food and drink facility to be paid to and the user when the user pays the food and drink fee to the food and drink facility by using the CPM method code payment in the payment of the food and drink fee. Consistency with electronic payment means can be achieved.

The payment processing unit 113 is, for example, when the business operator indicated by the business operator ID of the second identification code included in the payment request received by the request reception unit 112 and the business operator of the electronic payment means selected from the user match. Payment processing by code payment may be performed.

According to the above configuration, the payment processing unit 113 selects the food and drink facility to be paid to and the user when the user pays the food and drink fee to the food and drink facility by using the MPM method code payment in the payment of the food and drink fee. Consistency with electronic payment means can be achieved.

-Healthcare data acquisition department-
The health care data acquisition unit 114 acquires at least one of the user's health care data from the external system 5 or the user device 200. Regarding the mode in which the health care data acquisition unit 114 acquires the health care data, any mode may be used, and for example, a data file of the health care data may be received from the external system 5 or the user device 200. Further, as another example, the health care data acquisition unit 114 may remotely access the external system 5 or the user device 200 to acquire the health care data data file, or may acquire the health care data data file externally. The API implemented by the system 5 or the user apparatus 200 may be instructed to refer to the health care data, and as a result, the health care data may be acquired. The health care data acquisition unit 114 includes a meal data acquisition unit 1141.

-Meal data acquisition department-
The meal data acquisition unit 1141 acquires meal data related to meals at the eating and drinking facility from the facility terminal 300 when the payment processing is performed by the payment processing unit 113. When acquiring the meal data, the meal data acquisition unit 1141 acquires the meal data directly from the facility terminal 300, and also obtains the meal data via the business server 400 to which the facility terminal 300 belongs (the business server 400 connected to the facility terminal 300). You may get it.

For example, when the payment processing is performed by the payment processing unit 113, the meal data acquisition unit 1141 may acquire the meal data from the facility terminal 300 of the eating and drinking facility specified by the facility identification unit 117. In other words, the meal data acquisition unit 1141 does not have to acquire meal data from the facility terminal 300 of the eating and drinking facility not specified by the facility identification unit 117 even when the payment processing is performed by the payment processing unit 113.

For example, from the viewpoint of confidentiality, the user may have a meal that he / she does not want to cooperate with the payment device 100 or the meal-related service. In such a case, according to the above configuration, since the meal data acquisition unit 1141 does not acquire the meal data from the eating and drinking facility filtered by the acquisition source condition, it provides a user-friendly meal data hub function. be able to.

-Condition reception department-
The condition receiving unit 115 receives the recording destination condition from the first user device 200a of the first user. The mode in which the condition receiving unit 115 receives the recording destination condition is the same as that in the request receiving unit 112, and any mode may be used. The condition reception unit 115 is, for example, from the first user device 200a, as a meal-related service used by the first user, "being a healthcare service provided by the first external system 5a" or "the second external system 5b". You may accept the recording destination condition that "it is a meal management service to be provided".

According to the above configuration, the condition reception unit 115 can allow the user to manually select the meal-related service to be recorded. Therefore, according to the above configuration, the condition reception unit 115 can specify the meal-related service of the recording destination in a form according to the user's intention.

The condition receiving unit 115 may receive, for example, the acquisition source condition from the first user device 200a of the first user.

The "acquisition source condition" is a condition for specifying the eating and drinking facility from which the meal data is acquired. Specifically, the acquisition source condition may be a condition indicating at least one eating and drinking facility used by the first user from among a plurality of eating and drinking establishments. The acquisition source condition may be set for each user, for example, or the same condition may be uniformly set for a plurality of users.

-Usage information acquisition unit-
The usage information acquisition unit 116 acquires service usage information indicating the service usage record included in the recording destination condition from the user device 200 or the service providing device 500. Here, the "service usage record" is a record of the first user using the function of the service providing device 500. The usage information may include, for example, the last usage date and time indicating the last date and time when the function of the service providing device 500 is used as the service usage record. In this case, for example, the recording destination condition may include a condition that "the service is a meal-related service of the service providing device 500 whose last usage date and time is within a predetermined period (for example, the past one year or the like)".

According to the above configuration, the usage information acquisition unit 116 can automatically specify the meal-related service of the recording destination based on the usage information. Therefore, according to the above configuration, the usage information acquisition unit 116 can specify the meal-related service of the recording destination according to the usage record without taking the trouble of the user.

The usage information acquisition unit 116 may acquire facility usage information indicating the facility usage record included in the acquisition source condition from the user device 200 or the service providing device 500, for example. Here, the "facility usage record" is a record of the first user using the restaurant. The facility usage information may include, for example, the average amount of food and drink charges paid to the restaurant during a predetermined period (for example, the past 5 years, etc.) as the facility usage record. In this case, for example, the acquisition source condition may include a condition that "the facility must have an average amount of 000 yen or more".

-Facility identification department-
The facility specifying unit 117 identifies the restaurant from which the meal data is acquired from among the plurality of restaurants based on the acquisition source conditions.

-Accumulation part-
The storage unit 118 stores the meal data acquired by the meal data acquisition unit 1141 in the meal data storage unit 141 for a predetermined period.

-Data generator-
When the meal data cannot be acquired by the meal data acquisition unit 1141, the data generation unit 119 generates temporary meal data instead of the meal data that cannot be acquired based on the accumulated meal data. The data generation unit 119 is, for example, a statistical value (for example, a mode value, an average value, etc.) of accumulated meal data in a restaurant facility that could not be acquired (or another restaurant facility set to be similar to this restaurant facility). May be used as temporary meal data. The data generation unit 119 searches, for example, the menu name having the highest appearance frequency (order frequency) in the accumulated meal data. Then, the data generation unit 119 may set the menu name extracted as a result of the search and the items of the ingested nutrients such as calories and proteins associated with the menu name as temporary meal data. Here, the "nutrient item" specifically refers to the dietary data No. 1 shown in FIG. Refers to items such as 4 to 10. In addition, the data generation unit 119 calculates the average value of each nutrient item in the accumulated dietary data, and as provisional dietary data, the calculated average value is used for each nutrient item and the menu name is "tentative". An appropriate character string such as "menu" may be set.

-Calculator-
The calculation unit 120 calculates the amount of meals per person in a meal based on the meal data and the number of users. For example, when the number of users is "3", the calculation unit 120 calculates the value per person by dividing the value of each nutrient item in the meal data by 3 in each menu. The calculation unit 120 may calculate the amount of meals per person by summing up the values per person for all the menus eaten and eaten for each item of nutrients. For example, if menus A to B are ordered in one meal and the calorie of menu A is 300 kcal, the calorie of menu B is 900 kcal, and the calorie of menu C is 1,200 kcal, each calorie value is used by the number of users. You may divide by "3" and calculate the total value, that is, 100 kcal + 300 kcal + 400 kcal = 800 kcal as the amount of meal (calorie intake) per person.

-Designated reception department-
The designated reception unit 121 is at least the day of the week, the date of the meal, or the time of the meal to be transmitted from the first user device 200a or the second user device 200b to the second user device 200b by the meal data transmission unit 131. Accepts any one designation. The mode in which the designated reception unit 121 accepts the designation of the day of the week for meals and the like is the same as that in the request reception unit 112, and any mode may be used. The "meal time zone" here means, for example, breakfast (for example, 6:00 to 12:00), lunch (for example, 12:00 to 14:00), or dinner (for example, 16:00 to 23). : 00) may be used.

-Display section-
The display unit 122 refers to the payment means storage unit 143 that stores the payment means correspondence information, and causes the first user device 200a to display a plurality of electronic payment means corresponding to the first user. Specifically, the display unit 122 refers to the payment means storage unit 143 to generate electronic payment means output information. The display unit 122 transmits the generated electronic payment means output information to the first user device 200a via the communication unit 130. In this way, the display unit 122 causes the first user device 200a to display a plurality of electronic payment means corresponding to the first user.

The "payment support means information" is information indicating the correspondence relationship between the user and the electronic payment means of each of the plurality of businesses that own the food and drink facilities that provide the food and drink service to the user. The payment method correspondence information identifies, for example, "user identification information (hereinafter, also referred to as" user ID ")" for identifying a user and an electronic payment method for each business operator that can be used by the user with the user ID. This is information associated with the electronic payment means identification information (hereinafter, also referred to as “electronic payment means ID”). In this correspondence, the relationship between the user ID and the electronic payment means ID is one-to-N or N-to-N (a number of N: 1 or more). Further, the payment means correspondence information may be information for associating the user information with the electronic payment means information. Further, the above-mentioned correspondence between the user and the electronic payment means in the payment means correspondence information can be changed. For example, when the designated reception unit 121 receives a designation from the user device 200 to newly add an electronic payment means, the designated reception unit 121 specifies payment means correspondence information so that the user is newly associated with the designated electronic payment means. May be updated.

"User information" is information about a user. The user information includes, for example, a user ID, a user name indicating the user's name, and / or account identification information for identifying an account held by the user (for example, an account ID, an account number, etc.). User information may include, for example, a user's nickname, gender, date of birth, and / or body shape data representing each user's body shape (eg, height, weight, abdominal circumference, waist, hips, or foot size, etc.). .. The user information may include, for example, a token issued by the service providing device 500. This token may be issued by user authentication when the user accesses the service providing device 500.

"Electronic payment method information" is information indicating electronic payment methods for each business operator. The electronic payment method information is, for example, business identification information for identifying the corresponding business operator (hereinafter, also referred to as "business operator ID"), a business operator name indicating the business operator name, and a business operator common name. It may include a person's common name, logo image data indicating a business operator's logo, one or more electronic payment means IDs, payment method information indicating a payment method registered by the payment means reception unit 123 described later, and the like.

The "electronic payment means output information" is information indicating a plurality of electronic payment means corresponding to the user. The electronic payment means output information may be, for example, a screen displaying a list of "electronic payment means names (for example," business name "+" Pay ", etc.)" indicating the plurality of electronic payment means.

The display unit 122 displays, for example, various screens such as a home screen, a meal data screen, a coupon screen, a payment method selection screen, a code payment screen, an acquisition source designation screen, a recording destination designation screen, and / or a notification designation screen, which will be described later. It may be displayed at 200.

-Payment method reception department-
The payment means reception unit 123 receives from the user device 200 the selection of the electronic payment means to be used by the user from among the plurality of electronic payment means displayed by the display unit 122. As for the mode in which the payment means reception unit 123 accepts the selection of the electronic payment means, any mode may be used as in the request reception unit 112, and for example, the payment may be received via the user payment application installed in the user device 200. ..

The payment means reception unit 123 may accept registration of payment methods and authentication information that can be used by the user, for example, from the user device 200. The payment means reception unit 123 may, for example, accept registration of the payment method and authentication information for each of the electronic payment means corresponding to the user.

"Payment methods that can be used by users" include, for example, card payment by credit card or debit card, payment by bank transfer, cardless payment, payment by prepaid account, and / or payment by electronic money (including virtual currency). Various methods such as are conceivable. Further, the payment method that can be used by the user may be a method by code payment associated with the above-mentioned card payment, bank transfer payment, or the like. The payment means reception unit 123 may accept registration of account management information necessary for using the payment method in addition to registration of a payment method that can be used by the user.

"Authentication information" is information for receiving user authentication when using the above payment method. The authentication information may include, for example, an account ID for identifying a user account and a password for the user account.

"Account management information" is information for managing various accounts. The account management information includes, for example, an account ID, a user name, a user's date of birth, an address indicating a user's E-mail address, a user's telephone number, an account balance, and / or an account deposit / withdrawal history. Further, the account management information may include, for example, authentication information for accessing the account information of the user's account managed by a bank server or the like.

-Code generator-
The code generation unit 124 refers to the payment method storage unit 144 that stores the payment method information, and when the payment method that can be used by the user is a code payment method, the payment method reception unit 123 accepts the selection of the electronic payment method. At that time, an identification code for code payment including the business identification information in the selected electronic payment means is generated. Here, the "payment method information" is information indicating a payment method that can be used by the user. For example, when the available payment method is a method by code payment using the first identification code, the code generation unit 124 generates the first identification code when the payment means reception unit 123 accepts the selection of the electronic payment means. You may.

-Bonus granting department-
When the health care data acquired by the health care data acquisition unit 114 satisfies the privilege condition, the privilege granting unit 125 grants the user a privilege that can be used for payment.

The "privilege condition" is a condition for granting a privilege to the user. The privilege condition may be, for example, a threshold value of the number of steps per day of the user, which is activity data (for example, "3000 steps or more"). For example, if the privilege condition is "the equivalent amount of salt in one meal is 3.0 g or less", the privilege granting unit 125 determines that the equivalent amount of salt contained in the meal data is 3.0 g or less, the user. May be awarded 100 miles.

The privilege granting unit 125 may grant the privilege to the user's behavior other than the behavior that contributes to the user's health care, and for example, the privilege granting unit 125 may also grant the privilege to the behavior that promotes the use of the payment function of the integrated payment system 1. Benefits may be given to the user. For example, the privilege condition includes the condition "to activate the user payment application", and the privilege granting unit 125 grants the privilege to the user each time the user activates the user payment application on the user device 200. May be good. In addition, as another example, the privilege condition includes conditions such as "the user checks in to a specific place" and / or "reads the first identification code" and "generates the second identification code". May be included.

For example, if the meal data acquired by the meal data acquisition unit 1141 satisfies the privilege condition, the privilege granting unit 125 may grant the user a privilege that can be used for payment. According to such a configuration, the privilege granting unit 125 can promote the improvement of the user's eating habits by granting the privilege.

-Communication unit-
The communication unit 130 transmits and receives various information to and from the user device 200, the operator server 400, the external system 5, and the like via the network N. The communication unit 130 receives, for example, a payment request from the user device 200 via the network N, or transmits information indicating a processing result of payment by the payment request to the user device 200. The communication unit 130 transmits the electronic payment means output information to the user device 200 in order to select the electronic payment means to be used by the user from the plurality of electronic payment means. Further, the communication unit 130 includes a meal data transmission unit 131 and a code transmission unit 132.

-Meal data transmitter-
The meal data transmission unit 131 transmits the meal data to each service providing device 500 of at least one service specified by the recording destination specifying unit 111.

According to the above configuration, the meal data transmission unit 131 links the meal data at the eating and drinking facility to the meal-related service specified as the recording destination even if the user is using the meal-related service including a plurality of recording services. can do. Therefore, according to the above configuration, the meal data transmission unit 131 can support the recording of the user's meal at the eating and drinking facility for the plurality of services for recording the meal.

For example, the meal data transmission unit 131 may transmit temporary meal data generated by the data generation unit 119 to the service providing device 500 instead of the meal data acquired by the meal data acquisition unit 1141. Further, as another example, the meal data transmission unit 131 may transmit the default meal data common in the system to the service providing device 500 instead of the meal data acquired by the meal data acquisition unit 1141.

It is conceivable that some eating and drinking establishments cannot acquire meal data because they do not support the meal data hub function. With respect to eating and drinking in such a eating and drinking facility, according to the above configuration, the meal data transmitting unit 131 can transmit temporary meal data to the service providing device 500 instead even if the meal data cannot be acquired. When analyzing daily dietary statistics in dietary management services, health care services, etc., it is possible that the accuracy of the analysis results will be affected if there is no record of dietary data. In such a case, according to the above configuration, even if the meal data transmission unit 131 cannot acquire the meal data, the influence on the accuracy of the analysis result can be reduced by transmitting the provisional meal data. ..

The meal data transmission unit 131 may transmit, for example, meal data including the meal amount per person calculated by the calculation unit 120. For example, when a plurality of people eat and drink at a restaurant, if the meal data to be settled for payment is used as it is, meal data indicating the amount of meal that the first user does not actually ingest is transmitted to the service providing device 500. Will be done. According to such a configuration, the meal data transmission unit 131 can transmit the meal data indicating the amount calculated as the meal amount per person even when a plurality of people eat, to the service providing device 500, and thus the user's meal. It is possible to record more appropriate dietary data in management and healthcare.

The meal data transmission unit 131 refers to, for example, the user storage unit 142 that stores the first user and the second user in association with each other, and the meal data of the first user is stored in the second user apparatus 200b of the second user. You may send at least a part of. The meal data transmission unit 131 may, for example, send a message indicating the meal content (for example, a menu name, etc.) included in the meal data to the E-mail address of the second user. Further, as another example, the meal data transmission unit 131 may cause the user payment application of the second user device 200b to make a push notification including the meal data.

According to the above configuration, the meal data transmission unit 131 can easily share the meal contents of the first user with a second user such as a family member or a friend.

The meal data transmission unit 131 may transmit at least a part of the meal data of the first user to the second user apparatus 200b, for example, based on the designation received by the designated reception unit 121.

In sharing the meal contents of the first user with the second user, it is conceivable that information overload may occur if all the meals of the first user handled by the integrated payment system 1 are targeted. According to the above configuration, the meal data transmission unit 131 can share only the meal that the first user or the second user wants to share.

-Code transmitter-
The code transmission unit 132 transmits the identification code generated by the code generation unit 124 to the first user device 200a that has received the selection of the electronic payment means by the payment means reception unit 123.

-Memory unit-
The storage unit 140 stores authentication information, account management information, restaurant facility information, and / or electronic payment means output information. The storage unit 140 may include a meal data storage unit 141, a user storage unit 142, a payment means storage unit 143, and / or a payment method storage unit 144. The meal data storage unit 141 stores meal data. The user storage unit 142 stores the user information of the first user and the user information of the second user in association with each other. The payment means storage unit 143 stores payment information and payment means correspondence information. The payment method storage unit 144 stores payment method information. The storage unit 140 may store each information by using a database management system (DBMS), or may store the above information by using a file system. When using a DBMS, a table may be provided for each of the above information, and the above information may be managed by associating the tables with each other.

<3. Screen example>
A screen example of the integrated payment system 1 will be described with reference to FIGS. 6 to 9.

As shown in FIG. 6A, the home screen A1 is a screen that is first displayed when the user logs in to the integrated payment system 1 via the payment application. The home screen A1 has, for example, a total owned mileage display area a11 showing the total amount of benefits owned by the user (referred to as “miles” in this example), and an activity data screen (not shown) displaying user activity data. The activity data screen display button a12 for displaying, the meal data screen display button a13 for displaying the meal data screen A2 for displaying the user's meal data, and the body data screen (not shown) for displaying the user's body data. A physical data screen display button a14 for displaying the above, and a coupon list display area a15 showing a list of coupons that can be exchanged for miles owned by the user are included.

When the meal data screen display button a12 is pressed, the display unit 122 transitions to the meal data screen A2. Further, when the button of each coupon displayed in the coupon list display area a15 is designated (pressed), the display unit 122 transitions to the coupon screen A3 for displaying the contents of the designated coupon.

As shown in FIGS. 6 (b) and 6 (c), the meal data screen A2 displays the user's meal data. As shown in FIG. 6B, the meal data screen A2 may display the total value ingested in one day's meal (in this example, 2020/11/18) for each nutrient item. As shown in FIG. 6C, the meal data screen A2 may display a menu name for each meal (breakfast / lunch) and an item for each nutrient. Further, as shown in FIG. 6D, the coupon screen A3 displays the contents of the coupon designated from the above coupon list.

As shown in FIG. 7A, the payment means selection screen A4 is a screen for displaying a plurality of electronic payment means corresponding to the user. Further, the payment means selection screen A4 is also a screen for accepting the selection of the electronic payment means to be used when paying the food and drink charges at the eating and drinking facility from the user. The payment means selection screen A4 is one aspect of the electronic payment means output information. The payment method selection screen A4 has an additional designation button a41 for newly adding an electronic payment method (in this example, described as "member store Pay"), and an electronic payment that displays a list of electronic payment methods corresponding to the user. The means list display area a42 is included.

When the addition designation button a41 is pressed, the display unit 122 transitions to an electronic payment means addition screen (not shown) for adding a new electronic payment means.

The electronic payment means list display area a42 includes a first electronic payment means selection button a421 of the first business operator (vegetable restaurant) corresponding to the user, and a second electronic payment means selection button a422 of the second business operator (health cafe). , The third electronic payment method selection button a423 of the third business operator (company A employee cafeteria).

When the first electronic payment means selection button a421 is pressed, the display unit 122 transitions to the code payment screen A5 for payment payment in the electronic payment means of the vegetable restaurant.

As shown in FIG. 7B, the code payment screen A5 is a screen for making payment payment in the electronic payment means of the vegetable restaurant. In this example, it is assumed that a bank transfer by code payment is registered as a payment method in the electronic payment method of the vegetable restaurant. The code payment screen A5 includes a payment method display area a51 for displaying the registered payment method, and a first identification code display area a52 for displaying the first identification code generated by the code generation unit 124. As shown in FIG. 7C, when the first identification code displayed on the code payment screen A5 is read by the facility terminal 300 and the processing for payment payment is completed, the display unit 122 is completed. The payment completion notification dialog a53 may be displayed to that effect. Further, as another example, when the processing for payment settlement is completed, the display unit 122 does not display the payment completion notification dialog a53, but the payment completion screen indicating the completion from the code payment screen A5. The transition may be made to (not shown).

As shown in FIG. 8A, the acquisition source designation screen A7 is a screen for designating the eating and drinking facility from which the meal data is acquired. The acquisition source selection screen A7 has an acquisition source exclusion input form a71 for designating and inputting a restaurant to be excluded from the acquisition source, and a registration button a72 for registering the contents input in the acquisition source exclusion input form a71. include. For example, when "Company A employee cafeteria" is specified and input in the acquisition source exclusion input form a71 and the registration button 72 is pressed, the condition reception unit 115 accepts the designation to exclude "Company A employee cafeteria" from the acquisition source. Then, the condition that "it is not a company A employee cafeteria" is additionally set as the acquisition source condition.

As shown in FIG. 8B, the recording destination designation screen A8 is a screen for designating a meal-related service as a recording destination of meal data. The recording destination designation screen A8 has a recording destination designation input form a81 for designating and inputting a meal-related service as a recording destination, and a registration button 82 for registering the contents input in the recording destination designation input form a81. include. For example, when "health care service" and "meal management service" are designated and input in the record destination designation input form a81 and the registration button a82 is pressed, the condition reception unit 115 states that "it is a health care service". Set the recording destination condition that "it is a meal management service".

As shown in FIG. 8C, the notification designation screen A9 is a screen for designating the notification of the meal content of the first user to the second user. The notification designation screen A9 has a notification destination designation input form a91 for designating and inputting a second user (user U2a and user U2b in this example) of the notification destination, and a notification target designation for designating and inputting a meal to be notified. It includes an input form a92 and a registration button a93. When the user U2c is newly designated and input in the notification destination designation input form a91 and the registration button a82 is pressed, the designated reception unit 121 adds the user U2c to the second user of the notification destination.

<5. Data configuration example>
An example of a data configuration of the integrated payment system 1 will be described with reference to FIGS. 9 to 10. In addition, in the various information described in this example, it is not necessary to include all the items included in the various information exemplified in FIGS. 9 to 10, and items other than these may be included, and various information is used. It may be set appropriately according to the processing or the like.

As shown in FIG. 9, the meal data includes the transaction ID, the number of users, the menu name indicating the name of the menu, the calories in the menu, the protein, the carbohydrate, the dietary fiber, the fat, and the sugar. , Salt equivalent and the transaction date and time indicating the transaction execution date and time. In addition, this transaction date and time may be regarded as a meal date and time indicating the date and time when the first user ate at the eating and drinking facility.

As shown in FIG. 10, the user information includes a user ID, a user name, a date of birth, and a token. Further, the payment means correspondence information includes a user ID, an electronic payment means name, an electronic payment means ID, a business operator ID, and an advertisement ID. The payment information includes a payment ID, a payment date / time (date), a payment date / time (hour / minute / second), a business ID, a business name, a payment amount, a user ID, and a transaction ID. ..

<6. Operation example>
An operation example of the integrated payment system 1 according to the present embodiment will be described with reference to FIGS. 11 to 13.

<6-1. Flow ＞
In FIG. 11, when the payment device 100 pays the food and drink charges at the restaurant, the electronic payment means selected by the user performs a process for payment and payment of the food and drink charges, and after the payment is settled. , It is a flow chart which shows the example of the flow of the processing which links the meal data of the meal in the restaurant with the meal-related service. The code payment described in this example uses the CPM method. The order of the processes shown below is an example and may be changed as appropriate.

As shown in FIG. 11, the display unit 122 of the payment device 100 generates electronic payment output information (S10). The communication unit 130 transmits the generated electronic payment output information to the user device 200 in order to select the electronic payment means to be used by the user from among the plurality of electronic payment means (S11). The payment means reception unit 123 accepts the selection of the electronic payment means to be used by the user from the user device 200 (S12).

When the registered payment method is a code payment method (Yes in S13), the code generation unit 124 generates a first identification code when the payment method reception unit 123 accepts the selection of the electronic payment method (S14). ). The communication unit 130 transmits the first identification code to the user device 200 that has accepted the selection of the electronic payment means (S15).

The request receiving unit 112 receives a payment request including the business ID of the first identification code from the facility terminal 300 that has read the first identification code displayed on the user device 200 (S16).

The payment processing unit 113 is selected according to the payment request when the business operator indicated by the business operator ID of the first identification code and the business operator to which the restaurant facility requesting the payment request belongs match (Yes in S17). A payment process is performed by code payment in the electronic payment means (S18). The payment processing unit 113 transmits the processing result of the payment to the user device 200 and the facility terminal 300 via the communication unit 130 (S19).

When the business operator indicated by the business operator ID of the first identification code and the business operator to which the restaurant facility requesting the payment request belongs do not match (No in S17), the payment processing unit 113 generates an error message indicating a payment error. (S20). The communication unit 130 transmits the error message to the user device 200 and the facility terminal 300 (S21).

When the registered payment method is not a code payment method (No in S13), the request receiving unit 112 receives a payment request from the user device 200 (S22). In response to the payment request, the payment processing unit 113 performs payment processing for payment settlement using the payment method and authentication information registered in the selected electronic payment means (S23). The payment processing unit 113 transmits the result of the processing to the user device 200 and the facility terminal 300 via the communication unit 130 (S24).

The recording destination specifying unit 111 identifies at least one service that is a recording destination of meal data related to the user's meal from among a plurality of meal-related services that provide a service for recording meals to the user, based on the recording destination conditions. (S22). The meal data acquisition unit 1141 acquires the meal data related to the meal at the eating and drinking facility from the facility terminal 300 when the payment process is performed (S23). The meal data transmission unit 131 transmits the meal data to each service providing device 500 of the specified at least one service (S24).

<6-2. Interaction>
12 to 13 show that in the integrated payment system 1, the meal data of the meal paid and settled by the user at the restaurant is linked to the service providing device 500 by using the token issued when the user is authenticated to the service providing device 500. It is a sequence diagram which shows the interaction of a payment apparatus 100, a user apparatus 200, a facility terminal 300, and a service providing apparatus 500 at the time. In this example, the payment method is payment by CPM code payment.

As shown in FIG. 12, when the user U accesses the meal-related service of the service providing device 500, the user device 200 of the user U sends an authentication request for user authentication to the meal-related service to the service providing device 500. Do (S30). Upon receiving this authentication request, the service providing device 500 processes the user authentication and issues a token for cooperation with the payment device 100 to the user U (S31). The service providing device 500 transmits the issued talk and responds with the result of user authentication (S32).

The user device 200 makes a talk registration request received from the service providing device 500 to the payment device 100 (S33). The payment device 100 registers the token requested to be registered in the user information of the user U (S34).

The user device 200 displays the first identification code when paying the food and drink charges at the restaurant (S35). The facility terminal 300 reads the displayed first identification code (S36). When the facility terminal 300 reads the first identification code, it transmits a payment request to the payment device 100 (S37). Upon receiving the payment request, the payment device 100 executes the payment process (S38). When the payment process is executed, the payment device 100 generates payment information. The payment device 100 transmits the generated payment information to the facility terminal 300 (S39). The facility terminal 300 registers the received payment information in association with the meal data to be paid (S40). At this time, the facility terminal 300 uses the transaction ID to configure meal data collected for each transaction.

As shown in FIG. 13, the facility terminal 300 extracts meal data for each transaction to be linked (S50). The facility terminal 300 transmits the extracted meal data for each transaction to the payment device 100 (S51).

Upon receiving the meal data for each transaction, the payment device 100 converts the transaction ID into a token, that is, derives the token of the corresponding user using the transaction ID as a key (S52). Since the token is information for identifying the user for the service providing device 500, the payment device 100 converts it into meal data collected for each token (that is, for each user) (S53). The payment device 100 transmits meal data including tokens collected for each user to the service providing device 500 for the meal-related service specified as the recording destination for each user (S54). When the service providing device 500 receives the transmitted meal data, it registers the transmitted meal data in its own storage unit as information of the user U (S55).

In order for the user to confirm the meal content in the meal-related service, the user device 200 requests the service providing device 500 to inquire about the meal data (S56). Upon receiving the inquiry request, the service providing device 500 extracts the meal data of the user U (S57). The service providing device 500 transmits the extracted meal data and responds with the inquiry result (S58).

<7. Hardware configuration>
With reference to FIG. 14, an example of the hardware configuration in the case where the payment device 100 described above is realized by the computer 800 will be described. The function of each device can be realized by dividing it into a plurality of devices.

As shown in FIG. 14, the computer 800 includes a processor 801 and a memory 803, a storage device 805, an input I / F unit 807, a data I / F unit 809, a communication I / F unit 811 and a display device. Includes 813.

The processor 801 controls various processes in the computer 800 by executing a program stored in the memory 803. For example, each functional unit included in the control unit 110 of the payment device 100 can be realized by the processor 801 executing a program temporarily stored in the memory 803.

The memory 803 is a storage medium such as, for example, a RAM (Random Access Memory). The memory 803 temporarily stores the program code of the program executed by the processor 801 and the data required when the program is executed.

The storage device 805 is a non-volatile storage medium such as a hard disk drive (HDD) or a flash memory. The storage device 805 stores an operating system and various programs for realizing each of the above configurations. In addition, the storage device 805 stores a table for registering meal data, user information, payment information, electronic payment method information, payment method correspondence information, account management information, various output information, etc., and a DB for managing the table. It is also possible to do. Such programs and data are referenced from the processor 801 by being loaded into the memory 803 as needed.

The input I / F unit 807 is a device for receiving input from the user. Specific examples of the input I / F unit 807 include a keyboard, a mouse, a touch panel, various sensors, a wearable device, and the like. The input I / F unit 807 may be connected to the computer 800 via an interface such as USB (Universal Serial Bus).

The data I / F unit 809 is a device for inputting data from the outside of the computer 800. Specific examples of the data I / F unit 809 include a drive device for reading data stored in various storage media. It is also conceivable that the data I / F unit 809 is provided outside the computer 800. In that case, the data I / F unit 809 is connected to the computer 800 via an interface such as USB.

The communication I / F unit 811 is a device for performing data communication via the Internet N by wire or wirelessly with an external device of the computer 800. It is also conceivable that the communication I / F unit 811 is provided outside the computer 800. In that case, the communication I / F unit 811 is connected to the computer 800 via an interface such as USB.

The display device 813 is a device for displaying various information. Specific examples of the display device 813 include a liquid crystal display, an organic EL (Electro-Luminescence) display, a display of a wearable device, and the like. The display device 813 may be provided outside the computer 800. In that case, the display device 813 is connected to the computer 800 via, for example, a display cable or the like. Further, when the touch panel is adopted as the input I / F unit 807, the display device 813 can be integrally configured with the input I / F unit 807.

It should be noted that the present embodiment is an example for explaining the present invention, and is not intended to limit the present invention to only the embodiment thereof. Further, the present invention can be modified in various ways as long as it does not deviate from the gist thereof. Further, those skilled in the art can adopt an embodiment in which each element described below is replaced with an equal one, and such an embodiment is also included in the scope of the present invention.

The component included in the payment device 100 described in the above embodiment is that the program stored in the storage device 805 is executed by the processor 801 to realize the defined processing in cooperation with other hardware. It shall be done. In other words, these components are assumed to be software or firmware and corresponding hardware, and in both concepts, "function", "means", "part", "processing circuit", It is also described as "unit" or "module", and can be read as "unit" or "module".

[Modification example]
Although the present invention has been described based on the above embodiment, the following cases are also included in the present invention.

[Modification 1]
The user device 200 may include at least a part of each configuration in the payment device 100 according to the above embodiment. For example, the user payment application of the user device 200 may be provided with all the functions of the display unit 122 and the code generation unit 124 of the payment device 100.

[Modification 2]
An example has been described in which the meal data storage unit, the user storage unit, the payment means storage unit, and the payment method storage unit according to the above embodiment are all functional units included in the storage unit 140 of the payment device 100, but for example, the user device. 200 storage units (not shown) may be provided. Further, as another example, the meal data storage unit, the user storage unit, the payment means storage unit, and the payment method storage unit according to the above embodiment may be provided with a storage unit (not shown) of the business server 400. A storage unit (not shown) of the external system 5 may be provided.

[Modification 3]
The meal data in which the payment device 100 according to the above embodiment is linked to the service providing device 500 is set as one record for each menu, and an example of including the menu name and the nutrient item associated with the menu name has been described. The composition of meal data is not limited to this. In this example, as shown in the left half of FIG. 15 (meal data linkage method), the information related to the menu (hereinafter, also referred to as “menu information”) on the operator server 400 (or facility terminal 300) is classified by menu. The nutrient item is registered in advance, and the meal data acquired from the facility terminal 300 and the meal data provided to the service providing device 500 include the nutrient item.

As an example different from the above, as shown in the right half of FIG. 15 (menu ID linkage method), nutrients for each menu are registered in advance as menu information in the service providing device 500 of the meal-related service, and the service is provided at the time of registration. A menu ID may be issued by the providing device 500. The issued menu ID may be registered provided to the business operator server 400 (or facility terminal 300). The registered menu ID may be used to identify the menu in the facility terminal 300 or the payment device 100, and the menu ID may be used as meal data in cooperation with the service providing device 500. That is, the meal data acquired by the payment device 100 and transmitted to the service providing device 500 may include the menu ID, and the nutrient items included in the menu do not have to be included in the meal data (unnecessary). Become). With such a configuration, a general-purpose meal data hub function can be realized.

1 ... Integrated payment system, 100 ... Payment device, 110 ... Control unit, 111 ... Recording destination identification unit, 112 ... Request reception unit, 113 ... Payment processing unit, 114 ... Healthcare data acquisition unit, 115 ... Condition reception unit, 116 ... Usage information acquisition unit, 117 ... Facility identification unit, 118 ... Storage unit, 119 ... Data generation unit, 120 ... Calculation unit, 121 ... Designated reception unit, 122 ... Display unit, 123 ... Payment means reception unit, 124 ... Code generation Department, 125 ... privilege granting department, 130 ... communication department, 131 ... meal data transmission unit, 140 ... storage unit, 200 ... user device, 300 ... facility terminal, 400 ... operator server, 5 ... external system, 500 ... service provision Device, 800 ... Computer, 801 ... Processor, 803 ... Memory, 805 ... Storage device, 807 ... Input I / F section, 809 ... Data I / F section, 811 ... Communication I / F section, 813 ... Display device.

Claims (13)

A meal including a menu identification information of a meal of a first user and a nutrient item associated with the menu identification information based on a recording destination condition from a plurality of services providing a service for recording a meal to a user. A recording destination identification unit that identifies at least one service that is the recording destination of data,
A request reception unit that accepts a payment request for the payment when the first user pays for a meal at the restaurant from the facility terminal of the restaurant.
A payment processing unit that performs payment processing for payment of the payment based on the payment request,
Before If Kike' already processing is performed, the requesting facilities terminal of the payment request, and the food a the dietary data regarding options at the facility to obtain the meal data relating to the payment processing options data acquisition unit ,
A meal data transmission unit that transmits the meal data to each service providing device of the specified at least one service.
Payment device. When the payment processing is executed, the payment processing unit generates payment information including information for identifying a series of processing including the payment processing, which is the payment information of the payment processing.
The payment device includes a transmission unit for transmitting the payment information to the facility terminal from which the payment request is requested.
The meal data acquisition unit acquires the meal data collected for each series of processes from the facility terminal.
The payment device according to claim 1. The payment device further includes a condition reception unit that receives the recording destination condition indicating at least one service used by the first user from the plurality of services from the first user device of the first user.
The payment device according to claim 1 or 2. The payment device further includes a usage information acquisition unit that acquires usage information indicating the usage record of the function of the service providing device, which is included in the recording destination condition.
The payment device according to claim 1 or 2. From a plurality of restaurants, a facility identification unit that identifies the restaurant from which the meal data is acquired is further provided based on the acquisition source conditions.
When the payment process is performed, the meal data acquisition unit acquires the meal data from the facility terminal of the specified eating and drinking facility.
The payment device according to any one of claims 1 to 4. A storage unit that stores the meal data in the meal data storage unit for a predetermined period,
When the meal data cannot be acquired by the meal data acquisition unit, a data generation unit that generates temporary meal data instead of the meal data that cannot be acquired based on the accumulated meal data, and a data generation unit.
The meal data transmission unit transmits the provisional meal data to the service providing device instead of the meal data.
The payment device according to any one of claims 1 to 5. The meal data includes the number of people using the eating and drinking facility in the meal.
The payment device further includes a calculation unit for calculating the amount of meal per person in the meal based on the meal data and the number of users.
The meal data transmission unit transmits the meal data including the meal amount per person to the service providing device.
The payment device according to any one of claims 1 to 6. The meal data transmission unit refers to a user storage unit that stores the first user and a second user different from the first user in association with each other, and the second user apparatus of the second user. Send at least part of your dietary data,
The payment device according to any one of claims 1 to 7. The meal data includes the date and time of the meal.
The payment device is at least one of the day, day, or time zone of the meal to be transmitted from the first user device or the second user device of the first user to the second user device by the meal data transmission unit. It also has a designated reception section that accepts one designation.
The meal data transmission unit further transmits at least a part of the meal data of the first user to the second user device based on the designation.
The payment device according to claim 8. The first user refers to a payment means storage unit that stores payment means correspondence information indicating a correspondence relationship between the first user and the electronic payment means of each of the plurality of businesses that own the plurality of restaurants. A display unit for displaying a plurality of electronic payment means corresponding to the above on the first user device of the first user, and
A payment means receiving unit that accepts selection of an electronic payment means used by the user from the displayed plurality of electronic payment means from the first user device.
When the payment method is a code payment method with reference to a payment method storage unit that stores payment method information indicating a payment method that can be used by the first user, the payment method reception unit selects the electronic payment method. A code generation unit that generates an identification code for the code payment including the business identification information for identifying the business operator in the selected electronic payment means when the above is received.
A code transmission unit that transmits the identification code to the first user device that has accepted the selection of the electronic payment means, and
The payment payment request includes the business identification information of the identification code output by the first user device and read by the facility terminal.
Based on the payment request, the payment processing unit selects the business operator indicated by the business operator identification information of the identification code when the business operator to which the food and drink facility requesting the payment request belongs matches. The electronic payment means is processed for payment of the payment by the code payment.
The payment device according to any one of claims 1 to 9. The payment device further includes a privilege granting unit that grants the privilege that can be used for the payment to the first user when the acquired meal data satisfies the privilege condition.
The payment device according to any one of claims 1 to 10. On the computer
A meal including a menu identification information of a meal of a first user and a nutrient item associated with the menu identification information based on a recording destination condition from a plurality of services providing a service for recording a meal to a user. A recording destination identification function that identifies at least one service that is the recording destination of data,
A request reception function that accepts a payment request for the payment when the first user pays for a meal at the restaurant from the facility terminal of the restaurant.
A payment processing function that performs payment processing for payment of the payment based on the payment request,
Before If you Kike' already processing has been performed, from the requesting facility terminal of the payment request, and the meal data acquisition function for acquiring the meal data relating to the settlement process be the meal data about the meals in the dining options ,
A meal data transmission function for transmitting the meal data to each service providing device of the specified at least one service is realized.
program. The computer
A meal including a menu identification information of a meal of a first user and a nutrient item associated with the menu identification information based on a recording destination condition from a plurality of services providing a service for recording a meal to a user. At least one service that is the recording destination of the data is specified, and when the first user pays the price for the meal at the restaurant from the facility terminal of the restaurant, the payment request for the payment is received.
Based on the payment request, the payment process for the payment is performed, and the payment is processed.
Before If you Kike' already processing has been performed, from the requesting facility terminal of the settlement request, said to get the meal data relating to the settlement process be the meal data about the meals in the dining facility,
The meal data is transmitted to the respective service providing device of the specified at least one service.
Information processing method.

Images