JP2021044027A - Payment system and computer program therefor - Google Patents

Abstract

To provide a payment system for lightening the burden required for responding to various payment services.SOLUTION: Provided is a payment system with which information included in an information image 100 displayed by a payment terminal 40 is provided to a server 30 via a user terminal 60 and a payment process is executed, in which the information image 100 is displayed on the payment terminal 40 in such a way that essential information IFa defined in common irrespective of the type of payment means to be used for payment is included, the essential information IFa of the information image 100 is acquired by the user terminal 60, payment means to be used for payment is selected from various types of payment means by a user via the user terminal 60, payment information IFb including information for identifying the selected payment means and the essential information IFa is transmitted from the user terminal 60 to the server 30, the payment means is identified on the basis of the payment information IFb, and a payment process is executed by the server 30 so that payment corresponding to the essential information IFa is made in accordance with the identified payment means.SELECTED DRAWING: Figure 5

Description

The present invention relates to a system or the like that provides a payment service using an image such as a two-dimensional code.

A two-dimensional code with embedded payment information is displayed on a payment terminal installed in a store, etc., the two-dimensional code information is read by the user's terminal, and the obtained information is sent to the server. A system for transmitting and proceeding with payment processing is known (see, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2016-173752

Since various information can be included in an image such as a two-dimensional code, it is possible to correspond to various payment services for exchanging information using such an image. However, in general, the types and formats of information to be included in images such as two-dimensional codes are set independently for each payment service. Therefore, in order to introduce a new payment service, it is necessary to introduce a new program to the terminal that issues the two-dimensional code, etc., or to introduce a new terminal. The burden of costs increases.

Therefore, an object of the present invention is to provide a payment system or the like capable of reducing the burden required for supporting various payment services.

The payment system according to one aspect of the present invention is constructed as a client server system including a server, a user terminal that functions as a client for the server, and a payment terminal, and is included in an information image presented by the payment terminal. A payment system in which a payment process for settling a fee to be paid by a user is executed on the server by providing information necessary for the payment process to the server via the user terminal. An information image display means for displaying the information image on the payment terminal so that essential information commonly defined regardless of the type of payment means to be used is included as information necessary for the payment process, and the information image. The information acquisition means for causing the user terminal to acquire the essential information included in the above and the payment means to be used for payment from a plurality of types of payment means are selected by the user via the user terminal. The payment information providing means for causing the user terminal to transmit the payment information including the payment means identification information for identifying the payment means and the essential information acquired by the information acquisition means to the server, and the payment information to the server. The payment means is identified based on the payment means identification information included in the payment information, and the payment processing is performed so that the payment according to the essential information included in the payment information is performed according to the identified payment means. It includes a payment execution means to be executed, and a result information providing means for causing the server to transmit result information indicating the result of executing the payment process to the payment terminal. It is equipped with.

The computer program according to one aspect of the present invention is constructed as a client server system including a server, a user terminal that functions as a client for the server, and a payment terminal, and is included in an information image presented by the payment terminal. A computer program applied to a payment system in which a payment process for settling a fee payable by a user is executed on the server by providing information necessary for the payment process to the server via the user terminal. The information image is such that the computer included in the payment system includes essential information commonly defined regardless of the type of payment means to be used for payment as information necessary for the payment processing. An information image display means for displaying the above on the payment terminal, an information acquisition means for causing the user terminal to acquire the essential information contained in the information image, and a payment means to be used for payment from a plurality of types of payment means. The user terminal transmits the payment information including the payment means identification information for allowing the user to select the selected payment means and the essential information acquired by the information acquisition means from the user terminal to the server. The payment information providing means to be caused, the server is made to identify the payment means based on the payment means identification information included in the payment information, and the payment according to the essential information included in the payment information is identified. It functions as a payment execution means for executing the payment process so as to be performed according to the payment means, and a result information providing means for causing the server to transmit the result information indicating the result of the execution of the payment process to the payment terminal. It is configured as follows.

The figure which showed the schematic structure of the payment system which concerns on 1st Embodiment of this invention. The figure which shows an example of the structure of the script as an example of the processing program used by the payment execution server in payment processing. The figure which shows the schematic example of the processing which should be performed until the 2D code is displayed in the payment system of FIG. The figure which shows the schematic example of the processing which should be performed after the 2D code is displayed in the payment system of FIG. The figure which shows how the information described in a script is decided sequentially in the procedure of FIG. The figure which shows the specific example of the payment system of FIG. The flowchart which shows the procedure of the processing which should be performed until the 2D code is displayed in the payment system of FIG. The flowchart which shows the procedure of the processing which should be performed after the 2D code is displayed in the payment system of FIG. The flowchart following FIG. The figure which shows the modification of FIG. The figure which shows the schematic example of the processing which should be performed until the 2D code is displayed in the payment system which concerns on 2nd form. The figure which shows how the information described in a script is sequentially determined in the procedure of FIG. The flowchart which shows the procedure of processing which should be performed until the 2D code is displayed in the payment system which concerns on 2nd form. The figure which showed the schematic structure of the payment system which concerns on 3rd Embodiment of this invention. FIG. 14 is a diagram showing an example of a state in which information is transmitted from a service terminal to a payment execution server via a user terminal in the payment system of FIG. The figure which shows the specific example of the payment system of FIG. .. The flowchart which shows an example of the procedure of various processing performed to execute the payment processing in the payment system of FIG. The figure which shows the modification for totalizing sales.

(First form)
Hereinafter, the first embodiment of the present invention will be described with reference to FIGS. 1 to 9. As shown in FIG. 1, the payment system 1 according to the first embodiment includes a back office server 10, a script management server 20, a payment execution server 30, and a service terminal 40 that functions as a client for these servers 10 to 30. The management terminal 50 and the user terminal 60 are included as an example of the computer. Further, the payment system 1 cooperates with the account management server 70, the item management server 80, and the service management server 90 in relation to the payment service. Each of the servers 10 to 30, 70 to 90, and the terminals 40 to 60 can transmit or receive information from each other by being appropriately connected to a network (not shown), for example, the Internet. Therefore, the service terminal 40, the management terminal 50, and the user terminal 60 may appropriately function as clients of the account management server 70, the item management server 80, and the service management server 90.

The service terminal 40 is a terminal device installed and operated by a person who intends to provide a payment service to a user (hereinafter, referred to as a service provider) in a management area SA of a commercial facility or the like. The service terminal 40 has a function of displaying a two-dimensional code 100 as an example of an information image to be read by the user terminal 60 in order to provide a payment service. In the payment service in the payment system 1, the two-dimensional code 100 displayed on the service terminal 40 as an example of the payment terminal is read by the user terminal 60, and predetermined information is included in the essential information recorded in the two-dimensional code 100. The payment information with the above is transmitted from the user terminal 60 to the payment execution server 30. The procedure for payment processing will be described in detail later.

As an example, the service terminal 40 may include terminal devices such as a game machine 40A and a store terminal 40B. The game machine 40A is an example of a commercial game machine that allows a user to play a game in exchange for payment of a predetermined fee. The store terminal 40B is an example of a terminal device that is installed in a store such as a convenience store and provides various services such as selling various products such as tickets or collecting charges. The service provided to the user by the game machine 40A and the store terminal 40B is a service whose application is controlled in association with the payment service processed by the payment system 1, and should be distinguished from the payment service. is there. In the following, this type of service may be referred to as a related service to distinguish it from a payment service.

The service terminal 40 is not limited to the example of providing the related service. For example, a terminal that is installed for the purpose of letting the user use the payment service itself, such as a register terminal that registers sales of products purchased by the user at a store and calculates the fee to be paid by the user, does not provide related services. It may be provided as a service terminal 40. A so-called POS terminal may be provided as the service terminal 40. In addition, various terminal devices may be used as the service terminal 40. However, the service terminal 40 needs to be provided with a display device for displaying the two-dimensional code 100.

The management terminal 50 is a terminal device provided in the management area SA for the purpose of managing the payment service or making various settings related to the payment service. The management terminal 50 can be used as a terminal that provides the back office server 10 with information necessary for realizing the payment service. As the management terminal 50, various terminal devices such as a book-type personal computer may be used. A service terminal 40 such as a game machine 40A or a store terminal 40B may also be used as a management terminal 50. The management area SA is a concept indicating an area managed by a service provider, and does not necessarily mean one cohesive place. For example, the service terminal 40 may be installed in a store or the like, and the management terminal 50 may be installed in the office or the like of a service provider that operates the service terminal 40.

The user terminal 60 is a terminal that should be used for the personal use of the user. As an example, a smartphone having a network connection function is used as a user terminal 60. The user terminal 60 reads the two-dimensional code 100 displayed on the service terminal 40, adds predetermined information to the essential information included in the two-dimensional code 100, generates payment information, and obtains the payment. The information is transmitted to the payment execution server 30. The user terminal 60 is not limited to a smartphone, and an appropriate terminal device may be used as long as it has a network connection function and can read the two-dimensional code 100 displayed on the service terminal 40. It is preferable that the user terminal 60 has portability that can be carried and used at the place where the service terminal 40 is installed.

Next, each server will be described in sequence. The back office server 10, the script management server 20, and the payment execution server 30 are provided as servers that execute the payment processing necessary for providing the payment service or are in charge of incidental processing necessary for the execution. .. The back office server 10 is provided as a server that mediates between the service terminal 40 and the management terminal 50 and the script management server 20. For example, the back office server 10 sets payment conditions for a fee to be paid when a user uses the user terminal 60 based on the information acquired from the management terminal 50, and transfers the payment condition information to the script management server 20. Notice. Further, the back office server 10 acquires the information necessary for issuing the two-dimensional code 100 from the script management server 20 and provides the information to the service terminal 40.

The script management server 20 creates a script for causing the payment execution server 30 to execute the payment process according to the payment conditions set by the back office server 10, and stores and manages the obtained script in the script database DB2. The script created by the script management server 20 is a kind of computer program that describes the contents of the payment process to be performed by the payment system 1 in a format that can be executed by the payment execution server 30, and is used to provide a service. This corresponds to an example of a processing program that defines the processing to be executed by the payment execution server 30. Further, the script database DB2 corresponds to an example of the program holding means. The script will be described later with an example. The payment execution server 30 acquires a script corresponding to the payment information acquired from the user terminal 60 from the script management server 20, and executes the payment process according to the obtained script.

The payment execution server 30 is a server that executes payment processing. The payment execution server 30 executes the payment processing in cooperation with other servers such as the account management server 70 as appropriate according to the content of the payment processing. The account management server 70 as an example of the cooperation partner is a server that operates the account database DB 7 to process payment of charges using a specific type of electronic currency. For example, in the account database DB 7, information on the balance of a specific type of electronic currency possessed by the user is recorded in association with the user authentication code. The account management server 70 identifies the user's balance using the user authentication code as a clue, and consumes (subtracts) the amount or amount of electronic currency corresponding to the fee payable by the user from the specified balance, thereby using the electronic currency. Realize payment.

When the payment execution server 30 is required to pay the fee in the electronic currency managed by the account management server 70, the payment execution server 30 requests the account management server 70 to perform the payment process, thereby performing the payment process in cooperation with the account management server 70. Execute. Note that FIG. 1 shows an example in which a payment method in electronic currency managed by the account management server 70 is used as a payment method for realizing payment of charges. When a payment method such as withdrawal from a user's bank account (online banking) or payment using a credit card is required, the payment execution server 30 appropriately communicates with another server that realizes payment by those payment methods. Execute payment processing in cooperation with. That is, the account management server 70 is only an example of a server that executes payment processing in cooperation with the payment execution server 30. The mechanism itself for processing payments using the exchange of information via a network such as an electronic currency, a bank account, or a credit card is widely used in the market, and the payment execution server 30 depends on the payment method. The payment process may be executed by appropriately using various mechanisms. In any case, the payment execution server 30 executes the payment processing with reference to the information held in the server in association with the user identification information (the above-mentioned information on the balance of the account is an example). It may be configured.

The payment execution server 30 also appropriately cooperates with the item management server 80 and the service management server 90 in relation to the payment processing. The item management server 80 manages items related to sales such as the unit price of each item using the product or service provided by the service terminal 40 as an item, or the item in the service terminal 40, while appropriately referring to the item management database DB8. It is a server that manages matters related to sales processing, such as the payee of each fee. For example, when targeting the game machine 40A, the item management server 80 supports various contents provided by the game machine 40A as items, and the unit price, payee, etc. of each item correspond to a unique item code for each item. Attach and record in the item management database DB8. In that case, the item management server 80 provides the information in response to a request from the game machine 40A or the management terminal 50. Alternatively, the item management server 80 is in charge of processing such as recording the fee paid for the use of the content in the game machine 40A as sales and distributing the obtained sales among related businesses. The same applies to the case of the store terminal 40B, in which the products and services provided by the store terminal 40B are managed as items. When the payment is paid in the payment process executed according to the script, the payment execution server 30 notifies the item management server 80 of the payment details. Upon receiving the notification, the item management server 80 can grasp the payment details and reflect them in sales management and the like.

The service management server 90 is a server that manages related services provided to users by the service terminal 40, or other services further associated with the related services. Hereinafter, the service provided by the service management server 90 may be referred to as a user service. For example, when the game machine 40A is provided as the service terminal 40, the service management server 90 authenticates the user who plays the game on the game machine 40A, and the user plays the result of playing the game on the game machine 40A. A service is provided as a user service, which is stored in the user database DB 9 as data and the stored play data is transmitted in response to a request from the game machine 40A. Alternatively, the service management server 90 provides a user service based on play data in response to a request from the user terminal 60. As the user service in this case, various services such as viewing the user's play history, viewing the past play video, and purchasing items used in the game may be prepared. The same applies to the case where the store terminal 40B is provided as the service terminal 40, and the service management server 90 authenticates the user when providing the related service on the store terminal 40B, and performs various information necessary for providing the related service at the store. It may be configured to be appropriately provided to the terminal 40B.

User authentication on the service management server 90 is performed using user identification information unique to each user, such as a user ID. The user authentication code to be used for user identification on the payment execution server 30 or the account management server 70 is shared with, for example, the user identification information used on the service management server 90. However, the user authentication code may be associated with the user identification information used by the service management server 90 on a one-to-one basis. In either case, the payment execution server 30 cooperates with the service management server 90 to provide, for example, the result of the payment processing to the service management server 90 and reflect it in the user service provided by the service management server 90. Can be executed as an example of related processing. The related processing may be appropriately modified as long as it is distinguished from the payment processing and is associated with the user identification information. When the service terminal 40 does not provide the related service, the cooperation between the payment execution server 30 and the service management server 90 is unnecessary.

Next, an example of the script will be described with reference to FIG. The script shown in FIG. 2 is an example of a script for executing a payment process, and includes information for identifying each of a user, a payee, a payment method, and a payment content. The information described in the script is an example of information for specifying "who", "who", "why", and "what to do" regarding the payment process. The user's information is written in a script to identify "who" should make the payment. As the user information, for example, a user authentication code uniquely set for each user may be used.

The payee information is written in a script to identify "who" the fee should be paid to. The payee is, in short, the person to whom the fee should be paid. The payee may be, for example, a business operator as a service provider. Alternatively, another business operator that provides related services via the service terminal 40 may be set as the payment destination. Such businesses include, for example, businesses that provide content used in the game machine 40A, businesses that provide products such as tickets sold via the store terminal 40B, or businesses thereof. A business operator or the like who has been entrusted with collecting fees may be set as the payee. As an example, a business operator that operates the item management server 80 shown in FIG. 1, or a collection institution, a settlement institution, or the like designated by the business operator may be described in the script as a payment destination. In this case, the payment to the payee is realized by notifying the item management server 80 of the payment of the fee from the payment execution server 30.

Payment method information is written in a script to specify "why" to make a payment, that is, the payment method to be used to pay the fee. For example, payment methods such as payment by electronic currency, payment by withdrawal from a bank deposit account, payment by credit card, etc., which can complete payment using information processing via a network, are payment methods. Is set as. There are various types of electronic currencies depending on the issuing entity or the managing entity, but if payment in electronic currency is specified in the payment method information, payment will be made using any of the electronic currencies. Payment method information may be set so that it can be identified. For example, payment in electronic currency managed by the account management server 70 of FIG. 1 may be described in a script as a payment means. In this case, the payment of the fee is realized by the payment execution server 30 requesting the account management server 70 to make a payment according to the script. Scripts related to payment services are created at least according to the difference in payment methods. In other words, payment services are classified according to the difference in payment means, and the script also differs depending on the type of payment means. Further, the script may be further divided according to the difference in the payee of the fee.

Payment details information is written in a script to identify "what to do" with respect to the payment process. For example, information that identifies the action content of the user that caused the payment process may be described in the script, such as "pay XX yen for the purchase of item X". By referring to the payment content information together with the payment method and payee described in the script, the details of the payment to be realized in the payment process can be determined. The payment content information may include payment amount information as minimal information. For example, when the information of the item purchased by the user is not required in the payment process, the payment content information of the script may be set as the information for specifying the payment amount. The payment details may include information that identifies the type of item. For example, when targeting a game machine 40A, "credit" as a unit for measuring the game value to be consumed as a consideration for playing a game may be specified as an item type, and this may be described in a script. .. In that case, the final payment content may be fixed by selecting the amount of credit as an item to be purchased by the user on the user terminal 60. That is, it is possible to let the user select the quantity such as 1 credit and 2 credits on the user terminal 60 instead of selecting the quantity on the game machine 40A. Thereby, the user interface in the service terminal 40 can be simplified.

The script also contains comment, expiration date and serial number information. The comment is described in the script as text information to be displayed on the user terminal 60 when requesting the user to approve the payment via the user terminal 60. The expiration date is described in the script as information indicating the expiration date that the script can pass in the payment process. The script whose expiration date has passed is appropriately deleted from the script database DB2. As a result, the amount of data recorded in the script database DB2 can be suppressed to an appropriate range. The serial number is a code uniquely set for each script, and corresponds to an example of each of the processing information and the processing identification information uniquely associated with the script. In FIG. 2, as a method of associating the script with the serial number, the serial number is included in the script as a part of the script, but the serial number is not included in the script and the script and the serial number are associated with each other on a one-to-one basis. The script and the serial number may be associated with each other by recording the script in the script database DB2.

As described above, the script created by the script management server 20 is an example of a processing program as a computer program that describes the contents of the processing to be executed by the payment execution server 30. In addition, the set of various information to be described in the script corresponds to an example of the variable group included in the script. The information described in the script held in the script database DB2 includes a confirmed state and an undetermined state. These states correspond to an example of a state in which the values of variables included in the script are fixed or undetermined. For example, when user information is used as one variable, the value of the variable is fixed when the user authentication code is specifically specified, and the value of the variable is when the user authentication code is not specified. Corresponds to the unspecified state. A part of various information recorded in the script is set according to the information given from the management terminal 50. For example, information such as a payee may be described in a script as a variable whose specific value is determined according to the information given from the management terminal 50 via the back office server 10. Not all information is specifically determined when the script is created, and in the script stored in the script database DB2, the values of at least some variables are in an undetermined state. The value of the undetermined variable is appropriately determined in the process of sequentially transmitting information from the service terminal 40 to the payment execution server 30 via the user terminal 60. In the above, the script management server 20 creates the script after predetermining the type of information to be recorded in the script, but the information is transmitted from the service terminal 40 to the payment execution server 30 via the user terminal 60. In the process, new types of information to be added to the script may be specified. In any case, at the stage where the script management server 20 creates and records the script, the script is incomplete and the information is transmitted from the service terminal 40 to the payment execution server 30 via the user terminal 60. The script may be completed by appropriately determining the types of variables contained therein and the values of the variables.

Next, with reference to FIGS. 3 and 4, an example of a schematic procedure of the process executed by the payment system 1 to provide the payment service will be described. However, the procedure described below is an example of the processing procedure executed in the configuration illustrated in FIG. In each of FIGS. 3 and 4, servers and the like that are not directly related to the procedure in the figure are shown in gray.

FIG. 3 shows an example of a procedure for issuing the two-dimensional code 100, and FIG. 4 shows an example of a procedure that proceeds from the two-dimensional code 100 as a starting point. In the example of FIG. 3, first, the item management server 80 provides information necessary for setting payment terms and the like to the management terminal 50 (which may be replaced by the service terminal 40) (F11). .. The information provided may include, for example, information that identifies a product, a service item code, a unit price, a payee, etc. provided by the service terminal 40.

Next, the information necessary for creating the script is input in the management terminal 50, and the input information is provided from the management terminal 50 to the back office server 10 (F12). The information input by the management terminal 50 is information that specifies what kind of script is to be created by the script management server 20. For example, when creating the script of FIG. 2, as the types of information (variables) to be included in the script, the user, payee, payment method, payment content, comment, and expiration date are back office via the management terminal 50. A specific value (fixed value) is specified for the back office server 10 for some information and is specified for the server 10. In this case, the fixed value of the payee and the expiration date may be given to the back office server 10. The comments may be specified in a state in which all of them are fixed, or may be given in a state in which some of them are unconfirmed. Further, as a payment method, a plurality of candidates regarding a payment method desired to be used by the service provider may be given to the back office server 10. The expiration date may be appropriately set by the operator of the management terminal 50, or may be automatically set according to a certain rule.

When the necessary information is given to the back office server 10, a script creation condition is set in the back office server 10, and the condition is provided to the script management server 20. In response to this, a script according to the conditions given by the script management server 20 is created (F13). A serial number is added to the created script and recorded in the script database DB2. The serial number is notified from the script management server 20 to the service terminal 40 via the back office server 10 (F14). The serial number may be notified to the service terminal 40 via the management terminal 50. In addition, in order to determine which payment service the given serial number corresponds to, the service terminal 40, the management terminal 50, or the back office server 10 appropriately stores the serial number in association with the type of payment service. You can do it.

When the service terminal 40 is requested to provide a specific payment service, the two-dimensional code 100 is generated and obtained so that essential information including the serial number of the script corresponding to the payment service is recorded. The two-dimensional code 100 is displayed on the service terminal 40 (F15). In addition to the serial number of the script, the essential information included in the two-dimensional code 100 includes information on the payment details that are unconfirmed in the script, that is, information that specifies what kind of item to purchase and how much to pay. May be added. At the stage when the script is created by the script management server 20, the items purchased by the user via the service terminal 40 and the number of purchases thereof are undecided, and their specific values are not described in the script. On the other hand, at the time when the user purchases a product or service on the service terminal 40, what kind of item is purchased and how much is paid is specifically determined. Therefore, in the service terminal 40, the information to be confirmed when the user purchases the product or the like is recorded in the two-dimensional code 100 together with the serial number of the script as an example of the confirmation information. As a result, the serial number and payment content information can be transmitted to the user terminal 60 via the two-dimensional code 100. It should be noted that the process until the serial number is provided to the user terminal 60 and the process for displaying the two-dimensional code 100 on the user terminal 60 do not necessarily have to be continuous in time. That is, the user terminal 60 acquires the serial number from the script management server 20 in advance via the back office server 10, and when the user actually makes the payment, the information of the serial number acquired earlier and the payment at that time. The two-dimensional code 100 may be generated and displayed with reference to the information according to the content.

Next, with reference to FIG. 4, a processing procedure after the two-dimensional code 100 is displayed on the service terminal 40 will be described. Prior to starting the procedure of FIG. 4, the user terminal 60 accesses the service management server 90 and completes user authentication related to related services (F20), whereby a user such as a user ID used for user authentication is completed. It is assumed that the identification information is held by each of the user terminal 60 and the service management server 90. Further, the user identification information used for user authentication on the service management server 90 is valid as an example of a user authentication code which is a definite value of user information in a script for payment processing.

In the procedure of FIG. 4, first, the two-dimensional code 100 is photographed by the user terminal 60, and the essential information included in the two-dimensional code 100 is acquired by the user terminal 60 (F21). Next, on the user terminal 60, the user authentication code (user ID) used for user authentication of the related service is added to the essential information read from the two-dimensional code 100 as an example of definite information, and is obtained. The information is transmitted to the payment execution server 30 as an example of the primary information that is a part of the payment information (F22). When the payment execution server 30 receives the information, the serial number included in the information, that is, the serial number included in the two-dimensional code 100 is notified from the payment execution server 30 to the script management server 20 and corresponds to the serial number. It is requested to provide a script to be executed (F23).

In the script management server 20, the script corresponding to the notified serial number is extracted from the script database DB2, and the obtained script is provided to the payment execution server 30 (F24). In this case, it is confirmed whether or not the script is within the expiration date, and the script whose expiration date has passed may be regarded as invalid and the subsequent processing may be stopped. When the script is provided to the payment execution server 30, the payment execution server 30 starts the process of determining the payment method that has not been determined by the script (F25). In the process, the payment execution server 30 generates a list of payment means that can be used for payment of charges, and the list of payment means is provided to the user terminal 60 as an example of selection information. In this case, if a payment method candidate is specified for the information about the payment method of the script, the candidate is described in the payment method list. If no payment method is specified, a list of payment means that can be processed by the payment execution server 30 is described. On the other hand, the user terminal 60 displays the provided list and performs a process of allowing the user to select a payment method to be used for payment of the fee. The selection result is transmitted from the user terminal 60 to the payment execution server 30 as an example of secondary information that is a further part of the payment information IFb. In this case, the information indicating the selection result corresponds to an example of the payment means identification information. Along with the provision of the list to the user terminal 60, the text described in the script is transmitted to the user terminal 60, and the text is displayed on the user terminal 60, so that the payment can be made using the selected payment means. A process may be performed to confirm with the user whether or not the execution may be performed.

When the selection result of the payment means is transmitted from the user terminal 60, the payment execution server 30 determines a specific value regarding the payment method of the script according to the selection result from the user terminal 60. Then, the payment execution server 30 executes the payment process according to the confirmed script. For example, according to the payment method described in the script, the account management server 70 is requested to make a payment using electronic currency, that is, to withdraw (consume) the electronic currency from the account corresponding to the user authentication code (F26), and the processing is successful. If this is the case, the item management server 80 is notified of the payment details (F27), and the service management server 90 is also notified of the payment completion (F28). Further, the payment completion is notified to each of the user terminal 60 and the service terminal 40 (F29, F30). As a result, the user can know that the payment has been completed via the user terminal 60. In addition, the service terminal 40 can also grasp the completion of payment. In this case, when the service terminal 40 provides the related service on condition that the payment is completed, the processing necessary for providing the related service can be started by using the notification as a trigger. In order for the payment execution server 30 to notify the service terminal 40 of the completion of payment, it is necessary to provide the payment execution server 30 with information for determining the notification destination. For that purpose, for example, the information of the notification destination is recorded in advance in the script recorded in the script database DB2, or the information indicating the notification destination is included in the two-dimensional code 100 as a part of the essential information in the service terminal 40, and this is included. By providing the payment execution server 30 from the user terminal 60, the payment execution server 30 may be able to grasp the notification destination. Alternatively, the back office server 10 may manage the issuance status of the two-dimensional code 100 on each service terminal 40, and the payment execution server 30 may notify the service terminal 40 of the completion of payment via the back office server 10.

FIG. 5 shows an example of how the information to be described in the script is determined in the procedure shown in FIGS. 3 and 4. In the illustrated example, first, the payment content and the serial number are included in the essential information IFa in the two-dimensional code 100 generated by the service terminal 40 (in the figure, the store terminal 40B is shown, but other service terminals may be used). ing. Next, in the user terminal 60 that has read the two-dimensional code 100, the user authentication code and the payment method are added as confirmation information to the payment content and serial number information included in the two-dimensional code 100, and the payment information IFb Is generated. The obtained payment information IFb is transmitted to the payment execution server 30. However, it is not essential that the payment information IFb is transmitted all at once. For example, in the example of FIG. 4, information other than the payment method is transmitted in advance to the payment execution server 30, and the payment execution server 30 provides a list of payment means based on the information transmitted in advance, and the list is provided. The payment method information is confirmed by causing the user to select the payment method based on the above, and after the confirmation, the information specifying the payment method is transmitted from the user terminal 60 to the payment execution server 30. When the payment method candidate is not described in the script in advance, a list of payment methods is obtained from the payment execution server 30 prior to transmission of the user authentication code, script, etc., and the user is made to select the payment method according to the list. It is also possible to determine the payment information IFb and collectively transmit the obtained payment information IFb to the payment execution server 30. The serial number included in the payment information IFb is provided from the payment execution server 30 to the script management server 20, and the script corresponding to the serial number is provided from the script management server 20 to the payment execution server 30. In the script provided from the script management server 20 to the payment execution server 30, as shown in gray in the figure, the user information, the payment method information, and the payment content information are in an undetermined state.

In the payment execution server 30, the user authentication code, payment method, and payment method of the payment information IFb acquired from the user terminal 60 are used for information on the user, payment method, and payment details that are unconfirmed in the script acquired from the script management server 20. Information on payment details is quoted. This confirms all the information in the script.

According to the above example, the script required for payment processing is created by the script management server 20 according to the information provided from the management terminal 50 and stored in the script database DB2, and the serial number of the script is transferred to the service terminal 40. Provided. In the script created by the script management server 20, information determined in accordance with the conditions set by the service provider can be described in advance. For example, if a specific value related to payment destination information is transmitted from the management terminal 50 to the script management server 20 via the back office server 10, the specific value (fixed information) of the information is described in the script in advance. Can be kept. It is not necessary to include such information in the two-dimensional code 100.

On the other hand, on the payment execution server 30 side, it is necessary to change the content of the payment process according to the payment method that can be described in the script. For example, a server (account management server 70 or item management server 80 in the example of FIG. 1) to be a cooperation partner is appropriately selected according to a payment destination and a payment method, or a cooperation partner is set according to the type of service terminal 40. It is necessary to appropriately select a server (service management server 90 in the example of FIG. 1) and proceed with payment-related processing according to an appropriately determined procedure with the server of the cooperation partner. However, the work of adding, modifying, and changing the program for realizing these processes need only be performed by the business operator operating the payment execution server 30, and the service terminal 40 does not have a burden.

Further, the essential information IFa recorded in the two-dimensional code 100 is common information required to execute the payment process regardless of the type of the payment means. That is, payment content information is indispensable for executing payment processing regardless of the type of payment means. Moreover, the specific value regarding the payment content information is fixed on the service terminal 40 each time each payment is made. That is, regardless of what kind of payment method the payment service uses, the information such as the payment amount is information that is commonly required for the payment execution server 30 to execute the payment process, and the information thereof. It is necessary that a concretely determined value is given to the payment execution server 30. Therefore, even if the content of the payment process to be performed as the payment service, for example, the payment destination or the payment method, changes variously, the service terminal 40 needs to include the information indicating the payment content in the two-dimensional code 100 in common. There is. Further, the serial number is information that should be commonly recorded in the two-dimensional code 100 as information necessary for specifying the script regardless of the type of payment means. As described above, the essential information IFa is common information to be recorded in the two-dimensional code 100 regardless of the type of payment means. Since there is commonality as necessary information regardless of the type of payment means, it is possible to record the essential information IFa in the two-dimensional code 100 in a certain format regardless of the type of payment means.

Therefore, even when a new payment service is introduced, it is not necessary to add a program for newly generating a two-dimensional code in a format corresponding to the payment service on the service terminal 40 side. In addition, there is no need for capital investment such as providing dedicated hardware for a new payment service on the service terminal 40 side. On the other hand, the information not described in the two-dimensional code 100 can be described in a state specifically determined in advance when the script is created, or can be appropriately added by the user terminal 60. Therefore, even if there is a difference between the payment services regarding the information required when executing the payment process, the information other than the common essential information to be recorded in the two-dimensional code 100 is described in the script in advance. Or, it can be dealt with by adding it as appropriate on the user terminal 60 side.

Next, with reference to FIG. 6, an example of a specific configuration relating to the main part of the payment system 1 will be described. The configuration of FIG. 6 is one of the specific examples of the payment system 1 of FIG. 1, and the components corresponding to FIG. 1 are designated by the same reference reference numerals as those of FIG. In the example of FIG. 6, the back office server 10 is provided with a condition setting unit 11 and a serial acquisition unit 12 as logical devices realized by combining the computer hardware and the computer program Ps1. The condition setting unit 11 sets the conditions necessary for creating the script according to the input from the management terminal 50, and provides the conditions to the script management server 20. The serial acquisition unit 12 acquires the script serial number from the script management server 20 and provides the serial number to the service terminal 40. The serial number may be provided in response to a request from the service terminal 40.

The script management server 20 is provided with a script creation unit 21 and a script management unit 22 as logical devices realized by combining the computer hardware and the computer program Ps2. The script creation unit 21 creates a script for executing the payment process according to the condition information transmitted from the back office server 10, assigns a serial number to the obtained script, and saves it in the script database DB2. The script management unit 22 provides the back office server 10 with a serial number. Further, the script management unit 22 searches the script database DB 2 in response to a request from the payment execution server 30, selects a script to be executed by the payment execution server 30, and provides the obtained script to the payment execution server 30. .. The script management unit 22 may check the expiration date of the script at an appropriate timing, and manage the script database DB 2 so that the script whose expiration date has passed is deleted from the script database DB 2.

The payment execution server 30 is provided with a payment execution unit 31 and a payment notification unit 32 as logical devices realized by combining the computer hardware and the computer program Ps3. The payment execution unit 31 acquires a script corresponding to the serial number included in the payment information IFb received from the user terminal 60 from the script management server 20, or provides the user terminal 60 with a list of payment means and confirms the script. The payment process is executed in cooperation with the account management server 70 and the like according to the script. The payment notification unit 32 notifies the service terminal 40 and the user terminal 60 of the information on the result of the payment processing executed by the payment execution unit 31, and further notifies the item management server 80 and the service management server 90 as necessary.

The service terminal 40 is provided with a payment control unit 41 and a code control unit 42 as logical devices realized by combining the computer hardware and the computer program Pt1. The payment control unit 41 determines the information of the payment content to be included as a part of the essential information IFa in the two-dimensional code 100 in response to the purchase of the product or service on the service terminal 40, for example, the payment amount to be paid by the user. Responsible for processing such as calculation. The code control unit 42 acquires the serial number to be included as a part of the essential information IFa in the two-dimensional code 100, generates the essential information IFa together with the payment contents confirmed by the payment control unit 41, and obtains the essential information. A two-dimensional code 100 is generated based on IFa and displayed on the service terminal 40.

The user terminal 60 is provided with a code acquisition unit 61 and a payment control unit 62 as logical devices realized by combining the computer hardware and the computer program Pt2. The code acquisition unit 61 controls a camera (not shown) of the user terminal 60 to take a picture of the two-dimensional code 100, and acquires the essential information IFa included in the two-dimensional code 100. The payment control unit 62 adds a user authentication code, payment method information, and the like to the essential information IFa acquired by the code acquisition unit 61 to generate payment information IFb, and uses the obtained payment information IFb as a payment execution server. It executes various processes necessary for payment of a fee such as sending to 30.

The management terminal 50 is also provided with an appropriate logical device depending on the combination of the computer hardware and the computer program, but the management terminal 50 provides information such as payment terms necessary for creating a script for the back office server 10. It may function as a terminal device for inputting information, and for example, it may be provided so as to access a Web page provided by the back office server 10 via a Web browser or the like and input information. This type of mechanism is well known and details will be omitted in FIG.

7 to 9 are flowcharts showing an example of a procedure executed to provide a payment service in the payment system 1 shown in FIG. FIG. 7 is a specific example of the procedure up to the issuance of the two-dimensional code illustrated in FIG. 3, and FIGS. 8 and 9 are specific examples of the procedure after the display of the two-dimensional code illustrated in FIG. In the procedure of FIG. 7, first, information such as an item code is transmitted from the item management server 80 to the management terminal 50 (or may be the service terminal 40) (step S11), and is received by the management terminal 50. Information that specifies conditions necessary for creating a script based on the information is input and provided to the back office server 10 (step S12). The information in this case may be input on the management terminal 50 according to the guidance of the condition setting unit 11 of the back office server 10, for example.

Next, in the back office server 10, conditions for creating a script based on the information acquired from the management terminal 50 are set by the condition setting unit 11, and the condition setting unit 11 creates a script corresponding to the set conditions. Is requested to the script management server 20 (step S13). In response to this, the script creation unit 21 of the script management server 20 creates a script that matches the conditions (step S14), adds a serial number to the script (step S15), and the obtained script is the script database DB2. Is recorded in (step S16).

When a new script is recorded in the script database DB2, the serial number is provided from the script management unit 22 to the serial acquisition unit 12 of the back office server 10 (step S17), and the serial number is further provided to the service terminal 40. (Step S18). As an example, the serial number is provided to the service terminal 40 and stored on the service terminal 40 each time a script is created. However, the back office server 10 may store the serial number in association with the creation request in step S13, and the serial number may be provided to the service terminal 40 in response to a request from the service terminal 40. When a plurality of scripts are used properly, it is necessary to retain the serial number so that the serial number of the script corresponding to the payment generated by the service terminal 40 can be specified. For example, the back office server 10 specifies the serial number of the script corresponding to the payment service to be provided by the service terminal 40 in light of the conditions specified at the time of script creation, and provides the obtained serial number to the service terminal 40. Such processing may be performed.

In the service terminal 40, when payment is made in response to the purchase of a product or the like by the user, the payment content is determined by the payment control unit 41 (step S21), and then the code control unit 42 together with the payment content information. The two-dimensional code 100 is generated and displayed so as to include the serial number of the script for realizing the payment (step S22). The process of step S18 and the process of step S21 do not need to be continuous in time. For example, when the same script is repeatedly used for multiple payments while replacing the fixed value of the information, the serial number stored in the service terminal 40 or the back office server 10 is confirmed each time the payment is made. A two-dimensional code 100 may be created for each payment in combination with the payment contents to be made. When multiple scripts can be selectively applied to payments generated on the service terminal 40 because the payees are different, for example, specify which payee should be selected on the service terminal 40 and pay the payment. The two-dimensional code 100 may be created so that the corresponding serial number is included in the essential information IFa.

When the two-dimensional code 100 is displayed on the service terminal 40, the process proceeds to the procedure shown in FIG. In the procedure of FIG. 8, first, the camera or the like of the user terminal 60 is controlled by the code acquisition unit 61 of the user terminal 60 to take a picture of the two-dimensional code 100, and the essential information IFa included in the two-dimensional code 100, that is, The payment content information and the serial number are acquired by the code acquisition unit 61 (step S31). The acquired essential information IFa is passed to the payment control unit 62, and the payment control unit 62 adds a user authentication code to the essential information IFa as an example of terminal additional information (step S32). The user authentication code in this case is, for example, user authentication information used when the user uses the service of the service management server 90 by using the user terminal 60. If the user has authenticated the service management server 90 using the user terminal 60 and the user authentication information is held in the user terminal 60, the payment control unit 62 should add the user authentication information as a user authentication code. Just do it. However, the user may input the user authentication code at the stage of step S32, and if the user terminal 60 holds the user authentication code by the function of the computer program Pt2, the held user authentication code is the step. It may be added in S32.

Subsequently, the information in which the user authentication code is added to the essential information IFa is transmitted from the payment control unit 62 to the payment execution server 30 as an example of the primary information that is a part of the payment information IFb, and the payment processing is requested (step). S33). In the payment execution server 30 that receives the request, the payment execution unit 31 extracts the serial number included in the information acquired from the user terminal 60 and sends it to the script management server 20, and the script corresponding to the serial number is transmitted. Inquired (step S34). In the script management server 20, the script management unit 22 searches the script database DB2 using the serial number given by the payment execution server 30 as a key, so that the script corresponding to the serial number is selected (step S35). The selected script is provided from the script management unit 22 to the payment execution server 30 (step S36). As a result, the payment execution unit 31 of the payment execution server 30 specifies the script provided by the script management server 20 as a script to be executed. In step S35, it is confirmed whether or not the script selected by the script management unit 22 is within the expiration date, and if the expiration date has passed, the settlement process is terminated assuming that the corresponding script does not exist. You may. In this case, the payment execution server 30 may notify the service terminal 40 and the user terminal 60 that payment is not possible, and appropriate error processing may be executed on the respective terminals 40 and 60.

When a script is provided to the payment execution unit 31 of the payment execution server 30, a list of payment methods available for this payment is an example of selection information regarding the payment method information that is undecided by the script. It is provided from the payment execution unit 31 to the user terminal 60 (step S37). As described above, the list may be generated by describing the candidates for the payment means specified in advance in the script. When the candidate of the payment means is not specified in the script, the payment means that can be processed by the payment execution server 30 may be described in the list. The payment means that can be used by the payment execution server 30 is given to the payment execution server 30 in advance by, for example, a method of updating each time a processing program corresponding to the new payment means is added to the payment execution server 30. be able to. The payment control unit 62 of the user terminal 60 performs a process of causing the user to select a payment method from the provided list, and the payment execution server 30 is an example of secondary information whose selection result is a further part of the payment information IFb. Is transmitted to (step S38). At this time, a process of asking the user to confirm whether or not the payment process may be executed may also be performed, and the selection result of the payment method may be transmitted only when the user approves the payment execution.

When the selection result of the payment means is transmitted to the payment execution server 30, the payment execution unit 31 corresponds to the information included in the payment information IFb, that is, the user authentication code and the payment method (corresponding to the payment method selected by the user. ) And the confirmed value of the payment content are substituted into the script, all the information of the script is confirmed, and the payment processing is executed by the settlement execution unit 31 according to the confirmed script (step S39).

In the payment process, as an example, the payment execution unit 31 notifies the account management server 70 of the user authentication code and the payment amount, and the account management server 70 is requested to perform payment processing in electronic currency, and the account management server responds accordingly. 70 is realized by subtracting the balance of the electronic currency of the account corresponding to the user authentication code according to the payment amount (step S40). After that, the payment process proceeds to the procedure shown in FIG. 9, and the account management server 70 notifies the payment execution server 30 of the result of the payment process (step S42). If the payment is completed normally, the payment notification unit 32 of the payment execution server 30 notifies the item management server 80 of the payment completion with information such as the payee and the payment details (step S43), and the item management server. At 80, the payment record is recorded in response to the notification (step S44). Further, the payment result is also notified from the payment notification unit 32 to the service terminal 40, the user terminal 60, and the service management server 90 (step S45). As for the notification to the service terminal 40, for example, the back office server 10 manages the issuance status of the two-dimensional code 100 on the service terminal 40, and the payment execution server 30 notifies the back office server 10 of the payment result to the back office server. 10 may be realized by determining the service terminal 40 of the notification destination and transferring the payment result to the determined service terminal 40. Alternatively, in the script shown in FIG. 2, a notification destination of the payment result is added and a fixed value of the notification destination is recorded in advance when the script is created, or when the service terminal 40 generates the two-dimensional code 100. By including the fixed value of the information of the notification destination, the payment execution server 30 may be able to specify the service terminal 40 to be the notification destination. When the information of the notification destination is included in the script, for example, when the payment destination and the notification destination are different, there is an advantage that the processing to the payment destination and the processing to the notification destination can be separately executed.

Upon receiving the notification of the payment result, the payment control unit 41 of the service terminal 40 starts a predetermined process that should be permitted on condition that the payment of the fee is completed as a subsequent process (step S46). For example, a process such as permission to play a game or issuance of a ticket may be started as a subsequent process. The user terminal 60 notifies the user that the payment has been completed (step S47). Further, the service management server 90 executes a predetermined process that should be permitted on condition that the payment of the fee is completed as a related process (step S48). For example, a process associated with payment of a fee may be executed on the service management server 90 as a related process, such as giving a privilege to a user for a service provided by the service management server 90. In any case, the service terminal 40 may be configured to provide various services such as a game service and a ticket issuing service to the user when the result notified from the payment execution server 30 indicates the completion of payment.

According to the above form, in the script held in the script database DB2, information such as the user and payment details to be confirmed each time a payment is made is undecided, and the information to be confirmed when the payment is made is provided as a service. The script information is determined by appropriately adding it to the terminal 40 or the user terminal 60. Therefore, if the information to be confirmed in common among a plurality of payments is described in a script in advance and recorded in the script database DB2, one script held in the script database DB2 will be generated within the expiration date. It can be used repeatedly in multiple payments. This has the advantage that the load on the script management server 20 required for script creation can be reduced, or the amount of information to be recorded in the script database DB2 can be reduced.

In the first embodiment, the code control unit 42 functions as an example of the information image display means by executing the process of step S22 of FIG. 7, and the code acquisition unit 61 executes the process of step S31 of FIG. The payment control unit 62 functions as an example of the payment information providing means by executing the processes of steps S32, S33 and S38 of FIG. 8, and the payment execution unit 31 functions as an example of the payment information providing means. By executing the process of S39, it functions as an example of the payment execution means, and by executing the process of step S45 of FIG. 9, the payment notification unit 32 functions as an example of the result information providing means. Further, the payment control unit 62 functions as an example of the primary information providing means by executing the processes of steps S32 and S33 of FIG. 8, and the payment control unit 62 executes the process of step S38 of FIG. It functions as an example of the information providing means, and the payment execution unit 31 functions as an example of the selected information providing means by executing the process of step S37 in FIG. Further, the service management server 90 functions as an example of the related process execution means by executing the process of step S48 in FIG.

In the above embodiment, the serial number of the script is illustrated as the processing information to be recorded in the two-dimensional code 100 on the service terminal 40, but the script itself may be set as the processing information. An example thereof is shown in FIG. In the example of FIG. 10, the script illustrated in FIG. 2 is provided from the script management server 20 to the service terminal 40, and the service terminal 40 adds information such as the payment amount as fixed information regarding the payment content to generate essential information IFa. The essential information IFa is recorded in the two-dimensional code 100. That is, the script itself is recorded as processing information in the two-dimensional code 100. In the user terminal 60 that has read the two-dimensional code 100, a user authentication code is added as confirmed information about the user, primary information that is a part of the payment information IFb is generated, and the primary information is provided to the payment execution server 30. .. Further, when the payment method is selected by the user terminal 60 based on the list of payment methods transmitted from the payment execution server 30, secondary information that is a further part of the payment information IFb is generated, and the secondary information is generated. The information is provided to the payment execution server 30. Therefore, the settlement execution server 30 can specify the script to be executed and execute the processing according to the script without inquiring to the script management server 20. The script recorded in the two-dimensional code 100 may be in a compressed or encrypted state by a recoverable method.

In the above form, the service provider can request the creation of the script by using the management terminal 50, but instead of or in addition, the administrator of the script management server 20 uses the management terminal 50. You may instruct to create a script. Alternatively, the service terminal 40 may instruct the creation of a script. In that case, the management terminal 50 can be omitted.

(Second form)
In the first mode described above, a script is created according to the information from the management terminal 50 prior to the occurrence of payment in the service terminal 40, and this is stored in the script database DB2 in advance, but it is time to create the script. Is not limited to such an example. For example, it is possible to create a script when payment occurs at the service terminal 40. Hereinafter, an example of the payment system according to the second embodiment in which such a change has been made will be described with reference to FIGS. 11 to 13. The example described below is a partial modification of the processing in the payment system 1 shown in FIG. In FIGS. 11 to 13, the same reference numerals are given to the parts common to those in FIGS. 1 to 9, and the differences will be mainly described below.

In the payment system 1A of FIG. 11, the processing procedure from the creation of the script to the issuance of the two-dimensional code 100 is different. In the service system 1A of FIG. 11, when the user selects a product or service to be purchased, a process related to script creation is disclosed. However, prior to the processing, information related to script creation may be provided from the management terminal 50 to the back office server 10 or to the script management server 20 via the back office server 10. (F50). The information provided at this point may be information that should be commonly used within an appropriate range such as a facility such as a store where the service terminal 40 is installed or a service provider. Information specifying the type of payment means that the service provider wants the user to use may be provided from the management terminal 50 to the back office server 10. However, such information may be provided at the same time as the information is provided from the service terminal 40, which will be described later, and the information provision from the management terminal 50 may be omitted. Further, the item code, unit price, etc. required for creating the script may be provided from the item management server 80 to the service terminal 40 or the management terminal 50 (F51). If the information is given to the service terminal 40 or the management terminal 50 by a means other than the provision from the item management server 80, the provision from the item management server 80 is unnecessary.

When the user operates the service terminal 40 to select a product or service to be purchased, the service terminal 40 provides the back office server 10 with information necessary for creating a script for paying the fee for the product or service (the service terminal 40 provides the back office server 10 with information necessary for creating a script. F52). For example, information on the payee, payment method, expiration date, or comment may be provided to the back office server 10. A plurality of payment methods may be specified as the payment method. The back office server 10 temporarily stores the obtained information as default setting information. However, for a part of this information, for example, the payee, the payment method, etc., the store where the service terminal 40 is installed or the service provider who operates the service terminal 40 sets a common value regardless of individual payments. In the case, such information may be given from the management terminal 50 to the back office server 10 in advance.

Next, when the user requests the service terminal 40 to purchase, the back office server 10 is provided with payment content information such as payment items, unit price, and quantity, and terminal identification information for identifying the service terminal 40. (F53). As a result, in the script shown in FIG. 2, information other than the user, serial number, and payment method information is gathered on the back office server 10 in a state where the values are fixed. When multiple types of payment methods are specified as payment methods, the payment methods are in an undetermined state. After that, the back office server 10 requests the script management server 20 to create a script together with the default setting information and the information provided from the service terminal 40 (F54). The script management server 20 creates a script according to the information obtained from the back office server 10, adds a serial number to the script, and records the script in the script database DB2. The script saved at this stage is recorded with all the information other than the user and payment method information confirmed. Then, the serial number of the created script is provided to the service terminal 40 (F55). On the service terminal 40, the two-dimensional code 100 is displayed so that only the obtained serial number is included as essential information (F56).

Since the procedure after the essential information included in the two-dimensional code 100 is read by the user terminal 60 is the same as that in FIG. 4, details are omitted. However, in this example, as shown in FIG. 12, the user terminal 60 that has read the two-dimensional code 100 adds the user authentication code to the serial number as the essential information IFa to generate the payment information IFb. The payment information IFb is transmitted to the payment execution server 30. In the script recorded in the script database DB2, all the information other than the user authentication code and the payment method is recorded in a fixed state, so that the payment execution server 30 is a user terminal based on the script provided by the script management server 20. By providing a list of payment methods to 60 and letting the user select a payment method, acquiring information on the selected payment method and a user authentication code from the user terminal 60 and substituting those values into the script, the script Confirm all information. Thereby, it is possible to execute the payment process.

FIG. 13 shows a specific example of the procedure up to the issuance of the two-dimensional code 100 in the payment system 1A of FIG. 11 corresponding to FIG. 7. The specific configuration of the payment system 1A for executing each process of FIG. 13 may be the same as that of FIG. 6, and it is assumed that each process of FIG. 13 is executed based on the configuration shown in FIG. The processing procedure will be described. In the procedure of FIG. 13, first, the advance information is transmitted from the management terminal 50 to the back office server 10 (step S10), and the item from the item management server 80 to the service terminal 40 (or may be the management terminal 50). Transmission of a code or the like is executed (step S11). However, as described above, these processes may be omitted as appropriate.

When the user selects a product or service on the service terminal 40, certain information such as the payee is provided from the payment control unit 41 of the service terminal 40 to the back office server 10 (step S12A). At this stage, information may be provided that specifies one or more types of payment methods with respect to the payment method. The information may be provided in advance in step S10. The condition setting unit 11 of the back office server 10 stores the obtained information as default setting information in a storage device (not shown) of the back office server 10 (step S12B). After that, when the user confirms the purchase with respect to the service terminal 40, the payment control unit 41 of the service terminal 40 provides information on the payment contents such as the payment item, unit price, and quantity confirmed at that time, and the payment method. Information indicating options for the service terminal 40 and terminal identification information for identifying the service terminal 40 are provided to the back office server 10 (step S12C). In the back office server 10, the condition setting unit 11 requests the script management server 20 to create a script while designating the information stored in step S12B and the information transmitted in step S12C as script creation conditions. (Step S13A).

When the script creation is requested, the script creation unit 21 of the script management server 20 creates a script that matches the creation conditions (step S14), adds a serial number to the script (step S15), and obtains the script. The script is recorded in the script database DB2 (step S16). In the script recorded in this case, as described above, the information on the user and the payment method is undecided, and all other information is in a fixed state. However, if one type of payment method is specified as the payment method, the payment method information is substantially fixed at this point.

When a new script is recorded in the script database DB2, the serial number is provided from the script management unit 22 to the serial acquisition unit 12 of the back office server 10 (step S17), and the serial number is further provided to the service terminal 40. (Step S18). In response to the provision, the service terminal 40 generates the two-dimensional code 100 so that the code control unit 42 records the essential information IFa including only the serial number given via the back office server 10. Is displayed (step S22).

When the two-dimensional code 100 is displayed on the service terminal 40, processing such as provision of payment information IFb from the user terminal 60 to the payment execution server 30 is performed thereafter, and these processes are the same as those in FIGS. 8 and 9. However, the details thereof will be omitted. However, the information added by the user terminal 60 is only the information that specifies the user authentication code and the payment method selected by the user as the payment method. Further, when the payment process is completed, a process for deleting the script used for the settlement process may be added even if it is within the expiration date.

According to the second form, a new script is created each time a payment is made at the service terminal 40. Therefore, when creating a script, it is possible to create a script in a state where more information is confirmed as compared with the first form. Therefore, it is advantageous to reduce the information to be recorded in the two-dimensional code 100, simplify the two-dimensional code 100, and standardize the two-dimensional code 100 among a plurality of types of payment services. The code control unit 42 of the service terminal 40, the code acquisition unit 61 and the payment control unit 62 of the user terminal 60, the payment execution unit 31 of the payment execution server 30, and the payment notification unit 32 in the payment system 1A according to the second mode It functions as an example of means similar to the first embodiment.

In the second embodiment, the information (step S12A) transmitted in advance from the service terminal 40 is stored in the back office server 10, and the information (step S12C) transmitted thereafter is combined with the user authentication code of the script. After preparing the information other than the above, the script management server 20 was requested to create the script, but the information was temporarily held on the service terminal 40 according to the user's purchase operation, and the information other than the user authentication code was prepared. At this point, the service terminal 40 may request the script management server 20 to create a script. In this case, the back office server 10 may be omitted. Further, the management terminal 50 may be omitted as appropriate if it is not necessary to provide information to the back office server 10. Further, also in the second embodiment, as the essential information IFa to be recorded in the two-dimensional code 100, the script itself may be recorded as in FIG. 10 instead of the serial number.

In the first and second forms described above, the back office server 10, the script management server 20, and the payment execution server 30 are separately provided, but the configuration is only an example, and these are appropriately integrated. May be good. The back office server 10 may be omitted, and the service terminal 40 or the management terminal 50 may directly access the script management server 20. The service terminal 40 does not necessarily have to be configured as a single terminal device. For example, by linking a plurality of terminal devices, a set of these terminal devices may function as one service terminal.

As the information to be included in the essential information, appropriate information may be selected as long as the information is commonly required by the server regardless of the type of payment means. For example, in the first form, the payee information is information commonly required by the server regardless of the type of payment method, but in the first form, the information for confirming this is held in the script database DB2. Since it is described in advance in the script, it is not necessary to record the payment destination information in the two-dimensional code 100 on the service terminal 40 side. However, the first form may be modified so that the payment destination information is recorded in the two-dimensional code 100 on the service terminal 40 side. In this case, it is not necessary to create scripts separately from the viewpoint of different payees, and there is a possibility that a common script can be used between different payees. Also in the second embodiment, the two-dimensional code 100 may include a fixed value of a part of the information described in the script. For example, in addition to the serial number, a fixed value of the payment amount may be recorded in the two-dimensional code 100. In this way, what kind of information should be recorded as essential information for the information image to be displayed on the service terminal is as long as the types of information to be recorded in the information image can be standardized regardless of the difference in services. It may be changed as appropriate in.

In the above form, the two-dimensional code 100 is used as an example of the information image, but the information image is not limited to the two-dimensional code and can be used in various formats as long as the essential information can be recorded in a manner that can be acquired by the user terminal 60. It may be provided to record information.

In the above mode, the settlement execution server 30 executes the settlement process in cooperation with the account management server 70, and notifies the item management server 80 and the service management server 90 of the result of the settlement process, and these servers 80 and 90 use the settlement execution server 30. Although it is assumed that the related processing is executed, for example, the servers 80 and 90 are not indispensable for executing the processing for providing the payment service, and are used in the payment service to be provided by the payment terminal. It may be added, changed or deleted as appropriate according to the type of payment means to be used and the content of the processing to be executed by the server in order to realize the payment processing by the payment means. Further, the payment execution server 30 does not necessarily have to be configured to execute the payment processing in cooperation with other servers exemplified as the account management server 70. For example, the payment execution server 30 itself may be able to execute the payment process by itself, such as managing the balance of the user's electronic currency.

(Third form)
Next, a third embodiment of the present invention will be described with reference to FIGS. 14 to 17. In each figure, the same reference numerals are given to the parts common to the first embodiment, and the differences will be mainly described below. FIG. 14 shows a schematic configuration of the payment system 1B according to the third embodiment. The payment system 1B of the present embodiment is configured to select any one of the payment services from a plurality of types of payment services and proceed with the payment processing without using the script in the first or second form.

As shown in FIG. 14, the payment system 1B displays the two-dimensional code 100 on the service terminal 40 operated by the service provider, and the two-dimensional code 100 is displayed on the user terminal 60 used for the personal use of the user. It is common with the payment system 1 of the first and second forms in that the recorded essential information is read and the payment process is executed. However, the back office server 10 and the script management server 20 in the first and second forms are omitted. The management terminal 50 may be appropriately provided as needed, for example, for management and setting of the service terminal 40, or for exchanging information with the payment execution server 30A. Further, although not shown in FIG. 14, the item management server 80 in FIG. 1 may be appropriately provided as needed, for example, to provide information to the service terminal 40 side. The account management server 70 and the service management server 90 are the same as those in the first and second forms. Similar to the first and second forms, the account management server 70 is a server that manages the balance of an account of a specific type of electronic currency in association with user identification information, and electronically cooperates with the payment execution server 30A. This is an example of a server that processes currency payments. The server that the payment execution server 30A cooperates with in the payment processing is not limited to the account management server 70 shown in the figure, but is a server that manages other types of electronic currencies, a server that processes the withdrawal of charges from a bank account, and payment by credit card. The server or the like that processes the above may be used properly. The payment execution server 30A is pre-implemented with a group of computer programs that describe procedures for processing payments with a server that is a cooperation partner, and these computer programs are used to select a payment method that should be used for payment of charges. It is executed as appropriate according to. Further, the payment execution server 30A is provided with information in advance for specifying a payment method that can be processed, that is, a payment means that can be used for payment of charges. The information may be given, for example, as information on a list of payment means provided to the user terminal 60 in the first and second forms.

FIG. 15 shows an example of how information is transmitted from the service terminal 40 in the payment system 1B to the payment execution server 30A via the user terminal 60. In the illustrated example, first, the two-dimensional code 100 generated by the service terminal 40 (the store terminal 40B is shown in the figure, but other service terminals may be used) requires information on the payee and the payment details IFaA. Included in. The payment destination is included because the payment destination can be changed as appropriate according to the convenience of the service provider, the products to be sold, the type of service, etc. each time payment is made on the service terminal 40. This is because it is convenient for the service terminal 40 to specify the payment destination in order to deal with the circumstances of individual payments. However, when it is not necessary to consider the difference in the payment destination between the service terminals 40, for example, the payment destination is fixedly determined according to the payment method, the payment execution server 30A is notified in advance of the payment destination. By giving the information, the information of the payee may be omitted from the essential information IFaA.

In the user terminal 60 that has read the two-dimensional code 100, the user authentication code and the payment are added as confirmation information to the information of the payee and the payment contents included in the two-dimensional code 100, and the payment information IFbA is generated. The obtained payment information IFbA is transmitted to the payment execution server 30A. However, it is not essential that the payment information IFbA is transmitted all at once. For example, information other than the payment method, for example, a user authentication code is transmitted prior to the payment execution server 30A as an example of primary information, and the payment method information is sent to the user based on the payment method list provided by the payment execution server 30A. It is confirmed by having the payment means selected, and after the confirmation, untransmitted information may be transmitted from the user terminal 60 to the payment execution server 30A. Prior to the transmission of the user authentication code or the like, a list of payment means is acquired from the payment execution server 30A, and the payment means is selected by the user according to the list to determine the payment information IFbA, and the obtained payment information IFbA is used. It may be collectively transmitted to the payment execution server 30A. The payment execution server 30A executes the payment process according to the payment information IFbA acquired from the user terminal 60.

FIG. 16 shows an example of a specific configuration relating to a main part of the payment system 1B. In the example of FIG. 16, the payment execution server 30A is provided with the payment execution unit 31A and the payment notification unit 32 as logical devices realized by the combination of the computer hardware and the computer program Ps3A. The payment execution unit 31A provides the user terminal 60 with a list of payment means, or executes the payment process in cooperation with the account management server 70 or the like according to the payment information received from the user terminal 60. The payment notification unit 32 is similar to that of the first and second forms in that it notifies the service terminal 40 and the like of information on the result of the payment processing executed by the payment execution unit 31A.

The service terminal 40 is provided with a payment control unit 41 and a code control unit 42A as logical devices realized by combining the computer hardware and the computer program Pt1A. The payment control unit 41 is similar to that of the first form. The code control unit 42A acquires the payment content to be included as a part of the essential information IFaA in the two-dimensional code 100 from the payment control unit 41, and obtains the obtained information and the payment destination information given in advance to the service terminal 40. At the same time, the essential information IFaA is generated, and the two-dimensional code 100 is generated based on the obtained essential information IFaA and displayed on the service terminal 40.

The user terminal 60 is provided with a code acquisition unit 61 and a payment control unit 62A as logical devices realized by combining the computer hardware and the computer program Pt2A. The code acquisition unit 61 is the same as that of the first form. The payment control unit 62A generates payment information IFbA by adding a user authentication code, payment method information, etc. to the essential information IFaA acquired by the code acquisition unit 61, and uses the obtained payment information IFbA as a payment execution server. It executes various processes necessary for payment of a fee such as sending to 30.

FIG. 17 is a flowchart showing an example of a processing procedure executed for providing a payment service in the payment system 1B shown in FIG. In the procedure of FIG. 17, the payment content of the user is first determined by the payment control unit 41 of the service terminal 40 (step S21), and the two-dimensional code 100 is generated and displayed by the code control unit 42A (step S22). ). These procedures are the same as the processes of steps S21 and S22 of FIG. 8, but the essential information IFaA recorded in the two-dimensional code 100 includes information on the payee and the payment contents as illustrated in FIG.

In parallel with the processing in the service terminal 40, the payment control unit 62A of the user terminal 60 performs the user authentication processing (step S30). This process may be a local process in which the user terminal 60 inputs a user authentication code to identify the user, or the user terminal 60 and the service management server 90 cooperate to authenticate the user. It may be a process. When the user authentication process is completed, the code acquisition unit 61 acquires the essential information IFaA included in the two-dimensional code 100 (step S31), and the payment control unit 62A obtains the essential information IFaA in the user authentication process of step S30. The user authentication code is added to the essential information IFa as an example of the terminal additional information (step S32), and the obtained information is a part of the payment information IFbA. The payment control unit 62 gives the payment execution server as an example of the primary information. It is transmitted to 30A and a payment process is requested (step S33).

In the payment execution server 30A, a list of payment means that can be used in the current payment processing is provided from the payment execution unit 31 to the user terminal 60 as an example of selection information (step S37A). This list may be basically determined based on the information transmitted in step S33 as in the first embodiment. However, since the script in the first form is not used in the third form, it is not possible to describe the candidates for the payment means in advance in the script and provide those candidates as a list. However, for example, if information for specifying a payment destination or a payment method that can be used in association with a payment method is given to the payment execution server 30A in advance, it can be used in the current payment process based on the information transmitted in step S33. It is possible to discriminate a payment means, generate a list of payment means according to the determination result, and provide the payment means to the user terminal 60. On the other hand, regardless of the information transmitted in step S33, the user terminal 60 may be provided with a list of payment means that can be processed by the payment execution server 30A.

The payment control unit 62A of the user terminal 60 that has received the list performs a process of causing the user to select a payment method from the provided list, and the selection result is an example of secondary information that is a further part of the payment information IFbA. It is transmitted to the payment execution server 30A (step S38). These processes are also the same as those in the first and second forms. A process of asking the user to confirm whether or not the payment process may be executed may also be performed, and the selection result of the payment method may be transmitted only when the user approves the payment execution.

When the payment execution method selection result is transmitted to the payment execution server 30A, the payment execution unit 31A refers to the information included in the payment information IFbA, that is, the user authentication code, the payment method, and the payment content. The payment process is executed by (step S39). Similar to the first mode, the payment process may be performed in cooperation with the account management server 70 or the like according to the payment method included in the payment information IFbA (step S40). When the payment process is executed, the account management server 70 notifies the payment execution server 30A of the result of the payment process (step S42), and the payment notification unit 32 of the payment execution server 30A notifies the service terminal 40, the user terminal 60, and the service management. The payment result is notified to the server 90 (step S45). If the payment is completed normally, the payment control unit 41A of the service terminal 40 starts a predetermined process that should be permitted on condition that the payment of the fee is completed (step S46), and the user terminal 60 pays. The process of notifying the user that the process has been completed is executed as an example of the subsequent process (step S47). Further, the service management server 90 executes a predetermined process that should be permitted on condition that the payment of the fee is completed as a related process (step S48). These subsequent processes or related processes may be carried out in the same manner as in the first and second embodiments.

In the embodiment shown in FIGS. 16 and 17, the code control unit 42A functions as an example of the information image display means by executing the process of step S22 of FIG. 17, and the code acquisition unit 61 processes the process of step S31 of FIG. The payment control unit 62A functions as an example of the payment information providing means by executing the processes of steps S32, S33 and S38 of FIG. 17, and the payment execution unit 31A functions as an example of the payment information acquisition means. By executing the process of step S39 of FIG. 17, it functions as an example of the payment execution means, and by executing the process of step S45 of FIG. 17, the payment notification unit 32 functions as an example of the result information providing means. Further, the payment control unit 62A functions as an example of the primary information providing means by executing the processes of steps S32 and S33 of FIG. 17, and the payment control unit 62A executes the process of step S38 of FIG. 17 to perform the secondary. It functions as an example of the information providing means, and the payment execution unit 31A functions as an example of the selected information providing means by executing the process of step S37A of FIG. Further, the service management server 90 functions as an example of the related process execution means by executing the process of step S48 in FIG.

Also in the third embodiment described above, appropriate modifications or changes can be made. For example, even in the third embodiment, the information image is not limited to the two-dimensional code 100, and images in various formats may be used as the information image. The service management server 90 may also be added, changed or deleted as appropriate.

Further, a modified example applicable to any of the first to third forms will be illustrated below.

In each form, the service terminal 40 also functions as a payment terminal, but the service terminal and the payment terminal may be provided as different terminal devices. In that case, the service terminal and the payment terminal may be linked so that the provision of the service on the service terminal is controlled according to the result of the payment processing received by the payment terminal. In short, the service terminal need only be one that operates in association with the payment terminal, and both terminals may be realized by the same device or may be provided as separate devices that operate in association with each other.

In each form, each time a payment is made, the payment execution servers 30 and 30A provide the user terminal 60 with a list of payment means as an example of selection information, but the timing of providing the selection information is not necessarily the time for each payment. It does not have to be at the time of occurrence. For example, every time the selection information is updated on the payment execution servers 30 and 30A, or periodically, the selection information is distributed from the payment execution servers 30 and 30A to the user terminal 60, and the user terminal 60 owns itself at the time of individual payment. The user may be made to select the payment method by referring to the selection information stored in the storage device. For example, when a mechanism for appropriately distributing the update module of the computer programs Pt2 and Pt2A to be implemented in the user terminal 60 from the payment execution server 30, 30A or another server is provided, the update module is selected by using the distribution. Information can be given to the user terminal 60 in advance. In short, the process of providing the selection information to the user terminal 60 each time the payment process occurs is not essential, and as long as the user terminal 60 can select the payment method at the time of the payment, the selection information is in an appropriate manner. May be given to 60. Therefore, as described above, it is not essential that the payment information IFb and IFbA are transmitted from the user terminal 60 separately into the primary information and the secondary information, and when the selection information already exists in the user terminal 60, it is not essential. It is also possible to collectively transmit payment information IFb and IFbA.

On the other hand, in each form, the payment execution servers 30 and 30A can be used based on the primary information in relation to transmitting the payment information IFb and IFbA from the user terminal 60 separately into the primary information and the secondary information. The possibility of discriminating the types of payment means and providing a list of payment means as selection information to the user terminal 60 according to the judgment result has been described. For example, in the first and second forms, it is possible to specify a script according to a serial number and generate a list based on the candidates for payment means described in the script. In the third mode, it is possible to generate a list of payment means based on the payee, the payment content, and the like. Instead of or in addition to this, it is also possible to determine a candidate for payment means by using user identification information such as a user authentication code and provide selection information. In such a process, for example, the user identification information and the selection information are associated with each other and held in the payment execution servers 30 and 30A, and the selection information corresponding to the user identification information acquired from the user terminal 60 is provided to the user terminal 60. It can be realized by. In that case, the candidate for the payment method that the user wants to use is specified in advance by the user to the payment execution servers 30 and 30A via the user terminal 60, and the specified content is associated with the user identification information such as the user authentication code for payment. It may be held in the execution servers 30 and 30A. Furthermore, it is also possible to set a default value for the type of payment means or set a priority in association with the user identification information. In this case, it is possible to enhance the convenience of the user regarding the selection of the payment method. The default settings and the like may be processed based on instructions from the user, or may be automatically processed based on the user's usage history and the like.

Alternatively, the service terminal 40 may be divided into groups in appropriate units, and the selection information may be differentiated according to the groups. Such groups may be distinguished for each individual service terminal 40, or may be distinguished according to the differences in service providers. As an example, the service terminals 40 may be divided into groups for each store operated by the service provider, and the selection information may be differentiated for each store. In this case, if a service provider or the like is made to specify a candidate for a payment method that can be used as a payment method for each group, and the specified contents are associated with the identification information of the group and stored in the payment execution servers 30 and 30A. Good. However, when the user terminal 60 is requested to provide the selection information, it is necessary to determine which group the selection information should be provided. Therefore, the two-dimensional code 100 includes the group identification information. It is necessary to include it as a part of essential information and provide it from the user terminal 60 to the payment execution servers 30 and 30A.

In each of the above forms, as an example of the related processing, for example, an example of giving a privilege to the user for the service provided by the service management server 90 has been given, but the related processing is not limited to this. For example, in the third embodiment, when the user authentication process in step S30 of FIG. 17 is a local process, the user may not have completed user authentication with respect to the service management server 90. On the other hand, the payment execution server 30A has acquired the user authentication code in the process of step S31. Therefore, as the related process in step S48, the payment execution server 30A can provide the user authentication code to the service management server 90, and the service management server 90 can execute the user authentication process as a kind of related process. In this case, when the payment system 1A completes the payment for the use of the service terminal 40, the user authentication on the service management server 90 is completed in conjunction with the payment. Therefore, the user can use the service terminal 40 while using the service provided by the service management server 90 when the fee is paid, without requiring the service management server 90 to authenticate the user separately. Convenience is improved. For example, when the service management server 90 provides a service such as transmission of play data to the game machine 40A on condition of user authentication, the user can provide the service of the service management server 90 without requiring separate user authentication after the payment of the fee is completed. It is possible to use the game machine 40A while using it. Such a modification can be similarly applied to the payment systems 1 and 1A of the first and second forms.

Further, the service identification information for identifying the service provided by the service terminal 40 is included in the two-dimensional code 100 as a part of the essential information, and this is included in the payment execution server as a part of the payment information from the user terminal 60. It may be provided to 30 and 30A. Alternatively, the user terminal 60 may add the service identification information as a part of the payment information and provide the service identification information to the payment execution servers 30 and 30A. In that case, the payment execution servers 30 and 30A can determine what kind of service the payment processing is for according to the service identification information. Therefore, the process associated with the service identification information can be executed by itself as a kind of related process, or can be executed by a server of the cooperation partner such as the service management server 90. For example, when the service provided by the service terminal 40 is determined to be the game service in the game machine 40A, it is possible to execute a process specific to the game service.

In the payment systems 1, 1A and 1B of each form, the payment processing is performed by the payment execution servers 30 and 30A, so that the payment execution servers 30 and 30A can generate information for grasping the sales of each service terminal 40. it can. On the other hand, the service terminal 40 may be equipped with a mechanism that enables the collection of charges in cash, for example, and the payment execution servers 30 and 30A complete the payment on the service terminal 40 side, that is, the payment systems 1, 1A. It is not possible to grasp the sales based on the settlement that does not go through 1B. In such a situation, for example, when it is necessary to manage the sales by the payment through the payment systems 1, 1A and 1B and the sales by the payment completed by the service terminal 40 in total, for example, FIG. As shown in, a mechanism may be provided on the server side to add up and aggregate sales. In the example of FIG. 18, the game machine 40A as an example of the service terminal 40 is provided with a charge collecting device 43 for processing the charge payment in cash as an example of the charge collecting means, and the item management server 80 manages the sales. Works as an example. In this case, in the game machine 40A, the amount of the charge collected through the charge collection device 43 is generated as store sales information, and the obtained information is provided to the item management server 80 in a timely manner. On the other hand, the payment execution server 30 provides system sales information to the item management server 80 each time a payment process is performed. The system sales information may be, for example, the information notified in step S43 of FIG. In the item management server 80, based on the obtained store sales information and system sales information, the charges collected by the game machine 40A and the charges collected via the payment system 1 are added up to generate aggregated information. Will be done. The aggregated information may be generated or updated at an appropriate cycle such as once a month. In addition, the total of sales may be performed in units of an appropriate set such as a store in which the service terminal 40 is installed. The server that aggregates sales is not limited to the item management server 80, and an appropriate server may be in charge. Although FIG. 18 cites the first form as an example, such a modification can be similarly applied to the second and third forms.

Various aspects of the present invention derived from each of the above-described embodiments and modifications are described below. In the following description, in order to facilitate understanding of each aspect of the present invention, the corresponding components shown in the accompanying drawings are added in parentheses, thereby limiting the present invention to the illustrated form. It's not something.

The payment system (1; 1A; 1B) according to one aspect of the present invention is a client server system including a server (30; 30A), a user terminal (60) that functions as a client for the server, and a payment terminal (40). The information required for the payment process, which is constructed and included in the information image (100) presented by the payment terminal, is provided to the server via the user terminal, so that the fee payable by the user is settled. A payment system in which the payment process is executed by the server, and essential information (IFa; IFaA) commonly defined regardless of the type of payment method to be used for the payment is required for the payment process. The information image display means (42, S22; 42A, S22) for displaying the information image on the payment terminal so as to be included as information, and the user terminal for acquiring the essential information included in the information image. Information acquisition means (61, S31) and payment means to be used for payment from a plurality of types of payment means are selected by the user via the user terminal, and payment means identification for identifying the selected payment means. Payment information providing means (62, S32, S33) for transmitting payment information (IFb; IFbA) including information (information on a payment method as an example) and the essential information acquired by the information acquisition means from the user terminal to the server. , S38; 62A, S32, S33, S38) and the server, the payment means is identified based on the payment means identification information included in the payment information, and the essential information included in the payment information. The payment execution means (30, S39; 30A, S39) for executing the payment processing so that the payment according to the above is performed according to the identified payment means, and the result information indicating the result of the execution of the payment processing. It is provided with a result information providing means (32, S45) to be transmitted from the server to the payment terminal.

The computer program (Ps1 to Ps3, Pt1, Pt2; Ps3A, Pt1A, Pt2A) according to one aspect of the present invention includes a server (30; 30A), a user terminal (60) and a payment terminal (40) that function as clients for the server. ) Is constructed as a client server system, and information necessary for payment processing included in the information image (100) presented by the payment terminal is provided to the server via the user terminal. , A computer program applied to a payment system (1; 1A; 1B) in which a payment process for payment of a fee to be paid by a user is executed on the server, and a computer included in the payment system. An information image for displaying the information image on the payment terminal so that essential information (IFa; IFaA), which is commonly defined regardless of the type of payment means to be used for payment, is included as information necessary for the payment processing. It should be used for payment from a display means (42, S22; 42A, S22), an information acquisition means (61, S31) for causing the user terminal to acquire the essential information included in the information image, and a plurality of types of payment means. The payment means identification information (information on the payment method as an example) for causing the user to select the payment means via the user terminal and identifying the selected payment means, and the essential information acquired by the information acquisition means. Payment information providing means (62, S32, S33, S38; 62A, S32, S33, S38) for transmitting payment information (IFb; IFbA) including The payment means is identified based on the payment means identification information, and the payment process is executed so that the payment according to the essential information included in the payment information is performed according to the identified payment means. To function as a payment execution means (30, S39; 30A, S39) and a result information providing means (32, S45) for transmitting result information indicating the result of executing the payment process from the server to the payment terminal. It is composed of.

According to the above aspect, the payment terminal displays an information image so that essential information commonly defined regardless of the type of payment method to be used for payment is included as information necessary for payment processing. The user is made to select which type of payment method is used for payment via the user terminal, and the payment information including the selection result and the information included in the information image is transmitted from the user terminal to the server. Will be done. Therefore, the essential information to be recorded in the information image on the payment terminal side can be recorded in the information image in a common format regardless of which type of payment means is used. Therefore, even when a new payment service is introduced, it is not necessary to add a program that displays an information image containing unique information corresponding to the payment service on the payment terminal side, and it is dedicated to the new payment service. There is no need for capital investment such as installing hardware. On the other hand, to support the new payment service, the user terminal side adds a payment method corresponding to the new payment service as an option, and the server side executes the payment process according to the payment method corresponding to the new payment service. This can be achieved by adding a program to do so. As a result, it is possible to support various payment services while reducing the burden required on the payment terminal side.

The computer program according to one aspect of the present invention may be provided in a state of being stored in a storage medium. By using this storage medium, for example, by installing and executing the computer program according to the present invention on a computer, the system of the present invention can be realized by using the computer. The storage medium for storing the computer program may be a non-transient storage medium such as a CDROM.

In the above aspect, the required information may include information that specifies at least one of a fee to be paid by the user and a party to whom the fee is to be paid. The fee to be paid by the user or the information about the person to whom the fee should be paid is information that is commonly required regardless of the type of payment means in processing the payment. In addition, if the charge is not fixed, the charge changes each time a payment is made, so it is necessary to specify the charge from the payment terminal side. Even if the payment partner is not fixed, it is necessary to specify the payment partner from the payment terminal side each time payment is made. In such a case, the information about the charge or the payment partner is information that should be determined in common regardless of the type of payment method, and even if such information is included in the information image, the information is information regardless of the type of payment method. It is possible to standardize the image format, and it is possible to reduce the burden on the payment terminal side.

The payment information providing means includes primary information providing means (62, S32, S33; 62A, S32, S33) for transmitting primary information including the essential information from the user terminal to the server as a part of the payment information. A secondary information providing means (62, S38; 62A; S38) for transmitting secondary information including the payment means identification information from the user terminal to the server as a part of the payment information is provided on the server. Determines a payment means that can be used for payment according to the essential information based on the primary information, and uses the determined payment means as a payment means that can be selected as the payment means to be used for the payment. Selection information providing means (31, S37; 31A, S37A) for transmitting the indicated selection information to the user terminal is provided, and the secondary information providing means is said to be based on the selection information transmitted from the server. A payment means that can be used for payment according to essential information is presented to the user, the user is made to select any one payment means to be used for the payment, and the selected payment means identifies the payment means. The secondary information may be transmitted from the user terminal to the server so as to be identified by the information. According to this form, the selection information can be appropriately changed according to the primary information provided from the user terminal. Therefore, each time a payment is made, a candidate for a payment means suitable for the payment can be presented to the user so that the user can select one of the payment means.

The payment information providing means causes the user terminal to transmit the payment information from the user terminal to the server so as to include the user identification information for identifying the user of the user terminal, and the payment execution means is the user identification information. The settlement process may be executed with reference to the information stored in the server in association with. According to this, it is possible to execute the payment process by using various mechanisms for identifying the user and processing the payment.

In the above aspect, the payment system includes a service terminal (40) that is provided to operate in association with the payment terminal and provides a predetermined service to the user, and the service terminal transmits by the result information providing means. The service may be provided to the user when the result information to be given indicates that the settlement of the fee has been completed. According to this, it is possible to control the provision of the service by the service terminal in association with the completion of the payment by the payment system.

The payment information providing means causes the user terminal to transmit the payment information from the user terminal to the server so as to include the user identification information for identifying the user of the user terminal, and the user identification included in the payment information. The payment system may further include related process execution means (90, S48) for causing the server to execute the process associated with the information as a related process different from the payment process. According to this, it is possible to execute related processing different from the payment processing in parallel by using the user identification information provided to the server side for payment. Therefore, it is possible to omit the process of separately providing the user identification information from the user terminal to the server side in order to execute the related process, and it is possible to improve the convenience of the user.

The related process executing means may execute a process of authenticating the user with respect to the service of the service terminal as the related process. Alternatively, the related processing execution means may execute a process of identifying a user based on the user identification information included in the payment information and giving a privilege to the identified user as the related process. .. According to these forms, user authentication or granting of benefits to the user can be processed in conjunction with the payment process, so that the added value of the payment system can be increased.

The payment information providing means causes the user terminal to transmit the payment information to the server so as to include the service identification information for identifying the service provided by the service terminal, and is included in the payment information. A related processing execution means (90) for causing the server to execute the processing associated with the service identification information as a related processing different from the payment processing may be further provided. According to this, it is possible to increase the added value of the payment system by executing the processing peculiar to the service provided by the service terminal as the related processing in parallel with the payment processing.

The service terminal is provided with a charge collecting means (43) for collecting the charge from the user without using the payment process by the payment executing means, and the server is provided with the amount of the charge collected by the charge collecting means. May be provided as an aggregation means (80) that acquires the above-mentioned service terminal and aggregates the obtained charge amount and the charge amount settled in the payment process for each predetermined aggregation unit. According to this, even if the service terminal itself has a mechanism for collecting charges, the charges collected using the payment system and the charges collected by the service terminal are aggregated, and the sales obtained are collectively collected. It is possible to process it.

1,1A Payment system 30, 30A Payment execution server 31, 31A Payment execution unit (payment execution means, selection information providing means)
32 Payment notification unit (result information providing means)
40 Service terminal (payment terminal)
40A game machine 40B store terminal 41 payment control unit 42, 42A code control unit (information image display means)
43 Charge collection device (charge collection means)
60 User terminal 61 Code acquisition unit (information acquisition means)
62, 62A Payment control unit (payment information providing means, primary information providing means, secondary information providing means)
70 Account management server 80 Item management server (aggregation means)
90 Service management server (related processing execution means)
100 2D code (information image)

Claims (1)

The user terminal is constructed as a client-server system including a server, a user terminal that functions as a client for the server, and a payment terminal, and information necessary for payment processing included in an information image presented by the payment terminal is used for the user terminal. A payment system in which a payment process for settling a fee payable by a user is executed on the server by being provided to the server via the server.
An information image display means for displaying the information image on the payment terminal so that essential information commonly defined regardless of the type of payment means to be used for payment is included as information necessary for the payment processing.
An information acquisition means for causing the user terminal to acquire the essential information included in the information image, and
The payment means identification information for causing the user to select a payment means to be used for payment from a plurality of types of payment means via the user terminal and identifying the selected payment means and the payment means acquired by the information acquisition means. A payment information providing means for transmitting payment information including essential information from the user terminal to the server, and
The server is made to identify the payment means based on the payment means identification information included in the payment information, and the payment according to the essential information included in the payment information is performed according to the identified payment means. A payment execution means for executing the payment processing so as to be
A result information providing means for causing the server to transmit result information indicating the result of execution of the payment process to the payment terminal.
Payment system.

Images