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

# CMS Plugins

Integrating Trybit via ready-made plugins for popular CMS platforms.

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.

Ready-made plugins let you connect Trybit payment acceptance without writing integration code — if your website runs on one of the supported platforms.

<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>

### Supported platforms

* [WooCommerce (WordPress)](https://docs.trybit.com/cms-plugins/list/woocommerce)
* [OpenCart](https://docs.trybit.com/cms-plugins/list/opencart)
* [Tilda](https://docs.trybit.com/cms-plugins/list/tilda)
* [GetCourse](https://docs.trybit.com/cms-plugins/list/getcourse)
* [WHMCS](https://docs.trybit.com/cms-plugins/list/whmcs)
* [Xenforo 2](https://docs.trybit.com/cms-plugins/list/xenforo-2)
* [Drupal](https://docs.trybit.com/cms-plugins/list/drupal)
* [PrestaShop](https://docs.trybit.com/cms-plugins/list/prestashop)

The list is constantly growing. Installation instructions for each platform are in the documentation: <https://docs.trybit.com/cms-plugins/list>.

<figure><img src="https://1024061290-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlibkdeN79Y0EFrnLB1c%2Fuploads%2FYwYQEzNQMEC9M0B4J6DB%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.31.44.png?alt=media&amp;token=f8204406-0b1d-4a29-93a6-b409767eb990" alt=""><figcaption></figcaption></figure>

### What to do if your CMS isn't on the list

Use the [HTML payment widget](https://support.trybit.com/integration/html-widget.md) (installs on any website without coding) or [connect via API](https://support.trybit.com/integration/api.md) / [Host2Host integration](https://support.trybit.com/integration/h2h.md) if you have a developer.

If you're interested in a plugin that isn't yet available, contact our support team and we'll help find a solution.

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