What Happens After a Hosting Order Is Paid?

You have just received a payment notification. The client paid their invoice. But what actually happens on your backend between that payment and the client receiving their welcome email? If you are a reseller, understanding this chain helps you troubleshoot delays and set correct expectations. This article walks through each automated step in order, with approximate timings you can expect from a well-configured hosting automation platform.

What happens immediately after an invoice is marked paid?

The moment an invoice is settled—whether by manual mark or automatic payment gateway callback—the billing system triggers a chain of events. First, the invoice status changes to Paid and the payment is recorded. Next, the system checks if the invoice is linked to any pending orders. If so, those orders are moved from Pending to Active. This entire process usually completes within seconds, though gateway callbacks can introduce a short delay.

How does the provisioning queue work?

Once an order is marked Active, it enters the provisioning queue. The queue is a list of tasks that the automation engine processes sequentially or in parallel, depending on your configuration. Each task represents a step like creating a hosting account, setting up DNS, or sending an email. The queue prevents race conditions and ensures that dependent tasks run in the correct order.

For example, the system will not attempt to install an SSL certificate before the web server virtual host is created. The queue also allows for retries: if a task fails (e.g., due to a temporary API timeout), it can be re-attempted automatically after a short backoff.

Step 1: Control panel account creation (0–30 seconds)

The first provisioning task is typically creating the hosting account on your control panel—cPanel, Plesk, or Virtualmin for shared hosting; or a VPS management panel like Virtualizor or VirtFusion for virtual servers. The automation platform sends an API call to the control panel with the account details: domain, username, password, and package limits. The control panel then creates the account and returns a success or failure response.

If the control panel is slow or unresponsive, the task may time out. Most systems will retry once or twice before flagging the order for manual review. You can usually see the status of each task in the order's admin view.

Step 2: DNS zone creation (30–60 seconds)

After the control panel account exists, the system creates a DNS zone for the domain. This involves adding records: an A record pointing to the server's IP, a CNAME for www, MX records for email, and possibly TXT records for SPF and DKIM. If the domain is registered through your platform (or via a domain reseller API), the nameservers are also updated to point to your DNS infrastructure.

DNS propagation is not instant. Even after the zone is created, it may take minutes to hours for the changes to be visible worldwide, depending on TTL settings. The automation itself is quick—typically under 30 seconds—but the real-world effect is delayed.

Step 3: SSL certificate issuance (1–5 minutes)

With the DNS zone in place, the system can request an SSL certificate. For free certificates like Let's Encrypt, this involves an ACME challenge—usually a DNS-01 or HTTP-01 validation. The automation platform handles the challenge automatically: it adds a temporary DNS record or places a file on the web server, then tells the certificate authority to verify.

Issuance can take anywhere from a few seconds to a couple of minutes. If validation fails (e.g., because DNS hasn't propagated yet), the system will retry. Some platforms schedule a retry after a set interval, while others require manual intervention. A well-designed system will keep trying until the certificate is issued, then install it on the web server.

Step 4: Welcome email dispatch (immediately after SSL)

Once the account is fully functional and secured, the system sends a welcome email to the client. This email typically contains login credentials, nameserver information, and links to your client area and support resources. The email is often templated and can be customized with your branding.

Some platforms send the welcome email earlier—right after account creation—but sending it after SSL ensures the client's first visit to their control panel is secure. The dispatch itself is near-instant, though email delivery can be delayed by spam filters or SMTP issues.

Step 5: Monitoring agent activation (1–2 minutes)

Finally, the system activates monitoring for the new account. This could be a simple uptime check via HTTP, or a full monitoring agent installed on the server. The agent reports back to your monitoring dashboard, alerting you if the site goes down or resource usage spikes.

Monitoring activation is often overlooked but critical for proactive support. Without it, you might not know a client's site is offline until they complain.

What if something fails?

Failures happen. A control panel API might be down, DNS might not propagate in time, or an SSL challenge might fail. Good automation platforms log each step and provide retry mechanisms. You should be able to see which task failed and why, then either fix the issue and retry, or manually complete the step.

For resellers, this means you can reassure clients with accurate information: "Your account is being set up now; SSL will be active within a few minutes." You can also set up notifications for failed provisioning tasks so you can act quickly.

How Teculiar fits in

Teculiar is a platform that hosting, domain, and VPS resellers use to automate storefront, billing, provisioning, and support. It handles the entire chain described above out of the box, with a public API and embeddable widgets for customization. If you want to see how it can streamline your order fulfillment, check our pricing page.

What to do next

• Review your current automation logs to identify bottlenecks in your provisioning chain.
• Set up alerts for failed provisioning tasks so you can intervene before clients notice.
• Test the full order-to-active cycle with a test order to measure timings and spot issues.
• If you are not yet automated, explore a platform like Teculiar to eliminate manual steps.

Start by auditing your current process—then decide where automation can save you the most time.