Control method, computer program used therein, and linkage system, as well as service system incorporated in the linkage system, control method used therein, and computer program

Abstract

To provide a control method capable of reducing the time and effort required by a user for multiple payments. [Solution] The control method causes a payment server 20 of a payment system 2, which functions as a linking system for linking an arcade system 1 for providing games via a game machine 12 with a payment system 2 so that the price for games is settled, to execute a procedure for establishing a linking relationship (session) for settling the price for games between the arcade system 1 and the payment system 2, and a procedure for having the payment system 2 settle the price for games so that multiple payments are allowed in response to a payment request from the arcade system 1 when the linking relationship is established.

Description

[Technical field]

[0001] The present invention relates to a control method and the like applied to a computer incorporated in a linking system for linking a service system for providing a specified service with a payment system so that the fee for the service is paid. [Background technology]

[0002] 2. Description of the Related Art There is known a linking system for linking a service system for providing a predetermined service with a payment system so that the price of the service is paid (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 5496398 Summary of the Invention [Problem to be solved by the invention]

[0004] In the field of payment including the system of Patent Document 1, there is a need for multiple consecutive payments. For example, in prize games such as so-called crane games, a strategy may be used in which the position of a prize to be acquired in one play is changed, and the prize is actually acquired in the second and third plays. Even without a strategy, there are many cases where players play consecutively, taking on the second and third plays based on the feeling of the previous play. For this reason, there is a particularly high need for multiple consecutive payments when the payment is made for playing a prize game.

[0005] Therefore, an object of the present invention is to provide a control method etc. that can reduce the time and effort required by a user for multiple payments. [Means for solving the problem]

[0006] The control method of the present invention involves having a computer incorporated in an integration system for integrating a service system for providing a specified service with a payment system so that the fee for the specified service is settled, execute a first relationship setting procedure for establishing an integration relationship between the service system and the payment system for settling the fee for the specified service, and a fee settlement procedure for causing the payment system to settle the fee for the specified service so that multiple payments are allowed in response to a payment request from the service system when the integration relationship is established.

[0007] The computer program of the present invention is configured to cause a computer incorporated in an integration system for linking a service system for providing a specified service with a payment system so that the fee for the specified service is settled, to function as a first relationship setting means for establishing an integration relationship between the service system and the payment system for settling the fee for the specified service, and as a fee settlement means for settling the fee for the specified service to the payment system so that multiple payments are allowed in response to a payment request from the service system when the integration relationship is established.

[0008] The collaboration system of the present invention is an collaboration system for linking a service system for providing a specified service with a payment system so that the fee for the specified service is settled, and comprises a first relationship setting means for establishing a collaboration relationship between the service system and the payment system for settling the fee for the specified service, and a fee settlement means for causing the payment system to settle the fee for the specified service so that multiple payments are allowed in response to a payment request from the service system when the collaboration relationship is established.

[0009] On the other hand, a control method applicable to the service system of the present invention comprises having a computer incorporated in an integration system for integrating a service system for providing a specified service with a payment system so that the fee for the specified service is settled, the computer executing a second relationship setting procedure for establishing an integration relationship with the payment system for settling the fee for the specified service, and a payment request procedure for requesting the payment system to settle the fee for the specified service so that multiple payments are allowed in accordance with instructions from a user when the integration relationship is established.

[0010] In addition, a computer program applicable to the service system of the present invention is configured to cause a computer incorporated in a service system in an integration system for linking a service system for providing a specified service with a payment system so that the fee for the specified service is settled, to function as a second relationship setting means for establishing an integration relationship with the payment system for settling the fee for the specified service, and a payment request means for requesting the payment system to settle the fee for the specified service so that multiple payments are allowed in accordance with instructions from a user when the integration relationship is established.

[0011] Furthermore, the service system of the present invention is an interconnection system for interconnecting a service system for providing a specified service with a payment system so that the fee for the specified service is paid, and is equipped with a second relationship setting means for establishing an interconnection relationship with the payment system for paying the fee for the specified service, and a payment request means for requesting the payment system to pay the fee for the specified service so that multiple payments are allowed in accordance with instructions from a user when the interconnection relationship is established. [Brief description of the drawings]

[0012] [Figure 1]1 is a diagram showing an example of a configuration of a network system in which a linkage system according to an embodiment of the present invention is incorporated [Diagram 2] FIG. 4 is an explanatory diagram for explaining an outline of a linkage procedure in a first linkage form. [Diagram 3] 11 is a flowchart showing an example of a procedure of a target identification process. [Figure 4] 10 is a flowchart showing an example of a procedure of an authentication preparation process. [Diagram 5] 11 is a flowchart showing an example of a procedure of an authentication process. [Figure 6] 11 is a flowchart showing an example of a procedure of a first linked payment process. [Figure 7] 11 is a flowchart showing an example of a procedure for a linkage cancellation process. [Figure 8] FIG. 11 is an explanatory diagram for explaining an outline of a linkage procedure in a second linkage mode. [Figure 9] 10 is a flowchart showing an example of a procedure of a pairing process. [Figure 10] 10 is a flowchart showing an example of a procedure for application cooperation processing. [Figure 11] 10 is a flowchart showing an example of a procedure of a second linked payment process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] (Overview of the Collaborative System) An outline of a linkage system according to an embodiment of the present invention will be described with reference to FIG. 1. FIG. 1 is a diagram showing an example of the configuration of a network system in which a linkage system according to an embodiment of the present invention is incorporated. As shown in FIG. 1, this embodiment shows a case where the linkage system is applied to linkage between an arcade system 1 as an example of a service system and a payment system 2. The linkage system may also be applied so that the payment system 2 is paid for a service that the arcade system 1 provides directly to a user, but the example of FIG. 1 shows a case where the linkage system is applied so that the payment system is paid for a service that the arcade system 1 provides indirectly via a service terminal 11. In this case, the arcade system 1 is linked to the payment system 2 so that at least one of the fees for the services provided via various service terminals 11 is paid for.

[0014] Specifically, arcade system 1 is configured as a client-server system including arcade server 10 and service terminal 11 connected to arcade server 10 as a client device. Arcade server 10 may be configured as a single physical server device, or as a logical server combining multiple physical server devices. Furthermore, arcade server 10 may be configured as a cloud server combining multiple server devices connected to a WAN such as the Internet.

[0015] The service terminal 11 may include any suitable terminal that provides various services, but in the example of FIG. 1, it includes a game machine 12, a vending machine 13, and a user terminal device 15. The game machine 12 may be configured as appropriate, and may include any suitable game device, such as a user terminal device that provides a so-called mobile game, but in the example of FIG. 1, it is configured as an arcade game machine that provides various services associated with the game to the user in exchange for the user's payment of a predetermined fee. This type of game machine is sometimes called an arcade game machine. The predetermined service provided by the game machine 12 includes at least a service that allows the user to play the game. In addition to the service that allows the user to play the game, the game machine 12 may provide a service that sells various contents, such as items used in the game, for a fee, etc.

[0016] The type of game played on the game machine 12 is not particularly limited. Various games may be playable on the game machine 12, but in the example of FIG. 1, the game machine 12 is configured as a prize game machine that provides a prize game (a game for winning prizes). A prize game is a type of game in which a prize is awarded when a user operates an operation object via an input device to bring a state of a game object into a predetermined state. The operation object may be configured as appropriate, but in the example of FIG. 1, it is configured as a crane unit, which is a type of device for capturing (obtaining) a physical game object. The crane unit has multiple arms (usually two) for pinching the game object, and is configured to grab (capture) the game object by pinching it with these arms. Then, when the game object is captured by the crane unit and transported to an opening connected to an outlet for discharging the game object to the outside (when it reaches a predetermined state), a prize is awarded to the user. This type of prize game is often called a crane game.

[0017] The vending machine 13 is a device that sells various products such as beverages for a fee. In the vending machine 13, the sale of various products is provided as a predetermined service, for example. The user terminal device 15 is a general-purpose information and communication terminal provided for personal use by the user. For example, a smartphone, a tablet, a PC, etc. may be appropriately used as the user terminal device 15. The user terminal device 15 may provide an appropriate predetermined service, such as the purchase of various contents such as items to be used in a game. Alternatively, the user terminal device 15 may not function as the service terminal 11, but may simply function as an auxiliary terminal that provides a game-related service.

[0018] In the arcade system 1, the arcade server 10, the game machine 12, the vending machine 13, and the user terminal device 15 cooperate with each other appropriately to provide various client services to the user. For example, for the vending machine 13, a service may be provided in which the arcade server 10 acquires the user's purchase record and gives the user points according to the acquired record. Similarly, for the game machine 12, a service may be provided in which the user's play data, such as points according to the record, is stored on the arcade server 10 and the stored play data is provided to the game machine 12. Management of the play data including the points may be performed via the user terminal device 15. In other words, the user terminal device 15 may function as an ID for identifying each user, and transmission and reception of the play data may be performed between the user terminal device 15 and the arcade server 10. That is, the user terminal device 15 may be provided with a game-related service for managing such play data of the game machine 12. The game-related service may include a service for selling game-related content to the user.

[0019] Arcade server 10 is provided with an authentication processing unit 101, a service processing unit 102, and a payment linking unit 103 as logical devices realized by a combination of the computer hardware and a specific server program PG1. In addition to these devices, various logical devices are appropriately provided in arcade server 10, but these are not shown in the drawings.

[0020] The authentication processing unit 101 is responsible for various processes required to authenticate users who use the arcade system 1. The authentication processing unit 101 authenticates users using a user ID and secret information such as a password that is known only to the user. The user ID is an example of identification information for identifying a user in the arcade system 1, and is uniquely valid in the arcade system 1.

[0021] The service processing unit 102 is responsible for processing required to provide various services to authenticated users in cooperation with the service terminal 11. For example, the processing of the service processing unit 102 realizes services such as a service for providing the game machine 12 with various contents required for playing games on the game machine 12, a service for storing or providing user play data, and game-related services.

[0022] The payment linking unit 103 is responsible for processing required to have the payment system 2 settle the fees for various services provided by the service terminal 11. For example, the payment linking unit 103 realizes processing to have the payment system settle the fees for playing the game machine 12, the fees for purchasing products from the vending machine 13, or the fees for purchasing content related to games via the user terminal device 15. The processing handled by the payment linking unit 103 also includes processing to identify the services (products provided by the vending machine 13, playing games provided by the game machine 12, etc.) to be settled by the payment system, and to link the service terminal 11 with the user terminal device 15.

[0023] The authentication processing unit 101, the service processing unit 102, and the payment linking unit 103 do not necessarily need to be provided on the same physical server device. As described above, the arcade server 10 may be configured as a logical server that combines multiple physical server devices. Therefore, the authentication processing unit 101, the service processing unit 102, and the payment linking unit 103 may be realized by different physical server devices. Furthermore, the authentication processing unit 101, the service processing unit 102, or the payment linking unit 103 may be further divided and provided on multiple physical server devices depending on the type of processing. In short, each of the authentication processing unit 101, the service processing unit 102, and the payment linking unit 103 may be configured as a logical device realized by a combination of computer hardware of a single or multiple physical server devices and the server program PG1 as software.

[0024] The arcade system 1 is provided with a user database DB11, a content database DB12, a case management database DB13, and a linkage management database DB14 as databases to be referenced by the arcade server 10. The user database DB11 is a database that stores various data related to users in association with user IDs. For example, user data that records attributes such as personal information of users, play data that records game play by users, etc. may be recorded in the user database DB11.

[0025] The content database DB12 is a database that stores various contents provided in the game. The cabinet management database DB13 is a database that stores information on each service terminal 11 connected to the arcade system 1. For example, cabinet data, etc., in which information such as information on the service provided by each service terminal 11, information on the location (e.g., facility such as a store, or address, etc.), or information on an address on a network is recorded in association with a cabinet ID that identifies each service terminal 11, may be recorded in the cabinet management database DB13.

[0026] The cooperation management database DB14 is a database that stores data necessary for cooperation with the payment system 2. Examples of data recorded in the cooperation management database DB14 will be described later in the overview of the cooperation procedure.

[0027] On the other hand, the payment system 2, like the arcade system 1, is configured as a client-server system including a payment server 20 and a user terminal device 23 as a client device. The payment server 20 may be configured as a single physical server device, or may be configured as a logical server combining multiple physical server devices. Furthermore, the payment server 20 may be configured as a cloud server combining multiple server devices on a WAN such as the Internet.

[0028] Various computer devices may be appropriately used as the client device, but the example of FIG. 1 shows a user terminal device 23. The user terminal device 23 is a general-purpose information and communication terminal provided for personal use by the user, similar to the user terminal device 15. For example, a smartphone, a tablet, a PC, or the like may be appropriately used as the user terminal device 23. In the example of FIG. 1, the user terminal device 23 is configured as a smartphone, and includes a control unit 23U configured as a computer unit including a microprocessor and an internal storage device required for its operation, and a program PG3 for making the control unit 23U function as various logical devices. The program PG3 includes appropriate applications (hereinafter, sometimes referred to as apps) for making the user terminal device 23 perform various functions. The user terminal device 23 may be provided with various input devices or output devices connected to the control unit 23U, but the example of FIG. 1 shows a touch panel TP, a communication device CU, a monitor MO, and a camera CA. Each of the touch panel TP, the communication device CU, the monitor MO, and the camera CA is general-purpose hardware provided in an information and communication terminal such as a smartphone. The communication unit CU may include a transmission / reception function conforming to an appropriate short-range wireless communication standard.

[0029] The user terminal device 23 does not need to be a client device different from the user terminal device 15 used in the arcade system 1. The same information and communication terminal device may be used as the user terminal devices 15, 23 in each of the arcade system 1 and the payment system 2. The user terminal devices 15, 23 perform various functions through various applications. As an example, the following describes a case in which the same information and communication terminal device functions as the user terminal device 15 when performing a function based on an application for the arcade system 1 (hereinafter, may be referred to as a service application) and as the user terminal device 23 when performing a function based on an application for executing a payment using the payment system 2 (hereinafter, may be referred to as a payment application).

[0030] The payment server 20 is provided with an authentication processing unit 201 and a payment processing unit 202 as logical devices realized by a combination of the computer hardware and a predetermined server program PG2. In addition to these devices, various logical devices are appropriately provided in the payment server 20, but these are not shown in the figures.

[0031] The authentication processing unit 201 is responsible for various processes required to authenticate a user who uses the payment system 2. The authentication processing unit 201 authenticates a user using a user ID and secret information such as a password known only to the user. The user ID is an example of identification information for identifying a user in the payment system 2, and is uniquely valid in the payment system 2. The user ID in the arcade system 1 and the user ID in the payment system 2 are different from each other even if they are associated with the same user. There is no commonality or compatibility between the user IDs in both systems 1 and 2. Note that the arcade system 1 and the payment system 2 may be operated by a common operator, but the following describes, as an example, a case where the arcade system 1 and the payment system 2 are operated by different operators, in other words, a case where the arcade system 1 and the payment system 2 are constructed as independent systems (systems that provide unique services to the service terminal 11, etc.) and are linked to each other.

[0032] The payment processing unit 202 manages the user's electronic currency account and is responsible for processing to consume or increase the electronic currency in response to a request from the user terminal device 23. The electronic currency may include various currencies, such as electronic money (prepaid type) or various types of cryptographic (virtual) currencies (currencies managed by block chain technology) represented by Bitcoin. Instead of electronic currency, appropriate electronic value such as various points may be managed in the account. In addition, payment (including exchange into electronic currency) may be performed by credit card, debit card, or postpaid type electronic money. Various payments including payments by credit card or the like may be configured to be performed using a payment service provided by an external business operator different from the operator (business operator) that operates the payment system 2. For this reason, the processing handled by the payment processing unit 202 may include processing necessary for executing various payments. The payment processing unit 202 is also responsible for processing to settle the price of the service provided by the service terminal 11 in cooperation with the payment linkage unit 103 of the arcade system 1 and the user terminal device 23 as appropriate.

[0033] In the payment system 2, the authentication processing unit 201 and the payment processing unit 202 do not necessarily need to be provided on the same physical server device. In other words, similar to the example in the arcade system 1, each of the authentication processing unit 201 and the payment processing unit 202 may be configured as a logical device realized by a combination of computer hardware of a single or multiple physical server devices and the server program PG2 as software.

[0034] The payment system 2 is provided with a user database DB21, an account management database DB22, and a linkage management database DB23 as databases to be referenced by the payment server 20. The user database DB21 is a database that stores various data related to users in association with user IDs. For example, user data that records attributes such as personal information of users may be recorded in the user database DB21.

[0035] The account management database DB22 is a database that stores data that records the amount of electronic currency held by a user (balance) in association with an account ID (account). When a user holds an electronic currency account, data that associates the user's user ID with the account ID is recorded, for example, in the user database DB21. Therefore, if the user ID of a user is known, it is possible to identify the user's account ID and access the user's account.

[0036] The linkage management database DB23 is a database that stores data necessary for linkage with the arcade system 1. An example of data recorded in the linkage management database DB23 will be described later in the overview of the linkage procedure together with an example of the linkage management database DB14.

[0037] (Outline of collaboration) Next, the link between the arcade system 1 and the payment system 2 will be described. As described above, the payment system 2 manages user IDs in association with accounts. On the other hand, in the arcade system 1, various achievements (points, etc.) of each user may or may not be managed by a unique user ID. For example, the arcade system 1 may provide services without identifying users at least in some of the service terminals (e.g., vending machines, etc.; the same applies to the game machine 12 when management of points, etc. is not required), and in that case, management of user IDs may also be omitted. In this case, payment is possible only with the account (user ID) of the payment system 2, but the arcade system 1 and the payment system 2 need to link for payment. This link can be realized by an appropriate procedure, and includes, for example, a case where the link is requested from the arcade system 1 to the payment system 2 via the service terminal 11 that has acquired user information, and a case where the link is requested from the payment system 2 to the arcade system 1 via the user terminal device 23 that has acquired information on the service terminal 11. In the following, the latter case will be referred to as a first linkage form as an example, and the details of the procedure will be described later.

[0038] On the other hand, as described above, the arcade system 1 may also manage various achievements (points, etc.) of each user using a unique user ID. In this case, since the arcade system 1 and the payment system 2 each identify a user using a user ID set independently of each other, in order to use the payment system 2 for payment, it is necessary to identify which user ID of the payment system 2 the user of the arcade system 1 corresponds to. On the other hand, it is troublesome for a user to perform authentication using a user ID and password in both or one of the arcade system 1 and the payment system 2 every time a payment is made. For example, in a prize game, the arrangement of the game objects changes with each play, and there is a high need for continuous play, so that multiple payments may be required in a short period of time. When multiple payments are made in a short period of time (hereinafter, sometimes referred to as continuous payments), the load increases further if authentication, etc. is required for each payment. This is also true in the first cooperation form. In addition, the game machine 12 is available to an unspecified number of users, and is often installed in a facility such as a store where an unspecified number of people visit. Therefore, it is not preferable from the viewpoint of security to have the user input user authentication information of another payment system 2 on the game machine 12.

[0039] Therefore, in this embodiment, the arcade system 1 and the payment system 2 are linked so that consecutive payments are permitted without requiring authentication each time. Below, an overview of the linking procedure (mechanism) for each of the first linking embodiment and a embodiment in which the achievements of the game machine 12 (for example, the amount of points owned that are granted according to achievements) are managed (a game-related service is provided) via a service-related application of the user terminal device 15 (a form in which the arcade system 1 and the payment system 2 each provide a service while identifying the user using a user ID set independently of each other, which may be hereinafter referred to as the second linking embodiment) will be described.

[0040] [First form of collaboration] (Overview of collaboration procedures) Fig. 2 is an explanatory diagram for explaining an outline of the linking procedure in the first linking form. Fig. 2 (A) shows the procedure for identifying the service to be paid for, (B) shows the procedure for authenticating the user who is the payer, and (C) shows the procedure for payment after authentication. Note that in the example of Fig. 2, the game machine 12 is shown as a representative of the service terminals 11, but linking and payment may be performed in a similar procedure when a payment is made for a service of another service terminal 11.

[0041] As shown in (A) of FIG. 2, in the procedure of linkage in the first linkage form, a procedure for identifying a service to be paid for is first executed. Specifically, information for identifying the service to be paid for (hereinafter, sometimes referred to as service information) is provided from the game machine 12 (service terminal 11) to the user terminal device 23. This provision may be realized appropriately. For example, when the game machine 12 has a transmitting function for transmitting information according to a predetermined short-range wireless communication standard and the user terminal device 23 has a receiving function for receiving the information, the provision may be realized by the short-range wireless communication, but as an example, the provision is realized by a code CD. The code CD is generated in accordance with a predetermined standard so as to include the service information. An appropriate code may be used as the code CD, but in the example of FIG. 2, a two-dimensional code is provided on the game machine 12. The code CD may be appropriately provided on the game machine 12, and may be provided via a display device that displays the code CD when a display device is provided on the game machine 12, but as an example, the code CD is provided by attaching a sticker that displays the code CD. In this case, the user terminal device 23 acquires the service information from the game machine 12 via a camera CA as a reader for reading the service information of the code CD. In this example, the game machine 12 (or a code CD sticker provided thereon) functions as the information providing means of the present invention.

[0042] When the user terminal device 23 acquires the service information via the code CD, it transmits the acquired service information to the payment server 20 of the payment system 2 (F1). This transmission can be performed appropriately, but as an example, it is performed by the payment application after the code CD is read via the camera CA.

[0043] When the payment server 20 acquires the service information from the user terminal device 23, it transmits the service information to inquire of the arcade server 10 of the arcade system 1 whether or not cooperation for payment is possible (F2). By this inquiry, the arcade server 10 identifies the service to be paid for and the game machine 12 that provides it.

[0044] When the service for which payment is to be made is specified, an authentication procedure is started. As shown in FIG. 2B, this procedure includes steps F3 to F9 as an example. Also, steps F3 to F9 are divided into steps (F3 to F4) for preparing for authentication and steps (F5 to F9) for actually performing authentication as an example. Specifically, when the arcade server 10 acquires service information via an inquiry (F2) from the payment server 20, it transmits authentication information (e.g., information unique for each authentication, such as a one-time password) for authenticating whether or not payment can be made to the game machine 12 corresponding to the service information (F3).

[0045] When the game machine 12 acquires the authentication information from the arcade server 10, it provides the authentication information to the user terminal device 23 (F4). This provision can be performed appropriately, but as an example, it is performed by displaying the authentication information on a display device provided in the game machine 12. Then, the user of the user terminal device 23 inputs the authentication information displayed on the display device into the payment application. The game machine 12 ends the display of the authentication information when a predetermined ending condition is satisfied, such as the passage of a certain period of time.

[0046] On the other hand, when the payment application acquires the authentication information through manual input by the user who has seen the display of the authentication information, or through appropriate optical reading by a camera or the like, it transmits the authentication information to the payment server 20 (payment system 2) (F5). When the payment server 20 acquires the authentication information, it transmits the authentication information to the arcade server 10 (arcade system 1) to check whether the authentication information is correct, in other words, whether the authentication information is the authentication information issued for the current payment (F6). When the arcade server 10 acquires the authentication information, it judges whether the authentication information is correct and transmits the result to the payment server 20 (F7). When the payment server 20 acquires the judgment result, if the authentication information is correct, it issues a session ID and transmits it to the arcade server 10 (arcade system 1), thereby establishing a session (linked relationship) between both systems 1 and 2 (F8). The session ID is ID information unique to each session to identify each session (linked relationship). Therefore, even if the link is between the same game machine 12 and the user terminal device 23, a different session ID is issued once the session is released. When the session is established, the arcade server 10 (arcade system 1) notifies the result to the game machine 12 (F9). In this example, the service information functions as the predetermined information of the present invention.

[0047] If the authentication information is incorrect, the payment server 20 notifies the user terminal device 23 of the result to encourage the user to start over from the procedure of obtaining the service information again. The arcade server 10 similarly notifies the game machine 12 of the result of session (linkage) not being established in F9 instead of the result of linkage establishment. Also, in the example of FIG. 2, the session ID is issued by the payment system 2, but it may be issued by the arcade system 1 and shared with the payment system 2. Similarly, in the example of FIG. 2, authentication is performed by a procedure of obtaining authentication information issued by the arcade system 1 via the user terminal device 23 (executing two-step authentication), but user authentication may be realized appropriately, and two-step authentication may be omitted.

[0048] As shown in (C) of Fig. 2, when authentication is successful and an association is established, a session (association) is maintained between the arcade server 10 (arcade system 1) and the payment server 20 (payment system 2) until a predetermined release condition is satisfied. Specifically, when an association is established, the arcade system 1 generates first session data D1 in which the issued session ID and a cabinet ID for identifying the game machine 12 that is the object of payment (a unique ID for each game machine 12 or each service terminal 11 for identifying each service terminal 11) are recorded in association with each other, and the first session data D1 is stored in a state that can be referenced by the arcade server 10. For example, the first session data D1 may be recorded in the association management database DB14 (see Fig. 1).

[0049] Similarly, in the payment system 2, second session data D2 is generated in which the issued session ID and a user ID for identifying the user of the settler (which may be account information of the payment target associated with the user ID) are recorded in association with each other, and is stored in a state that can be referenced by the payment server 20. For example, the second session data D2 may be recorded in the linkage management database DB23 (see FIG. 1).

[0050] The settlement procedure when the session is maintained includes, for example, the procedures F11 to F16. Specifically, when a user issues an instruction (operation) to request the game machine 12 to play, the game machine 12 transmits a settlement request corresponding to the price of the play to the arcade server 10 (arcade system 1) (F11).

[0051] When the arcade server 10 acquires the payment request, it transmits the payment request to the payment server 20 (payment system 2) (F12). When the payment request is acquired, the payment server 20 executes the payment corresponding to the payment request (F13). In other words, in a situation where the session is maintained, procedures such as authentication normally required at the time of payment, an opportunity to confirm with the user whether or not to approve the payment, or the construction of a session are omitted, and the payment system 2 executes the payment directly based on the payment request from the arcade system 1. After executing the payment, the payment server 20 notifies the arcade server 10 (arcade system 1) and the user terminal device 23 of the payment result (F14). Note that the opportunity to confirm with the user whether or not to approve the payment is provided only at the time of the first payment, and may be omitted at the time of the second or subsequent payments. Alternatively, this opportunity may be provided each time a payment is made.

[0052] When the arcade server 10 acquires the payment result, it notifies the game machine 12 of the result (F15). When the game machine 12 acquires the payment result, if the payment is unsuccessful, it notifies the user of that fact, whereas if the payment is successful, it permits the play requested by the user (F16). That is, the game machine 12 transmits a payment request to the payment system 2 via the arcade system 1 in response to a play request by the user, and actually provides the requested play when the payment is executed in the payment system 2. Then, the steps of F11 to F16 are repeatedly executed every time a play request is instructed to the game machine 12. As a result, in a situation where the session is maintained, authentication and the like are omitted, and continuous payment is realized.

[0053] (Processing of linked systems) Next, the processing of the linked system in the first linked form will be described with reference to Figs. 3 to 7. Fig. 3 is a flow chart showing an example of the procedure of the target identification processing. The target identification processing is processing for identifying a service that is the object of payment. As an example, the target identification processing is realized by cooperation of the game machine 12, the payment linking unit 103 of the arcade server 10, the authentication processing unit 201 of the payment server 20, and the user terminal device 23. Note that in Fig. 3, the processing (procedure) executed mainly by the payment linking unit 103 of the arcade server 10 is shown as the arcade server 10, and the processing (procedure) executed mainly by the authentication processing unit 201 of the payment server 20 is shown as the payment server 20.

[0054] When service information is acquired from the code CD of the game machine 12 via the camera CA activated by the payment application, the user terminal device 23 (payment application) starts the target identification process of Fig. 3, and first transmits the acquired service information to the payment server 20 (step S101). The service information may appropriately include various information related to the service of the game machine 12, and includes, for example, information for identifying the target game machine 12 (for example, information on the housing ID). Then, after this transmission, the user terminal device 23 ends the current target identification process.

[0055] On the other hand, when service information is transmitted from the user terminal device 23, the payment server 20 starts the target identification process of Fig. 3 and first acquires the service information (step S201). Next, the payment system transmits the service information acquired in step S201 to the arcade server 10 (step S202). After this transmission, the payment server 20 ends the current target identification process.

[0056] When the service information is transmitted from the settlement server 20, the arcade server 10 starts the target identification process of FIG. 3 and first acquires the service information (step S301). Next, the arcade server 10 identifies the target game machine 12 of the service information acquired in step S301 (step S302). For example, the arcade server 10 identifies the target game machine 12 (the address of the destination of information, etc.) based on the cabinet ID included in the service information while referring to the cabinet data in the cabinet management database DB13. Then, the arcade server 10 ends this target identification process after this identification. This realizes the identification of the game machine 12 (service terminal 11) for which the payment should be made in the settlement system 2. Specifically, the steps (F1 to F2) in FIG. 2A are realized.

[0057] The authentication preparation process is a process for executing preparation for authentication for settling the price of the service to be paid for by payment system 2. As an example, the authentication preparation process is realized by cooperation between authentication processing unit 101 of arcade server 10, authentication processing unit 201 of payment server 20, and user terminal device 23. Note that in Fig. 4, the process (procedure) executed mainly by authentication processing unit 101 of arcade server 10 is shown as arcade server 10, and the process (procedure) executed mainly by authentication processing unit 201 of payment server 20 is shown as payment server 20, respectively.

[0058] When the service to be paid for is identified through the target identification process of Fig. 3, the arcade server 10 starts the authentication preparation process of Fig. 4 and first generates authentication information (time-limited information such as a one-time password) (step S303). The arcade server 10 then transmits the authentication information to the game machine 12 identified in the target identification process (step S302) of Fig. 3 (step S304). After this transmission, the arcade server 10 ends the current authentication preparation process.

[0059] On the other hand, when authentication information is transmitted from the arcade server 10, the game machine 12 starts the authentication preparation process of Fig. 4 and first acquires the authentication information (step S401). Next, the game machine 12 displays the acquired authentication information on the display device so that the user of the user terminal device 23 can confirm it (step S402). Then, after this display, the game machine 12 ends this authentication preparation process. As a result, authentication information for paying the consideration in the payment system 2 is provided to the user via the game machine 12. Specifically, the steps F3 to F4 in the example of Fig. 2(B), that is, the steps for executing preparation for authentication, are realized.

[0060] Fig. 5 is a flow chart showing an example of the procedure of authentication processing. The authentication processing is processing for authenticating a payer (user) who pays for a service that is the subject of payment. As an example, the authentication processing is realized by cooperation between the game machine 12, the authentication processing unit 101 of the arcade server 10, the authentication processing unit 201 of the payment server 20, and the user terminal device 23. Note that in Fig. 5, the processing (procedure) executed mainly by the authentication processing unit 101 of the arcade server 10 is shown as the arcade server 10, and the processing (procedure) executed mainly by the authentication processing unit 201 of the payment system 2 is shown as the payment server 20.

[0061] When the user inputs the authentication information displayed on the game machine 12 and acquires the authentication information, the user terminal device 23 (payment application) starts the authentication process of FIG. 5 and first transmits the acquired authentication information to the payment server 20 (step S501).

[0062] 5 and first acquires the authentication information (step S601). Then, the payment server 20 transmits the authentication information acquired in step S601 to the arcade server 10 (step S602).

[0063] When the arcade server 10 receives the authentication information from the settlement server 20, the arcade server 10 starts the authentication process of Fig. 5 and first acquires the authentication information (step S701). The arcade server 10 then determines whether the authentication information acquired in step S701 is correct (step S702). Specifically, the arcade server 10 determines whether the authentication information matches the authentication information transmitted to the game machine 12 that is the object of the settlement. The arcade server 10 then transmits the determination result to the settlement server 20 and the game machine 12 (step S703).

[0064] Furthermore, the arcade server 10 determines whether the authentication in step S702 was successful (whether the authentication information was correct) (step S704). If the authentication was successful (step S704: Yes), the arcade server 10 waits for a session ID to be sent from the payment server 20 to establish a session with the payment server 20. Then, when the session ID is sent from the payment server 20, the arcade server 10 acquires the session ID and stores it by generating first session data D1 (associating it with the cabinet ID of the game machine 12 that issued the authentication information) (step S705). On the other hand, if the authentication was unsuccessful (the authentication information was incorrect) (step S704: No), the arcade server 10 ends the current authentication process.

[0065] When the result of the authentication is transmitted from the arcade server 10, the settlement server 20 judges whether the authentication is successful or not based on the result of the judgment (step S603). If the authentication is successful (step S603: Yes), the settlement system issues a session ID to establish a session (linked relationship) with the arcade server 10 for settling the price of the game machine 12, and transmits the session ID to the arcade server 10 (step S604), and stores the session ID by generating second session data D2 (associating it with the settler or his account) (step S605). Next, the settlement server 20 transmits the current authentication result to the user terminal device 23 (step S606). After this transmission, the settlement server 20 ends the current authentication process.

[0066] When the authentication result is transmitted from the payment server 20, the user terminal device 23 acquires the result (step S502) and notifies the user by displaying it on a display device or the like (step S503). After this notification, the user terminal device 23 ends the current authentication process.

[0067] On the other hand, when the game machine 12 receives the authentication result from the arcade server 10, the game machine 12 starts the authentication process of FIG. 5 and first acquires the authentication result (step S801). Next, the game machine 12 notifies the user of the authentication result acquired in step S801 by displaying it on a display device or the like (step S802). After this notification, the current authentication process is terminated. As a result, a linkage relationship between the arcade system 1 and the payment system 2 for settling the price of the game machine 12 is established via the authentication information. More specifically, the steps F5 to F9 in the example of FIG. 2B, that is, the steps for actually executing authentication, are realized. After the authentication, a linkage relationship for settling is established between the arcade system 1 and the payment system 2.

[0068] Fig. 6 is a flow chart showing an example of the procedure of the first linked payment process. The first linked payment process is a process for executing successive payments (multiple payments in a short period of time) in a situation where a linked relationship (session) between the arcade server 10 and the payment server 20 is maintained. The first linked payment process is realized, as an example, by cooperation between the game machine 12, the payment linking unit 103 of the arcade server 10, the payment processing unit 202 of the payment server 20, and the user terminal device 23. Note that in Fig. 6, the process (procedure) executed mainly by the payment linking unit 103 of the arcade server 10 is shown as the arcade server 10, and the process (procedure) executed mainly by the payment processing unit 202 of the payment server 20 is shown as the payment server 20.

[0069] When a user instructs the game machine 12 to play a game while a session between the systems 1 and 2 is being maintained, the game machine 12 starts the first linked payment process shown in Fig. 6 and first transmits a payment request to the arcade server 10 (step S1201). This request includes information necessary for payment, such as the amount of the payment.

[0070] When a payment request is transmitted from the game machine 12, the arcade server 10 starts the first linked payment process of FIG. 6, acquires the payment request, and transmits it to the payment server 20 (step S1101). When a payment request is transmitted from the arcade server 10, the payment server 20 starts the first linked payment process of FIG. 6, and first acquires the payment request (step S1001). Next, the payment server 20 executes the payment according to the payment request acquired in step S1001 while referring to the second session data D2 (step S1002). This payment is realized by deducting the balance of the account of the user ID associated with the session ID. Next, the payment server 20 notifies the arcade server 10 and the user terminal device 23 (payment application) of the payment result in step S1002 (step S1003). Then, after this notification, the payment server 20 ends this first linked payment process.

[0071] When the user terminal device 23 (payment application) is notified of the payment result from the payment server 20, it starts the first linked payment process of Fig. 6 and first acquires the payment result (step S901). Next, the user terminal device 23 stores the payment result acquired in step S901 so that the user can check it at any time via the payment application (step S902). Then, after this storage, the user terminal device 23 ends the first linked payment process.

[0072] On the other hand, when the arcade server 10 is notified of the settlement result from the settlement server 20, it acquires the settlement result (step S1102) and notifies the game machine 12 (step S1103). Then, after this notification, the arcade server 10 ends this linked settlement process.

[0073] When the game machine 12 is notified of the payment result from the arcade server 10, it acquires it and determines whether or not the payment was successful based on the payment result (step S1202). If the payment has failed (step S1202: No), the game machine 12 skips the subsequent processing and ends the current first linked payment processing. In this case, the game machine 12 may appropriately notify the user of the result of the payment failure via a display device or the like.

[0074] On the other hand, if the payment is successful (step S1202: Yes), the game machine 12 permits the user to play the game instructed by the user and starts playing (step S1203). After the game starts playing, the game machine 12 ends the current first linked payment process. As a result, authentication and the like are omitted in a situation where a session is established, and the payment system 2 pays for the game in a relatively simple procedure. Generally, the session is released after the payment is completed, and authentication and the like are requested again at the time of the next payment. However, in the example of FIG. 6, the session is not released but maintained even after the payment. In other words, the payment system 2 does not release the session, but maintains it via the second session data D2 and the like. Therefore, the payment system 2 pays for the repeated play on the game machine 12 in a relatively simple procedure. More specifically, the procedures F11 to F16 in the example of FIG. 2C are realized. In the example of Figure 6, the session is maintained by omitting active processing to release the session, but processing to actively maintain the session (e.g., an instruction to maintain the session) may be executed by the payment system 2 or the like.

[0075] FIG. 7 is a flowchart showing an example of the procedure of the linkage cancellation process. The linkage cancellation process is a process for canceling the linkage relationship (session) between the arcade server 10 and the payment server 20. The linkage relationship between the two systems 1 and 2 is maintained until a predetermined cancellation condition is satisfied, for example, and is cancelled when the cancellation condition is satisfied. The cancellation condition may be appropriately satisfied, for example, when a predetermined time has passed since the establishment of the session, when the next payment is not executed within a predetermined time, when a predetermined number of payments have been executed, or when a predetermined location condition such as the user leaving the vicinity of the game machine 12 (for example, the facility where the game machine 12 is installed) is formed, and as an example, the cancellation condition is satisfied when a predetermined cancellation instruction requesting cancellation of the session maintenance is executed by the game machine 12. The example of FIG. 7 shows the procedure of the linkage cancellation process in such a case. In this case, the linkage cancellation process is realized by, for example, cooperation between the game machine 12, the payment linkage unit 103 of the arcade server 10, and the payment processing unit 202 of the payment server 20. In Figure 7, the processing (procedures) mainly performed by the payment linkage unit 103 of the arcade server 10 is shown as arcade server 10, and the processing (procedures) mainly performed by the payment processing unit 202 of the payment server 20 is shown as payment server 20.

[0076] Specifically, when a predetermined cancellation command is input, the game machine 12 starts the link cancellation process of Fig. 7 and first acquires the cancellation command (step S1301). Next, the game machine 12 requests the arcade server 10 to cancel the session (step S1302).

[0077] When a cancellation request is received from the game machine 12, the arcade server 10 starts the link cancellation process of Fig. 7 and first acquires the request (step S1401). Next, the arcade server 10 requests the settlement server 20 to cancel the session based on the request (step S1402). Furthermore, the arcade server 10 cancels the session (linked relationship) with the settlement server 20 based on the cancellation request, and transmits the result to the game machine 12 (step S1403). For example, the session (linked relationship) is cancelled by deleting (discarding) the first session data D1. Then, after notifying the game machine 12, the arcade server 10 ends the current link cancellation process.

[0078] When the result of the cancellation is transmitted from the arcade server 10, the game machine 12 acquires the result and notifies the user by displaying it on a display device or the like (step S1303). After this notification, the game machine 12 also ends the current link cancellation process.

[0079] On the other hand, when the payment server 20 receives a request for cancellation from the arcade server 10, the payment server 20 starts the link cancellation process of FIG. 7 and first acquires the request (step S1501). Next, the payment server 20 cancels the session, that is, the linkage for payment with the arcade server 10, based on the request (step S1502). For example, this cancellation is realized by deleting (discarding) the second session data D2. Then, after canceling the session, the payment server 20 ends the current link cancellation process. This cancels the session between the arcade system 1 and the payment system 2 based on the user's cancellation instruction. In other words, the session is maintained until the user instructs cancellation, and the session is cancelled at the user's discretion.

[0080] As described above, according to the first cooperation form, after the session (cooperation relationship) is established, the payment system 2 settles the game fee so that multiple consecutive (in a short period of time) payments are permitted in response to a payment request from the arcade system 1. In other words, after the session is established, the session is maintained so that multiple payments are permitted. Generally, the establishment of a session often requires the effort of user authentication and the like. At least various information for establishing a session needs to be transmitted and received between the two systems 1 and 2. As a result, it often takes time. For this reason, by maintaining the session so that multiple payments are permitted after the session is established, these procedures can be omitted. As a result, the effort and time required by the user for multiple payments can be reduced, and multiple payments, such as continuous play in a prize game, can be promoted.

[0081] Furthermore, the operator of the arcade system 1 can realize payment via the payment system 2 without having to build a payment system himself. In other words, a similar service can be provided without having a payment system. Furthermore, a payment request (information on the value of the payment object) is provided from the game machine 12, in other words, from the arcade system 1 to the payment system 2. Therefore, the arcade system 1 can determine the value of the payment object by itself. This allows the arcade system 1 to realize various campaigns such as discounts, preferential treatment, and special offers. Specifically, the arcade system 1 can request the payment system 20 to settle the amount remaining after deducting the discount amount from the value due to a discount service such as a coupon.

[0082] Furthermore, when the opportunity for approval to approve the payment of each consideration is omitted while the session is maintained, the approval process for the user is omitted, so that the user's time and effort can be further reduced. Meanwhile, the session is maintained until a release instruction is executed. This allows the user to feel secure about continuous payments. Furthermore, the service to be paid for is specified via a code CD including service information. In this case, it is possible to prevent the service information used for payment from being directly recognized by the user. The game machine 12 is often installed in a facility that can be used by an unspecified number of users. In that case, it is not preferable from the viewpoint of security if the service information is easily recognized by the user. Therefore, when the service information is provided to the user terminal device 23 via the code CD, it is possible to improve security.

[0083] Furthermore, even if the arcade system 1 does not manage user IDs (even if each user is not identified when the service is provided and points, etc., are not awarded), payment can be achieved through the payment service. Game machines 12 (arcade game machines) are often installed in facilities such as stores, and users who visit the facilities are not always users who perform user registration (e.g., regular users), but rather many users who do not perform user registration (e.g., users who are visiting the facility for the first time or users who are playing for the first time). For this reason, if payment is possible without the need for a user ID, it is compatible with games provided by arcade game machines (so-called arcade games). In other words, continuous payment can be achieved for services such as arcade games, which are often provided without the need for a user ID.

[0084] In the above-mentioned first cooperation form, the procedure of the payment server 20 in Fig. 5 including step S604 functions as a first relationship setting procedure of the present invention, and the authentication processing unit 201 of the payment server 20 executes the procedure to function as a first relationship setting means of the present invention. Also, the procedure of the payment server 20 in Fig. 6 including step S1002 functions as a value payment procedure of the present invention, and the payment processing unit 202 of the payment system 2 executes the procedure to function as a value payment means of the present invention. Similarly, the procedure of the payment server 20 in Fig. 7 including step S1502 functions as a cooperation cancellation procedure of the present invention. And, by implementing a function to execute the processes shown in Figs. 5 to 7 in each of the authentication processing unit 201 and the payment processing unit 202 of the payment system 2, the authentication processing unit 201 and the payment processing unit 202, and ultimately the payment system 2 (or the payment server 20) constitute an example of the cooperation system of the present invention.

[0085] Furthermore, in the first linkage form, the procedure of arcade server 10 in Fig. 5 including step S705 functions as a second relationship setting procedure of the present invention, and authentication processing unit 101 of arcade system 1 executes this procedure to function as second relationship setting means of the present invention. Similarly, the procedure of arcade server 10 in Fig. 6 including step S1101 functions as a payment request procedure of the present invention, and payment linkage unit 103 of arcade system 1 executes this procedure to function as payment request means of the present invention.

[0086] [Second form of collaboration] (Overview of collaboration procedures) FIG. 8 is an explanatory diagram for explaining an outline of the linking procedure in the second linking form. FIG. 8(A) shows the procedure for linking the systems 1 and 2 (establishing a linking relationship), and FIG. 8(B) shows the procedure for payment after the linking relationship is established. Note that in the example of FIG. 8, the game machine 12 is shown as a representative of the service terminal 11 as in the example of FIG. 2, but linking and payment may be performed in a similar procedure when a payment is made for a service of another service terminal 11. In the following, the case where a service-related app runs on the user terminal device 23 may be referred to as a service-related app, and the case where a payment app runs on the user terminal device 23 may be referred to as a payment app.

[0087] As shown in (A) of FIG. 8, in the procedure of linking in the second linking form, first, a procedure of linking the arcade system 1 and the payment system 2 (establishing a linking relationship) is executed. This procedure includes, as an example, procedures M1 to M10. Specifically, first, service information is provided from the game machine 12 to the user terminal device 23. In the second linking form, service information can be provided appropriately as in the first linking form, but the example of FIG. 8 shows a case where the service information is provided via the code CD as in the example of FIG. 2. In the second linking form, the camera CA of the user terminal device 23 also reads the code CD, but in the second linking form, unlike the first linking form, the reading is performed via a service-related app rather than a payment app. Then, when the service-related app (user terminal device 23) acquires the service information from the code CD, it transmits the service information to the arcade server 10 (arcade system 1) (M1).

[0088] When the arcade server 10 acquires the service information, it executes a link (pairing) between the game machine 12 corresponding to the service information and the service-related application (M2). This link can be realized as appropriate, but is executed as follows as an example. The service-related application can be configured as appropriate, but is configured as an example to manage play results (owned points, etc.) for each user via account information for identifying each user (or each play result). The arcade server 10 then realizes this link by creating a table that associates this account information with the cabinet ID of the game machine 12 corresponding to the service information. When the arcade server 10 executes the link, it notifies the service-related application of the result (M3). This notification can include various information as appropriate, but includes information necessary for settlement, such as the price of the game provided by the game machine 12, for example.

[0089] On the other hand, when a payment is instructed in the service-related app using the payment app, the service-related app calls the payment app (user terminal device 23) (M4). In other words, the payment app runs on the user terminal device 23 and launches the payment app so that its function becomes active (enabled) (including the case where an app that is already running in the background resumes operation). When the payment app is called by the service-related app, it obtains account information from the service-related app and transmits the account information to the payment server 20 (payment system 2) (M5). In this example, the instruction to make a payment using the payment app in the service-related app functions as a predetermined call instruction of the present invention.

[0090] When payment server 20 acquires the account information from the payment app, it transmits the account information to inquire of arcade server 10 of arcade system 1 whether or not collaboration for payment is possible (M6). When arcade server 10 acquires the account information, it determines that authentication has been established, and transmits the result of authentication establishment to payment server 20 (M7). With the transmission of the account information (in other words, with the provision of account information from the service-based app to the payment app via a link), it can be determined that the service-based app and the payment app are being executed on the same user terminal device 23, so additional authentication in arcade server 10 is omitted. Arcade server 10 may issue separate authentication information or the like and execute appropriate additional authentication.

[0091] When the payment server 20 obtains the authentication result (authentication success), it issues a session ID and transmits it to the arcade server 10 (arcade system 1), thereby establishing a session (linked relationship) between the two systems 1 and 2 (M8). The payment server 20 also notifies the payment app of the result of the session establishment (M9). Upon receiving this notification, the payment app calls the service-related app and provides the user with the result of the session establishment via the service-related app (M10). In this example, the account information functions as the predetermined information of the present invention.

[0092] 8B, when a linkage is established, a session (linkage) is maintained between arcade server 10 (arcade system 1) and payment server 20 (payment system 2) until a predetermined release condition is met. Specifically, when a linkage is established, first session data D1 is generated in arcade system 1, in which the issued session ID and account information for identifying a user of a service-based application (e.g., an account ID unique to each user) are associated and recorded, and the first session data D1 is stored in a state that can be referenced by arcade server 10.

[0093] Similarly, in the payment system 2, second session data D2 is generated that records the issued session ID in association with a user ID for identifying the user of the payment maker (which may be account information for the payment object associated with the user ID), and is stored in a state that can be referenced by the arcade server 10.

[0094] When the session is maintained, payment is executed via the service-based app. This payment procedure includes, as an example, the procedures M11 to F16. Specifically, in the second linkage form, the service-based app is interposed between the game machine 12 and the payment app, and the service-based app acquires information required to settle the price for the game machine 12 at least when linked with the game machine 12. Therefore, when an instruction (operation) is executed to request the service-based app to play on behalf of the game machine 12, the service-based app transmits a payment request corresponding to the price for that play to the arcade server 10 (arcade system 1) (M11).

[0095] When arcade server 10 acquires a payment request, it transmits the payment request to payment server 20 (payment system 2) (M12). When the payment request is acquired, payment server 20 executes the payment corresponding to the payment request (M13). In other words, when the session is maintained in the second cooperation form, procedures such as authentication and session construction that are normally required at the time of payment are omitted, and payment system 2 executes the payment directly based on the payment request from arcade system 1. After executing the payment, payment server 20 notifies arcade server 10 (arcade system 1) and the payment application of the payment result (M14).

[0096] When the payment application acquires the payment result, it stores the payment result so that the result is notified at least the next time it is started or when the payment result is referred to. On the other hand, when the arcade server 10 acquires the payment result, it notifies the service application and the game machine 12 of the result (M15). When the service application acquires the payment result, it notifies the user of the result of the payment (success or failure of the payment). Similarly, when the game machine 12 acquires the payment result, if the payment is unsuccessful, it notifies the user of that effect, whereas if the payment is successful, it permits the play requested by the user via the service application (M16). That is, the service application transmits a payment request to the payment system 2 via the arcade system 1 in accordance with the user's request for play, and if the payment is executed in the payment system 2, the request is permitted, and the play is actually provided via the game machine 12. Then, the steps M11 to M16 are repeatedly executed every time a request for play is instructed to the service application. As a result, even in the second form, in a situation where a session is maintained, authentication and the like are omitted, and continuous payment (multiple payments in a short period of time) is realized. In this example, the game-related service functions as the auxiliary service of the present invention. The payment application and the service-related application function as the payment function and the auxiliary service function of the present invention, respectively. The user terminal device 23 running the service-related application functions as the auxiliary service terminal of the present invention. The user terminal device 23 running the service-related application functions as the auxiliary service terminal of the present invention.

[0097] (Processing of linked systems) Next, the processing of the linked system in the second linkage form will be described with reference to Fig. 9 to Fig. 11. Note that the linkage cancellation processing may be executed in the second linkage form as well in the same manner as in the example of Fig. 7. For this reason, a description of a flowchart showing an example of the procedure of the linkage cancellation processing in the second linkage form will be omitted. However, in the second linkage form, the cancellation instruction may be executed on the service-related app (user terminal device 23) instead of the game machine 12.

[0098] FIG. 9 is a flow chart showing an example of the procedure of pairing processing. The pairing processing is processing for realizing pairing (linking) between the game machine 12 (service terminal 11) that provides a service to be paid for and a service-related application. The pairing processing is realized, as an example, by cooperation between the game machine 12, the payment linking unit 103 of the arcade server 10, and the user terminal device 23 (service-related application). Note that in FIGS. 9 to 11, the processing (procedures) executed mainly by the service-related application in the user terminal device 23 are shown as the service-related application, and the processing (procedures) executed mainly by the payment application are shown as the payment application. Also, in the example of FIG. 9, the processing (procedures) executed mainly by the payment linking unit 103 of the arcade server 10 is shown as the arcade server 10.

[0099] 9 and first transmits the acquired service information to the arcade server 10 (step S111). The service information may appropriately include various information related to the service of the game machine 12, and may include, for example, information for identifying the target game machine 12 (for example, information on the cabinet ID).

[0100] On the other hand, when service information is transmitted from a service-related application, the arcade server 10 starts the pairing process of FIG. 9 and first acquires the service information (step S311). Next, the arcade server 10 executes a link between the game machine 12 corresponding to the service information and the service-related application based on the service information acquired in step S311. Specifically, the arcade server 10 creates a table that associates the account information of the service-related application corresponding to the transmission source of the service information with the cabinet ID of the game machine 12 corresponding to the service information. Then, the arcade server 10 manages the pairing between the service-related application and the game machine 12 in this table, thereby realizing the link. Next, the arcade server 10 transmits the link result of step S312 to the target game machine 12 (the game machine 12 corresponding to the service information) and the service-related application (step S313). Then, after this transmission, the arcade server 10 ends the current pairing process.

[0101] When the link result is transmitted from the arcade server 10, the service-related application acquires the result (step S112) and notifies the user of the result by displaying it on a display device or the like (step S113). After this notification, the service-related application ends the current pairing process.

[0102] When the link result is transmitted from the arcade server 10, the game machine 12 starts the pairing process in FIG. 9 and first acquires the result (step S411). Next, the game machine 12 notifies the user of the link result acquired in step S411 by displaying it on a display device or the like (step S412). Then, after this notification, the game machine 12 ends the current pairing process. This realizes a link (linkage) between the game machine 12 that provides the service that is the subject of payment and the service-related app. More specifically, the steps M1 to M3 in the example of FIG. 8(A) are realized.

[0103] FIG. 10 is a flow chart showing an example of the procedure of application linkage processing. The application linkage processing is processing for establishing a linkage relationship between the arcade server 10 and the payment system 2 in order to settle the price of a target service. The application linkage processing is realized, as an example, by cooperation between the game machine 12, the authentication processing unit 101 of the arcade server 10, the authentication processing unit 201 of the payment server 20, and the user terminal device 23 (service-related application and payment application). Note that in FIG. 10, the processing (procedure) executed mainly by the authentication processing unit 101 of the arcade server 10 is shown as the arcade server 10, and the processing (procedure) executed mainly by the authentication processing unit 201 of the payment server 20 is shown as the payment server 2, respectively.

[0104] When a service-related app is instructed to cooperate with the payment server 20, the service-related app starts the application cooperation process in Fig. 10, first calls the payment app and transitions to the payment app (step S811). On the other hand, when the payment app is called by the service-related app, it starts the application cooperation process in Fig. 10, obtains account information from the service-related app and transmits it to the payment server 20 (step S511).

[0105] When the payment server 20 receives the account information from the payment application, the payment server 20 starts the application linking process shown in Fig. 10 and first acquires the account information (step S611). Next, the payment server 20 transmits the acquired account information to the arcade server 10 (step S612).

[0106] When the account information is transmitted from the settlement server 20, the arcade server 10 starts the application cooperation process of Fig. 10 and first acquires the account information (step S711). Next, the arcade server 10 transmits the authentication result (authentication success) of the acquired account information to the settlement server 20 (step S712).

[0107] When the settlement server 20 obtains the authentication result (authentication success) from the arcade system, it issues a session ID to establish a session (linkage relationship) with the arcade server 10 for settling the price of the game machine 12 (step S613). The settlement server 20 then transmits the issued session ID to the arcade server 10 (step S614) and stores the session ID by generating second session data D2 (associating it with the payer or his / her account) (step S615). The settlement server 20 then transmits the current linkage result to the settlement application (step S616). After this transmission, the settlement server 20 ends the current application linkage process.

[0108] When the session ID is sent from the settlement server 20, the arcade server 10 acquires the session ID (step S713) and generates the first session data D1 (associates it with the account information) and stores it (step S714). After this storage, the arcade server 10 ends the current application linking process.

[0109] On the other hand, when the result of the linkage is sent from the payment server 20, the payment application acquires the result (step S512). Next, the payment application calls the service application, and while sharing the acquired linkage result, transitions again to the service application (step S513), and ends the current application linkage process. When the service application is called by the payment application, it first acquires the linkage result from the payment application (step S812). Next, the service application notifies the user of the acquired linkage result by displaying it on a display device, etc. (step S813). Then, after this notification, the service application ends the current application linkage process. As a result, a linkage relationship between the arcade system 1 and the payment server 20 for settling the price of the game machine 12 is established via the service application. More specifically, the steps M4 to M10 in the example of FIG. 7B are realized.

[0110] FIG. 11 is a flow chart showing an example of the procedure of the second linked payment process. The second linked payment process is a process for executing continuous payments (payments) in a situation where a linked relationship (session) between the arcade server 10 and the payment server 20 is maintained in the second linked form. The second linked payment process is realized, as an example, by cooperation between the game machine 12, the payment linking unit 103 of the arcade server 10, the payment processing unit 202 of the payment server 20, and a service-related application. Note that in FIG. 11, the process (procedure) executed mainly by the payment linking unit 103 of the arcade server 10 is shown as the arcade server 10, and the process (procedure) executed mainly by the payment processing unit 202 of the payment server 20 is shown as the payment server 2.

[0111] When a user instructs payment of a fee (provision of play) while a session is being maintained between the systems 1 and 2, the service-related application starts the second linked payment process of Fig. 11 and first transmits a payment request to the arcade server 10 (step S911). This request includes information necessary for payment, such as the amount of the fee.

[0112] When the arcade server 10 receives a payment request from the service-related application, the arcade server 10 starts the second linked payment process of Fig. 11 and acquires the payment request (step S1111). Next, the arcade server 10 transmits the acquired payment request to the payment server 20 (step S1112).

[0113] When the payment request is transmitted from the arcade server 10, the payment server 20 starts the second linked payment process of FIG. 11 and first acquires the payment request (step S1011). Next, the payment server 20 executes the payment according to the payment request acquired in step S1011 while referring to the second session data D2 (step S1012). This payment is realized by deducting the balance of the account of the user ID associated with the session ID. Next, the payment server 20 notifies the arcade server 10 of the payment result in step S1012 (step S1013). In this case, the payment server 20 may also notify the payment app of the payment result so that the current payment result is reflected when the payment app is started. Then, after this notification, the payment server 20 ends the current second linked payment process.

[0114] On the other hand, when the arcade server 10 is notified of the payment result from the payment server 20, the arcade server 10 acquires the payment result (step S1113). Next, the arcade server 10 notifies the service application and the game machine 12 of the acquired payment result (step S1114). Then, after this notification, the arcade server 10 ends this second linked payment process.

[0115] When the service-related application is notified of the payment result from the arcade server 10, the service-related application acquires the result and stores the result so that the user can check it at any time (step S912). After storing the result, the service-related application ends the second linked payment process.

[0116] When the game machine 12 is notified of the payment result from the arcade server 10, it starts the second linked payment process of Fig. 11 and first acquires the payment result (step S1211). Next, the game machine 12 determines whether the payment was successful or not based on the acquired payment result (step S1212). If the payment has failed (step S1212: No), the game machine 12 skips the subsequent processes and ends this second linked payment process. In this case, the game machine 12 may appropriately notify the user of the result of the payment failure via a display device or the like.

[0117] On the other hand, if the payment is successful (step S1212: Yes), the game machine 12 permits the user to play the game instructed via the service-based app, and starts playing (step S1213). After the game starts, the game machine 12 ends the second linked payment process. As a result, authentication and the like are omitted in a situation where the session is maintained, and the payment system 2 pays for the game via the service-based app in a relatively simple procedure. Generally, the session is released after the payment is completed, and authentication and the like are requested again at the time of the next payment, but in the example of FIG. 11, the session is not released and is maintained even after the payment. Therefore, the payment system 2 pays for the play on the game machine 12 repeatedly in a relatively simple procedure via the service-based app. More specifically, the procedure of M11 to M16 in the example of FIG. 7C is realized.

[0118] As described above, according to the second cooperation form, it is possible to obtain an effect such as reducing the time and effort of the user for multiple payments, as in the first cooperation form. In addition, in the second cooperation form, a service application is interposed between the service terminal 11 such as the game machine 12 and the payment system 2, and the price of a service such as a game is paid through the service application. Therefore, by linking the service application with another service terminal 11 such as the vending machine 13, the cooperation relationship is maintained so that multiple payments across multiple service terminals 11 are permitted in a situation where the cooperation relationship is maintained. This reduces the time and effort required for payments for multiple services. As a result, it is possible to promote the use of multiple services. In particular, in a facility where multiple service terminals 11 each providing multiple services are installed, the convenience of the facility itself is improved as the convenience of payments for each service is improved, and an increase in the number of users can be expected.

[0119] Also, by using the payment app (payment function) and the service app (auxiliary function) separately, one user terminal device 23, 15 can function as both a terminal for the payment system 2 and a terminal for the arcade system 1. This improves user convenience. Furthermore, the functions of the service app and the payment app are automatically linked, and payment information is passed on, improving user convenience.

[0120] In the above second cooperation form, the procedure of the payment server 20 in Fig. 10 including step S614 functions as a first relationship setting procedure of the present invention, and the authentication processing unit 201 of the payment server 20 executes the procedure to function as a first relationship setting means of the present invention. Also, the procedure of the payment server 20 in Fig. 11 including step S1012 functions as a value payment procedure of the present invention, and the payment processing unit 202 of the payment server 20 executes the procedure to function as a value payment means of the present invention. Then, by implementing functions for executing the processes shown in Figs. 10 and 11 in the authentication processing unit 201 and the payment processing unit 202 of the payment server 20, respectively, the authentication processing unit 201 and the payment processing unit 202, and ultimately the payment system 2 (or the payment server 20) constitute an example of the cooperation system of the present invention.

[0121] Furthermore, in the second linkage form, the procedure of arcade server 10 in Fig. 10 including step S714 functions as a second relationship setting procedure of the present invention, and authentication processing unit 101 of arcade server 10 executes the procedure to function as second relationship setting means of the present invention. Similarly, the procedure of arcade server 10 in Fig. 11 including step S1112 functions as a payment request procedure of the present invention, and payment linkage unit 103 of arcade server 10 executes the procedure to function as payment request means of the present invention. Note that the procedure of the service-related app in Fig. 11 including step S911 may function as a payment request procedure of the present invention, and user terminal device 23 executes the procedure via the service-related app to function as payment request means of the present invention.

[0122] The present invention is not limited to the above-mentioned embodiment, and may be embodied in an appropriate modified or altered form. The present invention may also be embodied in an appropriate combination of various technical means included in the above-mentioned embodiment and the following modified embodiment. In the above-mentioned embodiment, the linkage system is applied to the payment of the price of the services provided by the game machine 12, the vending machine 13, and the user terminal device 15. However, the present invention is not limited to such an embodiment. For example, the linkage system may be applied to the payment of services such as the purchase of various tickets, the payment of the price for items lent at the game facility, or appropriate donations (so-called tips, etc.) for various contents.

[0123] In the second cooperation form described above, a payment request is provided to the payment system 2 via the arcade system 1. However, the present invention is not limited to this form. For example, a service-related app may cooperate with a payment app and execute a payment request to the payment system 2 via the payment app. In other words, the payment request may be executed as appropriate.

[0124] In the above embodiment, the authentication processing unit 201 and the payment processing unit 202, and further the payment system 2 (or the payment server 20) constitute an example of the linked system of the present invention. However, the present invention is not limited to such an embodiment. For example, the arcade system 1 may execute a part or all of the roles of the authentication processing unit 201 and the payment processing unit 202, so that a combination of the payment system 2 and the arcade system 1, or the arcade system 1 may function as the linked system of the present invention. Alternatively, another system may be interposed between the payment system 2 and the arcade system 1, and the other system may function as the linked system of the present invention by executing the roles of the authentication processing unit 201 and the payment processing unit 202. Furthermore, the combination of the other system, the payment system 2, and the arcade system 1 may function as the linked system. The service terminal 11 or the user terminal device 23 may function as the other system.

[0125] The same applies to the service system of the present invention. For example, the entire role of the arcade server 10 may be performed by the user terminal device 15, and the user terminal device 15 alone may function as the service system of the present invention. Alternatively, part of the role of the arcade server 10 may be shared by the user terminal device 15, and the combination of the arcade server 10 and the user terminal device 15 may function as the service system of the present invention, or another appropriate system may function as the service system of the present invention.

[0126] Various aspects of the present invention derived from the above-mentioned embodiments and modifications will be described below. In the following description, to facilitate understanding of each aspect of the present invention, corresponding components shown in the accompanying drawings are written in parentheses, but the present invention is not limited to the illustrated forms.

[0127] The control method of the present invention causes a computer (20) incorporated in a linking system (2) for linking a service system (1) for providing a specified service with a payment system (2) so that a fee for the specified service is settled, to execute a first relationship setting procedure for establishing a linking relationship between the service system (1) and the payment system for settling the fee for the specified service, and a fee settlement procedure for causing the payment system to settle the fee for the specified service in a state in which the linking relationship is established so that multiple payments are allowed in response to a payment request from the service system.

[0128] According to the present invention, after the linkage relationship is established, the payment system settles the price of a predetermined service in response to a payment request from the service system so that multiple payments are allowed. In other words, the linkage relationship is maintained so that multiple payments are allowed after the linkage relationship is established. In general, the linkage relationship often requires time and effort such as user authentication. At least various information for establishing the linkage relationship needs to be transmitted and received between the two systems. As a result, it often takes time. For this reason, by maintaining the linkage relationship so as to allow multiple payments after the linkage relationship is established, these procedures can be omitted. As a result, the user's time and effort for multiple payments can be reduced, and multiple payments, such as continuous play in a prize game, can be promoted.

[0129] The payment system may be appropriately configured. For example, the payment system may be configured as a reader for a payment card (one example of a payment medium) such as a credit card. The user may provide the predetermined information to the reader (payment system) by manual input or the like. Similarly, various media may be appropriately used as the payment medium. For example, as the payment medium, a recording medium such as a medium (e.g., an ID card) that records information (e.g., a user ID) for identifying each user associated with the payment value, or a medium that directly records the payment value may be used. For example, a user terminal device such as a smartphone may be used as a specific example of such a payment medium. In addition, the predetermined information for linking the payment system and the service system may be appropriately provided to one of the two systems (or both). For example, a user ID (predetermined information) may be provided to the service system via a card that records information on the user ID as the predetermined information. In other words, the predetermined information may be provided from the payment system to the service system. Or, conversely, the predetermined information may be provided from the service system to the payment system.

[0130] Specifically, for example, in one aspect of the control method of the present invention, the payment system is configured to pay for the specified service via a user terminal device (23), and the service system is provided with an information providing means (CD) for providing the user terminal device with specified information used in establishing the linkage relationship, and the first relationship setting procedure may acquire the specified information via the user terminal device and establish the linkage relationship based on the specified information.

[0131] The service system may be configured appropriately in the same manner. For example, the service system may be configured as a service terminal that directly provides a predetermined service to the user. Alternatively, the service system may be configured as a device separate from the service terminal. Furthermore, the information providing means may be configured appropriately. For example, the information providing means may be configured as a display device that displays the predetermined information. Alternatively, the information providing means may be configured appropriately to provide the predetermined information in various other ways.

[0132] For example, in one aspect of the control method of the present invention, the service system may be configured to provide the predetermined service via a service terminal (11), and the service terminal may function as the information providing means. In an aspect in which an information providing means is provided, the service terminal may be provided with a code (CD) generated in compliance with a predetermined standard so as to include the predetermined information, and the user terminal device may be provided with a reader (CA) for reading the code, and the predetermined information may be provided via the code. Alternatively, the service terminal may be provided with a transmission function for transmitting the predetermined information via short-range wireless communication, and the user terminal device may be provided with a receiving function (CU) for the short-range wireless communication, and the predetermined information may be provided via the short-range wireless communication. In these cases, it is possible to prevent the predetermined information used for payment from being directly recognized by the user. For example, depending on the type of service terminal, it may be installed in a facility that is available to an unspecified number of users. In that case, if the predetermined information is easily recognized by the user, it is not preferable from the viewpoint of security. For this reason, when the predetermined information is provided to the user terminal device via a code or a short-range wireless notification, it is possible to improve security.

[0133] In the settlement between the settlement system and the service system, an appropriate device may be involved, not limited to a user terminal device. For example, in a mode in which an information providing means is provided, the service system is configured to provide the predetermined service via a service terminal (11) and an auxiliary service that supports the predetermined service via an auxiliary service terminal (15), and the auxiliary service terminal functions as the information providing means by obtaining service information related to the service terminal from the service terminal so as to provide the auxiliary service in cooperation with the service terminal and providing the predetermined information to the user terminal device, and the payment procedure may cause the payment system to pay the price for the predetermined service after the auxiliary service terminal and the service terminal are linked based on the service information.

[0134] In addition, in a mode in which an auxiliary service terminal is involved, the service system is configured to provide a plurality of services as the predetermined services via a plurality of service terminals (12, 13), and the auxiliary service terminal is linked to the plurality of service terminals based on the service information of each service terminal, and the payment procedure may include, when payment for the plurality of services provided by the plurality of service terminals is requested in a situation in which the linkage is established, making the payment system pay the fees for the plurality of services. In this case, the linkage is maintained so that multiple payments across the plurality of service terminals are permitted. This reduces the time and effort required for payment for the plurality of services. As a result, the use of the plurality of services can be promoted. In particular, in a facility in which a plurality of service terminals each providing a plurality of services are installed, the convenience of the facility itself can be improved as the convenience of payment for each service is improved, and an increase in users can be expected.

[0135] Various terminals (devices) may be appropriately used as the auxiliary service terminal. For example, the auxiliary service terminal may be a dedicated terminal separate from the user terminal device. Also, for example, in a mode in which an auxiliary service terminal is involved, the user terminal device may be provided with a payment function for paying for the predetermined service and an auxiliary service function for providing the auxiliary service, and the user terminal device using the auxiliary service function may be used as the auxiliary service terminal. In this case, by using the payment function and the auxiliary service function separately, one user terminal device can be made to serve as both a terminal for the payment system and a terminal for the service system. This can improve the convenience of the user.

[0136] Even in the case where an auxiliary service terminal is involved, the predetermined information may be provided as appropriate. The same applies to the service information. For example, in a mode in which a user terminal device is provided with a payment function and an auxiliary service function, the service terminal may be provided with a code (CD) generated in compliance with a predetermined standard so as to include the service information, the user terminal device may be provided with a reader (CA) for reading the code, and the auxiliary service function may be configured to cooperate with the service terminal based on the service information read from the code via the reader. Alternatively, the service terminal may be provided with a transmission function for transmitting the service information by short-range wireless communication, the user terminal device may be provided with a receiving function (CU) for the short-range wireless communication, and the auxiliary service function may be configured to cooperate with the service terminal based on the service information received via the short-range wireless communication.

[0137] The auxiliary service function may be configured appropriately. For example, the auxiliary service function and the payment function may be configured as independent functions that are not linked to each other. In this case, for example, various information such as service information may be shared between the two functions through the intervention of the user. Alternatively, the auxiliary service function and the payment function may be configured to be linked to each other. For example, in a mode in which the payment function and the auxiliary service function are provided in a user terminal device, the auxiliary service function may be configured to call the payment function based on a predetermined call instruction after acquiring the service information. In this case, the two functions are automatically linked to each other, thereby improving user convenience.

[0138] Various services may be provided as the predetermined service as appropriate. For example, the predetermined service may be the sale of goods by a vending machine or the use of a predetermined facility. Specifically, in one aspect of the control method of the present invention, the service system may provide a game as the predetermined service.

[0139] The linked system may be configured by an appropriate system. For example, the linked system may be configured as a system (device) separate from the payment system and the service system. The linked system may also be a combination of the payment system and the service system (including an appropriate partial combination of both). Alternatively, the linked system may be either the payment system or the service system. For example, in one aspect of the control method of the present invention, the payment system may function as the linked system.

[0140] In multiple payments executed after the establishment of a linked relationship, an opportunity to confirm whether or not a payment is possible (whether or not to approve the payment) may be provided to the user for each payment, or may be omitted as appropriate. For example, in one aspect of the control method of the present invention, the service system may be configured to omit an opportunity to confirm with the user whether or not to approve the second or subsequent payments at least for the second or subsequent payments when multiple payments are requested. In this case, the approval process is omitted, which further reduces the user's time and effort.

[0141] The maintenance of the linkage may be cancelled based on an appropriate cancellation condition. For example, in a case where a specific service is provided at a specific facility and the user's location is identified through location information of a user terminal device, the cancellation condition may be satisfied when the user leaves the specific facility. Alternatively, the cancellation condition may be satisfied when a specific number of payments, such as five, are executed. The cancellation condition may also be satisfied when a specific cancellation instruction is executed by the user or when a specific time has elapsed. Specifically, for example, as one aspect of the control method of the present invention, the computer may further execute a cancellation procedure to cause the payment system to cancel the linkage when at least one of an instruction to cancel the linkage is executed by a user of the service system and a specific time has elapsed since the establishment of the linkage may be adopted. In this case, the user can be given a sense of security regarding continuous payments during the period until a condition such as a cancellation instruction or the passage of a specific time is satisfied.

[0142] The computer program (PG1) of the present invention is configured to cause a computer (20) incorporated in a linkage system (2) for linking a service system (1) for providing a specified service with a payment system (2) so that the fee for the specified service is settled, to function as a first relationship setting means (201) for establishing a linkage relationship between the service system and the payment system for settling the fee for the specified service, and as a fee settlement means (202) for settling the fee for the specified service to the payment system so that multiple payments are allowed in response to a payment request from the service system when the linkage relationship is established.

[0143] The collaboration system of the present invention is an collaboration system (2) for linking a service system (1) for providing a specified service with a payment system (2) so that a fee for the specified service is settled, and includes a first relationship setting means (201) for establishing a collaboration relationship between the service system and the payment system for settling the fee for the specified service, and a fee settlement means (202) for causing the payment system to settle the fee for the specified service so that multiple payments are allowed in response to a payment request from the service system when the collaboration relationship is established.

[0144] On the other hand, a control method applicable to the service system of the present invention causes a computer (20) incorporated in a service system (1) for providing a specified service in a linking system (2) for linking the service system (1) with a payment system (2) so that a fee for the specified service is settled, to execute a second relationship setting procedure for establishing a linking relationship with the payment system for settling the fee for the specified service, and a payment request procedure for requesting the payment system to settle the fee for the specified service so that multiple payments are allowed in accordance with instructions from a user when the linking relationship is established.

[0145] In addition, a computer program (PG2) applied to the service system of the present invention is configured to cause a computer (10) incorporated in a service system (1) for providing a specified service in a linking system (2) for linking the service system (1) with a payment system (2) so that the fee for the specified service is settled, to function as a second relationship setting means (101) for establishing a linking relationship with the payment system for settling the fee for the specified service, and as a payment request means (103) for requesting the payment system to settle the fee for the specified service so that multiple payments are allowed in accordance with instructions from a user when the linking relationship is established.

[0146] Furthermore, the service system of the present invention is a linking system (2) for linking a service system (1) for providing a predetermined service with a payment system (2) so that a fee for the predetermined service is paid, the service system comprising a second relationship setting means (101) for establishing a linking relationship with the payment system for paying the fee for the predetermined service, and a payment request means (103) for requesting the payment system to pay the fee for the predetermined service so that multiple payments are allowed according to an instruction from a user when the linking relationship is established. The service system of the present invention, the control method applied thereto, and the computer program can realize a service system related to the linking system of the present invention. [Explanation of symbols]

[0147] 1 Arcade System (Service System) 2. Payment System 10 Arcade Server (Computer) 20 Payment server (linked system, computer) 101 Authentication processing unit (second relationship setting means) 103 Payment linking unit (payment request means) 201 Authentication processing unit (first relationship setting means) 202 Payment processing unit (payment means) PG1 Server program (computer program) PG2 Server program (computer program)

Claims

1. A computer to be incorporated in a linking system for linking a service system for providing a predetermined service with a settlement system so that a fee for the predetermined service is settled, a first relationship setting procedure for establishing an association relationship between the service system and the payment system via identification information issued to be shared between the service system and the payment system after a certain authentication is successful, the association relationship maintaining the state after the certain authentication is successful as a relationship for settling the consideration for the certain service; a payment procedure for causing the payment system to pay the fee for the specified service in such a manner that multiple payments are allowed in response to a payment request from the service system by maintaining the linkage relationship until a predetermined cancellation condition is satisfied while the linkage relationship is established; A control method for executing the above.

2. The payment system is configured to settle the price of the predetermined service via a user terminal device, the service system is provided with an information providing means for providing to the user terminal device predetermined information related to the predetermined service included in information used to establish the linkage relationship; The control method according to claim 1 , wherein the first relationship setting step acquires the predetermined information via the user terminal device.

3. The service system is configured to provide the predetermined service via a service terminal; The control method according to claim 2 , wherein the service terminal functions as the information providing means.

4. The service terminal is provided with a code generated in accordance with a predetermined standard so as to include the predetermined information; The control method according to claim 3 , wherein the user terminal device is provided with a reader for reading the code, and the predetermined information is provided via the code.

5. the service terminal is provided with a transmission function for transmitting the predetermined information by short-range wireless communication; The control method according to claim 3 , wherein the user terminal device is provided with a receiving function for the short-range wireless communication, and the predetermined information is provided via the short-range wireless communication.

6. the service system is configured to provide the predetermined service via a service terminal and an auxiliary service that supports the predetermined service via an auxiliary service terminal; the auxiliary service terminal acquires service information related to the service terminal from the service terminal so as to provide the auxiliary service in cooperation with the service terminal, and functions as the information providing means by providing the predetermined information to the user terminal device; The control method according to claim 2 , wherein the payment procedure includes causing the payment system to pay for the predetermined service after the auxiliary service terminal and the service terminal are linked based on the service information.

7. the service system is configured to provide a plurality of services as the predetermined service via a plurality of service terminals, The auxiliary service terminal is linked to the plurality of service terminals based on the service information of each service terminal; The control method described in claim 6, wherein the fee payment procedure causes the payment system to pay for each of a plurality of services provided by the plurality of service terminals when payment is requested when the collaborative relationship is established.

8. The user terminal device is provided with a payment function for paying for the predetermined service and an auxiliary service function for providing the auxiliary service, The control method according to claim 7 , wherein the user terminal device utilizing the auxiliary service function is utilized as the auxiliary service terminal.

9. The service terminal is provided with a code generated in accordance with a predetermined standard so as to include the service information; The user terminal device is provided with a reader for reading the code, The control method according to claim 8 , wherein the auxiliary service function is configured to cooperate with the service terminal based on the service information read from the code via the reader.

10. the service terminal is provided with a transmission function for transmitting the service information by short-range wireless communication; The user terminal device is provided with a receiving function for the short-range wireless communication, The control method according to claim 8 , wherein the auxiliary service function is configured to cooperate with the service terminal based on the service information received via the short-range wireless communication.

11. The control method according to any one of claims 8 to 10, wherein the auxiliary service function is configured to call the payment function based on a predetermined call instruction after obtaining the service information.

12. The control method according to any one of claims 1 to 10, wherein the service system provides a game as the predetermined service.

13. The control method according to any one of claims 1 to 10, wherein the payment system functions as the linked system.

14. The control method according to any one of claims 1 to 10, wherein the service system is configured to omit an opportunity to confirm with a user whether or not to approve the second or subsequent payments when the multiple payments are requested, at least for the second or subsequent payments.

15. A control method as described in any one of claims 1 to 10, further comprising causing the computer to execute a disconnection procedure that causes the payment system to disconnect the connection when at least one of the following cases is met: an instruction to disconnect the connection is executed by a user of the service system, and a predetermined time has elapsed since the connection was established.

16. A computer to be incorporated in a linking system for linking a service system for providing a predetermined service with a payment system so that a fee for the predetermined service is paid, a first relationship setting means for establishing an association relationship between the service system and the payment system, which maintains a state after the success of the predetermined authentication, as a relationship for settling the consideration for the predetermined service between the service system and the payment system via identification information issued to be shared between the service system and the payment system after the success of the predetermined authentication; A computer program configured to function as a payment means for paying the fee for the specified service to the payment system so as to allow multiple payments in response to a payment request from the service system by maintaining the linked relationship until a specified termination condition is met when the linked relationship is established.

17. A linking system for linking a service system for providing a predetermined service with a payment system so that a fee for the predetermined service is paid, comprising: a first relationship setting means for establishing an association relationship between the service system and the payment system, which maintains a state after the success of the specified authentication, as a relationship for settling the consideration for the specified service between the service system and the payment system via identification information issued to be shared between the service system and the payment system after the success of the specified authentication; a payment settlement means for causing the payment system to settle the price of the specified service in such a manner that multiple payments are permitted in response to a payment request from the service system by maintaining the linked relationship until a predetermined cancellation condition is satisfied while the linked relationship is in a state where the linked relationship is established; A collaborative system that includes:

18. A service system for providing a predetermined service is linked to a payment system so that a fee for the predetermined service is paid, the service system being linked to a computer that is incorporated in the service system, a second relationship setting procedure for establishing an association relationship that maintains a state after the success of the specified authentication as a relationship for settling the consideration for the specified service with the payment system via identification information issued to be shared between the service system and the payment system after the success of the specified authentication; a payment request procedure for requesting the payment system to make a payment for the specified service so that multiple payments are allowed according to an instruction from a user by maintaining the linked relationship until a specified release condition is met while the linked relationship is in a state where the linked relationship is established; A control method for executing the above.

19. A service system for providing a predetermined service is linked to a payment system so that a fee for the predetermined service is paid, the service system being linked to a payment system, and a computer being incorporated in the service system in the linkage system, a second relationship setting means for establishing an association relationship that maintains a state after the success of the predetermined authentication as a relationship for settling the consideration for the predetermined service with the payment system via identification information issued to be shared between the service system and the payment system after the success of the predetermined authentication; and A computer program configured to function as a payment request means for requesting the payment system to pay for the specified service so as to allow multiple payments in accordance with instructions from a user by maintaining the linked relationship when the linked relationship is established until a specified termination condition is met.

20. A service system for providing a predetermined service and a payment system for making the service system cooperate with each other so that a payment for the predetermined service is paid, the service system comprising: a second relationship setting means for establishing an association relationship that maintains a state after the success of the specified authentication as a relationship for settling a price for the specified service with the payment system via identification information that is issued to be shared between the service system and the payment system after the success of the specified authentication; a payment request means for requesting the payment system to make a payment for the specified service so that multiple payments are allowed according to an instruction from a user by maintaining the linked relationship until a specified release condition is satisfied while the linked relationship is in a state where the linked relationship is established; A service system comprising:

Images