Payment server, payment system, method for controlling the payment server, and program

The settlement server addresses the limitation of existing systems by enabling fund transfers between financial institution accounts, allowing electronic payment systems to charge funds into a user's account at a financial institution.

JP2026181942APending Publication Date: 2026-11-19PAYPAY CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2025077779
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-08
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing electronic payment systems fail to facilitate the charging of funds to a user's account at a financial institution.

Method used

A settlement server capable of communicating with financial institution servers to process charges from a user's account at a first financial institution to a third account at a second financial institution via a second account of an electronic settlement service provider.

Benefits of technology

Enables the charging of funds into a user's account at a financial institution, enhancing the functionality of electronic payment systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026181942000001_ABST
    Figure 2026181942000001_ABST
Patent Text Reader

Abstract

To enable the charging of funds into users' accounts at financial institutions. [Solution] A settlement server that performs electronic settlements in an electronic settlement service, which is capable of communicating with a first financial institution server that manages accounts at a first financial institution and a second financial institution server that manages accounts at a second financial institution, and which includes a charge processing unit that causes the first financial institution server and the second financial institution server to perform a charge processing to transfer a charge amount from a first account, which is the user's account at the first financial institution, to a third account, which is the user's account at the second financial institution, via a second account, which is the electronic settlement service provider's account at the second financial institution.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a payment server, a payment system, a control method for a payment server, and a program.

Background Art

[0002] Conventionally, electronic payment services using user terminal devices owned by users are known. For example, Patent Document 1 proposes an electronic payment system that executes electronic payment by displaying code information such as barcodes and QR Code (registered trademark) on a user terminal device, and causing a store terminal device installed in a store to read the code information.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of Invention

Problems to be Solved by the Invention

[0004] However, in the electronic payment system described in Patent Document 1, although it is possible to charge electronic money to the user's account in the electronic payment service, there are cases where it is not possible to charge funds to the user's account at a financial institution.

[0005] The present invention has been made in consideration of such circumstances, and one of the objectives is to provide a payment server, a payment system, a control method for a payment server, and a program that are capable of charging funds to a user's account at a financial institution.

Means for Solving the Problems

[0006] One aspect of the present invention is a settlement server that performs electronic settlements in an electronic settlement service, which is capable of communicating with a first financial institution server that manages accounts at a first financial institution and a second financial institution server that manages accounts at a second financial institution, and comprises a charge processing unit that causes the first financial institution server and the second financial institution server to perform a charge processing to transfer a charge amount from a first account, which is the account of a user at the first financial institution, to a third account, which is the account of the user at the second financial institution, via a second account, which is the account of the electronic settlement service provider at the second financial institution. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide a settlement server, a settlement system, a method for controlling the settlement server, and a program that can charge funds into a user's account at a financial institution. [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 diagram showing the configuration of payment server 100. [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 merchant wallet information 178. [Figure 8] This is a diagram showing the configuration of the financial institution server 200. [Figure 9] This figure shows an example of the contents of account information 272. [Figure 10] This figure shows an example of the contents of merchant information 274. [Figure 11] FIG. 2 is a diagram illustrating an example of a home screen IM1 of a payment application 20. [Figure 12] FIG. 3 is a diagram illustrating an example of a home screen IM2 of a financial institution application 30. [Figure 13] FIG. 4 is a diagram illustrating an example of a first consent screen IM3 of the payment application 20. [Figure 14] FIG. 5 is a diagram illustrating an example of a second consent screen IM4 of the financial institution application 30. [Figure 15] FIG. 6 is a diagram illustrating an example of an error screen IM5 during account linking processing. [Figure 16] FIG. 7 is a diagram illustrating an example of a payment screen IM6 for account balance payment. [Figure 17] FIG. 8 is a sequence diagram illustrating an example of account balance payment by store scanning. [Figure 18] FIG. 9 is a diagram illustrating an example of a payment completion screen IM7 for account balance payment. [Figure 19] FIG. 10 is a sequence diagram illustrating an example of account balance payment by user scanning. [Figure 20] FIG. 11 is a diagram illustrating an example of a transaction history screen IM8. [Figure 21] FIG. 12 is a diagram illustrating an example of a charge screen IM9. [Figure 22] FIG. 13 is a sequence diagram illustrating an example of account balance charge processing. [Description of Embodiments]

[0009] Hereinafter, embodiments of a payment server, a payment system, a control method for a payment server, and a program according to the present invention will be described with reference to the drawings. Various apparatuses that appear in the following, such as "servers", for providing services to users or performing internal analysis may be implemented by a decentralized group of apparatuses, and the operators that operate the respective apparatuses may be different. Further, the hardware owner of the apparatuses (cloud server provider) and the operator that performs substantial operation may also be different. The electronic payment service is a service that supports payments related to the purchase of goods and services at stores. A store is, for example, a physical store (actual store) existing in the real space, but may also include a virtual store for electronic commerce. The virtual store may include those provided by an entity different from the electronic payment service operator. In that case, control is performed such that a transition is made to the interface screen of the electronic payment service at the time of payment for shopping at the virtual store. In the electronic payment service, a store is treated as belonging to, for example, a member store (brand), and processing such as payment when a purchase action is performed at the store is mainly performed between the user and the member store. Alternatively, processing such as payment may be performed between the user and the store.

[0010] [Electronic Payment Service] Figure 1 is a diagram illustrating an example of a configuration for implementing an electronic payment service. The electronic payment service is implemented centering on a payment server 100. The payment server 100 communicates with, for example, each of one or more user terminal apparatuses 10, one or more first store terminal apparatuses 50, one or more second store terminal apparatuses 70, and a plurality of financial institution servers 200 via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider apparatus, and the like.

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

[0012] Furthermore, the user terminal device 10 operates by running a financial institution application (hereinafter referred to as the financial institution app) 30 using a processor such as a CPU, in cooperation with the financial institution server 200 to provide users with financial services offered by the financial institution. The financial institution app 30 incorporates a payment SDK (Software Development Kit) 31. The payment SDK 31 is a program that has at least some of the functions of the payment app 20. The financial institution app 30 is installed on the user terminal device 10, for example, from an application store, and controls the camera, communication device, touch panel, etc.

[0013] 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 may include a so-called POS (Point of Sale) device, and the product price acquisition function and 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 paper or plastic media. The store code image 60 may also be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0014] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, tablet, personal computer, etc. The affiliated store interface 72 operates on the second store terminal device 70. The affiliated store interface 72 may be an affiliated store application or a browser. The affiliated store interface 72 accepts coupon settings etc. from the affiliated store operator 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 by running the affiliated store application, or reading a code image displayed by the user terminal device 10.

[0015] The payment server 100 implements 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 a merchant server, in which case payment information is transmitted from the POS device to the payment server 100 via the merchant server. In the following description, this distinction will not be made, and it will be assumed that payment information is transmitted from the first store terminal device 50.

[0016] The financial institution server 200 is a computer that manages accounts at a financial institution and communicates with the settlement server 100 via a network NW. The financial institution may be a financial institution that is part of the group of an electronic payment service provider. The financial institution may be, for example, an institution that provides financial services such as a bank or a securities company. In this embodiment, an example in which the financial institution is a bank will be described.

[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 identifies 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 diagram of the configuration of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a payment content provision unit 115, a payment processing unit 120, an information management unit 125, an account linking unit 130, a screen generation unit 135, a coupon acquisition unit 140, a charge processing unit 145, a deposit unit 150, 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 LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit), or by the cooperation of software and hardware. The program may be stored in advance on 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 on a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed on the storage device when the storage medium is inserted into the drive device.

[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 merchant wallet information 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 115, 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 115 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, etc., to the payment server 100.

[0025] The settlement processing unit 120 performs settlement processing based on settlement information transmitted by the user terminal device 10 or the first store terminal device 50. The settlement processing unit 120 performs settlement processing while referring to the user information 172. The settlement processing unit 120 also has a function to cause the financial institution server to settle the account balance.

[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 includes, for example, user URL, account ID, telephone number, password, as well as email address, user ID, name, address, date of birth, registration date, electronic money balance, credit payment settings, credit payment limit, credit payment amount, available credit payment amount, payment method settings, bank account, credit card, charge history information, payment history information, points, and coupon information. The user URL is used for money 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 electronic money 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), sending from a registered bank account, etc. Sending from a bank account may also be done via direct debit. When charging, the charge amount is automatically debited from the user's bank account and transferred to the electronic payment service provider's account. The electronic payment service provider then charges the user's electronic money upon receipt of the funds into their account. Users may register multiple bank accounts. In this case, the user may select the bank account from which to send the funds when charging. The credit payment setting indicates whether or not the user has completed the settings to enable electronic payments via credit card, and is set to either "Completed" or "Not Completed". The credit limit is the monthly limit on credit payments that can be made. The credit payment amount is the amount already used for credit payments during the current month. The available credit payment amount is the amount available for credit payments during the current month, calculated by subtracting the credit payment amount from the credit limit. Although the diagram shows only one credit limit, in reality there are also daily limits, etc., and the lower of these may be set as the credit limit. Further details on credit payments will be described later. The payment method setting is setting information that indicates whether the user will make an electronic payment using their electronic money balance, an electronic payment using a credit card, or an account balance payment using their bank account deposit balance at that time. The bank account is information about a bank account that can be used to deposit funds into the electronic payment service (branch number, account number, etc.). The credit card is information about a credit card that can be used to deposit funds into the electronic payment service (card number, etc.). The charge history information is a history of when the user has previously sent money to the electronic payment service to increase their electronic money balance. Payment history information is data that 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] Points are information indicating the number of points a user possesses. For example, users can use points in electronic payments at a rate of 1 point = 1 yen. Coupon information is information about coupons a user possesses. By using coupons in electronic payments, users can receive discounts on products or cashback based on the purchase amount.

[0029] 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 wallet ID are associated with the merchant ID, and a third table 176C in which the store name is associated with the store ID. The wallet ID is identification information for identifying the wallet into which the merchant's sales proceeds are deposited. In addition to this information, the merchant / store information 176 may also include information such as the merchant or store category, store location, and payment pattern.

[0030] Figure 7 shows an example of the contents of merchant wallet information 178. Merchant wallet information 178 is information that links, for example, a wallet ID with sales revenue for each electronic payment method (electronic money balance, credit card payment, bank account balance) and bank account information. The bank account information is the account information to which sales revenue is transferred (store number, account number, etc.).

[0031] The information management unit 125 manages user information 172, merchant / store information 176, and merchant wallet information 178 based on information obtained from the user terminal device 10 and the second store terminal device 70. For example, the information management unit 125 adds, edits, and deletes new records for user information 172, merchant / store information 176, and merchant wallet information 178.

[0032] [Electronic payment] When the payment processing unit 120 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 "electronic money balance", the payment processing unit 120 performs electronic payment as follows. For example, the payment processing unit 120 performs electronic payment by decreasing the electronic money balance managed in association with the account ID in the user information 172 and increasing the item value of sales proceeds from the "electronic money balance" managed in association with the wallet ID in the merchant wallet information 178. The item value of sales proceeds from electronic payment is not used as electronic money itself, for example, but the amount corresponding to the item value of sales proceeds from electronic payment is transferred to the merchant's bank account in a cycle according to the agreement between the merchant and the electronic payment service. The merchant may receive the sales proceeds as electronic money. In this case, the information management unit 125 may manage the merchant's electronic money balance in the merchant wallet information 178, linked to the merchant's wallet ID.

[0033] The payment processing unit 120 performs electronic payment for users whose "payment method setting" is set to "credit card payment" as follows. Credit card payment is a payment method that cooperates with a credit card company, which is a separate entity from the electronic payment service provider, and allows electronic payment that does not depend on the electronic money balance within the credit limit. In order to use the credit card payment service, it may be required to obtain a credit card provided by the electronic payment service provider. The amount used by credit card payment is settled by requesting the credit card company operator. In this case, the payment processing unit 120 sends the payment amount to the credit card company operator to process the credit card payment, and also performs electronic payment by increasing the value of the "sales amount by credit card payment" item managed in the merchant wallet information 178, which is associated with the merchant's wallet ID. The payment processing unit 120 also updates the credit card payment information in the user information 172. Specifically, the payment processing unit 120 adds the payment amount to the credit card usage amount in the user information 172 and subtracts the same amount from the available credit card payment amount. If the payment amount exceeds the available credit card payment amount, an error notification is sent back to the payment application 20.

[0034] The settlement processing unit 120 instructs the financial institution server 200 to perform account balance settlement for users whose "Setting Method" is set to "Account Balance Settlement". The configuration of the financial institution server 200 will be described below as a prerequisite for explaining the details of account balance settlement.

[0035] [Financial institution server] Figure 8 is a diagram of the configuration of the financial institution server 200. The financial institution server 200 includes, for example, a communication unit 210, an account balance settlement processing unit 220, a transfer processing unit 230, an information management unit 240, an account linking unit 250, and a storage unit 270. Components other than the communication unit 210 and the storage unit 270 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 LSIs, ASICs, FPGAs, and GPUs, or by the cooperation of software and hardware. The program may be stored in advance in a storage device such as an HDD 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.

[0036] The storage unit 270 can be an HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 270 may also be a NAS device that can be accessed by the financial institution server 200 via a network. The storage unit 270 stores information such as account information 272 and merchant information 274.

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

[0038] The account balance settlement processing unit 220 settles the account balance based on the user's account balance, using information received from the settlement server 100 and information stored in the storage unit 270. Details of account balance settlement will be described later.

[0039] The transfer processing unit 230 performs the transfer processing in response to the transfer request from the settlement server 100. Details of the transfer processing will be described later.

[0040] The information management unit 240 manages the account information 272 and merchant information 274 stored in the storage unit 270. For example, the information management unit 240 adds, edits, deletes, etc., new records for the account information 272 and merchant information 274.

[0041] Figure 9 shows an example of the contents of account information 272. Account information 272 is a collection of information such as branch number, account number, deposit balance, account balance payment limit, account balance payment usage amount, name, address, date of birth, password, transaction history information, and account ID. The branch number is a number used to identify a branch of a financial institution. The account number is a number used to identify the user's account. The deposit balance is information that shows the balance of the deposit the user has made with the financial institution. The account balance payment limit is the amount that the user can use to make account balance payments per month. The user can set the account balance payment limit as appropriate using the financial institution app 30. The account balance payment usage amount is the total amount the user has used for account balance payments during the current month. The name, address, and date of birth are the same information as the name, address, and date of birth included in user information 172 (Figure 5). The password is authentication information required when the user uses the financial institution's services and is used when launching the financial institution app 30 and logging in. Transaction history information is information that shows the transaction history of the user's account (deposit source information, withdrawal destination information, amount, date and time, etc.). The account ID is the same information as the account ID included in user information 172 (Figure 5), and is identification information used to identify the user. When account linking is performed as described later, the user's account ID and account information (branch number, account number, etc.) are linked and managed in the payment server 100 and the financial institution server 200.

[0042] Figure 10 shows an example of the contents of merchant information 274. Merchant information 274 is a collection of information such as merchant ID and merchant name. The merchant ID is identification information used to identify the merchant. The merchant name is information indicating the name of the merchant. The merchant ID and merchant name included in merchant information 274 are the same information as the merchant ID and merchant name included in the second table 176B (Figure 6) of merchant / store information 176, and this information is synchronized between the payment server 100 and the financial institution server 200.

[0043] [Account Linking] Next, we will explain account linking between the payment server 100 and the financial institution server 200. When a user uses account balance payment at a financial institution, they must link their account with the payment server 100 and the financial institution server 200 in advance. Users can proceed with the account linking procedure by applying to start using account balance payment from the payment app 20 or the financial institution app 30. As a prerequisite for account linking, the user must have an account with a financial institution, and both the payment app 20 and the financial institution app 30 must be installed on the user terminal device 10. In addition, when linking accounts, the user must be logged into both the payment app 20 and the financial institution app 30.

[0044] Figure 11 shows an example of the home screen IM1 of the payment app 20. As shown in Figure 11, the home screen IM1 of the payment app 20 includes areas A1 to A5 and button B1. Area A1 displays code images such as barcodes and QR codes (registered trademarks) used for smartphone payments. Area A2 displays icons for instructing major smartphone payment operations such as scanning, sending money, charging, and setting payment methods. Area A3 displays the user's electronic money balance or bank account balance.

[0045] For example, if a user selects (taps) a payment method icon displayed in area A2, the payment app 20 may display a selection screen on the display unit of the user terminal device 10, prompting the user to select a payment method. If the user selects electronic payment using their electronic money balance, the payment app 20 may display the user's electronic money balance in area A3. This allows the user to easily check their electronic money balance. On the other hand, if the user selects payment using their account balance, the payment app 20 may display the user's account balance in area A3. This allows the user to easily check their account balance.

[0046] Area A4 displays various icons for launching various mini-applications that can be executed with the payment application 20. Specifically, area A4 displays eight icons IC1 to IC8. Icons IC1 to IC6 are icons for launching mini-applications. When the user selects (taps) any of icons IC1 to IC6, the payment application 20 launches the mini-application corresponding to the selected icon. Icon IC7 is the favorites icon. When the user selects (taps) icon IC7, the payment application 20 displays a favorites screen on the display unit of the user terminal device 10, showing a list of the user's pre-set favorite mini-applications. Icon IC8 is the function list icon. When the user selects (tap) icon IC8, the payment application 20 displays a function list screen on the display unit of the user terminal device 10, showing a list of all mini-applications.

[0047] Area A5 displays the message, "Click here to apply for account balance settlement." When the user selects (tap) area A5, the first consent screen IM3 (Figure 13), described later, is displayed on the user terminal device 10, and the account linking process begins.

[0048] Button B1 is displayed at the bottom of the home screen IM1 of the payment app 20. When the user selects (tap) button B1, a payment screen (not shown) is displayed. The user takes a picture of the store code image 60 from the payment screen, thereby performing the user-scan electronic payment described above. Alternatively, the first store terminal device 50 reads the code image displayed on the payment screen, thereby performing the store-scan electronic payment described above.

[0049] The payment application 20 may also obtain payment history information from the payment server 100 and display it on the display unit of the user terminal device 10. This allows the user to easily check their payment history.

[0050] Figure 12 shows an example of the home screen IM2 of the financial institution application 30. When a user launches the financial institution application 30 using the user terminal device 10, the home screen IM2 shown in Figure 12 is displayed on the display unit of the user terminal device 10. Through the financial institution application 30, the user can use account balance settlement. Below, a bank application will be described as an example of the financial institution application 30.

[0051] As shown in Figure 12, the home screen IM2 of the financial institution app 30 includes areas A6, A7, and a payment button B2. Area A6 displays icons representing the various functions of the financial institution app 30 (such as transfer, borrowing, and debit). When the user selects (tap) any of the icons displayed in area A6, the function corresponding to the selected icon is executed. Area A7 displays the transaction history of the user's bank account.

[0052] The payment button B2 is a button that instructs the user to pay using their account balance. Account balance payment is a payment method of an electronic payment service linked to an account, separate from the financial institution providing the financial institution app 30. For example, when a user purchases goods at a store that is a merchant of the electronic payment service, they select (tap) the payment button B2. In response to the selection of the payment button B2, the financial institution app 30 executes the payment SDK 31 to retrieve and display the account balance payment screen from the electronic payment service's payment server 100.

[0053] If account linking is not performed between the payment server 100 and the financial institution server 200, the user will not be able to use account balance payment. Therefore, if the user selects (taps) the payment button B2 when account linking has not been performed between the payment server 100 and the financial institution server 200, the first consent screen IM3 (Figure 13), described later, will be displayed on the display unit of the user terminal device 10, and account linking will be initiated. Account linking is performed by the account linking unit 130 of the payment server 100 and the account linking unit 250 of the financial institution server 200.

[0054] Figure 13 shows an example of the first consent screen IM3 of the payment app 20. For example, if a user selects (taps) area A5 from the home screen IM1 (Figure 11) of the payment app 20, the payment app 20 displays the first consent screen IM3 on the display unit of the user terminal device 10. Also, if an account linkage has not been established between the payment server 100 and the financial institution server 200, and a user selects (taps) the payment button B2 from the home screen IM2 (Figure 12) of the financial institution app 30, the payment app 20 will launch and display the first consent screen IM3 on the display unit of the user terminal device 10.

[0055] The first consent screen, IM3, contains confirmation items for account linking. In the example shown in Figure 13, it states that when linking accounts, the information registered with the electronic payment service, the user's identity verification information, and the deposit and payment methods will be provided to the financial institution (bank) operating the financial institution server 200.

[0056] Buttons B3 and B4 are displayed at the bottom of the first consent screen IM3. When the user agrees to the confirmation items listed on the first consent screen IM3 and selects (taps) button B3, the payment app 20 sends an account linking instruction, including the user's account ID, to the payment server 100, and also sends the same account linking instruction to the financial institution server 200 via the payment server 100. Subsequently, the financial institution app 30 is launched on the user terminal device 10, and the second consent screen IM4 (Figure 14), described later, is displayed on the display unit of the user terminal device 10. On the other hand, when the user selects (taps) button B4, the payment app 20 terminates the procedure without sending the account linking instruction.

[0057] Figure 14 shows an example of the second consent screen IM4 of the financial institution app 30. The second consent screen IM4 contains confirmation items for account linking. In the example shown in Figure 14, it is stated that, in order to link accounts, the user's identity verification information, deposit account information, and transaction details registered with the financial institution (bank) will be provided to the electronic payment service provider operating the payment server 100. The second consent screen IM4 also displays the account information of the user to be linked.

[0058] Buttons B5 and B6 are displayed at the bottom of the second consent screen IM4. If the user agrees to the confirmation items listed on the second consent screen IM4 and selects (taps) button B5, the financial institution app 30 sends an account linking instruction, including the user's account information (branch number, account number, etc.), to the financial institution server 200, and then sends the said account linking instruction to the settlement server 100 via the financial institution server 200. Subsequently, the account linking process takes place between the settlement server 100 and the financial institution server 200. On the other hand, if the user selects (taps) button B6, the financial institution app 30 terminates the procedure without sending an account linking instruction.

[0059] The account linking unit 130 of the payment server 100 receives an account linking instruction from the payment app 20 and also receives an account linking instruction from the financial institution app 30 via the financial institution server 200. Upon receiving this instruction, the payment server 100 obtains the user's identity verification information (name, date of birth) held by the payment server 100 and the user's identity verification information (name, date of birth) held by the financial institution server 200. Furthermore, if the user's identity verification information held by the payment server 100 matches the user's identity verification information held by the financial institution server 200, the account linking unit 130 performs account linking. For example, the account linking unit 130 may obtain the identity verification information linked to the account ID included in the account linking instruction received from the payment app 20 from the user information 172. Alternatively, the account linking unit 130 may query the financial institution server 200 to obtain the identity verification information linked to the account information included in the account linking instruction received from the financial institution app 30. In this way, by verifying whether the user's identity verification information held by the payment server 100 matches the user's identity verification information held by the financial institution server 200, the security of the account linking process can be improved.

[0060] If the user's identity verification information held by the payment server 100 matches the user's identity verification information held by the financial institution server 200, the account linking unit 130 links the account ID included in the account linking instruction received from the payment app 20 with the account information included in the account linking instruction received from the financial institution app 30 and records it in the user information 172. As a result, the user's account information used for account balance settlement is recorded in the user information 172. The information management unit 125 manages the account information for charging the electronic money balance and the account information for account balance settlement separately in the "bank account" item in the user information 172.

[0061] Similarly, the account linking unit 250 of the financial institution server 200 receives account linking instructions from the payment application 20 via the payment server 100, and also receives account linking instructions from the financial institution application 30. Upon receiving these instructions, the account linking unit 250 obtains the user's identity verification information (name, date of birth) held by the payment server 100, as well as the user's identity verification information (name, date of birth) held by the financial institution server 200. The account linking unit 250 also performs account linking if the user's identity verification information held by the payment server 100 matches the user's identity verification information held by the financial institution server 200. For example, the account linking unit 250 may query the payment server 100 to obtain the identity verification information associated with the account ID included in the account linking instruction received from the payment application 20. Alternatively, the account linking unit 250 may obtain the identity verification information associated with the account information included in the account linking instruction received from the financial institution application 30 from the account information 272. In this way, by verifying whether the user's identity verification information held by the payment server 100 matches the user's identity verification information held by the financial institution server 200, the security of the account linking process can be improved.

[0062] If the user's identity verification information held by the payment server 100 matches the user's identity verification information held by the financial institution server 200, the account linking unit 250 links the account ID included in the account linking instruction received from the payment app 20 with the account information included in the account linking instruction received from the financial institution app 30 and records it in the account information 272. This completes the account linking between the payment server 100 and the financial institution server 200, and the user can use account balance payment.

[0063] If the user's identity verification information held by the payment server 100 does not match the user's identity verification information held by the financial institution server 200, the screen generation unit 135 of the payment server 100 generates an error screen IM5 (Figure 15) to inform the user of the mismatch, and sends the error screen to the user terminal device 10 for display.

[0064] Figure 15 shows an example of the error screen IM5 during account linking processing. The error screen IM5 is displayed when the name of the user registered with the electronic payment service does not match the name registered with the user's bank account. The error screen IM5 includes a button B7 for checking the user's identity verification information held by the payment server 100 and a button B8 for checking the user's identity verification information held by the financial institution server 200. The error screen IM5 also displays a message prompting the user to match the name in their electronic payment service account with the name in their bank account.

[0065] When button B7 is selected (tapped) by the user, the screen generation unit 135 generates a first confirmation screen (not shown) containing the user's identity verification information held by the payment server 100, and transmits the first confirmation screen to the user terminal device 10 for display. This allows the user to confirm their identity verification information (name, date of birth) held by the payment server 100. Button B7 may have a deep link built in to display the user's identity verification information held by the payment server 100. Alternatively, when the user selects (tap) button B7, the linked payment application 20 may be launched to display the identity verification information held by the payment server 100.

[0066] Furthermore, if button B8 is selected (tapped) by the user, the screen generation unit 135 generates a second confirmation screen (not shown) containing the user's identity verification information held by the financial institution server 200, and transmits the second confirmation screen to the user terminal device 10 for display. This allows the user to confirm their identity verification information (name, date of birth) held by the financial institution server 200.

[0067] For example, if a user's surname changes due to marriage or other reasons, and the user forgets to register the changed surname in either the electronic payment service or their bank account, the identity verification information will not match. Even in such cases, by displaying the error screen IM5 shown in Figure 15, the user can easily verify the identity verification information of the user held by the payment server 100 and the identity verification information of the user held by the financial institution server 200.

[0068] Users can use the payment app 20 to modify their personal identification information held by the payment server 100. Users can also use the financial institution app 30 to modify their personal identification information held by the financial institution server 200. Once the user's personal identification information is corrected, account linking between the payment server 100 and the financial institution server 200 can be facilitated.

[0069] In the example shown in Figure 15, an error screen is displayed when the user's name does not match, but this is not the only option. For example, an error screen may also be displayed when the user's date of birth does not match. The information used for identity verification is not limited to the user's name or date of birth; it can be any information used in the identity verification process, such as an address.

[0070] Thus, in this embodiment, when two services link accounts and a mismatch occurs in the identity verification information between the two, a screen is generated that allows users to easily verify the identity verification information of each service. This allows users to easily correct their identity verification information as needed.

[0071] [Account balance payment] Once account linking is complete, users will be able to use account balance payment. When the user selects the payment button B2 displayed on the home screen IM2 (Figure 12) of the financial institution app 30, the financial institution app 30 executes the payment SDK 31 to retrieve and display the account balance payment screen IM6 (Figure 16) from the electronic payment service's payment server 100.

[0072] Figure 16 shows an example of a payment screen IM6 for account balance settlement. The payment screen IM6 is generated by the screen generation unit 135 of the payment server 100. The screen generation unit 135 obtains the user's account information and points held by the user used for account balance settlement from the user information 172, queries the financial institution server 200 to obtain the user's account balance, and generates the payment screen IM6 based on this information. The payment server 100 may also obtain the account balance of linked users from the financial institution server 200 at regular intervals, associate it with the account ID, and store it in the storage unit 170, and the screen generation unit 135 may obtain the user's account balance from the storage unit 170 to generate the payment screen IM6. As shown in Figure 16, the payment screen includes first code information CD1, second code information CD2, areas A8 to A9, buttons B9 to B11, and toggle switch T.

[0073] The first code information CD1 is a one-dimensional code such as a barcode. The second code information CD2 is a two-dimensional code such as a QR code (registered trademark). The same information is encoded in both the first code information CD1 and the second code information CD2 and are read by the first store terminal device 50. The first code information CD1 and the second code information CD2 are used for account balance settlement via store scan. Area A8 displays the user's account balance used for account balance settlement. Area A9 displays the points held by the user. The toggle switch T is a switch for switching whether or not to use points in account balance settlement.

[0074] Button B9 is used to switch to the code reading screen (not shown) for reading the store code image 60 in order to settle the account balance by user scan. Button B10 is used to display the transaction history screen IM8 (Figure 20), which will be described later. Button B11 is used to display the charge screen IM9 (Figure 21), which will be described later.

[0075] When the first code information CD1 or the second code information CD2 is read by the first store terminal device 50, account balance settlement by store scan is performed. On the other hand, when the store code image 60 is read by the user terminal device 10, account balance settlement by user scan is performed. The following describes account balance settlement by store scan and account balance settlement by user scan, respectively.

[0076] [Account balance settlement via store scan] Figure 17 is a sequence diagram showing an example of account balance settlement via store scan. First, the user selects (tap) the payment button B2 from the home screen IM2 (Figure 12) of the financial institution app 30 (S101). As mentioned above, the payment button B2 is a button that instructs the user to settle the account balance using their account balance.

[0077] Next, the financial institution application 30 executes the payment SDK 31. The payment SDK 31 is a program that has at least some of the functions of the payment application 20. The payment SDK 31 sends a one-time code issuance request to the payment server 100 (S102). The one-time code issuance request includes an account ID for identifying the user's account in the electronic payment service.

[0078] The payment server 100 generates a one-time code in response to a request for one-time code issuance (S103). Here, the payment server 100 associates the one-time code with the user's account ID and stores it in the storage unit 170.

[0079] In S102, the financial institution application 30 sends a request to the settlement server 100 to issue a one-time code including the account ID, but it is not limited to this. For example, the financial institution application 30 may obtain the user's account information (branch number, account number, etc.) stored in the user terminal device 10 or the financial institution server 200, and instead of the account ID, send a request to the settlement server 100 to issue a one-time code including the user's account information (branch number, account number, etc.). In this case, in S103, the settlement server 100 may obtain the user's account ID linked to the user's account information (branch number, account number, etc.) from the user information 172, and store the generated one-time code and the user's account ID linked together in the storage unit 170.

[0080] Next, the settlement server 100 sends a one-time code to the financial institution application 30 (S14). The settlement SDK 31 embedded in the financial institution application 30 generates a code image based on the one-time code (S105). The code image generated here will be displayed on the settlement screen for account balance settlement. For example, as shown in Figure 13 above, the first code information CD1 and the second code information CD2 are displayed as code images on the settlement screen.

[0081] The user holds the display surface of the user terminal device 10 over the first store terminal device 50 (presents it). Meanwhile, the first store terminal device 50 decodes the code image using its optical reading function and obtains a one-time code (S106).

[0082] The first store terminal device 50 generates payment information including a one-time code, payment amount, merchant ID, store ID, etc., and transmits it to the payment server 100 (S107). The payment amount information is obtained in advance by barcode reading or manual input.

[0083] The payment server 100 obtains the user's account ID corresponding to the one-time code from the storage unit 170 based on the received payment information. The payment server 100 also sends an account balance settlement request to the financial institution server 200 with which the account linkage was established (S108). The account balance settlement request includes the user's account ID, the settlement amount, and the merchant ID.

[0084] The payment processing unit 120 of the payment server 100 may determine whether payment is possible based on the payment amount and the deposit balance of the user's bank account. Alternatively, the payment processing unit 120 may determine whether payment is possible based on the payment amount and the amount available for payment from the account balance (the amount obtained by subtracting the amount used for payment from the account balance payment limit). The payment processing unit 120 may query the financial institution server 200 to obtain the deposit balance of the user's bank account, the account balance payment limit, and the amount used for payment from the account balance. If the payment processing unit 120 determines that payment is not possible, it may notify the financial institution application 30 that payment from the account balance cannot be made and display this information to the financial institution application 30 via the payment SDK 31.

[0085] The financial institution server 200 performs account balance settlement based on the account balance settlement request (account ID, settlement amount, etc.) received from the settlement server 100 (S109). Specifically, the account balance settlement processing unit 220 of the financial institution server 200 obtains the user's account information (branch number, account number, etc.) linked to the account ID included in the account balance settlement request from the account information 272. The account information (branch number, account number, etc.) of the electronic payment service provider may be stored in the storage unit 270 in advance. The account balance settlement processing unit 220 also transfers the settlement amount from the user's account to the electronic payment service provider's account and updates the account information 272 (deposit balance, account balance settlement amount used, transaction history information, etc.). At this time, the information management unit 240 may obtain the merchant name linked to the merchant ID included in the account balance settlement request from the merchant information 274 and record the obtained merchant name and settlement amount in the transaction history information linked to the user's account information (branch number, account number, etc.) in the account information 272. Through the above process, the sales proceeds of the participating merchants can be temporarily transferred to the account of the electronic payment service provider.

[0086] In this embodiment, the settlement processing unit 120 of the settlement server 100 determines whether or not payment is possible, but this is not limited to this. For example, the account balance settlement processing unit 220 of the financial institution server 200 may determine whether or not payment is possible based on the payment amount and the deposit balance of the user's bank account. Alternatively, the account balance settlement processing unit 220 may determine whether or not payment is possible based on the payment amount and the amount available for account balance settlement (the amount obtained by subtracting the amount used for account balance settlement from the account balance settlement limit). If the account balance settlement processing unit 220 determines that payment is not possible, it may send an error notification to the settlement server 100. In response to the error notification, the settlement server 100 may notify the financial institution application 30 that account balance settlement cannot be performed and display this information on the financial institution application 30 via the settlement SDK 31.

[0087] Next, the financial institution server 200 sends a payment completion notification to the payment server 100 (S110). The payment processing unit 120 of the payment server 100 updates the merchant's sales balance in response to the payment completion notification (S111). Specifically, the payment processing unit 120 obtains the merchant's wallet ID from the merchant / store information 176 and adds the payment amount to the item value of sales balance settlement linked to the merchant's wallet ID in the merchant wallet information 178. Through the above process, the sales balance is transferred to the electronic payment service provider's account and the item value of sales balance in the merchant wallet information 178 is updated. Alternatively, the payment processing unit 120 may update the merchant's sales balance after confirming that the payment amount has been transferred to the electronic payment service provider's account after receiving the payment completion notification from the financial institution server 200.

[0088] The sales proceeds transferred to the electronic payment service provider's account will be deposited into the merchant's account by the deposit unit 150 of the payment server 100. The deposit unit 150 may also deposit the sales proceeds into the merchant's account immediately upon receipt of the funds into the electronic payment service provider's account. In this case, the deposit unit 150 may notify the merchant via email that the sales proceeds have been deposited into their account. Details regarding the deposit processing of sales proceeds by the deposit unit 150 will be described later.

[0089] When a merchant's sales figures are updated, the Information Management Unit 125 updates the payment history information in the User Information Unit 172. Specifically, the Information Management Unit 125 records the date and time of payment, merchant ID, payment amount, and payment method (account balance payment) in the payment history information fields of the User Information Unit 172. In this way, the Information Management Unit 125 manages not only the payment history of electronic money balances and credit card payments, but also the payment history of account balance payments.

[0090] The screen generation unit 135 of the payment server 100 generates a payment completion screen when the account balance payment is completed and sends a payment completion notification including the payment completion screen to the financial institution application 30 (S112). The financial institution application 30 displays the payment completion screen via the payment SDK 31.

[0091] Figure 18 shows an example of the IM7 payment completion screen for account balance payments. As shown in Figure 18, the IM7 payment completion screen displays the name of the merchant (○○ Convenience Store), the name of the store (□□ Station Front Store), the payment date and time (May 5, 2025, 15:15:15), the payment amount (1000 yen), the points to be awarded (10 points), the breakdown of the account balance payment (points: 500 yen, account balance: 500 yen), the payment amount (1000 yen), the payment number (0123456789...), and the payment method (points, account balance).

[0092] For example, in S107, the screen generation unit 135 of the payment server 100 obtains the merchant ID, store ID, and payment amount from the first store terminal device 50. The screen generation unit 135 also generates a payment completion screen IM7 which includes the name of the merchant indicated by the merchant ID, the name of the store indicated by the store ID, the breakdown of the account balance payment, and the payment amount. The payment completion screen IM7 is displayed on the display unit of the user terminal device 10. This allows the user to understand that the account balance payment has been completed.

[0093] As described above, in the store scan-based account balance settlement of this embodiment, the settlement processing unit 120 obtains settlement information, including the settlement amount for the product the user intends to purchase, from the first store terminal device 50, and sends an account balance settlement request, including the settlement amount and an account ID for identifying the user, to the financial institution server 200 with which the account linkage has been established, thereby causing the financial institution server 200 to perform account balance settlement using the user's account balance. This allows the user to use the financial institution's account balance settlement, improving convenience for the user.

[0094] [Account balance settlement via user scan] Figure 19 is a sequence diagram showing an example of account balance settlement via user scan. First, the user selects (tap) the payment button B2 from the home screen IM2 of the financial institution app 30 (S201). As mentioned above, the payment button B2 is a button that instructs the user to settle the account balance using their account balance.

[0095] Next, the financial institution application 30 executes the payment SDK 31. The payment SDK 31 is a program that has at least some of the functions of the payment application 20. The payment SDK 31 displays the aforementioned payment screen IM6 (Figure 16) on the display unit of the user terminal device 10. When the button B9 displayed on the payment screen IM6 is selected (tapped) by the user, the payment SDK 31 displays a code reading screen (not shown) on the display unit of the user terminal device 10.

[0096] When the user takes a picture of the store code image 60 from the code reading screen, the payment SDK 31 reads and decodes the store code image 60 using the optical reading function of the user terminal device 10 (S202). As mentioned above, the store code image 60 contains the store URL. The payment SDK 31 sends the first payment information, including the store URL and account ID, to the payment server 100 (S203).

[0097] The payment server 100 refers to the merchant / store information 176 and retrieves the merchant ID and store ID corresponding to the store URL from the first table 176A. The payment server 100 also retrieves the merchant name corresponding to the merchant ID from the second table 176B and the store name corresponding to the store ID from the third table 176C (S204). Subsequently, the payment server 100 sends the merchant name and store name to the financial institution application 30 (S205).

[0098] The user enters the payment amount into the user terminal device 10 on a screen displaying the merchant name or store name (S206). The payment SDK 31 embedded in the financial institution application 30 generates second payment information, including at least the payment amount, and sends it to the payment server 100 (S207).

[0099] The settlement server 100 sends an account balance settlement request to the financial institution server 200 based on the received second settlement information (S208). The account balance settlement request includes the user's account ID, the settlement amount, and the merchant ID.

[0100] Note that the processing in S209-S212 in Figure 19 is the same as the processing in S109-S112 in Figure 17, so the explanation is omitted. Based on the payment completion notification received in S212, the financial institution application 30 displays the payment completion screen IM7 (Figure 18) via the payment SDK 31.

[0101] For example, the screen generation unit 135 of the payment server 100 obtains the merchant ID, store ID, and payment amount based on the store URL obtained from the user terminal device 10 (financial institution application 30) in S203. The screen generation unit 135 also generates a payment completion screen that includes the name of the merchant indicated by the merchant ID, the name of the store indicated by the store ID, the breakdown of the account balance payment, and the payment amount. The payment completion screen is displayed on the display unit of the user terminal device 10. This allows the user to understand that the account balance payment has been completed.

[0102] In the case of the user scan shown in Figure 19, the financial institution application 30 may determine whether or not payment is possible. Specifically, the financial institution application 30 may obtain the deposit balance of the user's bank account from the financial institution server 200 in response to the payment amount entered in S206, and determine whether or not payment is possible based on the payment amount and the deposit balance of the user's bank account. Alternatively, the financial institution application 30 may obtain the account balance payment limit and the account balance payment usage amount from the financial institution server 200, and determine whether or not payment is possible based on the payment amount and the account balance payment usage amount (the amount obtained by subtracting the account balance payment usage amount from the account balance payment limit). Furthermore, if the financial institution application 30 determines that payment is not possible, it may display a message via the payment SDK 31 indicating that account balance payment cannot be performed.

[0103] Furthermore, in this embodiment, the financial institution server 200 is assumed to hold the merchant information 274, but this is not limited to this. For example, the financial institution server 200 may not hold the merchant information 274, and the settlement server 100 may send the account balance settlement, including the merchant name instead of the merchant ID, to the financial institution server 200 in S108 of Figure 17 and S208 of Figure 19. Alternatively, the information management unit 240 of the financial institution server 200 may record the merchant name and settlement amount included in the account balance settlement in the transaction history information linked to the user's account information (branch number, account number, etc.) in the account information 272. This eliminates the need to store the merchant information 274 in the storage unit 270, thus reducing the storage capacity of the storage unit 270.

[0104] As described above, in the user scan-based account balance settlement of this embodiment, the settlement processing unit 120 obtains settlement information, including the settlement amount of the product the user intends to purchase, from the user terminal device 10 (the settlement SDK 31 of the financial institution application 30), and sends an account balance settlement request, including the settlement amount and account information for identifying the user, to the financial institution server 200, thereby causing the financial institution server 200 to perform account balance settlement using the user's account balance. This allows the user to use the financial institution's account balance settlement, improving convenience for the user.

[0105] [Transaction History] Next, we will explain the transaction history of the user's account. As mentioned above, the information management unit 125 of the settlement server 100 manages not only the settlement history of electronic payments but also the settlement history of account balance payments in the settlement history information item of the user information 172. When button B10 on the settlement screen IM6 (Figure 16) is selected (tapped) by the user, the screen generation unit 135 generates a transaction history screen IM8 in which the settlement method is limited to account balance payments, based on the transaction history information contained in the user information 172. This point will be explained below.

[0106] Figure 20 shows an example of the transaction history screen IM8. The transaction history screen IM8 displays the transaction history of the user's account. As shown in Figure 20, the transaction history screen IM8 includes the merchant name, store name, settlement date and time, settlement method, and settlement amount for each account balance settlement. Users can view all transaction history by swiping up and down to scroll the screen on the transaction history screen IM8.

[0107] As mentioned above, the user terminal device 10 has the payment application 20 and the financial institution application 30 installed. When button B10 on the payment screen IM6 (Figure 16) is selected (tapped) by the user, the payment SDK 31 sends a request to the payment server 100 to generate a transaction history screen. As mentioned above, the payment SDK 31 is a program that has at least some of the functions of the payment application 20 and is incorporated into the financial institution application 30. When the screen generation unit 135 of the payment server 100 receives the request to generate a transaction history screen from the payment SDK 31, it generates a transaction history screen IM8, in which the payment method is limited to account balance payment, based on the transaction history information contained in the user information 172, and sends it to the user terminal device 10. The financial institution application 30 installed on the user terminal device 10 displays the transaction history screen IM8 via the payment SDK 31. This allows the user to check the transaction history of their financial institution account.

[0108] The screen generation unit 135 may generate a transaction history screen that includes information indicating which application, the payment application 20 (first application) or the financial institution application 30 (second application), was used to settle the account balance. This allows the user to easily understand which application was used to settle the account balance. For example, the transaction history screen IM8 shown in Figure 20 is a screen where the settlement method is limited to account balance settlement, and therefore displays "△△ Bank application". This allows the user to easily understand that the account balance settlement was made via the financial institution application 30 (second application).

[0109] Furthermore, in response to the user selecting (tapping) any transaction history included in the transaction history screen IM8, the financial institution app 30 may display the aforementioned settlement completion screen IM7 (Figure 18). Specifically, the financial institution app 30 may obtain and display the settlement completion screen IM7 from the settlement server 100 via the settlement SDK 31. Alternatively, the financial institution app 30 may launch the settlement app 20 and display the settlement completion screen without using the settlement SDK 31. This allows the user to check the details of the account balance settlement by operating the transaction history screen IM8.

[0110] As mentioned above, the payment application 20 as the first application and the financial institution application 30 as the second application are installed on the user terminal device 10. Furthermore, when the payment SDK 31 is executed in the financial institution application 30, the screen generation unit 135 generates a transaction history screen IM8 in response to a request from the payment SDK 31, with the payment method limited to account balance payment, and sends the transaction history screen IM8 to the financial institution application 30 for display. This allows the user to easily check the transaction history related to account balance payment from the financial institution application 30.

[0111] In this embodiment, a payment application 20 as the first application and a financial institution application 30 as the second application are installed on the user terminal device 10, but this is not limited to this. For example, a merchant application (hereinafter referred to as the merchant application) for purchasing goods from merchants of the electronic payment service via the internet may be installed on the user terminal device 10 as the second application. The merchant application may also incorporate a payment SDK, which is a program having at least some of the functions of the payment application 20. Furthermore, when the payment SDK is executed in the merchant application, the screen generation unit 135 may, in response to a request from the payment SDK, generate a transaction history screen limited to the user's payment method set in the user information 172, and send the transaction history screen to the merchant application for display. This allows the user to easily check the transaction history of the user's pre-set payment method from the merchant application.

[0112] As explained above, the settlement processing unit 120 obtains settlement information, including the settlement amount of the goods that the user intends to purchase, via the first application (payment app 20) or the second application (financial institution app, merchant app), and performs electronic settlement based on the settlement information. When the screen generation unit 135 receives a request from the second application to generate a transaction history screen that displays the transaction history of electronic settlements, it generates a transaction history screen IM8 that is limited to settlement methods according to the type of program (settlement SDK) executed in the second application, and sends the transaction history screen IM8 to the second application for display. For example, when the settlement SDK 31 for the financial institution app 30 is executed, the screen generation unit 135 may generate a transaction history screen limited to account balance settlements. This is because the financial institution app 30 is an application that uses account balance settlements. On the other hand, when the settlement SDK for the merchant app is executed, the screen generation unit 135 may generate a transaction history screen that is limited to the user's pre-configured settlement method. This is because in the merchant app, electronic settlements are performed using the user's pre-configured settlement method. This allows users to easily check their transaction history, even when electronic payments are made using multiple payment methods.

[0113] In this embodiment, the multiple payment methods performed by the payment processing unit 120 may include two or more of the following: payment using electronic money balance, payment using a credit card provided by a credit card company that collaborates with the electronic payment service, and payment using the user's account balance at a financial institution that collaborates with the electronic payment service.

[0114] Furthermore, the first application (payment app 20) may allow users to select from multiple payment methods, while the second application (financial institution app, merchant app) may limit users to only one of the multiple payment methods.

[0115] Furthermore, the transaction history screen IM8, which is limited to payment methods corresponding to the type of program (payment SDK) executed in the second application (financial institution app, merchant app), may also include the history of electronic payments made using payment methods corresponding to the type of program (payment SDK) among the electronic payments based on payment information obtained via the first application.

[0116] Furthermore, the coupon acquisition unit 140 may execute a process to acquire coupons that can only be used for account balance settlements, in response to a coupon acquisition instruction from the financial institution app 30. This is because the financial institution app 30 allows the use of coupons that can only be used for account balance settlements. The coupon acquisition unit 140 records information about the acquired coupons in the coupon information item in the user information 172. This makes it easy for users to acquire coupons that suit their purpose.

[0117] Furthermore, the coupon acquisition unit 140 may, in response to a coupon acquisition instruction from the merchant app, execute a process to acquire coupons that can only be used with the user's pre-configured payment method. This is because electronic payment is made from the merchant app using the user's pre-configured payment method. This makes it easy for users to acquire coupons that suit their needs.

[0118] [Account balance top-up process] Next, the process of charging the user's account balance will be explained. In this embodiment, it is possible to charge not only the user's electronic money balance but also the user's account balance. When button B11 on the payment screen IM6 (Figure 16) is selected (tapped) by the user, the screen generation unit 135 of the payment server 100 generates a charge screen IM9 fixed to charge the user's account balance, based on the user information 172. This point will be explained below.

[0119] Figure 21 shows an example of the charge screen IM9. The charge screen IM9 is a screen for entering information regarding adding funds to the user's account balance. As shown in Figure 21, the charge screen IM9 includes areas A10 to A13 and button B12, among others.

[0120] Area A10 displays the charge amount entered by the user. The user may enter the charge amount using the buttons displayed in Area A11 (such as "+1000", "+5000", "+10000", etc.) or the numeric keypad displayed in Area A13. In the example shown in Figure 21, the charge amount (5000 yen) is displayed in Area A10.

[0121] Area A12 displays information about the user's bank account used for topping up the account balance. In the example shown in Figure 21, the information about the user's bank account includes the bank name (△△ Bank), branch name (×× Branch), account type (savings), and the last four digits of the account number (1234).

[0122] Furthermore, users may register multiple bank accounts in the user information 172 of the payment server 100. Also, when a user selects (taps) area A12, the payment SDK 31 may display a screen listing the multiple bank accounts held by the user. This allows the payment SDK 31 to prompt the user to select a bank account to be used for charging the account balance.

[0123] As mentioned above, area A13 displays a numeric keypad used for entering the charge amount. Additionally, button B12 is displayed between areas A12 and A13. When the user enters the charge amount in area A10 and then selects (taps) button B12, the payment SDK 31 sends a charge instruction to the payment server 100. This point will be explained below.

[0124] Figure 22 is a sequence diagram showing an example of the account balance charge process. First, when the user selects (taps) the payment button B2 from the home screen IM2 (Figure 12), the financial institution application 30 executes the payment SDK 31 to obtain and display the account balance payment screen IM6 (Figure 16) from the payment server 100. As mentioned above, the payment SDK 31 is a program that has at least some of the functions of the payment application 20. When the user selects (taps) the button B11 from the payment screen IM6, the payment SDK 31 obtains and displays the charge screen IM9 (Figure 21) from the payment server 100 (S301).

[0125] The user enters the charge amount in area A10 of the charge screen IM9 and selects the source account information from area A12 of the charge screen IM9. Then, when the user presses button B12 on the charge screen IM9, the payment SDK 31 retrieves the charge amount entered in area A10 of the charge screen IM9 (S302) and retrieves the source account information selected from area A12 of the charge screen IM9 (S303).

[0126] Next, the financial institution app 30 sends a charge instruction to the payment server 100 via the payment SDK 31 (S304). The charge instruction includes the user's account ID, the charge amount, and the account information of the source of the charge.

[0127] The charge processing unit 145 of the payment server 100 obtains the user's account information for charging based on the charge instruction received from the financial institution application 30 (S305). Specifically, the account information for account balance settlement is registered in the "Bank Account" item of the user information 172. The charge processing unit 145 obtains the account information for account balance settlement linked to the user's account ID included in the charge instruction from the user information 172 as the account information for charging.

[0128] Next, the charge processing unit 145 controls the communication unit 110 to send a transfer request to the financial institution server 200 (hereinafter referred to as the first financial institution server 200) which manages the account information of the charge source (S306). The transfer request includes the charge amount, the user's account information of the charge source, and the account information of the electronic payment service provider.

[0129] The transfer processing unit 230 of the first financial institution server 200 executes the transfer process based on the transfer request sent from the settlement server 100 (S307). Specifically, the transfer processing unit 230 transfers the charge amount from the user's source account (first account) to the electronic payment service provider's account (second account) based on the charge amount included in the transfer request, the user's source account information, and the electronic payment service provider's account information. This allows the charge amount to be temporarily transferred to the electronic payment service provider's account. Subsequently, the transfer processing unit 230 sends a transfer completion notification to the settlement server 100 (S308).

[0130] Next, the charge processing unit 145 controls the communication unit 110 to send a transfer request to the financial institution server 200 (hereinafter referred to as the second financial institution server 200) which manages the account information of the electronic payment service provider (S309). The transfer request includes the charge amount, the account information of the electronic payment service provider, and the account information of the user to which the charge is to be made.

[0131] The transfer processing unit 230 of the second financial institution server 200 executes the transfer process based on the transfer request sent from the settlement server 100 (S310). Specifically, the transfer processing unit 230 transfers the charge amount from the electronic payment service provider's account (second account) to the user's account (third account) based on the charge amount included in the transfer request, the electronic payment service provider's account information, and the user's account information for the account to which the charge is to be made.

[0132] Furthermore, the user's source account for charging (Account 1) is the same account used to charge electronic money to the user's account in the electronic payment service, and the user's destination account for charging (Account 3) is the same account used for settling the user's account balance. More specifically, the user's source account for charging (Account 1) is the account that the user has previously registered with the electronic payment service as the source for charging electronic money, and the user's destination account for charging (Account 3) is the account that the user has registered as the bank account to be used for settling the account balance provided by the electronic payment service. This allows the user to charge cash to their account balance settlement account using their electronic money charging account. Subsequently, the transfer processing unit 230 sends a transfer completion notification to the settlement server 100 (S311).

[0133] Next, the information management unit 125 of the payment server 100 updates the charge history information in the user information 172 in response to the transfer completion notification (S312). Specifically, the information management unit 125 records the date and time of the charge, the charge amount, etc., in the charge history information of the user information 172. This completes the account balance charge process.

[0134] The screen generation unit 135 of the payment server 100 generates a charge completion screen (not shown) when the account balance charge process is completed, and sends a charge completion notification including the charge completion screen to the financial institution application 30 (S313). The financial institution application 30 displays the charge completion screen via the payment SDK 31.

[0135] In this way, the charge processing unit 145 of the payment server 100 sends a transfer request to the financial institution server 200 with which the account has been linked, causing the financial institution server 200 to perform the charge processing. This allows funds to be charged to the user's account balance at the financial institution.

[0136] The payment server 100 can communicate with the user terminal device 10, which has a first application (payment app 20) and a second application (financial institution app 30 or merchant app) installed, which incorporates a program (payment SDK 31) having at least some of the functions of the first application. The screen generation unit 135 may generate a charge screen fixed to the charge type according to the type of program (payment SDK) executed in the second application. For example, if the program executed in the second application is the payment SDK 31 for the financial institution app 30, a charge screen IM9 fixed to charging the user's account balance may be generated. On the other hand, if the program executed in the second application is the payment SDK for the merchant app, a charge screen fixed to charging the user's electronic money balance may be generated. This allows the charge process to be performed with the appropriate charge type.

[0137] In other words, when the settlement SDK 31 is executed in the financial institution application 30 (second application), the screen generation unit 135 may, in response to a request from the settlement SDK 31, generate a charge screen IM9 fixed to charging the user's account balance, and send the charge screen IM9 to the financial institution application 30 for display. This allows the user to easily charge funds to be used for account balance settlements into their account.

[0138] On the other hand, when the payment SDK is executed in the merchant app (second application), the screen generation unit 135 may, in response to a request from the payment SDK, generate a charge screen fixed to charging the user's electronic money balance, and send the charge screen to the merchant app for display. This allows the user to easily charge the electronic money to be used for electronic payments into their account.

[0139] The payment server 100 may also control the system so that when a user runs the payment application 20 (first application) on the user terminal device 10, the payment application 20 can either charge the electronic money balance or the account balance. For example, the screen generation unit 135 of the payment server 100 may generate a home screen IM1 that displays both a button to instruct the user to charge the electronic money balance and a button to instruct the user to charge the account balance, and display this screen on the payment application 20. Alternatively, the screen generation unit 135 may generate a home screen IM1 that displays the button to instruct the user to charge the electronic money balance, but does not display the button to instruct the user to charge the account balance, and display this screen on the payment application 20.

[0140] Furthermore, the payment server 100 may control the screen of the payment application 20 (first application) depending on whether the user has enabled account balance payment. For example, if the user has enabled account balance payment, the screen generation unit 135 of the payment server 100 may generate a home screen IM1 that displays both a button to instruct the user to charge their electronic money balance and a button to instruct the user to charge their account balance, and display this screen on the payment application 20. On the other hand, if the user has not enabled account balance payment, the screen generation unit 135 may generate a home screen IM1 that displays a button to instruct the user to charge their electronic money balance, but does not display a button to instruct the user to charge their account balance, and display this screen on the payment application 20.

[0141] As explained above, the charge processing unit 145 causes the servers of the first and second financial institutions to perform a charge process to transfer the charge amount from the first account, which is the user's account at the first financial institution, to the third account, which is the user's account at the second financial institution, via the second account, which is the account of the electronic payment service provider at the second financial institution. This makes it possible to charge funds to the user's account at the financial institution.

[0142] Furthermore, the information management unit 125 may manage separately, in user information 172, first account information containing multiple account information used to charge the user's account balance and second account information containing multiple account information used to charge the user's electronic money balance, and may also manage each of the multiple account information by associating a priority with it. In addition, the screen generation unit 135 may prioritize the display of account information with a higher priority on the charge screen IM9. For example, the screen generation unit 135 may display the account information with the highest priority among the multiple account information in area A12 of the charge screen IM9. Also, if the user selects (tap) area A12, the screen generation unit 135 may generate an account information selection screen (not shown) in which the multiple account information is sorted in order of priority, and send the account information selection screen to the user terminal device 10 for display. This makes it easier for the user to select account information with a higher priority.

[0143] Furthermore, the screen generation unit 135 may generate a cumulative charge plan screen (not shown) that includes the cumulative charge amount over a certain period for each of the user's source account information used for charging, and send the cumulative charge plan screen to the financial institution application 30 for display. This allows users to understand how much of each of the multiple source account information has been used for charging, even if they have multiple source account information.

[0144] In this embodiment, the charge processing for the account balance is performed by charging the charge amount from the user's source account to the user's destination account, but this is not limited to this. For example, the charge processing unit 145 of the payment server 100 may charge the charge amount to the user's account using the user's electronic money. Specifically, when the charge processing unit 145 charges the charge amount to the user's account using the user's electronic money, it may send a transfer request to the financial institution server 200 that includes the charge amount, the account information of the electronic payment service provider, and the account information of the user's destination account. The transfer processing unit 230 of the financial institution server 200 may, based on the transfer request from the payment server 100, transfer the charge amount from the account of the electronic payment service provider to the user's destination account and send a transfer completion notification to the payment server 100. The information management unit 125 of the payment server 100 may also deduct the charge amount from the user's electronic money balance in the user information 172 in response to the transfer completion notification. This allows users to use their existing electronic money to top up their account.

[0145] Furthermore, in this embodiment, charging is performed to the user's account from the charge screen IM9 of the financial institution app 30, but this is not limited to this. For example, it may be possible to charge the user's account from the payment app 20. Specifically, the user may set the payment method to "account balance" from the home screen IM1 of the payment app 20, and then select (tap) the "charge" button from area A2. After that, the screen generation unit 135 may generate a screen similar to the charge screen IM9 and display it in the payment app 20. This allows charging not only from the financial institution app 30 but also from the payment app 20, thereby improving convenience for the user.

[0146] [Processing of sales revenue deposit] The payment processing unit 120 processes electronic payments using multiple payment methods (e.g., electronic money balance, credit card payment, bank account balance). The information management unit 125 manages sales revenue for each electronic payment method for each merchant of the electronic payment service in the merchant wallet information 178 (Figure 7). The deposit unit 150 deposits sales revenue into the merchant's account at different timings depending on the electronic payment method. This allows merchants of the electronic payment service to receive sales revenue for each electronic payment method at any time they choose.

[0147] Specifically, the deposit unit 150 deposits sales proceeds from account balance payments into the merchant's account at an earlier time than sales proceeds from other payment methods (electronic money balance, credit card payments). For example, the deposit unit 150 may deposit sales proceeds from account balance payments into the merchant's account immediately, and sales proceeds from other payment methods into the merchant's account on a predetermined date each month (for example, the 1st). This allows merchants of electronic payment services to receive sales proceeds faster when account balance payments are made than when electronic payments are made using other payment methods.

[0148] Furthermore, if the merchant has registered an account at a financial institution designated by the electronic payment service provider as an account for receiving sales proceeds, the deposit unit 150 may allow the deposit of sales proceeds by account balance settlement to the merchant's account earlier than sales proceeds by other payment methods. On the other hand, if the merchant has not registered an account at a financial institution designated by the electronic payment service provider as an account for receiving sales proceeds, the deposit unit 150 may prohibit the deposit of sales proceeds by account balance settlement to the merchant's account earlier than sales proceeds by other payment methods. This can increase the number of accounts opened at financial institutions designated by electronic payment service providers.

[0149] Furthermore, the screen generation unit 135 may generate a sales confirmation screen (not shown) that displays sales for each payment method, and transmit the sales confirmation screen to a second store terminal device 70 used by the merchant operator for display. Specifically, the screen generation unit 135 may generate a sales confirmation screen that distinguishes between sales made by account balance settlement and sales made by other payment methods. This allows the merchant operator to easily grasp sales for each payment method.

[0150] Furthermore, the screen generation unit 135 may generate a sales confirmation screen (not shown) for each electronic payment method, which displays the sales for the current month, the amount already deposited into the merchant's account, and the amount not yet deposited into the merchant's account. This sales confirmation screen may then be transmitted to the second store terminal device 70 for display. This allows the merchant operator to easily grasp the sales for the current month, the amount already deposited into the merchant's account, and the amount not yet deposited into the merchant's account.

[0151] As described above, the payment system of this embodiment comprises a financial institution server 200 and a payment server 100. The first financial institution server 200, which is the source of the charge, is a server that manages accounts at the first financial institution. The second financial institution server 200, which is the destination of the charge, is a server that manages accounts at the second financial institution. The payment server 100 is a server that performs electronic payments in an electronic payment service and can communicate with the first and second financial institution servers 200. The payment server 100 includes a charge processing unit 145. The charge processing unit 145 causes the first and second financial institution servers 200 to perform a charge process to transfer the charge amount from the first account, which is the user's account at the first financial institution, to the third account, which is the user's account at the second financial institution, via the second account, which is the account of the electronic payment service provider at the second financial institution. This allows the user to charge funds to their account for use in settling their account balance.

[0152] In addition, in the user scan of this embodiment, the payment information may include a payment method (for example, electronic money balance, credit card payment, or account balance), and the payment processing unit 120 may perform electronic payment using the payment method included in the payment information.

[0153] Furthermore, in the store scan of this embodiment, the payment processing unit 120 may generate a one-time code that links the payment method set by the user with the user's account ID. When the payment processing unit 120 receives payment information including the one-time code from the first store terminal device 50, it may perform electronic payment using the payment method linked to the one-time code included in the payment information.

[0154] Furthermore, the payment processing unit 120 may change the one-time code in response to a change in the payment method by the user, and may send the changed one-time code to the user terminal device 10 (payment app 20, financial institution app 30) to display a code image based on the one-time code.

[0155] Furthermore, when the settlement processing unit 120 receives settlement information from a second application (financial institution application 30, merchant application), it may generate a one-time code associated with a settlement method corresponding to the type of program (settlement SDK) executed by the second application. For example, when the settlement SDK 31 for the financial institution application 30 is executed, the settlement processing unit 120 may generate a one-time code associated with "account balance settlement" as the settlement method. Also, if the settlement processing unit 120 determines that the settlement method associated with the one-time code included in the received settlement information is "account balance settlement," it may send an account balance settlement request to the financial institution server 200 to perform the account balance settlement.

[0156] The above explanation uses the example of a financial institution being a bank, but it is not limited to this. For example, the financial institution may be a securities company. In this case, the account balance settlement processing unit 220 may settle the account balance using the deposit balance of the securities account. The securities account may be an account for an MRF (Money Reserve Fund). This allows the deposit balance of the securities account to be used for account balance settlement.

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

[0158] 10. User terminal device 20 Payment Apps 30 Financial Institution Apps 31 Payment SDK 50. First store terminal device 70. Second store terminal device 100 Payment Servers 110 Communications Department 115 Payment Content Provision Department 120 Payment Processing Unit 125 Information Management Department 130 Account Linking Department 135 Screen generation section 140 Coupon Acquisition Section 145 Charging Processing Unit 150 Deposit Section 170 Storage section 200 Financial Institution Servers 210 Communications Department 220 Account Balance Settlement Processing Unit 230 Transfer Processing Unit 240 Information Management Department 250 Account Linking Department 270 Storage section

Claims

1. A settlement server that performs electronic payments in an electronic payment service, which is capable of communicating with a first financial institution server that manages accounts at a first financial institution and a second financial institution server that manages accounts at a second financial institution, The system includes a charge processing unit that causes the servers of the first and second financial institutions to perform a charge processing to transfer a charge amount from a first account, which is the user's account at the first financial institution, to a third account, which is the user's account at the second financial institution, via a second account, which is the electronic payment service provider's account at the second financial institution. Payment server.

2. The aforementioned charge processing unit, By sending a first transfer request including the charge amount, the account information of the first account, and the account information of the second account to the first financial institution server, the first financial institution server will transfer the charge amount from the first account to the second account. By sending a second transfer request, including the charge amount, the account information of the second account, and the account information of the third account, to the second financial institution server, the second financial institution server is instructed to transfer the charge amount from the second account to the third account. The settlement server according to claim 1.

3. The system further includes a settlement processing unit that transmits an account balance settlement request to the second financial institution server, which includes the payment amount for the goods the user intends to purchase and user identification information for identifying the user, thereby causing the second financial institution server to perform an account balance settlement using the user's account balance. The settlement server according to claim 1.

4. The first account is the same account used to charge electronic money to the user's account in the electronic payment service, The aforementioned third account is the same account used for settling the user's account balance. The settlement server according to claim 3.

5. The first account is an account that the user has previously registered with the electronic payment service as the source for charging electronic money. The third account is an account registered by the user as a bank account to be used for settling the account balance provided by the electronic payment service. The settlement server according to claim 4.

6. The payment server is capable of communicating with a user terminal device on which a first application and a second application, which incorporates a program having at least some of the functions of the first application, are installed. The second application further comprises a screen generation unit that generates a charge screen fixed to a charge type corresponding to the type of program executed in the second application, The settlement server according to claim 3.

7. The first application is a payment application for using the electronic payment service, The second application is a financial institution application for using financial services provided by the second financial institution, When the program is executed in the financial institution application, the screen generation unit generates the charge screen, which is fixed to charge the user's account balance, in response to a request from the program, and sends the charge screen to the financial institution application for display. The settlement server according to claim 6.

8. The first application is a payment application for using the electronic payment service, The second application is a merchant application for purchasing goods from merchants of the electronic payment service via the internet. When the program is executed in the merchant application, the screen generation unit generates the charge screen, which is fixed to charge the user's electronic money balance, in response to a request from the program, and sends the charge screen to the merchant application for display. The settlement server according to claim 6.

9. The system further includes an information management unit that separately manages first account information, which includes multiple account information used to charge the user's account balance, and second account information, which includes multiple account information used to charge the user's electronic money balance, and that manages each of the multiple account information by associating a priority with it. The screen generation unit, in the charge screen, prioritizes displaying the account information with the highest priority. The settlement server according to claim 7 or claim 8.

10. The charge processing unit receives a charge instruction from the second application, which includes the user identification information, the charge amount entered on the charge screen, and the account information selected from the charge screen. The settlement server according to claim 9.

11. The screen generation unit generates a cumulative charge plan screen for each of the first accounts used in the charge process, including the cumulative charge amount over a certain period, and transmits the cumulative charge plan screen to the financial institution application for display. The settlement server according to claim 7.

12. The system further includes an account linking unit that performs account linking between the settlement server and the second financial institution server. The charge processing unit sends the second transfer request to the second financial institution server with which the account linkage has been established, thereby causing the second financial institution server to transfer the charge amount from the second account to the third account. The settlement server according to claim 2.

13. When the charge processing unit charges the user's account using the user's electronic money, it sends a transfer request to the second financial institution server including the charge amount, the account information of the second account, and the account information of the third account, thereby causing the second financial institution server to perform a charge process to transfer the charge amount from the second account to the third account, and also deducts the charge amount from the user's electronic money balance. The settlement server according to claim 1.

14. The first financial institution server manages accounts at the first financial institution, The second financial institution server manages accounts at the second financial institution, A settlement server that performs electronic payments in an electronic payment service and is capable of communicating with the first financial institution server and the second financial institution server, A payment system that includes, The premium payment server is The system includes a charge processing unit that causes the servers of the first and second financial institutions to perform a charge processing to transfer a charge amount from a first account, which is the user's account at the first financial institution, to a third account, which is the user's account at the second financial institution, via a second account, which is the electronic payment service provider's account at the second financial institution. Payment system.

15. A settlement server that performs electronic payments in an electronic payment service, which is capable of communicating with the first financial institution server that manages accounts at the first financial institution and the second financial institution server that manages accounts at the second financial institution, The first financial institution server and the second financial institution server are instructed to perform a charge process to transfer the charge amount from the first account, which is the user's account at the first financial institution, to the third account, which is the user's account at the second financial institution, via the second account, which is the electronic payment service provider's account at the second financial institution. How to control the payment server.

16. A settlement server that performs electronic payments in an electronic payment service, which is capable of communicating with the first financial institution server that manages accounts at the first financial institution and the second financial institution server that manages accounts at the second financial institution, A process to cause the servers of the first and second financial institutions to perform a charge process to transfer a charge amount from the first account, which is the user's account at the first financial institution, to the third account, which is the user's account at the second financial institution, via the second account, which is the electronic payment service provider's account at the second financial institution, and A program that executes the command.

Citation Information

Patent Citations

  • Electronic payment system, electronic payment method, and program

    JP2022157339A