> For the complete documentation index, see [llms.txt](https://docs.violet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violet.io/prism/payments/payment-integrations.md). # Payment Integrations **Overview of Nested Pages** In the nested pages of the Payment Integrations section, you'll find: * **Supported Payment Gateways**: Information on various payment gateways you can integrate, including compatibility and setup instructions. * **Payments API Documentation**: Detailed guides on using the Payment API, including authentication methods, endpoints, and request/response formats. * **Integration Guides**: Step-by-step instructions for integrating payments into your application or website, tailored to different platforms and technologies. * **Recurring Payments**: Guidelines on setting up and managing subscriptions and recurring billing cycles. * **Common Issues & Troubleshooting**: A list of frequent problems and their solutions to help you resolve issues quickly. Explore these sections to streamline your payment integration process and enhance your understanding of the available tools and resources. --- # 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.violet.io/prism/payments/payment-integrations.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.