Payment technology
See the larger environment.
Explore →Payment operations intelligence
POS vs. gateway: what's the difference?
Both may appear in the same payment workflow, but they solve different problems and carry different contractual dependencies.
What a POS typically manages
A point-of-sale system can support order entry, pricing, inventory, staff permissions, checkout, receipts, refunds, and operating reports. Capabilities differ widely by industry and product.
A POS may include payment acceptance built in, rely on compatible terminals, or integrate with a separate gateway.
What a gateway typically manages
A payment gateway connects payment data and transaction requests among applications and processing services. Gateways may offer tokenization, reporting, recurring billing, fraud tools, routing, and API integrations depending on the provider.
The gateway does not automatically determine the entire merchant pricing schedule or control every underwriting and funding decision.
Where merchants get trapped
Hardware compatibility, locked-in software, proprietary stored tokens, subscription billing dependencies, and long-term leases can make a seemingly simple processor change costly.
- Inventory every device and software version.
- Document gateway, token and merchant-account dependencies.
- Ask which data and settings can be exported.
- Test refund, dispute, offline mode and reconciliation workflows.
- Require a written migration and rollback plan.
A practical selection rule
Choose the system that supports the business workflow and documented payment requirements. Then compare the full economic and contractual consequences of the supported processing arrangements.
Supported integrations and token portability must be confirmed with the specific software/gateway providers; do not assume one product's functionality applies to another.