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

# Introduction

MakaPay is a cross-chain payment infrastructure that enables merchants to accept cryptocurrency payments on multiple blockchains while managing gas fees from a single balance.

## Table of Contents

* [Getting Started](/getting-started/getting-started.md) - Quick setup guide
* [Merchant Guide](/guides/merchant-guide.md) - Complete merchant documentation
* [Gas Tank](/guides/gas-tank.md) - Unified gas management system
* [Fee Structure](/guides/fee-structure.md) - Understanding fees and pricing
* [API Reference](/developers/api-reference.md) - Developer API documentation
* [Technical Architecture](/developers/technical-architecture.md) - Smart contracts & cross-chain recovery

***

## Why MakaPay?

### The Problem

Accepting crypto payments across multiple blockchains is expensive and complex:

* **Gas Management Nightmare**: Each blockchain requires its own native token for gas (ETH, MATIC, BNB)
* **Idle Capital**: Merchants must maintain gas balances on every chain they support
* **Cost**: Managing gas across 4+ chains can cost \~$95/month in idle capital and gas fees
* **Complexity**: Different wallets, different tokens, different processes per chain

### The Solution

MakaPay introduces a **unified gas management system**:

* **Single Gas Balance**: Deposit USDT once to your Gas Tank on MakaChain
* **Multi-Chain Acceptance**: Accept payments on Ethereum, Polygon, BSC, and more
* **Reduced Costs**: Cut gas management costs to \~$30/month
* **Zero Complexity**: No need to manage native tokens on payment chains

***

## How It Works

```
┌─────────────────────────────────────────┐
│        MakaChain (Gas Hub)              │
│   Your Gas Tank Balance (USDT)          │
└─────────────────────────────────────────┘
              ↓           ↓           ↓
    ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
    │  Ethereum   │ │   Polygon   │ │     BSC     │
    │  Payments   │ │  Payments   │ │  Payments   │
    └─────────────┘ └─────────────┘ └─────────────┘
```

1. **Merchant creates a payment link** specifying amount, token, and network
2. **Customer pays** to a deterministic smart contract address
3. **MakaPay settles** the payment, deducting gas from your Gas Tank
4. **Merchant receives** the full payment amount

***

## Supported Networks

### Mainnet

| Network         | Chain ID | Tokens               |
| --------------- | -------- | -------------------- |
| Ethereum        | 1        | USDT, USDC           |
| Polygon         | 137      | USDT, USDC           |
| BNB Smart Chain | 56       | USDT, USDC, XRP, TRX |
| MakaChain       | 777178   | USDT                 |

### Testnet

| Network           | Chain ID | Tokens     |
| ----------------- | -------- | ---------- |
| Sepolia           | 11155111 | USDT, USDC |
| MakaChain Testnet | 777177   | USDT, USDC |

***

## Quick Links

* **Dashboard**: <https://app.makapay.io/dashboard>
* **API Base URL**: `https://app.makapay.io/api`
* **MakaChain Explorer**: <https://makascan.io>

***

## Support

For technical support or questions, contact us through the dashboard or open an issue in this repository.


---

# 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://docs.makapay.io/readme.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.