JP7354162B2 - Programs, information processing methods, terminals - Google Patents

Description

The present disclosure relates to a program, an information processing method, and a terminal.

2. Description of the Related Art Recently, services that enable the management of electronic money (electronic money) of terminals or users of terminals, payments using electronic money, etc., have become widespread using applications that can be executed on terminals such as smartphones. For example, Patent Document 1 discloses a technique for settling the purchase price of a product. However, regarding payments using electronic money, there is room for improvement, for example, in terms of user interface (UI).

Japanese Patent Application Publication No. 2002-176671

According to the first aspect of the present invention, a program executed by a terminal that executes payment-related processing based on first information for making a payment using a code image transmits a plurality of pieces of first information to a communication unit of the terminal. receiving the plurality of pieces of first information from the server via the terminal, controlling the control unit of the terminal to store the received plurality of first information in the storage unit of the terminal, and displaying a first code image based on the first information on the terminal. The terminal displays the first code image in the display area and causes the control unit to perform payment-related processing based on the display of the first code image in the display area. If the first information that can be used for payment is not stored in the storage unit other than the first information based on the first code image, the first information that can be used for payment in addition to the first code image displayed in the display area Displaying a first indication regarding the absence of the code image and the first code image in the display area is performed by the terminal.
According to a second aspect of the present invention, an information processing method for a terminal that executes payment-related processing based on first information for making a payment using a code image includes: the plurality of pieces of first information received from the server; controlling the control unit of the terminal to store the received plurality of first information in the storage unit of the terminal; and displaying the first code image based on the first information in the display area of the terminal. and performing processing related to payment by the control unit based on the display of the first code image in the display area, the first code image displayed in the display area among the plurality of first information. If the first information that can be used for payment other than the first information based on is not stored in the storage unit, there is no first code image that can be used for payment other than the first code image displayed in the display area. The method includes displaying a first display related to the above and a first code image in a display area.
According to the third aspect of the present invention, a terminal that executes payment-related processing based on first information for making a payment using a code image includes a communication unit that receives a plurality of pieces of first information from a server, and a communication unit that receives a plurality of pieces of first information from a server; The controller includes a control unit that controls storing a plurality of pieces of first information in a storage unit of the terminal, and a display unit that displays a first code image based on the first information, and the control unit displays a display unit for displaying the first code image. Based on the display, processing related to payment is executed, and the display unit displays first information that can be used for payment, in addition to the first information based on the first code image displayed on the display unit, among the plurality of first information. is not stored in the storage section, a first display indicating that there is no first code image available for payment other than the first code image displayed on the display section and the first code image are displayed.
According to the fourth aspect of the present invention, a terminal that executes payment-related processing based on first information for payment using a code image reads a program from a memory that stores the program, and executes processing based on the program. The processor includes: receiving a plurality of pieces of first information from the server via a communication unit of the terminal; storing the received pieces of first information in a storage unit of the terminal; displaying a first code image based on the information in the display area of the terminal; and performing processing related to payment based on the display of the first code image in the display area; , if the first information that can be used for payment is not stored in the storage unit other than the first information based on the first code image displayed in the display area, in addition to the first code image displayed in the display area, A first display regarding the fact that there is no first code image available for payment and a first code image are displayed in the display area.

FIG. 1 is a diagram illustrating an example of a configuration of a communication system in one aspect of an embodiment. FIG. 1 is a diagram illustrating an example of a system configuration of a store POS system in one aspect of the embodiment. 5 is a flowchart illustrating an example of the flow of processing executed by various devices in one aspect of the embodiment. The figure which shows an example of the display screen of the terminal in one aspect of embodiment. The figure which shows an example of the display screen of the terminal in one aspect of embodiment. 5 is a flowchart illustrating an example of the flow of processing executed by various devices in one aspect of the embodiment. FIG. 3 is a diagram illustrating an example of functions realized by the control unit of the server according to the first embodiment. FIG. 3 is a diagram showing an example of information stored in a storage unit of the server according to the first embodiment. FIG. 3 is a diagram showing an example of user registration data according to the first embodiment. The figure which shows an example of store registration data based on 1st Example. The figure which shows an example of the payment management database based on 1st Example. The figure which shows an example of the code management database based on 1st Example. FIG. 3 is a diagram illustrating an example of functions realized by the control unit of the terminal according to the first embodiment. FIG. 3 is a diagram showing an example of information stored in a storage unit of the terminal according to the first embodiment. The figure which shows an example of the code stock data for 1st terminal display based on 1st Example. The figure which shows an example of the code stock data for a 2nd terminal display based on 1st Example. The figure which shows an example of the data for payment based on 1st Example. The figure which shows an example of the display screen of the terminal based on 1st Example. The figure which shows an example of the display screen of the terminal based on 1st Example. 5 is a flowchart illustrating an example of the flow of a first code display process according to the first embodiment. The figure which shows an example of the display screen of the terminal based on the 1st modification. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a second embodiment. 7 is a flowchart showing an example of the flow of a second code display process according to the second embodiment. 10 is a flowchart illustrating an example of the flow of a third code display process according to a second modification. 7 is a flowchart illustrating an example of the flow of processing executed by various devices according to a second modification. The figure which shows an example of the display screen of the terminal based on a 2nd modification. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a third embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a third embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a third embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a third embodiment. 12 is a flowchart showing an example of the flow of the first terminal-side code replenishment process and the first server-side code replenishment process according to the fourth embodiment. The figure which shows an example of the display screen of the terminal based on 4th Example. The figure which shows an example of the display screen of the terminal based on 4th Example. The figure which shows an example of the display screen of the terminal based on 4th Example. The figure which shows an example of the display screen of the terminal based on 4th Example. The figure which shows an example of the display screen of the terminal based on 4th Example. The figure which shows an example of the display screen of the terminal based on 4th Example. The figure which shows an example of the display screen of the terminal based on 4th Example. The figure which shows an example of the display screen of the terminal based on 4th Example. The figure which shows an example of the display screen of the terminal based on 4th Example. 12 is a flowchart showing an example of the flow of second terminal-side code replenishment processing according to the fifth embodiment. 12 is a flowchart showing an example of the flow of second terminal-side code replenishment processing according to the fifth embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a fifth embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a fifth embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a fifth embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a fifth embodiment. FIG. 7 is a diagram showing an example of a display screen of a terminal according to a fifth embodiment.

<Compliance with legal matters>
Please note that the disclosures described herein are subject to compliance with the host country's legal requirements necessary for the implementation of the disclosures, such as confidentiality of communications.

Embodiments for implementing the information processing method and the like according to the present disclosure will be described with reference to the drawings.

[System configuration]
FIG. 1 is a diagram illustrating an example of the configuration of a communication system 1 according to an embodiment of the present disclosure.
As disclosed in FIG. 1, in the communication system 1, a server 10, terminals 20 (terminal 20A, terminal 20B, terminal 20C, . . . ), and a store POS system 40 are connected via a network 30. .

The server 10 provides the terminals 20 owned by users with a service that enables the transmission and reception of content, including messages, between the terminals 20 via the network 30. Further, the server 10 provides a service (hereinafter referred to as "payment service") that communicates with the terminal 20 to realize electronic payment (an example of payment, not limited to payment). Note that the number of terminals 20 connected to the network 30 is not limited.

The network 30 plays a role of connecting one or more terminals 20, one or more servers 10, and one or more store POS systems 40. That is, the network 30 refers to a communication network that provides a connection path so that the various devices described above can transmit and receive data after being connected.

One or more portions of network 30 may or may not be a wired network or a wireless network. Network 30 may include, by way of example and not limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (wireless LAN: WLAN), wide area network (WAN), wireless WAN (WWAN), metropolitan area network (MAN), part of the Internet, public switched telephone network (Public Switched Telephone Network (PSTN), mobile phone network, ISDN (integrated service digital networks), wireless LAN, LTE (long term evolution), CDMA (code division multiple access), Bluetooth (registered trademark), satellite communication, etc., or a combination of two or more of these. Network 30 may include one or more networks 30.

The terminals 20 (terminal 20A, terminal 20B, terminal 20C, ...) (not limited to, but an example of a terminal or information processing device) may be any information processing terminal that can realize the functions described in each embodiment. It may be a terminal. Terminal 20 may include, by way of example and not limitation, a smartphone, a mobile phone (feature phone), a computer (desktop, laptop, tablet, etc., by way of example and not limitation), a media computer platform (by way of example and not limitation, cable, satellite set, etc.). top boxes, digital video recorders), handheld computing devices (by way of example and not limitation, personal digital assistants, e-mail clients, etc.), wearables (such as glasses-like devices, watch-like devices, etc.), or other types of computers. , or communication platform. Further, the terminal 20 may be expressed as an information processing terminal.

Since the configurations of terminal 20A, terminal 20B, and terminal 20C are basically the same, in the following description, only terminal 20 will be described. Furthermore, if necessary, the terminal used by user X will be expressed as terminal 20X, and the user information in a predetermined service associated with user X or terminal 20X will be expressed as user information X. Note that the user information is user information associated with an account used by the user in a predetermined service. User information includes, by way of example and not limitation, the user's name, the user's icon image, the user's age, the user's gender, the user's address, and the user's hobbies, entered by the user or provided by a given service. It includes information associated with the user such as preferences and user identifiers, and may be any one or a combination of these, or may not be the same.

The server 10 (not limited to, but an example of a server, an information processing device, or an information management device) has a function of providing a predetermined service to the terminal 20. The server 10 may be any information processing device that can implement the functions described in each embodiment. Server 10 may include, by way of example and not limitation, a server device, a computer (such as, by way of example and not limitation, a desktop, laptop, tablet, etc.), a media computer platform (by way of example and not limitation, a cable, satellite set-top box, digital video recorder, etc.). ), handheld computing devices (by way of example and not limitation, PDAs, email clients, etc.), or other types of computers or communication platforms. Further, the server 10 may be expressed as an information processing device. If there is no need to distinguish between the server 10 and the terminal 20, the server 10 and the terminal 20 may or may not be each expressed as an information processing device.

In the embodiment described below, the server 10 will be described as having a function of providing a payment service using a payment application.

The store POS system 40 is a POS system that is installed and used in a store affiliated with a business operator that operates the server 10.
This store POS system 40 includes, by way of example and not limitation, a store code reader device 50, a code register 60, and a store server 70.

[Hardware (HW) configuration of each device]
The HW configuration of each device included in the communication system 1 will be explained.

(1) HW configuration of terminal FIG. 1 shows an example of the HW configuration of the terminal 20.
The terminal 20 includes a control unit 21 (CPU: central processing unit), a storage unit 28, a communication I/F 22 (interface), an input/output unit 23, a display unit 24, a microphone 25, a speaker 26, a camera 27, It includes a clock section 29A and a position calculation information detection section 29B. Each component of the HW of terminal 20 is interconnected via bus B, by way of example and not limitation. Note that it is not essential that the HW configuration of the terminal 20 includes all the components. By way of example and not limitation, terminal 20 may or may not be configured to remove an individual component or components, such as microphone 25, camera 27, etc.

The communication I/F 22 transmits and receives various data via the network 30. Communication may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 22 has a function of communicating with various devices such as the server 10 via the network 30. The communication I/F 22 transmits various data to various devices such as the server 10 according to instructions from the control unit 21. Furthermore, the communication I/F 22 receives various data transmitted from various devices such as the server 10 and transmits the received data to the control unit 21 . Moreover, the communication I/F 22 may be simply expressed as a communication section. In addition, when the communication I/F 22 is composed of a physically structured circuit, it may be expressed as a communication circuit.

The input/output unit 23 includes a device for inputting various operations to the terminal 20 and a device for outputting processing results processed by the terminal 20. In the input/output section 23, the input section and the output section may be integrated, or may be separated into an input section and an output section, or may not be.

The input unit is realized by any one or a combination of all types of devices that can receive input from the user and transmit information related to the input to the control unit 21. The input unit includes, by way of example and not limitation, a touch panel, a touch display, hardware keys such as a keyboard, a pointing device such as a mouse, a camera (operation input via moving images), and a microphone (operation input via voice).

The output unit is realized by any one of all types of devices capable of outputting the processing results processed by the control unit 21 or a combination thereof. Output units include, by way of example and not limitation, a touch panel, a touch display, a speaker (audio output), a lens (including, by way of non-limiting example, three dimensions output or hologram output), a printer, and the like.

The display unit 24 is realized by any one or a combination of all types of devices capable of displaying data according to the display data written in the frame buffer. The display unit 24 includes, by way of example and not limitation, a touch panel, a touch display, a monitor (by way of example and not limitation, a liquid crystal display or an OELD (organic electroluminescence display)), a head mounted display (HDM), a projection mapping, and a hologram. , devices capable of displaying images, text information, etc. in air (which may or may not be a vacuum). Note that these display units 24 may or may not be capable of displaying display data in 3D.

When the input/output unit 23 is a touch panel, the input/output unit 23 and the display unit 24 may have substantially the same size and shape and may be disposed facing each other.

The clock unit 29A is a built-in clock of the terminal 20, and outputs time information (timekeeping information). The clock section 29A includes, by way of example and not limitation, a clock using a crystal oscillator. The clock section 29A can also be expressed as a clock section or a time information detection section, by way of example and not limitation.

Note that the clock unit 29A may or may not have a clock to which the NITZ (Network Identity and Time Zone) standard or the like is applied.

The position calculation information detection unit 29B has a function of detecting (measuring) information (hereinafter referred to as “position calculation information”) necessary for the control unit 21 to calculate (measure) the position of its own terminal 20. Department. The position calculation information detection unit 29B can also be expressed as a position calculation sensor unit, by way of example and not limitation.
Note that the position calculation information detection unit 29B is not essential and may be excluded from the configuration requirements of the terminal 20.

The position calculation information detection unit 29B includes, by way of example and not limitation, a satellite positioning sensor (satellite positioning sensor) which is a sensor or unit for calculating the position of the terminal 20 using a satellite positioning system such as GPS (Global Positioning System). unit), and an inertial measurement sensor (IMU (Inertial Measurement Unit)) that is a sensor or unit for calculating the position of the terminal 20 using an inertial navigation system.

The satellite positioning unit includes, by way of example and not limitation, an RF receiving circuit that converts an RF (Radio Frequency) signal including a positioning satellite signal transmitted from a positioning satellite received by an antenna (not shown) into a digital signal; A positioning satellite signal is captured by performing correlation calculation processing on the digital signal output from the RF receiving circuit, and information such as satellite orbit data and time data extracted from the positioning satellite signal is used as position calculation information. It has a baseband processing circuit etc. for output.

The inertial measurement unit has an inertial sensor that is a sensor that detects information necessary for calculating the position of the terminal 20 by inertial navigation calculation. Inertial sensors include, by way of example and not limitation, a 3-axis acceleration sensor and a 3-axis gyro sensor, and use the acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor as position calculation information. Output.

The control unit 21 has a physically structured circuit for executing functions realized by codes or instructions included in a program, and includes, by way of example and not limitation, a data processing device built into hardware. This is realized by Therefore, the control unit 21 may or may not be expressed as a control circuit.

The control unit 21 may include, by way of example and not limitation, a central processing unit (CPU), a microprocessor, a processor core, a multiprocessor, an ASIC (application-specific integrated circuit), and a FPGA (field programmable). gate array).

The storage unit 28 has a function of storing various programs and various data necessary for the terminal 20 to operate. The storage unit 28 includes various storage media such as, by way of example and not limitation, an HDD (hard disk drive), an SSD (solid state drive), a flash memory, a RAM (random access memory), and a ROM (read only memory). Furthermore, the storage unit 28 may or may not be expressed as a memory.

In the terminal 20, the program P is stored in the storage unit 28, and by executing the program P, the control unit 21 executes processing as each unit included in the control unit 21. That is, the program P stored in the storage unit 28 causes the terminal 20 to realize each function executed by the control unit 21. Furthermore, this program P may or may not be expressed as a program module.

The microphone 25 is used for inputting audio data. The speaker 26 is used to output audio data. The camera 27 is used to obtain moving image data.

(2) HW configuration of server FIG. 1 shows an example of the HW configuration of the server 10.
The server 10 includes a control section 11 (CPU), a storage section 15, a communication I/F 14 (interface), an input/output section 12, a display 13, and a clock section 19. The HW components of server 10 are interconnected via bus B, by way of example and not limitation. Note that the HW of the server 10 does not necessarily include all the components as the HW configuration of the server 10 . By way of example and not limitation, the HW of the server 10 may or may not be configured to remove the display 13.

The control unit 11 has a physically structured circuit for executing functions realized by codes or instructions included in a program, and includes, by way of example and not limitation, a data processing device built into hardware. This is realized by

The control unit 11 is typically a central processing unit (CPU), and may or may not be a microprocessor, processor core, multiprocessor, ASIC, or FPGA. In the present disclosure, the control unit 11 is not limited to these.

The storage unit 15 has a function of storing various programs and various data necessary for the operation of the server 10. The storage unit 15 is realized by various storage media such as HDD, SSD, and flash memory. However, in the present disclosure, the storage unit 15 is not limited to these. Furthermore, the storage unit 15 may or may not be expressed as a memory.

The communication I/F 14 transmits and receives various data via the network 30. Communication may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 14 has a function of communicating with various devices such as the terminal 20 via the network 30. The communication I/F 14 transmits various data to various devices such as the terminal 20 according to instructions from the control unit 11. Further, the communication I/F 14 receives various data transmitted from various devices such as the terminal 20 and transmits the received data to the control unit 11. Moreover, the communication I/F 14 may be simply expressed as a communication section. Furthermore, when the communication I/F 14 is composed of a physically structured circuit, it may be expressed as a communication circuit.

The input/output unit 12 is realized by a device that inputs various operations to the server 10. The input/output unit 12 is realized by any one or a combination of all types of devices that can receive input from a user and transmit information related to the input to the control unit 11. The input/output unit 12 is typically implemented using hardware keys such as a keyboard or a pointing device such as a mouse. Note that the input/output unit 12 may or may not include, by way of example and not limitation, a touch panel, a camera (operation input via moving images), and a microphone (operation input via voice). However, in the present disclosure, the input/output unit 12 is not limited to these.

The display 13 is typically realized by a monitor (for example, but not limited to, a liquid crystal display or an organic electroluminescence display (OELD)). Note that the display 13 may or may not be a head mounted display (HDM). Note that these displays 13 may or may not be capable of displaying display data in 3D. In the present disclosure, the display 13 is not limited to these.

The clock unit 19 is a built-in clock of the server 10, and outputs time information (timekeeping information). The clock unit 19 includes, by way of example and not limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, and the like. The clock section 19 can also be expressed as a timekeeping section or a time information detection section, by way of example and not limitation.

(3) System configuration of store POS FIG. 2 shows an example of the system configuration of the store POS system 40.
The store POS system 40 is a POS system that is introduced and used in a store affiliated with a business operator that operates the server 10, and includes, by way of example and not limitation, a store code reader device 50, a code register 60, and a store. server 70.

The store code reader device 50 is communicatively connected to a code register 60 and a store server 70 via a POS communication I/F 57 (for example, but not limited to, a wired communication I/F or a wireless communication I/F in the store), and the code register 60 At the time of checkout, the terminal display code image displayed on the display section 24 of the terminal 20 is read. Then, based on reading the terminal display code image, payment request information is transmitted to the server 10 via the communication I/F 54, and after the payment is made in the server 10, information regarding the payment result (for example, the store payment completion notification) is received from the server 10 via the communication I/F 54.

The store code reader device 50 includes, by way of example and not limitation, a control section 51, an input/output section 52, a display section 53, a communication I/F 54, a storage section 55, a sound output section 56, and a POS communication I/F section. F57, a code reader 58, and a clock section 59.

The code reader 58 is a code reader for reading a two-dimensional code, and in this specification, the two-dimensional code (for example, QR code (registered trademark)) displayed on the display unit 24 of the terminal 20 and presented by the user of the terminal 20 )) includes a two-dimensional code reader (for example, a QR code reader) for reading a terminal display code.

By way of example and not limitation, the code register 60 is communicatively connected to the store code reader device 50 and the store server 70 via the POS communication I/F 57, and based on the store payment completion notification received by the store code reader device 50 from the server 10. , a receipt is printed with information on the total amount of sold products and the electronic currency balance of the user of the terminal 20. Further, by way of example and not limitation, a display may be configured that is provided integrally with the code register 60 or separately from the code register 60, and has a display surface facing the customer side. The code register 60 is a cash register configured to be compatible with a payment application, and can also be called a stationary terminal compatible with a payment application.

The store server 70 may, by way of example and not limitation, store information regarding its own store, information regarding products sold at its own store, information regarding services provided at its own store, and information on sales of products and provision of services at its own store. Manage various information such as information related to sales. The store server 70 is configured to be able to communicate with the store code reader device 50 and the code register 60 via the POS communication I/F 57, and is also configured to be able to communicate with external devices such as the server 10 via the network 30.

Note that the store server 70 does not necessarily need to be configured to be able to communicate directly with the store code reader device 50, and may be configured to be able to communicate with the store code reader device 50 via the code register 60. For example, the store payment completion notification received by the store code reader device 50 from the server 10 may be sent to the code register 60, and then sent from the code register 60 to the store server 70.

(4) Others The server 10 stores the program P in the storage unit 15, and by executing the program P, the control unit 11 executes processing as each unit included in the control unit 11. That is, the program P stored in the storage unit 15 causes the server 10 to realize each function executed by the control unit 11. This program P may or may not be expressed as a program module.
The same applies to other devices.

In each embodiment of the present disclosure, description will be made assuming that the CPU of the terminal 20 and/or the server 10 executes the program P.
The same applies to other devices.

Note that the control unit 21 of the terminal 20 and/or the control unit 11 of the server 10 may be formed not only in a CPU having a control circuit but also in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)), etc. Each process may or may not be realized by a dedicated logic circuit (hardware) or a dedicated circuit. Further, these circuits may be realized by one or more integrated circuits, and the plurality of processes shown in each embodiment may or may not be realized by one integrated circuit. Furthermore, LSIs are sometimes called VLSIs, super LSIs, ultra LSIs, etc. depending on the degree of integration. Therefore, the control unit 21 may or may not be expressed as a control circuit.
The same applies to other devices.

Further, the program P (by way of example, but not limitation, a software program, computer program, or program module) of each embodiment of the present disclosure may be provided in a state stored in a computer-readable storage medium, or It doesn't have to be done. The storage medium can store the program P in a "non-temporary tangible medium". Further, the program P may or may not be for realizing a part of the functions of each embodiment of the present disclosure. Furthermore, it may or may not be a so-called difference file (difference program) that can realize the functions of each embodiment of the present disclosure in combination with a program P already recorded on a storage medium.

The storage medium may include one or more semiconductor-based or other integrated circuits (ICs), such as, by way of example and not limitation, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), a hard・Disk drive (HDD), hybrid hard drive (HHD), optical disk, optical disk drive (ODD), magneto-optical disk, magneto-optical drive, floppy diskette, floppy disk drive (FDD), magnetic tape, solid state (SSD), a RAM drive, a secure digital card, or any other suitable storage medium, or a suitable combination of two or more thereof. Storage media may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate. Note that the storage medium is not limited to these examples, and may be any device or medium as long as it can store the program P. Further, the storage medium may or may not be expressed as a memory.

The server 10 and/or the terminal 20 can realize the functions of the plurality of functional units shown in each embodiment by reading the program P stored in the storage medium and executing the read program P.
The same applies to other devices.

Further, the program P of the present disclosure may or may not be provided to the server 10 and/or the terminal 20 via any transmission medium (communication network, broadcast waves, etc.) that can transmit the program. . By way of example and not limitation, the server 10 and/or the terminal 20 realize the functions of the plurality of functional units shown in each embodiment by executing a program P downloaded via the Internet or the like.
The same applies to other devices.

Furthermore, each embodiment of the present disclosure may be implemented in the form of a data signal in which the program P is embodied by electronic transmission.
At least part of the processing in the server 10 and/or the terminal 20 may or may not be realized by cloud computing configured by one or more computers.
At least part of the processing in the terminal 20 may or may not be performed by the server 10. In this case, at least part of the processing of each functional unit of the control unit 21 of the terminal 20 may or may not be performed by the server 10.
At least part of the processing in the server 10 may or may not be performed by the terminal 20. In this case, at least part of the processing of each functional unit of the control unit 11 of the server 10 may or may not be performed by the terminal 20.
Unless explicitly stated, the configuration of the determination in the embodiments of the present disclosure is not essential, and a predetermined process may be performed when the determination condition is met, or a predetermined process is performed when the determination condition is not met. You may or may not.

Note that the program of this disclosure uses, by way of example and not limitation, a scripting language such as ActionScript or JavaScript (registered trademark), a compiler language such as Objective-C or Java (registered trademark), or a markup language such as HTML5. Implemented.

Further, in this specification, the expression "by communication I/F" is used as appropriate. This indicates, by way of example and not limitation, that the device transmits and receives various information and data via the communication I/F (via the communication unit) based on the control of the control unit (processor, etc.) .

Further, in this specification, the term "deadline" is explained as indicating a certain period of time. However, instead of the term "deadline", the term "period" may be used.
Further, the term "deadline" may be used to mean the time or date and time (fixed time or fixed date and time) at which a period ends.

<First example>
In recent years, applications (application software) related to network services include applications for electronic payment using electronic money (payment application), applications for remittance of electronic money (remittance application), and some functions of these applications. Alternatively, payment applications that integrate all functions are becoming popular, and it has become possible for users of the terminal 20 to use these applications to receive various services related to electronic money.

The embodiments described below are, by way of example and not limitation, in which a user of the terminal 20 makes a payment using a payment application stored and executed on the terminal 20. Specifically, we propose a method for making payments in both online and offline states.

Hereinafter, a business that provides payment services using a payment application will be referred to as a "payment service business". Note that the payment service provider may or may not be expressed as a provider of a payment application or a provider of the server 10.

Further, in the following description, it is assumed that the server 10 is operated and managed by a payment service provider. Further, in the following, the name of the payment application will be appropriately referred to as "Payment App" for illustration and explanation.

Further, the payment application may be provided by the server 10 as a standalone application that does not have the functions of a so-called messaging service (MS), or may be provided by the server 10 as a composite application that has the functions of an MS. It may be provided by Further, the messaging service may or may not include an instant messaging service (IMS) that enables the transmission and reception of content such as simple messages between the terminals 20.

Further, the payment application may be provided by the server 10 as a standalone application that does not have a so-called social networking service (SNS) function, or as a composite application that has a SNS function. It may also be provided by the server 10.

Note that MS (including IMS) can also be considered as one form (one form) of SNS. Therefore, MS and SNS may or may not be distinguished.

In addition, stores that are affiliated with payment service providers are referred to as "affiliated stores (affiliated stores)," and are indicated in Figure 1 as "affiliated stores S1," "affiliated stores S2," etc. .

In addition, "electronic money" refers to electronic money that is distinguished from physical money and is owned by the terminal 20 managed by the payment application or the user of the terminal 20. ' means electronic payment using this electronic money.

Note that electronic money may or may not be expressed as "electronic money" or "digital currency (digital money)."
Further, legal currency or virtual currency may be used as "electronic money" or "digital currency".
Furthermore, "electronic money (electronic money)" and "digital currency (digital money)" may include cryptocurrencies (cryptoassets).
Further, virtual currency may include physical money such as coupons.

<Payment method>
(1) Online Payment First, as one aspect, an online payment method will be described with reference to a flowchart.

In the following, "online" indicates that the terminal 20 can communicate with the server 10, and "online state" indicates this online state. Furthermore, "online payment" indicates that payment is performed by the server 10 in an online state.

Note that, in the following, communication between the terminal 20 and the server 10 is performed using a frequency band different from that of wireless LAN communication, which is realized through a base station installed by a communication company (communication carrier), by way of example and not limitation. It is assumed that this is realized by the first communication method used. The first communication method includes, by way of example and not limitation, packet communication (so-called mobile data communication at terminal 20).

Further, as the communication method, a second communication method different from the first communication method may or may not be used. The second communication method includes, by way of example and not limitation, wireless LAN (eg, WiFi (registered trademark)).

Furthermore, the "online state" may or may not be defined as the terminal 20 and the server 10 being able to communicate using at least one of the first communication method and the second communication method. It's okay.

FIG. 3-1 is a flowchart showing an example of the flow of processing executed by each device in this case. Examples of processing executed by the control unit 21 of the terminal 20, processing executed by the control unit 51 of the store code reader device 50, and processing executed by the control unit 11 of the server 10 are shown in order from the left.

Each step in each process is indicated by a combination of uppercase letters and numbers, and the term "step" is omitted in this specification.
Further, the flowchart described below is merely an example of the processing in this embodiment, and in the flowchart described below, some steps may not be executed, or additional steps may be inserted.
The same applies to other flowcharts in this specification.

First, the control unit 21 transmits code generation request information for requesting generation of a terminal display code to the server 10 using the communication I/F 22 (via the communication I/F 22) (A110).

In the following, by way of example and not limitation, "code information" refers to information stored in a code image through encoding, etc., and information stored in a code image (hereinafter referred to as "original information"). This will be explained as a concept that includes "information") and "code image" in which original information is stored. In other words, "code information" includes "original information" and "code image."
"Original information" may be expressed as "encoded information" or "stored information," or may not be expressed as such.

Furthermore, hereinafter, by way of example and not limitation, the term "code" is assumed to have substantially the same meaning as "code information."

However, these definitions are just examples and are not limited to these.
For example, the term "code information" may or may not be used to mean "original information."
Furthermore, for example, the term "code" may or may not be used to mean "code image."

In this embodiment, as an example of the above source information, a number that is uniquely generated by the server 10 for each terminal 20 that sends the code generation request information or for each user of the terminal 20, and that has a predetermined number of digits. A "payment number" which is a random number is exemplified. The payment number is information associated with the terminal 20 or the user of the terminal 20, and can also be said to be information used for payment by the server 10.

Hereinafter, the payment code generated by the server 10 based on the code generation request information will be referred to as a "terminal display code", and the code image of this terminal display code will be referred to as a "terminal display code image".

Although details will be described later, the above-mentioned payment number is stored in the terminal display code image.
The terminal display code image and the payment number are examples of "first information" for making payment using the code image, and are transmitted from the server 10.

In the following, a case will be exemplified in which information for requesting the server 10 to generate the above code image for terminal display is code generation request information. That is, in this process, by way of example and not limitation, the terminal 20 requests the server 10 to generate a code image for terminal display, and in A110, code generation request information for requesting generation of the code image for terminal display is sent to the server. Send to 10.

In addition, in this specification, a "terminal display code" is explained as a code used for payment with the payment type "terminal code display".
In the payment type "terminal code display", when the user of the terminal 20 makes a payment at a store, etc., the user of the terminal 20 uses the payment application stored in the terminal 20 to display the terminal display code image displayed on the terminal 20 at the store. Present the code to the clerk at the cash register 60. Then, payment is realized by having this terminal display code image read by a store code reader device 50 or the like.
Since the terminal display code is a code (code image) presented by the user of the terminal 20 to a clerk at a store or the like, it can also be expressed as a "presentation code" or "user presentation code."

The code generation request information transmitted in A110 can include, by way of example and not limitation, identification information for identifying the terminal 20 or the user of the terminal 20. For example, terminal identification information for identifying one's own terminal 20 (for example, terminal ID), user identification information for identifying the user of one's own terminal 20 (for example, user ID), account information for a payment application (for example, application ID) This includes information such as:

When receiving code generation request information from the terminal 20 through the communication I/F 14 (C110), the control unit 11 performs a terminal display code generation process (C120).

Specifically, as an example and not a limitation, a method (algorithm) that generates a random number of a predetermined number of digits (for example, about 10 to 12 digits) is used to generate a random number of a predetermined number of digits. will be generated as a payment number. Then, by way of example and not limitation, a code image for terminal display is generated that includes at least the payment number as original information. More specifically, at least the payment number is encoded (encoded) and graphically (imaged) to generate a code image for terminal display represented by an image of a two-dimensional code (for example, a QR code). Further, the identification information of the terminal 20 or the user of the terminal 20 included in the received code generation request information and the generated payment number are stored in the storage unit 15 in association with each other.

Next, the control unit 11 transmits the generated terminal display code (in this example, a terminal display code image) to the terminal 20 via the communication I/F 14 (C130). The terminal 20 receives a terminal display code (in this example, a terminal display code image) from the server 10 via the communication I/F 22 (A130). In this case, the control unit 21 causes the display unit 24 to display the received terminal display code image, by way of example and not limitation.

Thereafter, when the terminal display code image displayed on the display unit 24 is presented to a store clerk or the like by the user of the terminal 20, the control unit 51 controls the terminal display code image displayed on the display unit 24 of the terminal 20. Control is performed to cause the code reader 58 to read the image (B150).

Thereafter, the control unit 51 accesses the server 10 through the communication I/F 54 using an application interface (API) associated with the payment application provided (distributed) by the payment service provider, and at least reads the data. The payment number obtained by decoding from the terminal display code image, identification information for identifying the store or store code reader device 50 (hereinafter referred to as "store identification information"), and the scheduled payment amount (hereinafter referred to as "store identification information"). (referred to as "scheduled payment amount") is transmitted to the server 10 via the communication I/F 54 (B160).

When the communication I/F 14 receives payment request information from the store code reader device 50 (C160), the control unit 11 performs payment processing (C170). Specifically, it is determined whether the payment number included in the received payment request information is stored in the storage unit 15 in association with the identification information of the terminal 20 or the user of the terminal 20. If the payment number is stored, it is determined that "payment is possible", and the electronic money balance of the terminal 20 or the user of the terminal 20 identified from the identification information stored in association with the payment number (payment application application Payment is made by subtracting the scheduled payment amount from the electronic money balance associated with the ID (hereinafter simply referred to as the "balance").

Thereafter, the control unit 11 transmits a store payment completion notification (hereinafter referred to as "store payment completion notification") to the store code reader device 50 via the communication I/F 14 (C180). The store payment completion notification includes, by way of example and not limitation, the fact that the payment has been completed (successful), the date and time of payment (payment date and time), and store payment information such as the payment amount (payment amount). .

Further, the control unit 11 transmits a terminal payment completion notification (hereinafter referred to as "terminal payment completion notification") to the terminal 20 via the communication I/F 14 (C190). The terminal payment completion notification includes, by way of example and not limitation, the fact that the payment was completed (successful), the date and time of the payment (payment date and time), the store identification information of the store where the payment was made (payment store identification information), and the payment amount ( payment information for the terminal, such as payment amount). Then, the control unit 11 ends the process.

Here, it is assumed that when the payment by the server 10 is successful, the server 10 sends a payment completion notification for the store and a payment completion notification for the terminal. It may not be possible to do so. In this case, a notification to the effect that the payment could not be made (for example, a payment error notification or a payment NG notification) may be sent to the store code reader device 50 and the terminal 20.
The same applies to other processes.

When the communication I/F 54 receives the store payment completion notification from the server 10 (B180), the control unit 51 ends the process.

Further, when receiving a terminal payment completion notification from the server 10 through the communication I/F 22, the control unit 21 updates the balance stored in the terminal 20 as payment application data based on the received terminal payment completion notification. do. Further, the control unit 21 causes the display unit 24 to display the payment result (A190). Then, the control unit 21 ends the process.

FIG. 3-2 is a diagram showing an example of the top screen displayed by the payment application executed on the terminal 20.
This top screen is a display screen that is displayed when the payment application is started, and the name of the payment application, "Payment APP", is displayed at the top of the screen. The balance (here, "3000 yen") is displayed in the frame below, and next to it, a charge button for charging (adding) electronic money is displayed. Further, below that, a plurality of function icons corresponding to various functions of the payment application are displayed.

Among these function icons, the icon labeled "Code" is, by way of example and not limitation, a "code icon" for displaying a code display screen on the display unit 24. When this code icon is touched by the user of the terminal 20, by way of example and not limitation, code generation request information is transmitted from the terminal 20 to the server 10, and the server 10 generates a terminal display code. The generated terminal display code is then transmitted from the server 10 to the terminal 20, and the code display screen shown in FIG. 3-3 is displayed on the display section 24 of the terminal 20.

FIG. 3-3 is a diagram showing an example of a code display screen.
On this code display screen, the word "code" is displayed at the top of the screen, and below it, the payment method, the points the user owns, and whether or not to use those points for payment are set. Points tab and are displayed.

Below that, as the code image of the terminal display code obtained from the server 10, there is a one-dimensional terminal display code image represented by a barcode, and a two-dimensional terminal display code represented by a QR code. Images QC0 are displayed in different areas within the display screen. Furthermore, by way of example and not limitation, a 12-digit payment number is displayed below the one-dimensional terminal display code image.

Further, in this example, the terminal display code displayed on the code display screen has a deadline for displaying the code (hereinafter referred to as "code display deadline").

The code display deadline is, by way of example and not limitation, a period during which the terminal display code is displayed on the terminal 20. The code display time limit may be, by way of example and not limitation, "the period from the time (date and time) when the terminal display code is displayed (display started) on the terminal until the code display time has elapsed." Although the code display time can be changed as appropriate, it can be set to "5 minutes" by way of example and not limitation.

Note that the code display deadline is not defined as the period during which the terminal display code is displayed on the terminal 20, but is defined as the time (date and time) when the period during which the terminal display code is displayed on the terminal 20 ends (expires). You may or may not do so.

Under the two-dimensional terminal display code image QC0, the remaining time of the code display deadline is displayed in a countdown format along with an update mark and update characters. This remaining time is displayed based on information measured by the clock section 29A of the terminal 20.
When the remaining time reaches "0", the code display screen is closed and the terminal display code is hidden. If the user of the terminal 20 subsequently wishes to make a payment, it is necessary to reacquire the terminal display code from the server 10.

The user of the terminal 20 can make a payment by presenting the code display screen shown in FIG. 3-3 to the store clerk at the code register 60 and having the store code reader device 50 read the terminal display code image within the code display period. I do. In this case, the store code reader device 50 accesses the server 10 through the communication I/F 54 using the above-mentioned API, etc., and transmits information necessary for payment to the server 10. As a result, the server 10 performs payment processing.

Up to this point, we have illustrated the processing for realizing online payment. In this process, the terminal display code generated by the server 10 and sent to the terminal 20 is immediately used for payment, by way of example and not limitation.

However, some users may not wish to use the terminal display code received from the server 10 immediately to make a payment, but to use it later to make a payment.

Furthermore, in order to apply the above processing, it is necessary that the terminal 20 and the server 10 be in a communicable state (online state). Of course, it is also necessary that the store code reader device 50 and the server 10 be in a communicable state.

However, when making a payment in a place where the signal strength is poor, such as underground, or when making a payment in a situation where the line is congested, such as at an event venue, the communication amount of the terminal 20 for a certain period (for example, one month) is limited. It is assumed that in cases where communication restrictions or communication speed limits are imposed due to exceedance, etc., the terminal 20 and the server 10 become unable to communicate (or have communication difficulties), making it difficult to make payments. be done.

Therefore, below, we will exemplify a method for realizing payment even in these cases.
Note that although the payment method described below is similarly applicable to both the online state and the offline state, it will be described here as a method for realizing payment in the offline state.

(2) Offline Payment An offline payment method as one aspect of the disclosed method will be described with reference to a flowchart.
In the following, "offline" indicates that the terminal 20 cannot communicate with the server 10, and "offline state" indicates this offline state. Furthermore, "offline payment" indicates that payment is performed by the server 10 in an offline state. Furthermore, it is assumed that the store code reader device 50 can communicate with the server 10.

FIG. 3-4 is a flowchart showing an example of the flow of processing executed by each device in this case. The diagram can be viewed in the same way as the flowchart described above.

The flowchart in FIG. 3-4 is a rewrite of the flowchart in FIG. 3-1 into offline specifications. The flowchart in Figure 3-1 includes, by way of example and not limitation, processing steps in an online state (for example, A240), processing steps in an offline state (for example, A250, B250, B280), and a case when returning from an offline state to an online state. The processing steps (for example, A290, C290) are different.

After A130, the control unit 21 stores the received terminal display code (in this example, a terminal display code image) in the storage unit 28 (A240).

Here, "stock" means storing the received terminal display code in the storage unit 28 so that it can be used later.
Note that in this specification, "stock" is sometimes simply expressed as "memory." Furthermore, storing the terminal display code is sometimes expressed as "storing the terminal display code in the terminal display code stock data."

In this process, in order to enable offline payment, the terminal display code (terminal display code image in this example) acquired from the server 10 in the online state is stocked (stored) in the storage unit 28 of the terminal 20. . When payment needs to be made offline, the stocked terminal display code can be used to make the payment without having to communicate with the server 10.

I will explain in detail. Assume that after A240, the state becomes offline.
Here, by way of example and not limitation, the terminal 20 detects that it is in an offline state using one of the following methods.

(A) While the payment application is being executed on the terminal 20, a connection confirmation request is sent from the server 10 to the terminal 20 at regular timing or at a specific timing. A connection response including information (for example, application ID) is sent to the server 10. In this case, when the control unit 21 of the terminal 20 no longer receives a connection confirmation request from the server 10, it determines that the terminal 20 is in an offline state.

(B) While the payment application is being executed on the terminal 20, a connection notification containing identification information (for example, application ID) is sent from the terminal 20 to the server 10 at regular timing or at a specific timing, and the server 10 A connection confirmation is sent to the terminal 20 in response to the connection notification. In the offline state, a connection notification cannot be sent from the terminal 20 to the server 10. Therefore, by way of example and not limitation, the control unit 21 of the terminal 20 determines that the terminal is in an offline state when detecting the occurrence of a connection notification transmission error.

Note that, by way of example and not limitation, the terminal 20 may use a library or application that obtains the network connection status to obtain information regarding the communication status of its own terminal 20 and determine whether or not it has become offline. You may or may not do so.

In the offline state, by way of example and not limitation, when the user of the terminal 20 performs a code display operation, the control unit 21 performs code display processing (A250). Specifically, the terminal display code image stocked in A240 is displayed on the display section 24. Then, when the displayed code image for terminal display is presented to a store clerk or the like by the user of the terminal 20, the control unit 51 transfers the code image for terminal display displayed on the display unit 24 of the terminal 20 to the code reader. 58 is controlled to read (B250). The control unit 51 then moves the process to B160.

After B160, when a store payment completion notification is received from the server 10 via the communication I/F 54 (B280), the store clerk, etc. receives a notification that the offline payment has been completed (successful) based on the received store payment completion notification. The user of the terminal 20 is notified orally.

After C180, the control unit 11 transmits a terminal payment completion notification to the terminal 20 (C290). However, in the offline state, the terminal 20 cannot receive the terminal payment completion notification. When the terminal 20 returns to the online state, the terminal 20 receives the terminal payment completion notification sent from the server 10. Then, when the terminal payment completion notification is received from the server 10 through the communication I/F 22, the control unit 21 causes the display unit 24 to display the payment result based on the received terminal payment completion notification (A290).

The process described above is an example of a process for performing offline payment.

Note that the code generation request information may be information requesting generation of one terminal display code, but may also be information requesting generation of multiple (two or more) terminal display codes. Specifically, as an example and not a limitation, instead of adding terminal display codes one by one, the number of codes that the terminal 20 requests to be generated at one time on the terminal 20 side or the server 10 side. (the number of codes that the server 10 generates at one time) is set. Then, the user of the terminal 20 may acquire this upper limit number of terminal display codes at once with one operation. In this case, multiple terminal display codes are generated by the server 10, the generated multiple terminal display codes are transmitted to the terminal 20, and the received multiple terminal display codes are stored in the terminal 20. do it.

The above process can be applied in the online state as well. In other words,
(1) When making a payment using the terminal display code later in the online state; (2) When making an offline payment; as described above, it is generated and transmitted by the server 10 in the online state. The terminal display code obtained is stored in the terminal 20. Then, payment is made using the terminal display code stored on the terminal 20.

However, some users may forget that they have stored the terminal display code in the terminal 20.
In addition, for example, when storing multiple terminal display codes in the terminal 20, the user can check the number of terminal display codes that have already been used for payment and the number of terminal display codes that have not yet been used for payment. It can be difficult to understand.

<Functional configuration>
(1) Functional Configuration of Server FIG. 4-1 is a diagram showing an example of functions realized by the control unit 11 of the server 10 in this embodiment.

In the following, a case will be described in which the user of the terminal 20 uses a payment application stored in the terminal 20 to make a payment using the above-mentioned payment type "terminal code display", by way of example and not limitation.

The server 10 has a payment management processing section 111 as a function realized by the control section 11.

The payment management processing unit 111 manages various information and data related to the payment application executed on the terminal 20, and manages electronic money of the terminal 20 or the user of the terminal 20, according to the payment management processing program 151 stored in the storage unit 15. It has the function of executing payment management processing to manage payments made by

In this embodiment, the payment management processing unit 111 executes, for example, the process shown in FIGS. 3-4 as the payment management process, according to the payment management processing program 151 stored in the storage unit 15.

By way of example and not limitation, the payment management processing unit 111 includes a terminal display code generation processing unit 1111 that generates a terminal display code through terminal display code generation processing, and a payment processing unit 1113 that executes payment through payment processing. Included as a functional part.

The terminal display code generation processing unit 1111 generates a terminal display code image represented by a two-dimensional code, by way of example and not limitation. A two-dimensional code is a display type code that has information in the horizontal and vertical directions, and includes a matrix code in which small squares are arranged vertically and horizontally (hereinafter referred to as "matrix code"), and a one-dimensional code. There are stacked codes (hereinafter referred to as "stacked codes") in which a plurality of original codes (barcodes, as an example, not limited) are stacked one above the other.

In this embodiment, in order to simplify the explanation, a QR code (registered trademark), which is an example of a widely used matrix code, will be described as an example of a terminal display code.

Note that, unlike the present embodiment, as a matrix code other than the QR code, a code such as an SP code, Vericode, maxi code, CP code, or Chameleon code may or may not be used. Furthermore, instead of the matrix code, various stack codes may or may not be used.

In addition, the terminal display code generation processing unit 1111 generates a one-dimensional code (by way of example and not limitation, a barcode) in addition to a two-dimensional code (by way of example and not limitation, a QR code). You may or may not do so. This is because some stores may not be able to read two-dimensional codes, but may be able to read one-dimensional codes.

The payment processing unit 1113 has, by way of example and not limitation, a function of performing payment processing based on information transmitted from the store POS system 40 or information transmitted from the terminal 20.

FIG. 4-2 is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this embodiment.
The storage unit 15 stores, by way of example and not limitation, a payment management processing program 151 that is read out by the control unit 11 and executed as payment management processing.

Further, the storage unit 15 stores user registration data 153, store registration data 155, payment management database 157, and code management database 159 as data, by way of example and not limitation.

The user registration data 153 is registration data of the terminal 20 that uses the payment service and the user of the terminal 20, and an example of the data structure is shown in FIG. 4-3.
The user registration data 153 stores, by way of example and not limitation, a user name, a terminal telephone number, a terminal e-mail address, an application ID, an authentication password, and other registration information in association with each other.

The user name is the name of the user of the terminal 20 who uses the payment service, and stores the name that the user of the terminal 20 registers when using the payment service.

The terminal phone number is the phone number of the terminal 20 of the user with this user name, and stores the phone number of the terminal 20 that the user of the terminal 20 registers when using the payment application.
The terminal email address is the email address of the terminal 20 of the user with this user name, and stores the email address of the terminal 20 that the user of the terminal 20 registers when using the payment application.
The terminal telephone number and the terminal email address are examples of identification information for identifying the terminal 20 (hereinafter referred to as "terminal identification information").

The application ID is an account (account information) of the payment application, and is an ID that allows the terminal 20 or the user of the terminal 20 to be identified. This application ID is set and stored as a unique ID by the server 10, by way of example and not limitation.

The authentication password is an authentication password that the user is required to input when performing payment authentication processing (hereinafter simply referred to as "authentication processing") on the terminal 20 of the user with this user name. The password you set will be remembered.

Note that the authentication process for payment does not necessarily have to be performed, and may not be performed. In this case, there is no need to store the authentication password in the user registration data 153.

Other registered information is other registered information of the user with this username, and includes, by way of example and not limitation, a user icon image, which is the image data of the icon used by the user in the payment application, the user's profile, etc. .

Store registration data 155 is registration data of stores that are affiliated with a business that provides a payment application (business of server 10). An example of the data structure of store registration data 155A, which is an example of this store registration data 155, is shown in FIG. 4-4.
In the store registration data 155A, by way of example and not limitation, industry type, store name, store location information, store POS system information, and store ID are stored in association with each other as store information.

The industry type stores the industry type of the store. This industry includes, by way of example and not limitation, "convenience stores," "supermarkets," "pharmacies," "izakayas," "department stores," "restaurants," "bookstores," and "watch stores." It will be done.

In the store name field, for each business type, store names of stores included in (belonging to) that business type are stored.

The store location information stores location information of the location of the store with this store name (hereinafter referred to as "store location information"). This store location information may represent the store location using two-dimensional or three-dimensional location coordinates, or may represent the store location using longitude and latitude (latitude, longitude, and altitude in some cases). .

The store POS system information stores information regarding the store POS system 40 used at this store. This store POS system information includes, by way of example and not limitation, information necessary for server 10 to communicate with store code reader device 50 and store server 70.

Since the store POS system 40 performs processing in cooperation with the server 10, by way of example and not limitation, the store POS system 40 acquires in advance a software package for a payment application provided (distributed) from the server 10, and stores it in the store code reader device 50 or the store. This software package can be stored in the server 70 and used by being called from a program for payment processing at a store. An application programming interface (API) is an example, and the store code reader device 50 activates the API, for example, to transmit information to the server 10 and receive information from the server 10.

In addition, the server 10 receives information such as the store's industry type, store name, store location information, store POS system information, etc. from the store server 70 of the store, and stores it in the store registration data 155, by way of example and not limitation. You can keep it as is.

The store ID is an ID that functions as identification information for identifying the store with this store name. This store ID is set and stored as a unique ID for each store by the server 10, by way of example and not limitation.
The store ID is an example of store identification information.

The payment management database 157 is a database that cumulatively stores data for managing information regarding payments of users of each terminal 20, and an example of the configuration of the payment management database 157A is shown in FIGS. 4-5.
Payment management data generated for each terminal 20 or each user of the terminal 20 is stored in the payment management database 157A.

Each payment management data stores, by way of example and not limitation, an application ID, balance, points, daily upper limit setting, auto charge setting, and payment history data.

The application ID stored in the user registration data 153 is stored in the application ID.
The balance field stores the balance associated with this application ID.

The points store stores points that can be earned at various services associated with the payment application and at affiliated stores affiliated with the payment application operator. By way of example and not limitation, points have a value equivalent to 1 yen per point, and can be exchanged for gift certificates, products, etc., and can also be converted into cash in a payment application and used for payment.

The daily upper limit set amount stores the upper limit amount per day that can be used for payment by the terminal 20 that owns this application ID or the user of the terminal 20.

The auto charge setting is a setting for whether or not to automatically replenish electronic money (auto charge) when the balance reaches a small amount (for example, "500 yen") or "0 yen". "ON" is stored when the auto charge setting is made by the user, and "OFF" is stored otherwise. By way of example and not limitation, auto-charging can be performed from a bank account registered by the user of the terminal 20, or the like.

The payment history data is data related to the payment history of the user of this application ID, and includes, by way of example and not limitation, the payment date and time that is the date and time when the payment was made by the server 10 for this application ID, and the ID of the store where the payment was made. A store ID, a payment store name that is the name of the store with the store ID, and a payment amount that is the paid amount are stored in chronological order in association with each other.

Note that it is not necessary to store all of the above information in the above payment management data. By way of example and not limitation, some or all of the points, daily maximum set amount, and auto charge settings may not be stored in the payment management data.
Furthermore, each time a payment is made, payment history information may be transmitted to the terminal 20 and stored in the terminal 20, but the payment history data may not be stored in the server 10.

The code management database 159 is a database for managing codes (terminal display codes in this embodiment), and an example of its data structure is shown in FIG. 4-6.
By way of example and not limitation, the code management database 159 stores, in chronological order, the code generation date and time, code number, and payment number in association with the application ID, as data generated for each application ID of a payment application. Contains code management data.

In the code generation date and time, the date and time when the terminal display code was generated is stored based on information timed by the clock section 19.
The code No. stores a number for identifying the code. For example, serial numbers are set and stored in chronological order.
The payment number issued when generating the terminal display code is stored in the payment number.

By way of example and not limitation, the data of the terminal display code stored in the code management data can be deleted from the code management data after a payment process is performed using the terminal display code.

As mentioned above, instead of deleting the data of the terminal display code that is no longer available from the code management data, as an example and not a limitation, the data of the terminal display code is Set a flag "Available/Unavailable" to indicate whether or not it can be used. Then, for the terminal display code that is no longer available, the flag may be set to "unusable", or it may not be necessary to do so.

Moreover, among the above, for example, the code generation date and time may not be stored in the code management data.
Further, instead of or in addition to the application ID, terminal identification information such as the terminal phone number stored in the user registration data 153 may or may not be stored in the code management data. Good too.

(2) Functional configuration of terminal FIG. 4-7 is a diagram showing an example of the functions realized by the control unit 21 of the terminal 20 in this embodiment.
The terminal 20 has a payment application processing section 211 as a function realized by the control section 21 .

The payment application processing unit 211 has a function of executing payment application processing, which is an example of processing for processing payments, based on the payment application software 281 stored in the storage unit 28.

In this embodiment, the payment application processing unit 211 executes, for example, the process shown in FIGS. 3-4 as the payment application process, according to the payment application program 282 stored in the storage unit 28.

In this embodiment, the processing related to payment includes, by way of example and not limitation, a process of obtaining a terminal display code from the server 10 (a process of requesting the server 10 to generate a terminal display code, a process of requesting the server 10 to generate a terminal display code, ), processing to stock terminal display codes acquired from server 10, processing to display stocked terminal display code images (code display processing), and displayed terminal display codes. Processing of instructing (guiding) the user to read the image with the store code reader device 50, processing of receiving (obtaining) a terminal payment completion notification from the server 10 after the payment is made by the server 10, etc. This is a concept that includes all processes that are executed by the terminal 20 as processes that are somehow related to the payment process, more specifically, processes that are related to the payment process.

The payment application processing unit 211 includes, by way of example and not limitation, a code display processing unit 2113 that executes code display processing as a functional unit.

In this embodiment, the code display processing unit 2113 performs a process of displaying a code display screen including a code image for terminal display, and also specifies the code based on the number of codes for terminal display stored in the code stock data for terminal display 2831. A process is performed to display information regarding the "remaining number of codes" (hereinafter referred to as "remaining code related information"). The remaining code number related information includes various information, which will be described in detail later.

In this embodiment, the total number of terminal display codes stored in the terminal display code stock data 2831 is counted as the "remaining number of codes". If no terminal display code is stored in the terminal display code stock data 2831, "remaining code number=0".

Note that the remaining number of codes can also be expressed as a "stock code number" or "stock number" in the sense of the number of stored codes.

FIG. 4-8 is a diagram showing an example of information stored in the storage unit 28 of the terminal 20 in this embodiment.
By way of example and not limitation, payment application software 281 is stored in the storage unit 28 as application software obtained by downloading or the like from the server 10 in advance.

Payment application software 281 includes, by way of example and not limitation, payment application program 282 and payment application data 283.

The payment application program 282 is a program read by the control unit 21 and executed as a payment application process, and includes, by way of example and not limitation, a code display processing program 2823 executed as a code display process as a subroutine program.

The payment application data 283 stores various data used in the payment application software. This payment application data 283 stores, by way of example and not limitation, terminal display code stock data 2831, payment data 2832, store data 2833, and remaining code related information display setting data 2835.

The terminal display code stock data 2831 is data in which terminal display codes acquired from the server 10 in the online state are stored, and an example of the data structure of the first terminal display code stock data 2831A is an example of this data. is shown in Figure 4-9.
In the first terminal display code stock data 2831A, by way of example and not limitation, code reception date and time, code number, and code data are stored in chronological order in association with each other.

As an example and not a limitation, the code reception date and time stores the date and time when the terminal 20 received the terminal display code from the server 10.
The code number that the terminal 20 receives from the server 10 together with the terminal display code is stored in the code number.
The code data stores, by way of example and not limitation, data of a code image of a terminal display code received by the terminal 20 from the server 10.

The data of the terminal display code stored in the first terminal display code stock data 2831A is, by way of example and not limitation, used by the server 10 to perform payment processing using the terminal display code, and from the server 10 to the terminal. After receiving the payment completion notification for the terminal (in the case of offline payment, after returning to the online state and receiving the terminal payment completion notification from the server 10), delete it from the first terminal display code stock data 2831A. You can do it like this.

Note that instead of deleting the data of the terminal display code that is no longer available from the terminal display code stock data 2831 as described above, for example, the data of the second terminal display code stock data 2831B in Figure 4-10 is deleted. As an example and not a limitation, it is also possible to store information on the usage status of the terminal display code in association with data of the terminal display code. Then, it may be possible to associate and store "unused" for terminal display codes that have not yet been used, and "used" for terminal display codes that have been used, or it is not necessary to do so. Good too.

Further, among the above, for example, the code reception date and time may not be stored in the terminal display code stock data 2831 (first terminal display code stock data 2831A or second terminal display code stock data 2831B). .

Also, instead of or in addition to the code reception date and time, by way of example and not limitation, the terminal display code received from the server 10 may be stored in the terminal display code stock data 2831 (first terminal display code stock data 2831A). or the second terminal display code stock data 2831B) (hereinafter referred to as the "code storage date and time"), or it is not necessary to do so.

Further, although details will be described later, the code data does not necessarily have to store the code image data of the terminal display code; instead of or in addition to this, the code image data of the terminal display code may be stored. The original information (in this embodiment, the payment number) may or may not be stored.
Further, one code acquired from the server 10 in the online state may or may not be stored in the terminal display code stock data 2831.

The payment data 2832 is payment data stored in the terminal 20, and the structure of the payment data 2832A, which is an example thereof, is shown in FIG. 4-11.
The payment data 2832A stores, by way of example and not limitation, an application ID, points, balance, daily upper limit setting, auto charge setting, and payment history data.

Based on the terminal payment completion notification received from the server 10 after returning to the online state, the control unit 21 determines, by way of example and not limitation, the date and time of payment by the server 10 and the store where the payment was made by the server 10. A store ID which is the ID of the store ID, a payment store name which is the name of the store with the store ID, and a payment amount which is the amount paid by the server 10 are associated and stored in payment history data in chronological order.

The store data 2833 stores various store information stored in the store registration data 155A of the server 10, by way of example and not limitation.

By way of example and not limitation, the store data 2833 can be updated by distributing the latest store information from the server 10 to the terminal 20 at the timing of updating the payment application software 281.

The remaining code number-related information display setting data 2835 is data in which information about settings regarding the display of remaining code number-related information (hereinafter referred to as "display settings") is stored.
Display settings include, by way of example and not limitation, display mode settings. Furthermore, the display mode includes various display modes such as display format, display position, and display color.

In this embodiment, the code display processing unit 2113 displays "remaining code number zero information" indicating that the number of remaining codes (stock number) is zero, as an example of information related to the number of remaining codes.
The remaining number of codes zero information is information indicating that the number of remaining codes is zero or information suggesting that the number of remaining codes is zero. This zero code remaining information includes, by way of example and not limitation, a message or image indicating that the terminal display code is not stored in the terminal display code stock data 2831. The remaining code number related information display setting data 2835 stores information on the display setting of zero code remaining number information.

The zero code remaining information is an example of second information regarding the fact that the first information is not stored in the storage unit, and information that notifies the user of the terminal that the first information is not stored in the storage unit. This is an example.
Further, the code remaining number zero information can also be expressed as "stock number zero information" in the sense that the stock number is zero.

Additionally, terminal data 289 is stored in the storage unit 28, by way of example and not limitation.
The terminal data 289 is data related to the terminal 20, and includes, by way of example and not limitation, terminal identification information such as a terminal telephone number and terminal email address, and various setting information on the terminal 20 side.

<Display screen example>
FIG. 4-12 is a diagram showing an example of the top screen of the payment application displayed on the display unit 24 of the terminal 20 in this embodiment.
The configuration of this top screen is similar to that shown in FIG. 3-2, and here a state in which the "code icon" is touched by the user of the terminal 20 is shown.

FIG. 4-13 is a diagram showing an example of a code display screen displayed on the display unit 24 of the terminal 20 in this embodiment. This code display screen is, by way of example and not limitation, a screen that is displayed when the "code icon" is touched as shown in Figure 4-12, and the terminal display code is included in the terminal display code stock data 2831. This is an example of a code display screen that is displayed when no code is stored.

On this code display screen, as an example and not a limitation, the message "There are no codes remaining. There are currently no available codes in stock" is displayed along with the "OK" icon, as an example of information with zero codes remaining. has been done. The "OK" icon is an icon operated by the user of the terminal 20 when approving the information on the number of remaining codes. When the "OK" icon is touched, the information on the number of remaining codes is displayed. will be deleted.

On the other hand, if the "code icon" is touched on the top screen of the payment application in FIG. 4-12, and at least one terminal display code is stored in the terminal display code stock data 2831, By way of example and not limitation, a code display screen is displayed that includes a code image for terminal display similar to that of FIG. 3-3.

When making an offline payment, the user of the terminal 20 presents the code display screen containing the above terminal display code image to the store clerk at the code register 60, reads the terminal display code image with the store code reader device 50, Payment is made by receiving it. In this case, the store code reader device 50 may, by way of example and not limitation, information acquired by decoding the read terminal display code image (in this example, a payment number), and information about the time when the terminal display code image was read. etc., to the server 10, and causes the server 10 to perform the payment.

In the above display screen example, the user of the terminal 20 can display the code display screen by, for example, touching the code icon without being aware of whether the user is online or offline. Convenience can be improved.

Note that the terminal display code stored in the terminal 20 can be used not only for offline payment but also for online payment. In other words, it is not necessary to determine (detect) whether the terminal 20 is in an offline state or not, and the payment can be made using the terminal display code stored in the terminal 20 regardless of whether it is online or offline. It is possible to do so.

<Processing>
FIG. 4-14 is an example of the flow of the first code display processing that is executed by the code display processing unit 2113 of the terminal 20 according to the first code display processing program, which is an example of the code display processing program 2823, in this embodiment. It is a flowchart which shows. This first code display process is performed, by way of example and not limitation, in step A250 of the process of FIGS. 3-4.

Here, in the process of FIG. 3-4, the process is shown to end after A290, but in reality, the process is looped.

Specifically, by way of example and not limitation, if a code acquisition operation by the user of the terminal 20 is detected after A290, the control unit 21 returns the process to A110. On the other hand, if a code display operation by the user of the terminal 20 is detected after A290, the control unit 21 returns the process to A250.

As described above, the terminal display code data stored in the terminal display code stock data 2831 is, by way of example and not limitation, used to perform payment processing by the server 10 using the terminal display code (C170). , After receiving the terminal payment completion notification from the server 10 in A290 (if offline payment is made, after returning to the online state and receiving the terminal payment completion notification from the server 10), the terminal display code stock data Deleted from 2831. Therefore, when the process returns to A250 after A290, the stored terminal display codes may have been used up and the remaining number of codes may be zero.

In the first code display process, the code display processing unit 2113 counts the number of remaining codes (D110). Then, the code display processing unit 2113 determines whether the counted number of remaining codes is zero (D120).

If it is determined that the remaining number of codes is zero (D120: YES), the code display processing unit 2113 acquires the display setting of the remaining code number zero information stored in the remaining code number related information display setting data 2835 ( D130).

Thereafter, the code display processing unit 2113 causes the display unit 24 to display a code display screen including information on the number of remaining codes with zero based on the display settings (including display mode settings, for example) acquired in D130 (D140). .

Thereafter, the code display processing unit 2113 determines whether the first display end condition is satisfied (D180). The first display termination condition may be, for example, detecting an operation by the user of the terminal 20 to approve the information with zero remaining codes, or detecting an operation to hide the code display screen by the user of the terminal 20. But it doesn't have to be that way.

If it is determined that the first display end condition is not satisfied (D180: NO), the code display processing unit 2113 remains on standby. On the other hand, if it is determined that the first display end condition is satisfied (D180: YES), the code display processing unit 2113 ends the first code display processing.

On the other hand, if it is determined that the remaining number of codes is not zero (D120: NO), the code display processing unit 2113 displays the code image of the terminal display code stored in the terminal display code stock data 2831 (e.g., A code display screen including the code image of the oldest terminal display code is displayed on the display unit 24 (D150).

Thereafter, the code display processing unit 2113 determines whether the second display end condition is satisfied (D190). The second display termination condition may be, for example, detecting an operation to hide the code display screen by the user of the terminal 20, or the expiration of the above-mentioned code display deadline, or may be other than that. .

If it is determined that the second display end condition is not satisfied (D190: NO), the code display processing unit 2113 remains on standby. On the other hand, if it is determined that the second display termination condition is satisfied (D190: YES), the code display processing unit 2113 terminates the first code display processing.

Note that, as described above, the method of the present disclosure is applicable if terminal display codes are stocked in the terminal 20. Therefore, the first code display process described above can be applied in the same way regardless of whether the device is online or offline.

<Code>
In the above process, an example is shown in which the terminal 20 requests the server 10 to generate a terminal display code image, and the terminal display code image generated by the server 10 is transmitted to the terminal 20. It is not limited to this. For example, the terminal 20 may request the server 10 to generate original information (in this example, a payment number), and the original information generated by the server 10 may be sent to the terminal 20, You don't have to do it that way.

Specifically, in the process of FIG. 3-1, at A110, the control unit 21 transmits code generation request information requesting the server 10 to generate original information (in this example, a payment number). Based on this code generation request information, the control unit 11 generates original information in C120, and transmits the generated original information to the terminal 20 in C130. Upon receiving the original information from the server 10 at A130, the control unit 21 generates a terminal display code image based on the received original information (in this example, the payment number). Then, the control unit 21 causes the display unit 24 to display the generated code image for terminal display.

Similarly, in the process of FIG. 3-4, when the original information (in this example, the payment number) is received from the server 10 at A130, the control unit 21 receives the received original information (in this example, the payment number) at A240. ) is stored in the terminal display code stock data 2831. Then, the control unit 21 reads the stocked original information from the terminal display code stock data 2831, and generates a terminal display code image based on the read original information. Then, at A250, the control unit 21 causes the display unit 24 to display the generated terminal display code image.

Also, unlike the above, the terminal 20 requests the server 10 to generate a terminal display code image, and the terminal display code image generated by the server 10 is sent to the terminal 20, but on the terminal 20 side, Instead of stocking the terminal display code image received from the server 10, the original information obtained by decoding the terminal display code image received from the server 10 may be stocked, or it may not be necessary to do so. good.

<Effects of the first embodiment>
In the first embodiment, the terminal 20 receives the code image and original information (not limited, but an example of first information) of the terminal display code transmitted from the server 10 via the communication I/F 22. Then, in the terminal 20, the control unit 21 stores the received code image and original information of the terminal display code in the terminal display code stock data 2831 of the storage unit 28.
In addition, the terminal 20 displays a code image of the stored terminal display code and a terminal display code image based on the original information (an example of the first code image, not a limitation) on the code display screen (not a limitation, but the terminal display code image is an example of the first code image). example of the display area).
Furthermore, the terminal 20 performs a process (not limited to An example of processing related to payment) is executed.
Then, after receiving the terminal payment completion notification, if the code image or original information of the terminal display code is not stored in the terminal display code stock data 2831, the terminal 20 receives the code remaining zero information (limited to The configuration is shown in which an example of the second information is displayed.
As an example of the effect obtained by such a configuration, based on processing related to payment, second information indicating that the first information is not stored in the storage unit is displayed in the display area of the terminal, so that the first information is not stored in the storage unit. It is possible to notify the user that the information has not been updated, and it is possible to improve the user's convenience.

Further, in the first embodiment, the terminal 20 includes a processor that reads the payment application program 282 from the memory that stores the program and executes payment application processing based on the read payment application program 282. Then, the processor receives, via the communication I/F 22, the code image and original information (not limited to, an example of the first information) of the terminal display code transmitted from the server 10, and the received terminal The code image and original information of the display code are stored in the terminal display code stock data 2831 of the storage unit 28, and the terminal display code image (limited) is stored based on the code image and original information of the stored terminal display code. The server 10 After completing the payment, execute the process of receiving a terminal payment completion notification from the server 10 (not limited to this, but an example of processing related to payment), and after receiving the terminal payment completion notification, execute the process of receiving the terminal payment completion notification from the server 10. This shows a configuration that displays zero code remaining information (not a limitation, but an example of second information) when no image or original information is stored in the terminal display code stock data 2831.
With such a configuration, the same effects as described above can be obtained.

Further, in the first embodiment, code images and original information of a plurality of terminal display codes are stored in the terminal display code stock data 2831. The zero code remaining information is displayed based on the determination result of the condition for the number of code images and original information (remaining code number) of multiple terminal display codes stored in the terminal display code stock data 2831. Shows the configuration displayed on the screen.
As an example of the effect obtained by such a configuration, since a plurality of pieces of first information can be stored in the storage section of the terminal, convenience for the user can be improved. Further, the second information can be displayed in the display area of the terminal at an appropriate timing based on the plurality of pieces of first information stored in the storage unit.

Furthermore, in the first embodiment, the zero code remaining information (not limited, but an example of second information) indicates that the code image or original information of the terminal display code is not stored in the terminal display code stock data 2831. The configuration is shown as information for notifying the user of the terminal 20.
As an example of the effect obtained by such a configuration, it is possible to notify the user of the terminal that the first information is not stored in the storage unit, thereby improving convenience for the user.

<First modification (1)>
In the first embodiment, at least one terminal display code image may be stored in the terminal display code stock data 2831 as a terminal display code image that can be used in an emergency. In this case, as an example and not a limitation, in the terminal display code stock data 2831, the terminal display code for emergencies should be associated with a flag indicating that it is for emergencies. I can do it.

Furthermore, in this case, the terminal display code for emergencies can be set on the terminal 20 by, for example, the user of the terminal 20 performing a selection operation. By way of example and not limitation, a list of terminal display codes stored in the terminal display code stock data 2831 is displayed within the payment application. Then, the user is allowed to select (for example, select by touch operation) the terminal display code that he or she wants to use for emergencies, and a flag indicating that the terminal display code is used for emergencies is set in association with the selected terminal display code. I can do it.

Note that a plurality of (two or more) terminal display codes may or may not be set as terminal display codes for emergencies.
Further, in this case, the user may or may not be allowed to select a plurality of (two or more) terminal display codes as terminal display codes for emergency situations.

In this case, when counting the number of remaining codes in D110 above, the terminal display code image with the flag indicating that it is for emergency use is excluded from the counting of the remaining number of codes, and the remaining number of codes (stock number) is calculated. It can be determined whether or not is zero.

In this modification, among the code images and original information of the terminal display code stored in the terminal display code stock data 2831, those that can be used in an emergency are excluded, and the terminal display code is stored in the terminal display code stock data 2831. This shows a configuration in which when no code image or original information is stored, information on the number of remaining codes (zero) is displayed on the code display screen.
As an example of the effect obtained by such a configuration, it is possible to ensure the first information that can be used in an emergency, while notifying the user that the first information is not stored, improving user convenience. be able to.

<First modification (2)>
In the first embodiment, the terminal display code displayed on the code display screen may or may not be excluded from counting the remaining number of codes.

Specifically, as an example and not a limitation, when reading and displaying one terminal display code from the terminal display codes stored in the terminal display code stock data 2831, the data of that terminal display code is stored in the active storage area (hereinafter referred to as "active storage area") of the storage unit 28 and deleted from the terminal display code stock data 2831. Thereafter, the total number of terminal display codes stored in the terminal display code stock data 2831 is counted as the remaining number of codes. By doing this, the terminal display code displayed on the code display screen is excluded from the count of the remaining number of codes.

FIG. 4-15 is a diagram showing an example of a code display screen in this modification.
This code display screen is, by way of example and not limitation, a screen that is displayed when the "code icon" is touched as shown in Figure 4-12, and the terminal display code is included in the terminal display code stock data 2831. This is an example of a code display screen that is displayed when one code is stored.

This code display screen includes a one-dimensional terminal display code image represented by a barcode and a two-dimensional terminal display code image represented by a QR code as the code image of the terminal display code stored in the active storage area. The code images QC1 are displayed in different areas on the display screen. Furthermore, by way of example and not limitation, a 12-digit payment number is displayed below the one-dimensional terminal display code image.

Additionally, at the bottom of this code display screen, the message "There are no codes available other than the one currently displayed." is displayed as an example of information on the number of codes remaining. Then, the terminal can notify the user of the terminal that the first information other than the first information displayed in the display area is not stored in the storage unit.

<First modification (3)>
In the first embodiment, the "first information (code information)" in the present disclosure is a payment number or a terminal display code image including the payment number, but is not limited thereto. For example, a token, which is a type of authentication information, or a terminal display code image including the token can also be used as the "first information (code information)" in the present disclosure.

In this case, instead of including the payment number in the terminal display code image, as an example and not a limitation, a token issued using a method (algorithm) that generates random tokens should be included in the terminal display code image. You may or may not have to do so. In this case, on the server 10 side, identification information for identifying the terminal 20 or the user of the terminal 20 and the issued token are associated and stored in the code management data of the code management database 159 of the storage unit 15. Just do it like this.

A "token" is, by way of example and not limitation, a type of authentication information used by the server 10 to authenticate that the terminal 20 or the user of the terminal 20 is the authorized terminal 20 or the authorized user of the terminal 20. be. "Authentication information" is information issued by a certification authority, and the above token functions as authentication information issued by the server 10 as a certification authority to authenticate the terminal 20 or the user of the terminal 20.

Note that the token can also be expressed as a "random token," "access token," "payment token," etc., for example. Since the tokens are issued randomly as described above, the tokens will be different each time the terminal display code is generated. Therefore, the token functions as a one-time password.

In addition to the payment number and token, the server 10 also provides an example of access information for the store code reader device 50 that has read the terminal display code image to access a website or web page provided by the server 10. Information such as a URL (Uniform Resource Locator) for accessing a payment page, which is a type of web page provided, may or may not be included.

<First modification (4)>
In the first embodiment, when the terminal 20 causes the display section 24 to display a terminal display code image, by way of example and not limitation, the control section 21 causes the store code reader device 50 to read the displayed terminal display code image. You may or may not need to perform a process of instructing (guiding) the user to do so. This process is an example of a process related to payment.

Specifically, as an example and not a limitation, on the code display screen that displays the code image for terminal display, in an area different from the area where the code image for terminal display is displayed, there is a message that says ``The displayed code image is the store code.'' A message such as "Please read it with a reader." can be displayed.

<First modification (5)>
In the first embodiment, when the number of remaining codes is zero, information on the number of remaining codes of zero is displayed, but the present invention is not limited to this. For example, when the number of codes remaining is less than or equal to a certain number (for example, one of "1" to "3"), the terminal 20 receives information indicating that the number of codes remaining is insufficient. , or information suggesting that the remaining number of codes is insufficient may or may not be displayed on the display unit 24.

<First modification (6)>
The display screen of the payment application described in the first embodiment is merely an example, and the design can be changed as appropriate. For example, a ``code (offline) icon'' labeled ``code (offline)'' is displayed on the top screen of the payment application, in addition to the above-mentioned ``code icon.'' If it is determined that the terminal 20 is in the online state, the terminal display code is displayed when the "code icon" is operated, and if it is determined that the terminal 20 is in the offline state, the "code (offline) icon" may or may not be displayed.

<First modification (7)>
Even if the terminal display code is displayed on the display unit 24 by performing the processes of A240 and A250 at the timing when the terminal 20 receives the terminal display code from the server 10 in A130 of the process in FIG. That's fine, and you don't have to do it that way.

In this case, as an example and not a limitation, after the code icon is touched on the top screen of the payment application (for example, Figure 3-2), the display may be switched directly to the code display screen of the code for terminal display. .

<Second example>
In the second embodiment, as another example of the information related to the number of remaining codes, information indicating the number of remaining codes or information suggesting the number of remaining codes (hereinafter comprehensively referred to as "remaining code number information") is sent to the terminal 20. This is an example of displaying on the display section 24 of.

The content described in the second embodiment is applicable to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

The code remaining number information in this embodiment includes, by way of example and not limitation,
・Representation of the number of remaining codes by numbers ・Representation of the number of remaining codes by different colors ・Representation of the number of remaining codes by color intensity ・Representation of the number of remaining codes by size ・Number of remaining codes It can include at least one image representation of, or a combination of these.

In addition, the number of remaining codes is shown as an example, not as a limitation.
- Representing the number of remaining codes with marks, icons, pictures, etc. - Representing the number of remaining codes with a gauge (gauge format)
・Remaining number of codes expressed as a card (card format)
・Graphic representation of the number of remaining codes (graph format)
or a combination thereof.

For example, when the "code icon" is touched on the top screen of the payment application in Figure 4-12, and at least one terminal display code is stored in the terminal display code stock data 2831, the code By way of example and not limitation, the display processing unit 2113 can display the following code display screen.

<Display screen example>
FIG. 5-1 is a diagram showing an example of a code display screen in this embodiment.
On this code display screen, as an example of remaining code information that represents the remaining number of codes as an image, on the area where the one-dimensional terminal display code is displayed, a rectangle for the number of codes remaining that has been counted is displayed. An image of the number of codes remaining is displayed. In this display example, since the number of remaining codes is five, five remaining code number images are displayed side by side. In this display example, the user of the terminal 20 can grasp the number of remaining codes at a glance.

FIG. 5-2 is a diagram showing another example of the code display screen in this embodiment.
On this code display screen, above the area where the one-dimensional terminal display code is displayed, an image of the two-dimensional code and the code are displayed as an example of remaining code information that represents the remaining number of codes as a combination of images and numbers. Information that is a combination of numbers "x1, x2, x3, . . ." indicating the remaining number is displayed. Even in this display example, the user of the terminal 20 can grasp the number of remaining codes at a glance.

FIG. 5-3 is a diagram showing another example of the code display screen in this embodiment.
On this code display screen, above the area where the one-dimensional terminal display code is displayed, as an example of remaining code information that represents the remaining number of codes as an image, the code is displayed as a gauge configured horizontally. The remaining number gauge is displayed.

The remaining code gauge is divided into a plurality of areas, and the areas corresponding to the number of remaining codes are colored and displayed. In this display example, the remaining code gauge is divided into five areas, and when the number of remaining codes is counted as "4," the four areas from the left are displayed in color. There is. Even in this display example, the user of the terminal 20 can grasp the number of remaining codes at a glance.

FIG. 5-4 is a diagram showing another example of the code display screen in this embodiment.
On this code display screen, as in FIG. 5-3, a remaining code gauge is displayed above the area where the one-dimensional terminal display code is displayed. In this display example, since the number of remaining codes is counted as "5", five areas from the left (all areas) are displayed in color. Furthermore, on the right side of the remaining code gauge, the word "FULL" is displayed to indicate that the remaining number of codes is full.

FIG. 5-5 is a diagram showing another example of the code display screen in this embodiment.
On this code display screen, above the area where the one-dimensional terminal display code is displayed, there is a remaining code mark, which is represented by an image of a face, as an example of remaining code information, which shows the number of remaining codes as an image. Displayed. In this display example, the code remaining mark is displayed with the same facial expression (for example, a smiling face) regardless of the remaining code number, but the color (face color) is displayed differently depending on the remaining code number. Specifically, by way of example and not limitation, the smaller the number of remaining codes, the darker the color, and conversely, the larger the number of remaining codes, the lighter the color.

Note that instead of changing the color density of the remaining code mark, the color of the remaining code mark may or may not be changed.
For example, the state with the least number of codes remaining is "red", the state with the most codes remaining is "blue", and the color of the remaining code mark is changed as follows: "red → orange → yellow → green → blue". It may or may not be displayed.

FIG. 5-6 is a diagram showing another example of the code display screen in this embodiment.
On this code display screen, like the code display screen above, a code remaining mark represented by a face image is displayed above the area where the one-dimensional terminal display code is displayed. In the illustrated example, a code remaining mark with a different facial expression is displayed depending on the remaining code number. Specifically, by way of example and not limitation, the more codes remaining, the brighter the expression, and conversely, the fewer the remaining codes, the darker the expression.

Note that it is also possible to display the remaining code mark in a combination of the mode shown in FIG. 5-5 and the mode shown in FIG. 5-6. In other words, it is also possible to display a code remaining mark with a different facial expression and a different face color depending on the remaining code number.

<Processing>
FIG. 5-7 shows an example of the flow of the second code display process executed by the code display processing unit 2113 of the terminal 20 according to the second code display process program, which is an example of the code display process program 2823, in this embodiment. It is a flowchart which shows. This second code display process is performed, by way of example and not limitation, at step A250 of the process of FIGS. 3-4.
Note that the same steps as those in the first code display process (FIG. 4-14) are given the same reference numerals and will not be described again.

The process in FIG. 5-7 is a rewrite of the process after D110 in the first code display process (FIG. 4-14).

After D110, the code display processing unit 2113 acquires the display setting for the remaining code number information stored in the remaining code number related information display setting data 2835 (E130). Thereafter, the code display processing unit 2113 displays a code display screen including the remaining code number information and the code image for terminal display on the display unit 24 based on the display settings (including display mode settings, for example) acquired in E130. (E140).

Thereafter, the code display processing unit 2113 determines whether the third display end condition is satisfied (E190). The third display termination condition may be, for example, detection of an operation to hide the code display screen by the user of the terminal 20, or the expiration of the above-mentioned code display deadline, or may be other than that. .

If it is determined that the third display end condition is not satisfied (E190: NO), the code display processing unit 2113 remains on standby. On the other hand, if it is determined that the third display end condition is satisfied (E190: YES), the code display processing unit 2113 ends the second code display processing.

<Effects of the second embodiment>
In the second embodiment, the number of code images and original information (not limited, but an example of first information) of terminal display codes stored in the terminal display code stock data 2831, that is, the remaining number of codes (stock number) A configuration is shown in which code remaining number information indicating the number of remaining codes (not limited, but an example of information regarding the number of first information stored in the storage unit) is displayed on the code display screen.
As an example of the effect obtained by such a configuration, the terminal displays information regarding the number of first information stored in the storage unit in the display area, thereby displaying information regarding the number of first information stored in the storage unit. can be notified to the user.

In this case, the code remaining number zero information shown in the first embodiment is the number of code images and original information of the terminal display code stored in the terminal display code stock data 2831 among the remaining code number information. It shows a configuration that is information indicating that it is zero.
As an example of the effect obtained by such a configuration, the terminal notifies the user of the number of pieces of first information stored in the storage unit and that the number of first information items stored in the storage unit is zero. be able to.

Further, in the second embodiment, the remaining code information is displayed in different display modes based on the number of code images and original information of the terminal display code stored in the terminal display code stock data 2831. It shows.
As an example of the effect obtained by such a configuration, the terminal can display the number of pieces of first information stored in the storage unit in a manner that allows the user to easily understand (can understand at a glance).

Further, the second embodiment shows a configuration in which the terminal 20 executes control by the control unit 21 to change the display mode of the remaining code number information based on displaying the terminal display code image on the code display screen. There is.
As an example of the effect obtained by such a configuration, the terminal performs control to change the display mode of information related to numbers based on displaying the first code image in the display area, thereby controlling the display of the first code image. Accordingly, the number of pieces of first information stored in the storage unit can be appropriately notified to the user.

<Second modification (1)>
In the second embodiment, when the number of remaining codes is relatively large, depending on the method of displaying the remaining code number information, the remaining code number information may not be completely displayed on the screen or may look bad. Therefore, an upper limit number of remaining code information to be displayed may or may not be set.

In addition, in this case, if the number of remaining codes exceeds the upper limit, the information on the number of remaining codes may be displayed in the same manner as when the number of remaining codes is the same as the upper limit. You don't have to. For example, if you set the upper limit to 5, if the number of remaining codes exceeds 5, the remaining code information will be displayed in the same manner as when there are 5 remaining codes. It can be done.

For example, the code display screen shown in Figure 5-4 above is for the case where the number of remaining codes is "5", and the five areas (all areas) of the remaining code number gauge are displayed in color. , the word "FULL" is displayed on the right side of the remaining code gauge. In this case, even when the number of remaining codes exceeds five, the remaining code information may or may not be displayed in the same manner as the code display screen shown in FIG. 5-4.

Also, different from this, if there are 5 codes remaining, the 5 areas (all areas) of the remaining code number gauge are displayed in color, but the word "FULL" is not displayed. If the number of remaining codes exceeds five, the characters "FULL" may or may not be displayed.

In addition, although the case where the remaining code number information is displayed in the gauge format shown in FIGS. 5-3 and 5-4 has been exemplified here, the same applies to the case where the remaining code number information is displayed in other formats.

Specifically, for example, if the number of remaining codes is expressed as a number, the number when the number of remaining codes exceeds the upper limit should be expressed as the same number as the number when the number of remaining codes is the same as the upper limit. Just do it.
For example, if the number of remaining codes is expressed by the intensity of a color, the intensity of the color when the number of remaining codes exceeds the upper limit is the same as that when the number of remaining codes is the same as the upper limit. It may be expressed by the density of .

<Second modification (2)>
As explained in the first modification (2), the terminal display code displayed on the code display screen may be excluded from the count of the remaining number of codes.

In this case, as described above, when reading and displaying one terminal display code from the terminal display codes stored in the terminal display code stock data 2831, the data of that terminal display code is stored. 28 and deleted from the terminal display code stock data 2831.

Thereafter, the total number of terminal display codes stored in the terminal display code stock data 2831 is counted as the remaining number of codes. By doing this, the terminal display code displayed on the code display screen is excluded from the count of the remaining number of codes. Based on the number of remaining codes counted in this way, the remaining number of codes information can be displayed in the manner shown in FIGS. 5-1 to 5-6, for example.

<Second modification (3)>
It may be possible to perform a process that combines the display of the zero remaining code information explained in the first embodiment and the display of the remaining code number information explained in the second embodiment, or it is not necessary to do so. good.

FIG. 5-8 is an example of the flow of the third code display process executed by the code display processing unit 2113 of the terminal 20 according to the third code display process program, which is an example of the code display process program 2823, in this modification example. It is a flowchart which shows. This third code display process is performed, by way of example and not limitation, in step A250 of the process of FIGS. 3-4.
Note that steps that are the same as those already described are given the same reference numerals, and repeated explanations will be omitted.

The process in FIG. 5-8 is a combination of the first code display process (FIG. 4-14) and the second code display process (FIG. 5-7).

After D110, if it is determined that the counted remaining number of codes is zero (D120: YES), the code display processing unit 2113 performs the processes of D130 to D180, and then ends the third code display process.

On the other hand, if it is determined that the counted remaining number of codes is not zero (D120: NO), the code display processing unit 2113 completes the third code display processing after performing the processing from E130 to E190.

<Second modification (4)>
A time limit (hereinafter referred to as "code expiration date") within which payment can be made using the terminal display code generated by the server 10 is set, and this code expiration date It is also possible to display the information in a manner that the user of the terminal 20 can recognize.

The code expiration date can be a term managed on the server 10 side for each generated terminal display code. For example, the date and time when the server 10 generated the terminal display code is defined as the "code generation date and time", and the validity period of the code set by the server 10 is defined as the "code validity period". In this case, as an example and not a limitation, "the period from the code generation date and time until the code validity time elapses" is set as the code validity period.

FIG. 5-9 is a flowchart showing an example of the flow of processing executed by each device in this modification. Examples of processing executed by the control unit 21 of the terminal 20, processing executed by the control unit 51 of the store code reader device 50, and processing executed by the control unit 11 of the server 10 are shown in order from the left.

The flowchart in FIG. 5-9 is a partial rewrite of the flowchart in FIG. 3-4. The flowchart of FIG. 3-4 differs from the flowchart in steps A330 to A350, B350, B360, C320, C330, C370, etc., by way of example and not limitation.

In this process, as an example, identification information for identifying the terminal 20 or the user of the terminal 20 will be described as the above-mentioned application ID.

After C110, the control unit 11 of the server 10 performs terminal display code generation processing (C320). Specifically, as an example and not a limitation, a method (algorithm) that generates a random number of a predetermined number of digits (for example, about 10 to 12 digits) is used to generate a random number of a predetermined number of digits. will be generated as a payment number. Then, by way of example and not limitation, a code image for terminal display is generated that includes at least the payment number as original information. More specifically, at least the payment number is encoded (encoded) and graphically (imaged) to generate a code image for terminal display represented by an image of a two-dimensional code (for example, a QR code).

In addition, the control unit 11 adds the code generation date and time based on the clock information of the clock unit 19 to the code management data of the application ID included in the received code generation request information in the code management database 159, by way of example and not limitation. , the code number, the generated payment number, and the code expiration date set for the generated terminal display code are stored in association with each other.

Next, the control unit 11 transmits, by way of example and not limitation, the generated terminal display code (in this example, the terminal display code image) and the code expiration date set for the terminal display code together with the code number. It is transmitted to the terminal 20 via the I/F 14 (C330).

When the communication I/F 22 receives the terminal display code (terminal display code image in this example) and the code expiration date from the server 10 (A330), the control unit 21 of the terminal 20 receives the received terminal display code. (in this example, a code image for terminal display) is stocked (A340). Specifically, the code data of the received terminal display code and the received code expiration date are stored in the terminal display code stock data 2831 in association with the code reception date and time and code number.

In the offline state, by way of example and not limitation, when the user of the terminal 20 performs a code display operation, the code display processing unit 2113 performs code display processing (A350).

Specifically, by way of example and not limitation, the code display processing unit 2113 reads the code data of the terminal display code stored in the terminal display code stock data 2831, and displays the code including the terminal display code image. The screen is displayed on the display unit 24. At this time, the code display processing unit 2113 associates the remaining code information with the code expiration date information and displays them on the code display screen, by way of example and not limitation.

Thereafter, when the user of the terminal 20 presents the terminal display code image displayed on the display unit 24 to a store clerk or the like, the control unit 51 controls the terminal display code image displayed on the display unit 24 of the terminal 20. is controlled to be read by the code reader 58 (B350).

Thereafter, the control unit 51 accesses the server 10 through the communication I/F 54 using the above-mentioned application interface (API), etc., and obtains at least the payment number obtained by decoding the read terminal display code image and the store identification number. Payment request information including the information, the scheduled payment amount, and the time when the terminal display code image was read (hereinafter referred to as "code reading time") is transmitted to the server 10 via the communication I/F 54 (B360). .

When payment request information is received from the store code reader device 50 through the communication I/F 14 (C160), the control unit 11 performs payment processing (C370).

Specifically, it is determined whether the payment number included in the received payment request information is stored in the code management database 159 in association with the application ID. If it is determined that the code has been stored, the code reading time included in the received payment request information is within the code expiration date stored in association with the payment number in the code management data of the application ID. Determine whether it exists or not. If this condition is satisfied, it is determined that "payment is possible", and the scheduled payment amount is subtracted from the balance stored in the payment management data of the application ID in the payment management database 157A, and the payment is made.

FIG. 5-10 is a diagram showing an example of a code display screen in this modification. This code display screen is displayed at A350 in the process of FIG. 5-9, by way of example and not limitation.
On this code display screen, similar to the code display screen in Figure 5-1, on the area where the one-dimensional terminal display code is displayed, a code for the number of remaining codes that has been counted is displayed, for example, in a rectangular shape. The remaining images are displayed. However, unlike the code display screen in Figure 5-1, the color density of the remaining code image corresponding to each terminal display code is based on the code expiration date associated with the corresponding terminal display code. is displayed.

In this case, as an example and not a limitation, the code display processing unit 2113 displays the code remaining number image corresponding to the terminal display code with a shorter remaining code expiration date in a lighter color. Conversely, the code remaining number image corresponding to the terminal display code with a longer remaining code expiration time is displayed in a darker color.

In addition, instead of changing the color density of the remaining code image based on the code expiration date, you may change the color of the remaining code image based on the code expiration date, or you may not do so. good. For example, the color of the remaining code number image can be changed in order of shortest remaining code expiration time, such as "red → orange → yellow → green → blue."

By doing so, the terminal can display the number of pieces of first information (code information) stored in the storage unit as well as the information on the expiration date (for example, the expiration date) associated with each piece of first information (code information). (remaining time) can be notified to the terminal user.

This method is effective when, for example, the terminal display codes are acquired from the server 10 at different times, or when the terminal display codes are replenished from the server 10 at different times. This is useful because the terminal user can grasp the deadline information at a glance.

In addition, in the above process, the terminal display code and the code expiration date (not a limitation, but an example of information regarding the expiration date) are transmitted from the server 10 to the terminal 20, and the terminal 20 receives the code. However, it is not limited to this.

Specifically, by way of example and not limitation, the code validity period is stored in advance in the payment application data 283 of the terminal 20. As an example and not a limitation, the code generation date and time (not a limitation, but an example of information regarding the expiration date) may be transmitted from the server 10, and the terminal 20 may be configured to receive the code generation date and time from the server 10. That's fine, and you don't have to do it that way. In this case, the terminal 20 can specify the code expiration date based on the received code generation date and time and the code expiration time stored in the payment application data 283.

Furthermore, instead of setting the date and time at which the code expiration date starts as the code generation date and time, the date and time at which the terminal display code was sent from the server 10 to the terminal 20 (hereinafter referred to as the "code transmission date and time") may be used. can. In this case, the terminal 20 can identify the code expiration date based on the code transmission date and time and the code expiration time stored in the payment application data 283, by way of example and not limitation.

In addition to this, by way of example and not limitation, information on the date and time when the code expiration date ends is transmitted from the server 10 to the terminal 20 as information regarding the expiration date. The terminal 20 can also specify the code expiration date based on the code expiration time and the date and time when the received code expiration date ends.

Further, the code expiration date associated with the terminal display code may not be transmitted from the server 10 to the terminal 20, so that the terminal 20 side may not know the code expiration date set by the server 10. In this case, the terminal display code stock data 2831 may not store the code expiration date, but may store the code reception date and time, code number, and code data in association with each other, by way of example and not limitation. .

Further, in this case, a temporary code expiration date (hereinafter referred to as "temporary code expiration date") may or may not be set on the terminal 20 side. Specifically, as an example and not a limitation, the temporary code expiration date may be set as "the period from the code reception date and time (or code storage date and time) until the code validity time elapses." You don't have to.

<Third Example>
In the second embodiment, information on the number of remaining codes is displayed on the code display screen, but as described above, there are two methods for counting the number of remaining codes. Therefore, it is difficult for the user to understand whether the terminal display code displayed on the code display screen is included in the number of remaining codes recognized from the remaining number of codes information or not. There is.

The content described in the third embodiment is applicable to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

FIG. 6-1 is a diagram showing an example of a code display screen in this embodiment.
On this code display screen, a first guide image represented by a rectangle with a number inside, for example, corresponding to the counted number of remaining codes is displayed above the area where the one-dimensional code image for terminal display is displayed. is displayed.

In this display example, five first guide images are displayed, and as an example and not a limitation, the color of the first guide image displayed on the far left changes to black and it floats toward the front. Highlighted as a condition. Further, the remaining four first guide images are displayed in a default state. When any one of the remaining four first guide images is touched, a terminal display code image corresponding to the first guide image is displayed at the center of the screen.

FIG. 6-2 is a diagram showing another example of the code display screen in this embodiment.
On this code display screen, a second guide image that is a simplified (simulated) two-dimensional code is displayed, for example, for the number of remaining codes counted, above the area where the one-dimensional code image for terminal display is displayed. has been done.

In this display example, five second guide images are displayed, and when any of the second guide images is touched by the user, the touch-operated second guide Based on the data of the terminal display code corresponding to the image, the terminal display code image is displayed in the center of the screen by animation.

In this display example, when the leftmost second guide image is touched, the entire image including the terminal display code image is changed based on the display position of the leftmost second guide image. The enlargement process is gradually performed to a specified size based on the size of the display screen of the display unit 24, and finally, when the specified size is reached, the enlargement process ends, and the image shown on the right side of the drawing in Figure 6-2 It will be displayed as shown. Further, when the enlargement process is completed, the display of the corresponding second guide image is erased, and the remaining four second guide images are displayed shifted to the left.

Note that instead of erasing the display of the guide image corresponding to the displayed code image for terminal display and then filling in the remaining guide images and displaying the displayed code image for terminal display, as in this example, The display of the guide image corresponding to is deleted, but the remaining guide images may or may not be displayed in the same position without being packed together.

FIG. 6-3 is a diagram showing another example of the code display screen in this embodiment.
On this code display screen, similar to the code display screen in Figure 6-2, on the area where the one-dimensional code image for terminal display is displayed, the number of remaining codes that have been counted is displayed, for example, as a rectangle. The third guide image is displayed, but in this example, the third guide image that was touched is displayed as is (active state), and the remaining third guide images change to inactive state. The difference is that it is displayed as

Specifically, in this display example, five third guide images are displayed, and when the user performs a touch operation on any third guide image, the touch operation is performed as in FIG. 6-2. Based on the data of the terminal display code corresponding to the operated third guide image, the terminal display code image is displayed in the center of the screen by animation.

In this display example, when the leftmost third guide image is touched, the entire image including the terminal display code image is changed based on the display position of the leftmost third guide image. The enlargement process is gradually performed to a specified size based on the size of the display screen of the display unit 24, and finally, when the specified size is reached, the enlargement process is completed, and the image shown on the right side of the drawing in Figure 6-3 is It will be displayed as shown. Furthermore, the leftmost third guide image that has been touched is displayed as is (active state), and the remaining four third guide images are changed to inactive states and displayed.

Note that the second guide image and the third guide image described above are just icons (marks) that simulate two-dimensional code images (for example, QR code images), and are not real code images. Therefore, it goes without saying that these guide images cannot be read by a code reader and cannot be used for payment.

FIG. 6-4 is a diagram showing another example of the code display screen in this embodiment.
In this code display screen, a plurality of terminal display codes (terminal display code images) stored in the terminal display code stock data 2831 are displayed by way of example, not limitation, when the user of the terminal 20 performs a swipe operation. , which can be switched and displayed in a sliding manner.

Specifically, as an example and not a limitation, the same number of terminal display codes (that is, remaining codes) as the terminal display codes stored in the terminal display code stock data 2831 may be placed above the area where the one-dimensional terminal display code image is displayed. (the same number as the stock number), for example, fourth guide images represented by circles (◯) are displayed side by side in the horizontal direction.

As an example and not a limitation, the fourth guide image corresponds to the first terminal display code, the second terminal display code, the third terminal display code, etc. in order from the left. Therefore, when the code image of the corresponding terminal display code is displayed in the center of the screen, the fourth guide image, which was displayed in white, changes to black and is displayed.

In this display example, since there are 5 codes remaining (stock number), 5 terminal display codes can be switched and displayed in a sliding manner, and each is represented by 5 circles. A fourth guide image is displayed.

The left side of the drawing shows a state where the first code image including the two-dimensional terminal display code image QC1 is displayed, the fourth guide image first from the left is displayed as a black circle, and the other The guide image No. 4 is displayed as a white circle.
The center of the drawing shows a state in which the user of the terminal 20 performs a touch operation on the display screen and then performs a swipe operation to the left from that position. By swiping leftward, the display of the first code image containing the two-dimensional terminal display code image QC1 changes to the display of the second terminal display code containing the two-dimensional terminal display code image QC2. Switch to .
The right side of the drawing shows a state where the second terminal display code including the two-dimensional terminal display code image QC2 is displayed by this swipe operation, and the fourth guide image second from the left is a black circle. The other fourth guide image is displayed as a white circle.

The various guide images exemplified above are information on the remaining number of codes (not limited to this, but is an example of information regarding the number of first information stored in the storage unit), as well as code images for terminal display and original information. This is an example of guidance information (guide information) for guiding (informing) the user of the terminal 20 of the correspondence relationship with information (not limited, but an example of first information).

Note that the display order of the guide image/terminal display code image in the above display example is not a limitation, but is an example, starting from the left, of the terminal display codes stored in the terminal display code stock data 2831. The acquisition can be done in order of oldest acquisition.

However, the display order is not limited to this. For example, the terminal display codes stored in the terminal display code stock data 2831 may be displayed from the left to the most recently acquired. You may or may not have to do it that way.
Further, the images may or may not be displayed in a completely random order.

<Effects of the third embodiment>
In the third embodiment, on the code display screen displayed on the display unit 24 of the terminal 20, a guide image based on the remaining number of codes (an example of information regarding the number, not a limitation) is displayed, and the display position of this guide image is displayed. As a standard, the entire image including the code image for terminal display is gradually enlarged to fill the display screen of the display unit 24 (not limited to, the number information is displayed at the position where it is displayed in the display area). An example of displaying the first code image in a nearby first area), and finally, when the size reaches the full display screen of the display unit 24, the expansion ends and the terminal display code image is displayed ( This is not a limitation, but is an example of displaying the first code image in the first area, and then displaying the first code image in the second area, which is further away from the position where the information regarding the number is displayed in the display area than the first area. ) shows the configuration.
As an example of the effect obtained by such a configuration, the terminal allows the user of the terminal to easily understand the correspondence between information regarding the number of first information stored in the storage unit and the displayed first information. (recognizable).

<Third modification (1)>
In the third embodiment, the display method when the terminal display code displayed on the code display screen is included in the count of remaining codes, but the terminal display code displayed on the code display screen is The same applies when excluding from counting.

As explained in the second modification (2), it is also conceivable to exclude the terminal display code displayed on the code display screen from counting the remaining code number and display the remaining code information.
In this case, it is necessary to inform the user that the terminal display code (code image) displayed on the code display screen is not included in the remaining number of codes. Therefore, by way of example and not limitation, the following display may be performed.

For example, if a method of displaying a rectangular guide image is applied as shown in FIG. The display screen is displayed at the center of the display screen, and guide images corresponding to the remaining number of codes counted after excluding one displayed terminal display code are displayed. At this time, the control unit 21 displays all guide images in a default state (does not highlight any guide images).

Furthermore, if a method of displaying a guide image simulating a two-dimensional code as shown in FIGS. 6-2 and 6-3 is applied, the control unit 21 may be configured to The code image of the code for use is displayed in the center of the code display screen, and guide images for the remaining number of codes counted after excluding the displayed one terminal display code are displayed. At this time, the control unit 21 displays all guide images in an inactive state (does not display any guide images in an active state).

More specifically, for example, if the remaining number of codes counted after excluding the terminal display code displayed on the code display screen is "5", a guide of "5" will be displayed in the above display mode. Display the image on the code display screen.

By doing this, the user can recognize that the displayed code image for terminal display does not correspond to the guide image (there is no correspondence relationship), and as a result, the displayed code (code image ) is not included in the number of remaining codes.

<Third modification (2)>
As described above, the terminal display code in the present disclosure can be used not only in an online state but also in an offline state. In the online state, the terminal 20 can receive a terminal payment completion notification from the server 10 immediately after the server 10 performs the payment. Therefore, by way of example and not limitation, after receiving the terminal payment completion notification, the terminal 20 can delete the data of the terminal display code used for the payment from the terminal display code stock data 2831.

However, in the offline state, the terminal 20 cannot receive the terminal payment completion notification from the server 10 until it returns to the online state, and therefore cannot know whether the server 10 has made the payment. Therefore, in the offline state, for example, even if the user of the terminal 20 uses one terminal display code displayed on the code display screen for payment (even if the store code reader device 50 reads it), the terminal 20 cannot delete the terminal display code. Therefore, for example, there is a possibility that the user of the terminal 20 may attempt to re-display the terminal display code once used for payment on the code display screen and use it for payment again.

Therefore, for example, on the code display screen shown in Figure 6-4, when the control unit 21 of the terminal 20 detects a swipe operation by the user and switches the display to the next terminal display code image, the code image is displayed before switching. The terminal display code data that was displayed may be deleted (discarded) so that it cannot be displayed again, or it may not be necessary to do so.

Note that this also applies to other display methods (for example, the display methods shown in FIGS. 6-1 to 6-3). In other words, for a terminal display code that has been displayed and then hidden, the data can be deleted so that it cannot be displayed again (that is, cannot be used for payment).

Further, as another method, the following can also be used.
When the terminal 20 detects that it is in an online state, it is possible to redisplay the terminal display code that has been displayed and then hidden without deleting it.
On the other hand, when the terminal 20 detects that it is offline, the terminal display code that was once displayed and then hidden is deleted so that it cannot be displayed again.

<Third modification (3)>
In addition to the various methods of displaying remaining code information described above, by way of example and not limitation, the user of the terminal 20 may perform a swipe operation (e.g. It is also possible to apply a display method in which when a user performs a flipping operation (by swiping from the bottom to the top), a page displaying the next terminal display code appears.

In addition, in this case, as in the third variation (2), once a page is turned, the terminal display code data displayed on the previous page is deleted so that it cannot be displayed again. You may or may not have to do so.

<Third modification (4)>
In the third embodiment, an example was shown in which a terminal display code image is displayed using a touch operation on a guide image as a trigger, but the present invention is not limited to this. Specifically, the various guide images mentioned above are used as information (remaining code information) that indicates the number of codes remaining (stock number), and an operation different from a touch operation on the guide image is used as a trigger to display the code image for terminal display. may or may not be displayed.

By way of example and not limitation, the terminal 20 displays a code display screen including code images for the remaining number of codes based on a touch operation of a code icon displayed on the top screen of the payment application. In this case, as an example and not a limitation, operation images such as buttons for displaying and switching code information (including code images and original information) and buttons for displaying and switching pages are also displayed on the code display screen. let

Then, each time the terminal 20 detects an operation (for example, a touch operation) on the above-mentioned operation image, the terminal 20 selects, by way of example and not limitation, a random order or an older one of the terminal display codes corresponding to the guide image. The code images for terminal display are displayed in order, and the display mode of the guide image is changed.

<Fourth Example>
The fourth embodiment is an embodiment related to replenishing the stock of terminal display codes stored in the terminal 20 and its user interface.

The content described in the fourth embodiment is applicable to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

<Processing>
FIG. 7-1 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. The left side shows the first terminal-side code replenishment process executed by the control unit 21 of the terminal 20, and the right side shows the first server-side code replenishment process executed by the control unit 11 of the server 10.

These processes are, by way of example and not limitation, processes that are executed as sub-processes (for example, executed in the background) of the payment application process of the terminal 20 described above and the payment management process of the server 10 described above. be.

First, the control unit 21 performs code replenishment condition determination processing (F110). As code replenishment conditions, the following conditions can be defined, for example.
(1) Detection of display and approval operation of zero code remaining information.
(2) Detection of code replenishment operation.
(3) The electromagnetic wave environment (communication environment) of the terminal has changed.
(4) Code update timing or update time has arrived.

Condition (1) is such that, after the control unit 21 displays the zero code remaining information on the display unit 24, if an approval operation by the user of the terminal 20 is detected for the zero code remaining information, the code is replenished. This is a condition that indicates that
Note that detection of an approval operation may not be included in the conditions. Specifically, when the control unit 21 causes the display unit 24 to display information on the number of remaining codes, the code may or may not be automatically replenished.

Condition (2) is a condition indicating that the code is to be replenished when an operation for replenishing the code by the user of the terminal 20 (hereinafter referred to as "code replenishment operation") is detected.

Condition (3) is a condition indicating that the code is to be replenished when the electromagnetic wave environment (communication environment) of the terminal 20 changes. Note that since radio waves are generally used for communication, it may be a change in the radio wave environment instead of a change in the electromagnetic wave environment.

As an example and not a limitation, if it is detected that the electromagnetic environment of the terminal 20 has changed from a "medium electromagnetic environment" to a "weak electromagnetic environment" based on the strength of the electromagnetic waves, there is a possibility that the terminal 20 will go into an offline state. It is possible to supplement the terminal display code.

Condition (4) is a condition that indicates that the code is to be replenished, for example, at regular timing (for example, once every 12 hours or 24 hours) or at a specific time (for example, midnight). .

In F110, the control unit 21 determines, by way of example and not limitation, whether at least one of the plurality of code replenishment conditions described above is satisfied.

Note that the above code replenishment conditions are merely examples, and conditions other than these may also be determined.
Also, by way of example and not limitation, a condition that is a combination of two or more of the above code replenishment conditions may be defined as the code replenishment condition.
Furthermore, by way of example and not limitation, the user of the terminal 20 may be allowed to select which of the above code replenishment conditions is to be applied.

If it is determined that the code replenishment condition is satisfied (F120: YES), the control unit 21 determines whether or not the online state is established (F130). If it is determined that the online state is established (F130: YES), the control unit 21 transmits code replenishment request information including at least the application ID to the server 10 via the communication I/F 22, by way of example and not limitation. F140).

Note that instead of the code replenishment request information, the code generation request information described above may or may not be transmitted from the terminal 20 to the server 10.

The control unit 11 of the server 10 determines whether code replenishment request information has been received from the terminal 20 (G110). If it is determined that the message has been received (G110: YES), a terminal display code generation process is performed (G120). Then, the control unit 21 transmits the generated terminal display code to the terminal 20 via the communication I/F 14 (G150).

Thereafter, the control unit 11 determines whether or not to end the process (G190), and if it is determined to continue the process (G190: NO), returns the process to G110. Furthermore, if it is determined that the process is to be terminated (G190: YES), the first server-side code replenishment process is terminated.

Further, if the code generation request information is not received from the terminal 20 (G110: NO), the control unit 11 shifts the process to G190.

When the terminal display code is received from the server 10 through the communication I/F 22 (F150), the control unit 21 adds and stores the received terminal display code to the terminal display code stock data 2831 (F160).

After that, the control unit 21 performs code replenishment notification processing (F170). In this code replenishment notification process, information notifying that the stock of terminal display codes has been replenished (hereinafter referred to as "code replenishment notification information") is displayed on the display unit 24.

Specifically, by way of example and not limitation, if the payment application is not being executed, the code replenishment notification information is displayed on the display unit 24 by means of a push notification associated with the payment application.
On the other hand, when the payment application is being executed, code replenishment notification information is displayed on a screen (for example, a code display screen) within the payment application.

Thereafter, the control unit 21 determines whether or not to end the process (F190), and if it is determined to continue the process (F190: NO), returns the process to F110. Furthermore, if it is determined that the process is to be terminated (F190: YES), the first terminal side code replenishment process is terminated.

Further, if it is determined that the code replenishment condition is not satisfied (F120: NO), or if it is determined that the online state is not established (F130: NO), the control unit 11 shifts the process to F190.

Note that the code replenishment request information may be information requesting replenishment of one terminal display code, but may also be information requesting replenishment of multiple (two or more) terminal display codes. Specifically, as an example and not a limitation, instead of replenishing the terminal display codes one by one, the number of codes that the terminal 20 requests replenishment at once on the terminal 20 side or the server 10 side. (The number of codes that the server 10 generates at one time for replenishment) is set in advance. Then, the user of the terminal 20 may replenish this upper limit number of terminal display codes at once with one operation. In this case, a plurality of terminal display codes are generated by the server 10, the generated plurality of terminal display codes are transmitted to the terminal 20, and the terminal 20 replenishes the received plurality of terminal display codes. do it.

<Display screen example>
FIG. 7-2 is a diagram showing an example of a code display screen in this embodiment.
Similar to the code display screen in Figure 6-3, this code display screen shows a two-dimensional code as an example of remaining code information above the area where the one-dimensional code image for terminal display is displayed. The guide image you created is displayed. In addition, on the right side of the area where the guide image is displayed, a code replenishment image indicated by a circle with a "+" character drawn inside is displayed as an example of an operation image for the user of the terminal 20 to perform a code replenishment operation. icon is displayed. When this code replenishment icon is touched by the user of the terminal 20, the stock of terminal display codes is replenished by the above process.

FIG. 7-3 is a diagram showing an example of a code replenishment notification in this embodiment.
On this code display screen, as an example of a code replenishment notification, the message "Code stock added. One code stock has been added." is displayed as a pop-up in the center of the screen along with an OK icon.

FIG. 7-4 is a diagram showing an example of a screen displayed when the OK icon in FIG. 7-3 is touched.
On this code display screen, as the stock of terminal display codes has been replenished, one terminal display code has been replenished to the right of the guide image that was displayed on the code display screen in Figure 7-1. One guide image corresponding to is additionally displayed. Further, the guide image corresponding to one additionally displayed terminal display code is displayed in an inactive state.

This means that information requesting replenishment of one terminal display code is sent from the terminal 20 to the server 10 as code replenishment request information, one terminal display code is generated by the server 10, and the generated one This is an example of a display screen when two terminal display codes are transmitted to the terminal 20 and one received terminal display code is supplemented at the terminal 20.

FIG. 7-5 is a diagram showing an example of a code replenishment notification in this embodiment.
On this code display screen, as an example of a code replenishment notification, the message ``Code stock addition 4 code stocks have been added.'' is displayed as a pop-up in the center of the screen along with an OK icon.

FIG. 7-6 is a diagram showing an example of a screen displayed when the OK icon in FIG. 7-5 is touched.
On this code display screen, since the stock of four terminal display codes has been replenished, the four terminal display codes that have been replenished are displayed on the right side of the guide image that was displayed on the code display screen in Figure 7-1. Four guide images corresponding to are additionally displayed. Further, the guide images corresponding to the four additionally displayed terminal display codes are displayed in an inactive state.

This means that information requesting replenishment of four terminal display codes is sent from the terminal 20 to the server 10 as code replenishment request information, and the server 10 generates four terminal display codes. This is an example of a display screen when four terminal display codes are sent to the terminal 20 and the four received terminal display codes are supplemented at the terminal 20.

In addition, for example, when the user of the terminal 20 performs a code replenishment operation to replenish codes, the user of the terminal 20 may be allowed to select the number of codes to be replenished.

FIG. 7-7 is a diagram showing an example of a code display screen in this case.
On this code display screen, the message "Add code stock. Please select the number of codes to stock." and the characters "Please select." for the user of the terminal 20 to select the number of codes to be stocked are input. box is displayed.

If you touch the box in which the words "Please select" have been entered, you can select the number of codes to be replenished in a drum roll manner, as shown in Figure 7-8. A drum roll containing possible chord numbers will be displayed. For example, when the user of the terminal 20 selects "2", "2" is entered and displayed in the box as shown in Figure 7-9, and the "OK" icon is touched. This adds two codes.

FIG. 7-10 is a diagram showing an example of a screen displayed when the OK icon in FIG. 7-9 is touched.
On this code display screen, since the stock of two terminal display codes has been replenished, the two replenished terminal display codes are displayed on the right side of the guide image that was displayed on the code display screen in Figure 7-1. Two guide images corresponding to are additionally displayed. Further, the guide images corresponding to the two additionally displayed terminal display codes are displayed in an inactive state.

<Effects of the fourth embodiment>
The fourth embodiment shows a configuration in which the terminal 20 changes the display mode of the remaining code number information by the control unit 21 based on reception of the terminal display code via the communication I/F 22.
As an example of the effect obtained by such a configuration, the terminal changes the display mode of information regarding the number of first information stored in the storage unit, so that, for example, the first information is replenished via the communication unit. It is possible to notify the user of the terminal that this has been done.

Further, in the fourth embodiment, the terminal 20 receives a code replenishment notification (not limited to this, but is an example of a notification indicating that the first information has been received) based on the reception of the terminal display code via the communication I/F 22. A configuration is shown in which the control section 21 performs this for the user of the terminal 20.
As an example of the effect obtained by such a configuration, the terminal can notify the user of the terminal that the first information has been received.

Further, in the fourth embodiment, the terminal 20 displays code generation request information or code replenishment request information (not a limitation, but an example of second information) on the display unit 24 based on information related to the remaining number of codes (not a limitation, but an example of second information). A configuration is shown in which an example of a request regarding transmission of first information is transmitted to the server 10 via the communication I/F 22.
As an example of the effect obtained by such a configuration, the terminal can transmit a request regarding transmission of the first information to the server based on the display of the second information, and can acquire the first information from the server.

<Fifth example>
The fifth embodiment is an embodiment that realizes replenishment of the stock of terminal display codes from an offline state.

The contents described in the fifth embodiment can be applied to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

In this embodiment, a state where the terminal 20 and the server 10 are unable to communicate using the first communication method described above is defined as an "offline state." Furthermore, it is assumed that the terminal 20 can communicate with the server 10 by using the second communication method described above.

<Processing>
FIGS. 8-1 and 8-2 are flowcharts showing an example of the flow of processing executed by each device in this embodiment. The left side shows the second terminal-side code replenishment process executed by the control unit 21 of the terminal 20, and the right side shows the first server-side code replenishment process executed by the control unit 11 of the server 10.
These processes are, by way of example and not limitation, processes that are executed as sub-processes (for example, executed in the background) of the payment application process of the terminal 20 described above and the payment management process of the server 10 described above. be.

The flowcharts in FIGS. 8-1 and 8-2 are obtained by adding processing (F210 to F280) in the case of F130: NO to the flowchart in FIG. 7-1.

If it is determined in F130 that the online state is not present (F130: NO), the control unit 21 determines whether the remaining number of codes is zero (F210).

If it is determined that the remaining number of codes is zero (F210: YES), the control unit 21 issues a zero remaining code notification and offline notification (F220). Specifically, as an example and not a limitation, information indicating that communication with the server 10 using the first communication method is impossible (offline state) is displayed on the display unit 24, along with information on the number of remaining codes being zero.

On the other hand, if it is determined that the remaining number of codes is not zero (F210: NO), the control unit 21 issues an offline notification (F230). Specifically, by way of example and not limitation, information indicating that communication with the server 10 using the first communication method is impossible (offline state) is displayed on the display unit 24.

After F220 or F230, the control unit 21 issues a code replenishment confirmation notification using the second communication method (F240). Specifically, as an example and not a limitation, information for confirming the intention of the user of the terminal 20 as to whether or not to communicate using the second communication method and replenish the terminal display code may be displayed on the display unit 24. let

Next, the control unit 21 determines whether or not the user of the terminal 20 has selected to perform code replenishment using the second communication method (F250), and if it is determined that it has been selected (F250: YES), the second communication method Communication using the communication method is attempted (F260).

If the communication using the second communication method is successful (F270: YES), the control unit 21 performs code replenishment processing (F280). Specifically, the above-mentioned code replenishment request information is transmitted to the server 10, a terminal display code is acquired from the server 10, and the terminal display code stock data 2831 is stored and replenished. The control unit 21 then moves the process to F190.

Note that in order to replenish the code using the second communication method, by way of example and not limitation, a wireless LAN (e.g., WiFi (registered trademark)), which is an example of the second communication method, may be used as an application that can cooperate with the payment application. A search application for searching for possible locations (spots) of stores, facilities, etc. is downloaded in advance by the terminal 20 and stored in the storage unit 28.

For example, when the user of the terminal 20 selects to perform code replenishment using the second communication method as a result of issuing the code replenishment confirmation notification using the second communication method of F240, the control unit 21 The stored search application may be activated to perform a process of searching for a spot where the second communication method can be used, or it may not be necessary to do so.

<Display screen example>
FIG. 8-3 is a diagram showing an example of a code display screen in this embodiment. On this code display screen, F220 in FIG. 8-2 is displayed by way of example and not limitation.
On this code display screen, the message "There are no codes remaining" is displayed as an example of information on the number of codes remaining, and the message "Currently offline" is displayed as an example of information indicating that communication with the server 10 using the first communication method is not possible. The message "Stock will be replenished when you go online." pops up in the center of the screen as a notification that there are zero codes remaining and as an offline notification. Further, an "OK" icon is displayed to indicate the intention to approve the content of the notification.

FIG. 8-4 is a diagram showing an example of a screen displayed when the "OK" icon is touched on the code display screen of FIG. 8-3. This screen is displayed at F240 in FIG. 8-2 by way of example and not limitation.
On this screen, as an example of information for confirming with the user of the terminal 20 whether or not to communicate using the second communication method and replenish the terminal display code, "Connect to a wireless network to obtain a code" is displayed. ” is displayed as a pop-up in the center of the screen as a code replenishment confirmation notification using the second communication method. Further, an "OK" icon for indicating an intention to approve the content of the notification and a "not now" icon for indicating an intention to not approve the communication content at this time are displayed.

When the "OK" icon is touched in FIG. 8-4, a screen as shown in FIG. 8-5 is displayed, for example.
On this screen, a selection box for selecting a wireless network is displayed in the center of the screen, and the user of the terminal 20 selects one candidate from among the wireless network candidates displayed in this selection box.

When a wireless network is selected in FIG. 8-5, communication via the selected wireless network is attempted. Then, when the communication is OK, a terminal display code is acquired from the server 10, and a screen as shown in FIG. 8-6, for example, is displayed.
In this display example, information requesting replenishment of five terminal display codes is sent from the terminal 20 to the server 10 as code replenishment request information, and the server 10 generates five terminal display codes. 5 terminal display codes are sent to the terminal 20, and the received 5 terminal display codes are replenished on the terminal 20. ” pops up in the center of the screen.

FIG. 8-7 is a diagram showing an example of a screen displayed when the OK icon in FIG. 8-6 is touched.
On this code display screen, since the stock of five terminal display codes has been replenished, five guide images corresponding to the five terminal display codes that have been replenished are displayed. Further, the terminal display code image corresponding to the leftmost guide image is displayed in the center of the screen, and the four guide images other than the leftmost guide image are displayed in an inactive state.

<Effects of the fifth embodiment>
In the fifth embodiment, information indicating that the terminal 20 is in an offline state (not a limitation, but an example of information indicating that communication by the terminal is not possible) is displayed on the code display screen. Then, the terminal 20 replenishes the code using the second communication method based on the touch operation by the user of the terminal 20 (not limited to, but an example of input by the terminal user) in response to the information indicating the offline state. This shows a configuration in which information about (not limited to, information about the communication settings of the terminal) is displayed on the code display screen.
As an example of the effect obtained by such a configuration, it is possible to notify the user of the terminal that communication by the terminal is not possible, and it is also possible to configure the communication settings of the terminal based on input by the terminal user. Thereby, for example, even if communication using the first communication method is impossible, it becomes possible to set the second communication method and communicate with the server using the second communication method.

1 communication system 10 server 20 terminal 30 network 40 store POS system 50 store code reader device 60 code register 70 store server

Claims (16)

A program executed by a terminal that executes processing related to payment based on first information for performing payment using a code image,
receiving a plurality of pieces of first information from a server via a communication unit of the terminal;
performing control to store the received plurality of first information in a storage unit of the terminal by a control unit of the terminal;
Displaying a first code image based on the first information in a display area of the terminal;
The terminal performs processing related to the payment by the control unit based on the display of the first code image in the display area,
Among the plurality of first information, the first information that can be used for the payment other than the first information based on the first code image displayed in the display area is not stored in the storage unit. , displaying in the display area a first display indicating that there is no first code image available for the payment other than the first code image displayed in the display area, and the first code image; is executed by the terminal. The program according to claim 1,
The first display includes textual information regarding the fact that the first code image is not available for the payment. The program according to claim 1,
The first display includes information indicating that the number of the first code images that can be used for the payment is one. 4. The program according to claim 3,
Displaying in the display area information regarding the number of pieces of first information that can be used for the payment stored in the storage unit among the plurality of pieces of first information,
The information regarding the number includes information on the first display. 5. The program according to claim 4,
The information regarding the number is displayed in a different manner based on the number of pieces of first information that can be used for the payment. The program according to claim 4 or claim 5,
Based on the reception of the first information via the communication unit, the terminal executes changing the display mode of the information regarding the number. The program according to any one of claims 1 to 6,
Based on the reception of the first information via the communication unit, the terminal may cause the control unit to notify a user of the terminal that the first information has been received. The program according to any one of claims 1 to 7,
Displaying the first display in the display area, and after processing regarding the payment, displaying in the display area second information regarding the fact that the first information that can be used for the payment is not stored in the storage unit. is performed on the terminal. 9. The program according to claim 8,
Based on the display of the second information, the terminal transmits a request regarding transmission of the first information to the server via the communication unit. The program according to any one of claims 1 to 9,
Displaying a second display indicating that communication by the terminal is not possible in the display area;
The terminal displays information regarding communication settings of the terminal in the display area based on an input by a user of the terminal on the second display. The program according to any one of claims 1 to 10,
Based on the processing related to the payment, the terminal performs control by the control unit to make the first information based on the first code image displayed in the display area unavailable. The program according to any one of claims 1 to 11,
The plural pieces of first information are transmitted from the server based on one operation on the terminal by a user of the terminal. The program according to any one of claims 1 to 12,
The plurality of pieces of first information include mutually different payment information. An information processing method for a terminal that executes processing related to payment based on first information for performing payment using a code image, the method comprising:
receiving a plurality of pieces of first information from a server via a communication unit of the terminal;
performing control to store the received plurality of first information in a storage unit of the terminal by a control unit of the terminal;
Displaying a first code image based on the first information in a display area of the terminal;
performing processing related to the payment by the control unit based on display of the first code image in the display area;
Among the plurality of first information, the first information that can be used for the payment other than the first information based on the first code image displayed in the display area is not stored in the storage unit. , displaying in the display area a first display indicating that there is no first code image available for the payment other than the first code image displayed in the display area, and the first code image; including. A terminal that executes processing related to payment based on first information for payment using a code image,
a communication unit that receives a plurality of pieces of first information from a server;
a control unit that performs control to store the received plurality of first information in a storage unit of the terminal;
a display unit that displays a first code image based on the first information,
The control unit executes processing related to the payment based on the display of the first code image on the display unit,
The display unit stores, in the storage unit, the first information that can be used for the payment, out of the plurality of first information, in addition to the first information based on the first code image displayed on the display unit. If not stored, a first display indicating that there is no first code image available for the payment other than the first code image displayed on the display unit, and the first code image are displayed. . A terminal that executes processing related to payment based on first information for payment using a code image,
comprising a processor that reads the program from a memory that stores the program and executes processing based on the program;
The processor includes:
receiving a plurality of pieces of first information from a server via a communication unit of the terminal;
storing the plurality of received first information in a storage unit of the terminal;
Displaying a first code image based on the first information in a display area of the terminal;
performing processing related to the payment based on displaying the first code image in the display area;
Among the plurality of first information, the first information that can be used for the payment other than the first information based on the first code image displayed in the display area is not stored in the storage unit. , displaying in the display area a first display indicating that there is no first code image available for the payment other than the first code image displayed in the display area, and the first code image; Execute.

Images