> 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/developers/wallet-integration.md).

# Wallet Integration

For wallet teams connecting to Coridor via Stellar anchor standards (SEP-10, SEP-24).

## Quick start

Coridor uses standard Stellar anchor flows: SEP-10 auth, SEP-24 interactive UI, poll transaction status, and on-chain USDC. Fiat is settled in **IDR** via bank transfer, QRIS, or e-wallet (Xendit).

**Start here:** [Integrate Coridor](/developers/integrate.md)

## Step-by-step guides

| Step | Doc                                                                          |
| ---- | ---------------------------------------------------------------------------- |
| 1    | [Integrate overview](/developers/integrate.md)                               |
| 2    | [Acquire USDC & XLM](/developers/acquire-usdc-and-xlm.md)                    |
| 3    | [Authenticate (SEP-10)](/developers/authenticate-sep-10.md)                  |
| 4    | [Initiate transaction (SEP-24)](/developers/initiate-transaction-sep-24.md)  |
| 5    | [Customer & bank info](/developers/customer-and-bank-info.md)                |
| 6    | [Close interactive flow](/developers/close-interactive-flow.md)              |
| 7    | [Send / receive USDC](/developers/send-receive-usdc.md)                      |
| 8    | [Poll transaction status](/developers/poll-transaction-status.md)            |
| 9    | [Withdraw payout & more\_info](/developers/withdraw-payout-and-more-info.md) |

## Architecture

```
Wallet                    Anchor Platform              coridor-server
  │                              │                            │
  ├── SEP-10 auth ──────────────►│                            │
  ├── POST /sep24/transactions ─►│                            │
  │◄── interactive URL ──────────┤                            │
  ├── open popup ─────────────────────────────────────────────►│ widget
  │                              │◄── callbacks / events ───────┤
  │◄── status updates ───────────┤                            │
```

The wallet does **not** call `POST /sep24/interactive/submit` — the user completes that in the browser popup.

## Reference

| Resource           | Production                                                  |
| ------------------ | ----------------------------------------------------------- |
| Home domain        | `sep.coridor.fun`                                           |
| stellar.toml & SEP | [stellar.md](/developers/stellar.toml-and-sep.md)           |
| HTTP API           | [api.md](/developers/http-api.md)                           |
| User flows         | [deposit](/user/deposit.md) · [withdraw](/user/withdraw.md) |

## Local development

| Service        | URL                     |
| -------------- | ----------------------- |
| SEP / TOML     | `http://localhost:8082` |
| Platform API   | `http://localhost:8086` |
| coridor-server | `http://localhost:8091` |

Run `./ap_start.sh` — see [README.md](https://github.com/demigohu/coridor/blob/main/README.md) and [DEPLOY.md](https://github.com/demigohu/coridor/blob/main/DEPLOY.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/developers/wallet-integration.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.