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

Abstract

To increase the convenience of a user when regular payments to different payment destinations occur on different payment dates.SOLUTION: A storage unit (101) of an auto-charge system (1) stores the relation of a plurality of payment dates when regular payments to different payment destinations occur and an auto-charge setting regarding the auto-charge of settlement means usable for the regular payments. An auto-charge execution unit (102) executes auto-charge on the basis of the auto-charge setting related to each payment date.SELECTED DRAWING: Figure 4

Description

[Technical Field]

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

[0002] In recent years, efforts have been made to improve the convenience of users of payment services. For example, Patent Document 1 describes a fixed-term balance payment system in which, when a user purchases a product at a store, the price of the product is not deducted from the balance of the payment method such as electronic money, but instead the total amount of the purchases made up to that point is deducted in one lump sum on the monthly settlement date. With fixed-term balance payment, if the balance of the payment method is insufficient, an auto-charge is performed to make up the shortfall. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-096746 Summary of the Invention [Problem to be solved by the invention]

[0004] For example, if payment methods such as electronic money could be used for periodic payments such as subscriptions, it would be more convenient for users. This also applies to periodic payments other than subscriptions. For example, if periodic payments to different payees occur on multiple payment dates, the user would need to manage the balance of the payment method so that the balance does not run out on each of the multiple payment dates, which would increase the user's management burden.

[0005] However, the technology in Patent Document 1 does not anticipate multiple payment dates on which periodic payments to different payees occur, and only performs auto-charge to make up for any shortfall in the balance on the monthly settlement date. For this reason, the conventional technology was unable to improve user convenience when multiple periodic payments to different payees occur on each of multiple payment dates.

[0006] One objective of this disclosure is to The goal is to make auto-charge settings easier to manage. [Means for solving the problem]

[0007] The auto-charge system of the present disclosure includes a storage unit that associates and stores each of a plurality of payment dates on which regular payments to different payees occur with an auto-charge setting for auto-charging of payment methods that can be used for the regular payments, and an auto-charge execution unit that executes the auto-charge based on the auto-charge setting associated with each of the plurality of payment dates. [Effects of the Invention]

[0008] According to the present disclosure, convenience for users is improved when periodic payments to different payees occur on each of multiple payment dates. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of an auto-charging system. [Figure 2] FIG. 10 is a diagram showing an example of the flow of membership registration for a music distribution service. [Figure 3] FIG. 10 is a diagram showing an example of a monthly payment schedule for a user. [Figure 4] FIG. 2 is a functional block diagram showing an example of functions realized in the auto-charging system. [Figure 5] FIG. 2 is a diagram illustrating an example of an electronic money database. [Figure 6]FIG. 2 is a diagram illustrating an example of a service database. [Figure 7] FIG. 10 is a diagram illustrating an example of processing executed in an auto-charge system. [Figure 8] FIG. 10 is a diagram illustrating an example of a functional block according to a modified example. [Figure 9] FIG. 13 is a diagram showing an example of a calendar screen displayed on a user terminal in Modification 4. [Figure 10] FIG. 10 is a diagram showing an example of a payment amount screen. DETAILED DESCRIPTION OF THE INVENTION

[0010] [1. Overall configuration of the auto-charging system] An example of an embodiment of an auto-charge system according to the present disclosure will be described. In this embodiment, electronic money will be described as an example of a payment method that can be auto-charged. Therefore, any description of electronic money can be read as payment method. The payment method is not limited to electronic money as long as it has a rechargeable balance. For example, the payment method may be called points, an account, a wallet, or any other name. The payment method may also be called a payment method, with prepaid payment methods being an example.

[0011] Fig. 1 is a diagram showing an example of the overall configuration of an auto-charge system. For example, the auto-charge system 1 includes an electronic money server 10, a service provider server 20, and a user terminal 30. Each of the electronic money server 10, the service provider server 20, and the user terminal 30 can be connected to a network N such as the Internet or a LAN. Although two service provider servers 20 are shown in Fig. 1, the number of service provider servers 20 may be one or three or more.

[0012] The electronic money server 10 is a server computer of a payment service provider. The payment service provider is a business that provides payment services related to electronic money. For example, the electronic money server 10 includes a control unit 11, a memory unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The memory unit 12 includes a volatile memory such as RAM and a non-volatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0013] The service provider server 20 is a server computer of the service provider. The service provider is a business that provides a service that generates periodic payments. Hereinafter, this service will be referred to as a periodic payment service. Periodic payments are payments that occur repeatedly at a predetermined cycle. In this embodiment, the periodic payment cycle is one month as an example, but the periodic payment cycle may be any length and is not limited to one month. For example, the periodic payment cycle may be one day, several days, one week, several weeks, several months, or one year.

[0014] In this embodiment, a subscription music distribution service, a video distribution service, and an e-book service are described as examples of periodic payment services. When there is no need to distinguish between music distribution services, video distribution services, and e-book services, they are collectively referred to as periodic payment services. The periodic payment service may be any service and is not limited to the example of this embodiment. For example, the periodic payment service may be a communication service, an electricity service, an e-commerce service, or a financial service. Examples of application of the auto-charge system 1 to other periodic payment services will be described in the modified examples below.

[0015] In this embodiment, the music distribution service, video distribution service, and e-book service are each provided by a different service provider. Therefore, it is assumed that there are three service provider servers 20. For example, the service provider server 20 includes a control unit 21, a storage unit 22, and a communication unit 23. The physical configurations of the control unit 21, the storage unit 22, and the communication unit 23 may be similar to those of the control unit 11, the storage unit 12, and the communication unit 13, respectively.

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

[0017] The programs stored in the storage units 12, 22, and 32 may be supplied via the network N. Also, the programs stored in a computer-readable information storage medium may be supplied via a reading unit (for example, an optical disk drive or a memory card slot) that reads the information storage medium, or an input / output unit (for example, a USB port) that inputs and outputs data to and from an external device.

[0018] Furthermore, the auto-charge system 1 only needs to include at least one computer and is not limited to the example of Fig. 1. For example, the auto-charge system 1 may include only the electronic money server 10, without including the service provider server 20 and the user terminal 30. In this case, the service provider server 20 and the user terminal 30 exist outside the auto-charge system 1. The auto-charge system 1 may also include the electronic money server 10 and other server computers of the payment service provider.

[0019] [2. Overview of the Auto-Charge System] In this embodiment, online electronic money will be described as an example of electronic money, but the electronic money may be of any type and is not limited to online electronic money. For example, the electronic money may be of a type that uses an IC card, a type that uses an IC chip in the user terminal 30, a type that uses a magnetic card, or a type that uses short-range wireless communication.

[0020] Online electronic money is electronic money that can be used for internet services such as electronic commerce services or travel reservation services. Online electronic money may also be usable in physical stores. For example, online electronic money may be of a type that can be used by scanning a barcode or two-dimensional code in a physical store. Hereinafter, online electronic money will be simply referred to as electronic money.

[0021] In this embodiment, an example is given in which a user uses a payment service, music distribution service, video distribution service, and e-book service from dedicated applications installed on the user terminal 30, but the user may also use these services from a browser on the user terminal 30. For example, after completing membership registration for the payment service, the user registers for each of the music distribution service, video distribution service, and e-book service. Here, the flow of membership registration for the music distribution service is given as an example.

[0022] FIG. 2 shows an example of the flow of membership registration for a music distribution service. For example, when an application for the music distribution service installed on the user terminal 30 is launched, the music distribution service's top screen G1 is displayed on the display unit 35. As can be seen from the top screen G1, the music distribution service is a monthly subscription for 1,000 yen. For example, when the user selects button B10, the membership registration screen G2 is displayed on the display unit 35. If the user has already registered as a member, they can log in to the music distribution service using link L11.

[0023] For example, the user enters information required for membership registration, such as name and email address, into input forms F20 and F21. The user selects one of the multiple payment methods available for the music distribution service by selecting radio button B22. For example, if the user selects the radio button B22 for electronic money (XXX Cash in FIG. 2) and proceeds with the membership registration process, the payment service application will be launched. When the user logs in to the payment service, an auto-charge setting screen G3 will be displayed on the display unit 35.

[0024] In this embodiment, a user can use the auto-charge function of an electronic money account to prevent monthly payments for a music distribution service from failing due to insufficient electronic money balance. For example, when a user uses the auto-charge function for the first time, the user goes through a predetermined application procedure. Here, it is assumed that the user has already completed the application procedure for the auto-charge function. For example, the user can specify the charge method, charge threshold, and post-charge balance as auto-charge settings using input forms F30 to F32.

[0025] The charge method is the payment method used for auto-charge. Various payment methods can be used as the charge method, such as a credit card, a bank account, an account at another financial institution, cryptocurrency, points, other electronic money, a debit card, or sales proceeds from a flea market service. In the example of Figure 2, the user's credit card is specified as the charge method.

[0026] The charge threshold is a balance that serves as a criterion for determining whether or not to perform auto-charge. In this embodiment, auto-charge is performed when the balance falls below the charge threshold, but auto-charge may also be performed when the balance falls below the charge threshold. The user can specify any charge threshold. For example, the user can specify a value of 1,000 yen or more, which is required for monthly payments for a music distribution service, as the charge threshold.

[0027] The post-charge balance is the balance after auto-charge. The post-charge balance can also be said to be the balance that is always kept in the electronic money. The user can specify any post-charge balance. For example, the user may specify a figure of 1,000 yen or more, which is required for monthly payments for a music distribution service, as the post-charge balance. The user may specify a figure of 1,000 yen or more, which is required for monthly payments for a music distribution service, as the post-charge balance. The user may specify a figure of 1,000 yen or more, which is required for monthly payments for a music distribution service, as the post-charge balance.

[0028] For example, if the user selects button B33, the auto-charge settings and membership registration are completed, the music distribution service application returns to the foreground, and membership registration completion screen G4 is displayed on display unit 35. As shown in membership registration completion screen G4, on the 5th of each month, which is the payment date for the music distribution service, auto-charge is executed so that "if the balance falls below 1,000 yen, the balance will be increased to 1,100 yen," and the 1,000 yen required for the monthly payment for the music distribution service is automatically deducted from the electronic money balance.

[0029] In this embodiment, membership registration for each of the video distribution service and the e-book service is performed in the same manner as for the music distribution service. For example, a user uses electronic money to make monthly payments for each of the video distribution service and the e-book service. The user specifies an auto-charge setting for the video distribution service and an auto-charge setting for the e-book service. On the payment date for each of the music distribution service, the video distribution service, and the e-book service, auto-charge is performed based on the auto-charge setting associated with that payment date.

[0030] FIG. 3 is a diagram showing an example of a schedule for a certain user's monthly payments. In this embodiment, monthly payments are made according to the schedule shown in FIG. 3. For example, the 5th of each month is the payment date for the music distribution service. On the 5th of each month, auto-charge is performed based on the auto-charge setting for the music distribution service, which states that "if the balance falls below 1,000 yen, the balance will be increased to 1,100 yen." On the 5th of each month, the 1,000 yen required to pay for the music distribution service is deducted from the electronic money balance.

[0031] For example, suppose a video streaming service requires a payment of 2,500 yen on the 13th of each month. On the 13th of each month, an auto-charge is executed based on the auto-charge settings for the video streaming service, such as "if the balance falls below 2,500 yen, the balance will be increased to 3,000 yen." On the 13th of each month, the 2,500 yen required to pay for the video streaming service is deducted from the electronic money balance.

[0032] For example, suppose an e-book service requires a payment of 1,200 yen on the 25th of each month. On the 25th of each month, an auto-charge is executed based on the auto-charge setting for the e-book service, which states that "if the balance falls below 1,200 yen, the balance will be set to 1,200 yen." On the 25th of each month, the 1,200 yen required to pay for the e-book service is deducted from the e-money balance.

[0033] As described above, in this embodiment, an auto-charge setting for the music distribution service, an auto-charge setting for the video distribution service, and an auto-charge setting for the e-book service are specified. When the payment date for each of the music distribution service, video distribution service, and e-book service arrives, auto-charge is executed based on the auto-charge setting for that payment date. This increases user convenience because the user does not need to worry about the balance of their electronic money on the payment date, and the balance will not run out. Details of the auto-charge system 1 will be described below.

[0034] [3. Functions realized by the auto-charge system] FIG. 4 is a functional block diagram showing an example of functions realized by the auto-charging system 1. As shown in FIG.

[0035] [3-1. Functions realized by the electronic money server] The data storage unit 100 is realized by the storage unit 12. The saving unit 101, the auto-charge execution unit 102, and the payment execution unit 103 are realized by the control unit 11.

[0036] [Data storage section] The data storage unit 100 stores data necessary for providing payment services. For example, the data storage unit 100 stores an electronic money database DB1.

[0037] Fig. 5 is a diagram showing an example of the electronic money database DB1. As shown in Fig. 5, the electronic money database DB1 is a database that stores information about electronic money held by a user. For example, the electronic money database DB1 stores a user ID for a payment service, a password for the payment service, the balance of electronic money, payment method information about payment methods that can be used for top-up, the name of a periodic payment service for which periodic payments occur, the user ID for the periodic payment service, the payment date, the payment amount, and auto-top-up settings.

[0038] The user ID is an example of identification information that can identify a user. In this embodiment, one user holds one electronic money, so the identification information can also be referred to as information that can identify electronic money. The identification information may be other information such as an email address, a telephone number, or an electronic money ID. In this embodiment, an example is given in which a unique user ID and password are used for each of the payment service and the periodic payment service, but a common user ID and password may also be used.

[0039] Payment method information is information that can identify the payment method used for charging. For example, if a credit card is used for charging, the payment method information includes the card number, expiration date, and cardholder name. For example, if a bank account is used for charging, the payment method information includes the financial institution code, branch code, and account number. Similarly, for other payment methods, the payment method information only needs to include information that can identify the other payment method. Payment method information for payment methods specified by the user is registered in the electronic money database DB1. The payment methods indicated in the payment method information can be used not only for automatic charging, but also for manual charging by the user.

[0040] The electronic money database DB1 stores the name of the periodic payment service for which the user pays with electronic money, and the user ID of the periodic payment service. For example, when a user specifies electronic money as the payment method when registering as a member of the periodic payment service, the electronic money server 10 receives the user ID of the periodic payment service from the service provider server 20. The electronic money server 10 stores the name of the periodic payment service and the received user ID of the periodic payment service in the electronic money database DB1.

[0041] A payment date is a date on which a periodic payment is made. The payment date can also be called a settlement date. The payment date occurs repeatedly at predetermined intervals. In this embodiment, a case will be described in which the day on which a user registers as a member of a periodic payment service becomes the user's monthly payment date. In the example of Figure 3, the user registers as a member of a music distribution service on the 5th of a certain month, so the payment date for the music distribution service is the 5th of each month. Similarly, the user registers as a member of a video distribution service and an e-book service on the 13th and 25th of each month, respectively, so the payment dates for the video distribution service and the e-book service are the 13th and 25th of each month, respectively. The payment date may be the same for all users, regardless of the date of membership registration.

[0042] The payment amount is the amount required for periodic payments. The payment amount can also be referred to as the settlement amount. In this embodiment, a case is described in which the payment amount for a certain periodic payment service is the same for all users who use this periodic payment service, but the payment amount may also be an amount that depends on the user. For example, if the periodic payment service offers multiple pricing plans, the payment amount may be set according to the pricing plan selected by the user.

[0043] The auto-charge setting is a setting related to auto-charge. In this embodiment, the case where the auto-charge setting indicates the charge method, charge threshold, and post-charge balance is described, but the auto-charge setting may indicate only the charge threshold and post-charge balance without indicating the charge method. In this case, a common charge method is used for multiple auto-charge settings. The common charge method is stored in the electronic money database DB1 as a setting separate from the auto-charge setting.

[0044] For example, the auto-charge setting may indicate only either the charge threshold or the post-charge balance. If the auto-charge setting indicates only the charge threshold, the post-charge balance may be a fixed value that cannot be specified by the user, or may be the same numerical value as the charge threshold. If the auto-charge setting indicates only the post-charge balance, the charge threshold may be the same numerical value as the post-charge balance.

[0045] The auto-charge setting may be any information indicating what type of auto-charge is to be performed, and may be information other than the charge method, charge threshold, and post-charge balance. For example, the auto-charge setting may indicate the charge amount rather than the post-charge balance. In other words, instead of the auto-charge setting in this embodiment that "when the balance falls below 1,000 yen, the balance will be set to 1,100 yen," the auto-charge setting may be "when the balance falls below 1,000 yen, 1,100 yen will be charged."

[0046] For another example, the auto-charge setting may indicate a period during which the auto-charge setting is applied. In this embodiment, a case is described in which the auto-charge setting is applied on the payment date of a flat-rate payment service, but if the auto-charge setting is also applied on other days, the auto-charge setting may indicate a period during which the auto-charge setting is applied. For example, if the auto-charge setting in FIG. 3, such as "When the balance falls below 1,000 yen, the balance will be set to 1,100 yen," is applied on the 1st to 5th of each month, this auto-charge setting may indicate a period such as "1st to 5th of each month."

[0047] The data storage unit 100 can store any data. The data stored in the data storage unit 100 is not limited to the electronic money database DB1. Instead of combining information such as electronic money balance and information related to periodic payments in a single database as in the present embodiment, these may be stored in separate databases. Alternatively, for example, a database for storing information related to periodic payments may exist for each periodic payment service.

[0048] [Storage Department] The storage unit 101 stores auto-charge settings corresponding to periodic payments. Storing the auto-charge settings means recording the auto-charge settings in memory. In this embodiment, a case will be described in which storing the auto-charge settings in the electronic money database DB1 corresponds to saving the auto-charge settings, but the auto-charge settings may also be stored in another database, another computer other than the electronic money server 10, or an information storage medium external to the electronic money server 10.

[0049] In this embodiment, the storage unit 101 stores a plurality of payment dates on which periodic payments to different payees occur in association with the auto-charge settings. There are a plurality of payment dates within a certain period. In this embodiment, the period is described as being every month from January to December, but this period may be any period that corresponds to the payment cycle. As mentioned above, the cycle is not limited to one month.

[0050] A payee is a person who receives a payment. A payee is a party to whom a user makes a payment. In this embodiment, a case where a service provider corresponds to a payee is taken as an example. Therefore, any description of a service provider can be read as a payee. A payee may be any person and is not limited to a service provider. For example, a payee may be a national government, a local government, a government agency, a non-profit organization, or an individual.

[0051] In this embodiment, the payee on a certain payment date is different from the payee on other payment dates. Therefore, the multiple payment dates include a first payment date on which a periodic payment to a first payee occurs, and a second payment date on which a periodic payment to a second payee different from the first payment date occurs and is different from the first payment date. In the example of Figure 3, there are three payment dates: the 5th of each month on which a periodic payment to a music distribution service occurs, the 13th of each month on which a periodic payment to a video distribution service occurs, and the 25th of each month on which a periodic payment to an e-book service occurs.

[0052] "Storing in association" means storing one piece of information in a state in which the other piece of information can be searched for. For example, the storage unit 101 stores a pair of a payment date and an auto-charge setting in the electronic money database DB1, thereby storing the payment date and the auto-charge setting in association with each other. In this embodiment, the auto-charge setting is specified on the auto-charge setting screen G3 when registering as a member of the periodic payment service, so the storage unit 101 stores the payment date of this periodic payment service and the auto-charge setting specified on the auto-charge setting screen G3 in association with each other.

[0053] In this embodiment, the storage unit 101 associates each of a plurality of payment dates with an auto-charge setting indicating a post-charge balance equal to or greater than the payment amount for the periodic payment on that payment date and stores the associated setting. For example, the storage unit 101 stores the auto-charge setting so as to indicate the post-charge balance specified in the input form F32 of the auto-charge setting screen G3. The auto-charge setting screen G3 may be restricted so that only a post-charge balance equal to or greater than the payment amount can be specified, or an error message may be displayed if a post-charge balance less than the payment amount is specified.

[0054] In the example of Fig. 3, the storage unit 101 stores the payment date for the music distribution service in association with the auto-charge setting indicating the post-charge balance specified by the user when registering as a member of the music distribution service. Similarly, the storage unit 101 stores the payment date for the video distribution service and the e-book service in association with the auto-charge setting indicating the post-charge balance specified by the user. The post-charge balance may be automatically determined to be a value corresponding to the payment amount.

[0055] In this embodiment, the charge method specified by the user is also included in the auto-charge settings, so the storage unit 101 associates each of the multiple payment dates with the auto-charge setting that indicates the charge method selected from the multiple charge methods and stores them. For example, the storage unit 101 stores the auto-charge setting so that it indicates the charge method specified in the input form F30 of the auto-charge settings screen G3. Since a payment method whose payment method information is stored in the electronic money database DB1 can be specified as the charge method, the input form F30 displays this payment method information in a selectable manner.

[0056] In this embodiment, the storage unit 101 stores the auto-charge setting when a user registers as a member of the periodic payment service, but the storage unit 101 can store the auto-charge setting at any time. For example, the storage unit 101 may store the auto-charge setting after the user registers as a member of the periodic payment service. If the user changes the auto-charge setting after registering as a member, the storage unit 101 may store the changed auto-charge setting specified by the user. For example, the auto-charge setting may not be set when the user registers as a member of the periodic payment service, but may be set after the user registers as a member.

[0057] [Auto Charge Execution Department] The auto-charge execution unit 102 executes auto-charge based on the auto-charge setting stored by the storage unit 101. Executing auto-charge means automatically charging electronic money. The auto-charge setting is set so that the balance will be equal to or greater than the amount of payment for periodic payments, so the auto-charge execution unit 102 executes auto-charge based on the auto-charge setting so that the balance will be equal to or greater than the amount of payment for periodic payments.

[0058] The auto-charge itself can use various known processes. For example, the auto-charge execution unit 102 executes the auto-charge based on the charge method indicated in the auto-charge setting. For example, if a credit card is specified as the charge method, the auto-charge execution unit 102 executes authorization of the credit card and, if the authorization is successful, executes the auto-charge so that the balance of electronic money increases.

[0059] For example, if a bank account is specified as the charge method, the auto-charge execution unit 102 executes auto-charge so that the balance of the bank account decreases and the balance of the electronic money increases. For example, if a crypto asset is specified as the charge method, the auto-charge execution unit 102 executes auto-charge so that the balance of the crypto asset decreases and the balance of the electronic money increases. If another charge method is specified, the auto-charge execution unit 102 executes auto-charge according to the other charge method.

[0060] In this embodiment, we will explain the case where the auto-charge execution unit 102 executes auto-charge based on auto-charge settings associated with each of multiple payment dates, but since an auto-charge setting may be associated with only one payment date, the auto-charge execution unit 102 may also execute auto-charge based on the auto-charge setting associated with one payment date.

[0061] For example, the auto-charge execution unit 102 obtains the current date and time using a real-time clock or a GPS signal, etc. The auto-charge execution unit 102 determines whether each of the multiple payment dates stored in the electronic money database DB1 has arrived based on the current date and time. When the auto-charge execution unit 102 determines that a certain payment date has arrived, it executes auto-charge based on the auto-charge setting associated with that payment date. When auto-charge for this payment date is performed, auto-charge settings associated with other payment dates are not referenced.

[0062] In this embodiment, auto-charge is not performed on days other than payment dates. However, as in a modified example described below, auto-charge may be performed on other days based on the default auto-charge setting. For example, auto-charge may be performed based on the auto-charge setting associated with a certain payment date until the payment date has passed. For example, auto-charge may be performed based on the auto-charge setting associated with a certain payment date for a certain period of time including the payment date.

[0063] In this embodiment, since a charge threshold is indicated in the auto-charge setting, the auto-charge execution unit 102 determines whether the balance of electronic money stored in the electronic money database DB1 is below the charge threshold. If the auto-charge execution unit 102 determines that the balance of electronic money is not below the charge threshold, it does not execute auto-charge, but if it determines that the balance of electronic money is below the charge threshold, it executes auto-charge. In particular, if a charge threshold is not used, the auto-charge execution unit 102 may determine whether auto-charge is necessary by determining whether the balance of electronic money is less than the payment amount.

[0064] In this embodiment, the auto-charge setting indicates the post-charge balance, and the auto-charge execution unit 102 executes auto-charge so that the post-charge balance becomes the post-charge balance indicated in the auto-charge setting associated with each of multiple payment dates. For example, on a certain payment date, the auto-charge execution unit 102 determines the charge amount as the difference between the post-charge balance indicated in the auto-charge setting associated with that payment date and the current balance of electronic money. The auto-charge execution unit 102 executes auto-charge so that the balance increases by the determined charge amount.

[0065] In this embodiment, the auto-charge execution unit 102 executes auto-charge before the payment time for each of multiple payment dates arrives, based on the auto-charge settings associated with that payment date. The payment time is the time at which payment is executed on each payment date. In this embodiment, for simplicity of explanation, an example is given in which the payment time is fixed at 10:00 AM regardless of the payment date, but the payment time may be any time and is not limited to 10:00 AM. For example, the payment time may be a time other than 10:00 AM, or the payment time on one payment date may be different from the payment time on another payment date.

[0066] In this embodiment, the payment time is 10:00 AM on a certain payment date, so auto-charge may be performed at least once between midnight and 10:00 AM on this payment date. Auto-charge does not necessarily have to be performed, and may not be performed if there is a sufficient balance of electronic money. Although a case will be described in which auto-charge based on the auto-charge setting associated with a certain payment date is not performed after the payment time on that payment date has arrived and payment has been completed, auto-charge based on this auto-charge setting may also be performed after the payment time has arrived and payment has been completed.

[0067] For example, when each of multiple payment dates arrives, the auto-charge execution unit 102 determines whether auto-charge is necessary at each predetermined time until the payment time based on the auto-charge setting associated with that payment date. The predetermined time is the time for determining whether auto-charge is necessary. In this embodiment, an example is given in which the predetermined time is one hour, but the predetermined time may be any time and is not limited to one hour. For example, the predetermined time may be other times such as one minute, five minutes, 30 minutes, two hours, or four hours.

[0068] In the example of Figure 3, the auto-charge execution unit 102 determines every hour between midnight and 10:00 AM on the 5th of each month whether the balance is less than 1,000 yen. If the auto-charge execution unit 102 determines that the balance is 1,000 yen or more, it does not execute auto-charge. If the auto-charge execution unit 102 determines that the balance is less than 1,000 yen, it executes auto-charge so that the balance becomes 1,100 yen.

[0069] For example, the auto-charge execution unit 102 determines whether the balance is less than 2,500 yen every hour from midnight to 10:00 a.m. on the 13th of each month. If the auto-charge execution unit 102 determines that the balance is 2,500 yen or more, it does not execute auto-charge. If the auto-charge execution unit 102 determines that the balance is less than 2,500 yen, it executes auto-charge so that the balance becomes 3,000 yen.

[0070] For example, the auto-charge execution unit 102 determines whether the balance is less than 1,200 yen every hour from midnight to 10:00 a.m. on the 25th of each month. If the auto-charge execution unit 102 determines that the balance is 1,200 yen or more, it does not execute auto-charge. If the auto-charge execution unit 102 determines that the balance is less than 1,200 yen, it executes auto-charge so that the balance becomes 1,200 yen.

[0071] The need for auto-charge may be determined each time the balance of the electronic money changes, rather than at predetermined time intervals. In this case, the auto-charge execution unit 102 may determine whether the balance of the electronic money is less than the charge threshold when the balance of the electronic money changes on the payment date. Alternatively, for example, the auto-charge execution unit 102 may execute auto-charge immediately before the payment time on each payment date based on the auto-charge setting associated with that payment date, as in a modified example described below.

[0072] Furthermore, in this embodiment, since the payment date and auto-charge settings differ depending on the user, the storage unit 101 associates and stores, for each user who makes periodic payments, the payment date for that user's payment with the auto-charge setting for that payment. When the payment date for that user arrives, the auto-charge execution unit 102 executes auto-charge for each individual user based on the user's auto-charge setting associated with the payment date so that the user's electronic money balance increases.

[0073] [Payment Execution Department] The payment execution unit 103 executes periodic payments. Executing a payment can also be referred to as executing a settlement. The payment process itself can utilize various known processes. When electronic money is used, as in this embodiment, the payment execution unit 103 executes a process of deducting the payment amount from the balance of the electronic money. When another payment method, such as points or an account, is used, the payment execution unit 103 executes a process of deducting the payment amount from the balance of the other payment method.

[0074] For example, the payment execution unit 103 determines whether the payment date stored in the electronic money database DB1 has arrived based on the current date and time. If it is determined that the payment date has not arrived, the payment execution unit 103 does not execute the payment, but if it is determined that the payment date has arrived, the payment execution unit 103 executes the payment so that the balance of the electronic money of the user to whom the payment is made is reduced by a predetermined payment amount. The payment execution unit 103 simply refers to the electronic money database DB1 to identify the users to whom the payment is made and the payment amounts of each user.

[0075] In this embodiment, since there are multiple payment dates in a month, the payment execution unit 103 executes the payment on each of the multiple payment dates based on the electronic money when that payment date arrives. For example, the payment execution unit 103 determines whether the payment time for each payment date has arrived. In this embodiment, the payment time is 10:00 AM, so the payment execution unit 103 determines whether 10:00 AM on the payment date has arrived. If the payment execution unit 103 does not determine that 10:00 AM on the payment date has arrived, it does not execute the payment, but if it determines that 10:00 AM on the payment date has arrived, it executes the payment.

[0076] In the example of Figure 3, when it is determined that 10:00 AM on the 5th of each month has arrived, the payment execution unit 103 executes the payment by deducting 1,000 yen from the remaining payment amount. When it is determined that 10:00 AM on the 13th of each month has arrived, the payment execution unit 103 executes the payment by deducting 2,500 yen from the remaining payment amount. When it is determined that 10:00 AM on the 25th of each month has arrived, the payment execution unit 103 executes the payment by deducting 1,200 yen from the remaining payment amount.

[0077] The payment execution unit 103 may execute the payment based on a request from the service provider server 20. In this case, when the payment time on the payment date arrives, the service provider server 20 requests the execution of the payment by transmitting a list of users to whom the payment is to be made to the electronic money server 10. Upon receiving the list, the payment execution unit 103 executes the payment so that the balance of the electronic money of the users included in the list is reduced by a predetermined payment amount.

[0078] The list may include user IDs of the periodic payment service. Since the relationship between the user IDs of the payment service and the user IDs of the periodic payment service is stored in the electronic money database DB1, the payment execution unit 103 can identify which user of the payment service corresponds to the user indicated by the user ID of the periodic payment service included in the list. The list may include user IDs of the payment service instead of user IDs of the periodic payment service. In this case, the service provider server 20 is assumed to store the relationship between the user IDs of the payment service and the user IDs of the periodic payment service.

[0079] For example, when a payment for a certain periodic payment service is completed, the payment execution unit 103 transmits a list of users whose payments have been completed to the service provider server 20 corresponding to that periodic payment service. This list may include the user ID of the settlement service or the user ID of the periodic payment service. By receiving the list, the service provider server 20 can identify which users' payments have been completed.

[0080] [3-2. Functions realized by the service provider server] In this embodiment, the service provider servers 20 for the music distribution service, video distribution service, and e-book service each have similar functions, so these will be collectively described as the functions of the service provider server 20 for the periodic payment service. The data storage unit 200 is realized by the storage unit 22. The service providing unit 201 is realized by the control unit 21.

[0081] [Data storage section] The data storage unit 200 stores data necessary to provide the subscription payment service, for example, the data storage unit 200 stores the service database DB2.

[0082] FIG. 6 is a diagram showing an example of service database DB2. Service database DB2 is a database that stores information about users who have registered as members of the periodic payment service. FIG. 6 shows an example of data storage for a music distribution service. For example, service database DB2 stores the user ID of the periodic payment service, payment date, payment amount, payment method information related to the payment method used for the periodic payment, payment status information related to the payment status, and the user ID of the payment service. When a user registers as a member of the periodic payment service, service provider server 20 generates various information such as the user ID of the periodic payment service and stores it in service database DB2. The payment status information is updated by service provision unit 201.

[0083] [Service Provision Department] The service providing unit 201 provides a periodic payment service. The method of providing the periodic payment service itself can use various known methods. For example, the service providing unit 201 provides the periodic payment service to a user who has completed payment. The service providing unit 201 identifies users who have completed payment based on the list received from the electronic money server 10 when a payment is executed by the payment execution unit 103. The service providing unit 201 updates the payment status information in the service database DB2 to indicate that payments for users included in the list have been completed.

[0084] [3-3. Functions implemented on user devices] The data storage unit 300 is realized by the storage unit 32. The display control unit 301 and the operation reception unit 302 are realized by the control unit 31.

[0085] [Data storage section] The data storage unit 300 stores data necessary for using each of the settlement service and the periodic payment service, for example, the data storage unit 300 stores applications for each of the settlement service and the periodic payment service.

[0086] [Display control section] The display control unit 301 causes the display unit 35 to display each screen described with reference to FIG.

[0087] [Operation reception section] The operation receiving unit 302 receives operations on each screen described with reference to FIG.

[0088] [4. Processing performed by the auto-charge system] 7 is a diagram showing an example of processing executed in the auto-charging system 1. This processing is executed by the control units 11, 21, and 31 operating in accordance with programs stored in the storage units 12, 22, and 32, respectively. In this embodiment, of the processing executed in the auto-charging system 1, processing related to auto-charging will be mainly described.

[0089] 7, the user terminal 30 executes processing with the service provider server 20 based on the application for the periodic payment service to display the top screen G1 and the member registration screen G2 (S1). The user selects electronic money as the payment method using the radio button B22 and proceeds with the member registration procedure. The user terminal 30 executes processing with the electronic money server 10 based on the application for the payment service to display the auto-charge setting screen G3 (S2).

[0090] When the user selects button B33, the user terminal 30 transmits the auto-charge settings specified in the input forms F30 to F32 to the electronic money server 10 (S3). When the electronic money server 10 receives the auto-charge settings from the user terminal 30 (S4), it saves the auto-charge settings in the electronic money database DB1 (S5). In S5, the electronic money server 10 also receives information such as the payment date from the service provider server 20 or the user terminal 30, and saves this information in association with the auto-charge settings. The user terminal 30 executes processing with the service provider server 20 to display a member registration completion screen G4 (S6). Through the above processing of S1 to S6, member registration for the periodic payment service is completed. Once member registration is complete, the user will be able to use the periodic payment service.

[0091] When registering as a member for the periodic payment service, auto-charge may be performed for the first payment. In this case, the electronic money server 10 determines whether auto-charge is necessary based on the auto-charge settings specified on the auto-charge setting screen G3 when registering as a member. If auto-charge is not necessary, the electronic money server 10 performs the first payment. If auto-charge is necessary, the electronic money server 10 performs auto-charge and then performs the first payment. When the first payment is completed, the member registration completion screen G4 is displayed on the display unit 35 by the processing of S6.

[0092] The service provider server 20 creates a list of users who are the subject of payment based on the service database DB2 (S7). The process of S7 may be performed daily or when the payment date approaches. The service provider server 20 transmits the list created in S7 to the electronic money server 10 (S8). Upon receiving the list from the service provider server 20 (S9), the electronic money server 10 updates the electronic money database DB1 so that the users who are the subject of payment are updated (S10). Since the payment method may be changed on the periodic payment service side, the latest information is transmitted to the electronic money server 10 by executing the processes of S7 to S10. For example, information on users who have changed their payment method for the periodic payment service from another payment method to electronic money, or from electronic money to another payment method, is shared with the electronic money server 10.

[0093] The electronic money server 10 determines whether the payment date for any of the regular payment services of any of the users has arrived based on the electronic money database DB1 (S11). If it is determined that the payment date has not arrived (S11: N), this process ends. If it is determined that the payment date has arrived (S11: Y), the electronic money server 10 identifies n (n is a natural number) users who have set up auto-charge among the users who are the subject of payment based on the electronic money database DB1 (S12).

[0094] The electronic money server 10 performs auto-charge every hour based on the auto-charge settings of the n users identified in S12 (S13). In S13, the electronic money server 10 determines whether auto-charge is necessary for each user based on the charge threshold indicated by the auto-charge setting of the user and the balance of electronic money held by the user. The electronic money server 10 performs auto-charge based on the auto-charge setting of the user for whom auto-charge is determined to be necessary.

[0095] The electronic money server 10 determines whether the payment time has arrived (S14). If it is determined that the payment time has not arrived (S14: N), the process returns to S13, and determines every hour whether auto-charge is required for n users, and performs auto-charge as necessary. If it is determined that the payment time has arrived (S14: Y), the electronic money server 10 executes payment for the periodic payment service (S15). In S15, if there are multiple periodic payment services for which payment should be executed, the electronic money server 10 executes payment for each of the multiple periodic payment services.

[0096] The electronic money server 10 transmits a list of users who have made payments to the service provider server 20 (S16). Upon receiving the list (S17), the service provider server 20 updates the service database DB2 so that the user's payment status is updated to the latest information (S18), and this process ends.

[0097] The auto-charge system 1 of this embodiment associates each of multiple payment dates with an auto-charge setting and stores it. The auto-charge system 1 performs auto-charge based on the auto-charge setting associated with each of the multiple payment dates. This increases user convenience by preventing insufficient balances without the user having to worry about the balance around each payment date, even if regular payments to different payees occur on multiple payment dates. Furthermore, by saving auto-charge settings for each payment date rather than using a common auto-charge setting for multiple payment dates, flexible auto-charge according to the payment date is possible.

[0098] Furthermore, the autocharge system 1 performs autocharge so that the post-charge balance is equal to the post-charge balance indicated in the autocharge setting associated with each of the multiple payment dates. This ensures that the post-charge balance is equal to or greater than the payment amount for each payment date, thereby more reliably preventing insufficient balances and enhancing user convenience. Furthermore, setting the post-charge balance also prevents unintended overcharges from being performed by the user, thereby enhancing user convenience. For example, suppose a malicious third party illegally logs into a subscription payment service and the subscription payment service is fraudulently used. In conventional technology, when an autocharge is performed to cover a shortfall, if a large payment is incurred due to fraudulent use, an autocharge is performed to cover the payment amount, resulting in a large payment. However, by setting the post-charge balance, even if such fraudulent use occurs, payments are generally only made up to the post-charge balance, preventing large payments from being made. Although a payment may fail and the subscription payment service may be suspended, the user can detect the fraudulent use. In addition to fraudulent use, large payments that the user would not be aware of can be prevented.

[0099] Furthermore, the auto-charge system 1 executes auto-charge based on the auto-charge settings associated with each of the multiple payment dates before the payment time arrives on that payment date. This allows auto-charge to be executed before the payment time arrives, more reliably preventing insufficient balance, thereby improving user convenience. When the payment time arrives and payment is executed, it is conceivable to execute auto-charge as part of that process, but in this case, there is a possibility that a large number of auto-charges will be concentrated, increasing the processing load on the electronic money server 10. By completing auto-charges in advance, the timing of auto-charge execution can be dispersed. As a result, the processing load on the electronic money server 10 can be reduced.

[0100] Furthermore, when each of multiple payment dates arrives, the auto-charge system 1 determines whether or not auto-charge is necessary at predetermined intervals until the payment time, based on the auto-charge settings associated with that payment date. If the shortfall is auto-charged when a payment is made, auto-charges may be concentrated, increasing the processing load on the electronic money server 10. By determining in advance at predetermined intervals whether or not auto-charge is necessary and then executing auto-charge, the timing of auto-charge execution can be dispersed. As a result, the processing load on the electronic money server 10 can be reduced.

[0101] Furthermore, the auto-charge system 1 associates each of a plurality of payment dates with an auto-charge setting that indicates a selected charging method from a plurality of charging methods and stores them in association with each other. This allows auto-charge to be performed using a flexible charging method for each payment date, improving user convenience.

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

[0103] 8 is a diagram showing an example of functional blocks in the modified example. Each of first display control unit 104, prediction unit 105, determination unit 106, reception unit 107, and second display control unit 108 is realized by control unit 11.

[0104] [5-1. Variation 1] For example, in the embodiment, the payment dates for the music distribution service, video distribution service, and e-book service are different from one another, but multiple periodic payments may occur on a given payment date. In Variation 1, in the example of Figure 3, the payment date for the video distribution service is the 5th of each month, the same as for the music distribution service, rather than the 13th.

[0105] In the case where multiple periodic payments occur on a single payment date, the storage unit 101 of the first modification stores the single payment date in association with an auto-charge setting corresponding to the total payment amount for each of the multiple periodic payments. In other words, the storage unit 101 may store multiple auto-charge settings for the same payment date in a unified manner as a single auto-charge setting.

[0106] For example, the storage unit 101 calculates the sum of the charge threshold and post-charge balance for the music distribution service and the charge threshold and post-charge balance for the video distribution service, and stores an auto-charge setting indicating the calculated sum. The storage unit 101 stores an auto-charge setting "When the balance falls below 3,500 yen, the balance will be set to 4,100 yen" which is the sum of the auto-charge setting for the music distribution service "When the balance falls below 1,000 yen, the balance will be set to 1,100 yen" and the auto-charge setting for the video distribution service "When the balance falls below 2,500 yen, the balance will be set to 3,000 yen."

[0107] Similarly, when three or more payments occur on a certain payment date, the storage unit 101 calculates the total value of the charge threshold and the post-charge balance, and stores the auto-charge setting indicating the calculated total value in association with the payment date. In the first modification, the process for saving the auto-charge setting differs from that of the embodiment, but the auto-charge itself can be executed in the same manner as in the embodiment.

[0108] In the autocharge system 1 of variant 1, when multiple periodic payments occur on a single payment date, the autocharge setting corresponding to the total payment amount for each of the multiple periodic payments is associated with and saved. When multiple periodic payments occur on a single payment date, the user's management burden increases with the number of payments. However, by setting the autocharge setting according to the total amount, the necessary amount can be reliably maintained on a single payment date, reliably preventing insufficient balances for individual payments and increasing user convenience. Since the autocharge settings are integrated within a single payment date, there is no need to manage multiple autocharge settings, reducing the burden of managing autocharge settings.

[0109] [5-2. Variation 2] For example, even if multiple periodic payments occur on one payment date, if the payment times for each payment are different, separate auto-charge settings may be saved for each payment time. In Variation 2, in the example described in Variation 1, assume that the payment time for the music distribution service is 10:00 AM on the 5th of each month, and the payment time for the video provision service is 3:00 PM on the 5th of each month. In this case, the auto-charge setting for the music distribution service may be applied until 10:00 AM on the 5th of each month, and the auto-charge setting for the video provision service may be applied from 10:00 AM on the 5th of each month until 3:00 PM.

[0110] In the second modification, when multiple periodic payments occur on a single payment date and the payment times for each of the multiple periodic payments are different from one another on the same payment date, the storage unit 101 stores separate auto-charge settings for each payment time. In the second modification, the electronic money database DB1 and the electronic money database DB1 store information on not only the payment date but also the payment time. For example, the payment time may be notified by the service provider server 20, or may be manually registered by the administrator of the payment service.

[0111] For example, when multiple periodic payments occur on a certain payment date, the storage unit 101 compares the payment times of the payments. If the payment times are the same, the storage unit 101 merges the multiple auto-charge settings into one, as in variant example 1. If the payment times are different, the storage unit 101 saves each payment time on a single payment date as a separate auto-charge setting. The auto-charge execution unit 102 executes auto-charge based on the auto-charge setting associated with a specific payment time for the multiple periodic payments until that specific payment time, and when that payment time has passed, executes auto-charge based on the auto-charge setting associated with the next payment time for the multiple periodic payments. The auto-charge execution unit 102 executes auto-charge based on the auto-charge setting associated with that payment time until a certain payment time. When that payment time has passed, the auto-charge execution unit 102 executes auto-charge based on the auto-charge setting associated with that payment time.

[0112] The auto-charge system 1 of Variation 2 saves separate auto-charge settings for each payment time when multiple periodic payments occur on a single payment date and the payment times for each of the multiple periodic payments differ from one another within the same payment date. The auto-charge system 1 performs auto-charge based on the auto-charge setting associated with a specific payment time for each of the multiple periodic payments until that specific payment time. After that payment time has passed, the auto-charge system performs auto-charge based on the auto-charge setting associated with the next payment time for each of the multiple periodic payments. This allows for more flexible auto-charge when the payment times differ from one another within a single payment date. For example, this can prevent an unnecessarily large balance from being charged by auto-charge.

[0113] [5-3. Variation 3] For example, in the embodiment, a case has been described in which auto-charge is not performed on days other than when regular payments do not occur, but on other days, auto-charge may be performed based on default auto-charge settings. The default auto-charge settings are assumed to be stored in the electronic money database DB1. The default auto-charge settings may be specified by the user or may be automatically determined by the payment service side based on the user's past charge history, etc. For example, the default auto-charge settings indicate the charge method, charge threshold, and post-charge balance, similar to the auto-charge settings associated with the payment date.

[0114] The auto-charge execution unit 102 of the third modification executes auto-charge on days other than the plurality of payment dates based on another auto-charge setting that is different from the auto-charge settings associated with each of the plurality of payment dates. The other days are days on which no periodic payments occur. In the example of FIG. 3, the other days are days other than the 5th, 13th, and 25th of each month. In the third modification, the other auto-charge setting is the default auto-charge setting, but multiple other auto-charge settings may exist depending on the time of the other days. For example, a default auto-charge setting for the first half of the month and a default auto-charge setting for the second half of the month may be defined separately.

[0115] The autocharge system 1 of the third modification example performs autocharge on days other than the plurality of payment dates based on an autocharge setting that differs from the autocharge setting associated with each of the plurality of payment dates. This allows for more flexible autocharge on days when no regular payments occur, thereby improving user convenience.

[0116] [5-4. Variation 4] For example, if a user registers as a member of many regular payment services, managing auto-charge settings can become complicated. Therefore, it may be possible to check the auto-charge settings associated with each payment date in calendar format. The auto-charge system 1 of Variation 4 includes a first display control unit 104. The first display control unit 104 displays a calendar screen showing the auto-charge settings associated with each of multiple payment dates. Various layouts can be used for the calendar itself.

[0117] FIG. 9 is a diagram showing an example of a calendar screen displayed on the user terminal 30 in Modification 4. Modification 4 describes a case in which the first display control unit 104 displays the calendar screen G5 using a payment service application, but the first display control unit 104 may also display the calendar screen G5 using a browser. For example, the first display control unit 104 obtains auto-charge settings associated with the user's monthly payment date based on the electronic money database DB1. The first display control unit 104 identifies the user's monthly payment schedule based on the electronic money database DB1.

[0118] For example, the first display control unit 104 generates display data for a calendar screen G5 that includes the user's monthly auto-charge settings and the user's monthly payment schedule. The calendar screen G5 shows the relationship between the user's payment date, auto-charge settings, and payment details. The display data may be in any format defined by the application. If a browser is used, the display data may be in HTML format. The first display control unit 104 displays the calendar screen G5 by transmitting display data for the calendar screen G5 to the user terminal 30. The auto-charge settings may be changeable from the calendar screen G5.

[0119] The auto-charge system 1 of the fourth modification displays a calendar screen G5 showing auto-charge settings associated with each of a plurality of payment dates. This makes it easier for the user to manage their monthly auto-charge settings using an intuitive image such as the calendar screen G5.

[0120] [5-5. Variation 5] For example, in the embodiment, a case has been described in which the need for auto-charge is determined every hour on a payment date, but the auto-charge execution unit 102 may execute auto-charge just before the payment time on each of multiple payment dates based on the auto-charge settings associated with that payment date. In Variation 5, a case has been described in which the need for auto-charge is determined only just before the payment time on a payment date, but by combining the embodiment and Variation 5, the need for auto-charge may be determined every hour on a payment date, and also just before the payment time.

[0121] "Immediately before the payment time" refers to a time within a predetermined time of the payment time. In Variation 5, as in the embodiment, the payment time is assumed to be 10:00 AM. Furthermore, "immediately before the payment time" is assumed to be 9:55 AM. The time interval between the payment time and the time immediately before the payment time may be any length and is not limited to 5 minutes. For example, these time intervals may be several seconds to several tens of seconds, one minute to several minutes, or longer than 5 minutes. However, if these time intervals are too long, there is a possibility that the balance after auto-charge will be used, resulting in a balance shortage, so they should be relatively short.

[0122] The auto-charge execution unit 102 determines whether the timing just before the payment time (9:55 AM on the payment date in variant 5) has arrived on each of the multiple payment dates. If the auto-charge execution unit 102 determines that the timing just before the payment time has not arrived, it does not execute auto-charge, but if it determines that the timing just before the payment time has arrived, it executes auto-charge. Only the timing at which auto-charge is executed differs from the embodiment, and the method of executing auto-charge itself is as described in the embodiment.

[0123] The auto-charge system 1 of Variation 5 executes auto-charge immediately before the payment time on each of multiple payment dates based on the auto-charge settings associated with that payment date. This ensures that auto-charge is executed immediately before the payment time, more reliably preventing insufficient balance at the time of payment. For example, this makes it easier to prevent a situation where a user uses electronic money for shopping at an e-commerce service after auto-charge is executed, resulting in insufficient balance at the time of payment.

[0124] [5-6. Variation 6] For example, with periodic payments, the payment amount is not fixed and may vary from month to month. In Variation 6, electricity services and communications services will be described as examples of periodic payment services with non-fixed payment amounts. With electricity services, monthly payments are made for electricity bills that vary depending on the amount of electricity used. With communications services, monthly payments are made for communications bills that vary depending on the amount of telephone or packet data used. With such periodic payment services, the payment amount varies depending on the user's usage, so the monthly payment amount may be predicted in advance and an auto-charge setting based on the predicted value may be saved.

[0125] The auto-charge system 1 of variant 6 includes a prediction unit 105 and a determination unit 106. The electronic money database DB1 of variant 6 is assumed to store past payment records by individual users. The payment record is the result of payments made in the past. For example, the past payment date and payment amount for each periodic payment service are assumed to be stored in the electronic money database DB1 as payment records. When the payment execution unit 103 executes a payment for a certain periodic payment service for a certain user, it associates the user ID of the user, the name of the periodic payment service, the payment date, and the payment amount and stores them in the electronic money database DB1.

[0126] The prediction unit 105 predicts the next payment amount of a periodic payment based on the payment history of the periodic payment for each of multiple payment dates for which the payment amount is not fixed. For example, the prediction unit 105 predicts the next payment amount of a certain user by calculating the average of past payment amounts based on the payment history of the user. The average may be a simple average or a weighted average in which the weight coefficient increases the closer to the present. The payment history used to predict the next payment amount may be the entire past period or a recent specified period (e.g., approximately six months). Furthermore, the prediction unit 105 may predict the next payment amount based on the payment amount for the same month last year instead of the average.

[0127] The determination unit 106 determines the content of the auto-charge setting to be associated with the payment date of a periodic payment for which the payment amount is not fixed, based on the next payment amount predicted by the prediction unit 105. For example, the determination unit 106 determines the content of the auto-charge setting so that the post-charge balance is equal to or greater than the next payment amount predicted by the prediction unit 105. This post-charge balance may be the same as the next payment amount, or may be an amount specified by the user or an amount with a predetermined margin. The storage unit 101 of the sixth modification stores the auto-charge setting determined by the determination unit 106. The method of executing auto-charge itself may be the same as the embodiment and modifications 1 to 5.

[0128] The autocharge system 1 of the sixth variation predicts the next payment amount for a periodic payment that does not have a fixed payment amount based on the payment history of the periodic payment. Based on the predicted next payment amount, the autocharge system 1 determines the content of the autocharge setting to be associated with the payment date of the periodic payment that does not have a fixed payment amount. This allows the autocharge setting to be set so that the balance is less likely to run out even if the payment amount is not fixed, thereby increasing user convenience.

[0129] [5-7. Variation 7] For example, periodic payments may be made using electronic money in combination with other payment methods. The other payment method may be any payment method other than electronic money that is eligible for auto-charge. For example, the other payment method may be a credit card, a bank account, an account at another financial institution, cryptocurrency, points, other electronic money, a debit card, or proceeds from sales at a flea market service. For example, if a user wishes to use electronic money in combination with other payment methods when registering as a member of the periodic payment service, the electronic money and other payment methods are used in combination. The user may specify one of multiple other payment methods to be used in combination with electronic money. The payment amount stored in the electronic money database DB1 is the portion of the payment amount for the periodic payment service that is paid with electronic money.

[0130] The storage unit 101 of the seventh modification is capable of storing, among multiple payment dates, a payment date for a periodic payment that can use both electronic money and other payment methods, in association with an auto-charge setting corresponding to a portion of the payment amount for the periodic payment. The portion of the payment amount is the portion of the payment amount that is paid with electronic money. The remaining portion of the payment amount is paid with other payment methods. In the seventh modification, a credit card is described as an example of other payment methods. There may be two or more other payment methods. The user can freely specify how much of the payment amount is paid with electronic money.

[0131] For example, if 700 yen of a 1,000 yen payment is paid with electronic money and the remaining 300 yen with a credit card, part of the payment amount is 700 yen. For example, the storage unit 101 stores an auto-charge setting that indicates a post-charge balance of at least part of the payment amount. Only the content of the auto-charge setting differs from the embodiment, and the format of the auto-charge setting and the method of executing the auto-charge are the same as those of the embodiment. The payment execution unit 103 may execute credit card payment processing so that the remaining part of the payment amount is paid with a credit card, or payments made with other payment methods may be executed as processing on the service provider server 20 side. Payments on all payment dates do not need to be executed in combination with other payment methods; payments on some payment dates may be executed in combination with other payment methods.

[0132] The auto-charge system 1 of the seventh modification can associate and save a payment date for a periodic payment that can use electronic money in combination with other payment methods, among multiple payment dates, with an auto-charge setting that corresponds to a portion of the payment amount for that periodic payment. This allows payments using multiple payment methods in combination, improving user convenience. Even when multiple payment methods are used in combination, it is possible to ensure that there is no shortage of electronic money to pay.

[0133] [5-8. Variation 8] For example, in the sixth modification, a case where the next payment amount for a periodic payment in which the payment amount is not fixed is predicted is described, but there may be a certain amount of time between the determination of the next payment amount and the arrival of the payment time on the payment date. If the electronic money server 10 can receive the determined next payment amount from the service provider server 20 during this time, the auto-charge setting may be saved based on the next payment amount received from the service provider server 20 without predicting the next payment amount.

[0134] In the eighth modification, the storage unit 101 stores, among the multiple payment dates, an auto-charge setting corresponding to a periodic payment amount after the payment amount for the periodic payment is determined, in association with the determined payment amount. When the payment amount for the periodic payment service that the service provider server 20 provides is determined, the service provider server 20 stores the payment amount in the service database DB2. For example, the payment amount may be uploaded to the service provider server 20 by a person related to the service provider, or may be automatically determined based on the user's usage of the periodic payment service.

[0135] For example, the service provider server 20 transmits a list of users to whom payments are to be made and the confirmed next payment amounts to the electronic money server 10. When the electronic money server 10 receives the list from the service provider server 20, it refers to the list and identifies the next payment amount for each user. The storage unit 101 stores the auto-charge settings so that the post-charge balance will be equal to or greater than the received payment amount. The method of executing auto-charge itself is the same as in the embodiment.

[0136] In the autocharge system 1 of the eighth modification, when a payment date is a periodic payment date where the payment amount is not fixed among the multiple payment dates, after the payment amount for the periodic payment is determined, the autocharge setting corresponding to the determined payment amount is associated and saved. This more reliably prevents insufficient balance for the next payment, improving user convenience.

[0137] [5-9. Variation 9] For example, in the embodiment, a case has been described in which the auto-charge setting is specified on the auto-charge setting screen G3 displayed on the payment service side, but the auto-charge setting may also be specified on a screen displayed on the periodic payment service side. In this case, the electronic money server 10 may receive a notification from the service provider server 20 indicating that the user has agreed to the auto-charge setting. This notification may include the content of the auto-charge setting specified by the user.

[0138] In the ninth modification, after the member registration screen G2 is displayed, an auto-charge setting screen G3 is displayed on the display unit 35 as a screen on the periodic payment service side. For example, the auto-charge setting screen G3 is displayed on the application of the periodic payment service. When a browser is used, the auto-charge setting screen G3 is displayed as a page of the domain of the periodic payment service. When it is necessary to display the balance of electronic money on the auto-charge setting screen G3, the user may log in to the payment service, and the user's balance of electronic money may be sent to the service provider server 20.

[0139] The auto-charge system 1 of the ninth modification includes a receiving unit 107. The receiving unit 107 further includes a receiving unit 107 that receives a predetermined notification when an operation to agree to the auto-charge setting is performed in the payee's regular payment service. This operation may be a predetermined operation indicating agreement to the auto-charge setting. For example, when the charge method, charge threshold, and post-charge balance have been specified, the operation of selecting button B33 corresponds to the operation to agree to the auto-charge setting.

[0140] The predetermined notification is a notification indicating that the user has agreed to the auto-charge setting on the periodic payment service side. The predetermined notification is sent by sending data in a predetermined format. The predetermined notification includes the auto-charge setting specified by the user. When the storage unit 101 receives the predetermined notification, it stores the auto-charge setting. The notification includes the user ID of the payment service. The storage unit 101 can identify which user's auto-charge setting it is from this user ID. The storage unit 101 stores the auto-charge setting included in the notification. The content of the auto-charge setting itself may be the same as in the embodiment.

[0141] The auto-charge system 1 of Variation 9 saves the auto-charge setting when it receives a predetermined notification sent when an operation to agree to the auto-charge setting is performed in the recurring payment service. This allows the auto-charge setting to be completed seamlessly on the recurring payment service side, improving user convenience. For example, the auto-charge setting can be completed without the payment service application launching midway or being redirected to the payment service's page.

[0142] [5-10. Variation 10] For example, electronic money can be used for payments other than regular payments. In this case, it becomes difficult for the user to manage the amount of electronic money used for regular payments. Therefore, a screen that distinguishes between the payment amounts for regular payments and the payment amounts for other payments may be displayed. The auto-charge system 1 includes a second display control unit 108. The second display control unit 108 displays a payment amount screen that distinguishes between the payment amounts for regular payments on each of a plurality of payment dates and the payment amounts for payments other than regular payments. Distinguishing between these amounts means displaying each payment amount separately.

[0143] FIG. 10 is a diagram showing an example of a payment amount screen. For example, the payment amount screen G6 displays the total amount of payments for periodic payments and the total amount of payments for other payments separately. In the example of FIG. 10, a case is described in which both the total amount and individual breakdowns are displayed on the payment amount screen G6, but only either the total amount or the individual breakdowns may be displayed on the payment amount screen G6. The total amount is calculated monthly, but the user may be able to specify any calculation period. For example, the total amount for each week or each half-year may be displayed on the payment amount screen G6.

[0144] In Modification 10, the electronic money database DB1 stores the electronic money usage history. The usage history includes information that can identify whether the payment is a regular payment or another payment. The electronic money server 10 stores the usage history in the electronic money database DB1 each time electronic money is used. The second display control unit 108 tallies the total amount of payments for regular payments and the total amount of payments for other payments based on the electronic money usage history. Based on these tallies, the second display control unit 108 generates display data for the payment amount screen G6 and transmits it to the user terminal 30.

[0145] The auto-charge system 1 of the tenth modification displays a payment amount screen G6 that distinguishes between the payment amounts for regular payments and payments other than regular payments on each of a plurality of payment dates. This reduces the administrative burden on the user for managing the payment amounts for regular payments.

[0146] [5-11. Variation 11] For example, in the embodiment, a case where auto-charge is performed based on one charge method has been described, but auto-charge may be performed using multiple charge methods in combination. The charge methods that can be used in combination for auto-charge may be a combination of the various methods described in the embodiment. The storage unit 101 of the eleventh modification example can store each of multiple payment dates in association with an auto-charge setting that indicates a combination of multiple charge methods.

[0147] The auto-charge setting of Modification 11 indicates multiple charge methods. The charge amount for each charge method may be specified separately, or multiple charge methods may be prioritized. When the auto-charge setting indicates a combination of multiple charge methods, the auto-charge execution unit 102 of Modification 11 executes auto-charge based on the multiple charge methods. The user can specify at their discretion whether to use multiple charge methods in combination.

[0148] 3, assume that the auto-charge settings for the 5th of each month indicate the use of both a credit card and a bank account. For example, if the auto-charge settings indicate that 70% of the charge amount is to be charged to the credit card and 30% is to be charged to the bank account, the auto-charge execution unit 102 executes auto-charge so that 70% of the required charge amount is charged to the credit card and 30% of the required charge amount is charged to the bank account.

[0149] For example, if multiple charging methods are prioritized, the auto-charge execution unit 102 attempts auto-charge in descending order of priority. If auto-charge fails using a charging method with a certain priority, the auto-charge execution unit 102 attempts auto-charge using the charging method with the next highest priority. In the same manner, the auto-charge execution unit 102 continues to attempt auto-charge in descending order of priority until auto-charge is successful.

[0150] For example, in the example of Figure 3, assume that the auto-charge settings for the 5th of each month specify that a credit card is the first priority and a bank account is the second. If the auto-charge execution unit 102 attempts and succeeds in auto-charge using a credit card, it will not execute auto-charge using a bank account. If auto-charge fails due to insufficient credit card credit, for example, the auto-charge execution unit 102 will execute auto-charge using a bank account, which is the next priority.

[0151] The auto-charge system 1 of the eleventh modification is capable of storing multiple payment dates in association with auto-charge settings that indicate a combination of multiple charging methods. When the auto-charge settings indicate a combination of multiple charging methods, the auto-charge system 1 executes auto-charge based on the multiple charging methods. This allows for flexible auto-charge that combines multiple charging methods.

[0152] [5-12. Modifications regarding other configurations] For example, the present disclosure includes configurations that solve problems other than the configuration that solves the problem of "improving user convenience when periodic payments to different payees occur on multiple payment dates." Therefore, the present disclosure also includes configurations described in Modifications 1 to 11 that do not assume the configurations described in the embodiments. Hereinafter, configurations that do not assume the configurations described in the embodiments will be described as modifications of Modifications 1 to 11.

[0153] [Modification regarding Modification 1] For example, in Modification 1, there may not be multiple payment dates on which periodic payments to different payees occur. Multiple periodic payments to different payees may occur on a single payment date. In the example described in Modification 1, payment for the e-book service on the 25th of each month may not occur. In this case, the only monthly payments are for the music distribution service and video distribution service on the 5th of each month, so there is only one payment date in a month.

[0154] For example, the storage unit 101 stores an auto-charge setting for the 5th of each month, such as "When the balance falls below 3,500 yen, the balance will be set to 4,100 yen" according to the total amount of the payment for the music distribution service and the payment for the video distribution service. The auto-charge setting does not need to be stored on days other than the 5th of each month. In this case, auto-charge will be executed only once a month.

[0155] Furthermore, multiple periodic payments may occur to the same payee on a single payment date. For example, the service provider of a music distribution service and the service provider of a video distribution service may be the same. In this case, payments to multiple periodic payment services provided by the same payee occur on the 5th of each month. The storage unit 101 may store an auto-charge setting, such as "when the balance falls below 3,500 yen, the balance will be increased to 4,100 yen," according to the total amount of multiple periodic payments to the same payee.

[0156] Auto-charge system 1, a variation of variation 1, stores auto-charge settings according to the total amount of multiple periodic payments that occur on one payment date, thereby reliably preventing insufficient balances even if multiple periodic payments occur on one payment date, thereby increasing user convenience. Auto-charge settings are consolidated within one payment date, eliminating the need to manage multiple auto-charge settings, thereby reducing the burden of managing auto-charge settings.

[0157] [Modification regarding Modification 2] For example, similar to the modification related to modification 1, the configuration of modification 2 does not need to have multiple payment dates on which periodic payments to different payees occur. For example, monthly payments may be made only on the 5th of each month for the music distribution service and the video distribution service. In this case, too, if the payment time for the music distribution service and the payment time for the video distribution service are different, the storage unit 101 may store the auto-charge settings up to each payment time separately, as in modification 2.

[0158] For example, in Modification 2, similar to the modification related to Modification 1, multiple periodic payments to the same payee may occur on one payment date. For example, even if the same service provider provides a music distribution service and a video distribution service, the storage unit 101 may store separate auto-charge settings at the respective payment times for the music distribution service and the video distribution service provided by the same service provider, as in Modification 2.

[0159] The auto-charge system 1 of the modified example related to the modified example 2 enables flexible auto-charge by saving separate auto-charge settings for each payment time when multiple regular payments occur on one payment date and the payment times for each of the multiple regular payments are different from each other.

[0160] [Modification regarding Modification 3] For example, the configuration of Modification 3, like the modifications related to Modifications 1 and 2, does not need to have multiple payment dates on which periodic payments are made to different payees. For example, there may only be a monthly payment for a music distribution service on the 5th of each month. In this case, the auto-charge execution unit 102 may execute auto-charge based on the default auto-charge setting for days other than the 5th of each month.

[0161] For example, in Modification 3, periodic payments to the same payee may occur on multiple payment dates. The music distribution service on the 5th of each month, the video distribution service on the 13th of each month, and the e-book service on the 25th of each month may all be provided by the same service provider. In this case, the auto-charge execution unit 102 may execute auto-charge based on the default auto-charge settings on days other than the 5th, 13th, and 25th of each month.

[0162] The modified auto-charge system 1 relating to variant example 3 can perform auto-charge based on the default auto-charge settings when there are days in a certain period when no regular payments occur, thereby enabling more flexible auto-charge and increasing user convenience.

[0163] [Modification regarding Modification 4] For example, the configuration of Modification 4, like the modifications related to Modifications 1 to 3, does not necessarily require that there be multiple payment dates on which periodic payments to different payees occur. For example, even if there is only one payment date each month, it may be possible to display a calendar like Modification 4. In addition, for example, it may also be possible to display a calendar like Modification 4 even if periodic payments to the same payee occur on multiple payment dates.

[0164] The auto-charge system 1 of the modified example related to the modified example 4 makes it easier to manage the monthly auto-charge settings by displaying a calendar screen G5 showing the auto-charge settings associated with at least one payment date.

[0165] [Modification regarding Modification 5] For example, the configuration of Modification 5 does not need to have multiple payment dates on which periodic payments to different payees occur, as in the modifications related to Modifications 1 to 4. For example, even if there is only one payment date each month, the auto-charge execution unit 102 may execute auto-charge immediately before the payment time, as in Modification 5, based on the auto-charge setting associated with the only payment date each month.

[0166] For example, even when periodic payments to the same payee occur on multiple payment dates, the auto-charge execution unit 102 may execute auto-charge based on the auto-charge setting associated with each payment date just before the payment time on that payment date, as in Variation Example 5. When multiple periodic payments occur in a single day and the payment times for each payment are different, the auto-charge execution unit 102 may execute auto-charge just before each payment time based on the auto-charge setting associated with that payment time.

[0167] The auto-charge system 1 of the modified example related to the modified example 5 executes auto-charge immediately before the payment time on at least one payment date based on the auto-charge setting associated with that payment date. Because auto-charge is executed immediately before the payment time, it is possible to more reliably prevent a shortage of balance at the time of payment.

[0168] [Modification regarding Modification 6] For example, similar to the modifications related to modifications 1 to 5, the configuration of modification 6 does not require that there be multiple payment dates on which periodic payments to different payees occur. For example, even if there is only one payment date each month, the prediction unit 105 may predict the next payment amount based on past payment records. The determination unit 106 may determine the content of the auto-charge settings based on the next payment amount predicted by the prediction unit 105, even if there is only one payment date each month.

[0169] For example, even when periodic payments to the same payee occur on multiple payment dates, the prediction unit 105 may predict the next payment amount based on past payment records. Even when periodic payments to the same payee occur on multiple payment dates, the determination unit 106 may determine the content of the auto-charge settings based on the next payment amount predicted by the prediction unit 105.

[0170] In the auto-charge system 1 of the modified example related to the modified example 6, when the payment amount of a periodic payment on at least one payment date is not fixed, the auto-charge setting is determined by predicting the next payment amount. This allows the auto-charge setting to be set so that the balance is less likely to run out even if the payment amount is not fixed, thereby increasing user convenience.

[0171] [Modification regarding Modification 7] For example, the configuration of Modification 7, like the modifications related to Modifications 1 to 6, does not need to have multiple payment dates on which periodic payments to different payees occur. For example, even if there is only one payment date per month, it may be possible to use electronic money and other payment methods in combination for the payment that occurs only once per month. The storage unit 101 may store the payment date that occurs only once per month in association with an auto-charge setting that corresponds to a portion of the payment amount for a payment using electronic money and other payment methods in combination.

[0172] For example, even if regular payments to the same payee occur on multiple payment dates, the storage unit 101 may store the payment date in association with an auto-charge setting corresponding to a portion of the payment amount for a payment using electronic money and another payment method in combination, as long as a combined payment is possible on at least one payment date.

[0173] The auto-charge system 1 of the modified example related to variant example 7 stores auto-charge settings according to the amount of electronic money to be paid when payment using electronic money in combination with other payment methods is possible on at least one payment date, thereby preventing a shortage of electronic money to be paid even when multiple payment methods are used in combination.

[0174] [Modification regarding Modification 8] For example, the configuration of Modification 8 may not require multiple payment dates on which periodic payments to different payees occur, as in the modifications related to Modifications 1 to 7. For example, even if there is only one payment date each month, the storage unit 101 may store an auto-charge setting corresponding to the periodic payment amount after the payment amount has been determined.

[0175] For example, even when periodic payments to the same payee occur on multiple payment dates, if the payment amount for at least one payment date is not fixed, the storage unit 101 may store the payment date and the auto-charge setting corresponding to the determined payment amount after the payment amount for that payment has been determined, in association with each other.

[0176] In the auto-charge system 1 of the modification relating to the modification 8, if the payment amount for at least one payment date is not fixed, after the payment amount for that payment is determined, the auto-charge setting corresponding to the determined payment amount is saved. This more reliably prevents the balance from being insufficient for the next payment, improving user convenience.

[0177] [Modification regarding Modification 9] For example, similar to the modifications related to modifications 1 to 8, the configuration of modification 9 does not require that there be multiple payment dates on which periodic payments to different payees occur. For example, even if there is only one payment date each month, receiving unit 107 may receive a notification when an operation to consent to the auto-charge setting is performed on the payee's service provider server 20. For example, receiving unit 107 may receive a notification in the same manner even if periodic payments to the same payee occur on multiple payment dates.

[0178] Furthermore, the recurring payment service may enable auto-charge settings on the condition that the user information registered with the settlement service matches the user information registered with the recurring payment service. The user information may be any information about the user, such as name, email address, address, telephone number, or user ID. In this case, the auto-charge setting is not set when registering as a member of the recurring payment service, but after registering as a member of the recurring payment service.

[0179] In the autocharge system 1 of the modification relating to the modification 9, the periodic payment service sets up the autocharge associated with at least one payment date. This allows the autocharge setting to be completed seamlessly on the periodic payment service side, improving user convenience.

[0180] [Modification regarding Modification 10] For example, the configuration of Modification 10, like the modifications related to Modifications 1 to 9, does not need to include multiple payment dates on which periodic payments to different payees occur. For example, even if there is only one payment date each month, the second display control unit 108 may display a payment amount screen G6 that distinguishes between the payment amount for the payment that occurs only once each month and the payment amounts for other payments. For example, the second display control unit 108 may similarly display the payment amount screen G6 even if periodic payments to the same payee occur on multiple payment dates.

[0181] Furthermore, if the user earns points when electronic money is selected as the payment method for the periodic payment service, the second display control unit 108 may display on the payment amount screen G6 how many points the user has earned by selecting electronic money as the payment method. In this case, the second display control unit 108 may display on the payment amount screen G6 the points earned for each periodic payment service. The points earned by paying for the periodic payment service are assumed to be stored in the electronic money database DB1.

[0182] The auto-charge system 1 of the modified example related to the modified example 10 can reduce the management burden on the user by displaying a payment amount screen G6 that distinguishes between the payment amount for at least one payment date and the payment amount for other payments.

[0183] [Modification regarding Modification 11] For example, the configuration of Modification 11, like the modifications related to Modifications 1 to 10, does not require that there be multiple payment dates on which periodic payments to different payees occur. For example, even if there is only one payment date each month, storage unit 101 may store auto-charge settings so that multiple charge methods are used in combination on the payment date that only occurs once each month. For example, storage unit 101 may similarly store auto-charge settings so that multiple charge methods are used in combination even if periodic payments to the same payee occur on multiple payment dates.

[0184] The auto-charge system 1 of the modification relating to the modification 11 associates and stores at least one payment date with an auto-charge setting indicating that multiple charging methods are to be used in combination. This allows for flexible auto-charge that combines multiple charging methods.

[0185] [5-13. Other variations] For example, the above-described modifications may be combined.

[0186] For example, a periodic payment service may be a service in which a paid member pays a regular membership fee. For example, if an upper limit is set for the auto-charge amount for each month, the relationship between the current auto-charge amount and the upper limit may be displayed on the payment amount screen G6 or another screen. For example, if an auto-charge is to be prevented from being performed for a certain period of time after being performed, this restriction may be lifted immediately before the payment time.

[0187] For example, a periodic payment may be a payment between individuals, rather than a payment to a service provider. In this case, the periodic payment may also be a periodic remittance. For example, a similar auto-charge mechanism can be used when a user sends money to their parents using electronic money. Furthermore, a periodic payment may not be performed automatically, but may be performed when the user performs a payment operation. In this case, the user performs a payment operation on a regular basis.

[0188] For example, instead of having an auto-charge setting for each payment date, an auto-charge setting may be set for each payee. In this case, if a payment is made to a specific payee, auto-charge will be performed based on the auto-charge setting associated with that payee. For example, there may be types of electronic money that allow withdrawals and types that do not allow withdrawals. The auto-charge setting may indicate which type of electronic money is to be auto-charged.

[0189] For example, a function described as being realized by the electronic money server 10 may be realized by the service provider server 20 or another server computer. A function described as being realized by the service provider server 20 may be realized by the electronic money server 10 or another server computer. For example, a function described as being realized by the electronic money server 10 or the service provider server 20 may be shared among multiple computers. Each function may be realized by at least one computer.

[0190] [6. Notes] For example, the auto-charging system according to the present disclosure can be configured as follows: (1) a storage unit that stores, in association with each other, a plurality of payment dates on which periodic payments to different payees occur and auto-charge settings for auto-charge of payment methods that can be used for the periodic payments; an auto-charge execution unit that executes the auto-charge based on the auto-charge settings associated with each of the plurality of payment dates; Includes an auto-charge system. (2) When a plurality of the periodic payments occur on one of the payment dates, the storage unit stores the one payment date in association with the auto-charge setting corresponding to the total amount of the payment for each of the plurality of periodic payments. (1) An auto-charge system as described above. (3) the storage unit stores the auto-charge setting separately for each payment time when a plurality of periodic payments occur on one payment date and the payment times of the plurality of periodic payments are different from each other within the one payment date; the auto-charge execution unit executes the auto-charge based on the auto-charge setting associated with a predetermined payment time among the plurality of periodic payments until the predetermined payment time, and when the predetermined payment time has passed, executes the auto-charge based on the auto-charge setting associated with the next payment time among the plurality of periodic payments; An auto-charge system according to (1) or (2). (4) the auto-charge execution unit executes the auto-charge on a day other than the plurality of payment dates based on another auto-charge setting other than the auto-charge setting associated with each of the plurality of payment dates; An auto-charge system according to any one of (1) to (3). (5) The auto-charge system further includes a first display control unit that displays a calendar screen showing the auto-charge settings associated with each of the plurality of payment dates. An auto-charge system according to any one of (1) to (4). (6) The storage unit stores each of the plurality of payment dates in association with the auto-charge setting indicating a post-charge balance equal to or greater than the payment amount in the periodic payment on the payment date; the auto-charge execution unit executes the auto-charge so that the post-charge balance becomes the balance indicated in the auto-charge setting associated with each of the plurality of payment dates. An auto-charge system according to any one of (1) to (5). (7) the auto-charge execution unit executes the auto-charge based on the auto-charge setting associated with each of the plurality of payment dates before the payment time on that payment date arrives; An auto-charge system according to any one of (1) to (6). (8) When each of the plurality of payment dates arrives, the auto-charge execution unit determines whether or not the auto-charge is necessary at each predetermined time until the payment time based on the auto-charge setting associated with the payment date. (7) An auto-charge system as described above. (9) the auto-charge execution unit executes the auto-charge immediately before the payment time on each of the plurality of payment dates based on the auto-charge setting associated with the payment date; An auto-charge system according to (7) or (8). (10) The auto-charging system includes: a prediction unit that predicts the next payment amount of the periodic payments based on the payment history of the periodic payments whose payment amounts are not fixed, among the periodic payments on each of the plurality of payment dates; a determination unit that determines, based on the next payment amount predicted by the prediction unit, the content of the auto-charge setting to be associated with the payment date of the periodic payment whose payment amount is not fixed; The auto-charging system according to any one of (1) to (9), further comprising: (11) The storage unit is capable of storing, among the plurality of payment dates, the payment date of the periodic payment for which the payment means can be used in combination with another payment means, in association with the auto-charge setting corresponding to a portion of the payment amount of the periodic payment. The auto-charge system according to any one of (1) to (10). (12) The storage unit stores, on the payment date of the periodic payment for which the payment amount is not fixed among the plurality of payment dates, the auto-charge setting corresponding to the determined payment amount after the payment amount of the periodic payment is determined. An auto-charge system according to any one of (1) to (11). (13) The auto-charge system further includes a receiving unit that receives a predetermined notification when an operation for agreeing to the auto-charge setting is performed in the service of the payee, The storage unit stores the auto-charge setting when the notification is received. An auto-charge system according to any one of (1) to (12). (14) The auto-charge system further includes a second display control unit that displays a payment amount screen that distinguishes between the payment amount of the regular payment on each of the plurality of payment dates and the payment amount of other payments different from the regular payment. An auto-charge system according to any one of (1) to (13). (15) The storage unit stores each of the plurality of payment dates in association with the auto-charge setting indicating a charging method selected from a plurality of charging methods. An auto-charge system according to any one of (1) to (14). (16) The storage unit is capable of storing each of the plurality of payment dates and the auto-charge setting indicating a combination of a plurality of charging methods in association with each other, When the auto-charge setting indicates a combination of the plurality of charge methods, the auto-charge execution unit executes the auto-charge based on the plurality of charge methods. An auto-charge system according to any one of (1) to (15). [Explanation of symbols]

[0191] 1 Auto-charge system, N network, 10 electronic money server, 11, 21, 31 control unit, 12, 22, 32 memory unit, 13, 23, 33 communication unit, 20 service provider server, 30 user terminal, 34 operation unit, 35 display unit, G1 top screen, G2 member registration screen, G3 auto-charge setting screen, G4 member registration completion screen, G5 calendar screen, G6 payment amount screen, 100 data storage unit, 101 storage unit, 102 auto-charge execution unit, 103 payment execution unit, 104 first display control unit, 105 prediction unit, 106 determination unit, 107 receiving unit, 108 second display control unit, 200 data storage unit, 201 service provision unit, 300 data storage unit, 301 display control unit, 302 operation reception unit, B10, B33 button, B22 radio button, DB1 Electronic money database, DB2 service database, F20, F30, F31, F32, input form, F50 input form, L11 link.

Claims

1. An application installed on a user's terminal, which allows a user to register to use a service that generates periodic payments and allows the use of both electronic money and points, comprising: a display control unit that displays a calendar screen showing the payment schedule; a storage unit that stores an auto-charge setting related to auto-charge of the electronic money that can be used for the periodic payment, the auto-charge setting indicating a selected charging method from a plurality of charging methods including a bank account, and that stores the auto-charge setting specified by the application; an auto-charge execution unit that executes the auto-charge based on the auto-charge setting; Includes an auto-charge system.

2. the auto-charge system further includes an awarding unit that, when the electronic money is selected as the payment method for the periodic payment, awards the points generated in the payment to the user; The auto-charging system according to claim 1.

3. The auto-charging system includes: a reception unit that receives a selection of one of a plurality of payment methods that can be used for the periodic payment, the plurality of payment methods including the electronic money and the points; a payment execution unit that executes the periodic payment based on the payment method selected from the plurality of payment methods; The auto-charging system according to claim 1 or 2, further comprising:

4. the display control unit displays the calendar screen showing a schedule of the periodic payments in financial services; the storage unit stores the auto-charge setting of the electronic money that can be used for the periodic payment in the financial service.

3. The auto-charging system according to claim 1 or 2.

5. The storage unit stores the recharge amount in the auto-recharge as the auto-recharge setting, The auto-charge execution unit executes the auto-charge based on the charge amount.

3. The auto-charging system according to claim 1 or 2.

6. the display control unit displays the calendar screen showing a schedule of each of the plurality of periodic payments occurring in one month; 3. The auto-charging system according to claim 1 or 2.

7. the display control unit displays the calendar screen showing a schedule of each of the plurality of periodic payments having different cycles; 3. The auto-charging system according to claim 1 or 2.

8. The computer a display control step of displaying a calendar screen showing the payment schedule in an application installed on a user terminal of a user, the application allowing registration for use to be able to use a service that generates periodic payments and allows the use of electronic money and points in combination; a saving step of saving an auto-charge setting related to auto-charge of the electronic money available for the periodic payment, the auto-charge setting indicating a selected charging method from a plurality of charging methods including a bank account, and the auto-charge setting specified by the application; an auto-charge execution step of executing the auto-charge based on the auto-charge setting; An auto-charge method that performs the following.

9. An application installed on a user's terminal, the application allowing registration to use a service that generates periodic payments and allows the use of both electronic money and points, the application comprising: a display control unit that displays a calendar screen showing the payment schedule; a storage unit that stores an auto-charge setting related to auto-charge of the electronic money that can be used for the periodic payment, the auto-charge setting indicating a selected charging method from a plurality of charging methods including a bank account, and that stores the auto-charge setting specified by the application; an auto-charge execution unit that executes the auto-charge based on the auto-charge setting; A program that allows a computer to function as a

Images