User terminal device, information processing method, and application program

The user terminal device and application program streamline electronic payments by directly transitioning to a payment interface from a captured code, addressing convenience issues and reducing processing time to 4 seconds.

JP7770529B1Active Publication Date: 2025-11-14PAYPAY CO LTD
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2024230569
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2024-12-26
Publication Date
2025-11-14
Estimated Expiration
2044-12-26

AI Technical Summary

Technical Problem

Conventional electronic payment systems are not sufficiently convenient for users, requiring multiple steps and prolonged processing times for completing payments using code images.

Method used

A user terminal device and application program that displays a first interface screen based on captured code information, allowing seamless transition to a second interface for inputting payment amounts directly within the payment app, reducing the overall time required for completing electronic payments.

Benefits of technology

Enhances user convenience by shortening the payment process from 10 seconds to 4 seconds, preventing unintended payments, and simplifying the operation through the use of universal links and time limits.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007770529000001_ABST
    Figure 0007770529000001_ABST
Patent Text Reader

Abstract

To provide highly convenient services for users. [Solution] A user terminal device displays a first interface screen on the display of the user terminal device based on code information of an electronic payment service captured by a camera installed in the user's user terminal device, and when a transition button on the first interface screen is operated, displays on the display a second interface screen of the store of the electronic payment service that corresponds to the code information, which second interface screen allows the user to input the amount related to the electronic payment using the electronic payment service.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

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

[0002] Conventionally, an electronic payment service using code information has been disclosed (see, for example, Patent Document 1). In this electronic payment service, a user operates a payment app to activate the camera and use the electronic payment service. [Prior art documents] [Patent documents]

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

[0004] Conventional technologies have not always provided sufficient convenience for users.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide a user terminal device, an information processing method, and an application program that can provide highly convenient services to users. [Means for solving the problem]

[0006] One aspect of the present invention is a user terminal device that displays a first interface screen on a display unit of the user terminal device based on code information of an electronic payment service captured by a camera installed in the user's user terminal device, and when a transition button on the first interface screen is operated, displays on the display unit a second interface screen of a store of the electronic payment service that corresponds to the code information, the second interface screen allowing the user to input the amount of an electronic payment using the electronic payment service. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide a user terminal device, an information processing method, and an application program that can improve user convenience. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100. [Figure 5] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 1 is a diagram (1) for explaining processing in an electronic payment service of a comparative example. [Figure 8] FIG. 10 is a diagram (2) for explaining the processing in the electronic payment service of the comparative example. [Figure 9] FIG. 2 is a diagram for explaining the processing in the electronic payment service of the present embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of an error screen. [Figure 11]1 is a flowchart showing an example of the flow of processing executed by (the functions of) user terminal device 10 and payment application 20. DETAILED DESCRIPTION OF THE INVENTION

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

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

[0011] Some or all of the functional components included in the electronic payment system may be distributed across multiple devices in any form, or may be integrated into any device. For example, some or all of the functional components of the payment server 100 may be included in another device.

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

[0013] [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).

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

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

[0016] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two types of electronic payment: Pattern 1 and Pattern 2. Details of Pattern 1 shown in Figure 2 will be described later.

[0017] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 decodes the store code image 60 using its optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL (store identification information) is the domain of the electronic payment service to which store identification information has been added, and is associated with an affiliated store ID, store ID, etc. in the payment server 100 (described below). The payment application 20 transmits first payment information including the store URL and account ID to the payment server 100 (S2). The payment server 100 searches for store information (described below) using the affiliated store ID and store ID corresponding to the store URL, acquires information on the affiliated store name and store name (S3), and transmits the information to the payment application 20 (S4). The process of S3 may be executed by the payment application 20. In this case, the store information is stored in the memory of the user terminal device 10. The user inputs the payment amount into the user terminal device 10 on a screen displaying the affiliated store name and store name (S5). The user terminal device 10 then 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 app 20 (S8), and the payment app 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include information on the payment amount in addition to the store URL. In this case, the step of the user inputting the payment amount is omitted, and the payment amount information is included in the first payment information and transmitted to the payment server 100. Information on the affiliated store name and store name may be displayed on the payment completion screen.

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

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

[0020] [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, an information processing unit 150, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), a GPU (Graphics Processing Unit), or an SOC (System On Chip), or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

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

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

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

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

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

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

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

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

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

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

[0031] [Comparative Example] FIG. 7 is a diagram (1) for explaining the processing in an electronic payment service of a comparative example. In the comparative example, when a user activates a camera app that is pre-installed on user terminal device 10 and captures a code image (code information) installed in a store with the camera, user terminal device 10 displays interface screen IM1 on the display unit of user terminal device 10. For example, user terminal device 10 displays interface screen IM1 based on information encoded in the code image. Interface screen IM1 is a preset screen that is displayed when information (URL) encoded in the code image of the electronic payment service is read, and is a screen that is displayed in common even if the store is different. This series of processes takes approximately 2 seconds.

[0032] As described above, since the camera app cannot be used to make electronic payments for electronic payment services, the payment app 20 is launched to capture a code image and make electronic payments, as shown in Figure 8. Figure 8 is a diagram (2) for explaining the processing in the electronic payment service of the comparative example. When the user operates the icon for the payment app 20 on the home screen (IM11) of the OS (Operating System) of the user terminal device 10, the home screen IM12 for the payment app 20 is displayed.

[0033] When the scan button is operated on the home screen IM2, the payment app 20 activates the camera of the user terminal device 10. The user captures a code image with the camera (IM13). The payment app 20 acquires the store's identification information based on the captured code image and displays an interface screen IM4 for making electronic payments at the store. The interface screen IM4 includes the store's name. When a predetermined operation is performed on the interface screen IM4, the payment app 20 displays an interface screen IM5. The interface screen IM5 is an interface screen for inputting the payment amount. When the payment amount is entered on the interface screen IM5, the payment is completed, and the payment app 20 displays an interface screen IM6 indicating that the payment has been completed. This series of processes takes approximately 10 seconds.

[0034] As described above, in the comparative example, even if a code image was captured using the camera app, the process could not proceed to electronic payment, and it was necessary to capture the code image and perform electronic payment using payment app 20. For this reason, it sometimes took a relatively long time from when the user attempted to make payment until the payment was completed.

[0035] In this embodiment, the time required from when a user attempts to make a payment until the payment is completed can be reduced.

[0036] [Outline of this embodiment] The user terminal device 10 displays a first interface screen (interface screen IM23, described later) on the display unit of the user terminal device 10 based on a code image (code information) of an electronic payment service captured by a camera (a function of a standard camera app) installed in the user's user terminal device 10. When a transition button on the first interface screen is operated, the user terminal device 10 displays a second interface screen (interface screen IM24 or IM25, described later) of a store of the electronic payment service corresponding to the code image on the display unit, which second interface screen allows the user to input the amount of electronic payment using the electronic payment service.

[0037] FIG. 9 is a diagram illustrating the processing in the electronic payment service of this embodiment. When a user activates a camera app (IM21) that is pre-installed on the user terminal device 10 and captures a code image (code information) installed at a store with the camera (IM22), the user terminal device 10 displays an interface screen IM23 on the display unit of the user terminal device 10. For example, the user terminal device 10 displays the interface screen IM23 based on the information encoded in the code image. For example, the user terminal device 10 uses a pre-installed web browser to access the encoded URL and display the interface screen IM23. At this time, the store's identification information encoded in the code image is added (associated) to the URL or the interface screen IM23. Adding (associating) the URL means that the store's identification information can be provided to the payment app 20 when a transition button B, described below, is operated. For example, the store's identification information may be included in the URL. This series of processes takes approximately 2 seconds. The time from launching the camera app to capturing the code image is about 1 second, and the time from capturing the code image to displaying the interface screen IM23 is also about 1 second.

[0038] When transition button B on interface screen IM23 is operated, the user terminal device 10 activates the payment app 20 so that the user can operate it, and provides the payment app 20 with store identification information. In response to this process, the payment app 20 displays interface screen IM24 for making an electronic payment according to the store identification information. The interface screen IM23 (web page) is linked to the store identification information of the electronic payment service obtained from the code information, and when transition button B is operated, the user terminal device 10 (payment app 20) displays interface screen IM24 (second interface screen) on the display unit for allowing the user to input the amount of an electronic payment using the electronic payment service at the store based on the store identification information. For example, when transition button B is operated, the payment app 20 installed on the user terminal device 10 acquires store identification information and displays interface screen IM24 on the display unit based on the acquired store identification information. The payment app 20 displays interface screen IM24, for example, based on a preset link.

[0039] Here, the link that displays interface screen IM24 when transition button B is operated is a link different from a deep link, and is a link that is activated (displays a predetermined screen provided by payment application 20) on the condition that payment application 20 is installed when the link is accessed. Links that are different from deep links are so-called universal links, app links, and other links that are generated to activate a specified application.

[0040] For example, interface screen IM24 includes buttons for selecting a store name, a payment method, etc. In the above process, payment application 20 may provide store identification information to payment server 100 and obtain, from payment server 100, information linked to the store identification information in the electronic payment service, such as the store name.

[0041] For example, if deep links are used in the above process, and the deep links conflict (if part or all of the deep link URL is duplicated), it could result in the launch of another app from a group company, for example.

[0042] In contrast to this, in the present embodiment, by using a link different from the deep link as described above, it is possible to prevent other applications from being launched.

[0043] When the user performs a predetermined operation (for example, pressing the Next button) on interface screen IM24, payment application 20 displays interface screen IM25. Interface screen IM25 includes an input field for inputting the payment amount. Display of interface screen IM24 may be omitted, and information such as the store name may be included on interface screen IM25. Note that the aforementioned interface screen IM24 may also include an input field for inputting the amount.

[0044] When the payment amount is entered on interface screen IM25, payment application 20 executes the electronic payment in cooperation with payment server 100 and displays interface screen IM26. Interface screen IM26 is an interface screen that indicates that the electronic payment has been completed. Interface screen IM26 includes information such as the store name and payment amount. It takes about 2 seconds from the display of interface screen IM24 to interface screen IM26.

[0045] As described above, in this embodiment, capturing a code image using a camera app allows seamless electronic payment using payment app 20, thereby improving user convenience. Furthermore, in this embodiment, the time from when a user attempts to make an electronic payment using a code image to when the electronic payment is completed can be shortened compared to the processing time in the comparative example. For example, in the comparative example, as described in Figures 7 and 8, it took 10 or 12 seconds, but in this embodiment, electronic payment can be completed in 4 seconds, a time saving of 6 or 8 seconds.

[0046] [Control on interface screen IM23] The user terminal device 10 determines whether transition button B has been operated within a predetermined time from when interface screen IM23 (first interface screen) is displayed. The user terminal device 10 (web browser) counts the time and performs the determination based on command information (e.g., a script) associated with the web page. If transition button B has been operated within the predetermined time, the user terminal device 10 displays interface screen IM24 (second interface screen) on the display unit. If transition button B has not been operated within the predetermined time, or if transition button B has been operated after the predetermined time has elapsed, the user terminal device 10 displays an error screen on the display unit. Figure 10 is a diagram showing an example of an error screen.

[0047] As described above, the user terminal device 10 can prevent the following event (1) from occurring by restricting the transition to the interface screen IM24 based on the predetermined time limit.

[0048] (1) If no time limit is set, payments to an unintended member store (store) may occur. This is prevented. For example, suppose a user opens interface screen IM23 to make an electronic payment at a first member store, and then, with interface screen IM23 still open, moves to the next member store, the second member store. If the user operates transition button B on interface screen IM23, which is still open during electronic payment at the second member store, without a time limit set, interface screen IM24 for electronic payment at the first member store may be displayed. If processing continues in this state, payment will be made at the first member store. However, by setting a time limit, electronic payment at the first member store is prevented, as described above.

[0049] Furthermore, if no time limit is set, after closing a screen such as interface screen IM23, for some reason, information from a previously used merchant may be used to make an electronic payment from another merchant. However, by setting a time limit, electronic payments from the first merchant are prevented from being made, as described above.

[0050] Even in the case of the processing in the comparative example, for some reason, information from a previously used member store may be used to make an electronic payment, but by imposing a time limit, electronic payments made at the first member store are prevented from occurring.

[0051] As mentioned above, past information is reset by the time limit, so the above event (1) is suppressed.

[0052] [flowchart] 11 is a flowchart showing an example of the flow of processing executed by (the functions of) user terminal device 10 and payment application 20. First, when a user operates the camera application to capture code information with the camera (S100), user terminal device 10 displays interface screen IM23 (first interface screen) on the display unit (S102). At this time, user terminal device 10 acquires the identification information of the store in the code information.

[0053] Next, the user terminal device 10 determines whether or not the transition button B has been operated within a predetermined time from when the interface screen IM23 was displayed (S104). If the transition button B has not been operated within the predetermined time, an error screen is displayed (S106). If the transition button B has been operated within the predetermined time, the user terminal device 10 starts the payment application 20 and provides the payment application 20 with the store identification information included in the code information (S108).

[0054] Next, the payment application 20 displays the interface screen IM24 (second interface screen) on the display unit based on the store identification information (S110). At this time, the payment application 20 may transmit the store identification information to the payment server 100 and obtain store information corresponding to the store identification information from the payment server 100.

[0055] As described above, user terminal device 10 displays the first interface screen in response to code information being captured by the camera app, and displays the second interface screen in payment app 20 when transition button B is operated, thereby improving user convenience. For example, the payment time using payment app 20 can be shortened compared to the comparative example, and operation is simplified, thereby improving user convenience.

[0056] According to the embodiment described above, the user terminal device 10 displays a first interface screen on the display unit of the user terminal device based on code information of the electronic payment service captured by a camera installed in the user's user terminal device, and when the transition button on the first interface screen is operated, displays a second interface screen of the store of the electronic payment service corresponding to the code information on the display unit, which second interface screen allows the user to enter the amount related to the electronic payment using the electronic payment service, thereby improving convenience for the user.

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

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

Claims

1. A camera application program installed on the user's user terminal device is launched, and a first interface screen is displayed on a display unit of the user terminal device based on code information of the electronic payment service captured by a camera installed on the user terminal device; When the transition button on the first interface screen is operated, a payment application program of the electronic payment service is started, and a second interface screen of a store of the electronic payment service corresponding to the code information is displayed on the display unit by the payment application program, the second interface screen being for allowing the user to input an amount related to electronic payment using the electronic payment service. User terminal device.

2. when the transition button is operated within a predetermined time from when the first interface screen is displayed, the second interface screen is displayed on the display unit; displaying an error screen on the display unit when the transition button is not operated within a predetermined time from when the first interface screen is displayed, or when the transition button is operated after the predetermined time has elapsed; 2. The user terminal device according to claim 1.

3. When the transition button is operated within the predetermined time, the second interface screen is displayed on the display unit to prompt the user to input the amount of electronic payment using the electronic payment service at the store based on identification information of the store that provides the electronic payment service obtained from the code information.

3. The user terminal device according to claim 2.

4. displaying the first interface screen, which is a web page based on information obtained from the code information, on the display unit; The web page is linked to the identification information of the store that provides the electronic payment service, which is obtained from the code information; When the transition button is operated, the second interface screen is displayed on the display unit to prompt the user to input an amount related to the electronic payment using the electronic payment service at the store based on the store's identification information.

3. The user terminal device according to claim 1 or 2.

5. When the transition button is operated, an electronic payment application of the electronic payment service installed on the user terminal device acquires identification information of the store, displaying the second interface screen on the display unit based on the acquired identification information of the store; 5. The user terminal device according to claim 4.

6. When the transition button is operated, the second interface screen is displayed on the display unit based on a preset link; the link is a link that causes the second interface screen to be displayed on the display unit on condition that the electronic payment application is installed.

6. The user terminal device according to claim 5.

7. The computer In response to a user's operation, a camera application program installed in the user's user terminal device is started, and a camera mounted on the user terminal device is started; displaying a first interface screen on a display unit of the user terminal device based on code information of the electronic payment service captured by the camera; When the transition button on the first interface screen is operated, a payment application program of the electronic payment service is started, and a second interface screen of a store of the electronic payment service corresponding to the code information is displayed on the display unit by the payment application program, the second interface screen being for allowing the user to input an amount related to electronic payment using the electronic payment service. Information processing methods.

8. On the computer, a camera application program installed on the user's user terminal device is started, and when a transition button included in a first interface screen displayed on the display unit of the user terminal device is operated based on code information of the electronic payment service captured by a camera mounted on the user terminal device, a payment application program of the electronic payment service is started, the payment application program is controlled to an operable state based on the user's operation, and identification information of the store of the electronic payment service corresponding to the code information is obtained; displaying on the display unit a second interface screen of the store of the electronic payment service according to the acquired store identification information, the second interface screen being for allowing the user to input an amount related to electronic payment using the electronic payment service; Application program.

Citation Information

Patent Citations

  • Prepaid type electronic money settlement system

    JP2010033546A

  • Settlement server, settlement system, settlement method, and settlement program

    JP2011210171A

  • Account payment system and account payment method

    JP2022171342A

  • Program for settlement

    JP2023034889A

  • Program, information processing terminal, and information processing method

    JP2024005079A