> 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/axerve.md). # Axerve How to pay for an order using Axerve payment gateway [Axerve](https://www.axerve.com/) Ecommerce Solutions is a payment gateway that can handle any use case you might have with your business. It accepts payments from all types of credit cards and any other system (MyBank, PayPal, Yandex, and more), letting you customize every aspect of the payment page. The Axerve payment platform processes more than 4 million requests every month. Thanks to the 250 alternative payment methods available and 20 acquirers, transactions can be completed successfully worldwide. Commerce Layer provides out-of-the-box **server-side** integration with Axerve's [Lightbox](https://docs.axerve.com/en/integration-types/lightbox) solution. This section will walk you through the different steps you need to follow in order to let your customers process their payments using the Axerve payment gateway on our platform. For any additional info about the **client-side** part of the integration, SDKs, and libraries please refer to [Axerve official developer documentation](https://docs.axerve.com/en/). --- # 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.commercelayer.io/how-tos/placing-orders/payments/axerve.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.