> 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/use-cases/accessing-liquidity.md).

# Accessing liquidity

All seven use cases follow the same core facility lifecycle. Your approved facility and transaction policy determine which activities can be financed.

{% stepper %}
{% step %}

## Check Your Facility

Retrieve the current facility status, borrowing availability, supported asset and designated wallet. Facility eligibility does not remove request-specific validation.
{% endstep %}

{% step %}

## Request a Drawdown

Submit the required amount, tenor and business-transaction context. Keep the idempotency key associated with the logical request.

Qiro validates the request before preparing the unsigned borrower transaction.
{% endstep %}

{% step %}

## Sign and Confirm Funding

Your designated wallet signs and broadcasts the prepared transaction. Qiro's current workflow then requires asynchronous approval and funding.

{% hint style="warning" %}
**A confirmed borrower request is not a funded drawdown.** Confirm `FUNDED` before relying on the liquidity for payments.
{% endhint %}
{% endstep %}

{% step %}

## Execute the Approved Flow

Use the funded liquidity through the agreed wallets, conversion partners and payment arrangements. Qiro provides credit; your business remains responsible for the underlying payment execution.
{% endstep %}

{% step %}

## Repay

When the repayment source becomes available, convert into the required asset if necessary and follow the repayment workflow. The current partner API fully repays one funded drawdown; it does not accept a borrower-selected partial amount.

Confirm `REPAID` and check the updated facility before drawing again. Sending tokens directly does not replace the documented repayment process.
{% endstep %}
{% endstepper %}

## API and Wallet Responsibilities

The API manages requests, preparation and status. Funds move through blockchain transactions.

Your business controls the designated wallet, authorizes signing, broadcasts its transactions and pays gas. Status endpoints are authoritative; webhooks provide lifecycle notifications.

## Availability and Repayment

Availability, permitted use, tenor and security arrangements are agreed during underwriting. An API request does not guarantee immediate funding. Each flow must identify funds available to the borrower for principal, accrued interest and applicable charges.

[Explore All Use Cases](https://docs.qiro.fi/use-cases/use-cases.md)
