> 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/reference/changelog.md).

# Changelog

Notable public changes to the **PaySats API (`/v1`)**, **`@paysats/sdk`**, and **`@paysats/mcp`**. Internal infra changes are omitted unless they affect integrators.

{% hint style="info" %}
Versions follow the npm packages. Breaking changes bump the major. API `/v1` endpoints are additive; if we need to break wire compatibility, it ships as `/v2`.
{% endhint %}

{% updates format="full" %}
{% update date="2026-06-11" %}

## Docs: welcome.md homepage

* Replaced `docs/README.md` with `docs/welcome.md` as GitBook homepage (`Welcome to PaySats` first in nav).
* Renamed `developers/README.md` to `developers/overview.md`.
* Added project GitBook skill at `.cursor/skills/gitbook/SKILL.md`.
  {% endupdate %}

{% update date="2026-06-11" %}

## Docs reframe: SEA agentic settlement

* Repositioned PaySats from Lightning off-ramp-only to **three BNB Chain primitives**: agentic DCA into BTC, BTC-backed borrowing, and **bank settlement** (IDR live).
* Added [Product primitives](/introduction/primitives.md) and [Tether Lightning rails](/integrations/tether-lightning.md) integration stub; moved Lightning / Boltz / TWDK detail out of intro pages.
* Updated welcome, Why PaySats, How it works, and Supported rails for Southeast Asia expansion (**PHP**, **VND**, **THB**, **INR** alongside live **IDR**).
* Renamed quickstart to **Settlement quickstart**; refreshed MCP and developer hub copy for agent last-mile settlement.
  {% endupdate %}

{% update date="2025-04-22" %}

## Documentation launch

* Published this GitBook with product overview, SDK / MCP / HTTP references, order-lifecycle guide, deposit-rails and payout-methods pages, and a worked end-to-end example.
* Added **"Why PaySats"** covering P2P scam exposure, bank-account freezes, and manual-exchange pain as motivation.
* Architecture page is intentionally locked at a high level; deeper internals will ship incrementally.
  {% endupdate %}

{% update date="2025-04-22" %}

## `@paysats/mcp` public

* MCP server with seven tools: `get_btc_idr_quote`, `list_payout_methods`, `get_deposit_rails`, `get_platform_stats`, `create_offramp_order`, `get_offramp_order`, `list_offramp_orders`.
* Two transports: `stdio` (Cursor / Claude Desktop) and `http` (remote MCP for Claude web / mobile).
* Three ways to run: self-host stdio, one-click Railway, Docker. Bearer-token auth required on every HTTP deploy.
  {% endupdate %}

{% update date="2025-04-22" %}

## `@paysats/sdk` public

* Typed Node client covering every `/v1` endpoint.
* Terminal-state helper `waitForOrder` with `pollMs`, `timeoutMs`, `onUpdate`, and `AbortSignal` support.
* Structured errors via `PaysatsApiError` (`status`, `body`).
  {% endupdate %}

{% update date="2025-04-01" %}

## Wrapped-BTC deposit rails

* Added `cbbtc` (Base) and `btcb` (BNB Chain) as `depositChannel` values.
* `POST /v1/offramp/orders` returns `deposit` (EVM instructions) instead of `bolt11` for these channels.
* Per-tenant ERC-4337 safe addresses exposed via `GET /v1/deposit/rails`.
  {% endupdate %}

{% update date="2025-03-01" %}

## `/v1` API: tenant-scoped

* Launched `/v1/quote/btc-idr`, `/v1/payout/methods`, `/v1/deposit/rails`, `/v1/platform/stats`, and the off-ramp order endpoints.
* All endpoints gated by tenant API keys (`x-api-key` or `Authorization: Bearer`).
  {% endupdate %}
  {% endupdates %}

## Coming soon

* **Spark deposit addresses** surfaced in the SDK for native on-chain BTC.
* **Webhooks** for push notifications on order state changes (reducing the need for `waitForOrder` polling).
* **QRIS ⇄ IDRX** full round-trip settlement.
* **Gift cards and e-vouchers** via the custom P2P merchant network.
* **Multi-tenant OAuth on the MCP edge** (today every MCP HTTP deployment is single-tenant, keyed by env var).

Have a request or want early access? Ping us on Telegram at [@vibcrypto](https://t.me/vibcrypto) 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/reference/changelog.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.