JP7742764B2 - Code payment system, method, and program - Google Patents

Description

The disclosed technology relates to a code payment system, a code payment method, and a code payment program.

One cashless payment method is code payment, which uses codes such as QR codes (registered trademark) and barcodes. A proposed code payment technology eliminates the need to carry multiple cards. When paying with a card, a card payment system suggests the optimal card for payment based on the location, date, and time of purchase, the purchase amount, and the customer's designated priorities. In this system, customers launch a dedicated app on their own customer device when making a purchase. When a store clerk enters the purchase amount into a POS terminal at the store's cash register, the POS terminal reads the card information registered on the customer device and transmits the card information and purchase information to a card payment management server. The server periodically obtains reward information for each card and extracts the reward information for the card transmitted from the POS terminal from the acquired reward information. The server then displays the reward information for each card on the customer's terminal screen. The recommended card order is then determined and displayed. When the customer selects the card to use for payment from this screen, a two-dimensional barcode appears on the screen. The payment is completed by holding this screen over the POS terminal.

Technology has also been proposed that applies code payments to payments for refueling at gas stations and other facilities. For example, a refueling system has been proposed that provides refueling while preventing the leakage of personal data and other information from customers using mobile devices. In this system, when information related to refueling settings is read from the mobile device by a reading means, refueling settings are made in the refueling device. The information related to refueling settings may include the type of fuel, payment card number, and amount of fuel filled, and the reading means can read an identification code displayed on the mobile device. This system then generates information related to payment based on the information related to the refueling obtained after refueling, displays the information related to payment as an identification code, and when the information related to payment is read by the mobile device, it is output to the payment card company.

Japanese Patent Application Laid-Open No. 2017-130092 Japanese Patent Application Laid-Open No. 2020-070089

With code payment systems, where payment is made from a pre-charged balance when the code is scanned, problems arise when the price of a product or service is determined after it has been provided. For example, at a self-service gas station, if code payment is made after filling up, the charge balance may not cover the price determined after filling up. There is also the possibility of fraudulent use, such as filling up and running with gas.

As mentioned above, when using deferred code payment in cases where the fee is determined after the provision of a product or service, it is conceivable that the code would be scanned once before the product or service is provided, and the balance would be checked before the product or service is provided. In this case, the code would need to be scanned again for payment after the product or service is provided, which would reduce convenience for users.

In one aspect, the disclosed technology aims to provide a code payment system, method, and program that can ensure user convenience while preventing fraudulent use, even when the fee is determined after the product or service is provided.

In one aspect, the disclosed technology includes an acquisition unit that acquires provisional payment information in which a first payment amount indicating the provisional price of a product or service is associated with code information obtained by reading a code image associated with a payment service provider. The disclosed technology also includes a first payment unit that executes payment processing for the first payment amount indicated by the provisional payment information, and a control unit that controls the product or service to a state in which it can be provided after the payment processing by the first payment unit is completed. The disclosed technology also includes a second payment unit that, when it detects that the provision of the product or service has been completed, determines a second payment amount indicating the official price of the product or service, and executes payment processing for the difference between the first payment amount and the second payment amount.

One aspect is that it has the effect of ensuring user convenience while preventing fraudulent use, even when the fee is determined after the product or service is provided.

1 is a block diagram showing a schematic configuration of a code payment system according to first and third embodiments. [0022] FIG. FIG. 2 is a functional block diagram of a user terminal according to the first embodiment. FIG. 2 is a functional block diagram of a store terminal according to the first embodiment. FIG. 2 is a functional block diagram of a relay device according to the first to third embodiments. FIG. 2 is a functional block diagram of a payment service provider device according to the first embodiment. FIG. 10 is a diagram illustrating an example of implementation of provisional payment and final payment. FIG. 1 is a block diagram showing a schematic configuration of a computer that functions as a user terminal. FIG. 2 is a block diagram showing a schematic configuration of a computer that functions as a store terminal. FIG. 2 is a block diagram showing a schematic configuration of a computer that functions as a relay device. FIG. 2 is a block diagram showing a schematic configuration of a computer that functions as a payment service provider device. FIG. 2 is a sequence diagram for explaining the operation of the code payment system according to the first embodiment. FIG. 10 is a diagram showing an example of a selection screen displayed on a display device of a store terminal. FIG. 10 is a diagram illustrating an example of a payment status DB. 10A and 10B are diagrams illustrating an example of a QR screen, a message screen, and a receipt screen displayed on a display device of a store terminal. FIG. 10 is a block diagram showing a schematic configuration of a code payment system according to a second embodiment. FIG. 10 is a functional block diagram of a user terminal according to the second embodiment. FIG. 10 is a functional block diagram of a store terminal according to a second embodiment. FIG. 10 is a functional block diagram of a payment service provider device according to the second and third embodiments. FIG. 10 is a sequence diagram for explaining the operation of the code payment system according to the second embodiment. FIG. 10 is a diagram showing an example of a QR code displayed on a display device of a user terminal. FIG. 11 is a functional block diagram of a user terminal according to the third embodiment. FIG. 11 is a functional block diagram of a store terminal according to a third embodiment. FIG. 11 is a sequence diagram for explaining the operation of the code payment system according to the third embodiment. 10A and 10B are diagrams showing an example of a card on which a QR code for each payment brand is printed, and a selection screen displayed on the display device of a user terminal. FIG. 10 is a diagram showing an example of a card on which QR codes for each payment brand and each amount for specifying the amount are printed.

An example of an embodiment of the disclosed technology will be described below with reference to the drawings. Each of the following embodiments describes a case where the code payment system of the disclosed technology is applied to the payment of fuel fees at a self-service gas station where users themselves refuel.

First Embodiment
In the first embodiment, an example of a dynamic MPM (Merchant-Presented Mode) method will be described in which a QR code (registered trademark) dynamically presented by a store is read by a user.

Figure 1 shows the schematic configuration of a code payment system 1 according to the first embodiment. As shown in Figure 1, the code payment system 1 according to the first embodiment includes a user terminal 10, a store terminal 20, a relay device 30, and a payment service provider device 40. The user terminal 10 and the payment service provider device 40, the store terminal 20 and the relay device 30, and the relay device 30 and the payment service provider device 40 are each connected to each other via a network so that they can communicate with each other. Note that the number of components included in the code payment system 1 is not limited to the example shown in Figure 1.

The user terminal 10 is an information processing terminal used by a user who receives a product or service (here, gasoline refueling). The user terminal 10 is, for example, a smartphone, tablet terminal, etc. An application for using the code payment system 1 runs on the user terminal 10.

The store terminal 20 is an information processing terminal for payment processing that is installed in a store (here, a gas station) where goods or services are provided. The store terminal 20 is, for example, a point-of-sale (POS) terminal, a personal computer, a smartphone, a tablet terminal, etc. An application for using the code payment system 1 runs on the store terminal 20. The store terminal 20 is also connected to a fuel pump 28.

The fuel dispenser 28 includes a pump that draws gasoline from the tank, a pump drive mechanism, a hose and nozzle for directing the drawn gasoline into the vehicle's fuel inlet, a sensor for acquiring information necessary for controlling the inflow of gasoline, a nozzle locking mechanism, a controller, and the like. The sensor, for example, detects the amount of fuel dispensed. The controller controls the pump drive mechanism based on the sensor's detection results so that the amount of gasoline specified by the store terminal 20 is dispensed. The nozzle locking mechanism is a mechanism that makes the nozzle usable in an unlocked state and makes the nozzle unusable in a locked state. For example, when the nozzle is moored in a predetermined position, the controller controls the locking mechanism to a locked state, preventing the nozzle from being removed from the predetermined position until a command indicating that fueling is possible is received from the store terminal 20. Furthermore, when the controller receives a command indicating that fueling is possible from the store terminal 20, it controls the locking mechanism to be released, allowing the nozzle to be removed from the predetermined position.

The relay device 30 is an information processing device under the jurisdiction of a gateway operator that relays between the store and the payment service provider. The relay device 30 centrally accepts and manages payments from multiple payment service providers that support code payments that can be handled by the store terminal 20, and relays processing corresponding to each corresponding payment service provider device 40. The relay device 30 is a server device, etc.

The payment service provider device 40 is an information processing device under the jurisdiction of each payment service provider. The payment service provider device 40 is a server device, etc.

The following describes the functional configuration of each of the user terminal 10, store terminal 20, relay device 30, and payment service provider device 40.

First, the functional configuration of the user terminal 10 will be described. As shown in FIG. 2, the user terminal 10 includes a reading unit 11 and a transmitting/receiving unit 12. The reading unit 11 and the transmitting/receiving unit 12 are examples of acquisition units of the disclosed technology.

The reading unit 11 reads the QR code displayed on the display device provided in the store terminal 20. As will be described in detail below, the QR code displayed here is a code image based on code information including a payment provider code, information on the provisional payment amount indicating the provisional price of the product or service, and a payment ID. The payment provider code is a code for identifying the payment provider corresponding to the payment brand used by the user. The payment ID is identification information for a series of payment processes. The provisional payment amount is an example of the first payment amount of the disclosed technology. The reading unit 11 passes the code information (payment provider code, provisional payment amount, and payment ID) acquired by reading the QR code and provisional payment information including a user ID, which is identification information for the user, to the transmitting/receiving unit 12. Note that the provisional payment information may also include information necessary for user authentication, such as a password linked to the user ID.

The transmitting/receiving unit 12 transmits the provisional payment information received from the reading unit 11 to the payment provider device 40 indicated by the payment provider code. Furthermore, after the payment provider device 40 has completed the payment process, the transmitting/receiving unit 12 receives the result of the payment process (hereinafter referred to as the "payment result"; details will be described later) transmitted from the payment provider device 40. The transmitting/receiving unit 12 displays the received payment result on a display device provided in the user terminal 10.

Next, the functional configuration of the store terminal 20 will be described. As shown in FIG. 3, the store terminal 20 includes a reception unit 21, a transmission/reception unit 22, a display control unit 23, a refueling control unit 24, and a determination unit 25. The reception unit 21, the transmission/reception unit 22, and the display control unit 23 are examples of acquisition units of the disclosed technology, and the refueling control unit 24 is an example of a control unit of the disclosed technology.

The reception unit 21 receives from the user the designation of a payment brand and the provisional payment amount or information for specifying the provisional payment amount. Information for specifying the provisional payment amount is, for example, the quantity of goods or services to be provided. For example, if the user wishes to refuel a specified amount of fuel, the user specifies the provisional payment amount. Also, if the user wishes to refuel a specified amount of fuel, the user specifies the quantity as information for specifying the provisional payment amount.

Specifically, the reception unit 21 displays a selection screen on the display device provided in the store terminal 20 for selecting a payment brand and a provisional payment amount or information for specifying the provisional payment amount. The reception unit 21 accepts information selected from the selection screen by the user's selection operation (hereinafter referred to as "selected information"). When the reception unit 21 accepts a quantity as information for specifying the provisional payment amount, it calculates the provisional payment amount based on the quantity and the unit price of the product or service. The reception unit 21 passes the accepted payment brand and provisional payment amount to the transmission/reception unit 22. Note that the selection screen does not necessarily have to be operated by the user, but may also be operated by store staff who hear the user's selection.

The transmitter/receiver unit 22 transmits a QR request to the relay device 30 to request a QR code from a payment provider device 40 under the jurisdiction of the payment provider corresponding to the accepted payment brand. The transmitter/receiver unit 22 includes in the QR request the payment provider code, a store code which is store identification information, and information on the provisional payment amount. The transmitter/receiver unit 22 also receives code information from the relay device 30. The code information is included in a QR response (details will be described later) sent from the payment provider device 40 to the relay device 30. The transmitter/receiver unit 22 passes the received code information to the display control unit 23.

In addition, when the transmitter/receiver unit 22 receives information on the actual payment amount (details will be described later) from the determination unit 25, it transmits the actual payment information, including the payment ID, payment provider code, store code, and actual payment amount, to the relay device 30.

When the display control unit 23 receives code information from the transceiver unit 22, it displays the code image represented by the code information, i.e., the QR code, on the display device. Once the display control unit 23 has displayed the QR code, it notifies the refueling control unit 24 that display is complete.

The refueling control unit 24 controls the refueling machine 28 to a state where it can provide goods or services after the provisional payment process (details will be described later) by the payment provider device 40 is completed. Here, the refueling control unit 24 controls the refueling machine 28 to be ready to refuel. Specifically, when the display control unit 23 notifies the refueling control unit 24 that display is complete, the refueling control unit 24 polls the relay device 30 and monitors whether the relay device 30 has received the result of the provisional payment process (hereinafter referred to as the "provisional payment result"; details will be described later) from the payment provider device 40. If the relay device 30 has received the provisional payment result and the provisional payment result indicates the completion of the provisional payment process, the refueling control unit 24 notifies the refueling machine 28 that refueling is possible and notifies the refueling machine 28 of the amount of refueling corresponding to the provisional payment amount or quantity specified by the user. Note that the refueling control unit 24 determines the amount of refueling to be notified to the refueling machine 28 so that the actual payment amount, which is the official price for that amount of refueling, is equal to or less than the provisional payment amount.

When the refueling control unit 24 has controlled the state so that refueling is possible, it notifies the decision unit 25 of this. Note that if the provisional payment result indicates an error due to, for example, insufficient balance, the refueling control unit 24 may display an error message on the display device without notifying the refueling machine 28 to start refueling.

When the determination unit 25 detects that the provision of the product or service has been completed, it determines the final payment amount, which indicates the official price for the product or service. The final payment amount is an example of the second payment amount of the disclosed technology. Specifically, the determination unit 25 detects the completion of refueling when a completion action indicating that refueling has been completed in the refueling machine 28 is performed. For example, the determination unit 25 detects the completion of refueling by acquiring detection data that indicates, using a sensor, that the user has returned the nozzle to a predetermined position. When the determination unit 25 detects the completion of refueling, it acquires the actual amount of fuel supplied from the refueling machine 28 and determines the final payment amount by multiplying the acquired amount of fuel supplied by the unit price of gasoline. The determination unit 25 passes the determined final payment amount to the transmission/reception unit 22.

The determination unit 25 also polls the relay device 30 and monitors whether the relay device 30 has received the final payment result from the payment service provider device 40. When the relay device 30 receives the final payment result, the determination unit 25 acquires the final payment result from the relay device 30 and stores the final payment information and the final payment result in a specified memory area in association with each other. The determination unit 25 also displays a receipt showing the details of the payment on a display device or outputs it using a printer.

Next, the functional configuration of the relay device 30 will be described. As shown in FIG. 4, the relay device 30 includes a transmitter/receiver 31 and a manager 32. A payment status database 38 is also stored in a predetermined storage area of the relay device 30.

The transmitter/receiver unit 31 receives a QR request sent from the store terminal 20 and transmits the QR request to the payment service provider device 40 indicated by the payment service provider code included in the QR request. The transmitter/receiver unit 31 also receives a QR response returned from the payment service provider device 40 in response to the QR request. The QR response includes the store code and code information. The transmitter/receiver unit 31 passes the received QR response to the management unit 32 and transmits the code information included in the QR response to the store terminal 20 indicated by the store code.

The transmitter/receiver unit 31 also receives a provisional payment result from the payment provider device 40. The provisional payment result includes a payment ID and result-related information. If personal authentication using the user ID is successful and there is a balance equivalent to the provisional payment amount, the result-related information includes information indicating that the provisional payment process has been completed (e.g., "OK"). If personal authentication fails, there is insufficient balance, or an error occurs in processing or communication in the payment provider device 40, the result-related information also includes an error code indicating the type of error that occurred. The transmitter/receiver unit 31 passes the received provisional payment result to the management unit 32.

The transmitter/receiver unit 31 also receives the payment information from the store terminal 20. The transmitter/receiver unit 31 transmits the payment information to the payment service provider device 40 indicated by the payment service provider code included in the payment information. The transmitter/receiver unit 31 also passes the received payment information to the management unit 32.

The transmitter/receiver unit 31 also receives the actual payment result from the payment provider device 40. The actual payment result includes a payment ID and result-related information. The result-related information includes the payment amount. The payment amount only needs to indicate the final transaction amount, and may be the actual payment amount, or the provisional payment amount and the difference. As with the provisional payment result, the result-related information also includes an error code if an error occurs. The transmitter/receiver unit 31 passes the received actual payment result to the management unit 32.

When the management unit 32 receives a QR response from the transceiver unit 31, it assigns the date and time of reception to the store code included in the QR response, the payment provider code and provisional payment amount represented by the code information, and stores them in the payment status DB 38 using the payment ID as a key. The management unit 32 also stores, in association with the payment ID, information indicating the status of the payment process indicated by that payment ID, indicating that a QR code has been issued and that the provisional payment result is awaited.

When the management unit 32 receives a provisional payment result from the transmission/reception unit 31, it assigns the date and time of receipt to the payment ID included in the provisional payment result and stores it in the payment status DB 38. If the result included in the provisional payment result is "OK," the management unit 32 stores information indicating that the provisional payment has been completed and that the fuel supply is waiting to be completed, in association with the corresponding payment ID, as information indicating the status of the payment process. If the provisional payment result includes an error code, the management unit 32 stores the error code in association with the corresponding payment ID as information indicating the status of the payment process.

When the management unit 32 receives the payment information from the transmission/reception unit 31, it assigns the date and time of reception to the payment provider code, store code, and payment amount included in the payment information, and stores them in the payment status DB 38 using the payment ID as a key. The management unit 32 also stores information indicating that refueling is complete and the payment result is awaited, in association with the payment ID, as information indicating the status of the payment process indicated by the payment ID.

When the management unit 32 receives the payment result from the transmission/reception unit 31, it assigns the date and time of receipt to the payment amount included in the payment result and stores it in the payment status DB 38 using the payment ID as a key. The management unit 32 also stores information indicating that the payment has been completed in association with the corresponding payment ID as information indicating the status of the payment process. If the payment result includes an error code, the management unit 32 stores the error code in association with the corresponding payment ID as information indicating the status of the payment process.

Next, the functional configuration of the payment service provider device 40 will be described. As shown in FIG. 5, the payment service provider device 40 includes a transmitter/receiver unit 41, an issuing unit 42, a first payment unit 43, and a second payment unit 44.

The transmitter/receiver 41 receives a QR request from the relay device 30. The transmitter/receiver 41 passes the received QR request to the issuing unit 42. In addition, when the transmitter/receiver 41 receives information about the QR code issued by the issuing unit 42 (details will be described later), it transmits this information to the relay device 30 as a QR return.

The transmitter/receiver 41 also receives provisional payment information from the user terminal 10. The transmitter/receiver 41 passes the received provisional payment information to the first payment unit 43 and the second payment unit 44. When the transmitter/receiver 41 receives a provisional payment result from the first payment unit 43, it transmits it to the relay device 30.

The transmitter/receiver 41 also receives the final payment information from the relay device 30. The transmitter/receiver 41 passes the received final payment information to the second payment unit 44. When the transmitter/receiver 41 receives the final payment result from the second payment unit 43, it transmits it to the relay device 30 and the user terminal 10.

When the issuing unit 42 receives a QR request from the transmitting/receiving unit 41, it assigns a payment ID to the payment process and issues a QR code representing the payment business operator code, provisional payment amount, and payment ID included in the QR request. The issuing unit 42 passes the code information representing the issued QR code and the store code included in the QR request to the transmitting/receiving unit 41 as information related to the QR code.

The first payment unit 43 executes payment processing for the provisional payment amount indicated in the provisional payment information. Specifically, the first payment unit 43 executes identity authentication based on the user ID included in the provisional payment information passed from the transmission/reception unit 41. Furthermore, if identity authentication is successful, and if the user's balance indicated by the user ID is equal to or greater than the provisional payment amount, the first payment unit 43 executes provisional payment processing to deduct the provisional payment amount from the balance. If identity authentication fails or the balance is insufficient, the first payment unit 43 generates an error code. The first payment unit 43 associates the identity authentication result and result-related information including information indicating that the provisional payment processing has been completed or an error code with the payment ID included in the provisional payment information and passes them to the transmission/reception unit 41 as the provisional payment result.

The second payment unit 44 executes payment processing for the difference between the provisional payment amount and the actual payment amount. Specifically, the second payment unit 44 executes actual payment processing for the difference between the provisional payment amount included in the provisional payment information passed from the transmission/reception unit 41 and the actual payment amount included in the actual payment information passed from the transmission/reception unit 41, so that the final payment amount becomes the actual payment amount. The second payment unit 44 associates the payment ID included in the actual payment information with the payment amount and result-related information including the result of the actual payment processing or an error code, and passes this to the transmission/reception unit 41 as the actual payment result.

Here, several patterns of actual payment processing regarding the difference are possible, as shown in the implementation example shown in Figure 6. In Example 1 of Figure 6, a payment is initially made using the provisional payment amount, and once the actual payment amount is confirmed, the provisional payment is canceled and the actual payment is made. Note that "payment" refers to the process of deducting the appropriate amount from the user's balance and paying the appropriate amount to the store indicated by the store code. In Example 2, a payment is initially made using the provisional payment amount, and once the actual payment amount is confirmed, the difference between the provisional payment amount and the actual payment amount is refunded. Note that in this embodiment, the provisional payment amount is set to be greater than or equal to the actual payment amount, so if there is a difference between the provisional payment amount and the actual payment amount, the actual payment processing in Example 2 will always result in a refund. In Example 3, the provisional payment amount is recorded as provisional sales, and once the actual payment amount is confirmed, the provisional sales amount is corrected to the actual payment amount and the actual sale is made.

In either case, in this embodiment, as in the basic model shown in Figure 6, the user only needs to scan the QR code once when making a provisional payment, and the actual payment is made automatically, so user convenience is not compromised. Note that the pattern adopted as an example of payment processing varies depending on the payment provider, but this difference can be absorbed by the gateway provider. For example, the relay device 30 can process the actual payment information and send it to the payment provider device 40 so that the actual payment processing can be performed according to the payment provider.

Next, we will explain the hardware configuration of each of the user terminal 10, store terminal 20, relay device 30, and payment service provider device 40.

The user terminal 10 may be realized, for example, by a computer 50 shown in FIG. 7. The computer 50 includes a CPU (Central Processing Unit) 51, memory 52 as a temporary storage area, and a non-volatile storage unit 53. The computer 50 also includes an input/output device 54 including an input device and display device realized by a touch panel display or the like, a camera, etc., and an R/W (Read/Write) unit 55 that controls the reading and writing of data from and to a storage medium 59. The computer 50 also includes a communication I/F (Interface) 56 that is connected to a network such as the Internet. The CPU 51, memory 52, storage unit 53, I/O device 54, R/W unit 55, and communication I/F 56 are connected to one another via a bus 57.

The storage unit 53 may be realized by a hard disk drive (HDD), a solid state drive (SSD), flash memory, etc. The storage unit 53, which serves as a storage medium, stores a user terminal program 60 for causing the computer 50 to function as the user terminal 10. The user terminal program 60 includes a reading process 61 and a sending/receiving process 62.

The CPU 51 reads the user terminal program 60 from the storage unit 53, expands it in the memory 52, and sequentially executes the processes contained in the user terminal program 60. By executing the reading process 61, the CPU 51 operates as the reading unit 11 shown in FIG. 2. Furthermore, by executing the transmission/reception process 62, the CPU 51 operates as the transmission/reception unit 12 shown in FIG. 2. In this way, the computer 50 that has executed the user terminal program 60 functions as the user terminal 10. The CPU 51 that executes the program is hardware.

The store terminal 20 may be realized, for example, by a computer 70 shown in FIG. 8. The computer 70 includes a CPU 71, memory 72 as a temporary storage area, and a non-volatile storage unit 73. The computer 70 also includes an input/output device 74 including an input device and display device realized by a touch panel display or the like, a printer, etc., and an R/W unit 75 that controls the reading and writing of data from and to a device storage medium 79. The computer 70 also includes a communication I/F 76 that is connected to a network such as the Internet or a LAN (Local Area Network). The CPU 71, memory 72, storage unit 73, input/output device 74, R/W unit 75, and communication I/F 76 are connected to one another via a bus 77.

The storage unit 73, which serves as a storage medium, stores a store terminal program 80 that causes the computer 70 to function as the store terminal 20. The store terminal program 80 includes a reception process 81, a transmission/reception process 82, a display control process 83, a refueling control process 84, and a decision process 85.

The CPU 71 reads the store terminal program 80 from the storage unit 73, expands it in the memory 72, and sequentially executes the processes of the store terminal program 80. The CPU 71 operates as the reception unit 21 shown in FIG. 3 by executing the reception process 81. The CPU 71 also operates as the transmission/reception unit 22 shown in FIG. 3 by executing the transmission/reception process 82. The CPU 71 also operates as the display control unit 23 shown in FIG. 3 by executing the display control process 83. The CPU 71 also operates as the fuel supply control unit 24 shown in FIG. 3 by executing the refueling control process 84. The CPU 71 also operates as the determination unit 25 shown in FIG. 3 by executing the determination process 85. As a result, the computer 70 that executes the store terminal program 80 functions as the store terminal 20. The CPU 71 that executes the program is hardware.

The relay device 30 may be realized, for example, by a computer 90 shown in FIG. 9. The computer 90 includes a CPU 91, a memory 92 as a temporary storage area, and a non-volatile storage unit 93. The computer 90 also includes an input/output device 94, an R/W unit 95 that controls the reading and writing of data from and to a storage medium 99, and a communication I/F 96. The CPU 91, memory 92, storage unit 93, input/output device 94, R/W unit 95, and communication I/F 96 are connected to one another via a bus 97.

The storage unit 93, which serves as a storage medium, stores a relay device program 100 for causing the computer 90 to function as the relay device 30. The relay device program 100 includes a transmission/reception process 101 and a management process 102. The storage unit 93 also includes an information storage area 108 in which information constituting the payment status DB 38 is stored.

The CPU 91 reads the relay device program 100 from the storage unit 93, loads it into the memory 92, and sequentially executes the processes of the relay device program 100. The CPU 91 operates as the transmission/reception unit 31 shown in FIG. 4 by executing the transmission/reception process 101. The CPU 91 also operates as the management unit 32 shown in FIG. 4 by executing the management process 102. The CPU 91 also reads information from the information storage area 108 and loads the payment status DB 38 into the memory 92. As a result, the computer 90 that has executed the relay device program 100 functions as the relay device 30. The CPU 91 that executes the program is hardware.

The payment service provider device 40 may be realized, for example, by a computer 110 shown in FIG. 10. The computer 110 includes a CPU 111, a memory 112 as a temporary storage area, and a non-volatile storage unit 113. The computer 110 also includes an input/output device 114, an R/W unit 115 that controls the reading and writing of data from and to a storage medium 119, and a communication I/F 116. The CPU 111, memory 112, storage unit 113, input/output device 114, R/W unit 115, and communication I/F 116 are connected to one another via a bus 117.

The storage unit 113, which serves as a storage medium, stores a payment service provider device program 120 that causes the computer 110 to function as the payment service provider device 40. The payment service provider device program 120 includes a transmission/reception process 121, an issuance process 122, a first payment process 123, and a second payment process 124.

The CPU 111 reads the payment service provider device program 120 from the storage unit 113, expands it in the memory 112, and sequentially executes the processes of the payment service provider device program 120. The CPU 111 operates as the transmission/reception unit 41 shown in FIG. 5 by executing the transmission/reception process 121. The CPU 111 also operates as the issuance unit 42 shown in FIG. 5 by executing the issuance process 122. The CPU 111 also operates as the first payment unit 43 shown in FIG. 5 by executing the first payment process 123. The CPU 111 also operates as the second payment unit 44 shown in FIG. 5 by executing the second payment process 124. As a result, the computer 110 that has executed the payment service provider device program 120 functions as the payment service provider device 40. The CPU 111 that executes the program is hardware.

The functions realized by each program can also be realized, for example, by a semiconductor integrated circuit, or more specifically, an ASIC (Application Specific Integrated Circuit).

Next, the operation of the code payment system 1 according to the first embodiment will be described with reference to the sequence diagram shown in Figure 11. The series of processes shown in the sequence diagram in Figure 11 is an example of the code payment method of the disclosed technology.

Figure 12 shows an example of the selection screen 131 displayed on the display device of the store terminal 20. The initial selection screen 131A is a screen for selecting a payment method, such as cash, credit card, electronic money, or QR code (code payment). When a user visits the store and selects "QR code" from the selection screen 131A, the processing of the sequence diagram shown in Figure 11 begins.

The reception unit 21 of the store terminal 20 transitions the selection screen 131 to a selection screen 131B for selecting a refueling method. Selection screen 131B is a screen for selecting, for example, the type of gasoline to be refueled and whether the provisional payment amount is to be specified directly by amount (hereinafter referred to as "specifying amount") or by quantity (hereinafter referred to as "specifying quantity"). For example, when the user selects specifying amount, the reception unit 21 transitions the selection screen 131 to a selection screen 131C for selecting the amount of refueling, i.e., the provisional payment amount. In the example of FIG. 12, the selection screen 131C is a screen for selecting the provisional payment amount from multiple amount options. The reception unit 21 may also display a numeric keypad on the selection screen 131C to accept the provisional payment amount entered by the user.

When the user selects the refueling amount on selection screen 131C, the reception unit 21 transitions selection screen 131 to selection screen 131D for selecting a payment brand. The user selects a payment brand from selection screen 131D. As a result, the reception unit 21 accepts the provisional payment amount and payment brand as selection information based on the user's selection operation on selection screens 131C and 131D (step S10).

The order of transition between selection screen 131C and selection screen 131D may be reversed. Furthermore, when quantity specification is selected on selection screen 131B, the reception unit 21 may transition to a selection screen for selecting information for specifying the amount of fuel to be refueled, i.e., the provisional payment amount. The reception unit 21 may then calculate the provisional payment amount from the accepted quantity. Furthermore, when "full tank" is selected on selection screen 131B, the reception unit 21 may accept a predetermined upper limit amount as the provisional payment amount. The predetermined upper limit amount may be the maximum amount expected when a full tank is refueled, an upper limit amount set in payment terms, or the like.

The reception unit 21 passes the received payment brand and provisional payment amount to the transceiver unit 22 of the store terminal 20. The transceiver unit 22 then transmits a QR request to the relay device 30, including information on the payment business code of the payment business corresponding to the payment brand, the store code, and the provisional payment amount (step S11).

Then, the transmitter/receiver 31 of the relay device 30 receives the QR request sent from the store terminal 20. The transmitter/receiver 31 transmits the QR request to the payment service provider device 40 indicated by the payment service provider code included in the QR request (S12).

Then, the transceiver unit 41 of the payment service provider device 40 receives the QR request sent from the relay device 30. The transceiver unit 41 passes the received QR request to the issuing unit 42. The issuing unit 42 assigns a payment ID to the corresponding payment process and issues a QR code representing the payment service provider code, provisional payment amount, and payment ID included in the QR request. The issuing unit 42 then passes the code information representing the issued QR code and the store code included in the QR request to the transceiver unit 41 as information related to the QR code. The transceiver unit 41 transmits the information related to the QR code to the relay device 30 as a QR return (step S13).

The transmitter/receiver 31 of the relay device 30 receives the QR response sent from the payment service provider device 40. The transmitter/receiver 31 transmits the code information included in the received QR response to the store terminal 20 indicated by the store code (step S14).

The transmitter/receiver 31 then passes the received QR reply to the management unit 32 of the relay device 30. The management unit 32 assigns the date and time of reception to the store code included in the QR reply, the payment provider code and provisional payment amount represented by the code information, and stores them in the payment status DB 38 using the payment ID as a key. The management unit 32 also stores information indicating the status of the payment process indicated by that payment ID, indicating that the code information has been sent and that the provisional payment result is awaited, in association with that payment ID (step S15). Figure 13 shows an example of the payment status DB 38. In the example of Figure 13, the first row is an example of the information stored in this step.

The transmitter/receiver 22 of the store terminal 20 receives the code information transmitted from the relay device 30. The transmitter/receiver 22 passes the received code information to the display controller 23 of the store terminal 20. The display controller 23 displays the code image represented by the code information, i.e., the QR code, on the display device (step S16). After displaying the QR code, the display controller 23 notifies the refueling controller 24 that the display is complete. The refueling controller 24 starts polling the relay device 30 and monitors whether the relay device 30 has received a provisional payment result from the payment provider device 40 (step S17). Specifically, the refueling controller 24 monitors whether a provisional payment result has been received by obtaining the latest status corresponding to the payment ID included in the code information indicating the displayed QR code from the payment status DB 38 of the relay device 30. In the case of the payment status DB 38 shown in FIG. 13, the latest status corresponding to the payment ID is the "status" associated with the "payment ID" for which the "date and time" is the most recent "payment ID."

The upper diagram in Figure 14 shows an example of a QR screen 132 displayed on the display device of the store terminal 20. The user launches a payment application corresponding to the specified payment brand on the user terminal 10 and performs a reading operation on the QR code displayed on the QR screen 132. This causes the reading unit 11 of the user terminal 10 to read the QR code (step S18). The reading unit 11 passes provisional payment information including the code information obtained by reading the QR code and the user ID to the transceiver unit 12 of the user terminal 10. The transceiver unit 12 transmits the provisional payment information passed from the reading unit 11 to the payment service provider device 40 corresponding to the payment application (step S19).

The transmitter/receiver unit 41 of the payment provider device 40 receives the provisional payment information transmitted from the user terminal 10. The transmitter/receiver unit 41 passes the received provisional payment information to the first payment unit 43 and the second payment unit 44. The first payment unit 43 executes the provisional payment process for the provisional payment amount indicated in the provisional payment information passed from the transmitter/receiver unit 41. The first payment unit 43 then associates the payment ID included in the provisional payment information with the personal authentication result and result-related information including information indicating that the provisional payment process has been completed or an error code, and passes this to the transmitter/receiver unit 41 as the provisional payment result. The transmitter/receiver unit 41 transmits the provisional payment result received from the first payment unit 43 to the relay device 30 (step S20).

The transmitter/receiver 31 of the relay device 30 receives the provisional payment result transmitted from the payment provider device 40. The transmitter/receiver 31 passes the received provisional payment result to the management unit 32. The management unit 32 assigns the date and time of reception to the payment ID included in the provisional payment result and stores it in the payment status DB 38. Furthermore, if the result included in the provisional payment result is "OK," the management unit 32 stores information indicating that the provisional payment has been completed and that the fuel supply is waiting to be completed, in association with the corresponding payment ID, as information indicating the status of the payment process. Furthermore, if the provisional payment result includes an error code, the management unit 32 stores the error code in association with the corresponding payment ID as information indicating the status of the payment process (step S21). In the example of Figure 13, the second line is an example of information stored in this step when the result is "OK." Furthermore, the sixth line is an example of information stored in this step when an error occurs.

When the refueling control unit 24 of the store terminal 20 detects by polling the relay device 30 that the provisional payment result corresponding to the target payment ID is OK (step S22), it notifies the refueling machine 28 that refueling is possible (step S23). The refueling control unit 24 also notifies the refueling machine 28 of the amount of refueling corresponding to the provisional payment amount or quantity specified by the user. The refueling control unit 24 then displays a message screen 133 on the display device of the store terminal 20 to notify the user that refueling is possible, as shown in the middle diagram of FIG. 14 (step S23). Note that if the provisional payment result indicates an error due to, for example, insufficient balance, the refueling control unit 24 does not notify the refueling machine 28 to start refueling, but instead displays an error message instead of the message screen 133 as shown in FIG. 14. If the refueling control unit 24 has controlled the refueling machine 28 to be in a state where refueling is possible, it notifies the determination unit 25 to that effect.

When the user refuels, completes the refueling, and performs a completion action such as returning the nozzle to a predetermined position, the determination unit 25 detects the completion action and obtains the actual amount of fuel dispensed from the fuel dispenser 28 (step S24). The determination unit 25 determines the final payment amount by multiplying the obtained amount of fuel dispensed by the unit price of the type of gasoline selected on the selection screen 131B. The determination unit 25 passes the determined final payment amount to the transmission/reception unit 22. The transmission/reception unit 22 transmits final payment information including the payment ID, payment provider code, store code, and final payment amount to the relay device 30 (step S25).

The transmitter/receiver unit 31 of the relay device 30 receives the final payment information transmitted from the store terminal 20. The transmitter/receiver unit 31 transmits the final payment information to the payment provider device 40 identified by the payment provider code included in the final payment information (step S26). The transmitter/receiver unit 31 then passes the received final payment information to the management unit 32. The management unit 32 assigns the date and time of reception to the payment provider code, store code, and final payment amount included in the final payment information, and stores them in the payment status DB 38 using the payment ID as a key. The management unit 32 also stores information indicating that refueling is complete and the final payment result is awaited, in association with the payment ID, as information indicating the status of the payment process indicated by the payment ID (step S27). In the example of Figure 13, the third line is an example of the information stored in this step.

The transceiver unit 41 of the payment provider device 40 receives the final payment information transmitted from the relay device 30. The transceiver unit 41 passes the received final payment information to the second payment unit 44. The second payment unit 44 executes the final payment process for the difference between the provisional payment amount included in the provisional payment information transmitted from the transceiver unit 41 and the final payment amount included in the final payment information, so that the final payment amount becomes the final payment amount. The second payment unit 44 associates the payment ID included in the final payment information with the payment amount and result-related information including the result of the payment process or an error code, and transmits this to the transceiver unit 41 as the final payment result. The transceiver unit 41 transmits the final payment result to the relay device 30 and the user terminal 10 (steps S28 and S29).

The transmitter/receiver unit 31 of the relay device 30 receives the final payment result transmitted from the payment provider device 40. The transmitter/receiver unit 31 passes the received final payment result to the management unit 32. The management unit 32 assigns the date and time of receipt to the payment amount included in the final payment result, and stores it in the payment status DB 38 using the payment ID as a key. The management unit 32 also stores information indicating the completion of the final payment in association with the corresponding payment ID as information indicating the status of the payment process. If the final payment result includes an error code, the management unit 32 also stores the error code in association with the corresponding payment ID as information indicating the status of the payment process (step S30).

When the decision unit 25 of the store terminal 20 detects, by polling the relay device 30, that the final payment result corresponding to the target payment ID has been approved, it obtains the final payment result from the payment status DB 38 (step S31). The decision unit 25 associates the final payment information with the final payment result and stores them in a specified memory area. The decision unit 25 also displays a receipt showing the details of the payment on a display device or outputs it using a printer. For example, the decision unit 25 displays a receipt screen 134 such as the one shown in the lower part of Figure 14 on a display device. The receipt screen 134 of Figure 14 displays the actual amount of fuel refueled and the final payment amount, as well as the provisional payment amount as a deposit and the difference between the provisional payment amount and the final payment amount as a refund. Note that the display example of the receipt screen 134 is not limited to that of Figure 14. For example, the display may be something like "Total: 4,000 yen, Payment: 5,000 yen, Change: 1,000 yen" or "Payment: 5,000 yen, Cancellation: 5,000 yen, Payment: 4,000 yen." The display may be based on the implementation used by the payment service provider (for example, the implementation shown in Figure 6). The user terminal 10 may also display a screen similar to the receipt screen 134 described above based on the received payment result (step S32).

As described above, according to the code payment system of the first embodiment, the user terminal reads a QR code associated with a payment provider and acquires provisional payment information, in which the provisional payment amount for the refueling amount is associated with the code information. The provisional payment information is then transmitted from the user terminal to the payment provider device, which then executes provisional payment processing for the provisional payment amount indicated in the provisional payment information. The store terminal then controls the vehicle to a state where refueling is possible after the provisional payment processing is completed, and when it detects that refueling is complete, it determines the final payment amount equivalent to the actual amount of refueling. The store terminal then transmits final payment information, including the final payment amount, to the payment provider device, which then executes final payment processing for the difference between the provisional payment amount and the final payment amount. In this way, user convenience is ensured because the user only needs to scan the QR code once. Furthermore, because the vehicle is not ready to refuel until the provisional payment is completed, fraudulent use, such as filling up and running with gasoline, can be prevented.

In the first embodiment, a case where a selection screen or the like is displayed on a display device provided in a store terminal is described, but the store terminal and the display device are not limited to being integrated together. For example, a display device may be provided separately from the store terminal, and the store terminal and the display device may be connected via a LAN. Alternatively, a store staff member may carry a tablet terminal or the like, which may function as the display device.

Second Embodiment
In the second embodiment, an example of a CPM (Consumer-Presented Mode) system will be described, in which a QR code (registered trademark) presented by a user is read by a store. In the code payment system according to the second embodiment, components similar to those in the code payment system 1 according to the first embodiment will be assigned the same reference numerals and detailed descriptions thereof will be omitted. Furthermore, for functional units whose reference numerals have the same last two digits between the first and second embodiments, descriptions of similar functions will be omitted.

Figure 15 shows the schematic configuration of the code payment system 2 according to the second embodiment. As shown in Figure 15, the code payment system 2 according to the second embodiment includes a user terminal 210, a store terminal 220, a handheld terminal 229, a relay device 230, and a payment service provider device 240. The store terminal 220 and the handheld terminal 229 are communicatively connected via a LAN. Note that the number of components included in the code payment system 2 is not limited to the example shown in Figure 15.

The handheld terminal 229 is an information processing terminal carried by store staff. The handheld terminal 229 includes a QR code reading unit, a display unit and input unit realized by a touch panel display or the like, and a communication unit. The handheld terminal 229 is, for example, a smartphone, tablet terminal, portable POS terminal, etc. The handheld terminal 229 reads the QR code displayed on the display device of the user terminal 210 and transmits the acquired code information to the store terminal 220.

The following describes the functional configuration of each of the user terminal 210, store terminal 220, relay device 230, and payment provider device 240.

First, the functional configuration of the user terminal 210 will be described. As shown in FIG. 16, the user terminal 210 includes a display control unit 213 and a transmission/reception unit 212. The display control unit 213 and the transmission/reception unit 212 are examples of an acquisition unit of the disclosed technology.

When the user launches a payment application corresponding to the specified payment brand on the user terminal 210 and selects the QR code display menu, the display control unit 213 displays a QR code on the display device of the user terminal 10. The QR code here represents the payment ID, payment provider code, and user ID.

The transmitter/receiver unit 212 receives the payment result from the payment provider device 40.

Next, the functional configuration of the store terminal 220 will be described. As shown in FIG. 17, the store terminal 220 includes a reception unit 221, a transmission/reception unit 222, a refueling control unit 24, and a determination unit 25.

The reception unit 221 receives the provisional payment amount or information for specifying the provisional payment amount through selection operations on the selection screen by the staff member who has heard the user's selection. The reception unit 221 is similar to the reception unit 21 of the first embodiment, except that it does not receive the specification of the payment brand that the reception unit 21 of the first embodiment receives. The reception unit 221 passes the provisional payment amount to the transmission/reception unit 222. Note that the selection operations on the selection screen do not necessarily have to be performed by the staff member, but may also be performed by the user themselves.

The transmitter/receiver unit 222 receives code information from the handheld terminal 229. The transmitter/receiver unit 222 transmits provisional payment information to the relay device 230, including the received code information (payment ID, payment provider code, and user ID), the store code, and the provisional payment amount received from the reception unit 221. After transmitting the provisional payment information, the transmitter/receiver unit 222 notifies the refueling control unit 24 that transmission of the provisional payment information has been completed.

The only difference is that in the first embodiment, the refueling control unit 24 starts polling upon receiving notification that the QR code display has been completed, whereas in the second embodiment, the refueling control unit 24 starts polling upon receiving notification that the above-mentioned provisional payment information has been sent.

Next, the functional configuration of the relay device 230 will be described. As shown in FIG. 4, the relay device 230 includes a transmission/reception unit 231 and a management unit 232. In addition, a payment status DB 38 is stored in a predetermined storage area of the relay device 230.

The transmitter/receiver 231 receives provisional payment information from the store terminal 220. The transmitter/receiver 231 transmits the received provisional payment information to the payment service provider device 240 corresponding to the payment service provider code included in the provisional payment information. The transmitter/receiver 231 also passes the received provisional payment information to the management unit 232. The transmitter/receiver 231 also receives the provisional payment result, the actual payment information, and the actual payment result in the same way as the transmitter/receiver 31 in the first embodiment.

When the management unit 232 receives provisional payment information from the transmission/reception unit 231, it assigns the date and time of reception to the store code included in the provisional payment information and the payment provider code included in the code information, and stores them in the payment status DB 38 using the payment ID as a key. The management unit 232 also stores, in association with the payment ID, information indicating the status of the payment process indicated by that payment ID, indicating that the provisional payment information has been sent and that the provisional payment result is awaited. The management unit 232 also performs the same process as the management unit 32 in the first embodiment to store the provisional payment result, the actual payment information, and the actual payment result in the payment status DB 38.

Next, we will explain the functional configuration of the payment service provider device 240. As shown in FIG. 18, the payment service provider device 240 includes a transmitter/receiver unit 241, a first payment unit 43, and a second payment unit 44.

The transmitter/receiver unit 241 is similar to the transmitter/receiver unit 41 in the first embodiment, except that it does not receive QR requests or send QR replies, and receives provisional payment information from the relay device 230 rather than the user terminal 210.

Next, we will explain the hardware configuration of each of the user terminal 210, store terminal 220, relay device 230, and payment service provider device 240.

The user terminal 210 may be realized, for example, by a computer 50 shown in FIG. 7. A user terminal program 260 for causing the computer 50 to function as the user terminal 210 is stored in the storage unit 53 of the computer 50. The user terminal program 260 includes a display control process 263 and a transmission/reception process 262.

The CPU 51 reads the user terminal program 260 from the storage unit 53, expands it in the memory 52, and sequentially executes the processes contained in the user terminal program 260. The CPU 51 operates as the display control unit 213 shown in FIG. 16 by executing the display control process 263. The CPU 51 also operates as the transmission/reception unit 212 shown in FIG. 16 by executing the transmission/reception process 262. As a result, the computer 50 that has executed the user terminal program 260 functions as the user terminal 210.

The store terminal 220 may be realized, for example, by a computer 70 shown in FIG. 8. A store terminal program 280 for causing the computer 70 to function as the store terminal 220 is stored in the storage unit 73 of the computer 70. The store terminal program 280 includes a reception process 281, a transmission/reception process 282, a refueling control process 84, and a decision process 85.

The CPU 71 reads the store terminal program 280 from the storage unit 73, expands it in the memory 72, and sequentially executes the processes of the store terminal program 280. The CPU 71 operates as the reception unit 221 shown in FIG. 17 by executing the reception process 281. The CPU 71 also operates as the transmission/reception unit 222 shown in FIG. 17 by executing the transmission/reception process 282. The other processes are the same as those of the store terminal program 80 according to the first embodiment. As a result, the computer 70 that has executed the store terminal program 280 functions as the store terminal 220.

The relay device 230 may be realized, for example, by a computer 90 shown in FIG. 9. A relay device program 2100 for causing the computer 90 to function as the relay device 230 is stored in the memory unit 93 of the computer 90. The relay device program 2100 includes a transmission/reception process 2101 and a management process 2102. The memory unit 93 also includes an information storage area 108 in which information constituting the payment status DB 38 is stored.

The CPU 91 reads the relay device program 2100 from the storage unit 93, loads it into the memory 92, and sequentially executes the processes of the relay device program 2100. The CPU 91 operates as the transmission/reception unit 231 shown in FIG. 4 by executing the transmission/reception process 2101. The CPU 91 also operates as the management unit 232 shown in FIG. 4 by executing the management process 2102. The CPU 91 also reads information from the information storage area 108 and loads the payment status DB 38 into the memory 92. As a result, the computer 90 that has executed the relay device program 2100 functions as the relay device 230.

The payment service provider device 240 may be realized, for example, by the computer 110 shown in FIG. 10. The memory unit 113 of the computer 110 stores a payment service provider device program 2120 for causing the computer 110 to function as the payment service provider device 240. The payment service provider device program 2120 includes a transmission/reception process 2121, a first payment process 123, and a second payment process 124.

The CPU 111 reads the payment service provider device program 2120 from the storage unit 113, expands it in the memory 112, and sequentially executes the processes contained in the payment service provider device program 2120. By executing the transmission/reception process 2121, the CPU 111 operates as the transmission/reception unit 241 shown in FIG. 18. The other processes are the same as those in the payment service provider device program 120 according to the first embodiment. As a result, the computer 110 that executes the payment service provider device program 2120 functions as the payment service provider device 240.

The functions realized by each program can also be realized, for example, by a semiconductor integrated circuit, or more specifically, an ASIC.

Next, the operation of the code payment system 2 according to the second embodiment will be described with reference to the sequence diagram shown in Figure 19. The series of processes shown in the sequence diagram in Figure 19 is an example of the code payment method of the disclosed technology.

When a user visits a store, they launch a payment application corresponding to the specified payment brand on their user terminal 210 and perform an operation to display the QR code, such as by selecting the QR code display menu. This starts the processing in the sequence diagram shown in Figure 19. The display control unit 213 of the user terminal 210 displays a QR code representing the payment ID, payment business operator code, and user ID on the display device of the user terminal 210 (step S210). Figure 20 shows an example of a QR code displayed on the display device of the user terminal 210.

The store staff member uses the handheld terminal 229 to read the QR code displayed on the display device of the user terminal 210 (step S211). The handheld terminal 229 then transmits the code information obtained by reading the QR code to the store terminal 220 (step S212).

The transmitter/receiver unit 222 of the store terminal 220 receives the code information transmitted from the handheld terminal 229. The reception unit 221 also receives selection information, which is information for specifying the provisional payment amount, from the staff member who has heard the user's selection (step S213). For example, the reception unit 221, similar to the reception unit 21 in the first embodiment, displays a selection screen 131 such as that shown in FIG. 12 to receive the selection information. Note that because the selection of the payment brand is performed on the user terminal 210 side, the selection screen 131D of FIG. 12 is unnecessary. The reception unit 221 passes the provisional payment amount based on the selection information to the transmitter/receiver unit 222. The transmitter/receiver unit 222 transmits provisional payment information including the received code information (payment ID, payment service provider code, and user ID), the store code, and the provisional payment amount received from the reception unit 221 to the relay device 230 (step S214).

The transmitter/receiver unit 231 of the relay device 230 receives the provisional payment information transmitted from the store terminal 220. The transmitter/receiver unit 231 transmits the received provisional payment information to the payment service provider device 240 corresponding to the payment service provider code included in the provisional payment information (step S215). The transmitter/receiver unit 231 also passes the received provisional payment information to the management unit 232. The management unit 232 assigns the date and time of reception to the store code included in the provisional payment information and the payment service provider code included in the code information, and stores them in the payment status DB 38 using the payment ID as a key. The management unit 232 also stores information indicating that the provisional payment information has been sent and that the provisional payment result is awaited, in association with the payment ID, as information indicating the status of the payment processing indicated by that payment ID (step S216).

Then, steps S20 to S32 are executed in the same manner as in the code payment system 1 of the first embodiment.

As described above, in the code payment system according to the second embodiment, a QR code displayed on a user terminal and associated with a payment provider is read by a handheld terminal connected to a store terminal. The handheld terminal acquires provisional payment information, which associates the provisional payment amount for the refueling with the read code information. The provisional payment information is then transmitted from the store terminal to a payment provider device, and the payment provider device executes provisional payment processing for the provisional payment amount indicated in the provisional payment information. The store terminal then controls the vehicle to a state in which refueling is possible after the provisional payment processing is completed, and when it detects that refueling is complete, it determines the final payment amount equivalent to the actual amount of refueling. The store terminal then transmits final payment information, including the final payment amount, to the payment provider device, and the payment provider device executes final payment processing for the difference between the provisional payment amount and the final payment amount. In this way, convenience for users is ensured because the user only needs to present the QR code once. Furthermore, because the vehicle is not ready to refuel until the provisional payment is completed, fraudulent use, such as filling up and running with gasoline, can be prevented.

In the second embodiment, we have described a case where the provisional payment amount or selection information, which is information for specifying the provisional payment amount, is obtained by a staff member or user making a selection on a selection screen displayed on the store terminal, but this is not limited to this. For example, an application running on a user terminal may display a screen similar to the selection screen displayed on the store terminal, accept selection information from the user, and transmit the selection information from the user terminal to the store terminal.

Third Embodiment
In the third embodiment, an example of a static MPM system will be described in which a user reads a QR code (registered trademark) that is statically presented at a store. In the code payment system according to the third embodiment, components similar to those in the code payment system 1 according to the first embodiment or the code payment system 2 according to the second embodiment will be assigned the same reference numerals and detailed descriptions thereof will be omitted. Furthermore, for functional units whose reference numerals have the same last two digits as those in the first or second embodiment, descriptions of similar functions will be omitted.

Figure 1 shows the schematic configuration of a code payment system 3 according to the third embodiment. As shown in Figure 1, the code payment system 3 according to the third embodiment includes a user terminal 310, a store terminal 320, a relay device 330, and a payment service provider device 340. Note that the number of components included in the code payment system 3 is not limited to the example shown in Figure 1.

The functional configuration of each of the user terminal 310, store terminal 320, relay device 330, and payment service provider device 340 will be explained below.

First, the functional configuration of the user terminal 310 will be described. As shown in FIG. 21 , the user terminal 310 includes a reading unit 311, a receiving unit 314, and a transmitting/receiving unit 312. The reading unit 311, the receiving unit 314, and the transmitting/receiving unit 312 are examples of acquisition units of the disclosed technology.

The reading unit 311 reads a fixedly displayed or printed QR code. The QR code in the third embodiment represents a payment service provider code. For example, a staff member may carry a card with the QR code printed on it, a panel or sticker with the QR code printed on it may be placed in a designated location in the store, or a fixed QR code may be displayed on a display device placed in a designated location in the store. The user specifies a payment brand and performs a reading operation on the QR code corresponding to that payment brand. The reading unit 311 passes the code information (payment service provider code) obtained by reading the QR code to the transmission/reception unit 312.

The reception unit 314 receives a provisional payment amount or information for specifying the provisional payment amount from the user. Specifically, the reception unit 314 displays a selection screen on the display device provided in the user terminal 310 for selecting the provisional payment amount or information for specifying the provisional payment amount. The reception unit 314 receives selected information selected from the selection screen by the user's selection operation. When the reception unit 314 receives a quantity as information for specifying the provisional payment amount, it calculates the provisional payment amount based on the quantity and the unit price of the product or service. The reception unit 314 passes the received provisional payment amount to the transmission/reception unit 312.

The transmitter/receiver unit 312 transmits provisional payment information, including the code information received from the reader unit 311, the provisional payment amount received from the receiver unit 314, and the user ID, to the corresponding payment service provider device 40. Furthermore, the transmitter/receiver unit 312 receives the payment result in the same way as the transmitter/receiver unit 12 in the first embodiment.

Next, the functional configuration of the store terminal 320 will be described. As shown in FIG. 22, the store terminal 320 includes a refueling control unit 24, a determination unit 25, and a transmission/reception unit 322.

When the transmitter/receiver unit 322 receives information about the actual payment amount from the determination unit 25, it transmits the actual payment information, including the payment ID, payment provider code, store code, and actual payment amount, to the relay device 330.

Next, the functional configuration of the relay device 330 will be described. As shown in FIG. 4, the relay device 330 includes a transmission/reception unit 331 and a management unit 332. In addition, a payment status DB 38 is stored in a specified memory area of the relay device 330.

The transmitter/receiver unit 331 is similar to the transmitter/receiver unit 231 in the second embodiment, except that it does not receive provisional payment information from the store terminal 320, transmit provisional payment information to the payment service provider device 340, or pass provisional payment information to the management unit 332.

The management unit 332 is similar to the management unit 232 in the second embodiment, except that it does not store provisional payment information in the payment status DB 38.

Next, we will explain the functional configuration of the payment service provider device 340. As shown in FIG. 18, the payment service provider device 340 includes a transmitter/receiver unit 341, a first payment unit 43, and a second payment unit 44.

The transmitter/receiver unit 341 is similar to the transmitter/receiver unit 241 in the second embodiment, except that it receives provisional payment information from the user terminal 310 rather than the relay device 330.

Next, we will explain the hardware configuration of each of the user terminal 310, store terminal 320, relay device 330, and payment service provider device 340.

The user terminal 310 may be realized, for example, by a computer 50 shown in FIG. 7. A user terminal program 360 for causing the computer 50 to function as the user terminal 310 is stored in the storage unit 53 of the computer 50. The user terminal program 360 has a reading process 361, a reception process 364, and a transmission/reception process 362.

The CPU 51 reads the user terminal program 360 from the storage unit 53, expands it in the memory 52, and sequentially executes the processes of the user terminal program 360. By executing the reading process 361, the CPU 51 operates as the reading unit 311 shown in FIG. 21. By executing the reception process 364, the CPU 51 operates as the reception unit 314 shown in FIG. 21. By executing the transmission/reception process 362, the CPU 51 operates as the transmission/reception unit 312 shown in FIG. 21. As a result, the computer 50 that has executed the user terminal program 360 functions as the user terminal 310.

The store terminal 320 may be realized, for example, by a computer 70 shown in FIG. 8. A store terminal program 380 for causing the computer 70 to function as the store terminal 320 is stored in the storage unit 73 of the computer 70. The store terminal program 380 includes a transmission/reception process 382, a refueling control process 84, and a decision process 85.

The CPU 71 reads the store terminal program 380 from the storage unit 73, expands it in the memory 72, and sequentially executes the processes of the store terminal program 380. By executing the transmission/reception process 382, the CPU 71 operates as the transmission/reception unit 322 shown in FIG. 22. The other processes are the same as those of the store terminal program 80 according to the first embodiment. As a result, the computer 70 that executes the store terminal program 380 functions as the store terminal 320.

The relay device 330 may be realized, for example, by the computer 90 shown in FIG. 9. A relay device program 3100 for causing the computer 90 to function as the relay device 330 is stored in the memory unit 93 of the computer 90. The relay device program 3100 includes a transmission/reception process 3101 and a management process 3102. The memory unit 93 also includes an information storage area 108 in which information constituting the payment status DB 38 is stored.

The CPU 91 reads the relay device program 3100 from the storage unit 93, loads it into the memory 92, and sequentially executes the processes of the relay device program 3100. The CPU 91 operates as the transmission/reception unit 331 shown in FIG. 4 by executing the transmission/reception process 3101. The CPU 91 also operates as the management unit 332 shown in FIG. 4 by executing the management process 3102. The CPU 91 also reads information from the information storage area 108 and loads the payment status DB 38 into the memory 92. As a result, the computer 90 that has executed the relay device program 3100 functions as the relay device 330.

The payment service provider device 340 may be realized, for example, by the computer 110 shown in FIG. 10. The memory unit 113 of the computer 110 stores a payment service provider device program 3120 for causing the computer 110 to function as the payment service provider device 340. The payment service provider device program 3120 includes a transmission/reception process 3121, a first payment process 123, and a second payment process 124.

The CPU 111 reads the payment service provider device program 3120 from the storage unit 113, expands it in the memory 112, and sequentially executes the processes contained in the payment service provider device program 3120. By executing the transmission/reception process 3121, the CPU 111 operates as the transmission/reception unit 341 shown in FIG. 18. The other processes are the same as those in the payment service provider device program 120 according to the first embodiment. As a result, the computer 110 that executes the payment service provider device program 3120 functions as the payment service provider device 340.

The functions realized by each program can also be realized, for example, by a semiconductor integrated circuit, or more specifically, an ASIC.

Next, the operation of the code payment system 3 according to the third embodiment will be described with reference to the sequence diagram shown in Figure 23. The series of processes shown in the sequence diagram in Figure 23 is an example of the code payment method of the disclosed technology.

For example, as shown in Figure 24, store staff carry cards 140 with QR codes printed for each payment brand. When a user visits a store and informs the staff of the specified payment brand, the staff presents the corresponding card 140. The user launches a payment application corresponding to the specified payment brand on the user terminal 310 and performs an operation to read the QR code printed on the presented card 140. The reading unit 311 passes the code information (payment business operator code) obtained by reading the QR code to the transmission/reception unit 312 (step S310).

As shown in FIG. 24, the reception unit 314 displays a selection screen 142 on the display device provided on the user terminal 310 for selecting the provisional payment amount or information for specifying the provisional payment amount. The example in FIG. 24 is a selection screen 142 for selecting the amount of fuel to be supplied, which is displayed when the user selects to specify the amount. If the user selects to specify the quantity, the reception unit 314 may display a selection screen for selecting the amount of fuel to be supplied. The reception unit 314 accepts the selection information selected from the selection screen by the user's selection operation (step S311). If the reception unit 314 accepts the quantity as information for specifying the provisional payment amount, it calculates the provisional payment amount based on the quantity and the unit price of the product or service. The reception unit 314 passes the accepted provisional payment amount to the transmission/reception unit 312.

The transmitter/receiver 312 transmits the provisional payment information, including the code information received from the reader 311, the provisional payment amount received from the acceptor 314, and the user ID, to the corresponding payment service provider device 40 (step S312). Thereafter, steps S20 to S32 are executed, similar to the code payment system 1 of the first embodiment.

As described above, the code payment system according to the third embodiment acquires provisional payment information, which associates the provisional payment amount for the amount of fuel with a fixedly displayed or printed QR code associated with a payment provider. The provisional payment information is then transmitted from the user terminal to the payment provider device, which then executes provisional payment processing for the provisional payment amount indicated in the provisional payment information. The store terminal then controls the vehicle to a state where fueling is possible after the provisional payment processing is completed, and when it detects that fueling is complete, determines the final payment amount equivalent to the actual amount of fuel. The store terminal then transmits final payment information, including the final payment amount, to the payment provider device, which then executes final payment processing for the difference between the provisional payment amount and the final payment amount. In this way, convenience for users is ensured because the user only needs to scan the QR code once. Furthermore, since fueling is not possible until the provisional payment is completed, fraudulent use, such as filling up and running with gasoline, can be prevented.

In the third embodiment, a case has been described in which the provisional payment amount or information for specifying the provisional payment amount is input on a selection screen displayed on the user terminal, but this is not limited to this. For example, as shown in FIG. 25, a QR code may be prepared for each payment brand and for each amount for specifying the amount. In this case, the user simply reads the QR code corresponding to the specified payment brand and provisional payment amount with the user terminal 310. In this case, the code information obtained by reading the QR code indicates the payment company code and the provisional payment amount.

In addition, in the third embodiment, the staff member operates the store terminal 320 to obtain the provisional payment result from the relay device 330. If the store terminal 320 is operated before the user reads the QR code, the store terminal 320 continues polling until the provisional payment result is stored in the payment status DB 38 of the relay device 330. If the store terminal 320 is operated after the user reads the QR code, the store terminal 320 sends a request to obtain the provisional payment result to the relay device 330 in response to the operation of the store terminal 320, and the provisional payment result is obtained.

In addition, while the third embodiment describes the case where a QR code is prepared for each payment brand, a QR code common to all payment brands may also be prepared. JPQR exists as a common QR code, but since JPQR has the issue of high payment fees, a QR code containing an oil industry common identifier that can be used at any gas station may be prepared. In this case, provisional payment information containing code information indicated by the QR code read by the user terminal or store terminal is sent to the payment service provider device. The payment service provider device notifies the relay device of the provisional payment result "OK" if it can confirm the oil industry common identifier from the code information included in the provisional payment information, along with authenticating the user and confirming the balance.

In addition, in the above embodiments, a payment ID is used to identify a series of payment processes at the user terminal, store terminal, relay device, and payment service provider device, but this is not limited to this. The relevant payment process may also be identified based on the store code, payment service provider code, receipt date and time, etc. Furthermore, if a store has multiple fuel lanes, the identification number of the fuel lane may also be included along with the store code.

In addition, in each of the above embodiments, the payment provider device may store the user's membership registration information in association with the user ID, and during the payment process, refer to the membership registration information to make a payment using points or coupons.

Furthermore, in each of the above embodiments, if an error occurs during processing or communication at the payment service provider device, a provisional payment result or final payment result including an error code indicating the error is sent to the relay device (e.g., line 8 in Figure 13). In this case, the user terminal or store terminal can cancel the processing based on the provisional payment information or final payment information that was sent. The same applies if an error occurs during processing or communication at the relay device.

For example, if a failure occurs between the relay device and the payment provider device during processing of provisional payment information, and an error is stored as the provisional payment result in the payment status DB of the relay device, the store terminal can cancel the processing of the provisional payment information. Also, for example, if a failure occurs between the store terminal and the relay device during processing of provisional payment information, and processing times out on the store terminal. In this case, if there is no response from the relay device within a certain period of time after the store terminal requests processing of the provisional payment information, the store terminal can cancel the processing of the provisional payment information.

Also, for example, suppose that after the provisional payment result "OK" is confirmed and refueling is possible, the completion of refueling is not detected for reasons such as the nozzle not being returned to the designated position, causing the relay device's processing to time out. In this case, if the relay device does not receive the actual payment information after a certain amount of time has passed since returning the provisional payment result, it can cancel the timeout error. Note that, in consideration of cases where refueling takes time, the store terminal may be able to request the relay device to extend the timeout on the relay device.

For example, if a failure occurs between the relay device and the payment provider device during processing of the actual payment information, and an error is stored as the actual payment result in the payment status DB of the relay device, the store terminal can cancel processing of the provisional payment information. For example, if a failure occurs between the store terminal and the relay device during processing of the actual payment information, and processing times out on the store terminal. In this case, if there is no response from the relay device within a certain period of time after the store terminal requests processing of the actual payment information, the store terminal can cancel processing of the actual payment information. If processing of the actual payment information is canceled, predetermined processing can be performed, such as reprocessing the actual payment information or settling the difference in cash.

For example, in the static MPM of the third embodiment, if a staff member operates a store terminal after reading a QR code on a user terminal, the operation on the store terminal may be delayed, resulting in a timeout. In this case, the store terminal can cancel the processing of the provisional payment information, and then the QR code can be read again on the user terminal.

Furthermore, in the above embodiments, a case has been described in which the code payment system of the disclosed technology is applied to the payment of fuel fees at a self-service gas station, but this is not limited to this. The disclosed technology can be applied in any case in which the official amount is determined after the product or service is provided.

Furthermore, while the above embodiment describes a configuration in which each program is pre-stored (installed) in a storage unit, this is not limited to this. The programs related to the disclosed technology can also be provided in a form stored on a storage medium such as a CD-ROM, DVD-ROM, or USB memory.

The following additional notes are provided regarding each of the above embodiments.

(Appendix 1)
an acquisition unit that acquires provisional payment information in which a first payment amount indicating provisional payment for a product or service is associated with code information obtained by reading a code image associated with a payment service provider;
a first payment unit that executes a payment process for a first payment amount indicated by the provisional payment information;
a control unit that controls the product or service to be ready for provision after the payment process by the first payment unit is completed;
a second payment unit that, when detecting completion of provision of the product or service, determines a second payment amount indicating a formal price for the product or service and executes a payment process for the difference between the first payment amount and the second payment amount;
A code payment system including.

(Appendix 2)
The code payment system described in Appendix 1, wherein the control unit outputs an error message without starting to provide the product or service if an error occurs in the payment processing by the first payment unit.

(Appendix 3)
A code payment system including a payment service provider device under the jurisdiction of the payment service provider, a store terminal provided in a store where the product or the service is provided, and a user terminal used by a user who receives the product or the service,
The acquisition unit acquires the provisional payment information at the user terminal or the store terminal, and transmits the acquired provisional payment information to the payment service provider device;
the first payment unit receives the provisional payment information in the payment service provider device, executes a payment process for the first payment amount indicated by the provisional payment information, and transmits a completion of the payment process to the store terminal;
the control unit controls the store terminal to a state in which the product or the service can be provided when the store terminal receives a notification of completion of the payment process from the payment service provider device;
The second settlement unit
When the store terminal detects that the provision of the product or the service has been completed, the store terminal determines the first payment amount and transmits the determined first payment amount to the payment service provider device;
The code payment system described in Supplementary Note 1 or Supplementary Note 2, wherein the payment service provider device executes a payment process for the difference between the first payment amount and the second payment amount received from the store terminal.

(Appendix 4)
The acquisition unit
At the store terminal, designation of the payment service provider and the first payment amount or information for identifying the first payment amount are accepted, information on the first payment amount is transmitted to the designated payment service provider device, the code image including the information on the first payment amount is received from the payment service provider device, and the received code image is displayed on a display device;
A code payment system as described in Appendix 3, in which the user terminal obtains the provisional payment information by reading the code image displayed on the display device, and transmits the obtained provisional payment information to the payment service provider device.

(Appendix 5)
The code payment system described in Appendix 3, wherein the acquisition unit acquires the code information by reading the code image displayed on the user terminal at the store terminal, acquires the provisional payment information by accepting the first payment amount or information for identifying the first payment amount, and transmits the acquired provisional payment information to the payment service provider device.

(Appendix 6)
The code payment system described in Appendix 3, wherein the acquisition unit acquires the code information by reading the code image that is fixedly displayed or printed on the user terminal, acquires the provisional payment information by accepting the first payment amount or information for identifying the first payment amount, and transmits the acquired provisional payment information to the payment service provider device.

(Appendix 7)
A code payment system as described in Appendix 6, wherein the code image is a code image common to multiple payment service providers.

(Appendix 8)
A code payment system described in any one of Appendix 4 to Appendix 7, wherein when the acquisition unit receives the quantity of the product or service as information for identifying the first payment amount, it calculates the first payment amount based on the quantity and the unit price of the product or service.

(Appendix 9)
A code payment system as described in any one of Supplementary Notes 3 to 8, further including a relay device between the store terminal and the payment provider device that centrally accepts payments from each of multiple payment providers that can be handled by the store terminal and relays processing corresponding to each of the corresponding payment provider devices.

(Appendix 10)
A code payment system described in any one of Supplementary Notes 1 to 9, wherein the first payment amount is set to be greater than the second payment amount.

(Appendix 11)
the product or service is refueling at a gas station,
The control unit controls the fuel dispenser to a state in which fuel can be dispensed after the payment process by the first payment unit is completed.

(Appendix 12)
acquiring provisional payment information in which a first payment amount indicating provisional payment for a product or service is associated with code information obtained by reading a code image associated with a payment service provider;
executes a payment process for the first payment amount indicated by the provisional payment information;
After the payment process for the first payment amount is completed, the product or service is provided.
A code payment method in which a computer executes a process including, when detecting completion of provision of the product or service, determining a second payment amount indicating the official price of the product or service, and executing a payment process for the difference between the first payment amount and the second payment amount.

(Appendix 13)
A code payment method as described in Appendix 12, further including a process for controlling the output of an error message without starting provision of the product or service if an error occurs in the payment process for the first payment amount.

(Appendix 14)
A code payment method executed in a code payment system that includes a payment business device under the jurisdiction of the payment business, a store terminal provided in a store where the product or service is provided, and a user terminal used by a user who receives the product or service,
The user terminal or the store terminal acquires the provisional payment information and transmits the acquired provisional payment information to the payment service provider device;
The payment service provider device receives the provisional payment information, executes a payment process for the first payment amount indicated by the provisional payment information, and transmits a completion of the payment process to the store terminal;
When the store terminal receives a notification of completion of the payment process from the payment service provider device, the store terminal controls the store terminal to a state in which the product or the service can be provided;
When the store terminal detects that the provision of the product or the service has been completed, the store terminal determines the first payment amount and transmits the determined first payment amount to the payment service provider device;
The code payment method described in Supplementary Note 12 or Supplementary Note 13, wherein the payment service provider device executes a payment process for the difference between the first payment amount and the second payment amount received from the store terminal.

(Appendix 15)
At the store terminal, designation of the payment service provider and the first payment amount or information for identifying the first payment amount are accepted, information on the first payment amount is transmitted to the designated payment service provider device, the code image including the information on the first payment amount is received from the payment service provider device, and the received code image is displayed on a display device;
A code payment method as described in Appendix 14, in which the user terminal obtains the provisional payment information by reading the code image displayed on the display device, and transmits the obtained provisional payment information to the payment service provider device.

(Appendix 16)
A code payment method as described in Appendix 14, in which the store terminal acquires the code information by reading the code image displayed on the user terminal, acquires the provisional payment information by accepting the first payment amount or information for identifying the first payment amount, and transmits the acquired provisional payment information to the payment service provider device.

(Appendix 17)
A code payment method as described in Appendix 14, in which the user terminal acquires the code information by reading the code image that is fixedly displayed or printed, acquires the provisional payment information by accepting the first payment amount or information for identifying the first payment amount, and transmits the acquired provisional payment information to the payment service provider device.

(Appendix 18)
A code payment method described in Appendix 17, in which the code image is a code image common to multiple payment service providers.

(Appendix 19)
acquiring provisional payment information in which a first payment amount indicating provisional payment for a product or service is associated with code information obtained by reading a code image associated with a payment service provider;
executes a payment process for the first payment amount indicated by the provisional payment information;
After the payment process for the first payment amount is completed, the product or service is provided.
A code payment program for causing a computer to execute a process including, when detecting completion of provision of the product or service, determining a second payment amount indicating the official price of the product or service, and executing a payment process for the difference between the first payment amount and the second payment amount.

(Appendix 20)
acquiring provisional payment information in which a first payment amount indicating provisional payment for a product or service is associated with code information obtained by reading a code image associated with a payment service provider;
executes a payment process for the first payment amount indicated by the provisional payment information;
After the payment process for the first payment amount is completed, the product or service is provided.
A storage medium storing a code payment program for causing a computer to execute a process including, when detecting completion of provision of the product or service, determining a second payment amount indicating the official price of the product or service, and executing a payment process for the difference between the first payment amount and the second payment amount.

1, 2, 3 Code payment system 10, 210, 310 User terminal 11, 311 Reading unit 12, 212, 312 Transmitting/receiving unit 213 Display control unit 314 Receiving unit 20, 220, 320 Store terminal 21, 221 Receiving unit 22, 222, 322 Transmitting/receiving unit 23 Display control unit 24 Fuel supply control unit 25 Determination unit 28 Fuel supply machine 229 Handy terminal 30, 230, 330 Relay device 31, 231, 331 Transmitting/receiving unit 32, 232, 332 Management unit 38 Payment status DB
40, 240, 340 Payment service provider device 41, 241, 341 Transmitting/receiving unit 42 Issuing unit 43 First payment unit 44 Second payment unit 50, 70, 90, 110 Computer 52, 72, 92, 112 Memory 53, 73, 93, 113 Storage unit 59, 79, 99, 119 Storage medium 60, 260, 360 User terminal program 80, 280, 380 Store terminal program 100, 2100, 3100 Relay device program 120, 2120, 3120 Payment service provider device program 131, 131A, 131B, 131C, 131D, 142 Selection screen 132 QR screen 133 Message screen 134 Receipt screen 140 Card

Claims (14)

an acquisition unit that acquires provisional payment information in which a first payment amount indicating provisional payment for a product or service is associated with code information obtained by reading a code image associated with a payment service provider;
a first payment unit that executes a payment process for a first payment amount indicated by the provisional payment information;
a control unit that controls the product or service to be ready for provision after the payment process by the first payment unit is completed;
a determination unit that determines a second payment amount indicating a formal price for the product or service when completion of provision of the product or service is detected;
a second settlement unit that executes a settlement process for the difference between the first settlement amount and the second settlement amount ,
the product or service is refueling at a gas station,
The control unit controls the fuel dispenser to a state in which fuel can be dispensed after the payment process by the first payment unit is completed.
Code payment system. The code payment system described in claim 1, wherein the control unit outputs an error message without starting provision of the product or service if an error occurs in the payment process by the first payment unit. A code payment system including a payment service provider device under the jurisdiction of the payment service provider, a store terminal provided in a store where the product or the service is provided, and a user terminal used by a user who receives the product or the service,
The acquisition unit acquires the provisional payment information at the user terminal or the store terminal, and transmits the acquired provisional payment information to the payment service provider device;
the first payment unit receives the provisional payment information in the payment service provider device, executes a payment process for the first payment amount indicated by the provisional payment information, and transmits a completion of the payment process to the store terminal;
the control unit controls the store terminal to a state in which the product or the service can be provided when the store terminal receives a notification of completion of the payment process from the payment service provider device;
the determination unit , when detecting completion of provision of the product or the service at the store terminal, determines the second payment amount and transmits the determined second payment amount to the payment service provider device;
The code payment system according to claim 1 or claim 2, wherein the second payment unit executes a payment process in the payment service provider device for the difference between the first payment amount and the second payment amount received from the store terminal. The acquisition unit
At the store terminal, designation of the payment service provider and the first payment amount or information for identifying the first payment amount are accepted, information on the first payment amount is transmitted to the designated payment service provider device, the code image including the information on the first payment amount is received from the payment service provider device, and the received code image is displayed on a display device;
The code payment system of claim 3, wherein the user terminal acquires the provisional payment information by reading the code image displayed on the display device, and transmits the acquired provisional payment information to the payment service provider device. The code payment system described in claim 3, wherein the acquisition unit acquires the code information by reading the code image displayed on the user terminal at the store terminal, acquires the provisional payment information by accepting the first payment amount or information for identifying the first payment amount, and transmits the acquired provisional payment information to the payment service provider device. The acquisition unit acquires the code information by reading the code image that is fixedly displayed or printed on the user terminal, and acquires the first payment amount or the first payment amount.
The code payment system according to claim 3, wherein the provisional payment information is acquired by accepting information for specifying the payment amount, and the acquired provisional payment information is transmitted to the payment service provider device. The code payment system described in claim 6, wherein the code image is a code image common to multiple payment service providers. The code payment system described in any one of claims 4 to 7, wherein when the acquisition unit receives the quantity of the product or service as information for specifying the first payment amount, it calculates the first payment amount based on the quantity and the unit price of the product or service. The code payment system described in any one of claims 3 to 8 further includes a relay device between the store terminal and the payment service provider device that centrally accepts payments from each of multiple payment service providers that can be handled by the store terminal and relays processing corresponding to each of the corresponding payment service provider devices. The code payment system described in any one of claims 1 to 9, wherein the first payment amount is set to be greater than the second payment amount. A code payment system including a payment business device under the jurisdiction of a payment business, a store terminal provided in a store where a product or service is provided, and a user terminal used by a user who receives the product or service,
an acquisition unit in the store terminal that acquires provisional payment information in which a first payment amount indicating a provisional price for the product or service is associated with code information obtained by reading a code image associated with the payment service provider, and transmits the acquired provisional payment information to the payment service provider device;
a first payment unit in the payment service provider device that receives the provisional payment information, executes a payment process for a first payment amount indicated by the provisional payment information, and transmits a completion of the payment process to the store terminal;
a control unit that controls the store terminal to a state in which the product or the service can be provided when completion of the payment process is received from the payment service provider device;
a determination unit configured to, when detecting completion of provision of the product or the service in the store terminal, determine a second payment amount indicating a formal price for the product or the service and transmit the determined second payment amount to the payment service provider device;
the payment service provider device includes a second payment unit that executes a payment process for the difference between the first payment amount and the second payment amount received from the store terminal,
The acquisition unit acquires the code information by reading the code image displayed on the user terminal at the store terminal, acquires the provisional payment information by accepting the first payment amount or information for identifying the first payment amount, and transmits the acquired provisional payment information to the payment service provider device.
Code payment system. A code payment system including a payment business device under the jurisdiction of a payment business, a store terminal provided in a store where a product or service is provided, and a user terminal used by a user who receives the product or service,
an acquisition unit that acquires provisional payment information in which a first payment amount indicating provisional consideration for the product or service is associated with code information obtained by reading a code image associated with the payment service provider in the user terminal or the store terminal, and transmits the acquired provisional payment information to the payment service provider device;
a first payment unit in the payment service provider device that receives the provisional payment information, executes a payment process for a first payment amount indicated by the provisional payment information, and transmits a completion of the payment process to the store terminal;
a control unit that controls the store terminal to a state in which the product or the service can be provided when completion of the payment process is received from the payment service provider device;
a determination unit configured to, when detecting completion of provision of the product or the service in the store terminal, determine a second payment amount indicating a formal price for the product or the service and transmit the determined second payment amount to the payment service provider device;
the payment service provider device includes a second payment unit that executes a payment process for the difference between the first payment amount and the second payment amount received from the store terminal,
A relay device is further included between the store terminal and the payment service provider device, which centrally accepts payments from each of a plurality of payment service providers that can be handled by the store terminal and relays processing corresponding to each of the corresponding payment service provider devices.
Code payment system. acquiring provisional payment information in which a first payment amount indicating provisional payment for a product or service is associated with code information obtained by reading a code image associated with a payment service provider;
executes a payment process for the first payment amount indicated by the provisional payment information;
After the payment process for the first payment amount is completed, the product or service is provided.
When the completion of provision of the product or the service is detected, a second payment amount indicating a formal price for the product or the service is determined;
A code payment method in which a computer executes a process including executing a payment process for a difference between the first payment amount and the second payment amount,
the product or service is refueling at a gas station,
Controlling the refueling machine to a state where the product or the service can be provided is controlling the refueling machine to a state where refueling is possible.
Code payment method. acquiring provisional payment information in which a first payment amount indicating provisional payment for a product or service is associated with code information obtained by reading a code image associated with a payment service provider;
executes a payment process for the first payment amount indicated by the provisional payment information;
After the payment process for the first payment amount is completed, the product or service is provided.
A code payment program for causing a computer to execute a process including, when detecting completion of provision of the product or the service, determining a second payment amount indicating a formal price for the product or the service, and executing a payment process for the difference between the first payment amount and the second payment amount ,
the product or service is refueling at a gas station,
Controlling the refueling machine to a state where the product or the service can be provided is controlling the refueling machine to a state where refueling is possible.
Code payment program.