Payment gateways, explained without the jargon

Teams tend to reach for this after something has already gone wrong. Here is payment gateways without the vocabulary that usually surrounds it.

In e-commerce every friction point has a price attached, and the arithmetic is unusually easy to check. Check it against what you would want a competitor's site to get wrong.

The short version

Offer the methods your customers already use. In practice this is a scheduling problem more than a technical one. Budget a little time for it every quarter and it never becomes a project of its own.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. The cost of getting this wrong is rarely visible on the day it happens.

Fees differ more than the marketing pages suggest. It is worth being explicit about, because assumptions differ quietly. It is the sort of thing that looks like polish right up until it costs you an enquiry.

Where to go from here

Never store card details you do not need. The reasoning matters more than the rule, because the rule has exceptions. It is the sort of thing that looks like polish right up until it costs you an enquiry.

How to tell if yours is fine

Small percentage changes matter here because they apply to every order, every month. Three things worth confirming about payment gateways before you move on:

• Someone can say what the current setup is without going to look
• Offer the methods your customers already use — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.