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

How it works

Six steps. One loop. Nothing left to guesswork.

Step through one report from a payment terminal: what happens on the device, what happens in Field, and who gets to decide at each point.

NORTHWIND PAYDowntown T-06 · PAX A920 Pro
FR-1001 · card readerFIXED REMOTELYapp.restart v3 · verified14:33:51 · no visit needed
CA$185 saved
14:32
Northwind PayLane 2
TotalCA$42.50
Card reader not respondingError E-R07. Try again or use another payment method.Try again
ReadyCard reader connected. Insert, tap or swipe.
Report a problemCard readerPrinterNetwork
  • Screenshot
  • Logs · last 30 min
  • Device state
  • Card numbers → [PAN]
Redacted on this terminal before it is sent.
Sent · FR-1001Ticket opened in 39 s. We are looking into it.Diagnosing
Fixing remotelyRestarting the payment app. No payment is in progress.
Report a problem

Step through it

One report, start to finish.

Use the tabs or the arrow keys. Each step shows the device, Field and the decision maker side by side.

On the device
The cashier taps the floating Report a problem button, picks a category if they want (Card reader, Printer, Network, App frozen, Other) and carries on serving.
In Field
Nothing yet: the device was dormant. Its only traffic so far was a small signed check-in.
Who decides
The person at the counter, or an authorised person who triggers a remote capture.
Report a problem
  • Screenshot
  • Logs · last 30 min
  • Device state
  • Crash & error events
  • Note: “Card reader”

1 tap · no form · works offline, uploads when it can

1 / 6

The evidence

What leaves the device, and what never does.

A report is small, redacted on the device and sent only when someone reports or an authorised person asks.

Sent with a report

  • Screenshots of what the person saw (payment screens are blanked)
  • The recent logs from the apps you choose
  • The device's state: battery, storage, network, printer and reader status, app versions
  • Crashes and errors around the report
  • The one-tap category and an optional note

Never sent

  • Card numbers, track data and PINs
  • Secrets and passwords
  • Anything at all, until someone reports or an authorised person asks

Your policy decides

Every proposed fix gets one of four answers.

AI proposes. Your policy decides, from how disruptive the fix is, how sure the diagnosis is and what the device is doing.

  • Runs on its own

    Low-impact fixes your policy allows, on a device that is idle.

  • Waits for people

    One approver for disruptive fixes, two different people for destructive ones.

  • Goes to an engineer

    Not sure enough, or the evidence looks suspicious. A person reads the report first.

  • Never runs

    Your policy forbids it, the device is protected, or the fleet has had enough changes for now.

How much runs on its own, set per customer

  1. Off
  2. Suggest only
  3. Approval for everything
  4. Automatic for low risk
  5. Automatic

Start with suggestions only. Move up when the record shows you the fixes would have been right.

The fixes

Named fixes. Never a shell.

Field runs only fixes from its signed library: restart an app, re-sync configuration, reset the network, roll back an update, reboot. The more disruptive a fix, the more people have to agree. See what Field can fix.

Never during a payment

A fix that changes something waits until no payment is in progress. If Field cannot tell, it waits and tells you it deferred.

Verify, or roll back

Every fix checks that it worked. If it did not, it is undone, the ticket says so and a person takes over.

Staged across a fleet

A fix for many devices goes to one first, then a few, then the rest, and stops on its own if results start failing.

And then it learns Rolling out

Your engineers teach it. The next fix is faster.

After a fix, an engineer confirms the AI’s root cause or corrects it. Confirmed causes become known issues, so the next report with the same fault skips the guesswork. The policy and the approvals above still decide what runs.

  1. 01AI proposes a causeRanked, with the log lines behind it.
  2. 02An engineer confirms or corrects itOne click, or the right answer.
  3. 03It becomes a known issueWith the fix that worked.
  4. 04The next one is fixed first timeMatched on arrival; your approval rules still apply.
↺ and the loop gets shorter every time

Across the fleet, the same knowledge powers clusters, regression watch after a rollout and a monthly savings report. See fleet intelligence

Detailed technical briefing available on request

The how behind this page — the evidence bundle, policy outcomes, execution stages, playbook guards and how AI triage is used — is in our technical briefing for customers, security teams and assessors. Ask us for access, then sign in.

Sign in to the briefing →

See the loop on your own terminal.

See TickFlow Field on a real PAX terminal in 30 minutes: a report, a redacted bundle, a diagnosis and a signed fix, end to end.

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.