> 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-nordics/p400-two-piece-sa/errors/printer-not-working.md).

# Printer Not Working

What to do when your P400 Two-Piece isn't printing receipts properly — check and clean the receipt roll, then run a test print.

{% hint style="info" %}
**Use this page when** receipts aren't printing properly — for example, they come out jagged, don't come out at all, or the print is fainter than usual.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: printer not working, receipts not printing, no receipt, faint receipt, jagged receipt, paper jam, receipt roll. Search terms: printer, receipt, not printing, faint, jagged, paper roll, hatch, cutter, test print, receipt data, tear off.

</details>

## Symptoms

You may see one or more of the following:

* Receipts don't come out at all.
* Receipts come out **jagged** or torn.
* The print is **fainter** than usual.

**Why this happens:** the receipt roll may not be inserted correctly, or dust or bits of paper may be blocking the printer.

## Before you start

Receipts are printed by the **operator unit** — the unit at the till.

## Resolution

{% stepper %}
{% step %}

### Check the receipt roll is inserted correctly

1. Open the **hatch** on the operator unit.
2. Check the receipt roll is sitting correctly in the printer, with the paper feeding out towards the top of the hatch.
3. Make sure a small piece of paper is **sticking out**, then close the hatch.

<figure><img src="https://content.gitbook.com/content/H3VBt0P9E0VJDk5TJ2jp/blobs/2bdlOP8iZwkQODscZbuO/image.png" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Take out the roll and blow it clean

Take the receipt roll out and blow away any dust from both the **roll** and the **printer compartment**.
{% endstep %}

{% step %}

### Clear the receipt cutter

Remove any bits of paper stuck in the **receipt cutter** (the edge where the receipt is torn off).
{% endstep %}

{% step %}

### Put the roll back in

1. Insert the receipt roll into the printer.
2. Leave a small piece of paper **sticking out**.
3. Close the hatch.

{% hint style="info" %}
Need new receipt rolls? You can order them from our webshop: [webshop.verifone.se](https://webshop.verifone.se).
{% endhint %}
{% endstep %}

{% step %}

### Run a test print

1. Press **#** to open the menu.
2. Select **Receipt data**.
3. Select **Print** to print a test receipt.

✅ **Receipt prints clearly — stop here.** ❌ **Still not printing properly — contact Support below.**
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Avoid paper jams:** always tear off the receipt by pulling it **sideways across the cutter edge**, rather than pulling it straight out.

![](https://content.gitbook.com/content/H3VBt0P9E0VJDk5TJ2jp/blobs/eCXtP7M8evKfwI1RJTEV/image.png)
{% endhint %}

**If the receipt prints clearly.** Your printer is working.

**If the problem continues.** Contact Support below.

## Still not working?

{% hint style="info" %}
**Still need help? Contact Verifone Support.**

If the steps above haven't resolved the issue, <mark style="color:red;">contact Verifone Support</mark>. Tell us the troubleshooting steps you've already tried — it helps us get you to the right support faster.
{% endhint %}


---

# 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-nordics/p400-two-piece-sa/errors/printer-not-working.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.
