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

# Support and FAQ

Answers to frequent technical questions about integration and Trybit support contacts.

Most questions during setup relate to notifications, authorization and test mode restrictions. Below are the answers to them, as well as links to Knowledge Base articles and the procedure for contacting support.

#### Why is the POSTBACK not arriving?

Check that the notification URL is correct and externally accessible on port 443 or 80 — other ports are not supported. Make sure the POSTBACK format (JSON or form-data) matches what your handler expects. A common cause is server time desynchronization: the JWT is valid for 5 minutes, and if the clock is behind or ahead, the signature fails verification. The delivery status is shown in the "Postback history" section, where the notification can also be resent. The section is located on the paid invoice page: "Payments" → the relevant invoice.

#### What does the 401 Unauthorized error mean?

The request failed authorization. Check that the key is passed in the header in the format `Authorization: Token <API KEY>`, without extra spaces or characters, and that the API KEY belongs to the project for which the invoice is being created.

#### How do I check an invoice status?

Send an [Invoice Information](https://docs.trybit.com/api-reference-v2/invoice-information.md) request with the INV number — a single request returns data for up to 100 invoices. The status is also shown in the "Payments" section of the dashboard.

#### Why does the test invoice status not change after confirmation?

The notification did not reach your server or was not processed. Check the integration settings and resend the notification — see [Testing the Integration](https://docs.trybit.com/start/test-integration.md).

#### Which settings can be changed after exiting test mode?

"Project currencies" and "Fees" are always available; "Auto-conversion", "Static wallets", "POS settings", "Payment page builder" and "Payment widget" — after the request is approved. The "Integration and API" section, project name, business type and description can be changed only in test mode; after changes, the project is sent for review again.

#### Can I change the website domain or bot link?

No — neither in test mode nor after exiting it. For another website or bot, add a new project.

#### In which currencies can I issue an invoice?

The invoice amount currency is passed in the currency parameter — see the full list of codes [on the Create Invoice page](https://docs.trybit.com/api-reference-v2/create-invoice.md). The customer pays the invoice in one of the cryptocurrencies enabled in the "Project currencies" section.

#### The customer paid, but the invoice was canceled. What should I do?

If the transaction was not confirmed in the network before the invoice expired, it will not be credited automatically. Contact support with the INV number, TXID and the address the funds were sent to.

#### The customer paid one invoice twice. How do I get the second payment credited?

Repeat payments for an already paid invoice are not credited automatically. Contact support with the INV number and the TXIDs of all transactions.

### Useful Knowledge Base articles

* [Which projects can be connected?](https://support.trybit.com/general-information/connection-requirements)
* [How do I add a project?](https://support.trybit.com/getting-started/add-project)
* [How do I configure a project?](https://support.trybit.com/getting-started/project-settings)
* [How do I create an invoice?](https://support.trybit.com/payments/methods-overview)
* [What are the service fees?](https://support.trybit.com/general-information/fees)
* [Which currencies and networks are supported?](https://support.trybit.com/general-information/currencies-networks)
* [How does payment work for the customer?](https://support.trybit.com/payments/payment-page)
* [How do I withdraw funds?](https://support.trybit.com/withdrawals/withdrawal-request)

### What to include in a support request

* the project SHOP ID;
* the invoice number (INV) and transaction TXID, if the question concerns a payment;
* the text of the API request and the response received, and the time of the request;
* the notification URL, if the POSTBACK is not arriving.

{% hint style="warning" %}
Never share your API KEY and SECRET KEY — support staff never request them.
{% endhint %}

{% hint style="success" %}
If you have any questions or need assistance, contact our support chat on the website and in the dashboard, or 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://docs.trybit.com/start/support-faq.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.
