How to choose a payment gateway.

Shopping for card acceptance means running into three words that get used interchangeably but aren't the same thing: gateway, processor, and merchant account. Getting the distinction straight is the first step to choosing well, because a good gateway decision touches everything downstream — how cards are secured, what you can do with them, and how much each sale costs.

Gateway vs processor vs merchant account

Think of a card transaction as a relay:

• The gateway is the software that securely captures a transaction — at a terminal, on a website, or in a virtual terminal — and transmits it for authorization, then relays the answer back. It usually also handles encryption, tokenization, recurring billing, and reporting.
• The processor routes the transaction through the card networks and moves the money.
• The merchant account is the account that receives your funds.

Many businesses buy all three as a bundle, and that's fine — but knowing they're separate roles helps you ask sharper questions and spot where cost and lock-in hide. A gateway that's tightly integrated with your processing and boarding, run by one accountable team, is usually simpler than stitching a standalone gateway onto a third-party processor.

The features that actually matter

Feature lists are long; the ones that change your day-to-day and your bill are short.

1. Security: E2EE and tokenization

This is non-negotiable. The gateway should end-to-end encrypt the card at capture and store it only as a token, so the clear card number never touches your systems. Beyond protecting you from a breach, it's what keeps your PCI scope small — see tokenization and SAQ-A compliance. Tokenization is also what powers cards on file, recurring charges, and refund-after-settlement.

2. The ways you actually sell

Match the gateway to your real channels. Do you need card-present acceptance on a terminal like the PAX A920? A virtual terminal for phone orders? Cards on file and recurring billing? Online checkout? A gateway that only does one channel forces you to bolt on others later.

3. Level 2/3 optimization

If any customers pay with business, corporate, purchasing, or government cards, the gateway's ability to append Level 2/3 data automatically can meaningfully lower interchange on those cards. Most gateways don't do this well — it's a real differentiator for B2B sellers (see B2B credit card processing).

4. ACH and eCheck

If you invoice or take large-ticket or recurring payments, bank-to-bank ACH/eCheck is often far cheaper than cards. A gateway that supports both card and ACH rails lets you route each payment to the cheaper one.

5. Reporting, reconciliation, and support

You'll live in the reporting. Clear batch reconciliation, volume and refund visibility, and exportable records save hours. And when something breaks mid-day, real human support beats a ticket queue. These "boring" factors often matter more than any single feature.

The questions that reveal the real cost

• Is pricing interchange-plus, with the markup itemized? If they won't show the split, that's your answer — see interchange-plus vs flat-rate.
• What are all the fixed fees? Gateway monthly fee, per-transaction fee, PCI fee, statement and batch fees. Add them into an effective rate.
• Is there a contract or early-termination fee? Lock-in is how a bad rate survives.
• Who owns the whole relationship? Gateway, processing, boarding, and support under one team is fewer finger-points when something goes wrong.

How Lifted Payments is set up

Lifted runs card processing on the Maverick gateway and ACH/eCheck on the NMI gateway, with automatic Level 2/3 optimization on commercial cards and E2EE tokenization via Voltage. It's the same routing layer under Lifted Pay, Lifted POS, and the merchant portal — so card-present, virtual terminal, cards on file, ACH, and reporting all live in one place, boarded and supported by one team. Pricing is interchange-plus, quoted after we read one recent statement, with no application fee.