---
title: "Acquirer Failure Contained in Seconds: Case Study"
description: "eComCharge support spotted an acquirer slowing to 30-second responses on platform monitors and isolated it through the interface in seconds, no outage, no client ticket."
url: "https://ecomcharge.com/case-studies/acquirer-failure-contained/"
lang: "en"
date_published: "2026-04-01"
last_updated: "2026-04-01"
author: "eComCharge"
image: "https://ecomcharge.com/static/assets/img/og-default.859636851186.png"
breadcrumbs: "Home > Case Studies > Acquirer failure contained in seconds, before a single merchant noticed"
---

Case study 03

# Acquirer failure contained in seconds, before a single merchant noticed

eComCharge support spotted an acquirer slowing to 30-second responses on platform monitors and isolated it through the interface in seconds, no outage, no client ticket.

[Request a demo](https://ecomcharge.com/contacts/sales/)

Low-risk
Platform stability
Proactive monitoring

**Seconds**
Time to isolate
Acquirer disabled via the interface, no engineering sprint

**0**
Downtime
Traffic redirected through other channels

**0**
Merchants affected
The failing acquirer stayed a local issue

At a glance

## How a PSP Contained an Acquirer Failure in Seconds, Before It Became a System Outage

Client
:   A low-risk PSP processing high transaction volumes across e-commerce and financial services merchants

Challenge
:   One acquirer degrading: response time 30 s+, queues growing, failover slowing down: an outage could reach every merchant

Solution
:   Proactive monitoring + acquirer isolation via the platform interface

Result
:   Issue detected and isolated in seconds: zero system outage, zero client ticket required

Segment
:   Low-risk PSP

Trigger
:   Response time 30s+

Detected by
:   eComCharge support monitors

Published
:   April 2026

Solution used

[Smart Routing](https://ecomcharge.com/platform/smart-routing/)

Names protected by NDA. Numbers as reported by the client or confirmed by platform data.

Challenge

## One acquirer slowed to 30 seconds per response.

One of the acquiring partners began experiencing severe performance degradation: response times increased to 30 seconds or more, and the effect spread through the whole platform.

**30 s+** Response time of the degraded acquirer, against a normal of about one second.

Even a single unstable acquirer can affect the entire system if not isolated in time.

Case study 03

### Queues built up

Transactions waited for a partner that answered in 30 seconds or more.

### Resources overloaded

Waiting requests held system resources that other traffic needed.

### Failover slowed down

Switching to alternative channels became less effective as the load grew.

Solution

## Detected on our monitors, isolated in seconds.

The eComCharge support team detected the degradation directly on platform monitors, without waiting for the client to raise a ticket.

Once confirmed, the acquirer was isolated through the interface in a matter of seconds. The decision is made by the support team in real time, with an on-call engineer available for confirmation.

Slow but alive

Increase queue depth to handle more parallel requests: the partner keeps processing while the load is managed.

Unresponsive

Disable it completely and redirect traffic to stable channels immediately.

What changed

## A local issue stayed local.

Instead of allowing a single failing partner to degrade the entire system, the issue was contained at the source. Traffic continued to flow through other available channels without creating system-wide bottlenecks.

Without isolation

- Slow acquirer keeps receiving trafficQueues grow uncontrollably
- System resources exhaustedPlatform-wide performance degrades
- Failover becomes less effectiveMerchants start seeing failures

With isolation

- Problem detected on support monitorsBefore client escalation
- Acquirer disabled via interface in secondsTraffic redirected instantly
- System stays stableA local issue stays local

Step 1

### Monitors detect the slowdown

Response time and queue depth visible in real time.

Step 2

### Slow or dead?

Slow: increase queue depth. Unresponsive: disable completely. On-call engineer if needed.

Step 3

### Isolation via interface

A few seconds. Traffic continues through stable channels, no client action required.

When it matters

## When acquirer isolation becomes critical.

System performance depends on external providers. When one of them starts responding slowly or becomes unstable, queues grow and failover between channels becomes less effective.

### Disable without stopping

Temporarily switch off unstable acquirers without stopping the entire system.

### Protect core traffic

Redirect payments to stable channels while the partner recovers.

### No business outage

Keep a technical incident from turning into a business outage.

What if you only have one acquirer?

This scenario is more common than it seems. Continuing to send traffic to a slow or unresponsive acquirer can overload the system: queues grow uncontrollably, and platform-wide performance degrades.

In one real case, the PSP had only one active acquiring partner at the time. Disabling it did not stop the business; it prevented the entire system from becoming unresponsive.

Temporarily disabling it helps

- Protect system stability
- Prevent resource exhaustion
- Buy time to resolve the issue without escalating the incident

Results

## Low-risk PSP · High transaction volume · Acquirer degradation incident

**Seconds**
Time to isolate
Acquirer disabled via the interface, no engineering sprint required

**✓ Proactive**
Detected by eComCharge
Support monitors flagged the issue before the client reported it

**0 downtime**
No system outage
Transaction flow maintained throughout the incident

**✓ Contained**
Local issue stayed local
One failing acquirer did not affect the rest of the platform

The support team doesn't wait for a client ticket. **Response time and slowdowns are visible on eComCharge monitors**, and when action is needed, isolation takes seconds, not minutes.

Case study 03

## Want a similar setup on your platform?

Tell us about your traffic, acquirers and merchants. We will show you how the same approach would work for you.

[Talk to us](https://ecomcharge.com/contacts/sales/)
