Payment systems, POS terminals, and information processing programs

Abstract

To enable easily and flexibly performing treatments other than settlement according to needs of a settling person in a settlement.SOLUTION: According to an embodiment, a settlement system includes first, second and third acquisition means, display means, request means and processing means. The first acquisition means acquires an authentication code for a code settlement. The second acquisition means acquires setting made by a settling person about processing other than a settlement which can be performed in the code settlement. The display means displays, on a terminal device, the authentication code acquired by the first and second acquisition means and a barcode representing the setting. The third acquisition means acquires data represented by the barcode displayed by the display means. The request means requests a settlement server for the settlement along with notification of the authentication code represented by the data acquired by the third acquisition means. The processing means performs processing for treatments corresponding to the setting represented by the data acquired by the third acquisition means.SELECTED DRAWING: Figure 7

Description

Technical Field

[0004] , , , , , , , POS terminal , , ,

[0003] , , , Whether or not to issue a receipt , ,

[0005] , , ,

[0001] Embodiments of the present invention relate to a payment system, POS terminal and an information processing program.

Background Art

[0002] Customers may or may not need a receipt for a transaction. Therefore, a transaction processing device having a function of switching whether to issue a receipt according to an operation by a store clerk has been considered. However, the store clerk has to listen to the customer's request, which is troublesome for both the store clerk and the customer. Under such circumstances, it has been desired to easily and flexibly perform measures such as receipt issuance other than payment during payment according to the needs of the payer.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the present invention is to provide a payment system and an information processing program that can easily and flexibly perform measures other than payment during payment according to the needs of the payer. POS terminal and an information processing program.

Means for Solving the Problems

[0005] The payment system according to the embodiment includes a first acquisition unit, a second acquisition unit, a display unit, a third acquisition unit, a request unit, and a processing unit. The first acquisition unit acquires an authentication code for code payment. The second acquisition unit acquires during code payment Whether or not to issue a receiptThe settings of the payer are obtained. The display means displays a barcode on the terminal device that represents the authentication code obtained by the first acquisition means and the settings obtained by the second acquisition means. The third acquisition means obtains the data represented by the barcode displayed on the terminal device by the display means. The request means notifies the payment server of the authentication code represented by the data obtained by the third acquisition means. The price of the transaction The payment request is made. The processing means receives data obtained by the third acquisition means. If the setting is to issue a receipt, the process for issuing a receipt will be performed; if the setting is not to issue a receipt, the process for issuing a receipt will not be performed. . [Brief explanation of the drawing]

[0006] [Figure 1] A block diagram illustrating the schematic configuration of a transaction processing system according to one embodiment. [Figure 2] A block diagram showing the main circuit configuration of the POS terminal in Figure 1. [Figure 3] A block diagram showing the main circuit configuration of the user terminal in Figure 1. [Figure 4] A schematic diagram showing the data structure of the configuration data in Figure 3. [Figure 5] Transaction processing flowchart. [Figure 6] A flowchart for processing code payments. [Figure 7] A flowchart for processing code payments. [Figure 8] A diagram showing an example of the top screen. [Figure 9] A diagram showing an example of a settings screen. [Figure 10] This diagram shows an example of a barcode screen. [Modes for carrying out the invention]

[0007] An example of an embodiment will be described below with reference to the drawings. Figure 1 is a block diagram showing the schematic configuration of the transaction processing system 1 according to this embodiment. Transaction processing system 1 is a system for processing transactions related to the buying and selling of goods between customers and stores. As part of its transaction processing, transaction processing system 1 also processes the payment for the transaction. Thus, transaction processing system 1 also functions as a payment system.

[0008] The transaction processing system 1 is configured so that the POS terminal 100, user terminal 200, receipt server 300, and payment server 400 can communicate with each other via the communication network 2. Communication network 2 can use the internet, VPN (virtual private network), LAN, public communication network, mobile communication network, etc., individually or in appropriate combinations. As an example, communication network 2 may be a combination of the internet and a mobile communication network. Note that any number of POS terminals 100 and user terminals 200 may be included in the transaction processing system 1, but only one of each is shown in Figure 1.

[0009] The POS terminal 100 processes information to handle transactions according to operations performed by an operator at the store. The POS terminal 100 may be a face-to-face type where the store clerk is the primary operator, a fully self-service type where the customer is the primary operator, or a semi-self-service type where both the store clerk and the customer are the primary operators. The user terminal 200 is an information processing terminal owned by the customer. Typically, the user terminal 200 is owned by the customer and brought into the store for use by the customer. The user terminal 200 may also be an information and communication terminal lent to the customer by the store, or an information and communication terminal attached to a shopping cart provided as equipment in the store.

[0010] The receipt server 300 performs information processing to provide an electronic receipt service that allows customers to view electronic receipts that electronically represent the results of transactions at stores. The receipt server 300 also performs information processing to allow users of the electronic receipt service to use the code payment service provided by the payment server 400. The settlement server 400 performs information processing for settling the price of a transaction processed by the POS terminal 100 by credit card settlement, electronic money settlement, or code settlement, etc. Either or both of the receipt server 300 and the settlement server 400 may be realized by using a single computer device, or may be realized by a plurality of computers collaborating.

[0011] Incidentally, the POS terminal 100, the receipt server 300, and the settlement server 400 are typically operated by different operators respectively. For example, the POS terminal 100 is operated by a retailer, the receipt server 300 is operated by an electronic receipt service provider, and the settlement server 400 is operated by a settlement service provider. However, any two or all of the POS terminal 100, the receipt server 300, and the settlement server 400 may be operated by the same operator.

[0012] FIG. 2 is a block diagram showing the main circuit configuration of the POS terminal 100. The POS terminal 100 includes a processor 101, a main storage unit 当翻訳为“主存储单元” 102, an auxiliary storage unit 当翻訳为“辅助存储单元” 103, a touch panel 104, a barcode scanner 105, a credit card reader 106, a proximity communication unit 107, a card reader / writer 108, a change unit 109, a receipt printer 110, a communication unit 111, and a transmission path 112. And the processor 101, the main storage unit 102, the auxiliary storage unit 103, the touch panel 104, the barcode scanner 105, the credit card reader 106, the proximity communication unit 107, the card reader / writer 108, the change unit 109, the receipt printer 110, and the communication unit 111 are connected to the transmission path 112.

[0013] The processor 101, the main storage unit 102, and the auxiliary storage unit 103 are connected by the transmission path 112 to form a computer for executing information processing related to the control of the POS terminal 100. By connecting the processor 101, the main memory unit 102, and the auxiliary storage unit 103 via the transmission path 112, a computer for performing information processing for controlling the POS terminal 100 is configured. The processor 101 corresponds to the central part of the computer. The processor 101 executes information processing for controlling each part in order to realize various functions as the POS terminal 100 according to information processing programs such as an operating system and application programs.

[0014] The main memory unit 102 corresponds to the main memory part of the computer. The main memory unit 102 includes a read-only memory area and a rewritable memory area. The main memory unit 102 stores a part of the above information processing program in the read-only memory area. Also, the main memory unit 102 may store data necessary for the processor 101 to execute processing for controlling each part in the read-only memory area or the rewritable memory area. The main memory unit 102 uses the rewritable memory area as a work area by the processor 101.

[0015] The auxiliary storage unit 103 corresponds to the auxiliary storage part of the computer. The auxiliary storage unit 103 can use, for example, an EEPROM (electric erasable programmable read-only memory), an HDD (hard disc drive), an SSD (solid state drive), or other various well-known storage devices. The auxiliary storage unit 103 stores data used when the processor 101 performs various processes and data generated by the processes in the processor 101. The auxiliary storage unit 103 may store the above information processing program. In this embodiment, the auxiliary storage unit 103 stores a transaction processing program PRA, which is one of the information processing programs. The transaction processing program PRA is an application program that describes the procedure of the transaction processing described later.

[0016] The touch panel 104 displays a screen for presenting information to the operator. The touch panel 104 also accepts input from the operator through touch operations on the screen. The barcode scanner 105 optically reads the barcode placed opposite the reading slot. The barcode scanner 105 outputs the barcode information represented by the read barcode. The credit card reader 106 reads card information from the credit card.

[0017] The proximity communication unit 107 performs proximity wireless communication with a nearby wireless tag and acquires data stored in the wireless tag. The proximity communication unit 107 also writes arbitrary information to the wireless tag through the proximity wireless communication described above. The card reader / writer 108 reads card data recorded on predetermined cards such as membership cards and prepaid cards. The card reader / writer 108 can also write arbitrary data to membership cards.

[0018] The same device may be used for at least two of the barcode scanner 105, credit card reader 106, proximity communication unit 107, and card reader / writer 108. For example, a single card reader that combines the functions of both the credit card reader 106 and the card reader / writer 108 may be used. The barcode scanner 105, credit card reader 106, proximity communication unit 107, and card reader / writer 108 may be separate from the POS terminal 100 and attached externally to the POS terminal 100. For example, a so-called payment terminal may be attached externally to the POS terminal 100, and this payment terminal may have at least one of the functions of the barcode scanner 105, credit card reader 106, proximity communication unit 107, and card reader / writer 108.

[0019] The change unit 109 counts the coins inserted through the coin slot and stores them in an internal storage compartment. The change unit 109 then discharges the coins stored in the storage compartment into a coin tray via a coin discharge port. The change unit 109 counts the banknotes inserted through the banknote slot and stores them in an internal storage compartment. The change unit 109 then discharges the banknotes stored in the storage compartment through a banknote discharge port. The banknote discharge port holds the discharged banknotes with a portion of them exposed to the outside. The receipt printer 110 prints an arbitrary image onto receipt paper under the control of the processor 101. As the receipt printer 110, a well-known printing device such as a thermal printer can be used.

[0020] The communication unit 111 performs communication processing for the processor 101 to exchange various data with any device, such as a receipt server 300 and a payment server 400, via the communication network 2. As the communication unit 111, a well-known device conforming to the communication method of the communication network 2 can be used. The transmission path 112 includes an address bus, a data bus, and control signal lines, etc. The transmission path 112 transmits data and signals exchanged between the connected parts.

[0021] As the basic hardware of the POS terminal 100, for example, the hardware of an existing POS terminal can be used. In this case, the transfer of the POS terminal 100 is generally carried out with the transaction processing program PRA stored in the auxiliary storage unit 103. However, the hardware of the POS terminal 100 and the transaction processing program PRA may be transferred separately, without the transaction processing program PRA stored in the auxiliary storage unit 103. The transaction processing program PRA may then be written to the auxiliary storage unit 103 in response to an operation by any worker. Alternatively, the hardware of the POS terminal 100 and the transaction processing program PRA may be transferred separately, with a different version of the transaction processing program of the same type as the transaction processing program PRA stored in the auxiliary storage unit 103. The transaction processing program PRA may then be written to replace the transaction processing program already stored in the auxiliary storage unit 103. The transfer of the transaction processing program PRA can be carried out by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network. The transaction processing program PRA may be stored in the main storage unit 102.

[0022] Figure 3 is a block diagram showing the main circuit configuration of the user terminal 200. The user terminal 200 includes a processor 201, a main memory unit 202, an auxiliary memory unit 203, a touch panel 204, a mobile communication unit 205, and a transmission line 206, among other things. The general functions of the processor 201, main memory unit 202, auxiliary memory unit 203, touch panel 204, and transmission line 206 are equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, touch panel 104, and transmission line 112, so their explanation will be omitted. However, the auxiliary memory unit 203 stores the user terminal program PRB instead of the transaction processing program PRA. The user terminal program PRB is an application program that describes the information processing procedure of the processor 201 to operate the user terminal 200 as a user interface for using the electronic receipt service provided by the receipt server 300. The auxiliary memory unit 203 also stores the configuration data DAA. The configuration data DAA will be described later.

[0023] The mobile communication unit 205 is an interface for data communication via the communication network 2. For example, a well-known communication device for performing data communication via a mobile communication network can be used as the mobile communication unit 205. The basic hardware of the user terminal 200 is expected to be, for example, the hardware of a smartphone or tablet computer.

[0024] The configuration data DAA is data used to manage user settings related to receipt issuance when using code payment, as described later. Figure 4 schematically represents the data structure of the configuration data DAA. The configuration data DAA includes five fields: FEA, FEB, FEC, FED, and FEE. Field FEA contains a flag (hereinafter referred to as the restaurant flag) indicating whether or not to issue a receipt when the store category where the transaction took place is "restaurant". Field FEB contains a flag (hereinafter referred to as the supermarket flag) indicating whether or not to issue a receipt when the store category where the transaction took place is "supermarket". Field FEC contains a flag (hereinafter referred to as the convenience store flag) indicating whether or not to issue a receipt when the store category where the transaction took place is "convenience store". Field FED contains a flag (hereinafter referred to as the clothing store flag) indicating whether or not to issue a receipt when the store category where the transaction took place is "clothing store". Field FEE contains a threshold score used to determine whether or not to issue a receipt based on the number of items in the transaction.

[0025] Next, the operation of the transaction processing system 1 configured as described above will be explained. Note that the content of the various processes described below is merely an example, and it is possible to change the order of some processes, omit some processes, or add other processes as appropriate. For example, in the following explanation, some processes have been omitted in order to clearly illustrate the characteristic operation of this embodiment. For example, if an error occurs, processing to deal with that error may be performed, but such processing has been omitted from the description.

[0026] When a customer intends to purchase goods at a store equipped with a POS terminal 100, they pick up the items they wish to purchase from the sales floor, take them to the checkout counter, and hand them over to a store employee who is in charge of operating the POS terminal 100. The employee then initiates a predetermined operation on the POS terminal 100 to register the goods handed over by the customer as the items to be traded. Alternatively, the customer may initiate a predetermined operation on the POS terminal 100 to register the items they wish to purchase as the items to be traded. In response, the processor 101 on the POS terminal 100 begins transaction processing based on the transaction processing program PRA.

[0027] Figure 5 is a flowchart of the transaction processing. As ACT11, processor 101 executes a registration process. The registration process is the process of registering products as transaction items in response to the operations performed by the store clerk or customer described above. The registration process may be similar to the process performed in other existing POS terminal devices.

[0028] Once the store clerk or customer has finished registering all the items to be traded, they instruct the system to begin the transaction using a predetermined procedure. In response, the processor 101 completes the registration process and proceeds to ACT 12. As ACT12, the processor 101 displays a designated screen on the touch panel 104. The designated screen allows the store clerk or customer to select a payment method to be used for settling the payment for the transaction being processed. The designated screen may, for example, represent soft keys for specifying each of the payment methods that are permitted. Examples of permitted payment methods include cash payment, credit card payment, prepaid card payment, electronic money payment, and code payment. Furthermore, the selective use of multiple payment services may be permitted for the same payment method. As ACT13, processor 101 waits for the payment method to be specified.

[0029] The store clerk listens to the customer's request, or the customer specifies the payment method by performing a predetermined operation, such as tapping a soft key associated with the payment method they wish to use. In response, processor 101 determines YES in ACT13 and proceeds to ACT14. As ACT14, processor 101 checks whether the specified payment method is code payment. If a payment method other than code payment is specified, processor 101 checks the specified payment method and proceeds to other processing to perform payment using that payment method. Other processing may include, for example, confirming that credit payment is specified and then using credit card reader 106 to perform credit payment. Other processing may include confirming that electronic money payment is specified and then using proximity communication unit 107 to perform electronic money payment. Other processing may include confirming that prepaid card payment is specified and then using card reader / writer 108 to perform prepaid card payment. Other processing may include confirming that cash payment is specified and then using change unit 109 to perform cash payment. These other processing may be similar to the processing performed in other existing POS terminal devices, so their illustration and explanation are omitted.

[0030] When a customer wishes to make a payment using code payment, they first activate the user terminal program PRB on the user terminal 200 and then instruct the system to activate the code payment function through a predetermined operation. In response to this instruction, the processor 201 on the user terminal 200 starts the code payment processing as part of the processing by the user terminal program PRB.

[0031] Figures 6 and 7 are flowcharts of the code payment process. In Figure 6, processor 201, designated as ACT31, initially sets the settings related to receipt issuance (hereinafter referred to as issuance settings) to "automatic". As ACT32, processor 201 displays the top screen on touch panel 204. The top screen is a GUI (graphical user interface) screen for operations related to initiating code payment.

[0032] Figure 8 shows an example of the SCA (Service Layout Adaptation) on the top screen. Note that the screen examples shown in Figure 8 and other figures may omit the illustration of some display objects. The top screen SCA represents buttons BUA and BUB, and switches SWA, as GUI objects.

[0033] Button BUA is a soft key used to receive instructions to execute a code payment. Button BUB is a soft key used to receive instructions to cancel a code payment. Switch SWA is a virtual switch that receives instructions related to changing the broadcasting setting via a swipe operation similar to sliding the slider SLA. The initial position of the slider SLA on Switch SWA is represented by a solid line. Therefore, Switch SWA also functions as an indicator showing that the broadcasting setting is "automatic".

[0034] In Figure 6, as ACT33, processor 201 checks whether or not an instruction has been given to execute a code payment. If processor 201 cannot confirm the relevant event, it determines NO and proceeds to ACT34. As ACT34, processor 201 checks whether a change in the issuing settings has been instructed. If processor 201 cannot confirm the relevant event, it determines NO and proceeds to ACT35. As ACT35, processor 201 checks whether it has been instructed to start setting the conditions for automatically determining whether or not to issue a receipt (hereinafter referred to as the issuance conditions). If processor 201 cannot confirm the relevant event, it determines NO and returns to ACT33. Thus, processor 201 awaits instructions to execute, modify, or start a setting as ACT33 to ACT35.

[0035] If the customer wishes to change the issuance conditions, they initiate the setting process through a predetermined operation. This operation is, for example, a swipe operation on the top screen SCA, sliding the slider SLA downwards as shown in Figure 8. Once the setting process is initiated in this way, the processor 201 determines YES at ACT35 in Figure 6 and proceeds to ACT36. As ACT36, processor 201 displays a settings screen on touch panel 204. The settings screen is a GUI screen for receiving instructions to change the issuance conditions.

[0036] Figure 9 shows an example of the settings screen SCB. The settings screen SCB represents the buttons BUC, BUD, BUE, BUF, BUG, ​​BUH, and BUI as GUI objects. The settings screen SCB also includes the display area ARA. Buttons BUC~BUF are associated with the categories "Restaurants," "Supermarkets," "Convenience Stores," and "Clothing Stores," respectively. Buttons BUC~BUF indicate whether or not to issue a receipt for transactions at stores belonging to the associated category, and are also toggle buttons for changing this setting. The setting screen SCB shown in Figure 9 is an example where the setting is to not issue a receipt for transactions at stores belonging to "Restaurants," but to issue a receipt for transactions at stores belonging to the categories of "Supermarkets," "Convenience Stores," and "Clothing Stores." For the setting screen SCB displayed by ACT36, processor 201 determines the display state of buttons BUC~BUF according to the flags set in fields FEA~FED of the setting data DAA.

[0037] Button BUG is a soft key that receives an instruction to increase the reference score displayed in the display area ARA. Button BUH is a soft key that receives an instruction to decrease the reference score displayed in the display area ARA. For the setting screen SCB displayed by ACT36, processor 201 displays the number representing the reference score set in the field FEE of the setting data DAA in the display area ARA. The button BUI is a soft key used to signal the termination of the changes to the publishing conditions.

[0038] After displaying the settings screen SCB as ACT36 in Figure 6, processor 201 proceeds to ACT37. As ACT37, processor 201 checks whether a change instruction has been issued. If processor 201 cannot confirm the relevant event, it determines NO and proceeds to ACT38. As ACT38, processor 201 checks whether a termination command has been issued. If processor 201 cannot confirm the event, it determines NO and returns to ACT37. Thus, processor 201 awaits a change instruction or a termination instruction as ACT37 and ACT38.

[0039] If a customer wants to change the issuance conditions, they perform a predetermined operation to do so. For example, if the settings screen SCB is in the state shown in Figure 9 and the customer wants to stop issuing receipts for transactions at stores where the category is "clothing store", they tap button BUF. Alternatively, if the settings screen SCB is in the state shown in Figure 9 and the customer wants to set the threshold score to "12", they tap button BUG twice. If the processor 201 has performed an operation to instruct such a change, it will determine YES in ACT37 and proceed to ACT39.

[0040] As ACT39, processor 201 updates the configuration data DAA in response to the change instruction. For example, if button BUF is tapped, processor 201 inverts the state of the flag set in field FED of configuration data DAA. For example, each time button BUG is tapped, processor 201 increments the value set in field FEE of configuration data DAA by one.

[0041] As ACT40, processor 201 updates the settings screen SCB to reflect the contents of the updated settings data DAA. For example, if processor 201 inverts the state of the flag set in field FED of the settings data DAA, it changes the display state of button BUF. For example, if processor 201 changes the value set in field FEE of the settings data DAA, it replaces the number displayed in display area ARA with the number representing the changed value. The processor 201 then returns to the waiting state for ACT37 and ACT38. Thus, the processor 201 repeatedly executes ACT39 and ACT40 each time a change instruction is given.

[0042] Once the customer has finished changing the issuance conditions, they signal termination by performing a predetermined operation, such as tapping the BUI button. In response, processor 201 determines YES in ACT38, returns to ACT32, and repeats the process as described above. If a customer wishes to change the issuance settings, they will do so by following predetermined instructions. For example, if a customer wants to issue a receipt for an upcoming payment regardless of the issuance conditions, they will swipe the slider SLA on the top screen SCA to the position POA, indicated by the dashed line. Alternatively, if a customer wishes not to issue a receipt for an upcoming payment regardless of the issuance conditions, they will swipe the slider SLA on the top screen SCA to the position POB, indicated by the dashed line. Or, if a customer has either the setting to issue receipts or not and wants to change the issuance setting to "automatic," they will swipe the slider SLA to the display position shown in Figure 8.

[0043] If such instructions for changing the issuance settings are given, the processor 201 determines YES at ACT34 in Figure 6 and proceeds to ACT41. As ACT41, processor 201 changes the publishing setting in response to a change instruction. For example, if a swipe operation is performed to move the slider SLA to position POA, processor 201 changes the publishing setting to "Publish". For example, if a swipe operation is performed to move the slider SLA to position POB, processor 201 changes the publishing setting to "Do not publish". If a swipe operation is performed to move the slider SLA to the display position shown in Figure 8, processor 201 changes the publishing setting to "Automatic". Processor 201 stores data indicating whether the publishing setting is "Automatic", "Publish", or "Do not publish" in the main storage unit 202 or auxiliary storage unit 203.

[0044] As ACT42, processor 201 updates the top screen SCA according to the changed publishing settings. For example, if processor 201 changes the publishing setting to "Publish," it updates the top screen SCA so that the slider SLA is displayed at position POA. For example, if processor 201 changes the publishing setting to "Do not publish," it updates the top screen SCA so that the slider SLA is displayed at position POB. For example, if processor 201 changes the publishing setting to "Automatic," it returns to the top screen SCA shown in Figure 8. Processor 201 then returns to the waiting state for ACT33 to ACT35.

[0045] If the customer decides to proceed with payment, they will initiate the process through a predetermined operation, such as tapping the BUA button on the top screen SCA. In response, the processor 201 determines YES at ACT33 in Figure 6 and proceeds to ACT51 in Figure 7. As ACT51, the processor 201 obtains a one-time code to be used as an authentication code for authentication for code payment. The processor 201 requests the one-time code from the receipt server 300, for example. The processor 201 sends predetermined request data for the one-time code request from the mobile communication unit 205 to the communication network 2 addressed to the receipt server 300. When this request data is transmitted to the receipt server 300 via the communication network 2, the receipt server 300 requests the one-time code from the payment server 400. The payment server 400 generates a one-time code in response to the request. The one-time code may be, for example, a code similar to one already used in code payments. The payment server 400 sends the generated one-time code to the receipt server 300 as a response to the request. When the receipt server 300 receives the one-time code from the payment server 400, it sends this one-time code to the user terminal 200 via the communication network 2 as a response to the request from the user terminal 200. In this manner, the one-time code sent from the receipt server 300 is transmitted to the user terminal 200 via the communication network 2, and when it is received by the mobile communication unit 205 at the user terminal 200, the processor 201 stores it in the main storage unit 202 or the auxiliary storage unit 203. The acquisition of such a one-time code may be the same process as that already performed for code payment. Thus, by the processor 201 executing information processing based on the user terminal program PRB, the computer with the processor 201 as its central component functions as a first means of acquiring a one-time code as an authentication code.

[0046] As ACT52, processor 201 checks whether the publishing setting is set to "automatic". If it is set to "automatic", processor 201 determines it is YES and proceeds to ACT53. As ACT53, processor 201 generates a first barcode. For example, processor 201 generates a first barcode representing barcode data that includes the one-time code obtained in ACT51 along with the configuration data DAA as additional data. At this time, processor 201 obtains the settings made by the payer by reading the configuration data DAA stored in the auxiliary storage unit 203. Thus, by processor 201 executing information processing based on the user terminal program PRB, the computer with processor 201 as its central component functions as a second acquisition means.

[0047] If the issuance setting is not "automatic", processor 201 determines NO in ACT52 and proceeds to ACT54. As ACT54, processor 201 checks whether the publishing setting is "Publish". If it is "Publish", processor 201 determines it is YES and proceeds to ACT55.

[0048] As ACT55, processor 201 generates a second barcode. For example, processor 201 generates a second barcode that represents barcode data that includes predetermined instruction data for issuing a receipt as additional data, along with the one-time code obtained in ACT51. At this time, processor 201 has received an instruction to set the issuance setting to "issue," and thus obtains the setting from the payer. Thus, by having processor 201 execute information processing based on the user terminal program PRB, the computer with processor 201 as its central component functions as a second acquisition means.

[0049] If the issuance setting is "Do not issue", processor 201 determines NO in ACT54 and proceeds to ACT56. As ACT56, processor 201 generates a third barcode. For example, processor 201 generates a third barcode that includes, as additional data, predetermined instruction data to indicate that a receipt should not be issued, along with the one-time code obtained in ACT51. At this time, processor 201 has received an instruction to set the issuance setting to "not issue," and thus obtains the setting from the payer. Thus, by having processor 201 execute information processing based on the user terminal program PRB, the computer with processor 201 as its central component functions as a second acquisition means.

[0050] After completing any of ACT53, ACT55, or ACT56, processor 201 proceeds to ACT57 in all cases. As ACT57, processor 201 displays a barcode screen on touch panel 204. The barcode screen is a screen that displays one of the first, second, or third barcodes generated in ACT53, ACT55, and ACT56 as a payment barcode.

[0051] Figure 10 shows an example of a barcode screen SCC. The barcode screen SCC represents the payment barcode BCA and button BUJ. The barcode screen SCC also includes the display area ARB. The payment barcode BCA is one of the first, second, or third barcodes generated in ACT53, ACT55, and ACT56. Button BUJ is a soft key for receiving instructions to close the barcode screen. Processor 201 displays the validity period of the one-time code obtained in ACT51 in the display area ARA. While the barcode screen SCC is being displayed, processor 201 continuously updates the validity period displayed in the display area ARA by decreasing it. The payment barcode (BCA) is not limited to a one-dimensional barcode as shown in Figure 10; it can also be a two-dimensional barcode or other type of barcode, i.e., a two-dimensional code. Thus, by having the processor 201 perform information processing based on the user terminal program PRB, the computer with the processor 201 as its central component functions as a display means.

[0052] The store clerk or customer specifies code payment at the POS terminal 100 by performing a predetermined operation, such as tapping a soft key associated with code payment. In this case, the processor 101 determines YES at ACT14 in Figure 5 and proceeds to ACT15. As ACT15, the processor 101 displays a guide screen on the touch panel 104. The guide screen is a screen that guides the store clerk or customer to have the payment barcode BCA read by the barcode scanner 105. The processor 101 displays a predetermined guide screen on the touch panel 104, for example, one that represents a text message.

[0053] As ACT16, processor 101 waits for the payment barcode BCA to be read. For example, when the barcode is read by the barcode scanner 105, processor 101 checks whether the barcode represents a one-time code, and if it does not represent a one-time code, it does not determine YES.

[0054] The store clerk or customer operates the barcode scanner 105 to read the payment barcode BCA displayed on the barcode screen SCC. If the processor 101 confirms that the payment barcode BCA has been scanned, for example, by determining that the barcode read by the barcode scanner 105 represents a one-time code, it determines YES in ACT 16 and proceeds to ACT 17.

[0055] As ACT17, processor 101 reads the settlement barcode BCA using barcode scanner 105 and extracts a one-time code and additional data from the barcode data. Thus, by having processor 101 perform information processing based on the transaction processing program PRA, the computer with processor 101 as its central component functions as a third acquisition means.

[0056] As ACT18, processor 101 requests payment from payment server 400. For example, processor 101 sends predetermined request data for payment to payment server 400 via communication unit 111 to communication network 2. The request data sent by processor 101 includes the payment amount for the transaction registered in ACT11 and the one-time code extracted in ACT17. When this request data is transmitted to payment server 400 via communication network 2, payment server 400 verifies the validity of the one-time code included in the request data, and if it is a valid one-time code, it processes the payment for the payment amount included in the request data. The payer for this payment is the customer using user terminal 200. Note that this payment processing may be the same as the processing already performed for code payments. Once payment is complete, payment server 400 sends notification data to POS terminal 100 via communication network 2 to notify completion. Thus, by having the processor 101 execute information processing based on the transaction processing program PRA, the computer with the processor 101 as its central component functions as a request mechanism.

[0057] After requesting payment as ACT18, processor 101 proceeds to ACT19. As ACT19, processor 101 waits for notification of payment completion. Then, as described above, if the notification data sent from payment server 400 is transmitted to POS terminal 100 via communication network 2 and received by communication unit 111, processor 101 determines YES in ACT19 and proceeds to ACT20.

[0058] As ACT20, processor 101 checks whether the additional data extracted in ACT17 is configuration data. If it is configuration data, processor 101 determines YES and proceeds to ACT21. In ACT21, the processor 101 checks whether the conditions for issuing a receipt, which are determined based on the configuration data, are met. For example, if the category to which the store using the POS terminal 100 belongs is "restaurant," the processor 101 determines that the conditions are met if the restaurant flag included in the configuration data extracted in ACT17 indicates that a receipt should be issued, and the number of items registered as transaction items in ACT11 is equal to or greater than the threshold number included in the configuration data extracted in ACT17. If the conditions are met in this way, the processor 101 determines YES in ACT21 and proceeds to ACT22.

[0059] As ACT22, processor 101 issues a receipt. For example, processor 101 generates a receipt image that represents the details of the transaction being processed in a predetermined format. Then processor 101 has the receipt printer 110 print the receipt image. Once processor 101 has finished printing the receipt, it terminates the transaction processing for the transaction being processed. Furthermore, if the conditions for issuing a receipt, which are determined based on the configuration data, are not met, the processor 101 will determine NO in ACT21, skip ACT22, and terminate the transaction processing. In other words, the processor 101 will not issue a receipt if the conditions are not met.

[0060] On the other hand, if the additional data extracted in ACT17 is not configuration data, processor 101 determines NO in ACT20 and proceeds to ACT23. In ACT23, processor 101 checks whether the additional data extracted in ACT17 is instruction data for issuing a receipt. If it is the correct instruction data, processor 101 determines YES and proceeds to ACT22. In other words, in this case, processor 101 issues a receipt unconditionally.

[0061] If the additional data extracted in ACT17 is instruction data to not issue a receipt, processor 101 determines NO in ACT23, skips ACT22, and terminates the transaction processing. In other words, processor 101 does not issue a receipt unconditionally. In this way, the processor 101 performs processing according to the settings represented by the additional data represented by the payment barcode BCA. In other words, by having the processor 101 execute information processing based on the transaction processing program PRA, the computer with the processor 101 as its central component functions as a processing means.

[0062] Furthermore, on the user terminal 200, the processor 201 displays the barcode screen SCC as ACT57 in Figure 7, and then proceeds to ACT58. As ACT58, processor 201 waits for a termination instruction. The store clerk or customer can signal termination at any time after having the payment barcode BCA read by the barcode scanner 105, for example by tapping button BUJ or performing a predetermined operation. In response, processor 201 determines YES as ACT58 and terminates the code payment process.

[0063] As described above, in the transaction processing system 1, when a payment is made using code payment, the receipt issuance setting on the user terminal 200 is imported into the POS terminal 100 along with the one-time code, and receipt issuance at the POS terminal 100 is controlled according to this setting. Thus, the POS terminal 100 can control the issuance of receipts according to the needs of the payer set on the user terminal 200. Furthermore, the paymenter's settings regarding receipt issuance control are obtained by reading the payment barcode BCA, which is used to input the one-time code into the POS terminal 100. Therefore, no special operation is required to input these settings into the POS terminal 100. In other words, it is not necessary for, for example, a customer to verbally tell a store clerk their preference, and for the clerk to input that preference; it is very easy.

[0064] Furthermore, the transaction processing system 1 checks whether the receipt issuance conditions, which are determined based on the setting data obtained from the user terminal 200, are met at the POS terminal 100, and then decides whether to issue or not issue a receipt. In this way, it is possible to flexibly control receipt issuance to meet the detailed needs of the payer, such as "receipts are only required for transactions at certain categories of stores" or "receipts are not required for transactions with a small number of items." Moreover, when receipt issuance control is performed based on setting data, the payer does not need to perform an operation to specify whether to issue or not issue a receipt for each transaction.

[0065] Furthermore, in the transaction processing system 1, if the user terminal 200 is set to issue or not issue a receipt for each transaction, the POS terminal 100 controls the issuance of receipts according to that setting. Thus, although the payer needs to perform an operation to specify whether to issue or not issue a receipt, they can flexibly decide whether to issue or not issue a receipt for each transaction.

[0066] Furthermore, in the transaction processing system 1, if the issuance / non-issuance of a receipt is not specified prior to settlement, the receipt issuance control based on the configuration data is applied. Thus, the settler can use the system flexibly, for example, by using the receipt issuance control based on the configuration data on a regular basis, while making exceptional decisions on issuance / non-issuance for some transactions.

[0067] This embodiment can be modified in various ways as follows: In this embodiment, the default setting for issuance is "automatic," but the default could also be "issued" or "not issued."

[0068] In this embodiment, the issuance setting can be set to "Issue" or "Do not issue," but this can be omitted, and the setting data can always be displayed on the payment barcode. Alternatively, the issuance setting can be set to "Automatic," but this can be omitted, and instruction data indicating "Issue" or instruction data indicating "Do not issue" can be displayed on the payment barcode. In this case, either "Issue" or "Do not issue" can be set as the default, and instructions to change it can be accepted for each transaction, or the specification of either "Issue" or "Do not issue" can be accepted for each transaction.

[0069] The conditions for determining whether or not to issue a receipt may be either the store category condition or the number of items condition in the embodiment. Alternatively, at least one of these conditions may be replaced with, or in addition to, another condition. An example of such another condition is that a receipt will not be issued if the payment amount is less than a predetermined amount.

[0070] The payment barcode may include data representing various individual settings of the payer, not just those related to receipt issuance / non-issuance. For example, settings such as whether a shopping bag is needed or not, whether a receipt is issued or not, or whether the customer is eating in or taking out may be represented in the payment barcode. In addition, settings related to various items that represent the individual requests of the payer may also be represented in the payment barcode. Furthermore, multiple types of settings may be represented on the same payment barcode.

[0071] The one-time code may also be obtained directly by the user terminal 200 from the payment server 400.

[0072] The authentication code is not limited to a one-time code; any code used for authentication related to code payments is acceptable.

[0073] The individual settings of the payer may be managed on the receipt server 300, the payment server 400, or a separate server, and these servers may generate payment barcodes or the data to be represented on the payment barcodes.

[0074] The processor 201 at the user terminal 200 makes a decision on whether to issue or not based on certain conditions, and may include issuance / non-issuance instruction data in the payment barcode according to this decision.

[0075] In the above embodiment, the processor 201 executes code payment processing based on the user terminal program PRB, which is an application program for using the electronic receipt service, and utilizes a code payment service provided incidentally as part of the electronic receipt service. However, it is also acceptable to use a code payment service provided independently of the electronic receipt service. In this case, the processor 201 is made to execute code payment processing based on an application program different from the application program for using the electronic receipt service.

[0076] Each of the functions realized by processors 101 and 201 through information processing can also be partially or entirely realized by hardware that performs non-program-based information processing, such as logic circuits. Furthermore, each of the above functions can also be realized by combining the above-mentioned hardware, such as logic circuits, with software control.

[0077] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be carried out in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. The invention described in the original claims of this application is listed below. [Note 1] A first means of obtaining an authentication code for code payment, A second means of obtaining settings made by the payer regarding actions other than payment that may be taken when making a code payment, A display means that causes a terminal device to display a barcode representing the authentication code obtained by the first acquisition means and the settings obtained by the second acquisition means, A third acquisition means for acquiring data represented by the barcode displayed on the terminal device by the display means, A request means that requests payment from the payment server along with notification of the authentication code represented by the data obtained by the third acquisition means, Processing means for performing actions according to the settings represented by the data acquired by the third acquisition means, A payment system equipped with [the following features]. [Note 2] The aforementioned request means requests settlement of the transaction price, The second acquisition means acquires the setting of whether or not to issue a receipt for the settlement transaction requested by the requesting means, The processing means performs processing to issue a receipt when the barcode acquired by the third acquisition means indicates a setting to issue a receipt, and does not perform processing to issue a receipt when it indicates a setting not to issue a receipt. The payment system described in Appendix 1. [Note 3] The second acquisition means acquires the setting of whether or not to issue a receipt for each type of transaction, The processing means performs processing to issue a receipt if the barcode acquired by the third acquisition means indicates a setting to issue a receipt for the type of transaction related to the payment requested by the requesting means, and does not perform processing to issue a receipt if the barcode indicates a setting not to issue a receipt for the type of transaction related to the payment requested by the requesting means. The payment system described in Appendix 2. [Note 4] The request means requests payment for a transaction involving one or more goods, The second acquisition means acquires the setting of a reference value, The processing means determines, based on the reference value represented by the barcode acquired by the third acquisition means, whether the transaction related to the payment requested by the request means is a large transaction with a large number of target products, or a small transaction with a smaller number of target products than a large transaction. If it is determined to be a large transaction, it performs processing to issue a receipt; if it is determined to be a small transaction, it does not perform processing to issue a receipt. The payment system described in Appendix 1. [Note 5] A first means of obtaining an authentication code for code payment, A second means of obtaining settings made by the payer regarding actions other than payment that may be taken when making a code payment, A display means for displaying a barcode representing the authentication code obtained by the first acquisition means and the settings obtained by the second acquisition means, A terminal device equipped with the following. [Note 6] The computer installed in the terminal device A first means of obtaining an authentication code for code payment, A second means of obtaining settings made by the payer regarding actions other than payment that may be taken when making a code payment, A display means for displaying a barcode representing the authentication code obtained by the first acquisition means and the settings obtained by the second acquisition means, An information processing program that enables a function to work. [Explanation of symbols]

[0078] 1...Transaction processing system, 2...Communication network, 100...POS terminal, 101...Processor, 102...Main memory unit, 103...Auxiliary memory unit, 104...Touch panel, 105...Barcode scanner, 106...Credit card reader, 107...Proximity communication unit, 108...Card reader / writer, 109...Change unit, 110...Receipt printer, 111...Communication unit, 112...Transmission path, 200...User terminal, 201...Processor, 202...Main memory unit, 203...Auxiliary memory unit, 204...Touch panel, 205...Mobile communication unit, 206...Transmission path, 300...Receipt server, 400...Payment server.

Claims

1. A first means of obtaining an authentication code for code payment, A second means of obtaining the payer's setting regarding whether or not to issue a receipt when making a code payment, A display means for displaying a barcode on a terminal device that represents the authentication code obtained by the first acquisition means and the settings obtained by the second acquisition means, A third acquisition means for acquiring data represented by the barcode displayed on the terminal device by the display means, A request means that requests the settlement server to settle the transaction price, accompanied by notification of the authentication code represented by the data obtained by the third acquisition means, A processing means that performs a process to issue a receipt if the data acquired by the third acquisition means indicates a setting to issue a receipt, and does not perform a process to issue a receipt if the data indicates a setting not to issue a receipt, A payment system equipped with [the following features].

2. The second acquisition means acquires the setting of whether or not to issue a receipt for each type of transaction, The processing means performs processing to issue a receipt if the data acquired by the third acquisition means indicates a setting to issue a receipt for the type of transaction related to settlement requested by the requesting means, and does not perform processing to issue a receipt if the data indicates a setting not to issue a receipt for the type of transaction related to settlement requested by the requesting means. The payment system according to claim 1.

3. A first means of obtaining an authentication code for code payment, A second means of obtaining the setting of standard values ​​by the payer regarding measures other than payment that may be taken when making a code payment, A display means for displaying a barcode on a terminal device that represents the authentication code obtained by the first acquisition means and the settings obtained by the second acquisition means, A third acquisition means for acquiring data represented by the barcode displayed on the terminal device by the display means, A request means that requests the settlement server to settle the payment for a transaction involving one or more products, accompanied by notification of an authentication code represented by the data obtained by the third acquisition means, Based on the reference value represented by the data acquired by the third acquisition means, the processing means determines whether the transaction relating to the settlement requested by the request means is a large transaction with a large number of target products, or a small transaction with a smaller number of target products than a large transaction, and performs processing to issue a receipt if it is determined to be a large transaction, and does not perform processing to issue a receipt if it is determined to be a small transaction. A payment system equipped with [the following features].

4. A first means of obtaining an authentication code for code payment, A second means of obtaining the payer's setting regarding whether or not to issue a receipt when making a code payment, A display means for displaying a barcode representing the authentication code obtained by the first acquisition means and the settings obtained by the second acquisition means, The payment system is configured together with a terminal device equipped with the following: A third acquisition means for acquiring data represented by the barcode displayed on the terminal device by the display means, A request means that requests the settlement server to settle the transaction price, accompanied by notification of the authentication code represented by the data obtained by the third acquisition means, A processing means that performs a process to issue a receipt if the data acquired by the third acquisition means indicates a setting to issue a receipt, and does not perform a process to issue a receipt if the data indicates a setting not to issue a receipt, A POS terminal equipped with the following features.

5. A first means of obtaining an authentication code for code payment, A second means of obtaining the payer's setting regarding whether or not to issue a receipt when making a code payment, A display means for displaying a barcode representing the authentication code obtained by the first acquisition means and the settings obtained by the second acquisition means, A computer installed in a POS terminal that constitutes a payment system together with a terminal device equipped with the following: A third acquisition means for acquiring data represented by the barcode displayed on the terminal device by the display means, A request means that requests the settlement server to settle the transaction price, accompanied by notification of the authentication code represented by the data obtained by the third acquisition means, A processing means that performs a process to issue a receipt if the data acquired by the third acquisition means indicates a setting to issue a receipt, and does not perform a process to issue a receipt if the data indicates a setting not to issue a receipt, An information processing program that enables a function to work.

Images