Using the product

Cancellations and completed provider termination

Separate customer requests, financial cancellation and actual remote service/domain completion.

Platform
Laravel / PHP
Laravel
13
PHP
8.4
Database
Dedicated MySQL-compatible production database

Customer request versus completion

A customer can request cancellation of an eligible service under services.manage; domain cancellation/renewal preferences follow their own account permissions and matching billing service. A request stops eligible future renewal work and creates staff review. It does not prove that hosting data was deleted, a domain registration was cancelled at its registry or an external subscription was stopped.

Unpaid order or invoice

Eligible unpaid orders/invoices can be cancelled through their explicit guarded action. The application checks pending checkout/offline evidence, delivery, payment history, associated orders/services and immutable accounting state. A browser closing checkout is not evidence that a provider page can no longer receive funds. Reconcile any uncertain attempt before cancelling or restarting payment.

Issued historical documents and completed receipts remain auditable. Cancellation does not erase a payment; record any externally completed refund using the payment ledger's explicit refund workflow.

Staff completion

Open the exact service/domain and review its saved provider mapping, customer and seller. Use supported provider actions or record independently completed external work through the protected completion controls. A completed-cancellation record must describe actual reviewed provider evidence; it is not a shortcut for an unavailable API. Domain nameserver/lock changes do not cancel registry ownership.

Automated termination

See lifecycle automation for the separately enabled irreversible hosting action. Product-licence expiry is not a destructive cancellation mechanism and must not delete a customer's running business data.

Diagnose a refusal

Read the exact hold instead of editing records directly. An invoice may contain another order, a different service period or a pending external payment. A domain may be linked to another domain's billing service. Preserve original invoice, service and provider-submission evidence while resolving the mismatch. Never clear history to make a cancellation screen accept an unsafe action.

← All EmailaBiller guidesGet help →

Need help with EmailaBiller?

Tell us the product version and what you are trying to do. Keep passwords and private keys out of your message.

Contact Emaila