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

The payment application program enhances operability and visibility by dynamically adjusting the size of identification codes in response to user gestures, addressing existing challenges in payment application technologies.

JP7681781B1Active Publication Date: 2025-05-22PAYPAY CO LTD

Patent Information

Application Number
JP2024162486
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2024-09-19
Publication Date
2025-05-22
Estimated Expiration
2044-09-19

AI Technical Summary

Technical Problem

Existing payment application technologies face challenges in improving operability and visibility, particularly in displaying identification codes for electronic payments.

Method used

A payment application program that includes a display control unit to enlarge or reduce the display size of identification codes in response to specific user operations, such as pinch-out and pinch-in gestures, enhancing user interaction and code readability.

Benefits of technology

This solution improves the operability and visibility of the payment application by allowing users to easily read identification codes, even in challenging conditions, without the need to transition to a separate payment screen.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007681781000001_ABST
    Figure 0007681781000001_ABST
Patent Text Reader

Abstract

The aim is to improve the operability and visibility of payment apps installed on user terminals in electronic payment services. [Solution] The payment application program is a payment application that is pre-installed on a terminal device used by a user of electronic payment to utilize an identification code, and has a display control unit that displays the identification code on a display unit of the terminal device, and a reception unit that accepts operations by the user on the terminal device, and when the reception unit accepts a specific operation, the display control unit enlarges or reduces the display size of the identification code in response to the specific operation.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] Cashless payment, which is a method of making a payment for goods or services without using currency, is becoming more and more popular. In particular, electronic payment using a payment application program (hereinafter referred to as a payment app) that can be installed in a terminal device such as a smartphone, is attracting attention due to its high convenience. One of the payment methods using a payment app is a method in which an identification code (a barcode or a QR code (registered trademark)) that encodes the user's identification information is displayed on the user's terminal device and read by a store terminal. In this method, a request for payment processing is transmitted from the store terminal to an electronic payment server, and the electronic payment server performs payment processing between an electronic account linked to the identification information of the store terminal and an electronic account linked to the identification information of the user. In this payment method, the user's operation is as follows: first, the payment app is started to display the identification code on the user's terminal device, and then the user holds the identification code over a code reader of the store terminal to read it, or the user requests a store staff member to read it.

[0003] Patent Document 1 describes the display of an identification code in a payment application. Specifically, it describes that an interface screen on which the above-mentioned identification code and buttons related to various other services are displayed includes a payment button for transitioning to a payment screen. It also describes that when the payment button is operated, transition is made to a payment screen separate from the interface screen, and the identification code is displayed in an enlarged manner. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2023-127458 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, the technology described in Patent Document 1 has room for improvement in terms of improving the operability and visibility of the payment app.

[0006] The present disclosure aims to improve the operability and visibility of a payment application installed on a user's terminal device in an electronic payment service. [Means for solving the problem]

[0007] A payment application program according to one embodiment of the present disclosure is a payment application that is pre-installed on a terminal device used by a user of electronic payment to utilize an identification code, and has a display control unit that displays the identification code on a display unit of the terminal device, and a reception unit that accepts operations by the user on the terminal device, and is characterized in that when the reception unit accepts a specific operation, the display control unit enlarges or reduces the display size of the identification code in response to the specific operation. Effect of the Invention

[0008] According to the present disclosure, it is possible to improve the operability and visibility of a payment application installed on a user's terminal device in an electronic payment service. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an overview of the present disclosure. [Diagram 2] FIG. 1 is a diagram illustrating an example of a system configuration of an electronic payment system. [Diagram 3] FIG. 13 is a diagram showing an example of a screen used for electronic payment. [Figure 4] 2 is a block diagram showing an example of a hardware configuration of a user terminal; FIG. [Diagram 5]FIG. 2 is a diagram illustrating an example of a software configuration of a user terminal. [Figure 6] FIG. 13 is a diagram illustrating a transition of a display screen. [Figure 7] 5 is a flowchart showing the flow of a display control process in the first embodiment. [Figure 8] FIG. 11 is a diagram illustrating how a display size is determined. [Figure 9] FIG. 13 is a diagram illustrating a transition of a display screen. [Figure 10] 10 is a flowchart showing the flow of a display control process in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Preferred embodiments of the payment application program, information processing device, and information processing method according to the present disclosure will be described in detail below with reference to the drawings. Note that the payment application program, information processing device, and information processing method according to the present disclosure are not limited to these embodiments. Also, the same components in the following embodiments are given the same reference numerals, and duplicated descriptions will be omitted. In this specification, the payment application program is referred to as a payment app.

[0011] (Summary of the Disclosure) FIG. 1 is a diagram showing an overview of the present disclosure. A payment application according to an embodiment of the present disclosure includes a display control unit that displays one or both of a first identification code 101 and a second identification code 102 as identification codes on a display unit of a terminal device (hereinafter referred to as a user terminal) used by a user, and a reception unit that receives an operation by the user on the user terminal. When a specific operation is received from the user, the display control unit enlarges or reduces the display size of the identification code in accordance with the specific operation. Specifically, the specific operation is, for example, a pinch out operation and a pinch in operation. In the following description, the pinch out operation and the pinch in operation are collectively referred to as a pinch operation.

[0012] FIG. 1(a) is a diagram showing an example of an initial state of a top screen 100 displayed on the display unit of a user terminal immediately after the start of a payment application. FIG. 1(b) is a diagram showing an example of a top screen 100A after a pinch-out operation. As shown in FIG. 1(a), a first identification code 101 and a second identification code 102, which are encoded identification information of a user, are displayed in a code display area 104 on the initial state of the top screen 100. The identification code is at least one of the first identification code 101, which is a one-dimensional code such as a barcode, and the second identification code 102, which is a two-dimensional code such as a QR code (registered trademark). In the figure, an example in which both are displayed is shown. Information other than the identification code, such as a payment method or balance information, may be displayed in the code display area 104.

[0013] Details will be described later, but there are two payment methods using the payment app: a first method in which a store staff member reads a user identification code in which the user's identification information is coded, and a second method in which a user uses a user terminal to scan a store identification code in which the store's identification information is coded and inputs the payment amount. In the following explanation, the first method is also referred to as store scan, and the second method is also referred to as user scan. The first identification code 101 and the second identification code 102 displayed in the code display area 104 are user identification codes used in the first method.

[0014] A payment button 109, which is operated when transitioning to a payment screen, is displayed at the bottom of the top screen 100. At the bottom of the code display area 104, various buttons are displayed which are operated when transitioning to a remittance screen, a points screen, a transaction history screen, and a charge screen, in addition to a scan button 108, which is operated when transitioning to a scan screen. The scan screen is a screen used in the second method described above. In addition, various buttons are displayed which are operated when transitioning to screens for various functions of the payment app. Furthermore, when the top screen 100 is scrolled, other information such as coupon information and store information is displayed within the display range of the display unit. In this way, a lot of information is laid out on the top screen 100.

[0015] When a pinch-out operation is received on a screen on which the user's identification codes 101 and 102 are displayed, the display control unit enlarges the display size of the identification codes 101 and 102. When a pinch-in operation is received, the display control unit reduces the display size of the identification codes 101 and 102. On the top screen 100A after the pinch-out operation, the code display area 104A is enlarged and displayed as shown in FIG. 1(b). By enlarging the code display area 104A, the identification codes 101A and 102A are also enlarged and displayed. The size of the enlarged code display area 104A is controlled by the display control unit so as not to exceed the display range of the display unit. Alternatively, the size of the enlarged identification codes 101A and 102A may be controlled by the display control unit so as not to exceed the display range of the display unit. Furthermore, when a pinch-in operation is performed in an enlarged state, the code display area 104 is reduced and displayed. As a result, the identification codes 101 and 102 are also reduced and displayed. The size of the reduced code display area 104 is controlled by the display control unit so as not to be smaller than the size of the initial state code display area 104. Alternatively, the display control unit may control the size of the reduced identification code so as not to be smaller than the initial state identification codes 101, 102. Enlargement and reduction of the identification code corresponding to the specific operation is preferably performed on the top screen that is displayed immediately after the start of the payment app.

[0016] In this way, the display size of the identification codes 101 and 102 displayed on the display unit can be changed in response to a specific operation by the user, thereby improving the operability and visibility of the payment application. Specifically, even if the hand shakes or the identification code is difficult to see when reading the identification code displayed on the user terminal using a handy code reader, the identification code can be enlarged on the screen and changed to a size suitable for reading. This allows the reading operation to be performed smoothly. Also, while it is possible to enlarge and display the identification code on a separate payment screen by operating the payment button 109 as in the past, according to the present disclosure, even if the user does not notice the payment button 109, it is possible to enlarge and display the identification code displayed on the screen within the same screen. Also, even if it takes time to update the screen in an environment with unstable communication conditions, it is possible to enlarge and display the identification code without transitioning to a separate payment screen. Also, it is possible to improve the visibility of the identification code while displaying a lot of information on the screen. In addition, the size of the identification code can be changed through intuitive operations that link the finger movements and the display size, such as enlarging the code by pinching outward by spreading two fingers apart, and shrinking the code by pinching inward by narrowing the gap between two fingers, thereby improving usability.

[0017] First Embodiment (Outline of the electronic payment system) An overview of an electronic payment system that uses a payment application program (hereinafter referred to as a payment app) according to the present disclosure will be described. FIG. 2 is a diagram showing an example of a system configuration of an electronic payment system 1. As shown in FIG. 2, the electronic payment system 1 includes a user terminal 2, a store terminal 3, and an electronic payment server 5, and the store terminal 3 and the electronic payment server 5 are communicatively connected to each other via a network 4. In addition, the user terminal 2 and the electronic payment server 5 are communicatively connected to each other via the network 4.

[0018] In this specification, a user is a person who uses a payment app to make a payment for goods or services at a store. The user obtains an account for the electronic payment service provided by the electronic payment system 1, for example, by using an account management function of the payment app. 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 app 200 on the user terminal 2. The electronic payment service can also be used by accessing a website provided by the electronic payment server 5 using a general web browser.

[0019] (Store terminal) The store terminal 3 is an information processing device used by a store that has a contract with a service provider that provides an electronic payment service, or a service provider. The store terminal 3 is composed of a computer having at least 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 the optical reading function may be realized by the POS device. The optical reading function is realized by a code reader 31 such as a barcode reader that reads an image of a one-dimensional code such as a barcode, or a camera that reads an image of a two-dimensional code such as a QR code (registered trademark). In addition, a store code image 32 is posted in the store. The store code image 32 shows the store URL, which is the identification information of the store, in the form of a two-dimensional code such as a QR code. The store code image 32 may be printed on a paper or plastic medium and posted, or may be displayed on a display. Hereinafter, a store or a service provider that has a contract with a service provider that provides an electronic payment service is referred to as an affiliated store. An example of an affiliated store is an organization that operates multiple physical stores or online shops. A "store" is a place that actually provides goods or services to users, such as a shop, restaurant, department store, movie theater, or sports gym. "Goods" include tangible objects such as goods that users actually acquire at a store, and intangible objects such as image data, video data, music data, and game programs. "Services" are services that users actually receive at a store, etc.

[0020] (Electronic payment server) The electronic payment server 5 is an information processing device that provides an electronic payment service that processes electronic payments and distributes information related to electronic payments, and is composed of a computer having at least a communication function and a program execution function. The electronic payment server 5 manages the electronic accounts of stores that are affiliated with the company and the electronic accounts of users who have accounts for the electronic payment service, and realizes various payments by, for example, transferring electronic money between electronic accounts. The electronic payment server 5 may be realized by one information processing device or by multiple information processing devices.

[0021] (User terminal) The user terminal 2 is a terminal device used when a user makes an electronic payment at an affiliated store. For example, a portable terminal such as a smartphone is generally used. The payment app 200 is pre-installed in the user terminal 2 when the user uses electronic payment. The payment app 200 is operated and managed by a service provider that provides electronic payment services. The payment app 200 will be described later. Methods of making electronic payments at affiliated stores using the payment app 200 can be broadly divided into two forms: store scan (first method) and user scan (second method).

[0022] (Store Scan) In the store scan, the store terminal 3 optically reads the user's identification code displayed on the user terminal 2 using the code reader 31, and obtains the user's identification information by decoding the read identification code. The store terminal 3 transmits the obtained user's identification information to the electronic payment server 5 together with a payment request. In response to the payment request, the electronic payment server 5 generates a one-time code 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 transmits 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 and the store's electronic account from a database and performs payment processing. When the payment processing is completed, the electronic payment server 5 displays a payment completion screen on the user terminal 2. The store terminal 3 may directly transmit and receive information related to the payment to and from the electronic payment server 5, or may transmit and receive information related to the payment via the server of an intermediate payment business operator.

[0023] To read the identification code in the store scan, the identification codes 101, 102 displayed on the top screens 100, 100A shown in FIG. 1 may be used, or the identification codes 311, 312 displayed on a payment screen 310 separate from the top screen 100 may be used. FIG. 3(a) is a diagram showing an example of the payment screen 310. The payment screen 310 is displayed on the display unit of the user terminal 2 when the user taps the payment button 109 displayed on the top screens 100, 100A. To return from the payment screen 310 to the top screen 100, simply operate button 314.

[0024] (User Scan) In user scanning, the user terminal 2 reads a store code image 32 such as a QR code posted in a store. The store code image 32 includes store identification information such as the store URL. The payment app 200 of the user terminal 2 adds the user's identification information to the read store URL information and transmits it to the electronic payment server 5. The electronic payment server 5 identifies the user and store from a 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 transmits information on the input amount to the electronic payment server 5. The electronic payment server 5 performs payment processing between the electronic accounts of the identified user and store. When the payment processing is completed, a payment completion screen is displayed on the user terminal 2.

[0025] The scan screen 320 shown in FIG. 3(b) is used to read the store code image 32 in the user scan. The user operates the payment application 200 to display the scan screen 320 on the display unit of the user terminal 2, and takes a picture of the store code image 32 posted in the store so that the store code image 32 is included in a frame 321. The user can transition to the scan screen 320 by tapping the scan button 108 displayed on the top screens 100 and 100A shown in FIG. 1, or by tapping the button 313 displayed on the payment screen 310 shown in FIG. 3(a). To return from the scan screen 320 to the payment screen 310, the user taps the button 322 in the scan screen 320. To return from the scan screen 320 to the top screen 100, the user only needs to operate the button 324.

[0026] 4 is a diagram showing a hardware configuration of a user terminal 2 according to this embodiment. As an example of the user terminal 2, an example of the internal configuration of a smartphone is shown. Note that, in this embodiment, the user terminal 2 is described taking a smartphone as an example, but is not limited to this. The user terminal 2 may be, for example, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, or a PDA (Personal Digital Assistant), etc.

[0027] The user terminal 2 includes a CPU 201, a ROM 202, a RAM 203, a storage unit 204, an operation unit 205, a communication I / F 208, a camera 209, a sound processing unit 210, and a vibration detection unit 212, and each unit is connected via a bus 213. The operation unit 205 includes a display unit 206 and an input unit 207.

[0028] The CPU 201 is a central processing unit that controls each part of the user terminal 2. The CPU 201 reads the programs stored in the ROM 202 or the storage unit 204 into the RAM 203 and executes the read programs to realize various functions included in the programs. The CPU 201 may be an MPU (Micro Processing Unit) or an ASIC (application specific integrated circuit). The CPU 201 may be an FPGA (Field Programmable Gate Array) or the like. The CPU 201 may be composed of one processor or a plurality of processors.

[0029] The ROM 202 stores the startup program of the user terminal 2, the OS (Operating System), and the like. The RAM 203 temporarily stores programs or data when the CPU 201 executes various processes. The RAM 203 is used as a work memory.

[0030] The storage unit 204 is a memory for storing application programs, various data, and the like. Examples of the storage unit 204 include an HDD (Hard Disk Drive), an SDD (Solid State Drive), a flash memory, and a storage.

[0031] The operation unit 205 is a user interface for accepting an operation by a user, inputting the accepted operation information to the CPU 201, and outputting output information output from the CPU 201 so that the user can recognize it. In this embodiment, the following description will be given assuming that the operation unit 205 is a display with a touch panel 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 displayed screens will be described later. The input unit 207 includes an input device such as various buttons and a touch panel, and transmits information input by the user via the input device to the CPU 201. Note that the operation unit 205 does not necessarily need to be integrally configured with the display unit 206 and the input unit 207, and may be configured separately. Also, the operation unit 205 may be configured to be provided separately from the main body of the user terminal 2 and connected wirelessly or by wire.

[0032] The communication I / F 208 includes an interface for communication connection with a network 4 including a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, a mobile communication network, etc., and an interface for short-range wireless communication such as Bluetooth (registered trademark) and NFC (Near Field Communication). The communication I / F 208 may be wired or wireless. The user terminal 2 receives data, etc. from other devices via the communication I / F 208, and transmits data, etc. generated or stored in the user terminal 2 to other devices via the communication I / F 208.

[0033] The camera 209 has an optical system such as a lens and an imaging element such as a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) sensor, and outputs captured image data to the CPU 201. The code reading function of the payment application 200 is realized using the camera 209.

[0034] The audio processing unit 210 includes a microphone and a speaker. The microphone captures the voices of users, store staff, etc., and outputs them as audio data to the CPU 201. The speaker outputs the audio data input from the CPU 201 so that the user can hear it.

[0035] The vibration detection unit 212 is configured with a gyro sensor or the like. The gyro sensor measures the rotation angular velocity when the user terminal 2 is tilted, and includes a vibration type gyro sensor, a capacitance type gyro sensor, etc. When the vibration detection unit 212 detects the vibration of the user terminal 2, it outputs a detection signal to the CPU 201.

[0036] The user terminal 2 is not limited to the configuration shown in FIG. 4. For example, a positioning unit for implementing a GPS function may be provided. The user terminal 2 may also include 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 in a storage medium for data storage (hereinafter referred to as a medium) connected by wire or wirelessly. The media I / F reads the programs and data stored in the medium, temporarily stores them in the RAM 203, and inputs them to the CPU 201. The CPU 201 can expand the input program in the work memory of the RAM 203 and execute the process. The medium includes, for example, optical recording media such as DVDs (Digital Versatile Discs) and PDs (Phase change rewritable Discs), magneto-optical recording media such as MOs (Magneto-Optical disks), tape media, magnetic recording media, and semiconductor memories.

[0037] The CPU 201 of the user terminal 2 realizes various functions by reading out the programs stored in the storage unit 204, ROM 202, or media into the RAM 203 and executing them. The programs may also be acquired from another device, such as a server device, via the network 4. Furthermore, it goes without saying that the user terminal 2 is provided with a configuration necessary for realizing the information processing in this embodiment.

[0038] (Overview of payment application functionality) Next, functions and data of the payment application 200 according to this embodiment will be described with reference to Fig. 5. Note that in this embodiment, the display control function in the user terminal 2 will be mainly described.

[0039] Fig. 5(a) is a diagram showing data stored in memory unit 204 of user terminal 2. As shown in Fig. 5(a), memory unit 204 of user terminal 2 stores, in addition to the program of payment application 200, data of various screens displayed in the payment application (hereinafter referred to as screen data 230), and user identification information 220 for the electronic payment service. Identification information 220 is assigned by electronic payment server 5 when an account is registered.

[0040] Payment application 200 is an application program installed and used on user terminal 2 of a user of an electronic payment service, and is operated and managed by a service provider that provides the electronic payment service. Payment application 200 is generally installed on user terminal 2 by downloading it from a website, but it may also be read from a medium and installed on user terminal 2. Payment application 200 may also be provided as a web application that runs on a web browser of user terminal 2.

[0041] In addition to a payment processing function for performing electronic payments in electronic payment services, the payment application 200 has a point function, a charge function, a coupon function, an information content delivery function, a My Page function for managing user account information, etc. In addition, the payment application 200 has a display control function for controlling the display of the screen, and a reception function for receiving operations.

[0042] Fig. 5(b) is a diagram showing the configuration of program modules of payment application 200. As shown in Fig. 5(b), payment application 200 of this embodiment has, as program modules, a payment processing unit 501, a reception unit 502, and a display control unit 503. Although not shown, payment application 200 also has various program modules for realizing the various functions described above.

[0043] The payment processing unit 501 executes payment processing using the identification code between the store terminal 3 or the electronic payment server 5. The payment processing unit 501 transmits and receives information related to payment between the user terminal 2 and the store terminal 3 or the electronic payment server 5 according to each processing procedure of the store scan and user scan described above, and starts and completes electronic payment.

[0044] The reception unit 502 receives an operation by a user via the operation unit 205 of the user terminal 2. When the operation unit 205 of the user terminal 2 is configured with a touch panel display, the operation on the touch panel display may be in the following forms. That is, a tap operation in which an operation target is touched with one finger, a swipe operation in which a finger is slid while touching the screen, a long press operation in which a touch state is maintained for a predetermined time or more, a pinch out operation in which the distance between two fingers touching the screen is moved from a narrowed state to a wider state, and a pinch in operation in which the distance between two fingers touching the screen is moved from a wider state to a narrowed state. The pinch in operation and the pinch out operation are collectively called pinch operations. Note that the operation on the user terminal 2 is not limited to these. The reception unit 502 may receive various operations such as a double tap operation, a triple tap operation, a swipe operation with multiple fingers, and the like, in which a tap operation is repeated multiple times. In addition, if the operation unit 205 is not a touch panel display but is configured with input devices such as a keyboard and a mouse, the reception unit 502 receives input for specific operations and other operations described below using an operation method corresponding to each input device.

[0045] The reception unit 502 receives a specific operation by a user. In this embodiment, the specific operation is a pinch-in operation and a pinch-out operation. Note that the specific operation is not limited to a pinch-in operation and a pinch-out operation, and may be other operations. Furthermore, the operation target of the specific operation may be the identification codes 101, 102, or the code display area 104. Alternatively, the specific operation may be performed in an area outside the code display area 104, or may be performed so as to straddle the inside and outside of the code display area 104.

[0046] The display control unit 503 controls the display of various screens corresponding to various functions of the payment application 200. The display control unit 503 acquires screen data 230 of a screen corresponding to a function from the storage unit 204 in response to an operation by a user, and reflects the identification information 220 and the balance information acquired from the electronic payment server 5 on the screen and displays it on the display unit 206. For example, when the user double-tap the activation icon of the payment application 200 displayed on the home screen of the user terminal 2, the payment application 200 is activated. When the payment application 200 is activated, the display control unit 503 displays the top screen 100 shown in FIG. 1(a). In addition, when the user taps the payment button 109 displayed on the top screen 100, the display control unit 503 displays the payment screen 310 shown in FIG. 3(a) on the display unit 206. When the scan button 108 displayed on the top screen 100 is tapped, the display control unit 503 displays the scan screen 320 shown in FIG. 3(b) on the display unit 206. In addition, when a button for various functions displayed on the top screen 100 is tapped, the display control unit 503 causes the display unit 206 to display a screen corresponding to the operated button.

[0047] In this embodiment, when the reception unit 502 receives a specific operation by a user, the display control unit 503 enlarges or reduces the display size of the identification code displayed on the screen in accordance with the specific operation. In this embodiment, the reception unit 502 receives the specific operation in a state in which the identification codes 101, 102 are displayed on the top screen 100 that is displayed immediately after the start of the payment application 200. The top screen 100 also displays a button 109 for transitioning to the payment screen 310. The display control when a specific operation is performed will be described in detail below.

[0048] FIG. 6 is a diagram for explaining a specific operation in the payment application 200 and a change in the display state of the screen. FIG. 6(a) shows an example of an initial state of the top screen 100 displayed immediately after the start of the payment application 200. As shown in FIG. 6(a), the top screen 100 displays a code display area 104 including a one-dimensional code, which is a first identification code 101, and a two-dimensional code, which is a second identification code 102, which are identification codes obtained by encoding the user's identification information. The code display area 104 may display a payment method 603 and balance information of an electronic account linked to the user's identification information. In addition, a fixed display area 608 at the bottom of the top screen 100 displays a payment button 109 operated when transitioning to a payment screen 310. In the fixed display area 608, a button operated when displaying information provided by an electronic payment service provider, a wallet button operated when displaying balance information, point information, and credit information are displayed. In addition, an account button operated when displaying account information or a My Code used for remittance, a home button operated when calling up the top screen 100 from another screen, and the like are also displayed in the fixed display area 608. The fixed display area 608 is not linked to screen scrolling, and is always displayed at a fixed position on the display unit 206 of the user terminal 2. In the example of Fig. 6, the fixed display area 608 is displayed at the bottom of the display unit 206. Note that in this specification, the terms "up, down, left, right" and "down" used in the description of the screen refer to the top, bottom, left, right and left within the plane of the screen.

[0049] A menu area 605 is provided directly below the code display area 104. In addition to the scan button, the menu area 605 displays each button operated when transitioning to a remittance screen, a points screen, a transaction history screen, and a charge screen. In addition, campaign information 610 and a notification icon 611 are displayed above the code display area 104. The campaign information 610 may not be displayed if the relevant campaign is not being implemented. In addition, a function selection area 606 is provided in which buttons operated when transitioning to screens for various functions of the payment application 200 are displayed, and a balance display area 607 is provided in which the point balance, creditable amount, balance of the payment application, etc. are displayed. Furthermore, when the top screen 100 is scrolled downward, information related to the payment application, such as coupon information and nearby store information, is displayed.

[0050] When the reception unit 502 receives a specific operation (pinch out operation and pinch in operation) on the top screen 100, the display control unit 503 enlarges or reduces the display size of the identification codes 101 and 102 in response to the specific operation. When a pinch out operation is received, the display control unit 503 enlarges the display size of the identification codes 101 and 102. When a pinch in operation is received, the display control unit 503 reduces the display size of the identification codes 101 and 102. Note that in the example of FIG. 6, the display control unit 503 enlarges or reduces the display size of the code display area 104 including the identification codes 101 and 102, thereby enlarging or reducing the display size of the identification codes 101 and 102. The enlarged identification codes 101C and 102C are shown in FIG. 6(c). In the top screen 100C shown in FIG. 6(c), the code display area 104C is displayed in an enlarged manner compared to the code display area 104 in FIG. 6(a). The identification codes 101C and 102C included in the code display area 104C are also enlarged.

[0051] When the reception unit 502 receives a second operation different from the specific operation on the top screen 100, the display control unit 503 changes the identification code 101, 102 or the code display area 104 to an active state. The active state is a state in which a specific operation can be received. In this embodiment, the second operation is a long press operation on the identification code 101, 102 or the code display area 104. However, the second operation is not limited to a long press operation, and may be other operations such as a state in which a finger is simply placed (touch operation), a tap operation, a double tap operation, etc. In addition, when the operation unit 205 is configured by an input device such as a keyboard or a mouse instead of a touch panel display, the reception unit 502 receives the input of the second operation by an operation method corresponding to each input device.

[0052] In order to make the user recognize that the area is in an active state, the display control unit 503 displays the identification code 101, 102 or the code display area 104, which is the object of operation, in a hover manner. The top screen 100B shown in FIG. 6(b) is a diagram showing an example in which the code display area 104B is displayed in a hover manner. The hover display is a visual change that occurs when a specific operation is performed on a specific element on the screen. For example, the display state may be changed so that the operated code display area 104B is visually recognized as floating from other areas, or the color of the code display area 104B may be changed. The hover display can show the user that the area to be operated is in an active state (operable). In addition to the hover display, the audio processing unit 210 may generate a sound or a vibration.

[0053] In this embodiment, the reception unit 502 receives a specific operation on the identification codes 101, 102 or the code display area 104 in the active state. That is, the reception unit 502 receives a second operation on the top screen 100 of Fig. 6(a), and receives the specific operation after hovering the code display area 104B as shown in Fig. 6(b). The specific operation changes the screen to the top screen 100C shown in Fig. 6(c).

[0054] When enlarging or reducing the display size of the identification codes 101, 102, the display control unit 503 preferably enlarges or reduces the display size according to the screen layout. Specifically, the display control unit 503 enlarges or reduces the display size of the identification codes 101, 102 or the code display area 104 within a range up to a predetermined maximum size that does not exceed the display range of the display unit 206. The display range on the display unit 206 is the entire area of ​​the display of the display unit 206, i.e., the range equivalent to the display size.

[0055] On the top screen 100, the longitudinal direction of the identification code 101, which is a one-dimensional code, is laid out so that it coincides with the width direction of the display unit 206. Also, the longitudinal direction of the code display area 104 is laid out so that it coincides with the width direction of the display unit 206. In the example of FIG. 6, the width direction of the display unit 206 is the left-right direction in the figure. In other words, when the longitudinal direction of the display of the display unit 206 is displayed as the up-down direction (scroll direction) of the top screen 100, the direction perpendicular to the longitudinal direction of the display of the display unit 206 is the width direction of the display unit 206.

[0056] The display control unit 503 enlarges the display size of the identification code 101, 102 or the code display area 104 so that the display size in the longitudinal direction of the identification code 101, which is a one-dimensional code, or the longitudinal direction of the code display area 104 fits within the size of the direction perpendicular to the longitudinal direction of the display range of the display unit 206. That is, in the example of Fig. 6, the display size in the longitudinal direction of the identification code 101 or the longitudinal direction of the code display area 104 is enlarged so as to fit within the width direction of the display unit 206.

[0057] Furthermore, display control unit 503 enlarges or reduces the display size of identification code 101, 102 or code display area 104 within a range up to a predetermined minimum size that is not smaller than the display size of identification code 101, 102 or code display area 104 in the initial state. The initial state is the display state of top screen 100 that is displayed immediately after payment application 200 is started up.

[0058] The enlargement or reduction may be a two-stage change in the display size between the minimum size and the maximum size, or the size may be changed continuously in response to an operation within the range from the minimum size to the maximum size. The display control unit 503 enlarges or reduces the identification codes 101, 102 or the code display area 104 while maintaining the aspect ratio of the identification codes 101, 102 and the code display area 104 in their initial state.

[0059] 6 shows an example in which the display size of the code display area 104 is enlarged or reduced, but the display control unit 503 may enlarge or reduce only the identification codes 101, 102. Also, only one of the two types of identification codes 101 and 102 may be enlarged or reduced, or both may be enlarged or reduced.

[0060] When enlarging or reducing the display size of the code display area 104, it is preferable that the display control unit 503 maintains the display size of the area (second area) excluding the code display area 104 in the top screen 100. The display control unit 503 may enlarge or reduce the display size of the code display area 104 so that the code display area 104 does not overlap the second area, or may enlarge or reduce the display size of the code display area 104 so that the code display area 104 overlaps part of the second area.

[0061] (Display control processing) Next, the flow of the display control process of this embodiment will be described with reference to Fig. 7. The process shown in this flowchart is written in the program of payment app 200 installed in user terminal 2. The program is stored in storage unit 204, called by CPU 201, and deployed in RAM 203 for execution. When the user operates the start-up icon of payment app 200 and starts up payment app 200, CPU 201 starts this process. In the following description, the symbol "S" means step.

[0062] In S101, the CPU 201 first obtains screen data 230 of the top screen 100 of the payment application 200 from the storage unit 204, and displays it on the display unit 206 as shown in FIG. 6(a). As described above, the top screen 100 is provided with the code display area 104, the menu area 605, the function selection area 606, the balance display area 607, the fixed display area 608, and the like. The payment button 109 is displayed in the fixed display area 608. Campaign information 610 and a notification icon 611 are displayed in the upper area of ​​the code display area 104. In addition, an operation button such as a credit payment button 612, which is operated when transitioning to a credit payment screen, may be displayed in the right area of ​​the code display area 104.

[0063] In the initial state shown in FIG. 6(a), the code display area 104 is arranged so as not to overlap with the campaign information 610 and the notification icon 611 displayed at the top, the menu area 605 displayed at the bottom, and the credit payment button 612 displayed in the right area. Also, in FIG. 6, the code display area 104 is arranged so that the center of the length direction coincides with the center of the width direction of the display unit 206. As described above, the width direction of the display unit 206 is perpendicular to the length direction of the display range of the display unit 206 in the screen layout example of FIG. 6. However, this is not limited to this, and the code display area 104 may be displayed biased to one end, such as left-justified or right-justified. The credit payment button 612 may be arranged on the left side of the code display area 104.

[0064] In S102, the CPU 201 accepts an operation on the top screen 100. When the input unit 207 detects that a long press operation has been input on the code display area 104, and the CPU 201 acquires the detection signal from the input unit 207 (S102; YES), the process proceeds to S103. If the operation on the top screen 100 is not an operation on the code display area 104 but an operation on another button (S112; YES), the process proceeds to a process corresponding to the operation (S113). For example, if the payment button 109 is operated, the process transitions to the payment screen 310 shown in FIG. 3(a), and the process proceeds to the payment screen 310. If no operation is performed on the top screen 100 (S112; NO), the process returns to S102 and waits for an operation.

[0065] In S103, the CPU 201 displays the code display area 104 in a hover display, and sets the code display area 104 in an active state. As shown in FIG. 6B, in the hover display, a shadow is displayed around the code display area 104, and a visual effect that makes the code display area 104 appear to be raised is obtained. The CPU 201 may also express the active state by vibration, sound, or the like together with the hover display. In addition, in the initial state, a tap mark 620 may be displayed in the code display area 104 to guide the user to operate the code display area 104. However, the position at which the CPU 201 detects the long press operation in S102 is not limited to the position of the tap mark 620, and may be any position within the code display area 104. The hover display continues for a predetermined time of about several seconds. That is, the active state continues for a predetermined time of about several seconds.

[0066] When the code display area 104 is in a hovered display state, i.e., when the code display area 104 is in an active state, the code display area 104 accepts a pinch operation on the code display area 104. When the input unit 207 detects a pinch out operation on the code display area 104 and the CPU 201 acquires the detection signal in S104 (S104; YES), the process proceeds to S105. In S105 to S106, the CPU 201 enlarges the display size of the code display area 104 in conjunction with the pinch out operation.

[0067] In S105, the CPU 201 determines the maximum size of the code display area 104. FIG. 8 is a diagram for explaining the display size of the code display area 104 in the layout of the top screen 100. In the description of FIG. 8, the width direction is the left - right direction of the figure, and the height direction is the up - down direction of the figure.

[0068] FIG. 8(a) shows the size and screen layout of the code display area 104 in the initial state. In the initial state, that is, in S101, it is assumed that the width size (hereinafter referred to as the width size) in the longitudinal direction of the code display area 104 is W1, and the height size (hereinafter referred to as the height size) in the height direction is H1. The display size W1×H1 in this initial state is determined in advance. The display size in the initial state may be determined as a ratio to the display size (display range) of the display unit 206. Specifically, the ratio W1 / Wd of the width size W1 of the code display area 104 to the width size Wd of the display is determined in advance so that it becomes a predetermined ratio α1 (α1 < 1). Similarly for the height size, the ratio H1 / Hd of the height size H1 of the code display area 104 to the height size Hd of the display is determined in advance so that it becomes a predetermined ratio β1 (β1 < 1). For example, α1 = 0.7, β1 = 0.2, etc.

[0069] The CPU 201 determines the width size W2 and height size H2 of the code display area 104 corresponding to the maximum ratio αmax at the time of enlargement determined in advance. αmax is the ratio W2 / Wd of the maximum width size W2 of the code display area 104 to the width size Wd of the display, and is determined in advance, for example, as αmax = 0.99. Also, αmax is set to a value greater than the ratio α1 in the initial state and less than or equal to 1 (α1 < αmax ≤ 1). The maximum height size H2 of the code display area 104 is determined based on the aspect ratio (H1 / W1) of the code display area 104 in the initial state. That is, the display size of the maximum code display area 104 after enlargement is determined by the following formulas (1) and (2).

[0070] W2 = αmax×Wd ···(1) H2 = W2 × (H1 / W1) (2)

[0071] The width W2 of the code display area 104 after enlargement is controlled so as to be equal to or smaller than the width Wd of the display of the display unit 206 at most.

[0072] In S106, the CPU 201 enlarges the code display area 104 in the width direction by ΔW and in the height direction by ΔH in conjunction with the pinch-out operation, with the size W2×H2 determined in S105 as the maximum size. When enlarging, the aspect ratio of the code display area 104 is maintained. When the size of the code display area 104 reaches the maximum size W2×H2, the display control unit 503 controls the code display area 104 to maintain the maximum size even if a pinch-out operation is performed. In this way, by limiting the maximum size after enlargement to the display size or less, the code display area 104 and the identification codes 101 and 102 are enlarged so as not to protrude from the screen. Therefore, the code is enlarged to an appropriate size that allows it to be read, and visibility is improved. In addition, even if the user does not perform the pinch-out operation accurately, the identification codes 101 and 102 do not protrude from the screen, and the operability of the user terminal 2 is improved.

[0073] Furthermore, when the input unit 207 detects a pinch-in operation on the code display area 104 while the code display area 104 is enlarged, and the CPU 201 acquires the detection signal in S107 (S107; YES), the process proceeds to S108. In S108 to S109, the CPU 201 reduces the display size of the code display area 104 in conjunction with the pinch-in operation.

[0074] In S108, the CPU 201 determines the minimum size of the code display area 104. In this embodiment, the display size W1×H1 of the code display area 104 in the initial state is set as the minimum size of the code display area 104. As described above, the width size W1 of the code display area 104 in the initial state, i.e., the minimum width size W1 of the code display area 104, is the size obtained by multiplying the width size Wd of the display of the display unit 206 by the ratio α1. The width size of the code display area 104 after reduction is controlled so that it is at least not smaller than the width size W1 of the code display area 104 in the initial state.

[0075] If a minimum ratio αmin is determined in advance instead of the ratio α1, the CPU 201 determines the width size Wmin and height size Hmin of the code display area 104 that correspond to the ratio αmin. In this case, the minimum width size Wmin and height size Hmin of the code display area 104 after reduction are determined by the following expressions (3) and (4).

[0076] Wmin = αmin × Wd (3) Hmin = Wmin × (H1 / W1) (4) However, αmin<αmax≦1.

[0077] In this case, the reduced width of the code display area 104 is displayed so as to be at least equal to or greater than the width Wmin of the code display area 104 in its initial state.

[0078] In S109, the CPU 201 reduces the code display area 104 in the width direction by ΔW and in the height direction by ΔH in conjunction with the pinch-in operation, with the size W1×H1 (or size Wmin×Hmin) determined in S108 as the minimum size. When reducing, the aspect ratio of the code display area 104 is maintained. When the size of the code display area 104 reaches the initial size W1×H1 (or the minimum size Wmin×Hmin), the display control unit 503 controls to maintain the initial size (or minimum size) even if a pinch-in operation is performed. In this way, by restricting the size after reduction so that it does not fall below the initial size (or a predetermined minimum size), the code is reduced to an appropriate size that allows code reading, improving visibility. In addition, even if the user does not perform the pinch-in operation accurately, the identification codes 101 and 102 do not become too small, improving the operability of the user terminal 2. After S109, proceed to S104.

[0079] If a pinch out operation is not performed in S104 (S104; NO), or if a pinch out operation is performed and then a pinch in operation is not performed after the enlarged display (S107; NO), the process proceeds to S110. In S110, the CPU 201 determines whether a predetermined time has elapsed since the active state or a predetermined time has elapsed since the last operation. If the predetermined time has not elapsed (S110; NO), the active state is maintained and the process proceeds to S104. If a predetermined time has elapsed since the active state or a predetermined time has elapsed since the last operation (S110; YES), the process proceeds to S111. In S111, the CPU 201 cancels the hover display and the active state of the code display area 104. After that, the process ends.

[0080] FIG. 8(b) is a diagram showing a top screen 100C in which a code display area 104C enlarged to a maximum size W2×H2 is displayed. In the example of FIG. 8(b), due to the enlargement of the code display area 104, a part of the area of the top screen 100C that was initially displayed is not shown on the screen. That is, the enlarged code display area 104C is displayed so as to overlap the campaign information 610, the notification icon 611, and the credit payment button 612, while the other areas are displayed so as not to overlap the code display area 104C. Operations on the various displayed buttons are acceptable.

[0081] When a pinch-in operation is performed on the code display area 104C in the enlarged state as shown in FIG. 8(b), the code display area 104 is reduced to the initial display size W1×H1 shown in FIG. 8(a).

[0082] In the description of the flowchart in FIG. 7, when performing an enlarged display or a reduced display, it was assumed that the width size and height size of the code display area 104C are changed by ΔW and ΔH respectively in conjunction with the pinch operation, but it is not limited to this. For example, when a pinch-out operation is performed, it may be changed from the initial state, which is the minimum size, to the maximum size at once, and when a pinch-in operation is performed, it may be changed from the maximum size to the initial state, which is the minimum size, at once. If the display size is limited to two levels in this way, the enlargement and reduction operations can be performed instantaneously.

[0083] Also, in the display example of FIG. 8(b), the campaign information 610 and the notification icon 611 are hidden by the code display area 104, but it is not limited to such a screen layout. The display of the campaign information 610 and the notification icon 611 may be maintained even after enlargement. In that case, the CPU 201 may shift the display positions of the menu area 605, the function selection area 606, the balance display area 607, and other areas arranged below the code display area 104 downward by the length (H2 - H1) of the enlargement in the height direction of the code display area 104. By doing so, it becomes possible for the user to visually recognize the information displayed on the top screen 100C even after enlargement.

[0084] As described above, according to the payment app 200 of the first embodiment, it is possible to enlarge or reduce the identification code displayed on the display unit 206 of the user terminal 2 based on a specific operation by the user. This improves the visibility of the identification code in the payment app 200. Furthermore, the identification code can be enlarged or reduced to a size suitable for code reading by an intuitive operation without transitioning to a payment screen, which is a separate screen, thereby improving operability.

[0085] In the first embodiment, an example is shown in which the code display area 104 (identification codes 101, 102) is changed to an active state by the second operation (long press operation) and then a specific operation is accepted, but the present disclosure is not limited to this. A configuration for transitioning to an active state does not necessarily have to be provided. In that case, the identification codes 101, 102 or the code display area 104 of the top screen 100 are always in an active state. In the flowchart of FIG. 7, after S101, S102 to S103 are skipped and the process proceeds to S104. As shown in FIG. 1, when the accepting unit 502 accepts a pinch operation on the identification codes 101, 102 or the code display area 104, the display control unit 503 enlarges or reduces the display size of the identification codes 101, 102 or the code display area 104 in response to the pinch operation. Also, if the pinch operation is not accepted (S104; NO or S107; NO), the process proceeds to S112.

[0086] <Second embodiment> In the first embodiment, an example was shown in which the target to be enlarged or reduced in response to a specific operation was the code display area 104 or the identification codes 101, 102, but the target to be enlarged or reduced may be the entire screen including the identification codes 101, 102. In the second embodiment, an example will be described in which the entire screen including the identification codes 101, 102 is enlarged or reduced in response to a specific operation. Note that the configurations 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 those in the first embodiment, so duplicated explanations will be omitted and the same components will be denoted by the same reference numerals.

[0087] FIG. 9 is a diagram for explaining display control by the payment application 200 of the second embodiment. FIG. 9(a) shows the initial state of the top screen 100 of the payment application 200, and FIG. 9(b) shows the top screen 100D enlarged by a pinch-out operation. The initial state top screen 100 is the same as that of the first embodiment. In the enlarged top screen 100D shown in FIG. 9(b), not only the code display area 104 but also the entire screen is enlarged and displayed. That is, other areas of the top screen 100 except for the code display area 104 are also enlarged together with the code display area 104. As a result, a part of the initial state top screen 100 does not fit within the display range of the display unit 206 and is displayed so as to protrude. However, the size and arrangement of the code display area 104 are controlled so that it fits within the display range of the display unit 206 even after enlargement.

[0088] (Display control processing) The display control process in the second embodiment will be described with reference to Fig. 10. The process shown in this flowchart is written in a program of the payment app 200 according to the second embodiment installed in the user terminal 2. The program is stored in the storage unit 204, called by the CPU 201, and deployed in the RAM 203 for execution. When the start-up icon of the payment app 200 is operated by the user and the payment app 200 is started, the CPU 201 starts this process. In the following description, the symbol "S" means a step.

[0089] In S201, the CPU 201 first obtains screen data 230 of the top screen 100 of the payment application 200 from the storage unit 204, and displays it on the display unit 206 as shown in FIG. 9(a). The top screen 100 is the same as in the first embodiment. Also, the size of the code display area 104 in the initial state is displayed with a predetermined initial size W1×H1, as in the first embodiment. Note that the width size Ws of the entire top screen 100 in the initial state matches the width size Wd of the display range (whole display) of the display unit 206. Also, the height size Hs of the top screen 100 in the initial state is a size according to the amount of information. In the example of FIG. 9, the height size Hs of the top screen 100 is longer than the height size Hd of the display range of the display unit 206, and the area displayed in the display range is changed by a scroll operation.

[0090] In S202, the CPU 201 accepts an operation on the top screen 100. In the second embodiment, the entire top screen 100 is the operation target, and the entire top screen 100 is assumed to be in an active state in advance and managed as being capable of accepting specific operations. If an operation on the top screen 100 has been performed (S202; YES), the process proceeds to S203.

[0091] In S203, the input unit 207 detects a pinch out operation on the top screen 100, and when the CPU 201 acquires the detection signal from the input unit 207 (S203; YES), the process proceeds to S204. In S204 to S205, the CPU 201 enlarges the display size of the entire screen of the top screen 100 in conjunction with the pinch out operation.

[0092] In S204, the CPU 201 determines the maximum size of the top screen 100 based on the predetermined maximum ratio αmax. αmax is the same as in the first embodiment, and is determined in advance as the ratio W2 / Wd of the maximum width size W2 of the code display area 104 to the width size Wd of the display. For example, it is determined in advance as αmax=0.99. In addition, αmax is set to a value greater than the ratio α1=W1 / Wd in the initial state and equal to or less than 1 (α1<αmax≦1). The aspect ratio (H1 / W1) of the code display area 104 in the initial state is maintained for the height size H2. That is, the maximum sizes W2 and H2 of the code display area 104 after enlargement are determined by the above-mentioned formulas (1) and (2).

[0093] In S205, the CPU 201 enlarges the entire screen of the top screen 100 in response to the pinch out operation by ΔW in the width direction and ΔH in the height direction while maintaining the aspect ratio (H1 / W1) of the code display area 104. At this time, the CPU 201 displays the enlarged top screen 100D so that the center of the width direction of the code display area 104 coincides with the center of the width direction of the display. The CPU 201 also displays the enlarged top screen 100D so that the upper and lower ends of the code display area 104 are displayed on the display. When the size of the code display area 104 reaches the maximum size W2×H2, even if a pinch out operation is performed, the display control unit 503 controls the code display area 104 to maintain the maximum size without enlarging it any further. In this way, by restricting the maximum size of the code display area 104 after enlargement to be equal to or smaller than the display size, the identification codes 101 and 102 are enlarged so as to fit within the display range of the display unit 206. Therefore, the code is enlarged to an appropriate size that allows it to be read, improving visibility. Even if the user does not perform a pinch-out operation accurately, the identification codes 101 and 102 do not go outside the display range, improving the operability of the user terminal 2.

[0094] Furthermore, the CPU 201 may adjust the brightness of the screen according to the display size of the identification code. That is, in response to a pinch-out operation, the CPU 201 controls to increase the brightness of the screen while enlarging the identification code 101, 102 or the code display area 104. The brightness may be increased by small amounts according to the amount of enlargement, or may be increased to the maximum brightness all at once. This makes it possible to display the identification code on a bright screen suitable for code reading, further improving visibility.

[0095] When the input unit 207 detects a pinch-in operation while the top screen 100 is enlarged, and the CPU 201 acquires the detection signal in S206, the process proceeds to S207. In S207 to S208, the CPU 201 reduces the display size of the enlarged top screen 100D in conjunction with the pinch-in operation.

[0096] In S207, the CPU 201 determines the minimum size of the top screen 100. In this embodiment, the CPU 201 sets the width size Ws of the top screen 100 in the initial state as the minimum width size of the top screen 100. As described above, the width size Ws of the top screen 100 in the initial state matches the width size Wd of the display of the display unit 206.

[0097] In S208, the CPU 201 reduces the top screen 100D by ΔW in the width direction and ΔH in the height direction in conjunction with the pinch-in operation, with the size determined in S207 as the minimum size. When reducing, the aspect ratio (H1 / W1) of the code display area 104 is maintained. At this time, the CPU 201 displays the reduced top screen 100 so that the center of the code display area 104 in the width direction coincides with the center of the display in the width direction. The CPU 201 also displays the reduced top screen 100 so that the upper and lower ends of the code display area 104 are displayed on the display. When the size of the top screen 100 reaches the initial size Ws×Hs, the CPU 201 is controlled by the display control unit 503 to maintain the initial size Ws×Hs even if a pinch-in operation is performed. In this way, the reduced size is limited so as not to fall below the initial size, so that the screen is reduced to an appropriate size that allows code reading. Since the user does not need to perform the pinch-in operation accurately, operability is improved.

[0098] Furthermore, the CPU 201 may adjust the brightness of the screen according to the display size of the identification code. That is, in response to a pinch-in operation, the identification code 101, 102 or the code display area 104 is reduced, and the CPU 201 controls to reduce the brightness of the screen. The brightness may be reduced in small increments according to the amount of reduction, or may be reduced all at once to the minimum brightness. The minimum brightness may be the brightness in the initial state of the top screen or a predetermined brightness that has been determined in advance. This allows the screen to be displayed at an appropriate brightness in conjunction with. After S208, the process proceeds to S202.

[0099] When an operation is detected in S202, the CPU 201 determines whether or not a pinch out operation is performed in S203. When a pinch out operation is not performed (S203; NO), or when a pinch out operation is performed and a pinch in operation is not performed after the enlarged display (S206; NO), the process proceeds to S209. In S209, the CPU 201 determines whether or not an operation other than a pinch operation is input. When an operation other than a pinch operation is performed, the process proceeds to S210, and a process corresponding to the operation is executed. For example, when the payment button is operated, the screen transitions to the payment screen 310. When the scan button is operated, the screen transitions to the scan screen 320. When any other operation of selecting various buttons or areas is performed, the screen transitions to a screen corresponding to the operation, and the process proceeds to the transition screen. When no operation other than a pinch operation is performed, the process returns to S202, and the process waits for an operation on the top screen 100. When no operation is performed even after a predetermined time has elapsed, the process ends.

[0100] 9(b) is a diagram showing the state in which the entire top screen has been enlarged. As the top screen is enlarged, the code display area 104 is enlarged, and the identification codes 101 and 102 displayed in the code display area 104 are also enlarged. In addition, the areas other than the code display area 104 are also enlarged. Due to the enlarged display, a part of the screen that was displayed in the initial state is outside the display range and is no longer displayed.

[0101] When a pinch-in operation is performed on top screen 100D in the state of FIG. 9(b), the entire enlarged top screen 100D is reduced to the size Ws×Hs of the initial state shown in FIG. 9(a).

[0102] In the description of the flowchart in Fig. 10, the width size and height size of the screen are changed by ΔW and ΔH in response to a pinch operation when enlarging or reducing, but this is not limited to the above. For example, when a pinch out operation is performed, the size may be changed from the initial state, which is the minimum size, to the maximum size in one go, and when a pinch in operation is performed, the size may be changed from the maximum size to the initial state in one go. In this way, if the display size of the top screen is limited to two states, enlarging and reducing operations can be performed instantly.

[0103] As described above, according to the payment application 200 of the second embodiment, in addition to the effects of the first embodiment, it is possible to enlarge or reduce the display of buttons and information other than the identification code. In this case, the size and layout of the identification code are controlled so that it fits on the screen, so it is possible to change the display size of the identification code without interfering with reading the code at the time of payment.

[0104] In the above-described embodiments, an example has been shown in which the code display area 104 of the top screen 100 is enlarged up to a predetermined maximum ratio αmax based on the display size. When enlarging only the identification code, the width size of the identification code (the longitudinal size in the case of a one-dimensional code) is enlarged up to a predetermined maximum ratio αmax so as not to exceed the width size of the display (the direction perpendicular to the longitudinal direction of the display range of the display unit). As shown in the first embodiment, only the identification code may be enlarged while maintaining the display size of the other areas of the top screen, or as shown in the second embodiment, the size of the entire top screen may be enlarged together with the enlargement of the identification code.

[0105] In addition, in the second embodiment, the entire display screen is enlarged, but the present invention is not limited to this. A part of the screen may be fixedly displayed, and the other part may be enlarged or reduced in response to a pinch operation. If the part of the screen that is fixedly displayed is, for example, a fixed display area 608 at the bottom of the screen, the fixed display area 608 will not be enlarged or reduced even if a pinch operation is performed. Therefore, frequently used buttons such as the payment button 109 in the fixed display area 608 are always displayed without going out of the display range, improving operability.

[0106] Also, as shown in the first embodiment, when the reception unit 502 receives a second operation different from the specific operation, the identification codes 101, 102 or the area 104 including the identification codes are changed to an active state and changed to a hover display, and when the reception unit 502 receives a specific operation on the screen (top screen 100) on which the identification codes 101, 102 are displayed, the display control unit 503 may be configured to enlarge or reduce the display size of the entire screen in response to the specific operation. In other words, when the user wants to enlarge or reduce only the identification codes 101, 102 or the area 104 including the identification codes, the user can perform a pinch operation after performing a long press operation on the identification codes 101, 102 or the area 104 including the identification codes, as in the first embodiment, and when the user wants to enlarge or reduce the entire screen, the user can perform a pinch operation without long press on the identification codes 101, 102 or the area 104 including the identification codes.

[0107] In the present disclosure, when enlarging the identification codes 101, 102 or the identification code display area 104, the display control unit preferably enlarges the identification codes 101, 102 or the code display area 104 so that they do not overlap with various areas other than the area, but the identification codes 101, 102 or the code display area 104 may be enlarged so that they overlap with various areas other than the area. In addition, the present disclosure is not limited to the enlargement or reduction of the identification codes displayed on the top screen, but can also be applied to identification codes displayed on other screens.

[0108] Furthermore, as described in the first embodiment above, when a second operation different from the specific operation is received, the display control unit may change the identification code or the area including the identification code to an active state and receive the specific operation in the active state. The second operation is, for example, a long press operation on the identification code or the area including the identification code. In the active state, the display control unit performs a hover display that gives a visual change to the identification code or the area including the identification code. The hover display is, for example, a display state that makes the user visually recognize the target area as floating above the screen, or an expression such as a change in color that makes the target area visually different from other areas.

[0109] Also, as described in the second embodiment, the display control unit may enlarge or reduce the entire screen in response to the specific operation, thereby enlarging or reducing the identification code. In this case, not only the identification code but also buttons and information displayed on the screen can be enlarged or reduced, so that the display of the screen can be adjusted to an appropriate size that is easy for the user to see and operate. When enlarging or reducing the entire screen, the display control unit enlarges or reduces the display size of the entire screen so that the identification code fits within the display range of the display unit. Also, in the second embodiment, when a second operation different from the specific operation is received, the display control unit may change the entire screen to an active state and receive the specific operation in the active state. In addition, in the active state, the display control unit may display an indication that the entire screen has become active. That is, when a second operation such as a long press operation is received on the entire screen, the display state may be changed to one indicating an active state, and then the specific operation may be received and the entire screen may be enlarged or reduced.

[0110] In addition, when the receiving unit changes the identification code or an area including the identification code to an active state when it receives a second operation different from the specific operation, when the receiving unit receives a specific operation on the screen on which the identification code is displayed, the display control unit may enlarge or reduce the display size of the entire screen in response to the specific operation.

[0111] Furthermore, the display control unit may adjust the brightness of the screen according to the display size of the identification code. That is, in response to a pinch-out operation, the display control unit may control to enlarge the identification code or code display area and increase the brightness of the screen. Also, in response to a pinch-in operation, the display control unit may control to reduce the identification code or code display area and decrease the brightness of the screen.

[0112] According to the present disclosure, it is possible to display a large amount of information in a limited display area while changing the size of an identification code to a size appropriate for reading the code, thereby improving the operability and visibility of a payment application.

[0113] Although the preferred embodiment of the present disclosure has been described above with reference to the attached drawings, the present disclosure is not limited to such examples. For example, the buttons and information displayed on the screen, the screen layout, the processing procedures shown in the flowchart, etc. are only examples and can be appropriately changed without departing from the technical idea of ​​the present disclosure. In addition, it is clear that a person skilled in the art can come up with various modified or amended examples within the scope of the disclosed technical idea, and it is understood that these also naturally belong to the technical scope of the present disclosure. [Explanation of symbols]

[0114] 1. Electronic payment systems 2. User terminal 100 Top screen 101, 102 Identification Code 104 Code display area 109 Payment Button 200 Payment App 501 Payment processing unit 502 Reception 503 Display control unit

Claims

1. A payment application program that is pre-installed in a terminal device used by a user of electronic payment to use an identification code, the terminal device comprising: a display control unit that causes a display unit of the terminal device to display the identification code; a reception unit that receives an operation by the user on the terminal device, The display control unit is When the reception unit receives a specific operation, the display size of the identification code is enlarged or reduced in accordance with the specific operation; the specific operation is a pinch out operation or a pinch in operation, When the pinch out operation is received, the display control unit increases a display size of the identification code, When the pinch-in operation is received, the display control unit reduces a display size of the identification code, the accepting unit accepts the specific operation while the identification code is displayed on a top screen that is displayed immediately after the start of the payment application program, An operation button for transitioning to a payment screen on which the identification code is displayed in an enlarged manner is displayed on the top screen. A payment application program comprising:

2. The payment application program according to claim 1 , wherein the display control unit enlarges or reduces a display size of the identification code so that the identification code fits within a display range of the display unit.

3. The payment application program according to claim 2, characterized in that the display control unit enlarges the display size of the identification code so that the longitudinal display size of the identification code fits within the size of the display range of the display unit in a direction perpendicular to the longitudinal direction.

4. The payment application program according to claim 2 , wherein the display control unit reduces the display size of the identification code so that the display size is not smaller than the size of the identification code in an initial state.

5. The payment application program according to claim 1 , wherein the display control unit enlarges or reduces the display size of the identification code by enlarging or reducing the display size of the entire screen on which the identification code is displayed.

6. A payment application program that is pre-installed in a terminal device used by a user of electronic payment to use an electronic payment using an identification code, the terminal device comprising: a display control unit that causes a display unit of the terminal device to display the identification code; a reception unit that receives an operation by the user on the terminal device, The display control unit is When the reception unit receives a specific operation, the display size of the identification code is enlarged or reduced in accordance with the specific operation; the specific operation is a pinch out operation or a pinch in operation, When the pinch out operation is received, the display control unit increases a display size of the identification code, When the pinch-in operation is received, the display control unit reduces a display size of the identification code, the display control unit enlarges or reduces a display size of a first area, which is an area including the identification code within a screen on which the identification code is displayed, to enlarge or reduce the identification code; The payment application program, characterized in that the display control unit maintains the display size of a second area, which is an area excluding the first area on the screen on which the identification code is displayed.

7. The payment application program according to claim 6 , wherein the display control unit enlarges or reduces a display size of the first area so that the first area fits within a display range of the display unit.

8. The payment application program described in claim 6, characterized in that the display control unit enlarges the display size of the first area so that the longitudinal display size of the first area fits within the size of the display range of the display unit in a direction perpendicular to the longitudinal direction.

9. The payment application program according to claim 6 , wherein the display control unit reduces the display size of the first area so that the display size does not fall below a display size of the first area in an initial state.

10. The payment application program according to claim 6 , wherein the reception unit receives the specific operation while the identification code is displayed on a top screen that is displayed immediately after the payment application program is started.

11. 11. The payment application program according to claim 10, wherein the top screen displays an operation button for transitioning to a payment screen on which the identification code is displayed in an enlarged scale.

12. A payment application program that is pre-installed in a terminal device used by a user of electronic payment to use an electronic payment using an identification code, the terminal device comprising: a display control unit that causes a display unit of the terminal device to display the identification code; a reception unit that receives an operation by the user on the terminal device, The display control unit is When the reception unit receives a specific operation, the display size of the identification code is enlarged or reduced in accordance with the specific operation; the specific operation is a pinch out operation or a pinch in operation, When the pinch out operation is received, the display control unit increases a display size of the identification code, When the pinch-in operation is received, the display control unit reduces a display size of the identification code, When the reception unit receives a second operation different from the specific operation, the identification code or a region including the identification code is changed to an active state; A payment application program characterized in that when the reception unit receives the specific operation in the active state, the display control unit enlarges or reduces the display size of the identification code or an area including the identification code in response to the specific operation.

13. The payment application program as described in claim 12, characterized in that the second operation is a long press operation on the identification code or an area including the identification code.

14. The payment application program according to claim 12 , wherein in the active state, the display control unit causes the identification code or an area including the identification code to be hovered over.

15. When the reception unit receives a second operation different from the specific operation, the identification code or a region including the identification code is changed to the active state, The payment application program according to claim 12, characterized in that when the reception unit receives the specific operation on the screen on which the identification code is displayed, the display control unit enlarges or reduces the display size of the entire screen in response to the specific operation.

16. The payment application program described in Claim 12, characterized in that the reception unit accepts the specific operation while the identification code is displayed on a top screen that is displayed immediately after the payment application program is launched.

17. A payment application program as described in claim 16, characterized in that the top screen displays an operation button for transitioning to a payment screen on which the identification code is displayed in an enlarged manner.

18. The payment application program described in Claim 12, characterized in that the display control unit enlarges or reduces the display size of the identification code so that the identification code fits within the display range of the display unit.

19. The payment application program described in Claim 18, characterized in that the display control unit enlarges the display size of the identification code so that the longitudinal display size of the identification code fits within the size of the display range of the display unit in a direction perpendicular to the longitudinal direction.

20. The payment application program as described in Claim 18, characterized in that the display control unit reduces the display size of the identification code so that it is not smaller than the size of the identification code in its initial state.

21. The payment application program described in Claim 12, characterized in that the display control unit enlarges or reduces the identification code by enlarging or reducing the display size of a first area, which is an area containing the identification code within the screen on which the identification code is displayed.

22. The payment application program as described in Claim 21, characterized in that the display control unit maintains the display size of a second area, which is an area on the screen excluding the first area.

23. The payment application program described in Claim 12, characterized in that the display control unit enlarges or reduces the display size of the identification code by enlarging or reducing the display size of the entire screen on which the identification code is displayed.

24. 13. The payment application program according to claim 1, wherein the display control unit increases or decreases a display size of the identification code on a screen on which the identification code is displayed.

25. 13. The payment application program according to claim 1, wherein the display control unit adjusts the brightness of a screen in accordance with a display size of the identification code.

26. A payment application program as described in any one of claims 1, 6 and 12, characterized in that the reception unit accepts the specific operation when the specific operation is performed on a first area, which is an area including the identification code within the screen on which the identification code is displayed, and also accepts the specific operation when the specific operation is performed on an area within the first area in which the identification code is not displayed.

27. ​​A payment application program as described in any one of claims 1, 6 and 12, characterized in that the reception unit accepts the specific operation when the specific operation is performed across the inside and outside of a first area, which is an area including the identification code within the screen on which the identification code is displayed.

28. A payment application program as described in any one of claims 1, 6 and 12, characterized in that the reception unit accepts the specific operation when the specific operation is performed outside a first area, which is an area including the identification code within a screen on which the identification code is displayed.

29. A payment application program described in any one of claims 1, 6, and 12, characterized in that the display control unit changes the display size of the identification code in two stages: a minimum size and a maximum size.

30. A payment application program as described in any one of claims 1, 6, and 12, characterized in that the display control unit continuously changes the display size of the identification code within a range from a minimum size to a maximum size in response to the specific operation.

31. A payment application program as described in any one of claims 1, 6 and 12, characterized in that the display control unit maintains the maximum size of a first area, which is an area including the identification code, when the first area reaches its maximum size even if a pinch-out operation is performed.

32. A payment application program as described in any one of claims 1, 6 and 12, characterized in that the display control unit maintains the minimum size even when the pinch-in operation is performed when the first area, which is the area including the identification code, reaches an initial size or a minimum size.

33. A payment application program as described in any one of claims 1, 6, and 12, characterized in that the identification code includes a barcode and a QR code.

34. An information processing device used by a user of electronic payment to use an electronic payment using an identification code, a display control unit that causes a display unit of the information processing device to display the identification code; a reception unit that receives an operation by the user on the information processing device, The display control unit is When the reception unit receives a specific operation, the display size of the identification code is enlarged or reduced in accordance with the specific operation; the specific operation is a pinch out operation or a pinch in operation, When the pinch out operation is received, the display control unit increases a display size of the identification code, When the pinch-in operation is received, the display control unit reduces a display size of the identification code, the accepting unit accepts the specific operation while the identification code is displayed on a top screen that is displayed immediately after a payment application program is started, An operation button for transitioning to a payment screen on which the identification code is displayed in an enlarged manner is displayed on the top screen.

23. An information processing apparatus comprising:

35. An information processing method executed by a computer of an information processing device used by a user of electronic payment to utilize an electronic payment using an identification code, comprising: displaying the identification code on a display unit of the information processing device; receiving an operation by the user on the information processing device; and when a specific operation is received, enlarging or reducing a display size of the displayed identification code in accordance with the specific operation, the specific operation is a pinch out operation or a pinch in operation, When the pinch out operation is received, a display size of the identification code is enlarged; When the pinch-in operation is received, a display size of the identification code is reduced; accepting the specific operation while the identification code is displayed on a top screen that is displayed immediately after the start of a payment application program; The information processing method according to the present invention, characterized in that an operation button for transitioning to a payment screen on which the identification code is displayed in an enlarged scale is displayed on the top screen.

Citation Information

Patent Citations

  • Program, display method, and information processing device

    JP2020042634A

  • Electronic settlement system, settlement management apparatus, card, electronic settlement method, and program

    JP2023094452A

  • Determination system, determination method, and program

    JP2023127458A

  • JPP7437644B

  • Image display system, image display method, image display program, and computer-readable recording medium storing said program

    WO2013161104A1

Cited By

  • Application programs and payment systems

    JP7863670B1