> 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/start/payment-icons-buttons.md).

# Integration of Icons and Buttons

Proper use of branded elements helps create a unified and recognizable user experience and increases conversion rates during the payment selection process.

The [Trybit Brand Guide](https://brand.trybit.com/) provides instructions for correctly placing Trybit on your website and in the payment process.

![Trybit Brand Guide](https://brand.trybit.com/~gitbook/image?url=https%3A%2F%2F1876679693-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F0qmF7ZfuUysWkk3Ugz0i%252Fuploads%252F89CWv8JhvbGEHatxv0hY%252FBanner.png%3Falt%3Dmedia%26token%3D84b31287-ae55-44c9-bbd4-2328cbd568dc\&width=768\&dpr=3\&quality=100\&sign=18da64b218bee1c5a08f3bed03e56fd5\&sv=3)

#### The brand guide includes:

* [Logo](https://brand.trybit.com/logo). Trybit logo variants and rules for their use.
* [Colour Palette](https://brand.trybit.com/colours). The brand colours that form the foundation of Trybit's visual identity.
* [Payment Marks](https://brand.trybit.com/payment-marks). Branded Trybit marks indicating that cryptocurrency is accepted. Icons of cryptocurrencies (BTC, ETH, USDT and others) and payment systems are also available. The SVG files can be added via HTML code or downloaded as an archive.
* [Payment Buttons](https://brand.trybit.com/payment-buttons). Buttons for payments and donations that start the cryptocurrency payment process.
* [Usage Examples](https://brand.trybit.com/usage-examples). Ready-made ways to tell users about the option to pay with cryptocurrency via Trybit.
* [Payment Method Display](https://brand.trybit.com/payment-display). Rules for presenting Trybit among other payment methods on your website.

![Trybit in payment methods list](https://brand.trybit.com/~gitbook/image?url=https%3A%2F%2F1876679693-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F0qmF7ZfuUysWkk3Ugz0i%252Fuploads%252Fip8CmTtPn77aJ2urpfQB%252F1%2520en.png%3Falt%3Dmedia%26token%3Dd1738cc3-2982-4338-9a67-661540cd45cb\&width=768\&dpr=3\&quality=100\&sign=c93716fd1866d4c1da923fc07c8e8354\&sv=3)

#### Using the brand guide helps:

* build customer trust;
* create a consistent brand image at every stage of payment;
* increase the number of successful payments and repeat purchases;
* raise the average order value and website conversion.

Icons and buttons are used in their original form, without changes to the design, colours or proportions. The Trybit icon is not used as a button: [payment buttons](https://brand.trybit.com/payment-buttons) are intended for starting a payment.

Correct integration of Trybit icons and buttons makes the payment process clear and predictable for users, which has a positive effect on key business metrics.

{% 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/start/payment-icons-buttons.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.