Settlement system, display control method and program

Abstract

To provide a settlement system for improving convenience of users in settlement services.SOLUTION: A display request reception unit (101) of a settlement system (1) receives a display request of a selection screen for a user to select a function relating to a settlement service. When the display request is received, a status information acquisition unit (102) acquires status information of status of identity verification of the user. A display control unit (103) displays the status on the selection screen based on the status information.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present disclosure relates to a payment system, a display control method, and a program. [Background technology]

[0002] Conventionally, payment services that require users to verify their identity have been known. For example, Patent Document 1 describes a service management system that, when a user starts a transaction for another service while logged in to the payment service, performs screening and procedures at the start of the transaction for the other service based on status information regarding the status of identity verification in the payment service (for example, whether identity verification has been completed). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7280419 Summary of the Invention [Problem to be solved by the invention]

[0004] For example, with the technology of Patent Document 1, a user can learn that the identity verification status of a payment service is available after actually starting the procedure to start a transaction for another service. However, with the technology of Patent Document 1, a user cannot learn this fact before starting the procedure. This is not limited to when starting a transaction for another service as in Patent Document 1, but also applies when a user selects a function related to a payment service. For this reason, conventional technologies have not been able to sufficiently improve user convenience.

[0005] One of the purposes of the present disclosure is to improve user convenience in payment services. [Means for solving the problem]

[0006] The payment system of the present disclosure includes a display request receiving unit that receives a request to display a selection screen for a user to select functions related to a payment service, a status information acquisition unit that acquires status information related to the user's identity verification status when the display request is accepted, and a display control unit that displays the status on the selection screen based on the status information. [Effects of the Invention]

[0007] The present disclosure can improve user convenience in payment services. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 2 is a diagram illustrating an example of a hardware configuration of a payment system. [Figure 2] FIG. 10 is a diagram illustrating an example of a screen displayed on a user terminal. [Figure 3] FIG. 10 is a diagram illustrating an example of a screen displayed on a user terminal. [Figure 4] FIG. 10 is a diagram illustrating an example of a screen displayed on a user terminal. [Figure 5] FIG. 1 is a diagram illustrating an example of functions implemented in a payment system. [Figure 6] FIG. 2 is a diagram illustrating an example of a user database. [Figure 7] FIG. 10 is a diagram illustrating an example of processing executed in the payment system. [Figure 8] FIG. 10 is a diagram illustrating an example of a function realized in a modified example. [Figure 9] FIG. 10 is a diagram showing an example of a screen displayed on a user terminal in Modification 1. [Figure 10] FIG. 19 is a diagram showing an example of a selection screen of Modification 8. [Figure 11] FIG. 20 is a diagram showing an example of a selection screen of Modified Example 9. DETAILED DESCRIPTION OF THE INVENTION

[0009] [1. Payment system hardware configuration] An example of an embodiment of a payment system, a display control method, and a program according to the present disclosure will be described. Fig. 1 is a diagram showing an example of the hardware configuration of a payment system. For example, the payment system 1 includes a payment server 10, a linked server 20, and a user terminal 30. Each of the payment server 10, the linked server 20, and the user terminal 30 is connected to a network N such as the Internet or a LAN.

[0010] The payment server 10 is a server computer for a payment service. The payment service is a service that provides users with electronic payments (cashless payments). For example, the payment server 10 includes a control unit 11, a memory unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The memory unit 12 includes at least one of a volatile memory such as RAM and a non-volatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0011] The linked server 20 is a server computer of an external service that links with the payment service. In this embodiment, the external service is a service that provides users with electronic payments using their bank accounts. The external service can also be a payment service other than the payment service provided by the payment server 10. In this embodiment, the term "payment service" refers not to the external service but to the payment service provided by the payment server 10. Although the example given here is one in which the operator operating the payment service and the operator operating the external service are different, these operators may be the same. For example, the linked server 20 includes a control unit 21, a memory unit 22, and a communication unit 23. The hardware configurations of the control unit 21, the memory unit 22, and the communication unit 23 may be the same as those of the control unit 11, the memory unit 12, and the communication unit 13, respectively.

[0012] The user terminal 30 is a user's computer. For example, the user terminal 30 is a smartphone, a tablet, a personal computer, or a wearable terminal. The user terminal 30 includes a control unit 31, a memory unit 32, a communication unit 33, an operation unit 34, a display unit 35, and an imaging unit 36. The hardware configurations of the control unit 31, the memory unit 32, and the communication unit 33 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The operation unit 34 is an input device such as a touch panel or a mouse. The display unit 35 is a display such as an LCD or organic EL. The imaging unit 36 includes at least one camera.

[0013] The programs stored in the storage units 12, 22, and 32 may be supplied to the payment server 10, the linked server 20, or the user terminal 30 via the network N. Furthermore, at least one of a reading unit (e.g., a memory card slot) that reads a computer-readable information storage medium and an input / output unit (e.g., a USB port) that inputs and outputs data to and from an external device may be included in the payment server 10, the linked server 20, or the user terminal 30. For example, a program stored in an information storage medium may be supplied to the payment server 10, the linked server 20, or the user terminal 30 via at least one of the reading unit and the input / output unit.

[0014] Furthermore, the payment system 1 only needs to include at least one computer. The computers included in the payment system 1 are not limited to the example in FIG. 1. For example, the payment system 1 may include only the payment server 10 and the user terminal 30. In this case, the linked server 20 exists outside the payment system 1. The payment system 1 may also include only the payment server 10. In this case, the linked server 20 and the user terminal 30 exist outside the payment system 1. For example, the payment system 1 may include the payment server 10 and another computer not shown in FIG. 1.

[0015] [2. Overview of the payment system] In this embodiment, a user operates a user terminal 30 to use a payment service. The user can use any payment method for the payment service. A payment method is a method used by a user for payment. For example, a payment method may be a credit card, electronic money, points, cryptocurrency, debit card, wallet, account such as a bank account, or other method. Codes such as barcodes or two-dimensional codes are also a means for payment, and therefore correspond to a payment method. A payment method can also be called a payment means, as it may be used for payment.

[0016] In this embodiment, an example is taken of a case where a user makes a payment using a payment app installed on the user terminal 30. The payment app is an application provided by a business operator that operates a payment service. Once the user installs the payment app on the user terminal 30 and registers as a member of the payment service, the user can use the payment service. Once the user has registered as a member and launched the payment app, the user terminal 30 displays the top screen of the payment app on the display unit 35. The top screen is the first screen that is displayed after the payment app is launched. The top screen is sometimes called the first view.

[0017] 2 to 4 are diagrams showing examples of screens displayed on the user terminal 30. For example, when the payment app is launched, as shown in the upper left of FIG. 2, the user terminal 30 displays on the display unit 35 a top screen SC1 including a code C10 generated based on a code ID that can temporarily identify the user. The code C10 is at least one of a barcode and a two-dimensional code. When the code C10 is read at a store that is a member of the payment service, the payment is executed based on the code ID obtained from the code C10.

[0018] In the example of Figure 2, online electronic money called "AAA Cash" is set as the payment source, so payment is made based on the pre-charged electronic money. The payment source is the payment method used for payment. The payment source may be any payment method. For example, the user may be able to register multiple payment methods as potential payment sources. In this case, the user specifies one of the multiple payment methods as the payment source. The user can change the payment source by selecting button B11. Payment based on the payment source specified by the user may be a known process.

[0019] The payment is not limited to the type in which the code C10 displayed on the user terminal 30 is read. The payment may be of any type. For example, the payment may be of the type in which the user terminal 30 reads a code displayed on a terminal in a store, the type in which the user terminal 30 reads a code posted in a store, the type in which the payment is completed only by operating the user terminal 30 (e.g., ID payment or account payment), the type in which an IC chip in the user terminal 30 is used, carrier payment which is payment by the carrier used by the user terminal 30, or any other type.

[0020] For example, the user can change the charge source by selecting button B12. The charge source is the payment method used for charging. The charge source can also be said to be the payment method that is the source of funds for charging. Charging is a process of increasing the balance of a payment method. In this embodiment, an example is given in which electronic money is charged, but the payment method to be charged can be any payment method that has the concept of charging and is not limited to electronic money. For example, charging can be performed on a payment method such as an account. The payment method that can be used as the charge source can also be any payment method.

[0021] For example, when a user selects button B12, the user terminal 30 displays a selection screen SC2 on the display unit 35, which includes a panel P20 for the user to select a charge source, as shown in the upper right of FIG. 2. In the example in the upper right of FIG. 2, a credit card is selected as the charge source, as shown in the top panel P20. By selecting the second panel P20 from the top, the user can register a new credit card and select it as the charge source. By selecting the third panel P20 from the top, the user can register an account at a bank that is an affiliate of the company that operates the payment service and select it as the charge source.

[0022] In this embodiment, a user can set an account at a bank that is not an affiliate of the company that operates the payment service as the charge source. However, processing such as charging using an account at a bank other than the payment service is performed primarily by an external service, not the payment service. Furthermore, in order to use an account at a bank other than the payment service, the user must complete identity verification with the payment service.

[0023] Identity verification is a process for confirming identity. Identity verification is sometimes called authentication. In this embodiment, eKYC (electronic Know Your Customer) is taken as an example of identity verification. In payment services, identity verification other than eKYC (for example, KYC that does not use electronic means) may be performed. Identity verification may be performed using various known methods. Identity verification may involve verifying an identity document such as a driver's license or personal identification number card, or may involve verifying information such as the user's address or telephone number without using an identity document.

[0024] In the example at the top right of FIG. 2, the user has not yet completed identity verification. Therefore, the user terminal 30 displays a message indicating that identity verification has not been completed, such as "identity verification is required for registration," on the bottom panel P20. For example, when the user selects the bottom panel P20, the user terminal 30 displays an identity verification screen SC3 on the display unit 35, which accepts identity verification operations, as shown at the bottom left of FIG. 2. For example, the user terminal 30 activates the photographing unit 36 and photographs the identity verification document.

[0025] In this embodiment, an example is given in which identity verification is performed by a service other than the payment service and the external service, but identity verification may also be performed by at least one of the payment service and the external service. The payment service obtains the result of identity verification performed by the other service from the other service. The process for identity verification may be a known process. For example, identity verification may be performed by image processing of an image of an identity verification document, or by visual confirmation by an operator. It may take a certain amount of time (for example, several hours to several days) from the application for identity verification to its completion.

[0026] For example, once identity verification is complete, the user terminal 30 displays a message indicating that identity verification has been completed on the identity verification screen SC3, as shown in the lower right of Fig. 2. Once identity verification is complete, the user becomes able to register an account at another bank as the source of charge. Once identity verification is complete, when the user selects panel P20 for registering an account at another bank (in the example at the upper right of Fig. 2, the bottommost panel P20), the user terminal 30 displays on the display unit 35, as shown in the upper left of Fig. 3, an account information input screen SC4 for the user to input account information related to the account at the other bank.

[0027] For example, the user enters the financial institution, account holder, branch, deposit type, and account number as account information on the account information input screen SC4. When the user enters the account information, the user terminal 30 displays a message indicating that the account information registration has been completed on the account information input screen SC4, as shown in the upper right of Fig. 3. When the user selects button B40, the user terminal 30 displays on the display unit 35 a selection screen SC2 indicating that an account at another bank has been set as the charge source, as shown in the lower left of Fig. 3.

[0028] In the example at the bottom left of FIG. 3, an account at another bank is set as the charge source, as shown in the top panel P20. The payment app may not display detailed account information (e.g., account number) of the account at the other bank set as the charge source. For example, when an account at the other bank is set as the charge source and a user performs an operation to charge, the user terminal 30 displays a charge screen SC5 for executing the charge on the display unit 35, as shown in the bottom right of FIG. 3. When the user inputs the charge amount on the charge screen SC5 and instructs to execute the charge, the payment server 10 executes the charge in cooperation with the linked server 20.

[0029] For example, after setting an account at another bank as the charge source, the user can change the charge source to another payment method, such as a credit card. When the user selects the second-from-top panel P20 in the selection screen SC2 in the upper left of FIG. 4, a credit card is set as the charge source. In this case, as shown in the upper right of FIG. 4, the user terminal 30 displays the selection screen SC2 on the display unit 35, indicating that a credit card has been set as the charge source. The second-from-top panel P20 and the bottom panel P20 each indicate that identity verification has been completed.

[0030] In this embodiment, a user can register only one account at another bank. Furthermore, in order to register a new account at another bank, the user must delete the previously registered account at that bank. In the state shown in the upper right of FIG. 4, if the user selects the trash can icon in the second-from-top panel P20, the registered account at that bank is deleted. As shown in the lower left of FIG. 4, the user terminal 30 deletes the panel P20 showing the registered account at the other bank from the selection screen SC2. When the user selects the bottom panel P20, as shown in the lower right of FIG. 4, the user terminal 30 displays the account information input screen SC4 on the display unit 35. Since identity verification has been completed, identity verification is not performed again.

[0031] As described above, the payment system 1 of this embodiment displays the identity verification status on the selection screen SC2 on which the user selects the charge source for the payment service. This allows the user to understand the identity verification status before selecting panel P20 for registering an account at another bank. For example, before selecting panel P20 for registering an account at another bank, the user can understand in advance whether identity verification is required or whether the account at another bank can be registered without further identity verification, thereby improving user convenience. Details of the payment system 1 will be described below.

[0032] [3. Functions realized by the payment system] Figure 5 is a diagram showing an example of functions realized by payment system 1. The units realized by payment system 1 can be configured as a single device or as smaller, distributed devices.

[0033] [3-1. Functions realized by the payment server] For example, the payment server 10 includes a data storage unit 100, a display request receiving unit 101, a status information acquisition unit 102, and a display control unit 103. The data storage unit 100 is realized by the storage unit 12. Each of the display request receiving unit 101, the status information acquisition unit 102, and the display control unit 103 is realized by the control unit 11.

[0034] [Data storage section] The data storage unit 100 stores data necessary for the payment service. For example, the data storage unit 100 stores a user database DB.

[0035] FIG. 6 is a diagram showing an example of a user database DB. The user database DB is a database that stores various information related to users. For example, the user database DB stores a user ID, password, code ID, payment method information, payment source information, charge source information, linked ID, terminal ID, and status information. The user database DB may also store other data. For example, the user database DB may store usage history information related to the usage history of the payment service.

[0036] The user ID is an example of user identification information that can identify a user. A login account may exist in addition to the user ID. The login account may be freely changeable by the user. The login account is also an example of user identification information. A password is information that is confirmed when logging in. The code ID is also an example of user identification information, as it is an ID that can identify a user in the payment service. The code ID is updated each time the code C10 is displayed. The user identification information may be information other than the user ID, login account, and code ID.

[0037] Payment method information is information that can identify the payment methods that a user can use for a payment service. The payment method indicated by the payment method information can be said to be a payment method that is a candidate for at least one of the payment source and the charge source. For example, payment method information is information such as a credit card number, electronic money number, bank account number, or point card number. Payment source information is information that can identify the payment method set for the payment source. Charge source information is information that can identify the payment method set for the charge source.

[0038] The linked ID is an ID that the payment server 10 uses to link with the linked server 20. For example, when a user registers an account at another bank, the linked server 20 issues the linked ID. The linked server 20 manages the linked ID in association with the account information of the account at the other bank. All or part of the account information of the account at the other bank may be managed by the payment server 10, but in this embodiment, only the linked ID is managed, and the account information of the account at the other bank is not managed. The linked ID may be information that the user uses to log in to an external service. The linked ID can also be considered user identification information common to the payment service and the external service. The linked ID may be issued by the payment server 10. A specific linked ID may not be issued, and the user identification information of the payment service may be used in the external service.

[0039] The terminal ID is an example of terminal identification information that can identify the user terminal 30. While the user identification information is information that can identify the user, the terminal identification information is information that can identify the user terminal 30. Therefore, when a user uses multiple user terminals 30, the terminal identification information of each user terminal 30 is different from one another. For example, the terminal ID may be issued by the payment server 10. The terminal identification information is not limited to the terminal ID. The terminal identification information may be the IP address of the user terminal 30, an ID recorded on a SIM card, individual identification information of the user terminal 30, or other information. In this embodiment, an example is given in which the terminal ID is generated by the payment server 10, but the terminal identification information, such as the terminal ID, may be stored in advance in the user terminal 30.

[0040] The status information is information relating to the status of identity verification. The status of identity verification can also be referred to as the implementation status of identity verification. For example, the status of identity verification is whether or not identity verification has been completed. For example, the status of identity verification is whether or not an identity verification application (including an application for renewal) has been completed. In this embodiment, an example is given in which the status information can have two statuses. That is, the status information is either a status indicating that identity verification has not been completed, or a status indicating that identity verification has been completed. In this embodiment, the status information is stored in the user database DB for each pair of user identification information and terminal identification information. Therefore, when a user uses multiple user terminals 30, status information is stored in the user database DB for each user terminal 30. When a user terminal 30 is shared by multiple users, status information is stored in the user database DB for each user who uses the user terminal 30.

[0041] The number of possible statuses for the status information may be three or more. If there are intermediate steps such as "identification documents uploaded" or "identification documents being verified" before identity verification is completed, the identity verification status may be the current step. Other statuses may also be present, such as "identification reapplication required" or "other documents required to be submitted," indicating that identity verification has been denied. The status information may indicate any one of a plurality of predetermined statuses. Identity verification may be an example of link information for linking the payment service with other services. In this embodiment, an example is given in which identity verification is performed by an external server; however, identity verification may also be performed by the payment server 10.

[0042] For example, the payment server 10 receives status information of a certain user from an external server that performs identity verification. The payment server 10 stores the status information received from the external server in the user database DB in association with the user ID of the user. When the external server updates the status information of a certain user, the payment server 10 receives the updated status information from the external server. The payment server 10 updates the status information associated with the user ID of the user. It is assumed that user identification information, such as a user ID, is linked between the payment server 10 and the external server.

[0043] In this embodiment, the status information indicates either a first value (e.g., "0") indicating that identity verification has not been completed, or a second value (e.g., "1") indicating that identity verification has been completed. The status information may have other values indicating intermediate steps. The value of the status information is expressed by letters, numbers, symbols, or a combination thereof. The initial value of the status information is the first value. When identity verification is completed, the status information is changed from the first value to a second value. The second value may be any value different from the first value.

[0044] The data stored in the data storage unit 100 is not limited to the above examples. The data storage unit 100 may store any data necessary for the payment service. For example, the data storage unit 100 may store data for various screens displayed on a payment app. The data storage unit 100 also stores programs and data necessary for payment, charging, and other processes.

[0045] [Display request reception section] The display request receiving unit 101 receives a request to display a selection screen SC2 for the user to select functions related to the payment service. Functions related to the payment service can also be considered as individual small services provided by the payment service. The payment service can also be considered as a concept that encompasses individual small services. Functions related to the payment service can also be considered as programs prepared by the payment service (for example, individual programs within the payment app or programs on the payment server 10 side). Functions related to the payment service can also be considered as types of information processing that can be performed by the payment service.

[0046] In this embodiment, a charge source setting function relating to setting the charge source will be described as an example of a function relating to payment services. The charge source setting function is a function for setting the payment method that will be the charge source. For example, the charge source setting function is a function for changing the payment method that will be the charge source. The charge source setting function may also be a function for registering a new payment method that will be the charge source. In the examples of Figures 2 to 4, the function that the user can use from selection screen SC2 corresponds to the charge source setting function.

[0047] Note that the function related to the payment service is not limited to the charge source setting function. For example, as in the modified example described below, the function related to the payment service may be a payment source setting function or a service usage function. Other examples of the function related to the payment service may include a function to newly register a payment method that can be used in the payment service, a function to change the user's own information, an authentication function for payment, or other functions. The function related to the payment service may be any function provided by the business operator that operates the payment service.

[0048] In this embodiment, since the display request receiving unit 101 is realized by the payment server 10, the display request for the selection screen SC2 is data that the payment server 10 receives from the user terminal 30. This data can be identified as a display request. The data format of the display request may be a format defined by an API or the like. In the example of FIG. 2, when the user selects button B12, the user terminal 30 transmits a display request for the selection screen SC2 to the payment server 10. The display request receiving unit 101 receives the display request for the selection screen SC2 from the user terminal 30. When the display request receiving unit 101 is realized by the user terminal 30, the display request receiving unit 101 may receive the display request by receiving an operation for the display request at the operation unit 34.

[0049] In this embodiment, the display request receiving unit 101 receives a request to display a selection screen SC2 for a user to select a charge source setting function for setting a charge source to be used for charging in the payment service, as a function related to the payment service. In the example of FIG. 2, the selection screen SC2 displays a panel P20 for selecting the charge source setting function. The user can use the charge source setting function by selecting panel P20. The charge source setting function may also be used by selecting an image or text other than panel P20. The selection screen SC2 only needs to receive an operation by the user to use the charge source setting function.

[0050] [Status information acquisition section] When a request to display the selection screen SC2 is accepted, the status information acquisition unit 102 acquires status information related to the status of the user's identity verification. In this embodiment, the status information is stored in the user database DB, so the status information acquisition unit 102 acquires the status information from the user database DB. The status information may be stored in a database other than the user database DB. In this case, the status information acquisition unit 102 acquires the status information from the other database. The status information may be stored in a computer other than the payment server 10 or an external information storage medium. In this case, the status information acquisition unit 102 acquires the status information from the other computer or the external information storage medium.

[0051] In this embodiment, the status information acquisition unit 102 acquires status information associated with the terminal identification information of the user terminal 30 that sent the display request for the selection screen SC2, based on a user database DB in which terminal identification information capable of identifying each of multiple user terminals 30 is associated with status information of identity verification performed by the user terminal 30. For example, the display request for the selection screen SC2 is assumed to include terminal identification information. The terminal identification information may be separate data from the display request for the selection screen SC2. The payment server 10 acquires the terminal identification information from the user database DB. The status information acquisition unit 102 acquires status information associated with the terminal identification information included in the display request from the user database DB. In this embodiment, the terminal ID corresponds to the terminal identification information, so the status information acquisition unit 102 acquires status information associated with the terminal ID included in the display request from the user database DB.

[0052] In this embodiment, the status information acquisition unit 102 acquires status information associated with the user identification information of the user who transmitted the display request for the selection screen SC2, based on a user database DB in which user identification information capable of identifying each of multiple users is associated with status information for verifying the identity of the user. For example, the display request for the selection screen SC2 is assumed to include user identification information. The user identification information may be separate data from the display request for the selection screen SC2. The payment server 10 acquires the user identification information from the user terminal 30. The status information acquisition unit 102 acquires status information associated with the user identification information included in the display request for the selection screen SC2 from the user database DB. For example, if a user ID corresponds to the user identification information, the status information acquisition unit 102 acquires status information associated with the user ID included in the display request for the selection screen SC2 from the user database DB. As described above, other information such as a code ID may also correspond to the user identification information.

[0053] In this embodiment, the charge source setting function corresponds to a function related to a payment service, so when a request to display selection screen SC2 is accepted, status information acquisition unit 102 acquires identity verification status information for setting a charge source. Since completion of identity verification is a condition for use of the charge source setting function, which enables a user to set an account at another bank as a charge source, status information acquisition unit 102 acquires identity verification status information that satisfies this condition for use. Payment server 10 permits the user to use the charge source setting function, which enables a user to set an account at another bank as a charge source, on the condition that the status information indicates completion of identity verification.

[0054] [Display control section] The display control unit 103 displays the identity verification status on the selection screen SC2 based on the status information. For example, the display control unit 103 generates display data for the entire selection screen SC2 indicating the identity verification status and transmits the display data to the user terminal 30, thereby displaying the identity verification status on the selection screen SC2. The display data is data necessary for display on the user terminal 30. The display data may be in any format. For example, the display data may be data in a markup language format such as HTML, image format such as JPEG, text format, or other format. The display control unit 103 may transmit display data for only the identity verification status portion to the user terminal 30, rather than the entire selection screen SC2. It is assumed that the data necessary for generating the display data is pre-stored in the data storage unit 100.

[0055] In this embodiment, the display control unit 103 displays a message indicating the identity verification status on the selection screen SC2. The message may be text or a character string. The display control unit 103 may display the identity verification status using a display method other than displaying a message. For example, the display control unit 103 may display an icon indicating the identity verification status on the selection screen SC2. The display control unit 103 may display the identity verification status on the selection screen SC2 using an image other than an icon. For example, the display control unit 103 may display the identity verification status on the selection screen SC2 using a window, a pop-up, a modal, or a banner. The method of displaying the identity verification status may be any of various methods used to display information.

[0056] For example, when the status information indicates that identity verification has been completed, the display control unit 103 displays on the selection screen SC2 that identity verification has been completed as the identity verification status. In this embodiment, when the status information has a second value, this corresponds to identity verification being completed, so when the status information has a second value, the display control unit 103 displays on the selection screen SC2 a message and an icon indicating that identity verification has been completed. In the examples of the selection screen SC2 at the bottom left in FIG. 3 and the selection screen SC2 at the bottom left in FIG. 4, the display control unit 103 displays in the bottom panel P20 a message and an icon indicating that identity verification has been completed.

[0057] In the example of the selection screen SC2 in the upper left of FIG. 4, the display control unit 103 displays a message and an icon indicating that identity verification has been completed in each of the topmost panel P20 and the bottommost panel P20. In the example of the selection screen SC2 in the upper right of FIG. 4, the display control unit 103 displays a message and an icon indicating that identity verification has been completed in each of the second-highest panel P20 and the bottommost panel P20. The display control unit 103 may use a display method other than a message and an icon to display on the selection screen SC2 that identity verification has been completed. Examples of other display methods are as described above.

[0058] For example, when the user selects a function related to a payment service on the selection screen SC2 that displays the identity verification status, the display control unit 103 enables transition to the next screen according to the identity verification status. The selection of a function is an operation on the selection screen SC2. In the example of FIGS. 2 to 4, the selection of the panel P20 corresponds to the selection of the function. The selection of a function may be performed by an operation other than the selection of the panel P20 (for example, the selection of a button or a message). The selection of a function may be performed by any operation.

[0059] In this embodiment, the charge source setting function corresponds to a function related to a payment service, so when the user selects the charge source setting function by selecting panel P20, the display control unit 103 enables transition to the next screen according to the identity verification status. The next screen is the destination screen. Screen transition means displaying another screen. In other words, screen transition means proceeding to the next screen. There may be another screen between the source screen and the destination screen. The display control unit 103 enables transition to another screen by including a link to another screen in the selection screen SC2 so that the other screen is displayed when the user selects the link.

[0060] In this embodiment, it is assumed that screen transition data indicating the relationship between the identity verification status and the next screen to which the user will transition is stored in advance in the data storage unit 100. The screen transition data may be in any format. For example, the screen transition data may be in the form of a mathematical formula, a table, part of a program, a machine learning model, or any other format. The display control unit 103 identifies the next screen associated with the identity verification status based on the screen transition data. The display control unit 103 displays a selection screen SC2 including a link to the identified next screen on the user terminal 30.

[0061] In the example shown in the upper right of FIG. 2, when the status information indicates that identity verification has not been completed and the user selects a function related to a payment service on the selection screen SC2, the display control unit 103 enables transition to an identity verification screen SC3, which allows the user to verify their identity, as the next screen. In this case, the display control unit 103 enables transition to the identity verification screen SC3 as the next screen by displaying the selection screen SC2, which includes a link to the identity verification screen SC3, on the user terminal 30. For example, the screen transition data indicates the relationship between the status indicating that identity verification has not been completed and the link to the identity verification screen SC3. In the example shown in the upper right of FIG. 2, the display control unit 103 enables transition to the identity verification screen SC3 by setting a link to the identity verification screen SC3 in the bottommost panel P20 based on this relationship.

[0062] In the example shown in the lower left of FIG. 3, when the status information indicates that identity verification has been completed and the user selects a function related to a payment service on the selection screen SC2, the display control unit 103 enables the user to transition to the next screen for using that function. In this embodiment, the charge source setting function corresponds to the payment service function. Therefore, the display control unit 103 enables the user to transition to the charge screen SC5 or another screen as the next screen by displaying the selection screen SC2, which includes a link to the charge screen SC5 or another screen (e.g., the account information input screen SC4), on the user terminal 30. For example, the screen transition data indicates the relationship between the status indicating that identity verification has been completed and the link to the charge screen SC5 or another screen. In the example shown in the lower left of FIG. 3, the display control unit 103 enables the user to transition to the charge screen SC5 or another screen by setting a link to the charge screen SC5 or another screen in the bottom panel P20 based on this relationship.

[0063] In this embodiment, the payment service includes functions that require identity verification and functions that do not require identity verification. Functions that require identity verification are functions that cannot be used by a user unless identity verification is completed. In other words, functions that require identity verification are functions whose use requires completion of identity verification. In the examples of Figures 2 to 4, the charge source setting function for setting an account at another bank as the charge source corresponds to a function that requires identity verification.

[0064] A function that does not require identity verification is a function that can be used by a user without completing identity verification. In other words, a function that does not require identity verification is a function for which completion of identity verification is not a condition for use. In the examples of Figures 2 to 4, the charge source setting function for setting a credit card as the charge source corresponds to a function that does not require identity verification. The charge source setting function for setting a specific bank account (in the examples of Figures 2 to 4, an account at "AAA Bank") also corresponds to a function that does not require identity verification.

[0065] In this embodiment, the display control unit 103 displays the status of identity verification associated with a function requiring identity verification on a selection screen SC2 that allows the user to select between a function requiring identity verification and a function not requiring identity verification. Associating a function requiring identity verification with the status of identity verification means arranging the status of identity verification within or near an image for selecting the function. In the examples of FIGS. 2 to 4, arranging the status of identity verification within a panel P20 for selecting a function requiring identity verification corresponds to associating the function with the status of identity verification. The display control unit 103 does not associate the status of identity verification with a function not requiring identity verification. The display control unit 103 does not arrange the status of identity verification within a panel P20 for selecting a function not requiring identity verification.

[0066] In this embodiment, the charge source setting function for setting an account at another bank as a charge source is not completed within the payment service alone but requires cooperation between the payment service and an external service. Therefore, the display control unit 103 displays the identity verification status on the selection screen SC2, which allows the user to select functions realized by the cooperation between the payment service and the external service. For example, account information for accounts at other banks is managed by the linkage server 20. When a user instructs the payment server 10 to charge an account at another bank as a charge source, the payment server 10 transmits a linkage ID to the linkage server 20. The linkage server 20 executes a process to reduce the balance of the account at the other bank by an amount corresponding to the charge amount based on the account information associated with the linkage ID. The linkage server 20 notifies the payment server 10 of the results of the process. When the payment server 10 receives a notification from the linkage server 20 that the process was successful, it executes a process to increase the user's electronic money balance. This series of processes is executed through cooperation between the payment server 10 and the linkage server 20.

[0067] In this embodiment, since the terminal identification information and the status information are associated with each other in the user database DB, the display control unit 103 displays the identity verification status on the selection screen SC2 of the user terminal 30 that sent the display request, based on the status information associated with the terminal identification information of the user terminal 30. As described above, the status information acquisition unit 102 acquires the status information associated with the terminal identification information, and the display control unit 103 displays the identity verification status on the selection screen SC2 of the user terminal 30 indicated by the terminal identification information, based on the status information. In this embodiment, the terminal ID corresponds to the terminal identification information, and the display control unit 103 displays the identity verification status on the selection screen SC2 of the user terminal 30 indicated by the terminal ID, based on the status information associated with the terminal ID.

[0068] In this embodiment, since user identification information and status information are associated with each other in the user database DB, the display control unit 103 displays the status on the selection screen SC2 of the user who sent the display request based on the status information associated with the user identification information of the user. As described above, the status information acquisition unit 102 acquires the status information associated with the user identification information, and therefore the display control unit 103 displays the identity verification status on the selection screen SC2 of the user indicated by the user identification information based on the status information. The selection screen SC2 of the user indicated by the user identification information is the selection screen SC2 displayed on the user terminal 30 to which the user is currently logged in. In this embodiment, the user ID corresponds to the user identification information, and therefore the display control unit 103 displays the identity verification status on the selection screen SC2 of the user indicated by the user ID based on the status information associated with the user ID.

[0069] In this embodiment, since the charge source setting function corresponds to a function related to a payment service, the display control unit 103 displays the identity verification status for setting a charge source on the selection screen SC2. That is, the display control unit 103 displays the identity verification status, which is a condition for a user to set a charge source, on the selection screen SC2. The display control unit 103 displays the identity verification status before transitioning to the identity verification screen SC3 or the charge screen SC5, which are the next screens after the selection screen SC2.

[0070] [3-2. Functions realized by the linked server] For example, the link server 20 includes a data storage unit 200 and a link unit 201. The data storage unit 200 is realized by the storage unit 22. The link unit 201 is realized by the control unit 21.

[0071] [Data storage section] The data storage unit 200 stores data necessary for the external service. For example, the data storage unit 200 stores a database that stores various information managed by the external service. In this embodiment, accounts at other banks are managed by the external service, so the database stores various information related to accounts at other banks. For example, the database stores information such as the financial institution name or financial institution code of the other bank, the branch name or branch code of the other bank, the account type, the account number, and the account holder.

[0072] For example, the data storage unit 200 stores a database in which each of a plurality of linked IDs is associated with account information of an account at another bank registered by the user corresponding to the linked ID. In this embodiment, a user can associate only one account with one linked ID, and therefore only one piece of account information is associated with one linked ID. If a user is allowed to associate multiple accounts with one linked ID, multiple pieces of account information may be associated with one linked ID. When a user completes identity verification in a payment service and performs an operation to register an account, the linked server 20 issues a linked ID and stores the account information of the account entered by the user in the database.

[0073] The data storage unit 200 may store data according to the external service. For example, the data storage unit 200 may store various information about a user who uses the external service. If the external service provides its own payment service, the data storage unit 200 may store data for a user to make a payment with the external service. For example, if identity verification is performed on the external service side, the data storage unit 200 may store status information indicating the status of identity verification performed on the external service side.

[0074] [Collaboration Department] The linking unit 201 links with the payment service based on the data stored in the data storage unit 200. In this embodiment, since the payment using an account at another bank is realized by an external service, the linking unit 201 links with the payment service by executing the payment using the account at the other bank (for example, a process of deducting an amount corresponding to the charge amount from the account balance). For example, when the linking unit 201 receives a request for charge using an account at another bank from the payment server 10, the linking unit 201 executes the payment for charge based on the account information of the account stored in the data storage unit 200.

[0075] For example, the linking server 20 can link with at least one of the servers of various financial institutions and a server that oversees the various financial institutions. The process by which the linking server 20 links with these servers to execute a payment using an account at another bank may be a known process. For example, the linking server 20 executes a process adopted as a known online banking process to execute a payment using an account at another bank. When the linking unit 201 executes the payment, it transmits the execution result of the payment to the payment server 10. When the payment server 10 receives the execution result of the payment, it increases the balance of the electronic money to be charged. The payment executed on the external service side and the charge executed on the payment service side may each be a known process.

[0076] [3-3. Functions implemented on user devices] For example, the user terminal 30 includes a data storage unit 300, an operation reception unit 301, and a display control unit 302. The data storage unit 300 is realized by the storage unit 32. The operation reception unit 301 and the display control unit 302 are realized by the control unit 31.

[0077] [Data storage section] The data storage unit 300 stores data necessary for a user to use a payment service. For example, the data storage unit 300 stores a payment app. When a user uses a payment service from a browser rather than a payment app, the data storage unit 300 stores the browser.

[0078] [Operation reception section] The operation acceptance unit 301 accepts various operations from the user. For example, the operation acceptance unit 301 accepts operations for the payment application. The operation acceptance unit 301 transmits data indicating the content of the user's operation to the payment server 10.

[0079] [Display control section] The display control unit 302 displays various screens on the display unit 35. For example, the display control unit 302 displays a top screen SC1, a selection screen SC2, an identity verification screen SC3, an account information input screen SC4, and a charge screen SC5 on the display unit 35. The display control unit 302 communicates with the payment server 10, the linked server 20, or another computer, receives data necessary to display these screens, and displays these screens on the display unit 35.

[0080] [4. Processing performed by the payment system] Figure 7 is a diagram showing an example of processing executed in payment system 1. The processing in Figure 7 is executed by control units 11, 21, and 31 executing programs stored in storage units 12, 22, and 32, respectively. Figure 7 explains the processing when a user selects button B12 on top screen SC1.

[0081] 7, when the user selects button B12, the user terminal 30 transmits a display request for selection screen SC2 to the payment server 10 (S1). The payment server 10 receives the display request for selection screen SC2 from the user terminal 30 (S2). The payment server 10 acquires status information associated with the user ID of the logged-in user and the terminal ID of the user terminal 30 that transmitted the display request for the selection screen, based on the user database DB (S3).

[0082] The payment server 10 executes processing between the user terminal 30 to display the identity verification status on the selection screen SC2 based on the status information acquired in S3 (S4). In S4, if the status information indicates that identity verification has not been completed, the payment server 10 generates display data for the selection screen SC2 including a message indicating that identity verification has not been completed. If the status information indicates that identity verification has been completed, the payment server 10 generates display data for the selection screen SC2 including a message indicating that identity verification has been completed. The payment server 10 transmits the display data for the selection screen SC2 to the user terminal 30. The user terminal 30 displays the selection screen SC2 on the display unit 35 based on the display data.

[0083] The following describes the processing that occurs when a user performs an operation to register an account at another bank when identity verification has not been completed. In the example of the selection screen SC2 in the upper right of Figure 2, selecting the bottom panel P20 corresponds to the user's operation to register an account at another bank. If it is not determined that the user has performed an operation to register an account at another bank, processing is executed according to the other operation performed by the user.

[0084] The user terminal 30 sends a display request for the next screen of the selection screen SC2 to the payment server 10 (S5). The display request for the next screen is a request for transitioning to a link included in the panel P20 selected by the user. In this case, the identity verification screen SC3 corresponds to the next screen. The payment server 10 receives the display request for the next screen from the user terminal 30 (S6). The payment server 10 executes processing for identity verification (S7). In S7, the payment server 10 redirects the user terminal 30 to another server that executes identity verification. The user terminal 30 executes identity verification in the same manner as a known process. The payment server 10 obtains the execution result of identity verification from the other server or the user terminal 30.

[0085] When identity verification is complete, the payment server 10 updates the status information stored in the user database DB (S8). In S8, the payment server 10 updates the status information associated with the user ID of the logged-in user and the terminal ID of the user terminal 30 that sent the request to display the selection screen so as to indicate that identity verification has been completed. The payment server 10 executes processing for registering an account at another bank between the linked server 20 and the user terminal 30 (S9). In S9, the payment server 10 displays an account information input screen SC4 on the user terminal 30. The payment server 10 acquires the account information entered by the user from the user terminal 30. The payment server 10 transmits the account information to the linked server 20. The linked server 20 issues an associated ID and manages it in association with the account information. The payment server 10 acquires the associated ID from the linked server 20 and stores it in the user database DB. In S9, authentication of the account at the other bank (for example, PIN authentication or biometric authentication) may be performed.

[0086] The payment server 10 sets an account at another bank as the charge source (S10). In S10, the payment server 10 updates the charge source information stored in the user database DB so that the charge source information indicates the account at the other bank. When the user instructs the execution of charge, the payment server 10 executes processing for charge with the account at the other bank as the charge source between the link server 20 and the user terminal 30 (S11), and this processing ends. In S11, the payment server 10 receives information such as the charge amount instructed by the user from the user terminal 30. The payment server 10 sends a charge request corresponding to the information to the link server 20. The link server 20 executes processing to reduce the balance of the account at the other bank by an amount corresponding to the charge amount. The payment server 10 receives the execution result of the processing from the link server 20, and executes processing to increase the balance of the electronic money.

[0087] [5. Summary of embodiments] The payment system 1 of this embodiment accepts a request to display the selection screen SC2. When the display request is accepted, the payment system 1 acquires status information. The payment system 1 displays the status on the selection screen SC2 based on the status information. This allows the user to understand the identity verification status before selecting a function related to a payment service on the selection screen SC2, thereby improving user convenience. For example, the user can easily understand the identity verification status when considering using a function related to a payment service. For example, in conventional technology, the identity verification status is displayed after the user selects a function related to a payment service. In conventional technology, the user cannot understand the identity verification status before selecting a function related to a payment service. If the user needs to complete identity verification to use the function, the user cannot understand whether the function can be used before selecting the function. For this reason, in conventional technology, status information is acquired assuming that the user will use the function. In contrast, the payment system 1 of this embodiment can lower the psychological hurdle for users to use the function by displaying the identity verification status on the selection screen SC2 for selecting the function, regardless of whether the user uses the function or not. In other words, the payment system 1 can motivate users to use the function.

[0088] Furthermore, when the status information indicates that identity verification has been completed, the payment system 1 displays the identity verification completion status on the selection screen SC2. This allows the user to understand that identity verification has been completed before selecting a function related to the payment service on the selection screen SC2, thereby enabling the payment system 1 to improve user convenience. For example, the user can understand before selecting a function that they can use the function immediately after selecting it, thereby lowering the psychological barrier to using the function. In other words, the payment system 1 can motivate the user to use the function. For example, if the function related to the payment service is a charge source setting function, the user can understand in advance that identity verification required to use the charge source setting function has been completed, thereby enabling the payment system 1 to motivate the user to start the charge source setting function.

[0089] Furthermore, when a user selects a function related to a payment service on the selection screen SC2 that displays the identity verification status, the payment system 1 enables transition to the next screen according to the status. This allows the payment system 1 to display different next screens depending on the identity verification status, thereby further improving user convenience.

[0090] Furthermore, when the status information indicates that identity verification has been completed and the user selects a function related to a payment service on selection screen SC2, payment system 1 allows the user to transition to the next screen for using the function. This allows a user whose identity verification has been completed to use the function related to a payment service on the screen next to selection screen SC2, so payment system 1 allows the user to use the function without requiring the user to perform any unnecessary operations or display any unnecessary screens.

[0091] Furthermore, the payment system 1 displays the status of identity verification associated with the function requiring identity verification on a selection screen SC2 on which the user can select between functions requiring identity verification and functions not requiring identity verification. This allows the user to easily understand which functions require identity verification and the status of identity verification required for use of the function. For example, since the status of identity verification is not associated with functions not requiring identity verification, the user can easily understand which functions do not require identity verification.

[0092] Furthermore, the payment system 1 displays the identity verification status on the selection screen SC2 on which the user selects a function realized by the payment service and the external service cooperating with each other. This allows the user to understand the identity verification status before selecting a function realized by the payment service and the external service cooperating with each other, so the payment system 1 can further enhance user convenience. For example, the payment system 1 can lower the psychological hurdle for the user to use the function. In other words, the payment system 1 can motivate the user to use the function.

[0093] Furthermore, the payment system 1 displays the identity verification status on the selection screen SC2 of the user terminal 30 based on the status information associated with the terminal identification information of the user terminal 30 that sent the display request. This allows the user to understand the identity verification status from the user terminal 30 during operation, so the payment system 1 can further improve user convenience. For example, even if a malicious third party logs in to the payment service by impersonating a legitimate user, the third party's terminal cannot successfully verify the identity. This allows the payment system 1 to prevent fraudulent use of the payment service and improve security.

[0094] Furthermore, the payment system 1 displays the identity verification status on the selection screen SC2 of the user who sent the display request, based on the status information associated with the user identification information of the user. This allows the user to understand the status of their identity verification, so the payment system 1 can further improve user convenience. For example, even if a malicious third party steals the user terminal 30 of a legitimate user and logs in to the payment service using their own user ID, they cannot use functions related to the payment service unless they log in using the legitimate user's user ID. This allows the payment system 1 to prevent fraudulent use of the payment service and improve security.

[0095] Furthermore, the function related to the payment service is a charge source setting function, which allows the payment system 1 to improve convenience for users who use the charge source setting function.

[0096] [6. Modifications] The present disclosure is not limited to the above-described embodiments, and may be modified as appropriate without departing from the spirit of the present disclosure.

[0097] 8 is a diagram showing an example of functions realized in the modified example. For example, the payment server 10 includes a determination unit 104, an update unit 105, an authentication request unit 106, a payment permission unit 107, and an estimation unit 108. Each of the determination unit 104, the update unit 105, the authentication request unit 106, the payment permission unit 107, and the estimation unit 108 is realized by the control unit 11.

[0098] [6-1. Variation 1] For example, a payment service may have multiple functions that require identity verification. In variant example 1, two functions that require identity verification are given as examples: the charge source setting function described in the embodiment, and the payment source setting function related to setting the payment source. In variant example 1, it is assumed that an account at another bank can be set as the payment source. However, it is assumed that a user must complete identity verification to set an account at another bank as the payment source. Furthermore, it is assumed that a user does not need to perform identity verification for the charge source setting function and identity verification for the payment source setting function separately. A user can use both the charge source setting function and the payment source setting function with a single identity verification.

[0099] FIG. 9 is a diagram showing an example of a screen displayed on the user terminal 30 of Modification 1. For example, when a user selects button B11 on the top screen SC1 in the state shown in the upper left of FIG. 9, the display control unit 103 causes the user terminal 30 to display a selection screen SC6 for selecting a payment source, as shown in the upper right of FIG. 9. The selection screen SC6 differs from the selection screen SC2 in the lower right of FIG. 9 in that it is a screen for accepting the selection of a payment source, but it is similar to the selection screen SC2 in that it is a screen for selecting functions in the payment service. The user can select a payment source by selecting panel P60. The display control unit 103 causes the selection screen SC2 and SC6 for each of the multiple functions to display the identity verification status. The display of the selection screen SC2 in the lower right of FIG. 9 is as described in the embodiment.

[0100] For example, the display control unit 103 identifies payment methods that the user can select as the payment source based on the payment method information stored in the user database DB. Based on the payment method identification result and the status information, the display control unit 103 generates display data for the entire selection screen SC6 indicating the identity verification status, and transmits the display data to the user terminal 30, thereby displaying the identity verification status on the selection screen SC6. The display control unit 103 may transmit display data for only the identity verification status portion to the user terminal 30, rather than the entire selection screen SC6.

[0101] In the example shown in the upper right of FIG. 9, the display control unit 103 displays a message on the bottom panel P60 indicating that identity verification has not been completed. Once identity verification is completed, the display control unit 103 displays a message on the panel P60 for setting an account at another bank as the payment source indicating that identity verification has been completed. The process by which the display control unit 103 displays the identity verification status on the payment source selection screen SC6 may be the same as the process for displaying the identity verification status on the charge source selection screen SC2. The details of this process are as described in the embodiment.

[0102] Although the selection screens SC2 and SC6 for the multiple functions are separate from each other in the example described above, the selection screens for the multiple functions may be the same screen. For example, the display control unit 103 may cause the user terminal 30 to display a single selection screen that allows the user to select both the charge source setting function and the payment source setting function. Furthermore, the multiple functions are not limited to the charge source setting function and the payment source setting function. For example, the multiple functions may include a service usage function, which will be described later, or other functions.

[0103] The payment system 1 of the first modification displays the status of identity verification on the selection screens SC2 and SC6 for each of the multiple functions that require identity verification. This allows the user to understand the status of identity verification before selecting each of the multiple functions, thereby improving user convenience.

[0104] [6-2. Variation 2] For example, as in Modification 1, when the status of identity verification is displayed on each of the selection screens SC2 and SC6 for a plurality of functions, the user may be allowed to transition to the identity verification screen SC3 from any of the selection screens SC2 and SC6. In Modification 2, the display control unit 103 is capable of transitioning to the identity verification screen SC3 for the user to verify their identity when the status information indicates that identity verification has not been completed and the user selects any of the plurality of functions. The process for transitioning from the selection screen SC2 at the bottom right of Fig. 9 to the identity verification screen SC3 is as described in the embodiment with reference to Fig. 2.

[0105] For example, when the status information indicates that identity verification has not been completed and the user selects a function related to a payment service on the selection screen SC6, the display control unit 103 enables transition to an identity verification screen SC3, which allows the user to verify their identity, as the next screen. In this case, the display control unit 103 enables transition to the identity verification screen SC3 as the next screen by displaying the selection screen SC6 including a link to the identity verification screen SC3 on the user terminal 30. Similarly, when functions other than the charge source setting function and the payment source setting function are provided as multiple functions requiring identity verification, the display control unit 103 may cause the selection screen SC6 including a link to the identity verification screen SC3 to be displayed on the user terminal 30 when the status information indicates that identity verification has not been completed.

[0106] In the payment system 1 of the second modification, when the status information indicates that identity verification has not been completed and the user selects any one of the functions, the payment system 1 can transition to an identity verification screen SC3 for the user to verify their identity. This allows the user to go through the identity verification procedure directly regardless of which of the functions the user selects, thereby improving user convenience.

[0107] [6-3. Variation 3] For example, in Modification 2, when a user selects the charge source setting function from the selection screen SC2 and completes identity verification, the identity verification status displayed on the selection screen SC6 may also reflect that identity verification has been completed. That is, when a user completes identity verification from the identity verification screen SC3, the display control unit 103 displays the identity verification status as completed on the selection screen SC6 for a function (here, the payment source setting function) other than the function selected by the user (here, the charge source setting function) among multiple functions. When the user performs identity verification by transitioning from the selection screen SC2 to the identity verification screen SC3, the status information is updated to indicate that identity verification has been completed. Therefore, the display control unit 103 can display the selection screen SC6 based on the updated status information, thereby displaying the identity verification status on the selection screen SC6 for the payment source setting function that the user did not select.

[0108] Conversely, when a user selects the payment source setting function from the selection screen SC6 and completes identity verification, the identity verification status displayed on the selection screen SC2 may also reflect that identity verification has been completed. That is, when a user completes identity verification from the identity verification screen SC3, the display control unit 103 displays, as the identity verification status, that identity verification has been completed on the selection screen SC2 for a function (here, the charge source setting function) other than the function selected by the user (here, the payment source setting function). When the user transitions from the selection screen SC6 to the identity verification screen SC3 and performs identity verification, the status information is updated to indicate that identity verification has been completed. Therefore, the display control unit 103 can display the selection screen SC2 based on the updated status information, thereby displaying the identity verification status on the selection screen SC2 for the charge source setting function that the user did not select.

[0109] Note that the functions related to payment services are not limited to the charge source setting function and the payment source setting function. For example, when a maximum payment usage amount is set, an increase function for increasing the maximum usage amount may correspond to a function related to payment services. In this case, status information indicating the application for identity verification and the update results is aggregated in the same user database DB. Therefore, if a user selects the increase function and performs identity verification without completing identity verification, the display control unit 103 may display the updated status on the selection screen SC2 for the charge source setting function. Another example is a function that enables a user to use withdrawable electronic money. Identity verification may also be required for this function.

[0110] In the payment system 1 of Variation 3, when a user completes identity verification on the identity verification screen SC3, the selection screens SC2 and SC6 for functions other than the function selected by the user among the plurality of functions display the status that identity verification has been completed. This allows the user to select any function among the plurality of functions to complete identity verification, thereby improving user convenience. Furthermore, the results of identity verification are also reflected for other functions that the user did not select during identity verification, so the user can check the latest status on the selection screens SC2 and SC6 for other functions.

[0111] [6-4. Variation 4] For example, once a user has performed identity verification once, that identity verification may be permanently valid, but for security reasons, identity verification may be required again. The payment system 1 of Variation 4 includes a determination unit 104 and an update unit 105. The determination unit 104 determines whether or not identity verification is required again when identity verification of the user has been completed. The determination unit 104 determines whether or not identity verification is required again by determining whether a predetermined condition is satisfied.

[0112] The predetermined condition is a condition that requires re-identification. The predetermined condition may be a condition that can be determined based on information about the user, or a condition that is not determined based on information about the user. For example, the predetermined condition may be a condition that a predetermined period of time has passed since identity verification was performed, a change in the user's surname, a change in the user's address, or other conditions. The predetermined period of time may vary depending on the user's trustworthiness in the payment service. The determination unit 104 may determine whether the user's surname or address has changed based on information registered in the payment service, or may determine whether the user's surname or address has changed based on information registered in a service other than the payment service.

[0113] The update unit 105 updates the status information so that the status information indicates that further identity verification is required based on the determination result of the determination unit 104. For example, if the determination unit 104 does not determine that further identity verification is required, the update unit 105 does not update the status information, and if the determination unit 104 determines that further identity verification is required, the update unit 105 updates the status information. In the same example as the embodiment, if the determination unit 104 determines that further identity verification is required, the update unit 105 updates the status information so that the second value is changed to the first value.

[0114] When the status information is updated, the display control unit 103 of Modification 4 displays, on the selection screen SC2, based on the updated status information, a message indicating that re-identification is required as the identity verification status. In Modification 4, an example is given in which the message indicating that re-identification is required and the message displayed when the user has never performed identity verification are the same, but these messages may be different from each other. In this case, the value of the status information when the user has never performed identity verification is different from the value of the status information when re-identification is required. The display control unit 103 may identify the status based on the value indicated by the status information and display the status accordingly. The re-identification process may follow the same flow as the first identity verification.

[0115] In the fourth modification, the payment system 1 determines whether or not re-identification is required when the user's identity has been verified. Based on the result of this determination, the payment system 1 updates the status information so that the status information indicates that re-identification is required. When the status information is updated, the payment system 1 displays, on the selection screen SC2, based on the updated status information, the identity verification status indicating that re-identification is required. This allows the user to understand that re-identification is required before selecting a function such as the charge source setting function, thereby enabling the payment system 1 to further improve user convenience. By requiring the user to verify their identity again, the payment system 1 can improve security.

[0116] [6-5. Variation 5] For example, the display request receiving unit 101 may receive a request to display a selection screen SC6 that allows a user to select a payment source setting function related to setting the payment source used for payments in the payment service as a function related to the payment service. The selection screen SC6 for the payment source setting function is as described in Variation 1. Variation 1 exemplifies a case in which both the charge source setting function and the payment source setting function are realized, but in Variation 5, the charge source setting function does not have to be realized. In other words, the payment service of Variation 5 may only support the payment source setting function. When a user performs an operation to change the payment source, the payment server 10 updates the payment source information stored in the user database DB.

[0117] When a display request is received, the status information acquisition unit 102 of Modification 5 acquires status information of identity verification for setting the payment source. This differs from the embodiment in that the status information indicates the status of identity verification for the payment source setting function, but the process by which the status information acquisition unit 102 acquires the status information may be the same as in the embodiment. The display control unit 103 of Modification 5 displays the status of identity verification for setting the payment source on the selection screen SC6. This differs from the embodiment in that the selection screen SC6 on which the identity verification status is displayed is a screen for selecting the payment source setting function, but the process for display executed by the display control unit 103 may be the same as in the embodiment.

[0118] The payment system 1 of Variation 5 accepts a request to display a selection screen SC2 that allows a user to select a payment source setting function for setting a payment source to be used in payments in the payment service as a function related to the payment service. When the display request is accepted, the payment system 1 acquires status information about identity verification for setting a payment source. The payment system 1 displays the status of identity verification for setting a payment source on the selection screen SC2. This allows the payment system 1 to improve convenience for users who use the payment source setting function.

[0119] [6-6. Variation 6] For example, as in Variation 5, when an account at another bank is set as the payment source, authentication may be requested from the user each time a payment is made. Variation 6 takes as an example a case where authentication is requested at the time of payment after identity verification of a payment source requiring identity verification has been completed. The payment system 1 of Variation 6 includes an authentication request unit 106 and a payment permission unit 107. When a payment is made based on a payment source requiring identity verification, the authentication request unit 106 requests authentication for the payment from the user. Variation 6 describes an account at another bank as an example of a payment source requiring identity verification. The payment source requiring identity verification may be a payment means other than an account at another bank. Data that can identify which payment means is the payment source requiring identity verification is assumed to be pre-stored in the data storage unit 100.

[0120] For example, the authentication request unit 106 determines whether an account at another bank is set as the payment source based on the payment source information. In the sixth modification, when a user performs an operation to display the code C10, the authentication request unit 106 determines whether an account at another bank is set as the payment source based on the payment source information. The authentication request unit 106 may make this determination at other times. For example, the authentication request unit 106 may make this determination when the payment app is launched, when the code C10 is read, or at other times.

[0121] For example, if it is determined that an account at another bank is not set as the payment source, the authentication request unit 106 does not request the user to perform predetermined authentication, but if it is determined that an account at another bank is set as the payment source, the authentication request unit 106 requests the user to perform predetermined authentication. Requesting authentication means displaying a screen for authentication on the user terminal 30. The screen may be a screen that accepts the user's input of authentication information (e.g., a PIN or password), or may be a screen that activates a biometric authentication function possessed by the user terminal 30. The authentication request unit 106 requests authentication by transmitting display data of the screen to the user terminal 30. The authentication request unit 106 may also request authentication without displaying a particular screen. In this case, the authentication request unit 106 requests authentication from the user by transmitting data indicating that authentication is requested to the user terminal 30.

[0122] The authentication requested of the user may be any authentication. For example, the authentication request unit 106 may request PIN authentication or biometric authentication from the user. Other examples of the predetermined authentication may include possession authentication using a card such as a cash card, password authentication, or other authentication. The authentication process may be a known process. Information required for authentication (for example, correct authentication information) is assumed to be stored in the data storage unit 100. The authentication may be performed by the payment server 10 or the user terminal 30, or may be performed by an authentication server.

[0123] The payment permission unit 107 permits payment if authentication is successful. The payment permission unit 107 does not permit payment if authentication is not successful. For example, if authentication is not successful, the payment permission unit 107 does not permit payment by not permitting display of the code C10. If authentication is successful, the payment permission unit 107 permits payment by permitting display of the code C10. Even when payment is made by a method other than reading the code C10, the payment permission unit 107 may permit payment depending on the method. If authentication is performed by an authentication server, the payment permission unit 107 may obtain the result of authentication execution from the server. If authentication is performed by the user terminal 30, the payment permission unit 107 may obtain the result of authentication execution from the user terminal 30.

[0124] Authentication may be requested at the time of payment when identity verification of a payment source that requires identity verification has not been completed, or when identity verification has been completed but the validity period for identity verification has expired and renewal is required. In this case, the authentication request unit 106 initially requests authentication using a PIN or password from the user at the time of payment. The payment permission unit 107 permits payment if authentication is successful. The payment system 1 may also perform identity verification after payment. If identity verification after payment is not performed, the payment system 1 may not permit subsequent payments.

[0125] In the sixth variation, the payment system 1 requests authentication for a payment from a user when a payment is made based on a payment source that requires identity verification. If authentication is successful, the payment system 1 authorizes the payment. This enables the payment system 1 to improve payment security. For example, if authentication is required at the time of payment after identity verification of a payment source that requires identity verification has been completed, the payment system 1 can prevent fraudulent use when the user terminal 30 is lost or the code C10 is leaked by combining identity verification and authentication. For example, if payment is authorized based on authentication instead of identity verification, the payment system 1 can improve user convenience by temporarily authorizing payment based on authentication.

[0126] [6-7. Variation 7] For example, as described in the embodiment, payments based on payment sources that require identity verification are provided through collaboration between the payment service and an external service. In this case, identity verification may be required not only by the payment service but also by the external service. In variant 7, the display control unit 103 may display on the selection screen SC2, SC6, or another screen that identity verification information related to identity verification can be linked to an external service when identity verification has been completed by the payment service. Assume that the user has been identified by the payment service, but has not been identified by the external service.

[0127] The identity verification information may be any information related to identity verification. For example, the identity verification information may be information indicating whether identity verification has been completed by the payment service. The identity verification information may be information uploaded during identity verification by the payment service (e.g., information such as an ID card or personal identification number). The other screen that displays that identity verification information can be linked to an external service may be any screen other than the selection screens SC2 and SC6, and may be, for example, a screen to which the selection screens SC2 and SC6 transition.

[0128] For example, the display control unit 103 may display on the selection screens SC2 and SC6 that the user's identity has been verified, and may display on another screen after the user transitions from the selection screens SC2 and SC6 that the identity verification information in the payment service can be linked (for example, a message such as "The identity verification information in the payment service can be linked to an external service. Do you want to link?"). If the user selects to link the identity verification information, the identity verification information is linked from the payment service to the external service. In the external service, the user's identity will be verified even if the user does not upload an identity verification document, etc.

[0129] For example, conversely to the above, the display control unit 103 may display on the selection screen SC2, SC6 or another screen that, when the user has already been identified by an external service, the user's identity can be linked to the payment service. In this case, the user's identity has been identified by the external service, but the payment service has not yet identified the user. If the user selects to link the identity information, the identity information is linked from the external service to the payment service. The payment service will then identify the user as having been identified, even if the user does not upload an identity document, etc.

[0130] As described above, when identity verification has been completed for one of the payment service and the external service, the display control unit 103 may display on the selection screen SC2, SC6 or another screen that identity verification information related to identity verification can be linked with another service different from the one service. The one service is the payment service or the external service for which identity verification has been completed. The other service is the payment service or the external service for which identity verification has not been completed.

[0131] The display control unit 103 may display on the selection screens SC2, SC6, or other screens that payments based on payment sources requiring identity verification are provided in cooperation with an external service. For example, the display control unit 103 displays a message such as "Payments based on accounts at other banks are provided in cooperation with an external service" in panel P20 of the selection screen SC6. The display control unit 103 may also display a similar message on other screens. Data necessary for displaying the message is assumed to be stored in the data storage unit 100. In addition to the message, the display control unit 103 may also use an image such as an icon to display that payments based on payment sources requiring identity verification are provided in cooperation with an external service.

[0132] In the payment system 1 of Variation 7, when identity verification has been completed in one of the payment service and the external service, the selection screen SC2, SC6, or another screen displays that identity verification information related to identity verification can be linked with the other service different from the one service. This allows the user to link identity verification information, eliminating the need for identity verification in both the payment service and the external service, and the payment system 1 can improve user convenience.

[0133] [6-8. Variation 8] For example, the display request receiving unit 101 may receive a request to display a selection screen for the user to select a service usage function related to the use of available services available from the payment service as a function related to the payment service. In Variation 8, an example is taken of a case where apps for available services are prepared. Furthermore, an example is taken of a case where the payment app is a super app and the apps for available services are mini apps. A super app is an app that manages multiple mini apps. A mini app is an app called from the super app. An app for an available service that is available to the user through the service usage function may be a normal app that does not fall under the category of a mini app. An available service does not necessarily require the use of an app. A user may use an available service by other means, such as a browser, rather than an app. The manner in which an app is used is an example of payment system 1 in Variation 8. This point is also true for Variations 9 and 10.

[0134] Note that the mini-apps of Variation 8 include apps that operate based on the payment app as a super app, but also include apps for transitioning to apps provided by linked server 20 or other servers via the payment app. Furthermore, mini-apps may also include apps for transitioning to website screen displays, etc., via the payment app. In Variation 8, since the user uses available services from an app, it can also be said that the user uses an app usage function as an example of a service usage function. When a display request is received, status information acquisition unit 102 of Variation 8 acquires status information of identity verification for use of available services. While this differs from the embodiment in that the status information indicates the status of identity verification for the service usage function, the process by status information acquisition unit 102 to acquire the status information may be the same as that of the embodiment.

[0135] FIG. 10 is a diagram showing an example of a selection screen SC7 of Modification 8. The top screen SC1 in the upper left of FIG. 10 is the same as the top screen SC1 in the upper left of FIG. 2. For example, the top screen SC1 includes an app list L13 that displays a list of mini apps. When the user performs an operation to display all apps from the app list L13, a selection screen SC7 is displayed that allows the user to select an app from all apps. The selection screen SC7 displays icons representing multiple apps. The user can select an app by selecting an icon. The display control unit 103 may display the identity verification status in the app list L13 of the top screen SC1. In other words, the selection screen in the present disclosure includes not only the selection screen SC7 but also the top screen SC1.

[0136] The display control unit 103 of Modification 8 displays the status of identity verification for use of available services on the selection screen SC7. For example, the display control unit 103 displays the identity verification status in association with an app that requires identity verification among the apps of multiple available services based on the status information. Associating a status with an app means displaying the status within or near an icon for selecting the app. In the example at the top right of FIG. 10 , the status information indicates that identity verification has not been completed. The display control unit 103 displays a speech bubble indicating that identity verification has not been completed in association with an app that requires identity verification (for example, an app for "installment payment," "check-in," or "coupon"). As described in the embodiment, the status may be displayed in any manner. The status display method is not limited to displaying an image such as a speech bubble.

[0137] In the example at the bottom right of FIG. 10, the status information indicates that identity verification has been completed. The display control unit 103 displays a balloon indicating that identity verification has been completed in association with an app that requires identity verification (for example, an app for "installment payment," "check-in," or "coupon"). For apps that do not require identity verification, a balloon indicating information other than identity verification may be displayed. Note that data indicating apps that require identity verification is assumed to be stored in advance in the data storage unit 100. The display control unit 103 can identify which apps require identity verification by referring to the data.

[0138] The payment system 1 of the eighth modification displays the identity verification status for using the available services on the selection screen SC7, which allows the user to select a service usage function related to the use of the available services available from the payment service, as a function related to the payment service. This allows the payment system 1 to improve the convenience for users who use the service usage function.

[0139] [6-9. Variation 9] For example, an app for an available service in Variation 8 requires identity verification in order for a user to use the app. Once a user completes identity verification within an app for a certain available service, the app becomes available. As described in the embodiment, a user can also complete identity verification from a payment app. If a user completes identity verification from the payment app, identity verification within the app may be omitted. In other words, once identity verification from the payment service is completed, the app may be available for use without identity verification from the app.

[0140] FIG. 11 is a diagram showing an example of a selection screen SC7 of Modification 9. In the example at the top left of FIG. 11, the user has not yet completed identity verification. In this case, the display control unit 103 displays on the selection screen SC7 that identity verification has not been completed. The process for displaying the selection screen SC7 at the top left of FIG. 11 is as described in Modification 8. When the status information indicates that identity verification has been completed from the payment service, the display control unit 103 of Modification 9 displays on the selection screen SC7, as the identity verification status, that available services are available even if identity verification is not performed from the available services.

[0141] For example, as shown in the upper right of FIG. 11 , the display control unit 103 causes the user terminal 30 to display a selection screen SC2 for the charge source setting function described in the embodiment. When the user completes identity verification using the same procedure as in the embodiment, the display control unit 103 causes the user terminal 30 to display an identity verification screen SC3 indicating that identity verification has been completed, as shown in the lower left of FIG. 11 . When the user then performs an operation to display a selection screen SC7 for the service usage function, the display control unit 103 displays a message indicating that the app can be used without identity verification from the app in a speech bubble near the icon of each app on the selection screen SC7 based on the status information, as shown in the lower right of FIG. 11 . The process for displaying the selection screen SC7 in the lower right of FIG. 11 is as described in Modification Example 8.

[0142] In the payment system 1 of Variation 9, when the status information indicates that identity verification from the payment service has been completed, the selection screen SC2 displays, as the identity verification status, that the available service is available even if identity verification from the available service is not performed. This allows the user to understand that the available service is available even if identity verification is not performed before selecting the available service, so the payment system 1 can improve user convenience. For example, the payment system 1 can lower the psychological barrier for the user to use the available service. In other words, the payment system 1 can motivate the user to use the available service.

[0143] [6-10. Variation 10] For example, among the available services in Modifications 8 and 9, there may be an app that the user is not interested in. For this reason, the payment system 1 may estimate the availability of the available service for the user and display the identity verification status based on the availability. For example, a user who has purchased an airline ticket or made a payment at a travel agency may be interested in an available service that accepts applications for travel insurance, so the identity verification status may be displayed in the app for that available service displayed on the service usage function selection screen SC7. Identity verification is also required for that available service.

[0144] The payment system 1 of the tenth modification includes an estimation unit 108. The estimation unit 108 estimates the user's availability to use the available service based on user information about the user. The user information may be any information about the user. For example, the user information may be demographic information, information about the user's usage history of the payment service, information about the user's usage history of other services, or other information. The availability may be a binary value indicating whether or not the user uses the available service, or may be the degree to which the user uses the available service. In the tenth modification, an example is given in which the availability is expressed numerically, but the availability may also be expressed in other formats such as letters or symbols.

[0145] For example, the data storage unit 100 stores availability data indicating a relationship between user information and the availability of each available service. The availability data may be in any format. For example, the availability data may be in the form of a mathematical formula, a table, a part of a program, a machine learning model, or any other format. The estimation unit 108 estimates the availability of each available service associated with the user information based on the availability data. For example, the estimation unit 108 estimates that a specific available service will be used if an attribute indicated by the user information is a predetermined attribute. The estimation unit 108 estimates that a specific available service will be used if a user performs a predetermined action in a payment service or other service.

[0146] The display control unit 103 of the tenth modification displays the identity verification status for use of the available services on the selection screen SC2 based on the status information and the availability. For example, the display control unit 103 does not display the identity verification status for available services that are not estimated to be available among the multiple available services, and displays the identity verification status for available services that are estimated to be available.

[0147] The payment system 1 of Variation 10 displays the identity verification status for use of available services on the selection screen SC2 based on the status information and availability. This allows the user to understand the identity verification status for use of the available service in which they are interested before selecting the service, thereby improving the user's visibility on the selection screen SC2. Furthermore, because the user can understand the status of the available service in advance, the payment system 1 can lower the psychological hurdle for the user to use the available service. In other words, the payment system 1 can motivate the user to use the available service.

[0148] [6-11. Other variations] For example, the above modifications may be combined.

[0149] For example, although the embodiment has been described with reference to an example in which a user uses a payment service through a payment app, the user may also use the payment service through the browser of the user terminal 30. In this case, the user may execute payment by having the code C10 displayed on the browser read at the store, or may execute payment online rather than at the store without using the code C10. Online payments are completed by simply operating the user terminal 30. For example, the user may execute payment for online e-commerce services, e-book services, travel reservation services, communication services, or other services through the browser.

[0150] For example, the functions described as being realized by the payment server 10 may be realized by the linked server 20, the user terminal 30, or another computer. The processes described as being realized by the payment server 10 may be shared among multiple computers. The processes described as being realized by the linked server 20 may be realized by the payment server 10. In this case, the payment server 10 will also have the function of managing accounts at other banks and executing payments based on the accounts at other banks.

[0151] [7. Notes] For example, the payment system can be configured as follows: (1) a display request receiving unit that receives a request to display a selection screen for a user to select a function related to the payment service; a status information acquisition unit that acquires status information regarding a status of identity verification of the user when the display request is accepted; a display control unit that displays the status on the selection screen based on the status information; Payment systems, including: (2) the display control unit, when the status information indicates that the identity verification has been completed, causes the selection screen to display, as the status, that the identity verification has been completed. (1) A payment system as described above. (3) the display control unit, when the user selects the function on the selection screen on which the status is displayed, enables transition to a next screen according to the status. A payment system according to (1) or (2). (4) the display control unit, when the status information indicates that the identity verification has been completed and the user selects the function on the selection screen, enables the user to transition to the next screen for using the function. (3) A payment system as described in (3). (5) the payment service has a plurality of functions that require the identity verification, the display control unit causes the status to be displayed on the selection screen for each of the plurality of functions. A payment system according to any one of (1) to (4). (6) the display control unit is capable of transitioning to an identity verification screen for the user to perform the identity verification when the status information indicates that the identity verification has not been completed and the user selects any one of the plurality of functions. (5) A payment system as described in (5). (7) when the user completes the identity verification from the identity verification screen, the display control unit displays, as the status, on the selection screen of the function other than the function selected by the user among the plurality of functions, that the identity verification has been completed. (6) A payment system as described in (6). (8) the display control unit displays the status on the selection screen, from which the user can select the function requiring the identity verification and the function not requiring the identity verification, in association with the function requiring the identity verification. A payment system according to any one of (1) to (7). (9) the display control unit displays the status on the selection screen for the user to select the function realized by the payment service and the external service cooperating with each other; A payment system according to any one of (1) to (8). (10) the status information acquisition unit acquires the status information associated with the terminal identification information of the user terminal that transmitted the display request, based on a database in which terminal identification information capable of identifying each of a plurality of user terminals is associated with the status information of the identity verification performed from the user terminal; the display control unit causes the status to be displayed on the selection screen of the user terminal based on the status information associated with the terminal identification information of the user terminal that has transmitted the display request; A payment system according to any one of (1) to (9). (11) the status information acquisition unit acquires the status information associated with the user identification information of the user who transmitted the display request, based on a database in which user identification information capable of identifying each of the plurality of users is associated with the status information of the user's identity verification; the display control unit causes the status to be displayed on the selection screen of the user who transmitted the display request, based on the status information associated with the user identification information of the user. A payment system according to any one of (1) to (10). (12) The payment system includes: a determination unit that determines whether or not re-identification of the user is necessary when the user's identity has been confirmed; an update unit that updates the status information so that the status information indicates that the identity verification is required again based on the determination result of the determination unit; Further comprising: When the status information is updated, the display control unit displays, on the selection screen based on the updated status information, the status indicating that the identity verification is required again. A payment system according to any one of (1) to (11). (13) the display request receiving unit receives, as the function, the display request for the selection screen for the user to select a charge source setting function related to setting of a charge source used for charging in the payment service; the status information acquisition unit acquires the status information of the identity verification for setting the charge source when the display request is accepted, The display control unit displays the status of the identity verification for setting the charge source on the selection screen. A payment system according to any one of (1) to (12). (14) the display request receiving unit receives, as the function, the display request for the selection screen for the user to select a payment source setting function related to setting of a payment source to be used for payment in the payment service; the status information acquisition unit acquires the status information of the identity verification for setting the payment source when the display request is accepted; the display control unit causes the selection screen to display the status of the identity verification for setting the payment source. A payment system according to any one of (1) to (13). (15) The payment system includes: an authentication request unit that requests authentication for the payment from the user when the payment is made based on the payment source for which the identity verification is required; a payment authorization unit that authorizes the payment if the authentication is successful; The payment system according to (14), further comprising: (16) the payment based on the payment source for which the identity verification is required is provided through collaboration between the payment service and an external service; When the identity verification has been completed in one of the payment service and the external service, the display control unit displays on the selection screen or another screen that identity verification information related to the identity verification can be linked to another service different from the one service. A payment system according to any one of (1) to (15). (17) the display request receiving unit receives, as the function, the display request for the selection screen for the user to select a service use function related to the use of an available service available from the payment service; the status information acquisition unit acquires the status information of the identity verification for use of the available service when the display request is accepted; the display control unit causes the selection screen to display the status of the identity verification for use of the available service. A payment system according to any one of (1) to (16). (18) When the identity verification is completed by the payment service, the available service can be used without the identity verification being performed by the available service, When the status information indicates that the identity verification from the payment service has been completed, the display control unit displays, on the selection screen, as the status, that the available service is available even if the identity verification from the available service has not been performed. (17) A payment system according to (17). (19) The payment system further includes an estimation unit that estimates availability of the user to use the available service based on user information about the user; the display control unit displays the status of the identity verification for use of the available service on the selection screen based on the status information and the availability. A payment system according to (17) or (18). [Explanation of symbols]

[0152] 1 Payment system, N network, 10 Payment server, 11, 21, 31 Control unit, 12, 22, 32 Memory unit, 13, 23, 33 Communication unit, 20 Linkage server, 30 User terminal, 34 Operation unit, 35 Display unit, 36 Photography unit, 100 Data storage unit, 101 Display request reception unit, 102 Status information acquisition unit, 103 Display control unit, 104 Determination unit, 105 Update unit, 106 Authentication request unit, 107 Payment permission unit, 108 Estimation unit, 200 Data storage unit, 201 Linkage unit, 300 Data storage unit, 301 Operation reception unit, 302 Display control unit, B11, B12, B40 Button, C10 Code, DB User database, L13 App list, P20 Panel, P60 Panel, SC1 Top screen, SC2 Selection screen, SC3 Identity verification screen, SC4 account information input screen, SC5 charge screen, SC6 selection screen, SC7 selection screen.

Claims

[Claim 1] a display request receiving unit that receives a request to display a selection screen for a user to select a function related to the payment service; a status information acquisition unit that acquires status information regarding a status of identity verification of the user when the display request is accepted; a display control unit that displays the status on the selection screen based on the status information; Payment systems, including:

Images