> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/how-tos/placing-orders/payments/braintree.md). # Braintree [Braintree](https://www.braintreepayments.com) is a full-stack payments platform that makes it easy to accept payments in your app or website. It is available for merchants in the United States, Canada, Australia, Europe, Singapore, Hong Kong SAR China, Malaysia, and New Zealand. Merchants can use Braintree to accept **PayPal**, **Apple Pay**, **Google Pay**, **Venmo**, and most credit and debit cards, including **Visa**, **Mastercard**, **American Express**, **Discover**, **JCB**, and **Diner’s Club**. Commerce Layer provides out-of-the-box **server-side** integration with Braintree. This section will walk you through the different steps you need to follow in order to let your customers process their payments using the Braintree payment gateway on our platform. For any additional info about the **client-side** part of the integration, SDKs, and libraries please refer to [Braintree official developer documentation](https://developers.braintreepayments.com). --- # 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.commercelayer.io/how-tos/placing-orders/payments/braintree.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.