> 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/main-use-cases.md).

# Main use cases

Coridor is a **fiat bridge** for Stellar apps focused on Indonesia. These are the primary ways teams use it today.

{% stepper %}
{% step %}

## Wallet top-up and cash out

**Who:** Stellar wallets (Demo Wallet, Privy embedded wallets, custodial apps)

**Flow:** User deposits IDR via VA/QRIS/OVO → receives USDC. Or withdraws USDC → receives IDR in their bank account.

**Why Coridor:** Standard SEP-24 — no custom payment API. Home domain `sep.coridor.fun`.

**Example:** A savings app lets users top up before joining an on-chain pool.
{% endstep %}

{% step %}

## dApp / DeFi onboarding (IDR users)

**Who:** Stellar dApps that need users who only hold Rupiah

**Flow:** User on-ramps to USDC in-wallet, then swaps, stakes, or joins protocols on Stellar.

**Why Coridor:** Local payment methods Indonesians already use; USDC lands on Stellar (same network as the dApp).
{% endstep %}

{% step %}

## Community savings & ROSCA (arisan)

**Who:** Apps like pooled savings circles where members contribute USDC each cycle

**Flow:** Members **top up IDR → USDC** through Coridor, contribute on-chain, winners receive payouts; **cash out** to bank when leaving.

**Why Coridor:** IDR in via QRIS/VA; USDC compatible with pool contracts; bank payout for off-ramp.
{% endstep %}

{% step %}

## Remittance-style payout (USDC → bank)

**Who:** Apps that hold USDC on Stellar and need to pay out IDR locally

**Flow:** SEP-24 withdraw → user sends USDC with memo → Coridor triggers Xendit payout to Indonesian bank account.

**Why Coridor:** Handles fiat leg and compliance path via anchor + Xendit instead of building payout rails in-house.
{% endstep %}

{% step %}

## Wallet / anchor integration (B2B)

**Who:** Wallet teams and integrators

**Flow:** Implement SEP-10 + SEP-24 against `sep.coridor.fun`; open interactive URL; poll transaction status.

**Why Coridor:** Composable anchor on [Anchor Platform](https://developers.stellar.org/docs/platforms/anchor-platform) — no need to rebuild SEP infrastructure for IDR.

See [Integrate Coridor](/developers/integrate.md).
{% endstep %}
{% endstepper %}

## Comparison at a glance

| Use case        | Direction  | Fiat method    | On-chain                |
| --------------- | ---------- | -------------- | ----------------------- |
| Top-up          | IDR → USDC | VA, QRIS, OVO  | Anchor sends USDC       |
| Cash out        | USDC → IDR | Bank transfer  | User sends USDC + memo  |
| dApp funding    | IDR → USDC | Same as top-up | User spends USDC in app |
| B2B integration | Both       | Via widget     | SEP-24 standard         |

## Not in scope (v1)

* Cross-border remittance outside IDR ↔ USDC on Stellar
* Non-Stellar chains (bridge to Stellar first)
* Cash pickup at agent locations (bank / e-wallet only)

## Next

* [Getting started](/getting-started/start.md)
* [Deposit](/user/deposit.md) · [Withdraw](/user/withdraw.md)
* [Developer integration](/developers/wallet-integration.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://docs.coridor.fun/overview/main-use-cases.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.