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

Abstract

The aim is to improve the usability of payment applications installed on user terminals in electronic payment services. [Solution] The payment application program is a payment application program that is pre-installed on a terminal device used by a user of electronic payment in order to use electronic payment using an identification code, and is characterized by comprising: a detection unit that detects when the user shakes the terminal device; and a display control unit that, when the detection unit detects the shaking motion, transitions the screen displayed on the display unit of the terminal device to the payment screen used for electronic payment.

Description

Technical Field

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

Background Art

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

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

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

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

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

[0007] A payment application program according to one aspect of the present disclosure is a payment application program that is pre-installed on a terminal device used by a user of electronic payment to use electronic payment using an identification code, and is characterized by comprising: a detection unit that detects the user shaking the terminal device; and a display control unit that, when the detection unit detects the shaking motion, transitions the screen displayed on the display unit of the terminal device to a payment screen used for electronic payment. [Effects of the Invention]

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

[0009] [Figure 1] This diagram shows an overview of this disclosure. [Figure 2] This is a diagram showing an example of the system configuration of an electronic payment system. [Figure 3] This is a diagram showing an example of a screen used for electronic payments. [Figure 4] Block diagram showing an example of a user terminal hardware configuration. [Figure 5] This figure shows an example of the software configuration of a user terminal. [Figure 6] This figure shows an example of screen transitions in the first embodiment. [Figure 7] This figure shows an example of screen transitions in the first embodiment. [Figure 8] This flowchart shows the flow of the display control process in the first embodiment. [Figure 9] This figure shows an example of screen transitions in the second embodiment. [Figure 10] This figure shows an example of screen transitions in the third embodiment. [Figure 11] This flowchart shows the flow of the display control process in the third embodiment. [Figure 12] This figure shows an example of screen transitions in the fourth embodiment. [Figure 13] This is a flowchart showing the flow of the display control process in the fourth embodiment. [Figure 14] This is a flowchart showing the flow of the setting process in the fifth embodiment. [Figure 15] This figure shows an example of a settings screen in the fifth embodiment. [Modes for carrying out the invention]

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

[0011] FIG. 1 is a diagram showing an overview of the present disclosure. A settlement application according to an embodiment of the present disclosure is a program pre-installed on a terminal device (hereinafter referred to as a user terminal) used by a user of electronic settlement to utilize electronic settlement using an identification code. The settlement application includes a detection unit that detects an operation of the user shaking the user terminal, and a display control unit that, when the detection unit detects the shaking operation, causes the screen displayed on the display unit of the user terminal to transition to a settlement screen used for electronic settlement.

[0012] The shaking operation is a form of operation of the user terminal and is an operation in which the user intentionally shakes the user terminal. In this specification, the shaking operation is referred to as a shaking action.

[0013] According to the present disclosure, the settlement screen can be displayed on the user terminal by the shaking action. Therefore, the operability of the settlement application is improved.

[0014] The settlement screen may be a first settlement screen including a user code in which the user's identification information is encoded, or a second settlement screen for reading a store code in which the store's identification information is encoded. Alternatively, the display control unit may switch between the first settlement screen and the second settlement screen each time the detection unit detects the shaking action as the settlement screen.

[0015] Although details will be described later, there are a first method and a second method for the payment method using the settlement application. The first method is a method in which a store staff reads a user identification code in which the user's identification information is encoded using a code reader of a store terminal. The second method is a method in which a store identification code in which the identification information of a store posted in a store or the like is encoded is scanned by a user terminal and the payment amount is input. In the following description, the first method is also referred to as store scan, and the second method is also referred to as user scan. The first settlement screen is a settlement screen used in the first method and is also referred to as a payment screen 103 in this specification. The second settlement screen is a settlement screen used in the second method and is also referred to as a scan screen 104 in this specification.

[0016] Figure 1(a) shows an example of the top screen 101 that is displayed on the user's terminal immediately after launching the payment app. When the top screen 101 is displayed, if the user performs a "shake action SH" by shaking the user's terminal, the screen transitions to Figure 1(b).

[0017] Figure 1(b) shows the state after transitioning to the payment screen 103, which is the payment screen that is reached when the user performs an action SH. On the payment screen 103, a one-dimensional code such as a barcode or a two-dimensional code such as a QR code (registered trademark) is displayed as the user code. If the user performs another action SH while the payment screen 103 is displayed, the screen transitions to the scan screen 104 shown in Figure 1(c).

[0018] Furthermore, if a user performs a shake action SH while a payment screen such as the payment screen 103 or the scan screen 104 is displayed, the display control unit transitions to the screen that was displayed on the display unit before the payment screen was displayed. In the example in Figure 1, the screen that was displayed before the payment screen was displayed was the top screen 101, so the system transitions to the top screen 101. This allows the system to transition from the payment screen back to the original screen via the shake action SH.

[0019] Note that the screen displayed in the display area before the payment screen is shown is not limited to the top screen 101, but may also be screens displayed in various functions included in the payment app. In this specification, the various functions included in the payment app are referred to as mini-apps. Mini-apps include functions such as money transfer, points, transaction history display, charge, coupon, utility bill payment, stamp card, shopping, finance, and other functions. These mini-app screens can conventionally be accessed from various buttons displayed on the top screen 101.

[0020] If the screen displayed on the display unit before the payment screen was displayed was a mini-app screen, and the user performs an action SH while the payment screen is displayed, the display control unit will transition to the mini-app screen.

[0021] Alternatively, if the screen displayed on the display unit before the payment screen was displayed was a mini-app screen, and the user performs an action SH while the payment screen is displayed, the display control unit may transition to the top screen 101. Details of screen transitions will be described later.

[0022] Thus, with the payment app disclosed herein, when a user shakes their device, the display on the screen switches to the payment screen used for electronic payments. Therefore, the screen can be switched with one hand, and the screen can be switched quickly and easily compared to conventional button operations.

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

[0024] In this specification, a user is defined as a person who uses a payment application 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, using the account management function of the payment application. The user's account is managed by the electronic payment server 5 and is linked to the user's identification information and electronic account. The user can access the electronic payment service by installing the payment application 200 on the user terminal 2. The electronic payment service can also be accessed by using a general web browser to access the website provided by the electronic payment server 5.

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

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

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

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

[0029] For reading the identification code during store scanning, the identification code displayed on the top screen 101 shown in Figure 1(a) may be used, or the identification code displayed on the payment screen 103 shown in Figure 1(b) may be used. Figure 3(a) is a diagram illustrating the payment screen 103. The payment screen 103 is displayed on the display unit 206 of the user terminal 2 when the user taps the payment button 109 displayed on the top screen 101 or performs the shake action SH. The payment screen 103 displays the first identification code 311 and the second identification code 312 as user codes that encode the user's identification information. Note that at least one of the first identification code 311 and the second identification code 312 is displayed on the payment screen 103. In the example in Figure 3(a), both are displayed. The payment screen 103 may also display payment-related information such as available amount, charge balance, and points. The payment screen 103 also displays a button 313 that is operated when transitioning to the scan screen 104 used in the user scan described later. To transition from the payment screen 103 to the scan screen 104, you can either operate button 313 or perform the shake action SH. To return from the payment screen 103 to the top screen 101, you can operate button 314. Details of screen transitions will be described later.

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

[0031] For reading the store code image 32 during user scanning, the scan screen 104 shown in Figure 3(b) is used. The user operates the payment app 200 to display the scan screen 104 on the display unit 206 of the user terminal 2, and takes a picture of the store code image 32 displayed in the store so that it fits within the frame 321. The user can transition to the scan screen 104 by tapping the scan button 108 displayed on the top screen 101 shown in Figure 1(a), or by tapping the button 313 displayed on the payment screen 103 shown in Figure 3(a), or by performing the shake action SH. To return from the scan screen 104 to the payment screen 103, the user taps the button 322 on the scan screen 104. To return from the scan screen 104 to the top screen 101, the user can operate the button 314 or perform the shake action SH.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0045] Figure 5(a) is a diagram showing the data stored in the storage unit 204 of the user terminal 2. As shown in Figure 5(a), the storage unit 204 of the user terminal 2 stores the program of the payment application 200, data for various screens displayed in the payment application (hereinafter referred to as screen data 230), user identification information 220 for the electronic payment service, and various setting information 240 for the payment application 200. The identification information 220 is assigned by the electronic payment server 5 when the account is registered. The setting information 240 includes various setting information related to the functions of the payment application 200. For example, it stores setting information on whether to enable or disable the shake action SH, and setting information on the screen transition order by the shake action SH. The screen data 230 includes screen data for the top screen 101, payment screen 103, and scan screen 104 as described above, as well as screen data for mini-applications, screen data for the amount input screen and payment completion screen displayed during payment processing, and screen data for various error notification screens.

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

[0047] The payment app 200 has various functions in addition to payment processing functions for making electronic payments in electronic payment services. For example, it includes a money transfer function, a points function, a transaction history display function, a charge function, a coupon function, a utility bill payment function, a stamp card function, a shopping function, a finance function, an information content distribution function, a My Page function for managing user account information, and other functions. In the following description, functions other than the payment processing function in the payment app 200 are collectively referred to as mini-apps. The payment app 200 also has a display control function to control the display of the screen, an action detection function to detect the shake action SH, a setting function that accepts various settings from the user, such as whether to enable or disable the action detection function and the order of screen transitions.

[0048] Figure 5(b) shows the configuration of the program modules of the payment application 200. As shown in Figure 5(b), the payment application 200 of this embodiment has a payment processing unit 501, an action detection unit 502, a display control unit 503, and a setting unit 504 as program modules. Although not shown, the payment application 200 also has various program modules and data related to the mini-application.

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

[0050] The action detection unit 502 detects the shaking action SH performed by the user on the user terminal 2. That is, when the user performs a shaking action SH, the vibration detection unit 212, which is composed of a gyro sensor or the like, detects it, and the detection signal is input to the CPU 201. The action detection unit 502 detects that a shaking action SH has been performed by acquiring the detection signal input to the CPU 201. The vibration detection unit 212 distinguishes between shaking actions SH performed intentionally by the user and unintentional vibrations. That is, the vibration detection unit 212 distinguishes between shaking actions SH as an operation and vibrations of the user terminal 2 caused by walking or hand tremors. The vibration detection unit 212 detects a shaking action SH, for example, when it detects a vibration amount above a predetermined threshold or a vibration above a predetermined number of times. When the vibration detection unit 212 detects that a shaking action SH has been performed, it inputs a detection signal to the CPU 201 indicating that a shaking action SH has been detected.

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

[0052] In this embodiment, when the action detection unit 502 detects an action SH, the display control unit 503 transitions the screen displayed on the display unit 206 of the user terminal 2 to a payment screen used for electronic payment. The destination payment screen may be a first payment screen (payment screen 103) containing a user code that encodes the user's identification information, or a second payment screen (scan screen 104) for reading a store code that encodes the store's identification information. The display control when the action detection unit 502 detects an action SH will be described in detail below.

[0053] Figure 6 illustrates the first screen transition pattern, and Figure 7 illustrates the second screen transition pattern.

[0054] In the first pattern shown in Figure 6, if the action detection unit 502 detects an action SH while the top screen 101 shown in Figure 6(a) is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the payment screen 103, which is one form of the payment screen. Figure 6(b) shows the destination payment screen 103. If the action detection unit 502 detects an action SH while the payment screen 103 is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the scan screen 104, which is another form of the payment screen. Figure 6(c) shows the destination scan screen 104. If the action detection unit 502 detects an action SH while the scan screen 104 is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the screen before the payment screen was displayed, i.e., the top screen 101. The system returns to the state shown in Figure 6(a).

[0055] In the second pattern shown in Figure 7, when the action detection unit 502 detects an action SH while the top screen 101 is displayed as shown in Figure 7(a), the display control unit 503 transitions the screen displayed on the display unit 206 to the scan screen 104. Figure 7(b) shows the destination scan screen 104. If the action detection unit 502 detects an action SH while the scan screen 104 is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the payment screen 103. Figure 7(c) shows the destination payment screen 103. If the action detection unit 502 detects an action SH while the payment screen 103 is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the screen before the payment screen was displayed, i.e., the top screen 101. The state returns to Figure 7(a).

[0056] Whether the display control unit 503 performs the screen transition using the first pattern or the second pattern described above is predetermined and stored in the storage unit 204 as setting information 240 for the payment application 200. Alternatively, the user may set this in the setting unit 504, and this setting information 240 may be stored in the storage unit 204.

[0057] (Display control processing) The flow of the display control process in this embodiment will be explained with reference to Figure 8. The flowchart shown in Figure 8(a) corresponds to the first screen transition pattern shown in Figure 6, and the flowchart shown in Figure 8(b) corresponds to the second screen transition pattern shown in Figure 7. The processes shown in these flowcharts are written in the program of the payment application 200 installed on the user terminal 2. The program is stored in the memory unit 204, called by the CPU 201, loaded into RAM 203, and executed. The CPU 201 obtains information on the screen transition pattern set in the setting information 240 stored in the memory unit 204, and based on the obtained information, calls and executes either the flowchart in Figure 8(a) or the flowchart in Figure 8(b). When the user operates the startup icon of the payment application 200 and the payment application 200 is started, the CPU 201 starts this process. In the following explanation, the symbol "S" means step.

[0058] The flowchart shown in Figure 8(a) will be explained. In S801, the CPU 201 first obtains screen data of the top screen 101 of the payment application 200 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 6(a). The top screen 101 is provided with a code display area 604, a menu area 605, a function selection area 606, a balance display area 607, a fixed display area 608, etc. The fixed display area 608 displays a payment button 109. Inside the code display area 604, a first identification code 601 and a second identification code 602 are displayed as user codes that encode the user's identification information. In addition, payment method and balance information may be displayed inside the code display area 604. Campaign information 610 and notification icons 611 are displayed in the upper area of ​​the code display area 604. In addition, operation buttons such as a credit payment button 612, which are operated when transitioning to the credit payment screen, may be displayed in the right-hand area of ​​the code display area 604.

[0059] If the vibration detection unit 212 detects the shaking action SH in S802 and the CPU 201 acquires the detection signal (S802; YES), the process proceeds to S803.

[0060] In S803, the CPU 201 transitions the screen to be displayed on the display unit 206 to the payment screen 103. That is, the CPU 201 obtains the screen data for the payment screen 103 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 6(b). With the payment screen 103 displayed, the store terminal 3 may read the user code using the code reader 31 and perform the payment processing. In that case, the CPU 201 sends and receives information with the store terminal 3 according to the store scan payment processing procedure described above, and displays the payment completion screen (not shown) etc. in accordance with the payment completion notification sent from the electronic payment server 5.

[0061] If, while the payment screen 103 is displayed, the vibration detection unit 212 detects a shaking action SH in S804 and the CPU 201 acquires the detection signal (S804; YES), the process proceeds to S805.

[0062] In S805, the CPU 201 transitions the screen to be displayed on the display unit 206 to the scan screen 104. That is, the CPU 201 acquires the screen data of the scan screen 104 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 6(c). With the scan screen 104 displayed, the CPU 201 activates the camera 209 and makes it possible to read the store code posted in the store. When the store code is read by the scan screen 104 and payment processing is started, the CPU 201 sends and receives information with the electronic payment server 5 according to the user scan payment processing procedure described above, and displays the amount input screen and payment completion screen, etc.

[0063] If, while the scan screen 104 is displayed, the vibration detection unit 212 detects a shaking action SH in S806 and the CPU 201 acquires the detection signal (S806; YES), the process proceeds to S801. That is, the CPU 201 transitions the screen to be displayed on the display unit 206 to the top screen 101 shown in Figure 1. Subsequently, the processes from S802 to S806 are repeated.

[0064] In S802, S804, and S806, if no shake action SH is detected after a predetermined time has elapsed, this flowchart will be terminated while maintaining the displayed screen.

[0065] The flowchart shown in Figure 8(b) will now be explained. In S811, the CPU 201 first obtains the screen data of the top screen 101 of the payment application 200 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 7(a). The processing in S811 is the same as in S801 described above. The content displayed on the top screen 101 is also the same as in Figure 6(a).

[0066] If the vibration detection unit 212 detects the shaking action SH in S812 and the CPU 201 acquires the detection signal (S812; YES), the process proceeds to S813.

[0067] In S813, the CPU 201 transitions the screen to be displayed on the display unit 206 to the scan screen 104. That is, the CPU 201 acquires the screen data of the scan screen 104 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 7(b). With the scan screen 104 displayed, the CPU 201 activates the camera 209 and makes it possible to read the store code posted in the store. When the store code is read by the scan screen 104 and payment processing is started, the CPU 201 sends and receives information with the electronic payment server 5 according to the user scan payment processing procedure described above, and displays the amount input screen, payment completion screen, etc.

[0068] If, while the scan screen 104 is displayed, the vibration detection unit 212 detects a shaking action SH in S814 and the CPU 201 acquires the detection signal (S814; YES), the process proceeds to S815.

[0069] In S815, the CPU 201 transitions the screen to be displayed on the display unit 206 to the payment screen 103. That is, the CPU 201 obtains the screen data for the payment screen 103 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 7(c). Note that while the payment screen 103 is displayed, the store terminal 3's code reader 31 may read the user code and perform the payment processing. In that case, the CPU 201 sends and receives information with the store terminal 3 according to the store scan payment processing procedure described above, and displays the payment completion screen (not shown) etc. in accordance with the payment completion notification sent from the electronic payment server 5.

[0070] When the payment screen 103 is displayed, if the vibration detection unit 212 detects a shaking action SH in S816 and the CPU 201 acquires the detection signal (S816; YES), the process proceeds to S811. That is, the CPU 201 transitions the screen to be displayed on the display unit 206 to the top screen 101 shown in Figure 1. Subsequently, the processes from S812 to S816 are repeated.

[0071] In steps S812, S814, and S816, if no shake action SH is detected after a predetermined time has elapsed, this flowchart will be terminated while maintaining the displayed screen.

[0072] As explained above, according to the payment application 200 of the first embodiment, when the user performs a shake action SH on the user terminal 2, the application can transition to a payment screen such as the payment screen 103 or the scan screen 104. Furthermore, if the user performs a shake action SH while the payment screen is displayed, the application can return to the top screen 101 that was displayed before the payment screen was displayed. Therefore, the application can easily transition to the payment screen with one-handed operation and return to the original screen from the payment screen, improving usability.

[0073] In the first embodiment, we described an example in which payment processing is performed on the payment screen 103 or scan screen 104, which is the destination, and a payment completion screen is displayed when the payment processing is completed. However, if the payment processing is not completed, the user may be redirected to an error notification screen that notifies the user of an error.

[0074] <Second Embodiment> Next, a second embodiment of this disclosure will be described. In the second embodiment, an example in which the display state of the payment screen 103 is set to horizontal display will be described. Horizontal display will be described later. Note that the configuration of the payment application 200, the user terminal 2, the store terminal 3, and the electronic payment server 5 in the second embodiment are the same as in the first embodiment, so redundant explanations will be omitted and the same parts will be denoted by the same reference numerals.

[0075] Figure 9 illustrates the screen transitions of the payment application 200 in the second embodiment. In the second embodiment, as shown in Figure 9(a), the top screen 101 is displayed, and the user terminal 2 performs a shake action SH. When the action detection unit 502 detects the shake action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to a horizontal payment screen 900, which is one form of the payment screen. Figure 9(b) shows the horizontal payment screen 900, which is the destination of the transition.

[0076] The horizontal payment screen 900 is a screen that displays the payment screen, including the user code, with the longitudinal direction of the display range of the display unit 206 being the horizontal direction. In the figure, the horizontal direction is represented as the left-right direction. On the horizontal payment screen 900, as shown in Figure 9(b), either one or both of the user code, namely the first identification code 911 (a one-dimensional code) and the second identification code 912 (a two-dimensional code), are displayed. In the example in Figure 9(b), both are displayed. In this horizontal payment screen 900, the longitudinal direction of the first identification code 911, which is the user code, is displayed so that it coincides with the longitudinal direction of the display range of the display unit 206. The display range of the display unit 206 is the entire area of ​​the display unit 206, i.e., the area corresponding to the display size. This display state is called horizontal display. In the normal payment screen 103 shown in Figure 3(a), the longitudinal direction of the first identification code 911, which is the user code, is displayed so that it coincides with the direction perpendicular to the longitudinal direction of the display range of the display unit 206. This display state is called vertical display.

[0077] In the example of the horizontal payment screen 900 shown in Figure 9(b), the user code is displayed enlarged compared to the normal payment screen 103 shown in Figure 3(a). Preferably, the user code is displayed at a size that maximizes it within the display range of the display unit 206. Specifically, the enlargement is such that the longitudinal size of the first identification code 911 fits within the longitudinal size of the display range of the display unit 206, and the maximum vertical size when the first identification code 911 and the second identification code 912 are placed vertically fits within the size in the direction perpendicular to the longitudinal direction of the display range. The aspect ratio of the enlarged user code maintains the aspect ratio of the user code displayed on the normal payment screen 103. It is also enlarged while being positioned within the screen to include appropriate margins. Note that the user code does not necessarily need to be displayed enlarged; it may be the same display size as the user code on the normal payment screen 103, or it may be any size. However, regardless of the display size, the aspect ratio of the user code displayed on the horizontal payment screen 900 shall be the same as the aspect ratio of the user code displayed on the regular payment screen 103. In addition, information such as available amount, charge balance, and points may be displayed on the horizontal payment screen 900, just as on the regular payment screen 103.

[0078] If the action detection unit 502 detects an action SH while the horizontal payment screen 900 is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the scan screen 104, which is another form of the payment screen. Figure 9(c) shows the destination scan screen 104. If the action detection unit 502 detects an action SH while the scan screen 104 is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the screen before the payment screen was displayed, i.e., the top screen 101, returning to the state shown in Figure 9(a).

[0079] Furthermore, when the payment screen is to be displayed horizontally, this setting is predetermined and stored in the storage unit 204 as setting information 240. Based on the setting information 240, the CPU 201 decides whether to display the payment screen horizontally or vertically.

[0080] (Display control processing) The display control process in the second embodiment is performed using the same processing procedure as the flowchart in Figure 8(a). However, in S803, the CPU 201 displays the horizontal payment screen 900 shown in Figure 9(b) instead of the normal payment screen 103.

[0081] <Modification 1 of the second embodiment> The display control process in the second embodiment may follow the same processing procedure as the flowchart in Figure 8(b). In that case, at S815, the CPU 201 displays the horizontal payment screen 900 shown in Figure 9(b) instead of the normal payment screen 103. When the display control process in the second embodiment is executed using the processing procedure of the flowchart in Figure 8(b), the following screen transitions occur.

[0082] First, as shown in Figure 9(a), with the top screen 101 displayed, the user terminal 2 performs a shake action SH. When the action detection unit 502 detects the shake action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to the scan screen 104 shown in Figure 9(c). When the scan screen 104 is displayed, the action detection unit 502 detects the shake action SH, and the display control unit 503 transitions the screen displayed on the display unit 206 to the horizontal payment screen 900 shown in Figure 9(b). When the horizontal payment screen 900 is displayed, the action detection unit 502 detects the shake action SH, and the display control unit 503 transitions the screen displayed on the display unit 206 to the screen before the payment screen was displayed, i.e., the top screen 101, returning to the state shown in Figure 9(a).

[0083] <Modification 2 of the second embodiment> The display control unit 503 may switch the display state of the first payment screen between horizontal and vertical display each time it detects an action SH transmitted by the action detection unit 502. In this case, the screen transition will be as follows.

[0084] First, as shown in Figure 9(a), with the top screen 101 displayed, the user terminal 2 performs a shake action SH. When the action detection unit 502 detects the shake action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to the horizontal payment screen 900 (horizontal display) shown in Figure 9(b). When the horizontal payment screen 900 is displayed, the action detection unit 502 detects the shake action SH, and the display control unit 503 transitions the screen displayed on the display unit 206 to the normal payment screen 103 (vertical display) shown in Figure 3(c). When the normal payment screen 103 shown in Figure 3(c) is displayed, the action detection unit 502 detects the shake action SH, and the display control unit 503 transitions the screen displayed on the display unit 206 to the screen before the payment screen was displayed, i.e., the top screen 101, returning to the state shown in Figure 9(a).

[0085] <Modification 3 of the second embodiment> If the top screen 101 is displayed and the shake action SH is detected, the display control unit 503 may transition to the horizontal payment screen 900 (horizontal display) shown in Figure 9(b). If the shake action SH is detected while the horizontal payment screen 900 is displayed, the display control unit 503 transitions to the normal payment screen 103 (vertical display) shown in Figure 3(c). Then, if the shake action SH is detected while the normal payment screen 103 shown in Figure 3(c) is displayed, the display control unit 503 may transition to the scan screen 104 shown in Figure 9(c). After that, if the shake action SH is detected while the scan screen 104 is displayed, the display control unit 503 may transition to the top screen 101 and return to the state shown in Figure 9(a).

[0086] <Modification 4 of the second embodiment> In cases where the scan screen 104 is displayed first and the horizontal payment screen 900 is displayed later based on the shake action SH, if the shake action SH is detected while the horizontal payment screen 900 is displayed, the display control unit 503 may transition to the normal payment screen 103 shown in Figure 3(c). Subsequently, if the shake action SH is detected while the normal payment screen 103 shown in Figure 3(c) is displayed, the display control unit 503 may transition to the top screen 101 and return to the state shown in Figure 9(a).

[0087] As explained above, according to the payment application 200 of the second embodiment, the payment screen to which the user transitions when the user performs the shake action SH on the user terminal 2 can be a horizontal payment screen 900. Furthermore, if the shake action SH is performed while the horizontal payment screen 900 is displayed, the user can transition to a vertical payment screen 103. Furthermore, if the shake action SH is performed while the vertical payment screen 103 is displayed, the user can transition to the horizontal payment screen 900.

[0088] Furthermore, the order of screen transitions in the second embodiment and the modified example may be set by the user. Also, the order of screen transitions is arbitrary; for example, the first cycle may be the screen transitions of the second embodiment (Figure 9), and the second cycle may be the screen transitions of modified example 1.

[0089] <Third Embodiment> Next, a third embodiment of this disclosure will be described. In the first and second embodiments, an example was described in which the shake action SH is performed on the top screen 101 of the payment application 200. In the third embodiment, a case will be described in which the screen before transitioning to the payment screen is not the top screen 101, but a mini-application screen. Note that the configuration of the payment application 200, the user terminal 2, the store terminal 3, and the electronic payment server 5 in the third embodiment are the same as in the first embodiment, so redundant explanations will be omitted, and the same parts will be denoted by the same reference numerals.

[0090] Figure 10 is a diagram illustrating the screen transitions by the payment application 200 of the third embodiment. In the third embodiment, the coupon application screen is shown as an example of the mini-application screen 1000. With the mini-application screen 1000 displayed in this state, the user terminal 2 performs a shake action SH. When the action detection unit 502 detects the shake action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to the payment screen 103, which is one form of the payment screen. Figure 10(b) shows the payment screen 103, which is the destination. The payment screen 103 may be a normal payment screen 103, as described in the first embodiment, or it may be a horizontal payment screen 900, as described in the second embodiment. Figure 10(b) shows an example where a normal payment screen 103 is displayed.

[0091] If the action detection unit 502 detects the shake action SH while the payment screen 103 is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the scan screen 104, which is another form of the payment screen. Figure 10(c) shows the destination scan screen 104. If the action detection unit 502 detects the shake action SH while the scan screen 104 is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the screen that was displayed before the payment screen 103 was displayed, i.e., the coupon screen. Figure 10(d) shows the destination coupon screen. Thus, in this third embodiment, the user can transition to the payment screen by shaking the action SH even from the mini-app screen. Furthermore, the user can transition back to the original mini-app screen by shaking the action SH from the payment screen.

[0092] (Display control processing) Next, the display control process in the third embodiment will be described with reference to Figure 11. Figure 11 is a flowchart showing the flow of the display control process in the third embodiment. The process shown in the flowchart of Figure 11 is written in the program of the payment application 200 installed on the user terminal 2. The program is stored in the storage unit 204, called by the CPU 201, loaded into the RAM 203, and executed.

[0093] On the top screen 101 displayed after launching the payment app 200, if a user operates a button for any function (mini-app), the process transitions to the corresponding mini-app. Upon transitioning to the mini-app's processing, the CPU 201 begins the process shown in this flowchart.

[0094] In S1101, the CPU 201 obtains screen data for the mini-application screen 1000 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 10(a). As described above, the mini-application screen 1000 shown in Figure 10(a) is an example of the screen displayed when the coupon application is launched. Note that the mini-application screen 1000 is not limited to the coupon application screen, but may also be screens for other various functions included in the payment application 200.

[0095] If the vibration detection unit 212 detects a shaking action SH in S1102 and the CPU 201 acquires the detection signal (S1102; YES), the process proceeds to S1103.

[0096] In S1103, the CPU 201 transitions the screen to be displayed on the display unit 206 to the payment screen 103. That is, the CPU 201 obtains the screen data for the payment screen 103 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 10(b). With the payment screen 103 displayed, the store terminal 3 may read the user code using the code reader 31 and perform the payment processing. In that case, the CPU 201 sends and receives information with the store terminal 3 according to the store scan payment processing procedure described above, and displays the payment completion screen (not shown) etc. in accordance with the payment completion notification sent from the electronic payment server 5.

[0097] If, while the payment screen 103 is displayed, the vibration detection unit 212 detects a shaking action SH in S1104 and the CPU 201 acquires the detection signal (S1104; YES), the process proceeds to S1105.

[0098] In S1105, the CPU 201 transitions the screen to be displayed on the display unit 206 to the scan screen 104. That is, the CPU 201 acquires the screen data of the scan screen 104 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 10(c). When the scan screen 104 is displayed, the CPU 201 activates the camera 209 and makes it possible to read the store code posted in the store. When the store code is read by the scan screen 104 and payment processing is started, the CPU 201 sends and receives information with the electronic payment server 5 according to the user scan payment processing procedure described above, and displays the amount input screen and payment completion screen, etc.

[0099] With the scan screen 104 displayed, if the vibration detection unit 212 detects a shaking action SH in S1106 and the CPU 201 acquires the detection signal (S1106; YES), the process proceeds to S1101. That is, the CPU 201 transitions the screen to be displayed on the display unit 206 to the mini-application screen 1000 shown in Figure 1. Subsequently, the processes from S1102 to S1106 are repeated.

[0100] In steps S1102, S1104, and S1106, if no shake action SH is detected after a predetermined time has elapsed, this flowchart will be terminated while maintaining the displayed screen.

[0101] <Modification 1 of the third embodiment> In the display control processing of the third embodiment, the display order of the payment screen may be transitioned so that the scan screen 104 is displayed first and the payment screen 103 is displayed second. That is, first, as shown in Figure 10(a), the mini-application screen 1000 is displayed, and the user terminal 2 performs a shake action SH. When the action detection unit 502 detects the shake action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to the scan screen 104 shown in Figure 10(c). When the scan screen 104 is displayed, the action detection unit 502 detects the shake action SH, and the display control unit 503 transitions the screen displayed on the display unit 206 to the payment screen 103 shown in Figure 10(b). When the payment screen 103 is displayed, the action detection unit 502 detects the shake action SH, and the display control unit 503 transitions the screen displayed on the display unit 206 to the screen before the payment screen was displayed, i.e., the mini-application screen 1000, and returns to the state in Figure 10(a).

[0102] In this case, the processing flow is the same as swapping steps S1103 and S1105 in the flowchart of Figure 11.

[0103] <Modification 2 of the third embodiment> Furthermore, in the third embodiment, the payment screen 103 to which the user transitions via the shake action SH may be replaced with the horizontal payment screen 900 shown in Figure 9(b) instead of the normal payment screen 103. That is, each time the shake action SH is performed from the mini-app screen 1000, the user may transition in the following order: horizontal payment screen 900, scan screen 104, and back to the mini-app screen 1000. Alternatively, each time the shake action SH is performed from the mini-app screen 1000, the user may transition in the following order: scan screen 104, horizontal payment screen 900, and back to the mini-app screen 1000.

[0104] <Modification 3 of the third embodiment> In the third embodiment, if the payment screen 103 to which the shake action SH is performed is the horizontal payment screen 900 shown in Figure 9(b), the horizontal payment screen 900 and the normal payment screen 103 may be switched each time the shake action SH is performed. That is, each time the shake action SH is performed, the screens may transition in the following order: mini-app screen 1000, horizontal payment screen 900, normal payment screen 103, scan screen 104, mini-app screen 1000. Alternatively, each time the shake action SH is performed, the screens may transition in the following order: mini-app screen 1000, scan screen 104, horizontal payment screen 900, normal payment screen 103, mini-app screen 1000. Furthermore, in these examples, the transition order between the horizontal payment screen 900 (horizontal display) and the normal payment screen 103 (vertical display) may be reversed.

[0105] As explained above, with the payment app 200 of the third embodiment, the user can transition from the mini-app screen to a payment screen such as the payment screen 103 or the scan screen 104 by performing the shake action SH. Therefore, the user can easily transition to the payment screen with just one hand, improving usability. In particular, the mini-app screen often does not display the payment button 109 or scan button 108 that are displayed on the top screen 101 of the payment app 200. Therefore, conventionally, if a user wanted to transition from the mini-app screen to the payment screen, they had to return to the top screen 101 and operate the payment button 109 or scan button 108. On the other hand, with the payment app 200 of the third embodiment, the user can transition to the payment screen simply by performing the shake action SH while the mini-app screen is displayed. Therefore, the usability of the payment app is improved. In addition, the user can return to the original mini-app screen before the payment screen was displayed by performing the shake action SH on the payment screen, making the screen transition from the payment screen to the mini-app smoother.

[0106] Furthermore, the order of screen transitions in the third embodiment and the modified examples may be set by the user. Also, the order of screen transitions is arbitrary; for example, the first round may be the screen transitions of the third embodiment, and the second round may be the screen transitions of modified example 1.

[0107] <Fourth Embodiment> Next, a fourth embodiment of this disclosure will be described. In the third embodiment, an example was described in which, when the shake action SH is performed on the screen of the mini-app of the payment app 200, the user transitions to the payment screen, and then returns to the mini-app screen by the shake action SH. In the fourth embodiment, an example will be described in which, when the screen before transitioning to the payment screen is the screen of the mini-app, the user transitions to the payment screen, and then returns to the top screen 101 by the subsequent shake action SH. Note that the configuration of the payment app 200, the user terminal 2, the store terminal 3, and the electronic payment server 5 in the fourth embodiment are the same as in the first embodiment, so redundant explanations will be omitted, and the same parts will be denoted by the same reference numerals.

[0108] Figure 12 is a diagram illustrating the screen transitions by the payment application 200 of the fourth embodiment. As shown in Figure 12(a), in the fourth embodiment, the coupon application screen is shown as an example of the mini-application screen 1000. With the mini-application screen 1000 displayed in this state, the user terminal 2 performs a shake action SH. When the action detection unit 502 detects the shake action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to the payment screen 103, which is one form of the payment screen. Figure 12(b) shows the payment screen 103, which is the destination. The payment screen 103 may be a normal payment screen 103, as described in the first embodiment, or it may be a horizontal payment screen 900, as described in the second embodiment. Figure 12(b) shows an example in which a normal payment screen 103 is displayed.

[0109] If the action detection unit 502 detects a shake action SH while the payment screen 103 is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the scan screen 104, which is another form of the payment screen. Figure 12(c) shows the destination scan screen 104. If the action detection unit 502 detects a shake action SH while the scan screen 104 is displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the top screen 101 of the payment application 200. Figure 12(d) shows the destination top screen 101. Thus, in the fourth embodiment, it is possible to transition to the payment screen by a shake action SH even from the screen 1000 of the mini-application. Furthermore, it is possible to transition to the top screen 101 of the payment application 200 by a shake action SH from the payment screen.

[0110] (Display control processing) Next, the display control process in the fourth embodiment will be described with reference to Figure 13. Figure 13 is a flowchart showing the flow of the display control process in the fourth embodiment. The processes shown in the flowchart of Figure 13 are written in the program of the payment application 200 installed on the user terminal 2. The program is stored in the storage unit 204, called by the CPU 201, loaded into the RAM 203, and executed. Note that steps S1301 to S1306 are the same as steps S1101 to S1106 in Figure 11.

[0111] On the top screen 101 displayed after launching the payment app 200, if a user operates a button for any function (mini-app), the process transitions to the corresponding mini-app. Upon transitioning to the mini-app's processing, the CPU 201 begins the process shown in this flowchart.

[0112] In S1301, the CPU 201 obtains screen data for the mini-application screen 1000 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 12(a). As described above, the mini-application screen 1000 shown in Figure 12(a) is an example of a screen displayed when a coupon application is launched. Note that the mini-application screen 1000 is not limited to the coupon application screen, but may also be screens for various functions included in the payment application 200.

[0113] If the vibration detection unit 212 detects a shaking action SH in S1302 and the CPU 201 acquires the detection signal (S1302; YES), the process proceeds to S1303.

[0114] In S1303, the CPU 201 transitions the screen to be displayed on the display unit 206 to the payment screen 103. That is, the CPU 201 obtains the screen data for the payment screen 103 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 13(b). With the payment screen 103 displayed, the store terminal 3 may read the user code using the code reader 31 and perform the payment processing. In that case, the CPU 201 sends and receives information with the store terminal 3 according to the store scan payment processing procedure described above, and displays the payment completion screen (not shown) etc. in accordance with the payment completion notification sent from the electronic payment server 5.

[0115] If, while the payment screen 103 is displayed, the vibration detection unit 212 detects a shaking action SH in S1304 and the CPU 201 acquires the detection signal (S1304; YES), the process proceeds to S1305.

[0116] In S1305, the CPU 201 transitions the screen to be displayed on the display unit 206 to the scan screen 104. That is, the CPU 201 acquires the screen data of the scan screen 104 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 12(c). When the scan screen 104 is displayed, the CPU 201 activates the camera 209 and makes it possible to read the store code posted in the store. When the store code is read by the scan screen 104 and payment processing is started, the CPU 201 sends and receives information with the electronic payment server 5 according to the user scan payment processing procedure described above, and displays the amount input screen and payment completion screen, etc.

[0117] If, while the scan screen 104 is displayed, the vibration detection unit 212 detects a shaking action SH in S1106 and the CPU 201 acquires the detection signal (S1306; YES), the process proceeds to S1307.

[0118] In S1307, the CPU 201 transitions the screen to be displayed on the display unit 206 to the top screen 101 of the payment application 200. That is, the CPU 201 obtains the screen data of the top screen 101 from the storage unit 204 and displays it on the display unit 206 as shown in Figure 12(d).

[0119] If the system transitions to the top screen 101, or if no shake action SH is detected after a predetermined time has elapsed in S1102, S1104, or S1106, this flowchart will terminate while maintaining the displayed screen.

[0120] If the top screen 101 is displayed, the CPU 201 may accept the action SH performed on the top screen 101, as shown in the first and second embodiments. In that case, the CPU 201 performs the screen transition as described in the first and second embodiments.

[0121] <Modification 1 of the 4th embodiment> In the display control processing of the fourth embodiment, the display order of the payment screens may be transitioned so that the scan screen 104 is displayed first, followed by the payment screen 103. That is, first, as shown in Figure 12(a), the mini-application screen 1000 is displayed, and the user terminal 2 performs a shake action SH. When the action detection unit 502 detects the shake action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to the scan screen 104 shown in Figure 12(c). When the scan screen 104 is displayed, the action detection unit 502 detects the shake action SH, and the display control unit 503 transitions the screen displayed on the display unit 206 to the payment screen 103 shown in Figure 12(b). When the payment screen 103 is displayed, the action detection unit 502 detects the shake action SH, and the display control unit 503 transitions the screen displayed on the display unit 206 to the top screen 101 as shown in Figure 12(d).

[0122] In this case, the processing flow is the same as swapping steps S1303 and S1305 in the flowchart of Figure 13.

[0123] <Modification 2 of the 4th embodiment> Furthermore, in the fourth embodiment, the payment screen 103 to which the user transitions via the shake action SH may be replaced with the horizontal payment screen 900 shown in Figure 9(b) instead of the normal payment screen 103. That is, each time the shake action SH is performed from the mini-app screen 1000, the user may transition in the order of horizontal payment screen 900, scan screen 104, and top screen 101. Alternatively, each time the shake action SH is performed from the mini-app screen 1000, the user may transition in the order of scan screen 104, horizontal payment screen 900, and top screen 101.

[0124] <Modification 3 of the 4th embodiment> In the fourth embodiment, if the payment screen 103 to which the user transitions via the shake action SH is the horizontal payment screen 900 shown in Figure 9(b), the user may switch between the horizontal payment screen 900 and the normal payment screen 103 each time the shake action SH is performed. That is, each time the shake action SH is performed, the user may transition in the following order: mini-app screen 1000, horizontal payment screen 900, normal payment screen 103, scan screen 104, mini-app screen 1000. Alternatively, each time the shake action SH is performed, the user may transition in the following order: mini-app screen 1000, scan screen 104, horizontal payment screen 900, normal payment screen 103, mini-app screen 1000. Furthermore, in these examples, the transition order between the horizontal payment screen 900 (horizontal display) and the normal payment screen 103 (vertical display) may be reversed.

[0125] As explained above, according to the payment application 200 of the fourth embodiment, the user can transition from the mini-application screen 1000 to payment screens such as the payment screen 103 and the scan screen 104 by shaking the device. Therefore, the user can easily transition to the payment screen with just one hand, improving usability. Furthermore, the user can transition from the payment screen to the top screen 101 by shaking the device. From the top screen 101, buttons are displayed that are used to transition to the payment screen, as well as buttons that are used to transition to various mini-application screens, allowing for a smooth transition to the next function to be used.

[0126] Furthermore, the order of screen transitions in the fourth embodiment and the modified example may be set by the user. Also, the order of screen transitions is arbitrary; for example, the first round may be the screen transitions of the fourth embodiment, and the second round may be the screen transitions of modified example 1.

[0127] <Fifth Embodiment> Next, a fifth embodiment of this disclosure will be described. It is preferable that the user can switch between enabling and disabling the Shake Action SH as shown in the first to fourth embodiments. As the fifth embodiment, the setting function for the Shake Action SH will be described. Note that the configuration of the payment application 200, the user terminal 2, the store terminal 3, and the electronic payment server 5 in the fourth embodiment are the same as in the first embodiment, so redundant explanations will be omitted, and the same parts will be denoted by the same reference numerals.

[0128] The Shake Action SH setting function is one of the program modules of the payment application 200 and corresponds to the setting unit 504 shown in Figure 5(b). In other words, the CPU 201 functions as the setting unit 504 by executing the program module.

[0129] The setting unit 504 receives a setting from the user to enable or disable the shake action SH and stores it in the storage unit 204 as setting information for the payment application 200. If the shake action SH is enabled by the setting unit 504, the action detection unit 502 and the display control unit 503 transition the screen displayed on the display unit 206 based on the shake action SH, as shown in the first to fourth embodiments. If the shake action SH is disabled by the setting unit 504, the action detection unit 502 does not output a detection signal to the CPU 201 even if the vibration detection unit 212 detects the shake action SH. Therefore, no screen transition based on the shake action SH is performed.

[0130] (Setup process) Referring to Figure 14, the flow of the setting process executed by the payment application 200 of the fifth embodiment will be explained. The process shown in the flowchart of Figure 14 is written in the program of the payment application 200 installed on the user terminal 2. The program is stored in the memory unit 204, called by the CPU 201, loaded into RAM 203, and executed. When the payment application 200 is started and the account button displayed on the top screen 101 (the button in the lower right of Figure 1(a)) is operated, the user is redirected to the account management screen. The account management screen (not shown) has various setting menus for the operation settings of the payment application 200, including settings related to the Shake Action SH, as well as volume settings, font size settings, notification settings, language settings, etc. When the user selects the Shake Action SH setting from this setting menu, the CPU 201 starts this flowchart.

[0131] In S1401, the CPU 201 displays the setting screen 1500 related to the shake action SH on the display unit 206.

[0132] In S1402, the CPU 201 retrieves the currently set setting information for the shake action SH from the setting information 240 stored in the memory unit 204. The setting information for the shake action SH indicates either enable or disable. In S1402, the CPU 201 reflects the retrieved current setting information for the shake action SH on the setting screen 1500.

[0133] Figure 15 shows an example of the settings screen 1500 for the Shake Action SH. As shown in Figure 15, the settings screen 1500 displays buttons to select either Enable 1501 or Disable 1502, and a check mark 1503 indicating the current setting information. In the example in Figure 15, the check mark 1503 is displayed for Enable 1501.

[0134] In S1403, if the user performs an operation to switch the settings related to the Shake Action SH (S1403; YES), the process proceeds to S1404. The switching operation is performed by the user selecting either the enabled button 1501 or the disabled button 1502 displayed on the settings screen 1500. The selection operation may be performed by tapping, for example. If the user operates a button different from the current setting, the CPU 201 determines that the Shake Action SH has been switched and proceeds to S1404.

[0135] In S1404, CPU201 switches the setting related to the Shake Action SH to the selected setting. For example, if the setting information for Shake Action SH obtained in S1402 is "Enabled", and the user selects "Disabled" 1502 on setting screen 1500, CPU201 switches the setting related to Shake Action SH to disabled. Also, for example, if the setting information for Shake Action SH obtained in S1402 is "Disabled", and the user selects "Enabled" 1501 on setting screen 1500, CPU201 switches the setting related to Shake Action SH to enabled.

[0136] In S1405, the CPU 201 saves the settings information that were switched in S1404 to the storage unit 204, and this flowchart ends.

[0137] In S1403, if the same button as the current setting is selected, or if the button 1504 to return to the previous screen is operated, the CPU 201 determines that the shake action SH will not be switched. In that case, steps S1404 to S1405 are skipped and the processing of this flowchart is terminated. If the button 1504 to return to the previous screen is operated, the CPU 201 displays the account management screen, which was displayed before the settings screen 1500 was displayed, on the display unit 206, and then terminates the processing of this flowchart.

[0138] As explained above, the payment application 200 of the fifth embodiment allows the user to enable or disable the Shake Action SH through a setting operation. The Shake Action SH setting information is acquired by the CPU 201 when the payment application 200 is launched and reflected in subsequent operations. That is, if the Shake Action SH setting information is set to "enabled", the CPU 201 executes screen transitions based on the Shake Action SH as shown in the first to fourth embodiments. If the Shake Action SH setting information is set to "disabled", the CPU 201 does not execute screen transitions based on the Shake Action SH. If the Shake Action SH is set to "disabled", screen transitions are executed based on button operations, similar to the conventional payment application 200.

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

[0140] 1. Electronic payment system 2. User terminals 101 Top screen 103 Payment screen 104 Scan screen 501 Payment Processing Unit 502 Action detection unit 503 Display Control Unit 504 Settings Section SH Shake Action

Claims

1. A payment application program that is pre-installed on a terminal device used by a user of electronic payment in order to use electronic payment using an identification code, wherein the terminal device With the payment application program running, a detection unit detects when the user shakes the terminal device, When the detection unit detects the shaking motion, the display control unit transitions the screen displayed on the display unit of the terminal device to the payment screen used for the electronic payment, A payment application program characterized by functioning as such.

2. A payment application program that is pre-installed on a terminal device used by a user of electronic payment to utilize electronic payment using an identification code, and which displays a top screen containing multiple buttons for transitioning to various screens after startup, wherein the terminal device is With the top screen displayed, a detection unit detects when the user shakes the terminal device, When the detection unit detects the shaking motion, the display control unit transitions the screen displayed on the display unit of the terminal device to the payment screen used for the electronic payment, A payment application program characterized by functioning as such.

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

4. The payment application program according to claim 1 or 2, characterized in that the payment screen is a second payment screen for reading a store code in which the store's identification information is encoded.

5. The payment screen includes a first payment screen that includes a user code in which the user's identification information is encoded, and a second payment screen for reading a store code in which the store's identification information is encoded. The payment application program according to claim 1 or 2, characterized in that the display control unit switches between displaying the first payment screen and the second payment screen each time the detection unit detects the shaking motion.

6. When the detection unit detects the shaking motion, the display control unit transitions the screen displayed on the display unit to the first payment screen. The payment application program according to claim 5, characterized in that when the detection unit detects the shaking motion while the first payment screen is displayed, the display control unit transitions the screen displayed on the display unit to the second payment screen.

7. When the detection unit detects the shaking motion, the display control unit transitions the screen displayed on the display unit to the second payment screen. The payment application program according to claim 5, characterized in that when the detection unit detects the shaking motion while the second payment screen is displayed, the display control unit transitions the screen displayed on the display unit to the first payment screen.

8. The payment application program according to claim 3, characterized in that the display control unit displays the first payment screen in a first state in which the longitudinal direction of the user code coincides with the longitudinal direction of the display range of the display unit.

9. The payment application program according to claim 5, characterized in that the display control unit displays the first payment screen in a first state in which the longitudinal direction of the user code coincides with the longitudinal direction of the display range of the display unit.

10. The payment application program according to claim 3, characterized in that the display control unit displays the first payment screen in a second state in which the longitudinal direction of the user code coincides with a direction perpendicular to the longitudinal direction of the display range of the display unit.

11. The payment application program according to claim 5, characterized in that the display control unit displays the first payment screen in a second state in which the longitudinal direction of the user code coincides with a direction perpendicular to the longitudinal direction of the display range of the display unit.

12. The display state of the first payment screen includes a first state in which the longitudinal direction of the user code coincides with the longitudinal direction of the display range of the display unit, and a second state in which the longitudinal direction of the user code coincides with a direction perpendicular to the longitudinal direction of the display range of the display unit. The payment application program according to claim 3, characterized in that the display control unit switches between the first state and the second state and displays them each time the detection unit detects the shaking motion.

13. The display state of the first payment screen includes a first state in which the longitudinal direction of the user code coincides with the longitudinal direction of the display range of the display unit, and a second state in which the longitudinal direction of the user code coincides with a direction perpendicular to the longitudinal direction of the display range of the display unit. The payment application program according to claim 5, characterized in that the display control unit switches between the first state and the second state and displays them each time the detection unit detects the shaking motion.

14. The payment application program according to claim 3, characterized in that the user code displayed on the first payment screen includes at least one of a one-dimensional code or a two-dimensional code.

15. The payment application program according to claim 5, characterized in that the user code displayed on the first payment screen includes at least one of a one-dimensional code or a two-dimensional code.

16. The payment application program according to claim 1, characterized in that, when the detection unit detects the shaking motion while the payment screen is displayed, the display control unit transitions the screen displayed on the display unit to the screen that was displayed on the display unit before the payment screen was displayed.

17. The payment application program according to claim 16, characterized in that the screen displayed on the display unit before the payment screen was displayed is the top screen displayed immediately after the start of the payment application program.

18. The payment application program according to claim 16, characterized in that the screen displayed on the display unit before the payment screen was displayed is a screen displayed in a function included in the payment application program.

19. If the screen that was displayed on the display unit before the payment screen was displayed is a screen displayed in a function included in the payment application program, The payment application program according to claim 1, characterized in that when the detection unit detects the shaking motion while the payment screen is displayed, the display control unit transitions to the top screen that is displayed immediately after the start of the payment application program.

20. The payment application program according to claim 2, characterized in that, when the detection unit detects the shaking motion while the payment screen is displayed, the display control unit transitions the screen displayed on the display unit to the screen that was displayed on the display unit before the payment screen was displayed.

21. The payment application program according to claim 1 or 2, further comprising a setting unit that accepts a setting by the user to enable or disable the aforementioned shaking action.

22. An information processing device used by a user of electronic payment to utilize electronic payment using an identification code, A detection unit that detects when the user shakes the information processing device while the payment application program is running, When the detection unit detects the shaking motion, the display control unit transitions the screen displayed on the display unit of the information processing device to the payment screen used for electronic payment. An information processing device characterized by comprising:

23. An information processing device used by a user of electronic payment to utilize electronic payment using an identification code, With the top screen of the payment application, which includes multiple buttons for transitioning to various screens, displayed, a detection unit detects the user shaking the information processing device, When the detection unit detects the shaking motion, the display control unit transitions the screen displayed on the display unit of the information processing device to the payment screen used for electronic payment. An information processing device characterized by comprising:

24. An information processing method performed by a computer in a terminal device used by a user of electronic payment in order to use electronic payment using an identification code, With the payment application program running, the user shakes the terminal device; When the aforementioned shaking motion is detected, the screen displayed on the display unit of the terminal device is transitioned to the payment screen used for the electronic payment; An information processing method characterized by including

25. An information processing method performed by a computer in a terminal device used by a user of electronic payment in order to use electronic payment using an identification code, The process includes the step of detecting the user shaking the terminal device while the top screen of the payment application, which includes multiple buttons for transitioning to various screens, is displayed, When the aforementioned shaking motion is detected, the screen displayed on the display unit of the terminal device is transitioned to the payment screen used for the electronic payment; An information processing method characterized by including

Images