> 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/test-integration.md).
# Integration Testing
Before accepting real payments, the integration must be tested end to end: the invoice is created the same way a customer will create it, and the payment notification reaches your server and is processed correctly. For this purpose, every new project has a test mode.
### What is test mode
Test mode is enabled automatically after a project is added and remains active until the request to exit it is approved. The current state is shown in the project page header — the "Test mode" toggle.
* Invoices can be created by any method and confirmed without actual payment.
* Test invoices do not affect the balance — funds are not credited.
* Settings in the "Integration and API" section can be changed only in test mode.
* The "Auto-conversion", "Static wallets", "POS settings", "Payment page builder" and "Payment widget" sections become available after the request is approved.
### How to test the integration
1. **Create an invoice as a customer.** Place an order on your website or in your bot — the same way real customers will. An invoice created manually in the "Payments" section does not test the integration.
2. **Open test invoices.** In the "Payments" section, switch to "Test" and open the created invoice.
3. **Confirm the invoice without payment.** Click "Confirm invoice without payment".
4. **Check the notification.** Trybit will send a POSTBACK to the notification URL, and the invoice status will change to "Paid". Make sure your system received the notification, verified the signature and updated the order status.
{% hint style="info" %}
For the "API", "CMS plugins" and "HTML widget (with postback)" methods, a successful POSTBACK check is mandatory — without it, the request to exit test mode cannot be submitted. For "HTML widget (without postback)", no check is required.
{% endhint %}
### What to do if the invoice status does not change
* Check that the notification URL is correct and externally accessible on port 443 or 80.
* Make sure the POSTBACK format (JSON or form-data) matches what your handler expects.
* Check the server time: the JWT is valid for 5 minutes; if the clock is out of sync, the signature is considered invalid.
* Make sure the signature is verified with the SECRET KEY of this particular project.
The delivery result of each notification — the request and your server's response — is shown in the "Postback history" section. After making corrections, the notification can be resent. The section is located on the paid invoice page: "Payments" → the relevant invoice.
### What to check before submitting the request
* The invoice is created through placing an order on your platform.
* The POSTBACK is delivered, the signature is verified and the order status is updated.
* The success and failure payment URLs lead to the correct pages.
* The project details comply with [the requirements and restrictions](https://support.trybit.com/general-information/connection-requirements).
### How to exit test mode
The request is submitted at the "Review and submit" step of the project adding process. Review takes up to 24 hours from submission; the request status is shown in the dashboard. Once approved, you will receive an email notification. If the request is rejected, the reason will be stated — depending on it, you can make changes and resubmit the request.
### What changes after exiting test mode
* The "Confirm invoice without payment" button no longer works: an invoice is confirmed by full payment or manually — if you agree to accept a partially received amount.
* Deposits are credited to the balance.
* The "Auto-conversion", "Static wallets", "POS settings", "Payment page builder" and "Payment widget" sections become available.
* The "Integration and API" section, as well as the project name, business type and description, become locked for editing.
### How to re-enable test mode
Turn on the "Test mode" toggle in the project header. This is needed, for example, to change the settings in the "Integration and API" section. After the changes, the project is sent for review again — it takes up to 24 hours, and accepting real payments is suspended during this time.
{% 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/test-integration.md?ask=&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.
