> 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/reference/rozo-intents-tech-design.md).

# Intent Payment Flow

A Rozo intent describes a requested payment outcome. Your application creates the request, the payer authorizes the source payment, and your application checks the destination result.

```
Choose the task and supported route
                 ↓
Preview the amount and fees
                 ↓
Create the order and save its reference
                 ↓
Payer checks and authorizes payment
                 ↓
Read status or receive a verified notification
                 ↓
Reconcile the destination result
```

## What your application supplies

* The payment amount and asset according to the chosen API.
* The source and destination networks supported by that flow.
* The destination address when using a wallet transfer API. Merchant integrations instead use the receiving configuration associated with the merchant app.
* Any required recipient memo, app identity and application order reference.

Follow [Choose Your Integration](/start/choose-your-integration.md) before constructing a request. Do not combine fields from different APIs solely because they serve similar payment use cases.

## What your application receives

The selected API returns its order reference, payment instructions and status fields. Use those instructions for this order only. The returned amount and payment deadline take precedence over illustrative values in a guide.

Track the order until the requested destination result is confirmed. Source-payment detection is an intermediate result, not a general settlement guarantee. See the [payment lifecycle](/reference/rozo-intentpay-techdoc.md) for completion checks across merchant, Funding, Checkout and paid-API flows.

## Responsibilities at the integration boundary

The payer or authorized wallet signer approves the payment. Your application validates the recipient and amount, keeps request references, verifies notifications and reconciles uncertain create results through order lookup before taking further action. Do not assume that repeating a create request is safe.

Rozo executes the selected payment flow and exposes its result through the documented interface. Applications do not need to operate Rozo infrastructure to integrate. If an outcome remains unclear, query the existing order and [contact support](/company/contact-us.md) before sending again.

## References

* [Bridge & Wallet API](/integration/api-doc/bridge-api.md)
* [Merchant API](/integration/api-doc/merchant-api.md)
* [Funding API](/integration/api-doc/bridge-api/funding.md)
* [Webhook verification](/integration/api-doc/merchant-api/webhook.md)
* [Contracts & Audits](/reference/contracts-and-audits.md)