> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/company/payment-method-centre/payment-method-centre-fields.md).

# Payment Method Centre Fields

### Header Level Icons

These functionalities are designed to meet diverse needs, ensuring users experience seamless navigation and effective management of customer information.

1. **Refresh:**
   * This empowering functionality allows users to refresh search results based on selected criteria, ensuring the displayed information is consistently up-to-date.
2. **Save:**
   * The Save feature preserves updated user interface (UI) settings, delivering a personalized and consistent experience for future interactions within the module.
3. **Advanced Search:**
   * Elevating customer information retrieval, the Advanced Search option enables users to conduct sophisticated searches by specifying criteria like Column Name, Operator, and Value. This facilitates precise and tailored information retrieval.
4. **Columns:**
   * Representing customizable criteria, Columns empower users to refine their searches further. The options in the dropdown menu for Columns dynamically adjust based on the active tab, ensuring relevance and convenience.

The options included the Columns dropdown are -

* **Name**: This field indicates the name of the Payment Method, such as Visa, MasterCard, Cash, and others.
* **Type**: This field specifies the type of Payment Method, which can include cash, credit card, cheque, and others. For more detailed information about Payment Method types, please click here.
* **Is Active**: This field reflects whether the Payment Method is currently active and in use within the system.

5. **Download:**

* This versatile feature allows users to export and download data in various file formats, providing a summarized overview for quick reference. Options include CSV, TXT, MS-Word, MS-Excel, PDF, and MS-Excel(.xlsx), catering to diverse user preferences and use cases.

### Context View (Right Click Options):

By right-clicking on the Payment Method row or the selected record, users gain access to the following options:

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FQiPEbRUpA7OyMwAp0JQW%2FOpen%20Delete%20Payment%20Method%20Centre.png?alt=media&amp;token=f4e1a50c-2784-4e70-89c5-272f6a0e84fd" alt=""><figcaption></figcaption></figure>

**Open**: This action directs users to the Payment Method module, enabling them to review details and make necessary modifications.

**Delete**: This option grants users the ability to remove the Payment Method permanently from the system.


---

# 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.xorosoft.com/xoroerp-1/admin/company/payment-method-centre/payment-method-centre-fields.md?ask=<question>&goal=<user_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.