> For the complete documentation index, see [llms.txt](https://ftcoders.first-tech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ftcoders.first-tech.com/first-tech-ttp-sdk/best-practices-for-handling-the-device.md). # Best Practices for Handling the Device ### **Identify the Location of the NFC Chip on Your Device** Failures in Tap to Phone transactions are often caused by delays in positioning the card correctly on the device. The NFC chip location varies between manufacturers and models, and identifying the ideal zone can prevent this issue. Tips for locating the NFC chip: * Check the mobile device's user manual, which often includes a diagram indicating the physical location of the NFC chip (front, back, or top). * Test in a staging environment by tapping the card while the application is in test mode. * Listen to the sounds emitted by the application, which distinguish between successful and unsuccessful taps. * Move the card calmly, without abrupt movements, until you find the ideal position. Test both sides (front and back). This practice helps minimize failures, ensuring fast and efficient transactions in production environments. ### **Disable the Phone’s Battery Saver Mode** Android's battery saver mode can terminate background processes or restrict power allocation to the NFC chip, reducing its efficiency and range. This may cause failures in terminal creation, session setup, or card reading during tap transactions. We recommend disabling this function during the process to ensure proper device operation and maintaining a good battery level to avoid interruptions. ### **Stay on Wi-Fi and Avoid Using the App During Network Changes** A stable connection is essential for payment data exchange and receipt transmission. To ensure successful transactions, avoid using the application in situations that affect radio signal propagation, such as: * Entering or exiting elevators, buildings, or construction sites. * Moving into shadow areas (Wi-Fi/4G dead zones). * Traveling or transitioning between different network coverage areas. Remain still next to the customer during the transaction to prevent network fluctuations or switches that could interfere with payment processing and authorization. --- # 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://ftcoders.first-tech.com/first-tech-ttp-sdk/best-practices-for-handling-the-device.md?ask=&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.