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

# Integration Methods

Integrating with Trybit via API, CMS plugins, an HTML widget, and other tools.

Trybit offers several ways to connect payment acceptance — choose based on your team's technical readiness and your project's needs.

| Method                                             | Developer needed | When it fits                                                              |
| -------------------------------------------------- | ---------------- | ------------------------------------------------------------------------- |
| [API](/integration/api.md)                         | Yes              | Maximum flexibility and control over the payment-acceptance logic         |
| [Host2Host (White Label)](/integration/h2h.md)     | Yes              | Accepting payments without redirecting the client to a third-party domain |
| [HTML Payment Widget](/integration/html-widget.md) | No               | Quickly installing a payment form/button on your website without coding   |
| [CMS Plugins](/integration/cms-plugins.md)         | No / minimal     | Your website runs on a popular CMS (WordPress, Tilda, etc.)               |

Payment-status notifications for any of these methods can be received via [POSTBACK](/integration/postback.md) — to the merchant's own server.

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