> 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/integration/html-widget.md).

# HTML Payment Widget

Integrating Trybit via an HTML widget.

To start integrating, you need to create a project in your Trybit dashboard and obtain an API key and Shop ID — this data is needed to configure the interaction between your system and the platform, and to authorize requests.

The **HTML widget** is a ready-made payment form you can install on your website without API integration and without a developer. The customer simply chooses a currency, enters the amount and email — payment takes place in an embedded window (iframe), without redirecting to a separate page. You'll receive payment notifications in your dashboard, by email, on Telegram, and via POSTBACK if needed.

<figure><img src="https://1024061290-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlibkdeN79Y0EFrnLB1c%2Fuploads%2FpQZOX0ARJEcm18e4c3hV%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-15%20%D0%B2%2014.11.38.png?alt=media&amp;token=d4da5a83-a894-439c-ac10-5847a0d5d295" alt=""><figcaption></figcaption></figure>

### How to configure the widget

Configure the widget in the project settings, under "Payment Widget."

1. Choose the design and the text of the button or form.
2. For a button, you need to set a fixed payment amount. In a form, the customer can enter the amount themselves.
3. Choose the widget language.
4. Enable or disable the customer email field in the HTML form settings.
5. Save the settings and copy the generated code.

### How to add the form or button to your website

The widget can be installed using one of two methods — chosen in the same builder:

* [HTML form](https://docs.trybit.com/buttons-forms/html-widget/form) — the widget is displayed immediately as an embedded block on the page;
* [HTML button](https://docs.trybit.com/buttons-forms/html-widget/button) — only a button is shown on the page, and the payment form opens on click.

<figure><img src="https://1024061290-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlibkdeN79Y0EFrnLB1c%2Fuploads%2F0gCLZmEjC8SEShcpzmJZ%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-15%20%D0%B2%2016.33.02.png?alt=media&amp;token=997dab64-3873-45c5-8c38-f02ae4a9d3ed" alt=""><figcaption></figcaption></figure>

The generated code is inserted into your website's page code.

You can read more about the HTML widget in [this section](https://docs.trybit.com/buttons-forms/html-widget).

### Where to place the permanent link

The same builder also lets you get not just embeddable code, but also a permanent link to a separate payment page with the same settings — without needing to embed any code on your website at all. This link is convenient to place wherever HTML code can't be inserted:

* in a Telegram channel;
* in a social media profile description;
* in an email newsletter;
* on a landing page or in an ad.

{% 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/integration/html-widget.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.