David Siddons — fintech copywriter

How to pick a payment provider (without the typical sales spin)

Most provider guides are sales funnels in disguise. Here’s a buyer’s filter: the five checks that stop your payments from bleeding cash and customers.

When it comes to payment advice, most “how to choose” guides aren’t guides at all. They’re marketing decks in disguise, written by the very providers you’re meant to be comparing.

Which is why you get paragraphs about “seamless onboarding” and “global reach”… and nothing about the fees buried in the contract.

I’m not a provider. I’m not selling you a gateway.

I’ve just spent too many years inside fintech – watching payment companies polish their pitch and watching merchants discover what that pitch left out.

This isn’t another “top five PSPs” list. It’s a filter. Five things you’ll wish you’d asked before you signed. The fine print that blows up six months later. The clause that locks you in when you try to leave. The checkout that looks fine on desktop but leaks sales on mobile.

This is the stuff nobody tells you. Until it’s too late.

1. Costs you can actually predict

“Simple, transparent pricing.” You’ve read that line before.

In practice it means three layers of fees, a calculator you don’t trust, and a rep who tells you “it depends” when you ask what you’ll actually pay.

The basics:

And here’s the bigger problem: small merchants still get treated as second-class. A “micro” business under £2m turnover, or a “small” one under £10m, almost always pays more than the big players.

It’s not fair. But the economics are real: risk checks, onboarding, fraud monitoring. Providers spread those costs across merchants, and the smaller ones pick up more of the bill.

That doesn’t mean you’re stuck. Start with your fee model. Blended gives you one neat rate but no breakdown. Interchange++ (IC++) lays it bare – interchange, scheme fees, and the only negotiable bit: the acquirer’s margin. If you’re being fleeced, IC++ is how you’ll find out.

And here’s the blunt rule: if they can’t show you a real statement from a merchant like you, they’re hiding something.

2. Integration without migraines

Every PSP claims their docs are “developer friendly”.

Translation: they’ve published an API reference and left your engineers to figure it out.

Integration costs you twice. Once in dev hours. Again when the half-finished build leaks revenue in production.

Check for:

If a provider won’t give you an honest implementation timeline and a recent reference, assume the headaches are waiting for you.

Integration doesn’t need to be easy. It needs to be predictable.

When switching goes wrong Plenty of merchants think switching is plug-and-play. Sign Friday, live by Monday.

It never works like that.

I’ve written case studies where “one-week” migrations dragged into a month. Sandbox fine. Production a mess. Refunds stuck. Checkouts failing. Customers walking.

By the time they stabilised, the team had burned weeks of dev time and double-paid two providers just to keep the lights on.

You’ve probably seen it yourself.

That’s why the migration path matters. Dual-run, rollback, clear cutover plan. If the provider hand-waves it, you’ll be the next cautionary tale.

3. Support when it breaks

Payments never fail neatly during office hours. They fail on a weekend, late at night, when you’re nowhere near your desk.

That’s when “24/7 support” gets tested. Do you reach a human, or a chatbot that tells you to raise a ticket?

The questions to ask are simple:

This is where bargain providers show their real cost. Fees look fine until downtime hits. Then you’re the one drafting apology emails at midnight while your “lean” provider tells you to wait.

So don’t just ask “Do you have 24/7 support?”

Ask:

Who do I get when it’s 2am on a Sunday, and how long until they fix it?”

The myth of ‘set and forget’ payments

“Switch it on and forget about it.” That’s the sales line.

And it’s rubbish.

Gateways update. Scheme rules change. Fraud shifts.

The flow that worked in January can be leaking by July.

I once transcribed a podcast-style interview where a merchant described losing thousands before anyone from their payment provider noticed. Decline rates creeping. 3-D Secure spiking. Fraud filters quietly blocking good customers.

Nobody checks until the numbers dip. By then it’s already too late.

Payments aren’t plumbing. They need watching.

So if a provider sells you “set and forget”, ask them how they’ll flag problems before you do. Because if you’re the one spotting them, you’ve already lost.

4. Contract traps

The sales call is full of talk about flexibility. The contract usually isn’t.

What to watch for:

Most merchants only notice these clauses when they try to leave. By then, it’s too late.

If a provider won’t walk you through the exit terms in plain English, it’s because they don’t want you walking out.

5. Checkout your customers don’t abandon

You’re not just picking a provider for yourself. You’re picking one for your customers.

And they don’t care about your contract. They care about whether the payment clears without fuss.

Check for:

Providers brag about coverage and compliance. Buyers just want the checkout to work.

So try their demo. If you wouldn’t type your own card into it, don’t expect your customers to.

Questions your board will ask (that you should answer first)

Payment decisions usually get made in the weeds – by ops, by product, by whoever owns the checkout.

But when it blows up, it lands in the boardroom.

And the questions are always the same:

If you can’t answer those now, you’ll be answering them later with everyone staring at you.

So flip it. Ask the board-level questions first, while you still have leverage.

Final word

Picking a payment provider isn’t about chasing the lowest rate or the flashiest feature list.

It’s about predictable costs, integrations you can live with, support that actually answers, contracts you can escape, and a checkout customers don’t hate.

Get those right and payments stop being a daily worry. They just work.

Which is the whole point.

Was this post useful?

You can find more like it here. If it resonated enough to act on, you know what to do next.