> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-getting-started/verifone-central/commerce.md).

# Commerce

Use Commerce to monitor payment activity, analyze reporting data, and take payment actions.

### Reporting

* [Payments Dashboard](/verifone-central-getting-started/verifone-central/commerce/payments-dashboard.md) — monitor transaction KPIs, payment methods, refunds, and authorization rates.
* [Reporting](/verifone-central-getting-started/verifone-central/commerce/reporting.md) — analyze transactions, 3DS, settlements, invoices, and payouts.

Use filters to focus results by organization, date, currency, channel, transaction type, status, wallet, and more.

### Payment tools

* [Virtual Terminal](/online-payments/virtual-terminal.md) — initiate card-not-present payments.
* [Pay by Link](/online-payments/pay-by-link.md) — create and share a payment link.

Use transaction details in reporting to capture, refund, or cancel a payment.

### Related administration

Manage organizations, contracts, points of interaction, users, and advanced settings in [Administration](/verifone-central-getting-started/verifone-central/administration-tools.md).

{% hint style="info" %}
Your available data and tools depend on your organization and role.
{% endhint %}

### Support

Find regional contact options in [Help & Support](/verifone-central-getting-started/verifone-central/help-and-support.md).

{% hint style="warning" %}
When the language is set to Arabic or Hebrew in the *My Account* section, the menus and buttons might be placed differently than in the other language settings. As a result, the documentation might not describe the positions of menus and buttons for the Arabic and Hebrew language versions of Verifone Central.
{% endhint %}


---

# 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.verifone.com/verifone-central-getting-started/verifone-central/commerce.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.