Proposed system, proposed method, and program
The proposed system addresses the limitation of existing payment systems by acquiring and proposing second service information based on unsettled products or services, effectively supporting user payments and enhancing convenience.
Patent Information
- Application Number
- JP2024012743
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-01-31
- Publication Date
- 2025-04-16
- Estimated Expiration
- 2044-01-31
AI Technical Summary
Existing payment systems cannot support payments for unsettled products or services and do not make proposals based on a user's potential needs.
A proposed system that includes an unsettled product or service acquisition unit, a second service information acquisition unit, and a proposal unit to suggest second service information to users based on unsettled information.
Enables the system to make proposals according to a user's potential needs, supporting payments for unsettled products or services and enhancing user convenience.
Smart Images

Figure 0007663730000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a proposal system, a proposal 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, the technology of Patent Document 1 proposes the purchase of an investment product according to amount information based on the payment information of the payment actually made by the user, and therefore cannot encourage the payment of unsettled products or services that the user has not yet paid. This point is the same for other conventional technologies, and it is not possible to make suggestions according to the user's potential desires, such as the payment of unsettled products or services.
[0005] One of the objectives of the present disclosure is to make suggestions that meet the potential needs of users. [Means for solving the problem]
[0006] The proposal system of the present disclosure includes an unpaid information acquisition unit that acquires unpaid information regarding an unpaid product or unpaid service that has not been paid for by a user and is handled in a first service, a second service information acquisition unit that acquires second service information regarding a second service different from the first service based on the unpaid information, and a proposal unit that proposes the second service information to the user. Effect of the Invention
[0007] The present disclosure can make suggestions that meet the potential needs of users. [Brief description of the drawings]
[0008] [Figure 1] FIG. 2 is a diagram illustrating an example of a hardware configuration of a proposed 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 illustrating an example of functions realized in the proposed system. [Figure 4] FIG. 4 is a diagram illustrating an example of a first service database. [Diagram 5] FIG. 13 is a diagram illustrating an example of a payment service database. [Figure 6] FIG. 2 is a diagram illustrating an example of a process executed in the proposed system. [Figure 7] FIG. 2 is a diagram illustrating an example of a process executed in the proposed system. [Figure 8] FIG. 13 is a diagram illustrating an example of a function realized in a modified example. [Figure 9] FIG. 13 is a diagram showing an example of a payment completion screen in Modification 5. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] [1. Hardware configuration of the proposed system] An example of an embodiment of a proposed 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 the proposed system. For example, the proposed system 1 includes a first service server 10, a second service server 20, a payment server 30, a user terminal 40, and a store terminal 50. Each of the first service server 10, the second service server 20, the payment server 30, the user terminal 40, and the store terminal 50 is connected to a network N such as the Internet or a LAN.
[0010] The first service server 10 is a server computer for the first service. In this embodiment, the first service is an electronic commerce service as an example, but the first service is not limited to an electronic commerce service. The first service may be any service. For example, the first service may be an online flea market service, a travel reservation service, a communication service, a financial service, a video distribution service, a salon service such as a beauty salon, a restaurant reservation service, or other services. For example, a user operates a user terminal 40 to access the first service server 10 and use the first service. The first service is not limited to an online service. The first service may be an offline service.
[0011] For example, the first service server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The storage unit 12 includes at least one of a volatile memory such as a RAM and a non-volatile memory such as a flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.
[0012] The second service server 20 is a server computer for the second service. The second service is a service different from the first service. In this embodiment, a service provided by a card company that issues a credit card is taken as an example of the second service, but the second service may be an electronic commerce service different from the first service, an online flea market service, a travel reservation service, a communication service, a financial service, a video distribution service, a salon service such as a beauty salon, a restaurant reservation service, or other services. For example, a user operates a user terminal 40 to access the second service server 20 and use the second service. The second service is not limited to an online service. The second service may be an offline service.
[0013] For example, the second service 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 similar to those of the control unit 11, the storage unit 12, and the communication unit 13, respectively.
[0014] The payment server 30 is a server computer of the payment service. The payment service is a service that provides electronic payment (cashless payment) to users. The payment service is a service different from the first service and the second service. For example, the payment service can be linked with the first service and the second service. Linkage between services means that data can be sent and received. The operators of the payment service, the first service, and the second service may be the same or different from each other.
[0015] For example, the payment server 30 includes a control unit 31, a storage unit 32, and a communication unit 33. The hardware configurations of the control unit 31, the storage unit 32, and the communication unit 33 may be similar to those of the control unit 11, the storage unit 12, and the communication unit 13, respectively.
[0016] The user terminal 40 is a user's computer. For example, the user terminal 40 is a smartphone, a tablet, a personal computer, or a wearable terminal. The user terminal 40 includes a control unit 41, a memory unit 42, a communication unit 43, an operation unit 44, a display unit 45, and an imaging unit 46. The hardware configurations of the control unit 41, the memory unit 42, and the communication unit 43 may be similar to those of the control unit 31, the memory unit 32, and the communication unit 33, respectively. The operation unit 44 is an input device such as a touch panel or a mouse. The display unit 45 is a display such as a liquid crystal or organic EL. The imaging unit 46 includes at least one camera.
[0017] The store terminal 50 is a computer of a store affiliated with the payment service. For example, the store terminal 50 is a POS terminal, a handheld terminal, a smartphone, a tablet, or a personal computer. The store terminal 50 includes a control unit 51, a memory unit 52, a communication unit 53, an operation unit 54, a display unit 55, and a reading unit 56. The hardware configurations of the control unit 51, the memory unit 52, the communication unit 53, the operation unit 54, and the display unit 55 may be similar to those of the control unit 11, the memory unit 12, the communication unit 13, the operation unit 44, and the display unit 45, respectively. The reading unit 56 includes at least one code reader or reader / writer. The reading unit 56 may include at least one camera.
[0018] The programs stored in the storage units 12, 22, 32, 42, and 52 may be supplied to the first service server 10, the second service server 20, the payment server 30, the user terminal 40, or the store terminal 50 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 first service server 10, the second service server 20, the payment server 30, the user terminal 40, or the store terminal 50. For example, a program stored in an information storage medium may be supplied to the first service server 10, the second service server 20, the payment server 30, the user terminal 40, or the store terminal 50 via at least one of the reading unit and the input / output unit.
[0019] Furthermore, the proposed system 1 may include at least one computer. The computer included in the proposed system 1 is not limited to the example of FIG. 1. For example, the proposed system 1 may include only the payment server 30 and the user terminal 40. In this case, the first service server 10, the second service server 20, and the store terminal 50 exist outside the proposed system 1. The proposed system 1 may include only the payment server 30. In this case, the first service server 10, the second service server 20, the user terminal 40, and the store terminal 50 exist outside the proposed system 1. For example, the proposed system 1 may include the payment server 30 and other computers not shown in FIG. 1.
[0020] [2. Overview of the proposed system] In this embodiment, the user operates the user terminal 40 to use the first service, the second service, and the payment service. For example, a first app which is an application for the first service, a second app which is an application for the second service, and a payment app which is an application for the payment service are each installed in the user terminal 40. The user can use each of the first service, the second service, and the payment service from these apps. When the user performs an operation to start the user terminal 40, the user terminal 40 displays a menu screen showing these apps on the display unit 45.
[0021] FIG. 2 is a diagram showing an example of a screen displayed on the user terminal 40. For example, the menu screen SC1 includes a first application icon I10, a second application icon I11, and a payment application icon I12. When the user selects the icon I10, the user terminal 40 launches the first application. As shown in the upper right of FIG. 2, the user terminal 40 displays a first service screen SC2, which corresponds to the top page (first view) of the first service, on the display unit 45. The user can use the first service from the first service screen SC2. In this embodiment, the user can use an electronic commerce service, which is an example of the first service, from the first service screen SC2.
[0022] For example, a user can input any search criteria on the first service screen SC2 to search for products or services handled by the e-commerce service. When a user views a product or service screen, the first service server 10 updates browsing history information indicating the user's browsing history. When a user registers a product or service as a favorite, the first service server 10 updates favorite information indicating the user's favorite products. When a user adds a product or service to a shopping cart, the first service server 10 updates shopping cart information indicating the user's shopping cart. This series of processes may be similar to processes adopted in known e-commerce services. The process for a user to purchase a product or service may also be similar to known processes.
[0023] For example, when the user selects the icon I11, the user terminal 40 launches the second application. The user terminal 40 accesses the second service server 20. Although the screen of the second service is omitted in FIG. 2, the screen of the second service may be similar to a known screen. The process when the user uses the second service from the screen of the second service may also be similar to the process adopted in the known second service. In this embodiment, the service provided by the card company corresponds to the second service, so the user can view the card statement, apply for installment payments, apply for bonus payments, or apply for cash advances. The process for these applications may also be similar to the process adopted in the known second service.
[0024] For example, when the user selects the icon I12, the user terminal 40 launches a payment application. As shown in the lower left of FIG. 2, the user terminal 40 displays a payment service screen SC3, which corresponds to the top page of the payment service, on the display unit 45. The user can use the payment service from the payment service screen SC3. The user can use any payment means in the payment service. The payment means is a means used by the user for payment. For example, the 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. A code such as a barcode or a two-dimensional code is also a means for payment, and therefore corresponds to a payment means. The payment means can also be called a payment means.
[0025] For example, when the payment app is launched, the user terminal 40 causes the display unit 45 to display a payment service screen SC3 including a code C30 generated based on a code ID that can temporarily identify the user. The code C30 is at least one of a barcode and a two-dimensional code. When the code C30 is read by the reading unit 56 of the store terminal 50, the payment is executed based on the code ID acquired from the code C30. In the example of FIG. 2, a credit card is set as the payment source, so the payment is executed based on the credit card. The process for the payment may be a known process.
[0026] The payment is not limited to the type in which the store terminal 50 reads the code C30 displayed on the user terminal 40. The payment may be of any type. For example, the payment may be of the type in which the user terminal 40 reads a code displayed on the store terminal 50, the type in which the user terminal 40 reads a code posted in the store, the type in which the payment is completed only by operating the user terminal 40, the type in which an IC chip in the user terminal 40 is used, or any other type. When the payment is completed, as shown in the lower right of FIG. 2, the user terminal 40 displays a payment completion screen SC4 on the display unit 45, indicating that the payment has been completed.
[0027] In this embodiment, when there is a product or service (hereinafter referred to as an unpaid product) or service (hereinafter referred to as an unpaid service) that the user is interested in but has not paid for among the products or services handled in the first service, second service information I40 regarding the second service is proposed on the payment completion screen SC4 to support the user's payment. In the example of FIG. 2, the second service information I40 indicates an installment payment app for supporting the purchase of the product or service. The installment payment app is an application provided by the card company of the credit card used for payment.
[0028] The installment payment app may be the same as the second app launched by selecting the icon I11, or may be a mini app within the second app, which is a super app. In this embodiment, however, the installment payment app is taken as an example to be a mini app within the payment app, which is a super 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. 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 second service server 20 via the payment app. Furthermore, the mini app may also include an app that transitions to a website screen display, etc. via the payment app.
[0029] For example, the payment service screen SC3 includes an app list L31 that shows a list of mini apps. The user can select any mini app from the app list L31. An installment payment app suggested by the second service information I40 is also displayed in the app list L31. When the user selects "View all," the user terminal 40 displays mini apps that cannot be displayed in the app list L31. The app list L31 may also display mini apps for services other than the first service and the second service. A link such as that in the app list L31 may correspond to a mini app.
[0030] Furthermore, an integrated application that integrates the first application, the second application, and the payment application may be installed in the user terminal 30. Of the integrated application, a portion for providing a first service to the user may correspond to the first application, a portion for providing a second service to the user may correspond to the second application, and a portion for providing a payment service to the user may correspond to the payment application. For example, a smartphone application is often not one program but a collection of many small programs (for example, programs corresponding to subroutines called from a main routine). The concept of including many programs is the integrated application, and the small programs within the integrated application may correspond to the first application, the second application, and the payment application.
[0031] For example, if the user is not aware of the app list L31, he / she may not be aware of the existence of the installment payment app. In this case, the user can be made aware of the existence of the installment payment app by the second service information I40. For example, if the user is unsure whether to purchase a high-priced unpaid product or service with the first service, the user can recognize that the burden of payment can be reduced by using the installment payment app. In other words, the proposal system 1 can support the user in purchasing the unpaid product or service by proposing the installment payment app indicated by the second service information I40.
[0032] As described above, the proposal system 1 of this embodiment displays the second service information I40 on the payment completion screen SC4 in order to support the user in purchasing the unpaid product or service when there is an unpaid product or service in the first service. This allows the proposal system 1 to make suggestions according to the user's potential needs. Suggestions according to potential needs may also be made for purposes other than supporting the purchase of the unpaid product or service. Details of the proposal system 1 will be described below.
[0033] [3. Functions realized by the proposed system] Fig. 3 is a diagram showing an example of functions realized by the proposed system 1. Each unit realized by the proposed system 1 can be configured by consolidating it into one device, or by distributing the devices into smaller units.
[0034] [3-1. Functions realized by the first service server] For example, the first service server 10 includes a data storage unit 100 and a first service providing unit 101. The data storage unit 100 is realized by the storage unit 12. The first service providing unit 101 is realized by the control unit 11.
[0035] [Data storage section] The data storage unit 100 stores data necessary for the first service. For example, the data storage unit 100 stores a first service database DB1.
[0036] FIG. 4 is a diagram showing an example of the first service database DB1. The first service database DB1 is a database in which various information related to the user in the first service is stored. For example, the first service database DB1 stores a user ID, a password, browsing history information, favorite information, and shopping cart information. The first service database DB1 may store other data. For example, the first service database DB1 may store at least one of wish list information indicating a wish list in which products or services the user wants are registered, purchase history information indicating products or services purchased by the user in the first service, and payment method information related to payment methods that the user can use in the first service.
[0037] The user ID of the first service is an example of user identification information that can identify a user in the first service. 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 user ID of the first service may be the same as at least one of the user ID of the second service and the user ID of the payment service, or may be different from each other. When the user IDs are different from each other, the association of the user IDs is assumed to be managed by the proposed system 1. For example, at least one of the first service server 10, the second service server 20, and the payment server 30 manages the association. The association makes it possible to identify which user ID corresponds to which user.
[0038] The browsing history information indicates the store ID of a store that handles a product or service viewed by the user, an ID that can identify the product or service, and the viewing date and time. The favorite information indicates the store ID of a store that handles a product or service that the user has registered in his or her favorites, an ID that can identify the product or service, and the registration date and time. The shopping cart information indicates the store ID of a store that handles a product or service that the user has registered in his or her shopping cart, an ID that can identify the product or service, the quantity of the product or service, and the registration date and time. The browsing history information, favorite information, and shopping cart information may be in any format adopted by known e-commerce services.
[0039] The data stored in the data storage unit 100 is not limited to the above example. The data storage unit 100 may store data necessary for the first service. For example, the data storage unit 100 may store a database in which various information related to the product or service handled in the first service (for example, a store ID of a store that handles the product or service, an ID for identifying the product or service, a description of the product or service, an image of the product or service, a price of the product or service, an inventory of the product or service, or other information) is stored. The data storage unit 100 may store data of various screens displayed on the first app.
[0040] [First Service Provision Department] The first service providing unit 101 provides the first service to the user based on the data stored in the data storage unit 100. In this embodiment, since the electronic commerce service corresponds to the first service, the first service providing unit 101 provides various services for the user to perform electronic commerce. In the example of FIG. 2, the first service providing unit 101 displays the first service screen SC2 on the user terminal 40, and performs a process such as searching for a product, viewing a product, registering a product in a favorites list, registering a product in a shopping cart, or other processes. These processes may be similar to processes adopted in a known electronic commerce service. Similarly, when the first service is a service other than an electronic commerce service, the process executed by the first service providing unit 101 may be similar to processes adopted in the other known services.
[0041] [3-2. Functions realized by the second service server] For example, the second service server 20 includes a data storage unit 200 and a second service providing unit 201. The data storage unit 200 is realized by the storage unit 22. The second service providing unit 201 is realized by the control unit 21.
[0042] [Data storage section] The data storage unit 200 stores data necessary for the second service. For example, the data storage unit 200 stores a database in which various information related to the user in the second service is stored. In this embodiment, the service provided by the card company that issued the credit card corresponds to the second 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 corresponding to the second service.
[0043] [Second Service Department] The second service providing unit 201 provides the second service to the user based on the data stored in the data storage unit 200. In this embodiment, the service provided by the card company that issued the credit card corresponds to the second service, so the second 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 to a lump sum payment, a revolving payment, a bonus payment, or an installment payment. For example, the second service providing unit 201 displays a screen for the second service on the user terminal 40 and accepts an application for installment payment from the user. The process for accepting an application for installment payment may be a known process.
[0044] [3-3. Functions realized by the payment server] For example, the payment server 30 includes a data storage unit 300, a payment execution unit 301, a payment determination unit 302, an outstanding information acquisition unit 303, a second service information acquisition unit 304, and a proposal unit 305. The data storage unit 300 is realized by the memory unit 32. Each of the payment execution unit 301, the payment determination unit 302, the outstanding information acquisition unit 303, the second service information acquisition unit 304, and the proposal unit 305 is realized by the control unit 31.
[0045] [Data storage section] The data storage unit 300 stores data necessary for the payment service. For example, the data storage unit 300 stores a payment service database DB2.
[0046] FIG. 5 is a diagram showing an example of the payment service database DB2. The payment service database DB2 is a database in which various information related to a user is stored. For example, the payment service database DB2 stores a user ID, a password, a code ID, payment method information, and payment history information. The payment service database DB2 may store other data. For example, the payment service database DB2 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. The payment service database DB2 may store information such as browsing history information, favorite information, and shopping cart information acquired from the first service server 10.
[0047] The user ID of the payment service is an example of user identification information that can identify the user in the payment service. 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 the user in the payment service. The code ID is updated every time the code C30 is displayed.
[0048] Payment method information is information that enables a user to identify payment methods that can be used in 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 301 described below updates the payment history information to indicate the details of the payment.
[0049] The data stored in the data storage unit 300 is not limited to the above example. The data storage unit 300 may store any data necessary for the payment service. For example, the data storage unit 300 may store data of various screens displayed on the payment application.
[0050] [Payment Execution Department] The payment execution unit 301 executes the payment in the payment service. The process for the payment may be a known process. In the case of a type of payment in which the code C30 displayed on the user terminal 40 is read by the store terminal 50 as in this embodiment, the payment execution unit 301 executes the payment based on the payment request received from the store terminal 50. The payment execution unit 301 refers to the payment service database DB2 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 50. For example, if the user has set a credit card as the payment source, the payment execution unit 301 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.
[0051] The process executed by the payment execution unit 301 is not limited to the above example. In the case of a type where a code displayed on the store terminal 50 is read by the user terminal 40, a type where a code posted in a store is read by the user terminal 40, a type where the payment is completed only by operating the user terminal 40 (e.g., ID payment or account payment), a type where an IC chip in the user terminal 40 is used, carrier payment which is payment by a carrier used by the user terminal 40, or other types of payment, the payment execution unit 301 may acquire information necessary for the payment and execute the payment by communicating with at least one of the user terminal 40 and the store terminal 50. When the payment execution unit 301 executes the payment, it updates the user's payment history information to indicate the content of the executed payment.
[0052] [Payment Judgment Department] The payment determination unit 302 determines whether or not the user has made a payment for a product other than the unpaid product or a service other than the unpaid service, in a payment service different from the first service and the second service. The payment determination unit 302 determines whether or not the user has made a payment, based on the processing result of the payment execution unit 301. That is, the payment determination unit 302 determines whether or not the payment processing by the payment execution unit 301 has been completed. The payment determination unit 302 determines whether or not the processing indicated in the program executed by the payment execution unit 301 for payment has been completed. The product or service that is the subject of payment in the payment service may happen to be the same as the unpaid product or unpaid service, but is basically different from the unpaid product or unpaid service.
[0053] In this embodiment, the payment request does not include information (e.g., JAN code) that can identify the product or service that is the subject of the payment. Therefore, the payment determination unit 302 does not determine whether the product that is the subject of the payment is different from the unpaid product, or whether the service that is the subject of the payment is different from the unpaid service. The payment determination unit 302 determines whether a payment has been made by a user who has an unpaid product or service, without specifying what the product or service that is the subject of the payment is specifically.
[0054] The payment request may include information that can identify the product or service that is the subject of the payment. In this case, the payment determination unit 302 may specify what the product or service that is the subject of the payment is specifically. The payment determination unit 302 may determine the above information included in the payment request and whether the product that is the subject of the payment is different from the unpaid product, or whether the service that is the subject of the payment is different from the unpaid service.
[0055] [Unpaid Information Acquisition Department] The unpaid information acquisition unit 303 acquires unpaid information related to unpaid products or services that are not paid for by the user and are handled by the first service. The unpaid products or services can also be called unpurchased products or services that are not purchased by the user. The unpaid products or services may be any product or service. Products that do not have a physical presence, such as travel products or content, may correspond to unpaid products. The unpaid services may be services that can be applied for (reserved) online, or services that the user applies for by visiting the site.
[0056] In this embodiment, an e-commerce service will be described as an example of the first service, so the unpaid information acquisition unit 303 acquires unpaid information of an unpaid product or service that the user is considering purchasing in the e-commerce service. The unpaid product or service that the user is considering purchasing is an unpaid product or service that the user has viewed, or an unpaid product or service that the user has performed an operation to register for the first service. For example, the unpaid information acquisition unit 303 acquires the user's unpaid information from the first service server 10.
[0057] For example, if the user ID is the same for the first service and the payment service, the outstanding information acquisition unit 303 transmits the user ID of the user for which outstanding information is to be acquired to the first service server 10, and requests the outstanding information. The first service server 10 refers to the first service database DB1, and transmits the outstanding information of the user indicated by the user ID to the payment server 30. The outstanding information acquisition unit 303 acquires the outstanding information transmitted by the first service server 10. If the user ID is different for the first service and the payment service, the association of the user IDs is managed in at least one of the first service and the payment service. Based on the association, at least one of the first service and the payment service may specify which user's outstanding information should be acquired or transmitted.
[0058] The unpaid information does not have to be information that can identify the specific unpaid product or unpaid service. The unpaid information may be any information related to the unpaid product or unpaid service. In this embodiment, an example is given in which the unpaid information is information indicating the presence or absence of an unpaid product or unpaid service. For example, the unpaid information is a first value indicating the presence of an unpaid product or unpaid service, or a second value indicating the absence of an unpaid product or unpaid service. The unpaid information may be stored in the data storage unit 100 of the first service server 10, or may be generated by the first service server 10.
[0059] The unpaid information may indicate other information related to the unpaid product or the unpaid service. For example, the unpaid information may be the price of the unpaid product or the unpaid service, the price range of the unpaid product or the unpaid service, the number of the unpaid product or the unpaid service, the general category of the unpaid product or the unpaid service, information that can identify what the unpaid product or the unpaid service is specifically, the total amount of the unpaid product or the unpaid service, the inventory of the unpaid product or the unpaid service, the elapsed time since the user considered the unpaid product or the unpaid service (for example, the elapsed time since the user viewed it, the elapsed time since it was registered as a favorite, or the elapsed time since it was registered in the shopping cart), or the store that handles the unpaid product or the unpaid service.
[0060] Also, the unpaid information acquisition unit 303 may acquire the unpaid information from the first service server 10 without making a request for the unpaid information to the first service server 10. For example, when there is an unpaid product in the first service that has not been paid for by the user, the first service server 10 may transmit the unpaid information to the payment server 30. In this case, the unpaid information acquisition unit 303 acquires the unpaid information from the first service server 10 without making a request for the unpaid information. When a product has been in an unpaid state for a predetermined period of time, the first service server 10 may transmit the unpaid information to the payment server 30. The first service server 10 transmits, together with the unpaid information, information (e.g., a user ID) capable of identifying which user the unpaid information belongs to to the payment server 30.
[0061] In this embodiment, the unpaid information acquisition unit 303 acquires the unpaid information when the payment determination unit 302 determines that the user has made a payment. The unpaid information acquisition unit 303 does not acquire the unpaid information when the payment determination unit 302 does not determine that the user has made a payment.
[0062] For example, when the payment determination unit 302 determines that the user has made a payment, the unpaid information acquisition unit 303 requests unpaid information from the first service server 10. The user ID of the user who made the payment is included in the request for unpaid information. The first service server 10 refers to the first service database DB1 and at least one of the browsing history information, favorite information, and shopping cart information associated with the user ID, and determines whether there is an unpaid product or an unpaid service. When the user IDs for the first service and the payment service are different, the association of the user IDs can be referenced as described above.
[0063] For example, when the first service server 10 determines that there is an unpaid product or an unpaid service in the at least one of the items, it generates unpaid information indicating that there is an unpaid product or an unpaid service and transmits it to the payment server 30. When the first service server 10 determines that there is no unpaid product or an unpaid service in the at least one of the items, it generates unpaid information indicating that there is no unpaid product or an unpaid service and transmits it to the payment server 30. The unpaid information acquisition unit 303 acquires the unpaid information generated and transmitted by the first service server 10. Even when the unpaid information indicates information other than the presence or absence of an unpaid product or an unpaid service, the unpaid information acquisition unit 303 may acquire the unpaid information in a similar manner. When the unpaid information itself is stored in the first service database DB1, the first service server 10 does not need to generate the unpaid information on the spot.
[0064] [Second Service Information Acquisition Department] The second service information acquisition unit 304 acquires second service information I40 related to a second service different from the first service based on unpaid payment information. In this embodiment, the second service information acquisition unit 304 acquires second service information I40 related to a second app for the user to use the second service. That is, the second service app is a mini app, but the second service app may be a normal app that is not 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 menu screen SC1 of the OS of the user terminal 40 corresponds to a normal app. The second service app is an app distributed by a business operator that provides the second service to the user.
[0065] The second service information I40 may mean data related to the second service, but in this embodiment, it means an object (e.g., an image or text) visually displayed on the payment completion screen SC4. The actual data for displaying the second service information I40 is stored in advance in the data storage unit 300. The second service information acquisition unit 304 acquires the second service information I40 by acquiring the actual data. The actual data for displaying the second service information I40 may not be stored in advance in the data storage unit 300, but may be dynamically generated on the spot. In this case, the data that is the source of the second service information I40 is stored in the data storage unit 300. The second service information acquisition unit 304 may generate the second service information I40 based on the original data.
[0066] In this embodiment, a payment for a product different from the unpaid product or a service different from the unpaid service is basically performed in the payment service. Therefore, the second service information acquisition unit 304 acquires the second service information I40 when it is determined that the user has made a payment for the different product or the different service. The second service information acquisition unit 304 does not acquire the second service information I40 when it is not determined that the user has made a payment for the different product or the different service.
[0067] For example, the second service information acquisition unit 304 acquires second service information I40 of a second service that supports the payment of unpaid products or unpaid services. Supporting a payment means reducing the amount of a single payment, delaying the time of payment by deferred payment, reducing the total amount of payment by using a coupon, or a combination of these. In this embodiment, the service provided by the card company that issued the credit card set by the user as the payment source corresponds to the second service, so the second service information acquisition unit 304 acquires second service information I40 of an installment payment app provided by the card company.
[0068] The second service information acquisition unit 304 may acquire the second service information I40 of other apps other than the installment payment app. For example, the other apps may be a second app launched by selecting the icon I11, a point management app for the user to manage his / her own points, an advertising app for the user to earn points by viewing an advertisement, an app for the user to photograph and upload a receipt, or a coupon app for the user to earn a coupon. These other apps may be mini apps. Actual data for displaying the second service information I40 of these other apps may be stored in advance in the data storage unit 300.
[0069] [Proposal Department] The suggestion unit 305 suggests the second service information I40 to the user. In this embodiment, the suggestion unit 305 suggests the second service information I40 to the user in a payment app of the user terminal 40. Proposing the second service information I40 to the user means transmitting data for displaying the second service information I40 to the user terminal 40 or another computer. In this embodiment, the suggestion unit 305 suggests the second service information I40 to the user on a payment completion screen SC4 indicating that the payment has been completed. The payment completion screen SC4 is a screen indicating that the payment has been completed.
[0070] For example, the payment completion screen SC4 displays a message indicating that the payment has been completed, the payment location, the payment date and time, the payment amount, the payment target, or a combination of these. In this embodiment, the case where the suggestion unit 305 displays the payment completion screen SC4 itself is taken as an example, but the payment completion screen SC4 may be displayed by a function other than the suggestion unit 305. Regardless of the form of the suggestion of the second service information I40, the suggestion unit 305 may suggest the second service information I40 to the user on the payment completion screen SC4 by displaying the second service information I40 as a pop-up on the payment completion screen SC4 or a new screen superimposed on the payment completion screen SC4.
[0071] For example, when the payment is completed and the second service information acquisition unit 304 acquires the second service information I40, the suggestion unit 305 generates display data of a payment completion screen SC4 including the second service information I40. The display data is data for displaying some kind of screen on the user terminal 40. 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 305 suggests the second service information I40 to the user by transmitting display data of the payment completion screen SC4 including the second service information I40 to the user terminal 40.
[0072] In this embodiment, when the payment determination unit 302 determines that the user has made a payment, the suggestion unit 305 proposes to the user second service information I40 indicating an installment payment app. That is, the suggestion unit 305 proposes to the user second service information I40 indicating an installment payment app on the condition (trigger) that the payment determination unit 302 determines that the user has made a payment. When the payment determination unit 302 does not determine that the user has made a payment, the suggestion unit 305 may propose other information, such as advertisements for other services, to the user.
[0073] The method of proposing the second service information I40 is not limited to the above example. The suggestion unit 305 may suggest the second service information I40 to the user by transmitting data for displaying the second service information I40 to the user terminal 40 or another computer. For example, the suggestion unit 305 may suggest the second service information I40 to the user by displaying the second service information I40 on a screen other than the payment completion screen SC4 among the screens displayed on the payment app. For example, the suggestion unit 305 may suggest the second service information I40 to the user on a screen before payment. Furthermore, the suggestion unit 305 may suggest to the user benefit information related to the first service on a screen before payment. The suggestion unit 305 can suggest information that can be proposed based on unpaid information on any screen. The suggestion unit 305 may suggest the second service information I40 to the user using means other than the payment app. The other means may be email, SMS, push notification, banner notification, or other means.
[0074] Furthermore, when proposing the second service information I40 to the user, the suggestion unit 305 may propose the second service information I40 in association with information on an unpaid product or an unpaid service. The information on the unpaid product or the unpaid service is the name, image, price, store, or a combination of these. The information on the unpaid product or the unpaid service may be included in the unpaid information, or may be separate data from the unpaid information and obtained by the payment server 30 from the first service server 10. The information on the unpaid product or the unpaid service may simply be information indicating whether or not there is an unpaid product or an unpaid service.
[0075] For example, the suggestion unit 305 may suggest the second service information I40 in association with a specific name of an unpaid product or an unpaid service, or may suggest only that there is an unpaid product or an unpaid service together with the second service information I40. Information on the unpaid product or the unpaid service may be included in the second service information I40. For example, the suggestion unit 305 may suggest the second service information I40 indicating a message such as "Why not try using installment payments for the product you are looking for in the first service?". By doing so, the suggestion system 1 can more clearly convey to the user the purpose of suggesting the second service compared to a case in which only the second service is suggested alone. For another example, the suggestion unit 305 may suggest benefit information related to a benefit related to the first service in addition to the second service information I40. The benefit proposed by the suggestion unit 305 may be a coupon, points, or other benefit available in the first service. The suggestion unit 305 may suggest the second service information I40 indicating a message such as "Why not try using a coupon for the product you are looking for in the first service?".
[0076] The suggestion unit 305 may determine whether the unpaid product or unpaid service indicated by the unpaid information satisfies a predetermined condition, and may suggest the second service information I40 to the user based on the result of the determination. The predetermined condition is a condition that serves as a criterion for whether the suggestion unit 305 should suggest the second service information I40. Data indicating the predetermined condition is assumed to be stored in the data storage unit 300. For example, the predetermined condition may be the price of the unpaid product or unpaid service, a store that handles it, or other conditions.
[0077] [3-4. Functions realized on user terminals] For example, the user terminal 40 includes a data storage unit 400, an operation reception unit 401, and a display control unit 402. The data storage unit 400 is realized by the storage unit 42. The operation reception unit 401 and the display control unit 402 are realized by the control unit 41.
[0078] [Data storage section] The data storage unit 400 stores data necessary for the user to use a payment service. For example, the data storage unit 400 stores a payment application. When the user uses the payment service from a browser instead of the payment application, the data storage unit 400 stores the browser.
[0079] [Operation reception section] The operation acceptance unit 401 accepts various operations by the user. For example, the operation acceptance unit 401 accepts an operation for a payment application. The operation acceptance unit 401 transmits data indicating the content of the user's operation to the payment server 30.
[0080] [Display control section] The display control unit 402 displays various screens on the display unit 45. For example, the display control unit 402 displays a menu screen SC1, a first service screen SC2, a payment service screen SC3, and a payment completion screen SC4 on the display unit 45. The display control unit 402 may communicate with the first service server 10, the payment server 30, or another computer, receive data necessary to display these screens, and display these screens on the display unit 45.
[0081] [3-5. Functions realized by store terminals] For example, the store terminal 50 includes a data storage unit 500 and a payment execution unit 501. The data storage unit 500 is realized by the storage unit 52. The payment execution unit 501 is realized by the control unit 51.
[0082] [Data storage section] The data storage unit 500 stores data necessary for providing a payment service to a user. For example, the data storage unit 500 stores a database in which various information such as prices of products or services handled by a store is stored. The data storage unit 500 also stores information on products or services for which a user is to make a payment. The data storage unit 500 may store information on the location where the store terminal 50 is located.
[0083] [Payment Execution Department] The payment execution unit 501 provides a payment service to the user. For example, when the store terminal 50 reads the code C30 with the reading unit 56, the payment execution unit 501 acquires a code ID from the code C30. The payment execution unit 501 acquires a payment amount based on the result of reading the barcode of the product or the like. The payment execution unit 501 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 30. The payment request may be any request used in a known payment service. The payment execution unit 501 acquires a result of the execution of the payment from the payment server 30 and completes the payment at the store. This series of processes may also be any process used in a known payment service.
[0084] [4. Processing performed by the proposed system] Figures 6 and 7 are diagrams showing an example of processing executed in the proposed system 1. The processing in Figures 6 and 7 is executed by the control units 11, 21, 31, 41, and 51 executing programs stored in the storage units 12, 22, 32, 42, and 52, respectively. When the processing in Figures 6 and 7 is executed, it is assumed that the first application, the second application, and the payment application are each installed in the user terminal 40. Furthermore, it is assumed that the user has completed registration for use of each of the first service, the second service, and the payment service.
[0085] 6, when the user performs an operation to start up the user terminal 40, the user terminal 40 displays a menu screen SC1 on the display unit 45 (S1). The user terminal 40 identifies the user's operation based on a detection signal from the operation unit 44 (S2). Here, a case where the user selects either icon I10 or I12 is taken as an example. If the user performs another operation, such as selecting icon I11, a process corresponding to the other operation is executed, and this process ends.
[0086] In S2, when the user selects the icon I10 for launching the first application (S2: first application), the user terminal 40 launches the first application and executes processing for providing the first service to the user with the first service server 10 (S3). In S3, the first service server 10 may update at least one of the browsing history information, the favorite information, and the shopping cart information stored in the first service database DB1.
[0087] In S2, when the user selects the icon I12 for launching the payment app (S2: payment app), the user terminal 40 launches the payment app and executes processing with the payment server 30 to display the payment service screen SC3 (S4). In S4, the payment server 30 logs the user into the payment service, generates a code ID, and transmits display data of the payment service screen SC3 to the user terminal 40. The user causes the store terminal 50 to read the code C30. When the store terminal 50 reads the code C30 with the reading unit 56 (S5), it extracts the code ID from the code C30 and transmits a payment request to the payment server 30 (S6). When the payment server 30 receives the payment request (S7), it executes the payment based on the payment request (S8).
[0088] The payment server 30 judges whether the payment is completed based on the processing result of S8 (S9). That is, in S9, the payment server 30 judges whether the user has performed the payment. If it is not judged that the payment is completed (S9: N), the process returns to S9. If it is judged that the payment is completed in S9 (S9: Y), the payment server 30 executes a process to obtain unpaid information from the first service server 10 (S10). The payment server 30 judges whether the unpaid information indicates that there is an unpaid product or an unpaid service (S11). If it is judged that the unpaid information does not indicate that there is an unpaid product or an unpaid service in S11 (S11: N), this process ends. In this case, a payment completion screen SC4 that does not include the second service information I40 is displayed on the user terminal 40.
[0089] In S11, if it is determined that the unpaid information indicates that there is an unpaid product or service (S11: Y), the process moves to FIG. 7, where the payment server 30 acquires the second service information I40 of the installment payment app (S12). The payment server 30 executes a process with the user terminal 40 to propose the second service information I40 of the installment payment app on the payment completion screen SC4 (S13). In S13, the payment server 30 generates display data for the payment completion screen SC4 including the second service information I40 of the installment payment app and transmits it to the user terminal 40. The user terminal 40 displays the payment completion screen SC4 as shown in the lower right of FIG. 2 on the display unit 45.
[0090] The user terminal 40 judges whether or not the user has selected the second service information I40 (S14). If it is judged in S14 that the user has not selected the second service information I40 (S14:N), this process ends. If it is judged in S14 that the user has selected the second service information I40 (S14:Y), the user terminal 40 executes a process for providing the second service to the user with the second service server 20 (S15), and this process ends.
[0091] [5. Summary of the embodiment] The proposal system 1 of this embodiment acquires the second service information I40 based on the unpaid information. The proposal system 1 proposes the second service information I40 to the user. The unpaid information reflects the user's potential desire to purchase an unpaid product or service, so the proposal system 1 can make a proposal based on such unpaid information to meet the user's potential desire. The second service information I40 allows the user to know the existence of a second service that will fulfill the user's potential desire, so the proposal system 1 can improve the user's convenience. By proposing the second service information I40, the proposal system 1 can motivate the user to use the second service, so the use of the second service can be promoted.
[0092] In addition, the proposal system 1 determines whether the user has made a payment for a product different from the unpaid product or a service different from the unpaid service in the payment service. When it is determined that the user has made a payment for the different product or the different service, the proposal system 1 acquires the second service information I40. In this way, when the user makes a payment unrelated to the unpaid product or the unpaid service, the proposal system 1 can make a proposal according to the user's potential desire. For example, the proposal system 1 can propose the second service information I40 at a timing when the payment for the different product or the different service is made in the payment service and the user's consciousness is directed toward a purchase. In other words, the proposal system 1 can propose the second service information I40 at a more effective timing, thereby enhancing the appeal effect of the second service.
[0093] In addition, the proposal system 1 proposes the second service information I40 to the user on the payment completion screen SC4 indicating that the payment has been completed. This allows the proposal system 1 to propose the second service information I40 to the user more effectively by proposing the second service information I40 on the payment completion screen SC4 which is likely to attract the user's attention.
[0094] In addition, the proposed system 1 acquires unpaid information on unpaid products or services that the user is considering purchasing in an e-commerce service, which is an example of the first service. This allows the proposed system 1 to make proposals in response to the user's potential needs in the e-commerce service.
[0095] In addition, the proposed system 1 acquires the second service information I40 of the installment payment app. This allows the proposed system 1 to promote the use of the installment payment app by users. For example, even if a user is hesitant to purchase an expensive unpaid product or service, by learning about the existence of the installment payment app, the user can positively consider purchasing the unpaid product or service.
[0096] In addition, the proposed system 1 acquires second service information I40 of a second service that supports the payment of an unpaid product or service. This allows the proposed system 1 to support the user in paying for the unpaid product or service. For example, even if a user is hesitant to purchase an expensive unpaid product or service, by learning of the existence of a second service that supports payment, the user can positively consider purchasing the unpaid product or service.
[0097] [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.
[0098] 8 is a diagram showing an example of functions realized in the modified example. For example, the payment server 30 further includes a user location information acquisition unit 306, a campaign information acquisition unit 307, and a payment information acquisition unit 308. Each of the user location information acquisition unit 306, the campaign information acquisition unit 307, and the payment information acquisition unit 308 is realized by the control unit 31.
[0099] [6-1. Variation 1] For example, when a user needs to make a high-priced payment, he or she may want to use a second service, such as an installment payment app. For this reason, when an unpaid product or service is high-priced, the second service information I40 may be proposed. The unpaid information of the first modification indicates the price of the unpaid product or service. The data storage unit 100 of the first modification stores a price database indicating the prices of various products or services. The price database may be similar to a database employed in a known electronic commerce service.
[0100] The second service information acquisition unit 304 of the first modification acquires the second service information I40 based on the price indicated by the unpaid information. The second service information acquisition unit 304 determines whether the price indicated by the unpaid 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 second service information I40 to be proposed. The threshold may be common to all users, or may be determined for each 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 300.
[0101] In the above example, the second service information I40 is displayed based on whether the price indicated by the unpaid information is less than a predetermined threshold value, but the threshold value may be a price set by the user. For example, the second service information acquisition unit 304 may acquire the second service information I40 based on whether the price indicated by the unpaid information is equal to or greater than a threshold value according to the user's usage history of the installment payment service. For example, if the user has made installment payments in the past, the threshold value may be determined based on the amount of installment payments made by the user. As this threshold value, the average amount of installment payments made by the user, the payment amount for which the user has made installment payments most frequently, or other values may be adopted.
[0102] In addition, when the second service information I40 of the installment payment service is proposed to the user, the card company may propose the second service information I40 to a user who has a history of installments in the past. This is because a user who has never used installment payments before is unlikely to use an installment payment service. Based on the history information on the card company side, the relevant user and conditions (amount, etc.) may be extracted and linked to the payment business operator. The payment business operator may propose the second service information I40 to users who meet the conditions. The two-way data link between the payment business operator and the card company can further deepen the link between the services.
[0103] For example, if the second service information acquisition unit 304 determines that the price indicated by the unpaid information is less than the threshold, it does not acquire the second service information I40. If the suggestion unit 305 determines that the price indicated by the unpaid information is less than the threshold, it does not acquire the second service information I40. If the second service information acquisition unit 304 determines that the price indicated by the unpaid information is equal to or greater than the threshold, it acquires the second service information I40. If the suggestion unit 305 determines that the price indicated by the unpaid information is equal to or greater than the threshold, it suggests the second service information I40 to the user.
[0104] In addition, when there are multiple unpaid products or multiple unpaid services, the second service information acquisition unit 304 may acquire the second service information I40 based on the price of each of the multiple unpaid products or multiple unpaid services. For example, the second service information acquisition unit 304 may not acquire the second service information I40 when there is no unpaid product or unpaid service whose price is equal to or higher than the threshold, and may acquire the second service information I40 when there is at least one unpaid product or unpaid service whose price is equal to or higher than the threshold. The second service information acquisition unit 304 may acquire the second service information I40 when there are a predetermined number (e.g., five) or more unpaid products or unpaid services whose prices are equal to or higher than the threshold.
[0105] For example, when there are a plurality of unpaid products or a plurality of unpaid services, the second service information acquisition unit 304 may calculate the total amount (total price) of these prices. The second service information acquisition unit 304 may acquire the total amount calculated by the first service server 10, instead of calculating the total amount of the prices. The second service information acquisition unit 304 may not acquire the second service information I40 when the total amount is less than a threshold, and may acquire the second service information I40 when the total amount is equal to or greater than the threshold. The second service information acquisition unit 304 may calculate an average amount instead of the total amount. The second service information acquisition unit 304 may not acquire the second service information I40 when the average amount is less than a threshold, and may acquire the second service information I40 when the average amount is equal to or greater than the threshold.
[0106] The proposal system 1 of the first modification acquires the second service information I40 based on the price indicated by the unpaid information. This allows the proposal system 1 to propose the second service information I40 to a user for whom the proposal of the second service information I40 would be effective. For example, when a user is hesitant to purchase an expensive unpaid product or service, the proposal system 1 can propose the second service information I40, such as an installment payment app, and can provide the user with more beneficial second service information I40.
[0107] [6-2. Variation 2] For example, in the embodiment, an example is given of a case where an e-commerce service corresponds to the first service, but the first service is not limited to an online service, of which e-commerce service is an example. In the second modification, an example is given of a case where the first service is an offline service. An offline service is a service provided at a specific location in the real world. For example, a product sales service at a home appliance retailer or retail store, a treatment service at a beauty salon or aesthetic salon, or other services correspond to an offline service.
[0108] The proposed system 1 of the second modification includes a user location information acquisition unit 306. The user location information acquisition unit 306 acquires user location information related to the user's location. The user location information is information that allows the user's location to be estimated. The user location information may be publicly known information. For example, the user location information may be latitude and longitude, coordinates other than latitude and longitude, information on a communication device such as an access point or a mobile base station, or other information. The user location information is detected by the user terminal 40. For example, the GPS receiver, the communication unit 43, the photographing unit 46, or other means of the user terminal 40 are used to acquire the user location information. The method of acquiring the user location information may also be a publicly known method. For example, the user location information acquisition unit 306 may acquire the user location information based on a payment location, which is the location where the user made a payment. The payment location is a location where a store or the like that is affiliated with the payment service is located. For example, the user location information acquisition unit 306 may acquire the user location information based on terminal identification information that identifies the terminal of the store. In this case, data indicating the relationship between the terminal identification information of each store and the location information indicating the location of the store is assumed to be stored in advance in the data storage unit 300. The user location information acquisition unit 306 acquires the location information associated with the terminal identification information as the user location information based on the data. For example, when the user makes a payment at a home electronics retail store or in the vicinity thereof, the user location information acquisition unit 306 may acquire the user location information indicating the home electronics retail store. As another example, when determining the payment location, the user location information acquisition unit 306 may determine a plurality of payment locations in a predetermined period. For example, when the user makes a payment at two or more specific locations (e.g., home electronics retail stores) in the most recent month, the user location information acquisition unit 306 may acquire the user location information indicating the locations.
[0109] In the second modification, a case where a GPS receiver of the user terminal 40 is used is taken as an example. For example, the user terminal 40 acquires user location information based on a signal received by the GPS receiver. The user terminal 40 transmits the user location information acquired using the GPS receiver to the first service server 10. The user location information acquisition unit 306 acquires the user location information from the user terminal 40. The user location information acquisition unit 306 can acquire the user location information at any timing. For example, the user location information acquisition unit 306 may acquire the user location information at the timing when the user terminal 40 is started, the timing when the first application is started, the timing when the second application is started, the timing when the payment application is started, or at other timing.
[0110] The unpaid information acquisition unit 303 of the second modification acquires unpaid information of an unpaid product or an unpaid service based on the user location information. For example, the unpaid information acquisition unit 303 may acquire the unpaid information by estimating the unpaid product or the unpaid service based on the user location information, or may acquire the unpaid information from the first service server 10. As an example of the unpaid information of the second modification, information for identifying the unpaid product or the unpaid service (e.g., JAN code, etc.) will be described. Note that the unpaid information is not limited to information for identifying the unpaid product or the unpaid service. In the second modification as well, the unpaid information may be various information exemplified in the embodiment, etc.
[0111] In the second modification, the positional relationship data indicating the relationship between the position indicated by the user position information and the unpaid information for identifying the unpaid product or the unpaid service is stored in advance in the data storage unit 300. The positional relationship data may be in any format. For example, the positional relationship data may be in a table format, a mathematical formula format, a part of a program, or a machine learning model. The unpaid product or the unpaid service indicated by the unpaid information is a product or a service handled at the location associated with the unpaid information or a location nearby the location. Nearby means an area including the location indicated by the user position information, or a location within a predetermined distance from the location indicated by the user position information. Depending on the location, no unpaid product or unpaid service may be associated.
[0112] For example, if a home appliance retailer is present at or near a certain location, the unpaid information associated with the location in the location relationship data indicates a product or service sold at the home appliance retailer as an unpaid product or service. Since a home appliance retailer handles multiple products or services, the unpaid information may indicate a representative product or service among them (e.g., the most popular product or service), or may indicate a product or service that is the highlight of the home appliance retailer or a product or service that is currently on a campaign. For another example, if a beauty salon is present at or near a certain location, the unpaid information associated with the location in the location relationship data indicates a product or service sold at the beauty salon as an unpaid product or service. Similarly, for other locations, products or services handled at or near other locations may be indicated in advance in the unpaid information of the location relationship data as unpaid products or services.
[0113] For example, the unpaid information acquisition unit 303 acquires unpaid information associated with the location indicated by the user location information based on the location relationship data. That is, the unpaid information acquisition unit 303 acquires unpaid information indicating products or services handled at the location indicated by the user location information or a place nearby as unpaid products or unpaid services. The processing of the second service information acquisition unit 304 and the proposal unit 305 after the unpaid information is acquired may be similar to that of the embodiment. When the first and second modifications are combined, the second service information acquisition unit 304 acquires the second service information I40 based on the price of the unpaid product or unpaid service indicated by the unpaid information associated with the location indicated by the user location information.
[0114] As described above, the unpaid information acquisition unit 303 may acquire unpaid information by estimating an unpaid product or an unpaid service based on the user location information and the location relationship data. For example, the unpaid information acquisition unit 303 may acquire unpaid information of an unpaid product or an unpaid service from the first service server 10 based on the user location information. In this case, it is assumed that the location relationship data is stored in the data storage unit 100 of the first service server 10. For example, the unpaid information acquisition unit 303 transmits user location information to the first service server 10 to inquire about unpaid information. The first service server 10 transmits unpaid information associated with the user location information to the payment server 30 based on the location relationship data. The unpaid information acquisition unit 303 acquires unpaid information from the first service server 10. When the first service server 10 can acquire user location information directly from the user terminal 40, the unpaid information acquisition unit 303 may acquire unpaid information from the first service server 10 without inquiring about the first service server 10.
[0115] The method of utilizing the user location information is not limited to the above example. For example, the user location information may be utilized not to obtain unpaid information but to propose the second service information I40. For example, the suggestion unit 305 may propose the second service information I40 to the user based on the user location information. Furthermore, the suggestion unit 305 may propose the second service information I40 to the user based on the unpaid information and the user location information. In the example described in the embodiment, the unpaid information indicates an online unpaid product or an unpaid service. On the other hand, the user location information indicates an offline location. The suggestion unit 305 may propose the second service information I40 to the user based on the unpaid information, which is online information, and the user location information, which is offline information.
[0116] For example, the unpaid information indicates a home appliance of an online electronic commerce service (it may be a specific product or only a type of product). Furthermore, it is assumed that the user location information indicates a location of a home appliance retail store or its vicinity. In this case, the suggestion unit 305 may suggest second service information I40 suitable for the home appliance based on the unpaid information and the user location information. Data indicating a combination of the unpaid information and the user location information and the second service information I40 to be suggested to the user is stored in the data storage unit 300. The suggestion unit 305 suggests the second service information I40 according to the combination of the unpaid information and the user location information based on the data. The suggestion unit 305 may suggest benefit information related to benefits (e.g., coupons, etc.) related to the first service other than the second service information I40. Data necessary for suggesting the benefit information is also stored in the data storage unit 300.
[0117] The proposal system 1 of the second modification acquires unpaid information of an unpaid product or an unpaid service based on user location information. This allows the proposal system 1 to estimate an unpaid product or an unpaid service based on the user's location, and acquire and propose the second service information I40. For example, even if the user does not use an e-commerce service, the proposal system 1 can estimate what unpaid product or unpaid service the user is considering based on the location the user actually visited, and acquire and propose the second service information I40 corresponding to the estimated unpaid product or unpaid service.
[0118] Furthermore, the proposal system 1 proposes second service information I40 to the user based on the user location information. This allows the proposal system 1 to make optimal proposals according to the user's location, thereby improving user convenience. For example, the user can know the second service information I40 according to his / her own location. If the user is in or near a home appliance retail store, the user can know the second service information I40 related to home appliances. If the user is in or near a baby goods store, the user can know the second service information I40 related to baby goods.
[0119] [6-3. Variation 3] For example, when a user has entered a campaign, the user is likely to be considering a product or service that is the subject of the campaign. Therefore, an unpaid product or service may be estimated based on the campaign to which the user has entered. The campaign may be any campaign that can be entered from the user terminal 40. In the third modification, a campaign for an e-commerce service similar to that of the embodiment will be described as an example of a campaign.
[0120] The proposed system 1 of the modified example 3 includes a campaign information acquisition unit 307. The campaign information acquisition unit 307 acquires campaign information related to a campaign to which the user has entered in the first service. It is assumed that the first service database DB1 of the modified example 3 stores campaign information. The campaign information is information that can identify the campaign to which the user has entered. For example, the campaign information indicates the ID of the campaign to which the user has entered and the date and time of entry.
[0121] The data storage unit 300 may store a campaign database in which various information on campaigns held in the first service is stored. The campaign database may store the period during which the campaign is held, the name of the campaign, the product or service that is the target of the campaign, the affiliated store that is the target of the campaign (for example, when a user enters a campaign of a certain affiliated store, the user and the affiliated store may be associated to determine whether there is an unpaid product or unpaid service provided by the affiliated store), specific contents of the campaign (for example, benefits that a user can obtain by entering a campaign), or other information. Every time a campaign is held in the first service, the first service server 10 adds information on the campaign to the campaign database.
[0122] The unpaid information acquisition unit 303 of the third modification acquires unpaid information based on campaign information. As an example of the unpaid information of the third modification, information for identifying an unpaid product or an unpaid service (e.g., a JAN code, etc.) will be described. Note that the unpaid information is not limited to information for identifying an unpaid product or an unpaid service. In the third modification, the unpaid information may be various information exemplified in the embodiments, etc. The unpaid information acquisition unit 303 may acquire unpaid information indicating the unpaid products or unpaid services of each affiliated store that is the subject of a campaign.
[0123] In the third modification, campaign relationship data indicating the relationship between the campaign indicated by the campaign information and the unpaid information for identifying the unpaid product or unpaid service is stored in advance in the data storage unit 300. The campaign relationship data may be in any format. For example, the campaign relationship data may be in a table format, a mathematical formula format, a part of a program, or a machine learning model. The unpaid product or unpaid service indicated by the unpaid information is a product or service that is the subject of the campaign associated with the unpaid information. Some campaigns may not be associated with any unpaid product or unpaid service.
[0124] For example, the unpaid information acquisition unit 303 acquires unpaid information associated with the campaign indicated by the campaign information based on the campaign relation data. That is, the unpaid information acquisition unit 303 acquires unpaid information indicating a product or service handled in the campaign indicated by the campaign information as an unpaid product or service. The processing of the second service information acquisition unit 304 and the proposal unit 305 after the unpaid information is acquired may be similar to that of the embodiment. When the first and third modifications are combined, the second service information acquisition unit 304 acquires the second service information I40 based on the price of the unpaid product or service indicated by the unpaid information associated with the campaign indicated by the campaign information.
[0125] The proposal system 1 of the third modification acquires unpaid information based on campaign information. This allows the proposal system 1 to estimate an unpaid product or service based on the campaign, and acquire and propose the second service information I40. For example, since there is a high possibility that the user is particularly interested in a product or service that is the subject of a campaign that the user has entered, the proposal system 1 can estimate what unpaid product or service the user is considering based on the campaign that the user has entered, and acquire and propose the second service information I40 corresponding to the estimated unpaid product or service.
[0126] [6-4. Variation 4] For example, in the embodiment, only one first service is exemplified, but multiple first services may exist. In the fourth modification, a case where multiple first services that are different electronic commerce services exist is exemplified. The payment service is capable of linking with each of the multiple first services. For example, the payment service links with two first services, such as a first electronic commerce service and a second electronic commerce service. The payment service may link with three or more first services. User IDs are linked between the payment service and the first service, and at least one of the first service server 10 and the payment server 30 is capable of identifying which user has which user ID.
[0127] In the fourth modification, a first service server 10 is assumed to exist for each first service. The payment server 30 is capable of communicating with the first service servers 10 of each of the multiple first services. The functions of each first service server 10 may be similar to those of the first service servers 10 described in the embodiment. Each first service server 10 stores a first service database DB1 in which various information on users in the first service provided by the first service server 10 is stored, and a database in which various information on products or services handled in the first service provided by the first service server 10 is stored.
[0128] The unsettled information acquisition unit 303 of the fourth modification acquires unsettled information for each of a plurality of first services. For example, the unsettled information acquisition unit 303 acquires unsettled information for unsettled products or unsettled services handled in each of a plurality of first services from the first service server 10 of that first service. The process in which the unsettled information acquisition unit 303 acquires the unsettled information for each first service is as described in the embodiment. The content indicated by the unsettled information for one first service may be different from the content indicated by the unsettled information for another first service.
[0129] The second service information acquisition unit 304 of the fourth modification acquires the second service information I40 based on the unpaid information of each of the plurality of first services. For example, the second service information acquisition unit 304 determines whether or not at least one of the unpaid information of each of the plurality of first services indicates that there is an unpaid product or an unpaid service. If none of the unpaid information indicates that there is an unpaid product or an unpaid service, the second service information acquisition unit 304 does not acquire the second service information I40, and if at least one of the unpaid information indicates that there is an unpaid product or an unpaid service, the second service information acquisition unit 304 acquires the second service information I40.
[0130] For example, the second service information acquisition unit 304 may determine whether or not there is a predetermined number of pieces of unpaid information indicating that there is an unpaid product or an unpaid service among the unpaid information for each of the multiple first services. If it is determined that there is not a predetermined number of pieces of unpaid information indicating that there is an unpaid product or an unpaid service, the second service information acquisition unit 304 may not acquire the second service information I40, and may acquire the second service information I40 if it is determined that there is a predetermined number of pieces of unpaid information indicating that there is an unpaid product or an unpaid service.
[0131] When combining the first and fourth modified examples, the unpaid information of each of the first services may indicate the price of the unpaid product or service in the first service. In this case, the second service information acquisition unit 304 may determine whether the price indicated by the unpaid information of each of the first services is equal to or higher than a threshold. The second service information acquisition unit 304 may not acquire the second service information I40 when it is determined that the price indicated by all the unpaid information is less than the threshold, and may acquire the second service information I40 when it is determined that the price indicated by at least one of the unpaid information is equal to or higher than the threshold.
[0132] Alternatively, for example, the second service information acquisition unit 304 may calculate the total amount or average amount of the price indicated by the unpaid information of each of the first services, and determine whether the total amount or the average amount is equal to or greater than a threshold. If the second service information acquisition unit 304 determines that the total amount or the average amount is less than the threshold, it may not acquire the second service information I40, and if it determines that the total amount or the average amount is equal to or greater than the threshold, it may acquire the second service information I40.
[0133] The proposal system 1 of the fourth modification acquires the second service information I40 based on the unpaid information of each of the first services. This allows the proposal system 1 to make more effective proposals by comprehensively considering the potential needs of the users of each of the first services.
[0134] [6-5. Variation 5] For example, the second service information acquisition unit 304 may acquire second service information I40 related to an application list including the second application, which is an application list related to applications available on the user terminal 40 of the user. In the fifth modification, second service information I40 for displaying an application list including not only the second application but also other applications is proposed, instead of second service information I40 showing only the second application as in Fig. 2. The second service information acquisition unit 304 acquires second service information I40, an example of which will be described below.
[0135] Fig. 9 is a diagram showing an example of a screen displayed on the user terminal 40 of the fifth modified example. For example, when the user selects "See all" in the application list L31 in the state of the payment service screen SC3 in the upper left of Fig. 9, the user terminal 40 displays on the display unit 45 a modal M32 including an application list from which more applications can be selected, as shown in the upper right of Fig. 9. When the user selects an application from the application list in the modal M32, the user terminal 40 launches the application.
[0136] In the fifth modification, when the user executes a payment, as shown in the lower left of Fig. 9, the user terminal 40 displays second service information I40 indicating a link for displaying a list of apps or other information on the payment completion screen SC4. The second service information I40 may be information for displaying the app list L31 of Fig. 2. When the user selects the second service information I40, as shown in the lower right of Fig. 9, the user terminal 40 displays a modal M41 similar to the modal M32 on the display unit 45. The app list of the modal M41 shows an installment payment app, which is an example of the second app.
[0137] For example, the user can use the second app by selecting the second app from the list of apps displayed in the modal M41. It is assumed that actual data for displaying the list of apps is stored in the data storage unit 300. The second service information acquisition unit 304 acquires second service information I40 for displaying the list of apps including the second app based on the actual data. The flow proposed to the user after the second service information I40 is acquired is the same as in the embodiment.
[0138] The proposal system 1 of the fifth modification acquires second service information I40 related to an application list including a second application, which is an application list related to applications available on the user terminal of the user. The proposal system 1 can promote the use of applications other than the second application while proposing an installment payment application.
[0139] [6-6. Variation 6] For example, the second service information I40 may be proposed after taking into consideration payment information related to a payment executed in a payment service. The proposed system 1 of the sixth modification further includes a payment information acquisition unit 308 that acquires payment information related to a payment executed by the user in a payment service different from the first service and the second service. The user performs an operation for payment from the user terminal 40. For example, the user's operation for starting a payment app, an operation for displaying the code C30, an operation for causing the store terminal 50 to read the code C30, or other operation corresponds to the user executing a payment using the user terminal 40. Information processing for executing the payment is executed by the payment execution unit 301.
[0140] The payment information may be any information related to the content of the payment. For example, the payment information is all or part of the information included in the payment request received by the payment server 30 from at least one of the user terminal 40 and the store terminal 50. 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.
[0141] In this embodiment, the payment information acquisition unit 308 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 308 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 308 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. For example, the payment information may indicate the payment location, the product or service that was the subject of the payment, the time of the payment, or other information.
[0142] The second service information acquisition unit 304 of the sixth modification acquires the second service information I40 further based on the payment information. For example, the second service information acquisition unit 304 determines whether or not 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 acquire the second service information I40. The threshold may be common to all users, or may be determined for each 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 300.
[0143] For example, the second service information acquisition unit 304 acquires the second service information I40 of 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. The second service information acquisition unit 304 does not acquire the second service information I40 of the installment payment app when it is determined that the payment amount indicated by the payment information is less than a threshold. When it is determined that the payment amount indicated by the payment information is less than a threshold, the second service information acquisition unit 304 may acquire other information such as an advertisement to be displayed instead of the second service information I40. It is assumed that data of the other information is also stored in the data storage unit 100.
[0144] The second service information acquisition unit 304 may acquire the second service information I40 based on the payment location indicated by the payment information, the product or service that is the subject of the payment, the payment time, or other information. For example, the second service information acquisition unit 304 may acquire the second service information I40 of the second app provided by a store located in the payment location indicated by the payment information. The second service information acquisition unit 304 may acquire the second service information I40 of the second app provided by a store located near the payment location indicated by the payment information. The second service information acquisition unit 304 may acquire the second service information I40 indicating a coupon for a product or service similar to the product or service that is the subject of the payment.
[0145] The suggestion unit 305 may also determine the relevance between the payment information and the unpaid product or the unpaid service, and may suggest the second service information I40 to the user based on the result of the determination. For example, it is assumed that the unpaid product or the unpaid service is a home appliance. Furthermore, it is assumed that the payment information indicates that the store or the location where the user made the payment is in a home appliance retailer. In this case, the suggestion unit 305 may determine that the user is looking for a home appliance (i.e., it determines that there is a relevance between the payment information and the unpaid product or the unpaid service), and may suggest the second service information I40 related to the home appliance to the user. As another example, it is assumed that the unpaid product or the unpaid service is a baby product. Furthermore, it is assumed that the payment information indicates that the product where the user made the payment is a baby product, or that the store where the user made the payment is a baby product store. In this case, the suggestion unit 305 may estimate that the user is looking for a baby product, and may suggest the second service information I40 related to the baby product to the user.
[0146] The proposed system 1 of the sixth modification acquires payment information on a payment made by a user in a payment service. The proposed system 1 further acquires second service information I40 based on the payment information. This allows the proposed system 1 to propose not only unpaid information but also second service information I40 according to the payment information on the payment service side, thereby making it possible to propose more useful information to the user.
[0147] [6-7. Other Modifications] For example, the above modifications may be combined.
[0148] 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 40. In this case, the user may execute the payment by having the store terminal 50 read the code C30 displayed on the browser, or may execute the payment online instead of at the store without using the code C30 in particular. The online payment is completed only by the operation on the user terminal 40. 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 proposal system 1 may propose the second service information I40 on the payment completion screen SC4 of such an online payment. In this case, the second service information I40 may be information for proposing the payment app to the user.
[0149] For example, the functions described as being realized by the payment server 30 may be realized by the first service server 10, the second service server 20, the user terminal 40, the store terminal 50, or another computer. The processes described as being realized by the payment server 30 may be shared among multiple computers.
[0150] [7. Notes] For example, the proposed system can be configured as follows. (1) an unpaid information acquisition unit that acquires unpaid information regarding an unpaid product or an unpaid service that has not been paid for by a user and that is handled in a first service; a second service information acquisition unit that acquires second service information related to a second service different from the first service based on the unpaid information; a suggestion unit that proposes the second service information to the user; The proposed system includes: (2) the proposal system further includes a payment determination unit that determines whether the user has made a payment for a product other than the unpaid product or a service other than the unpaid service, using a payment service other than the first service and the second service; the second service information acquisition unit acquires the second service information when it is determined that the user has executed the payment for the different product or the different service. The proposed system described in (1). (3) the suggestion unit suggests the second service information to the user on a payment completion screen indicating that the payment has been completed. The proposed system described in (2). (4) the first service is an e-commerce service; the unpaid information acquisition unit acquires the unpaid information of the unpaid product or the unpaid service that the user is considering purchasing in the electronic commerce service; The proposed system according to any one of (1) to (3). (5) The unpaid information indicates a price of the unpaid product or the unpaid service, The second service information acquisition unit acquires the second service information based on the price indicated by the unsettled information. The proposed system according to any one of (1) to (4). (6) The suggestion system further includes a user location information acquisition unit that acquires user location information related to a location of the user, the unpaid information acquisition unit acquires the unpaid information of the unpaid product or the unpaid service based on the user location information; The proposed system according to any one of (1) to (5). (7) The suggestion system further includes a user location information acquisition unit that acquires user location information related to a location of the user, The suggestion unit suggests the second service information to the user based on the user location information. The proposed system according to any one of (1) to (6). (8) The proposal system further includes a campaign information acquisition unit that acquires campaign information regarding a campaign to which the user has entered in the first service, The unpaid information acquisition unit acquires the unpaid information based on the campaign information. The proposed system according to any one of (1) to (7). (9) the outstanding payment information acquisition unit acquires the outstanding payment information for each of the plurality of first services, The second service information acquisition unit acquires the second service information based on the unpaid information of each of the plurality of first services. The proposed system according to any one of (1) to (8). (10) the second service information acquisition unit acquires the second service information related to a second application for the user to use the second service; The proposed system according to any one of (1) to (9). (11) the second service information acquisition unit acquires the second service information relating to an application list regarding applications available on the user terminal of the user, the application list including the second application; The proposed system according to (10). (12) The second service information acquisition unit acquires the second service information of the second service that supports the payment of the unpaid product or the unpaid service. The proposed system according to any one of (1) to (11). (13) The proposed system further includes a payment information acquisition unit that acquires payment information regarding a payment made by the user using a payment service different from the first service and the second service; The second service information acquisition unit acquires the second service information further based on the payment information. The proposed system according to any one of (1) to (12). [Explanation of symbols]
[0151] 1 Proposed system, N Network, 10 First service server, 11, 21, 31, 41, 51 Control unit, 12, 22, 32, 42, 52 Memory unit, 13, 23, 33, 43, 53 Communication unit, 20 Second service server, 30 Payment server, 40 User terminal, 44, 54 Operation unit, 45, 55 Display unit, 46 Photography unit, 50 Store terminal, 56 Reading unit, 100, 200, 300, 400, 500 Data storage unit, 301, 501 Payment execution unit, 302 Payment judgment unit, 303 Unpaid information acquisition unit, 304 Second service information acquisition unit, 305 Proposal unit, 306 User location information acquisition unit, 307 Campaign information acquisition unit, 308 Payment information acquisition unit, 401 Operation reception unit, 402 Display control unit, C30 Code, DB1 First service database, DB2 payment service database, I10, I11, I12 icons, L311 app list, I40 second service information, SC1 menu screen, SC2 first service screen, SC3 payment service screen, SC4 payment completion screen.
Claims
1. an unpaid information acquisition unit that acquires unpaid information regarding an unpaid product or an unpaid service that has not been paid for by a user and that is handled in a first service; a payment determination unit that determines whether the first service and a second service different from the first service are different payment services, and whether the user has made a payment for a product different from the unpaid product or a service different from the unpaid service; a second service information acquisition unit that acquires second service information related to the second service based on the unpaid information when it is determined that the user has made the payment for the different product or the different service; a suggestion unit that proposes the second service information to the user; The proposed system includes:
2. the suggestion unit suggests the second service information to the user on a payment completion screen indicating that the payment has been completed. The recommendation system of claim 1 .
3. the first service is an electronic commerce service; the unpaid information acquisition unit acquires the unpaid information of the unpaid product or the unpaid service that the user is considering purchasing in the electronic commerce service; The proposal system according to claim 1 or 2.
4. The unpaid information indicates a price of the unpaid product or the unpaid service, The second service information acquisition unit acquires the second service information based on the price indicated by the unpaid information. The proposal system according to claim 1 or 2.
5. A user location information acquisition unit that acquires user location information regarding a user's location; an unpaid information acquisition unit that acquires unpaid information of an unpaid product or an unpaid service based on location relationship data indicating a relationship between a location indicated by the user location information and unpaid information for identifying the unpaid product or the unpaid service that is not paid for by the user and is handled in a first service; a second service information acquisition unit that executes a determination as to whether the unpaid information indicates that the unpaid product or the unpaid service exists, and acquires second service information related to a second service different from the first service based on a result of the execution of the determination; a suggestion unit that proposes the second service information to the user; The proposed system includes:
6. The suggestion system further includes a user location information acquisition unit that acquires user location information related to a location of the user, The suggestion unit suggests the second service information to the user based on the user location information. The proposal system according to claim 1 or 2.
7. A campaign information acquisition unit that acquires campaign information regarding a campaign in which a user has entered in the first service; an unpaid information acquisition unit that acquires unpaid information related to an unpaid product or an unpaid service that has not been paid for by the user and is handled by the first service based on the campaign information; a second service information acquisition unit that executes a determination as to whether the unpaid information indicates that the unpaid product or the unpaid service exists, and acquires second service information related to a second service different from the first service based on a result of the execution of the determination; a suggestion unit that proposes the second service information to the user; The proposed system includes:
8. the outstanding payment information acquisition unit acquires the outstanding payment information for each of the plurality of first services; The second service information acquisition unit acquires the second service information based on the unpaid information of each of the plurality of first services. The proposal system according to claim 1 or 2.
9. An unpaid information acquisition unit that acquires unpaid information regarding an unpaid product or an unpaid service that has not been paid by a user and is handled by a first service; a second service information acquisition unit that executes a determination as to whether the unpaid information indicates that the unpaid product or the unpaid service exists, and acquires second service information regarding the app list, which is an app list regarding apps available on the user terminal of the user, including a second app for the user to use a second service different from the first service, based on a result of the execution of the determination; a suggestion unit that proposes the second service information to the user; The proposed system includes:
10. The second service information acquisition unit acquires the second service information of the second service that supports the payment of the unpaid product or the unpaid service. The proposal system according to claim 1 or 2.
11. The proposed system further includes a payment information acquisition unit that acquires payment information regarding a payment executed by the user using a payment service different from the first service and the second service, The second service information acquisition unit acquires the second service information further based on the payment information. The proposal system according to claim 1 or 2.
12. A computer comprising: an unpaid information acquisition step of acquiring unpaid information regarding an unpaid product or an unpaid service that has not been paid for by a user and that is handled by a first service; a payment determination step of determining whether the first service and a second service different from the first service are different payment services, and whether the user has made a payment for a product different from the unpaid product or a service different from the unpaid service; a second service information acquisition step of acquiring second service information related to the second service based on the unpaid information when it is determined that the user has made the payment for the different product or the different service; a proposing step of proposing the second service information to the user; A proposed method for carrying out the above.
13. an unpaid information acquisition unit that acquires unpaid information regarding an unpaid product or an unpaid service that has not been paid for by a user and that is handled in the first service; a payment determination unit that determines whether the first service and a second service different from the first service are different payment services, and whether the user has made a payment for a product different from the unpaid product or a service different from the unpaid service; a second service information acquisition unit that acquires second service information related to the second service based on the unpaid information when it is determined that the user has made the payment for the different product or the different service; a suggestion unit that proposes the second service information to the user; A program that makes a computer function as a
Citation Information
Patent Citations
Selection device, selection method, and selection program
JP2022104128A
Operation method of electronic device for providing item information and electronic device for supporting the same
JP2022168799A
Information processing system, information processing method, and program
JP2023061602A
Cited By
Display control system, display control method, and program
JP7915330B1