# Optimal Tap Positioning Guide

### Overview

This section provides guidelines on the best position for tapping a card on Q3-series terminals, specifically models like Q3F, which feature front contactless readers

<div align="left"><figure><img src="/files/K4pXVszWCIO1V8k3H0BT" alt=""><figcaption></figcaption></figure></div>

### App Design Considerations

Developer's Role:

* In applications designed for these terminals, developers should include prompts or guides indicating the optimal card tap position.
* This guidance is crucial to ensure users are aware of the area with the strongest antenna signal for reliable card reading

<div align="left"><figure><img src="/files/d6KlneMHq2eGgdPocgIB" alt=""><figcaption></figcaption></figure></div>

### Guidance for Optimal Tap Position

* The exact position for optimal card tapping should align with the area of highest antenna intensity in the terminal.
* Details on this position may vary based on the specific terminal model and should be confirmed with the hardware specifications.

### Important Notes

* Ensuring users tap their card at the correct spot is essential for efficient and error-free transactions.
* Developers should prioritize this feature in their app designs for enhanced user experience and transaction success rates.


---

# Agent Instructions: 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:

```
GET https://smartpossdk.gitbook.io/cloudpossdk/faq/card/optimal-tap-positioning-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
