> For the complete documentation index, see [llms.txt](https://docs.payengine.co/developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payengine.co/developer-docs/getting-started-1/getting-started.md).

# 1. Creating User Accounts

You can begin interacting with your account in development mode as soon as you create it. All features are available in development mode but you can’t create live charges until you activate it. To begin offering payment solutions to your customers, you must first activate your account. 

When you're ready to get your account activation process kicked off, follow these instructions. When you first create your partner account, there will be a notice displayed prompting you to activate your account (see image below). Click on that button to get this process started.

![](https://2556322805-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MRlN2yYeruyG-6M2wZN%2F-MRp5uCP6aVj_8srTnq2%2F-MRpHxV6J6vql2UrPKU7%2FScreen%20Shot%202021-01-24%20at%208.41.20%20AM.png?alt=media\&token=8735eba3-81ed-48fe-ad59-b30c9938cb05)

This will start a wizard which will walk you through the various questions you need to answer about you and your business.


---

# 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://docs.payengine.co/developer-docs/getting-started-1/getting-started.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.