Information processing device, control method for information processing device, information processing system, and program

Abstract

To improve the convenience of using electronic payment services. [Solution] An information processing device that provides electronic payment services, comprising: an acquisition means for acquiring specific information contained in account information managed by a linked service that can be linked with the electronic payment service; a code transmission means for transmitting an authentication code to a destination terminal indicated by the acquired specific information; and an account generation means for generating account information for an electronic payment service linked with the linked service, which includes the specific information, when an authentication code is received from the terminal.

Description

Technical Field

[0006] , , ,

[0005] , If an operation to generate account information is performed on the aforementioned mobile device, , ,

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

Background Art

[0002] When making a payment for goods or services, cashless payment, which makes a payment without using money, is becoming widespread. In particular, electronic payment using a payment application or the like that can be installed on a terminal device such as a smartphone has attracted attention due to its high convenience.

[0003] In order to use an electronic payment service, it is required to register one telephone number for one account. When registering a telephone number, a method of having the user input the telephone number is generally widely adopted. However, simply having the user input the telephone number cannot guarantee that the input telephone number is the same as the actual telephone number of the mobile terminal, and it is impossible to prevent unauthorized use by an illegal user. In Patent Document 1, measures are taken to strengthen security using SMS (Short Message Service) authentication.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In the use of an electronic payment service, an improvement in convenience is required.

Means for Solving the Problems

[0006] An information processing apparatus according to an aspect of the present disclosure is A partner server capable of providing services in conjunction with an electronic payment service, and a mobile terminal capable of using the partner service provided by the partner server, communicates with the partner server, an information processing apparatus that provides an electronic payment service, and If an operation to generate account information is performed on the aforementioned mobile device, pre Note Specific information included in account information managed by the linked service From the aforementioned partner service The system is characterized by comprising: an acquisition means for acquiring information; a code transmission means for transmitting an authentication code to a destination terminal indicated by the acquired specific information; and an account generation means, upon receiving the authentication code from the terminal, for generating account information for the electronic payment service that includes the specific information and is linked to the linked service. [Effects of the Invention]

[0007] According to one aspect of the present invention, convenience can be improved when using electronic payment services. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of information processing. [Figure 2] This figure shows an example of the system configuration. [Figure 3] This figure shows an example of the hardware configuration of a mobile device. [Figure 4] This figure shows an example of the software configuration of a mobile device. [Figure 5] This diagram shows the software configuration of the electronic payment server. [Figure 6] This is a sequence diagram showing the processing flow of an information processing system. [Figure 7] This is a diagram showing the display screen of a mobile device. [Figure 8] This is a diagram illustrating the database of an electronic payment server. [Figure 9] This is a flowchart showing the processing of mobile devices. [Figure 10] This is a flowchart showing the processing by the electronic payment server. [Modes for carrying out the invention]

[0009] <Embodiment 1> Preferred embodiments of the information processing apparatus, information processing method, program, and information processing system relating to this disclosure will be described in detail below with reference to the drawings. However, these embodiments do not limit the information processing apparatus, information processing method, program, and information processing system relating to this disclosure. Furthermore, identical components are denoted by the same reference numerals in the following embodiments, and redundant descriptions are omitted.

[0010] Generally, when a user starts using an electronic payment service, they install an electronic payment application provided by the electronic payment server onto their mobile device. After installing the electronic payment application, they register an account for the electronic payment service by entering necessary information (including their phone number) and undergoing code verification via SMS using their phone number. Thus, a prescribed security authentication is performed when registering for a new service. On the other hand, users who do not currently use electronic payment services may find the various tasks, such as the account registration process described above, burdensome, and may not end up using the service. There is a need for a system that allows users to easily use electronic payment services without burdening them.

[0011] Therefore, this embodiment describes an example in which a user who does not currently use an electronic payment service begins using an electronic payment service and links their ID with another application (referred to as a linked application) for which the user has already registered an account.

[0012] In this embodiment, by linking the electronic payment service and the linked application using IDs, some of the electronic payment service's functions can be used as mini-applications on the linked application. That is, users can use the electronic payment service on the linked application they normally use without having to install the electronic payment application on their mobile device. Furthermore, because the electronic payment service account is registered using the linked application's account information through ID linking, some user information (also called account information) can be omitted, simplifying account creation. The linked application is, for example, a social networking service (SNS) communication application that users are expected to use frequently. By displaying guidance notifications that lead to the use of the electronic payment service within this linked application, it is possible to provide an opportunity for users who have little interest in electronic payments to start using them. On the other hand, the provider of the electronic payment service can gain the advantage of acquiring many new users by displaying instructions for using the electronic payment service in a popular SNS application.

[0013] In this embodiment, the part of user information that can be omitted when registering an account refers to the telephone number. The telephone number is used as the destination to which the code generated by the electronic payment server is sent to the mobile device when performing code authentication using SMS during account registration (account creation) for the electronic payment service. As a result, users do not need to directly enter their telephone number when opening an account for the electronic payment service through the linked application. In order to achieve the above, it is assumed that one unique telephone number is registered for each account in the user information of the linked application.

[0014] As described above, for example, by launching one linked application, the functions of the linked application and the functions of the electronic payment service can be used within the linked application, so that the operations can be simplified for the user. Note that as the electronic payment function within the linked application, only the use of some functions (such as payment of fees or transfer to other accounts) is assumed. When more functions are required, the electronic payment application can be installed and each function can be used within the electronic payment application. In this embodiment, a method for using the electronic payment service by linking with the linked service and ID will be described.

[0015] FIG. 1 is a diagram for explaining the outline of the information processing system of this embodiment. The information processing system of this embodiment includes a mobile terminal 101, an electronic payment server 102, and a linked server 103. The outline of the processing of each device in this embodiment will be described. The processing shown in FIG. 1 starts when the user's operation to link the electronic payment service and ID within the linked application installed in the mobile terminal 101 is received.

[0016] In S1, the user's mobile terminal 101 requests the linked server for the phone number, which is part of the user information. In S2, the linked server transmits the phone number, which is part of the user information, from the storage unit or the like to the mobile terminal. In S3, the mobile terminal displays the phone number received from the linked server on the display unit, obtains the user's confirmation, and then transmits it to the electronic payment server 102. In S4, the electronic payment server 102 generates an authentication code and transmits it to the obtained phone number. That is, the authentication code is transmitted to the mobile terminal 101 by SMS (Short Message Service) using the telephone line. In S5, the user who owns the mobile terminal 101 confirms the authentication code received by SMS from the electronic payment server and inputs it on the authentication code input screen. In S6, when the authentication process is successful, the linked server 103 opens an account linked with the linked service and ID and displays a link success screen on the mobile terminal 101. The above is the outline of the processing performed by each device. After the configuration of the device is described below, the detailed processing of each device will be described.

[0017] FIG. 2 is a diagram showing an example of the configuration of an information processing system. Referring to FIG. 2, the configuration of the information processing system according to the present embodiment will be described. The information processing system includes a mobile terminal 101, an electronic payment server 102, and a linked server 103. These devices are connected to each other via a network N so as to be communicable with each other by wire or wirelessly. The network N is, for example, a LAN (Local Area Network) and a WAN (Wide Area Network) such as the Internet. Hereinafter, the mobile terminal 101, the electronic payment server 102, and the linked server 103 may be collectively referred to as an information processing device.

[0018] The information processing device may include a GPS (Global Positioning System) function, a camera function, and the like. The information processing device can provide the position information acquired by the GPS function to other devices. The information processing device can provide the code information (information such as one-dimensional code and two-dimensional code) acquired by the camera function to other devices.

[0019] The electronic payment server 102 is an information processing device that provides an electronic payment service for performing electronic payment processing and distributing information related to electronic payment. The user can receive the provision of the electronic payment service by installing an electronic payment application on the mobile terminal 101. Further, in the present embodiment, in a linked service that can be linked with the electronic payment service, it is possible to partially use the functions of the electronic payment service according to the linked situation. Note that in the present embodiment, the linkage of services means that the user IDs of applications are linked to the same telephone number. That is, the basis for determining the same account between applications is whether the telephone numbers are the same. By linking user IDs between different services, it is possible to share information between services. Note that the electronic payment service can also be used by accessing a page provided by the electronic payment server 102 using a general web browser.

[0020] By installing an electronic payment app on their mobile device, users can use the app to make payments for goods or services at stores, view and claim reward information distributed by stores or affiliated merchants, and view recommendation information.

[0021] For example, the electronic payment server 102 manages the electronic accounts of participating stores and users, and enables various payments by transferring electronic money between electronic accounts. In addition to payment processing functions for electronic payments, the electronic payment app has various other functions. These include, for example, a money transfer function, a points function, a transaction history display function, a top-up function, a coupon function, a utility bill payment function, a stamp card function, a shopping function, a finance function, an information content distribution function, a user account information management function, and other functions. The linked server 103 is a server that distributes the linked application. In this embodiment, the linked application is assumed to be an application that enables communication between mobile devices that have the linked application installed by sending and receiving messages. Accordingly, it is assumed that the linked application can be used by registering the phone number of the mobile device.

[0022] In Figure 2, only one mobile device is shown for the sake of illustration; however, in reality, each mobile device with the linked application or electronic payment application installed communicates with other mobile devices, the linked server 103, and the electronic payment server 102.

[0023] Information transmitted and received between the mobile terminal 101, the electronic payment server 102, and other devices may be written in a scripting language such as JavaScript®. The transmitted and received information may also be written in a stylesheet language such as CSS (Cascading Style Sheets), or a programming language such as Java®. Alternatively, the transmitted and received information may be written in a markup language such as XML (Extensible Markup Language) or HTML (HyperText Markup Language). Or, this information may be converted into a data description language such as JSON (JavaScript Object Notation) before transmission and reception.

[0024] Figure 3 is a block diagram showing an example of the hardware configuration of a mobile terminal 101. The mobile terminal 101 has a CPU 301, ROM 302, RAM 303, storage device 304, input / output interface 305, and network interface 306. Each component is connected to the others by a system bus.

[0025] The CPU 301 reads the program stored in the ROM 302 into the RAM 303 and executes the read program to perform various control functions. The CPU 301 may be an MPU (Micro Processing Unit) or an ASIC (application-specific integrated circuit). The CPU 301 may also be an FPGA (Field Programmable Gate Array), etc.

[0026] ROM 302 stores control programs such as the startup program for the mobile terminal 101. RAM 303 temporarily stores control programs or data when the CPU 301 performs various controls. RAM 303 is used as work memory. Storage device 304 is memory for storing applications, software, and various data. Examples of storage device 304 include HDD (Hard Disk Drive), SSD (Solid State Drive), flash memory, and storage devices.

[0027] The input / output interface 305 is an interface for transmitting output information to an output device such as a display unit 310. The display unit 310 can be a display or a projector. Furthermore, the display unit 310 may be located outside the mobile terminal 101, as shown in Figure 3, or it may be located within the mobile terminal 101. In this embodiment, the mobile terminal 101 is assumed to be equipped with a display unit 310.

[0028] The input / output interface 305 is an interface for receiving input information from input devices such as the input unit 311. Examples of input devices 311 include a mouse, keyboard, buttons, and touch panel. The input unit 311 may be located outside the mobile terminal 101, as shown in Figure 3, or it may be located inside the mobile terminal 101.

[0029] Furthermore, the input / output interface 305 may be connected to the display unit 310 and the input unit 311 wirelessly or via a wired connection. The input / output interface 305 may be configured as an input interface and an output interface. The network interface 306 is an interface for receiving data from other devices via the network N and transmitting data generated or stored by the mobile terminal 101 to other devices via the network N.

[0030] Note that the mobile terminal 101 is not limited to the configuration shown in Figure 3. For example, it may be provided with a camera unit for implementing camera functionality, a positioning unit for implementing GPS functionality, and a microphone unit and speaker unit for implementing call functionality.

[0031] The mobile terminal 101 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 301 via RAM 303. The CPU 301 can read the provided programs from the storage device onto RAM 303 via the media interface and execute the read programs. 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.

[0032] The CPU 301 of the mobile terminal 101 implements various functions of the mobile terminal 101 by executing programs read from the RAM 303. The CPU 301 reads and executes these programs from a 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 mobile terminal 101 is provided with the necessary configuration to realize the information processing in this embodiment. Note that the block diagram shown in Figure 3 may also be applied to the hardware configuration of the electronic payment server 102 and the linked server 103, in addition to the mobile terminal 101.

[0033] Figure 4 shows an example of the software configuration of the mobile terminal 101 according to this embodiment. Specifically, it is a diagram illustrating each application stored in the ROM of the mobile terminal 101, and the program modules of those applications.

[0034] Figure 4(a) shows the application data stored in the storage device 304 of the mobile terminal 101. As shown in Figure 4(a), the storage device 304 of the mobile terminal 101 stores the linked application 401 and the SMS application 402. Hereinafter, the application will simply be referred to as the app. In this embodiment, the linked app is assumed to be an SNS (Social Networking Service) application. That is, it is assumed to be an application that enables communication between users who have installed the linked app 401 on their mobile terminals by sending and receiving messages or information over the internet. In addition, in this embodiment, the linked app 401 is required to register the phone number assigned to the mobile terminal 101. This is because one account is linked to one phone number and managed by the linked server 103. As a result, the linked app 401 cannot create multiple accounts on a single mobile terminal. Furthermore, when registering a new linked app 401, SMS authentication using the phone number is required. SMS authentication is an authentication method that verifies the user's identity using SMS (Short Message Service) on a mobile phone. When a user logs into the service, they enter an authentication code (such as numbers) sent from the linked server 103 to their registered mobile phone number to verify their identity. Note that the linked application 401 is not limited to the applications described above. Any application that manages the mobile phone number of each user may be used, even if it is used for purposes other than those mentioned above.

[0035] The SMS (Short Message Service) app 402 is an application for sending and receiving messages using the phone number assigned to the mobile device 101. The SMS app 402 is an application that allows users to send and receive short text messages using a phone number as the recipient. Unlike the aforementioned linked SNS apps, it can be used without special account registration or app installation, as long as the recipient's phone number is known. In other words, the SMS app 402 is a function that is installed by default on the mobile device 101.

[0036] Figure 4(b) is a diagram showing the configuration of the program module of the linked application 401. As shown in Figure 4(b), the linked application 401 in this embodiment has a reception unit 404, a display control unit 405, a request unit 406, a transmission unit 407, and a determination unit 408 as program modules.

[0037] The reception unit 404 receives user operations in the linked application 401 via the display unit 310 or input unit 311 of the mobile terminal 101. The display control unit 405 controls the display of each screen in the linked application 401 and switches (transitions) the displayed screen based on user operations. The request unit 406 requests the phone number information of the mobile terminal 101 from the linked server when linking the linked application 401 with the electronic payment application provided by the electronic payment server. The detailed processing of the request unit 406 will be described later.

[0038] The transmission unit 407 transmits messages, image data, or various information from the linked application 401 to another mobile terminal or the linked server 103. The determination unit 408 determines the processing based on user operations during the process of linking the linked service and the electronic payment service. Specifically, for example, on the consent screen for sharing user information between the linked service and the electronic payment service, different processing is performed depending on whether consent is given or not. In this case, the determination unit 408 determines which processing was given.

[0039] Figure 5 shows an example of the software configuration of the electronic payment server 102. The electronic payment server 102 has a communication unit 500, a control unit 510, and a storage unit 520. The control unit 510 also includes a payment processing unit 511, a transmitting / receiving unit 512, a generation unit 513, an authentication unit 514, and a registration unit 515. The control unit 510 controls the entire electronic payment server 102. The storage unit 520 includes an electronic payment user information DB 521.

[0040] The communication unit 500 communicates with the mobile terminal 101 and other devices via the network N. The payment processing unit 511 performs electronic payments. The following describes the general processing of the mobile terminal equipped with an electronic payment application and the electronic payment server 102 equipped with the payment processing unit 511. First, with the electronic payment application running, the mobile terminal 101 decodes the store code image using its optical reading function. The store code image contains information about the store URL (Uniform Resource Locator). This store URL is the domain of the electronic payment service to which information that can identify the store has been added. The mobile terminal then sends the first payment information, including the store URL and account ID, to the electronic payment server 102. The payment processing unit 511 of the electronic payment server 102 searches for store information from the identification information corresponding to the store URL and obtains information about the merchant name and store name. The payment processing unit 511 sends the obtained information to the electronic payment application. Next, the store user enters the payment amount into the mobile terminal 101 on the screen where the merchant name and store name are displayed. The mobile terminal 101 generates second payment information, including at least the payment amount, and sends it to the electronic payment server 102. The payment processing unit 511 of the electronic payment server 102 performs the electronic payment based on the received second payment information. It then sends a payment completion notification (information for displaying the payment completion screen) to the mobile terminal 101. The above is one example of payment processing between a mobile terminal (electronic payment app) and the electronic payment server 102, but in reality, there are various cases that are not limited to this.

[0041] The transmitting / receiving unit 512 obtains payment-related information from the mobile terminal 101 via the communication unit 500. The transmitting / receiving unit 512 also obtains the user's phone number from the mobile terminal 101 during the process of linking the partner service with the electronic payment service. Furthermore, the transmitting / receiving unit 512 sends an authentication code to the SMS application on the mobile terminal 101 during the linking process.

[0042] The generation unit 513 generates an authentication code to be sent to the mobile terminal 101 during the process of linking the linked service and the electronic payment service. The authentication unit 514 performs SMS authentication using the authentication code received from the mobile terminal 101. The registration unit 515 registers the account of the mobile terminal 101 that has successfully authenticated. That is, it registers the new account in the electronic payment user information DB (database) stored in the storage unit. The registration unit 515 also manages whether the new account is an account that links with the linked service by registering a flag in the electronic payment user information DB. A detailed explanation of the electronic payment user information DB will be described later with reference to Figure 9.

[0043] Figure 6 is a sequence diagram illustrating the process flow for linking the partner service and the electronic payment service. This process is for a user who has already created a user account in the partner service but has not yet created a user account in the electronic payment service to create an account for the electronic payment service linked with the partner application 401. In this process, the electronic payment server 102 sends an authentication code to the SMS application 402 on the mobile terminal 101 using the phone number. In this embodiment, the phone number sent to the electronic payment server 102 is not manually entered by the user, but is entered using prefill-in with the mobile terminal information registered in the partner service. Therefore, it is assumed that the partner application 401 is installed on the user's mobile terminal 101, but the electronic payment application is not installed.

[0044] This process is executed by the CPUs of the mobile terminal 101, the electronic payment server 102, and the linked server 103 loading programs stored in ROM into RAM. For convenience, the main entity of each process will be described using the name of the device or application, but in reality, it is executed by the CPU of each device controlling its respective functional units. In addition, although the mobile terminal 101 is operated by the CPU 301 executing the program of the linked application 401, the main entity of the process will be described as the linked application 401. Furthermore, "S" in each process refers to a step in the sequence diagram, and this is also the case in the subsequent flowchart. This process is started when the user taps (presses) a predetermined guidance display on the display screen within the linked application 401.

[0045] Figure 7 shows the display screen of the mobile terminal 101. The user taps the guidance 701 on the home screen of the linked application 401 shown in Figure 7(a), which starts the processing shown in the sequence diagram in Figure 6.

[0046] In S601, the linked application 401 of the mobile terminal 101 displays a user consent screen. This is the consent screen shown in Figure 7(b), and the consent includes consent to share specific user information between the services when linking the linked service and the electronic payment service. In this embodiment, the specific information is the telephone number assigned to the mobile terminal 101. However, the specific information is not limited to this; for example, it could be a telephone number or information contained in the SIM (Subscriber Identity Module), such as IMSI (International Mobile Subscriber Identity), that can identify the recipient. In the consent screen shown in Figure 7(b), consent is determined to have been obtained when the user performs a consent operation (adds a check mark) to the items that require consent and presses the OK button (not shown) located at the bottom of the consent screen.

[0047] In S602, the linked application 401 requests the electronic payment server 102 to display a web view. A web view is a mechanism that displays a website within an application by embedding the functionality of a web browser within the application. This allows the user to view web content without leaving the application. In this embodiment, the linked application 401 displays the web view provided by the electronic payment server 102.

[0048] In S603, the electronic payment server 102 displays a web view screen provided by the electronic payment server 102 on the linked application 401 running on the mobile terminal 101. The displayed screen is as shown in Figure 7(c), and it is a screen that prompts the user to register for the electronic payment service. As a prerequisite, since this screen is accessed from the display screen of the linked application 401, the user has already registered for an account with the linked service. Furthermore, button 705 on this screen is for users who have not yet used the electronic payment service provided by the electronic payment server 102, and it is a button that allows the user to register for the electronic payment service using the user information of the linked service. Button 706 is for users who have already used the electronic payment service provided by the electronic payment server 102 and have already registered for an account, and it is a button that links the IDs of both. Ultimately, both buttons lead to the ID linking process between the electronic payment service and the linked service. As mentioned above, this embodiment assumes a user who has not registered an account with the electronic payment service, so the user will press button 705 labeled "New Registration with Linked ID" in Figure 7(c). The process shown in Figure 6 below is what happens when button 705 in Figure 7(c) is pressed.

[0049] In S604, the linked application 401 requests the linked server 103 to retrieve the telephone number corresponding to the mobile terminal 101, which is one of the user information items. In S605, the linked server 103 retrieves the telephone number corresponding to the mobile terminal 101 from the linked user information stored in the memory unit in response to a request from a user logged into the linked application 401. In S606, the linked server 103 sends the retrieved telephone number to the linked application 401.

[0050] In S607, the linked application 401 displays the phone number obtained from the linked server 103. The process from S604 to S607 (i.e., the process of obtaining the phone number from the information registered in the linked server 103 and displaying it on the phone number display screen shown in Figure 7(d)) ​​is called prefill-in. Figure 7(d) shows the display screen after the phone number has been entered by prefill-in. In S608, the linked application 401 sends the phone number to the electronic payment server 102. Specifically, when the user presses the button 707 labeled "Confirm phone number and send SMS" on the screen shown in Figure 7(d), the displayed phone number of the mobile terminal 101 is sent to the electronic payment server 102 as a short message. Note that the means by which the mobile terminal 101 sends the phone number to the electronic payment server 102 is not limited to SMS. That is, it may be sent using, for example, mobile data communication or an internet connection, without using a telephone line. Furthermore, in S608, the electronic payment server 102 also receives the telephone number in response to the transmission process by the linked application 401.

[0051] In S609, the electronic payment server 102 generates an authentication code. In S610, the electronic payment server 102 sends the authentication code via SMS to the phone number obtained in S608. At this time, the linked application 401 on the mobile terminal 101 displays an authentication screen as shown in Figure 7(e). The user opens the SMS application, checks the authentication code received from the electronic payment server 102, and enters it into the authentication screen shown in Figure 7(e). Upon receiving the authentication code from the user, in S611, the linked application 401 sends the authentication code to the electronic payment server 102.

[0052] In S612, the electronic payment server 102 performs authentication based on the authentication code obtained from the mobile terminal. Specifically, it determines whether the code generated by the electronic payment server 102 in S609 and sent to the mobile terminal 101 matches the code obtained from the mobile terminal 101 in S611. If they match, authentication is successful; if they do not match, authentication fails. In S613, the electronic payment server 102 performs a new account creation process based on the successful authentication. It also performs an ID linking process. When creating an account, the user appropriately enters the information necessary for account creation. For example, if the user can freely set the ID number or account name, they will set it in this process.

[0053] Upon account creation, the electronic payment server 102 adds the new account information to the electronic payment user information DB 521 stored in the storage unit 520. Specifically, the user's ID number, telephone number, consent status, and ID linkage status are linked and stored. The ID linkage process performed by the electronic payment server 102 updates this consent status and ID linkage status, and displays a linkage completion screen, as shown in Figure 7(f), on the linked application.

[0054] Figure 8 shows the configuration of the electronic payment user information DB 521. In the electronic payment user information DB 521, a telephone number, consent status, and ID linkage status are linked and stored for each ID. ID 801 is the ID number in the electronic payment service. In this embodiment, the ID number of the electronic payment service and the ID number of the linked service do not need to match. Each ID number or user information is linked by a common piece of information, the telephone number, and it is determined that the two are the same account based on whether the telephone numbers match. Telephone number 802 is the telephone number of the mobile terminal 101 registered in the linked service and is linked to ID 801. The consent status 803 stores "agree" or "disagree" according to the user's consent operation on the screen of Figure 7(b) displayed on the mobile terminal 101 in S601. The ID linkage status 804 stores whether or not the account is linked with the linked service. Therefore, the ID linkage status 804 is stored in association with (linked to) the memory status of the consent status 803, and if the consent status 803 is "consented", the ID linkage status 804 will be "○". In addition, in the electronic payment user information DB shown in Figure 8, the telephone number 802 corresponds to the specific information described above. Furthermore, the database shown in this diagram is managed similarly in the linked service. If the phone numbers are the same, the consent status 803 and ID linkage status 804 stored in both services will contain the same information. As a result, the linked service determines, for example, whether to display the guidance 701 in Figure 7(a) based on the ID linkage status 804. In other words, the display screen of the linked application for IDs where the ID linkage status 804 is stored as "×" is controlled to display guidance 701. As explained above, different ID numbers (or strings) are stored in both services, each linked to a phone number.

[0055] In S614, the electronic payment server 102 begins providing payment functionality within the linked application 401. Figure 7(g) shows the home screen of the linked application 401 after the linking process is complete. This screen is accessed when the user presses the "Return to Service" button 709 on the linking completion screen shown in Figure 7(f). Compared to the home screen of the linked application 401 shown in Figure 7(a), it can be seen that the electronic payment function 710 has been added. From this point onward, by launching the linked application 401, the user can use some of the electronic payment service functions in addition to the functions of the linked application within the same application. Note that the electronic payment service functions as a mini-application within the linked application. Therefore, there are limitations on the functionality of the electronic payment service within the linked application 401. For this reason, after the linking process is completed in S614, the electronic payment server 102 may display a message prompting the user to install the electronic payment application 403 on the mobile terminal 101. The display method is not limited, but for example, a message may be displayed in the space where the electronic payment function of the linked application 401 is displayed.

[0056] The above is a sequence diagram of the ID linking process between the partner service and the electronic payment service in this embodiment. By starting the user flow from the partner application 401, the electronic payment service can be made known to a larger number of users. In addition, the process of registering a phone number with the electronic payment service, in which the user directly enters the phone number, is omitted by prefill-in and entered automatically, thus improving convenience for the user.

[0057] Next, the processing flows focusing on the mobile terminal 101 and the electronic payment server 102 will be explained using Figures 9 and 10.

[0058] Figure 9 is a flowchart illustrating the ID linking process in the mobile terminal 101. This process is executed by the CPU 301 of the mobile terminal 101 loading the program of the linked application 401, which is stored in the ROM 302 or storage device 304, into the RAM 303. Since each process in this flowchart is executed by the CPU 301 controlling the various functional units shown in Figure 4(b), the main component of the process in this flowchart will be the linked application 401. This process is started when the user taps the guidance 701 on the home screen of the linked application 401 shown in Figure 7(a).

[0059] In S901, the linked application 401 displays a consent screen. In S902, the linked application 401 determines on the consent display screen whether the user performed a consent action in S901. If it determines that a consent action was performed, the linked application 401 proceeds to S903. On the other hand, if it determines that no consent action was performed, the linked application 401 terminates the processing of this flowchart.

[0060] In S903, the linked application 401 displays the linking registration screen shown in Figure 7(c). In S904, the linked application 401 determines which button was pressed on the linking registration screen. If it is determined that the user has never used the electronic payment service and button 705, which indicates new registration with the linked service's ID, was pressed, the linked application 401 proceeds to S906. On the other hand, if it is determined that the user has already installed the electronic payment app but has not linked their ID with the linked service and button 706 was pressed, the linked application 401 proceeds to S905.

[0061] In S905, the linked application 401 sends a message to the electronic payment server 102 indicating that it will perform ID linkage processing. As a result, the electronic payment server 102 updates the electronic payment user information DB 521 stored in the memory unit 520 and shares the linkage status with the linked service. After that, the linked application 401 terminates the processing of this flowchart.

[0062] In S906, the linked application 401 performs prefill-in. That is, it retrieves the telephone number from the user information registered in the linked server 103 and displays it on the telephone number display screen shown in Figure 7(d). In S907, the linked application 401 sends the telephone number to the electronic payment server 102. The transmission method is as explained in Figure 6.

[0063] In S908, the linked application 401 receives an authentication code from the electronic payment server 102 via SMS. In S909, the mobile terminal 101 sends the authentication code to the electronic payment server 102. After that, the linked application 401 terminates the process of this flowchart.

[0064] Figure 10 is a flowchart of the ID linking process of the electronic payment server 102. This process is executed by the CPU of the electronic payment server 102 loading the program stored in ROM or storage device into RAM. This process starts when a request to display the electronic payment web view is received from the mobile terminal 101 based on the user operation on the linking registration screen shown in Figure 7(c).

[0065] In S1001, the electronic payment server 102 displays a linking registration screen on the mobile terminal 101. Specifically, the electronic payment server 102 displays a linking registration screen, as shown in Figure 7(c), on the web view display screen within the linked application running on the mobile terminal 101.

[0066] In S1002, the electronic payment server 102 obtains the phone number of the mobile terminal 101 from the mobile terminal 101. In S1003, the electronic payment server 102 generates an authentication code. In S1004, the electronic payment server 102 sends the generated authentication code via SMS to the obtained phone number. In S1005, the electronic payment server 102 performs authentication processing on the code obtained from the mobile terminal. In S1006, the electronic payment server 102 determines whether the code authentication was successful. If it determines that the code authentication was successful, the electronic payment server 102 proceeds to S1007; otherwise, it returns to S1006.

[0067] In S1007, the electronic payment server 102 creates an account. That is, it adds the information of the new account to the electronic payment user information DB 521 shown in Figure 8. In addition, the linked application 401 displays the linking completion screen shown in Figure 7(f). After that, the electronic payment server 102 terminates this flowchart.

[0068] As described above, this embodiment improves the convenience of using electronic payment services. Specifically, the electronic payment service and the linked service are linked by displaying the trigger for using the electronic payment service on the display screen of the linked application. By linking IDs, it becomes possible to use the electronic payment service within the linked application 401 already installed on the mobile terminal 101, saving the user the trouble of installing an electronic payment application. In addition, the "telephone number" that is required to be entered during the new account registration process for the electronic payment service can be obtained from the linked server 103. The user can avoid directly entering their telephone number, thereby avoiding input errors. In other words, the user can use the electronic payment service with fewer steps, thus improving convenience.

[0069] <Other Embodiments> In the embodiment described above, SMS authentication was used as the authentication method in S612 of Figure 6. However, this is not the only option; for example, there may be a form of authentication that uses outgoing calls. In outgoing call authentication, the mobile terminal 101 makes a call to the electronic payment server 102 via a telephone line. The authentication method determines that authentication is successful when the telephone number stored in the incoming call history of the electronic payment server 102 matches the telephone number of the mobile terminal 101 that was notified in advance.

[0070] The above-described embodiment uses an electronic payment service and its linked service, which require registration of a phone number for use, as an example, but is not limited to this. It can be applied to any application that requires phone number input for account registration, not just electronic payments, but also, for example, to ID linking between social networking services (SNS) applications.

Claims

1. An information processing device that communicates with a partner server capable of providing services in conjunction with an electronic payment service, and a mobile terminal capable of using the partner service provided by the partner server, and provides the electronic payment service, When an operation to generate account information is performed on the aforementioned mobile terminal, an acquisition means is provided to obtain specific information included in the account information managed by the aforementioned linked service from the aforementioned linked service, A code transmission means that transmits an authentication code to the destination terminal indicated by the acquired specific information, When the authentication code is received from the terminal, an account generation means generates account information for the electronic payment service linked to the linked service, which includes the specific information. An information processing device characterized by comprising:

2. The information processing device according to claim 1, characterized in that the specific information includes information on the telephone number of the mobile terminal that uses the linked service.

3. The information processing apparatus according to claim 2, further comprising a display control means for causing the display unit of the mobile terminal to display a screen for generating an account for the electronic payment service.

4. The information processing apparatus according to claim 3, characterized in that the display control means causes a screen for generating an account as a web view screen on the application of the linked service operating on the mobile terminal.

5. If the linked service has given consent to share the account information with the electronic payment service, The information processing apparatus according to claim 4, characterized in that the display control means causes the display unit to display a screen for generating an account for the electronic payment service.

6. The information processing apparatus according to claim 5, wherein the acquisition means acquires the specific information when an operation is performed on the screen for generating the account to generate an account for the electronic payment service using the account information of the linked service.

7. The information processing device according to claim 1, characterized in that each account for the electronic payment service is stored in the database of the information processing device, associated with whether or not it is linked to the linked service.

8. The information processing device according to claim 7, characterized in that when the account generation means generates a count for the electronic payment service via the linked service, the account is stored in the database as having been linked with the linked service.

9. The information processing device according to claim 7, characterized in that, if the account of the linked service is not an account linked to the electronic payment service, a message prompting the user to link with the electronic payment service is displayed on the display screen of the linked service.

10. The information processing device according to claim 9, characterized in that when the user presses the aforementioned notification, a screen for performing a consent operation is displayed.

11. The information processing device according to claim 7, characterized in that, if the account of the linked service is an account that has already been linked with the electronic payment service, the linked service displays an indication that the functions used in the electronic payment service are available.

12. The information processing device according to claim 1, characterized in that the functions of the electronic payment service can be used within the linked service to which the account has already been linked.

13. A control method for an information processing device that communicates with a partner server capable of providing services in conjunction with an electronic payment service, and a mobile terminal capable of using the partner service provided by the partner server, and provides the electronic payment service, When an operation to generate account information is performed on the aforementioned mobile device, the acquisition step involves obtaining specific information included in the account information managed by the aforementioned linked service from the aforementioned linked service, A code transmission step in which an authentication code is sent to the destination terminal indicated by the specific information obtained, When the authentication code is received from the terminal, an account generation step is performed to generate account information for the electronic payment service linked with the linked service, which includes the specific information. A control method for an information processing device, characterized by comprising the following:

14. A program for providing an electronic payment service, which operates on an information processing device that communicates with a partner server capable of providing a service in conjunction with an electronic payment service, and a mobile terminal capable of using the partner service provided by the partner server, wherein the information processing device When an operation to generate account information is performed on the aforementioned mobile terminal, an acquisition means is provided to obtain specific information included in the account information managed by the aforementioned linked service from the aforementioned linked service, A code transmission means that transmits an authentication code to the destination terminal indicated by the acquired specific information, When the authentication code is received from the terminal, an account generation means generates account information for the electronic payment service linked to the linked service, which includes the specific information. A program characterized by being designed to function as such.

15. An information processing system including an electronic payment server that provides electronic payment services, a partner server that can provide services in cooperation with the electronic payment service, and a mobile terminal that can use the electronic payment service and the partner service provided by the partner server, The aforementioned mobile terminal is A display control means that displays a consent screen for sharing user information of the linked service with the electronic payment service, When a consent operation is performed on the consent screen, the request means requests the user information from the linked server, Equipped with, The aforementioned linked server is: Based on the aforementioned request, the system includes a transmission means for obtaining specific information contained in the account information corresponding to the mobile terminal from a storage unit and transmitting it, The electronic payment server described above is A code transmission means that transmits an authentication code to the destination terminal indicated by the acquired specific information, When the authentication code is received from the terminal, an account generation means generates account information for the electronic payment service linked to the linked service, which includes the specific information. An information processing system characterized by comprising the following features.

Images