> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/merchant-portal/guides/virtual-terminal.md).

# Virtual Terminal

Virtual Terminal lets you accept online payments without any equipment. It's simple to use, mobile-friendly, and serves as a back-office management tool. Key features include batch reports, transaction search, and card-on-file payments.

The following articles provide a step-by-step guide on using Virtual Terminal:

* [Accessing Virtual Terminal](/merchant-portal/guides/virtual-terminal/accessing-virtual-terminal.md)
* [Adding or Ordering the Equipment](/merchant-portal/guides/virtual-terminal/adding-or-ordering-the-equipment.md)
* [Recurring Payments](/merchant-portal/guides/virtual-terminal/recurring-payments.md)
* [Processing Sales Transaction](/merchant-portal/guides/virtual-terminal/processing-sales-transaction.md)
* [Processing ACH Transaction](/merchant-portal/guides/virtual-terminal/processing-ach-transaction.md)
* [Transaction Search](/merchant-portal/guides/virtual-terminal/transaction-search.md)
* [Open Batches](/merchant-portal/guides/virtual-terminal/open-batches.md)
* [VT Settings](/merchant-portal/guides/virtual-terminal/vt-settings.md)

{% hint style="warning" %}
**Note**: You can access the VT Settings option only if you are assigned the *admin* user role.
{% 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.xplorpay.com/merchant-portal/guides/virtual-terminal.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.