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

# HTML-widget

Enable crypto payment acceptance on your website using a ready-made HTML widget.

**The HTML widget** is suitable if you need to accept payments on your website without API integration and without a developer. You configure the appearance in the dashboard, copy the ready-made code and paste it onto your page. The customer selects a currency, enters an amount and email, and the payment takes place in an embedded window — without leaving for another website.

### Form or button — which to choose

| <p><br></p>            | [**HTML form**](/buttons-forms/html-widget/form.md)                      | [**HTML button**](/buttons-forms/html-widget/button.md)                     |
| ---------------------- | ------------------------------------------------------------------------ | --------------------------------------------------------------------------- |
| Appearance             | An embedded payment block directly on the page                           | A button that opens the payment window when clicked                         |
| What can be configured | Form style, button text, email and amount fields, language               | Template, text, style and size of the button, amount and currency, language |
| When to choose         | A dedicated payment page or section where the customer enters the amount | A product or service card, a package with a fixed price                     |

### Where the widget is configured

The widget is configured in the "Payment widget" section of the project settings: "My projects" → the relevant project → "Project settings" → "Payment widget". The section becomes available after the request to exit test mode is approved.

The integration method is selected at the "Integration" step of the project adding process:

* **HTML widget (with postback)** — Trybit sends POSTBACK notifications about the payment status to your server. Before submitting the request to exit test mode, you need to test POSTBACK delivery.
* **HTML widget (without postback)** — no notifications are sent to the server; no POSTBACK check is required.

### What is a permanent payment link

The same section generates a permanent link in the format <https://pay.trybit.com/static/\\><SHOP ID>. It opens a separate page with the widget and the same settings — no need to embed code on your website. The link is convenient to place where HTML cannot be inserted: in a Telegram channel, profile description, newsletter or ad.

### How to receive payment notifications

* **POSTBACK** — to the notification URL, with the "HTML widget (with postback)" method. → [Automatic POSTBACK](/api-reference-v2/postback.md)
* **Dashboard** — all payments are shown in the "Payments" section.
* **Email and Telegram** — enabled in the account "Settings". → [Notifications](https://support.trybit.com/account/notifications)

{% 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/buttons-forms/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.