> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/uk-and-intl/applications/securetable/securetable-maitred-edition-for-tyro/payment-process/general-use-of-securetable-to-apply-payments.md).

# General use of SecureTable to apply payments

### General use of SecureTable to apply payments

 This section will cover the general workflow that users and customers will see when using SecureTable. The workflow will vary slightly based on the SecureTable application's configuration. The workflow steps that are user-configurable are also optional and can be skipped during the transaction process. Those will be indicated as such below.

***

### Before starting a transaction 

Before starting a transaction using a payment terminal with SecureTable, at least one check must be printed from the POS system. SecureTable can also work with split checks as well a tables with multiple checks. Open tables without printed checks cannot be accessed by SecureTable.

<figure><img src="https://content.gitbook.com/content/70eSU57m5853RfAjtrLZ/blobs/Dz3yQbPvwjgrFIyeHkrE/image.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/70eSU57m5853RfAjtrLZ/blobs/Ad8BBvI34Tx3p4KONIwx/image.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/70eSU57m5853RfAjtrLZ/blobs/lGjHvLbmhqdrCB4KomJJ/image.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/70eSU57m5853RfAjtrLZ/blobs/UQ5BvfzMb2AvMSA1WqVB/image.png" alt=""><figcaption></figcaption></figure>


---

# 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.payfacto.com/payfacto-knowledge/uk-and-intl/applications/securetable/securetable-maitred-edition-for-tyro/payment-process/general-use-of-securetable-to-apply-payments.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.