Gateway vs merchant account
A payment gateway is the technology path that encrypts and routes authorization requests from your website, app, or virtual terminal toward the processing network. A merchant account is the settlement relationship that ultimately funds your business bank account (subject to underwriting and your agreement).
Many online and mail-order/telephone (MO-TO) merchants need both. Confusing the two leads to incomplete setups—nice checkout, nowhere for funds to land, or an account with no way to authorize remote sales.
Online / MO-TO
Gateways matter most when the card is not physically present:
- E-commerce checkout and invoices
- Recurring billing (policy and risk review still apply)
- Phone or mail orders entered through a virtual terminal
Card-present businesses may still use gateway-connected smart terminals or hybrid POS. For in-person hardware focus, see POS & terminals.
Integration conversation
Before anyone promises “plug and play,” we ask:
- What cart, CRM, or custom stack you use
- Whether you need tokenization, recurring tools, or simple pay-by-link
- Card-not-present volume and fraud controls you already run
- How refunds and chargebacks are handled today
We do not invent named bank-agent relationships or unverified partner certifications on this page. Security themes belong on data security.
Ready to talk fit? Get a quote. Questions: FAQ.
Common questions
Do I need a gateway if I only take cards in person?
Not always. Many card-present setups use terminals or POS that authorize without a separate e-commerce gateway. Hybrid businesses often need both.
Is the gateway my merchant account?
No. Different jobs. See merchant accounts.
Can you integrate with any cart?
Compatibility depends on the gateway and your stack. That is part of the fit conversation—not a blanket claim.
Where do PCI questions show up?
Card-not-present and stored credentials raise PCI and security questions early—read data security.
How do I start?
Talk gateway fit via quote.