Application program, payment control method, and payment system

The application program enables offline electronic payments using secret keys and user identification tokens, addressing communication issues in electronic transactions by ensuring secure and legitimate offline code generation.

JP2024165499AActive Publication Date: 2024-11-28PAYPAY CO LTD

Patent Information

Application Number
JP2023081752
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-17
Publication Date
2024-11-28
Estimated Expiration
2043-05-17

AI Technical Summary

Technical Problem

In electronic payments, communication difficulties between a terminal device and a payment server can prevent the acquisition of a valid one-time code, leading to interrupted transactions and confusion for users regarding available payment options.

Method used

An application program that operates on a user's terminal device, enabling offline code image generation and display when communication with the payment server is challenging, using a secret key and user identification token to facilitate offline transactions.

Benefits of technology

Ensures seamless payment processing even in areas with weak connectivity, maintaining security by avoiding personal information inclusion and enhancing transaction legitimacy through timed and token-based offline code generation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024165499000001_ABST
    Figure 2024165499000001_ABST
Patent Text Reader

Abstract

To smoothly guide a user to payment that uses an offline code image.SOLUTION: An application program is for causing a terminal device to perform processing of communicate with a payment server when electronic payment is made, and in a first state where communication with the payment server is normal, causing a 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, and in a second state where the communication with the payment server is difficult, causing the display unit to display an interface screen that accepts an operation to consent to payment in an offline mode, and when a transition condition is satisfied including the operation of the consent being performed, causing the display unit to display an offline code image generated without using the one-time code.SELECTED DRAWING: Figure 9
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an application program, a payment control method, and a payment system. [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 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, if communication between the terminal device and the payment server is difficult at the time of electronic payment, a valid one-time code cannot be obtained, and electronic payment may not be possible. In such a case, it is expected that it may be difficult for the user to understand what payment options are available.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objectives is to provide an application program, a payment control method, and a payment system that can smoothly guide users to make payments using offline code images. [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 the terminal device to communicate with the payment server when electronic payment is made, and when communication with the payment server is in a normal first state, causing the terminal device to display on a display unit of the terminal device an online code image generated using a one-time code obtained by communication from the payment server, and when communication with the payment server is in a difficult second state, causing the display unit to display an interface screen that accepts an operation to accept payment in offline mode, and when a transition condition is satisfied including the operation of accepting being performed, causing the display unit to display an offline code image generated without using the one-time code. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to provide an application program, a payment control method, and a payment system that can smoothly guide a user to make a payment using an offline code image. [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 (online payment). [Diagram 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment (online payment). [Figure 4]1 is a configuration diagram of a payment server 100 according to a first 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] FIG. 13 is a diagram showing an example of a standby screen IM2. [Figure 11] FIG. 13 is a diagram showing an example of a half sheet IM3. [Figure 12] FIG. 13 is a diagram showing an example of a detailed explanation screen IMe. [Figure 13] FIG. 13 is a diagram showing an example of a first offline mode screen IM4 on which a first offline code image is displayed. [Figure 14] FIG. 13 is a diagram showing an example of a second offline mode screen IM5 on which a second offline code image is displayed. [Figure 15] FIG. 13 is a diagram showing an example of a payment method selection screen IM6. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, with reference to the drawings, an embodiment of the application program, the payment control method, the payment server, the program, and the payment system of the present invention will be described. The application program and the payment server cooperate to provide an 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) existing in real space, but may also include a virtual store of electronic commerce. The virtual store may include a store 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 is 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 a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by a payment server 100. The payment server 100 communicates with, for example, one or more user terminal devices 10, one or more first store terminal devices 50, and one or more second store terminal devices 70 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.

[0011] 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] 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] 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] 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, a POS gateway, an affiliated store server, etc., in which case the payment information is sent from the POS device to the payment server 100 via various devices. In the following explanation, no distinction is made between these, 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 an example of the general flow of electronic payment (online 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 the automatic update timing (for example, every minute) is reached, and at other timings, the payment application 20 sends a request to issue a one-time code to the payment server 100 (S11). The payment server 100 (payment content provider 120 described later) generates a one-time code (S12) and sends it to the payment application 20 (S13). The payment application 20 displays a code image (online 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 using an optical reading function and acquires the one-time code, etc. (S15). Then, the first store terminal device 50 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 by manual input. 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). Note that, in parallel with this, information notifying the first store terminal device 50 of the completion of payment is also transmitted.

[0018] Note that electronic payment may be performed using only one of the above patterns. The "account ID" described in Fig. 2 may be other information (such as a telephone number) that can be used as user identification information.

[0019] [Payment server] FIG. 4 is a configuration diagram of the payment server 100 according to the first embodiment. The payment server 100 includes, for example, a communication unit 110, a payment 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), or a GPU (Graphics Processing Unit), or may be realized by cooperation between software and hardware. The program may be stored in advance in a storage device (storage device having a non-transient storage medium) such as an HDD (Hard Disk Drive) or a flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or a CD-ROM, and may be installed in the storage device by mounting the storage medium in a drive device.

[0020] The storage unit 170 is a HDD, a flash memory, a 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, payment content information 174, and affiliated store / shop information 176.

[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 payment 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 payment content providing unit 120 appropriately reads necessary content from the payment content information 174 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.

[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] 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 is information associated with, for example, a user URL, an account ID, a phone number, a password, an email address, a user ID, a name, an address, a date of birth, a registration date, a charge balance, a deferred payment setting, a deferred payment limit, a deferred payment usage amount, a deferred payment available amount, a payment method setting, a bank account, a credit card number, an issued one-time code, a user identification token for offline payment described later, a secret key (for charge balance), a secret key (for deferred payment), an upper limit for offline payment, charge history information, and payment history information.

[0025] The user URL is used for money transfer processing between users. When registering for the electronic payment service, registration of a phone number and password is mandatory. The account ID is issued to the user by the payment server 100, and the user ID is an ID that the user can set at will (does not have to set). Similarly, the email address, name, address, and date of birth are also information that the user can set at will (does not have to set). The registration date is the date that the user registered with the electronic payment service (the date that the account was created). Hereinafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account.

[0026] The charge balance is information indicating the balance of electronic money that is set by a user by transferring money to an account in advance. Methods of transfer include transfer from an ATM (Automatic Teller Machine) of a designated business (bank) and transfer from a registered bank account. The deferred payment setting is information indicating whether or not the setting for enabling deferred electronic payment has been completed, and is set to either "completed" or "not completed." The payment method setting is setting information indicating whether the user will make electronic payment from the charge balance or deferred 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 deposited into an electronic payment service. The charge history information is a history of the user transferring money to an electronic payment service in advance to increase the charge balance. The payment history information is information indicating the details of the payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.) for each payment.

[0027] 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 ID. 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.

[0028] 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.

[0029] [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.

[0030] The payment processing unit 130 performs electronic payment for users whose "setting information" is set to "deferred payment" as follows. Deferred payment is set separately from "credit payment" 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 deferred payment limit. In order to receive the deferred payment service, a credit card provided by the operator of the electronic payment service may be required. The amount used for deferred 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 deferred payment amount and subtracting the same amount from the available deferred 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 deferred payment amount at the time of provisional payment, an error notification is returned to the payment application 20.

[0031] [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 first state (online payment possible state) in which communication between the payment application 20 and the payment server 100 is not difficult. 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, together with the code image CD, text (in the figure, "Pay with balance") is displayed indicating whether electronic payment is to be made using the charge balance or electronic payment is to be made by deferred payment. This text is drawn by the payment application 20 based on information updated by the payment application 20 each time the changeover switch (toggle switch) SW is operated. In addition, the top screen IM1 includes an operation area CA including the changeover switch SW and a transition button TB1. Note that the "switch" and "button" are GUIs (Graphical User Interfaces) realized in cooperation with a touch panel. The changeover switch SW is operated to switch between electronic payment using the charge balance and electronic payment by deferred payment. The changeover switch SW is set to electronic payment using the charge balance by default, and every time the user operates the switch SW, the setting is switched between electronic payment using the charge balance and electronic payment by deferred payment. In the figure, the explanation "Balance payment" is displayed, which means that the setting is set to electronic payment using the charge balance. The operation area CA is provided with buttons for instructing main operations in electronic payment, such as a button for instructing scanning (starting user scanning) and a button for instructing charging. When the transition button TB1 is operated, the screen transitions to a payment screen that displays the code image used for electronic payment and the available amount.

[0032] [Offline payment] Hereinafter, a description will be given of electronic payment (offline payment) in the second state in which a valid one-time code is not acquired due to difficulty in communication between the payment application 20 and the payment server 100. The offline payment of this embodiment can be performed at the store where the store scan is performed as described above.

[0033] The payment application 20 determines whether to perform online or offline payment depending on whether communication with the payment server 100 is in a first state where communication is normal or in a second state where communication is difficult. For example, the payment application 20 determines that the payment is in the second state when 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). When the payment application 20 determines that communication with the payment server 100 is in the second state, it generates an offline code using the time and secret key kept by the user terminal device 10, 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 an offline code generated by itself without using a one-time code.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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 acquired (if the 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. That is, the offline payment is proceeded. "At least a part of the read information" means "at least a part of the offline code" and is simply referred to as the offline code below. 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 stored in the storage unit 170 as provided to the payment application 20. The time handled in the offline payment is measured, for example, in minutes, but is not limited thereto. 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. For example, the payment processing unit 130 generates multiple codes within a predetermined range of the current time measured by the payment server 100 plus or minus a predetermined time (e.g., one minute) in case there is a time difference between the user terminal device 10 and the payment server 100, and if any of the codes matches the offline code acquired from the store terminal device, it determines that the offline authentication condition is satisfied, that is, that the payment information is valid.

[0039] 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 (set to 5000 yen in the example of FIG. 5), 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 frequency of electronic payments made by the user in the past, 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.

[0040] 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.

[0041] At another time, when a user launches the payment application 20 in a store where store scanning is performed, or when a payment operation is performed with the payment application 20, the payment application 20 sends a request to issue a one-time code to the payment server 100 (S31). If an event occurs n times or more where a response to the one-time code issuance 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). 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 using an optical reading function and obtains an offline key, etc. (S33).

[0042] 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.

[0043] According to this process, electronic payment can be made even when communication between the payment application 20 and the payment server 100 is difficult, such as when the store where the store scan is performed is located in an area with weak radio waves, making it possible to realize electronic payment more flexibly. Also, by proceeding with electronic payment without including user identification information such as an account ID in the offline code even in offline payment, it is possible to prevent a decrease in the degree of protection of the user's personal information.

[0044] Furthermore, by generating an offline code image using both the time and the offline key and performing offline payment, the probability that the payment is legitimate can be increased. If an offline code image is generated using only the offline key and offline payment is performed, it becomes impossible to know when the offline code image was generated, and the legitimacy of the payment is reduced. Furthermore, if an offline code image is generated using only the time and offline payment is performed, anyone can generate the offline code image if the generation logic of the offline code image is exposed. By generating an offline code image using both of these, the generation timing of the offline code image can be known, and the offline key is included in the offline code image, so that it is guaranteed that it is based on the information issued by the payment server 100. As a result, the probability that the payment is legitimate can be increased.

[0045] Furthermore, by setting the upper limit for offline payments lower than that for online payments, a more secure electronic payment can be achieved.

[0046] The following describes screen control by the payment application 20. Fig. 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.

[0047] First, the payment application 20 judges whether or not a notification has not been received from the payment server 100 (S100). The notification may be, for example, a one-time password returned in response to the one-time password issuance request described above. If a notification has been received from the payment server 100, the payment application 20 displays an online mode screen (for example, the one shown in FIG. 7) and continues normal operation (S102).

[0048] If no notification is received from the payment server 100, the payment application 20 causes the user terminal device 10 to display a standby screen IM2 indicating that it is difficult to read information from the payment server 100 (S104). Figure 10 is a diagram showing an example of the standby screen IM2. The standby screen IM2 does not display a valid code image, but displays text TX1 indicating the connection status with the payment server 100 to the user.

[0049] Next, the payment application 20 determines whether the second state has been determined (S106). As described above, the condition for determining the second state is when "an event occurs n times or more in which a notification such as a response to a one-time code issuance request does not arrive within a predetermined time." If the second state has not been determined, the process returns to S100.

[0050] When the second state is determined, 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 (S108). 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).

[0051] 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 (S110). The error screen includes text explaining that an Internet connection is difficult, etc.

[0052] If a valid offline key has been acquired, payment application 20 determines whether counter value k is equal to or greater than threshold value Th (S112). Counter value k is set to zero when payment application 20 is installed in user terminal device 10, for example, and is incremented by one each time the approval operation determined in S116 is performed. That is, the determination process in S112 determines whether the approval operation has been performed a predetermined number of times (= threshold value Th) or more. Threshold value Th is, for example, a value of about 1 to 3.

[0053] If the counter value k is less than the threshold value Th, the payment application 20 causes the user terminal device 10 to display the half sheet exemplified in FIG. 11 (S114). FIG. 11 is a diagram showing an example of a half sheet IM3. The half sheet IM3 is displayed in a size smaller than the screen on which the online code image such as the top screen IM1 is displayed. The half sheet IM3 is an example of an "interface screen". The half sheet IM3 displays a text TX2 explaining offline payment. The half sheet IM3 is also provided with a first operation unit B1 (an example of the operation unit A) for instructing a transition to a detailed explanation screen regarding payment in offline mode, and a second operation unit B2 for instructing to accept payment in offline mode. FIG. 12 is a diagram showing an example of a detailed explanation screen IMe. The detailed explanation screen IMe displays a text TXe explaining offline payment. The detailed explanation screen IMe is also provided with a first operation unit Be1 (an example of the operation unit B) for instructing a transition to a help page regarding payment in offline mode, and a second operation unit Be2 for instructing to return to the half sheet IM3. The help page is updated by the payment server 100 from time to time, and the payment application 20 downloads the help page at any timing when communication between the user terminal device 10 and the payment server 100 is normal, and stores (caches) it in the memory of the user terminal device 10. This makes it possible to provide the user with a help page that describes detailed information about payment in offline mode, even in a situation where communication with the payment server 100 is difficult. Note that the help page may also be displayed in a size smaller than the screen on which the online code image, such as the top screen IM1, is displayed, similar to the half sheet IM3.

[0054] The payment application 20 determines whether or not an operation has been performed on the second operation section B2 of the half sheet IM3, that is, whether or not an operation to approve payment in the offline mode has been performed (S116).

[0055] When an operation to approve payment in offline mode is performed, the payment application 20 causes the user terminal device 10 to display the offline mode screen (S118). Also, when it is determined in S112 that the counter value k is equal to or greater than the threshold value Th, the payment application 20 causes the user terminal device 10 to display the offline mode screen (S118). The offline mode screen is a screen on which an offline code image is displayed. In this way, the transition conditions to the offline mode screen include, for example, that a valid offline key has been acquired from the payment server 100, and basically include that an operation to approve has been performed, but if the operation to approve has been performed a predetermined number of times or more, the operation to approve is excluded.

[0056] By carrying out such processing, it is possible to smoothly guide the user to offline payment using the offline code image.

[0057] The offline mode screen will be described below. The offline mode screen includes a first offline mode screen on which a first offline code image that allows offline payment by a first payment method is displayed, and a second offline mode screen on which a second offline code image that allows offline payment by a second payment method is displayed, and these may be switchable between them by a user's operation. In other words, in the offline mode payment provided by the electronic payment system, the first payment method and the second payment method may be selectively implemented. For example, similar to online payment, the first payment method is a method of making electronic payment by charge balance, and the second payment method is a method of making electronic payment by post-payment. Each of the first payment method and the second payment method may be a method different from these, such as a payment method using a debit card function, a point payment, a credit card payment, etc.

[0058] In this case, the payment application 20 acquires a first offline key for generating a first offline code image and a second offline key for generating a second offline code image less frequently than the one-time code. Each of the first offline key and the second offline key includes the same information as the offline key described above, and further includes identification information indicating whether it is the first offline key or the second offline key. The payment application 20 generates a first offline code using the first offline key, generates a first offline code image based on the first offline code, and displays the first offline code image on the user terminal device 10. The payment application 20 also generates a second offline code using the second offline key, generates a second offline code image based on the first offline code, and displays the second offline code image on the user terminal device 10. The user identification tokens included in the first offline key and the second offline key may be the same or different (they are the same in FIG. 5).

[0059] FIG. 13 is a diagram showing an example of a first offline mode screen IM4 on which a first offline code image is displayed, and FIG. 14 is a diagram showing an example of a second offline mode screen IM5 on which a second offline code image is displayed. The first offline mode screen IM4 displays a first code image CD#1. The first offline mode screen IM4 displays a current payment method and has a third operation section B3 for instructing a transition to a payment method selection screen IM6. The first offline mode screen IM4 also has a reload button B5. When the reload button B5 is operated, a communication request is transmitted to the payment server 100, and the process of the flowchart in FIG. 9 is started. On the other hand, the second offline mode screen IM5 displays a second code image CD#2. The second offline mode screen IM5 displays a current payment method and has a fourth operation section B4 for instructing a transition to a payment method selection screen IM6. The second offline mode screen IM5 also has a reload button B5.

[0060] Fig. 15 is a diagram showing an example of a payment method selection screen IM6. The payment method selection screen IM6 has a sixth operation section B6 to an eighth operation section B8 which list selectable payment methods (payment methods). When the sixth operation section B6 is operated, the screen transitions to a first offline mode screen IM4, and when the seventh operation section B7 is operated, the screen transitions to a second offline mode screen IM5. The process when the eighth operation section is selected may be determined arbitrarily.

[0061] The payment application 20 may take over the setting of the payment method for online payment as the initial setting for offline payment. For example, the payment application 20 may determine whether the screen to be displayed first when it is decided to perform offline payment is the first offline mode screen IM4 or the second offline mode screen IM5, according to the setting for online payment. In this case, the payment application 20 stores the setting of the payment method for online payment in the memory of the user terminal device 10.

[0062] If the payment information acquired during offline payment includes information obtained from the first offline code screen, i.e., the first offline key, the payment server 100 proceeds with the electronic payment using the first payment method, and if the payment information acquired from the second offline code screen, i.e., the second offline key, the payment server 100 proceeds with the electronic payment using the second payment method.

[0063] By carrying out such processing, it is possible to expand the range of choices available to users in offline payments using offline code images, and to improve convenience.

[0064] Note that the above-described offline processing may be executed in the first state. In other words, the processing described as the offline processing may be executed at all times regardless of the communication state between the user terminal device 10 and the payment server 100.

[0065] 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]

[0066] 10 User terminal device 20. Payment App 100 Payment Server 120 Payment 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 electronic payment is made, the terminal device Communicating with the payment server; When communication with the payment server is in a normal first state, an online code image generated using a one-time code acquired from the payment server through communication is displayed on a display unit of the terminal device; When the device is in a second state in which communication with the payment server is difficult, the device causes the display unit to display an interface screen that accepts an operation to accept payment in offline mode, and when a transition condition is satisfied, including the operation of accepting, the device causes the display unit to display an offline code image generated without using the one-time code. Application program for.

2. The transition condition further includes that a valid offline key for generating the offline code image is obtained from the payment server; causing the terminal device to generate the offline code image using the offline key; The application program according to claim 1.

3. If the consent operation is performed a predetermined number of times or more, The fact that the operation of approving has been performed is removed from the transition conditions; When the communication with the payment server is in the second state, the terminal device is caused to perform a process of displaying the offline code image on the display unit without displaying the interface screen on the display unit. The application program according to claim 1.

4. The interface screen is provided with an operation unit A for instructing a transition to an explanation screen that displays an explanation regarding the payment in the offline mode.

2. The application program according to claim 1.

5. The explanation screen is provided with an operation unit B for instructing a transition to a help page that is more detailed than the explanation screen, the application program causes the terminal device to acquire data of the help page from the payment server in advance through communication; The terminal device stores the stored information in a memory thereof. When the operation unit B is operated, the terminal device is caused to perform a process of displaying the help page on the display unit.

5. The application program according to claim 4.

6. When the communication with the payment server is in the second state and the transition condition is not satisfied, causing the display unit to perform a process of displaying an error screen. The application program according to claim 1.

7. causing the terminal device to perform a process of displaying the interface screen on the display unit in a size smaller than a screen on which the online code image is displayed; The application program according to claim 1.

8. The terminal device, when an operation for instructing a reload is performed on the interface screen, it is determined whether communication with the payment server is in the first state or the second state; Based on the determination result, a process is performed to display the online code image on a display unit of the terminal device, or to display the offline code image on the display unit.

2. The application program according to claim 1.

9. A payment control method executed by a terminal device that cooperates with a payment server to provide an electronic payment service to a user, comprising: When electronic payment is made, the terminal device Communicating with the payment server; When communication with the payment server is in a normal first state, an online code image generated using a one-time code acquired from the payment server through communication is displayed on a display unit of the terminal device; When the device is in a second state in which communication with the payment server is difficult, the device causes the display unit to display an interface screen that accepts an operation to accept payment in offline mode, and when a transition condition including the operation of accepting is satisfied, the device causes the display unit to display an offline code image generated without using the one-time code. Payment control methods.

10. The application program according to claim 1; A payment server that provides an electronic payment service to a user in cooperation with an application program running on a terminal device of the user, a communication unit that communicates with a store terminal device installed in a store and receives payment information from the store terminal device, the payment information including at least a part of information read from the code image displayed by the store terminal device and a payment amount; a providing unit that provides a one-time code to the application program via the communication unit; and A payment processing unit that performs electronic payment based on the payment information, If the payment information includes information based on the one-time code, proceed with electronic payment using the one-time code; a payment processing unit that, when the payment information includes information obtained from the offline code image, proceeds with electronic payment using the information obtained from the offline code image; A payment server having A payment system comprising:

Citation Information

Patent Citations

  • Software group construction / Generation / Execution system and method

    JP2002229786A

  • Payment and Settlement System and Method Using Barcodes

    JP2016514312A

  • Information processing method, program, and terminal

    JP2020204883A

  • Program, information processing method, terminal

    JP6815447B1

  • Information processing device, information processing method, and information processing program

    JP7090217B1

Cited By

  • Program for terminal, terminal, and information processing method

    JP2026079303A

  • Terminal program, terminal, and information processing method

    JP7774119B1