> For the complete documentation index, see [llms.txt](https://docs.builtbydao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.builtbydao.com/housing-loyalty/rent-payments.md).

# Rent and Issuance

The lease and payment provider govern how rent is due and paid. RentalAndRebate does not receive the payment, split cash with Treasury, or change late-fee and tenancy rules.

## Separate the two events

1. **Rent payment:** the resident pays the amount due under the lease through the supported payment workflow.
2. **Housing Loyalty issuance:** after the qualifying base-rent period is verified, authorized rental operations issue the calculated Housing Loyalty credits.

Keeping these events separate prevents an application failure or chain delay from misrepresenting whether rent was paid.

## Calculation

Housing Loyalty amount = qualifying base rent × stamped property rate.

| Qualifying base rent | 5% rate | 10% rate | 15% rate |
| -------------------: | ------: | -------: | -------: |
|               $1,000 |      50 |      100 |      150 |
|               $1,500 |      75 |      150 |      225 |
|               $2,000 |     100 |      200 |      300 |

The contract uses whole, zero-decimal credits and cannot issue more than the qualifying amount for the record. Fees, deposits, damages, utilities, and unrelated charges are excluded.

## Dashboard evidence

The resident should be able to see the property and lease reference, qualifying period, base amount, stamped rate, calculated credit, authorization status, transaction hash, and confirmation state. Private lease and payment documents remain off-chain.

{% content-ref url="/pages/JxkR5zUnET7Ppq6pfpCO" %}
[How Housing Loyalty Works](/housing-loyalty/how-it-works.md)
{% endcontent-ref %}


---

# 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.builtbydao.com/housing-loyalty/rent-payments.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.