> For the complete documentation index, see [llms.txt](https://docs.rozo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rozo.ai/integration/api-doc/merchant-api.md).

# Merchant API

Use this API when you are a **merchant accepting payments**. Your receiving wallet address is configured once on your merchant `appId` (via [partners.rozo.ai](https://partners.rozo.ai)) — so payment requests **never include a destination address**. Customers pay from any supported chain, and you receive the token and chain you chose.

## Pages

* [API Quick Start (Merchant)](/integration/api-doc/merchant-api/api-quick-start-merchant.md) — create a payment and poll its status in two calls.
* [Merchant API Keys](/integration/api-doc/merchant-api/merchant-api-keys.md) — Admin vs Orders scope, and using keys from an AI agent.
* [API Doc (POSTMAN)](/integration/api-doc/merchant-api/api-doc-postman.md) — full OpenAPI spec and Postman collection.
* [Webhook](/integration/api-doc/merchant-api/webhook.md) — get notified on `payment_payin_completed` and `payment_payout_completed`.

## Bridging your own funds instead?

If you want to send funds to an **arbitrary destination address you specify per request**, use the [Bridge & Wallet API](/integration/api-doc/bridge-api.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.rozo.ai/integration/api-doc/merchant-api.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.