> 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/customer-and-bank-info.md).

# Customer & Bank Info

How Coridor collects user data during deposit and withdraw flows.

## Overview

| Concern              | Coridor                                     |
| -------------------- | ------------------------------------------- |
| KYC                  | **SEP-12** on anchor (staging: auto-accept) |
| Withdraw destination | **Bank account** in interactive widget      |
| Deposit              | **IDR amount + payment method** in widget   |

Wallets do **not** need to pass customer fields in the initial SEP-24 call for staging demos.

## Withdraw — bank details (interactive form)

Collected in the Coridor widget when the user submits:

| Field               | Example      |
| ------------------- | ------------ |
| Bank name           | `BCA`        |
| Account number      | `1234567890` |
| Account holder name | `John Doe`   |

The wallet opens the interactive URL; **do not** duplicate this form in the wallet unless you have a custom integration.

## Deposit — payment method (interactive form)

| UI value                              | Rail                              |
| ------------------------------------- | --------------------------------- |
| Virtual Account (BCA/BNI/Mandiri/BRI) | Xendit VA                         |
| QRIS                                  | Xendit Payments API v3            |
| E-Wallet (OVO)                        | Mobile number + push notification |

## SEP-12 KYC

Production wallets should expect SEP-12 flows per anchor config. On **staging**, KYC is simplified / auto-accepted — focus testing on SEP-24 + payments.

## Optional: mobile number for OVO

If building a custom client (not using Coridor widget), deposit e-wallet flows need `account_mobile_number` in Xendit channel properties — the default widget collects this.


---

# 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/customer-and-bank-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.