> For the complete documentation index, see [llms.txt](https://docs.tupayonline.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tupayonline.com/english/welcome-to-tupay-api.md).
# Welcome to Tupay API
Here you will find useful information regarding the integration with Tupay.
## Onboarding process
### 1. Sign Up.
Fill in the [**Signup form**](https://merchants.tupayonline.com/signup) for Tupay.\
We will contact you and approve your Sign Up request.
### 2. Account Creation.
As soon as we accept your request to start processing with us, you will receive an email to configure your account in our [STG environment](https://merchants-stg.tupayonline.com/login) . Activate your STG account.
### 3. Environments.
Our STG environment is a safe environment you can use to test your integration and any new features you need to test risk-free.
\
Login into our STG Tupay Panel and Fetch your API credentials by going to **Settings** > **API Access**, read our documentation and start the integration process!
### 4. Integration.
Integrate Tupay and make sure everything is working smoothly :rocket:
### 5. Go Live.
When you have completed the integration process, you will want to start processing,\
to do that, you will need an account in our **Production** environment.
\
You will see a "*Request Go Live*" button over the top right corner on the **Home** of the **STG Tupay Panel**.
\
Proceed to Request Go Live, we will receive your request, review your tests and if everything looks fine, you will receive an email to activate your account in Production :smile:
### User journey
Send all the required fields :ballot\_box\_with\_check: via API to create a frictionless payment experience for your users and avoid extra steps.
## Postman collection
---
# 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.tupayonline.com/english/welcome-to-tupay-api.md?ask=&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.
.png){kind=link}
.png)