> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/transit-digitization/get-started/concepts/integration-models.md).
# Integration Models
### Account Based Ticketing (ABT)
ABT systems rely on a central server to store the most accurate and up-to-date information about riders financial and travel records. In this model, the ABT server is the authoritative source of information, and the digital card serves as a mean to access the transit network.
When riders use their digital cards to access the transit network, the system communicates with the ABT server to verify riders information, such as their balance or account status.
### Card Based Ticketing (CBT)
CBT systems operate by storing the most accurate and up-to-date information about riders financial and travel data directly on the physical or digital card. In this model, the card itself contains all the relevant information needed for transactions.
When riders use their digital cards to access the transit network, the system reads the data stored on the card, such as the balance or recent travel history. After the transaction, the updated information, the new balance or a record of the trip, is written onto the card.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.payments.thalescloud.io/transit-digitization/get-started/concepts/integration-models.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.