> For the complete documentation index, see [llms.txt](https://docs.onta.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onta.network/basics/interactive-blocks/tapcore.md).
# TapCore
TapCore brings tap-to-pay functionality to standard POS terminals that merchants already use, requiring no specialized hardware. This breakthrough leverages NFC technology to translate cryptocurrency transactions into formats that existing payment infrastructure can recognize.
Beyond tap payments, TapCore also supports QR code scanning widely used in many countries. The entire payment process takes less time than a typical card transaction.
For merchants, the system integrates with standard payment workflows, minimizing operational changes while eliminating traditional interchange fees. The underlying architecture connects existing payment terminals to blockchain infrastructure through middleware that handles all the translation and routing. This bridges the gap between retail systems and crypto infrastructure, creating a pathway for mainstream adoption without requiring merchants to change their hardware or workflows.
---
# 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.onta.network/basics/interactive-blocks/tapcore.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.
