> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-us/payware-connect/device-management/store-portal-device-master/setting-up-a-new-pos-device.md).

# Setting Up a New POS Device

Set up a new POS device in the Store Portal's Device Master.

{% hint style="info" %}
**Use this when** you need to add a new POS device — POSAPP, Payment Terminal, or Mobile — to Device Master in the Store Portal.
{% endhint %}

{% stepper %}
{% step %}

### Open Device Master

Hover over **Account Admin**, then select **Device Master**. The Device Master window lists existing POS devices and their statuses.
{% endstep %}

{% step %}

### Start a new device

Select the **New Device** icon, then select **New Device**. The **New Device Setup** window opens.
{% endstep %}

{% step %}

### Choose the device type and serial number

Select a **Device Type** and enter the device serial number. Available types include **POSAPP** (Customer POS Application), **Payment Terminal**, and **Mobile**. Select **POSAPP** for devices not listed in Device Master.
{% endstep %}

{% step %}

### Assign a PWC\_PE TID

Select a **PWC\_PE TID** when Terminal Management is enabled. The list shows available terminals; otherwise the device uses `0001`. Create terminals before assigning them.

{% hint style="info" %}
If the Client ID is `18500010001` and the PWC\_PE TID is `0014`, transactions display Client ID `18500010014`.
{% endhint %}
{% endstep %}

{% step %}

### Name the device

Enter the optional **LANE** and **Group Name** (or select a group from **Current Groups**), then enter a **Terminal Name**. PAYware Connect creates a unique Device Key. Each transaction includes the device serial number and Device Key.
{% endstep %}

{% step %}

### Configure VeriShield and ByPass/EMV

Select **Enable VeriShield** when applicable. Select **Enable Device for ByPass/EMV** when applicable — this option appears only for accounts configured for the ByPass/EMV payment engine. ByPass has reached end of life for all processors except ADS.
{% endstep %}

{% step %}

### Set additional configuration and receipt content

Expand **Additional Configuration**, if available. Add receipt content in the **Parameters** table, if needed — you can add a disclaimer, header, or footer. Enter up to 42 characters per line in the parameter's **Value** field.
{% endstep %}

{% step %}

### Save

Select **Save** to create the device and return to Device Master.
{% endstep %}
{% endstepper %}

<details>

<summary>Keywords</summary>

Also called: add a device, new device setup, POS device master, device type, PWC\_PE TID. Search terms: new device, device master, POSAPP, payment terminal, mobile device, device key.

</details>


---

# 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://docs.verifone.com/support-us/payware-connect/device-management/store-portal-device-master/setting-up-a-new-pos-device.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.