JP2021076993A - Accounting management device and program - Google Patents

Abstract

To provide appropriate relief to a user who has missed payment deadline for an accounting service by treating the user according to duration of its use of the accounting service.SOLUTION: An accounting management server 40 sets a grace period before current use of a billing item 32a for which next payment due date has passed is restricted. When setting the grace period, the accounting management server 40 varies length of the grace period according to the length of the approved purchase period of the billing item 32a up to the previous or current time.SELECTED DRAWING: Figure 6

Description

The present invention relates to a billing management device and a program.

Conventionally, as a network management system, for example, an automatic service stop monitoring system has been proposed in which a non-paying subscriber is detected, and when the non-paying subscriber is detected, the telephone service of the subscriber is stopped for a certain period of time. (See, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 10-210191

However, the system disclosed in Patent Document 1 has a problem that it is harsh for non-payment subscribers because there is no grace period until the telephone service is stopped. Further, since the telephone service is stopped regardless of the subscription period of the telephone service of the non-paying subscriber, there is a problem that there is little merit of continuously subscribing to the telephone service.

The present invention has been made in view of such a problem, and an object of the present invention is to appropriately relieve a user who has passed the payment deadline of a billing item by treatment according to the purchase continuation period of the billing item. And.

In order to solve the above problems, the billing management device according to the present invention is used.
Equipped with a setting means to set a grace period until the use of the billing item whose payment deadline for the next time has passed is restricted.
When setting the grace period, the setting means makes the length of the grace period different depending on the length of the purchase continuation period of the billing item up to the previous time or the present time.

According to the present invention, a user who has passed the payment deadline of a billing item can be appropriately relieved by treatment according to the purchase continuation period of the billing item.

It is a schematic block diagram which shows the in-app billing system of this embodiment. It is a block diagram which shows the functional structure of a terminal device. It is a block diagram which shows the functional structure of a cloud server. It is a block diagram which shows the functional structure of the billing management server. It is a figure which shows the management data table. It is a figure which shows the grace control parameter information. It is a flowchart which shows an example of the operation of the in-app billing system when a billing item is purchased. It is a flowchart which shows an example of the operation of the in-app purchase system when the login operation to the mobile application is performed. It is a flowchart which shows an example of the polling operation by a billing management server and a store server.

Hereinafter, a specific aspect of the present invention will be described with reference to the drawings.

<< Configuration of in-app purchase system 1 >>
First, the configuration of the present embodiment will be described with reference to FIG. FIG. 1 is a schematic configuration diagram showing the in-app billing system 1 of the present embodiment.

As shown in FIG. 1, the in-app billing system 1 includes a terminal device 10, a store server 20, a cloud server 30, a billing management server 40, and the like. The terminal device 10, the store server 20, the cloud server 30, and the billing management server 40 are connected to each other via the communication network N so that they can communicate with each other.

The terminal device 10 is, for example, a smartphone or tablet terminal used by the user. Specifically, the terminal device 10 is an iPhone (registered trademark) or iPad (registered trademark) provided by Apple (registered trademark), and an Android (registered trademark) version of a smartphone or tablet provided by Google (registered trademark). It is a terminal. The number of terminal devices 10 is not particularly limited.

The store server 20 is a server that issues a receipt for the purchase of a billing item (including the billing item 32a (described later)) in the mobile application 12a (described later) activated in the terminal device 10. Is. Further, the store server 20 is a server that verifies whether or not the receipt is valid when a verification request for the receipt (receipt issued by the store server 20) is made by the billing management server 40 described later. .. The store server 20 is at least two of a store server compatible with the above-mentioned iPhone (registered trademark) and iPad (registered trademark) and a store server compatible with the above-mentioned Android (registered trademark) version of a smartphone or tablet terminal. Consists of different types of store servers.

The cloud server 30 is a server that provides a cloud service (for example, use of a billing item 32a) when using the mobile application 12a (described later) started in the terminal device 10.

The billing management server 40 is a server that manages the billing status of billing items 32a and the like that can be purchased in the mobile application 12a activated in the terminal device 10.

<Configuration of terminal device 10>
Next, the configuration of the terminal device 10 will be described with reference to FIG. FIG. 2 is a block diagram showing a functional configuration of the terminal device 10.

As shown in FIG. 2, the terminal device 10 includes a control unit 11, a storage unit 12, an operation unit 13, a display unit 14, a communication unit 15, and the like.

The control unit 11 includes a CPU that executes various programs stored in the storage unit 12 to perform predetermined operations and control each unit, and a memory that serves as a work area during program execution (all of which are not shown). ). The control unit 11 executes various processes in cooperation with the program stored in the storage unit 12.

The storage unit 12 is composed of a non-volatile semiconductor memory or the like. The storage unit 12 stores system programs and application programs executed by the control unit 11, data necessary for executing these programs, and the like. Further, the storage unit 12 stores, for example, a certain mobile application 12a downloaded from the store server 20 via the communication network N.

The mobile application 12a incorporates an API (Application Programming Interface) for so-called in-app purchase, and the charge item 32a (described later) can be purchased by using the API. More specifically, the billing method for this billing item 32a is a monthly billing method, and the user can use this billing item 32a by performing a subscription procedure (continuous billing for automatic renewal). You can do it.

The operation unit 13 includes various function keys, receives press input of each key by the user, and outputs the operation information to the control unit 11. Further, the operation unit 13 has a touch panel or the like in which transparent electrodes are arranged in a grid pattern so as to cover the surface of the display unit 14, detects a position pressed by a finger, a touch pen, or the like, and uses the position information as operation information. Output to the control unit 11.

The display unit 14 is composed of an LCD (Liquid Crystal Display) or the like, and performs various displays on the screen according to a display control signal from the control unit 11.

The communication unit 15 wirelessly connects to the communication network N and communicates with an external device connected to the communication network N.

<Configuration of cloud server 30>
Next, the configuration of the cloud server 30 will be described with reference to FIG. FIG. 3 is a block diagram showing a functional configuration of the cloud server 30.

As shown in FIG. 3, the cloud server (billing item providing means) 30 includes a control unit 31, a storage unit 32, a communication unit 33, and the like.

The control unit 31 includes a CPU that executes various programs stored in the storage unit 32 to perform predetermined calculations and controls each unit, and a memory that serves as a work area during program execution (all of which are not shown). ). The control unit 31 executes various processes in cooperation with the program stored in the storage unit 32.

The storage unit 32 is composed of a non-volatile semiconductor memory or the like. The storage unit 32 stores system programs and application programs executed by the control unit 31, data necessary for executing these programs, and the like.

In addition, the storage unit 32 stores billing items 32a and the like that can be used in the mobile application 12a described above. When the payment (subscription) of the billing item 32a by one user is approved, the control unit 31 is in the mobile application 12a in which the one user logs in via the terminal device 10 until the next payment deadline. The billing item 32a can be used in.

The communication unit 33 is composed of a modem, a router, a network card, and the like. The communication unit 33 transmits / receives data to / from an external device connected via the communication network N.

<Configuration of billing management server 40>
Next, the configuration of the billing management server 40 will be described with reference to FIG. FIG. 4 is a block diagram showing a functional configuration of the billing management server 40.

As shown in FIG. 4, the charge management server (charge management device) 40 includes a control unit 41, a storage unit 42, a communication unit 43, and the like.

The control unit (determining means, first setting means (setting means), second setting means, reporting means) 41 executes various programs stored in the storage unit 42 to perform predetermined calculations and control each unit. It is equipped with a CPU that performs the above and a memory that serves as a work area when the program is executed (both are not shown). The control unit 41 executes various processes in cooperation with the program stored in the storage unit 42.

The storage unit 42 is composed of a non-volatile semiconductor memory or the like. The storage unit 42 stores system programs and application programs executed by the control unit 41, data necessary for executing these programs (including grace control parameter information 42b (described later)), and the like.

Further, the storage unit 42 is provided with a billing management DB 42a. The billing management DB 42a stores a management data table for managing the billing status of each user who subscribes to various billing items including the billing item 32a.

FIG. 5 is a diagram showing the management data table. The data table shown in FIG. 5 is, for example, a data table showing the billing status as of September 10, 2019.
As shown in FIG. 5, in the management data table, for example, "user code", "content number", "purchasing device", "current receipt status", "first purchase date", "receipt expiration date", Items such as "reason for expiration", "purchase continuation period", "approved purchase continuation period", "grace period", "number of disapprovals (penalties)", "contract" are provided, and data related to these items are provided to each other. It is designed to be associated and stored.

Here, the "user code" is a code for identifying each user. The "content number" is a number for identifying each billing item. The "purchasing device" represents the type of terminal device 10 used when purchasing a billing item. The "current receipt status" indicates the payment status (normal or expired) determined based on the current receipt (the latest receipt grasped by the billing management server 40). The "first purchase date" is the date on which the target billing item is purchased for the first time. The "receipt deadline" is the next payment deadline.

The "reason for expiration" indicates the reason why the expiration date shown in the "receipt expiration date" item described above has been passed, and is one of "billing error", "cancellation", and "none". Represented by. A "billing error" is described when, for example, the payment amount cannot be collected due to the expiration date of the credit card or the insufficient balance of the prepaid card. In addition, "cancellation" is described when the user cancels the subscription contract of the target billing item. In addition, "none" is written when the deadline has not been passed. The "purchase continuation period" is the period during which the target billing item is continuously subscribed. In other words, it represents the period from the "first purchase date" to the "receipt expiration date". The "approved purchase continuation period" is the period during which the target billing item is continuously subscribed without exceeding the payment deadline. Therefore, once the payment deadline is overdue, it is the period from the date of the overdue to the present. The maximum period of the subscription period (purchase period) of the past billing item 32a that does not exceed the payment deadline may be the approved purchase continuation period. The "grace period" is a deadline date derived based on the grace period (described later) set when the payment deadline is overdue. The timing for setting the grace period is not limited to when the payment deadline has passed, and may be another timing such as when the billing item 32a is purchased (subscription renewal). The "number of disapprovals (penalties)" is the number of times the payment deadline has been passed in the past. The "contract status" indicates the current contract status, and the mobile app 12a is in a state where it is possible to log in to the mobile application 12a and use the target billing item. "Stop using", which means that you can log in but cannot use the target billing item, and "Automatic cancellation", which means that you cannot log in to the mobile app 12a or use the target billing item. ", It is represented by one of" self-cancellation ", which is a state in which the user can log in to the mobile application 12a but cannot use the charge item due to the cancellation of the subscription contract of the target charge item. ..

Here, the method of setting the grace period described above will be described.
The control unit 41 uses the grace control parameter information 42b stored in the storage unit 42 for the data in which the information of the "current receipt status" item in the management data table has changed from "normal" to "expired". Set a grace period.
Specifically, by using the grace control parameter information 42b shown in FIG. 6, the control unit 41 uses 20 days when the approval purchase continuation period is 10 years or more, 10 days when the approval purchase continuation period is 5 years or more, and 3 years or more. In the case of, the grace period is set to 5 days, in the case of 1 year or more, 3 days, and in the case of less than 1 year, 0 days.

In addition, a method of setting the information of the above-mentioned "contract status" item will be described.
The control unit 41 uses the grace control parameter information 42b stored in the storage unit 42 for the data whose grace period has expired, which is shown in the item of "grace period" of the management data table, to display the item of "contract status". Set the information.
Specifically, the control unit 41 uses the grace control parameter information 42b shown in FIG. 6 to provide information on the item of "contract status" regardless of the number of disapprovals when the approval purchase continuation period is 5 years or more. Set to "suspend". In addition, if the approval purchase continuation period is 1 year or more and less than 5 years, if the number of disapprovals is less than 3 times, the information in the item of "contract status" is set as "suspension of use" and the number of disapprovals is 3 times or more. If so, set the information in the "Contract status" item to "Automatic cancellation". If the approval purchase continuation period is less than one year, the information in the "contract status" item is set to "automatic cancellation" regardless of the number of disapprovals. If the information in the "contract status" item is set to "suspension of use", as shown in FIG. 5, the date of suspension of use in this "contract status" item (for example, 2019/8 / 30) is also written. In addition, when the information of the item of "contract status" is set to "automatic cancellation", as shown in FIG. 5, the date of automatic cancellation in the item of "contract status" (for example, 2019/8 / 28) is also written.
Further, the control unit 41 is in a state where the information of the item of "grace period" in the above management data table is not set, or the information of the item of "grace period" is set but the grace period has not passed. For, the information in the "contract status" item is set to "under contract". However, when the user cancels the subscription contract of the target billing item, the control unit 41 sets the information of the item of "contract status" as "self-cancellation". If the information in the "Contract status" item is set to "Self-cancellation", as shown in Fig. 5, the date when the self-cancellation procedure was performed in this "Contract status" item (for example, 2019 / 7/25) is also written.

The communication unit 43 is composed of a modem, a router, a network card, and the like. The communication unit 43 transmits / receives data to / from an external device connected via the communication network N.

≪Operation of in-app purchase system 1≫
Next, the operation of the in-app purchase system 1 in each phase will be described with reference to FIGS. 7 to 9.

<Operation of in-app billing system 1 when billing item 32a is purchased>
FIG. 7 is a flowchart showing an example of the operation of the in-app billing system 1 when the billing item 32a is purchased.

As shown in FIG. 7, first, when the procedure operation for purchasing the billing item 32a in the mobile application 12a running in the terminal device 10 is performed via the operation unit 13, the billing item 32a Is performed, and a payment request is made to the store server 20 (step S1).

Next, the store server 20 that has received the payment request issues a receipt for the purchase of the billing item 32a, and transmits the receipt to the terminal device 10 (step S2).

Next, the terminal device 10 that has received the receipt transfers the receipt and the login information of the user who is logged in to the mobile application 12a from the own device to the cloud server 30 (step S3).

Next, the cloud server 30 transfers the transferred receipt to the billing management server 40, and also transfers the user code extracted from the login information to the billing management server 40 (step S4).

Next, when the billing management server 40 receives the receipt and the user code, the billing management server 40 requests the store server 20 to verify whether or not the receipt is a valid receipt (step S5).

Next, the store server 20 verifies the receipt based on the receipt verification request by the billing management server 40, and transmits the verification result to the billing management server 40 (step S6). Then, the process by the store server 20 is terminated.

Next, the billing management server 40 reports the received verification result to the cloud server 30 (step S7). Further, the billing management server 40 updates the information of the billing management DB 42a based on the received verification result (step S8). Specifically, the billing management server 40 updates the data of the user who purchased the billing item 32a in step S1 of the management data table (see FIG. 5). For example, if the subscription of the billing item 32a contracted by the user whose user code is "aaaaaa" is renewed on September 25, 2019, the information of the item "receipt expiration date" shown in FIG. 5 is "2019". It will be updated to "10/25", and the information of the items of "Purchase duration" and "Approved purchase duration" will be updated to "3 years and 5 months" respectively. In addition, when the user whose user code is "dddddd" subscribes to the billing item 32a on September 25, 2019, the information of the "current receipt status" item shown in FIG. 5 is updated to "normal". Then, the information of the item of "Receipt expiration date" is updated to "2019/10/25", the information of the item of "Expiration reason" is updated to "None", and the information of the item of "Purchase continuation period" is updated. Updated to "4 years and 6 months", the information in the "Approved purchase duration" item is updated to "0 years and 1 month", the information in the "Disapproval count" item is updated to "1", and "Contract status" The information in the item "" is updated to "Under contract". Then, the process by the billing management server 40 is terminated.

Next, when the cloud server 30 that has received the report of the result of the above verification is a report that the report is a valid receipt (step S9; YES), the charge by the user who purchased the charge item 32a in step S1. The use of the item 32a is permitted, and the charging item 32a is provided to the terminal device 10 of the user (step S10). Then, the process by the cloud server 30 is terminated.
On the other hand, when the above report is a report that the receipt is not valid (step S9; NO), the cloud server 30 disallows the user who purchased the billing item 32a in step S1 from using the billing item 32a. An error notification is sent to the user's terminal device 10 (step S11). Then, the process by the cloud server 30 is terminated.

<Operation of in-app purchase system 1 when login operation to mobile app 12a is performed>
FIG. 8 is a flowchart showing an example of the operation of the in-app purchase system 1 when the login operation to the mobile application 12a is performed.

As shown in FIG. 8, first, when the operation for logging in to the mobile application 12a is performed via the operation unit 13, the terminal device 10 performs the login process to the mobile application 12a, and at this time, the operation unit 13 The login information input via the above is transmitted to the cloud server 30 (step S21).

Next, the cloud server 30 that has received the login information extracts the user code from the login information and transfers the user code to the billing management server 40 (step S22).

Next, the billing management server 40 that has received the user code collates the user code using the management data table (see FIG. 5) of the billing management DB 42a (step S23). Then, the billing management server 40 reports the collation result regarding the user code to the cloud server 30 (step S24). Then, the process by the billing management server 40 is terminated.

Next, the cloud server 30 determines whether or not the contract status for the user code is "self-cancellation" based on the report from the billing management server 40 (step S25).

If it is determined in step S25 that the contract status for the user code is "self-cancellation" (step S25; YES), the cloud server 30 disallows the user of the user code to use the billing item 32a. , Notifies the user's terminal device 10 that the billing item 32a cannot be used (step S26).
On the other hand, if it is determined in step S25 that the contract status for the user code is not "self-cancellation" (step S25; NO), the cloud server 30 has a grace period for payment of the billing item 32a for the user code. Is determined (step S27).

If it is determined in step S27 that the grace period for payment of the billing item 32a has not yet passed (step S27; NO), the cloud server 30 permits the user of the above user code to use the billing item 32a. The billing item 32a is provided to the terminal device 10 of the user (step S28).
On the other hand, if it is determined in step S27 that the grace period for payment of the billing item 32a has expired (step S27; YES), the cloud server 30 uses the above user code based on the report from the billing management server 40. It is determined whether or not the contract status of the above is "suspension of use" (step S29).

If it is determined in step S29 that the contract status for the user code is "suspended" (step S29; YES), the cloud server 30 disallows the user of the user code to use the billing item 32a. , Notifies the user's terminal device 10 that the billing item 32a cannot be used (step S30).
On the other hand, in step S29, when it is determined that the contract status for the user code is not "suspension of use" (step S29; NO), the cloud server 30 uses the user based on the report from the billing management server 40. It is determined whether or not the contract status for the code is "automatic cancellation" (step S31).

If it is determined in step S31 that the contract status for the user code is "automatic cancellation" (step S31; YES), the cloud server 30 does not allow the user of the user code to log in to the mobile application 12a. Then, the user is notified that he / she cannot log in to the terminal device 10 (step S32). Then, the process by the cloud server 30 is terminated.
On the other hand, in step S31, when it is determined that the contract status for the user code is not "automatic cancellation" (step S31; NO), the processing by the cloud server 30 is terminated.

<Polling operation by billing management server 40 and store server 20>
FIG. 9 is a flowchart showing an example of polling operation by the billing management server 40 and the store server 20.

As shown in FIG. 9, first, the billing management server 40 extracts the receipt information of the user code in the grace period from the management data table of the billing management DB 42a at a predetermined time every day, and based on the receipt information. The receipt status is sequentially inquired to the store server 20 (step S31). Here, for example, as shown in FIG. 5, the receipt information includes information on items other than the "user code" and "content number" in the management data table, and the management data table is omitted from the illustration. However, the information of the item of "final receipt data" is included.

Next, the store server 20 reports the result of the inquiry to the billing management server 40 (step S32). Then, the process by the store server 20 is terminated.

Next, the billing management server 40 determines whether or not the report received from the store server 20 is a report indicating that there is progress (step S33).

If it is determined in step S33 that there is progress (step S33; YES), the billing management server 40 updates the receipt information of the user code with progress, more specifically, for example. , Correct the information of each item of "current receipt status", "receipt expiration date", "expiration reason", "purchase continuation period", "approved purchase continuation period", and "number of disapprovals" shown in FIG. (Step S34), the process proceeds to step S35. On the other hand, if it is determined in step S33 that the report does not indicate that there is progress (step S33; NO), the billing management server 40 advances the process to step S35.

Next, the billing management server 40 determines whether or not all the receipt statuses of the receipt information (target receipt information) of the user code during the grace period have been inquired (step S35).

If it is determined in step S35 that all the receipt statuses of the target receipt information have been inquired (step S35; YES), the processing by the billing management server 40 ends.
On the other hand, if it is determined in step S35 that all the receipt statuses of the target receipt information have not been inquired (step S35; NO), the billing management server 40 returns the process to step S31 and repeats the subsequent processes. ..

As described above, the billing management server 40 of the in-app billing system 1 of the present embodiment sets a grace period until the use of the billing item 32a whose payment deadline for the next time has passed is restricted. Further, when setting the grace period, the billing management server 40 makes the length of the grace period different according to the length of the approval purchase continuation period of the billing item 32a up to the previous time or the present time.
Therefore, according to the billing management server 40 of the present embodiment, the user who has passed the payment deadline of the billing item 32a can be appropriately relieved by the treatment according to the approval purchase continuation period of the billing item 32a. ..
In addition, Apple (registered trademark) and Google (registered trademark) each provide their own mechanism to enable the setting of the grace period, but since the grace period that can be set differs depending on each company, which store the user can set. It is not fair because the grace period that can be enjoyed differs depending on whether you use the server. Therefore, by setting an original grace period by the billing management server 40 without using the above mechanism, a unified grace period can be set regardless of which store server the user uses. Fairness can be maintained in the relief of users.

Further, when it is determined that the payment deadline has passed, the billing management server 40 of the present embodiment sets a grace period until the use of the billing item 32a whose payment deadline has passed is restricted.
Therefore, according to the billing management server 40 of the present embodiment, the grace period is set based on the timing when the payment deadline has passed, so that the grace period can be set fairly.

Further, according to the billing management server 40 of the present embodiment, grace periods having different lengths are set corresponding to each division period divided by a plurality of preset threshold values, and the payment deadline has passed. Since the grace period corresponding to the above-mentioned division period to which the length of the approval purchase continuation period up to that point of the billing item 32a applies is set, the grace period can be set fairly and efficiently.

Further, the billing management server 40 of the present embodiment suspends the use of the billing item 32a or contracts for the mobile application 12a in which the billing item 32a is used when payment is not made during the above grace period. A cloud server (billing item providing means) 30 that sets whether to cancel (automatic cancellation) and suspends the use of the set billing item 32a or cancels the contract of the mobile application 12a (automatic cancellation) to provide the billing item 32a. Report to.
Therefore, according to the billing management server 40 of the present embodiment, it is possible to efficiently deal with the target user of the cloud server 30 when payment is not made during the grace period.

Further, in the billing management server 40 of the present embodiment, if payment is not made during the above grace period, the number of disapprovals is 3 or more, and the length of the approval purchase continuation period of the billing item 32a is long. When it is 5 years (threshold) or more, the use of the billing item 32a is set to be suspended, while the number of disapprovals is 3 or more and the length of the approval purchase continuation period of the billing item 32a. If is less than 5 years (threshold), the contract of the mobile application 12a is set to be canceled (automatic cancellation). Further, the billing management server 40 suspends the use of the billing item 32a when the number of disapprovals is less than 3 and the length of the approval purchase continuation period of the billing item 32a is one year (threshold) or more. On the other hand, if the number of disapprovals is less than 3 and the length of the approval purchase continuation period of the billing item 32a is less than 1 year (threshold), the contract of the mobile application 12a is canceled ( Set to set as automatic cancellation).
Therefore, according to the billing management server 40 of the present embodiment, the user who has passed the payment grace period of the billing item 32a is appropriately relieved by the treatment according to the approval purchase continuation period and the number of disapprovals of the billing item 32a. can do.

Although the present invention has been specifically described above based on the embodiments, the present invention is not limited to the above embodiments and can be modified without departing from the gist thereof.
For example, in the above embodiment, the in-app billing system 1 is divided into a cloud server 30 and a billing management server 40 from the viewpoint of security, but the cloud server 30 and the billing management server 40 may be integrated as one server. ..

Further, in the above embodiment, when setting the grace period, the billing management server 40 makes the length of the grace period different according to the length of the approval purchase continuation period of the billing item 32a up to the previous time or this time. However, for example, the length of the grace period may be different depending on the number of times the payment deadline has passed in the past for the billing item 32a whose payment deadline has passed for the next time. In such cases, the longer the grace period, the more times the payment deadline has passed in the past.

Further, in the above embodiment, the grace period is set according to the length of the "approved purchase continuation period", but the length of the grace period is simply changed according to the length of the "purchase continuation period". The configuration may be different.

Further, in the above embodiment, the period from the "first purchase date" to the "receipt expiration date" is set as the "purchase continuation period", but from the "first purchase date" to the "previous billing item purchase date". The period of may be set as the "purchase continuation period".

Further, in the above embodiment, the control unit 41 of the billing management server 40 uses the grace control parameter information 42b shown in FIG. 6 to set the grace period and the contract state when the grace period is exceeded. For example, the control unit (changing means) 41 may be able to change the parameters of the grace control parameter information 42b based on the operation of the user who manages the billing management server 40.

Further, in the above embodiment, when the grace period is set due to the payment deadline of the billing item 32a having passed, the control unit (notification means) 41 of the billing management server 40 is directed to the terminal device 10 of the corresponding user. You may notify that the grace period has been set.

Further, in the above-described embodiment, an example in which a non-volatile semiconductor memory or the like is used as a computer-readable medium for the program according to the present invention has been disclosed, but the present invention is not limited to this example. As another computer-readable medium, a portable recording medium such as a CD-ROM can be applied. A carrier wave is also applied as a medium for providing the data of the program according to the present invention via a communication line.

Although the embodiments of the present invention have been described, the scope of the present invention is not limited to the above-described embodiments, but includes the scope of the invention described in the claims and the equivalent scope thereof.
The inventions described in the claims originally attached to the application of this application are added below. The claims in the appendix are as specified in the claims originally attached to the application for this application.
[Additional Notes]
<Claim 1>
It has a first setting means to set a grace period until the use of the billing item whose payment deadline for the next time has passed is restricted.
The first setting means, when setting the grace period, is characterized in that the length of the grace period is made different according to the length of the purchase continuation period of the billing item up to the previous time or the present time. apparatus.
<Claim 2>
A determination means for determining whether or not the payment deadline for the next billing item has passed is provided.
When the determination means determines that the payment deadline has passed, the first setting means sets a grace period until the use of the billing item whose payment deadline has passed is restricted. Item 1. The billing management device according to item 1.
<Claim 3>
Grace periods with different lengths are set corresponding to each division period divided by a plurality of preset threshold values.
The first setting means according to claim 1 or 2, wherein a grace period corresponding to the division period to which the length of the purchase continuation period up to that time of the billing item whose payment deadline has passed is applied. The described billing management device.
<Claim 4>
It has a first setting means to set a grace period until the use of the billing item whose payment deadline for the next time has passed is restricted.
When setting the grace period, the first setting means makes the length of the grace period different according to the number of times the payment deadline has passed for the billing item whose payment deadline has passed for the next time. Characterized billing management device.
<Claim 5>
A second setting means for setting whether to suspend the use of the billing item or cancel the contract of the application in which the billing item is used when payment is not made during the grace period.
A reporting means for reporting the suspension of use of the billing item or cancellation of the contract of the application set by the second setting means to the billing item providing means for providing the billing item, and
The billing management device according to any one of claims 1 to 4, wherein the billing management device is provided.
<Claim 6>
The second setting means sets to stop the use of the billing item when the length of the purchase continuation period of the billing item is equal to or greater than the threshold value, while the length of the purchase continuation period of the billing item is set. The billing management device according to claim 5, wherein if the value is less than the threshold value, the contract of the application is set to be canceled.
<Claim 7>
The second setting means is further described in claim 6, wherein the value of the threshold value is made different according to the number of times the payment deadline has expired in the past for the billing item whose payment deadline for the next time has passed. Billing management device.
<Claim 8>
Conditions for setting the grace period by the first setting means and conditions for setting whether to suspend the use of the billing item or cancel the contract of the application by the second setting means. The billing management device according to claim 6 or 7, further comprising a changing means capable of changing at least one of the conditions based on a user operation.
<Claim 9>
When the grace period is set by the first setting means, it is characterized by providing a notification means for notifying the purchaser of the billing item for which the grace period has been set to the effect that the grace period has been set. The billing management device according to any one of 1 to 8.
<Claim 10>
The computer of the billing management device,
Equipped with a setting means to set a grace period until the use of billing items whose payment deadline has passed for the next time is restricted
The setting means is a program characterized in that when setting the grace period, the length of the grace period is changed according to the length of the purchase continuation period of the billing item up to the previous time or the present time.
<Claim 11>
The computer of the billing management device,
Equipped with a setting means to set a grace period until the use of the billing item whose payment deadline for the next time has passed is restricted.
When setting the grace period, the setting means makes the length of the grace period different according to the number of times the payment deadline has passed in the past for the billing item whose payment deadline has passed for the next time. program.

1 In-app billing system 10 Terminal device 12a Mobile app 20 Store server 30 Cloud server (means for providing billing items)
32a Billing item 40 Billing management server (billing management device)
41 Control unit (determination means, first setting means (setting means), second setting means, reporting means)

Claims (11)

It has a first setting means to set a grace period until the use of the billing item whose payment deadline for the next time has passed is restricted.
The first setting means, when setting the grace period, is characterized in that the length of the grace period is made different according to the length of the purchase continuation period of the billing item up to the previous time or the present time. apparatus. A determination means for determining whether or not the payment deadline for the next billing item has passed is provided.
When the determination means determines that the payment deadline has passed, the first setting means sets a grace period until the use of the billing item whose payment deadline has passed is restricted. Item 1. The billing management device according to item 1. Grace periods with different lengths are set corresponding to each division period divided by a plurality of preset threshold values.
The first setting means according to claim 1 or 2, wherein a grace period corresponding to the division period to which the length of the purchase continuation period up to that time of the billing item whose payment deadline has passed is applied. The described billing management device. It has a first setting means to set a grace period until the use of the billing item whose payment deadline for the next time has passed is restricted.
When setting the grace period, the first setting means makes the length of the grace period different according to the number of times the payment deadline has passed for the billing item whose payment deadline has passed for the next time. Characterized billing management device. A second setting means for setting whether to suspend the use of the billing item or cancel the contract of the application in which the billing item is used when payment is not made during the grace period.
A reporting means for reporting the suspension of use of the billing item or cancellation of the contract of the application set by the second setting means to the billing item providing means for providing the billing item, and
The billing management device according to any one of claims 1 to 4, wherein the billing management device is provided. The second setting means sets to stop the use of the billing item when the length of the purchase continuation period of the billing item is equal to or greater than the threshold value, while the length of the purchase continuation period of the billing item is set. The billing management device according to claim 5, wherein if the value is less than the threshold value, the contract of the application is set to be canceled. The second setting means is further described in claim 6, wherein the value of the threshold value is made different according to the number of times the payment deadline has expired in the past for the billing item whose payment deadline for the next time has passed. Billing management device. Conditions for setting the grace period by the first setting means and conditions for setting whether to suspend the use of the billing item or cancel the contract of the application by the second setting means. The billing management device according to claim 6 or 7, further comprising a changing means capable of changing at least one of the conditions based on a user operation. When the grace period is set by the first setting means, it is characterized by providing a notification means for notifying the purchaser of the billing item for which the grace period has been set to the effect that the grace period has been set. The billing management device according to any one of 1 to 8. The computer of the billing management device,
Equipped with a setting means to set a grace period until the use of billing items whose payment deadline has passed for the next time is restricted
The setting means is a program characterized in that when setting the grace period, the length of the grace period is changed according to the length of the purchase continuation period of the billing item up to the previous time or the present time. The computer of the billing management device,
Equipped with a setting means to set a grace period until the use of the billing item whose payment deadline for the next time has passed is restricted.
When setting the grace period, the setting means makes the length of the grace period different according to the number of times the payment deadline has passed in the past for the billing item whose payment deadline has passed for the next time. program.

Images