TickFlowTickFlowField
PricingFAQ
Sign In
Book a demo
Skip to content
  • Overview
  • How it works
  • Security
  • Platforms
  • Integrations
  • Solutions
  • Developers
  • Trust
  • Pricing

Platforms

Built for the devices at the counter, not the ones in the office.

Android payment terminals first, then Windows, macOS and Linux point-of-sale and kiosk machines, web POS in the browser, and SDKs for Android, React Native and iOS apps you build yourself.

Supported platforms

Northwind PayLane 2
TotalCA$42.50Insert, tap or swipe
Report a problem

PAX A920 Pro · A77

Android POS · printer · chip, tap, swipe

Kotlin agent, installed through PAXSTORE or your EMM

Tier B as Device Owner: reboot, network reset, app updates and rollbacks, silent installs.

  • Floating Report button
  • Logs and bug reports
  • Reboot · network reset
  • App update / rollback

Android capability tiers

What the agent can do depends on how it is installed.

Tier A runs anywhere and already gives you evidence-backed tickets, especially with the Field SDK in your app. Tier B, as Device Owner through your EMM, unlocks most remote fixes. Tier C uses vendor privileges where the terminal vendor allows it. Distribution on bank terminals goes through the vendor’s terminal management store and your app approval process.

Android capabilities by install tier
CapabilityTier A · standard appTier B · Device OwnerTier C · vendor-privilegedNote
Floating Report buttonPartlyYesYesA: needs the overlay permission; some vendor launchers block it
Screenshot of any appPartlyPartlyYesA/B: Android asks for consent every session
Your own app's logs (Field SDK)YesYesYes
System-wide logsNoPartlyYesB: network and security logs, bug reports
Restart, clear cache, re-sync configPartlyYesYesA: only through the SDK inside your app
Reboot, network resetNoYesYes
Install, update, roll back appsNoYesYesC: through the vendor's store or TMS
Clear app data, factory resetNoYesYesDestructive: always two people

Terminal models are named to show the platforms Field is built for. Names are trademarks of their owners; no vendor partnership or certification is implied.

Windows · macOS · Linux

One Go daemon, a native button on each OS.

  • Windows

    A LocalSystem service for buffering, Event Log, WER crash reports and commands, plus a per-user tray process for the button and the screenshot. Signed MSI for Intune, SCCM or GPO.

  • macOS

    A LaunchDaemon with a user LaunchAgent. Screen Recording granted once, or through an MDM privacy profile on managed Macs. Notarised package.

  • Linux

    A systemd service reading journald and app files. A button where a desktop session exists, otherwise a hardware key or a remote trigger.

Web POS in Chrome

A Manifest V3 extension records console and network activity for the last few minutes of the reporting tab, with headers redacted and no request bodies by default, plus the screenshot. Force-install it with Chrome policy, which also removes the debugger banner.

iOS, honestly

iOS does not let an app float over others, read other apps’ logs or run in the background. On iOS, Field lives inside your app as an SDK, optionally with MDM for device-level actions.

SDKs

Inside your own app, on every phone and terminal.

When the app at the counter is yours, the SDK adds what only the app knows: the screen, the error, the order. Same Report button, same redaction rules, same evidence.

  • Available

    Android

    Inside your payment or store app: real stack traces, the screen the person was on and the order context, handed to the agent or sent directly where no agent runs.

  • Rolling out

    React Native

    One SDK for cross-platform apps, with the same report, the same redaction rules and the same evidence on Android and iOS.

  • Rolling out

    iOS, inside your app

    iOS does not allow a device-wide agent, so on iOS Field is the SDK in your own app: a Report button, your app's evidence, redacted before it leaves.

Going deeper

Closer to the terminal, with the people who make it.

The tiers above are what any Android terminal allows. With a terminal maker’s help, Field can do more of the fixing itself, and be surer of which device it is talking to.

  • Rolling out

    Deeper integration with leading Android POS makers

    Working with a first terminal maker so more fixes run remotely, the cashier sees fewer prompts, and the agent ships through the maker's own management tools. More makers to follow.

  • Rolling out

    Hardware-backed device identity

    Where the terminal supports it, a device proves its key lives in genuine hardware, so a copied identity is turned away.

What the agent collects

Dormant until someone asks. Then only what diagnosis needs.

A small signed check-in, about every 15 minutes
Model, OS and agent versions, battery, storage, signal, clock skew. Under 100 KB a day is the target.
On a report: a screenshot
What was on screen when the person tapped. Screens the OS marks as secure, such as PIN entry, come out blank.
On a report: the last 30 minutes of logs
From the apps the agent is set up to watch, redacted on the device before they leave it.
On a report: device state and recent crashes
Network, storage and peripheral status (paper, reader state, never card data), crash and ANR reasons.

Never

  • Card numbers, track data, PINs or verification codes: redacted on the device, and a server hit quarantines the bundle
  • Anything from the payment kernel or PIN entry: the agent never touches them
  • A continuous stream: between reports the agent sends only its check-in
  • Request bodies from web POS by default; headers are redacted
  • Location, contacts, messages, camera or microphone

Rolling it out

Installed through the tools you already use.

  1. 01

    Sign in to your portal

    Agent builds are not public. Your administrators find them in your organisation’s portal, with an enrolment code for the fleet they belong to.

  2. 02

    Push it with your fleet tools

    Your MDM or EMM, the terminal vendor’s management store, Intune, SCCM or GPO on Windows, a profile on Macs, Chrome policy for web POS.

  3. 03

    Each device enrols itself

    It makes its own key, checks our key against the code, and appears in your fleet. Codes expire and can be revoked; a device can be cut off at any time.

Rolling out

Updates without surprises

New agent versions are published to your portal. They reach a pilot group of your devices first and the rest only once that group is healthy, and you can pin a client or a fleet to a version while you test.

Tell us what is in your fleet.

Send us the models and how they are managed. We will tell you which tier you can run and what it fixes.

Book a demoEstimate your savings

Or write to hello@tickflow.co

Report a problem.
TickFlow Field

On-demand diagnosis and remote repair for payment terminals and field devices. Part of the TickFlow family, built by Orthoplex Solutions in Canada.

hello@tickflow.co

Product

  • How it works
  • Security & PCI
  • Platforms
  • Integrations
  • Product tour
  • Playbook catalog
  • Compare
  • Pricing

Solutions

  • Savings calculator
  • Banks & acquirers
  • ISOs & resellers
  • Retail & QSR
  • Kiosk operators

Developers

  • Developers
  • Trust centre
  • Changelog

Field

  • Book a demo
  • Open Field
  • Privacy policy
  • Terms of service
  • Report a vulnerability
© 2026 Orthoplex Solutions. TickFlow and TickFlow Field are products of Orthoplex Solutions.Pilot targets and figures marked illustrative are not results.ServiceNow, Zendesk and ClickUp are trademarks of their respective owners (ClickUp™ of Mango Technologies, Inc.), named to show compatibility; no partnership is implied, and TickFlow is not affiliated with, endorsed by or sponsored by them.