> For the complete documentation index, see [llms.txt](https://help.alternativepayments.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.alternativepayments.io/payments-and-invoicing/pos/pos-receipts-and-reference-numbers.md).

# POS Receipts and Reference Numbers

**Every approved POS payment prints two copies. The numbers on the slip will not all match the dashboard — here's which ones to use.**

***

When a POS payment is approved, the terminal prints a **merchant copy** and a **cardholder copy**. Hand the cardholder copy to your customer. Keep the merchant copy with your records.

The receipt can show more than one ID. Your Alternative Payments dashboard uses different labels. Match them this way.

***

### **What you will see in the dashboard**

Open the payment from [Transactions](https://app.alternativepayments.io/dashboard/all-transactions). On **Payment overview** you will see:

* **Transaction type** — **Point of Sale (POS)**
* **Device serial number** — the serial on the terminal that took the sale
* **Payment ID** — Alternative Payments' unique identifier for the payment. Use this when you talk to our team about a refund or a dispute.
* **Reference** — the reference from the sale (this is the number that lines up with the merchant reference on the receipt)

{% hint style="info" %}
**Note:** The receipt may also print a tender / terminal-local number (often with a prefix such as NUFT). That number is generated by the device. It will not match Payment ID. Do not use it to request a refund.
{% endhint %}

***

### **Merchant copy vs. cardholder copy**

| Copy            | Who keeps it  | What it is for             |
| --------------- | ------------- | -------------------------- |
| Merchant copy   | You           | Your record of the sale    |
| Cardholder copy | Your customer | Their record of the charge |

If the printer produces a blank slip, the paper is loaded incorrectly. Flip or reseat the roll — see [Unboxing and First-Time Setup](/payments-and-invoicing/pos/setting-up-your-terminal.md).

***

### **Finding the payment in your dashboard**

1. **Log into your** [**Alternative Payments dashboard**](https://app.alternativepayments.io/)
2. **Open Transactions**\
   \
   Go to **Accounts receivable** > [**Transactions**](https://app.alternativepayments.io/dashboard/all-transactions). Stay on the **Payments** tab.
3. **Filter to Point of Sale (POS)**\
   \
   Open **More filters**, choose **Type**, and check **Point of Sale (POS)**. You can also sort the **Type** column.
4. **Open the payment**\
   \
   Confirm **Transaction type** is Point of Sale (POS) and that **Device serial number** matches the terminal.

***

### **If you cannot find a payment**

* Confirm the terminal showed **approved**, not canceled. A payment canceled with **X** on the terminal will not appear in your dashboard. See [Cancel, Refund, and POS Payouts](/payments-and-invoicing/pos/pos-refunds-cancels-and-payouts.md).
* Search with **Payment ID** or **Reference**, not the tender number on the slip.
* Allow a short delay after the sale, then refresh Transactions.

**Love our platform?** Rate us on [Channel Program](https://channelprogram.com/v/alternativepayments) and check out our [Referral Program page](https://www.alternativepayments.io/referral-partners/)!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.alternativepayments.io/payments-and-invoicing/pos/pos-receipts-and-reference-numbers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.