Global In-Person POS Pricing and Features Guide

Choose an international in-person payment provider by country coverage, merchant entity, card mix, hardware, software workflow, settlement, disputes, and platform integration—not one published domestic-card rate. Public prices are useful for screening; the target market's current official quote and agreement govern.

Wavesteam can compare and integrate payment technology. It does not guarantee merchant approval or act as an acquirer, bank, tax adviser, or card-compliance assessor.

---

1. Providers solve different operating models

Square, Stripe Terminal, PayPal POS, Shopify POS, Adyen, and Clover are not interchangeable product tiers. Availability, pricing, devices, and features differ by country and entity. A capability on a US page should not be assumed in Europe, the Middle East, or Asia.

---

2. Compare complete unit economics

For each country and transaction type, calculate:

monthly payment cost = processing + fixed transaction charges + cross-border/FX + hardware + POS software + connectivity + disputes + payout/other service fees

Use the same monthly volume, transaction count, average ticket, domestic/international and card-present/manual-entry mix, refund and chargeback rate, device count, and payout needs. Published rates often exclude taxes, premium cards, currency conversion, disputes, hardware, or a required software plan.

The cheapest percentage is not necessarily the lowest cost. Fixed fees matter on small tickets; international cards and manual entry can be more expensive; slow settlement and reserves affect working capital; a provider with higher processing but better inventory and staff workflows can reduce operating cost.

---

3. Hardware and software are one acceptance scope

Compare readers, countertop terminals, receipt printers, cash drawers, barcode scanners, customer displays, cellular support, Tap to Pay where offered, and replacement logistics. Then evaluate catalog, tax, tips, discounts, refunds, split tender, staff permissions, shifts, inventory, offline behavior, and reconciliation.

Test target cards and wallets, contactless and chip, refund, reversal, duplicate submission, callback loss/reorder, weak network, day close, firmware update, device reassignment, and provider outage. Offline capability has product- and risk-specific limits and must be verified for the merchant account.

For a software platform serving other merchants, do not use one merchant account for everyone. The provider's official platform or marketplace product must support onboarding, identity, merchant terms, connected accounts, payouts or splits, disputes, and data boundaries. The payment provider and qualified counsel confirm the money-flow model.

---

4. Integration and reconciliation

Create an internal order and payment attempt before calling the provider. Verify server notifications and ensure idempotent posting. Separate authorized, captured, settled, refunded, reversed, and disputed states. Preserve provider and terminal IDs, currency, fee, payout batch, and FX evidence.

Reconcile business orders to provider transactions and provider payouts to bank deposits. A provider's gross sales dashboard is not accounting revenue. Tax, refunds, tips, fees, chargebacks, and delayed batches need explicit treatment.

Use provider-hosted card capture or certified terminals to reduce card-data scope where appropriate. Outsourcing processing does not eliminate merchant responsibility for provider due diligence, written responsibilities, and applicable validation.

---

5. Match route to business

• A small US store or service business can screen all-in-one products first.
• A Shopify merchant adding physical sales should compare Shopify POS before creating separate catalog and inventory.
• A SaaS product embedding payments should compare developer and platform products such as Stripe Terminal or an enterprise acquirer.
• A multi-country chain needs local coverage, unified reporting, routing, devices, and country-by-country contracts.
• Events and mobile teams should test Tap to Pay or lightweight hardware alongside network and backup devices.

Wavesteam uses the client's countries, stores, volumes, tickets, card mix, refunds, devices, and settlement requirements to create a normalized provider matrix. We validate onboarding assumptions, payment/refund paths, weak-network recovery, and day-close reconciliation, then deliver a preferred route, backup, integration boundary, and migration trigger. The chosen institution remains responsible for approval, rates, settlement, and regulated processing.