JP2018088167A - Payment system, method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a scheme of meal charge aid that is available only at a store that is a participating store designated by a company.SOLUTION: A payment system for meal charge aid to employees includes: means for creating payment data on the basis of a received card settlement telegram, wherein the payment data includes either a first indication that indicates an object for the meal charge aid or a second indication that indicates an object not for the meal charge aid, and wherein the first indication and the second indication are set on the basis of a pair of a company identifier and a participating store identifier both contained in the payment data; means for calculating an amount of the meal charge aid on the basis of the payment data that includes the first indication among pieces of the payment data, wherein the amount of meal charge aid indicates an amount of money to be paid to a card holder; and means for creating billing data for the company on the basis of the calculated amount of money for the meal charge aid.SELECTED DRAWING: Figure 7

Description

  The present invention relates to a settlement system, method and program. More specifically, the present invention provides a meal subsidy mechanism that can only be used at merchant-designated stores designated by the company as part of its employee benefits while improving the company's cash flow. The present invention relates to a settlement system, method and program. The present invention also relates to a settlement system, method, and program capable of targeting only expenditure related to the work of employees with respect to meal cost assistance.

  Employee benefits are various measures and systems that companies provide to employees and their families in anticipation of benefits such as securing and retaining the workforce and improving motivation and efficiency. Companies have established various welfare measures and systems, but as a kind of welfare, a prepaid card is known that gives employees a meal for a certain period in advance (Patent Document 1). . Since this prepaid card can add an additional amount to the card balance, it can be used repeatedly. By using this prepaid card, companies can take measures to reduce the burden of meals on employees, and employees enjoy a benefit system called meal subsidies that can be used during daily work. be able to. Such measures and systems increase the number of restaurant chain stores and retail chain stores that can use prepaid cards. Then, you can eat using a prepaid card.

  As an example of such a service, a service called “ticket restaurant” has been conventionally known. In this service, a company distributes a dedicated electronic meal card to employees, and when the employee presents and pays for an electronic meal card at a restaurant or the like that has joined this service, the card holder provides meal assistance. It can be received. In this service, a dedicated card reader is installed at the store, and payment can be made by holding the card over at the time of payment. The company charges a certain amount in advance for the electronic meal card used in this service and gives it to the employee, so that the employee can enjoy this service every month.

JP 09-128602 A

Edited by Masayuki Yamamoto, “All Payment Service Mechanisms and Rules in Card Payment Business”, Financial and Finance Situation Study Group, May 28, 2012

  However, in such a meal payment assistance system using a prepaid card, the company must charge a prepaid card held by the employee in advance every month, but the employee does not necessarily use the full amount Not limited to this, it contributed to the deterioration of cash flow.

  Such a prepaid card can be used at any store where the service is affiliated, so it is also used for meals used by employees outside working hours. In addition, there is a risk that it can be used for expenses such as liquor, so it may be used inappropriately as employee benefits. Furthermore, in the above-mentioned example service, companies and restaurants have to introduce dedicated systems and equipment, so the burden on companies and restaurants is heavy, and regardless of whether the employee's working day or not. Since it can be used, it may be used for holiday eating and drinking.

  Some companies want to encourage employees to use restaurants and convenience stores that are tenants of buildings for policy reasons, but it is difficult to specify the use at a specific store with such prepaid cards. there were.

  The present invention has been made to solve such a problem, and can be used only at a store of a member store designated by a company as part of a welfare program for employees while improving the cash flow of the company. It is an object of the present invention to provide a settlement system, method and program capable of providing a meal cost assistance mechanism. It is another object of the present invention to provide an account settlement system, method and program capable of targeting only expenditures related to employee work.

  A payment system for subsidizing meals for an employee, which is one aspect of the present invention, is means for generating settlement data based on a received card payment message, wherein the settlement data is a meal cost assistance target. Either the first display or the second display indicating that the meal fee is not supported, the first display and the second display are a company identifier and a member store identifier included in the settlement data. A means set based on a pair, and a means for calculating an amount of meal subsidy based on the settlement data having the first display among the settlement data, wherein the amount of meal subsidy is Means for indicating the amount to be paid to the cardholder, and means for generating billing data for the company based on the calculated amount of meal subsidy.

  In another aspect of the present invention, a checkout method executed by a checkout system for subsidizing meals for employees is to generate checkout data based on a received card payment message, wherein the checkout is performed. The data has either a first display indicating a meal cost assistance target or a second display indicating a meal cost assistance target, and the first display and the second display are included in the settlement data. Set based on a pair of a company identifier and a merchant identifier, and calculating an amount of meal subsidy based on the settlement data having the first display among the settlement data The meal subsidy amount indicates an amount to be paid to the cardholder, and billing data for the company is generated based on the calculated meal subsidy amount. The features.

  According to the present invention, it is possible to provide a meal cost assistance mechanism that can be used only at a store of a member store designated by a company as part of a welfare for employees while improving the cash flow of the company. become. In addition, according to the present invention, it is possible to target only expenditure related to the work of employees. Furthermore, according to the present invention, it is not necessary to install a new system / equipment in a company, a restaurant or the like, and a conventionally used card payment mechanism can be used as it is.

It is a block diagram of the whole system containing the system which concerns on this invention. 1 is a system configuration diagram of a system according to the present invention. It is a figure explaining the user master concerning the present invention. It is a figure explaining the object member store master concerning the present invention. It is a figure explaining the authorization message | telegram which concerns on this invention. It is a figure explaining the adjustment information which concerns on this invention. It is a flowchart explaining the mechanism of the meal cost assistance which concerns on this invention. It is a block diagram of the whole system of 2nd Embodiment containing the system which concerns on this invention. It is a figure explaining the payment message | telegram for debit cards used by 2nd Embodiment. It is a figure explaining the user master used by 2nd Embodiment. It is a figure explaining the adjustment information used in 2nd Embodiment. It is a flowchart explaining the mechanism of the meal cost assistance based on this invention performed by 2nd Embodiment. It is a block diagram of the whole system of 3rd Embodiment containing the system which concerns on this invention. It is a figure explaining the user master used by 3rd Embodiment. It is a figure explaining the adjustment information used in 3rd Embodiment. It is a flowchart explaining the mechanism of the meal cost assistance based on this invention performed by 3rd Embodiment.

(overall structure)
FIG. 1 is a configuration diagram of the entire system including a system 100 according to the present invention. In the present specification, the system 100 is described as a system controlled by a credit card company for convenience of explanation, but the present invention is not limited to this embodiment. The present invention uses a conventional card payment mechanism. In this specification, a card payment embodiment using a credit card will be described first.

  The system 100 is a system controlled by a credit card company, and through a network 120, a member store terminal 110a, a member store terminal 110b,... And a member store terminal 110n (in this specification, these are collectively referred to as “member store”). The terminal 110 "is communicably connected. The member store terminal 110 is a known device installed in a member store that has signed a member store contract with a credit card company, and can transmit data such as authorization data and sales settlement data to the credit card company system 100. It is a device. The member store terminal 110 may be a conventional online payment terminal such as CAT (Credit Authorization Terminal), or a tablet terminal or smartphone in which a dedicated application capable of credit card payment is installed. It may be a terminal.

  As explained in Non-Patent Document 1, authorization (also referred to as “authorization”) is a credit card company that approves a card transaction of a customer (card member) at a member store for each transaction. Refers to processing. If the transaction is approved as a result of the authorization process, the subsequent process can be executed. However, if the transaction is denied as a result of the authorization process, the subsequent process is not performed. The system 100 of the credit card company holds information such as the repayment status of the card member and the card usage status, and the authorization checks the card expiration date, security code check, theft / counterfeit card based on such information. Perform checks, credit limit checks, etc. In addition, as explained in Non-Patent Document 1, sales settlement (also known as “Clearing”) is a process for receiving payment (payment) of card usage fees at member stores. This means that the card usage fee is scrutinized and aggregated and the details are reported, and the electronic data of the sales data is transmitted to the system 100 of the credit card company. The authorization message and the sales data message may be transmitted separately, or may be transmitted together as a single message. The messages exchanged between the member store terminal 110 and the card company system 100 including the message of authorization and the message of sales data may be collectively referred to as “authorized message”.

  The system 100 accumulates the authorization telegram received from the member store terminal 110, and when a predetermined date arrives, performs a checkout process for each card member and generates billing data. The billing data is presented to the cardholder by a predetermined method (for example, mail or online confirmation). The system 100 can provide a meal cost assistance mechanism described later in this specification.

  The network 120 may be any known network capable of mutual communication between the system 100 and the member store terminal 110, and is not particularly limited.

  Further, the system 100 is communicably connected to the company system 130 via the network 140, and the employee's attendance information matching process described in the meal cost assistance mechanism described later in this specification (an arbitrary settlement is performed by the employee). Processing to determine whether or not it occurred at the time of the employee's work). The company system 130 is a system of a company where card members work. The network 140 may be a well-known network capable of mutual communication between the system 100 and the enterprise system 130, and is not particularly limited.

(System configuration)
FIG. 2 is a system configuration diagram of the system 100 according to the present invention. As shown in FIG. 2, the system 100 includes a control unit 201, a main storage unit 202, an auxiliary storage unit 203, an interface (IF) unit 204, and outputs that are connected to each other via a bus 220, as in a general computer. A unit 205 can be provided. In addition, the system 100 can include a user master 206, a target member store master 207, an authorization message 208, and checkout information 209.

  The control unit 201 is also called a central processing unit (CPU), controls each component in the system 100 and calculates data, and stores various programs stored in the auxiliary storage unit 203 in the main storage unit 202. It can be read and executed. The main storage unit 202 is also called a main memory, and can store various received data, computer-executable instructions, data after arithmetic processing by the instructions, and the like. The auxiliary storage unit 203 is a storage device typified by a hard disk (HDD) and is used when data and programs are stored for a long period of time.

  In the embodiment of FIG. 2, an embodiment in which the control unit 201, the main storage unit 202, and the auxiliary storage unit 203 are provided in the same server computer will be described. However, as another embodiment, the system 100 includes a control unit 201, a main storage unit, By using a plurality of storage units 202 and auxiliary storage units 203, parallel distributed processing by a plurality of server computers can be realized. As another embodiment, a plurality of servers for the system 100 may be installed, and a plurality of servers may share one auxiliary storage unit 203.

  The IF unit 204 serves as an interface for transmitting and receiving data to and from other systems and devices, and provides an interface for receiving various commands and input data (such as various masters and tables) from the system operator. Can do. The output unit 205 can provide a display screen for displaying the processed data, a printing unit for printing the data, and the like.

  The user master 206 is a master table for storing card member information. Here, the user master 206 according to the present invention will be described with reference to FIG. The user master 206 can include a member ID 301, a password (PW) 302, member information 303, a company code 304, company information 305, a user ID 306, and a target credit card number 307, but is limited to these data items. Without including other data items.

  The member ID 301 is an identifier for identifying a card member in a credit card company. Since one card member may have a plurality of credit cards, the member ID 301 is a number different from the credit card number. A password (PW) 302 is an authentication password used when a card member accesses the system 100. The member information 303 indicates information such as a card member's name, address, and contact information.

  The company code 304 is an identifier for identifying a company in which a card member works. The company information 305 indicates information such as the name and location of the company where the card member works. The user ID 306 is an identifier for identifying the card member in the company where the card member works. The user ID 306 only needs to be able to identify the employee (card member) in the working company, and may correspond to the employee code assigned in the company. The target credit card number 307 indicates a credit card number to be processed by the meal fee assistance mechanism according to the present invention. A plurality of target credit card numbers 307 may be registered and is not particularly limited.

  Returning to FIG. 2, the target member store master 207 is a member store that has signed a member store contract with a credit card company, and is designated by the company as a target member store for meal cost assistance according to the present invention. This is a master table for storing the information. The target member store master 207 can identify which company can use the meal fee assistance mechanism according to the present invention and which member store can use it. Here, the target member store master 207 according to the present invention will be described with reference to FIG. Target member store master 207 can include company code 304, member store ID 401, member store information 402, but can also be configured to include other data items.

  The company code 304 is an identifier for identifying a company in which a card member works, and is an identifier for identifying a company that uses the meal cost assistance mechanism according to the present invention. The member store ID 401 is an identifier for identifying each member store. The member store information 402 can indicate information such as the address of the member store, the company name, the closing date agreed with the credit card company, the payment date of the settlement amount, and the transfer account. As is well known to those skilled in the art, a different member store ID is assigned to each store even in the same company (for example, a convenience store or a restaurant chain). For this reason, even if it is the same restaurant, the member store ID given to a restaurant located within walking distance of a company and the member assigned to a restaurant of the same chain located tens of kilometers away from the company The store ID will be different. For this reason, a company can make only a specific store a store that can use the meal fee assistance mechanism according to the present invention by designating each member store ID. That is, the combination of the company code 304 and the member store ID 401 registered in the target member store master 207 indicates which member store has been designated by the company using the meal fee assistance mechanism according to the present invention.

  Returning to FIG. 2, the authorization message 208 is a database (DB) that stores an authorization message transmitted from the member store terminal 110 to the system 100. An authorization message is a message generated for a credit card transaction of a cardholder at a member store, and the business categories indicating the contents of the credit card transaction are “pre-authorization (credit)”, “sales”, “cancellation / return”. Including telegrams. The authorization message includes a credit card number, information for identifying a member store (member store ID), amount information, and the like. Here, the authorization message 208 according to the present invention will be described with reference to FIG.

  The authorization message 208 can include a card number 501, member store ID 401, date and time 502, business category 503, and card usage amount 504, but can also be configured to include other data items.

  The card number 501 indicates the number of a credit card used for card payment at the member store, and the member store ID 401 is an identifier for identifying the member store where the card payment is performed. The date and time 502 indicates the date and time when the card payment was made at the member store. The business category 503 indicates the business category described above, for example, “sales”. The card usage amount 504 indicates the amount of the card settlement.

  Returning to FIG. 2 again, the settlement information 209 is a database that stores billing data (payment information) for card members, which is generated based on the authorization message stored in the authorization message 208. The data stored in the checkout information 209 can be used to create a bill for a cardholder when a predetermined date arrives, or can be used to create a data for checking the contents of the bill online. Can be done. In addition to the card usage amount, the settlement information 209 includes a cost to be collected from the card member (for example, an annual membership fee), or a cost to be refunded to the card member (for example, the amount of meal subsidy described in this specification). Can be included. Here, the settlement information 209 according to the present invention will be described with reference to FIG.

  The settlement information 209 can include a card number 501, a member store ID 401, a date and time 502, a business category 503, a card usage amount 504, a user ID 306, a company code 304, an auxiliary target flag 601 and a billing processing flag 602. Can also be configured to include these data items.

  The settlement information 209 is generated based on the authorization message stored in the authorization message 208. If there is a pair of data whose business category 503 is "sales" and "cancellation / return", those data are Offset. Furthermore, data whose business category is “pre-approval (credit)” is not subject to processing because it is not billing data for card members. For this reason, the initial data stored in the settlement information 209 stores only data for which the business division 503 is “sales”.

  The card number 501, member store ID 401, date and time 502, business category 503, and card usage amount 504 of the settlement information 209 correspond to the data items described above with reference to FIG. That is, the card number 501 indicates the number of a credit card used for card payment at a member store, and the member store ID 401 is an identifier for identifying the member store where the card payment is performed. The date and time 502 indicates the date and time when the card payment was made at the member store. The business category 503 indicates the business category of “sales”, and the card usage amount 504 indicates the amount of the card settlement.

  The user ID 306 and the company code 304 correspond to the user ID 306 and the company code 304 of the user master 206 described with reference to FIG. The user ID 306 and the company code 304 make an inquiry to the user master 206 using the card number 501 of the settlement information 209 as a search key, and the user ID and company code of the data that matches the target credit card number 307 of the user master 206 It is.

  The assist target flag 601 is a flag indicating whether or not the assist target flag 601 is an assist target in the process of determining meal cost assistance, which will be described later. The billing process flag 602 is a flag indicating whether or not the data has been billed for the card member.

(Meal fee assistance mechanism: credit card)
The meal fee assistance mechanism according to the present invention is a mechanism in which a company pays a certain amount when an employee eats and drinks or shop for a meal at a member store designated by the company. The member stores designated by the company can be designated for each individual store.For example, the convenience stores and restaurants in the vicinity of the company can be designated individually, and the chain of the same convenience store and restaurant can be specified. However, stores located away from the company can be excluded. Furthermore, as will be described later, since it is possible to match card payment information and employee attendance information, it is possible to support only expenses spent at the time of employee work, for example, expenses spent on holidays. Assistance against can be prevented. In addition, employees themselves can choose not to include voluntary expenditures (for example, eating, drinking, or purchasing alcohol at a member store designated by the company after leaving work, even on work days) Can be excluded if the data is included). In one embodiment of the present invention, it is possible to limit the time zone in which the card payment is made. For example, it is possible to set only the expenditure in the lunch time zone designated by the company as the subject of assistance.

  Below, the mechanism of meal cost assistance according to the present invention will be described with reference to FIG. FIG. 7 is a flowchart for explaining the mechanism of meal cost assistance according to the present invention.

  In S701, the card member makes a card settlement at the member store for the expense of meals. Expenditure for meals includes expenditures for meals in restaurants and purchases of foods and the like in stores. When the credit card held by the card member is read by the member store terminal 110, an authorization message including information for identifying the card (for example, a card number) is transmitted to the system 100 of the credit card company. As described above, the authorization message includes an authorization message and sales data message. The transmitted authorization message can include a card number 501, member store ID 402, date and time 502, business category 503, and card usage amount 504. The member store terminal 110 is a device conventionally used in credit card payment.

  In S702, the system 100 stores the received authorization message in the authorization message 208. The system 100 may temporarily store the authorization message on the main storage unit 202 and store the authorization message in the authorization message 208 after the processing of S702 ends, or immediately after receiving the authorization message. 208 may be stored.

  In S703, the system 100 reads the authorization message from the authorization message 208 at a predetermined timing, and performs data processing on the read data. Hereinafter, this data processing will be described.

  The system 100 makes an inquiry to the user master 206 using the card number 501 included in the read data as a search key, and obtains the user ID 306 and company code 304 of the data in which the card number 501 and the target credit card number 307 match. Append to the read data. The system 100 makes an inquiry to the target member store master 207 using the company code 304 and member store ID 401 included in the added data as a search key, and there is data in which the company code 304 and member store ID 401 are paired. Determine whether or not. If it is determined that it is present, a flag indicating “subject” is set in the auxiliary target flag 601 included in the added data, and if it is determined that it is not present, A flag indicating “not subject to assistance” is set in the target flag 601. The billing process flag 602 is set with a flag indicating “unbilled”. After such data processing is performed, the processed data is stored in the settlement information 209.

  In S704, the system 100 reads out data indicating that the billing processing flag indicates “unbilled” among the data stored in the settlement information 209, and stores the data in the company system 130 of the company associated with the company code 304 of the read data. On the other hand, the data read from the settlement information 209 can be transmitted. The enterprise system 130 performs matching processing with the employee's attendance information based on the user ID 306 and the date / time 502 information included in the received data, and the employee indicated by the data works on the day indicated by the date / time 502. It can be determined whether or not. If it is determined that the company system is working, the company system 130 does not perform any processing. If there is a day when the employee has not worked, the assistance target flag 601 indicates “not supported” for the data of that day. Can be transmitted to the system 100 after the flag indicating that the The system 100 can update the corresponding data stored in the settlement information 209 based on the updated data among the received settlement information data. With the data communication between the system 100 and the enterprise system 130 and the data update process described above, it is possible to provide meal assistance only on the day the employee works. In another embodiment of the present invention, the system 100 transmits the user ID 306 and the date / time 502 of the data read from the settlement information 209 to the company system 130, and the employee associated with the user ID 306 is displayed on the date of the date / time 502. Information (for example, ○ and ×) indicating whether or not he / she was working may be received from the enterprise system 130. The system 100 can update the settlement information 209 based on the received information (for example, ◯ and X).

  In S <b> 705, the system 100 can read the payment information before the actual billing process is performed for the employee from the payment information 209 and present it to the card member (employee) through the application provided by the system 100. it can. The employee can access the system 100 using his / her PW 302 through a well-known personal computer or mobile phone, and can confirm his / her settlement information. When there is settlement data (for example, alcohol-related) that is determined not to be included in the subsidy information in the presented settlement information, the employee uses the value of the subsidy flag 601 of such data through the application. It can be changed to “Not supported”. The system 100 can receive the change operation and update the corresponding data in the settlement information 209. Note that the value of the auxiliary target flag 601 of the settlement information 209 can be changed through the application only when the value is changed from “auxiliary target” to “not auxiliary target”. This restriction is intended to prevent fraudulent acts by employees (actually payment data that is not a target of assistance, but an action that is subject to assistance by an operation).

  In S706, the system 100 reads data from the settlement information 209 when a predetermined date arrives, and generates billing data for the card member. Further, the system 100 sums up the value of the card usage amount 504 of the billing data in which the value of the assistance target flag 601 indicates “assistance subject” in the billing data for the card member, and the work place of the card member is determined. The meal subsidy amount can be calculated according to the standard. For example, if the combined card usage amount 504 is 20,000 yen and the company's subsidy rate is 30% (however, the maximum monthly amount is up to 5000 yen), the simple calculation is 20,000 yen x 30% = 6000 yen. However, since the upper limit is determined to be 5000 yen, the meal subsidy for the employee is 5000 yen. When the total amount is 10,000 yen, the upper limit amount is less than 5000 yen, so the meal subsidy amount is 10,000 yen x 30% = 3000 yen. According to the present invention, it is not necessary for the company side to give the meal fee subsidy to the employee in advance, and the meal fee can be subsidized only for the expenditure for which the card payment is actually made. Therefore, it is superior to the invention described in Patent Document 1 and the conventional service in terms of cash flow.

  The system 100 can add minus 5000 yen data to the billing data of the employee based on the calculation result of the meal cost subsidy. The final billing data will be communicated to the employee in a predetermined manner (eg, postal mail, online confirmation, etc.). In addition, the system 100 may add up all the amount data (in the above example, 5000 yen or 3000 yen) for subsidizing food costs for employees of the company, and use the combined amount as billing data for the company. it can. Regarding billing to a company, an account transfer contract may be concluded between the company and the card company in advance, and the billed amount may be withdrawn from the company account and transferred to the card company account.

  The company system 130 can receive billing data for the company from the system 100 as meal cost assistance. The company uses the received billing data to manage the provisions stipulated in 2) “In the case where there is no economic benefit from the provision of meals” in the Basic Income Tax Notification 36-38 issued by the NTA. It is also possible to partially subtract the subsidy from the income tax.

  As another embodiment of the present invention, the settlement information 209 can be configured to store only data that has not been billed. In this case, when this processing flow is performed successfully, the data to be processed is moved to the backup database.

  In another embodiment of the present invention, the system 100 determines that the assistance target flag is included only in the data stored in the settlement information 209 when the value of the date and time 502 falls within the time zone specified by the company. The value of 601 can be set to “auxiliary target”.

  The following table is a comparison between the meal cost assistance mechanism according to the present invention and an example of a conventionally performed service described in [Background Art].

(Meal fee assistance mechanism: debit card)
Next, the meal cost assistance mechanism according to the present invention will be described by taking an embodiment using a debit card as an example. A debit card is an immediate payment card that is issued by a bank or a credit card company. In detail, a debit card is a card that is linked or directly linked to a bank account that was designated in advance when the debit card was issued, and when you shop at a merchant, the payment is immediately withdrawn from the account (immediate payment). . If there is no balance in the account, no withdrawal will be made and you will not be able to shop. Since the debit card is linked / directly linked to a bank account, it is not necessary to charge (prepay) in advance like a prepaid card or electronic money.

  FIG. 8 is a configuration diagram of the entire system of the embodiment for the debit card (second embodiment) including the system 100 according to the present invention. The system 100 is connected to the bank system 150 and the enterprise system 130 through a network. The corporate system 130 is a corporate system where a debit card user works. The bank system 150 is a well-known bank system that handles debit card settlement, and is connected to a plurality of member store terminals 160 through a network. The member store terminal 160 is a well-known device responsible for debit card payment.

  When the debit card payment is performed at the member store, the member store terminal 160 can transmit a debit payment message 900 as shown in FIG. 9 to the bank system 150. Since the debit card is designated with a bank account for debiting when the card is issued, the debit payment message 900 is transmitted to the bank system 150 of the bank having the designated bank account. A known relay system (for example, a communication payment information processing center) may exist between the member store terminal 160 and the bank system 150, and the relay system may be involved in the control of the debit payment message 900. For example, the relay system transfers the debit payment message 900 to the bank system 150 while holding the debit payment message 900, and then responds to receiving a notification from the bank system 150 that the account withdrawal has been completed successfully. Thus, the relay system may transmit the debit settlement message 900 to the system 100.

  FIG. 9 is a diagram illustrating a debit payment message 900 that is a payment message for a debit card. The debit payment message 900 can include a debit card number 901, member store ID 401, date and time 902, bank account 903, and payment amount 904, but can also be configured to include other data items.

  The debit card number 901 is an identifier for identifying the debit card. The member store ID 401 is an identifier for identifying a member store that can use debit card payment, and may be the same member store ID as the member store that can use credit card payment. The date and time 902 indicates the date and time when the debit card payment was made. A bank account 903 indicates bank account information for debiting the debit card payment. The settlement amount 904 indicates a price (settlement amount) for debit card settlement.

  Referring back to FIG. 8, when the bank system 150 receives the debit payment message 900, the bank system 150 determines whether or not the price can be withdrawn from the corresponding bank account based on the information of the bank account 903 and the payment amount 904. be able to. If the withdrawal cannot be made, a message indicating that the settlement is not possible is transmitted to the member store terminal 160 to communicate that the debit card settlement has failed. If it can be debited, the bank system 150 deducts the payment indicated by the settlement amount 904 from the bank account, updates the balance of the bank account, and transmits a debit settlement message 900 to the system 100.

  When the system 100 receives the debit payment message 900, the system 100 makes an inquiry to the user master 1000 using the debit card number 901 as a search key, reads out the corresponding company code 304 and user ID 306, and includes information included in the debit payment message 900. The settlement information 1100 can be generated based on the read company code 304 and user ID 306 information. Here, the user master 1000 and the settlement information 1100 will be described with reference to FIGS. 10 and 11.

  FIG. 10 is a diagram illustrating the user master 1000 used in the second embodiment. User master 1000 can include debit card number 901, company code 304, and user ID 306, but can also be configured to include other data items. The user master 1000 is a database indicating which company the debit card user is working for and the identification number (for example, employee code) of the employee in the company. The debit card number 901 is an identifier for identifying the debit card, the company code 304 is an identifier for identifying the company where the debit card user works, and the user ID 306 is the debit card user at the company. Is an identifier (for example, an employee code) for identifying

  FIG. 11 is a diagram for explaining the settlement information 1100 used in the second embodiment. The settlement information 1100 is settlement data for which debit card settlement has been performed, and is a database having identification information on the card user's company and company. Specifically, the settlement information 1100 may include a debit card number 901, a member store ID 401, a date and time 902, a bank account 903, a payment amount 904, a user ID 306, a company code 304, an auxiliary target flag 1101, and a refund flag 1102. Although it can be configured to include other data items. The information of the debit card number 901, the member store ID 401, the date and time 902, the bank account 903, and the payment amount 904 is information included in the debit payment message 900, and the user ID 306 and the company code 304 are stored in the user master 1000. It is the information that was included. Information included in the debit payment message 900 and the user master 1000 is information extracted based on the debit card number 901.

  The assistance target flag 1101 indicates whether or not the expenditure may be a target of meal cost assistance according to the present invention, and the refund flag 1102 is a flag indicating whether or not the refund process has actually been performed.

  Returning to FIG. 8 again, the system 100 accesses the target member store master 207 using the pair of the company code 304 and member store ID 401 included in the checkout information 1100 as a search key, and determines whether there is a matching pair of data. judge. If it is determined that the data exists, the system 100 can set a flag indicating “assisting target” in the assisting target flag 1101 of the data. When it is determined that the data does not exist, the system 100 can set a flag indicating “not supported” in the assistance target flag 1101 of the data. The system 100 performs such processing on all data of the settlement information 1100.

  Thereafter, the system 100 reads the data of the settlement information 1100 for each debit card number 901 at a predetermined timing (for example, once a month), and a flag indicating “auxiliary target” is set in the auxiliary target flag 1101. Data settlement amount 904 is added up. The system 100 performs data processing for calculating the amount of meal support based on the summed amount. For example, if the total amount is 20,000 yen and the company's subsidy rate is 30% (however, the maximum monthly amount is up to 5000 yen), the simple calculation would be 20,000 yen x 30% = 6000 yen. Since the upper limit is set at 5000 yen, the meal subsidy for the employee is 5000 yen. When the total amount is 10,000 yen, the upper limit amount is less than 5000 yen, so the meal subsidy amount is 10,000 yen x 30% = 3000 yen. According to the present invention, it is not necessary for the company side to give the meal subsidy amount in advance to the employee, and the subsidy can be subsidized only for the expenditure for which the debit card is actually paid. Therefore, it is superior to the invention described in Patent Document 1 and the conventional service in terms of cash flow.

  The system 100 can generate transfer data for transferring the amount after the above data processing to the account indicated by the bank account 903. The generated transfer data is transmitted from the system 100 to the bank system 150, and the bank system 150 performs a transfer process for the account indicated by the bank account 903. A transfer source account (for example, an account of a card company) may exist in a plurality of banks, and a transfer process is executed from the transfer source account to an account indicated by the bank account 903. With such a mechanism, a debit card user can receive meal cost assistance from a company.

  Furthermore, the system 100 may add all the amount data for subsidizing meals for employees of the company (in the above example, 5000 yen or 3000 yen) and use the combined amount as billing data for the company. it can. That is, the amount charged to the company is equal to the amount of meal subsidy for the employee. Regarding billing to a company, an account transfer contract may be concluded between the company and the card company in advance, and the billed amount may be withdrawn from the company account and transferred to the card company account.

  Below, the mechanism for meal cost assistance according to the present invention will be described with reference to FIG. FIG. 12 is a flowchart for explaining a meal cost assistance mechanism according to the present invention, which is executed in the second embodiment. The meal fee assistance mechanism according to the present invention is a mechanism in which a company pays a certain amount when an employee eats or eats food or purchases for a meal at a member store designated by the company. The member store designated by the company can be designated for each individual store. Furthermore, since it is possible to match debit card payment information and employee attendance information, it is possible to assist only the expenses spent at the time of employee work. Employees themselves can choose not to include any expenditures as subsidies, and can also limit the time periods during which card payments were made.

  In S1201, the debit card user makes a card payment at the member store for the expense of meals. Expenditure for meals includes expenditures for meals in restaurants and purchases of foods and the like in stores. When the debit card is read by the member store terminal 160, a debit payment message 900 is transmitted to the bank system 150. Since the debit card is designated with a bank account for debiting when the card is issued, the debit payment message 900 is transmitted to the bank system 150 of the bank having the designated bank account.

  In S1202, upon receiving the debit payment message 900, the bank system 150 can determine whether or not the payment can be withdrawn from the corresponding bank account based on the information of the bank account 903 and the payment amount 904. If the withdrawal cannot be made, a message indicating that the settlement is not possible is transmitted to the member store terminal 160 to communicate that the debit card settlement has failed. If it can be debited, the bank system 150 deducts the payment indicated by the settlement amount 904 from the bank account, updates the balance of the bank account, and transmits a debit settlement message 900 to the system 100.

  In step S1203, when the system 100 receives the debit payment message 900, the system 100 makes an inquiry to the user master 1000 using the debit card number 901 as a search key, reads the corresponding company code 304 and user ID 306, and debit payment message 900. The settlement information 1100 can be generated based on the information included in the information and the information of the read company code 304 and user ID 306.

  The system 100 accesses the target member store master 207 using the pair of the company code 304 and the member store ID 401 included in the settlement information 1100 as a search key, and determines whether there is a matching pair of data. If it is determined that the data exists, the system 100 can set a flag indicating “assisting target” in the assisting target flag 1101 of the data. When it is determined that the data does not exist, the system 100 can set a flag indicating “not supported” in the assistance target flag 1101 of the data. This process is performed on all data of the settlement information 1100.

  In step S1204, the system 100 reads the data stored in the settlement information 1100, and transmits the data read from the settlement information 1100 to the company system 130 of the company associated with the company code 304 of the read data. it can. The enterprise system 130 performs matching processing with the employee's attendance information based on the user ID 306 and date / time 902 information included in the received data, and the employee indicated by the data works on the day indicated by the date / time 902. It can be determined whether or not. When it is determined that the company system is working, the company system 130 does not perform any processing. If there is a day when the company has not been working, the assistance target flag 1101 for the data of the day is “not supported”. Can be transmitted to the system 100 after the flag indicating that the The system 100 can update the corresponding data stored in the settlement information 1100 based on the updated data among the received settlement information data. With the data communication between the system 100 and the enterprise system 130 and the data update process described above, it is possible to provide meal assistance only on the day the employee works. In another embodiment of the present invention, the system 100 transmits the user ID 306 and the date / time 902 among the data read from the settlement information 1100 to the company system 130, and the employee associated with the user ID 306 is displayed on the date of the date / time 902. Information (for example, ○ and ×) indicating whether or not he / she was working may be received from the enterprise system 130. The system 100 can update the settlement information 1100 based on the received information (for example, ◯ and X).

  In S1205, the system 100 can read the settlement information before actual refund processing is performed for the employee from the settlement information 1100 and present it to the employee through an application provided by the system 100. An employee can access the system 100 through a well-known personal computer, a mobile phone, or the like to check his / her own payment information. When there is settlement data (for example, alcohol-related) that is determined not to be included in the subsidized information in the presented settlement information, the employee sets the value of the subsidy flag 1101 of such data through the application. It can be changed to “Not supported”. The system 100 can receive the change operation and update corresponding data in the settlement information 1100. Note that the value of the auxiliary target flag 1101 of the settlement information 1100 can be changed through the application only when the value is changed from “auxiliary target” to “not auxiliary target”. This restriction is intended to prevent fraudulent acts by employees (actually payment data that is not a target of assistance, but an action that is subject to assistance by an operation).

  In S1206, the system 100 reads the data of the settlement information 1100 for each debit card number 901 at a predetermined timing (for example, once a month), and a flag indicating “auxiliary target” is set in the auxiliary target flag 1101. The settlement amount 904 of the data is added up. The system 100 performs data processing for calculating the amount of meal support based on the summed amount. For example, if the total amount is 20,000 yen and the company's subsidy rate is 30% (however, the maximum monthly amount is up to 5000 yen), the simple calculation would be 20,000 yen x 30% = 6000 yen. Since the upper limit is set at 5000 yen, the meal subsidy for the employee is 5000 yen. When the total amount is 10,000 yen, the upper limit amount is less than 5000 yen, so the meal subsidy amount is 10,000 yen x 30% = 3000 yen. According to the present invention, it is not necessary for the company side to give the meal subsidy amount in advance to the employee, and the subsidy can be subsidized only for the expenditure for which the debit card is actually paid. Therefore, it is superior to the invention described in Patent Document 1 and the conventional service in terms of cash flow.

  Thereafter, the system 100 can generate transfer data for transferring the amount after the above-described data processing to the account indicated by the bank account 903. The generated transfer data is transmitted from the system 100 to the bank system 150, and the bank system 150 performs a transfer process for the account indicated by the bank account 903. A transfer source account (for example, an account of a card company) may exist in a plurality of banks, and a transfer process is executed from the transfer source account to an account indicated by the bank account 903. A flag indicating “refunded” is set in the refund flag 1102 of the data subjected to the data processing.

  In addition, the system 100 may add up all the amount data (in the above example, 5000 yen or 3000 yen) for subsidizing food costs for employees of the company, and use the combined amount as billing data for the company. it can.

  As another embodiment of the present invention, the checkout information 1100 may be configured to store only data that has not been refunded. In such a case, when the processing flow of FIG. 12 is successfully performed, the data to be processed is moved to the backup database.

  In another embodiment of the present invention, the system 100 determines that the auxiliary target flag is only when the value of the date and time 902 is within the time zone specified by the company among the data stored in the settlement information 1100. The value of 1101 can be set to “auxiliary target”.

  The following table is a comparison between the meal cost assistance mechanism according to the present invention and an example of a conventionally performed service described in [Background Art].

(Meal fee assistance mechanism: prepaid card)
Next, the meal cost assistance mechanism according to the present invention will be described by taking an embodiment using a prepaid card as an example. In the service using the prepaid card described in the “Background Technology” section of the present specification, the company previously charged the prepaid card, but the prepaid card according to the present invention was used. In the meal subsidy mechanism, since the subsidy is calculated afterwards in the same manner as in the above-described embodiment, the company does not need to charge the subsidize in advance.

  FIG. 13 is a configuration diagram of the entire system of a prepaid card embodiment (third embodiment) including the system 100 according to the present invention. The system 100 is communicably connected to the enterprise system 130 through a network, and the employee's attendance information matching process described in the meal cost assistance mechanism described later in this specification (an arbitrary settlement occurs when the employee works) Processing for determining whether or not the operation has been performed). The corporate system 130 is a corporate system where prepaid card users work. The member store terminal 170 is a well-known device responsible for prepaid card payment. The system 100 is connected to a plurality of member store terminals 170 through a network.

  When the prepaid card payment is performed at the member store, the member store terminal 170 can transmit a prepaid card payment message to the system 100. The prepaid card payment message may include, for example, a prepaid card number 1401, a member store ID 401, a date and time 1501, and a payment amount 1502. After receiving and storing the prepaid card payment message, the system 100 updates the balance information of the corresponding prepaid card, and also stores information stored in the user master 1400 and information included in the prepaid card payment message. Can be merged to generate the settlement information 1500. In addition, the system 100 can present the prepaid card balance information (balance information before and / or after settlement) to the member store terminal 170.

  FIG. 14 is a diagram illustrating a user master 1400 used in the third embodiment. User master 1400 can include a prepaid card number 1401, company code 304, and user ID 306, but can also be configured to include other data items. The user master 1400 is a database indicating to which company the prepaid card user is working and an identification number (for example, employee code) of an employee in the company. The prepaid card number 1401 is an identifier for identifying the prepaid card, the company code 304 is an identifier for identifying the company where the prepaid card user works, and the user ID 306 is the prepaid card user at the company. Is an identifier (for example, an employee code) for identifying

  FIG. 15 is a diagram for explaining the settlement information 1500 used in the third embodiment. The settlement information 1500 is settlement data for which a prepaid card settlement has been performed, and is a database having identification information of the card user's work company and the work company. Specifically, the settlement information 1500 may include a prepaid card number 1401, a member store ID 401, a date and time 1501, a settlement amount 1502, a user ID 306, a company code 304, an auxiliary target flag 1503, and a charge flag 1504. Can also be configured to include these data items. Information on the prepaid card number 1401, member store ID 401, date and time 1501, and settlement amount 1502 is information included in the prepaid card settlement message, and the user ID 306 and the company code 304 are included in the user master 1400. Information. The assistance target flag 1503 is a flag indicating whether or not the expenditure can be a meal cost assistance target according to the present invention. The charge flag 1504 is a flag indicating whether or not the corresponding prepaid card has been charged with respect to the expenditure for which meal cost assistance has been applied.

  The prepaid card number 1401 is an identifier for identifying a prepaid card. The member store ID 401 is an identifier for identifying a member store that can use prepaid card payment, and may be the same member store ID as a member store that can use credit card payment / debit card payment. The date and time 1501 indicates the date and time when the prepaid card payment was made. The settlement amount 1502 indicates the price (settlement amount) for prepaid card settlement.

  Below, the mechanism for meal cost assistance according to the present invention will be described with reference to FIG. FIG. 16 is a flowchart for explaining a meal cost assistance mechanism according to the present invention, which is executed in the third embodiment. The meal fee assistance mechanism according to the present invention is a mechanism in which a company pays a certain amount when an employee eats or eats food or purchases for a meal at a member store designated by the company. The member store designated by the company can be designated for each individual store. Furthermore, since the information of the prepaid card settlement and the employee's attendance information can be matched, it is possible to assist only the expense spent during the work of the employee. Employees themselves can choose not to include any expenditures as subsidies, and can also limit the time periods during which card payments were made.

  In S1601, a prepaid card user makes a card payment at a member store for spending meals. Expenditure for meals includes expenditures for meals in restaurants and purchases of foods and the like in stores. When the prepaid card is read by the member store terminal 170, a prepaid card settlement message is transmitted to the system 100.

  In S1602, upon receiving a prepaid card payment message, system 100 can update prepaid card balance information (not shown). The balance information before and after the update may be presented to the member store terminal 170.

  In step S1603, the system 100 can merge the information included in the received prepaid card payment message and the information included in the user master 1400 using the prepaid card number 1401 as a key to generate settlement information 1500. An example of the settlement information 1500 is as described above with reference to FIG. 15, and NULL is set as an initial value for the auxiliary target flag 1503 and the charge flag 1504.

  The system 100 accesses the target member store master 207 using the pair of the company code 304 and the member store ID 401 included in the settlement information 1500 as a search key, and determines whether there is a matching pair of data. When it is determined that the data exists, the system 100 can set a flag indicating “assisting target” in the assisting target flag 1503 of the data. This process is performed on all data of the settlement information 1500.

  In step S1604, the system 100 reads the data stored in the settlement information 1500, and transmits the data read from the settlement information 1500 to the company system 130 of the company associated with the company code 304 of the read data. it can. The enterprise system 130 performs matching processing with the employee's attendance information based on the information of the user ID 306 and the date / time 1501 included in the received data, and the employee indicated by the data works on the day indicated by the date / time 1501. It can be determined whether or not. When it is determined that the company system is working, the company system 130 does not perform any processing. When there is a day when the company has not been working, the assistance target flag 1503 is set to “not subject to assistance” for the data of that day. Can be transmitted to the system 100 after the flag indicating that the The system 100 can update the corresponding data stored in the settlement information 1500 based on the updated data among the received settlement information data. With the data communication between the system 100 and the enterprise system 130 and the data update process described above, it is possible to provide meal assistance only on the day the employee works. In another embodiment of the present invention, the system 100 transmits the user ID 306 and the date and time 1501 among the data read from the checkout information 1500 to the company system 130, and the employee associated with the user ID 306 is displayed on the date of the date and time 1501. Information (for example, ○ and ×) indicating whether or not he / she was working may be received from the enterprise system 130. The system 100 can update the settlement information 1500 based on the received information (for example, ◯ and X).

  In S <b> 1605, the system 100 can read the settlement information before the employee is charged for the meal subsidy amount from the settlement information 1500 and present it to the employee through the application provided by the system 100. . An employee can access the system 100 through a well-known personal computer, a mobile phone, or the like to check his / her own payment information. When there is settlement data that is determined not to be included in the subsidy information in the presented settlement information, the employee sets the value of the subsidy flag 1503 of such data to “not subsidy” through the application. Can be changed. The system 100 can receive the change operation and update the corresponding data in the settlement information 1500. Note that the value of the auxiliary object flag 1503 of the settlement information 1500 can be changed through the application only when the value is changed from “auxiliary object” to “not auxiliary object”. This restriction is intended to prevent fraudulent acts by employees (actually payment data that is not a target of assistance, but an action that is subject to assistance by an operation).

  In S1606, the system 100 reads the data of the settlement information 1500 for each prepaid card number 1401 at a predetermined timing (for example, once a month), and sets a flag indicating “subject target” to the auxiliary target flag 1503. The settlement amount 1502 of the data is added up. The system 100 performs data processing for calculating the amount of meal support based on the summed amount. For example, if the total amount is 20,000 yen and the company's subsidy rate is 30% (however, the maximum monthly amount is up to 5000 yen), the simple calculation would be 20,000 yen x 30% = 6000 yen. Since the upper limit is set at 5000 yen, the meal subsidy for the employee is 5000 yen. When the total amount is 10,000 yen, the upper limit amount is less than 5000 yen, so the meal subsidy amount is 10,000 yen x 30% = 3000 yen. According to the present invention, it is not necessary for the company side to give the meal subsidy amount in advance to the employee, and the subsidy can be subsidized only for the expenditure for which the prepaid card settlement is actually performed. Therefore, it is superior to the invention described in Patent Document 1 in terms of cash flow.

  Thereafter, the system 100 updates the balance information of the prepaid card stored in the system 100 with the calculated meal subsidy amount, and the charge flag 1504 of the data subject to this data processing indicates “charged” Can be set.

  In addition, the system 100 may add up all the amount data (in the above example, 5000 yen or 3000 yen) for subsidizing food costs for employees of the company, and use the combined amount as billing data for the company. it can.

  As another embodiment of the present invention, the checkout information 1500 may be configured to store only data that has not been charged. In such a case, when the processing flow of FIG. 16 is successfully performed, the data to be processed is moved to the backup database.

  In another embodiment of the present invention, the system 100 determines that the assistance target flag is only when the value of the date and time 1501 is within the range of the time zone specified by the company among the data stored in the settlement information 1500. A value of 1503 can be set to “auxiliary target”.

  The following table is a comparison between the meal cost assistance mechanism according to the present invention and an example of a conventionally performed service described in [Background Art].

  In the first to third embodiments, the user masters 206, 1000, and 1400 have been described as separate tables. However, these tables may be integrated into one.

  Although the principle of the present invention has been described above with reference to exemplary embodiments, those skilled in the art will appreciate that various embodiments that change in configuration and details can be realized without departing from the spirit of the present invention. Will understand. That is, the present invention can adopt an embodiment as, for example, a system, apparatus, method, program, or storage medium.

100 system 110, 160, 170 member store terminal 120, 140 network 130 corporate system 150 bank system 201 control unit 202 main storage unit 203 auxiliary storage unit 204 interface (IF) unit 205 output unit 206, 1000, 1400 user master 207 target Merchant master 208 Authorization message 209, 1100, 1500 Checkout information 900 Debit payment message

Claims (15)

A payment system for subsidizing meals for employees,
A means for generating settlement data based on the received card payment message, wherein the settlement data includes either a first display indicating a meal cost assistance target or a second display indicating a meal cost assistance target. Means for setting the first display and the second display based on a pair of a company identifier and a member store identifier included in the checkout data;
A means for calculating an amount for subsidizing meal based on the settlement data having the first display among the settlement data, wherein the amount for subsidizing meal is an amount paid to a cardholder. Showing, means,
A payment system comprising: means for generating billing data for a company based on the calculated amount of meal subsidy. Read the settlement data that has not yet been used to calculate the amount of money for subsidizing meals, and with respect to the corporate system associated with the company identifier included in the readout settlement data, of the readout settlement data Means for transmitting at least a user identifier and date and time information;
The update information associated with the transmitted user identifier and the date and time information is received from the enterprise system, and the settlement data is updated based on the update information, the update information being the card possession The payment system according to claim 1, further comprising: means based on attendance information in a person's company. Means for presenting to the cardholder the settlement data that has not yet been used to calculate the amount of subsidization;
Means for receiving input from the cardholder, the input indicating changing the settlement data having the first display to the settlement data having the second display;
The payment system according to claim 1, further comprising: means for updating the payment data presented to the cardholder based on the received input.   4. The apparatus according to claim 2 or 3, further comprising means for updating the settlement data in which the time indicated by the date and time information included in the settlement data is within a time zone specified by a company with the first display. Checkout system described in. The card payment message is an authorization message for credit card payment,
A means for generating second billing data for the cardholder based on the calculated meal subsidy amount, wherein the amount of the second billing data is the total amount of the generated settlement data The payment system according to any one of claims 1 to 4, further comprising: means equal to an amount obtained by subtracting the calculated amount for subsidizing meal cost. The card payment message is a debit card payment message,
A means for generating transfer data for the bank account of the cardholder included in the debit card settlement message based on the calculated meal subsidy amount, wherein the transfer data is the calculated meal The settlement system according to any one of claims 1 to 4, further comprising means for indicating a subsidy amount. The card payment message is a payment message for a prepaid card,
The payment system according to any one of claims 1 to 4, further comprising: means for updating a balance of the prepaid card of the cardholder based on the calculated amount of money for subsidizing meals. A payment method executed by a payment system for subsidizing meals for employees,
The payment data is generated based on the received card payment message, and the payment data includes either a first display indicating a meal charge assistance target or a second display indicating that the meal charge assistance target is not included. The first display and the second display are set based on a company identifier and member store identifier pair included in the settlement data;
Among the payment data, calculating the amount of meal cost assistance based on the payment data having the first display, wherein the amount of meal cost assistance is the amount paid to the cardholder Showing,
Generating a billing data for a company based on the calculated meal subsidy amount. Read the settlement data that has not yet been used to calculate the amount of money for subsidizing meals, and with respect to the corporate system associated with the company identifier included in the readout settlement data, of the readout settlement data Sending at least a user identifier and date and time information;
Receiving update information associated with the transmitted user identifier and date / time information from the enterprise system, and updating the settlement data based on the update information, wherein the update information is stored in the card The payment method according to claim 8, further comprising: based on attendance information in a person's company. Presenting the cardholder with the settlement data that has not yet been used to calculate the amount of the meal support;
Receiving input from the cardholder, wherein the input indicates changing the settlement data having the first display to the settlement data having the second display;
The settlement method according to claim 8, further comprising: updating the settlement data presented to the cardholder based on the received input.   The method according to claim 9, further comprising: updating the settlement data in which the time indicated by the date and time information included in the settlement data is within a time zone specified by a company in the first display. The settlement method described. The card payment message is an authorization message for credit card payment,
Generating the second billing data for the cardholder based on the calculated meal subsidy amount, wherein the amount of the second billing data is the total amount of the generated settlement data The payment method according to any one of claims 8 to 11, further comprising: an amount equal to an amount obtained by subtracting the calculated amount of subsidized meal cost. The card payment message is a debit card payment message,
Generating transfer data for the bank account of the cardholder included in the debit card payment message based on the calculated meal subsidy amount, wherein the transfer data is the calculated meal The payment method according to any one of claims 8 to 11, further comprising: indicating a subsidy amount. The card payment message is a payment message for a prepaid card,
The payment method according to any one of claims 8 to 11, further comprising: updating the balance of the prepaid card of the cardholder based on the calculated amount of subsidized meal fee.   The program for making a computer perform the method as described in any one of Claims 8 thru | or 14.