Payment gateways for online stores, explained

On Tuesday a customer paid you. On Thursday a slightly smaller number arrived in your bank account, and nothing anywhere explained either the gap or the two days.

Both are products of a chain of four or five separate companies that each took a slice and each had a reason. Understanding payment gateways for online stores is mostly understanding who those companies are, because once you can name them the fee stops being a mystery and becomes a list.

The short version: a gateway moves the card details, a processor moves the money, a merchant account holds it briefly, and the card networks and the customer's bank set most of the price. Your "rate" is a stack of charges from different parties, only some of which anyone will negotiate with you.

No rates appear in this post. Pricing changes constantly and varies by country, card type and business, so a figure quoted in a blog post is usually wrong by the time you read it. Read your own statement instead; the sections below tell you what you are looking at.

What happens in the three seconds after "Pay"

Authorization. The gateway encrypts the card details and passes them, through a processor, to the card network, which routes them to the bank that issued the card. The issuing bank decides yes or no — balance, fraud rules, address checks — and sends the answer back. This is the part the customer waits for.

Nothing has moved yet. An authorization is a hold on the customer's available balance, not a payment.

Capture. You tell the processor to actually take the authorized amount, usually automatically at the point of sale, sometimes later if you ship before charging. Authorizations expire, which is why an order left uncaptured for days can fail even though it "went through".

Clearing and settlement. Overnight, the card networks net up who owes whom and the funds move between banks. This is the stage that costs the calendar days.

Payout. Your provider sends the settled money, minus fees, to your bank on its own schedule — daily, every couple of days, weekly, or on a rolling delay if your account is new or considered risky.

So the two-day gap is settlement plus payout schedule, not anyone sitting on your money for sport.

Gateway, processor, merchant account: who does what

These three words get used as synonyms in marketing copy and they are three different jobs.

That last row is what nearly every small store uses, and it is usually the right choice. A payment service provider lets you accept cards in an afternoon without being individually underwritten. The trade is a published blended rate rather than a negotiated one, and an account under someone else's umbrella — which matters when we reach holds.

The anatomy of a fee

When you see one percentage on your statement, it is a blend of these.

Two consequences of that table are worth stating plainly.

The largest slice is not your provider's. Interchange goes to the bank that issued the customer's card and is set by the card network, which is why a premium rewards credit card costs you more to accept than a basic debit card, for identical goods, on the same day. Your provider is the party you can argue with and usually not the party taking the most.

Fixed per-transaction fees dominate small baskets. A flat amount per transaction is almost invisible on a large order and a serious tax on a small one. If your average order is small, the fixed component matters more than the percentage, and that is the number to compare between providers.

Why two stores pay different rates for the same card

Because price depends on risk and on data. A card physically present is cheaper than one typed into a website. A transaction where address verification passes, the card is enrolled in the network's authentication scheme and the merchant category is low-risk costs less than one where none of that holds.

Category matters too. Businesses with high dispute rates — event tickets, long-lead custom orders, subscriptions — are priced for the disputes they generate, whether or not yours does.

Chargebacks, and why they are not refunds

A refund is you deciding to return money. A chargeback is the customer's bank taking it back without asking you first.

The sequence: the cardholder disputes the charge with their own bank; the bank provisionally pulls the funds from your account and usually adds a dispute fee; you get a window to submit evidence — this is called representment — and the issuer decides. Winning gets you the money back. The fee usually stays gone either way.

Then there is the part that catches people out. Your dispute ratio, roughly disputes divided by transactions, is monitored by the card networks and by your provider. Cross their thresholds and the consequences escalate from warnings to higher pricing, to a rolling reserve where a share of your revenue is held back, to the account being closed. For a small store, the reserve is the dangerous one, because it hits cash flow in a month when you were already having a bad month.

What actually reduces disputes is unglamorous: a recognizable name on the card statement, shipping with tracking, a reply within a day, and a return policy clear enough that refusing a refund rarely happens. Most first disputes are a customer who could not reach you, or did not recognize the charge.

If someone contacts you before disputing, refund them. A voluntary refund costs you the sale. A chargeback costs you the sale, a fee, and a mark on your ratio.

What a gateway will not do for you

It does not decide whether the payment succeeds. The issuing bank does. A high decline rate is usually the customer's bank being cautious about your category, country or basket size, and switching gateway may not move it.

It does not take the fraud risk. On card-not-present transactions, the merchant generally wears the loss. Gateways supply tools — address checks, network authentication, rules, scoring — and leave the consequences with you.

It does not make you compliant by itself. Using a hosted field or redirect so card numbers never touch your server cuts your obligations enormously, which is why you should do it, but PCI DSS duties remain yours.

It does not guarantee access to your money. Accounts get reviewed, payouts get delayed, reserves get imposed, and sudden volume growth is one of the triggers. Keep a second provider configured if an outage would stop your business, and keep enough cash that a two-week hold is survivable.

Four questions before you choose

1. What is your average order value? Small baskets make the fixed per-transaction fee the deciding number. Large ones make the percentage decisive.
2. Where are your customers? Cross-border and conversion fees are often larger than the headline difference between two providers, and local payment methods can affect conversion more than any fee.
3. How fast do you need the money? Payout schedules differ, and a weekly cycle changes how much working capital you need.
4. What happens when it breaks? Find out who you contact about a stuck payout and what the published dispute window is before you need either.

Where this sits with your store platform

Your platform and your payment provider are separate relationships. mAutomate runs the storefront, the marketing, the customer support and the business operations — inventory, sales, analytics, domains and business email — and the processing fees above belong to whichever payment provider you connect, not to your platform plan.

Keep the distinction straight when comparing costs: the two get added into one number and only half of it is negotiable. Ecommerce platform fees explained covers the platform half. The plans page lists what each tier includes; every plan starts with a 14-day free trial, no card required.