JP2024012704A - Auto-charge system, method for auto-charge, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: 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

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present disclosure relates to an auto-charge system, an auto-charge method, and a program.

In recent years, efforts have been made to improve convenience for users of payment services. For example, Patent Document 1 states that when a user purchases a product at a store, the purchase price is not deducted from the balance of the payment method such as electronic money, but the payment amount is calculated by adding up the usage amount on the monthly payment date. The periodic balance payment that is to be deducted all at once is listed. With regular balance payments, if the balance in your payment method is insufficient, automatic charging will be performed to make up for the shortage.

JP2021-096746A

For example, if it becomes possible to use payment methods such as electronic money for periodic payments such as subscriptions, it is thought that convenience for users will increase. This also applies to periodic payments other than subscriptions. For example, if periodic payments to different payees occur on each of multiple payment dates, the user must manage the balance of the payment method so as not to run out of funds on each of the multiple payment dates. This is thought to increase the administrative burden on the user.

However, the technology of Patent Document 1 does not assume multiple payment dates in which regular payments are made to different payees, but rather makes up for the shortfall in the balance on the settlement date that comes once a month. It's just something that performs auto-charging. For this reason, with the conventional technology, it has not been possible to improve user convenience when regular payments to different payees occur on each of a plurality of payment dates.

One of the objectives of the present disclosure is to improve convenience for users when periodic payments to different payees occur on each of a plurality of payment dates.

The auto-charging system according to the present disclosure includes: each of a plurality of payment dates on which periodic payments to different payees occur; and auto-charging settings regarding auto-charging of payment means that can be used for the periodic payments; and 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.

According to the present disclosure, convenience for users is improved when regular payments to different payees occur on each of a plurality of payment dates.

It is a figure showing an example of the whole composition of an auto charge system. It is a diagram showing an example of the flow of membership registration for a music distribution service. It is a figure which shows an example of the schedule regarding a certain user's monthly payment. FIG. 2 is a functional block diagram showing an example of functions realized by the auto-charge system. It is a diagram showing an example of an electronic money database. FIG. 3 is a diagram showing an example of a service database. It is a figure showing an example of processing performed by an auto charge system. It is a figure which shows an example of the functional block in a modification. 12 is a diagram illustrating an example of a calendar screen displayed on a user terminal in Modification 4. FIG. It is a figure showing an example of a payment amount screen.

[1. Overall configuration of auto charge system]
An example of an embodiment of an auto-charging 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 is subject to automatic charging. For this reason, parts that describe electronic money can be read as payment means. The payment method is not limited to electronic money, as long as it has a balance that can be charged. For example, the payment instrument may be referred to as points, an account, a wallet, or some other name. A payment instrument may also be referred to as a payment instrument, an example of which is a prepaid payment instrument.

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, there may be one or more service provider servers 20.

The electronic money server 10 is a server computer of a payment provider. A payment service provider is a service provider that provides payment services related to electronic money. For example, the electronic money server 10 includes a control section 11, a storage section 12, and a communication section 13. Control unit 11 includes at least one processor. The storage unit 12 includes volatile memory such as RAM and nonvolatile 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.

The service provider server 20 is a server computer of a service provider. A service provider is a business that provides services that require periodic payments. Hereinafter, this service will be referred to as the periodic payment service. A periodic payment is a payment that occurs repeatedly at a predetermined period. In this embodiment, an example is given in which the periodic payment period is one month, but the periodic payment period may be of any length and is not limited to one month. For example, the periodicity of periodic payments may be one day, several days, one week, several weeks, several months, or one year.

In this embodiment, a subscription music distribution service, a video distribution service, and an electronic book service will be described as examples of regular 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 regular payment services. The periodic payment service may be any service and is not limited to the example of this embodiment. For example, a recurring payment service may be a communication service, an electricity service, an e-commerce service, or a financial service. Application examples of the auto-charge system 1 to other periodic payment services will be explained in the later-described modified examples.

In this embodiment, each of the music distribution service, video distribution service, and electronic book service is provided by different service providers. Therefore, it is assumed that three service provider servers 20 exist. For example, the service provider server 20 includes a control section 21, a storage section 22, and a communication section 23. The physical configurations of the control section 21, the storage section 22, and the communication section 23 may be the same as those of the control section 11, the storage section 12, and the communication section 13, respectively.

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 section 31, a storage section 32, a communication section 33, an operation section 34, and a display section 35. The physical configurations of the control section 31, the storage section 32, and the communication section 33 may be the same as those of the control section 11, the storage section 12, and the communication section 13, respectively. The operation unit 34 is an input device such as a touch panel or a mouse. The display section 35 is a liquid crystal display or an organic EL display.

Note that the programs stored in the storage units 12, 22, and 32 may be supplied via the network N. In addition, a program stored in a computer-readable information storage medium can be used as a reading section (for example, an optical disk drive or a memory card slot) for reading the information storage medium, or an input/output section for inputting and outputting data with external equipment. (e.g., a USB port).

Further, the auto-charge system 1 only needs to include at least one computer, and is not limited to the example shown in 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 include the electronic money server 10 and other server computers of the payment provider.

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

Online electronic money is electronic money that can be used in Internet services such as electronic commerce services or travel reservation services. Online electronic money may be available at physical stores. For example, online electronic money may be of a type that can be used at a physical store by reading a barcode or two-dimensional code. Hereinafter, online electronic money will be simply referred to as electronic money.

In this embodiment, a case will be exemplified in which a user uses a payment service, a music distribution service, a video distribution service, and an e-book service from a dedicated application installed on the user terminal 30. These services may be accessed from over 30 browsers. For example, after completing member registration for a payment service, the user registers for each of a music distribution service, a video distribution service, and an electronic book service. Here, we will take the flow of membership registration for a music distribution service as an example.

FIG. 2 is a diagram illustrating an example of the flow of member registration for a music distribution service. For example, when the music distribution service application installed on the user terminal 30 is started, the top screen G1 of the music distribution service is displayed on the display unit 35. As shown in the top screen G1, the music distribution service is a monthly subscription of 1,000 yen. For example, when the user selects button B10, member registration screen G2 is displayed on display unit 35. If the user has already registered as a member, he or she can log in to the music distribution service from link L11.

For example, the user inputs information necessary for membership registration, such as name and email address, into input forms F20 and F21. By selecting radio button B22, the user selects one of the plurality of payment methods available for the music distribution service. For example, when the user selects the radio button B22 for electronic money (XXX cash in FIG. 2) and proceeds with the membership registration procedure, the payment service application is started. When the user logs into the payment service, an auto-charge setting screen G3 is displayed on the display unit 35.

In this embodiment, the user can use the automatic charge function of electronic money so that the monthly payment for the music distribution service does not fail due to insufficient balance of electronic money. For example, when a user uses the auto-charge function for the first time, he or she completes a predetermined application procedure. Here, it is assumed that the user has completed the application procedure for the auto charge function. For example, the user can specify the charging method, charging threshold, and post-charging balance as auto charging settings from the input forms F30 to F32.

The charge method is the payment method used for auto charge. Various payment methods can be used for charging, such as credit cards, bank accounts, accounts at other financial institutions, crypto assets, points, other electronic money, debit cards, or sales proceeds from flea market services. There may be. In the example of FIG. 2, the user's credit card is designated as the charging method.

The charging threshold is the balance that is used as a criterion for determining whether or not to perform automatic charging. In this embodiment, it is assumed that auto-charging is performed when the charge becomes less than the charge threshold, but auto-charging may be performed when the charge becomes less than the charge threshold. The user can specify an arbitrary charge threshold. For example, the user specifies a value of 1,000 yen or more required for monthly payment of the music distribution service as the charging threshold.

The balance after charging is the balance after auto-charging. The balance after charging can also be said to be the balance always kept in electronic money. The user can specify any post-charge balance. For example, the user specifies a value of 1,000 yen or more required for monthly payment of the music distribution service as the balance after charging. The user specifies a value greater than or equal to the charging threshold as the post-charging balance.

For example, when the user selects the button B33, the auto charge setting and membership registration are completed, the music distribution service application returns to the foreground, and the membership registration completion screen G4 is displayed on the display unit 35. As shown in the member registration completion screen G4, on the 5th of every month, which is the payment date for the music distribution service, auto-charging is performed so that ``if the balance becomes less than 1,000 yen, the balance will be reduced to 1,100 yen.'' , the 1,000 yen required for the monthly payment for the music distribution service will be automatically deducted from your electronic money balance.

In this embodiment, it is assumed that membership registration for each of the video distribution service and the electronic 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 a video distribution service and an e-book service. The user specifies auto-charge settings for the video distribution service and auto-charge settings for the e-book service. On each payment date of the music distribution service, video distribution service, and electronic book service, auto-charging is performed based on the auto-charging settings associated with the payment date.

FIG. 3 is a diagram illustrating an example of a schedule regarding monthly payments for a certain user. In this embodiment, monthly payments are made according to the schedule shown in FIG. For example, the 5th of every month is the payment date for the music distribution service. On the 5th of every month, auto-charging is performed based on the auto-charging setting for the music distribution service, such as "If the balance becomes less than 1,000 yen, the balance will be set to 1,100 yen." On the 5th of every month, the 1,000 yen required to pay for the music distribution service will be deducted from your electronic money balance.

For example, assume that a video distribution service requires a payment of 2,500 yen on the 13th of every month. On the 13th of every month, auto-charging is performed based on the auto-charging settings for the video distribution service such as "When the balance becomes less than 2,500 yen, the balance will be increased to 3,000 yen." On the 13th of every month, the 2,500 yen needed to pay for the video distribution service will be deducted from your electronic money balance.

For example, assume that an e-book service requires a payment of 1,200 yen on the 25th of every month. On the 25th of every month, auto-charging is performed based on the auto-charging settings for the e-book service such as "If the balance becomes less than 1,200 yen, the balance will be reduced to 1,200 yen." On the 25th of every month, the 1,200 yen needed to pay for the e-book service will be deducted from your e-money balance.

As described above, in this embodiment, auto charge settings for music distribution service, auto charge settings for video distribution service, and auto charge settings for e-book service are specified. When each payment date for the music distribution service, video distribution service, and e-book service comes, auto-charging is performed based on the auto-charging settings for the payment date. As a result, even if the user is not aware of the balance of electronic money on the payment date, the balance will not be insufficient, increasing convenience for the user. Hereinafter, details of the auto charge system 1 will be explained.

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

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

[Data storage unit]
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.

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 regarding electronic money held by users. For example, the electronic money database DB1 includes the user ID of the payment service, the password of the payment service, the balance of electronic money, payment method information regarding payment methods that can be used for charging, the name of the regular payment service where regular payments occur, The user ID, payment date, payment amount, and auto charge setting of the regular payment service are stored.

The user ID is an example of identification information that can identify a user. In this embodiment, since one user owns one piece of electronic money, the identification information can also be said to be information that allows the electronic money to be identified. The identification information may be an email address, a telephone number, or other information such as 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 regular payment service, but a common user ID and password may be used.

Payment method information is information that can identify the payment method used for charging. For example, when a credit card is used for charging, the payment method information includes the card number, expiration date, and name holder. For example, when a bank account is used for charging, the payment method information includes a financial institution code, a branch code, and an account number. Similarly, for other payment methods, the payment method information may include information that allows identification of other payment methods. Payment method information of payment methods specified by the user is registered in the electronic money database DB1. The payment method indicated in the payment method information can be used not only for automatic charging but also for manual charging by the user.

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

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

The payment amount is the amount required for periodic payments. The payment amount can also be called the settlement amount. In this embodiment, a case will be explained 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 vary depending on the user. good. For example, if a plurality of rate plans are available for the regular payment service, the payment amount may be set according to the rate plan selected by the user.

Auto charge settings are settings related to auto charge. In this embodiment, a case will be explained in which the auto charge setting indicates the charge method, the charge threshold, and the balance after charge. However, the auto charge setting may also indicate only the charge threshold and the balance after charge without indicating the charge method. good. In this case, a common charging method is used for multiple auto-charging settings. It is assumed that the common charge method is stored in the electronic money database DB1 as a setting different from the auto charge setting.

For example, the auto charge setting may indicate only either the charge threshold or the post-charge balance. When the auto charge setting indicates only the charge threshold, the balance after charge 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.

The auto charge setting may be information indicating what kind 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 instead of the post-charge balance. In other words, instead of the automatic charge setting of "When the balance becomes less than 1,000 yen, the balance will be changed to 1,100 yen" as in this embodiment, "When the balance becomes less than 1,000 yen, the balance will be set to 1,100 yen." It may also be an auto-charge setting such as ``Charge the amount of time.''

For example, the auto charge setting may also indicate a period to which the auto charge setting is applied. In this embodiment, a case will be explained in which the auto charge setting is applied on the payment date of the fixed amount payment service, but if the auto charge setting is applied on other days as well, the period to which the auto charge setting is applied will be changed. May be indicated in auto-charge settings. For example, if you apply the auto charge setting shown in Figure 3, "When the balance becomes less than 1,000 yen, the balance will be set to 1,100 yen" from the 1st to the 5th of every month, this auto charge setting , or may indicate a period such as "1st to 5th of every month."

Note that the data storage unit 100 can store arbitrary data. The data stored in the data storage unit 100 is not limited to the electronic money database DB1. The information on the balance of electronic money and the information on periodic payments are not collected in one database as in this embodiment, but may be stored in separate databases. In addition, for example, a database for storing information regarding periodic payments may exist for each periodic payment service.

[Storage section]
The storage unit 101 stores auto charge settings according to periodic payments. Saving 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. The information may be stored in another computer or in an information storage medium external to the electronic money server 10.

In the present embodiment, a case will be described in which the storage unit 101 stores auto charge settings in association with each of a plurality of payment dates on which regular payments are made to different payees. There are multiple payment dates within a given period. In this embodiment, a case will be described in which this period is every month from January to December, but this period may be any period that corresponds to the payment cycle. As mentioned above, the period is not limited to one month.

A payee is a person who receives payment. The payee is the person to whom the user pays. In this embodiment, a case where the service provider corresponds to the payee will be exemplified. Therefore, the portions that describe service providers can be read as payment recipients. The payee may be any person and is not limited to the service provider. For example, the payee may be the country, a local government, a government agency, a non-profit organization, or an individual.

In this embodiment, the payee on a certain payment date and the payee on another payment date are different from each other. For this reason, multiple payment dates are defined as the first payment date on which periodic payments are made to the first payee, and the second payment date on which periodic payments are made to a second payee different from the first payee. A second payment date that is different from the first payment date. In the example in Figure 3, periodic payments to the music distribution service occur on the 5th of every month, periodic payments to the video distribution service occur on the 13th of each month, and periodic payments to the e-book service occur. There are three payment dates, such as the 25th of each month.

Storing two pieces of information in an associated manner means storing one piece of information in a searchable state. For example, the storage unit 101 associates and saves the payment date and autocharge setting by storing the pair of the payment date and autocharge setting in the electronic money database DB1. In this embodiment, when registering as a member of a regular payment service, auto charge settings are specified on the auto charge setting screen G3. associate and save the auto charge settings.

In the present embodiment, the storage unit 101 associates and stores each of a plurality of payment dates with an auto-charge setting indicating a balance after charging that is equal to or greater than the payment amount for regular payments on the payment date. 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 that is equal to or greater than the payment amount can be specified, or an error message may be displayed when a post-charge balance that is less than the payment amount is specified.

In the example of FIG. 3, the storage unit 101 associates and stores the payment date of the music distribution service and the auto charge setting indicating the post-charge balance specified by the user at the time of membership registration of the music distribution service. Similarly, the storage unit 101 stores the video distribution service and the e-book service in association with the payment date and the auto-charge setting indicating the post-charge balance designated by the user. The balance after charging may be automatically determined to be a value corresponding to the payment amount.

In this embodiment, since the charging method specified by the user is also included in the auto-charging settings, the storage unit 101 stores the auto-charging information indicating each of the plurality of payment dates and the charging method selected from the plurality of charging methods. Save settings in association with. For example, the storage unit 101 stores the auto charge setting so as to indicate the charge method specified in the input form F30 of the auto charge setting screen G3. Since a payment method whose payment method information is stored in the electronic money database DB1 can be specified as a charging method, information on this payment method is displayed in a selectable manner on the input form F30.

In this embodiment, the storage unit 101 stores the auto-charge settings at the time of member registration for a regular payment service, but the storage unit 101 can save the auto-charge settings at any timing. For example, after registering as a member of a regular payment service, the storage unit 101 may store the auto charge settings. When the user changes the auto charge settings after membership registration, the storage unit 101 may save the changed auto charge settings specified by the user. For example, auto-charge setting may not be performed when registering as a member of a regular payment service, but auto-charging setting may be performed after member registration.

[Auto charge execution section]
The auto-charge execution unit 102 executes auto-charge based on the auto-charge settings saved by the storage unit 101. Executing auto charge means automatically charging electronic money. Since the auto-charge settings are set so that the balance is greater than or equal to the payment amount for periodic payments, the auto-charge execution unit 102 sets the balance to be equal to or greater than the payment amount for periodic payments based on the auto-charge settings. Execute auto charge so that

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

For example, when a bank account is specified as the charging method, the auto-charging execution unit 102 executes auto-charging so that the balance of the bank account decreases and the balance of electronic money increases. For example, when crypto assets are specified as the charge method, the auto charge execution unit 102 executes auto charge so that the balance of crypto assets decreases and the balance of electronic money increases. If another charging method is specified, the auto-charging execution unit 102 may execute auto-charging according to the other charging method.

In this embodiment, a case will be described in which the auto-charge execution unit 102 executes auto-charge based on auto-charge settings associated with each of a plurality of payment dates. Since the auto-charge execution unit 102 may be associated, the auto-charge execution unit 102 may execute auto-charge based on the auto-charge setting associated with one payment date.

For example, the auto-charge execution unit 102 obtains the current date and time using a real-time clock, a GPS signal, or the like. The auto-charge execution unit 102 determines whether each of the plurality of payment dates stored in the electronic money database DB1 has arrived based on the current date and time. When it is determined that a certain payment date has arrived, the auto-charging execution unit 102 executes auto-charging based on the auto-charging setting associated with this payment date. Autocharging on this payment date does not reference autocharging settings associated with other payment dates.

In this embodiment, it is assumed that auto-charging is not performed on days other than the payment date, but as in the modified example described later, auto-charging is not performed on other days based on the default auto-charging settings. May be executed. For example, autocharging may be performed based on autocharging settings associated with a certain payment date until a certain payment date has passed. For example, auto-charging may be performed for a certain period of time including a certain payment date based on auto-charging settings associated with this payment date.

In this embodiment, since the 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 has become less than the charge threshold. The auto charge execution unit 102 does not execute auto charge when it is determined that the balance of electronic money has become less than the charge threshold, and performs auto charge when it is determined that the balance of electronic money has become less than the charge threshold. Execute. In particular, when a charging threshold is not used, the auto-charging execution unit 102 may determine whether auto-charging is necessary by determining whether the balance of electronic money is less than the payment amount.

In this embodiment, since the balance after charging is indicated in the auto charge setting, the auto charge execution unit 102 automatically performs the automatic charging so that the balance after charging is the balance indicated in the auto charge setting associated with each of the plurality of payment dates. Execute charge. For example, on a certain payment date, the auto-charge execution unit 102 determines the difference between the post-charge balance indicated in the auto-charge settings associated with the payment date and the current balance of electronic money as the charge amount. . The auto charge execution unit 102 executes auto charge so that the balance increases by the determined charge amount.

In the present embodiment, the auto-charge execution unit 102 executes auto-charge before the payment time on each of a plurality of payment dates arrives, based on the auto-charge settings associated with the payment date. The payment time is the time at which the payment is made within the respective payment date. In this embodiment, in order to simplify the explanation, an example will be given in which the payment time is fixed at 10:00 a.m. regardless of the payment date, but the payment time may be any time, It's not limited to 10 o'clock. For example, the payment time may be a time other than 10 a.m., or the payment time on one payment day may be different from the payment time on another payment day.

In this embodiment, since the payment time is 10:00 am on a certain payment day, there is a possibility that auto-charging will be executed at least once between 12:00 am and 10:00 am on this payment day. Auto-charging does not necessarily have to be performed, and may not be performed if there is a sufficient balance of electronic money. This describes a case in which autocharging based on the autocharging settings associated with this payment date does not occur after the payment time has arrived and the payment has been completed for a certain payment date, but even after the payment time has arrived and the payment has been completed. , auto-charge may be performed based on this auto-charge setting.

For example, when each of a plurality of payment dates comes, the auto-charging execution unit 102 determines whether auto-charging is necessary or not based on the auto-charging settings associated with the payment date at each predetermined time until the payment time. Determine. The predetermined time is a time for determining whether auto-charging 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 period may be other times such as 1 minute, 5 minutes, 30 minutes, 2 hours, or 4 hours.

In the example of FIG. 3, the auto-charge execution unit 102 determines whether the balance is less than 1,000 yen every hour from midnight to 10 a.m. on the 5th of every month. If the auto-charge execution unit 102 determines that the balance is 1,000 yen or more, it does not execute auto-charge. When 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.

For example, the auto-charge execution unit 102 determines whether the balance is less than 2,500 yen every hour from midnight to 10 a.m. on the 13th of every 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.

For example, the auto-charge execution unit 102 determines whether the balance is less than 1,200 yen every hour from midnight to 10 a.m. on the 25th of every 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.

Note that the necessity of auto-charging may not be determined at predetermined intervals, but may be determined each time the balance of electronic money changes. In this case, the auto-charge execution unit 102 may determine whether the balance of electronic money is less than the charging threshold when the balance of electronic money changes on the day of the payment date. For example, the auto-charging execution unit 102 may execute auto-charging immediately before the payment time on each payment day based on the auto-charging settings associated with the payment date, as in a modified example described below. It's okay.

In addition, in this embodiment, since the payment date and auto charge settings differ depending on the user, the storage unit 101 stores, for each user who makes regular payments, the payment date of the user's payment and the automatic charge setting for the payment. Associate and save the auto charge settings. For each individual user, when the payment date of the user's payment arrives, the auto charge execution unit 102 calculates the electronic money balance of the user based on the user's auto charge setting associated with the payment date. All you have to do is auto-charge so that the amount increases.

[Payment execution department]
The payment execution unit 103 executes periodic payments. Executing payment can also be referred to as executing settlement. Various known processes can be used to process the payment itself. When electronic money is used as in the present embodiment, the payment execution unit 103 may execute a process of subtracting the payment amount from the balance of the electronic money. If another payment method such as points or an account is used, the payment execution unit 103 may execute a process of subtracting the payment amount from the balance of the other payment method.

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. The payment execution unit 103 does not execute the payment if it is determined that the payment date has not arrived, and if it is determined that the payment date has arrived, the balance of the electronic money of the user who is the target of payment reaches the predetermined payment. Make the payment so that it decreases by the amount. The payment execution unit 103 may refer to the electronic money database DB1 and specify the users to whom payment is to be made and the payment amount of each user.

In this embodiment, since there are multiple payment dates in one month, the payment execution unit 103 executes the payment on the payment date based on electronic money when each of the multiple payment dates comes. do. For example, the payment execution unit 103 determines whether the payment time on each payment date has arrived. In this embodiment, since the payment time is 10 am, the payment execution unit 103 determines whether 10 am has arrived on the payment date. The payment execution unit 103 does not execute the payment if it is not determined that 10 a.m. on the payment date has arrived, and executes the payment if it is determined that 10 a.m. has arrived on the payment date.

In the example of FIG. 3, the payment execution unit 103 executes the payment by subtracting the balance of 1,000 yen from the payment amount when it is determined that 10 a.m. on the 5th of every month has arrived. The payment execution unit 103 executes the payment by subtracting the balance of 2,500 yen from the payment amount when it is determined that 10 am on the 13th of every month has arrived. The payment execution unit 103 executes the payment by subtracting the balance of 1,200 yen from the payment amount when it is determined that 10 am on the 25th of every month has arrived.

Note that 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 electronic money server 10 to execute the payment by transmitting a list of users to whom payment is to be made. When the payment execution unit 103 receives the list, it executes the payment so that the electronic money balance of the users included in the list is reduced by a predetermined payment amount.

The list may include user IDs for recurring payment services. Since the relationship between the user ID of the payment service and the user ID of the regular payment service is stored in the electronic money database DB1, the payment execution unit 103 allows the user indicated by the user ID of the regular payment service included in the list to make the payment. It is possible to specify which users of the service the service corresponds to. The list may include the user ID of the payment service instead of the user ID of the regular payment service. In this case, the service provider server 20 stores the relationship between the user ID of the payment service and the user ID of the regular payment service.

For example, when 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 this periodic payment service. This list may include the user ID of the payment service or the user ID of the regular payment service. By receiving the list, the service provider server 20 can identify which users have completed their payments.

[3-2. Functions realized by service provider server]
In this embodiment, a case will be described in which the service provider servers 20 of the music distribution service, video distribution service, and e-book service have similar functions, This will be explained as a function of the server 20. The data storage section 200 is realized by the storage section 22. The service providing unit 201 is realized by the control unit 21.

[Data storage]
The data storage unit 200 stores data necessary for providing periodic payment services. For example, the data storage unit 200 stores a service database DB2.

FIG. 6 is a diagram showing an example of the service database DB2. The service database DB2 is a database that stores information regarding users who have registered as members of the regular payment service. FIG. 6 shows an example of data storage for a music distribution service. For example, the service database DB2 includes the user ID of the regular payment service, the payment date, the payment amount, the payment method information regarding the payment method used for the regular payment, the payment status information regarding the payment status, and the user ID of the payment service. Stored. The service provider server 20 generates various information such as a user ID of the regular payment service when registering as a member of the regular payment service, and stores it in the service database DB2. The payment status information is updated by the service providing unit 201.

[Service provision department]
The service providing unit 201 provides a regular payment service. Various known methods can be used to provide the periodic payment service. For example, the service providing unit 201 provides a regular payment service to a user who has completed payment. The service providing unit 201 identifies the user who has completed the payment based also on the list received from the electronic money server 10 when the payment execution unit 103 executes the payment. The service providing unit 201 updates the payment status information in the service database DB2 to indicate that the payments of the users included in the list have been completed.

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

[Data storage]
The data storage unit 300 stores data necessary for using each of the payment service and the regular payment service. For example, the data storage unit 300 stores applications for payment services and periodic payment services.

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

[Operation reception department]
The operation accepting unit 302 accepts operations on each screen described in FIG. 2.

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

As shown in FIG. 7, the user terminal 30 executes processing for displaying the top screen G1 and member registration screen G2 with the service provider server 20 based on the application of the regular payment service (S1). . The user specifies electronic money as the payment method using radio button B22 and proceeds with the membership registration procedure. The user terminal 30 executes processing for displaying the auto-charge setting screen G3 with the electronic money server 10 based on the payment service application (S2).

When the user selects button B33, user terminal 30 transmits the auto-charge settings specified for input forms F30 to F32 to electronic money server 10 (S3). When the electronic money server 10 receives the auto charge setting from the user terminal 30 (S4), it stores the auto charge setting 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 stores it in association with the auto charge setting. The user terminal 30 executes processing for displaying the member registration completion screen G4 with the service provider server 20 (S6). Through the above processing of S1 to S6, membership registration for the regular payment service is completed. Once membership registration is completed, the user will be able to use the regular payment service.

Note that auto-charging may be performed for the first payment when registering as a member of a regular payment service. In this case, the electronic money server 10 determines whether auto-charging is necessary based on the auto-charging setting specified on the auto-charging setting screen G3 at the time of member registration. The electronic money server 10 executes the first payment if auto-charging is not necessary. If auto-charging is necessary, the electronic money server 10 executes auto-charging and then executes the first payment. When the first payment is completed, a membership registration completion screen G4 is displayed on the display section 35 through the process of S6.

The service provider server 20 creates a list of users eligible for payment based on the service database DB2 (S7). The process of S7 may be executed every day, or may be executed 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 to whom payment is to be made are updated (S10). Since the payment method may be changed on the periodic payment service side, it is assumed that the latest information is transmitted to the electronic money server 10 by executing the processes of S7 to S10. For example, information about users who have changed their payment method for regular payment services from other payment methods to electronic money, or from electronic money to another payment method, is shared with the electronic money server 10.

Based on the electronic money database DB1, the electronic money server 10 determines whether the payment date for any periodic payment service of any user has arrived (S11). If it is not determined that the payment date has arrived (S11:N), this process ends. When it is determined that the payment date has arrived (S11: Y), the electronic money server 10 selects n (n is a natural number) users who have set up automatic charging among the users eligible for payment based on the electronic money database DB1. The user is identified (S12).

The electronic money server 10 performs auto-charging every hour based on the auto-charging settings of the n users identified in S12 (S13). In S13, the electronic money server 10 determines whether auto-charging is necessary for each user based on the charging threshold indicated by the auto-charging setting of the user and the balance of electronic money held by the user. The electronic money server 10 executes auto-charging based on the auto-charging settings of the user who has determined that auto-charging is necessary.

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

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

The auto-charge system 1 of this embodiment stores each of a plurality of payment dates and auto-charge settings in association with each other. The auto-charge system 1 performs auto-charging based on auto-charging settings associated with each of a plurality of payment dates. As a result, even if periodic payments to different payees occur on multiple payment dates, it is possible to prevent insufficient balances around each payment date without being aware of the balance, which is convenient for users. Sexuality increases. Additionally, by saving auto-charge settings for each payment date instead of using common auto-charge settings for multiple payment dates, flexible auto-charging according to the payment date becomes possible.

Further, the auto-charge system 1 executes auto-charging so that the balance after charging becomes the one indicated in the auto-charging settings associated with each of the plurality of payment dates. As a result, if the balance after charging is equal to or greater than the payment amount on each payment date, it is possible to more reliably prevent the balance from becoming insufficient, thereby increasing convenience for the user. Furthermore, by setting the balance after charging, it is also possible to prevent more charging than the user intended, thereby increasing convenience for the user in this respect as well. For example, suppose that a malicious third party illegally logs into a regular payment service and uses the regular payment service fraudulently. As with conventional technology, when an auto charge is executed to make up for the shortfall, if a large amount of payment is incurred due to fraudulent use, an auto charge is executed to make up for the payment amount and a large payment is made. However, by setting a post-charge balance, even if such unauthorized use occurs, payments will generally only be made within the post-charge balance, thus preventing large payments from being made. can. Although there is a possibility that the recurring payment service will be suspended due to a payment failure, the user will be able to notice the fraudulent use. In addition to unauthorized use, it is also possible to prevent large payments that the user is unaware of.

Furthermore, before the payment time on each of the plurality of payment dates arrives, the autocharging system 1 executes autocharging based on the autocharging settings associated with the payment date. As a result, auto-charging can be performed before the payment time arrives, and insufficient balance can be more reliably prevented, increasing convenience for the user. When the payment time arrives and the payment is executed, auto-charging may be executed as part of the flow, but in this case, a large number of auto-charging will be concentrated and the processing load on the electronic money server 10 will increase. may increase. By completing auto-charging in advance, the execution timing of auto-charging can be distributed. As a result, the processing load on the electronic money server 10 can be reduced.

In addition, when each of a plurality of payment dates comes, the auto-charging system 1 determines whether or not auto-charging is necessary based on the auto-charging settings associated with the payment date at predetermined time intervals until the payment time. judge. If the shortfall is automatically charged at the time of payment execution, there is a possibility that the automatic charges will be concentrated and the processing load on the electronic money server 10 will increase. By determining in advance whether or not auto-charging is necessary at predetermined intervals and executing auto-charging, the execution timing of auto-charging can be distributed. As a result, the processing load on the electronic money server 10 can be reduced.

Further, the auto charge system 1 stores each of the plurality of payment dates in association with an auto charge setting indicating a charge method selected from a plurality of charge methods. As a result, auto-charging can be performed using a flexible charging method on each payment date, increasing convenience for the user.

[5. Modified example]
Note that the present disclosure is not limited to the embodiments described above. Changes can be made as appropriate without departing from the spirit of the present disclosure.

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

[5-1. Modification example 1]
For example, in the embodiment, a case has been described in which the payment dates for the music distribution service, video distribution service, and electronic book service are different from each other, but multiple regular payments may occur on a certain payment date. In modification 1, in the example of FIG. 3, the payment date for the video distribution service is not the 13th of every month, but the same as the music distribution service, the 5th of every month.

In the case where multiple regular payments occur on one payment date, the storage unit 101 of Modification 1 stores the total amount of payments on that one payment date and on each of the multiple regular payments. The corresponding auto charge settings are associated and saved. That is, the storage unit 101 may integrate and save multiple auto-charge settings on the same payment date as one auto-charge setting.

For example, the storage unit 101 calculates the total value of the charge threshold and post-charge balance of the music distribution service and the charge threshold and post-charge balance of the video distribution service, and sets the auto charge setting to indicate the calculated total value. save. The storage unit 101 stores the auto charge setting for the music distribution service, "When the balance becomes less than 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 becomes 2,500 yen." If the balance falls below 3,500 yen, the balance will be changed to 3,000 yen," and the auto charge setting that adds up ``If the balance falls below 3,500 yen, the balance will be set to 4,100 yen.'' is saved.

Similarly, when three or more payments occur on a certain payment day, the storage unit 101 calculates the charge threshold and the total value of the post-charge balance, and sets the auto charge setting indicating the calculated total value to the corresponding one. All you have to do is save it in association with the payment date. In Modification 1, although the process for saving auto charge settings is different from the embodiment, the auto charge itself may be executed in the same manner as in the embodiment.

In the auto-charging system 1 of Modification 1, when multiple periodic payments occur on one payment day, the total amount of payment on the one payment date and each of the plurality of periodic payments. Associate and save the auto charge settings according to the . If multiple regular payments occur within one payment date, the administrative burden on the user will increase by the number of payments, but by setting auto-charge according to the total amount, it will be possible to reduce the burden on one payment date. Since the necessary amount can be maintained reliably, the occurrence of insufficient balance due to individual payments is reliably prevented, and user convenience is enhanced. Auto charge settings are integrated within one payment date, eliminating the need to manage multiple auto charge settings, reducing the burden of managing auto charge settings.

[5-2. Modification 2]
For example, even if multiple regular payments occur on one payment day, if the payment times of the individual payments are different from each other, separate auto-charge settings may be saved for each payment time. In variation 2, in the example described in variation 1, the payment time for the music distribution service is 10:00 a.m. on the 5th of every month, and the payment time for the video providing service is 3:00 p.m. on the 5th of every month. . In this case, auto charge settings for music distribution services will be applied until 10 a.m. on the 5th of every month, and auto charge settings for video distribution services will be applied from 10 a.m. on the 5th of every month until 3 p.m. Settings may be applied.

The storage unit 101 of Modification 2 saves payments when a plurality of periodic payments occur on one payment day and the payment times for each of the plurality of periodic payments are different from each other within one payment date. Save separate auto charge settings for each time. In the second modification, it is assumed that not only the payment date but also the payment time information is stored in the electronic money database DB1 and the electronic money database DB1. For example, the payment time may be notified from the service provider server 20, or may be manually registered by the administrator of the payment service.

For example, when multiple regular payments occur on a certain payment day, the storage unit 101 compares their payment times. If the mutual payment times are the same, the storage unit 101 integrates a plurality of auto charge settings into one as in Modification 1. If the payment times are different, the storage unit 101 stores each payment time as a separate auto charge setting within one payment day. The auto-charging execution unit 102 executes auto-charging based on the auto-charging settings associated with the payment time until a predetermined payment time among a plurality of regular payments, and when the payment time has passed. performs an autocharge based on the autocharge settings associated with the next payment time of multiple recurring payments. The auto-charge execution unit 102 executes auto-charge until a certain payment time based on the auto-charge setting associated with this payment time. When this payment time has passed, the auto-charge execution unit 102 executes auto-charge based on the auto-charge setting associated with the next payment time.

In the auto-charging system 1 of the second modification, when a plurality of periodic payments occur on one payment day and the payment times of each of the plurality of periodic payments are different from each other within one payment day, Save separate autocharge settings for each payment time. The auto-charging system 1 executes auto-charging based on the auto-charging settings associated with the payment time until a predetermined payment time among multiple regular payments, and when the payment time has passed, , perform an autocharge based on an autocharge setting associated with the next payment time of the plurality of recurring payments. This enables more flexible auto-charging when payment times differ within a single payment date. For example, auto-charging can prevent your balance from being charged to an unnecessarily large amount.

[5-3. Modification 3]
For example, in the embodiment, auto-charging is not performed on other days when no recurring payments occur, but auto-charging is performed on other days based on the default auto-charging settings. It's okay. It is assumed that the default auto-charge settings are stored in the electronic money database DB1. The default auto charge setting may be specified by the user, or may be automatically determined by the payment service depending on the user's past charge performance. For example, the default auto-charge setting may indicate the charging method, charging threshold, and post-charging balance, as well as the auto-charging setting associated with the payment date.

The auto-charge execution unit 102 of Modification 3 performs auto-charging on other days different from the plurality of payment dates based on other auto-charging settings different from the auto-charging settings associated with each of the plurality of payment dates. Execute charge. Other days are days when no recurring payments occur. In the example of FIG. 3, the other days are days other than the 5th, 13th, and 25th of every month. In Modification 3, it is assumed that the other auto-charge settings are the default auto-charge settings, but a plurality of other auto-charge settings may exist depending on the time of the day. For example, default auto charge settings for the first half of the month and default auto charge settings for the second half of the month may be determined separately.

The auto-charging system 1 of the third modification performs auto-charging on other days different from the plurality of payment dates based on other auto-charging settings different from the auto-charging settings associated with each of the plurality of payment dates. Execute. This allows for more flexible auto-charging on days when regular payments do not occur, increasing convenience for the user.

[5-4. Modification example 4]
For example, if a user registers as a member of many regular payment services, managing auto-charge settings may become complicated. Therefore, the auto charge settings associated with each payment date may be confirmed in a calendar format. The auto-charge system 1 of Modification 4 includes a first display control section 104. The first display control unit 104 displays a calendar screen showing auto charge settings associated with each of the plurality of payment dates. Various layouts are available for the calendar layout itself.

FIG. 9 is a diagram illustrating an example of a calendar screen displayed on the user terminal 30 of Modification 4. In the fourth modification, a case will be described in which the first display control unit 104 uses a payment service application to display the calendar screen G5. However, the first display control unit 104 uses a browser to display the calendar screen G5. You may let them. For example, the first display control unit 104 acquires the auto charge setting 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.

For example, the first display control unit 104 generates display data for the calendar screen G5 including the user's monthly auto-charge settings and the user's monthly payment schedule. The calendar screen G5 shows the relationship among the user's payment date, auto-charge settings, and payment details. The display data may be data in any format defined by the application. If a browser is used, the displayed data may be in HTML format. The first display control unit 104 causes the calendar screen G5 to be displayed by transmitting display data for the calendar screen G5 to the user terminal 30. It may be possible to change the auto charge setting from the calendar screen G5.

The auto-charge system 1 of Modification 4 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 monthly auto-charge settings using intuitive images such as the calendar screen G5.

[5-5. Modification 5]
For example, in the embodiment, a case has been described in which the necessity of auto-charging is determined every hour on a payment date. Auto-charging may be performed based on auto-charging settings associated with the payment date. In modification 5, a case will be described in which the necessity of auto-charging is determined only immediately before the payment time on the payment date. However, by combining the embodiment and modification 5, the necessity of auto-charging is determined every hour on the payment date. is determined, and the necessity of auto-charging may also be determined immediately before the payment time.

Immediately before the payment time is a time within a predetermined time of the payment time. In modification 5, similarly to the embodiment, it is assumed that the payment time is 10 am. Furthermore, it is assumed that the time immediately before the payment time is 9:55 am. The time interval between the payment time and the time immediately before the payment time may be of any length and is not limited to 5 minutes. For example, these time intervals may be from seconds to tens of seconds, from one minute to several minutes, or longer than five minutes. However, if these time intervals are too long, there is a possibility that the balance after auto-charging will be used and the balance will become insufficient, so it should be kept short to some extent.

The auto-charge execution unit 102 determines whether the timing immediately before the payment time (9:55 a.m. on the payment date in modification example 5) has arrived on each of the plurality of payment dates. The auto-charge execution unit 102 does not perform auto-charging when it is not determined that the timing immediately before the payment time has arrived, and executes the auto-charging when it is determined that the timing immediately before the payment time has arrived. The only difference from the embodiment is the timing at which auto-charge is executed, and the method of executing auto-charge itself is the same as described in the embodiment.

The auto-charging system 1 of Modification 5 executes auto-charging immediately before the payment time on each of a plurality of payment dates, based on the auto-charging settings associated with the payment date. As a result, auto-charging is executed immediately before the payment time, so that insufficient balance at the payment time can be more reliably prevented. For example, after auto-charging is executed, it becomes easier to prevent a user from using electronic money for shopping in an electronic commerce service and running out of funds at the payment time.

[5-6. Modification 6]
For example, with periodic payments, the payment amount is not fixed and may change from month to month. In modification 6, an electric power service and a communication service will be described as examples of regular payment services in which the payment amount is not fixed. Electricity services require monthly payments for electricity, which fluctuate depending on the amount of electricity used. With communication services, monthly payments are required for communication charges that vary depending on the usage of telephone calls, packets, etc. In such a regular payment service, the payment amount varies depending on the amount of usage by the user, so the monthly payment amount may be predicted in advance and an auto charge setting according to the predicted value may be saved.

The auto-charge system 1 of modification 6 includes a prediction unit 105 and a determination unit 106. It is assumed that the electronic money database DB1 of modification 6 stores past payment records by individual users. Payment history is the result of payments made in the past. For example, assume that past payment dates and payment amounts are stored in the electronic money database DB1 for each periodic payment service as payment records. When a certain user executes a payment for a certain periodic payment service, the payment execution unit 103 associates the user ID of this user, the name of this periodic payment service, the payment date, and the payment amount and stores them in the electronic money database DB1.

The prediction unit 105 predicts the next payment amount in the periodic payment based on the payment history of the periodic payment for which the payment amount is not fixed among the periodic payments on each of the plurality of payment dates. . For example, the prediction unit 105 predicts a user's next payment amount by calculating the average value of past payment amounts based on the user's payment history. The average value may be a simple average, or may be a weighted average such that the closer to the current value the higher the weighting coefficient. The payment history used in predicting the next payment amount may be for the entire past period or may be for the most recent predetermined period (for example, about half a year). Furthermore, the prediction unit 105 may predict the payment amount for the same month last year as the next payment amount instead of the average value.

The determining unit 106 determines, based on the next payment amount predicted by the prediction unit 105, the contents of the auto charge setting to be associated with the payment date of a regular payment whose payment amount is not fixed. For example, the determining unit 106 determines the contents of the auto-charging setting so that the balance after charging is equal to or greater than the next payment amount predicted by the predicting unit 105. This balance after charging may be the same as the next payment amount, or may be an amount specified by the user or an amount with a margin of a predetermined amount. The storage unit 101 of the sixth modification stores the auto charge setting determined by the determination unit 106. The method of performing auto-charging itself may be the same as in the embodiment and Modifications 1 to 5.

The auto-charging system 1 of Modification 6 predicts the next payment amount in the periodic payment based on the payment history of the periodic payment in which the payment amount is not fixed. The auto-charge system 1 determines the contents of the auto-charge setting associated with the payment date of a regular payment whose payment amount is not fixed, based on the predicted next payment amount. As a result, even if the payment amount is not fixed, it is possible to set the automatic charge so that it is unlikely that the balance will become insufficient, thereby increasing convenience for the user.

[5-7. Modification 7]
For example, periodic payments may be made using electronic money and other payment methods. Other payment methods may be any payment method other than electronic money that is subject to automatic charging. For example, other payment methods may be credit cards, bank accounts, other financial institution accounts, crypto assets, points, other electronic money, debit cards, or proceeds from flea market services. For example, if a user wishes to use electronic money and other payment means together when registering as a member of a regular payment service, electronic money and other payment means are used together. The user may specify one to be used in conjunction with electronic money from among a plurality of other payment methods. The payment amount stored in the electronic money database DB1 is the portion of the payment amount for the regular payment service that is paid with electronic money.

The storage unit 101 of Modified Example 7 stores data according to the payment date of a periodic payment that allows electronic money and other payment methods together, and a part of the payment amount of the periodic payment, among a plurality of payment dates. Auto charge settings can be associated and saved. A portion of the payment amount is the portion of the payment amount that is paid using electronic money. The remainder of the payment amount will be paid through other payment methods. In Modification 7, a credit card will be explained as an example of another payment method. There may be two or more other payment methods. It is assumed that the user can arbitrarily specify how much of the payment amount is to be paid in electronic money.

For example, if you pay 700 yen out of a payment amount of 1,000 yen using electronic money and pay the remaining 300 yen using a credit card, part of the payment amount is 700 yen. For example, the storage unit 101 stores an auto-charge setting indicating a balance after charging a portion or more of the payment amount. The only difference from the embodiment is the content of the auto charge setting, and the format of the auto charge setting and the method of executing auto charge are the same as in the embodiment. The payment execution unit 103 may execute a credit card payment process so that the remaining part of the payment amount is paid by credit card, or the payment by other payment means may be processed by the service provider server 20 side. May be executed. Payments on all payment dates do not need to be executed in conjunction with other payment means, and payments on some payment dates may be executed in conjunction with other payment means.

The auto-charging system 1 of Modification Example 7 is configured to set a payment date of a periodic payment that allows electronic money and other payment methods together, and a part of the payment amount of the periodic payment, among multiple payment dates. It is possible to associate and save the corresponding auto charge settings. This allows payment to be made using multiple payment methods, increasing convenience for the user. Even if a payment is made using multiple payment methods, it is possible to prevent the amount of electronic money from running out.

[5-8. Modification 8]
For example, in Modification 6, we explained the case of predicting the next payment amount of a periodic payment where the payment amount is not fixed. There may be a certain amount of time in between. During this period, if the electronic money server 10 is able to receive the next confirmed payment amount from the service provider server 20, the next payment received from the service provider server 20 can be received without predicting the next payment amount. Auto-recharge settings may be saved based on the amount.

The storage unit 101 of Modified Example 8 stores the fixed payment on the payment date of a periodic payment for which the payment amount is not fixed among the plurality of payment dates, after the payment amount of the periodic payment is determined. Associate and save the auto charge settings according to the amount. When the payment amount for the periodic payment service provided by the service provider server 20 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 according to the usage status of the regular payment service by the user.

For example, the service provider server 20 transmits to the electronic money server 10 a list of users to whom payment is to be made and the determined next payment amount. 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 setting so that the balance after charging is equal to or greater than the received payment amount. The method of performing auto-charging itself is the same as in the embodiment.

The auto-charging system 1 of Modified Example 8 is configured such that on a payment date of a periodic payment on which the payment amount is not fixed among multiple payment dates, after the payment amount of the periodic payment is determined, Associate and save the auto charge settings according to the payment amount. As a result, it is possible to more reliably prevent insufficient balance at the next payment, thereby increasing convenience for the user.

[5-9. Modification 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 is specified on the screen displayed on the periodic payment service side. May be specified. 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 contents of the auto-charge setting specified by the user.

In modification 9, after the membership registration screen G2 is displayed, an auto-charge setting screen G3 is displayed on the display unit 35 as a screen for the regular payment service. For example, the auto-charge setting screen G3 is displayed on a regular payment service application. When a browser is used, the auto-charge setting screen G3 is displayed as a page of the periodic payment service domain. When it is necessary to display the electronic money balance on the auto charge setting screen G3, the user logs into the payment service and the user's electronic money balance is sent to the service provider server 20. good.

The auto-charge system 1 of modification 9 includes a receiving section 107. The receiving unit 107 further includes a receiving unit 107 that receives a predetermined notification when an operation for consenting to auto-charge setting is performed in the regular payment service of the payee. This operation may be any predetermined operation that indicates consent to the auto-charge setting. For example, the operation of selecting button B33 with the charging method, charging threshold, and post-charging balance specified corresponds to the operation for agreeing to the automatic charging setting.

The predetermined notification is a notification indicating that the user has agreed to the automatic charge setting on the periodic payment service side. The predetermined notification is performed by transmitting data in a predetermined format. The predetermined notification shall include the auto-charge settings specified by the user. The storage unit 101 stores the auto charge setting when a predetermined notification is received. The notification shall include the user ID of the payment service. Using this user ID, the storage unit 101 can identify which user's auto charge setting is used. The storage unit 101 stores the auto charge settings included in the notification. The contents of the auto charge setting itself may be the same as those in the embodiment.

The auto-charge system 1 of modification 9 saves the auto-charge setting when receiving a predetermined notification that is sent when an operation for consenting to the auto-charge setting is performed in a regular payment service. As a result, the periodic payment service can seamlessly complete the automatic charge setting, increasing convenience for the user. For example, you will be able to complete the auto-charge setup without having to start up the payment service application midway or being redirected to the payment service page.

[5-10. Modification 10]
For example, electronic money can also be used for payments other than regular payments. In this case, it becomes difficult for the user to manage how much electronic money is used for regular payments. Therefore, a screen may be displayed that distinguishes the payment amount for regular payments and the payment amount for other payments. The auto-charge system 1 includes a second display control section 108. The second display control unit 108 displays a payment amount screen that distinguishes 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. Distinguishing means displaying each payment amount separately.

FIG. 10 is a diagram showing an example of the payment amount screen. For example, on the payment amount screen G6, the total amount of payments for regular payments and the total amount of payments for other payments are displayed separately. In the example of FIG. 10, a case will be explained where both the total amount and the individual breakdown are displayed on the payment amount screen G6, but even if only either the total amount or the individual breakdown is displayed on the payment amount screen G6. good. The total amount is assumed to be aggregated monthly, but the user may be able to specify an arbitrary aggregation period. For example, the weekly or semi-annual total amount may be displayed on the payment amount screen G6.

In modification 10, it is assumed that the electronic money usage history is stored in the electronic money database DB1. 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 every time electronic money is used. The second display control unit 108 totals the total amount of payments for regular payments and the total amount of payments for other payments, based on the usage history of electronic money. The second display control unit 108 generates display data for the payment amount screen G6 based on these total results and transmits it to the user terminal 30.

The auto-charge system 1 of Modification 10 displays a payment amount screen G6 that distinguishes the payment amount of regular payments on each of a plurality of payment dates and the payment amount of other payments different from regular payments. let This makes it possible to reduce the administrative burden on the user for managing the payment amount in periodic payments.

[5-11. Modification 11]
For example, in the embodiment, a case has been described in which auto-charging is performed based on one charging method, but auto-charging may be performed using a plurality of charging methods in combination. The charging method itself that can be used in combination with auto-charging may be a combination of the various methods described in the embodiments. The storage unit 101 of Modification 11 can store each of a plurality of payment dates and an auto charge setting indicating a combination of a plurality of charge methods in association with each other.

In the auto charge setting of modification 11, a plurality of charging methods are shown. The charging amount for each charging method may be specified separately, or a plurality of charging methods may be prioritized. When the auto charge setting indicates a combination of a plurality of charge methods, the auto charge execution unit 102 of Modification 11 executes auto charge based on the plurality of charge methods. The user can arbitrarily specify whether or not to use multiple charging methods together.

In the example of FIG. 3, it is assumed that the automatic charge setting on the 5th of each month indicates that a credit card and bank account can be used together. For example, if the auto charge setting indicates that the credit card charge amount is 70% and the bank account charge amount is 30%, the auto charge execution unit 102 will charge 70% of the required charge amount. % to your credit card, and perform auto-charging so that 30% of the required amount is charged to your bank account.

For example, if a plurality of charging methods are prioritized, the auto-charging execution unit 102 attempts auto-charging in descending order of priority. If autocharging fails with a charging method with a certain priority, the autocharging execution unit 102 attempts autocharging with a charging method with the next priority. Thereafter, in the same manner, the auto-charging execution unit 102 attempts auto-charging in descending order of priority until auto-charging is successful.

For example, in the example shown in FIG. 3, suppose that the credit card is designated as the first auto-charge setting on the 5th of every month, and the bank account is designated as the second. If the auto-charge execution unit 102 attempts auto-charge using a credit card and is successful, it does not execute auto-charge using a bank account. If auto-charging fails due to lack of credit card slots, etc., auto-charging execution unit 102 executes auto-charging using the next priority bank account.

The auto-charge system 1 of Modification 11 can store each of a plurality of payment dates in association with an auto-charge setting indicating a combination of a plurality of charge methods. When the auto charge setting indicates a combination of a plurality of charge methods, the auto charge system 1 executes auto charge based on the plurality of charge methods. This allows for flexible auto-charging that combines multiple charging methods.

[5-12. Variations regarding other configurations]
For example, in addition to a configuration that solves the problem of "improving user convenience when periodic payments to different payees occur on each of multiple payment dates," the present disclosure also solves other problems. Contains configuration to resolve. Therefore, among the configurations described in Modifications 1 to 11, the present disclosure also includes configurations that are not based on the configuration described in the embodiment. Hereinafter, configurations that are not premised on the configuration described in the embodiment will be described as modifications regarding Modifications 1 to 11.

[Modification regarding modification 1]
For example, in Modification 1, there may not be multiple payment dates on which regular payments are made to different payees. A plurality of regular payments to different payees may occur within a single payment date. In the example described in Modification 1, there is no need to pay for the electronic book service on the 25th of every month. In this case, the monthly payment is only for the music distribution service and video distribution service on the 5th of each month, so there is only one payment date in one month.

For example, as an auto-charge setting on the 5th of every month, the storage unit 101 stores a message that says "If the balance becomes less than 3,500 yen, the balance becomes less than 3,500 yen." 4,100 yen". Save the auto charge settings. Auto charge settings may not be saved on days other than the 5th of each month. In this case, automatic charging will be executed only once every month.

Furthermore, multiple regular payments to the same payee may occur within one payment date. For example, the service provider of the music distribution service and the service provider of the video distribution service may be the same. In this case, payments to multiple regular payment services provided by the same payee occur on the 5th of every month. The storage unit 101 stores auto charge settings such as "When the balance becomes less than 3,500 yen, the balance will be changed to 4,100 yen" according to the total amount of multiple periodic payments to the same payee. Good too.

The auto-charging system 1 of the modified example related to the modified example 1 saves auto-charging settings according to the total amount of multiple regular payments that occur within one payment date, thereby allowing multiple regular payments to occur on one payment date. Even if periodic payments occur, insufficient balance is reliably prevented and user convenience is improved. Auto charge settings are integrated within one payment date, eliminating the need to manage multiple auto charge settings, reducing the burden of managing auto charge settings.

[Modification regarding modification 2]
For example, in the configuration of Modified Example 2, similarly to the modified example related to Modified Example 1, there does not have to be a plurality of payment dates on which periodic payments are made to different payees. For example, monthly payments may be made only for music distribution service and video distribution service on the 5th of each month. In this case as well, if the payment time for the music distribution service and the payment time for the video distribution service are different, the storage unit 101 performs automatic charging settings up to the respective payment times as in Modification 2. You can also save them separately.

For example, in Modification 2, as in the Modification 1, multiple regular payments to the same payee may occur within 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 stores each of the music distribution service and video distribution service provided by the same service provider as in Modification 2. You may save separate autocharge settings for different payment times.

The auto-charging system 1 of the modified example related to the modified example 2 is configured to adjust the payment time when a plurality of periodic payments occur on one payment day and the payment times of each of the plurality of periodic payments are different from each other. Flexible auto-charging is possible by saving separate auto-charging settings for each device.

[Modification regarding modification 3]
For example, in the configuration of Modified Example 3, similarly to the modified examples related to Modified Examples 1 and 2, there does not have to be a plurality of payment dates on which periodic payments are made to different payees. For example, there may only be a music distribution service on the 5th of each month as a monthly payment. In this case, the auto-charge execution unit 102 may execute auto-charge on days other than the 5th of each month based on the default auto-charge settings.

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

Modified auto-charge system 1 related to modified example 3 is more flexible because auto-charge can be executed based on the default auto-charge settings when there is a day in which no regular payment occurs within a certain period. Automatic charging becomes possible, increasing user convenience.

[Modification regarding modification 4]
For example, in the configuration of Modified Example 4, similarly to the modified examples related to Modified Examples 1 to 3, there does not have to be a plurality of payment dates on which periodic payments are made to different payees. For example, even if there is only one payment date per month, a calendar display like Modification 4 may be possible. In addition, for example, when regular payments to the same payee occur on a plurality of payment dates, a calendar display as in Modification 4 may be possible.

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

[Modification regarding modification 5]
For example, in the configuration of Modified Example 5, similarly to the modified examples related to Modified Examples 1 to 4, there does not have to be a plurality of payment dates on which periodic payments are made to different payees. For example, even if there is only one monthly payment date, the autocharging execution unit 102 sets the autocharging associated with the monthly payment date immediately before the payment time, as in Modification 5. Auto-charging may be performed based on.

For example, even when regular payments to the same payee occur on multiple payment dates, the auto-charge execution unit 102, as in Modification 5, immediately before the payment time on each payment date, Auto-charging may be performed based on auto-charging settings associated with the payment date. If multiple regular payments occur in one day, and the payment times of the individual payments are different, the auto-charge execution unit 102 performs an automatic charge execution unit 102 that associates the payment time with the payment time immediately before each payment time. Auto-charging may be performed based on the auto-charging settings set.

The auto-charging system 1 of the modified example related to Modified Example 5 executes auto-charging immediately before the payment time on at least one payment date based on the auto-charging setting associated with the payment date. Since auto-charging is executed immediately before the payment time, insufficient balance at the payment time can be more reliably prevented.

[Modification regarding modification 6]
For example, in the configuration of Modified Example 6, similarly to the modified examples related to Modified Examples 1 to 5, there does not have to be a plurality of payment dates on which regular payments are made to different payees. For example, the prediction unit 105 may predict the next payment amount based on past payment records even if there is only one payment date each month. The determining unit 106 may determine the contents of the auto charge setting based on the next payment amount predicted by the predicting unit 105 even if there is only one payment date per month.

For example, even if regular 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. The determining unit 106 determines the contents of the auto charge setting based on the next payment amount predicted by the predicting unit 105 even when regular payments to the same payee occur on multiple payment dates. It's okay.

The auto-charge system 1 of the modified example related to the modified example 6 predicts the next payment amount and determines the contents of the auto-charge setting when the payment amount of the regular payment on at least one payment date is not fixed. . As a result, even if the payment amount is not fixed, it is possible to set the automatic charge so that it is unlikely that the balance will become insufficient, thereby increasing convenience for the user.

[Modification regarding modification 7]
For example, in the configuration of Modified Example 7, as in the modified examples related to Modified Examples 1 to 6, there does not have to be a plurality of payment dates on which regular payments are made to different payees. For example, even if there is only one payment date each month, it may be possible to use electronic money and other payment methods in combination for payments that occur only once each month. The storage unit 101 may associate and store a payment date, which occurs only once a month, and an auto-charge setting corresponding to a portion of the payment amount in a payment using both electronic money and other payment methods.

For example, even if periodic payments to the same payee occur on multiple payment dates, if simultaneous payments are possible on at least one payment date, the storage unit 101 stores the payment date and the electronic An auto-charge setting corresponding to a portion of the payment amount in a payment using money and other payment methods may be stored in association with each other.

The auto-charge system 1 of the modified example related to the modified example 7 saves the auto-charge setting according to the electronic money payment amount when payment using electronic money and other payment methods is possible on at least one payment date. By doing so, even if a payment is made using multiple payment methods, it is possible to prevent the payment amount of electronic money from running out.

[Modification regarding modification 8]
For example, in the configuration of Modified Example 8, similarly to the modified examples related to Modified Examples 1 to 7, there does not have to be a plurality of payment dates on which periodic payments are made to different payees. For example, even if there is only one monthly payment date, the storage unit 101 may store the auto charge settings according to the determined payment amount after the payment amount of the regular payment is determined. .

For example, even if periodic payments to the same payee occur on multiple payment dates, the storage unit 101 stores the payment amount of the payment on at least one payment date as long as the payment amount is not fixed. After the amount is determined, the payment date and the auto-charge setting according to the determined payment amount may be associated and saved.

If the payment amount of the payment on at least one payment date is not fixed, the auto-charging system 1 of the modified example related to the modified example 8 performs auto-charging according to the determined payment amount after the payment amount of the payment is determined. Save settings. As a result, it is possible to more reliably prevent insufficient balance at the next payment, thereby increasing convenience for the user.

[Modification regarding modification 9]
For example, in the configuration of Modified Example 9, similarly to the modified examples related to Modified Examples 1 to 8, there does not have to be a plurality of payment dates on which periodic payments are made to different payees. For example, even if there is only one payment date per month, the receiving unit 107 may receive a notification when an operation is performed to agree to the auto-charge setting on the payment destination's service provider server 20. It's okay. For example, the receiving unit 107 may receive notifications in a similar manner even when regular payments to the same payee occur on multiple payment dates.

Furthermore, automatic charge setting may be possible on the periodic payment service side, provided that the user information registered in the payment service and the user information registered in the periodic payment service match. The user information may be any information related to the user, and may be, for example, a name, email address, address, telephone number, or user ID. In this case, the automatic charge setting is not performed when registering as a member of the regular payment service, but after registering as a member of the regular payment service.

In an auto-charge system 1 of a modification related to modification 9, auto-charging settings associated with at least one payment date are performed on the periodic payment service side. As a result, the periodic payment service can seamlessly complete the automatic charge setting, increasing convenience for the user.

[Modification regarding modification 10]
For example, in the configuration of Modified Example 10, similarly to the modified examples related to Modified Examples 1 to 9, there does not have to be a plurality of payment dates on which regular payments are made to different payees. For example, even when there is only one monthly payment date, the second display control unit 108 displays a payment amount screen that distinguishes between the payment amount for payments that occur only once a month and the payment amounts for other payments. G6 may also be displayed. For example, the second display control unit 108 may similarly display the payment amount screen G6 even when regular payments to the same payee occur on multiple payment dates.

Furthermore, if the user accumulates points when electronic money is selected as the payment method for the regular payment service, the second display control unit 108 displays how many points the user will earn by selecting electronic money as the payment method. It may be displayed on the payment amount screen G6 whether the payment amount has been acquired or not. In this case, the second display control unit 108 may display the acquired points on the payment amount screen G6 for each regular payment service. It is assumed that the points generated by payment for the regular payment service are stored in the electronic money database DB1.

The auto-charge system 1 of the modification related to modification 10 reduces the management burden on the user by displaying a payment amount screen G6 that distinguishes the payment amount on at least one payment date and the payment amount for other payments. can.

[Modification regarding modification 11]
For example, in the configuration of Modified Example 11, similarly to the modified examples related to Modified Examples 1 to 10, there does not have to be a plurality of payment dates on which regular payments are made to different payees. For example, even if there is only one monthly payment date, the storage unit 101 may save the auto-charging settings so that multiple charging methods can be used together on the monthly payment date. good. For example, the storage unit 101 similarly stores auto charge settings so that multiple charge methods can be used in combination even when regular payments to the same payee occur on multiple payment dates. It's okay.

The auto-charging system 1 of the modified example related to Modified Example 11 stores at least one payment date and an auto-charging setting indicating that a plurality of charging methods are used together in association with each other. This allows for flexible auto-charging that combines multiple charging methods.

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

For example, the periodic payment service may be a service in which a member who becomes a paid member is required to pay a regular membership fee. For example, if an upper limit is set for auto-charging in each month, the relationship between the auto-charging amount up to now and the upper limit may be displayed on the payment amount screen G6 or another screen. For example, if auto-charging is not to be executed for a certain period of time after auto-charging is executed, this restriction may be lifted immediately before the payment time.

For example, periodic payments may be payments between individuals rather than payments to a service provider. In this case, periodic payments can also be referred to as periodic remittances. For example, when a user sends money to his or her parents using electronic money, a similar auto-charging mechanism can be used. Furthermore, periodic payments may not be performed automatically, but may be performed when a user performs a payment operation. In this case, the user performs payment operations periodically.

For example, instead of having an auto-charge setting for each payment date, an auto-charging setting may exist for each payee. In this case, if the payment is to a specific payee, auto-charging will be performed based on the auto-charging settings associated with the payee. For example, there may be types of electronic money that can be withdrawn and types that cannot be withdrawn. The auto-charge setting may indicate which type of electronic money is to be auto-charged.

For example, the functions described as being implemented by electronic money server 10 may be implemented by service provider server 20 or another server computer. The functions described as being implemented by the service provider server 20 may also be implemented by the electronic money server 10 or other server computers. For example, the functions described as being implemented 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.

[6. Additional notes]
For example, the auto-charging system according to the present disclosure can also have the following configuration. (1)
a storage unit that associates and stores each of a plurality of payment dates on which periodic payments are made to different payees and an auto-charge setting regarding auto-charging of a payment method that can be used for the periodic payment;
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;
Auto charge system including.
(2)
If a plurality of the periodic payments occur on one payment date, the storage section stores information according to the one payment date and the total amount of the payment amount for each of the plurality of periodic payments. associate and save the auto charge settings;
The auto-charging system described in (1).
(3)
When a plurality of the periodic payments occur on one of the payment dates and the payment times of each of the plurality of periodic payments are different from each other within the one payment date, the storage unit stores the periodic payments. save said auto-charge settings separately for each time;
The auto-charge execution unit executes the auto-charge based on the auto-charge setting associated with the payment time until a predetermined payment time among the plurality of regular payments, and when the payment time has passed. If so, performing the auto-charging based on the auto-charging setting associated with the next payment time among the plurality of periodic payments;
The auto-charging system according to (1) or (2).
(4)
The auto charge execution unit may perform the auto charge execution on other days different from the plurality of payment dates based on other auto charge settings different from the auto charge settings associated with each of the plurality of payment dates. perform a charge,
The auto-charging 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.
The auto-charging system according to any one of (1) to (4).
(6)
The storage unit associates and stores each of the plurality of payment dates and the autocharge setting indicating a balance after charging that is 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 is indicated in the auto-charge setting associated with each of the plurality of payment dates.
The auto-charging system according to any one of (1) to (5).
(7)
The auto-charge execution unit executes the auto-charge before the payment time on each of the plurality of payment dates arrives, based on the auto-charge setting associated with the payment date.
The auto-charging system according to any one of (1) to (6).
(8)
When each of the plurality of payment dates comes, the autocharging execution unit is configured to perform autocharging at predetermined time intervals until the payment time, based on the autocharging settings associated with the payment date. Determine whether or not it is necessary.
The auto-charging system described in (7).
(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.
The auto-charging system according to (7) or (8).
(10)
The auto charge system is
A prediction unit that predicts the next payment amount in the periodic payment based on the payment history of the periodic payment for which the payment amount is not fixed among the periodic payments on each of the plurality of payment dates. and,
a determining unit that determines the content of the auto charge setting to be associated with the payment date of the periodic payment for which the payment amount is not fixed, based on the next payment amount predicted by the prediction unit;
The auto-charging system according to any one of (1) to (9), further comprising:
(11)
The storage unit stores data according to the payment date of the periodic payment that allows the payment method and another payment method to be used together, and a portion of the payment amount of the periodic payment, among the plurality of payment dates. It is possible to associate and save the auto charge settings.
The auto-charging system described in (1) to (10).
(12)
Among the plurality of payment dates, on the payment date of the periodic payment for which the payment amount is not fixed, the storage unit stores the fixed payment after the payment amount of the periodic payment is fixed. Associate and save the auto charge settings according to the amount,
The auto-charging 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 receiving the notification.
The auto-charging system according to any one of (1) to (12).
(14)
The auto charge system displays a payment amount screen that distinguishes the payment amount of the periodic payment and the payment amount of other payments different from the periodic payment on each of the plurality of payment dates. 2 further including a display control unit;
The auto-charging system according to any one of (1) to (13).
(15)
The storage unit associates and stores each of the plurality of payment dates and the auto charge setting indicating a charge method selected from a plurality of charge methods.
The auto-charging 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 charge methods in association with each other,
The auto charge execution unit executes the auto charge based on the plurality of charge methods when the auto charge setting indicates a combination of the plurality of charge methods.
The auto-charging system according to any one of (1) to (15).

1 auto charge system, N network, 10 electronic money server, 11, 21, 31 control section, 12, 22, 32 storage section, 13, 23, 33 communication section, 20 service provider server, 30 user terminal, 34 operation section , 35 display section, 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 section, 101 storage section, 102 auto charge execution section, Reference Signs List 103 payment execution unit, 104 first display control unit, 105 prediction unit, 106 determination unit, 107 reception 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 section, 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)

a storage unit that associates and stores each of a plurality of payment dates on which periodic payments are made to different payees and an auto-charge setting regarding auto-charging of a payment method that can be used for the periodic payment;
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;
Auto charge system including.

Images