> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/readme-1/process-a-basic-transaction/transactions-tendering-seq-tendering.md).

# Tender a sale using sequential tendering

If sequential tendering is enabled for the register, you can process payments for a transaction using a variety of tender types. Each payment is processed separately, in a sequence, until the full transaction amount is paid.

**To process payments using sequential tendering:**

1. Enter all of the items to the transaction.
2. Tap **Transaction** | **Tender Sale**. You can also press **F12** or **Enter**.
3. On the **Sequential Tender** screen, enter the tender amount next to the first tender type, e.g., credit card.
4. Tap **Pay**.
5. Process the payment, e.g., follow the prompts on the POS terminal.
6. On the **Tender** screen, enter the tender amount next to the second tender type, e.g., debit card.
7. Tap **Pay**.
8. Process the payment, e.g., follow the prompts on the POS terminal.

When the payment has been successfully processed, a green check mark displays beside the tender type and amount.

<div align="left"><img src="/files/DSFOqJy68ChsrvGRNu32" alt=""></div>

If the payment cannot be processed, a green check mark will not display and you will not be able to complete the transaction until that amount is paid, either by using a different credit card, debit card, or gift card, or by using a different tender type.

9. Continue to enter tender amounts next to different tender types, tap **Pay**, and process the payment until the full transaction amount is paid.

{% hint style="success" %}
If the customer is paying the remaining amount, click in the amount field next to the appropriate tender type and press **+** on the keyboard. POS automatically enters the remaining amount of the transaction for that tender type.
{% endhint %}

10. Tap **Yes** to print the receipt.

**To void payments using sequential tendering:**

Sometimes you will need to void a payment after it has been processed. For example, you might void a payment during sequential tendering if the customer realizes they used the wrong credit card or debit card.

{% hint style="info" %}
Voiding a payment during sequential tendering is different from voiding a transaction. Refer to [**Void transactions**](/readme-1/advanced-transaction-tasks/transactions-voiding.md) for more information.
{% endhint %}

1. On the **Sequential** **Tender** screen, tap the payment you want to void to select it.
2. Tap **Void**. A void request is sent to the payment processor.

When the payment is voided, the green check mark and the amount are deleted from beside the tender type. You should not have to do anything else to void the payment.

3. Tap **OK**.
4. (Optional) Repeat the steps above to void additional payments.


---

# 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.rmhpos.com/readme-1/process-a-basic-transaction/transactions-tendering-seq-tendering.md?ask=<question>&goal=<endgoal>
```

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