> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/changelog/legacy-changelog/new-release-list-of-simulator-supported-payment-channels.md). # New Release: List of simulator-supported payment channels We are thrilled to announce that the list of simulator-supported payment channels has been released! 🎉 As you may already know, Coda provides a [portal simulator](/codapay/integration-guides/testing-guide/sandbox-testing-guide.md) and an [old simulator](broken://pages/tM6UHJDCfYe6LMn1iBto) for sandbox testing. At the same time, not all payment channels are supported, causing unnecessary confusion. Therefore, this page lists all Coda simulator's supported and non-supported payment channels. Our team is committed to providing a seamless and efficient integration experience. If you have any questions or need further assistance, please don't hesitate to reach out to our support team. Thank you for your continued support and collaboration. We look forward to enhancing your payment experience with our API. --- # 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.coda.co/changelog/legacy-changelog/new-release-list-of-simulator-supported-payment-channels.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.