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

Abstract

To suppress fraudulent activity in electronic payment services. [Solution] A payment application program installed on a terminal device used by an electronic payment user has a display control unit that controls a screen displayed on the display unit of the terminal device, and the screen includes a first screen for inputting the amount to be paid or sent by the electronic payment, and a second screen which includes a string of characters indicating the amount, a predetermined message, a first button for instructing the execution of the payment or transfer of the amount, and a second button for canceling the payment or transfer, and when the display control unit transitions from the first screen to the second screen, the display control unit transitions the screens such that the string of characters indicating the amount displayed on the first screen is maintained while the string of characters indicating the amount is displayed on the second screen.

Description

Technical Field

[0001] The present invention relates to a payment application program, an information processing server, and an information processing method.

Background Art

[0002] As a payment method, cashless electronic payment is known. Patent Document 1 describes an electronic payment method using a payment application program that can be installed on a terminal device such as a smartphone.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the method described in Patent Document 1, there is room for improvement in preventing illegal acts that induce the user operating the payment application program to make a payment or transfer that the user does not intend.

[0005] An object of the present invention is to suppress illegal acts in electronic payment services.

Means for Solving the Problems

[0006] The present invention relates to a payment application program installed on a terminal device used by an electronic payment user, and includes a display control unit that controls a screen displayed on the display unit of the terminal device, wherein the screen includes a first screen for inputting an amount when making a payment or remittance by electronic payment, and a second screen which includes a string of characters indicating the amount, a predetermined message, a first button for instructing the execution of the payment or remittance of the amount, and a second button for canceling the payment or remittance, and the display control unit is characterized in that, when transitioning from the first screen to the second screen, the display control unit transitions the screen such that the string of characters indicating the amount displayed on the first screen is maintained while the string of characters indicating the amount is displayed on the second screen. [Effects of the Invention]

[0007] According to the present invention, fraudulent activities in electronic payment services can be suppressed. [Brief explanation of the drawing]

[0008] [Figure 1] This is a diagram showing an example of the system configuration of an electronic payment system. [Figure 2] This is a block diagram showing an example of the device's hardware configuration. [Figure 3] This figure shows an example of the functional configuration of a user's terminal device. [Figure 4] This is a diagram showing an example of a screen used for electronic payments. [Figure 5] This is a flowchart illustrating the flow of electronic payment processing. [Figure 6] This figure shows an example of a payment amount input screen. [Figure 7] This figure shows an example of a payment confirmation screen. [Figure 8] This diagram shows a comparison example of a payment confirmation screen. [Figure 9] This figure shows an example of a payment completion screen. [Figure 10]This figure shows an example of a payment completion screen. [Figure 11] This figure shows an example of a payment confirmation screen. [Figure 12] This figure shows an example of a screen for entering the amount to be sent. [Figure 13] This figure shows an example of a remittance confirmation screen. [Figure 14] This figure shows an example of a screen indicating that the remittance process is complete. [Modes for carrying out the invention]

[0009] Hereinafter, embodiments of the payment application program, information processing server, and information processing method according to the present invention will be described in detail with reference to the drawings. The payment application program, information processing server, and information processing method according to the present invention are not limited to the following embodiments. In addition, the same components are denoted by the same reference numerals in the following embodiments, and redundant descriptions are omitted.

[0010] In recent years, fraudulent activities have been occurring in which electronic payment services are used to defraud users of electronic money and other electronic payment methods by pretending to issue refunds. For example, fraudsters may lie to the target user, claiming they want to issue a refund, and instruct them to operate the payment app of an electronic payment service in order to issue a refund. Then, after getting the target user to the screen where they can enter the amount to be sent in the payment app, the fraudsters may falsely present the user with a code or other information for a refund and have the user enter the amount to be sent, thereby sending the user's electronic money or other electronic payment methods to the fraudster.

[0011] Although the target user has no intention of making a transfer, they may be unfamiliar with using the payment app and end up performing operations as instructed by the malicious user. On the screens provided by the payment app, there are various screens for entering numerical values other than the amount, such as recipient identification information, passcodes, gift codes, and the user's own phone number. Additionally, malicious users give instructions to deliberately cause confusion to target users who are unfamiliar with using the payment app, making them repeat operations multiple times to rush them. In such situations, it is imaginable that even if the target user enters the transfer amount on the payment app, they will not easily recognize that the entered numerical value is the amount to be transferred from their account balance. Therefore, in the following embodiments, a method will be described to enable users using the electronic payment service to easily recognize that the numerical value entered on the screen for entering the transfer or payment amount is the amount to be transferred or paid from their account balance.

[0012] <First Embodiment> [Overview of Electronic Payment System] FIG. 1 is a diagram showing an example of the system configuration of an electronic payment system using the payment application program (also referred to as a payment app) of this embodiment. As shown in FIG. 1, the electronic payment system 100 includes a terminal device 120, a payee terminal 130, and an electronic payment server 150. The payee terminal 130 and the electronic payment server 150 are communicatively connected to each other via a network 140. Also, the terminal device 120 and the electronic payment server 150 are communicatively connected to each other via the network 140.

[0013] A user is a person who operates the terminal device 120 to pay a store or the like with electronic money for goods purchased at a store or the like or services received from a store or the like, or to transfer electronic money to another user. The user has obtained an account for the electronic payment service provided by the electronic payment system 100 using the account management function of the payment application 300. The user's account is managed by the electronic payment server 150 and is linked to the user's identification information and the user's electronic money account. The user can receive the provision of the electronic payment service by installing the payment application 300 on the terminal device 120.

[0014] [Payment destination terminal] The payment destination terminal 130 is an information processing device used by the payment destination of the user's electronic money, such as a store that has contracted with a service provider that provides an electronic payment service, or a provider that provides services or the like. The payment destination terminal 130 has a reader 131 that reads a one-dimensional code or a two-dimensional code. In addition, a payment destination code image 132 is posted at the payment destination of a store or the like. The payment destination code image 132 shows the URL, which is the identification information of the payment destination, in the form of a two-dimensional code. The payment destination code image 132 may be printed and posted on a paper or plastic medium, or may be displayed on an electronic display. The two-dimensional code is, for example, a QR code (registered trademark).

[0015] [Electronic payment server] The electronic payment server 150 is an information processing server that provides electronic payment services, including electronic payment processing and distribution of information related to electronic payments. The electronic payment server 150 includes a computer with communication and program execution functions. The electronic payment server 150 manages the electronic money accounts of payment recipients and the electronic money accounts of users who have accounts for the electronic payment service. For example, various electronic payments are realized when the electronic payment server 150 transfers electronic money from the balance of the payment recipient user's electronic money account. In this embodiment, the information processing server that realizes the electronic payment server 150 is not limited to a single device, but includes a system in which multiple devices behave as if they were a single device.

[0016] [User's terminal device] The terminal device 120 is an information processing device used by users when making electronic payments, and is also called a user terminal. For example, the terminal device 120 may be a smartphone, tablet, notebook PC (Personal Computer), desktop PC, or PDA (Personal Digital Assistant). In this embodiment, the terminal device 120 will be described as a smartphone as an example. The user of the terminal device 120 will be referred to as User A.

[0017] The payment application 300 is an application program installed on the terminal device 120. The payment application 300 is operated and managed by a service provider that provides electronic payment services via the electronic payment server 150. Details of the functions of the payment application 300 will be described later. There are two methods for making electronic payments using the payment application 300: store scan and user scan.

[0018] [Payment via store scan] Store scan payment is a method in which a payment terminal 130 installed in a store reads the identification information of user A and performs payment via electronic payment. Specifically, the payment terminal 130 optically reads the code image 422 (see Figure 4(b)) containing the identification information of user A displayed on the terminal device 120 using a reader 131, decodes the read code image to obtain the identification information of user A, and transmits the obtained identification information of user A to the electronic payment server 150 along with the payment request. The electronic payment server 150 generates a one-time code in response to the payment request and returns it to the payment terminal 130. The payment terminal 130 adds the identification information of the payee and the payment amount to the received one-time code and transmits it to the electronic payment server 150. Based on the information received from the payment terminal 130, the electronic payment server 150 identifies the electronic money account of user A and the electronic money account of the payee from its database and performs the electronic payment processing. Once the electronic payment process is complete, the electronic payment server 150 notifies the terminal device 120, and the terminal device 120 displays a payment completion screen. The payment recipient terminal 130 may also send and receive payment-related information with the electronic payment server 150 via the server of the intermediate payment provider.

[0019] [Regarding payments via user scan] User scan payment is a method in which the terminal device 120 reads the identification information of the payee and makes an electronic payment. Specifically, the payment application 300 of the terminal device 120 reads the payee code image 132 of the payee using the camera function of the terminal device 120. The payee code image 132 has a URL that identifies the payee encoded in it, and the payment application 300 of the terminal device 120 obtains the URL from the payee code image 132. The payment application 300 of the terminal device 120 sends the URL information, to which user A's identification information has been added, to the electronic payment server 150. Based on the received URL and user A's identification information, the electronic payment server 150 identifies the user and payee from its database and displays the payment amount input screen 600 (see Figure 6(a)) on the payment application 300. The payment application 300 of the terminal device 120 accepts the amount input by user A on the payment amount input screen 600 and sends the information of the entered amount to the electronic payment server 150. The electronic payment server 150 processes the electronic payment by transferring the received amount of electronic money from user A's electronic money account to the recipient's electronic money account. Details of payments by user scan will be described later.

[0020] [Terminal device hardware configuration] Figure 2(a) shows the hardware configuration of the user's terminal device 120. The terminal device 120 includes a CPU 201, ROM 202, RAM 203, storage unit 204, operation unit 205, communication interface 208, camera 209, voice processing unit 210, and vibration detection unit 212, with each unit connected via a bus 213. The operation unit 205 includes a display unit 206 and an input unit 207.

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

[0022] ROM202 stores the startup program and OS (Operating System) of the terminal device 120. RAM203 temporarily stores programs or data when the CPU201 performs various processes. RAM203 is used as work memory.

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

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

[0025] The communication interface 208 includes an interface for communication connection with a network 140, including LAN (Local Area Network), WAN (Wide Area Network), the Internet, and mobile communication networks, as well as interfaces for short-range wireless communication such as Bluetooth® and NFC (Near Field Communication). The communication interface 208 can be wired or wireless. The terminal device 120 receives data from other devices via the communication interface 208 and transmits data generated or stored by the terminal device 120 to other devices via the communication interface 208.

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

[0027] The audio processing unit 210 includes a microphone and a speaker. The microphone acquires the voices of users, 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 users can listen to it.

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

[0029] Furthermore, it goes without saying that the terminal device 120 is provided with the necessary configuration to realize predetermined information processing. Note that the hardware configuration of the terminal device 120 is not limited to the configuration shown in Figure 2. For example, a positioning unit for realizing GPS functionality may be provided. The terminal device 120 may also be equipped with a media I / F (not shown). The media I / F is an interface for connecting a media drive device that reads and writes data and programs stored on a data storage medium (hereinafter referred to as "media") connected by wire or wireless. The media I / F reads programs and data stored on the media, temporarily stores them in the RAM 203, and inputs them to the CPU 201. The CPU 201 can then load the input program into the work memory of the RAM 203 and execute processing. The media includes, for example, optical recording media such as DVDs (Digital Versatile Discs) and PDs (Phase Change Rewritable Disks), magneto-optical recording media such as MOs (Magneto-Optical disks), tape media, magnetic recording media, or semiconductor memory.

[0030] [Electronic payment server hardware configuration] Figure 2(b) shows an example of the hardware configuration of the electronic payment server 150. The electronic payment server 150 has a CPU 211, ROM 212, RAM 213, storage unit 214, and communication interface 215. The CPU 211 has the same configuration as the CPU 201, the ROM 212 as the ROM 202, the RAM 213 as the RAM 203, the storage unit 214 as the storage unit 204, and the communication interface 215 as the communication interface 208, so their explanations are omitted.

[0031] [Functional Configuration of Payment Applications] Figure 3 is a block diagram showing an example of the functions of the payment application 300 according to this embodiment. The payment application 300 is an application program installed and used on the terminal device 120 of a user of an electronic payment service, and is operated and managed by the service provider that provides the electronic payment service. The payment application 300 is generally installed on the terminal device 120 by downloading it from a website, but it may also be installed on the terminal device 120 by reading it from media. Alternatively, the payment application 300 may be provided as a web application that runs on the web browser of the terminal device 120.

[0032] Figure 3(a) shows the data contained in the terminal device 120. As shown in Figure 3(a), the terminal device 120 contains the program for the payment application 300. Furthermore, the terminal device 120 contains screen data 330 for various screens displayed in the payment application 300, and user A identification information 320. The data shown in Figure 3(a) is described as being stored in the storage unit 204 of the terminal device 120, but the location where the data is stored is not limited. At least a portion of the data shown in Figure 3(a) may be stored in an external storage unit, such as cloud storage. The identification information 320 is assigned by the electronic payment server 150 when the account is registered. The screen data 330 includes screen data for the top screen, payment screen, scan screen, payment amount input screen, various confirmation screens, payment completion screen, remittance screen, and various error notification screens.

[0033] Figure 3(b) shows the functional configuration of the payment application 300. The payment application 300 in this embodiment includes a payment processing unit 301, a reception unit 302, and a display control unit 303.

[0034] The settlement processing unit 301 performs electronic settlement processing between the terminal device 120 and other terminal devices other than terminal device 120, the payee terminal 130, or the electronic settlement server 150.

[0035] The reception unit 302 receives user input via the operation unit 205 of the terminal device 120. If the operation unit 205 is not a touch panel display but consists of input devices such as a keyboard or mouse, the reception unit 302 receives input for specific operations and other operations described later using the operation method corresponding to each input device.

[0036] The display control unit 303 displays various screens corresponding to the various functions of the payment application 300 on the display unit 206 of the terminal device 120. The display control unit 303 acquires screen data 330 for the various screens from the storage unit 204 in response to user operations and displays it on the display unit 206. At that time, the display control unit 303 may also reflect identification information 320 and balance information acquired from the electronic payment server 150 on the screen.

[0037] The CPU 201 of the terminal device 120 implements various functions included in the payment application 300 by reading programs stored in the memory unit 204, ROM 202, and media into the RAM 203 and executing them. The terminal device 120 may also acquire programs from other devices, such as a server device, via the network 140.

[0038] Although the functions of the payment application 300 and the data related to the payment application 300 shown in Figure 3 have been described as being included in the terminal device 120, they may also be included in the electronic payment server 150. For example, the payment application 300 may be a web application in which the electronic payment server 150 provides electronic payment services using a web browser displayed on the display unit 206 of the terminal device 120. In this case, the electronic payment server 150 may execute the functions of the payment application 300 on the web browser displayed on the terminal device 120, thereby executing the display processing of various screens and electronic payment processing by the payment application 300 on the web browser.

[0039] [Electronic payment processing via user scan] When the payment app 300 is launched by user A, the CPU 201 of the terminal device 120 retrieves the screen data of the payment app 300 from the storage unit 204 and displays the top screen 410 (see Figure 4(a)) on the display unit 206. For example, when user A taps the launch icon for the payment app 300 displayed on the home screen of the terminal device 120, the CPU 201 launches the payment app 300.

[0040] Figure 4(a) shows an example of the top screen 410 of the payment app 300. The top screen 410 includes a store scan payment button 412 that transitions to the store scan payment screen 420. The top screen 410 also includes a button 411 that transitions to the user scan payment screen 430 for making payments by user scan. Furthermore, the top screen 410 includes buttons that transition to the remittance screen, points screen, transaction history screen, charge screen, and various other buttons that are operated when transitioning to various functions included in the payment app 300.

[0041] Figure 4(b) shows the store scan payment screen 420 that is displayed on the display unit 206 when the store scan payment button 412 included in the top screen 410 is tapped. The store scan payment screen 420 displays the code image 422 that the payment destination terminal 130 reads when scanning the store. The store scan payment screen 420 includes a button 421 that transitions to the user scan payment screen 430 for making a payment by user scan.

[0042] Figure 4(c) shows an example of the user scan payment screen 430. The user scan payment screen 430 is a screen for reading the payee code image 132 when making a payment by user scan.

[0043] Figure 5 is a flowchart illustrating the flow of electronic payment processing. Figure 5 will be used to explain the details of electronic payment processing using user scan payment. In this embodiment, when the user scan payment screen 430 shown in Figure 4(c) is displayed, the flowchart in Figure 5 begins.

[0044] The processes performed at each step in the flowchart of Figure 5 are described in the payment application 300 program stored in the memory unit 204 of the terminal device 120. In the description of the flowchart of Figure 5, "execution by the payment application 300" means that the CPU 201 retrieves the payment application 300 program from the memory unit 204 and loads it into the RAM 203, and the CPU 201 then executes the payment application 300 program. In the description of flowcharts in this specification, the symbol "S" means a step.

[0045] In S501, when user A takes a picture of the payee code image 132 so that the payee code image 132 is within the frame 431 of the user scan payment screen 430, the payment application 300 displays the payment amount input screen. In this embodiment, the payment application 300 displays the payment amount input screen 600 (see Figure 6(a)) as the payment amount input screen. Figure 4(d) shows the user scan payment screen 430 when the payee code image 132 is scanned.

[0046] Figure 6 shows an example of the payment amount input screen 600. The payment amount input screen 600 is a screen that allows the user to input the amount of electronic money to be paid to the payee. The payment amount input screen 600 includes a payee name display area 601, a payment amount display area 602, a balance display area 603, a number button area 604, and a next button 605. The payee name display area 601 is an area that displays the name of the electronic money payee. The number button area 604 includes number buttons for user A to input an amount, and the number entered by user A is displayed in the payment amount display area 602 as the electronic money payment amount. The balance display area 603 is an area that displays the balance of user A's electronic money. When user A pays the amount requested by the payee, user A inputs the payment amount by touching the number buttons in the number button area 604. The payment application 300 displays the screen on the display unit 206 by acquiring screen data from the storage unit 204.

[0047] The payment amount input screen 600 in Figure 6 is the screen that appears when user A reads the payment destination code image, which contains the identification information of PPP Restaurant, in order to pay electronic money to PPP Restaurant. Figure 6(a) shows the payment amount input screen before entering the payment amount.

[0048] In S502, the payment application 300 determines whether an amount has been entered in the payment amount display area 602. If the payment application 300 determines that an amount has been entered (S502 is YES), it proceeds to S503; otherwise (S502 is NO), it repeats S502 until an amount is entered.

[0049] In S503, the payment application 300 determines whether the "Next" button 605 included in the payment amount input screen 600 has been tapped. If the payment application 300 determines that the "Next" button 605 has been tapped (S503 is YES), it proceeds to S504 to continue the payment process. Otherwise (S503 is NO), it returns to S502 and repeats the process.

[0050] The payment amount input screen 600 in Figure 6(b) is an example of the payment amount input screen 600 when an amount is entered in the payment amount display area 602. As shown in Figure 6(b), when user A enters a number on the payment amount input screen 600, the string 606 representing the number entered by user A is displayed in the payment amount display area 602 of the payment amount input screen 600. In the payment amount display area 602 of Figure 6(b), "500 yen" is displayed as the string 606, indicating that 500 yen worth of electronic money will be paid from the balance of user A's electronic money account.

[0051] Thus, in user scan payment, the payment app 300 prompts user A to enter the amount to pay to the recipient on the payment amount input screen 600. However, if user A is unfamiliar with operating the app, user A may not realize that the number entered on the payment amount input screen 600 represents the amount of electronic money to be used to pay the recipient by reducing user A's electronic money account balance. As mentioned above, it is necessary to ensure that users can easily recognize that the number entered on the payment amount input screen is the amount to be paid from their own account balance. Therefore, in this embodiment, when the next button 605 on the payment amount input screen 600 is pressed, the process proceeds to S504.

[0052] In S504, the payment application 300 transitions the screen displayed on the display unit 206 from the payment amount input screen 600 to the payment confirmation screen 700 (see Figure 7(e)). For example, the payment application 300 transitions to the payment confirmation screen 700, which is the confirmation screen of this embodiment, while maintaining the format of the string 606 of the amount entered on the payment amount input screen 600, which is the payment amount input screen of this embodiment.

[0053] Figure 7(e) shows an example of the payment confirmation screen 700 displayed in S504. The payment confirmation screen 700 is a screen in which a dialog box 701 is superimposed on the payment amount input screen 600. The dialog box 701 contains a message 702, a cancel button 703, and a payment execution button 704.

[0054] Message 702 includes a string 706 indicating the payment amount. Message 702 is a message indicating that the amount of electronic money indicated by the string 706 will be paid from the user's account and the user's electronic money balance will decrease. The string 706 indicating the payment amount is displayed in the same manner as the string 606 displayed in the payment amount display area 602 on the payment amount input screen 600. That is, the string 706 indicating the payment amount is displayed in the same manner as the string 606 indicating the numerical value entered by user A. In this embodiment, the same manner means at least one of the same font, the same size, and the same position, and Figure 7(e) is an example in which the string indicating the payment amount is displayed in the same font, the same size, and the same position.

[0055] Here, a decrease in the electronic money balance means a decrease in the electronic money balance in effect. For example, if the equivalent of electronic money decreases, such as with point payments, or if it is a deferred payment such as with credit card payments, it will also mean a decrease in the electronic money balance. Alternatively, if the bank balance is directly used for payment, such as with debit payments, it will also mean a decrease in the electronic money balance. In other words, electronic payments using the terminal device 120 may also be payments made using a credit card that the user has registered in advance. In the case of credit card payments, the terminal device 120 should transfer the amount of electronic money indicated by the payment amount to the recipient's account and request the amount indicated by the payment amount from the user's credit card company. In the case of debit payments, the terminal device 120 should transfer the amount of electronic money indicated by the payment amount to the recipient's account and withdraw the amount indicated by the payment amount from the user's bank account.

[0056] Figure 8 shows a comparative example of a payment confirmation screen. The payment confirmation screen in the comparative example is an example of displaying a confirmation message without maintaining the appearance of the string 606 that indicates the number entered by user A and displayed in the payment amount display area 602 of the payment amount input screen 600. In the comparative example in Figure 8, the string 801 indicating the payment amount, "500 yen," included in the message, has a different appearance, such as font, compared to string 606. As a result, the payment confirmation screen shown in Figure 8 is a confirmation screen where it is difficult for user A to recognize where the number "500 yen" indicating the payment amount was entered. Furthermore, as shown in Figure 8, if the strings in the message are displayed uniformly on the confirmation screen, it will not be a screen that user A will pay attention to, and there is a risk that user A will recognize it as a normal confirmation screen and proceed with the operation.

[0057] On the other hand, the payment confirmation screen 700 of this embodiment, shown in Figure 7(e), is displayed such that a message indicating that the amount will decrease User A's electronic money balance is added to the string 606, which shows the value entered by User A and was displayed in the payment amount display area 602. Therefore, User A can intuitively recognize that the number entered by User A on the payment amount input screen 600 matches the payment amount included in the message 702. Thus, User A can be made to recognize that the number entered earlier was an amount that would decrease User A's electronic money balance.

[0058] Figures 7(a) to 7(e) show the screens displayed in chronological order. Of these, Figures 7(b) to 7(d) show an example of the screens during the transition from the payment amount input screen 600 in Figure 7(a) to the payment confirmation screen 700 in Figure 7(e). Even during the transition from the payment amount input screen 600 to the payment confirmation screen 700, the payment application 300 controls the screen so that the string 606 indicating the numerical value entered by user A, displayed in the payment amount display area 602, continues to be displayed while maintaining its form. That is, the string 606 that was displayed in the payment amount display area 602 on the payment amount input screen 600 is assumed to remain displayed in the same font, size, and position as the transition from the payment amount input screen 600 to the payment confirmation screen 700.

[0059] Furthermore, as shown in Figures 7(b) to 7(d), the transition from the payment amount input screen 600 to the payment confirmation screen 700 may be such that the text of message 702 other than the string 706 indicating the payment amount, the cancel button 703, and the payment execution button 704 are displayed later. By performing the screen transition in this manner, it is possible to emphasize to user A that the amount indicated by the string 706 in message 702 corresponds to the amount entered by user A on the payment amount input screen 600. In addition, if message 702 is read aloud, it may be displayed sequentially.

[0060] The payment application 300 provides various screens for entering numerical values. Therefore, in this embodiment, the format of the string 606 indicating the value entered by user A is maintained so that it is easy to recognize that the numerical value entered by user A is the payment amount on the payment amount input screen 600. Furthermore, when transitioning to the payment confirmation screen 700, a special screen transition is performed so that user A can recognize that the numerical value entered this time is a special numerical value.

[0061] Furthermore, the operation required to proceed to the payment confirmation screen 700 is not limited to pressing the "Next" button. The payment application 300 may also be configured to transition from the payment amount input screen to the confirmation screen when a predetermined operation is performed by user A.

[0062] In S505, the payment application 300 determines the type of button pressed by user A on the payment confirmation screen 700. If the button pressed by user A is the "cancel" button 703, the process proceeds to S508.

[0063] In S508, the payment app 300 cancels the payment procedure to the payee. The method of cancellation is not limited. In S508, the payment app 300 may return the screen to the payment amount input screen 600, or it may return the screen to the top screen 410.

[0064] Thus, the payment confirmation screen 700 of this embodiment includes a "cancel" button 703 for canceling the electronic payment procedure. The "cancel" button 703 is displayed with the word "cancel" included in a way that is easy for user A to understand. Therefore, the payment confirmation screen 700 is not only a screen that clearly shows user A that the number entered by user A represents the payment amount, but also a screen that user A can cancel the electronic payment procedure without hesitation.

[0065] On the other hand, in S505, if the button pressed by user A on the payment confirmation screen 700 is the payment execution button 704, the payment application 300 proceeds to S506.

[0066] In S506, the payment application 300 requests the electronic payment server 150 to perform an electronic payment process that transfers the amount of electronic money to the recipient's account from the balance of user A's electronic money account. For example, the payment application 300 generates payment data corresponding to the amount displayed on the payment confirmation screen 700 according to the payment processing program and sends the payment data to the electronic payment server 150.

[0067] In S507, the payment application 300 displays the payment completion screen on the display unit 206. The payment application 300 reads the screen data stored in the storage unit 204 and displays the payment completion screen.

[0068] Figure 9 is a diagram illustrating the screen transition to the payment completion screen. When the payment execution button 704 is pressed on the payment confirmation screen 700, the screen transitions from the payment confirmation screen 700 in Figure 9(a) to the first payment completion screen 910 shown in Figure 9(b). The payment application 300 displays a string 911 indicating the payment amount on the first payment completion screen 910 in the same manner as the string 706 indicating the payment amount included in the payment confirmation screen 700. The first payment completion screen 910 is a screen for user A to confirm the amount that has been paid. In this way, the manner of the string 606 indicating the numerical value entered by user A on the payment amount input screen 600 is maintained and displayed until the first payment completion screen 910. Therefore, user A can intuitively confirm that a payment of the amount entered on the payment amount input screen 600 has been executed.

[0069] Then, when the first payment completion screen 910 is displayed, the payment app 300 changes its display to the second payment completion screen 1040 (see Figure 10(d)). The second payment completion screen 1040 is a screen for the payee or the payee's staff to confirm that the payment has been completed.

[0070] The screen transition from the first payment completion screen 910 to the second payment completion screen 1040 will be explained. First, the string 911 indicating the payment amount included in the first payment completion screen 910 is enlarged to a predetermined size. Figure 9(d) shows an example of the first payment completion screen 910 with the string indicating the payment amount enlarged to a predetermined size.

[0071] As shown in Figures 9(b) to 9(d), the payment application 300 may control the size of the string 911 indicating the payment amount included in the first payment completion screen 910 so that it gradually increases over time.

[0072] Figures 10(a) to 10(d) illustrate the screens displayed in chronological order. To facilitate visual confirmation by the recipient's staff, the display angle of the area 931 containing the enlarged payment amount and the recipient's name is rotated clockwise around its center of gravity, changing over time so that it is inverted 180 degrees. The payment application 300 may also transition to the payment confirmation screen 700, display it in an unrotated state for a predetermined time, and then begin rotating the display.

[0073] In this way, the payment app 300 displays a second payment completion screen 1040 in which the payment amount and the name of the payee are ultimately rotated 180 degrees and upside down. This makes it easy for user A to recognize that they need to show the second payment completion screen 1040 to the staff of the payee. Also, in the second payment completion screen 1040, area 931 is upside down. When user A shows the display surface of the terminal device 120 to the staff of the payee facing them, they tilt the terminal device 120 backward from its normal position with the display surface facing user A so that the display surface of the terminal device 120 faces upward. By simply tilting the terminal device 120 in this way, the payment amount displayed on the screen can be easily seen by the staff of the payee.

[0074] It should be noted that, not only in the payment app 300, but also on terminals such as smartphones and PCs, various confirmation screens are displayed to the user. For this reason, even if a confirmation screen is displayed, user A may not show interest and may naturally press a button other than the "cancel" button in order to proceed with the process. However, the payment confirmation screen 700 of this embodiment, displayed in S504, is a screen that instructs user A to execute the final payment, and is different from a normal confirmation screen. For this reason, in S504, the payment app 300 may display something to indicate that the payment confirmation screen 700 is different from other confirmation screens. For example, in order to draw attention to the payment confirmation screen 700, the payment app 300 may add and display a visual effect that was not displayed in the display of the payment amount input screen 600.

[0075] Figure 11 shows an example of how the payment confirmation screen 700 is displayed. When the payment application 300 displays the payment confirmation screen 700 in S504, it may place particles 1101 as a visual effect. Particles are visual effects that represent scattering particles, smoke, sparks, etc., and are composed of many particles, with the shape, direction of movement, speed, distance of movement, position coordinates, display time, and color of each particle being controlled. Even when particles 1101 are added in this way, the payment application 300 controls the system to accept button presses so that user A can cancel the payment procedure at any time. Furthermore, in order to suppress user A's psychological resistance to pressing the buttons, the payment application 300 may control the placement of particles 1101 so that they do not overlap with the cancel button 703 or the execute payment button 704.

[0076] Furthermore, the visual effects added to the payment confirmation screen 700 may change depending on the date and time, or they may change randomly. By adding such special visual effects to the payment confirmation screen 700, even if user A is a regular user of the payment app 300, transitioning to the payment confirmation screen 700 can be something to look forward to. Therefore, even if the number of operations the user has to perform before executing a payment increases, the inconvenience the user may feel can be reduced.

[0077] As described above, according to this embodiment, a confirmation screen can be displayed on the payment amount input screen 600 so that the user can easily see that the number entered by the user is the amount to be paid from the user's account. For this reason, it is expected that fraudulent activity in electronic payment services will be suppressed.

[0078] <Second Embodiment> The first embodiment described a method for displaying a confirmation screen in user-scan payment. This embodiment describes a user-to-user transfer, where electronic money is transferred from the sender's account to the recipient's account, as an example of electronic payment. This embodiment will mainly describe the differences from the first embodiment. Unless otherwise specified, the configuration and processing are the same as in the first embodiment.

[0079] For example, let's assume that terminal device 120 in Figure 1 is a terminal device used by user A, the sender of the funds. In this case, user A inputs the identification information of recipient user B into terminal device 120. One way to obtain the identification information of recipient user B is for terminal device 120 to read a coded image containing the identification information of recipient user B displayed on the terminal device used by recipient user B. Alternatively, the identification information of recipient user B may be the user ID or phone number of recipient user B, and sender user A may directly input the identification information of recipient user B into terminal device 120. Alternatively, sender user A may register the identification information of other users in the address book of the payment application 300 and select the identification information of recipient user B from the address book.

[0080] In this embodiment, when user A selects the remittance function from the top screen 410 of the payment application 300 and enters the identification information of recipient user B, the flowchart shown in Figure 5 is initiated. In this embodiment, at S501 in Figure 5, the payment application 300 displays a remittance amount input screen 1200 (see Figure 12(a)) for accepting input of the remittance amount.

[0081] Figure 12 shows an example of the remittance amount input screen 1200. The remittance amount input screen 1200 includes a recipient display area 1201 that displays the selected recipient user B, a remittance amount display area 1202 that displays the amount to be paid, a balance display area 1203 that displays the balance of user A's electronic money, a number button area 1204 for entering the amount, and a next button 1205. User A enters the remittance amount by touching the number buttons in the number button area 1204. The payment application 300 displays the screen on the display unit by acquiring screen data from the storage unit 204. Figure 12(a) shows the remittance amount input screen before entering the remittance amount.

[0082] In S502, the payment application 300 determines whether an amount has been entered in the amount display area 1202. If the payment application 300 determines that an amount has been entered (S502 is YES), it proceeds to S503; otherwise (S502 is NO), it repeats S502 until an amount is entered.

[0083] In S503, the payment application 300 determines whether the "Next" button 1205 included in the remittance amount input screen 1200 has been tapped. If the payment application 300 determines that the "Next" button 1205 has been tapped (S503 is YES), it proceeds to S504 to continue the remittance process. Otherwise (S503 is NO), it returns to S502 and repeats the process. Figure 12(b) shows an example of the remittance amount input screen 1200 when an amount has been entered in the remittance amount display area 1202. The remittance amount display area 1202 displays a string 1206 indicating the number entered by user A.

[0084] In S504, the payment application 300 transitions the screen displayed on the display unit 206 from the remittance amount input screen 1200 to the remittance confirmation screen 1300 (see Figure 13(e)).

[0085] Figure 13(e) shows an example of the remittance confirmation screen 1300 displayed in S504 in this embodiment. The remittance confirmation screen 1300 is a screen in which a dialog box 1301 is superimposed on the remittance amount input screen 1200. The dialog box 1301 includes a message 1302, a cancel button 1303, and an execute remittance button 1304. Even when executing a remittance, the string 1306 indicating the remittance amount included in message 1302 is displayed in the same manner as the string 1206 displayed in the remittance amount display area 1202 on the remittance amount input screen 1200. Message 1302 is a message indicating that electronic money equivalent to the amount indicated by string 1306 will be reduced from user A's account balance, and the reduced electronic money will be sent to user B. Therefore, even when sending electronic money, user A can intuitively recognize that the number entered by user A is the remittance amount that will reduce user A's electronic money balance.

[0086] Figures 13(a) to 13(e) show the screens displayed in chronological order. Of these, Figures 13(b) to 13(d) show an example of the screens during the transition from the remittance amount input screen 1200 in Figure 13(a) to the remittance confirmation screen 1300 in Figure 13(e). Even during the transition from the remittance amount input screen 1200 to the remittance confirmation screen 1300, the payment application 300 controls the screen so that the string 1206 indicating the numerical value entered by user A continues to be displayed while maintaining its form.

[0087] In the transition from the remittance amount input screen 1200 to the remittance confirmation screen 1300, as shown in Figures 13(b) to 13(d), the text of message 1302 other than the string 1306 indicating the remittance amount, the cancel button 1303, and the execute remittance button 1304 may be displayed later. By performing the screen transition in this manner, similar to the first embodiment, the numerical value entered on the remittance amount input screen 1200 can be emphasized to user A as the remittance amount. In this embodiment as well, the payment application 300 may add visual effects such as particles to the remittance confirmation screen 1300.

[0088] In S505, the payment application 300 determines the type of button pressed by user A on the remittance confirmation screen 1300. If the button pressed by user A is the cancel button 703, the process proceeds to S508.

[0089] In S508, the payment application 300 cancels the electronic money transfer procedure to recipient user B. In this way, the transfer confirmation screen 1300 of this embodiment also displays the "cancel" button 703 for canceling the transfer procedure, including the string "cancel" in a way that is easy for user A to understand. Thus, the transfer confirmation screen 1300 of this embodiment is also configured to allow the sender user A to cancel the transfer without hesitation.

[0090] On the other hand, in S505, if the button pressed by user A on the remittance confirmation screen 1300 is the remittance execution button 1304, the payment application 300 proceeds to S506.

[0091] In S506, the payment application 300 requests the electronic payment server 150 to perform an electronic payment process to transfer the amount of electronic money to be transferred from the account balance of the sender user A to the account of the recipient user B. When making the transfer request, the payment application 300 sends information to the electronic payment server 150 that includes the identification information of the recipient user B, the amount to be transferred, and the identification information that identifies the sender user A. Once the electronic payment server 150 has transferred the amount of electronic money indicated by the transfer amount from the sender user A's account to the recipient user B's account, it notifies the terminal device 120 that the transfer has been completed.

[0092] In S507, the payment application 300 displays the remittance completion screen 1400 (Figure 14(b)) on the display unit 206. The payment application 300 reads the remittance completion screen data stored in the storage unit 204 and displays the remittance completion screen 1400.

[0093] Figure 14 is a diagram illustrating the screen transition to the remittance completion screen 1400. When the remittance execution button 1304 is pressed on the remittance confirmation screen 1300, the payment application 300 transitions from the remittance confirmation screen 1300 shown in Figure 14(a) to the remittance completion screen 1400 shown in Figure 14(b).

[0094] As explained above, according to this embodiment, even when making a remittance, a confirmation screen can be displayed so that the user can easily see that the number entered on the payment amount input screen is the amount to be paid from the user's account. For this reason, it is expected that fraudulent activity in electronic payment services will be suppressed.

[0095] <Other Embodiments> The display of confirmation screens such as the payment confirmation screen 700 or the remittance confirmation screen 1300 described above is not limited to the time of payment or remittance. When an operation is performed that reduces the electronic money balance, a confirmation screen such as the payment confirmation screen 700 or the remittance confirmation screen 1300 will be displayed when the final instruction is given. Therefore, even if the route to transition to the confirmation screen is different from the usual, once the user A transitions to the confirmation screen, they will be made aware that they are on the screen immediately before performing an operation that will reduce their electronic money balance.

[0096] The embodiments described above describe the case in which electronic payment is performed using electronic money. Electronic money may be points or currencies used independently by various companies, or it may be currency provided by a state that is made electronically tradable, or it may be currency that is not managed by an organization. In other words, the electronic payment in the embodiments described above may be, for example, a transfer of deposits or a transfer of virtual currency.

[0097] It should be noted that the scope of the present invention is not limited to the embodiments described above. For example, the content of buttons and information displayed on the screen, the screen layout, and the processing procedures shown in the flowchart are examples and can be modified as appropriate without departing from the technical idea of ​​the present invention. Furthermore, it is clear to those skilled in the art that various modifications or alterations can be conceived within the scope of the technical idea of ​​the present invention, and these are also understood to naturally fall within the technical scope of the present invention. [Explanation of symbols]

[0098] 120 Terminal devices 300 payment apps 303 Display Control Unit

Claims

1. On the computer of the terminal device used by electronic payment users, A first step is to display a first screen on the display unit of the terminal device for inputting the amount to be paid or transferred by the aforementioned electronic payment; A second step of transitioning the screen to be displayed on the display unit from the first screen to the second screen, such that the string indicating the amount is displayed on the second screen while maintaining the form of the string indicating the amount displayed on the first screen, the second screen includes a string indicating the amount, a predetermined message, a first button for instructing the execution of payment or transfer of the amount, and a second button for canceling the payment or transfer. A payment application program to execute a payment.

2. The aforementioned predetermined message is a message indicating that the user's balance will decrease by the aforementioned amount. The payment application program according to feature 1.

3. The characteristics of the string refer to the size of the string and the type of font. The payment application program according to feature 1.

4. The "nature" of the string refers to the position of the string. The payment application program according to feature 1.

5. In the second step described above, In the second screen, the string representing the amount is displayed at the same position as the string representing the amount in the first screen, and is displayed in the same font as the string representing the amount in the first screen. The payment application program according to feature 1.

6. In the second step described above, Even during the transition from the first screen to the second screen, the string representing the amount continues to be displayed in the same manner as it was displayed on the first screen. The payment application program according to feature 1.

7. In the second step described above, After the string of characters indicating the amount is displayed, the screen transitions from the first screen to the second screen, with the predetermined message, the first button, and the second button being displayed. The payment application program according to feature 6.

8. To the aforementioned computer, In the case of payment by electronic payment, after the first button is pressed by the user, a third screen indicating that the payment has been executed is displayed. When transitioning from the second screen to the third screen, a third step is further performed to transition to the third screen while maintaining the form of the string representing the amount included in the second screen. The payment application program according to feature 1.

9. In step 3 described above, After enlarging the string representing the amount included in the third screen to a predetermined size, the enlarged string is rotated to change the display angle of the string representing the amount. The payment application program according to feature 8.

10. In the second step described above, The second screen is displayed with visual effects that were not present when the first screen was displayed. The payment application program according to feature 1.

11. In the second step described above, By arranging predetermined particles, the aforementioned visual effect is applied. The payment application program according to feature 10.

12. In the second step described above, The predetermined particles are arranged such that they do not overlap the first button and the second button. The payment application program according to feature 11.

13. The aforementioned payment is a payment made via user scan. The payment application program according to feature 1.

14. In the aforementioned electronic payment, the payment or remittance is made using the user's deposit or electronic money balance. The payment application program according to feature 1.

15. The aforementioned electronic money includes points. The payment application program according to feature 14.

16. An information processing server that controls terminal devices used by users of electronic payments, The terminal device has a display control unit that controls the screen displayed on the display unit of the terminal device, The aforementioned screen shows: A first screen for entering the amount when making a payment or remittance using the aforementioned electronic payment method, A second screen includes a display area for displaying the amount, a predetermined message, a first button for instructing the payment or transfer of the amount, and a second button for canceling the payment or transfer. The display control unit, When transitioning from the first screen to the second screen, the screen transition is performed such that the string representing the amount is displayed in the display area while maintaining the form of the string representing the amount contained in the first screen. An information processing server characterized by the following features.

17. An information processing method for controlling the screen displayed on the display unit of a terminal device used by a user of electronic payment, The aforementioned screen shows: A first screen for entering the amount when making a payment or remittance using the aforementioned electronic payment method, A second screen includes a string of characters indicating the amount, a predetermined message, a first button for instructing the payment or transfer of the amount, and a second button for canceling the payment or transfer. When transitioning from the first screen to the second screen, the computer of the terminal device includes the step of transitioning the screens such that the string representing the amount displayed on the first screen is maintained while the string representing the amount is displayed on the second screen. An information processing method characterized by the following:

Images