> 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.

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2FbKdg5JrdHbzTvkNT9kPn%2Fimage.png?alt=media&amp;token=7f09a764-d99b-4bee-bb8d-54f020ecefbd" alt=""><figcaption></figcaption></figure>

## 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bossithq.com/pos/order-creation/checkout/payments/payment-types/card-payment.md?ask=<question>&goal=<user_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.
