> For the complete documentation index, see [llms.txt](https://studioworks.gitbook.io/studioworks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studioworks.gitbook.io/studioworks-docs/support/wrong-purchase-account.md).

# I purchased with the wrong account

The purchase or asset appears under a different account.

{% hint style="info" icon="bolt" %}
**Quick check:** Compare the account shown in your purchase confirmation with the account you are currently using.
{% endhint %}

## Fix it

1. Sign in to the account that was actually used for the purchase and check the delivery instructions.
2. If the asset assignment needs correction, contact StudioWorks privately with the product name and order reference.
3. Do not change your server license key on a guess: other installed assets may depend on its account ownership.

## Check the result

The delivery and account assignment are clear. Transfers depend on the platform's available options; do not assume they can be performed automatically.

[Contact StudioWorks](https://discord.gg/UmqU67rp4v). Never send passwords or secret server keys.


---

# 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://studioworks.gitbook.io/studioworks-docs/support/wrong-purchase-account.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.