> 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/getting-started/add-project.md). # Adding a Project Learn how to properly add a project to Trybit. A project in Trybit is a separate payment-acceptance point: a website, a Telegram bot, or a donation page — with its own keys, settings, and statistics. The type is chosen once at creation and determines which fields and setup steps you'll go through next. ### Project types When adding a project, you need to choose how you'll accept payments — this determines the form's field set: * **Website** — if you accept payments on a website. Integration will be required (see the [Integration](/integration.md) section). * **Telegram Bot** — if you accept payments through a Telegram bot. A separate project type. Integration will be required. * **Donations** — if you want to accept donations on a separate Trybit page. No integration required — more details on the [Accepting Donations](/payments/donation-page.md) page. The donations payment method is not suitable for commercial activity — it's intended only for voluntary donations and cannot be used to pay for goods, services, or any commercial transactions. {% hint style="info" %} **Important:** the project type cannot be changed after the project is created — choose it carefully at the first step of the project-adding process. {% endhint %} ### Can I add multiple projects to one account Yes. You can create and run several projects within one account — for example, for different business lines or different websites. Each project is configured independently: its own currencies, fees, integration, and payment page. ### How to add a project for accepting payments on a Website The project-adding process consists of 6 steps: Project Type → About the Project → Verification → Integration and API → Keys and Test Payments → Review and Submit. 1. **Project Type** — select "Website." The project type affects the field set and review order. The type cannot be changed after the project is created. 2. **About the Project:**\ Project name — displayed on the payment page, in customer receipts, and in your dashboard. Enter the name the way your customers know you. Line of business — choose the closest category. It must match your project's actual activity. Project description — 100 to 250 characters, describe in detail your niche, products or services, and target market. Generic phrasing like "we sell goods" slows down review. Expected turnover — an estimate of monthly payment volume. Provide a realistic figure — this speeds up review. Domain — a link to the live website where payments will be accepted. You'll need to verify it at the next step. Once you move to the next step, the link can no longer be changed. Contact for communication — provide a contact you check regularly. Our manager and support team will help with onboarding, answer questions, and quickly resolve any issues. We'll also use this contact to reach you if questions come up during moderation. 3. **Verification** — confirming domain ownership using one of three methods (your choice): DNS — add a TXT record with the issued value to the domain's DNS; Meta tag — place the issued tag inside the homepage; HTML file — upload a file with the issued content to the website's root folder. Verification is automatic and takes up to a minute. 4. **Integration** — choosing a connection method:\ API → Direct API integration. Full control over the payment flow. POSTBACK verification will be required next. CMS plugins → Ready-made modules for popular CMS platforms. URLs are filled in automatically. POSTBACK verification will be required next. HTML widget (with POSTBACK) → A widget for your website. Sends postback notifications about payment status. POSTBACK verification will be required next. HTML widget (without POSTBACK) → The same widget, without postback notifications. POSTBACK verification is not required. 5. **Keys and Test Payment** — at this step, the project's API key, Shop ID, and Secret key are issued. You'll need them to complete integration. Integration can be done using one of the available methods (see the [Integration Methods](/integration/methods.md) section). After completing integration, you need to test receiving POSTBACK (see the [Testing Your Integration](/integration/testing.md) section). You can submit a request to exit test mode only after successfully testing your integration. 6. **Review and Submit** — a final check of the entered data before sending it for moderation. Be sure to review the [requirements and restrictions](/general-information/connection-requirements.md) for the project and check all the data you've entered. Submit your request to exit test mode — review takes up to 24 hours from submission. You can track the request status in your dashboard. Once approved, you'll receive an email notification and can start accepting cryptocurrency payments on your website or platform. If the request is declined, a reason will be provided. Depending on the reason, you may be able to make changes and resubmit your request. After completing all the steps, the project appears in "My Projects." Until the request to exit test mode is approved, the project automatically stays in test mode. ### How to add a project for accepting payments via a Telegram Bot The project-adding process consists of 6 steps: Project Type → About the Project → Verification → Integration and API → Keys and Test Payments → Review and Submit. 1. **Project Type** — select "Telegram Bot." The project type affects the field set and review order. The type cannot be changed after the project is created. 2. **About the Project:**\ Project name — displayed on the payment page, in customer receipts, and in your dashboard. Enter the name the way your customers know you. Line of business — choose the closest category. It must match your project's actual activity. Project description — 100 to 250 characters, describe in detail your niche, products or services, and target market. Generic phrasing like "we sell goods" slows down review. Expected turnover — an estimate of monthly payment volume. Provide a realistic figure — this speeds up review. Bot link — a direct link to the bot or its @username. You'll need to verify it at the next step. Once you move to the next step, the link can no longer be changed. 3. **Verification** — open @BotFather, use the /setabouttext command, select your bot, paste the code, and confirm. Telegram updates the bot's data within a few minutes. 4. **Integration** — choosing a connection method:\ API → Direct API integration. Full control over the payment flow. POSTBACK verification will be required next. 5. **Keys and Test Payment** — at this step, the project's API key, Shop ID, and Secret key are issued. You'll need them to complete integration. After completing API integration, you need to test receiving POSTBACK (see the [Testing Your Integration](/integration/testing.md) section). You can submit a request to exit test mode only after successfully testing your integration. 6. **Review and Submit** — a final check of the entered data before sending it for moderation. Be sure to review the requirements and restrictions for the project and check all the data you've entered. Submit your request to exit test mode — review takes up to 24 hours from submission. You can track the request status in your dashboard. Once approved, you'll receive an email notification and can start accepting cryptocurrency payments on your website or platform. If the request is declined, a reason will be provided. Depending on the reason, you may be able to make changes and resubmit your request. After completing all the steps, the project appears in "My Projects." Until the request to exit test mode is approved, the project automatically stays in test mode. ### How to add a project for accepting Donations {% hint style="info" %} The donations payment method is intended only for voluntary donations and cannot be used to pay for goods, services, or any commercial transactions. {% endhint %} The project-adding process consists of 4 steps: Project Type → About the Project → Verification → Review and Submit. 1. **Project Type** — select "Donations." The project type affects the field set and review order. The type cannot be changed after the project is created. 2. **About the Project:**\ Project name — displayed on the payment page, in customer receipts, and in your dashboard. Enter the name the way your customers know you. Line of business — choose the closest category. It must match your project's actual activity. Project description — 100 to 250 characters, describe in detail your niche, products or services, and target market. Generic phrasing like "we sell goods" slows down review. Social media link — it's important to indicate the profiles where you're building your audience. These can only be changed in test mode. 3. **Verification** — confirming ownership of the specified profile/bot: place the issued verification code in the profile or bot description. 4. **Review and Submit** — a final check of the entered data before sending it for moderation. Submit your request to exit test mode — review takes up to 24 hours from submission. You can track the request status in your dashboard. Once approved, you'll receive an email notification and can start accepting cryptocurrency payments on your website or platform. If the request is declined, a reason will be provided. Depending on the reason, you may be able to make changes and resubmit your request. After completing all the steps, the project appears in "My Projects." Until the request to exit test mode is approved, the project automatically stays in test mode. ### What can be changed after a project is created Before exiting test mode after project creation, only the "Project Currencies" and "Fees" sections can be edited. Once test mode is lifted and the project becomes active, the remaining sections open up: "Autoconversion," "Static Wallets," "Payment Page Builder," "POS Settings," and "Payment Widget." After exiting test mode, you can freely make changes to the project settings without needing to re-enable test mode — with the exception of the "Integration and API" section: the POSTBACK format, success/failure payment URLs, notification URL, and integration method cannot be changed. Also, the project name, line of business, and project description can only be changed while in test mode. A separate restriction applies to the website URL or Telegram bot — this data cannot be changed either in test mode or after exiting it. If you need to specify a different website or bot, you'll need to create a new project. {% 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.trybit.com/getting-started/add-project.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.