tencent cloud

Data Lake Compute

Release Notes
Product Introduction
Overview
Strengths
Use Cases
Purchase Guide
Billing Overview
Refund
Payment Overdue
Configuration Adjustment Fees
Getting Started
Complete Process for New User Activation
DLC Data Import Guide
Quick Start with Data Analytics in Data Lake Compute
Quick Start with Permission Management in Data Lake Compute
Quick Start with Partition Table
Enabling Data Optimization
Cross-Source Analysis of EMR Hive Data
Standard Engine Configuration Guide
Configuring Data Access Policy
Operation Guide
Console Operation Introduction
Development Guide
Runtime Environment
SparkJar Job Development Guide
PySpark Job Development Guide
Query Performance Optimization Guide
UDF Function Development Guide
System Restraints
Client Access
JDBC Access
TDLC Command Line Interface Tool Access
Third-party Software Linkage
Python Access
Practical Tutorial
Accessing DLC Data with Power BI
Table Creation Practice
Using Apache Airflow to Schedule DLC Engine to Submit Tasks
Direct Query of DLC Internal Storage with StarRocks
Spark cost optimization practice
DATA + AI
Using DLC to Analyze CLS Logs
Using Role SSO to Access DLC
Resource-Level Authentication Guide
Implementing Tencent Cloud TCHouse-D Read and Write Operations in DLC
DLC Native Table
SQL Statement
SuperSQL Statement
Overview of Standard Spark Statement
Overview of Standard Presto Statement
Reserved Words
API Documentation
History
Introduction
API Category
Making API Requests
Data Table APIs
Task APIs
Metadata APIs
Service Configuration APIs
Permission Management APIs
Database APIs
Data Source Connection APIs
Data Optimization APIs
Data Engine APIs
Resource Group for the Standard Engine APIs
Data Types
Error Codes
General Reference
Error Codes
Quotas and limits
Operation Guide on Connecting Third-Party Software to DLC
FAQs
FAQs on Permissions
FAQs on Engines
FAQs on Features
FAQs on Spark Jobs
DLC Policy
Privacy Policy
Data Privacy And Security Agreement
Service Level Agreement
Contact Us

Refund

PDF
Focus Mode
Font Size
Last updated: 2025-08-05 14:21:50
Note
Self-service return is supported only for monthly subscribed private data engines. You don't need to return pay-as-you-go engines, as you can delete or suspend them to stop billing. Public engines won't incur fees when they are idle, so there is no need to return them.

Self-service return

Once returned, a data engine will be isolated. During the isolation period, it will be unavailable, with the data retained though.
To recover an isolated data engine, go to the Billing Center > Renewal Management page in the Tencent Cloud console, select Data Lake Compute, and renew it.
You cannot return the data engine again within 30 minutes after you renew and recover it from isolation.
The isolation period is fifteen days. After it elapses, the system will terminate the data engine permanently.
The system will notify your Tencent Cloud account creator, global resource collaborators, and financial collaborators by email and SMS when your data engine is terminated.

Refund rules

Refund amount = Currently effective order amount + Ineffective order amount - Used resource value
Parameter
Description
Currently effective order amount
The amount paid for the currently effective order, excluding discounts and vouchers.
Ineffective order amount
The amount paid for the order that will take effect in the future, excluding vouchers.
Used resource value
It is calculated as follows:
If the cluster has been used for one month as of the date of return, 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 refund is less than or equal to 0, it will be calculated as 0, and resources will be returned.
Note
Discounts and vouchers are not refundable.
The refund amount will be refunded to your account at the ratio of cash and free credit paid upon purchase.

Help and Support

Was this page helpful?

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

Feedback