Klearly

• Environments requiring guaranteed offline acceptance with documented offline settlement behavior (not publicly evidenced)
• Organizations that prohibit phone-based acceptance due to operational policies
• Enterprises requiring documented SOC 2 or ISO attestations be available publicly or early in procurement

• Reports of app malfunctions and freezes that can interrupt payment acceptance.
• Perceptions of fee increases over time reported by some merchants.
• Confusion among some merchants about the availability of dedicated terminals versus an app-only model.

• Requires compatible NFC-capable devices; support documentation lists supported iPhone models and indicates older devices may be unsupported for contactless acceptance.

• No clear, dated public product roadmap with feature release timelines was found in the sources reviewed.

• Hospitality-focused acceptance workflows and documentation oriented toward peak service periods.
• Emphasis on phone-based Tap-to-Pay / SoftPOS acceptance with guidance on device compatibility and integration options.
• Investor and press coverage highlight a positioning toward updating hospitality acceptance methods.

• SumUp: widely recognized SMB pricing and large SMB adoption across many markets.
• Adyen / Worldline: mature enterprise controls, extensive compliance documentation, and global operational scale.

A testimonial excerpt shown on the vendor's pricing page states that devices are fast and that administrative processes improved following adoption. Because the excerpt appears on Klearly's site, prospective buyers should treat it as curated marketing material unless independently verified on a third-party review platform.

A Reddit thread includes a brief user comment noting use of Klearly with a phone as a terminal. This indicates at least some merchants employ a phone-as-terminal approach but does not provide structured evidence about reliability, fees, or support quality.

• Reduced dependence on dedicated hardware.
• Operational workflows aimed at faster payments during service peaks.

• Perceived increases in transaction fees.
• Reliability concerns in a payment-critical environment.
• Mismatch between expectations of a dedicated hardware terminal and an app-based acceptance model.

• App freezing or inability to take payments during service.
• Feeling misled about whether a dedicated terminal is available.

No detailed, independently verifiable case studies with methodology and before/after metrics were found in the public materials reviewed.

Press coverage and vendor announcements reference partnerships and customer relationships, which suggest market traction; however, these mentions do not provide quantified outcomes such as reduced checkout time, chargeback rates, or specific cost savings with independent verification.

• Single-location to small multi-location hospitality businesses (small-staff operations), including independent restaurants and small chains.

• Full-service restaurants
• Cafés and bars
• Clubs and hospitality venues
• Fast food / quick service

• Owner/operator or general manager
• Finance or operations managers responsible for reconciliation and payout timing
• IT or POS integration partner for integrated implementations

• Queue management and checkout speed during peak periods
• Hardware procurement and maintenance burdens associated with dedicated terminals
• Desire to integrate payments with existing POS or order flows

• Venues with sufficient connectivity (mobile data or reliable Wi‑Fi) and NFC-capable devices
• Clear device usage policies (company phones vs personal devices) and device-management practices
• POS vendor cooperation where deep integration is required

• Primary target: SMB hospitality merchants (restaurants, cafés, bars, clubs) in the Netherlands and broader Europe.
• Secondary/adjacent: market vendors and micro-merchants seeking to reduce hardware dependency by using phones as acceptance devices.
• Positioning: device-agnostic acceptance that uses existing NFC-capable devices to reduce reliance on dedicated terminals.