Payment system, proposed method, and program

Abstract

App information regarding apps of related services related to the payment performed by the user is proposed. [Solution] A payment information acquisition unit (102) of a payment system (1) acquires payment information related to a payment when a user who uses a payment service makes a payment using a user terminal (30). An application information acquisition unit (103) acquires application information related to an application of a related service related to the payment based on the payment information. A suggestion unit (104) suggests application information to the user on the user terminal (30).

Description

[Technical field]

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

[0002] Conventionally, there is known a payment service in which a user executes a payment using a user terminal. For example, Patent Document 1 describes that when a user executes a payment using a payment app installed on the user terminal, a payment server selects an investment product based on the amount information of the payment, 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] Patent Publication No. 2022-104128 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the technology of Patent Document 1, investment products are only proposed to the user via a finance app, which is a mini app, so the user may not even 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 recommended to them. This point is also true for apps other than mini apps.

[0005] One objective of the present disclosure is to suggest app information regarding apps of related services related to a payment performed by a user. [Means for solving the problem]

[0006] The payment system of the present disclosure includes a payment information acquisition unit that acquires payment information related to a payment when a user who uses a payment service makes a payment using a user terminal, an app information acquisition unit that acquires app information related to an app of a related service related to the payment based on the payment information, and a proposal unit that proposes the app information to the user on the user terminal. Effect of the Invention

[0007] The present disclosure can suggest app information related to apps of related services related to a payment performed by a user. [Brief description of the drawings]

[0008] [Figure 1] FIG. 2 is a diagram illustrating an example of a hardware configuration of a payment system. [Diagram 2] FIG. 13 is a diagram illustrating an example of a screen displayed on a user terminal. [Diagram 3] FIG. 2 is a diagram showing an example of functions realized in the payment system. [Figure 4] FIG. 4 is a diagram illustrating an example of a user database. [Diagram 5] FIG. 2 is a diagram illustrating an example of a process executed in the payment system. [Figure 6] FIG. 13 is a diagram illustrating an example of a function realized in a modified example. [Figure 7] FIG. 13 is a diagram showing an example of a screen displayed on a user terminal in the first modification example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] [1. Hardware configuration of payment system] An example of an embodiment of a payment system, a proposed method, and a program according to the present disclosure will be described. Fig. 1 is a diagram showing an example of a hardware configuration of a payment system. For example, the payment system 1 includes a payment server 10, an associated server 20, a user terminal 30, and a store terminal 40. Each of the payment server 10, the associated 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 payment server 10 is a server computer for a payment service. The payment service is a service that provides electronic payment (cashless payment) to a user. For example, the payment server 10 includes a control unit 11, a memory unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The memory unit 12 includes at least one of a volatile memory such as 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 of the related service. The related service is a service related to payment. The related service can also be said to be a service linked to the payment service. In other words, the related service can also be said to be a service accessible via a payment app that provides the payment service. In this embodiment, a case is taken as an example in which a service provided by a card company that issues a credit card that can be used in the payment service corresponds to the related service, but the related service may be other services. For example, the related service may be an electronic commerce service, an online flea 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 a user's computer. For example, the user terminal 30 is a smartphone, a tablet, a personal computer, or a wearable terminal. The user terminal 30 includes a control unit 31, a memory unit 32, a communication unit 33, an operation unit 34, a display unit 35, and an imaging unit 36. The hardware configurations of the control unit 31, the memory unit 32, and the communication unit 33 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The operation unit 34 is an input device such as a touch panel or a mouse. The display unit 35 is a display such as a liquid crystal or organic EL. The imaging unit 36 ​​includes at least one camera.

[0013] The store terminal 40 is a computer of a store affiliated with the payment service. For example, the store terminal 40 is a POS terminal, a handheld terminal, a smartphone, a tablet, or a personal computer. The store terminal 40 includes a control unit 41, a memory 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 memory unit 42, the communication unit 43, the operation unit 44, and the display unit 45 may be similar to those of the control unit 11, the memory 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 reader / writer. The reading unit 46 may include at least one camera.

[0014] The program stored in the storage units 12, 22, 32, 42 may be supplied to the payment server 10, the associated server 20, the user terminal 30, or the store terminal 40 via the network N. At least one of a reading unit (e.g., a memory card slot) that reads a computer-readable information storage medium and an input / output unit (e.g., a USB port) for inputting and outputting data to and from an external device may be included in the payment server 10, the associated server 20, the user terminal 30, or the store terminal 40. For example, a program stored in an information storage medium may be supplied to the payment server 10, the associated 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] Furthermore, 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 associated 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 associated 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, a user operates the user terminal 30 to use the payment service. The user can use any payment means in the payment service. A payment means is a means used by a user for payment. For example, a payment means may be a credit card, electronic money, points, cryptocurrency, a debit card, a wallet, an account such as a bank account, or other means. Codes such as barcodes or two-dimensional codes are also means for payment and therefore correspond to a payment means. A payment means can also be called a payment means.

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

[0018] FIG. 2 is a diagram showing an example of a screen displayed on the user terminal 30. For example, when a payment application is started, as shown in the upper left of FIG. 2, the user terminal 30 displays a top screen SC1 including a code C10 generated based on a code ID that can temporarily identify a user on the display unit 35. 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, a payment is executed based on the code ID acquired from the code C10. In the example of FIG. 2, a credit card is set as the payment source, so a payment is executed based on the credit card. The process for the payment may be a known process.

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

[0020] In this embodiment, an installment payment app for making installment payments after the fact is proposed to the user on the payment completion screen SC2 indicating that the payment has been completed according to the payment amount. The installment payment app is an application provided by the card company of the credit card used in the payment. In this embodiment, the payment app is a super app, and the installment payment app is a mini app. The super app is an app that manages multiple mini apps. The mini app is an app that is called from the super app. Note that the mini app in this embodiment includes an app that operates based on the payment app as a super app, but also includes an app that transitions to an app provided by the related server 20 via the payment app. Furthermore, the mini app may also include an app that transitions to a screen display of a website via the payment app. As shown in the upper left of FIG. 2, the top screen SC1 includes an app list L11 that shows a list of mini apps.

[0021] For example, a user can launch an installment payment app from the app list L11 on the top screen SC1, but for large payments, the installment payment app can be launched directly from the payment completion screen SC2. When the user's payment amount is equal to or greater than a threshold, the user terminal 30 displays the payment completion screen SC2 including app information I20 indicating the installment payment app on the display unit 35, as shown in the upper right of Fig. 2. Users who have made large payments are highly likely to wish to pay in installments, and can therefore proceed with the installment payment procedure directly from the payment completion screen SC2.

[0022] For example, when a user selects app information I20 for an installment payment app, the user terminal 30 launches the installment payment app and displays an app screen SC3 for installment payments on the display unit 35, as shown in the lower right of Fig. 2. Generally, it may take several days for a payment to be reflected on a screen that manages credit card usage, but in this embodiment, payment information is sent from the payment app to the installment payment app. Based on that information, the user terminal 30 can display an app screen SC3 for accepting an installment payment application on the display unit 35 immediately after payment.

[0023] On the other hand, when the user's payment amount is less than the threshold, the payment amount is low, so the probability that the user will desire an installment payment app is low. For this reason, as shown in the lower left of Fig. 2, the user terminal 30 displays a payment completion screen SC2 that does not include app information I20 of the installment payment app on the display unit 35. For example, when the user's payment amount is less than the threshold, the payment completion screen SC2 includes other information I21 that shows advertisements for other services, such as electronic commerce services. When the user's payment amount is less than the threshold, the payment completion screen SC2 may include app information I20 of other apps (e.g., a points management app) other than the installment payment app.

[0024] As described above, when a user makes a payment using the user terminal 30, the payment system 1 of this embodiment determines whether the payment amount of the payment is equal to or greater than the threshold. When it is determined that the payment amount of the payment is equal to or greater than the threshold, the payment system 1 displays the app information I20 of the installment payment app on the payment completion screen SC2. This allows the payment system 1 to suggest to the user an installment payment app that is likely to be used by a user who has made a high-value payment.

[0025] On the other hand, when the payment system 1 determines that the payment amount of the payment is less than the threshold, it displays app information I20 of apps other than the installment payment app, or other information I21 such as advertisements for other services on the payment completion screen SC2. This allows the payment system 1 to suggest other useful information to the user when the probability that the user will use the installment payment app is low. Details of the payment system 1 will be described below.

[0026] [3. Functions realized by the payment system] Fig. 3 is a diagram showing an example of functions realized by payment system 1. The units realized by payment system 1 can be integrated into one device, or can be further dispersed among devices.

[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 memory 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 section] The data storage unit 100 stores data necessary for the payment service. For example, the data storage unit 100 stores a user database DB.

[0029] Fig. 4 is a diagram showing an example of a user database DB. The user database DB is a database in which various information related to a user is stored. For example, the user database DB stores a user ID, a password, a code ID, payment method information, and payment history information. Other data may be stored in the user database DB. For example, the user database DB may store payment source information related to a payment method set by the user as a payment source, or charge source information related to a payment method set by the user as a charge source of electronic money.

[0030] The user ID is an example of user identification information that can identify a user. A login account may exist in addition to the user ID. The login account may be freely changeable by the user. The password is information that is confirmed at the time of login. The code ID is also an ID that can identify a user in the payment service. The code ID is updated every time the code C10 is displayed.

[0031] Payment method information is information that enables a user to identify payment methods that can be used for a payment service. For example, payment method information is information such as a credit card number, an electronic money number, or a point card number balance. Payment history information is information related to the user's usage history of a payment service. For example, payment history information indicates the date and time of payment, the place of payment, the payment amount, the payment target, or a combination of these. When a user makes a payment, the payment execution unit 101 described below updates the payment history information to indicate the details of the payment.

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

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

[0034] The process executed by the payment execution unit 101 is not limited to the above example. In the case of a type of payment in which a code displayed on the store terminal 40 is read by the user terminal 30, a type in which a code posted in a store is read by the user terminal 30, a type in which the payment is completed only by operating the user terminal 30, a type in which an IC chip in the user terminal 30 is used, or other types of payment, the payment execution unit 101 only needs to acquire information necessary for the payment and execute the payment by communicating with at least one of the user terminal 30 and the store terminal 40. When the payment execution unit 101 executes a payment, it updates the user's payment history information to indicate the content of the executed payment.

[0035] [Payment Information Acquisition Department] When a user who uses a payment service makes a payment using the user terminal 30, the payment information acquisition unit 102 acquires payment information related to the payment. When a user makes a payment using the user terminal 30, the user performs an operation for payment from the user terminal 30. For example, when a user performs an operation for starting a payment app, an operation for displaying the code C10, an operation for causing the store terminal 40 to read the code C10, or other operation, this corresponds to the user performing a payment using the user terminal 30. Information processing for performing the payment is executed by the payment execution unit 101.

[0036] In this embodiment, the payment information acquisition unit 102 acquires payment information when a user executes a payment using a payment app on the user terminal 30. 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 a 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 not be information included in the payment request, but may be information indicating the result of the execution of the payment. In other words, the payment information may be information indicating whether or not the payment has been executed.

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

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

[0039] The application information I20 may mean data related to an application, but in this embodiment, it means an object (e.g., an image or text) visually displayed on the payment completion screen SC2. Actual data for displaying the application information I20 is pre-stored in the data storage unit 100. The application information acquisition unit 103 acquires the application information I20 by acquiring the actual data. The actual data for displaying the application information I20 may not be pre-stored in the data storage unit 100, but may be dynamically generated on the spot. In this case, it is presumed that original data for the application information I20 is stored in the data storage unit 100. The application information acquisition unit 103 may generate the application information I20 based on the original data.

[0040] In this embodiment, the service of the card company that issued the credit card set by the user as the payment source corresponds to the related service, so the app information acquisition unit 103 acquires 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. The threshold is an amount that serves as a criterion for determining whether or not to display the app information I20. The threshold may be common to all users, or may be determined according to the user. For example, a threshold may be set for each demographic information such as the user's gender or age group. The threshold is assumed to be 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 a threshold, 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 a threshold, 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 a threshold, the app information acquisition unit 103 acquires other information I21 such as an advertisement to be displayed instead of the app information I20. It is assumed that the data of the other information I21 is also stored in the data storage unit 100.

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

[0043] The other apps other than the installment payment app are apps that are likely to interest users who have made low-value payments. For example, the other apps may be a points management app that allows users to manage their own points, an advertising app that allows users to earn points when they view advertisements, an app that allows users to take pictures of receipts and upload them, or a coupon app that allows users to earn coupons. These other apps may be mini apps. Actual data for displaying the app information I20 of these other apps may be stored in advance in the data storage unit 100.

[0044] [Proposal Department] The suggestion unit 104 suggests the app information I20 to the user on the user terminal 30. In this embodiment, the suggestion unit 104 suggests the app information I20 to the user on the payment application 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 this embodiment, the suggestion unit 104 suggests the app information I20 to the user on a 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 is completed. For example, the payment completion screen SC2 displays a message indicating that the payment is completed, the payment location, the payment date and time, the payment amount, the payment target, or a combination of these. In this embodiment, a case where the suggestion unit 104 displays the payment completion screen SC2 itself is taken as an example, but the payment completion screen SC2 may be displayed by a function other than the suggestion 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 as a pop-up on the payment completion screen SC2 or a new screen superimposed on the payment completion screen SC2.

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

[0046] In this embodiment, the suggestion unit 104 suggests the app information I20 indicating the installment payment app to the user when the payment amount indicated by the payment information is equal to or greater than the threshold. When the payment amount indicated by the payment information is less than the threshold, the suggestion unit 104 does not suggest the app information I20 indicating the installment payment app to the user. In the example of FIG. 2, when the payment amount indicated by the payment information is less than the threshold, the suggestion unit 104 suggests other information I21 such as advertisements for other services to the user. When the payment amount indicated by the payment information is less than the threshold, the suggestion unit 104 may not make any suggestion. For example, when the payment amount indicated by the payment information is equal to or greater than the threshold, the suggestion unit 104 may suggest the app information I20 of the first app (in this embodiment, the installment payment app) to the user, and when the payment amount indicated by the payment information is less than the threshold, the suggestion unit 104 may suggest the app information I20 of the second app (in this embodiment, an app other than the installment payment app) to the user.

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

[0048] [3-2. Functions realized by related servers] 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 section] The data storage unit 200 stores data necessary for the related service. For example, the data storage unit 200 stores a database in which various information related to users who use the related service is stored. In this embodiment, the services provided by the card company that issued the credit card correspond to the related service, so the database stores various information related to the credit card. For example, the database stores the credit card number, expiration date, name of the cardholder, credit card usage history, payment method 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 Department] The related service providing unit 201 provides related services to the user based on the data stored in the data storage unit 200. In this embodiment, the services provided by the card company that issued the credit card correspond to the related services, so the related service providing unit 201 provides various services, including a service for viewing the credit card usage history and a service for changing the payment method, such as a lump sum payment or installment payment. In the example of FIG. 2, the related service providing 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 realized on user terminals] For example, the user terminal 30 includes a data storage unit 300, an operation reception unit 301, and a display control unit 302. The data storage unit 300 is realized by the storage unit 32. The operation reception unit 301 and the display control unit 302 are realized by the control unit 31.

[0052] [Data storage section] The data storage unit 300 stores data necessary for the user to use a 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 the payment application, the data storage unit 300 stores the browser.

[0053] [Operation reception section] The operation reception unit 301 receives various operations by the user. For example, the operation reception unit 301 receives an operation for a payment application. The operation reception unit 301 transmits data indicating the content of the user's operation to the payment server 10.

[0054] [Display control section] The display control unit 302 displays various screens on the display unit 35. For example, the display control unit 302 displays a top screen SC1, a payment completion screen SC2, and an application screen SC3 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 displaying these screens, and displays these screens on the display unit 35.

[0055] [3-4. Functions realized by store terminals] 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 section] The data storage unit 400 stores data necessary for providing a payment service to a user. For example, the data storage unit 400 stores a database in which various information such as prices of products or services handled by a store is stored. The data storage unit 400 also stores information on products or services for which a user is to make a payment. The data storage unit 400 may store information on the location where the store terminal 40 is located.

[0057] [Payment Execution Department] The payment execution unit 401 provides a payment service 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 a code ID from the code C10. The payment execution unit 401 acquires a payment amount based on the result of reading 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 any request used in a known payment service. The payment execution unit 401 acquires a result of the execution of the payment from the payment server 10 and completes the payment at the store. This series of processes may also be any process adopted in a known payment service.

[0058] [4. Processing performed by the payment system] Fig. 5 is a diagram showing an example of a process executed in payment system 1. Control units 11, 21, 31, and 41 execute programs stored in storage units 12, 22, 32, and , respectively, to execute the process in Fig. 5.

[0059] As shown in FIG. 5, when the payment application is started on the user terminal 30, the payment server 10 executes a process for displaying the top screen SC1 between the user terminal 30 and the payment server 10 (S1). In S1, the payment server 10 has the user log in to the payment service, generates a code ID, and transmits 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), it 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), it executes the payment based on the payment request (S5).

[0060] The payment server 10 refers to the payment request received in S4 and acquires payment information indicating the payment amount of the payment executed in S5 (S6). The payment server 10 judges whether the payment amount indicated by the payment information acquired in S6 is equal to or greater than a threshold (S7). If it is judged in S7 that the payment amount is equal to or greater than the threshold (S7: Y), the payment server 10 acquires the application information I20 of the installment payment application (S8). The payment server 10 executes a process between the user terminal 30 and the payment server 10 to propose the application information I20 of the installment payment application on the payment completion screen SC2 (S9). In S9, the payment server 10 generates display data of the payment completion screen SC2 including the application information I20 of the installment payment application and transmits it to the user terminal 30. The user terminal 30 displays the payment completion screen SC2 as shown in the upper right of FIG. 2 on the display unit 35.

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

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

[0063] [5. Summary of the embodiment] In the present embodiment, when a user who uses a payment service executes a payment using a user terminal 30, the payment system 1 acquires payment information related to the payment. Based on the payment information, the payment system 1 acquires app information I20 related to an app of a related service related to the payment. The payment system 1 proposes the app information I20 to the user on the user terminal 30. This allows the payment system 1 to propose to the user app information I20 of a related service related to the payment executed by the user. For example, the payment system 1 can promote the use of apps by users. The payment system 1 can improve user convenience because it eliminates the need for the user to search for and launch a desired app from within the user terminal 30.

[0064] Furthermore, when payment is completed, the payment system 1 proposes the app information I20 to the user on the payment completion screen SC2 that is displayed on the user terminal 30. This allows the payment system 1 to more effectively propose the app information I20 to the user by proposing the app information I20 on the payment completion screen SC2 that is likely to be noticed by the user.

[0065] Furthermore, the payment system 1 acquires payment information indicating the payment amount in the payment. The payment system 1 acquires the app information I20 based on the payment amount indicated by the payment information. This allows the payment system 1 to propose to the user app information I20 according to the payment amount. For example, the payment system 1 can improve user convenience by suggesting to the user app information I20 of an installment payment app that is likely to interest users who have made high-value payments. Conversely, the payment system 1 can improve user convenience by suggesting to the user app information I20 of a point management app that is likely to interest users who have made low-value payments.

[0066] Furthermore, the payment system 1 acquires payment information when a user makes a payment using a payment app in the user terminal 30. The payment system 1 acquires app information I20 related to a mini app in the payment app. The payment system 1 proposes the app information I20 to the user in the payment app in the user terminal 30. This makes it possible to propose to the user the app information I20 of the mini app related to the payment made by the user. For example, the payment system 1 can promote the use of mini apps by the user.

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

[0068] 6 is a diagram showing an example of functions realized in the modified 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 application 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 other service information acquisition unit 107, the user attribute information acquisition unit 108, the application operation information acquisition unit 109, and the selection unit 110 is realized by the control unit 11.

[0069] [6-1. Variation 1] For example, as described in the embodiment, on the top screen SC1 of the payment app, apps are displayed in a selectable manner in the app list L11 on the screen. The app list L11 may be included on a screen other than the top screen SC1. The app list L11 may be included on a screen other than the top screen SC1, which corresponds to a so-called first view. For example, the app list L11 may be included on a screen that is displayed when a user selects a menu icon on the payment app, a screen that shows the usage history of the payment app, or a screen that accepts settings for the payment app.

[0070] Displaying an app so that it can be selected means that an image of the app (in the example of FIG. 2, an icon such as "invoice" or "installment payment") or text of the app is displayed so that the app is launched when the user selects the app. For example, displaying an image or text including information that can identify the app (for example, a link or ID of the app) corresponds to displaying an app so that it can be selected. The number of apps displayed in the app list L11 may be any number. For example, in the app list L11, about 7 to 8 apps are displayed so that they can be selected, and when the user performs an operation to display more apps, the user terminal 30 may cause the display unit 35 to display more apps so that they can be selected.

[0071] For example, when a payment application is launched on the user terminal 30 and the user logs in to the payment service, the payment server 10 generates display data for a top screen SC1 including an application list L11. Data indicating applications to be included in the application list L11 is assumed to be stored in advance in the data storage unit 100 of the payment server 10. The payment server 10 arranges applications in the application list L11 based on the data, generates display data for the top screen SC1, and transmits the display data 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 application list L11 on the display unit 35.

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

[0073] Fig. 7 is a diagram showing an example of a screen displayed on the user terminal 30 of the first modified example. For example, when the user performs an operation to display details in the application list L11 (for example, an operation to select "View all" in the application list L11) in the state of the top screen SC1 in the upper left of Fig. 7, the user terminal 30 displays on the display unit 35 a modal M12 including an application list L120 from which more applications can be selected, as shown in the upper right of Fig. 7. When the user selects an application from the application list L120, the user terminal 30 launches the application.

[0074] The suggestion unit 104 of the first modification suggests app information I20 for displaying an app list L120 related to a list of apps to the user on the user terminal 30. In the first modification, as in the embodiment, a case in which the app information I20 is suggested 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 suggestion unit 104 displays the app information I20 for displaying the app list L120 on the payment completion screen SC2, as shown in the lower left of FIG.

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

[0076] The payment system 1 of the first modification proposes app information I20 for displaying the app list L120 to the user on the user terminal 30. The payment system 1 can let more users know about the existence of apps of related services related to the payment app.

[0077] [6-2. Variation 2] For example, suggesting the application information I20 for displaying the application list L120 as in the modified example 1 is effective for a beginner user who does not know the existence of the application list L120 in the first place, or a user who has not used the application list L120 much. On the other hand, a user who has been using a payment application for a long time, or a user who frequently uses the application list L120, knows the existence of the application list L120, and therefore it may be better to suggest the application information I20 of a specific application as in the embodiment, rather than the application information I20 as in the modified example 1. Therefore, in the modified example 2, the application information I20 for displaying the application list L120 as in the modified example 1 is proposed to a user who does not use the application list.

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

[0079] The usage status of the payment app is the period since the start of use of the payment app, or the user's operations on the payment app. The usage status of the payment app may indicate whether the user is a beginner or not. A beginner is a user who has been using the payment app for less than a predetermined period of time (e.g., the period from registration for use of a payment service). The usage status of the app lists L11, L120 is the operations on the apps displayed in the app lists L11, L120. For example, the number of times or frequency of use of an app displayed in the app lists L11, L120 corresponds to the usage status of the app lists L11, L120.

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

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

[0082] For example, the usage status information indicates the usage status of the payment app itself. The suggestion unit 104 may determine whether or not the user is a beginner based on the usage status of the payment app itself indicated by the usage status information. If the user is not determined to be a beginner, the suggestion unit 104 does not suggest the app information I20 in the app list L120, and if the user is determined to be a beginner, the suggestion unit 104 suggests the app information I20 in the app list L120.

[0083] For example, the suggestion unit 104 may calculate the startup frequency of the payment app based on the usage status of the payment app indicated by the usage status information, and suggest 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 greater than a predetermined frequency, the suggestion unit 104 does not suggest the app information I20 in the app list L120. If the startup frequency of the payment app is less than the predetermined frequency, the suggestion unit 104 suggests the app information I20 in the app list L120.

[0084] For example, the suggestion unit 104 may determine whether the user has made a payment or whether the number of payments in a predetermined period is equal to or greater than a predetermined number based on the usage status of the payment app indicated by the usage status information, and may suggest the app information I20 in the app list L120 based on the result of the determination. If it is determined that the user has made a payment or the number of payments in a predetermined period is equal to or greater than a predetermined number, the suggestion unit 104 does not suggest the app information I20 in the app list L120. If it is determined that the user has not made a payment or the number of payments in a predetermined period is less than a predetermined number, the suggestion unit 104 suggests the app information I20 in the app list L120.

[0085] For example, the usage status information indicates the usage status of the application lists L11 and L120. The suggestion unit 104 may determine whether an operation for displaying the application list L120 (for example, selection of "View all" in the application list L11) has been performed or whether the number of times of the operation during a predetermined period is equal to or greater than a predetermined number of times based on the usage status information, and may suggest the application information I20 of the application list L120 based on the result of the determination. If an operation for displaying the application list L120 has been performed or if the number of times of the operation during a predetermined period is equal to or greater than a predetermined number of times, the suggestion unit 104 does not suggest the application information I20 of the application list L120. If there is no operation for displaying the application list L120 or if the number of times of the operation during a predetermined period is less than the predetermined number of times, the suggestion unit 104 suggests the application information I20 of the application list L120.

[0086] For example, the suggestion unit 104 may determine whether or not an operation has been performed on an app displayed in the app list L11, L120, or whether or not the number of times of the operation during a predetermined period is equal to or greater than a predetermined number, based on the usage status information, and may suggest the app information I20 of the app list L120 based on the result of the determination. If an operation has been performed on an app in the app list L11, L120, or if the number of times of the operation during a predetermined period is equal to or greater than a predetermined number, the suggestion unit 104 may not suggest the app information I20 of the app list L120. If there has been no operation on an app in the app list L11, L120, or if the number of times of the operation during a predetermined period is less than a predetermined number, the suggestion unit 104 may suggest the app information I20 of the app list L120. That is, the suggestion unit 104 may suggest the app information I20 of the app list L120 to a user who has never launched an app, a user who has launched less than a predetermined number of apps, or a user who has launched an app less than a predetermined number of times.

[0087] The payment system 1 of the second modification proposes the app information I20 to the user on the user terminal 30 based on the usage status information. In this way, the payment 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 payment app and the app lists L11 and L120 by the user. As a result, the payment system 1 can promote the use of the app. For example, the payment system 1 can encourage a user who does not use a payment app at all or who does not use a payment app very often to use the apps in the app lists L11 and L120. The payment system 1 can encourage a user who does not use any apps displayed in the app lists L11 and L120 at all or who does not use apps displayed in the app lists L11 and L120 very often to use the apps displayed in the app lists L11 and L120.

[0088] [6-3. Variation 3] For example, new apps may be added to the app lists L11 and L120, or existing apps may be deleted. Furthermore, the layout of the app lists L11 and L120 may be changed, or the order of apps in the app lists L11 and L120 may be changed. Alternatively, update information such as a campaign may be available for a specific app, or a version upgrade may be available for a specific app. In such a case, when a change occurs in the app lists L11 and L120, the user may be notified of the change in the app lists L11 and L120 by the app information I20 for displaying the app lists L11 and L120.

[0089] The payment system 1 of the third modification includes a change determination unit 106. The change determination unit 106 determines whether or not a change has occurred in the application lists L11 and L120. Change presence / absence data indicating whether or not a change has occurred in the application lists L11 and L120 is assumed to be stored in advance in the data storage unit 100. For example, when an update occurs in the payment application and a change occurs in the application lists L11 and L120, the payment server 10 updates the change presence / absence data to indicate that a change has occurred in the application lists L11 and L120 based on an operation by an administrator of the payment service.

[0090] The change determination unit 106 may automatically determine whether a change has occurred in the application lists L11, L120 based on the contents of an update to the payment application, rather than on the administrator's operation. In this case, the data storage unit 100 stores the history of the payment application. When the payment application is updated, the change determination unit 106 may compare the payment application before the update stored as the history of the payment application with the payment application after the update to determine whether a change has occurred in the application lists L11, L120.

[0091] When the change determination unit 106 determines that a change has occurred in the application lists L11, L120, the suggestion unit 104 of the third modification proposes application information I20 for displaying the application lists L11, L120 to the user on the user terminal 30. When the change determination unit 106 determines that no change has occurred in the application lists L11, L120, the suggestion unit 104 does not propose application information I20 for displaying the application lists L11, L120 to the user on the user terminal 30. In this case, the suggestion unit 104 may propose application information I20 of a specific application as in the embodiment, or may propose other information I21 such as an advertisement, to the user on the user terminal 30.

[0092] When the suggestion unit 104 suggests the app information I20 for displaying the app lists L11 and L120 to a certain user, the suggestion unit 104 may record data indicating that the app information I20 has been suggested in association with the user in the data storage unit 100. The suggestion unit 104 may not suggest the app information I20 again to the user for whom the data has been recorded. That is, after a change occurs in the app lists L11 and L120, the suggestion unit 104 may not suggest the app information I20 again to the user to whom the suggestion unit 104 suggested the app information I20 for displaying the app lists L11 and L120.

[0093] In addition, the second and third modified examples may be combined. In this case, the usage status information acquisition unit 105 may acquire usage status information when the change determination unit 106 determines that a change has occurred in the application list L11, L120. In this case, the usage status information may indicate the usage status after the change has occurred in the application list L11, L120. For example, when a change has occurred in the application list L11, L120, the payment server 10 resets the usage status information of each user. The payment server 10 updates the usage status information of the user based on the subsequent use of at least one of the payment app and the application list L11, L120 by the user. The suggestion unit 104 proposes the application information I20 of the application list L120 to the user at the user terminal 30 based on the usage status information indicating the usage status after the change has occurred in the application list L11, L120. The method of proposing the application information I20 based on the usage status information is as described in the second modified example.

[0094] The payment system 1 of the third modification judges whether or not a change has occurred in the application lists L11 and L120. When it is judged that a change has occurred in the application lists L11 and L120, the payment system 1 proposes application information I20 to the user on the user terminal 30. This allows the payment system 1 to 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 payment 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 payment system 1 can appeal to the user more effectively by proposing the application information I20 based on the usage status information after the change has occurred in the application lists L11 and L120.

[0095] [6-4. Variation 4] For example, in the embodiment, the payment information indicates the payment amount, but the payment information may indicate other information related to the payment. The payment information acquisition unit 102 in variant 4 acquires payment information indicating the payment location in the payment. The payment location is the location where the payment is made. The payment location is an affiliated party (e.g., a store) that is affiliated with the payment service and receives the payment in the payment. In variant 4, the payment is made at a store, so the payment information indicates the store where the payment was made. For example, the payment information indicates a store ID that can identify the store. The payment location may be specified by other information such as latitude and longitude rather than an ID such as a store ID.

[0096] In the fourth modification, the payment request received by the payment server 10 from the store terminal 40 includes information on the payment location. This information may be the store ID itself, or a store terminal ID that allows the payment 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 payment information acquisition unit 102 acquires the information on the payment location included in the payment request as payment information indicating the payment location. Since the payment history information also indicates the payment location, the payment information acquisition unit 102 may acquire the payment history information as payment information indicating the payment location.

[0097] The app information acquisition unit 103 of the fourth modification acquires app information I20 based on the payment location indicated by the payment information. Payment location relationship data indicating the relationship between the payment location and the app information I20 to be proposed to the user is assumed to be stored in advance in the data storage unit 100. The payment location relationship data may be in any format, such as a table format, a formula format, a part of a program code, or a machine learning model. The app information acquisition unit 103 acquires app information I20 associated with the payment location indicated by the payment information. Actual data of each piece of app information I20 is also assumed to be stored in the data storage unit 100.

[0098] For example, if the payment location relationship data is associated with app information I20 of an app of a store near the payment location, the app information acquisition unit 103 acquires the app information I20 of the store near the payment location based on the payment location relationship data. If the payment location relationship data is associated with app information I20 indicating an app of a store in the same category as the payment location or related to the payment location, the app information acquisition unit 103 acquires the app information I20 indicating an app of a store in the same category as the payment location or related to the payment location based on the payment location relationship data. If the payment location relationship data is associated with app information I20 of an app of a store in the same group as the payment location or a store in an affiliated relationship with the payment location, the app information acquisition unit 103 acquires the app information I20 of the app of the store in the same group as the payment location or a store in an affiliated relationship with the payment location based on the payment location relationship data.

[0099] For example, if the payment location relation data is associated with app information I20 of an app that manages a receipt issued at the payment location, the app information acquisition unit 103 acquires the app information I20 of the app that manages the receipt. If the payment location relation data is associated with app information I20 of an app that manages a campaign held at the payment location, the app information acquisition unit 103 acquires the app information I20 of the app that manages the campaign based on the payment location relation data. The app information acquisition unit 103 may acquire app information I20 of another app associated with the payment location. The suggestion unit 104 may suggest 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 of the embodiment, the process of suggesting the app information I20 by the suggestion unit 104 may be similar to that of the embodiment.

[0100] The payment system 1 of the fourth modification acquires payment information indicating a payment location for payment. The payment system 1 acquires app information I20 based on the payment location indicated by the payment information. The payment system 1 can suggest app information I20 according to the payment location to the user. For example, the payment system 1 can suggest the nearby store to the user by suggesting app information I20 of an app for a store near the payment location to the user, thereby increasing the effect of attracting customers to the nearby store. The payment system 1 can also promote the use of the app for the nearby store.

[0101] [6-5. Variation 5] For example, the payment information acquisition unit 102 of the fifth modified example acquires payment information indicating the payment method used in the payment. In the example of the payment app of FIG. 2, the payment information indicates the payment method set as the payment source. The payment source information indicating the payment source is stored in the user database DB. When the user performs an operation to change the payment source from the payment app, the payment server 10 updates the user's payment source information to indicate the payment source specified by the user. For example, when the user specifies a credit card as the payment source, the payment server 10 updates the user's payment source information to indicate the credit card. When the user specifies electronic money as the payment source, the payment server 10 updates the user's payment source information to indicate the electronic money.

[0102] For example, information on the payment method used in the payment may be included in the payment request received by the payment server 10 from the store terminal 40, but in the fifth modification, it is included in the payment source information stored in the user database DB. Therefore, when a payment is executed, the payment information acquisition unit 102 acquires the current payment source information to acquire payment information indicating the payment method used in the payment. When information indicating the payment method used in the payment is indicated in the payment history information, the payment information acquisition unit 102 may acquire the payment history information as payment information indicating the payment method.

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

[0104] For example, if the payment method related data is associated with a credit card and the app information I20 of the installment payment app, the app information acquisition unit 103 acquires the app information I20 of the installment payment app when the payment information indicates a credit card. If the payment method related data is associated with electronic money and the app information I20 of the balance check app for checking the balance of the electronic money, the app information acquisition unit 103 acquires the app information I20 of the balance check app when the payment information indicates electronic money.

[0105] For example, if a bank account and app information I20 of an account management app for managing a bank account are associated with the payment method related data, the app information acquisition unit 103 acquires the app information I20 of the account management app when the payment information indicates a bank account. Since coupons or points may also be usable as payment methods, if a coupon or points and app information I20 of an app for managing coupons or points are associated with the payment method related data, the app information acquisition unit 103 acquires the app information I20 of the app when the payment information indicates a coupon or points. The suggestion unit 104 may suggest 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 of the embodiment, the process of suggesting the app information I20 by the suggestion unit 104 may be similar to that of the embodiment.

[0106] The payment system 1 of the fifth modification acquires payment information indicating the payment method used in the payment. The payment system 1 acquires app information I20 based on the payment method indicated in the payment information. The payment system 1 can suggest app information I20 according to the payment method to the user. For example, when the user uses a credit card to make a payment, the payment system 1 suggests app information I20 of an installment payment app, so that the user does not need to search for an installment payment app by himself / herself among apps installed on the user terminal 30, thereby improving user convenience. The payment system 1 can suggest to the user an installment payment app that is useful for a user who uses a credit card.

[0107] [6-6. Variation 6] For example, the payment information acquisition unit 102 of the sixth modification acquires payment information indicating the payment frequency of a user who has made a payment. In the sixth modification, the payment information indicating the payment frequency is stored in the user database DB. The payment information of the sixth modification indicates the frequency of payments over a certain period of time (for example, the past month or year). For example, when a certain user makes 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 does not need to 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 the certain user based on the payment history information of the certain user.

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

[0109] For example, if the payment frequency relation data is associated with the payment frequency being equal to or greater than a threshold and the app information I20 of the point management app, the app information acquisition unit 103 acquires the app information I20 of the point management app when the payment frequency indicated by the payment information is equal to or greater than the threshold. If the payment frequency relation data is associated with the payment frequency being less than a threshold and the app information I20 of the campaign app, the app information acquisition unit 103 acquires the app information I20 of the campaign app when the payment frequency indicated by the payment information is less than a threshold. The suggestion unit 104 may suggest 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 of the embodiment, the process of the suggestion unit 104 suggesting the app information I20 may be the same as that of the embodiment.

[0110] The payment system 1 of the sixth modification acquires payment information indicating the payment frequency of a user who has made a payment. The payment system 1 acquires app information I20 based on the payment frequency indicated by the payment information. The payment system 1 can suggest app information I20 to the user according to the payment frequency. For example, a user with a relatively high payment frequency and a user with a relatively low payment frequency may be interested in different apps, so the payment system 1 can suggest to the user app information I20 of apps that the user is more likely to be interested in.

[0111] [6-7. Variation 7] For example, the payment information acquisition unit 102 of the seventh modification acquires payment information indicating the product or service that is the subject of payment. In the seventh modification, 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 payment. This information may be a general code such as a JAN code, or a code that is uniquely determined by the store. This information may be a character string indicating the product name or service name. The payment information acquisition unit 102 acquires information included in the payment request as payment information indicating the product or service that is the subject of payment. When the product or service that is the subject of payment is indicated 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 payment.

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

[0113] For example, if a vehicle, which is an example of a product to be paid, is associated with the payment target relationship data, and the application information I20 of an insurance application provided by an insurance company, the application information acquisition unit 103 acquires the application information I20 of the insurance application when the payment information indicates a vehicle. If a treatment at a beauty salon, which is an example of a service to be paid, is associated with the payment target relationship data, and the application information I20 of a beauty salon reservation application that accepts reservations at a beauty salon, the application information acquisition unit 103 acquires the application information I20 of the beauty salon reservation application when the payment information indicates a treatment at a beauty salon. The suggestion unit 104 may suggest 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 suggesting the application information I20 by the suggestion unit 104 may be the same as that of the embodiment.

[0114] The payment system 1 of the seventh modification acquires payment information indicating a product or service that is the subject of payment. The payment system 1 acquires app information I20 based on the product or service indicated by the payment information. The payment system 1 can suggest to the user app information I20 according to the product or service that is the subject of payment. For example, the payment system 1 can suggest app information I20 of an app that is more likely to interest the user by suggesting app information I20 according to the product or service that the user purchased through payment.

[0115] [6-8. Variation 8] For example, the payment information acquisition unit 102 of the eighth modification acquires payment information indicating the payment time when the payment was executed. The payment time may be expressed as a date and time, or may be expressed as only one of the day of the week, the date, or the time. In the eighth modification, when the payment execution unit 101 of the payment server 10 executes a payment, the payment information acquisition unit 102 acquires payment information indicating the current date and time as the payment time using a real-time clock or the like. Since the payment history information also indicates the payment time, the payment information acquisition unit 102 may acquire the payment history information as payment information indicating the payment time.

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

[0117] For example, the payment server 10 may specify in advance a daytime activity range and a nighttime activity range from user activity such as past payment history. In this case, the payment time relation data is associated with the daytime payment time and the app information I20 of the app provided by the store in the daytime activity range. Furthermore, the payment time relation data is associated with the nighttime payment time and the app information I20 of the app provided by the store in the nighttime activity range. When the payment information indicates a daytime time period, the app information acquisition unit 103 acquires the app information I20 of the app provided by the store in the daytime activity range. When the payment information indicates a nighttime time period, the app information acquisition unit 103 acquires the app information I20 of the app provided by the store in the nighttime activity range.

[0118] The payment time relation data may indicate a time other than daytime or nighttime. For example, the payment time relation data may indicate a relation 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 app information I20 according to whether the payment information indicates a weekday or weekend. The suggestion unit 104 may suggest 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 of the embodiment, the process of the suggestion unit 104 proposing the app information I20 may be the same as that of the embodiment. For example, the app information acquisition unit 103 may acquire the app information I20 according to whether the payment information indicates a specific day of the week (for example, a day of the off-season). If a store whose off-season is on Wednesday is running a campaign on Wednesday, the app information acquisition unit 103 may identify app information I20 of an app provided by the store running a campaign on Wednesday based on the payment time relationship data when the day of the week indicated by the payment information is Wednesday, and acquire the identified app information I20.

[0119] The payment system 1 of the eighth modification acquires payment information indicating the payment time when the payment was made. The payment system 1 acquires the app information I20 based on the payment time indicated by the payment information. The payment system 1 can suggest the app information I20 according to the payment time to the user. For example, since the app in which the user is interested may differ depending on the payment time, the payment system 1 can suggest the app information I20 of the app in which the user is more interested.

[0120] [6-9. Variation 9] For example, a user may use other services besides the payment service, such as an electronic commerce service, a travel reservation service, a communication service, or a financial service. Various information about the user may be recorded in the other services. For this reason, the payment system 1 may suggest app information I20 to the user based on not only the payment information but also the information about the user in the other services.

[0121] The payment system 1 of the 9th modification includes an other service information acquisition unit 107. The other service information acquisition unit 107 acquires other service information related to a user in other services different from the payment service. The other service information may be information of a user registered in the other service (e.g., demographic information such as the user's gender or age group) or information related to the user's use of the other service.

[0122] In variant 9, an example is taken of the other service being an e-commerce service. Furthermore, an example is taken of the other service information indicating the payment method (e.g., invoice payment or credit card payment) of the product purchased by the user through the e-commerce service. The payment information in variant 9 is assumed to be information indicating whether or not payment has been completed. The other service information acquisition unit 107 acquires the user's other service information from the computer of the e-commerce service (e.g., associated server 20 or another computer).

[0123] In variant example 9, the user ID is assumed to be common to the payment service and other services. The other service information acquisition unit 107 transmits the user ID of the user from which other service information is to be acquired to the computer of the other service. Upon receiving the user ID, the computer of the other service identifies the user for which other service information should be sent. The computer of the e-commerce service transmits the other service information of the identified user to the payment server 10. The other service information acquisition unit 107 acquires other service information from the computer of the other service.

[0124] The user ID may be different between the payment service and the other service. In this case, 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 sent based on the relationship.

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

[0126] In the ninth modification, a case is taken as an example in which the other service information indicates the payment method for a product purchased by a user through an electronic commerce service, so the app information acquisition unit 103 acquires app information I20 based on the payment method indicated by the other service information. For example, if the other service relation data is associated with the payment method being invoice payment and app information I20 of a bill payment app that enables invoice payment on the user terminal 30, the app information acquisition unit 103 acquires app information I20 of the bill payment app when the payment method indicated by the other service information is invoice payment.

[0127] For example, if the other service related data is associated with a payment method being credit card payment and app information I20 of a postpaid app, the app information acquisition unit 103 acquires the app information I20 of the postpaid app when the payment method indicated by the other service information is credit card payment. The suggestion unit 104 may suggest 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 of the embodiment, the process of suggesting the app information I20 by the suggestion unit 104 may be similar to that of the embodiment.

[0128] The other service information may indicate any content of the other service. The other service information may indicate content other than the user's payment method. For example, the other service information may indicate the price of a product or service purchased by the user from the other service. In this case, if the other service relation data is associated with the price being equal to or greater than a threshold and with the app information I20 of the installment payment app, 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 equal to or greater than the threshold.

[0129] For example, if the other service is a travel reservation service, the other service information may be a travel product reserved by the user. In this case, if the other service relation data indicates that the travel product reserved by the user is an overseas travel product and the app information I20 of an insurance app provided by an insurance company that handles overseas travel insurance, the app information acquisition unit 103 acquires the app information I20 of the present app when the travel product indicated by the other service information is an overseas travel product. Similarly, if the other service is a service other than an electronic commerce service or a travel reservation service, the app information acquisition unit 103 may acquire the app information I20 according to the other service information of the other service.

[0130] The other service relation data may also indicate the relationship between the payment information and the other service information and the application information I20 to be proposed to the user. In this case, the application information acquisition unit 103 may refer to the other service relation data and acquire the application information I20 associated with the payment information and the other service information.

[0131] The payment system 1 of the ninth modification acquires other service information related to the user in other services different from the payment service. The payment system 1 acquires app information I20 based further on the other service information. This allows the payment system 1 to propose optimal app information I20 to the user that also takes into consideration information in other services. For example, the payment system 1 proposes app information I20 of an invoice app to a user who has purchased a product by invoice payment in an e-commerce service, so that the user can pay the invoice using the invoice app after the product arrives.

[0132] [6-10. Variation 10] For example, the app information I20 that the user is interested in may differ depending on the user's attributes. Therefore, the payment system 1 may present the app information I20 according to the user's attributes. The payment system 1 of the modification 10 includes a user attribute information acquisition unit 108. The user attribute information acquisition unit 108 acquires user attribute information related to the user's attributes. The user's attributes can be said to be a classification of the user. For example, the user attribute information may indicate the user's age, residential area, sex, age group, family structure, behavioral characteristics in the payment service, or other attributes. In the modification 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 application information acquisition unit 103 of the modified example 10 acquires the application information I20 further based on the user attribute information. In the modified example 10, as in the modified example 9, a case is taken as an example in which the payment information is information indicating whether or not the payment has been completed. For example, when the payment information indicating the completion of the payment is acquired, the application information acquisition unit 103 acquires the application information I20 based on the user attribute information. It is assumed that the user attribute relationship data indicating the relationship between the user attribute information and the application 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 format such as a table format, a 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 user attribute information. It is assumed that the actual data of each application information I20 is also stored in the data storage unit 100.

[0134] For example, if the user attribute relationship data indicates that the user attribute is a family structure having children and that the app of a financial institution that provides a loan for educational expenses is associated with the user attribute, the app information acquisition unit 103 acquires app information I20 of the app of the financial institution when the user attribute information indicates the family structure. If the user attribute relationship data indicates that the user attribute is a family structure of a single person and that the property app that provides information on properties for single-person living is associated with the user attribute, the app information acquisition unit 103 acquires app information I20 of the property app when the user attribute information indicates the family structure. Similarly, for other user attributes, the app information acquisition unit 103 may acquire app information I20 of the app associated with the user attribute indicated by the user attribute information.

[0135] Furthermore, the user attribute relationship data may indicate the relationship between the payment information and the user attribute information, and the app information I20 to be proposed to the user. 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 the user attribute information. The suggestion unit 104 may suggest 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 of the embodiment, the process of the suggestion unit 104 suggesting the app information I20 may be similar to that of the embodiment.

[0136] The payment system 1 of the tenth modification acquires the application information I20 further based on the user attribute information. This allows the payment system 1 to propose to the user the optimal application information I20 that also takes into account the user's attributes. For example, the payment system 1 can propose to the user the application information I20 of an application that is likely to interest a user with a specific attribute.

[0137] [6-11. Variation 11] For example, when a user has already used an app, the app that should be suggested to the user may differ depending on the usage status of the app by the user. For this reason, the payment system 1 may suggest the app information I20 according to the operation of the user on the app. The payment system 1 of the modification 11 includes the app operation information acquisition unit 109. The app operation information acquisition unit 109 acquires app operation information related to the operation of the user on the app. The app operation information can also be information indicating the usage status of the app by the user. The app operation information is assumed to be stored in the user database DB. When a certain user performs some operation on the app, the payment server 10 updates the app operation information of the user. For example, the app operation information may be startup information (e.g., information indicating at least one of whether the app is started and the number of times it is started) related to the app started from the home screen (the screen at the top left of Figs. 2 and 7) of the payment app or the app list L11, L120. The app operation information may be startup information (e.g., information indicating at least one of whether the app is started and the number of times it is started) after the app information I20 is suggested.

[0138] In the eleventh modification, the application operation information indicates the number of times an application is started. The application operation information may indicate the number of times each of a plurality of applications is started. For example, when a user starts an application from the application list L11, the payment server 10 acquires data indicating that the user has started the application from the user terminal 30. The payment server 10 updates the application operation information based on the data so that the number of times the user has started the application increases. The payment server 10 may acquire data indicating the specific operation content performed by the user in the application from the user terminal 30, and update the application operation information of the user so as to indicate the specific operation content. The application operation information acquisition unit 109 acquires the application operation information thus updated from the user database DB.

[0139] The application information acquisition unit 103 of the eleventh modification acquires the application information I20 further based on the application operation information. In the eleventh modification, as in the ninth and tenth modifications, a case is taken as an example in which the payment information is information indicating whether or not the payment has been completed. For example, when the payment information indicating the completion of the payment 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 format such as a table format, a 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 application operation information. It is assumed that the actual data of each piece of application information I20 is also stored in the data storage unit 100.

[0140] For example, when the application operation information indicates the number of times an application is launched, and the application operation relationship data indicates the relationship between the number of times an application is launched and the application information I20 to be recommended to a user, the application information acquisition unit 103 acquires the application information I20 of an application that is launched relatively few times. The application information acquisition unit 103 may acquire the application information I20 of an application that is launched less than a threshold. Conversely, the application information acquisition unit 103 may acquire the application information I20 of an application that is launched relatively many times. The application information acquisition unit 103 may acquire the application information I20 of an application that is launched more than a threshold.

[0141] In addition, when the application operation information indicates specific operation contents in the application, rather than the number of times the application is launched, the application information acquisition unit 103 may acquire application information I20 according to the specific operation contents indicated by the application operation information. In this case, the application operation relation data indicates the relationship between the specific operation contents in the application and the application information I20 to be proposed to the user. The application information acquisition unit 103 may acquire application information I20 associated with the specific operation contents in the application.

[0142] Furthermore, the application operation relationship data may indicate a relationship between the payment information and the application operation information, and the application information I20 to be proposed to the user. In this case, the application information acquisition unit 103 may refer to the application operation relationship data and acquire the application information I20 associated with the payment information and the application operation information. The suggestion unit 104 may suggest 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 suggestion unit 104 suggesting the application information I20 may be similar to that of the embodiment.

[0143] The payment system 1 of the eleventh modification acquires the application information I20 further based on the application operation information. This allows the payment system 1 to propose to the user the optimal application information I20 that also takes into account the user's operation on each application. For example, the payment system 1 can inform the user of the existence of an application that the user does not usually use by proposing to the user the application information I20 of an application that the user does not often select. The payment system 1 can save the user the trouble of searching for and launching an application that the user usually uses by proposing to the user the application information I20 of an application that the user often selects. For example, the payment system 1 can also prevent the next time from proposing an application that the user has selected and launched by selecting the application information I20. In this case, the payment system 1 can prevent the user from repeatedly proposing an application that the user is aware of.

[0144] [6-12. Variation 12] For example, as described in the embodiment, when a payment is made, the suggestion unit 104 can suggest other information I21 other than the app information I20 to the user. In the example of Fig. 2, the suggestion unit 104 can also suggest other information I21 showing an advertisement on the payment completion screen SC2. Although the payment completion screen SC2 is a screen that attracts the user's attention, there is a limit to the information that can be displayed therein, so information more suitable for the user may be selected based on the payment information.

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

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

[0147] In the twelfth modification, as in the embodiment, a case is taken as an example in which the payment information indicates a payment amount. The proposal relationship data indicates a relationship between whether the payment amount is equal to or greater than a threshold and information to be proposed to the user among a plurality of pieces of information (at least one of the application information I20 and the other information I21). For example, based on the proposal relationship data, the selection unit 110 selects the application information I20 of an installment payment application when the payment amount indicated by the payment information is equal to or greater than a threshold. Based on the proposal relationship data, the selection unit 110 selects other information I21 such as an advertisement when the payment amount indicated by the payment information is less than a threshold.

[0148] In addition, even if the payment information indicates content other than the payment amount, the proposal relationship data indicates the relationship between the other content and information to be proposed to the user among the multiple pieces of information (at least one of the application information I20 and the other information I21). The selection unit 110 may select information associated with the other content indicated by the payment information based on the proposal relationship data.

[0149] The suggestion unit 104 of the 12th modification suggests the app information I20 when the selection unit 110 selects the app information I20. The suggestion unit 104 suggests the other information I21 when the selection unit 110 selects the other information I21. The selection unit 110 may select both the app information I20 and the other information I21, and in this case, the suggestion unit 104 may suggest both the app information I20 and the other information I21 to the user.

[0150] The payment system 1 of the twelfth modification selects information to be proposed to the user from among a plurality of pieces of information including the app information I20 and other information I21, based on the payment information. When the app information I20 is selected by the selection unit 110, the payment system 1 proposes the app information I20. This allows the payment system 1 to propose optimal information according to the payment information to the user. For example, the payment system 1 can propose the app information I20 to a user for whom a proposal for a certain app is valid. The payment system 1 can propose the other information I21 to a user for whom a proposal for information I21 other than the app information I20 is valid.

[0151] [6-13. Variation 13] For example, the app information acquisition unit 103 may determine the relevance between each of a plurality of pieces of app information I20 that are candidates for proposal to the user and the user based on the payment information, and acquire the app information I20 of an app with a relatively high relevance. The relevance is a degree of certainty that the user is estimated to be interested in the app information I20. In the thirteenth modification, it is assumed that relevance data indicating the relationship between the payment information and the app information I20 that is related to the user is stored in advance in the data storage unit. The relevance data may be in any format, such as a table format, a formula format, a part of a program code, or a machine learning model. The app information acquisition unit 103 acquires the app 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 etc., or the app information I20 of a specific app described in the embodiment etc. As another 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 of a specific app. The determination of relevance in Modification 13 includes these two patterns.

[0153] For example, when a change occurs in the application list L11, L120 and the payment amount of the user is equal to or greater than a threshold, both the application information I20 of the application list L120 (FIG. 7) and the application information I20 of the installment payment application (FIG. 2) may be displayed. In this case, the application information I20 according to the priority may be proposed based on a predetermined priority (for example, a priority such as giving priority to a judgment regarding a specific application). The specific application information I20 may be proposed to a user specified by the user's past operation history (for example, a user who viewed the application lists L11, L120, a user who selected "See all" in the application list L11). Furthermore, the relevance may be determined by combining with other information. For example, by combining information that the payment location is a beauty salon and that the user is a woman, the application information I20 of the installment payment application related to the payment amount and the application information I20 of the beauty application for women may be proposed.

[0154] In variant 13, an example is taken in which the payment information indicates three items, namely, the payment amount, the payment location, and the payment method. The details of these are as described in the embodiment, variant 4, and variant 5, respectively. The association data indicates an installment payment app as an app related to the payment amount being equal to or greater than a threshold. The association data indicates apps of nearby stores as an app related to the payment location being a specified location. The association data indicates a points management app as an app related to the payment method being points.

[0155] For example, the app information acquisition unit 103 identifies a relevant app from among multiple apps based on the three items indicated by the payment information and the association data. For example, the app information acquisition unit 103 identifies an installment payment app when the payment amount indicated by the payment information is equal to or greater than a threshold. The app information acquisition unit 103 identifies an app for a nearby store when the payment location indicated by the payment information is a specified location. The app information acquisition unit 103 identifies a points management app when the payment method indicated by the payment information is points. There may be cases where there is no relevant app, and in this case, the app information acquisition unit 103 may not identify any app.

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

[0157] For example, it is assumed that the predetermined selection condition is a condition related to a predetermined priority. Furthermore, it is assumed that the payment amount is set as the predetermined selection condition. In this case, the application information acquisition unit 103 determines the relevance of the application by giving priority to the payment amount. When the application information acquisition unit 103 determines that there is relevance based on the payment amount, it acquires the application information I20 of the installment payment application without determining the payment location and the payment method. When the application information acquisition unit 103 determines that there is no relevance based on the payment amount, it determines the relevance of the application based on the payment location. When the application information acquisition unit 103 determines that there is relevance based on the payment location, it acquires the application information I20 of the application of the nearby store without determining the payment method. When the application information acquisition unit 103 determines that there is no relevance based on the payment location, it determines the relevance of the application based on the payment method. In this way, the application information acquisition unit 103 may determine a plurality of items (in the above example, three items: the payment amount, the payment location, and the payment method) one after another based on the priority set as the selection condition.

[0158] For example, the predetermined selection condition is a condition related to past payment information. In this case, the app information acquisition unit 103 acquires information indicating each of past payment amounts, payment locations, and payment methods as past payment information to determine relevance. The information may indicate the frequency of each of the past payment amounts, payment locations, and payment methods. For example, when the app information acquisition unit 103 identifies that there are relatively many payments at a certain payment location during a certain period, it may identify an app related to the payment location as a relevant app and suggest the app information I20 of the app to the user.

[0159] For example, the predetermined selection condition is assumed to be information other than the payment information (for example, information on an operation on an app, user attribute information, or campaign information, etc.). If the other information indicates that the user has selected an installment payment app related to the payment amount many times, the app information acquisition unit 103 may identify the installment payment app related to the payment amount as a highly relevant app and acquire the app information I20 of the installment payment app. That is, the app information acquisition unit 103 may identify an app that has been selected relatively many times based on the other information and acquire the app information I20 of the app. For example, if the payment location of the current payment made by the user is a beauty salon and the user attribute information indicates a woman, the app information acquisition unit 103 may identify a beauty app targeted at women as a highly relevant app based on a combination of these pieces of information and acquire the app information I20 of the beauty app. For another example, if the payment method used by the user this time is a credit card, and a credit card campaign is being held in a certain app, the app information acquisition unit 103 may identify the app as a highly relevant app and acquire the app information I20 of the app. The information necessary for these processes is indicated in the relationship data.

[0160] The relevance may be expressed by a score. The relevance may be expressed by a numerical value, a character, or other symbols. For example, the application information acquisition unit 103 calculates a score indicating the level of relevance for each application by substituting the content indicated by the payment information into a predetermined formula. The application information acquisition unit 103 may acquire application information I20 having a relatively high score.

[0161] The suggestion unit 104 of the thirteenth modification proposes app information I20 of relatively highly relevant apps to the user on the user terminal 30. The suggestion unit 104 of the thirteenth modification may propose all or some of a plurality of relevant apps. In this case, the apps may be displayed in order of relevance. Although the app information I20 acquired by the app information acquisition unit 103 is different from that of the embodiment, the process of the suggestion unit 104 proposing the app information I20 may be the same as that of the embodiment.

[0162] The payment system 1 of the thirteenth modification determines the relevance between the user and each of a plurality of apps that are candidates for suggestion to the user based on the payment information, and acquires app information I20 of the app with a relatively high relevance. The payment system 1 proposes the app information I20 of the app with a relatively high relevance to the user via the user terminal 30. This allows the payment system 1 to propose the app information I20 of the app with a high relevance to the user, and therefore to propose the app information I20 that is more interesting to the user.

[0163] [6-14. Other Modifications] For example, the above modifications may be combined.

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

[0165] For example, the functions described as being realized by the payment server 10 may be realized by the related server 20, the user terminal 30, the store terminal 40, or another computer. The processes described as being realized by the payment server 10 may be shared among multiple computers.

[0166] [7. Notes] For example, the system can be configured as follows: (1) a payment information acquisition unit that acquires payment information related to a payment when a user who uses a payment service makes a payment using a user terminal; an application information acquiring unit that acquires application information related to an application of a related service related to the payment based on the payment information; a suggestion unit that proposes the application information to the user in the user terminal; Payment systems, including: (2) the suggestion unit suggests the app information to the user on a payment completion screen that is displayed on the user terminal when the payment is completed. (1) A payment system as described above. (3) The user executes the payment using a payment app installed on the user terminal, The suggestion unit suggests the app information for displaying an app list related to the list of apps to the user on the user terminal. A payment system according to (1) or (2). (4) The payment system further includes a usage status information acquisition unit that acquires usage status information regarding a usage status of at least one of the payment app and the app list by the user, The suggestion unit suggests the app information to the user on the user terminal based on the usage status information acquisition unit. (3) A payment system as described above. (5) The payment system further includes a change determination unit that determines whether a change has occurred in the list of applications, the suggestion unit, when the change determination unit determines that a change has occurred in the application list, suggests the application information to the user on the user terminal. A payment system according to (3) or (4). (6) The payment information acquisition unit acquires the payment information indicating a payment amount for the payment, The application information acquisition unit acquires the application information based on the payment amount indicated by the payment information. A payment system according to any one of (1) to (5). (7) The payment information acquisition unit acquires the payment information indicating a payment location for the payment, The application information acquisition unit acquires the application information based on the payment location indicated by the payment information. A payment system according to any one of (1) to (6). (8) The payment information acquisition unit acquires the payment information indicating a payment method used for the payment, The application information acquisition unit acquires the application information based on the payment method indicated by the payment information. A payment system according to any one of (1) to (7). (9) The payment information acquisition unit acquires the payment information indicating a payment frequency of the user who executed the payment, The application information acquisition unit acquires the application information based on the payment frequency indicated by the payment information. A payment system according to any one of (1) to (8). (10) The payment information acquisition unit acquires the payment information indicating the product or service that is the subject of the payment, The application information acquisition unit acquires the application information based on the product or the service indicated by the payment information. A payment system according to any one of (1) to (9). (11) The payment information acquisition unit acquires the payment information indicating a payment time when the payment was executed, The application information acquisition unit acquires the application information based on the payment time indicated by the payment information. A payment system according to any one of (1) to (10). (12) The payment system further includes an other service information acquisition unit that acquires other service information related to the user in other services different from the payment service, The application information acquisition unit acquires the application information further based on the other service information. A 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 related to attributes of the user, The application information acquisition unit acquires the application information further based on the user attribute information. A payment system according to any one of (1) to (12). (14) The payment system further includes an application operation information acquisition unit that acquires application operation information regarding an operation of the application by the user, The application information acquisition unit acquires the application information further based on the application operation information. A payment system according to any one of (1) to (13). (15) the suggestion unit is capable of suggesting 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 a plurality of pieces of information including the application information and the other information based on the payment information, the suggestion unit, when the application information is selected by the selection unit, suggests the application information. A payment system according to any one of (1) to (14). (16) The application information acquisition unit determines a relevance between the user and each of a plurality of application information that are candidates for proposal to the user, based on the payment information, and acquires the application information that has a relatively high relevance; The suggestion unit suggests the app information having a relatively high relevance to the user on the user terminal. A payment system according to any one of (1) to (15). (17) the payment information acquisition unit acquires the payment information when the user executes the payment using a payment application of the user terminal, the application information acquisition unit acquires the application information related to a mini application in the payment application, The suggestion unit suggests the app information to the user through the payment app of the user terminal. A payment system according to any one of (1) to (16). [Explanation of symbols]

[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 shooting 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 provision 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 payment information acquisition unit that acquires payment information regarding a payment when a user who uses a payment service makes a payment using a payment app installed on a user terminal; an application information acquiring unit that acquires application information for displaying an application list related to an application list of related services related to the payment based on the payment information; a suggestion unit that proposes the application information to the user in the user terminal; Payment systems including.

2. the application information acquisition unit acquires the application information selected by the user to display the application list; The payment system according to claim 1 .

3. The payment system further includes a usage status information acquisition unit that acquires usage status information regarding a usage status of at least one of the payment app and the app list by the user, The suggestion unit suggests the app information to the user on the user terminal based on the usage status information.

3. A payment system according to claim 1 or 2.

4. The payment system further includes a change determination unit that determines whether a change has occurred in the list of applications, the suggestion unit, when it is determined by the change determination unit that a change has occurred in the application list, suggests the application information to the user on the user terminal.

3. A payment system according to claim 1 or 2.

5. the suggestion unit suggests the app information to the user on a payment completion screen that is displayed on the user terminal when the payment is completed.

3. A payment system according to claim 1 or 2.

6. a payment information acquisition unit that acquires payment information indicating a payment amount when a user who uses a payment service makes a payment using a user terminal; an application information acquisition unit that acquires application information on an application of a related service related to the payment based on the payment amount indicated by the payment information; a suggestion unit that proposes the application information to the user in the user terminal; Payment systems including.

7. The payment information acquisition unit acquires the payment information indicating a payment location for the payment, The application information acquisition unit acquires the application information based on the payment location indicated by the payment information.

3. A payment system according to claim 1 or 2.

8. a payment information acquisition unit that acquires, when a user who uses a payment service makes a payment using a user terminal, payment information indicating a payment method used in the payment; an application information acquisition unit that acquires application information on an application of a related service related to the payment based on the payment method indicated by the payment information; a suggestion unit that proposes the application information to the user in the user terminal; Payment systems including.

9. a payment information acquisition unit that acquires, when a user who uses a payment service makes a payment using a user terminal, payment information indicating the payment frequency of the user who made the payment; an application information acquiring unit that acquires application information on an application of a related service related to the payment based on the payment frequency indicated by the payment information; a suggestion unit that proposes the application information to the user in the user terminal; Payment systems including.

10. a payment information acquisition unit that acquires payment information indicating a product or service that is the subject of the payment when a user who uses the payment service makes a payment using a user terminal; an application information acquisition unit that acquires application information on an application of a related service related to the payment based on the product or the service indicated by the payment information; a suggestion unit that proposes the application information to the user in the user terminal; Payment systems including.

11. a payment information acquisition unit that acquires, when a user who uses a payment service makes a payment using a user terminal, payment information indicating a time when the payment was made; an application information acquisition unit that acquires application information on an application of a related service related to the payment based on the payment time indicated by the payment information; a suggestion unit that proposes the application information to the user in the user terminal; Payment systems including.

12. The payment system further includes an other service information acquisition unit that acquires other service information related to the user in other services different from the payment service, The application information acquisition unit acquires the application information further based on the other service information.

3. A 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 related to attributes of the user, The application information acquisition unit acquires the application information further based on the user attribute information.

3. A payment system according to claim 1 or 2.

14. a payment information acquisition unit that acquires payment information related to a payment when a user who uses a payment service makes a payment using a user terminal; an application operation information acquisition unit that acquires application operation information regarding at least one of whether or not an application of a related service related to the payment has been started by the user and the number of times the application has been started, or application operation information regarding specific operation content in the application of the related service related to the payment by the user; an application information acquisition unit that acquires application information related to the application based on the payment information and the application operation information; a suggestion unit that proposes the application information to the user in the user terminal; Payment systems including.

15. a payment information acquisition unit that acquires payment information related to a payment when a user who uses a payment service makes a payment using a user terminal; an application information acquiring unit that acquires application information related to an application of a related service related to the payment based on the payment information; a suggestion unit that proposes the application information to the user in the user terminal; A payment system comprising: the suggestion unit is capable of suggesting 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 a plurality of pieces of information including the application information and the other information based on the payment information, the suggestion unit, when the application information is selected by the selection unit, suggests the application information. Payment system.

16. a payment information acquisition unit that acquires payment information related to a payment when a user who uses a payment service makes a payment using a user terminal; an app information acquisition unit that determines a relevance between the user and each of a plurality of app information items that are candidates for suggestion to the user, the app information items being related to apps of related services that are related to the payment, based on the payment information, and acquires the app information items that have a relatively high relevance; a suggestion unit that proposes, to the user, the app information having a relatively high relevance to the user in the user terminal; Payment systems including.

17. the payment information acquisition unit acquires the payment information when the user executes the payment using a payment application of the user terminal, the application information acquisition unit acquires the application information related to a mini application in the payment application, The suggestion unit suggests the app information to the user through the payment app of the user terminal.

3. A payment system according to claim 1 or 2.

18. A computer comprising: a payment information acquisition step of acquiring payment information regarding a payment when a user who uses a payment service makes a payment using a payment application installed in a user terminal; an application information acquiring step of acquiring application information for displaying an application list related to an application list of related services related to the payment based on the payment information; a proposing step of proposing the application information to the user at the user terminal; A proposed method for carrying out the above.

19. a payment information acquisition unit that acquires payment information regarding a payment when a user who uses a payment service makes a payment using a payment app installed on a user terminal; an application information acquiring unit that acquires application information for displaying an application list related to an application list of related services that are related to the payment based on the payment information; a suggestion unit that proposes the application information to the user in the user terminal; A program that makes a computer function as a

Images