tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Refund

PDF
Focus Mode
Font Size
Last updated: 2026-03-24 15:44:16
TDSQL-C for MySQL supports termination/refund operations on clusters or instances under clusters in the console. This document describe the refund instructions.
Yearly/monthly subscription (prepaid): For TDSQL-C for MySQL, each account is entitled to unconditional full refund only once within five days after purchase by default. Non-full refunds will be provided for other refund requests.
Pay-as-you-go (postpaid): All TDSQL-C for MySQL resources can be returned directly, but there will be no refunds. The above operations can be performed in the console: either on the Cluster Management page > Terminate/Refund (tab view) or Cluster List > Operation column > More > Terminate/Refund (list view).
For the pay-as-you-go (postpaid) option, you will be charged based on your actual resource usage, and no refunds are involved. The following instructions are mainly for yearly/monthly subscribed clusters.

Self-Service Returns

After a yearly/monthly subscribed cluster is returned, it won’t be charged any more once its status changes to "Isolating" or "Isolated".
When a yearly/monthly subscribed cluster is returned, it is retained in the recycle bin for 7 days, where it cannot be accessed. To restore the cluster, go to the recycle bin and renew it.
When a yearly/monthly subscrbed cluster is terminated, its IP address will be released, and it becomes inaccessible.
Tencent Cloud has the right to reject the application for any suspected exceptional or malicious returns.
Certain resources purchased during promotions may not be eligible for return. You can check the latest information on the official website.

Five-Day Free Returns

Tencent Cloud refund policy is applicable to the TDSQL-C for MySQL product. You can return your purchased TDSQL-C for MySQL clusters within 5 (inclusive) days with no questions asked.
Each account can return one yearly/monthly subscribed TDSQL-C for MySQL instance unconditionally within five (inclusive) days after purchase by default.
For clusters with billing mode switched from pay-as-you-go to yearly/monthly subscription, the five-day free returns are not supported.
Tencent Cloud has the right to reject the application for any suspected exceptional or malicious returns.

Rules for five-day free returns

For an order eligible for 5-day free returns, the refund is the total amount paid upon purchase, including the amount of cash account, revenue account, and complimentary account.
Note:
Discounts and vouchers are not refundable.
All the refund amount will be credited into your Tencent Cloud account.

Standard Returns

If you have already returned an instance unconditionally within five days after purchase, you can also return 199 yearly/monthly subscribed instances in a self-service manner at any time in the console. Fees for consumed resources will be deducted from the refund. The remaining amount will be returned to your Tencent Cloud account by the proportion of the cash and voucher amount paid for the purchase.

Rules for standard returns

Refund = currently effective order amount + ineffective order amount - used resource value
Current orders: The amount paid for current orders, excluding discounts and vouchers.
Future orders: The amount paid for future orders, excluding vouchers.
Fees for consumed resources are calculated based on the following policies:
For the used part, if the usage has lasted at least one month as of the date of downgrade, fees will be deducted by month; otherwise, fees will be deducted in a pay-as-you-go manner.
The usage is accurate down to the second.
If the refunded amount ≤ 0, it is considered 0, and resources are deleted.
Note:
Discounts and vouchers will not be returned.
The refund will be returned to your Tencent account by the proportion of the cash and free credit paid for the purchase.

Relevant Documents



Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback