tencent cloud

TencentDB for PostgreSQL

Release Notes and Announcements
Release Notes
Product Announcements
Product Introduction
Overview
Features
Strengths
Scenarios
Information Security
Regions and AZs
Product Feature List
Large version lifecycle description
MSSQL Compatible Version
Billing
Billing Overview
Instance Type and Specification
Purchase Methods
Refund
Overdue Payments
Backup Space Billing
Database Audit Billing Overview
Getting Started
Creating TencentDB for PostgreSQL Instance
Connecting to TencentDB for PostgreSQL Instance
Managing TencentDB for PostgreSQL Instance
Importing Data
Migrating Data with DTS
Kernel Version Introduction
Kernel Version Overview
Kernel Version Release Notes
Viewing Kernel Version
Proprietary Kernel Features
Database Audit
Audit Service Description
Activating Audit Service
View Audit Logs
Modify audit services
Audit Performance Description
User Guide
Instance Management
Upgrading Instance
CPU Elastic Scaling
Read-Only Instance
Account Management
Database Management
Parameter Management
Log Management and Analysis
Backup and Restoration
Data Migration
Extension Management
Network Management
Access Management
Data Security
Tenant and Resource Isolation
Security Groups
Monitoring and Alarms
Tag
AI Practice
Using the Tencentdb_ai Plug-In to Call Large Models
Building Ai Applications with the Tencentdb Ai Plug-In
Combining Supabase to Quickly Build Backend Service Based on TencentDB for PostgreSQL
Use Cases
postgres_fdw Extension for Cross-database Access
Automatically Creating Partition in PostgreSQL
Searching in High Numbers of Tags Based on pg_roaringbitmap
Querying People Nearby with One SQL Statement
Configuring TencentDB for PostgreSQL as GitLab's External Data Source
Supporting Tiered Storage Based on cos_fdw Extension
Implement Read/Write Separation via pgpool
Implementing Slow SQL Analysis Using the Auto_explain Plugin
Using pglogical for Logical Replication
Using Debezium to Collect PostgreSQL Data
Set Up a Remote Disaster Recovery Environment for PostgreSQL Locally on CVM
Read-Only Instance and Read-Only Group Practical Tutorial
How to Use SCF for Scheduled Database Operations
Fix Table Bloat
Performance White Paper
Test Methods
Test Results
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Read-only Replica APIs
Backup and Recovery APIs
Parameter Management APIs
Security Group APIs
Performance Optimization APIs
Account APIs
Specification APIs
Network APIs
Data Types
Error Codes
FAQs
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us
DocumentationTencentDB for PostgreSQLBillingOverdue Payments

Overdue Payments

PDF
Focus Mode
Font Size
Last updated: 2026-02-09 11:45:09
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.

Balance Reminder

We will estimate the number of days it takes your account balance to become negative based on the usage in the past 24 hours and current balance. If it is less than five days, we will send a reminder to your Tencent Cloud account creator and all the collaborators via email and SMS.

Overdue Payment Reminder

For pay-as-you-go resources, fees are deducted on the hour. When your account balance is in negative, we will notify the Tencent Cloud account creator and all the collaborators via email and SMS.

Overdue Payment Processing

Starting from the moment your account becomes negative:
You can continue to use your database for 2 hours from the moment your account becomes negative. We will also continue to bill you for this period.
After your account has been overdue for 2 hours, your database instance will automatically shut down. We will also stop billing you for service.
After automatic shutdown:
Within 24 hours after automatic shutdown, if your account is not topped up to a positive balance, you will not be able to start your database; If your balance is positive, the billing continues, and you can start your database.
If your account remains negative for 24 hours after shutdown, the database will be repossessed, and all data will be deleted and cannot be recovered.
We will notify the Tencent Cloud account creator and all the collaborators via email and SMS when the database is repossessed.
When you do not use pay-as-you-go resources any longer, terminate them as soon as possible to avoid further fee deduction. After the database is terminated or repossessed, the data will be deleted and cannot be recovered. Since your actual resource consumption changes from time to time, some deviation may exist for the stated balance.
Previous Topic: RefundNext Topic: Backup Space Billing

Help and Support

Was this page helpful?

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

Feedback