tencent cloud

TDSQL Boundless

Release Notes
Product Introduction
Overview
Scenarios
Product Architecture
Instance Types
Compatibility Notes
Kernel Features
Kernel Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Billing
Billing Overview
Purchase Method
Pricing Details
Renewal
Overdue Payments
Refund
Getting Started
Creating an Instance
Connect to Instances
User Guide
Data Migration
Data Subscription
Instance Management
Configuration Change
Parameter Configuration
Account Management
Security Group
Backup and Restoration
Database Auditing
Tag Management
Use Cases
Technical Evolution and Usage Practices of Online DDL
Lock Mechanism Analysis and Troubleshooting Practices
Data Intelligent Scheduling and Related Practices for Performance Optimization
TDSQL Boundless Selection Guide and Practical Tutorial
Developer Guide
Developer Guide (MySQL Compatibility Mode)
Developer Guide (HBase Compatibility Mode)
Performance Tuning
Performance Tuning Overview
SQL Tuning
DDL Tuning
Performance White Paper
Performance Overview
TPC-C Test
Sysbench Test
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Security Group APIs
Task APIs
Backup APIs
Rollback APIs
Parameter APIs
Database APIs
Data Types
Error Codes
General Reference
System Architecture
SQL Reference
Database Parameter Description
TPC-H benchmark data model reference
Error Code Information
Security and Compliance
FAQs
Agreements
Service Level Agreement
Terms of Service
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Overdue Payments

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2026-02-10 11:06:00
This article introduces the handling mechanism for TDSQL Boundless payment overdue; please ensure timely account recharge to prevent service interruption.

Yearly/Monthly Subscription-based Cloud Database

Alarms

Alert messages are pushed to users from 7 days before expiration. The system will notify the cloud account creators, as well as global resource collaborators and financial collaborators via email and SMS (the actual receiving method is subject to users' subscription configuration under the Message Center).
For the notification mechanism from 7 days before expiration to resource release, see Billing Process in Prepaid Billing.

Expiration Handling

1. Renewal Processing Before Expiration

Starting from 7 days before resource expiration, the system will automatically send notifications for renewal reminders to users.

2. Grace Period After Expiration

Within 7 days after resource expiration:
The cloud database can still function normally.
The system will continue to send expiration reminders.
It is recommended to renew as soon as possible to avoid service interruption.

3. Service Termination and Destruction Process

Starting from the 8th day after resource expiration:
This cloud database automatically shuts down, stops providing services, can no longer be used, and enters the data retention period.
Data retention period - Resource isolation phase:
Resources will be isolated and retained for 8 days. During this period, users can still power on and renew to recover services.
If no renewal is made, the resources will be destroyed upon expiration of the isolation period.
Data retention period - Final backup phase:
The system automatically creates a final backup before resource destruction.
Final backup data will be retained for 7 days (starting from the destruction date).
Final backups will be automatically cleared upon expiration, and the data cannot be recovered.

Pay-as-you-go cloud database

Note:
Promptly terminate pay-as-you-go instance resources when you no longer use them to avoid further fees.
Your actual resource consumption may change continuously, so the balance warning may have a certain degree of error.

Alarms

The system deducts fees for pay-as-you-go resources at each integral point. When your account balance is less than 0, the system will notify the creators of the cloud account, as well as global resource collaborators and financial collaborators via email and SMS (the actual receiving method is subject to the subscription configuration in the Message Center for users).
Message notification mechanism, see Pay-as-you-go Billing Description.

Arrears Handling

1. When the Account Is in Arrears (Balance < 0):

Within 24 hours: The cloud database can still function normally and will continue to be billed.
Exceeding 24 hours: The cloud database automatically shuts down, stops providing services, and stops billing.

2. After Automatic Shutdown

2.1. Within 8 Days After Shutdown:

If the account balance is topped up to ≥ 0, you can manually power on the instance to restore services.
If the balance remains < 0, you will be unable to power on the instance.

2.2. After 8 Days of Shutdown:

If the account remains overdue, the cloud database resources will be destroyed.
Upon destruction of the cloud database, the system will notify the Tencent Cloud account creator, collaborators for global resources, and financial collaborators via email and SMS.
The system automatically creates a final backup of resources before destruction.

2.3. Clearance Period for Final Backups:

The final backup created automatically will have its data retained for 7 days (starting from the destruction date).
Final backups will be automatically cleared upon expiration, and the data cannot be recovered.

Ajuda e Suporte

Esta página foi útil?

comentários