# Payment gateways explained for small shops

URL: https://ekom.blog/payment-gateways-explained-for-small-shops/
Published: 2025-11-21
Author: Ekom
Topics: How the internet works

> What a payment gateway does, how it differs from a processor and a merchant account, and what small shops should compare before choosing one.

When a customer types their card details into your shop, you probably don't think about where those numbers go. You shouldn't have to. But if you're setting up a store, you'll need to pick a payment gateway, and the choices come with jargon that makes it harder than it needs to be.

Gateway, processor, acquirer, merchant account, payment facilitator. They all sound like the same thing. They aren't. Here's the plain version, and what actually matters when you're a small shop choosing one.

## What a payment gateway is

A payment gateway is the service that securely takes the customer's payment details at checkout and passes them on to be approved. Think of it as the card reader of an online shop. In a physical shop, a terminal reads your card and talks to the bank. Online, the gateway plays that role.

It does a few jobs:

- Collects the card details securely, usually through an encrypted form or a hosted payment page.

- Sends the transaction for approval and returns the result (approved or declined) to your shop.

- Handles security checks, like extra verification steps for the customer's bank.

- Reports and records each payment so you can reconcile your sales.

That's the gateway's whole job: capture, pass on, report back.

## The other names you'll hear

- Payment processor: the company that moves the transaction between the card networks and the banks. The gateway talks to the processor.

- Acquiring bank (acquirer): the bank that receives the money on your behalf and settles it to your account.

- Merchant account: a special account at an acquirer that lets you accept card payments. Traditionally you opened one yourself.

- Payment facilitator (or "aggregator"): a company that bundles all of the above, so you don't need your own merchant account. You sign up, connect it to your shop and start. Many popular services work this way.

For a small shop, the bundled route is the usual starting point. It's quick, and you aren't dealing with several separate contracts. The trade-off is that the provider holds a lot of power over your account: they may hold funds or pause an account if something looks risky.

## Hosted, embedded or redirect?

How the payment form appears matters for security and for conversion.

Style
What the customer sees
Good for

Redirect / hosted page
Taken to the provider's page to pay, then back
Simplest, least security burden

Embedded form (iframe or fields)
Pays on your site, but the card fields come from the provider
Smoother look, still low burden

Direct integration
Card details touch your own server
Rarely a good idea for small shops

Choose hosted or embedded. They keep card numbers off your server, which greatly reduces your security responsibilities under card industry rules (PCI DSS). Handling card data directly is a much heavier job than most small shops should take on.

## What to compare

### 1. Does it support your country and customers?

This is the first filter, and it matters more than any feature. Not every gateway can pay out to every country, and not every one supports local payment methods. If your customers use bank transfers, mobile money, local cards or wallets rather than international cards, the right gateway for you may be a regional one. Ask whether they support payouts to your bank, your currency and your customers' usual methods.

### 2. Fees, and how they are structured

Typical pricing is a percentage plus a fixed amount per transaction. Watch for:

- Extra charges for international cards or currency conversion

- Fees for refunds and chargebacks

- Monthly fees or minimums

- Payout fees

Compare by working out what a typical order would cost you, not just the headline rate.

### 3. Payout speed and reserves

How long between a customer paying and the money reaching your account? Some providers pay out in a day or two, others take a week or more, and some hold a percentage back for a period on new accounts. For a small shop with thin cash flow, this matters.

### 4. Integration with your platform

Check that it works smoothly with your shop software, whether that's Shopify, WooCommerce or something else. A well-maintained official integration saves you from custom code. On a WordPress shop, keep it updated like any other plugin; see keeping plugins, themes and core updated safely.

### 5. Checkout experience

Fewer steps and familiar payment methods mean fewer abandoned carts. Check how it looks on a phone, because most shoppers will be on one. A good gateway also supports saved cards and wallets such as Apple Pay and Google Pay. Mobile payments: Apple Pay, Google Pay and Samsung Wallet explains how those fit in.

### 6. Fraud tools and chargeback support

Fraud and card testing are real for small shops too. Look for basic fraud screening, support for 3-D Secure verification, and help with disputes. Also think about protecting your own checkout form; I covered abuse in how online forms get abused, and how to protect them.

### 7. Support and reliability

When money is stuck, you need a human. Look at how reachable support is and what the uptime record is. Check whether they have a status page.

### 8. Account stability

Read the terms about what they restrict, when they might freeze funds, and what documents they ask for. The worst time to discover a clause is after a frozen payout.

## What to ignore

- The lowest headline rate if payouts are slow or support is poor.

- Features you won't use, such as advanced subscription billing, if you sell single items.

- Brand fame alone. The best-known option isn't automatically available or affordable in your market.

## A simple checklist

- Supports your country, currency and payout method

- Supports the payment methods your customers actually use

- Hosted or embedded checkout, so you don't handle card data

- Fees are clear, including international, refund and payout costs

- Payout schedule suits your cash flow

- Good integration with your shop platform

- Fraud tools and dispute support

- Real support and a status page

## Should you have a backup gateway?

Once you have steady sales, a second option is worth considering. If your only gateway has an outage or freezes your account, your shop can't take money. It's the same dependency lesson as in the Cloudflare outage: when the internet's middleman trips: one provider, one point of failure.

## Key takeaways

- A gateway securely captures card details and passes them on for approval.

- Processors, acquirers and merchant accounts sit behind it; many providers bundle them.

- Choose a hosted or embedded checkout so card numbers stay off your server.

- Compare country support, total fees, payout speed, integration and support, not just the headline rate.

- Read the terms about holds and freezes before you sign up.

## Related reading

- How online shops talk to delivery companies

- VPNs explained: when you need one and when you do not

- Why I still recommend email lists

Before you choose, write down your top five customer payment methods and your payout bank. Then check each gateway against that list, and only then compare fees.

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
