> 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/manual-payments.md). # Manual payments Besides being integrated with the most common payment gateways, Commerce Layer offers the possibility to use a **manual gateway**, useful to process wire transfers, cash payments, and other kinds of manual payments. Creating a manual payment gateway is quite easy: just choose a meaningful name that helps you identify the gateway within your organization and flag the "Require capture before shipping" checkbox in case you want to start fulfilling orders only once the manual payment is captured. This section will walk you through the steps you need to follow in order to let your customers process their payments using a manual gateway on our platform. --- # 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/manual-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.