> 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/user/faq.md).

# FAQ

## General

<details>

<summary>What is Coridor?</summary>

Coridor is a **Stellar anchor** for Indonesia: swap **IDR** (Rupiah) for **USDC** on Stellar and back, using local payments (VA, QRIS, e-wallet) via Xendit.

</details>

<details>

<summary>Is this real money / production?</summary>

Hackathon/staging runs on **Stellar testnet** + **Xendit sandbox**. Not mainnet or real IDR unless a go-live is announced.

</details>

<details>

<summary>Which wallets are supported?</summary>

Any wallet with **SEP-24** and home domain **`sep.coridor.fun`**. Easiest: [Stellar Demo Wallet](https://demo-wallet.stellar.org/).

</details>

## Deposit

<details>

<summary>Which payment methods are available?</summary>

Virtual Account (BCA, BNI, Mandiri, BRI), **QRIS**, and **OVO** (e-wallet).

</details>

<details>

<summary>Why doesn’t the QR look like Xendit’s hosted page?</summary>

Coridor uses **embedded checkout** (Payments API v3): the QR is rendered in the Coridor widget, not on Xendit’s branded page. The QRIS payload is still valid for scanning in production.

</details>

<details>

<summary>Why is there a “Simulate” button?</summary>

Only in **Xendit test mode**. Sandbox VA/QRIS cannot be paid via real banking apps. In production the button is hidden — real payment + webhook completes the flow.

</details>

<details>

<summary>What are the fees?</summary>

Default: **Rp 5,000** flat + **\~0.5%** spread on market USDC/IDR (CoinGecko).

</details>

## Withdraw

<details>

<summary>Why did my USDC balance change after withdraw?</summary>

Standard **SEP-24**: after closing the popup, the wallet prepares an **on-chain USDC payment**. You must **Approve** in the wallet — it is not a silent auto-debit.

</details>

<details>

<summary>What is the memo?</summary>

A transaction identifier so the anchor matches your USDC payment. It **must** match when you send USDC.

</details>

<details>

<summary>How long until IDR hits my bank?</summary>

After USDC is detected on-chain, Coridor triggers Xendit payout. Timing varies in sandbox; production depends on the bank.

</details>

## Developers

<details>

<summary>Where is stellar.toml?</summary>

`https://sep.coridor.fun/.well-known/stellar.toml`

See [Stellar & SEP](/developers/stellar.toml-and-sep.md).

</details>

<details>

<summary>Public rate API for the docs site?</summary>

```http
GET https://api.coridor.fun/rate?type=indicative&sell_asset=iso4217:IDR&buy_asset=stellar:USDC:GATALTGTWIOT6BUDBCZM3Q4OQ4BO2COLOAZ7IYSKPLC2PMSOPPGF5V56&sell_amount=100000
```

</details>

<details>

<summary>Do I need an API key for /rate or /health?</summary>

No — these endpoints are public on staging.

</details>

## Security

<details>

<summary>Does Coridor store my wallet seed?</summary>

No. Your wallet signs transactions. The anchor only holds a distribution account for USDC inventory.

</details>

<details>

<summary>KYC data?</summary>

Staging: simplified / auto-accept KYC. Production: follow applicable SEP-12 policy.

</details>


---

# 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.coridor.fun/user/faq.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.