> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.1/guides/user-guides/create-payment-manager-types/create-payment-hub-ee-payment-manager.md).
# Create Payment Hub EE Payment Manager
## Description
This guide provides the steps to create Payment Hub EE Payment Manager.
## Pre-requisites
The user should have a Program Manager role.
## Steps
1. Navigate to *Programs* using the menu bar.
2. Click on Configuration and then on Payment Hub EE Payment Manager.
3. Click on *Create* button which will navigate to the Payment Hub EE Payment Manager creation page.
4. In the payment manager creation page provide a name for the payment manager, select the program name, select Automatically Create batch if needed, and all the other configurations will auto-populate and can be changed accordingly.
5. Once the payment manager is saved it will be listed under the payment manager list view page which further can be used under the program configuration for which it was created.
---
# 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.openg2p.org/1.1/guides/user-guides/create-payment-manager-types/create-payment-hub-ee-payment-manager.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.
