> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/premium/managing-your-subscription.md).

# Managing your subscription

Viewing, cancelling, and transferring your subscription.

There are two places to manage subscriptions. Per server, on that server's Premium page. Per user, on your account-wide subscription list.

## Per-server management

Open the dashboard for the server, then go to **Premium** in the sidebar.

You can:

* See the current subscription status.
* See the next renewal date.
* Cancel the subscription.
* Transfer the subscription to another server.

### Cancelling

Click **Cancel Subscription** and confirm in the pop-up. You keep premium access until the end of your current billing period.

#### Who can cancel

The user who started the subscription can cancel it, as can the server owner and anyone with the Manage Premium dashboard permission. If you are not allowed to cancel a given subscription, the dashboard shows a clear message.

## Per-user management

Visit [ticketking.xyz/user/subscriptions](https://ticketking.xyz/user/subscriptions) to see every subscription you have started across all your servers in one place. Each row shows the linked server, the status, the renewal date, a Cancel button, and a Transfer button. This is handy if you manage more than one subscription.

## Transferring premium between servers

You can move a subscription to another server from either place:

* **The server's Premium page.** Open **Premium** on the source server and click **Transfer premium to another server**.
* **Your subscriptions page.** Visit [ticketking.xyz/user/subscriptions](https://ticketking.xyz/user/subscriptions) and click **Transfer** next to the server the subscription is on.

Then pick the target server and confirm. All of the premium time left on the source server moves with the subscription, and future renewals add their time to the target server.

The target server must not already have an active subscription, and you must be an administrator of it. On the source server you need permission to manage premium. After a transfer there is a 24-hour cooldown before you can transfer again.

### If the server was deleted or the bot was removed

A server's Premium page only opens while Ticket King is in that server. If the server was deleted, or the bot was removed from it, transfer from your subscriptions page instead. The person paying for the subscription can move it from there even though nobody can manage the old server any more.

## Renewals

Your subscription renews automatically at the end of each billing period. You do not have to do anything. If a renewal payment cannot be collected, for example because a card expired, you are notified by email, and premium ends at the existing expiry if the payment still cannot be taken.

## Removing the bot does not cancel your subscription

{% hint style="warning" %}
Removing Ticket King from your Discord server does **not** cancel your subscription. Billing continues until you cancel on the dashboard. You can re-add the bot at any time and your subscription continues, or move it to another server from your [subscriptions page](https://ticketking.xyz/user/subscriptions).
{% endhint %}

## Related

{% content-ref url="/pages/6CWAb1CzYGaZh9FJZcaW" %}
[Subscribing](https://ticketking.xyz/docs/premium/subscribing.md)
{% endcontent-ref %}

{% content-ref url="/pages/6tX1aY5JZnlchmBE7ReF" %}
[What happens if a server is no longer premium](https://ticketking.xyz/docs/premium/no-longer-premium.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ticketking.xyz/docs/premium/managing-your-subscription.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
