> 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/supported-rails.md).

# Supported rails

Rails power all three primitives on **BNB Chain**. **Bank settlement** has the fullest API surface today; **DCA** and **BTC-backed borrowing** use the same on-chain infrastructure.

## Primitive coverage

| Primitive                | Live rails today                                            | Notes                                      |
| ------------------------ | ----------------------------------------------------------- | ------------------------------------------ |
| **Bank settlement**      | Lightning, cbBTC (Base), BTCB (BNB) → IDR banks / e-wallets | Full API + MCP                             |
| **Agentic DCA into BTC** | BTCB on BNB, MCP agent triggers                             | Recurring / agent-driven swaps into BTC    |
| **BTC-backed borrowing** | BTCB on BNB collateral → IDRX                               | Borrow against BTC collateral on BNB Chain |

## Markets

| Market      | Currency | Payout status |
| ----------- | -------- | ------------- |
| Indonesia   | IDR      | **Live**      |
| Philippines | PHP      | Planned       |
| Vietnam     | VND      | Planned       |
| Thailand    | THB      | Planned       |
| India       | INR      | Planned       |

Within each live market, banks and e-wallets are always served by `GET /v1/payout/methods`. **Do not hard-code** `bankCode` or `bankName`.

## Bitcoin in: deposit channels

| `depositChannel`      | Chain                  | Token                  | Notes                                                                                                                                         |
| --------------------- | ---------------------- | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| `lightning` (default) | Lightning Network      | BTC (sats)             | Pay the returned **BOLT11** invoice. Fastest; native invoice flow. Stack detail: [Tether Lightning rails](/integrations/tether-lightning.md). |
| `cbbtc`               | Base (chainId 8453)    | **cbBTC** (8 decimals) | Send cbBTC to the per-tenant ERC-4337 safe from `GET /v1/deposit/rails`.                                                                      |
| `btcb`                | BNB Chain (chainId 56) | **BTCB** (18 decimals) | Send BTCB to the per-tenant ERC-4337 safe from `GET /v1/deposit/rails`. Primary chain for PaySats primitives.                                 |

{% hint style="info" %}
**Coming on the deposit side:** native on-chain BTC via **Spark** (`getSingleUseDepositAddress` / `getStaticDepositAddress`), plus other wrapped BTC variants (WBTC, ZBTC). Backend wiring exists; SDK surface is being finalized.
{% endhint %}

## Local fiat out: payout methods

**Indonesia (IDR)** is live today. **PHP**, **VND**, **THB**, and **INR** are on the roadmap.

Each payout method entry:

```ts
type PayoutMethod = {
  bankCode: string;
  bankName: string;
  maxAmountTransfer?: number | string | null;
  kind: "bank" | "ewallet";
};
```

### Banks (`kind: "bank"`)

**Indonesia (live):** BCA (code `014`, most common payout target), Mandiri, BRI, BNI, CIMB Niaga, Permata, Danamon, and the rest of the Bank Indonesia member list, routed through IDRX redeem partners.

**India (planned):** HDFC, ICICI, SBI, Axis, Kotak, and the IFSC list, via INR-pegged stablecoin redeem and UPI / IMPS rails.

**Philippines, Vietnam, Thailand (planned):** local bank lists via market-specific stablecoin redeem partners.

`recipientDetails` for banks must be a **digits-only account number** (or market-specific identifier once each region launches).

### E-wallets (`kind: "ewallet"`)

**Indonesia (live, IDRX e-wallet rails):**

* **GoPay**
* **OVO**
* **DANA**
* **Jago**
* **ShopeePay**

**India (planned):** Paytm, PhonePe, Google Pay (UPI VPA routing).

**Philippines, Vietnam, Thailand (planned):** market-specific e-wallet partners.

`recipientDetails` for e-wallets must be a **mobile number** in E.164 (`+628123456789`) or local format (`08123456789`). Server-side validation returns actionable errors.

## Fees

{% hint style="warning" %}
A fixed fiat settlement fee applies for **bank** and **e-wallet** payout in Indonesia (**Rp 5,000** today). Equivalent fees will apply per market at launch. Network and swap costs are bundled into the quote locked at order creation.
{% endhint %}

## Quick reference

{% columns %}
{% column %}
**Simplest path** (first integration)

* Deposit: `lightning`
* Payout: `bank` → BCA
* Amount basis: `idrAmount`

Returns a BOLT11 invoice; payer pays; IDR lands in the named bank. Lightning detail: [Tether Lightning rails](/integrations/tether-lightning.md).
{% endcolumn %}

{% column %}
**BNB Chain path** (BTCB holders)

* Deposit: `btcb`
* Payout: `ewallet` → GoPay / OVO
* Amount basis: `idrAmount`

Returns an EVM deposit address. Pipeline swaps via IDRX and redeems to local fiat.
{% endcolumn %}
{% endcolumns %}

Next: [Product primitives](/introduction/primitives.md) · [Settlement quickstart](/getting-started/quickstart.md) · [Deposit rails](/developers/deposit-rails.md) · [Payout methods](/developers/payout-methods.md)


---

# 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/supported-rails.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.