Application program, electronic settlement method, and terminal

Abstract

To more flexibly achieve electronic settlement.SOLUTION: Causing a display unit of the terminal to display an online code image generated using a one time code acquired from a settlement server through communication when a state of the settlement server is a first state in which the state of the settlement server is normal, and causing the display unit of the terminal to generate an offline code image using an offline key acquired from the settlement server at a lower frequency than the one time code when the state of the settlement server is a second state in which the state of the settlement server is not normal; A process of displaying the offline code image on a display unit of the terminal.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an application program, an electronic payment method, and a terminal device. [Background technology]

[0002] A form of electronic payment in which a payment app running on a terminal device such as a smartphone displays a code image and a store device reads information from the code image is becoming widespread (Patent Document 1). In this form of electronic payment, a one-time code issued by a payment server in association with a user's account is used as the original information to be displayed on the code image. The use of the one-time code eliminates the need to include personal information, etc. in the code image, thereby improving security. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7237224 Summary of the Invention [Problem to be solved by the invention]

[0004] In the electronic payment of the above-described aspect, when an electronic payment is to be made, a request for a one-time code is sent from the payment app to the payment server, and a one-time code is issued in response. Therefore, in conventional technology, depending on the communication situation at the time of electronic payment, a valid one-time code may not be obtained, making the electronic payment impossible.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide an application program, an electronic payment method, and a terminal device that can enable electronic payments to be realized more flexibly. [Means for solving the problem]

[0006] One aspect of the present invention is an application program that operates on a user's terminal device and works in cooperation with a payment server to provide electronic payment services to the user, wherein when the payment server is in a normal first state, the application program causes an online code image generated using a one-time code obtained by communication from the payment server to be displayed on a display unit of the terminal device, and when the payment server is in an abnormal second state, the application program causes an offline code image to be generated using an offline key obtained from the payment server less frequently than the one-time code, and displays the offline code image on a display unit of the terminal device. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide an application program, an electronic payment method, and a terminal device that enable more flexible electronic payment. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] 1 is a configuration diagram of a payment server 100 according to an embodiment. [Figure 5] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 10 is a diagram showing an example of a top screen IM1 of payment application 20. [Figure 8] FIG. 10 is a sequence diagram illustrating a flow of processing performed for offline payment. [Figure 9] 10 is a flowchart showing an example of a processing flow related to screen control by payment application 20. [Figure 10] 10 is an interface screen displayed in a second state. [Figure 11] 10 is another interface screen displayed in the second state. [Figure 12] 10 is an example of an interface screen displayed in a second state. [Figure 13] 10 is a flowchart showing an example of the flow of processing executed by payment application 20. DETAILED DESCRIPTION OF THE INVENTION

[0009] Below, with reference to the drawings, embodiments of the application program, electronic payment method, and terminal device of the present invention will be described. Various devices, such as the "server" mentioned below, that provide services to users and perform internal analysis may be realized by a group of distributed devices, and each device may be operated by a different business. Furthermore, the hardware owner (the cloud server provider) and the business that actually operates the device may also be different. The application program and payment server work together to provide the electronic payment service. In the following description, the application program is referred to as a payment app. The electronic payment service is a service that supports payments for the purchase of goods and services at a store. A store is, for example, a physical store (real-world store) that exists in real space, but may also include a virtual store for e-commerce. Virtual stores may also include stores provided by entities other than the operator of the electronic payment service. In such cases, the user may be controlled to transition to an interface screen for the electronic payment service when making a payment for a purchase at the virtual store. In an electronic payment service, a store is treated as belonging to, for example, a member store (brand), and when a purchase is made at a store, processing such as payment is primarily conducted between the user and the member store. Alternatively, processing such as payment may be conducted between the user and the store.

[0010] [Electronic payment service] FIG. 1 shows an example of the configuration of an electronic payment system in which an electronic payment service is realized. The electronic payment service is realized mainly by a payment server 100. An electronic payment system that realizes the electronic payment service includes, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, and the payment server 100. These devices communicate, for example, via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, etc. Some or all of the functional components included in the electronic payment system may be distributed in any form across multiple devices, or may be integrated into any device.

[0011] [User terminal device] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment app 20, which operates in cooperation with the payment server 100 to provide electronic payment services to users. The payment app 20 is installed on the user terminal device 10 from, for example, an application store, and controls the camera, communication device, touch panel, etc.

[0012] [First store terminal device] The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device. The store code image 60 is placed in the store and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0013] [Second store terminal device] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, tablet terminal, personal computer, etc. An interface for affiliated stores 72 runs on the second store terminal device 70. The interface for affiliated stores 72 may be an app for affiliated stores or a browser. The interface for affiliated stores 72 accepts coupon settings and the like from the operator of the affiliated store and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image and reading the code image displayed by the user terminal device 10 by executing the app for affiliated stores.

[0014] [Payment server] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, this distinction will not be made and it is assumed that payment information is sent from the first store terminal device 50.

[0015] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns for electronic payment: Pattern 1 and Pattern 2.

[0016] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10, with the payment application 20 running, decodes the store code image 60 using its optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is the domain of the electronic payment service to which store identification information has been added, and is associated with an affiliated store ID, store ID, etc. in the payment server 100 (described below). The payment application 20 sends first payment information including the store URL and account ID to the payment server 100 (S2). The payment server 100 searches for store information (described below) using the affiliated store ID and store ID corresponding to the store URL, acquires the affiliated store name and store name information (S3), and sends this to the payment application 20 (S4). The user enters the payment amount into the user terminal device 10 on the screen displaying the affiliated store name and store name (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount and sends it to the payment server 100 (S6). The payment server 100 makes the electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notice (information for displaying a payment completion screen) to the payment app 20 (S8), and the payment app 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include information on the payment amount in addition to the store URL. In this case, the step of the user inputting the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0017] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, the payment app 20 sends a request to issue a one-time code to the payment server 100 when the payment app 20 is launched, when a payment operation is performed in the payment app 20, at the automatic update timing (e.g., every minute), and at other timings (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image, such as a QR code or barcode, generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first in-store terminal device 50, and the first in-store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). The first in-store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode, manually entering it, etc. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs electronic payment (S17). Then, the payment server 100 sends a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0018] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuing a one-time code may be omitted in store scanning, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0019] [Payment server functional configuration] 4 is a configuration diagram of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a content providing unit 120, a payment processing unit 130, an information management unit 140, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), a GPU (Graphics Processing Unit), or an SOC (System On Chip), or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0020] The storage unit 170 is a HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172, content information 174, affiliated store / shop information 176, and credit card payment information 178. Some of this information may be stored in the storage unit of the user terminal device 10. Details of each piece of information will be described later.

[0021] The communication unit 110 is a communication interface for connecting to the network NW, and is, for example, a network interface card.

[0022] The content providing unit 120 has, for example, a web server function, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The content providing unit 120 reads out necessary content from the content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs from the user while content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100. The above content may be generated by the payment application 20. In this case, the content providing unit 120 provides the payment application 20 with information necessary for generating the content.

[0023] The payment processing unit 130 performs payment processing based on the payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0024] FIG. 5 is a diagram showing an example of the contents of user information 172. User information 172 is an example of user registration information. User information 172 includes, for example, a user URL, account ID, telephone number, and password, as well as associated information such as email address, user ID, name, address, date of birth, registration date, charge balance, credit card payment settings, credit card limit, credit card payment amount, available credit card payment amount, payment method settings, bank account, credit card number, charge history information, and payment history information. The user URL is used for remittance processing between users. Registration of a telephone number and password is required when registering for an electronic payment service. The account ID is issued to the user by the payment server 100, and the user ID can be set by the user (or does not have to be set). Similarly, the email address, name, address, and date of birth can be set by the user (or do not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0025] The charge balance is information indicating the balance of electronic money set by the user by transferring funds to the account in advance. Transfer methods include transfer from a designated service provider (bank) ATM (Automatic Teller Machine) or transfer from a registered bank account. The credit payment setting is information indicating whether the settings for enabling electronic credit payments using the payment app 20 have been completed and is set to either "completed" or "not completed." The credit payment limit is the monthly credit payment limit, the credit payment usage amount is the amount of credit payments already used in the current month, and the available credit payment amount is the amount of credit payments available in the current month, calculated by subtracting the credit payment usage amount from the credit payment limit. While the figure shows only one credit payment limit, in reality, there may also be daily limits, and the lower of these may be set as the credit payment limit. Further details of credit payments will be described later. The payment method setting is setting information indicating whether the user will make electronic payments using the charge balance or by credit payment at that time. The bank account and credit card number are information on the bank account or credit card number (account number, card number) that can be used to deposit funds into the electronic payment service. The charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. The payment history information is information that shows the breakdown of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0026] 6 is a diagram showing an example of the contents of affiliated store / store information 176. The affiliated store / store information 176 includes, for example, a first table 176A in which an affiliated store ID and a store ID are associated with a store URL, a second table 176B in which an affiliated store ID is associated with an affiliated store name and sales amount (described above), and a third table 176C in which a store ID is associated with a store name. In addition to this information, the affiliated store / store information 176 may also include information such as the category of the affiliated store or store, the store's location, and payment patterns.

[0027] The information management unit 140 acquires information provided by other server devices and terminal devices. The information management unit 140 manages user information 172 and affiliated store / store information 176 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds new records to, edits, deletes, etc., the user information 172 and affiliated store / store information 176.

[0028] [Electronic Payment] When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 references the user information 172 to acquire the "payment method setting" of the user. For users whose "payment method setting" is set to "charge balance," the payment processing unit 130 performs electronic payment as follows: For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales proceeds. The item value of the affiliated store's sales proceeds is not itself used as electronic money, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0029] The payment processing unit 130 performs electronic payments for users whose "setting information" is set to "Credit card payment (Credit card payment using code information)" as follows. Credit card payment is a payment method in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service. The operator of the electronic payment service acts as the creditor, and allows electronic payments within the credit card payment limit, independent of the remaining balance. To receive the credit card payment service, a user may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used for credit card payment is settled in full for one month on the payment date of the following month, for example, by debit from a bank account. In this case, the payment processing unit 130 makes a provisional payment by adding the payment amount to the credit card payment amount and subtracting the same amount from the available credit card balance. On the closing date, the payment processing unit 130 performs the process described above to debit the current month's payment on the payment date of the following month, or requests the operator of the credit card company to perform this process. If the payment amount exceeds the available credit card balance at the time of provisional payment, an error notification is returned to the payment application 20.

[0030] [overview] When the payment server 100 is in a first normal state, the payment application 20 causes the display unit of the user terminal device 10 to display an online code image generated using a one-time code acquired by communication from the payment server 100. When the payment server 100 is in a second abnormal state, the payment application 20 causes the display unit of the user terminal device 10 to generate an offline code image using an offline key acquired from the payment server 100 less frequently than the one-time code.

[0031] The first state is a state in which the payment application 20 can communicate with the payment server 100 and obtain a one-time code from the payment server 100.

[0032] The second state is a state in which the payment application 20 cannot communicate with the payment server 100 and obtain a one-time code from the payment server 100. The second state may be, for example, a state in which the payment application 20 has difficulty connecting to the network NW, a state in which communication with the network NW is unstable, or a state in which the above communication state is an error. The instability means that information cannot be sent or received, or the communication speed is below a threshold.

[0033] The second state may be a state in which the payment server 100 cannot provide a one-time code in response to a request from the payment application 20. The second state is determined based on the result of communication between the payment application 20 and the payment server 100. For example, the payment application 20 acquires information indicating the state of the payment server 100 from the payment server 100, and determines the second state based on this information. The second state is a state in which the payment application 20 can communicate with the payment server 100, but the payment server 100 cannot send the one-time code to the application program (for example, a state in which the code cannot be sent within a predetermined time). The second state is also a state in which the payment application 20 can communicate with the payment server 100, but the payment server 100 is inhibited from sending the one-time code.

[0034] The second state is, for example, a state in which the processing load of the payment server 100 is equal to or greater than a threshold, a state in which the payment server 100 is restricting network traffic, a state in which the payment server 100 is in an error state, a state in which a session out error is returned from the payment server 100, a state in which an error has occurred related to the circuit breaker of the payment server 100, or a state in which another error has occurred related to the payment server 100. Thus, in this embodiment, the second state is a state in which the payment server 100 cannot send a one-time code in addition to (or instead of) a case in which communication is difficult.

[0035] [Switching between charge balance and deferred payment (when paying online)] FIG. 7 is a diagram showing an example of the top screen IM1 of the payment app 20. The illustrated state assumes that the payment app 20 or the payment server 100 is in the first state (a state where online payment is possible). In the first state, a valid one-time code is provided to the payment app 20 from the payment server 100. "Valid" means that the code is generated in response to the most recently issued one-time code issuance request. The top screen IM1 displays a code image CD. The code image CD may include, for example, a barcode or a QR code. By sliding a specific area on the top screen IM1, the user can switch between electronic payment using the remaining balance or electronic payment by credit card. When the user operates the "Pay" button B1, the screen transitions to a payment screen that displays the code image used for electronic payment and the available balance. The payment screen displays an enlarged version of the code image CD.

[0036] [Offline payment] The following describes electronic payment (offline payment) in the second state in which payment application 20 cannot acquire a valid one-time code. Offline payment in this embodiment can be performed at the store where store scanning is performed as described above.

[0037] The payment application 20 determines whether to perform online or offline payment depending on whether the state is the first state or the second state. For example, the payment application 20 determines that the state is the second state if an event occurs n times or more where a response to a one-time code issuance request does not arrive within a predetermined time (n is an integer equal to or greater than 1). If the payment application 20 determines that the state is the second state, it generates an offline code using the time measured by the user terminal device 10 and a secret key (offline key), generates an offline code image based on the offline code, and displays the offline code image on the display unit of the user terminal device 10. In other words, the payment application 20 generates the offline code image based on the offline code that it generated itself without using a one-time code.

[0038] The secret key is obtained from the payment server 100 to the payment application 20 less frequently than the one-time code. For example, the activated payment application 20 obtains the secret key approximately once a week. In this obtaining process, a secret key issuance request may be sent from the payment application 20 to the payment server 100, or the payment server 100 may voluntarily provide the secret key to the payment application 20.

[0039] Payment application 20 may generate an offline code using a user identification token in addition to the time and the secret key. The user identification token may be fixedly assigned to the user, or may be sent from payment server 100 together with the secret key issuance request. An example of an offline key is one that includes one or both of the secret key and the user identification token.

[0040] For example, payment application 20 generates the offline code based on data obtained by inputting the secret key and time into a predetermined function and combining the data with the user identification token. This method is merely an example, and payment application 20 may generate the offline code using any decryptable method based on some or all of the secret key, time, and user identification token.

[0041] Furthermore, payment application 20 may cause user terminal device 10 to synchronize the time measured by user terminal device 10 with the time measured by payment server 100 at a predetermined timing (for example, each time a secret key issuance request is made). At this time, payment application 20 may perform a process of adjusting the time of a radio clock or the like at approximately the same time as payment server 100.

[0042] When the offline code image is read by the first store terminal device 50 and payment information including at least a portion of the read information and the payment amount is acquired (if the information includes information based on the offline code image generated by the payment application 20 using time), the payment processing unit 130 of the payment server 100 proceeds with electronic payment based on the payment information if the offline authentication conditions are met. In other words, the offline payment proceeds. "At least a portion of the read information" means "at least a portion of the offline code," and will be referred to simply as the offline code below.

[0043] The offline authentication condition is related to the offline code image generated by payment application 20 based on the offline code. For example, the offline authentication condition includes that the time read from the offline code image (hereinafter, application time) is within a predetermined range compared with the time measured by payment server 100 (hereinafter, server time). The offline authentication condition may include that the offline key (one or both of the secret key and the user identification token) is stored in storage unit 170 as having been provided to payment application 20.

[0044] The time used in offline payment is measured in minutes, for example, but is not limited to this. When the payment processing unit 130 acquires the payment information, it identifies a secret key from the user identification token included in the offline code included in the payment information, and generates an offline code using the identified secret key and the current time measured by the payment server 100 in the same manner as the payment app 20. If the offline code acquired from the first store terminal device 50 matches the code it generated, it determines that the offline code is valid.

[0045] For example, in case there is a time difference between the user terminal device 10 and the payment server 100, the payment processing unit 130 generates multiple codes within a specified range of the current time measured by the payment server 100 plus or minus a specified time (for example, 1 minute), and if any of these codes matches the offline code obtained from the store terminal device, it determines that the offline authentication conditions are met, i.e., that the payment information is legitimate.

[0046] The payment processing unit 130 may set a lower upper limit on the payment amount for a single electronic payment when performing an offline payment (when the payment information includes information obtained from an offline code image) than when performing an online payment (when the payment information includes information based on a one-time code). The payment processing unit 130 may set a fixed upper limit on the payment amount for offline payments that is lower than that for online payments, or may dynamically determine the upper limit based on the user's payment history, etc. In the latter case, the payment processing unit 130 determines the upper limit based on the user's past frequency of electronic payments, the amount paid per transaction, the tendency of the category of payment items, etc. When performing an offline payment, if payment information for an amount exceeding the upper limit is obtained from the payment app 20, the payment processing unit 130 sends an error message to the first store terminal device 50 and, after communication with the user terminal device 10 is restored, also sends an error message to the user terminal device 10.

[0047] 8 is a sequence diagram illustrating the flow of processing performed for offline payment. First, at a timing unrelated to electronic payment, the payment application 20 sends a request to issue an offline key to the payment server 100 (S21). The payment server 100 generates an offline key (S22) and sends it to the payment application 20 (S23). The payment application 20 stores the received offline key in the memory of the user terminal device 10.

[0048] At another time, when a user launches the payment app 20 or performs a payment operation using the payment app 20 at a store where store scanning is performed, the payment app 20 sends a one-time code issuance request to the payment server 100 (S31). If an event occurs n or more times where a response to the one-time code issuance request does not arrive within a predetermined time, the payment app 20 generates an offline code and displays an offline code image generated based on the offline code (S32). Instead of an event where a response to the one-time code issuance request does not arrive within a predetermined time, the payment app 20 may determine whether or not the state is a second state, and if the state is the second state, display the offline code image. For example, the payment app 20 determines whether or not the state is the second state based on information obtained from the payment server 100. The user holds (presents) the display surface of the user terminal device 10 over (presents) the first store terminal device 50, and the first store terminal device 50 decodes the code image using its optical reading function and acquires an offline key, etc. (S33).

[0049] The first store terminal device 50 then generates payment information including the offline key, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S33). The payment server 100 identifies the user corresponding to the user identification token based on the received information, determines whether the offline authentication conditions are met as described above (S34), and proceeds with the electronic payment if the offline authentication conditions are met (S35). In this case, information notifying the completion of the payment is also transmitted exclusively to the first store terminal device 50.

[0050] According to the above process, electronic payment can be made more flexibly even when payment application 20 cannot obtain a one-time code from payment server 100. Furthermore, even in offline payments, by proceeding with electronic payment without including user identification information such as an account ID in the offline code, the level of protection of the user's personal information can be prevented from being reduced.

[0051] Furthermore, generating an offline code using both the time and the offline key and performing an offline payment can increase the probability that the payment is legitimate. If an offline code is generated using only the offline key and an offline payment is performed, it becomes impossible to know when the offline code was generated, thereby reducing the legitimacy of the payment. Furthermore, if an offline code is generated using only the time and an offline payment is performed, anyone can generate an offline code if the logic for generating the offline code is exposed. Generating an offline code image using both of these allows the timing of the offline code's generation to be known, and including the offline key in the offline code ensures that it is based on information issued by the payment server 100. As a result, the probability that the payment is legitimate can be increased.

[0052] Furthermore, by setting the upper limit for offline payments lower than that for online payments, more secure electronic payments can be realized.

[0053] [flowchart] 9 is a flowchart showing an example of the flow of processing related to screen control by the payment application 20. The processing of this flowchart is started in various situations where communication with the payment server 100 occurs.

[0054] First, payment application 20 determines whether it is in the second state (S100). For example, it determines whether it is in a state where a one-time password cannot be received in response to the one-time password issuance request described above. If it is not in the second state (if it is in the first state), payment application 20 displays an online code image in online mode and continues normal operation (S102).

[0055] In the second state, payment application 20 determines whether a valid offline key (secret key and user identification token) has been acquired and stored in the memory of user terminal device 10 (S104). A valid offline key is, for example, an offline key for which the elapsed time since acquisition has not exceeded an upper limit time (a time approximately equivalent to the issuance cycle of the offline key).

[0056] If a valid offline key has not been acquired, payment application 20 causes an error screen to be displayed on user terminal device 10 (S106). The error screen includes text explaining that the second state has occurred.

[0057] If a valid offline key has been acquired, payment application 20 executes a predetermined process (S108), generates content, and displays the generated content on the display unit of user terminal device 10 (S110). For example, payment application 20 displays an offline code image on user terminal device 10.

[0058] [Outline of prescribed process] The payment application 20 performs the following process. (1) Based on the content of the processing of the payment app 20 in the second state, the payment app 20 determines whether to display the offline code image on the display unit in response to a user operation or under the control of the payment app 20.

[0059] The payment application 20 refers to the correspondence information and determines whether to display the offline code image on the display unit in response to a user operation or under the control of the payment application 20. The correspondence information is information that associates the content of the processing of the payment application 20 with information indicating whether to display the offline code image on the display unit in response to a user operation or information indicating whether to display the offline code image on the display unit under the control of the payment application 20.

[0060] (2) Based on the interface screen that the payment app 20 displays on the display unit when in the second state, the payment app 20 determines whether to display the offline code image on the display unit through user operation or through control by the payment app 20.

[0061] The payment application 20 refers to the correspondence information and determines whether to display the offline code image on the display unit in response to a user operation or under the control of the payment application 20. The correspondence information is information that associates information about an interface screen that the payment application 20 displays on the display unit with information indicating whether to display the offline code image on the display unit in response to a user operation or information indicating whether to display the offline code image on the display unit under the control of the payment application 20.

[0062] The correspondence information may be information in which one or both of the content of processing by the payment app 20 and information related to an interface screen to be displayed on the display unit by the payment app 20 are associated with information indicating whether to display an offline code image on the display unit in response to a user operation or information indicating whether to display an offline code image on the display unit under the control of the payment app 20. The payment app 20 refers to the correspondence information and determines whether to display an offline code image on the display unit in response to a user operation or under the control of the payment app 20.

[0063] [Details of the specified process] (A) A process for displaying an offline code image on the display unit in response to a user operation will be described. When the payment app 20 is in the second state and the offline code image is displayed on the display unit in response to a user operation, the payment app 20 displays an interface screen (IM11 in FIG. 10, IM13 in FIG. 11) on the display unit that accepts an operation to transition to offline mode in which electronic payment using the offline code image is made. The offline mode is a mode in which an offline code image is displayed on the display unit in order to make electronic payment using the offline code image. The above phrase "displaying an offline code image on the display unit in response to a user operation" includes the payment app 20 determining or judging that the online code image is not available in the current processing status or the displayed interface screen, and that the use of the offline code image is triggered by the user operation.

[0064] In response to a user's operation to switch to offline mode on the interface screen, payment application 20 switches the electronic payment mode to offline mode and displays an offline code image on the display unit. IM12 in Figures 10 and 11 (described later) is a screen that is displayed upon switching to offline mode. The code information in IM12 in Figures 10 and 11 and IM22 in Figure 12 is an example of an offline code image.

[0065] When the payment application 20 transitions to offline mode, it displays an interface screen (IM12 in Figures 10 and 11) on the display unit indicating that it is in offline mode, and when an operation to display an offline code image is performed on the interface screen (for example, when the payment button is operated), it displays the offline code image on the display unit.

[0066] FIG. 10 shows an interface screen displayed in the second state. Interface screen IM11 includes a half sheet containing information indicating that an error has occurred due to the second state, a "Close" button, and the like. When the user operates the "Close" button (when an active operation is performed), payment application 20 displays interface screen IM12 on the display unit. Interface screen IM12 is a screen that is displayed upon transition to offline mode. When the payment button is operated on interface screen IM12, payment application 20 displays interface screen IM22 of FIG. 12, which will be described later, on the display unit. Interface screen IM22 is an interface screen that includes an offline code image.

[0067] For example, if the control or processing of the payment application 20 becomes stuck due to the second state, the payment application 20 displays the interface screen IM11. In this case, when the "Close" button is pressed, this operation triggers the payment application 20 to display the interface screen IM12. Triggered by the above operation, the payment application 20 decides to use the offline code image.

[0068] 11 shows another interface screen displayed in the second state. Interface screen IM13 includes a half sheet including information indicating the second state and a button for instructing "display offline code image." When the user operates the "display offline code image" button (actively operates), payment application 20 displays interface screen IM12 on the display unit.

[0069] 10 and 11, after the display of interface screen IM11 or IM13, the display of interface screen IM12 may be omitted and interface screen IM22 of Fig. 12 may be displayed instead. Whether interface screen IM11 of Fig. 10 or interface screen IM13 of Fig. 11 is displayed depends on the processing status of payment application 20 or the interface screen being displayed. This determination is also made by referring to the correspondence information described above.

[0070] As described above, payment app 20 can transition to offline mode or display an offline code image on the display unit based on a user's operation, allowing the user to make electronic payments more flexibly. Until now, such user-initiated use of an offline code image has not been practiced. Therefore, when a second state occurs, such as an error, payment app 20 has been closed. In contrast, in this embodiment, payment app 20 uses an offline code image in response to a user's operation, improving user convenience and allowing the user to make electronic payments more flexibly.

[0071] (B) A process for displaying an offline code image on the display unit under the control of the payment app 20 will be described. When the payment app 20 is in the second state and causes the display unit to display an offline code image under the control of the payment app 20, the payment app 20 transitions the electronic payment mode to offline mode and displays the offline code image on the display unit without displaying an interface screen (e.g., IM11 in FIG. 10 or IM13 in FIG. 11) that accepts an operation to transition to offline mode for performing electronic payment using the offline code image on the display unit. The above phrase "displaying an offline code image on the display unit under the control of the payment app 20" includes the payment app 20 deciding or determining that the use of an offline code image is triggered by the control of the payment app 20 because an online code image cannot be used in the current processing status or the displayed interface screen.

[0072] When the payment application 20 transitions to offline mode, it displays an interface screen (e.g., IM21 in FIG. 12) on the display unit indicating that it is in offline mode, and when an operation to display an offline code image is performed on the interface screen (e.g., when the payment button is operated), it displays the offline code image on the display unit.

[0073] 12 shows an example of an interface screen displayed in the second state. Interface screen IM21 includes information indicating that electronic payment using the offline code image is possible, a "Pay" button, and the like. When the user operates the "Pay" button, payment application 20 displays interface screen IM22 on the display unit.

[0074] In the process of FIG. 12, the display of the interface screen IM21 may be omitted and the interface screen IM22 of FIG. 12 may be displayed instead.

[0075] Furthermore, in the above example, when in the second state, the payment application 20 may automatically transition the mode related to providing information to light mode (simple mode). Light mode is a mode in which one or both of the information to be displayed and the functions to be provided are simplified compared to when not in the second state. This allows the payment application 20 to provide predetermined information and functions to the user by suppressing communication and load with the network NW or the payment server 100 when communication with the network NW or the payment server 100 is not normal or when the processing load on the payment server 100 is high. The above-mentioned interface screens IM12 and IM21 are examples of interface screens in light mode. When not in light mode, for example, an interface screen different from the interface screen IM12 or IM21 is provided to the user.

[0076] The payment application 20 may be configured to use an offline code image in the light mode. For example, the payment application 20 may transition to the light mode when in the second state and generate an offline code image in the light mode. The payment application 20 may be configured to use an offline code image in a mode different from the light mode. The payment application 20 may generate an offline code image without transitioning to the light mode when in the second state.

[0077] [Flowchart of the specified process] FIG. 13 is a flowchart showing an example of the flow of processing executed by payment application 20. First, payment application 20 determines whether to execute the above-described process (A) or process (B) (S200), and determines whether to execute process (A) (S202). If process (B) is executed without executing process (A), payment application 20 transitions to offline mode (S204). Next, payment application 20 displays an interface screen corresponding to (B) (e.g., IM21, IM22 in FIG. 12) on the display unit (S206). This allows the user to make an electronic payment using the offline code image. Note that interface screens IM21 and IM22, which are examples of interface screens corresponding to (B), are used in light mode; however, if the transition to light mode is not performed (normal mode), other interface screens may be displayed.

[0078] When executing process (A), payment application 20 displays interface screen 1 corresponding to (A) (e.g., IM11 in FIG. 10 or IM13 in FIG. 11) on the display unit (S208). Next, payment application 20 determines whether the user has performed an operation (S210). If no operation has been performed, processes S212 and S214 are skipped.

[0079] If the operation is performed, payment application 20 transitions to offline mode (S212). Next, payment application 20 displays interface screen 2 (e.g., IM12 in FIGS. 10 and 11) corresponding to (A) on the display unit (S214). This allows the user to make electronic payments using the offline code image.

[0080] For example, if the second state occurs when the user attempts to display the home screen, the payment app 20 may determine to display an offline code image by control of the payment app 20. In the second state, for example, the payment app 20 may change to light mode and display the interface screen IM21 shown in FIG. 12 described above, and when the user operates the payment button, display the interface screen IM22. For example, if the second state occurs when the user operates the payment button on the home screen, the payment app 20 may determine to display an offline code image by control of the payment app 20.

[0081] Alternatively, for example, if the second state is entered when the user operates the payment button on the home screen, payment app 20 may determine to display an offline code image in response to a user operation. If the second state is entered when the payment button is operated, for example, payment app 20 may display interface screen IM13 shown in FIG. 11 described above, and when the user operates an operation to use the offline code image, display interface screen IM12. Then, when the user operates the payment button on interface screen IM12, payment app 20 may display the offline code image on the display unit.

[0082] As described above, payment application 20 displays an offline code image on the display unit based on the user's operation or the control of payment application 20, depending on the control status of payment application 20 or the status of the content to be displayed. This makes it possible to use electronic payments using offline code images in a variety of situations, making electronic payments more flexible.

[0083] According to the embodiment described above, when the state of the payment server 100 is in the first normal state, the payment app 20 displays an online code image generated using a one-time code obtained by communication from the payment server 100 on the display unit of the terminal device, and when the state of the payment server 100 is in the second abnormal state, the payment app 20 generates an offline code image using an offline key obtained from the payment server 100 less frequently than the one-time code, and displays the offline code image on the display unit of the terminal device, thereby making it possible to realize electronic payments more flexibly.

[0084] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0085] 10 User terminal device 20. Payment App 100 Payment Server 120 Contents Provider 130 Payment processing unit 140 Information Management Department

Claims

1. An application program that operates on a user's terminal device and cooperates with a payment server to provide electronic payment services to the user, When the payment server is in a normal first state, an online code image generated using the one-time code acquired from the payment server by communication is displayed on a display unit of the terminal device; When the state of the payment server is in a second state that is not normal, an offline code image is generated using an offline key acquired from the payment server less frequently than the one-time code, and the offline code image is displayed on a display unit of the terminal device. Application program for.

2. the second state is determined based on a result of communication with the payment server; the second state is a state in which the application program can communicate with the payment server, but the payment server cannot transmit the one-time code to the application program; The application program according to claim 1 .

3. the second state is determined based on a result of communication with the payment server; the second state is a state in which the application program can communicate with the payment server, but the payment server is inhibited from transmitting the one-time code; The application program according to claim 1 .

4. based on the content of the process of the application program in the second state, determining whether the offline code image is to be displayed on the display unit by an operation of the user or by control of the application program; The application program according to claim 1 .

5. referring to the correspondence information, determining whether to display the offline code image on the display unit in response to an operation by the user or under control of the application program; The correspondence information is information in which the content of the processing of the application program is associated with information indicating whether the offline code image is to be displayed on the display unit by an operation of the user, or information indicating whether the offline code image is to be displayed on the display unit by control of the application program.

5. The application program according to claim 4.

6. Based on an interface screen displayed on the display unit by the application program in the second state, determining whether the offline code image is to be displayed on the display unit by an operation of the user or by control of the application program; The application program according to claim 1 .

7. referring to the correspondence information, determining whether to display the offline code image on the display unit in response to an operation by the user or under control of the application program; The correspondence information is information in which information regarding an interface screen to be displayed on the display unit by the application program is associated with information indicating whether the offline code image is to be displayed on the display unit by an operation of the user, or information indicating whether the offline code image is to be displayed on the display unit by control of the application program.

7. The application program according to claim 6.

8. In the second state, when the offline code image is displayed on the display unit by the user's operation, displaying an interface screen on the display unit for accepting an operation to transition to an offline mode for performing electronic payment using the offline code image; in response to an operation by the user on the interface screen to transition to the offline mode, transitioning the electronic payment mode to the offline mode through the operation by the user, and displaying the offline code image on the display unit; 8. The application program according to claim 4.

9. When the device has transitioned to the offline mode, an interface screen indicating that the device is in the offline mode is displayed on the display unit; When an operation to display the offline code image is performed on the interface screen, the offline code image is displayed on the display unit.

9. The application program according to claim 8.

10. In the second state, when the offline code image is displayed on the display unit under the control of the application program, transitioning the electronic payment mode to the offline mode without displaying on the display unit an interface screen for accepting an operation to transition to the offline mode for performing electronic payment using the offline code image, and displaying the offline code image on the display unit; 8. The application program according to claim 4.

11. When the device has transitioned to the offline mode, an interface screen indicating that the device is in the offline mode is displayed on the display unit; When an operation to display the offline code image is performed on the interface screen, the offline code image is displayed on the display unit. The application program according to claim 10.

12. The computer of the user's terminal device, An electronic payment method for providing an electronic payment service to a user in cooperation with a payment server, comprising: When the payment server is in a normal first state, a process of displaying an online code image generated using a one-time code acquired from the payment server through communication on a display unit of the terminal device; When the state of the payment server is in a second state that is not normal, a process of generating an offline code image using an offline key acquired from the payment server less frequently than the one-time code, and displaying the offline code image on a display unit of the terminal device is performed; Electronic payment methods that perform.

13. A terminal device for providing electronic payment services to users in cooperation with a payment server, When the payment server is in a normal first state, a process of displaying an online code image generated using a one-time code acquired from the payment server through communication on a display unit of the terminal device; When the state of the payment server is in a second state that is not normal, a process of generating an offline code image using an offline key acquired from the payment server less frequently than the one-time code, and displaying the offline code image on a display unit of the terminal device is performed; A terminal device that runs

Images