Management device

Abstract

For payments made using a designated payment service, only the portion equivalent to the actual monetary value used by the user for gaming will be treated as a payment. [Solution] The operator-side management device 4 includes a ticket type assignment unit 402 on which the user purchases a first ticket type linked to information of the second value from the first value; an information storage unit 401 that receives information related to the purchase ID and purchase amount in response to the execution of the purchase process for the first ticket type; a charge unit 404 that charges the third value used for playing based on the first ticket type purchased by the user; and a settlement processing unit 406 that requests the settlement processing unit 3 to execute a return process for the first ticket type corresponding to the purchase ID, and also requests the execution of a new purchase process to purchase a second ticket type different from the first ticket type by subtracting the amount of first value equivalent to the remaining balance of the third value after playing from the amount of first value used to purchase the first ticket type.

Description

Technical Field

[0001] The present invention relates to a management device.

Background Art

[0002] In the game of a gaming machine, it has been considered to introduce cashless settlement for the charge of valuable value used for lending out game balls. The following prior art documents disclose systems available when cashless settlement is introduced.

[0003] For example, in Patent Document 1, a system is disclosed that aims to support cashless settlement in a game arcade. The system determines whether the valuable value associated with a storage medium (ball lending card) is for cash deposit or for cashless settlement. When it is determined that the valuable value includes both the cash deposit portion and the cashless settlement portion, the cash deposit portion of the valuable value is settled in cash, and the cashless settlement portion of the valuable value is refunded to an account. Also, in Patent Document 2, a system is disclosed that aims to appropriately support multiple settlement methods in a game arcade. The system includes a value - adding means capable of adding value to a game medium by multiple purchase methods, a value management means for managing the remaining value in association with the purchase method, and a settlement means capable of settling the remaining value by multiple settlement methods.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] The systems described in the aforementioned prior art aim to distinguish between cashless payments and cash payments and to implement settlement processing appropriate to each payment method, but they have the following problems, for example. Specifically, the process from payment to settlement is not adequately managed, and when using existing cashless payment systems, while these cashless payments often award points or other valuable assets, it is not possible to ensure that points equivalent to the amount of payment actually used for the game are awarded at the time of settlement after playing.

[0006] Therefore, the present invention aims to appropriately manage the process from settlement to final settlement, so that, for settlements using a predetermined settlement service, only the amount equivalent to the actual monetary value used by the user in the game is treated as having been settled. [Means for solving the problem]

[0007] To achieve the above objective, a management device according to one aspect of the present invention further comprises: a ticket purchase means (e.g., a ticket granting unit 402) for a user to purchase a first ticket, which is a second value, from a first value used in a predetermined payment service; a purchase information receiving means (e.g., an information storage unit 401) in a payment processing device that provides a payment service to a user, which receives purchase identification information and information related to the purchase amount in response to the execution of the purchase process for the first ticket; a charging means (e.g., a charging unit 404) that performs charging of a third value used for gaming based on the first ticket purchased by the user; and a first settlement processing means (e.g., a settlement processing unit 406) that requests the payment processing device to perform a return process for the first ticket corresponding to the purchase identification information, and requests the payment processing device to perform a new purchase process for purchasing a second ticket different from the first ticket by subtracting the quantity of first value equivalent to the remaining balance of third value after the user has played the game from the quantity of first value used to purchase the first ticket.

[0008] The system includes: a ticket type purchase information storage means (e.g., an information storage unit 401) that stores ticket type purchase information associating purchase identification information corresponding to the purchase of a first type of ticket with the quantity of a second value; a second settlement processing means (e.g., a settlement processing unit 406) that performs an update process to update the quantity of the second value to the quantity obtained by subtracting the quantity of the third value remaining after the user has played from the quantity of the third value that has been charged; and a return processing execution request feasibility determination means (e.g., a settlement processing unit 406) that determines whether or not a return processing execution request can be made based on predetermined conditions that have been registered in advance. If the return processing execution request feasibility determination means determines that a return processing request cannot be made, the update process may be executed by the second settlement processing means. [Effects of the Invention]

[0009] According to the present invention, the process from payment to settlement is appropriately managed, and for payments made using a predetermined payment service, only the amount equivalent to the actual monetary value used by the user for gaming is treated as having been settled. [Brief explanation of the drawing]

[0010] [Figure 1] This is a schematic diagram illustrating the outline of a management system according to an embodiment of the present invention. [Figure 2] This is a functional block diagram showing the functions of the user terminals that make up the above management system. [Figure 3] This is a functional block diagram showing the functions of the payment processing unit that constitutes the above management system. [Figure 4] This is a functional block diagram showing the functions of the operator-side management device that constitutes the above management system. [Figure 5] This is a functional block diagram showing the functions of the charging machine that constitutes the management system described above. [Figure 6] This is a functional block diagram showing the functions of the settlement device that constitutes the above management system. [Figure 7]In the above management system, the diagram shows the data update status according to the processing progress, and shows (a) assignment information, (b) charge information, (c) settlement information, (d) house money balance, and (e) general-purpose money balance. [Figure 8] This sequence diagram shows the processing flow executed in the above management system, illustrating an example of the process from a user's request for house money to the actual granting of house money. [Figure 9] This sequence diagram shows the processing flow executed in the above management system, illustrating an example of the process from reading the game card at the charging machine, to the card balance being charged, and finally to the user playing the game. [Figure 10] This sequence diagram shows the processing flow executed in the above management system, illustrating another example of the process from reading the game card at the charging machine, to charging the card balance, and finally to the user playing the game. [Figure 11] This sequence diagram shows the processing flow executed in the above management system, illustrating another example of the process from reading the game card at the charging machine, to charging the card balance, and finally to the user playing the game. [Figure 12] This sequence diagram shows the processing flow executed in the above management system, illustrating another example of the process from reading the game card at the charging machine, to charging the card balance, and finally to the user playing the game. [Figure 13] This sequence diagram shows the processing flow executed in the above management system, illustrating another example of the process from reading the game card at the charging machine, to charging the card balance, and finally to the user playing the game. [Figure 14] This sequence diagram shows the processing flow executed in the above management system, illustrating an example of the process from the start of the user's settlement procedure to the completion of the settlement process, specifically the process up to the transmission of charge cancellation information from the settlement device to the operator's management device. [Figure 15] It is a sequence diagram showing the flow of processing executed in the above management system, and shows an example of the processing after return information is transmitted from the operator-side management device to the settlement processing device among the flows from the start of the settlement procedure by the user to the completion of the settlement processing. [Figure 16] It is a sequence diagram showing the flow of processing executed in the above management system, and shows another example of the processing until the settlement processing is executed among the flows from the start of the settlement procedure by the user to the completion of the settlement processing. [Figure 17] It is a sequence diagram showing the flow of processing executed in the above management system, and shows another example of the processing until the charge cancellation information is transmitted among the flows from the start of the settlement procedure by the user to the completion of the settlement processing. [Figure 18] It is a sequence diagram showing the flow of processing executed in the above management system, and shows another example of the flow from the start of the settlement procedure by the user to the completion of the settlement processing. [Figure 19] It is a sequence diagram showing the flow of processing executed in the above management system, and shows another example of the flow from the start of the settlement procedure by the user to the completion of the settlement processing. [Figure 20] It is a sequence diagram showing the flow of processing executed in the above management system, and shows an example of the flow of processing for registering the suspension of use of the game card and determining the availability based on the suspension information.

Mode for Carrying Out the Invention

[0011] ●System Overview Hereinafter, an embodiment of the management system according to the present invention will be described with reference to the drawings.

[0012] Figure 1 shows an example of the overall configuration of the management system 1 according to this embodiment. The management system 1 consists of a user terminal 2, a payment processing device 3, an operator-side management device 4, a charging machine 41, a unit 42, a gaming machine 43, and a settlement device 44. The user terminal 2 also implements an application program (hereinafter referred to as "payment app 21") that works in cooperation with the payment processing device 3 to execute the payment services provided by the payment processing device 3, and an application program (hereinafter referred to as "management app 22") that works in cooperation with the operator-side management device 4 to perform transactions and settlements of valuable assets necessary for playing games on the gaming machine 43. The devices or terminals that constitute the management system 1 described above are just examples, and may include various devices or terminals that operate in a typical hall, such as monitoring terminals used by hall staff to monitor the hall, or counting machines for counting game balls.

[0013] In this embodiment, among the devices or terminals that constitute the management system 1, the payment processing device 3 and the payment application 21 implemented on the user terminal 2 constitute the payment service provision system 11 and work together to provide payment services to the user. In addition, the operator-side management device 4, the charging machine 41, the unit 42, the gaming machine 43, the settlement device 44, and the management application 22 implemented on the user terminal 2 constitute the gaming service provision system 12 and work together to provide gaming services to the user.

[0014] The payment service provision system 11 is a system that provides payment services related to the purchase of goods and services, and handles transactions based on the real value of legal tender or electronic money held by the user. Users of the system can make payments when purchasing goods and services. The payment processing device 3 and the user terminal 2 implementing the payment application 21, which constitute the payment service provision system 11, are configured to communicate with each other via a communication network NW1. The communication network NW1 is, for example, the internet, and may be constructed using public telephone networks, mobile phone networks, wireless communication channels, Ethernet (registered trademark), etc.

[0015] The gaming service provision system 12 is a system for providing gaming services to users using gaming machines 43, such as pachinko and slot machines, within a hall. It processes and manages information necessary to provide gaming services using gaming machines 43 to users, including charging the balance on the card used by the user to play on the gaming machines 43, conducting transactions to charge the card balance, and managing the operating status of the gaming machines 43 within the hall. This gaming service provision system 12 is managed by the operator that operates the gaming services. In this embodiment, the operator providing the gaming service to users may consist of multiple operators, such as a person who manages the valuable assets used during gaming and a person who operates the hall. Hereafter, in the description of this embodiment, the operators who operate the gaming service will be collectively referred to as "operator" without distinction. Of the devices or terminals constituting this gaming service provision system 12, the operator-side management device 4, the charging machine 41, the unit 42, the gaming machine 43, and the settlement device 44 are configured to communicate via the communication network NW2. The communication network NW2 is, for example, a LAN, but may be constructed by a dedicated line, whether wired or wireless. However, the communication network NW2 may consist of multiple types of communication networks, and may include public communication networks such as the Internet. For example, if the operator-side management device 4 is implemented by a server or cloud computer on the Internet, the operator-side management device 4 and other devices and terminals are configured to communicate via the Internet. In addition, the operator-side management device 4 and the user terminal 2, which implements the management application 22, are configured to communicate via the communication network NW1.

[0016] The management system 1, configured in this manner, executes and manages the transaction of valuable assets that users use to borrow gaming media for gaming in the provision of gaming services by the gaming machine 43, and the settlement of any remaining valuable assets after gaming. The gaming machine 43 is, for example, a pachinko or slot machine that uses a game medium such as game balls (pachinko balls) or tokens to play the game. In this embodiment, unless otherwise specified, the explanation will be given using the case where the gaming machine 43 is a pachinko machine and the game medium is game balls as an example.

[0017] When a user borrows a gaming medium, they receive a gaming card from the hall and then charge the card balance to the card as a predetermined value used for borrowing gaming mediums. The user then borrows gaming mediums up to the limit of the card balance. In this embodiment, house money issued and managed by the operator providing the gaming service can be used to charge the card balance. In this embodiment, this house money is electronic money that can be managed as digital data, and the user can obtain it through a payment service provided by the payment processing device 3. Notwithstanding this embodiment, the card balance may also be available for purchase with cash in addition to house money.

[0018] In this hall, two types of cards are used as gaming cards: a general card and a membership card. A standard card is a prepaid card issued by the hall to an unspecified user on a case-by-case basis, and its use is generally limited to the same day. A membership card is a card that can be used at specific amusement parlors or their affiliated stores, and is issued to each registered user and held by the user. Both general cards and membership cards are, for example, magnetic cards or IC cards, and record a card ID as identification information for the game card, as well as information such as the card balance corresponding to the user's charge amount and the number of game tokens (tokens) the user has won through gameplay. However, the operator's management device 4 may manage information such as the card balance and tokens linked to the card ID. In this case, unit 42 receives the card balance linked to the card ID from the operator's management device 4 based on the card ID recorded on the game card, recognizes the card balance, and transmits the card balance after gameplay to the operator's management device 4. This allows the operator's management device 4 to recognize the card balance after gameplay.

[0019] The game card is an example of a recording medium that stores identification information (recording medium identification information) for identifying the person to whom the game medium is lent. This recording medium does not have to be the game card mentioned above; any recording medium that can store recording medium identification information is acceptable. For example, the user terminal 2 may be used as the recording medium, or a card originally intended for use other than the management system 1 may be used. Furthermore, the recording medium identification information only needs to be unique information that can identify the person to whom the gaming medium is lent. As long as it can fulfill this role, it may be identification information that is not prepared for the management system 1, such as the terminal identification information (IMEI) of user terminal 2, or the management application ID of management application 22 may be used.

[0020] In addition, while the management system 1 handles three types of value, in this embodiment, for the sake of explanation, the value handled in the payment service provision system 11 may be referred to as "general-purpose money," the value used to borrow game media when playing games on the game machine 43 may be referred to as "card balance," and the value handled in transactions of the said card balance may be referred to as "house money."

[0021] Furthermore, a "voucher type" is defined as an item (thing) to which information about house money obtained by the user through the payment service provided by the payment processing device 3 is linked. When a user obtains house money through that payment service, it is considered that they have purchased a voucher type to which that house money information is linked. In other words, obtaining house money and purchasing a voucher type are synonymous. However, while house money is updated through card balance transactions, etc., voucher types are not updated. Voucher types can be purchased in units of 100 yen per loan handled in the game (loan processing), and the purchase amount ranges from 100 yen to 10,000 yen per voucher type.

[0022] ●User terminal 2 User terminal 2 is a terminal used by users who receive gaming services from gaming machines 43 within the hall. Users use this user terminal 2 to receive payment services and perform the necessary processing and operations to receive gaming services. This user terminal 2 is implemented by a portable smart device such as a smartphone, and as shown in the example in Figure 2, it mainly consists of a functional block comprising an information storage unit 201, a reading unit 202, an input / output unit 203, and a communication unit 204.

[0023] The information storage unit 201 is a functional unit that stores various types of information and is implemented using a solid-state drive, flash memory, or the like.

[0024] The reading unit 202 is a functional unit that reads two-dimensional barcodes such as QR codes (registered trademark), and is implemented, for example, by a CCD camera or a CMOS camera. Information can be obtained by decoding the code read by this reading unit 202.

[0025] The input / output unit 203 is a functional unit that accepts input and operations of various types of information and outputs information, and is implemented by, for example, a touch panel, a speaker, etc.

[0026] The communication unit 204 is a functional unit that performs data transmission and reception with the payment processing device 3 and the operator-side management device 4 via the communication network NW1 using a predetermined communication protocol, and is implemented by a browser program or the like.

[0027] In this embodiment, as described above, the user terminal 2 implements a payment application 21 for executing payment services provided by the payment processing device 3 and a management application 22 for conducting house money transactions.

[0028] The payment application 21 is an application program for providing payment services to users, and it works in cooperation with the payment processing device 3, functioning as an interface for users when making payments. This payment application 21 comprises a functional unit consisting of an information storage unit 211, a purchase processing unit 212, a first ID issuance unit 213, and a communication processing unit 214.

[0029] The information storage unit 211 is an area reserved in the information storage unit 201 of the user terminal 2, and stores information necessary for the execution of the functions of the payment application 21. This information storage unit 211 stores at least the payment application ID used by the payment processing unit 3 and the operator-side management device 4 to identify the user or the payment application 21. In addition, it may also store the purchase ID issued by the first ID issuing unit 213 (described later), purchase processing logs, and balance information of general-purpose money linked to the payment application ID. However, the payment application 21 may store only the payment application ID, and the payment processing unit 3 may manage the other information. In this case, the payment application 21 may communicate with the payment processing unit 3 to obtain information linked to the payment application ID. The payment app ID can be any information that can identify the user or the payment app 21, and may be information pre-configured in the payment app 21 or information set by the user. It may also be the terminal identification number (IMEI) pre-configured in the user terminal 2.

[0030] The purchase processing unit 212 is a functional unit that, in accordance with the user's instructions, is responsible for executing settlements related to the purchase and payment of goods and services using the user's general-purpose money. This purchase processing unit 212 works in cooperation with the payment processing unit 3 to execute the necessary processing on the user terminal 2 side for settlements in which the user pays a predetermined amount to the operator of the gaming service using the user's general-purpose money. For example, when a user requests the granting of house money on the management application 22, and payment becomes necessary as a result, the purchase processing unit 212 receives an operation from the user to pay a predetermined amount of general-purpose money to the operator of the gaming service. In response, the purchase processing unit 212, via the communication processing unit 214, sends a request to the payment processing unit 3 to execute the purchase process. When the payment processing unit 3 executes the purchase process, the communication processing unit 214 receives purchase information from the payment processing unit 3 as the result of the purchase process execution.

[0031] The first ID issuing unit 213 issues a purchase ID (purchase identification information) that can identify the purchase process in conjunction with the execution of the purchase process. The purchase ID may be issued when a request to execute the purchase process is received from the user, or when a purchase process request is sent from the user terminal 2 to the payment processing unit 3, or it may be issued when the purchase process is executed in the payment processing unit 3 and purchase information is received from the payment processing unit 3 as a result of the execution of the purchase process. In the embodiment in which the purchase ID is issued by the payment processing device 3, the payment application 21 does not necessarily need to be equipped with the first ID issuing unit 213. Additionally, the purchase ID may be associated with a flag indicating the execution status and result of the purchase process.

[0032] The communication processing unit 214 communicates with the payment processing unit 3 via the communication unit 204 and performs the sending and receiving of various information. Through this communication processing unit 214, the payment application 21 sends a purchase processing request to the payment processing unit 3 and receives purchase information from the payment processing unit 3 as a result of the purchase processing.

[0033] The management app 22 is an application program for executing transactions and managing information necessary when users play games in the hall. It works in cooperation with the operator's management device 4 and functions as an interface for users to receive house money or top up their card balance. This management application 22 comprises a functional unit consisting of an information storage unit 221, a second ID issuance unit 222, a coding processing unit 223, an information acquisition unit 224, and a communication processing unit 225.

[0034] The information storage unit 221 is an area reserved in the information storage unit 201 of the user terminal 2, and stores information necessary for the execution of the management application 22's functions. This information storage unit 221 stores at least the management application ID used by the operator-side management device 4 to identify the user or the management application 22. In addition, it may also store the charge ID, charge log, and house money balance information linked to the management application ID, which will be described later. However, the management application 22 may store only the management application ID, while the operator-side management device 4 manages the other information. In this case, the management application 22 may communicate with the operator-side management device 4 to obtain information linked to the management application ID. The management app ID can be any information that can identify the user or the management app 22, and may be information pre-configured in the management app 22 or information set by the user. It may also be the terminal identification number (IMEI) pre-configured in the user terminal 2. However, the payment app ID and the management app ID must be different and distinguishable from each other.

[0035] The second ID issuing unit 222 issues a charge ID (charge identification information) that can identify a charge to the card balance when a user charges the card balance. The charge ID is issued, for example, when a user obtains the card ID of the game card to be charged from the charging machine 41 in order to charge the card at the charging machine 41. Furthermore, if the operator-side management device 4 or the charging machine 41 is equipped with a charge ID issuance function, this second ID issuance unit 222 does not necessarily have to be provided in the management application 22.

[0036] The coding processing unit 223 codes the information necessary for the transaction into a two-dimensional code such as a QR code (registered trademark). The information to be coded is, for example, the charge ID issued by the second ID issuing unit 222. If the charging machine 41 is equipped with a reading processing unit 412 (see Figure 5) that reads the two-dimensional code, the charging machine 41 can obtain the charge ID from the two-dimensional code displayed on the screen of the user terminal 2 by the reading processing unit 412. Furthermore, the coding processing unit 223 can also code other information, such as the management application ID, in addition to the charge ID.

[0037] The information acquisition unit 224 reads the coded information from the reading unit 202 and decodes it, thereby acquiring the coded information. This information acquisition unit 224 can, for example, acquire a charge ID and card ID as request information for the charge process using a two-dimensional code displayed on the screen of the charge machine 41, or acquire a charge ID and card ID as authentication information for the settlement process using a two-dimensional code displayed on the screen of the settlement device 44.

[0038] The communication processing unit 225 communicates with the operator-side management device 4 via the communication unit 204 and performs the transmission and reception of various types of information. For example, this communication processing unit 225 functions as a purchase information transmission means that transmits purchase information indicating the execution result of the purchase process performed by the payment processing unit 3 to the operator-side management device 4. Furthermore, it functions as a charge request processing means that transmits a request to the operator-side management device 4 for charging the card balance using house money held by the user, along with the card ID, a charge ID that identifies the charge processing of the card balance associated with the game card, and the charge request amount. Furthermore, it functions as an authentication request processing means that sends an authentication request to the operator-side management device 4, along with the card ID and charge ID, requesting authentication of the legitimacy of the settlement.

[0039] The management application 22 configured in this manner constitutes the management device of the present invention, either on its own or together with the operator-side management device 4.

[0040] ●Payment processing device 3 The payment processing device 3 is a device that provides payment services related to the purchase of goods and services, and executes payments based on the actual legal tender or electronic money held by the user, in accordance with the user's request. In this embodiment, the payment service provided by this payment processing device 3 is provided for transactions in which the user receives house money used to charge their card balance, using various general-purpose currencies.

[0041] One example of a payment service is a service that enables transactions by transferring electronic money between accounts of trading partners. In this example, so-called common electronic money usable at amusement parlors belonging to the service's member stores is used as general-purpose money. The payment processing device 3 manages, for example, the electronic money accounts of trading partners or the information of such accounts for the purpose of transactions, and in accordance with a request from a designated trading partner, it deposits electronic money into the designated trading partner's account or transfers electronic money from the designated trading partner's account to the account of another trading partner. In this example, when the payment processing device 3 receives a payment request from a user requesting to pay a predetermined amount of electronic money to the operator, it executes a process to transfer the electronic money from the user's account to the operator's account.

[0042] Another example of a payment service is a service that enables transactions by transferring legal tender between the accounts of the parties involved in the transaction. In this example, actual legal tender is used as general-purpose money. The payment processing device 3 manages, for example, the bank accounts of the parties involved in the transaction or information about those bank accounts, and, in accordance with a request from a designated party, transfers legal tender from the designated party's bank account to the bank account of another party involved in the transaction. In this example, when the payment processing device 3 receives a payment request from a user requesting that a predetermined amount of legal tender be paid to the operator, it executes a process to transfer the legal tender from the user's account to the operator's account.

[0043] Another example of a payment service is a service that enables transactions through credit sales. In this example, at amusement parlors belonging to the service's member stores, traders make payments using credit cards (information associated with credit cards) under the credit provision of a credit company. The payment processing device 3 makes advance payments to designated trading partners and debits payments from the bank accounts of other trading partners according to the transaction. In this example, actual legal tender, or equivalent value, provided as credit to the user by the credit company, is used as general-purpose money. In this example, when the payment processing device 3 receives a payment request from a user requesting a predetermined amount to be paid by credit card, it performs a payment advance to the operator.

[0044] The payment application 21 is provided according to the type of payment service described above, and the user installs the payment application 21 corresponding to the payment service they use on the user terminal 2. The payment processing unit 3 receives payment request information from the user on the payment application 21, including information specifying the user account and the operator to be traded, and a predetermined amount, and performs the payment based on the payment request information. When the payment processing unit 3 sends a payment completion notification to the payment application 21, a payment completion screen is displayed on the payment application 21.

[0045] This payment processing device 3 is implemented, for example, by a so-called server computer and is equipped with hardware resources such as a CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), and a hard disk drive, as well as software resources such as computer programs executed by the CPU. As shown in the example in Figure 3, it mainly constitutes a functional block consisting of an information storage unit 301, a purchase processing unit 302, an ID issuance unit 303, a return processing unit 304, a new purchase processing unit 305, a point issuance unit 306, a point cancellation unit 307, and a communication processing unit 308.

[0046] The information storage unit 301 stores information about users of the payment service and electronic payment history information. In this embodiment, users of the payment service include both users and operators. User information includes, for example, user account information, bank account information, information about general-purpose money held by the user, and information about points awarded to the user in accordance with the payment.

[0047] The purchase processing unit 302 executes a payment to the operator using the general-purpose money held by the user, in accordance with the user's request to execute a purchase process. The quantity (amount) of general-purpose money to be paid, i.e., the payment amount, can be specified by the user, for example, on the management application 22. As a payment service, actual legal tender provided to the user by a credit company is used as general-purpose money. Purchase information related to the settlement result is registered in the information storage unit 301 and transmitted to the user terminal 2. This purchase information includes, for example, information related to the purchase ID and the purchase amount.

[0048] The ID issuing unit 303 issues a purchase ID (purchase identification information) that identifies the purchase process executed by the purchase processing unit 302 and the new purchase process executed by the new purchase processing unit 305, which will be described later. The purchase ID is issued at the time the purchase process and the new purchase process are executed, and in that timeline, it may be issued before the execution of the process or after the execution of the process. Furthermore, the purchase ID may be issued by the payment application 21, in which case the payment processing device 3 does not need to have an ID issuing unit 303.

[0049] The return processing unit 304 returns the ticket type that the user has purchased for gameplay in response to a request from the operator's management device 4. More specifically, when the return processing unit 304 receives a request from the operator's management device 4 for a return of the ticket type (first ticket type) purchased in the purchase process corresponding to a predetermined purchase ID, it returns the ticket type purchased in the purchase process corresponding to that purchase ID. The system may be configured to send a notification to the operator's management device 4 once the return of a specified type of ticket is completed.

[0050] In response to the return processing unit 304 returning a ticket type purchased in a purchase process corresponding to a predetermined purchase ID, the new purchase processing unit 305 executes a new purchase process to purchase a different ticket type (second ticket type) from the previously purchased ticket type, using a quantity obtained by subtracting the amount of general-purpose money equivalent to the remaining card balance after the user has played from the amount of general-purpose money settled by the user in the purchase process corresponding to the predetermined purchase ID. When executing the new purchase process, the ID issuing unit 303 may issue a new purchase ID that can identify the new purchase process, or a different ticket type from the previously purchased ticket type may be purchased, or the content of the purchase process itself may be updated without changing the previous purchase ID. Through this new purchase processing by the new purchase processing unit 305, the user retrospectively executes a settlement for general-purpose money equivalent to the amount of house money or card balance actually used for gameplay. In this invention, the new purchase processing unit 305, together with the return processing unit 304 described above, constitutes the settlement means in the payment processing unit 3.

[0051] The point issuance unit 306 awards points to the user in proportion to the amount of general-purpose money used for payment when a purchase is processed by the purchase processing unit 302. It also awards points to the user in proportion to the amount of general-purpose money used for payment when a new purchase is processed by the new purchase processing unit 305. Points will be awarded at a predetermined rate, and users can use them in accordance with the predetermined usage method.

[0052] The point cancellation unit 307 cancels the issuance of points granted to the user by the purchase process corresponding to a predetermined purchase ID when the ticket type purchased by the purchase process corresponding to a predetermined purchase ID is returned by the return processing unit 304. As a result, similar to general-purpose money, only points corresponding to the amount of general-purpose money settled, equivalent to the amount of house money or card balance actually used by the user for gameplay, are issued to the user.

[0053] The communication processing unit 308 performs data transmission and reception with the user terminal 2 and the operator-side management device 4. The communication processing unit 308 allows the payment processing unit 3 to receive purchase processing requests from the user terminal 2 and to transmit purchase information, including the purchase ID and purchase amount, as a result of the purchase process. The payment processing unit 3 also receives return information from the operator-side management device 4 requesting the return of a ticket type purchased in a predetermined purchase process and transmits new purchase information related to the results of a new purchase process.

[0054] ● Operator-side management device 4 The operator-side management device 4 is a device that manages information related to the user's gaming, such as deposits of house money and charges to card balances. This operator-side management device 4 is implemented by a so-called server computer and is equipped with hardware resources such as a CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), and a hard disk drive, as well as software resources such as computer programs executed by the CPU. As shown in the example in Figure 4, it mainly constitutes a functional block consisting of an information storage unit 401, a ticket type assignment unit 402, an ID issuance unit 403, a charge unit 404, an authentication processing unit 405, a settlement processing unit 406, and a communication processing unit 407. Furthermore, the operator-side management device 4 does not necessarily have to be installed in the hall, and some or all of its functions may be implemented by a cloud computer. In addition, the operator-side management device 4 may consist of multiple hardware resources distributed according to the type of function to be performed. In this case, these multiple hardware resources are connected by wired or wireless means and transmit and receive information from each other.

[0055] The information storage unit 401 is a storage unit that stores various types of information related to the user's transactions. The information stored includes, for example, user information, grant information, charge information, and settlement information.

[0056] User information is information about the user. This user information includes at least a management application ID that can identify the management application 22 used by the user. In addition, information handled by the management application 22 may include, as appropriate, the ID and password used by the user to log in to the system via the management application 22, as well as information such as the balance of house money and card balance. Furthermore, for registered users, information related to the user's gaming, such as the user's name or registered name, the user's contact information (e.g., email address, phone number, address, etc.), and the number of tokens the user has saved, may also be included as appropriate.

[0057] The grant information is information that indicates the details of the house money granting process that was executed in accordance with the purchase process after the purchase process was executed at the user's instruction. As shown in the example in Figure 7(a), this grant information includes a payment app ID that can identify the payment app 21 used by the user during the purchase process, a management app ID that can identify the management app 22 used by the user during the purchase process, a purchase ID that can identify the purchase process corresponding to the granting of house money, and the quantity (amount) and type of house money granted to the user. This information is interconnected.

[0058] Charge information is information that shows the details of the card balance charge process. As shown in the example in Figure 7(b), this charge information includes a management app ID that can identify the management app 22 used by the user when charging, a card ID that can identify the game card used by the user, a charge ID that can identify the charge process, and the amount of the charged card balance. This information is interconnected.

[0059] Settlement information is information generated by the settlement device 44 during settlement processing and indicates the details of the settlement process. This settlement information includes the payment application ID, card ID, charge ID, and settlement amount, as shown in the example in Figure 7(c).

[0060] The ticket type assignment unit 402 assigns house money and ticket types to the user in accordance with the amount of general-purpose money paid by the user to the operator through the purchase process executed by the payment processing unit 3. The ticket type assignment unit 402 can grasp the contents of the purchase information from the purchase information received from the user terminal 2 and the purchase information received from the payment processing unit 3, and thereby assigns house money to the user in accordance with the purchase amount.

[0061] The ID issuing unit 403 issues a charge ID (charge identification information) that can identify the charging of the card balance. This ID issuing unit 403 issues a charge ID when the card balance is charged by the charge unit 404, which will be described later. Furthermore, if the charge ID is issued by the user terminal 2 or the charge machine 41, the operator-side management device 4 does not necessarily need to be equipped with an ID issuing unit 403.

[0062] The charge unit 404 performs a charge process that uses the house money held by the user to charge a card balance corresponding to the charge request amount, associated with the card ID and charge ID. The charge process performed by the operator-side management device 4 subtracts an amount of house money from the house money held by the user that corresponds to the charge request amount, and stores the card balance corresponding to the amount of house money subtracted in the information storage unit 401, associated with the card ID and charge ID. As a result, the user is granted a card balance. Regarding the charge process, if the issuers of the house money and the card balance are different, for example, a transfer of electronic money or legal tender to each account is performed in the background, and the house money is deducted and the card balance is charged accordingly. In other words, when a user requests a charge to their card balance, a predetermined amount corresponding to the charge request is transferred from the house money issuer's account to the card balance issuer's account. This transfer is accompanied by information that identifies the user who requested the charge, such as the user account and card ID. As a result, for the specified user, the house money is deducted and the card balance is charged according to the result of the transfer.

[0063] When the authentication processing unit 405 receives settlement authentication information from the user terminal 2 during card balance settlement, it performs an authentication process to authenticate the legitimacy of the user receiving the settlement. This process involves referring to the information storage unit 401 and determining whether the settlement authentication information matches the information stored in the information storage unit 401. The settlement authentication information includes, for example, the mutually associated card ID and charge ID.

[0064] The settlement processing unit 406 performs the information processing necessary for settling the card balance.

[0065] As one of its functions, the settlement processing unit 406 executes a settlement process to set the card balance associated with the game card to zero, based on a settlement request received from the management application 22 or the settlement device 44, when the game card is a membership card. The settlement request received from the management application 22 or the settlement device 44 includes information that identifies the settlement target, such as the card ID, management application ID, and charge ID, as well as the settlement amount. The settlement processing unit 406 can refer to the information storage unit 401 to identify the card balance to be settled from the management application ID linked to the charge ID included in the settlement request.

[0066] Furthermore, as one of its functions, the settlement processing unit 406 requests the payment processing unit 3, via the communication processing unit 407 (described later), to perform a return process and a new purchase process for the ticket type purchased in the purchase process corresponding to a predetermined purchase ID. As a result, the payment processing unit 3 receives a request to perform a return process to return the ticket type purchased in the purchase process related to the predetermined purchase ID, as well as a request to perform a new purchase process to purchase a ticket type different from the purchased ticket type, using a quantity obtained by subtracting the amount of general-purpose money equivalent to the remaining card balance after the user has played from the amount of general-purpose money the user has settled in accordance with the predetermined purchase ID. Furthermore, the settlement processing unit 406 can identify a predetermined purchase ID for a ticket type purchased during the purchase process that is eligible for return, by referring to the information storage unit 401 and based on the management application ID linked to the charge ID received from the management application 22 or the settlement device 44. This process of identifying the predetermined purchase ID can also be performed in the execution of other functions described later.

[0067] Furthermore, as one of its functions, the settlement processing unit 406 updates information in response to settlement execution requests received from the user terminal 2 or settlement device 44, settlement execution information received from the settlement device 44, or the execution of return processing and new purchase processing for the ticket type purchased by the settlement processing unit 3 in response to a new purchase processing execution request. For example, regarding the information provided, the amount of house money corresponding to the purchase ID that identifies a predetermined purchase process subject to settlement processing will be updated to a quantity obtained by subtracting the amount equivalent to the remaining card balance after the user has played the game from that quantity. Furthermore, regarding the charge information, the amount of the card balance charged in accordance with the charge ID will be updated to a quantity obtained by subtracting the amount equivalent to the card balance remaining after the user has played games from that quantity.

[0068] Furthermore, as one of its functions, the settlement processing unit 406 cancels and adds information in response to settlement execution requests received from the user terminal 2 or settlement device 44, settlement execution information received from the settlement device 44, or the execution of return processing and new purchase processing for the ticket type purchased by the settlement processing unit 3 in response to a new purchase processing execution request. For example, the first assignment information corresponding to the first purchase ID that identifies the first purchase process subject to settlement processing is canceled, and a second assignment information is registered that associates the second purchase ID newly issued by the new purchase process with the amount obtained by subtracting the amount of house money equivalent to the remaining card balance after the user has played from the amount of house money associated with the first purchase ID. Furthermore, the first charge information corresponding to the charge ID that identifies the first charge transaction subject to settlement processing is canceled, and a second charge information is registered that associates the newly issued second charge ID with the amount obtained by subtracting the amount equivalent to the remaining card balance after the user has played from the amount of the card balance associated with the first charge ID. In either case, the first grant information or first charge information that was subject to settlement processing will be retained as historical information.

[0069] Furthermore, as one of its functions, the settlement processing unit 406 determines whether or not to request a return of the ticket type purchased by the settlement processing unit 3, based on predetermined conditions that have been registered in advance. The predetermined conditions are, for example, based on the predetermined return period for the ticket type, and whether or not the purchase date of the ticket type for which a return is requested is a past date that exceeds the return period. If the purchase date is a past date that exceeds the return period, the unit determines that the request for the return is not to be processed. The settlement processing unit 406 determines whether to request the execution of the above-mentioned return process based on predetermined conditions. If it determines that the request is not valid, it executes the update process; if it determines that the request is valid, it does not perform any processing. The update process updates the assigned information by changing the amount of house money corresponding to the purchase ID that identifies the predetermined purchase process subject to settlement to the amount obtained by subtracting the amount of card balance remaining after the user has played from the amount of card balance charged corresponding to the charge ID. Furthermore, a predetermined condition is, for example, whether or not a request to execute a return process can be made to the payment processing device 3. If a request to execute a return process cannot be made, specifically if communication with the payment processing device 3 is interrupted or the system on the payment processing device 3 side is stopped, the request to execute the return process is determined to be denied. Another predetermined condition is, for example, whether or not the number of return processes during a predetermined period is less than the upper limit, or whether or not the amount related to the return process during a predetermined period is less than the upper limit.

[0070] Furthermore, the settlement processing unit 406, as one of its functions, determines the legitimacy of the card balance at the time of settlement based on pre-registered specific conditions. The specific conditions include, for example, whether the legitimacy of the card balance is recognized when the usage history (game history) of the game card charged from the ticket type managed by the operator-side management device 4 is matched with the balance of third-party value remaining after the user has played games. The settlement processing unit 406 determines the legitimacy of the card balance at the time of settlement based on specific conditions. If legitimacy is confirmed, it approves the request to execute a new purchase process to purchase a different type of card than the one purchased. If legitimacy is not confirmed, it rejects the request.

[0071] Furthermore, the settlement processing unit 406 described above can be configured to execute only one of its functions or a combination of multiple functions, provided that these functions do not conflict with each other.

[0072] The communication processing unit 407 transmits and receives various types of information with the user terminal 2, the payment processing unit 3, and other devices and terminals that make up the gaming service provision system 12. For example, the communication processing unit 407 receives a request to execute a settlement process from the user terminal 2 or the settlement device 44 based on the charge ID. At this time, the communication processing unit 407 functions as a settlement request receiving means. Furthermore, the communication processing unit 407 functions as a charge identification information inquiry receiving means that receives inquiries for the charge ID along with the card ID of the game card from the settlement device 44. It also functions as a charge identification information transmission means that transmits the charge ID associated with the card ID to the settlement device 44 in response to this inquiry. Furthermore, the communication processing unit 407 functions as an authentication request receiving means that receives an authentication request from the user terminal 2, along with the card ID and charge ID, requesting authentication of the legitimacy of the settlement. In the authentication process performed by the authentication processing unit 405 in response to this, if authentication is successful, it functions as an authorization information transmitting means that transmits authorization information to the settlement device 44, allowing the settlement of the card balance associated with the charge ID. If authentication fails, it functions as a restriction information transmitting means that transmits restriction information to the settlement device 44, restricting the settlement of the card balance associated with the charge ID. Furthermore, the communication processing unit 407 functions as a charge request receiving means that receives a charge request from the user terminal 2 or the charging machine 41, along with the card ID, charge ID, and charge request amount, for charging the card balance using house money held by the user. Furthermore, the communication processing unit 407 functions as a settlement execution information receiving means that receives settlement execution information indicating that settlement has been performed, along with the charge ID, from the settlement device 44.

[0073] ●Charging machine 41 The charging machine 41 is an example of a charging device that charges a card balance to a game card in an amount corresponding to a predetermined exchangeable quantity, based on the amount of house money specified by the user. This charging machine 41 is equipped with hardware resources such as a CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), and flash memory, as well as software resources such as computer programs executed by the CPU. As shown in the example in Figure 5, it mainly constitutes a functional block consisting of an information storage unit 411, a read processing unit 412, a read / write processing unit 413, an ID issuance unit 414, a coding processing unit 415, a charging unit 416, an input / output unit 417, and a communication processing unit 418.

[0074] The information storage unit 411 is a functional unit that stores various types of information and is implemented by a solid-state drive, flash memory, or the like.

[0075] The reading processing unit 412 has the function of reading the two-dimensional code displayed on the user terminal 2 and decoding and obtaining the encoded information, and is implemented using a CCD camera or scanner. The charging machine 41 can use this reading processing unit 412 to read, for example, the charge ID and management application ID from the two-dimensional code displayed on the user terminal 2.

[0076] The read / write processing unit 413 is a functional unit that reads information such as the card ID recorded on the game card and writes information such as the card balance to the game card, and is implemented, for example, by a reader / writer.

[0077] The ID issuing unit 414 issues a charge ID (charge identification information) that can identify a charge to the card balance when a user charges the card balance. The charge ID is issued, for example, when the read / write processing unit 413 reads the card ID and the card ID is coded by the coding processing unit 415 (described later), and is coded together with the card ID. Furthermore, if the management application 22 or the operator-side management device 4 is equipped with a charge ID issuance function, the ID issuance unit 414 does not necessarily have to be installed in the charging machine 41.

[0078] The coding processing unit 415 codes the card ID of the game card read by the reading / writing processing unit 413 and the charge ID issued by the ID issuing unit 414 into a two-dimensional code. In addition, other information such as the card balance can also be included in the information to be coded.

[0079] The charge unit 416 performs a charge process that uses the house money held by the user to charge a card balance corresponding to the charge request amount, in association with the card ID and charge ID. The charge process by the charge machine 41 is performed in the operation of recording the card balance on the game card. Specifically, the amount of house money equivalent to the charge request amount is deducted from the house money held by the user, and the card balance corresponding to the amount of house money deducted is recorded on the game card by the read / write processing unit 413. Regarding the charging process by the charging unit 416, if the user is charging a card balance to a membership card they already possess, the charging machine 41 receives the membership card from the user, charges the card balance to the membership card, and returns it to the user. On the other hand, if the game card is a general card or if a new membership card is to be issued, in response to the user's charge request, the machine either charges a predetermined card balance to a game card stocked in the machine and issues it, or issues a game card from the machine's stock that already has a predetermined charge amount charged to it.

[0080] The input / output unit 417 is a functional unit that accepts input and operations of various types of information and outputs information, and is implemented by, for example, a touch panel, display, speaker, etc.

[0081] The communication processing unit 418 transmits and receives data with the operator-side management device 4 via the communication network NW2 in accordance with a predetermined communication protocol.

[0082] ●Unit 42 Unit 42 is a device, also called an inter-machine machine, installed for each gaming machine 43. It lends gaming media to the user within the limits of the balance on the gaming card and dispenses the gaming media from the dispensing mechanism of the gaming machine 43. Furthermore, unit 42 may be equipped with a banknote deposit device and capable of lending gaming media to users within the limits of the amount deposited through the banknote deposit device.

[0083] This unit 42 includes a counting unit that counts the game media dispensed from the game machine 43 and collected via the unit 42 using a counting sensor, a balance processing unit that reads the card ID and card balance from the game card using a reader / writer, and associates the balance (number of game media held) indicating the amount of game media obtained by the user through playing on the game machine 43, and the card balance after playing with the game card. When the card balance is managed by the operator's management device 4, the balance processing unit communicates with the operator's management device 4, receives information on the card balance associated with the card ID from the operator's management device 4 when the user starts playing, and transmits information on the card balance associated with the card ID to the operator's management device 4 in accordance with the use of the card balance.

[0084] Notwithstanding this embodiment, unit 42 may also be equipped with the functions of the charging machine 41 described above. In this case, unit 42 constitutes the charging machine 41 in the process of charging the card balance. Furthermore, unit 42 may be equipped with the functions of the settlement device 44 described later. In this case, unit 42 constitutes the settlement device 44 in the settlement process of the card balance.

[0085] ●Gaming machine 43 The gaming machine 43 is a device in which a user plays a game using a game medium, such as a pachinko machine or a slot machine. The game medium is a game ball (pachinko ball) for pachinko or a token for a slot machine. The game medium does not have to have a physical form and may be provided to the user as an idea, and it broadly includes any medium necessary to play a game on the gaming machine 43.

[0086] ●Payment device 44 The settlement device 44 is a device that performs a settlement process to set the card balance associated with the game card to zero. This settlement device 44 is equipped with hardware resources such as a CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), and flash memory, as well as software resources such as computer programs executed by the CPU. As shown in the example in Figure 6, it mainly constitutes a functional block consisting of an information storage unit 441, a read processing unit 442, a read / write processing unit 443, a coding processing unit 444, a settlement processing unit 445, an input / output unit 446, and a communication processing unit 447.

[0087] The information storage unit 441 is a functional unit that stores various types of information and is implemented by a solid-state drive, flash memory, or the like.

[0088] The reading processing unit 442 has the function of reading the two-dimensional code displayed on the user terminal 2 and decoding and acquiring the coded information, and is implemented using a CCD camera or scanner.

[0089] The read / write processing unit 443 is a functional unit that reads information such as the card ID and card balance recorded on the game card, and writes information such as the card balance to the game card, and is implemented, for example, by a reader / writer.

[0090] The coding processing unit 444 codes the card ID of the game card read by the read / write processing unit 443 into a two-dimensional code. The information to be coded may include not only the card ID, but also information related to the charge ID and card balance. For example, the charge ID is obtained by querying the operator's management device 4 based on the card ID. If the card balance is managed by the operator's management device 4, it can be obtained by querying the operator's management device 4 based on the card ID, and receiving a response to the query. On the other hand, if the card balance is recorded on the game card, it can be obtained by reading the game card with the read / write processing unit 443.

[0091] The settlement processing unit 445 performs a settlement of the card balance recorded on the game card, which has been read by the read / write processing unit 443, in order to perform the settlement process. Specifically, it instructs the read / write processing unit 443 to overwrite the card balance recorded on the game card with zero.

[0092] The input / output unit 446 is a functional unit that accepts input and operations of various types of information and outputs information, and can be implemented by, for example, a touch panel, display, speaker, etc. This input / output unit 446 can display a two-dimensional code encoded by the coding processing unit 444 of various IDs, or display payment instructions to the user. Furthermore, the input / output unit 446 constitutes an identification information provision means that provides various IDs to the user terminal 2 by outputting various IDs encoded in a two-dimensional code in a manner that can be read by the user terminal 2. However, the identification information provision means is not limited to the example where various IDs are encoded by the coding processing unit 444 and provided to the user; as long as various IDs can be provided to the user terminal 2, the identification information provision means can also be realized by short-range wireless communication such as NFC communication.

[0093] The communication processing unit 447 transmits and receives data with the operator-side management device 4 via the communication network NW2 in accordance with a predetermined communication protocol. For example, the communication processing unit 447 functions as a charge ID inquiry transmission means that sends an inquiry to the operator-side management device 4 for a charge ID that identifies the process of charging the card balance to the game card, along with the card ID. In response, it also functions as a charge identification information receiving means that receives the charge ID associated with the card ID from the operator-side management device 4. Furthermore, the communication processing unit 447 functions as a settlement permission information receiving means that receives settlement permission information from the operator-side management device 4 based on the results of an authentication process that authenticates the legitimacy of settlement, which is performed based on the card ID and charge ID acquired by the user terminal 2.

[0094] ●Other examples of functional configurations Furthermore, in the management system 1 described above, the functional units of the charging machine 41 and the settlement device 44 may be integrated into one of the devices, or into a separate device, so that the card balance charging process and settlement process can be executed together in either the charging machine 41 or the settlement device 44, or one of the devices.

[0095] Furthermore, in describing the functions of the devices or terminals constituting the management system 1 described above, the main components for implementing the present invention have been mentioned. However, notwithstanding this, known devices, terminals, or functional units that are provided in actual hall operations may be appropriately provided. For example, it may include a counting machine for counting the number of balls dispensed, a cash processing mechanism that enables cash transactions, and a ticket issuing device that issues receipts with barcodes indicating the remaining game value. Furthermore, the functional components of each device or terminal may not always be necessary depending on how they are used, and in such cases, unnecessary functional components may be omitted. [Examples]

[0096] The processes executed in the management system 1 according to Example 1 will be described below with reference to the diagram. Figure 8 shows the process flow from when a user makes a payment based on general currency until they receive house money. First, when a user performs an operation on the management application 22 to request the granting of a predetermined amount of house money (S101), a payment corresponding to the granting of that predetermined amount of house money is requested. In response, the user sends a request to the payment processing device 3 on the payment application 21 to pay the operator an amount of general-purpose money corresponding to the predetermined amount of house money, and also sends a request to execute the purchase process (S102).

[0097] The payment processing device 3, in response to a purchase processing request from the user, issues a purchase ID via the ID issuing unit 303 (S103), and the purchase processing unit 302 executes the payment based on pre-held information such as the user's and operator's accounts (S104). In addition, the point issuing unit 306 issues points to the user in a quantity corresponding to the payment amount in response to the execution of the payment (S105). Once payment is complete, the payment processing device 3 transmits purchase information, including at least the purchase ID and purchase amount, to the user terminal 2 (S106), and the user confirms the purchase information on the payment application 21.

[0098] The management application 22 receives purchase information from the payment application 21 and transmits the purchase information to the operator's management device 4 (S107). Furthermore, the purchase information transmitted from the payment application 21 to the operator-side management device 4 may differ in some respects from the purchase information received by the payment application 21 from the payment processing device 3. For example, it may include information related to the payment application ID, management application ID, purchase ID, and purchase amount.

[0099] When the operator management device 4 confirms, based on the purchase information, that payment for a predetermined quantity of house money corresponding to general-purpose money has been completed, the ticket type granting unit 402 grants the predetermined quantity of house money to the user and also grants the user the ticket type corresponding to the house money (S108), and stores the granting information in the information storage unit 401 (S109).

[0100] In this embodiment, the operator-side management device 4 may confirm the execution of the purchase process solely based on the purchase information received from the user terminal 2, or it may also receive purchase information indicating the execution of the purchase process from the payment processing device 3 separately, and then confirm the execution of the purchase process by matching the purchase information received from the user terminal 2 and the payment processing device 3. Alternatively, the operator-side management device 4 may request authentication from the payment processing device 3 along with the purchase information received from the user terminal 2, and the user may be granted house money and denominations according to the authentication result. Furthermore, although the payment processing device 3 issued the purchase ID in the example described above, the user terminal 2 may issue the purchase ID and send it to the payment processing device 3 along with the purchase processing request. [Examples]

[0101] Figure 9 shows the process flow from when a user charges their card balance using house money to when they start playing. In this example, the card balance is managed by the operator's management device 4. The charging machine 41 reads the card ID of the game card (S201). When reading the card ID, if the user already possesses an issued membership card, the charging machine 41 reads the card ID from the membership card using the read / write processing unit 413. On the other hand, if the user does not yet possess a game card, the read / write processing unit 413 reads the card ID from a game card that is stocked in the machine as a newly issued game card. Once the charging machine 41 has read the game card using the read / write processing unit 413 and obtained the card ID, the coding processing unit 415 codes the card ID into a two-dimensional code and displays it on the screen (S202).

[0102] The charging machine 41 may accept input from the user for the charge request amount either before or after reading the game card. In this case, the charge request amount may be coded into a two-dimensional code along with the card ID. However, the user may be able to input the charge request amount on the management application 22 at an appropriate timing before the transmission of the charge information described later. Furthermore, when displaying the two-dimensional code, the charging machine 41 may also display the card balance, or it may encode the card balance together with the card ID into the two-dimensional code. In this example, the card balance is held by the operator's management device 4, and the charging machine 41 can retrieve the card balance from the operator's management device 4 based on the card ID.

[0103] The user obtains the card ID by reading a two-dimensional code containing at least the card ID from the charging machine 41 using the user terminal 2 (S203). In response, when the second ID issuing unit 222 issues a charge ID (S204), charge request information requesting a charge is sent to the operator-side management device 4 (S205). This charge request information includes, for example, information relating to the management application ID, card ID, charge ID, and the charge request amount. Furthermore, when sending a charge request, an operation to confirm the execution of sending the charge information, such as pressing a button on the screen, may be included.

[0104] When the operator-side management device 4 receives charge information from the user terminal 2, the charge unit 404 performs a charge process that deducts the user's house money according to the charge request amount and charges the card balance according to the charge request amount (S206). In response to the execution of the charge process, the charge information is registered in the information storage unit 401 (S207). The charge machine 41 then ejects a game card (issues a new game card if one is to be issued) when it receives information from the operator-side management device 4 that the charge information has been registered. The results of the charge process and the card balance after the charge process can be checked by the user, for example, on the management application 22. Users who have received a charge on their card balance can then enjoy playing games on the gaming machine 43 using their gaming card (S208).

[0105] In this embodiment, the charging machine 41 may issue a charge ID, and this charge ID may be encoded into a two-dimensional code along with the card ID. As a result, the user terminal 2, upon reading the two-dimensional code, obtains both the charge ID and the card ID at the same time. Furthermore, although this embodiment involves obtaining the card ID from the game card, the card ID may be stored in the management application 22 beforehand, and when the user terminal 2 requests a charge process from the operator-side management device 4, the card ID stored in the management application 22 may be called. This allows the operator-side management device 4 to be requested to perform a charge process without having to operate the charge machine 41. [Examples]

[0106] Figure 10 shows a modified version of Embodiment 2, illustrating the processing flow when a request to charge the card balance using house money is made on the user terminal 2 when the card balance is recorded on the game card. The charging machine 41 reads the card ID of the game card (S301). When reading the card ID, if the user already possesses an issued membership card, the charging machine 41 reads the card ID from the membership card using the read / write processing unit 413. On the other hand, if the user does not yet possess a game card, the read / write processing unit 413 reads the card ID from a game card that is stocked in the machine as a newly issued game card. Once the charging machine 41 obtains the card ID using the read / write processing unit 413, the charging machine 41 encodes the card ID into a two-dimensional code using the encoding processing unit 415 and displays it on the screen (S302).

[0107] The user obtains the card ID by reading a two-dimensional code containing at least the card ID from the charging machine 41 using the user terminal 2 (S303). In response, when the second ID issuing unit 222 issues a charge ID (S304), charge request information requesting a charge is sent to the operator-side management device 4 (S305). This charge request information includes, for example, information relating to the management application ID, card ID, charge ID, and the charge request amount. Furthermore, the input of the charge request amount and the display of the card balance on the charging machine 41 can be performed in the same manner as in Example 2.

[0108] The operator-side management device 4 checks whether there is a quantity of house money equivalent to the charge request amount specified by the user and determines whether the charge process can be executed (S306). If the user has a quantity of house money equivalent to the charge request amount and the charge process can be executed, the operator-side management device 4 sends a request to the charge machine 41 to execute a charge process for the charge request amount specified by the user (S307). In response, the charging machine 41 performs a charging process using the charging unit 416 (S308). That is, the charging unit 416 instructs the read / write processing unit 413 to record the card balance corresponding to the charge request amount onto the game card. Upon execution of the charging process, the game card is ejected from the charging machine 41 (or issued if a new game card is to be issued). Furthermore, before the charging process is executed, the user may be required to perform an operation to confirm the execution of the charging process, such as pressing a button on the screen of the charging machine 41.

[0109] The charge information related to the result of the charge process is transmitted from the charge machine 41 to the operator-side management device 4 (S309) and registered in the information storage unit 401 of the operator-side management device 4 (S310). This charge information includes, for example, the management application ID, card ID, charge ID, and information related to the charged card balance. In addition, the operator-side management device 4 deducts the user's house money according to the charged card balance along with registering the charge information. The results of the charge process and the card balance after the charge process can be checked, for example, on the charge machine 41, and the user who has received the charge on their card can enjoy playing games on the game machine 43 using the game card (S311).

[0110] In this embodiment, as in Embodiment 2, the charging machine 41 may issue a charge ID, and this charge ID may be encoded into a two-dimensional code along with the card ID. As a result, the user terminal 2, which reads the two-dimensional code, obtains both the charge ID and the card ID at the same time. Furthermore, similar to Example 2, the card ID may be pre-stored in the management application 22, and when the user terminal 2 requests a charge process from the operator-side management device 4, the card ID stored in the management application 22 may be retrieved. This allows the user to request a charge process from the operator-side management device 4 without having to operate the charge machine 41. [Examples]

[0111] Figure 11 shows a modified example of Embodiment 2, illustrating the processing flow when a request to charge the card balance using house money is made on the charging machine 41, in a case where the card balance is managed by the operator-side management device 4. The charging machine 41 reads the card ID of the game card (S401). When reading the card ID, if the user already possesses an issued membership card, the charging machine 41 reads the card ID from that membership card using the read / write processing unit 413. On the other hand, if the user does not yet possess a game card, the read / write processing unit 413 reads the card ID from a game card that is stocked in the machine as a newly issued game card.

[0112] Next, the user is requested by the charging machine 41 to obtain a management application ID. In response, the user operates the management application 22, and the coding processing unit 223 displays the management application ID, which has been coded into a two-dimensional code, on the screen (S402). The user then has the reading processing unit 412 of the charging machine 41 read the two-dimensional code. Upon obtaining the management application ID (S403), the charging machine 41 issues a charge ID using the ID issuing unit 414 (S404).

[0113] The charging machine 41 requests the operator's management device 4 to execute the charging process, along with the card ID, management application ID, charge ID, and charge information relating to the charge request amount (S405). The charging machine 41 receives information regarding the charge request amount from the user at a predetermined timing before sending the charge processing execution request to the operator-side management device 4. Furthermore, when sending the charge request, an operation to confirm the execution of sending the charge information, such as pressing a button on the screen of the charging machine 41, may be included.

[0114] When the operator-side management device 4 receives charge information from the user terminal 2, the charge unit 404 performs a charge process that deducts the user's house money according to the charge request amount and charges the card balance according to the charge request amount (S406). In response to the execution of the charge process, the charge information is registered in the information storage unit 401 (S407). The charge machine 41 then ejects a game card (issues a new game card if one is to be issued) when it receives information from the operator-side management device 4 that the charge information has been registered. The results of the charge process and the card balance after the charge process can be checked by the user, for example, on the management application 22. Users who have received a charge on their card balance can then enjoy playing games on the gaming machine 43 using their gaming card (S408).

[0115] In this embodiment, the user terminal 2 may be instructed to issue a charge ID, and this charge ID may be encoded into a two-dimensional code along with the management application ID. As a result, the charging machine 41, upon reading the two-dimensional code, obtains both the charge ID and the management application ID at the same time. Furthermore, as in Example 2, the card ID may be stored in the management application 22 beforehand, and when encoding into a two-dimensional code, the card ID stored in the management application 22 may be called up. This eliminates the need for the user to have the charging machine 41 read the game card. Furthermore, in Examples 2 to 4, a charge ID that can identify the charge process is issued, and information such as the charge amount is linked to the charge ID. However, instead of issuing a charge ID, information related to the charge amount may be linked to the management app ID and card ID, and the charge process may be identified by the management app ID and card ID. [Examples]

[0116] Figure 12 shows a modified example of Embodiment 4, illustrating the processing flow when a request to charge the card balance using house money is made on the charging machine 41 when the card balance is recorded on the game card. The charging machine 41 reads the card ID of the game card (S501). When reading the card ID, if the user already possesses an issued membership card, the charging machine 41 reads the card ID from the membership card using the read / write processing unit 413. On the other hand, if the user does not yet possess a game card, the read / write processing unit 413 reads the card ID from a game card that is stocked in the machine as a newly issued game card. When the charging machine 41 receives an issued game card from the user and obtains the card ID from the game card, it may also obtain the card balance if one is recorded on the game card. Furthermore, if the charging machine 41 obtains the card balance, it may display the card balance on the screen.

[0117] Next, the user is requested by the charging machine 41 to obtain a management application ID. In response, the user operates the management application 22, and the coding processing unit 223 displays the management application ID, which has been coded into a two-dimensional code, on the screen (S502). The user then has the reading processing unit 412 of the charging machine 41 read the two-dimensional code. Upon obtaining the management application ID (S503), the charging machine 41 issues a charge ID using the ID issuing unit 414 (S504).

[0118] The charging machine 41 confirms with the operator's management device 4 that the charging process has been executed (S505). That is, it checks whether there is a quantity of house money equivalent to the amount of the charge request specified by the user, and confirms whether the charging process can be executed. Furthermore, the charging machine 41 accepts input of the charge request amount from the user at any time between receiving the charge request operation and sending confirmation of the execution of the charge process to the operator-side management device 4. However, the user may input the charge request amount on the management application 22, and the charge request amount may be encoded into a two-dimensional code along with the management application ID. In this case, the charging machine 41 can obtain both the management application ID and the charge request amount by reading the two-dimensional code.

[0119] When the charging machine 41 receives information from the operator's management device 4 authorizing the execution of the charging process (S506), the charging unit 416 executes the charging process (S507). That is, the charging unit 416 instructs the read / write processing unit 413 to record the card balance corresponding to the charge request amount onto the game card. In response to the execution of the charging process, the game card is ejected from the charging machine 41 (or issued if a new game card is to be issued). Furthermore, before the charging process is executed, the user may be required to perform an operation to confirm the execution of the charging process, such as pressing a button on the screen of the charging machine 41.

[0120] The charge information related to the result of the charge process is transmitted from the charge machine 41 to the operator-side management device 4 (S508) and registered in the information storage unit 401 of the operator-side management device 4 (S509). This charge information includes, for example, the management application ID, card ID, charge ID, and information related to the charged card balance. In addition, the operator-side management device 4 deducts the user's house money according to the charged card balance along with registering the charge information. The results of the charge process and the card balance after the charge process can be checked, for example, on the charge machine 41, and the user who has received the charge on their card can enjoy playing games on the game machine 43 using the game card (S510). [Examples]

[0121] Figure 13 shows a modified version of Example 2, illustrating the process flow from when the card balance is recorded on the game card, when a purchase request is made from the operator's management device 4 to the payment processing device 3 in response to a user request, to the charging of the card balance and the start of the game. The user performs a charge request operation at the charging machine 41 to charge the balance on their game card (S601). The charge request operation is an operation to request the operator's management device 4 to charge the card balance, and first the user is asked to have their card ID read.

[0122] The user has the charging machine 41 read the game card. The charging machine 41 reads the game card using the read / write processing unit 413 and obtains the card ID (S602). If a card balance is recorded on the game card, the charging machine 41 may read the card balance using the read / write processing unit 413 and display the card balance on the screen.

[0123] The charging machine 41 reads the card ID using the reading / writing processing unit 413, encodes it into a two-dimensional code using the encoding processing unit 415, and displays it on the screen (S603). The charging machine 41 may issue a charge ID using the ID issuing unit 414 and encode the charge ID together with the card ID into a two-dimensional code.

[0124] The user obtains the card ID by reading a two-dimensional code containing at least the card ID from the charging machine 41 using the user terminal 2 (S604). Then, along with the predetermined charge request amount, the card ID, and the application ID being used, the user requests the charge processing from the operator's management device 4 (S605). Furthermore, if the charging machine 41 issues a charge ID, the charge processing request will include that charge ID. However, instead of having the charging machine 41 issue the charge ID, the management application 22 may issue the charge ID using the second ID issuing unit 222 and include that charge ID in the charge processing request. Alternatively, instead of having the charging machine 41 or the management application 22 issue the charge ID, the ID issuing unit 403 of the operator-side management device 4 may be used to issue the charge ID.

[0125] When the operator-side management device 4 receives a charge processing request from the user terminal 2, it requests the payment processing device 3 to perform a purchase process to pay the operator a quantity corresponding to the charge request amount from the user (S606). In this purchase processing request, the operator-side management device 4 has previously received user information necessary for the payment processing device 3 to perform the purchase process in the user's name, and transmits this information along with the purchase processing request.

[0126] The payment processing device 3, in response to a request from the operator-side management device 4, issues a purchase ID via the ID issuing unit 303 (S607) and executes the purchase process via the purchase processing unit 302 (S608). In addition, upon execution of the purchase process, the point issuing unit 306 issues points to the user in a quantity corresponding to the payment amount. Once the purchase process is complete, the payment processing device 3 transmits purchase information, including the purchase ID and purchase amount, to the operator-side management device 4 (S609).

[0127] When the operator-side management device 4 confirms the completion of the purchase process, it assigns a predetermined amount of house money and a predetermined amount of tickets to the user based on the purchase information using the ticket type assignment unit 402 (S610), and stores the assignment information in the information storage unit 401 (S611). Furthermore, the charge unit 404 performs a charge process that deducts the user's house money according to the charge request amount and charges the card balance according to the charge request amount (S612). In response to the execution of the charge process, the charge information is registered in the information storage unit 401 (S613). Furthermore, if a charge ID is received from the user terminal 2 during the charge process, the charge ID is registered in the information storage unit 401. On the other hand, in the configuration where the charge ID is issued by the operator-side management device 4, the operator-side management device 4 issues the charge ID using the ID issuance unit 403 when executing the charge process.

[0128] The results of the charge process and the card balance after the charge process can be checked by the user, for example, on the management application 22. Users who have received a charge on their card balance can then enjoy playing games on the gaming machine 43 using their gaming card (S614).

[0129] In this embodiment, the operator-side management device 4 initially granted house money to the user in response to the execution of the purchase process in the payment processing device 3, and then charged the card balance. However, the process of granting house money may be omitted, and the card balance may be charged in response to the execution of the purchase process. Furthermore, the purchase ID may be issued by the operator's management device 4. [Examples]

[0130] Figures 14 and 15 illustrate the processing flow when a user receives a settlement of their card balance. This example shows the case where the card balance is recorded on the game card. First, as shown in Figure 14, the user has the game card read by the settlement device 44 (S701). The settlement device 44 reads the card ID and card balance from the game card using the read / write processing unit 443, and then queries the operator management device 4 for the charge ID associated with the card ID (S702).

[0131] When the operator-side management device 4 responds to an inquiry from the settlement device 44 and returns the charge ID associated with the card ID (S703), the settlement device 44 uses the coding processing unit 444 to encode the settlement information consisting of the card ID, charge ID, and card balance into a two-dimensional code and displays the two-dimensional code on the screen (S704).

[0132] The user reads the two-dimensional code containing the settlement information using the reader unit 202 of the user terminal 2 and obtains the settlement information (S705). In response, the management application 22 generates settlement authentication information by adding the management application ID to the settlement information, and then transmits this settlement authentication information to the operator-side management device 4 along with a settlement authentication request (S706).

[0133] Upon receiving settlement authentication information from the user terminal 2, the operator-side management device 4 performs authentication processing using the authentication processing unit 405 (S707). If authentication is successful, it transmits settlement authorization information to the settlement device 44 (S708). The settlement authorization information includes, at a minimum, a charge ID as information that can identify the information subject to settlement processing, but may also include a card ID and information related to the card balance. On the other hand, if authentication fails, error handling is performed (S709). Error handling includes, for example, sending an error notification to the user terminal 2 and displaying the authentication error on the management application 22. Alternatively, the error notification may also be sent to the payment device 44 and the authentication error may be displayed on the screen of the payment device 44, or the occurrence of the authentication error may be notified to the terminal used by the hall administrator.

[0134] When the settlement device 44 receives settlement permission information from the operator-side management device 4, the settlement processing unit 445 executes the settlement process (S710). That is, the settlement device 44 overwrites the card balance recorded on the game card with zero using the read / write processing unit 443. As a result of executing the settlement process, the settlement device 44 sends charge cancellation information to the operator-side management device 4 (S711). The charge cancellation information includes at least a charge ID as information that identifies the target of the settlement process, but may also include a card ID and information related to the settled card balance.

[0135] Next, as shown in Figure 15, the operator-side management device 4, upon receiving the charge cancellation information, uses the settlement processing unit 406 to identify the purchase ID associated with the charge ID that indicates the target of the settlement process, and then transmits return information to the payment processing device 3, requesting a return process and a new purchase process for the ticket type purchased in the purchase process corresponding to the said purchase ID (S720). The return information includes, at least, the purchase ID indicating the purchase process to be returned, as well as information relating to the settlement amount, i.e., the card balance after settlement or the amount of general-purpose money equivalent to the card balance after settlement.

[0136] Although not shown in the diagram, the operator-side management device 4 determines whether or not to request the execution of a return process based on predetermined conditions registered in advance by the settlement processing unit 406, and if it determines that the request is not to execute, it executes the update process described above.

[0137] Upon receiving return information from the operator-side management device 4, the payment processing device 3, via the return processing unit 304, returns the ticket type purchased in the purchase process related to the predetermined purchase ID (S721). Furthermore, in conjunction with this, the point cancellation unit 307 cancels the points issued in the purchase process related to the purchase ID to be returned (S722). Next, the payment processing unit 3 issues a new purchase ID via the ID issuing unit 303 (S723), and the new purchase processing unit 305 executes a new purchase process to purchase a different type of ticket than the one purchased, using a quantity obtained by subtracting the amount of general-purpose money equivalent to the remaining card balance after the user has played from the amount of general-purpose money the user has paid for in accordance with the predetermined purchase ID (S724). At the same time, the point issuing unit 306 issues points to the user corresponding to the amount of general-purpose money paid for in the new purchase process (S725). Once the new purchase process is complete, the payment processing device 3 sends a notification to the operator-side management device 4 that the return of the ticket type purchased in the purchase process linked to the specified purchase ID has been completed, along with the new purchase information (S726). The new purchase information includes at least the newly issued purchase ID and information related to the purchase amount.

[0138] The operator-side management device 4 updates the information in the information storage unit 401 in response to the receipt of new purchase information (S727). Specifically, regarding the purchase information, the purchase ID of the returned item will be overwritten with a new purchase ID, and the amount of house money granted through payment will be overwritten with the amount corresponding to the purchase amount of the new purchase. Furthermore, regarding the charge information, based on the charge ID identified in the charge cancellation information, the charged card balance will be overwritten with a quantity corresponding to the purchase amount in the new purchase process. This overwritten card balance quantity is the amount obtained by subtracting the quantity equivalent to the card balance remaining after the user played from the quantity of the card balance charged by the type of ticket purchased in the purchase process corresponding to the specified purchase ID that was subject to return, i.e., it represents the card balance actually used by the user for playing.

[0139] In addition, the operator-side management device 4 may, instead of updating the information in the information storage unit 401 in response to the receipt of new purchase information, perform information cancellation and additional registration. Specifically, with respect to the purchase information, the first grant information corresponding to the first purchase ID that identifies the first purchase process that was subject to return processing is canceled, and a second grant information is added, which includes a second purchase ID newly issued by the new purchase process and the amount of house money corresponding to the purchase amount of the new purchase process. With respect to this newly registered grant information, the amount of house money granted to the user through payment is the amount obtained by subtracting the amount of house money equivalent to the card balance remaining after the user played from the amount of house money associated with the canceled first purchase ID, that is, the amount of house money that the user actually used to charge their card balance. This makes it possible to identify the amount of house money that the user actually used to charge their card balance. Furthermore, the first grant information or first charge information that is subject to settlement processing will be retained as history information.

[0140] Furthermore, the operator-side management device 4 may perform processing related to updating or canceling and registering at least the charge information before sending the return information to the payment processing device 3. [Examples]

[0141] Figure 16 shows a modified example of Embodiment 7, illustrating the processing flow when a user receives a settlement of their card balance. This example shows the case where the card balance is managed by the operator's management device 4. First, the user has the settlement device 44 read the game card (S801). The settlement device 44 reads the card ID from the game card using the read / write processing unit 443, and then queries the operator's management device 4 for the charge ID and card balance associated with the card ID (S802).

[0142] When the operator-side management device 4 responds to an inquiry from the settlement device 44 and returns information related to the charge ID linked to the card ID and the card balance (S803), the settlement device 44 uses the coding processing unit 444 to encode the settlement information consisting of the card ID, charge ID, and card balance into a two-dimensional code and displays the two-dimensional code on the screen (S804).

[0143] The user reads the two-dimensional code containing the settlement information using the reader unit 202 of the user terminal 2 and obtains the settlement information (S805). In response, the management application 22 generates settlement authentication information by adding the management application ID to the settlement information, and then transmits this settlement authentication information to the operator-side management device 4 along with a settlement authentication request (S806).

[0144] Upon receiving settlement authentication information from the user terminal 2, the operator-side management device 4 performs authentication processing using the authentication processing unit 405 (S807). If authentication is successful, the settlement processing unit 406 performs settlement processing (S808). Specifically, in this settlement processing, the settlement processing unit 406 of the operator-side management device 4 sets the card balance held by the user to zero. On the other hand, if authentication fails, error handling is performed (S809). Error handling includes, for example, sending an error notification to the user terminal 2 and displaying the authentication error on the management application 22. Alternatively, the error notification may also be sent to the payment device 44 and the authentication error may be displayed on the screen of the payment device 44, or the terminal used by the hall administrator may be notified of the occurrence of the authentication error.

[0145] In response to the execution of the settlement process, the operator-side management device 4 transmits the return information to the settlement processing device 3, as described with reference to Figure 15 in Example 7, and receives the execution of the return process and new purchase process for the ticket type purchased in the purchase process. [Examples]

[0146] Figure 17 shows a modified version of Example 7, illustrating the processing flow when a user receives a settlement of their card balance. This example shows a case where the card balance is recorded on the game card, and the process of authenticating the legitimacy of the settlement is omitted. First, the user has the settlement device 44 read the game card (S901). The settlement device 44 reads the card ID and card balance from the game card using the read / write processing unit 443, and then queries the operator management device 4 for the charge ID associated with the card ID (S902).

[0147] When the operator-side management device 4 responds to an inquiry from the settlement device 44 and returns information relating to the management app ID and charge ID linked to the card ID (S903), the settlement device 44 displays settlement information consisting of the management app ID and card balance on the screen (S904). Furthermore, the screen displaying the settlement information may also include buttons or other features that allow the user to approve the settlement information and request the execution of the settlement process.

[0148] When the settlement device 44 receives an operation from the user requesting the execution of settlement processing (S905), the settlement processing unit 445 executes the settlement processing (S906). That is, the settlement device 44 overwrites the card balance recorded on the game card with zero using the read / write processing unit 443. The settlement device 44 transmits charge cancellation information to the operator-side management device 4 as a result of executing the settlement process (S807). The charge cancellation information includes at least a charge ID as information that identifies the target of the settlement process, but may also include a card ID and information related to the settled card balance.

[0149] Upon receiving the charge cancellation information, the operator-side management device 4 transmits the return information to the payment processing device 3, as described with reference to Figure 15 in Example 7, and receives the execution of the return processing and new purchase processing for the ticket type purchased in the purchase process. [Examples]

[0150] Figure 18 shows a modified version of Example 7, illustrating the processing flow when a user receives a settlement of their card balance. This example shows the case where the card balance is recorded on the game card. First, the user has the settlement device 44 read the game card (S1001). The settlement device 44 reads the card ID and card balance from the game card using the read / write processing unit 443, and then queries the operator management device 4 for the charge ID associated with the card ID (S1002).

[0151] When the operator-side management device 4 responds to an inquiry from the settlement device 44 and returns the charge ID associated with the card ID (S1003), the settlement device 44 uses the coding processing unit 444 to encode the settlement information consisting of the card ID, charge ID, and card balance into a two-dimensional code and displays the two-dimensional code on the screen (S1004).

[0152] The user reads the two-dimensional code containing the settlement information using the reader unit 202 of the user terminal 2 and obtains the settlement information (S1005). In response, the management application 22 generates settlement authentication information by adding the management application ID to the settlement information, and then transmits this settlement authentication information to the operator-side management device 4 along with a settlement authentication request (S1006).

[0153] Upon receiving settlement authentication information from the user terminal 2, the operator-side management device 4 performs authentication processing using the authentication processing unit 405 (S1007). If authentication is successful, it transmits settlement authorization information to the settlement device 44 (S1008). The settlement authorization information includes, at a minimum, a charge ID as information that can identify the information subject to settlement processing, but may also include a card ID and information related to the card balance. On the other hand, if authentication fails, error handling is performed (S1009). Error handling includes, for example, sending an error notification to the user terminal 2 and displaying the authentication error on the management application 22. Alternatively, the error notification may also be sent to the payment device 44 and the authentication error may be displayed on the screen of the payment device 44, or the occurrence of the authentication error may be notified to the terminal used by the hall administrator.

[0154] When the settlement device 44 receives settlement permission information from the operator-side management device 4, the settlement processing unit 445 executes the settlement process (S1010). That is, the settlement device 44 overwrites the card balance recorded on the game card with zero using the read / write processing unit 443. As a result of executing the settlement process, the settlement device 44 sends charge cancellation information to the operator-side management device 4 (S1011). The charge cancellation information includes at least a charge ID as information that identifies the target of the settlement process, but may also include a card ID and information related to the settled card balance.

[0155] Upon receiving the charge cancellation information, the operator-side management device 4 updates the information in the information storage unit 401 based on the charge cancellation information (S1012). Specifically, the user app ID linked to the charge ID to be canceled, and furthermore, the purchase ID linked to that user app ID, are identified, and the grant information linked to that purchase ID is updated. When updating the grant information, the amount of house money is updated to the amount obtained by subtracting the amount equivalent to the card balance remaining after the user has played from the previous amount. Furthermore, regarding the update of charge information identified by the charge ID to be canceled, the charged card balance will be overwritten with a quantity corresponding to the purchase amount in the new purchase process. This overwritten card balance quantity is the amount obtained by subtracting the quantity equivalent to the card balance remaining after the user played from the quantity of the card balance charged by the type of ticket purchased in the purchase process corresponding to the specified purchase ID that was subject to return, i.e., it represents the card balance actually used by the user to play. [Examples]

[0156] Figure 19 shows a modified example of Embodiment 7, illustrating the processing flow when a user receives a settlement of their card balance. This example shows a case where the card balance is recorded on the game card, and the charge ID issued by the management application 22 or charging machine 41 of the user terminal 2 is stored in the management application 22. First, the user has the settlement device 44 read the game card (S1101). The settlement device 44 reads the card ID and card balance from the game card using the read / write processing unit 443, and then the coding processing unit 444 codes at least the card ID into a two-dimensional code and displays the two-dimensional code on the screen (S1102).

[0157] The user reads the coded two-dimensional code using the reader unit 202 of the user terminal 2 and obtains the card ID (S1103). In response, the management application 22 generates settlement authentication information by adding the management application ID and charge ID to the card ID, and then transmits this settlement authentication information to the operator-side management device 4 along with a settlement authentication request (S1104). Alternatively, the card balance may be coded along with the card ID in the settlement device 44, and the user terminal 2 may obtain the card balance and then transmit settlement authentication information, including the card balance, to the operator-side management device 4.

[0158] Upon receiving settlement authentication information from the user terminal 2, the operator-side management device 4 performs authentication processing using the authentication processing unit 405 (S1105). If authentication is successful, it sends settlement authorization information to the settlement device 44 (S1106). The settlement authorization information includes, at a minimum, the card ID associated with the card balance subject to settlement. On the other hand, if authentication fails, error handling is performed (S1107). Error handling includes, for example, sending an error notification to the user terminal 2 and displaying the authentication error on the management application 22. Alternatively, the error notification may also be sent to the payment device 44 and the authentication error may be displayed on the screen of the payment device 44, or the occurrence of the authentication error may be notified to the terminal used by the hall administrator.

[0159] When the settlement device 44 receives settlement permission information from the operator-side management device 4, the settlement processing unit 445 executes the settlement process (S1108). That is, the settlement device 44 overwrites the card balance recorded on the game card with zero using the read / write processing unit 443. As a result of executing the settlement process, the settlement device 44 transmits charge cancellation information to the operator-side management device 4 (S1109). The charge cancellation information includes at least the card ID as information that identifies the target of the settlement process, but the charge ID may be transmitted to the settlement device 44 as part of the charge cancellation information by transmitting the charge ID to the settlement device 44 when transmitting the settlement permission information. The charge cancellation information may also include information related to the settled card balance.

[0160] Upon receiving the charge cancellation information, the operator-side management device 4 transmits the return information to the payment processing device 3, as described with reference to Figure 15 in Example 7, and receives the execution of the return processing and new purchase processing for the ticket type purchased in the purchase process. In this embodiment, since the target of the settlement process is identified by the card ID, it is also possible to manage the charge amount in a way that allows it to be identified by the management app ID and the card ID, without issuing a charge ID at the time of the charge process.

[0161] ● Information update related to processing Figure 7 illustrates the content of the information that is updated according to the status during the series of processes from the purchase process to settlement described above. In Figure 7, (a) to (e) show the values ​​for (a) Grant Information, (b) Charge Information, (c) Settlement Information, (d) House Money Balance, and (e) General Purpose Money Balance at the time of House Money Grant, when the card balance is charged, and when the settlement is completed, respectively. Note that (e) the general-purpose money balance is shown as the "starting" value, which is the value before the house money is granted. Also, it is assumed that the user initially has neither house money nor card balance. Furthermore, in this example, the exchange ratio for general-purpose money, house money, and card balance is 1:1 for all of them. For example, 10,000 general-purpose money grants the same amount of 10,000 house money, and then 10,000 house money grants the same amount of 10,000 card balance.

[0162] In the illustrated example, as shown in Figure 7(e), the user initially possesses "20,000" general-purpose money. The user then requests to make a payment of "10,000" general-purpose money in order to receive "10,000" worth of house money. Once this payment is completed, the house money balance becomes "10,000," as shown in "At Grant Time" in Figure 7(d). Also, as shown in "At Grant Time" in Figure 7(e), the general-purpose money balance is "10,000," which is "20,000" minus "10,000." Furthermore, in accordance with the execution of the purchase process, the house money grant information and denomination information are recorded as shown in "At Grant Time" in Figure 7(a). By referring to the recorded grant information and denomination information, it can be determined that "10,000" of house money and denominations were granted by the purchase process corresponding to purchase ID "1001", and that payment application 21 with payment application ID "R001" and management application 22 with management application ID "P001" were involved in the purchase process.

[0163] When a user requests to charge their card balance by "10,000" using house money, and the charge process is completed, the house money balance becomes "0" as shown in "Charge Complete" in Figure 7(d). On the other hand, as shown in "Charge Complete" in Figure 7(a), the card type (amount granted) remains "10,000". In addition, information related to the charge process is recorded as shown in "Charge Complete" in Figure 7(b). That is, by referring to the recorded charge information, it can be determined that a card balance of "10,000" has been charged to the game card with card ID "C001" by the charge process corresponding to charge ID "2001".

[0164] Here, the user will use a card balance of "8,000" to play the game, and the remaining "2,000" card balance will be settled after the game. When the settlement process for the card balance of "2,000" is executed, as shown in "Settlement Complete" in Figure 7(a), the amount of house money linked to purchase ID "1001" is updated in the grant information from the initially granted "10,000" to "8,000" which the user actually used for gameplay. Here, the voucher type does not indicate that it has been updated like the amount of house money granted, but rather that the "10,000" voucher type was returned through the return process described above, and a new voucher type of "8,000" was purchased through the new purchase process described above. The illustrated example shows a case where a new purchase ID is issued through a new purchase process associated with settlement. Upon completion of settlement, the purchase ID is updated from the previous "1001" to the newly issued "1002". However, it is not always necessary to issue a new purchase ID through a new purchase process; in that case, the purchase ID remains "1001".

[0165] Furthermore, regarding the charge information, as shown in "When settlement is complete" in Figure 7(b), the charge amount of the card balance linked to charge ID "C001" is updated from the initially charged amount of "10,000" to the amount of "8,000" that the user actually used for gaming. Furthermore, the house money balance becomes "0" after the settlement process, as shown in "When settlement is complete" in Figure 7(d). Furthermore, as shown in "When settlement is complete" in Figure 7(e), the general-purpose money balance is updated to "12,000" by subtracting the "8,000" that the user actually used to play from the initial "20,000" due to the return process of the purchased ticket type and the new purchase process.

[0166] In the above explanation, it was assumed that the information would be updated through the return and new purchase processes for the ticket type purchased during the purchase process. However, regardless of this, it is also possible to retain the previous information as a history while adding and registering the new information.

[0167] Furthermore, while the general-purpose money balance in the above example indicates that the payment service is a transaction of electronic money or legal tender between accounts of the parties involved in the transaction, if the payment service is a credit sale transaction such as credit card payment, the general-purpose money balance is managed as, for example, a debt owed by the user to the credit company (a claim from the credit company's perspective). In this case, using the above example, the user would incur a debt of "10,000" in accordance with the initial payment execution, while the user would also incur a debt of "8,000" for the actual amount used for gaming due to the return and new purchase processes of the purchased ticket type.

[0168] According to the management system 1 of this embodiment described above, the process from purchase to settlement is appropriately managed, and for settlements using a predetermined payment service, only the amount equivalent to the actual value used by the user for gaming is treated as having been settled. In addition to the points issued by the settlement, the card balance required for gaming and the house money required to charge the card balance are also treated as if only the amount actually used by the user for gaming was issued. As a result, users can make settlements without worrying about remaining card balances after gaming, and the settlement procedure is simple and hassle-free. Furthermore, for operators, the entire process from settlement execution to return processing and new purchase processing is appropriately and systematically managed, reducing the burden of management and making it convenient.

[0169] Furthermore, according to the management system 1 of this embodiment, even if it is not possible to convert the card balance back to general-purpose money, it becomes possible to convert it back to house money. As a result, the user can continue to use the card balance for gaming, etc., by charging it.

[0170] ●Other examples The invention according to the above embodiment can also be configured as follows. <Example of issuing points by charging the card balance> In the management system 1 according to the embodiment described above, points are issued in response to the settlement of general-purpose money, but points may also be issued in response to the charge amount when the card balance is charged. In this case, the operator-side management device 4 may be equipped with a function unit similar to the point issuance unit 306 and point cancellation unit 307 of the payment processing device 3, and points according to the charge amount may be handled in the same manner as the payment processing device 3. That is, when a settlement process based on a predetermined charge ID is executed, previously issued points are canceled. Furthermore, the amount of the card balance charged in accordance with the predetermined charge ID is updated to the amount obtained by subtracting the amount equivalent to the card balance remaining after the user has played games, i.e., the amount of the card balance actually used by the user to play games, and points corresponding to the updated amount are issued again.

[0171] <Example of registering the suspension of a game card> In the management system 1 according to the above embodiment, it may be possible to register the suspension of use of a game card. In this case, the information storage unit 201 of the operator-side management device 4 and / or a predetermined table provided in unit 42 or settlement device 44 can be used to register the suspension of use of a game card. In addition, the operator-side management device 4 and / or unit 42 or settlement device 44 are provided with determination means for determining whether or not a game card can be used. The suspension information consists of, for example, a management app ID, a card ID, and an availability flag, all of which are associated with each other. The determination means refers to the availability flag to determine whether the game card corresponding to a predetermined card ID is usable.

[0172] An example of the processing flow in this example is shown in Figure 20. For example, if a game card is lost or stolen, the user can perform an operation to deactivate the game card linked to the management application 22 from the management application 22 (S1201). When a user terminal 2 sends a request to the operator management device 4 to deactivate the management application ID and the game card, the operator management device 4 registers this information in the information storage unit 201 (S1202). The deactivation information is then sent to unit 42 and settlement device 44, and registered in predetermined tables, etc., provided in each (S1203).

[0173] When a game is played using a game card, for example, unit 42 reads the card ID from the game card (S1204), and then determines whether the card ID can be used by referring to the suspension information stored in a predetermined table (S1205). As a result, if it is determined that the game card is usable, the process continues with the assumption that playing using the game card is permitted, and the processing related to the game is executed (S1206). On the other hand, if it is determined that the game card is unusable, the game using the game card is considered restricted, processing is interrupted, and error handling is performed (S1207). Error handling may involve, for example, notifying the error on unit 42, or notifying the user's management application 22, the original owner of the game card, of the occurrence of the error via the operator-side management device 4.

[0174] Similarly, when a settlement process is performed, the settlement device 44 reads the card ID from the game card (S1208), and then determines whether the card ID is usable by referring to the suspension information stored in a predetermined table (S1209). As a result, if it is determined that the game card is usable, the process continues with permission to execute settlement processing based on the game card, and the settlement-related processing is executed (S1210). On the other hand, if it is determined that the game card is unusable, the execution of settlement processing based on the game card is restricted, the process is interrupted, and error processing is performed (S1211). Error processing may include, for example, notifying the user of the game card's original owner via the settlement device 44 or notifying the user of the error via the operator-side management device 4.

[0175] In the example of processing described above, Unit 42 and the settlement device 44 are made to hold the suspension information, and Unit 42 and the settlement device 44 determine whether the game card can be used. However, regardless of this, when Unit 42 or the settlement device 44 reads the card ID from the game card, it may also query the operator-side management device 4 about the usability of the game card corresponding to that card ID. In response to the query from Unit 42 or the settlement device 44, the operator-side management device 4 refers to the information storage unit 201 to determine whether the game card can be used and returns the determination result to Unit 42 or the settlement device 44. Depending on the determination result, Unit 42 or the settlement device 44 may continue processing or execute error handling.

[0176] In this example, if a user loses their game card, they can easily prevent its fraudulent use by simply deactivating it through the management app 22.

[0177] <Example of managing charging methods with flags> When charging the card balance to a game card using the charging machine 41, in addition to the charge amount, a flag indicating whether the charge is based on cash payment or cashless payment may be recorded on the game card. As a result, when the settlement device 44 reads a game card, it can refer to the flag recorded on the game card to determine whether the remaining balance on the game card was charged via cashless payment or cash payment. If the balance is due to cashless payment, the device may then query the operator's management device 4 for the charge ID and proceed with the settlement process.

[0178] This allows, for example, if cash settlement of the card balance is to be disabled, the charging machine 41 can suppress the settlement process of the balance card based on cash payment simply by making a determination based on the flags recorded on the game card.

[0179] <Example 1 of preventing fraudulent settlements> In cases where the card balance is recorded on a game card, fraud may be detected by determining whether the game card is forged or whether the card balance recorded on the game card has been fraudulently charged. In this example, when the settlement device 44 receives a settlement request from the user for the card balance recorded on the game card, it reads the card ID from the game card and queries the operator-side management device 4 for the charge ID and charge amount associated with the card ID. The settlement device 44 also obtains information regarding the card balance used by the user for gameplay from the in-hall management device that manages the user's gameplay. Furthermore, the in-hall management device constitutes part of the gaming service provision system 12 and works in cooperation with unit 42 and gaming machine 43 to manage user gaming information. Specifically, each time a user plays using a gaming card, the device acquires and manages the card ID of the gaming card and information related to the change in the quantity of gaming media due to the game, thereby allowing the remaining balance of the card used for gaming to be identified for each user. Notwithstanding this example, the in-hall management device may also be performed by the operator-side management device 4.

[0180] The settlement device 44 determines the validity of a settlement request based on the charge amount obtained from the operator's management device 4 and the card balance used by the user for gaming, obtained from the hall management device. Specifically, if the amount obtained by subtracting the card balance used by the user for gaming from the charge amount does not match the card balance recorded on the gaming card, the settlement request is rejected as fraudulent. In this case, the settlement device 44 may call a staff member or notify a staff member or manager. On the other hand, if they match, the settlement request is considered valid and the settlement process continues. This allows for the detection and avoidance of fraudulent settlement requests, even if the game card is forged or the balance recorded on the game card has been fraudulently charged.

[0181] Alternatively, the decision on whether or not to process the settlement may be made by the operator-side management device 4 instead of the settlement device 44. In this case, the settlement device 44 transmits the card ID and card balance of the game card to be settled to the operator-side management device 4. The operator-side management device 4 also obtains information regarding the card balance used by the user for gameplay from the in-hall management device. The operator-side management device 4 then determines whether or not to process the settlement request based on the charged amount and the card balance used by the user for gameplay.

[0182] <Example 2 of preventing fraudulent settlements> In the embodiment described above, the payment processing device 3 executes a return process and a new purchase process in response to a settlement process. However, if the same user requests settlement multiple times in a short period of time, or if a return process is executed based on a settlement request, the new settlement request may be deemed fraudulent, the settlement request from the user may be rejected, and the provision of payment services to the user may be suspended. In this case, information regarding the number of settlement requests and settlement processes, and the date and time of each, may be managed for each user. If multiple settlement requests are received or multiple settlement processes are executed from the same user in a short period of time, such as on the same day, a warning message may be displayed on the settlement device 44 or the user terminal 2.

[0183] In the embodiments of the present invention described above, the user terminal 2 and the charging machine 41 displayed the information necessary for the transaction encoded into a two-dimensional code as appropriate. However, regardless of this, the information necessary for the transaction may be converted into a one-dimensional code such as a barcode or a mark, as long as it can be recognizably transmitted to other terminals, etc. Alternatively, the information may be transmitted using short-range wireless communication such as NFC communication.

[0184] <Payment can be made at affiliated stores> In the embodiment described above, the management system 1 is built and operated in a specific amusement parlor, but it may also be built and operated in multiple amusement parlors (affiliated stores). Specifically, for example, if it is a corporation (operator) that operates multiple amusement parlors, a gaming service provision system 12 is configured in each amusement parlor, and the management system 1 is configured so that the multiple gaming service provision systems 12 communicate with the payment service provision system 11 via the communication network NW1. In such a management system 1, settlement is possible on the same day, even if it is not at the amusement parlor where the gaming card was initially issued. More specifically, if there are three affiliated stores, A (Store A), B (Store B), and C (Store C), a game card is initially issued to the user at Store A, and after the balance is charged, the user can move to Store B and settle the balance on the game card there. In this case, the settlement at Store B is limited to the same day that the balance was charged at Store A. This allows settlement at any of the affiliated stores, which is expected to improve convenience for users and create opportunities for customers to visit the stores.

[0185] Furthermore, the above embodiments of the present invention can be applied to other embodiments, in whole or in part, through appropriate design, as long as no inconsistencies arise in function or processing. Furthermore, in order to perform the processing necessary for implementing the present invention, the software resources provided by each of the above-mentioned devices and terminals can be distributed and held across multiple devices, or consolidated into a predetermined device. [Explanation of Symbols]

[0186] 1: Management System 11: Payment service provision system 12: Gaming service provision system 2: User terminal 201: Information storage section 202: Reading section 203: Input / output section 204: Communications Department 21: Payment app 211: Information storage section 212: Purchase Processing Department 213: First ID Issuance Department 214: Communication Processing Unit 22: Management app 221: Information storage section 222: Second ID Issuance Department 223: Encoding Processing Unit 224: Information acquisition department 225: Communication Processing Unit 3: Payment Processing Unit 301: Information storage section 302: Purchase Processing Department 303: ID Issuance Department 304: Returns Processing Department 305: New Purchase Processing Section 306: Point Issuance Department 307: Point Cancellation Section 308: Communication Processing Unit 4: Operator-side management device 401: Information storage section 402: Ticket type issuance department 403: ID Issuance Department 404: Charging section 405: Authentication Processing Unit 406: Settlement Processing Unit 407: Communication Processing Unit 41: Charging machine 411: Information storage section 412: Read Processing Unit 413: Read / Write Processing Unit 414: ID Issuance Department 415: Encoding Processing Unit 416: Charging section 417: Input / output section 418: Communication Processing Unit 42: Unit 43: Gaming machine 44:Payment device 441: Information storage section 442: Read Processing Unit 443: Read / Write Processing Unit 444: Encoding Processing Unit 445: Settlement Processing Unit 446: Input / output section 447: Communication Processing Unit NW1: Communication Network NW2: Communication Network

Claims

1. A method of purchasing a type of ticket in which a user purchases a first type of ticket linked to information of a second value from a first value used in a designated payment service, In a payment processing device that provides the payment service to the user, a purchase information receiving means receives purchase identification information that identifies the purchase process and information related to the purchase amount in response to the execution of the purchase process for the first type of ticket, A charging means that performs a charge of a third value to be used for playing games based on the first type of ticket purchased by the user, Equipped with, The settlement processing device is further characterized by comprising: a first settlement processing means that requests the settlement processing device to perform a return process for the first type of ticket corresponding to the purchase identification information, and a first settlement processing means that requests the settlement processing device to perform a new purchase process for a second type of ticket different from the first type of ticket, using a quantity obtained by subtracting the amount of first value equivalent to the remaining balance of the third value after the user has played the game from the quantity of first value used to purchase the first type of ticket, Management device.

2. A ticket type purchase information storage means stores ticket type purchase information that associates the purchase identification information corresponding to the purchase of the first ticket type with the quantity of the second value, A second settlement processing means that performs an update process to update the quantity of the second value to the quantity obtained by subtracting the quantity of the third value remaining after the user has played the game from the quantity of the third value that has been charged, A return processing request eligibility determination means that determines whether or not to request the execution of the return processing based on predetermined conditions that have been registered in advance, Equipped with, The update process is executed by the second settlement process means when the return process execution request feasibility determination means determines that the return process cannot be executed. The control device according to claim 1.

Images