> For the complete documentation index, see [llms.txt](https://docs.codemash.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codemash.io/dashboard/payments.md). # Payments The CodeMash Payments module is a powerful tool that provides a single API gateway for making payments in your application. With this module, you can easily integrate with some of the world's leading payment providers, including Apple Pay, Google Pay, Stripe, Kevin, Paysera, and Decta. One of the key features of the Payments module is its flexible payments schema, which allows you to define pricing without coding. This can be especially useful if you set up multiple pricing tiers or complex pricing structures. The module is designed to be easy to use and allows you to quickly set up and manage your payment integrations through a simple interface. In addition to its flexible pricing capabilities, the Payments module is also designed to be secure and reliable. It allows you to accept various payment methods, including credit and debit cards, mobile payments, and online bank transfers. This can help to ensure that your payments are processed smoothly and securely and can help to build trust with your customers --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.codemash.io/dashboard/payments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.