> For the complete documentation index, see [llms.txt](https://docs.nusa.nissology.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nusa.nissology.ai/renting/refunds.md).

# Refunds

**"Full refund if your rental ends unexpectedly."**

That's the promise on every rental, on every machine.

## When you're refunded in full

Your whole rental is refunded if it ends before its time because:

* **the machine went offline** and didn't come back,
* **Nusa itself had a problem** that ended the rental, or
* **the model you rented couldn't be made ready.**

The refund goes back to your Credit, and you're told on the rental, in Jobs and by email.

## When you're not refunded

* **You end the rental early yourself.** The time left isn't refunded.
* **Your own connection or code stops** while the machine is still running fine.
* **A model you switched to during the rental can't be made ready.** Go back to the model you rented, or choose another.
* **Nusa ended the rental because you broke the terms.** If you think it was a mistake, [contact Nusa support](mailto:support@nissology.ai) to appeal.

## If the connection drops for a moment

If the machine's connection drops briefly, you see that it's being retried. Your rental hasn't ended, but its clock keeps running and its end time doesn't move. If the machine doesn't come back, the rental ends and you're refunded in full.

## If the model can't be made ready

If the model you rented can't be made ready:

* **If the machine didn't have enough memory free for it**, you choose: end the rental and be refunded in full, or carry on with a different, usually smaller, model, without a refund.
* **Otherwise**, the rental ends and is refunded in full.

## For hosts

When a rental on your machine ends unexpectedly, the renter is refunded and **you aren't paid for that rental for now**. A review decides whether you're paid.

* **You're emailed at once**, with how to ask for a review. See [The emails you get](file:///6919936/hosting/stopping-rentals.md#the-emails-you-get).
* **To ask for a review**, [contact Nusa support](mailto:support@nissology.ai) if you believe your machine wasn't at fault. Nusa may also review it on its own. While a review you asked for is under way, the rental shows as under review.
* **When a review ends, you're emailed the result.** If you're to be paid, what the rental would have earned is added to your Earnings, and is Pending for 7 days like any new earnings.

A rental that ended because your machine went offline also lowers its reliability score, unless a review finds your machine wasn't at fault. To take your computer back without this, pause rentals instead of quitting Nusa Node. See [Pausing rentals](file:///6919936/hosting/stopping-rentals.md).


---

# 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.nusa.nissology.ai/renting/refunds.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.