The Human Side of Payments: As Payments Scale and Automate, is Merchant Service Keeping Up?

Executive Summary

But they raise a different question for merchants: as the organization behind their payments changes structurally and technologically, is merchant service keeping pace?

This report investigates what consolidation, restructuring and automation could mean for continuity, responsiveness and the human knowledge merchants receive from their payment provider. It examines five specific implications and what the evidence suggests about merchant need.

The findings suggest this is worth examining closely.

1. The payments industry is consolidating and restructuring

Between July and August 2026 alone, Windsor Drake Research identified significant M&A activity across the payments sector, with major transactions reshaping the competitive landscape. Simultaneously, BCG's 2026 research describes AI adoption across payment-company functions including onboarding, underwriting, fraud, disputes, servicing and operations.

The trend is clear: consolidation is happening, automation is expanding, and operating models are evolving alongside them.

For merchants, these changes create a practical question: during this transformation, does the relationship remain continuous, responsive and informed?

To answer that, consider what these structural changes could actually mean.

2. Losing an established point of contact

This is not inherently problematic. Team change happens in every organisation.

The question is how knowledge and accountability move with that change. Does the new contact have access to the merchant's history? Can they answer questions about why previous decisions were made?

When consolidation happens quickly, or when cost reduction follows acquisition, the gap between "the person leaves" and "someone else knows what they knew" can be substantial.

For merchants, this can mean having to rebuild context with a new contact on issues where continuity matters.

3. New teams having to relearn the merchant and its business

Some of this may be documented. Some may exist only in email chains, old notes or the departing contact's memory. Some may not be recorded anywhere.

Relearning takes time. During that period, the merchant may experience slower problem-solving, repetitive questions and decisions made without full context. The team is essentially starting from the contract and working backwards, rather than starting from the relationship and working outward.

For merchants, this transition period is where maintaining service continuity can become particularly important.

4. Longer response and feedback times

Where restructuring results in broader account coverage or fewer people handling escalations, this can mean less time per account and longer response queues.

For merchants, responsiveness is not a nice-to-have. It is a primary driver of whether they stay.

5. Overloaded teams creating friction internally

A new onboarding workflow may require human checking where exceptions or edge cases arise. Integration issues may also require investigation where an automated process does not operate as expected. During a transition period, teams may therefore need to manage both new automated processes and cases that continue to require human intervention, which can create additional operational pressure.

For merchants, this can mean delayed responses on issues where human expertise is precisely what's needed.

6. Immature automation creating friction

These potential implementation challenges mean that the benefits of automation may not always be immediate. During a transition period, some cases may continue to require human verification or intervention while processes are refined. For merchants, this makes the quality of the transition important: where automated processes require additional human intervention, continuity and responsiveness remain relevant alongside the efficiencies the technology is intended to deliver.

7. So what could this mean for continuity, responsiveness and human knowledge?

1. 1.A merchant loses their established contact.
2. 2.The new team has to relearn the business.
3. 3.Meanwhile, the team is carrying heavier workloads because consolidation reduced headcount.
4. 4.A new automation system has just rolled out and is creating false positives, requiring human checking.
5. 5.Questions now take longer to answer.

Where these implications occur together, they can compound each other and test the resilience of the merchant relationship.

When asked what could trigger a review, merchants cited:

Cost is the most common trigger, particularly amongst smaller merchants. But technical issues and support sit alongside price as significant reasons merchants could reconsider their provider.

KAE identified other current frustrations including slow or unreliable settlement, integration difficulties, fraud and chargeback issues, and system downtime.

And the merchant's requirements are not fixed either.

In short: merchants need their providers to do two things simultaneously, a) handle the current relationship with continuity and responsiveness, and b) adapt as requirements change.

If consolidation and restructuring reduce continuity and responsiveness precisely during the period when merchants most need consistency, the provider is being tested under stress.

8. The handoff is where the system breaks

For routine requests, automation can work well. An automated onboarding process, automated fraud checks, automated settlement, these can be efficient when everything follows the standard path.

A business model changes. An integration behaves unexpectedly. Requirements span several markets. A technical problem needs investigation. A merchant has an unusual payment setup and the automated system doesn't know how to handle it.

At that point, the question is not whether automation has failed. It is what happens next.

This is consumer research, not merchant research. But it illustrates a broader principle: automation and access to people can complement each other. The gap is the handoff.

For payment providers, the critical moment is when an issue moves from the automated system to a human. Information already provided should move with the issue. Ownership should remain clear. The next person should have context, not force the merchant to start again.

A handoff that forces the merchant to explain their situation twice is technically an escalation. It is not continuity.

And if the next person is overloaded, new to the account, or learning on the fly because the account knowledge didn't transfer, the handoff breaks under pressure.

Conclusion: Service architecture matters as much as technology