# Architecture
The architecture defines a layered platform structure for the TokenOS system.\
At the base lies the **OS**, providing the fundamental operating environment. Above it, the **TokenOS Platform** is organized into three main service domains:
* **System** (Device Services, KMS Service, RKL Service),
* **Fiscal** (Fiscal Service),
* **Payment** (Card Service for EMV).
On top of the platform, the **App Layer** hosts applications such as the **Token Launcher**, **ATMS**, **ECR/Sale App**, **Payment Gateway**, and **Payment Native Apps**, interacting with the underlying services.
Externally, through secure network connections, the platform integrates with higher-level systems:
* **Token POS Services** (e.g., ATMS, RKL),
* **Token X Services** (e.g., Connect, Store, Fiscal Cloud, Maestro),
* **Payment Services**.
These services are orchestrated and managed centrally by the **Token TSM** (Trusted Service Manager), enabling secure management and communication between the device-side platform and external ecosystems.
---
# 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://developer.tokeninc.com/token-developer-portal-1/payment-service/architecture.md?ask=
```
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.