> 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/payment-display.md). # How to Add the Trybit Payment Method to Your Website How to present the Trybit payment method on your website: branded elements and display recommendations for customers. Once your integration is configured and tested, it's worth clearly showing customers that cryptocurrency payment via Trybit is available on your website — this increases trust and recognition of the new payment method. ### Where to get branded elements Ready-made branded elements — the logo, icons for supported payment methods, buttons — are available right in your dashboard, in the project's [brand-kit](https://brand.trybit.com/) section. There's no need to download them from third-party sources. ### What's recommended to display on your website * Name — a clear, correctly worded label for the payment method. * Icon — the Trybit brand mark and/or cryptocurrency icons. * Note — a brief description of the method and its terms. You can review payment-method display recommendations in [this section](https://brand.trybit.com/payment-display). ### Why this matters * customers see a familiar, recognizable payment method rather than an unfamiliar form — this reduces hesitation at checkout; * explicitly mentioning the payment method helps customers who were specifically looking for a crypto payment option but weren't sure the website supported it. {% hint style="success" icon="lightbulb" %} Not sure where to start? Use the knowledge base search (🔍the search icon in the page header) — it's often faster than browsing manually, especially given the volume of material. {% 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/payment-display.md?ask=&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.