> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/tour/billing/payment-integrations.md). # Payment integrations Bunny connects to electronic payment processors via plugins. Without any of these plugins enabled, the only payments you can register are checks and wire transfers that you manually enter as paid. ### Stripe Bunny integrates with Stripe, the world's leading payment processor, for debit/credit card and bank payments. Read more about the [Stripe integration](/guide/advanced-guides/integrations/stripe.md) for configuration details. ### Demo pay Your Bunny instance is created with Demo pay enabled by default. This enables you to easily test the payment user experience without actually transferring any real money or setting up a payment processor in test mode. The payments made with Demo Pay are recorded as real transactions, but you can delete all the data before going live with Bunny or you can set up a separate production instance. --- # 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.bunny.com/guide/tour/billing/payment-integrations.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.