> For the complete documentation index, see [llms.txt](https://docs.zirodelta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zirodelta.com/use-cases/payout-advances.md).

# Advances against upcoming payouts

**For:** marketplaces, delivery, creator and canteen platforms.

## The problem

Sellers, drivers, creators and small merchants are often paid at the end of the day or week, but their costs come first. Banks rarely lend to them, even though the platform knows exactly how much they sell.

## How it works

1. The platform shares a seller's sales history with the [Credit Engine](/modules/credit-engine.md) to set a safe advance.
2. The seller receives part of their next payout early.
3. When the payout comes due, the [Settlement Engine](/modules/settlement-engine.md) repays the advance first and releases the rest to the seller.

## Who funds it

Zirodelta's own capital, never the platform's users' money.

## Modules used

Credit, Settlement.

## Things to know

* Lending is regulated in most countries. Advances run through licensed lending partners where the law requires it.
* Advances are short, and limits are set from real sales data.

## Status

In development.


---

# 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.zirodelta.com/use-cases/payout-advances.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.