Skip to main content
In request mode, a customer submits a reason and PayRequest records an effective cancellation date. A support request keeps the discussion and any proposals together. The subscription remains active pending that date unless an agreed earlier end is confirmed. In immediate mode, the customer’s confirmed cancellation ends the subscription immediately. Product settings and service restrictions determine which actions are available. See Customer self-service.

Calculate the effective date

The product can use a notice period in calendar months or days. When calendar months are configured, they take precedence over days. Calendar-month calculations keep the same day where possible and use the last valid day when needed. The effective date is the latest of:
  • The request date plus the configured notice period.
  • A later next billing date.
  • A later explicit contract end on the subscription.
For example, one calendar month from October 15 is November 15; this is not an instruction to add 30 days. Check the actual calculated date in the portal and request rather than promising an end date from the product setting alone. The default day-based notice is 30 days when no overriding setting applies. An end date can affect future billing; it does not settle or cancel invoices already issued.

Review a pending request

  1. Open the cancellation in Requests and inspect the linked subscription, reason, requested date and effective date.
  2. Check existing unpaid invoices, pending collections, paid access and any external service or domain linked to it.
  3. Reply to the customer to explain the end date and any separate invoice or service work.
  4. Use Confirm scheduled cancellation to confirm the agreed date, or prepare an eligible alternative proposal if the customer might prefer one.
Confirm scheduled cancellation does not cancel a future-dated subscription immediately. The business cannot use the former reject action to withdraw a customer’s cancellation. Only the customer can withdraw it, including through explicit acceptance of an eligible alternative.

Offer an alternative

Eligible active, single-quantity subscriptions billed by PayRequest can support these proposals: The current discount range is 1–80% for 1–12 billing periods. Product switches require compatible currency, interval and VAT basis. Provisioned services, provider-managed schedules and subscriptions with an active payment retry are excluded from these offers. Other eligibility checks can also hide unavailable options.
1

Prepare terms

Select an available offer, enter its terms and expiry, and add a message if helpful. Its expiry must precede the relevant billing, cancellation and proposed end dates.
2

Preview

Choose Preview proposal and review the dates, amounts and future consequences. Previewing does not publish or send the offer.
3

Publish

Publish proposal and notify customer makes the offer available in the portal and queues the support notification. A new published offer replaces a previous pending offer.
4

Wait for an explicit decision

The primary customer or an enabled customer administrator reviews the terms, confirms agreement and accepts or declines. The original cancellation remains until the relevant alternative is accepted.
Ignoring, declining, withdrawing or letting a proposal expire preserves the original cancellation date. Acceptance of a discount or eligible product switch withdraws the pending cancellation without adding a new minimum term. Changed subscription terms require a new preview and offer. A cheaper product is not an automatic migration for a VPS, domain, VPN or other provisioned service. Arrange external-service changes separately.

Confirm an already-agreed earlier end

If the customer already agreed directly to stop sooner, the account owner can use End immediately, enter a reason and review the previous end date and access consequences. Confirm that shutdown and any data export have been agreed, then use End now and send confirmation. This is separate from publishing a proposal for the customer to consider. It ends the native subscription and disables future billing/retries; it does not delete an external server. Existing invoices and payments remain unchanged. Review unpaid invoices and pending consolidated items first, and use the separate credit-note flow for applicable invoice corrections or refunds.

Automatic processing and confirmations

Scheduled cancellations are checked every five minutes. Provider and external-service updates may have their own processing times; do not promise an exact second of shutdown. Scheduled and immediate confirmations generate a customer email with the subscription and end date. A later status confirmation is generated when scheduled cancellation takes effect. Inspect the request’s email status if the customer has not received it: queued or provider-accepted does not prove inbox delivery. Check the final subscription status and effective date before telling a customer cancellation has completed. A missing email alone is not a reason to submit a second cancellation.

Domains, access and existing invoices

A request can initiate disabling auto-renew on a linked domain registration. Check the registrar result separately; cancellation does not itself delete or transfer the domain. If the customer later stays, review whether renewal needs to be re-enabled. Canceling a subscription or accepting an offer does not erase existing invoices, reverse a settled payment or automatically issue a refund. Agree on export and access for any external service before ending it.

Share the customer instructions

Send Cancel or pause your subscription so the customer can find their service, review the end date and understand any proposal.

Customer self-service

Configure the available customer actions.

Pausing and resuming

Manage a temporary pause separately from cancellation.