Case study 04

Performance crisis resolved in days, without scaling the entire infrastructure

One high-volume merchant was degrading a whole PSP platform. Two dedicated servers and an 80/20 traffic split restored 7-second processing in days, instead of a 2–3× infrastructure upgrade.

Low-risk SaaS Dedicated infrastructure
7 sec Processing time Back to normal, queue wait time eliminated
2 servers vs a 2–3× upgrade Only what was actually needed
Days Time to resolve Configured and deployed while the issue was active
At a glance

How a PSP Solved a Performance Crisis Without Doubling Its Infrastructure

Client
A low-risk PSP working with e-commerce and financial services merchants, including several high-volume clients
Challenge
One large merchant's load pushed processing time up for everyone on the shared pool; a full infrastructure upgrade looked like the only way out
Solution
Dedicated server allocation for a high-volume merchant: 80/20 traffic split
Result
Processing time returned to normal · no infrastructure scaling required
Context

Dedicated capacity without leaving SaaS.

The PSP operates on eComCharge’s SaaS payment platform: a shared cloud environment where infrastructure resources are pooled across all tenants.

In a typical SaaS model, dedicated infrastructure per merchant is not an option, and one client’s load can affect everyone else. eComCharge allows PSPs to allocate dedicated infrastructure at the PSP level and at the individual merchant level, without migrating to on-premise.

Shared by default

Resources are pooled across all tenants of the SaaS platform.

Dedicated when needed

Servers can be allocated per PSP or per individual merchant.

Same environment

No migration to on-premise and no separate installation.

Challenge

One merchant took most of the shared resources.

A large merchant pushed significant traffic through the platform and consumed the majority of shared system resources. The result was complaints from two directions at once.

Before: one shared pool
80% Share of the shared resources taken by one large merchant.

The problem was not a lack of total capacity. It was a lack of isolation.

Case study 04

The large merchant

Reported increased response times.

Smaller merchants

Started experiencing degradation on the same platform.

Solution

Two dedicated servers instead of doubling everything.

The obvious fix would have been to scale up the entire PSP infrastructure by 2× or 3×. That would have meant paying for resources nobody else needed: all other merchants performed fine before this happened.

Instead, the eComCharge team allocated two dedicated servers for the high-volume merchant, at a fraction of the cost of a full upgrade.

After: traffic split
2–3× Alternative: a full infrastructure upgrade, expensive and unnecessary for the actual problem.
2 Dedicated servers for one merchant. Problem solved within days, at a fraction of the cost.

The configuration is done manually: the eComCharge team assesses the merchant’s traffic patterns and needs, then sets up the routing split. When the issue is already active, this is completed within days.

When this matters

For any PSP with a varied merchant mix.

The larger the portfolio and the more varied the merchant mix, the more likely this situation becomes, regardless of risk profile or vertical. The allocation is a managed configuration by the eComCharge team, not a self-service feature, and can be deployed quickly when needed.

Isolate the largest

Move the most demanding merchants out of the shared environment.

Guarantee capacity

Reserve processing capacity without over-provisioning for everyone.

Protect the rest

Keep one merchant’s load from degrading the experience for others.

Enterprise SLAs

Support service agreements with specific performance commitments.

Typical triggers
A high-volume merchant slows others down Performance guarantees for top clients Scaling everything would cost too much Guaranteed throughput in the contract
Results

Low-risk PSP · eComCharge SaaS · Dedicated merchant infrastructure

7 sec Processing time restored Back to normal: queue wait time eliminated
2 servers Instead of 2–3× upgrade Proportional solution: only what was actually needed
✓ All merchants Performance restored across the board Large and small merchants both benefited
Days Time to resolve Configured and deployed quickly while the issue was active

The problem was not a lack of total capacity; it was a lack of isolation. eComCharge supports dedicated infrastructure per merchant within a shared SaaS environment: something most payment platforms do not offer.

Keep reading

More case studies

All case studies
Case study 04

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.