What Is a Payment Gateway Fee?

If you take payments online, over the phone, or through an invoice link, you're almost certainly paying a payment gateway fee. It's the charge for the piece of software that carries a card-not-present transaction from your website or keypad to the processor. It rarely shows up as one big number. It's usually a small monthly fee plus a few cents a transaction, and that's exactly why most owners never look at it twice.

This guide covers what a gateway does, how a payment gateway fee is usually structured, where to find it on your statement, and when it's worth pushing back.

What a payment gateway actually does

When a customer swipes, taps or dips a card at your counter, the terminal talks to the processor directly. When there's no physical card in front of you, something else has to do that job. That something is the gateway.

It sits between wherever the card number gets typed in and your processor. That could be:

• A checkout page on your website or online store
• A virtual terminal, where your staff keys in a card number on a computer
• An invoicing or billing tool that sends customers a "pay now" link
• Recurring billing, where a card on file gets charged every month

The gateway encrypts the card data, sends it off for approval, and returns the answer. Most also store cards for repeat billing and give you a dashboard for lookups and refunds.

How a payment gateway fee is structured

There's no single standard. But almost every gateway bill is built from some mix of these pieces:

• Monthly gateway fee. A flat charge for having the gateway turned on, whether you run one transaction or a thousand.
• Per-transaction gateway fee. A few cents on every authorization. This one sits on top of your normal processing fees, not instead of them.
• Setup fee. A one-time charge to open the gateway account. Plenty of providers skip it.
• Add-on fees. Separate charges for extras like recurring billing, stored cards, fraud screening, or extra user logins.

The per-transaction piece is the one to watch. A few cents sounds like nothing. But it applies to every authorization, and depending on the setup that can include declines, voids and refunds, not just completed sales. If you run a lot of small tickets, those cents add up faster than the monthly fee does.

Where it hides on your statement

Sometimes the payment gateway fee comes from your processor and shows up on your merchant statement. Sometimes it comes from a separate gateway company and gets billed to a credit card or bank account on file. That second setup is easy to forget about, because it never appears next to your other processing costs.

On a statement, look for lines like:

• Gateway fee or gateway monthly
• Gateway transaction fee or gateway per item
• Internet or e-commerce access fee
• Virtual terminal fee
• Authorization fee (this can be the gateway's per-transaction charge, or the processor's own, or both)

If you see two different per-transaction charges for the same online sale, one from the processor and one from the gateway, you're paying two layers. That isn't automatically wrong, but you should know about it.

When the payment gateway fee is a problem

For a business doing real online volume, a gateway is a normal cost of doing business. It becomes a problem in a few situations:

• You're paying for a gateway you don't use. You set up a virtual terminal years ago, keyed in a handful of cards, and the monthly fee has been running ever since. This one is common, and it's the easiest to fix.
• You're paying for two gateways. A business switches software or adds an online store and ends up with a second gateway while the first one keeps billing.
• Your per-transaction fee is out of line with your ticket size. If your average sale is small, a per-item gateway charge eats a bigger share of every dollar.
• The fee was bundled in and never itemized. Some providers fold the gateway into a higher markup instead of listing it. You're still paying for it. You just can't see it.

One more thing worth knowing. Card-not-present transactions usually carry higher interchange than card-present ones, because the networks see more fraud risk when the card isn't physically there. If you can take a payment in person instead of keying it in, it's often cheaper even before the gateway comes into it.

What you can do about it

• Find every gateway you're paying for. Check your merchant statements and any separate bills from software or gateway companies. Cancel anything you're not using, in writing.
• Ask for the fees in writing. Monthly, per-transaction, and add-ons, line by line. If the answer is "it's bundled," ask what the markup would be without it.
• Negotiate the per-transaction piece. If you run steady online volume, this is often the easiest number to move. A lower monthly fee doesn't help much if every sale carries an extra charge.
• Check whether your processor includes one. Some processors include a gateway with the merchant account at no extra monthly cost. If yours doesn't, ask.

The bottom line on payment gateway fees

A payment gateway fee is rarely the biggest number on your statement. But it's one of the easiest to leave running for no reason, or to get billed for twice. Pull your last statement and run your effective rate: total fees divided by total card sales. Our free rate checker does the math for you in a couple of minutes. If the number looks high, send over one statement and we'll go through every line with you, gateway fees included. No rush, and nothing out of your pocket either way.

This is general information, not legal advice; surcharging rules change and vary by state.