> 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/receiving-money/steps.md).

# Steps

Allows your merchant account to get paid in a way that works for you using the various options we provide. You can receive funds from anyone, anywhere directly into your wallet through our payment methods that support; `mobile` `money`, and `card` 

### Steps for receiving money

1. Create your request data as a JSON
2. Set the relevant request headers;

   a) **`Content-Type`: `application/json`**\
   b) **`Accept`**: **`application/json`**

   c) [**`Authorization`**](/authorization/access-token.md#how-to-get-an-access-token)

   The access token that was generated on the authorization `API`
3. `POST` the composed data to the collections `API`.
4. Process the response returned by the `API`

   In-case the response contains a `payment_url` that is required to complete a transaction, we expect your application to redirect the customer to the payment `URL`
5. As the payment is being processed on our side, any change in payment status will be sent to the respective [`webhook URL`](/webhook.md) of the merchant 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/receiving-money/steps.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.