Skip to content

Knowledgebase

Investigate a paid WHMCS order that did not create hosting

whmcs, resellers

When a paid hosting order does not produce a working account, determine which part of the process failed before running Create again. Payment receipt, order review, the service status and the remote account are separate records that need to agree.

01 Find the failed step

  1. Open the order and its invoice. Confirm the actual transaction and paid balance rather than relying on a customer's receipt screenshot.
  2. Open the related service. Record its product, server, username, domain and status.
  3. Check the product's Module Settings and automatic setup timing. A product configured for manual acceptance will not necessarily provision immediately after payment.
  4. Inspect Module Queue and the activity or module log for the attempted action. Record the complete error privately.
  5. Check the assigned remote server for the account or partially created resources before retrying.

02 Correct the cause

If no module call occurred, verify the intended setup trigger and whether an administrator still needs to accept the order. If the call was rejected, compare the package name with the server's exact package or plan name. Check module credentials, permissions, network access and whether the target server has capacity for another account.

If the request timed out, ask the server administrator to inspect the remote result. An existing account may need to be linked or completed rather than created again. Do not change the service to Active merely to remove an error unless the actual service is ready and its record has been reconciled.

How do I retry provisioning without creating a duplicate account?

Retry the specific failed action after its cause is fixed. Confirm that the account exists with the correct owner, domain and resource limits, then test the expected customer access. Check welcome-email delivery separately because successful provisioning does not prove the message was received.

Record the resolution in the client or service notes. If escalation is needed, provide the WHMCS version, module, action time, redacted error and remote account state. Exclude passwords, access tokens and complete request dumps containing customer data.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support