> 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.3/pbms/functionality/program-management/user-guides/create-payment-manager.md).
# Configure Payment Manager in Program
## Description
This guide provides steps to configure the payment manager in a program.
## Prerequisites
The user must have the Program Administrator role.
## Steps
1. Navigate to *Programs* using the menu bar.
2. Click on the program name for which configuration to be done.
3. Navigate to the *Configuration* section on the Program detailed view page.
4. Click on *Add a line* in the *Payment Manager* section.
5. Click on the *Create* button on the Add: Payment Managers pop-up window.
6. Select the payment manager type.
7. If a payment manager is already created ([Create Payment Manager](/1.3/pbms/functionality/program-management/user-guides/create-manager-type/create-payment-manager-types.md)), search and select the same or else once the name is provided to the program manager, *Create and Edit* buttons will appear. Click on *Create and Edit* to create a payment manager.
8. Provide the details in the payment manager creation manager.
9. Click on the *Save* button and then click on the *Save & Close* button which will save the payment manager to that program under configuration.
---
# 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.3/pbms/functionality/program-management/user-guides/create-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.
