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

Abstract

The aim is to improve the operability of payment apps 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 to utilize an identification code, and is characterized in that it includes a detection unit that detects the user's action of shaking the terminal device, and a display control unit that, when the detection unit detects the shaking action, transitions the screen displayed on the display unit of the terminal device to a payment screen used for the electronic payment.

Description

[Technical field]

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

[0002] Cashless payments, which are payments for goods or services made without using currency, are becoming more common. In particular, electronic payments using payment application programs (hereinafter referred to as payment apps) that can be installed on terminal devices such as smartphones are attracting attention due to their high convenience. There are two payment methods using payment apps. The first method is to have a user's identification code (barcode or QR code (registered trademark)) in which the user's identification information is coded, displayed on the user's terminal device, and store staff reads it using a code reader on the store terminal. The second method is to scan a store's identification code posted in the store with the user's terminal, and input the payment amount.

[0003] Patent Document 1 describes an example of a screen used in the first method. Specifically, it describes that when a predetermined button on a screen that displays buttons related to various services and is displayed on a user terminal after the payment application is started is operated, the screen transitions to a payment screen that is different from the screen, and an identification code for the user is enlarged and displayed on the payment screen. Patent Document 2 describes an example of displaying a scan screen used to read a store code in the second method on the user terminal, and then transitioning to an amount input screen. [Prior art documents] [Patent documents]

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

[0005] However, the techniques described in the patent documents leave room for improvement in terms of improving the operability of payment apps.

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

[0007] A payment application program according to one embodiment of the present disclosure is a payment application 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 is characterized in that it includes a detection unit that detects the user's action of shaking the terminal device, and a display control unit that, when the detection unit detects the shaking action, transitions a screen displayed on a display unit of the terminal device to a payment screen used for the electronic payment. Effect of the Invention

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

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

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

[0011] Fig. 1 is a diagram showing an overview of the present disclosure. A payment application according to an embodiment of the present disclosure is a program pre-installed in a terminal device (hereinafter referred to as a user terminal) used by an electronic payment user to utilize electronic payment using an identification code. The payment application has a detection unit that detects a user's action of shaking the user terminal, and a display control unit that transitions a screen displayed on the display unit of the user terminal to a payment screen used for electronic payment when the detection unit detects the shaking action.

[0012] The shaking motion is one form of operation of a user terminal, and is a motion in which the user intentionally shakes the user terminal. In this specification, the shaking motion is called a shaking action.

[0013] According to the present disclosure, a payment screen can be displayed on a user terminal by a shaking action, thereby improving the operability of a payment app.

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

[0015] Although details will be described later, there are two payment methods using the payment app: Method 1 and Method 2. In Method 1, a store staff member reads a user identification code in which the user's identification information is coded using a code reader in the store terminal. In Method 2, a store identification code in which the store's identification information is coded and displayed in a store or the like is scanned using a user terminal, and the payment amount is input. In the following description, Method 1 is also referred to as store scan, and Method 2 is also referred to as user scan. The first payment screen is a payment screen used in Method 1, and is also referred to as payment screen 103 in this specification. The second payment screen is a payment screen used in Method 2, and is also referred to as scan screen 104 in this specification.

[0016] Fig. 1(a) is a diagram showing an example of a top screen 101 displayed on the display unit of a user terminal immediately after the start of a payment application. When the user performs a "shake action SH" by shaking the user terminal while the top screen 101 is displayed, the screen transitions to Fig. 1(b).

[0017] Fig. 1(b) shows the state where the screen has transitioned to a payment screen 103 as the settlement screen to which the user transitions when the user performs a shaking action SH. A one-dimensional code such as a barcode or a two-dimensional code such as a QR code (registered trademark) is displayed as a user code on the payment screen 103. When the user further performs a shaking action SH while the payment screen 103 is displayed, the screen transitions to a scan screen 104 shown in Fig. 1(c).

[0018] Furthermore, when a user performs a shaking action SH while a payment screen such as payment screen 103 or 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 of Fig. 1, the screen that was displayed before the payment screen was displayed was top screen 101, so the transition is to top screen 101. In this way, the payment screen can be transitioned to the original screen by the shaking action SH.

[0019] The screen displayed on the display unit before the payment screen is displayed is not limited to the top screen 101, and may be a screen displayed in various functions included in the payment app. Various functions included in the payment app are referred to as mini-apps in this specification. Mini-apps include 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, and other functions. Conventionally, transitions to these mini-app screens have been possible from various buttons displayed on the top screen 101.

[0020] If the screen displayed on the display unit before the payment screen is displayed is a mini app screen, when the user performs a shaking action SH while the payment screen is displayed, the display control unit transitions to the mini app screen.

[0021] Alternatively, in the case where the screen displayed on the display unit before the payment screen was displayed was a mini app screen, when the user performs a shaking action SH while the payment screen is displayed, the display control unit may transition to the top screen 101. Details of the screen transition will be described later.

[0022] In this way, according to the payment app of the present disclosure, when a user shakes the user terminal, the display on the display unit can be switched to a payment screen used for electronic payment. Therefore, the screen can be switched with one hand, and the screen can be switched quickly and easily compared to the conventional button operation.

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

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

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

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

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

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

[0029] In reading the identification code in the store scan, the identification code displayed on the top screen 101 shown in FIG. 1(a) may be used, or the identification code displayed on the payment screen 103 shown in FIG. 1(b) may be used. FIG. 3(a) is a diagram for explaining the payment screen 103. When the user taps the payment button 109 displayed on the top screen 101 or performs a shaking action SH, the payment screen 103 is displayed on the display unit 206 of the user terminal 2. The payment screen 103 displays a first identification code 311 and a second identification code 312 as a user code in which the user's identification information is coded. 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 of FIG. 3(a), both are displayed. The payment screen 103 may also display information related to the payment, such as the available amount, charge balance, and points. The payment screen 103 also displays a button 313 that is operated when transitioning to a scan screen 104 used in the user scan described later. To transition from the payment screen 103 to the scan screen 104, the user may operate button 313 or perform a shaking action SH. To return from the payment screen 103 to the top screen 101, the user may operate button 314. Details of screen transitions will be described later.

[0030] (User Scan) In user scanning, the user terminal 2 reads a store code image 32 such as a QR code posted in a store. The store code image 32 contains store URL information. The payment app 200 of the user terminal 2 adds the user's identification information to the read store URL information and transmits it to the electronic payment server 5. The electronic payment server 5 identifies the user and store from a database based on the received store URL and user identification information, and displays an amount input screen on the user terminal 2. The user terminal 2 accepts the amount input by the user on the amount input screen, and transmits information on the input amount to the electronic payment server 5. The electronic payment server 5 performs payment processing between the electronic accounts of the identified user and store. When the payment processing is completed, a payment completion screen is displayed on the user terminal 2.

[0031] The scan screen 104 shown in FIG. 3(b) is used to read the store code image 32 in the user scan. The user operates the payment application 200 to display the scan screen 104 on the display unit 206 of the user terminal 2, and takes a picture of the store code image 32 posted in the store so that the store code image 32 fits within the frame 321. The scan screen 104 can be transitioned to by tapping the scan button 108 displayed on the top screen 101 shown in FIG. 1(a), tapping the button 313 displayed on the payment screen 103 shown in FIG. 3(a), or by a shaking action SH. To return from the scan screen 104 to the payment screen 103, the user taps the button 322 in the scan screen 104. To return from the scan screen 104 to the top screen 101, the user operates the button 314 or performs a shaking action SH.

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

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

[0034] The CPU 201 is a central processing unit and controls each part of the user terminal 2. The CPU 201 reads a program stored in the ROM 202 or the storage unit 204 into the RAM 203 and executes the read program to realize various functions included in the program. The CPU 201 may be an MPU (Micro Processing Unit) or an ASIC (Application Specific Integrated Circuit). The CPU 201 may be an FPGA (Field Programmable Gate Array) or the like. The CPU 201 may be composed of one processor or may be composed of multiple processors.

[0035] The ROM 202 stores a boot program, an OS (Operating System), etc. of the user terminal 2. The RAM 203 temporarily stores programs or data when the CPU 201 executes various processes. The RAM 203 is used as a working memory.

[0036] The storage unit 204 is a memory for storing application programs, various data, etc. Examples of the storage unit 204 include a hard disk drive (HDD), a solid state drive (SDD), a flash memory, and storage.

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

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

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

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

[0041] The vibration detection unit 212 is configured with a gyro sensor or the like. The gyro sensor measures the rotational angular velocity when the user terminal 2 is tilted, and includes a vibration type gyro sensor, a capacitance type gyro sensor, and the like. When the vibration detection unit 212 detects the vibration of the user terminal 2, it outputs a detection signal to the CPU 201. The detection of the shaking action SH is realized by the vibration detection unit 212.

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

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

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

[0045] FIG. 5(a) is a diagram showing data stored in the storage unit 204 of the user terminal 2. As shown in FIG. 5(a), the storage unit 204 of the user terminal 2 stores, in addition to the program of the payment application 200, data of various screens displayed in the payment application (hereinafter referred to as screen data 230), identification information 220 of the user in the electronic payment service, and various setting information 240 of the payment application 200. The identification information 220 is provided by the electronic payment server 5 at the time of account registration. The setting information 240 includes various setting information related to the functions of the payment application 200. For example, setting information on whether to enable or disable the shake action SH, setting information on the transition order of the screens by the shake action SH, and the like are stored. The screen data 230 includes screen data of the top screen 101, the payment screen 103, and the scan screen 104 described above, as well as screen data of mini apps, screen data of an amount input screen, a payment completion screen, and the like displayed in the payment process, and screen data of various error notification screens.

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

[0047] The payment application 200 has various functions in addition to a payment processing function for performing electronic payments in electronic payment services. For example, it includes a remittance 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 delivery function, a My Page function for managing user account information, and other functions. In the following description, functions in the payment application 200 other than the payment processing function are collectively referred to as mini-applications. The payment application 200 also has a display control function for controlling the display of a screen, an action detection function for detecting a shaking action SH, a setting function for accepting various settings from a user, such as whether to enable or disable the action detection function, and the screen transition order.

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

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

[0050] The action detection unit 502 detects a shaking action SH made by the user on the user terminal 2. That is, when the user makes a shaking action SH, the vibration detection unit 212, which is configured by 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 the shaking action SH has been made by acquiring the detection signal input to the CPU 201. The vibration detection unit 212 detects a shaking action SH made intentionally by the user and unintentional vibrations. That is, the vibration detection unit 212 detects a shaking action SH as an operation action and vibrations of the user terminal 2 caused by walking or shaking. The vibration detection unit 212 detects a shaking action SH when it detects, for example, a vibration amount equal to or greater than a predetermined threshold or a vibration equal to or greater than a predetermined number of times. When the vibration detection unit 212 detects that a shaking action SH has been made, it inputs a detection signal indicating that the shaking action SH has been detected to the CPU 201.

[0051] The display control unit 503 displays various screens corresponding to various functions of the payment app 200 on the display unit 206 of the user terminal 2. The display control unit 503 obtains screen data 230 of various screens from the storage unit 204 in response to operations by the user, and displays them on the display unit 206. At that time, the identification information 220, balance information obtained from the electronic payment server 5, etc. may be reflected on the screen. For example, when the user double-tap the start-up icon of the payment app 200 displayed on the home screen of the user terminal 2, the payment app 200 is started. When the payment app 200 is started, the display control unit 503 displays the top screen 101 shown in FIG. 1(a).

[0052] In this embodiment, when the action detection unit 502 detects a shaking 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 transition destination payment screen may be a first payment screen (payment screen 103) including a user code in which the user's identification information is coded, or a second payment screen (scan screen 104) for reading a store code in which the store's identification information is coded. The display control when the action detection unit 502 detects a shaking action SH will be described in detail below.

[0053] FIG. 6 is a diagram for explaining a first pattern of screen transition, and FIG. 7 is a diagram for explaining a second pattern of screen transition.

[0054] In the first pattern shown in FIG. 6, when the action detection unit 502 detects a shaking action SH while the top screen 101 shown in FIG. 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 aspect of the payment screen. FIG. 6(b) shows the payment screen 103, which is the transition destination. When the action detection unit 502 further detects a shaking 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 aspect of the payment screen. FIG. 6(c) shows the scan screen 104, which is the transition destination. When the action detection unit 502 detects a shaking 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, that is, the top screen 101. Return to the state of FIG. 6(a).

[0055] In the second pattern shown in FIG. 7, when the action detection unit 502 detects a shaking action SH while the top screen 101 is displayed as shown in FIG. 7(a), the display control unit 503 first transitions the screen displayed on the display unit 206 to the scan screen 104. FIG. 7(b) shows the scan screen 104, which is the transition destination. When the action detection unit 502 further detects a shaking 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. FIG. 7(c) shows the payment screen 103, which is the transition destination. When the action detection unit 502 detects a shaking 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, that is, the top screen 101. Return to the state of FIG. 7(a).

[0056] Whether display control unit 503 performs a screen transition in the above-mentioned first pattern or the second pattern is determined in advance and stored in storage unit 204 as setting information 240 of payment application 200. Alternatively, the user may set this in setting unit 504, and the setting information 240 may be stored in storage unit 204.

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

[0058] The flow chart shown in FIG. 8(a) will be described. 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 FIG. 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, and the like. 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 obtained by encoding the user's identification information. In addition, inside the code display area 604, a payment method and balance information may be displayed. In the upper area of ​​the code display area 604, campaign information 610 and a notification icon 611 are displayed. In addition, in the right area of ​​the code display area 604, operation buttons such as a credit payment button 612 operated when transitioning to a credit payment screen may be displayed.

[0059] In S802, if a shaking action SH is detected by the vibration detection unit 212 and the CPU 201 acquires the detection signal (S802; YES), the process proceeds to S803.

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

[0061] With the payment screen 103 being displayed, if a shaking action SH is detected by the vibration detection unit 212 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 displayed on the display unit 206 to the scan screen 104. That is, the CPU 201 acquires screen data for the scan screen 104 from the storage unit 204, and displays it on the display unit 206 as shown in FIG. 6(c). With the scan screen 104 displayed, the CPU 201 activates the camera 209, enabling it to read a 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 transmits and receives information to and from the electronic payment server 5 according to the procedure of the user scan payment processing described above, and displays an amount input screen, a payment completion screen, and the like.

[0063] With the scan screen 104 displayed, if a shaking action SH is detected by the vibration detection unit 212 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 displayed on the display unit 206 to the top screen 101 shown in Fig. 1. Thereafter, the processes of S802 to S806 are repeated.

[0064] In S802, S804, and S806, if a shaking action SH is not detected within a predetermined time, the process ends with the screen being displayed.

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

[0066] In S812, if a shaking action SH is detected by the vibration detection unit 212 and the CPU 201 acquires the detection signal (S812; YES), the process proceeds to S813.

[0067] In S813, the CPU 201 transitions the screen displayed on the display unit 206 to the scan screen 104. That is, the CPU 201 acquires screen data for the scan screen 104 from the storage unit 204, and displays it on the display unit 206 as shown in FIG. 7(b). With the scan screen 104 displayed, the CPU 201 activates the camera 209, enabling it to read a 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 transmits and receives information to and from the electronic payment server 5 according to the procedure of the user scan payment processing described above, and displays an amount input screen, a payment completion screen, and the like.

[0068] With the scan screen 104 displayed, if a shaking action SH is detected by the vibration detection unit 212 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 displayed on the display unit 206 to the payment screen 103. That is, the CPU 201 obtains screen data for the payment screen 103 from the storage unit 204, and displays it on the display unit 206 as shown in FIG. 7(c). Note that while the payment screen 103 is displayed, the code reader 31 of the store terminal 3 may read the user code and execute payment processing. In this case, the CPU 201 transmits and receives information to and from the store terminal 3 in accordance with the procedure of the store scan payment processing described above, and displays a payment completion screen (not shown) in accordance with the payment completion notification sent from the electronic payment server 5.

[0070] With the payment screen 103 displayed, if a shaking action SH is detected by the vibration detection unit 212 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 displayed on the display unit 206 to the top screen 101 shown in Fig. 1. Thereafter, the processes of S812 to S816 are repeated.

[0071] In S812, S814, and S816, if a shaking action SH is not detected within a predetermined time, the process ends with the screen being displayed.

[0072] As described above, according to the payment app 200 of the first embodiment, when a user performs a shaking action SH on the user terminal 2, the screen can transition to a payment screen such as the payment screen 103 or the scan screen 104. Also, when a user performs a shaking action SH while the payment screen is displayed, the screen can return to the top screen 101 that was displayed before the payment screen was displayed. Therefore, the screen can be easily transitioned to the payment screen with an operation using only one hand, and can also be returned to the original screen from the payment screen, improving operability.

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

[0074] <Second embodiment> Next, a second embodiment of the present disclosure will be described. In the second embodiment, an example in which the display state of the payment screen 103 is horizontal display will be described. The 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 those in the first embodiment, so duplicated explanations will be omitted and the same parts will be described with the same reference numerals.

[0075] Fig. 9 is a diagram illustrating screen transitions by the payment app 200 of the second embodiment. In the second embodiment, a shaking action SH is performed by the user terminal 2 while the top screen 101 is displayed as shown in Fig. 9(a). When the action detection unit 502 detects the shaking 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 aspect of a payment screen. Fig. 9(b) shows the horizontal payment screen 900 to which the transition is made.

[0076] The horizontal payment screen 900 is a screen that displays a payment screen including a user code with the longitudinal direction of the display range of the display unit 206 as the horizontal direction. In the figure, the horizontal direction is represented as the left-right direction. As shown in FIG. 9(b), the horizontal payment screen 900 displays, as a user code, either or both of a first identification code 911, which is a one-dimensional code, and a second identification code 912, which is a two-dimensional code. In the example of FIG. 9(b), both are displayed. In this horizontal payment screen 900, the first identification code 911, which is the user code, is displayed so that its longitudinal direction 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 of the display unit 206, that is, the range equivalent to the display size. Such a display state is called a horizontal display. In the normal payment screen 103 shown in FIG. 3(a), the first identification code 911, which is the user code, is displayed so that its longitudinal direction coincides with the direction perpendicular to the longitudinal direction of the display range of the display unit 206. Such a display state is called a vertical display.

[0077] In the example of the horizontal payment screen 900 in FIG. 9(b), the user code is enlarged as compared with the normal payment screen 103 shown in FIG. 3(a). Preferably, the user code is displayed in a size that maximizes the display range of the display unit 206. Specifically, the user code is enlarged to a range in which 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 of the first identification code 911 and the second identification code 912 arranged 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 is maintained to that of the user code displayed on the normal payment screen 103. The user code is arranged and enlarged within the screen so as to include an appropriate margin. The user code does not necessarily need to be enlarged, and may be displayed in the same size as the user code on the normal payment screen 103, or may be any size. However, regardless of the size at which the user code is displayed, 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 normal payment screen 103. Also, like the normal payment screen 103, the horizontal payment screen 900 may also display information such as the available credit, charge balance, and points.

[0078] When the action detection unit 502 detects a shaking 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 aspect of the payment screen. FIG. 9(c) shows the scan screen 104 to which the transition is made. When the action detection unit 502 detects a shaking 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, and returns to the state of FIG. 9(a).

[0079] When the payment screen is displayed horizontally, the setting is determined in advance and stored in storage unit 204 as setting information 240. Based on setting information 240, CPU 201 determines whether the display state of the payment screen is to be horizontal or vertical.

[0080] (Display control processing) The display control process in the second embodiment is executed in the same procedure as the flowchart in Fig. 8(a). However, in S803, the CPU 201 displays a horizontal payment screen 900 shown in Fig. 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 have the same processing procedure as the flowchart in Fig. 8(b). In that case, in S815, the CPU 201 displays the horizontal payment screen 900 shown in Fig. 9(b) instead of the normal payment screen 103. When the display control process in the second embodiment is executed in the processing procedure of the flowchart in Fig. 8(b), the following screen transition occurs.

[0082] First, a shaking action SH is performed by the user terminal 2 with the top screen 101 displayed as shown in Fig. 9(a). When the action detection unit 502 detects the shaking action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to the scan screen 104 shown in Fig. 9(c). When the action detection unit 502 detects the shaking action SH with the scan screen 104 displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the horizontal payment screen 900 shown in Fig. 9(b). When the action detection unit 502 detects the shaking action SH with the horizontal payment screen 900 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, and returns to the state of Fig. 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 display and vertical display every time the action detection unit 502 detects a shaking action SH. In this case, the following screen transition occurs.

[0084] First, a shaking action SH is performed by the user terminal 2 with the top screen 101 displayed as shown in FIG. 9(a). When the action detection unit 502 detects the shaking action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to a horizontal payment screen 900 (horizontal display) shown in FIG. 9(b). When the action detection unit 502 detects the shaking action SH with the horizontal payment screen 900 displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to a normal payment screen 103 (vertical display) shown in FIG. 3(c). When the action detection unit 502 detects the shaking action SH with the normal payment screen 103 shown in FIG. 3(c) displayed, the display control unit 503 transitions the screen displayed on the display unit 206 to the screen before the settlement screen was displayed, that is, the top screen 101, and returns to the state of FIG. 9(a).

[0085] <Modification 3 of the second embodiment> When a shaking action SH is detected while the top screen 101 is displayed, the display control unit 503 may transition to a horizontal payment screen 900 (horizontal display) shown in FIG. 9(b). When a shaking action SH is detected while the horizontal payment screen 900 is displayed, the display control unit 503 transitions to a normal payment screen 103 (vertical display) shown in FIG. 3(c). Then, when a shaking action SH is detected while the normal payment screen 103 shown in FIG. 3(c) is displayed, the display control unit 503 may transition to a scan screen 104 shown in FIG. 9(c). After that, when a shaking 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 of FIG. 9(a).

[0086] <Modification 4 of the Second Embodiment> In the case where the scan screen 104 is displayed first and the horizontal payment screen 900 is displayed later based on a shaking action SH, if the shaking 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 Fig. 3(c). After that, if the shaking action SH is detected while the normal payment screen 103 shown in Fig. 3(c) is displayed, the display may transition to the top screen 101 and return to the state of Fig. 9(a).

[0087] As described above, according to the payment app 200 of the second embodiment, the payment screen to which the user transitions when a shaking action SH is performed on the user terminal 2 can be the horizontal payment screen 900. Furthermore, when a shaking action SH is performed with the horizontal payment screen 900 displayed, it is possible to cause the screen to transition to the vertically displayed payment screen 103. Furthermore, when a shaking action SH is performed with the vertically displayed payment screen 103 displayed, it is possible to cause the screen to transition to the horizontal payment screen 900.

[0088] The order of screen transitions in the second embodiment and the modified example may be set by the user. The order of screen transitions may be arbitrary, such as the first round being the screen transition of the second embodiment (FIG. 9) and the second round being the screen transition of modified example 1.

[0089] <Third embodiment> Next, a third embodiment of the present disclosure will be described. In the first and second embodiments, an example in which a shaking action SH is executed on the top screen 101 of the payment application 200 has been described. In the third embodiment, a case in which the screen before transitioning to the payment screen is not the top screen 101 but a mini app screen will be described. Note that the configurations of the payment application 200, the user terminal 2, the store terminal 3, and the electronic payment server 5 in the third embodiment are the same as those in the first embodiment, so duplicated descriptions will be omitted and the same parts will be described with the same reference numerals.

[0090] FIG. 10 is a diagram for explaining screen transition by the payment application 200 of the third embodiment. In the third embodiment, a state in which a coupon application screen is displayed is shown as an example of the mini application screen 1000. In this state in which the mini application screen 1000 is displayed, a shaking action SH is performed by the user terminal 2. When the action detection unit 502 detects the shaking action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to a payment screen 103, which is one aspect of a payment screen. FIG. 10(b) shows the payment screen 103 to which the transition is made. The payment screen 103 may be the normal payment screen 103 as described in the first embodiment, or may be the horizontal payment screen 900 as described in the second embodiment. FIG. 10(b) shows an example in which the normal payment screen 103 is displayed.

[0091] When the action detection unit 502 detects a shaking 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 aspect of the payment screen. FIG. 10(c) shows the scan screen 104, which is the transition destination. When the action detection unit 502 detects a shaking 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, that is, the coupon screen. FIG. 10(d) shows the coupon screen, which is the transition destination. In this way, in the third embodiment, even from a mini app screen, a transition to the payment screen can be made by a shaking action SH. Also, a transition from the payment screen to the original mini app screen can be made by a shaking action SH.

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

[0093] When a user operates a button for any function (mini app) on top screen 101 that is displayed after starting payment application 200, the process shifts to the corresponding mini app. When the process shifts to the mini app, CPU 201 starts the process shown in this flowchart.

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

[0095] In S1102, if a shaking action SH is detected by the vibration detection unit 212 and the CPU 201 acquires the detection signal (S1102; YES), the process proceeds to S1103.

[0096] In S1103, the CPU 201 transitions the screen displayed on the display unit 206 to the payment screen 103. That is, the CPU 201 obtains screen data for the payment screen 103 from the storage unit 204, and displays it on the display unit 206 as shown in FIG. 10(b). With the payment screen 103 displayed, the code reader 31 of the store terminal 3 may read the user code, and the payment process may be executed. In this case, the CPU 201 transmits and receives information to and from the store terminal 3 in accordance with the procedure of the store scan payment process described above, and displays a payment completion screen (not shown) in accordance with the payment completion notification transmitted from the electronic payment server 5.

[0097] With the payment screen 103 displayed, if a shaking action SH is detected by the vibration detection unit 212 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 displayed on the display unit 206 to the scan screen 104. That is, the CPU 201 acquires screen data for the scan screen 104 from the storage unit 204, and displays it on the display unit 206 as shown in FIG. 10(c). With the scan screen 104 displayed, the CPU 201 activates the camera 209, enabling it to read a 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 transmits and receives information to and from the electronic payment server 5 according to the procedure of the user scan payment processing described above, and displays an amount input screen, a payment completion screen, and the like.

[0099] With the scan screen 104 displayed, if a shaking action SH is detected by the vibration detection unit 212 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 displayed on the display unit 206 to the mini app screen 1000 shown in Fig. 1. Thereafter, the processes of S1102 to S1106 are repeated.

[0100] In S1102, S1104, and S1106, if a shaking action SH is not detected within a predetermined time, the process ends with the screen being displayed.

[0101] <Modification 1 of the third embodiment> In the display control process in the third embodiment, the display order of the payment screens may be changed so that the scan screen 104 comes first and the payment screen 103 comes later. That is, first, a shaking action SH is performed by the user terminal 2 while the mini app screen 1000 is displayed as shown in FIG. 10(a). When the action detection unit 502 detects the shaking action SH, the display control unit 503 changes the screen displayed on the display unit 206 to the scan screen 104 shown in FIG. 10(c). When the action detection unit 502 detects the shaking action SH while the scan screen 104 is displayed, the display control unit 503 changes the screen displayed on the display unit 206 to the payment screen 103 shown in FIG. 10(b). When the action detection unit 502 detects the shaking action SH while the payment screen 103 is displayed, the display control unit 503 changes the screen displayed on the display unit 206 to the screen before the payment screen was displayed, i.e., the mini app screen 1000, and returns to the state of FIG. 10(a).

[0102] The process flow in this case is a flow in which S1103 and S1105 in the flowchart of FIG. 11 are interchanged.

[0103] <Modification 2 of the third embodiment> Furthermore, in the third embodiment, the payment screen 103 to which a transition occurs in response to a shaking action SH may be a horizontal payment screen 900 shown in Fig. 9(b) instead of the normal payment screen 103. That is, each time a shaking action SH is performed from the mini app screen 1000, the screen may transition in this order from the horizontal payment screen 900, the scan screen 104, and the mini app screen 1000. Alternatively, each time a shaking action SH is performed from the mini app screen 1000, the screen may transition in this order from the scan screen 104, the horizontal payment screen 900, and the mini app screen 1000.

[0104] <Modification 3 of the third embodiment> In the third embodiment, when the payment screen 103 to which a transition occurs in response to a shaking action SH is the horizontal payment screen 900 shown in FIG. 9(b), the horizontal payment screen 900 and the normal payment screen 103 may be switched each time the shaking action SH is performed. That is, each time the shaking action SH is performed, the screens may transition in the order of mini app screen 1000, horizontal payment screen 900, normal payment screen 103, scan screen 104, and mini app screen 1000. Alternatively, each time the shaking action SH is performed, the screens may transition in the order of mini app screen 1000, scan screen 104, horizontal payment screen 900, normal payment screen 103, and mini app screen 1000. In addition, 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 described above, according to the payment application 200 of the third embodiment, a shake action SH can be used to transition from a mini app screen to a payment screen such as the payment screen 103 or the scan screen 104. Therefore, the payment screen can be easily transitioned to by an operation with only one hand, improving operability. In particular, the payment button 109 and the scan button 108 displayed on the top screen 101 of the payment application 200 are often not displayed on the mini app screen. Therefore, in the past, when a user wanted to transition from the mini app screen to the payment screen, he or she had to return to the top screen 101 once and operate the payment button 109 or the scan button 108. On the other hand, according to the payment application 200 of the third embodiment, a transition to the payment screen can be made by simply performing a shake action SH while the mini app screen is displayed. Therefore, the operability of the payment application is improved. In addition, a shake action SH on the payment screen can be used to return to the original mini app screen before the payment screen was displayed, making the screen transition from the payment screen to the mini app smooth.

[0106] The order of screen transitions in the third embodiment and the modified example may be set by the user. The order of screen transitions may be arbitrary, such as the first round being the screen transition of the third embodiment and the second round being the screen transition of the modified example 1.

[0107] <Fourth embodiment> Next, a fourth embodiment of the present disclosure will be described. In the third embodiment, an example was described in which, when a shake action SH is executed on a screen of a mini app of the payment app 200, the screen transitions to a payment screen, and the screen returns to the mini app by a shake action SH. In the fourth embodiment, an example is described in which, when the screen before the transition to the payment screen is the mini app screen, the screen transitions to a payment screen, and the screen returns to the top screen 101 by a shake action SH thereafter. Note that the configurations 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 those in the first embodiment, and therefore, duplicated explanations will be omitted, and the same parts will be described with the same reference numerals.

[0108] FIG. 12 is a diagram for explaining screen transitions by the payment application 200 of the fourth embodiment. As shown in FIG. 12(a), the fourth embodiment also shows a coupon application screen as an example of the mini application screen 1000. With the mini application screen 1000 displayed in this manner, the user terminal 2 performs a shaking action SH. When the action detection unit 502 detects the shaking action SH, the display control unit 503 transitions the screen displayed on the display unit 206 to a payment screen 103, which is one aspect of a payment screen. FIG. 12(b) shows the payment screen 103 to which the transition is made. The payment screen 103 may be the normal payment screen 103 as described in the first embodiment, or may be the horizontal payment screen 900 as described in the second embodiment. FIG. 12(b) shows an example in which the normal payment screen 103 is displayed.

[0109] When the action detection unit 502 detects a shaking 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 aspect of the payment screen. FIG. 12(c) shows the scan screen 104, which is the transition destination. When the action detection unit 502 detects a shaking 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. FIG. 12(d) shows the top screen 101, which is the transition destination. In this way, in the fourth embodiment, even from the screen 1000 of the mini application, a transition to the payment screen can be made by a shaking action SH. Also, a transition from the payment screen to the top screen 101 of the payment application 200 can be made by a shaking action SH.

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

[0111] When a user operates a button for any function (mini app) on top screen 101 that is displayed after starting payment application 200, the process shifts to the corresponding mini app. When the process shifts to the mini app, CPU 201 starts the process shown in this flowchart.

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

[0113] In S1302, if a shaking action SH is detected by the vibration detection unit 212 and the CPU 201 acquires the detection signal (S1302; YES), the process proceeds to S1303.

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

[0115] With the payment screen 103 displayed, if a shaking action SH is detected by the vibration detection unit 212 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 displayed on the display unit 206 to the scan screen 104. That is, the CPU 201 acquires screen data for the scan screen 104 from the storage unit 204, and displays it on the display unit 206 as shown in FIG. 12(c). With the scan screen 104 displayed, the CPU 201 activates the camera 209, enabling it to read a 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 transmits and receives information to and from the electronic payment server 5 according to the procedure of the user scan payment processing described above, and displays an amount input screen, a payment completion screen, and the like.

[0117] With the scan screen 104 displayed, if a shaking action SH is detected by the vibration detection unit 212 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 displayed on the display unit 206 to the top screen 101 of the payment application 200. That is, the CPU 201 obtains screen data of the top screen 101 from the storage unit 204, and displays it on the display unit 206 as shown in FIG.

[0119] When a transition to the top screen 101 has occurred, or when in S1102, S1104, or S1106 a shaking action SH is not detected within a predetermined time period, this flow chart ends with the displayed screen maintained.

[0120] When the top screen 101 is displayed, a shaking action SH may be accepted on the top screen 101 as shown in the first and second embodiments. In that case, the CPU 201 performs a screen transition as described in the first and second embodiments.

[0121] <Modification 1 of the Fourth Embodiment> In the display control process in the fourth embodiment, the display order of the settlement screens may be changed so that the scan screen 104 comes first and the payment screen 103 comes later. That is, first, a shaking action SH is performed by the user terminal 2 while the mini app screen 1000 is displayed as shown in FIG. 12(a). When the action detection unit 502 detects the shaking action SH, the display control unit 503 changes the screen displayed on the display unit 206 to the scan screen 104 shown in FIG. 12(c). When the action detection unit 502 detects the shaking action SH while the scan screen 104 is displayed, the display control unit 503 changes the screen displayed on the display unit 206 to the payment screen 103 shown in FIG. 12(b). When the action detection unit 502 detects the shaking action SH while the payment screen 103 is displayed, the display control unit 503 changes the screen displayed on the display unit 206 to the top screen 101 as shown in FIG. 12(d).

[0122] The process flow in this case is a flow in which S1303 and S1305 in the flowchart of FIG. 13 are interchanged.

[0123] <Modification 2 of the Fourth Embodiment> Also, in the fourth embodiment, the payment screen 103 to which a transition occurs in response to a shaking action SH may be a horizontal payment screen 900 shown in Fig. 9(b) instead of the normal payment screen 103. That is, each time a shaking action SH is performed from the mini app screen 1000, the screen may transition in this order from the horizontal payment screen 900, the scan screen 104, and the top screen 101. Alternatively, each time a shaking action SH is performed from the mini app screen 1000, the screen may transition in this order from the scan screen 104, the horizontal payment screen 900, and the top screen 101.

[0124] <Modification 3 of the fourth embodiment> In the fourth embodiment, when the payment screen 103 to which a transition occurs in response to a shaking action SH is the horizontal payment screen 900 shown in FIG. 9(b), the horizontal payment screen 900 and the normal payment screen 103 may be switched each time the shaking action SH is performed. That is, each time the shaking action SH is performed, the screens may transition in the order of mini app screen 1000, horizontal payment screen 900, normal payment screen 103, scan screen 104, and mini app screen 1000. Alternatively, each time the shaking action SH is performed, the screens may transition in the order of mini app screen 1000, scan screen 104, horizontal payment screen 900, normal payment screen 103, and mini app screen 1000. In addition, 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 described above, according to the payment app 200 of the fourth embodiment, a shaking action SH can be used to transition from the mini app screen 1000 to a payment screen such as the payment screen 103 or the scan screen 104. This allows easy transition to the payment screen with one hand, improving operability. Also, a shaking action SH can be used to transition from the payment screen to the top screen 101. The top screen 101 displays buttons to be operated when transitioning to the payment screen as well as buttons to be operated when transitioning to various mini app screens, allowing for a smooth transition to the next function to be used.

[0126] The order of screen transitions in the fourth embodiment and the modified example may be set by the user. The order of screen transitions may be arbitrary, such as the first round being the screen transition of the fourth embodiment and the second round being the screen transition of the modified example 1.

[0127] <Fifth embodiment> Next, a fifth embodiment of the present disclosure will be described. It is preferable that the shaking action SH shown in the first to fourth embodiments can be switched between enabled and disabled by a setting operation by the user. As the fifth embodiment, a setting function for the shaking action SH will be described. Note that the configurations of the payment application 200, the user terminal 2, the store terminal 3, and the electronic payment server 5 in the fourth embodiment are the same as those in the first embodiment, so duplicated explanations will be omitted and the same parts will be described with the same reference numerals.

[0128] The setting function of the shake action SH is one of the program modules of the payment application 200, and corresponds to the setting unit 504 shown in Fig. 5(b). That is, the CPU 201 functions as the setting unit 504 by executing the program module.

[0129] The setting unit 504 accepts a setting for switching whether to enable or disable the shake action SH from the user, and stores the setting in the storage unit 204 as setting information for the payment application 200. When 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. When 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, a screen transition based on the shake action SH is not performed.

[0130] (Settings process) The flow of the setting process executed by the payment application 200 of the fifth embodiment will be described with reference to FIG. 14. The process shown in the flowchart of FIG. 14 is written in the program of the payment application 200 installed in the user terminal 2. The program is stored in the storage unit 204, and is called by the CPU 201, and is deployed in the RAM 203 and executed. When the payment application 200 is started and the account button (the button at the bottom right of FIG. 1(a)) displayed on the top screen 101 is operated, the screen transitions to an account management screen. On the account management screen (not shown), various setting menus are provided as operation setting menus of the payment application 200, such as settings related to the shake action SH, as well as volume settings, character size settings, notification settings, language settings, etc. When the user selects the setting of the shake action SH from this setting menu, the CPU 201 starts this flowchart.

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

[0132] In S1402, the CPU 201 acquires setting information related to the currently set shaking action SH from the setting information 240 stored in the storage unit 204. The setting information related to the shaking action SH is information indicating either activation or deactivation. In S1402, the CPU 201 reflects the acquired setting information related to the current shaking action SH on the setting screen 1500.

[0133] Fig. 15 is a diagram showing an example of a setting screen 1500 related to the shaking action SH. As shown in Fig. 15, a button for selecting either Enable 1501 or Disable 1502, and a check mark 1503 indicating the current setting information are displayed on the setting screen 1500. In the example of Fig. 15, the check mark 1503 is displayed next to Enable 1501.

[0134] In S1403, when the user performs a switching operation for the setting related to the shaking action SH (S1403; YES), the process proceeds to S1404. The switching operation is performed by the user selecting either the enable 1501 button or the disable 1502 button displayed on the setting screen 1500. The selection operation is, for example, a tap operation. When the user operates a button different from the current setting, the CPU 201 determines that the shaking action SH has been switched, and the process proceeds to S1404.

[0135] In S1404, the CPU 201 switches the setting related to the shake action SH to the selected setting. For example, when the setting information of the shake action SH acquired in S1402 is "valid" and the user selects "invalid" 1502 on the setting screen 1500, the CPU 201 switches the setting related to the shake action SH to "invalid." Also, for example, when the setting information of the shake action SH acquired in S1402 is "invalid" and the user selects "valid" 1501 on the setting screen 1500, the CPU 201 switches the setting related to the shake action SH to "valid."

[0136] In S1405, the CPU 201 stores the setting information switched in S1404 in the storage unit 204, and ends this flowchart.

[0137] In S1403, if the same button as the current setting is selected, or if the back to previous screen button 1504 is operated, the CPU 201 determines that the shake action SH is not to be switched. In that case, S1404 to S1405 are skipped, and the process of this flowchart ends. In addition, if the back to previous screen button 1504 is operated, the CPU 201 causes the display unit 206 to display the account management screen, which was displayed before the setting screen 1500 was displayed, and then ends the process of this flowchart.

[0138] As described above, according to the payment application 200 of the fifth embodiment, it is possible to switch between enabling and disabling the shake action SH by a setting operation by the user. The setting information of the shake action SH is acquired by the CPU 201 when the payment application 200 is started, and is reflected in the subsequent operation. That is, when the setting information of the shake action SH is set to "enabled", the CPU 201 executes a screen transition based on the shake action SH as shown in the first to fourth embodiments. Also, when the setting information of the shake action SH is set to "disabled", the CPU 201 does not execute a screen transition based on the shake action SH. When the shake action SH is set to "disabled", a screen transition is executed based on a button operation, as in the conventional payment application 200.

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

[0140] 1. Electronic payment systems 2. User terminal 101 Top screen 103 Payment screen 104 Scan Screen 501 Payment processing unit 502 Action detection unit 503 Display control unit 504 Settings SH Shake action

Claims

1. A payment application program that is pre-installed in a terminal device used by a user of electronic payment to use an identification code, the terminal device comprising: A detection unit that detects an action of the user shaking the terminal device; a display control unit that transitions a screen displayed on a display unit of the terminal device to a payment screen used for the electronic payment when the detection unit detects the shaking motion; Function as a the payment screen includes a first payment screen including a user code in which identification information of the user is coded, and a second payment screen for reading a store code in which identification information of a store is coded, 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.

2. the display control unit, when the detection unit detects the shaking motion, transitions a screen to be displayed on the display unit to the first payment screen; The payment application program according to claim 1, 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.

3. the display control unit, when the detection unit detects the shaking motion, transitions a screen to be displayed on the display unit to the second payment screen; The payment application program according to claim 1, 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.

4. A payment application program described in any one of claims 1 to 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.

5. A payment application program described in any one of claims 1 to 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.

6. the display state of the first payment screen includes a first state in which a longitudinal direction of the user code coincides with a longitudinal direction of a 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 1 , wherein the display control unit switches between the first state and the second state each time the detection unit detects the shaking motion.

7. A payment application program that is pre-installed in a terminal device used by a user of electronic payment to use an identification code-based electronic payment, the terminal device comprising: A detection unit that detects an action of the user shaking the terminal device; a display control unit that transitions a screen displayed on a display unit of the terminal device to a payment screen used for the electronic payment when the detection unit detects the shaking motion; Function as a the payment screen is a first payment screen including a user code in which the user's identification information is encoded, the display state of the first payment screen includes a first state in which a longitudinal direction of the user code coincides with a longitudinal direction of a 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 display control unit switches between the first state and the second state and displays the first state and the second state each time the detection unit detects the shaking motion.

8. 8. The payment application program according to claim 1, wherein the user code displayed on the first payment screen includes at least one of a one-dimensional code and a two-dimensional code.

9. A payment application program as described in any one of claims 1, 2, 3, 6, and 7, 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.

10. 10. The payment application program according to claim 9, wherein the screen displayed on the display unit before the payment screen is displayed is a top screen that is displayed immediately after the payment application program is started.

11. 10. The payment application program according to claim 9, wherein the screen displayed on the display unit before the payment screen is displayed is a screen displayed in a function included in the payment application program.

12. When the screen displayed on the display unit before the payment screen is displayed is a screen displayed in a function included in the payment application program, A payment application program as described in claim 1 or 7, characterized in that when the detection unit detects the shaking motion while the payment screen is displayed, the display control unit transitions to a top screen that is displayed immediately after launching the payment application program.

13. 8. The payment application program according to claim 1, further comprising a setting unit that accepts a setting by the user as to whether the shaking action is enabled or disabled.

14. An information processing device used by a user of electronic payment to use an electronic payment using an identification code, A detection unit that detects an action of the user shaking the information processing device; a display control unit that transitions a screen displayed on a display unit of the information processing device to a payment screen used for the electronic payment when the detection unit detects the shaking motion; Equipped with the payment screen includes a first payment screen including a user code in which identification information of the user is coded, and a second payment screen for reading a store code in which identification information of a store is coded, The information processing device, 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.

15. An information processing device used by a user of electronic payment to use an electronic payment using an identification code, comprising: A detection unit that detects an action of the user shaking the information processing device; a display control unit that transitions a screen displayed on a display unit of the information processing device to a payment screen used for the electronic payment when the detection unit detects the shaking motion; Equipped with the payment screen is a first payment screen including a user code in which the user's identification information is encoded, the display state of the first payment screen includes a first state in which a longitudinal direction of the user code coincides with a longitudinal direction of a 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 information processing device, characterized in that the display control unit switches and displays the first state and the second state each time the detection unit detects the shaking motion.

16. An information processing method executed by a computer of a terminal device used by a user of electronic payment to utilize an electronic payment using an identification code, comprising: detecting a motion of the user shaking the terminal device; a step of transitioning a screen displayed on a display unit of the terminal device to a payment screen used for the electronic payment when the shaking motion is detected; Including, the payment screen includes a first payment screen including a user code in which identification information of the user is coded, and a second payment screen for reading a store code in which identification information of a store is coded, The information processing method is characterized in that, each time the shaking motion is detected, the first payment screen and the second payment screen are switched and displayed.

17. An information processing method executed by a computer of a terminal device used by a user of electronic payment to utilize the electronic payment using an identification code, comprising: detecting a motion of the user shaking the terminal device; a step of transitioning a screen displayed on a display unit of the terminal device to a payment screen used for the electronic payment when the shaking motion is detected; Including, the payment screen is a first payment screen including a user code in which the user's identification information is encoded, the display state of the first payment screen includes a first state in which a longitudinal direction of the user code coincides with a longitudinal direction of a 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; An information processing method, comprising: switching between the first state and the second state and displaying the state each time the shaking motion is detected.

Images