This document introduces the overdue payment handling mechanism of TDSQL-C for MySQL accounts. Please top up promptly to avoid resource unavailability.
Note：
If you are a customer of a Tencent Cloud partner, the rules regarding resources when there are overdue payments are subject to the agreement between you and the partner.
Overdue Payment Handling Mechanism for Yearly/Monthly Subscription Instances
Introduction of Overdue Payment Warning
During the period from 7 days before instance expiration until the instance release time, the system will send warning messages to the users. Notifications will be sent to the Tencent Cloud account creator, global resource collaborators, and financial collaborators through methods such as email and SMS (the actual receiving method will be based on the users' message center subscription configurations). For detailed notification mechanisms regarding message reminders from 7 days before instance expiration until instance release time, see Prepaid Billing > Billing Process. Overdue Payment Handling Mechanism
The system will send users renewal reminder notifications 7 days before the expiration of the instance.
The instance can continue to be used within 7 days after expiration, but renewal is required as soon as possible. The system will send expiration reminder notifications for cloud resources.
Starting from the 8th day after expiration, the instance will no longer be used and will be moved to the recycle bin. Users can view the instance on the recycle bin page in the console and can still perform renewal operations.
The maximum retention period in the recycle bin is 7 days. If the instance is not renewed after being in the recycle bin for 7 days, it will be reclaimed by the system, and the data will be cleared and unrecoverable.
After expiration, the instance has 7 days available for use and 7 days not available for use, giving users a total of 14 days to renew the instance. If there is sufficient balance, instances that are set to automatic renewal will also be renewed as usual.
Overdue Payment Handling Mechanism for Pay-as-You-Go Instances
Note
Terminate pay-as-you-go resources promptly when they are no longer used to avoid further charges. Your actual resource consumption may change continuously, so the balance warning may have a certain degree of error.
If the compute billing mode of TDSQL-C for MySQL is yearly/monthly subscription and the storage billing mode is pay-as-you-go, the overdue payment handling mechanism for the instance will be consistent with that of pay-as-you-go instances.
Introduction of Overdue Payment Warning
The system will charge for pay-as-you-go instances on the hour. When the user's account balance is less than 0, the system will notify the Tencent Cloud account creator, global resource collaborators, and financial collaborators through methods such as email and SMS (the actual receiving method will be based on the users' message center subscription configurations). Overdue Payment Handling Mechanism
From the moment when your account balance is less than 0:
Within 24 hours, TDSQL-C for MySQL instances will continue to be used and charged.
After 24 hours, TDSQL-C for MySQL instances will be isolated, charging is stopped, and they will be removed from the instance list and displayed in the recycle bin.
After isolation:
Within 7 days of isolation, if the balance is topped up to be greater than or equal to 0, billing will continue, and instances that are isolated due to overdue payment will be recovered automatically and resume operation.
After 7 days of isolation, if your account balance remains less than 0, the isolated instances will be taken offline and placed in the recycling queue. After recycling, all data will be cleared and will not be recovered. When instances are recycled, the system will notify the Tencent Cloud account creator, global resource collaborators, and financial collaborators, through methods such as email and SMS.