> For the complete documentation index, see [llms.txt](https://docs.qiro.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qiro.fi/developer-section/qiro-instant-settlement/overview.md).

# Overview

Qiro Instant Settlement separates API authorization from wallet authorization.

An OAuth access token allows the partner application to call Qiro APIs. It cannot move funds. Money moves only when the approved designated wallet signs and broadcasts a blockchain transaction prepared by Qiro.

Qiro owns:

* partner authentication and resource authorization;
* facility, policy, chain, token, contract, and wallet resolution;
* request validation and unsigned transaction preparation;
* contract-event reconciliation;
* normalized status APIs and signed webhooks.

The partner owns:

* OAuth client credential custody;
* designated wallet custody and signing policy;
* gas payment and transaction broadcasting;
* webhook receipt, deduplication, and status reconciliation.

Qiro never accepts partner-supplied wallet, chain, contract, rate, fee, credit-limit, or allocation overrides for money-moving operations.

## Lifecycle pattern

Most money-moving workflows follow the same pattern:

1. The partner creates a durable resource with an idempotency key.
2. Qiro validates business and contract state.
3. Qiro returns a short-lived unsigned transaction preparation.
4. The partner wallet signs and broadcasts exactly that transaction.
5. Qiro verifies contract evidence and updates the resource status.
6. Qiro sends a signed webhook for partner-relevant lifecycle changes.

Status endpoints are authoritative. Webhooks are at least once and may arrive more than once or out of order across different resources.

## OpenAPI specification

Use the guides for workflow context. The exact API contract is maintained in `openapi.yaml`. The GitBook owner will register that file and insert the rendered OpenAPI Reference separately.
