Settlement system, proposal method, and program

Abstract

To propose application information regarding an application of related service related to settlement implemented by a user.SOLUTION: When a user, who uses settlement service, implements settlement by using a user terminal (30), a settlement information acquisition unit (102) of a settlement system (1) acquires settlement information regarding the settlement. An application information acquisition unit (103) acquires application information regarding an application of related service related to settlement on the basis of the settlement information. A proposal unit (104) proposes the application information to the user with the user terminal (30).SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present disclosure relates to a payment system, a proposal method, and a program.

Background Art

[0002] Conventionally, a payment service in which a user executes a payment using a user terminal has been known. For example, in Patent Document 1, when a user executes a payment using a payment app installed on the user terminal, the payment server selects an investment product based on the payment amount information and proposes the purchase of the selected investment product via a finance app, which is a mini app launched within the payment app.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the technology of Patent Document 1, since investment products are only proposed to the user via the finance app, which is a mini app, the user may not be aware of the existence of various mini apps that can be launched within the payment app of Patent Document 1, or may not be aware of the existence of mini apps that are suitable for the user. The same applies to apps other than mini apps.

[0005] One object of the present disclosure is to propose app information regarding apps for related services related to a payment executed by a user.

Means for Solving the Problems

[0006] When a user who uses a payment service executes a payment using a user terminal, the payment system according to the present disclosure includes a payment information acquisition unit that acquires payment information related to the payment, an application information acquisition unit that acquires application information related to an application of a related service related to the payment based on the payment information, and a proposal unit that proposes the application information to the user on the user terminal.

Advantages of the Invention

[0007] The present disclosure can propose application information related to an application of a related service related to a payment executed by a user.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Embodiments for Carrying Out the Invention

[0009] [1. Hardware Configuration of Payment System] An example of an embodiment of a settlement system, a proposal 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 the settlement system. For example, the settlement system 1 includes a settlement server 10, a related server 20, a user terminal 30, and a store terminal 40. Each of the settlement server 10, the related server 20, the user terminal 30, and the store terminal 40 is connected to a network N such as the Internet or a LAN.

[0010] The settlement server 10 is a server computer for settlement services. The settlement service is a service that provides users with electronic settlement (cashless settlement). For example, the settlement server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The storage unit 12 includes at least one of a volatile memory such as a RAM and a non-volatile memory such as a 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 related server 20 is a server computer for related services. The related service is a service related to settlement. The related service can also be said to be a service that cooperates with the settlement service. In other words, the related service can also be said to be a service accessible via a settlement application that provides the settlement service. In the present embodiment, an example is given where the service provided by the card company that issued the credit card available for the settlement service corresponds to the related service, but the related service may be other services. For example, the related service may be an e-commerce service, an online free market service, a travel reservation service, a communication service, a financial service, a video distribution service, or other services. For example, the related server 20 includes a control unit 21, a storage unit 22, and a communication unit 23. The hardware configurations of the control unit 21, the storage unit 22, and the communication unit 23 may be the same as those of the control unit 11, the storage unit 12, and the communication unit 13, respectively.

[0012] The user terminal 30 is the 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 storage unit 32, a communication unit 33, an operation unit 34, a display unit 35, and a photographing unit 36. The hardware configurations of the control unit 31, the storage unit 32, and the communication unit 33 may be the same as those of the control unit 11, the storage 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 a liquid crystal or an organic EL. The photographing unit 36 includes at least one camera.

[0013] The store terminal 40 is the computer of a store that subscribes to the payment service. For example, the store terminal 40 is a POS terminal, a handy terminal, a smartphone, a tablet, or a personal computer. The store terminal 40 includes a control unit 41, a storage unit 42, a communication unit 43, an operation unit 44, a display unit 45, and a reading unit 46. The hardware configurations of the control unit 41, the storage unit 42, the communication unit 43, the operation unit 44, and the display unit 45 may be the same as those of the control unit 11, the storage unit 12, the communication unit 13, the operation unit 34, and the display unit 35, respectively. The reading unit 46 includes at least one code reader or a reader / writer. The reading unit 46 may include at least one camera.

[0014] Note that the programs stored in the storage units 12, 22, 32, and 42 may be supplied to the payment server 10, the related server 20, the user terminal 30, or the store terminal 40 via the network N. Also, at least one of a reading unit (for example, a memory card slot) that reads a computer-readable information storage medium and an input / output unit (for example, a USB port) for inputting / outputting data to / from an external device may be included in the payment server 10, the related server 20, the user terminal 30, or the store terminal 40. For example, a program stored in the information storage medium may be supplied to the payment server 10, the related server 20, the user terminal 30, or the store terminal 40 via at least one of the reading unit and the input / output unit.

[0015] Also, the payment system 1 may include at least one computer. The computers included in the payment system 1 are not limited to the example of FIG. 1. For example, the payment system 1 may include only the payment server 10 and the user terminal 30. In this case, the related server 20 and the store terminal 40 exist outside the payment system 1. The payment system 1 may include only the payment server 10. In this case, the related server 20, the user terminal 30, and the store terminal 40 exist outside the payment system 1. For example, the payment system 1 may include the payment server 10 and other computers not shown in FIG. 1.

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

[0017] In this embodiment, an example is given where the user executes payment using the payment application installed on the user terminal 30. The payment application is an application provided by the operator who operates the payment service. When the user installs the payment application on the user terminal 30 and registers as a member of the payment service, the user can use the payment service. When the user completes the membership registration and launches the payment application, the user terminal 30 causes the display unit 35 to display the top screen of the payment application. The top screen is the screen that is first displayed after the payment application is launched. The top screen may also be called the first view.

[0018] FIG. 2 is a diagram showing an example of a screen displayed on the user terminal 30. For example, when the payment application is launched, as shown in the upper left of FIG. 2, the user terminal 30 causes the display unit 35 to display 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 by the reading unit 46 of the store terminal 40, payment is executed based on the code ID obtained from the code C10. In the example of FIG. 2, since a credit card is set as the payment source, payment based on the credit card is executed. The processing for payment may be a known process.

[0019] Note that the payment is not limited to the type in which the code C10 displayed on the user terminal 30 is read by the store terminal 40. The payment may be of any type. For example, the payment may be of a type in which the code displayed on the store terminal 40 is read by the user terminal 30, a type in which the code posted in the store is read by the user terminal 30, a type that is completed only by an operation on the user terminal 30, a type in which the IC chip of the user terminal 30 is used, or other types.

[0020] In this embodiment, according to the payment amount in the payment, a payment installment application for making an installment payment afterwards is proposed to the user on a payment completion screen SC2 indicating that the payment has been completed. The payment installment application is an application provided by the card company of the credit card used in the payment. In this embodiment, an example is given in which the payment application is a super application and the payment installment application is a mini application. A super application is an application that manages a plurality of mini applications. A mini application is an application that is called from a super application. Note that the mini application in this embodiment includes an application that operates based on the payment application as a super application, but also includes an application for transitioning to an application provided by the related server 20 via the payment application. Further, the mini application may include an application for transitioning to a screen display of a website or the like via the payment application. As shown in the upper left of FIG. 2, the top screen SC1 includes an application list L11 showing a list of mini applications.

[0021] For example, the user can also launch the installment payment application from the application list L11 on the top screen SC1. However, for high-value payments, the installment payment application can be directly launched from the payment completion screen SC2. When the user's payment amount is equal to or greater than the threshold, as shown in the upper right of FIG. 2, the user terminal 30 causes the display unit 35 to display a payment completion screen SC2 including application information I20 indicating the installment payment application. Since the probability that a user who has made a high-value payment wishes to use installment payment is high, the user can directly perform the installment payment procedure from the payment completion screen SC2.

[0022] For example, when the user selects the application information I20 of the installment payment application, as shown in the lower right of FIG. 2, the user terminal 30 launches the installment payment application and causes the display unit 35 to display an application screen SC3 for installment payment. Generally, on a screen for managing the usage status of a credit card, it may take several days for the payment to be reflected. However, in this embodiment, it is assumed that payment information is transmitted from the payment application to the installment payment application. Based on the said information, the user terminal 30 can cause the display unit 35 to display an application screen SC3 for accepting an installment payment application immediately after the payment.

[0023] On the other hand, when the user's payment amount is less than the threshold, since the payment amount is low, the probability that the user wishes to use the installment payment application is low. Therefore, as shown in the lower left of FIG. 2, the user terminal 30 causes the display unit 35 to display a payment completion screen SC2 that does not include the application information I20 of the installment payment application. For example, when the user's payment amount is less than the threshold, the payment completion screen SC2 includes other information I21 indicating advertisements for other services such as e-commerce services. When the user's payment amount is less than the threshold, the payment completion screen SC2 may include the application information I20 of an application other than the installment payment application (for example, an application for point management).

[0024] As described above, when the user executes a payment using the user terminal 30, the payment system 1 of this embodiment determines whether or not the payment amount of the payment is equal to or greater than a threshold value. When it is determined that the payment amount of the payment is equal to or greater than the threshold value, the payment system 1 causes the application information I20 of the installment payment application to be displayed on the payment completion screen SC2. Thereby, the payment system 1 can propose to the user an installment payment application that is highly likely to be used by the user who has executed a high-value payment.

[0025] On the other hand, when it is determined that the payment amount of the payment is less than the threshold value, the payment system 1 causes the application information I20 of an application other than the installment payment application or other information I21 such as an advertisement of another service to be displayed on the payment completion screen SC2. Thereby, when the probability that the user uses the installment payment application is low, the payment system 1 can propose other useful information to the user. Hereinafter, the details of the payment system 1 will be described.

[0026] [3. Functions Realized by the Payment System] FIG. 3 is a diagram showing an example of functions realized by the payment system 1. Each part realized by the payment system 1 can be configured by being integrated into one device or by further dispersing the device more finely.

[0027] [3-1. Functions Realized by the Payment Server] For example, the payment server 10 includes a data storage unit 100, a payment execution unit 101, a payment information acquisition unit 102, an application information acquisition unit 103, and a proposal unit 104. The data storage unit 100 is realized by the storage unit 12. Each of the payment execution unit 101, the payment information acquisition unit 102, the application information acquisition unit 103, and the proposal unit 104 is realized by the control unit 11.

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

[0029] FIG. 4 is a diagram showing an example of a user database DB. The user database DB is a database in which various types of information about users are stored. For example, the user database DB stores a user ID, a password, a code ID, payment means information, and payment history information. Other data may be stored in the user database DB. For example, the user database DB may store payer information regarding the payment means set as the payer by the user, or charge source information regarding the payment means set as the charge source of the electronic money by the user.

[0030] The user ID is an example of user identification information that can identify a user. Separately from the user ID, there may be an account for login. The login account may be allowed to be freely changed by the user. The password is information that is confirmed at the time of login. The code ID is also an ID that can identify the user in the payment service. The code ID is updated every time the code C10 is displayed.

[0031] The payment means information is information that can identify the payment means available to the user in the payment service. For example, the payment means information is information such as a credit card number, information such as an electronic money number, or information such as a remaining balance of a point card number. The payment history information is information regarding the usage history of the payment service by the user. For example, the payment history information indicates the payment date and time, the payment location, the payment amount, the payment target, or a combination thereof. When the user executes a payment, the payment execution unit 101 described later updates the payment history information so as to indicate the details of the payment.

[0032] Note that the data stored in the data storage unit 100 is not limited to the above example. The data storage unit 100 may store data necessary for the payment service. For example, the data storage unit 100 may store data of various screens displayed on the payment application.

[0033] [Payment Execution Unit] The settlement execution unit 101 executes the settlement in the settlement service. The processing for settlement may be known processing. In the case of settlement of the type where the code C10 displayed on the user terminal 30 is read by the store terminal 40 as in this embodiment, the settlement execution unit 101 executes the settlement based on the settlement request received from the store terminal 40. The settlement execution unit 101 refers to the user database DB and executes the settlement based on the settlement means information associated with the code ID included in the settlement request received from the store terminal 40. For example, if the user has set a credit card as the payment source, the settlement execution unit 101 executes the settlement based on information such as the credit card number indicated by the settlement means information. It is assumed that information such as the settlement amount necessary for the settlement is also included in the settlement request.

[0034] Note that the processing executed by the settlement execution unit 101 is not limited to the above example. In the case of settlement of the type where the code displayed on the store terminal 40 is read by the user terminal 30, the type where the code posted in the store is read by the user terminal 30, the type that is completed only by an operation on the user terminal 30, the type where the IC chip of the user terminal 30 is used, or other types of settlement, the settlement execution unit 101 may obtain the information necessary for the settlement by communicating with at least one of the user terminal 30 and the store terminal 40 and execute the settlement. When the settlement execution unit 101 executes the settlement, it updates the settlement history information of the user so as to indicate the content of the executed settlement.

[0035] [Settlement Information Acquisition Unit] The settlement information acquisition unit 102 acquires settlement information regarding the settlement when a user who uses the settlement service executes the settlement using the user terminal 30. For the user to execute the settlement using the user terminal 30 means that the user performs an operation for settlement from the user terminal 30. For example, an operation to start the settlement application, an operation to display the code C10, an operation to cause the store terminal 40 to read the code C10, or other operations performed by the user correspond to the user executing the settlement using the user terminal 30. The information processing for the execution of the settlement is executed by the settlement execution unit 101.

[0036] In this embodiment, when the user executes a payment using the payment application on the user terminal 30, the payment information acquisition unit 102 acquires payment information. The payment information may be any information related to the content of the payment. For example, the payment information is all or part of the information included in the payment request received by the payment server 10 from at least one of the user terminal 30 and the store terminal 40. The payment information may be information indicating the execution result of the payment instead of the information included in the payment request. That is, the payment information may be information indicating whether the payment has been executed or not.

[0037] In this embodiment, the payment information acquisition unit 102 acquires payment information indicating the payment amount in the payment. For example, the payment information indicating the payment amount is included in the payment request. The payment information acquisition unit 102 acquires the payment information included in the payment request. After the payment is executed, since the payment amount is indicated in the payment history information, the payment information acquisition unit 102 may acquire the payment information by acquiring the information of the part indicating the payment amount in the payment history information. Note that the payment information may indicate other contents than the payment amount. Other examples of the payment information will be described in the modification examples below.

[0038] [Application Information Acquisition Unit] Based on the payment information, the application information acquisition unit 103 acquires application information I20 regarding an application of a related service related to the payment. In this embodiment, the case where the application information acquisition unit 103 acquires the application information I20 regarding the mini application in the payment application is taken as an example. That is, the case where the application of the related service is a mini application is taken as an example, but the application of the related service may be a normal application that is not a mini application. A normal application is an application that can be launched from a location other than the payment application which is a super application. For example, an application whose icon is displayed on the home screen of the OS of the user terminal 30 corresponds to a normal application. The application of the related service is an application distributed by a business operator that provides related services to the user.

[0039] The app information I20 may mean data related to the app, but in this embodiment, it means an object (such as an image or text, etc.) that visually appears on the payment completion screen SC2. Assume that the actual data for displaying the app information I20 is pre-stored in the data storage unit 100. The app information acquisition unit 103 acquires the app information I20 by acquiring the actual data. The actual data for displaying the app information I20 may not be pre-stored in the data storage unit 100, but may be dynamically generated on the spot. In this case, assume that the data that is the source of the app information I20 is stored in the data storage unit 100. The app information acquisition unit 103 may generate the app information I20 based on the source data.

[0040] In this embodiment, since the service of the card company that issued the credit card set by the user as the payer corresponds to the related service, the app information acquisition unit 103 acquires the app information I20 of the installment payment app provided by the card company. For example, the app information acquisition unit 103 acquires the app information I20 based on the payment amount indicated by the payment information. The app information acquisition unit 103 determines whether the payment amount indicated by the payment information is equal to or greater than a threshold value. The threshold value is the amount that serves as the criterion for determining whether to display the app information I20. The threshold value may be common to all users, or may be determined according to the user. For example, the threshold value may be set for each demographic information such as the user's gender or age group. Assume that the threshold value is stored in the data storage unit 100.

[0041] For example, when it is determined that the payment amount indicated by the payment information is equal to or greater than the threshold value, the app information acquisition unit 103 acquires the app information I20 of the installment payment app. When it is determined that the payment amount indicated by the payment information is less than the threshold value, the app information acquisition unit 103 does not acquire the app information I20 of the installment payment app. In the example of FIG. 2, when it is determined that the payment amount indicated by the payment information is less than the threshold value, the app information acquisition unit 103 acquires other information I21 such as an advertisement that is displayed instead of the app information I20. Assume that the data of the other information I21 is also stored in the data storage unit 100.

[0042] In addition, when it is determined that the settlement amount indicated by the settlement information is less than the threshold value, the application information acquisition unit 103 may acquire the application information I20 of an application other than the installment payment application. That is, when it is determined that the settlement amount indicated by the settlement information is equal to or greater than the threshold value, the application information acquisition unit 103 acquires the application information I20 of the first application (in this embodiment, the installment payment application), and when it is determined that the settlement amount indicated by the settlement information is less than the threshold value, the application information acquisition unit 103 may acquire the application information I20 of a second application different from the first application (in this embodiment, an application other than the installment payment application).

[0043] An application other than the installment payment application is an application with a high probability that a user who has performed a low-amount settlement is interested in. For example, the other application may be a point management application for the user to manage their own points, an advertising application where the user can obtain points by viewing advertisements, an application for the user to take and upload receipts, or a coupon application for the user to obtain coupons. These other applications may be mini-applications. The actual data for the display of the application information I20 of these other applications may be stored in advance in the data storage unit 100.

[0044] [Proposal Department] The proposal unit 104 proposes app information I20 to the user on the user terminal 30. In the present embodiment, the proposal unit 104 proposes the app information I20 to the user in the payment app of the user terminal 30. Proposing the app information I20 to the user means transmitting data for displaying the app information I20 to the user terminal 30 or another computer. In the present embodiment, the proposal unit 104 proposes the app information I20 to the user on the payment completion screen SC2 displayed on the user terminal 30 when the payment is completed. The payment completion screen SC2 is a screen indicating that the payment has been completed. For example, on the payment completion screen SC2, a message indicating that the payment has been completed, the payment location, the payment date and time, the payment amount, the payment target, or a combination of these is displayed. In the present embodiment, the case where the proposal unit 104 displays the payment completion screen SC2 itself is taken as an example, but the payment completion screen SC2 may be displayed by another function other than the proposal unit 104. Regardless of the form of the proposal of the app information I20, the proposal unit 104 may propose the app information I20 to the user on the payment completion screen SC2 by displaying the app information I20 over the payment completion screen SC2 in a pop-up or a new screen on the payment completion screen SC2.

[0045] For example, when the payment is completed and the app information acquisition unit 103 acquires the app information I20, the proposal unit 104 generates display data of the payment completion screen SC2 including the app information I20. The display data is data for causing the user terminal 30 to display some screen. When a browser is used, the display data is HTML data. When a dedicated app such as a payment app is used, it is data (for example, HTML data or image data) used when causing the app to display some screen. The proposal unit 104 proposes the app information I20 to the user by transmitting the display data of the payment completion screen SC2 including the app information I20 to the user terminal 30.

[0046] In this embodiment, when the settlement amount indicated by the settlement information is equal to or greater than the threshold value, the proposal unit 104 proposes the application information I20 indicating the installment payment application to the user. When the settlement amount indicated by the settlement information is less than the threshold value, the proposal unit 104 does not propose the application information I20 indicating the installment payment application to the user. In the example of FIG. 2, when the settlement amount indicated by the settlement information is less than the threshold value, the proposal unit 104 proposes other information I21 such as an advertisement for another service to the user. The proposal unit 104 may not make any proposal particularly when the settlement amount indicated by the settlement information is less than the threshold value. For example, when the settlement amount indicated by the settlement information is equal to or greater than the threshold value, the proposal unit 104 proposes the application information I20 of the first application (in this embodiment, the installment payment application) to the user, and when the settlement amount indicated by the settlement information is less than the threshold value, the proposal unit 104 may propose the application information I20 of the second application (in this embodiment, an application other than the installment payment application) to the user.

[0047] Note that the method of proposing the application information I20 is not limited to the above example. The proposal unit 104 may propose the application information I20 to the user by transmitting data for displaying the application information I20 to the user terminal 30 or another computer. For example, the proposal unit 104 may propose the application information I20 to the user by displaying the application information I20 on a screen other than the settlement completion screen SC2 among the screens displayed on the settlement application. The proposal unit 104 may propose the application information I20 to the user by using means other than the settlement application. The other means may be e-mail, SMS, push notification, banner notification, or other means.

[0048] [Functions Realized by the Related Server] For example, the related server 20 includes a data storage unit 200 and a related service providing unit 201. The data storage unit 200 is realized by the storage unit 22. The related service providing unit 201 is realized by the control unit 21.

[0049] [Data Storage Unit] The data storage unit 200 stores data necessary for related services. For example, the data storage unit 200 stores a database in which various information about users who use related services is stored. In this embodiment, since the service provided by the card company that issued the credit card corresponds to the related service, various information about the credit card is stored in the database. For example, the database stores the credit card number, expiration date, cardholder name, usage history of the credit card, payment methods such as lump-sum payment or installment payment, or other information. The data storage unit 200 may store data according to the related service.

[0050] [Related Service Provision Unit] The related service provision unit 201 provides related services to the user based on the data stored in the data storage unit 200. In this embodiment, since the service provided by the card company that issued the credit card corresponds to the related service, the related service provision unit 201 provides various services including a service for viewing the usage history of the credit card and a service for changing payment methods such as lump-sum payment or installment payment. In the example of FIG. 2, the related service provision unit 201 displays the application screen SC3 on the user terminal 30 and accepts an application for installment payment from the user. The process of accepting an application for installment payment may be a known process.

[0051] [3-3. Functions Implemented on the User Terminal] 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 implemented by the storage unit 32. The operation reception unit 301 and the display control unit 302 are implemented by the control unit 31.

[0052] [Data Storage Unit] The data storage unit 300 stores data necessary for the user to use the payment service. For example, the data storage unit 300 stores a payment application. When the user uses the payment service from a browser instead of a payment application, the data storage unit 300 stores the browser.

[0053] [Operation Reception Unit] The operation reception unit 301 receives various operations of the user. For example, the operation reception unit 301 receives operations on the payment application. The operation reception unit 301 transmits data indicating the operation content of the user to the payment server 10.

[0054] [Display Control Unit] The display control unit 302 causes various screens to be displayed on the display unit 35. For example, the display control unit 302 causes the top screen SC1, the payment completion screen SC2, and the application screen SC3 to be displayed on the display unit 35. The display control unit 302 communicates with the payment server 10, the related server 20, or another computer, receives data necessary for the display of these screens, and causes these screens to be displayed on the display unit 35.

[0055] [3-4. Functions Implemented by the Store Terminal] For example, the store terminal 40 includes a data storage unit 400 and a payment execution unit 401. The data storage unit 400 is realized by the storage unit 42. The payment execution unit 401 is realized by the control unit 41.

[0056] [Data Storage Unit] The data storage unit 400 stores data necessary for providing payment services to the user. For example, the data storage unit 400 stores a database in which various information such as the prices of products or services handled by the store is stored. The data storage unit 400 also stores information on the products or services to be paid for by the user. The data storage unit 400 may store information on the location where the store terminal 40 is located.

[0057] [Payment Execution Unit] The payment execution unit 401 provides payment services to the user. For example, when the store terminal 40 reads the code C10 with the reading unit 46, the payment execution unit 401 acquires the code ID from the code C10. The payment execution unit 401 acquires the payment amount based on the reading result of the barcode of the product or the like. The payment execution unit 401 transmits a payment request including information necessary for payment, such as the code ID, the payment amount, and the location of the store, to the payment server 10. The payment request may be a request used in a known payment service. The payment execution unit 401 acquires the execution result of the payment from the payment server 10 and completes the payment in the store. These series of processes may also be processes adopted in a known payment service.

[0058] [4. Processes Executed in the Payment System] FIG. 5 is a diagram showing an example of the processes executed in the payment system 1. The processes in FIG. 5 are executed by the control units 11, 21, 31, 41 executing the programs stored in the storage units 12, 22, 32, 42, respectively.

[0059] As shown in FIG. 5, when the payment application is launched on the user terminal 30, the payment server 10 executes a process for displaying the top screen SC1 between the payment server 10 and the user terminal 30 (S1). In S1, the payment server 10 logs the user in to the payment service, generates a code ID, and transmits the display data of the top screen SC1 to the user terminal 30. The user causes the store terminal 40 to read the code C10. When the store terminal 40 reads the code C10 with the reading unit 46 (S2), the store terminal 40 extracts the code ID from the code C10 and transmits a payment request to the payment server 10 (S3). When the payment server 10 receives the payment request (S4), the payment server 10 executes the payment based on the payment request (S5).

[0060] The settlement server 10 refers to the settlement request received in S4 and acquires settlement information indicating the settlement amount of the settlement executed in S5 (S6). The settlement server 10 determines whether the settlement amount indicated by the settlement information acquired in S6 is equal to or greater than a threshold value (S7). In S7, if it is determined that the settlement amount is equal to or greater than the threshold value (S7: Y), the settlement server 10 acquires the app information I20 of the installment payment app (S8). The settlement server 10 executes a process for proposing the app information I20 of the installment payment app on the settlement completion screen SC2 to the user terminal 30 (S9). In S9, the settlement server 10 generates display data of the settlement completion screen SC2 including the app information I20 of the installment payment app and transmits it to the user terminal 30. The user terminal 30 causes the settlement completion screen SC2 as shown in the upper right of FIG. 2 to be displayed on the display unit 35.

[0061] The user terminal 30 determines whether the user has selected the app information I20 (S10). In S10, if it is determined that the user has not selected the app information I20 (S10: N), this process ends. In S10, if it is determined that the user has selected the app information I20 (S10: Y), the user terminal 30 executes a process for displaying the app screen SC3 to the associated server 20 (S11), and this process ends. In S11, the user terminal 30 transmits the settlement information to the installment payment app. The user terminal 30 transmits the settlement information to the associated server 20 via the installment payment app. The associated server 20 generates display data of the app screen SC3 and transmits it to the user terminal 30. Thereafter, a process for installment payment of the settlement executed in S5 is executed.

[0062] In S7, if it is determined that the settlement amount is less than the threshold value (S7: N), the settlement server 10 executes a process for displaying the settlement completion screen SC2 that does not include the app information I20 to the user terminal 30 (S12), and this process ends. In S12, the settlement server 10 generates display data of the settlement completion screen SC2 including other information I21 such as an advertisement and transmits it to the user terminal 30. The user terminal 30 causes the settlement completion screen SC2 as shown in the lower left of FIG. 2 to be displayed on the display unit 35 and executes a process according to the user's operation.

[0063] [Summary of Embodiment] When a user who uses a payment service executes a payment using the user terminal 30, the payment system 1 of the present embodiment acquires payment information regarding the payment. Based on the payment information, the payment system 1 acquires application information I20 regarding an application of a related service related to the payment. The payment system 1 proposes the application information I20 to the user on the user terminal 30. Thereby, the payment system 1 can propose the application information I20 of the related service related to the payment executed by the user to the user. For example, the payment system 1 can promote the use of applications by the user. Since the payment system 1 eliminates the need for the user to search for and launch a desired application from among the user terminals 30, the convenience of the user can be improved.

[0064] In addition, the payment system 1 proposes the application information I20 to the user on the payment completion screen SC2 displayed on the user terminal 30 when the payment is completed. Thereby, the payment system 1 can more effectively propose the application information I20 to the user by proposing the application information I20 on the payment completion screen SC2 that is easy for the user to notice.

[0065] In addition, the payment system 1 acquires payment information indicating the payment amount in the payment. The payment system 1 acquires the application information I20 based on the payment amount indicated by the payment information. Thereby, the payment system 1 can propose the application information I20 corresponding to the payment amount to the user. For example, the payment system 1 can improve the convenience of the user by proposing the application information I20 of an installment payment application that a user who has executed a high-value payment is likely to be interested in to the user. Conversely, the payment system 1 can improve the convenience of the user by proposing the application information I20 of a point management application that a user who has executed a low-value payment is likely to be interested in to the user.

[0066] In addition, when the user executes a payment using the payment app on the user terminal 30, the payment system 1 acquires payment information. The payment system 1 acquires app information I20 regarding the mini-app within the payment app. The payment system 1 proposes the app information I20 to the user in the payment app on the user terminal 30. Thereby, the app information I20 of the mini-app related to the payment executed by the user can be proposed to the user. For example, the payment system 1 can promote the use of the mini-app by the user.

[0067] [6. Modification Example] The present disclosure is not limited to the embodiments described above. The present disclosure can be appropriately changed without departing from the gist of the present disclosure.

[0068] FIG. 6 is a diagram showing an example of a function realized in the modification example. For example, the payment server 10 includes a usage status information acquisition unit 105, a change determination unit 106, another service information acquisition unit 107, a user attribute information acquisition unit 108, an app operation information acquisition unit 109, and a selection unit 110. Each of the usage status information acquisition unit 105, the change determination unit 106, the another service information acquisition unit 107, the user attribute information acquisition unit 108, the app operation information acquisition unit 109, and the selection unit 110 is realized by the control unit 11.

[0069] [6-1. Modification Example 1] For example, as described in the embodiment, on the top screen SC1 of the payment app, apps are displayed selectably in the app list L11 on the screen. The app list L11 may be included in other screens other than the top screen SC1. The app list L11 may be included in other screens other than the top screen SC1 corresponding to the so-called first view. For example, the app list L11 may be included in a screen displayed when the user selects a menu icon on the payment app, a screen showing the usage history of the payment app, or a screen for accepting the settings of the payment app.

[0070] When an app is displayed so that it can be selected, it means that when the user selects the app, the app will start, and an image of the app (in the example of FIG. 2, icons such as "Claim" and "Installment Payment") or text is displayed. For example, the display of an image or text containing information that can identify the app (e.g., a link or ID of the app) corresponds to the app being displayed so that it can be selected. The number of apps displayed in the app list L11 can be any number. For example, in the app list L11, about 7 to 8 apps are displayed so that they can be selected. When the user performs an operation to display more apps, the user terminal 30 may display more apps in the display unit 35 so that they can be selected.

[0071] For example, when the payment app is launched on the user terminal 30 and the user logs in to the payment service, the payment server 10 generates display data for the top screen SC1 including the app list L11. Assume that the data indicating the apps to be included in the app list L11 is pre-stored in the data storage unit 100 of the payment server 10. Based on the data, the payment server 10 arranges the apps in the app list L11, generates the display data for the top screen SC1, and transmits it to the user terminal 30. The user terminal 30 receives the display data from the payment server 10 and displays the top screen SC1 including the app list L11 on the display unit 35.

[0072] Note that the data indicating the apps to be included in the app list L11 may be pre-stored in the data storage unit 300 of the user terminal 30. In this case, the user terminal 30 may display the top screen SC1 including the app list L11 in which the apps can be selected on the display unit 35 without receiving the display data for the part of the app list L11 from the payment server 10.

[0073] FIG. 7 is a diagram showing an example of a screen displayed on the user terminal 30 of Modification 1. For example, in the state of the top screen SC1 in the upper left of FIG. 7, when the user performs an operation for displaying details in the app list L11 (for example, an operation of selecting "View All" in the app list L11), as shown in the upper right of FIG. 7, the user terminal 30 causes the display unit 35 to display a modal M12 including an app list L120 in which more apps can be selected. When the user selects an app from the app list L120, the user terminal 30 launches the app.

[0074] The proposal unit 104 of Modification 1 proposes app information I20 for displaying an app list L120 related to the list of apps to the user on the user terminal 30. In Modification 1, as in the embodiment, the case where the app information I20 is proposed on the payment completion screen SC2 is taken as an example. When the user completes the payment in the same procedure as in the embodiment, the proposal unit 104 causes the payment completion screen SC2 to display the app information I20 for displaying the app list L120 as shown in the lower left of FIG. 7.

[0075] For example, when the user selects the app information I20, as shown in the lower right of FIG. 7, the user terminal 30 causes the display unit 35 to display a modal M12 including the app list L120. The user terminal 30 may communicate with the payment server 10 to obtain data necessary for displaying the modal M12. Note that the app information I20 may be information for displaying the app list L11 on the top screen SC1 instead of the app list L120.

[0076] The payment system 1 of Modification 1 proposes app information I20 for displaying an app list L120 to the user on the user terminal 30. The payment system 1 can make more users aware of the existence of apps of related services related to the payment app.

[0077] [6-2. Modification 2] For example, the proposal of the application information I20 for displaying the application list L120 as in Modification 1 is effective for novice users who are unaware of the existence of the application list L120 in the first place, or users who have not used the application list L120 much. On the other hand, users who have used the payment application for a long time or users who often use the application list L120 know the existence of the application list L120. Therefore, for such users, it may be better to propose the application information I20 of a specific application as in the embodiment rather than the application information I20 as in Modification 1. Thus, in Modification 2, the application information I20 for displaying the application list L120 as in Modification 1 is proposed to users who do not use the application list.

[0078] For example, the payment system 1 of Modification 2 includes a usage status information acquisition unit 105. The usage status information acquisition unit 105 acquires usage status information regarding the usage status of at least one of the payment application and the application lists L11, L120 by the user. The usage status information may indicate the usage status of both the payment application and the application lists L11, L120, or may indicate the usage status of either the payment application or the application lists L11, L120.

[0079] The usage status of the payment application is the period from the start of using the payment application or the user's operation in the payment application. The usage status of the payment application may indicate whether the user is a novice. A novice is a user whose period from the start of using the payment application (for example, the period from registering for using the payment service) is less than a predetermined length. The usage status of the application lists L11, L120 is the operation on the applications displayed in the application lists L11, L120. For example, the number of times or the frequency of using the applications displayed in the application lists L11, L120 corresponds to the usage status of the application lists L11, L120.

[0080] Note that the usage information is assumed to be stored in the user database DB. For example, when the user uses the payment app, the payment server 10 updates the usage information according to the user's usage result at that time. For example, when the user uses the app lists L11 and L120, the payment server 10 may update the usage information so that the number of times or the usage frequency of the user using the app lists L11 and L120 increases. When the period from the start of using the payment app reaches a predetermined length or more, the payment server 10 may update the usage information so as to indicate that the user is no longer a beginner.

[0081] The proposal unit 104 of the modification example 2 proposes the app information I20 of the app list L120 to the user on the user terminal 30 based on the usage information. For example, the proposal unit 104 determines whether the usage status indicated by the usage information is a predetermined usage status, and based on the result of the determination, proposes the app information I20 of the app list L120 to the user on the user terminal 30. For example, when it is determined that the usage status indicated by the usage information is a predetermined usage status, the proposal unit 104 proposes the app information I20 of the app list L120 to the user on the user terminal 30. An example of the predetermined usage status is as follows.

[0082] For example, assume that the usage information indicates the usage status of the payment app itself. The proposal unit 104 may determine whether the user is a beginner based on the usage status of the payment app itself indicated by the usage information. When it is determined that the user is not a beginner, the proposal unit 104 does not propose the app information I20 of the app list L120, and when it is determined that the user is a beginner, the proposal unit 104 proposes the app information I20 of the app list L120.

[0083] For example, the proposal unit 104 may calculate the startup frequency of the payment app based on the usage status of the payment app indicated by the usage information, and propose the app information I20 in the app list L120 based on the startup frequency of the payment app. If the startup frequency of the payment app is equal to or higher than a predetermined frequency, the proposal unit 104 does not propose the app information I20 in the app list L120. If the startup frequency of the payment app is less than the predetermined frequency, the proposal unit 104 proposes the app information I20 in the app list L120.

[0084] For example, the proposal unit 104 may determine whether the user is making a payment or whether the number of payments during a predetermined period is equal to or more than a predetermined number based on the usage status of the payment app indicated by the usage information, and propose the app information I20 in the app list L120 based on the result of the determination. If it is determined that the user is making a payment, or if it is determined that the number of payments during a predetermined period is equal to or more than a predetermined number, the proposal unit 104 does not propose the app information I20 in the app list L120. If it is determined that the user is not making a payment, or if it is determined that the number of payments during a predetermined period is less than a predetermined number, the proposal unit 104 proposes the app information I20 in the app list L120.

[0085] For example, assume that the usage information indicates the usage status of the app lists L11 and L120. The proposal unit 104 determines whether an operation for displaying the app list L120 (for example, selection of "View All" in the app list L11) has been performed based on the usage information, or whether the number of times of such an operation during a predetermined period is equal to or more than a predetermined number, and may propose the app information I20 in the app list L120 based on the result of the determination. If an operation for displaying the app list L120 has been performed, or if the number of times of such an operation during a predetermined period is equal to or more than a predetermined number, the proposal unit 104 does not propose the app information I20 in the app list L120. If no operation for displaying the app list L120 has been performed, or if the number of times of such an operation during a predetermined period is less than a predetermined number, the proposal unit 104 proposes the app information I20 in the app list L120.

[0086] For example, based on the usage information, the proposal unit 104 determines whether there is an operation on the apps displayed in the app lists L11 and L120, or whether the number of times of such operation during a predetermined period is equal to or more than a predetermined number of times. Based on the result of the determination, the proposal unit 104 may propose the app information I20 of the app list L120. If there is an operation on the apps in the app lists L11 and L120, or if the number of times of such operation during a predetermined period is equal to or more than a predetermined number of times, the proposal unit 104 does not propose the app information I20 of the app list L120. If there is no operation on the apps in the app lists L11 and L120, or if the number of times of such operation during a predetermined period is less than a predetermined number of times, the proposal unit 104 proposes the app information I20 of the app list L120. That is, the proposal unit 104 may propose the app information I20 of the app list L120 to a user who has never launched an app, a user whose launched apps are less than a predetermined number, or a user whose number of times of launching an app is less than a predetermined number.

[0087] The settlement system 1 of Modification Example 2 proposes app information I20 to the user on the user terminal 30 based on the usage information. Thereby, the settlement system 1 can make the user aware of the existence of the app lists L11 and L120 according to the usage status of at least one of the settlement app and the app lists L11 and L120 by the user. As a result, the settlement system 1 can promote the use of the app. For example, the settlement system 1 can encourage the use of the apps in the app lists L11 and L120 for a user who has never used the settlement app or a user who has not used the settlement app much. The settlement system 1 can encourage the use of the apps displayed in the app lists L11 and L120 for a user who has never used the apps displayed in the app lists L11 and L120 or a user who has not used the apps displayed in the app lists L11 and L120 much.

[0088] [6-3. Modification Example 3] For example, new apps may be added to or existing apps may be deleted from the app lists L11 and L120. Furthermore, the layout of the app lists L11 and L120 may be changed, or the order of the apps in the app lists L11 and L120 may be changed. Or, there may be update information such as a campaign for a predetermined app, or there may be a version upgrade of a predetermined app. In such a case, when a change occurs in the app lists L11 and L120, the app information I20 for displaying the app lists L11 and L120 may be used to make the user aware of the changes in the app lists L11 and L120.

[0089] The settlement system 1 of Modification Example 3 includes a change determination unit 106. The change determination unit 106 determines whether or not a change has occurred in the app lists L11 and L120. It is assumed that the change presence / absence data indicating whether or not a change has occurred in the app lists L11 and L120 is stored in advance in the data storage unit 100. For example, when an update occurs in the settlement app and a change occurs in the app lists L11 and L120, the settlement server 10 updates the change presence / absence data so as to indicate that a change has occurred in the app lists L11 and L120 based on the operation of the administrator of the settlement service.

[0090] Note that the change determination unit 106 may automatically determine whether or not a change has occurred in the app lists L11 and L120 based on the content of the update of the settlement app instead of the operation of the administrator. In this case, the data storage unit 100 stores the history of the settlement app. When the settlement app is updated, the change determination unit 106 may compare the settlement app before the update stored as the history of the settlement app with the settlement app after the update to determine whether or not a change has occurred in the part of the app lists L11 and L120.

[0091] When the proposal unit 104 of Modification Example 3 is determined by the change determination unit 106 that changes have occurred in the application lists L11 and L120, the proposal unit 104 proposes, to the user on the user terminal 30, application information I20 for displaying the application lists L11 and L120. When the change determination unit 106 determines that no changes have occurred in the application lists L11 and L120, the proposal unit 104 does not propose, to the user on the user terminal 30, the application information I20 for displaying the application lists L11 and L120. In this case, the proposal unit 104 may propose, to the user on the user terminal 30, the application information I20 of a specific application as in the embodiment, or may propose other information I21 such as an advertisement.

[0092] Note that when the proposal unit 104 proposes, to a certain user, the application information I20 for displaying the application lists L11 and L120, the proposal unit 104 may record, in the data storage unit 100, data indicating that the application information I20 has been proposed, in association with the user. For the user for whom the data is recorded, the proposal unit 104 may not propose the application information I20 again. That is, after changes have occurred in the application lists L11 and L120, the proposal unit 104 may not propose the application information I20 again for the user to whom the application information I20 for displaying the application lists L11 and L120 has been proposed.

[0093] Further, Modifications 2 and 3 may be combined. In this case, when the Usage Information Acquisition Unit 105 is determined by the Change Determination Unit 106 that a change has occurred in the application lists L11 and L120, the usage information may be acquired. The usage information in this case may indicate the usage status after the change has occurred in the application lists L11 and L120. For example, when a change occurs in the application lists L11 and L120, the settlement server 10 resets the usage information of each user. The settlement server 10 updates the usage information of the user based on the use of at least one of the user's settlement applications and the application lists L11 and L120 thereafter. The Proposal Unit 104 proposes the application information I20 of the application list L120 to the user on the user terminal 30 based on the usage information indicating the usage status after the change has occurred in the application lists L11 and L120. The method of proposing the application information I20 based on the usage information is as described in Modification 2.

[0094] The settlement system 1 of Modification 3 determines whether a change has occurred in the application lists L11 and L120. When it is determined that a change has occurred in the application lists L11 and L120, the settlement system 1 proposes the application information I20 to the user on the user terminal 30. Thereby, the settlement system 1 can make the user aware of the change in the application lists L11 and L120. For example, when a new application is added to the application lists L11 and L120, the settlement system 1 can make the user aware of the existence of the new application and promote the use of the new application. For example, the settlement system 1 can appeal to the user more effectively by proposing the application information I20 based on the usage information after the change has occurred in the application lists L11 and L120.

[0095] [6-4. Modification 4] For example, in the embodiment, the case where the settlement information indicates the settlement amount is taken as an example. However, the settlement information may indicate other information related to the settlement. The settlement information acquisition unit 102 of Modification Example 4 acquires settlement information indicating the settlement location in the settlement. The settlement location is the location where the settlement is made. The settlement location is one of the affiliates (e.g., stores) that join the settlement service and receive the payment in the settlement. In Modification Example 4, since the settlement is made at the store, the settlement information indicates the store where the settlement is made. For example, the settlement information indicates a store ID that can identify the store. The settlement location may be specified by other information such as latitude and longitude instead of an ID such as a store ID.

[0096] In Modification Example 4, it is assumed that the settlement request received by the settlement server 10 from the store terminal 40 includes information on the settlement location. This information may be the store ID itself or a store terminal ID that allows the settlement server 10 to identify the store ID. The relationship between the store terminal ID and the store ID may be stored in advance in the data storage unit 100. The settlement information acquisition unit 102 acquires the information on the settlement location included in the settlement request as the settlement information indicating the settlement location. Since the settlement history information also indicates the settlement location, the settlement information acquisition unit 102 may acquire the settlement history information as the settlement information indicating the settlement location.

[0097] The app information acquisition unit 103 of Modification Example 4 acquires the app information I20 based on the settlement location indicated by the settlement information. It is assumed that the settlement location relationship data indicating the relationship between the settlement location and the app information I20 to be proposed to the user is stored in advance in the data storage unit 100. The settlement location relationship data may be in any form such as a table format, a mathematical formula format, a part of program code, or a machine learning model. The app information acquisition unit 103 acquires the app information I20 associated with the settlement location indicated by the settlement information. The actual data of each app information I20 is also assumed to be stored in the data storage unit 100.

[0098] For example, assuming that app information I20 of an app of a neighboring store of the settlement location is associated with the settlement location relationship data, the app information acquisition unit 103 acquires the app information I20 of the app of the neighboring store of the settlement location based on the settlement location relationship data. Assuming that app information I20 indicating an app of a store in the same category or having relevance to the settlement location is associated with the settlement location relationship data, the app information acquisition unit 103 acquires the app information I20 indicating an app of a store in the same category or having relevance to the settlement location based on the settlement location relationship data. Assuming that app information I20 of an app of a store in the same group as the settlement location or a store having a partnership relationship with the settlement location is associated with the settlement location relationship data, the app information acquisition unit 103 acquires the app information I20 of an app of a store in the same group as the settlement location or a store having a partnership relationship with the settlement location based on the settlement location relationship data.

[0099] For example, assuming that app information I20 of an app that manages receipts issued at the settlement location is associated with the settlement location relationship data, the app information acquisition unit 103 acquires the app information I20 of the app that manages receipts. Assuming that app information I20 of an app that manages a campaign held at the settlement location is associated with the settlement location relationship data, the app information acquisition unit 103 acquires the app information I20 of the app that manages the campaign based on the settlement location relationship data. The app information acquisition unit 103 may acquire app information I20 of other apps associated with the settlement location. The proposal unit 104 may propose the app information I20 acquired by the app information acquisition unit 103 to the user. Although the app information I20 acquired by the app information acquisition unit 103 is different from the embodiment, the process of the proposal unit 104 proposing the app information I20 may be the same as that of the embodiment.

[0100] The payment system 1 of Modification Example 4 acquires payment information indicating the payment location in a payment. The payment system 1 acquires the application information I20 based on the payment location indicated by the payment information. The payment system 1 can propose the application information I20 corresponding to the payment location to the user. For example, the payment system 1 can propose a neighboring store to the user by proposing the application information I20 of the application of the neighboring store of the payment location to the user, so that the effect of attracting customers to the neighboring store is enhanced. The payment system 1 can also promote the use of the application of the neighboring store.

[0101] [6-5. Modification Example 5] For example, the payment information acquisition unit 102 of Modification Example 5 acquires payment information indicating the payment means used in a payment. In the example of the payment application in FIG. 2, the payment information indicates the payment means set as the payer. It is assumed that the payer information indicating the payer is stored in the user database DB. When the user performs an operation to change the payer from the payment application, the payment server 10 updates the user's payer information so as to indicate the payer specified by the user. For example, when the user designates a certain credit card as the payer, the payment server 10 updates the user's payer information so as to indicate the credit card. When the user designates electronic money as the payer, the payment server 10 updates the user's payer information so as to indicate the electronic money.

[0102] For example, the information on the payment means used in a payment may be included in the payment request received by the payment server 10 from the store terminal 40, but in Modification Example 5, it is assumed to be included in the payer information stored in the user database DB. Therefore, when a payment is executed, the payment information acquisition unit 102 acquires the current payer information, thereby acquiring the payment information indicating the payment means used in the payment. When the information indicating the payment means used in the payment is shown in the payment history information, the payment information acquisition unit 102 may acquire the payment history information as the payment information indicating the payment means.

[0103] The application information acquisition unit 103 of Modification Example 5 acquires application information I20 based on the payment means indicated by the payment information. It is assumed that the payment means relationship data indicating the relationship between the payment means and the application information I20 to be proposed to the user is stored in the data storage unit 100 in advance. The payment means relationship data may be in any format such as a table format, a mathematical formula format, a part of program code, or a machine learning model. The application information acquisition unit 103 acquires the application information I20 associated with the payment means indicated by the payment information. The actual data of each application information I20 is also assumed to be stored in the data storage unit 100.

[0104] For example, if the payment means relationship data associates a credit card with the application information I20 of an installment payment application, the application information acquisition unit 103 acquires the application information I20 of the installment payment application when the payment information indicates a credit card. If the payment means relationship data associates electronic money with the application information I20 of a balance confirmation application for checking the balance of the electronic money, the application information acquisition unit 103 acquires the application information I20 of the balance confirmation application when the payment information indicates electronic money.

[0105] For example, if the payment means relationship data associates a bank account with the application information I20 of an account management application for managing the bank account, the application information acquisition unit 103 acquires the application information I20 of the account management application when the payment information indicates a bank account. Since coupons or points may also be used as payment means, if the payment means relationship data associates a coupon or point with the application information I20 of an application for managing the coupon or point, the application information acquisition unit 103 acquires the application information I20 of the said application when the payment information indicates a coupon or point. The proposal unit 104 may propose the application information I20 acquired by the application information acquisition unit 103 to the user. Although the application information I20 acquired by the application information acquisition unit 103 is different from that of the embodiment, the process of the proposal unit 104 proposing the application information I20 may be the same as that of the embodiment.

[0106] The payment system 1 of Modification Example 5 acquires payment information indicating the payment means used in the payment. Based on the payment means indicated by the payment information, the payment system 1 acquires the application information I20. The payment system 1 can propose the application information I20 corresponding to the payment means to the user. For example, when the user executes a payment using a credit card, the payment system 1 proposes the application information I20 of the installment payment application, eliminating the need for the user to search for the installment payment application among the applications installed on the user terminal 30 by themselves, thus enhancing the convenience for the user. The payment system 1 can propose a useful installment payment application to the user who uses a credit card.

[0107] [6-6. Modification Example 6] For example, the payment information acquisition unit 102 of Modification Example 6 acquires payment information indicating the payment frequency of the user who executed the payment. In Modification Example 6, it is assumed that the payment information indicating the payment frequency is stored in the user database DB. The payment information of Modification Example 6 indicates the payment frequency over a certain period (for example, the past one month or one year). For example, when a user executes a payment, the payment server 10 updates the payment information of the user so that the payment frequency of the user increases. The payment information acquisition unit 102 acquires the payment information stored in the user database DB. The payment frequency information may not be stored in the user database DB in advance. In this case, the payment information acquisition unit 102 may acquire the payment information indicating the payment frequency by dynamically calculating the payment frequency of a certain user based on the payment history information of the user.

[0108] The application information acquisition unit 103 of Modification Example 6 acquires application information I20 based on the payment frequency indicated by the payment information. Assume that the payment frequency relationship data indicating the relationship between the payment frequency and the application information I20 to be proposed to the user is stored in the data storage unit 100 in advance. The payment frequency relationship data may be in any format such as a table format, a mathematical formula format, a part of a program code, or a machine learning model. The application information acquisition unit 103 acquires the application information I20 associated with the payment frequency indicated by the payment information. Assume that the actual data of each piece of application information I20 is also stored in the data storage unit 100.

[0109] For example, assume that in the payment frequency relationship data, the fact that the payment frequency is equal to or higher than the threshold value is associated with the application information I20 of the point operation application. Then, when the payment frequency indicated by the payment information is equal to or higher than the threshold value, the application information acquisition unit 103 acquires the application information I20 of the point operation application. Assume that in the payment frequency relationship data, the fact that the payment frequency is less than the threshold value is associated with the application information I20 of the campaign application. Then, when the payment frequency indicated by the payment information is less than the threshold value, the application information acquisition unit 103 acquires the application information I20 of the campaign application. The proposal unit 104 may propose the application information I20 acquired by the application information acquisition unit 103 to the user. Although the application information I20 acquired by the application information acquisition unit 103 is different from that in the embodiment, the process of the proposal unit 104 proposing the application information I20 may be the same as that in the embodiment.

[0110] The payment system 1 of Modification Example 6 acquires payment information indicating the payment frequency of the user who executed the payment. The payment system 1 acquires the application information I20 based on the payment frequency indicated by the payment information. The payment system 1 can propose the application information I20 corresponding to the payment frequency to the user. For example, since the applications that relatively high-payment-frequency users and relatively low-payment-frequency users are interested in may be different from each other, the payment system 1 can propose the application information I20 of the application that the user is more likely to be interested in to the user.

[0111] [6-7. Modification Example 7] For example, the payment information acquisition unit 102 of Modification Example 7 acquires payment information indicating the product or service that is the subject of the payment. In Modification Example 7, it is assumed that the payment request received by the payment server 10 from the store terminal 40 includes information on the product or service that is the subject of the payment. This information may be a general code such as a JAN code, or a code uniquely defined by the store. This information may also be a character string indicating the product name or service name. The payment information acquisition unit 102 acquires the information included in the payment request as payment information indicating the product or service that is the subject of the payment. When the product or service that is the subject of the payment is shown in the payment history information, the payment information acquisition unit 102 may acquire the payment history information as payment information indicating the product or service that is the subject of the payment.

[0112] The application information acquisition unit 103 of Modification Example 7 acquires application information I20 based on the product or service indicated by the payment information. It is assumed that payment target relationship data indicating the relationship between the product or service that is the subject of the payment and the application information I20 to be proposed to the user is stored in advance in the data storage unit 100. The payment target relationship data may be in any format such as a table format, a mathematical formula format, a part of program code, or a machine learning model. The application information acquisition unit 103 acquires the application information I20 associated with the payment target indicated by the payment information. The actual data of each piece of application information I20 is also assumed to be stored in the data storage unit 100.

[0113] For example, if vehicle, which is an example of a product to be settled, and app information I20 of an insurance app provided by an insurance company are associated with the settlement target relationship data, when the settlement information indicates a vehicle, the app information acquisition unit 103 acquires the app information I20 of the insurance app. If a beauty treatment, which is an example of a service to be settled, and app information I20 of a beauty salon reservation app that accepts reservations at the beauty salon are associated with the settlement target relationship data, when the settlement information indicates a beauty treatment at the beauty salon, the app information acquisition unit 103 acquires the app information I20 of the beauty salon reservation app. The proposal unit 104 may propose the app information I20 acquired by the app information acquisition unit 103 to the user. Although the app information I20 acquired by the app information acquisition unit 103 is different from the embodiment, the process of the proposal unit 104 proposing the app information I20 may be the same as that in the embodiment.

[0114] The settlement system 1 of Modification 7 acquires settlement information indicating a product or service that is the settlement target. Based on the product or service indicated by the settlement information, the settlement system 1 acquires app information I20. The settlement system 1 can propose app information I20 corresponding to the product or service that is the settlement target to the user. For example, the settlement system 1 can propose app information I20 of an app that the user is more likely to be interested in by proposing app information I20 corresponding to the product or service purchased by the user through settlement.

[0115] [6-8. Modification 8] For example, the settlement information acquisition unit 102 of Modification 8 acquires settlement information indicating the settlement time at which the settlement was executed. The settlement time may be expressed in date and time, or may be expressed by only one of day of the week, date, or time. In Modification 8, when the settlement execution unit 101 of the settlement server 10 executes a settlement, the settlement information acquisition unit 102 uses a real-time clock or the like to acquire settlement information indicating the current date and time as the settlement time. Since the settlement history information also indicates the settlement time, the settlement information acquisition unit 102 may acquire the settlement history information as settlement information indicating the settlement time.

[0116] The app information acquisition unit 103 of Modification Example 8 acquires app information I20 based on the settlement time indicated by the settlement information. Assume that the settlement time relationship data indicating the relationship between the settlement time and the app information I20 to be proposed to the user is stored in the data storage unit 100 in advance. The settlement time relationship data may be in any form such as a table format, a mathematical formula format, a part of program code, or a machine learning model. The app information acquisition unit 103 acquires the app information I20 associated with the settlement time indicated by the settlement information. Assume that the actual data of each app information I20 is also stored in the data storage unit 100.

[0117] For example, the settlement server 10 may also specify in advance the daytime action range and the nighttime action range from the user's actions such as past settlement histories. In this case, the settlement time relationship data associates the daytime settlement time with the app information I20 of the apps provided by the stores within the daytime action range. Furthermore, the settlement time relationship data associates the nighttime settlement time with the app information I20 of the apps provided by the stores within the nighttime action range. When the settlement information indicates the daytime time zone, the app information acquisition unit 103 acquires the app information I20 of the apps provided by the stores in the daytime action range. When the settlement information indicates the nighttime time zone, the app information acquisition unit 103 acquires the app information I20 of the apps provided by the stores in the nighttime action range.

[0118] Note that the settlement time-related data may indicate a time other than daytime or nighttime. For example, the settlement time-related data may indicate the relationship between a time such as a weekday or weekend and the app information I20 to be proposed to the user. In this case, the app information acquisition unit 103 may acquire the corresponding app information I20 according to whether the settlement information indicates a weekday or a weekend. The proposal unit 104 may propose the app information I20 acquired by the app information acquisition unit 103 to the user. Although the app information I20 acquired by the app information acquisition unit 103 is different from that in the embodiment, the process of the proposal unit 104 proposing the app information I20 may be the same as that in the embodiment. For another example, the app information acquisition unit 103 may acquire the corresponding app information I20 according to whether the settlement information indicates a specific day of the week (for example, a day of the week during the slack period). Suppose a store whose slack period is Wednesday is having a campaign on Wednesday. Then, when the day of the week indicated by the settlement information is Wednesday, the app information acquisition unit 103 may identify, based on the settlement time-related data, the app information I20 of the app provided by the store having the campaign on Wednesday, and acquire the identified app information I20.

[0119] The settlement system 1 of Modification 8 acquires settlement information indicating the settlement time at which settlement was executed. The settlement system 1 acquires app information I20 based on the settlement time indicated by the settlement information. The settlement system 1 can propose app information I20 corresponding to the settlement time to the user. For example, since the apps that the user is interested in may differ depending on the settlement time, the settlement system 1 can propose the app information I20 of the app that the user is more interested in.

[0120] [6-9. Modification 9] For example, the user may also use other services other than the settlement service, such as an e-commerce service, a travel reservation service, a communication service, or a financial service. Various information of the user may be recorded in other services. Therefore, the settlement system 1 may propose app information I20 to the user based not only on the settlement information but also on the user's information in other services.

[0121] The payment system 1 of Modification Example 9 includes an other service information acquisition unit 107. The other service information acquisition unit 107 acquires other service information regarding a user in another service different from the payment service. The other service information may be information about a user registered in another service (for example, demographic information such as the user's gender or age group), or may be information regarding the use of the user in another service.

[0122] In Modification Example 9, a case where another service is an e-commerce service is taken as an example. Further, a case where the other service information indicates the payment method of a product purchased by the user in the e-commerce service (for example, whether it is payment by invoice or payment by credit card) is taken as an example. The payment information of Modification Example 9 is assumed to be information indicating whether the payment has been completed or not. The other service information acquisition unit 107 acquires the other service information of the user from a computer of the e-commerce service (for example, the related server 20 or another computer).

[0123] In Modification Example 9, it is assumed that the user ID is common in the payment service and another service. The other service information acquisition unit 107 transmits the user ID of the user for which the other service information is to be acquired to the computer of the other service. When the computer of the other service receives the user ID, it specifies which user's other service information should be transmitted. The computer of the e-commerce service transmits the other service information of the specified user to the payment server 10. The other service information acquisition unit 107 acquires the other service information from the computer of the other service.

[0124] Note that the user IDs may be different in the payment service and another service. In this case, it is assumed that the relationship between the user ID of the payment service and the user ID of the other service is managed by at least one of the payment server 10 and the computer of the other service. The computer of the other service may specify which user's other service information should be transmitted based on the relationship.

[0125] The application information acquisition unit 103 of Modification Example 9 acquires application information I20 based on further other service information. For example, when settlement information indicating the completion of settlement is acquired, the application information acquisition unit 103 acquires application information I20 based on the other service information. Assume that other service relationship data indicating the relationship between the other service information and the application information I20 to be proposed to the user is stored in the data storage unit 100 in advance. The other service relationship data may be in any format such as a table format, a mathematical formula format, a part of program code, or a machine learning model. The application information acquisition unit 103 acquires the application information I20 associated with the other service information. Assume that the actual data of each piece of application information I20 is also stored in the data storage unit 100.

[0126] In Modification Example 9, taking the case where the other service information indicates the payment method of the product purchased by the user through an e-commerce service as an example, the application information acquisition unit 103 acquires the application information I20 based on the payment method indicated by the other service information. For example, assume that in the other service relationship data, the fact that the payment method is invoice payment is associated with the application information I20 of an invoice payment application that enables invoice payment on the user terminal 30. Then, when the payment method indicated by the other service information is invoice payment, the application information acquisition unit 103 acquires the application information I20 of the invoice payment application.

[0127] For example, assume that in the other service relationship data, the fact that the payment method is credit card payment is associated with the application information I20 of a post-payment application. Then, when the payment method indicated by the other service information is credit card payment, the application information acquisition unit 103 acquires the application information I20 of the post-payment application. The proposal unit 104 may propose the application information I20 acquired by the application information acquisition unit 103 to the user. Although the application information I20 acquired by the application information acquisition unit 103 is different from that in the embodiment, the process of the proposal unit 104 proposing the application information I20 may be the same as that in the embodiment.

[0128] Note that the other service information may indicate any content in other services. The other service information may indicate other content other than the user's payment method. For example, the other service information may indicate the price of goods or services purchased by the user in other services. In this case, assuming that the price being above a threshold value and the app information I20 of the installment payment app are associated with the other service related data, the app information acquisition unit 103 acquires the app information I20 of the installment payment app when the price indicated by the other service information is above the threshold value.

[0129] For example, when the other service is a travel reservation service, the other service information may be the travel product reserved by the user. In this case, assuming that the travel product reserved by the user being an overseas travel product and the app information I20 of an insurance app provided by an insurance company handling overseas travel insurance are associated with the other service related data, the app information acquisition unit 103 acquires the app information I20 of this app when the travel product indicated by the other service information is an overseas travel product. Similarly, when the other service is a service other than an e-commerce service or a travel reservation service, the app information acquisition unit 103 may acquire the app information I20 corresponding to the other service information of the other service.

[0130] Also, the relationship between the payment information and the other service information and the app information I20 to be proposed to the user may be shown in the other service related data. In this case, the app information acquisition unit 103 may refer to the other service related data and acquire the app information I20 associated with the payment information and the other service information.

[0131] The settlement system 1 of Modification Example 9 acquires other service information regarding a user in another service different from the settlement service. The settlement system 1 acquires the app information I20 based on the other service information. Thereby, the settlement system 1 can propose the optimal app information I20 to the user considering the information in other services. For example, the settlement system 1 proposes the app information I20 of the bill app to a user who purchases a product by paying a bill in an e-commerce service, so that the user can pay the bill with the bill app after the product arrives.

[0132] [6-10. Modification Example 10] For example, the app information I20 that a user is interested in may vary depending on the user's attributes. Therefore, the settlement system 1 may present the app information I20 according to the user's attributes. The settlement system 1 of Modification Example 10 includes a user attribute information acquisition unit 108. The user attribute information acquisition unit 108 acquires user attribute information regarding the user's attributes. The user's attributes can be referred to as the classification of the user. For example, the user attribute information may indicate the user's age, residential area, gender, age group, family composition, characteristics of actions in the settlement service, or other attributes. In Modification Example 10, it is assumed that the user attribute information is stored in the user database DB. The user attribute information acquisition unit 108 refers to the user database DB and acquires the user attribute information.

[0133] The app information acquisition unit 103 of Modification Example 10 acquires app information I20 based on the user attribute information as well. In Modification Example 10, similar to Modification Example 9, the case where the settlement information is information indicating whether the settlement has been completed is taken as an example. For example, when the app information acquisition unit 103 acquires settlement information indicating the completion of settlement, it acquires app information I20 based on the user attribute information. Assume that the user attribute relationship data indicating the relationship between the user attribute information and the app information I20 to be proposed to the user is stored in the data storage unit 100 in advance. The user attribute relationship data may be in any form such as a table format, a mathematical formula format, a part of program code, or a machine learning model. The app information acquisition unit 103 acquires the app information I20 associated with the user attribute information. Assume that the actual data of each app information I20 is also stored in the data storage unit 100.

[0134] For example, assume that in the user attribute relationship data, the user attribute being a family composition with children is associated with an app of a financial institution that provides a loan for educational expenses. Then, when the user attribute information indicates the family composition, the app information acquisition unit 103 acquires the app information I20 of the app of the financial institution. Assume that in the user attribute relationship data, the user attribute being a single-person family composition is associated with a property app that provides information on properties for living alone. Then, when the user attribute information indicates the family composition, the app information acquisition unit 103 acquires the app information I20 of the property app. Similarly for other user attributes, the app information acquisition unit 103 may acquire the app information I20 of the app associated with the user attribute indicated by the user attribute information.

[0135] Also, in the user attribute relationship data, the relationship between payment information, user attribute information, and app information I20 to be proposed to the user may be shown. In this case, the app information acquisition unit 103 may refer to the user attribute relationship data and acquire the app information I20 associated with the payment information and user attribute information. The proposal unit 104 may propose the app information I20 acquired by the app information acquisition unit 103 to the user. Although the app information I20 acquired by the app information acquisition unit 103 is different from the embodiment, the process of the proposal unit 104 proposing the app information I20 may be the same as that in the embodiment.

[0136] The payment system 1 of Modification Example 10 acquires the app information I20 based on the user attribute information. Thereby, the payment system 1 can propose to the user the optimal app information I20 that also takes into account the user's attributes. For example, the payment system 1 can propose to the user the app information I20 of an app that a user with specific attributes is likely to be interested in.

[0137] [6-11. Modification Example 11] For example, when a user is already using an app, the apps that are better to recommend to the user may vary depending on the usage situation of the app by the user. Therefore, the settlement system 1 may recommend app information I20 according to the operation on the app by the user. The settlement system 1 of Modification Example 11 includes an app operation information acquisition unit 109. The app operation information acquisition unit 109 acquires app operation information regarding the operation on the app by the user. The app operation information can also be said to be information indicating the usage situation of the app by the user. Assume that the app operation information is stored in the user database DB. When a certain user performs some operation on the app, the settlement server 10 updates the app operation information of the said user. For example, the app operation information may be startup information regarding the app launched from the home screen of the settlement app (the upper left screen in FIGS. 2 and 7) or the app lists L11 and L120 (for example, information indicating at least one of the presence or absence of app startup and the number of startups). The app operation information may be startup information after the app information I20 is recommended (for example, information indicating at least one of the presence or absence of app startup and the number of startups).

[0138] Modification Example 11 takes the case where the app operation information indicates the number of app startups as an example. The app operation information may indicate the number of startups of each of a plurality of apps. For example, when a certain user launches a certain app from the app list L11, the settlement server 10 acquires data indicating that the said user has launched the said app from the user terminal 30. Based on the said data, the settlement server 10 updates the app operation information so that the number of startups of the said app by the said user increases. The settlement server 10 may also acquire from the user terminal 30 data indicating the specific operation content performed by the user within the said app, and update the app operation information of the said user to indicate the said operation content. The app operation information acquisition unit 109 acquires the app operation information updated in this way from the user database DB.

[0139] The application information acquisition unit 103 of Modification Example 11 acquires application information I20 based on the application operation information. In Modification Example 11, similar to Modification Examples 9 and 10, a case where the settlement information is information indicating whether the settlement has been completed is taken as an example. For example, when the settlement information indicating the completion of the settlement is acquired, the application information acquisition unit 103 acquires the application information I20 based on the application operation information. It is assumed that the application operation relationship data indicating the relationship between the application operation information and the application information I20 to be proposed to the user is stored in the data storage unit 100 in advance. The application operation relationship data may be in any form such as a table format, a mathematical formula format, a part of program code, or a machine learning model. The application information acquisition unit 103 acquires the application information I20 associated with the application operation information. It is also assumed that the actual data of each application information I20 is stored in the data storage unit 100.

[0140] For example, when the application operation information indicates the number of times the application has been launched and the application operation relationship data shows the relationship between the number of times the application has been launched and the application information I20 to be proposed to the user, the application information acquisition unit 103 acquires the application information I20 of the application with a relatively low number of launches. The application information acquisition unit 103 may acquire the application information I20 of the application whose number of launches is less than the threshold. Conversely, the application information acquisition unit 103 may acquire the application information I20 of the application with a relatively high number of launches. The application information acquisition unit 103 may acquire the application information I20 of the application whose number of launches is equal to or greater than the threshold.

[0141] Note that when the application operation information indicates not the number of times the application has been launched but the specific operation content within the application, the application information acquisition unit 103 may acquire the application information I20 corresponding to the specific operation content indicated by the application operation information. In this case, the application operation relationship data shows the relationship between the specific operation content within the application and the application information I20 to be proposed to the user. The application information acquisition unit 103 may acquire the application information I20 associated with the specific operation content within the application.

[0142] In addition, the relationship between payment information, app operation information, and app information I20 to be proposed to the user may be shown in the app operation-related data. In this case, the app information acquisition unit 103 may refer to the app operation-related data and acquire the app information I20 associated with the payment information and the app operation information. The proposal unit 104 may propose the app information I20 acquired by the app information acquisition unit 103 to the user. Although the app information I20 acquired by the app information acquisition unit 103 is different from that in the embodiment, the process of the proposal unit 104 proposing the app information I20 may be the same as that in the embodiment.

[0143] The payment system 1 of Modification Example 11 acquires the app information I20 based on the app operation information as well. Thereby, the payment system 1 can propose to the user the optimal app information I20 that also takes into account the user's operations on each app. For example, the payment system 1 can inform the user of the existence of apps that the user does not usually use by proposing the app information I20 of apps that the user rarely selects to the user. The payment system 1 can save the trouble for the user to search for and launch the apps that the user usually uses by proposing the app information I20 of the apps that the user often selects to the user. For example, the payment system 1 can also prevent proposing to the user the apps that the user has already noticed multiple times.

[0144] [6-12. Modification Example 12] For example, as described in the embodiment, when the payment is executed, the proposal unit 104 can also propose other information I21 other than the app information I20 to the user. In the example of FIG. 2, the proposal unit 104 can also propose other information I21 showing an advertisement on the payment completion screen SC2. Although the payment completion screen SC2 is a screen that the user pays attention to, since there is a limit to the information that can be displayed therein, more user-suitable information may be selected based on the payment information.

[0145] The settlement system 1 of Modification Example 12 includes a selection unit 110. The selection unit 110 selects information to be proposed to the user from among a plurality of pieces of information including app information I20 and other information I21 based on the settlement information. The plurality of pieces of information are information that are candidates for proposal. Assume that the actual data of the other information I21 is also stored in the data storage unit 100. In Modification Example 12, the case where the information proposed on the settlement completion screen SC2 is selected by the selection unit 110 is taken as an example. However, as described in the embodiment, the information proposed on a screen other than the settlement completion screen SC2 may be selected by the selection unit 110.

[0146] For example, assume that proposal relationship data indicating the relationship between the settlement information and the information to be proposed to the user among the plurality of pieces of information is stored in the data storage unit 100 in advance. The proposal relationship data may be in any format such as a table format, a mathematical formula format, a part of program code, or a machine learning model. The app information acquisition unit 103 acquires the app information I20 associated with the proposed information. Assume that the actual data of each piece of app information I20 is also stored in the data storage unit 100.

[0147] In Modification Example 12, as in the embodiment, the case where the settlement information indicates the settlement amount is taken as an example. In the proposal relationship data, the relationship between whether the settlement amount is equal to or greater than the threshold value and the information to be proposed to the user (at least one of the app information I20 and the other information I21) among the plurality of pieces of information is shown. For example, when the settlement amount indicated by the settlement information is equal to or greater than the threshold value based on the proposal relationship data, the selection unit 110 selects the app information I20 of the installment payment app. When the settlement amount indicated by the settlement information is less than the threshold value based on the proposal relationship data, the selection unit 110 selects other information I21 such as an advertisement.

[0148] Note that even when the settlement information indicates other content than the settlement amount, in the proposal relationship data, the relationship between the other content and the information to be proposed to the user (at least one of the app information I20 and the other information I21) among the plurality of pieces of information is shown. The selection unit 110 may select the information associated with the other content indicated by the settlement information based on the proposal relationship data.

[0149] When the proposal unit 104 of Modification Example 12 selects the application information I20 by the selection unit 110, the proposal unit 104 proposes the application information I20. When the selection unit 110 selects other information I21, the proposal unit 104 proposes the other information I21. Since the selection unit 110 may select both the application information I20 and the other information I21, in this case, the proposal unit 104 may propose both the application information I20 and the other information I21 to the user.

[0150] The payment system 1 of Modification Example 12 selects information to be proposed to the user from a plurality of information including the application information I20 and other information I21 based on the payment information. When the application information I20 is selected by the selection unit 110, the payment system 1 proposes the application information I20. Thereby, the payment system 1 can propose the optimal information according to the payment information to the user. For example, the payment system 1 can propose the application information I20 to a user for whom the proposal of a certain specific application is effective. The payment system 1 can propose other information I21 to a user for whom the proposal of other information I21 other than the application information I20 is effective.

[0151] [6-13. Modification Example 13] For example, the application information acquisition unit 103 may determine the relevance between each of a plurality of application information I20 that are candidates for proposals to the user and the user based on the payment information, and acquire the application information I20 of the application with relatively high relevance. The relevance is the probability that the user is presumed to be interested in the application information I20. In Modification Example 13, it is assumed that relevance data indicating the relationship between the payment information and the application information I20 relevant to the user is stored in the data storage unit in advance. The relevance data may be in any form such as a table format, a mathematical formula format, a part of program code, or a machine learning model. The application information acquisition unit 103 acquires the application information I20 associated with the user attribute information.

[0152] For example, the determination of relevance in Modification 13 may be a determination of whether to display the app information I20 of the app list L120 described in Modification 2 or the like, or the app information I20 of a specific app described in the embodiment or the like. Alternatively, for example, the determination of relevance in Modification 13 may be a determination of which app information I20 to display when there are multiple pieces of app information I20 for a specific app. The determination of relevance in Modification 13 includes these two patterns.

[0153] For example, when a change occurs in the app lists L11 and L120 and the user's settlement amount is equal to or greater than the threshold value, both the app information I20 of the app list L120 (FIG. 7) and the app information I20 of the installment payment app (FIG. 2) may be displayed. In this case, app information I20 corresponding to the priority may be proposed based on a predetermined priority (for example, a priority that prioritizes the determination regarding a specific app). App information I20 for a specific user identified by the user's past operation history (for example, a user who viewed the app lists L11 and L120, a user who selected "View All" in the app list L11) may be proposed. Furthermore, relevance may be determined in combination with other information. For example, in combination with the information that the settlement location is a beauty salon and the user is female, app information I20 of a beauty app for women may be proposed together with the app information I20 of an installment payment app related to the settlement amount.

[0154] In Modification 13, an example is given where the settlement information indicates three items: the settlement amount, the settlement location, and the settlement means. These details are as described in the embodiment, Modification 4, and Modification 5, respectively. In the relevance data, an installment payment app is shown as an app relevant to the settlement amount being equal to or greater than the threshold value. In the relevance data, an app of a neighboring store is shown as an app relevant to the settlement location being a predetermined location. In the relevance data, a point management app is shown as an app relevant to the settlement means being points.

[0155] For example, the application information acquisition unit 103 identifies relevant applications from a plurality of applications based on three items indicated by the payment information and the relevance data. For example, when the payment amount indicated by the payment information is equal to or greater than a threshold value, the application information acquisition unit 103 identifies an installment payment application. When the payment location indicated by the payment information is a predetermined location, the application information acquisition unit 103 identifies the application of the neighboring store. When the payment method indicated by the payment information is points, the application information acquisition unit 103 identifies a point management application. Since there may be no relevant applications, in this case, the application information acquisition unit 103 may not identify any applications.

[0156] For example, when three applications, namely an installment payment application, an application of a neighboring store, and a point management application, are identified based on the three items indicated by the payment information, the application information acquisition unit 103 may select an application with relatively high relevance from these three based on a predetermined selection condition. The predetermined selection condition is a condition serving as a criterion for the application information acquisition unit 103 to select some of the applications when a plurality of applications are identified. Examples of the predetermined selection condition include conditions related to a predetermined priority, conditions related to past payment information, and conditions related to information other than the payment information (for example, information on operations on the application, user attribute information, or campaign information, etc.). For another example, the predetermined selection condition may be a condition related to the payment information at that time (for example, the day of the week when the payment was made).

[0157] For example, assume that a predetermined selection condition is a condition regarding a preset priority. Further, assume that as a predetermined selection condition, it is set that the settlement amount is prioritized. In this case, the application information acquisition unit 103 determines the relevance of the application, prioritizing the settlement amount. When it is determined based on the settlement amount that there is relevance, the application information acquisition unit 103 acquires the application information I20 of the installment payment application without determining the settlement location and the settlement means. When it is determined based on the settlement amount that there is no relevance, the application information acquisition unit 103 determines the relevance of the application based on the settlement location. When it is determined based on the settlement location that there is relevance, the application information acquisition unit 103 acquires the application information I20 of the application of the neighboring store without determining the settlement means. When it is determined based on the settlement location that there is no relevance, the application information acquisition unit 103 determines the relevance of the application based on the settlement means. In this way, the application information acquisition unit 103 may sequentially determine a plurality of items (in the above example, the three items of the settlement amount, the settlement location, and the settlement means) based on the priority defined as the selection condition.

[0158] For example, assume that a predetermined selection condition is a condition regarding past settlement information. In this case, the application information acquisition unit 103 acquires information indicating each of the past settlement amount, the settlement location, and the settlement means as past settlement information and determines the relevance. The frequency of each of the past settlement amount, the settlement location, and the settlement means may be indicated in the information. For example, when the application information acquisition unit 103 specifies that there are relatively many settlements at a specific settlement location during a specific period, the application related to the settlement location may be specified as a relevant application, and the application information I20 of the application may be proposed to the user.

[0159] For example, assume that a predetermined selection condition is other information than settlement information (for example, information on operations on an application, user attribute information, or campaign information, etc.). If other information indicates that the number of times the user has selected an installment payment application related to the settlement amount is large, the application information acquisition unit 103 may identify the installment payment application related to the settlement amount as an application with high relevance and acquire the application information I20 of the installment payment application. That is, the application information acquisition unit 103 may identify an application with a relatively large number of selections based on other information and acquire the application information I20 of the application. For example, when the settlement location of the user's current settlement is a beauty salon and the user attribute information indicates a female, the application information acquisition unit 103 may, based on the combination of these pieces of information, identify a beauty application targeted at females as an application with high relevance and acquire the application information I20 of the beauty application. For another example, for instance, when the settlement means used by the user this time is a credit card, if a credit card campaign is being conducted in a certain specific application, the application information acquisition unit 103 may identify the application as an application with high relevance and acquire the application information I20 of the application. Assume that the information required for these processes is shown in the relevance data.

[0160] Note that the relevance may be expressed by a score. The relevance may be expressed by a numerical value, a character, or other symbols, etc. For example, the application information acquisition unit 103 calculates a score indicating the degree of relevance for each individual application by substituting the content indicated by the settlement information into a predetermined calculation formula. The application information acquisition unit 103 may acquire the application information I20 of an application with a relatively high score.

[0161] The proposal unit 104 of Modification Example 13 proposes the application information I20 of an application with relatively high relevance to the user on the user terminal 30. Note that the proposal unit 104 of Modification Example 13 may propose all or some of the applications with relevance. In this case, they may be displayed in descending order of relevance. Although the application information I20 acquired by the application information acquisition unit 103 is different from that in the embodiment, the process of the proposal unit 104 proposing the application information I20 may be the same as that in the embodiment.

[0162] The settlement system 1 of Modification Example 13 determines the relevance between each of a plurality of apps that are candidates for proposals to the user and the user based on the settlement information, and acquires the app information I20 of the app with relatively high relevance. The settlement system 1 proposes the app information I20 of the app with relatively high relevance to the user on the user terminal 30. Thereby, since the settlement system 1 can propose the app information I20 of the app with high relevance to the user, it can propose the app information I20 that the user is more interested in.

[0163] [6-14. Other Modification Examples] For example, the above modification examples may be combined.

[0164] For example, in the embodiment, the case where the user uses the settlement service with the settlement app is taken as an example, but the user may use the settlement service with the browser of the user terminal 30. In this case, the user may execute the settlement by causing the store terminal 40 to read the code C10 displayed on the browser, or may execute the settlement online instead of in the store without using the code C10 in particular. The online settlement is completed only by an operation on the user terminal 30. For example, the user may execute the settlement of an online e-commerce service, an e-book service, a travel reservation service, a communication service, or other services from the browser. The settlement system 1 may propose the app information I20 on the settlement completion screen SC2 of such an online settlement. The app information I20 in this case may be information for proposing a settlement app to the user.

[0165] For example, the functions described as being realized by the settlement server 10 may be realized by the related server 20, the user terminal 30, the store terminal 40, or other computers. The processes described as being realized by the settlement server 10 may be shared by a plurality of computers.

[0166] [7. Supplementary Note] For example, the system may also have the following configuration. (1) A settlement information acquisition unit that acquires settlement information regarding the settlement when a user who uses a settlement service executes the settlement using a user terminal; An application information acquisition unit that acquires application information regarding an application of a related service related to the settlement based on the settlement information; A proposal unit that proposes the application information to the user on the user terminal; A settlement system including the above. (2) The proposal unit proposes the application information to the user on a settlement completion screen displayed on the user terminal when the settlement is completed. The settlement system according to (1). (1) The settlement system described in. (3) The user executes the settlement using a settlement application installed on the user terminal. The proposal unit proposes the application information to the user on the user terminal for displaying an application list regarding the list of the applications. The settlement system according to (1) or (2). (1) or (2) The settlement system described in. (1) or (2) The settlement system described in. (4) The settlement system further includes a usage status information acquisition unit that acquires usage status information regarding at least one of the usage status of the settlement application and the application list by the user. The proposal unit proposes the application information to the user on the user terminal based on the usage status information acquisition unit, the usage status information acquisition unit. The settlement system according to (3). (3) The settlement system described in. (3) The settlement system described in. (5) The settlement system further includes a change determination unit that determines whether or not a change has occurred in the application list. The proposal unit proposes the application information to the user on the user terminal when it is determined by the change determination unit that a change has occurred in the application list. The settlement system according to (3) or (4). (3) or (4) The settlement system described in. (3) or (4) The settlement system described in. (6) The settlement information acquisition unit acquires the settlement information indicating the settlement amount in the settlement. The app information acquisition unit acquires the app information based on the settlement amount indicated by the settlement information. (1)~(5) The settlement system according to any one of the above. (7) The settlement information acquisition unit acquires the settlement information indicating the settlement location in the settlement. The app information acquisition unit acquires the app information based on the settlement location indicated by the settlement information. (1)~(6) The settlement system according to any one of the above. (8) The settlement information acquisition unit acquires the settlement information indicating the settlement means used in the settlement. The app information acquisition unit acquires the app information based on the settlement means indicated by the settlement information. (1)~(7) The settlement system according to any one of the above. (9) The settlement information acquisition unit acquires the settlement information indicating the settlement frequency of the user who executed the settlement. The app information acquisition unit acquires the app information based on the settlement frequency indicated by the settlement information. (1)~(8) The settlement system according to any one of the above. (10) The settlement information acquisition unit acquires the settlement information indicating the goods or services subject to the settlement. The app information acquisition unit acquires the app information based on the goods or services indicated by the settlement information. (1)~(9) The settlement system according to any one of the above. (11) The settlement information acquisition unit acquires the settlement information indicating the settlement time when the settlement was executed. The app information acquisition unit acquires the app information based on the settlement time indicated by the settlement information. (1)~(10) The settlement system according to any one of the above. (12) The payment system further includes an other service information acquisition unit that acquires other service information about the user in another service different from the payment service. The app information acquisition unit acquires the app information based further on the other service information. (1)~(11) The payment system according to any one of (1) to (11). (13) The payment system further includes a user attribute information acquisition unit that acquires user attribute information about the attributes of the user. The app information acquisition unit acquires the app information based further on the user attribute information. (1)~(12) The payment system according to any one of (1) to (12). (14) The payment system further includes an app operation information acquisition unit that acquires app operation information about operations by the user on the app. The app information acquisition unit acquires the app information based further on the app operation information. (1)~(13) The payment system according to any one of (1) to (13). (15) The proposal unit can also propose other information other than the app information to the user when the payment is executed. The payment system further includes a selection unit that selects information to be proposed to the user from among a plurality of information including the app information and the other information based on the payment information. When the app information is selected by the selection unit, the proposal unit proposes the app information. (1)~(14) The payment system according to any one of (1) to (14). (16) The app information acquisition unit determines the relevance between each of a plurality of pieces of app information that are candidates for proposals to the user and the user based on the payment information, and acquires the app information with relatively high relevance. The proposal unit proposes the app information with relatively high relevance to the user on the user terminal. (1)~(15) The payment system according to any one of (1) to (15). (17) When the user executes the payment using the payment application of the user terminal, the payment information acquisition unit acquires the payment information, The application information acquisition unit acquires the application information regarding the mini-app in the payment application, The proposal unit proposes the application information to the user in the payment application of the user terminal. The payment system according to any one of (1) to (16).

Explanation of Signs

[0167] 1 Payment system, N Network, 10 Payment server, 11, 21, 31, 41 Control unit, 12, 22, 32, 42 Storage unit, 13, 23, 33, 43 Communication unit, 20 Related server, 30 User terminal, 34, 44 Operation unit, 35, 45 Display unit, 36 Photographing unit, 40 Store terminal, 46 Reading unit, 100 Data storage unit, 101 Payment execution unit, 102 Payment information acquisition unit, 103 Application information acquisition unit, 104 Proposal unit, 105 Usage status information acquisition unit, 106 Change determination unit, 107 Other service information acquisition unit, 108 User attribute information acquisition unit, 109 Application operation information acquisition unit, 110 Selection unit, 200 Data storage unit, 201 Related service providing unit, 300 Data storage unit, 301 Operation reception unit, 302 Display control unit, 400 Data storage unit, 401 Payment execution unit, DB User database, C10 Code, I20 Application information, I21 Information, L11 Application list, M12 Modal, SC1 Top screen, SC2 Payment completion screen, SC3 Application screen, L120 Application list.

Claims

1. A settlement information acquisition unit that acquires settlement information regarding the settlement when a user who uses a settlement service executes the settlement using a user terminal; An application information acquisition unit that acquires application information regarding an application of a related service related to the settlement based on the settlement information; A proposal unit that proposes the application information to the user on the user terminal; A settlement system including the above.

2. The proposal unit proposes the application information to the user on a settlement completion screen displayed on the user terminal when the settlement is completed. The settlement system according to Claim 1.

3. The user executes the settlement using a settlement application installed on the user terminal. The proposal unit proposes the application information to the user on the user terminal for displaying an application list regarding the list of the applications. The settlement system according to Claim 1 or 2.

4. The settlement system further includes a usage status information acquisition unit that acquires usage status information regarding at least one of the usage status of the settlement application and the application list by the user. The proposal unit proposes the application information to the user on the user terminal based on the usage status information. The settlement system according to Claim 3.

5. The settlement system further includes a change determination unit that determines whether or not a change has occurred in the application list. When the change determination unit determines that a change has occurred in the application list, the proposal unit proposes the application information to the user on the user terminal. The settlement system according to Claim 3.

6. The settlement information acquisition unit acquires the settlement information indicating the settlement amount in the settlement. The application information acquisition unit acquires the application information based on the settlement amount indicated by the settlement information. The settlement system according to Claim 1 or 2.

7. The settlement information acquisition unit acquires the settlement information indicating the settlement location in the settlement. The application information acquisition unit acquires the application information based on the settlement location indicated by the settlement information. The settlement system according to Claim 1 or 2.

8. The settlement information acquisition unit acquires the settlement information indicating the settlement means used in the settlement. The application information acquisition unit acquires the application information based on the settlement means indicated by the settlement information. The settlement system according to Claim 1 or 2.

9. The payment information acquisition unit acquires the payment information indicating the payment frequency of the user who executed the payment. The app information acquisition unit acquires the app information based on the payment frequency indicated by the payment information. The payment system according to claim 1 or 2.

10. The payment information acquisition unit acquires the payment information indicating the goods or services that are the subject of the payment. The app information acquisition unit acquires the app information based on the goods or services indicated by the payment information. The payment system according to claim 1 or 2.

11. The payment information acquisition unit acquires the payment information indicating the payment time when the payment was executed. The app information acquisition unit acquires the app information based on the payment time indicated by the payment information. The payment system according to claim 1 or 2.

12. The payment system further includes another service information acquisition unit that acquires other service information about the user in another service different from the payment service. The app information acquisition unit acquires the app information based on the other service information. The payment system according to claim 1 or 2.

13. The payment system further includes a user attribute information acquisition unit that acquires user attribute information about the attributes of the user. The app information acquisition unit acquires the app information based on the user attribute information. The payment system according to claim 1 or 2.

14. The payment system further includes an app operation information acquisition unit that acquires app operation information about the operations of the user on the app. The app information acquisition unit acquires the app information based on the app operation information. The payment system according to claim 1 or 2.

15. When the payment is executed, the proposal unit can also propose other information other than the app information to the user. The payment system further includes a selection unit that selects information to be proposed to the user from a plurality of information including the app information and the other information based on the payment information. When the app information is selected by the selection unit, the proposal unit proposes the app information. The payment system according to claim 1 or 2.

16. The app information acquisition unit determines the relevance between each of a plurality of pieces of the app information that are candidates for proposals to the user and the user based on the payment information, and acquires the app information with relatively high relevance. The proposal unit proposes the app information with relatively high relevance to the user on the user terminal. The payment system according to claim 1 or 2.

17. The payment information acquisition unit acquires the payment information when the user executes the payment using the payment app of the user terminal. The app information acquisition unit acquires the app information regarding the mini apps within the payment app. The proposal unit proposes the app information to the user in the payment app of the user terminal. The payment system according to claim 1 or 2.

18. A payment information acquisition step of acquiring payment information regarding the payment when a user who uses a payment service executes the payment using a user terminal; An app information acquisition step of acquiring app information regarding an app of a related service related to the payment based on the payment information; A proposal step of proposing the app information to the user on the user terminal; A proposal method including the above steps.

19. A payment information acquisition unit that acquires payment information regarding a payment when a user who uses a payment service executes the payment using a user terminal; An app information acquisition unit that acquires app information regarding an app of a related service related to the payment based on the payment information; A proposal unit that proposes the app information to the user on the user terminal; A program for causing a computer to function as the above units.

Images