When you create a subscription offering you can set up how frequently you would like to bill your users. However, note that a monthly cycle bills on the corresponding day of the next month rather than at a fixed interval of 30 days. For example, if a user signs up on the 5th of November, the next bill will occur on the 5th of December, and the following bill will be on the 5th of January.
Similarly, this logic applies to billing periods that repeat every 3 months, every 6 months, and every year.
The exception being if a user purchases a subscription or is billed in a month on a date that does not exist in the following month (for example they are billed on January 31st, but February only has 28 days), then the next billing date falls on the last day of that month. Thus, in this example, the renewal would happen on February 28th, or the 29th in the event of a leap year.
This will result in shifting the renewal date for the subsequent months as well. In our example, if a user subscribes to a monthly term on January 31st, the next renewal date happens on February 28th. The following renewals will also happen on the 28th day of the subsequent months - on March 28th, April 28th, and so on.
Subscription Renewal
Piano employs a comprehensive renewal system to ensure seamless and uninterrupted access for users with active subscriptions.
When a subscription is initially purchased, the next billing date is set based on the billing period. The access expiration time is set on the next renewal date at 11:59 pm.
Upon the next billing date, there are multiple attempts/runs per day (starting at around 02:20 AM EST) when renewals are processed based on multiple factors such as renewal volume, release schedule, and time when the subscription renewal date was last modified.
Therefore you may observe transactions throughout the day, as the renewal job processes subscription renewals in batches.
In cases where a transaction is declined during renewal, the further handling depends on whether a grace period is enabled or not.