> ## 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.

# POS Gateway

> Card-present payments from your point of sale through Mojo Payments' cloud, with no payment server in the store.

POS Gateway connects your point of sale to your CardPointe terminals through Mojo Payments' cloud, so there's no
payment server to run in the store. It's turned on by Mojo Payments and billed **per location**
it's on at.

You'll find it under **Settings → POS Gateway**.

## Turning it on at a location

Each location is turned on separately (and billed for each location it's on at). Turning a location off stops its
registers taking payments through the gateway at once.

## MIDs

The gateway uses each MID's CardPointe login from [Card Processing](/merchants/card-processing). A MID shows **Ready**
once its login is set; until then its registers can't take payments.

## Register keys

Each register gets its own **key**, made for one terminal:

<Steps>
  <Step title="Choose the location">The location the register is at.</Step>
  <Step title="Choose the terminal">From the terminals CardPointe lists for that location, by the name you gave them in CardPointe.</Step>
  <Step title="Create the key">The key is named after the terminal. Copy the secret now: it's shown only once.</Step>

  <Step title="Download the register setup (on-premises POS)">
    While the secret is on screen, **Download register setup** gives a zip with the Mojo Payments CLI, its settings and
    this key, ready for the register. Choose **Passport** if that's your POS. See [Installing the CLI](/cli/install).
  </Step>
</Steps>

Give the key id and secret, or the register's setup download, to whoever sets up your POS
([Connecting a point of sale](/integrators/overview)). A key works
only with its terminal and its location's MIDs. A key with **no terminal** is for back-office work (voids, refunds,
look-ups). **Revoke** a key to stop it at once, for example when a register is replaced.

## Terminal settings

Each location's terminals can behave differently. The settings are grouped the way a sale runs:

| Group | Settings |
| - | - |
| Sales | Capture approved sales (off: approve now, capture later); Allow signatures |
| Tips | Allow tips; up to three tip choices as percentages (0 shows a **No tip** button; leave a box empty to offer fewer) |
| Card present | Ask PIN debit or credit; show the amount; customer confirms the amount; ask for the CVV or billing ZIP, each optionally required |
| Keyed | For a card number typed on the terminal: ask for the CVV or billing ZIP, each optionally required |
| Terminal | Beep; how long the result shows; how long to wait before retrying a busy terminal |
| Testing | A test card, used only on CardConnect's test MIDs |

Locations you don't change use the defaults. **Back to the defaults** resets a location.

## Gateway version

Each location shows which version of the gateway it runs. Mojo Payments may move a location to a new version (for
example to try a new feature) and can move it back; you'll hear from us first.

## Calls

**Calls** lists every call your registers made through the gateway: when, what (sale, void, look-up…), the location,
amount and result. Payments themselves are in CardPointe.


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