Information processing device, method for controlling the information processing device, and program

Abstract

This can improve usability. [Solution] The present invention provides an information processing device comprising: a display control unit that controls the display screen to display an item for displaying a code image usable in a payment application when the display screen of the display unit is locked and user authentication is successful; and a control unit that controls the display screen to display a code image in response to the display control unit detecting an operation on the item.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus, a control method for the information processing apparatus, and a program.

Background Art

[0002] In recent years, some user terminals are equipped with a screen lock function. Patent Document 1 discloses a technique for unlocking the screen without depending on a specific operation by the user.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] There is a demand for a technology capable of improving user experience.

Means for Solving the Problems

[0005] An information processing apparatus according to an aspect of the present disclosure includes a display control unit that performs control to display an item for displaying a code image available in a payment application on the display screen when the display screen in the display unit is in a screen locked state and user authentication is successful, and a control unit that performs control to display the code image on the display screen in response to detecting an operation on the item by the display control unit.

Effects of the Invention

[0006] According to the present disclosure, user experience can be improved.

Brief Description of the Drawings

[0007] [Figure 1]This figure shows an example of the system configuration. [Figure 2] This is a block diagram showing an example of the hardware configuration of an information processing device. [Figure 3] This figure shows an example of the configuration of user terminal functions. [Figure 4] This sequence diagram illustrates an example of the process by which a user's device goes from a screen-locked state to displaying the payment application screen. [Figure 5] This figure shows an example of a lock screen that appears after the user's device is started up. [Figure 6] This figure shows an example of a wallet application screen. [Figure 7] This figure shows an example of a payment screen for performing a payment using the store scan procedure in a payment application. [Figure 8] This flowchart shows an example of a process performed by the operating system. [Figure 9] This flowchart shows an example of the processes performed by a wallet application. [Figure 10] This flowchart shows an example of the process performed by a payment application. [Figure 11] This diagram illustrates how to find the icon corresponding to a payment application. [Figure 12] This figure shows an example of elements that appear on an item. [Figure 13] This diagram shows an example of displaying items corresponding to the payment application depending on the method of electronic money transfer. [Figure 14] This figure shows an example where the display of an item changes in response to a specific user action. [Modes for carrying out the invention]

[0008] Preferred embodiments of the information processing apparatus, control method for the information processing apparatus, and program relating to this disclosure will be described in detail below with reference to the drawings. However, the information processing apparatus, control method for the information processing apparatus, and program relating to this disclosure are not limited to the embodiments described below. Furthermore, identical components are denoted by the same reference numerals in the following embodiments, and redundant descriptions are omitted.

[0009] In recent years, payment methods using user terminals have become increasingly popular due to their high level of convenience. Users can make payments by having a store terminal read a code image displayed on their user terminal, or by having their user terminal read a code image placed in the store.

[0010] For example, a user can make such a payment by installing an application with payment (including money transfer) functionality (hereinafter referred to as a payment application) on their terminal and launching the payment application.

[0011] Incidentally, some user terminals are equipped with a screen lock function to prevent the leakage of personal information. A screen lock function is a function that restricts the functions that can be performed on the user terminal. For example, when the screen lock function is enabled, the user can use certain functions of the user terminal, but cannot use other functions. Once the user performs an operation for user authentication, such as entering a passcode, and the screen lock is released, the user can use all the functions provided by the user terminal.

[0012] Furthermore, from a convenience standpoint, it is desirable for users to be able to make frequent payments in their daily lives smoothly. Therefore, technologies that unlock the screen without requiring specific user actions such as entering a passcode are known.

[0013] However, in such a technology, even after the screen lock is released, the user may need to search for an application that provides functions for purposes such as payment, and further perform a predetermined operation after starting the application.

[0014] Hereinafter, a technique for displaying a code image used for payment by a specific operation of the user from a screen (hereinafter referred to as a lock screen) displayed when the screen lock function is valid will be described. This can improve user convenience.

[0015] <<First Embodiment>> FIG. 1 is a diagram showing an example of the configuration of the system in the present disclosure. The system shown in FIG. 1 includes a user terminal 101, a payment server 102, and a store terminal 103. The user terminal 101, the payment server 102, and the store terminal 103 are communicably connected via a network 104. Examples of the network 104 include a LAN (Local Area Network) and a WAN (Wide Area Network).

[0016] In the system shown in FIG. 1, the case where there is one user terminal 101 and one store terminal 103 each will be described as an example, but there may be two or more user terminals 101 and store terminals 103 each.

[0017] (Regarding the user terminal) User terminal 101 is a terminal device owned by a user who uses the payment service described later. A payment application is installed on user terminal 101. By running the payment application on user terminal 101, payment services can be provided to users using user terminal 101. In this disclosure, user terminal 101 is explained using a smartphone as an example. However, user terminal 101 may be a notebook PC or a tablet device. In other words, user terminal 101 can be any information processing device capable of running a payment application. In addition, applications other than the payment application and the wallet application described later may be installed on user terminal 101, and these applications may also be run.

[0018] A payment service is a service that processes payments by transferring electronic money equivalent to the payment amount from the user's account to the merchant's account. Furthermore, payment services also include remittance services, which process remittances by transferring electronic money from the first account held by the sending user (the first user) to the second account held by the receiving user (the second user).

[0019] The payment application has functions such as displaying a code image used during payment and providing services related to payment services. Furthermore, the payment application can generate a code image based on a one-time code, as described later. A code image is an image generated by encoding (one-dimensional or two-dimensional encoding) information such as a string. In addition, the payment application can read the code image using the camera unit provided on the user terminal 101 and provide the read information to the payment server 102.

[0020] Furthermore, the user terminal 101 has a wallet function. The wallet function is a function that allows the user to use multiple payment-related functions in one place. The functions available through the wallet function include the use of point cards, electronic tickets, transportation IC cards, electronic money cards, credit cards, or debit cards. In this disclosure, the wallet function will be explained using the example of being provided by an application (hereinafter referred to as the wallet application). However, the wallet function may also be provided by a function of the OS (Operating System) of the user terminal 101.

[0021] The wallet application, through its functionality, can display information about applications, including payment applications, installed on the user terminal 101. For example, the wallet application can retrieve information about applications configured within that application and display the retrieved information.

[0022] In this disclosure, the user terminal 101 can place an icon for using the wallet function (hereinafter referred to as the wallet icon) on the lock screen using a setting function provided by the OS (for example, sometimes referred to as a widget function). By placing the wallet icon on the lock screen using the setting function, the user can access the wallet function from the locked screen state. The setting function may also be provided by an application. Furthermore, the OS functions including the wallet function and the setting function may be provided on the user terminal 101 as a single function (an OS function or an application function).

[0023] (Regarding the payment server) The payment server 102 generates one-time codes in response to requests from user terminals 101 and performs payment processing in response to requests from store terminals 103, which will be described later. A one-time code is a code with an expiration date that is generated by the payment server 102 in response to a request from a payment application. The generated one-time code is linked to a user ID registered with the payment server 102 and managed by the payment server 102. When the expiration date of the one-time code has passed, the payment application can request the payment server 102 to generate a new one-time code.

[0024] (Regarding store post boxes) The store terminal 103 is a terminal device used by store employees. The store terminal 103 requests payment processing from the payment server 102 by, for example, scanning a code image displayed on the payment application of the user terminal 101. Specifically, the store terminal 103 transmits the one-time code obtained by scanning the code image, along with the store ID and payment amount, to the payment server 102 via the POS (Point of Sales) system. The payment server 102 then processes the payment by transferring electronic money equivalent to the payment amount from the user's account corresponding to the user ID linked to the one-time code to the store's account corresponding to the store ID. Details of the payment processing and remittance processing will now be explained.

[0025] (Regarding payment processing) There are two steps involved in processing a payment: the store scan procedure and the user scan procedure. Each procedure will be explained below.

[0026] [Store Scan Procedure] The user presents the code image displayed on the payment application on the user terminal 101 to the store clerk. The store clerk then scans the code image displayed on the payment application on the user terminal 101 with the store terminal 103, which then makes the above-described request to the payment server 102. Subsequently, the payment server 102 performs the payment processing. In other words, payment by the store scan procedure is a payment using a one-time code. In this embodiment, payment will be explained using the store scan procedure as an example.

[0027] [User Scan Procedure] Store staff place printed materials in the store that contain a code image embedded with store information to identify the store. Users read the code image from the printed materials placed in the store using the scanning function of the payment application on the user terminal 101. After the user enters the payment amount, the user terminal 101 sends the user ID, acquired store information, and payment amount to the payment server 102. The payment server 102 then processes the payment. In other words, payment using the user scan procedure does not use one-time codes.

[0028] (Regarding the remittance process) The first user, who is the sender, uses the scanning function of the payment application on the first user's terminal to read the code image displayed on the second user's terminal, who is the recipient. The code image displayed on the second user's terminal contains the second user's identification information linked to the second user's account. The first user then enters the amount to send, and the first user's terminal sends the retrieved second user identification information and the amount to the payment server 102. The payment server 102 then processes the transfer.

[0029] (Hardware configuration of information processing equipment) The user terminal 101, payment server 102, and store terminal 103 described above are implemented by an information processing device 200 ("an example of a computer") with a configuration as shown in Figure 2. Figure 2 is a block diagram showing an example of the hardware configuration of the information processing device 200. The information processing device 200 has a CPU 201, ROM 202, RAM 203, storage device 204, input / output I / F 205, and network interface (I / F) 207. These components are connected to each other by a system bus. An operation unit 206 is also connected to the input / output I / F 205.

[0030] The CPU 201 reads programs stored in the ROM 202 and the memory device 204 into the RAM 203, and executes the read programs to perform various controls. The CPU 201 may be an MPU (Micro Processing Unit) or an ASIC (application-specific integrated circuit). The CPU 201 may also be an FPGA (Field Programmable Gate Array), etc.

[0031] ROM202 stores control programs such as the startup program for the information processing device 200. RAM203 is used as work memory to temporarily store control programs or data when the CPU201 performs various control operations.

[0032] The storage device 204 is memory for storing applications, software, and various data. Examples of storage devices 204 include HDDs (Hard Disk Drives), SSDs (Solid State Drives), flash memory, and storage devices. If the storage device 204 is a user terminal 101, it stores payment applications and wallet applications, etc.

[0033] The input / output interface 205 is an interface for sending output information to the control unit 206 and receiving input information from the control unit 206. The control unit 206 includes an output unit and an input unit.

[0034] The output unit can display images as a display unit (e.g., a screen) or output sound as an audio output unit. The display unit and audio output unit may be provided in the information processing device 200 or outside the information processing device 200. If the display unit has a touch panel function, it functions as an input unit.

[0035] The input unit can input control information to the input / output interface 205 as a pointing device or physical operation key, or input audio information to the input / output interface 205 as an audio input unit. The input unit may be provided in the information processing device 200 or outside the information processing device 200. The input / output interface 205 may be configured as an input interface and an output interface.

[0036] Network I / F 207 is an interface for receiving data from other devices via network 104 and transmitting data generated or stored by the information processing device 200 to other devices via network 104.

[0037] Note that the information processing device 200 is not limited to the configuration shown in Figure 2. For example, a user terminal 101 may be equipped with a camera unit to implement camera functionality. A store terminal 103 may be equipped with a scanning unit to scan code images.

[0038] The information processing device 200 may also be equipped with a media interface (not shown). The media interface reads programs and data stored in a storage device (not shown) connected by wire or wireless, and provides them to the CPU 201 via RAM 203. The CPU 201 can read the provided program from the storage device onto RAM 203 via the media interface and execute the read program. The storage device is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or PD (Phase Change Rewritable Disk), or a magneto-optical recording medium such as an MO (Magneto-Optical disk). Alternatively, the storage device may be a tape medium, a magnetic recording medium, or a semiconductor memory.

[0039] The CPU 201 of the information processing device 200 reads and executes these programs from the storage device, but as an alternative, these programs may be obtained from other devices via a predetermined communication network. Furthermore, it goes without saying that the information processing device 200 is provided with the necessary configurations to realize the information processing in this embodiment.

[0040] (An example of the user terminal's functional configuration) Figure 3 shows an example of the configuration of the user terminal 101's functions. The user terminal 101 has a display control unit 311, a control unit 312, a setting unit 313, and an authentication unit 314 as functions of the OS 310. The user terminal 101 also has a communication unit 300, a payment application 320, and a wallet application 330.

[0041] The communication unit 300 transmits information and data to other devices and receives information and data from other devices via the network 104. For example, the communication unit 300 can send a request for a one-time code to the settlement server 102 via the network 104 and receive a one-time code generated by the settlement server 102.

[0042] The display control unit 311 can display the lock screen or the screen that appears after the screen lock is released (hereinafter referred to as the home screen), and can detect user operations on the display unit.

[0043] The control unit 312 can issue a startup command to a predetermined application when it detects a user operation on a predetermined icon by the display control unit 311, or when it receives a predetermined notification. In other words, the control unit 312 can control applications and software operated on the OS 310. The control unit 312 also controls whether to enable or disable the screen lock function.

[0044] The configuration unit 313 can configure settings for applications and software operated on the OS 310. For example, the configuration unit 313 can configure settings for each application, such as whether or not to provide information acquired by the user terminal 101 to the application, and whether to notify the application when update data is acquired.

[0045] Furthermore, the settings unit 313 can change the configuration of the lock screen and home screen, or change the arrangement of icons corresponding to applications, in response to user operations. For example, if a user performs an operation (e.g., long-press) on an area of ​​the home screen where no icons are placed, a selection area will be displayed for changing the configuration of the lock screen or home screen, or the arrangement of icons. If the user wants to change the configuration of the lock screen, for example, they can select a configuration for the lock screen in that selection area, thereby placing specific icons on the lock screen.

[0046] The authentication unit 314 performs user authentication and determines whether the user authentication is successful or not. User authentication in this disclosure will be explained using facial recognition as an example. However, user authentication in this disclosure is not limited to facial recognition and may also be biometric authentication such as fingerprint authentication, voiceprint authentication, vein authentication, and iris authentication, authentication by entering a passcode, pattern authentication, or authentication by reading an ID card or other personally identifiable card.

[0047] The wallet application 330 is an application that provides wallet functionality to the user. For example, the wallet application 330 can provide payment functionality based on information from other applications and card information registered with this application. As for the payment application 320, as described above, its explanation will be omitted.

[0048] (The process of displaying the payment application screen) Figure 4 is a sequence diagram showing an example of the process by which the user terminal 101 displays the payment application 320 screen from a screen-locked state.

[0049] In S401, after the user terminal 101 is started up, the display control unit 311 displays a lock screen as shown in Figure 5 on the display unit of the user terminal 101. The lock screen may also be displayed when the user terminal 101 wakes up from sleep mode (when the display screen turns on).

[0050] Figure 5 shows an example of a lock screen displayed after the user terminal 101 is started up. The lock screen 500 shown in Figure 5 is provided with a wallet icon 501. The wallet icon 501 is an icon for displaying the screen of the wallet application 330. The wallet icon 501 is also an icon set by the setting function of the setting unit 313.

[0051] Returning to Figure 4, in S402, the display control unit 311 detects user operation on the wallet icon 501 provided on the displayed lock screen 500. In other words, we will explain using the operation on the wallet icon 501 as an example to trigger user authentication in order to unlock the screen.

[0052] Furthermore, the user can unlock the screen without performing any action on the wallet icon 501, that is, without launching the wallet application 330. Unlocking the screen through this method is referred to as normal screen unlocking. For example, as an action to unlock the screen in the normal way, the user performs a specific action on the lock screen, an action on a specific icon on the lock screen, or an action on a physical key on the user terminal 101. After this, user authentication is performed as described later. If this user authentication is successful, the screen lock is released. When the screen lock is released in the normal way, the wallet application 330 is not launched, and the top home screen is displayed.

[0053] In S403, the authentication unit 314 performs user authentication in response to the display control unit 311 detecting a user operation on the wallet icon 501 in S402. For example, in the case of facial recognition, the authentication unit 314 activates the camera unit provided on the user terminal 101 so as to face the user. The authentication unit 314 then performs user authentication based on the image of the user's face acquired via the camera unit and the user's facial image pre-configured in the setting unit 313.

[0054] In S404, if the authentication unit 314 successfully authenticates the user in S403, the control unit 312 issues a startup command to the wallet application 330. Also, if the authentication unit 314 successfully authenticates the user in S403, the screen lock is released. This makes it possible to use other applications, including the wallet application 330.

[0055] In S405, the wallet application 330 is started in response to a startup command from OS310 in S404, and displays the wallet application screen as shown in Figure 6.

[0056] Figure 6 shows an example of the screen of the wallet application 330. The wallet application screen 600 shown in Figure 6 is provided with item 610 corresponding to the payment application 320 and item 620 corresponding to a credit card. In other words, the payment application 320 and the credit card information of Company XXX are pre-registered in the wallet application 330. Based on this registration information, items 610 and 620 are displayed on the wallet application screen 600.

[0057] Item 610 displays the logo for the payment application 320 and the balance of the electronic money available through the payment application 320. This allows the user to see at a glance whether they can pay with the payment application 320 when making a payment. Item 620 also displays a diagram representing the credit cards available to the user through the wallet function.

[0058] Returning to Figure 4, in S406, if the wallet application 330 detects a user operation on an item on the wallet application screen 600, it notifies the OS 310 of the user operation on the operated item. In this disclosure, the example given is that item 610 was operated on by the user.

[0059] In S407, the control unit 312, having received notification of a user operation on item 610 in S406, issues a startup command to the payment application 320 for item 610. The control unit 312 can specify the screen that the payment application 320 will display by including a code in the startup command that corresponds to a specific screen that can be displayed by the payment application 320. In this embodiment, S407 will be explained using the example of specifying the screen for making a payment in the store scan procedure.

[0060] In S408, the payment application 320 starts up in response to a startup instruction from the OS 310 in S407 and requests a one-time code from the payment server 102. However, the request for a one-time code does not necessarily have to be made when the payment application 320 starts up. For example, if the startup instruction includes a code corresponding to the screen for making a payment using the user scan procedure, there is no need to generate a code image, so the payment application 320 does not request a one-time code from the payment server 102 in S408.

[0061] In S409, the payment server 102 generates a one-time code in response to the request in S408 and sends the generated one-time code to the payment application 320 on the user terminal 101, which is the requesting party.

[0062] In S410, the payment application 320 generates a code image by encoding the one-time code received in S409, and displays the payment application screen on which the generated code image is placed, as shown in Figure 7. When making a payment, the user presents the payment screen 700 displayed on the user terminal 101 to the store clerk.

[0063] Figure 7 shows an example of a payment application screen (hereinafter referred to as the payment screen) for making payments using the store scan procedure. The payment screen 700 shown in Figure 7 displays a one-dimensional code image 710 and a two-dimensional code image 711 generated from a one-time code, as well as the balance 712 of the electronic money available in the payment application 320.

[0064] The payment screen 700 also includes a "Scan and Pay" button 720 and a "Close" button 730. Button 720 is a button that transitions to a screen (not shown) for performing payment using the user scan procedure. The "Close" button 730 is a button that closes the payment screen 700. When the payment application 320 detects an operation on the "Close" button 730, it closes the payment screen 700. After the payment screen 700 is closed, the top screen of the payment application 320 is displayed. Alternatively, the top home screen may be displayed after the payment screen 700 is closed.

[0065] Returning to Figure 4, at S411, the store terminal 103 reads the code image displayed on the payment screen 700 presented by the user. The store terminal 103 then analyzes the read code image to obtain a one-time code.

[0066] In S412, the store terminal 103 transmits the one-time code obtained in S411, the store ID for identifying the store, and the payment amount to the payment server 102.

[0067] In S413, the payment server 102 executes the payment process based on the one-time code, store ID, and payment amount obtained in S412. For example, in S413, the payment server 102 identifies the user's account linked to the one-time code and the store's account linked to the store ID, and then performs a process to transfer electronic money equivalent to the payment amount from the user's account to the store's account.

[0068] Figure 8 is a flowchart showing an example of the processing performed by the OS310 in this embodiment. The processing shown in Figure 8 is achieved when the CPU201 of the user terminal 101 reads a program stored in the ROM202 or storage device 204 into the RAM203 and executes the read program. The processing shown in Figure 8 is started when the user terminal 101 is started up or wakes up from sleep mode.

[0069] In S801, the CPU 201, using the display control unit 311, displays the lock screen 500 on the display unit of the user terminal 101, and then proceeds to S802.

[0070] In S802, the CPU 201, using the display control unit 311, determines whether or not the wallet icon 501 on the lock screen 500 has been operated. If the CPU 201 determines in S802 that the wallet icon 501 has been operated (Yes), it proceeds to S803. If the CPU 201 determines in S802 that the wallet icon 501 has not been operated (No), it returns to S802 and repeats the determination until the wallet icon 501 is operated.

[0071] In S803, the CPU 201, in response to the authentication unit 314 detecting an operation on the wallet icon 501 in S802, performs user authentication and proceeds to S804. For example, in the case of facial recognition, the authentication unit 314 activates the camera unit as described above and performs user authentication based on the image of the user's face acquired through the camera unit and the user's face image pre-configured in the setting unit 313.

[0072] Furthermore, for other authentication methods, the authentication unit 314 can perform user authentication by displaying a screen corresponding to that authentication method or by activating a function unit provided on the user terminal 101.

[0073] In S804, the CPU 201 determines, based on the results of user authentication performed in S803, whether user authentication was successful or not, using the authentication unit 314. If the CPU 201 determines in S804 that user authentication was successful (Yes) using the authentication unit 314, the process proceeds to S805. If the CPU 201 determines in S804 that user authentication was not successful (No), i.e., that user authentication failed, the process returns to S802. If the result in S804 is (No), the display control unit 311 may display a message indicating that user authentication failed on the lock screen. The authentication unit 314 may then perform user authentication again with the user's consent (for example, by the user's operation on a button to re-execute user authentication).

[0074] In S805, the CPU 201, via the control unit 312, issues a startup command to the wallet application 330, and the process proceeds to S806.

[0075] In S806, the CPU 201, via the control unit 312, determines whether or not it has received a notification from the wallet application 330 regarding a user operation for an item corresponding to the payment application 320. If the CPU 201 determines in S806, via the control unit 312, that it has received a notification from the wallet application 330 regarding a user operation for an item corresponding to the payment application 320 (Yes), it proceeds to S807. If the CPU 201 determines in S806, via the control unit 312, that it has not received a notification from the wallet application 330 regarding a user operation for an item corresponding to the payment application 320 (No), it returns to S806 and repeats the determination until it receives this user operation notification.

[0076] In S807, the CPU 201, via the control unit 312, issues a startup command to the payment application 320 in response to the user operation notification received in S806, and terminates this flow. In S807, as described above, the control unit 312 specifies the screen that the payment application 320 will display by including a code corresponding to a specific screen that the payment application 320 can display (for example, the payment screen 700) in the startup command.

[0077] Figure 9 is a flowchart illustrating an example of the processing performed by the wallet application 330 in this embodiment. The processing shown in Figure 9 begins after the wallet application 330 is started in response to a startup command from the OS 310. In Figure 9, the explanation uses the example of a user operation being performed on an item 610 corresponding to the payment application 320.

[0078] In S901, CPU201 displays the wallet application screen 600 via the wallet application 330, and then proceeds to S902.

[0079] In S902, the CPU 201 determines whether an item on the wallet application screen 600 has been manipulated by the wallet application 330. If the CPU 201 determines in S902 that an item on the wallet application screen 600 has been manipulated by the wallet application 330 (Yes), the process proceeds to S903. If the CPU 201 determines in S902 that an item on the wallet application screen 600 has not been manipulated by the wallet application 330 (No), the process returns to S902 and repeats the determination until the item is manipulated.

[0080] In S903, the CPU201, via the wallet application 330, notifies the OS310 of the user operation on item 610 manipulated in S902, and then proceeds to S904.

[0081] Note that for cards such as credit cards, debit cards, point cards, or transportation IC cards that are configured in the wallet application 330 and do not require the application to be launched, no notification of user operation will be sent to the S903. For example, if item 620 is operated, the wallet application 330 on the S903 will display a screen for using the credit card corresponding to item 620.

[0082] In S904, the CPU 201 controls the wallet application 330 to close the wallet application screen 600, thereby terminating this flow. Note that in S904, the wallet application 330 does not necessarily have to close the wallet application screen 600.

[0083] Figure 10 is a flowchart illustrating an example of the processing performed by the payment application 320 in this embodiment. The processing shown in Figure 10 begins after the payment application 320 is started in response to a startup instruction from the OS 310, which has received a user operation notification from the wallet application 330. In Figure 10, the display of the payment screen 700 is used as an example for explanation.

[0084] In S1001, the CPU 201 requests a one-time code from the payment server 102 via the payment application 320, and proceeds to S1002. In S1002, the CPU 201 receives the one-time code generated in response to the request in S1001 from the payment server 102 via the payment application 320, and proceeds to S1003.

[0085] In S1003, the CPU 201 displays the payment screen 700 using the payment application 320 and proceeds to S1004. Specifically, in S1003, the CPU 201 generates a code image by encoding the one-time code received in S1002 using the payment application 320. Then, in S1003, the CPU 201 displays the payment screen 700 on which the generated code images (for example, a one-dimensional code image 710 and a two-dimensional code image 711) are placed using the payment application 320.

[0086] In S1004, the CPU 201 determines whether the close button 730 has been pressed by the payment application 320. If the CPU 201 determines in S1004 that the close button 730 has been pressed by the payment application 320 (Yes), it closes the payment screen 700 and terminates this flow. If the CPU 201 determines in S1004 that the close button 730 has not been pressed by the payment application 320 (No), it returns to S1004 and repeats the determination until the close button 730 is pressed. If the button 720 on the payment screen 700 is pressed, the payment application 320 displays a screen for performing payment using the user scan procedure.

[0087] In this way, the user operates the wallet icon from the lock screen, and then operates the corresponding item in the payment application 320 that is displayed, which brings up the payment screen. This allows the user to make payments smoothly.

[0088] By displaying the payment screen during this process, users can avoid the hassle of searching for the payment application from the home screen displayed after unlocking the screen, and the hassle of transitioning to the payment screen after launching the payment application.

[0089] Figure 11 illustrates the process of searching for the icon corresponding to the payment application 320. Figure 11(a) shows an example of the home screen of the user terminal 101. The home screen 1100 shown in Figure 11(a) is the top home screen (first home screen) displayed after unlocking the screen. The home screen 1100 has multiple icons corresponding to applications installed on the user terminal 101, but there is no icon corresponding to the payment application 320. User operation on the home screen 1100 (for example, a swipe operation) causes the screen to transition from the home screen 1100 to the home screen shown in Figure 11(b).

[0090] Figure 11(b) shows an example of the home screen of the user terminal 101. The home screen 1110 shown in Figure 11(b) is a screen (second home screen) that can be accessed from the home screen 1100. The home screen 1110 has multiple icons corresponding to applications installed on the user terminal 101, including icon 1111 corresponding to the payment application 320.

[0091] Thus, in order for the user to launch the payment application 320, they need to navigate to the home screen where the corresponding icon 1111 is located after unlocking the screen, and then find the icon 1111.

[0092] Note that icon 1111 may be placed on the top home screen (home screen 1100). Even in this case, displaying the payment screen 700 may require several screen transitions from the top screen of the payment application 320, which is displayed after the application is launched. These screen transitions may require user interaction.

[0093] In other words, while the usual method requires the user to go through a lot of trouble to display the payment screen 700 after unlocking the screen, in this embodiment, the payment screen 700 can be displayed by operating an item 610 on the wallet application screen 600.

[0094] According to this embodiment, the payment screen of a payment application can be displayed from the lock screen. This improves usability.

[0095] <<Second Embodiment>> In the first embodiment, it was explained that when user authentication is successful, the wallet application 330 displays items corresponding to the payment application 320, etc. In this embodiment, a different method of displaying items from the first embodiment will be described.

[0096] The basic configurations of the user terminal 101, payment server 102, and store terminal 103 in this embodiment are the same as those of the devices in the first embodiment, so their description will be omitted.

[0097] Figure 12 shows an example of elements displayed on an item. Figure 12(a) shows an example where a logo 1201 indicating the payment application 320 is displayed as an element of item 1200 corresponding to the payment application 320. Figure 12(b) shows an example where a logo indicating the payment application 320 and a 2D code image 1211 are displayed as elements of item 1210 corresponding to the payment application 320. The 2D code image 1211 is, for example, a dummy code image and is a code image that cannot be read by the store terminal 103. However, the 2D code image 1211 may be readable by the store terminal 103. In addition, elements of the item corresponding to the payment application 320 include the motif character of the payment application 320, illustrations, strings of text, shapes, or combinations thereof.

[0098] In this way, displaying elements related to the payment application 320, or elements that the user can recognize as payment-related items, enables the user to select items smoothly. Furthermore, displaying such elements is useful if the user does not want others to see the balance available in the payment application 320.

[0099] Figure 13 shows an example of displaying items corresponding to the payment application 320 according to the method of electronic money transfer. The wallet application screen 1300 shown in Figure 13 displays item 1301 for making an immediate payment via the store scan procedure and item 1302 for making a deferred payment via the store scan procedure. The wallet application screen 1300 also displays item 1303 for making a payment via the user scan procedure and item 1304 for sending electronic money to other users using the payment application 320.

[0100] Instant payment refers to a payment method where, when a user makes a payment, the electronic money equivalent to the payment amount is immediately deducted from the balance of the payment application 320. Post-payment refers to a payment method where, for example, on a fixed day each month, the electronic money equivalent to the transaction amount for transactions made during a certain period is deducted from the account linked to the payment application 320.

[0101] When item 1301 is operated, a payment screen for immediate payment is displayed. When item 1302 is operated, a payment screen for deferred payment is displayed. These payment screens display a one-dimensional code and a two-dimensional code generated by encoding a one-time code, similar to payment screen 700.

[0102] When item 1303 is operated, a reading screen is displayed for reading the code image placed in the store. This screen is the same as the screen displayed when button 720 on payment screen 700 is operated.

[0103] Furthermore, when item 1304 is manipulated, a screen (not shown) is displayed for sending electronic money to other users registered by the user. From this screen, the user can select another registered user as the recipient and enter the amount to send, thereby sending electronic money equivalent to that amount to the recipient user.

[0104] Thus, when the same application (for example, the payment application 320) offers multiple different methods for transferring electronic money, the wallet application 330 can change the display mode and number of items according to the method, and display these items accordingly. This allows the user to smoothly select a payment method according to the situation.

[0105] Figure 14 illustrates an example where the display of an item changes in response to a specific user action. Figure 14(a) shows item 1400, which is used for instant payment via the store scan procedure. When the user performs a specific action on item 1400 (e.g., a swipe), item 1400 switches to item 1410, which is used for deferred payment via the store scan procedure, as shown in Figure 14(b). Furthermore, when item 1410 shown in Figure 14(b) is operated on by the user (e.g., a tap), the deferred payment screen is displayed.

[0106] In this way, when a specific operation is performed on an item corresponding to a payment application, the item switches to one that corresponds to a different electronic money transfer method from the one displayed before the specific operation was performed, among the electronic money transfer methods available in the payment application 320. This allows items to be displayed without encroaching on the display area where the items are displayed.

[0107] Furthermore, the display configuration of the items shown in Figures 12 to 14 may be changed by user configuration. Alternatively, the display configuration of the items shown in Figures 12 to 14 may be set as the default when registering with the wallet application 330.

[0108] According to this embodiment, the wallet application can change the display mode of items and display items corresponding to the electronic money transfer methods available in the payment application, while achieving the same effects as in the first embodiment.

[0109] <<Other Embodiments>> In the above-described embodiment, the wallet application screen 600 is displayed in response to an operation on the wallet icon 501 provided on the lock screen 500, and the payment screen 700 with a code image is displayed in response to an operation on an item on that screen. However, the method of displaying a screen for transferring electronic money, such as the payment screen 700, is not limited to this.

[0110] <Example 1> For example, on the lock screen 500, an icon for displaying the payment screen 700 is placed in place of the wallet icon 501. This configuration can be achieved by the user changing the configuration of the lock screen 500. When the display control unit 311 detects the user's operation on the icon for displaying the payment screen 700, the authentication unit 314 performs user authentication. If the authentication unit 314 succeeds in user authentication, the control unit 312 issues a startup command to the payment application 320. The payment application 320 starts up in response to the startup command from the OS 310, and when it receives a one-time code from the payment server 102, it displays the payment screen 700. In other words, the payment screen 700 may be displayed without the wallet application screen 600 on which the items are placed being displayed (without the wallet application 330 being started).

[0111] <Modification 2> A code image usable by the payment application 320 may be placed on the lock screen 500. This placement can be achieved by the user changing the configuration of the lock screen 500.

[0112] For example, if a code image can be generated based on information that uniquely identifies the user handled by the payment application 320 (e.g., user ID) without receiving a one-time code from the payment server 102, the code image usable by the payment application 320 is placed on the lock screen 500. This code image may or may not be readable by the store terminal 103.

[0113] Here, we assume a case where the code image placed on the lock screen 500 is processed and displayed in a way that makes it unreadable by the store terminal 103. In this case, when the display control unit 311 detects a user operation on the code image, the authentication unit 314 performs user authentication. If the authentication unit 314 succeeds in user authentication, the control unit 312 issues a startup command to the payment application 320. Then, the payment screen 700 is displayed. Alternatively, if the authentication unit 314 succeeds in user authentication, the display control unit 311 may close the lock screen 500 and display the code image processed to be readable by the store terminal 103 on the home screen. In this way, regardless of whether user authentication is successful or not, or immediately after successful user authentication, the code image usable by the payment application 320 is displayed, allowing the user to make payments smoothly.

[0114] Furthermore, the configuration of the aforementioned information processing device 200 can be flexibly changed, for example, by calling external platforms via APIs or network computing depending on the function.

[0115] Furthermore, the embodiments described above can be combined as appropriate, as long as the processing content is not contradictory. [Explanation of symbols]

[0116] 200 Information Processing Devices 320 Payment Applications 330 Wallet Applications

Claims

1. An information processing device that provides a payment service and executes a payment application that operates on an OS, and a wallet function that can provide payment-related functions including the functions of the payment application, wherein the wallet function is provided as a function of the OS, A storage unit in which the OS stores payment information, including information about the payment application registered in the wallet function, When the display screen in the display unit is in a screen-locked state and user authentication is successful by the OS function, the display control unit controls the wallet function to display an item on the display screen for displaying a code image usable in the payment application, based on the information stored in the storage unit. The display control unit detects an operation on the item, and in response, the OS launches the payment application, and the control unit controls the launched payment application to display the code image on the display screen. An information processing device characterized by comprising:

2. The information processing device according to claim 1, characterized in that the code image is a code image generated by encoding a one-time code received from a payment server providing the payment application.

3. The information processing apparatus according to claim 2, characterized in that the control unit performs control to display the payment screen of the payment application on which the code image is placed, in response to the display control unit detecting an operation on the item.

4. The information processing apparatus according to any one of claims 1 to 3, characterized in that the display control unit performs the control when the user authentication performed by the OS in response to an operation on a specific icon provided on the lock screen is successful.

5. The aforementioned specific icon is an icon corresponding to the wallet application, which is an application provided by the OS as the wallet function. The information processing apparatus according to claim 4, characterized in that, if the user authentication is successful, the display control unit controls the display of the screen of the wallet application on which the item is provided.

6. If the user authentication is successful, The display control unit does not perform the control, The information processing apparatus according to claim 4, characterized in that the control unit gives a startup instruction to the payment application that displays the code image.

7. If the user authentication is successful, the display control unit performs control to display at least one of the delivery items, which are items corresponding to each of the multiple delivery methods of electronic money available in the payment application, including the item. The information processing apparatus according to claim 1, characterized in that, upon detection of an operation on the item to be delivered by the display control unit, the control unit performs control to display a screen for delivering electronic money using a delivery method corresponding to the item that was operated on.

8. The display control unit, A first display corresponding to a first delivery method, which is one of several delivery methods for electronic money usable in the aforementioned payment application, is applied to the item. The information processing device according to claim 1, characterized in that, when a first operation is detected on the item in the state of the first display, a second display corresponding to a second delivery method, which is a method among the delivery methods different from the first delivery method, is displayed on the item.

9. The control unit, When the display control unit detects a second operation on the item in the first display state, it performs control to display a screen corresponding to the first transfer method. The information processing apparatus according to claim 8, characterized in that when the display control unit detects a second operation on the item in the state of the second display, it performs control to display a screen corresponding to the second transfer method.

10. The first operation is a swipe operation, The information processing apparatus according to claim 9, characterized in that the second operation is a tap operation.

11. The information processing device according to claim 7 or 8, characterized in that the multiple methods for transferring the electronic money include a method for making a payment immediately by store scan procedure, a method for making a payment later by store scan procedure, a method for making a payment by user scan procedure, and a method for sending electronic money to another user using the payment application.

12. The information processing device according to claim 1 or 2, characterized in that the item displays a logo indicating the payment application and a balance available in the payment application.

13. If user authentication performed on the aforementioned lock screen without any operation on the specific icon is successful, The display control unit does not perform the control, The information processing apparatus according to claim 5, characterized in that the control unit performs control to display a home screen on which icons corresponding to the payment application are arranged.

14. When an operation is performed on the aforementioned icon, the control unit issues a startup command to the payment application. The information processing device according to claim 13, characterized in that, in the payment application launched in response to the launch instruction, if an operation to transition to the payment screen of the payment application is performed on the top screen of the payment application, the device transitions to the payment screen.

15. A control method for an information processing device that provides a payment service and executes a payment application that operates on an OS, and a wallet function that provides payment-related functions including the functions of the payment application, wherein the wallet function is provided as a function of the OS, A storage step in which the OS stores payment information, including information about the payment application registered in the wallet function, When the display screen in the display unit is in a screen-locked state and user authentication is successful by the OS function, a display control step is performed to control the wallet function to display an item on the display screen for displaying a code image usable by the payment application, based on the information stored in the storage step. A control step in which the OS launches the payment application in response to detecting an operation on the item in the display control step, and controls the launched payment application to display the code image on the display screen. A control method characterized by having the following features.

16. A wallet function that provides payment services and offers payment-related functions including the functions of a payment application that runs on the OS, and an information processing device that executes the wallet function provided as a function of the OS, A storage unit in which the OS stores payment information, including information about the payment application registered in the wallet function, When the display screen in the display unit is in a screen-locked state and user authentication is successful by the OS function, the display control unit controls the wallet function to display an item on the display screen for displaying a code image usable in the payment application, based on the information stored in the storage unit. The display control unit detects an operation on the item, and in response, the OS launches the payment application, and the control unit controls the launched payment application to display the code image on the display screen. A program characterized by being designed to function as such.

Images