Card-Present Terminal Decisions
- The terminal decides your liability shift. Chip and contactless push counterfeit fraud to the issuer. Swipe-only or keyed leaves it on you
- Square's card-present rate is 2.6% + 15c, not the widely quoted 2.6% + 10c. At 5,500 transactions a month that five-cent gap is worth $275. Verified against Square's own fee page on 2026-08-02
- There's no single cheapest card-present processor. Below about a $19.50 ticket, PayPal Zettle's 9c fixed fee wins. Above it, Helcim wins. That holds until Stax's subscription is earned back, somewhere north of $58,000 a month. Every ranking here states its ticket size, volume and interchange assumption
- Mobile card readers (Square, Stripe Reader) do fine under $500K/year of card-present volume. Countertop terminals suit fixed locations with higher throughput
- Clover, Toast and Lightspeed all publish card-present rates, but Clover's real rate is set by your reseller, not by Clover. Ask for the five things in the warning below
- Verify EMV certification and contactless support before buying. An older certified terminal may not meet the newer contactless tap requirements
- Leasing hardware is almost always a worse deal than buying it. Most leases are hard to cancel
Your terminal decides three things on every in-person sale. What the fees look like, how much fraud you see, and who carries the liability when a card turns out to be stolen. An EMV chip or contactless terminal pushes counterfeit fraud liability to the issuer. A swipe-only or keyed transaction keeps it on you. This page covers chip against tap against swipe, mobile POS, countertop selection, keyed entry risk and omnichannel.
One store, one terminal? The answer turns on your average ticket first, your monthly volume second. It doesn't turn on brand. And there isn't one right answer for everybody.
Everything below is card-present only. It assumes the blended pass-through this site publishes at Cost Model Assumptions. That's 0.89% + $0.158 of interchange plus an assumed 0.14% + $0.02 of network assessments, so 1.03% + $0.178. Change the assumption and the crossovers move. That's why it's published.
- Average ticket under about $19.50: PayPal Zettle at 2.29% + $0.09 (source, verified 2026-08-02). At small tickets the fixed fee decides it, and 9c is the lowest anyone here publishes. The catch is disputes. PayPal charges $20 on card chargebacks either way, and $30 on every dispute once your ratio passes 1.5%. Square charges $0. A dispute-prone business should price that in before taking the 9c.
- Average ticket above about $19.50, up to roughly $58,000 a month: Helcim at interchange + 0.40% + 8c. $0 a month, no setup, PCI, statement or cancellation fee (source, verified 2026-08-02). All in that's 1.43% + $0.258. It passes Square at a $9.23 ticket and Zettle at $19.53. Neither charges a monthly fee, so there's no volume you have to reach first. On a $50 ticket at $20,000 a month it costs $389 against Square's $580. That's $191 a month.
- Simplest path, and it isn't the cheapest: Square Terminal at 2.6% + 15c on the Free plan. No subscription, no contract (source, verified 2026-08-02). Square isn't cheapest at any ticket or volume in the table below. What you're buying is POS software and the hour you don't spend on setup. That's a legitimate thing to buy. Hardware is bought outright, and the device price isn't on the fee page. Check Square's shop before you budget.
- Somewhere above $58,000-$70,000 a month: get a Stax quote. It passes interchange through at 0% markup + 8c, on a subscription priced by annual volume, not monthly (source, verified 2026-08-02). At its published $199 floor it overtakes Helcim at roughly $70,300 a month on a $15 ticket, $60,400 on a $50 ticket and $58,000 on a $150 ticket. Treat those as the earliest possible crossovers, not promises. Above $250,000 a year Stax publishes "$199+" with no ceiling, so your quote sets the real number.
Be careful with any advice that names a fixed monthly volume for switching pricing models. A volume threshold only exists when the interchange-plus provider charges a monthly fee. Stax does, so its thresholds are real. Helcim doesn't, so with Helcim the question is your ticket size, not your volume.
The fleet management, omnichannel and device hygiene sections below are for multiple locations or a complex POS setup.
What Card-Present Processing Actually Costs
Every figure here came from the vendor's own pricing page on 2 August 2026. Where a vendor doesn't publish, this table says so rather than guessing.
The flat rates and the interchange-plus rates in this table are not directly comparable as printed. A flat rate already contains interchange. An interchange-plus rate doesn't. To rank them you have to assume what interchange costs, and that assumption changes the answer. Ours is published in full at Cost Model Assumptions.
| Provider | Card-present rate | Monthly | Chargeback fee | Source |
|---|---|---|---|---|
| Square | 2.6% + 15c (Free); 2.5% + 15c (Plus); 2.4% + 15c (Premium) | None on Free | Not published | squareup.com |
| Helcim | Interchange + 0.40% + 8c, falling to +0.15% + 6c at $1M-5M/month | $0 | $0 if you win, $15 if you lose | helcim.com |
| Stax | Interchange + 0% + 8c | $99-$199+ by annual volume | $25 with the optional protection add-on | staxpayments.com |
| PayPal Zettle | 2.29% + $0.09 | None | $15 wallet ($0 if you win), $20 card, $30 above a 1.5% ratio | paypal.com |
| Shopify Payments | US: Basic 2.6% + 10c, Grow 2.5% + 10c, Advanced 2.4% + 10c. Canada carries no cents on any plan | US $39-$2,300+, or $29-$299 billed annually | Not published | shopify.com/pricing |
| Stripe Terminal | 2.7% + $0.05. Cards issued abroad add 1.5% | None | $15 to receive plus $15 to counter | stripe.com/pricing |
| Moneris (Canada) | CA$: 2.65% + $0.10 credit, Interac Debit $0.12. Foreign cards +0.80% | No monthly stated for Flat Rate; CA$5 minimum merchant discount, CA$5 Moneris Go software fee, CA$34.95 Moneris Go terminal | CA$25, plus CA$80 authorization chargeback handling | moneris.com |
| Clover (direct) | 2.3% + 10c restaurant and QSR, 2.6% + 10c entry retail and services. Keyed and online 3.5% + 10c. Reseller-dependent in practice | $0 to $129.85 | Not published at any tier | clover.com/pricing |
| Toast | 2.49% Traditional, 3.09% Pay-as-you-Go. The + 15c is reported by third parties, not published by Toast | $0 Starter Kit, $69 restaurant, $90 retail | Not published at any tier | pos.toasttab.com/shop/starter-kits |
| Lightspeed | 2.6% + 10c retail (X-Series). No rate published for the restaurant product | Retail $89-$289, restaurant $69-$399 | $15, described as a single fee covering the defence | lightspeedhq.com |
The widely quoted "Stripe Terminal at 2.6% + $0.10" matches no Stripe geography. The US figure is 2.7% + $0.05, read from a US connection.
Comparison content routinely says they don't. All three do, and the rates are in the table above. Lightspeed's supposed "1.5%" appears nowhere on its site.
What's still true: Clover's actual rate is reseller-dependent, and Clover says so on its own pricing page. Treat the published direct rates as your anchor. Anything above them is markup.
Get these five things in writing before signing any of the three:
- Effective rate including every markup, on your actual card mix, benchmarked against the vendor's own published rate
- Monthly software cost per device or terminal
- The chargeback fee. Clover and Toast publish none at any tier; Lightspeed publishes $15
- Contract term and the early termination fee. Clover's hardware promotions require three years and auto-renew unless you give 30 days' notice. Toast's own 10-K says 12 to 36 months, so push for 12
- Whether hardware is subscribed or bought. On Clover's own published figures the 36-month subscription premium runs $227 to $3,622. Its FAQ confirms you don't own the device at term end
For Clover, the hardware subscription is where the cost hides. You can now check it against Clover's own outright prices. For Toast, it's the payments lock-in. A Toast contract typically stops you switching processors without replacing the POS.
What Matters
- EMV chip transactions shift liability. If you accept a dipped chip card and it's fraudulent, the issuer eats it. If you swipe, you eat it.
- Contactless is expected. Customers increasingly tap. If you can't accept tap, you look dated.
- Keyed transactions are high-risk. Every keyed entry is a liability and fraud exposure.
- Terminal security is your problem. Tampered terminals mean stolen cards and your account shutdown.
- Omnichannel needs planning. If you sell online too, unified processing matters.
EMV vs. Contactless vs. Swipe
EMV (Chip Dip)
| Aspect | Details |
|---|---|
| Security | Highest for card-present. Chip generates unique cryptogram per transaction. |
| Liability | Fraud liability shifts to issuer when chip is read. |
| Speed | 2-4 seconds. Slightly slower than tap. |
| Customer expectation | Standard. Everyone expects chip readers. |
Contactless (Tap)
| Aspect | Details |
|---|---|
| Security | Same cryptogram technology as chip. |
| Liability | Same liability shift as EMV. |
| Speed | 1-2 seconds. Fastest card method. |
| Customer expectation | Growing. Post-COVID, many prefer no-touch. |
| Requirements | NFC-enabled terminal. Most modern terminals include this. |
Swipe (Mag-stripe)
| Aspect | Details |
|---|---|
| Security | Lowest. Static data, easily cloned. |
| Liability | Fraud liability stays with merchant. |
| Speed | Fast, but irrelevant given liability. |
| When acceptable | Fallback only when chip fails. Should be rare. |
Rule: Chip and tap always. Swipe as last resort.
Mobile POS Options
Mobile POS (mPOS) means a card reader connected to a phone or tablet.
When Mobile POS Works
- Mobile businesses (food trucks, market vendors)
- Pop-up retail
- Service businesses at customer locations
- Low-volume retail testing a location
- Backup terminal when primary fails
When Mobile POS Doesn't Work
- High-volume retail (too slow, battery issues)
- Situations requiring receipt printer integration
- Complex inventory/POS needs
- Unreliable phone connectivity
Common Mobile POS Options
| Device | Published card-present rate | Best For | Notes |
|---|---|---|---|
| Square Reader | 2.6% + 15c (Free plan) | Very low volume, simplicity | Locked to Square ecosystem |
| Stripe Terminal | 2.7% + $0.05 US | Developers, omnichannel | More technical setup |
| PayPal Zettle | 2.29% + $0.09 | PayPal users, low volume | Lowest published US flat card-present rate here. Card chargebacks cost $20, and $30 once your dispute ratio passes 1.5% |
| Clover Go | Not published, set by your reseller | SMBs wanting Clover ecosystem | Ask about hardware leasing before signing |
Rates verified against each vendor's own pricing page on 2026-08-02 (paypal.com, squareup.com, stripe.com/pricing). Among the US flat rates verified here, PayPal Zettle's 2.29% + $0.09 is lowest at every ticket size. On a $40 sale it costs $1.01 against Square's $1.19. Stripe Terminal's US rate is 2.7% + $0.05, so the same sale costs $1.13. The fixed fee decides small-ticket rankings, and Zettle's 9c is the lowest of the three.
That advantage narrows if you take disputes. PayPal's $20 card chargeback fee is charged win or lose. Above a 1.5% dispute ratio every dispute costs $30, wins included. Square charges $0. Zettle's fixed fee undercuts Square's by 6c a transaction, so one $20 chargeback eats the fixed-fee advantage on about 330 sales. Run your own dispute rate before you take the rate.
The bigger caveat: "cheapest flat rate" isn't "cheapest". Every device in the table above is flat-rate. A flat rate charges the same on regulated debit as on a premium rewards card. An interchange-plus reader from Helcim at interchange + 0.40% + 8c behaves completely differently by card type. Using the published pass-through assumption and Visa's card-present schedule:
| $40 card-present sale | Zettle (2.29% + 9c) | Helcim (interchange + 0.40% + 8c) |
|---|---|---|
| Regulated debit | $1.01 | $0.56 |
| Standard rewards credit | $1.01 | $1.08 |
| Premium rewards credit | $1.01 | $1.26 |
| Blended SMB retail mix | $1.01 | $0.83 |
So Helcim is far cheaper on debit. Slightly dearer on a standard rewards card. Clearly dearer on a premium rewards card. And cheaper on the blend once your average ticket clears $19.53. Below that, Zettle wins on the blend too. Pull your own card mix off a statement first. It's the input doing all the work here.
One more structural point. Shopify Payments charges 10c per in-person transaction in the US, and no cents at all in Canada. Ten cents is among the lowest fixed fees here. That matters most on tickets under $10.
Mobile POS Trade-offs
| Pro | Con |
|---|---|
| Low upfront cost | Higher per-transaction fees |
| Portable | Battery dependent |
| Quick setup | Limited integration |
| Good for testing | May outgrow quickly |
Countertop Terminals
Traditional terminals that sit at checkout.
Key Features to Require
- EMV chip reader
- NFC/contactless
- PIN pad (for debit)
- Internet connectivity (Ethernet preferred, WiFi fallback)
- Receipt printer (built-in or separate)
Key Features to Evaluate
| Feature | Why It Matters |
|---|---|
| Dual-facing screen | Customer can see amount, enter PIN, tip |
| Integrated printer | Fewer failure points |
| Battery backup | Continues during brief power outages |
| PCI PTS certification | Security compliance |
Terminal Manufacturers vs. Processors
Terminal hardware comes from PAX Technology, Ingenico and Verifone. They make the devices. They aren't payment processors. Your processor decides which terminals are compatible.
- Locked terminals (Toast, Clover, Square): Hardware only works with that processor's software and processing. Cheaper or "free" upfront but no portability.
- Open terminals (PAX, Ingenico, Verifone): Can be programmed to work with many processors. More expensive upfront but portable if you switch.
Buying standalone terminals rather than a POS bundle? PAX A920/A80 and the Ingenico Move/Desk series are the usual SMB picks. Your processor's support team can tell you which models they certify.
Terminal Locking
Some processors bundle "free" terminals that only work with them. When you leave:
- Terminal becomes paperweight
- No token portability
- Forced to start over
Ask before accepting bundled hardware: "If I switch processors, can this terminal work with others?"
MOTO/Keyed Transaction Risk
MOTO (Mail Order / Telephone Order) and keyed transactions are high-risk. They're also the one channel where every processor publishes a penalty rate.
| Provider | Card-present | Keyed | The penalty | Source, verified 2026-08-02 |
|---|---|---|---|---|
| Square | 2.6% + 15c | 3.5% + 15c (keyed and card on file) | +0.9% | squareup.com |
| PayPal | 2.29% + $0.09 (Zettle) | 3.49% + $0.09 | +1.2% | paypal.com |
| Stripe | Terminal rate | Terminal rate +0.5% for manual entry | +0.5% | stripe.com/pricing |
| Helcim | Interchange + 0.40% + 8c | Billed at the online rate, interchange + 0.50% + 25c | +0.10% + 17c | helcim.com |
| Stax | Interchange + 8c | Billed card-not-present, interchange + 15c | +7c | staxpayments.com |
On Square, a shop running $50,000 a month through keyed entry instead of the reader pays $450 extra for the same sales. On interchange-plus the markup penalty is smaller. But the underlying interchange downgrades too, so the real gap is wider than the markup suggests.
When Keyed Entry Is Acceptable
- Established B2B customer calling with a repeat order
- Card present but chip won't read (1 attempt only)
- Phone orders with verified existing accounts
When Keyed Entry Is a Red Flag
| Scenario | Risk |
|---|---|
| Walk-in customer says chip "doesn't work" | Possible counterfeit or card testing |
| Employee keying cards at end of shift | Possible collusion or internal fraud |
| High keyed ratio at one register/employee | Internal fraud signal |
| Keyed transactions for pickup orders | Card may not be present at all |
Liability Shift Loss
Keyed transactions don't get EMV liability shift. If the charge is fraudulent, you eat the loss.
Employee Training
Train staff:
- Never key a card if the customer refuses to try chip/tap
- If chip fails twice, ask for different card
- Document why any keyed transaction was necessary
- Never key a number read over the phone by a walk-in customer
Monitoring Keyed Ratio
Track keyed transactions as percentage of total CP volume.
| Ratio | Status |
|---|---|
| < 2% | Normal. Cards occasionally fail. |
| 2-5% | Investigate. Check by employee. |
| > 5% | Problem. Review immediately. |
"Can we pull a report showing keyed transaction percentage by employee or register?"
Device Fleet Hygiene
If you have multiple terminals, fleet management matters.
Reader Labeling and Inventory
- Label each terminal with unique identifier
- Track serial numbers and locations
- Know which terminal is at which register/location
- Maintain spare for quick replacement
Connectivity Best Practices
| Connection | Pro | Con |
|---|---|---|
| Ethernet | Most reliable, fastest | Requires wired infrastructure |
| WiFi | Flexible placement | Interference, security concerns |
| Cellular (LTE) | Works anywhere | Monthly cost, slower |
| Bluetooth to phone | Portable | Battery dependent, pairing issues |
Recommendation: Ethernet for fixed locations. Cellular for mobile. WiFi as middle ground.
Firmware Update Cadence
- Terminals require firmware updates for security and features
- Schedule updates during off-hours (after close or before open)
- Test after update before peak hours
- Some processors push updates automatically (verify this is happening)
Offline Mode Risks
Many terminals can accept transactions offline and batch-upload later.
Risks:
- Offline transactions have no real-time auth
- If card is actually declined, you don't find out until batch
- Fraud risk is higher
- Weekend offline batches can mean Monday surprises
Guidance: Disable offline mode unless absolutely necessary. If required, set low limits.
Battery and Charging Discipline
For mobile and battery-backup terminals:
- Charge overnight
- Replace batteries proactively
- Don't drain to zero (damages battery)
- Have backup charger/battery
When a Reader Disappears from Dashboard
If a terminal stops appearing in your processor dashboard:
- Check power and connectivity first
- Verify firmware is current
- Check if it was reassigned or removed
- Contact processor support if unresolved
- Consider it potentially compromised until explained
IVR/Phone Payment Risk
Taking card numbers over the phone creates PCI scope and fraud exposure.
PCI Scope Implications
If staff hear or transcribe card numbers:
- Your environment is in PCI scope
- Call recordings with card data are violations
- Systems that display card numbers need protection
Authentication Challenges
Phone payments have:
- No 3DS option
- No device fingerprint
- No address verification at point of call
- Only CVV as protection
Fraud Patterns
| Pattern | Description |
|---|---|
| Social engineering | Fraudster calls claiming to be customer, provides stolen card |
| ATO via support | Fraudster calls to add card or change details |
| Employee collusion | Staff takes card info for personal use |
When Phone Payments Are Acceptable
- Established B2B relationships with known contacts
- Follow-up to in-person transaction (card failed, callback with different card)
- Low-ticket, low-risk items
Better Alternatives
| Instead of Phone | Do This |
|---|---|
| Customer reads card over phone | Email/text a payment link |
| Staff keys card number | Send hosted checkout link |
| Repeat B2B orders by phone | Set up on-file billing |
Related: Invoicing
Omnichannel Considerations
If you sell in-person and online, unified processing simplifies everything.
Benefits of One Processor for Both
| Benefit | Why It Matters |
|---|---|
| Unified reporting | One dashboard for all transactions |
| Single reconciliation | One deposit, one statement |
| Token sharing | Cards saved online work in-person and vice versa |
| Consistent pricing | No managing two rate structures |
When Separate Processors Make Sense
- Specialized CP processor with better terminal support
- Legacy in-person setup that works, new online launch
- Temporary while migrating
Omnichannel Pitfalls
- Different merchant IDs for CP and CNP can confuse reconciliation
- Customer disputes may land in wrong system
- Token portability between channels isn't automatic
- Reporting gaps between systems
"Are our in-person and online transactions on the same merchant account? Do saved cards work across channels?"
Terminal Security
Terminal tampering leads to card skimming, data theft, and account termination.
Tamper Inspection Checklist
Weekly check:
- Terminal casing intact, no unusual gaps
- Card slot matches original design
- No overlay on PIN pad
- No loose cables or wires
- Tamper stickers/seals unbroken
- Serial number matches your records
Physical Security Basics
- Terminals should be visible to staff, not hidden
- Cable terminals to prevent grab-and-run theft
- Limit who can access back of terminal
- Lock terminals in safe overnight (high-risk locations)
What to Do If Tampering Suspected
- Stop using the terminal immediately
- Do not process transactions
- Contact your processor security team
- Preserve the terminal as evidence
- Review recent transactions for anomalies
- File police report if theft confirmed
Test to Run
2-week terminal audit:
Week 1: Baseline and inspect.
- Pull keyed transaction percentage by terminal/employee
- Inspect all terminals for tampering
- Verify firmware is current
- Check connectivity type and reliability
Week 2: Remediate and measure.
- Address any high keyed ratios
- Update firmware if needed
- Fix connectivity issues
- Re-check keyed ratio
Success criteria: Keyed ratio under 2%, all terminals current on firmware, no tampering signs.
Scale Callout
| Volume | Focus |
|---|---|
| Under $100k/mo CP | Get a basic EMV/NFC terminal and don't overthink the hardware. On cost, Helcim or Zettle beat Square at this volume, and which one depends on your ticket. Pick Square and you're paying for the software, not saving on the rate. Stripe Terminal at 2.7% + $0.05 sits between them on a mid-size ticket. |
| $100k-$1M/mo CP | Fleet management matters. Standardize terminals, track keyed ratios, schedule firmware updates. This is also the band where a Stax quote starts to be worth getting. |
| Over $1M/mo CP | Multi-location consistency, dedicated terminal support, employee training programs, regular security audits. Helcim publishes bands to $5M/mo; above that everyone is negotiating. |
Where This Breaks
-
Multi-location businesses with inconsistent terminal versions. Old terminals at some locations create liability gaps and reporting inconsistencies.
-
Mixed CP/CNP with reconciliation complexity. Separate merchant IDs for channels creates accounting headaches.
-
High-turnover staff requiring constant retraining. Security and procedure training gets neglected with frequent staff changes.
Analyst Layer: Metrics to Track
| Metric | What It Tells You | Target |
|---|---|---|
| Keyed transaction % | Liability exposure and fraud risk | < 2% |
| EMV dip vs. tap ratio | Customer preference, terminal capability | Track trend |
| Offline transaction % | Batch risk | < 1% or 0% |
| Terminal uptime | Hardware reliability | > 99% |
| Chargeback ratio by channel | CP should be lower than CNP | CP < 0.3% |
Next Steps
Choosing terminals?
- Compare EMV vs contactless vs swipe - Know the trade-offs
- Evaluate mobile POS - When mPOS works and doesn't
- Check countertop features - What to require
Managing existing fleet?
- Monitor keyed transaction ratio - Under 2% target
- Implement tamper inspection - Weekly checks
- Follow fleet hygiene - Labeling, connectivity, firmware
Concerned about security?
- Train employees on keyed transactions - When to refuse
- Secure physical terminals - Cable, lock, visible
- Know response protocol - Stop, preserve, report
Related Pages
- Card-Present Fraud - In-person fraud risks
- Terminal Operations - Day-to-day management
- Buying Payments - Processor selection
- Invoicing - Phone payment alternatives
- EMV & Contactless - Chip security
- PCI DSS - Physical security requirements
- Processor Management - Acquirer relationships
- Reading Statements - Fee analysis
- Decline Codes - Transaction failures
- Chargeback Prevention - Dispute reduction
- EMV Liability - Liability shift rules
- Checkout Conversion - Omnichannel integration