Skip to content
All insights
Payments2 Sept 20265 min read

Acquiring is a servicing business, not a gateway

Merchants rarely leave an acquirer because a transaction failed. They leave because the exception was never resolved.

Acquiring is frequently evaluated as a technical capability: can it authorise, can it capture, can it settle. Those are entry requirements. What differentiates an acquirer over time is how it handles everything that does not go to plan.

The visible part

Acceptance, authorisation and settlement are the product surface. A gateway integration, a terminal estate and a settlement report are the things a merchant sees. They matter, and they are increasingly commoditised.

The part that decides retention

  • Onboarding. How long does it take, what is asked for, and who explains why? A slow or opaque process loses good merchants before the first transaction.
  • Declines. Are they explained? A merchant who understands why a transaction failed can fix the cause; one who receives a generic code cannot.
  • Chargebacks. Deadlines are unforgiving. The difference between an acquirer with a workable evidence workflow and one without is measured in recovered revenue.
  • Settlement breaks. When a batch does not reconcile, who investigates and how quickly? This is where finance teams form their opinion of a provider.
  • Pricing clarity. Fees that appear without explanation erode trust faster than high fees that are understood.

What this means for platforms

A platform adding acceptance should decide early how much of the servicing it will own. Taking payments is straightforward; resolving the consequences of taking payments is an operating function. Merchants will route their questions to whoever sold them the capability, regardless of where the processing sits.

That means the servicing model — hours, escalation paths, evidence handling, reconciliation support — should be designed as part of the product, not assembled after launch.

Questions worth asking an acquiring partner

  • What does onboarding actually require, document by document?
  • How are declines explained to the merchant, and in what detail?
  • Who owns chargeback evidence, and what tooling is provided?
  • What happens on a settlement break, and within what timeframe?
  • Which fees are pass-through, and how are they shown on reporting?

Acquiring is a long relationship built on operational competence. The gateway gets you the first transaction. The servicing keeps the merchant.

This note is general commentary and does not constitute legal, regulatory or investment advice. Specific permissions and obligations depend on your business, jurisdiction and the institutions involved.

Next step

Let's talk business.

If this raises a question about your own proposition, we are happy to discuss it.