> ## Documentation Index
> Fetch the complete documentation index at: https://kb.paymentsmojo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mojo Payments CLI

> The `mojo` command: card-present payments for an on-premises POS that runs a program and reads a file.

The **Mojo Payments CLI** (`mojo.exe`) lets a point of sale on a Windows machine take payments without making HTTPS
calls itself. The POS runs `mojo` with an action and a request, the CLI calls the [POS Gateway API](/api/overview), and
writes the answer to a **result file** the POS reads.

```
POS ──runs──▶ mojo.exe "-a=AuthorizeXml" "-f=sale.txt" "-c=<request>" ──HTTPS──▶ POS Gateway
POS ◀──reads── sale.txt (the answer)
```

* **One file, nothing to install**: a single `mojo.exe` for 64-bit Windows, with its settings in `appsettings.json` beside
  it. No runtime, no service.
* **Runs per payment**: the POS starts it for each action; it exits when the result file is written.
* **Same requests as the API**: the request in `-c` is the API's XML request for that action ([Actions](/api/actions)).

<CardGroup cols={2}>
  <Card title="Install" icon="download" href="/cli/install">Get a register's setup from the portal.</Card>
  <Card title="Commands and results" icon="terminal" href="/cli/commands">Every action, and the result file.</Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.