Resolving Multiple Payment Attempts

Introduction

Navigating through multiple payment attempts can be a frustrating experience, both for 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

Resolving Multiple Transaction Attempts

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

Service Provider Downtime / Maintenance
Intermittent Network Connection Trouble
Faulty Device
Direct Merchant Temporary Impact

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






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

a. Check the payment providers 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: 02/05/2024