Gateway vs processor vs PSP

Why the terminology matters

Gateway, processor and PSP describe three different jobs in a single payment. Conflating them is how merchants end up with the wrong contract, surprise fees, or a provider that can't actually support their category. Here's each role in plain terms.

The three roles

How a payment actually flows

1. The customer enters card details — the gateway captures and tokenizes them.
2. The processor sends the authorization through the card network to the issuer.
3. The issuer approves or declines; the answer returns the same path in milliseconds.
4. Later, the processor batches captured transactions for clearing.
5. The acquirer settles funds (minus fees and any reserve) to your bank.

Why it matters when you’re high-risk

Generalist PSPs that aggregate thousands of merchants onto a shared account move fast for low-risk businesses — but their model is to drop anything that looks risky, often freezing funds first. High-risk merchants are usually better served by a dedicated merchant account with a specialist acquirer, fronted by a gateway and an orchestration layer that can route across many acquirers.

Where MIDs fits

MIDs provides the gateway and an orchestration layer on top of direct relationships with 30+ acquiring banks — so you get one integration, but real merchant accounts underwritten for your vertical and intelligent routing across all of them.