eatOS
Troubleshooting Guide1 min read

Resolving Multiple Payment Attempts

Troubled by failed eatOS payments? Troubleshooting is a breeze with our guide! Discover solutions to common issues like multiple payment attempts and server errors, explained in an engaging, easy-to-understand tone. G...

Introduction

Navigating through multiple payment attempts can be a frustrating experience for both customers and merchants alike. This guide is designed to provide a clear and effective pathway to resolve such issues, ensuring a smooth and efficient transaction process while minimizing inconvenience for all parties involved.

Table of Contents

Resolving Multiple Transaction Attempts

This could potentially be related to a couple of things, such as:

_For all the above, there is a bit of ambiguity, and the resolution timeline becomes a bit hard to identify._

To start, request as much info as possible about where and which devices are experiencing the trouble and submit it as a production issue report support request using the format below. This will allow the team to get all the necessary insights and address the matter at hand for a quick resolution.

Create New Support Ticket:
Create New Support Ticket:

A few things you could do to check and advise the merchant to do are:

a. Check the payment provider's status page & subscribe to incident reports.

b. Check for Device Logs.

c. Check the networking insights (or request to have them checked) for anomalies.

d. Request the merchant to check if the network service provider is having intermittent latency or connectivity.

e. Initiate Force Stop for the application to prevent any app misbehavior. (Should that be the root cause)

f. Request a reboot of the payment terminal. (Action can vary for reboot based on device type - confirm payment terminal and advise)

g. Submit a PIR as well to have the engineering team look for deeper insights on an instance.

Back to top

Updated on: 07/03/2025

Share your feedback

Send My Feedback Cancel

Thank you!

Was this article helpful?

Back to Troubleshooting Guide