Information processing device, information processing system, information processing method and program

Abstract

An information processing device, an information processing system, an information processing method, and a program are provided that can improve convenience regarding the settlement of transaction objects. [Solution] The information processing device includes a user identification data acquisition unit that acquires user identification data of a user who uses a payment terminal device to make payment for a transaction object, an application identification data acquisition unit that acquires identification data of a designated application specified by the user from the payment terminal device, a contract status acquisition unit that acquires a contract status corresponding to the user identification data and the identification data of the designated application, and a usage authority determination unit that determines the usage authority of the designated application based on the contract status.

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing system, an information processing method, and a program. [Background technology]

[0002] Conventionally, an electronic payment system, which is an example of an information processing system, has been disclosed, for example, in Patent Document 1. Such an electronic payment system includes a payment server, which is an example of an information processing device. The payment server performs payment for a transaction object by acquiring data related to the payment of the transaction object via an application installed in a store terminal, which is an example of a payment terminal device. Such an electronic payment system can improve convenience regarding the payment of a transaction object by allowing a user to use the electronic payment system via the store terminal. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-181911 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in such information processing systems, the setup work for the applications used in the payment terminal device is complicated, and therefore convenience in terms of payment of transaction objects is not high. [Means for solving the problem]

[0005] An information processing device that solves the above problem includes a user identification data acquisition unit that acquires user identification data of a user who uses a payment terminal device that makes payment for a transaction object, an application identification data acquisition unit that acquires identification data of a designated application specified by the user from the payment terminal device, a contract status acquisition unit that acquires a contract status corresponding to the user identification data and the identification data of the designated application, and a usage authority determination unit that determines the usage authority of the designated application based on the contract status.

[0006] An information processing system that solves the above problem includes a user identification data acquisition unit that acquires user identification data of a user who uses a payment terminal device that makes payment for a transaction object, an application identification data acquisition unit that acquires identification data of a designated application designated by the user from the payment terminal device, a contract status acquisition unit that acquires a contract status corresponding to the user identification data and the identification data of the designated application, and a usage authority determination unit that determines the usage authority of the designated application based on the contract status.

[0007] An information processing method that solves the above problem involves at least one computer acquiring user identification data of a user who uses a payment terminal device to make payment for a transaction object, acquiring identification data of a designated application designated by the user from the payment terminal device, acquiring a contract status corresponding to the user identification data and the identification data of the designated application, and determining the authorization to use the designated application based on the contract status.

[0008] A program that solves the above problem causes at least one computer to acquire user identification data of a user who uses a payment terminal device to make payment for a transaction object, acquire identification data of a designated application designated by the user from the payment terminal device, acquire a contract status corresponding to the user identification data and the identification data of the designated application, and determine the usage authority of the designated application based on the contract status. [Effects of the Invention]

[0009] According to the present invention, it is possible to improve convenience regarding the settlement of transaction objects. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing the overall configuration of an information processing system according to the first embodiment. [Figure 2] FIG. 2 is a diagram illustrating the electrical configuration of the payment terminal device of the first embodiment. [Figure 3] FIG. 3 is a diagram illustrating the electrical configuration of the information processing apparatus according to the first embodiment. [Figure 4] FIG. 4 is a diagram showing the contract type and contract status of the first embodiment. [Figure 5] FIG. 5 is a diagram illustrating the application management database of the first embodiment. [Figure 6] FIG. 6 is a diagram showing the contract performance database of the first embodiment. [Figure 7] FIG. 7 is a diagram illustrating the user management database according to the first embodiment. [Figure 8] FIG. 8 is a flowchart showing the application registration process according to the first embodiment. [Figure 9] FIG. 9 is a flowchart showing the data provision control process according to the first embodiment. [Figure 10] FIG. 10 is a flowchart showing the use determination control process according to the first embodiment. [Figure 11]FIG. 11 is a flowchart showing the use determination control process according to the first embodiment. [Figure 12] FIG. 12 is a flowchart showing the contract renewal control process according to the first embodiment. [Figure 13] FIG. 13 is a diagram showing a display screen of the payment terminal device of the first embodiment. [Figure 14] FIG. 14 is a diagram showing a display screen of the payment terminal device according to the first and third embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0011] [First embodiment] An information processing device, an information processing system, an information processing method, and a program according to an embodiment will be described.

[0012] <Configuration of Information Processing System 10> 1, an information processing system 10 is configured to perform settlement of transaction objects. Transaction objects include, for example, goods and services. Transactions include, for example, purchase, sale, loan, use, and reservation.

[0013] The information processing system 10 is configured to provide an application to a user. Hereinafter, an application may be simply referred to as an app. The user makes a payment for a transaction object. The user may be a store manager or a store salesperson. The user may be a taxi driver or a mobile salesperson. In other words, the user is a seller who makes a payment for a transaction object.

[0014] The information processing system 10 includes an information processing device 11. The information processing device 11 manages apps to be provided to users. The information processing device 11 may perform payments related to the use of the apps. For example, the information processing device 11 performs payments from an app provider for the management of the apps. The information processing device 11 may be a payment server that performs payments for transaction objects. The app provider may be the creator of the apps. For example, the information processing device 11 performs payments for the provision of apps to users. The information processing device 11 is managed by an administrator of the information processing system 10, but may also be managed by an administrator different from the administrator of the information processing system 10.

[0015] The information processing system 10 includes at least one provision server 12. The information processing system 10 may include a first provision server 12A and a second provision server 12B. The provision server 12 provides an application to the information processing device 11. The provision server 12 is managed by an application provider.

[0016] Information processing system 10 includes at least one payment terminal device 18. Information processing system 10 may include first payment terminal device 18A and second payment terminal device 18B. Payment terminal device 18 is used, for example, by a user. Payment terminal device 18 may be installed in a store. Payment terminal device 18 may be a portable terminal device that can be carried by the user.

[0017] Payment terminal device 18 is configured to make payment for the transaction object. Payment terminal device 18 may make payment for the transaction object by communicating with the purchase terminal device of the purchaser. The purchaser purchases the transaction object. Payment terminal device 18 may make payment for the transaction object by reading data from a card held by the purchaser or a mobile terminal device held by the purchaser. Payment terminal device 18 may make various types of code payments. Payment terminal device 18 may be capable of communicating with a cash register. Payment terminal device 18 may be linked to a cash register.

[0018] Payment terminal device 18 can use an app provided by information processing device 11. Payment terminal device 18 can start the app by installing the app provided by information processing device 11.

[0019] The information processing device 11, at least one provision server 12, and at least one payment terminal device 18 may be able to communicate with each other via a network 19. Hereinafter, a description of communication between each of the multiple devices via the network 19 will be omitted.

[0020] <Configuration of payment terminal device 18> 2, payment terminal device 18 may be realized by at least one computer. Payment terminal device 18 includes a terminal control unit 20, a terminal storage unit 21, a terminal communication unit 22, a terminal input unit 23, a terminal display unit 24, and a terminal reading unit 25.

[0021] Terminal control unit 20 may be a processor that controls payment terminal device 18. Terminal control unit 20 includes an arithmetic unit and a main storage medium. The arithmetic unit loads an OS (Operating System) and programs from terminal storage unit 21 to the main storage medium and executes instructions retrieved from the main storage medium. The arithmetic unit is at least one circuit. The circuit may be a CPU (Central Processing Unit), a GPU (Graphic Processing Unit), or an NPU (Neural network Processing Unit). Terminal storage unit 21 is a secondary storage medium and is a non-transitory computer-readable medium that stores programs. Terminal storage unit 21 may include a storage medium that is detachable from payment terminal device 18.

[0022] The terminal communication unit 22 is implemented as hardware, software, or a combination thereof. The terminal communication unit 22 transmits and receives data to and from the information processing device 11. The terminal input unit 23 is configured to input data in response to a user's operation. The terminal input unit 23 may be a touch panel integrated with the terminal display unit 24. The terminal input unit 23 may be a pointing device with operation buttons. The terminal display unit 24 displays an image in response to an output instruction from the terminal control unit 20.

[0023] The terminal reading unit 25 is configured to read data. The terminal reading unit 25 may be a camera that captures an image of a payment code. The terminal reading unit 25 may be a barcode scanner that reads a payment code. The terminal reading unit 25 may be a card reader that reads data from an IC card or a cash card. The terminal reading unit 25 may be a reader that supports contactless payment, such as touch payment.

[0024] <Configuration of information processing device 11> As shown in FIG. 3, the information processing device 11 may be realized by at least one computer. The information processing device 11 includes a control unit 30, a storage unit 31, and a communication unit 32. The control unit 30 may be a processor that controls the information processing device 11. The control unit 30 includes a calculation unit and a main storage medium. The control unit 30 has a configuration similar to that of the terminal control unit 20, and therefore, description of the calculation unit and the main storage medium will be omitted. The calculation unit may be implemented as hardware, software, or a combination thereof. The storage unit 31 is a secondary storage medium and is a non-transitory computer-readable medium that stores data for managing the information processing device 11. The storage unit 31 may include a storage medium that is detachable from the information processing device 11.

[0025] The communication unit 32 is implemented as hardware, software, or a combination thereof. The information processing device 11 may include an operation unit for an administrator to input data, and may include a display unit for displaying images.

[0026] The provision server 12 has the same configuration as the information processing device 11. That is, the provision server 12 has configurations similar to the control unit 30, the storage unit 31, and the communication unit 32 in the information processing device 11. Explanation of the configuration of the provision server 12 will be omitted.

[0027] <Functions of the information processing device 11> In the information processing device 11, the control unit 30 executes programs to realize various functions. The control unit 30 includes a user identification data acquisition unit 30A, a registration unit 30B, a usage request acquisition unit 30C, an application identification data acquisition unit 30D, a terminal identification data acquisition unit 30E, a contract status acquisition unit 30F, and a usage authority determination unit 30G. The control unit 30 also includes a usage control unit 30H, a display control unit 30I, and a contract status providing unit 30J.

[0028] The user identification data acquisition unit 30A is configured to acquire user identification data. The user identification data acquisition unit 30A may acquire the user identification data from the payment terminal device 18. The user identification data acquisition unit 30A may acquire the user identification data from the storage unit 31 in response to input data from the payment terminal device 18. For example, the input data may be a user account and password that are different from the user identification data. For example, the user account may be the user's email address. The user identification data acquisition unit 30A may acquire the user identification data from an external server (not shown) in response to the input data from the payment terminal device 18. The external server may be a server that manages some or all of the input data and the user identification data. The user identification data is a user identifier. For example, the user identification data may be a store code. For example, the user identification data may be a business code of a business that operates multiple stores. In other words, multiple users may use the same user identification data.

[0029] The registration unit 30B is configured to register an app by an app provider. The registration unit 30B may be configured to register an app by an administrator or other agent of the information processing device 11. The registration unit 30B may register an app from the provision server 12. The registration unit 30B may register a contract form for the app along with the registration of the app.

[0030] The usage request acquisition unit 30C is configured to acquire a usage request for an app designated by a user. Hereinafter, an app designated by a user may be referred to as a designated app. The designated app is an example of a designated application. The usage request acquisition unit 30C may acquire the usage request for the designated app from the payment terminal device 18. The method for making a usage request for the designated app will be described in detail below.

[0031] The use of the designated app may include launching the designated app. The use of the designated app may include use of all or some of the functions of the designated app. The use of the designated app may include use of all or some of the functions of the designated app after launching the designated app.

[0032] The installation of the designated app is a prerequisite for launching the designated app and using all or some of the functions of the designated app, and may be included in the use of the designated app. The purchase of the designated app is a prerequisite for launching the designated app and using all or some of the functions of the designated app, and may be included in the use of the designated app.

[0033] In this way, the usage request may include a request to launch the designated app. The usage request may include a request to use all or some of the functions of the designated app. The usage request may include a request to install the designated app. The usage request may include a request to purchase the designated app.

[0034] Application identification data acquisition unit 30D is configured to acquire application identification data. Application identification data is an identifier of an application. Hereinafter, the application identification data of a designated application may be referred to as designated application identification data. Application identification data acquisition unit 30D may acquire the designated application identification data from payment terminal device 18.

[0035] Terminal identification data acquisition unit 30E is configured to acquire terminal identification data. Terminal identification data is an identifier of payment terminal device 18. Terminal identification data may be data assigned to payment terminal device 18 by an administrator of information processing device 11. Terminal identification data is data unique to payment terminal device 18. Terminal identification data acquisition unit 30E may acquire terminal identification data from payment terminal device 18.

[0036] The contract status acquisition unit 30F is configured to acquire a contract status for the user's use of the application. The contract status acquisition unit 30F may acquire a contract status corresponding to the user identification data and the designated application identification data. The contract status acquisition unit 30F may acquire a contract status corresponding to the user identification data, the designated application identification data, and the terminal identification data.

[0037] The usage authority determination unit 30G is configured to determine the usage authority of an app. The usage authority may include installation authority to install an app. The usage authority may include authority to launch an app. The usage authority may include authority to use all or some of the functions of an app. The usage authority determination unit 30G may determine the usage authority of a designated app based on a contract status corresponding to the user identification data and the designated app identification data. The usage authority determination unit 30G may determine the usage authority of a designated app based on a contract status corresponding to the user identification data, the designated app identification data, and the terminal identification data. The contract status includes whether or not a contract exists.

[0038] The usage control unit 30H is configured to control the use of the designated app. Specifically, the usage control unit 30H controls the purchase of the designated app, the installation of the designated app, the launch of the designated app, and the use of all or some of the functions of the designated app. The usage control unit 30H is configured to allow the use of the app when it is determined that the user has permission to use the app. The usage control unit 30H is configured to restrict the use of the app when it is determined that the user does not have permission to use the app. Control over the use of the designated app will be described in detail below.

[0039] The display control unit 30I is configured to display an image on the payment terminal device 18. The display control unit 30I may cause the payment terminal device 18 to display a purchase screen 24C shown in FIG. 13. The purchase screen 24C is a screen related to a new contract for the designated app or an update of the contract status of the designated app. The display control unit 30I may cause the payment terminal device 18 to display an installation screen 24D shown in FIG. 13. The installation screen 24D is a screen related to the installation of the designated app. The display control unit 30I may cause the payment terminal device 18 to display a startup screen 24E shown in FIG. 14. The startup screen is a screen related to the startup of the designated app. The screen related to the use of the designated app will be described in detail below.

[0040] Contract status providing unit 30J provides various data to a user in response to a request from the user. When contract status providing unit 30J receives a request from a user to view the contract status, it may provide the user with the contract status corresponding to the user identification data. When contract status providing unit 30J receives a request from a user to view the contract status, it may provide the user with the contract status of all payment terminal devices 18 corresponding to the user identification data.

[0041] <Contract type and contract status> As shown in FIG. 4, the contract type of an app indicates a contract fee for using the app. The contract type of an app may be set in response to an app registration request from an app provider. The contract type of an app includes a free contract type and a paid contract type.

[0042] The free contract format is a contract format in which the right to use the app is free of charge. The free contract format is a contract based on usage identification data and device identification data. Apps with a free contract format may be referred to as free apps.

[0043] The paid contract type is a contract type in which the right to use an app is paid for. An app in the paid contract type may be referred to as a paid app. The paid contract type may include a one-time payment contract type and a recurring payment contract type.

[0044] The one-time payment contract format is a paid contract format that allows for continuous use with a one-time payment. More specifically, the one-time payment contract format is a paid contract format that allows for continuous use with a one-time payment fee, provided the app provider continues to provide the app. The one-time payment contract format is a paid contract format that allows for continuous use with a one-time payment fee, provided the service is not terminated due to fraudulent use or violation of terms by the user. In this way, the one-time payment contract format is a paid contract format with no set usage period. Apps that use a one-time payment contract format are sometimes referred to as one-time payment apps.

[0045] A recurring payment contract is a paid contract with a set usage period. A recurring payment contract is a paid contract in which the app is purchased continuously for each usage period. More specifically, a recurring payment contract is a paid contract in which the app can be used continuously for the usage period by paying a usage fee for each usage period, provided that the app provider continues to provide the app during the usage period. A recurring payment contract is a paid contract in which the app can be used continuously for the usage period by paying a contract fee for each usage period, provided that the app is not terminated due to fraudulent use or violation of the terms and conditions by the user during the usage period. In other words, a recurring payment contract is a contract in which the app is continuously used for each usage period, provided that payments for app use are made normally. Apps under a recurring payment contract are sometimes referred to as recurring payment apps.

[0046] The contract status of an app may include a contract type and a contract period. The contract status of an app may include a contract status where a contract exists and a contract status where a contract does not exist. The contract status of an app may include an invalid contract status where the user does not have permission to use the specified app and an valid contract status where the user has permission to use the specified app. The valid contract status may include an individual valid contract status and a collective valid contract status.

[0047] The individual valid contract status is the contract status for free contracts and paid contracts. The individual valid contract status is a contract for each usage identification data and terminal identification data. The individual valid contract status is a contract status in which a user individually purchases an app from payment terminal device 18 via payment terminal device 18.

[0048] The collective valid contract status is a contract status in a paid contract format. The collective valid contract status is a contract based on usage identification data rather than terminal identification data. In other words, the collective valid contract status is a contract status in which it is determined that the user has permission to use the specified app for multiple payment terminal devices 18 based on the user identification data, regardless of the terminal identification data.

[0049] The collective valid contract status may be a contract status in which a user purchases apps collectively from multiple payment terminal devices 18 by applying to an administrator of information processing device 11, without going through payment terminal device 18. The collective valid contract status may be a contract status in which a user purchases apps collectively from multiple payment terminal devices 18 by applying to an application provider, without going through payment terminal device 18.

[0050] In this way, if a user signs a contract under the collectively valid contract status, the user can use the app on the payment terminal device 18 of their choice. The collectively valid contract status is a contract that is renewed for each usage period, provided that payment for the use of the app is properly completed. Apps in the collectively valid contract status may be referred to as collectively paid apps.

[0051] An invalid contract status is a contract status when the contract type is a paid contract type. An invalid contract status may also be a situation where the contract period has expired in the case of an individual valid contract status or a lump-sum valid contract status. An invalid contract status may include, for example, a situation where a contract (purchase) has not been made, a situation where the contract period has expired, a contract termination by the user, suspension of provision of the app due to the user's fraudulent use or violation of the terms of use, or suspension of provision of the app by the app provider. Thus, an invalid contract status may be a situation where the contract type is a paid contract type and the app has been purchased but the contract has become invalid, or a situation where the contract type is a paid contract type and the app has not been purchased.

[0052] <Application Management Database 31A> 5, an application management database 31A is stored in the storage unit 31. The application management database 31A manages applications provided to users by application providers. The application management database 31A includes at least one application management data 41.

[0053] In the application management data 41, application identification data, provider identification data, provider communication destination, contract type, usage fee, and application version are associated with each other. In the diagram, the identification data may be indicated as "ID." The provider identification data is an identifier of the application provider. The usage fee is the payment amount for using the application. The provider communication destination is data for communicating with the application provider. The application management data 41 may not include all of the application identification data, provider identification data, provider communication destination, contract type, usage fee, and application version, and may include other data.

[0054] The application management database 31A can manage multiple applications, which may include applications related to payment and applications not related to payment. The multiple apps may or may not include a device management app. The multiple apps may include a POS (Point of Sale) app. The multiple apps may include at least one of a reward management app, a sales management app, an inventory management app, a customer management app, a cash register linkage app, an accounting software linkage app, and a time and attendance management app.

[0055] The terminal management app is an app for managing data related to users who are logged in to payment terminal device 18. In payment terminal device 18, the terminal management app can switch data related to users. The data related to users is user identification data, but is not limited to this and may be, for example, a user account. The terminal management app manages apps installed in payment terminal device 18. The terminal management app may be an app for accessing information processing device 11 from payment terminal device 18. The terminal management app is available when it is determined that there is usage authority corresponding to the user identification data. The terminal management app may be a free app. The terminal management app may be pre-installed in payment terminal device 18. The terminal management app may also be an app required for payment terminal device 18 to make payment for a transaction object.

[0056] The reward management app is an app for providing rewards to purchasers. The rewards may be points or coupons. The points and coupons may be used in e-commerce services, such as travel reservations.

[0057] In this way, the plurality of applications may include a first application and a second application. The first application and the second application may be combined in any combination. An example of the first application may be a device management application.

[0058] <Contract performance database 31B> As shown in FIG. 6, the memory unit 31 stores a contract history database 31B. The contract history database 31B manages the contract history of the app by the user. The contract history may include the start of the contract and the ongoing renewal of the contract. The contract history database 31B includes at least one contract history data 42.

[0059] In the contract performance data 42, contract management identification data, user identification data, application identification data, contract type, contract content, and terminal identification data are associated with each other. The contract management identification data may be associated with a contract date and time (not shown). The contract management identification data is an identifier for the contract performance. The contract content indicates whether or not a contract has been concluded. The contract performance data 42 may not include some of the contract management identification data, user identification data, application identification data, contract type, contract content, and terminal identification data, and may include data other than these.

[0060] <User Management Database 31C> 7, a user management database 31C is stored in the storage unit 31. The user management database 31C manages data related to users and data related to apps used by the users. The user management database 31C includes at least one user data 43.

[0061] In the user data 43, user identification data, a password, and a payment method are associated with each other. In the user data 43, at least one piece of application identification data is associated with the user identification data. In the user data 43, application identification data, a contract status, and terminal identification data are associated with each other.

[0062] The payment method is a method by which a user makes a payment to use an app. For example, the payment method may include credit card payment, cash payment, and bank account payment. The payment method may be managed for each application identification data.

[0063] The application identification data associated with the user identification data is an identifier indicating an application that has been installed after being purchased by the user. Therefore, in the user management database 31C, the application identification data associated with the user identification data can be recognized as the identifier of the installed application.

[0064] The user data 43 may not include all of the user identification data, password, payment method, application identification data, contract status, and terminal identification data, or may include other data. The user management database 31C may be managed as the same database as the contract performance database 31B. The user management database 31C may include payment identification data separate from the user identification data.

[0065] <App registration process> The application registration process will now be described with reference to Fig. 8. The application registration process is executed by the control unit 30 at predetermined intervals.

[0066] As shown in FIG. 8 , in step S10, the control unit 30 determines whether an application registration request has been input from the provider server 12. The application registration request is input from the provider server 12 to the information processing device 11 in response to an instruction from the application provider. The application registration request includes data requesting registration of the application management data 41. The application registration request may include provider identification data, application installation data, a contract type, a usage fee, and a version. The application registration request may be input in response to an instruction from an administrator of the information processing device 11, instead of an instruction from the application provider. In this case, the application registration request is input to the information processing device 11 in response to an application from the application provider to the administrator of the information processing device 11 and in response to an instruction from the administrator of the information processing device 11.

[0067] If the control unit 30 determines that an application registration request has not been input, the control unit 30 ends the application registration process. If the control unit 30 determines that an application registration request has been input, the control unit 30 proceeds to step S11.

[0068] In step S11, the control unit 30 executes an application management data registration process. In this process, the control unit 30 generates application identification data. If the application registration request already includes application identification data, the control unit 30 does not need to generate application identification data. The control unit 30 acquires the provider identification data, application installation data, contract type, usage fee, and version included in the application registration request. The control unit 30 generates application management data 41 based on the application identification data, provider identification data, application installation data, contract type, usage fee, and version. The control unit 30 may read a provider communication destination corresponding to the provider identification data from the storage unit 31 and generate the application management data 41. The control unit 30 registers the generated application management data 41 in the application management database 31A.

[0069] <Data provision control process> Next, the data provision control process will be described with reference to Fig. 9. The data provision control process is a process executed by the control unit 30 at predetermined intervals.

[0070] As shown in FIG. 9, in step S20, control unit 30 determines whether a viewing request has been input. The viewing request may be input from payment terminal device 18, or may be input from a user terminal device different from payment terminal device 18. The viewing request includes data indicating a request to view user data 43 corresponding to user identification data. The viewing request may also include data indicating a request to view the contract status corresponding to the user identification data. The viewing request may also include user identification data and a password.

[0071] If the control unit 30 determines that a view request has not been input, it ends the data provision control process. If the control unit 30 determines that a view request has been input, it moves the process to step S21.

[0072] In step S21, the control unit 30 executes a user identification data acquisition process. In this process, the control unit 30 acquires the user identification data included in the browsing request. The control unit 30 acquires the password included in the browsing request. The control unit 30 may refer to the user management database 31C and authenticate the user based on the user identification data and password. If the control unit 30 has successfully authenticated the user, the control unit 30 may proceed to step S22. If the control unit 30 has not successfully authenticated the user, the control unit 30 may end the data provision control process without executing steps S22 and S23.

[0073] In step S22, the control unit 30 executes a user data acquisition process, in which the control unit 30 acquires the user data 43 from the user management database 31C.

[0074] In step S23, control unit 30 executes a user data provision process. In this process, control unit 30 transmits user data 43 to payment terminal device 18 or the user terminal device that output the viewing request. This allows control unit 30 to provide user data 43 to the user. In other words, when control unit 30 receives a request to view the contract status from the user, it provides the user with the contract status and terminal identification data corresponding to the user identification data.

[0075] When multiple payment terminal devices 18 are associated with the user identification data, control unit 30 may provide the contract status of all associated payment terminal devices 18. In this case, control unit 30 provides the contract status for each terminal identification data, but may also provide the contract status for each terminal number or terminal name.

[0076] As a specific example, we will explain a case where multiple payment terminal devices 18 are associated with the same user identification data, and a view request is output to information processing device 11 from one of the multiple payment terminal devices 18, first payment terminal device 18A. In this case, control unit 30 transmits the contract statuses of not only first payment terminal device 18A but also multiple payment terminal devices 18, including other payment terminal devices 18 associated with the same user identification data, to first payment terminal device 18A. In other words, first payment terminal device 18A allows the user to check the contract statuses of all payment terminal devices 18 associated with the user identification data. This improves convenience regarding payment of transaction objects.

[0077] <Usage Determination Control Process> Next, the use determination control process will be described with reference to Figures 10 and 11. The use determination control process is a process executed by the control unit 30 at predetermined intervals. In this case, the use determination control process will be described on the assumption that user authentication has been performed normally, but is not limited to this.

[0078] As shown in FIG. 10 , in step S30, the control unit 30 determines whether a designated app request has been input from the payment terminal device 18. The designated app request indicates a request for data related to the usage authority of the designated app designated by the user. The data related to the usage authority of the designated app is data according to the contract status of the designated app, and includes data related to the purchase, installation, and launch of the designated app. The designated app request may include user identification data, designated app identification data, and terminal identification data. In this embodiment, when the user performs an operation to designate a designated app while the app list screen 24B shown in FIG. 13 is displayed on the terminal display unit 24 of the payment terminal device 18, the terminal control unit 20 transmits the designated app request to the information processing device 11.

[0079] If the control unit 30 determines that a designated application request has not been input, the control unit 30 ends the use determination control process. If the control unit 30 determines that a designated application request has been input, the control unit 30 proceeds to step S31.

[0080] In step S31, control unit 30 executes a user identification data acquisition process. In this process, control unit 30 acquires the user identification data included in the designated application request. In this manner, control unit 30 acquires the user identification data from payment terminal device 18.

[0081] In step S32, control unit 30 executes a designated application identification data acquisition process. In this process, control unit 30 acquires the designated application identification data included in the designated application request. In this manner, control unit 30 acquires the designated application identification data of the multiple applications from payment terminal device 18.

[0082] In step S33, control unit 30 executes a terminal identification data acquisition process. In this process, control unit 30 acquires the terminal identification data included in the designated application request. In this manner, control unit 30 acquires the terminal identification data from payment terminal device 18. Control unit 30 may execute steps S31 to S33 in any order, or may execute them as the same process.

[0083] In step S34, the control unit 30 executes a contract status acquisition process. In this process, the control unit 30 reads out the contract status corresponding to the user identification data and the designated application identification data from the user management database 31C. As a result, the control unit 30 acquires the contract status corresponding to the user identification data and the designated application identification data.

[0084] In step S35, the control unit 30 executes a data matching process. In this process, the control unit 30 matches the user data 43 corresponding to the user identification data included in the designated application request with the designated application identification data included in the designated application request. The control unit 30 may also match the user data 43 corresponding to the user identification data included in the designated application request with the designated application identification data and terminal identification data included in the designated application request.

[0085] In detail, the control unit 30 reads out the contract status corresponding to the designated application identification data from the user data 43 corresponding to the user identification data. When the contract status is a collective valid contract status, the control unit 30 compares the user data 43 corresponding to the user identification data included in the designated application request with the designated application identification data included in the designated application request, regardless of the terminal identification data. In this way, when the contract status is a collective valid contract status, the control unit 30 does not compare the terminal identification data. When the contract status is not a collective valid contract status, the control unit 30 compares the user data 43 corresponding to the user identification data included in the designated application request with the designated application identification data and terminal identification data included in the designated application request.

[0086] In step S36, the control unit 30 determines whether the designated application identification data is in the application identification data corresponding to the user identification data. In particular, if the contract status is a collective valid contract status, the control unit 30 determines whether the designated application identification data is in the application identification data corresponding to the user identification data. If the contract status is not a collective valid contract status, the control unit 30 determines whether the designated application identification data is in the application identification data corresponding to the user identification data and the terminal identification data.

[0087] If the control unit 30 determines that the designated application identification data is not in the application identification data corresponding to the user identification data, the control unit 30 proceeds to step S38. If the control unit 30 determines that the designated application identification data is in the application identification data corresponding to the user identification data, the control unit 30 proceeds to step S37.

[0088] In step S37, the control unit 30 determines whether the contract status corresponding to the user identification data and the designated application identification data is a valid contract status. If the control unit 30 determines that the contract status is a valid contract status, the control unit 30 proceeds to step S45 in Fig. 11. If the control unit 30 determines that the contract status is not a valid contract status, the control unit 30 proceeds to step S38.

[0089] In step S38, the control unit 30 determines whether the app corresponding to the designated app identification data is a free app. If the control unit 30 determines that the app corresponding to the designated app identification data is a free app, the control unit 30 proceeds to step S43 in Fig. 11 without displaying a purchase screen 24C (described later). If the control unit 30 determines that the app corresponding to the designated app identification data is not a free app, the control unit 30 proceeds to step S39. The control unit 30 may execute step S38 before executing step S34.

[0090] In step S39, control unit 30 executes a purchase screen display control process. In this process, control unit 30 transmits a display instruction to payment terminal device 18 that output the designated app request to display purchase screen 24C. The display instruction for purchase screen 24C is data for displaying purchase screen 24C on terminal display unit 24. Purchase screen 24C is a screen for purchasing authorization to use the designated app. In this way, when control unit 30 receives a designated app request and determines that the user does not have authorization to use the designated app, control unit 30 causes payment terminal device 18 to display purchase screen 24C.

[0091] In step S40, the control unit 30 determines whether a purchase request has been input from the payment terminal device 18. The purchase request indicates a purchase related to the use of an app. The purchase request may include user identification data, a password, designated app identification data, and terminal identification data. In this embodiment, when the user performs an operation to select the purchase button while the purchase screen 24C shown in FIG. 13 is displayed on the terminal display unit 24 of the payment terminal device 18, the terminal control unit 20 transmits the purchase request to the information processing device 11.

[0092] If the control unit 30 determines that a purchase request has not been input from the payment terminal device 18, it again proceeds to step S40. If the control unit 30 determines that a purchase request has been input from the payment terminal device 18, it proceeds to step S41. If a purchase request has not been input from the payment terminal device 18 until a predetermined time has elapsed, the control unit 30 may end the usage determination control process. The control unit 30 may also end the usage determination control process in response to a predetermined operation by the user. The predetermined operation may be, for example, an operation to close the purchase screen 24C.

[0093] In step S41, the control unit 30 executes a payment control process. In this process, the control unit 30 authenticates the user based on the user identification data and password included in the purchase request. If the user authentication is successful, the control unit 30 performs payment using the payment method corresponding to the specified application identification data.

[0094] In step S42, the control unit 30 determines whether the payment was completed normally. If the control unit 30 determines that the payment was not completed normally, it ends the use determination control process. If the control unit 30 determines that the payment was not completed normally, it may cause the payment terminal device 18 to display an image that notifies the user of an error and encourages the user to make a purchase. If the control unit 30 determines that the payment was completed normally, it proceeds to step S43 in FIG. 11.

[0095] As shown in FIG. 11, in step S43, the control unit 30 executes a contract performance data registration process. In this process, the control unit 30 generates contract management identification data. The control unit 30 acquires a contract format corresponding to the designated application identification data included in the designated application request or purchase request. The control unit 30 generates contract details indicating that a contract has been concluded. The control unit 30 generates contract performance data 42 based on the user identification data, designated application identification data, and terminal identification data included in the designated application request or purchase request, the generated contract management identification data and contract details, and the acquired contract format. The control unit 30 registers the generated contract performance data 42 in the contract performance database 31B.

[0096] In step S44, the control unit 30 executes a user data update process. In this process, the control unit 30 acquires a contract period corresponding to the contract type. For example, if the contract type is a one-month recurring payment contract, the control unit 30 acquires the period corresponding to that contract type as the contract period. The control unit 30 generates user data 43 based on the user identification data, designated application identification data, and terminal identification data included in the payment request, and the acquired contract type and contract period. The control unit 30 registers the generated user data 43 in the user management database 31C.

[0097] In step S45, the control unit 30 determines whether the designated application is already installed. If the application identification data corresponding to the user identification data includes the designated application identification data and the application is in an invalid contract state, the control unit 30 determines that the application is already installed. If the control unit 30 determines that the designated application is already installed, the control unit 30 proceeds to step S50. If the control unit 30 determines that the designated application is not already installed, the control unit 30 proceeds to step S46.

[0098] In step S46, control unit 30 executes an installation screen display control process. In this process, control unit 30 transmits a display instruction to payment terminal device 18 that output the designated app request to display installation screen 24D. The display instruction for installation screen 24D is data for displaying installation screen 24D on terminal display unit 24. Installation screen 24D is a screen for installing the designated app. In this way, control unit 30 causes payment terminal device 18 to display installation screen 24D for the designated app when the designated app is not already installed.

[0099] In step S47, the control unit 30 determines whether an installation request has been input from the payment terminal device 18. The installation request indicates that the designated app should be installed. The installation request may include user identification data, designated app identification data, and terminal identification data. In this embodiment, when the user performs an operation to select the install button while the installation screen 24D shown in FIG. 13 is displayed on the terminal display unit 24 of the payment terminal device 18, the terminal control unit 20 sends the installation request to the information processing device 11.

[0100] If the control unit 30 determines that an installation request has not been input from the payment terminal device 18, it again proceeds to step S47. If the control unit 30 determines that an installation request has been input from the payment terminal device 18, it proceeds to step S48. If an installation request has not been input from the payment terminal device 18 until a predetermined time has elapsed, the control unit 30 may end the usage determination control process. The control unit 30 may end the usage determination control process in response to a predetermined operation by the user. The predetermined operation may be, for example, an operation to close the installation screen 24D.

[0101] In step S48, control unit 30 executes an installation permission process, in which control unit 30 grants payment terminal device 18, to which the installation request has been output, permission to install the designated application.

[0102] In step S49, control unit 30 executes an installation control process. In this process, control unit 30 transmits installation data corresponding to the designated app to payment terminal device 18, which has output the installation request. As a result, payment terminal device 18 receives the installation data corresponding to the designated app and installs the designated app.

[0103] In step S50, control unit 30 executes a startup screen display control process. In this process, control unit 30 transmits a display instruction to payment terminal device 18, which has output the designated app request, to display startup screen 24E. The display instruction for startup screen 24E is data for displaying startup screen 24E on terminal display unit 24. Startup screen 24E is a screen for launching the designated app. In this way, control unit 30 causes payment terminal device 18 to display startup screen 24E of the designated app when the designated app has been installed.

[0104] In step S51, control unit 30 determines whether a startup request has been input from payment terminal device 18. The startup request indicates that a designated app should be started. The startup request may include user identification data, designated app identification data, and terminal identification data. In this embodiment, when a user performs an operation to designate a start button while startup screen 24E is displayed on terminal display unit 24 of payment terminal device 18, terminal control unit 20 sends a startup request to information processing device 11.

[0105] If the control unit 30 determines that a startup request has not been input from the payment terminal device 18, it again proceeds to step S51. If the control unit 30 determines that a startup request has been input from the payment terminal device 18, it proceeds to step S52. If a startup request has not been input from the payment terminal device 18 until a predetermined time has elapsed, the control unit 30 may end the use determination control process. The control unit 30 may end the use determination control process in response to a predetermined operation by the user. The predetermined operation may be, for example, an operation to close the startup screen 24E.

[0106] In step S52, control unit 30 executes a start permission process, in which control unit 30 grants the start authority of the designated application to payment terminal device 18 to which the start request has been output.

[0107] In step S53, control unit 30 executes a startup control process. In this process, control unit 30 transmits startup permission data to payment terminal device 18, to which the startup request was output. As a result, payment terminal device 18 receives the startup permission data corresponding to the designated app and starts the designated app.

[0108] In this way, the control unit 30 determines the use authority of the designated application based on the contract status corresponding to the user identification data and the designated application identification data. In particular, the control unit 30 determines that the use authority exists when the contract status corresponding to the user identification data and the designated application is a valid contract status. The control unit 30 determines that the use authority does not exist when the contract status corresponding to the user identification data and the designated application is an invalid contract status.

[0109] For example, when the control unit 30 determines that the contract status is not a lump-sum paid contract status, it determines the use authority of the designated app based on the contract status corresponding to the user identification data, the designated app identification data, and the terminal identification data. For example, when the control unit 30 determines that the contract status is a lump-sum paid contract status, it determines the use authority of the designated app based on the contract status corresponding to the user identification data and the designated app identification data, regardless of the terminal identification data.

[0110] When the control unit 30 acquires a request to use the designated app and determines that the user has permission to use the designated app, it allows the user to install the designated app, launch the designated app, and use the functions of the designated app. When the control unit 30 acquires a request to use the designated app and determines that the user does not have permission to use the designated app, it restricts the user from installing the designated app, launching the designated app, and using the functions of the designated app. The functions of the designated app are functions within the designated app that can be used after the designated app is launched, and are separate from the installation function and launch function, but may include the installation function and launch function.

[0111] A case where multiple user identification data are used in the same payment terminal device 18 will be described. The user identification data includes first user identification data of a first user and second user identification data of a second user. In such a case, the control unit 30 determines the use authority for the designated app based on the first user identification data and the terminal identification data. The control unit 30 determines the use authority for the designated app based on the second user identification data and the terminal identification data.

[0112] In this way, multiple user identification data can be used, although multiple user identification data cannot be used to simultaneously log in to the same payment terminal device 18. This improves the versatility of payment terminal device 18.

[0113] On the other hand, if the app is installed on the same payment terminal device 18, the authorization to use the app is determined based on the user identification data. For example, if the contract status of the app based on the first user identification data is a valid contract status, control unit 30 determines that the user has authorization to use the app based on the first user identification data. If the contract status of the app based on the second user identification data is not a valid contract status, control unit 30 determines that the user does not have authorization to use the app based on the second user identification data.

[0114] Specifically, when control unit 30 receives from payment terminal device 18 a first use request for the designated app that includes designated app identification data, terminal identification data, and first user identification data, and the contract status is a valid contract status, control unit 30 determines that the user has permission to use the designated app. When control unit 30 receives from payment terminal device 18 a second use request for the designated app that includes the same designated app identification data and terminal identification data as the first use request, and second user identification data, and the contract status is an invalid contract status, control unit 30 determines that the user does not have permission to use the designated app.

[0115] Next, a case where one user identification data is used in multiple payment terminal devices 18 will be described. In such a case, the control unit 30 determines the use authority of the designated app based on the user identification data and the first terminal identification data. The control unit 30 determines the use authority of the designated app based on the user identification data and the second terminal identification data. In particular, when the contract status is a collective valid contract status, the control unit 30 determines the use authority of the designated app based on the user identification data, regardless of the terminal identification data.

[0116] In this way, if user identification data is associated with multiple terminal identification data, the same user identification data can be used in multiple payment terminal devices 18. In this case, the same user identification data can be used in multiple payment terminal devices 18 to simultaneously use the app.

[0117] In this embodiment, if the user identification data and the terminal identification data are associated with a plurality of applications, the control unit 30 can simultaneously use a plurality of applications corresponding to the user identification data and the terminal identification data.

[0118] In payment terminal device 18, when a user inputs user identification data and a password, terminal control unit 20 can retain the user identification data and the password for a predetermined period of time. For example, after starting up payment terminal device 18 itself, when a user inputs user identification data and a password, terminal control unit 20 can authenticate the user and allow the user to log in. Hereinafter, this type of authentication may be referred to as login authentication.

[0119] The terminal management app is installed in payment terminal device 18 by default. Therefore, terminal control unit 20 causes the terminal management app to store the user identification data of the user who has been authenticated to log in to payment terminal device 18. As a result, terminal control unit 20 can control the situation so that the user is logged in to the terminal management app based on the user identification data of the authenticated user through login authentication to payment terminal device 18. Note that the terminal management app may perform login authentication separate from login authentication to payment terminal device 18. In other words, login authentication to the terminal management app includes login authentication to payment terminal device 18, but may also include login authentication to the terminal management app.

[0120] When a user requests the use of another application through operation while logged in to the terminal management application, the terminal control unit 20 transmits the stored user identification data, the application identification data of the other application, and the terminal identification data to the information processing device 11.

[0121] In such a case, when the control unit 30 in the information processing device 11 executes the use determination control process and the use authority for the other application is permitted, the terminal control unit 20 can log in to the other application and start the other application.

[0122] In this way, the control unit 30 logs in to the terminal management app based on the user identification data. When the control unit 30 acquires the separate app identification data as the designated app identification data, the control unit 30 determines the usage authority for the separate app based on the contract status corresponding to the user identification data of the user logged in to the terminal management app and the separate app identification data. In this way, the user does not need to input user identification data for each app, thereby improving user convenience. The terminal management app corresponds to an example of a first app, and the separate app corresponds to an example of a second app.

[0123] <Contract renewal control process> Next, the contract renewal control process will be described with reference to Fig. 12. The contract renewal control process is a process executed by the control unit 30 at predetermined intervals.

[0124] As shown in Fig. 12, in step S60, the control unit 30 determines whether the confirmation condition is met. The confirmation condition may be met at a predetermined time. If the control unit 30 determines that the confirmation condition is not met, it terminates the contract renewal control process. If the control unit 30 determines that the confirmation condition is met, it proceeds to step S61.

[0125] In step S61, the control unit 30 executes a user data acquisition process. In this process, the control unit 30 acquires user identification data. Specifically, the control unit 30 acquires the contract status corresponding to the user identification data.

[0126] In step S62, the control unit 30 determines whether the contract type included in the contract status is a recurring payment contract type. If the control unit 30 determines that the contract type is not a recurring payment contract type, it terminates the contract renewal control process. If the control unit 30 determines that the contract type is a recurring payment contract type, it proceeds to step S63.

[0127] In step S63, the control unit 30 determines whether the contract period included in the contract status has expired. If the control unit 30 determines that the contract period has not expired, it terminates the contract renewal control process. If the control unit 30 determines that the contract period has expired, it proceeds to step S41.

[0128] In step S41, the control unit 30 executes a payment control process. In step S42, if the control unit 30 determines that the payment has been completed successfully, the process proceeds to step S43. If the control unit 30 determines that the payment has not been completed successfully, the control unit 30 terminates the contract renewal control process. If the control unit 30 determines that the payment has not been completed successfully, the control unit 30 may display an error notification on the terminal display unit 24, prompting the user to purchase the specified app.

[0129] In step S43, the control unit 30 registers the contract history data 42 for automatically extending the contract period of the app in the contract history database 31 B. In step S44, the control unit 30 registers the user data 43 for automatically extending the contract period of the app in the user management database 31 C.

[0130] In this way, when the control unit 30 determines that the contract period corresponding to an app included in the user data 43 has expired, it controls to automatically extend the contract period if payment for use of the app is normally completed. When the control unit 30 determines that the contract period corresponding to an app included in the user data 43 has expired, it does not automatically extend the contract period unless payment for use of the app is normally completed. In this way, the control unit 30 controls to maintain an invalid contract status in which there is no authority to use the app.

[0131] In this embodiment, if payment for use of an app is not completed successfully, control unit 30 will not uninstall the app for which the user does not have permission to use from payment terminal device 18. This reduces the control load on control unit 30.

[0132] In this embodiment, if payment for the use of an app is not completed successfully, the control unit 30 does not perform control to hide apps that the user does not have permission to use on the payment terminal device 18. This allows the user to recognize that the app has already been installed, reducing the likelihood that the user will install it again. The control unit 30 may execute the contract renewal control process for all user identification data.

[0133] <Display screen of payment terminal device 18> As shown in FIG. 13, login screen 24A may be displayed on terminal display unit 24 of payment terminal device 18. Login screen 24A is displayed on terminal display unit 24 when payment terminal device 18 is started and the user logs in to payment terminal device 18. Login screen 24A may also be displayed on terminal display unit 24 when an app is used with payment terminal device 18. Login screen 24A displays an input field for user identification data and an input field for a password. When the user operates the login button after entering the user identification data and password, the user logs in to payment terminal device 18.

[0134] When login to payment terminal device 18 is successful, application list screen 24B is displayed on terminal display unit 24. Application list screen 24B may be displayed within the terminal management app or may be displayed in an app separate from the terminal management app. Application list screen 24B displays the icons, names, descriptions, and contract types of applications that can be installed on payment terminal device 18.

[0135] When an app icon is operated, if the contract status of the app is invalid and the user does not have usage authority, a purchase screen 24C is displayed on the terminal display unit 24. Detailed data of the app is displayed on the purchase screen 24C. A purchase button is displayed on the purchase screen 24C. In this way, the purchase screen 24C includes a purchase image related to the purchase of the specified app. In other words, the purchase image is displayed on the terminal display unit 24. When the purchase button is operated, payment for the usage authority of the app is made.

[0136] When payment for the authorization to use the app has been successfully completed and the app is not yet installed in payment terminal device 18, an installation screen 24D is displayed on terminal display unit 24. Installation screen 24D is a screen for installing the app for which payment has been successfully completed. An install button is displayed on installation screen 24D. When the install button is operated, the app is installed. In this way, installation screen 24D includes an installation image related to the installation of the specified app. In other words, the installation image is displayed on terminal display unit 24.

[0137] On the other hand, if payment for the authorization to use the app has been successfully completed and the app is already installed in payment terminal device 18, then, for example, a start-up screen 24E is displayed on terminal display unit 24 instead of installation screen 24D. Start-up screen 24E is a screen on which an operation for starting the designated app can be performed.

[0138] Note that installation of a designated app on payment terminal device 18 includes installation by another user. The following describes a case where a designated app has already been installed on payment terminal device 18 by a first user, and a second user who does not have usage authority for the same payment terminal device 18 successfully completes payment for usage authority for the designated app. In such a case, the second user can use the designated app installed by the first user, and there is no need to install the designated app twice. In this way, when multiple users use an app on the same payment terminal device 18, it is possible to avoid a situation where each user has to install the app separately. This improves the convenience of the app setup process.

[0139] In this embodiment, if the contract status of the app is a valid contract status and the user has usage authority, when the app icon is operated, the purchase screen 24C is not displayed on the terminal display unit 24. In this way, the purchase image is not displayed on the terminal display unit 24.

[0140] If the designated app is not installed in payment terminal device 18, installation screen 24D is displayed on terminal display unit 24, and the designated app can be used by installing it. On the other hand, if the designated app is installed in payment terminal device 18, installation screen 24D is not displayed on terminal display unit 24, and startup screen 24E is displayed, and the app can be used by starting it.

[0141] As shown in FIG. 14, the startup screen 24E is a screen for launching an application whose contract status is a valid contract status. A launch button is displayed on the startup screen 24E. When the launch button is operated, the application is launched. In this manner, the startup screen 24E includes a launch image related to the launch of the designated application. In other words, the launch image is displayed on the terminal display unit 24.

[0142] When a request to view the contract status is received from the user, a contract status management screen 24F is displayed on the terminal display unit 24. An image relating to the contract status of the app corresponding to the user identification data is displayed on the contract status management screen 24F. At least one piece of terminal identification data is displayed on the contract status management screen 24F. The terminal number or terminal name may be displayed on the contract status management screen 24F instead of the terminal identification data.

[0143] When the terminal identification data is operated, the terminal contract status management screen 24G is displayed. An image relating to the contract status of the application corresponding to the specified terminal identification data is displayed on the terminal contract status management screen 24G. In this way, an image relating to the contract status of the application corresponding to the user identification data is displayed on the terminal display unit 24 for each terminal identification data.

[0144] For example, a case will be described in which first payment terminal device 18A and second payment terminal device 18B correspond to the same user identification data. In this case, when a request to view the contract status is received from first payment terminal device 18A, first payment terminal device 18A displays contract status management screen 24F including the contract status of the app for first payment terminal device 18A and the contract status of the app for second payment terminal device 18B. Note that an identification image may be displayed for first payment terminal device 18A that has made the request to view the contract status, allowing it to be distinguished from other payment terminal devices 18. The identification image may be, for example, an image that reads "Current Terminal."

[0145] <Actions and Effects of the First Embodiment> The operation and effects of the first embodiment will be described. (1-1) The control unit 30 acquires the user identification data of the user using the payment terminal device 18 and the contract status corresponding to the designated application identification data specified by the user. The control unit 30 determines the authorization to use the designated application based on the contract status. Therefore, the authorization to use the designated application specified by the user can be determined based on the contract status of the designated application. This improves the convenience of payment for the transaction object.

[0146] (1-2) When control unit 30 acquires, as the designated application identification data, application identification data other than that of the terminal management application, it determines the authorization to use the application based on the contract status corresponding to the user identification data of the user logged in to the terminal management application and the application identification data. Therefore, by determining the authorization to use the application while the terminal management application is logged in to payment terminal device 18, it is possible to enable the application to be used on payment terminal device 18. This improves convenience regarding the payment of the transaction subject.

[0147] (1-3) Control unit 30 determines the authorization to use another app based on the user identification data, application identification data other than the terminal management app, and the contract status corresponding to the terminal identification data. Therefore, the authorization to use another app can be determined based on the terminal identification data of payment terminal device 18 as well. This improves convenience regarding payment of the transaction subject.

[0148] (1-4) If the control unit 30 determines based on the contract status that the user does not have permission to use an app other than the terminal management app, the control unit 30 restricts the launch of the other app and the use of functions in the other app. This makes it possible to control the launch and use of the other app depending on the contract status. This improves the convenience of payment for the transaction subject.

[0149] (1-5) When the contract status corresponding to the user identification data and the designated application identification data is a collective valid contract status, the control unit 30 determines that the user has the authority to use the designated application based on the contract status corresponding to the user identification data and the designated application identification data. Therefore, when the contract status is a collective valid contract status, the single user identification data can be used to determine the authority to use the designated application in each of multiple payment terminal devices 18. This improves convenience regarding payments for transaction objects.

[0150] (1-6) When the control unit 30 determines that the contract status of the designated app is not a collective valid contract status, it determines the launch authority of the designated app based on the contract status corresponding to the user identification data, the designated app identification data, and the terminal identification data. Therefore, when the contract status of the designated app is not a collective valid contract status, it is possible to determine the use authority of the designated app for each of multiple payment terminal devices 18 based on the user identification data and the terminal identification data. This improves convenience regarding payments for transaction objects.

[0151] (1-7) The control unit 30 permits the use of the designated app when it determines that the user has authorization to use the designated app based on the user identification data and the contract status of the designated app. Therefore, whether the contract status is a collective valid contract status can determine whether the designated app is associated with the payment terminal device 18. In this way, it is possible to provide diversity in the authorization to use the designated app. This can improve convenience in payment for the transaction object.

[0152] (1-8) If the contract status corresponding to the user identification data and the designated app is an invalid contract status, the control unit 30 determines that the user does not have permission to use the designated app. When the control unit 30 determines that the user does not have permission to use the designated app, it can cause the payment terminal device 18 to display a purchase screen 24C related to the purchase of permission to use the designated app. Therefore, displaying the purchase screen 24C can promote updating of the contract status corresponding to the permission to use the designated app. This can improve convenience regarding payment for the transaction object.

[0153] (1-9) The control unit 30 determines that the user has authorization to use the designated app when the contract status corresponding to the user identification data and the designated app identification data is a valid contract status. When the control unit 30 determines that the user has authorization to use the designated app, the control unit 30 allows the use of the designated app without displaying the purchase screen 24C. Therefore, when the contract status of the designated app is a valid contract status, the designated app can be used without displaying the purchase screen 24C. This improves convenience regarding payment for the transaction object.

[0154] (1-10) When control unit 30 receives a request from a user to view the contract status, it provides the user with the contract statuses of multiple payment terminal devices 18 corresponding to the user identification data. Therefore, by providing the user with the contract statuses of the apps of multiple payment terminal devices 18 as intended by the user, it is possible to provide the user with an environment in which it is easy to understand the contract status of the apps. This improves convenience regarding payments for transaction objects.

[0155] [Second embodiment] Next, a second embodiment will be described. In the following description, the same configuration as the already described embodiment will be omitted or simplified, and only the configuration different from the already described embodiment will be described. The first embodiment and the second embodiment can be implemented in combination with each other as long as there is no technical contradiction.

[0156] In the second embodiment, the contract type may include a direct payment contract type and an indirect payment contract type. In the direct payment contract type, the information processing device 11 performs payment directly, as in the first embodiment, but payment may also be made with an external server via the information processing device 11. In other words, the user may perform payment directly with the administrator of the information processing device 11 or its agent. In the indirect payment contract type, the information processing device 11 is not involved in the payment. In the indirect payment contract type, the providing server 12, which is different from the information processing device 11, performs payment directly, but payment may also be made with an external server via the providing server 12. In other words, the user may perform payment directly with the app provider or its agent, without going through the administrator of the information processing device 11 or its agent. For example, the first providing server 12A may provide an app using the direct payment contract type. The second providing server 12B may provide an app using the indirect payment contract type.

[0157] <Payment control processing> 10, the control unit 30 determines whether the contract format of the designated application is the indirect payment contract format. If the control unit 30 determines that the contract format of the designated application is the indirect payment contract format, the control unit 30 inquires about the payment status of the second provision server 12B.

[0158] The information processing device 11 acquires the status of payment related to the use of the designated app through communication with the second provision server 12B. When the payment is completed successfully, the second provision server 12B transmits payment completion data to the information processing device 11. The payment completion data indicates that the payment has been completed successfully. The payment completion data includes user identification data, designated app identification data, and terminal identification data, but may also include other data that can identify these data. Note that the inquiry and acquisition of the status of payment related to the use of the designated app may be performed manually. In this case, the payment completion data may be input into the information processing device 11 by an administrator of the information processing device 11.

[0159] In step S42, when the payment completion data is input from the second providing server 12B, the control unit 30 determines that the payment has been completed normally. <Actions and Effects of the Second Embodiment> The operation and effects of the second embodiment will be described.

[0160] (2-1) Even when the provider server 12 performs payment for the designated application, the control unit 30 can determine the authorization to use the application. Therefore, it is possible to improve convenience regarding payment for the transaction object.

[0161] [Third embodiment] Next, a third embodiment will be described. The first, second, and third embodiments can be combined and implemented within the scope of technical compatibility.

[0162] In the third embodiment, a request to use a designated app may be specified on home screen 24H shown in FIG. 14 , which is displayed on terminal display unit 24 of payment terminal device 18. Home screen 24H is a screen on which apps already installed in payment terminal device 18 are displayed. In particular, home screen 24H is a screen on which a request to use a designated app can be made without going through a terminal management app. The terminal management app may be launched from home screen 24H of payment terminal device 18.

[0163] When a user performs an operation on the payment terminal device 18 to designate a designated app from one or more apps displayed on the home screen 24H, the terminal control unit 20 transmits a designated app request to the information processing device 11. Thereafter, the information processing device 11 is controlled in the same manner as in the first embodiment. More specifically, if the user does not have permission to use the designated app, a purchase screen 24C is displayed on the terminal display unit 24. If the user has permission to use the designated app, a start-up screen 24E is displayed on the terminal display unit 24. If apps that are not installed on the home screen 24H are also displayed, an installation screen 24D may be displayed on the terminal display unit 24 when payment is successfully completed in response to the purchase request for the designated app.

[0164] In particular, in payment terminal device 18, an app installed by a user in payment terminal device 18 is not automatically uninstalled even if the user subsequently loses authorization to use the app. Furthermore, even if a different user logs in to payment terminal device 18, the apps installed in payment terminal device 18 are displayed in the same way for all users. As a result, an app installed by a first user is displayed on home screen 24H when a second user logs in, just as it was when the first user logged in.

[0165] A designated app installed by a first user may have valid contract information for the first user and an invalid contract status for the second user. In such a case, when the control unit 30 receives a first launch request for the designated app from the payment terminal device 18 and the contract status is valid, the control unit 30 determines that the user has permission to use the designated app. The first launch request for the designated app includes designated app identification data, terminal identification data, and first user identification data. This allows the control unit 30 to allow the first user to launch the designated app.

[0166] In this way, when the first user attempts to launch the designated app that the first user installed, the first user's contract status for the designated app is valid, and it is determined that the first user has the authority to use the designated app. As a result, the first user is permitted to launch the designated app, and the designated app is launched.

[0167] On the other hand, when a second launch request for the designated app is received from payment terminal device 18 and the contract status is invalid, control unit 30 determines that the user does not have the launch authority for the designated app. The second launch request for the designated app includes the same designated app identification data and terminal identification data as the first usage request, and second user identification data. Then, control unit 30 causes payment terminal device 18 to display a purchase image related to the purchase of the usage authority for the designated app.

[0168] In this way, when the second user attempts to launch the designated app installed by the first user, the second user's contract status for the designated app is invalid, and it is determined that the second user does not have the authority to launch the designated app. This restricts the second user's launch, and a purchase screen 24C is displayed on the terminal display unit 24. The second user does not need to install the app; by performing a purchase operation while purchase screen 24C is displayed, the contract status of the designated app can be changed to a valid contract status.

[0169] [Example of change] This embodiment can be modified as follows: This embodiment and the following modifications can be combined and implemented within the scope of technical compatibility.

[0170] The payment terminal device 18 may send a usage request to the information processing device 11 via the app list screen 24B in the first embodiment, or may send a usage request to the information processing device 11 via the home screen 24H in the third embodiment.

[0171] The purchase screen 24C may be displayed in the entire display area of ​​the terminal display unit 24, or the purchase screen 24C may be displayed in a portion of the display area of ​​the terminal display unit 24. The installation screen 24D may be displayed in the entire display area of ​​the terminal display unit 24, or the installation screen 24D may be displayed in a portion of the display area of ​​the terminal display unit 24. The start-up screen 24E may be displayed in the entire display area of ​​the terminal display unit 24, or the start-up screen 24E may be displayed in a portion of the display area of ​​the terminal display unit 24.

[0172] The terminal display unit 24 displays the purchase screen 24C, the installation screen 24D, and the startup screen 24E as separate screens, but they may also be displayed as a common screen. In this case, the terminal display unit 24 may display different images, such as a purchase image, an installation image, and a startup image, on the same common screen. That is, the terminal display unit 24 may display a purchase image, an installation image, and a startup image. For example, the purchase button may change to an install button after a user operates a purchase button on the purchase screen 24C and payment for the app's usage rights is completed. The screen on which the install button changes to an install button corresponds to an example of the installation screen 24D, and the install button corresponds to an example of an installation image. For example, the install button may change to a launch button after a user operates the install button on the installation screen 24D and installation of the app is completed. The screen on which the launch button changes to an launch screen 24E corresponds to an example of the launch button, and the launch button corresponds to an example of a launch image. For example, after the app has been installed, the user may operate the purchase button on the purchase screen 24C and payment for the app's usage rights is completed, and the purchase button changes to a launch button. The screen that has changed into the start button corresponds to an example of the start screen 24E, and the start button corresponds to an example of the start image.

[0173] A first app installed by default and a second app installed manually by the user may be displayed on home screen 24H of payment terminal device 18. The first app may be, for example, a device management app. The second app may be, for example, a POS app.

[0174] The request to use the designated app may be specified on the home screen 24H of the payment terminal device 18. The app displayed on the home screen 24H is already installed on the payment terminal device 18. Therefore, when the first user specifies the app displayed on the home screen 24H as the designated app, the control unit 30 determines that a request to launch the designated app has been input if the contract status of the designated app is valid. When the second user specifies the app displayed on the home screen 24H as the designated app, the control unit 30 determines that a request to purchase the designated app has been input if the contract status of the designated app is invalid.

[0175] When displaying the home screen 24H, the control unit 30 may, assuming that a designated app request has been input, display an image based on the contract status so as to correspond to the app displayed on the home screen 24H. In particular, when displaying the home screen 24H, the control unit 30 may, assuming that a designated app request has been input, display any one of a purchase image, an installation image, and a launch image so as to correspond to the app displayed on the home screen 24H. In such a case, multiple apps may correspond to the designated app due to the input of the designated app request.

[0176] When displaying the application list screen 24B, the control unit 30 may assume that a designated application request has been input and may display an image based on the contract status to correspond to the application displayed on the application list screen 24B. In particular, when displaying the application list screen 24B, the control unit 30 may assume that a designated application request has been input and may display any one of a purchase image, an installation image, and a launch image to correspond to the application displayed on the application list screen 24B. In such a case, multiple applications may correspond to the designated application due to the input of the designated application request.

[0177] As described above, the present application also includes a configuration in which either a purchase button or an install button is displayed on the app list screen 24B. In this case, in addition to the icons, names, descriptions, and contract types of apps that can be installed in payment terminal device 18, either a purchase button or an install button is displayed on the app list screen 24B depending on the user's usage authority and the installation status of the apps. Specifically, the control unit 30 causes the terminal display unit 24 to display either a purchase button or an install button for each app depending on the contract status corresponding to the user's user identification data and the app identification data for each app displayed on the app list screen 24B. Similarly to the purchase button and the install button, the present application also includes a configuration in which a launch button is displayed on the app list screen 24B.

[0178] 10 and 11 , the control unit 30 determines whether an installation request and a launch request are input after a purchase request is input, but this is not limiting. For example, the control unit 30 may cause the terminal display unit 24 to display a purchase screen 24C, an installation screen 24D, or a launch screen 24E according to the user identification data of the user logged in to the first app and the contract status corresponding to the designated app identification data of the second app. For example, the control unit 30 may cause the terminal display unit 24 to display a purchase screen 24C, an installation screen 24D, or a launch screen 24E according to the user identification data of the user logged in to the first app and the installation status of the second app.

[0179] The designated app request may include data indicating whether the designated app has been installed. Thus, in step S45 of Fig. 11, control unit 30 may obtain data indicating whether the designated app has been installed, included in the designated app request from payment terminal device 18, and determine whether the designated app has been installed. In other words, in step S45 of Fig. 11, control unit 30 may obtain data indicating whether the designated app has been installed from payment terminal device 18 and determine whether the designated app has been installed.

[0180] The collective valid contract status may be able to set an upper limit on the number of payment terminal devices 18 to which usage authority is granted. For example, the collective valid contract status may be set to have an upper limit of 100 payment terminal devices 18 to which usage authority is granted. The collective valid contract status may also be set to have an upper limit of the number of payment terminal devices 18 to which usage authority is granted in stages.

[0181] The collective valid contract status may be set in advance to the terminal identification data to which usage authority is granted. The control unit 30 may receive the terminal identification data to which usage authority is granted from the payment terminal device 18 or a user terminal device. In the user management database 31C, at least one piece of terminal identification data may be associated with user identification data and application identification data. In such a case, in steps S35 to S37, the control unit 30 may execute processing based on the terminal identification data even if the contract status is the collective valid contract status. The control unit 30 may receive an instruction to change the terminal identification data to which usage authority is granted from the payment terminal device 18 or a user terminal device.

[0182] The collective valid contract status may be set in response to a user request. The collective valid contract status may be set in response to a user request, regardless of the application provider. In this case, the control unit 30 may set the collective valid contract status corresponding to the designated application identification data when a user request is input.

[0183] The contract status may be that an actual contract exists, but even if no contract exists, it is acceptable as long as the application for purchase, application for installation, purchase procedure, and installation procedure for the app have been completed.

[0184] Control unit 30 may transmit an instruction to payment terminal device 18 to display an error image when a usage request is input but payment is not completed normally. Control unit 30 may transmit an instruction to payment terminal device 18 to display one of multiple types of error images when a usage request is input but payment is not completed normally. The multiple types of error images may include an image when there is no app identification data and an image when there is app identification data but the contract is invalid.

[0185] When a viewing request is input from payment terminal device 18, control unit 30 may provide the contract status of the app that corresponds to the user identification data and terminal identification data. When a viewing request is input from payment terminal device 18, control unit 30 may not provide the contract status of the app that corresponds to the user identification data but does not correspond to the terminal identification data.

[0186] When a viewing request is input from the payment terminal device 18, the control unit 30 may provide a list of the contract status and terminal identification data of the application corresponding to the user identification data. The control unit 30 may receive a contract cancellation request for the app from the payment terminal device 18 or the user terminal device. When the control unit 30 receives a contract cancellation request, the control unit 30 may register the contract details in the contract record database 31B. When the control unit 30 receives a contract cancellation request, the control unit 30 may update the contract status to the canceled status.

[0187] The control unit 30 may receive a request to stop providing an application from the provider server 12. When the control unit 30 receives the request to stop providing an application, the control unit 30 may delete the application management data 41 to be stopped from the application management database 31A. When the control unit 30 receives the request to stop providing an application, the control unit 30 may update the application management database 31A so as to invalidate the application management data 41 to be stopped.

[0188] The invalid contract status may be distinguishable as to whether an individual valid contract status has become invalid or whether a collective valid contract status has become invalid. The invalid contract status may be a free contract. The free contract may become invalid upon a request from the user to cancel the app contract. The free contract may become invalid upon a request from the app provider to stop providing the app.

[0189] The lump-sum contract status may be a free contract. The lump-sum contract status may not be a recurring payment contract. The lump-sum contract status may not be a one-time payment contract. The contract type does not have to include any of the free-of-charge contract type, one-time payment contract type, and recurring payment contract type. The contract type may include other contract types in addition to the free-of-charge contract type, one-time payment contract type, and recurring payment contract type.

[0190] The contract status does not have to include any of the invalid contract status, individual valid contract status, and collective valid contract status. The contract status may include other contract statuses in addition to the invalid contract status, individual valid contract status, and collective valid contract status.

[0191] Although the designated app is not automatically installed when the purchase of the designated app is completed, the designated app may be installed automatically. In other words, the installation request may be included in the purchase request. In such a case, the installation screen 24D may not be displayed on the terminal display unit 24.

[0192] Although the designated app does not automatically launch when installation is complete, the designated app may also launch automatically. That is, the launch request may be included in the installation request or the purchase request. In such a case, the launch screen 24E may not be displayed on the terminal display unit 24.

[0193] As long as the user identification data, password, designated application identification data, and device identification data included in the designated application request are retained, the purchase request, installation request, and launch request do not need to include the retained data.

[0194] Payment terminal device 18 may send an installation request and a launch request separately as usage requests for the designated app to information processing device 11, or may send the installation request and the launch request as a single usage request to information processing device 11. In other words, control unit 30 may receive an installation request and a launch request separately as usage requests for the designated app from payment terminal device 18, or may send the installation request and the launch request as a single usage request to information processing device 11.

[0195] The usage authority of the designated app may include other authority in addition to the installation authority and the launch authority. The other authority may include, for example, the authority to use optional functions. The usage authority of the designated app may include at least one of the installation authority and the launch authority.

[0196] If the control unit 30 does not determine that the user has permission to use the designated app, the control unit 30 may restrict the use of some of the functions of the designated app. For example, if the control unit 30 does not determine that the user has permission to use the designated app, the control unit 30 may allow the designated app to be installed but restrict the launch of the designated app. In other words, if the control unit 30 does not determine that the user has permission to use the designated app, the control unit 30 may restrict the use of some or all of the functions of the designated app.

[0197] The user identification data is data for controlling the app, and may be the same as or different from the identification data used when logging in to payment terminal device 18. In other words, the user identification data is data for logging in to the terminal management app, but may be the same as or different from the identification data used when logging in to payment terminal device 18.

[0198] Payment terminal device 18 may include a printing unit that prints receipt paper in conjunction with the payment of a transaction. Payment terminal device 18 may also include a transport unit that transports receipt paper printed by the printing unit.

[0199] The information processing device 11 may have the configuration of another server. The information processing device 11 may have, for example, some or all of the functions of the provision server 12. The information processing device 11 may have, for example, some or all of the functions of an e-commerce service.

[0200] The information processing device 11 may be composed of multiple servers. The multiple servers may include, for example, a payment server related to the payment of transaction objects and an application management server related to the application provided to the payment terminal device 18. The multiple servers may be managed by different administrators or the same administrator. The information processing system 10 may not include the providing server 12. The information processing system 10 may not include the payment terminal device 18.

[0201] The phrase "at least any" used herein means one or more of the desired options. As an example, when the number of options is two, the phrase "at least any" used herein means only one option or both options. As another example, when the number of options is three or more, the phrase "at least any" used herein means only one option or any combination of two or more options.

[0202] [Note] The technical concepts grasped from the above-described embodiment and modified examples will be described below. [1] The information processing device includes a user identification data acquisition unit that acquires user identification data of a user who uses a payment terminal device that makes payment for a transaction object, an application identification data acquisition unit that acquires identification data of a designated application designated by the user from the payment terminal device, a contract status acquisition unit that acquires a contract status corresponding to the user identification data and the identification data of the designated application, and a usage authority determination unit that determines the usage authority of the designated application based on the contract status.

[0203] [2] In the above information processing device, the payment terminal device includes a first application and a second application, and when the usage authority determination unit acquires identification data of the second application as identification data of the specified application, it determines the usage authority of the second application based on the contract status corresponding to the user identification data logged in to the first application and the identification data of the second application.

[0204] [3] The information processing device includes a terminal identification data acquisition unit that acquires terminal identification data of the payment terminal device from the payment terminal device, and when the usage authority determination unit acquires identification data of the second application as identification data of the designated application, it determines the usage authority of the second application based on the contract status corresponding to the user identification data, the identification data of the second application, and the terminal identification data.

[0205] [4] The information processing device includes a usage control unit that restricts usage of the second application when it is determined that the user does not have the authorization to use the second application based on the contract status.

[0206] [5] The information processing device includes a usage request acquisition unit that acquires a usage request for the designated application from the payment terminal device, and a terminal identification data acquisition unit that acquires terminal identification data of the payment terminal device from the payment terminal device, wherein the user identification data includes first user identification data of a first user and second user identification data of a second user, and the contract status includes a valid contract status in which the usage authority for the designated application is present and an invalid contract status in which the usage authority for the designated application is not present, and the usage authority determination unit, when a first usage request for the designated application including the identification data, the terminal identification data, and the first user identification data of the designated application is acquired from the payment terminal device, determines that the usage authority for the designated application is present when the contract status is the valid contract status, and when a second usage request for the designated application including the same identification data of the designated application as the first usage request, the same terminal identification data as the first usage request, and the second user identification data is acquired from the payment terminal device, determines that the usage authority for the designated application is not present when the contract status is the invalid contract status.

[0207] [6] The above information processing device is provided with a display control unit that causes the payment terminal device to display an image, wherein the usage request includes a request to launch the designated application, and the usage authority determination unit determines that the usage authority for the designated application exists when a first launch request for the designated application, which includes identification data of the designated application, the terminal identification data, and the first user identification data, is received from the payment terminal device and the contract status is the valid contract status, and determines that the usage authority for the designated application does not exist when a second launch request for the designated application, which includes the same identification data of the designated application as the first usage request, the same terminal identification data as the first launch request, and the second user identification data, is received from the payment terminal device and the contract status is the invalid contract status, and the display control unit causes the payment terminal device to display a purchase image related to the purchase of the usage authority for the designated application when the contract status is the invalid contract status, when the second launch request is received from the payment terminal device and the contract status is the invalid contract status.

[0208] [7] In the above information processing device, the contract status includes a collective valid contract status in which the usage authority for the designated application is available for multiple payment terminal devices based on the user identification data, and when the contract status corresponding to the user identification data and the designated application is the collective valid contract status, the usage authority determination unit determines the usage authority for the designated application based on the contract status corresponding to the user identification data and the designated application.

[0209] [8] The information processing device includes a terminal identification data acquisition unit that acquires terminal identification data of the payment terminal device from the payment terminal device, and when the usage authority determination unit determines that the contract status corresponding to the designated application is not the collective valid contract status, it determines the usage authority of the designated application based on the user identification data, the designated application, and the contract status corresponding to the terminal identification data.

[0210] [9] The information processing device includes a usage control unit that allows use of the designated application when it determines that the usage authority exists based on the user identification data and the contract status corresponding to the designated application.

[0211]

[10] The information processing device includes a display control unit that causes the payment terminal device to display an image, and the contract status includes an invalid contract status in which there is no usage authority for the designated application, and the usage authority determination unit determines that there is no usage authority when the contract status corresponding to the user identification data and the designated application is the invalid contract status, and when it determines that there is no usage authority for the designated application, the display control unit causes the payment terminal device to display a purchase image related to the purchase of the usage authority for the designated application.

[0212]

[11] In the information processing device, the contract status includes a valid contract status in which the usage authority for the designated application is present, and the usage authority determination unit determines that the usage authority is present when the contract status corresponding to the user identification data and the designated application is the valid contract status, and when it determines that the usage authority for the designated application is present, the display control unit does not display the purchase image.

[0213]

[12] The information processing device includes a terminal identification data acquisition unit that acquires terminal identification data of the payment terminal device from the payment terminal device, and a contract status providing unit that, when a request to view the contract status is acquired from the payment terminal device, provides the contract status of multiple payment terminal devices, including the payment terminal device, that corresponds to the user identification data to the payment terminal device.

[0214]

[13] The information processing system includes a user identification data acquisition unit that acquires user identification data of a user who uses a payment terminal device that makes payment for a transaction object; an application identification data acquisition unit that acquires identification data of a designated application designated by the user from the payment terminal device; a contract status acquisition unit that acquires a contract status corresponding to the user identification data and the identification data of the designated application; and a usage authority determination unit that determines the usage authority of the designated application based on the contract status.

[0215]

[14] The information processing method includes at least one computer that acquires user identification data of a user who uses a payment terminal device to make a payment for a transaction object, acquires identification data of a designated application designated by the user from the payment terminal device, acquires a contract status corresponding to the user identification data and the identification data of the designated application, and determines the authorization to use the designated application based on the contract status.

[0216]

[15] The program causes at least one computer to perform the following operations: acquire user identification data of a user who uses a payment terminal device to make payment for a transaction object; acquire identification data of a designated application designated by the user from the payment terminal device; acquire a contract status corresponding to the user identification data and the identification data of the designated application; and determine the authorization to use the designated application based on the contract status. [Explanation of symbols]

[0217] 10...information processing system, 11...information processing device, 12...providing server, 18...payment terminal device, 30...control unit, 30A...user identification data acquisition unit, 30C...usage request acquisition unit, 30D...application identification data acquisition unit, 30E...terminal identification data acquisition unit, 30F...contract status acquisition unit, 30G...usage authority determination unit, 30H...usage control unit, 30I...display control unit, 30J...contract status providing unit, 31...memory unit, 31A...application management database, 31B...contract history database, 31C...user management database, 41...application management data, 42...contract history data, 43...user data.

Claims

1. A user identification data acquisition unit acquires user identification data of a user who uses a payment terminal device to settle transactions and who sells the transactions, An application identification data acquisition unit that acquires identification data of a designated application, which is different from the transaction target and is specified by the user, from the payment terminal device. A terminal identification data acquisition unit that acquires terminal identification data of the payment terminal device from the payment terminal device, A contract status acquisition unit acquires the contract status corresponding to the user identification data, the specified application identification data, and the terminal identification data. The system includes a user rights determination unit that determines the user rights of the designated application based on the aforementioned contract status. Information processing device.

2. In the information processing apparatus according to claim 1, The aforementioned contract status includes the status of individual valid contracts, which are contracts on a per-user identification data and per-terminal identification data basis. When the user rights determination unit determines that the contract status corresponding to the designated application is the individual valid contract status, it determines the user rights for the designated application based on the contract status corresponding to the user identification data, the identification data of the designated application, and the terminal identification data. Information processing device.

3. In the information processing apparatus according to claim 1, When a request to view the contract status is received from the payment terminal device, the system includes a contract status provision unit that provides the payment terminal device with the contract status of multiple payment terminal devices corresponding to the user identification data. Information processing device.

4. In the information processing apparatus according to claim 1, When it is determined that the user does not have the right to use the designated application based on the contract status, the system includes a usage control unit that restricts the use of the designated application. Even if the user control unit determines that the user does not have the necessary authorization, it will not uninstall the designated application from the payment terminal device, nor will it perform any control to hide the designated application on the payment terminal device. Information processing device.

5. In the information processing apparatus described in Claim 4, When the usage control unit determines that the contract period included in the contract status has ended, in the case where the contract format of the designated application is a recurring payment contract format, if the settlement for the use of the designated application is completed successfully, it will allow the use of the designated application by extending the contract period, and if the settlement for the use of the designated application is not completed successfully, it will restrict the use of the designated application by not extending the contract period. Information processing device.

6. In the information processing apparatus according to claim 1, The payment terminal device is equipped with a display control unit that displays an image, The aforementioned contract status includes invalid contract status where the user rights for the specified application are not granted, The display control unit, when payment for the use of the designated application is not completed successfully, causes the payment terminal device to display one of several types of error images, including an image for when there is no identification data for the designated application and an image for when there is identification data for the designated application but the contract is invalid. Information processing device.

7. In the information processing apparatus described in Claim 1, A usage request acquisition unit that acquires usage requests for the specified application from the payment terminal device, The payment terminal device includes a display control unit that displays an image, The user identification data includes the first user identification data of the first user and the second user identification data of the second user. The aforementioned contract status includes a valid contract status in which the user has the right to use the designated application, and an invalid contract status in which the user does not have the right to use the designated application. If the designated application is installed on the payment terminal by the first user, it will also be displayed on the home screen of the payment terminal where the applications already installed on the payment terminal are displayed when the second user logs in. The aforementioned usage request includes a request to launch the specified application which can be specified from the home screen, When the user rights determination unit obtains a request from the payment terminal device to launch the designated application, which includes the second user identification data, and the contract status is the invalid contract status, it determines that the user does not have the right to use the designated application. When the display control unit determines that the user does not have the right to use the designated application, it causes the payment terminal device to display a purchase image related to the purchase of the right to use the designated application. Information processing device.

8. In the information processing apparatus described in Claim 1, A usage request acquisition unit that acquires usage requests for the specified application from the payment terminal device, The payment terminal device includes a display control unit that displays an image, The aforementioned contract status includes a valid contract status in which the user has the right to use the designated application, and an invalid contract status in which the user does not have the right to use the designated application. When the user rights determination unit receives the user request, it determines that the user has the right to use the application if the designated application is a free application. The display control unit, When the aforementioned usage request is received, and the designated application is a paid application and the contract status is the invalid contract status, the payment terminal device shall display a purchase image relating to the purchase of the usage rights for the designated application. When the aforementioned usage request is received, and the designated application is the paid application, and the contract status is the valid contract status, and the designated application is not installed on the payment terminal device, the payment terminal device will display an installation image related to the installation of the designated application. Information processing device.

9. In the information processing apparatus according to claim 8, The display control unit displays either a purchase button or an install button on the application list screen displayed on the payment terminal device, depending on the user's access rights and the installation status of the specified application. Information processing device.

10. In the information processing apparatus according to Claim 1, The contract format for the aforementioned designated application includes an indirect settlement contract format in which an external server handles the settlement. The user rights determination unit, if the contract format of the designated application is the indirect settlement contract format, queries the provision server for the settlement status and determines the user rights of the designated application based on the receipt of settlement completion data from the provision server indicating that the settlement for the use of the designated application has been successfully completed. Information processing device.

11. In the information processing apparatus according to claim 1, The system includes a registration unit that, upon receiving an application registration request from an external service server, which includes the identification data of the specified application, the contract format of the specified application, and the usage fee of the specified application, registers the identification data of the specified application, the contract format of the specified application, and the usage fee of the specified application in a database, and that, upon receiving a service termination request from the service server, disables the specified application. Information processing device.

12. A user identification data acquisition unit acquires user identification data of a user who uses a payment terminal device to settle transactions and who sells the transactions, An application identification data acquisition unit that acquires identification data of a designated application, which is different from the transaction target and is specified by the user, from the payment terminal device. A terminal identification data acquisition unit that acquires terminal identification data of the payment terminal device from the payment terminal device, A contract status acquisition unit acquires the contract status corresponding to the user identification data, the specified application identification data, and the terminal identification data. The system includes a user rights determination unit that determines the user rights of the designated application based on the aforementioned contract status. Information processing system.

13. At least one computer, To obtain user identification data of a user who uses a payment terminal device to settle transactions and who sells the transactions, The payment terminal device obtains identification data of a designated application that is different from the transaction target and is specified by the user, The terminal identification data of the payment terminal device is obtained from the payment terminal device, To obtain the contract status corresponding to the user identification data, the specified application identification data, and the terminal identification data, Based on the aforementioned contract status, the following actions are performed: Information processing methods.

14. On at least one computer, To obtain user identification data of a user who uses a payment terminal device to settle transactions and who sells the transactions, The payment terminal device obtains identification data of a designated application that is different from the transaction target and is specified by the user, The terminal identification data of the payment terminal device is obtained from the payment terminal device, To obtain the contract status corresponding to the user identification data, the specified application identification data, and the terminal identification data, Based on the aforementioned contract status, determine the right to use the specified application and perform the following actions: program.

Images