> For the complete documentation index, see [llms.txt](https://moonie.gitbook.io/mooniepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moonie.gitbook.io/mooniepay/welcome.md).

# Welcome

MooniePay empowers businesses to seamlessly accept and send payments across multiple providers—primarily in Africa and expanding globally—through a single, unified integration. Instead of integrating each mobile money operator, bank, or payment gateway individually, MooniePay provides a streamlined infrastructure that simplifies the entire process.

With MooniePay, you can offer your customers a wide range of payment options while maintaining full control, visibility, and scalability within your platform.

***

### **🚀 What You’ll Find Here**

This documentation is designed to guide you from your first API call to advanced payment workflows.

It is structured to:

* Introduce you to core concepts and architecture
* Walk you through authentication and environment setup
* Help you integrate payments and payouts step-by-step
* Provide real-world use cases and best practices
* Support you in debugging and troubleshooting efficiently

Whether you're building a simple checkout experience or a fully integrated financial system, MooniePay gives you the tools to move faster and operate reliably.

***

### 🌍 Why MooniePay?

* **Single Integration** → Access multiple payment providers
* **Local + Global Reach** → Especially optimized for African markets
* **Unified API** → Consistent request and response structure
* **Scalable Infrastructure** → Built for startups and large platforms
* **Real-time Processing** → Fast and reliable transactions

MooniePay allows you to focus on your product while we handle the complexity of payments.

***

### 🛠️ Help & Support

We aim to make your integration experience as smooth as possible, but if you ever need help, we’ve got you covered.

#### Support

For any issues related to integration, transactions, or API usage, our support team is available to assist you.

You can reach us via:

* Email support
* Live chat
* Developer support channels

***

#### Community

Join our developer community to connect with other builders and the MooniePay team.

Inside the community, you can:

* Ask questions and get real-time help
* Share your integration experience
* Learn from other developers
* Stay updated on new features and releases
* Provide feedback directly to the team

We encourage a respectful and collaborative environment for everyone.

***

### 💬 Feedback

Your feedback helps us improve MooniePay.

If you have suggestions, feature requests, or documentation improvements, feel free to share them through:

* Your dashboard feedback form
* The feedback option within this documentation

We actively review and prioritize community input to continuously improve the platform.

***

### ✨ Let’s Get Started

Ready to integrate?

Head over to the **Authentication** section to get your API keys and start making your first request.

Welcome to MooniePay — where payments are simplified, scalable, and built for the future.


---

# 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://moonie.gitbook.io/mooniepay/welcome.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.
