User terminal device, information processing method, and application program

Abstract

To provide services that are highly convenient for users. [Solution] A user terminal device that displays a first interface screen on the display unit of the user terminal device based on code information of an electronic payment service captured by a camera mounted on the user terminal device, and when a transition button on the first interface screen is operated, displays a second interface screen on the display unit of the store of the electronic payment service corresponding to the code information, which allows the user to input the amount related to the electronic payment using the electronic payment service.

Description

Technical Field

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

Background Art

[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 application to activate a camera and use the electronic payment service.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the conventional technology, the convenience for the user may not be sufficiently high in some cases.

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

Means for Solving the Problems

[0006] One aspect of the present invention is a user terminal device that displays a first interface screen on the display unit of a user terminal device based on code information of an electronic payment service captured by a camera mounted on the user terminal device, and when a transition button on the first interface screen is operated, displays a second interface screen on the display unit of a store of the electronic payment service corresponding to the code information, which allows the user to input the amount related to the 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 drawing]

[0008] [Figure 1] This diagram shows an example of a configuration for implementing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payments. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payments. [Figure 4] This is a diagram showing the configuration of payment server 100. [Figure 5] This figure shows an example of the contents of user information 172. [Figure 6] This figure shows an example of the contents of merchant / store information 176. [Figure 7] Figure (1) illustrates the processing in the comparative example electronic payment service. [Figure 8] Figure (2) illustrates the processing in the comparative example electronic payment service. [Figure 9] This is a diagram illustrating the processing in the electronic payment service of this embodiment. [Figure 10] This figure shows an example of an error screen. [Figure 11]This flowchart shows an example of the processing flow performed by the user terminal device 10 (and its functions) and the payment application 20. [Modes for carrying out the invention]

[0009] The following describes embodiments of the information processing apparatus, information processing method, and program of the present invention with reference to the drawings. Various devices such as "servers" that appear below, which provide services to users or perform internal analysis, may be implemented by a distributed group of devices, and the operators of each device may be different. Furthermore, the owner of the hardware of the devices (the provider of the cloud server) and the operator that actually operates them may also be different. The application program and the payment server work together to provide an electronic payment service. In the following description, the application program will be referred to as a payment app. The electronic payment service is a service that supports payment for the purchase of goods and services at a store. A store is, for example, a physical store (real store) that exists in the real world, but may also include a virtual store for e-commerce. A virtual store may include one provided by an entity different from the operator of the electronic payment service. In that case, when settling a purchase at a virtual store, the user is controlled to transition to the interface screen of the electronic payment service. In the electronic payment service, a store is treated as belonging to, for example, a merchant (brand), and processing such as payment when a purchase is made at a store is mainly carried out between the user and the merchant. Alternatively, processing such as payment may be carried out between the user and the store.

[0010] [Electronic payment service] Figure 1 shows an example of the configuration of an electronic payment system that implements electronic payment services. The electronic payment service is implemented with a payment server 100 at its center. An electronic payment system that implements electronic payment services includes, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, and a payment server 100. These devices communicate with each other, for example, via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, provider equipment, etc.

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

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

[0013] [Store Terminal Device #1] The first store terminal device 50 is installed in a store, for example. 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. Note that the store code image 60 may be displayed by a display placed in the store (which may be a 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 franchise store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. In the second store terminal device 70, an interface 72 for franchise stores operates. The interface 72 for franchise stores may be an application for franchise stores or a browser. The interface 72 for franchise stores accepts settings of coupons, etc. by the operator of the franchise store and transmits them to the settlement server 100. The second store terminal device 70 which is a smartphone has a function of displaying a code image corresponding to the store code image or reading the code image displayed by the user terminal device 10 by executing an application for franchise stores.

[0015] [Settlement Server] The settlement server 100 realizes electronic settlement based on the settlement 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 a franchise store server. In that case, the settlement information is transmitted from the POS device to the settlement server 100 via the franchise store server. In the following description, without particularly distinguishing this, it is assumed that the settlement information is transmitted from the first store terminal device 50.

[0016] FIG. 2 and FIG. 3 are sequence diagrams illustrating a general flow of electronic payment. There may be two patterns, Pattern 1 and Pattern 2, in electronic payment. The details of Pattern 1 shown in FIG. 2 will be described later.

[0017] In the case of Pattern 1 shown in FIG. 2 (hereinafter referred to as user scan), the user terminal device 10 decodes the store code image 60 by means of an optical reading function (S1). The store code image 60 contains information on the store URL (Uniform Resource Locator). This store URL (store identification information) is obtained by adding information that can identify the store to the domain of the electronic payment service, and is associated with the franchise store ID, 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 franchise store ID and store ID corresponding to the store URL, acquires information on the franchise store name and store name (S3), and transmits it 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 storage unit of the user terminal device 10. The user inputs the payment amount into the user terminal device 10 on the screen where the franchise store name and store name are displayed (S5). Then, the user terminal device 10 generates the second payment information including at least the payment amount, and transmits it to the payment server 100 (S6). The payment server 100 performs an electronic payment based on the received second payment information (S7). Then, the payment server 100 transmits a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays a payment completion screen (S9). When the store code image 60 is displayed by a display placed in the store, the store code image 60 may contain not only the store URL but also payment amount information. In this case, the procedure for the user to input 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 franchise store name and store name may be included and displayed on the payment completion screen.

[0018] In the case of Pattern 2 shown in Figure 3 (hereinafter referred to as Store Scan), when the payment app 20 is launched, when a payment operation is performed in the payment app 20, when it is time for an automatic update (for example, every minute), and at other times, the payment app 20 sends a request to the payment server 100 to issue a one-time code (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 that was generated based on the one-time code (S14). The user holds the display surface of the user terminal device 10 over the first store terminal device 50 (presents it), and the first store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). Then, the first store terminal device 50 generates payment information including the one-time code, payment amount, merchant ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is obtained in advance by barcode scanning or manual input. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs the electronic payment (S17). The payment server 100 then sends a payment completion notification to the payment app 20 (S18), and the payment app 20 displays a payment completion screen (S19).

[0019] Furthermore, electronic payment may be performed using only one of the above patterns. Also, the "account ID" explained in Figure 2 may be other information that can be used as user identification information (for example, a phone number). In addition, the issuance of a one-time code may be omitted during store scanning, and the payment app 20 may display a code image generated based on the user's account ID. In that case, the payment server 100 will identify the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0020] [Payment Server Functional Configuration] Figure 4 is a diagram of the configuration of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a content provision unit 120, a payment processing unit 130, an information management unit 140, an information processing unit 150, and a storage unit 170. Components other than the communication unit 110 and the storage unit 170 are realized, for example, by 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 LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), GPU (Graphics Processing Unit), and SOC (System On Chip), or by the cooperation of software and hardware. The program may be stored in advance on a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device equipped with a non-transient storage medium), or it may be stored on a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed on the storage device when the storage medium is inserted into the drive device.

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

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

[0023] The content provider unit 120, for example, has the functionality of a web server and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The content provider unit 120 reads the 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 the content is being played by the payment application 20 and transmits the aforementioned payment information to the payment server 100. The above content may also be generated by the payment application 20. In this case, the content provider unit 120 provides the payment application 20 with the information necessary for generating the content.

[0024] The payment processing unit 130 performs payment processing based on 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] Figure 5 shows 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, user URL, account ID, telephone number, password, as well as information such as email address, user ID, name, address, date of birth, registration date, charge balance, credit payment settings, credit payment limit, credit payment amount, available credit payment amount, payment method settings, bank account, credit card number, charge history information, and payment history information. The user URL is used for money transfer processing between users. When registering for a new electronic payment service, registration of a telephone 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 (or does not have to set). Similarly, the email address and name, address, and date of birth are also information that the user can set at will (or does not have to set). The registration date is the date the user registered for the electronic payment service (the date the account was created). Hereafter, 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 set by the user by sending money to their account in advance. Methods of sending money include sending from an ATM (Automatic Teller Machine) of a designated provider (bank) and sending from a registered bank account. The credit payment setting indicates whether or not the user has completed the settings to enable electronic payments by credit card, and is set to either "Completed" or "Not Completed". The credit payment limit is the monthly limit for credit payments, the credit payment amount is the amount already used for credit payments in the current month, and the available credit payment amount is the amount available for credit payments in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the diagram shows only one credit payment limit, in reality there are also daily limits, and the lower of these may be set as the credit payment limit. Further details on credit payments will be described later. The payment method setting indicates whether the user will use electronic payment with the charge balance or payment by credit card at that time. The bank account and credit card number information, respectively, refers to the bank account or credit card number (account number, card number) to which funds can be deposited into the electronic payment service. The charge history information is a record of when the user has previously sent money to the electronic payment service to increase the charge balance. The payment history information shows the details of each payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

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

[0028] [Electronic payment] When the payment processing unit 130 obtains payment information from the user terminal device 10 or the first store terminal device 50, it refers to the user information 172 to obtain the user's "payment method setting". 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, which is managed in association with the user ID, and increasing the value of the merchant's sales proceeds item. For example, the value of the merchant's sales proceeds item is not used as electronic money itself, but rather the amount corresponding to the value of the sales proceeds item is transferred to the bank account in a cycle according to the agreement between the merchant and the electronic payment service.

[0029] The payment processing unit 130 performs electronic payment as follows for users whose "settings information" is set to "credit payment". Credit payment is a payment method that is carried out 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 donor and allows electronic payment that does not depend on the charge balance within the credit payment limit. In order to use the credit payment service, it may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used by credit payment is settled in a lump sum for the month on the payment date of the following month, for example, by withdrawal from a bank account. In this case, the payment processing unit 130 performs a provisional settlement by adding the settlement amount to the amount used by credit payment and subtracting the same amount from the available credit payment limit. When the closing date arrives, it processes the payment for the current month to be withdrawn on the payment date of the following month as described above, or requests the credit card company operator to perform the said process. If the settlement amount exceeds the available credit payment limit at the time of provisional settlement, an error notification is sent back to the payment application 20.

[0030] The Information Management Unit 140 acquires information provided by other server devices and terminal devices. Based on the information acquired from the user terminal device 10 and the second store terminal device 70, the Information Management Unit 140 manages user information 172 and affiliated store / store information 176. The Information Management Unit 140 performs operations such as adding, editing, and deleting new records for user information 172 and affiliated store / store information 176.

[0031] [Comparative Example] Figure 7 is a diagram (1) illustrating the processing in the comparative example's electronic payment service. In the comparative example, when a user activates the camera application standardly installed on the user terminal device 10 and captures a code image (code information) installed in the store with the camera, the user terminal device 10 displays the interface screen IM1 on its display unit. For example, the user terminal device 10 displays the interface screen IM1 based on the information encoded in the code image. The interface screen IM1 is a pre-configured screen that is displayed when the information (URL) encoded in the code image of the electronic payment service is read, and it is a screen that is displayed in the same way even if the store is different. The time required for this series of processes is about 2 seconds.

[0032] As described above, since electronic payments cannot be made using the camera app, the payment app 20 is launched and a code image is captured to perform the electronic payment, as shown in Figure 8. Figure 8 is Figure (2) for illustrating 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 of the payment app 20 is displayed.

[0033] On the home screen IM2, when the scan button is pressed, the payment application 20 activates the camera on the user terminal device 10. The user captures a code image with the camera (IM13). Based on the captured code image, the payment application 20 obtains the store's identification information and displays the interface screen IM4 for making an electronic payment 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 application 20 displays the interface screen IM5. The interface screen IM5 is for entering the payment amount. Once the payment amount is entered on the interface screen IM5, the payment is completed, and the payment application 20 displays the payment completion interface screen IM6. This entire process 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. Instead, it was necessary to use the payment app 20 to capture the code image and perform the electronic payment. As a result, the time required from the moment the user attempted to make a payment until the payment was completed was sometimes relatively long.

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

[0036] [Summary of this invention] 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 the electronic payment service captured by the camera installed in the user terminal device 10 (function of the standard camera application). 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 the electronic payment service store corresponding to the code image, which is a second interface screen for inputting the amount related to the electronic payment using the electronic payment service.

[0037] Figure 9 is a diagram illustrating the processing in the electronic payment service of this embodiment. When a user activates the camera application standardly installed on the user terminal device 10 (IM21) and captures a code image (code information) installed in the store with the camera (IM22), the user terminal device 10 displays the interface screen IM23 on its display unit. 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 its built-in web browser to access the encoded URL and display the interface screen IM23. At this time, the store identification information encoded in the code image is added (associated) to the URL or interface screen IM23. Adding (associating) means making it possible to provide the store identification information to the payment application 20 when the transition button B, described later, is operated. For example, the store identification information may be included in the URL. The time required for this series of processes is approximately 2 seconds. The time from launching the camera app to capturing the code image is approximately 1 second, and the time from capturing the code image to the display of the IM23 interface screen is also approximately 1 second.

[0038] When the transition button B on interface screen IM23 is operated, the user terminal device 10 activates the payment application 20 to a state where the user can operate it and provides the payment application 20 with the store's identification information. In response to this process, the payment application 20 displays interface screen IM24 for performing electronic payment according to the store's identification information. The interface screen IM23 (web page) is linked to the store's identification information for the electronic payment service obtained from the code information, and when the transition button B is operated, the user terminal device 10 (payment application 20) displays interface screen IM24 (second interface screen) on the display unit for inputting the amount related to the electronic payment using the electronic payment service at the store based on the above store's identification information. For example, when the transition button B is operated, the payment application 20 installed on the user terminal device 10 acquires the store's identification information and displays interface screen IM24 on the display unit based on the acquired store's identification information. The payment application 20 displays interface screen IM24, for example, based on a pre-configured link.

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

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

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

[0042] In contrast, in this embodiment, by using a link different from deep linking as described above, it is possible to suppress the launch of other applications.

[0043] On interface screen IM24, when the user performs a predetermined operation (for example, pressing the "Next" button), the payment application 20 displays interface screen IM25. Interface screen IM25 includes an input field for entering the payment amount. The display of interface screen IM24 may be omitted, and interface screen IM25 may contain information such as the store name. Alternatively, the aforementioned interface screen IM24 may also include an input field for entering the amount.

[0044] When the payment amount is entered on interface screen IM25, the payment application 20 works with the payment server 100 to execute the electronic payment and displays interface screen IM26. Interface screen IM26 is an interface screen that indicates that the electronic payment has been completed. Interface screen IM26 contains information such as the store name and payment amount. The time from the display of interface screen IM24 to interface screen IM26 is approximately 2 seconds.

[0045] As described above, in this embodiment, by capturing a code image using the camera application, electronic payment using the payment application 20 can be performed seamlessly, thereby improving user convenience. Furthermore, in this embodiment, the time from when the 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 of the comparative example. For example, in the comparative example, as explained in Figures 7 and 8, it took 10 or 12 seconds, but in this embodiment, electronic payment can be performed in 4 seconds, shortening the time by 6 or 8 seconds.

[0046] [Regarding control on interface screen IM23] The user terminal device 10 determines whether the transition button B was operated within a predetermined time frame from the time the interface screen IM23 (first interface screen) is displayed. The above time counting and determination is performed by the user terminal device 10 (web browser) based on command information (e.g., a script) associated with the web page. If the transition button B is operated within the predetermined time frame, the user terminal device 10 displays the interface screen IM24 (second interface screen) on its display unit. If the transition button B is not operated within the predetermined time frame, or if the transition button B is operated after the predetermined time has elapsed, the user terminal device 10 displays an error screen on its display unit. Figure 10 shows an example of an error screen.

[0047] As described above, the user terminal device 10 can suppress the occurrence of the event described in (1) below by restricting the transition to the interface screen IM24 based on a predetermined time limit.

[0048] (1) If no time limit is set, payments to unintended merchants (stores) may occur, but this will be suppressed. For example, suppose a user opens interface screen IM23 to make an electronic payment at the first merchant, and while interface screen IM23 is still open, the user moves to the next merchant, the second merchant. If the user operates the transition button B on the open interface screen IM23 during the electronic payment at the second merchant, if no time limit is set, the interface screen IM24 for the electronic payment at the first merchant may be displayed. If the process proceeds in this state, the payment will be made at the first merchant. However, by setting a time limit, the electronic payment at the first merchant as described above will be suppressed.

[0049] Furthermore, if no time limit is imposed, after closing an interface screen such as IM23, for some reason, information from a previously used merchant may be used for electronic payment at another merchant. However, by imposing a time limit, the occurrence of electronic payments at the first merchant as described above is suppressed.

[0050] Even in the case of processing comparative examples, for some reason, information from a previously used merchant may be used, and information from another merchant may be used for electronic payments. However, by imposing a time limit, the occurrence of electronic payments at the first merchant as described above is suppressed.

[0051] As described above, past information is reset by the time limit, thus suppressing the event described in (1) above.

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

[0053] Next, the user terminal device 10 determines whether the transition button B was operated within a predetermined time from the time the interface screen IM23 was displayed (S104). If the transition button B was not operated within the predetermined time, an error screen is displayed (S106). If the transition button B was operated within the predetermined time, the user terminal device 10 launches the payment application 20 and provides the payment application 20 with the store identification information contained 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 also send 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, the user terminal device 10 can improve user convenience by displaying the first interface screen in response to the capture of code information by the camera application, and by displaying the second interface screen to the payment application 20 when the transition button B is operated. For example, the payment time using the payment application 20 can be shortened compared to the comparative example, and the operation can be simplified, thereby improving user convenience.

[0056] According to the embodiments 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 mounted on the user terminal device, and when a transition button on the first interface screen is operated, the user can improve convenience by displaying a second interface screen on the display unit of the store of the electronic payment service corresponding to the code information, which allows the user to input the amount related to the electronic payment using the electronic payment service.

[0057] Although embodiments for carrying out the present invention have been described above using examples, the present invention is not limited in any way to these embodiments, and various modifications and substitutions can be made without departing from the spirit of the present invention. [Explanation of symbols]

[0058] 10. User terminal device 20 Payment Apps 100 Payment Servers 120 Content Provision Department 130 Payment Processing Unit 140 Information Management Department

Claims

[Claim 1] Based on the code information of the electronic payment service captured by the camera mounted on the user's terminal device, the first interface screen is displayed on the display unit of the user terminal device. When the transition button on the first interface screen is operated, the display unit displays the second interface screen of the store of the electronic payment service corresponding to the code information, which is a second interface screen for inputting the amount related to the electronic payment using the electronic payment service. User terminal device.

Images