> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.eatos.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Rectifying Double Payment Incidents

### Introduction

Encountering duplicate payments within your eatOS system can be frustrating, but rest assured, we're here to guide you through the resolution process. This article provides a step-by-step guide to help you navigate and resolve the issue seamlessly.

### Table of Contents

* [ **Resolving Duplicate Payments** ](#3-resolving-duplicate-payments) 

---

### Resolving Duplicate Payments

**Step 1: Gather Important Details**

Start by collecting essential information related to the incident. Make sure you have the following particulars on hand:

* The station where the duplicate payment occurred.
* The last four digits of the card are used for the transaction.
* The order number associated with the payment.

|| **Note: If you don't have access to the last four digits of the card, you can cross-reference the total amount with the transaction logs available through the processor portal. Use the transaction time and total amount for verification.**

**Step 2: Initiate a Support Ticket**

**To get started with resolving the duplicate payment, follow these steps:**

1. Log in to your eatOS account.
2. Navigate to the support section.
3. Click on **"Create New Support Ticket."**

![Create New Support Ticket:](https://storage.crisp.chat/users/helpdesk/website/74260be74e639800/image-2_xl8no6.png)
             
4. Provide all the gathered information about the duplicate payment.
5. Verify the details and submit the support ticket.

Once you've furnished the necessary information and verified the duplicate payment, your request will be escalated to our development support team for resolution. Our team is dedicated to ensuring a prompt and satisfactory outcome for you.

|| **Note: Please be aware that instructions may undergo updates over time. For the most up-to-date guidance, refer to the latest documentation provided, or feel free to reach out to our dedicated support team.**


[Back to top](#3-introduction)