Program, information processing method, server

The server-based authentication method simplifies electronic payment transactions by confirming user authentication indirectly, addressing the cumbersome nature of existing methods and improving user convenience.

JP7594848B2Active Publication Date: 2024-12-05라인페이가부시키가이샤
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2018240336
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2018-12-21
Publication Date
2024-12-05
Estimated Expiration
2038-12-21

AI Technical Summary

Technical Problem

Existing electronic payment authentication methods using terminals, such as mobile phones, are cumbersome and not user-friendly, particularly in scenarios where quick and easy authentication is desired.

Method used

A server manages electronic money transactions by receiving payment information and authenticating the user without directly transmitting authentication details to the terminal, instead using alternative information to confirm user authentication and send payment information based on pre-established conditions.

Benefits of technology

This approach simplifies the authentication process, enhancing user convenience by allowing certain transactions to proceed without requiring explicit user authentication on the terminal, thus streamlining electronic payments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007594848000001
    Figure 0007594848000001
  • Figure 0007594848000002
    Figure 0007594848000002
  • Figure 0007594848000003
    Figure 0007594848000003
Patent Text Reader

Abstract

To provide an authentication method, a program and a server which are easy to use for the authentication of a user by a terminal in payment by electronic money.SOLUTION: Provided is an authentication method executed by a server that manages payment of electronic money by a terminal. This method includes: receiving, by a communication unit of the server, information that pertains to the payment of electronic money by the terminal; transmitting, by the communication unit, information that pertains to the authentication of the user of the terminal to the terminal; receiving, by the communication unit, information that indicates that the user of the terminal has been authenticated by the terminal; and transmitting, by the communication unit, payment information to the terminal that indicates that payment by electronic money has been made, on the basis of information that indicates that the user of the terminal has been authenticated. The payment information is transmitted to the terminal by the communication unit on the basis of acquisition of information that is different from authentication information for authenticating the user, while information pertaining to the authentication of the user of the terminal is not transmitted to the terminal by the communication unit.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to an authentication method, a program, and a server. [Background technology]

[0002] Recently, services that use terminals such as mobile phones to perform electronic payments have become widespread. For example, Patent Document 1 discloses a method of authentication by comparing secret code data inputted into a terminal with secret code data previously stored in the terminal. However, there are cases where authentication of a terminal user in electronic currency payments is inconvenient. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2002-176671 A Summary of the Invention

[0004] According to a first aspect of the present invention, a server that manages electronic currency settlement by a terminal Run Can program receiving information regarding electronic currency settlement by the terminal through a communication unit of the server; transmitting information regarding authentication of a user of the terminal to the terminal through the communication unit; receiving information indicating that the user of the terminal has been authenticated by the terminal through the communication unit; and transmitting payment information indicating that a settlement by electronic currency has been made based on the information indicating that the user of the terminal has been authenticated. Through By Shinbu On your device Sending and is executed by the server The payment information is transmitted to the terminal by the communication unit based on the acquisition of information different from authentication information for authenticating the user, without transmitting information regarding authentication of the user of the terminal to the terminal by the communication unit. According to a second aspect of the present invention, a server for managing electronic currency settlement by a terminal Information Processing Methodreceiving information regarding electronic currency settlement by the terminal through a communication unit of the server; transmitting information regarding authentication of a user of the terminal to the terminal through the communication unit; receiving information indicating that the user of the terminal has been authenticated by the terminal through the communication unit; and transmitting payment information indicating that a settlement by electronic currency has been made based on the information indicating that the user of the terminal has been authenticated. Through By Shinbu On your device The payment information is transmitted to the terminal by the communication unit based on acquisition of information other than authentication information for authenticating the user, without transmitting information regarding authentication of a user of the terminal to the terminal by the communication unit. According to a third aspect of the present invention, a server that manages electronic currency payments by a terminal comprises a communication unit that receives information regarding electronic currency payments by the terminal, transmits information regarding authentication of a user of the terminal to the terminal, receives information indicating that the user of the terminal has been authenticated by the terminal, and transmits payment information indicating that payment has been made by electronic currency to the terminal based on the information indicating that the user of the terminal has been authenticated, and a control unit that, based on acquisition of information other than authentication information for authenticating the user, controls the communication unit not to transmit information regarding the authentication of the user of the terminal to the terminal, and to transmit payment information to the terminal by the communication unit. [Brief description of the drawings]

[0005] [Figure 1] FIG. 1 illustrates an example of a configuration of a communication system according to an embodiment. [Diagram 2] FIG. 1 is a diagram illustrating an example of a system configuration of a store POS system according to an embodiment. [Figure 3-1] FIG. 2 is a diagram showing an example of functions realized by a control unit of the server according to the first embodiment. [Figure 3-2] FIG. 4 is a diagram showing an example of information stored in a storage unit of the server according to the first embodiment. [Figure 3-3] FIG. 4 is a diagram showing an example of user registration data according to the first embodiment. [Diagram 3-4] FIG. 2 is a diagram showing an example of store registration data according to the first embodiment. [Figure 3-5]FIG. 4 is a diagram showing an example of a payment management database according to the first embodiment. [Diagram 3-6] FIG. 2 is a diagram showing an example of functions realized by a control unit of the terminal according to the first embodiment. [Diagram 3-7] FIG. 4 is a diagram showing an example of information stored in a storage unit of the terminal according to the first embodiment. [Diagram 3-8] FIG. 4 is a diagram showing an example of authentication skip condition data according to the first embodiment. [Diagram 3-9] FIG. 4 is a diagram showing an example of terminal user data according to the first embodiment. [Figure 3-10] FIG. 11 is a diagram showing an example of authentication skip condition user setting data according to the first embodiment. [Figure 3-11] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-12] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-13] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-14] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-15] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-16] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-17] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-18] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-19] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-20] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-21] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-22] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-23] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-24]FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-25] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-26] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-27] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-28] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 3-29] 5 is a flowchart showing an example of a processing flow of the terminal, the store code reader device, and the server according to the first embodiment. [Figure 3-30] 5 is a flowchart showing an example of a processing flow of the terminal, the store code reader device, and the server according to the first embodiment. [Figure 3-31] 5 is a flowchart showing an example of a processing flow of the terminal, the store code reader device, and the server according to the first embodiment. [Figure 3-32] 5 is a flowchart showing an example of a processing flow of the terminal, the store code reader device, and the server according to the first embodiment. [Figure 3-33] 10 is a flowchart showing an example of the flow of a first authentication skip determination process according to the first embodiment. [Figure 3-34] FIG. 11 is a diagram showing an example of authentication skip condition data according to the first modified example. [Figure 3-35] 11 is a flowchart showing an example of the flow of processes performed by a terminal, a store code reader device, and a server according to a first modified example. [Figure 3-36] FIG. 13 is a diagram showing an example of a data configuration of a terminal-reading code management database according to a first modified example. [Figure 4-1] FIG. 11 is a diagram showing an example of functions realized by a control unit of a server according to the second embodiment. [Figure 4-2] FIG. 11 is a diagram showing an example of information stored in a storage unit of a server according to the second embodiment. [Figure 4-3] FIG. 11 is a diagram showing an example of authentication skip condition data according to the second embodiment. [Figure 4-4]10 is a flowchart showing an example of the processing flow of a terminal, a store code reader device, and a server according to the second embodiment. [Figure 4-5] 10 is a flowchart showing an example of the processing flow of a terminal, a store code reader device, and a server according to the second embodiment. [Figure 4-6] 10 is a flowchart showing an example of the processing flow of a terminal, a store code reader device, and a server according to the second embodiment. [Diagram 4-7] 13 is a flowchart showing an example of the flow of processes performed by a terminal, a store code reader device, and a server according to a second modified example. [Figure 4-8] 13 is a flowchart showing an example of the flow of processes performed by a terminal, a store code reader device, and a server according to a second modified example. [Figure 4-9] 13 is a flowchart showing an example of the flow of processes performed by a terminal, a store code reader device, and a server according to a second modified example. [Figure 5-1] FIG. 13 is a diagram showing an example of functions realized by a control unit of the server according to the third embodiment. [Figure 5-2] 13 is a flowchart showing an example of the processing flow of a terminal, a store code reader device, and a server according to the third embodiment. [Figure 5-3] 13 is a flowchart showing an example of the flow of processes performed by a terminal, a store code reader device, and a server according to a third modified example. [Figure 5-4] 13 is a flowchart showing an example of the flow of processes performed by a terminal, a store code reader device, and a server according to a third modified example. [Figure 6-1] FIG. 13 is a diagram showing an example of functions realized by a control unit of a server according to the fourth embodiment. [Figure 6-2] FIG. 13 is a diagram showing an example of information stored in a storage unit of a server according to the fourth embodiment. [Figure 6-3] FIG. 13 is a diagram showing an example of a data configuration of an IMS user management database according to the fourth embodiment. [Figure 6-4] FIG. 13 is a diagram showing an example of a data configuration of an IMS group management database according to the fourth embodiment. [Figure 6-5] FIG. 13 is a diagram showing an example of a data configuration of a remittance / receipt management database according to the fourth [Figure 6-6] FIG. 13 is a diagram showing an example of functions realized by a control unit of the terminal according to the fourth embodiment. [Figure 6-7] FIG. 13 is a diagram showing an example of information stored in a storage unit of a terminal according to the fourth embodiment. [Figure 6-8] FIG. 13 is a diagram showing an example of a data configuration of authentication skip condition data according to the fourth embodiment. [Figure 6-9] FIG. 13 is a diagram showing an example of the data configuration of remittance / received money data according to the fourth embodiment. [Figure 6-10] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-11] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-12] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-13] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-14] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-15] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-16] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-17] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-18] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-19] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-20] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-21] FIG. 13 is a view showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 6-22] 13 is a flowchart showing an example of a processing flow of a terminal and a server according to the fourth embodiment. [Figure 6-23] 13 is a flowchart showing an example of a processing flow of a terminal and a server according to the fourth embodiment. [Figure 6-24] FIG. 13 is a diagram showing an example of a data configuration of authentication skip condition data according to a fourth modified example. [Figure 6-25] 13 is a flowchart showing an example of a processing flow of a terminal and a server according to the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0006] <Compliance with legal matters> It should be noted that the disclosures described herein are subject to compliance with the laws of the country of implementation, such as communications secrecy, as necessary for the implementation of the disclosure.

[0007] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment for implementing an authentication method and the like according to the present disclosure will be described with reference to the drawings.

[0008] [System Configuration] FIG. 1 is a diagram illustrating an example of a configuration of a communication system 1 according to an embodiment of the present disclosure. As shown 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.

[0009] The server 10 provides a service that realizes transmission and reception of contents including messages between terminals 20 to terminals 20 owned by users via a network 30. The server 10 also provides a service (hereinafter referred to as a "payment service") that realizes electronic payment (not limited to this, but an example of payment) by communicating with the terminals 20. The number of terminals 20 connected to the network 30 is not limited.

[0010] 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. In other words, the network 30 refers to a communication network that provides connection paths so that the above-mentioned various devices can transmit and receive data after being connected.

[0011] One or more portions of network 30 may or may not be a wired or wireless network. Network 30 may include, by way of example and without limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular network, integrated service digital networks (ISDN), wireless LAN, long term evolution (LTE), code division multiple access (CDMA), Bluetooth, satellite communications, or the like, or a combination of two or more thereof. Network 30 may include one or more networks 30.

[0012] The terminal 20 (terminal 20A, terminal 20B, terminal 20C, ...) (not limited to, an example of a terminal or an information processing device) may be any terminal as long as it is an information processing terminal capable of realizing the functions described in each embodiment. The terminal 20 includes, not limited to, a smartphone, a mobile phone (feature phone), a computer (not limited to, for example, a desktop, a laptop, a tablet, etc.), a media computer platform (not limited to, for example, a cable or satellite set-top box, a digital video recorder), a handheld computer device (not limited to, for example, a PDA (personal digital assistant), an email client, etc.), a wearable terminal (a glasses-type device, a watch-type device, etc.), or other types of computers or communication platforms. The terminal 20 may also be expressed as an information processing terminal.

[0013] Since the configurations of the terminals 20A, 20B, and 20C are basically the same, the terminal 20 will be described below. In addition, as necessary, the terminal used by the user X will be expressed as the terminal 20X, and the user information in a predetermined service associated with the user X or the terminal 20X will be expressed as the user information X. Note that the user information is information of a user associated with an account used by the user in a predetermined service. The user information includes, by way of example and without limitation, information associated with a user, such as the user's name, the user's icon image, the user's age, the user's sex, the user's address, the user's hobbies and interests, and the user's identifier, which is input by the user or given by the predetermined service, and may be any one of these, or a combination thereof, or may not be the same.

[0014] The server 10 (not limited to, 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 device that can realize the functions described in each embodiment as an information processing device. The server 10 includes, not limited to, a server device, a computer (not limited to, for example, a desktop, a laptop, a tablet, etc.), a media computer platform (not limited to, for example, a cable or satellite set-top box, a digital video recorder), a handheld computer device (not limited to, for example, a PDA, an email client, etc.), or other types of computers or communication platforms. The server 10 may also be expressed as an information processing device. When it is not necessary to distinguish between the server 10 and the terminal 20, the server 10 and the terminal 20 may or may not be expressed as information processing devices.

[0015] In the embodiment described below, the server 10 is described as having a function of providing a messaging service (IMS (Instant Messaging Service)) and a function of providing a payment service.

[0016] In addition, the server having the function of providing IMS and the server having the function of providing payment services may be separate entities, and two servers, an IMS server and a payment server, may or may not be configured.

[0017] Also, as a non-limiting example, the business operator that operates server 10 is a company (e.g., company "X"), and the affiliated stores (affiliated stores) that are affiliated with the IMS operator are "Store S1," "Store S2," ...

[0018] The store POS system 40 is a POS system that is installed and used in a store that is affiliated with an IMS company. The 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.

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

[0020] (1) Terminal hardware configuration 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, a clock unit 29A, and a position calculation information detection unit 29B. The HW components of the terminal 20 are connected to each other via a bus B, for example and not for limitation. It is not essential that the HW configuration of the terminal 20 includes all of the components. For example and not for limitation, the terminal 20 may or may not be configured such that individual components, such as the microphone 25, the camera 27, or multiple components, are removable.

[0021] The communication I / F 22 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as the communication between the two devices is possible. 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. The communication I / F 22 also receives various data transmitted from various devices such as the server 10 and transmits it to the control unit 21. The communication I / F 22 may also be simply referred to as a communication unit. When the communication I / F 22 is configured with a physically structured circuit, it may also be referred to as a communication circuit.

[0022] The input / output unit 23 includes a device for inputting various operations to the terminal 20, and a device for outputting the results of processing performed by the terminal 20. The input / output unit 23 may be an integrated input unit and an output unit, or may be separate from the input unit and the output unit, or may not be.

[0023] The input unit is realized by any one or a combination of all kinds of devices that can receive input from a user and transmit information related to the input to the control unit 21. Examples of the input unit include, but are not limited to, hardware keys such as a touch panel, a touch display, and a keyboard, a pointing device such as a mouse, a camera (operation input via moving images), and a microphone (operation input by voice).

[0024] The output unit is realized by any one or a combination of all kinds of devices capable of outputting the processing results processed by the control unit 21. Examples of the output unit include, but are not limited to, a touch panel, a touch display, a speaker (audio output), a lens (for example, but not limited to, 3D (three dimensions) output and hologram output), a printer, etc.

[0025] The display unit 24 is realized by any one of all kinds of devices capable of displaying according to the display data written in the frame buffer, or a combination thereof. The display unit 24 includes, but is not limited to, a touch panel, a touch display, a monitor (for example, but not limited to, a liquid crystal display or an organic electroluminescence display (OLED)), a head mounted display (HDM), a projection mapping, a hologram, a device capable of displaying images, text information, and the like 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.

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

[0027] The clock unit 29A is a built-in clock of the terminal 20, and outputs time information (timekeeping information). The clock unit 29A is configured to have, for example and without limitation, a clock using a crystal oscillator, a clock using the NITZ (Network Identity and Time Zone) standard, etc. The clock unit 29A can also be expressed as a timekeeping unit or a time information detection unit, for example and without limitation.

[0028] The position calculation information detection unit 29B is a functional unit that detects (measures) information (hereinafter referred to as "position calculation information") necessary for the control unit 21 to calculate (measure) the position of its own terminal 20. The position calculation information detection unit 29B can also be expressed as a position calculation sensor unit, for example and without limitation.

[0029] The position calculation information detection unit 29B includes, by way of example and not limitation, a satellite positioning sensor (satellite positioning unit) 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), and an inertial measurement sensor (inertial measurement unit (IMU)) which is a sensor or unit for calculating the position of the terminal 20 using an inertial navigation system.

[0030] The satellite positioning unit includes, by way of example and not limitation, an RF receiving circuit that converts RF (Radio Frequency) signals, including positioning satellite signals transmitted from positioning satellites and received by an antenna (not shown), into digital signals, and a baseband processing circuit that performs correlation calculation processing or the like on the digital signals output from the RF receiving circuit to capture the positioning satellite signals, and outputs information such as satellite orbit data and time data extracted from the positioning satellite signals as information for position calculation.

[0031] The inertial measurement unit has an inertial sensor that is a sensor that detects information required to calculate the position of the terminal 20 by inertial navigation calculation. The inertial sensor includes, but is not limited to, a three-axis acceleration sensor and a three-axis gyro sensor, and outputs the acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor as information for position calculation.

[0032] The control unit 21 has a circuit physically structured to execute the functions realized by the code or instructions contained in the program, and is realized by a data processing device built into hardware, for example and without limitation. Therefore, the control unit 21 may or may not be expressed as a control circuit.

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

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

[0035] Terminal 20 stores program P in storage unit 28, and executes this program P, causing control unit 21 to execute processing as each unit included in control unit 21. In other words, program P stored in storage unit 28 causes terminal 20 to realize each function executed by control unit 21. Also, this program P may or may not be expressed as a program module.

[0036] The microphone 25 is used to input voice data, the speaker 26 is used to output voice data, and the camera 27 is used to obtain video data.

[0037] (2) Server hardware configuration FIG. 1 shows an example of the HW configuration of the server 10. As shown in FIG. The server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I / F 14 (interface), an input / output unit 12, a display 13, and a clock unit 19. The components of the HW of the server 10 are connected to each other via a bus B, for example and not for limitation. It is not essential that the HW of the server 10 includes all the components as the configuration of the HW of the server 10. For example and not for limitation, the HW of the server 10 may or may not be configured such that the display 13 is detachable.

[0038] The control unit 11 has circuits physically structured to execute functions realized by codes or instructions contained in a program, and is realized, for example and not by way of limitation, by a data processing device embedded in hardware.

[0039] The control unit 11 is typically a central processing unit (CPU), but may also be a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA, but is not limited to these in the present disclosure.

[0040] The storage unit 15 has a function of storing various programs and various data required for the operation of the server 10. The storage unit 15 is realized by various storage media such as an HDD, an SSD, and a 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.

[0041] The communication I / F 14 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as the communication between the two devices is possible. 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. The communication I / F 14 also receives various data transmitted from various devices such as the terminal 20 and transmits it to the control unit 11. The communication I / F 14 may also be simply referred to as a communication unit. When the communication I / F 14 is configured with a physically structured circuit, it may also be referred to as a communication circuit.

[0042] 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 of all types of devices that can receive input from a user and transmit information related to the input to the control unit 11, or a combination thereof. The input / output unit 12 is typically realized by 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, as non-limiting examples, a touch panel, a camera (operation input via moving images), or a microphone (operation input by voice). However, in the present disclosure, the input / output unit 12 is not limited to these.

[0043] The display 13 is typically realized by a monitor (for example, but not limited to, a liquid crystal display or an organic electroluminescence display (OLED)). The display 13 may or may not be a head mounted display (HDM) or the like. 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.

[0044] The clock unit 19 is a built-in clock of the server 10, and outputs time information (timekeeping information). The clock unit 19 is configured to include, for example and without limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, etc. The clock unit 19 can also be expressed as a timekeeping unit or a time information detection unit, for example and without limitation.

[0045] (3) Store POS system configuration 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 installed and used in a store that is affiliated with the business operator (IMS 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.

[0046] The store code reader device 50 is communicatively connected to the code register 60 and the store server 70 via a POS communication I / F 57 (by way of example and not limitation, a wired communication I / F or wireless communication I / F within the store), and reads a terminal display code displayed on the display unit 24 of the terminal 20 during a transaction at the code register 60. Then, based on having read the terminal display code, it sends information relating to the payment at the terminal 20 (by way of example and not limitation, payment request information, which will be described later) to the server 10 via the communication I / F 54, and receives information relating to the result of the payment at the server 10 (by way of example and not limitation, store payment result information, which will be described later) from the server 10 via the communication I / F 54.

[0047] The store code reader device 50 has, by way of example and not limitation, a control unit 51, an input / output unit 52, a display unit 53, a communication I / F 54, a memory unit 55, a sound output unit 56, a POS communication I / F 57, and a code reader 58.

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

[0049] The code register 60 is, by way of example and not limitation, communicatively connected to the store code reader 50 and the store server 70 via the POS communication I / F 57, and issues a receipt on which the total amount of the sold items is printed, based on the store payment result information acquired by the store code reader 50 from the server 10. 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.

[0050] The store server 70 manages various types of information, such as, for example and without limitation, store information about its own store, information about products sold at its own store, information about services provided at its own store, information about sales from the sale of products and provision of services at its own store, etc. 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.

[0051] The store server 70 does not necessarily need to be configured to be able to communicate directly with the store code reader device 50, but 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 result information acquired 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.

[0052] (4)Other The server 10 stores a program P in the storage unit 15, and by executing this program P, the control unit 11 executes the processes of each unit included in the control unit 11. In other words, 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.

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

[0054] The control unit 21 of the terminal 20 and / or the control unit 11 of the server 10 may or may not realize each process by a CPU having a control circuit, but may also realize each process by a logic circuit (hardware) formed in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) or a dedicated circuit. These circuits may or may not be realized by one or more integrated circuits, and the multiple processes shown in each embodiment may or may not be realized by one integrated circuit. Furthermore, an LSI may be called a VLSI, a super LSI, an ultra LSI, or the like, 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.

[0055] In addition, the program P (for example, but not limited to, a software program, a computer program, or a program module) of each embodiment of the present disclosure may or may not be provided in a state stored in a computer-readable storage medium. The storage medium can store the program P in a "non-transitory tangible medium." In addition, the program P may or may not be for realizing part of the functions of each embodiment of the present disclosure. Furthermore, the program P 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 in a storage medium.

[0056] 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 IC (ASIC)), a hard disk drive (HDD), a hybrid hard drive (HHD), an optical disk, an optical disk drive (ODD), a magneto-optical disk, a magneto-optical drive, a floppy diskette, a floppy disk drive (FDD), a magnetic tape, a solid state drive (SSD), a RAM drive, a secure digital card, or a drive, any other suitable storage medium, or a suitable combination of two or more of these. The storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate. It should be noted that the storage medium is not limited to these examples and may be any device or medium capable of storing the program P. In addition, the storage medium may or may not be referred to as a memory.

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

[0058] Furthermore, 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 capable of transmitting a program (such as a communication network or broadcast waves). The server 10 and / or the terminal 20 executes the program P downloaded via the Internet or the like, as a non-limiting example, to realize the functions of the multiple functional units shown in each embodiment. The same applies to other devices.

[0059] Furthermore, each embodiment of the present disclosure may also be realized in the form of a data signal embedded in a carrier wave in which the program P is embodied by electronic transmission. At least a part of the processing in the server 10 and / or the terminal 20 may or may not be realized by cloud computing configured with one or more computers. At least a part of the processing in the terminal 20 may or may not be configured to be performed by the server 10. In this case, at least a part of the processing of each functional unit of the control unit 21 of the terminal 20 may or may not be configured to be performed by the server 10. At least a part of the processing in the server 10 may or may not be performed by the terminal 20. In this case, at least a 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 judgment configuration in the embodiments of the present disclosure is not essential, and a specified process may or may not be executed when the judgment condition is satisfied, or a specified process may or may not be executed when the judgment condition is not satisfied.

[0060] Note that the programs of the present disclosure are implemented using, by way of example and not limitation, scripting languages ​​such as ActionScript and JavaScript (registered trademark), object-oriented programming languages ​​such as Objective-C and Java (registered trademark), and markup languages ​​such as HTML5.

[0061] First Embodiment In recent years, network services such as IMS and SNS (Social Networking Service) have become popular. "IMS" is a service that allows users of communication devices to send and receive messages between each other's communication devices in order to communicate with each other over the Internet. In this specification, the term "IMS" is used, which is an abbreviation for instant messaging service, but in a broad sense it means messaging services in general and is not limited to instant messaging services. "SNS" is a service that forms a social network or community on the Internet, primarily for the purpose of communication between users of communication devices. IMS can also be considered a form of SNS. For this reason, IMS and SNS may or may not be distinguished from each other.

[0062] Furthermore, in connection with these network services, applications (application software) for electronic payments are becoming widespread, and there are an increasing number of cases in which users of terminals 20 use applications for electronic payments to make payments at stores.

[0063] The first to third embodiments are, by way of example and not limitation, embodiments in which electronic payments are made using IMS payment application software (hereinafter simply referred to as the "payment application"), which is an application for electronic payments that is provided by an IMS operator and can be used by a user of terminal 20 as one function of IMS application software (hereinafter simply referred to as the "IMS application") or as an application that works in conjunction with the IMS application.

[0064] More specifically, in the first to third embodiments, when a user of terminal 20 purchases a product at a store or receives a service provided by the store, the user performs electronic payment using a payment application. At this time, authentication for electronic payment requested of the user on the terminal 20 side is skipped if a specific condition is met.

[0065] In the embodiments described below, unless otherwise specified, "payment" refers to "electronic payment" using a payment application. Additionally, unless otherwise specified, "authentication" means authenticating that the user of terminal 20 is a legitimate user in order to make a payment, and "authentication processing" means the processing for realizing this authentication for payment. Additionally, unless otherwise specified, "authentication skip conditions" refer to conditions for skipping the above-mentioned authentication processing for payment, and "skip authentication processing" means ignoring the processing command for the authentication processing and processing the next command, in other words, omitting the authentication processing. Furthermore, unless otherwise specified, "IMS money" refers to electronic currency that is managed by an IMS operator on server 10 and that can be used by a user of terminal 20 in a payment application.

[0066] Here, "electronic currency" refers to a payment method that uses information and communication technology and is an alternative to cash, provided by a business operator (an IMS business operator in the embodiment described below). As will be described later in a modified example, the electronic currency in this disclosure is not limited to IMS money, but can be understood to include a general concept of payment means that users can use as an alternative to cash. The contents described in the first embodiment are applicable to any of the other embodiments.

[0067] <Functional configuration> (1) Functional configuration of the server FIG. 3-1 is a diagram illustrating an example of functions realized by the control unit 11 of the server 10 in this embodiment. The server 10 has a server main processing unit 111, an IMS processing unit 112, and a payment management processing unit 113 as functions realized by the control unit 11.

[0068] The server main processing unit 111 has a function of executing server main processing, which is processing for comprehensively controlling the server 10 , in accordance with a server main processing program 151 stored in the storage unit 15 .

[0069] The IMS processing unit 112 has a function of executing IMS processing, which is processing for realizing transmission and reception of content including IMS messages and the like between terminals 20, in accordance with an IMS processing program 1512 stored in the storage unit 15.

[0070] The payment management processing unit 113 has a function of executing a payment management process, which is a process for executing and managing payments using IMS money, in accordance with a payment management processing program 1513 stored in the storage unit 15.

[0071] In this embodiment, it will be described that a user of terminal 20 can use a payment application stored in terminal 20 to make payments using two payment types, namely, "display terminal code" and "read terminal code", as examples and not limitations.

[0072] The payment type "terminal code display" is a payment type in which, when a user of terminal 20 makes a payment at a store, the user uses a payment application stored in terminal 20 to present a terminal display code displayed on terminal 20 to a store clerk at the store's code register 60, and has this terminal display code read by store code reader device 50 to make the payment.

[0073] The payment type "terminal code reading" is a payment type in which, when a user of terminal 20 makes a payment at a store, the user uses a payment application stored in terminal 20 to read a terminal reading code posted in a location such as the front of the store, around the code register 60, or in a display area corresponding to the type of product sold at the store (easy-to-understand examples include the bento area, beverage area, and food area), to make the payment.

[0074] In this embodiment, the terminal display code and the terminal read code are each represented by a two-dimensional code. A two-dimensional code is a display type code that has information in the horizontal and vertical directions, and includes a matrix type code (hereinafter referred to as a "matrix code") in which small squares are arranged vertically and horizontally, and a stack type code (hereinafter referred to as a "stack code") in which multiple one-dimensional codes (barcodes are used as an example and not a limitation) are stacked vertically.

[0075] In this embodiment, for the sake of simplicity, a QR code (registered trademark), which is an example of a widely used matrix code, will be described as an example of a terminal-displaying code and a terminal-reading code.

[0076] Unlike the present embodiment, a matrix code other than the QR code may or may not be used, such as an SP code, VeriCode, MaxiCode, CP code, or Chameleon code. Also, instead of a matrix code, various stack codes may or may not be used.

[0077] The payment management processing unit 113 includes, as functional units, a terminal display code generation processing unit 1131, a terminal display code transmission processing unit 1133, a store payment result information transmission processing unit 1136, and a terminal payment result information transmission processing unit 1137, but is not limited to these.

[0078] The terminal display code generation processing unit 1131 has a function of generating a terminal display code. Upon receiving terminal display code generation request information transmitted from the terminal 20, the terminal display code generation processing unit 1131 generates, as a terminal display code, a QR code including at least access information for accessing a payment page, which is one of the web pages provided by the server 10, and authentication information.

[0079] The access information includes, by way of example and not limitation, a URL (Uniform Resource Locator) for the store code reader device 50 that reads the terminal display code to access the payment page. This access information can also be expressed as a "link" or "link information." Hereinafter, the URL of the payment page will be referred to as the "payment page URL."

[0080] The authentication information includes, by way of example and not limitation, a token randomly issued by the server 10 as authentication information required by the server 10 to authenticate that the terminal 20 or a user of the terminal 20 is a genuine terminal 20 or a genuine user of the terminal 20.

[0081] The authentication information is information issued by a certification authority, and the token is authentication information issued by the server 10 acting as a certification authority to authenticate the terminal 20 or the user of the terminal 20.

[0082] The token in this embodiment can also be expressed as, for example, a "random token," an "access token," or a "payment token." In this embodiment, the token is issued randomly, so the token is different every time a terminal-display code is generated. For this reason, the token or the terminal-display code that includes this token functions as a one-time password.

[0083] In this embodiment, the terminal display code generation processing unit 1131 generates a one-dimensional code (a barcode, for example, not limited to) as well as a two-dimensional code (a QR code, for example, not limited to) as a terminal display code. This is because some stores may not support reading two-dimensional codes but may support reading one-dimensional codes.

[0084] Furthermore, in this embodiment, when the terminal display code generation processing unit 1131 generates a terminal display code, it associates this terminal display code with a validity period (for example, a period of "5 minutes" from the time of code generation) and transmits it to the terminal 20. If the terminal display code displayed on the terminal 20 within this validity period is read by the store code reader device 50, payment is possible, but if the terminal display code is read by the store code reader device 50 after the validity period has elapsed, it is necessary to reacquire the terminal display code. In other words, the terminal display code in this embodiment functions as a time-limited code.

[0085] On the other hand, the terminal reading code used for the payment type "terminal code reading" includes at least the payment page URL as access information for the terminal 20 that reads the terminal reading code to access the payment page.

[0086] In this embodiment, the terminal reading code will be described as including two types of terminal reading codes.

[0087] The first type of terminal-readable code (hereinafter referred to as the "first type of terminal-readable code") is a code used in various types of stores in Japan (a typical example is a Japanese convenience store) etc. As an example of a usage mode, this first type of terminal-readable code can be a code used to make a payment for a type of product sold at a store for a uniform price (fixed amount), such as a lunch box or a drink.

[0088] The first type terminal reading code may include, by way of example and not limitation, a payment page URL associated with the store that operates the first type terminal reading code and corresponding to the product or product type sold at that store.

[0089] For stores that use the first type terminal reading code, the server 10 stores and manages the product or product type, sales price, and payment page URL in association with the store's store ID (a non-limiting example of store identification information) of the store.

[0090] The second type of terminal read code (hereinafter referred to as the "second type terminal read code") is a special code that is used in certain stores overseas (a typical example is a food stall in China) and in electronic commerce using the Internet. This second type of terminal read code differs from the first type of terminal read code in that, as an example of a usage mode, the server 10 does not manage the product type or sales price, and the user of the terminal 20 can use the code to enter the price of the product to be purchased and make a payment.

[0091] The second type terminal reading code includes, by way of example and not by way of limitation, a payment page URL associated with and corresponding to the store that operates the second type terminal reading code.

[0092] For a store that uses the second type terminal reading code, the server 10 stores and manages, by way of example and not limitation, a payment page URL in association with the store ID of the store.

[0093] Unlike this embodiment, only one of the first type terminal reading code and the second type terminal reading code may be used as the terminal reading code. In other words, the terminal reading code is not divided into two types, and only the first type terminal reading code or only the second type terminal reading code may be used as the terminal reading code. In this case, configurations relating to terminal reading codes of types that are not applicable to the functions, data, processes, etc. described in this embodiment can be deleted.

[0094] FIG. 3-2 is a diagram illustrating an example of information stored in the storage unit 15 of the server 10 in this embodiment. In the storage unit 15, as a non-limiting example, a server main processing program 151 is stored as a program, which is read by the control unit 11 and executed as a server main processing. The server main processing program 151 also includes, as subroutine programs, an IMS processing program 1512 which is read by the control unit 11 and executed as IMS processing, and a payment management processing program 1513 which is executed as payment management processing. The settlement management process will be described in detail later using a flowchart.

[0095] Further, in the storage unit 15, as examples and not limitations, the following data are stored: user registration data 153, store registration data 155, a payment management database 157, and a code management database 159.

[0096] The user registration data 153 is registration data of the terminal 20 and the user of the terminal 20 who uses the payment service, and an example of the data configuration is shown in FIG. 3-3. In the user registration data 153, for example and not for limitation, a user name, a terminal phone number, a terminal email address, a user ID, an authentication password, and other registration information are stored in association with each other.

[0097] The user name is the name of the user of the terminal 20 who uses the payment service, and the name registered when the user of the terminal 20 uses the payment service is stored.

[0098] The terminal phone number is the phone number of the terminal 20 of the user of this user name, and the phone number of the terminal 20 registered when the user of the terminal 20 uses the payment service is stored. The terminal email address is the email address of the terminal 20 of the user of this user name, and the email address of the terminal 20 that the user of the terminal 20 registers when using the payment service is stored. 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").

[0099] The user ID is an ID that functions as identification information for identifying a user of the terminal 20, and is an ID that is uniquely set for a user who uses the payment application. As a non-limiting example, the user ID is set and stored by the server 10 as a unique ID for each user. The user ID is an example of identification information for identifying a user of the terminal 20 (hereinafter referred to as "user identification information").

[0100] The authentication password is an authentication password that the user is required to input when performing authentication processing for payment (hereinafter simply referred to as "authentication processing") on the terminal 20 of the user with this username, and the password set by the user is stored.

[0101] The other registration information is other registration information of the user of this username, and includes, by way of example and not limitation, a user icon image, which is image data of an icon used by the user in an IMS application, a user profile, and the like.

[0102] The above various types of user information can be stored and managed on the server 10 side as user information common to the IMS application and the payment application.

[0103] The store registration data 155 is registration data of stores that are affiliated with IMS businesses (payment service businesses), and an example of the data configuration is shown in FIG. 3-4. In the store registration data 155, a business type, a store name, store location information, store POS system information, a store ID, a first specific business type flag, and a second specific business type flag are stored in association with each other as store information.

[0104] The business type stores the business type of the store. Examples of the business type include, but are not limited to, "convenience store," "supermarket," "pharmacy," "pub," "department store," "restaurant," "bookstore," and "watch shop."

[0105] In the store name, for each business type, the store name of the store included (belonging) in that business type is stored.

[0106] 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 location of the store in two-dimensional or three-dimensional position coordinates, or may represent the location of the store in longitude and latitude (latitude, longitude, and in some cases altitude).

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

[0108] Since the store POS system 40 performs processing in cooperation with the server 10, as a non-limiting example, a software package for a payment service provided (distributed) by the server 10 can be acquired in advance and stored in the store code reader device 50 and the store server 70, and this software package can be called and used from a program for payment processing at the store. An application programming interface (API) is a typical example, and the store code reader device 50 can, for example, start the API to transmit information to the server 10 and receive information from the server 10.

[0109] In addition, the server 10 can receive information such as the store's business type, store name, store location information, store POS system information, etc. from the store server 70 of the store and store the information in the store registration data 155, without being limited thereto.

[0110] The store ID is an ID that functions as identification information for identifying a store with this store name. As a non-limiting example, the store ID is set and stored by the server 10 as a unique ID for each store. The store ID is an example of identification information for identifying a store (hereinafter, referred to as "store identification information").

[0111] The first specific business type flag is a flag indicating whether or not the business type is a first type of specific business type (hereinafter referred to as "first specific business type") that has been set in advance, with "ON" being stored for businesses that fall under the first specific business type, and "OFF" being stored for businesses that do not fall under the first specific business type. The first specific business type can be set in advance on the server 10 side, by way of example and not of limitation. In this example, "convenience store" and "supermarket", which are businesses that many users use on a daily basis, are set as the first specific business types.

[0112] The second specific business type flag is a flag indicating whether or not the business type is a second type of specific business type (hereinafter referred to as the "second specific business type") that has been set in advance, with "ON" being stored for businesses that fall under the second specific business type, and "OFF" being stored for businesses that do not fall under the second specific business type. The second specific business type can also be set in advance on the server 10 side, by way of example and not of limitation. In this example, a "pub", which is a business type with a high risk of a user misplacing the terminal 20, is set as the second specific business type.

[0113] The settlement management database 157 is a database that cumulatively stores data for managing information related to settlements by users of the terminals 20, and an example of the data configuration is shown in FIG. 3-5. The payment management database 157 stores payment management data generated for each terminal 20 or for each user of the terminal 20 .

[0114] Each payment management data includes, by way of example and not limitation, the user ID of the user of the terminal 20, the balance, IMS points, the daily upper limit amount, auto-charge settings, and payment history data.

[0115] In the user ID, the user ID stored in the user registration data 153 is stored. The balance field stores the latest value of the balance (remaining amount) of IMS money owned by the user with this user ID.

[0116] IMS points are points that can be accumulated through various IMS services and at affiliated stores that are affiliated with IMS operators. IMS points are, by way of example and not of limitation, worth 1 yen per point and can be exchanged for gift certificates, products, etc., or can be converted into cash in a payment application and used for payment.

[0117] The daily upper limit set amount field stores the upper limit amount per day that the user with this user ID can use for payment. The auto-charge setting is a setting for whether or not to automatically replenish (auto-charge) IMS money when the remaining balance is low (e.g., "500 yen") or "0 yen," and if auto-charge is set by the user of terminal 20, "ON" is stored, otherwise "OFF" is stored. As a non-limiting example, auto-charge can be performed from a bank account or the like registered by the user of terminal 20.

[0118] The payment history data is data relating to the payment history of the user with this user ID, and as an example, and not limited to, for the user with this user ID, the payment date and time, which is the date and time when the payment was made by server 10, the store ID, which is the ID of the store where the payment was made, the payment store name, which is the name of the store with that store ID, and the payment amount, which is the amount paid, are associated and stored in chronological order.

[0119] The code management database 159 is a database for managing terminal-displaying codes and terminal-reading codes, and includes a terminal-displaying code management database 1591 and a terminal-reading code management database 1593 .

[0120] The terminal display code management database 1591 is a database for managing terminal display codes, and by way of example and not limitation, stores data associating a user ID stored in the user registration data 153 with a token contained in a terminal display code generated for the terminal 20 of a user identified from the user ID.

[0121] In addition, instead of or in addition to the user ID, which is user identification information, terminal identification information such as a terminal telephone number stored in the user registration data 153 may or may not be stored in the terminal display code management database 1591.

[0122] The terminal reading code management database 1593 is a database for managing terminal reading codes, and by way of example and not limitation, data for managing first type terminal reading codes and data for managing second type terminal reading codes are stored.

[0123] Specifically, for the first type terminal reading code, as a non-limiting example, data is stored that associates, for each store ID, the product or product type sold at the store, the sales price, and the payment page URL. In this embodiment, since products are sold at a flat rate (fixed price) in stores that use the first type terminal reading code, data may be stored that associates the sales price with the payment page URL without associating the product or product type.

[0124] As for the second type terminal reading code, as a non-limiting example, data is stored that associates a payment page URL with each store ID.

[0125] In addition, instead of or in addition to the store ID, which is store identification information, store POS system information stored in store registration data 155, contact information such as the store's telephone number and store's email address, etc. may or may not be stored in terminal reading code management database 1593.

[0126] (2) Functional configuration of the terminal FIG. 3-6 is a diagram showing an example of functions realized by the control unit 21 of the terminal 20 in this embodiment. The terminal 20 has, as functions realized by the control unit 21, a terminal main processing unit 211, an IMS application processing unit 212, a payment application processing unit 213, and a position calculation processing unit 217.

[0127] The terminal main processing unit 211 has a function of executing terminal main processing, which is processing for comprehensively controlling the terminal 20, according to a terminal main processing program 281 stored in the storage unit 28. As a non-limiting example, when the terminal 20 is a mobile phone, the terminal main processing unit 211 controls calls to other mobile phones or fixed phones via the communication I / F 22, controls access to various websites via the communication I / F 22, controls displaying various information on the display unit 24, performs processing for analyzing various sound data input from the microphone 25, or performs processing for analyzing still images and moving images captured by the camera 27.

[0128] The IMS application processing unit 212 has the function of executing IMS application processing, which is processing for sending and receiving content with other users' terminals 20 via the server 10, based on the IMS application 282 stored in the memory unit 28.

[0129] The payment application processing unit 213 has a function of executing a payment application process, which is a process for communicating with the server 10 and making a payment, based on a payment application 283 stored in the storage unit .

[0130] The payment application processing unit 213 has a terminal display code acquisition processing unit 2131, a code reading processing unit 2133, an authentication skip determination processing unit 2135, and an authentication processing unit 2137 as functional units.

[0131] The terminal display code acquisition processing unit 2131 has a function of executing a process for acquiring a terminal display code from the server 10 in the case of the payment type "terminal code display".

[0132] The code reading processing unit 2133 has a function of executing a process for reading a terminal reading code posted in a store when the payment type is "terminal code reading".

[0133] The authentication skip determination processing unit 2135 has a function of executing an authentication skip determination process, which is a process for determining whether or not to skip the authentication process executed by the authentication processing unit 2137, in accordance with an authentication skip determination processing program 2845 stored in the memory unit 28.

[0134] In this embodiment, as an example and not a limitation, for the payment type “terminal code display”, the authentication skip determination processing unit 2135 executes the authentication skip determination processing at the timing after receiving the terminal display code from the server 10 based on the processing of the terminal display code acquisition processing unit 2131. In addition, as a non-limiting example, for the payment type "terminal code reading", the authentication skip determination processing unit 2135 executes the authentication skip determination processing at a timing after receiving information regarding the payment schedule (hereinafter referred to as "payment schedule information") from the server 10, based on the information contained in the terminal reading code read based on the processing of the code reading processing unit 2133. However, the timing for executing these authentication skip determination processes can be changed as appropriate.

[0135] The authentication processing unit 2137 has a function of performing authentication processing in accordance with an authentication processing program 2847 stored in the storage unit . In the authentication process, as a non-limiting example, a display process related to the execution of authentication for the user of terminal 20 is performed in which an authentication screen is displayed on display unit 24 to prompt the user of terminal 20 to input an authentication password, and it is determined whether the authentication password input on this authentication screen matches the registered authentication password.

[0136] The position calculation processing unit 217 has a function of executing a position calculation process, which is a process of calculating the position of its own terminal 20, based on the position calculation information output from the position calculation information detection unit 29B. The position calculation processing unit 217 performs satellite positioning calculation based on, for example, satellite orbit data and time data output from a satellite positioning sensor (satellite positioning unit) included in the position calculation information detection unit 29B, to calculate the position of its own terminal 20. The position calculation processing unit 217 also performs inertial navigation calculation based on information on acceleration and angular velocity output from an inertial measurement sensor (inertial measurement unit) included in the position calculation information detection unit 29B, to calculate the position of its own terminal 20.

[0137] Unlike this embodiment, and by way of example and not limitation, a processing device or arithmetic device (e.g., a CPU or DSP) may be provided in the position calculation information detection unit 29B, and the position calculation information detection unit 29B, rather than the control unit 21 of the terminal 20, may or may not calculate and output the position of the terminal 20.

[0138] Also, as a non-limiting example, a wireless device that enables terminal 20 to acquire location information, such as a beacon that transmits a beacon signal (a typical example is a Bluetooth signal), may be installed in an affiliated store, and terminal 20 may or may not acquire location information based on the beacon signal transmitted from the beacon installed in the store.

[0139] FIG. 3-7 is a diagram illustrating an example of information stored in the storage unit 28 of the terminal 20 in this embodiment. The memory unit 28 stores, by way of example and not limitation, a terminal main processing program 281 that is read by the control unit 21 and executed as terminal main processing, and a position calculation processing program 287 that is read by the control unit 21 and executed as position calculation processing.

[0140] In addition, in the storage unit 28, as examples and not limitations, an IMS application 282 and a payment application 283 are stored as application software acquired in advance from the server 10 by, for example, downloading. It should be noted that the IMS application 282 and the payment application 283 may be one application or separate applications.

[0141] In addition, the storage unit 28 stores, by way of example and not limitation, terminal data 286 and calculated position history data 288.

[0142] Terminal data 286 is data relating to this terminal 20, and includes, by way of example and not limitation, terminal identification information such as a terminal telephone number and a terminal email address, the lock setting "ON / OFF" on the OS side of terminal 20, a terminal unlock password for unlocking the OS side of terminal 20, and the authentication setting "ON / OFF" on the terminal side.

[0143] The calculated position history data 288 stores, by way of example and not limitation, a history of the position (hereinafter referred to as the "calculated position") of the terminal 20 calculated by the position calculation processing unit 217 performing position calculation processing at predetermined time intervals (for example, "every minute," "every five minutes," or "every ten minutes").

[0144] The payment application 283 includes a payment application program 284 that is read by the control unit 21 and executed as a payment application process, and payment application data 285 in which various data related to the payment application is stored.

[0145] The payment application program 284 includes, as subroutine programs, an authentication skip determination processing program 2845 that is read by the control unit 21 and executed as authentication skip determination processing, and an authentication processing program 2847 that is read by the control unit 21 and executed as authentication processing, and is not limited to this.

[0146] The payment application data 285 includes, by way of example and not limitation, authentication skip condition data 2851, payment data 2853, and store data 2855.

[0147] The store data 2855 stores, by way of example and not limitation, store information in which a business type stored in the store registration data 155 of the server 10 is associated with a first specific business type flag and a second specific business type flag.

[0148] This store data 2855 can be updated, for example, when the IMS application 282 or the payment application 283 is updated, by the latest store information being delivered from the server 10 to the terminal 20.

[0149] The authentication skip condition data 2851 is data in which authentication skip conditions, which are conditions for skipping the authentication process, are defined, and an example of the data configuration is shown in FIG. 3-8. The authentication skip condition data 2851 stores a condition category No. which is the category number of the authentication skip condition, a condition No. which is the number of the authentication skip condition included in the category of this condition category No., the authentication skip condition of this condition No., application / non-application indicating whether or not to apply this authentication skip condition for judgment, and the importance (priority) of this authentication skip condition in association with each other. Each authentication skip condition and its judgment method will be described in detail below.

[0150] <Condition Category No. "SP1"> Condition category No. "SP1" is a "time" category, and includes, by way of example and not limitation, authentication skip conditions of condition Nos. "SP1-1" and "SP1-2".

[0151] The authentication skip condition for condition No. "SP1-1" is set as "the current date and time is within a set time from the last payment date and time." "Last payment date and time" is the date and time when the last payment was made (the most recent date and time when the payment was made), regardless of whether the authentication process was skipped on the terminal 20. This means that if the current date and time is within a set time (e.g., "within one hour") from the last payment date and time, the payment will be made again soon, so authentication is omitted to improve user convenience.

[0152] In determining whether or not the authentication skip condition exists, as a non-limiting example, terminal 20 can obtain the current date and time based on the time measured by clock unit 29A and the last payment date and time stored in the payment history data of payment data 2853, and determine whether or not the current date and time is within a set time from the last payment date and time.

[0153] The authentication skip condition for condition No. "SP1-2" is set to "the current time is included in the set time period." The set time period can be set in advance by the user of terminal 20, without being limited thereto. Specifically, for example, the user of terminal 20 can set the time period during which he or she frequently makes payments as the set time period, thereby skipping authentication when making a payment during the set time period.

[0154] In determining whether or not the authentication skip condition exists, for example and without limitation, terminal 20 may obtain the current time based on the time kept by clock unit 29A and determine whether or not the current time is included in the set time period.

[0155] <Condition Category No. "SP2"> Condition category No. "SP2" is a category of "store / location", and includes, by way of example and not limitation, authentication skip conditions No. "SP2-1" to "SP2-4".

[0156] The authentication skip condition for condition No. "SP2-1" is set as "having previously performed a payment or authentication for a payment at the store where the payment is to be made." "Store where payment is planned" refers to a store where payment is planned to be made (a store where payment is not yet confirmed). In other words, if a payment or authentication for a store where payment is planned to be made has been made in the past, authentication will be omitted to improve user convenience.

[0157] In determining whether or not the authentication skip condition exists, terminal 20 can, by way of example and not limitation, obtain the history of calculated locations stored in calculated location history data 288, the latest calculated location, and the payment date and time stored in payment history data, and determine whether or not there is a calculated location that matches the latest calculated location among the calculated locations corresponding to the same date and time as the past payment date and time.

[0158] The authentication skip condition for condition No. "SP2-2" is set as "the store where payment is to be made is the set store." Basically, the set store can be set on the server 10 side. As a non-limiting example, the server 10 side can compile stores that are statistically frequently used by users and set them as set stores. This means that authentication is omitted in stores that are frequently used by users to improve user convenience.

[0159] It should be noted that the setting of the set store may be performed on the terminal 20 side, not on the server 10 side. For example, the user of the terminal 20 may set a store that the user uses frequently as the set store on the terminal 20. Also, for example, the user of the terminal 20 may set a store of a specific type (e.g., a convenience store) near the user's home as the set store as it is safe, but may not set other stores as it is risky.

[0160] In determining whether or not the authentication skip condition exists, terminal 20 can, by way of example and not limitation, obtain the history of calculated locations stored in calculated location history data 288, the payment store name stored in payment history data, and the store information stored in store data 2855, and determine whether or not there is a calculated location that matches the latest calculated location among the calculated locations that correspond to the same date and time as the past payment date and time at the set store.

[0161] The authentication skip condition for condition No. "SP2-3" is set as "the store where payment is to be made is a store of the first specific business type." As mentioned above, the first specific business types are defined as businesses that many users use on a daily basis, such as "convenience stores" and "supermarkets." This means that when payment is to be made at these stores, authentication is omitted to improve user convenience.

[0162] In determining whether or not the authentication skip condition exists, the terminal 20 can, by way of example and not limitation, obtain the history of calculated locations stored in the calculated location history data 288, the payment store name stored in the payment history data, and the first specific industry flag stored in the store data 2855, and determine whether or not there is a calculated location that matches the latest calculated location among the calculated locations that correspond to the same date and time as a past payment date and time at a store with the first specific industry flag set to “ON”.

[0163] The authentication skip condition for condition No. "SP2-4" is set to "more than a set time from the date and time of payment at a store of a second specific type of business." As described above, the second specific type of business can be set to a type of business where there is a high risk of the user misplacing the terminal 20, such as an "izakaya bar." The set time can be set to, for example, "3 hours," "6 hours," or "12 hours." This means that when a payment is made at a store where there is a high risk of the user misplacing the terminal 20, authentication is mandatory from the date and time of the payment until the set time has elapsed, but authentication is omitted if the set time has elapsed from the date and time of the payment.

[0164] In determining whether or not the authentication skip condition is met, terminal 20 can, by way of example and not limitation, obtain the current date and time based on the time measured by clock unit 29A, the payment date and time stored in the payment history data of payment data 2853 in memory unit 28, and the second specific industry flag stored in store data 2855, and determine whether or not the current date and time has exceeded a set time from the payment date and time at a store with the second specific industry flag set to “ON”.

[0165] <Condition Category No. "SP3"> Condition category No. "SP3" is a category of "amount", and includes, by way of example and not limitation, authentication skip conditions of condition Nos. "SP3-1" to "SP3-3".

[0166] The authentication skip condition for condition No. "SP3-1" is set as "the daily upper limit set amount is not exceeded." The "daily upper limit" is the upper limit set as a threshold for the total amount of payments already made in a day (amount already paid). In other words, if the total amount of payments already made in a day does not exceed the daily upper limit, authentication is omitted to improve user convenience.

[0167] Conversely, if the total amount of payments already made in a day exceeds the daily upper limit, authentication is required to warn users that they are spending too much money. Also, when minors make payments, parents can set restrictions on their use.

[0168] In determining whether or not the authentication skip condition exists, the terminal 20 can, by way of example and not limitation, obtain the daily upper limit set amount stored in the payment data 2853 and the total payment amount for that day identified from the payment history data, and determine whether or not the total amount exceeds the daily upper limit set amount.

[0169] The authentication skip condition for condition No. "SP3-2" is set as "the balance is equal to or less than a set amount (or is less than the set amount) and auto-charge setting is OFF." The set amount can be set in advance by the user of terminal 20, and is not limited to this example. This is because if the balance is equal to or less than the set amount (or is less than the set amount), the user cannot pay for high-priced items and the risk is considered to be low, so authentication is omitted to improve user convenience.

[0170] However, if the auto-charge setting is "ON", IMS money is automatically replenished, which allows the user to purchase expensive items, creating a risk. Therefore, the conditions for skipping authentication are that the balance is equal to or less than the set amount (or is less than the set amount) and that the auto-charge setting is "OFF".

[0171] In this case, if the auto-charge setting is "ON", in principle the authentication process will not be skipped even if the balance is equal to or less than the set amount (or less than the set amount). However, as described above, in order to improve user convenience, it is also possible to skip the authentication process even if the auto-charge setting is "ON". In this case, as a non-limiting example, the authentication skip condition for the above condition No. "SP3-2" can be set to "balance is equal to or less than the set amount (or less than the set amount)". In other words, even if the auto-charge setting is "ON", authentication process does not necessarily have to be mandatory. When the auto-charge setting is "ON", if the balance is equal to or less than the set amount (or less than the set amount), authentication process may or may not be performed.

[0172] In determining whether or not the authentication skip condition exists, the terminal 20 can, by way of example and not limitation, obtain the balance and auto-charge setting stored in the payment data 2853 and determine whether the balance is less than or equal to the set amount (or is less than the set amount) and the auto-charge setting is "OFF".

[0173] The authentication skip condition for condition number "SP3-3" is set as "payment frequency or payment amount per month is within an appropriate range." For example, the average, maximum, or most frequent monthly payment frequency over a specified period of the past (the past six months or the past year) is set as the threshold frequency, and the average, maximum, or most frequent monthly payment amount over the specified period of the past is calculated as the threshold amount. If the upcoming payment causes the payment frequency to exceed the threshold frequency or the payment amount to exceed the threshold amount, authentication will be performed, and authentication will be omitted in all other cases.

[0174] In determining whether or not the authentication skip condition exists, the terminal 20 can, by way of example and not limitation, obtain the payment frequency and payment amount calculated from the payment history data stored in the payment data 2853, and the threshold frequency and threshold amount stored in the memory unit 28, and determine whether the payment frequency exceeds the threshold frequency and whether the payment amount exceeds the threshold amount.

[0175] The above authentication skip condition may or may not be based on the number of times payments are made with IMS money (number of payments) rather than on the frequency of payments made with IMS money (payment frequency). Also, the payment frequency being within an appropriate range, the number of payments being within an appropriate range, and the payment amount being within an appropriate range may or may not be determined as separate conditions.

[0176] The authentication skip condition for condition No. "SP3-4" is set to "the planned payment amount is equal to or less than the set amount (or is less than the set amount)." The set amount can be set to a range that is not considered too high for a one-time payment in light of common sense or social conventions, such as "10,000 yen" or "20,000 yen." "Expected payment amount" means the amount to be paid in the future (amount not yet determined before payment). In other words, if the amount to be paid in the future is not so high, authentication is omitted to improve user convenience.

[0177] In determining whether or not the authentication skip condition exists, the terminal 20 can, by way of example and not limitation, obtain the planned payment amount from the server 10 and determine whether or not the planned payment amount is equal to or less than a set amount (or less than the set amount).

[0178] However, in this embodiment, for the payment type "display terminal code", the terminal 20 executes the authentication skip determination process at the timing after receiving the terminal display code from the server 10. However, at this timing, the terminal 20 has not yet acquired the planned payment information from the server 10, and the planned payment amount is unknown. For this reason, in this embodiment, the authentication skip condition of condition No. "SP3-4" is marked as "X" to indicate that it is not applicable for the payment type "display terminal code", and marked as "O" to indicate that it is applicable only for the payment type "read terminal code".

[0179] <Condition Category No. "SP4"> Condition category No. "SP4" is a category of "products", and includes, by way of example and not limitation, authentication skip conditions of condition Nos. "SP4-1" and "SP4-2".

[0180] The condition for skipping authentication for condition No. "SP4-1" is set as "the product to be purchased is a daily consumer good." "Products to be purchased" refers to products that are to be purchased through payment in the future (products that are not yet confirmed before payment). In other words, if the products to be purchased through payment in the future are daily necessities, authentication is omitted to improve user convenience.

[0181] The authentication skip condition for condition No. "SP4-2" is set to "there is a purchase history of the product to be purchased." This means that if the product to be purchased matches a product that the user of the terminal 20 has purchased more than once, authentication is omitted to improve user convenience.

[0182] To determine these authentication skip conditions, the terminal 20 needs to obtain information about the product to be purchased. However, in this embodiment, for both the payment types "display terminal code" and "read terminal code", information about the product to be purchased is not sent from the server 10 to the terminal 20. For this reason, the terminal 20 cannot determine the authentication skip conditions included in the condition category No. "SP4 (product)".

[0183] In this embodiment, for the payment type "terminal code reading", the success or failure of the authentication skip conditions of condition numbers "SP4-1" and "SP4-2" is determined using the method described below as an alternative method.

[0184] First, for the authentication skip condition of condition No. "SP4-1", the terminal 20 reads the terminal read code, then accesses the payment page based on the payment page URL included in the terminal read code, and acquires the store ID and sales amount associated with the payment page URL from the server 10. Then, the terminal 20 determines that the intended purchase item is a daily consumer good if the store identified from the store ID acquired from the server 10 is a store in a first specific industry and the sales amount is equal to or less than the threshold amount (or is less than the threshold amount).

[0185] Next, for the authentication skip condition of condition No. "SP4-2", the terminal 20 reads the terminal reading code, then accesses the payment page in the same manner as above, and obtains the store ID and sales amount associated with the payment page URL from the server 10. The terminal 20 then determines whether or not there is a payment store ID and payment amount stored in the payment history data that match the store ID and sales amount obtained from the server 10, and if there is a match, determines that there is a purchase history for the product to be purchased.

[0186] <Condition Category No. "SP5"> Condition category No. "SP5" is a "security" category, and includes, by way of example and not limitation, an authentication skip condition of condition No. "SP5-1".

[0187] The authentication skip condition for condition No. "SP5-1" is set to "terminal locked or payment application locked." This means that when the OS (Operating System) side of the terminal 20 is locked or the payment application side is locked, authentication such as inputting a terminal unlock password or a payment application unlock password is required to release these locked states. This means that authentication for payment is not required to improve user convenience.

[0188] In determining whether or not the authentication skip condition exists, terminal 20 can, by way of example and not limitation, obtain information on whether the OS side of terminal 20 is locked, which is stored in terminal data 286, and information on whether the payment application side is locked, which is stored in payment application data 285, and determine whether or not the terminal or the payment application is locked.

[0189] <Condition Category No. "SP6"> Condition category No. "SP6" is a category of "authentication settings", and includes, by way of example and not limitation, an authentication skip condition of condition No. "SP6-1".

[0190] The authentication skip condition for condition No. "SP6-1" is set as "authentication setting on the terminal side is OFF, or authentication setting on the payment application side is OFF." The terminal-side authentication is various types of authentication required of the user at the terminal 20, including user identity authentication, etc. The payment application-side authentication is authentication required of the user when making a payment using the payment application. This means that authentication is omitted if the user of terminal 20 has set terminal 20 to omit authentication, or if the payment application has set the payment application to omit authentication.

[0191] In determining the authentication skip condition, the terminal 20 can, by way of example and not limitation, obtain the terminal-side authentication setting stored in the terminal data 286 and the condition-specific setting flag for condition No. "SP6-1" stored in the authentication skip condition user setting data of the payment data 2853, and determine whether or not at least one of the terminal-side authentication setting and the payment application-side authentication setting is "OFF".

[0192] In addition, for each of the above authentication skip conditions, whether or not to apply the authentication skip condition and perform authentication skip determination is determined for each payment type.

[0193] Specifically, for the payment type "Display terminal code," by way of example and not limitation, the authentication skip conditions for condition No. "SP3-3," "SP3-4," "SP4-1," and "SP4-2" are marked as "X" indicating that they are not applicable, and the other authentication skip conditions are marked as "O" indicating that they are applicable.

[0194] The authentication skip condition for condition No. "SP3-3" is marked as not applicable "x" because, with the payment type "terminal code display", the terminal 20 cannot obtain information regarding the planned payment amount and cannot determine whether the planned payment amount is within an appropriate range. However, since it is possible to determine whether the payment frequency is within an appropriate range, the determination of whether the planned payment amount is within an appropriate range may or may not be omitted.

[0195] Similarly, the authentication skip condition for condition No. "SP3-4" is marked as "X" (not applicable) because terminal 20 cannot obtain information regarding the planned payment amount and cannot determine whether the planned payment amount is equal to or less than the set amount (or is less than the set amount).

[0196] In addition, the authentication skip conditions for condition No. "SP4-1" and "SP4-2" are marked as not applicable "X" because, as mentioned above, with the payment type "terminal code display", the terminal 20 cannot obtain information regarding the product to be purchased, and therefore cannot determine whether the product to be purchased is a daily consumer good, nor can it determine whether there is a purchase history for the product to be purchased.

[0197] On the other hand, for the payment type "Terminal code reading", as an example and not a limitation, in principle it cannot be applied to the authentication skip conditions of condition No. "SP4-1" and "SP4-2", but since it can be applied by the alternative method mentioned above, "× (◯)" is specified.

[0198] Also, for each of the above authentication skip conditions, an "importance" (which can also be called a "priority" indicating the degree to which the authentication skip condition is applied preferentially) is set for each payment type. The importance is expressed as a three-level scale, from "A" to "C," with "A" being the most important and "C" being the least important, by way of example and not of limitation.

[0199] Specifically, for the payment type "Display terminal code," by way of example and not limitation, the authentication skip conditions of condition numbers "SP1-1," "SP2-1," "SP2-4," "SP3-1," "SP3-2," "SP5-1," and "SP6-1" are assigned an importance level of "A," the authentication skip conditions of condition numbers "SP2-2" and "SP2-3" are assigned an importance level of "B," and the authentication skip condition of condition number "SP1-2" is assigned an importance level of "C." Additionally, the authentication skip conditions of condition numbers "SP3-3," "SP3-4," "SP4-1," and "SP4-2" are not applicable, and therefore an importance level of "- (none)" is assigned to them.

[0200] In addition, for the payment type "Terminal code reading," by way of example and not by way of limitation, an importance level of "A" is assigned to the authentication skip conditions of condition Nos. "SP2-1," "SP2-4," "SP3-4," "SP4-1," "SP4-2," and "SP6-1," an importance level of "B" is assigned to the authentication skip conditions of condition Nos. "SP1-1," "SP2-2," "SP2-3," "SP3-1," "SP3-2," and "SP5-1," and an importance level of "C" is assigned to the authentication skip conditions of condition Nos. "SP1-2" and "SP3-3."

[0201] The above-mentioned importance settings are merely examples, and the settings can be changed as appropriate. In the above, the applicability and importance are determined for each authentication skip condition (for each condition No.), but instead, the applicability and importance may or may not be determined for each category (condition category No.) of authentication skip conditions.

[0202] In this embodiment, the importance is set in association with the authentication skip condition, but this setting of the importance is not a mandatory requirement, and it is also possible not to set the importance. In other words, the authentication skip condition data 2851 does not have to have a column for the importance. In this case, in the authentication skip determination process, as a non-limiting example, the success or failure of the authentication skip conditions is determined in any order, and if any of the authentication skip conditions is satisfied, it is determined that the authentication process should be skipped.

[0203] The information indicated by the category of the authentication skip condition in the above authentication skip condition data 2851 and the information used to determine each authentication skip condition included in each category are included in information related to IMS money (not limited to, but an example of electronic currency).

[0204] Specifically, for example, the category "SP1 (time)" includes information about the time when a settlement was made with IMS money, and this information can be broadly considered as information about IMS money. For example, the category "SP2 (store / location)" includes information about the location where a payment was made with IMS money and information about the store where a payment was made with IMS money, and this information can be considered information about IMS money in a broad sense. Also, for example, the category "SP3 (amount)" includes information about the amount of IMS money, and this information can be said to be information about IMS money in a broad sense. Also, for example, the "SP4 (products)" category includes information about products purchased with IMS money, and this information can be broadly considered as information about IMS money.

[0205] The meaning of the term "information relating to..." is the same for other examples, so explanations for each will be omitted.

[0206] FIG. 3-9 is a diagram showing an example of the data configuration of the payment data 2853. As shown in FIG. The payment data 2853 stores the user ID, authentication password, a payment application unlock password which is a password for unlocking the locked state of the payment application, IMS points, balance, daily upper limit amount, auto-charge settings, payment history data, authentication skip condition settings, and authentication skip condition user setting data.

[0207] The payment history data stores data similar to the payment history data stored in the payment management data of this user ID managed in the payment management database 157 of the server 10. As a non-limiting example, after a payment is made by the server 10, the payment date and time, the payment store ID, the name of the payment store, and the payment amount are transmitted from the server 10 to the terminal 20, and the history is stored as the payment history data.

[0208] The authentication skip condition setting is a setting related to an authentication skip condition used for authentication skip determination by the own terminal 20. The authentication skip condition setting includes, by way of example and without limitation, "user setting" and "automatic setting".

[0209] The "user setting" is a setting for making an authentication skip determination by applying an authentication skip condition determined based on a selection / determination operation of the user of the terminal 20 from among the authentication skip conditions defined in the authentication skip condition data 2851. The "automatic setting" is a setting in which the terminal 20 performs authentication skip determination using an authentication skip condition that is automatically determined from among the authentication skip conditions defined in the authentication skip condition data 2851.

[0210] The authentication skip condition user setting data is setting data related to the above authentication skip condition setting "user setting", and an example of the data configuration is shown in FIG. 3-10. In the authentication skip condition user setting data, a condition category number, a condition number, a setting type, a condition category setting flag, and a condition setting flag are stored in association with each other.

[0211] The condition category number and condition number stored in the condition category number and condition number are those defined in the authentication skip condition data 2851, respectively.

[0212] As the setting type, either "by condition category" or "by condition" is stored. The setting type "by condition category" is a type for allowing the user of the terminal 20 to set an authentication skip condition to be applied by condition category. In other words, this setting type "by condition category" is used when setting to apply an authentication skip condition collectively for each category. The setting type "by condition" is a type for allowing the user of the terminal 20 to set an authentication skip condition to be applied by condition. In other words, this setting type "by condition" is used when setting to apply an authentication skip condition individually for each condition.

[0213] The condition category setting flag is a flag that indicates whether or not to apply the authentication skip condition included in the condition category number when the setting type is "condition category". For condition categories that are applied, "ON" is set in association with the condition category number, and for condition categories that are not applied, "OFF" is set in association with the condition category number.

[0214] The condition-specific setting flag is a flag indicating whether or not to apply the authentication skip condition of the condition No. when the setting type is "condition-specific", and for a condition to be applied, "ON" is set in association with the condition No., and for a condition not to be applied, "OFF" is set in association with the condition No. As a non-limiting example, for a category in which the condition category-specific setting flag is set to "ON", all the condition-specific setting flags are also set to "ON".

[0215] (3) Functional configuration of the store code reader device FIG. 2 shows an example of functions realized by the control unit 51 of the store code reader device 50 in this embodiment. The store code reader 50 has a store code reader main processing unit 511 and a store payment processing unit 513 as functions realized by the control unit 51.

[0216] The store code reader device main processing unit 511 has the function of executing store code reader device main processing, which is processing for comprehensively controlling the store code reader device 50, in accordance with a store code reader device main processing program 551 stored in the memory unit 55.

[0217] The store payment processing unit 513 has a function of executing store payment processing, which is processing related to payment at the store, in accordance with a store payment processing program 5511 stored in the storage unit 55.

[0218] FIG. 2 shows an example of information stored in the storage unit 55 of the store code reader device 50 in this embodiment. The storage unit 55 stores, by way of example and not limitation, a store code reader main processing program 551 which is read by the control unit 51 and executed as store code reader main processing. The store code reader main processing program 551 also includes, as a subroutine program, a store payment processing program 5511 which is read by the control unit 51 and executed as store payment processing. The store payment process will be described in detail later using a flowchart.

[0219] <Payment method> A payment method using the payment application in this embodiment will be described with reference to an example of a display screen displayed on the display unit 24 of the terminal 20.

[0220] (1) Payment type: "Display terminal code" 3-11 to 3-14 are screen diagrams for explaining the payment flow when the payment type "display terminal code" is selected and authentication skip is not performed.

[0221] FIG. 3-11 is a diagram showing an example of a payment application screen displayed on the display unit 24 of the terminal 20. As shown in FIG. This payment application screen is the display screen that appears when the payment application is launched, and the name of the payment application, "IMS Pay," is displayed at the top of the screen. In the box below that, the balance (here, "3,000 yen") is displayed, and next to that is a charge button for charging the amount. Also displayed below that are multiple function icons corresponding to various functions of the payment application.

[0222] Among these functional icons, the icon labeled "Code" is a "code icon" for obtaining a terminal display code from the server 10 when making a payment with the payment type "Display terminal code." Also, the icon labeled "Code reader" is a code reader icon for activating a code reader (hereinafter referred to as "application code reader") provided as a function of the payment application in order to read a terminal reading code on the terminal 20 when making a payment with the payment type "Read terminal code."

[0223] FIG. 3-12 is a diagram showing an example of an authentication screen that is displayed when the user of terminal 20 touches the "code icon" on the payment application screen. If it is not determined in the authentication skip determination process described later that the authentication process should be skipped, this authentication screen is displayed. This authentication screen displays the word "Password" (authentication password) along with the message "Please enter your current password." Below this is a password display field where the entered password is displayed, and a keyboard for entering the password.

[0224] FIG. 3-13 is a diagram showing an example of a terminal display code screen that is displayed when the authentication result is "OK" in the authentication process based on the password input on the above authentication screen. This terminal display code screen displays the word "Code" at the top of the screen, and below that, an IMS point tab for setting the payment method and whether or not to use IMS points for payment is displayed. Also below that, a terminal display code represented by a barcode and a terminal display code represented by a QR code are displayed as terminal display codes transmitted from the server 10 and received by the terminal 20. Also, as described above, a validity period is set for these terminal display codes, and the remaining time of the validity period is displayed in countdown form in association with the terminal display code.

[0225] The user of the terminal 20 presents the above-mentioned terminal display code screen to a store clerk at the code register 60 and makes a payment by having the store clerk read the terminal display code with the store code reader device 50. In this case, the store code reader device 50 accesses the payment page based on the payment page URL included in the read terminal display code and transmits the information required for the payment.

[0226] FIG. 3-14 is a diagram showing an example of a payment completion screen displayed on the terminal 20 when the payment by the server 10 is completed. On this payment completion screen, the words "Payment Completed" are displayed in the center of the terminal display code screen (Figure 3-13) in a pop-up format along with the message "You can check the details in 'Payment History'" and a "Confirmation icon" for checking the payment history.

[0227] Figures 3-15 and 3-16 are screen diagrams for explaining the payment flow when authentication skip is enabled for the "Display terminal code" payment type. Figure 3-15 shows the same payment application screen as Figure 3-11, and Figure 3-16 shows the same terminal display code screen as Figure 3-13.

[0228] When the "code icon" on the payment application screen in Fig. 3-15 is touched by the user of terminal 20, if it is determined in the authentication skip determination process described below that the authentication process should be skipped, the display will switch to the terminal display code screen in Fig. 3-16. In other words, the display will switch from the payment application screen to the terminal display code screen without displaying the authentication screen in Fig. 3-12.

[0229] (2) Payment type: "Terminal code reading" As mentioned above, there are two types of payment types for "Terminal code reading": reading a first-type terminal-readable code and reading a second-type terminal-readable code. We will explain each of these.

[0230] (2-1) Type 1 terminal reading code Figure 3-17 shows the same payment application screen as Figure 3-11, with the "code reader icon" among the function icons tapped. When the user taps the code reader icon, the application code reader is started, and a reading standby screen as shown in Fig. 3-18 is displayed on the display unit 24. In this state, if the user moves the terminal 20 so that the two-dimensional code is included within the frame in the center of the screen, the two-dimensional code is read by the application code reader.

[0231] Figure 3-19 is a diagram showing an example of a display screen displayed on the display unit 24 when a two-dimensional code is read by an application code reader, and shows the state in which a first type terminal reading code has been read by the application code reader. When the first type terminal reading code is read by the terminal 20, the terminal 20 accesses a payment page based on the URL included in the read first type terminal reading code, and transmits information required for payment.

[0232] FIG. 3-20 is a diagram showing an example of a payment page screen displayed on the display unit 24 of the terminal 20. As shown in FIG. At the top of this payment page, the store where the payment will be made (here, "XXX SHOP"), the date of the payment (here, "10 / 24 / 2018"), and the amount to be paid (here, "480 yen") are displayed. Below that are the payment method and an IMS points tab for setting whether or not to make the payment using IMS points. Also below that is a payment execution icon labeled "Make Payment" for executing the payment.

[0233] FIG. 3-21 is a diagram showing an example of a payment completion screen that is displayed when the user of the terminal 20 taps the payment execution icon on the payment page screen. On this payment completion screen, the words "Payment Completed" are displayed in a pop-up format in the center of the payment page, along with the message "You can check the details in your Payment History." and a confirmation icon for checking your payment history.

[0234] (2-2) Type 2 terminal reading code 3-22 to 3-24 show display screens similar to those shown in FIGS. 3-17 to 3-19. FIG. 3-25 is a diagram showing an example of a planned payment amount input setting screen that is displayed when the terminal 20 accesses the server 10 after reading the second type terminal reading code. This planned payment amount input setting screen displays the store where the payment is to be made (here, "XXX SHOP") along with an icon image of the user of terminal 20, and below that is a planned payment amount display field where the input planned payment amount is displayed, as well as the current balance and a keyboard for inputting the planned payment amount.

[0235] In this planned payment amount input setting screen, for example, as shown in Fig. 3-26, when the user of terminal 20 inputs the planned payment amount (here, "480 yen") and taps the "Complete icon" displayed below, the keyboard is hidden and a payment execution icon for executing the payment, indicated as "Make payment," is displayed, for example, as shown in Fig. 3-27. Then, when the user of terminal 20 taps the payment execution icon, a payment completion screen is displayed, for example, as shown in 3-28.

[0236] <Processing> 3-29 to 3-32 are flowcharts showing an example of the flow of processes executed by each device in this embodiment. These figures show, from left to right, a first payment application process which is an example of payment application processing executed by the payment application processing unit 213 of the terminal 20, a first store payment process which is an example of store payment processing executed by the store payment processing unit 513 of the store code reader device 50, and a first payment management process which is an example of payment management processing executed by the payment management processing unit 113 of the server 10.

[0237] Each step in each process is indicated by a combination of a capital letter and a number, and in this specification, the terminology for the step is omitted. Furthermore, the flowcharts described below are merely examples of the processing in this embodiment, and some steps in the flowcharts described below may not be executed, or additional steps may be inserted.

[0238] First, the payment application processing unit 213 of the terminal 20 accepts (A1) a user's terminal payment operation on the input / output unit 23. Then, the payment application processing unit 213 determines the payment type based on the accepted terminal payment operation (A3).

[0239] If the payment type is "terminal code display" (A3: terminal code display), the terminal display code acquisition processing unit 2131 transmits terminal display code generation request information including the user ID to the server 10 via the communication I / F 22 (A5).

[0240] The server 10 determines whether or not a request for generating a code for terminal display has been received from the terminal 20 via the communication I / F 14 (C1), and if it is determined that the request has been received (C1; Yes), the terminal display code generation processing unit 1131 performs a process for generating a code for terminal display (C3).

[0241] Specifically, as a non-limiting example, a random token is issued using a method (algorithm) for generating a random token. Then, a terminal display code including access information and the issued token is generated. More specifically, for example, data consisting of a URL character string of a website provided by the server 10 and a token character string (for example, a parameter portion beginning with a "?" symbol) is encoded (coded) and graphically converted to generate a terminal display code represented by an image of a two-dimensional code. Also, the user ID included in the received terminal display code generation request information is associated with the issued token and stored in the terminal display code management database 1591.

[0242] Next, the terminal display code transmission processing unit 1133 transmits the generated terminal display code to the terminal 20 via the communication I / F 14 (C5).

[0243] When the payment application processing unit 213 receives the terminal display code from the server 10 via the communication I / F 22 (A7), it executes a first authentication skip determination process in accordance with the authentication skip determination process program 2845 stored in the storage unit 28 (A9).

[0244] 3-33 is a flowchart showing an example of the flow of the first authentication skip determination process. Note that, in order to distinguish it from the authentication skip determination processes in the other embodiments, it will be referred to as "first authentication skip determination process" for convenience.

[0245] First, the authentication skip determination processing unit 2135 determines the payment type (D1). If the payment type is determined to be "terminal code display" (D1; terminal code display), the authentication skip determination processing unit 2135 determines the authentication skip condition setting stored in the payment data 2853 (D3).

[0246] If it is determined that the authentication skip condition setting is “user setting” (D3; user setting), the authentication skip determination processing unit 2135 determines the authentication skip condition to be applied based on the authentication skip condition user setting in the authentication skip condition user setting data stored in the payment data 2853 and the application / non-application specified in “Payment type: Terminal code display” in the authentication skip condition data 2851 (D5).

[0247] Specifically, as a non-limiting example, among the authentication skip conditions stored in association with "O" in the application / non-application of "Payment type: Terminal code display" in the authentication skip condition data 2851, the authentication skip conditions to be applied are determined to be those included in a condition category in which "By condition category" is stored in the setting type and "ON" is stored in the condition category setting flag in the authentication skip condition user setting data, and those authentication skip conditions in which "By condition" is stored in the setting type and "ON" is stored in the condition category setting flag.

[0248] Furthermore, if it is determined that the authentication skip condition setting is "automatic setting" (D3; automatic setting), the authentication skip determination processing unit 2135 determines the authentication skip condition to be applied based on the application or non-application and importance (priority) specified in "Payment type: Terminal code display" of the authentication skip condition data 2851 (D7).

[0249] Specifically, as a non-limiting example, among the authentication skip conditions stored in the authentication skip condition data 2851 with "O" associated with the application or non-application of "Payment type: Terminal code display", the authentication skip condition associated with, for example, "A" or "B" as the importance is determined to be the authentication skip condition to be applied.

[0250] On the other hand, if it is determined that the payment type is "terminal code reading" (D1; terminal code reading), the authentication skip determination processing unit 2135 determines the authentication skip condition setting stored in the payment data 2853 of the storage unit 28 (D9).

[0251] If it is determined that the authentication skip condition setting is “user setting” (D9; user setting), the authentication skip determination processing unit 2135 determines the authentication skip condition to be applied based on the authentication skip condition user setting of the authentication skip condition user setting data stored in the payment data 2853 and the application / non-application specified for the payment type: terminal code reading of the authentication skip condition data 2851 (D11).

[0252] Specifically, as a non-limiting example, among the authentication skip conditions stored in association with "O" in the application / non-application of "Payment type: Terminal code reading" in the authentication skip condition data 2851, the authentication skip conditions to be applied are determined to be those included in a condition category in which "By condition category" is stored in the setting type and "ON" is stored in the condition category setting flag in the authentication skip condition user setting data, and those authentication skip conditions in which "By condition" is stored in the setting type and "ON" is stored in the condition category setting flag.

[0253] Furthermore, if it is determined that the authentication skip condition setting is "automatic setting" (D9; automatic setting), the authentication skip determination processing unit 2135 determines the authentication skip condition to be applied based on the application or non-application and importance (priority) defined in "Payment type: Terminal code reading" in the authentication skip condition data 2851 (D13).

[0254] Specifically, as a non-limiting example, among the authentication skip conditions stored in the authentication skip condition data 2851 in association with "O" for the payment type: whether or not terminal code reading is applicable, the authentication skip condition associated with, for example, "A" or "B" for importance is determined to be the authentication skip condition to be applied.

[0255] After D5, D7, D11, or D13, the authentication skip determination processor 2135 acquires information necessary for determining whether each of the determined authentication skip conditions is satisfied (D15). The information necessary for determining whether each of the authentication skip conditions is satisfied and the method of determining the same are as described above.

[0256] Thereafter, the authentication skip determination processing unit 2135 performs a determination as to whether the authentication skip condition is satisfied (D17). Specifically, based on the information acquired in D15, the authentication skip determination processing unit 2135 determines whether each of the authentication skip conditions determined in D5, D7, D11, or D13 is satisfied. Then, for example, if at least one of the authentication skip conditions is satisfied, the authentication process is determined to be skipped, and otherwise the authentication process is determined not to be skipped. Then, the authentication skip determination processing unit 2135 ends the first authentication skip determination processing.

[0257] The above-described method of determining the authentication skip condition and the method of determining whether the authentication skip condition is satisfied are merely examples, and the method is not limited to these.

[0258] Specifically, by way of example and not limitation, only authentication skip conditions associated with importance level "A" may or may not be determined as authentication skip conditions to be applied. Also, authentication skip conditions with importance level "C" may or may not be included in the authentication skip conditions to be applied.

[0259] Also, as a non-limiting example, for an authentication skip condition associated with an importance level of "A", it is determined that the authentication process is skipped if at least one of the authentication skip conditions is satisfied, but for an authentication skip condition associated with an importance level of "B", it may or may not be determined that the authentication process is skipped if all of the authentication skip conditions are satisfied.

[0260] Returning to the main process, the payment application processing unit 213 determines whether or not a determination has been made to skip the authentication process in the first authentication skip determination process (A11). If it has been determined to skip the authentication process (A11; Yes), the payment application processing unit 213 proceeds to A19.

[0261] On the other hand, if it is determined that the authentication process is not to be skipped (A11: No), the authentication processing unit 2137 performs the authentication process (A13). Specifically, an authentication screen is displayed on the display unit 24, and the user is prompted to input an authentication password. Then, if the input authentication password matches the authentication password stored in the payment data 2853 of the storage unit 28, the authentication result is determined to be "OK". On the other hand, if the authentication passwords do not match, the authentication result is determined to be "NG".

[0262] If the authentication result is determined to be "NG" (A15; No), the payment application processing unit 213 executes error processing (A17). Specifically, for example, a notification is issued to prompt the user to re-enter the authentication password. Then, the payment application processing unit 213 returns the process to A13.

[0263] Thereafter, the payment application processing unit 213 causes the display unit 24 to display the terminal display code (A19). At this time, the payment application processing unit 213 may or may not display a message (code reading instruction display) or the like instructing the user of the terminal 20 to have the terminal display code read by the store code reader device 50 on the display unit 24 together with the terminal display code.

[0264] The store payment processing unit 513 of the store code reader device 50 accepts a store payment operation by a store clerk at the store via the input / output unit 52 (B1). Then, based on the accepted store payment operation, the store payment processing unit 513 determines whether the payment type is "display terminal code" (B3).

[0265] If the payment type is "Display terminal code" (B3; Yes), the store payment processing unit 513 performs a process to set the planned payment amount (B5). Specifically, based on the amount input operation by the store clerk into the input / output unit 52, the amount of the product to be sold is set as the "planned payment amount."

[0266] Thereafter, the store payment processing unit 513 issues a terminal display code read instruction notification (B7). Specifically, for example, the store clerk is notified by displaying a message instructing the user to read the terminal display code on the display unit 53 or by outputting a sound instructing the user to read the terminal display code from the sound output unit 56. In response to this terminal display code read instruction notification, the store clerk prompts the user of the terminal 20 to present the terminal display code.

[0267] When the terminal display code displayed on the display unit 24 of the terminal 20 in A19 is read by the code reader 58 of the store code reader device 50 (B9), the store payment processing unit 513 performs a code information acquisition process (B11). Specifically, the store payment processing unit 513 decodes (decodes) data from the read terminal display code to acquire various information contained in the read terminal display code.

[0268] Thereafter, the store payment processing unit 513 accesses the payment page via the communication I / F 54 based on the payment page URL obtained from the read terminal display code, and sends second payment request information to the server 10, including, by way of example and not limitation, the store ID, the token obtained from the terminal display code, and the planned payment amount set in B5 (B13).

[0269] When the payment management processing unit 113 receives the second payment request information from the store code reader device 50 via the communication I / F 14 (C9), it performs payment processing (C11). Specifically, as a non-limiting example, it identifies a user ID stored in the terminal display code management database 1591 of the storage unit 15 in association with the token included in the second payment request information received from the store code reader device 50. Then, it determines whether or not the planned payment amount can be paid based on the balance stored in the payment management data of the identified user ID in the payment management database 157 of the storage unit 15. If the payment is possible, it updates the balance by subtracting the planned payment amount, updates the payment history data, and sets the payment result as "success". On the other hand, if the payment is not possible, it sets the payment result as "failure". The settled amount is paid to the store directly by the IMS operator (the payment service operator) or through an agency.

[0270] Next, the payment management processing unit 113 judges the payment result (C13). If the payment result is "success" (C13; success), the store-use payment result information transmission processing unit 1136 transmits store-use payment success information as store-use payment result information to the store code reader device 50 via the communication I / F 14 (C15). Similarly, the terminal-use payment result information transmission processing unit 1137 transmits terminal-use payment success information as terminal-use payment result information to the terminal 20 via the communication I / F 14 (C17). Then, the payment management processing unit 113 ends the first payment management process.

[0271] On the other hand, if the payment result is "failed" (C13; failed), the store-use payment result information transmission processing unit 1136 transmits store-use payment failure information as store-use payment result information to the store code reader device 50 via the communication I / F 14 (C19). Similarly, the terminal-use payment result information transmission processing unit 1137 transmits terminal-use payment failure information as terminal-use payment result information to the terminal 20 via the communication I / F 14 (C21). Then, the payment management processing unit 113 ends the first payment management process.

[0272] When the store payment processing unit 513 receives store payment result information from the server 10 via the communication I / F 54 (B15), it determines the payment result (B17), and if the payment result is "success" (B17; success), it performs a payment success notification process (B19). Then, the store payment processing unit 513 ends the first store payment process.

[0273] On the other hand, if the payment result is "failed" (B17; failed), the store payment processing unit 513 performs a payment failure notification process (B21). Then, the store payment processing unit 513 ends the first store payment process.

[0274] When the payment application processing unit 213 receives terminal payment result information from the server 10 via the communication I / F 22 (A21), it determines the payment result (A23), and if the payment result is “successful” (A23; success), it performs payment success notification processing (A25).

[0275] Thereafter, the payment application processing unit 213 determines whether or not to display the payment history (A27). Specifically, as a non-limiting example, when a user's operation to check the payment history is detected on the input / output unit 23, it is determined that the payment history is to be displayed.

[0276] If it is determined that the payment history is to be displayed (A27; Yes), the payment application processing unit 213 performs a payment history display process (A29). Then, the payment application processing unit 213 ends the first payment application process.

[0277] On the other hand, if the payment result is "failed" (A23; failed), the payment application processing unit 213 performs a payment failure notification process (A26). Then, the payment application processing unit 213 ends the first payment application process.

[0278] Next, if it is determined in A3 that the payment type is “terminal code reading” (A3; terminal code reading), the code reading processing unit 2133 launches an application code reader in accordance with user operation and performs processing to read the terminal reading code (first type terminal reading code or second type terminal reading code) (A31).

[0279] Thereafter, the payment application processing unit 213 performs a code information acquisition process (A33). Specifically, the payment application processing unit 213 decodes (decodes) data from the terminal reading code read by the application code reader, and acquires various pieces of information contained in the terminal reading code.

[0280] Thereafter, the payment application processing unit 213 accesses the payment page via the communication I / F 22 based on the payment page URL obtained from the read terminal reading code (A35).

[0281] The payment management processing unit 113 judges the payment schedule information in response to the access to the payment page from the terminal 20 (C33). Specifically, it refers to the terminal reading code management database 1593 and acquires the information stored in association with the payment page. Then, the payment management processing unit 113 transmits the payment schedule information according to the judgment result to the terminal 20 via the communication I / F 14 (C35).

[0282] In this case, if the information associated with the payment page is information about a store that uses a first type terminal reading code, the payment management processing unit 113 sends first type planned payment information, including the store where the payment is to be made and the planned payment amount, to the terminal 20 via communication I / 14. On the other hand, if the information associated with the payment page is information about a store that uses a second type terminal reading code, the payment management processing unit 113 sends second type planned payment information, including the store where the payment is to be made (but not the planned payment amount), to the terminal 20 via communication I / 14.

[0283] When the payment application processing unit 213 receives payment schedule information from the server 10 via the communication I / F 22 (A37), it determines the type of the received payment schedule information (A39). If the type of the payment schedule information is "type 2 payment schedule information" (A39; type 2), it performs a payment schedule amount setting process (A41). Specifically, based on the amount input operation by the user of the terminal 20 to the input / output unit 23, it sets the total amount of the products to be purchased as the "payment schedule amount".

[0284] After A41, or if the type of payment schedule information is "second type payment schedule information" (A39; first type), the payment application processing unit 213 executes the first authentication skip determination process (A9) in accordance with the authentication skip determination process program 2845 stored in the storage unit 28. Then, the payment application processing unit 213 executes the processes of A11 to A17.

[0285] After that, the payment application processing unit 213 sends first payment request information including, by way of example and not limitation, the user ID and payment confirmation information on the payment page to the server 10 (A43). However, if the process of A41 has been executed, the first payment request information also includes the set planned payment amount and sends it to the server 10. Then, the payment application processing unit 213 performs the processes from A21 onwards.

[0286] When the payment management processing unit 113 receives the first payment request information from the terminal 20 via the communication I / F 14 (C37), it performs the payment process (C11). Then, the payment management processing unit 113 proceeds to the process from C13 onwards.

[0287] If it is determined in B5 that the payment type is not "terminal code display" (B3; No), the store payment processing unit 513 proceeds to B15. The case where the payment type is not "display terminal code" is the case where the payment type is "read terminal code." In this case, as a non-limiting example, a store clerk instructs the user of terminal 20 to read the terminal read code, and the user of terminal 20 launches the application code reader of terminal 20 to read the terminal read code.

[0288] As described above, it is also possible to use only one type of code out of the first type terminal reading code and the second type terminal reading code as the terminal reading code. In this case, only one type of payment schedule information is sent from the server 10 to the terminal 20 in step C35 of Figure 3-31, and there is no need for the terminal 20 to determine the type of payment schedule information, so step A39 of Figure 3-31 can be deleted. Furthermore, if only the first type terminal reading code is applied, there is no need to set the payment amount on the terminal 20, so step A41 in FIG. 3-31 can also be deleted.

[0289] <Advantages of the First Embodiment> The first embodiment shows a configuration in which the terminal 20 performs an authentication process (not limited to, an example of a display process) for electronic payment (not limited to, an example of payment) for the user of the terminal 20, and receives information related to payment by IMS money (not limited to, an example of electronic currency) via the communication I / F 22 (not limited to, an example of a communication unit of the terminal) based on the result of the authentication process, and acquires information other than an authentication password (not limited to, an example of authentication information for authenticating the user of the terminal).Then, the terminal 20 makes an authentication skip determination based on the acquired information, and if the authentication skip condition is established, the authentication process is not performed, and information on the payment result by the server 10 (not limited to, an example of information related to payment by electronic currency) is received via the communication I / F 22. As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can easily receive information related to the payment with electronic currency without performing display processing related to the execution of authentication for the user of the terminal. Also, when making a payment with electronic currency, the terminal can obtain information other than the authentication information for authenticating the user of the terminal, and thus can reduce the processing load of the terminal since it is not necessary to perform display processing. Also, when making a payment with electronic currency, since it is not necessary to perform display processing each time, the payment can be made quickly and smoothly, and the convenience of the user can be improved.

[0290] In addition, the first embodiment shows a configuration in which information different from the above authentication password (not limited to, an example of information different from authentication information) includes information about IMS money (not limited to, an example of information about electronic currency). One example of the effect obtained by such a configuration is that when making a payment with electronic currency, the terminal can obtain information about the electronic currency and thereby avoid having to perform display processing regarding the execution of authentication for the user of the terminal, thereby reducing the processing load on the terminal.

[0291] In addition, the first embodiment shows a configuration in which the information regarding the above-mentioned IMS money includes information regarding the amount of IMS money associated with the terminal 20 or the user of the terminal 20 (not limited to, an example of information regarding the amount of electronic currency associated with the terminal or the user of the terminal). As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information regarding the amount of the electronic currency, and thus can reduce the processing load of the terminal since it does not need to perform display processing regarding the execution of authentication for the user of the terminal. Also, since the information regarding the amount of the electronic currency is associated with the terminal or the user of the terminal, the terminal can appropriately perform processing related to the payment based on the information regarding the appropriate amount of the electronic currency.

[0292] Moreover, in the first embodiment, the information on the amount of IMS money includes information on a daily upper limit set amount (not limited to this, but an example of information on a set amount of electronic currency). As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information regarding the set amount of the electronic currency, thereby eliminating the need to perform display processing regarding the execution of authentication for the user of the terminal, thereby reducing the processing load on the terminal.

[0293] Furthermore, the first embodiment shows a configuration in which the terminal 20 does not perform authentication processing until the daily upper limit set amount (not a limitation, but an example of the set amount) is exceeded. As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal does not display a message regarding the execution of authentication until the set amount of the electronic currency is exceeded, thereby reducing the processing load on the terminal and improving user convenience. On the other hand, when making a payment with electronic currency, if the set amount is exceeded, a message regarding the execution of authentication may be displayed, thereby alerting the user that the set amount has been exceeded.

[0294] In addition, the first embodiment shows a configuration in which the information regarding the amount of IMS money includes information regarding the balance of IMS money associated with the terminal 20 or the user of the terminal 20 (not limited to this, an example of information regarding the balance of electronic currency associated with the terminal or the user of the terminal). As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information regarding the balance of the electronic currency, and thus can reduce the processing load of the terminal since it does not need to perform display processing regarding the execution of authentication for the user of the terminal. Also, since the information regarding the balance of the electronic currency is associated with the terminal or the user of the terminal, the terminal can appropriately perform processing related to the payment based on the information regarding the appropriate balance of the electronic currency.

[0295] Moreover, the first embodiment shows a configuration in which the terminal 20 does not perform authentication processing when the balance of IMS money is equal to or less than a set amount. As an example of the effect obtained by such a configuration, when making a payment with electronic currency, if the balance of the electronic currency is equal to or less than a set amount, the terminal does not display a message regarding the execution of authentication, thereby reducing the processing load of the terminal. Also, for example, when the balance of electronic currency is low, a large amount of payment cannot be made and the risk is considered to be low, so by not displaying a message regarding the execution of authentication, it is possible to improve user convenience while ensuring safety.

[0296] In addition, the first embodiment shows a configuration in which, when an auto-charge setting (not limited to, a setting in which electronic currency is automatically deposited into the terminal) is configured on the terminal 20, authentication processing is performed when the balance of IMS money is equal to or less than the set amount. As an example of the effect obtained by such a configuration, if the terminal is set to automatically deposit electronic money when the electronic money in the terminal falls below a set amount or falls below the set amount, the electronic money is automatically deposited in the terminal when the amount becomes small, which makes it possible to make large payments and creates a risk. Therefore, by displaying a message regarding the execution of authentication, it is possible to alert the user that large payments will be possible.

[0297] Furthermore, the first embodiment shows a configuration in which the information relating to IMS money includes information relating to the frequency or number of times payments were made using IMS money (without being limited to this, information relating to the frequency or number of times payments were made using electronic currency). As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information regarding the frequency or number of times that a payment has been made with electronic currency, thereby eliminating the need to perform display processing related to the execution of authentication for the user of the terminal, thereby reducing the processing load on the terminal. Also, for example, when payments have been made with electronic currency frequently or many times, it is highly likely that the same user is also making payments with electronic currency and the risk is considered to be low, so by not performing display processing, it is possible to improve user convenience while ensuring safety.

[0298] Moreover, in the first embodiment, the information on IMS money includes information on the date and time of the final settlement using IMS money (not limited to this, but an example of information on the time when settlement was made using electronic currency). One example of the effect that can be obtained by such a configuration is that, when making a payment with electronic currency, the terminal obtains information regarding the time when the payment was made with electronic currency, thereby eliminating the need to perform display processing regarding the execution of authentication for the user of the terminal, thereby reducing the processing load on the terminal.

[0299] Moreover, the first embodiment shows a configuration in which the terminal 20 does not perform authentication processing if it is within a set time from the date and time of the final settlement using IMS money. As an example of the effect obtained by such a configuration, when a payment is made with electronic currency, if a set time has passed since the time the payment was made with electronic currency, the terminal does not need to display a message regarding the execution of authentication, thereby reducing the processing load of the terminal. Also, for example, if not much time has passed since the payment was made with electronic currency, the same user is likely to make another payment and the risk is considered to be low, so by not displaying a message regarding the execution of authentication, it is possible to improve user convenience while ensuring safety.

[0300] Moreover, the first embodiment shows a configuration in which the information on IMS money includes information on the location where a payment was made using IMS money (not limited to information on the location where a payment was made using electronic currency). One example of the effect that can be obtained by such a configuration is that, when making a payment with electronic currency, the terminal obtains information regarding the location where the payment was made with electronic currency, thereby eliminating the need to perform display processing regarding the execution of authentication for the user of the terminal, thereby reducing the processing load on the terminal.

[0301] In addition, the first embodiment shows a configuration in which the information regarding the location where the payment was made with the above-mentioned IMS money includes information regarding the store where the payment was made with IMS money (not limited to, information regarding the store where the payment was made with electronic currency). One example of the effect that can be obtained by such a configuration is that, when making a payment with electronic currency, the terminal obtains information about the store where the payment was made with electronic currency, thereby eliminating the need to perform display processing regarding the execution of authentication for the user of the terminal, thereby reducing the processing load on the terminal.

[0302] In addition, the first embodiment illustrates a configuration in which the terminal 20 does not perform authentication processing based on location information of the store where payment was made with IMS money (not limited to, but an example of information regarding the location where payment was made with electronic currency) and location information of the terminal 20 calculated by the location calculation processing unit 217 (not limited to, but an example of information regarding the terminal's location). As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal does not display information regarding the execution of authentication based on information regarding the store where the payment was made with electronic currency and information regarding the location of the terminal, thereby reducing the processing load of the terminal. Also, for example, if the location of the terminal is not far from the store where the user has made a payment with electronic currency in the past, it is highly likely that the user is about to make a payment at the same store, and the risk is considered to be low, so by not displaying information regarding the execution of authentication, it is possible to improve user convenience while ensuring safety.

[0303] In addition, the first embodiment shows a configuration in which the information regarding the above-mentioned IMS money includes information regarding the location where authentication was performed for making an IMS money payment (not limited to this, an example of information regarding the location where authentication was performed for making an electronic currency payment). As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information regarding the location where authentication for making an electronic currency payment was performed, and thus can reduce the processing load of the terminal since it is not necessary to perform display processing regarding the execution of authentication for the user of the terminal. Also, for example, if the location is where authentication for making an electronic currency payment was performed in the past, it is highly likely that authentication will be performed again for the same user, and the risk is considered to be low, so by not performing display processing, it is possible to improve user convenience while ensuring safety.

[0304] Moreover, the first embodiment shows a configuration in which the information different from the authentication password includes information related to a location. One example of the effect that can be obtained by such a configuration is that, when making a payment with electronic currency, the terminal can obtain information regarding the location, thereby eliminating the need to perform display processing regarding the execution of authentication for the terminal user, thereby reducing the processing load on the terminal.

[0305] Moreover, in the first embodiment, the location-related information includes information about the location of the store where the product is purchased. As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information about the place where the product is purchased, and thus can reduce the processing load of the terminal since it does not need to perform display processing related to the execution of authentication for the terminal user. Also, the information about the place where the product is purchased can be used, for example, as information to determine whether the place is a store that sells inexpensive products such as daily necessities, and can be used as a guide for whether authentication should be executed for the terminal user.

[0306] Moreover, in the first embodiment, the information regarding the place where the product is purchased includes information regarding the store that sells the product. As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information about the store selling the product, and thus can reduce the processing load on the terminal since it does not need to perform display processing related to the execution of authentication for the terminal user. Also, the information about the store selling the product can be used, for example, as information to determine whether the store sells inexpensive products such as daily necessities, and can be used as a guide for whether authentication should be executed for the terminal user.

[0307] Furthermore, the first embodiment illustrates a configuration in which the terminal 20 does not perform authentication processing if the store where payment is to be made is a set store or a store of a first specific industry (not limited to, but an example of a first location), but performs authentication processing until a set time has elapsed from the date and time of payment at a store of a second specific industry that is different from these stores (not limited to, but an example of a second location). As an example of the effect obtained by such a configuration, when the terminal obtains information about a first location when making a payment with electronic currency, it does not display any indication regarding the execution of authentication, but when it obtains information about a second location different from the first location, it displays any indication regarding the execution of authentication until a set time has elapsed since the payment is made at the second location with electronic currency. Therefore, for example, in cases where a user leaves the terminal at the second location or loses the terminal at the second location, it is possible to prevent a third party who has obtained the terminal from making an unauthorized payment.

[0308] Moreover, the first embodiment shows a configuration in which the information different from the authentication password includes information related to the product. As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information about the product, and thus can avoid display processing related to the execution of authentication for the user of the terminal, thereby reducing the processing load of the terminal. Also, the information about the product can be used to determine whether a high-priced or low-priced product has been purchased, and thus can be used as a guide for determining whether authentication for the user of the terminal should be executed.

[0309] In addition, the first embodiment shows a configuration in which information different from the above authentication password includes information regarding the settings of the terminal 20 or a payment application stored in the terminal 20 (not limited to, but an example of information regarding the settings of the terminal or an application stored in the terminal). As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information about the settings of the terminal or an application stored in the terminal, and thus can avoid display processing related to the execution of authentication for the user of the terminal, thereby reducing the processing load of the terminal. Also, for example, if the information about the settings of the terminal or an application stored in the terminal is information set by the user, the user's intention can be respected, and user convenience can be improved.

[0310] In addition, the first embodiment shows a configuration in which information different from the above authentication password includes information set in the terminal 20 indicating whether the terminal 20 is locked or not (not limited to, an example of information related to the security of the terminal set in the terminal). As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information related to the security of the terminal set in the terminal, and thereby can avoid display processing related to the execution of authentication for the user of the terminal, thereby reducing the processing load of the terminal. Also, for example, if the information related to the security of the terminal is information related to the authentication of the user of the terminal, convenience for the user can be improved by omitting display processing related to the execution of authentication for the user of the terminal.

[0311] In addition, the first embodiment shows a configuration in which information different from the above authentication password includes information on terminal-side authentication settings set in the terminal 20 or information on payment authentication settings set in a payment application stored in the terminal 20 (not limited to, an example of information regarding skipping authentication execution set in the terminal or an application stored in the terminal). As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can obtain information regarding skipping authentication execution that is set in the terminal or in an application stored in the terminal, thereby eliminating the need to perform display processing regarding the execution of authentication for the user of the terminal, thereby reducing the processing load on the terminal.

[0312] In addition, the first embodiment shows a configuration in which information other than the above authentication password includes information sent from a server 10 (not limited to, but an example of a server that manages payments using electronic currency) related to payments using IMS money. One example of the effect that can be obtained by such a configuration is that when making a payment with electronic currency, the terminal can obtain information regarding the payment with electronic currency sent from the server, thereby eliminating the need to perform display processing regarding the execution of authentication for the user of the terminal, thereby reducing the processing load on the terminal.

[0313] In addition, the first embodiment shows a configuration in which the terminal 20 may not execute the payment process based on information other than the above authentication password, and displays a terminal display code for making a payment with IMS money (not limited to, an example of code information for making a payment with electronic currency) on the display unit 24, and receives information on the payment result with IMS money via the communication I / F 22 based on reading the terminal display code by the code reader 58 (not limited to, an example of a code reader) of the store code reader device 50. As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can easily receive information relating to the payment with electronic currency by simply having a code reader read the code information for making the payment with electronic currency displayed in the display area of ​​the terminal.

[0314] In addition, the first embodiment shows a configuration in which the terminal 20 displays a message or the like (not limited to this, an example of a display related to reading of code information) on the display unit 24 instructing the user of the terminal 20 to have the terminal display code read by the code reader 58 of the store code reader device 50, and obtains information different from the authentication password based on the reading of the terminal reading code by the code reader 58 of the store code reader device 50. As an example of the effect obtained by such a configuration, the terminal can notify the user of the information related to reading of the code information. Also, when making a payment by electronic currency, the terminal can easily obtain information different from the authentication information by simply having the code reader read the code information displayed in the display area of ​​the terminal.

[0315] Moreover, in the first embodiment, the information different from the authentication password includes a payment amount (not limited to this, but is an example of information related to the price of the product to be purchased and the total amount). As an example of the effect that can be obtained by such a configuration, when making a payment with electronic currency, the terminal can easily obtain information regarding the price and total amount of the items to be purchased by simply having a code reader read the code information displayed in the display area of ​​the terminal.

[0316] Furthermore, the first embodiment shows a configuration in which the terminal 20 does not perform authentication processing when the amount to be paid is equal to or less than the set amount. As an example of the effect obtained by such a configuration, when the total amount of the purchased goods is equal to or less than the set amount set by the terminal at the time of payment with electronic currency, the terminal does not display a message regarding the execution of authentication, thereby improving user convenience. Also, if the total amount of the purchased goods is low, the risk is considered to be low, so by not displaying a message regarding the execution of authentication, it is possible to improve user convenience while ensuring safety.

[0317] Furthermore, the first embodiment shows a configuration in which the terminal 20 does not perform authentication processing if there is a purchase history for the product to be purchased (this is not a limitation, but is an example of a case in which the product matches a product that the user of the terminal has purchased at least once). As an example of the effect obtained by such a configuration, when a payment is made with electronic currency, if the product matches a product that the user of the terminal has purchased more than once, the terminal does not display a message regarding the execution of authentication, thereby improving user convenience. Also, since the risk is considered low if the same product is purchased, not displaying a message regarding the execution of authentication can improve user convenience while ensuring safety.

[0318] In addition, the first embodiment shows a configuration in which the terminal 20 receives and acquires information different from the authentication password via the communication I / F 22, the information being sent from the server 10 managing payments using IMS money based on reading a terminal display code (not limited to this, an example of code information). As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the terminal can easily obtain information other than the authentication information sent from the server that manages the payment with electronic currency by simply reading the code information.

[0319] In addition, the first embodiment shows a configuration in which the information regarding the payment using IMS money mentioned above includes information indicating that payment was made using IMS money, sent from server 10 (not limited to, but an example of an external server). As an example of the effect obtained by such a configuration, the terminal can obtain information indicating that a payment has been made with electronic currency from an external server.

[0320] Furthermore, in the first embodiment, the terminal 20, which performs authentication regarding the payment of the user of the terminal 20, acquires information necessary for making an authentication skip determination, and if the acquired information does not satisfy the authentication skip condition, performs authentication processing for the user of the terminal 20, and based on the result of the authentication processing, receives information regarding IMS money by the communication I / F 22. On the other hand, if the acquired information satisfies the authentication skip condition, the configuration is shown in which the authentication processing for the user of the terminal 20 is not performed, and information regarding IMS money is received by the communication I / F 22. As an example of the effect obtained by such a configuration, when the information acquired by the terminal satisfies the conditions, unlike when the conditions are not satisfied, the processing related to authentication of the user of the terminal is not executed, so that the processing load of the terminal can be reduced. Also, since the user of the terminal does not need to perform operations necessary for authentication, the convenience of the user can be improved.

[0321] <First Modification Example (1)> In the first embodiment, the type of authentication for the user of the terminal 20 is password authentication, and the display process for executing this authentication is processing for displaying an authentication screen for inputting an authentication password, but this is not limited to this. In addition, for example, the type of authentication for the user of the terminal 20 may be biometric authentication such as face authentication, fingerprint authentication, voice authentication, etc., and the process for displaying an authentication screen required for performing these biometric authentications may or may not be the display process for executing authentication for the user of the terminal.

[0322] Also, as a non-limiting example, the process of displaying an authentication screen in the authentication process for obtaining an account such as a user ID for using a payment service may or may not be a display process related to the execution of authentication for the user of the terminal. And, when the result of this authentication process is "OK", the terminal 20 may or may not receive information on the account for using the payment service from the server 10 as information related to payment by electronic currency.

[0323] <Effects of the first modified example (1)> As an example of the effect of this modified example, the terminal can easily receive information regarding payments made with electronic currency without performing display processing regarding the execution of authentication for the user of the terminal, also for authentication other than authentication using an authentication password.

[0324] Furthermore, the terminal can easily obtain information required for using the settlement service as information regarding settlement by electronic currency, without performing display processing related to the execution of authentication for the user of the terminal.

[0325] <First Modification (2)> In the first embodiment, electronic currency is described as IMS money, but is not limited to this. Electronic currency is not limited to IMS money, and may be a concept including, but not limited to, any payment means that a user can use as an alternative to cash, such as so-called virtual currency, in-game currency, gift codes sent (presented) as gifts by users of other terminals 20, points sent (presented) to a user by various point services including the above-mentioned IMS points, and the like.

[0326] <Effects of the first modified example (2)> As an example of the effect obtained by this variant, when making a payment with electronic currency other than the electronic currency associated with the IMS, the terminal can easily receive information related to the payment with electronic currency without performing a display process related to the execution of authentication for the user of the terminal.

[0327] <First Modification (3)> In the first embodiment, the terminal display code and the terminal read code are described as two-dimensional codes, but are not limited thereto. At least one of the terminal display code and the terminal read code may or may not be the one-dimensional code described above (as an example, but not limited to, a barcode), as an example, but not limited to.

[0328] In addition, at least one of the terminal-display code and the terminal-read code may be a character code represented by a character string of information stored in the code, and the terminal-display code may be character-recognized by reading it with a camera in the store, and the terminal-read code may be character-recognized by reading it with camera 27 of terminal 20, or the like, to obtain the information contained in each code, or this is not necessary.

[0329] <Effects of the first modified example (3)> As an example of the effect of this modification, a terminal can be settled based on a terminal display code or a terminal read code different from the two-dimensional code. Also, even if the terminal or the store code reader device does not support two-dimensional codes, settlement by electronic money can be realized.

[0330] <First Modification (4)> In the first embodiment, the information regarding payment sent from the server 10 is stored as payment history data in the memory unit 28 of the terminal 20, and the terminal 20 makes an authentication skip decision based on the information regarding payment contained in this payment history data, but this is not limited to the above.

[0331] Specifically, it is also possible to prevent the storage of the payment history data in the storage unit 28 of the terminal 20. In this case, the terminal 20 may or may not request the server 10 for information necessary for authentication skip determination, and may or may not perform authentication skip determination based on the information acquired from the server 10.

[0332] <Effects of the first modified example (4)> One of the advantages of this modified example is that it is not necessary to store information about the history of payments using electronic currency in the terminal, thereby saving on the storage capacity of the terminal.

[0333] <First Modification (5)> In the first embodiment, store location information is included in store data 2855 delivered from server 10 to terminal 20, and terminal 20 may or may not make an authentication skip determination based on the store location information included in store data 2855 and location information of terminal 20 calculated by location calculation processing unit 217 (hereinafter referred to as "terminal location information").

[0334] Specifically, for example, when determining the authentication skip condition of “the store where payment is planned is the set store” of condition No. “SP2-2” included in condition category No. “SP2”, it is possible to determine whether the latest calculated location of terminal 20 matches the location of the set store stored in store data 2855. The same applies to other authentication skip conditions related to stores and locations.

[0335] <Effects of the first modified example (5)> As an example of the effect obtained by this modified example, the terminal can easily determine whether or not the authentication skip condition is met based on terminal location information calculated by its own terminal 20 and store location information acquired from an external source.

[0336] <First Modification (6)> In the first embodiment, the daily upper limit set amount is set as an upper limit set amount that is a threshold value for the total amount of the amount already paid (payment amount) in that day, but the present invention is not limited to this.

[0337] Specifically, as an example and not by way of limitation, the daily upper limit set amount may or may not be set as an upper limit set amount that is a threshold amount for the combined amount of the total amount already paid (payment amount) in that day and the amount to be paid in the future (scheduled payment amount).

[0338] In addition, the upper limit set amount does not necessarily have to be the upper limit set amount for one day, but may or may not be the upper limit set amount for a specified period of the past (past week, past two weeks, past month, etc.).

[0339] Also, the upper limit set amount can be set to the amount to be paid in the future (planned payment amount), that is, the set amount for the amount to be paid in one go, and authentication skip determination can be made based on the authentication skip condition that "the planned payment amount is equal to or less than the set amount (or is less than the set amount)." In this way, when the user of terminal 20 purchases a low-priced item, the authentication process can be skipped.

[0340] <Effects of the first modified example (6)> One example of the effect obtained by this modified example is that it is possible to determine whether or not to display a message regarding the execution of authentication by taking into consideration not only the amount paid in the past (payment amount) but also the amount to be paid in the future (planned payment amount).

[0341] In addition, convenience for the user can be improved by not displaying a message regarding the execution of authentication until the amount of a single payment exceeds a set amount.

[0342] <First Modification (7)> The various authentication skip conditions described in the first embodiment are merely examples, and can be added, deleted, or changed as appropriate.

[0343] Specifically, as a non-limiting example, the authentication skip condition of condition No. "SP1-1" of "the current date and time is within a set time from the last payment date and time" can be changed to "the current date and time is within a set time from the last authentication date and time." This is because, for example, after a user of terminal 20 performs authentication at terminal 20 to purchase a certain product (e.g., a lunch box), there may be a case where the user needs to perform authentication again at terminal 20 to immediately purchase another product (e.g., coffee).

[0344] Furthermore, the above-mentioned "last authentication date and time" is not necessarily limited to the date and time when authentication for payment was last performed. As a non-limiting example, the "last authentication date and time" in the above-mentioned authentication skip condition can also be the date and time when authentication for a type of authentication other than authentication for payment was last performed, such as the date and time when authentication for money transfer was last performed when making a person-to-person transfer of IMS money described later in the fourth embodiment, the date and time when authentication for unlocking the OS side of terminal 20 was last performed, or the date and time when authentication for unlocking the payment application side was last performed.

[0345] Also, by way of example and not limitation, the "last payment date and time" in the authentication skip condition of condition No. "SP1-1" can be the "last charge date and time", which is the most recent date and time when IMS money was charged by the user, or the "last payment-related operation date and time", which is the most recent date and time when a user operation related to payment was performed within the payment application. If not much time has passed since IMS money was last charged, it is highly likely that the user charged IMS money for payment, so it is reasonable to skip the authentication process. Also, if not much time has passed since the last user operation related to payment was performed within the payment application, it is highly likely that the user performed the operation with the intention of making a payment, so it is reasonable to skip the authentication process.

[0346] Furthermore, the "set time period" in the authentication skip condition of condition No. "SP1-2" can be a concept including a specific day of the week or a specific date. As a non-limiting example, Saturday or Sunday may be set as the specific day of the week. This is because many users go out shopping or eating on Saturdays and Sundays, and there tends to be more opportunities for payments to be made on these days. Furthermore, Christmas (including Christmas Eve) and the first three days of the New Year may be set as the specific date. This is because many users go out to buy presents or have dinner on Christmas, and many users go out for New Year's sales during the first three days of the year, and there tends to be more opportunities for payments to be made on both days.

[0347] There is also a risk that a third party may use the terminal 20 of the user of the terminal 20 to purchase expensive goods through payment, and then convert the goods into cash. As such, it is possible to add, as a non-limiting example, an authentication skip condition that "the store where the payment is to be made is not a store that sells goods that are easily convertible into cash." Goods that are easily convertible into cash include, for example, jewelry and watches, and if the payment is to be made at a store that sells such goods (such as a jewelry store or a watch store), it is possible to prevent the authentication process from being skipped by the terminal 20.

[0348] Also, it is possible to add an authentication skip condition related to the weather. For example, on rainy or snowy days, the number of users using public transportation increases, increasing the risk of the terminal 20 being left behind. For this reason, as a non-limiting example, an authentication skip condition that "the weather on that day is not rainy or snowy" can be added, so that the authentication process is not skipped on rainy or snowy days.

[0349] <Effects of the first modified example (7)> As one example of the effect obtained by this modified example, when making a payment with electronic currency, the terminal will not display any message regarding the execution of authentication not only if it is within a set time since the date and time when authentication for payment was last performed, but also if it is within a set time since the date and time when a type of authentication other than authentication for payment was last performed, thereby further improving user convenience.

[0350] In addition, when making a payment with electronic currency, if it is within a set time from the date and time when the electronic currency was last deposited, or if it is within a set time from the date and time when the payment operation within the application was last performed, then a display regarding the execution of authentication is not displayed, thereby further improving user convenience.

[0351] In addition, by not displaying information about the execution of authentication on a specific day of the week or a specific date, it is possible to further improve user convenience.

[0352] In addition, by not performing display processing regarding the execution of authentication for the terminal user based on information that takes into account the user's risk, it is possible to realize appropriate payment that takes into account the balance between user convenience and risk.

[0353] <First Modification (8)> In the processing of Figure 3-29 described in the first embodiment, when the payment type is "terminal code display", the terminal 20 performs the first authentication skip determination processing at the timing after receiving the terminal display code from the server 10 (after A7), but this is not limited to this.

[0354] As a non-limiting example, the terminal 20 may or may not perform the first authentication skip determination process before transmitting terminal display code generation request information to the server 10 (before A5 in Figure 3-29).

[0355] Also, as a non-limiting example, after the terminal 20 transmits terminal display code generation request information to the server 10 (A7 in FIG. 3-29), rather than the terminal display code being immediately transmitted from the server 10 to the terminal 20, the authentication skip determination process may or may not be performed before the terminal display code is transmitted from the server 10 to the terminal 20.

[0356] Specifically, after receiving terminal display code generation request information transmitted from the terminal 20 (C1 in FIG. 3-29; Yes), the server 10 transmits authentication request information for requesting authentication to the terminal 20. Then, at the timing after receiving this authentication request information from the server 10, the terminal 20 performs a first authentication skip determination process.

[0357] If it is determined that the authentication process is to be skipped, the terminal 20 skips the authentication process and transmits authentication skip execution information indicating that the authentication process has been skipped to the server 10. On the other hand, if it is determined that the authentication process is not to be skipped, the terminal 20 performs the authentication process, and if the authentication result is "OK", transmits authentication success information indicating that the authentication has been successful to the server 10. Then, after receiving either the authentication skip execution information or the authentication success information from the terminal 20, the server 10 performs a terminal display code generation process to generate a terminal display code (C3 in FIG. 3-29), and transmits the generated terminal display code to the terminal 20 (C5 in FIG. 3-29).

[0358] In this case, after the server 10 receives the terminal display code generation request information sent from the terminal 20 (C1 in FIG. 3-29; Yes), it can perform a terminal display code generation process to generate a terminal display code (C3 in FIG. 3-29), and then transmit authentication request information to the terminal 20.

[0359] As described above, the timing for performing the authentication skip determination process on the terminal 20 side can be roughly divided into any one of three timings, as described above.

[0360] <Effects of the first modified example (8)> As an example of the effect obtained by this modified example, when making a payment with electronic currency, the terminal can determine whether or not to execute a display process regarding the execution of authentication for the user of the terminal at one of multiple timings based on information other than authentication information for authenticating the user of the terminal.

[0361] <First Modification (9)> In the above embodiment, for both the payment types "display terminal code" and "read terminal code," information regarding the product to be purchased is not transmitted from server 10 to terminal 20, and terminal 20 cannot obtain information regarding the product to be purchased. However, it is also possible to allow terminal 20 to obtain information regarding the product to be purchased, for example, by the following method.

[0362] Specifically, as a non-limiting example, software for enabling identification of the type of product based on an image captured by a camera provided as a function of a payment application (hereinafter referred to as an "application camera") or an imaging device (or imaging unit) such as camera 27 provided in terminal 20 is stored in memory unit 28 of terminal 20.

[0363] In the payment type "display terminal code", for example, before A1 of the first payment application process in FIG. 3-29, terminal 20 activates the application camera or camera 27 in accordance with a user operation to take an image of the product to be purchased. That is, the user of terminal 20 takes an image of the product to be purchased with the application camera or camera 27 at the store's code register 60. Then, terminal 20 performs a product type identification process to identify the type of product from the captured image (hereinafter referred to as the "captured image"). Then, after performing the processes "A3; display terminal code to A7", terminal 20 performs a first authentication skip determination process (A9).

[0364] Similarly, for the payment type "terminal code reading", for example, before A1 of the first payment application process in FIG. 3-29, terminal 20 starts the application camera or camera 27 in accordance with a user operation to capture an image of the product to be purchased. Then, terminal 20 performs a product type identification process to identify the type of product from the captured image. Then, after performing the processes "A3; terminal code reading to A41", terminal 20 performs a first authentication skip determination process (A9).

[0365] Fig. 3-34 is a diagram showing an example of the authentication skip condition data 2851 in this case. This data configuration is similar to the authentication skip condition data 2851 in Fig. 3-8, but the part surrounded by a thick black frame is different.

[0366] Specifically, for the authentication skip condition of condition No. "SP4-1" "The product to be purchased is a daily consumer good", "○" is set as the applicability for both the payment types "display terminal code" and "read terminal code". This is because by using the above method, it becomes possible to identify the type of product on the terminal 20, and it is possible to determine whether the product to be purchased is a daily consumer good based on the identified type of product. Furthermore, the importance level "B" is set for the payment type "display terminal code", and the importance level "A" is set for the payment type "read terminal code".

[0367] Additionally, for the authentication skip condition of condition No. "SP4-2" "there is a purchase history of the product to be purchased", "○" is set as the applicability for the payment type "display terminal code". This is because by using the above method, it becomes possible to identify the type of product at the terminal 20, and by storing the history of the identified product type in the storage unit 28, it becomes possible to determine whether there is a purchase history of the product to be purchased. Additionally, the importance level "B" is set for the payment type "display terminal code", and the importance level "A" is set for the payment type "read terminal code".

[0368] In addition, in the first embodiment, for the payment type "terminal code reading", the success or failure of the authentication skip conditions of condition Nos. "SP4-1" and "SP4-2" was determined using an alternative method, but with the above-mentioned method using a camera, it is possible to identify the type of product to be purchased with terminal 20, and therefore it is possible to determine the success or failure of these authentication skip conditions based on the identification results.

[0369] In addition to taking pictures of the products to be purchased with the camera of the terminal 20 as described above, it is also possible to provide a camera in the store code reader device 50, for example, and have the camera of the store code reader device 50 take pictures of the products that the user of the terminal 20 wants to purchase.

[0370] In this case, one method is for the store code reader device 50 to identify the type of the product to be purchased based on an image captured by a camera and transmit the identified type of the product to be purchased to the terminal 20.

[0371] As another method, the store code reader device 50 can transmit an image captured by a camera to the terminal 20, and the terminal 20 can identify the type of product to be purchased based on the captured image received from the store code reader device 50.

[0372] <Effects of the first modified example (9)> In this modified example, information other than the authentication password described above includes information about products sold in the store (not limiting, but an example of information about products). As an example of the effect obtained by such a configuration, the terminal does not need to perform display processing related to the execution of authentication for the user of the terminal based on the information about the product, and therefore the processing load on the terminal can be reduced.

[0373] In addition, this modified example illustrates a configuration in which terminal 20 acquires an image of the product to be purchased captured by the application camera or camera 27 (not limited to, but an example of an imaging device) of terminal 20, and does not perform authentication processing based on the acquired image. As an example of the effect obtained by such a configuration, the terminal does not display information regarding the execution of authentication based on the image of the product captured by the imaging device, thereby reducing the processing load of the terminal. For example, if the product identified from the image captured by the imaging device is a product with a past purchase history or a specific type of product, the convenience for the user can be improved by not displaying information regarding the execution of authentication.

[0374] In addition, this modified example shows a configuration in which information different from the above-mentioned authentication password includes information on a product to be purchased (not limited to this, but is an example of information on a product to be purchased by the user of the terminal). One example of the effect obtained by such a configuration is that the terminal does not need to perform display processing regarding the execution of authentication for the user of the terminal based on information regarding the products purchased by the user of the terminal, thereby reducing the processing load on the terminal.

[0375] Moreover, this modified example shows a configuration in which, when information on a product to be purchased by the user of the terminal 20 is acquired and it is determined that there is a purchase history of the product to be purchased, no authentication process is performed. As an example of the effect obtained by such a configuration, if the product matches a product that the user of the terminal has purchased more than once, the terminal does not display a message regarding the execution of authentication, thereby reducing the processing load of the terminal. Also, since the risk is considered low if the same product is purchased, by not displaying a message regarding the execution of authentication, it is possible to improve user convenience while ensuring safety.

[0376] Moreover, this modified example shows a configuration in which, when information on a product to be purchased by the user of the terminal 20 is acquired and it is determined that the product to be purchased is a daily consumer good, authentication processing is not performed. As an example of the effect obtained by such a configuration, when the product purchased by the user is a daily consumer good, the terminal does not display a message regarding the execution of authentication, thereby reducing the processing load of the terminal. Also, since the risk of purchasing daily consumer goods is considered to be low, it is possible to improve user convenience while ensuring safety by not displaying a message regarding the execution of authentication.

[0377] In addition to the above, as a method for identifying the product and the product type purchased by the user of terminal 20 at terminal 20, a method using short-range wireless communication or non-contact communication can also be applied, by way of example and not of limitation.

[0378] Specifically, as a non-limiting example, an RF tag (e.g., an IC tag) storing product identification information or product type identification information is embedded in each product or each product type sold in a store. Furthermore, the terminal 20 is equipped with a reader / writer compatible with RF tags. The terminal 20 then uses radio waves to scan the RF tag embedded in the product purchased by the user and acquires the product identification information or product type identification information stored in the RF tag, thereby identifying the product purchased by the user and its product type.

[0379] <First Modification (10)> In the first embodiment, the store may or may not request the server 10 to skip the authentication process for the terminal 20, and the server 10 may or may not transmit information for skipping the authentication process (hereinafter referred to as "authentication skip information") to the terminal 20.

[0380] In this modified example, it is possible to cause the terminal 20 to skip the authentication process based on the authentication skip information sent from the server 10. For this reason, even when a person who is trying to purchase a product or receive a service uses another person's terminal 20 to make a payment, a problem may occur in which the authentication process is skipped in the terminal 20 and the payment is made. This modified example is intended to skip the authentication process of the terminal 20, while placing the risk on the store, while being aware that such a problem may occur.

[0381] First, a case where authentication skip is performed on a store-by-store basis will be described. This is a case where the decision as to whether or not to skip the authentication process of the terminal 20 is left to the discretion of the store, and the store is targeted at stores that have agreed to skip the authentication process of the terminal 20 while being aware of the risks.

[0382] Figure 3-35 is a flowchart showing an example of the process flow of each device in this case, which is an excerpt of the process portion of Figure 3-31, which is the process portion when the payment type is "terminal code reading" in the process described in the first embodiment. Note that the same steps as in the previous flowcharts are given the same reference numerals and will not be described again.

[0383] If the store payment processing unit 513 determines in B5 that the payment type is not “terminal code display”, that is, that the payment type is “terminal code reading” (B3; No), it sends authentication skip request information to the server 10 via the communication I / F 54 (B51).

[0384] Specifically, if the store is one that uses the first type terminal reading code, the store payment processing unit 513 sends authentication skip request information to the server 10, which includes, by way of example and not limitation, the store ID and sales price information of the product sold in association with the first type terminal reading code. Furthermore, if the store itself is a store that uses second type terminal reading codes, the store payment processing unit 513 transmits to the server 10 authentication skip request information including the store ID, for example and not for limitation.

[0385] Here, the authentication skip request information is information for requesting the server 10 to generate authentication skip information for allowing the terminal 20 to skip the authentication process. As a non-limiting example, this authentication skip request information can be transmitted from the store code reader device 50 to the server 10 based on the approval of the store server 70.

[0386] Further, although the description herein is given assuming that the store code reader device 50 transmits the authentication skip request information to the server 10, instead, the store server 70 may or may not transmit the authentication skip request information to the server 10.

[0387] When the payment management processing unit 113 receives authentication skip request information from the store code reader device 50 via the communication I / F 14 (C51), it performs a terminal reading code generation determination process (C53).

[0388] Specifically, as a non-limiting example, it is determined whether the store that sent the authentication skip request information is an affiliated store. Also, if the received authentication skip request information includes sales price information of the product sold in association with the first type terminal reading code, it is determined whether the sales price indicated by this sales price information is within an appropriate range (as a non-limiting example, below a threshold amount (which depends on the type of business of the store and the product / product type sold, for example, "1000 yen or less," "2000 yen or less," "3000 yen or less"). If these conditions are met, it is determined to generate a terminal reading code. On the other hand, if these conditions are not met, it is determined not to generate a terminal reading code.

[0389] If it is determined that a terminal read code is to be generated (N55; Yes), the payment management process unit 113 performs a terminal read code generation process (C57).

[0390] In this terminal reading code generation process, the payment management processing unit 113 generates a terminal reading code including access information. More specifically, for example, the character string of the payment page URL is encoded and graphically converted to generate a terminal reading code represented by an image of a two-dimensional code. The payment management processing unit 113 also associates the sales amount (only for stores that use the first type terminal reading code), the payment page URL, and the presence or absence of authentication skip (here, authentication skip is "yes") with the store ID of the store, and stores them in the terminal reading code management database 1593 of the code management database 159.

[0391] Thereafter, the payment management processing unit 113 transmits the generated terminal reading code via the communication I / F 14 to the store code reader device 50 that is the sender of the authentication skip request information (C59).

[0392] On the other hand, if it is determined that the terminal reading code is not to be generated (C55; No), the payment management processing unit 113 notifies the store code reader device 50 via the communication I / F 14 that the terminal reading code cannot be generated (C61). Then, the payment management processing unit 113 proceeds to C63.

[0393] The store payment processing unit 513 determines whether or not a terminal reading code has been received from the server 10 via the communication I / F 54 (B53), and if it determines that the terminal reading code has been received (B53; Yes), it causes the display unit 53 to display the received terminal reading code (B55).

[0394] The payment application processing unit 213 of the terminal 20 reads the terminal reading code with the application code reader (A51). Specifically, it reads either the terminal reading code posted in the store or the terminal reading code displayed on the store code reader device 50 in B55. Then, the payment application processing unit 213 performs the processes of A33 and A35.

[0395] After C59 or C61, the payment management processing unit 113 judges the payment schedule information in response to the access to the payment page from the terminal 20 (C63). Specifically, it refers to the terminal reading code management database 1593 and acquires the information stored in association with the payment page URL of this payment page. Then, the payment management processing unit 113 transmits the payment schedule information (authentication skip "Yes" or "No") in response to the judgment result to the terminal 20 via the communication I / F 14 (C65).

[0396] If the information stored in association with the payment page URL is information indicating that the authentication skip is "not performed" (in the case of the process flow from C61 to C63), the process is the same as C35 in Fig. 3-31. In other words, the payment management processing unit 113 transmits payment schedule information not including the authentication skip information to the terminal 20.

[0397] On the other hand, if the information stored in association with the payment page URL indicates that authentication skip has been performed (in the case of the processing flow from C59 to C63), the payment management processing unit 113 sends payment schedule information including the authentication skip information to the terminal 20. In this case, if the information associated with the payment page URL is information about a store that uses a first type terminal reading code, the payment management processing unit 113 sends to the terminal 20 first type payment schedule information including the store where the payment is to be made, the amount to be paid, and authentication skip information. On the other hand, if the information associated with the payment page URL is information about a store that uses a second type terminal reading code, the payment management processing unit 113 sends second type payment information (excluding the planned payment amount) including the store where the payment is scheduled and authentication skip information to the terminal 20 via communication I / 14.

[0398] When the payment application processing unit 213 receives payment schedule information (authentication skip "yes" or "no") from the server 10 via the communication I / F 22 (A53), it performs the processes of A39 and A41, and then performs a second authentication skip determination process (A55). Note that, for the sake of distinction from the authentication skip determination process in other embodiments, this process is conveniently referred to as the "second authentication skip determination process."

[0399] In this second authentication skip determination process, the authentication skip determination processing unit 2135 determines whether or not the payment schedule information received from the server 10 includes authentication skip information. If the terminal reading code displayed on the store code reader device 50 is read in A51, it is determined that the received payment schedule information includes authentication skip information, whereas if the terminal reading code posted in the store is read, it is determined that the received payment schedule information does not include authentication skip information. If it is determined that the received payment schedule information includes authentication skip information, it is determined to skip the authentication process. Then, the payment application processing unit 213 moves the process to A11.

[0400] In addition, in the above-mentioned second authentication skip determination process, as a non-limiting example, if the authentication setting for payment on the payment application side on terminal 20 is set to "ON" or if a mode setting is configured on terminal 20 that does not skip the authentication process, it is possible to prevent the authentication process from being skipped even if the payment schedule information includes authentication skip information.

[0401] Next, the above processing is processing in the case where authentication skipping is performed on a store-by-store basis, but as a non-limiting example, it is also possible to allow authentication skipping to be performed on a product-by-product or product type-by-product basis sold in a store.

[0402] FIG. 3-36 is a diagram showing an example of the terminal reading code management database 1593 stored in the storage unit 15 of the server 10 in this case. This terminal reading code management database 1593 includes terminal reading code management data generated for a store that has agreed to allow the terminal 20 to skip the authentication process.

[0403] The terminal reading code management data for each store stores, by way of example and not limitation, the product type, sales price, payment page URL, and whether or not authentication is skipped, all in association with the store ID of the store.

[0404] In this example, the product types include "lunch box," "drink," and "gift item," and each product type is associated with a sales price, a payment page URL, and whether or not authentication skip is enabled. The product types "lunch box" and "drink" are set with "yes" as the authentication skip option, while the product type "gift item" is set with "no" as the authentication skip option. Therefore, when a user purchases a lunch box or drink at this store, the authentication process is skipped at terminal 20, but when a user purchases a gift item at this store, the authentication process is not skipped at terminal 20.

[0405] Furthermore, within one product type, it is also possible to classify and associate the sales price, the payment page URL, and whether or not authentication can be skipped. Specifically, as a non-limiting example, the product type "lunch box" can be classified into lunch boxes with a sales price of "200 yen," lunch boxes with a sales price of "300 yen," and lunch boxes with a sales price of "500 yen," and each classification can be associated with a payment page URL and whether or not authentication can be skipped.

[0406] The above-mentioned multiple patterns can be appropriately changed on the server 10 side depending on the operation of the store.

[0407] <Effects of the first modified example (10)> In this modification, information different from the authentication password includes authentication skip information. As an example of the effect obtained by such a configuration, the terminal can skip authentication of the user of the terminal based on skip information for the terminal to skip authentication of the user of the terminal. Also, since it is possible to determine whether or not to skip authentication of the user of the terminal based on the skip information, and it is not necessary to determine whether other conditions are satisfied, the processing load of the terminal can be reduced.

[0408] In this modification, the authentication skip information is generated by the server 10 based on the authentication skip request information transmitted from the store code reader device 50. As an example of the effect obtained by such a configuration, the terminal can easily skip authentication of the terminal user based on skip information generated by the server based on a request from the store that manages the products. Also, since it is possible to determine whether or not to skip authentication of the terminal user based on the skip information generated by the server, and it is not necessary to determine whether other conditions are met, the processing load of the terminal can be reduced.

[0409] <Second embodiment> The second embodiment is an embodiment that improves the convenience of payment, similar to the first embodiment. More specifically, as a non-limiting example, when making a payment using a payment application on the terminal 20, the server 10 performs an authentication skip determination, and if an authentication skip condition is met, the authentication process that was previously required of the user of the terminal 20 is skipped. The contents described in the second embodiment are applicable to any of the other embodiments. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0410] <Functional configuration> FIG. 4-1 is a diagram illustrating an example of functions realized by the control unit 11 of the server 10 in this embodiment. The payment management processing unit 113 includes, by way of example and not limitation, a terminal display code generation processing unit 1131, a terminal display code transmission processing unit 1133, a store payment result information transmission processing unit 1136, and a terminal payment result information transmission processing unit 1137, as well as an authentication skip determination processing unit 1139 as functional units.

[0411] The authentication skip determination processing unit 1139 has a function of executing an authentication skip determination process, which is a process for determining whether or not to skip the authentication process executed by the terminal 20, in accordance with an authentication skip determination processing program 1515 stored in the storage unit 15. This authentication skip determination process can also be called an authentication necessity determination process for determining whether or not it is necessary to have the terminal 20 perform the authentication process.

[0412] In this embodiment, for example and not limitation, for the payment type “terminal code display”, the authentication skip determination processing unit 1139 executes the authentication skip determination processing at the timing after receiving terminal display code generation request information from the terminal 20. Furthermore, for example and not by way of limitation, in the case of the payment type "terminal code reading", the authentication skip determination processing unit 1139 executes the authentication skip determination processing at the timing after receiving the first payment request information from the terminal 20. However, the timing for executing these authentication skip determination processes can be changed as appropriate.

[0413] FIG. 4-2 is a diagram illustrating an example of information stored in the storage unit 15 of the server 10 in this embodiment. The payment management processing program 1513 includes, as a subroutine program, an authentication skip determination processing program 1515, which is read by the control unit 11 and executed as authentication skip determination processing, as a non-limiting example.

[0414] In addition, in the memory unit 15, as examples and not limitations, in addition to user registration data 153, store registration data 155, payment management database 157, and code management database 159, authentication skip condition data 156, and credit score data 158 are stored as data.

[0415] The authentication skip condition data 156 is data that defines an authentication skip condition that is a condition for causing the terminal 20 to skip the authentication process for payment.

[0416] The credit score data 158 is data in which a credit score, which represents the social credit of the user of the terminal 20 as a numerical value, a rank, or the like, is stored for each terminal 20 or for each user of the terminal 20 . The credit score is calculated or determined based on, for example and not by way of limitation, the payment history, age, employment status, annual income, etc., of the user of the terminal 20.

[0417] In this embodiment, as an example and not a limitation, the credit score is quantified using a scoring system ranging from "0 points" to "100 points," with a credit score of "100 points" indicating the user's highest social credibility and a credit score of "0 points" indicating the user's lowest social credibility.

[0418] 4-3 is a diagram showing an example of the data configuration of the authentication skip condition data 156 in this embodiment. This data configuration is similar to the authentication skip condition data 2851 of the terminal 20, but the contents are partially different. The following description will focus on the different conditions.

[0419] <Condition Category No. "SP2-5"> For condition category No. "SP2 (store / location)", the authentication skip condition for condition No. "SP2-5" is set as "the location of the store where the payment is to be made is not far from the location of the terminal". This means that if the location of the store where the payment is to be made and the location of the terminal 20 where the payment is to be made are not far from each other by, for example, a set distance or more, the authentication process of the terminal 20 is skipped.

[0420] In this determination, by way of example and not limitation, in the authentication skip determination process, the server 10 acquires store location information of the store where payment is to be made from store information registered in the store registration data 155. The server 10 also requests the terminal 20 for terminal location information, and receives and acquires the latest calculated location calculated by the location calculation processing unit 217 from the terminal 20 as terminal location information. The server 10 then determines whether or not the store location and the terminal location are apart by a set distance or more.

[0421] In addition, in the above authentication skip condition, as an example and not a limitation, information on the region (area) in which each store is located may be stored in the memory unit 15 of the server 10, and the server 10 may identify the region in which the store where payment is to be made is located, and then may or may not determine whether the terminal location is included in the identified region.

[0422] <Condition Category No. "SP5-2"> As an authentication skip condition of condition No. "SP5-2" included in condition category No. "SP5 (security)", "credit score of terminal user is 80 points or more" is defined. This means that when the credit score of the user of terminal 20 stored in credit score data 158 is 80 points or more, that is, when the credit of the user of terminal 20 has reached a certain level, the authentication process of terminal 20 is skipped.

[0423] In this determination, the terminal 20 acquires the credit score of the user of the terminal 20 to which the payment is to be made from the credit scores stored in the credit score data 158. Then, it is determined whether the acquired credit score is 80 points or more.

[0424] Other conditions are the same as the authentication skip condition data 2851 of the terminal 20, but in this embodiment, unlike the first embodiment, the server 10 performs the authentication skip determination process. For this reason, the server 10 acquires information necessary for authentication skip determination from information stored and managed by the server 10, such as user information stored in the user registration data 153 of the storage unit 15, store information stored in the store registration data 155, and payment management information stored in the payment management database 157 (hereinafter referred to as "server management information"). In addition, the server 10 requests the terminal 20 to acquire information not managed by the server 10, such as location information (terminal location information) of the terminal 20. Then, the server 10 performs authentication skip determination based on the acquired information.

[0425] Next, for the payment type "Display terminal code," by way of example and not limitation, "X" is set to not apply to condition numbers "SP2-1" to "SP2-5" (conditions included in condition category number "SP2"), condition numbers "SP3-3", "SP3-4", condition numbers "SP4-1", and "SP4-2" (conditions included in condition category number "SP4").

[0426] The authentication skip conditions included in condition category No. "SP2" are marked as not applicable "X" because, with the payment type "display terminal code", the server 10 is unable to determine the store where the payment is to be made at the time of performing the authentication skip determination process.

[0427] The authentication skip conditions for condition No. "SP3-3" and "SP3-4" are marked as "X" (not applicable) because, when the payment type is "terminal code display", the server 10 is unable to grasp the estimated payment amount at the time when performing the authentication skip determination process.

[0428] The authentication skip conditions included in condition category No. "SP4" are marked as not applicable "X" because when the payment type is "display terminal code", the server 10 is unable to grasp the product to be purchased at the time of performing the authentication skip determination process.

[0429] On the other hand, for the payment type “Terminal code reading”, as an example and not a limitation, the authentication skip condition of condition No. “SP5-1” is set to not applicable “× (O)”, and the other authentication skip conditions are set to applicable “O”.

[0430] In addition, for both the payment types "Display terminal code" and "Read terminal code", the authentication skip condition for condition No. "SP5-1" is set to "X (O)". This is because, due to basic specifications, the server 10 is unable to grasp the lock status on the OS side of the terminal 20 and the lock status on the payment application side. However, if the specifications on the terminal 20 side are changed so that information regarding these locking states is notified to the server 10, the server 10 side will be able to grasp the locking state of the terminal 20, making it possible to make an authentication skip decision.

[0431] <Processing> 4-4 to 4-6 are flowcharts showing an example of the flow of processes executed by each device in this embodiment. These figures show, from left to right, a second payment application process which is an example of payment application processing executed by the payment application processing unit 213 of the terminal 20, a second store payment process which is an example of store payment processing executed by the store payment processing unit 513 of the store code reader device 50, and a second payment management process which is an example of payment management processing executed by the payment management processing unit 113 of the server 10.

[0432] It should be noted that the flowcharts described below are merely examples of the processing in this embodiment, and some steps in the flowcharts described below may not be executed, or additional steps may be inserted. Additionally, the same steps as those in the previously described flowcharts are given the same reference numerals and will not be described again.

[0433] First, the payment application processing unit 213 of the terminal 20 executes the processes A1 to A3. If the payment type is "terminal code display" (A3: terminal code display), the terminal display code acquisition processing unit 2131 executes the process A5.

[0434] If the server 10 determines that it has received terminal display code generation request information from the terminal 20 via the communication I / F 14 (C1; Yes), the authentication skip determination processing unit 1139 executes a third authentication skip determination process (G1) in accordance with the authentication skip determination process program 1515 stored in the storage unit 15. Note that, for the sake of distinction from the authentication skip determination processes in the other embodiments, this will be referred to as the "third authentication skip determination process" for convenience.

[0435] Specifically, the authentication skip determination processing unit 1139 determines whether the authentication skip condition contained in the authentication skip condition data 156 of the memory unit 15 is satisfied or not, based on various server management information acquired from the memory unit 15 and information acquired by requesting the terminal 20, in a manner similar to that of the first embodiment.

[0436] After performing the third authentication skip determination process, the payment management processing unit 113 determines whether or not it is determined to skip the authentication process (G3). If it is determined to skip the authentication process (G3; Yes), the payment management processing unit 113 moves the process to C3.

[0437] On the other hand, if it is determined that the authentication process is not to be skipped (G1: No), the payment management processing unit 113 transmits additional authentication request information to the terminal 20 via the communication I / F 14 (G5).

[0438] The payment application processing unit 213 determines whether additional authentication request information has been received from the server 10 via the communication I / F 22 (E1), and if it is determined that additional authentication request information has not been received (E1; No), the process proceeds to A7. In this case, the authentication process in the terminal 20 is skipped.

[0439] On the other hand, if it is determined that additional authentication request information has been received from server 10 via communication I / F 22 (E1; Yes), payment application processing unit 213 executes the processes of A13 to A17. In this case, authentication processing is executed in terminal 20.

[0440] If the authentication process results in "OK" (A15; Yes), the payment application processing unit 213 sends authentication success information to the server 10 via the communication I / F 22 (E3).

[0441] When the payment management processing unit 113 receives authentication success information from the terminal 20 via the communication I / F 14 (G7), it executes the processes of C3 and C5. That is, after receiving information indicating that the authentication has been successful from the terminal 20, it generates a terminal display code (C3) and transmits the generated terminal display code to the terminal 20 (C5).

[0442] On the other hand, if it is determined in A3 that the payment type is "terminal code reading" (A3; terminal code reading), the payment application processing unit 213 executes the processes of A31 to A43.

[0443] When the server 10 receives the first payment request information from the terminal 20 via the communication I / F 14 (C37), the authentication skip determination processing unit 1139 executes the third authentication skip determination processing in accordance with the authentication skip determination processing program 1515 stored in the memory unit 15 (G1).

[0444] After performing the third authentication skip determination process, the payment management processing unit 113 determines whether or not it is determined to skip the authentication process (G3). If it is determined to skip the authentication process (G3; Yes), the payment management processing unit 113 moves the process to C11.

[0445] On the other hand, if it is determined that the authentication process is not to be skipped (G1: No), the payment management processing unit 113 transmits additional authentication request information to the terminal 20 via the communication I / F 14 (G5).

[0446] The payment application processing unit 213 determines whether additional authentication request information has been received from the server 10 via the communication I / F 22 (E1), and if it is determined that additional authentication request information has not been received (E1; No), the process proceeds to A21. In this case, the authentication process in the terminal 20 is skipped.

[0447] On the other hand, if the payment application processing unit 213 determines that additional authentication request information has been received from the server 10 via the communication I / F 22 (E1; Yes), it executes the processes of A13 to A17. In this case, the authentication process is executed in the terminal 20.

[0448] In the above process, when the payment type is "terminal code display", the server 10 performs the third authentication skip determination process after receiving terminal display code generation request information from the terminal 20 (after C1; Yes), but this is not limited to the above. As a non-limiting example, the server 10 may or may not perform the third authentication skip determination process at the timing after receiving the second payment request information from the store code reader device 50 (after C9).

[0449] <Effects of the second embodiment> In the second embodiment, the server 10 receives payment request information (not limited to, an example of information related to payment of electronic currency by the terminal) from the terminal 20 via the communication I / F 14, and transmits additional authentication request information (not limited to, information related to authentication of the user of the terminal) to the terminal 20 via the communication I / F 14. The server 10 also receives authentication success information (not limited to, an example of information indicating that the user of the terminal has been authenticated) from the terminal 20 via the communication I / F 14, and transmits payment result information (an example of payment information indicating that payment by electronic currency has been performed) to the terminal 20 via the communication I / F 14 based on the received authentication success information. The server 10 then acquires information other than an authentication password (not limited to, an example of authentication information) for authenticating the user of the terminal 20, thereby not transmitting additional authentication request information to the terminal 20 via the communication I / F 14, and transmitting payment result information to the terminal 20 via the communication I / F 14. As an example of the effect obtained by such a configuration, when making a payment with electronic currency, the server acquires information different from the authentication information for authenticating the user of the terminal, and therefore does not transmit information related to the authentication of the user of the terminal to the terminal, thereby reducing the processing load on the server. Also, since payment information can be transmitted to the terminal without transmitting information related to the authentication of the user of the terminal to the terminal, convenience for the user can be improved.

[0450] In addition, the second embodiment illustrates a configuration in which information different from the above authentication password includes terminal identification information of the terminal 20 or information associated with user identification information of the terminal 20 (not limited to this, an example of information associated with identification information for identifying the terminal or the user of the terminal). As an example of the effect obtained by such a configuration, the server can obtain information associated with identification information for identifying the terminal or the user of the terminal, and transmit payment information to the terminal without transmitting information regarding authentication of the user of the terminal to the terminal.

[0451] In addition, the second embodiment illustrates a configuration in which the terminal identification information of the above-mentioned terminal 20 or information associated with the user identification information of the terminal 20 includes information related to IMS money associated with the terminal 20 or the user of the terminal 20 (not limited to, an example of information related to electronic currency associated with the terminal or the user of the terminal). As an example of the effect that can be obtained by such a configuration, the server can obtain information regarding the terminal or electronic currency associated with the user of the terminal, and transmit payment information to the terminal without transmitting information regarding the authentication of the user of the terminal to the terminal.

[0452] In addition, the second embodiment illustrates a configuration in which the information regarding the IMS money associated with the above-mentioned terminal 20 or the user of the terminal 20 includes information regarding the amount of IMS money associated with the terminal 20 or the user of the terminal 20 (not limited to, an example of information regarding the amount of electronic currency associated with the terminal or the user of the terminal). As an example of the effect obtained by such a configuration, the server can transmit payment information to the terminal without transmitting information regarding the authentication of the terminal user to the terminal by acquiring information regarding the amount of electronic currency associated with the terminal or the user of the terminal. For example, when the amount of electronic currency is low, it becomes possible to omit authentication at the terminal by not transmitting information regarding the authentication of the terminal user to the terminal, thereby improving user convenience.

[0453] In addition, the second embodiment shows a configuration in which information regarding the amount of IMS money associated with the above-mentioned terminal 20 or the user of the terminal 20 includes a daily upper limit set amount (not limited to, but an example of information regarding the set amount of the electronic currency). As an example of the effect obtained by such a configuration, the server can obtain information regarding the set amount of electronic currency and transmit payment information to the terminal without transmitting information regarding the authentication of the terminal's user to the terminal.

[0454] In addition, the second embodiment shows a configuration in which the server 10 does not send additional authentication request information (not limited to this, but an example of information regarding authentication of the terminal user) to the terminal 20 via the communication I / F 14 until the above-mentioned daily upper limit set amount is exceeded, and sends payment result information to the terminal 20 via the communication I / F 14. As an example of the effect obtained by such a configuration, the server does not transmit information regarding the authentication of the user of the terminal to the terminal until the set amount of electronic currency is exceeded, so that the amount of communication on the server can be reduced and the load on the server can be lightened. Also, when the set amount of electronic currency is exceeded, the server transmits information regarding the authentication of the user of the terminal to the terminal, so that the user of the terminal can be alerted that the set amount has been exceeded.

[0455] In addition, the second embodiment shows a configuration in which the information regarding the amount of the above-mentioned IMS money includes information on the balance of IMS money associated with the terminal 20 or the user of the terminal 20 (not limited to this, an example of information regarding the balance of electronic currency associated with the terminal or the user of the terminal). As an example of the effect obtained by such a configuration, the server can transmit payment information to the terminal without transmitting information related to authentication of the terminal user by acquiring information related to the balance of electronic currency associated with the terminal or the user of the terminal. Also, the server can appropriately perform processing related to payment based on the information related to the balance of electronic currency associated with the terminal or the user of the terminal.

[0456] In addition, the second embodiment shows a configuration in which, when the balance of the above-mentioned IMS money is equal to or less than the set amount, the server 10 does not send additional authentication request information (not limited to, but an example of information regarding authentication of the terminal user) to the terminal 20 via the communication I / F 14, and sends payment result information to the terminal 20 via the communication I / F 14. As an example of the effect obtained by such a configuration, when the balance of electronic currency is equal to or less than a set amount, the server does not transmit information regarding the authentication of the terminal user to the terminal, thereby reducing the amount of communication on the server and the load on the server. Also, for example, when the balance of electronic currency is low, large amounts cannot be paid and the risk is considered low, so by not transmitting information regarding the authentication of the terminal user to the terminal, it becomes possible to omit authentication at the terminal, thereby improving user convenience while ensuring safety.

[0457] In addition, the second embodiment shows a configuration in which, when the auto-charge setting of the terminal 20 is "ON", the server 10 sends additional authentication request information to the terminal 20 via the communication I / F 14 when the balance of the IMS money is less than or equal to the set amount, and sends payment result information to the terminal 20 via the communication I / F 14 when the auto-charge setting of the terminal 20 is "ON". As an example of the effect obtained by such a configuration, if the server is set to automatically deposit electronic currency into the terminal when the electronic currency in the terminal falls below a set amount or falls below the set amount, the electronic currency is automatically deposited into the terminal when the amount becomes small, making it possible to make large-value payments, which creates a risk. Therefore, the server can alert the user that large-value payments will be possible by transmitting information related to the authentication of the user of the terminal to the terminal via the communication unit.

[0458] Moreover, the second embodiment shows a configuration in which the information on IMS money includes information on the frequency or number of times that settlements have been made with IMS money. As an example of the effect obtained by such a configuration, the server can obtain information regarding the frequency or number of times payments have been made with electronic currency, and transmit payment information to the terminal without transmitting information regarding the authentication of the terminal user to the terminal. For example, when payments are made frequently or many times with electronic currency, it is highly likely that the same user is making payments with electronic currency and the risk is considered to be low, so by not transmitting information regarding the authentication of the terminal user to the terminal, it becomes possible to omit authentication at the terminal, thereby improving user convenience while ensuring safety.

[0459] Moreover, the second embodiment shows a configuration in which the information on the IMS money includes information on the time when the settlement was made with the IMS money. As an example of the effect that can be obtained by such a configuration, the server can obtain information regarding the time when a payment was made using electronic currency, and thereby transmit payment information to the terminal without transmitting information regarding the authentication of the terminal's user to the terminal.

[0460] In addition, the second embodiment shows a configuration in which, if it is within a set time from the time the payment was made, the server 10 does not send additional authentication request information (not limited to this, an example of information regarding authentication of the terminal user) to the terminal 20 via the communication I / F 14, and sends payment result information to the terminal 20 via the communication I / F 14. As an example of the effect obtained by such a configuration, if it is within a set time from the time of the payment, the server does not transmit information related to the authentication of the user of the terminal to the terminal, so that the amount of communication on the server can be reduced and the load on the server can be lightened. Also, for example, if not much time has passed since the payment, the same user is likely to make a payment again and the risk is considered to be low, so by not transmitting information related to the authentication of the user of the terminal to the terminal, it is possible to improve user convenience while ensuring safety.

[0461] Moreover, the second embodiment shows a configuration in which the information on the IMS money includes information on the place where the payment was made with the IMS money. As an example of the effect that can be obtained by such a configuration, the server can obtain information regarding the location where a payment was made using electronic currency, and thereby transmit payment information to the terminal without transmitting information regarding the authentication of the terminal's user to the terminal.

[0462] Moreover, in the second embodiment, the information about the place where the payment was made with IMS money includes information about the store where the payment was made with IMS money. As an example of the effect that can be obtained by such a configuration, the server can obtain information about the store where the payment was made with electronic currency, and send payment information to the terminal without sending information about the authentication of the terminal's user to the terminal.

[0463] In addition, the second embodiment illustrates a configuration in which the server 10 does not send additional authentication request information (not limited to, but an example of information regarding authentication of the terminal user) to the terminal 20 via the communication I / F 14 based on the location of the store where the payment was made with IMS money and the location of the terminal 20, but sends payment result information to the terminal 20 via the communication I / F 14. As an example of the effect obtained by such a configuration, the server does not transmit information regarding the authentication of the user of the terminal to the terminal based on information regarding the store where the payment was made with electronic currency and information regarding the location of the terminal, so that the amount of communication on the server can be reduced and the load on the server can be lightened. Also, for example, if the location of the terminal is not far from the store where the user has previously made a payment with electronic currency, it is highly likely that the user is about to make a payment at the same store and the risk is considered to be low, so by not transmitting information regarding the authentication of the user of the terminal to the terminal, it is possible to improve user convenience while ensuring safety.

[0464] Moreover, the second embodiment shows a configuration in which the information related to the IMS money includes information related to the location of the store where authentication for making a payment with IMS money was performed. As an example of the effect obtained by such a configuration, the server can transmit payment information to the terminal without transmitting information regarding the authentication of the user of the terminal to the terminal by acquiring information regarding the location where authentication for electronic currency settlement was performed. Also, for example, if authentication for electronic currency settlement was performed in the past at a location where authentication is to be performed again for the same user, the risk is considered to be low, so by not transmitting information regarding the authentication of the user of the terminal to the terminal, it is possible to improve user convenience while ensuring safety.

[0465] In addition, the second embodiment illustrates a configuration in which the terminal identification information of the above-mentioned terminal 20 or information associated with the user identification information of the terminal 20 (not limited to, an example of information associated with identification information for identifying a terminal or a user of the terminal) includes information on products purchased by the user of the terminal 20. As an example of the effect that can be obtained by such a configuration, the server can obtain information regarding products purchased by the user of the terminal and transmit payment information to the terminal without transmitting information regarding the authentication of the user of the terminal to the terminal.

[0466] In addition, the second embodiment illustrates a configuration in which the server 10 does not send additional authentication request information to the terminal 20 via the communication I / F 14 based on information on the product purchased by the user of the terminal 20 and information on the product to be purchased by the user of the terminal 20, but sends payment result information to the terminal 20 via the communication I / F 14. As an example of the effect obtained by such a configuration, the server does not transmit information regarding the authentication of the user of the terminal to the terminal based on information regarding the product purchased by the user of the terminal and information regarding the product to be purchased by the user of the terminal, so that the amount of communication on the server can be reduced and the load on the server can be lightened. Also, for example, if the same product has been purchased in the past, it is highly likely that the same user is trying to purchase the same product, and the risk is considered to be low, so by not transmitting information regarding the authentication of the user of the terminal to the terminal, it is possible to improve user convenience while ensuring safety.

[0467] Moreover, the second embodiment shows a configuration in which information different from the authentication password includes information related to the store. As an example of an effect obtained by such a configuration, the server can obtain information regarding the location and transmit payment information to the terminal without transmitting information regarding authentication of the terminal's user to the terminal.

[0468] In the second embodiment, the store-related information includes information about the store where the product is purchased, and is transmitted from the store server 70 and received by the server 10 via the communication I / F 14. As an example of the effect obtained by such a configuration, the server can obtain information about the store where the product is purchased by receiving the information transmitted from the server of the store that manages the product.

[0469] In addition, the second embodiment illustrates a configuration in which the server 10 receives location information of the terminal 20 from the terminal 20 via the communication I / F 14, and based on the location information of the store where the user of the terminal 20 purchases a product and the location information of the terminal 20, does not send additional authentication request information to the terminal 20 via the communication I / F 14, but sends payment result information to the terminal 20 via the communication I / F 14. As an example of the effect obtained by such a configuration, the server does not transmit information regarding the authentication of the user of the terminal to the terminal based on information regarding the location of the store where the product is purchased and information regarding the location of the received terminal, so that the amount of communication on the server can be reduced and the load on the server can be lightened. Also, for example, if the location of the store where the product is purchased and the location of the terminal are not far from each other, it is highly likely that the user is about to make a payment at that store and the risk is considered to be low, so by not transmitting information regarding the authentication of the user of the terminal to the terminal, the convenience for the user can be improved.

[0470] Moreover, the second embodiment shows a configuration in which the information different from the authentication password includes information related to the product. As an example of the effect obtained by such a configuration, the server can obtain information regarding a product and transmit payment information to the terminal without transmitting information regarding authentication of the terminal's user to the terminal.

[0471] In addition, the second embodiment shows a configuration in which, when the product to be purchased is a daily consumer good, the server 10 does not send additional authentication request information (not limited to, but an example of information regarding authentication of the terminal user) to the terminal 20 via the communication I / F 14, but sends payment result information to the terminal 20 via the communication I / F 14. As an example of the effect obtained by such a configuration, if the information regarding a product matches the information regarding a pre-set product, the server does not send information regarding the authentication of the terminal's user to the terminal, thereby reducing the amount of communication on the server and the load on the server.

[0472] Moreover, in the second embodiment, the information about the product includes information about the total price of the product to be purchased. As an example of the effect obtained by such a configuration, the server can transmit payment information to the terminal without transmitting information related to the authentication of the user of the terminal to the terminal by acquiring information related to the total price of the goods. Also, for example, if the total price of the goods is low, the risk is considered low, so by not transmitting information related to the authentication of the user of the terminal to the terminal, it is possible to improve the convenience of the user while ensuring safety.

[0473] <Second Modification Example (1)> It is possible to combine the authentication skip judgment on the terminal 20 side described in the first embodiment with the authentication skip judgment on the server 10 side described in the second embodiment to perform composite processing, or it is not necessary to do so.

[0474] 4-7 and 4-8 are flowcharts showing an example of the flow of the processes executed by each device in this case. These figures show, from left to right, a third payment application process which is an example of payment application processing executed by the payment application processing unit 213 of the terminal 20, a third store payment process which is an example of store payment processing executed by the store payment processing unit 513 of the store code reader device 50, and a third payment management process which is an example of payment management processing executed by the payment management processing unit 113 of the server 10.

[0475] If the payment application processing unit 213 determines in A3 that the payment type is "terminal code display" (A3; terminal code display), it performs a first authentication skip determination process (H3). Then, the payment application processing unit 213 performs the processes of A11 to A17.

[0476] If it is determined in A15 that the authentication result is “OK” (A15; Yes), or if it is determined in A11 that the authentication process should be skipped (A11; Yes), the payment application processing unit 213 transmits, via the communication I / F 22, terminal display code generation request information to the server 10, which includes the user ID and authentication skip status information, which is information indicating whether the authentication process has been skipped (H15).

[0477] The payment management processing unit 113 judges whether or not terminal display code generation request information has been received from the terminal 20 via the communication I / F 14 (J1). If it is judged that the information has been received (C1; Yes), the authentication skip determination processing unit 1139 executes a fourth authentication skip determination process (J3) after carrying out the processes of C3 to C9. Note that, for the sake of distinction from the authentication skip determination processes in the other embodiments, this will be referred to as the "fourth authentication skip determination process".

[0478] In this fourth authentication skip determination process, the authentication skip determination processing unit 1139 determines whether or not the authentication process has been skipped in the terminal 20 based on the authentication skip status information included in the terminal display code generation request information received from the terminal 20.

[0479] If the authentication process has not been skipped in the terminal 20, the authentication skip determination processing unit 1139 determines that additional authentication is not required. This is because the authentication process has already been completed in the terminal 20. On the other hand, when the authentication process is skipped in the terminal 20, the authentication skip determination processing unit 1139 determines whether the authentication skip condition is satisfied based on the authentication skip condition included in the authentication skip condition data 156 in the storage unit 15. If the authentication skip condition is satisfied, it is determined that additional authentication is not required, and if the authentication skip condition is not satisfied, it is determined that additional authentication is required. This is because, although the authentication process is skipped in the terminal 20, depending on the result of the authentication skip determination by the server 10, it may be better to have the terminal 20 perform additional authentication.

[0480] As a specific example, there may be a case where, due to a difference between the settings regarding authentication skip on the terminal 20 side and the settings regarding authentication skip on the server 10 side, it is determined that the authentication process should be skipped on the terminal 20 because the amount to be paid is not high, but the server 10 determines that there is a problem (risk) in skipping the authentication process of the terminal 20 because the amount to be paid is high, and therefore the authentication skip on the terminal 20 is cancelled and additional authentication is performed.

[0481] Unlike the above, when the authentication process is skipped in the terminal 20, the server 10 may determine that additional authentication is unnecessary by trusting the judgment of the terminal 20. In this case, the server 10 does not need to make an authentication skip judgment.

[0482] If it is determined in the fourth authentication skip determination process that additional authentication is required (G3; No), the payment management processing unit 113 sends additional authentication request information to the terminal 20 via the communication I / F 14 (G5). Then, the payment management processing unit 113 receives authentication success information from the terminal 20 via the communication I / F 14 (G7), and then performs payment processing (C11). Then, the payment management processing unit 113 moves the process to C13.

[0483] After A19, the payment application processing unit 213 performs processes E1, A13 to A17, and E3, and then moves the process to A21.

[0484] <Effects of the second modified example (1)> As an example of the effect obtained by this modification, the terminal and the server can cooperate to determine whether or not to execute a display process related to authentication of the user of the terminal. Also, by transmitting information on whether or not the display process has been executed from the terminal to the server, the server can easily determine whether or not to cause the terminal to execute additional display processes.

[0485] <Second Modification Example (2)> As in the first modified example (10), the store may request the server 10 to make the terminal 20 skip the authentication process.

[0486] Figure 4-9 is a flowchart showing an example of the process flow of each device in this case, which is an excerpt of the process portion of Figure 4-5, which is the process portion when the payment type is "terminal code reading" in the process described in the second embodiment. Note that the same steps as in the previous flowcharts are given the same reference numerals and will not be described again.

[0487] When the payment management processing unit 113 receives authentication skip request information from the store code reader device 50 via the communication I / F 14 (C51), it performs processes C53 to C65. After that, when the payment management processing unit 113 receives first payment request information from the terminal 20 via the communication I / F 14 (C37), the authentication skip determination processing unit 1139 executes a fifth authentication skip determination process (G51). Note that, for the sake of distinction from the authentication skip determination processes in the other embodiments, this will be referred to as the "fifth authentication skip determination process" for convenience.

[0488] In this fifth authentication skip determination process, the authentication skip determination processor 1139 refers to the terminal reading code management database 1593 to determine whether or not authentication skip "Yes" is associated with the payment page URL accessed by the terminal 20, and if so, determines to skip the authentication process. Then, the payment management processor 113 moves the process to G3 and onwards.

[0489] <Effects of the second modified example (2)> In this modification, information different from the authentication password includes authentication skip information. As an example of the effect obtained by such a configuration, the server can easily cause the terminal to skip authentication of the user of the terminal, based on skip information for skipping authentication of the user of the terminal.

[0490] In this modification, the authentication skip information is generated by the server 10 based on the authentication skip request information transmitted from the store code reader device 50. As an example of the effect obtained by such a configuration, the server can generate skip information for causing the terminal to skip authentication of the user of the terminal, based on a request from a store that manages products.

[0491] <Second Modification Example (3)> The server 10 may or may not change the authentication skip condition based on the credit score of the user of the terminal 20.

[0492] Specifically, as an example and not by way of limitation, the server 10 may or may not lengthen the “set time” in the authentication skip condition of condition No. “SP1-1” in the authentication skip condition data 156 as the credit score of the user of the terminal 20 increases.

[0493] More specifically, as a non-limiting example, the set time when the credit score is 0 points is set to "2 hours." In addition, a threshold value of the credit score is set to an integer multiple of 10 points (10 points, 20 points, . . . , 100 points). Then, each time the credit score of the user of terminal 20 reaches the threshold value, the set time can be lengthened by one hour.

[0494] Also, by way of example and not of limitation, the server 10 may or may not increase the "daily upper limit amount" in the authentication skip condition of condition No. "SP3-1" in the authentication skip condition data 156 as the credit score of the user of the terminal 20 increases. More specifically, by way of example and not of limitation, the daily upper limit amount is set to "0 yen" when the credit score is 0 points. Also, a threshold value that is an integral multiple of 10 points (10 points, 20 points, ..., 100 points) is set as the credit score threshold. Then, each time the credit score of the user of the terminal 20 reaches the threshold, the daily upper limit amount can be increased by 5,000 yen.

[0495] Also, by way of example and not limitation, the higher the credit score of the user of terminal 20, the more likely it may be determined that the authentication process should be skipped. For example, for a user with a credit score of "90 points or more," the authentication process is skipped regardless of whether the other types of authentication skip conditions are met. Also, for a user with a credit score of "80 points or more and less than 90 points," the authentication process is skipped if any one of the other types of authentication skip conditions is met, and for a user with a credit score of "70 points or more and less than 80 points," the authentication process is skipped if any two of the other types of authentication skip conditions are met. The same applies below.

[0496] Also, as a non-limiting example, for a user whose credit score is equal to or greater than a threshold score (e.g., "60 points or more"), an authentication skip determination is made only at server 10 using the method described in the second embodiment, whereas for a user whose credit score is less than the threshold score (e.g., "less than 60 points"), an authentication skip determination may or may not be made at both terminal 20 and server 10 using the method described in the second variant example (1).

[0497] <Effects of the second modified example (3)> As an example of the effect obtained by this modification, the skip condition can be changed based on the trustworthiness of the user of the terminal. For example, the higher the trustworthiness of the user of the terminal, the easier it is to skip authentication, thereby improving the convenience for the user.

[0498] <Second Modification Example (4)> As a place where the terminal 20 performs the payment, for example, a case where a product is purchased using sales on a bullet train or a case where a meal is eaten at a moving food stall can be assumed. In this case, the location of the terminal 20 and the location of the store will each change.

[0499] Therefore, for mobile stores, the server 10 acquires store location information from the mobile store. The server 10 also acquires terminal location information from the terminal 20. Then, when judging the authentication skip condition of condition No. "SP2-5", for example, "the location of the store where the payment is to be made and the location of the terminal are not far apart", the server 10 may make the judgment based on the store location information acquired from the mobile store and the terminal location information acquired from the terminal 20.

[0500] <Effects of the second modified example (4)> As an example of the effect obtained by this modified example, even if the store moves, the server can appropriately skip authentication of the terminal user based on the location information obtained from the terminal and the location information obtained from the store.

[0501] <Third embodiment> The third embodiment is an embodiment in which the above-mentioned authentication skip information is included in the code for payment. In the third embodiment, based on the same idea as <First Modification (10)>, the authentication process of the terminal 20 is skipped by placing a risk on the store side. The difference from <First Modification (10)> is that the authentication skip information is included in the terminal reading code. The contents described in the third embodiment are applicable to any of the other embodiments. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0502] <Functional configuration> FIG. 5-1 is a diagram illustrating an example of functions realized by the control unit 11 of the server 10 in this embodiment. The payment management processing unit 113 has a terminal display code generation processing unit 1131, a terminal display code transmission processing unit 1133, a store-use payment result information transmission processing unit 1136, a terminal-use payment result information transmission processing unit 1137, and an authentication skip determination processing unit 1139, as well as a special terminal read code generation processing unit 1134 and a special terminal read code transmission processing unit 1135.

[0503] The special terminal reading code generation processing unit 1134 has a function of generating a special terminal reading code, which is a special terminal reading code including authentication skip information.

[0504] The special terminal read code transmission processing unit 1135 has a function of transmitting the special terminal read code generated by the special terminal read code generation processing unit 1134 to the terminal 20.

[0505] <Processing> Figure 5-2 is a flowchart showing an example of the process flow of each device in this embodiment, which is an excerpt of the process in Figure 3-29, which is the process when the payment type is "terminal code reading" in the process described in the first embodiment. Note that the same steps as in the previous flowcharts are given the same reference numerals and will not be described again.

[0506] If the store payment processing unit 513 determines in B5 that the payment type is not “terminal code display,” i.e., that the payment type is “terminal code reading” (B3; No), it sends special terminal reading code generation request information to the server 10 via the communication I / F 54 (M51).

[0507] Specifically, if the store is one that uses the first type terminal reading code, the store payment processing unit 513 sends to the server 10 a request information for generating a special terminal reading code, which includes, by way of example and not limitation, the store ID, sales price information for the product sold in association with the first type terminal reading code, and authentication skip request information. In addition, if the store is a store that uses second type terminal reading codes, the store payment processing unit 513 sends special terminal reading code generation request information to the server 10, which includes, by way of example and not limitation, the store ID and authentication skip request information.

[0508] Here, the authentication skip request information is the same as the authentication skip request information described in <First Modification (10)>, and is information (request information) requesting the server 10 to generate authentication skip information. As a non-limiting example, this authentication skip request information can be transmitted from the store code reader device 50 to the server 10 based on the approval of the store server 70. In other words, the authentication skip request information can also be said to be information requested by the server (store server 70) of the store where the terminal 20 makes a settlement with IMS money.

[0509] Specifically, if one's store is one that uses Type 1 terminal reading codes, then, by way of example and not limitation, sales price information for products such as boxed lunches and drinks that the store sells at a fixed price can be included in the special terminal reading code generation request information.

[0510] However, the information that can be included in the special terminal reading code generation request information is not limited to the above information. In addition to the above information, for example and without limitation, information on the product to be sold in association with the special terminal reading code (product name, product type, etc.) may or may not be included.

[0511] In addition, the above-mentioned product-related information may or may not be information about products that are less than or equal to a set amount (depending on the type of store and the products / types of products sold, for example, products that are "less than 500 yen" or "less than 500 yen," products that are "less than 1000 yen" or "less than 1000 yen"), but this may be the case.

[0512] Also, in a store that uses the first type terminal reading code, as a non-limiting example, the total amount of goods that the user of terminal 20 will purchase with IMS money may or may not be included in the special terminal reading code generation request information, such as by having a store clerk input and set the total amount of goods that the user of terminal 20 will purchase with IMS money into the store code reader device 50.

[0513] In addition, the store code reader device 50 may or may not include area information of the store's location (not limited to, but an example of location-related information) in place of or in addition to the store ID (store identification information) in the special terminal reading code generation request information and transmit it to the server 10.

[0514] In this embodiment, the store code reader device 50 is described as transmitting the request information for generating a code for reading a special terminal to the server 10. Alternatively, the store server 70 may or may not transmit the request information for generating a code for reading a special terminal to the server 10.

[0515] When the payment management processing unit 113 receives special terminal read code generation request information from the store code reader device 50 via the communication I / F 14 (N51), it performs special terminal read code generation determination processing (N53).

[0516] Specifically, as a non-limiting example, it is determined whether the store that sent the special terminal reading code generation request information is an affiliated store. Also, if the received special terminal reading code generation request information includes sales price information of the product sold in association with the first type terminal reading code, it is determined whether the sales price indicated by this sales price information is within an appropriate range (as a non-limiting example, below a threshold amount (which depends on the type of store's business and the product / product type sold, for example, "1000 yen or less," "2000 yen or less," "3000 yen or less"). Then, if these conditions are met, it is determined to generate a special terminal reading code. On the other hand, if these conditions are not met, it is determined not to generate a special terminal reading code.

[0517] If it is determined that a special terminal read code is to be generated (N55; Yes), the special terminal read code generation processing unit 1134 carries out a special terminal read code generation process (N57).

[0518] In this special terminal read code generation process, the special terminal read code generation processing unit 1134 generates a special terminal read code including access information and authentication skip information, for example and not by way of limitation. More specifically, for example, data consisting of a character string of a payment page URL and a character string of a command instructing or requesting to skip the authentication process is encoded (coded) and graphically converted to generate a special terminal read code represented by an image of a two-dimensional code.

[0519] In addition, the payment management processing unit 113 associates the sales amount (only for stores that use the first type special terminal reading code), the payment page URL, and whether or not authentication skip is enabled (here, authentication skip is enabled) with the store ID of this store, and stores the associated information in the terminal reading code management database 1593 of the code management database 159.

[0520] In addition, rather than including a command instructing or requesting that the authentication process be skipped in the special terminal reading code as the authentication skip information, a token including the authentication skip information may or may not be included in the special terminal reading code.

[0521] Thereafter, the special terminal reading code transmission processing unit 1135 transmits the special terminal reading code via the communication I / F 14 to the store code reader device 50 that transmitted the special terminal reading code generation request information (N59).

[0522] On the other hand, if it is determined that a special terminal reading code should not be generated (N55; No), the payment management processing unit 113 notifies the store code reader device 50 via the communication I / F 14 that it is not possible to generate a special terminal reading code (N61). The payment management processing unit 113 then proceeds to N63.

[0523] The store payment processing unit 513 determines whether or not a special terminal reading code has been received from the server 10 via the communication I / F 54 (M53), and if it determines that a special terminal reading code has been received (M53; Yes), it displays the received special terminal reading code on the display unit 53 (M55).

[0524] On the other hand, if the store payment processing unit 513 determines that it has received authentication skip impossible information without receiving the special terminal reading code from the server 10 via the communication I / F 54 (M53; No), it transfers the processing to B15 in FIG. 3-32.

[0525] The payment application processing unit 213 of the terminal 20 reads, with the application code reader, either the terminal reading code posted in the store or the special terminal reading code displayed on the display unit 53 of the store code reader device 50 in M55 (L51). Then, the payment application processing unit 213 performs the processes of A33 and A35.

[0526] The payment management processing unit 113 judges the payment schedule information in response to the access to the payment page from the terminal 20 (N63). Specifically, it refers to the terminal reading code management database 1593 and acquires the information stored in association with the payment page. Then, the payment management processing unit 113 transmits the payment schedule information according to the judgment result to the terminal 20 via the communication I / F 14 (N65).

[0527] In this case, if the information associated with the payment page is information about a store that uses a first type special terminal reading code, the payment management processing unit 113 sends first type planned payment information, including the store where the payment is to be made and the planned payment amount, to the terminal 20 via communication I / 14. On the other hand, if the information associated with the payment page is information about a store that uses a second type special terminal reading code, the payment management processing unit 113 sends second type planned payment information, including the store where the payment is to be made (but not the planned payment amount), to the terminal 20 via communication I / 14.

[0528] When the payment application processing unit 213 receives the payment schedule information from the server 10 via the communication I / F 22 (L53), it performs the processes of A39 and A41, and then performs a sixth authentication skip determination process (L55).

[0529] In this sixth authentication skip determination process, the authentication skip determination processing unit 2135 determines whether or not the code information acquired in the code information acquisition process of A33 includes authentication skip information. If the special terminal reading code displayed on the store code reader device 50 is read in L51, it is determined that the acquired code information includes authentication skip information, whereas if the terminal reading code posted in the store is read, it is determined that the acquired code information does not include authentication skip information. If it is determined that the acquired code information includes authentication skip information, it is determined that the authentication process is to be skipped. Then, the payment application processing unit 213 moves the process to A11.

[0530] <Effects of the third embodiment> In the third embodiment, a server 10 (not limited to, an example of an information processing device) generates a special terminal read code (not limited to, an example of code information) related to a payment of IMS money (not limited to, an example of electronic currency) by a terminal 20. The server 10 acquires information (not limited to, an example of information) such as store information and sales amount information based on special terminal read code request information. Then, the server 10 generates a special terminal read code based on the acquired information, including information related to the authentication process executed by the terminal 20 (not limited to, an example of information related to authentication of a user of the terminal). As an example of the effect obtained by such a configuration, the information processing device can easily generate code information including information related to the authentication of the user of the terminal based on the acquired information. In addition, the information related to the authentication of the user of the terminal can be acquired by the terminal via the generated code information, thereby improving the convenience for the user.

[0531] In addition, the third embodiment shows a configuration in which the above-mentioned special terminal reading code (not limited to, but an example of code information) includes information that is read by an application code reader (not limited to, but an example of a code reader) of the terminal 20. As an example of the effect obtained by such a configuration, the information processing device can generate code information including information to be read by a code reader of the terminal.

[0532] Moreover, the third embodiment shows a configuration in which the information acquired by the server 10 includes information different from the authentication password (which is not limited to this and is an example of authentication information for authenticating a user of a terminal). As an example of an effect obtained by such a configuration, the information processing device can generate code information including information related to the authentication of the user of the terminal by acquiring information different from the authentication information for authenticating the user of the terminal. In addition, since the information related to the authentication of the user of the terminal can be acquired by the terminal via the generated code information, the convenience for the user can be improved.

[0533] Moreover, the third embodiment shows a configuration in which the information different from the authentication password includes information related to a location. As an example of an effect obtained by such a configuration, the information processing device can generate code information including information related to authentication of the user of the terminal by acquiring information related to the location. In addition, since the information related to authentication of the user of the terminal can be acquired by the terminal via the generated code information, the convenience for the user can be improved.

[0534] Moreover, in the third embodiment, the information about the location includes store identification information (not limited to this, but an example of information about a store where settlement with electronic money is performed by a terminal). As an example of the effect obtained by such a configuration, the information processing device can generate code information including information regarding authentication of the user of the terminal by acquiring information regarding the store where the electronic currency settlement is performed by the terminal. In addition, since the information regarding authentication of the user of the terminal can be acquired by the terminal via the generated code information, the convenience for the user can be improved.

[0535] In addition, the third embodiment shows a configuration in which the above-mentioned special terminal reading code is generated including authentication skip information when the store is a store of a first specific industry (not limited to this, an example of a specific store) stored in the server 10. As an example of the effect obtained by such a configuration, when the store is a specific store stored in the information processing device, the information processing device can generate code information including information regarding the authentication of the user of the terminal. Also, since the information regarding the authentication of the user of the terminal can be acquired by the terminal via the generated code information, the convenience for the user can be improved.

[0536] Moreover, the third embodiment shows a configuration in which the information different from the authentication password includes information related to the product name and product type (not limited to this, but an example of information related to the product) sold in the store. As an example of the effect obtained by such a configuration, the information processing device can generate code information including information related to authentication of the user of the terminal by acquiring information related to the product. In addition, the information related to authentication of the user of the terminal can be acquired by the terminal via the generated code information, thereby improving user convenience.

[0537] Moreover, in the third embodiment, the information on the above-mentioned products includes information on products that are equal to or less than a set price. As an example of the effect obtained by such a configuration, the information processing device can generate code information including information regarding the authentication of the user of the terminal by acquiring information regarding products that are equal to or less than a set price. In this case, for example, if the price of the product purchased by the user is low, the risk is considered to be low. Therefore, by generating code information including information regarding the authentication of the user of the terminal, it is possible to ensure safety while making it possible to acquire information regarding the authentication of the user of the terminal at the terminal via the generated code information, thereby improving user convenience.

[0538] Moreover, in the third embodiment, the information on the above-mentioned products includes information on the total price of the products that the user of the terminal 20 purchases with IMS money. As an example of the effect obtained by such a configuration, the information processing device can generate code information including information regarding the authentication of the terminal user by acquiring information regarding the total price of the goods purchased by the terminal user with electronic currency. In this case, for example, if the total price of the goods purchased by the terminal user with electronic currency is low, the risk is considered to be low. Therefore, by generating code information including information regarding the authentication of the terminal user, it is possible to ensure safety while making it possible for the terminal to acquire information regarding the authentication of the terminal user via the generated code information, thereby improving user convenience.

[0539] Moreover, in the third embodiment, the information acquired by the server 10 includes authentication skip request information (not limited to this, an example of request information for requesting generation of information related to authentication of a user of a terminal). As an example of an effect obtained by such a configuration, the information processing device can generate code information including information regarding the authentication of the user of the terminal by acquiring request information requesting the generation of information regarding the authentication of the user of the terminal. In addition, since the information regarding the authentication of the user of the terminal can be acquired by the terminal via the generated code information, the convenience for the user can be improved.

[0540] In addition, the third embodiment shows a configuration in which the information acquired by the server 10 includes authentication skip request information (not limited to this, an example of request information requested by a server of a store where electronic currency settlement is performed by a terminal). As an example of the effect obtained by such a configuration, the information processing device can generate code information including information regarding authentication of the user of the terminal according to the intention of the store by acquiring request information requested by a server of the store where electronic currency settlement is performed by the terminal. Also, since information regarding authentication of the user of the terminal can be acquired by the terminal via the generated code information, convenience for the user can be improved.

[0541] In addition, the third embodiment shows a configuration in which the information including the above-mentioned special terminal reading code includes authentication skip information (not limited to this, an example of skip information for the terminal to skip authentication of the terminal user). As an example of an effect obtained by such a configuration, the information processing device can generate code information including skip information for the terminal to skip authentication of the user of the terminal, and can cause the terminal to skip authentication of the user of the terminal via the generated code information.

[0542] Moreover, in the third embodiment, the above authentication skip information includes information that allows the terminal 20 to skip the authentication process by the terminal 20 by acquiring the authentication skip information. As an example of the effect obtained by such a configuration, it is possible to cause the terminal to simply and reliably skip authentication of the user of the terminal based on the skip information included in the code information.

[0543] In addition, the third embodiment shows a configuration in which the server 10 transmits a special terminal reading code (not limited to, but an example of code information) to the store code reader device 50 via the communication I / F 14, and receives payment request information from the terminal 20 via the communication I / F 14 based on the special terminal reading code being read by the application code reader of the terminal 20. As an example of the effect obtained by such a configuration, the server can receive and obtain information regarding electronic currency settlement by the terminal based on the transmitted code information being read by the code reader of the terminal.

[0544] Moreover, the third embodiment shows a configuration in which the information different from the authentication password includes authentication skip information associated with the special terminal reading code. As an example of the effect obtained by such a configuration, the server can associate information different from the authentication information with the code information read by the code reader of the terminal.

[0545] In the third embodiment, the authentication skip information includes information generated by the store code reader device 50. As an example of the effect obtained by such a configuration, the server can associate information generated based on the store that manages the product with code information read by the code reader of the terminal.

[0546] In the third embodiment, the authentication skip information is generated based on request information transmitted from the store code reader device 50. In the third embodiment, the authentication skip information is generated based on request information transmitted from the store code reader device 50. As an example of the effect obtained by such a configuration, the server can generate information to be associated with the code information, based on a request from a store that manages products.

[0547] <Third Modification (1)> In the third embodiment, the server 10 generates a special terminal reading code including authentication skip information, but this is not limited to this. As a non-limiting example, the server 10 can generate a special terminal reading code including information used by the terminal 20 to skip authentication of the user of the terminal 20, that is, information required for the terminal 20 to make an authentication skip determination.

[0548] Specifically, as an example and not by way of limitation, server 10, upon request from a store, in the special terminal read code generation process, can generate a special terminal read code including various information such as information regarding the price of the product that the user of terminal 20 plans to purchase with IMS money, information regarding the product that the user of terminal 20 plans to purchase with IMS money, information regarding the region (area) in which the user of terminal 20 will make payment with IMS money, and information regarding the store where the user of terminal 20 will purchase the product with IMS money.

[0549] For example, based on the operation of a store clerk, the store code reader device 50 includes the prices of the products that the user of the terminal 20 plans to purchase and their total amount as a planned payment amount in the special terminal read code generation request information and transmits it to the server 10. The server 10 then generates a special terminal read code including the planned payment amount contained in the special terminal read code generation request information received from the store code reader device 50.

[0550] Also, for example, the store code reader device 50, based on an operation by a store clerk, transmits to the server 10 special terminal read code generation request information including product identification information for identifying the product purchased by the user of the terminal 20 and product type identification information for identifying the product type. The server 10 then generates a special terminal read code including the product identification information or product type identification information included in the special terminal read code generation request information received from the store code reader device 50.

[0551] Also, for example, the store code reader device 50 transmits information such as area information of the location of its own store and its own store identification information (store ID) that are stored in advance in its own device, together with special terminal read code generation request information to the server 10. Then, the server 10 generates a special terminal read code by including the area information and store identification information contained in the special terminal read code generation request information received from the store code reader device 50.

[0552] The special terminal reading code generated by the server 10 in this manner is transmitted to the store code reader device 50, displayed thereon, and read by the terminal 20, as described above. The terminal 20 can make an authentication skip determination based on various information acquired by decoding data from the read special terminal reading code. The method of determining whether or not to skip authentication by the terminal 20 may or may not be based on the description of the above-mentioned embodiment and modified examples.

[0553] <Effects of the third modified example (1)> In this modified example, the information included in the special terminal reading code includes information used by the terminal 20 to skip authentication of the user of the terminal 20 . As an example of the effect obtained by such a configuration, the server can generate code information including information used by the terminal to skip authentication of the user of the terminal. Also, the information used by the terminal to skip authentication of the user of the terminal can be obtained by the terminal via the generated code information, and based on this information, the terminal can easily determine whether or not to skip authentication of the user.

[0554] In addition, this modified example shows a configuration in which the information included in the special terminal reading code includes information about the product that the user of the terminal 20 purchases with IMS money. As an example of the effect obtained by such a configuration, the server can generate code information including information about the product that the user of the terminal purchases with the electronic currency. Also, the generated code information can be used to enable the terminal to obtain information about the product that the user of the terminal purchases with the electronic currency, and for example, the terminal can easily determine whether or not to skip user authentication based on the product that the user purchases.

[0555] In addition, this modification shows a configuration in which the information on the product purchased by the user of the terminal 20 with IMS money includes information on the price of the product purchased by the user of the terminal 20 with IMS money. As an example of the effect obtained by such a configuration, the server can generate code information including information on the price of the product. Also, the information on the price of the product can be obtained by the terminal via the generated code information, and for example, the terminal can easily determine whether or not to skip user authentication based on the price of the product purchased by the user.

[0556] Furthermore, in this modified example, the information included in the special terminal reading code includes information regarding the region (area) in which the user of the terminal 20 makes the payment. As an example of the effect obtained by such a configuration, the server can generate code information including information about a location. Also, the information about the location can be acquired by the terminal via the generated code information, and for example, the terminal can easily determine whether or not to skip user authentication based on the area where the user makes a payment or the location of a store.

[0557] In addition, this modified example shows a configuration in which the information included in the special terminal reading code includes information about the store where the user of the terminal 20 purchases the product. As an example of the effect obtained by such a configuration, the server can generate code information including information about the store where the product is purchased. Also, the information about the store where the product is purchased can be acquired by the terminal via the generated code information, and for example, the terminal can easily determine whether or not to skip user authentication based on the store where the user purchases the product.

[0558] <Third Modification (2)> In the third embodiment, the server 10 generates a special terminal reading code including authentication skip information, but this is not limited to this. Specifically, as a non-limiting example, the terminal 20 can generate a terminal display code used in the payment type "terminal display code" and including authentication skip information (hereinafter referred to as "special terminal display code").

[0559] 5-3 and 5-4 are flowcharts showing an example of the process flow of each device in this case. Note that the same steps as those in the previous flowcharts are given the same reference numerals and will not be described again.

[0560] If the payment application processing unit 213 determines in A3 that the payment type is "terminal code display" (A3; terminal code display), it performs a first authentication skip determination process (H3). Then, the payment application processing unit 213 performs the processes of A11 to A17.

[0561] If it is determined in A15 that the authentication result is "OK" (A15; Yes), or if it is determined in A11 that the authentication process is to be skipped (A11; Yes), the payment application processing unit 213 performs a special terminal display code generation process (P15). Specifically, as a non-limiting example, it generates a special terminal display code that includes authentication skip status information, which is information on whether the authentication process was skipped in terminal 20. Then, the payment application processing unit 213 causes the generated special terminal display code to be displayed on the display unit 24 (P19).

[0562] The store payment processing unit 513 causes the code reader 58 to read the special terminal display code displayed on the display unit 24 of the terminal 20 (Q9). Then, the store payment processing unit 513 performs a code information acquisition process to acquire information contained in the read special terminal display code (Q11),...

Claims

1. A program executed by a server that manages electronic currency settlement by a terminal, receiving information regarding electronic currency settlement by the terminal through a communication unit of the server; transmitting, to the terminal by the communication unit, additional authentication request information for causing the terminal to execute an authentication process for authenticating the user of the terminal, when the balance of the electronic currency is equal to or greater than a set amount based on information related to the balance of the electronic currency associated with the terminal or the user of the terminal; receiving, by the communication unit, information indicating that a user of the terminal has been authenticated by the terminal; The server executes the process of transmitting payment information indicating that payment has been made using the electronic currency to the terminal via the communication unit based on information indicating that the user of the terminal has been authenticated.

2. The program according to claim 1, When the electronic currency in the terminal is set to be automatically deposited into the terminal when the electronic currency in the terminal falls below a set amount or is less than the set amount, or when the balance of the electronic currency is equal to or greater than a set amount, the server transmits the additional authentication request information to the terminal via the communication unit.

3. The program according to claim 1 or 2, The server executes the step of transmitting the additional authentication request information to the terminal via the communication unit based on information regarding the balance of electronic currency associated with the terminal or the user of the terminal, as well as information regarding payment using electronic currency associated with the terminal or the user of the terminal.

4. The program according to claim 3, The information regarding payments using electronic currency includes information regarding the frequency or number of times payments using electronic currency have been made.

5. The program according to claim 3, The information relating to the payment by electronic currency includes information relating to the time when the payment by electronic currency was made.

6. The program according to claim 5, The additional authentication request information is transmitted to the terminal by the communication unit if the time has passed outside a set period of time from the time the payment was made.

7. The program according to claim 3, The information relating to the payment by electronic currency includes information relating to the location where the payment by electronic currency is made.

8. The program according to claim 7, The information regarding the place where the payment was made with the electronic currency includes information regarding the store where the payment was made with the electronic currency.

9. The program according to claim 8, The information about the store includes information about a location of the store, The additional authentication request information is transmitted to the terminal by the communication unit when the location of the store does not match the location of the terminal.

10. The program according to claim 3, The information relating to the electronic currency settlement includes information relating to the location where the authentication for the electronic currency settlement was performed.

11. The program according to any one of claims 1 to 10, The additional authentication request information is transmitted to the terminal by the communication unit when a product purchased by the user of the terminal does not match a product to be purchased by the user of the terminal.

12. The program according to any one of claims 1 to 11, The server transmits the additional authentication request information to the terminal via the communication unit based on information about a store where the product is purchased; If the store where the product is to be purchased is not the set store, the additional authentication request information is transmitted to the terminal by the communication unit.

13. The program according to claim 12, Information about the store where the product is purchased is transmitted from a store server of the store that manages the product, and is received by the communication unit.

14. The program according to any one of claims 1 to 13, transmitting the additional authentication request information to the terminal by the communication unit based on information regarding the location of the store where the product is purchased; receiving information about the location of the terminal by the communication unit, The additional authentication request information is transmitted to the terminal by the communication unit when the location of the store does not match the location of the terminal.

15. The program according to any one of claims 1 to 14, The server transmits the additional authentication request information to the terminal through the communication unit based on information about the product; The additional authentication request information is transmitted to the terminal by the communication unit when the product does not match a preset product.

16. The program according to any one of claims 1 to 15, The server transmits the additional authentication request information to the terminal via the communication unit based on information about a total price of the product; The additional authentication request information is transmitted to the terminal by the communication unit when the total amount of the merchandise is equal to or greater than a set amount.

17. An information processing method for a server that manages electronic currency settlement by a terminal, comprising: receiving information regarding electronic currency settlement by the terminal through a communication unit of the server; transmitting, to the terminal by the communication unit, additional authentication request information for causing the terminal to execute an authentication process for authenticating the user of the terminal, when the balance of the electronic currency is equal to or greater than a set amount based on information related to the balance of the electronic currency associated with the terminal or the user of the terminal; receiving, by the communication unit, information indicating that a user of the terminal has been authenticated by the terminal; The method includes transmitting, to the terminal, payment information indicating that payment has been made using the electronic currency, based on information indicating that the user of the terminal has been authenticated, via the communication unit.

18. A server that manages electronic currency settlement by a terminal, The communication unit receives information regarding electronic currency payment by the terminal, and if the balance of the electronic currency is equal to or greater than a set amount based on information regarding the balance of electronic currency associated with the terminal or a user of the terminal, sends additional authentication request information to the terminal to cause the terminal to execute an authentication process to authenticate the user of the terminal, receives information indicating that the user of the terminal has been authenticated by the terminal, and sends payment information to the terminal indicating that payment has been made using the electronic currency based on the information indicating that the user of the terminal has been authenticated.

Citation Information

Patent Citations

  • Mobile phone

    JP2002176671A

  • Settlement method and settlement system

    JP2006268302A

  • Information processor, settlement system, settlement method and program

    JP2009217489A

  • False use preventing method of electronic money, electronic money settling system, mobile terminal, and electronic settling device

    WO2006109574A1

  • Information accessing device, computer program, information processing system, access control system, mobile terminal, method for controlling mobile terminal, and program for controlling mobile terminal

    WO2014103543A1