Information processing device, information processing method, and program

Abstract

To securely and smoothly link sensitive information, such as bank account balances, across multiple services. [Solution] An information processing device that processes information via a service that operates in cooperation with a first application and a second application running on a user's terminal device, comprising: a determination unit that determines whether a request received from the second application to obtain the account balance of a bank account linked to the service satisfies predetermined conditions; and a linkage unit that, if it is determined that the predetermined conditions are met, receives the account balance of the bank account from the account management server based on the first identification information of the user commonly held by the device and the account management server that manages the bank account, and links with the second application.

Description

Technical Field

[0004] , , , , ,

[0005] , , ,

[0003] , , ,

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

Background Art

[0002] Conventionally, a technique for linking an account of an electronic payment service with a bank account has been known. For example, in Patent Document 1, when an acquisition request for the account balance of a bank account linked to an electronic payment service received from a payment application satisfies a predetermined condition, based on the identification information of the user that is commonly held by a payment server and an account management server that manages the bank account, a technique is disclosed in which the account balance of the bank account is received from the account management server and stored.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The technique described in Patent Document 1 securely and smoothly links the account balance of a bank account to an electronic payment service using identification information different from the bank account number. However, in the conventional technique, for example, when a specific service such as an electronic payment service functions as a platform and operates a plurality of services, there are cases where sensitive information such as the account balance of a bank account is not securely and smoothly linked between these plurality of services.

[0005] The present invention has been made in consideration of such circumstances, and one of its objects is to provide an information processing apparatus, an information processing method, and a program that can securely and smoothly link sensitive information such as the account balance of a bank account between a plurality of services.

Means for Solving the Problems

[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 application and a second application 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 application, satisfies predetermined conditions; and a linkage unit that, if it is determined that the predetermined conditions are met, receives the account balance of the bank account from the account management server based on first identification information of the user, which is commonly held by the device and the account management server that manages the bank account, and links with the second application. [Effects 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 link sensitive information, such as bank account balances, between multiple services. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram shows an example of a configuration for implementing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payments. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payments. [Figure 4] This is a configuration diagram of the payment server 100 according to the first embodiment. [Figure 5] This figure shows an example of the contents of user information 172. [Figure 6] This figure shows an example of the contents of merchant / store information 176. [Figure 7] This figure shows an example of the contents of bank account information 210 stored by the bank server 200. [Figure 8] This figure shows an example of the contents of securities account information 310 stored by the securities server 300. [Figure 9] This figure shows an example of the top screen of a payment app 20. [Figure 10] This figure shows an example of the top-up screen for payment app 20. [Figure 11] This figure shows an example of an authentication / consent flow performed by the bank server 200. [Figure 12] This figure shows an example of an authentication / consent flow performed by the securities server 300. [Figure 13] This figure shows an example of the contents of the chain connection management table 178. [Figure 14] This figure shows an example of a securities mini-app screen that displays the bank account balance obtained from the bank server 200 by the securities server 300. [Figure 15] This sequence diagram shows an example of the processing flow performed by the user terminal device 10, the payment server 100, the bank server 200, and the securities server 300. [Figure 16] This diagram shows an example of the transition process from a securities mini-app to a banking mini-app. [Modes for carrying out the invention]

[0009] The following describes embodiments of the information processing apparatus, information processing method, and program of the present invention with reference to the drawings. Various devices used to provide services to users or perform internal analysis, such as the "server," "management device," and "information providing device" described below, may be implemented by a distributed group of devices, and the operators of each device may be different. Furthermore, the owner of the hardware of the devices (the provider of the cloud server) and the operator that actually operates them may also be different. The application program and the payment server work together to provide an electronic payment service. In the following description, the application program will be referred to as the payment app. The electronic payment service is a service that supports payment for 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 e-commerce. A virtual store may include one provided by an entity different from the operator of the electronic payment service. In that case, when settling a purchase at a virtual store, the user may be directed to the interface screen of the electronic payment service. In the electronic payment service, stores are treated as belonging to, for example, affiliated merchants (brands), and processing such as payment when a purchase is made at a store is mainly carried out between the user and the affiliated merchant. Alternatively, payment and other processing may be conducted 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 with a payment server 100 at its center. 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, and provider equipment.

[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, the configurations for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, the payment application 20 is executed by a processor such as a CPU, and it operates to provide an electronic payment service to the user in cooperation with the payment server 100. The payment application 20 is installed in the user terminal device 10 from, for example, an application store, and controls a camera, a communication device, a 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. Note that the store code image 60 may be displayed by a display placed in the store (which may be a display of a terminal device such as a smartphone).

[0013] The second store terminal device 70 is used by the operator of the franchise store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. In the second store terminal device 70, an interface 72 for franchise stores operates. The interface 72 for franchise stores may be an application for franchise stores or a browser. The interface 72 for franchise stores accepts settings of coupons, etc. by the operator of the franchise store and transmits them to the settlement server 100. The second store terminal device 70 which is a smartphone has functions such as displaying a code image corresponding to the store code image or reading the code image displayed by the user terminal device 10 by executing an application for franchise stores.

[0014] The settlement server 100 realizes electronic settlement based on the settlement 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 a franchise store server. In that case, the settlement information is transmitted from the POS device to the settlement server 100 via the franchise store server. In the following description, without particularly distinguishing this, it is assumed that the settlement information is transmitted from the first store terminal device 50.

[0015] The bank server 200 transfers money from the bank account of the user to the settlement server 100 in response to the instruction of the user. The settlement server 100 charges the remaining recharge amount of the user, which will be described later, by the amount of the transferred money received. In addition, the bank server 200 transmits information indicating the account balance of the bank account of the user (hereinafter referred to as the bank account balance) to the settlement server 100 in response to an instruction from the user or the settlement server 100. The details of this process will be described later. The bank server 200 stores information indicating the bank account balance of the user in the bank account information 210.

[0016] The securities server 300 provides asset management services using the user's charge balance or bank account balance, in response to the user's instructions. 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, but the 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] Figures 2 and 3 are sequence diagrams illustrating the general flow of electronic payments. There may be two patterns for electronic payments: Pattern 1 and Pattern 2.

[0018] In the case of Pattern 1 shown in Figure 2 (hereinafter referred to as User Scan), 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 contains information about the store URL (Uniform Resource Locator). This store URL is an electronic payment service domain to which information that can identify the store has been added, and is associated with the merchant ID and store ID, etc., at the payment server 100 (described later). The payment application 20 sends the 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 later) from the merchant ID and store ID corresponding to the store URL, obtains the merchant name and store name information (S3), and sends it to the payment application 20 (S4). The user enters the payment amount into the user terminal device 10 on the screen where the merchant name and store name are displayed (S5). The user terminal device 10 then generates second payment information, including at least the payment amount, and sends 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 sends a payment completion notification (information for displaying the payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). If the store code image 60 is displayed on a display placed in the store, the store code image 60 may include payment amount information as well as the store URL. In this case, the procedure for the user to enter the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Merchant name and store name information may be included and displayed on the payment completion screen.

[0019] In the case of Pattern 2 shown in Figure 3 (hereinafter referred to as Store Scan), when the payment app 20 is launched, when a payment operation is performed in the payment app 20, when it is time for an automatic update (for example, every minute), and at other times, the payment app 20 sends a request to the payment server 100 to issue a one-time code (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 that was generated based on the one-time code (S14). The user holds the display surface of the user terminal device 10 over the first store terminal device 50 (presents it), and the first store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). Then, the first store terminal device 50 generates payment information including the one-time code, payment amount, merchant ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is obtained in advance by barcode scanning or manual input. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs the electronic payment (S17). The payment server 100 then sends a payment completion notification to the payment app 20 (S18), and the payment app 20 displays a payment completion screen (S19).

[0020] Furthermore, electronic payment may be performed using only one of the above patterns. Also, the "account ID" explained in Figure 2 may be other information that can be used as user identification information (for example, a phone number). In addition, the issuance of a one-time code may be omitted during store scanning, and the payment app 20 may display a code image generated based on the user's account ID. In that case, the payment server 100 will identify the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0021] [Payment Server] Figure 4 is a configuration diagram of a payment server 100 according to the first embodiment. The payment server 100 includes, for example, a communication unit 110, a payment content provision unit 120, a payment processing unit 130, an information management unit 140, and a storage unit 170. Components other than the communication unit 110 and the storage unit 170 are realized, for example, by 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), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or GPU (Graphics Processing Unit), or by the cooperation 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 equipped with a non-transient storage medium), or it may be stored in a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed in the storage device when the storage medium is mounted on a drive device. The information management unit 140 further comprises a generation unit 142, a determination unit 144, and a linkage unit 146, the details of which will be described later. The information management unit 140 is an example of an "information processing device" as defined in the claims.

[0022] The storage unit 170 can be an HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 170 may also be a NAS (Network Attached Storage) device that the payment server 100 can access via the network. The storage unit 170 stores information such as user information 172, payment content information 174, merchant / store information 176, and a chain connection management table 178.

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

[0024] The payment content provision unit 120, for example, has the functionality 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 provision unit 120 reads the necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 receives various inputs from the user while the content is being played by the payment application 20 and transmits the aforementioned payment information and other data to the payment server 100.

[0025] The payment processing unit 130 performs payment processing based on 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] Figure 5 shows an example of the contents of User Information 172. User Information 172 is an example of user registration information. User Information 172 is associated with information such as user URL, account ID, telephone number, password, email address, user ID, name, address, date of birth, registration date, charge balance, credit payment settings, credit payment limit, credit payment amount, available credit payment amount, payment method settings, credit card number, bank account, bank mini-app registration, bank mini-app ID, securities mini-app registration, securities mini-app ID, charge history information, and payment history information. The user URL is used for transfer processing between users. When registering for a new electronic payment service, registration of a telephone number and password is mandatory. The account ID is issued to the user by the payment server 100, and the user ID is an ID that the user can set at will (or does not have to set). Similarly, the email address and name, address, and date of birth are also information that the user can set at will (or does not have to set). The registration date is the date the user registered for the electronic payment service (the date the account was created). Hereafter, the user 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 set by the user by sending money to their account in advance. Methods of sending money include sending from an ATM (Automatic Teller Machine) of a designated provider (bank) and sending from a registered bank account. The credit payment setting indicates whether or not the user has completed the settings to enable electronic payments by credit card, and is set to either "Completed" or "Not Completed". The credit payment limit is the monthly limit for credit payments, the credit payment amount is the amount already used for credit payments in the current month, and the available credit payment amount is the amount available for credit payments in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the diagram shows only one credit payment limit, in reality there are also daily limits, and the lower of these may be set as the credit payment limit. Further details on credit payments will be described later. The payment method setting indicates whether the user will use electronic payment with the charge balance or payment by credit card at that time. The bank account and credit card number information, respectively, refers to the bank account or credit card number (account number, card number) to which funds can be deposited into the electronic payment service. The charge history information is a record of when the user has previously sent money to the electronic payment service to increase the charge balance. The payment history information shows 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] Bank Mini-App Registration is information indicating whether or not a user has completed registration for the application program (hereinafter referred to as "Bank Mini-App") provided by the bank server 200 on the payment app 20 (for example, whether or not they have logged in to the bank server 200 via the Bank Mini-App). The Bank Mini-App is an application program developed and provided using the payment app 20 as a platform, and users do not need to download the app again. Registration for using the Bank Mini-App is completed simply by entering the necessary information on the payment app 20. Here, the necessary information includes, for example, the user's bank account number and password, and if the user has not yet opened an account with the bank, it also includes information such as name, date of birth, email address, telephone number, and identification document (photo). Once registration is complete, the information management unit 140 stores flag information (for example, "YES") indicating that the user has registered for the Bank Mini-App in the "Bank Mini-App Registration" field of the user information 172. Once registration is complete, the user gives the consent described below on the Bank Mini-App. This allows users to access various functions provided by the bank server 200 (for example, displaying bank account balances, making transfers, taking out loans, foreign currency deposits, time deposits, and purchasing investment trusts) via a bank mini-app running on the payment app 20. When a user accesses these 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 providing the functions of the bank mini-app). Registration for the bank mini-app is performed, as described later, for example, when a user first launches the bank mini-app on the top screen of the payment app 20, or when they first launch the bank mini-app to check their bank account balance on the charge balance screen. The bank mini-app is an example of the "first app" in the claims.

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

[0030] Securities mini-app registration is information indicating whether or not a user has completed registration for the securities mini-app (for example, whether or not they have logged into the securities server 300 via the securities mini-app) when using the application program (hereinafter referred to as the "securities mini-app") provided by the securities server 300 on the settlement application 20. Similar to the bank mini-app, the securities mini-app is an application program developed and provided using the settlement application 20 as a platform, and users do not need to download the app again. Registration for using the securities mini-app is completed simply by entering the necessary information on the settlement application 20. Here, the necessary information includes, for example, the user's securities account number and password, and if the user has not yet opened an account with the securities company, it also includes information such as name, date of birth, email address, telephone number, and identification document (photo). Once registration is complete, the information management unit 140 stores flag information (for example, "YES") indicating that the user has registered for the securities mini-app in the "Securities Mini-App Registration" field of the user information 172. Once registration is complete, the user gives the consent described later on the securities mini-app. This allows users to access various functions provided by the securities server 300 (for example, asset management in stocks and ETFs (Exchange Traded Funds) using their charge balance or bank account balance, and viewing market information for stocks and ETFs) via a securities mini-app running on the payment app 20. When a user accesses these 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 providing the functions of the securities mini-app). Registration for the securities mini-app is performed, for example, when a user first launches the securities mini-app on the top screen of the payment app 20. The securities mini-app is an example of the "second app" in the claims.

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

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

[0033] The Information Management Unit 140 manages user information 172 and affiliated store / store information 176 based on information obtained from the user terminal device 10 and the second store terminal device 70. The Information Management Unit 140 performs operations such as adding, editing, and deleting new records for user information 172 and affiliated store / store information 176.

[0034] [Bank Server] Figure 7 shows an example of the contents of the bank account information 210 stored by the bank server 200. The bank account information 210 is a collection of information such as the bank account number, bank account balance, bank mini-app ID, user consent, and validity period. The bank account number is user identification information assigned by the bank when the user opens an account with the bank that operates the bank server 200. The bank account balance is information indicating the balance the user has deposited with the bank. The bank mini-app ID is the bank mini-app ID notified by the settlement server 100. User consent is information indicating whether or not the user has consented to enabling the bank account balance display function (in other words, information indicating whether or not the user has consented to the sharing of bank account balance information). When the user completes logging into the bank server 200, the bank server 200 asks the user whether or not they consent to enabling the bank account balance display function, and if the user consents to enabling the bank account balance display function, "YES" is stored in the user consent field of the bank account information 210.

[0035] The validity period is the period during which the bank mini-app can be used without further consent, 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 further consent. The validity period is set, for example, to expire 90 days after confirmation of user consent. During this period, each 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 the function was last used. 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 period during which the bank mini-app can be used without further consent has expired. In this case, when the user uses the bank mini-app again, the bank server 200 will again ask the user whether or not to enable the bank account balance display function. If the user then agrees again to enable the bank account balance display function, the bank server 200 resets the validity period from the time the user agreed. Please note that the validity period will only be refreshed 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). For example, if you send money from the bank server 200 to top up your balance, the refresh will not be performed.

[0036] [Securities Server] Figure 8 shows an example of the contents of the securities account information 310 stored by the securities server 300. The securities account information 310 is a collection of information such as the securities account number, held securities information, securities mini-app ID, user consent, and validity period. The securities account number is user identification information assigned by the securities company when the user opens an account with the securities company that operates the securities server 300. Held securities information is information that shows the securities that the user has purchased and holds from the securities company and their details (quantity held, acquisition price, etc.). The securities mini-app ID is the securities mini-app ID notified by the settlement server 100. User consent is information indicating whether or not the user has consented to enabling the display function of the bank account balance managed by the bank server 200 (in other words, information indicating whether or not the user has consented to the sharing of bank account balance information). Once the user has completed logging in to the securities server 300, the securities server 300 asks the user whether they agree to enable the bank account balance display function. If the user agrees to enable the bank account balance display function, the securities server 300 stores "YES" in the user consent field of the securities account information 310.

[0037] The validity period is the period during which the securities mini-app can be used without further consent. In other words, during the set validity period, the user can use the bank account balance display function without further consent. The validity period is set, for example, to expire 90 days after confirmation of user consent. During this period, each 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 the function was last used. 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 period during which the securities mini-app can be used without further consent has expired. In this case, when the user uses the securities mini-app again, the securities server 300 will again ask the user whether or not to enable the bank account balance display function. If the user then agrees again 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 will only be refreshed when the user uses the securities mini-app (in other words, when the securities mini-app accesses the securities server 300 using the user's securities mini-app ID as the key).

[0038] As described above, in this embodiment, the bank server 200 is the primary inquirer to ask whether the user agrees to enable the bank account balance display function on the bank mini-app, and the securities server 300 is the primary inquirer to ask whether 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 settlement server 100 may be the primary inquirer to ask whether the user agrees to enable the bank account balance display function on the bank mini-app (for example, before the user logs in to the bank server 200) on behalf of the bank server 200. Similarly, the settlement server 100 may ask whether the user agrees to enable the bank account balance display function on the securities mini-app (for example, before the user logs in to the securities server 300) on behalf of the securities server 300. In that case, the settlement 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, or it 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 the payment processing unit 130 obtains payment information from the user terminal device 10 or the first store terminal device 50, it refers to the user information 172 to obtain the user's "payment method setting". 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, which is managed in association with the user ID, and increasing the value of the merchant's sales proceeds item. For example, the value of the merchant's sales proceeds item is not used as electronic money itself, but rather the amount corresponding to the value of the sales proceeds item is transferred to the bank account in a cycle according to the agreement between the merchant and the electronic payment service.

[0040] The payment processing unit 130 performs electronic payment as follows for users whose "settings information" is set to "credit payment". Credit payment is a payment method in cooperation with a credit card company, which is a separate entity from the electronic payment service operator. The electronic payment service operator acts as the donor and allows electronic payment within the credit limit, without relying on the charge balance. In order to use the credit payment service, users may be required to obtain a credit card provided by the electronic payment service operator. The amount used by credit payment is settled in a lump sum for the month on the payment date of the following month, for example, by withdrawal from a bank account. In this case, the payment processing unit 130 performs a provisional settlement by adding the settlement amount to the amount used by credit payment and subtracting the same amount from the available credit payment limit. When the closing date arrives, it processes the payment for the current month to be withdrawn on the payment date of the following month as described above, or requests the credit card company operator to perform the said process. If the settlement amount exceeds the available credit payment limit at the time of provisional settlement, an error notification is sent back to the payment app 20.

[0041] [Top screen] Figure 9 shows an example of the top screen of the payment app 20. The top screen displays a code image CI. The code image CI includes, for example, barcodes and QR codes. Next to the code image CI, there is a toggle switch SW for switching between electronic payment using the charged balance and electronic payment using credit. Note that "switch" and "button" are GUIs (Graphical User Interfaces) implemented in cooperation with the touch panel. The user can switch between electronic payment using the charged balance and electronic payment using credit by, for example, swiping the toggle switch SW. Figure 9 shows that "balance payment" is enabled, and it is possible to switch to credit payment by swiping the toggle switch SW. The top screen also includes an operation area OA, transition buttons TB1 and TB2. The operation area OA is equipped with buttons that instruct the main operations in electronic payment, such as a button to instruct scanning (starting user scanning), a button to charge the charged balance, a button to display points earned by the user, and a button to display the history of electronic payments performed by the user. When the transition button TB1 is pressed, the user transitions to a payment screen displaying the code image used for electronic payment and the available balance. When the transition button TB2 is pressed, the user transitions to a screen displaying the available balance for either balance payment or credit payment. In Figure 7, since electronic payment using the charged balance is set, when the transition button TB2 is pressed, the available balance for balance payment is displayed.

[0042] [Mini App] At the bottom of the operating area OA, for example, a group of buttons (switches) M1, M2, ... for launching mini-applications are displayed. As mentioned above, a mini-application is an application that operates using the payment application 20 as a platform and provides some kind of service. The service provider develops the mini-application by referring to the SDK (Software Development Kit), which consists of application development programs and technical documents provided by the administrator of the payment application 20. A mini-application is an application that operates when the payment application 20 is running. For example, when the payment application 20 is installed, some or all of the mini-application may be installed, or some or all of the mini-application may be installed from the service server corresponding to the mini-application. For example, when a mini-application is launched, it accesses the service server that provides the service corresponding to the mini-application, and the mini-application and the service server cooperate to provide services to the user. In this case, the service server may be the payment server 100 itself. In Figure 9, as an example, a button M1 is shown to launch a banking mini-application that provides banking services to users in cooperation with a banking server 200, which is an example of a service server, and a button M2 is shown to launch a securities mini-application that provides asset management services to users in cooperation with a securities server 300, which is another example of a service server. However, buttons for launching various types of mini-applications may be displayed, such as reservation apps for amusement facilities like movie theaters, or payment apps for paying public transportation fares.

[0043] [Charging screen] Figure 10 shows an example of the charge screen of the payment application 20. The charge screen is accessed, for example, when a user presses the charge button on the top screen. The charge screen displays an input area IA for entering the charge amount and a display area DA for displaying the bank account to which the charge amount will be sent. When a user enters the charge amount in the input area IA and presses the charge button TB3, the payment application 20 sends a charge instruction to the bank server 200, and the bank server 200 sends an amount equivalent to the charge amount from the bank account displayed in the display area DA to the payment server 100. In other words, the sending bank account must have an account balance of at least the charge amount entered by the user, so it is desirable that the user can check the balance of the bank account when entering the charge amount. For this reason, the bank mini-application displays an icon IC1 (an example of an "operation frame") in the display area DA to display the bank account balance, and displays the bank account balance obtained from the bank server 200 when a user who meets the predetermined conditions described later presses the icon IC1. As a result, the charge screen, which hides the bank account balance as shown on the left side of Figure 9, transitions to the charge screen, which displays the bank account balance as shown on the right side of Figure 9. This allows the user to enter the charge amount while confirming the displayed bank account balance.

[0044] Conversely, when a user presses 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 hides the bank account balance. In this way, the user can switch between displaying and hiding the bank account balance by pressing icons IC1 and IC2. In this embodiment, as an example, icons IC1 and IC2, which are shaped like human eyes, are used to switch between displaying and hiding the bank account balance. However, the present invention is not limited to such a configuration, and the bank mini-app may display any display (text, icons, images, etc.) that can attract the user's attention when the bank account balance is hidden. Furthermore, in this embodiment, the processing mainly performed by the bank mini-app may be performed as a function implemented in the bank mini-app, or it may be performed based on instructions from the settlement server 100. For example, the display processing performed by the bank mini-app may be performed by the settlement server 100, which functions as a "display control unit" and instructs the bank mini-app on the manner and timing of the display, causing the bank mini-app to perform the display processing.

[0045] Thus, when a user presses the charge button on the top screen of the bank mini-app to transition to the charge screen, the bank account balance is pre-obtained from the bank server 200, and the user can switch the display / hide of the obtained bank account balance by pressing icons IC1 and IC2. However, conventionally, there are legal restrictions on directly obtaining information about bank account balances from the bank and displaying it in an external application program. Furthermore, in conventional technology, when an external application program accesses a financial institution to obtain user information, the user is generally required to log in to the financial institution's system each time, or to enter a token (one-time password) that is only valid temporarily and issued by the financial institution's system, which can be inconvenient for the user. As described below, the present invention improves the authentication / consent flow related to obtaining bank account balances while satisfying legal restrictions by using a bank mini-app ID commonly held by the settlement server 100 and the bank server 200.

[0046] [Authentication / Consent Flow for Bank Mini-Apps] Figure 11 shows an example of an authentication / consent flow executed by the bank server 200. The authentication / consent flow shown in Figure 11 is executed, for example, when a user has not yet completed registration for the bank mini-app, and the user presses the icon IC1 on the charge screen shown in Figure 10, or when the user presses the mini-app button M1 on the top screen shown in Figure 9. "When a user has not yet completed registration for the bank mini-app" can be determined, for example, by the settlement server 100 referring to the user information 172 and determining whether the user's "bank mini-app registration" is YES or not. If a user has not yet completed registration for the bank mini-app, the bank mini-app has not been able to obtain the bank account balance from the bank server 200 in advance when transitioning from the top screen to the charge screen. Therefore, even when the icon IC1 on the charge screen is pressed, the bank mini-app will proceed to the authentication / consent flow shown in Figure 11 without displaying the bank account balance.

[0047] As shown in the left-hand screen of Figure 11, the bank mini-app first accesses the bank server 200 and displays the login screen for the bank server 200. When the user enters the 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 asks whether the user agrees to enable the display of the bank account balance (right-hand screen of Figure 11). For example, the bank mini-app asks whether the user agrees to link the bank's deposit account information and transaction details to the settlement server 100. On the other hand, if the user does not have a bank account, they can, for example, press the guidance display at the bottom of the screen (e.g., "Click here if you do not have an account") to proceed with opening a bank account. After the bank account is opened, the user accesses the login screen again, enters the necessary information, and logs in.

[0048] When a user confirms the consent content and presses the consent button TB5, the bank server 200 sets the user consent corresponding to the user's bank mini-app ID to YES and simultaneously sets the validity period starting from the time the consent button TB5 was pressed. Next, the bank server 200 sends the bank account balance corresponding to the user's bank mini-app ID to the settlement 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. The bank mini-app displays the notified bank account balance on the charge screen. Subsequently, during the validity period, when the settlement app 20 transitions to the charge screen, the bank mini-app retrieves the bank account balance in advance from the bank server 200 using the user's bank mini-app ID as a key, and displays the bank account balance without having to perform the authentication / consent flow again when the user presses the icon IC1. In other words, this allows for the linking of the electronic payment service account and the bank account in a way that is highly convenient for the user, so that the bank account balance can be used for electronic payments.

[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 settlement server 100, and the information management unit 140, upon receiving the bank account balance, 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 settlement server 100. More generally, the bank server 200 only needs to transmit the bank account balance to at least one of the settlement server 100 and the bank mini-app.

[0050] [Chain connection to securities server 300] In this way, by linking the bank account balance from the bank server 200 to the payment application 20 with the user's consent, the convenience for the user in using the electronic payment service can be improved. However, since multiple mini-applications can operate on the payment application 20, depending on the function of the mini-application, extending the linking of the bank account balance to other mini-applications, rather than limiting it to the payment application 20 as a super application, could improve the convenience of the mini-application for the user. The present invention realizes such a function using a securities mini-application as an example.

[0051] Figure 12 shows an example of an authentication / consent flow performed by the securities server 300. The authentication / consent flow shown in Figure 12 is performed, for example, when a user has not yet completed registration for the securities mini-app and presses the mini-app button M2 on the top screen shown in Figure 9. "When a user has not yet completed registration for the securities mini-app" can be determined, for example, by the settlement server 100 referring to the user information 172 and determining whether the user's "securities mini-app registration" is YES or not.

[0052] As shown in the left-hand screen of Figure 12, the securities mini-app first accesses the securities server 300 and displays the login screen for the securities server 300. When the user enters the 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 asks whether the user agrees to enable the display of the bank account balance (right-hand screen of Figure 12). This is the securities server 300 asking the user whether they agree to enable the display of the bank account balance through the securities mini-app. As shown in Figure 12, the securities server 300 may also ask whether the user wants to obtain the charge balance of the electronic payment service in addition to the bank account balance through integration. On the other hand, if the user has not opened a securities account, they can, for example, press the guidance display at the bottom of the screen (e.g., "Click here if you haven't opened an account yet") to proceed with opening a securities account. After the securities account is opened, the user accesses the login screen again, enters the necessary information, and logs in.

[0053] When a user confirms the terms of agreement and presses the consent button TB6, the securities server 300 sets the user consent corresponding to the user's securities mini-app ID to YES and simultaneously sets an effective period starting from the time the consent button TB6 is pressed. During this effective period, the user does not need to press the consent button TB6 again, and the securities server 300 can retrieve the bank account balance from the bank server 200 via the settlement server 100 and display it in the securities mini-app.

[0054] More specifically, the securities server 300 sends a request to the settlement server 100 to retrieve the bank account balance, including the user's securities mini-app ID. When the settlement server 100 receives the request to retrieve the bank account balance, the determination unit 144 determines whether the request satisfies predetermined conditions (chain connection determination process). Here, predetermined conditions include, for example, that the user has agreed to enable the display function of the bank account balance on both the bank mini-app and the securities mini-app (agreement to link the bank account balance). The determination unit 144 can determine whether the user has agreed on 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 meets predetermined conditions, the linking unit 146 uses the user's bank mini-app ID as a key to acquire the bank account balance from the bank server 200. After acquiring the bank account balance from the bank server 200, the linking unit 146 then uses the securities mini-app ID as a key to link the acquired bank account balance to the securities server 300. The securities server 300 displays the linked bank account balance on the securities mini-app screen. Thus, according to this embodiment, assuming 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 account balance is linked from the bank server 200 to the securities server 300 via the settlement server 100, and the securities server 300 displays the bank account balance in the securities mini-app. This enables secure and smooth linking of sensitive information such as bank account balances between multiple services.

[0056] Figure 13 shows an example of the contents of the chain connection management table 178. The chain connection management table 178 associates, for example, account ID, user consent (bank mini-app), validity period (bank mini-app), user consent (securities mini-app), validity period (securities mini-app), and whether or not a chain connection exists. User consent (bank mini-app) and validity period (bank mini-app) are the same information as "user consent" and "validity period" stored in the bank account information 210 shown in Figure 7. That is, when a user completes the authentication / consent flow shown in Figure 12, the bank server 200 sets "user consent" and "validity period" in the bank account information 210, while notifying the settlement server 100 of the same information, and the information management unit 140 sets the notified information as user consent (bank mini-app) and 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 Figure 8. That is, when the user completes the authentication / consent flow shown in Figure 13, the securities server 300 sets the "user consent" and "validity period" in the securities account information 310, while simultaneously notifying the settlement server 100 of the same information. The information management unit 140 then sets the notified information as the user consent (securities mini-app) and validity period (securities mini-app).

[0057] The Information Management Unit 140 sets "Presence of Chain Connection" to "Yes" if both User Consent (Bank Mini-App) and User Consent (Securities Mini-App) are set to "YES" and the current time is within the validity period (Bank Mini-App) and validity period (Securities Mini-App). Subsequently, when the Determination Unit 144 receives a request from the Securities Server 300 (or Securities Mini-App) to retrieve the bank account balance, it refers to the Chain Connection Management Table 178 and, if "Presence of Chain Connection" is set to "Yes", it permits the linking of the bank account balance for that user to the Securities Server 300 (or Securities Mini-App). Subsequently, the Linking Unit 146 links the bank account balance to the Securities Server 300.

[0058] Furthermore, the bank account information 210 shown in Figure 7, the securities account information 310 shown in Figure 8, and the linked connection management table 178 shown in Figure 13 each include an effective period that enables the linking of bank account balances without requiring further consent from the user. However, the present invention is not limited to such a configuration, and the effective period does not need to be set. In that case, once the user consents, the bank account balances will be linked permanently.

[0059] [Display bank account balance] Figure 14 shows an example of a securities mini-app screen displaying the bank account balance obtained by the securities server 300 from the bank server 200. The screen shown in Figure 14 is displayed when a user operates the securities mini-app after completing the authentication / consent flow shown in Figures 11 and 12, for example. As an example, Figure 14 shows a screen in which a user purchases stocks using the asset management service on the securities mini-app. As shown in Figure 14, the stock purchase screen includes fields for inputting, for example, the stock name, account type, purchase amount (or a combination of stock price and purchase quantity), and payment method.

[0060] The payment methods include, for example, radio button R1 for selecting to purchase from the charge balance and radio button R2 for selecting to purchase from the bank balance. This is because, after the user completes the authentication / consent flow shown in Figure 12, the securities mini-app receives the charge balance and bank account balance from the settlement server 100. If the user selects the charge balance to purchase stocks, the securities mini-app deducts the purchase amount from the user's electronic payment service charge balance to realize the user's stock purchase. More specifically, the securities mini-app notifies the settlement server 100 that it will deduct the purchase amount from the user's electronic payment service charge balance, and the settlement server 100 deducts the purchase amount from the charge balance. At the same time, the securities server 300 stores the user's stock purchase information (stock name, account type, purchase amount, etc.) in the "Holdings Information" of the securities account information 310. On the other hand, if the user selects the bank account balance to purchase stocks, the securities server 300 deducts the purchase amount from the user's bank account balance to realize the user's stock purchase. More specifically, the securities mini-app notifies the bank server 200 via the settlement server 100 that it will deduct the purchase price of the stocks from the user's bank account balance. The bank server 200 deducts the purchase price from the bank account balance, and at the same time, the securities server 300 stores the user's stock purchase information (such as the name of the stock purchased, the account type, and the purchase price) in the "Holdings Information" section of the securities account information 310.

[0061] In this scenario, communication between the securities server 300 and the settlement server 100 is conducted via the securities mini-app ID, while communication between the settlement server 100 and the bank server 200 is conducted via the bank mini-app ID. That is, whether the securities server 300 retrieves the bank account balance from the bank server 200 via the settlement server 100, or whether a user uses their bank account balance to purchase financial products, sensitive information such as the user's bank account number or securities account number is not transmitted. Instead, identification information such as the bank mini-app ID or securities mini-app ID is used to perform communication via a chained connection. In other words, this enables secure and smooth sharing of sensitive information, such as bank account balances, between multiple services.

[0062] [Process Flow] Next, with reference to Figure 15, the processing flow performed by the user terminal device 10, the settlement server 100, the bank server 200, and the securities server 300 will be described. Figure 15 is a sequence diagram showing an example of the processing flow performed by the user terminal device 10, the settlement server 100, the bank server 200, and the securities server 300.

[0063] First, the user accesses the bank server 200 via the bank mini-application on the user terminal device 10 and executes the authentication / consent flow shown in Figure 11 on the bank mini-application (S10). Once the authentication / consent flow is complete, the bank server 200 notifies the settlement server 100 of the user's consent regarding the linking of the bank account balance (S12). Next, the user accesses the securities server 300 via the securities mini-application on the user terminal device 10 and executes the authentication / consent flow shown in Figure 12 on the securities mini-application (S14). Once the authentication / consent flow is complete, the securities server 300 notifies the settlement server 100 of the user's consent regarding the linking of the bank account balance (S16).

[0064] Next, the user uses the securities mini-app on the user terminal device 10 (for example, by opening the screen for purchasing financial products), and the user terminal device 10 sends a request to the securities server 300 to retrieve the bank account balance (S18). Next, the securities server 300 sends a request to the settlement server 100 to retrieve the bank account balance, including the user's securities mini-app ID (S20). Next, the determination unit 144 of the settlement server 100 performs a chain connection determination process, that is, it determines whether the user has agreed to link the bank account balance on both the bank mini-app and the securities mini-app (S22).

[0065] If it is determined that the user has agreed to link their bank account balance on both the bank mini-app and the securities mini-app, the linking unit 146 sends a request to the bank server 200 to retrieve the bank account balance, including the user's bank mini-app ID (S24). Next, the bank server 200 identifies the user associated with the received bank mini-app ID and sends the user's bank account balance, linked to the bank mini-app ID, to the settlement server 100 (S26). Next, the linking unit 146 sends the user's bank account balance, linked to the securities mini-app ID, to the securities server 300 (S28). Next, the securities server 300 sends 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 completes the processing shown in this sequence diagram.

[0066] [Transition process to the banking mini-app] The sequence diagram shown in Figure 15 assumes 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 order. However, some users may start using the securities mini-app by completing only the authentication / consent flow on the securities mini-app without completing the authentication / consent flow on the bank mini-app. In that case, the chain connection determination process at S22 in the sequence diagram of Figure 15 will fail. In that case, the linkage unit 146 may transition the mini-app running 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 Figure 11. In another embodiment, if the securities mini-app fails to obtain the bank account balance, the linkage unit 146 may display an icon indicating that the bank account balance is unknown, and, depending on the user's selection, transition the securities mini-app to the bank mini-app and execute the authentication / consent flow on the bank mini-app.

[0067] Figure 15 shows an example of the transition process from a securities mini-app to a bank mini-app. As an example, Figure 15 shows a scenario where a user completes only the authentication / consent flow on the securities mini-app, starts using the securities mini-app, and purchases financial products. In this case, the securities mini-app fails to retrieve 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, pressing IC3 will cause the user terminal device 10 to transition from the securities mini-app to the bank mini-app and display the authentication / consent flow screen on the bank mini-app shown in Figure 11. Users who wish to display and use their bank account balance can complete the authentication / consent flow on the bank mini-app and return to the purchase screen to check their bank account balance and use it to purchase financial products.

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

[0069] Furthermore, in the above embodiment, for the sake of explanation, the processing of the bank mini-application is distinguished from the processing of the bank server 200, and the processing of the securities mini-application is distinguished from the processing of the securities server 300. However, the processing mainly performed by the bank mini-application (securities mini-application) can also be implemented as processing mainly performed by the bank server 200 (securities server 300), except for the display processing on the user terminal device 10. Conversely, the processing mainly performed by the bank server 200 (securities server 300) can also be implemented as processing mainly performed by the bank mini-application (securities mini-application), except for the storage and updating processing of bank account information 210 (securities account information 310).

[0070] Furthermore, the above embodiment described a case in which a payment application 20 serves as the platform, a bank mini-application and a securities mini-application operate, and the bank account balance managed by the bank server 200 is linked to the securities server 300 using a first identification information (bank mini-application ID) different from the bank account number and a second identification information (securities mini-application ID) different from the securities account number. However, the present invention is not limited to such a configuration, and the content of the applications and the information they link may differ. For example, a social networking service (SNS) application serves as the platform, a first game mini-application and a second game mini-application operate, and game points managed by the first game server are linked to the second game server using a first identification information different from the first game user identifier and a second identification information different from the second game user identifier.

[0071] According to the embodiment described above, a request received from the securities mini-app to retrieve the account balance of a bank account linked to an electronic payment service is determined to satisfy predetermined conditions. If it is determined that the predetermined conditions are satisfied, the settlement server 100 and the bank server 200 receive the account balance of the bank account from the bank server 200 based on the bank mini-app ID commonly held by both the settlement server 100 and the bank server 200, and link it to the securities mini-app. This enables secure and smooth sharing of sensitive information, such as bank account balances, between multiple services.

[0072] Although embodiments for carrying out the present invention have been described above using examples, the present invention is not limited in any way to these embodiments, and various modifications and substitutions can be made without departing from the spirit of the present invention. [Explanation of Symbols]

[0073] 10. User terminal device 20 Payment Apps 100 Payment Servers 120 Payment Content Provision Department 130 Payment Processing Unit 140 Information Management Department 142 Generation part 144 Judgment section 146 Liaison Department 200 bank servers 300 Securities Servers

Claims

1. An information processing device that processes information via a service that operates in cooperation with a first application and a second application running 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 predetermined conditions, If it is determined that the predetermined conditions are met, the device includes a linking unit that receives the account balance of the bank account from the account management server based on the first identification information of the user, which is commonly held by the device and the account management server that manages the bank account, and links with the second application. Information processing device.

2. The aforementioned service is an electronic payment service, The second application is an application program that works in conjunction with an asset management server to provide an asset management service using at least one of the charge balance of the electronic payment service and the account balance. If the aforementioned linking unit determines that the predetermined conditions are met, it links the account balance of the bank account to the second application based on a second identification information different from the first identification information, which is the user's second identification information commonly held by the device and the asset management server. The information processing apparatus according to claim 1.

3. The system further includes a generation unit that generates the first identification information when the user registers with the first application, and generates the second identification information when the user registers with the second application. The information processing apparatus according to claim 2.

4. The first application is an application program for utilizing the functions of the account management server, The aforementioned conditions include the user having agreed to link the account balance of the bank account on both the first application and the second application. The information processing apparatus according to claim 1.

5. If the linking unit determines that the first application has not yet agreed to link the account balance of the bank account, it will redirect the second application to the first application and cause the first application to execute a process to agree to link the account balance of the bank account. The information processing apparatus according to claim 4.

6. Information processing device, An information processing method that processes information through a service that operates in cooperation with a first application and a second application running on a user's terminal device, The system determines whether the request received from the second application to retrieve the account balance of a bank account linked to the service satisfies predetermined conditions. If it is determined that the predetermined conditions are met, the device receives the account balance of the bank account from the account management server based on the first user identification information commonly held by the device and the account management server that manages the bank account, and links it to the second application. Information processing methods.

7. In an information processing device, A program that processes information through a service that operates in cooperation with a first application and a second application running on the user's terminal device, The system determines whether a request received from the second application to retrieve the account balance of a bank account linked to the service satisfies predetermined conditions. If it is determined that the predetermined conditions are met, the device receives the account balance of the bank account from the account management server based on the first user identification information commonly held by the device and the account management server that manages the bank account, and links it to the second application. program.

Images