Auto-charge system, auto-charge method, and program

Abstract

To improve user convenience. [Solution] The usage information acquisition unit (101) of the auto-charge system (1) acquires usage information regarding the use of a payment method that is capable of auto-charging and is used in at least one of multiple services. The presentation unit (102) makes a presentation to the user according to the usage information when the user specifies a designated setting for auto-charging. The setting acquisition unit (103) acquires the designated setting for auto-charging specified by the user when a presentation is made. The auto-charge execution unit (104) executes auto-charging based on the designated setting.

Description

Technical Field

[0001] The present disclosure relates to an auto - recharge system, an auto - recharge method, and a program.

Background Art

[0002] Conventionally, a payment service corresponding to a payment means capable of auto - recharge has been known. For example, in Patent Document 1, an auto - recharge setting indicating whether to auto - recharge electronic money when the balance of the electronic money becomes less than a threshold value is stored, and when the auto - recharge setting indicates auto - recharge, based on a payment means such as a bank account registered by the user, a communication system that executes auto - recharge of electronic money is described.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the technology of Patent Document 1, the user has to consider by himself / herself what auto - recharge setting is appropriate and specify the auto - recharge setting, so the convenience of the user cannot be sufficiently improved. This is the same for other technologies other than Patent Document 1. In the conventional technology, the convenience of the user in a payment service corresponding to a payment means capable of auto - recharge cannot be sufficiently improved.

[0005] One of the objects of the present disclosure is to improve the convenience of the user.

Means for Solving the Problems

[0006] The auto-charge system relating to this disclosure is a payment means that enables auto-charging and includes: a usage information acquisition unit that acquires usage information relating to the use of the payment means in at least one of a plurality of services; a presentation unit that makes a presentation to the user according to the usage information when a designated setting relating to the auto-charge setting is specified by the user; a setting acquisition unit that acquires the designated setting specified by the user when such a presentation is made; and an auto-charge execution unit that performs the auto-charge based on the designated setting. [Effects of the Invention]

[0007] This disclosure can improve user convenience. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of the hardware configuration of an auto-charge system. [Figure 2] This figure shows an example of a screen displayed on a user's terminal. [Figure 3] This figure shows an example of the functions implemented by the auto-charge system. [Figure 4] This figure shows an example of a user database. [Figure 5] This figure shows an example of the process performed by the auto-charge system. [Figure 6] This figure shows an example of a function that can be achieved through modification. [Figure 7] This figure shows an example of screen transitions in modified example 2. [Figure 8] This figure shows an example of a designation setting associated with at least one of multiple periods in modified example 4. [Figure 9] This diagram shows an example of the relationship between the source service and the charging timing. [Figure 10] This figure shows an example of a settings screen where suggested settings are displayed based on the settings history information. [Figure 11] This figure shows an example of the settings screen for Modification Example 7. [Figure 12] This figure shows an example of how the specified settings are suggested to be changed in Modification Example 8. [Figure 13] This figure shows an example of the settings screen in modified example 10. [Figure 14] This figure shows an example of the settings screen in modified example 12. [Modes for carrying out the invention]

[0009] [1. Hardware configuration of the auto-charge system] This disclosure describes an example of an embodiment of the auto-charge system, auto-charge method, and program. Figure 1 shows an example of the hardware configuration of the auto-charge system. For example, the auto-charge system 1 includes a server 10 and a user terminal 20. Each of the server 10 and the user terminal 20 is connected to a network N such as the Internet or a LAN. At least one of the server 10 and the user terminal 20 may be present in multiple units.

[0010] Server 10 is a server computer for a payment service. The payment service is a service that provides electronic payments (cashless payments) to users. For example, 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 volatile memory such as RAM and non-volatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0011] The user terminal 20 is the user's computer. For example, the user terminal 20 is a smartphone, a tablet, a personal computer, or a wearable terminal. The user terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an operation unit 24, and a display unit 25. The hardware configurations of the control unit 21, the storage unit 22, and the communication unit 23 may be the same as those of the control unit 11, the storage unit 12, and the communication unit 13, respectively. The operation unit 24 is an input device such as a touch panel or a mouse. The display unit 25 is a display such as a liquid crystal or an organic EL.

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

[0013] Also, the auto-charge system 1 may include at least one computer. The computer included in the auto-charge system 1 is not limited to the example of FIG. 1. For example, the auto-charge system 1 may include only the server 10. In this case, the user terminal 20 exists outside the auto-charge system 1. The auto-charge system 1 may include the server 10 and another computer not shown in FIG. 1 (e.g., a server computer for a point service described later).

[0014] [Overview of Auto-Charge System] In this embodiment, an example is given of a case where a user uses a payment service from a payment application stored in the user terminal 20. The payment application is an application provided by the administrator of the payment service. The user can use any payment method in the payment service. For example, the user may be able to use electronic money, a balance not called electronic money, a credit card, a card other than a credit card, points, a bank account, an account other than a bank account, a cryptocurrency, a wallet, or other payment methods in the payment service. Since the payment method may be used for payment, it can also be called a payment means.

[0015] For example, the user installs a payment application on the user terminal 20 and registers as a member of the payment service. When the user completes the membership registration of the payment service, the user can start the payment application on the user terminal 20 and use the payment service. Note that the user may use the payment service from an application other than the payment application stored in the user terminal 20 (for example, an application provided by a credit card company or other non-payment application), or may use the payment service from the browser stored in the user terminal 20.

[0016] FIG. 2 is a diagram showing an example of a screen displayed on the user terminal 20. For example, when the user operates the user terminal 20 to start the payment application, as shown in the upper left of FIG. 2, the user terminal 20 displays the top screen SC1 of the payment application on the display unit 25. The top screen SC1 includes a tab T10 for the user to switch between a state where a payment code (for example, a barcode or a two-dimensional code) for payment is displayed, a state where an operation for charging or sending electronic money is accepted, and a state where a point code as a point card is displayed. In the example in the upper left of FIG. 2, the top screen SC1 is in a state where an operation for charging or sending electronic money is accepted.

[0017] For example, when a user selects button B11 for charging electronic money, the user terminal 20 displays a charge screen SC2 on the display unit 25, as shown in the upper right of Figure 2, which accepts the user to specify the charge amount. The user can enter any charge amount in the input form F20. The user can change the charge source by selecting panel P21, which shows the current charge source. The charge source is the payment method that provides the funds for the charge. In the example in the upper right of Figure 2, a credit card is specified as the charge source. The user can specify the charge amount from the charge screen SC2 and charge immediately.

[0018] In this embodiment, we will give an example of a case where the user can also set up auto-charge from the charge screen SC2. For example, when the user selects the auto-charge button B22, the user terminal 20 displays a setting screen SC3 on the display unit 25, which accepts the specification of the auto-charge setting, as shown in the lower left of Figure 2. In the example in the lower left of Figure 2, the user specifies the balance after charging as the auto-charge setting. The balance after charging is the balance after auto-charging has been performed. The balance after charging can also be said to be the balance that the user wants to maintain. For example, when the electronic money balance falls below the balance after charging, auto-charging is performed so that the electronic money balance becomes equal to or greater than the balance after charging.

[0019] The auto-charge settings may be the same as those used in publicly known payment services. The auto-charge settings are not limited to the examples of this embodiment. For example, the auto-charge settings may include the charge amount, the balance threshold at which auto-charge is triggered, the date on which auto-charge is triggered, the charge source used for auto-charge, the upper limit of the cumulative charge amount for a specific period (e.g., one day, one week, or one month), or a combination of these. Users can specify various auto-charge settings from the settings screen SC3.

[0020] In this embodiment, an appropriate balance is suggested as an auto-charge setting based on the user's usage history in each of multiple services where electronic money can be used. The multiple services include the payment service used from the payment app of this embodiment and other services different from the payment service. The other services may be any service. For example, the other services may be other payment services different from the payment service used from the payment app of this embodiment, e-commerce services, travel booking services, communication services, or financial services.

[0021] Hereafter, the auto-charge settings suggested to the user will be referred to as suggested settings. The auto-charge settings specified by the user will be referred to as specified settings. When there is no need to distinguish between suggested settings and specified settings, they will simply be referred to as settings. Suggested settings and specified settings may be the same or different from each other. Suggested settings are for reference only, so users may specify specified settings that are different from the suggested settings. Suggested settings may only be suggested in certain cases. For example, they may only be suggested when a user specifies a specified setting for the first time, when a certain amount of time has not elapsed since the user registered as a member of the payment app, or when the payment app's usage history has been obtained.

[0022] For example, server 10 refers to the electronic money usage history for the past year and identifies the highest amount of electronic money used. If the highest amount was 18,000 yen, in the example in the lower left of Figure 2, message M30 showing the same 18,000 yen as the highest amount is displayed, and the suggested setting is proposed. As will be described later, message M30 may also show a total amount obtained by adding a predetermined amount (for example, 5,000 yen) to the highest amount. The user refers to message M30 and enters an arbitrary post-charge balance as the specified setting in input form F31. The post-charge balance that the user can specify may be an integer multiple of a predetermined amount, such as in units of 10 yen, 100 yen, or 1,000 yen.

[0023] For example, when the user selects button B32, the server 10 saves the balance after charging entered in input form F31 as the specified setting. Once the specified setting is saved, the user terminal 20 displays a completion screen SC4 on the display unit 25, indicating that the specified setting has been saved, as shown in the lower right of Figure 2. In the example in the lower right of Figure 2, the user specified the same setting as the suggested setting, so the specified setting is 18,000 yen, the same as the suggested setting. When the electronic money balance falls below 18,000 yen, auto-charge is performed to bring the electronic money balance to 18,000 yen or more.

[0024] As described above, the auto-charge system 1 of this embodiment proposes an appropriate balance after charging as a suggested setting, based on the user's electronic money usage history. The auto-charge system 1 obtains the specified setting from the user. The auto-charge system 1 performs auto-charging based on the specified setting. This allows the user to specify the setting by referring to the suggested setting, thus enhancing user convenience. The details of the auto-charge system 1 will be described below.

[0025] [3. Functions realized by the auto-charge system] Figure 3 shows an example of the functions realized by the auto-charge system 1. The various components realized by the auto-charge system 1 of this embodiment can be configured by combining them into a single device or by further distributing them into smaller devices.

[0026] [3-1. Functions implemented by the payment server] For example, the server 10 includes a data storage unit 100, a usage information acquisition unit 101, a display unit 102, a setting acquisition unit 103, and an auto-charge execution unit 104. The data storage unit 100 is implemented by a storage unit 12. Each of the usage information acquisition unit 101, the display unit 102, the setting acquisition unit 103, and the auto-charge execution unit 104 is implemented by a control unit 11.

[0027] [Data Storage Unit] The data storage unit 100 stores various data for auto-charging. For example, the data storage unit 100 stores the user database DB.

[0028] Figure 4 shows an example of a user database DB. The user database DB is a database that stores various information for payment. For example, the user database DB stores user ID, login account, password, payment method information, current balance of electronic money, electronic money usage information, and specified settings. The information stored in the user database DB is not limited to the example in Figure 4. Other information may be stored in the user database DB. For example, the user database DB may store information necessary for displaying payment codes, information necessary for displaying point codes, payment source information in the payment app, user's email address, phone number, SNS or messaging app accounts, or other information.

[0029] A user ID is an example of user identification information that can identify a user. A login account is also an example of user identification information. A login account is user identification information that a user enters to log in to a payment service. The login account may be freely changed by the user. A user ID is user identification information that is managed separately from the login account. In this embodiment, we take the example of a case where there is a login account separate from the user ID (where there are at least two pieces of user identification information), but there may be only one piece of user identification information. That is, the user ID and login account do not have to be separate. A password is authentication information that is verified during login. The login account and password may be the user's biometric information.

[0030] Payment method information is information that identifies the payment methods available to the user in the payment service. For example, payment method information may include credit card numbers, electronic money numbers, bank account information, or point card numbers. The current balance of electronic money is updated each time the electronic money is used or topped up. For example, one of the payment methods indicated in the payment method information is used as the source of the top-up. The current balance of electronic money may be managed on a computer other than server 10.

[0031] Electronic money usage information is information that shows at least one of the usage history and planned usage of electronic money. The usage information may show only the usage history, only the planned usage, or both the usage history and planned usage. Server 10 retrieves the individual pieces of information included in the usage information from at least one of the computers that manage the payment service and the computers that manage other services other than the payment service, and stores the usage information in the user database DB. The usage information may also be information regarding the use of electronic money and other payment methods.

[0032] The usage history is information that shows how electronic money has been used in the past. For example, if electronic money was used at a store, the usage history would show the store information, the amount used, and the date and time of use. The store is not limited to a physical store; it may also be an online store. The usage history may also show information about the goods or services purchased with the electronic money. In addition to purchases at stores, if the electronic money is capable of sending money, the usage history may also show the history of money transfers. For example, the usage history may show the recipient's information, the amount transferred, and the date and time of the transfer. The usage history may also show the history of transfers from one electronic money to another.

[0033] The usage plan is information indicating how electronic money will be used in the future. For example, if electronic money is used for a financial product's installment plan, the usage plan will show the financial product's identification information, the installment date, and the installment amount. If there are multiple usage plans, the usage information may show all of them. If electronic money is used for payment in a subscription service, the usage plan will show the subscription service's identification information, the payment date, and the payment amount. If electronic money is used to pay for a product reserved by the user, the usage plan will show the product's identification information, the payment date, and the price.

[0034] In this embodiment, we take the example of a case where the specified setting stored in the user database DB indicates the balance after charging. The specified setting may indicate other settings. For example, the specified setting may indicate the payment method from which the charge originated. The specified setting may indicate the period during which the specified setting applies (for example, the beginning, middle, or end of a certain month). The specified setting may indicate the activation conditions described in the modified examples below. The specified setting may indicate any of the auto-charge settings mentioned above.

[0035] The data stored in the data storage unit 100 is not limited to the examples above. The data storage unit 100 may also store other data related to the payment service. For example, the data storage unit 100 may store data necessary for displaying the top screen SC1, the charge screen SC2, the settings screen SC3, the completion screen SC4, or other screens.

[0036] [Usage information acquisition department] The usage information acquisition unit 101 acquires usage information regarding the use of electronic money in at least one of multiple services. Electronic money is an example of a payment method that allows for automatic top-up. Therefore, wherever "electronic money" is written, it can be read as "a payment method that allows for automatic top-up." The payment method that allows for automatic top-up may be any payment method and is not limited to electronic money. For example, the payment method that allows for automatic top-up may be a balance not called electronic money, an account such as a bank account, a wallet, or another payment method.

[0037] In this embodiment, since usage information is stored in the user database DB, the usage information acquisition unit 101 acquires usage information from the user database DB. For example, the usage information acquisition unit 101 acquires usage information associated with the user ID or login account of a user who is logged into the payment service from the usage information stored in the user database DB. The usage information may also be stored in a database other than the user database DB, a computer other than the server 10, or an information storage medium. The usage information acquisition unit 101 may acquire usage information from a database other than the user database DB, a computer other than the server 10, or an information storage medium.

[0038] In this embodiment, the usage information acquisition unit 101 acquires usage information regarding the use of electronic money in each of the multiple services. For example, if electronic money was available in three services such as a payment service, an e-commerce service, and a travel booking service, the usage information would show the use of electronic money in the payment service, the use of electronic money in the e-commerce service, and the use of electronic money in each of the travel booking services.

[0039] For example, the usage information acquisition unit 101 may acquire usage information regarding the use of electronic money in all of the multiple services that accept electronic money. The usage information will show a mixture of electronic money usage in each of the multiple services. As an example, the electronic money usage in each of the multiple services may be combined into a single data set, but the electronic money usage in each individual service may be separated into separate data sets. In this case, the combined data set will constitute the usage information.

[0040] Furthermore, the usage information acquisition unit 101 may acquire usage information regarding the use of electronic money in some of the multiple services that can use electronic money. For example, the usage information acquisition unit 101 may acquire usage information regarding the use of electronic money in any of the multiple services that can use electronic money. That is, the usage information acquisition unit 101 may acquire usage information that shows the use of electronic money in only one specific service among the multiple services that can use electronic money.

[0041] Furthermore, the usage information acquisition unit 101 may acquire usage information showing the use of electronic money over the entire past period, or it may acquire usage information showing the use of electronic money over a specific period in the past. For example, the usage information acquisition unit 101 may acquire usage information showing the use of electronic money over the most recent period (for example, the last week, the last month, or the last year). The usage information acquisition unit 101 may acquire usage information showing the use of electronic money in the future. The usage information acquisition unit 101 may acquire usage information showing the use of electronic money over both the past and the future.

[0042] [Presentation part] The presentation unit 102 provides the user with a presentation based on usage information when the user specifies the settings related to auto-charge. When the user specifies the settings, it means that the settings screen SC3, which accepts the specification of the settings, is displayed, or a screen related to the settings screen SC3 is displayed. For example, in the upper right example of Figure 2, when the user selects button B22 for setting auto-charge, a screen other than the settings screen SC3 may be displayed. In this case, the other screen may correspond to a screen related to the settings screen SC3. A presentation based on usage information may be made on the other screen, and then the user may be redirected to the settings screen SC3. Alternatively, for example, if a link such as "See setting amount" is displayed on the settings screen SC3, and the user selects this link, the other screen displayed may correspond to a screen related to the settings screen SC3. A presentation based on usage information may be made on the other screen, and then the user returns to the settings screen SC3. A presentation based on usage information may mean displaying the usage information itself (for example, "The highest daily usage amount in the past month was 10,000 yen."), or it may mean suggesting the suggested settings described later. When the presentation unit 102 makes a presentation according to the user information, it means that the presentation unit 102 transmits data indicating the content of the presentation according to the user information.

[0043] In this embodiment, an example is given where the presentation unit 102 presents to the user by proposing suggested settings for auto-charge based on usage information. In this embodiment, an example is given where the suggested setting is the balance after charging, but the suggested setting may be any other setting as described above. For example, the suggested setting may be the charge amount, the balance that triggers the auto-charge, the date on which the auto-charge is triggered, the charging source used for auto-charge, or a combination of these. The suggested setting may also be any other setting adopted in known auto-charge systems. The configuration that proposes suggested settings based on usage information is a novel configuration, but the items indicated by the suggested setting (the specific settings for auto-charge) themselves may be known items.

[0044] When the presentation unit 102 proposes a suggested setting, it means that the presentation unit 102 sends data indicating the suggested setting to the user terminal 20. Alternatively, the presentation unit 102 may send data indicating the suggested setting to the user's email address, phone number, or chat account instead of the user terminal 20. The data indicating the suggested setting can be in any format. For example, the data indicating the suggested setting may be HTML or other markup language data, image data, text data, data for displaying notifications on the user terminal 20, email data, or various message data.

[0045] In this embodiment, the suggested settings are proposed on the settings screen SC3, so the presentation unit 102 proposes the suggested settings to the user by sending the display data of the settings screen SC3 showing the suggested settings to the user terminal 20. In the example in the lower left of Figure 2, message M30 corresponds to the suggested settings. The suggested settings may also be proposed in other forms such as text other than message M30, images such as icons, or other formats. The suggested settings may also be entered as defaults in, for example, the input form F31. The presentation unit 102 may also propose the suggested settings to the user through other screens other than the settings screen SC3 (for example, the top screen SC1 or the charge screen SC2), windows, popups, modals, or banners.

[0046] The methods by which the presentation unit 102 proposes suggested settings are not limited to the examples above. The presentation unit 102 can propose suggested settings to the user by any method. For example, the presentation unit 102 may propose suggested settings to the user using the notification function of the payment app. The presentation unit 102 may propose suggested settings to the user using the notification function of the user terminal 20 itself, rather than the payment app. The presentation unit 102 may propose suggested settings to the user via email, SMS, messaging apps, SNS, or other methods.

[0047] For example, the data storage unit 100 stores relational data that shows the relationship between usage information and the specific content of the suggested settings. The relational data may be in any data format, such as a table format, mathematical formula format, program code, machine learning model, or other format. The presentation unit 102 may refer to the relational data and propose suggested settings that are associated with the usage information. The presentation unit 102 may also propose suggested settings for the values ​​shown in the usage information without using the relational data.

[0048] In this embodiment, the presentation unit 102 proposes a suggested setting to the user based on the highest amount of electronic money used during the most recent predetermined period. The presentation unit 102 identifies the highest amount of usage indicated in the usage information and proposes a post-charge balance equal to or greater than that highest amount to the user as a suggested setting. The highest amount may be the highest amount per transaction, or it may be an additional high amount for the total usage during a predetermined period (for example, one day). The presentation unit 102 may also calculate the average amount of usage during the most recent predetermined period instead of the highest amount and propose a post-charge balance equal to or greater than that average amount as a suggested setting.

[0049] In this embodiment, since the use of payment methods in each of the multiple services is indicated in the usage information, the presentation unit 102 makes presentations to the user according to the use of payment methods in each of the multiple services. Also, since the balance after charging is specified as a specified setting, the presentation unit 102 may make presentations to the user by proposing a suggested balance for the balance of the payment method. That is, the presentation unit 102 may propose a suggested balance as a suggested setting. The suggested balance is the balance after charging that is proposed to the user.

[0050] For example, the presentation unit 102 identifies the highest amount used by the user across multiple services using electronic money and proposes to the user a post-charge balance equal to or greater than that highest amount as a suggested setting. If the electronic money was usable for three services, such as payment services, e-commerce services, and travel booking services, the presentation unit 102 identifies the highest amount used in each of these three services and proposes to the user a post-charge balance equal to or greater than that highest amount as a suggested setting.

[0051] For example, the presentation unit 102 may propose a post-charge balance that is equal to or greater than the highest amount of electronic money usage over the entire past period, rather than the most recent predetermined period. The presentation unit 102 may also propose a balance such that the more frequently electronic money is used, the higher the proposed balance, rather than based on the amount of electronic money used. The number of uses may be the aggregated result of either the most recent predetermined period or the entire past period.

[0052] The presentation unit 102 may also propose to the user the sum of a first amount and a second amount, which are determined according to the usage information, as the proposed balance. For example, the first amount is the maximum amount. The second amount is a predetermined amount. The second amount is the amount added to the first amount. If the maximum amount is 18,000 yen and the second amount is 5,000 yen, the presentation unit 102 may propose the sum of these, 23,000 yen, as the proposed balance. The data indicating the second amount is stored in the data storage unit 100. The presentation unit 102 calculates the proposed balance based on this data. The second amount may be the same for all users, or it may be determined according to the user. For example, the higher the average amount of electronic money used, the higher the second amount may be, or the greater the variation in the amount of electronic money used, the higher the second amount may be.

[0053] Furthermore, the presentation unit 102 may propose a suggested balance based on future usage plans rather than the usage history indicated by the usage information. For example, suppose a user uses electronic money for a financial product's savings plan. In this case, the usage information may indicate the user's future savings amount. The presentation unit 102 may propose a post-charge balance equal to or greater than the user's savings amount as the suggested balance. If the user plans to save for multiple financial products, the usage information may propose a post-charge balance equal to or greater than the sum of the savings amounts for each of the multiple financial products as the suggested balance.

[0054] Furthermore, the presentation unit 102 may propose a suggested balance based on both the usage history indicated by the usage information and the planned usage indicated by the usage information. For example, the presentation unit 102 may propose a post-charge balance that is equal to or greater than the higher of the highest amount identified from the usage history indicated by the usage information and the accumulated amount identified from the planned usage indicated by the usage information. For example, the presentation unit 102 may propose a suggested balance that is the sum of the highest amount identified from the usage history indicated by the usage information and the accumulated amount identified from the planned usage indicated by the usage information. Alternatively, the presentation unit 102 may calculate the sum or average of the said highest amount and said accumulated amount and propose a post-charge balance that is equal to or greater than the calculated value as the suggested balance.

[0055] [Setting Acquisition Section] The setting acquisition unit 103 acquires the specified setting when the presentation unit 102 makes a presentation (for example, when a suggested setting is proposed to the user). When the presentation unit 102 makes a presentation, it means after the presentation has been made. For example, when a suggested setting is proposed to the user, it means after the suggested setting has been proposed to the user. The setting acquisition unit 103 may acquire the specified setting specified on the same screen where the suggested setting was proposed (in the example in the lower left of Figure 2, the setting screen SC3), or it may acquire the specified setting specified on a different screen than the one where the suggested setting was proposed. When the setting acquisition unit 103 acquires the specified setting, it means that the setting acquisition unit 103 acquires data indicating the specified setting.

[0056] For example, the setting acquisition unit 103 acquires the specified setting from the user terminal 20, which is specified by the user. In this embodiment, the setting acquisition unit 103 acquires the specified balance related to the balance of the payment method as the specified setting. The specified balance is the balance after charging, as specified by the user. The setting acquisition unit 103 stores the specified setting in the user database DB. If the specified setting is already stored in the user database DB, the setting acquisition unit 103 updates the specified setting stored in the user database DB. The setting acquisition unit 103 can acquire the specified setting stored in the user database DB at any time.

[0057] Furthermore, if the user does not specify any particular settings, the setting acquisition unit 103 may acquire the suggested settings as the specified settings. Alternatively, for example, if the user chooses to have the settings set automatically, the setting acquisition unit 103 may acquire the suggested settings as the specified settings. In this case, an image for selecting automatic settings will be displayed on the settings screen SC3. The user chooses to have the settings set automatically by selecting this image. The user can then specify the suggested settings as the specified settings with a single tap using this image. For example, if the user selects message M30, the setting acquisition unit 103 may acquire the suggested settings as the specified settings.

[0058] [Auto-charge execution unit] The auto-charge execution unit 104 performs auto-charging based on the specified settings. The method by which the auto-charge execution unit 104 performs auto-charging based on the specified settings may be the same as known auto-charging methods. In this embodiment, since the specified balance is acquired as the specified setting, the auto-charge execution unit 104 performs auto-charging so that the specified balance is maintained. For example, the auto-charge execution unit 104 determines whether the current balance of the electronic money has fallen below the specified balance. If the auto-charge execution unit 104 determines that the current balance of the electronic money has not fallen below the specified balance, it does not perform auto-charging. If it determines that the current balance of the electronic money has fallen below the specified balance, it performs auto-charging so that the balance of the electronic money becomes equal to or greater than the specified balance. The auto-charge execution unit 104 may also perform auto-charging if insufficient balance occurs when a payment is executed.

[0059] [3-2. Functions implemented on the user terminal] For example, the user terminal 20 includes a data storage unit 200, an operation reception unit 201, and a display control unit 202. The data storage unit 200 is implemented by a storage unit 22. The operation reception unit 201 and the display control unit 202 are implemented by a control unit 21.

[0060] [Data Storage Unit] The data storage unit 200 stores the data necessary for the user to use the payment service. For example, the data storage unit 200 stores the payment application. If the user uses the payment service from another application or browser instead of the payment application, the data storage unit 200 stores the other application or browser.

[0061] [Operation Reception Section] The operation reception unit 201 receives various user operations. For example, the operation reception unit 201 receives operations on the payment application. The operation reception unit 201 transmits data indicating the user's operation to the server 10.

[0062] [Display Control Unit] The display control unit 202 displays various screens on the display unit 25. For example, the display control unit 202 displays the top screen SC1, the charge screen SC2, the settings screen SC3, and the completion screen SC4 on the display unit 25. The display control unit 202 communicates with the server 10 to receive display data for these screens and displays these screens on the display unit 25 based on the display data. The display data is the data necessary for displaying the screen. The display data may be data for the entire screen or data for a part of the screen. For example, the display data may be data in a markup language such as HTML, image data, text data, or other data.

[0063] [4. Processes performed by the auto-charge system] Figure 5 shows an example of the process performed by the auto-charge system 1. Figure 5 shows the auto-charge related process among the processes performed by the auto-charge system 1. The control units 11 and 21 execute the programs stored in the memory units 12 and 22, respectively, thereby executing the process shown in Figure 5. The steps in Figure 5 represent an example of an auto-charge method.

[0064] As shown in Figure 5, when the payment application is launched, the user terminal 20 performs a login process with the server 10 to allow the user to log in to the payment service (S1). The user terminal 20 then performs a process with the server 10 to display the top screen SC1 (S2). When the user selects button B11 on the top screen SC1, the user terminal 20 then performs a process with the server 10 to display the charge screen SC2 (S3).

[0065] When the user terminal 20 selects button B22, it sends a request to the server 10 to display the settings screen SC3 (S4). When the server 10 receives the request to display the settings screen SC3 (S5), it retrieves the user ID of the logged-in user or usage information associated with the login account based on the user database DB (S6). Based on the usage information, the server 10 generates display data for the settings screen SC3, including a message M30 indicating the suggested settings, and sends it to the user terminal 20, thereby proposing suggested settings to the user (S7).

[0066] When the user terminal 20 receives display data for the setting screen SC3 from the server 10 (S8), it displays the setting screen SC3 on the display unit 25 (S9). The user terminal 20 accepts the user's specified settings (S10). When the user selects button B32, the user terminal 20 sends a setting request for the specified settings to the server 10 (S11). When the server 10 receives the setting request for the specified settings from the user terminal 20 (S12), it saves the specified settings to the user database DB (S13). The server 10 performs auto-charge based on the specified settings (S14), and this process ends.

[0067] [5. Summary of Embodiments] The auto-charge system 1 of this embodiment acquires usage information regarding the use of electronic money in at least one of a plurality of services. When a user specifies a designated setting, the auto-charge system 1 provides the user with a presentation corresponding to the usage information. When a presentation is made, the auto-charge system 1 acquires the designated setting specified by the user. The auto-charge system 1 performs auto-charging based on the designated setting. As a result, the user can specify the designated setting by referring to the presentation corresponding to the usage information, and the auto-charge system 1 can improve user convenience.

[0068] Furthermore, the auto-charge system 1 presents suggested settings to the user based on usage information. This allows the user to specify their desired settings by referring to the suggested settings, thus enhancing user convenience.

[0069] Furthermore, the auto-charge system 1 acquires usage information regarding the use of payment methods in each of the multiple services. The auto-charge system 1 provides the user with suggestions based on their use of electronic money in each of the multiple services. As a result, the auto-charge system 1 can propose more appropriate settings by providing suggestions that comprehensively consider the use of electronic money in each of the multiple services.

[0070] Furthermore, the auto-charge system 1 presents the user with a suggested balance for the electronic money balance. The auto-charge system 1 acquires the specified balance for the electronic money balance as a specified setting. The auto-charge system 1 performs auto-charging so that the specified balance is maintained. As a result, the user can understand the suggested balance for auto-charges that are performed in a way that maintains the specified balance, and then specify an appropriate balance, thus improving user convenience.

[0071] Furthermore, the auto-charge system 1 proposes to the user a suggested balance, which is the sum of a first amount and a second amount, based on usage information. This allows the user to specify a balance that ensures they have sufficient funds in their electronic money account, and thus the auto-charge system 1 can enable the user to specify a balance that makes it less likely for them to run out of funds.

[0072] [6. Variant] This disclosure is not limited to the embodiments described above. This disclosure may be modified as appropriate without departing from the spirit of this disclosure.

[0073] Figure 6 shows an example of a function realized in a modified version. For example, the server 10 includes a setting history information acquisition unit 105, a change proposal unit 106, an other usage information acquisition unit 107, and a point service information acquisition unit 108. Each of the setting history information acquisition unit 105, the change proposal unit 106, the other usage information acquisition unit 107, and the point service information acquisition unit 108 is realized by the control unit 11.

[0074] [6-1. Variation 1] For example, in the embodiment, the usage information is given as an example where information regarding the use of electronic money in each of multiple services where electronic money is available corresponds to usage information. However, the usage information acquisition unit 101 may acquire usage information regarding the use of electronic money in any of the multiple services. That is, the usage information may be information regarding the use of electronic money in a specific single service.

[0075] In variation 1, we take the example of a case where information regarding the use of electronic money in a payment service provided by a payment app corresponds to usage information. Even if electronic money can be used in other services such as e-commerce services, the usage information does not show information about its use in other services. The usage information stored in the user database DB only shows information about the use of electronic money in the payment service. The usage information may also be information about the use of electronic money in other specific services other than the payment service.

[0076] In Modification 1, the presentation unit 102 presents the user with options based on their use of a payment method in any of the multiple services. For example, the presentation unit 102 proposes suggested settings to the user based on their use of a payment method in any of the multiple services. Based on usage information, the presentation unit 102 identifies the highest amount used in a particular service and proposes a post-charge balance equal to or greater than that highest amount as a suggested setting. Based on usage information, the presentation unit 102 calculates the average amount used in a particular service and proposes a post-charge balance equal to or greater than that average amount as a suggested setting. The presentation unit 102 may also present the amount used for the payment method in any of the multiple services itself, rather than a suggested setting.

[0077] Furthermore, the specific service indicated by the usage information may not be fixed in advance but may be determined dynamically. For example, the usage information acquisition unit 101 may acquire usage information for each of multiple services and then acquire usage information related to the use of a specific service that will be referenced for suggesting the suggested information. The usage information acquisition unit 101 may determine the service with the highest average usage amount as the specific service, or the service with the highest frequency of use as the specific service, or a service with a history of regular use as the specific service (for example, if a user regularly shops at an e-commerce service, the e-commerce service may be determined as the specific service). The presentation unit 102 may acquire the highest or average amount for the dynamically determined service and propose a post-charge balance that is the same as or greater than the highest or average amount as the suggested setting.

[0078] The auto-charge system 1 of Modification 1 acquires usage information regarding the use of electronic money in any of several services. The auto-charge system 1 provides the user with a suggestion based on the use of electronic money in any of the several services. This allows the user to specify settings based on the suggestion based on the use of electronic money in a particular service, thereby improving the user's convenience when using electronic money in a particular service.

[0079] [6-2. Variation 2] For example, in this embodiment, we take the case of transitioning from the charge screen SC2 in the payment service to the settings screen SC3 in the payment service. The settings screen SC3 may also be accessible from services other than the payment service. In Modification 2, we take the case of transitioning from a financial service provided by a securities company to the settings screen SC3 as an example. Hereafter, the service that is the source of the transition to the settings screen SC3 will be referred to as the source service. In Modification 2, we take the example of a case where there are two services that can be source services: the payment service and the financial service. However, the services that can be source services may be other services other than the payment service and the financial service, or there may be three or more.

[0080] Figure 7 shows an example of screen transitions in Modification 2. As shown in Figure 7, in Modification 2, the user can transition to the settings screen SC3 using the financial service as the source service. For example, the user terminal 20 stores the financial app, which is an application for the financial service. When the user terminal 20 launches the financial app, it displays the financial screen SC5, which is used to access the financial service, on the display unit 25. In the example in Figure 7, the financial screen SC5 shows the settings for investment trust accumulation. The financial screen SC5 is displayed by the server computer of the financial service.

[0081] For example, the financial screen SC5 displays a button B50 for specifying the auto-charge settings when electronic money is used for investment trust accumulation. Button B50 includes a link to the payment application settings screen SC3. The link to launch the payment application may be the same as a publicly known link. For example, a link called a deep link may be set for button B50. When the user selects button B50, the user terminal 20 launches the payment application and displays the settings screen SC3 on the display unit 25. The server 10 can identify which service is the source service based on the information of the link indicated by button B50. The screen transition when the payment service is the source service is as explained in Figure 2.

[0082] In the modified example 2, the usage information acquisition unit 101 acquires usage information regarding the use of electronic money in the source service when transitioning from one of the multiple services to the setting screen SC3 which accepts specified settings. The usage information indicates the use of electronic money in the source service, not the use of electronic money in each of the multiple services. For example, the user database DB may store separate usage information for each service, or the use of electronic money in each of the multiple services may be combined into one usage information, and the single usage information may indicate which service the electronic money use is in.

[0083] For example, when the user transitions to the settings screen SC3, the usage information acquisition unit 101 identifies the source service that triggered the display of the settings screen SC3. When the user transitions from the charge screen SC2 to the settings screen SC3, as shown in Figure 2, the usage information acquisition unit 101 identifies the payment service as the source service. In this case, the usage information acquisition unit 101 acquires usage information indicating the use of electronic money in the payment service. When the user transitions from the financial screen SC5 to the settings screen SC3, as shown in Figure 7, the usage information acquisition unit 101 identifies the financial service as the source service. In this case, the usage information acquisition unit 101 acquires usage information indicating the use of electronic money in the financial service.

[0084] In the modified example 2, the presentation unit 102 makes presentations to the user on the settings screen SC3 that correspond to the use of electronic money in the source service. For example, the presentation unit 102 proposes suggested settings to the user on the settings screen SC3 that correspond to the use of electronic money in the source service. The presentation unit 102 identifies the maximum amount of electronic money used in the source service and proposes to the user a post-charge balance equal to or greater than that maximum amount as a suggested setting. The presentation unit 102 identifies the average amount of electronic money used in the source service and proposes to the user a post-charge balance equal to or greater than that average amount as a suggested setting. In the example on the right side of Figure 7, the presentation unit 102 identifies the accumulated amount in the financial service, which is the source service, using usage information and proposes a post-charge balance equal to the accumulated amount as a suggested setting.

[0085] In the modified version 2, the auto-charge system 1 acquires usage information regarding the use of electronic money in the source service when transitioning from one of several services to the settings screen SC3, which accepts specified settings. On the settings screen SC3, the auto-charge system 1 provides the user with suggestions based on their electronic money usage in the source service. This allows the user to refer to suggested settings based on their usage in the source service, thereby improving user convenience. For example, if the source service is a payment service, the user is trying to specify settings based on their usage in the payment service, so the auto-charge system 1 provides suggestions based on their usage in the payment service, allowing the user to refer to suggestions based on the usage for which they are trying to specify settings. If the source service is a financial service, the user is trying to specify settings based on their usage in the financial service, so the auto-charge system 1 provides suggestions based on their usage in the financial service, allowing the user to refer to suggestions based on the usage for which they are trying to specify settings.

[0086] [6-3. Modification 3] For example, in Modification 2, we took the example of a case where suggested settings are proposed based on usage information in the source service, but suggested settings may also be proposed based on usage information in a service other than the source service. The other service is a service other than the source service among several services that can use electronic money. In Modification 3, similar to Modification 2, we take the example of a case where two services, a payment service and a financial service, can be the source service.

[0087] In the modified example 3, the usage information acquisition unit 101 acquires usage information regarding the use of electronic money in a service other than the source service when transitioning from one of multiple services to the setting screen SC3 which accepts specified settings. The usage information acquisition unit 101 acquires usage information regarding the use of a second service other than the first service when the first service among multiple services is the source service. The usage information acquisition unit 101 acquires usage information regarding the use of a financial service, which is another service, when the source service is a payment service. The usage information acquisition unit 101 acquires usage information regarding the use of a payment service, which is another service, when the source service is a financial service.

[0088] In the modified example 3, the presentation unit 102 presents the user on the settings screen SC3 with suggestions based on their use of electronic money in other services. For example, the presentation unit 102 proposes suggested settings to the user on the settings screen SC3 based on their use of electronic money in other services. When the first service among multiple services is the source service, the presentation unit 102 proposes suggested settings based on the usage in the second service. For example, the presentation unit 102 proposes a post-charge balance that is the same as or greater than the highest amount used in the second service as a suggested setting. The presentation unit 102 proposes a post-charge balance that is the same as or greater than the average amount used in the second service as a suggested setting. The presentation unit 102 may also present the amount of electronic money used in other services instead of a suggested setting.

[0089] In the example of Modification 3, if the source service is a payment service, the presentation unit 102 proposes a post-charge balance that is the same as or greater than the highest or average amount used in other services, such as financial services, as a proposed setting.

[0090] In the modified example 3, when transitioning from one of several services to the settings screen SC3, which accepts specified settings, the auto-charge system 1 acquires usage information regarding the use of electronic money in a service other than the source service. On the settings screen SC3, the auto-charge system 1 provides the user with a presentation based on the use of electronic money in the other service. This allows the user to refer to the presentation based on usage in the source service, thereby improving user convenience. For example, if the source service is a payment service, the user can refer to the presentation based on usage in another service, such as a financial service, thus preventing the specified setting from being a post-charge balance that falls below the accumulated amount.

[0091] [6-4. Modification 4] For example, a user may be able to specify auto-charge settings for at least one of several periods. A period is the period to which the specified setting is associated. There is a one-to-one correspondence between periods and specified settings. In variation 4, we take the example of a case where the specified setting is associated with at least one of three periods, such as the beginning, middle, and end of a month, but there may be two periods to which the specified setting is associated, or four or more. Also, the specified setting may be associated with all of the multiple periods, or with only some of the multiple periods. The length of each individual period may be different from each other, or the same from each other. For example, within a given month, there may be multiple periods, such as the period during which the financial service is accumulated and the rest of the month.

[0092] Figure 8 shows an example of a designated setting associated with at least one of multiple periods in Modification 4. The usage information acquisition unit 101 in Modification 4 acquires usage information regarding the use of electronic money in at least one of multiple periods. In the example in Figure 8, there are three periods: early, mid, and late in the month, so the usage information acquisition unit 101 acquires usage information regarding the use of electronic money in at least one of the early, mid, and late periods. That is, the usage information acquisition unit 101 acquires usage information showing usage for each period. The usage information acquisition unit 101 may acquire usage information for all of the multiple periods such as early, mid, and late in the month, or it may acquire usage information for only some of the periods.

[0093] In the modified example 4, the presentation unit 102 provides the user with suggestions based on their electronic money usage during at least one of several periods. For example, the presentation unit 102 proposes suggested settings to the user based on their electronic money usage during at least one of several periods. The presentation unit 102 proposes suggested settings for each period based on the electronic money usage during that period. The presentation unit 102 proposes a post-charge balance equal to or greater than the highest or average amount of electronic money used in the first half of the month as the suggested setting for the first half of the month. The presentation unit 102 proposes a post-charge balance equal to or greater than the highest or average amount of electronic money used in the middle of the month as the suggested setting for the middle of the month. The presentation unit 102 proposes a post-charge balance equal to or greater than the highest or average amount of electronic money used in the last half of the month as the suggested setting for the last half of the month. The presentation unit 102 may also present the amount of electronic money used in at least one of the first, middle, and last half of the month instead of suggested settings.

[0094] In the example shown in Figure 8, the display unit 102 suggests the settings for the first half of the month by displaying message M30A on the settings screen SC3, indicating that the highest amount of electronic money usage in the first half of the month is 8,000 yen. The user then enters the specified settings for the first half of the month into the input form F31A, referring to message M30A. The display unit 102 suggests the settings for the first half of the month by displaying message M30B on the settings screen SC3, indicating that the highest amount of electronic money usage in the middle of the month is 12,000 yen. The user then enters the specified settings for the middle of the month into the input form F31B, referring to message M30B. The display unit 102 suggests the settings for the first half of the month by displaying message M30C on the settings screen SC3, indicating that the highest amount of electronic money usage in the latter half of the month is 7,000 yen. The user, referring to message M30C, enters the specified settings for the latter half of the month into input form F31C. The user may enter the specified settings into all of input forms F31A to F31C, or into any one or two of input forms F31A to F31C.

[0095] In the modified example 4, the setting acquisition unit 103 acquires the specified settings for at least one of a plurality of periods. For example, the setting acquisition unit 103 acquires the specified settings for at least one of the early, middle, and late months of the month and stores them in the user database DB. The auto-charge execution unit 104 performs auto-charging for at least one of the plurality of periods based on the specified settings for that period. For example, the auto-charge execution unit 104 performs auto-charging for the early month based on the specified settings for the early month. The auto-charge execution unit 104 performs auto-charging for the middle month based on the specified settings for the middle month. The auto-charge execution unit 104 performs auto-charging for the late month based on the specified settings for the late month.

[0096] In variation 4, the user can specify auto-charge settings for at least one of multiple periods. The auto-charge system 1 acquires usage information regarding the use of electronic money for at least one of multiple periods. The auto-charge system 1 proposes suggested settings to the user based on the use of electronic money for at least one of multiple periods. This allows the user to specify settings for each period, thereby improving user convenience.

[0097] [6-5. Variation 5] For example, auto-charging may be performed when a predetermined charging timing occurs. The charging timing is the timing at which the auto-charging execution unit 104 determines whether or not to perform auto-charging. The auto-charging timing may be a predetermined date and time (for example, a specific time within a day), or it may be the timing at which a specific event occurs, such as when a payment is completed in a payment application. The charging timing data indicating the charging timing is pre-stored in the data storage unit 100. The auto-charging execution unit 104 should identify the auto-charging timing based on this data.

[0098] In Modification 5, the auto-charge execution unit 104 may perform auto-charge at a charge timing corresponding to the source service that transitions to the setting screen SC3 which accepts specified settings, among multiple services. The meaning of the source service is as explained in Modification 2. The auto-charge execution unit 104 obtains the current date and time using a real-time clock or GPS, etc., and determines whether or not the charge timing has arrived. If the auto-charge execution unit 104 determines that the charge timing has arrived, it performs auto-charge.

[0099] Figure 9 shows an example of the relationship between the source service and the charging timing. The relationship in Figure 9 is an example of charging timing data. In the example in Figure 9, if the source service is a payment service, the charging timing is assumed to be once a day. If the source service is a financial service, in addition to once a day, a charging timing of once every hour is set during the period when accumulation takes place (for example, from the 13th to the 15th of each month). The auto-charge execution unit 104 determines whether or not a charging timing has arrived based on the charging timing data and executes auto-charge.

[0100] For example, server 10 may refer to charge timing data and store the charge timing associated with the source service as a specified setting in the user database DB. The auto-charge execution unit 104 performs auto-charging based on the charge timing indicated in the specified setting. Server 10 may also store information that can identify the destination service in the user database DB, and the auto-charge execution unit 104 performs auto-charging based on this information and the charge timing data.

[0101] The auto-charge system 1 in Modification 5 executes auto-charge at a timing corresponding to the source service that transitions to the settings screen accepting specified settings, among multiple services. As a result, the auto-charge system 1 executes auto-charge at a timing corresponding to the source service, thereby improving user convenience. For example, in the example in Figure 9, if a financial service is used for monthly deposits between the 13th and 15th, the auto-charge system 1 can prevent deposit orders from failing due to insufficient funds by increasing the frequency of auto-charges during this period compared to other periods.

[0102] [6-6. Variation 6] For example, suggested settings may be made based on the user's specified settings history. The auto-charge system 1 of Modification 6 includes a setting history information acquisition unit 105. The setting history information acquisition unit 105 acquires setting history information regarding the history of specified settings. For example, the user database DB stores the setting history information. Each time a user updates a specified setting, the server 10 updates the setting history information to show the result of the user's specified setting update. The setting history information may be stored in a database other than the user database DB, another computer other than the server 10, or an information storage medium. The setting history information acquisition unit 105 may acquire usage information from other databases, other computers, or information storage media.

[0103] Figure 10 shows an example of the settings screen SC3 where suggested settings are proposed based on the setting history information. In the modified example 6, the presentation unit 102 makes presentations to the user based on the setting history information. For example, the presentation unit 102 proposes suggested settings to the user based on the setting history information. The presentation unit 102 proposes the higher of the highest or average amount identified by the usage information and the highest or average amount of the post-charge balance indicated by the setting history information as the suggested setting. In the example in Figure 10, the presentation unit 102 proposes the highest amount of the post-charge balance previously specified by the user as the suggested setting. The presentation unit 102 may also propose a setting selected randomly from the history indicated by the setting history information as the suggested setting.

[0104] Furthermore, the presentation unit 102 may present the user with the setting history information itself, rather than proposing suggested settings. The presentation unit 102 may also present the information by displaying the setting history in the second service when the user is configuring from the first service. In other words, the presentation unit 102 may display the setting history in the second service itself, rather than proposing suggested settings.

[0105] The auto-charge system 1 in Modification 6 acquires setting history information regarding the history of specified settings. The auto-charge system 1 then provides information to the user based on the setting history information. As a result, the user can refer to the information provided according to their specified setting history, thus improving user convenience.

[0106] In modification 6, the presentation unit 102 may make presentations based on setting history information rather than on usage information. In this case, the server 10 does not need to include the usage information acquisition unit 101. The presentation unit 102 may propose one of the contents of past specified settings indicated by the setting history information as a suggested setting, or it may propose the average value of the post-charge balance of multiple past specified settings indicated by the setting history information as a suggested setting. The presentation unit 102 may also make presentations by displaying the setting history information itself instead of a suggested setting. Even if the presentation unit 102 makes presentations based on setting history information rather than on usage information, the user can still specify settings by referring to the presentations, thus solving the problem of improving user convenience. For this reason, a configuration in which the presentation unit 102 makes presentations based on setting history information rather than on usage information is also within the scope of this disclosure.

[0107] [6-7. Variation 7] For example, several specified amounts that can serve as candidates for the proposed balance may be predetermined. The specified amount data indicating the multiple specified amounts is pre-stored in the data storage unit 100. The multiple specified amounts may be any amount, for example, integer multiples of a predetermined amount. In Modification 7, the case where the specified amount is an integer multiple of 5,000 yen is given as an example. In Modification 7, the presentation unit 102 proposes to the user a specified amount from among the multiple specified amounts that corresponds to the usage information as the proposed balance. The amount corresponding to the usage information is an amount determined based on the usage amount indicated by the usage information. For example, the amount corresponding to the usage information is the highest amount or the average amount. The presentation unit 102 may propose the specified amount that is closest to the amount corresponding to the usage information. The presentation unit 102 may propose the closest specified amount among the specified amounts that are greater than or equal to the amount corresponding to the usage information. For example, suppose the specified amounts are 10,000 yen, 20,000 yen, and 30,000 yen, and the amount corresponding to the usage information is 12,000 yen. In this case, numerically the closest amount is 10,000 yen, but the offering unit 102 may propose 20,000 yen, which is the closest amount among the specified amounts of 12,000 yen or more.

[0108] Figure 11 shows an example of the setting screen SC3 in Modification 7. For example, the presentation unit 102 calculates the highest or average amount for the user over the most recent predetermined period, in the same manner as in the embodiment. In Modification 7, the presentation unit 102 identifies the specified amount that is closest to the calculated highest or average amount from among a plurality of specified amounts. If there are two specified amounts that are closest to the highest or average amount, the presentation unit 102 only needs to identify the higher or lower of the two specified amounts. The presentation unit 102 proposes the identified specified amount as the proposed balance.

[0109] In the example in Figure 11, multiple specified amounts are defined as integer multiples of 5,000 yen. For example, if the highest amount identified by the presentation unit 102 is 18,000 yen, the closest specified amount is 20,000 yen. As shown in Figure 11, the presentation unit 102 proposes button B33, which indicates 20,000 yen, the specified amount closest to the highest amount identified based on the usage information, as the proposed balance. The presentation unit 102 may also propose a specified amount as the proposed setting that is closest to the sum of the first value and the second value described in the embodiment. For example, if the first value is the highest amount of 18,000 yen and the second value is 5,000 yen, the presentation unit 102 may propose 25,000 yen, the specified amount closest to the sum of these two values, 23,000 yen, as the proposed balance.

[0110] For example, if the average amount identified by the presentation unit 102 is 7,500 yen, the closest specified amounts are 5,000 yen and 10,000 yen. The presentation unit 102 proposes either 5,000 yen or 10,000 yen, which are the specified amounts closest to the average amount identified based on the usage information, as the proposed balance. If the first value described in the embodiment is the average amount of 7,500 yen and the second value is 5,000 yen, the presentation unit 102 may propose either 10,000 yen or 15,000 yen, which are the specified amounts closest to the sum of these two amounts, 12,500 yen, as the proposed balance.

[0111] The presentation unit 102 may also propose the amount closest to the amount corresponding to the usage information from among multiple specified amounts equal to or greater than the amount corresponding to the usage information as the proposed balance. For example, if the highest amount identified by the presentation unit 102 is 16,000 yen, then the amount closest to the highest amount from among multiple specified amounts equal to or greater than that highest amount is 20,000 yen. The presentation unit 102 proposes 20,000 yen, which is the amount closest to the highest amount from among multiple specified amounts equal to or greater than the highest amount, as the proposed balance. The specified amount of 15,000 yen has the smallest difference from the highest amount of 16,000 yen, but since it is less than the highest amount, it is not proposed as the proposed balance. The same may apply when the average amount is used as the amount corresponding to the usage information, and when the sum of the first and second values ​​is used.

[0112] In the example shown in Figure 11, the user can specify the suggested setting as the designated setting without having to enter a numerical value in the input form F31 by selecting button B33. The setting acquisition unit 103 acquires the suggested setting as the designated setting when the user selects button B33. The user can also enter a numerical value unrelated to the specified amount in the input form F31. In this case, the setting acquisition unit 103 acquires the numerical value entered in the input form F31 as the designated setting. If the user selects a specified amount different from the suggested setting, the setting acquisition unit 103 may acquire the specified amount selected by the user as the designated setting.

[0113] In the modified version 7, the auto-charge system 1 proposes a predetermined amount to the user as a suggested balance, based on usage information, from among several predetermined amounts. This allows the auto-charge system 1 to propose a convenient, rounded balance.

[0114] [6-8. Variation 8] For example, depending on a user's electronic money usage history, the settings specified by the user may not be appropriate. Suppose a user specifies a balance of 10,000 yen as an example of their settings. Later, the user manually tops up their balance via the SC2 top-up screen and makes a purchase of 20,000 yen. In this case, the appropriate balance for the user might be 20,000 yen, not the 10,000 yen they specified. Therefore, in such cases, the user may be offered the option to change their settings.

[0115] The auto-charge system 1 of Modification 8 includes a change suggestion unit 106. The change suggestion unit 106 suggests changes to the specified settings to the user based on the user's electronic money usage history and the specified balance. The electronic money usage history is shown in the usage information after the user has specified the specified balance. The change suggestion unit 106 determines whether or not to suggest changes to the specified settings based on the usage history after a user has specified the specified balance and the specified balance specified by that user. If the change suggestion unit 106 determines that it does not want to suggest changes to the specified settings, it does not suggest changes to the specified settings; if it determines that it does want to suggest changes to the specified settings, it suggests changes to the specified settings.

[0116] Figure 12 shows an example of how a change to the specified setting is proposed in Modification Example 8. For example, the change proposal unit 106 identifies the maximum amount of electronic money used by the user after they have specified the specified setting, based on the usage information. The change proposal unit 106 determines whether the maximum amount is greater than or equal to the specified setting. If the change proposal unit 106 determines that the maximum amount is less than or equal to the specified setting, it does not propose a change to the specified setting; otherwise, it proposes a change to the specified setting.

[0117] In the example in Figure 12, the user's specified setting is 10,000 yen, and the user's maximum spending limit is 20,000 yen. Therefore, the change suggestion unit 106 suggests to the user that they change their specified setting. For example, the change suggestion unit 106 sends an email M to the user's email address indicating a change to the specified setting. Email M may include the suggested setting. In the example in Figure 12, the user's maximum spending limit of 20,000 yen is included as the suggested setting. As explained in the embodiment, the sum of the maximum amount (an example of the first amount) and the second amount may be included as the suggested setting in email M. When the user selects a link in email M, the user terminal 20 displays the setting screen SC3 on the display unit 25.

[0118] The method by which the change proposal unit 106 proposes changes to the specified settings is not limited to the example in Figure 12. The change proposal unit 106 may propose changes to the specified settings by means other than email M. For example, the change proposal unit 106 may propose changes to the specified settings to the user through a screen such as the top screen SC1 of the payment application, a window, a pop-up, a modal, or a banner. The change proposal unit 106 may also propose changes to the specified settings to the user through the notification function of the user terminal 20 itself, SMS, a messaging application, SNS, or other means.

[0119] The auto-charge system 1 in modified version 8 suggests to the user a change in their specified settings based on the user's electronic money usage history and the specified balance. This allows the user to realize that their current specified settings may not be appropriate, thus improving user convenience.

[0120] [6-9. Modification 9] For example, in the embodiment, a case was given in which suggested settings are proposed based on usage information of electronic money subject to auto-charge. However, suggested settings may also be proposed based not only on electronic money usage information, but also on other usage information related to the use of other payment methods other than electronic money. In Modification 9, a credit card is described as an example of another payment method. The other payment method may be any payment method and is not limited to a credit card. The other payment method may be other electronic money, a balance not called electronic money, a card other than a credit card, points, a bank account, an account other than a bank account, cryptocurrency, or a wallet. The other payment method may also be a payment method set as the source of payment or charge.

[0121] The auto-charge system 1 of Modification 9 includes an other usage information acquisition unit 107. The other usage information acquisition unit 107 acquires other usage information relating to the use of other payment methods related to electronic money. The other usage information is information that shows at least one of the usage history and planned usage of other payment methods. The other usage information may show only the usage history, only the planned usage, or both the usage history and planned usage. The server 10 acquires the individual information contained in the other usage information from at least one of the computer that manages the other payment methods and stores the other usage information in the user database DB. If the other payment method is a credit card, the other usage information may be the amount used by the credit card, the remaining amount of the credit limit, the installment payment amount, the revolving payment amount, the bonus payment amount, the cash advance amount, the remaining amount of the cash advance limit, or other information.

[0122] In the modified example 9, the case where other usage information is stored in the user database DB is given as an example. The other usage information acquisition unit 107 acquires other usage information from the user database DB. For example, the other usage information acquisition unit 107 acquires other usage information from the other usage information stored in the user database DB that is associated with the user ID or login account of a user who is logged into the payment service. Other usage information may be stored in a database other than the user database DB, a computer other than the server 10, or an information storage medium. The other usage information acquisition unit 107 may acquire other usage information from a database, a computer, or an information storage medium.

[0123] In Modification 9, the presentation unit 102 provides the user with suggestions based on other usage information, corresponding to the use of other electronic money. For example, the presentation unit 102 proposes suggested settings to the user based on other usage information. Suppose the other payment method is a credit card set as the source of the electronic money charge. In this case, if the specified setting is a balance after charging that is greater than the remaining credit limit of the credit card, the credit limit may be insufficient and the auto-charge may fail. For this reason, the presentation unit 102 may propose suggested settings within the range of the remaining credit limit indicated by the other usage information. For example, the presentation unit 102 may propose the lower of the maximum or average amount of electronic money identified in the same manner as in the embodiment, and the remaining credit limit indicated by the other usage information, as the suggested setting. The presentation unit 102 may also present the amount indicated by the other usage information itself, rather than proposing suggested settings.

[0124] The auto-charge system 1 in Modification 9 acquires other usage information regarding the use of other payment methods related to electronic money. Based on this other usage information, the auto-charge system 1 provides the user with suggestions corresponding to the use of other electronic money. This allows the auto-charge system 1 to provide suggestions that take into account not only the electronic money subject to auto-charge, but also the use of other payment methods, thereby improving user convenience. For example, the auto-charge system 1 can prevent situations where it would show a suggestion that the credit limit of the credit card set as the charging source is insufficient.

[0125] [6-10. Variation 10] For example, in this embodiment, the balance after charging was described as an example of a suggested setting and a specified setting, but the suggested setting and the specified setting can be any setting related to auto-charging, and are not limited to the balance after charging. In Modification 10, the activation conditions for activating auto-charging are described as another example of a suggested setting and a specified setting. The activation condition is the condition for whether or not to perform auto-charging. The activation condition can also be called the timing or trigger of auto-charging. The activation condition may be a time-based condition or a condition related to the balance of the electronic money. Hereafter, the activation condition as a suggested setting will be called the suggested activation condition. The activation condition as a specified setting will be called the specified activation condition.

[0126] Figure 13 shows an example of the settings screen SC3 in modified example 10. As shown in Figure 13, the presentation unit 102 of modified example 10 presents information to the user by proposing proposed activation conditions for activating auto-charge. For example, the presentation unit 102 identifies the date and time when the use of electronic money is scheduled based on usage information. The presentation unit 102 proposes that date and time or an earlier date and time as a proposed activation condition. The presentation unit 102 may also identify the date and time when electronic money is frequently used (for example, the time period when the number of uses in the most recent predetermined period exceeds a threshold) and propose that date and time or an earlier date and time as a proposed activation condition.

[0127] For example, the suggestion unit 102 may suggest a suggestion activation condition once per first period (e.g., one month) to users who tend to use electronic money in large amounts per transaction (for example, users whose transaction amount is above a threshold and who are expected to purchase multiple items at once). The suggestion unit 102 may also suggest a suggestion activation condition once per second period (e.g., daily) which is shorter than the first period, to users who tend to use electronic money in small amounts per transaction (for example, users whose transaction amount is below a threshold and who are expected to purchase items frequently). In this way, the suggestion unit 102 may suggest suggestion activation conditions according to the frequency of use indicated by the usage information.

[0128] In the example shown in Figure 13, the presentation unit 102 suggests the activation conditions by displaying a message M33 on the settings screen SC3 indicating that the charge timing should be set before the deposit date, since the deposit date is identified by the financial service usage information. The settings screen SC3 includes an input form F34 that accepts the specification of the specified activation conditions. In the modified example 10, the setting acquisition unit 103 acquires the specified activation conditions related to the activation of auto-charge as specified settings. For example, the setting acquisition unit 103 acquires the specified activation conditions specified by the user in the input form F34 from the user terminal 20. The setting acquisition unit 103 stores the acquired specified activation conditions in the user database DB.

[0129] In the modified version 10, the auto-charge execution unit 104 performs auto-charging based on specified activation conditions. For example, the auto-charge execution unit 104 obtains the current date and time using a real-time clock or GPS, etc., and determines whether the date and time indicated by the specified activation conditions has arrived. If the auto-charge execution unit 104 determines that the date and time indicated by the specified activation conditions has not arrived, it does not perform auto-charging. If it determines that the date and time indicated by the specified activation conditions has arrived, it performs auto-charging. If the specified activation conditions are not time-based conditions but conditions related to the balance of the electronic money, the auto-charge execution unit 104 can determine whether the specified activation conditions have been met by determining whether the current balance of the electronic money has reached the balance indicated by the specified activation conditions, and then perform auto-charging.

[0130] The auto-charge system 1 of variation 10 presents the user with suggested activation conditions for auto-charging. The auto-charge system 1 acquires the specified activation conditions for auto-charging as specified settings. The auto-charge system 1 performs auto-charging based on the specified activation conditions. As a result, the user can specify the specified activation conditions by referring to the suggested activation conditions according to the usage information, thus improving the convenience of the user in specifying the specified activation conditions.

[0131] [6-11. Variation 11] For example, in the embodiment, a case was given in which suggested settings are proposed based on usage information of electronic money subject to auto-charge. However, suggested settings may also be proposed based not only on electronic money usage information, but also on point service information regarding the use of point services that manage points that can be used in conjunction with electronic money. Point service information is information that shows at least one of the usage history and planned usage of the point service. Point service information may show only the usage history, only the planned usage, or both the usage history and planned usage.

[0132] The auto-charge system 1 of modification 11 includes a point service information acquisition unit 108. The point service information acquisition unit 108 acquires point service information regarding the use of point services by users. The server 10 acquires point service information from the computer that manages the point services and stores the point service information in the user database DB. For example, the point service information may include point balance, login history to the point services, date and time of presentation of the point card, amount of points used, date and time of use, store used, or other information.

[0133] Modification 11 takes the case where point service information is stored in the user database DB as an example. The point service information acquisition unit 108 acquires point service information from the user database DB. For example, the point service information acquisition unit 108 acquires point service information associated with the user ID or login account of a user who is logged into the payment service from the point service information stored in the user database DB. The point service information may also be stored in a database other than the user database DB, a computer other than the server 10, or an information storage medium. The point service information acquisition unit 108 may acquire point service information from a database other than the user database DB, a computer other than the server 10, or an information storage medium.

[0134] In Modification 11, the presentation unit 102 makes presentations to the user based on the point service information. For example, the presentation unit 102 proposes suggested settings to the user based on the point service information. When a user makes a payment using both electronic money and points, if the point balance is large, there may be no problem with payment even if the electronic money balance is small. For this reason, the presentation unit 102 may propose a suggested balance such that the suggested balance decreases as the point balance indicated by the point service information increases. The presentation unit 102 may also propose a suggested balance such that the suggested balance increases as the point balance indicated by the point service information decreases. The presentation unit 102 may also present the amount indicated by the point service information itself, rather than a suggested setting.

[0135] For example, if a user does not usually use point services, electronic money payments may become the primary method of payment. For this reason, the presentation unit 102 may propose a suggested balance such that the less the amount used as indicated by the point service information, the higher the suggested balance. The presentation unit 102 may propose a suggested balance such that the more the amount used as indicated by the point service information, the lower the suggested balance. The presentation unit 102 may propose a suggested balance such that the less the number of times the point card is presented as indicated by the point service information, the higher the suggested balance. The presentation unit 102 may propose a suggested balance such that the more the number of times the point card is presented as indicated by the point service information, the lower the suggested balance.

[0136] The auto-charge system 1 of the modified version 11 acquires point service information regarding the user's use of the point service. The auto-charge system 1 then makes a presentation to the user based on the point service information. As a result, the user can refer to the presentation according to the point service information, and the auto-charge system 1 can effectively enhance user convenience.

[0137] In modification 11, the presentation unit 102 may make a presentation based on point service information rather than on usage information. In this case, the server 10 does not need to include the usage information acquisition unit 101. The presentation unit 102 may propose an amount calculated from the point service information as a suggested setting, or it may present the amount indicated by the point service information itself. Even if the presentation unit 102 makes a presentation based on the point service rather than on usage information, the user can specify the setting by referring to the presentation, thus solving the problem of improving user convenience. For this reason, a configuration in which the presentation unit 102 makes a presentation based on point service information rather than on usage information is also within the scope of this disclosure.

[0138] [6-12. Variation 12] For example, as explained to some extent in Modification 2, the auto-charge setting may be specified from each of multiple services. In Modification 12, it is assumed that the setting can be specified from both the payment service and the financial service similar to that in Modification 2. In this case, when the setting is specified from the financial service, the setting specified from the payment service may be taken into consideration when proposing the suggested setting.

[0139] Figure 14 shows an example of the settings screen SC3 in Modification 12. As shown in Figure 14, the presentation unit 102 of Modification 12 may present to the user the case in which a specified setting is specified from a second service different from the first service, based on the auto-charge settings already set in the first service, which is one of the multiple services. For example, the presentation unit 102 may propose to the user a suggested setting in which a specified setting is specified from a second service different from the first service, based on the auto-charge settings already set in the first service. The presentation unit 102 may propose a suggested setting that is the sum of the post-charge balance indicated by the specified setting specified by the user from the first service and the amount to be used indicated by the usage information in the second service, or a post-charge balance greater than or equal to that sum. The presentation unit 102 may also present the auto-charge settings already set in the first service themselves, instead of a suggested setting.

[0140] In the example in Figure 14, the payment service corresponds to the first service, and the financial service corresponds to the second service. For example, if the user specifies a balance after charging of 20,000 yen as a setting from the payment service, then 20,000 yen will be shown as the setting in the user database DB. When the user specifies a setting from the financial service, the presentation unit 102 may propose a balance after charging of 30,000 yen, which is the amount obtained by adding 10,000 yen that is scheduled to be deposited in the financial service, based on the setting specified from the payment service, as a suggested setting.

[0141] The auto-charge system 1 of the modified version 12 provides the user with a notification when a specified setting is to be made from a second service that is different from the first service, based on the auto-charge settings already made in the first service, which is one of several services. As a result, when the user makes a specified setting from the second service, they can refer to the notification corresponding to the specified setting already made in the first service, and the auto-charge system 1 can improve user convenience.

[0142] [6-13. Other variations] For example, the above variations may be combined.

[0143] For example, the functions described as being implemented on server 10 may be implemented on user terminal 20 or other computers. The functions described as being implemented on server 10 may be shared among multiple computers.

[0144] [7. Addendum] For example, the auto-charge system 1 can also be configured as follows:

[0145] (1) A payment method that enables automatic charging, comprising a usage information acquisition unit that acquires usage information regarding the use of the payment method in at least one of multiple services, When the user specifies the settings for the auto-charge setting, the display unit presents the user with information corresponding to the usage information. When the above presentation is made, a setting acquisition unit acquires the specified setting specified by the user, An auto-charge execution unit that performs the auto-charge based on the specified settings, An auto-charge system including this. (2) The presentation unit makes the presentation by presenting the user with suggested settings regarding the auto-charge settings based on the usage information. (1) The auto-charge system described above. (3) The usage information acquisition unit acquires the usage information relating to the use of the payment method in each of the plurality of services, The presentation unit presents to the user the presentation corresponding to the use of the payment method in each of the multiple services. The auto-charge system described in (1) or (2). (4) The usage information acquisition unit acquires the usage information relating to the use of the payment method in any of the multiple services, The presentation unit makes the presentation to the user according to the use of the payment method in any of the multiple services. The auto-charge system described in any of (1) to (3). (5) When transitioning from one of the multiple services to a setting screen that accepts the specified settings, the usage information acquisition unit acquires the usage information regarding the use of the payment method in the transition service. The display unit, in the settings screen, displays to the user the display corresponding to the use of the payment method in the source service. (4) The auto-charge system described above. (6) When transitioning from one of the multiple services to a setting screen that accepts the specified settings, the usage information acquisition unit acquires the usage information regarding the use of the payment method in a service other than the source service. The display unit, in the settings screen, displays to the user the display corresponding to the use of the payment method in the other service. The auto-charge system described in (4) or (5). (7) The user can specify the auto-charge settings for at least one of multiple periods, The usage information acquisition unit acquires the usage information relating to the use of the payment method during at least one of the plurality of periods. The presentation unit provides the user with the presentation corresponding to the use of the payment method during at least one of the multiple periods. An auto-charge system as described in any of (1) to (6). (8) The auto-charge execution unit executes the auto-charge at a charging timing corresponding to the source service that is the source of the transition to the setting screen that accepts the specified settings, among the multiple services. The auto-charge system described in any of (1) to (7). (9) The auto-charge system further includes a setting history information acquisition unit that acquires setting history information relating to the history of the specified settings, The presentation unit further presents the user with the setting history information. An auto-charge system as described in any of (1) to (8). (10) The presentation unit makes the presentation by proposing a suggested balance regarding the balance of the payment method to the user. The setting acquisition unit acquires the specified balance relating to the balance of the payment method as the specified setting. The auto-charge execution unit performs the auto-charge so that the specified balance is maintained. The auto-charge system described in any of (1) to (9). (11) The presentation unit proposes to the user the sum of a first amount and a second amount corresponding to the usage information, as the proposed balance. (10) The auto-charge system described above. (12) The presentation unit proposes to the user, from among a plurality of predetermined amounts, the predetermined amount corresponding to the usage information, as the proposed balance. The auto-charge system described in (10) or (11). (13) The auto-charge system further includes a change suggestion unit that proposes changes to the specified settings to the user based on the user's usage history of the payment method and the specified balance. The auto-charge system described in any of (10) to (12). (14) The auto-charge system further includes an other-use information acquisition unit that acquires other-use information regarding the use of other payment methods related to the payment method, The display unit, based on the other usage information, displays to the user the display corresponding to the use of the other payment method. The auto-charge system described in any of (1) to (13). (15) The presentation unit makes the presentation by proposing to the user the proposed activation conditions for the activation of the auto-charge. The setting acquisition unit acquires the specified activation conditions for the activation of the auto-charge as the specified setting. The auto-charge execution unit executes the auto-charge based on the specified activation conditions. The auto-charge system described in any of (1) to (14). (16) The auto-charge system further includes a point service information acquisition unit that acquires point service information regarding the use of point services by the user, The display unit further displays the information to the user based on the point service information. The auto-charge system described in any of (1) to (15). (17) The presentation unit, based on the auto-charge settings already configured in the first service, which is one of the multiple services, presents to the user when the specified settings are specified from a second service different from the first service. The auto-charge system described in any of (1) to (16). [Explanation of symbols]

[0146] 1 Auto-charge system, 10 Server, 11,21 Control unit, 12,22 Storage unit, 13,23 Communication unit, 20 User terminal, 24 Operation unit, 25 Display unit, 100 Data storage unit, 101 Usage information acquisition unit, 102 Presentation unit, 103 Setting acquisition unit, 104 Auto-charge execution unit, 105 Setting history information acquisition unit, 106 Change proposal unit, 107 Other usage information acquisition unit, 108 Point service information acquisition unit, 200 Data storage unit, 201 Operation reception unit, 202 Display control unit, B11,B22,B32,B50 Buttons, DB User database, F20,F31,F32 Input form, M30 Message, P21 Panel, SC1 Top screen, SC2 Charge screen, SC3 Settings screen, SC4 Completion screen, SC5 Financial screen, T10 Tab, M Email, N Network.

Claims

1. A payment method that enables automatic charging, comprising a usage information acquisition unit that acquires usage information regarding the use of the payment method in at least one of multiple services, When the user specifies the settings for the auto-charge setting, the display unit presents the user with information corresponding to the usage information. When the above presentation is made, a setting acquisition unit acquires the specified setting specified by the user, An auto-charge execution unit that performs the auto-charge based on the specified settings, An auto-charge system including this.

2. The presentation unit makes the presentation by presenting the user with suggested settings regarding the auto-charge settings based on the usage information. The auto-charge system according to claim 1.

3. The usage information acquisition unit acquires the usage information relating to the use of the payment method in each of the plurality of services, The presentation unit presents to the user the presentation corresponding to the use of the payment method in each of the multiple services. The auto-charge system according to claim 1 or 2.

4. The usage information acquisition unit acquires the usage information relating to the use of the payment method in any of the multiple services, The presentation unit makes the presentation to the user according to the use of the payment method in any of the multiple services. The auto-charge system according to claim 1 or 2.

5. When transitioning from one of the multiple services to a setting screen that accepts the specified settings, the usage information acquisition unit acquires the usage information regarding the use of the payment method in the transition service. The display unit, in the settings screen, displays to the user the display corresponding to the use of the payment method in the source service. The auto-charge system according to claim 4.

6. When transitioning from one of the multiple services to a setting screen that accepts the specified settings, the usage information acquisition unit acquires the usage information regarding the use of the payment method in a service other than the source service. The display unit, in the settings screen, displays to the user the display corresponding to the use of the payment method in the other service. The auto-charge system according to claim 4.

7. The user can specify the auto-charge setting for at least one of multiple periods. The usage information acquisition unit acquires the usage information relating to the use of the payment method during at least one of the plurality of periods. The presentation unit provides the user with the presentation corresponding to the use of the payment method during at least one of the plurality of periods. The auto-charge system according to claim 1 or 2.

8. The auto-charge execution unit executes the auto-charge at a charging timing corresponding to the source service that is the source of the transition to the setting screen that accepts the specified settings, among the multiple services. The auto-charge system according to claim 1 or 2.

9. The auto-charge system further includes a setting history information acquisition unit that acquires setting history information relating to the history of the specified settings, The presentation unit further presents the user with the setting history information. The auto-charge system according to claim 1 or 2.

10. The presentation unit makes the presentation by proposing a suggested balance regarding the balance of the payment method to the user. The setting acquisition unit acquires the specified balance relating to the balance of the payment method as the specified setting. The auto-charge execution unit performs the auto-charge so that the specified balance is maintained. The auto-charge system according to claim 1 or 2.

11. The presentation unit proposes to the user the sum of a first amount and a second amount corresponding to the usage information, as the proposed balance. The auto-charge system according to claim 10.

12. The presentation unit proposes to the user, from among a plurality of predetermined amounts, the predetermined amount corresponding to the usage information, as the proposed balance. The auto-charge system according to claim 10.

13. The auto-charge system further includes a change suggestion unit that proposes changes to the specified settings to the user based on the user's usage history of the payment method and the specified balance. The auto-charge system according to claim 10.

14. The auto-charge system further includes an other-use information acquisition unit that acquires other-use information regarding the use of other payment methods related to the payment method, The display unit, based on the other usage information, displays to the user the display corresponding to the use of the other payment method. The auto-charge system according to claim 1 or 2.

15. The presentation unit makes the presentation by proposing to the user the proposed activation conditions for the activation of the auto-charge. The setting acquisition unit acquires the specified activation conditions for the activation of the auto-charge as the specified setting. The auto-charge execution unit executes the auto-charge based on the specified activation conditions. The auto-charge system according to claim 1 or 2.

16. The auto-charge system further includes a point service information acquisition unit that acquires point service information regarding the use of point services by the user, The display unit further displays the information to the user based on the point service information. The auto-charge system according to claim 1 or 2.

17. The presentation unit, based on the auto-charge settings already configured in the first service, which is one of the plurality of services, presents to the user when the specified settings are specified from a second service different from the first service. The auto-charge system according to claim 1 or 2.

18. A payment method that enables automatic charging, comprising a step of acquiring usage information regarding the use of the payment method in at least one of multiple services, When the user specifies the settings for the auto-charge setting, a presentation step is made to the user that provides information corresponding to the usage information. When the above presentation is made, the setting acquisition step involves acquiring the specified setting specified by the user, An auto-charge execution step that performs the auto-charge based on the specified settings, Auto-charge methods including

19. A payment method that enables automatic charging, and a usage information acquisition unit that acquires usage information regarding the use of the payment method in at least one of a plurality of services, When the user specifies the settings for the auto-charge setting, a display unit presents information to the user in accordance with the usage information. When the above presentation is made, a setting acquisition unit acquires the specified setting specified by the user. Based on the specified settings, the auto-charge execution unit performs the auto-charge. A program that makes a computer function.

Images