Payment application program, information processing device, and information processing method

Abstract

The aim is to improve the usability of payment applications installed on user terminals in electronic payment services. [Solution] A payment application program that is pre-installed on a terminal device used by a user of electronic payment to use electronic payment using an identification code, comprising: a reception unit that receives operations from the user to the terminal device; and a display control unit that controls the display on the display unit of the terminal device based on the operations received by the reception unit, wherein the display control unit transitions to a first payment screen used for electronic payment when the reception unit receives a first operation to a first operation button displayed on the display unit, and transitions to a second payment screen used for electronic payment, which is different from the first payment screen, when the reception unit receives a second operation to the first operation button that is different from the first operation.

Description

Technical Field

[0001] The present disclosure relates to a settlement application program, an information processing apparatus, and an information processing method.

Background Art

[0002] In the settlement for goods or services, cashless settlement without using money is becoming popular. In particular, electronic settlement using a settlement application program (hereinafter referred to as a settlement app) that can be installed on a terminal device such as a smartphone has attracted attention due to its high convenience. There are the following two methods for the settlement method using a settlement app. The first settlement method is a method in which an identification code for a user (barcode or QR code (registered trademark)) in which the user's identification information is encoded is displayed on the user's terminal device, and a store staff reads it using a code reader of the store terminal. The second settlement method is a method in which an identification code for a store posted at the store is scanned by the user terminal and the payment amount is input.

[0003] Patent Document 1 describes an example of a screen used in the first settlement method. Specifically, when a predetermined button on a screen on which buttons related to various services displayed on the user terminal after the settlement app is launched is operated, it transitions to a payment screen different from that screen, and an identification code for the user is enlarged and displayed on the payment screen. Patent Document 2 describes an example in which a scan screen used for reading a store code in the second settlement method is displayed on the user terminal and then transitions to an amount input screen.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

[0005] However, the technologies described in the patent documents have room for improvement in terms of enhancing the usability of payment applications.

[0006] This disclosure aims to improve the usability of payment applications installed on users' terminal devices in electronic payment services. [Means for solving the problem]

[0007] A payment application program according to one aspect of the present disclosure is a payment application program that is pre-installed on a terminal device used by a user of electronic payment to use electronic payment using an identification code, and comprises: a reception unit that receives operations from the user to the terminal device; and a display control unit that controls the display on the display unit of the terminal device based on the operations received by the reception unit, wherein the display control unit transitions to a first payment screen used for electronic payment when the reception unit receives a first operation to a first operation button displayed on the display unit, and transitions to a second payment screen used for electronic payment, which is different from the first payment screen, when the reception unit receives a second operation to the first operation button that is different from the first operation. [Effects of the Invention]

[0008] According to this disclosure, it is possible to improve the usability of payment applications installed on users' terminal devices in electronic payment services. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an overview of the first embodiment of the present disclosure. [Figure 2] This figure shows an overview of the second embodiment of the present disclosure. [Figure 3] This is a diagram showing an example of the system configuration of an electronic payment system. [Figure 4]This is a diagram showing an example of a screen used for electronic payments. [Figure 5] Block diagram showing an example of a user terminal hardware configuration. [Figure 6] This figure shows an example of the software configuration of a user terminal. [Figure 7] This flowchart shows the flow of the display control process in the first embodiment. [Figure 8] This figure shows an example of screen transitions in the first embodiment. [Figure 9A] This figure shows an example of the screen after the second operation in the second embodiment. [Figure 9B] This figure shows an example of the screen after the second operation in the second embodiment. [Figure 9C] This figure shows an example of the screen after the second operation in the second embodiment. [Figure 9D] This figure shows an example of the screen after the second operation in the second embodiment. [Figure 9E] This figure shows an example of the screen after the second operation in the second embodiment. [Figure 10] This figure shows an example of the My Code screen. [Figure 11] This flowchart shows the flow of the display control process in the second embodiment. [Figure 12] This diagram shows the flowchart that follows Figure 11. [Modes for carrying out the invention]

[0010] Preferred embodiments of the payment application program, information processing device, and information processing method relating to this disclosure will be described in detail below with reference to the drawings. However, these embodiments do not limit the payment application program, information processing device, and information processing method relating to this disclosure. Furthermore, identical components will be denoted by the same reference numerals in the following embodiments, and redundant descriptions will be omitted. In this specification, the payment application program will be referred to as a payment app.

[0011] FIG. 1 is a diagram showing an overview of the first embodiment of the present disclosure. A settlement application according to an embodiment of the present disclosure is a program pre-installed in a terminal device (hereinafter referred to as a user terminal) used by a user of electronic payment to utilize electronic payment using an identification code. The settlement application has a reception unit that receives an operation by a user with respect to the user terminal, and a display control unit that controls the display on the display unit of the user terminal based on the operation received by the reception unit. When the reception unit receives a first operation on the first operation button displayed on the display unit, the display control unit causes a transition to a first settlement screen used for electronic settlement. When the reception unit receives a second operation on the first operation button, which is different from the first operation, the display control unit causes a transition to a second settlement screen used for electronic settlement, which is different from the first settlement screen.

[0012] The first settlement screen is a screen including a user code in which the identification information of the user is encoded. Hereinafter, the first settlement screen is referred to as a payment screen 110 in this specification. The second settlement screen is a screen for reading a store code in which the identification information of the store is encoded. The second settlement screen is referred to as a scan screen 120 in this specification.

[0013] Although details will be described later, the payment method using the settlement application includes a first settlement method of reading the user code displayed on the user terminal using a code reader of the store terminal, and a second settlement method of reading the store code posted in the store using the user terminal and inputting the payment amount. In the following description, the first settlement method is also referred to as store scan, and the second settlement method is also referred to as user scan. The first settlement screen is a settlement screen used in the first settlement method. The second settlement screen is a settlement screen used in the second settlement method.

[0014] The first operation button is displayed on the top screen 100 displayed immediately after the start of the settlement application program. The first operation button is referred to as a payment button 109 in this specification.

[0015] Figure 1(a) shows an example of the top screen 100. As shown in Figure 1(a), the first identification code 101 and the second identification code 102 are displayed in the code display area 104 on the top screen 100. The first identification code 101 is the user code described above and is a one-dimensional code such as a barcode. The second identification code 102 is the user code described above and is a two-dimensional code such as a QR code (registered trademark). At least one of the first identification code 101 and the second identification code 102 is displayed on the top screen 100. In the example in Figure 1(a), both are displayed. The first identification code 101 and the second identification code 102 displayed on the top screen 100 are user codes used in the first payment method.

[0016] On the top screen 100, a payment button 109, which is operated when transitioning to the payment screen 110, is displayed, for example, in the lower area of ​​the top screen 100. Also, a scan button 108, which is operated when transitioning to the scan screen 120, is displayed at the bottom of the code display area 104 on the top screen 100. Furthermore, the top screen 100 displays buttons that are operated when transitioning to the money transfer screen, points screen, transaction history screen, charge screen, and various other buttons that are operated when transitioning to various functions included in the payment app. These various functions included in the payment app are referred to as mini-apps in this specification. Mini-apps include money transfer functions, points functions, transaction history display functions, charge functions, coupon functions, utility bill payment functions, stamp card functions, shopping functions, finance functions, and other functions.

[0017] Furthermore, scrolling down the top screen will display other information such as coupon information and store information within the display area.

[0018] Furthermore, the payment button 109 is controlled to maintain its position before and after scrolling the top screen 100. That is, the payment button 109 is fixedly displayed in the same position before and after screen scrolling. On the other hand, the scan button 108 moves in conjunction with screen scrolling. That is, when screen scrolling is performed, the scan button 108 may move out of the display area and disappear from view.

[0019] As described above, in this disclosure, when a first operation is performed on the payment button 109 by the user, the display control unit transitions to the payment screen 110 shown in Figure 1(b). Furthermore, when a second operation different from the first operation is performed on the payment button 109, the display control unit transitions to the scan screen 120 shown in Figure 1(c).

[0020] In the example in Figure 1, the first operation is a tap operation and the second operation is a long press operation. However, the first operation is not limited to these operations and may be any other operation. The payment screen 110 and the scan screen 120 will be described later, but both the payment screen 110 and the scan screen 120 are screens used in electronic payments. The user may be allowed to set the assignment of operations for the payment button 109 to the destination screen.

[0021] According to this disclosure, the payment button 109 can accept multiple different operations, and the user can transition to different payment screens depending on the operation. Specifically, an operation on the payment button 109 can transition to either the payment screen 110 or the scan screen 120. This improves the usability of the payment application. In particular, to transition from the top screen 100 to the scan screen 120, the user previously had to operate the scan button 108 displayed on the top screen 100. However, the scan button 108 can move out of the display area and disappear when the top screen 100 is scrolled. In that case, the user had to scroll again to bring the scan button 108 back into the display area. On the other hand, the payment button 109 is always displayed in the same position even when scrolled. By long-pressing the payment button 109, the user can transition to the scan screen 120 faster than operating the scan button 108.

[0022] Figure 2 is a diagram illustrating an overview of the second embodiment of this disclosure. The payment application according to the second embodiment of this disclosure is a program that is pre-installed on a terminal device (user terminal) used by an electronic payment user to utilize electronic payment using an identification code. The payment application includes a reception unit that receives user operations on the user terminal, and a display control unit that controls the display on the user terminal's display unit based on the operations received by the reception unit. When the reception unit receives a first operation on a first operation button displayed on the display unit, the display control unit transitions to a first payment screen used for electronic payment. Furthermore, when the reception unit receives a second operation on the first operation button that is different from the first operation, the display control unit displays a selection of candidate screens to transition to.

[0023] Figure 2(a) shows an example of the top screen 100. The top screen 100 in Figure 2(a) is the same as that in Figure 1(a). As described above, in the second embodiment of this disclosure, when a first operation is performed on the payment button 109 by the user, the display control unit transitions to the payment screen 110 shown in Figure 2(b). Furthermore, when a second operation different from the first operation is performed on the payment button 109, the display control unit displays a selection of candidate screens to transition to, as shown in the top screen 100A of Figure 2(c).

[0024] The candidates for the destination screen include at least the first payment screen and a second payment screen used for electronic payments, which is different from the first payment screen. In the example in Figure 2(c), a first selection object 130 that transitions to the payment screen 110, which is the first payment screen, and a second selection object 140 that transitions to the scan screen 120, which is the second payment screen, are displayed. In this way, the candidates are displayed as operation buttons for transitioning to the destination screen. When the first selection object 130 is operated, the display control unit transitions the screen displayed on the display unit to the payment screen 110, and when the second selection object 140 is operated, the display control unit transitions the screen displayed on the display unit to the scan screen 120.

[0025] Furthermore, the candidate screens to transition to may include function screens displayed within the functions (mini-apps) included in the payment application program. A function screen is, for example, the My Code screen used when receiving a remittance from another user. A function screen may also be a screen displayed within a points function or a coupon function.

[0026] In the example in Figure 2, the first operation is a tap operation, and the second operation is a long press operation. However, the first operation is not limited to these operations and may be any other operation.

[0027] Thus, according to the payment app of this disclosure, when a second operation is received by the payment button 109, a selection of screen transition destinations can be displayed according to the second operation. When the user selects one of the candidates, the app can transition to the selected destination screen. This improves the usability of the payment app. In particular, conventionally, in order to transition from the top screen 100 to the scan screen 120, the scan button 108 displayed on the top screen 100 had to be operated. However, the scan button 108 may move out of the display range and disappear due to scrolling of the top screen 100. In that case, the user had to scroll again to bring the scan button 108 back into the display range. On the other hand, since the payment button 109 is always displayed in the same position even when scrolling, by long-pressing the payment button 109, the user can transition to the scan screen 120 faster than operating the scan button 108.

[0028] <First Embodiment> (Overview of the electronic payment system) This document outlines an electronic payment system using the payment application program (hereinafter referred to as the "payment app") related to this disclosure. Figure 3 shows an example of the system configuration of the electronic payment system 1. As shown in Figure 3, the electronic payment system 1 includes a user terminal 2, a store terminal 3, and an electronic payment server 5. The store terminal 3 and the electronic payment server 5 are connected to each other via a network 4. In addition, the user terminal 2 and the electronic payment server 5 are connected to each other via a network 4.

[0029] In this specification, a user is a person who makes a payment for goods or services at a store using a payment application. The user obtains an account for the electronic payment service provided by the electronic payment system 1, for example, using the account management function of the payment application. The user's account is managed by the electronic payment server 5 and is linked to the user's identification information and the user's electronic account. The user can receive the electronic payment service by installing the payment application 200 on the user terminal 2. The electronic payment service can also be used by accessing the website provided by the electronic payment server 5 using a general web browser.

[0030] (Store terminal) The store terminal 3 is an information processing device used by stores or service providers that have a contract with a service provider that provides electronic payment services. The store terminal 3 consists of at least a computer having a product price acquisition function, an optical reading function, a program execution function, and a communication function. The store terminal 3 includes a so-called POS (Point of Sale) device, and the product price acquisition function and optical reading function may be implemented by the POS device. The optical reading function is implemented by a code reader 31 such as a barcode reader that reads images of one-dimensional codes such as barcodes, or a camera that reads images of two-dimensional codes such as QR codes (registered trademark). In addition, a store code image 32 is displayed in the store. The store code image 32 shows the store URL, which is the store's identification information, in the form of a two-dimensional code such as a QR code (registered trademark). The store code image 32 may be printed on paper or plastic media and displayed, or it may be displayed on a screen. Hereinafter, stores or service providers that have a contract with a service provider that provides electronic payment services will be referred to as member stores. Member businesses include, for example, organizations that operate multiple physical stores or online shops. A "store" is any place where goods or services are actually provided to users, such as shops, restaurants, department stores, movie theaters, or gyms. "Goods" include tangible items such as goods that users actually acquire at a store, or intangible items such as image data, video data, music data, and game programs. "Services" are services that users actually receive at a store or similar establishment.

[0031] (Electronic payment server) The electronic payment server 5 is an information processing device that provides electronic payment services, including electronic payment processing and distribution of information related to electronic payments. It consists of at least a computer having communication and program execution functions. The electronic payment server 5 manages the electronic accounts of merchant stores and the electronic accounts of users who have accounts for the electronic payment service. It enables various payments, for example, by transferring electronic money between electronic accounts. The electronic payment server 5 may be implemented by a single information processing device or by multiple information processing devices.

[0032] (User terminal) User terminal 2 is a terminal device used when a user makes an electronic payment at a participating merchant. For example, a portable device such as a smartphone is commonly used. The payment app 200 is pre-installed on user terminal 2 when a user makes an electronic payment. The payment app 200 is operated and managed by the service provider that provides the electronic payment service. The payment app 200 will be described later. There are two main methods for making an electronic payment at a participating merchant using the payment app 200: store scan and user scan.

[0033] (Store scan) In store scanning, the store terminal 3 optically reads the user's identification code displayed on the user terminal 2 using a code reader 31, decodes the read identification code to obtain the user's identification information. The store terminal 3 sends the obtained user identification information along with a payment request to the electronic payment server 5. The electronic payment server 5 generates a one-time code in response to the payment request and returns it to the store terminal 3. The store terminal 3 adds the store's identification information and payment amount information to the received one-time code and sends it to the electronic payment server 5. Based on the information received from the store terminal 3, the electronic payment server 5 identifies the user's and store's electronic accounts from its database and performs the payment processing. Once the payment processing is complete, the electronic payment server 5 displays a payment completion screen on the user terminal 2. The store terminal 3 may send and receive payment-related information directly with the electronic payment server 5, or it may send and receive payment-related information via the server of an intermediate payment service provider.

[0034] For reading the identification code during store scanning, the identification code displayed on the top screen 100 shown in Figure 1(a) may be used, or the identification code displayed on the payment screen 110 shown in Figure 1(b) may be used. Figure 4(a) is a diagram illustrating the payment screen 110. The payment screen 110 is displayed on the display unit 206 of the user terminal 2 when the payment button 109 displayed on the top screen 100 is tapped by the user. The payment screen 110 displays a first identification code 111 and a second identification code 112 as user codes that encode the user's identification information. Note that at least one of the first identification code 111 and the second identification code 112 is displayed on the payment screen 110. In the example in Figure 4(a), both are displayed. The payment screen 110 may also display payment-related information such as the available amount, charge balance, and points. The payment screen 110 also displays a button 113 that is operated when transitioning to the scan screen 120 used in the user scan described later. To transition from the payment screen 110 to the scan screen 120, simply operate button 113. To return from the payment screen 110 to the top screen 100, simply operate button 114. Details regarding screen transitions will be described later.

[0035] (User scan) In the user scan, the user terminal 2 reads a store code image 32, such as a QR code (registered trademark), displayed in the store. The store code image 32 contains information about the store's URL. The payment application 200 on the user terminal 2 adds the user's identification information to the read store URL information and sends it to the electronic payment server 5. The electronic payment server 5 identifies the user and store from its database based on the received store URL and user identification information, and displays an amount input screen on the user terminal 2. The user terminal 2 accepts the amount input by the user on the amount input screen and sends the entered amount information to the electronic payment server 5. The electronic payment server 5 performs the settlement process between the identified user and store's electronic accounts. Once the settlement process is complete, a settlement completion screen is displayed on the user terminal 2.

[0036] For reading the store code image 32 during user scanning, the scan screen 120 shown in Figure 4(b) is used. The user operates the payment app 200 to display the scan screen 120 on the display unit 206 of the user terminal 2, and takes a picture of the store code image 32 displayed in the store so that it fits within the frame 121. The user can transition to the scan screen 120 by tapping the scan button 108 displayed on the top screen 100 shown in Figure 1(a), or by tapping the button 113 displayed on the payment screen 110 shown in Figure 4(a). To return to the payment screen 110 from the scan screen 120, the user taps the button 122 on the scan screen 120. To return to the top screen 100 from the scan screen 120, the user operates the button 114.

[0037] Figure 5 shows the hardware configuration of the user terminal 2 according to this embodiment. An example of the user terminal 2 is shown, specifically the internal configuration of a smartphone. In this embodiment, the user terminal 2 is described using a smartphone as an example, but is not limited to this. The user terminal 2 may be, for example, a tablet device, a notebook PC (Personal Computer), a desktop PC, or a PDA (Personal Digital Assistant).

[0038] The user terminal 2 is equipped with a CPU 201, ROM 202, RAM 203, storage unit 204, operation unit 205, communication interface 208, camera 209, voice processing unit 210, and vibration detection unit 212, and each unit is connected via a bus 213. The operation unit 205 has a display unit 206 and an input unit 207.

[0039] The CPU 201 is the central processing unit and controls various parts of the user terminal 2. The CPU 201 reads programs stored in the ROM 202 or memory unit 204 into the RAM 203 and executes the read programs to realize the various functions contained in the programs. The CPU 201 may be an MPU (Micro Processing Unit) or an ASIC (application specific integrated circuit). The CPU 201 may also be an FPGA (Field Programmable Gate Array), etc. The CPU 201 may consist of one processor or multiple processors.

[0040] ROM202 stores the startup program and OS (Operating System) of user terminal 2. RAM203 temporarily stores programs or data when the CPU201 executes various processes. RAM203 is used as work memory.

[0041] The storage unit 204 is memory for storing application programs and various data. Examples of storage units 204 include HDDs (Hard Disk Drives), SSDs (Solid State Drives), flash memory, and storage devices.

[0042] The operation unit 205 is a user interface that receives operations from the user, inputs the received operation information to the CPU 201, and outputs the output information from the CPU 201 in a way that the user can recognize. In this embodiment, the operation unit 205 is assumed to be a touch panel display in which the display unit 206 and the input unit 207 are integrally configured. The display unit 206 includes a display and a display control circuit, and displays various screens on the display based on the output information input from the CPU 201. The screens that are displayed will be described later. The input unit 207 includes input devices such as various buttons and a touch panel, and transmits information input by the user via the input devices to the CPU 201. Note that the operation unit 205 does not necessarily have to have the display unit 206 and the input unit 207 integrally configured; they may be configured separately. Also, the operation unit 205 may be provided separately from the main body of the user terminal 2 and connected wirelessly or by wire.

[0043] Communication I / F208 includes an interface for communication connection with network 4, including LAN (Local Area Network), WAN (Wide Area Network), the Internet, and mobile communication networks, as well as interfaces for short-range wireless communication such as Bluetooth® and NFC (Near Field Communication). Communication I / F208 can be wired or wireless. User terminal 2 receives data etc. from other devices via communication I / F208 and transmits data etc. generated or stored by user terminal 2 to other devices via communication I / F208.

[0044] Camera 209 has an optical system including a lens and an image sensor such as a CCD (Charge Coupled Device) or CMOS (Complementary Metal Oxide Semiconductor) sensor, and outputs the captured image data to CPU 201. The code reading function of the payment application 200 is implemented using camera 209.

[0045] The audio processing unit 210 includes a microphone and a speaker. The microphone acquires the voice of users, store staff, etc., and outputs it as audio data to the CPU 201. The speaker outputs the audio data input from the CPU 201 so that users can listen to it.

[0046] The vibration detection unit 212 is composed of a gyro sensor and the like. The gyro sensor measures the rotational angular velocity when the user terminal 2 is tilted, and includes vibration-type gyro sensors and capacitive-type gyro sensors. When the vibration detection unit 212 detects vibration in the user terminal 2, it outputs the detection signal to the CPU 201.

[0047] Note that the user terminal 2 is not limited to the configuration shown in Figure 5. For example, a positioning unit for implementing GPS functionality may be provided. The user terminal 2 may also be equipped with a media I / F (not shown). The media I / F is an interface for connecting a media drive device that reads and writes data and programs stored on a data storage medium (hereinafter referred to as "media") connected by wire or wireless. The media I / F reads programs and data stored on the media, temporarily stores them in RAM 203, and inputs them to CPU 201. CPU 201 can load the input program into the work memory of RAM 203 and execute processing. The media includes, for example, optical recording media such as DVD (Digital Versatile Disc) and PD (Phase change rewritable Disk), magneto-optical recording media such as MO (Magneto-Optical disk), tape media, magnetic recording media, or semiconductor memory.

[0048] The CPU 201 of the user terminal 2 implements various functions by reading programs stored in the memory unit 204, ROM 202, and media into the RAM 203 and executing them. Programs may also be obtained from other devices, such as a server, via the network 4. Furthermore, it goes without saying that the user terminal 2 is equipped with the necessary configurations to realize the information processing in this embodiment.

[0049] (Overview of payment application features) Next, the functions and data of the payment application 200 according to this embodiment will be described with reference to Figure 6. In this embodiment, the display control function on the user terminal 2 will be described in particular.

[0050] Figure 6(a) is a diagram showing the data stored in the storage unit 204 of the user terminal 2. As shown in Figure 6(a), the storage unit 204 of the user terminal 2 stores the program of the payment application 200, as well as data for various screens displayed in the payment application (hereinafter referred to as screen data 230), and user identification information 220 for the electronic payment service. The identification information 220 is assigned by the electronic payment server 5 when the account is registered. The screen data 230 includes screen data for the top screen 100, payment screen 110, and scan screen 120 mentioned above, as well as screen data for mini-applications, screen data for the amount input screen and payment completion screen displayed during payment processing, and screen data for various error notification screens.

[0051] The payment application 200 is an application program installed and used by the user terminal 2 of a user of an electronic payment service, and is operated and managed by the service provider that provides the electronic payment service. While the payment application 200 is typically installed on the user terminal 2 by downloading it from a website, it may also be installed on the user terminal 2 by reading it from media. Alternatively, the payment application 200 may be provided as a web application that runs on the web browser of the user terminal 2.

[0052] The payment application 200 has various functions in addition to payment processing functions for making electronic payments in the electronic payment service. For example, it includes a money transfer function, a points function, a transaction history display function, a top-up function, a coupon function, a utility bill payment function, a stamp card function, a shopping function, a finance function, an information content distribution function, a user account information management function, and other functions. In the following description, functions other than the payment processing function in the payment application 200 are collectively referred to as mini-applications. The payment application 200 also has a reception function that accepts operations from the user on the user terminal 2, a display control function that controls the display on the screen, and so on.

[0053] Figure 6(b) shows the configuration of the program modules of the payment application 200. As shown in Figure 6(b), the payment application 200 of this embodiment has a payment processing unit 601, a reception unit 602, and a display control unit 603 as program modules. Although not shown, the payment application 200 also has various program modules and data related to the mini-application.

[0054] The payment processing unit 601 performs payment processing using an identification code with the store terminal 3 or the electronic payment server 5. The payment processing unit 601 sends and receives payment-related information between the user terminal 2 and the store terminal 3 or the electronic payment server 5 according to the processing procedures for store scan and user scan described above, and starts and completes the electronic payment.

[0055] The reception unit 602 receives operations from the user via the operation unit 205 of the user terminal 2. When the operation unit 205 of the user terminal 2 is configured as a touch panel display, the operations on the touch panel display can take the following forms: a tap operation where the target of the operation is touched with one finger, a swipe operation where the finger is slid across the screen while touching it, a long press operation where the finger is held in contact with the screen for a predetermined time or longer, a pinch-out operation where the distance between two fingers touching the screen is moved from a narrowed state to a widened state, a pinch-in operation where the distance between two fingers touching the screen is moved from a widened state to a narrowed state, etc. The screen is scrolled by a swipe operation in the scroll direction. Operations on the user terminal 2 are not limited to these. The reception unit 602 may accept a variety of operations, such as repeating a tap operation multiple times, a double tap operation, a triple tap operation, or a swipe operation with multiple fingers. Furthermore, if the operation unit 205 is not a touch panel display but consists of input devices such as a keyboard or mouse, the reception unit 602 accepts input for specific operations and other operations described later using the operation method corresponding to each input device.

[0056] In this embodiment, the reception unit 602 accepts two types of operations for the payment button 109. In this embodiment, the first operation is a tap operation, and the second operation is a long press operation. Note that the first and second operations are not limited to tap operations and long press operations, but may be other operations.

[0057] The display control unit 603 displays various screens corresponding to the various functions of the payment application 200 on the display unit 206 of the user terminal 2. The display control unit 603 acquires screen data 230 for the various screens from the storage unit 204 in response to user operations and displays them on the display unit 206. At that time, identification information 220 and balance information acquired from the electronic payment server 5 may also be reflected on the screen. For example, when the user double-tap the startup icon for the payment application 200 displayed on the home screen of the user terminal 2, the payment application 200 starts. As soon as the payment application 200 starts, the display control unit 603 displays the top screen 100 shown in Figure 1(a).

[0058] In this embodiment, the display control unit 603 transitions to different payment screens corresponding to each of the two types of operations performed on the payment button 109. Specifically, when the reception unit 602 receives a first operation on the payment button 109, the display control unit 603 transitions to the payment screen 110, which is the first payment screen used for electronic payment. Furthermore, when the reception unit 602 receives a second operation on the payment button 109, the display control unit 603 transitions to the scan screen 120, which is the second payment screen used for electronic payment.

[0059] (Display control processing) The flow of the display control process in the first embodiment will be explained with reference to Figures 7 and 8. The process shown in the flowchart of Figure 7 is written in the program of the payment application 200 installed on the user terminal 2. The program is stored in the memory unit 204, called by the CPU 201, loaded into RAM 203, and executed. When the user operates the startup icon of the payment application 200 and the payment application 200 is started, the CPU 201 starts this process. In the following explanation, the symbol "S" means step. Figure 8 is a diagram showing a specific example of screen transitions in the first embodiment.

[0060] In S701, the CPU 201 first obtains the screen data of the top screen 100 of the payment application 200 from the storage unit 204 and displays it on the display unit 206.

[0061] Figure 8(a) is a diagram illustrating the top screen 100. The top screen 100 includes a code display area 104, a menu area 805, a function selection area 806, a balance display area 807, a fixed display area 808, etc. Inside the code display area 104, the first identification code 101 and the second identification code 102 are displayed as user codes. Payment method and balance information may also be displayed inside the code display area 104. Campaign information 810 and notification icons 811 are displayed in the upper area of ​​the code display area 104. Operation buttons such as the credit payment button 812, which are operated when transitioning to the credit payment screen, may also be displayed in the right-hand area of ​​the code display area 104.

[0062] The fixed display area 808 displays the payment button 109, as well as a button 813 used to display information provided by the electronic payment service provider, and a wallet button 814 used to display balance information, point information, and credit information. The fixed display area 808 also displays the account button 815 used to display account information and the My Code used for transfers, and the home button 816 used to access the top screen 100 from other screens. The fixed display area 808 is not linked to screen scrolling and is always displayed in a fixed position on the display unit 206 of the user terminal 2. Therefore, the placement of the payment button 109 is also not linked to screen scrolling and is always displayed in a fixed position on the display unit 206 of the user terminal 2. In the example in Figure 8, the fixed display area 808 is displayed at the bottom of the display range of the display unit 206. In this specification, up, down, left, and right in the screen description refer to the up, down, left, and right within the screen plane, corresponding to the up, down, left, and right in the figure. The display range refers to the entire display area of ​​the display unit 206, i.e., the range corresponding to the display size.

[0063] Figure 8(b) shows state 100B after scrolling the top screen 100. In state 100B, the function selection area 806 and the balance display area 807 are displayed above the display range of the display unit 206. Also, area 821, which was outside the display range in the top screen 100 in Figure 8(a), is displayed within the display range in state 100B. Various information content such as coupon information and store information is displayed in area 821. The arrangement of the fixed display area 808 is maintained in state 100B after scrolling, the same as before scrolling (Figure 8(a)). The arrangement of the payment button 109 is also maintained before and after scrolling. The scan button 108 is moved outside the display range and is not displayed in state 100B after scrolling.

[0064] If an operation on the payment button 109 is detected in S702 and the CPU 201 acquires the detection signal (S702; YES), the process proceeds to S703.

[0065] In S703, CPU201 determines the type of operation detected in S702. If the operation detected in S702 is a tap operation (S703; YES), proceed to S704. Otherwise (S703; NO), proceed to S706.

[0066] In S704, the CPU 201 transitions the screen to be displayed on the display unit 206 to the payment screen 110. That is, the CPU 201 obtains the screen data for the payment screen 110 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 8(c). Subsequently, in S705, the CPU 201 proceeds to the first settlement process. The first settlement process is the settlement process performed by the store scan (first settlement method) described above. In the first settlement process, the CPU 201 reads the user code using the code reader 31 of the store terminal 3 and performs the settlement process. The CPU 201 (settlement processing unit 601) sends and receives information with the store terminal 3 according to the procedure of the store scan settlement process described above, and displays the settlement completion screen (not shown) etc. in accordance with the settlement completion notification sent from the electronic settlement server 5.

[0067] In S706, CPU201 determines whether the operation detected in S702 is a long press operation. If it is a long press operation (S706; YES), proceed to S707.

[0068] In S707, the CPU 201 transitions the screen to be displayed on the display unit 206 to the scan screen 120. That is, the CPU 201 acquires the screen data of the scan screen 120 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 8(d). Subsequently, in S708, the CPU 201 proceeds to the second settlement process. The second settlement process is the settlement process performed by the user scan (second settlement method) described above. That is, with the scan screen 120 displayed, the CPU 201 activates the camera 209 and makes it possible to read the store code posted in the store. When the store code is read by the scan screen 120 and the settlement process is started, the CPU 201 sends and receives information with the electronic settlement server 5 according to the procedure of the user scan settlement process described above, and displays the amount input screen and the settlement completion screen, etc.

[0069] If no operation is entered in S702 or S706 after a predetermined time has elapsed, this flowchart will be terminated.

[0070] As described above, the payment application 200 of the first embodiment accepts two types of operations for the payment button 109. When the user taps the payment button 109, the payment screen 110 is displayed on the display unit 206, and when the user long-presses the payment button 109, the scan screen 120 is displayed on the display unit 206. Therefore, it is possible to transition to two different payment screens from the same operation button. Since the payment button 109 is always displayed in a fixed position on the top screen 100, the user does not get confused when operating, and usability is improved. In addition, even when the scan button 108 has moved outside the display range due to screen scrolling, the payment button 109 can still be accessed, further improving usability. Conventionally, if the user wanted to transition to the scan screen 120 from a state where the scan button 108 had moved outside the display range due to scrolling the top screen 100, the user had to scroll back to a position where the scan button 108 was displayed before operating the scan button 108. According to this disclosure, it is possible to transition from the payment button 109, which is not linked to scrolling, to the scan screen 120.

[0071] <Second Embodiment> Next, a second embodiment of the present disclosure will be described. In the payment application 200 of the second embodiment, when the payment button 109 is pressed and held, a selection object for selecting the next screen to be viewed will be displayed, and an example of accepting the user's selection of the next screen to be viewed will be described. The selection object will be described later. Note that the configuration of the payment application 200, the user terminal 2, the store terminal 3, and the electronic payment server 5 in the second embodiment are the same as in the first embodiment, so redundant explanations will be omitted, and the same parts will be denoted by the same reference numerals.

[0072] Figures 9A to 9E illustrate screen transitions by the payment application 200 of the second embodiment. In the second embodiment, the reception unit 602 accepts a long press operation on the payment button 109 displayed on the top screen 100. When a long press operation is performed on the payment button 109, the display control unit 603 displays a selection of candidate screens to transition to. For example, as shown in Figure 9A, a first selection object 130 and a second selection object 140 are displayed near the payment button 109 on the top screen 900A as candidate screens to transition to. The first selection object 130 and the second selection object 140 each display information corresponding to the destination screen.

[0073] In the example in Figure 9A, the first selection object 130 displays "Show Code" as information corresponding to the destination screen. In other words, the first selection object 130 indicates that the destination screen is the payment screen 110, which displays the user code. The second selection object 140 displays "Scan and Pay" as information indicating the destination screen. In other words, the second selection object 140 indicates that the destination screen is the scan screen 120. Note that in the example in Figure 9A, the payment method associated with the destination screen is displayed as information indicating the destination screen, such as "Show Code" and "Scan and Pay". In other words, "Show Code" represents store scan (first payment method), where the user code is displayed on the user terminal 2 and read by the store terminal 3, and "Scan and Pay" represents user scan (second payment method), where the store code is read by the user terminal 2.

[0074] When either the first selection object 130 or the second selection object 140 is operated by the user, the display control unit 603 displays the screen corresponding to the selected object on the display unit 206. If the first selection object 130 is operated, the display control unit 603 transitions to the payment screen 110 shown in Figure 4(a). If the second selection object 140 is operated, the display control unit 603 transitions to the scan screen 120 shown in Figure 4(b). Upon transitioning to each screen, the payment application 200 transitions to a state where the corresponding payment process can be executed.

[0075] In the example in Figure 9A, the selected object is shown as a callout around the payment button 109, but is not limited to this example. For example, as shown in screen 900B in Figure 9B and 900C in Figure 9C, the selected object may be displayed as a pop-up in the form of buttons, such as the first button 901, the second button 902, and the third button 903.

[0076] In the examples in Figures 9B and 9C, the first button 901 displays "Show Code" as information indicating the destination screen. In other words, it indicates that the payment screen 110, where the user code is displayed, is the destination screen for the first button 901. The second button 902 displays "Scan and Pay" as information indicating the destination screen. In other words, it indicates that the scan screen 120 is the destination screen for the second button 902. The third button 903 displays "My Code" as information indicating the destination screen. In other words, it indicates that the My Code screen is the destination screen for the third button 903. The My Code screen is the screen used in the user-to-user money transfer function.

[0077] Furthermore, as shown in the screen 900D in Figure 9D, when the first button 901a, second button 902a, and third button 903a are displayed by a long press operation, the colors of the first button 901a, second button 902a, and third button 903a may be changed to a different color from the background screen 900D. In addition, text indicating the destination, such as "Show Code," "Scan," and "My Code," and images corresponding to the text (illustrations showing a code, illustrations showing a scan screen, illustrations showing My Code, etc.) may be displayed within each button. Also, as will be described in detail later, while the first button 901a, second button 902a, and third button 903a are displayed, the color of the payment button 109 may be changed, or it may be changed to a different mark ("×" mark 909).

[0078] Furthermore, as shown in screen 900E in Figure 9E, the first button 901b, the second button 902b, and the third button 903b may be displayed at a closer distance from the payment button 109 ("×" mark 909). In the example in Figure 9E, the first button 901b, the second button 902b, and the third button 903b are displayed in an arc around the payment button ("×" mark 909). It is also preferable that the display positions of the first button 901b, the second button 902b, and the third button 903b be within reach of the user's thumb from the payment button ("×" mark 909). The first button 901b, the second button 902b, and the third button 903b may also be displayed side by side.

[0079] Figure 10 shows an example of the My Code screen 1000. As shown in Figure 10, the My Code screen 1000 is used when receiving a remittance from another user. The My Code screen 1000 displays a My Code 1001, which is a two-dimensional code containing identification information that identifies the user of the user terminal 2 receiving the remittance.

[0080] Here, we will explain the user-to-user money transfer function. The user terminal 2 of the sending user reads the My Code of the receiving user, accepts input of the transfer amount from the sending user, and sends information including the recipient user's identification information indicated by the read My Code, the transfer amount, and the identification information that identifies the sending user to the electronic payment server 5. The electronic payment server 5 transfers the amount of electronic money indicated by the transfer amount from the sending user's account to the receiving user's account, and notifies the sending user terminal 2 or the terminal device used by the receiving user that the transfer has been completed.

[0081] The My Code screen 1000 also displays the My Code expiration date 1002, account name, link button 1004, and copy button 1005. The link button 1004 and copy button 1005 are buttons that generate link information for receiving the remittance amount. When the link button 1004 is operated, the CPU 201 of the user terminal 2 receives input of the remittance amount from the user, generates link information for receiving the remittance amount, and posts the information including the link information to the SNS (Social Networking Service). When the copy button 1005 is operated, the CPU 201 of the user terminal 2 receives input of the remittance amount from the user, generates link information for receiving the remittance amount, and copies (temporarily stores) the generated link information. The copied link information can be sent using email or messaging apps. This provides the link information to the terminal device of other users (the users who are sending the money). When another user (the user who is sending the money) performs a remittance operation using the link information, the electronic payment server 5 sends a notification to the recipient user indicating that the remittance has been made. When the recipient user performs a receiving operation, the electronic payment server 5 transfers the amount of electronic money indicated by the transfer amount from the sender user's account to the recipient user's account.

[0082] Conventionally, the following methods were used to display the My Code screen 1000 on the display unit 206: (1) Transition to the user's account screen (not shown) by operating the account button 815 displayed in the fixed display area 808 of the top screen 100, and then operating the My Code button displayed on the account screen. (2) Operation of the billing button on the screen accessed from the remittance function button in the menu area 805. In other words, it was not possible to display the My Code screen 1000 directly from the top screen 100 using either of these transition methods. On the other hand, in the second embodiment, by operating the third button 903 that pops up when the payment button 109 on the top screen 100 is long-pressed, it becomes possible to transition directly from the top screen 100 to the My Code screen 1000.

[0083] (Display control processing) Next, the display control process in the second embodiment will be described with reference to Figures 11 and 12. Figures 11 and 12 are flowcharts showing the flow of the display control process in the third embodiment. The processes shown in the flowcharts of Figures 11 and 12 are written in the program of the payment application 200 installed on the user terminal 2. The program is stored in the storage unit 204, called by the CPU 201, loaded into RAM 203, and executed. When the user operates the startup icon of the payment application 200 and the payment application 200 is started, the CPU 201 starts the processes shown in the flowchart. Note that the processes S1101 to S1105 are the same as S701 to S705 in Figure 7. The following description will focus on the processes that differ from the first embodiment.

[0084] In S1101, the CPU 201 first obtains screen data for the top screen 100 of the payment application 200 from the storage unit 204 and displays it on the display unit 206. The top screen 100 is the same as in the first embodiment, so its description is omitted.

[0085] If an operation on the payment button 109 is detected in S1102 and the CPU 201 acquires the detection signal (S1102; YES), the process proceeds to S1103.

[0086] In S1103, CPU201 determines the type of operation detected in S1102. If the operation detected in S1102 is a tap operation (S1103; YES), proceed to S1104. Otherwise (S1103; NO), proceed to S1106.

[0087] In S1104, the CPU 201 transitions the screen to be displayed on the display unit 206 to the payment screen 110. Then, in S1105, the process proceeds to the first settlement process. The first settlement process is the settlement process using the store scan method described above.

[0088] In S1106, CPU201 determines whether the operation detected in S1102 is a long press operation. If it is a long press operation (S1106; YES), proceed to S1107.

[0089] In S1107, CPU201 displays a selection object in a pop-up window for the user to select the next screen to proceed to. As described above, the selection object may be a first selection object 130 and a second selection object 140 displayed in the form of a speech bubble, or it may be displayed in the form of a button. The number of selection objects may be two, three, or four or more, as shown in the diagram.

[0090] The CPU 201 preferably displays the selected object near the payment button 109. Specifically, it is preferable that all selected objects are displayed within the user's field of vision without the user having to move their gaze away from the payment button 109 they are focusing on. As shown in Figure 9A, if the payment button 109 is displayed at the bottom of the screen, it is preferable to display the selected objects lined up directly above the payment button 109. In the example in Figure 9A, the payment button 109, the first selected object 130, and the second selected object 140 are arranged within a range of about one-third of the screen 100A. In the examples in Figures 9B and 9C, the payment button 109, the first button 901, the second button 902, and the third button 903 are arranged within a range of about half of the screens 900B and 900C. Also, in the examples in Figures 9B and 9C, an example is shown in which the third button 903 (My Code), the second button 902 (Scan and Pay), and the first button 901 (Code Display) are displayed in order from closest to the payment button 109. The order of placement can be reversed, or any order is acceptable. Furthermore, the display order of the selected objects may be determined based on the frequency of use of the corresponding destination screen for each button. In that case, frequently used objects may be displayed closer to the payment button 109.

[0091] The CPU 201 may adjust the screen brightness and display color when displaying the selected object. Specifically, the CPU 201 adjusts the screen brightness and display color so that the selected object is displayed brighter than its background. In the examples of Figures 9B and 9C, the first button 901, the second button 902, the third button 903, and the fixed display area 808 are displayed brightly, while the area behind the first button 901, the second button 902, and the third button 903 is displayed darker than the first button 901, the second button 902, and the third button 903. Also, as shown in Figure 9D, the colors of the first button 901a, the second button 902a, and the third button 903a may be displayed in a different color from the background screen 900D, or the color and shape of the payment button 109 may be changed, or the mark 909 may be displayed while these buttons 901a to 903a are displayed.

[0092] In the example shown in Figure 9E, the payment button 109 ("×" mark 909), the first button 901b, the second button 902b, and the third button 903b are all positioned within approximately one-quarter or less of the screen 900E. By displaying the first button 901b, the second button 902b, and the third button 903b in a position closer to the payment button 109 ("×" mark 909), all of these buttons can be operated with the movement of the thumb, making it possible to complete the payment with one hand. In addition, in the example shown in Figure 9E, the first button 901b, the second button 902b, and the third button 903b are displayed in a different color from the background screen 900E, but as shown in Figures 9B and 9C, it is also possible to reduce the brightness of the background screen 900E and increase the brightness of the buttons. After displaying the selected object, proceed to S1201 in Figure 12. In this embodiment, the display of the selected object will be maintained even after releasing the finger from the payment button 109 after pressing and holding it.

[0093] In S1201, the CPU 201 determines whether the first button 901 or the first selection object 130, which indicates "code display," has been selected by the user. The selection operation is, for example, a tap operation. If the first button 901 or the first selection object 130 has been selected (S1201; YES), the process proceeds to S1202, and the CPU 201 displays the payment screen 110 on the display unit 206. After that, the process proceeds to the first payment process in S1203. The first payment process is the payment process using the store scan method described above. If the first button 901 or the first selection object 130 has not been selected by the user (S1201; NO), the process proceeds to S1204.

[0094] In S1204, the CPU 201 determines whether the second button 902 or the second selection object 140, which indicates "Scan and Pay," has been selected by the user. The selection operation is, for example, a tap operation. If the second button 902 or the second selection object 140 has been selected (S1204; YES), the process proceeds to S1205, and the CPU 201 displays the scan screen 120 on the display unit 206. After that, the process proceeds to the second payment process in S1206. The second payment process is the payment process using the user scan method described above. If the second button 902 or the second selection object 140 has not been selected by the user (S1204; NO), the process proceeds to S1207.

[0095] In S1207, the CPU 201 determines whether the third button 903, which indicates "My Code," has been selected by the user. The selection operation may be, for example, a tap. If the third button 903 is selected (S1207; YES), the process proceeds to S1208, where the CPU 201 displays the My Code screen 1000 on the display unit 206. Subsequently, in S1209, the process proceeds to My Code processing, such as receiving a balance using the My Code. If the third button 903 has not been selected by the user (S1207; NO), the process proceeds to S1210.

[0096] In S1210, CPU201 determines whether a predetermined time has elapsed since the selected object was displayed in a pop-up window in S1107. If the predetermined time has not elapsed (S1210; NO), it returns to S1201 and waits for a selection operation on any of the selected objects. If the predetermined time has elapsed since the selected object was displayed in a pop-up window (S1210; YES), in S1211, CPU201 cancels the pop-up display of the selected object and returns to S1101. In S1101, the top screen 100 is displayed.

[0097] If no operation is performed on the payment button 109 after a predetermined time has elapsed in S1102, or if an invalid operation is performed on the payment button 109, this flowchart will terminate.

[0098] <Variation> In the flowchart example described above, even after long-pressing the payment button 109 and releasing the finger from the payment button 109, the display of the selected objects (buttons 901-903) is maintained. Furthermore, when any of the selected objects are tapped, the corresponding screen is accessed. As a modification of the second embodiment, the following operation example and behavior will be explained with reference to Figure 9E.

[0099] When the payment button 109 is pressed and held, the first button 901b, the second button 902b, and the third button 903b are displayed around the payment button 109 as selected objects, as shown in Figure 9E. The process up to this point is the same as S1101 to S1107 in Figure 11. In the modified example, when the first button 901b, the second button 902b, and the third button 903b are displayed due to the payment button 109 being pressed and held, and the finger is released from the payment button 109 (press and hold released), the CPU 201 clears the display of the first button 901b, the second button 902b, and the third button 903b. Also, while the payment button 109 is being pressed and held, that is, while the first button 901b, the second button 902b, and the third button 903b are displayed, the CPU 201 changes the payment button 109 to an "X" mark 909. The "×" mark 909 indicates that a long press is being performed and is displayed in a different color than the payment button 109. When the finger is released from the "×" mark 909 (long press released), the CPU 201 returns the display of the "×" mark 909 to the original payment button 109. Note that the mark indicating a long press is not limited to the "×" mark 909; other symbols or letters may also be used.

[0100] Furthermore, when the payment button 109 is pressed and held, and the first button 901b, second button 902b, and third button 903b are displayed, if the finger is slid to any of the first button 901b, second button 902b, or third button 903b while the button is still pressed and held, the CPU 201 changes the color of the button the finger is slid to. After that, when the finger is released from the button the finger is slid to, the CPU 201 transitions the display screen to the screen corresponding to the button the finger was slid to. That is, if the button the finger is slid to is the first button 901b, the CPU 201 displays the payment screen 110 on the display unit 206. Then the process proceeds to the first payment process. If the button the finger is slid to is the second button 902b, the CPU 201 displays the scan screen 120 on the display unit 206. Then the process proceeds to the second payment process. If the button the finger is slid to is the third button 903b, the CPU 201 displays the My Code screen 1000 on the display unit 206. After that, the process proceeds to My Code processing, such as receiving a balance using My Code. In other words, the user long-presses the payment button 109, then slides their finger across the screen to one of the following positions: the first button 901b, the second button 902b, or the third button 903b, and then releases their finger. The color of the button the finger has moved to changes to indicate that it is selected. When the finger is released, the screen corresponding to the button the finger has moved to is displayed.

[0101] The operations described above as modified examples are applicable not only to cases where selected objects are arranged in an arc shape or horizontally, as shown in Figure 9E, but also to the cases shown in Figures 9A to 9D.

[0102] As described above, the payment application 200 of the second embodiment accepts two types of operations for the payment button 109. When the user taps the payment button 109, the payment screen 110 is displayed on the display unit 206. When the user long-presses the payment button 109, a selection object indicating candidate destinations for the screen transition is displayed on the display unit 206. Therefore, the user can select a destination and transition to the desired screen. Since the payment button 109 is always displayed in a fixed position on the top screen 100, the user does not get confused during operation, improving usability. Furthermore, even when the scan button 108 has moved outside the display range due to scrolling, the payment button 109 can still be accessed, improving usability. In other words, conventionally, if the user wanted to transition to the scan screen 120 from a state where the scan button 108 had moved outside the display range due to scrolling, the user had to scroll again to a position where the scan button 108 was displayed before operating the scan button 108. According to this disclosure, it is possible to transition from the payment button 109, which is not linked to scrolling, to the scan screen 120. Furthermore, regarding receiving balances using My Code, even users who are unfamiliar with how to display My Code or the function itself will be able to easily display their My Code, improving usability.

[0103] In the examples in Figures 9A to 9E, the payment screen 110, the scan screen 120, and the My Code screen 1000 are shown as examples of candidate destination screens, but the system is not limited to these. For example, as another example of the user-to-user money transfer function of the payment app 200, a money transfer screen using the recipient user's phone number or information identifying the recipient user (e.g., user ID) may be displayed as a candidate destination screen. In this case, the user terminal 2 transitions to a recipient input screen that accepts input of the recipient user's phone number or user ID and the transfer amount. The recipient input screen accepts the recipient user's phone number or user ID and the transfer amount. The CPU 201 sends the recipient user's phone number or user ID entered on the recipient input screen, the transfer amount, and user identification information identifying the sender to the electronic payment server 5. The electronic payment server 5 then transfers the amount of electronic money indicated by the transfer amount from the sender's account to the recipient's account linked to the transmitted phone number or user ID. Here, the recipient's phone number or user ID may be pre-registered in the payment app 200 in conjunction with information about that user. In this case, the user terminal 2 receives from the sender's user the specification of the recipient registered in the payment app 200 and the input of the transfer amount to that recipient, and transmits the phone number or user ID linked to the specified recipient, the transfer amount, and user identification information that identifies the sender to the electronic payment server 5.

[0104] Furthermore, the user may be able to set the options for the destination screen that will pop up when the payment button 109 is pressed and held. In this case, the payment app 200 will display a settings screen on the display unit 206 of the user terminal 2 for the user to set the options for the destination screen, and will accept the settings from the user.

[0105] Furthermore, the candidates for the destination screen may include not only screens used for payment, but also screens for mini-apps (functions included in payment app 200). For example, in addition to the user-to-user money transfer function mentioned above, screens used for point functions and coupon functions may also be included as candidates for the destination screen.

[0106] Furthermore, although the above embodiment shows an example in which the destination candidate (selected object) is displayed in the upper area of ​​the payment button 109, the invention is not limited to this, and the destination candidate may also be displayed in the right or left area of ​​the payment button 109, and the display format of the destination candidate is arbitrary.

[0107] Preferred embodiments of this disclosure have been described above with reference to the attached drawings, but this disclosure is not limited to such examples. For example, the content of buttons and information displayed on the screen, the screen layout, and the processing procedures shown in the flowchart are examples and can be modified as appropriate without departing from the technical idea of ​​this disclosure. Furthermore, it is clear that those skilled in the art can conceive of various modifications or alterations within the scope of the disclosed technical idea, and these will naturally also fall within the technical scope of this disclosure. [Explanation of symbols]

[0108] 1. Electronic payment system 2. User terminals 100 Top screen 110 Payment screen 120 scan screen 1000 My Code Screen 601 Payment Processing Unit Room 602 Reception Desk 603 Display Control Unit

Claims

1. A payment application program that is pre-installed on a terminal device used by a user of electronic payment in order to use electronic payment using an identification code, wherein the terminal device A reception unit that receives operations from the user on the terminal device, The aforementioned reception unit functions as a display control unit that controls the display on the display unit of the terminal device based on the operation received by the reception unit, The display control unit, When the reception unit receives a first operation for the first operation button displayed on the display unit, it transitions to the first payment screen used for the electronic payment. When the receiving unit receives a second operation different from the first operation for the first operation button, it pops up an object showing a candidate screen to transition to, allowing the user to select it. The aforementioned candidates include a function screen displayed in a function included in the payment application program, and buttons for transitioning to the function screen are not displayed on the top screen of the payment application program, except for the aforementioned object. A payment application program characterized by the following features.

2. The payment application program according to claim 1, characterized in that the candidate includes at least one of the first payment screen and a second payment screen used for the electronic payment, which is different from the first payment screen.

3. The first payment screen is a screen that includes a user code in which the user's identification information is coded, The payment application program according to claim 2, characterized in that the second payment screen is a screen for reading a store code in which store identification information is encoded.

4. The payment application program according to claim 1, characterized in that the aforementioned function screen is a screen used for the money transfer function between users.

5. The payment application program according to claim 1, characterized in that the display control unit makes the display form of the first operation button when the object is displayed different from the display form of the first operation button when the object is not displayed.

6. The payment application program according to claim 1, characterized in that the display control unit displays the frequently used object on the destination screen corresponding to the object closer to the first operation button than the less frequently used object.

7. The second operation is a long press operation, When the object is displayed by pressing and holding the first operation button, and the finger that performed the press and hold is slid to one of the objects, the display control unit changes the display form of the object to which the finger was slid. The payment application program according to claim 1, characterized in that when the finger that performed the long-press operation is released from the object to which it was slid, the display control unit transitions to the screen corresponding to the object to which it was slid.

8. The payment application program according to any one of claims 1 to 7, characterized in that the arrangement of the first operation buttons is controlled by the display control unit so as to be maintained before and after the reception unit accepts a scroll operation of the screen displayed on the display unit.

9. The payment application program according to claim 8, characterized in that the first operation button is displayed on the top screen that is displayed immediately after the startup of the payment application program.

10. The payment application program according to claim 9, characterized in that the top screen includes a user code that has been reduced in size compared to the user code included in the first payment screen.

11. The payment application program according to claim 10, further characterized in that the top screen displays a second operation button for transitioning to a second payment screen for reading a store code, which contains the store's identification information.

12. The payment application program according to claim 11, characterized in that the second operation button may move out of the display range of the display unit when the reception unit receives a scroll operation.

13. The first payment screen includes an operation button to transition to the second payment screen. The payment application program according to any one of claims 2 to 7, characterized in that the second payment screen includes an operation button for transitioning to the first payment screen.

14. The first operation is a tap operation, The payment application program according to claim 8, characterized in that the second operation is a long press operation.

15. The payment application program according to claim 8, characterized in that the display control unit maintains the display of the candidate when the second operation on the first operation button is released.

16. The payment application program according to claim 8, characterized in that the display control unit cancels the display of the candidate when the second operation on the first operation button is released.

17. The payment application program according to claim 8, characterized in that if any of the above candidates is selected, the display control unit transitions to a screen corresponding to the selected candidate.

18. An information processing device used by a user of electronic payment to utilize electronic payment using an identification code, A reception unit that receives operations from the user on the information processing device, The system includes a display control unit that controls the display on the display unit of the information processing device based on the operation received by the reception unit, The display control unit, When the reception unit receives a first operation for the first operation button displayed on the display unit, it transitions to the first payment screen used for the electronic payment. When the receiving unit receives a second operation different from the first operation for the first operation button, it pops up an object showing a candidate screen to transition to, allowing the user to select it. The aforementioned candidates include a function screen displayed in a function included in a payment application program pre-installed on the information processing device, and buttons for transitioning to the aforementioned function screen are not displayed on the top screen of the payment application program, except for the aforementioned object. An information processing device characterized by the following:

19. An information processing method performed by a computer in a terminal device used by a user of electronic payment in order to use electronic payment using an identification code, When the terminal device receives a first operation from the user for a first operation button displayed on the terminal device's display unit, the terminal device transitions to a first payment screen used for electronic payment. The system includes the step of, when the user performs a second operation on the first operation button that is different from the first operation, displaying a pop-up object showing a candidate screen to transition to, which can be selected. The aforementioned candidates include a function screen displayed in a function included in a payment application program pre-installed on the terminal device, and buttons for transitioning to the function screen are not displayed on the top screen of the payment application program, except for the aforementioned object. An information processing method characterized by the following:

Images