tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary

Refund

PDF
Focus Mode
Font Size
Last updated: 2026-03-20 16:27:40
Yearly/monthly subscription (prepaid): You can return TencentDB for MySQL instances and request a refund (non-full).
Pay-as-you-go (postpaid): After a user apply for a return for TencentDB for MySQL, resources will be withdrawn. As billing is based on your actual resource usage, this process does not involve a refund request.
You can return yearly/monthly subscribed and pay-as-you-go instances in the instance list in the TencentDB for MySQL console.
Note:
If a terminated or returned yearly/monthly subscription instance is restored from the recycle bin, it cannot be terminated or returned again within 30 minutes. If you need to terminate or return the instance, perform the operation 30 minutes after it has been restored.

Returning Instances

When a yearly/monthly subscription instance is returned and its status has changed to Isolating, it will no longer generate fees.
After a yearly/monthly subscribed instance is terminated, its IP resources will be released simultaneously, and the instances cannot be accessed. If the instance has read-only or disaster recovery instances:
Read-only instances will be terminated at the same time.
Disaster recovery instances will disconnect their sync connections and be promoted to source instances automatically.
When a yearly/monthly subscribed instance is returned, it is retained in the recycle bin for 7 days, where it cannot be accessed. To restore the instance, go to the recycle bin and renew it.
Upon a pay-as-you-go instance is returned, it is transferred to the cloud database recycle bin, where it is retained for 24 hours. During this period, the instance is inaccessible. If you want to restore the instance, you can initiate a power-on recovery in the recycle bin.
Tencent Cloud has the right to reject any suspected abnormal or malicious application for return.
Certain resources purchased during promotions may not be eligible for return. You can check the latest information on the official website.

Standard Returns

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.

Standard return policies

Refund amount = Current Orders + Future Orders - Consumed Resources Fees
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.

Instructions on Canceling Renewal Orders

TencentDB for MySQL supports manual or automatic renewal for prepaid yearly/monthly subscription instances. After an instance is renewed, you can cancel the renewal order that does not take effect.
Note:
Canceling the renewal order shortens the expiration time. You can only cancel renewal orders that do not take effect, while effective renewal orders cannot be canceled.
If a configuration adjustment is performed after renewal, the renewal order before the adjustment cannot be canceled.

Refund Amount and Methods

Refund amount = Actual order payment amount
The amount actually paid for an order (cash/free credit/cash vouchers) can be fully refunded, while promo vouchers/discounts cannot be returned.
For more information on how to return instances in the console, see Terminating Instance.
To cancel a renewal order in the console, see Self-Service Cancellation of Renewal Order Process.

Help and Support

Was this page helpful?

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

Feedback