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

# Invoice Statuses

A description of invoice statuses in Trybit.

### What invoice statuses exist

* **Created** — the invoice is issued and valid, awaiting payment.
* **Paid** — payment has been credited in full.
* **Partially paid** — less than the invoice amount arrived at the address (see below).
* **Overpaid** — more than the invoice amount arrived at the address.
* **Cancelled** — the invoice wasn't paid and its validity period has expired.

### How long payment confirmation takes

The time depends on the network:

| Network                                           | Confirmation time           |
| ------------------------------------------------- | --------------------------- |
| ERC20 / TRC20 / BSC / TON / SOL / BASE / ARB / OP | 30 seconds to 5 minutes     |
| BTC                                               | 10 minutes to several hours |
| LTC                                               | 2-10 minutes                |

Exact ranges are shown right on the payment page, next to each network in the selection list.

Status can be tracked using the "Check Transaction" button [on the payment page](/payments/payment-page.md).

{% hint style="info" %}
**Important:** if an invoice is cancelled (its validity period has expired), it won't be paid and credited automatically — even if the customer managed to send the full amount before the deadline but the transaction wasn't confirmed on the network in time. To have such a payment credited, you need to contact support directly — the reasons for a delay can vary, including blockchain network congestion.
{% endhint %}

### Partial payment: why it happens and what to do

This happens when the customer didn't account for their wallet's, exchange's, or the network's fee — and less than the invoice amount arrived at the address. The system automatically calculates and displays the minimum missing amount on the invoice page.

From there, there are three options:

* **The customer pays the missing amount** (factoring in fees). If their wallet's or exchange's minimum send limit is greater than the top-up amount, they can send more — the invoice will still be confirmed.
* **The merchant confirms the invoice manually** — in the "Payments" section, find the invoice using the status filter → "Confirm." This means the merchant agrees to accept the amount actually received as payment in full.
* **Auto-confirmation by allowed deviation** — if enabled [in the project settings](/getting-started/project-settings.md), the invoice is confirmed automatically for a small underpayment.

{% hint style="success" %}
If you have any questions or need help, you can contact our support via chat on the website and in your personal account, as well as reach us on Telegram. Support contacts are listed [on our website](https://trybit.com/support).
{% endhint %}


---

# 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://support.trybit.com/payments/invoice-statuses.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.