> For the complete documentation index, see [llms.txt](https://apidocs.paygateway.paytota.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.paygateway.paytota.com/dashboard/registration.md).

# Registration

1\. Normally you submit your details to us via other channels of communication established or via email.

{% hint style="danger" %}
Email <sales@paytota.com>
{% endhint %}

2\. You will be required to submit the different relevant KYC documents. These documents are required by our legal to ascertain your business authenticity. Some times we are acting as intermediaries for payment service providers or fintechs and in that we create accounts as authorised.

3\. We use your details to set up the main admin account that you can use to sign in to start to explore our platform.

4\. If everything is okay with the submitted KYC, it should take two (2) business days to verify your account

5\. You can go ahead to create a business account


---

# 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://apidocs.paygateway.paytota.com/dashboard/registration.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.