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

# Getting Started

- [Registration](https://developer.dusupay.com/getting-started/registration.md): Any entity interested in the DusuPay  API needs to register and fulfil the compliance/KYC requirements before they are granted access to the platform.
- [Error Handling](https://developer.dusupay.com/getting-started/error-handling.md): The DusuPay API uses HTTP status codes to indicate the success or failure of the API requests. The section describes the summary of these codes and what they mean in our context.
- [Authentication](https://developer.dusupay.com/getting-started/authentication.md): The DusuPay API uses a key pair (Public and Secret Keys) for authentication. To make an authenticated request to our API, you need to pass custom headers as described in this section.
- [Merchant Account Credentials](https://developer.dusupay.com/getting-started/merchant-account-credentials.md): For every approved merchant account, a set of credentials is automatically generated and stored on the record. This section describes how the merchant can manage credentials after the account creation
- [Generate Secret Key](https://developer.dusupay.com/getting-started/merchant-account-credentials/generate-secret-key.md): The section below describes (with screenshots) how to generate and store a new secret key. The process assumes that you're already logged in to the merchant dashboard.
- [Regenerate Security Keys](https://developer.dusupay.com/getting-started/merchant-account-credentials/regenerate-security-keys.md): The section below describes (with screenshots) how to generate a new set of security keys. The process assumes that you're already logged in to the merchant dashboard.
- [Supported Countries/Regions](https://developer.dusupay.com/getting-started/supported-countries-regions.md): The DusuPay platform supports a wide variety of payment methods, transaction types and currencies across a number of countries or regions. Merchant accounts will be enabled for only what they request.
- [Transaction Limits](https://developer.dusupay.com/getting-started/transaction-limits.md): For some of the transaction currencies that DusuPay supports, there are limits that control what a single transaction account is able to do per transaction and in a 24hr period.
- [Sandbox Test Accounts](https://developer.dusupay.com/getting-started/sandbox-test-accounts.md): The table below describes the test account numbers that can be used for tests on the sandbox to simulate transactions. Two scenarios (success and failure) can be simulated based on the account number.
- [DusuPay Public Keys](https://developer.dusupay.com/getting-started/dusupay-public-keys.md): This section shares the two public keys used by DusuPay for the two environments (Sandbox and Production). The keys can be copied and stored as files to later be used in transaction processing.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.dusupay.com/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.