> 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/withdraw-payout-and-more-info.md).

# Withdraw Payout & More Info

Fiat completion for Coridor **withdraw** (USDC → IDR bank transfer).

## How withdraw completes

|                    | Coridor withdraw                  |
| ------------------ | --------------------------------- |
| User receives      | **IDR bank transfer**             |
| External ID        | Xendit payout ID (internal)       |
| User-facing status | Bank credit + **`more_info_url`** |

## When IDR is sent

After:

1. User sends USDC with correct **memo**
2. Observer confirms on-chain payment
3. coridor-server calls **Xendit payout** to the bank details from the widget

SEP-24 status progresses toward **`completed`**.

## more\_info\_url

When the wallet redirects or the user opens transaction details:

```typescript
if (transaction.status === "pending_user_transfer_complete" ||
    transaction.status === "pending_anchor" ||
    transaction.status === "completed") {
  window.open(transaction.more_info_url);
}
```

Coridor `more_info` page (production):

```
https://api.coridor.fun/sep24/transaction/more_info?token=<jwt>
```

Shows status, memo (withdraw), bank details, auto-refresh every 5 seconds.

## Deposit completion

Deposit completes when:

* IDR payment succeeds (Xendit webhook or sandbox simulate)
* Anchor sends USDC to the user

USDC appears in the wallet — no separate fiat reference step.

## external\_transaction\_id

If present on the SEP-24 transaction object, it may reference Xendit payment/payout IDs for support.

## Support debugging

```http
GET https://api.coridor.fun/health
```

Check `xendit_configured` and USDC inventory before large withdraw tests.

## Related

* [Poll status](/developers/poll-transaction-status.md)
* [User withdraw guide](/user/withdraw.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/withdraw-payout-and-more-info.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.