Information processing device, information processing method, and program

Abstract

To enable a user to efficiently set a payment method available for one service as a payment method for another service. [Solution] An information processing device comprising: an acquisition unit that acquires request information from a terminal device of a user of an electronic payment service requesting that the user's account information in the electronic payment service be linked to an external service; an integration unit that links the account information to the external service based on the acquired request information; and a setting unit that sets payment methods that the user can use in the electronic payment service, which are included in the account information, as payment methods that can be used in the external service in accordance with the linking.

Description

[Technical Field]

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

[0002] Conventionally, there is known a technology for registering credit card information in a payment app installed on a terminal device such as a smartphone, and executing credit card payments via the payment app without exposing the physical credit card to the outside. For example, Patent Document 1 describes a technology for, when a card registration request is received from a user terminal, performing authentication based on the card information, registered user information, and input information input from the user terminal, and registering the card in the app based on the result of the authentication. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-103891 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above technology requires users to manually register their credit card information in the app, which means that with the conventional technology, users may not be able to efficiently set a payment method available for one service as a payment method for another service.

[0005] The present invention has been made in consideration of these circumstances, and one of its objectives is to provide an information processing device, an information processing method, and a program that enable users to efficiently set a payment method available for one service as the payment method for another service. [Means for solving the problem]

[0006] One aspect of the present invention is an information processing device comprising: an acquisition unit that acquires request information from a terminal device of a user of an electronic payment service requesting that the user's account information in the electronic payment service be linked to an external service; an integration unit that links the account information to the external service based on the acquired request information; and a setting unit that sets payment methods that the user can use in the electronic payment service, which are included in the account information, as payment methods that can be used in the external service in accordance with the linkage. [Effects of the Invention]

[0007] According to one aspect of the present invention, an information processing device, an information processing method, and a program can be provided that enable a user to efficiently set a payment method available for one service as a payment method for another service. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100 according to the first embodiment. [Figure 5] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 10 is a diagram showing an example of a top screen of the payment application 20. [Figure 8] FIG. 10 is a diagram illustrating an example of the flow of account linkage between an electronic payment service and an external service. [Figure 9] FIG. 10 is a diagram illustrating an example of a flow for provisioning a credit card after account linkage is completed. [Figure 10] FIG. 10 is a diagram illustrating an example of detailed processing of provisioning executed by a setting unit 158. [Figure 11] FIG. 10 is a diagram showing an example of a cooperative relationship between payment methods of an electronic payment service and payment methods of an external service. [Figure 12] FIG. 10 is a diagram showing an example of payment methods via an application interface displayed by an external service after the payment methods are linked. [Figure 13] FIG. 10 is a diagram showing an example of payment methods via a web interface displayed by an external service after the payment methods are linked. [Figure 14] 10 is a sequence diagram showing an example of the flow of processing executed by the payment application 20, the payment server 100, and the external service server 200 in cooperation with each other. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, with reference to the drawings, embodiments of an information processing device, an information processing method, and a program according to the present invention will be described. Various devices, such as a "server," a "management device," and an "information providing device," that provide services to users and perform internal analysis, may be implemented as a group of distributed devices, and each device may be operated by a different business. Furthermore, the hardware owner (the cloud server provider) and the business that actually operates the device may also be different. An application program and a payment server work together to provide an electronic payment service. In the following description, the application program is referred to as a "payment app." An electronic payment service is a service that supports payments for the purchase of goods and services at a store. A store is, for example, a physical store (real-world store) existing in real space, but may also include a virtual store for e-commerce transactions. A virtual store may also include a store operated by an entity other than the operator of the electronic payment service. In such a case, a transition to an interface screen for the electronic payment service may be performed when making a payment for a purchase at the virtual store. In an electronic payment service, a store is treated as belonging to, for example, an affiliated store (brand), and processing such as payment when a purchase is made at the store is primarily conducted between the user and the affiliated store. Alternatively, processing such as payment may be carried out between the user and the store.

[0010] [Electronic payment service] Figure 1 shows an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by a payment server 100. The payment server 100 communicates with, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, and an external service server 200 via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, etc.

[0011] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment app 20, which operates in cooperation with the payment server 100 to provide electronic payment services to users. The payment app 20 is installed on the user terminal device 10 from, for example, an application store, and controls the camera, communication device, touch panel, etc.

[0012] The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device. The store code image 60 is placed in the store and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0013] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, tablet terminal, personal computer, etc. An interface for affiliated stores 72 runs on the second store terminal device 70. The interface for affiliated stores 72 may be an app for affiliated stores or a browser. The interface for affiliated stores 72 accepts coupon settings and the like from the operator of the affiliated store and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image and reading the code image displayed by the user terminal device 10 by executing the app for affiliated stores.

[0014] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, this distinction will not be made and it is assumed that payment information is sent from the first store terminal device 50.

[0015] The external service server 200 provides various services to users who have registered accounts via multiple types of interfaces, including a web interface and an application interface. For example, the external service server 200 provides a web browser that can be installed on the user terminal device 10. By logging in to the web browser on the user terminal device 10, the user can use various services, such as personalized search and email services, tailored to the user's preferences. Furthermore, for example, the external service server 200 provides an application program that can be installed on the user terminal device 10. By logging in to an application on the user terminal device 10, the user can use various services, such as personalized search and email services, on the application.

[0016] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns for electronic payment: Pattern 1 and Pattern 2.

[0017] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10, with the payment application 20 running, decodes the store code image 60 using its optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is the domain of the electronic payment service to which store identification information has been added, and is associated with an affiliated store ID, store ID, etc. in the payment server 100 (described below). The payment application 20 sends first payment information including the store URL and account ID to the payment server 100 (S2). The payment server 100 searches for store information (described below) using the affiliated store ID and store ID corresponding to the store URL, acquires the affiliated store name and store name information (S3), and sends this to the payment application 20 (S4). The user enters the payment amount into the user terminal device 10 on the screen displaying the affiliated store name and store name (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount and sends it to the payment server 100 (S6). The payment server 100 makes the electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notice (information for displaying a payment completion screen) to the payment app 20 (S8), and the payment app 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include information on the payment amount in addition to the store URL. In this case, the step of the user inputting the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0018] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, the payment app 20 sends a request to issue a one-time code to the payment server 100 when the payment app 20 is launched, when a payment operation is performed in the payment app 20, at the automatic update timing (e.g., every minute), and at other timings (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image, such as a QR code or barcode, generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first in-store terminal device 50, and the first in-store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). The first in-store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode, manually entering it, etc. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs electronic payment (S17). Then, the payment server 100 sends a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0019] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuing a one-time code may be omitted in store scanning, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0020] [Payment server] FIG. 4 is a configuration diagram of the payment server 100 according to the first embodiment. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 130, an information management unit 140, an information processing unit 150, and a storage unit 170. The information processing unit 150 further includes an acquisition unit 152, a linking unit 154, a determination unit 156, and a setting unit 158. The components other than the communication unit 110 and the storage unit 170 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0021] The storage unit 170 is a HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172, payment content information 174, and affiliated store / shop information 176.

[0022] The communication unit 110 is a communication interface for connecting to the network NW, and is, for example, a network interface card.

[0023] The payment content providing unit 120 has, for example, a function of a web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The payment content providing unit 120 reads out necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs from the user while content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

[0024] The payment processing unit 130 performs payment processing based on the payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0025] FIG. 5 is a diagram showing an example of the contents of user information 172. User information 172 is an example of user registration information. User information 172 includes, for example, a user URL, account ID, telephone number, and password, as well as other information such as email address, user ID, name, address, date of birth, registration date, charge balance, credit card payment settings, credit card limit, credit card payment amount, available credit card payment amount, payment method settings, bank account, credit card number, balance card number, charge history information, and payment history information. The user URL is used for remittance processing between users. When registering for the electronic payment service, registration of a phone number and password is required. The account ID is issued to the user by the payment server 100, and the user ID can be set by the user (or does not have to be set). The email address, name, address, and date of birth are also information that can be set by the user (or do not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0026] The charge balance indicates the balance of electronic money set by the user by transferring funds to the account in advance. Transfer methods include transfers from a designated bank's ATM (Automatic Teller Machine) or from a registered bank account. The credit payment setting indicates whether the settings for electronic credit payment have been completed and is set to either "Completed" or "Not Completed." The credit payment limit is the monthly credit payment limit. The credit payment amount is the amount of credit payment already used in the current month. The available credit payment amount is the amount of credit payment available in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the figure shows only one credit payment limit, in reality, there may also be daily limits, and the lower of these may be set as the credit payment limit. Further details on credit payments will be discussed later. The payment method setting indicates whether the user will currently make electronic payments using the charge balance or by credit payment. The bank account and credit card number are information on a bank account or credit card number (account number, card number), respectively, that can be used to deposit funds into an electronic payment service. The balance card number is information on a card number that identifies a balance card. Here, a balance card refers to a virtual card that a user can charge in advance from a bank account or a charge balance and use to make an electronic payment. By using a balance card, a user can make an online payment, for example, at an online shopping site that does not support charge balance payments, by entering the card number of the balance card. In this case, the online shopping site sends payment information (including, for example, the payment amount and the balance card number) to the payment server 100, and the payment server 100 performs the payment by subtracting the payment amount from the charge balance.

[0027] The credit card and balance card may be integrated and issued as a single hybrid card. In this case, the hybrid card may be a physical card rather than a virtual card. When a hybrid card is issued, the payment app 20 is configured to allow the user to switch the payment method of the hybrid card between charge balance payment and credit payment. This allows the user to use the hybrid card to make a payment at the store's credit payment terminal, even at a physical store that is not affiliated with the electronic payment service, to execute charge balance payment or credit payment. The charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. The payment history information is information that indicates the details of each payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0028] 6 is a diagram showing an example of the contents of affiliated store / store information 176. The affiliated store / store information 176 includes, for example, a first table 176A in which an affiliated store ID and a store ID are associated with a store URL, a second table 176B in which an affiliated store ID is associated with an affiliated store name and sales amount (described above), and a third table 176C in which a store ID is associated with a store name. In addition to this information, the affiliated store / store information 176 may also include information such as the category of the affiliated store or store, the store's location, and payment patterns.

[0029] The information management unit 140 manages the user information 172 and the affiliated store / store information 176 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds new records to, edits, deletes, etc. the user information 172 and the affiliated store / store information 176.

[0030] As will be described later, the information processing unit 150 performs account linking between the electronic payment service and the external service provided by the external service server 200, and the associated linking of payment methods. Details of the processing executed by the information processing unit 150 will be described later. The information processing unit 150 is an example of an "information processing device" in the claims.

[0031] [Electronic Payment] When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 references the user information 172 to acquire the "payment method setting" of the user. For users whose "payment method setting" is set to "charge balance," the payment processing unit 130 performs electronic payment as follows: For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales proceeds. The item value of the affiliated store's sales proceeds is not itself used as electronic money, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0032] The payment processing unit 130 performs electronic payments for users whose "setting information" is set to "credit card payment" as follows. Credit card payment is a payment method in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service. The operator of the electronic payment service acts as the creditor, allowing electronic payments within the credit card payment limit and independent of the remaining balance. To receive the credit card payment service, a user may be required to obtain a credit card provided by the operator of the electronic payment service. The monthly amount used for credit card payment is settled on the following month's payment date, for example, by debit from a bank account. In this case, the payment processing unit 130 makes a provisional settlement by adding the settlement amount to the credit card payment amount and subtracting the same amount from the available credit card balance. On the closing date, the payment processing unit 130 performs the process described above to debit the current month's payment on the following month's payment date, or requests the credit card company operator to perform this process. If the settlement amount exceeds the available credit card balance at the time of provisional settlement, an error notification is returned to the payment app 20.

[0033] [Top screen] FIG. 7 is a diagram showing an example of the top screen of the payment application 20. A code image CI is displayed on the top screen. The code image CI includes, for example, a barcode and a QR code. A selector switch SW is displayed next to the code image CI to switch between electronic payment using the charge balance and electronic payment by credit card. Note that the "switch" and "button" refer to a GUI (Graphical User Interface) implemented in cooperation with the touch panel. In FIG. 7, "Credit" is displayed, which means that the setting is for electronic payment by credit card. The user can switch between electronic payment using the charge balance and electronic payment by credit card by, for example, swiping the selector switch SW.

[0034] The top screen also includes an operation area OA and transition buttons TB1, TB2, and TB3. The operation area OA is provided with buttons for instructing major operations in electronic payment, such as a button for instructing scanning (starting a user scan), a button for transferring the charge balance to another user, a button for displaying the points the user has earned, and a button for displaying the history of electronic payments performed by the user. When transition button TB1 is operated, the screen transitions to a payment screen that displays the code image used for electronic payment and the available balance. When transition button TB2 is operated, the screen transitions to a screen that displays the available balance for balance payment or credit payment. In FIG. 7, electronic payment using the charge balance is set, so when transition button TB2 is operated, the available balance for balance payment is displayed.

[0035] Below the operation area OA, a group of buttons (switches) M1, M2, ... for launching mini apps are further displayed. A mini app is an app that operates using the payment app 20 as a platform and provides some kind of service. A service provider develops a mini app by referring to an SDK (Software Development Kit), which is an app development program and technical documentation provided by the administrator of the payment app 20. A mini app is an app that operates while the payment app 20 is running. For example, a part or all of the mini app may be installed when the payment app 20 is installed, or a part or all of the mini app may be installed from a service server corresponding to the mini app. For example, when a mini app is launched, the mini app accesses an external service server 200 that provides a service corresponding to the mini app, and the mini app and the external service server 200 work together to provide the service to the user. In this case, the external service server 200 may be the payment server 100 itself. As an example, Figure 7 displays a button M1 for a mini-app that provides a function related to coupons that can be used in electronic payment services provided by affiliated stores, and a button M2 for a mini-app that provides a function to invest in investment products (e.g., stocks, bonds, etc.) provided by a securities company.However, buttons for launching various types of mini-apps may be displayed, such as a reservation app for using amusement facilities such as movie theaters, or a payment app for paying public transportation fares.

[0036] [Linkage with external services] Transition button TB3 is a transition button for linking an account for an electronic payment service with an account for an external service provided by external service server 300. When transition button TB3 is operated, payment application 20 transitions to a screen for linking an account for an electronic payment service with an account for an external service provided by external service server 300. In the following, this embodiment will describe a case where payment methods available to a user in an electronic payment service are linked to external service server 300 in addition to linking accounts.

[0037] Fig. 8 is a diagram showing an example of the flow of account linking between an electronic payment service and an external service. The screen shown in Fig. 8 is displayed, for example, when a user presses transition button TB3 on the top screen of payment application 20 shown in Fig. 7.

[0038] As shown in the left part of FIG. 8, for example, when a user presses transition button TB3 on the top screen, payment application 20 displays information on the screen indicating that the electronic payment service account will be linked to an external service. In the left part of FIG. 8, area A1 shows a list of permissions and information of the electronic payment service account that will be provided to the external service through the linkage. For example, in area A1, payment application 20 displays information such as the following: that payment can be made using the electronic payment service when making a payment with the external service; that payment using the electronic payment service can be continuously used for payments with the external service (e.g., a subscription with the external service); that the payment application 20 will refer to a portion of the phone number registered with the electronic payment service; that the information and card information registered with the electronic payment service will be referred to; that the user's payment information and service usage history will be referred to; and that the payment application 20 will refer to personal identification information (e.g., name, date of birth, address, etc.).

[0039] When the user confirms the consent items displayed in area A1 and presses transition button TB4, payment application 20 sends request information requesting that the user's account information in the electronic payment service be linked to an external service to payment server 100. On the other hand, when the user presses transition button TB5, payment application 20 transitions to, for example, the top screen of FIG. 7 without linking the account information.

[0040] When the acquisition unit 152 of the payment server 100 acquires request information from the payment application 20, the linking unit 154 links (shares) the user's account information (in this case, the account information may include the user's identification information stored in the user information 172 as well as the contents of the consent terms described in area A1) with the external service server 200 via the network NW.

[0041] In response to the linking by the linking unit 154, the setting unit 158 ​​sets the payment methods included in the account information that the user can use in the electronic payment service as payment methods that can be used in the external service. For example, referring to the user information 172 in FIG. 5, the user with account ID "001" can use a charge balance, credit card payment, a credit card, and a balance card as payment methods in the electronic payment service. Therefore, the setting unit 158 ​​sets the external service server 200 to make these payment methods available in the external service (or sends a request to the external service server 200 to make them available).

[0042] The right part of Fig. 8 shows a notification screen indicating that the linking by the linking unit 154 and the setting by the setting unit 158 ​​have been completed. As shown in the right part of Fig. 8, when payment application 20 receives completion information from payment server 100 indicating that the electronic payment service account has been linked to the external service, it displays the completion information on the screen. Furthermore, payment application 20 displays, for example, in area A2, notification information indicating that the payment method can be used with a device or service that has logged in to the external service, and a list of payment methods linked with the external service.

[0043] For example, the right side of Fig. 8 shows that the payment application 20 has already linked the charge balance, credit payment, balance card, and credit card to external services as payment methods. Note that the difference between credit payment and credit card is that credit payment requires the intervention of an electronic payment service, whereas credit card payment is executed without the intervention of an electronic payment service (unless the electronic payment service itself is the issuer of the credit card).

[0044] Provisioning In this way, a user can link multiple payment methods available in an electronic payment service to an external service with a simple operation, such as pressing the consent button TB4. However, for example, if an external service provides a digital wallet function that encrypts a credit card in a terminal device and enables credit card payments (tap payments) using the terminal device, processing generally referred to as provisioning, such as encryption processing and validation processing by the credit card issuer, is required. The following describes, as an example, a case in which an external service provides a digital wallet function corresponding to a credit card and credit card provisioning is performed accordingly. However, the present invention is not limited to such a configuration. Similarly, when an external service provides a digital wallet function corresponding to the balance card or hybrid card described above, provisioning such as encryption processing and validation processing for the balance card or hybrid card is also performed.

[0045] In response to the linking by the linking unit 154, the determination unit 156 determines whether the payment methods available to the user in the electronic payment service correspond to the digital wallet provided by the external service. More specifically, the determination unit 156 may determine whether the payment methods available to the user in the electronic payment service include a credit card. In the case of the right part of FIG. 8 , the determination unit 156 determines that a credit card, which is one of the payment methods available to the user in the electronic payment service, corresponds to a digital wallet. Therefore, the determination unit 156 causes the payment app 20 to display a transition button TB6 to guide the user to set up tap payment. When the user presses the transition button TB6, the payment app 20 transitions to a screen for performing provisioning. On the other hand, when the user presses the transition button TB7, the payment app 20 transitions to, for example, the top screen of FIG. 7 without performing provisioning.

[0046] Figure 9 is a diagram showing an example of the flow of credit card provisioning after account linking is completed. The screen shown in Figure 9 is displayed, for example, when the user presses transition button TB6 on the screen of payment application 20 shown on the right side of Figure 8.

[0047] As shown in the left part of FIG. 9, for example, when a user presses transition button TB6 on the payment app 20 screen shown in the right part of FIG. 8, the payment app 20 displays information indicating that a digital wallet will be set up in an external service. In the left part of FIG. 9, area A3 shows notification information indicating that touch payment at a store will be enabled by setting up the digital wallet. When the user checks the notification information displayed in area A3 and presses transition button TB8, the payment app 20, in cooperation with the setting unit 158 ​​of the payment server 100, performs provisioning to add a credit card to the digital wallet. On the other hand, when the user presses transition button TB9, the payment app 20 transitions to, for example, the screen shown in the right part of FIG. 8 without performing provisioning.

[0048] Once provisioning is complete, the payment application 20 displays information indicating that the credit card has been added to the digital wallet and that contactless payment has been enabled, as shown in area A4 on the right side of Figure 9. This allows the user to make electronic payments when purchasing goods or services at a brick-and-mortar store without exposing their physical credit card.

[0049] Furthermore, in conventional technologies, when a user sets up a credit card in a digital wallet, this is achieved by a separate operation that links the terminal device where the digital wallet is set up with the credit card information. On the other hand, according to the present embodiment, by linking accounts between the electronic payment service and the external service, it becomes possible to seamlessly set up a credit card in a digital wallet, thereby reducing the burden on the user compared to conventional technologies that require a separate operation that links the terminal device with the credit card information.

[0050] Fig. 10 is a diagram showing an example of detailed processing of provisioning. The screen shown on the left side of Fig. 10 is displayed, for example, when the user presses transition button TB8 on the payment application 20 screen shown on the left side of Fig. 9. Note that, for simplicity of explanation, the following description will be given simply assuming that payment application 20 is the subject of operation, but provisioning may be performed while communicating with setting unit 158 ​​of payment server 100 (for example, while being controlled by setting unit 158), and payment application 20 may simply display a screen.

[0051] First, the payment application 20 displays a confirmation screen for the user's address information, for example, in area A5. The user's address information may be, for example, the address information stored in user information 172. When the user confirms the address information and presses transition button TB10, the payment application 20 proceeds to the device selection screen, second from the left in FIG. 10. The device selection screen is a screen for specifying the terminal device on which the digital wallet is to be set up. For example, FIG. 10 shows, as an example, a device selection screen for selecting one of two devices (a smartphone corresponding to transition button TB11, and a tablet terminal corresponding to transition button TB12).

[0052] When the user selects one of the devices from the device selection screen and presses the corresponding transition button (transition button TB11 or TB12 in FIG. 10), payment application 20 connects to the bank server of the bank linked to the credit card. The bank to connect to at this time can be identified based on the bank account stored in user information 172, for example. After connecting to the bank server, payment application 20 then displays the terms and conditions of the issuer that issued the credit card. When the user confirms the issuer's terms and conditions and presses transition button TB13, provisioning is completed and the screen transitions to the screen shown on the right side of FIG. 9.

[0053] Figure 11 is a diagram showing an example of the linkage between payment methods of an electronic payment service and payment methods of an external service. The left side of Figure 11 shows the payment methods available to the user in the electronic payment service, and the right side of Figure 11 shows the payment methods available in the external service by linking the user's account with the electronic payment service. For example, the external service may provide multiple payment methods available via multiple types of interfaces, including a web interface and an app interface, and the determination unit 156 determines whether each of the multiple payment methods available to the user in the electronic payment service is compatible with each of the multiple payment methods provided by the external service.

[0054] When it is determined that each of the multiple payment methods available to the user in the electronic payment service corresponds to each of the multiple payment methods provided by the external service, setting unit 158 ​​sets each of the multiple payment methods available to the user in the electronic payment service to each of the multiple payment methods provided by the external service (or sends request information requesting setting to external service server 200). In another aspect, external service server 200 may have the correspondence determination function of determination unit 156 and the payment method setting function of setting unit 158, and payment application 20 or payment server 100 may simply send information about the payment methods available to the user in the electronic payment service to external service server 200 and request external service server 200 to determine the correspondence and set the payment method.

[0055] In the situation shown in FIG. 11, for example, payment methods available to a user in an electronic payment service include a charge balance, credit card payment, a balance card, and a credit card, while payment methods provided by an external service include a payment method via an application interface (e.g., purchasing an app or service from an application store), a payment method via a web interface (e.g., on a web browser screen), and a digital wallet. In this case, the determination unit 156 determines whether the charge balance, credit card payment, balance card, and credit card correspond to the payment method via the application interface, the payment method via the web interface, and the digital wallet, respectively. In the case of FIG. 11, the determination unit 156 determines that the charge balance, credit card payment, balance card, and credit card all correspond to the payment method via the application interface, the balance card and credit card correspond to the payment method via the web interface, and the credit card corresponds to the digital wallet. Therefore, the setting unit 158 ​​sets the payment method of the electronic payment service in association with the payment method of the external service, as indicated by the arrows in FIG. 11.

[0056] Figure 12 shows an example of a payment method via an app interface displayed by an external service after linking a payment method. Figure 12 shows an example of a case where, after linking a payment method, a user logs in to the external service and accesses an app store provided by the external service.

[0057] As shown in FIG. 12, when a user selects an app to purchase and proceeds to the purchase screen, the external service displays the payment methods linked to the electronic payment service, namely, the charge balance, credit card, balance card, and credit card, as shown in area A6. The user can select one of the displayed payment methods and press the payment button to perform electronic payment with the external service. For example, in the case of FIG. 12, the user selects the charge balance, so the external service server 200 transmits information to the payment server 100 indicating that the charge balance has been selected as the payment method and that the payment amount is 100 yen, and the payment processing unit 130 of the payment server 100 executes the charge balance payment for 100 yen.

[0058] Figure 13 shows an example of a payment method via a web interface displayed by an external service after linking a payment method. Figure 13 shows an example where, after linking a payment method, a user logs in to the external service and accesses an online shopping site using a web browser provided by the external service.

[0059] As shown in FIG. 13, when a user selects a product to purchase and proceeds to the purchase screen, the external service displays the payment methods linked from the electronic payment service, namely, a credit card and a balance card, as shown in area A7. For example, if the user selects a credit card, the user is normally required to enter the credit card number into input form IN. However, in this embodiment, as described above, the user's credit card information is linked to the external service, and the web browser provided by the external service presents the linked credit card number to the user with it automatically entered (auto-filled) into input form IN. The user can confirm the accuracy of the automatically entered credit card number and press the payment button to complete electronic payment with the external service.

[0060] In this way, according to this embodiment, even if there are multiple payment methods available in the electronic payment service, the user can link and set them as payment methods available in the external service with a simple operation. In particular, in the prior art, when a user sets a payment method in an external service, it is necessary to add a payment method for each individual service provided by the external service. However, according to this embodiment, the burden on the user of setting up such payment methods can be reduced.

[0061] [Processing flow] Fig. 14 is a sequence diagram showing an example of the flow of processing executed by cooperation between payment application 20, payment server 100, and external service server 200. The processing of the sequence diagram shown in Fig. 14 is executed, for example, when a user presses transition button TB4, which requests account linking, on the screen shown in the left part of Fig. 8.

[0062] First, the payment application 20 sends a request for account linking to the payment server 100 (step S10). Next, upon receiving the request for account linking, the payment server 100 executes account linking and setting of a payment method on the external service server 200 (step S12). Next, upon completing the account linking and setting of a payment method, the external service server 200 sends a completion notification to the payment server 100 (step S14).

[0063] Next, the payment server 100 determines whether the linked payment method is compatible with digital wallets (including credit cards) (step S16). Here, it is assumed that the linked payment method is determined to be compatible with digital wallets. In that case, the payment server 100 causes the payment application 20 to display a notification of account linking completion and a guide to setting up the digital wallet, as shown in the right part of FIG. 8 (step S18).

[0064] Next, in response to the user's operation, payment application 20 sends a digital wallet setting request to payment server 100 (step S20). Upon receiving the digital wallet setting request, payment server 100 executes provisioning (step S22). Upon completion of provisioning, payment server 100 sends a digital wallet setting completion notification to payment application 20 (step S24). This ends the processing of this flowchart.

[0065] For the sake of convenience, the above description distinguishes between the software functions of payment application 20, payment server 100, and external service server 200, but the allocation of these software functions may be rearranged as appropriate. For example, payment application 20 may have a function for linking user account information instead of payment server 100, and may directly request external service server 200 to link account information and set up a payment method without using payment server 100 as an intermediary. Furthermore, for example, external service server 200 may have some or all of the functions of payment server 100, and may link account information and set up a payment method through communication between payment application 20 and external service server 200.

[0066] According to the embodiment described above, a user can easily link and set payment methods available in an electronic payment service as payment methods available in an external service, and if the user has payment methods available in the digital wallet, provisioning is performed to activate the digital wallet after linking. In other words, this allows a user to efficiently set payment methods available in one service as payment methods for another service.

[0067] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0068] 10 User terminal device 20. Payment App 100 Payment Server 120 Payment Contents Department 130 Payment processing unit 140 Information Management Department 150 Information Processing Department 152 Acquisition Department 154 Collaboration Department 156 Judgment section 158 Setting Section 200 External service server

Claims

1. an acquisition unit that acquires, from a terminal device of a user of an electronic payment service, request information requesting that account information of the user in the electronic payment service be linked to an external service; a linking unit that links the account information with the external service based on the acquired request information; a setting unit that sets, in response to the link, a payment method that is included in the account information and that can be used by the user in the electronic payment service as a payment method that can be used in the external service; a determination unit that determines, in response to the link, whether a payment method that the user can use in the electronic payment service is compatible with a digital wallet provided by the external service; When it is determined that the payment method corresponds to the digital wallet, the setting unit sets the payment method to the digital wallet in accordance with the user's consent. Information processing device.

2. The payment method corresponding to the digital wallet is a credit card, the setting unit executes provisioning for setting the credit card in the digital wallet after the linking is completed, and sets the payment method in the digital wallet upon completion of the provisioning. The information processing device according to claim 1 .

3. an acquisition unit that acquires, from a terminal device of a user of an electronic payment service, request information requesting that account information of the user in the electronic payment service be linked to an external service; a linking unit that links the account information with the external service based on the acquired request information; a setting unit that sets, in response to the link, a payment method that is included in the account information and that can be used by the user in the electronic payment service as a payment method that can be used in the external service; The external service provides a plurality of payment methods available through a plurality of types of interfaces, including a web interface and an app interface; a determination unit that determines whether each of a plurality of payment methods that can be used by the user in the electronic payment service and that are included in the account information corresponds to each of the plurality of payment methods provided by the external service; when it is determined that each of the plurality of payment methods available to the user in the electronic payment service corresponds to each of the plurality of payment methods provided by the external service, the setting unit sets each of the plurality of payment methods available to the user in the electronic payment service to each of the plurality of payment methods provided by the external service; Information processing device.

4. The computer acquires, from a terminal device of a user of an electronic payment service, request information requesting that account information of the user in the electronic payment service be linked to an external service; Linking the account information to the external service based on the acquired request information; In response to the link, set the payment methods that are included in the account information and that can be used by the user in the electronic payment service as payment methods that can be used in the external service; In response to the link, determining whether a payment method available to the user in the electronic payment service is compatible with a digital wallet provided by the external service; If it is determined that the payment method is compatible with the digital wallet, the payment method is set to the digital wallet in accordance with the user's consent. Information processing methods.

5. On the computer, acquires, from a terminal device of a user of an electronic payment service, request information requesting that account information of the user in the electronic payment service be linked to an external service; linking the account information with the external service based on the acquired request information; In response to the link, a payment method that is included in the account information and that can be used by the user in the electronic payment service is set as a payment method that can be used in the external service; determining whether a payment method available to the user in the electronic payment service corresponds to a digital wallet provided by the external service in response to the link; If it is determined that the payment method is compatible with the digital wallet, the payment method is set to the digital wallet in accordance with the user's consent. program.

6. The computer acquires, from a terminal device of a user of an electronic payment service, request information requesting that account information of the user in the electronic payment service be linked to an external service; Linking the account information to the external service based on the acquired request information; In response to the link, set the payment methods that are included in the account information and that can be used by the user in the electronic payment service as payment methods that can be used in the external service; The external service provides a plurality of payment methods available through a plurality of types of interfaces, including a web interface and an app interface; determining whether each of a plurality of payment methods available to the user in the electronic payment service, which are included in the account information, corresponds to each of the plurality of payment methods provided by the external service; When it is determined that each of the plurality of payment methods available to the user in the electronic payment service corresponds to each of the plurality of payment methods provided by the external service, each of the plurality of payment methods available to the user in the electronic payment service is set to each of the plurality of payment methods provided by the external service. Information processing methods.

7. On the computer, acquires, from a terminal device of a user of an electronic payment service, request information requesting that account information of the user in the electronic payment service be linked to an external service; linking the account information with the external service based on the acquired request information; In response to the link, a payment method that is included in the account information and that can be used by the user in the electronic payment service is set as a payment method that can be used in the external service; The external service provides a plurality of payment methods available through a plurality of types of interfaces, including a web interface and an app interface; determining whether each of a plurality of payment methods that can be used by the user in the electronic payment service, which are included in the account information, corresponds to each of the plurality of payment methods provided by the external service; When it is determined that each of the plurality of payment means available to the user in the electronic payment service corresponds to each of the plurality of payment means provided by the external service, each of the plurality of payment means available to the user in the electronic payment service is set to each of the plurality of payment means provided by the external service. program.

Images