> 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/steps.md).

# Where to Start

A guide to getting started with Trybit.

Connecting Trybit is a short, multi-step process: from registration to your first real payment. Below is a detailed plan with links to instructions for each step.

### Step 1. Register in your personal dashboard

Create an account — it takes a couple of minutes. If you run into access issues later (lost email, confirmation email not arriving), solutions are on the [Registration and Account Access](/getting-started/sign-up.md) page.

### Step 2. Add a project

In your personal dashboard, click "Add Project" and go through the project-adding process: first choose the type — Website, Telegram Bot, or Donations (the type can't be changed after creation). Next, fill in the project details (name, line of business, description, expected turnover, domain or link to your bot/social profile) and confirm ownership — of the domain, bot, or profile, depending on the project type. The project is created immediately in test mode. A detailed breakdown of all steps in the project-adding process is on the [Adding a Project](/getting-started/add-project.md) page.

<figure><img src="https://1024061290-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlibkdeN79Y0EFrnLB1c%2Fuploads%2Fhoj8o3ihPGpIhL5GhYks%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202026-10-14%20%D0%B2%2018.05.24.png?alt=media&amp;token=2b5c8bfd-13ac-4aa3-ad12-7cbc04d0e0e0" alt="" width="380"><figcaption></figcaption></figure>

### Step 3. Complete verification

After filling in the project information and before starting integration, you need to confirm ownership of the domain or Telegram bot using one of the available methods.

### Step 4. Complete integration

After confirming project ownership, you need to choose one of the available integration methods. There are 4 options:&#x20;

* API — maximum flexibility, requires a developer;&#x20;
* CMS plugins — if your website runs on a popular platform (WordPress, Tilda, etc.);&#x20;
* HTML widget (with postback) — ready-made code to embed on your website, with payment notifications;&#x20;
* HTML widget (without postback) — the same widget, but without postback verification — suitable if you don't need notifications on your own server.

More details on the [Integration Methods](/integration/methods.md) page.

<figure><img src="https://1024061290-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlibkdeN79Y0EFrnLB1c%2Fuploads%2F07CGLWjADFAqn87ZMuO9%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202026-10-14%20%D0%B2%2018.08.35.png?alt=media&amp;token=82147f37-2482-4b93-9e74-ac8aff019a88" alt=""><figcaption></figcaption></figure>

### Step 5. Test your integration

The API key, Shop ID, and Secret key are issued at the "Keys and Test Payment" step of the project-adding process — right after choosing your integration method. Create a test invoice and complete payment on your platform from start to finish to make sure everything works correctly — the payment is created, the status updates, notifications arrive. How to do this — on the [Testing Your Integration](/integration/testing.md) page.

### Step 6. Submit a request to exit test mode

You can exit test mode only after you've fully set up integration and verified that POSTBACK works correctly — at the "Testing Your Integration" step. After that, you'll be able to submit the project for exiting test mode. Review takes up to 24 hours. Project requirements for approval — on the [Requirements and Restrictions](/general-information/connection-requirements.md) page.

### Step 7. Configure your project and start accepting payments

At this step, you finish [setting up the project](/getting-started/project-settings.md): choose currencies and adjust the checkout page display to your liking, and fine-tune all payment-acceptance parameters to the configuration most convenient for you — then you can start accepting payments.

### Step 8. Tell customers about the new payment method

Place Trybit's branded icons and payment buttons on your website — this increases recognition and customer trust in the new payment method. Ready-made elements and recommendations are on the [How to Add the Trybit Payment Method to Your Website](/integration/payment-display.md) page.

### If you need help

At any step, you can reach the support chat on the website or in your personal dashboard, or write to us on Telegram.

{% 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/getting-started/steps.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.