> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/pos/order-creation/checkout/payments/payment-types/card-payment.md).
# Card Payment
Card payments can be processed with either an integrated card payment or a non-integrated card payment.
## Integrated Card Payment
When a card terminal is integrated with the POS system, the two devices communicate directly. Once you select the card payment method on the POS, the exact amount is automatically sent to the terminal without the need to key it in manually. Once the customer completes the transaction on the terminal, the POS system is **automatically updated**, streamlining the checkout process and reducing the risk of manual errors.
> If a terminal that's supposed to be connected is not communicating due to a technical issue (such as Wi-Fi disconnection), a **"Force payment"** option will appear. In this case, you can proceed with **Force payment** to manually finalize the payment process.
## Non-Integrated Card Payment
In a **non-integrated** setup, selecting the **Card** payment method on the POS will **not attempt any device connection**. Instead, the system will **immediately register the payment**, functioning similarly to how a cash payment is recorded.
---
# 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.bossithq.com/pos/order-creation/checkout/payments/payment-types/card-payment.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.