Skip to content

Knowledgebase

Reconcile a HostBill renewal that remains pending upstream

domain-nexus, hostbill

A HostBill renewal remains unconfirmed when Domain Nexus has accepted the request but the upstream provider has not completed it. The connector deliberately avoids extending the local term at that point. Preserve the original request context while checking the provider outcome.

01 Follow the pending renewal

  1. Record the HostBill domain ID, original expiry date, requested renewal term and displayed upstream operation reference.
  2. Read that operation in the reseller portal or through the API. Check whether it is pending, completed or failed with a specific provider reason.
  3. Confirm that upstream processing and HostBill's scheduled environment are operating, including access to the API-key environment variable.
  4. When the original operation has completed, retry the same HostBill renewal workflow with its original domain, term and pre-renewal expiry context.
  5. Confirm the connector's success and the updated expiry, then run normal domain synchronisation and reconcile the customer invoice.

02 Preserve the renewal identity

The connector derives its request identity from the module, operation, domain, term and a HostBill anchor. For renewal, that anchor includes the stored expiry date. Changing the expiry or order context before recovering the same billed renewal can create a different request identity.

If synchronisation has already updated the local expiry while the original billing workflow is still unresolved, investigate the completed upstream operation before pressing Renew again. Do not turn that updated expiry into an unintended additional renewal.

Common questions

Does accepted mean the domain was renewed?

No. The connector reports pending work and leaves the term unextended until it sees a completed result. Verify the actual expiry after completion.

Can I just create another renewal order?

First reconcile the original operation. A new order can represent another chargeable term, even when your intention was only to recover a timeout.

What if the provider returned a final failure?

Read the reason and correct the applicable issue, such as funds, status or eligibility. A permanent failure and an unknown outcome require different recovery decisions.

Why is HostBill still pending after upstream success?

Check the saved request context, worker credentials, domain assignment and synchronisation result. Share the original and current expiry dates and operation ID with support, without the API key.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution