Information processing device, information processing method, and program

Abstract

To enable secure and smooth sharing of sensitive information, such as bank account balances, between multiple services. [Solution] An information processing device that processes information through a service that operates in cooperation with a first app and a second app running on a user's terminal device, the information processing device comprising: a determination unit that determines whether a request to obtain the account balance of a bank account linked to the service, received from the second app, satisfies a specified condition; and a linking unit that, if it is determined that the specified condition is satisfied, receives the account balance of the bank account from the account management server based on first identification information of the user that is held in common by the information processing device itself and an account management server that manages the bank account, and links to the second app.

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 are known technologies for linking an account for an electronic payment service with a bank account. For example, Patent Document 1 discloses a technology for receiving and storing the account balance of a bank account linked to an electronic payment service from an account management server based on user identification information held in common by a payment server and an account management server that manages the bank account, when a request for obtaining the account balance of the bank account linked to the electronic payment service received from a payment app satisfies a predetermined condition. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2024-106165 A Summary of the Invention [Problem to be solved by the invention]

[0004] The technology described in Patent Document 1 securely and smoothly links the account balance of a bank account to an electronic payment service by using identification information different from the bank account number. However, with the conventional technology, for example, when a specific service such as an electronic payment service functions as a platform to operate multiple services, sensitive information such as the account balance of a bank account may not be securely and smoothly linked between these multiple services.

[0005] The present invention has been made in consideration of these circumstances, and one of its objectives is to provide an information processing device, information processing method, and program that can securely and smoothly share sensitive information, such as bank account balances, between multiple services. [Means for solving the problem]

[0006] One aspect of the present invention is an information processing device that processes information via a service that operates in cooperation with a first app and a second app running on a user's terminal device, and is equipped with a determination unit that determines whether a request to obtain the account balance of a bank account linked to the service, received from the second app, satisfies a specified condition, and a linking unit that, if it is determined that the specified condition is satisfied, receives the account balance of the bank account from the account management server based on first identification information of the user that is held in common by the information processing device itself and an account management server that manages the bank account, and links to the second app. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to provide an information processing device, an information processing method, and a program that can securely and smoothly share sensitive information, such as bank account balances, between multiple services. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. [Diagram 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Diagram 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] 1 is a configuration diagram of a payment server 100 according to a first embodiment. [Diagram 5] FIG. 13 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 13 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 2 is a diagram showing an example of the contents of bank account information 210 stored in a bank server 200. [Figure 8] 2 is a diagram showing an example of the contents of securities account information 310 stored in securities server 300. FIG. [Figure 9] FIG. 2 is a diagram showing an example of a top screen of a payment application 20. [Figure 10] FIG. 13 is a diagram showing an example of a charge screen of payment application 20. [Figure 11] FIG. 2 is a diagram illustrating an example of an authentication / consent flow executed by the bank server 200. [Figure 12] 1 is a diagram showing an example of an authentication / consent flow executed by a securities server 300. FIG. [Figure 13] 13 shows an example of the contents of a chain connection management table 178. FIG. [Figure 14] 13 is a diagram showing an example of a securities mini-appli screen that displays a bank account balance acquired by securities server 300 from bank server 200. FIG. [Figure 15] 1 is a sequence diagram showing an example of the flow of processes executed by a user terminal device 10, a payment server 100, a bank server 200, and a securities server 300. FIG. [Figure 16] FIG. 13 is a diagram showing an example of a transition process from a securities mini-appli to a bank mini-appli. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, with reference to the drawings, an embodiment of an information processing device, an information processing method, and a program of the present invention will be described. Various devices for providing services to users and performing internal analysis, such as a "server," "management device," and "information providing device" that will appear below, may be realized by a group of distributed devices, and each device may be operated by a different business operator. Furthermore, the owner of the hardware of the device (the cloud server provider) and the business operator 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 application. An electronic payment service is a service that supports payments related to the purchase of goods and services at a store. A store is, for example, a physical store (real store) that exists in the real world, but may also include a virtual store for electronic commerce. A virtual store may include a store provided by an entity different from the operator of the electronic payment service. In that case, when making a payment for shopping at a virtual store, the screen may be controlled to transition to an interface screen of the electronic payment service. 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 a store is mainly performed 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] Fig. 1 is a diagram showing 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, a bank server 200, and a securities server 300 via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, and the like.

[0011] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a 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 reception 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 application 20, thereby operating to provide an electronic payment service to a user in cooperation with a payment server 100. The payment application 20 is installed in 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, a tablet terminal, a personal computer, or the like. An interface 72 for affiliated stores runs on the second store terminal device 70. The interface 72 for affiliated stores may be an app for affiliated stores or a browser. The interface 72 for affiliated stores accepts coupon settings and the like made by 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 a 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 the payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, no distinction is made between these two and it is assumed that the payment information is sent from the first store terminal device 50.

[0015] In response to an instruction from a user, the bank server 200 transfers money from the user's bank account to the payment server 100, and the payment server 100 charges the user's charge balance (described below) by the received amount of the transfer. In addition, in response to an instruction from the user or the payment server 100, the bank server 200 transmits information indicating the account balance of the user's bank account (hereinafter, bank account balance) to the payment server 100, and the details of this process will be described later. The bank server 200 stores information indicating the user's bank account balance in the bank account information 210.

[0016] The securities server 300 provides an asset management service using the charge balance or bank account balance of the user in response to an instruction from the user. At this time, the securities server 300 obtains the bank account balance from the bank server 200 via the settlement server 100 and displays it on the user terminal device 10 of the user who wishes to use the asset management service; details of this process will be described later. The securities server 300 stores information indicating the user's securities account in the securities account information 310.

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

[0018] 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 activated decodes the store code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is an electronic payment service domain to which store-identifying information is added, and is associated with an affiliated store ID, a store ID, etc. in the payment server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the affiliated store ID and the store ID corresponding to the store URL, acquires the affiliated store name and the store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount into the user terminal device 10 on the screen on which the affiliated store name and the store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount, and transmits it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). The payment server 100 then transmits a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 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 not only the store URL but also information on the payment amount. In this case, the step of the user inputting the payment amount is omitted, and the information on the payment amount is included in the first payment information and transmitted to the payment server 100. Information on the affiliated store name and the store name may be included in the payment completion screen and displayed.

[0019] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, when the payment application 20 is started, when a payment operation is performed in the payment application 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or a 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 store terminal device 50, and the first store terminal device 50 decodes the code image by an optical reading function and obtains the one-time code, etc. (S15). The first store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). The payment server 100 then transmits a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0020] 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, issuance of a one-time code may be omitted in the store scan, 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.

[0021] [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, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized 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 realized by cooperation between software and hardware. The program may be stored in advance in a storage device (storage device having a non-transient storage medium) such as an HDD (Hard Disk Drive) or a flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or a CD-ROM, and may be installed in the storage device by mounting the storage medium in a drive device. The information management unit 140 further includes a generation unit 142, a determination unit 144, and a collaboration unit 146. Details of these functional units will be described later. The information management unit 140 is an example of an "information processing device" in the claims.

[0022] The storage unit 170 is a HDD, a flash memory, a 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, affiliated store / shop information 176, and a chain connection management table 178.

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

[0024] 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 appropriately reads necessary content from the payment content information 174 and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs by the user while the content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

[0025] 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.

[0026] FIG. 5 is a diagram showing an example of the contents of the user information 172. The user information 172 is an example of the registration information of a user. The user information 172 is information associated with information such as a user URL, an account ID, a phone number, a password, an email address, a user ID, a name, an address, a date of birth, a registration date, a charge balance, a credit payment setting, a credit payment limit, a credit payment amount used, a credit payment available amount, a payment method setting, a credit card number, a bank account, a bank mini app registration, a bank mini app ID, a securities mini app registration, a securities mini app ID, a charge history information, and a payment history information. The user URL is used for a remittance process between users. When registering for the electronic payment service, it is necessary to register a phone number and a password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be set by the user at will (does not have to be set). Similarly, the email address, and the name, address, and date of birth are information that can be set by the user at will (does 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.

[0027] The charge balance is information indicating the balance of electronic money that is set by a user by transferring money to an account in advance. The means of transfer include transfer from an ATM (Automatic Teller Machine) of a designated company (bank) and transfer from a registered bank account. The credit payment setting is information indicating whether or not the setting for enabling electronic payment by credit payment has been completed, and is set to either "completed" or "not completed." The credit payment limit is the credit payment limit that can be used each month, the credit payment usage amount is the amount of credit payment that has already been used in the current month, and the credit payment available amount is the amount of credit payment that can be used in the current month, which is calculated by subtracting the credit payment usage amount from the credit payment limit. Although only one credit payment limit is shown in the figure, in reality, there is also a daily upper limit, and the lower of these may be set as the credit payment limit. Further details of credit payment will be described later. The payment method setting is setting information indicating whether the user will perform electronic payment using the charge balance or payment by credit payment at that time. The bank account and credit card number are information on a bank account or credit card number (account number, card number) that can be used to deposit funds into an electronic payment service. Charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. Payment history information is information that indicates the details of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0028] The bank mini-app registration is information indicating whether or not a user has completed registration to the bank mini-app (for example, whether or not the user has logged in to the bank server 200 via the bank mini-app) when using an application program (hereinafter referred to as the "bank mini-app") provided by the bank server 200 on the payment app 20. The bank mini-app is an application program developed and provided using the payment app 20 as a platform, and the user does not need to download the app again, and registration to use the bank mini-app is completed by simply inputting necessary information on the payment app 20. Here, the necessary information includes, for example, information such as the user's bank account number and password, and if the user has not yet opened an account with the bank, information such as the user's name, date of birth, email address, telephone number, and identification document (photograph of face). When registration to use is completed, the information management unit 140 stores flag information (for example, "YES") indicating that the user has registered to the bank mini-app in the "bank mini-app registration" of the user information 172. When registration to use is completed, the user gives consent to be described later on the bank mini-app. This allows the user to use various functions provided by the bank server 200 (e.g., displaying bank account balance, transferring money, taking loans, foreign currency deposits, fixed term deposits, purchasing investment trusts, etc.) via the bank mini-app running on the payment app 20. When the user uses these various functions via the bank mini-app, the bank mini-app accesses the bank server 200 to receive these functions (in other words, the bank server 200 also functions as a service server that provides the functions of the bank mini-app). As described below, registration to the bank mini-app is performed, for example, when the user launches the bank mini-app for the first time on the top screen of the payment app 20 or when the user launches the bank mini-app for the first time to check the bank account balance on the charge balance charge screen. The bank mini-app is an example of a "first app" in the claims.

[0029] When the user completes registration for the bank mini app, the generation unit 142 generates a bank mini app ID for the user to uniquely identify the bank mini app, and stores the bank mini app ID in the user information 172. Furthermore, the information management unit 140 notifies the bank server 200 of the generated bank mini app ID.

[0030] The securities mini-app registration is information indicating whether or not a user has completed registration to the securities mini-app (for example, whether or not the user has logged in to the securities server 300 via the securities mini-app) when using an application program (hereinafter referred to as the "securities mini-app") provided by the securities server 300 on the payment application 20. Like the banking mini-app, the securities mini-app is an application program developed and provided using the payment application 20 as a platform, and the user does not need to download the application separately, and registration to the securities mini-app is completed by simply inputting necessary information on the payment application 20. Here, the necessary information includes, for example, information such as the user's securities account number and password, and if the user has not yet opened an account with the securities company, information such as the user's name, date of birth, email address, telephone number, and identification document (face photo). When registration is completed, the information management unit 140 stores flag information (for example, "YES") indicating that the user has been registered to the securities mini-app in the "securities mini-app registration" of the user information 172. When registration is completed, the user gives consent to be described later on the securities mini-app. This allows the user to use various functions provided by the securities server 300 (e.g., asset management into stocks and ETFs (Exchange Traded Funds) using the charge balance or bank account balance as capital, viewing stock and ETF market information, etc.) via the securities mini-app running on the payment app 20. When the user uses these various functions via the securities mini-app, the securities mini-app accesses the securities server 300 to receive these functions (in other words, the securities server 300 also functions as a service server that provides the functions of the securities mini-app). Registration into the securities mini-app is performed, for example, when the user launches the securities mini-app on the top screen of the payment app 20 for the first time. The securities mini-app is an example of a "second app" in the claims.

[0031] When a user completes registration for the securities mini app, generation unit 142 generates a securities mini app ID for the user to uniquely identify the securities mini app, and stores the ID in user information 172. Furthermore, information management unit 140 notifies securities server 300 of the generated securities mini app ID.

[0032] 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 name and sales amount (described above) are associated with an affiliated store ID, 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 location of the store, and payment patterns.

[0033] The information management unit 140 manages user information 172 and 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, and deletes the user information 172 and affiliated store / store information 176.

[0034] [Bank server] FIG. 7 is a diagram showing an example of the contents of bank account information 210 stored by bank server 200. Bank account information 210 is information in which, for example, bank account number, bank account balance, bank mini-app ID, user consent, validity period, and other information are associated with each other. Bank account number is user identification information given by the bank when the user opens an account with the bank that operates bank server 200. Bank account balance is information indicating the balance deposited by the user in the bank. Bank mini-app ID is the bank mini-app ID notified by payment server 100. User consent is information indicating whether or not the user agrees to enable the bank account balance display function (in other words, information indicating whether or not the user agrees to information sharing of bank account balance). When the user completes logging in to bank server 200, bank server 200 inquires of the user whether or not the user agrees to enable the bank account balance display function, and if the user agrees to enable the bank account balance display function, stores "YES" in the user consent of bank account information 210.

[0035] The validity period is a consent-free usage period of the bank mini-app that is set by the bank server 200 when the user agrees to enable the bank account balance display function. In other words, during the set validity period, the user can use the bank account balance display function without consent again. The validity period is set, for example, to expire 90 days after the user's consent is confirmed. During this period, every time the user uses the bank account balance display function via the bank mini-app, the bank server 200 extends (refreshes) the validity period by resetting it from the time of the last use of the function as the starting point. On the other hand, if the user does not use the bank mini-app again during the validity period, the bank server 200 determines that the consent-free usage period of the bank mini-app has expired. In this case, when the user uses the bank mini-app again, the bank server 200 inquires the user again about whether or not to enable the bank account balance display function. After that, when the user agrees again to enable the bank account balance display function, the bank server 200 resets the validity period from the time of the user's consent as the starting point. Note that the validity period is refreshed only when the user uses the bank mini-app (in other words, when the bank mini-app accesses the bank server 200 using the user's bank mini-app ID as a key), and is not refreshed, for example, when a transfer is made from the bank server 200 to top up the charge balance.

[0036] [Securities Server] 8 is a diagram showing an example of the contents of securities account information 310 stored by securities server 300. Securities account information 310 is information in which, for example, securities account number, held stock information, securities mini-app ID, user consent, validity period, and other information are associated. The securities account number is user identification information given by the securities company when the user opens an account with the securities company that operates securities server 300. The held stock information is information indicating stocks that the user purchased at the securities company and is holding and their details (held quantity, acquisition price, etc.). The securities mini-app ID is the securities mini-app ID notified by settlement server 100. The user consent is information indicating whether or not the user consents to enabling the display function of bank account balances managed by bank server 200 (in other words, information indicating whether or not the user consents to information sharing of bank account balances). When the user completes logging in to the securities server 300, the securities server 300 inquires the user as to whether or not he or she agrees to enable the bank account balance display function, and if the user agrees to enable the bank account balance display function, "YES" is stored in the user consent field of the securities account information 310.

[0037] The validity period is the consent-free usage period of the securities mini app. That is, during the validity period, the user can use the bank account balance display function without consent again. The validity period is set, for example, to expire 90 days after the user's consent is confirmed. During this period, every time the user uses the bank account balance display function via the securities mini app, the securities server 300 extends (refreshes) the validity period by resetting it from the time of the last use of the function. On the other hand, if the user does not use the securities mini app again during the validity period, the securities server 300 determines that the consent-free usage period of the securities mini app has expired. In this case, when the user uses the securities mini app again, the securities server 300 inquires the user again about whether or not to enable the bank account balance display function. After that, if the user again agrees to enable the bank account balance display function, the securities server 300 resets the validity period from the time the user agreed. The validity period is refreshed only when the user uses the securities mini-appli (in other words, when the securities mini-appli accesses the securities server 300 using the user's securities mini-appli ID as a key).

[0038] As described above, in this embodiment, the bank server 200 mainly inquires whether or not the user agrees to enable the bank account balance display function on the bank mini-app, and the securities server 300 mainly inquires whether or not the user agrees to enable the bank account balance display function on the securities mini-app. However, the present invention is not limited to such a configuration, and the payment server 100 mainly inquires whether or not the user agrees to enable the bank account balance display function on the bank mini-app on behalf of the bank server 200 (for example, before the user logs in to the bank server 200). Similarly, the payment server 100 may inquire whether or not the user agrees to enable the bank account balance display function on the securities mini-app on behalf of the securities server 300 (for example, before the user logs in to the securities server 300). In this case, the payment server 100 may store the "user consent" and "validity period" stored in the bank account information 210 in the user information 172 instead of the bank server 200, and may store the "user consent" and "validity period" stored in the securities account information 310 in the user information 172 instead of the securities server 300.

[0039] [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 refers to the user information 172 to acquire the "payment method setting" of the user. For a user 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. The item value of the affiliated store's sales is not used as electronic money itself, for example, and an amount corresponding to the item value of the sales is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0040] The payment processing unit 130 performs electronic payment 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, and the operator of the electronic payment service acts as a creditor and allows electronic payment that is not dependent on the charge balance within the credit card payment limit. In order to receive the credit card payment service, a credit card provided by the operator of the electronic payment service may be required. The amount used in the credit card payment is settled on the payment date of the following month, for example, by debiting from a bank account, for one month. In this case, the payment processing unit 130 performs provisional payment by adding the payment amount to the credit card payment amount and subtracting the same amount from the available credit card payment amount, and when the closing date comes, it performs processing to debit the payment for the current month on the payment date of the following month as described above, or requests the operator of the credit card company to perform the processing. In addition, if the payment amount exceeds the available credit card payment amount at the time of provisional payment, an error notification is returned to the payment application 20.

[0041] [Top page] FIG. 9 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 changeover switch SW for switching between making electronic payment using the charge balance and making electronic payment using credit card payment is displayed next to the code image CI. Note that the "switch" and "button" are GUIs (Graphical User Interfaces) realized in cooperation with a touch panel. For example, a user can switch between making electronic payment using the charge balance and making electronic payment using credit card payment by swiping the changeover switch SW. FIG. 9 shows that "balance payment" is enabled, and that it is possible to switch to credit card payment by swiping the changeover switch SW. The top screen also includes an operation area OA, a transition button TB1, and a transition button TB2. 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 charging the charge balance, a button for displaying points acquired by the user, 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 Figure 7, electronic payment using the charge balance is set, so when transition button TB2 is operated, the available balance for balance payment is displayed.

[0042] [Mini App] At the bottom of the operation area OA, for example, a group of buttons (switches) M1, M2, ... for activating a mini app are further displayed. As described above, 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 a program and technical documentation for app development provided by an administrator of the payment app 20. A mini app is an app that operates, for example, when the payment app 20 is activated. For example, when the payment app 20 is installed, a part or all of the mini app may be 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 the mini app is activated, a service server that provides a service corresponding to the mini app is accessed, and the mini app and the service server work together to provide a service to a user. At this time, the service server may be the payment server 100 itself. As an example, Figure 9 displays a button M1 for launching a banking mini-app that works in cooperation with bank server 200, an example of a service server, to provide banking services to the user, and a button M2 for launching a securities mini-app that works in cooperation with securities server 300, an example of a service server, to provide asset management services to the user. However, buttons for launching various types of mini-apps, such as a reservation app for using amusement facilities such as movie theaters, or a payment app for paying public transportation fares, may be displayed.

[0043] [Charge screen] FIG. 10 is a diagram showing an example of a charge screen of the payment application 20. The charge screen is displayed, for example, when a user presses a charge button on the top screen. The charge screen displays an input area IA for inputting a charge amount and a display area DA for displaying a bank account for transferring the charge amount. When a user inputs a charge amount in the input area IA and presses the charge button TB3, the payment application 20 transmits a charge instruction to the bank server 200, and the bank server 200 transfers an amount equivalent to the charge amount from the bank account displayed in the display area DA to the payment server 100. That is, since the remittance source bank account needs to have an account balance at least equal to or greater than the charge amount input by the user, it is desirable for the user to be able to check the balance of the bank account when inputting the charge amount. For this reason, the bank mini-app displays an icon IC1 (an example of an "operation frame") for displaying the bank account balance in the display area DA, and displays the bank account balance acquired from the bank server 200 in response to a user who satisfies a predetermined condition described later pressing the icon IC1. As a result, the charge screen shown in the left part of Figure 9, which does not display the bank account balance, transitions to a charge screen shown in the right part of Figure 9, which displays the bank account balance, and the user can enter the charge amount while checking the displayed bank account balance.

[0044] Conversely, when the user presses the icon IC2 on the charge screen displaying the bank account balance, the bank mini-app switches from the charge screen displaying the bank account balance to a charge screen that does not display the bank account balance. In this way, the user can switch between displaying and hiding the bank account balance by pressing the icons IC1 and IC2. Note that in this embodiment, as an example, the icons IC1 and IC2 in the shape of human eyes are used to switch between displaying and hiding the bank account balance, but the present invention is not limited to such a configuration, and the bank mini-app may perform any display (text, icon, image, etc.) that can attract the user's attention when the bank account balance is not displayed. Furthermore, in this embodiment, the process mainly executed by the bank mini-app may be executed as a function implemented in the bank mini-app, or may be executed based on an instruction from the payment server 100. For example, the display process executed by the bank mini-app may be executed by the payment server 100 functioning as a "display control unit" to instruct the mode and timing of display by the bank mini-app, so that the bank mini-app executes the display process.

[0045] In this way, when the user presses the charge button on the top screen to transition to the charge screen, the bank mini-app obtains the bank account balance from the bank server 200 in advance, and the user presses the icons IC1 and IC2 to switch between displaying and hiding the obtained bank account balance. However, in the past, there were legal restrictions on obtaining information on the bank account balance directly from the bank and displaying it on an external application program. Furthermore, in the conventional technology, generally, every time an external application program accesses a financial institution to obtain user information, the user is required to log in to the financial institution system or to enter a token (one-time password) issued by the financial institution system that is valid only temporarily, which may be inconvenient for the user. As described below, the present invention improves the authentication / consent flow related to obtaining the bank account balance while satisfying legal restrictions by using a bank mini-app ID commonly held by the payment server 100 and the bank server 200.

[0046] [Banking mini-app authentication / consent flow] FIG. 11 is a diagram showing an example of an authentication / consent flow executed by the bank server 200. The authentication / consent flow shown in FIG. 11 is executed, for example, when a user has not completed registration with the bank mini-app and the user presses the icon IC1 on the charge screen shown in FIG. 10 or presses the mini-app button M1 on the top screen shown in FIG. 9. "When the user has not completed registration with the bank mini-app" can be determined, for example, by the payment server 100 referring to the user information 172, based on whether or not the "bank mini-app registration" of the user is YES. When the user has not completed registration with the bank mini-app, the bank mini-app has not acquired the bank account balance from the bank server 200 in advance when transitioning from the top screen to the charge screen. Therefore, even if the icon IC1 on the charge screen is pressed, the bank mini-app will transition to the authentication / consent flow shown in FIG. 11 without displaying the bank account balance.

[0047] As shown in the left screen of FIG. 11, the bank mini-app first accesses the bank server 200 and displays a login screen for the bank server 200. When the user inputs necessary information (e.g., bank account number and login password) on the login screen for the bank server 200 and presses the login button TB4, the bank server 200 inquires whether the user agrees to enable the bank account balance display function (the right screen of FIG. 11). For example, the bank mini-app inquires whether the user agrees to link the bank's deposit account information and transaction details to the payment server 100. On the other hand, if the user has not opened a bank account, the user, for example, presses a guide display at the bottom of the screen (e.g., "Click here if you have not opened an account") to perform the procedure to open a bank account. After that, if the bank account is opened, the user accesses the login screen again, inputs necessary information, and logs in.

[0048] When the user confirms the consent content and presses the consent button TB5, the bank server 200 sets the user consent corresponding to the bank mini-app ID of the user to YES, and at the same time, sets the validity period from the time when the consent button TB5 was pressed. Next, the bank server 200 transmits the bank account balance corresponding to the bank mini-app ID of the user to the payment server 100, and when the information management unit 140 receives the bank account balance, it notifies the bank mini-app of the received bank account balance. The bank mini-app displays the notified bank account balance on the charge screen. Thereafter, during the validity period, when the payment app 20 transitions to the charge screen, the bank mini-app obtains the bank account balance from the bank server 200 in advance using the bank mini-app ID of the user as a key, and displays the bank account balance in response to the user pressing the icon IC1 without executing the authentication / consent flow again. That is, this allows the account of the electronic payment service and the bank account to be linked in a manner that is highly convenient for the user in order to use the account balance of the bank account for electronic payment.

[0049] In the above description, the bank server 200 transmits the bank account balance corresponding to the user's bank mini-app ID to the payment server 100, and upon receiving the bank account balance, the information management unit 140 notifies the bank mini-app of the received bank account balance. However, the present invention is not limited to such a configuration, and the bank server 200 may directly notify the bank mini-app of the bank account balance without going through the payment server 100. More generally, the bank server 200 may transmit the bank account balance to at least one of the payment server 100 and the bank mini-app.

[0050] [Chain connection to securities server 300] In this way, by linking the bank account balance from bank server 200 to payment app 20 with the user's consent, the convenience of the user in using electronic payment services can be improved. However, since multiple mini apps can run on payment app 20, depending on the mini app's functions, the convenience of the mini app for users can be improved by expanding the link destination of the bank account balance to other mini apps rather than limiting it to payment app 20 as a super app. The present invention realizes such a function by using a securities mini app as an example.

[0051] Fig. 12 is a diagram showing an example of an authentication / consent flow executed by securities server 300. The authentication / consent flow shown in Fig. 12 is executed, for example, when a user has not completed registration with the securities mini app and the user presses mini app button M2 on the top screen shown in Fig. 9. "When a user has not completed registration with the securities mini app" can be determined, for example, by payment server 100 referring to user information 172, based on whether "securities mini app registration" for the user is YES.

[0052] As shown in the left screen of FIG. 12, the securities mini-app first accesses the securities server 300 and displays a login screen for the securities server 300. When the user inputs necessary information (e.g., securities account number and login password) on the login screen for the securities server 300 and presses the login button TB5, the securities server 300 inquires whether the user agrees to enable the display function of the bank account balance (the screen on the right side of FIG. 12). This is the securities server 300 inquiring of the user through the securities mini-app whether the user agrees to enable the display function of the bank account balance. As shown in FIG. 12, the securities server 300 may inquire whether the charge balance of the electronic payment service is to be obtained by linkage in addition to the bank account balance. On the other hand, if the user has not opened a securities account, for example, the user presses a guide display at the bottom of the screen (e.g., "Click here if you have not opened an account") to open a securities account. After that, if a securities account is opened, the user accesses the login screen again, inputs necessary information, and logs in.

[0053] When the user confirms the consent details and presses the consent button TB6, the securities server 300 sets the user consent corresponding to the securities mini-app ID of the user to YES, and at the same time sets a validity period starting from the time the consent button TB6 was pressed. During this validity period, the securities server 300 can obtain the bank account balance from the bank server 200 via the payment server 100 and display it on the securities mini-app without the user having to press the consent button TB6 again.

[0054] More specifically, the securities server 300 transmits a request to obtain the bank account balance including the securities mini-app ID of the user to the payment server 100. When the payment server 100 receives the request to obtain the bank account balance, the determination unit 144 determines whether or not the request satisfies a predetermined condition (chain connection determination process). Here, the predetermined condition is, for example, that the user has agreed to enable the bank account balance display function in both the bank mini-app and the securities mini-app (has agreed to the linking of the account balances of the bank accounts). The determination unit 144 can determine whether or not the user has agreed in both the bank mini-app and the securities mini-app by, for example, referring to the chain connection management table 178 described later.

[0055] If the determination unit 144 determines that the acquisition request satisfies the predetermined condition, the linking unit 146 acquires the bank account balance from the bank server 200 using the bank mini-app ID of the user as a key. After acquiring the bank account balance from the bank server 200, the linking unit 146 then links the acquired bank account balance to the securities server 300 using the securities mini-app ID as a key. The securities server 300 displays the linked bank account balance on the screen of the securities mini-app. As described above, according to the present embodiment, on the premise that the user has agreed to enable the bank account balance display function on both the bank mini-app and the securities mini-app, the bank server 200 links the bank account balance to the securities server 300 via the payment server 100, and the securities server 300 displays the bank account balance on the securities mini-app. This allows sensitive information such as the account balance of a bank account to be securely and smoothly linked between multiple services.

[0056] FIG. 13 is a diagram showing an example of the contents of the chain connection management table 178. The chain connection management table 178 associates, for example, an account ID, a user consent (bank mini app), a validity period (bank mini app), a user consent (securities mini app), a validity period (securities mini app), and the presence or absence of a chain connection. The user consent (bank mini app) and the validity period (bank mini app) are the same information as the "user consent" and the "validity period" stored in the bank account information 210 shown in FIG. 7. That is, when the user completes the authentication / consent flow shown in FIG. 12, the bank server 200 sets the "user consent" and the "validity period" in the bank account information 210, while notifying the same information to the payment server 100, and the information management unit 140 sets the notified information to the user consent (bank mini app) and the validity period (bank mini app). Similarly, the user consent (securities mini-app) and validity period (securities mini-app) are the same information as the "user consent" and "validity period" stored in the securities account information 310 shown in Fig. 8. That is, when the user completes the authentication / consent flow shown in Fig. 13, the securities server 300 sets the "user consent" and "validity period" in the securities account information 310, while notifying the same information to the payment server 100, and the information management unit 140 sets the notified information as the user consent (securities mini-app) and validity period (securities mini-app).

[0057] If both the user consent (banking mini app) and the user consent (securities mini app) are set to "YES" and the current time is within the validity period (banking mini app) and validity period (securities mini app), the information management unit 140 sets "presence of chain connection" to "yes". When the determination unit 144 subsequently receives a request to obtain the bank account balance from the securities server 300 (or the securities mini app), it refers to the chain connection management table 178, and if "presence of chain connection" is set to "yes", it allows the bank account balance of the user to be linked to the securities server 300 (or the securities mini app). The linking unit 146 then links the bank account balance to the securities server 300.

[0058] Note that bank account information 210 shown in Fig. 7, securities account information 310 shown in Fig. 8, and linked connection management table 178 shown in Fig. 13 each include a validity period during which linking of bank account balances is valid without the need for re-consent by the user. However, the present invention is not limited to such a configuration, and a validity period does not need to be set. In that case, once the user has given their consent, bank account balances will be linked permanently.

[0059] [View bank account balance] Fig. 14 is a diagram showing an example of a securities mini-app screen that displays the bank account balance acquired by the securities server 300 from the bank server 200. The screen shown in Fig. 14 is displayed when a user operates the securities mini-app after, for example, completing the authentication / consent flows shown in Figs. 11 and 12. Fig. 14 shows, as an example, a screen on which a user purchases stocks using an asset management service on the securities mini-app. As shown in Fig. 14, the stock purchase screen includes items for inputting, for example, the name of the stock, the account type, the purchase amount (or a combination of the stock price and the purchase quantity), and the payment method.

[0060] The payment method includes, for example, a radio button R1 for selecting purchase from charge balance and a radio button R2 for selecting purchase from bank balance. This is because the securities mini app has received linkage of charge balance and bank account balance from the payment server 100 as a result of the user completing the authentication / consent flow shown in FIG. 12. When the user selects charge balance to purchase stocks, the securities mini app realizes the user's purchase of stocks by deducting the purchase amount of the stocks from the charge balance of the user's electronic payment service. More specifically, the securities mini app notifies the payment server 100 that the purchase amount of the stocks will be deducted from the charge balance of the user's electronic payment service, and the payment server 100 deducts the purchase amount from the charge balance, and at the same time, the securities server 300 stores the user's purchase information of the stocks (such as the name of the stocks purchased, the account type, and the purchase amount) in the "stock information held" of the securities account information 310. On the other hand, when the user selects bank account balance to purchase stocks, the securities server 300 realizes the user's purchase of stocks by deducting the purchase amount of the stocks from the user's bank account balance. More specifically, the securities mini-app notifies bank server 200 via payment server 100 that the purchase amount of stocks will be deducted from the user's bank account balance, and while bank server 200 deducts the purchase amount from the bank account balance, securities server 300 stores the user's stock purchase information (such as the name of the purchased stock, account type, purchase amount, etc.) in the ``held stock information'' of securities account information 310.

[0061] At this time, the communication between the securities server 300 and the payment server 100 is performed via the securities mini-app ID, whereas the communication between the payment server 100 and the bank server 200 is performed via the bank mini-app ID. In other words, in both cases, when the securities server 300 obtains the bank account balance from the bank server 200 via the payment server 100, and when the user purchases a financial product using the bank account balance, sensitive information such as the user's bank account number or securities account number is not communicated, and communication is performed by chain connection using identification information such as the bank mini-app ID or securities mini-app ID. In other words, this allows sensitive information such as the account balance of a bank account to be linked securely and smoothly between multiple services.

[0062] [Processing flow] Next, a process flow executed by the user terminal device 10, the payment server 100, the bank server 200, and the securities server 300 will be described with reference to Fig. 15. Fig. 15 is a sequence diagram showing an example of a process flow executed by the user terminal device 10, the payment server 100, the bank server 200, and the securities server 300.

[0063] First, the user accesses the bank server 200 via the bank mini app on the user terminal device 10, and executes the authentication / consent flow shown in Fig. 11 on the bank mini app (S10). When the authentication / consent flow is completed, the bank server 200 notifies the payment server 100 of the user's consent regarding the linking of bank account balances (S12). Next, the user accesses the securities server 300 via the securities mini app on the user terminal device 10, and executes the authentication / consent flow shown in Fig. 12 on the securities mini app (S14). When the authentication / consent flow is completed, the securities server 300 notifies the payment server 100 of the user's consent regarding the linking of bank account balances (S16).

[0064] Next, the user uses the securities mini-app on the user terminal device 10 (for example, opens a screen for purchasing a financial product), and the user terminal device 10 sends a request to obtain the bank account balance to the securities server 300 (S18). Next, the securities server 300 sends a request to obtain the bank account balance, including the securities mini-app ID of the user, to the payment server 100 (S20). Next, the determination unit 144 of the payment server 100 performs a chain connection determination process, i.e., determines whether the user has agreed to linking the account balance of their bank account on both the bank mini-app and the securities mini-app (S22).

[0065] If it is determined that the user has agreed to linking the account balance of the bank account in both the bank mini-app and the securities mini-app, the linking unit 146 transmits a request to the bank server 200 to obtain the bank account balance, including the bank mini-app ID of the user (S24). Next, the bank server 200 identifies the user associated with the received bank mini-app ID, and transmits the bank account balance of the user to the bank mini-app ID and transmits the bank account balance to the payment server 100 (S26). Next, the linking unit 146 transmits the bank account balance of the user to the securities mini-app ID and transmits the securities account balance to the securities server 300 (S28). Next, the securities server 300 transmits the received bank account balance to the user terminal device 10 (S30). Next, the user terminal device 10 displays the bank account balance on the securities mini-app (S32). This ends the processing of this sequence diagram.

[0066] [Transition to bank mini app] The sequence diagram shown in FIG. 15 is based on the premise that the user has completed the authentication / consent flow on the bank mini app and the authentication / consent flow on the securities mini app in that order. However, some users may complete only the authentication / consent flow on the securities mini app without completing the authentication / consent flow on the bank mini app and start using the securities mini app. In that case, the chain connection determination process at S22 in the sequence diagram of FIG. 15 will fail. In that case, the linking unit 146 may transition the mini app executed on the user terminal device 10 from the securities mini app to the bank mini app and execute the authentication / consent flow on the bank mini app shown in FIG. 11. As another aspect, when the securities mini app fails to acquire the bank account balance, the linking unit 146 may display an icon indicating that the bank account balance is unknown, and transition the securities mini app to the bank mini app according to the user's selection and execute the authentication / consent flow on the bank mini app.

[0067] FIG. 15 is a diagram showing an example of a transition process from the securities mini-app to the bank mini-app. FIG. 15 shows, as an example, a scene in which a user completes only the authentication / consent flow on the securities mini-app, starts using the securities mini-app, and purchases a financial product. In this case, the securities mini-app fails to obtain the bank account balance, and displays icon IC3 indicating that the amount of the bank account balance is unknown. If the user wishes to display the bank balance, the user presses IC3, and the user terminal device 10 transitions the securities mini-app to the bank mini-app and displays a screen of the authentication / consent flow on the bank mini-app shown in FIG. 11. A user who wishes to display and use the bank account balance can complete the authentication / consent flow on the bank mini-app and return to the purchase screen again to check the bank account balance and use it to purchase a financial product.

[0068] In the above embodiment, it is assumed that the banking mini-app and the securities mini-app are mini-apps with the payment app 20 as a super app. However, the present invention is not limited to such a configuration, and at least one of the banking mini-app and the securities mini-app may be a native app. In that case, for example, when a user presses button M1 or M2 on the top screen of Fig. 9, the payment app 20 will launch the banking app or the securities app as a native app (if the banking app or the securities app has not been installed on the user terminal device 10, the user will be transitioned to a download page for the banking app or the securities app).

[0069] Furthermore, in the above embodiment, for convenience of explanation, a distinction is made between the processing of the bank mini-app and the processing of the bank server 200, and a distinction is made between the processing of the securities mini-app and the processing of the securities server 300. However, the processing mainly based on the bank mini-app (securities mini-app) can also be implemented as processing mainly based on the bank server 200 (securities server 300) except for the display processing on the user terminal device 10. Conversely, the processing mainly based on the bank server 200 (securities server 300) can also be implemented as processing mainly based on the bank mini-app (securities mini-app) except for the storage and update processing of the bank account information 210 (securities account information 310).

[0070] Furthermore, in the above embodiment, a case has been described in which the payment app 20 is used as a platform, the bank mini app and the securities mini app run, and the bank account balance managed by the bank server 200 is linked to the securities server 300 using first identification information (bank mini app ID) different from the bank account number and second identification information (securities mini app ID) different from the securities account number. However, the present invention is not limited to such a configuration, and the apps and the linked information may be different. For example, a SNS app may be used as a platform, the first game mini app and the second game mini app run, and the game points managed by the first game server are linked to the second game server using first identification information different from the first game user identifier and second identification information different from the second game user identifier.

[0071] According to the embodiment described above, it is determined whether a request to obtain the account balance of a bank account linked to an electronic payment service, received from the securities mini-app, satisfies a predetermined condition, and if it is determined that the predetermined condition is satisfied, the account balance of the bank account is received from the bank server 200 based on a bank mini-app ID commonly held by the payment server 100 and the bank server 200, and linked to the securities mini-app. This allows sensitive information such as the account balance of a bank account to be securely and smoothly linked between multiple services.

[0072] 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]

[0073] 10 User terminal device 20. Payment App 100 Payment Server 120 Payment Contents Provider 130 Payment processing unit 140 Information Management Department 142 Generation part 144 Judgment section 146 Collaboration Department 200 Bank Server 300 Securities Server

Claims

1. An information processing device that processes information via a service that operates in cooperation with a first application and a second application that operate on a user's terminal device, a determination unit that determines whether a request to obtain the account balance of a bank account linked to the service received from the second application satisfies a predetermined condition; a linking unit that, when it is determined that the predetermined condition is satisfied, receives an account balance of the bank account from the account management server based on first identification information of the user that is held in common by the device itself and an account management server that manages the bank account, and links to the second application; the service is an electronic payment service; the second application is an application program that provides an asset management service using at least one of a charge balance of the electronic payment service and the account balance in conjunction with an asset management server; when it is determined that the predetermined condition is satisfied, the linking unit links the account balance of the bank account to the second app based on second identification information of the user, the second identification information being different from the first identification information and commonly held by the asset management server and the asset management device itself; the first identification information is information different from a bank account number used by the account management server to identify the bank account of the user, The second identification information is information different from a securities account number used by the asset management server to identify the securities account of the user. Information processing device.

2. a generation unit configured to generate the first identification information when the user registers in the first application and to generate the second identification information when the user registers in the second application, The information processing device according to claim 1 .

3. the first application is an application program for utilizing a function of the account management server, The predetermined condition includes that the user has agreed to the linking of the account balances of the bank accounts on both the first app and the second app. The information processing device according to claim 1 .

4. When it is determined that the linking of the account balances of the bank accounts has not been agreed to on the first application, the linking unit transitions the second application to the first application and causes the first application to execute a process for agreeing to the linking of the account balances of the bank accounts. The information processing device according to claim 3 .

5. An information processing device, An information processing method for processing information via a service that operates in cooperation with a first application and a second application that operate on a user's terminal device, comprising: determining whether a request for obtaining an account balance of a bank account linked to the service received from the second application satisfies a predetermined condition; if it is determined that the predetermined condition is satisfied, receiving an account balance of the bank account from the account management server based on first identification information of the user that is held in common by the device itself and an account management server that manages the bank account, and linking the account balance to the second application; the service is an electronic payment service; the second application is an application program that provides an asset management service using at least one of a charge balance of the electronic payment service and the account balance in conjunction with an asset management server; If it is determined that the predetermined condition is satisfied, linking the account balance of the bank account to the second application based on second identification information of the user, the second identification information being different from the first identification information and commonly held by the asset management server and the device itself; the first identification information is information different from a bank account number used by the account management server to identify the bank account of the user, The second identification information is information different from a securities account number used by the asset management server to identify the securities account of the user. Information processing methods.

6. In the information processing device, A program for processing information via a service operating in cooperation with a first application and a second application that operate on a user's terminal device, determining whether a request for obtaining an account balance of a bank account linked to the service received from the second application satisfies a predetermined condition; if it is determined that the predetermined condition is satisfied, receiving an account balance of the bank account from the account management server based on first identification information of the user that is held in common by the device itself and an account management server that manages the bank account, and linking the account balance to the second application; the service is an electronic payment service; the second application is an application program that provides an asset management service using at least one of a charge balance of the electronic payment service and the account balance in conjunction with an asset management server; If it is determined that the predetermined condition is satisfied, linking the account balance of the bank account to the second application based on second identification information of the user, the second identification information being different from the first identification information and commonly held by the asset management server and the device itself; the first identification information is information different from a bank account number used by the account management server to identify the bank account of the user, The second identification information is information different from a securities account number used by the asset management server to identify the securities account of the user. program.

7. An information processing device that processes information via a service that operates in cooperation with a first application and a second application that operate on a user's terminal device, a determination unit that determines whether a request to obtain the account balance of a bank account linked to the service received from the second application satisfies a predetermined condition; a linking unit that, when it is determined that the predetermined condition is satisfied, receives an account balance of the bank account from the account management server based on first identification information of the user that is held in common by the device itself and an account management server that manages the bank account, and links to the second application; the service is an electronic payment service; the second application is an application program that provides an asset management service using at least one of a charge balance of the electronic payment service and the account balance in conjunction with an asset management server; when it is determined that the predetermined condition is satisfied, the linking unit links the account balance of the bank account to the second app based on second identification information of the user, the second identification information being different from the first identification information and commonly held by the asset management server and the asset management device itself; the second application displays the charge balance and the account balance in a selectable manner so that the user can purchase financial products on the asset management service; Information processing device.

8. An information processing device, An information processing method for processing information via a service that operates in cooperation with a first application and a second application that operate on a user's terminal device, comprising: determining whether a request for obtaining an account balance of a bank account linked to the service received from the second application satisfies a predetermined condition; if it is determined that the predetermined condition is satisfied, receiving an account balance of the bank account from the account management server based on first identification information of the user that is held in common by the device itself and an account management server that manages the bank account, and linking the account balance to the second application; the service is an electronic payment service; the second application is an application program that provides an asset management service using at least one of a charge balance of the electronic payment service and the account balance in conjunction with an asset management server; If it is determined that the predetermined condition is satisfied, linking the account balance of the bank account to the second application based on second identification information of the user, the second identification information being different from the first identification information and commonly held by the asset management server and the device itself; the first identification information is information different from a bank account number used by the account management server to identify the bank account of the user, the second application displays the charge balance and the account balance in a selectable manner so that the user can purchase financial products on the asset management service; Information processing methods.

9. In the information processing device, A program for processing information via a service operating in cooperation with a first application and a second application that operate on a user's terminal device, determining whether a request for obtaining an account balance of a bank account linked to the service received from the second application satisfies a predetermined condition; if it is determined that the predetermined condition is satisfied, receiving an account balance of the bank account from the account management server based on first identification information of the user that is held in common by the device itself and an account management server that manages the bank account, and linking the account balance to the second application; the service is an electronic payment service; the second application is an application program that provides an asset management service using at least one of a charge balance of the electronic payment service and the account balance in conjunction with an asset management server; If it is determined that the predetermined condition is satisfied, linking the account balance of the bank account to the second application based on second identification information of the user, the second identification information being different from the first identification information and commonly held by the asset management server and the device itself; the second application displays the charge balance and the account balance in a selectable manner so that the user can purchase financial products on the asset management service; program.

Images