> 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-denmark/cm5p/vejledninger/sadan-tester-du-chipkortlaeseren.md).

# Sådan tester du chipkortlæseren

Kør kortlæsertesten på en CM5P-terminal for at kontrollere, at chiplæseren virker.

{% hint style="info" %}
**Brug dette, når** du skal kontrollere, om chip- (kort)læseren på en CM5P-terminal virker, ved at køre den indbyggede test af kortlæseren.
{% endhint %}

## Kør kortlæsertesten

{% stepper %}
{% step %}

### Åbn appstarteren

Stryg ned på betalingsskærmen fra toppen, og tryk derefter på **9-boks-gitteret** symbolet øverst ved siden af Wi-Fi-ikonet.

<figure><img src="https://2708971099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fa0qV9Wx6LdSaDc8JrEef%2Fuploads%2FGzCVTs965NlOZZhJ5MWm%2Fchip-slide-down.png?alt=media" alt="Stryg ned fra toppen" width="180"><figcaption></figcaption></figure>

<figure><img src="https://2708971099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fa0qV9Wx6LdSaDc8JrEef%2Fuploads%2FstL1Jd1I8SZT8DhhDMZl%2Fchip-launcher.png?alt=media" alt="Appstarteren" width="180"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Åbn Diagnostik

Vælg **Diagnostik**.

<figure><img src="https://2708971099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fa0qV9Wx6LdSaDc8JrEef%2Fuploads%2FormcBX9cfdOIxZGCx7Yg%2Fchip-diagnostics-menu.png?alt=media" alt="Diagnostik-menuen" width="180"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Åbn kortlæsertesten

Rul ned, og vælg **Kortlæsertest**.

<figure><img src="https://2708971099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fa0qV9Wx6LdSaDc8JrEef%2Fuploads%2F1pfRkORiqlV7SCF9I4tE%2Fchip-card-reader-test.png?alt=media" alt="Kortlæsertest" width="235"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Se resultatet

Testen viser, om kortlæseren virker.

{% hint style="info" %}
Du skal indsætte et kort for at kontrollere dette.
{% endhint %}

<figure><img src="https://2708971099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fa0qV9Wx6LdSaDc8JrEef%2Fuploads%2FFxWj1I7yGwAzAwzABdCP%2Fchip-test-result.png?alt=media" alt="Resultat af kortlæsertesten" width="240"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Hvis testen viser, at chiplæseren ikke virker, se [Registrerer ikke indsatte kort](/support-denmark/cm5p/fejl/registrerer-ikke-indsatte-kort.md) for at rengøre læseren og om nødvendigt arrangere en udskiftning.
{% endhint %}

<details>

<summary>Nøgleord</summary>

Også kaldet: test af kortlæser, test af chiplæser, chiptest. Søgetermer: chiplæser, kortlæser, test, diagnostik, chip, læsertest.

</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-denmark/cm5p/vejledninger/sadan-tester-du-chipkortlaeseren.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.