> 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/setting-up-your-terminal.md).

# Unboxing and First-Time Setup

**Your terminal is ready to take payments after a short setup — charge it, load the paper, and connect to Wi-Fi.**

***

When your POS terminal arrives, you do not need a technician. Unbox it, power it on, load the printer paper, connect to Wi-Fi, and you are ready to collect payment.

***

### **What's in the box**

* The POS terminal (S1F2)
* The charger that shipped with the terminal
* A starter roll of printer paper

The S1F2 is handheld: about 200 × 78 × 56 mm and 1.1 lb.

The terminal's serial number is on the device. Once the device is linked to your account, that serial also appears under **Team Preferences** > **Preferences** > **Point of sale** in [Your terminals](https://help.alternativepayments.io/payments-and-invoicing/pos/managing-pos-in-the-portal.md), and on each POS payment as **Device serial number**.

***

### **Charge the terminal**

Use **only the charger that came in the box**. The port looks like a standard USB-C port, but other USB-C cables will not charge the device.

Charging can be slow, even with the correct cable. Plug it in overnight before a workday. A full charge lasts a full day. The battery is user-replaceable (5,840 mAh); a spare covers a full day in the field.

{% hint style="warning" %}
**Tip:** If the terminal will not power on after charging, do not force it. Open the battery compartment, take the battery out, seat it again, and power on. See [POS Troubleshooting](https://help.alternativepayments.io/payments-and-invoicing/pos/pos-troubleshooting-and-faq.md).
{% endhint %}

***

### **Load the printer paper**

Blank receipts are almost always a paper-loading issue, not a broken printer.

1. **Open the printer cover** on the top of the terminal.
2. **Set the roll on top of the roller.** The paper should rest on the roller. Do not thread it through the roller.
3. **Confirm the orientation.** The paper should feed so the printed side comes out cleanly. If receipts print blank, flip the roll and try again.
4. **Close the cover** and print a test receipt from the terminal.

Use paper that matches the width of the roll that shipped with the terminal. A roll that is slightly too wide will crease and jam. When the starter roll runs out, see [Buying Receipt Paper](https://help.alternativepayments.io/payments-and-invoicing/pos/buying-receipt-paper.md).

***

### **Connect to Wi-Fi**

Your terminal needs Wi-Fi to take payments.

1. Power the terminal on.
2. Open the terminal's network / Wi-Fi settings.
3. Join the Wi-Fi network at that location.
4. Wait until the terminal shows it is connected.

If you take the terminal to a customer's site, you will need to join **their** Wi-Fi before you can collect payment.

***

### **Take your first payment**

Once the terminal is charged, paper is loaded, and Wi-Fi is connected, you can [take a payment](https://help.alternativepayments.io/payments-and-invoicing/pos/taking-a-pos-payment.md).

**Love our platform?** 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.alternativepayments.io/payments-and-invoicing/pos/setting-up-your-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.
