A domain order can be blocked even when the WHMCS connector is installed correctly. Check the reseller account's current access and commercial state before changing credentials or resubmitting a paid request.
01 Separate the possible causes
| Evidence | What to investigate |
|---|---|
| Authentication rejected | API username, key, endpoint, expiry or allowed source address. |
| Account held or suspended | Reseller status and the authorised release process. |
| Operation permission denied | Credential scopes, TLD capabilities and account assignment. |
| Insufficient available funds | Wallet balance, reservations and payment posting. |
| Provider operation pending | The existing order and upstream operation, before another submission. |
02 Investigate the current order
- Record the local order or invoice ID and the connector's error or request reference.
- Confirm the configured API base is the current Domain Nexus endpoint and the username belongs to the intended reseller credential.
- Read the reseller profile or check the portal's account state. If the account is on hold, identify the reason and the party authorised to resolve it.
- Inspect any upstream operation already created for the order. Determine whether it was rejected before execution, remains pending or has completed.
- After the cause is corrected, resume the original supported workflow with its original business reference.
Common questions
Does paying a WHMCS invoice automatically release an upstream hold?
Not necessarily. Local customer billing, reseller funding and account access are different records. Confirm the relevant payment posting and release state.
Should I issue a new API key to bypass a suspension?
No. A new credential does not change the reseller account's legitimate hold. Resolve that state through the authorised account workflow.
Are existing domains deleted when an account is suspended?
A suspension is not proof of registry deletion. Check the actual domain status and continue managing renewal obligations through the permitted support process.
What should support receive?
Provide the connector version, account identifier, domain, UTC request time and redacted error or operation reference. Never include the full API key, a transfer code or unrelated customer records.
After recovery, test a read-only request and review the original order outcome before reopening unattended order processing.
Related articles
- Diagnose API permission errors using the profile and capability endpoints
- Reconcile wallet balances, ledger entries and reserved holds
- Follow a domain operation through pending, failed and manual-review states
- Configure WHMCS domain synchronisation and investigate pending registrations
- Collect registry-specific fields in a WHMCS reseller order form