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

# Welcome to PaySats

PaySats is an **agentic Bitcoin and stablecoin settlement app for Southeast Asia**, built on **BNB Chain**. Users and AI agents **DCA into BTC**, **collateralize BTC to borrow local stablecoins** (e.g. IDRX), and **settle directly into bank accounts**, starting with **IDR** in Indonesia, expanding to **PHP**, **VND**, **THB**, and **INR**.

Southeast Asian fiat bleeds slowly against the dollar. BTC and dollar stablecoins like USDC preserve purchasing power. PaySats is the **last-mile settlement layer** that connects on-chain value to named local accounts via **MCP** today and **x402-compatible** agent rails next.

## Three primitives

| Primitive                | Summary                                                           | Status         |
| ------------------------ | ----------------------------------------------------------------- | -------------- |
| **Agentic DCA into BTC** | Recurring / agent-driven exit from local currency into BTC on BNB | **Live**       |
| **BTC-backed borrowing** | Collateralize BTC; borrow IDR stablecoins (IDRX)                  | **Live**       |
| **Bank settlement**      | Wallet ↔ bank / e-wallet through licensed redeem partners         | **Live (IDR)** |

Full detail: [Product primitives](/introduction/primitives.md).

## Where to next

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Why PaySats</strong></td><td>SEA currency bleed, P2P risk, and the case for trusted programmatic settlement.</td><td><a href="/pages/h7Rx8jYDT61PbyDoF8pt">/pages/h7Rx8jYDT61PbyDoF8pt</a></td></tr><tr><td><strong>Product primitives</strong></td><td>DCA, borrowing, and bank settlement on BNB Chain.</td><td><a href="/pages/NBOgaUtevzSZduYvlOJp">/pages/NBOgaUtevzSZduYvlOJp</a></td></tr><tr><td><strong>Settlement quickstart</strong></td><td>Your first IDR bank settlement in five steps using the SDK.</td><td><a href="/pages/kJXKzs648TNWx0R9TS1h">/pages/kJXKzs648TNWx0R9TS1h</a></td></tr><tr><td><strong>MCP server</strong></td><td>Agent last-mile settlement: quote, list rails, create orders.</td><td><a href="/pages/34Qs1fXJV5fqN5U9vJtA">/pages/34Qs1fXJV5fqN5U9vJtA</a></td></tr></tbody></table>

## What PaySats does, in one picture

```mermaid
flowchart TB
  subgraph primitives [PaySats on BNB Chain]
    dca[Agentic DCA into BTC]
    borrow[BTC-backed borrow IDRX]
    settle[Bank settlement]
  end
  agents[AI agents MCP / x402] --> primitives
  settle --> idr[IDR live]
  settle --> sea[PHP VND THB INR next]
  dca --> borrow
  borrow --> settle
```

**Live settlement path (today):**

* **Bitcoin in:** Lightning (see [Tether Lightning rails](/integrations/tether-lightning.md)), **cbBTC** on Base, or **BTCB** on BNB Chain.
* **Stablecoin middle:** IDRX burn / redeem via licensed partners.
* **IDR out:** BCA and partner banks, or e-wallets (GoPay, OVO, Jago, …).

## Developer hub

{% hint style="success" %}
PaySats exposes **three integration surfaces** for the **settlement primitive**: HTTP `/v1`, `@paysats/sdk`, and `@paysats/mcp`. All three use the same tenant API key.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>HTTP API /v1</strong></td><td>curl, TypeScript, and SDK examples for every endpoint.</td><td><a href="/pages/if9bvLCA4SH56TUzu0ur">/pages/if9bvLCA4SH56TUzu0ur</a></td></tr><tr><td><strong>Order lifecycle</strong></td><td>All order states from <code>IDLE</code> to <code>COMPLETED</code>, with terminal-state rules.</td><td><a href="/pages/7IpIXkcXcUjeoBJ9znBg">/pages/7IpIXkcXcUjeoBJ9znBg</a></td></tr><tr><td><strong>Deposit rails</strong></td><td>Lightning, cbBTC on Base, and BTCB on BNB Chain. What each rail returns.</td><td><a href="/pages/IOmE6toQhGn0qmk0T8Pn">/pages/IOmE6toQhGn0qmk0T8Pn</a></td></tr><tr><td><strong>Payout methods</strong></td><td>Banks vs e-wallets, <code>bankCode</code>/<code>bankName</code>, and recipient format rules.</td><td><a href="/pages/kAV3jzK4JRswZs2VZt0t">/pages/kAV3jzK4JRswZs2VZt0t</a></td></tr></tbody></table>

## Current status

{% hint style="warning" %}
**Beta.** **Agentic DCA**, **BTC-backed borrowing**, and **bank settlement (IDR)** are production-ready. **QRIS ↔ IDRX** and **gift-card** flows are actively being wired. See [Supported rails](/introduction/supported-rails.md) and [Product primitives](/introduction/primitives.md).
{% endhint %}

Need access? Ping us on Telegram at [@vibcrypto](https://t.me/vibcrypto) to request a tenant API key, or email <code class="expression">space.vars.support\_email</code>.


---

# 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://doc.paysats.exchange/introduction/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.