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

# What is Coridor

Coridor is a **Stellar anchor** for Indonesia. It lets users and apps move value between **IDR** (Indonesian Rupiah) and **USDC** on Stellar using familiar local payment rails, Virtual Account, QRIS, and E-wallet powered by **Xendit**.

Wallets and apps connect through standard Stellar protocols (**SEP-10**, **SEP-24**, **SEP-38**). There is no proprietary Coridor SDK.

## The problem

Indonesia runs on local fiat — bank transfers, QRIS, and e-wallets. Most Stellar wallets need a way for users to **cash in** (IDR → USDC) and **cash out** (USDC → IDR) without leaving the apps they already use.

Building that from scratch means SEP infrastructure, KYC flows, payment partners, rate logic, and on-chain settlement. Coridor packages that as a **composable anchor** any SEP-24 wallet can plug into.

## What Coridor provides

| Layer              | What you get                                                      |
| ------------------ | ----------------------------------------------------------------- |
| **Anchor (SEP)**   | Auth, deposit/withdraw, KYC, quotes at `sep.coridor.fun`          |
| **Interactive UI** | Payment widget at `api.coridor.fun` (VA, QRIS, OVO, bank form)    |
| **Fiat rails**     | Xendit for IDR collection and bank payout                         |
| **On-chain**       | USDC delivery and inventory on Stellar testnet (staging)          |
| **Rates**          | Live USDC/IDR from market data + configurable spread and flat fee |

## Who it is for

* **End users** — top up or cash out through a Stellar wallet (e.g. Demo Wallet, embedded wallets like Privy)
* **Wallet teams** — add Indonesia IDR on/off-ramp via SEP-24
* **App builders** — embed fiat rails in dApps, savings products, or remittance flows on Stellar

## Current status

|             | Staging (today)                                 |
| ----------- | ----------------------------------------------- |
| Network     | Stellar **testnet**                             |
| Fiat        | Xendit **sandbox** (Simulate for VA/QRIS demos) |
| Home domain | `sep.coridor.fun`                               |
| Asset       | USDC (`GATALTGT...` on testnet)                 |

Not mainnet or live IDR unless a production go-live is announced.

## Next

* [How Coridor works](/overview/how-coridor-works.md)
* [Main use cases](/overview/main-use-cases.md)
* [Architecture](/overview/architecture.md)
* [Getting started](/getting-started/start.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coridor.fun/overview/what-is-coridor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.