Application program, electronic payment method, and terminal device

Abstract

To make electronic payments more flexible. [Solution] 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, the application program causing, when the state of the payment server is in a normal first state, for the purpose of displaying an online code image generated using a one-time code obtained by communication from the payment server on the display unit of the terminal device, and when the state of the payment server is in an abnormal second state, for the purpose of generating an offline code image using an offline key obtained from the payment server less frequently than the one-time code, and displaying the offline code image on the display unit of the terminal device.

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 device at the store 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 in the code image. By using the one-time code, there is no need to include personal information in the code image, and therefore security is improved. [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 above-described electronic payment, 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 the conventional technology, depending on the communication situation at the time of electronic payment, a valid one-time code may not be obtained, and the electronic payment may not be possible.

[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 make it possible to realize electronic payments 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, the application program causing, when the state of the payment server is a normal first state, for the application program to cause 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 state of the payment server is an abnormal second state, for the application program to cause an offline code image to be generated using an offline key obtained from the payment server less frequently than the one-time code, and to display the offline code image on the display unit of the terminal device. Effect 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 can enable electronic payment to be realized more flexibly. [Brief description of the drawings]

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

[0009] Hereinafter, with reference to the drawings, an embodiment of the application program, electronic payment method, and terminal device of the present invention will be described. Various devices for providing services to users and performing internal analysis, such as the "server" that will be described below, may be realized by a group of distributed devices, and each device may be operated by a different business operator. Furthermore, the owner of the hardware of the device (the cloud server provider) and the business operator that actually operates the device may also be different. The application program and the payment server work together to provide the electronic payment service. In the following description, the application program is referred to as a payment application. The electronic payment service is a service that supports payments related to the purchase of goods and services at a store. The store is, for example, a physical store (real store) that exists in the real world, but may also include a virtual store for electronic commerce. The virtual store may include those provided by an entity different from the operator of the electronic payment service. In that case, when making a payment for shopping at the virtual store, the screen may be controlled to transition to an interface screen of the electronic payment service. In the electronic payment service, the store is treated as belonging to, for example, an affiliated store (brand), and processing such as payment when a purchase is made at the store is mainly performed between the user and the affiliated store. Alternatively, processing such as payment may be performed between the user and the store.

[0010] [Electronic payment service] FIG. 1 is a diagram showing 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. The 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 a payment server 100. These devices communicate with each other, 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, and the like. Some or all of the functional configuration included in the electronic payment system may be distributed in any form among 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 a 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 reception 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 application 20, thereby operating to provide an electronic payment service to a user in cooperation with a payment server 100. The payment application 20 is installed in 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, a tablet terminal, a personal computer, or the like. An interface 72 for affiliated stores runs on the second store terminal device 70. The interface 72 for affiliated stores may be an app for affiliated stores or a browser. The interface 72 for affiliated stores accepts coupon settings and the like made by 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 a 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 the payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, no distinction is made between these two and it is assumed that the 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 of 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 activated decodes the store code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is an electronic payment service domain to which store-identifying information is added, and is associated with an affiliated store ID, a store ID, etc. in the payment server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the affiliated store ID and the store ID corresponding to the store URL, acquires the affiliated store name and the store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount into the user terminal device 10 on the screen on which the affiliated store name and the store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount, and transmits it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). The payment server 100 then transmits a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 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 not only the store URL but also information on the payment amount. In this case, the step of the user inputting the payment amount is omitted, and the information on the payment amount is included in the first payment information and transmitted to the payment server 100. Information on the affiliated store name and the store name may be included in the payment completion screen and displayed.

[0017] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, when the payment application 20 is started, when a payment operation is performed in the payment application 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or a 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 store terminal device 50, and the first store terminal device 50 decodes the code image by an optical reading function and obtains the one-time code, etc. (S15). The first store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). The payment server 100 then transmits 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, issuance of a one-time code may be omitted in the store scan, 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 a SOC (System On Chip), or may be realized by cooperation between software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transient storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage medium (non-transient 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, a flash memory, a RAM (Random Access Memory), or the like. 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. The communication unit 110 is, for example, a network interface card.

[0022] The content providing unit 120 has, for example, a function of a web server, 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 by the user while the 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 required 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 the user information 172. The user information 172 is an example of the registration information of a user. The user information 172 is, for example, a user URL, an account ID, a telephone number, a password, as well as information associated with an email address, a user ID, a name, an address, a date of birth, a registration date, a charge balance, a credit payment setting, a credit payment limit, a credit payment amount used, a credit payment available amount, a payment method setting, a bank account, a credit card number, charge history information, and payment history information. The user URL is used for a remittance process between users. When registering for the electronic payment service, it is necessary to register a telephone number and a password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be set by the user at will (does not have to be set). Similarly, the email address, and the name, address, and date of birth are information that can be set by the user at will (does 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 a user by transferring money to an account in advance. Means of transfer include transfer from an ATM (Automatic Teller Machine) of a designated business (bank) and transfer from a registered bank account. The credit payment setting is information indicating whether or not the setting for enabling electronic payment by credit payment using the payment application 20 has been completed, and is set to either "completed" or "not completed". The credit payment limit is the credit payment limit that can be used each month, the credit payment usage amount is the amount of credit payment already used in the current month, and the credit payment available amount is the amount of credit payment that can be used in the current month, which is calculated by subtracting the credit payment usage amount from the credit payment limit. Although only one credit payment limit is shown in the figure, in reality, there is also a daily upper limit, and the lower of these may be set as the credit payment limit. Further details of the credit payment will be described later. The payment method setting is setting information indicating whether the user will perform electronic payment using the charge balance or payment by credit payment at that time. The bank account and credit card number are information on a bank account or credit card number (account number, card number) that can be used to deposit funds into an electronic payment service. Charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. Payment history information is information that indicates the details 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 name and sales amount (described above) are associated with an affiliated store ID, 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 location of the store, 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, and deletes 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 refers to the user information 172 to acquire the "payment method setting" of the user. For a user 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. The item value of the affiliated store's sales is not used as electronic money itself, for example, and an amount corresponding to the item value of the sales 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 payment for users whose "setting information" is set to "credit payment (credit payment using code information)" as follows. Credit 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, and the operator of the electronic payment service acts as a creditor and allows electronic payment that is not dependent on the charge balance within the credit payment limit. In order to receive the credit payment service, a credit card provided by the operator of the electronic payment service may be required. The amount used in the credit payment is settled on the payment date of the following month, for example, by debiting from a bank account, for one month. In this case, the payment processing unit 130 performs provisional payment by adding the payment amount to the credit payment amount and subtracting the same amount from the available credit payment amount, and when the closing date comes, it performs processing to debit the payment for the current month on the payment date of the following month as described above, or requests the operator of the credit card company to perform such processing. In addition, if the payment amount exceeds the available credit payment amount 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 display 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 the 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. Unstable 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 a 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 transmit the one-time code to the application program (for example, a state in which the one-time code cannot be transmitted 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 transmitting the one-time code.

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

[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 application 20. Note that the illustrated state is premised on the premise that the state of the payment application 20 or the payment server 100 is the first state (a state in which online payment is possible). In the first state, a valid one-time code is provided from the payment server 100 to the payment application 20. "Valid" means that it is in response to the most recently transmitted request for issuing a one-time code. The top screen IM1 displays a code image CD. The code image CD includes, for example, a barcode and a QR code. In addition, by sliding a specific area of ​​the top screen IM1, the user can switch between making an electronic payment using the charge balance or making an electronic payment using a credit card. When the user operates the "Pay" button B1, the screen transitions to a payment screen that displays a code image used for electronic payment and the available amount. The payment screen is a screen in which the code image CD is displayed in an enlarged form.

[0036] [Offline payment] Below, a description will be given of electronic payment (offline payment) in the second state in which the payment application 20 is unable to acquire a valid one-time code. The offline payment of this embodiment can be carried out at the aforementioned store scan store.

[0037] The payment application 20 determines whether to perform online payment 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 when an event occurs n times or more in which 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). When 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 an 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 a secret key about 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 spontaneously provide the secret key to the payment application 20.

[0039] The payment application 20 may generate an offline code by using a user identification token in addition to the time and the secret key. The user identification token may be one that is fixedly assigned to the user, or may be one that is sent from the 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 an offline code based on data obtained by inputting a secret key and time into a predetermined function and combining the data with a user identification token. This method is merely an example, and payment application 20 may generate an offline code by any method that can be decrypted based on some or all of the secret key, time, and user identification token.

[0041] Furthermore, the payment application 20 may cause the user terminal device 10 to synchronize the time measured by the user terminal device 10 with the time measured by the payment server 100 at a predetermined timing (for example, every time a secret key issuance request is made). At this time, the payment application 20 may perform a process of synchronizing the time measured by the user terminal device 10 with the time measured by a radio clock or the like at approximately the same time as the 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 part of the read information and the payment amount is obtained (if information based on the offline code image generated by the payment application 20 using time is included), the payment processing unit 130 of the payment server 100 proceeds with electronic payment based on the payment information if the offline authentication condition is satisfied. In other words, the offline payment proceeds. "At least a part of the read information" means "at least a part of the offline code" and will be simply referred to as the offline code below.

[0043] The offline authentication condition is related to the offline code image generated by the 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 the 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 provided to the payment application 20 and is stored in the storage unit 170.

[0044] The time used in offline payment is measured, for example, in minutes, but is not limited to this. When the payment processing unit 130 acquires the payment information, it identifies a secret key from a 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 application 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 discrepancy 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 (e.g., 1 minute), and if any of them matches the offline code obtained from the store terminal device, it determines that the offline authentication conditions are met, that is, that the payment information is legitimate.

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

[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 for issuing 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 timing, when a user activates the payment application 20 in a store where the store scan is performed, or when an operation for making a payment is performed in the payment application 20, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S31). When an event occurs n times or more where a response to the one-time code issuing request does not arrive within a predetermined time, the payment application 20 generates an offline code and displays an offline code image generated based on the offline code (S32). Instead of the event occurs n times or more where a response to the one-time code issuing request does not arrive within a predetermined time, the payment application 20 may determine whether or not the second state is in effect, and if the second state is in effect, display the offline code image. For example, the payment application 20 determines whether or not the second state is in effect based on information acquired from the payment server 100. The user holds (presents) the display surface of the user terminal device 10 over the first store terminal device 50, and the first store terminal device 50 decodes the code image by an optical reading function and acquires an offline key or the like (S33).

[0049] Then, the first store terminal device 50 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, and determines whether the offline authentication conditions are satisfied as described above (S34), and proceeds with the electronic payment if the offline authentication conditions are satisfied (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 even when payment application 20 cannot obtain a one-time code from payment server 100, making it possible to realize electronic payment more flexibly. Also, in offline payment, by proceeding with electronic payment without including user identification information such as an account ID in the offline code, it is possible to prevent a decrease in the level of protection of the user's personal information.

[0051] Furthermore, by generating an offline code using both the time and the offline key and performing an offline payment, the probability that the payment is legitimate can be increased. 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, which reduces 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. By generating an offline code image using both of these, the timing of the generation of the offline code can be known, and the offline key is included in the offline code, so it is guaranteed 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, a more secure electronic payment can be achieved.

[0053] [flowchart] 9 is a flowchart showing an example of a process flow related to screen control by the payment application 20. The process 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 issue 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, the payment application 20 determines whether a valid offline key (secret key and user identification token) has been acquired and stored in the memory of the user terminal device 10 (S104). A valid offline key is, for example, an offline key for which the elapsed time from the acquisition time has not exceeded an upper limit time (a time approximately equal to the issuance cycle of the offline key).

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

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

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

[0059] The payment application 20 refers to the correspondence information and determines whether to display an offline code image on the display unit by a user's operation or by control of the payment application 20. The correspondence information is information in which the content of the processing of the payment application 20 is associated with information indicating whether to display an offline code image on the display unit by a user's operation or information indicating whether to display an offline code image on the display unit by control of the payment application 20.

[0060] (2) Based on the interface screen that the payment application 20 displays on the display unit in the second state, the payment application 20 determines whether to display the offline code image on the display unit in response to a user's operation or under the control of the payment application 20.

[0061] The payment application 20 refers to the correspondence information and determines whether to display the offline code image on the display unit by a user's operation or by control of the payment application 20. The correspondence information is information in which information on an interface screen to be displayed on the display unit by the payment application 20 is associated with information indicating whether to display the offline code image on the display unit by a user's operation or information indicating whether to display the offline code image on the display unit by control of the payment application 20.

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

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

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

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

[0066] FIG. 10 is an interface screen displayed in the second state. Interface screen IM11 includes a half sheet including 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 causes interface screen IM12 to be displayed 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 causes interface screen IM22 of FIG. 12, which will be described later, to be displayed 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 is stuck due to the second state, the payment application 20 displays the interface screen IM11. In this case, when "Close" is operated, this operation is used as a trigger to cause 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. The 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), the payment application 20 displays the 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 in Fig. 12 may be displayed. Whether interface screen IM11 in Fig. 10 or interface screen IM13 in 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, the payment application 20 can transition to offline mode or display an offline code image on the display unit based on the user's operation, allowing the user to make electronic payments more flexibly. Up until now, such an offline code image has not been used starting from the user. For this reason, when the second state occurs, such as an error, the payment application 20 has been closed. In contrast, as described above, in this embodiment, the payment application 20 uses an offline code image in response to the user's operation, improving user convenience and allowing the user to make electronic payments more flexibly.

[0071] (B) A process of 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 causes the display unit to switch to the offline mode without displaying an interface screen (e.g., IM11 in FIG. 10, IM13 in FIG. 11) that accepts an operation to switch to the offline mode in which electronic payment is made using the offline code image, and causes the display unit to display the offline code image. The above "displaying an offline code image on the display unit under the control of the payment app 20" includes the payment app 20 deciding or judging that the control of the payment app 20 is used as a trigger to use an offline code image because an online code image cannot be used in the current processing status or the interface screen being displayed.

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

[0073] 12 is an example of an interface screen displayed in the second state. The interface screen IM21 includes information indicating that electronic payment using an offline code image is possible, a "Payment" button, etc. When the user operates the "Payment" button, the payment application 20 causes the display unit to display the interface screen IM22.

[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] In the above example, in the second state, the payment application 20 may automatically switch the mode related to the provision of information to a light mode (simple mode). The 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 the payment application 20 is not in the second state. In this way, when communication with the network NW or the payment server 100 is not normal or the processing load of the payment server 100 is high, the payment application 20 can provide the user with predetermined information or functions by suppressing communication and load with the network NW or the payment server 100. The above-mentioned interface screens IM12 and IM21 are examples of interface screens in the light mode. When the light mode is not in the 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 the process executed by the payment application 20. First, the payment application 20 specifies whether to execute the above-mentioned process (A) or process (B) (S200), and judges whether to execute the process (A) (S202). When executing the process (B) without executing the process (A), the payment application 20 transitions to offline mode (S204). Next, the payment application 20 displays an interface screen corresponding to (B) (e.g., IM21, 22 in FIG. 12) on the display unit (S206). This allows the user to make an electronic payment using the offline code image. Note that the interface screens IM21, IM22, which are examples of the interface screen corresponding to (B), are those in the light mode, but when the light mode is not transitioned to (when the normal mode is being used), other interface screens may be displayed.

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

[0079] If the operation is performed, the payment application 20 transitions to offline mode (S212). Next, the payment application 20 displays an 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 an electronic payment using the offline code image.

[0080] For example, when 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. When the second state occurs, for example, the payment app 20 may change to a light mode and display the interface screen IM21 of Fig. 12 described above, and when the user operates the payment button, display the interface screen IM22. For example, when 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, the payment application 20 may determine to display the offline code image in response to the user's operation. If the second state is entered when the payment button is operated, for example, the payment application 20 displays the interface screen IM13 of FIG. 11 described above, and when the user operates an operation to use the offline code image, the payment application 20 displays the interface screen IM12. Then, when the user operates the payment button on the interface screen IM12, the payment application 20 displays 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 various situations, making electronic payments more flexible.

[0083] According to the embodiment described above, when the state of the payment server 100 is the first normal state, the payment application 20 causes the display unit of the terminal device to display an online code image generated using a one-time code obtained by communication from the payment server 100, and when the state of the payment server 100 is the second abnormal state, the payment application 20 causes the display unit of the terminal device to display an offline code image using an offline key obtained from the payment server 100 less frequently than the one-time code, thereby making it possible to realize electronic payment 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 for operating on a user's terminal device and providing an electronic payment service to the user in cooperation with a payment server, comprising: When the state of the payment server is a normal first state, displaying an online code image generated using a one-time code acquired from the payment server by communication on a display unit of the terminal device; an application program for performing a process of generating an offline code image using an offline key acquired from the payment server less frequently than the one-time code when the payment server is in a second abnormal state, and displaying the offline code image on a display unit of the terminal device, 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. Application program.

2. An application program for operating on a user's terminal device and providing an electronic payment service to the user in cooperation with a payment server, comprising: When the state of the payment server is a normal first state, displaying an online code image generated using a one-time code acquired from the payment server by communication on a display unit of the terminal device; an application program for performing a process of generating an offline code image using an offline key acquired from the payment server less frequently than the one-time code when the payment server is in a second abnormal state, and displaying the offline code image on a display unit of the terminal device, 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. Application program.

3. An application program for operating on a user's terminal device and providing an electronic payment service to the user in cooperation with a payment server, comprising: When the state of the payment server is a normal first state, displaying an online code image generated using a one-time code acquired from the payment server by communication on a display unit of the terminal device; an application program for performing a process of generating an offline code image using an offline key acquired from the payment server less frequently than the one-time code when the payment server is in a second abnormal state, and displaying the offline code image on a display unit of the terminal device, Based on the content of the process of the application program in the second state, determining whether to display the offline code image on the display unit by an operation of the user or by control of the application program; Application program.

4. An application program for operating on a user's terminal device and providing an electronic payment service to the user in cooperation with a payment server, comprising: When the state of the payment server is a normal first state, displaying an online code image generated using a one-time code acquired from the payment server by communication on a display unit of the terminal device; an application program for performing a process of generating an offline code image using an offline key acquired from the payment server less frequently than the one-time code when the payment server is in a second abnormal state, and displaying the offline code image on a display unit of the terminal device, referring to correspondence information, determining whether to cause the offline code image to be displayed on the display unit by an operation of the user or by control of the application program; The correspondence information is information in which the content of the process of the application program is associated with information indicating whether to cause the offline code image to be displayed on the display unit by an operation of the user, or information indicating whether to cause the offline code image to be displayed on the display unit by control of the application program. Application program.

5. An application program for operating on a user's terminal device and providing an electronic payment service to the user in cooperation with a payment server, comprising: When the state of the payment server is a normal first state, displaying an online code image generated using a one-time code acquired from the payment server by communication on a display unit of the terminal device; an application program for performing a process of generating an offline code image using an offline key acquired from the payment server less frequently than the one-time code when the payment server is in a second abnormal state, and displaying the offline code image on a display unit of the terminal device, Based on an interface screen that the application program causes to be displayed on the display unit in the second state, determining whether to display the offline code image on the display unit by an operation of the user or by control of the application program; Application program.

6. referring to correspondence information, determining whether to cause the offline code image to be displayed on the display unit by an operation of the user or by 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.

6. The application program according to claim 5.

7. 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 for transitioning to an offline mode for performing electronic payment using the offline code image; in response to an operation for switching to the offline mode being performed by the user on the interface screen, switching the electronic payment mode to the offline mode by the operation of the user, and displaying the offline code image on the display unit; 7. The application program according to claim 3.

8. When the offline mode is entered, an interface screen indicating that the offline mode is being entered is displayed on the display unit; When an operation for displaying the offline code image is performed on the interface screen, the offline code image is displayed on the display unit.

8. The application program according to claim 7.

9. 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 for transitioning to an offline mode for performing electronic payment using the offline code image, and causing the offline code image to be displayed on the display unit.

7. The application program according to claim 3.

10. When the offline mode is entered, an interface screen indicating that the offline mode is being entered is displayed on the display unit; When an operation for displaying the offline code image is performed on the interface screen, the offline code image is displayed on the display unit.

10. The application program according to claim 9.

11. 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 state of the payment server is 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 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. The second state is determined based on a result of communication with the payment server, The second state is a state in which the terminal device can communicate with the payment server, but the payment server cannot transmit the one-time code to the terminal device; or The second state is determined based on a result of communication with the payment server, The second state is a state in which the terminal device is capable of communicating with the payment server, but the payment server is inhibited from transmitting the one-time code. Electronic payment methods.

12. A terminal device for providing an electronic payment service to a user in cooperation with a payment server, When the state of the payment server is 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, 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. The second state is determined based on a result of communication with the payment server, The second state is a state in which the terminal device can communicate with the payment server, but the payment server cannot transmit the one-time code to the terminal device; or The second state is determined based on a result of communication with the payment server, The second state is a state in which the terminal device is capable of communicating with the payment server, but the payment server is inhibited from transmitting the one-time code. Terminal device.

13. 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 state of the payment server is 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, 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. Based on the content of the process of the terminal device when in the second state, determining whether to display the offline code image on the display unit by an operation of the user or by controlling the terminal device; Electronic payment methods.

14. A terminal device for providing an electronic payment service to a user in cooperation with a payment server, When the state of the payment server is 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 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. Based on the content of the process of the terminal device when it is in the second state, determining whether to display the offline code image on the display unit by an operation of the user or by controlling the terminal device; Terminal device.

15. 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 state of the payment server is 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 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. referring to correspondence information, determining whether to cause the offline code image to be displayed on the display unit by an operation of the user or by controlling the terminal device; The correspondence information is information in which the content of the process of the terminal device is associated with information indicating whether to cause the offline code image to be displayed on the display unit by an operation of the user, or information indicating whether to cause the offline code image to be displayed on the display unit by control of the terminal device. Electronic payment methods.

16. A terminal device for providing an electronic payment service to a user in cooperation with a payment server, When the state of the payment server is 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, 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. referring to correspondence information, determining whether to cause the offline code image to be displayed on the display unit by an operation of the user or by controlling a terminal device; The correspondence information is information in which the content of the process of the terminal device is associated with information indicating whether to cause the offline code image to be displayed on the display unit by an operation of the user, or information indicating whether to cause the offline code image to be displayed on the display unit by control of the terminal device. Terminal device.

17. 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 state of the payment server is 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, 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. Based on an interface screen displayed on the display unit by the terminal device in the second state, determining whether to display the offline code image on the display unit by an operation of the user or by controlling the terminal device; Electronic payment methods.

18. A terminal device for providing an electronic payment service to a user in cooperation with a payment server, When the state of the payment server is 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 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. Based on an interface screen displayed on the display unit by the terminal device in the second state, determining whether to display the offline code image on the display unit by an operation of the user or by controlling the terminal device; Terminal device.

Images