> For the complete documentation index, see [llms.txt](https://docs.dutchmanbridge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dutchmanbridge.com/get-started/going-live.md).

# Going live

* **KYB approved.** You received `partner.approved` (or the console shows *Approved*). Do not put real customers through until it is.
* **API key server-side only.** No key in front-end bundles, mobile apps, or logs. Rotate on any suspicion.
* **Webhook verified.** `PUT /webhook` came back with `test.delivered: true`, your handler checks the signature and the timestamp tolerance, and you answer `2xx` before doing the work.
* **Idempotent by webhook `id`.** Retries and replays reuse the same `id`; dedupe on it and `2xx` duplicates without acting.
* **`REVIEW` is handled.** A Tier 1 submission that returns `REVIEW` is not a failure. Show the customer a pending state and act on `kyc.status_updated`. Handle `REJECTED` (show `reason`) and `kyc.reverification_requested` too.
* **Quotes expire.** Execute within `expiresIn` seconds or re-quote; never cache a quote id across user sessions. Treat `GET .../rate` as indicative.
* **Read `data`, branch on HTTP status.** Success bodies are `{ success, data, meta? }`; 204s have no body; errors carry `code`.
* **Pagination loops terminate on `meta.nextCursor === null`**, with `limit` ≤ 100.
* **You authenticate your customer.** Dutchman Bridge checks only your API key; any 2FA, PIN or session check before a withdrawal or send is your app's to enforce.
* **No hardcoded currency.** A customer's fiat comes from their `country`; read `currency` off the balance, virtual account and quote responses rather than assuming one.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dutchmanbridge.com/get-started/going-live.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.