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

# Payments and locations

> Your locations and MIDs, and the card payments your POS made.

## Locations and MIDs

* `GET /locations` (`locations.view`): your locations (stores), with address, receipt name, time zone and status.
  `GET /locations/{id}` for one.
* `GET /accounts` (`accounts.view`): your MIDs, each with the location it belongs to. `?locationId=` keeps one
  location's. A MID's `id` is what [invoices](/developers/invoices) take as `merchantAccountId`.

## Card payments

`GET /pos-gateway/transactions` (`payments.view`) lists every call your point-of-sale made through the
[POS Gateway](/api/overview), newest first, a page at a time: sales, voids, refunds, captures and look-ups. Sort by
`when`, `action`, `mid`, `status` or `amount`.

| Field | Is |
| - | - |
| `action` | What the POS asked for, e.g. `AuthorizeXml` (a sale on the terminal), `VoidXml`, `RefundXml`. |
| `orderId` | The POS's own order id. |
| `amount` | In dollars. |
| `respStat` | The processor's answer: `A` approved, `B` retry, `C` declined. |
| `respText` | The processor's words, e.g. `Approval`. |
| `retRef` | The processor's reference: it ties a sale to its void, refund and deposit. |
| `error` | Why the gateway couldn't complete the call, when it couldn't. |

## Business cards

`GET /pos-gateway/business-cards?days=90` adds up approved sales by card kind (purchasing, corporate, business, debit,
credit, prepaid) and brand, and estimates what sending Level 3 data saves, or would have saved, on corporate and
purchasing cards.


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