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

# Payment Methods Overview

Learn about the different ways to create invoices in Trybit.

Trybit lets you create invoices in different ways depending on your project type and the level of integration you need.

### If you have a website and a developer

[API](/integration/api.md) or [Host2Host](/integration/h2h.md) integration — an invoice is created automatically for every order, with no manual action. Host2Host additionally doesn't redirect the client to a third-party domain.

### If your website runs on a popular CMS

[CMS plugin](/integration/cms-plugins.md) — a ready-made plugin for your platform (WooCommerce, OpenCart, Tilda, and others), connects without coding.

### If you need to connect payment acceptance quickly without coding

[HTML payment widget](/integration/html-widget.md) — a ready-made form or button to embed on your website, or a permanent link to a ready-made payment page — without API integration.

### If you need a one-off invoice for a specific customer

[Creating payment links](/payments/payment-links.md) — manually creating an invoice in your dashboard, without integration.

### If the same customer pays multiple times

[Static wallets](/payments/static-wallets.md) — a permanent address tied to the user; convenient, for example, for topping up a balance in a gaming service.

### If you need to accept payments offline — at a point of sale or an event

[POS terminal](/payments/pos.md) — a permanent link to the terminal page: the seller enters the amount, shows the customer a QR code, and the status updates automatically. Works from a mobile device, tablet, or register screen.

### If you need to accept donations

[Accepting donations](/payments/donation-page.md) — a permanent link where the payer enters the amount themselves. Requires no website or integration — suitable for content creators, nonprofits, and any collection of arbitrary amounts.

### Comparison table

| Method              | Website needed                            | Developer needed        | Best for                                   |
| ------------------- | ----------------------------------------- | ----------------------- | ------------------------------------------ |
| API                 | Yes                                       | Yes                     | Automating every order                     |
| Host2Host           | Yes                                       | Yes                     | Automation without redirects               |
| CMS plugin          | Yes (on a supported CMS)                  | No                      | Quick setup on a ready-made platform       |
| HTML widget         | Yes (or not needed with a permanent link) | No                      | Accepting payments without API integration |
| Manual payment link | No                                        | No                      | A one-off invoice for a specific customer  |
| Static wallets      | No                                        | No (or API, optionally) | Repeat payments from the same user         |
| POS terminal        | No                                        | No                      | An offline point of sale or event          |
| Accepting donations | No                                        | No                      | Donations and arbitrary amounts            |

### What all methods have in common

Regardless of how the invoice is created, the payment itself always happens on the same [payment page ](/payments/payment-page.md)— with a choice of currency, network, and payment method (transfer to a wallet address, Web3 wallet, WalletConnect), automatic confirmation, and notifications.

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