Transaction management method, store terminal, and transaction management system

Abstract

To provide a mechanism for suppressing transmission of radio waves when purchasing merchandise at a service station.SOLUTION: A user terminal according to one aspect of the present disclosure includes at least one processor. The at least one processor generates a two-dimensional code including configuration information used for purchasing merchandise at a service station, and displays the two-dimensional code for purchase of merchandise at the service station.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] One aspect of the present disclosure relates to a user terminal, a store terminal, a transaction management system, a transaction management method, and a transaction management program.

Background Art

[0002] A mechanism for assisting the purchase of products at a service station that sells energy sources is known. For example, Patent Document 1 discloses a technique for performing settlement of a fueling service by registering information necessary for a transaction in an IC tag in advance and reading the IC tag.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The technique described in Patent Document 1 uses wireless communication to read an IC tag. In a service station that handles flammable dangerous goods, it is desired to suppress the transmission of radio waves.

Means for Solving the Problems

[0005] A user terminal according to one aspect of the present disclosure includes at least one processor. The at least one processor generates a two-dimensional code including setting information used for purchasing products at a service station and displays the two-dimensional code for purchasing products at the service station.

[0006] A store terminal according to an aspect of the present disclosure is disposed at a service station and includes at least one processor. The at least one processor reads a two-dimensional code displayed on a user terminal, obtains setting information used for purchasing a product at the service station, and executes a process related to the purchase based on the setting information.

[0007] A transaction management system according to an aspect of the present disclosure includes a user terminal and a store terminal of a service station. The user terminal generates a two-dimensional code including setting information used for purchasing a product at the service station and displays the two-dimensional code for purchasing the product at the service station. The store terminal obtains the setting information by reading the two-dimensional code displayed on the user terminal and executes a process related to the purchase based on the setting information.

[0008] A transaction management method according to an aspect of the present disclosure is executed by a user terminal including at least one processor. The transaction management method includes a step of generating a two-dimensional code including setting information used for purchasing a product at the service station and a step of displaying the two-dimensional code for purchasing the product at the service station.

[0009] A transaction management program according to an aspect of the present disclosure causes a computer to execute a step of generating a two-dimensional code including setting information used for purchasing a product at the service station and a step of displaying the two-dimensional code for purchasing the product at the service station.

[0010] In such an aspect, the setting information used for purchasing a product at the service station is displayed as a two-dimensional code. Since radio waves are not required for reading the two-dimensional code, it is possible to suppress the transmission of radio waves when purchasing a product at the service station.

Advantages of the Invention

[0011] According to one aspect of the present disclosure, a mechanism for suppressing radio wave transmission during the purchase of goods at a service station can be provided.

Brief Description of the Drawings

[0012]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Modes for Carrying Out the Invention

[0013] Hereinafter, embodiments in the present disclosure will be described in detail with reference to the accompanying drawings. In the description of the drawings, the same or equivalent elements are denoted by the same reference numerals, and redundant descriptions are omitted.

[0014] [System Overview] A transaction management system according to an embodiment is a computer system that manages product transactions at a service station. A service station is a store that sells energy sources. An energy source is a resource used to power a power source, such as a vehicle, and is provided to power a vehicle. Examples of service stations include gas stations, hydrogen stations, and charging stations. Hereinafter, a service station will also be referred to simply as a "store." A product refers to any tangible or intangible object traded for or without payment, and is a concept that includes the provision of services. A "product transaction" refers to the exchange of a product between two parties. Examples of transactions include buying and selling, lending, borrowing, and bartering. Payment methods involved in a transaction are not limited. For example, payment methods may include cash, credit cards, debit cards, electronic money, or other deferred payment methods. A deferred payment method refers to a payment method in which a customer purchases a product and then deposits funds into a store. More specifically, the transaction management system according to this embodiment manages the purchase and sale of products using deferred payment cards. A deferred payment card refers to a card used for deferred payment, a payment method in which a customer pays for a product after purchasing it. An example of a deferred payment card is a credit card, but the type of deferred payment card is not limited to this. There are no limitations on how the deferred payment card is implemented; for example, it may be provided to the customer as a tangible card like a general credit card, or it may be provided as a virtual card represented by electronic data. A customer is someone who purchases a product. A customer can be referred to as a consumer or a user.

[0015] In this disclosure, the phrase "transmitting" data or information from a first computer to a second computer refers to the transmission of the data or information for ultimate delivery to the second computer. Note that this phrase also includes cases where another computer or communication device relays the data or information in the transmission.

[0016] [System Configuration] While referring to FIG. 1, the outline of the mechanism of the transaction management system 1 will be described. FIG. 1 is a diagram showing an example of the overall configuration including the transaction management system 1.

[0017] In the present embodiment, the customer 90 owns a user terminal 91. The user terminal 91 is a computer used by the customer 90. The type and configuration of the user terminal 91 are not limited. For example, the user terminal 91 may be a mobile terminal such as a smartphone, a tablet terminal, or a wearable terminal (e.g., a smartwatch). The user terminal 91 may be a component of the transaction management system 1 or may be a component not included in the transaction management system 1.

[0018] The user terminal 91 receives an input of setting information used for purchasing a product by an operation of the customer 90. The setting information includes at least one of a one-time token used for verification of the customer 90, customer identification information which is an identifier uniquely identifying the customer 90, product information indicating the product, and payment-related information used for payment. The one-time token is electronic data for verifying (authenticating) whether the customer 90 who purchases the product is the person himself / herself. The one-time token is generated, for example, for each purchase of a product and is used for verification only once. For example, the one-time token is generated by the application server 70. The payment-related information indicates at least one of a coupon and a point card. The coupon is electronic data used for discounting the price of a product. For example, the coupon includes information specifying the product to be discounted, the discount amount, the upper limit of use, and the expiration date, etc. The point card refers to a card for managing points given to the customer 90 corresponding to a product transaction (specifically, a purchase). The customer 90 can save the points and use the points as at least a part of the purchase price of the product. The user terminal 91 generates a two-dimensional code including the setting information. The two-dimensional code is a visible code expressed to have information in the horizontal and vertical directions.

[0019] The user terminal 91 displays a two-dimensional code for purchasing products in a store. For example, when the customer 90 purchases a product, the customer visits the store with the user terminal 91. The customer 90 operates the user terminal 91 to display the two-dimensional code, and holds the surface on which the two-dimensional code is displayed in front of the two-dimensional code reader 19. The two-dimensional code reader 19 is a device capable of reading information in the two-dimensional code. The two-dimensional code reader 19 is connected to the store terminal 10. The two-dimensional code reader 19 transmits the setting information read from the two-dimensional code to the store terminal 10. In response to this operation, various processes related to the purchase of products are executed on the store terminal 10.

[0020] The store terminal 10 is a computer placed in a store that handles products. The store terminal 10 executes processes related to the purchase of products. In one example, the processes related to the purchase of products may include the selection or setting of the product to be purchased, or may include the settlement process. The configuration of the store terminal 10 is not limited. For example, the store terminal 10 may be a general cash register, may be equipped with a POS (Point of Sale) function, or may be another form of device equipped with a cash register function or a POS function. Although only one store terminal 10 is shown in FIG. 1, of course, the transaction management system 1 can manage transactions at multiple store terminals 10 in multiple stores. Each store terminal 10 may be a component of the transaction management system 1, or may not be a component included in the transaction management system 1.

[0021] The transaction management system 1 includes a transaction management server 20, which is a computer for managing individual transactions, and an application server 70 for generating one-time tokens. The transaction management server 20 can communicate and connect with each of at least one store terminal 10. Also, the transaction management server 20 can communicate and connect with the application server 70, a database 30 for storing various types of information used in individual transactions, and a settlement management server 40 of a credit card company for managing settlements. The application server 70 can also communicate and connect with each of at least one user terminal 91. The store terminal 10 can also communicate and connect with a first sales management server 50 and a second sales management server 60 that comprehensively manage transactions at one or more stores. For example, the first sales management server 50 and the second sales management server 60 execute a closing process for finalizing transactions (sales). Each of the first sales management server 50 and the second sales management server 60 may be a component of the transaction management system 1 or may not be a component included in the transaction management system 1.

[0022] The configuration and type of the communication network used for communication connection between computers are not limited in any way and may be designed according to any policy. For example, the communication network may be constructed by the Internet, an intranet, or a combination thereof. Also, the communication network may be constructed by a wired network, a wireless network, or a combination thereof.

[0023] With reference to FIG. 1, an example of the processing flow in one transaction, that is, one purchase procedure, will be described. The user terminal 91 requests a one-time token query by transmitting customer identification information to the application server 70 (step S11). In response to the request, the application server 70 generates a one-time token and transmits the generated one-time token and customer identification information to the transaction management server 20 (step S12). The transaction management server 20 stores the correspondence between the one-time token and the customer identification information in the database 30. The application server 70 transmits a response including the generated one-time token to the user terminal 91 (step S13). A customer 90 who intends to purchase a product in a store operates the user terminal 91 to input setting information. The customer 90 may input the setting information in advance before entering the store, or may input the setting information in the store. The setting information includes, for example, a one-time token and product information. The user terminal 91 generates a two-dimensional code including the setting information.

[0024] In response to customer 90 displaying the two-dimensional code on user terminal 91 and holding the user terminal 91 over two-dimensional code reader 19, two-dimensional code reader 19 starts reading the two-dimensional code. Two-dimensional code reader 19 transmits the setting information read from the two-dimensional code to store terminal 10. Store terminal 10 transmits the setting information to transaction management server 20 (step S21). Transaction management server 20 reads from database 30 the formal card number of the postpaid card and the tokenized card number of the postpaid card based on the customer identification information associated with the one-time token indicated by the setting information. Also, transaction management server 20 requests a credit check from settlement management server 40 by transmitting the formal card number to settlement management server 40 (step S22). Settlement management server 40 executes a credit check in response to the request and transmits the result (credit result) to transaction management server 20 (step S23). Transaction management server 20 transmits a response including the credit result and the tokenized card number of the postpaid card to store terminal 10 (step S14). If the credit result indicates approval of the transaction, customer 90 can purchase goods at the store using the postpaid card.

[0025] In this embodiment, the transaction management system 1 uses two types of card numbers, i.e., a formal card number and a tokenized card number, as identifiers for uniquely identifying a postpaid card. The formal card number is a number set by the card company when issuing a postpaid card. The formal card number is notified to the customer 90 when the postpaid card is issued. Therefore, the customer 90 can know his / her formal card number. On the other hand, the tokenized card number is a card number obtained by replacing at least a part of the formal card number with another character string by tokenization. Tokenization refers to a process of replacing the original character string with another character string without having a mathematical relationship with the original character string. Tokenization can be realized, for example, by generating the other character string with a random number. The original character string (the character string before replacement) and the other character string (the character string after replacement) are associated one-to-one. Since there is no mathematical relationship between these two character strings, the original character string cannot be identified from the other character string by mathematical processing. In order to obtain the original character string, it is necessary to know the one-to-one correspondence relationship. Tokenization is different from encryption in that there is no mathematical relationship between the data before and after replacement. Encryption is a process of converting original data into encrypted data by an encryption algorithm and an encryption key. Therefore, there is a mathematical relationship between the original data and the encrypted data by the encryption algorithm and the encryption key.

[0026] The process flow of the closing process will be described with reference to FIG. 1. The example in FIG. 1 shows two types of closing processes corresponding to the existence of two types of sales management servers, i.e., the first sales management server 50 and the second sales management server 60. The store terminal 10 communicates and connects with one of the first sales management server 50 and the second sales management server 60.

[0027] In the first closing process, the first sales management server 50 is used. In this case, the store terminal 10 transmits transaction information indicating one or more transactions to the first sales management server 50 (step S31). The transaction information includes individual tokenized card numbers corresponding to individual transactions, but does not include individual formal card numbers corresponding to individual transactions. The first sales management server 50 transmits one or more tokenized card numbers to the transaction management server 20 (step S32). The transaction management server 20 refers to the database 30 and reads out the corresponding formal card number for each of the tokenized card numbers. Then, the transaction management server 20 transmits one or more formal card numbers to the first sales management server 50 (step S33). The first sales management server 50 transmits settlement information corresponding to the transaction information received from the store terminal 10 to the settlement management server 40. (step S34). The settlement information includes individual regular card numbers corresponding to individual transactions. Thereafter, the card company executes settlement by the postpaid card.

[0028] In the second closing process, the second sales management server 60 is used. In this case, the store terminal 10 transmits transaction information indicating one or more transactions to the second sales management server 60 (step S41). The transaction information includes individual tokenized card numbers corresponding to individual transactions, but does not include individual formal card numbers corresponding to individual transactions. The second sales management server 60 transmits settlement information corresponding to the transaction information to the transaction management server 20 (step S42). The transaction management server 20 refers to the database 30 and reads out the corresponding formal card number for each of the tokenized card numbers. Then, the transaction management server 20 replaces one or more tokenized card numbers in the settlement information with one or more formal card numbers, and transmits the processed settlement information to the settlement management server 40 (step S43). Thereafter, the card company executes settlement by the postpaid card.

[0029] The products to which the transaction management system 1 is applied are not limited in any way. For example, the transaction management system 1 may be constructed for transactions of energy sources (such as gasoline, light oil, hydrogen, electricity, etc.), other products, or services (such as gasoline refueling service for gasoline vehicles, charging service for electric vehicles, car washing, etc.) at service stations. That is, the product may be fuel oil, hydrogen, etc., and the store may be a gas station or a hydrogen station. In this case, the store terminal 10 may be a fuel dispenser or a hydrogen dispenser having a cash register function or a POS function.

[0030] While referring to FIG. 2, the functional elements related to the transaction management system 1 will be described. FIG. 2 is a diagram showing an example of the functional configuration of the transaction management system 1.

[0031] The user terminal 91 includes a display unit 92 and a generation unit 93 as functional elements. The display unit 92 is a functional element that displays a setting screen for presetting setting information used for purchasing products at a service station. The display unit 92 receives input of the setting information. The generation unit 93 is a functional element that generates a two-dimensional code including the setting information set on the setting screen. The generation unit 93 may generate a two-dimensional code including part or all of the setting information.

[0032] The store terminal 10 includes a setting information acquisition unit 11 and a purchase processing unit 12 as functional elements. The setting information acquisition unit 11 is a functional element that acquires various types of information sent from the user terminal 91. The purchase processing unit 12 is a functional element that executes processing related to product transactions (specifically, purchases).

[0033] The transaction management server 20 includes a credit request unit 21, a data acquisition unit 22, and a settlement information processing unit 23 as functional elements. The credit request unit 21 is a functional element that executes processing related to confirmation of credit for post-payment means. The data acquisition unit 22 is a functional element that accesses the database 30 to acquire various types of information. The settlement information processing unit 23 is a functional element that relays the transfer of settlement information from the second sales management server 60 to the settlement management server 40.

[0034] The database 30 is a device that stores various types of information used for individual transactions. For example, the database 30 may store data regarding product information, coupon information, and point card information for each customer 90. Further, the database 30 may store card data regarding a postpaid card. The database 30 may be a component of the transaction management system 1 or may be a component not included in the transaction management system 1. The database 30 in the present embodiment is a device separate from the transaction management server 20, but may be a component of the transaction management server 20.

[0035] Each record of the card data includes customer identification information and a pair of the official card number (card information) of the postpaid card and the tokenized card number. That is, this card data associates the customer identification information, the official card number, and the tokenized card number. The card data is generated based on the information of the credit card provided by the customer 90 and stored in the database 30. Each record of the card data may be encrypted to improve security. The details of the procedure for registering the card data are not limited, and the flow of the procedure may be arbitrarily determined. In any case, when the card data is generated and stored, the official card number of the postpaid card is tokenized to generate a tokenized card number. In the present embodiment, it is assumed that the card data corresponding to the customer identification information is stored in the database 30 (hereinafter referred to as "setting of the postpaid card").

[0036] The settlement management server 40 includes a credit inquiry unit 41 and a settlement unit 42 as functional elements. The credit inquiry unit 41 is a functional element that executes a credit inquiry in an individual transaction (settlement). The settlement unit 42 is a functional element that executes processing related to settlement.

[0037] The first sales management server 50 includes a token section 51 and a transaction / settlement management section 52 as functional elements. The token section 51 is a functional element that acquires an official card number from the transaction management server 20. The transaction / settlement management section 52 is a functional element that acquires transaction information from the store terminal 10 and transmits settlement information to the settlement management server 40.

[0038] The second sales management server 60 includes a transaction / settlement management section 61 as a functional element. The transaction / settlement management section 61 is a functional element that acquires transaction information from the store terminal 10 and transmits settlement information to the transaction management server 20.

[0039] The application server 70 includes a token generation section 71 as a functional element. The token generation section 71 is a functional element that acquires customer identification information from the user terminal 91 and generates a one-time token.

[0040] Figure 3 is a diagram showing the general hardware configuration of a computer 100 that can function as a server or terminal related to the transaction management system 1. For example, the computer 100 includes a processor 101, a main memory section 102, an auxiliary storage section 103, a communication control section 104, an input device 105, and an output device 106. The processor 101 executes an operating system and an application program. The main memory section 102 is composed of, for example, ROM and RAM. The auxiliary storage section 103 is composed of, for example, a hard disk or a flash memory and generally stores a larger amount of data than the main memory section 102. The auxiliary storage section 103 stores a program 110 for causing at least one computer to function as a server or a terminal. The communication control section 104 is composed of, for example, a network card or a wireless communication module. The input device 105 is composed of, for example, a keyboard, a mouse, a touch panel, etc. The output device 106 is composed of, for example, a monitor and a speaker.

[0041] Each functional element of each device is realized by causing the processor 101 or the main memory unit 102 to load the program 110 and execute the program. The program 110 includes code for realizing each functional element of the corresponding server or terminal. The processor 101 operates the communication control unit 104, the input device 105, or the output device 106 according to the program 110, and reads and writes data in the main memory unit 102 or the auxiliary storage unit 103. By this process, each functional element of the corresponding server or terminal is realized. Data or databases necessary for the process may be stored in the main memory unit 102 or the auxiliary storage unit 103.

[0042] Each server may be composed of one or more computers. When a plurality of computers are used, these computers are connected to each other via a communication network to logically constitute one server.

[0043] The program 110 may correspond to a transaction management program. The program 110 may be provided after being fixedly recorded on a tangible recording medium such as a CD-ROM, a DVD-ROM, or a semiconductor memory. Alternatively, the program 110 may be provided via a communication network as a data signal superimposed on a carrier wave.

[0044] FIG. 4 is a diagram showing an example of a setting screen. The setting screen is a screen for setting setting information. The setting screen may be provided to the user terminal 91 as, for example, a screen of an installed application or a screen of a web application. The user terminal 91 displays the setting screen and accepts input of setting information from the customer 90. The setting screen includes an ID setting 911, a product setting 912, and a payment-related setting 913.

[0045] Before or during the display of the setting screen, the user terminal 91 requests a one-time token query from the application server 70 and obtains a one-time token. For example, the one-time token query may be executed by background processing before the display of the setting screen. The user terminal 91 may automatically obtain the one-time token, or may obtain it triggered by the operation of the customer 90. Also, the user terminal 91 may or may not display the one-time token on the setting screen. The one-time token is used only once for verifying whether the customer 90 is the actual person. An available expiration period may be set for the one-time token.

[0046] The ID setting 911 is a screen element for setting customer identification information. For example, the transaction management system 1 may issue customer identification information to the customer 90 registered as a user and transmit the customer identification information to the user terminal 91. The user terminal 91 may automatically set the customer identification information in the ID setting 911.

[0047] The product setting 912 is a screen element for setting product information. The product information may be default values related to products that the customer 90 usually or frequently purchases. The product information includes, for example, the type of fuel and the fuel supply amount. Examples of the type of fuel include premium gasoline, regular gasoline, and light oil. Examples of the fuel supply amount include a quantity (e.g., 3L to 100L, etc.) or an amount (e.g., 300 yen to 14,999 yen, etc.). By combining the type of fuel and the fuel supply amount, the product information is set, for example, as "premium gasoline 30L".

[0048] The payment-related setting 913 is a screen element for setting payment-related information. For example, the payment-related setting 913 includes a coupon setting 913a for setting a coupon and a point card setting 913b for setting a point card. The coupon setting 913a may accept the selection of a coupon pre-distributed to the user terminal 91. The coupon may be distributed, for example, from the transaction management system 1 to the user terminal 91, or may be distributed from another server or the like to the user terminal 91. The point card setting 913b may accept, for example, the input of a point card number that uniquely identifies the point card. The payment-related setting 913 in this embodiment can set the coupon setting 913a and the point card setting 913b individually, but arbitrary restrictions may be imposed on the setting. For example, a restriction may be imposed that the setting of a post-payment card is required for the input to the point card setting 913b.

[0049] On the setting screen, at least one of a one-time token, customer identification information, product information, and payment-related information is set. For example, the customer 90 operates at least one of the ID setting 911, the product setting 912, and the payment-related setting 913 to input setting information. The one-time token is automatically acquired using the customer identification information. Regarding the setting information, there are various combinations of patterns corresponding to the presence or absence of each setting of the ID setting 911, the product setting 912, and the payment-related setting 913. The user terminal 91 processes at least one of the one-time token, customer identification information, product information, and payment-related information set on the setting screen as setting information, and generates a two-dimensional code 914 including the setting information.

[0050] The user terminal 91 may generate a two-dimensional code 914 each time the setting information is updated. For example, the user terminal 91 may generate the two-dimensional code 914 triggered by obtaining a one-time token. Alternatively, the user terminal 91 may display a confirmation screen or the like for determining the setting information, and generate the two-dimensional code 914 triggered by the customer's confirmation operation. The two-dimensional code 914 may be displayed on the setting screen or on other screens. The user terminal 91 may transmit part or all of the setting information to the transaction management server 20 via the application server 70. The transaction management server 20 may store the setting information in the database 30. The user terminal 91 may generate a two-dimensional code 914 including part or all of the setting information. In one example, when part of the setting information (for example, customer identification information) is stored in the database 30, the user terminal 91 may generate a two-dimensional code 914 that does not include the customer identification information. If part of the setting information is not included in the two-dimensional code 914, the setting information may be treated as a pattern in which the part is not set. When the post-payment card is set (the database 30 stores card data), the user terminal 91 may or may not display the official card number on the setting screen. Even when the post-payment card is set, the user terminal 91 generates a two-dimensional code 914 that does not include the official card number.

[0051] [System Operation] With reference to FIGS. 5 to 8, the operation of the transaction management system 1 will be described, and the transaction management method according to the present embodiment will be described. FIGS. 5 to 8 are all sequence diagrams showing an example of the operation of the transaction management system 1. More specifically, FIG. 5 shows the query process of the one-time token, FIG. 6 shows the process in one transaction (one purchase procedure), and FIGS. 7 and 8 are diagrams showing examples of the closing process. In FIGS. 5 to 8, the correspondence with the steps shown in FIG. 1 is also shown.

[0052] First, with reference to FIG. 5, the processing related to the one-time token will be described as processing flow S1. In step S101, the user terminal 91 requests a one-time token query by sending customer identification information to the application server 70. In one example, the user terminal 91 requests a one-time token query before or during the display of the setting screen as shown in FIG. 4.

[0053] In step S102, the token generation unit 71 of the application server 70 generates a one-time token in response to the request for a one-time token query. The one-time token is generated for each one-time token query.

[0054] In step S103, the application server 70 sends a notification including the generated one-time token and customer identification information to the transaction management server 20. The transaction management server 20 receives the notification.

[0055] In step S104, the transaction management server 20 stores the correspondence relationship between the one-time token and the customer identification information in the database 30. Thereby, the transaction management server 20 can derive the customer identification information based on the one-time token.

[0056] In step S105, the application server 70 sends a response including the generated one-time token to the user terminal 91. The user terminal 91 obtains the one-time token by receiving the response.

[0057] Next, with reference to FIG. 6, the processing in a single transaction will be described as processing flow S2. In step S201, the display unit 92 of the user terminal 91 displays a setting screen for presetting setting information used for purchasing goods at the service station. For example, the display unit 92 displays a setting screen as shown in FIG. 4 and receives input of setting information from the customer 90. The processing flow S1 shown in FIG. 5 may be executed before the processing of step S201 or during the processing of step S201.

[0058] In step S202, the generation unit 93 of the user terminal 91 generates a two-dimensional code 914 including the setting information set on the setting screen. The setting information includes at least one of a one-time token, customer identification information, product information, and payment-related information. For example, the generation unit 93 generates a two-dimensional code 914 including a one-time token, product information, and payment-related information and not including customer identification information. In this example, the setting information corresponds to a pattern in which a one-time token, product information, and payment-related information are set and customer identification information is not set.

[0059] In step S203, the user terminal 91 displays the two-dimensional code 914 for purchasing a product in the store. For example, the customer 90 operates the user terminal 91 to display the two-dimensional code 914, and holds the surface on which the two-dimensional code 914 is displayed in front of the two-dimensional code reader 19.

[0060] In step S204, the two-dimensional code reader 19 reads the two-dimensional code 914. For example, in response to the customer 90 holding the user terminal 91 in front of the two-dimensional code reader 19, the two-dimensional code reader 19 starts reading the two-dimensional code 914 displayed on the user terminal 91.

[0061] In step S205, the setting information acquisition unit 11 of the store terminal 10 acquires the setting information from the two-dimensional code 914 displayed on the user terminal 91. The two-dimensional code reader 19 reads the two-dimensional code 914 displayed on the user terminal 91 and transmits the read information to the store terminal 10. Thereby, the store terminal 10 acquires the setting information. The store terminal 10 holds the acquired setting information.

[0062] In step S206, the purchase processing unit 12 of the store terminal 10 transmits a credit inquiry to the transaction management server 20. The credit inquiry is a data signal for checking the credit status of the postpaid card. The credit inquiry includes, for example, the current date and time, a store ID which is an identifier for uniquely identifying the store where the store terminal 10 is located, a one-time token, and a provisional purchase amount. The provisional purchase amount is a purchase amount temporarily set to execute a credit inquiry for the postpaid card, and is not the purchase amount of the product. An extremely low amount is set as the provisional purchase amount. For example, the minimum value that can occur in a transaction (for example, 1 yen if it is Japanese yen) may be set as the provisional purchase amount. The transaction management server 20 receives the credit inquiry.

[0063] In step S207, the data acquisition unit 22 of the transaction management server 20 accesses the database 30 to obtain customer identification information corresponding to the one-time token indicated by the credit inquiry, and further obtains card data corresponding to the customer identification information. Since the customer identification information can be derived from the one-time token, the transaction management server 20 can determine that the customer 90 has read the two-dimensional code 914 by the two-dimensional code reader 19. That is, the transaction management server 20 can verify whether the customer 90 who purchases the product is the person himself / herself. Through this process, the data acquisition unit 22 obtains two types of card numbers corresponding to the customer identification information, that is, the formal card number and the tokenized card number.

[0064] In step S208, the credit request unit 21 of the transaction management server 20 transmits a credit inquiry request to the settlement management server 40. The credit inquiry request is a data signal for causing the settlement management server 40 to execute a credit inquiry for the postpaid card corresponding to the customer identification information. The credit inquiry request includes the current date and time, the formal card number obtained from the database 30, and the provisional purchase amount indicated by the credit inquiry. The settlement management server 40 receives the credit inquiry request.

[0065] In step S209, the credit inquiry unit 41 of the settlement management server 40 executes a credit inquiry for the postpaid card corresponding to the official card number indicated in the credit inquiry request, and transmits the result to the transaction management server 20 as the credit result. The credit inquiry unit 41 determines whether the postpaid card can be used in the transaction at the store by referring to data indicating the status of the postpaid card, the usage limit amount, etc. Since the provisional purchase amount is an extremely low amount (for example, the minimum value that can occur in the transaction), unless there are special circumstances such as the postpaid card being suspended or already exceeding the usage limit, the credit inquiry unit 41 approves the use of the postpaid card. The credit inquiry unit 41 transmits the result of the credit inquiry to the transaction management server 20 as the credit result. The transaction management server 20 receives the credit result.

[0066] In step S210, the credit request unit 21 of the transaction management server 20 transmits a response to the store terminal 10. The response is a data signal indicating an answer to the credit inquiry. The response includes the credit result and the tokenized card number. The store terminal 10 receives the response. This response does not include the official card number. That is, the credit request unit 21 transmits the tokenized card number to the store terminal 10 without transmitting the official card number to the store terminal 10. Since the store terminal 10 does not obtain the official card number, the store clerk does not recognize the official card number of the customer 90's postpaid card in the transaction.

[0067] In step S211, the purchase processing unit 12 of the store terminal 10 executes settings related to the purchase of goods. The purchase processing unit 12 executes the settings based on the goods information acquired from the user terminal 91. The specific method of setting related to the purchase of goods is not limited. For example, if the goods are fuel oil such as gasoline or light oil, the goods information may indicate default values related to refueling set in advance (for example, the type of fuel and the amount of refueling). The store terminal 10 displays the goods information (default value) on the monitor and asks the customer 90 whether to purchase the goods according to the information. The customer 90 can operate the store terminal 10 to determine the details of the goods to be purchased. For example, the customer 90 can operate a fuel dispenser, which is an example of the store terminal 10, to select refueling based on the default value, or request refueling after changing the type of fuel or the amount of refueling from the default value. As described above, the type of goods is not limited at all, and correspondingly, the content of the goods information is not limited either.

[0068] In step S212, the purchase processing unit 12 of the store terminal 10 executes a purchase process (settlement process) to finalize the transaction. The purchase processing unit 12 executes settlement by credit card only when the credit result indicates that the use of a credit card is possible. When a floor limit is set for purchases using a credit card, the purchase processing unit 12 accepts only transactions within a predetermined upper limit amount. The floor limit refers to an amount of a certain standard that requires a credit inquiry. When the purchase amount exceeds the floor limit, approval from the card company is required. When the purchase amount is below the floor limit, no credit inquiry is made. For example, if the floor limit is 15,000 yen, the purchase processing unit 12 accepts purchases and settlements by credit card only when the purchase amount is 15,000 yen or less. At this point, since a credit inquiry using an extremely low amount (for example, the minimum value that can occur in a transaction) has been completed, settlement subject to the floor limit is possible. For example, when the store terminal 10 is a fuel dispenser at a gas station, the fuel dispenser controls refueling so that the purchase amount does not exceed the floor limit.

[0069] When there is an available coupon, the purchase processing unit 12 may display the coupon on the monitor and inquire of the customer 90 whether at least a part of the coupon is to be used for purchasing goods. The purchase processing unit 12 may calculate the amount after discount from the purchase amount based on the selection of the customer 90 and the purchase amount. When the customer 90 uses a coupon for the purchase, the purchase processing unit 12 may accept the transaction if the purchase amount is less than or equal to the sum of the floor limit and the discount amount.

[0070] When there is a remaining point balance on the point card, the purchase processing unit 12 may display the remaining point balance on the monitor and inquire of the customer 90 whether at least a part of the points is to be used for purchasing goods. The purchase processing unit 12 may add or subtract the points on the point card based on the selection of the customer 90 and the purchase amount. When the customer 90 uses points for the purchase, the purchase processing unit 12 may accept the transaction if the purchase amount is less than or equal to the sum of the floor limit and the points used.

[0071] When the purchase processing is completed, the purchase processing unit 12 issues a receipt, generates a record of transaction information indicating a single transaction, and stores the record in a predetermined storage unit. One record of the transaction information indicates, for example, the transaction date and time, the store ID, the tokenized card number, and the product information. The product information indicates, for example, the name, unit price, quantity, and purchase amount (= unit price × quantity) for each of one or more products.

[0072] In the processing flow S2, the store terminal 10 receives a response including the tokenized card number and executes the settlement of the goods based on the response. That is, the store terminal 10 executes the settlement of the goods without obtaining the official card number.

[0073] In each individual store terminal 10, the processing flow S2 is executed for each individual transaction (settlement), whereby transaction information is accumulated in each individual store terminal 10. The accumulated transaction information is transmitted to the first sales management server 50 or the second sales management server 60 by the closing process.

[0074] Next, with reference to FIG. 7, the closing process via the first sales management server 50 will be described as processing flow S3. This closing process is generally a daily process, but the execution timing of processing flow S2 is not limited to this and may be executed at any timing.

[0075] In step S301, the purchase processing unit 12 of the store terminal 10 transmits transaction information indicating one or more transactions (more specifically, one or more transactions that occurred after the previous closing process) to the first sales management server 50. The first sales management server 50 receives the transaction information.

[0076] In step S302, the token unit 51 of the first sales management server 50 transmits a token request to the transaction management server 20. The token request is a data signal for obtaining the official card number of the postpaid card and includes one or more tokenized card numbers indicated by the transaction information. The transaction management server 20 receives the token request.

[0077] In step S303, the data acquisition unit 22 of the transaction management server 20 accesses the database 30 to obtain one or more official card numbers corresponding to one or more tokenized card numbers indicated by the token request. Since the official card number and the tokenized card number have a one-to-one correspondence, the data acquisition unit 22 can obtain the official card number for each of the one or more tokenized card numbers.

[0078] In step S304, the data acquisition unit 22 transmits a token response to the first sales management server 50. The token response is a data signal indicating a response to the token request and includes one or more pairs of the official card number and the tokenized card number. The first sales management server 50 receives the token response.

[0079] In step S305, the transaction / settlement management unit 52 of the first sales management server 50 transmits settlement information corresponding to the transaction information to the settlement management server 40. Specifically, the transaction / settlement management unit 52 generates settlement information by replacing each of the one or more tokenized card numbers indicated by the transaction information with a formal card number. This replacement is called detokenization. The transaction / settlement management unit 52 transmits this settlement information to the settlement management server 40. The settlement management server 40 receives the settlement information, and the settlement unit 42 executes settlement based on the settlement information. The transmission of the settlement information by the first sales management server 50 (step S305) may or may not correspond to the transmission of the transaction information by the store terminal 10 (step S301). For example, both the transmission of the transaction information and the transmission of the settlement information may be daily processes. Alternatively, the transmission of the transaction information may be a daily process, and the transmission of the settlement information may be a monthly process or a process every half month.

[0080] Next, with reference to FIG. 8, the closing process via the second sales management server 60 will be described as process flow S4. Similar to process flow S3, this closing process may be a daily process or may be executed at another arbitrary timing.

[0081] In step S401, the purchase processing unit 12 of the store terminal 10 transmits transaction information indicating one or more transactions (more specifically, one or more transactions that occurred after the previous closing process) to the second sales management server 60. The second sales management server 60 receives the transaction information.

[0082] In step S402, the transaction / settlement management unit 61 of the second sales management server 60 transmits its transaction information to the transaction management server 20 as settlement information. Different from the first sales management server 50, the second sales management server 60 (transaction / settlement management unit 61) does not execute a token. The transaction management server 20 receives the settlement information. The transmission of the settlement information by the second sales management server 60 (step S402) may or may not correspond to the transmission of the transaction information by the store terminal 10 (step S401). For example, both the transmission of the transaction information and the transmission of the settlement information may be daily processes. Alternatively, the transmission of the transaction information may be a daily process, and the transmission of the settlement information may be a monthly process or a process every half month.

[0083] In step S403, the data acquisition unit 22 and the settlement information processing unit 23 of the transaction management server 20 cooperate to replace the tokenized card number in the settlement information with the formal card number. The data acquisition unit 22 accesses the database 30 to acquire one or more formal card numbers corresponding to the one or more tokenized card numbers indicated by the settlement information. The settlement information processing unit 23 replaces each of the one or more tokenized card numbers indicated by the settlement information with the formal card number. That is, the settlement information processing unit 23 executes the token.

[0084] In step S404, the settlement information processing unit 23 transmits the processed settlement information to the settlement management server 40. The settlement management server 40 receives the settlement information, and the settlement unit 42 executes the settlement based on the settlement information.

[0085] FIG. 9 is a sequence diagram showing another example of the transaction process by the transaction management system 1 according to the embodiment. While referring to FIG. 9, the process in one transaction is taken as the process flow S5, and the differences from the process flow S2 will be mainly described. In the process flow S5, it is assumed that the database 30 stores the product information corresponding to the customer identification information. FIG. 9 shows an example in which the store terminal 10 inquires the transaction management server 20 about the product information.

[0086] In step S501, the display unit 92 of the user terminal 91 displays the setting screen. The process of step S501 is the same as the process of step S201. The processing flow S1 shown in FIG. 5 may be executed before the process of step S501 or during the process of step S501.

[0087] In step S502, the generation unit 93 of the user terminal 91 generates a two-dimensional code 914 including the setting information set on the setting screen. For example, the generation unit 93 generates a two-dimensional code 914 including a one-time token and payment-related information and not including customer identification information and product information. In this example, the setting information corresponds to a pattern in which a one-time token and payment-related information are set and customer identification information and product information are not set.

[0088] In step S503, the user terminal 91 displays the two-dimensional code 914 for purchasing a product in the store. The process of step S503 is the same as the process of step S203.

[0089] In step S504, the two-dimensional code reader 19 reads the two-dimensional code 914. The process of step S504 is the same as the process of step S204.

[0090] In step S505, the setting information acquisition unit 11 of the store terminal 10 acquires the setting information from the two-dimensional code 914 displayed on the user terminal 91. The process of step S505 is the same as the process of step S205.

[0091] In step S506, the purchase processing unit 12 of the store terminal 10 sends a credit inquiry and a product information inquiry to the transaction management server 20. The product information inquiry is a data signal for requesting acquisition of product information. The product information inquiry may be part of the credit inquiry or another data signal.

[0092] In step S507, the data acquisition unit 22 of the transaction management server 20 accesses the database 30 to acquire customer identification information corresponding to the one-time token indicated by the credit inquiry, and further acquires product information and card data corresponding to the customer identification information.

[0093] In step S508, the credit request unit 21 of the transaction management server 20 sends a credit inquiry request to the settlement management server 40. The process of step S508 is the same as the process of step S208.

[0094] In step S509, the credit inquiry unit 41 of the settlement management server 40 executes a credit inquiry for the postpaid card corresponding to the formal card number indicated by the credit inquiry request, and sends the result to the transaction management server 20 as the credit result. The process of step S509 is the same as the process of step S209.

[0095] In step S510, the credit request unit 21 of the transaction management server 20 sends a response to the store terminal 10. The response includes the credit result, product information, and the tokenized card number. The store terminal 10 receives the response.

[0096] In step S511, the purchase processing unit 12 of the store terminal 10 executes settings related to the purchase of the product. The purchase processing unit 12 executes the settings based on the product information acquired from the transaction management server 20. The process of step S511 is the same as the process of step S211 except for the different acquisition routes of the product information.

[0097] In step S512, the purchase processing unit 12 of the store terminal 10 executes a purchase process (settlement process) to finalize the transaction. The process of step S512 is the same as the process of step S212.

[0098] After the execution of the processing flow S5, the processing flow S3 shown in FIG. 7 or the processing flow S4 shown in FIG. 8 may be executed.

[0099] FIG. 10 is a sequence diagram showing another example of transaction processing by the transaction management system 1 according to the embodiment. While referring to FIG. 10, the processing in one transaction will be described mainly as processing flow S6, with the differences from processing flow S2 being mainly explained. In processing flow S6, the processing flow S1 shown in FIG. 5 is not executed. FIG. 10 shows an example where the customer 90 does not set a postpaid card (an example where the database 30 does not store card data).

[0100] In step S601, the display unit 92 of the user terminal 91 displays a setting screen. The processing in step S601 is the same as the processing in step S201.

[0101] In step S602, the generation unit 93 of the user terminal 91 generates a two-dimensional code 914 including the setting information set on the setting screen. For example, the generation unit 93 generates a two-dimensional code 914 that includes product information and does not include a one-time token, customer identification information, and payment-related information. In this example, the setting information corresponds to a pattern in which product information is set and a one-time token, customer identification information, and payment-related information are not set.

[0102] In step S603, the user terminal 91 displays the two-dimensional code 914 for purchasing a product in the store. The processing in step S603 is the same as the processing in step S203.

[0103] In step S604, the two-dimensional code reader 19 reads the two-dimensional code 914. The processing in step S604 is the same as the processing in step S204.

[0104] In step S605, the setting information acquisition unit 11 of the store terminal 10 acquires the setting information from the two-dimensional code 914 displayed on the user terminal 91. The processing in step S605 is the same as the processing in step S205.

[0105] In step S606, the purchase processing unit 12 of the store terminal 10 executes the settings related to the purchase of the product. The processing in step S606 is the same as the processing in step S211.

[0106] In step S607, the purchase processing unit 12 of the store terminal 10 executes a purchase process (settlement process) for finalizing the transaction. The purchase processing unit 12 may receive a selection of a payment means from the customer 90. For example, the purchase processing unit 12 may accept payment by cash, a post-payment means, or a pre-payment means (e.g., a prepaid card).

[0107] FIG. 11 is a sequence diagram showing another example of the transaction process by the transaction management system 1 according to the embodiment. With reference to FIG. 11, the process in a single transaction is taken as process flow S7, and the differences from process flow S2 will be mainly described. In process flow S7, it is assumed that the database 30 stores product information corresponding to customer identification information. Also, in process flow S7, the process flow S1 shown in FIG. 5 is not executed. FIG. 11 shows an example in which the post-payment card of the customer 90 is not set (the database 30 does not store card data), and the store terminal 10 inquires the transaction management server 20 about product information.

[0108] In step S701, the display unit 92 of the user terminal 91 displays a setting screen. The process of step S701 is the same as the process of step S201.

[0109] In step S702, the generation unit 93 of the user terminal 91 generates a two-dimensional code 914 including the setting information set on the setting screen. For example, the generation unit 93 generates a two-dimensional code 914 that includes customer identification information and does not include a one-time token, product information, and payment-related information. In this example, the setting information corresponds to a pattern in which customer identification information is set and a one-time token, product information, and payment-related information are not set.

[0110] In step S703, the user terminal 91 displays the two-dimensional code 914 for purchasing products in the store. The process of step S703 is the same as the process of step S203.

[0111] In step S704, the two-dimensional code reader 19 reads the two-dimensional code 914. The process of step S704 is the same as the process of step S204.

[0112] In step S705, the setting information acquisition unit 11 of the store terminal 10 acquires setting information from the two-dimensional code 914 displayed on the user terminal 91. The process of step S705 is the same as the process of step S205.

[0113] In step S706, the purchase processing unit 12 of the store terminal 10 sends an inquiry about product information to the transaction management server 20. The inquiry about product information includes customer identification information. The transaction management server 20 receives the inquiry about product information.

[0114] In step S707, the data acquisition unit 22 of the transaction management server 20 accesses the database 30 to acquire product information corresponding to the customer identification information indicated by the inquiry about product information.

[0115] In step S708, the credit request unit 21 of the transaction management server 20 sends a response to the store terminal 10. The response includes product information. The store terminal 10 receives the response.

[0116] In step S709, the purchase processing unit 12 of the store terminal 10 executes settings related to the purchase of products. The process of step S709 is the same as the process of step S511.

[0117] In step S710, the purchase processing unit 12 of the store terminal 10 executes a purchase process (settlement process) to finalize the transaction. The process of step S710 is the same as the process of step S607.

[0118] [Effect] As described above, the user terminal according to one aspect of the present disclosure includes at least one processor. The at least one processor generates a two-dimensional code including setting information used for purchasing products at the service station, and displays the two-dimensional code for purchasing products at the service station.

[0119] A store terminal according to an aspect of the present disclosure is disposed at a service station and includes at least one processor. The at least one processor reads a two-dimensional code displayed on a user terminal, obtains setting information used for purchasing a product at the service station, and executes a process related to the purchase based on the setting information.

[0120] A transaction management system according to an aspect of the present disclosure includes a user terminal and a store terminal of a service station. The user terminal generates a two-dimensional code including setting information used for purchasing a product at the service station and displays the two-dimensional code for purchasing the product at the service station. The store terminal obtains the setting information by reading the two-dimensional code displayed on the user terminal and executes a process related to the purchase based on the setting information.

[0121] A transaction management method according to an aspect of the present disclosure is executed by a user terminal including at least one processor. The transaction management method includes a step of generating a two-dimensional code including setting information used for purchasing a product at the service station and a step of displaying the two-dimensional code for purchasing the product at the service station.

[0122] A transaction management program according to an aspect of the present disclosure causes a computer to execute a step of generating a two-dimensional code including setting information used for purchasing a product at the service station and a step of displaying the two-dimensional code for purchasing the product at the service station.

[0123] In such an aspect, the setting information used for purchasing a product at the service station is displayed as a two-dimensional code. Since radio waves are not required to read the two-dimensional code, it is possible to suppress the transmission of radio waves when purchasing a product at the service station.

[0124] In a user terminal related to another aspect, at least one processor displays a setting screen for presetting setting information, and generates a two-dimensional code including the setting information set on the setting screen. In this case, outside the service station, the setting information can be set, so that a flexible mechanism can be provided for purchasing products at the service station.

[0125] In a user terminal related to another aspect, at least one processor may obtain a one-time token used for customer verification at the service station and generate a two-dimensional code including the one-time token. In this case, since it is verified whether the customer who purchases the product is the person himself / herself, the security of the product transaction is improved.

[0126] In a store terminal related to another aspect, the setting information may include product information indicating a product. At least one processor may execute processing related to purchase based on the product information. In this case, since the specification of product information in the store becomes simple or unnecessary, the convenience of product transactions is improved.

[0127] In a store terminal related to another aspect, the setting information may include customer identification information that uniquely identifies a customer at the service station. At least one processor may obtain product information indicating a product from the transaction management server based on the customer identification information, and execute processing related to purchase based on the product information. In this case, the preset product information is managed by the transaction management server, and based on the product information, the store terminal executes processing related to purchase. Thereby, since the specification of product information in the store becomes simple or unnecessary, the convenience of product transactions is improved.

[0128] [Modification Example] As described in detail above based on the embodiments of the present disclosure. However, the present disclosure is not limited to the above embodiments. The present disclosure can be variously modified without departing from the gist thereof.

[0129] In the embodiment, it has been described that the user terminal 91 displays a setting screen and accepts input of setting information. However, the setting information may be copied to the user terminal 91 from different media. For example, the customer 90 may own an NFC tag (hereinafter referred to as a "separate tag") that is separate from the user terminal 91. The separate tag may store in advance the setting information desired by the customer 90. The database 30 may store the correspondence between the identifier of the separate tag and the setting information. Further, the transaction management system 1 may provide the user terminal 91 with a transfer screen for copying the setting information. For example, the customer 90 may input the identifier of the separate tag he / she owns into the transfer screen. The transaction management system 1 may read out from the database 30 the setting information corresponding to the input identifier of the separate tag and transmit the setting information to the user terminal 91. The user terminal 91 may store the received setting information in a memory area. In this way, the setting information may be copied from the separate tag to the user terminal 91. Alternatively, a copying device (for example, a reader / writer) for reading the setting information from the separate tag and writing the setting information to the user terminal 91 may be installed in the store. By operating the copying device, the setting information may be copied from the separate tag to the user terminal 91.

[0130] In the embodiment, it has been described that the user terminal 91 displays a setting screen and accepts input of product information. However, the product information may be stored (registered) in advance by the application server 70. For example, the user terminal 91 may transmit a query for product information to the application server 70 together with a request for one-time token query. The application server 70 may transmit the product information to the user terminal 91 together with a response to the request for one-time token query. The user terminal 91 may generate a two-dimensional code including the one-time token and the product information acquired from the application server 70.

[0131] In another modification example, the information of the point card may be managed by an external server (hereinafter referred to as the "point management server") that manages points. The store terminal 10 may send the point card number acquired by reading the two-dimensional code to the external point management server. The point management server may determine whether the point card number is valid, specify the remaining point balance corresponding to the point card number, and send the remaining point balance to the store terminal 10. When the point card number is valid, the customer 90 can acquire points corresponding to the purchase of goods or use at least a part of the remaining point balance as at least a part of the purchase price. Further, the transaction management server 20 may send the point card number to the external point management server and acquire the remaining point balance.

[0132] In the present disclosure, the expression "at least one processor executes the first process, executes the second process,... executes the nth process." or a corresponding expression indicates a concept including a case where the execution subject (i.e., the processor) of the n processes from the first process to the nth process changes midway. That is, this expression indicates a concept including both a case where all of the n processes are executed by the same processor and a case where the processor changes in an arbitrary manner in the n processes.

[0133] The processing procedures of the method executed by at least one processor are not limited to the examples in the embodiments. For example, a part of the above-described steps (processes) may be omitted, or each step may be executed in a different order. Further, any two or more of the above-described steps may be combined, or a part of the steps may be modified or deleted. Alternatively, other steps may be executed in addition to the above-described steps.

Explanation of Signs

[0134] 1... Transaction management system, 10... Store terminal, 11... Setting information acquisition unit, 12... Purchase processing unit, 19... Two-dimensional code reader, 20... Transaction management server, 21... Credit request unit, 22... Data acquisition unit, 23... Settlement information processing unit, 30... Database, 40... Settlement management server, 41... Credit inquiry unit, 42... Settlement unit, 50... First sales management server, 51... Token unit, 52... Transaction / settlement management unit, 60... Second sales management server, 61... Transaction / settlement management unit, 70... Application server, 71... Token generation unit, 90... Customer, 91... User terminal, 92... Display unit, 93... Generation unit, 911... ID setting, 912... Product setting, 913... Payment-related setting, 914... Two-dimensional code.

Claims

1. A user terminal comprising at least one processor, wherein the at least one processor generates a two-dimensional code including setting information used for purchasing a product at a service station, and displays the two-dimensional code for purchasing the product at the service station.

2. The at least one processor displays a setting screen for presetting the setting information, and generates the two-dimensional code including the setting information set on the setting screen. The user terminal according to claim 1.

3. The at least one processor obtains a one-time token used for customer verification at the service station, and generates the two-dimensional code including the one-time token. The user terminal according to claim 1 or 2.

4. A store terminal disposed at a service station, comprising at least one processor, wherein the at least one processor obtains setting information used for purchasing a product at the service station by reading a two-dimensional code displayed on a user terminal, and executes processing related to the purchase based on the setting information.

5. The setting information includes product information indicating the product, and the at least one processor executes processing related to the purchase based on the product information. The store terminal according to claim 4.

6. The setting information includes customer identification information for uniquely identifying a customer at the service station, and the at least one processor obtains product information indicating the product from a transaction management server based on the customer identification information, and executes processing related to the purchase based on the product information. The store terminal according to claim 4.

7. A transaction management system comprising a user terminal and a store terminal of a service station, wherein the user terminal generates a two-dimensional code including setting information used for purchasing a product at the service station, and displays the two-dimensional code for purchasing the product at the service station, [[ID= ​ ​ ​ ​ ​ ​ ​ A transaction management method executed by a user terminal including at least one processor, comprising: generating a two-dimensional code including setting information used for purchasing a product at a service station; displaying the two-dimensional code for purchasing the product at the service station; A transaction management method including the above steps.

9. generating a two-dimensional code including setting information used for purchasing a product at a service station; displaying the two-dimensional code for purchasing the product at the service station; A transaction management program that causes a computer to execute the above steps.

Images